<?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>84</VOL>
    <NO>92</NO>
    <DATE>Monday, May 13, 2019</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>Agency Health</EAR>
            <PRTPAGE P="iii"/>
            <HD>Agency for Healthcare Research and Quality</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Patient Safety Organizations:</SJ>
                <SJDENT>
                    <SJDOC>Voluntary Relinquishment from the AABB Center for Patient Safety, </SJDOC>
                    <PGS>20890</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09788</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Agricultural Marketing</EAR>
            <HD>Agricultural Marketing Service</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Soybean Promotion, Research, and Consumer Information; Beef Promotion and Research; Amendments to Allow Redirection of State Assessments to the National Program; Technical Amendments, </DOC>
                      
                    <PGS>20765-20771</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="6">2019-09700</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Agriculture</EAR>
            <HD>Agriculture Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Agricultural Marketing Service</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>20846</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09758</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Antitrust Division</EAR>
            <HD>Antitrust Division</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Changes under the National Cooperative Research and Production Act:</SJ>
                <SJDENT>
                    <SJDOC>American Society of Mechanical Engineers, </SJDOC>
                    <PGS>20908-20909</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09702</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>DirectTrust Standards, </SJDOC>
                    <PGS>20909</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09698</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Consumer Financial Protection</EAR>
            <HD>Bureau of Consumer Financial Protection</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Home Mortgage Disclosure, </DOC>
                    <PGS>20972-21041</PGS>
                    <FRDOCBP T="13MYP2.sgm" D="69">2019-08983</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>20864-20865</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09720</FRDOCBP>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09723</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Census Bureau</EAR>
            <HD>Census Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>20848-20849</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09767</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers Medicare</EAR>
            <HD>Centers for Medicare &amp; Medicaid Services</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Home Health Services; CFR Correction, </DOC>
                      
                    <PGS>20810</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="0">2019-09854</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>20890-20891</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09781</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>Procedural Justice-Informed Alternatives to Contempt Demonstration Project Data Collection, </SJDOC>
                    <PGS>20891-20893</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="2">2019-09756</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Civil Rights</EAR>
            <HD>Civil Rights Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Delaware Advisory Committee, </SJDOC>
                    <PGS>20847</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09744</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>District of Columbia Advisory Committee, </SJDOC>
                    <PGS>20847-20848</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09746</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>New Jersey Advisory Committee, </SJDOC>
                    <PGS>20846-20847</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09749</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Coast Guard</EAR>
            <HD>Coast Guard</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Fire Protection for Recreational Vessels, </DOC>
                    <PGS>20827-20838</PGS>
                    <FRDOCBP T="13MYP1.sgm" D="11">2019-09699</FRDOCBP>
                </DOCENT>
                <SJ>Safety Zone:</SJ>
                <SJDENT>
                    <SJDOC>Tall Ships Challenge Great Lakes 2019, Buffalo, NY, Cleveland, OH, Bay City, MI, Green Bay, WI, Sturgeon Bay, WI, Kenosha, WI and Erie, PA, </SJDOC>
                    <PGS>20825-20827</PGS>
                    <FRDOCBP T="13MYP1.sgm" D="2">2019-09821</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>20902</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09754</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Census Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Economic Analysis Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Foreign-Trade Zones Board</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>International Trade Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Oceanic and Atmospheric Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Telecommunications and Information Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Commodity Futures</EAR>
            <HD>Commodity Futures Trading Commission</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Certain Swap Data Repository and Data Reporting Requirements, </DOC>
                    <PGS>21044-21124</PGS>
                    <FRDOCBP T="13MYP3.sgm" D="80">2019-08788</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Defense Department</EAR>
            <HD>Defense Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Board of Visitors, National Defense University, </SJDOC>
                    <PGS>20865-20866</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09780</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Defense Business Board, </SJDOC>
                    <PGS>20866</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09737</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Defense Nuclear</EAR>
            <HD>Defense Nuclear Facilities Safety Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>20866-20867</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09884</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Economic Analysis Bureau</EAR>
            <HD>Economic Analysis Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Reporting Requirements:</SJ>
                <SJDENT>
                    <SJDOC>Annual Survey of Foreign Direct Investment in the United States, </SJDOC>
                    <PGS>20855-20856</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09794</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Annual Survey of Foreign Ocean Carriers' Expenses in the United States, </SJDOC>
                    <PGS>20856-20857</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09795</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Annual Survey of U.S. Direct Investment Abroad, </SJDOC>
                    <PGS>20851-20852</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09792</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Quarterly Survey of Financial Services Transactions Between U.S. Financial Services Providers and Foreign Persons, </SJDOC>
                    <PGS>20852</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09804</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Quarterly Survey of Foreign Airline Operators' Revenues and Expenses in the United States, </SJDOC>
                    <PGS>20849</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09790</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Quarterly Survey of Foreign Direct Investment in the United States--Transactions of U.S. Affiliate With Foreign Parent, </SJDOC>
                    <PGS>20853-20854</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09818</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Quarterly Survey of Insurance Transactions by U.S. Insurance Companies with Foreign Persons, </SJDOC>
                    <PGS>20852-20853</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09808</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Quarterly Survey of Ocean Freight Revenues and Foreign Expenses of U.S. Carriers, </SJDOC>
                    <PGS>20850-20851</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09796</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Quarterly Survey of Transactions in Selected Services and Intellectual Property with Foreign Persons, </SJDOC>
                    <PGS>20855</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09810</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Quarterly Survey of U.S. Airline Operators' Foreign Revenues and Expenses, </SJDOC>
                    <PGS>20854-20855</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09802</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <PRTPAGE P="iv"/>
                    <SJDOC>Quarterly Survey of U.S. Direct Investment Abroad--Transactions of U.S. Reporter with Foreign Affiliate, </SJDOC>
                    <PGS>20849-20850</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09809</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Education Department</EAR>
            <HD>Education Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Educational Opportunity Centers Program Annual Performance Report, </SJDOC>
                    <PGS>20867-20868</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09722</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Significant Disproportionality State Survey, </SJDOC>
                    <PGS>20867</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09811</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Energy Department</EAR>
            <HD>Energy Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Energy Regulatory Commission</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Nuclear Security Administration</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>20870-20871</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09783</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Response to Recommendation 2019-1 of the Defense Nuclear Facilities Safety Board, Uncontrolled Hazard Scenarios and Implementation at the Pantex Plant, </DOC>
                    <PGS>20868-20870</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="2">2019-09782</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Environmental Protection</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Air Quality Implementation Plans; Approvals and Promulgations:</SJ>
                <SJDENT>
                    <SJDOC>Maryland; Reasonably Available Control Technology for Cement Kilns, Revisions to Portland Cement Manufacturing Plant and Natural Gas Compression Station Regulations, and Removal of Nitrogen Oxides Reduction and Trading Program Replaced by Other Programs and Regulations; Correction, </SJDOC>
                      
                    <PGS>20808-20810</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="2">2019-09336</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Air Quality State Implementation Plans; Approvals and Promulgations:</SJ>
                <SJDENT>
                    <SJDOC>Partial Approval, Partial Disapproval and Limited Approval, Limited Disapproval of Arizona Air Plan Revisions, Pinal County Air Quality Control District, </SJDOC>
                    <PGS>20838-20843</PGS>
                    <FRDOCBP T="13MYP1.sgm" D="5">2019-09830</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Receipt of Several Pesticide Petitions Filed for Residues of Pesticide Chemicals in or on Various Commodities, </DOC>
                    <PGS>20843-20845</PGS>
                    <FRDOCBP T="13MYP1.sgm" D="2">2019-09776</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>RadNet, </SJDOC>
                    <PGS>20880-20881</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09833</FRDOCBP>
                </SJDENT>
                <SJ>Enforcement and Compliance:</SJ>
                <SJDENT>
                    <SJDOC>Enhancing EPA-State Planning and Communication, </SJDOC>
                    <PGS>20882</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09764</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Ozone Transport Commission  and the Mid-Atlantic Northeast Visibility Union, </SJDOC>
                    <PGS>20881-20882</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09774</FRDOCBP>
                </SJDENT>
                <SJ>Permits:</SJ>
                <SJDENT>
                    <SJDOC>Federal Indian Country Minor New Source Review Program, </SJDOC>
                    <PGS>20879-20880</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09831</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Product Cancellation Order for Certain Pesticide Registrations and Amendments to Terminate Uses, </DOC>
                    <PGS>20882-20885</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="3">2019-09778</FRDOCBP>
                </DOCENT>
                <SJ>Registration Review:</SJ>
                <SJDENT>
                    <SJDOC>Draft Human Health and/or Ecological Risk Assessments for Several Pesticides, </SJDOC>
                    <PGS>20885-20887</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="2">2019-09777</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Aviation</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Airworthiness Directives:</SJ>
                <SJDENT>
                    <SJDOC>The Boeing Company Airplanes, </SJDOC>
                      
                    <PGS>20772-20774</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="2">2019-09747</FRDOCBP>
                </SJDENT>
                <SJ>Amendment of Class E Airspace:</SJ>
                <SJDENT>
                    <SJDOC>Mount Vernon, IL, </SJDOC>
                      
                    <PGS>20774-20776</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="2">2019-09701</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Airworthiness Directives:</SJ>
                <SJDENT>
                    <SJDOC>Airbus SAS Airplanes, </SJDOC>
                    <PGS>20822-20823</PGS>
                    <FRDOCBP T="13MYP1.sgm" D="1">2019-09742</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Learjet Inc. Airplanes, </SJDOC>
                    <PGS>20823-20825</PGS>
                    <FRDOCBP T="13MYP1.sgm" D="2">2019-09689</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals</SJ>
                <SJDENT>
                    <SJDOC>Renewal, Maintenance, Preventive Maintenance, Rebuilding, and Alteration, </SJDOC>
                    <PGS>20946</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09770</FRDOCBP>
                </SJDENT>
                <SJ>Petition for Exemption; Summary:</SJ>
                <SJDENT>
                    <SJDOC>Bell Helicopter Textron, </SJDOC>
                    <PGS>20945-20946</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09824</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Bureau</EAR>
            <HD>Federal Bureau of Investigation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Number of Full-time Law Enforcement Employees as of October 31, </SJDOC>
                    <PGS>20909-20910</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09769</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Communications</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Use of Spectrum Bands above 24 GHz for Mobile Radio Services, </DOC>
                      
                    <PGS>20810-20820</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="10">2019-09426</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Energy</EAR>
            <HD>Federal Energy Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Combined Filings, </DOC>
                    <PGS>20872-20877</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09713</FRDOCBP>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09714</FRDOCBP>
                    <FRDOCBP T="13MYN1.sgm" D="2">2019-09718</FRDOCBP>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09772</FRDOCBP>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09773</FRDOCBP>
                </DOCENT>
                <SJ>Complaint:</SJ>
                <SJDENT>
                    <SJDOC>TransMontaigne Partners, LP and Metroplex Energy, Inc. v. Colonial Pipeline Co., </SJDOC>
                    <PGS>20877-20878</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09709</FRDOCBP>
                </SJDENT>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Venture Global Plaquemines LNG, LLC and Venture Global Gator Express, LLC; Plaquemines LNG and Gator Express Pipeline Project, </SJDOC>
                    <PGS>20871-20872</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09719</FRDOCBP>
                </SJDENT>
                <SJ>Initial Market-Based Rate Filings Including Requests for Blanket Section 204 Authorizations:</SJ>
                <SJDENT>
                    <SJDOC>Glen Ullin Energy Center, LLC, </SJDOC>
                    <PGS>20875-20876</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09705</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>MeterGenius, Inc., </SJDOC>
                    <PGS>20872</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09706</FRDOCBP>
                </SJDENT>
                <SJ>Petition for Declaratory Order:</SJ>
                <SJDENT>
                    <SJDOC>Alternative Transmission Inc., </SJDOC>
                    <PGS>20878</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09716</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Indicated Generation Owners, </SJDOC>
                    <PGS>20873</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09708</FRDOCBP>
                </SJDENT>
                <SJ>Request under Blanket Authorization</SJ>
                <SJDENT>
                    <SJDOC>National Fuel Gas Supply Corp., </SJDOC>
                    <PGS>20878-20879</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09715</FRDOCBP>
                </SJDENT>
                <SJ>Request under Blanket Authorization:</SJ>
                <SJDENT>
                    <SJDOC>Equitrans, LP, </SJDOC>
                    <PGS>20875</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09707</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Reserve</EAR>
            <HD>Federal Reserve System</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Change in Bank Control:</SJ>
                <SJDENT>
                    <SJDOC>Acquisitions of Shares of a Bank or Bank Holding Company, </SJDOC>
                    <PGS>20887</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09793</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Formations of, Acquisitions by, and Mergers of Bank Holding Companies, </DOC>
                    <PGS>20887</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09791</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Trade</EAR>
            <HD>Federal Trade Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Guides for the Nursery Industry, </DOC>
                      
                    <PGS>20776-20777</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="1">2019-09745</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Labeling and Advertising of Home Insulation, </DOC>
                      
                    <PGS>20777-20790</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="13">2019-09622</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Granting of Requests for Early Termination of the Waiting Period under the Premerger Notification Rules, </DOC>
                    <PGS>20887-20890</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="3">2019-09815</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fish</EAR>
            <HD>Fish and Wildlife Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Endangered and Threatened Species:</SJ>
                <SJDENT>
                    <SJDOC>Incidental Take Permit Application and Proposed Habitat Conservation Plan for the Sand Skink, Lake County, FL; Categorical Exclusion, </SJDOC>
                    <PGS>20907-20908</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09711</FRDOCBP>
                </SJDENT>
                <PRTPAGE P="v"/>
                <SJ>Incidental Take Permit Application:</SJ>
                <SJDENT>
                    <SJDOC>Proposed Habitat Conservation Plan for the Sand Skink, Orange County, FL; Categorical Exclusion, </SJDOC>
                    <PGS>20908</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09712</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Proposed Habitat Conservation Plan for the Scrub-Jay and Eastern Indigo Snake, Volusia County, FL; Categorical Exclusion, </SJDOC>
                    <PGS>20906-20907</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09710</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food and Drug</EAR>
            <HD>Food and Drug Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Determination of Regulatory Review Period for Purposes of Patent Extension:</SJ>
                <SJDENT>
                    <SJDOC>AUSTEDO, </SJDOC>
                    <PGS>20896-20897</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09805</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>GORE VIABAHN VBX BALLOON EXPANDABLE ENDOPROSTHESIS, </SJDOC>
                    <PGS>20894-20896</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="2">2019-09817</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Financial Transparency and Efficiency of the Prescription Drug User Fee Act, Biosimilar User Fee Act, and Generic Drug User Fee Amendments, </SJDOC>
                    <PGS>20893-20894</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09803</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Foreign Trade</EAR>
            <HD>Foreign-Trade Zones Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Authorization of Production Activity:</SJ>
                <SJDENT>
                    <SJDOC>Fluid Equipment Development Co., LLC, Foreign-Trade Zone 70, Detroit, MI, </SJDOC>
                    <PGS>20857</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09789</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health and Human</EAR>
            <HD>Health and Human Services Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Agency for Healthcare Research and Quality</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Centers for 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>Health Resources and Services Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Inspector General Office, Health and Human Services Department</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Institutes of Health</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Health Resources</EAR>
            <HD>Health Resources and Services Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Testing Services and Scores for Foreign Health Care Workers to Demonstrate English Language Proficiency, </DOC>
                    <PGS>20897-20899</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="2">2019-09730</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Homeland</EAR>
            <HD>Homeland Security Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Coast Guard</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>U.S. Customs and Border Protection</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Housing</EAR>
            <HD>Housing and Urban Development Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Mortgage and Loan Insurance Programs under the National Housing Act—Debenture Interest Rates, </DOC>
                    <PGS>20905-20906</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09828</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Inspector General Health</EAR>
            <HD>Inspector General Office, Health and Human Services Department</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Program Integrity—Medicare and State Health Care Programs; CFR Correction, </DOC>
                      
                    <PGS>20810</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="0">2019-09856</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Interior</EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Fish and Wildlife Service</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Internal Revenue</EAR>
            <HD>Internal Revenue Service</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Recognition and Deferral of Section 987 Gain or Loss, </DOC>
                      
                    <PGS>20790-20801</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="11">2019-09552</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>User Fees Relating to Enrolled Agents and Enrolled Retirement Plan Agents, </DOC>
                      
                    <PGS>20801-20804</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="3">2019-09732</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Withholding of Tax and Information Reporting with Respect to Interests in Partnerships Engaged in the Conduct of a U.S. Trade or Business, </DOC>
                    <PGS>21198-21225</PGS>
                    <FRDOCBP T="13MYP5.sgm" D="27">2019-09515</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Quarterly Publication of Individuals, Who Have Chosen to Expatriate, </DOC>
                    <PGS>20954-20968</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="14">2019-09731</FRDOCBP>
                </DOCENT>
            </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 Magnesia Carbon Bricks from the People's Republic of China, </SJDOC>
                    <PGS>20857-20858</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09785</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Fresh Tomatoes from Mexico, </SJDOC>
                    <PGS>20858-20861</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="3">2019-09786</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice Department</EAR>
            <HD>Justice Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Antitrust Division</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Bureau of Investigation</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Proposed Consent Decree:</SJ>
                <SJDENT>
                    <SJDOC>CERCLA, </SJDOC>
                    <PGS>20910</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09771</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Legal</EAR>
            <HD>Legal Services Corporation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>20910</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09918</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>NASA</EAR>
            <HD>National Aeronautics and Space Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>National Environmental Policy Act; Wallops Flight Facility; Site-wide, </SJDOC>
                    <PGS>20910-20912</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="2">2019-09763</FRDOCBP>
                </SJDENT>
            </CAT>
        </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>Daimler Trucks North America, LLC, </SJDOC>
                    <PGS>20951-20954</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="3">2019-09753</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>FCA US, LLC and Volkswagen Group of America, Inc., </SJDOC>
                    <PGS>20948-20951</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="3">2019-09751</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Spartan Motors USA, Inc., </SJDOC>
                    <PGS>20947-20948</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09752</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Institute</EAR>
            <HD>National Institutes of Health</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Eunice Kennedy Shriver National Institute of Child Health and Human Development, </SJDOC>
                    <PGS>20901-20902</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09735</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Cancer Institute, </SJDOC>
                    <PGS>20900</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09736</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Center for Complementary and Integrative Health, </SJDOC>
                    <PGS>20899-20900</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09739</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute of Diabetes and Digestive and Kidney Diseases, </SJDOC>
                    <PGS>20899-20901</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09733</FRDOCBP>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09740</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute on Aging, </SJDOC>
                    <PGS>20899</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09738</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Office of the Director, </SJDOC>
                    <PGS>20900</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09734</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Energy National Nuclear</EAR>
            <HD>National Nuclear Security Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Defense Programs Advisory Committee, </SJDOC>
                    <PGS>20871</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09762</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Oceanic</EAR>
            <HD>National Oceanic and Atmospheric Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Fisheries of the Northeastern United States:</SJ>
                <SJDENT>
                    <SJDOC>Northeast Multispecies Fishery; Common Pool Measures for Fishing Year 2019; Correction, </SJDOC>
                      
                    <PGS>20820-20821</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="1">2019-09826</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Taking and Importing Marine Mammals:</SJ>
                <SJDENT>
                    <SJDOC>U.S. Navy Training and Testing in the Atlantic Fleet Training and Testing Study Area, </SJDOC>
                    <PGS>21126-21196</PGS>
                    <FRDOCBP T="13MYP4.sgm" D="70">2019-09541</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <PRTPAGE P="vi"/>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Application for Exempted Fishing Permits, </DOC>
                    <PGS>20862</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09787</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Science</EAR>
            <HD>National Science Foundation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>20912-20913</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09741</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Telecommunications</EAR>
            <HD>National Telecommunications and Information Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>State and Local Implementation Grant Program 2.0 Closeout Documentation, </SJDOC>
                    <PGS>20862-20863</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09766</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Postal Regulatory</EAR>
            <HD>Postal Regulatory Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Periodic Reporting, </DOC>
                      
                    <PGS>20806-20808</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="2">2019-09779</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>New Postal Product, </DOC>
                    <PGS>20913</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09816</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Postal Service</EAR>
            <HD>Postal Service</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Inspection Service Authority; Civil Monetary Penalty Inflation Adjustment, </DOC>
                      
                    <PGS>20804-20806</PGS>
                      
                    <FRDOCBP T="13MYR1.sgm" D="2">2019-09436</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Presidential Documents</EAR>
            <HD>Presidential Documents</HD>
            <CAT>
                <HD>PROCLAMATIONS</HD>
                <DOCENT>
                    <DOC>Southern U.S. Border; Addressing Mass Migration Through (Proc. 9880), </DOC>
                    <PGS>21227-21231</PGS>
                    <FRDOCBP T="13MYD0.sgm" D="4">2019-09992</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Railroad Retirement</EAR>
            <HD>Railroad Retirement Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>20913-20914</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09950</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Securities</EAR>
            <HD>Securities and Exchange Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>20914, 20919-20920, 20939-20940</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09797</FRDOCBP>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09798</FRDOCBP>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09799</FRDOCBP>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09801</FRDOCBP>
                </DOCENT>
                <SJ>Application:</SJ>
                <SJDENT>
                    <SJDOC>ALPS Variable Investment Trust, et al., </SJDOC>
                    <PGS>20914-20915</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09721</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Toroso Investments, LLC and Tidal ETF Trust, </SJDOC>
                    <PGS>20933-20935</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="2">2019-09800</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>20944</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09894</FRDOCBP>
                </DOCENT>
                <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
                <SJDENT>
                    <SJDOC>BOX Exchange, LLC, </SJDOC>
                    <PGS>20940-20944</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="4">2019-09724</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Cboe BYX Exchange, Inc., </SJDOC>
                    <PGS>20935-20937</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="2">2019-09727</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Cboe BZX Exchange, Inc., </SJDOC>
                    <PGS>20937-20939</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="2">2019-09728</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Cboe EDGA Exchange, Inc., </SJDOC>
                    <PGS>20917-20919</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="2">2019-09725</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Cboe EDGX Exchange, Inc., </SJDOC>
                    <PGS>20915-20917, 20920-20933</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="2">2019-09726</FRDOCBP>
                    <FRDOCBP T="13MYN1.sgm" D="13">2019-09729</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Small Business</EAR>
            <HD>Small Business Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Administrator's Line of Succession Designation, </DOC>
                    <PGS>20944</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09775</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>State Department</EAR>
            <HD>State Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals</SJ>
                <SJDENT>
                    <SJDOC>Request for Commodity Jurisdiction Determination, </SJDOC>
                    <PGS>20945</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09827</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Advisory Committee for the Study of Eastern Europe and the Independent States of the Former Soviet Union, </SJDOC>
                    <PGS>20944-20945</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09784</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>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>
        </AGCY>
        <AGCY>
            <EAR>Customs</EAR>
            <HD>U.S. Customs and Border Protection</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Commercial Gaugers and Laboratories; Accreditation and Approval:</SJ>
                <SJDENT>
                    <SJDOC>AmSpec, LLC (Savannah, GA), </SJDOC>
                    <PGS>20903-20904</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09835</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>AmSpec, LLC (Texas City, TX), </SJDOC>
                    <PGS>20903</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="0">2019-09832</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Freeboard International (Linden, NJ), </SJDOC>
                    <PGS>20904-20905</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09834</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Veteran Affairs</EAR>
            <HD>Veterans Affairs Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Privacy Act; Matching Program, </DOC>
                    <PGS>20968-20969</PGS>
                    <FRDOCBP T="13MYN1.sgm" D="1">2019-09757</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Bureau of Consumer Financial Protection, </DOC>
                <PGS>20972-21041</PGS>
                <FRDOCBP T="13MYP2.sgm" D="69">2019-08983</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Commodity Futures Trading Commission, </DOC>
                <PGS>21044-21124</PGS>
                <FRDOCBP T="13MYP3.sgm" D="80">2019-08788</FRDOCBP>
            </DOCENT>
            <HD>Part IV</HD>
            <DOCENT>
                <DOC>Commerce Department, National Oceanic and Atmospheric Administration, </DOC>
                <PGS>21126-21196</PGS>
                <FRDOCBP T="13MYP4.sgm" D="70">2019-09541</FRDOCBP>
            </DOCENT>
            <HD>Part V</HD>
            <DOCENT>
                <DOC>Treasury Department, Internal Revenue Service, </DOC>
                <PGS>21198-21225</PGS>
                <FRDOCBP T="13MYP5.sgm" D="27">2019-09515</FRDOCBP>
            </DOCENT>
            <HD>Part VI</HD>
            <DOCENT>
                <DOC>Presidential Documents, </DOC>
                <PGS>21227-21231</PGS>
                <FRDOCBP T="13MYD0.sgm" D="4">2019-09992</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>84</VOL>
    <NO>92</NO>
    <DATE>Monday, May 13, 2019</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="20765"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Agricultural Marketing Service</SUBAGY>
                <CFR>7 CFR Parts 1220 and 1260</CFR>
                <DEPDOC>[No. AMS-LPS-13-0083]</DEPDOC>
                <RIN>RIN 0581-AD49</RIN>
                <SUBJECT>Soybean Promotion, Research, and Consumer Information; Beef Promotion and Research; Amendments To Allow Redirection of State Assessments to the National Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Agricultural Marketing Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; technical amendments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This final rule amends the Soybean Promotion, Research, and Consumer Information Order (Soybean Order) and the Beef Promotion and Research Order (Beef Order) to add provisions allowing producers subject to these Orders to request, under certain circumstances, that their assessments paid to a State board or council authorized under their respective statutes, be redirected to the national program. The final rule also makes technical amendments to the Beef Order.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The final rule is effective June 12, 2019.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kenneth Payne, Research and Promotion Division, at (202) 720-1118, fax (202) 720-1125, or by email at 
                        <E T="03">Kenneth.Payne@ams.usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Executive Orders 12866 and 13771</HD>
                <P>This rulemaking does not meet the definition of a significant regulatory action contained in section 3(f) of Executive Order 12866 and is not subject to review by the Office of Management and Budget (OMB). Additionally, because this rule does not meet the definition of a significant regulatory action it does not trigger the requirements contained in Executive Order 13771. See OMB's Memorandum titled “Interim Guidance Implementing Section 2 of the Executive Order of January 30, 2017, titled `Reducing Regulation and Controlling Regulatory Costs' ” (February 2, 2017).</P>
                <HD SOURCE="HD1">Executive Order 12988</HD>
                <P>This final rule has been reviewed under Executive Order 12988, Civil Justice Reform. It is not intended to have retroactive effect.</P>
                <HD SOURCE="HD1">Executive Order 13175</HD>
                <P>AMS has assessed the impact of this final rule on Indian tribes and determined that this rule will not, to our knowledge, have tribal implications that require tribal consultation under Executive Order 13175. If a Tribe requests consultation, AMS will work with the Department of Agriculture's (USDA) Office of Tribal Relations to ensure meaningful consultation is provided where changes, additions, and modifications are identified in this final rule.</P>
                <HD SOURCE="HD1">Background Summary and Final Action Taken</HD>
                <HD SOURCE="HD2">Soybean Order</HD>
                <P>The Soybean Promotion, Research, and Consumer Information Act (Soybean Act) (7 U.S.C. 6301-6311) provides that administrative proceedings must be exhausted before parties may file suit in court. Under section 1971 of the Soybean Act, a person subject to the Soybean Order may file a petition with USDA stating that the Soybean Order, any provision of the Soybean Order, or any obligation imposed in connection with the Soybean Order, is not in accordance with the law and request a modification of the Soybean Order or an exemption from the Soybean Order. The petitioner is afforded the opportunity for a hearing on the petition. After a hearing, USDA would rule on the petition. The Soybean Act provides that district courts of the United States in any district in which such person is an inhabitant, or has their principal place of business, has jurisdiction to review USDA's ruling on the petition, if a complaint for this purpose is filed within 20 days after the date of the entry of the ruling.</P>
                <P>Further, section 1974 of the Soybean Act provides, with certain exceptions, that nothing in the Soybean Act may be construed to preempt or supersede any other program relating to soybean promotion, research, consumer information, or industry information organized under the laws of the United States or any State. One exception in the Soybean Act concerns assessments collected by Qualified State Soybean Boards (QSSBs). The exception provides that to ensure adequate funding of the operations of QSSBs under the Soybean Act, no State law or regulation may limit or have the effect of limiting the full amount of assessments that a QSSB in that State may collect, and which is authorized to be credited under the Soybean Act. Another exception concerns certain referenda conducted during specified periods by a State relating to the continuation of a QSSB or State soybean assessment.</P>
                <HD SOURCE="HD2">Beef Order</HD>
                <P>Section 11 of the Beef Research and Promotion Act of 1985 (Beef Act) (7 U.S.C. 2901-2911) provides that nothing in the Beef Act may be construed to preempt or supersede any other program relating to beef promotion organized and operated under the laws of the United States or any State. There are no administrative proceedings that must be exhausted prior to any judicial challenge to the provisions of this rule.</P>
                <HD SOURCE="HD2">Soybean Order Amendments</HD>
                <P>The Soybean Act and the Soybean Order issued thereunder authorize the collection of an assessment from soybean producers of one-half of one percent (0.5 percent) of the net market value of soybeans, processed soybeans, or soybean products. In most cases, these assessments are collected by QSSBs that retain up to half of the assessments as authorized by the Soybean Act. The QSSBs as defined under Section 1967(14) of the Soybean Act will forward the remainder to the United Soybean Board (Soybean Board), which administers the national soybean checkoff program.</P>
                <P>
                    The original Soybean Order, which became effective July 9, 1991, mandated that all producers marketing soybeans pay an assessment of one-half of one percent (0.5 percent) of the net market price of the market price of soybeans sold. The original Soybean Order contained a provision in § 1220.228(b)(5)(i), which required QSSBs that were authorized or required 
                    <PRTPAGE P="20766"/>
                    to pay refunds to producers to certify to the Soybean Board that they would honor any request from a producer for a refund from the QSSB by forwarding to the Soybean Board those contributions for which the producer received a credit, pursuant to § 1220.223(a)(3). In other words, this section implicitly authorized refunds by the QSSB if State law allowed or required the QSSB to pay refunds; it further directed that the producer receive a credit for those refunds, with the amount sent to the Soybean Board.
                </P>
                <P>In late 1995, 7 CFR 1220.228(b)(5)(i) was removed as part of a referendum process and rulemaking to eliminate obsolete regulatory language. However, the rulemaking inadvertently removed language that should have been retained regarding a producer's ability to redirect funds to the national program should they choose to do so. While this provision was removed from the order, QSSBs were still required to comply with the terms of their certification as a QSSB and, therefore, continued to allow for redirection of funds at the producer's request.</P>
                <P>In States where payments to a QSSB are not required by State law, the opportunity for producers to choose, on a monthly basis, to direct the full federal assessment to the Soybean Board is already AMS' current policy and required under a QSSB's certification; this rule is intended to formalize the policy. Therefore, AMS is adding provisions that remedy the removal of the original refund language. A new provision is added to the Soybean Order to (i) require producers in States where refunds are authorized to forward that refund to the Soybean Board and (ii) provide an opportunity for a refund if the QSSB is not authorized by State statute but is organized and operating within a State and is certified by the Soybean Board, as provided by § 1220.228(a)(2). To avail themselves of this option, producers need to submit to their QSSB a form (QSSB-1) postmarked by the 30th day of the month following the month the soybeans were sold. Assessments will not be able to be retroactively redirected from the QSSB to the Soybean Board. Likewise, AMS will require that the QSSB must respond by the last day of the month following the month in which the OMB-approved QSSB-1 form was received.</P>
                <P>Regardless of a State's requirements or refunding provisions, a producer is required by the Soybean Act to pay an assessment of one-half of one percent (0.5 percent) of the net market value of soybeans, processed soybeans, or soybean products. Several States have additional producer assessments, mandated by State statutes, that are collected in addition to the assessment required by the Soybean Act. If a QSSB offers a producer refund under a State statute, the QSSB can only refund to the producer any State assessment collected in excess of the assessment that the producer is required to pay under the Soybean Act. AMS will allow the portion of the assessment compelled by the Soybean Act that the QSSB would normally keep to be redirected to the national program by the producer if State law allows.</P>
                <P>Examples:</P>
                <P>
                    • 
                    <E T="03">Example 1—States with no State Law:</E>
                     A soybean producer in California pays an assessment for a soybean sale. The assessment is collected by a certified Western Region Soybean Board, which keeps 50% and forwards the remaining 50% to the Soybean Board. California has no State law requiring a California assessment, so the California producer 
                    <E T="03">may</E>
                     request that the 50% of the assessment amount retained by the Western Region Soybean Board be redirected to the Soybean Board.
                </P>
                <P>
                    • 
                    <E T="03">Example 2—States with a State Law that Authorizes Refunds:</E>
                     A soybean producer in Iowa pays an assessment for a soybean sale. The assessment is collected by Iowa Soybean Promotion Board, which keeps 50% and forwards the remaining 50% to the Soybean Board. Iowa has a State law with a refund provision, so the Iowa producer 
                    <E T="03">may</E>
                     request that the 50% of the assessment amount retained by the Iowa Soybean Promotion Board be redirected to the Soybean Board.
                </P>
                <P>
                    • 
                    <E T="03">Example 3—States with a State Law that Does Not Authorize Refunds:</E>
                     A soybean producer in Virginia pays an assessment for a soybean sale. The assessment is collected by the Virginia Soybean Board which keeps 50% and forwards the remaining 50% to the Soybean Board. Virginia has a State law with no refund provision, so the Virginia soybean producer 
                    <E T="03">may not</E>
                     request that the 50% of the assessment amount retained by the Virginia Soybean Board be redirected to the Soybean Board.
                </P>
                <HD SOURCE="HD2">Beef Order Amendments</HD>
                <P>
                    Similarly, the Beef Promotion and Research Act of 1985 (Beef Act) and the Beef Promotion and Research Order (Beef Order) issued thereunder authorize the collection of an assessment from cattle producers of $1.00 per head of cattle sold. In most cases, these assessments are collected by Qualified State Beef Councils (QSBCs) that retain up to one-half of the assessments, as authorized by the Beef Act.
                    <SU>1</SU>
                    <FTREF/>
                     The QSBCs, as defined under Section 3(14) of the Beef Act, are required to forward the remainder to the Cattlemen's Beef Promotion and Research Board (Beef Board), which administers the national beef checkoff program.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The Montana Beef Council is currently required by court order to obtain prior affirmative consent from producers before retaining any portion of the federal assessment.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Section 3(14) of the Beef Act states that “the term “qualified State beef council” means a beef promotion entity that is authorized by State statute or is organized and operating within a State, that receives voluntary contributions and conducts beef promotion, research, and consumer information programs, and that is recognized by the Board as the beef promotion entity within such State.” 7 U.S.C. 2902(14). Likewise, 7 CFR 1260.115 of the Beef Order states “
                        <E T="03">Qualified State beef council</E>
                         means a beef promotion entity that is authorized by State statute or a beef promotion entity organized and operating within a State that receives voluntary assessments or contributions; conducts beef promotion, research, and consumer and industry information programs; and that is certified by the Board pursuant to this subpart as the beef promotion entity in such State.”
                    </P>
                </FTNT>
                <P>The original Beef Order, which became effective July 18, 1986, mandated that all producers owning and marketing cattle pay an assessment of $1.00 per head of cattle, to be collected each time cattle are sold. The original Beef Order contained a provision in § 1260.181(b)(5), which required QSBCs that were authorized or required by State law to pay refunds to producers to certify to the Beef Board that they would honor any request from a producer for a refund from the QSBC by forwarding to the Beef Board those contributions for which the producer received a credit, pursuant to § 1260.172(a)(3). In other words, this section authorized refunds by the QSBC if State law allowed or required the QSBC to pay refunds; it further directed that the producer receive a credit for those refunds, with the amount redirected to the Beef Board.</P>
                <P>In late 1995, 7 CFR 1260.181(b)(5) was removed as part of rulemaking to eliminate obsolete regulatory language. However, the rulemaking inadvertently removed language that should have been retained regarding a producer's ability to redirect funds to the national program should they choose to do so. While this provision was removed from the order, QSBCs were still required to comply with the terms of their certification as a QSBC and, therefore, continued to allow for redirection of funds at the producer's request. Therefore, AMS is adding provisions to remedy the removal of the original language in § 1260.181.</P>
                <P>
                    Furthermore, while the Beef Act and Beef Order authorize QSBCs to retain up to 50 cents per head of cattle assessed, neither the Beef Act nor the Beef Order 
                    <PRTPAGE P="20767"/>
                    require producers to contribute a portion of the $1.00-per-head assessment to a QSBC. Thus, unless a State statute requires the collection of the $1.00-per-head assessment set forth in the Beef Act (the federal assessment) or requires producers to contribute a portion of the $1.00-per-head federal assessment to the State beef council, producers are able to choose whether or not to contribute up to 50 cents per head of the federal assessment to their QSBC. While the original Beef Order did not address the specific situation that allows producers to choose whether or not to contribute up to 50 cents per head of the federal assessment to a QSBC, AMS is addressing this in the new language. A new provision is being added to the Beef Order to (i) require QSBCs in States where refunds to producers of the $1.00-per-head assessment collected per the Beef Act and Order are authorized by State statute to forward that refund to the Beef Board, and (ii) provide an opportunity for producers to choose to direct the full $1.00-per-head federal assessment to the Beef Board in States where State law does not require the collection of the $1.00-per-head assessment set forth in the Beef Act (the federal assessment) or in States where State statutes do not require producers to contribute a portion of the $1.00-per head federal assessment to the State beef council.
                </P>
                <P>
                    In States where payments to a QSBC are not required by State law, the opportunity for producers to choose, on a monthly basis, to direct the full $1.00-per-head federal assessment to the Beef Board is already AMS' current policy; this rule is intended to formalize the policy. The Beef Board also conveyed this policy in its July 26, 2018, memo “Obligation to Redirect Assessments Upon Producer Request if Not Precluded by State Law.
                    <SU>3</SU>
                    <FTREF/>
                     As QSBCs are responsible for collecting assessments on cattle sold in or originating in their State (§§ 1260.172(a)(5) and 1260.181(b)(3)), producers who are allowed refunds under State statutes and choose to redirect the full $1.00-per-head assessment to the Beef Board must submit to the QSBC a written request on an approved request form (QSBC-1).
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">https://www.beefboard.org/library/files/redirection-memo-072916.pdf</E>
                        .
                    </P>
                </FTNT>
                <P>
                    QSBCs generally describe the requirements and process for refunds in their Application for Certification that is reviewed and approved by the Beef Board. As part of their certification requirements, QSBCs must certify that any requests from producers for refunds will be honored by forwarding such request to the Beef Board if allowed by state law. In practice, QSBCs follow similar operating procedures for collecting the $1.00-per-head assessment across collection points (
                    <E T="03">e.g.,</E>
                     markets, dealers, brokers) and are required to reconcile transactions on a monthly basis.
                    <SU>4</SU>
                    <FTREF/>
                     To align with their monthly reconciliation and budget planning, QSBCs provide for a monthly process through which producers can, if allowed by state law, redirect their assessments to the Beef Board. To avail themselves of this option, producers must submit a QSBC-1 form that is postmarked by the 15th day of the month following the month the cattle were sold. Assessments cannot be retroactively redirected from the QSBC to the Beef Board, and QSBCs will be required to respond to such requests within 60 days.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Cattlemen's Beef Board January 26, 2018, Guidelines for Qualified State Beef Councils.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Montana Beef Council (MBC) presently operates differently and is therefore an exception to this process. Under a Preliminary Injunction in 
                        <E T="03">R-CALF</E>
                         v. 
                        <E T="03">Sonny Perdue,</E>
                         MBC is required to obtain affirmative consent from producers before retaining 
                        <E T="03">any</E>
                         portion of the federal assessment. As a result, MBC collects and sends all assessments to the Beef Board unless producers request, currently on an annual basis, that $0.50 of the $1.00-per-head assessment be provided back to MBC.
                    </P>
                </FTNT>
                <P>Regardless of a State's requirements or refunding provisions, a producer is required by the Beef Act to pay an assessment of $1.00 on each head of cattle sold. Several States have additional producer assessments, mandated by State statutes, which are collected in addition to the $1.00-per-head assessment required by the Beef Act. If a QSBC offers a producer refund under a State statute, the QSBC can only refund to the producer any State assessment collected in addition to the $1.00-per-head assessment that the producer is required to pay under the Beef Act. This final rule provides that the portion of the $1.00-per-head federal assessment that the QSBC would normally keep under § 1260.181(b)(4) can be redirected to the national program by the producer if State law allows.</P>
                <P>Examples:</P>
                <P>
                    • 
                    <E T="03">Example 1—States with no State Law:</E>
                     A producer in Kansas pays the $1.00 federal assessment for a cattle sale. The Kansas Beef Council collects $1.00, keeps $0.50, and forwards $0.50 to the Beef Board. Since there is no Kansas law compelling producers to contribute to the Kansas Beef Council, the producer 
                    <E T="03">may</E>
                     request that the $0.50 of the original $1.00 assessment be redirected to the Beef Board. This example is depicted in Figure 1.
                </P>
                <GPH SPAN="3" DEEP="153">
                    <GID>ER13MY19.019</GID>
                </GPH>
                <P>
                    • 
                    <E T="03">Example 2—States with a State Law that Authorizes Refunds:</E>
                     A producer in Colorado pays $1.00 in assessments for a cattle sale. The Colorado Beef Council collects $1.00, keeps $0.50, and forwards $0.50 to the Beef Board. Colorado State law requires an assessment but allows a refund. The producer 
                    <E T="03">may</E>
                     request that the $0.50 
                    <PRTPAGE P="20768"/>
                    cents of the original $1.00 assessment be redirected to the Beef Board. This example is depicted in Figure 2.
                </P>
                <GPH SPAN="3" DEEP="151">
                    <GID>ER13MY19.020</GID>
                </GPH>
                <P>Based on current understanding, AMS believes that most states fall within one of these two examples—either they have no state law compelling them to contribute to a QSBC or they have a state law that provides for refunds. In either case, a producer in these states can request that the $0.50 of the original $1.00 assessment be redirected to the Beef Board.</P>
                <P>
                    • 
                    <E T="03">Example 3—States with a State Law that Does Not Authorize Refunds:</E>
                     A producer in Arizona pays $1.00 in assessments for a cattle sale. The Arizona Beef Council collects $1.00, keeps $0.50, and forwards $0.50 to the Beef Board. Arizona law compels the collection of the $1.00-per-head assessment and does not provide for a refund. The producer 
                    <E T="03">may not</E>
                     request the Arizona Beef Council to redirect any portion of the $0.50 to the Beef Board. This example is depicted in Figure 3.
                </P>
                <GPH SPAN="3" DEEP="157">
                    <GID>ER13MY19.021</GID>
                </GPH>
                <P>
                    Based on our current understanding of state laws, AMS believes that a few states fall under this example including Arizona, California, Georgia, Louisiana, Michigan, Oregon, Washington, and Wyoming. Because there is a state law in place that mandates assessments without allowing for a refund, producers in these states 
                    <E T="03">may not</E>
                     request that the $0.50 of the original $1.00 assessment be redirected to the Beef Board. In general, AMS recommends stakeholders fully consult state laws as these examples are used for illustrative purposes and are subject to change.
                </P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>Pursuant to the requirements set forth in the Regulatory Flexibility Act (RFA) (5 U.S.C. 601-612), the Administrator of the AMS has considered the economic effect of this action on small entities and has determined that this final rule will not have a significant economic impact on a substantial number of small entities. The purpose of RFA is to fit regulatory actions to the scale of businesses subject to such actions in order that small businesses will not be unduly burdened.</P>
                <HD SOURCE="HD2">Soybean Industry</HD>
                <P>USDA's Farm Service Agency estimates that there are 569,998 soybean producers subject to the Soybean Order. This estimate comes from including all soybean producers engaged in the production of soybeans in the previous 2 years. The majority of producers subject to the Soybean Order are small businesses under the criteria established by the Small Business Administration (SBA) (13 CFR 121.201). SBA defines small agricultural producers as those having annual receipts of less than $750,000.</P>
                <P>This final rule imposes no new burden on the soybean industry. This action clarifies that soybean producers, under certain circumstances, have the option to request that their assessments paid to a State board be directed to the national program. This action is not expected to change how producers or QSSBs operate with respect to directing funds when appropriate to the national program.</P>
                <P>
                    In the July 15, 2016 proposed rule, AMS provided a chart with estimates by 
                    <PRTPAGE P="20769"/>
                    state for the potential amount that could be redirected to the national program (81 FR 45987). The estimates varied depending on whether redirection was possible and the degree to which state law affected refund amounts. AMS received comments indicating that the chart was difficult to follow and, in some cases, inaccurate. As a result, AMS is generalizing its estimate of potential financial impacts to range between $0 (for those states in which redirection is not possible) to up to $14 million (for high producing soybean states in which redirection is possible). However, given that this action is not expected to change how and whether producers choose to exercise the refund provisions in states where redirection of funds is possible, AMS does not anticipate a significant increase in producer requests that would impact the amount of assessments retained by a given state.
                </P>
                <P>The information collection requirements on QSSBs are minimal. QSSBs are already required to remit assessments to the national programs. We have not identified any relevant Federal rules that duplicate, overlap, or conflict with this rule.</P>
                <P>Accordingly, AMS has determined that this final rule will not have a significant economic impact on a substantial number of small soybean entities.</P>
                <HD SOURCE="HD2">Beef Industry</HD>
                <P>In the February 2013, publication of “Farms, Land in Farms, and Livestock Operations,” USDA's National Agricultural Statistics Service (NASS) estimated that the number of operations in the United States with cattle in 2012 totaled approximately 915,000, down from 950,000 in 2009. The majority of these operations that are subject to the Beef Order may be classified as small entities. According to the NASS website “Farms, Land in Farms, and Livestock Operations,” the issues released between 2005 and 2013 included “Livestock Operations” in the title. Beginning in 2014, livestock operations data will be available in the Census of Agriculture and most recent data can be referenced from Census data.</P>
                <P>This final rule imposes no new burden on the beef industry. This action clarifies that producers, under certain circumstances, have the option of requesting that their assessments paid to a State council be directed to the national program. This action is not expected to change how producers or QSBCs operate with respect to directing funds when appropriate to the national program.</P>
                <P>In the July 15, 2016, proposed rule, AMS provided a chart with estimates by state for the potential amount that could be redirected to the national program (81 FR 45988). The estimates varied depending on whether redirection was possible and the degree to which state law affected refund amounts. AMS received comments indicating that the chart was difficult to follow and, in some cases, inaccurate. As a result, AMS is generalizing its estimate of potential financial impacts to range between $0 (for those states in which redirection is not possible) to up to $4.6 million (for high producing beef states in which redirection is possible). However, given that this action is not expected to change how and whether producers choose to exercise the refund provisions in states where redirection of funds is possible, AMS does not anticipate a significant increase in producer requests that would impact the amount of assessments retained by a given state. Currently, a few States are in various stages of establishing or amending State laws regarding beef checkoff requirements, so this information may change over time.</P>
                <P>The information collection requirements on QSBCs are minimal. QSBCs are already required to remit assessments to the national programs. We have not identified any relevant Federal rules that duplicate, overlap, or conflict with this rule.</P>
                <P>Accordingly, AMS has determined that this final rule will not have a significant economic impact on a substantial number of small producers.</P>
                <HD SOURCE="HD1">Paperwork Reduction Act</HD>
                <P>In accordance with OMB regulations (5 CFR part 1320) that implement the Paperwork Reduction Act of 1995 (44 U.S.C Chapter 35 (PRA)), this collection has been submitted to OMB with the reference number 0581-0246. Upon approval, the collection will be merged with OMB number 0581-0093, “National Research, Promotion, and Consumer Information Programs.” This final rule established the use of two new forms, which impose a total annual burden of 2.49 hours. The Producer Redirection of Checkoff Assessment forms, QSBC-1 and QSSB-1, require the minimum information necessary to effectively allow producers in certain states that pay their assessments to a State board or council authorized under their respective statutes, to redirect the assessment to the national program. The information collection requirements in the request are essential to carry out the legislative purpose of the Beef Act and the Soybean Act. Under the Beef and Soybean Orders, producers are required to pay an assessment each time cattle or soybeans are sold. While the Beef and Soybean Orders impose certain recordkeeping requirements, information required under the Beef and Soybean Orders can be compiled from records currently maintained. Such records must be retained for at least 3 years beyond the marketing year of their applicability.</P>
                <P>AMS is committed to complying with the E-Government Act, to promote the use of the internet and other information technologies to provide increased opportunities for citizen access to Government information and services, and for other purposes. As with all Federal promotion programs, reports and forms are periodically reviewed to reduce information requirements and duplication by industry and public sector agencies. In the proposed rule published July 15, 2016, (81 FR 45984) comments were invited on: (a) Whether the proposed collection of information is necessary for the proper performance of functions of the Order and USDA's oversight of the program, including whether the information will have practical utility; (b) the accuracy of USDA's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents including the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology. No separate comments were received regarding the information collection section. However, AMS received a few comments that discussed the paperwork burden of the forms. AMS's response to those comments is discussed in the comments section.</P>
                <HD SOURCE="HD1">Comments</HD>
                <P>
                    A proposed rule concerning this action was published in the 
                    <E T="04">Federal Register</E>
                     on July 15, 2016 (81 FR 45984). A 60-day comment period ending September 13, 2016, was provided for interested persons to respond to the proposal. AMS received 14 comments. Of the 14 comments received, 12 commenters referenced proposed changes to the Beef Order, one commenter referenced proposed changes to the Soybean Order, and one commenter referenced both the Soybean and Beef Orders. One commenter did not provide comments within the timeframe provided in the proposed order. However, in general, this 
                    <PRTPAGE P="20770"/>
                    commenter provided thoughts similar to those who opposed to the proposed rule.
                </P>
                <HD SOURCE="HD2">Beef Order Comments</HD>
                <P>
                    Of the 12 comments received regarding the Beef Order, over half stated that they opposed the proposed rule while the others recommended clarification, modification, or changes to the proposed rule. The majority of commenters believe that assessments should go to the national program, 
                    <E T="03">unless</E>
                     a producer provides affirmative consent that their federal assessment paid to a State council to remain with the State program. In their view, this approach would be consistent with a voluntary contribution as specified in the statute. These commenters suggest that having to request that their assessments paid to a State council be directed to the national program creates a mandatory contribution. Some commenters argued this is unconstitutional. AMS disagrees. This action continues to provide producers with a choice about where they want their funds directed. Since the inception of the national program, few producers have requested redirection of their funds to the national program, instead choosing to keep a portion of the federal assessment to support and invest in local programs and activities. For example, over the last three years, fewer than 20 producers or businesses have requested redirection of their funds to the national program. Thus, the majority of producers prefer that the QSBCs retain their assessments. Requiring the majority of producers to provide prior affirmative consent to keep their funds locally with the QSBCs would create an unnecessary burden to the industry as a whole.
                </P>
                <P>A few commenters recommended that the deadline to request a redirection be extended. However, due to the need for QSBCs to reconcile their financial transactions on a monthly basis, the deadline for a redirection request must remain as a monthly process as stated in the proposed rule.</P>
                <P>A few commenters recommended that AMS provide clarification of the individual State laws, clarify any conflicts with state laws, and modify/correct any examples provided in the rule and the tables to accurately reflect the governing state law. Specifically, the commenters requested greater clarification of the application of refunds in each state. AMS believes that application of State laws are best interpreted by the States themselves. The States, not AMS, are responsible for interpretation of their respective laws.</P>
                <P>A few commenters pointed out that some QSBC names were incorrect. AMS has updated the list as part of its technical amendments and is reflected in this final rule.</P>
                <P>One commenter requested that AMS clarify the terminology in the rule to reflect assessments of cattle producers, not “beef” producers, which, in their view, would include multinational trade associations and packers. That same commenter strongly disagreed with the assumption that only 20 operations would request a redirection. AMS modified terminology in the preamble accordingly and clarifies that it is producers as defined at § 1260.116 who are subject to assessment per the requirements at § 1260.172. Furthermore, while the commenter disagrees that only 20 producers or operations would request redirection and thus that AMS's information collection burden is too low, AMS has reviewed the number of redirection requests received over the last 3 years as the basis for its estimate. Over the last three years, fewer than 20 producers or businesses in total have requested redirection of their funds to the national program. Based on that data, AMS anticipates that the number of redirection requests will be similar to past years. Therefore, we do not believe the burden estimate is too low.</P>
                <P>One commenter recommended several rule text changes. First, the commenter recommended changes to proposed rule § 1260.181(b)(5) to correct a perceived syntax error. The commenter recommended adding two new subsections to correct. Additionally, the commenter recommended a change to § 1260.312(c) to provide clarity and consistency with § 1260.181(b)(4). AMS reviewed the comments and believes they have merit. Consequently, these technical amendments are reflected in this final rule.</P>
                <HD SOURCE="HD2">Soybean Order Comments</HD>
                <P>
                    AMS received two comments respecting the Soybean Order. Both commenters recommended a rule text change to clarify that the proposed rule applies to QSSBs subject to both § 1220.228(a)(1) and (2) of the Soybean Promotion, Research, and Consumer Information Order. Both commenters also raised concerns with how the state refund rules applied to QSSBs. With respect to the commenters' recommended new amendatory language, AMS is unclear on section cross references and believes the suggested changes include an error. Rather than adopt the commenters suggested changes as they proposed, we have made modifications to the amendatory text by adding a new § 1220.228(e) to reflect that this rule applies to all QSSBs (
                    <E T="03">i.e.,</E>
                     those entities that elect to serve due to their state authorization under § 1220.228(a)(1) and those entities that apply for certification under § 1220.228(a)(2)). AMS also moved the proposed text about producers receiving a refund and their obligations to remit this refund to the Board to the appropriate Assessments section at § 1220.223(a)(3). Further, as stated above, states are responsible for interpreting their laws, and AMS advises stakeholders to carefully review the state refund laws applicable to their state.
                </P>
                <P>Accordingly, no changes will be made to the rule as proposed other than the tables and other technical amendments.</P>
                <HD SOURCE="HD1">Beef Technical Amendments</HD>
                <P>In addition, several technical amendments are made to update information in the Beef Promotion and Research Order and rules and regulations:</P>
                <P>Section 1260.181(b)(4) currently requires QSBCs to remit assessments to the Beef Board by the last day of the month in which the QSBC received the assessment “unless the Board determines a different date.” The Beef Board's practice has been to require QSBCs to remit assessments by the 15th day of the following month. This section will be updated to reflect actual practice.</P>
                <P>Section 1260.315 is amended to reflect the current listing of QSBCs.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>7 CFR Part 1220</CFR>
                    <P>Administrative practice and procedure, Advertising, Agricultural research, Marketing agreements, Soybeans and soybean products, Reporting and recordkeeping requirements.</P>
                    <CFR>7 CFR Part 1260</CFR>
                    <P>Administrative practice and procedure, Advertising, Agricultural research, Imports, Marketing agreement, Meat and meat products, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <P>For reasons set forth in the preamble, 7 CFR parts 1220 and 1260 are amended as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1220—SOYBEAN PROMOTION, RESEARCH, AND CONSUMER INFORMATION</HD>
                </PART>
                <REGTEXT TITLE="7" PART="1220">
                    <AMDPAR>1. The authority citation for part 1220 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 7 U.S.C. 6301-6311 and 7 U.S.C. 7401.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1220">
                    <PRTPAGE P="20771"/>
                    <AMDPAR>2. In § 1220.223, revise paragraph (a)(3) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1220.223 </SECTNO>
                        <SUBJECT>Assessments.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(3) In determining the assessment due from each producer under paragraph (a)(1) or (2) of this section, a producer who is contributing to a Qualified State Soybean Board shall receive a credit from the Board for contributions to such Qualified State Soybean Board on any soybeans assessed under this section in an amount not to exceed one-quarter of one percent of the net market price of the soybeans assessed. Producers receiving a refund from a State entity are required to remit that refunded portion to the Board in the manner and form required by the Secretary.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1220">
                    <AMDPAR>3. In § 1220.228, add paragraph (e) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1220.228 </SECTNO>
                        <SUBJECT>Qualified State Soybean Boards.</SUBJECT>
                        <STARS/>
                        <P>(e) Entities authorized or required to pay refunds to producers must certify to the Board that any requests from producers for such refunds for contributions to it by the producer will be honored by forwarding to the Board that portion of such refunds equal to the amount of credit received by the producer for contributions pursuant to § 1220.223(a)(3). Entities not authorized by State statute but organized and operating within a State and certified by the Board pursuant to paragraph (a)(2) of this section must provide producers an opportunity for a State refund and must forward that refunded portion to the Board.</P>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 1260—BEEF PROMOTION AND RESEARCH</HD>
                </PART>
                <REGTEXT TITLE="7" PART="1260">
                    <AMDPAR>4. The authority citation for part 1260 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>7 U.S.C. 2901-2911 and 7 U.S.C. 7401.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1260">
                    <AMDPAR>5. In § 1260.172, add paragraph (a)(7) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1260.172 </SECTNO>
                        <SUBJECT>Assessments.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(7) A producer may request a redirection of assessments from a Qualified State Beef Council to the Board in accordance with § 1260.181(b)(8) or (9) by submitting a redirection request on the appropriate form postmarked by the 15th day of the month following the month in which the cattle were sold. Requests may not be retroactive. Requests to redirect assessments must be submitted by the producers who paid the assessments.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1260">
                    <AMDPAR>6. In § 1260.181, revise the section heading and paragraph (b)(4) and add paragraphs (b)(8) and (9) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1260.181 </SECTNO>
                        <SUBJECT>Qualified State Beef Councils.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(4) Certify to the Board that such organization shall remit to the Board assessments paid and remitted to the council, minus authorized credits issued to producers pursuant to § 1260.172(a)(3), by the 15th day of the month following the month in which the assessment was remitted to the Qualified State Beef Council unless the Board determines a different date for remittance of assessments.</P>
                        <STARS/>
                        <P>(8) Certify to the Board, if the Council is authorized or permitted to pay refunds of contributions to the Council, that any requests from producers for such refunds by the producers will be honored by redirecting to the Board that portion of such refunds equal to the amount of credit received by the producer for contributions pursuant to § 1260.172(a)(3).</P>
                        <P>(9) Certify to the Board that, if the Council is in a State in which State law does not require collection of the $1-per-head assessment set forth in the Act (the federal assessment) by the Council, or if the Council is in a State in which State statutes do not require producers to contribute a portion of the $1-per-head federal assessment to the Council, the Council will provide an opportunity for producers to choose to direct the full $1-per-head federal assessment to the Board. </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1260">
                    <AMDPAR>7. In § 1260.312, revise paragraph (c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1260.312 </SECTNO>
                        <SUBJECT>Remittance to the Cattlemen's Board or Qualified State Beef Council.</SUBJECT>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Remittances.</E>
                             The remitting person shall remit all assessments to the Qualified State Beef Council or its designee, or, if there is no Qualified State Beef Council, to the Cattlemen's Board at an address designated by the Board, with the report required in paragraph (a) of this section not later than the 15th day of the month following the month in which the cattle were purchased or marketed. All remittances sent to a Qualified State Beef Council or the Cattlemen's Board by the remitting persons shall be by check or money order payable to the order of the Qualified State Beef Council or the Cattlemen's Board. All remittances shall be received subject to collection and payment at par.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1260">
                    <AMDPAR>8. Revise § 1260.315 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1260.315 </SECTNO>
                        <SUBJECT>Qualified State Beef Councils.</SUBJECT>
                        <P>The following State beef promotion entities have been certified by the Board as Qualified State Beef Councils:</P>
                        <P>(a) Alabama Cattlemen's Association.</P>
                        <P>(b) Arizona Beef Council.</P>
                        <P>(c) Arkansas Beef Council.</P>
                        <P>(d) California Beef Council.</P>
                        <P>(e) Colorado Beef Council Authority.</P>
                        <P>(f) Delaware Beef Advisory Board.</P>
                        <P>(g) Florida Beef Council, Inc.</P>
                        <P>(h) Georgia Beef Board, Inc.</P>
                        <P>(i) Hawaii Beef Industry Council.</P>
                        <P>(j) Idaho Beef Council.</P>
                        <P>(k) Illinois Beef Association, Inc.</P>
                        <P>(l) Indiana Beef Council, Inc.</P>
                        <P>(m) Iowa Beef Cattle Producers Association/dba/Iowa Beef Industry Council.</P>
                        <P>(n) Kansas Beef Council.</P>
                        <P>(o) Kentucky Cattlemen's Association, Inc.</P>
                        <P>(p) Louisiana Beef Industry Council.</P>
                        <P>(q) Maryland Beef Council.</P>
                        <P>(r) Michigan Beef Industry Commission.</P>
                        <P>(s) Minnesota Beef Council.</P>
                        <P>(t) Mississippi Beef Council.</P>
                        <P>(u) Missouri Beef Industry Council, Inc.</P>
                        <P>(v) Montana Beef Council.</P>
                        <P>(w) Nebraska Beef Council.</P>
                        <P>(x) Nevada Beef Council.</P>
                        <P>(y) New Jersey Beef Industry Council.</P>
                        <P>(z) New Mexico Beef Council.</P>
                        <P>(aa) New York Beef Industry Council.</P>
                        <P>(bb) North Carolina Cattlemen's Beef Council.</P>
                        <P>(cc) North Dakota Beef Commission.</P>
                        <P>(dd) Ohio Beef Council.</P>
                        <P>(ee) Oklahoma Beef Council.</P>
                        <P>(ff) Oregon Beef Council.</P>
                        <P>(gg) Pennsylvania Beef Council.</P>
                        <P>(hh) South Carolina Beef Council.</P>
                        <P>(ii) South Dakota Beef Industry Council.</P>
                        <P>(jj) Tennessee Beef Industry Council.</P>
                        <P>(kk) Texas Beef Council.</P>
                        <P>(ll) Utah Beef Council.</P>
                        <P>(mm) Vermont Beef Industry Council.</P>
                        <P>(nn) Virginia Beef Industry Council.</P>
                        <P>(oo) Washington State Beef Commission.</P>
                        <P>(pp) West Virginia Beef Council, Inc.</P>
                        <P>(qq) Wisconsin Beef Council, Inc.</P>
                        <P>(rr) Wyoming Beef Council.</P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Bruce Summers,</NAME>
                    <TITLE>Administrator, Agricultural Marketing Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09700 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3410-02-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <PRTPAGE P="20772"/>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2018-0901; Product Identifier 2018-NM-114-AD; Amendment 39-19624; AD 2019-08-03]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; The Boeing Company Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We are adopting a new airworthiness directive (AD) for certain The Boeing Company Model 737-100, -200, -200C, -300, -400, and -500 series airplanes. This AD was prompted by reports that frame web and frame integral inboard chord cracking is occurring on multiple airplanes in multiple locations below the passenger floor. This AD requires repetitive detailed, general visual, and high frequency eddy current (HFEC) inspections of the section 43 lower lobe frames at certain stations; an inspection to determine if certain repairs are installed; and applicable on-condition actions. We are issuing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD is effective June 17, 2019.</P>
                    <P>The Director of the Federal Register approved the incorporation by reference of a certain publication listed in this AD as of June 17, 2019.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        For service information identified in this final rule, contact Boeing Commercial Airplanes, Attention: Contractual &amp; Data Services (C&amp;DS), 2600 Westminster Blvd., MC 110-SK57, Seal Beach, CA 90740-5600; telephone 562-797-1717; internet 
                        <E T="03">https://www.myboeingfleet.com.</E>
                         You may view this service information at the FAA, Transport Standards Branch, 2200 South 216th St., Des Moines, WA. For information on the availability of this material at the FAA, call 206-231-3195. It is also available on the internet at 
                        <E T="03">http://www.regulations.gov</E>
                         by searching for and locating Docket No. FAA-2018-0901.
                    </P>
                </ADD>
                <HD SOURCE="HD1">Examining the AD Docket</HD>
                <P>
                    You may examine the AD docket on the internet at 
                    <E T="03">http://www.regulations.gov</E>
                     by searching for and locating Docket No. FAA-2018-0901; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this final rule, the regulatory evaluation, any comments received, and other information. The address for Docket Operations (phone: 800-647-5527) is U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        George Garrido, Aerospace Engineer, Airframe Section, FAA, Los Angeles ACO Branch, 3960 Paramount Boulevard, Lakewood, CA 90712-4137; phone: 562-627-5232; fax: 562-627-5210; email: 
                        <E T="03">george.garrido@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Discussion</HD>
                <P>
                    We issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 by adding an AD that would apply to certain The Boeing Company Model 737-100, -200, -200C, -300, -400, and -500 series airplanes. The NPRM published in the 
                    <E T="04">Federal Register</E>
                     on October 16, 2018 (83 FR 52171). The NPRM was prompted by reports that frame web and frame integral inboard chord cracking is occurring on multiple airplanes in multiple locations below the passenger floor. The NPRM proposed to require repetitive detailed, general visual, and HFEC inspections of the section 43 lower lobe frames from station (STA) 380 to STA 520; an inspection to determine if certain repairs are installed; and applicable on-condition actions.
                </P>
                <P>We are issuing this AD to address frame cracking, which could result in the failure of multiple frames or the combination of a severed frame and cracks in fuselage chem-milled pockets in this area, which could lead to uncontrolled decompression of the airplane.</P>
                <HD SOURCE="HD1">Comments</HD>
                <P>We gave the public the opportunity to participate in developing this final rule. The following presents the comments received on the NPRM and the FAA's response to each comment.</P>
                <HD SOURCE="HD1">Effect of Winglets on Accomplishment of the Proposed Actions</HD>
                <P>Aviation Partners Boeing stated that accomplishing the Supplemental Type Certificate (STC) ST01219SE does not affect the actions specified in the NPRM.</P>
                <P>We concur with the commenter. We have redesignated paragraph (c) of the proposed AD as paragraph (c)(1) of this AD and added paragraph (c)(2) to this AD to state that installation of STC ST01219SE does not affect the ability to accomplish the actions required by this AD. Therefore, for airplanes on which STC ST01219SE is installed, a “change in product” alternative method of compliance (AMOC) approval request is not necessary to comply with the requirements of 14 CFR 39.17.</P>
                <HD SOURCE="HD1">Request for Clarification About Frame Replacement</HD>
                <P>Commenter Mark Bowen observed that if a crack or “non SRM/Boeing repair” is found as part of inspections accomplished under Boeing Alert Service Bulletin 737-53A1361, the only action given in the proposed AD is to contact Boeing for repair or alternative inspections. He asked whether frame replacement could be considered an alternative option to contacting Boeing for a repair or alternative inspections.</P>
                <P>We partially agree with the commenter's request. Frame replacement that removes the cracked or repaired structure may be an option to repair or alternative inspections, provided the replacement can be shown to adequately address the unsafe condition. However, we note that the commenter did not provide sufficient documentation to show that, in regard to the unsafe condition identified in this AD, a frame replacement would adequately address the unsafe condition. In addition, the commenter did not provide details on a proposed method of compliance for accomplishing the proposed frame replacement or post-replacement inspections, nor any evidence of support for the proposal from the Boeing Commercial Airplanes Organization Designation Authorization (ODA). Operators may apply for an alternative method of compliance in accordance with paragraph (i) of this AD, provided they can show that frame replacement adequately addresses the unsafe condition. We have not changed this AD in this regard.</P>
                <HD SOURCE="HD1">Request To Change Exception Language</HD>
                <P>
                    Boeing requested that we change paragraph (i)(4) of the proposed AD to refer to paragraph (h) of the proposed AD instead of (h)(2). We contacted Boeing to clarify the intent of their comment and they stated that they wanted to allow using the phrase “the original issue date of this service bulletin” (rather than “the effective date of this AD”) for determining compliance with this AD only when used in flag notes and notes. Boeing clarified that Boeing Alert Service Bulletin 737-53A1361, dated July 17, 2018, uses the phrase “the original issue date of this service bulletin” in several notes and 
                    <PRTPAGE P="20773"/>
                    flag notes. Boeing added that those notes, which are required for compliance (“RC”), specify conditions under which certain airplanes do not have to do certain actions following approved repairs. Boeing noted that if those notes are not excepted in paragraph (h)(1) of this AD, then operators would have to request an AMOC if the applicable repairs were approved after the original issue date of the service bulletin and before the effective date of this AD.
                </P>
                <P>We agree with the commenter's request to allow using the phrase “the original issue date of this service bulletin” for determining compliance with this AD only when used in flag notes and notes. We have revised paragraph (h)(1) of this AD to provide an exception to the phrase “the original issue date of this service bulletin,” in a note or flag note. We have determined it is not necessary to change paragraph (i)(4) of this AD in this regard.</P>
                <HD SOURCE="HD1">Request To Correct Wording for Consistency</HD>
                <P>Boeing requested that we change paragraph (g)(1) of the proposed AD to refer to “applicable on-condition actions” instead of “applicable corrective actions.” The commenter suggested that “on-condition actions” would be consistent with current standards.</P>
                <P>We agree because this language would be consistent with the preamble of this AD, as well as current terminology standards. We have made the requested change in paragraph (g)(1) of this AD.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>We reviewed the relevant data, considered the comments received, and determined that air safety and the public interest require adopting this final rule with the changes described previously and minor editorial changes. We have determined that these minor changes:</P>
                <P>• Are consistent with the intent that was proposed in the NPRM for addressing the unsafe condition; and</P>
                <P>• Do not add any additional burden upon the public than was already proposed in the NPRM.</P>
                <P>We also determined that these changes will not increase the economic burden on any operator or increase the scope of this final rule.</P>
                <HD SOURCE="HD1">Related Service Information Under 1 CFR Part 51</HD>
                <P>
                    We reviewed Boeing Alert Service Bulletin 737-53A1361, dated July 17, 2018. This service information describes procedures for repetitive detailed, general visual, and HFEC inspections of the section 43 lower lobe frames from STA 380 to STA 520; a general visual inspection to determine if certain repairs are installed; and applicable on-condition actions. 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 the 
                    <E T="02">ADDRESSES</E>
                     section.
                </P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>We estimate that this AD affects 262 airplanes of U.S. registry. We estimate the following costs to comply with this AD:</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s25,r50,12,r50,r50">
                    <TTITLE>Estimated Costs for Required Actions</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">Inspections</ENT>
                        <ENT>Up to 84 work-hours × $85 per hour = $7,140 per inspection cycle</ENT>
                        <ENT>$0</ENT>
                        <ENT>Up to $7,140 per inspection cycle</ENT>
                        <ENT>Up to $1,870,680 per inspection cycle.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>We have received no definitive data that would enable us to provide cost estimates for the on-condition actions specified in this AD.</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>We are 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>
                <P>This AD is issued in accordance with authority delegated by the Executive Director, Aircraft Certification Service, as authorized by FAA Order 8000.51C. In accordance with that order, issuance of ADs is normally a function of the Compliance and Airworthiness Division, but during this transition period, the Executive Director has delegated the authority to issue ADs applicable to transport category airplanes and associated appliances to the Director of the System Oversight Division.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>This AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify that this AD:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),</P>
                <P>(3) Will not affect intrastate aviation in Alaska, and</P>
                <P>(4) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Adoption of the Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:</P>
                <PART>
                    <PRTPAGE P="20774"/>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </PART>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 39.13</SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>2. The FAA amends § 39.13 by adding the following new airworthiness directive (AD):</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2019-08-03 The Boeing Company:</E>
                             Amendment 39-19624; Docket No. FAA-2018-0901; Product Identifier 2018-NM-114-AD.
                        </FP>
                        <HD SOURCE="HD1">(a) Effective Date</HD>
                        <P>This AD is effective June 17, 2019.</P>
                        <HD SOURCE="HD1">(b) Affected ADs</HD>
                        <P>None.</P>
                        <HD SOURCE="HD1">(c) Applicability</HD>
                        <P>(1) This AD applies to The Boeing Company Model 737-100, -200, -200C, -300, -400, and -500 series airplanes, certificated in any category, as identified in Boeing Alert Service Bulletin 737-53A1361, dated July 17, 2018.</P>
                        <P>(2) Installation of Supplemental Type Certificate (STC) ST01219SE does not affect the ability to accomplish the actions required by this AD. Therefore, for airplanes on which STC ST01219SE is installed, a “change in product” alternative method of compliance (AMOC) approval request is not necessary to comply with the requirements of 14 CFR 39.17.</P>
                        <HD SOURCE="HD1">(d) Subject</HD>
                        <P>Air Transport Association (ATA) of America Code 53, Fuselage.</P>
                        <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                        <P>This AD was prompted by reports that frame web and frame integral inboard chord cracking is occurring on multiple airplanes in multiple locations below the passenger floor. We are issuing this AD to address frame cracking, which could result in the failure of multiple frames or the combination of a severed frame and cracks in fuselage chem-milled pockets in this area, which could lead to uncontrolled decompression of the airplane.</P>
                        <HD SOURCE="HD1">(f) Compliance</HD>
                        <P>Comply with this AD within the compliance times specified, unless already done.</P>
                        <HD SOURCE="HD1">(g) Required Actions</HD>
                        <P>(1) For airplanes identified as Group 1 in Boeing Alert Service Bulletin 737-53A1361, dated July 17, 2018: Within 120 days after the effective date of this AD, inspect the airplane and do all applicable on-condition actions using a method approved in accordance with the procedures specified in paragraph (i) of this AD.</P>
                        <P>(2) For airplanes identified as Groups 2 through 6 in Boeing Alert Service Bulletin 737-53A1361, dated July 17, 2018: Except as required by paragraph (h) of this AD, at the applicable times specified in paragraph 1.E., “Compliance,” of Boeing Alert Service Bulletin 737-53A1361, dated July 17, 2018, do all applicable actions identified as “RC” (required for compliance) in, and in accordance with, the Accomplishment Instructions of Boeing Alert Service Bulletin 737-53A1361, dated July 17, 2018.</P>
                        <HD SOURCE="HD1">(h) Exceptions to Service Information Specifications</HD>
                        <P>(1) For purposes of determining compliance with the requirements of this AD: Where Boeing Alert Service Bulletin 737-53A1361, dated July 17, 2018, uses the phrase “the original issue date of this service bulletin,” this AD requires using “the effective date of this AD,” except where Boeing Alert Service Bulletin 737-53A1361, dated July 17, 2018, uses the phrase “the original issue date of this service bulletin” in a note or flag note.</P>
                        <P>(2) Where Boeing Alert Service Bulletin 737-53A1361, dated July 17, 2018, specifies contacting Boeing for repair instructions or contacting Boeing for alternative inspections: This AD requires doing the repair, or the alternative inspections and applicable on-condition actions, using a method approved in accordance with the procedures specified in paragraph (i) of this AD.</P>
                        <HD SOURCE="HD1">(i) Alternative Methods of Compliance (AMOCs)</HD>
                        <P>
                            (1) The Manager, Los Angeles ACO 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 certification office, send it to the attention of the person identified in paragraph (j) of this AD. Information may be emailed to: 
                            <E T="03">9-ANM-LAACO-AMOC-Requests@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>
                        <P>(3) An AMOC that provides an acceptable level of safety may be used for any repair, modification, or alteration required by this AD if it is approved by the Boeing Commercial Airplanes Organization Designation Authorization (ODA) that has been authorized by the Manager, Los Angeles ACO Branch, FAA, to make those findings. To be approved, the repair method, modification deviation, or alteration deviation must meet the certification basis of the airplane, and the approval must specifically refer to this AD.</P>
                        <P>(4) Except as required by paragraph (h)(2) of this AD: For service information that contains steps that are labeled as RC, the provisions of paragraphs (i)(4)(i) and (i)(4)(ii) of this AD apply.</P>
                        <P>(i) The steps labeled as RC, including substeps under an RC step and any figures identified in an RC step, must be done to comply with the AD. If a step or substep is labeled “RC Exempt,” then the RC requirement is removed from that step or substep. An AMOC is required for any deviations to RC steps, including substeps and identified figures.</P>
                        <P>(ii) Steps not labeled as RC may be deviated from using accepted methods in accordance with the operator's maintenance or inspection program without obtaining approval of an AMOC, provided the RC steps, including substeps and identified figures, can still be done as specified, and the airplane can be put back in an airworthy condition.</P>
                        <HD SOURCE="HD1">(j) Related Information</HD>
                        <P>
                            For more information about this AD, contact George Garrido, Aerospace Engineer, Airframe Section, FAA, Los Angeles ACO Branch, 3960 Paramount Boulevard, Lakewood, CA 90712-4137; phone: 562-627-5232; fax: 562-627-5210; email: 
                            <E T="03">george.garrido@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) Boeing Alert Service Bulletin 737-53A1361, dated July 17, 2018.</P>
                        <P>(ii) [Reserved]</P>
                        <P>
                            (3) For service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Contractual &amp; Data Services (C&amp;DS), 2600 Westminster Blvd., MC 110-SK57, Seal Beach, CA 90740-5600; telephone 562-797-1717; internet 
                            <E T="03">https://www.myboeingfleet.com.</E>
                        </P>
                        <P>(4) You may view this service information at the FAA, Transport Standards 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 service information that is incorporated by reference at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to: 
                            <E T="03">http://www.archives.gov/federal-register/cfr/ibr-locations.html.</E>
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Des Moines, Washington, on May 1, 2019.</DATED>
                    <NAME>Michael Kaszycki,</NAME>
                    <TITLE>Acting Director, System Oversight Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09747 Filed 5-10-19; 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-2019-0041; Airspace Docket No. 19-AGL-6]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of Class E Airspace; Mount Vernon, IL</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <PRTPAGE P="20775"/>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action modifies the Class E surface area and Class E airspace extending upward from 700 feet above the surface at Mount Vernon Airport, Mount Vernon, IL. This action is due to an airspace review caused by the decommissioning of the Mount Vernon VHF omnidirectional range (VOR), which provided navigation information to the instrument procedures at this airport, as part of the VOR Minimum Operational Network (MON) Program. The geographic coordinates and name of the airport are also being updated to coincide with the FAA's aeronautical database. Airspace redesign is necessary for the safety and management of instrument flight rules (IFR) operations at this airport.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective 0901 UTC, August 15, 2019. The Director of the Federal Register approves this incorporation by reference action under Title 1 Code of Federal Regulations part 51, subject to the annual revision of FAA Order 7400.11 and publication of conforming amendments.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        FAA Order 7400.11C, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">http://www.faa.gov/air_traffic/publications/.</E>
                         For further information, you can contact the Airspace Policy Group, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591; telephone: (202) 267-8783. The Order is also available for inspection at the National Archives and Records Administration (NARA). For information on the availability of FAA Order 7400.11C at NARA, call (202) 741-6030, or go to 
                        <E T="03">https://www.archives.gov/federal-register/cfr/ibr-locations.html.</E>
                    </P>
                    <P>FAA Order 7400.11, Airspace Designations and Reporting Points, is published yearly and effective on September 15.</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 surface area and Class E airspace extending upward from 700 feet above the surface at Mount Vernon Airport, Mount Vernon, IL, to support IFR operations at this airport.</P>
                <HD SOURCE="HD1">History</HD>
                <P>
                    The FAA published a notice of proposed rulemaking in the 
                    <E T="04">Federal Register</E>
                     (84 FR 6708; February 28, 2019) for Docket No. FAA-2019-0041 to amend the Class E surface area and Class E airspace extending upward from 700 feet above the surface at Mount Vernon Airport, Mount Vernon, IL. Interested parties were invited to participate in this rulemaking effort by submitting written comments on the proposal to the FAA. One comment was received supporting this action. No response is provided.
                </P>
                <P>Class E airspace designations are published in paragraph 6002 and 6005 of FAA Order 7400.11C, dated August 13, 2018, and effective September 15, 2018, which is incorporated by reference in 14 CFR 71.1. The Class E airspace designations listed in this document will be published subsequently in the Order.</P>
                <HD SOURCE="HD1">Availability and Summary of Documents for Incorporation by Reference</HD>
                <P>
                    This document amends FAA Order 7400.11C, Airspace Designations and Reporting Points, dated August 13, 2018, and effective September 15, 2018. FAA Order 7400.11C is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. FAA Order 7400.11C 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 Title 14 Code of Federal Regulations (14 CFR) part 71 by:</P>
                <P>Modifying the Class E surface area to within a 4.1-mile radius (reduced from a 4.2-mile radius) at Mount Vernon Airport, Mount Vernon, IL, and removing the Mount Vernon VOR/DME and the associate extension from the airspace legal description;</P>
                <P>And modifying the Class E airspace extending upward from 700 feet above the surface at Mount Vernon Airport, Mount Vernon, IL, by removing the Mount Vernon VOR/DME and the associated extension from the airspace legal description; and by updating the name of the airport (formerly Mount Vernon/Outland Airport) and the geographic coordinates of the airport to coincide with the FAA's aeronautical database.</P>
                <P>This action is due to an airspace review caused by the decommissioning of the Mount Vernon VOR, which provided navigation information for the instrument procedures at these airports, as part of the VOR MON Program.</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, is non-controversial and unlikely to result in adverse or negative comments. 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 Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air). </P>
                </LSTSUB>
                <HD SOURCE="HD1">Adoption of 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 part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <PRTPAGE P="20776"/>
                        <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 7400.11C, Airspace Designations and Reporting Points, dated August 13, 2018, and effective September 15, 2018, is amended as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 6002 Class E Airspace Areas Designated as Surface Areas.</HD>
                        <STARS/>
                        <HD SOURCE="HD1">AGL IL E2 Mount Vernon, IL [Amended]</HD>
                        <FP SOURCE="FP-2">Mount Vernon Airport, IL</FP>
                        <FP SOURCE="FP1-2">(Lat. 38°19′24″ N, long. 88°51′31″ W)</FP>
                        <P>Within a 4.1-mile radius of Mount Vernon Airport.</P>
                        <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 IL E5 Mount Vernon, IL [Amended]</HD>
                        <FP SOURCE="FP-2">Mount Vernon Airport, IL</FP>
                        <FP SOURCE="FP1-2">(Lat. 38°19′24″ N, long. 88°51′31″ W)</FP>
                        <P>That airspace extending upward from 700 feet above the surface within a 6.6-mile radius of Mount Vernon Airport.</P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Fort Worth, Texas, on May 6, 2019.</DATED>
                    <NAME>John A. Witucki,</NAME>
                    <TITLE>Acting Manager, Operations Support Group, ATO Central Service Center.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09701 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL TRADE COMMISSION</AGENCY>
                <CFR>16 CFR Part 18</CFR>
                <SUBJECT>Guides for the Nursery Industry</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Rescission of the Guides for the Nursery Industry.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Trade Commission (“FTC” or “Commission”) has completed its review of the Guides for the Nursery Industry (“Nursery Guides” or “Guides”) as part of its systematic review of all current Commission regulations and guides. Pursuant to that review, the Commission now rescinds the Guides.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The rescission is effective June 12, 2019.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Copies of this document are available on the Commission's website, 
                        <E T="03">www.ftc.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Hampton Newsome, (202) 326-2889, Attorney, Division of Enforcement, Bureau of Consumer Protection, Federal Trade Commission, 600 Pennsylvania Avenue NW, Washington, DC 20580.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    The Commission issued the Guides for the Nursery Industry in 1979.
                    <SU>1</SU>
                    <FTREF/>
                     These Guides address various sales claims for outdoor plants, including representations regarding quantity, size, grade, kind, species, age, maturity, condition, vigor, hardiness, growth ability, price, and origin or place where grown. The Commission amended the Guides in 1994 to update legal terminology, and again in 2007 to make a technical correction.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The Commission issued the Guides in 1979 (44 FR 11176 (Feb. 27, 1979)) to replace trade practice rules for the nursery industry (16 CFR part 34) first promulgated in the 1950s (23 FR 4803 (June 28, 1958)). The Guides were intended to help marketers avoid making claims that are unfair or deceptive under Section 5 of the FTC Act, 15 U.S.C. 45. Industry guides, such as the Nursery Guides, are administrative interpretations of laws administered by the Commission. They do not have the force of law and are not independently enforceable. Failure to follow industry guides may result, however, in enforcement action under the FTC Act, 15 U.S.C. 45. In any such action, the Commission must prove that the act or practice at issue is unfair or deceptive in violation of Section 5 of the FTC Act.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         59 FR 64546 (Dec. 14, 1994); 72 FR 901 (Jan. 9, 2007).
                    </P>
                </FTNT>
                <P>The Commission reviews its rules and guides periodically to seek information about their costs and benefits to consumers and businesses, regulatory and economic impact, and general effectiveness in protecting consumers and helping industry avoid deceptive claims. These reviews assist the Commission in identifying rules and guides that warrant modification or rescission.</P>
                <P>
                    On February 22, 2018, the Commission initiated its scheduled regulatory review of the Nursery Guides and solicited public comment on several issues.
                    <SU>3</SU>
                    <FTREF/>
                     Specifically, the Commission sought input on the continuing need for the Guides; their economic impact; possible conflict between the Guides and state, local, federal, or international laws; and the effect of any technological, economic, environmental, or other industry changes. The Commission also solicited comment on issues specific to the Guides, such as whether the Commission should update plant classification references. In response, the Commission received one comment from the National Federation of Independent Business (“NFIB”). NFIB argued the Commission should rescind the Guides because they are an unnecessary federal regulatory burden. NFIB also contended that regulation or guidance concerning the nursery business is more properly conducted at the state, rather than federal, level.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         83 FR 7643 (Feb. 22, 2018).
                    </P>
                </FTNT>
                <P>Based on the lack of comments, as well as the paucity of consumer complaints and the lack of need for law enforcement action over the past two decades, on September 10, 2018 (83 FR 45582), the Commission published a Notice of Proposed Rulemaking (“NPRM”) seeking comments on a proposed rescission of the Guides. The Commission stated that the Guides no longer appear necessary, and thus serve little purpose to industry or consumers. Specifically, the types of practices detailed in the Guides do not appear to be prevalent in the nursery industry; little evidence exists that industry members currently use the Guides to help avoid deceptive practices; and rescission will have no impact on the FTC's ability to address unfair and deceptive practices in the nursery industry.</P>
                <HD SOURCE="HD1">II. Comments Received</HD>
                <P>
                    In response to the proposed rescission notice, the Commission received five comments, offering conflicting opinions.
                    <SU>4</SU>
                    <FTREF/>
                     The National Federation of Independent Business (“NFIB”), which had commented on the initial Notice, supported the proposed rescission, commenting that “federal agencies should refrain from imposing unwarranted burdens on the American people and revoke unnecessary regulation.” AmericanHort, an industry association representing nursery growers, greenhouses, and other garden retailers, supported retaining the Guides but also noted that “the overall need for the Guides has perhaps diminished somewhat based on the general evolution of consumer protection mechanisms in our society.”
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The comments, which can be found at 
                        <E T="03">https://www.ftc.gov/policy/public-comments/2018/09/initiative-770,</E>
                         included AmericanHort (#00007), NFIB (Nat'l Fed'n of Independent Business) (#00005), Lerner (#00004), Smith (#00003), and Harrod (#00002).
                    </P>
                </FTNT>
                <P>
                    Three individual commenters opposed rescinding the Guides. Commenter Harrod argued that, “due to the dishonest nature of some people,” the Guides will always be needed. The commenter also asserted that rescission would imply that it is “now okay to deceive people to make money.” Similarly, commenter Lerner explained that the “average nursery consumer lacks the expertise to identify species of plants” and suggested the lack of complaints may be due to the Guides' effectiveness.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Commenter Smith also opposed rescission without elaboration.
                    </P>
                </FTNT>
                <PRTPAGE P="20777"/>
                <P>
                    Although AmericanHort downplayed the Guides' overall necessity, it singled out the wild plant guidance (16 CFR 18.6) as particularly important. That section indicates that marketers should not sell plants collected from the wild without disclosing that fact.
                    <SU>6</SU>
                    <FTREF/>
                     The provision further advises that nurseries may identify plants “propagated” from lawfully-collected wild plants as “nursery-propagated.” AmericanHort explained that, while this guidance involves a relatively narrow issue, it is a “critical element of industry guidance” developed following negotiations between industry and conservation groups in the early 1990s. AmericanHort expressed concern this guidance would be lost if the Commission discontinues the Guides.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Section 18.6 (“Plants collected from the wild state”) reads: “It is an unfair or deceptive act or practice to sell, offer for sale, or distribute industry products collected from the wild state without disclosing that they were collected from the wild state; 
                        <E T="03">provided, however,</E>
                         that plants propagated in nurseries from plants lawfully collected from the wild state may be designated as `nursery-propagated.' ”
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Harrod, who supported retention, added that wild plants “rarely prosper for a prolonged period of time.”
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Rescission of the Guides</HD>
                <P>The Commission has decided to rescind the Guides because they no longer appear necessary. In reaching this conclusion, the Commission has considered the comments received, the prevalence of practices covered by the Guides, the industry's use of the Guides, and the Commission's ability to address deceptive practices through enforcement actions or issuance of other educational materials in the Guides' absence. As discussed below, FTC staff can provide guidance and business education regarding the advertising of wild plants.</P>
                <P>
                    The record indicates that the types of practices addressed in the Guides are not prevalent in the nursery industry. The Guides focus on misrepresentations about species, size, rate of growth, and other plant characteristics. Neither the comments nor consumer complaints provide evidence that these types of deceptive practices are prevalent. Indeed, as discussed in the NPRM, nearly all recent complaints received by the Commission regarding plant sales involve online plant orders that were either dormant or dead upon arrival, incomplete, not delivered in the time promised (or at all), or not refunded upon request.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The Guides address some of the practices identified in the complaints indirectly or in limited ways. For instance, § 18.1(c)(2) states it is deceptive to represent “[t]hat industry products are healthy . . . when such is not the fact.” In addition, some complaints involve incorrect orders, which are covered by § 18.1(a). The Commission sees no need to maintain the Guides to address these limited issues and has found no basis to amend the Guides to address other Section 5 violations, such as the failure to deliver products.
                    </P>
                </FTNT>
                <P>Furthermore, with the exception of guidance on wild plants, the Commission lacks clear evidence that industry members currently use the Guides to help avoid deceptive practices. AmericanHort acknowledged that the need for the Guides has “perhaps diminished” over the years. As noted in the NPRM, FTC staff found no mention of the Guides on websites for industry associations, nurseries, or other industry entities.</P>
                <P>
                    The Guides do not appear to add substantially to general FTC guidance on deceptive practices under the FTC Act.
                    <SU>9</SU>
                    <FTREF/>
                     The current provisions focus on misrepresentations about plant characteristics and generally address claims that are clearly deceptive on their face, and thus unambiguously addressed by Section 5 of the FTC Act. In contrast, most of the agency's Guides address difficult implied claims, thus providing valuable information to help businesses avoid deception and substantiate claims that might otherwise lead to consumer confusion (
                    <E T="03">e.g.,</E>
                     the Green Guides in 16 CFR part 260). Given AmericanHort and Harrod's comments about the usefulness of the Guides' wild plant section, the FTC staff will continue to provide business guidance on this topic through its online Business Center, which contains plain-language advice to help businesses understand their responsibilities and comply with the FTC Act.
                    <SU>10</SU>
                    <FTREF/>
                     This will ensure the wild plant guidance remains available to industry while also giving the FTC flexibility to update such guidance as needed.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Section 5 of the FTC Act, 15 U.S.C. 45(a)(1), prohibits unfair or deceptive acts or practices in or affecting commerce. See FTC Policy Statement on Deception, appended to 
                        <E T="03">Cliffdale Assocs., Inc.,</E>
                         103 F.T.C. 110, 175 (1984) (“Deception Policy Statement”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         See 
                        <E T="03">https://www.ftc.gov/tips-advice/business-center/guidance.</E>
                    </P>
                </FTNT>
                <P>
                    Finally, contrary to a few commenter suggestions, the Guides' rescission will not impact sellers' obligations to avoid deceptive practices and otherwise comply with the law, nor will it impact the FTC's ability to address deceptive practices in the nursery industry. The Guides themselves are not rules. Instead, they contain interpretations of how the Commission would apply the FTC Act to nursery practices. Therefore, their rescission has no effect on existing obligations. Moreover, rescission does not signal an FTC withdrawal from efforts to prevent deception in the labeling and advertising of these products. Industry members must continue to follow the law articulated in pertinent Commission and court decisions, both of which are generally applicable to all industries. Industry should also consult the FTC's Policy Statement on Deception for guidance, which describes how the Commission applies established legal principles to address deceptive trade practices. As stated in the Deception Statement, the Commission “will find deception if there is a representation, omission, or practice that is likely to mislead the consumer acting reasonably in the circumstances, to the consumer's detriment.” 
                    <SU>11</SU>
                    <FTREF/>
                     If the Commission determines that certain practices in the sale of outdoor plants are materially misleading, it can continue to address such practices through enforcement actions under Section 5 of the FTC Act.
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Deception Policy Statement, 103 F.T.C. at 175.
                    </P>
                </FTNT>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 16 CFR Part 18</HD>
                    <P>Advertising, Nursery, Trade practices.</P>
                </LSTSUB>
                <PART>
                    <HD SOURCE="HED">PART 18—[REMOVED]</HD>
                </PART>
                <REGTEXT TITLE="16" PART="18">
                    <AMDPAR>For the reasons stated in the preamble, and under the authority of 15 U.S.C. secs. 5, 6, and 18, the Federal Trade Commission amends 16 CFR by removing part 18.</AMDPAR>
                </REGTEXT>
                <SIG>
                    <P>By direction of the Commission, Commissioners Chopra and Slaughter dissenting.</P>
                    <NAME>Julie A. Mack,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09745 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 6750-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL TRADE COMMISSION</AGENCY>
                <CFR>16 CFR Part 460</CFR>
                <RIN>RIN 3084-AB40</RIN>
                <SUBJECT>Labeling and Advertising of Home Insulation: Trade Regulation Rule</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Federal Trade Commission (“Commission”) amends its Trade Regulation Rule Concerning the Labeling and Advertising of Home Insulation (“R-value Rule” or “Rule”) to clarify, streamline, and improve existing requirements. Specifically, the amendments clarify the Rule's coverage, improve Fact Sheet disclosures, require certain test methods to substantiate R-value claims for non-insulation products, update the test procedures 
                        <PRTPAGE P="20778"/>
                        incorporated into the Rule, and exempt certain disclosures for limited format advertising.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The amendments will become effective on May 13, 2020. The incorporation by reference of certain publications listed in the rule is approved by the Director of the Federal Register as of May 13, 2020.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Copies of this document are available on the Commission's website, 
                        <E T="03">www.ftc.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Hampton Newsome, Attorney (202-326-2889), Division of Enforcement, Bureau of Consumer Protection, Federal Trade Commission, 600 Pennsylvania Avenue NW, Washington, DC 20580.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    The Commission promulgated the R-value Rule in 1979 to address the failure of the home insulation marketplace to provide essential pre-purchase information to consumers, primarily an insulation product's “R-value.” 
                    <SU>1</SU>
                    <FTREF/>
                     An insulation product's “R-value” represents the product's ability to restrict heat flow and, therefore, reduce energy costs. The higher the R-value, the better the product's insulating ability. R-value ratings vary among types and forms of home insulations and even among products of the same type and form.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The Commission promulgated the R-value Rule pursuant to Section 18 of the Federal Trade Commission Act (“FTC Act”), 15 U.S.C. 57a. The Rule became effective on September 30, 1980. 
                        <E T="03">See</E>
                         44 FR 50218 (Aug. 27, 1979).
                    </P>
                </FTNT>
                <P>
                    For insulation marketed for use in residential structures, the Rule requires R-value disclosures, directs manufacturers to substantiate the claims made in these disclosures, and prohibits certain claims unless they are true and non-misleading. Specifically, the Rule requires insulation sellers to disclose the insulation product's R-value and related information based on uniform, industry-adopted test procedures.
                    <SU>2</SU>
                    <FTREF/>
                     This information enables consumers to evaluate the performance and cost-effectiveness of competing products.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Additional Commission rules or guides may also apply to home insulation sellers. 
                        <E T="03">See, e.g.,</E>
                         16 CFR parts 701 and 702 (warranty-related rules), and 16 CFR part 260 (Guides for the Use of Environmental Marketing Claims). Further, Section 5 declares that unfair or deceptive acts or practices are unlawful, and requires that advertisers and other sellers have a reasonable basis for advertising and other promotional claims before they are disseminated. 
                        <E T="03">See FTC Policy Statement on Deception,</E>
                         103 F.T.C. 174, 175 (1984) (appended to 
                        <E T="03">Cliffdale Assocs., Inc.,</E>
                         103 F.T.C. 110 (1984)) (“
                        <E T="03">Deception Statement</E>
                        ”); 
                        <E T="03">FTC Policy Statement on Unfairness,</E>
                         appended to 
                        <E T="03">International Harvester Co.,</E>
                         104 F.T.C. 949 (1984); and 
                        <E T="03">FTC Policy Statement Regarding Advertising Substantiation,</E>
                         104 F.T.C. 839 (1984) (appended to 
                        <E T="03">Thompson Med. Co.,</E>
                         104 F.T.C. 648 (1984)) (“
                        <E T="03">Substantiation Statement</E>
                        ”).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">A. Products Covered</HD>
                <P>
                    The R-value Rule covers all “home insulation products.” Under the Rule, the term “insulation” includes any product “mainly used to slow down heat flow” from, for example, a heated interior through exterior walls to the outside.
                    <SU>3</SU>
                    <FTREF/>
                     The Rule covers most types of insulation marketed for use in residential structures.
                    <SU>4</SU>
                    <FTREF/>
                     It does not cover insulation marketed solely for use in commercial (including industrial) buildings.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         16 CFR 460.2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The Rule does not cover pipe insulation or any type of duct insulation except for duct wrap. 
                        <E T="03">See</E>
                         44 FR at 50238, n. 170 (the Commission explained that pipe insulation is used primarily to reduce condensation). In addition, while most of the Rule's provisions do not apply to non-insulation products with insulating characteristics, such as storm windows or storm doors, the amendments announced in this Notice add substantiation requirements for R-value claims made for such products.
                    </P>
                </FTNT>
                <P>
                    Home insulation falls into two basic categories: “mass” and “reflective.” Mass insulations reduce heat transfer by conduction (through the insulation's mass), convection (air movement within, and through, the air spaces inside the insulation), and radiation. Reflective insulations (primarily aluminum foils) reduce heat transfer by radiation, when the insulation is installed facing an airspace. Within these basic categories, home insulation is made from various materials (
                    <E T="03">e.g.,</E>
                     fiberglass, cellulose, polyurethane, aluminum foil) and comes in various forms (
                    <E T="03">e.g.,</E>
                     batt, dry-applied loose-fill, spray-applied, board stock, multi-sheet reflective).
                </P>
                <HD SOURCE="HD2">B. Covered Parties</HD>
                <P>The Rule applies to home insulation manufacturers, professional installers, retailers who sell insulation for do-it-yourself installation, and new home sellers, including sellers of manufactured housing (“covered entities”). It also applies to laboratories that conduct R-value tests for those who base their R-value claims on these test results.</P>
                <HD SOURCE="HD2">C. The Rule's Basis</HD>
                <P>
                    The Commission first issued the R-value Rule in response to a variety of unfair or deceptive acts or practices in the insulation industry. Specifically, the Commission found that many sellers: (1) Failed to disclose R-values, impeding informed purchasing decisions and misleading consumers who based their purchases on price or thickness alone; (2) exaggerated R-value disclosures and often failed to account for material factors (
                    <E T="03">e.g.,</E>
                     aging, settling) that reduce thermal performance; (3) failed to inform consumers about an R-value's meaning and importance; (4) exaggerated fuel bill savings and failed to disclose that savings vary depending on consumers' particular circumstances; or (5) falsely claimed that consumers' insulation purchases would qualify for tax credits, or that products had been “certified” or “favored” by federal agencies.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         44 FR at 50222-24.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">D. The Rule's Requirements</HD>
                <P>
                    The Rule requires covered entities to disclose R-value and related information (
                    <E T="03">e.g.,</E>
                     thickness, coverage area per package) on package labels and manufacturers' fact sheets. Covered entities must derive these disclosures from tests conducted according to one of four specified ASTM International (“ASTM”) test procedures that measure thermal performance under “steady-state” (
                    <E T="03">i.e.,</E>
                     static) conditions.
                    <SU>6</SU>
                    <FTREF/>
                     Industry members must conduct tests for mass insulation products on the insulation material alone (excluding any airspace) at a mean temperature of 75 °F. The Rule's R-value tests account for factors that can affect insulation's thermal performance. For example, tests for polyurethane, polyisocyanurate, and extruded polystyrene insulation account for aging, and tests for loose-fill insulation products reflect the effect of settling.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The Rule (§ 450.5) incorporates by reference ASTM test procedures, which ASTM reviews and revises periodically. For mass insulations, the required tests are ASTM C177, C518, C1363, or C1114. The Rule requires testing for reflective insulation products according to ASTM C1363, which generates R-values for insulation systems (such as those that include one or more air spaces). Industry members must test the R-value of a single-sheet reflective insulation product under ASTM E408 or C1371.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         44 FR at 50219-20, 50227-28.
                    </P>
                </FTNT>
                <P>
                    The Rule also requires specific disclosures on manufacturer product labels and fact sheets, installer receipts, and new home seller contracts. For example, insulation labels must display the product's R-value and the statement “R means resistance to heat flow. The higher the R-value, the greater the insulating power.” 
                    <SU>8</SU>
                    <FTREF/>
                     The Rule also requires that certain affirmative disclosures appear in advertising and other promotional materials (including those on the internet) containing an R-value, price, thickness, or energy-saving claim, or comparing one type of insulation to another. For example, if an advertisement contains an R-value, it must disclose the type of insulation 
                    <PRTPAGE P="20779"/>
                    being sold and the thickness needed to obtain that R-value, as well as the statement: “The higher the R-value, the greater the insulating power. Ask your seller for the fact sheet on R-values.” In addition, if an advertisement contains an energy saving claim, it must disclose: “Savings vary. Find out why in the seller's fact sheet on R-values. Higher R-values mean greater insulating power.”
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         16 CFR 460.12(c).
                    </P>
                </FTNT>
                <P>
                    The Rule also requires manufacturers and other sellers to have a “reasonable basis” for any energy-saving claims they make on labels or in advertising.
                    <SU>9</SU>
                    <FTREF/>
                     Although the Rule does not specify how they must substantiate such claims, the Commission explained when issuing the Rule that scientifically reliable measurements of fuel use in actual houses, or reliable computer models or methods of heat flow calculations, would meet the reasonable basis standard.
                    <SU>10</SU>
                    <FTREF/>
                     Sellers other than manufacturers can rely on the manufacturer's claims unless they know, or should know, that the manufacturer lacks a reasonable basis for its claims.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         16 CFR 460.19.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         44 FR at 50233-34.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Regulatory Review</HD>
                <P>
                    The Commission reviews its rules and guides periodically to ascertain their costs and benefits, regulatory and economic impact, and general effectiveness in protecting consumers and helping industry avoid deceptive claims. These reviews assist the Commission in identifying rules and guides warranting modification or rescission. As part of its last review in 2005, the Commission issued several amendments to update and improve the Rule. For example, the Commission added a temperature differential requirement for testing, updated tests for reflective insulation, and required new initial installed thickness disclosures for loose-fill insulation.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         70 FR 31258 (May 31, 2005).
                    </P>
                </FTNT>
                <P>
                    In 2016, the Commission initiated a new regulatory review through the publication of an Advance Notice of Proposed Rulemaking (ANPR).
                    <SU>12</SU>
                    <FTREF/>
                     In the ANPR, the Commission sought comments on, among other things, the economic impact of, and the continuing need for, the Rule; the Rule's benefits to consumers; and the burdens it places on industry, including small businesses, subject to its requirements.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         81 FR 35661 (June 3, 2016).
                    </P>
                </FTNT>
                <P>
                    Following the ANPR, the Commission published a Notice of Proposed Rulemaking (NPRM) on January 22, 2018 (83 FR 2934). In the NPRM, the Commission proposed to: (1) Clarify that the Rule covers products marketed for residential applications, even if those products are originally developed for the commercial market; (2) require marketers to use the Rule's testing requirements to substantiate any R-value claims for non-insulation products marketed in whole or in part to reduce residential energy use by slowing heat flow; (3) add information about air sealing and installation to fact sheets; (4) clarify that online retailers must provide labels and fact sheets; (5) eliminate reference to an obsolete aging specification; (6) revise provisions addressing the incorporation by reference of ASTM test procedures; (7) eliminate a provision that automatically updates ASTM test procedures; and (8) exempt space-constrained advertising from certain affirmative disclosures.
                    <SU>13</SU>
                    <FTREF/>
                     In response to the NPRM, the Commission received 13 comments.
                    <SU>14</SU>
                    <FTREF/>
                     After considering the comments, the Commission now issues final amendments to the Rule, which, as discussed below, largely track the amendments proposed in the NPRM.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         The amendments also make a non-substantive change to § 460.2 (
                        <E T="03">i.e.,</E>
                         changing the term “slow down” to “slow”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         The comments are located at: 
                        <E T="03">https://www.ftc.gov/policy/public-comments/2018/03/initiative-740.</E>
                         Polyisocyanurate Insulation Manufacturers Association (PIMA) (#00009); AFM Corporation (#00010); North American Insulation Manufacturers Association (NAIMA) (#00011); Insulation Contractors Association of America (ICAA) (#00012); Reflective Insulation Manufacturers Association (RIMA) (#00013); American Chemistry Council (ACC) (#00014); Brick Industry Association (#00015); EPS Industry Alliance (EPS-IA) (#00016); Harrison (#00008); Anonymous (#00007); Aresty (#00006); Ji (#00003); and Extruded Polystyrene Foam Association (XPSA) (#00002).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Issues Raised by Commenters</HD>
                <HD SOURCE="HD2">A. Need for and Costs and Benefits of the Rule</HD>
                <P>In the NPRM, the Commission determined to retain the Rule, given its benefits and minimal costs as reported by commenters. Summarizing comments received in response to the ANPR, the Commission explained that the Rule helps consumers and industry members by combating deceptive and unfair practices, creating a level playing field that promotes competition, fostering a marketplace in which industry can more easily self-regulate, furnishing guidelines to industry for product testing and evaluation, and promoting consumer confidence. The commenters also indicated the Rule does not impose significant, unwarranted costs on industry members or consumers.</P>
                <P>
                    In response to the NPRM, several commenters supported the Commission's decision to retain the Rule and reiterated many of their earlier points.
                    <SU>15</SU>
                    <FTREF/>
                     No commenters objected to the Rule's retention. Accordingly, the Commission retains the Rule.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         PIMA, NAIMA, Anonymous, and Ji.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Commercial Insulation Products Sold in the Residential Market</HD>
                <P>
                    <E T="03">Background:</E>
                     The Rule does not cover insulation sold for use in commercial (including industrial) buildings.
                    <SU>16</SU>
                    <FTREF/>
                     However, comments submitted in response to the ANPR stated that some products developed and marketed primarily for commercial or industrial structures are also marketed for residential applications. In the NPRM, the Commission proposed amending the Rule to clarify that such products fall within the Rule's existing coverage of “home insulation.”
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See, e.g.,</E>
                         45 FR 68920 (Oct. 17, 1980) (staff guidance).
                    </P>
                </FTNT>
                <P>
                    <E T="03">Comments:</E>
                     Several commenters supported the proposed amendment; none objected.
                    <SU>17</SU>
                    <FTREF/>
                     NAIMA explained that the clarification effectively addresses disclosures for products developed initially or primarily for commercial or industrial applications but also marketed in the residential sector. The amendment, according to NAIMA, apprises industry members that commercial and industrial products marketed to homeowners must comply with the Rule.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         ACC, AFM, ICAA, NAIMA, PIMA, and XPSA.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Discussion:</E>
                     As discussed in the NPRM and the comments, some industry members operating in the residential market appear to be unaware that they must follow the R-value Rule for products marketed for residential applications even if originally developed and intended for the commercial or industrial market. Accordingly, the final amendments clarify that the Rule covers such products.
                </P>
                <HD SOURCE="HD2">C. R-Value Claims for Non-Insulation Products</HD>
                <P>
                    <E T="03">Background:</E>
                     Since its original promulgation, the Rule has applied only to products marketed primarily as insulation and thus has excluded non-insulation products with insulating characteristics, such as siding, coatings, caulking, weather stripping, garage doors, or draperies. In the NPRM, the Commission proposed expanding the Rule's current testing requirements to R-value claims made for any non-insulation product marketed to reduce energy use by slowing heat flow in residential buildings.
                    <PRTPAGE P="20780"/>
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Commenters supported (and none opposed) the Commission's proposal.
                    <SU>18</SU>
                    <FTREF/>
                     XPSA, for example, agreed that marketers must support claims for insulating performance qualities for these types of products. NAIMA observed a prevalence of questionable R-value claims for non-insulation products and argued the amendment would provide clear notice that marketers must substantiate R-value claims for such products. Specifically, NAIMA cited numerous questionable R-value (
                    <E T="03">e.g.,</E>
                     R-24) and insulation-related claims made for paints and ceramic coatings. None of the commenters stated that the Rule's testing requirements in § 460.5 would be inappropriate for substantiating such claims or would otherwise fail to cover R-value claims for these various products. Finally, the Brick Industry Association (BIA) explained that its technical documents contain R-value claims for brick wall assemblies derived from a modified version of ASTM C1363. Asserting that its modified approach is consistent with the intent behind ASTM C1363, BIA urged the Commission to approve its R-value disclosures.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         NAIMA, XPSA, Brick Industry Association, ICAA, and ACC.
                    </P>
                </FTNT>
                <P>
                    In addition to discussing the proposed amendment, several commenters raised concerns about energy savings claims.
                    <SU>19</SU>
                    <FTREF/>
                     NAIMA, for instance, asked the Commission to affirm marketers must substantiate any type of energy savings claim. NAIMA, along with ACC, also recommended the Commission reference the Policy Statement Regarding Advertising Substantiation 
                    <SU>20</SU>
                    <FTREF/>
                     and remind manufacturers about the need for competent and reliable scientific evidence to back their claims. Such Commission affirmation, in NAIMA's view, would allow members to “more authoritatively” challenge deceptive competitor claims.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         XPSA, ACC, and NAIMA.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See Substantiation Statement</E>
                        .
                    </P>
                </FTNT>
                <P>
                    <E T="03">Discussion:</E>
                     Consistent with the proposal, the Commission's final amendments direct sellers to use the Rule's existing testing requirements to substantiate R-value claims for non-insulation products, with the exception of fenestration and fenestration attachments.
                    <SU>21</SU>
                    <FTREF/>
                     The Commission has observed a prevalence of grossly exaggerated R-value claims for non-insulation products, such as coatings, paint, and housewrap sold primarily for reasons other than their ability to impede heat flow. Because the Rule has not covered these products, the Commission has challenged such practices as false and unsubstantiated under Section 5 of the FTC Act.
                    <SU>22</SU>
                    <FTREF/>
                     Commenters confirmed that these questionable R-value claims for non-insulation products are common.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         As noted in the NPRM, the amendments exclude fenestration and fenestration attachments because these products are covered under the rating and certification activities of entities such as the National Fenestration Rating Council (NFRC) and DOE. 
                        <E T="03">See</E>
                         Energy Policy Act of 1992 (Section 121 of Pub. L. 102-486).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Edward Sumpolec,</E>
                         No. 6:09-cv-378-ORL-36KRS (M.D. Fla. Jan. 9, 2013); 
                        <E T="03">In the Matter of Kryton Coatings International, Inc. and Procraft, Inc.,</E>
                         FTC Matter/File Number: 012 3060. Docket Number: C-4052 (June 18, 2002); and 
                        <E T="03">Federal Trade Commission</E>
                         v. 
                        <E T="03">Innovative Designs, Inc.,</E>
                         2:16-cv-01669-NBF (W.D. Pa. Nov. 4, 2016).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         NAIMA; Robert Aresty.
                    </P>
                </FTNT>
                <P>
                    To address this problem, the new provision will furnish an effective means to reduce deceptive claims by providing clear guidance for marketers seeking to make truthful, substantiated claims, while establishing a more direct means to combat unsubstantiated R-value claims. The amended rule requires marketers to base any voluntary R-value claim made in advertising for a non-insulation product on the appropriate tests referenced in § 460.5 of the Rule (
                    <E T="03">i.e.,</E>
                     the standard ASTM tests incorporated into the Rule and currently applicable to R-value disclosures for insulation). Accordingly, marketers acting in good faith will have clear notice of the test procedures they should use to substantiate their R-value claims. In addition, the amendment will give the FTC a more efficient and direct means to challenge R-value claims that are not adequately substantiated. The amendment does not impose any disclosure, labeling, or additional requirements for non-insulation products beyond the testing requirements.
                    <SU>24</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         Specifically, as indicated in the amendment to the Rule's Appendix, the requirements of §§ 460.6 through 460.21 do not apply to R-value claims for such products. Although the Rule's recordkeeping requirements (§ 460.9) do not apply to the amendment, marketers still must possess substantiation (
                        <E T="03">e.g.,</E>
                         test reports) for their claims, just as they must for any claim pursuant to the FTC Act.
                    </P>
                </FTNT>
                <P>It is likely most marketers who choose to make R-value claims for various non-insulation products already rely on the appropriate ASTM testing standards. Accordingly, this amendment should pose little or no additional burden. At the same time, it will clarify that marketers must substantiate R-value claims and will provide a check on unscrupulous sellers who seek an unfair advantage by exaggerating product R-values based on faulty tests.</P>
                <P>The final amendment does not contain a provision approving specific technical disclosures related to R-value claims made for brick wall assemblies. Without additional details about how such R-values are derived, the Commission cannot address the particular testing BIA described. Should marketers need guidance about testing for this or other products covered by the new provision, they can contact FTC staff.</P>
                <P>
                    In response to commenter concerns about energy savings claims, the Commission reaffirms that sellers must substantiate their energy savings claims with competent and reliable scientific evidence. Section 460.19 of the Rule requires manufacturers to have a reasonable basis for savings claims and specifies recordkeeping requirements for data that support such claims. In addition, the Commission has provided general guidance for making truthful and not misleading advertising claims through a variety of means, including the Deception Policy Statement and the Policy Statement Regarding Advertising Substantiation.
                    <SU>25</SU>
                    <FTREF/>
                     Marketers may also refer to past Commission cases involving deceptive energy savings claims for further guidance on these issues.
                    <SU>26</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See Deception Statement;</E>
                         and 
                        <E T="03">Substantiation Statement.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See, e.g., In re Gorell Enterprises Inc.,</E>
                         FTC File No. 112-3053 (May 16, 2012); 
                        <E T="03">In re Long Fence &amp; Home LLLP,</E>
                         FTC File No. 112-3005 (Apr. 5, 2012); 
                        <E T="03">In re Serious Energy Inc.,</E>
                         FTC File No. 112-3001 (May 16, 2012); 
                        <E T="03">In re THV Holdings LLC,</E>
                         FTC File No. 112-3057 (May 16, 2012); and 
                        <E T="03">In re Winchester Industries,</E>
                         FTC File No. 102-3171 (May 16, 2012).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">D. Additional Fact Sheet Disclosures</HD>
                <P>
                    <E T="03">Background:</E>
                     In the NPRM, the Commission proposed changing the Rule's fact sheet disclosures to better alert consumers to factors that may affect their heating and cooling costs. The current fact sheets generally advise consumers that their fuel savings depend on a variety of considerations, including their geographic location, type of house, fuel use, and family size. Comments on the ANPR, however, suggested the fact sheets should also mention that proper insulation installation and home air sealing can affect fuel costs. Accordingly, the Commission proposed amending the fact sheets to specifically address these two factors and sought comments on how much time manufacturers would require to make such changes. The Commission also asked whether the Rule should require specific disclosures for R-19 batt insulation, as suggested by some commenters, when installed in typical wall cavities, where compression can reduce R-value.
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Commenters supported including information about installation and home air sealing on fact sheets.
                    <FTREF/>
                    <SU>27</SU>
                      
                    <PRTPAGE P="20781"/>
                    ACC, for instance, indicated the two additional disclosures will help improve consumer understanding of building envelope performance. NAIMA added that the new information will assist consumers in choosing insulation.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         NAIMA, ICAA, and ACC.
                    </P>
                </FTNT>
                <P>Although commenters did not identify any significant regulatory burden associated with the changes, a few requested sufficient compliance time. ACC estimated its members could implement the proposed changes within 180 days. However, given that older fact sheets are likely to remain in circulation beyond that date, it asked the Commission to consider a “reasonable approach” to enforcement within the first year. NAIMA, on the other hand, recommended a two-year effective date to allow manufacturers to exhaust existing stock and revise fact sheets for a wide variety of products.</P>
                <P>Although ACC did not oppose the proposed fact sheet change, it suggested additional mandatory disclosures related to air sealing. Specifically, it recommended that fact sheets include a link to Department of Energy (“DOE”) information about air sealing for homes and buildings. It also requested additional language in § 460.17 requiring installers to tell customers insulation has been installed in accordance with the manufacturer's instructions. Furthermore, ACC recommended additional disclosures consistent with its assertion in comments to the ANPR that an insulation's air infiltration properties impact overall home efficiency. NAIMA, however, expressed its continued disagreement with ACC on the matter. In its view, insulation does not play a major role in blocking total air infiltration in a home, and resistance to air flow is accomplished largely by other measures required by building energy codes, such as gypsum board, sheathing, house wrap, and sealing of joints and holes.</P>
                <P>
                    Finally, NAIMA supported specific disclosures on fact sheets for R-19 batts because such insulation, which is usually 6
                    <FR>1/4</FR>
                    ″ thick, is frequently compressed into 5 
                    <FR>1/2</FR>
                    ″  wall cavities, thus reducing R-value. NAIMA suggested requiring that fact sheets disclose the compressed insulation's R-value rounded to the nearest whole number.
                </P>
                <P>
                    <E T="03">Discussion:</E>
                     The final amendments require fact sheets to include installation and air sealing information. As discussed in the NPRM and by the commenters, these changes will better alert consumers to factors that may affect their heating and cooling costs. The final amendments also contain a new provision requiring fact sheets to disclose reductions in the R-value of R-19 batts when such insulation is compressed into typical wall cavities. This new disclosure will help alert building professionals and consumers to the lower R-value resulting from compression in the typical installation of this product. Finally, the Commission sets the effective date of these new disclosures (and all other final amendments) at one year, which gives manufacturers an entire selling season to make the required changes. The one-year compliance period should be sufficient for manufacturers to update their fact sheets posted online as well as those provided to retailers. Should manufacturers confront issues with existing fact sheet stock, they can contact FTC staff for guidance.
                </P>
                <P>
                    Although the final amendments include the general disclosures proposed in the NPRM, the Commission declines to require additional disclosures related to installation and air infiltration as suggested by ACC. Such disclosures do not appear necessary because the Rule already requires information on labels and fact sheets regarding the importance of proper installation in achieving the labeled R-value. In addition, the Commission declines to require disclosures about the air sealing qualities of insulation and associated impacts on overall energy performance. Commenters responding to the ANPR and NPRM disagreed about this issue. For example, while ACC argued the air sealing performance of insulation is important, NAIMA asserted that marketers should not claim a product's ability to block air infiltration, and not its R-value, is paramount. Likewise, NAIMA objected to claims suggesting insulation that limits air infiltration performs better overall than other insulations.
                    <SU>28</SU>
                    <FTREF/>
                     Furthermore, on several occasions since the Rule's initial promulgation in 1979, the Commission has acknowledged that R-value tests do not account for many factors, such as the design characteristics and geographic location of the building, the specific application in which the product is installed, outside and inside temperatures, air and moisture movement, installation technique, and others. At the same time, the Commission has also maintained that quantifying and providing uniform comparative ratings to reflect these various factors would significantly complicate the Rule's disclosures and likely confuse consumers without providing commensurate benefits.
                    <SU>29</SU>
                    <FTREF/>
                     Accordingly, consistent with the NPRM, the final Rule does not include disclosures addressing these issues. However, the Commission reiterates that under § 460.19 of the Rule, insulation manufacturers must have a reasonable basis for any energy savings claims they make for their insulation products.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         In addition, a Fact Sheet titled “R-Value Introduction” issued by DOE's Oak Ridge National Laboratory also raises questions about the importance of insulation's ability to limit air movement. The Fact Sheet states: “The ability of insulation to limit air movement should not be confused with `air sealing.' The insulation reduces air movement only within the space it occupies. It will not reduce air movement through other cracks between building parts. For example, controlling air movement within a wall cavity will not stop air that leaks between the foundation and the sill plate or between the wall joists and a window frame.” 
                        <E T="03">See https://web.ornl.gov/sci/buildings/tools/insulation/r-value/intro</E>
                        .
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See</E>
                         44 FR at 50226; and 68 FR 41872, 41877-41879 (July 15, 2003).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">E. Online Disclosures</HD>
                <P>
                    <E T="03">Background:</E>
                     In the NPRM, the Commission proposed amending § 305.14 to require online insulation sellers to post labels and fact sheets on their websites for covered insulation products they sell directly to consumers. Large retailers commonly offer insulation for purchase through their websites. Though the current Rule requires retailers to “make fact sheets available to your customers,” it does not specify that fact sheets must be provided for online sales. In the NPRM, the Commission sought comment on the proposed change, including any burdens associated with providing such information online and any other associated issues.
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Two commenters supported the proposal; none opposed it.
                    <SU>30</SU>
                    <FTREF/>
                     NAIMA explained that the burden associated with this requirement would be “nominal” and no different than existing burdens on insulation sellers.
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         NAIMA and ICAA.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Discussion:</E>
                     The final Rule adopts the proposed amendment. The new requirement for online fact sheets will effectuate the Rule's original intent by ensuring online consumers have access to the same information (both fact sheets and labels) as shoppers in stores. Retailers can make these disclosures through a variety of means, such as using expandable thumbnail images of package labels and fact sheets, or with conspicuous links directly to the required information.
                </P>
                <HD SOURCE="HD2">F. Aging of Cellular Plastics</HD>
                <P>
                    <E T="03">Background:</E>
                     In the NPRM, the Commission proposed continuing to require tests on cellular plastic insulations that fully reflect aging on the product's R-value, as currently indicated in § 460.5. In addition, the 
                    <PRTPAGE P="20782"/>
                    Commission proposed eliminating the Rule's reference to the rescinded GSA Specification HH-I-530A aging standard, which appears to be obsolete. The Commission did not propose, as requested by several commenters, a new mandate that industry use only ASTM C1303 or CAN/ULC S770 (
                    <E T="03">i.e.,</E>
                     the LTTR (“long-term thermal resistance”) method) to measure aging. As discussed in detail in the NPRM, several commenters urged the Commission to adopt the LTTR method because, in their view, the test is now well-established and would ensure R-value disclosures for cellular plastic insulations accurately reflect aging effects. Others, however, opposed its adoption, questioning the method's R-value results, coverage, and timeframe. In the NPRM, the Commission declined proposing a requirement that manufacturers use these methods in light of the significant disagreements about the tests' accuracy, scope of coverage, and applicable time frames.
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Commenters generally supported the Commission's proposal to retain a general requirement that sellers conduct R-value tests on samples of cellular plastic insulations that fully reflect the effect of aging on the product's R-value. EPS-AI, for instance, stated that the Rule properly requires that tests for thermal resistance of polyurethane, polyisocyanurate, and extruded polystyrene fully reflect aging effects on the product's R-value. AFM agreed the Rule should continue to require that manufacturers determine the full effect of aging on their R-values, describing this provision as “important protection for consumers.” NAIMA similarly supported retaining this provision. Commenters also supported the proposed elimination of the obsolete GSA aging standard.
                    <SU>31</SU>
                    <FTREF/>
                     EPS-IA noted that the provision's removal would have no adverse impacts.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">See</E>
                         NAIMA, EPS-IA, and PIMA.
                    </P>
                </FTNT>
                <P>
                    Commenters, however, continued to express opposing views about incorporating the LTTR method into the Rule. XPSA agreed with the Commission's decision to forgo adopting the aging standard. Reiterating its previous comments, XPSA stated that evidence does not demonstrate the method provides “a uniform means of accurately comparing different cellular plastic thermal insulations.” 
                    <SU>32</SU>
                    <FTREF/>
                     Others, however, continued to urge the Commission to mandate the LTTR method. EPS-IA argued that, by not adopting the widely accepted ASTM C1303 test, the Commission is failing to fulfill its mission to prevent deception in the marketing of home insulation products and that there is “very little opposition to this standard test method.” It also submitted commercial product literature that, in its view, demonstrates that the lack of mandatory test method has led to deceptive R-value figures from extruded polystyrene manufacturers. Additionally, EPS-IA characterized the spray polyurethane industry's criticism of the LTTR method as “conjecture and self-serving opposition” that fails to hold up against evidence from Oak Ridge National Laboratories and ASTM.
                    <SU>33</SU>
                    <FTREF/>
                     Similarly, PIMA argued the accuracy of ASTM C1303 is well-documented by industry research and DOE studies, and stated that any comments to the contrary are “without merit” and should have no bearing on the Commission's decision. However, PIMA reiterated that the method is not applicable to closed-cell foam insulation products with impermeable facers. PIMA explained that ASTM C518 best measures the R-value of impermeable products (
                    <E T="03">e.g.,</E>
                     foil-faced polyisocyanurate insulation), which are being used more frequently as continuous exterior insulation in new residential construction. PIMA also recognized that other factors may support the FTC's decision to forgo mandating ASTM C1303 for testing closed-cell foam insulation products but did not delineate those factors.
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         83 FR at 2941.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         Commenter Ji suggested that, because products may be stored in warehouses for a period of time after ASTM testing, the R-value reflected on the product label may no longer be accurate at the time of sale. Accordingly, Ji recommended that the test be done in a timely manner to maintain accuracy. However, the Rule already contains provisions related to aging, including the settling of blown cellulose and the aging of cellular plastics. 16 CFR 460.5(a)(1).
                    </P>
                </FTNT>
                <P>
                    <E T="03">Discussion:</E>
                     Consistent with the NPRM, the final Rule retains the requirement in Section 460.5 that R-values fully reflect the effects of aging on cellular plastics and eliminates that section's reference to the GSA Specification HH-I-530A aging standard. Commenters did not identify any adverse impacts from eliminating the Rule's reference to the canceled GSA test. In addition, the final Rule does not mandate use of the LTTR method. Commenters on both the ANPR and NPRM disagreed about whether the Commission should mandate use of the LTTR method. Moreover, the record demonstrates that significant disagreements and concerns remain about various aspects of ASTM C1303 and CAN/ULC S770, including their accuracy, scope of coverage, and applicable timeframe. Nonetheless, because commenters did not identify a viable alternative test method, the Commission understands that many industry members will continue to use the LTTR method to gauge the effects of aging on R-value.
                    <SU>34</SU>
                    <FTREF/>
                     If new developments occur in the future that would warrant its adoption as a regulatory requirement, the Commission may revisit the issue, and interested parties may petition the Commission to consider additional rulemaking.
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         
                        <E T="03">See</E>
                         70 FR at 31264.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">G. Disclosures for Reflective Insulation</HD>
                <P>
                    <E T="03">Background:</E>
                     Reflective insulations, primarily aluminum foils, work by reducing heat transfer when installed facing an airspace. The Rule requires reflective insulation manufacturers to use specific tests to determine R-values, and to disclose those ratings to consumers for particular applications.
                    <SU>35</SU>
                    <FTREF/>
                     Section 460.5(c) requires industry members to test single-sheet systems using ASTM E 408-71 (“Standard Test Methods for Total Normal Emittance of Surfaces Using Inspection-Meter Techniques”), or ASTM C 1371-04a (“Standard Test Method for Determination of Emittance of Materials Near Room Temperature Using Portable Emissometers”). For reflective systems with more than one sheet, § 460.5(b) requires the use of ASTM C 1363-97, “ “Standard Test Method for Thermal Performance of Building Materials and Envelope Assemblies by Means of a Hot Box Apparatus”,” in a test panel constructed according to ASTM C1224-03, “Standard Specification for Reflective Insulation for Building Applications,” and under the test conditions specified in ASTM C1224-03. Section 460.12 of the Rule also requires that labels for reflective insulation include “the number of foil sheets; the number and thickness of the air spaces; and the R-value provided by that system when the direction of heat flow is up, down, and horizontal.”
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         
                        <E T="03">See</E>
                         64 FR 48024, 48038-48039 (Sep. 1, 1999).
                    </P>
                </FTNT>
                <P>
                    The Rule also covers radiant barrier insulations, which are generally installed in attics facing the open airspace. However, as the Commission has stated, R-value claims are not appropriate for these products because no generally accepted test procedure exists to determine their R-value.
                    <SU>36</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         68 FR at 41889-90.
                    </P>
                </FTNT>
                <P>
                    In the NPRM, the Commission did not propose new requirements regarding disclosures or testing for reflective insulations. However, the Commission sought comment on whether to replace the term “aluminum” with “reflective material” or a similar term because 
                    <PRTPAGE P="20783"/>
                    these insulation systems may not always involve aluminum.
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Commenters generally supported the Commission's decision to retain the Rule's requirements for reflective insulation. NAIMA, for instance, supported the Rule's existing label disclosures for reflective insulation products. RIMA also supported retaining the requirement, but offered several suggestions to improve the Rule's provisions. First, it suggested technical amendments to reflective insulation-related terms. Specifically, it recommended replacing “aluminum foil” with “reflective insulation,” noting that low-emittance surfaces are not limited to aluminum foil or film. It also suggested replacing the term “emissivity” with “emittance,” explaining that, although these two terms often appear interchangeably, the ASTM test procedures incorporated in the Rule generally use the term emittance. Similarly, it suggested replacing the term “difference” with “differential” in the Rule's test procedure section (§ 460.5) to be consistent with the ASTM methods.
                </P>
                <P>RIMA also recommended two substantive changes to the reflective insulation requirements. First, it suggested eliminating the reference to ASTM E408 for measuring emittance, explaining that this procedure measures “normal emittance,” while the other procedure allowed by the Rule, ASTM C1371, measures “hemispherical emittance.” Because “normal emittance” measurements are generally lower than “hemispherical emittance,” RIMA asserted that ASTM E408 results generally lead to higher, and thus “overestimated,” R-values. Second, RIMA argued that § 460.5(b) is overly restrictive because it limits use of the ASHRAE Handbook of Fundamentals to specific air space sizes from one line in Table 3 (pages 26.14 and 26.15). RIMA argued that the Rule should specifically allow “interpolation and moderate extrapolation for air spaces greater than 3.5” as stated in a footnote to the ASHRAE table.</P>
                <P>
                    <E T="03">Discussion:</E>
                     Based on the comments, the final Rule includes several technical amendments. First, it replaces references to “aluminum foil” and “foil” and similar words with the more general terms “reflective insulation” and “reflective” because, as noted in the NPRM, these insulation systems may not always involve aluminum.
                    <SU>37</SU>
                    <FTREF/>
                     In addition, consistent with RIMA's suggestion, the final Rule replaces the terms “emissivity” with “emittance” and “differential” with “difference” in § 460.5 to be consistent with the terms used in the test procedures incorporated in the Rule.
                    <SU>38</SU>
                    <FTREF/>
                     These minor conforming changes have no substantive impact on the existing requirements.
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         Specifically, the amendments remove the reference to “aluminum foil” in § 460.2 and replace references to “foil” or “aluminum foil” in § 460.5 with “reflective insulation.”
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">See, e.g.,</E>
                         ASTM C518, 7.7.1 and ASTM C1224, 9.7.3 (“temperature difference”).
                    </P>
                </FTNT>
                <P>The Commission does not further amend the Rule's reflective insulation provisions. Specifically, the amended Rule will continue to allow the use of ASTM E408 as well as C1371. Although the Commission may consider eliminating the test in the future, it declines to make such a change without providing an opportunity for public comment. Furthermore, RIMA's comments did not indicate whether the inconsistencies between the ASTM E408 and C1371 have caused substantial problems in the marketplace nor did it explain the extent to which the test differences impact advertised R-values. In the future, if retaining ASTM E408 in the Rule creates a substantive problem, stakeholders may petition the Commission to consider further Rule amendments.</P>
                <P>
                    Regarding RIMA's proposal to allow extrapolation of values from the ASHRAE table, the Commission has already explained in a 2005 
                    <E T="04">Federal Register</E>
                     final rule that “it does not intend to restrict the use of the tables only to those values specifically printed in the tables themselves.” 
                    <SU>39</SU>
                    <FTREF/>
                     Instead, the Commission recognized “that explanatory information in the footnotes to the ASHRAE handbook allow for interpolation and moderate extrapolation” and expected “industry members to use this guidance in complying with the Rule.” 
                    <SU>40</SU>
                    <FTREF/>
                     Commenters have not identified any ongoing problems stemming from this guidance or lack of a specific reference in the Rule. Accordingly, the Commission does not amend this part of the Rule.
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         70 FR at 31270.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">H. Updating Test References</HD>
                <P>
                    <E T="03">Background:</E>
                     In the NPRM, the Commission proposed updating § 460.5 to reflect the most recent versions of the ASTM test procedures. In addition, to ensure consistency with the Office of 
                    <E T="04">Federal Register</E>
                     (OFR) regulations, it proposed removing § 460.7 to eliminate automatic updates to the ASTM test procedures incorporated by reference in the Rule. Specifically, OFR regulations state that incorporation by reference is “limited to the edition of the publication that is approved,” and “future amendments or revisions of the publication are not included.” 
                    <SU>41</SU>
                    <FTREF/>
                     The proposed amendment would also ensure the Rule provides notice and an opportunity to comment on test updates before they are incorporated by reference. The Commission indicated that it would periodically review the Rule's test procedures to ensure the Rule contains the most recent versions.
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         
                        <E T="03">See</E>
                         1 CFR 51.1(f).
                    </P>
                </FTNT>
                <P>
                    <E T="03">Comments:</E>
                     Commenters supported the proposed amendments to update the Rule's test procedure provisions.
                    <SU>42</SU>
                    <FTREF/>
                     According to NAIMA, the change will ensure the Commission “provides notice and an opportunity to comment on updates before they are incorporated into the regulations.” PIMA expressed support for FTC's continued reliance on consensus-based test standards such as those administered by ASTM because such “standards are continually reviewed by subject-matter experts and allow for broad stakeholder input through transparent development and maintenance processes.” It also encouraged FTC to consider the best method to update test standards “moving forward” and noted the burdensome process involved with updating the Rule's references. AFM added that the Rule should change its ASTM reference to the organization's current name, “ASTM International.” It also recommended the Rule state that the test methods are “developed” rather than “designed” by ASTM.
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         PIMA and NAIMA. No commenters opposed this.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Discussion:</E>
                     Given the support for the test method updates announced in the NPRM, the Commission amends the Rule to reflect the most current test versions.
                    <SU>43</SU>
                    <FTREF/>
                     In addition, the amendments remove § 460.7 to eliminate automatic updates to the ASTM test procedures incorporated by reference in the Rule. The Commission will continue to update the test procedures as part of its routine Rule reviews. In the interim, if interested parties identify the need for any specific updates, they should petition the Commission for an amendment. The final Rule also updates the formal name for ASTM to “ASTM International” and changes the term “designed” to “developed” to better reflect ASTM's role.
                    <SU>44</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         The final amendments reference the latest versions of three recently updated tests: ASTM C518-17, ASTM C739-17, and ASTM C1149-17.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         It appears that ASTM tends to use the term “development” with regard to standards. 
                        <E T="03">See, e.g.,</E>
                         2016 Annual Book of ASTM Standards, Section 4, Vol. 04.06 (“Thermal Insulation: Building and Environmental Acoustics”), at iii (“[ASTM] is a 
                        <PRTPAGE/>
                        globally recognized leader in the development and delivery of international voluntary standards.”).
                    </P>
                </FTNT>
                <PRTPAGE P="20784"/>
                <HD SOURCE="HD2">I. Limited Format Disclosures</HD>
                <P>
                    <E T="03">Background:</E>
                     In the NPRM, the Commission proposed amending the Rule to exempt space-constrained advertising from the required disclosures in §§ 460.18 and 460.19, which may be infeasible or impractical for some methods of advertising.
                </P>
                <P>
                    <E T="03">Comments:</E>
                     The commenters expressed different views on the proposal. NAIMA supported the amendment, explaining that the required disclosures “may be infeasible or impractical for some methods of advertising, such as [T]witter and mobile sources.” It also noted the amendment is consistent with similar exemptions for radio and television advertisements.
                    <SU>45</SU>
                    <FTREF/>
                     ICAA, however, opposed the exemption, noting that digital advertising is likely to “outpace print and radio advertising,” making it the “mainstream communication channel for consumers.” In its view, the exemption would lead to an absence of disclosures “where the bulk of advertising dollars are expended,” and consumers would have no knowledge of the applicable federal rules for these claims. To address space-constrained formats, ICAA suggested the Rule require marketers to provide a short hyperlink (
                    <E T="03">e.g.,</E>
                     “See FTC disclosures here”) to take consumers directly “to the appropriate code sections.” 
                    <SU>46</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         PIMA also supported the amendments.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         Commenter Ji also opposed the exemption, stating that the current disclosures “help consumers make the right choice.”
                    </P>
                </FTNT>
                <P>
                    <E T="03">Discussion:</E>
                     As proposed in the NPRM, the final Rule exempts space-constrained advertisements from the affirmative disclosures in §§ 460.18 and 460.19.
                    <SU>47</SU>
                    <FTREF/>
                     For example, the Rule requires the following statement in any insulation advertisement containing an R-value claim: “The higher the R-value, the greater the insulating power. Ask your seller for the fact sheet on R-values.” The amendment exempts such statements for space-constrained advertisements. It defines “space-constrained” as any communication made through interactive media (such as the internet, online services, and software, including but not limited to internet search results and banner ads) that has space, format, size or technological limitations or restrictions that effectively prevent marketers from making the required disclosures.
                </P>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         The Commission has already excluded television and radio advertising from the more detailed disclosure requirements because it found meaningful disclosures are probably not effective in those media. 
                        <E T="03">See</E>
                         70 FR at 31271; 51 FR 39650 (Oct. 30, 1986).
                    </P>
                </FTNT>
                <P>
                    This change will reduce the Rule's burdens without significantly reducing its effectiveness. Specifically, the Rule already provides several tiers of disclosures. In addition to the affirmative advertising disclosures, sellers must provide disclosures on package labels, as well as in fact sheets, that must be made available to customers before purchase. Furthermore, the final amendments add new requirements to ensure labels and fact sheets are available for online sales, making this important R-value information accessible to consumers before their purchase. In addition, the amendments do not create a blanket exemption for disclosures on all mobile devices or similar formats. Indeed, some of the required disclosures (
                    <E T="03">e.g.,</E>
                     R-value disclosures triggered by § 460.18(b) and (c)) do not require significant space and thus are unlikely to qualify for the exemption. Accordingly, industry members must show there is insufficient space for the required disclosures to claim the exemption. Finally, the exemption does not alter advertisers' obligation to follow the substantiation requirements in § 460.19.
                    <SU>48</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         Section 460.19 requires a reasonable basis for fuel savings claims and directs marketers to maintain proof of such claims for three years.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">J. Mean Temperature</HD>
                <P>
                    <E T="03">Background:</E>
                     Since its promulgation in 1979, § 460.5 of the Rule has required R-value testing at a 75 °F mean temperature for most insulation products. In initially issuing this requirement, the Commission explained that the “choice of this particular temperature is based on a significant volume of record evidence that 75 °F is already a widely-used test temperature and is incorporated in many voluntary industry standards and federal procurement specifications.” 
                    <SU>49</SU>
                    <FTREF/>
                     Section 460.5 requires testing at a 50 °F temperature differential (
                    <E T="03">i.e.,</E>
                     the difference between the hot and cold surface during testing).
                </P>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         44 FR at 50227.
                    </P>
                </FTNT>
                <P>
                    In response to the ANPR, some commenters recommended the Rule address insulation performance at mean temperatures lower than 75 °F. Specifically, they suggested the Commission consider either requiring an additional R-value disclosure at a low mean temperature or requiring disclosures about the cold weather performance of certain insulations. In the NPRM (83 FR at 2942), the Commission did not propose revising the Rule's mean test temperature requirement, nor did it propose specific affirmative disclosures for insulation products that may exhibit lower R-values at low temperatures. The Commission explained that, given the temperature differences throughout the country, no one temperature is likely to be sufficiently representative of consumer experiences.
                    <SU>50</SU>
                    <FTREF/>
                     The Commission noted, however, that nothing in the FTC Act or the Rule prohibits sellers from promoting their products' performance in low temperatures in their advertising. If a seller's products have better R-values than others at low temperatures, it may make truthful, substantiated claims conveying its products' advantages.
                    <SU>51</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         In initially issuing the Rule, the Commission did not attempt to specify a mean test temperature representative of any particular geographical region or season. Indeed, it reasoned that any attempt to do so would yield results inappropriate for other regions or seasons. Accordingly, the Commission chose a single temperature widely used in industry standards, recognizing the fact that it is not perfectly representative. 
                        <E T="03">See</E>
                         64 FR at 48037; and 44 FR at 50219, 50227.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         
                        <E T="03">See</E>
                         68 FR at 41878-41879.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Comments:</E>
                     The commenters generally supported the Commission's decision to retain the current mean temperature requirements.
                    <SU>52</SU>
                    <FTREF/>
                     NAIMA, for example, agreed that the range of temperature differences throughout the country makes it unlikely a single temperature will be representative of consumer experiences. It also noted that mandatory R-value disclosures at additional temperatures would increase the industry burden without a corresponding consumer benefit. ACC did not oppose the proposal but looked for further guidance on specific disclosures and whether they are substantiated. Specifically, it asked whether a manufacturer can make additional R-value claims, beyond those required by the Rule, “at another temperature provided the statement is clearly qualified that the testing was conducted at another temperature.” Further, it inquired whether additional claims such as “R-value at XX degrees F” or “thermal resistance at XX degrees F” would be considered adequately substantiated, qualified, and otherwise compliant with the Rule and Section 5 of the FTC Act.
                </P>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         
                        <E T="03">See</E>
                         PIMA, XPSA, and NAIMA.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Discussion:</E>
                     The Commission declines to amend the Rule's mean temperature requirements. As discussed in the NPRM, in publishing the original Rule, the Commission did not attempt to specify a mean test temperature representative of any particular geographical region or season. Further, given the temperature differences throughout the country, no one 
                    <PRTPAGE P="20785"/>
                    temperature is likely to be sufficiently representative of consumer experiences. Accordingly, the
                </P>
                <P>Commission established a single temperature widely used in industry standards, recognizing it provides a reasonable benchmark to compare claims. As discussed in the NPRM and in comments, this reasoning still holds true.</P>
                <P>
                    Regarding ACC's questions about additional claims, the Commission reiterates its view that sellers may make truthful, substantiated claims conveying, for example, that their products have higher R-values at low temperatures compared to competing products. However, as the Commission considers the net impression of an entire advertisement to determine whether it is deceptive, the Commission declines to offer an opinion about ACC's suggested advertising claims in isolation.
                    <SU>53</SU>
                    <FTREF/>
                     Industry members may consult existing FTC guidance in developing their own advertising claims.
                    <SU>54</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         “[T]he Commission will evaluate the entire advertisement, transaction, or course of dealing in determining how reasonable consumers are likely to respond. Thus, in advertising the Commission will examine `the entire mosaic, rather than each tile separately.' ” Deception Policy Statement, 
                        <E T="03">supra</E>
                         (quoting 
                        <E T="03">FTC</E>
                         v. 
                        <E T="03">Sterling Drug,</E>
                         317 F.2d 669, 674 (2d Cir. 1963)).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         The Commission determines whether an advertisement is deceptive by engaging “in a three-step inquiry, considering: (i) What claims are conveyed in the ad, (ii) whether those claims are false, misleading, or unsubstantiated, and (iii) whether the claims are material to prospective consumers.” 
                        <E T="03">POM Wonderful, LLC</E>
                         v. 
                        <E T="03">F.T.C.,</E>
                         777 F.3d 478, 490 (D.C. Cir. 2015), 
                        <E T="03">cert. denied,</E>
                         136 S. Ct. 1839 (2016). The adequacy of disclosures may depend on how consumers interpret particular claims, including the net consumer impression of the advertisement. 
                        <E T="03">See Kraft, Inc.</E>
                         v. 
                        <E T="03">F.T.C.,</E>
                         970 F.2d 311, 314, 318 (7th Cir. 1992).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">K. R-Value per Inch Claims</HD>
                <P>
                    <E T="03">Background:</E>
                     Section 460.20 of the Rule prohibits R-value per inch claims unless test results prove the product's R-value per inch does not drop at greater thicknesses. As the Commission has explained previously, R-value per inch claims lead “consumers to believe that insulation R-values are linear,” when, in fact, they often are not. For many insulation products, R-value does not increase proportionally with thickness. Accordingly, unqualified R-value per inch claims are often deceptive.
                    <SU>55</SU>
                    <FTREF/>
                     Therefore, the Rule prohibits these claims unless a differing, outstanding FTC Order applies or the seller has actual test results proving the product's R-value per inch is constant at various thicknesses. In response to comments seeking further clarification, the Commission declined to propose amendments in NPRM because it lacked evidence indicating the Rule's current language is ambiguous or confusing.
                </P>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         44 FR at 50234.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Comments:</E>
                     Commenters offered differing views on R-value per inch claims. ACC agreed with the Commission's approach and indicated that the current Rule is clear and concise. However, NAIMA asked for further clarity and reiterated a concern, expressed in earlier comments, about a recent decision from the Better Business Bureau's National Advertising Division (“NAD”) involving cellulose insulation claims.
                    <SU>56</SU>
                    <FTREF/>
                     In particular, NAIMA requested the Commission clarify what constitutes “actual test data” under the Rule, a concept contested in the NAD proceeding. According to NAIMA, cellulose manufacturers have substantiated their R-value claims at multiple thicknesses merely through a coverage chart, which, in NAIMA's view, does not constitute “actual test data.” Finally, NAIMA urged the Commission to amend the Rule to include the following clarification: “Any express or implied claim that fibrous insulation R-value is linear with thickness is per se misleading and, therefore, prohibited, unless qualifying for one of the exceptions set forth in this section.”
                </P>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         NAIMA (citing 
                        <E T="03">Applegate Insulation (Cellulose Insulation Products),</E>
                         Case #5961, NAD/CARU Case reports (June 2016)).
                    </P>
                </FTNT>
                <P>
                    <E T="03">Discussion:</E>
                     The Commission declines to amend the Rule's R-value per inch provision or to require marketers to make additional disclosures related specifically to fibrous insulation. As discussed in the NPRM, in adopting this provision, the Commission recognized that many consumers may believe the relationship between R-value and thickness is linear. Specifically, the Commission explained that misleading “references to the R-value for a one-inch thickness of the material will encourage consumers to think that it is appropriate to multiply this figure by the desired number of inches, as though the R-value per inch was constant.” The current provision addresses this issue by prohibiting R-value per inch claims unless supported by the tests required by the Rule, which the Commission considers to be competent and reliable scientific evidence. Furthermore, § 460.20 applies to all insulation. Therefore, a specific provision relating to fibrous insulation, as some commenters suggested, is unnecessary. Finally, the Commission lacks a basis to address the claims reviewed by NAD, given the limited information in the comments and the absence of views from cellulose manufacturers involved in the dispute.
                </P>
                <HD SOURCE="HD2">L. Spray Foam Disclosures</HD>
                <P>
                    <E T="03">Background and Comments:</E>
                     NAIMA asked the Commission to consider new regulatory requirements for spray foam insulation (SPF). Specifically, NAIMA raised concerns that the Rule does not adequately ensure SPF products deliver their advertised R-value. Unlike other insulation sellers, SPF installers, according to NAIMA, must essentially “manufacture” their insulation on-site to deliver the advertised thermal performance or R-value. In doing so, NAIMA explained that installers must manage a process involving “generators, compressors, proportioning pumps, temperature controls, heated hoses and spray guns” while wearing personal protective equipment. NAIMA claimed that certain SPF companies advocate “underfilling” wall cavities because, according to those companies, the superior air sealing qualities of foam insulation compensate for any reductions in R-value due to such a practice. NAIMA objects to such representations and argued that no “reliable, scientifically validated method” exists to support claims about R-value degradation due to air infiltration. In its view, air barriers, which are separate from insulation and typically required for new homes, already prevent any air infiltration through fiberglass or other types of insulation. NAIMA further stated that, as long as the wall assembly is sealed to code specifications, all forms of insulation achieve the same thermal performance.
                </P>
                <P>
                    To address these concerns, NAIMA recommended the Commission require that: (1) SPF installations entirely fill the wall cavity; (2) SPF installers maintain testing records; (3) SPF manufacturers give homeowners detailed information about “the manufacturing process that will occur in their residence”; (4) SPF installers disclose the mixture of chemicals and installation of foam in the home; and (5) manufacturer and installer websites publicly disclose information about SPF insulation R-values. NAIMA stated that, in lieu of these specific requirements, the Commission could add a general requirement applicable to all forms of insulation, including fiberglass and mineral wool, that installers follow manufacturer's installation recommendations. Additionally, commenter Harrison raised concerns about the fire risks associated with “sprayed and sheet insulation materials” and called for improved 
                    <PRTPAGE P="20786"/>
                    regulation to give clarity and guidance to industry members.
                </P>
                <P>
                    <E T="03">Discussion:</E>
                     The Commission does not propose Rule requirements to address SPF insulation. NAIMA highlights an ongoing debate, discussed in the NPRM (83 FR at 2938-2940), between foam and fiberglass manufacturers about the impact of an insulation's air infiltration qualities on insulation performance and overall home efficiency. However, NAIMA has not established a prevalence of deceptive practices that would support the sweeping Rule amendments it recommends. Furthermore, the Rule already addresses many of the issues NAIMA raised, such as the need for installers to deliver the advertised R-value (
                    <E T="03">e.g.,</E>
                     460.17) and the importance of properly installing insulation (
                    <E T="03">e.g.,</E>
                     460.12 and 460.13).
                </P>
                <P>The Rule requires appropriate R-value disclosures and the substantiation of claims made in these disclosures, and prohibits false or misleading claims. It does not mandate the R-value of insulation installed in homes nor does it address whether some forms of insulation may be more effective than others for certain applications. These issues generally fall within the authority and expertise of state and local energy code officials, DOE experts, and other building professionals. This does not mean that the Commission endorses any particular claims or practices in the market. Any representations made by insulation sellers, whether covered by the R-value Rule or not, must be substantiated and otherwise not violate Section 5 of the FTC Act. Thus, manufacturers must back up any claims about insulation performance with competent and reliable scientific evidence. The Commission will take NAIMA's comments under advisement and continue to follow developments in the market. Finally, the Commission does not propose any changes to the Rule to address insulation safety issues. Safety issues generally fall within the mission and authority of other agencies such as the Consumer Products Safety Commission.</P>
                <HD SOURCE="HD1">VI. Regulatory Flexibility Act</HD>
                <P>
                    The Regulatory Flexibility Act (RFA), 5 U.S.C. 601 through 612, requires that the Commission provide an Initial Regulatory Flexibility Analysis (IRFA) with a proposed rule and a Final Regulatory Flexibility Analysis (FRFA), if any, with the final rule, unless the Commission certifies that the rule will not have a significant economic impact on a substantial number of small entities. 
                    <E T="03">See</E>
                     5 U.S.C. 603 through 605.
                </P>
                <P>The Commission does not anticipate that the amendments will have a significant economic impact on a substantial number of small entities. The Commission recognizes that some of the affected manufacturers may qualify as small businesses under the relevant thresholds. Because the R-value Rule covers home insulation manufacturers and retailers, professional installers, new home sellers, and testing laboratories, the Commission believes that any amendments to the Rule may affect a substantial number of small businesses. However, the Commission does not expect that the economic impact of the amendments will be significant because these amendments involve updates, clarifications and minor changes to the Rule.</P>
                <P>Although the Commission has certified under the RFA that the amendments would not have a significant impact on a substantial number of small entities, the Commission has determined, nonetheless, that it is appropriate to publish an FRFA in order to explain the impact of the amendments on small entities as follows:</P>
                <HD SOURCE="HD2">A. Description of the Reasons That Action by the Agency Is Being Taken</HD>
                <P>The Commission initiated this rulemaking to assist consumers in their insulation purchases by clarifying several provisions, updating requirements, ensuring proper test procedures are followed to determine the R-values of covered products, and exempting certain types of advertising from affirmative disclosures.</P>
                <HD SOURCE="HD2">B. Issues Raised by Comments in Response to the IRFA</HD>
                <P>The Commission did not receive any comments specifically related to the impact of the final amendment on small businesses. No comments were filed by the Chief Counsel for Advocacy of the Small Business Administration.</P>
                <HD SOURCE="HD2">C. Small Entities to Which the Proposed Rule Will Apply</HD>
                <P>The R-value Rule covers home insulation manufacturers and retailers, professional installers, new home sellers, and testing laboratories. The Commission recognizes that many affected entities may qualify as small businesses under the relevant thresholds. The Commission does not expect, however, that the economic impact of implementing the amendments will be significant because the Commission plans to provide businesses with ample time to implement the requirements, and the amendments require information disclosures that do not impose substantial burdens.</P>
                <HD SOURCE="HD2">D. Projected Reporting, Recordkeeping and Other Compliance Requirements</HD>
                <P>The Commission anticipates that the amendments may slightly increase reporting or recordkeeping requirements associated with the Rule for some small entities, while reducing some compliance requirements associated with advertising in space-constrained formats. The amendments likely will increase some compliance requirements by extending the requirement to substantiate R-value claims to non-insulation products. The amendments will also require manufacturers to update labels and fact sheets, but provides substantial time for manufacturers to update these materials. The amendments will also likely reduce burden by exempting certain disclosures for limited format advertising.</P>
                <HD SOURCE="HD2">E. Description of Steps Taken To Minimize Significant Economic Impact, if Any, on Small Entities, Including Alternatives</HD>
                <P>The Commission did not propose any specific small entity exemption or other significant alternatives, but sought comment and information on the need, if any, for alternative compliance methods that would reduce the economic impact of the Rule on small entities. In particular, the Commission sought comments on whether it should time the Rule's effective date to provide additional time for small business compliance. No comments identified any new compliance costs, and several comments argued that some of the amendments will reduce compliance costs.</P>
                <HD SOURCE="HD1">VII. Paperwork Reduction Act</HD>
                <P>
                    The current Rule contains recordkeeping, disclosure, testing, and reporting requirements that constitute information collection requirements as defined by 5 CFR 1320.3(c), the definitional provision within the Office of Management and Budget (OMB) regulations that implement the Paperwork Reduction Act (PRA). OMB has approved the Rule's existing information collection requirements through January 31, 2021 (OMB Control No. 3084-0109). As detailed below, the amendments' changes to the Rule's labeling requirements should not alter in the net the Rule's overall PRA burden.
                    <SU>57</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>57</SU>
                         The PRA analysis for this rulemaking focuses strictly on the information collection requirements created by and/or otherwise affected by the amendments. Unaffected information collection provisions have previously been accounted for in 
                        <PRTPAGE/>
                        past FTC analyses under the Rule and are covered by the current PRA clearance from OMB.
                    </P>
                </FTNT>
                <PRTPAGE P="20787"/>
                <P>
                    The Commission adopts a small number of rule amendments designed to clarify the Rule, update its disclosures, and require specific testing procedures for non-insulation products. In the Commission's view, the amendments will not increase the PRA burden associated with those testing procedures. Under the current requirements, any marketer making an R-value claim must have competent and reliable evidence to back that claim. Accordingly, it is likely that such marketers already conduct testing for claims under the normal course of business. Thus, the requirement should not increase those burdens. The amendments regarding the small changes to fact sheets and online displays of fact sheets and labels also should not increase the Rule's current PRA burden. The Rule already requires retailers to provide fact sheets to their consumers. In addition, any potential increase in burden resulting from those amendments would likely be offset by the amendment exempting space-constrained advertising from the affirmative disclosures in §§ 460.18 and 460.19.
                    <SU>58</SU>
                    <FTREF/>
                     Finally, no comments disputed this PRA analysis when presented in the NPRM. Consequently, the Commission believes the amendments will not result in incremental PRA burden.
                </P>
                <FTNT>
                    <P>
                        <SU>58</SU>
                         The fact sheet amendments in § 460.13(e) do not constitute a “collection of information” under the PRA because they are a “public disclosure of information originally supplied by the government to the recipient for the purpose of disclosure to the public” as indicated in OMB regulations. 
                        <E T="03">See</E>
                         5 CFR 1320.3(c)(2).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">VIII. Incorporation by Reference</HD>
                <P>
                    Consistent with 5 U.S.C. 552(a) and 1 CFR part 51, the Commission incorporates the specifications of the following documents published by the American Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc. and ASTM International: 
                    <SU>59</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>59</SU>
                         Quoted descriptions of ASTM standards from 
                        <E T="03">www.astm.org.</E>
                    </P>
                </FTNT>
                <P>• 2017 ASHRAE Handbook—Fundamentals, I-P Edition (published 2017) (ASHRAE Handbook covers basic principles and data used in the heating, ventilation, air conditioning and refrigeration industry);</P>
                <P>• ASTM C 177-13, “Standard Test Method for Steady-State Heat Flux Measurements and Thermal Transmission Properties by Means of the Guarded-Hot-Plate Apparatus” (published October 2013) (“This test covers the measurement of heat flux and associated test conditions for flat specimens. The guarded-hot-plate apparatus is generally used to measure steady-state heat flux through materials having a “low” thermal conductivity and commonly denoted as “thermal insulators.”);</P>
                <P>• ASTM C 518-17, “Standard Test Method for Steady-State Thermal Transmission Properties by Means of the Heat Flow Meter Apparatus” (published July 2017) (“This test method covers the measurement of steady state thermal transmission through flat slab specimens using a heat flow meter apparatus.”);</P>
                <P>• ASTM C 739-17, “Standard Specification for Cellulosic Fiber Loose- Fill Thermal Insulation” (published August 2017) (“This specification covers the composition and physical requirements of chemically treated, recycled cellulosic fiber loose-fill type thermal insulation for use in attics or enclosed spaces in housing, and other framed buildings within the ambient temperature range from—45 to 90 °C by pneumatic or pouring application.”);</P>
                <P>• ASTM C 1045-07 (reapproved 2013), “Standard Practice for Calculating Thermal Transmission Properties Under Steady-State Conditions (published January 2014)” (“This practice is intended to provide the user with a uniform procedure for calculating the thermal transmission properties of a material or system from standard test methods used to determine heat flux and surface temperatures.”);</P>
                <P>• ASTM C 1114-06 (Reapproved 2013), “Standard Test Method for Steady-State Thermal Transmission Properties by Means of the Thin-Heater Apparatus” (published January 2014) (“This test method covers the determination of the steady-state thermal transmission properties of flat slab specimens of thermal insulation using a thin heater of uniform power density having low lateral heat flow.”);</P>
                <P>• ASTM C 1149-17, “Standard Specification for Self-Supported Spray Applied Cellulosic Thermal Insulation” (published October 2017) (“The specification covers the physical properties of self-supported spray applied cellulosic fibers intended for use as thermal insulation or an acoustical absorbent material, or both.”);</P>
                <P>• ASTM C 1224-15, “Standard Specification for Reflective Insulation for Building Applications” (published November 2015) (“This specification covers the general requirements and physical properties of reflective insulations for use in building applications.”);</P>
                <P>• ASTM C 1363-11, “Standard Test Method for Thermal Performance of Building Materials and Envelope Assemblies by Means of a Hot Box Apparatus” (published June 2011) (“This test method establishes the principles for the design of a hot box apparatus and the minimum requirements for the determination of the steady state thermal performance of building assemblies when exposed to controlled laboratory conditions. This method is also used to measure the thermal performance of a building material at standardized test conditions such as those required in ASTM material Specifications C739, C764, C1224 and Practice C1373.”);</P>
                <P>• ASTM C 1371-15, “Standard Test Method for Determination of Emittance of Materials Near Room Temperature Using Portable Emissometers” (published June 2015) (“This test method covers a technique for determination of the emittance of opaque and highly thermally conductive materials using a portable differential thermopile emissometer. The purpose of the test method is to provide a comparative means of quantifying the emittance of materials near room temperature.”);</P>
                <P>• ASTM C 1374-14, “Standard Test Method for Determination of Installed Thickness of Pneumatically Applied Loose-Fill Building Insulation” (published May 2014) (“This test method covers determination of the installed thickness of pneumatically applied loose-fill building insulations prior to settling by simulating an open attic with horizontal blown applications.”);</P>
                <P>• ASTM E 408-13, “Standard Test Methods for Total Normal Emittance of Surfaces Using Inspection-Meter Techniques” (published June 2013) (“These test methods cover determination of the total normal emittance of surfaces by means of portable, as well as desktop, inspection meter instruments.”).</P>
                <P>
                    The ASHRAE Handbook and the ASTM standards are reasonably available to interested parties. Members of the public can obtain copies of ASTM C 177-13, ASTM C 518-17, ASTM C 739-17, ASTM C 1045-07, ASTM C 1114-06, ASTM C 1149-17, ASTM C 1224-15, ASTM C 1363-11, ASTM C 1371-15, ASTM C 1374-14, and ASTM E 408-13 from ASTM International, 100 Barr Harbor Drive, West Conshohocken, PA 19428; telephone: 1-877-909-2786; internet address: 
                    <E T="03">http://www.astm.org.</E>
                     Members of the public can obtain copies of the 2017 ASHRAE Handbook—Fundamentals, I-P Edition (2017) from ASHRAE Headquarters 1791 Tullie Circle, NE Atlanta, GA 30329; telephone (404) 636-8400; internet address: 
                    <E T="03">https://www.ashrae.org.</E>
                     The ASHRAE 
                    <PRTPAGE P="20788"/>
                    Handbook and the ASTM standards are also available for inspection at the FTC Library (202-326-2395), Federal Trade Commission, Room H-630, 600 Pennsylvania Avenue NW, Washington, DC 20580.
                </P>
                <HD SOURCE="HD1">Final Rule Language</HD>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 16 CFR Part 460</HD>
                    <P>Advertising, Incorporation by reference, Insulation, Labeling, Reporting and recordkeeping requirements, Trade practices.</P>
                </LSTSUB>
                <P>For the reasons stated in the preamble, the Federal Trade Commission amends 16 CFR part 460 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 460—LABELING AND ADVERTISING OF HOME INSULATION</HD>
                </PART>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>1. The authority citation for part 460 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            15 U.S.C. 41 
                            <E T="03">et seq.</E>
                             (38 Stat. 717, as amended).
                        </P>
                    </AUTH>
                    <EXTRACT>
                        <P>Appendix A also issued under 46 FR 22179 (April 16, 1981); 46 FR 22180 (April 16, 1981); 48 FR 31192 (July 7, 1983).</P>
                    </EXTRACT>
                </REGTEXT>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>2. Revise § 460.1 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 460.1 </SECTNO>
                        <SUBJECT> What this part does.</SUBJECT>
                        <P>This part deals with R-value claims, as well as home insulation labels, fact sheets, ads, and other promotional materials in or affecting commerce, as “commerce” is defined in the Federal Trade Commission Act. If you are covered by this part, breaking any of its rules is an unfair or deceptive act or practice or an unfair method of competition under Section 5 of that Act. You can be fined heavily (up to the civil monetary penalty amount specified in § 1.98 of this chapter) each time you break a rule.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>3. Revise § 460.2 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 460.2 </SECTNO>
                        <SUBJECT> What is home insulation.</SUBJECT>
                        <P>Insulation is any material mainly used to slow heat flow. It may be mineral or organic, fibrous, cellular, or reflective. It may be in rigid, semirigid, flexible, or loose-fill form. Home insulation is for use in old or new homes, condominiums, cooperatives, apartments, modular homes, or mobile homes. It does not include pipe insulation. It does not include any kind of duct insulation except for duct wrap. It also includes insulation developed and marketed for commercial or industrial buildings that is also marketed for and used in residential buildings.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>4. Revise § 460.3 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 460.3 </SECTNO>
                        <SUBJECT> Who is covered.</SUBJECT>
                        <P>You are covered by this part if you are a member of the home insulation industry. This includes individuals, firms, partnerships, and corporations. It includes manufacturers, distributors, franchisors, installers, retailers, utility companies, and trade associations. Advertisers and advertising agencies are also covered. So are labs doing tests for industry members. If you sell new homes to consumers, you are covered. If you make R-value claims for non-insulation products described in § 460.22, you are covered by the requirements of that section.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>5. Revise § 460.4 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 460.4 </SECTNO>
                        <SUBJECT> When the rules in this part apply.</SUBJECT>
                        <P>You must follow the rules in this part each time you import, manufacture, distribute, sell, install, promote, or label home insulation. You must follow them each time you prepare, approve, place, or pay for home insulation labels, fact sheets, ads, or other promotional materials for consumer use. You must also follow them each time you supply anyone covered by this part with written information that is to be used in labels, fact sheets, ads, or other promotional materials for consumer use. Testing labs must follow the rules unless the industry members tell them, in writing, that labels, fact sheets, ads, or other promotional materials for home insulation will not be based on the test results. You must follow the requirements in § 460.22 each time you make an R-value claim for non-insulation products marketed in whole or in part to reduce residential energy use by slowing heat flow.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>6. Revise § 460.5 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 460.5 </SECTNO>
                        <SUBJECT> R-value tests.</SUBJECT>
                        <P>R-value measures resistance to heat flow. R-values given in labels, fact sheets, ads, or other promotional materials must be based on tests done under the methods listed in paragraphs (a) through (d) of this section.</P>
                        <P>(a) All types of insulation except reflective insulation must be tested with ASTM C177-13, “Standard Test Method for Steady-State Heat Flux Measurements and Thermal Transmission Properties by Means of the Guarded-Hot-Plate Apparatus;” ASTM C518-17, “Standard Test Method for Steady-State Thermal Transmission Properties by Means of the Heat Flow Meter Apparatus;” ASTM C1363-11, “Standard Test Method for Thermal Performance of Building Materials and Envelope Assemblies by Means of a Hot Box Apparatus” or ASTM C1114-06, “Standard Test Method for Steady-State Thermal Transmission Properties by Means of the Thin-Heater Apparatus.” The tests must be done at a mean temperature of 75 degrees Fahrenheit and with a temperature difference of 50 degrees Fahrenheit plus or minus 10 degrees Fahrenheit. The tests must be done on the insulation material alone (excluding any airspace). R-values (“thermal resistance”) based upon heat flux measurements according to ASTM C177-13 or ASTM C518-17 must be reported only in accordance with the requirements and restrictions of ASTM C1045-07, “Standard Practice for Calculating Thermal Transmission Properties Under Steady-State Conditions.”</P>
                        <P>(1) For polyurethane, polyisocyanurate, and extruded polystyrene, the tests must be done on samples that fully reflect the effect of aging on the product's R-value.</P>
                        <P>(2) For loose-fill cellulose, the tests must be done at the settled density determined under paragraph 8 of ASTM C739-17, “Standard Specification for Cellulosic Fiber Loose-Fill Thermal Insulation.”</P>
                        <P>(3) For loose-fill mineral wool, self-supported, spray-applied cellulose, and stabilized cellulose, the tests must be done on samples that fully reflect the effect of settling on the product's R-value.</P>
                        <P>(4) For self-supported spray-applied cellulose, the tests must be done at the density determined pursuant to ASTM C1149-17, “Standard Specification for Self-Supported Spray Applied Cellulosic Thermal Insulation.”</P>
                        <P>(5) For loose-fill insulations, the initial installed thickness for the product must be determined pursuant to ASTM C1374-14, “Standard Test Method for Determination of Installed Thickness of Pneumatically Applied Loose-Fill Building Insulation,” for R-values of 13, 19, 22, 30, 38, 49 and any other R-values provided on the product's label pursuant to § 460.12.</P>
                        <P>(b) Single sheet reflective insulation materials must be tested with ASTM E408-13, “Standard Test Methods for Total Normal Emittance of Surfaces Using Inspection-Meter Techniques,” or ASTM C1371-15, “Standard Test Method for Determination of Emittance of Materials Near Room Temperature Using Portable Emissometers.” This test determines the emittance of the reflective surfaces—its power to radiate heat. To get the R-value for a specific emittance, air space, and direction of heat flow, use Table 3 in the ASHRAE Handbook, Chapter 26, if the product is intended for applications that meet the conditions specified in the tables. You must use the R-value shown for 50 degrees Fahrenheit, with a temperature difference of 30 degrees Fahrenheit.</P>
                        <P>
                            (c) Reflective insulation systems with more than one sheet, and single sheet 
                            <PRTPAGE P="20789"/>
                            systems that are intended for applications that do not meet the conditions specified in Table 3 in the ASHRAE Handbook, Chapter 26 must be tested with ASTM C1363-11, “Standard Test Method for Thermal Performance of Building Materials and Envelope Assemblies by Means of a Hot Box Apparatus,” in a test panel constructed according to ASTM C1224-15, “Standard Specification for Reflective Insulation for Building Applications,” and under the test conditions specified in ASTM C1224-15. To get the R-value from the results of those tests, use the formula specified in ASTM C1224-15.
                        </P>
                        <P>(d) For insulation materials with reflective facings, you must test the R-value of the material alone (excluding any air spaces) under the methods listed in paragraph (a) of this section. You can also determine the R-value of the material in conjunction with an air space. You can use one of two methods to do this:</P>
                        <P>(1) You can test the system, with its air space, under ASTM C1363-11, “Standard Test Method for Thermal Performance of Building Materials and Envelope Assemblies by Means of a Hot Box Apparatus” If you do this, you must follow the requirements in paragraph (a) of this section on temperature, aging and settled density.</P>
                        <P>(2) You can add up the tested R-value of the material and the R-value of the air space. To get the R-value for the air space, you must follow the requirements in paragraph (b) of this section.</P>
                        <P>
                            (e) The standards required in this section are 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. All approved material is available for inspection at the FTC Library (202-326-2395), Federal Trade Commission, Room H-630, 600 Pennsylvania Avenue NW, Washington, DC 20580 and is available from the sources listed in paragraphs (e)(1) and (2) of this section. It is also available for inspection at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030 or go to 
                            <E T="03">www.archives.gov/federal-register/cfr/ibr-locations.html.</E>
                        </P>
                        <P>
                            (1) ASHRAE Headquarters, 1791 Tullie Circle, NE, Atlanta, GA 30329; telephone (404) 636-8400; 
                            <E T="03">https://www.ashrae.org.</E>
                        </P>
                        <P>(i) 2017 ASHRAE Handbook—Fundamentals, Chapter 26: Heat, Air, and Moisture Control in Building Assemblies—Material Properties, Inch Pound (I-P) Edition (Copyright 2017).</P>
                        <P>(ii) [Reserved]</P>
                        <P>
                            (2) ASTM Int'l, 100 Barr Harbor Drive, P.O. Box C700, West Conshocken, PA 19428-2959, 877-909-2786, 
                            <E T="03">www.astm.org/.</E>
                        </P>
                        <P>(i) ASTM C 177-13, “Standard Test Method for Steady-State Heat Flux Measurements and Thermal Transmission Properties by Means of the Guarded-Hot-Plate Apparatus” (published October 2013).</P>
                        <P>(ii) ASTM C 518-17, “Standard Test Method for Steady-State Thermal Transmission Properties by Means of the Heat Flow Meter Apparatus” (published July 2017).</P>
                        <P>(iii) ASTM C 739-17, “Standard Specification for Cellulosic Fiber Loose-Fill Thermal Insulation” (published August 2017).</P>
                        <P>(iv) ASTM C 1045-07 (Reapproved 2013), “Standard Practice for Calculating Thermal Transmission Properties Under Steady-State Conditions” (published January 2014).</P>
                        <P>(v) ASTM C 1114-06 (Reapproved 2013), “Standard Test Method for Steady-State Thermal Transmission Properties by Means of the Thin-Heater Apparatus” (published January 2014).</P>
                        <P>(vi) ASTM C 1149-17, “Standard Specification for Self-Supported Spray Applied Cellulosic Thermal Insulation” (published October 2017).</P>
                        <P>(vii) ASTM C 1224-15, “Standard Specification for Reflective Insulation for Building Applications” (published November 2015).</P>
                        <P>(viii) ASTM C 1363-11, “Standard Test Method for Thermal Performance of Building Materials and Envelope Assemblies by Means of a Hot Box Apparatus” (published June 2011).</P>
                        <P>(ix) ASTM C 1371-15, “Standard Test Method for Determination of Emittance of Materials Near Room Temperature Using Portable Emissometers” (published June 2015).</P>
                        <P>(x) ASTM C 1374-14, “Standard Test Method for Determination of Installed Thickness of Pneumatically Applied Loose-Fill Building Insulation” (published May 2014).</P>
                        <P>(xi) ASTM E 408-13, “Standard Test Methods for Total Normal Emittance of Surfaces Using Inspection-Meter Techniques” (published June 2013). </P>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 460.6 </SECTNO>
                    <SUBJECT>[Amended] </SUBJECT>
                </SECTION>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>7. In § 460.6, remove the words “aluminum foil” and add in their place the words “reflective insulation.” </AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 460.7 </SECTNO>
                    <SUBJECT>[Removed and Reserved] </SUBJECT>
                </SECTION>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>8. Remove and reserve § 460.7.</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 460.9 </SECTNO>
                    <SUBJECT>[Amended] </SUBJECT>
                </SECTION>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>9. In § 460.9(e), remove the words “aluminum foil” and “emissivity” and add in their place the words “reflective insulation” and “emittance,” respectively. </AMDPAR>
                </REGTEXT>
                  
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>10. In § 460.12, revise paragraphs (b)(4) and (5) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 460.12 </SECTNO>
                        <SUBJECT> Labels.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(4) For reflective insulation: The number of sheets; the number and thickness of the air spaces; and the R-value provided by that system when the direction of heat flow is up, down, and horizontal. You can show the R-value for only one direction of heat flow if you clearly and conspicuously state that the insulation can only be used in that application.</P>
                        <P>(5) For insulation materials with reflective facings, you must follow the rule in this section that applies to the material itself. For example, if you manufacture boardstock with a reflective facing, follow paragraph (b)(3) of this section. You can also show the R-value of the insulation when it is installed in conjunction with an air space. This is its “system R-value.” If you do this, you must clearly and conspicuously state the conditions under which the system R-value can be attained.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>11. In § 460.13:</AMDPAR>
                    <AMDPAR>a. Amend the introductory text by adding the phrase “Each fact sheet must contain these items:” at the end;</AMDPAR>
                    <AMDPAR>b. Remove the undesignated phrase “Each fact sheet must contain these items:” following the introductory text;</AMDPAR>
                    <AMDPAR>c. Revise paragraph (e); and</AMDPAR>
                    <AMDPAR>d. Add paragraph (f).</AMDPAR>
                    <P>The revision and addition read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 460.13 </SECTNO>
                        <SUBJECT>Fact sheets.</SUBJECT>
                        <STARS/>
                        <P>(e) After the chart and any statement dealing with the specific type of insulation, ALL fact sheets must carry this statement, boxed, in 12-point type:</P>
                        <EXTRACT>
                            <HD SOURCE="HD3">READ THIS BEFORE YOU BUY</HD>
                            <HD SOURCE="HD3">What You Should Know About R-values</HD>
                            <P>The chart shows the R-value of this insulation. R means resistance to heat flow. The higher the R-value, the greater the insulating power. Compare insulation R-values before you buy.</P>
                            <P>
                                There are other factors to consider. The amount of insulation you need depends mainly on the climate you live in. Also, your fuel savings from insulation will depend upon the climate, the type and size of your house, the amount of insulation already in your house, your fuel use patterns and family size, proper installation of your insulation, and how tightly your house is sealed against air leaks. If you buy too much insulation, it will cost you more than what you'll save on fuel.
                                <PRTPAGE P="20790"/>
                            </P>
                            <P>To get the marked R-value, it is essential that this insulation be installed properly.</P>
                        </EXTRACT>
                        <P>(f) For R-19 insulation batts, the fact sheet must also disclose the insulation's R-value when installed in wall cavities where the insulation's thickness exceeds the depth of the cavity.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>12. Revise § 460.14 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 460.14 </SECTNO>
                        <SUBJECT> How retailers must handle labels and fact sheets.</SUBJECT>
                        <P>If you sell insulation to do-it-yourself customers, you must have fact sheets for the insulation products you sell. You must make the fact sheets available to your customers, whether you offer insulation products for sale offline or online. You can decide how to do this, as long as your insulation customers are likely to notice them. For example, you can put them in a display, and let customers take copies of them. You can keep them in a binder at a counter or service desk, and have a sign telling customers where the fact sheets are. You need not make the fact sheets available to customers if you display insulation packages on the sales floor where your insulation customers are likely to notice them and each individual insulation package offered for sale contains all package label and fact sheet disclosures required by §§ 460.12 and 460.13. If you are offering products for sale online, the product labels and fact sheets required by this part, or a direct link to this information, must appear clearly and conspicuously and in close proximity to the covered product's price on each web page that contains a detailed description of the covered product and its price.</P>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 460.17 </SECTNO>
                    <SUBJECT>[Amended] </SUBJECT>
                </SECTION>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>13. In § 460.17, remove the words “aluminum foil” and add in their place the words “reflective insulation.” </AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>14. In § 460.18, revise paragraph (e) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 460.18 </SECTNO>
                        <SUBJECT> Insulation ads.</SUBJECT>
                        <STARS/>
                        <P>(e) The affirmative disclosure requirements in this section do not apply to television or radio advertisements or to space-constrained advertisements. For the purposes of this part, “space-constrained advertisement” means any communication made through interactive media (such as the internet, online services, and software, including but not limited to internet search results and banner ads) that has space, format, size or technological limitations or restrictions that prevent industry members from making disclosures required by this part clearly and conspicuously. Industry members maintain the burden of showing that there is insufficient space to provide the disclosures that this part otherwise requires be made clearly and conspicuously.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>15. In § 460.19, revise paragraph (g) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 460.19 </SECTNO>
                        <SUBJECT> Savings claims.</SUBJECT>
                        <STARS/>
                        <P>(g) The affirmative disclosure requirements in this section do not apply to television or radio advertisements or to space-constrained advertisements. “Space-constrained advertisement” is defined in § 460.18(e).</P>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ § 460.22 through 460.24</SECTNO>
                    <SUBJECT> [Redesignated as §§ 460.23 through 460.25]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>16. Redesignate §§ 460.22 through 460.24 as §§ 460.23 through 460.25.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>17. Add a new § 460.22 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 460.22 </SECTNO>
                        <SUBJECT> R-value claims for non-insulation products.</SUBJECT>
                        <P>If you make an R-value claim for a product, other than a fenestration-related product, that is not home insulation and is marketed in whole or in part to reduce residential energy use by slowing heat flow, you must test the product pursuant to § 460.5 using a test or tests in that section appropriate to the product. Any advertised R-value claims must fairly reflect the results of those tests. For the purposes of this section, fenestration-related products include windows, doors, and skylights as well as attachments for those products.</P>
                    </SECTION>
                </REGTEXT>
                <HD SOURCE="HD1">Appendix to Part 460 [Designated as Appendix A to Part 460 and Amended] </HD>
                <REGTEXT TITLE="16" PART="460">
                    <AMDPAR>18. Designate the appendix to part 460 as appendix A to part 460 and amend newly designated appendix A as follows:</AMDPAR>
                    <AMDPAR>a. In the introductory text:</AMDPAR>
                    <AMDPAR>i. Remove “16 CFR part 460” and “part 460” everywhere they appear and add in their place “this part”.</AMDPAR>
                    <AMDPAR>ii. Remove “below” and add in its place “in paragraphs (a) through (d) of this appendix”.</AMDPAR>
                    <AMDPAR>
                        iii. Remove “in the 
                        <E T="04">Federal Register</E>
                         cited at the end of each exemption” and add in its place “cited in the authority citation to this part”.
                    </AMDPAR>
                    <AMDPAR>b. In paragraph (a), remove “46 FR 22179 (1981).”</AMDPAR>
                    <AMDPAR>c. In paragraph (b), remove “46 FR 22180 (1981).”</AMDPAR>
                    <AMDPAR>d. Redesignate paragraphs (c) introductory text and (c)(1) through (4) as paragraphs (c)(1) and (c)(1)(i) through (iv), respectively.</AMDPAR>
                    <AMDPAR>e. Designate the undesignated paragraph following newly designated paragraph (c)(1)(iv) as paragraph (c)(2).</AMDPAR>
                    <AMDPAR>f. In newly designated paragraph (c)(2), remove “48 FR 31192 (1983).”</AMDPAR>
                    <AMDPAR>g. Add paragraph (d).</AMDPAR>
                    <P>The addition reads as follows:</P>
                    <HD SOURCE="HD1">Appendix A to Part 460—Exemptions</HD>
                    <EXTRACT>
                        <STARS/>
                        <P>(d) The requirements in §§ 460.6 through 460.21 do not apply to R-value claims covered by § 460.22. </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <P>By direction of the Commission.</P>
                    <NAME>April J. Tabor,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09622 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6750-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <CFR>26 CFR Part 1</CFR>
                <DEPDOC>[TD 9857]</DEPDOC>
                <RIN>RIN 1545-BL11</RIN>
                <SUBJECT>Recognition and Deferral of Section 987 Gain or Loss</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final regulations and removal of temporary regulations.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document contains final regulations relating to combinations and separations of qualified business units (QBUs) subject to section 987 and the recognition and deferral of foreign currency gain or loss with respect to a QBU subject to section 987 in connection with certain QBU terminations and certain other transactions involving partnerships. In addition, this document withdraws temporary regulations regarding the allocation of assets and liabilities of certain partnerships for purposes of section 987. The final regulations affect taxpayers that own certain QBUs.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P/>
                    <P>
                        <E T="03">Effective date:</E>
                         These regulations are effective on May 13, 2019.
                    </P>
                    <P>
                        <E T="03">Applicability dates:</E>
                         For dates of applicability, see §§ 1.987-2(e), 1.987-4(h), and 1.987-12(j).
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Steven D. Jensen at (202) 317-6938 (not a toll-free number).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    This document contains final regulations under §§ 1.987-2 and 1.987-4 relating to combinations and separations of QBUs subject to section 987. This document also contains final regulations under § 1.987-12 relating to the recognition and deferral of foreign currency gain or loss under section 987 
                    <PRTPAGE P="20791"/>
                    with respect to a QBU subject to section 987 in connection with certain QBU terminations and certain other transactions involving partnerships (together with the final regulations under §§ 1.987-2 and 1.987-4, the final regulations). In addition, this document withdraws temporary regulations under § 1.987-7T regarding the allocation of assets and liabilities of certain partnerships for purposes of section 987.
                </P>
                <HD SOURCE="HD2">I. Background on Section 987 Regulations</HD>
                <P>
                    On December 8, 2016, the Department of the Treasury (Treasury Department) and the Internal Revenue Service (IRS) published Treasury Decision 9794 (the 2016 final regulations) in the 
                    <E T="04">Federal Register</E>
                     (81 FR 88806), which contains rules relating to the determination of the taxable income or loss of a taxpayer with respect to a section 987 QBU; the timing, amount, character, and source of any section 987 gain or loss; and other provisions.
                </P>
                <P>
                    On the same date, the Treasury Department and the IRS also published Treasury Decision 9795 (the temporary regulations) in the 
                    <E T="04">Federal Register</E>
                     (81 FR 88854) and a notice of proposed rulemaking (REG-128276-12) in the 
                    <E T="04">Federal Register</E>
                     (81 FR 88882) by cross-reference to the temporary regulations. The temporary regulations include the following rules that are not specifically affected by this Treasury decision: An annual deemed termination election for a section 987 QBU; an elective method, available to taxpayers that make the annual deemed termination election, for translating all items of income or loss with respect to a section 987 QBU at the yearly average exchange rate; rules regarding the treatment of section 988 transactions of a section 987 QBU; rules regarding QBUs with the U.S. dollar as their functional currency; rules regarding the translation of income used to pay creditable foreign income taxes; and rules under section 988 requiring the deferral of certain section 988 loss that arises with respect to related-party loans.
                </P>
                <P>In addition, the temporary regulations contain the following provisions that are specifically affected by this Treasury decision: §§ 1.987-2T and 1.987-4T, relating to combinations and separations of QBUs; § 1.987-7T, which provides a liquidation value percentage methodology for allocating assets and liabilities of certain partnerships (section 987 aggregate partnerships, as defined in § 1.987-1(b)(5) of the 2016 final regulations); and § 1.987-12T, which requires deferral of foreign currency gain or loss under section 987 with respect to certain transactions defined as deferral events or outbound loss events—transactions that generally include QBU terminations and certain partnerships transactions.</P>
                <P>
                    On January 17, 2017, the Treasury Department and the IRS published Notice 2017-07, 2017-3 I.R.B. 423, announcing that certain rules under § 1.987-12T would be modified to prevent potential abuse by taxpayers making retroactive check-the-box elections. Section 1.987-12T(j)(1) states that § 1.987-12T generally applies to any deferral event or outbound loss event that occurs on or after January 6, 2017 (that is, thirty days after the date that § 1.987-12T was filed with the 
                    <E T="04">Federal Register</E>
                    ). Under § 1.987-12T(j)(2), however, § 1.987-12T also applies to any deferral event or outbound loss event that occurs on or after December 7, 2016, if such deferral event or outbound loss event is undertaken with a principal purpose of recognizing section 987 loss. Notice 2017-07 indicated that § 1.987-12T(j)(2) would be modified so that § 1.987-12T also will apply to any deferral event or outbound loss event that is undertaken with a principal purpose of recognizing section 987 loss 
                    <SU>1</SU>
                    <FTREF/>
                     and that occurs as a result of an entity classification election made under § 301.7701-3 that is filed on or after December 22, 2016, and that is effective before December 7, 2016. Additionally, Notice 2017-07 provided that § 1.987-12T(j)(1) would be modified so that § 1.987-12T also will apply to any deferral event or outbound loss event that occurs as a result of an entity classification election made under § 301.7701-3 that is filed on or after January 6, 2017, and that is effective before January 6, 2017.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Notice 2017-07 inadvertently referred to a principal purpose of recognizing section 987 gain or loss. These final regulations, by contrast, finalize the rule in the temporary regulations by applying § 1.987-12(j)(2) solely to deferral events and outbound loss events undertaken with a principal purpose of recognizing section 987 loss.
                    </P>
                </FTNT>
                <P>
                    On October 16, 2017, the Treasury Department and the IRS issued Notice 2017-57, 2017-42 I.R.B. 325, announcing that future guidance would defer the applicability dates of §§ 1.987-2T, 1.987-4T, and 1.987-7T (along with certain other provisions of the 2016 final regulations and temporary regulations) by one year. The temporary regulations provide that these sections apply to taxable years beginning on or after the day that is one year after the first day of the first taxable year following December 7, 2016. 
                    <E T="03">See</E>
                     §§ 1.987-2T(e); 1.987-4T(h); 1.987-7T(d).
                </P>
                <P>On June 25, 2018, the Treasury Department and the IRS published Notice 2018-57, 2018-26 IRB 774, announcing that future guidance would defer the applicability dates of §§ 1.987-2T, 1.987-4T, and 1.987-7T (along with certain other provisions of the 2016 final regulations and temporary regulations) by one additional year.</P>
                <HD SOURCE="HD2">II. Executive Order 13789</HD>
                <P>Executive Order 13789, issued on April 21, 2017, instructs the Secretary of the Treasury (the Secretary) to review all significant tax regulations issued on or after January 1, 2016, and to take concrete action to alleviate the burdens of regulations that (i) impose an undue financial burden on U.S. taxpayers; (ii) add undue complexity to the Federal tax laws; or (iii) exceed the statutory authority of the IRS. Executive Order 13789 further instructs the Secretary to submit to the President within 60 days an interim report that identifies regulations that meet these criteria. Notice 2017-38, 2017-30 I.R.B. 147, which was published on July 24, 2017, included the 2016 final regulations in a list of eight regulations identified by the Secretary in the interim report as meeting at least one of the first two criteria specified in E.O. 13789.</P>
                <P>
                    E.O. 13789 further instructs the Secretary to submit to the President by September 18, 2017, a final report that recommends specific actions to mitigate the burden imposed by regulations identified in the interim report. On October 16, 2017, the Secretary published in the 
                    <E T="04">Federal Register</E>
                     this final report (82 FR 48013), which indicated, among other things, that the Treasury Department and the IRS intend to propose certain modifications to the 2016 final regulations to reduce burden and compliance challenges associated with those regulations and are actively considering other rules in connection with that proposal.
                </P>
                <HD SOURCE="HD2">III. Deferral of Section 987 Gain or Loss on Certain Terminations and Other Transactions Involving Partnerships</HD>
                <P>Under the 2016 final regulations, the owner of a section 987 QBU that terminates includes in income all of the net unrecognized section 987 gain or loss with respect to the section 987 QBU in the year it terminates. Under these rules, a termination can result, for example, solely from a transfer of a section 987 QBU from a taxpayer to a related party, notwithstanding that the QBU's assets continue to be used in the same trade or business by the related party.</P>
                <P>
                    Because a termination can result in the deemed remittance of all the assets 
                    <PRTPAGE P="20792"/>
                    of a section 987 QBU in circumstances in which the assets continue to be used by a related person in the conduct of the same trade or business that formerly was conducted by the section 987 QBU, terminations can facilitate the selective recognition of section 987 losses. In issuing the temporary regulations, the Treasury Department and the IRS determined that terminations of section 987 QBUs generally should not be permitted to facilitate the selective recognition of losses when the assets and liabilities of the section 987 QBU are transferred to a related person and remain subject to section 987 in the hands of the transferee. Similar policy considerations arise when the transfer of a partnership interest to a related person results in deemed transfers that cause the recognition of section 987 loss with respect to a section 987 QBU owned through the partnership, notwithstanding that the trade or business of the section 987 QBU continues without interruption and remains subject to section 987, and in the context of certain outbound transfers even when the assets do not remain subject to section 987 in the hands of the transferee (because, for example, the transferee has the same functional currency as the QBU). In order to address these policy concerns, the temporary regulations defer section 987 losses resulting from certain termination events, partnership transactions, and certain other transactions involving outbound transfers.
                </P>
                <P>In addition, the temporary regulations generally apply to defer the recognition of section 987 gains as well as losses when the transferee is subject to section 987 with respect to the assets of the section 987 QBU. The temporary regulations do not, however, defer gain to the extent the assets of a section 987 QBU are transferred by a U.S. person to a related foreign person, consistent with the policies underlying section 367.</P>
                <HD SOURCE="HD2">IV. Combinations and Separations of QBUs</HD>
                <P>The temporary regulations also include rules to prevent similarly inappropriate results when certain section 987 QBUs are combined or separated. Absent a special rule, the combination of multiple section 987 QBUs that have the same owner, or the separation of a section 987 QBU into two or more section 987 QBUs that have the same owner, would give rise to a transfer between an owner and one or more section 987 QBUs under the 2016 final regulations.</P>
                <P>Consistent with the policy of deferring section 987 gain or loss under § 1.987-12T when assets of a section 987 QBU are reflected on the books and records of another section 987 QBU in the same controlled group as a result of certain transactions that result in deemed transfers, the temporary regulations provide that section 987 gain or loss generally is not recognized when two or more section 987 QBUs (combining QBUs) with the same owner combine into a single section 987 QBU (combined QBU) or when a section 987 QBU (separating QBU) separates into multiple section 987 QBUs (each, a separated QBU).</P>
                <P>The temporary regulations also include certain mechanical rules applicable in this context, including (i) rules related to determining the net unrecognized section 987 gain or loss of combined QBUs and separated QBUs, and (ii) provisions regarding combining section 987 QBUs that have different functional currencies than their respective combined QBUs.</P>
                <HD SOURCE="HD2">V. Determination of a Partner's Share of Assets and Liabilities of a Section 987 Aggregate Partnership</HD>
                <P>The 2016 final regulations set forth rules applicable to section 987 aggregate partnerships, which are defined as partnerships for which all of the capital and profits interests are owned, directly or indirectly, by persons that are related within the meaning of section 267(b) or section 707(b). Under the aggregate approach set forth in the 2016 final regulations, assets and liabilities reflected on the books and records of an eligible QBU of a section 987 aggregate partnership are allocated to each partner, which is considered an indirect owner of the eligible QBU. If the eligible QBU has a different functional currency than its indirect owner, then the assets and liabilities of the eligible QBU that are allocated to the partner are treated as a section 987 QBU of the indirect owner.</P>
                <P>The temporary regulations provide specific rules for determining a partner's share of the assets and liabilities reflected on the books and records of an eligible QBU owned indirectly through a section 987 aggregate partnership. Specifically, § 1.987-7T(b) provides that, in any taxable year, a partner's share of each asset and liability of a section 987 aggregate partnership is proportional to the partner's liquidation value percentage with respect to the aggregate partnership. A partner's liquidation value percentage is defined as the ratio of the liquidation value of the partner's interest in the partnership to the aggregate liquidation value of all the partners' interests in the partnership. The liquidation value of the partner's interest in the partnership is the amount of cash the partner would receive with respect to its interest if, immediately following the applicable determination date, the partnership sold all of its assets for cash equal to the fair market value of such assets (taking into account section 7701(g)), satisfied all of its liabilities (other than those described in § 1.752-7), paid an unrelated third party to assume all of its § 1.752-7 liabilities in a fully taxable transaction, and then liquidated.</P>
                <HD SOURCE="HD1">Summary of Comments and Explanation of Revisions</HD>
                <P>The Treasury Department and the IRS received one comment regarding the temporary regulations. In addition, the Treasury Department and the IRS received several comments in response to Notice 2017-38 pertaining to the temporary regulations. After consideration of all the comments, the regulations under §§ 1.987-2T, 1.987-4T, and 1.987-12T, as revised by this Treasury decision, are adopted as final regulations. In addition, the regulations under § 1.987-7T are withdrawn. The Treasury Department and the IRS are continuing to study the other provisions of the temporary regulations that are not specifically addressed by this Treasury decision. In addition, several comments were received that relate to rules in the 2016 final regulations. Comments on the 2016 final regulations, and provisions of the temporary regulations that are not specifically addressed by this Treasury decision, are beyond the scope of this rulemaking and are not addressed in this preamble. The Treasury Department and the IRS will consider these comments in connection with any future guidance projects addressing the issues discussed in the comments.</P>
                <HD SOURCE="HD2">I. Comments Recommending Withdrawal of the Temporary Regulations</HD>
                <P>A number of comments recommended that all of the temporary regulations, including §§ 1.987-2T, 1.987-4T, and 1.987-12T, be withdrawn. Comments generally indicated that the 2016 final regulations and the temporary regulations are unduly complex and present significant financial and compliance burdens for taxpayers subject to the 2016 final regulations.</P>
                <P>
                    As described in the Background section of this Preamble, in its final report to the President in response to E.O. 13789, the Treasury Department indicated that the 2016 final regulations have proved difficult to apply for many taxpayers. The final report indicated that the Treasury Department and the IRS intend to propose modifications to the 2016 final regulations that will 
                    <PRTPAGE P="20793"/>
                    reduce the compliance burdens associated with the regulations. While the Treasury Department and the IRS intend to reduce those burdens as described in the final report, the Treasury Department and the IRS continue to consider it inappropriate to permit the selective recognition of section 987 losses and the deferral of section 987 gains. This is particularly true when such selective loss recognition may be accomplished through related-party transactions that do not significantly impact the conduct of the trade or business of a section 987 QBU or its owner but nonetheless generate significant tax benefits, as is true of deferral events and outbound loss events.
                </P>
                <P>Accordingly, the Treasury Department and the IRS have determined that finalizing §§ 1.987-2T, 1.987-4T, and 1.987-12T, while simultaneously deferring the applicability date of the 2016 final regulations and developing guidance to mitigate the complexity and administrative challenges associated with, the 2016 final regulations, appropriately balances taxpayers' burdens with the need to prevent abuse under the 2016 final regulations or under another method of complying with section 987 utilized by a taxpayer during a period for which the 2016 final regulations are not applicable. Accordingly, this Treasury decision finalizes the rules in §§ 1.987-2T, 1.987-4T, and 1.987-12T with certain clarifications.</P>
                <HD SOURCE="HD2">II. Comments Recommending a Delay of the Applicability Date of the Temporary Regulations</HD>
                <P>Comments recommended that the applicability date for the 2016 final regulations and the temporary regulations, including §§ 1.987-2T, 1.987-4T, and 1.987-12T, be delayed for a specified period, such as one or two years. Similarly, comments recommended that the final and temporary regulations, including §§ 1.987-2T, 1.987-4T, and 1.987-12T, be withdrawn in their entirety and reproposed (in one case, with an effective date at least two years after such regulations are finalized) to allow taxpayers time to effectively plan to implement the final and temporary regulations. Generally, the comments indicated that taxpayers required additional time to update and implement existing systems to comply with the 2016 final regulations and the temporary regulations. One comment specifically recommended that the applicability date for § 1.987-12T be delayed until the applicability date of the 2016 final regulations. The comment indicated that, in certain instances, the applicability date of § 1.987-12T prevented the recognition of losses in connection with certain transactions that were in the planning and implementation stages when the temporary regulations were issued. No comments identified specific compliance challenges associated with § 1.987-12T.</P>
                <P>The Treasury Department and the IRS decline to delay the applicability date of § 1.987-12T. As discussed in Part I of this Summary of Comments and Explanation of Revisions, § 1.987-12T prevents taxpayers from selectively recognizing section 987 losses through certain technical terminations of a section 987 QBU and similar transactions that would be relatively easy to effect through related-party transactions without meaningfully impacting a taxpayer's business operations. If the applicability date were delayed, taxpayers would be incentivized to engage in such selective recognition of section 987 losses, which would be contrary to the purposes of section 987 and § 1.987-12T. Delaying the application of related provisions under §§ 1.987-2T and 1.987-4T concerning combinations and separations of a section 987 QBU could similarly incentivize transactions designed to accelerate section 987 losses for taxpayers that have elected to apply the 2016 final regulations early. In this regard, the Treasury Department and the IRS observe that the transactions to which §§ 1.987-2T, 1.987-4T, and 1.987-12T are applicable occur exclusively among related persons, such that taxpayers may avoid the application of those sections by avoiding undertaking such transactions.</P>
                <P>Accordingly, the final regulations retain the applicability dates of the temporary regulations, as modified by Notice 2017-07, Notice 2017-57, and Notice 2018-57. Specifically, the final regulations provide that §§ 1.987-2(c)(9), 1.987-4(c)(2), and 1.987-4(f) apply to taxable years beginning on or after the day that is three years after the first day of the first taxable year following December 7, 2016. If, however, a taxpayer makes an election under § 1.987-11(b), then §§ 1.987-2(c)(9), 1.987-4(c)(2), and 1.987-4(f) apply to taxable years to which §§ 1.987-1 through 1.987-10 apply as a result of such election.</P>
                <P>Similarly, § 1.987-12 incorporates the applicability date provisions of § 1.987-12T, as modified by Notice 2017-07. Thus, the final regulations under § 1.987-12 generally apply to any deferral event or outbound loss event that occurs on or after January 6, 2017. Section 1.987-12 also applies to any deferral event or outbound loss event that occurs as a result of an entity classification election made under § 301.7701-3 that is filed on or after January 6, 2017, and that is effective before January 6, 2017. However, § 1.987-12 applies to any deferral event or outbound loss event occurring on or after December 7, 2016, if such deferral event or outbound loss event was undertaken with a principal purpose of recognizing section 987 loss. Similarly, § 1.987-12 applies to any deferral event or outbound loss event that occurs as a result of an entity classification election made under § 301.7701-3 that was filed on or after December 22, 2016, that was effective before December 7, 2016, and that was undertaken with a principal purpose of recognizing section 987 loss.</P>
                <HD SOURCE="HD2">III. Comments Regarding the Determination of a Partner's Share of Assets and Liabilities of a Section 987 Aggregate Partnership</HD>
                <P>Comments recommended alternative approaches for determining a partner's share of the assets and liabilities of a section 987 aggregate partnership. Comments recommended that § 1.987-7 be withdrawn and replaced with the approach of the 2006 proposed regulations under section 987, which provided that a partner's share of assets and liabilities reflected on the books and records of an eligible QBU held indirectly through the partnership must be determined in a manner consistent with how the partners have agreed to share the economic benefits and burdens corresponding to those partnership assets and liabilities, taking into account the rules and principles of subchapter K. The comment indicated that that the liquidation value percentage approach was inconsistent with certain principles of subchapter K, resulting in distortions in the calculation of section 987 gain or loss in certain cases.</P>
                <P>
                    The Treasury Department and the IRS have determined that, in the absence of a more comprehensive set of rules for determining a partner's share of assets and liabilities reflected on the books and records of an eligible QBU held indirectly through the partnership that also articulates the interaction of those rules with applicable rules in subchapter K, a more flexible approach is warranted. Moreover, the Treasury Department and the IRS have determined that, in certain instances, the liquidation value percentage methodology set forth in § 1.987-7T may be interpreted as applying in a way that inappropriately distorts the computation of section 987 gain or loss. 
                    <PRTPAGE P="20794"/>
                    Specifically, under such an interpretation, certain changes in a partner's liquidation value percentage may introduce distortions in the calculation of net unrecognized section 987 gain or loss under § 1.987-4, giving rise to net unrecognized section 987 gain or loss that is not attributable to fluctuations in exchange rates. For example, an appreciation or depreciation in property value can result in a change in liquidation value percentage that causes a change in owner functional currency net value for purposes of Step 1 of the § 1.987-4(d) calculation of unrecognized section 987 gain or loss for a taxable year without an offsetting adjustment under Step 6 or otherwise that would prevent the change in liquidation value percentage from distorting the calculation of unrecognized section 987 gain or loss. As a result, such unrecognized appreciation or depreciation generally can result in unrecognized section 987 gain or loss for a taxable year being allocated to each partner that indirectly owns a section 987 QBU even when there is no change in exchange rates.
                </P>
                <P>Accordingly, the Treasury Department and the IRS are withdrawing § 1.987-7T (and making a conforming change to an example in § 1.987-12). Until new regulations are proposed and finalized, taxpayers may use any reasonable method for determining a partner's share of assets and liabilities reflected on the books and records of an eligible QBU held indirectly through the partnership. For this purpose, taxpayers may rely on subchapter K principles (consistent with the 2006 proposed regulations under section 987) or an approach similar to the liquidation value percentage method set forth in § 1.987-7T. However, the Treasury Department and the IRS do not believe that it would be reasonable to apply the liquidation value percentage method without corresponding adjustments to the determination of net unrecognized section 987 gain or loss. Thus, for example, a taxpayer using the liquidation value percentage method may be required to adjust its determination of net unrecognized section 987 gain or loss of a section 987 QBU that is owned indirectly through a partnership to prevent the determination of unrecognized section 987 gain or loss that is not attributable to fluctuations in exchange rates. These adjustments may include, for example, treating any change in a partner's owner functional currency net value that is attributable to a change in the partner's liquidation value percentage as resulting in a transfer to or from an indirectly owned section 987 QBU.</P>
                <HD SOURCE="HD1">Special Analyses</HD>
                <HD SOURCE="HD2">I. Regulatory Planning and Review—Economic Analysis</HD>
                <P>Executive Orders 13563 and 12866 direct agencies to assess 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.</P>
                <P>This regulation is not subject to review under section 6(b) of Executive Order 12866 pursuant to the Memorandum of Agreement (April 11, 2018) between the Department of the Treasury and the Office of Management and Budget regarding review of tax regulations. Therefore, a regulatory impact assessment is not required.</P>
                <HD SOURCE="HD2">II. Paperwork Reduction Act</HD>
                <P>This regulation does not establish a new collection of information nor modify an existing collection that requires the approval of the Office of Management and Budget under the Paperwork Reduction Act (44 U.S.C. chapter 35).</P>
                <HD SOURCE="HD2">III. Regulatory Flexibility Act</HD>
                <P>It is hereby certified that these regulations will not have a significant economic impact on a substantial number of small entities within the meaning of section 601(6) of the Regulatory Flexibility Act (5 U.S.C. chapter 6). Accordingly, a regulatory flexibility analysis is not required. This certification is based on the fact that these regulations will primarily affect U.S. corporations that have foreign operations, which tend to be larger businesses. Accordingly, a regulatory flexibility analysis under the Regulatory Flexibility Act is not required.</P>
                <P>Pursuant to section 7805(f), the notice of proposed rulemaking preceding this regulation was submitted to the Chief Counsel for Advocacy of the Small Business Administration for comment on its impact on small businesses. No comments were received.</P>
                <HD SOURCE="HD2">IV. Unfunded Mandates Reform Act</HD>
                <P>Section 202 of the Unfunded Mandates Reform Act of 1995 requires that agencies assess anticipated costs and benefits and take certain other actions before issuing a final rule that includes any Federal mandate that may result in expenditures in any one year by a state, local, or tribal government, in the aggregate, or by the private sector, of $100 million in 1995 dollars, updated annually for inflation. In 2018, that threshold is approximately $150 million. This rule does not include any Federal mandate that may result in expenditures by state, local, or tribal governments, or by the private sector in excess of that threshold.</P>
                <HD SOURCE="HD2">V. Executive Order 13132: Federalism</HD>
                <P>Executive Order 13132 (entitled “Federalism”) prohibits an agency from publishing any rule that has federalism implications if the rule either imposes substantial, direct compliance costs on state and local governments, and is not required by statute, or preempts state law, unless the agency meets the consultation and funding requirements of section 6 of the Executive Order. This proposed rule does not have federalism implications, does not impose substantial direct compliance costs on state and local governments, and does not preempt state law within the meaning of the Executive Order.</P>
                <HD SOURCE="HD1">Drafting Information</HD>
                <P>The principal author of these final regulations is Steven D. Jensen of the Office of Associate Chief Counsel (International). However, other personnel from the IRS and the Treasury Department participated in their development.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 26 CFR Part 1</HD>
                    <P>Income taxes, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Adoption of Amendments to the Regulations</HD>
                <P>Accordingly, 26 CFR part 1 is amended as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1—INCOME TAXES</HD>
                </PART>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Paragraph 1.</E>
                         The authority citation for part 1 is amended by adding an entry for § 1.987-12 in numerical order to read in part as follows:
                    </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>26 U.S.C. 7805 * * *</P>
                    </AUTH>
                    <STARS/>
                    <EXTRACT>
                        <P>Section 1.987-12 is issued under 26 U.S.C. 987 and 989.</P>
                    </EXTRACT>
                    <STARS/>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 2.</E>
                         Section 1.987-0 is amended by:
                    </AMDPAR>
                    <AMDPAR>
                        1. Revising the entries for § 1.987-2(c)(9), § 1.987-4(c)(2), (f), § 1.987-12(a), (a)(1), (a)(2), (a)(3), (b), (b)(1), (b)(2), (b)(3), (b)(4), (c), (c)(1), (c)(2), (c)(3), (c)(4), (d), (d)(1), (d)(2), (d)(3), (d)(4), (d)(5), (e), (e)(1), (e)(2), (f), (f)(1), (f)(2), (g), and (h).
                        <PRTPAGE P="20795"/>
                    </AMDPAR>
                    <AMDPAR>2. Adding entries for § 1.987-2(e), (e)(1), (e)(2), § 1.987-4(f)(1), (f)(2), (f)(3), (h), (h)(1), (h)(2), § 1.987-12(i), (i)(1), (i)(2), (i)(3), (j), (j)(1), and (j)(2).</AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1.987-0 </SECTNO>
                        <SUBJECT>Table of contents.</SUBJECT>
                        <STARS/>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="03">§ 1.987-2 Attribution of items to eligible QBUs; definition of a transfer and related rules.</E>
                            </FP>
                            <STARS/>
                            <P>(c)(9) Certain disregarded transactions not treated as transfers.</P>
                            <STARS/>
                            <P>(e) Effective/applicability date.</P>
                            <P>(1) In general.</P>
                            <P>(2) Certain disregarded transactions not treated as transfers.</P>
                            <STARS/>
                            <FP SOURCE="FP-2">
                                <E T="03">§ 1.987-4 Determination of net unrecognized section 987 gain or loss of a section 987 QBU.</E>
                            </FP>
                            <STARS/>
                            <P>(c)(2) Coordination with § 1.987-12.</P>
                            <STARS/>
                            <P>(f) Combinations and separations.</P>
                            <P>(1) Combinations.</P>
                            <P>(2) Separations.</P>
                            <P>(3) Examples.</P>
                            <STARS/>
                            <P>(h) Effective/applicability date.</P>
                            <P>(1) In general.</P>
                            <P>(2) Combinations and separations.</P>
                            <STARS/>
                            <FP SOURCE="FP-2">
                                <E T="03">§ 1.987-12 Deferral of section 987 gain or loss.</E>
                            </FP>
                            <P>(a) In general.</P>
                            <P>(1) Overview.</P>
                            <P>(2) Scope.</P>
                            <P>(3) Exceptions.</P>
                            <P>(b) Gain or loss recognition in connection with a deferral event.</P>
                            <P>(1) In general.</P>
                            <P>(2) Deferral event.</P>
                            <P>(3) Gain or loss recognized under § 1.987-5 in the taxable year of a deferral event.</P>
                            <P>(4) Successor QBU.</P>
                            <P>(c) Recognition of deferred section 987 gain or loss in the taxable year of a deferral event and in subsequent taxable years.</P>
                            <P>(1) In general.</P>
                            <P>(2) Recognition upon a subsequent remittance.</P>
                            <P>(3) Recognition of deferred section 987 loss in certain outbound successor QBU terminations.</P>
                            <P>(4) Special rules regarding successor QBUs.</P>
                            <P>(d) Loss recognition upon an outbound loss event.</P>
                            <P>(1) In general.</P>
                            <P>(2) Outbound loss event.</P>
                            <P>(3) Loss recognized upon an outbound loss event.</P>
                            <P>(4) Adjustment of basis of stock received in certain nonrecognition transactions.</P>
                            <P>(5) Recognition of outbound section 987 loss that is not converted into stock basis.</P>
                            <P>(e) Source and character.</P>
                            <P>(1) Deferred section 987 gain or loss and certain outbound section 987 loss.</P>
                            <P>(2) Outbound section 987 loss reflected in stock basis.</P>
                            <P>(f) Definitions.</P>
                            <P>(1) Controlled group.</P>
                            <P>(2) Qualified successor.</P>
                            <P>(g) Anti-abuse.</P>
                            <P>(h) Examples.</P>
                            <P>(i) Coordination with fresh start transition method.</P>
                            <P>(1) In general.</P>
                            <P>(2) Adjustment to deferred section 987 gain or loss.</P>
                            <P>(3) Adjustments in the case of an outbound loss event.</P>
                            <P>(j) Effective/applicability date.</P>
                            <P>(1) In general.</P>
                            <P>(2) Exceptions.</P>
                        </EXTRACT>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 3.</E>
                         Section 1.987-2 is amended by
                    </AMDPAR>
                    <AMDPAR>1. Revising paragraphs (c)(9).</AMDPAR>
                    <AMDPAR>2. Adding paragraph (e).</AMDPAR>
                    <P>The revision and addition read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1.987-2 </SECTNO>
                        <SUBJECT>Attribution of items to eligible QBUs; definition of a transfer and related rules.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>
                            (9) 
                            <E T="03">Certain disregarded transactions not treated as transfers</E>
                            —(i) 
                            <E T="03">Combinations of section 987 QBUs.</E>
                             The combination of two or more separate section 987 QBUs (combining QBUs) that are directly owned by the same owner, or that are indirectly owned by the same partner through a single section 987 aggregate partnership, into one section 987 QBU (combined QBU) does not give rise to a transfer of any combining QBU's assets or liabilities to the owner under § 1.987-2(c). In addition, transactions between the combining QBUs occurring in the taxable year of the combination do not result in a transfer of the combining QBUs' assets or liabilities to the owner under § 1.987-2(c). For this purpose, a combination occurs when the assets and liabilities that are properly reflected on the books and records of two or more combining QBUs begin to be properly reflected on the books and records of a combined QBU and the separate existence of the combining QBUs ceases. A combination may result from any transaction or series of transactions in which the combining QBUs become a combined QBU. For rules regarding the determination of net unrecognized section 987 gain or loss of a combined QBU, see § 1.987-4(f)(1).
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Change in functional currency from a combination.</E>
                             If, following a combination of section 987 QBUs described in paragraph (c)(9)(i) of this section, the combined section 987 QBU has a different functional currency than one or more of the combining section 987 QBUs, any such combining section 987 QBU is treated as changing its functional currency and the owner of the combined section 987 QBU must comply with the regulations under section 985 regarding the change in functional currency. See §§ 1.985-1(c)(6) and 1.985-5.
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Separation of section 987 QBUs.</E>
                             The separation of a section 987 QBU (separating QBU) into two or more section 987 QBUs (separated QBUs) that, after the separation, are directly owned by the same owner, or that are indirectly owned by the same partner through a single section 987 aggregate partnership, does not result in a transfer of the separating QBU's assets or liabilities to the owner under § 1.987-2(c). Additionally, transactions that occurred between the separating QBUs in the taxable year of the separation prior to the completion of the separation do not result in transfers for purposes of section 987. For this purpose, a separation occurs when the assets and liabilities that are properly reflected on the books and records of a separating QBU begin to be properly reflected on the books and records of two or more separated QBUs. A separation may result from any transaction or series of transactions in which a separating QBU becomes two or more separated QBUs. A separation may also result when a section 987 QBU that is subject to a grouping election under § 1.987-1(b)(2)(ii)(A) changes its functional currency. For rules regarding the determination of net unrecognized section 987 gain or loss of a separated QBU, see § 1.987-4(f)(2).
                        </P>
                        <STARS/>
                        <P>
                            (e) 
                            <E T="03">Effective/applicability date</E>
                            —(1) 
                            <E T="03">In general.</E>
                             Except as set forth in paragraph (h)(2) of this section, this section is applicable as specified in § 1.987-11.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Certain disregarded transactions not treated as transfers.</E>
                             Paragraph (c)(9) of this section applies to taxable years beginning on or after the day that is three years after the first day of the first taxable year following December 7, 2016. Notwithstanding the preceding sentence, if a taxpayer makes an election under § 1.987-11(b), then paragraph (c)(9) of this section applies to taxable years to which §§ 1.987-1 through 1.987-10 apply as a result of such election.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1.987-2T</SECTNO>
                    <SUBJECT> [Removed]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 4.</E>
                         Section 1.987-2T is removed. 
                    </AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 5.</E>
                         Section 1.987-4 is amended by
                    </AMDPAR>
                    <AMDPAR>1. Revising paragraphs (c)(2) and (f).</AMDPAR>
                    <AMDPAR>2. Adding paragraph (h).</AMDPAR>
                    <P>The revisions and addition read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1.987-4 </SECTNO>
                        <SUBJECT>Determination of net unrecognized section 987 gain or loss of a section 987 QBU.</SUBJECT>
                        <STARS/>
                        <PRTPAGE P="20796"/>
                        <P>(c) * * *</P>
                        <P>
                            (2) 
                            <E T="03">Coordination with § 1.987-12.</E>
                             For purposes of paragraph (c)(1) of this section, amounts taken into account under § 1.987-5 are determined without regard to § 1.987-12.
                        </P>
                        <STARS/>
                        <P>
                            (f) 
                            <E T="03">Combinations and separations</E>
                            —(1) 
                            <E T="03">Combinations.</E>
                             The net unrecognized section 987 gain or loss of a combined QBU (as defined in § 1.987-2(c)(9)(i)) for a taxable year is determined under paragraph (b) of this section by taking into account the net accumulated unrecognized section 987 gain or loss of each combining QBU (as defined in § 1.987-2(c)(9)(i)) for all prior taxable years to which the regulations under section 987 apply, as determined under paragraph (c) of this section, and by treating the combining QBUs as having combined immediately prior to the beginning of the taxable year of combination. See paragraph (f)(3) of this section, 
                            <E T="03">Example 1,</E>
                             for an illustration of this rule.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Separations.</E>
                             The net unrecognized section 987 gain or loss of a separated QBU (as defined in § 1.987-2(c)(9)(iii)) for a taxable year is determined under paragraph (b) of this section by taking into account the separated QBU's share of the net accumulated unrecognized section 987 gain or loss of the separating QBU (as defined in § 1.987-2(c)(9)(iii)) for all prior taxable years to which the regulations under section 987 apply, as determined under paragraph (c) of this section, and by treating the separating QBU as having separated immediately prior to the beginning of the taxable year of separation. A separated QBU's share of the separating QBU's net accumulated unrecognized section 987 gain or loss for all such prior taxable years is determined by apportioning the separating QBU's net accumulated unrecognized section 987 gain or loss for all such prior taxable years to each separated QBU in proportion to the aggregate adjusted basis of the gross assets properly reflected on the books and records of each separated QBU immediately after the separation. For purposes of determining the owner functional currency net value of the separated QBUs on the last day of the taxable year preceding the taxable year of separation under § 1.987-5(d)(1)(B) and (e), the balance sheets of the separated QBUs on that day will be deemed to reflect the assets and liabilities reflected on the balance sheet of the separating QBU on that day, apportioned between the separated QBUs in a reasonable manner that takes into account the assets and liabilities reflected on the balance sheets of the separated QBUs immediately after the separation. See paragraph (f)(3) of this section, 
                            <E T="03">Example 2,</E>
                             for an illustration of this rule.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Examples.</E>
                             The following examples illustrate the rules of paragraphs (f)(1) and (2) of this section.
                        </P>
                        <EXAMPLE>
                            <HD SOURCE="HED">(i) Example 1.</HD>
                            <P>
                                <E T="03">Combination of two section 987 QBUs that have the same owner.</E>
                                 (A) 
                                <E T="03">Facts.</E>
                                 DC1, a domestic corporation, owns Entity A, a DE. Entity A conducts a business in France that constitutes a section 987 QBU (French QBU) that has the euro as its functional currency. French QBU has a net accumulated unrecognized section 987 loss from all prior taxable years to which the regulations under section 987 apply of $100. DC1 also owns Entity B, a DE. Entity B conducts a business in Germany that constitutes a section 987 QBU (German QBU) that has the euro as its functional currency. German QBU has a net accumulated unrecognized section 987 gain from all prior taxable years to which the regulations under section 987 apply of $110. During the taxable year, Entity A and Entity B merge under local law. As a result, the books and records of French QBU and German QBU are combined into a new single set of books and records. The combined entity has the euro as its functional currency.
                            </P>
                            <P>
                                (B) 
                                <E T="03">Analysis.</E>
                                 Pursuant to § 1.987-2(c)(9)(i), French QBU and German QBU are combining QBUs, and their combination does not give rise to a transfer that is taken into account in determining the amount of a remittance (as defined in § 1.987-5(c)). For purposes of computing net unrecognized section 987 gain or loss under this section for the year of the combination, the combination is deemed to have occurred on the last day of the owner's prior taxable year, such that the owner functional currency net value of the combined section 987 QBU at the end of that taxable year described under paragraph (d)(1)(B) of this section takes into account items reflected on the balance sheets of both French QBU and German QBU at that time. Additionally, any transactions between French QBU and German QBU occurring during the year of the merger will not result in transfers to or from a section 987 QBU. Pursuant to paragraph (f)(1) of this section, the combined QBU will have a net accumulated unrecognized section 987 gain from all prior taxable years of $10 (the $100 loss from French QBU plus the $110 gain from German QBU).
                            </P>
                        </EXAMPLE>
                        <EXAMPLE>
                            <HD SOURCE="HED">(ii) Example 2.</HD>
                            <P>
                                <E T="03">Separation of two section 987 QBUs that have the same owner.</E>
                                 (A) 
                                <E T="03">Facts.</E>
                                 DC1, a domestic corporation, owns Entity A, a DE. Entity A conducts a business in the Netherlands that constitutes a section 987 QBU (Dutch QBU) that has the euro as its functional currency. The business of Dutch QBU consists of manufacturing and selling bicycles and scooters and is recorded on a single set of books and records. On the last day of Year 1, the adjusted basis of the gross assets of Dutch QBU is €1,000. In Year 2, the net accumulated unrecognized section 987 loss of Dutch QBU from all prior taxable years is $200. During Year 2, Entity A separates the bicycle and scooter business such that each business begins to have its own books and records and to meet the definition of a section 987 QBU under § 1.987-1(b)(2) (hereafter, “bicycle QBU” and “scooter QBU”). There are no transfers between DC1 and Dutch QBU before the separation. After the separation, the aggregate adjusted basis of bicycle QBU's assets is €600 and the aggregate adjusted basis of scooter QBU's assets is €400. Each section 987 QBU continues to have the euro as its functional currency.
                            </P>
                            <P>
                                (B) 
                                <E T="03">Analysis.</E>
                                 Pursuant to § 1.987-2(c)(9)(iii), bicycle QBU and scooter QBU are separated QBUs, and the separation of Dutch QBU, a separating QBU, does not give rise to a transfer taken into account in determining the amount of a remittance (as defined in § 1.987-5(c)). For purposes of computing net unrecognized section 987 gain or loss under this section for Year 2, the separation will be deemed to have occurred on the last day of the owner's prior taxable year, Year 1. Pursuant to paragraph (f)(2) of this section, bicycle QBU will have a net accumulated unrecognized section 987 loss of $120 (€600/€1,000 × $200), and scooter QBU will have a net accumulated unrecognized section 987 loss of $80 (€400/€1,000 × $200).
                            </P>
                            <STARS/>
                        </EXAMPLE>
                        <P>
                            (h) 
                            <E T="03">Effective/applicability date</E>
                            —(1) 
                            <E T="03">In general.</E>
                             Except as set forth in paragraph (h)(2) of this section, this section is applicable as specified in § 1.987-11.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Combinations and separations.</E>
                             Paragraphs (c)(2) and (f) of this section apply to taxable years beginning on or after the day that is three years after the first day of the first taxable year following December 7, 2016. Notwithstanding the preceding sentence, if a taxpayer makes an election under § 1.987-11(b), then paragraphs (c)(2) and (f) of this section applies to taxable years to which §§ 1.987-1 through 1.987-10 apply as a result of such election.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1.987-4T</SECTNO>
                    <SUBJECT> [Removed]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 6.</E>
                         Section 1.987-4T is removed.
                    </AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1.987-7</SECTNO>
                    <SUBJECT> [Amended]  </SUBJECT>
                </SECTION>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 7.</E>
                         Section 1.987-7 is amended by removing and reserving paragraph (b).
                    </AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1.987-7T </SECTNO>
                    <SUBJECT> [Removed]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 8.</E>
                         Section 1.987-7T is removed.
                    </AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 9.</E>
                         Section 1.987-12 is revised to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.987-12</SECTNO>
                        <SUBJECT> Deferral of section 987 gain or loss.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">In general</E>
                            —(1) 
                            <E T="03">Overview.</E>
                             This section provides rules that defer the recognition of section 987 gain or loss that, but for this section, would be recognized in connection with certain QBU terminations and certain other transactions involving partnerships. This paragraph (a) provides an overview of this section and describes the section's scope of application, including 
                            <PRTPAGE P="20797"/>
                            with respect to QBUs subject to section 987 but to which §§ 1.987-1 through 1.987-11 generally do not apply. Paragraph (b) of this section describes the extent to which section 987 gain or loss is recognized under § 1.987-5 or similar principles in the taxable year of a deferral event (as defined in paragraph (b)(2) of this section) with respect to a QBU. Paragraph (c) of this section describes the extent to which section 987 gain or loss that, as a result of paragraph (b), is not recognized under § 1.987-5 or similar principles is recognized upon the occurrence of subsequent events. Paragraph (d) of this section describes the extent to which section 987 loss is recognized under § 1.987-5 or similar principles in the taxable year of an outbound loss event (as defined in paragraph (d)(2) of this section) with respect to a QBU. Paragraph (e) of this section provides rules for determining the source and character of gains and losses that, as a result of this section, are not recognized under § 1.987-5 or similar principles in the taxable year of a deferral event or outbound loss event. Paragraph (f) of this section defines controlled group and qualified successor for purposes of this section. Paragraph (g) of this section provides an anti-abuse rule. Paragraph (h) of this section provides examples illustrating the rules described in this section. Paragraph (i) of this section provides rules coordinating the application of this section with the fresh start transition method. Paragraph (j) of this section provides dates of applicability.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Scope.</E>
                             This section applies to any foreign currency gain or loss realized under section 987(3), including foreign currency gain or loss of an entity described in § 1.987-1(b)(1)(ii) (certain entities not otherwise subject to the regulations under section 987). References in this section to section 987 gain or loss refer to any foreign currency gain or loss realized under section 987(3), references to a section 987 QBU refer to any eligible QBU (as defined in § 1.987-1(b)(3)(i), but without regard to § 1.987-1(b)(3)(ii)) that is subject to section 987, and references to a section 987 aggregate partnership refer to any partnership for which the acquisition or disposition of a partnership interest could give rise to foreign currency gain or loss realized under section 987(3). Additionally, references to recognition of section 987 gain or loss under § 1.987-5 encompass any determination and recognition of gain or loss under section 987(3) that would occur but for this section. Accordingly, the principles of this section apply to a QBU subject to section 987 regardless of whether the QBU otherwise is subject to §§ 1.987-1 through 1.987-11. An owner of a QBU that is not subject to § 1.987-5 must adapt the rules set forth in this section as necessary to recognize section 987 gains or losses that are subject to this section consistent with the principles of this section.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Exceptions</E>
                            —(i) 
                            <E T="03">Annual deemed termination elections.</E>
                             This section does not apply to section 987 gain or loss of a section 987 QBU with respect to which the annual deemed termination election described in § 1.987-8(d) is in effect.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">De minimis exception.</E>
                             This section does not apply to a section 987 QBU for a taxable year if the net unrecognized section 987 gain or loss of the section 987 QBU that, as a result of this section, would not be recognized under § 1.987-5 in the taxable year does not exceed $5 million.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Gain and loss recognition in connection with a deferral event</E>
                            —(1) 
                            <E T="03">In general.</E>
                             Notwithstanding § 1.987-5, the owner of a section 987 QBU with respect to which a deferral event occurs (a deferral QBU) includes in taxable income section 987 gain or loss in connection with the deferral event only to the extent provided in paragraphs (b)(3) and (c) of this section. However, if the deferral event also constitutes an outbound loss event described in paragraph (d) of this section, the amount of loss recognized by the owner may be further limited under that paragraph.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Deferral event</E>
                            —(i) 
                            <E T="03">In general.</E>
                             A deferral event with respect to a section 987 QBU means any transaction or series of transactions that satisfy the conditions described in paragraphs (b)(2)(ii) and (iii) of this section.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Transactions.</E>
                             The transaction or series of transactions include either:
                        </P>
                        <P>(A) A termination of the section 987 QBU other than any of the following terminations: A termination described in § 1.987-8(b)(3), a termination described in § 1.987-8(c), or a termination described solely in § 1.987-8(b)(1); or</P>
                        <P>
                            (B) A disposition of part of an interest in a section 987 aggregate partnership or DE through which the section 987 QBU is owned, a disposition of part of a directly held section 987 QBU, or any contribution by another person to a section 987 aggregate partnership, DE, or section 987 QBU of assets that, immediately after the contribution, are not considered to be included on the books and records of an eligible QBU, provided that the contribution gives rise to a deemed transfer from the section 987 QBU to the owner. See paragraph (h) of this section, 
                            <E T="03">Examples 1, 2,</E>
                             and 
                            <E T="03">4,</E>
                             for illustrations of this rule.
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Assets on books of successor QBU.</E>
                             Immediately after the transaction or series of transactions, assets of the section 987 QBU are reflected on the books and records of a successor QBU (as defined in paragraph (b)(4) of this section).
                        </P>
                        <P>
                            (3) 
                            <E T="03">Gain or loss recognized under § 1.987-5 in the taxable year of a deferral event.</E>
                             In the taxable year of a deferral event with respect to a deferral QBU, the owner of the deferral QBU recognizes section 987 gain or loss as determined under § 1.987-5, except that, solely for purposes of applying § 1.987-5, all assets and liabilities of the deferral QBU that, immediately after the deferral event, are reflected on the books and records of a successor QBU are treated as not having been transferred and therefore as remaining on the books and records of the deferral QBU notwithstanding the deferral event.
                        </P>
                        <P>
                            (4) 
                            <E T="03">Successor QBU.</E>
                             For purposes of this section, a section 987 QBU (potential successor QBU) is a successor QBU with respect to a section 987 QBU referred to in paragraph (b)(2)(ii) of this section if, immediately after the transaction or series of transactions described in that paragraph, the potential successor QBU satisfies all of the conditions described in paragraphs (b)(4)(i) through (iii) of this section.
                        </P>
                        <P>(i) The books and records of the potential successor QBU reflect assets that, immediately before the transaction or series of transactions described in paragraph (b)(2)(ii) of this section, were reflected on the books and records of the section 987 QBU referred to in that paragraph.</P>
                        <P>(ii) The owner of the potential successor QBU and the owner of the section 987 QBU referred to in paragraph (b)(2)(ii) of this section immediately before the transaction or series of transactions described in that paragraph are members of the same controlled group.</P>
                        <P>(iii) In the case of a section 987 QBU referred to in paragraph (b)(2)(ii)(A) of this section, if the owner of the section 987 QBU immediately before the transaction or series of transactions described in that paragraph was a U.S. person, the potential successor QBU is owned by a U.S. person.</P>
                        <P>
                            (c) 
                            <E T="03">Recognition of deferred section 987 gain or loss in the taxable year of a deferral event and in subsequent taxable years</E>
                            —(1) 
                            <E T="03">In general</E>
                            —(i) 
                            <E T="03">Deferred section 987 gain or loss.</E>
                             A deferral QBU owner (as defined in paragraph (c)(1)(ii) of this section) recognizes section 987 gain or loss attributable to the deferral QBU that, as a result of paragraph (b) of 
                            <PRTPAGE P="20798"/>
                            this section, is not recognized in the taxable year of the deferral event under § 1.987-5 (deferred section 987 gain or loss) in the taxable year of the deferral event and in subsequent taxable years as provided in paragraphs (c)(2) through (4) of this section.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Deferral QBU owner.</E>
                             For purposes of this paragraph (c), a deferral QBU owner means, with respect to a deferral QBU, the owner of the deferral QBU immediately before the deferral event, or the owner's qualified successor.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Recognition upon a subsequent remittance</E>
                            —(i) 
                            <E T="03">In general.</E>
                             Except as provided in paragraph (c)(3) of this section, a deferral QBU owner recognizes deferred section 987 gain or loss in the taxable year of the deferral event and in subsequent taxable years upon a remittance from a successor QBU to the owner of the successor QBU (successor QBU owner) in the amount described in paragraph (c)(2)(ii) of this section.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Amount.</E>
                             The amount of deferred section 987 gain or loss that is recognized pursuant to this paragraph (c)(2) in a taxable year of the deferral QBU owner is the outstanding deferred section 987 gain or loss (that is, the amount of deferred section 987 gain or loss not previously recognized) multiplied by the remittance proportion of the successor QBU owner with respect to the successor QBU for the taxable year ending with or within the taxable year of the deferral QBU owner, as determined under § 1.987-5(b) (and, to the extent relevant, paragraphs (b) and (c)(2)(iii) of this section) without regard to any election under § 1.987-8(d). For purposes of computing this remittance proportion, multiple successor QBUs of the same deferral QBU are treated as a single successor QBU. See paragraph (h) of this section, 
                            <E T="03">Example 5,</E>
                             for an illustration of this rule.
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Deemed remittance when a successor QBU ceases to be owned by a member of the deferral QBU owner's controlled group.</E>
                             For purposes of this paragraph (c)(2), in a taxable year of the deferral QBU owner in which a successor QBU ceases to be owned by a member of a controlled group that includes the deferral QBU owner, the successor QBU owner is treated as having a remittance proportion of 1. Accordingly, if there is only one successor QBU with respect to a deferral QBU and that successor QBU ceases to be owned by a member of the controlled group that includes the deferral QBU owner, all outstanding deferred section 987 gain or loss with respect to that deferral QBU will be recognized. This paragraph (c)(2)(iii) does not affect the application of §§ 1.987-1 through 1.987-11 to the successor QBU owner with respect to its ownership of the successor QBU.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Recognition of deferred section 987 loss in certain outbound successor QBU terminations.</E>
                             Notwithstanding paragraph (c)(2) of this section, if assets of the successor QBU (transferred assets) are transferred (or deemed transferred) in a transaction that would constitute an outbound loss event if the successor QBU had a net accumulated section 987 loss at the time of the exchange, then the deferral QBU owner recognizes outstanding deferred section 987 loss, if any, to the extent it would recognize loss under paragraph (d)(1) of this section if (i) the deferral QBU owner owned the successor QBU, (ii) the deferral QBU owner had net unrecognized section 987 loss with respect to the successor QBU equal to its outstanding deferred section 987 loss with respect to the deferral QBU, and (iii) the transferred assets were transferred (or deemed transferred) in an outbound loss event. Any outstanding deferred section 987 loss with respect to the deferral QBU that is not recognized as a result of the preceding sentence is recognized by the deferral QBU owner in the first taxable year in which the deferral QBU owner (including any qualified successor) ceases to be a member of a controlled group that includes the acquirer of the transferred assets or any qualified successor of such acquirer.
                        </P>
                        <P>
                            (4) 
                            <E T="03">Special rules regarding successor QBUs</E>
                            —(i) 
                            <E T="03">Successor QBU with respect to a deferral QBU that is a successor QBU.</E>
                             If a section 987 QBU is a successor QBU with respect to a deferral QBU that is a successor QBU with respect to another deferral QBU, the first-mentioned section 987 QBU is considered a successor QBU with respect to the second-mentioned deferral QBU. For example, if QBU A is a successor QBU with respect to QBU B, and QBU B is a successor QBU with respect to QBU C, then QBU A is a successor QBU with respect to QBU C.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Separation of a successor QBU.</E>
                             If a successor QBU with respect to a deferral QBU separates into two or more separated QBUs (as defined in § 1.987-2(c)(9)(iii)), each separated QBU is considered a successor QBU with respect to the deferral QBU.
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Combination of a successor QBU.</E>
                             If a successor QBU with respect to a deferral QBU combines with another section 987 QBU of the same owner, resulting in a combined QBU (as defined in § 1.987-2(c)(9)(i)), the combined QBU is considered a successor QBU with respect to the deferral QBU.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Loss recognition upon an outbound loss event</E>
                            —(1) 
                            <E T="03">In general.</E>
                             Notwithstanding § 1.987-5, the owner of a section 987 QBU with respect to which an outbound loss event occurs (an outbound loss QBU) includes in taxable income in the taxable year of an outbound loss event section 987 loss with respect to that section 987 QBU only to the extent provided in paragraph (d)(3) of this section.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Outbound loss event.</E>
                             An outbound loss event means, with respect to a section 987 QBU:
                        </P>
                        <P>(i) Any termination of the section 987 QBU in connection with a transfer by a U.S. person of assets of the section 987 QBU to a foreign person that is a member of the same controlled group as the U.S. transferor immediately before the transaction or, if the transferee did not exist immediately before the transaction, immediately after the transaction (related foreign person), provided that the termination would result in the recognition of section 987 loss with respect to the section 987 QBU under § 1.987-5 and paragraph (b) of this section but for this paragraph (d); or</P>
                        <P>
                            (ii) Any transfer by a U.S. person of part of an interest in a section 987 aggregate partnership or DE through which the U.S. person owns the section 987 QBU to a related foreign person that has the same functional currency as the section 987 QBU, or any contribution by such a related foreign person to such a partnership or DE of assets that, immediately after the contribution, are not considered to be included on the books and records of an eligible QBU, provided that the transfer would result in the recognition of section 987 loss with respect to the section 987 QBU under § 1.987-5 and paragraph (b) of this section but for this paragraph (d). See paragraph (h) of this section, 
                            <E T="03">Example 3,</E>
                             for an illustration of this rule.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Loss recognized upon an outbound loss event.</E>
                             In the taxable year of an outbound loss event with respect to an outbound loss QBU, the owner of the outbound loss QBU recognizes section 987 loss as determined under § 1.987-5 and paragraphs (b) and (c) of this section, except that, solely for purposes of applying § 1.987-5, the following assets and liabilities of the outbound loss QBU are treated as not having been transferred and therefore as remaining on the books and records of the outbound loss QBU notwithstanding the outbound loss event:
                        </P>
                        <P>
                            (i) In the case of an outbound loss event described in paragraph (d)(2)(i) of this section, assets and liabilities that, 
                            <PRTPAGE P="20799"/>
                            immediately after the outbound loss event, are reflected on the books and records of the related foreign person described in that paragraph or of an eligible QBU owned by such related foreign person; and
                        </P>
                        <P>(ii) In the case of an outbound loss event described in paragraph (d)(2)(ii) of this section, assets and liabilities that, immediately after the outbound loss event, are reflected on the books and records of the eligible QBU from which the assets and liabilities of the outbound loss QBU are allocated and not on the books and records of a section 987 QBU.</P>
                        <P>
                            (4) 
                            <E T="03">Adjustment of basis of stock received in certain nonrecognition transactions.</E>
                             If an outbound loss event results from the transfer of assets of the outbound loss QBU in a transaction described in section 351 or section 361, the basis of the stock that is received in the transaction is increased by an amount equal to the section 987 loss that, as a result of this paragraph (d), is not recognized with respect to the outbound loss QBU in the taxable year of the outbound loss event (outbound section 987 loss).
                        </P>
                        <P>
                            (5) 
                            <E T="03">Recognition of outbound section 987 loss that is not converted into stock basis.</E>
                             Outbound section 987 loss attributable to an outbound loss event that is not described in paragraph (d)(4) of this section is recognized by the owner of the outbound loss QBU in the first taxable year in which the owner or any qualified successor of the owner ceases to be a member of a controlled group that includes the related foreign person referred to in paragraph (d)(2)(i) or (ii) of this section, or any qualified successor of such person.
                        </P>
                        <P>
                            (e) 
                            <E T="03">Source and character</E>
                            —(1) 
                            <E T="03">Deferred section 987 gain or loss and certain outbound section 987 loss.</E>
                             The source and character of deferred section 987 gain or loss recognized pursuant to paragraph (c) of this section, and of outbound section 987 loss recognized pursuant to paragraph (d)(5) of this section, is determined under § 1.987-6 as if such deferred section 987 gain or loss were recognized pursuant to § 1.987-5 without regard to this section on the date of the related deferral event or outbound loss event.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Outbound section 987 loss reflected in stock basis.</E>
                             If loss is recognized on the sale or exchange of stock described in paragraph (d)(4) of this section within two years of the outbound loss event described in that paragraph, then, to the extent of the outbound section 987 loss, the source and character of the loss recognized on the sale or exchange is determined under § 1.987-6 as if such loss were section 987 loss recognized pursuant to § 1.987-5 without regard to this section on the date of the outbound loss event.
                        </P>
                        <P>
                            (f) 
                            <E T="03">Definitions</E>
                            —(1) 
                            <E T="03">Controlled group.</E>
                             For purposes of this section, a controlled group means all persons with the relationships to each other specified in sections 267(b) or 707(b).
                        </P>
                        <P>
                            (2) 
                            <E T="03">Qualified successor.</E>
                             For purposes of this section, a qualified successor with respect to a corporation (transferor corporation) means another corporation (acquiring corporation) that acquires the assets of the transferor corporation in a transaction described in section 381(a), but only if (A) the acquiring corporation is a domestic corporation and the transferor corporation was a domestic corporation, or (B) the acquiring corporation is a controlled foreign corporation (as defined in section 957(a)) (CFC) and the transferor corporation was a CFC. A qualified successor of a corporation includes the qualified successor of a qualified successor of the corporation.
                        </P>
                        <P>
                            (g) 
                            <E T="03">Anti-abuse.</E>
                             No section 987 loss is recognized under § 1.987-5 or this section in connection with a transaction or series of transactions that are undertaken with a principal purpose of avoiding the purposes of this section.
                        </P>
                        <P>
                            (h) 
                            <E T="03">Examples.</E>
                             The following examples illustrate the application of this section. For purposes of the examples, DC1 is a domestic corporation that owns all of the stock of DC2, which is also a domestic corporation, and CFC1 and CFC2 are CFCs. In addition, DC1, DC2, CFC1, and CFC2 are members of a controlled group as defined in paragraph (f)(1) of this section, and the de minimis rule of paragraph (a)(3)(ii) of this section is not applicable. Finally, except as otherwise provided, Business A is a section 987 QBU with the euro as its functional currency, there are no transfers between Business A and its owner, and Business A's assets are not depreciable or amortizable.
                        </P>
                        <EXAMPLE>
                            <HD SOURCE="HED">(1) Example 1.</HD>
                            <P>
                                <E T="03">Contribution of a section 987 QBU to a member of the controlled group.</E>
                                 (i) 
                                <E T="03">Facts.</E>
                                 DC1 owns all of the interests in Business A. The balance sheet of Business A reflects assets with an aggregate adjusted basis of €1,000x and no liabilities. DC1 contributes €900x of Business A's assets to DC2 in an exchange to which section 351 applies. Immediately after the contribution, the remaining €100x of Business A's assets are no longer reflected on the books and records of a section 987 QBU. DC2, which has the U.S. dollar as its functional currency, uses the former Business A assets in a business (Business B) that constitutes a section 987 QBU. At the time of the contribution, Business A has net accumulated unrecognized section 987 gain of $100x.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Analysis.</E>
                                 (A) Under § 1.987-2(c)(2)(ii), DC1's contribution of €900x of Business A's assets to DC2 is treated as a transfer of all of the assets of Business A to DC1, immediately followed by DC1's contribution of €900x of Business A's assets to DC2. The contribution of Business A's assets is a deferral event within the meaning of paragraph (b)(2) of this section because:
                            </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) The transfer from Business A to DC1 is a transfer of substantially all of Business A's assets to DC1, resulting in a termination of Business A under § 1.987-8(b)(2); and
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Immediately after the transaction, assets of Business A are reflected on the books and records of Business B, a section 987 QBU owned by a member of DC1's controlled group and a successor QBU within the meaning of paragraph (b)(4) of this section. Accordingly, Business A is a deferral QBU within the meaning of paragraph (b)(1) of this section, and DC1 is a deferral QBU owner of Business A within the meaning of paragraph (c)(1)(ii) of this section.
                            </P>
                            <P>(B) Under paragraph (b)(3) of this section, DC1's taxable income in the taxable year of the deferral event includes DC1's section 987 gain or loss determined with respect to Business A under § 1.987-5, except that, for purposes of applying § 1.987-5, all assets and liabilities of Business A that are reflected on the books and records of Business B immediately after Business A's termination are treated as not having been transferred and therefore as though they remained on Business A's books and records (notwithstanding the deemed transfer of those assets under § 1.987-8(e)). Accordingly, in the taxable year of the deferral event, DC1 is treated as making a remittance of €100x, corresponding to the assets of Business A that are no longer reflected on the books and records of a section 987 QBU, and is treated as having a remittance proportion with respect to Business A of 0.1, determined by dividing the €100x remittance by the sum of the remittance and the €900x aggregate adjusted basis of the gross assets deemed to remain on Business A's books at the end of the year. Thus, DC1 recognizes $10x of section 987 gain in the taxable year of the deferral event. DC1's deferred section 987 gain equals $90x, which is the amount of section 987 gain that, but for the application of paragraph (b) of this section, DC1 would have recognized under § 1.987-5 ($100x), less the amount of section 987 gain recognized by DC1 under § 1.987-5 and this section ($10x). </P>
                        </EXAMPLE>
                        <EXAMPLE>
                            <HD SOURCE="HED">
                                <E T="03">(2) Example 2.</E>
                                  
                            </HD>
                            <P>
                                  
                                <E T="03">Election to be classified as a corporation.</E>
                                 (i) 
                                <E T="03">Facts.</E>
                                 DC1 owns all of the interests in Entity A, a DE. Entity A conducts Business A, which has net accumulated unrecognized section 987 gain of $500x. Entity A elects to be classified as a corporation under § 301.7701-3(a). As a result of the election and pursuant to § 301.7701-3(g)(1)(iv), DC1 is treated as contributing all of the assets and liabilities of Business A to newly-formed CFC1, which has the euro as its functional currency. Immediately after the contribution, the assets and liabilities of Business A are reflected on CFC1's balance sheet.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Analysis.</E>
                                 Under § 1.987-2(c)(2)(ii), DC1's contribution of all of the assets and liabilities of Business A to CFC1 is treated as a transfer of all of the assets and liabilities 
                                <PRTPAGE P="20800"/>
                                of Business A to DC1, followed immediately by DC1's contribution of those assets and liabilities to CFC1. Because the deemed transfer from Business A to DC1 is a transfer of substantially all of Business A's assets to DC1, the Business A QBU terminates under § 1.987-8(b)(2). The contribution of Business A's assets is not a deferral event within the meaning of paragraph (b)(2) of this section because, immediately after the transaction, no assets of Business A are reflected on the books and records of a successor QBU within the meaning of paragraph (b)(4) of this section due to the fact that the assets of Business A are not reflected on the books and records of a section 987 QBU immediately after the termination as well as the fact that the requirement of paragraph (b)(4)(iii) of this section is not met. Accordingly, DC1 recognizes section 987 gain with respect to Business A under § 1.987-5 without regard to this section. Because the requirement of paragraph (b)(4)(iii) of this section is not met, the result would be the same even if the assets of Business A were transferred in a section 351 exchange to an existing foreign corporation that had a different functional currency than Business A. 
                            </P>
                        </EXAMPLE>
                        <EXAMPLE>
                            <HD SOURCE="HED">
                                <E T="03">(3) Example 3.</E>
                            </HD>
                            <P>
                                  
                                <E T="03">Outbound loss event.</E>
                                 (i) 
                                <E T="03">Facts.</E>
                                 The facts are the same as in 
                                <E T="03">Example 2 in paragraph (h)(2) of this section,</E>
                                 except that Business A has net accumulated unrecognized section 987 loss of $500x rather than net accumulated unrecognized section 987 gain of $500x.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Analysis.</E>
                                 (A) The analysis of the transactions under §§ 1.987-2(c)(2)(ii), 1.987-8(b)(2), and paragraph (b) of this section is the same as in 
                                <E T="03">Example 2 in paragraph (h)(2) of this section.</E>
                                 However, the termination of Business A as a result of the transfer of the assets of Business A by a U.S. person (DC1) to a foreign person (CFC1) that is a member of DC1's controlled group is an outbound loss event described in paragraph (d)(2) of this section.
                            </P>
                            <P>(B) Under paragraphs (d)(1) and (3) of this section, in the taxable year of the outbound loss event, DC1 includes in taxable income section 987 loss recognized with respect to Business A as determined under § 1.987-5, except that, for purposes of applying § 1.987-5, all assets and liabilities of Business A that are reflected on the books and records of CFC1, a related foreign person described in paragraph (d)(2) of this section, are treated as not having been transferred. Accordingly, DC1's remittance proportion with respect to Business A is 0, and DC1 recognizes no section 987 loss with respect to Business A. DC1's outbound section 987 loss is $500x, which is the amount of section 987 loss that DC1 would have recognized under § 1.987-5 ($500x) without regard to paragraph (d) of this section, less the amount of section 987 loss recognized by DC1 under paragraph (d)(3) of this section ($0). Under paragraph (d)(4) of this section, DC1 must increase its basis in its CFC1 shares by the amount of the outbound section 987 loss ($500x).</P>
                        </EXAMPLE>
                        <EXAMPLE>
                            <HD SOURCE="HED">
                                <E T="03">(4) Example 4.</E>
                            </HD>
                            <P>
                                  
                                <E T="03">Conversion of a DE to a partnership.</E>
                                 (i) 
                                <E T="03">Facts.</E>
                                 (A) DC1 owns all of the interests in Entity A, a DE that conducts Business A. On the last day of Year 1, DC1 sells 50 percent of its interest in Entity A to DC2 (the Entity A sale).
                            </P>
                            <P>
                                (B) For Federal income tax purposes, Entity A is converted to a partnership when DC2 purchases the 50 percent interest in Entity A. DC2's purchase is treated as the purchase of 50 percent of the assets of Entity A (that is, the assets of Business A), which, prior to the purchase, were treated as held directly by DC1 for Federal income tax purposes. Immediately after DC2's deemed purchase of 50 percent of Business A assets, DC1 and DC2 are treated as contributing their respective interests in Business A assets to a partnership. 
                                <E T="03">See</E>
                                 Rev. Rul. 99-5, 1999-1 CB 434 (situation 1). In connection with the deemed contribution, DC1 and DC2 agree to share equally in all items of the partnership's profits and loss, and, for purposes of § 1.987-7, to determine their share of assets and liabilities of the resulting partnership in accordance with their respective shares of partnership profits.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Analysis.</E>
                                 (A) The transactions deemed to occur under Rev. Rul. 99-5 are not taken into account for purposes of this section. The Entity A sale and resulting existence of a partnership, however, have consequences under section 987 and this section, as described in this Example 4 in paragraphs (h)(4)(ii)(B) through (D) of this section.
                            </P>
                            <P>(B) Immediately after the Entity A sale, Entity A is a section 987 aggregate partnership within the meaning of § 1.987-1(b)(5) because DC1 and DC2 own all the interests in partnership capital and profits, DC1 and DC2 are related within the meaning of section 267(b), and the partnership has an eligible QBU (Business A) that would be a section 987 QBU with respect to a partner if owned by the partner directly. As a result of the Entity A sale, 50 percent of the assets and liabilities of Business A ceased to be reflected on the books and records of DC1's Business A section 987 QBU. As a result, such assets and liabilities are treated as if they were transferred from DC1's Business A section 987 QBU to DC1. Additionally, following DC2's acquisition of 50 percent of the interest in Entity A, DC2 is allocated 50 percent of the assets and liabilities of Business A under §§ 1.987-2(b). Because DC2 and Business A have different functional currencies, DC2's portion of the Business A assets and liabilities constitutes a section 987 QBU. Accordingly, 50 percent of the assets and liabilities of Business A are treated as transferred by DC2 to DC2's Business A section 987 QBU.</P>
                            <P>(C) The Entity A sale is a deferral event described in paragraph (b)(2) of this section because:</P>
                            <P>(1) The sale constitutes the disposition of part of an interest in a DE; and</P>
                            <P>(2) Immediately after the transaction, assets of DC1's Business A section 987 QBU are reflected on the books and records of DC1's Business A section 987 QBU and DC2's Business A section 987 QBU, each of which is a successor QBU with respect to DC1's Business A section 987 QBU within the meaning of paragraph (b)(4) of this section. Accordingly, DC1's Business A section 987 QBU is a deferral QBU within the meaning of paragraph (b)(1) of this section, and DC1 is a deferral QBU owner within the meaning of paragraph (c)(1)(ii) of this section. Under paragraph (b)(1) of this section, DC1 includes in taxable income section 987 gain or loss with respect to Business A in connection with the deferral event to the extent provided in paragraphs (b)(3) and (c) of this section.</P>
                            <P>(D) Under paragraph (b) of this section, in the taxable year of the Entity A sale, DC1 includes in taxable income section 987 gain or loss with respect to Business A as determined under § 1.987-5, except that, for purposes of applying § 1.987-5, all assets and liabilities of Business A that, immediately after the Entity A sale, are reflected on the books and records of successor QBUs are treated as though they were not transferred and therefore as remaining on the books and records of DC1's Business A section 987 QBU notwithstanding the Entity A sale. Accordingly, DC1's remittance amount under § 1.987-5 is $0, and DC1 recognizes no section 987 gain or loss with respect to Business A. </P>
                        </EXAMPLE>
                        <EXAMPLE>
                            <HD SOURCE="HED">
                                <E T="03">(5) Example 5.</E>
                                  
                            </HD>
                            <P>
                                  
                                <E T="03">Partial recognition of deferred gain or loss.</E>
                                 (i) 
                                <E T="03">Facts.</E>
                                 DC1 owns all of the interests in Entity A, a DE that conducts Business A in Country X. During Year 1, DC1 contributes all of its interests in Entity A to DC2 in an exchange to which section 351 applies. At the time of the contribution, Business A has net accumulated unrecognized section 987 gain of $100x. After the contribution, Entity A continues to conduct business in Country X (Business B). In Year 3, as a result of a net transfer of property from Business B to DC2, DC2's remittance proportion with respect to Business B, as determined under § 1.987-5, is 0.25.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Analysis.</E>
                                 (A) For the reasons described in 
                                <E T="03">Example 1 in paragraph (h)(1) of this section,</E>
                                 the contribution of Entity A by DC1 to DC2 results in a termination of Business A and a deferral event with respect to Business A, a deferral QBU; DC1 is a deferral QBU owner within the meaning of paragraph (c)(1)(ii) of this section; Business B is a successor QBU with respect to Business A; DC2 is a successor QBU owner; and the $100x of net accumulated unrecognized section 987 gain with respect to Business A becomes deferred section 987 gain as a result of the deferral event.
                            </P>
                            <P>(B) Under paragraph (c)(1) of this section, DC1 recognizes deferred section 987 gain with respect to Business A in accordance with paragraphs (c)(2) through (4) of this section. Under paragraph (c)(2)(i) of this section, DC1 recognizes deferred section 987 gain in Year 3 as a result of the remittance from Business B to DC2. Under paragraph (c)(2)(ii) of this section, the amount of deferred section 987 gain that DC1 recognizes is $25x, which is DC1's outstanding deferred section 987 gain or loss ($100x) with respect to Business A multiplied by the remittance proportion (0.25) of DC2 with respect to Business B for the taxable year as determined under § 1.987-5(b).</P>
                        </EXAMPLE>
                        <P>
                            (i) 
                            <E T="03">Coordination with fresh start transition method</E>
                            —(1) 
                            <E T="03">In general.</E>
                             If a taxpayer is a deferral QBU owner, or is or was the owner of an outbound loss QBU, and the taxpayer is required under § 1.987-10(a) to apply the fresh start transition method described in § 1.987-10(b) to the deferral QBU or outbound 
                            <PRTPAGE P="20801"/>
                            loss QBU, or would have been so required if the taxpayer had owned the deferral QBU or outbound loss QBU on the transition date (as defined in § 1.987-11(c)), the adjustments described in paragraphs (i)(2) and (3) of this section, as applicable, must be made on the transition date.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Adjustment to deferred section 987 gain or loss.</E>
                             The amount of any outstanding deferred section 987 gain or loss of a deferral QBU owner with respect to a deferral QBU described in paragraph (i)(1) of this section must be adjusted to equal the amount of outstanding deferred section 987 gain or loss that the deferral QBU owner would have had with respect to the deferral QBU on the transition date if, immediately before the deferral event, the deferral QBU had transitioned to the method prescribed by §§ 1.987-1 through 1.987-10 pursuant to the fresh start transition method.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Adjustments in the case of an outbound loss event.</E>
                             The basis of any stock described in paragraph (d)(4) of this section that was received in connection with the transfer (or deemed transfer) of assets of an outbound loss QBU described in paragraph (i)(1) of this section and that is held on the transition date must be adjusted to equal the basis that such stock would have had on the transition date if, immediately prior to the outbound loss event, the outbound loss QBU had transitioned to the method prescribed by §§ 1.987-1 through 1.987-10 pursuant to the fresh start transition method. If no such stock was received, the amount of any outbound section 987 loss with respect to the outbound loss QBU that may be recognized on or after the transition date pursuant to paragraph (d)(5) of this section must be adjusted to equal the amount of such loss that would be outstanding and that may be recognized pursuant to that paragraph if, immediately before the outbound loss event, the outbound loss QBU had transitioned to the method prescribed by §§ 1.987-1 through 1.987-10 pursuant to the fresh start transition method.
                        </P>
                        <P>
                            (j) 
                            <E T="03">Applicability date</E>
                            —(1) 
                            <E T="03">In general.</E>
                             Except as described in paragraph (j)(2) of this section, this section applies to any deferral event or outbound loss event that occurs on or after January 6, 2017. This section also applies to any deferral event or outbound loss event that occurs as a result of an entity classification election made under § 301.7701-3 that is filed on or after January 6, 2017, and that is effective before January 6, 2017.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Exceptions</E>
                            —(i) 
                            <E T="03">Principal purpose.</E>
                             This section applies to any deferral event or outbound loss event occurring on or after December 7, 2016, if such deferral event or outbound loss event was undertaken with a principal purpose of recognizing section 987 loss.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Entity classification.</E>
                             This section also applies to any deferral event or outbound loss event that occurs as a result of an entity classification election made under § 301.7701-3 that was filed on or after December 22, 2016, that was effective before December 7, 2016, and that was undertaken with a principal purpose of recognizing section 987 loss. 
                        </P>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1.987-12T </SECTNO>
                    <SUBJECT> [Removed]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 10.</E>
                         Section 1.987-12T is removed.
                    </AMDPAR>
                </REGTEXT>
                <SIG>
                    <NAME>Kirsten Wielobob,</NAME>
                    <TITLE>Deputy Commissioner for Services and Enforcement.</TITLE>
                    <DATED>Approved: April 8, 2019.</DATED>
                    <NAME>David J. Kautter,</NAME>
                    <TITLE>Assistant Secretary of the Treasury (Tax Policy).</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09552 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4830-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <CFR>26 CFR Part 300</CFR>
                <DEPDOC>[TD 9858]</DEPDOC>
                <RIN>RIN 1545-BO38</RIN>
                <SUBJECT>User Fees Relating to Enrolled Agents and Enrolled Retirement Plan Agents</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final regulation.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document contains final regulations that amend regulations relating to imposing user fees for enrolled agents and enrolled retirement plan agents. The final regulations remove the initial enrollment user fee for enrolled retirement plan agents because the IRS no longer offers initial enrollment as an enrolled retirement plan agent. The final regulations also increase the amount of the renewal user fee for enrolled retirement plan agents from $30 to $67. In addition, the final regulations increase the amount of both the enrollment and renewal user fee for enrolled agents from $30 to $67. The final regulations affect individuals who are, or apply to become, enrolled agents and individuals who are enrolled retirement plan agents. The Independent Offices Appropriations Act of 1952 authorizes charging user fees.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P/>
                    <P>
                        <E T="03">Effective date:</E>
                         This regulation is effective June 12, 2019.
                    </P>
                    <P>
                        <E T="03">Applicability date:</E>
                         For the dates of applicability, see §§ 300.5(d), 300.6(d), and 300.10(d).
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mark Shurtliff at (202) 317-6845 (not a toll-free number).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background and Explanation of Provisions</HD>
                <P>This document contains amendments to 26 CFR part 300 regarding user fees.</P>
                <HD SOURCE="HD2">A. User Fee Authority and Enrolled Agent and Enrolled Retirement Plan Agent User Fees</HD>
                <P>The Independent Offices Appropriations Act of 1952 (IOAA) (31 U.S.C. 9701) authorizes each agency to promulgate regulations establishing a charge for services the agency provides (user fees). The charges must be fair and must be based on the costs to the government, the value of the service to the recipient, the public policy or interest served, and other relevant facts. Under the IOAA, user fee regulations are subject to policies prescribed by the President. Those policies are currently set forth in the Office of Management and Budget (OMB) Circular A-25, 58 FR 38142 (July 15, 1993).</P>
                <P>
                    Under OMB Circular A-25, Federal agencies that provide services that confer special benefits on identifiable recipients beyond those accruing to the general public are to establish user fees that recover the full cost of providing the special benefit. An agency that seeks to impose a user fee for government-provided services must calculate the full cost of providing those services, review user fees biennially, and update them as necessary. Section 330(a)(1) of title 31 of the United States Code authorizes the Secretary of the Treasury to regulate the practice of representatives before the Department of the Treasury (Treasury Department). Pursuant to section 330 of title 31, the Secretary has published regulations governing practice before the IRS in 31 CFR part 10 and reprinted the regulations as Treasury Department Circular No. 230 (Circular 230). Section 10.3 of Circular 230 defines who may practice before the IRS and includes individuals who have been granted enrollment to practice as enrolled agents and enrolled retirement plan agents. Section 10.4 of Circular 230 authorizes the IRS to grant enrollment as an enrolled agent or enrolled retirement plan agent to individuals who demonstrate special competence in tax matters by passing a written examination administered by, or under 
                    <PRTPAGE P="20802"/>
                    the oversight of, the IRS and who have not engaged in any conduct that would justify suspension or disbarment under Circular 230. Section 10.4 also authorizes the IRS to grant enrollment as an enrolled agent or an enrolled retirement plan agent to a qualifying former IRS employee by virtue of past IRS service and technical experience if the former employee has not engaged in any conduct that would justify suspension or disbarment under the provisions of Circular 230 and meets certain other requirements. The ability to practice before the IRS is a special benefit that is conferred on enrolled agents and enrolled retirement plan agents that does not accrue to the general public.
                </P>
                <P>Once eligible for enrollment as an enrolled agent, whether by examination or former employment with the IRS, an individual must file an application for enrollment with the IRS and pay a $30 nonrefundable user fee. To maintain active enrollment and eligibility to practice before the IRS, an individual who has been enrolled as an enrolled agent or enrolled retirement plan agent must file an application to renew enrollment every three years and pay a $30 nonrefundable user fee. 31 CFR 10.6(d).</P>
                <P>As required by the IOAA and OMB Circular A-25, the IRS Return Preparer Office (RPO) completed its 2017 biennial review of the enrollment and renewal user fees associated with enrolled agents and enrolled retirement plan agents. As discussed in section B of this preamble, during its review the RPO took into account the increase in labor, benefits, and overhead costs incurred in connection with providing services to individuals who enroll or renew enrollment as enrolled agents and enrolled retirement plan agents since the user fee was last changed in 2011. In addition, RPO determined that costs associated with Federal tax-compliance checks and suitability checks on enrolled individuals should be recovered as part of the user fee for administering the enrollment and renewal programs. The 2017 biennial review also took into account new costs associated with administering the program for enrolled agents and enrolled retirement plan agents, including the costs of operating a dedicated toll-free helpline in the RPO for enrollment and renewal matters.</P>
                <HD SOURCE="HD2">B. Calculation of the User Fee</HD>
                <P>
                    The IRS follows generally accepted accounting principles (GAAP) in calculating the full cost of administering the program for enrollment or renewal. GAAP is established by the Financial Accounting Standards Board (FASB). Recognition of costs is based on Statement of Federal Financial Accounting Standards (SFFAS) No. 4: Managerial Cost Accounting Concepts and Standards for the Federal Government, issued by the Federal Accounting Standard Advisory Board (FASAB). The FASAB Handbook of Federal Accounting Standards and Other Pronouncements, as Amended, is available at 
                    <E T="03">https://files.fasab.gov/pdffiles/2018_fasab_handbook.pdf.</E>
                </P>
                <HD SOURCE="HD3">1. Cost Center Allocation</HD>
                <P>The IRS determines the cost of its services and activities using a cost-accounting system that tracks costs to organizational units. The lowest organizational unit in the IRS's cost-accounting system is a cost center. Cost centers are usually separate offices that are distinguished by subject-matter area of responsibility or geographic region. Costs of operating a cost center are recorded in the IRS's cost-accounting system. Costs of user fees include direct costs, such as labor, and indirect costs. Indirect costs are not easily traceable and are allocated using a method or by applying an overhead rate.</P>
                <HD SOURCE="HD3">2. Determining the per Unit Cost</HD>
                <P>To establish the per-unit cost, the total cost of providing the service is divided by the volume of services provided.</P>
                <HD SOURCE="HD3">3. Cost Estimation of Direct Labor</HD>
                <P>Not all cost centers are fully devoted to one service for which the IRS charges user fees. Some cost centers work on a number of different services across the IRS. In these cases, the IRS uses various cost-measurement techniques to estimate the cost incurred in those cost centers attributable to the program. These techniques include using various timekeeping systems to measure the time required to accomplish activities, or using information provided by subject-matter experts on the time devoted to a program. Once the IRS has estimated the average time required to accomplish an activity, it multiplies that time estimate by the relevant organizational unit's average labor and benefits cost per unit of time to determine the labor and benefits cost incurred to provide the service. To determine the full cost, IRS then adds overhead as discussed below.</P>
                <HD SOURCE="HD3">4. Overhead</HD>
                <P>Overhead is an indirect cost of operating an organization that cannot be immediately associated with an activity that the organization performs. Overhead includes costs of resources that are jointly or commonly consumed by one or more organizational unit's activities but are not specifically identifiable to a single activity.</P>
                <P>These costs can include:</P>
                <P>• General management and administrative services of sustaining and supporting organizations.</P>
                <P>• Facilities management and ground maintenance services (security, rent, utilities, and building maintenance).</P>
                <P>• Procurement and contracting services.</P>
                <P>• Financial management and accounting services.</P>
                <P>• Information technology services.</P>
                <P>• Services to acquire and operate property, plants and equipment.</P>
                <P>• Publication, reproduction, and graphics and video services.</P>
                <P>• Research, analytical, and statistical services.</P>
                <P>• Human resources/personnel services.</P>
                <P>• Library and legal services.</P>
                <P>To calculate the overhead allocable to a service, the IRS multiplies a Corporate Overhead rate by the labor and benefits costs determined as discussed previously. The IRS calculates the Corporate Overhead rate annually based on cost elements underlying the Statement of Net Cost included in the IRS Annual Financial Statements, which are audited by the Government Accountability Office. The Corporate Overhead rate is the ratio of the sum of the IRS's indirect labor and benefits costs from the supporting and sustaining organizational units—those that do not interact directly with taxpayers—and all non-labor costs to the IRS's labor and benefits costs of its organizational units that interact directly with taxpayers.</P>
                <P>The Corporate Overhead rate of 68.00 percent for costs reviewed during FY 2017 was calculated based on FY 2016 costs (which are assumed to be fixed and reoccurring) as follows:</P>
                <GPOTABLE COLS="2" OPTS="L0,tp0,p1,7/8,g1,t1,i1" CDEF="s10,16">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Indirect Labor and Benefits Costs</ENT>
                        <ENT>$1,681,373,747</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Non-Labor Costs</ENT>
                        <ENT>+ $2,879,907,032</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Total Indirect Costs</ENT>
                        <ENT>$4,561,280,779</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Direct Labor and Benefits Costs</ENT>
                        <ENT>÷ $6,708,063,559</ENT>
                    </ROW>
                    <ROW RUL="n,d">
                        <ENT I="01">Corporate Overhead Rate</ENT>
                        <ENT>68.00%</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD3">5. Calculation of the per Unit Cost of the User Fee</HD>
                <P>
                    The IRS used projections for fiscal years 2018 through 2020 to determine the direct costs associated with enrolled agent enrollment and renewal and enrolled retirement plan agent renewal. Direct costs are incurred by the RPO and include labor costs for enrollment and 
                    <PRTPAGE P="20803"/>
                    renewal submission processing; tax compliance and background checks; continuing education and testing-related activities; and communications, which include the new toll-free helpline.
                </P>
                <P>The labor and benefits for the work performed related to administering the program for enrolled agent enrollment and renewal and enrolled retirement plan agent renewal is projected to be $2,708,603 in total over fiscal years 2018 through 2020. The labor and benefits costs include the cost to perform background checks and tax compliance checks, which are services that were not included in the previous $30 user fee. The number of enrollment and renewal applications is based on the FY2016 numbers adjusted by the anticipated increase in enrollment. Adding Corporate Overhead expenses to the total labor and benefits results in total costs of $4,550,453 as shown below:</P>
                <GPOTABLE COLS="2" OPTS="L0,tp0,p1,8/9,g1,t1,i1" CDEF="s10,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Labor and Benefits</ENT>
                        <ENT>$2,708,603</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Corporate Overhead (68%)</ENT>
                        <ENT>$1,841,850</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Labor, Benefits, and Overhead</ENT>
                        <ENT>$4,550,453</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Dividing this total cost by the projected population of initial enrollment and renewal applications for fiscal years 2018 through 2020 results in a cost per application of $67 as shown below:</P>
                <GPOTABLE COLS="2" OPTS="L0,tp0,p1,8/9,g1,t1,i1" CDEF="s10,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Labor, Benefits and Overhead</ENT>
                        <ENT>$4,550,453</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Number of Applications</ENT>
                        <ENT>÷ 68,343</ENT>
                    </ROW>
                    <ROW RUL="n,d">
                        <ENT I="01">Cost per Application</ENT>
                        <ENT>$67</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Taking into account the full amount of these costs, the RPO determined that the full cost of administering the program for enrolled agents and enrolled retirement plan agents has increased from $30 to $67 per application for enrollment or renewal. The user fee complies with the directive in OMB Circular A-25 to recover the full cost of providing a service that confers special benefits on identifiable recipients beyond those accruing to the general public.</P>
                <HD SOURCE="HD2">C. Notice of Proposed Rulemaking and Final Regulations</HD>
                <P>
                    On November 19, 2018, a notice of proposed rulemaking (REG-122898-17) proposing to amend the regulations relating to imposing user fees for enrolled agents and retirement plan agents was published in the 
                    <E T="04">Federal Register</E>
                     (83 FR 58202). The document proposed removing the initial enrollment user fee for enrolled retirement plan agents because the IRS no longer offers initial enrollment as an enrolled retirement plan agent.
                </P>
                <P>The document also proposed increasing the amount of the renewal user fee for enrolled retirement plan agents from $30 to $67. In addition, the document proposed increasing the amount of both the enrollment and renewal user fees for enrolled agents from $30 to $67. The notice of proposed rulemaking contains a detailed explanation regarding the amendments to these regulations.</P>
                <P>Two comments responding to the notice of proposed rulemaking were received. A public hearing on the notice of proposed rulemaking was scheduled for January 24, 2019. As stated in the notice of proposed rulemaking, requests to speak and outlines of topics to be discussed at the hearing were required to be submitted by January 18, 2019. On January 22, 2019, the public hearing was cancelled due to a lapse in appropriations (IR-2019-05). Because no requests to speak at the hearing had been received, the hearing was not rescheduled. After consideration of the comments, this Treasury Decision adopts the regulations proposed by the notice of proposed rulemaking without change.</P>
                <HD SOURCE="HD1">Summary of Comments</HD>
                <P>
                    Two comments were submitted on the notice of proposed rulemaking. The comments are available at 
                    <E T="03">www.regulations.gov</E>
                     or upon request.
                </P>
                <P>One of the comments agreed with the proposed user fee regulations because the commenter's status as an enrolled agent allows him to earn income by representing taxpayers before the IRS. The comment stated that the commenter supported the increase, so long as the user fees comply with the relevant authorities. As discussed in the background section of this preamble, the IOAA authorizes each agency to promulgate regulations that impose user fees for services the agency provides to identifiable recipients. User fee regulations under the IOAA are subject to policies prescribed by the President, which are set forth in OMB Circular A-25. As described in the background section of this preamble, the Treasury Department and IRS complied with the requirements of the IOAA and OMB Circular A-25 in promulgating these regulations. The notice of proposed rulemaking and the background section of this preamble provide a detailed analysis of how the RPO determined the full cost of providing services to enrolled agents and enrolled retirement plan agents (83 FR 58202). Accordingly, the user fee complies with the relevant authorities.</P>
                <P>The other comment generally disagreed with enrollment and renewal user fees associated with enrolled agents and enrolled retirement plan agents. The comment stated that the Federal government should bear the full cost of administering programs related to tax professionals. This comment was not accepted because it is contrary to the policies prescribed by the President as set forth in OMB Circular A-25. Accordingly, the proposed regulations are adopted without change.</P>
                <HD SOURCE="HD1">Special Analyses</HD>
                <P>Executive Orders 13563 and 12866 direct agencies to assess 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.</P>
                <P>OIRA has determined that this regulation is significant and subject to review under section 6(b) of Executive Order 12866.</P>
                <P>
                    Pursuant to the Regulatory Flexibility Act (5 U.S.C. chapter 6), it is hereby certified that this regulation will not have a significant economic impact on a substantial number of small entities. The user fee primarily affects individuals who are enrolled agents, apply to become enrolled agents, or are enrolled retirement plan agents. Only individuals, not businesses, can be enrolled agents or enrolled retirement plan agents. Thus, any economic impact of the user fee on small entities generally will occur only when an enrolled agent or enrolled retirement plan agent owns a small business or when a small business employs enrolled agents or enrolled retirement plan agents and reimburses them for their renewal fees. The Treasury Department and IRS estimate that approximately 22,781 individuals will apply annually for enrollment as an enrolled agent, renewal as an enrolled agent, or renewal as an enrolled retirement plan agent. Due to the relatively small number of small businesses that employ enrolled agents or enrolled retirement plan agents, a substantial number of small entities are not likely to be affected. Further, the economic impact on any small entities affected would be limited to paying the $37 difference in cost between the $67 user fee and the previous $30 user fee for each enrolled agent or enrolled retirement plan agent that a small entity employs and reimburses, or otherwise pays for, the 
                    <PRTPAGE P="20804"/>
                    cost of the user fee. The total economic impact of this regulation is thus approximately $842,897 annually, which is the product of the approximately 22,781 individuals and the $37 increase in the fee which is not a significant economic impact. Accordingly, it is certified that the rule will not have a significant economic impact on a substantial number of small entities.
                </P>
                <P>It is not anticipated that the increase in user fee that is paid every three years and averages to $12.33 per year will negatively affect enrollment, which has historically remained steady as user fee amounts have changed. Pursuant to section 7805(f), the notice of proposed rulemaking was submitted to the Chief Counsel for Advocacy of the Small Business Administration for comment on its impact on small business (83 FR 58202). No comments on the notice of proposed rulemaking were received from the Chief Counsel for Advocacy of the Small Business Administration.</P>
                <HD SOURCE="HD1">Drafting Information</HD>
                <P>The principal author of these regulations is Mark Shurtliff of the Office of the Associate Chief Counsel (Procedure and Administration). Other personnel from the Treasury Department and the IRS participated in their development.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 26 CFR Part 300</HD>
                    <P>Reporting and recordkeeping requirements, User fees.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Adoption of Amendments to the Regulations</HD>
                <P>Accordingly, 26 CFR part 300 is amended as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 300—USER FEES</HD>
                </PART>
                <REGTEXT TITLE="26" PART="300">
                    <AMDPAR>
                        <E T="04">Paragraph. 1.</E>
                         The authority citation for part 300 continues to read as follows:
                    </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>31 U.S.C. 9701.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 300.0 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="26" PART="300">
                    <AMDPAR>
                        <E T="04">Par. 2.</E>
                         Section 300.0 is amended by removing paragraph (b)(10) and redesignating paragraphs (b)(11) through (13) as paragraphs (b)(10) through (12).
                    </AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="300">
                    <AMDPAR>
                        <E T="04">Par. 3.</E>
                         Section 300.5 is amended by revising paragraphs (b) and (d) to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 300.5 </SECTNO>
                        <SUBJECT>Enrollment of enrolled agent fee.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Fee.</E>
                             The fee for initially enrolling as an enrolled agent with the IRS is $67.
                        </P>
                        <STARS/>
                        <P>
                            (d) 
                            <E T="03">Applicability date.</E>
                             This section applies beginning June 12, 2019.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="300">
                    <AMDPAR>
                        <E T="04">Par. 4.</E>
                         Section 300.6 is amended by revising paragraphs (b) and (d) to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 300.6 </SECTNO>
                        <SUBJECT>Renewal of enrollment of enrolled agent fee.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Fee.</E>
                             The fee for renewal of enrollment as an enrolled agent with the IRS is $67.
                        </P>
                        <STARS/>
                        <P>
                            (d) 
                            <E T="03">Applicability date.</E>
                             This section applies beginning June 12, 2019.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 300.10 </SECTNO>
                    <SUBJECT>[Removed]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="26" PART="300">
                    <AMDPAR>
                        <E T="04">Par. 5.</E>
                         Section 300.10 is removed.
                    </AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 300.11 </SECTNO>
                    <SUBJECT>[Redesignated as § 300.10 and Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="26" PART="300">
                    <AMDPAR>
                        <E T="04">Par. 6.</E>
                         Redesignate § 300.11 as § 300.10 and amend newly redesignated § 300.10 by revising paragraphs (b) and (d) to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 300.10 </SECTNO>
                        <SUBJECT>Renewal of enrollment of enrolled retirement plan agent fee.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Fee.</E>
                             The fee for renewal of enrollment as an enrolled retirement plan agent with the IRS is $67.
                        </P>
                        <STARS/>
                        <P>
                            (d) 
                            <E T="03">Applicability date.</E>
                             This section applies beginning June 12, 2019.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§§ 300.12 and 300.13</SECTNO>
                    <SUBJECT>[Redesignated as §§ 300.11 and 300.12]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="26" PART="300">
                    <AMDPAR>
                        <E T="04">Par. 7.</E>
                         Redesignate §§ 300.12 and 300.13 as §§ 300.11 and 300.12.
                    </AMDPAR>
                </REGTEXT>
                <SIG>
                    <NAME>Kirsten Wielobob,</NAME>
                    <TITLE>Deputy Commissioner for Services and Enforcement.</TITLE>
                    <DATED>Approved: April 19, 2019.</DATED>
                    <NAME>David J. Kautter,</NAME>
                    <TITLE>Assistant Secretary of the Treasury (Tax Policy).</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09732 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">POSTAL SERVICE</AGENCY>
                <CFR>39 CFR Part 233</CFR>
                <SUBJECT>Inspection Service Authority; Civil Monetary Penalty Inflation Adjustment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>
                        Postal Service
                        <SU>TM</SU>
                        .
                    </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Interim final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document updates postal regulations by implementing inflation adjustments to civil monetary penalties that may be imposed under consumer protection and mailability provisions enforced by the Postal Service pursuant to the Deceptive Mail Prevention and Enforcement Act and the Postal Accountability and Enhancement Act. These adjustments are required under the Federal Civil Penalties Inflation Adjustment Act of 1990, as amended by the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015. This document includes the adjustments for 2018 and 2019 for statutory civil monetary penalties subject to the 2015 Act.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         May 13, 2019.
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Steven Sultan, (202) 268-7385, 
                        <E T="03">SESultan@uspis.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Federal Civil Penalties Inflation Adjustment Improvements Act of 2015 (2015 Act), Public Law 114-74, 129 Stat. 584, amended the Federal Civil Penalties Inflation Adjustment Act of 1990 (1990 Act), Public Law 101-410, 104 Stat. 890 (28 U.S.C. 2461 note), to improve the effectiveness of civil monetary penalties and to maintain their deterrent effect. Section 3 of the 1990 Act specifically includes the Postal Service in the definition of “agency” subject to its provisions.</P>
                <P>
                    Beginning in 2017, the 2015 Act requires the Postal Service to make an annual adjustment for inflation to civil penalties that meet the definition of “civil monetary penalty” under the 1990 Act. The Postal Service must make the annual adjustment for inflation and publish the adjustment in the 
                    <E T="04">Federal Register</E>
                     by January 15 of each year. The Postal Service did not complete the annual adjustments for 2018 or 2019 due to an oversight. In order to satisfy the annual adjustment requirement, the Postal Service will be making both the 2018 and 2019 annual adjustments at this time. Each penalty will be adjusted as instructed by the Office of Management and Budget (OMB) based on the Consumer Price Index (CPI-U) from the most recent October. OMB has furnished detailed instructions regarding the annual adjustment for 2018 in memorandum M-18-03, 
                    <E T="03">Implementation of Penalty Inflation Adjustments for 2018, Pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015</E>
                     (December 15, 2017), 
                    <E T="03">https://www.whitehouse.gov/wp-content/uploads/2017/11/M-18-03.pdf.</E>
                     OMB provided detailed instructions regarding the annual adjustment for 2019 in memorandum M-19-04, 
                    <E T="03">Implementation of Penalty Inflation Adjustments for 2019, Pursuant to the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015</E>
                     (December 14, 2018), 
                    <E T="03">https://www.whitehouse.gov/wp-content/uploads/2017/11/m_19_04.pdf.</E>
                     For 2018, OMB has advised that an adjustment multiplier of 1.02041 will be 
                    <PRTPAGE P="20805"/>
                    used. For 2019, OMB has advised that an adjustment multiplier of 1.02522 will be used. The Postal Service will first apply the 2018 adjustment multiplier. The Postal Service will then apply the 2019 adjustment multiplier on the 2018 adjusted amount. The new penalty amount must be rounded to the nearest dollar after each adjustment multiplier is applied. The new penalty amounts will take effect immediately upon publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>The 2015 Act allows the interim final rule and annual inflation adjustments to be published without prior public notice or opportunity for public comment.</P>
                <HD SOURCE="HD1">Adjustments to Postal Service Civil Monetary Penalties</HD>
                <P>
                    Civil monetary penalties may be assessed for postal offenses under sections 106 and 108 of the Deceptive Mail Prevention and Enforcement Act, Public Law 106-168, 113 Stat. 1811, 1814 (
                    <E T="03">see,</E>
                     39 U.S.C. 3012(a), (c)(1), (d), and 3017(g)(2), (h)(1)(A)); and section 1008 of the Postal Accountability and Enhancement Act, Public Law 109-435, 120 Stat. 3259-3261 (
                    <E T="03">see,</E>
                     39 U.S.C. 3018 (c)(1)(A)). The statutory civil monetary penalties subject to the 2015 Act and the amount of each penalty the annual adjustment for inflation are as follows:
                </P>
                <HD SOURCE="HD2">39 U.S.C. 3012(a)—False Representations and Lottery Orders</HD>
                <P>Under 39 U.S.C. 3005(a)(1)-(3), the Postal Service may issue administrative orders prohibiting persons from using the mail to obtain money through false representations or lotteries. Persons who evade, attempt to evade, or fail to comply with an order to stop such prohibited practices may be liable to the United States for a civil penalty under 39 U.S.C. 3012(a). The regulations implemented pursuant to this section currently imposes a $69,463 penalty for each mailing less than 50,000 pieces, $138,925 for each mailing of 50,000 to 100,000 pieces, and $13,893 for each additional 10,000 pieces above 100,000 not to exceed $2,778,505. The new penalties will be as follows: $72,669 for each mailing less than 50,000 pieces, $145,335 for each mailing of 50,000 to 100,000 pieces, and $14,535 for each additional 10,000 pieces above 100,000 not to exceed $2,906,718.</P>
                <HD SOURCE="HD2">39 U.S.C. 3012(c)(1)—False Representation and Lottery Penalties in Lieu of or as Part of an Order</HD>
                <P>In lieu of or as part of an order issued under 39 U.S.C. 3005(a)(1)-(3), the Postal Service may assess a civil penalty. Currently, the amount of this penalty, set in the implementing regulations to 39 U.S.C. 3012(c)(1), is $34,731 for each mailing that is less than 50,000 pieces, $69,463 for each mailing of 50,000 to 100,000 pieces, and an additional $6,946 for each additional 10,000 pieces above 100,000 not to exceed $1,389,252. The new penalties will be: $36,334 for each mailing that is less than 50,000 pieces, $72,669 for each mailing of 50,000 to 100,000 pieces, and an additional $7,267 for each additional 10,000 pieces above 100,000 not to exceed $1,453,359.</P>
                <HD SOURCE="HD2">39 U.S.C. 3012(d)—Misleading References to the United States Government; Sweepstakes and Deceptive Mailings</HD>
                <P>Persons sending certain deceptive mail matter described in 39 U.S.C. 3001(h)-(k), including:</P>
                <P>• Solicitations making false claims of Federal Government connection or approval;</P>
                <P>• Certain solicitations for the purchase of a product or service that may be obtained without cost from the Federal Government;</P>
                <P>• Solicitations containing improperly prepared “facsimile checks”; and</P>
                <P>• Certain solicitations for “skill contests” and “sweepstakes” sent to individuals who, in accordance with 39 U.S.C. 3017(d), have requested that such materials not be mailed to them;</P>
                <FP>may be liable to the United States for a civil penalty under 39 U.S.C. 3012(d). Currently, this penalty is not to exceed $13,893 for each mailing. The new penalty will be $14,535.</FP>
                <HD SOURCE="HD2">39 U.S.C. 3017(g)(2)—Commercial Use of Lists of Persons Electing Not To Receive Skill Contest or Sweepstakes Mailings</HD>
                <P>Under 39 U.S.C. 3017(g)(2), the Postal Service may impose a civil penalty against a person who provides information for commercial use about individuals who, in accordance with 39 U.S.C. 3017(d), have elected not to receive certain sweepstakes and contest information. Currently, this civil penalty may not exceed $2,778,505 per violation. The new penalty may not exceed $2,906,718 per violation.</P>
                <HD SOURCE="HD2">39 U.S.C. 3017(h)(1)(A)—Reckless Mailing of Skill Contest or Sweepstakes Matter</HD>
                <P>Currently, under 39 U.S.C. 3017(h)(1)(A) and its implementing regulations, any promoter who recklessly mails nonmailable skill contest or sweepstakes matter may be liable to the United States in the amount of $13,893 per violation for each mailing to an individual. The new penalty is $14,535 per violation.</P>
                <HD SOURCE="HD2">39 U.S.C. 3018(c)(1)(A)—Hazardous Material</HD>
                <P>Under 39 U.S.C. 3018(c)(1)(A), the Postal Service may impose a civil penalty payable into the Treasury of the United States on a person who knowingly mails nonmailable hazardous materials or fails to follow postal laws on mailing hazardous materials. Currently, this civil penalty is at least $300, but not more than $119,786 for each violation. The new penalty is at least $314, but not more than $125,314 for each violation.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 39 CFR Part 233</HD>
                    <P>Administrative practice and procedure, Banks, Banking, Credit, Crime, Infants and children, Law enforcement, Penalties, Privacy, Seizures and forfeitures.</P>
                </LSTSUB>
                <P>For the reasons set out in this document, the Postal Service amends 39 CFR part 233 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 233—INSPECTION SERVICE AUTHORITY</HD>
                </PART>
                <REGTEXT TITLE="39" PART="233">
                    <AMDPAR>1. The authority citation for 39 CFR part 233 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>39 U.S.C. 101, 102, 202, 204, 401, 402, 403, 404, 406, 410, 411, 1003, 3005(e)(1), 3012, 3017, 3018; 12 U.S.C. 3401-3422; 18 U.S.C. 981, 983, 1956, 1957, 2254, 3061; 21 U.S.C. 881; Pub. L. 101-410, 104 Stat. 890 (28 U.S.C. 2461 note); Pub. L. 104-208, 110 Stat. 3009; Secs. 106 and 108, Pub. L. 106-168, 113 Stat. 1806 (39 U.S.C. 3012, 3017); Pub. L. 114-74, 129 Stat. 584.</P>
                    </AUTH>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 233.12</SECTNO>
                    <SUBJECT> [Amended] </SUBJECT>
                </SECTION>
                <REGTEXT TITLE="39" PART="233">
                    <AMDPAR>2. In § 233.12:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), remove “$69,463” and add in its place “$72,669”, remove “$138,925” and add in its place “$145,335”, remove “$13,893” and add in its place “$14,535”, and remove “$2,778,505” and add in its place “$2,906,718”.</AMDPAR>
                    <AMDPAR>b. In paragraph (b), remove “$34,731” and add in its place “$36,334”, remove “$69,463” and add in its place “$72,669”, remove “$6,946” and add in its place “$7,267”, and remove “$1,389,252” and add in its place “$1,453,359”.</AMDPAR>
                    <AMDPAR>c. In paragraph (c)(4), remove “$13,893” and add in its place “$14,535”.</AMDPAR>
                    <AMDPAR>d. In paragraph (d), remove “$2,778,505” and add in its place “$2,906,718”.</AMDPAR>
                    <AMDPAR>e. In paragraph (e), remove “$13,893” and add in its place “$14,535”.</AMDPAR>
                    <AMDPAR>
                        f. In § 233.12(f), remove “$300” and add in its place “$314” and remove 
                        <PRTPAGE P="20806"/>
                        “$119,786” and add in its place “$125,314”.
                    </AMDPAR>
                </REGTEXT>
                <SIG>
                    <NAME>Ruth Stevenson,</NAME>
                    <TITLE>Attorney, Federal Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09436 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">POSTAL REGULATORY COMMISSION</AGENCY>
                <CFR>39 CFR Part 3050</CFR>
                <DEPDOC>[Docket No. RM2018-1; Order No. 5086]</DEPDOC>
                <SUBJECT>Periodic Reporting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Postal Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Commission adopts final rules that require the Postal Service to provide information about cost and service issues affecting flats-shaped mail (flats). The Commission intends to analyze this information over time to identify trends and measurable goals that will lead to the development of a plan to improve these cost and service issues.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective June 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        For additional information, Order No. 5086 can be accessed electronically through the Commission's website at 
                        <E T="03">https://www.prc.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David A. Trissell, General Counsel, at 202-789-6820.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Background</FP>
                    <FP SOURCE="FP-2">II. Basis and Purpose of Final Rules</FP>
                    <FP SOURCE="FP-2">III. Final Rules</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Background</HD>
                <P>On March 1, 2019, the Commission proposed specific reporting requirements to facilitate measuring and tracking cost and service performance issues related to flats. The Commission adopts final rules on these requirements, with minor revisions to the proposed rules as described below.</P>
                <HD SOURCE="HD1">II. Basis and Purpose of Final Rules</HD>
                <P>The Commission initiated this proceeding to explore potential enhancements to the Postal Service's data systems and to facilitate the development of consistent reporting requirements to measure, track, and report cost and service performance issues related to flats. With the adoption of these rules, the Postal Service will be required to annually file data at the national, and facility level data (when specified). These reporting requirements are designed to provide sufficient information to improve transparency into the cost and service issues associated with flats. In addition, the reporting requirements will increase the accountability of the Postal Service related to operational initiatives related to flats.</P>
                <P>The final rules incorporate many of the suggestions identified by commenters, as well as additional clarifying language added by the Commission; however, the substance of the rules remains unchanged.</P>
                <P>The Commission revises paragraphs (b) through (g) to extend the filing date to 95 days after the end of the fiscal year.</P>
                <P>Paragraph (b) of proposed § 3050.50 is modified in several ways. First, in § 3050.50(b)(2), the Commission removes the word “estimate,” as the Commission expects the Postal Service to use the actual unit attributable costs for each product. Second, in § 3050.50(b)(4), the Commission clarifies that the comparison should be conducted as the percentage change in unit attributable costs, and the Commission makes additional minor clarifications to the language. Third, in § 3050.50(b)(5), the Commission removes the word “current” and adds the word “changes” after “mail mix” for clarity. The Commission expands the reporting requirement for § 3050.50(b)(5) to provide data from FY 2013 to present. In addition, the Commission clarifies in § 3050.50(b)(5)(ii) through (iii) that the calculation should be for combined flat-shaped products rather than each flat-shaped product. Fourth, the Commission adds a requirement in § 3050.50(b)(5) that the Postal Service explain the methodology used to calculate mail mix changes. Finally, the Commission modifies § 3050.50(b)(6) and (7) to make clear that that the Postal Service must identify the drivers of changes in the result of the analyses.</P>
                <P>Paragraph (e) of proposed § 3050.50 is clarified, as suggested by the Postal Service, to indicate the appropriate five years of historical data that the Commission is requesting. In addition, paragraph (e) of proposed § 3050.50 is supplemented with a rule for instances where a specific report name may change, and additional reporting required when a report name change occurs.</P>
                <P>Paragraph (f) of proposed § 3050.50 is modified to ensure that the Postal Service reports on operational changes and/or initiatives that will have any impact on flat-shaped mail operations, flat-shaped mail costs, and/or flat-shaped mail service.</P>
                <P>Paragraph (g) of proposed § 3050.50 is modified to ensure that the Postal Service reports on data enhancements that will have any impact on measuring, tracking, and/or reporting on flat-shaped mail costs, operations, and/or service.</P>
                <P>Finally, the Commission incorporates the majority of the suggested formatting edits to the rules provided by the Public Representative in Attachment A to her comments.</P>
                <HD SOURCE="HD1">III. Final Rules</HD>
                <P>The Commission places the reporting requirements for flat-shaped mail products in a new section in 39 CFR part 3050.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects for 39 CFR Part 3050</HD>
                    <P>Administrative practice and procedure, Postal Service.</P>
                </LSTSUB>
                <P>For the reasons stated in the preamble, the Commission amends chapter III of title 39 of the Code of Federal Regulations as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 3050—PERIODIC REPORTING</HD>
                </PART>
                <REGTEXT TITLE="39" PART="3050">
                    <AMDPAR>1. The authority citation for part 3050 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 39 U.S.C. 503, 3651, 3652, 3653.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="39" PART="3050">
                    <AMDPAR>2. Add § 3050.50 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 3050.50</SECTNO>
                        <SUBJECT> Information pertaining to cost and service for flat-shaped mail.</SUBJECT>
                        <P>(a) The reports in paragraphs (b) through (f) of this section shall be filed with the Commission at the times indicated.</P>
                        <P>(b) Within 95 days after the end of each fiscal year, the Postal Service shall file a financial report that analyzes data from the fiscal year for all mail products that consist of more than 80 percent flat-shaped mail. At a minimum, the report shall include:</P>
                        <P>(1) Volume and shape workpapers that identify products that contain more than 80 percent flat-shaped mail (flat-shaped products).</P>
                        <P>(2) Unit attributable cost workpapers for each flat-shaped product that is disaggregated into the following cost categories: Mail processing unit cost, delivery unit cost, vehicle service driver unit cost, purchased transportation unit cost, window service unit cost, and other unit cost.</P>
                        <P>(3) A narrative that explains the methodology used to calculate the unit attributable cost categories described in paragraph (b)(2) of this section.</P>
                        <P>
                            (4) A narrative supported by workpapers that identifies flat-shaped products for which the percentage change in average unit attributable cost was greater than the percentage change in total market dominant average unit attributable cost for the same fiscal year. The narrative must include 
                            <PRTPAGE P="20807"/>
                            identification of cost categories that are driving above average change in unit attributable cost for flat-shaped product and a specific plan to reduce unit attributable cost for the identified flat-shaped product.
                        </P>
                        <P>(5) An analysis of volume trends, and mail mix changes for flat-shaped products from FY 2013 to present, which includes, at a minimum, a comparison of:</P>
                        <P>(i) The aggregate unit attributable costs for combined flat-shaped products for each fiscal year,</P>
                        <P>(ii) The calculated estimate of aggregate unit attributable costs for combined flat-shaped products for each fiscal year, using FY 2013 fiscal year's volume distribution,</P>
                        <P>(iii) A narrative that identifies drivers of changes in volume trends and mail mix, and</P>
                        <P>(iv) A narrative that explains the methodology used to calculate the estimated unit attributable cost described in paragraph (b)(5)(ii) of this section.</P>
                        <P>(6) An analysis of the Flat Sequencing System (FSS), which includes, at a minimum, the percent of flat-shaped mail destinating in a FSS zone that were not finalized on FSS equipment, the cost of processing flat-shaped mail on the FSS, and the delivery point sequence (DPS) percentage of FSS mail. In addition, a narrative that identifies drivers of changes in the results of the analysis between fiscal years.</P>
                        <P>(7) A manual processing analysis, which includes, at a minimum, the cost of manually processing flat-shaped mail, the percent of flat-shaped mail that was manually processed, and the percent of flat-shaped mail that was entered at automation prices. In addition, a narrative that identifies drivers of changes in the results of the analysis between fiscal years.</P>
                        <P>(8) An estimate, with supporting workpapers, of the cost impact of bundle processing on flat-shaped products for the fiscal year. If no estimate is available, provide a timeline to estimate the cost impact of bundle processing on flat-shaped products.</P>
                        <P>(9) An estimate, with supporting workpapers, of the cost impact of low productivity on automated equipment on flat-shaped products for the fiscal year. If no estimate is available, provide a timeline to estimate the cost impact of low productivity on automated equipment on flat-shaped products.</P>
                        <P>(10) An estimate, with supporting workpapers, of the cost impact of manual processing on flat-shaped products for the fiscal year. If no estimate is available, provide a timeline to estimate the cost impact of manual processing on flat-shaped products.</P>
                        <P>(11) An estimate, with supporting workpapers, of the cost impact of allied operations on flat-shaped products for the fiscal year. If no estimate is available, provide a timeline to estimate the cost impact of allied operations on flat-shaped products.</P>
                        <P>(12) An estimate, with supporting workpapers, of the cost impact of transportation on flat-shaped products for the fiscal year. If no estimate is available, provide a timeline to estimate the cost impact of transportation on flat-shaped products.</P>
                        <P>(13) An estimate, with supporting workpapers, of the cost impact of last mile/delivery on flat-shaped products for the fiscal year. If no estimate is available, provide a timeline to estimate the cost impact of last mile/delivery on flat-shaped products.</P>
                        <P>(c) Within 95 days after the end of each fiscal year, the Postal Service shall file a service report that analyzes data from the fiscal year for all mail products that consist of more than 80 percent flat-shaped mail. At a minimum, the analysis must include:</P>
                        <P>(1) Service performance scores for all flat-shaped products.</P>
                        <P>(2) An estimate, with supporting workpapers, of the service impact of bundle processing on flat-shaped products for the fiscal year. If no estimate is available, provide a timeline to estimate the service impact of bundle processing on flat-shaped products.</P>
                        <P>(3) An estimate, with supporting workpapers, of the service impact of low productivity on automated equipment on flat-shaped products for the fiscal year. If no estimate is available, provide a timeline to estimate the service impact of low productivity on automated equipment on flat-shaped products.</P>
                        <P>(4) An estimate, with supporting workpapers, of the service impact of manual processing on flat-shaped products for the fiscal year. If no estimate is available, provide a timeline to estimate the service impact of manual processing on flat-shaped products.</P>
                        <P>(5) An estimate, with supporting workpapers, of the service impact of allied operations on flat-shaped products for the fiscal year. If no estimate is available, provide a timeline to estimate the service impact of allied operations on flat-shaped products.</P>
                        <P>(6) An estimate, with supporting workpapers, of the service impact of transportation on flat-shaped products for the fiscal year. If no estimate is available, provide a timeline to estimate the service impact of transportation on flat-shaped products.</P>
                        <P>(7) An estimate, with supporting workpapers, of the service impact of last mile/delivery on flat-shaped products for the fiscal year. If no estimate is available, provide a timeline to estimate the service impact of last mile/delivery on flat-shaped products.</P>
                        <P>(d) Within 95 days after the end of each fiscal year, the Postal Service shall file an analysis of costs by operationally relevant grouping from FY 2013 to present.</P>
                        <P>(1) The report shall utilize fiscal year data filed in accordance with § 3050.22, and § 3050.28(c) and (d) and any other data necessary to complete the analysis.</P>
                        <P>(2) The report shall also include a narrative that explains the methodology used to calculate costs by operationally relevant grouping.</P>
                        <P>(e) Within 95 days after the end of each fiscal year, the Postal Service shall file the following reports that include data by both quarter and fiscal year, as well as at the national level and at the facility level unless otherwise specified. The reports shall include, at a minimum, five years of quarterly historical fiscal year data covering the reporting year and the previous four fiscal years.</P>
                        <P>(1) Bundle Breakage Visibility Reports which include, at a minimum, number of bundles processed, number of bundles processed by class, product, facility, and machine type, number of broken bundles; and number of broken bundles by class, product, facility, and machine type.</P>
                        <P>(2) Mail Processing Variance Reports, which include, at a minimum, for each machine type that process flat-shaped mail: Category, plant/facility, volume, actual workhours, earned workhours (target hours), productivity, variance, and percent achieved, and target productivities, including narrative that explains methodology used to develop target.</P>
                        <P>(3) eFlash Report, which includes, at a minimum manual letter and flats volume, manual letter and flats workhours, manual letter and flats cost analysis, manual letter and flats handling time, and manual letter and flats handling cost per piece.</P>
                        <P>(4) Work in Process metrics, which include, at a minimum, measurement of: unload scan to bundle sorter scan, unload scan to tray mechanization scan, bundle sorter scan to mail processing equipment piece scan, tray mechanization scan to next automation scan, and unload scan to first automation scan.</P>
                        <P>
                            (5) First-Class Mail Root Cause Point Impact Report, which includes, at a minimum, root cause, shape, service standard, point impact, rank, results 
                            <PRTPAGE P="20808"/>
                            attributed to air transit Automated Area Distribution Center (AADC)/Area Distribution Center (ADC) processing delays, and results attributed to surface transit AADC/ADC processing delays.
                        </P>
                        <P>(6) SVWeb Report, which includes, at a minimum, on-time departure percentage, on-time arrival percentage, space utilization type by container type, average load percentage, total number of late containers, misrouted containers based on unload scans at unexpected site, National Performance Assessment (NPA) goals, goal achievement, the total score for six required scans, trips on time, space utilization targets, and comparison of fiscal year space utilization to targets.</P>
                        <P>(7) Last Mile Impact Report, which includes, at a minimum, overall on-time score, on-time score at last processing, and last mile impact for all flat-shaped products at each service standard.</P>
                        <P>(8) For each report listed in paragraphs (e)(1) through (7) of this section, the Postal Service shall provide a narrative that describes any changes made to underlying data systems during the fiscal year that impact the methodology used to produce the report.</P>
                        <P>(9) For each report listed in paragraphs (e)(1) through (7) of this section, the Postal Service shall provide a narrative that discusses trends, changes, and reasons for any changes in data within the report.</P>
                        <P>(10) If any of the reports listed in paragraphs (e)(1) through (7) of this section no longer exist by that name in any year, the Postal Service must provide the closest successor to that report to provide the required information. The Postal Service must identify all differences between the original report and the successor report, and provide a narrative that explains the impact of using the successor report opposed to the original report.</P>
                        <P>(f) Within 95 days after the end of each fiscal year, the Postal Service shall file a report that identifies all national operational changes and/or initiatives that occurred during the fiscal year related to flat-shaped mail and all planned national operational changes and/or initiatives for the next fiscal year related to flat-shaped mail. The operational changes and/or initiatives should impact operations related to flat-shaped mail, impact the cost of flat-shaped mail, and/or impact the service of flat-shaped mail.</P>
                        <P>(1) The report shall identify data from paragraphs (b), (c), (d), and/or (e) of this section that will be impacted by each operational change/initiative.</P>
                        <P>(2) The report shall also include an estimate, with supporting workpapers, of the impact of each operational change/initiative on the data selected in paragraph (f)(1) of this section.</P>
                        <P>(g) Within 95 days after the end of each fiscal year, the Postal Service shall file a report that identifies all data enhancements that occurred during the fiscal year related to data systems that affect flat-shaped mail. The data enhancements identified should have an impact on measuring, tracking, and/or reporting on flat-shaped mail cost, operations, and/or service.</P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <P>By the Commission.</P>
                    <NAME>Stacy L. Ruble,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09779 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 7710-FW-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Part 52</CFR>
                <DEPDOC>[EPA-R03-OAR-2016-0309; FRL-9993-31-Region 3]</DEPDOC>
                <SUBJECT>Approval and Promulgation of Air Quality Implementation Plans; Maryland; Reasonably Available Control Technology for Cement Kilns, Revisions to Portland Cement Manufacturing Plant and Natural Gas Compression Station Regulations, and Removal of Nitrogen Oxides Reduction and Trading Program Replaced by Other Programs and Regulations; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; correcting amendment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document corrects an error in the Environmental Protection Agency (EPA) rule language of the March 28, 2018 final rule pertaining to oxides of nitrogen (NO
                        <E T="52">X</E>
                        ) and Reasonably Available Control Technology (RACT), submitted by the State of Maryland.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This final correcting amendment is effective on May 13, 2019.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Marilyn Powers, Planning &amp; Implementation Branch (3AD30), Air &amp; Radiation Division, U.S. Environmental Protection Agency, Region III, 1650 Arch Street, Philadelphia, Pennsylvania 19103. The telephone number is (215) 814-2308. Ms. Powers can also be reached via electronic mail at 
                        <E T="03">powers.marilyn@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On March 28, 2018, (83 FR 13192), EPA published a final rulemaking action announcing approval of several amendments to the Code of Maryland Regulations (COMAR) into the Maryland SIP. The amendments included (but were not limited to): (1) NO
                    <E T="52">X</E>
                     RACT for cement kilns for the 2008 ozone national ambient air quality standards (NAAQS); (2) the removal of obsolete provisions related to the NO
                    <E T="52">X</E>
                     Budget Trading Program; and (3) amendments to the requirements for Portland cement plants and natural gas compressor stations.
                </P>
                <P>
                    In the final rulemaking, EPA inadvertently omitted COMAR 26.11.29.05 from the regulations incorporated by reference into the Code of Federal Regulations at 40 CFR 52.1070. The intent of the rule was to incorporate COMAR 26.11.29 in its entirety, consistent with Maryland's November 24, 2015 submittal, as well as EPA's original analysis of the submittal.
                    <SU>1</SU>
                    <FTREF/>
                     This document corrects the erroneous omission.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         Technical Support Document at 6, in the docket for the original rulemaking action.
                    </P>
                </FTNT>
                <P>
                    In the final rulemaking document published in the 
                    <E T="04">Federal Register</E>
                     on March 28, 2018 (83 FR 13192), on page 13195, in the second and third columns, the revised rule language should have read—“d. Adding the subheading “26.11.29 Control of NO
                    <E T="52">X</E>
                     Emissions from Natural Gas Pipeline Stations” and the entries ”26.11.29.01” through “26.11.29.05”.” Additionally, the table in paragraph (c) of section 52.1070, under the newly-added heading “26.11.29 Control of NO
                    <E T="52">X</E>
                     emissions from Natural Gas Pipeline Stations” should have included COMAR 26.11.29.05.
                </P>
                <HD SOURCE="HD1">Need for Correction</HD>
                <P>
                    As published, the final rule failed to fully incorporate Maryland's proposed SIP revision as it was submitted and as EPA intended to approve. Section 553 of the Administrative Procedure Act, 5 U.S.C. 553(b)(3)(B), provides that, when an agency for good cause finds that notice and public procedure are impracticable, unnecessary or contrary to the public interest, the agency may issue a rule without providing notice and an opportunity for public comment. EPA has determined that there is good cause for making this rule final without prior proposal and opportunity for comment because we are merely correcting an incorrect citation in a previous action which underwent notice and comment rulemaking. Thus, notice and public procedure are unnecessary. EPA finds that this constitutes good cause under 5 U.S.C. 553(b)(3)(B).
                    <PRTPAGE P="20809"/>
                </P>
                <HD SOURCE="HD1">Corrections of Publication</HD>
                <P>
                    <E T="03">In this Final rule:</E>
                     Correction, EPA is amending 40 CFR 52.1070 to incorporate COMAR 26.11.29.05 by reference, as was initially intended.
                </P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    In this rule, EPA is finalizing regulatory text that includes incorporation by reference. In accordance with requirements of 1 CFR 51.5, EPA is finalizing the incorporation by reference of the revisions to Maryland regulations at COMAR 26.11.29 as discussed in this final action, and EPA's original, May 28, 2018 final action (83 FR 13192). EPA has made, and will continue to make, these materials generally available through 
                    <E T="03">http://www.regulations.gov</E>
                     and at the EPA Region III Office (please contact the person identified in the 
                    <E T="02">For Further Information Contac</E>
                    t section of this preamble for more information). Therefore, these materials have been approved by EPA for inclusion in the SIP, have been incorporated by reference by EPA into that plan, are fully federally enforceable under sections 110 and 113 of the CAA as of the effective date of the final rulemaking of EPA's approval, and will be incorporated by reference by the Director of the Federal Register in the next update to the SIP compilation.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         62 FR 27968 (May 22, 1997).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Statutory and Executive Order Reviews</HD>
                <P>
                    Under Executive Order (E.O.) 12866 (58 FR 51735, October 4, 1993), this action is not a significant regulatory action and is therefore not subject to review by the Office of Management and Budget. For this reason, this action is also not subject to Executive Order 13211, “Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use” (66 FR 28355, May 22, 2001). Because the agency has made a good cause finding that this action is not subject to notice-and-comment requirements under the Administrative Procedures Act or any other statute as indicated in the Supplementary Information section above, it is not subject to the regulatory flexibility provisions of the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ), or to sections 202 and 205 of the Unfunded Mandates Reform Act of 1995 (UMRA) (Pub. L. 104-4). In addition, this action does not significantly or uniquely affect small governments or impose a significant intergovernmental mandate, as described in sections 203 and 204 of UMRA. This rule also does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes, as specified by Executive Order 13175 (65 FR 67249, November 9, 2000), nor will it 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 governments, as specified by Executive Order 13132 (64 FR 43255, August 10, 1999). This rule also is not subject to Executive Order 13045 (62 FR 19885, April 23, 1997), because it is not economically significant.
                </P>
                <P>
                    This technical correction action does not involve technical standards; thus, the requirements of section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) do not apply. The rule also does not involve special consideration of environmental justice related issues as required by Executive Order 12898 (59 FR 7629, February 16, 1994). In issuing this rule, EPA has taken the necessary steps to eliminate drafting errors and ambiguity, minimize potential litigation, and provide a clear legal standard for affected conduct, as required by section 3 of Executive Order 12988 (61 FR 4729, February 7, 1996). EPA has complied with Executive Order 12630 (53 FR 8859, March 15, 1998) by examining the takings implications of the rule in accordance with the “Attorney General's Supplemental Guidelines for the Evaluation of Risk and Avoidance of Unanticipated Takings” issued under the executive order. This rule does not impose an information collection burden under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq</E>
                    ).
                </P>
                <P>
                    The Congressional Review Act (5 U.S.C. 801 
                    <E T="03">et seq.</E>
                    ), as added by the Small Business Regulatory Enforcement Fairness Act of 1996, 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. Section 808 allows the issuing agency to make a rule effective sooner than otherwise provided by the CRA if the agency makes a good cause finding that notice and public procedure is impracticable, unnecessary or contrary to the public interest. This determination must be supported by a brief statement. 5 U.S.C. 808(2). As stated previously, EPA had made such a good cause finding, including the reasons therefore, and established an effective date of May 13, 2019. EPA will submit a report 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 prior to publication of the rule in the 
                    <E T="04">Federal Register</E>
                    . This correction to 40 CFR 52.1070 for Maryland is not a “major rule” as defined by 5 U.S.C. 804(2).
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 52</HD>
                    <P>Environmental protection, Air pollution control, Incorporation by reference, Nitrogen dioxide, Ozone, Particulate matter, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: April 25, 2019. </DATED>
                    <NAME>Cosmo Servidio, </NAME>
                    <TITLE>Regional Administrator, Region III.</TITLE>
                </SIG>
                <P>40 CFR part 52 is amended as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 52—APPROVAL AND PROMULGATION OF IMPLEMENTATION PLANS</HD>
                </PART>
                <REGTEXT TITLE="40" PART="52">
                    <AMDPAR>1. The authority citation for part 52 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                             42 U.S.C. 7401 
                            <E T="03">et seq.</E>
                        </P>
                    </AUTH>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart V—Maryland</HD>
                </SUBPART>
                <REGTEXT TITLE="40" PART="52">
                    <AMDPAR>2. In § 52.1070, the table in paragraph (c) is amended by adding the entry “26.11.29.05” in numerical order to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 52.1070 </SECTNO>
                        <SUBJECT> Identification of plan.</SUBJECT>
                        <STARS/>
                        <P>
                            (c) * * *
                            <PRTPAGE P="20810"/>
                        </P>
                        <GPOTABLE COLS="5" OPTS="L1,i1" CDEF="xs60,r50,12,r50,r50">
                            <TTITLE>Epa—Approved Regulations, Technical Memoranda, and Statutes in the Maryland SIP</TTITLE>
                            <BOXHD>
                                <CHED H="1">
                                    Code of
                                    <LI>Maryland</LI>
                                    <LI>Administrative</LI>
                                    <LI>Regulations</LI>
                                    <LI>(COMAR)</LI>
                                    <LI>citation</LI>
                                </CHED>
                                <CHED H="1">Title/subject</CHED>
                                <CHED H="1">
                                    State
                                    <LI>effective </LI>
                                    <LI>date</LI>
                                </CHED>
                                <CHED H="1">EPA approval date</CHED>
                                <CHED H="1">
                                    Additional explanation/
                                    <LI>citation</LI>
                                    <LI>at 40 CFR 52.1100</LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW EXPSTB="04" RUL="s">
                                <ENT I="21">
                                    <E T="02">26.11.29 Control of NOX Emissions From Natural Gas Pipeline Stations</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">26.11.29.05</ENT>
                                <ENT>Maintaining Records</ENT>
                                <ENT>7/20/2015</ENT>
                                <ENT>3/28/2018, 83 FR 13192</ENT>
                                <ENT/>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09336 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 6560-50-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare and Medicaid Services</SUBAGY>
                <CFR>42 CFR Part 484</CFR>
                <SUBJECT>Home Health Services</SUBJECT>
                <HD SOURCE="HD2">CFR Correction</HD>
                <REGTEXT TITLE="42" PART="484">
                    <AMDPAR>In Title 42 of the Code of Federal Regulations, Part 482 to End, revised as of October 1, 2018, on page 167, in § 484.115, in paragraphs (a)(1) introductory text and (a)(2) introductory text, “January 13, 2017” is corrected to read “January 13, 2018”.</AMDPAR>
                </REGTEXT>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09854 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 1301-00-D</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Office of Inspector General</SUBAGY>
                <CFR>42 CFR Part 1001</CFR>
                <SUBJECT>Program Integrity—Medicare and State Health Care Programs</SUBJECT>
                <HD SOURCE="HD2">CFR Correction</HD>
                <REGTEXT TITLE="42" PART="1001">
                    <AMDPAR>In Title 42 of the Code of Federal Regulations, Part 482 to End, revised as of October 1, 2018, in § 1001.952, on pages 959 through 961, the word “beneficiary” is changed to read “recipient” in the following paragraphs: (x)(5), (y)(4), (y)(5) introductory text, (y)(5)(iii), (y)(5)(v), and (y)(11).</AMDPAR>
                </REGTEXT>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09856 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 1301-00-D</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <CFR>47 CFR Parts 2, 25, and 30</CFR>
                <DEPDOC>[GN Docket No. 14-177; FCC 19-30]</DEPDOC>
                <SUBJECT>Use of Spectrum Bands Above 24 GHz for Mobile Radio Services</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 or FCC) adopts rules for specific millimeter wave bands above 24 GHz in the 
                        <E T="03">Fifth Report and Order.</E>
                         The Commission takes two actions that continue its efforts to make available millimeter wave (mmW) spectrum, at or above 24 GHz, for fifth-generation (5G) wireless, Internet of Things, and other advanced spectrum-based services, including satellite broadband services. First, the Commission establishes rules to allow Fixed-Satellite Service (FSS) operators such as satellite broadband service operators, to operate with individually licensed earth stations transmitting in the 50.4-51.4 GHz band using criteria identical to those applicable in the 24.75-25.25 GHz band. Second, the Commission establishes a process for the Department of Defense (Department) to operate on a shared basis in the Upper 37 GHz band (37.6-38.6 GHz band) in limited circumstances.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective June 12, 2019.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        John Schauble of the Wireless Telecommunications Bureau, Broadband Division at (202) 418-0797 or 
                        <E T="03">John.Schauble@fcc.gov,</E>
                         Michael Ha of the office of Engineering and Technology, Policy and Rules Division, at 202-418-2099 or 
                        <E T="03">Michael.Ha@fcc.gov,</E>
                         or Jose Albuquerque of the International Bureau, Satellite Division, at 202-418-2288 or 
                        <E T="03">Jose.Albuquerque@fcc.gov</E>
                        . For information regarding the PRA information collection requirements contained in this PRA, contact Cathy Williams, Office of Managing Director, at (202) 418-2918 or 
                        <E T="03">Cathy.Williams@fcc.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a summary of the Commission's Fifth Report and Order GN Docket No. 14-177, FCC 19-30, adopted on April 12, 2019 and released on April 15, 2019. The complete text of this document is available for public inspection and copying from 8 a.m. to 4:30 p.m. Eastern Time (ET) Monday through Thursday or from 8 a.m. to 11:30 a.m. ET on Fridays in the FCC Reference Information Center, 445 12th Street SW, Room CY-A257, Washington, DC 20554. The complete text is available on the Commission's website at 
                    <E T="03">https://docs.fcc.gov/public/attachments/FCC-19-30A1.pdf,</E>
                     or by using the search function on the ECFS web page at 
                    <E T="03">http://www.fcc.gov/cgb/ecfs/</E>
                    . Alternative formats are available to persons with disabilities by sending an email to 
                    <E T="03">fcc504@fcc.gov</E>
                     or by calling the Consumer &amp; Governmental Affairs Bureau at (202) 418-0530 (voice), (202) 418-0432 (tty).
                </P>
                <HD SOURCE="HD1">Final Regulatory Flexibility Analysis</HD>
                <P>
                    The Regulatory Flexibility Act (RFA) requires that an agency prepare a regulatory flexibility analysis for notice and comment rulemakings, unless the agency certifies that “the rule will not, if promulgated, have a significant economic impact on a substantial number of small entities.” Accordingly, the Commission has prepared a Final Regulatory Flexibility Analysis (FRFA) concerning the possible impact of the rule changes contained in this 
                    <E T="03">Fifth Report and Order</E>
                     on small entities.
                    <PRTPAGE P="20811"/>
                </P>
                <HD SOURCE="HD1">Paperwork Reduction Act</HD>
                <P>The requirements in revised § 25.136 (e), (f), and (g) constitute new or modified collections subject to the Paperwork Reduction Act of 1995 (PRA), Public Law 104-13. They 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 the new information collection requirements contained in this proceeding. This document will be submitted to OMB for review under section 3507(d) of the PRA. In addition, the Commission notes that, pursuant to the Small Business Paperwork Relief Act of 2002, the Commission previously sought, but did not receive, specific comment on how the Commission might further reduce the information collection burden for small business concerns with fewer than 25 employees. The Commission describes impacts that might affect small businesses, which includes more businesses with fewer than 25 employees, in the Final Regulatory Flexibility Analysis. In the present document, the Commission has assessed the effects of its filing requirements on satellite providers and finds that these requirements will not impose undue burdens on businesses with fewer than 25 employees. The filing requirements the Commission is imposing are necessary to ensure that the proposed operations will comply with the technical rules the Commission has established and not unduly preclude possible future terrestrial operation in the band.</P>
                <HD SOURCE="HD1">Congressional Review Act</HD>
                <P>
                    The Commission will send a copy of the 
                    <E T="03">Fifth Report and Order,</E>
                     including this FRFA, in a report to Congress and the Government Accountability Office pursuant to the Congressional Review Act, see U.S.C. 801(a)(1)(A).
                </P>
                <P>
                    In addition, the Commission will send a copy of the 
                    <E T="03">Fifth Report and Order,</E>
                     including this FRFA, to the Chief Counsel for Advocacy of the SBA. A copy of the 
                    <E T="03">Fifth Report and Order,</E>
                     and FRFA (or summaries thereof) will also be published in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>1. The Commission takes two actions that continues its efforts to make available millimeter wave (mmW) spectrum, at or above 24 GHz, for 5G wireless, Internet of Things (IoT), and other advanced spectrum-based services, including satellite broadband services. First, the Commission establishes rules authorizing FSS operators such as satellite broadband service operators, to license individual earth stations in the 50.4-51.4 GHz band using criteria identical to those applicable in the 24.75-25.25 GHz band. This action will allow FSS operators to provide additional capacity that can be used to provide faster and more advanced services to their customers. Second, the Commission establishes a process for the Department of Defense (Department) to operate on a shared basis in the Upper 37 GHz band (37.6-38.6 GHz) in limited circumstances. This action will provide certainty to potential applicants as the Commission begins the auction process for the Upper 37 GHz band, the 39 GHz band (38.6-40 GHz band), and the 47 GHz band (47.2-48.2 GHz) later this year.</P>
                <HD SOURCE="HD1">II. Background</HD>
                <P>
                    2. On June 8, 2018, the Commission released the 
                    <E T="03">Third Report &amp; Order</E>
                     (
                    <E T="03">Third R&amp;O</E>
                    ), 83 FR 34478, 
                    <E T="03">Memorandum Opinion and Order</E>
                     (
                    <E T="03">MO&amp;O</E>
                    ), and 
                    <E T="03">Third Further Notice of Proposed Rulemaking</E>
                     (
                    <E T="03">Third FNPRM</E>
                    ), 83 FR 34520, in this proceeding. In relevant parts, the 
                    <E T="03">Third FNPRM</E>
                     proposed permitting the licensing of individual FSS earth stations in the 50.4-51.4 GHz band using criteria identical to those applicable in the 24.75-25.25 GHz band. With respect to the 37 GHz band, the Commission noted that it had adopted rules that establish coordination zones for 14 military sites and three scientific sites identified by the National Telecommunications and Information Administration (NTIA), and it sought comment on “on how best to accommodate coordination zones for future Federal operations at a limited number of additional sites.” In contrast, for the Lower 37 GHz band, the Commission sought comment on a proposed coordination mechanism and alternatives to facilitate co-equal shared use of the Lower 37 GHz band between Federal and non-Federal users, as well as among non-Federal users.
                </P>
                <P>
                    3. The 50.4-51.4 GHz band includes primary Federal and non-Federal allocations for fixed and mobile services, as well as primary Federal and non-Federal allocations for fixed-satellite (Earth-to-space) and mobile satellite (Earth-to-space) services. In 1998, the Commission designated the 50.4-51.4 GHz band for use by wireless (fixed and mobile) services. In the 
                    <E T="03">Spectrum Frontiers FNPRM,</E>
                     81 FR 79894, the Commission proposed to authorize fixed and mobile operations throughout the 50.4-52.6 GHz band in accordance with the part 30 Upper Microwave Flexible Use Service (UMFUS) rules. The Commission also proposed to use geographic area licensing to license UMFUS stations in the band on a Partial Economic Area (PEA) basis and sought comment on sharing with satellite services. The Commission received ten satellite applications or market access requests and 20 earth station applications seeking to use the existing FSS (Earth-to-space) allocation in the 50.4-51.4 GHz band for delivery of broadband services.
                </P>
                <P>
                    4. In the 
                    <E T="03">Third FNPRM,</E>
                     the Commission proposed rules that would permit licensing of individual FSS earth stations in the 50.4-51.4 GHz band using criteria identical to those applicable in the 24.75-25.25 GHz band Specifically, the Commission proposed to apply the permitted aggregate population limits within the specified earth station Power Flux Density (PFD) contour on a per-county basis, similar to the requirement in the 27.5-28.35 GHz band, and to adopt constraints on the number of permitted earth stations on both a per county and a per PEA basis. To reflect these requirements, the Commission proposed to modify § 25.136 of the Commission's rules to include the 50.4-51.4 GHz band. The Commission also proposed to amend footnote NG65 to the U.S. Table of Allocations to include the 50.4-51.4 GHz band, making clear the relative interference protection obligations between the co-primary services.
                </P>
                <P>
                    5. With respect to the Upper 37 GHz band, the entire 37 GHz band is allocated to the fixed and mobile services on a primary basis for Federal and non-Federal use. In the 
                    <E T="03">Spectrum Frontiers R&amp;O,</E>
                     81 FR 79894, the Commission made five decisions addressing the Federal and non-Federal use of the band that are relevant here. First, it adopted service rules to permit non-Federal fixed and mobile terrestrial operation throughout the 37 GHz band. Second, it divided the band into two segments: a lower band segment from 37.0-37.6 GHz (Lower 37 GHz band) and an upper band segment from 37.6-38.6 GHz (Upper 37 GHz band). Third, it made the Lower 37 GHz band available for coordinated co-primary sharing between Federal and non-Federal users. Fourth, it adopted rules to license the Upper 37 GHz band geographically by PEAs in 200 megahertz channel blocks (but changed the band plan to 100 megahertz blocks in the 
                    <E T="03">Spectrum Frontiers Fourth R&amp;O,</E>
                     84 FR 1618). Fifth, it established the coordination zones throughout the entire 37-38.6 GHz band for the 14 military sites and three scientific sites identified by NTIA. While the Commission noted that Federal agencies 
                    <PRTPAGE P="20812"/>
                    still had the ability to add future sites on a coordinated basis, it did not indicate how this could be done.
                </P>
                <P>
                    6. In the 
                    <E T="03">Third FNPRM,</E>
                     the Commission sought comment on how best to accommodate coordination zones for future Federal operations at a limited number of additional sites. The Commission asked whether it should amend its rules to add more specific sites for Federal operations, or whether it should establish a process that would permit Federal entities in the future to identify a limited number of additional sites on an as-needed basis. The Commission also asked whether the coordination zones previously established in its rules might be reduced to better accommodate nearby non-Federal operations without adversely impacting Federal operations at those sites.
                </P>
                <P>
                    7. The Commission received 26 comments and 17 reply comments on the 
                    <E T="03">Third FNPRM</E>
                    . A list of commenters, reply commenters, and parties filing 
                    <E T="03">ex parte</E>
                     submissions relating to the issues are addressed in this 
                    <E T="03">Fifth Report and Order</E>
                    . No petitions for reconsideration of the 
                    <E T="03">Third R&amp;O</E>
                     were filed.
                </P>
                <HD SOURCE="HD1">III. Discussion</HD>
                <HD SOURCE="HD2">A. 50.4-51.4 GHz Band</HD>
                <P>8. AT&amp;T, Boeing, EchoStar, SES, SpaceX, Telesat, TIA, and Viasat, support licensing of individual FSS earth stations in the 50.4-51.4 GHz band. Although not specifically opposed to the idea of allowing earth stations to operate in the 50.4-51.4 GHz band, CTIA, Nokia, and T-Mobile argue that it is premature to adopt rules for sharing between terrestrial and FSS operations before UMFUS service rules are adopted. They urge the Commission to adopt UMFUS service rules either first or simultaneously. In contrast, most satellite operators, asserting that there is no need to delay adopting FSS earth station sharing rules, point to workability in other bands, imminent plans for 50.4-51.4 GHz band satellite deployment, and the need to alleviate the current regulatory uncertainty, which the operators describe as debilitating, particularly given the high cost and long lead time involved in designing and building next-generation satellites. EchoStar and Boeing further encourage the Commission not only to swiftly adopt the proposed rules, but also to proceed with processing pending earth station applications in this band conditioned upon the outcome of the proceeding.</P>
                <P>
                    9. With respect to the terms under which the 50.4-51.4 GHz band would be made available for individually licensed earth stations, there is a split between commenters who support using the same criteria applicable in the 24.75-25.25 GHz band and those who ask the Commission to adopt more permissive criteria. EchoStar, TIA, and AT&amp;T support the criteria contained in the 
                    <E T="03">Third FNPRM,</E>
                     which would allow up to three earth station locations in a given county and a maximum of 15 earth station locations in a given PEA. AT&amp;T, in addition, expressly opposes any relaxation in sharing criteria proposed in the 
                    <E T="03">Third FNPRM,</E>
                     asserting a lack of evidence and justification for disturbing the existing balance between services achieved by the rules introduced in other bands. T-Mobile similarly cautions that the Commission should go no further than the current sharing framework adopted for the 24 GHz band, which it characterizes as a consistent approach across already allocated bands. In contrast, Boeing, SES, SpaceX, and Telesat ask the Commission to adopt more permissive or flexible sharing criteria than the Commission proposed, and they assert that the shorter propagation distances of the 50.4-51.4 GHz band make it suitable for more robust sharing. Similarly, Viasat supports individual licensing of earth stations in the 50.4-51.4 GHz band consistent with the more liberal sharing framework applicable in the 47.2-48.2 GHz band, and it further asks the Commission to clarify that smaller earth stations may be permitted to operate in the 47.2-48.2 GHz and 50.4-51.4 GHz bands on a secondary basis with respect to terrestrial services. Other parties request that the Commission add an allocation for FSS in the 51.4-52.4 GHz band. CCA contends that the Commission should not adopt rules that could prejudice future mobile use.
                </P>
                <P>
                    10. The Commission adopts its proposal to permit licensing of individual FSS earth stations in the 50.4-51.4 GHz band using the criteria the Commission adopted for the 24.75-25.25 GHz band. This action will allow FSS operators to provide faster and more advanced services to their customers. Under those criteria, there may be no more than three earth stations in the 50.4-51.4 GHz band in a county and no more than 15 earth stations in any PEA. The area in which the earth station generates a PFD, at 10 meters above ground level, of greater than or equal to −77.6 dBm/m
                    <SU>2</SU>
                    /MHz, together with the similar area of any other earth station operating in the 50.4-51.4 GHz band in the same county, may not cover, in the aggregate, more than the amount of population specified below:
                </P>
                <GPOTABLE COLS="02" OPTS="L2,tp0,i1" CDEF="s100,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Population within the County where earth station is located</CHED>
                        <CHED H="1">
                            Maximum permitted aggregate population within
                            <LI>
                                − 77.6 dBm/m
                                <SU>2</SU>
                                /MHz PFD contour of earth stations
                            </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Greater than 450,000 </ENT>
                        <ENT>0.1 percent of population in county.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Between 6,000 and 450,000 </ENT>
                        <ENT>450 people.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fewer than 6,000 </ENT>
                        <ENT>7.5 percent of population in county.</ENT>
                    </ROW>
                </GPOTABLE>
                <FP>
                    Furthermore, the area in which the earth station generates a PFD, at 10 meters above ground level, of greater than or equal to −77.6 dBm/m
                    <SU>2</SU>
                    /MHz may not contain any major event venue, urban mass transit route, passenger railroad, or cruise ship port. In addition, that area shall not cross any of the following types of roads, as defined in functional classification guidelines issued by the Federal Highway Administration: Interstate, Other Freeways and Expressways, or Other Principal Arterial.
                </FP>
                <P>
                    11. Although the 50.4-52.6 GHz band remains under consideration for UMFUS licensing, establishing UMFUS service rules will require us to address issues concerning sharing with co-primary Federal services in the 50.4-52.6 GHz band, as well as protection of passive services in the adjacent 50.2-50.4 GHz and 52.6-54.25 GHz bands. In the meantime, the Commission notes that a significant number of FSS operators seek to license space stations and earth stations in the band. As in the case of other bands shared between co-primary terrestrial and fixed-satellite services, (
                    <E T="03">e.g.,</E>
                     24.75-25.25 GHz, 37.5-40 GHz and 47.2-48.2 GHz), the Commission finds that, where an FSS allocation already exists in the 50.4-51.4 GHz band, a limited number of individually licensed FSS earth stations can share the 50.4-51.4 GHz band with minimal impact on terrestrial operations in this band. Both the 24 GHz and 50 GHz bands are satellite uplink bands. As in 24 GHz, the limits, the Commission will impose on FSS earth stations in the 50 GHz band will “better provide FSS 
                    <PRTPAGE P="20813"/>
                    with additional capacity for satellite services while permitting substantial terrestrial use of the band.” Throughout this proceeding, the Commission has sought to promote spectrum efficiency by permitting spectrum made available for UMFUS to be shared with other allocated services when possible. The Commission recognizes there are a significant number of pending FSS earth station applications for the 50.4-51.4 GHz band. The Commission agrees that operators in this co-primary service seeking to proceed with system development need this degree of regulatory certainty and should not have to wait while the more complex issues associated with UMFUS licensing are addressed and resolved. Thus, the Commission adopts the proposed rules, which will facilitate sharing between FSS and UMFUS, while the Commission continues to consider the rules for terrestrial operations in the band.
                </P>
                <P>
                    12. At this time, the Commission will not adopt any of the various proposals for increased flexibility for FSS earth station licensing. The Commission recognizes the differences in propagation characteristics between the 50 GHz band and lower frequency bands,
                    <SU>1</SU>
                    <FTREF/>
                     but the Commission concludes that, prior to the adoption of UMFUS licensing rules, it would be premature to extend FSS earth station flexibility beyond the more conservative limits adopted in the 24.75-25.25 GHz band. Accordingly, the Commission modifies § 25.136 of its rules to include the 50.4-51.4 GHz band, thereby applying the identical licensing criteria to these FSS earth stations as are applicable to those in the 24.75-25.25 GHz band. The Commission also makes a minor conforming modification to § 25.130(b)(4) to include this newly modified rule section in the list of rule sections with which FSS transmitting earth station applicants must comply when seeking authorization in bands shared with UMFUS. In addition, the Commission amends footnote NG65 to the U.S. Table of Allocations as proposed to include the 50.4-51.4 GHz band, making clear the relative interference protection obligations between the co-primary services.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Radio signals in the 50 GHz band are more subject to attenuation from oxygen and water vapor than signals in the 24 GHz band. Thus, all other things being equal, radio signals in the 50 GHz band will not travel as far as signals in the 24 GHz band.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Federal Sites in 37-38.6 GHz</HD>
                <P>
                    13. In response to the 
                    <E T="03">Third FNPRM,</E>
                     NTIA, on behalf of the Department, has identified one additional Federal site in the Upper 37 GHz band beyond the 14 military sites and three scientific sites identified in the Commission's rules. Specifically, it requests a small coordination zone around Edwards Air Force Base to the south of Federal facilities in China Lake, California. In addition, NTIA requests the conversion into a single area of the four overlapping coordination zones currently listed in the Table under the China Lake site. NTIA indicates that these changes would simplify the Table to ensure sufficient protection is available for the Department's operations in the China Lake coordination area, as well as ensuring sufficient protection for nearby Edwards Air Force Base, without impacting any Upper 37 GHz licensees' access to the surrounding population centers in southern California. The Commission amends the Table to consolidate the China Lake coordination zones and accommodate Edwards Air Force Base.
                </P>
                <P>14. Further, the Department expects to deploy at additional sites in the future, and the lower 37 GHz band (37.0-37.6 GHz) may not be sufficient. Because of the Commission's forthcoming plans to auction spectrum in this band before the end of the year and because failure to address possible coordination with Federal users could create uncertainty for potential non-Federal bidders in the auction for spectrum in the Upper 37 GHz band, the Commission believes it's critical to address these needs for coordination here.</P>
                <P>15. The Commission recognizes that 5G and other advanced technologies will support a wide variety of applications, including applications that can be used by Federal users. Although the Commission's rules identify the current military sites where licensees would be required to coordinate within a distance of 30 kilometers, the Department expects that there likely will be additional sites where it will need to use the band, but the Department cannot specifically identify these other locations at this time. Unlike the current sites where non-Federal licensees must coordinate with the Department of Defense, the Department seeks to coordinate its use of these additional sites with non-Federal licensees.</P>
                <P>16. Accordingly, the Commission establishes a process that accommodates the military's needs, while protecting the interests of non-Federal licensees in the Upper 37 GHz spectrum band. The Department may submit requests for access to the Upper 37 GHz band for specific additional military bases and ranges, for the purpose of defense applications or national security. Such requests must include a justification regarding why the proposed operations could not be accommodated in the Lower 37 GHz band. The Department is willing to limit its requests to operations that cannot be accommodated in the Lower 37 GHz band. FCC staff will review the request to assess any potential impact on non-Federal licensees, contacting the potentially affected licensees and facilitating direct coordination with the Department and NTIA (including establishing a mechanism for appropriate notice to prospective future successors-in-interest to the affected licensees). The FCC will determine whether the request for access can be accommodated without creating a significant risk of harmful interference to current or planned deployments by potentially affected non-Federal licensees. NTIA would provide the applicable military departments any new or revised frequency assignments that are successfully coordinated. The Commission finds that this process strikes a reasonable balance among the stakeholders.</P>
                <P>
                    17. The Commission recognizes the concerns of commenters that increasing the number of Federal sites in the Upper 37 GHz band, or establishing a process for future Federal sites that lacks sufficient certainty, might negatively affect an auction of the Upper 37 GHz band and the value of the spectrum. The Commission nonetheless finds that the process it adopts here addresses the need for greater certainty for bidders in an auction, especially given the technical characteristics and expected deployments in the Upper 37 GHz band. First, requests by the Department are likely to be relatively rare, as the Commission anticipates that most such operations can be accommodated in the Lower 37 GHz band.
                    <SU>2</SU>
                    <FTREF/>
                     Second, military use, if it cannot be accommodated in the Lower 37 GHz band, will be limited to military bases and ranges, for the purpose of defense applications or national security, and most likely will be in remote areas. Third, the technical characteristics of operations in this region of the spectrum, marked by high path losses and use of advanced antennas and adaptive power control, can minimize any significant impact on licensees' operations. Fourth, as noted above, the FCC, after consultation with 
                    <PRTPAGE P="20814"/>
                    potentially affected licensees, NTIA, and the Department, will determine whether the request for access can be accommodated without creating a significant risk of harmful interference to current or planned deployments by potentially affected non-Federal licensees. Although commenters suggest that the Department's needs can be accommodated by secondary market transactions with non-Federal licensees, the Commission does not find that it would be appropriate for secondary markets to be the sole mechanism for addressing future needs for defense and national security applications. Moreover, the same argument that AT&amp;T raises to support the likelihood of successful Department negotiations on the secondary market—that the Department already has the practical ability to control the deployment of facilities on its military bases and ranges—also supports the likelihood that, under the process described above, non-Federal licensees could successfully negotiate coordination agreements with the Department regarding access to the Upper 37 GHz band at such military sites. Accordingly, the Commission believes that the process it establishes will protect winning bidders from harmful interference while enabling the Department to carry out operations in the Upper 37 GHz band for specific additional military sites on a limited basis.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The Commission is continuing discussions with the Department of Defense on how to effectuate usage of the Lower 37 GHz band, and the Commission intends to take steps towards specifying rules for sharing the band within three months, including exploring whether giving priority access to military use of the 37.0-37.2 GHz band would facilitate usage of the Lower 37 GHz band.
                    </P>
                </FTNT>
                <P>
                    18. The Commission disagrees with T-Mobile's assertion that the process it establishes for coordination of future Department access to the Upper 37 GHz band is inconsistent with the Administrative Procedure Act. First, the Commission provided ample notice in the 
                    <E T="03">Third FNPRM</E>
                     for its decisions. In the 
                    <E T="03">Third FNPRM,</E>
                     the Commission asked not only whether it should amend its rules to add more specific sites for Federal operations, but also whether it should establish a process that would permit Federal entities in the future to identify a limited number of additional sites on an as-needed basis. Second, T-Mobile's assertion that the process the Commission adopts is arbitrary and capricious is based on a description that does not match the process its adopt in light of the record generated, and its need to balance competing objectives under section 309(j) of the Act. The statutory factors the Commission promotes here include, 
                    <E T="03">e.g.,</E>
                     “development and rapid deployment of new technologies, products, and services for the benefit of the public, including those residing in rural areas, without administrative or judicial delays;” and “efficient and intensive use of the electromagnetic spectrum  . . . .” T-Mobile claims that “the proposed process would not include any guidelines for the location or number of additional military sites.” However, the process the Commission adopts is limited to specific locations, 
                    <E T="03">i.e.,</E>
                     military bases and ranges, limits requests solely for the purpose of defense applications or national security, and only in those instances where the Department can justify that its proposed operations cannot by accommodated in the Lower 37 GHz band.
                </P>
                <P>19. In addition, the Commission notes that the Department and the wireless industry are working together to advance spectrum-based technologies through various collaborative efforts, such as their participation in the National Spectrum Consortium and engagement in the Defense Advanced Research Projects Agency Spectrum Collaboration Challenge. Further, the Department and the wireless industry are working together to coordinate operations across many frequency bands, such as in the 3.5 GHz band. The Commission anticipates that those working relationships can facilitate successful coordination of operations in the 37 GHz band.</P>
                <HD SOURCE="HD1">IV. Final Regulatory Flexibility Analysis</HD>
                <P>
                    20. As required by the Regulatory Flexibility Act of 1980, as amended (RFA), an Initial Regulatory Flexibility Analysis (IRFA) was incorporated in the 
                    <E T="03">Third FNPRM</E>
                     released in June 2018 in this proceeding. The Commission sought written public comment on the proposals in the 
                    <E T="03">Third FNPRM,</E>
                     including comments on the IRFA. No comments were filed addressing the IRFA. This present FRFA conforms to the RFA.
                </P>
                <HD SOURCE="HD2">A. Need for, and Objectives of, the Fifth Report and Order</HD>
                <P>
                    21. In the 
                    <E T="03">Fifth Report and Order,</E>
                     the Commission authorizes FSS use of the 50.4-51.4 GHz band for individually licensed earth stations, which will allow FSS operators to provide additional capacity that can be used to provide faster and more advanced services to their customers. In authorizing FSS use of the 50.4-51.4 GHz band for individually licensed earth stations, the Commission will apply the licensing criteria it adopted for the 24.75-25.25 GHz band. Accordingly, in the 
                    <E T="03">Fifth Report and Order</E>
                     the Commission modify § 25.136 of its rules to include the 50.4-51.4 GHz band and make a minor conforming modification to § 25.130(b)(4) to include this newly modified rule section in the list of rules sections that FSS transmitting earth station applicants must comply with when seeking authorization in bands shared with UMFUS. Additionally, the Commission amends footnote NG65 to the U.S. Table of Allocations as proposed to include the 50.4-51.4 GHz band, making clear the relative interference protection obligations between the co-primary services.
                </P>
                <P>22. With regard to Federal use in the 37 GHz band, the Commission establishes a process that accommodates the military's needs, while protecting the interests of non-Federal licensees in the Upper 37 GHz spectrum band. The Department may submit requests for access to the Upper 37 GHz band for specific additional military sites, such as military bases and ranges. Such requests must include a justification regarding why the proposed operations could not be accommodated in the Lower 37 GHz band. The FCC will review the request to assess any potential impact on non-Federal licensees, contacting the potentially affected licensees and facilitating direct coordination with the Department and NTIA (including establishing a mechanism for appropriate notice to prospective future successors-in-interest to the affected licensees). The FCC will determine whether the request for access can be accommodated without creating a significant risk of harmful interference to current or planned deployments by potentially affected non-Federal licensees. This action will accommodate military needs while providing certainty to potential applicants as the Commission begins the auction process for the Upper 37 GHz band, the 39 GHz band (38.6-40 GHz band), and the 47 GHz band (47.2-48.2 GHz) later this year.</P>
                <HD SOURCE="HD2">B. Summary of Significant Issues Raised by Public Comments in Response to the IRFA</HD>
                <P>23. There were no comments filed that specifically addressed the proposed rules and policies presented in the IRFA.</P>
                <HD SOURCE="HD2">C. Response to Comments by the Chief Counsel for Advocacy of the Small Business Administration</HD>
                <P>
                    24. Pursuant to the Small Business Jobs Act of 2010, which amended the RFA, the Commission is required to respond to any comments filed by the Chief Counsel for Advocacy of the Small Business Administration (SBA), and to provide a detailed statement of any change made to the proposed rules as a result of those comments.
                    <PRTPAGE P="20815"/>
                </P>
                <P>25. The Chief Counsel did not file any comments in response to the proposed rules in this proceeding.</P>
                <HD SOURCE="HD2">D. Description and Estimate of the Number of Small Entities To Which the Proposed Rules Will Apply</HD>
                <P>26. The RFA requires the Commission to describe and to estimate 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 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>
                    27. 
                    <E T="03">Small Businesses, Small Organizations, Small Governmental Jurisdictions.</E>
                     The Commission actions, over time, may affect small entities that are not easily categorized at present. The Commission therefore describes here, 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 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 28.8 million businesses.
                </P>
                <P>28. 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.” Nationwide, as of August 2016, there were approximately 356,494 small organizations based on registration and tax data filed by nonprofits with the Internal Revenue Service (IRS).</P>
                <P>29. 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 2012 Census of Governments indicate that there were 90,056 local governmental jurisdictions consisting of general purpose governments and special purpose governments in the United States. Of this number there were 37,132 General purpose governments (county, municipal and town or township) with populations of less than 50,000 and 12,184 Special purpose governments (independent school districts and special districts) with populations of less than 50,000. The 2012 U.S. Census Bureau data for most types of governments in the local government category show that the majority of these governments have populations of less than 50,000. Based on this data the Commission estimates that at least 49,316 local government jurisdictions fall in the category of “small governmental jurisdictions.”</P>
                <P>
                    30. 
                    <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 appropriate size standard under SBA rules is that such a business is small if it has 1,500 or fewer employees. For this industry, U.S. Census Bureau data for 2012 show that there were 967 firms that operated for the entire year. Of this total, 955 firms had employment of 999 or fewer employees and 12 had employment of 1,000 employees or more. Thus, under this category and the associated size standard, the Commission estimates that the majority of wireless telecommunications carriers (except satellite) are small entities.
                </P>
                <P>
                    31. 
                    <E T="03">Fixed Microwave Services.</E>
                     Microwave services include common carrier, private-operational fixed, and broadcast auxiliary radio services. They also include the UMFUS, the mmW service, Local Multipoint Distribution Service (LMDS), the Digital Electronic Message Service (DEMS), and the 24 GHz Service, where licensees can choose between common carrier and non-common carrier status. At present, there are approximately 66,680 common carrier fixed licensees, 69,360 private and public safety operational-fixed licensees, 20,150 broadcast auxiliary radio licensees, 411 LMDS licenses, 33 24 GHz DEMS licenses, 777 39 GHz licenses, and five 24 GHz licensees, and 467 mmW licenses in the microwave services. The Commission has not yet defined a small business with respect to microwave services. The closest applicable SBA category is Wireless Telecommunications Carriers (except Satellite) and the appropriate size standard for this category under SBA rules is that such a business is small if it has 1,500 or fewer employees. For this industry, U.S. Census Bureau data for 2012 shows that there were 967 firms that operated for the entire year. Of this total, 955 had employment of 999 or fewer, and 12 firms had employment of 1,000 employees or more. Thus, under this SBA category and the associated standard, the Commission estimates that the majority of fixed microwave service licensees can be considered small.
                </P>
                <P>32. The Commission does not have data specifying the number of these licensees that have more than 1,500 employees, and thus is unable at this time to estimate with greater precision the number of fixed microwave service licensees that would qualify as small business concerns under the SBA's small business size standard. Consequently, the Commission estimates that there are up to 36,708 common carrier fixed licensees and up to 59,291 private operational-fixed licensees and broadcast auxiliary radio licensees in the microwave services that may be small and may be affected by the rules and policies adopted herein. The Commission notes, however, that both the common carrier microwave fixed, and the private operational microwave fixed licensee categories includes some large entities.</P>
                <P>
                    33. 
                    <E T="03">Satellite Telecommunications.</E>
                     This category 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 category has a small business size standard of $32.5 million or less in average annual receipts, under SBA rules. For this category, U.S. Census Bureau data for 2012 shows that there were a total of 333 firms that operated for the entire year. Of this total, 299 firms had annual receipts of less than $25 million. Consequently, the Commission estimates that the majority of satellite telecommunications providers are small entities.
                </P>
                <P>
                    34. 
                    <E T="03">All Other Telecommunications.</E>
                     The “All Other Telecommunications” category 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 
                    <PRTPAGE P="20816"/>
                    telecommunications to, and receiving telecommunications from, satellite systems. Establishments providing internet services or voice over internet protocol (VoIP) services via client-supplied telecommunications connections are also included in this industry.” The SBA has developed a small business size standard for “All Other Telecommunications,” which consists of all such firms with gross annual receipts of $32.5 million or less. For this category, U.S. Census Bureau data for 2012 shows that there were a total of 1,442 firms that operated for the entire year. Of these firms, a total of 1400 firms had gross annual receipts of under $25 million and 42 firms had gross annual receipts of $25 million to $49, 999,999. Thus, the Commission estimates that a majority of “All Other Telecommunications” firms potentially affected by its actions can be considered small.
                </P>
                <P>
                    35. 
                    <E T="03">Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing.</E>
                     This industry comprises establishments primarily engaged in manufacturing radio and television broadcast and wireless communications equipment. Examples of products made by these establishments are: Transmitting and receiving antennas, cable television equipment, GPS equipment, pagers, cellular phones, mobile communications equipment, and radio and television studio and broadcasting equipment.” The SBA has established a size standard for this industry of 1,250 employees or less. U.S. Census Bureau data for 2012 shows that 841 establishments operated in this industry in that year. Of that number, 828 establishments operated with fewer than 1,000 employees, 7 establishments operated with between 1,000 and 2,499 employees and 6 establishments operated with 2,500 or more employees. Based on this data, the Commission concludes that a majority of manufacturers in this industry is small.
                </P>
                <HD SOURCE="HD2">E. Description of Projected Reporting, Recordkeeping, and Other Compliance Requirements</HD>
                <P>
                    36. The Commission expects the rules adopted in the 
                    <E T="03">Fifth Report and Order</E>
                     will impose new or additional reporting or recordkeeping and/or other compliance obligations on small entities as well as other applicants and licensees. FSS earth station applicants and licensees in the 50.4-51.4 GHz band will be subject to the reporting, recordkeeping, and compliance requirements applicable in the 24.75-25.25 GHz band. When they submit applications for authority to operate earth stations in the 50.4-51.4 GHz band, they will be required to demonstrate that the proposed earth stations comply with technical criteria designed to ensure that the earth stations would not unduly limit possible future terrestrial service. These demands are necessary to ensure that the proposed operations will comply with the technical rules, and not unduly preclude possible future terrestrial operation in the band and will require small businesses as well as other entities that intend to offer such satellite telecommunications services to use professional, accounting, engineering or survey services in order to meet these requirements. To attain consistency with the existing application of the Commission's rules, the reporting, recordkeeping, and other compliance requirements resulting from the Commission's actions in the 
                    <E T="03">Fifth Report and Order</E>
                     will apply to all entities in the same manner.
                </P>
                <HD SOURCE="HD2">F. Steps Taken to Minimize the Significant Economic Impact on Small Entities, and Significant Alternatives Considered</HD>
                <P>37. The RFA requires an agency to describe any significant, specifically small business, alternatives that it has considered in reaching its 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 or reporting requirements under the rule for 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 small entities.</P>
                <P>38. Rather than creating a new framework for the licensing of FSS earth stations in the 50.4-51.4 GHz band, the Commission chose to apply the identical licensing criteria applicable to the 24.75-25.25 GHz band and adopt existing rule sections that FSS transmitting earth station applicants must comply with when seeking authorization in bands shared with UMFUS. These steps will minimize the significant economic impact on small entities by not increasing the cost of compliance with an entirely new set of rules and regulations. Moreover, to the extent an entity is already licensed and operating the 24.75-25.25 GHz band, they may have the processes and procedures and infrastructure in place to facilitate compliance with the Commission's rules, and therefore may only incur minimal incremental costs to comply with the rules adopted for the 50.4-51.4 GHz band.</P>
                <HD SOURCE="HD1">V. Ordering Clauses</HD>
                <P>
                    39. Accordingly, 
                    <E T="03">it is ordered,</E>
                     pursuant to sections 1, 2, 3, 4, 5, 7, 301, 302, 302a, 303, 304, 307, 309, and 310 of the Communications Act of 1934, 47 U.S.C. 151, 152, 153, 154, 155, 157, 301, 302, 302a, 303, 304, 307, 309, and 310, section 706 of the Telecommunications Act of 1996, as amended, 47 U.S.C. 1302, and § 1.411 of the Commission's Rules, 47 CFR 1.411, that this 
                    <E T="03">Fifth Report and Order is hereby adopted.</E>
                </P>
                <P>
                    40. 
                    <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 
                    <E T="03">Fifth Report and Order,</E>
                     including the Final Regulatory Flexibility Analysis, to the Chief Counsel for Advocacy of the Small Business Administration.
                </P>
                <P>
                    41. 
                    <E T="03">It is further ordered</E>
                     that the amendments of the Commission's rules as set forth under Final Rules 
                    <E T="03">are adopted,</E>
                     effective thirty days from the date of publication in the 
                    <E T="04">Federal Register</E>
                    . Section 25.136(e), (f), and (g) contain new or modified information collection requirements that require review by OMB under the PRA. The Commission directs the Bureau to announce the compliance date for those information collections in a document published in the 
                    <E T="04">Federal Register</E>
                     after OMB approval and directs the Bureau to cause § 25.136(h) to be revised accordingly.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Parts 2, 25 and 30</HD>
                    <P>Communications common carriers, Communications equipment, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene Dortch,</NAME>
                    <TITLE>Secretary, Office of the Secretary.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Final Rules</HD>
                <P>For the reasons discussed in the preamble, the Federal Communications Commission amends 47 CFR parts 2, 25 and 30 as follows:</P>
                <PART>
                    <PRTPAGE P="20817"/>
                    <HD SOURCE="HED">PART 2—FREQUENCY ALLOCATIONS AND RADIO TREATY MATTERS; GENERAL RULES AND REGULATIONS</HD>
                </PART>
                <REGTEXT TITLE="47" PART="2">
                    <AMDPAR>1. The authority citation for part 2 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 47 U.S.C. 154, 302a, 303, and 336, unless otherwise noted.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="2">
                    <AMDPAR>2. In § 2.106, the Table of Frequency Allocations is amended as follows:</AMDPAR>
                    <AMDPAR>a. Revise page 60.</AMDPAR>
                    <AMDPAR>b. In the list of non-Federal Government (NG) Footnotes, footnote NG65 is revised.</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 2.106 </SECTNO>
                        <SUBJECT>Table of Frequency Allocations.</SUBJECT>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="20818"/>
                            <GID>ER13MY19.022</GID>
                        </GPH>
                        <PRTPAGE P="20819"/>
                        <HD SOURCE="HD1">Non-Federal Government (NG) Footnotes</HD>
                        <STARS/>
                        <P>NG65 In the bands 24.75-25.25 GHz, 47.2-48.2 GHz, and 50.4-51.4 GHz, stations in the fixed and mobile services may not claim protection from individually licensed earth stations authorized pursuant to 47 CFR 25.136. However, nothing in this footnote shall limit the right of Upper Microwave Flexible Use Service licensees to operate in conformance with the technical rules contained in 47 CFR part 30. The Commission reserves the right to monitor developments and to undertake further action concerning interference between Upper Microwave Flexible Use Service and Fixed-Satellite Service, including aggregate interference to satellite receivers, if appropriate.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 25—SATELLITE COMMUNICATIONS</HD>
                </PART>
                <REGTEXT TITLE="47" PART="25">
                    <AMDPAR>3. The authority citation for part 25 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 47 U.S.C. 154, 301, 302, 303, 307, 309, 310, 319, 332, 605, and 721, unless otherwise noted.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="25">
                    <AMDPAR>4. Amend § 25.130 by revising paragraph (b)(4) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 25.130 </SECTNO>
                        <SUBJECT>Filing requirements for transmitting earth stations.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(4) Applicants for earth stations licensed in accordance with § 25.136 must demonstrate that the transmitting earth stations will meet the relevant criteria specified in that section, including any showings required under § 25.136(a)(4), (c), (d)(4), and/or (e)(4).</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="25">
                    <AMDPAR>5. Amend § 25.136 by:</AMDPAR>
                    <AMDPAR>a. Revising the section heading;</AMDPAR>
                    <AMDPAR>b. In paragraph (c)(2), removing “table 1” and “Table 1” and adding in their place “table 2” and “Table 2”, respectively;</AMDPAR>
                    <AMDPAR>c. In paragraph (d)(4)(ii), removing “table 1” and “Table 1” and adding in their place “table 3” and “Table 3”, respectively;</AMDPAR>
                    <AMDPAR>d. Revising paragraphs (e), (f), and (g); and</AMDPAR>
                    <AMDPAR>e. Adding paragraph (h).</AMDPAR>
                    <P>The revisions and addition read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 25.136 </SECTNO>
                        <SUBJECT>Earth Stations in the 24.75-25.25 GHz, 27.5-28.35 GHz, 37.5-40 GHz, 47.2-48.2, GHz and 50.4-51.4 GHz bands.</SUBJECT>
                        <STARS/>
                        <P>(e) Notwithstanding that FSS is co-primary with the Upper Microwave Flexible Use Service in the 24.75-25.25 GHz and 50.4-51.4 GHz bands, earth stations in these bands shall be limited to individually licensed earth stations. An applicant for a license for a transmitting earth station in the 24.75-25.25 GHz or 50.4-51.4 GHz band must meet one of the following criteria to be authorized to operate without providing any additional interference protection to stations in the Upper Microwave Flexible Use Service:</P>
                        <P>
                            (1) The FSS licensee also holds the relevant Upper Microwave Flexible Use Service license(s) for the area in which the earth station generates a power flux density (PFD), at 10 meters above ground level, of greater than or equal to −77.6dBm/m
                            <SU>2</SU>
                            /MHz;
                        </P>
                        <P>(2) The earth station in the 24.75-25.25 GHz band was authorized prior to August 20, 2018; or the earth station in the 50.4-51.4 GHz band was authorized prior to June 12, 2019; or</P>
                        <P>(3) The application for the earth station in the 24.75-25.25 GHz band was filed prior to August 20, 2018; or the application for the earth station in the 50.4-51.4 GHz band was filed prior to June 12, 2019; or</P>
                        <P>(4) The applicant demonstrates compliance with all of the following criteria in its application:</P>
                        <P>(i) There are no more than two other authorized earth stations operating in the same frequency band within the county where the proposed earth station is located that meet the criteria contained in either paragraph (e)(1), (2), (3), or (4) of this section, and there are no more than 14 other authorized earth stations operating in the same frequency band within the Partial Economic Area where the proposed earth station is located that meet the criteria contained in paragraph (e)(1), (2), (3), or (4) of this section. For purposes of the requirement in this paragraph (e)(4), multiple earth stations that are collocated with or at a location contiguous to each other shall be considered as one earth station;</P>
                        <P>
                            (ii) The area in which the earth station generates a power flux density (PFD), at 10 meters above ground level, of greater than or equal to −77.6 dBm/m
                            <SU>2</SU>
                            /MHz, together with the similar area of any other earth station operating in the same frequency band authorized pursuant to paragraph (e) of this section, does not cover, in the aggregate, more than the amount of population of the county within which the earth station is located as noted in table 4 to this paragraph (e)(4)(ii):
                        </P>
                        <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s100,r100">
                            <TTITLE>
                                Table 4 to Paragraph 
                                <E T="01">(e)(4)(ii)</E>
                            </TTITLE>
                            <BOXHD>
                                <CHED H="1">Population within the County where earth station is located</CHED>
                                <CHED H="1">
                                    Maximum permitted aggregate population within −77.6 dBm/m
                                    <SU>2</SU>
                                    /MHz PFD contour of earth stations
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">Greater than 450,000</ENT>
                                <ENT>0.1 percent of population in county.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Between 6,000 and 450,000</ENT>
                                <ENT>450 people.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Fewer than 6,000</ENT>
                                <ENT>7.5 percent of population in county.</ENT>
                            </ROW>
                        </GPOTABLE>
                        <P>(iii) The area in which the earth station generates a PFD, at 10 meters above ground level, of greater than or equal to −77.6 dBm/m2/MHz does not contain any major event venue, urban mass transit route, passenger railroad, or cruise ship port. In addition, the area mentioned in paragraph (e)(4)(ii) of this section shall not cross any of the following types of roads, as defined in functional classification guidelines issued by the Federal Highway Administration pursuant to 23 CFR 470.105(b): Interstate, Other Freeways and Expressways, or Other Principal Arterial. The Federal Highway Administration Office of Planning, Environment, and Realty Executive Geographic Information System (HEPGIS) map contains information on the classification of roads. For purposes of this paragraph (e)(4), an urban area shall be an Adjusted Urban Area as defined in section 101(a)(37) of Title 21 of the United States Code; and</P>
                        <P>
                            (iv) The applicant has successfully completed frequency coordination with the UMFUS licensees within the area in which the earth station generates a PFD, at 10 meters above ground level, of greater than or equal to −77.6 dBm/m2/MHz with respect to existing facilities constructed and in operation by the UMFUS licensee. In coordinating with UMFUS licensees, the applicant shall use the applicable processes contained in § 101.103(d) of this chapter.
                            <PRTPAGE P="20820"/>
                        </P>
                        <P>(f) If an earth station applicant or licensee in the 24.75-25.25 GHz, 27.5-28.35 GHz, 37.5-40 GHz, 47.2-48.2 GHz and/or 50.4-51.4 GHz bands enters into an agreement with an UMFUS licensee, their operations shall be governed by that agreement, except to the extent that the agreement is inconsistent with the Commission's rules or the Communications Act.</P>
                        <P>(g) Any earth station authorizations issued pursuant to paragraph (a)(4), (c), (d)(4), or (e)(4) of this section shall be conditioned upon operation being in compliance with the criteria contained in the applicable paragraph.</P>
                        <P>
                            (h) Paragraphs (e), (f), and (g) of this section contain new or modified information-collection and recordkeeping requirements. Compliance with these information-collection and recordkeeping requirements will not be required until after approval by the Office of Management and Budget. The Commission will publish a document in the 
                            <E T="04">Federal Register</E>
                             announcing that compliance date and revising this paragraph (h) accordingly.
                        </P>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 30—UPPER MICROWAVE FLEXIBLE USE SERVICE</HD>
                </PART>
                <REGTEXT TITLE="47" PART="30">
                    <AMDPAR>5. The authority citation for part 30 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>47 U.S.C. 151, 152, 153, 154, 301, 303, 304, 307, 309, 310, 316, 332, 1302, unless otherwise noted.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="30">
                    <AMDPAR>6. Amend § 30.205 by:</AMDPAR>
                    <AMDPAR>a. Designating the table in paragraph (b) as table 4;</AMDPAR>
                    <AMDPAR>b. In newly designated table 4 to paragraph (b), revising the entry for “China Lake, CA” and adding an entry for “Edwards AFB, CA” immediately following the entry for “White Sands Missile Range, NM”; and</AMDPAR>
                    <AMDPAR>c. Adding paragraph (c).</AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 30.205 </SECTNO>
                        <SUBJECT>Federal coordination requirements.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <GPOTABLE COLS="3" OPTS="L1,i1" CDEF="s50,xs90,r150">
                            <TTITLE>
                                Table 4 to Paragraph (
                                <E T="01">b</E>
                                )—Coordination Areas for Federal Terrestrial Systems
                            </TTITLE>
                            <BOXHD>
                                <CHED H="1">Location</CHED>
                                <CHED H="1">Agency</CHED>
                                <CHED H="1">
                                    Coordination area
                                    <LI>(decimal degrees)</LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">China Lake, CA</ENT>
                                <ENT>Navy</ENT>
                                <ENT>50 kilometer radius centered on latitude 35.614781 and longitude −117.454309.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">Edwards AFB, CA</ENT>
                                <ENT>Air Force</ENT>
                                <ENT>20 kilometer radius centered on latitude 34.922905 and longitude −117.891219.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                        </GPOTABLE>
                        <P>(c) In addition to the locations listed in table 4 to paragraph (b) of this section, requests may be submitted to the Commission for access to the 37.6-38.6 GHz band for specific additional military bases and ranges for the purpose of defense applications or national security when the proposed military operations cannot be accommodated in the 37-37.6 GHz band.</P>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09426 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 648</CFR>
                <DEPDOC>[Docket No. 151211999-6343-02]</DEPDOC>
                <RIN>RIN 0648-XG900</RIN>
                <SUBJECT>Fisheries of the Northeastern United States; Northeast Multispecies Fishery; Common Pool Measures for Fishing Year 2019; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary rule; possession and trip limit implementation; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS is correcting a temporary rule that implemented measures for Northeast multispecies common pool vessels for the 2019 fishing year. These measures included possession and trip limits and the allocation of zero trips into the Closed Area II Yellowtail Flounder/Haddock Special Access Program for common pool vessels to target yellowtail flounder. The trip limit for Gulf of Maine winter flounder was incorrect.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective May 10, 2019, through April 30, 2020.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Spencer Talmage, Fishery Management Specialist, 978-281-9232.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Need for Correction</HD>
                <P>NMFS published measures for the Northeast multispecies common pool fishery for fishing year 2019 on April 26, 2019 (84 FR 17926). These measures included possession and trip limits for all stocks of regulated multispecies.</P>
                <P>The document incorrectly listed the trip limit for Gulf of Maine (GOM) winter flounder as 2,000 lb (907 kg) per trip, instead of the correct trip limit of 1,000 lb (454 kg) per trip. This correction will not adversely affect fishing operations. The corrected trip limit of 1,000 lb (454 kg) is the same as the 1,000 lb (454 kg) trip limit for the stock in the previous year. The 1,000 lb (454 kg) limit is based on past experience and anticipated fishing effort. There was no discussion of any increase because there was intended to be no change in the limit from the previous fishing year to prevent an overage from occurring in Trimester 1. This correction is necessary to prevent early trimester closures and overages of common pool quotas while facilitating optimized harvest.</P>
                <HD SOURCE="HD1">Correction</HD>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of April 26, 2019, in FR Doc. 2019-08441, on page 17927, table 1, is corrected to read as follows:
                    <PRTPAGE P="20821"/>
                </P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s100,r100">
                    <TTITLE>Table 1—2019 Fishing Year Common Pool Possession and Trip Limits</TTITLE>
                    <BOXHD>
                        <CHED H="1">Stock</CHED>
                        <CHED H="1">2019 Trip limit</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            GB Cod (outside Eastern U.S./Canada Area)
                            <LI O="xl">GB Cod (inside Eastern U.S./Canada Area)</LI>
                        </ENT>
                        <ENT>250 lb (113 kg) per DAS, up to 500 lb (227 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GB Cod [Closed Area II Yellowtail Flounder/Haddock SAP (for targeting haddock)]</ENT>
                        <ENT>500 lb (227 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GOM Cod</ENT>
                        <ENT>50 lb (23 kg) per DAS, up to 100 lb (45 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GB Haddock</ENT>
                        <ENT>100,000 lb (45, 359 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GOM Haddock</ENT>
                        <ENT>500 lb (227 kg) per DAS, up to 1,000 lb (454 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GB Yellowtail Flounder</ENT>
                        <ENT>100 lb (45 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SNE/MA Yellowtail Flounder</ENT>
                        <ENT>100 lb (45 kg) per DAS, up to 200 lb (91 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cape Cod (CC)/GOM Yellowtail Flounder</ENT>
                        <ENT>750 lb (340 kg) per DAS, up to 1,500 lb (680 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">American Plaice</ENT>
                        <ENT>750 lb (340 kg) per DAS, up to 1,500 lb (680 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Witch Flounder</ENT>
                        <ENT>600 lb (272 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GB Winter Flounder</ENT>
                        <ENT>250 lb (113 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GOM Winter Flounder</ENT>
                        <ENT>1,000 lb (454 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SNE/MA Winter Flounder</ENT>
                        <ENT>2,000 lb (907 kg) per DAS, up to 4,000 lb (1814 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Redfish</ENT>
                        <ENT>Unlimited.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">White Hake</ENT>
                        <ENT>1,500 lb (680 kg) per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pollock</ENT>
                        <ENT>Unlimited.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Atlantic Halibut</ENT>
                        <ENT>1 fish per trip.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Windowpane Flounder
                            <LI O="xl">Ocean Pout</LI>
                            <LI O="xl">Atlantic Wolffish</LI>
                        </ENT>
                        <ENT>Possession Prohibited.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Classification</HD>
                <P>The Assistant Administrator for Fisheries, NOAA, finds good cause pursuant to 5 U.S.C. 553(b)(B) and 5 U.S.C. 553(d)(3) to waive prior notice and the opportunity for public comment and the 30-day delayed effectiveness period because it would be contrary to the public interest. This action corrects an error that inadvertently identified the trip limit of GOM winter flounder for the Northeast multispecies common pool fishery at 2,000 lb (907 kg) per trip rather than the correct 1,000 lb (454 kg) per trip.</P>
                <P>Delay of this action would leave the common pool fishery with a trip limit for GOM winter flounder that is too high to control catch and may lead to early closure of a trimester and quota overages. Any overage of the quota for either of the first two trimesters must be deducted from the Trimester 3 quota, which could substantially disrupt the trimester structure and intent to distribute fishing effort across the entire fishing year. An overage reduction in Trimester 3 would further reduce fishing opportunities for common pool vessels and likely result in early closure of Trimester 3. Additionally, any overage of the annual quota would be deducted from common pool's quota for the next fishing year, to the detriment of the fishery.</P>
                <P>For the reasons above, delay of this action for prior notice and the opportunity for public comment and the 30-day delayed effectiveness period would undermine management objectives of the FMP and cause unnecessary negative economic impacts to the common pool fishery.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        16 U.S.C. 1801 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: May 8, 2019.</DATED>
                    <NAME>Alan D. Risenhoover,</NAME>
                    <TITLE>Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09826 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </RULE>
    </RULES>
    <VOL>84</VOL>
    <NO>92</NO>
    <DATE>Monday, May 13, 2019</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="20822"/>
                <AGENCY TYPE="F">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2017-0812; Product Identifier 2016-NM-198-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Airbus SAS Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule; withdrawal.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA withdraws a notice of proposed rulemaking (NPRM) that proposed a new airworthiness directive (AD), which would have applied to all Airbus SAS Model A330-200 Freighter, A330-200, and A330-300 series airplanes. The NPRM would have required reinforcement modifications of various structural parts of the fuselage, and related investigative and corrective actions if necessary. Since the NPRM was issued, we have determined that more restrictive maintenance requirements are necessary and that the NPRM does not adequately address the identified unsafe condition. Accordingly, the NPRM is withdrawn.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        As of May 13, 2019, the proposed rule, which was published in the 
                        <E T="04">Federal Register</E>
                         on September 19, 2017 (82 FR 43715), is withdrawn.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may examine the AD docket on the internet at 
                        <E T="03">http://www.regulations.gov</E>
                         by searching for and locating Docket No. FAA-2017-0812; or in person at the Docket Management Facility between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this AD action, the NPRM (82 FR 43715, September 19, 2017) (“the NPRM”), the regulatory evaluation, any comments received, and other information. The address for the Docket Office (telephone 800-647-5527) is the Docket Management Facility, 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>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Vladimir Ulyanov, Aerospace Engineer, International Section, Transport Standards Branch, FAA, 2200 South 216th St., Des Moines, WA 98198; telephone and fax 206-231-3229.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Discussion</HD>
                <P>
                    We proposed to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) with a NPRM for a new AD for all Airbus SAS Model A330-200 Freighter, A330-200, and A330-300 series airplanes. The NPRM published in the 
                    <E T="04">Federal Register</E>
                     on September 19, 2017 (82 FR 43715). The NPRM would have required reinforcement modifications of various structural parts of the fuselage, and related investigative and corrective actions if necessary. The NPRM was prompted by an evaluation by the design approval holder (DAH) indicating that certain fuselage structures are subject to widespread fatigue damage (WFD). The proposed actions were intended to prevent crack initiation and undetected propagation in the fuselage, which could result in reduced structural integrity of the airplane.
                </P>
                <HD SOURCE="HD1">Actions Since NPRM Was Issued</HD>
                <P>Since we issued the NPRM, Airbus SAS developed new modifications for Model A330-200 Freighter series airplanes and issued associated service information. In addition, for certain required modifications, upper thresholds in flight hours have been defined and the applicability of certain required actions was redefined to certain airplane configurations. In light of these changes, we are considering further rulemaking.</P>
                <HD SOURCE="HD1">Comments</HD>
                <P>We gave the public the opportunity to participate in considering the proposal. The following presents the comments received on the proposal and the FAA's response to each comment.</P>
                <HD SOURCE="HD1">Support for the NPRM</HD>
                <P>The commenters Grant Bingham, Ryan Pearson, Nicole Pfeffer, and Dyess Verfuth indicated their support for the NPRM.</P>
                <HD SOURCE="HD1">Requests To Publish One AD for Each Individual Piece of Service Information</HD>
                <P>American Airlines (AAL) and Delta Airlines (DAL), speaking also on behalf of Hawaiian Airlines, requested that the proposed AD be separated into several ADs, preferably with one AD issued per one piece of service information. All commenters pointed to the extreme difficulty of capturing and tracking the various tasks and compliance times for each airplane configuration on the respective operator's maintenance tracking system. AAL contended that the variety of maintenance thresholds, tasks, and service information that fall under the requirements of one AD would force the development of an untested workaround within their maintenance tracking system. AAL noted that their system is optimally designed for one service bulletin per one AD. DAL further argued that the request to separate this proposed AD into one AD per individual piece of service information was consistently requested by numerous operators since 2014 at Industry Structures Task Group meetings.</P>
                <P>Additionally, both commenters reasoned that if any of the associated service information was revised or the proposed AD was superseded, the resulting update and revision of their own associated internal documentation would cause a substantial burden on the operators. AAL pointed out that such a large-scale revision to compliance documentation may result in unnecessary confusion between the operators and the local FAA authority. AAL went on to note that if an alternate method of compliance were issued for a specific situation or piece of service information, AAL would be obligated to revise their internal documentation as well, resulting in an increased burden on operators.</P>
                <P>
                    AAL also expressed concern that, due to the wide range of maintenance thresholds, the possibility exists that they may never be able to show accomplishment of the proposed AD. AAL explained that in several instances the maintenance thresholds are so high that their airplanes may never reach the threshold specified by certain service information, which may result in the appearance that they have not yet accomplished service information that specifies action at higher thresholds, even as they are complying with other 
                    <PRTPAGE P="20823"/>
                    service information that specifies action at lower thresholds.
                </P>
                <P>We acknowledge the commenters' request and justifications. We have withdrawn this proposed AD. We are considering further rulemaking that clarifies the applicability of modifications to Airbus SAS Model A330-200 Freighter series airplanes and its associated service information, defines upper thresholds in flight hours for certain airplanes, and redefines the applicability of some required actions to certain airplane configurations.</P>
                <HD SOURCE="HD1">Requests To Reference the Latest Service Information</HD>
                <P>AAL and DAL noted that, since the proposed AD was issued, revised service information is available and they have requested that we update the proposed AD to reference the latest service information. The commenters also requested that we revise the proposed AD to include previous revisions of the service information as credit for operators who have already accomplished the proposed actions using those revisions.</P>
                <P>We acknowledge the commenter's requests. We are considering further rulemaking, which would refer to the latest service information available, and, if appropriate, allow previous revisions of the service information as credit for operators who have already accomplished the proposed actions using those revisions.</P>
                <HD SOURCE="HD1">FAA's Conclusions</HD>
                <P>Upon further consideration, we have determined that more restrictive maintenance requirements are necessary and that the NPRM does not adequately address the identified unsafe condition. Accordingly, the NPRM is withdrawn.</P>
                <P>Withdrawal of the NPRM does not preclude the FAA from issuing another related action or commit the FAA to any course of action in the future.</P>
                <HD SOURCE="HD1">Regulatory Impact</HD>
                <P>Since this action only withdraws an NPRM, it is neither a proposed nor a final rule and therefore is not covered under Executive Order 12866, the Regulatory Flexibility Act, or DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979).</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 Withdrawal</HD>
                <P>
                    Accordingly, we withdraw the NPRM, Docket No. FAA-2017-0812, Product Identifier (formerly Directorate Identifier) 2016-NM-198-AD, which was published in the 
                    <E T="04">Federal Register</E>
                     on September 19, 2017 (82 FR 43715).
                </P>
                <SIG>
                    <DATED>Issued in Des Moines, Washington, on May 3, 2019.</DATED>
                    <NAME>Mike Kaszycki,</NAME>
                    <TITLE>Acting Director, System Oversight Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09742 Filed 5-10-19; 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-2019-0204; Product Identifier 2018-CE-042-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Learjet 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>We propose to adopt a new airworthiness directive (AD) for certain Learjet Inc. Model 60 airplanes. This proposed AD was prompted by a report of a reverse thrust command accelerating the airplane instead of decelerating the airplane. The acceleration with reverse thrust commanded occurred when the thrust reverser doors were in the stowed position instead of the deployed position. This proposed AD would require installing a Thrust Reverser (T/R) Voice Command Warning System (VCWS) to alert the crew of a T/R malfunction. We are proposing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We must receive comments on this proposed AD by June 27, 2019.</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">http://www.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>
                        For service information identified in this NPRM, contact Learjet Inc., MS 53, P.O. Box 7707, Wichita, Kansas 67277-7707; telephone: (toll free) 1-866-538-1247; (514) 855-2999; internet: 
                        <E T="03">https://my.businessaircraft.bombardier.com.</E>
                         You may view this service information at the FAA, Policy and Innovation Division, 901 Locust, Kansas City, Missouri 64106. For information on the availability of this material at the FAA, call (816) 329-4148.
                    </P>
                </ADD>
                <HD SOURCE="HD1">Examining the AD Docket</HD>
                <P>
                    You may examine the AD docket on the internet at 
                    <E T="03">http://www.regulations.gov</E>
                     by searching for and locating Docket No. FAA-2019-0204; 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 regulatory evaluation, any comments received, and other information. The street address for Docket Operations (phone: 800-647-5527) is listed above. Comments will be available in the AD docket shortly after receipt.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        James Galstad, Aerospace Engineer, Wichita ACO Branch, 1801 Airport Road, Room 100, Wichita, Kansas 67209; telephone: (316) 946-4135; fax: (316) 946-4107; email: 
                        <E T="03">james.galstad@faa.gov</E>
                         or 
                        <E T="03">Wichita-COS@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    We invite you to send any written relevant data, views, or arguments about this proposal. Send your comments to an address listed under the 
                    <E T="02">ADDRESSES</E>
                     section. Include “Docket No. FAA-2019-0204; Product Identifier 2018-CE-042-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this NPRM. We will consider all comments received by the closing date and may amend this NPRM because of those comments.
                </P>
                <P>
                    We will post all comments we receive, without change, to 
                    <E T="03">http://www.regulations.gov,</E>
                     including any personal information you provide. We will also post a report summarizing each substantive verbal contact we receive about this NPRM.
                </P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>
                    We received a report of a high-speed rejected takeoff involving a Learjet Model 60 airplane that occurred when all four main landing gear (MLG) tires blew out during the takeoff roll. The tires blew out due to internal heat damage consistent with under-inflation, overloading, or a combination of both. Subsequently, damage from tires caused damage to various components, 
                    <PRTPAGE P="20824"/>
                    including the MLG squat switches, brake hydraulic tubes, wheel speed sensor wiring, and anti-skid components. In the event of squat switch wiring failures, thrust reverser operation can be adversely affected. During the subject accident, forward thrust occurred when the thrust reverser doors stowed due to the failure, and at the same time the crew was still commanding reverse thrust. Squat switch wiring can also be damaged by other external factors, such as bird strikes or deer strikes.
                </P>
                <P>We consider this NPRM to be the third of three ADs that are related to each other, and collectively address unsafe conditions that might result from damage to critical components on the landing gear or in the wheel well that affect the braking, spoiler, and thrust reverser systems. AD 2010-11-11, Amendment 39-16316 (75 FR 32255, June 8, 2010), was issued to prevent tire failure, and AD 2013-13-09, Amendment 39-17497 (78 FR 39574, July 2, 2013), was issued to prevent failure of the braking system or adverse operation of the spoiler and reverse thruster system due to external damage, particularly from tire failure, which could result in loss of control of the airplane. This proposed AD would require installing a T/R VCWS to alert the crew of a T/R malfunction. We are proposing this AD to mitigate failure of the engine thrust reverser system.</P>
                <P>This condition, if not addressed, could result in the airplane overrunning the runway or a runway excursion.</P>
                <HD SOURCE="HD1">Related Service Information Under 1 CFR Part 51</HD>
                <P>
                    We reviewed Bombardier Learjet 60 Service Bulletin SB 60-78-9, dated June 25, 2018. The service bulletin contains procedures for installing a T/R VCWS to alert the pilot of a T/R malfunction. 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 the 
                    <E T="02">ADDRESSES</E>
                     section.
                </P>
                <HD SOURCE="HD1">FAA's Determination</HD>
                <P>We are proposing this AD because we evaluated all the relevant information and determined 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</HD>
                <P>This proposed AD would require installing the T/R VCWS.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>We estimate that this proposed AD affects 289 airplanes of U.S. registry.</P>
                <P>We estimate the following costs to comply with this proposed AD:</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,r50,12,12,12">
                    <TTITLE>Estimated costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">
                            Cost per
                            <LI>product</LI>
                        </CHED>
                        <CHED H="1">
                            Cost on U.S.
                            <LI>operators</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Install a T/R VCWS</ENT>
                        <ENT>20 work-hours × $85 per hour = $1,700</ENT>
                        <ENT>$28,274</ENT>
                        <ENT>$29,974</ENT>
                        <ENT>$8,662,486</ENT>
                    </ROW>
                </GPOTABLE>
                <P>According to the manufacturer, some of the costs of this proposed AD may be covered under warranty, thereby reducing the cost impact on affected individuals. We do not control warranty coverage for affected individuals. As a result, we have included all costs in our cost estimate.</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>We are 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>
                <P>This AD is issued in accordance with authority delegated by the Executive Director, Aircraft Certification Service, as authorized by FAA Order 8000.51C. In accordance with that order, issuance of ADs is normally a function of the Compliance and Airworthiness Division, but during this transition period, the Executive Director has delegated the authority to issue ADs applicable to small airplanes, gliders, balloons, airships, domestic business jet transport airplanes, and associated appliances to the Director of the Policy and Innovation Division.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>We 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) Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),</P>
                <P>(3) Will not affect intrastate aviation in Alaska, and</P>
                <P>(4) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The 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 (AD):</AMDPAR>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        <E T="04">Learjet Inc.:</E>
                         Docket No. FAA-2019-0204; Product Identifier 2018-CE-042-AD.
                    </FP>
                    <HD SOURCE="HD1">(a) Comments Due Date</HD>
                    <P>We must receive comments by June 27, 2019.</P>
                    <HD SOURCE="HD1">(b) Affected ADs</HD>
                    <P>
                        None.
                        <PRTPAGE P="20825"/>
                    </P>
                    <HD SOURCE="HD1">(c) Applicability</HD>
                    <P>This AD applies to Learjet Inc. Model 60 airplanes, serial numbers 60-001 through 60-430, certificated in any category.</P>
                    <HD SOURCE="HD1">(d) Subject</HD>
                    <P>Joint Aircraft System Component (JASC)/Air Transport Association (ATA) of America Code 78, Engine Exhaust.</P>
                    <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                    <P>This AD was prompted by a report of a reverse thrust command accelerating the airplane instead of decelerating the airplane because the engine thrust reverser doors were stowed instead of deployed. We are issuing this AD to mitigate failure of the engine thrust reverser system. The unsafe condition, if not addressed, could result in the airplane overrunning the runway or a runway excursion.</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) Install a Thrust Reverser Voice Command Warning System</HD>
                    <P>Within the next 1,200 hours time-in-service or within the next 48 months after the effective date of this AD, whichever occurs first, install a Thrust Reverser Voice Command Warning System and perform a functional test in accordance with sections 3.A. through 3.C. of the Accomplishment Instructions in Bombardier Learjet 60 Service Bulletin SB 60-78-9, dated June 25, 2018.</P>
                    <HD SOURCE="HD1">(h) Alternative Methods of Compliance (AMOCs)</HD>
                    <P>(1) The Manager, Wichita ACO 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 certification office, send it to the attention of the person identified in paragraph (i) of this AD.</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">(i) Related Information</HD>
                    <P>
                        (1) For more information about this AD, contact James Galstad, Aerospace Engineer, Wichita ACO Branch, 1801 Airport Road, Room 100, Wichita, Kansas 67209; telephone: (316) 946-4135; fax: (316) 946-4107; email: 
                        <E T="03">james.galstad@faa.gov</E>
                         or 
                        <E T="03">Wichita-COS@faa.gov.</E>
                    </P>
                    <P>
                        (2) For service information identified in this AD, contact Learjet Inc., MS 53, P.O. Box 7707, Wichita, Kansas 67277-7707; telephone: (toll free) 1-866-538-1247; (514) 855-2999; internet: 
                        <E T="03">https://my.businessaircraft.bombardier.com.</E>
                         You may view this service information at the FAA, Policy and Innovation Division, 901 Locust, Kansas City, Missouri 64106. For information on the availability of this material at the FAA, call (816) 329-4148.
                    </P>
                </EXTRACT>
                <SIG>
                    <DATED>Issued in Kansas City, Missouri, on May 3, 2019.</DATED>
                    <NAME>Melvin J. Johnson,</NAME>
                    <TITLE>Aircraft Certification Service, Deputy Director, Policy and Innovation Division, AIR-601.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09689 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[Docket Number USCG-2019-0212]</DEPDOC>
                <RIN>RIN 1625-AA00</RIN>
                <SUBJECT>Safety Zone; Tall Ships Challenge Great Lakes 2019, Buffalo, NY, Cleveland, OH, Bay City, MI, Green Bay, WI, Sturgeon Bay, WI, Kenosha, WI and Erie, PA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard proposes to create safety zones around each tall ship visiting the Great Lakes during the Tall Ships Challenge 2019 race series. These safety zones will provide for the regulation of vessel traffic in the vicinity of each tall ship in the navigable waters of the United States. The Coast Guard is taking this action to safeguard participants and spectators from the hazards associated with the limited maneuverability of these tall ships and to ensure public safety during tall ships events. We invite your comments on this proposed rulemaking.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments and related material must be received by the Coast Guard on or before June 12, 2019.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments identified by docket number USCG-2019-0212 using the Federal eRulemaking Portal at 
                        <E T="03">https://www.regulations.gov</E>
                        . See the “Public Participation and Request for Comments” portion of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for further instructions on submitting comments.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions about this proposed rulemaking, call or email LT Jason Radcliffe, 9th District Waterways Management, U.S. Coast Guard; telephone 216-902-6060, email 
                        <E T="03">jason.a.radcliffe2@uscg.mil</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Table of Abbreviations</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">CFR Code of Federal Regulations</FP>
                    <FP SOURCE="FP-1">DHS Department of Homeland Security</FP>
                    <FP SOURCE="FP-1">FR Federal Register</FP>
                    <FP SOURCE="FP-1">NPRM Notice of proposed rulemaking</FP>
                    <FP SOURCE="FP-1">§ Section </FP>
                    <FP SOURCE="FP-1">U.S.C. United States Code</FP>
                </EXTRACT>
                <HD SOURCE="HD1">II. Background, Purpose, and Legal Basis</HD>
                <P>
                    During the Tall Ships Challenge Great Lakes 2019, tall ships will be participating in maritime parades, training cruises, races, and mooring in the harbors of Buffalo, NY, Cleveland, OH, Bay City, MI, Green Bay, WI, Sturgeon Bay, WI, Kenosha, WI and Erie, PA. This is a tri-annual event that teaches character building and leadership through sail training. The Tall Ships event seeks to educate the public about both the historical aspects of sailing ships as well as their current use as training vessels for students. Tall ships are large, traditionally-rigged sailing vessels. The event will consist of festivals at each port of call, sail training cruises, tall ship parades, and races between the ports. More information regarding the Tall Ships Challenge 2019 and the participating vessels can be found at: 
                    <E T="03">https://tallshipsnetwork.com/series/tall-ships-challenge-great-lakes-2019/</E>
                    .
                </P>
                <P>At 12:01 a.m. June 28, 2019, a safety zone will be established around each tall ship participating in this event. The safety zone around each ship will remain in effect as the tall ships travel throughout the Great Lakes. The safety zones will terminate at 12:01 a.m. on September 2, 2019.</P>
                <P>
                    These safety zones are necessary to protect the tall ships from potential harm and to protect the public from the hazards associated with the limited maneuverability of tall sailing ships. When operating under sail, they require a substantial crew to manually turn the rudder and adjust the sails, therefore they cannot react as quickly as modern ships. Additionally, during parades of sail, the tall ships will be following a set course through a crowded harbor, and it is imperative that spectator craft stay clear since maneuvering the tall ships to avoid large crowds of spectator craft would not be possible. Due to the high profile nature and extensive publicity associated with this event, each Captain of the Port (COTP) expects a large number of spectators in confined areas adjacent to the tall ships. The combination of large numbers of recreational boaters, congested waterways, boaters crossing commercially transited waterways and low maneuverability of the tall ships could easily result in serious injuries or fatalities. Therefore, the Coast Guard will enforce a safety zone around each 
                    <PRTPAGE P="20826"/>
                    ship to ensure the safety of both participants and spectators in these areas. The Coast Guard is proposing this rulemaking under authority in 46 U.S.C. 70034, 70051; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; Department of Homeland Security Delegation No. 0170.1.
                </P>
                <HD SOURCE="HD1">III. Discussion of Proposed Rule</HD>
                <P>The Coast Guard proposes to establish safety zones from 12:01 a.m. on June 28, 2019 until 12:01 a.m. on September 2, 2019. The safety zones would cover all navigable waters within 100 yards of a tall ship in the Great Lakes. The duration of the zone is intended to ensure the safety of vessels and these navigable waters during the 2019 Tall Ships Challenge. No vessel or person would be permitted to enter the safety zone without obtaining permission from the COTP or a designated representative. If the tall ships are operating in a confined area such as a small harbor and there is not adequate room for vessels to stay out of the safety zone because of a lack of navigable water, then vessels will be permitted to operate within the safety zone and shall travel at the minimum speed necessary to maintain a safe course. The navigation rules shall apply at all times within the safety zone. The regulatory text we are proposing appears at the end of this document.</P>
                <HD SOURCE="HD1">IV. Regulatory Analyses</HD>
                <P>We developed this proposed rule after considering numerous statutes and Executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes and Executive orders and we discuss First Amendment rights of protestors.</P>
                <HD SOURCE="HD2">A. Regulatory Planning and Review</HD>
                <P>Executive Orders 12866 and 13563 direct agencies to assess the costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits. Executive Order 13771 directs agencies to control regulatory costs through a budgeting process. This NPRM has not been designated a “significant regulatory action,” under Executive Order 12866. Accordingly, the NPRM has not been reviewed by the Office of Management and Budget (OMB), and pursuant to OMB guidance it is exempt from the requirements of Executive Order 13771.</P>
                <P>This regulatory action determination is based on the size, location, duration, and time-of-day of the safety zone. Vessel traffic would be able to safely transit around this safety zone or through it at slow speed in congested areas. Moreover, the Coast Guard would issue a Broadcast Notice to Mariners via VHF-FM marine channel 16 about the zone, and the rule would allow vessels to seek permission to enter the zone.</P>
                <HD SOURCE="HD2">B. Impact on Small Entities</HD>
                <P>The Regulatory Flexibility Act of 1980, 5 U.S.C. 601-612, as amended, requires Federal agencies to consider the potential impact of regulations on small entities during rulemaking. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. The Coast Guard certifies under 5 U.S.C. 605(b) that this proposed rule would not have a significant economic impact on a substantial number of small entities.</P>
                <P>While some owners or operators of vessels intending to transit the safety zone may be small entities, for the reasons stated in section IV.A above, this proposed rule would not have a significant economic impact on any vessel owner or operator.</P>
                <P>
                    If you think that your business, organization, or governmental jurisdiction qualifies as a small entity and that this rule would have a significant economic impact on it, please submit a comment (see 
                    <E T="02">ADDRESSES</E>
                    ) explaining why you think it qualifies and how and to what degree this rule would economically affect it.
                </P>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we want to assist small entities in understanding this proposed rule. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section. The Coast Guard will not retaliate against small entities that question or complain about this proposed rule or any policy or action of the Coast Guard.
                </P>
                <HD SOURCE="HD2">C. Collection of Information</HD>
                <P>This proposed rule would not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
                <HD SOURCE="HD2">D. Federalism and Indian Tribal Governments</HD>
                <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. We have analyzed this proposed rule under that Order and have determined that it is consistent with the fundamental federalism principles and preemption requirements described in Executive Order 13132.</P>
                <P>
                    Also, this proposed rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it would not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. If you believe this proposed rule has implications for federalism or Indian tribes, please contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section.
                </P>
                <HD SOURCE="HD2">E. Unfunded Mandates Reform Act</HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this proposed rule would not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
                <HD SOURCE="HD2">F. Environment</HD>
                <P>
                    We have analyzed this proposed rule under Department of Homeland Security Directive 023-01 and Commandant Instruction M16475.1D, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (42 U.S.C. 4321-4370f), and have made a preliminary determination that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This proposed rule involves a safety zone lasting more than one week. Normally such actions are categorically excluded from further review under paragraph L60(a) of Appendix A, Table 1 of DHS Instruction Manual 023-01-001-01, Rev. 01. A preliminary Record of Environmental Consideration supporting this determination is available in the docket where indicated under 
                    <E T="02">ADDRESSES</E>
                    . We seek any comments or information that may lead to the discovery of a 
                    <PRTPAGE P="20827"/>
                    significant environmental impact from this proposed rule.
                </P>
                <HD SOURCE="HD2">G. Protest Activities</HD>
                <P>
                    The Coast Guard respects the First Amendment rights of protesters. Protesters are asked to contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section to coordinate protest activities so that your message can be received without jeopardizing the safety or security of people, places, or vessels.
                </P>
                <HD SOURCE="HD1">V. Public Participation and Request for Comments</HD>
                <P>We view public participation as essential to effective rulemaking, and will consider all comments and material received during the comment period. Your comment can help shape the outcome of this rulemaking. If you submit a comment, please include the docket number for this rulemaking, indicate the specific section of this document to which each comment applies, and provide a reason for each suggestion or recommendation.</P>
                <P>
                    We encourage you to submit comments through the Federal eRulemaking Portal at 
                    <E T="03">http://www.regulations.gov.</E>
                     If your material cannot be submitted using 
                    <E T="03">http://www.regulations.gov,</E>
                     contact the person in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this document for alternate instructions.
                </P>
                <P>
                    We accept anonymous comments. All comments received will be posted without change to 
                    <E T="03">https://www.regulations.gov</E>
                     and will include any personal information you have provided. For more about privacy and the docket, visit 
                    <E T="03">https://www.regulations.gov/privacyNotice</E>
                    .
                </P>
                <P>
                    Documents mentioned in this NPRM as being available in the docket, and all public comments, will be in our online docket at 
                    <E T="03">https://www.regulations.gov</E>
                     and can be viewed by following that website's instructions. Additionally, if you go to the online docket and sign up for email alerts, you will be notified when comments are posted or a final rule is published.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
                    <P>Harbors, Marine Safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, the Coast Guard proposes to amend 33 CFR part 165 as follows:</P>
                <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>46 U.S.C. 70034, 70051; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; Department of Homeland Security Delegation No. 0170.1.</P>
                </AUTH>
                <AMDPAR>2. Add § 165.T09-0073 to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 165.T09-0073 </SECTNO>
                    <SUBJECT>Safety Zone; Tall Ships Challenge Great Lakes 2019; Buffalo, NY, Cleveland, OH, Bay City, MI, Green Bay, WI, Sturgeon Bay, WI, Kenosha, WI and Erie, PA.</SUBJECT>
                    <P>(a) Definitions. The following definitions apply to this section:</P>
                    <P>
                        (1) Navigation rules means the Navigation Rules, International and Inland (See, 1972 COLREGS and 33 U.S.C. 2001 
                        <E T="03">et seq.</E>
                        ).
                    </P>
                    <P>(2) Official patrol means those persons designated by Captain of the Port Buffalo, Detroit, Sault Ste. Marie, Duluth and Lake Michigan to monitor a tall ship safety zone, permit entry into the zone, give legally enforceable orders to persons or vessels within the zone, and take other actions authorized by the cognizant Captain of the Port.</P>
                    <P>(3) Public vessel means vessels owned, chartered, or operated by the United States or by a State or political subdivision thereof.</P>
                    <P>(4) Tall ship means any sailing vessel participating in the Tall Ships Challenge 2019 in the Great Lakes.</P>
                    <P>(b) Location. The following areas are safety zones: All navigable waters of the United States located in the Ninth Coast Guard District within a 100 yard radius of any tall ship.</P>
                    <P>(c) Regulations.</P>
                    <P>(1) No person or vessel is allowed within the safety zone unless authorized by the cognizant Captain of the Port, their designated representative, or the on-scene official patrol.</P>
                    <P>(2) Persons or vessels operating within a confined harbor or channel, where there is not sufficient navigable water outside of the safety zone to safely maneuver are allowed to operate within the safety zone and shall travel at the minimum speed necessary to maintain a safe course. Vessels operating within the safety zone shall not come within 25 yards of a tall ship unless authorized by the cognizant Captain of the Port, their designated representative, or the on-scene official patrol.</P>
                    <P>(3) When a tall ship approaches any vessel that is moored or anchored, the stationary vessel must stay moored or anchored while it remains within the tall ship's safety zone unless ordered by or given permission from the cognizant Captain of the Port, their designated representative, or the on-scene official patrol to do otherwise.</P>
                    <P>(d) Effective period. This rule is effective from 12:01 a.m. on Wednesday, June 28, 2019 through 12:01 a.m. on Monday September 2, 2019.</P>
                    <P>(e) Navigation Rules. The Navigation Rules shall apply at all times within a tall ships safety zone.</P>
                </SECTION>
                <SIG>
                    <DATED>Dated: May 8, 2019.</DATED>
                    <NAME>J.M. Nunan,</NAME>
                    <TITLE>Rear Admiral, U.S. Coast Guard, Commander, Ninth Coast Guard District.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09821 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 175</CFR>
                <CFR>46 CFR Part 25</CFR>
                <DEPDOC>[Docket No. USCG-2018-0099]</DEPDOC>
                <RIN>RIN 1625-AC41</RIN>
                <SUBJECT>Fire Protection for Recreational Vessels</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard proposes to amend the rules for recreational vessels by moving fire extinguishing equipment standards for recreational vessels from the uninspected vessel subchapter, which includes requirements for both recreational and commercial vessels, to the subchapter applicable only to recreational vessels. This proposed move would relieve owners of recreational vessels from having to adhere to NFPA 10 fire extinguisher inspection, maintenance, and recordkeeping requirements intended to apply to commercial vessels only. This would not alter fire extinguishing equipment standards for commercial vessels, but would correct an incongruity in our regulations.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Comments and related material must be received by the Coast Guard on or before July 12, 2019. Comments sent to the Office of Management and Budget (OMB) on collection of information must reach OMB on or before 60 days after publication in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments identified by docket number USCG-2018-0099 using the Federal eRulemaking Portal at 
                        <E T="03">https://www.regulations.gov.</E>
                         See the “Public Participation and Request for Comments” portion of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for further instructions on submitting comments.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For information about this document, call or 
                        <PRTPAGE P="20828"/>
                        email Sean Ramsey, Office of Design and Engineering Standards, Lifesaving and Fire Safety Division (CG-ENG-4), Coast Guard; telephone 202-372-1392, email 
                        <E T="03">Sean.M.Ramsey@uscg.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Table of Contents for Preamble </HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Public Participation and Request for Comments</FP>
                    <FP SOURCE="FP-2">II. Abbreviations</FP>
                    <FP SOURCE="FP-2">III. Basis and Purpose</FP>
                    <FP SOURCE="FP1-2">A. Purpose</FP>
                    <FP SOURCE="FP1-2">B. Basis</FP>
                    <FP SOURCE="FP-2">IV. Background</FP>
                    <FP SOURCE="FP-2">V. Discussion of Proposed Rule</FP>
                    <FP SOURCE="FP-2">VI. Regulatory Analyses</FP>
                    <FP SOURCE="FP1-2">A. Regulatory Planning and Review</FP>
                    <FP SOURCE="FP1-2">B. Small Entities</FP>
                    <FP SOURCE="FP1-2">C. Assistance for Small Entities</FP>
                    <FP SOURCE="FP1-2">D. Collection of Information</FP>
                    <FP SOURCE="FP1-2">E. Federalism</FP>
                    <FP SOURCE="FP1-2">F. Unfunded Mandates Reform Act</FP>
                    <FP SOURCE="FP1-2">G. Taking of Private Property</FP>
                    <FP SOURCE="FP1-2">H. Civil Justice Reform</FP>
                    <FP SOURCE="FP1-2">I. Protection of Children</FP>
                    <FP SOURCE="FP1-2">J. Indian Tribal Governments</FP>
                    <FP SOURCE="FP1-2">K. Energy Effects</FP>
                    <FP SOURCE="FP1-2">L. Technical Standards</FP>
                    <FP SOURCE="FP1-2">M. Environment</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Public Participation and Request for Comments</HD>
                <P>The Coast Guard views public participation as essential to effective rulemaking, and will consider all comments and material received during the comment period. Your comment can help shape the outcome of this rulemaking. If you submit a comment, please include the docket number for this rulemaking, indicate the specific section of this document to which each comment applies, and provide a reason for each suggestion or recommendation.</P>
                <P>
                    We encourage you to submit comments through the Federal eRulemaking Portal at 
                    <E T="03">https://www.regulations.gov.</E>
                     If you cannot submit your material by using 
                    <E T="03">https://www.regulations.gov,</E>
                     contact the person in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this notice of proposed rulemaking (NPRM) for alternate instructions. Documents mentioned in this NPRM, and all public comments, will be available in our online docket at 
                    <E T="03">https://www.regulations.gov,</E>
                     and can be viewed by following that website's instructions. Additionally, if you visit the online docket and sign up for email alerts, you will be notified when comments are posted or if a final rule is published.
                </P>
                <P>
                    We accept anonymous comments. All comments received will be posted without change to 
                    <E T="03">https://www.regulations.gov</E>
                     and will include any personal information you have provided. For more about privacy and the docket, visit 
                    <E T="03">https://www.regulations.gov/privacyNotice.</E>
                </P>
                <P>
                    We are not planning to hold a public meeting, but will consider doing so if public comments indicate a meeting would be helpful. We would issue a separate 
                    <E T="04">Federal Register</E>
                     notice to announce the date, time, and location of such a meeting.
                </P>
                <HD SOURCE="HD1">II. Abbreviations </HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">CATEX Categorical exclusion</FP>
                    <FP SOURCE="FP-2">CFR Code of Federal Regulations</FP>
                    <FP SOURCE="FP-2">“Fire Protection” rule Harmonization of Standards for Fire Protection, Detection, and Extinguishing Equipment final rule, 81 FR 48220, published July 22, 2016</FP>
                    <FP SOURCE="FP-2">FR Federal Register</FP>
                    <FP SOURCE="FP-2">NBSAC National Boating Safety Advisory Council</FP>
                    <FP SOURCE="FP-2">NFPA 10 National Fire Protection Association Standard for Portable Fire Extinguishers, 2010 edition</FP>
                    <FP SOURCE="FP-2">NPRM Notice of proposed rulemaking</FP>
                    <FP SOURCE="FP-2">OMB Office of Management and Budget</FP>
                    <FP SOURCE="FP-2">RA Regulatory analysis</FP>
                    <FP SOURCE="FP-2">§ Section symbol</FP>
                    <FP SOURCE="FP-2">U.S.C. United States Code</FP>
                </EXTRACT>
                <HD SOURCE="HD1">III. Basis and Purpose</HD>
                <HD SOURCE="HD2">A. Purpose</HD>
                <P>This proposed rule would update Coast Guard regulations pertaining to fire extinguishing equipment requirements and the associated standards used by recreational vessels. The Coast Guard proposes removing some requirements and burdens that were unintentionally applied to the recreational vessel community by the final rule titled, “Harmonization of Standards for Fire Protection, Detection, and Extinguishing Equipment” (the “Fire Protection” rule), 81 FR 48220, published July 22, 2016. The Coast Guard also proposes moving fire extinguishing equipment rules for recreational vessels from subpart 25.30 (Fire Extinguishing Equipment) of subchapter C (Uninspected Vessels) of Title 46 of the Code of Federal Regulations (CFR) to part 175 of subchapter S (Boating Safety) of Title 33, where other recreational vessel rules already exist.</P>
                <HD SOURCE="HD2">B. Basis</HD>
                <P>Section 4302(a)(2) of Title 46 of the United States Code (U.S.C.) authorizes the Secretary of Homeland Security to prescribe regulations requiring the installation, carrying, or use of firefighting equipment and prohibiting the installation, carrying, or use of equipment that does not conform to the safety standards established under section 4302. The Secretary of Homeland Security delegated this authority to the Coast Guard by the Department of Homeland Security Delegation No. 0170.1(II)(92)(b).</P>
                <HD SOURCE="HD1">IV. Background</HD>
                <P>Portable fire extinguishers may be rechargeable or non-rechargeable (disposable). Rechargeable extinguishers can be refilled after use or after a certain amount of time has elapsed, while non-rechargeable extinguishers must be discarded. Recreational vessels typically carry non-rechargeable extinguishers. This is because rechargeable extinguishers are not common in the 5-B size that is required for recreational vessels, and can be difficult to find and purchase. Also, rechargeable units of this size tend to be special purpose extinguishers such as carbon dioxide or clean agent extinguishers commonly used in an areas such as server rooms, not on recreational vessels, and come at a significantly higher price than non-rechargeable extinguishers.</P>
                <P>
                    Through the “Fire Protection” rule, the Coast Guard sought to harmonize and align Coast Guard regulations with current international and industry consensus standards, including the National Fire Protection Association's “Standard for Portable Fire Extinguishers,” 2010 edition (NFPA 10).
                    <SU>1</SU>
                    <FTREF/>
                     NFPA 10 requires vessel owners and operators to complete monthly visual inspections and annual maintenance—defined in NFPA 10 as a thorough examination, and repair or replacement if needed—of portable fire extinguishers, and to maintain records of the inspections and maintenance. In the “Fire Protection” rule, the Coast Guard allowed the monthly inspections of all fire extinguishers to be carried out by the vessel owner, operator, person-in-charge, or a designated member of the crew, rather than by a certified person as provided in NFPA 10. The “Fire Protection” rule also allowed these individuals to perform annual maintenance on non-rechargeable (disposable) extinguishers, but retained the NFPA 10 requirement that rechargeable extinguishers be maintained by a certified person such as a licensed servicing agency.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         NFPA is a nonprofit organization that develops technical codes and consensus standards to eliminate death, injury, property and economic loss due to fire, electrical and related hazards. NFPA 10 is one of those standards that lists requirements to ensure that portable fire extinguishers will work as intended to provide a first line of defense against fires of limited size.
                    </P>
                </FTNT>
                <P>
                    As part of the regulatory analysis (RA) for the 2016 “Fire Protection” rule, the Coast Guard estimated that recreational vessel owners would not be burdened by any costs from the implementation of NFPA 10. The Coast Guard did not 
                    <PRTPAGE P="20829"/>
                    receive public comments on this topic during the public comment period on that rule. After publication of the rule, however, we realized the requirements to visually inspect and maintain non-rechargeable (disposable) extinguishers as described in NFPA 10, and to keep records of those activities in compliance with NFPA 10, represented new burdens on recreational vessel owners and operators. We did not account for those burdens in the RA for the 2016 rule and we lacked the data to justify placing those burden on recreational vessel owners and operators.
                </P>
                <P>Finally, after publication of the “Fire Protection” rule, the Coast Guard noted an incongruity in our vessel safety regulations regarding fire extinguishers. The current recreational vessel fire extinguishing equipment rules exist separately from other recreational vessel rules. This proposed rule would consolidate the recreational vessel fire extinguishing equipment requirements from 46 CFR subpart 25.30 into 33 CFR part 175, where other recreational vessel-specific rules are located. This proposed rule would also create a clear distinction between fire extinguishing equipment regulations intended for commercial vessels and the regulations intended for recreational vessels.</P>
                <P>In support of this effort, on October 22, 2016, the National Boating Safety Advisory Council (NBSAC) passed a resolution (NBSAC Resolution 2016-96-02) recommending that the Coast Guard remove the NFPA 10 recordkeeping requirements from recreational vessels and consolidate recreational vessel fire protection and boating safety requirements into 33 CFR subchapter S. The 50 States and 6 U.S. territories that enforce boating safety requirements may choose to incorporate Coast Guard regulations into their own legislation or regulations. We alerted the States to the NBSAC Resolution 2016-96-02 and to the fact that we did not intend for recreational vessel owners and operators to be subject to the NPFA 10 monthly visual inspection, annual maintenance, and recordkeeping requirements.</P>
                <HD SOURCE="HD1">V. Discussion of Proposed Rule</HD>
                <P>This proposed rule is discussed in detail in the following three steps:</P>
                <P>(1) Remove recreational vessel fire extinguishing equipment regulations from 46 CFR subpart 25.30 (Fire Extinguishing Equipment).</P>
                <P>(a) Fire extinguishing equipment regulations in 46 CFR subpart 25.30 (Fire Extinguishing Equipment) currently apply to all motorboats and motor vessels (as defined by 46 CFR 24.10-1), both recreational and commercial. In order to make subpart 25.30 regulations apply to commercial vessels only, the Coast Guard proposes to revise the applicability section in 46 CFR 25.30-1 so that the fire extinguishing equipment regulations in subpart 25.30 would explicitly not apply to recreational vessels. We would change only the applicability of the fire extinguishing equipment regulations, and would not change the applicability of any other requirements in part 25.</P>
                <P>(b) The other requirements in part 25 (life preservers, navigation lights, ventilation, etc.) will not be changed or moved to Title 33 of the CFR because they either expressly exclude recreational vessels or already exist in the Title 33 provisions for recreational vessels.</P>
                <P>(2) Move all of the fire extinguishing equipment regulations for recreational vessels from 46 CFR subpart 25.30 to 33 CFR part 175, subpart E, and revise the regulations to no longer require recreational vessel owners and operators to follow the monthly visual inspection, annual maintenance, and recordkeeping requirements of NFPA 10.</P>
                <P>(a) The Coast Guard would create a new subpart E, Fire Protection Equipment, under part 175 (Equipment Requirements) in 33 CFR subchapter S (Boating Safety), and add the fire extinguishing equipment regulations from 46 CFR subpart 25.30 to that new subpart.</P>
                <P>(b) The Coast Guard would limit the applicability of this new subpart to recreational vessels, as defined in 33 CFR 175.3, with propulsion machinery to clarify that the fire extinguishing equipment requirements would not apply to non-motorized sail boats, kayaks, canoes, and other human powered recreational vessels that do not require portable fire extinguishers. The fire extinguishing equipment requirements added to subpart E would be the same as in current 46 CFR subpart 25.30, but would be modified to clarify the regulatory language, update outdated information, and omit the requirement for recreational vessels to comply with NFPA 10. Instead of applying NFPA 10 and requiring monthly visual inspections, annual maintenance, and recordkeeping, we would indicate that fire extinguishers should be maintained in good and serviceable condition. Both the “good and serviceable condition” standard and the NFPA 10 requirements (monthly visual inspection, annual maintenance, and recordkeeping) exist to achieve the same result—that fire extinguishers remain in a working condition. However, the NFPA 10 requirements are very specific and prescriptive. The good and serviceable condition” standard is goal oriented and non-prescriptive. The “good and serviceable condition” standard relieves the owners and operators of recreational vessels of the burden of following the specifics of NFPA 10 while allowing them the freedom to achieve the same result as the NFPA 10 requirements. For these reasons, the Coast Guard has opted to follow the goal-based standard to ensuring fire extinguishers remain in working condition instead of NFPA 10's prescriptive and regimented inspection, maintenance and recordkeeping requirements for recreational vessels.</P>
                <P>(3) Update text in 33 CFR part 175, new subpart E—Fire Protection Equipment.</P>
                <P>(a) The Coast Guard would make several small administrative changes to the text being moved from 46 CFR subpart 25.30 to new 33 CFR part 175 subpart E, to clarify the regulatory language and update outdated information. For example, we would remove reference to the no longer published COMDTINST M16714.3, and remove references to the Marine Safety Center as an approving entity for fire extinguishers as they no longer approve fire extinguishers.</P>
                <P>(b) The Coast Guard would change the terms “motorboats” and “motor vessels,” as currently used in subpart 25.30, to more clear terms of “Recreational vessels 65 feet and less in length” and “Recreational vessels more than 65 feet in length” respectively. This change would align the language used in new subpart E with the terminology already used in 33 CFR part 175, and reinforce the subpart's intent to apply the requirements to recreational vessels, and not all motorboats and motor vessels. It would also make clearer the distinction between the two vessel size categories, allowing readers to easily find the fire extinguishing equipment requirements appropriate for a particular type of vessel.</P>
                <P>(c) The Coast Guard would add new language to clarify acronyms, and update cross-references to 46 CFR subpart 25.30. For example, replacing the B.H.P. acronym with “brake horse power” and updating references to clearly point towards 46 CFR instead of chapter I.</P>
                <P>
                    (d) The Coast Guard would modify the language moved from 46 CFR subpart 25.30 to refer to recreational vessels by model years, as opposed to contracting or manufacturing dates. The latter are applicable to commercial vessels only. This change would allow the recreational boating community to more easily identify their vessel 
                    <PRTPAGE P="20830"/>
                    requirements, and it would align with industry and market naming practices.
                </P>
                <P>(e) Because this rule is not intended to and would not change any exceptions that already apply to recreational vessels, the Coast Guard proposes to retain all the existing recreational fire extinguishing equipment exemptions, such as those for vessels manufactured before August 22, 2016, and the fire extinguishing equipment exemptions for vessels manufactured before November 19, 1952, as provided in 46 CFR 25.30-80 and 46 CFR 25.30-90. Where we previously allowed exemptions for vessels manufactured or contracted before August 22, 2016, we would apply the same exemptions to recreational vessels with model years before 2017. Where regulations previously exempted vessels manufactured or contracted before November 19, 1952, we would apply those exemptions to recreational vessels with model years before 1953. We would also retain the exemption in 46 CFR 25.30-20(a) that allows recreational vessels less than 26 feet in length propelled by outboard motors and not carrying passengers for hire to not have to carry portable fire extinguishers if the construction of the vessel will not permit the entrapment of explosive or flammable gases or vapors.</P>
                <P>In summary, the Coast Guard proposes separating recreational vessel fire extinguishing equipment rules from commercial vessel fire extinguishing equipment rules, and consolidating recreational vessel-specific requirements into one part, which would not contain NFPA 10 visual inspection, annual maintenance, and recordkeeping requirements for recreational vessels. This change would affect only recreational vessels with propulsion machinery, and would not affect commercial vessels.</P>
                <HD SOURCE="HD1">VI. Regulatory Analyses</HD>
                <P>The Coast Guard developed this NPRM after considering numerous statutes and Executive orders related to rulemaking. A summary of our analyses based on these statutes or Executive orders follows.</P>
                <HD SOURCE="HD2">A. Regulatory Planning and Review</HD>
                <P>Executive Orders 12866 (Regulatory Planning and Review) and 13563 (Improving Regulation and Regulatory Review) 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, reducing costs, harmonizing rules, and promoting flexibility. Executive Order 13771 (Reducing Regulation and Controlling Regulatory Costs) directs agencies to reduce regulation and control regulatory costs, and provides that “for every one new regulation issued, at least two prior regulations be identified for elimination, and that the cost of planned regulations be prudently managed and controlled through a budgeting process.”</P>
                <P>
                    The Office of Management and Budget (OMB) has not designated this proposed rule a significant regulatory action under section 3(f) of Executive Order 12866. Accordingly, OMB has not reviewed it. OMB considers this rule to be an Executive Order 13771 deregulatory action. 
                    <E T="03">See</E>
                     OMB's Memorandum “Guidance Implementing Executive Order 13771, Titled `Reducing Regulation and Controlling Regulatory Costs' ” (April 5, 2017). An RA follows.
                </P>
                <P>The Coast Guard promulgates regulations to ensure that maritime organizations and employees engage in activities that protect the environment, human, and marine life, and that reflect safe boating practices. To meet this mission, this proposed rule would correct errors resulting from the “Fire Protection” final rule (81 FR 48220), effective as of August 22, 2016. The “Fire Protection” update to the fire extinguishing equipment rules in 46 CFR subpart 25.30 (Requirements) of subchapter C (Uninspected Vessels) inadvertently applied NFPA 10 monthly visual inspection, annual maintenance, and recordkeeping requirements to both recreational and commercial vessels, which created unintended regulatory requirements for recreational vessels—the largest regulated vessel community under the Coast Guard's purview. The proposed rule would remove the NFPA 10 recordkeeping and monthly visual inspection requirements together with the requirement for annual maintenance from the recreational vessel community, and require extinguishers be kept in good and serviceable condition. The proposed rule would not change the fire extinguishing equipment requirements for commercial vessels in 46 CFR subpart 25.30 or any other recreational vessel requirements.</P>
                <P>Additionally, the Coast Guard proposes to correct an incongruity in our vessel safety equipment regulations by shifting recreational vessel fire extinguishing equipment requirements from 46 CFR subpart 25.30, (Fire Extinguishing Equipment) to 33 CFR part 175, new subpart E (Equipment Requirements). This would move all the recreational vessel fire extinguishing equipment rules from a commercial vessel subpart in 46 CFR subpart 25.30 to a recreational vessel section in 33 CFR part 175. This alignment would not alter the regulations for commercial vessels, but would separate commercial regulations from regulations for the recreational vessel community.</P>
                <P>
                    The Coast Guard considered a potential cost of this proposed rule. There is a possibility that States and territorial jurisdictions had chosen to update their statutes and regulations to incorporate NFPA 10 into their legislation or regulations. Based on available data and a thorough search of state legislative documents, the Coast Guard finds no evidence of the States and territorial jurisdictions changing their regulations to satisfy NFPA 10. Therefore, we determine that the States and territorial jurisdictions will not need to revise their regulations and incur any cost.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Per Coast Guard subject matter expert review and communication with State &amp; territorial jurisdictions.
                    </P>
                </FTNT>
                <P>There are no costs to the regulated public. The primary cost savings of this rule would be from correcting the unintended regulatory requirements of NFPA 10 inspection, maintenance, and recordkeeping requirements placed on the recreational vessel community.</P>
                <P>Table 1 presents a summary of the impacts of this proposed rule.</P>
                <PRTPAGE P="20831"/>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s50,r150">
                    <TTITLE>Table 1—Summary of Impacts of the Proposed Rule</TTITLE>
                    <BOXHD>
                        <CHED H="1">Category</CHED>
                        <CHED H="1">Summary</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Applicability</ENT>
                        <ENT>Recreational vessels are no longer required to comply with the fire extinguishing equipment requirements in 46 CFR subpart 25.30.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Affected population</ENT>
                        <ENT>11,005,841 recreational vessels with disposable fire extinguishers (50 States and 6 Territorial jurisdictions).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Costs (2016$, 7% discount rate)</ENT>
                        <ENT>No Cost.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cost Savings</ENT>
                        <ENT>Removes NFPA 10 inspection, maintenance, and recordkeeping requirements from the recreational vessel community. Savings equate to 12 minutes per year per vessel.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Benefits</ENT>
                        <ENT>Shifts recreational vessel fire extinguishing equipment requirements from 46 CFR subpart 25.30 to 33 CFR part 175, subpart E, creating a clear distinction between fire extinguishing equipment regulations intended for commercial vessels and those intended for recreational vessels.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD3">Affected Population</HD>
                <P>
                    The affected population consists of recreational vessels subject to the provisions of 46 CFR subpart 25.30 and the 50 State and 6 territorial jurisdictions. The RA performed for the “Fire Protection” final rule (81 FR 48220) used recreational vessel population data from the Coast Guard Office of Auxiliary and Boating Safety's document titled, 
                    <E T="03">2013 Recreational Boating Statistics,</E>
                    <SU>3</SU>
                    <FTREF/>
                     to estimate the affected population. For this analysis, the Coast Guard uses the most recently published data from the 
                    <E T="03">2016 Recreational Boating Statistics</E>
                     to identify a population of 11,005,841 
                    <SU>4</SU>
                    <FTREF/>
                     registered motorized recreational vessels that would be affected by the fire extinguishing equipment requirements in 46 CFR subpart 25.30.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Recreational Boating Statistics 2013. Accessed at 
                        <E T="03">https://www.uscgboating.org/assets/1/AssetManager/2013RecBoatingStats.pdf</E>
                        .
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Recreational Boating Statistics 2016, Table 37. Accessed at 
                        <E T="03">https://www.uscgboating.org/library/accident-statistics/Recreational-Boating-Statistics-2016.pdf</E>
                        .
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Cost Analysis</HD>
                <P>This NPRM proposes 18 changes to the fire extinguishing equipment regulations in 33 CFR part 175, subpart E, and 46 CFR subpart 25.30. These changes are summarized as follows:</P>
                <P>• Remove recreational vessel fire extinguishing equipment regulations from 46 CFR subpart 25.30 (Fire Extinguishing Equipment).</P>
                <P>• Move the recreational vessel fire extinguishing equipment regulations from 46 CFR subpart 25.30 to new 33 CFR part 175, subpart E. This would include new § 175.301 to 33 CFR part 175, subpart E, to specify the applicability of subpart E to recreational vessels. It would also include new §§ 175.305, 175.310, 175.315, 175.320, 175.380, and 175.390 to reflect requirements previously applied by 46 CFR subpart 25.30, but excluding those that require recreational vessel owners and operators to follow the monthly visual inspection, annual maintenance, and recordkeeping requirements of NFPA 10.</P>
                <P>Update recreational vessel fire extinguishing equipment regulations to clarify regulatory language and update outdated information. Overall, there are no costs to the regulated public associated with these 18 changes to the regulatory text. The changes and economic impacts of these changes are described in Table 2.</P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s70,r70,r150,xs50">
                    <TTITLE>Table 2—Assessment of Cost Impacts of the Proposed Rule to the Regulated Public</TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            Existing 46 CFR part 25
                            <LI>sections</LI>
                        </CHED>
                        <CHED H="1">Proposed 33 CFR part 175 sections</CHED>
                        <CHED H="1">Description of proposed change</CHED>
                        <CHED H="1">Cost impact</CHED>
                    </BOXHD>
                    <ROW RUL="s" EXPSTB="03">
                        <ENT I="21">
                            <E T="02">Definitions</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s" EXPSTB="00">
                        <ENT I="01">§ 25.30-1(b) &amp; (c)</ENT>
                        <ENT>§ 175.3</ENT>
                        <ENT>
                            Add the definition of 
                            <E T="03">Model Year</E>
                             to the section
                        </ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW RUL="s" EXPSTB="03">
                        <ENT I="21">
                            <E T="02">Applicability</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s" EXPSTB="00">
                        <ENT I="01">§ 25.30-1</ENT>
                        <ENT>§ 175.301</ENT>
                        <ENT>Adopt existing text from 46 CFR 25.30-1, with new text to clarify the applicability of this subpart to recreational vessels with propulsion machinery only</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW RUL="s" EXPSTB="03">
                        <ENT I="21">
                            <E T="02">General Provisions</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s" EXPSTB="00">
                        <ENT I="01">§ 25.30-5(a)</ENT>
                        <ENT>§ 175.305</ENT>
                        <ENT>Adopt existing text from 46 CFR 25.30-5(a), with text edits to clarify approved equipment must be approved by the Commandant (CG-ENG-4)</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW RUL="s" EXPSTB="03">
                        <ENT I="21">
                            <E T="02">Portable Fire Extinguishers and Semi-Portable Fire Extinguishing Systems</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">§ 25.30-5(b)</ENT>
                        <ENT>§ 175.310(a)</ENT>
                        <ENT>Adopt existing text from 46 CFR 25.30-5(b)</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">§ 25.30-10(a)</ENT>
                        <ENT>§ 175.310(b)</ENT>
                        <ENT>Adopt existing text from 46 CFR 25.30-10(a), with edits removing the requirement that the extinguishers be maintained, inspected, and recorded in accordance with NFPA 10. Add new text, extracted from relevant sections of NFPA 10, requiring that fire extinguishers must accessible, have a good operating pressure, not be expired, or previously used, and be maintained in accordance with the manufacturer's instructions</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">§ 25.30-10(f)</ENT>
                        <ENT>§ 175.310(c)</ENT>
                        <ENT>Adopt text from 46 CFR 25.30-10(f), with text edits for clarification</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20832"/>
                        <ENT I="01">§ 25.30-10(g)</ENT>
                        <ENT>§ 175.310(d)</ENT>
                        <ENT>Adopt text from 46 CFR 25.30-10(g)</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">§ 25.30-10(h)</ENT>
                        <ENT>§ 175.310(e)</ENT>
                        <ENT>Adopt text from 46 CFR 25.30-10(h)(1)-25.30-10(h)(4), with edits changing the motorboat references to recreational vessel references</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">§ 25.30-10 (h)(4)(i)</ENT>
                        <ENT>§ 175.310(f)</ENT>
                        <ENT>Adopt text from 46 CFR 25.30-10(h)(4)(i), with edits changing the motorboat references to recreational vessel references</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">§ 25.30-10(j)</ENT>
                        <ENT>§ 175.310(g)</ENT>
                        <ENT>Adopt text from 46 CFR 25.30-10(j)</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW RUL="s" EXPSTB="03">
                        <ENT I="21">
                            <E T="02">Fixed Fire Extinguishing Systems</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">§ 25.30-15(a)</ENT>
                        <ENT>§ 175.315(a)</ENT>
                        <ENT>Adopt existing text from 46 CFR 25.30-315(a) with text edits to clarify approved equipment must be approved by the Commandant (CG-ENG-4)</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">§ 25.30-15(b)</ENT>
                        <ENT>§ 175.315(b)</ENT>
                        <ENT>Adopt existing text from 46 CFR 25.30-315(b)</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">§ 25.30-15(c)</ENT>
                        <ENT>§ 175.315(c)</ENT>
                        <ENT>Adopt existing text from 46 CFR 25.30-315(c) with edits to update references from NFPA 13 to the 46 CFR source</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW RUL="s" EXPSTB="03">
                        <ENT I="21">
                            <E T="02">Fire Extinguishing Equipment Required</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">§ 25.30-20(a)</ENT>
                        <ENT>§ 175.320(a)</ENT>
                        <ENT>Adopt text from 46 CFR 25.30-20(a)(1) and 25.30-20(a)(2), with edits changing the motorboat references to recreational vessels not more than 65 feet</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Table 25.30-20(A)(1)</ENT>
                        <ENT>Table 1 to § 175.320(a)</ENT>
                        <ENT>Adopt Table 25.30-20(A)(1) from 46 CFR 25.30-20(a), with edits changing the table numbering for clarity</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Figure 25.30-20(A1)</ENT>
                        <ENT>Figure 1 to § 175.320(a)(2)</ENT>
                        <ENT>Adopt Figure 25.30-20(A1) from 46 CFR 25.30-20(a), with edits changing the figure numbering for clarity</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Figure 25.30-20(A2)</ENT>
                        <ENT>Figure 2 to § 175.320(a)(2)</ENT>
                        <ENT>Adopt Figure 25.30-20(A2) from 46 CFR 25.30-20(a), with edits changing the figure numbering for clarity</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">§ 25.30-20(c)</ENT>
                        <ENT>§ 175.320(b)</ENT>
                        <ENT>Adopt text from 46 CFR 25.30-20(c)(1) 2012; 25.30-20(c)(4), with edits changing the motor vessels references to recreational vessels over 65 feet, and text edits for clarity</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Table 25.30-20(B)(1)</ENT>
                        <ENT>Table 1 to § 175.320(b)</ENT>
                        <ENT>Adopt Table 25.30-20(B)(1) from 46 CFR 25.30-20(b), with edits changing the table numbering for clarity</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">§ 25.30-20(b)(2)(1)</ENT>
                        <ENT>§ 175.320(b)</ENT>
                        <ENT>Adopt text from 46 CFR 25.30-20(a), with edits changing the motor vessels references to recreational vessels over 65 feet</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">§ 25.30-20(a)(3) &amp; § 25.30-20(c)(5)</ENT>
                        <ENT>§ 175.320(c)</ENT>
                        <ENT>Combine the text from 46 CFR 25.30-20(a)(3) &amp; 25.30-20(c)(5) into a new section that clarifies Table 1 to 46 CFR 175.320(a) and Table 1 to 46 CFR 175.320(b) contain the minimum number of extinguishers needed on a vessel</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW RUL="s" EXPSTB="03">
                        <ENT I="21">
                            <E T="02">Location and Number of Fire Extinguishers Required for Vessels Constructed prior to August 22, 2016</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s" EXPSTB="00">
                        <ENT I="01">§ 25.30-80</ENT>
                        <ENT>§ 175.380</ENT>
                        <ENT>Adopt text from 46 CFR subpart 25.30-80 with updated references to Table 1 to 46 CFR 175.320(a) and Table 1 to 46 CFR 175.320(b)</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW RUL="s" EXPSTB="03">
                        <ENT I="21">
                            <E T="02">Vessels Contracted prior to November 19, 1952</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s" EXPSTB="00">
                        <ENT I="01">§ 25.30-90</ENT>
                        <ENT>§ 175.390</ENT>
                        <ENT>Adopt text from 46 CFR 25.30-90 with updated references to the new 46 CFR 175 and text edits for clarity</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW RUL="s" EXPSTB="03">
                        <ENT I="21">
                            <E T="02">Proposed Edits to 46 CFR Part 25.30</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">§ 25.30-1</ENT>
                        <ENT/>
                        <ENT>Edit and reorganize paragraph for clarity.</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">§ 25.30-1</ENT>
                        <ENT/>
                        <ENT>Remove applicability to non-commercial vessels</ENT>
                        <ENT>No cost.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD3">Costs</HD>
                <P>
                    The Coast Guard considered all potential costs of this proposed rule. We considered the possibility that States and territorial jurisdictions may choose to update their statutes and regulations if they had previously changed their regulations to satisfy NFPA 10. However, based on available data and a thorough search of State and territorial jurisdictions' legislative documents, the Coast Guard finds no evidence of the States and territorial jurisdictions changing their regulations to satisfy NFPA 10. Therefore, they will not incur any costs as no State or territory will need to change back their regulations.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Per Coast Guard subject matter expert review and communication with State &amp; territorial jurisdictions.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Cost Savings</HD>
                <P>The primary savings of this proposed rule stem from the correction of the unintended regulatory requirements placed on the recreational vessel community by the “Fire Protection” rule with regards to recordkeeping and monthly visual inspection requirements associated with the type of fire extinguisher on board a recreational vessel.</P>
                <P>
                    NFPA 10 has specific inspection requirements for both rechargeable and non-rechargeable portable fire extinguishers. Owners of vessels with 
                    <PRTPAGE P="20833"/>
                    non-rechargeable (disposable) extinguishers, commonly used in the recreational vessel community, are subject to a monthly visual inspection ensuring the fire extinguisher is available and still operational and maintain records of their compliance by placing an initial in a log book as confirmation of a visual inspection. For rechargeable fire extinguishers, NFPA 10 requires an annual inspection by a qualified technician permitted by State and local authorities in addition to monthly visual inspections. Rechargeable extinguishers are not common in the 5-B size that is required for recreational boats, and must be actively sought and bought from a more industrial distributor. Rechargeable units of this size tend to be special purpose extinguishers such as carbon dioxide or clean agent extinguishers commonly used in areas such as server rooms, not on recreational boats, and come at a significantly higher price. Non-rechargeable or disposable units are intended for use by the public and are the primary type of fire extinguisher on recreational vessels. They are primarily marketed to the general public because of their low operating and maintenance costs, low upfront cost, reliability as well as the ease of care and can be purchased at retail stores. As a result, rechargeable fire extinguishers are generally purchased by commercial vessel owners and operators, while non-rechargeable units are purchased by recreational vessel owners. Therefore, we estimate the savings to recreational boaters will stem from no longer needing to perform a monthly visual inspection along with its associated minor recordkeeping requirement confirming the inspection. We estimate such monthly inspections would take 1 minute per month to complete for an annual total of 12 minutes per fire extinguisher.
                    <SU>6</SU>
                    <FTREF/>
                     Data on how many recreational vessel owners have complied with current NFPA 10 requirements since 2016 is non-existent as is data on the various labor categories of the recreational vessel owners. Therefore, while the proposed rule may reduce the regulatory burden to some recreational vessel owners, we do not have enough information on the potential scale of this reduction and consequently, do not attempt to monetize these potential cost savings. However, as mentioned above, we estimate a time savings component of approximately 12 minutes per year per fire extinguisher (1 minutes/month).
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The value of a person's recreational time is dependent on a number of factors such as income, age, and employment status. We did not have this information for owners of the recreational vessels subject to this proposed rulemaking and therefore were unable to monetize the cost savings associated with the 12 minute burden reduction. This is a 12 minute- reduction per fire extinguisher, and we estimate that 5.3 percent of the affected population of recreational vessels carry more than one fire extinguisher.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Estimate based on Coast Guard subject matter experts.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Benefits</HD>
                <P>By shifting the recreational vessel fire extinguishing equipment requirements from 46 CFR subpart 25.30 to 33 CFR part 175, subpart E, this rule would create a clear distinction between fire extinguishing equipment regulations intended for commercial vessels and those intended for recreational vessels.</P>
                <HD SOURCE="HD3">Alternatives</HD>
                <HD SOURCE="HD3">Alternative 1: Preferred Alternative</HD>
                <P>The preferred alternative would be to: (1) Move the fire extinguishing equipment requirements for recreational vessels from 46 CFR subpart 25.30 to 33 CFR part 175, new subpart E; (2) separate recreational vessel fire protection regulations from commercial vessel regulations; (3) remove all NFPA 10 inspection, maintenance and recordkeeping requirements from recreational vessels; and (4) consolidate recreational vessel fire extinguishing equipment requirements into one subchapter. The preferred alternative follows the NBSAC recommendation.</P>
                <HD SOURCE="HD3">Alternative 2: No-Action Alternative</HD>
                <P>Under this alternative, recreational vessel fire protection rules would remain in 46 CFR subpart 25.30, and NFPA 10 would continue to apply to recreational vessels. The Coast Guard did not select this alternative because it maintains an unintended burden on recreational vessel owners and does not follow the NBSAC's recommendation.</P>
                <HD SOURCE="HD3">Alternative 3: Policy Over Regulation</HD>
                <P>This alternative would create a new Coast Guard policy based on the NBSAC's recommendation that would outline fire extinguishing equipment standards. The Coast Guard did not select this option because States adopt Coast Guard regulations, not Coast Guard policy recommendations. Furthermore, it is not considered a good regulatory practice to determine shipping regulations via policy instruments. Finally, this alternative would not follow the NBSAC's recommendation.</P>
                <HD SOURCE="HD3">Alternative 4: Add Exemption From NFPA 10 Requirements</HD>
                <P>Alternative 4 would add language to 46 CFR subpart 25.30 explicitly stating that NFPA 10 does not apply to recreational vessels. The Coast Guard did not select this option because this alternative would not follow the NBSAC's recommendation.</P>
                <HD SOURCE="HD2">B. Small Entities</HD>
                <P>Under the Regulatory Flexibility Act, 5 U.S.C. 601-612, the Coast Guard has considered whether this proposed rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
                <P>
                    The proposed rule corrects the unintended regulatory requirements placed on 11,005,841 recreational vessels and would move fire extinguishing equipment requirements for recreational vessels from subpart 25.30 of part 25 in Title 46 of the CFR to a new subpart E (Fire Protection Equipment) of part 175 in Title 33 of the CFR. The Coast Guard's economic analysis concluded that these proposed changes would not impose costs on any of the recreational vessels that comprise the affected population described in this NPRM, and thus not have a cost impact on small entities that own and operate the recreational vessels. Therefore, the Coast Guard certifies under 5 U.S.C. 605(b) that this proposed rule would not have a significant economic impact on a substantial number of small entities. If you think that your business, organization, or governmental jurisdiction qualifies as a small entity and that this proposed rule would have a significant economic impact on it, please submit a comment to the docket at the address listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this NPRM. In your comment, explain why you think it qualifies and how and to what degree this proposed rule would economically affect it.
                </P>
                <HD SOURCE="HD2">C. Assistance for Small Entities</HD>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996, Public Law 104-121, the Coast Guard wants to assist small entities in understanding this proposed rule so that they can better evaluate its effects on them and participate in the rulemaking. If the proposed rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact the person in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this NPRM. The Coast Guard will not retaliate against 
                    <PRTPAGE P="20834"/>
                    small entities that question or complain about this proposed rule or any policy or action of the Coast Guard.
                </P>
                <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247).</P>
                <HD SOURCE="HD2">D. Collection of Information</HD>
                <P>
                    This proposed rule would call for no new collection of information under the Paperwork Reduction Act of 1995, 44 U.S.C. 3501-3520. While the proposed rule would remove recordkeeping requirements of NFPA 10, the Coast Guard did not account for this burden in the Collection of Information analysis performed for the “Fire Protection” final rule (81 FR 48220), which modified the Collection of Information, 
                    <E T="03">Certificates of Compliance, Boiler/Pressure Vessel Repairs, Cargo Gear Records, Shipping Papers, and NFPA 10 Certificates, OMB Control Number 1625-0037,</E>
                     because the Coast Guard never intended to apply these requirements to recreational vessels. Therefore, this action will not modify the existing collection of information.
                </P>
                <HD SOURCE="HD2">E. Federalism</HD>
                <P>A rule has implications for federalism under Executive Order 13132 (Federalism) if it has a substantial direct effect on States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. We have analyzed this proposed rule under Executive Order 13132 and have determined that it is consistent with the fundamental federalism principles and preemption requirements described in Executive Order 13132. Our analysis follows.</P>
                <P>It is well settled that States may not regulate in categories reserved for regulation by the Coast Guard. The Coast Guard regulates recreational vessel safety, including firefighting equipment, under the authority contained in 46 U.S.C. 4302. Chapter 43 of 46 U.S.C. contains an express preemption provision for recreational vessel safety standards. Under 46 U.S.C. 4306, a State or political subdivision of a State may not establish, continue in effect, or enforce a law or regulation establishing a recreational vessel or associated equipment performance or other safety standard, or impose a requirement for associated equipment unless: (1) The standard is identical to a Coast Guard regulation prescribed under 46 U.S.C. 4302; (2) the Coast Guard specifically provides an exemption under 46 U.S.C. 4305; or (3) the State standard regulates marine safety articles carried or used to address a hazardous condition or circumstance unique to that State (as long as the Coast Guard does not disapprove). This proposed rule would establish minimum requirements, under 46 U.S.C. 4302, for fire extinguishing equipment for recreational vessels, and therefore, the States may not issue regulations that differ from Coast Guard regulations within the categories of safety standards or equipment for recreational vessels, except in the limited circumstances identified above. Therefore, this proposed rule is consistent with the fundamental federalism principles and preemption requirements described in Executive Order 13132.</P>
                <P>
                    Additionally, for rules with federalism implications and preemptive effect, Executive Order 13132 specifically directs agencies to consult with State and local governments during the rulemaking process. If you believe this rule would have implications for federalism under Executive Order 13132, please contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION</E>
                     section of this NPRM.
                </P>
                <HD SOURCE="HD2">F. Unfunded Mandates Reform Act</HD>
                <P>The Unfunded Mandates Reform Act of 1995, 2 U.S.C. 1531-1538, requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Although this proposed rule would not result in such an expenditure, we discuss the effects of this proposed rule elsewhere in this NPRM.</P>
                <HD SOURCE="HD2">G. Taking of Private Property</HD>
                <P>This proposed rule would not cause a taking of private property or otherwise have taking implications under Executive Order 12630 (Governmental Actions and Interference with Constitutionally Protected Property Rights).</P>
                <HD SOURCE="HD2">H. Civil Justice Reform</HD>
                <P>This proposed rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988 (Civil Justice Reform) to minimize litigation, eliminate ambiguity, and reduce burden.</P>
                <HD SOURCE="HD2">I. Protection of Children</HD>
                <P>We have analyzed this proposed rule under Executive Order 13045 (Protection of Children from Environmental Health Risks and Safety Risks). This proposed rule is not an economically significant rule and would not create an environmental risk to health or risk to safety that might disproportionately affect children.</P>
                <HD SOURCE="HD2">J. Indian Tribal Governments</HD>
                <P>This proposed rule does not have tribal implications under Executive Order 13175 (Consultation and Coordination with Indian Tribal Governments), because it would not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
                <HD SOURCE="HD2">K. Energy Effects</HD>
                <P>The Coast Guard has analyzed this proposed rule under Executive Order 13211 (Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use). We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy.</P>
                <HD SOURCE="HD2">L. Technical Standards</HD>
                <P>
                    The National Technology Transfer and Advancement Act, codified as a note to 15 U.S.C. 272, directs agencies to use voluntary consensus standards in their regulatory activities unless the agency provides Congress, through OMB, with an explanation of why using these standards would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are technical standards (
                    <E T="03">e.g.,</E>
                     specifications of materials, performance, design, or operation; test methods; sampling procedures; and related management systems practices) that are developed or adopted by voluntary consensus standards bodies.
                </P>
                <P>This proposed rule does not use technical standards. Therefore, the Coast Guard did not consider the use of voluntary consensus standards.</P>
                <HD SOURCE="HD2">M. Environment</HD>
                <P>
                    We have analyzed this proposed rule under Department of Homeland 
                    <PRTPAGE P="20835"/>
                    Security Management Directive 023-01, Revision 01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (42 U.S.C. 4321-4370f), and have made a preliminary determination that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. A preliminary Record of Environmental Consideration supporting this determination is available where indicated under the “Public Participation and Request for Comments” section of this NPRM.
                </P>
                <P>This proposed rule meets the criteria for categorical exclusion (CATEX) under paragraphs L52, L54, and L57 of Table 1 in Appendix A of DHS Directive 023-01 (series). The CATEX L52 pertains to regulations concerning vessel operation safety standards; CATEX L54 pertains to regulations that are editorial or procedural, such as those updating addresses or establishing application procedures; and CATEX 57 pertains to regulations concerning manning, documentation, admeasurements, inspection, and equipping of vessels.</P>
                <P>This proposed rule is intended to update Coast Guard regulations pertaining to fire extinguishing requirements and the associated standards used by recreational vessels. The Coast Guard seeks any comments or information that may lead to the discovery of a significant environmental impact from this proposed rule.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>33 CFR Part 175</CFR>
                    <P>Fire prevention, Marine safety.</P>
                    <CFR>46 CFR Part 25</CFR>
                    <P>Fire prevention, Marine safety, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, the Coast Guard proposes to amend 33 CFR part 175 and 46 CFR part 25 as follows:</P>
                <HD SOURCE="HD1">Title 33—Navigation and Navigable Waters</HD>
                <PART>
                    <HD SOURCE="HED">PART 175—EQUIPMENT REQUIREMENTS</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 175 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P> 46 U.S.C. 4302; Department of Homeland Security Delegation No. 0170.1.</P>
                </AUTH>
                <AMDPAR>2. In § 175.3, add in alphabetic order the definition of “Model year” to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 175.3 </SECTNO>
                    <SUBJECT>Definitions.</SUBJECT>
                    <STARS/>
                    <P>
                        <E T="03">Model year</E>
                         means the period beginning August 1 of any year and ending on July 31 of the following year. Each model year is designated by the year in which it ends.
                    </P>
                    <STARS/>
                </SECTION>
                <AMDPAR>3. Add new subpart E to read as follows:</AMDPAR>
                <SUBPART>
                    <HD SOURCE="HED">Subpart E—Fire Protection Equipment</HD>
                </SUBPART>
                <CONTENTS>
                    <SECHD>Sec.</SECHD>
                    <SECTNO>175.301</SECTNO>
                    <SUBJECT>Applicability.</SUBJECT>
                    <SECTNO>175.305</SECTNO>
                    <SUBJECT>General provisions.</SUBJECT>
                    <SECTNO>175.310</SECTNO>
                    <SUBJECT>Portable fire extinguishers and semi-portable fire extinguishing systems.</SUBJECT>
                    <SECTNO>175.315</SECTNO>
                    <SUBJECT>Fixed fire extinguishing systems.</SUBJECT>
                    <SECTNO>175.320</SECTNO>
                    <SUBJECT>Fire extinguishing equipment required.</SUBJECT>
                    <SECTNO>175.380</SECTNO>
                    <SUBJECT>Condition and number of fire extinguishers required for recreational vessels built before model year 2017.</SUBJECT>
                    <SECTNO>175.390</SECTNO>
                    <SUBJECT>Condition and number of fire extinguishers required for recreational vessels built before model year 1953. </SUBJECT>
                </CONTENTS>
                <SECTION>
                    <SECTNO>§ 175.301</SECTNO>
                    <SUBJECT> Applicability.</SUBJECT>
                    <P>(a) This subpart applies to recreational vessels that are propelled or controlled by propulsion machinery.</P>
                    <P>(b) Recreational vessels constructed prior to August 22, 2016, will be deemed built before model year 2017 and must meet the requirements of 33 CFR 175.380.</P>
                    <P>(c) Recreational vessels constructed prior to November 19, 1952, will be deemed built before model year 1953 and must meet the requirements of 33 CFR 175.390.</P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 175.305 </SECTNO>
                    <SUBJECT>General provisions.</SUBJECT>
                    <P>
                        Where fire extinguishing equipment in this subpart is required to be of an approved type, such equipment must be approved as provided in 46 CFR subchapter Q. A listing of current and formerly approved equipment and materials may be found on the internet at: 
                        <E T="03">http://cgmix.uscg.mil/equipment.</E>
                         Each OCMI may be contacted for information concerning approved equipment.
                    </P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 175.310 </SECTNO>
                    <SUBJECT>Portable fire extinguishers and semi-portable fire extinguishing systems.</SUBJECT>
                    <P>(a) All portable and semi-portable fire extinguishers must be of an approved type.</P>
                    <P>(b) Portable and semi-portable fire extinguishers must be maintained in good and serviceable working condition and must—</P>
                    <P>(1) Be carried aboard the vessel;</P>
                    <P>(2) Have a pressure gauge reading or indicator in the operable range or position, if there is one;</P>
                    <P>(3) Not be expired or appear to have been previously used; and</P>
                    <P>(4) Be maintained in accordance with the manufacturer's instructions.</P>
                    <P>(c) Vaporizing-liquid type fire extinguishers containing carbon tetrachloride, chlorobromomethane, or other toxic vaporizing liquids are not acceptable as equipment required by this subpart.</P>
                    <P>(d) Portable or semi-portable extinguishers, which are required by their name plates to be protected from freezing, must not be located where freezing temperatures may be expected.</P>
                    <P>(e) The use of dry chemical stored pressure fire extinguishers not fitted with pressure gauges or indicating devices, manufactured prior to January 1, 1965, is permitted on board recreational vessels if such extinguishers are maintained in good and serviceable condition. The following maintenance and inspections are required for such extinguishers:</P>
                    <P>(1) When the date on the inspection record tag on the extinguishers shows that 6 months have elapsed since the last weight check ashore, then such extinguishers are no longer accepted as meeting required maintenance conditions until they are reweighed ashore, found to be in a serviceable condition, and within required weight conditions.</P>
                    <P>
                        (2) If the weight of the container is 
                        <FR>14</FR>
                         ounce less than that stamped on the container, it must be serviced.
                    </P>
                    <P>(3) If the outer seal or seals (which indicate tampering or use when broken) are not intact, the boarding officer or marine inspector will inspect such extinguishers to see that the frangible disc in the neck of the container is intact; and if such disc is not intact, the container must be serviced.</P>
                    <P>(4) If there is evidence of damage, use, or leakage, such as dry chemical powder observed in the nozzle or elsewhere on the extinguisher, the extinguisher must be serviced or replaced.</P>
                    <P>(f) Dry chemical extinguishers, stored pressure extinguishers, and fire extinguishers without pressure gauges or indicating devices, manufactured after January 1, 1965, cannot be labeled with the marine type label described in 46 CFR 162.028-4. These extinguishers, may be carried onboard recreational vessels as excess equipment, subject to paragraphs (a) and (b).</P>
                    <P>(g) Semi-portable extinguishers must be fitted with a suitable hose and nozzle, or other practicable means, so that all portions of the space concerned may be covered.</P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 175.315 </SECTNO>
                    <SUBJECT>Fixed fire extinguishing systems.</SUBJECT>
                    <P>
                        (a) A fixed fire extinguishing system must be of a type approved or accepted under 46 CFR part 162 when it is installed.
                        <PRTPAGE P="20836"/>
                    </P>
                    <P>(b) A carbon dioxide system must be designed and installed in accordance with 46 CFR 76.15.</P>
                    <P>(c) An automatic sprinkler system must be designed and installed in accordance with 46 CFR 25.30-15(c).</P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 175.320 </SECTNO>
                    <SUBJECT>Fire extinguishing equipment required.</SUBJECT>
                    <P>(a) Recreational vessels 65 feet or less in length.</P>
                    <P>(1) Recreational vessels 65 feet or less in length must carry at least the minimum number of portable fire extinguishers set forth in Table 1 to § 175.320(a). Vessels less than 26 feet in length, propelled by outboard motors, are not required to carry portable fire extinguishers if the construction of the vessels will not permit the entrapment of explosive or flammable gases or vapors.</P>
                    <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s100,13,13">
                        <TTITLE>Table 1 to § 175.320(a)</TTITLE>
                        <BOXHD>
                            <CHED H="1">
                                Length
                                <LI>(feet)</LI>
                            </CHED>
                            <CHED H="1">
                                Minimum number of 5-B portable fire extinguishers required 
                                <SU>1</SU>
                            </CHED>
                            <CHED H="2">
                                If no fixed
                                <LI>fire</LI>
                                <LI>extinguishing</LI>
                                <LI>system in</LI>
                                <LI>machinery</LI>
                                <LI>space</LI>
                            </CHED>
                            <CHED H="2">
                                If fixed fire
                                <LI>extinguishing</LI>
                                <LI>system in</LI>
                                <LI>machinery</LI>
                                <LI>space</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Under 16</ENT>
                            <ENT>1</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">16 or more, but less than 26</ENT>
                            <ENT>1</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">26 or more, but less than 40</ENT>
                            <ENT>2</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">40 or more, but not more than 65</ENT>
                            <ENT>3</ENT>
                            <ENT>2</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             One 20-B portable fire extinguisher may be substituted for two 5-B portable fire extinguishers.
                        </TNOTE>
                    </GPOTABLE>
                    <P>(2) Figure 1 to § 175.320(a)(2) illustrates the conditions under which fire extinguishers are required to be carried on board. Figure 2 to § 175.320(a)(2) illustrates conditions that do not, in themselves, require that fire extinguishers be carried.</P>
                    <BILCOD>BILLING CODE 9110-04-C</BILCOD>
                    <GPH SPAN="3" DEEP="390">
                        <PRTPAGE P="20837"/>
                        <GID>EP13MY19.018</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 9110-04-P</BILCOD>
                    <P>(b) Recreational vessels more than 65 feet in length.</P>
                    <P>(1) Recreational vessels more than 65 feet in length must carry at least the minimum number of portable fire extinguishers specified for their tonnage as set forth in Table 1 to § 175.320(b).</P>
                    <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s10,r10,13">
                        <TTITLE>Table 1 to § 175.320(b)</TTITLE>
                        <BOXHD>
                            <CHED H="1" O="L">Gross tonnage—</CHED>
                            <CHED H="2">More than</CHED>
                            <CHED H="2">Not more than</CHED>
                            <CHED H="1">
                                Minimum
                                <LI>number of</LI>
                                <LI>20-B portable</LI>
                                <LI>fire</LI>
                                <LI>extinguishers</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>50</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">50</ENT>
                            <ENT>100</ENT>
                            <ENT>2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">100</ENT>
                            <ENT>500</ENT>
                            <ENT>3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">500</ENT>
                            <ENT>1,000</ENT>
                            <ENT>6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1,000</ENT>
                            <ENT/>
                            <ENT>8</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>(2) In addition to the portable fire extinguishers required by Table 1 to § 175.320(b), the following fire extinguishing equipment must be fitted in the machinery space:</P>
                    <P>(i) One 20-B fire extinguisher must be carried for each 1,000 brake horsepower of the main engines or fraction. However, not more than six such extinguishers are required to be carried.</P>
                    <P>(ii) On recreational vessels of more than 300 gross tons, either one 160-B semi-portable fire extinguishing system must be fitted, or alternatively, a fixed fire extinguishing system must be fitted in the machinery space.</P>
                    <P>(3) The frame or support of each 160-B semi-portable fire extinguisher required by paragraph (b)(2)(ii) of this section must be welded or otherwise permanently attached to a bulkhead or deck.</P>
                    <P>(4) If an approved semi-portable fire extinguisher has wheels, it must be securely stowed when not in use to prevent it from rolling out of control under heavy sea conditions.</P>
                    <P>(c) Extinguishers with larger numerical ratings or multiple letter designations. Extinguishers with larger numerical ratings or multiple letter designations may be used to meet the requirements of Table 1 to § 175.320(a) and Table 1 to § 175.320(b).</P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 175.380 </SECTNO>
                    <SUBJECT>Condition and number of fire extinguishers required for recreational vessels built before model year 2017.</SUBJECT>
                    <P>Recreational vessels with a model year between 1953 and 2017 must meet the following requirements:</P>
                    <P>(a) Previously installed extinguishers with extinguishing capacities that are less than what is required in Table 1 to § 175.320(a) or Table 1 to § 175.320(b) of this subpart need not be replaced but must be maintained in good condition.</P>
                    <P>(b) All extinguishers installed after August 22, 2016, must meet the applicable requirements in §§ 175.305 through 175.320.</P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 175.390</SECTNO>
                    <SUBJECT> Condition and number of fire extinguishers required for recreational vessels built before model year 1953.</SUBJECT>
                    <P>
                        Recreational vessels built before model year 1953 must meet the applicable number and general type of equipment provisions of §§ 175.305 through 175.320. Existing items of 
                        <PRTPAGE P="20838"/>
                        equipment and installations previously approved but not meeting the applicable requirements for type approval may be continued in service provided they are in good condition. All new installations and replacements must meet the requirements of §§ 175.305 through 175.320.
                    </P>
                    <HD SOURCE="HD1">Title 46—Shipping</HD>
                </SECTION>
                <PART>
                    <HD SOURCE="HED">PART 25—REQUIREMENTS</HD>
                </PART>
                <AMDPAR>4. The authority citation for part 25 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>33 U.S.C. 1903(b); 46 U.S.C. 2103, 3306, 4102, 4302; Department of Homeland Security Delegation No. 0170.1(II)(77), (92)(a), 92(b).</P>
                </AUTH>
                <AMDPAR>5. Revise § 25.30-1 to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 25.30-1 </SECTNO>
                    <SUBJECT>Applicability.</SUBJECT>
                    <P>(a) This subpart applies to all vessels, except for recreational vessels as defined in 33 CFR 175.3.</P>
                    <P>(b) All vessels, except recreational vessels, contracted for before August 22, 2016, and after November 19, 1952, must meet the requirements of 46 CFR 25.30-80.</P>
                    <P>(c) All vessels, except recreational vessels, contracted for before November 19, 1952, must meet the requirements of 46 CFR 25.30-90.</P>
                </SECTION>
                <SIG>
                    <DATED>Dated: May 6, 2019.</DATED>
                    <NAME>John P. Nadeau,</NAME>
                    <TITLE>Assistant Commandant for Prevention Policy, U.S. Coast Guard.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09699 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 9110-04-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Part 52</CFR>
                <DEPDOC>[EPA-R09-OAR-2019-0159; FRL-9993-51-Region 9]</DEPDOC>
                <SUBJECT>Partial Approval, Partial Disapproval and Limited Approval, Limited Disapproval of Arizona Air Plan Revisions, Pinal County Air Quality Control District</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Environmental Protection Agency (EPA) is proposing to partially approve and partially disapprove revisions to the Pinal County Air Quality Control District (PCAQCD) portion of the Arizona State Implementation Plan (SIP). These revisions concern the District's demonstration regarding reasonably available control technology (RACT) requirements and negative declarations for the 2008 8-hour ozone National Ambient Air Quality Standards (NAAQS or “standards”) in the portion of the Phoenix-Mesa ozone nonattainment area under the jurisdiction of the PCAQCD. The EPA is also proposing a limited approval and limited disapproval of two rules PCAQCD submitted with its RACT SIP demonstration. We are proposing action on a local SIP revision under the Clean Air Act (CAA or “Act”). We are taking comments on this proposal and plan to follow with a final action.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Any comments must arrive by June 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments, identified by Docket ID No. EPA-R09-OAR-2019-0159 at 
                        <E T="03">https://www.regulations.gov.</E>
                         For comments submitted at 
                        <E T="03">Regulations.gov</E>
                        , follow the online instructions for submitting comments. Once submitted, comments cannot be edited or removed from 
                        <E T="03">Regulations.gov</E>
                        . The EPA may publish any comment received to its public docket. Do not submit electronically any information you consider to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Multimedia submissions (audio, video, etc.) must be accompanied by a written comment. The written comment is considered the official comment and should include discussion of all points you wish to make. The EPA will generally not consider comments or comment contents located outside of the primary submission (
                        <E T="03">i.e.</E>
                         on the web, cloud, or other file sharing system). For additional submission methods, please contact the person identified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section. For the full EPA public comment policy, information about CBI or multimedia submissions, and general guidance on making effective comments, please visit 
                        <E T="03">https://www.epa.gov/dockets/commenting-epa-dockets.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Stanley Tong, EPA Region IX, (415) 947-4122, 
                        <E T="03">tong.stanley@epa.gov.</E>
                         EPA Region IX is located at 75 Hawthorne Street, San Francisco, CA 94105-3901.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Throughout this document, “we,” “us” and “our” refer to the EPA.</P>
                <HD SOURCE="HD1">Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. The State's Submittal</FP>
                    <FP SOURCE="FP1-2">A. What documents did the State submit?</FP>
                    <FP SOURCE="FP1-2">B. Are there other versions of these documents?</FP>
                    <FP SOURCE="FP1-2">C. What is the purpose of the submitted documents?</FP>
                    <FP SOURCE="FP-2">II. The EPA's Evaluation and Proposed Action</FP>
                    <FP SOURCE="FP1-2">A. How is the EPA evaluating the submitted documents?</FP>
                    <FP SOURCE="FP1-2">B. Do the documents meet the evaluation criteria?</FP>
                    <FP SOURCE="FP1-2">C. What are the deficiencies?</FP>
                    <FP SOURCE="FP1-2">D. EPA Recommendations To Further Improve the RACT SIP and the Submitted Rules</FP>
                    <FP SOURCE="FP1-2">E. Public Comment and Proposed Action</FP>
                    <FP SOURCE="FP-2">III. Incorporation by Reference</FP>
                    <FP SOURCE="FP-2">IV. Statutory and Executive Order Reviews</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. The State's Submittal</HD>
                <HD SOURCE="HD2">A. What documents did the State submit?</HD>
                <P>Table 1 lists the documents addressed by this proposal with the dates that they were adopted by the local air agency and submitted by the Arizona Department of Environmental Quality (ADEQ).</P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="xs65,r50,18,18">
                    <TTITLE>Table 1—Submitted Documents</TTITLE>
                    <BOXHD>
                        <CHED H="1">Local agency</CHED>
                        <CHED H="1">Document</CHED>
                        <CHED H="1">Adopted</CHED>
                        <CHED H="1">Submitted</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">PCAQCD</ENT>
                        <ENT>Reasonably Available Control Technology (RACT) Analysis, Negative Declaration and Rules Adoption</ENT>
                        <ENT>11/30/2016</ENT>
                        <ENT>2/3/2017</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PCAQCD</ENT>
                        <ENT>Chapter 5, Article 13 Surface Coating Operations</ENT>
                        <ENT>11/30/2016</ENT>
                        <ENT>2/3/2017</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>5-13-100, “General”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>5-13-200, “Definitions”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>5-13-300, “Standards”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>5-13-400, “Administrative Requirements”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>5-13-500, “Monitoring and Records”</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20839"/>
                        <ENT I="22"> </ENT>
                        <ENT>Note: the submittal explicitly excludes 5-13-390 “Spray Paint and Other Surface Coating Operations” (as amended 10/12/95)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PCAQCD</ENT>
                        <ENT>Chapter 5, Article 20 Storage and Loading of Gasoline at Gasoline Dispensing Facilities</ENT>
                        <ENT>11/30/2016</ENT>
                        <ENT>2/3/2017</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>5-20-100 “General”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>5-20-200 “Definitions”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>5-20-300 “Standards”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>5-20-400 “Administrative Requirements”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>5-20-500 “Monitoring and Records”</ENT>
                    </ROW>
                </GPOTABLE>
                <P>On August 3, 2017, the submittals for PCAQCD's RACT SIP, negative declarations, and two rules were deemed by operation of law to meet the completeness criteria in 40 CFR part 51 Appendix V, which must be met before formal EPA review.</P>
                <HD SOURCE="HD2">B. Are there other versions of these documents?</HD>
                <P>There are no previous versions of the RACT SIP and negative declarations in the PCAQCD portion of the Arizona SIP for the 2008 8-hour ozone NAAQS. There are no previous versions of Chapter 5, Articles 13 or 20 in the PCAQCD portion of the Arizona SIP.</P>
                <HD SOURCE="HD2">C. What is the purpose of the submitted documents?</HD>
                <P>
                    Volatile Organic Compounds (VOCs) and oxides of nitrogen (NO
                    <E T="52">X</E>
                    ) help produce ground-level ozone, smog, and particulate matter, which harm human health and the environment. Section 110(a) of the CAA requires states to submit regulations that control VOC and NO
                    <E T="52">X</E>
                     emissions. Sections 182(b)(2) and (f) require that SIPs for ozone nonattainment areas classified as Moderate or above implement RACT for any source covered by a Control Techniques Guidelines (CTG) document and for any major source of VOCs or NO
                    <E T="52">X</E>
                    . The PCAQCD is subject to this requirement as it regulates the Pinal County portion of the Phoenix-Mesa ozone nonattainment area that is currently designated and classified as a Moderate nonattainment area for the 2008 8-hour ozone NAAQS. Therefore, the PCAQCD must, at a minimum, adopt RACT-level controls for all sources covered by a CTG document and for all major non-CTG sources of VOCs or NO
                    <E T="52">X</E>
                     within the ozone nonattainment area that it regulates. Any stationary source that emits or has the potential to emit at least 100 tons per year (tpy) of VOCs or NO
                    <E T="52">X</E>
                     is a major stationary source in a Moderate ozone nonattainment area (CAA section 182(b)(2), (f) and 302(j)).
                </P>
                <P>
                    Section III.D of the preamble to the EPA's final rule to implement the 2008 ozone NAAQS (80 FR 12264, March 6, 2015) discusses RACT requirements. It states in part that RACT SIPs must contain adopted RACT regulations, certifications where appropriate that existing provisions are RACT, and/or negative declarations that no sources in the nonattainment area are covered by a specific CTG. Id. at 12278. It also provides that states must submit appropriate supporting information for their RACT submissions as described in the EPA's implementation rule for the 1997 ozone NAAQS. See Id. and 70 FR 71612, 71652 (November 29, 2005). The submitted RACT SIP (“
                    <E T="03">2016 RACT SIP”</E>
                    ) and negative declarations provide PCAQCD's analyses of its compliance with the CAA section 182 RACT requirements for the 2008 8-hour ozone NAAQS. PCAQCD also adopted and submitted for SIP approval the following two rules with its 
                    <E T="03">2016 RACT SIP.</E>
                </P>
                <P>Chapter 5, Article 13 is a new rule that establishes VOC content limits for surface coating operations in the Pinal County portion of the Phoenix-Mesa 8-hour ozone nonattainment area. It contains: Definitions; VOC content limits; various partial exemptions; requirements for coating application methods, cleanup of application equipment, work practices for the handling, disposal and storage of VOC containing materials, and emission control systems; and requirements for monitoring, testing, and recordkeeping.</P>
                <P>Chapter 5, Article 20 is a new rule that establishes limits for VOC emissions from gasoline during storage and loading of gasoline at gasoline dispensing facilities. It contains: Definitions; various exemptions; requirements for vapor recovery equipment, general housekeeping, gasoline storage equipment, and gasoline loading operations; and requirements for monitoring, testing, and recordkeeping.</P>
                <P>The EPA's technical support document (TSD) has more information about the District's RACT SIP, negative declarations, rules, and the EPA's evaluations thereof.</P>
                <HD SOURCE="HD1">II. The EPA's Evaluation and Proposed Action</HD>
                <HD SOURCE="HD2">A. How is the EPA evaluating the submitted documents?</HD>
                <P>
                    SIP rules must require RACT for each category of sources covered by a CTG document as well as each major source of VOCs or NO
                    <E T="52">X</E>
                     in ozone nonattainment areas classified as Moderate or above (CAA section 182(b)(2)). The PCAQCD regulates a Moderate ozone nonattainment area (40 CFR 81.303) so the District's rules must implement RACT.
                </P>
                <P>
                    States should also submit for SIP approval negative declarations for those source categories for which they have not adopted CTG-based regulations (because they have no sources above the CTG-recommended applicability threshold) regardless of whether such negative declarations were made for an earlier SIP.
                    <SU>1</SU>
                    <FTREF/>
                     To do so, the submittal should provide reasonable assurance that no sources subject to the CTG requirements currently exist in the portion of the ozone nonattainment area that is regulated by the PCAQCD.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         57 FR 13498, 13512 (April 16, 1992).
                    </P>
                </FTNT>
                <P>
                    The District's analysis must demonstrate that each major source of VOCs or NO
                    <E T="52">X</E>
                     in the ozone nonattainment area is covered by a RACT-level rule. In addition, for each CTG source category, the District must either demonstrate that a RACT-level rule is in place, or submit a negative declaration. Guidance and policy documents that we use to evaluate CAA section 182 RACT requirements include the following:
                </P>
                <P>1. “State Implementation Plans; General Preamble for the Implementation of Title I of the Clean Air Act Amendments of 1990,” 57 FR 13498 (April 16, 1992); 57 FR 18070 (April 28, 1992).</P>
                <P>
                    2. EPA Office of Air Quality Planning and Standards, “Issues Relating to VOC Regulation Cutpoints, Deficiencies, and 
                    <PRTPAGE P="20840"/>
                    Deviations,” May 25, 1988 (“the Bluebook,” revised January 11, 1990).
                </P>
                <P>3. EPA Region IX, “Guidance Document for Correcting Common VOC &amp; Other Rule Deficiencies,” August 21, 2001 (“the Little Bluebook”).</P>
                <P>
                    4. “State Implementation Plans; Nitrogen Oxides Supplement to the General Preamble; Clean Air Act Amendments of 1990 Implementation of Title I; Proposed Rule,” (the NO
                    <E T="52">X</E>
                     Supplement), 57 FR 55620, (November 25, 1992).
                </P>
                <P>5. Memorandum dated May 18, 2006, from William T. Harnett, Director, Air Quality Policy Division, to Regional Air Division Directors, Subject: “RACT Qs &amp; As—Reasonably Available Control Technology (RACT): Questions and Answers.”</P>
                <P>6. “Final Rule to Implement the 8-hour Ozone National Ambient Air Quality Standard—Phase 2,” 70 FR 71612 (November 29, 2005).</P>
                <P>7. “Implementation of the 2008 National Ambient Air Quality Standards for Ozone: State Implementation Plan Requirements,” 80 FR 12264 (March 6, 2015).</P>
                <P>Rules that are submitted for inclusion into the SIP must be enforceable (CAA section 110(a)(2)), must not interfere with applicable requirements concerning attainment and reasonable further progress or other CAA requirements (CAA section 110(l)), and must not modify certain SIP control requirements in nonattainment areas without ensuring equivalent or greater emissions reductions (CAA section 193).</P>
                <P>In addition to the documents listed above, guidance and policy documents that we use to evaluate enforceability, stringency, and revision/relaxation requirements include the following:</P>
                <P>1. “Design Criteria for Stage I Vapor Control Systems—Gasoline Service Stations,” EPA-450/R-75-102, November 1975.</P>
                <P>2. “Control of Volatile Organic Emissions from Existing Stationary Sources—Volume VI: Surface Coating of Miscellaneous Metal Parts and Products,” EPA-450/2-78-015, June 1978.</P>
                <P>3. “Control Techniques Guidelines for Miscellaneous Metal and Plastic Parts Coatings,” EPA 453/R-08-003, September 2008.</P>
                <P>4. “Model Volatile Organic Compound Rules for Reasonably Available Control Technology,” June 1992.</P>
                <P>5. Memorandum dated March 17, 2011, from Scott Mathias, Interim Director, Air Quality Policy Division, U.S. EPA to Regional Air Division Directors, Subject: “Approving SIP Revisions Addressing VOC RACT Requirements for Certain Coatings Categories.”</P>
                <HD SOURCE="HD2">B. Do the documents meet the evaluation criteria?</HD>
                <P>
                    PCAQCD's 
                    <E T="03">2016 RACT SIP</E>
                     provides the District's demonstration that the applicable SIP for the PCAQCD satisfies CAA section 182 RACT requirements for the 2008 8-hour ozone NAAQS. This conclusion is based on the District's analysis of SIP-approved requirements that apply to the following: (1) Source categories for which a CTG has been issued, and (2) major non-CTG stationary sources of VOC or NO
                    <E T="52">X</E>
                     emissions.
                </P>
                <P>With respect to CTG source categories, PCAQCD determined that it only had sources subject to the CTGs covering surface coatings and gasoline service stations. PCAQCD submitted for SIP approval two rules to implement RACT for these categories: Chapter 5, Article 13 Surface Coating Operations, and Chapter 5, Article 20 Storage and Loading of Gasoline at Gasoline Dispensing Facilities. We find that these rules meet the enforceability, stringency, and SIP relaxation/revision requirements, with the exception of a number of identified deficiencies. Specifically, we find that Article 13 largely incorporates the VOC content limits from Table 2 of the 2008 Miscellaneous Metal and Plastic Parts (MMPP) Coatings CTG. However, Article 13 does not contain all of the recommended metal parts coating categories from the CTG, it allows some exemptions not found in the CTG, and it does not address recommended categories and limits in Tables 3 through 6 of the MMPP CTG. We also find that Article 20 needs to be strengthened to correct an enforceability issue. These approvability issues preclude full approval of these two rules. In spite of these deficiencies, inclusion of these two rules would substantially strengthen the SIP because the SIP does not currently contain rules covering these sources. Our TSD has more information about our evaluation of Articles 13 and 20.</P>
                <P>
                    Where there are no existing sources covered by a particular CTG document, or no major non-CTG sources, states may, in lieu of adopting RACT requirements for those sources, adopt negative declarations certifying that there are no such sources in the relevant nonattainment area. Appendix C of the 
                    <E T="03">2016 RACT SIP</E>
                     lists the District's negative declarations where it has no sources subject to the applicable CTG for the 2008 8-hour ozone NAAQS. These negative declarations are re-listed in Table 2 below. The District concludes that it has no sources subject to the CTGs based on a review of its permit files and emission inventory as well as business listings and county planning records.
                </P>
                <P>
                    In addition, the 
                    <E T="03">2016 RACT SIP</E>
                     states “[t]here is one Title V (
                    <E T="03">i.e.,</E>
                     major source) in the Pinal County portion of the nonattainment area which is a landfill . . . [and the] facility is currently subject to the 40 CFR part 60, subpart WWW Standards of Performance (NSPS) for Municipal Solid Waste Landfills and the 40 CFR part 63, subpart AAAA National Emission Standards for Hazardous Air Pollutants (NESHAP) for Municipal Waste Landfills.” Appendix A of the 
                    <E T="03">2016 RACT SIP</E>
                     indicates this landfill has a potential to emit of 15.1 tpy of VOC. As described in more detail in our TSD, this landfill has a potential to emit less than 100 tpy of VOC and thus is not a major source. The District is therefore not required to demonstrate that this source is implementing RACT-level controls.
                </P>
                <P>
                    We reviewed PCAQCD's list of permitted facilities and list of negative declarations in the 
                    <E T="03">2016 RACT SIP</E>
                     Appendices A and C, respectively. We also searched the EPA's National Emissions Inventory for 2011 and 2014 to verify the District's conclusion that it has no stationary sources subject to the CTG source categories for which it has adopted a negative declaration. We agree with the District's negative declarations in the 
                    <E T="03">2016 RACT SIP</E>
                     Appendix C. However, our review found that the cutback asphalt CTG and certain sections of the MMPP CTG were not addressed by either a negative declaration or a RACT rule. Also, the District must adopt negative declarations for major VOC and major NO
                    <E T="52">X</E>
                     sources since available data shows the District does not have stationary sources in the ozone nonattainment area that emit at least 100 tpy. These approvability issues preclude full approval of the 
                    <E T="03">2016 RACT SIP.</E>
                     Our TSD has more information on our evaluation of the 
                    <E T="03">2016 RACT SIP.</E>
                    <PRTPAGE P="20841"/>
                </P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="xs120,r100">
                    <TTITLE>Table 2—PCAQCD Negative Declarations</TTITLE>
                    <BOXHD>
                        <CHED H="1">EPA document No.</CHED>
                        <CHED H="1">Title</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">EPA-450/2-77-008</ENT>
                        <ENT>Surface Coating of Cans.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-77-008</ENT>
                        <ENT>Surface Coating of Coils.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-77-008</ENT>
                        <ENT>Surface Coating of Paper.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-77-008</ENT>
                        <ENT>Surface Coating of Fabric.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-77-008</ENT>
                        <ENT>Surface Coating of Automobiles and Light-Duty Trucks.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-77-022</ENT>
                        <ENT>Solvent Metal Cleaning.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-77-025</ENT>
                        <ENT>Refinery Vacuum Producing Systems, Wastewater Separators, and Process Unit Turnarounds.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-77-026</ENT>
                        <ENT>Tank Truck Gasoline Loading Terminals.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-77-032</ENT>
                        <ENT>Surface Coating of Metal Furniture.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-77-033</ENT>
                        <ENT>Surface Coating of Insulation of Magnet Wire.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-77-034</ENT>
                        <ENT>Surface Coating of Large Appliances.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-77-035</ENT>
                        <ENT>Bulk Gasoline Plants.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-77-036</ENT>
                        <ENT>Storage of Petroleum Liquids in Fixed-Roof Tanks.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-78-029</ENT>
                        <ENT>Manufacture of Synthesized  Pharmaceutical Products.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-78-030</ENT>
                        <ENT>Manufacture of Pneumatic Rubber Tires.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-78-032</ENT>
                        <ENT>Factory Surface Coating of Flat Wood Paneling.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-78-033</ENT>
                        <ENT>Graphic Arts-Rotogravure and Flexography.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-78-036</ENT>
                        <ENT>Leaks from Petroleum Refinery Equipment.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-78-047</ENT>
                        <ENT>Petroleum Liquid Storage in External Floating Roof Tanks.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/2-78-051</ENT>
                        <ENT>Leaks from Gasoline Tank Trucks and Vapor Collection Systems.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/3-82-009</ENT>
                        <ENT>Large Petroleum Dry Cleaners.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/3-83-006</ENT>
                        <ENT>Leaks from Synthetic Organic Chemical Polymer and Resin Manufacturing Equipment.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/3-83-007</ENT>
                        <ENT>Leaks from Natural Gas/Gasoline Processing Plants.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/3-83-008</ENT>
                        <ENT>Manufacture of High-Density Polyethylene, Polypropylene, and Polystyrene Resins.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/3-84-015</ENT>
                        <ENT>Air Oxidation Processes in Synthetic Organic Chemical Manufacturing Industry.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-450/4-91-031</ENT>
                        <ENT>Reactor Processes and Distillation Operations in Synthetic Organic Chemical Manufacturing Industry.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-453/R-96-007</ENT>
                        <ENT>Wood Furniture Manufacturing Operations.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-453/R-94-032, 61 FR 44050; 8/27/96</ENT>
                        <ENT>ACT Surface Coating at Shipbuilding and Ship Repair Facilities Shipbuilding and Ship Repair Operations (Surface Coating).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-453/R-97-004, 59 FR 29216; 6/06/94</ENT>
                        <ENT>Aerospace MACT and Aerospace (CTG &amp; MACT).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-453/R-06-001</ENT>
                        <ENT>Industrial Cleaning Solvents.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-453/R-06-002</ENT>
                        <ENT>Offset Lithographic Printing and Letterpress Printing.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-453/R-06-003</ENT>
                        <ENT>Flexible Package Printing.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA-453/R-06-004</ENT>
                        <ENT>Flat Wood Paneling Coatings.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA 453/R-07-003</ENT>
                        <ENT>Paper, Film, and Foil Coatings.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA 453/R-07-004</ENT>
                        <ENT>Large Appliance Coatings.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA 453/R-07-005</ENT>
                        <ENT>Metal Furniture Coatings.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA 453/R-08-004</ENT>
                        <ENT>Fiberglass Boat Manufacturing Materials.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA 453/R-08-005</ENT>
                        <ENT>Miscellaneous Industrial Adhesives.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EPA 453/R-08-006</ENT>
                        <ENT>Automobile and Light-Duty Truck Assembly Coatings.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">C. What are the deficiencies?</HD>
                <P>
                    On March 11, 2019,
                    <SU>2</SU>
                    <FTREF/>
                     the EPA provided comments to PCAQCD on the approvability issues in the 
                    <E T="03">2016 RACT SIP</E>
                     and the submitted rules. The following provisions do not satisfy the requirements of section 110 and part D of title I of the Act and prevent full approval of the 
                    <E T="03">2016 RACT SIP</E>
                     and submitted rules.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Letter dated March 11, 2019, from Doris Lo, Manager, Rules Office, EPA, Region IX, to Michael Sundblom, Director, Pinal County Air Quality Control District, Subject: “RE: EPA Comments on the Pinal County Air Quality Control District Reasonably Available Control Technology (RACT) Analysis, Negative Declaration and Rules Adoption.”
                    </P>
                </FTNT>
                <HD SOURCE="HD3">1. 2016 RACT SIP</HD>
                <P>
                    a. Missing negative declarations for major VOC sources and major NO
                    <E T="52">X</E>
                     sources.
                </P>
                <P>b. Missing negative declaration (or rule) for cutback asphalt.</P>
                <HD SOURCE="HD3">2. Chapter 5, Article 13—Surface Coating Operations</HD>
                <P>a. Rule exempts categories that are recommended for regulation by the CTG.</P>
                <P>
                    b. One VOC content limit is less stringent than the CTG, and some CTG coating categories and Tables 3 through 6 of the MMPP CTG are not addressed.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The deficiency regarding the lack of coverage for Tables 3 through 6 can be addressed by either modifying Chapter 5, Article 13 to cover these categories of sources, or through a negative declaration for these tables.
                    </P>
                </FTNT>
                <P>c. The emission control system requirements are potentially confusing and should be clarified.</P>
                <HD SOURCE="HD3">3. Chapter 5, Article 20—Storage and Loading of Gasoline at Gasoline Dispensing Facilities</HD>
                <P>a. An exemption to verify that a gasoline cargo tank has a valid vapor tightness certification decal prior to loading gasoline is overly broad and challenging to verify or enforce.</P>
                <P>b. One section must be reworded to state a prohibition.</P>
                <P>Our TSD has additional information on the deficiencies in the RACT SIP and submitted rules.</P>
                <HD SOURCE="HD2">D. EPA Recommendations To Further Improve the RACT SIP and the Submitted Rules</HD>
                <P>
                    Our March 11, 2019 comment letter and TSD include recommendations for the next time the local agency modifies the rules. These recommendations would strengthen and improve enforceability of the rules. Our comment letter also includes a recommendation to adopt a negative declaration for the 2016 CTG for the Oil and Natural Gas Industry. Our comment letter and TSD are included in the docket materials.
                    <PRTPAGE P="20842"/>
                </P>
                <HD SOURCE="HD2">E. Public Comment and Proposed Action</HD>
                <P>
                    For the reasons discussed above and explained more fully in our TSD, the EPA proposes to partially approve and partially disapprove the ADEQ's February 3, 2017 submittal of the PCAQCD 
                    <E T="03">2016 RACT SIP</E>
                     as a revision to the Arizona SIP. Under CAA section 110(k)(3), we propose to approve the 
                    <E T="03">2016 RACT SIP,</E>
                     with the exception of major VOC sources, major NO
                    <E T="52">X</E>
                     sources, and the following CTG source categories: Cutback asphalt, MMPP coatings, Gasoline Service Stations, and Surface Coating of Miscellaneous Metal Parts and Products, as satisfying the RACT requirements of CAA section 182(b)(2) and (f) for the Pinal County portion of the Phoenix-Mesa ozone nonattainment areas.
                </P>
                <P>
                    Also under CAA section 110(k)(3), we propose to disapprove the 
                    <E T="03">2016 RACT SIP</E>
                     as it pertains to major VOC sources, major NO
                    <E T="52">X</E>
                     sources, cutback asphalt, and the MMPP coatings CTG (Tables 3 through 6) based on the EPA's finding that these categories were not adequately addressed in the 
                    <E T="03">2016 RACT SIP.</E>
                </P>
                <P>
                    Because the inclusion of Chapter 5, Articles 13 and 20 would strengthen the SIP, we are proposing a limited approval of Chapter 5, Article 13 (excluding 5-13-390) 
                    <SU>4</SU>
                    <FTREF/>
                     and Article 20, as authorized by sections 110(k)(3) and 301(a) of the Act. If finalized, this action would incorporate the submitted rules into the SIP, including those provisions identified as deficient. This approval is limited because the EPA is simultaneously proposing a limited disapproval of Chapter 5, Articles 13 and 20, under section 110(k)(3) based on the stringency and enforceability issues the EPA identified in these rules.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         PCAQCD's SIP submittal explicitly excludes section 5-13-390.
                    </P>
                </FTNT>
                <P>
                    Because Chapter 5, Article 13 is the rule the District submitted in fulfillment of its RACT SIP obligation for the 1978 CTG for Surface Coating of Miscellaneous Metal Parts and Products, and the 2008 CTG for MMPP Coatings (except for Tables 3 through 6), the proposed limited approval and limited disapproval of Chapter 5, Article 13 would not fully satisfy the District's RACT SIP obligation for these two CTG source categories. Once the EPA approves a SIP revision to correct the deficiencies in Chapter 5, Article 13, the District's RACT SIP obligation will be met for the Surface Coating of Miscellaneous Metal Parts and Products CTG, and the MMPP Coatings CTG (except for Tables 3 through 6).
                    <SU>5</SU>
                    <FTREF/>
                     Similarly, because Chapter 5, Article 20 was submitted in fulfillment of the District's RACT SIP obligation for the 1975 Gasoline Service Stations CTG, the proposed limited approval and limited disapproval of this rule would not fully satisfy the District's RACT SIP obligation for this CTG source category. Once the EPA approves a SIP revision to correct the deficiencies in Chapter 5, Article 20, the District's RACT SIP obligation will be met for the Gasoline Service Stations CTG source category.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         We will evaluate how the District addresses the MMPP CTG Tables 3 through 6 in its future submittal. As noted above, the District may either modify Chapter 5, Article 13 to cover these sources, or adopt a negative declaration.
                    </P>
                </FTNT>
                <P>
                    The EPA is committed to working with the ADEQ and PCAQCD to resolve the identified RACT deficiencies. However, should we finalize the proposed partial disapproval of the above-enumerated elements of the 
                    <E T="03">2016 RACT SIP</E>
                     and the limited disapproval of Chapter 5, Articles 13 and 20, the action would trigger a 2-year clock for the federal implementation plan (FIP) requirement under section 110(c). In addition, final disapproval would trigger sanctions under CAA section 179 and 40 CFR 52.31 unless the EPA approves subsequent SIP revisions that correct the deficiencies in the 
                    <E T="03">2016 RACT SIP</E>
                     and two submitted rules within 18 months of the effective date of the final action.
                </P>
                <P>
                    We will accept comments from the public on the proposed partial approval and partial disapproval for the 
                    <E T="03">2016 RACT SIP</E>
                     and the proposed limited approval and limited disapproval for Chapter 5, Articles 13 and 20 until June 12, 2019. If finalized, this action would incorporate the 
                    <E T="03">2016 RACT SIP,</E>
                     negative declarations, and submitted rules into the SIP, including those provisions identified as deficient. Our proposed approval of the submitted rules is limited because the EPA is simultaneously proposing a limited disapproval of the rules under section 110(k)(3).
                </P>
                <P>
                    Note that the submitted rules have been adopted by the PCAQCD, and the EPA's final limited disapproval would not prevent the local agency from enforcing them. The limited disapproval also would not prevent any portion of the rules from being incorporated by reference into the federally enforceable SIP as discussed in a Memorandum dated July 9, 1992, from John Calcagni, Director, Air Quality Management Division, U.S. EPA to EPA Regional Air Directors, Regions I-X, Subject: “Processing of State Implementation Plan (SIP) Submittals,” found at: 
                    <E T="03">https://www.epa.gov/sites/production/files/2015-07/documents/procsip.pdf.</E>
                </P>
                <HD SOURCE="HD1">III. Incorporation by Reference</HD>
                <P>
                    In this rule, the EPA is proposing to include in a final EPA rule regulatory text that includes incorporation by reference. In accordance with requirements of 1 CFR 51.5, the EPA is proposing to incorporate by reference the PCAQCD rules described in Table 1 of this preamble. The EPA has made, and will continue to make, these materials available through 
                    <E T="03">www.regulations.gov</E>
                     and at the EPA Region IX Office (please contact the person identified in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this preamble for more information).
                </P>
                <HD SOURCE="HD1">IV. Statutory and Executive Order Reviews</HD>
                <P>
                    Additional information about these statutes and Executive Orders can be found at 
                    <E T="03">https://www.epa.gov/laws-regulations/laws-and-executive-orders.</E>
                </P>
                <HD SOURCE="HD2">A. Executive Order 12866: Regulatory Planning and Review and Executive Order 13563: Improving Regulation and Regulatory Review</HD>
                <P>This proposed action is not a significant regulatory action and was therefore not submitted to the Office of Management and Budget (OMB) for review.</P>
                <HD SOURCE="HD2">B. Executive Order 13771: Reducing Regulations and Controlling Regulatory Costs</HD>
                <P>This proposed action is not an Executive Order 13771 regulatory action because SIP approvals, including limited approvals, are exempted under Executive Order 12866.</P>
                <HD SOURCE="HD2">C. Paperwork Reduction Act (PRA)</HD>
                <P>This proposed action does not impose an information collection burden under the PRA because this action does not impose additional requirements beyond those imposed by state law.</P>
                <HD SOURCE="HD2">D. Regulatory Flexibility Act (RFA)</HD>
                <P>I certify that this action will not have a significant economic impact on a substantial number of small entities under the RFA. This action will not impose any requirements on small entities beyond those imposed by state law.</P>
                <HD SOURCE="HD2">E. Unfunded Mandates Reform Act (UMRA)</HD>
                <P>
                    This proposed action does not contain any unfunded mandate as described in UMRA, 2 U.S.C. 1531-1538, and does not significantly or uniquely affect small governments. This proposed action does 
                    <PRTPAGE P="20843"/>
                    not impose additional requirements beyond those imposed by state law. Accordingly, no additional costs to state, local, or tribal governments, or to the private sector, will result from this proposed action.
                </P>
                <HD SOURCE="HD2">F. Executive Order 13132: Federalism</HD>
                <P>This proposed action does not have federalism implications. It will not have substantial direct effects on the states, on the relationship between the national government and the states, or on the distribution of power and responsibilities among the various levels of government.</P>
                <HD SOURCE="HD2">G. Executive Order 13175: Coordination With Indian Tribal Governments</HD>
                <P>This proposed action does not have tribal implications, as specified in Executive Order 13175, because the SIP is not approved to apply on any Indian reservation land or in any other area where the EPA or an Indian tribe has demonstrated that a tribe has jurisdiction, and will not impose substantial direct costs on tribal governments or preempt tribal law. Thus, Executive Order 13175 does not apply to this proposed action.</P>
                <HD SOURCE="HD2">H. Executive Order 13045: Protection of Children From Environmental Health Risks and Safety Risks</HD>
                <P>The EPA interprets Executive Order 13045 as applying only to those regulatory actions that concern environmental health or safety risks that the EPA has reason to believe may disproportionately affect children, per the definition of “covered regulatory action” in section 2-202 of the Executive Order. This proposed action is not subject to Executive Order 13045 because it does not impose additional requirements beyond those imposed by state law.</P>
                <HD SOURCE="HD2">I. Executive Order 13211: Actions That Significantly Affect Energy Supply, Distribution, or Use</HD>
                <P>This proposed action is not subject to Executive Order 13211, because it is not a significant regulatory action under Executive Order 12866.</P>
                <HD SOURCE="HD2">J. National Technology Transfer and Advancement Act (NTTAA)</HD>
                <P>Section 12(d) of the NTTAA directs the EPA to use voluntary consensus standards in its regulatory activities unless to do so would be inconsistent with applicable law or otherwise impractical. The EPA believes that this proposed action is not subject to the requirements of section 12(d) of the NTTAA because application of those requirements would be inconsistent with the CAA.</P>
                <HD SOURCE="HD2">K. Executive Order 12898: Federal Actions To Address Environmental Justice in Minority Populations and Low-Income Population</HD>
                <P>The EPA lacks the discretionary authority to address environmental justice in this rulemaking.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 52</HD>
                    <P>Environmental protection, Air pollution control, Incorporation by reference, Intergovernmental relations, Nitrogen dioxide, Ozone, Reporting and recordkeeping requirements, Volatile organic compounds.</P>
                </LSTSUB>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                         42 U.S.C. 7401 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: April 30, 2019.</DATED>
                    <NAME>Michael Stoker,</NAME>
                    <TITLE>Regional Administrator, Region IX.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09830 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Part 180</CFR>
                <DEPDOC>[EPA-HQ-OPP-2019-0041; FRL-9991-91]</DEPDOC>
                <SUBJECT>Receipt of Several Pesticide Petitions Filed for Residues of Pesticide Chemicals in or on Various Commodities</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of filing of petitions and request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document announces the Agency's receipt of several initial filings of pesticide petitions requesting the establishment or modification of regulations for residues of pesticide chemicals in or on various commodities.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before June 12, 2019.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit your comments, identified by docket identification (ID) number and the pesticide petition number (PP) of interest as shown in the body of this document, by one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                         Follow the online instructions for submitting comments. Do not submit electronically any information you consider to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         OPP Docket, Environmental Protection Agency Docket Center (EPA/DC), (28221T), 1200 Pennsylvania Ave. NW, Washington, DC 20460-0001.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         To make special arrangements for hand delivery or delivery of boxed information, please follow the instructions at 
                        <E T="03">http://www.epa.gov/dockets/contacts.html.</E>
                    </P>
                    <FP>
                        Additional instructions on commenting or visiting the docket, along with more information about dockets generally, is available at 
                        <E T="03">http://www.epa.gov/dockets.</E>
                    </FP>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Michael Goodis, Registration Division (RD) (7505P), main telephone number: (703) 305-7090, email address: 
                        <E T="03">RDFRNotices@epa.gov.</E>
                         The mailing address for each contact person is: Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Ave. NW, Washington, DC 20460-0001. As part of the mailing address, include the contact person's name, division, and mail code. The division to contact is listed at the end of each pesticide petition summary.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. General Information</HD>
                <HD SOURCE="HD2">A. Does this action apply to me?</HD>
                <P>You may be potentially affected by this action if you are an agricultural producer, food manufacturer, or pesticide manufacturer. 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>• Crop production (NAICS code 111).</P>
                <P>• Animal production (NAICS code 112).</P>
                <P>• Food manufacturing (NAICS code 311).</P>
                <P>• Pesticide manufacturing (NAICS code 32532).</P>
                <P>
                    If you have any questions regarding the applicability of this action to a particular entity, consult the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     for the division listed at the end of the pesticide petition summary of interest.
                </P>
                <HD SOURCE="HD2">B. What should I consider as I prepare my comments for EPA?</HD>
                <P>
                    1. 
                    <E T="03">Submitting CBI.</E>
                     Do not submit this information to EPA through 
                    <E T="03">regulations.gov</E>
                     or email. Clearly mark the part or all of the information that you claim to be CBI. For CBI information in a disk or CD-ROM that you mail to EPA, mark the outside of the disk or CD-ROM as CBI and then identify electronically within the disk or CD-ROM the specific information that is claimed as CBI. In addition to one complete version of the comment that 
                    <PRTPAGE P="20844"/>
                    includes information claimed as CBI, a copy of the comment that does not contain the information claimed as CBI must be submitted for inclusion in the public docket. Information so marked will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.
                </P>
                <P>
                    2. 
                    <E T="03">Tips for preparing your comments.</E>
                     When preparing and submitting your comments, see the commenting tips at 
                    <E T="03">http://www.epa.gov/dockets/comments.html.</E>
                </P>
                <P>
                    3. 
                    <E T="03">Environmental justice.</E>
                     EPA seeks to achieve environmental justice, the fair treatment and meaningful involvement of any group, including minority and/or low-income populations, in the development, implementation, and enforcement of environmental laws, regulations, and policies. To help address potential environmental justice issues, the Agency seeks information on any groups or segments of the population who, as a result of their location, cultural practices, or other factors, may have atypical or disproportionately high and adverse human health impacts or environmental effects from exposure to the pesticides discussed in this document, compared to the general population.
                </P>
                <HD SOURCE="HD1">II. What action is the Agency taking?</HD>
                <P>EPA is announcing its receipt of several pesticide petitions filed under section 408 of the Federal Food, Drug, and Cosmetic Act (FFDCA), 21 U.S.C. 346a, requesting the establishment or modification of regulations in 40 CFR part 180 for residues of pesticide chemicals in or on various food commodities. The Agency is taking public comment on the requests before responding to the petitioners. EPA is not proposing any particular action at this time. EPA has determined that the pesticide petitions described in this document contain the data or information prescribed in FFDCA section 408(d)(2), 21 U.S.C. 346a(d)(2); however, EPA has not fully evaluated the sufficiency of the submitted data at this time or whether the data support granting of the pesticide petitions. After considering the public comments, EPA intends to evaluate whether and what action may be warranted. Additional data may be needed before EPA can make a final determination on these pesticide petitions.</P>
                <P>
                    Pursuant to 40 CFR 180.7(f), a summary of each of the petitions that are the subject of this document, prepared by the petitioner, is included in a docket EPA has created for each rulemaking. The docket for each of the petitions is available at 
                    <E T="03">http://www.regulations.gov</E>
                    .
                </P>
                <P>As specified in FFDCA section 408(d)(3), 21 U.S.C. 346a(d)(3), EPA is publishing notice of the petition so that the public has an opportunity to comment on this request for the establishment or modification of regulations for residues of pesticides in or on food commodities. Further information on the petition may be obtained through the petition summary referenced in this unit.</P>
                <HD SOURCE="HD3">New Tolerance Exemptions for Inerts (Except PIPS)</HD>
                <P>
                    <E T="03">PP</E>
                     IN-11136. (EPA-HQ-OPP-2019-0048). Monsanto Company (1300 I Street NW, Suite 450 East, Washington, DC 20005) requests to establish an exemption from the requirement of a tolerance for residues of formic acid (CAS Reg. No. 64-18-6) and sodium formate (CAS Reg. No. 141-53-7) when used as an inert ingredient in pesticide formulations applied to growing crops pre- and post-harvest under 40 CFR 180.910 for use as adjuvants or pH buffering agents. The petitioner believes no analytical method is needed because it is not required for an exemption from the requirement of a tolerance. Contact: RD.
                </P>
                <P>
                    <E T="03">PP</E>
                     IN-11242. (EPA-HQ-OPP-2018-0736). Arkema Inc. c/o Lewis &amp; Harrison, LLC, 2461 South Clark Street, Arlington, VA 22202, requests to establish an exemption from the requirement of a tolerance for residues of 2-propenoic acid, methyl ester, polymer with ethene and 2,5-furandione (CAS Reg. No. 88450-35-5), with a minimum number average molecular weight of 10,694 daltons, when used as an inert ingredient in pesticide formulations under 40 CFR 180.960. The petitioner believes no analytical method is needed because it is not required for an exemption from the requirement of a tolerance. Contact: RD
                </P>
                <P>
                    <E T="03">PP</E>
                     IN-11244. (EPA-HQ-OPP-2019-0099). Solvay USA Inc., c/o SciReg, Inc., 12733 Director's Loop, Woodbridge, VA 22192, requests to establish an exemption from the requirement of a tolerance for residues of 2-propenoic acid, ethyl ester, polymer, with sodium 2-methyl-2-[(1-oxo-2-propen-1-yl)amino]-1-propanesulfonate (1:1), oxidized (CAS Reg. No. 2230086-40-3) when used as a pesticide inert ingredient in pesticide formulations under 40 CFR 180.960. The petitioner believes no analytical method is needed because it is not required for an exemption from the requirement of a tolerance. Contact: RD.
                </P>
                <P>
                    <E T="03">PP</E>
                     IN-11247. (EPA-HQ-OPP-2019-0098). LNouvel, Inc., 4657 Courtyard Trail, Plano, TX 75024, requests to establish an exemption from the requirement of a tolerance for residues of tetraethyl orthosilicate (CAS Reg. No. 78-10-4) when used as a pesticide inert ingredient in pesticide formulations at a maximum of 50,000 parts per million (ppm) under 40 CFR 180.910 and 180.930. The petitioner believes no analytical method is needed because it is not required for an exemption from the requirement of a tolerance. Contact: RD.
                </P>
                <P>
                    <E T="03">PP</E>
                     IN-11248. (EPA-HQ-OPP-2019-0138). LNouvel, Inc., 4657 Courtyard Trail, Plano, TX 75024-2114, requests to establish an exemption from the requirement of a tolerance for residues of poly(oxy-1,2-ethanediyl), alpha-(3-(1,3,3,3-tetramethyl-1-((trimethylsilyl)oxy)disiloxanyl)propyl)-omega-hydroxy- (CAS Reg. No. 67674-67-3), when used as an inert ingredient in pesticide formulations under 40 CFR 180.930. The petitioner believes no analytical method is needed because it is not required for an exemption from the requirement of a tolerance. Contact: RD
                </P>
                <P>
                    <E T="03">PP</E>
                     IN-11251. (EPA-HQ-OPP-2019-0096). Keller and Heckman LLP, 1001 G Street, NW, Suite 500 West, Washington, DC 20001 on behalf of Kuraray Co. Ltd., requests to establish an exemption from the requirement of a tolerance for residues of acetic acid ethenyl ester, polymer with ethene and ethenol with a minimum number average molecular weight (in amu), 20,000 (CAS Reg. No. 26221-27-2) when used as a pesticide inert ingredient in pesticide formulations under 40 CFR 180.960. The petitioner believes no analytical method is needed because it is not required for an exemption from the requirement of a tolerance. Contact: RD.
                </P>
                <P>
                    <E T="03">PP</E>
                     IN-11254. (EPA-HQ-OPP-2019-0093). The Clariant Corporation, 4000 Monroe Road, Charlotte, NC, requests to amend an exemption from the requirement of a tolerance for residues of Alkyl Alcohol Alkoxylate (AAA) surfactants to include Oxirane, 2-methyl-, polymer with oxirane, mono undecyl ether branched and linear (CAS Reg. No. 2222805-23-2) when used as a pesticide inert ingredient in pesticide formulations under 40 CFR 180.910, 180.930, 180.940 and 180.960. The petitioner believes no analytical method is needed because it is not required for an exemption from the requirement of a tolerance. Contact: RD.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>21 U.S.C. 346a.</P>
                </AUTH>
                <SIG>
                    <PRTPAGE P="20845"/>
                    <DATED>Dated: April 16, 2019.</DATED>
                    <NAME>Michael Goodis,</NAME>
                    <TITLE>Director, Registration Division, Office of Pesticide Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09776 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>84</VOL>
    <NO>92</NO>
    <DATE>Monday, May 13, 2019</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="20846"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <DATE>May 8, 2019.</DATE>
                <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 June 12, 2019 will be considered. Written comments should be addressed to: Desk Officer for Agriculture, Office of Information and Regulatory Affairs, Office of Management and Budget (OMB), New Executive Office Building, 725 17th Street NW, Washington, DC 20502. Commenters are encouraged to submit their comments to OMB via email to: 
                    <E T="03">OIRA_Submission@OMB.EOP.GOV</E>
                     or fax (202) 395-5806 and to Departmental Clearance Office, USDA, OCIO, Mail Stop 7602, Washington, DC 20250-7602. Copies of the submission(s) may be obtained by calling (202) 720-8958.
                </P>
                <P>An agency may not conduct or sponsor a collection of information unless the collection of information displays a currently valid OMB control number and the agency informs potential persons who are to respond to the collection of information that such persons are not required to respond to the collection of information unless it displays a currently valid OMB control number.</P>
                <HD SOURCE="HD1">Animal and Plant Health Inspection Service</HD>
                <P>
                    <E T="03">Title:</E>
                     Location of Irradiation Treatment Facilities in the United States.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0579-0383.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                     The United States Department of Agriculture (USDA) is responsible for preventing plant diseases or insect pests from entering into the United States, preventing the spread of pests and noxious weeds not widely distributed into the United States, and eradicating those imported pests when eradication is feasible. The Plant Protection Act (7 U.S.C. 7701—
                    <E T="03">et seq.</E>
                    ) authorizes USDA to carry out this mission. Under the Plant Protection Act, the Animal and Plant Health Inspection Service (APHIS) is authorized, among other things, to regulate the importation of plants, plant products, and other articles to prevent the introduction of plant pests in the United States.
                </P>
                <P>
                    <E T="03">Need and Use of the Information:</E>
                     APHIS will use the following information collection activities to provide criteria for the approval/certification of irradiation treatment facilities in an effort to prevent the introduction or spread of plant pests and plant diseases in the United States: Request for Initial Certification and Inspection of Facility; Certification and Recertification of Facility; Denial and Withdrawal of Certification; Compliance Agreement; Irradiation Facilities Treating Imported Articles; Irradiation Treatment Framework Equivalency Work plan; Irradiation Facilities Notification; Recordkeeping; Facility to Maintain and Provide Updated Map Identifying Places Horticultural/Crops are Grown; Facility Contingency Plan; Letter of Concurrence or Non-Agreement; Treatment Arrangements; Pest Management Plan; and Facility Map—Detailed Layout of Facility. If the information is not collected, APHIS would have no practical way of determining that any given commodity had actually been irradiated.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Business or other for-profits; Federal Government; State, Local or Tribal Government.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     24.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Reporting: On occasion.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     988.
                </P>
                <SIG>
                    <NAME>Ruth Brown,</NAME>
                    <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09758 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3410-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Agenda and Notice of Public Meeting of the New Jersey Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Announcement of 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 (FACA), that a planning meeting of the New Jersey Advisory Committee to the Commission will convene by conference call, on Friday, May 17, 2019 at 11:30 a.m. (EDT). The purpose of the meeting is to announce the selection of the topic of the Committee's civil rights project, identify the members appointed to the Planning Workgroup and to discuss plans for the Briefing Meeting.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Friday, May 17, 2019, at 11:30 a.m. (EDT).</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Public Call-In Information: Conference call number: 1-888-394-8218 and conference call ID number: 6970676.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ivy L. Davis, at 
                        <E T="03">ero@usccr.gov</E>
                         or by phone at 202-376-7533.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Interested members of the public may listen to the discussion by calling the following toll-free conference call number: 1-888-394-8218 and conference call ID number: 6970676. Please be advised that before placing them into the conference call, the conference call operator may ask callers to provide their names, their organizational affiliations (if any), and email addresses (so that callers may be notified of future meetings). Callers can expect to incur charges for calls they initiate over wireless lines, and the Commission will not refund any incurred charges. Callers will incur no 
                    <PRTPAGE P="20847"/>
                    charge for calls they initiate over land-line connections to the toll-free telephone number herein.
                </P>
                <P>Persons with hearing impairments may also follow the discussion by first calling the Federal Relay Service at 1-800-877-8339 and providing the operator with the toll-free conference call number: 1-888-394-8218 and conference call ID number: 6970676.</P>
                <P>
                    Members of the public are invited to make statements during the Public Comment section of the meeting or to submit written comments. The comments must be received in the regional office approximately 30 days after each scheduled meeting. Written comments may be mailed to the Eastern Regional Office, U.S. Commission on Civil Rights, 1331 Pennsylvania Avenue, Suite 1150, Washington, DC 20425, or emailed to Evelyn Bohor at 
                    <E T="03">ero@usccr.gov.</E>
                     Persons who desire additional information may contact the Eastern Regional Office at (202) 376-7533.
                </P>
                <P>
                    Records and documents discussed during the meeting will be available for public viewing as they become available at: 
                    <E T="03">https://gsageo.force.com/FACA/FACAPublicViewCommitteeDetails?id=a10t0000001gzjVAAQ</E>
                    ; click the “Meeting Details” and “Documents” links. Records generated from this meeting may also be inspected and reproduced at the Eastern Regional Office, as they become available, both before and after the meetings. Persons interested in the work of this advisory committee are advised to go to the Commission's website, 
                    <E T="03">www.usccr.gov,</E>
                     or to contact the Eastern Regional Office at the above phone number, email or street address.
                </P>
                <HD SOURCE="HD1">Agenda: Friday, May 17, 2019 at 11:30 a.m. (EDT)</HD>
                <FP SOURCE="FP-2">I. Welcome and Roll Call</FP>
                <FP SOURCE="FP-2">II. Planning Meeting</FP>
                <FP SOURCE="FP1-2">—Announce Committee Selection of Civil Rights Project</FP>
                <FP SOURCE="FP1-2">—Identify members Appointed to the Planning Workgroup</FP>
                <FP SOURCE="FP1-2">—Discuss Plans for the Briefing Meeting</FP>
                <FP SOURCE="FP-2">III. Other Business</FP>
                <FP SOURCE="FP-2">IV. Next Meeting</FP>
                <FP SOURCE="FP-2">V. Public Comment</FP>
                <FP SOURCE="FP-2">VI. Adjourn</FP>
                <P>
                    <E T="03">Exceptional Circumstance:</E>
                     Pursuant to 41 CFR 102-3.150, the notice for this meeting is given less than 15 calendar days prior to the meeting because of the exceptional circumstances of the federal government shutdown.
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>David Mussatt,</NAME>
                    <TITLE>Supervisory Chief, Regional Programs Unit.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09749 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Agenda and Notice of Public Meeting of the Delaware Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Announcement of 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 (FACA), that a planning meeting of the Delaware Advisory Committee to the Commission will convene by conference call, on Monday, May 20, 2019 at 4:00 p.m. (EDT). The purpose of the meeting is to discuss and vote on the Committee's report on implicit bias and policing in communities of color in Delaware.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Monday, May 20, 2019 at 4:00 p.m. (EDT).</P>
                    <P>
                        <E T="03">Public Call-In Information:</E>
                         Conference call number: 1-888-254-3590 and conference call ID: 4124362.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ivy L. Davis, at 
                        <E T="03">ero@usccr.gov</E>
                         or by phone at 202-376-7533
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Interested members of the public may listen to the discussion by calling the following toll-free conference call number: 1-888-254-3590 and conference call ID: 4124362. Please be advised that before placing them into the conference call, the conference call operator may ask callers to provide their names, their organizational affiliations (if any), and email addresses (so that callers may be notified of future meetings). Callers can expect to incur charges for calls they initiate over wireless lines, and 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 herein.</P>
                <P>Persons with hearing impairments may also follow the discussion by first calling the Federal Relay Service at 1-800-877-8339 and providing the operator with the toll-free conference call number:1-888-254-3590 and conference call ID: 4124362.</P>
                <P>
                    Members of the public are invited make statements during the Public Comment section of the meeting or to submit written comments; the written comments must be received in the regional office approximately 30 days after each scheduled meeting. Written comments may be mailed to the Eastern Regional Office, U.S. Commission on Civil Rights, 1331 Pennsylvania Avenue, Suite 1150, Washington, DC 20425 or emailed to Evelyn Bohor at 
                    <E T="03">ero@usccr.gov.</E>
                     Persons who desire additional information may contact the Eastern Regional Office at (202) 376-7533.
                </P>
                <P>
                    Records and documents discussed during the meeting will be available for public viewing as they become available at: 
                    <E T="03">https://gsageo.force.com/FACA/FACAPublicViewCommitteeDetails?id=a10t0000001gzlEAAQ</E>
                     click the “Meeting Details” and “Documents” links. Records generated from this meeting may also be inspected and reproduced at the Eastern Regional Office, as they become available, both before and after the meetings. Persons interested in the work of this advisory committee are advised to go to the Commission's website, 
                    <E T="03">www.usccr.gov,</E>
                     or to contact the Eastern Regional Office at the above phone number, email or street address.
                </P>
                <HD SOURCE="HD1">Agenda: Monday, May 20, 2019 at 4:00 p.m. (EDT)</HD>
                <FP SOURCE="FP-2">I. Welcome and Roll Call</FP>
                <FP SOURCE="FP-2">II. Project Planning</FP>
                <FP SOURCE="FP1-2">—Discuss and Vote on Draft Report</FP>
                <FP SOURCE="FP-2">III. Other Business</FP>
                <FP SOURCE="FP-2">IV. Public Comment</FP>
                <FP SOURCE="FP-2">V. Next Meeting</FP>
                <FP SOURCE="FP-2">VI. Adjourn</FP>
                <P>
                    <E T="03">Exceptional Circumstance:</E>
                     Pursuant to 41 CFR 102-3.150, the notice for this meeting is given less than 15 calendar days prior to the meeting because of the exceptional circumstances of the federal government shutdown.
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>David Mussatt,</NAME>
                    <TITLE>Supervisory Chief, Regional Programs Unit.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09744 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">COMMISSION ON CIVIL RIGHTS</AGENCY>
                <SUBJECT>Agenda and Notice of Public Meeting of the District of Columbia Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Commission on Civil Rights.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Announcement of 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 (FACA), that a meeting of the District of Columbia Advisory Committee to the Commission will convene by conference 
                        <PRTPAGE P="20848"/>
                        call, at 12:00 p.m. (EDT) Thursday, June 6, 2019. The purpose of the planning meeting is to continue project planning for a future briefing meeting on the Committee's civil rights project that examines the intersection of homelessness, mental health and the criminal justice system, including a review of the DC Mental Health Court.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Thursday, June 6, 2019 at 12:00 p.m. (EDT).</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Public Call-In Information: Conference call number: 1-877-260-1479 and conference call ID number: 1929821.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ivy L. Davis, at 
                        <E T="03">ero@usccr.gov</E>
                         or by phone at 202-376-7533.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Interested members of the public may listen to the discussion by calling the following toll-free conference call number: 1-877-260-1479 and conference call ID number: 1929821. Please be advised that before placing them into the conference call, the conference call operator may ask callers to provide their names, their organizational affiliations (if any), and email addresses (so that callers may be notified of future meetings). Callers can expect to incur charges for calls they initiate over wireless lines, and 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 herein.</P>
                <P>Persons with hearing impairments may also follow the discussion by first calling the Federal Relay Service at 1-800-877-8339 and providing the operator with the toll-free conference call number: 1-877-260-1479 and conference call ID number: 1929821.</P>
                <P>
                    Members of the public are invited to make statements during the Public Comments section of the meeting or to submit written comments. The comments must be received in the regional office by Monday, July 8, 2019. Comments may be mailed to the Eastern Regional Office, U.S. Commission on Civil Rights, 1331 Pennsylvania Avenue, Suite 1150, Washington, DC 20425 or emailed to Evelyn Bohor at 
                    <E T="03">ero@usccr.gov.</E>
                     Persons who desire additional information may contact the Eastern Regional Office at 202-376-7533.
                </P>
                <P>
                    Records and documents discussed during the meeting will be available for public viewing as they become available at: 
                    <E T="03">https://gsageo.force.com/FACA/FACAPublicViewCommitteeDetails?id=a10t0000001gzlKAAQ.</E>
                     Please click the “Meeting Details” and “Documents” links. Records generated from this meeting may also be inspected and reproduced at the Eastern Regional Office, as they become available, both before and after the meeting. Persons interested in the work of this advisory committee are advised to go to the Commission's website, 
                    <E T="03">www.usccr.gov,</E>
                     or to contact the Eastern Regional Office at the above phone numbers, email or street address.
                </P>
                <HD SOURCE="HD1">Agenda</HD>
                <HD SOURCE="HD2">Thursday, June 6, 2019, at 12:00 p.m. (EDT)</HD>
                <FP SOURCE="FP-2">I. Welcome and Rollcall</FP>
                <FP SOURCE="FP-2">II. Discuss Project and Hearing Planning</FP>
                <FP SOURCE="FP-2">III. Other Business</FP>
                <FP SOURCE="FP-2">IV. Next Planning Meeting</FP>
                <FP SOURCE="FP-2">V. Public Comments</FP>
                <FP SOURCE="FP-2">VI. Adjourn</FP>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>David Mussatt,</NAME>
                    <TITLE>Supervisory Chief, Regional Programs Unit.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09746 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Census Bureau</SUBAGY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <P>The Department of Commerce will submit to the Office of Management and Budget (OMB) for clearance the following proposal for collection of information under the provisions of the Paperwork Reduction Act.</P>
                <P>
                    <E T="03">Agency:</E>
                     U.S. Census Bureau.
                </P>
                <P>
                    <E T="03">Title:</E>
                     American Community Survey Methods Panel Tests, 2019 Due Dates Test.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0607-0936.
                </P>
                <P>
                    <E T="03">Form Number(s):</E>
                     ACS-1, ACS internet.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Non-substantive Change Request.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     144,000.
                </P>
                <P>
                    <E T="03">Average Hours per Response:</E>
                     40 minutes.
                </P>
                <P>
                    <E T="03">Burden Hours:</E>
                     No additional burden hours are requested under this non-substantive change request.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     The American Community Survey (ACS) collects detailed socioeconomic data from about 3.5 million housing units in the United States and 36,000 in Puerto Rico each year. The ACS also collects detailed socioeconomic data from about 195,000 residents living in Group Quarter (GQ) facilities. An ongoing data collection effort with an annual sample of this magnitude requires that the ACS continue research, testing, and evaluations aimed at reducing respondent burden, improving data quality, achieving survey cost efficiencies, and improving ACS questionnaire content and related data collection materials. The ACS Methods Panel is a research program designed to address and respond to issues and survey needs.
                </P>
                <P>Residents of sampled housing units are invited to self-respond to the ACS through a series of up to five mailings. These mailings are sent to respondents over approximately six and a half weeks. Research has shown that when a request has a sense of urgency, people are more likely to comply with the request (Kotter, 2008; Gunelius, 2009). One way of creating a sense of urgency is through deadline or due date messaging. The current ACS mailings contain implied due date messages, such as “. . . please complete the survey online as soon as possible” or “If you have not already responded, please do so now” but do not provide an explicit due date. The purpose of this test is to assess the effect on self-response of an explicit due date message in the fifth mailing.</P>
                <P>Six experimental treatments are proposed. One treatment will serve as the control and will not contain an explicit due date. The other treatments will vary the use and placement of a due date.</P>
                <P>This test will study the impact on self-response and cost of including a due date in the fifth mailing. To field this test, the Census Bureau plans to use the ACS production sample (clearance number: 0607-0810, expires 06/30/2020). Thus, there is no increase in burden from this test since each treatment will result in the same burden estimate per interview (40 minutes). The Census Bureau proposes to test the use of due date messages as part of the ACS September or October 2019 panel, adhering to the same data collection protocols as production ACS.</P>
                <P>
                    The ACS sample design consists of randomly assigning each monthly sample panel into 24 groups of approximately 12,000 addresses each. Each group, called a methods panel group, within a monthly sample is representative of the full monthly sample. Each monthly sample is a representative subsample of the entire annual sample and is representative of the sampling frame. The Census Bureau proposes to use two randomly selected methods panel groups for each treatment. Hence, each treatment will have a sample size of approximately 24,000 addresses. In total, approximately 144,000 addresses will be used for the six experimental treatments. The remaining sample will receive production materials.
                    <PRTPAGE P="20849"/>
                </P>
                <P>The Census Bureau proposes to evaluate treatment comparisons by comparing self-response rates. For each comparison a two-tailed test will be used so that the Census Bureau can measure the impact on the evaluation measure in either direction with 80 percent power, at the α = 0.1 level. The sample size will be able to detect differences of approximately 1.74 percentage points between the self-response return rates between two experimental treatments. Additionally, a cost analysis will also be conducted.</P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or households.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     One-time test as part of the monthly American Community Survey.
                </P>
                <P>
                    <E T="03">Respondent's Obligation:</E>
                     Mandatory.
                </P>
                <P>
                    <E T="03">Legal Authority:</E>
                     Title 13, United States Code, Sections 141, 193, and 221.
                </P>
                <P>
                    This information collection request may be viewed at 
                    <E T="03">www.reginfo.gov</E>
                    . Follow the instructions to view Department of Commerce collections currently under review by OMB.
                </P>
                <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">OIRA_Submission@omb.eop.gov</E>
                     or fax to (202) 395-5806.
                </P>
                <SIG>
                    <NAME>Sheleen Dumas,</NAME>
                    <TITLE>Departmental Lead PRA Officer, Office of the Chief Information Officer, Commerce Department.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09767 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-07-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Economic Analysis</SUBAGY>
                <DEPDOC>[Docket No. 1903292999-9299-01]</DEPDOC>
                <RIN>RIN 0691-XC090</RIN>
                <SUBJECT>BE-9: Quarterly Survey of Foreign Airline Operators' Revenues and Expenses in the United States</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Economic Analysis, Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of reporting requirements.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>By this Notice, the Bureau of Economic Analysis (BEA), Department of Commerce, is informing the public that it is conducting the mandatory survey titled Quarterly Survey of Foreign Airline Operators' Revenues and Expenses in the United States (BE-9). The data collected on the BE-9 survey are needed to measure U.S. trade in transport services and to analyze the impact of U.S. trade on the U.S. and foreign economies. This survey is authorized by the International Investment and Trade in Services Survey Act.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Christopher Stein, Chief, Services Surveys Branch (BE-50), Balance of Payments Division, Bureau of Economic Analysis, U.S. Department of Commerce, 4600 Silver Hill Road, Washington, DC 20233; phone (301) 278-9189; or via email at 
                        <E T="03">Christopher.Stein@bea.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Through this Notice, BEA publishes the reporting requirements for the BE-9 survey form. As noted below, all entities required to respond to this mandatory survey will be contacted by BEA. Entities must submit the completed survey forms within 45 days after the end of each calendar quarter. This Notice is being issued in conformance with the rule BEA issued on April 24, 2012 (77 FR 24373), establishing guidelines for collecting data on international trade in services and direct investment through notices, rather than through rulemaking. Additional information about BEA's collection of data on international trade in services and direct investment can be found in the 2012 rule, the International Investment and Trade in Services Survey Act (22 U.S.C. 3101 
                    <E T="03">et seq.</E>
                    ), and 15 CFR part 801. Survey data on international trade in services and direct investment that are not collected pursuant to the 2012 rule are described separately in 15 CFR part 801. The BE-9 survey form and instructions are available at 
                    <E T="03">www.bea.gov/ssb.</E>
                </P>
                <HD SOURCE="HD1">Reporting</HD>
                <P>Notice of specific reporting requirements, including who is to report, the information to be reported, the manner of reporting, and the time and place of filing reports, will be mailed to those required to complete this survey.</P>
                <P>
                    <E T="03">Who Must Report:</E>
                     (a) Reports are required from U.S. offices, agents, or other representatives of foreign airline operators that had total reportable revenues or total reportable expenses that were $5 million or more during the prior year, or are expected to be $5 million or more during the current year.
                </P>
                <P>(b) Entities required to report will be contacted individually by BEA. Entities not contacted by BEA have no reporting responsibilities.</P>
                <P>
                    <E T="03">What To Report:</E>
                     The survey collects information on foreign airline operators' revenues and expenses in the United States.
                </P>
                <P>
                    <E T="03">How To Report:</E>
                     Reports can be filed using BEA's electronic reporting system at 
                    <E T="03">www.bea.gov/efile.</E>
                     Copies of the survey forms and instructions, which contain complete information on reporting procedures and definitions, can be downloaded from 
                    <E T="03">www.bea.gov/ssb</E>
                     and submitted through mail or fax. Form BE-9 inquiries can be made by phone to BEA at (301) 278-9303 or by sending an email to 
                    <E T="03">be-9help@bea.gov.</E>
                </P>
                <P>
                    <E T="03">When To Report:</E>
                     Reports are due to BEA 45 days after the end of each calendar quarter.
                </P>
                <HD SOURCE="HD1">Paperwork Reduction Act Notice</HD>
                <P>
                    This data collection has been approved by the Office of Management and Budget (OMB) in accordance with the Paperwork Reduction Act and assigned control number 0608-0068. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid control number assigned by OMB. Public reporting burden for this collection of information is estimated to average 6 hours per response. Additional information regarding this burden estimate may be viewed at 
                    <E T="03">www.reginfo.gov;</E>
                     under the Information Collection Review tab, click on “Search” and use the above OMB control number to search for the current survey instrument. Send comments regarding this burden estimate to Director, Bureau of Economic Analysis (BE-1), U.S. Department of Commerce, 4600 Silver Hill Rd., Washington, DC 20233; and to the Office of Management and Budget, Paperwork Reduction Project 0608-0068, 725 17th Street NW, Washington, DC 20503, or via email at 
                    <E T="03">OIRA_Submission@omb.eop.gov.</E>
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>22 U.S.C. 3101-3108.</P>
                </AUTH>
                <SIG>
                    <NAME>Paul W. Farello,</NAME>
                    <TITLE>Associate Director for International Economics, Bureau of Economic Analysis.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09790 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3510-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Economic Analysis</SUBAGY>
                <DEPDOC>[Docket No. 190329314-9314-01]</DEPDOC>
                <RIN>RIN 0691-XC099</RIN>
                <SUBJECT>BE-577: Quarterly Survey of U.S. Direct Investment Abroad—Transactions of U.S. Reporter With Foreign Affiliate</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Economic Analysis, Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of reporting requirements.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        By this Notice, the Bureau of Economic Analysis (BEA), Department of Commerce, is informing the public 
                        <PRTPAGE P="20850"/>
                        that it is conducting the mandatory survey titled Quarterly Survey of U.S. Direct Investment Abroad—Transactions of U.S. Reporter with Foreign Affiliate (BE-577). The data collected on the BE-577 survey are needed to measure the size and economic significance of U.S. direct investment abroad and its impact on the U.S. and foreign economies. This survey is authorized by the International Investment and Trade in Services Survey Act.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jessica Hanson, Chief, Direct Transactions and Positions Branch (BE-49), Bureau of Economic Analysis, U.S. Department of Commerce, 4600 Silver Hill Road, Washington, DC 20233; phone (301) 278-9595; or via email at 
                        <E T="03">Jessica.Hanson@bea.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Through this Notice, BEA publishes the reporting requirements for the BE-577 survey form. As noted below, all entities required to respond to this mandatory survey will be contacted by BEA. Entities must submit the completed survey forms within 30 days after the end of each calendar or fiscal quarter, or within 45 days if the report is for the final quarter of the financial reporting year. This Notice is being issued in conformance with the rule BEA issued on April 24, 2012 (77 FR 24373), establishing guidelines for collecting data on international trade in services and direct investment through notices, rather than through rulemaking. Additional information about BEA's collection of data on international trade in services and direct investment can be found in the 2012 rule, the International Investment and Trade in Services Survey Act (22 U.S.C. 3101 
                    <E T="03">et seq.</E>
                    ), and 15 CFR part 801. Survey data on international trade in services and direct investment that are not collected pursuant to the 2012 rule are described separately in 15 CFR part 801. The BE-577 survey forms and instructions are available at 
                    <E T="03">www.bea.gov/dia.</E>
                </P>
                <HD SOURCE="HD1">Reporting</HD>
                <P>Notice of specific reporting requirements, including who is to report, the information to be reported, the manner of reporting, and the time and place of filing reports, will be mailed to those required to complete this survey.</P>
                <P>
                    <E T="03">Who Must Report:</E>
                     (a) Reports are required from each U.S. person that has a direct and/or indirect ownership interest of at least 10 percent of the voting stock in an incorporated foreign business enterprise, or an equivalent interest in an unincorporated foreign business enterprise, and that meets the additional conditions detailed in Form BE-577.
                </P>
                <P>(b) Entities required to report will be contacted individually by BEA. Entities not contacted by BEA have no reporting responsibilities.</P>
                <P>
                    <E T="03">What To Report:</E>
                     The survey collects information on transactions between parent companies and their affiliates and on direct investment positions (stocks).
                </P>
                <P>
                    <E T="03">How To Report:</E>
                     Reports can be filed using BEA's electronic reporting system at 
                    <E T="03">www.bea.gov/efile.</E>
                     Copies of the survey form and instructions, which contain complete information on reporting procedures and definitions, can be downloaded from 
                    <E T="03">www.bea.gov/dia</E>
                     and submitted through mail or fax. Form BE-577 inquiries can be made by phone to BEA at (301) 278-9261 or by sending an email to 
                    <E T="03">be577@bea.gov.</E>
                </P>
                <P>
                    <E T="03">When To Report:</E>
                     Reports are due to BEA 30 days after the close of each calendar or fiscal quarter, or 45 days if the report is for the final quarter of the financial reporting year.
                </P>
                <HD SOURCE="HD1">Paperwork Reduction Act Notice</HD>
                <P>
                    This data collection has been approved by the Office of Management and Budget (OMB) in accordance with the Paperwork Reduction Act and assigned control number 0608-0004. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid control number assigned by OMB. Public reporting burden for this collection of information is estimated to average 1 hour per response. Additional information regarding this burden estimate may be viewed at 
                    <E T="03">www.reginfo.gov;</E>
                     under the Information Collection Review tab, click on “Search” and use the above OMB control number to search for the current survey instrument. Send comments regarding this burden estimate to Director, Bureau of Economic Analysis (BE-1), U.S. Department of Commerce, 4600 Silver Hill Rd., Washington, DC 20233; and to the Office of Management and Budget, Paperwork Reduction Project 0608-0004, 725 17th Street NW, Washington, DC 20503, or via email at 
                    <E T="03">OIRA_Submission@omb.eop.gov.</E>
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>22 U.S.C. 3101-3108.</P>
                </AUTH>
                <SIG>
                    <NAME>Paul W. Farello,</NAME>
                    <TITLE>Associate Director for International Economics, Bureau of Economic Analysis.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09809 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3510-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Economic Analysis</SUBAGY>
                <DEPDOC>[Docket No. 190329307-9307-01]</DEPDOC>
                <RIN>RIN 0691-XC094</RIN>
                <SUBJECT>BE-30: Quarterly Survey of Ocean Freight Revenues and Foreign Expenses of U.S. Carriers</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Economic Analysis, Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of reporting requirements.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>By this Notice, the Bureau of Economic Analysis (BEA), Department of Commerce, is informing the public that it is conducting the mandatory survey titled Quarterly Survey of Ocean Freight Revenues and Foreign Expenses of U.S. Carriers (BE-30). The data collected on the BE-30 survey are needed to measure U.S. trade in transport services and to analyze the impact of U.S. trade on the U.S. and foreign economies. This survey is authorized by the International Investment and Trade in Services Survey Act.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Christopher Stein, Chief, Services Surveys Branch (BE-50), Balance of Payments Division, Bureau of Economic Analysis, U.S. Department of Commerce, 4600 Silver Hill Road, Washington, DC 20233; phone (301) 278-9189; or via email at 
                        <E T="03">Christopher.Stein@bea.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Through this Notice, BEA publishes the reporting requirements for the BE-30 survey form. As noted below, all entities required to respond to this mandatory survey will be contacted by BEA. Entities must submit the completed survey forms within 45 days after the end of each calendar quarter. This Notice is being issued in conformance with the rule BEA issued on April 24, 2012 (77 FR 24373), establishing guidelines for collecting data on international trade in services and direct investment through notices, rather than through rulemaking. Additional information about BEA's collection of data on international trade in services and direct investment can be found in the 2012 rule, the International Investment and Trade in Services Survey Act (22 U.S.C. 3101 
                    <E T="03">et seq.</E>
                    ), and 15 CFR part 801. Survey data on international trade in services and direct investment that are not collected pursuant to the 2012 rule are described separately in 15 CFR part 801. The BE-30 survey form and instructions are available at 
                    <E T="03">www.bea.gov/ssb.</E>
                    <PRTPAGE P="20851"/>
                </P>
                <HD SOURCE="HD1">Reporting</HD>
                <P>Notice of specific reporting requirements, including who is to report, the information to be reported, the manner of reporting, and the time and place of filing reports, will be mailed to those required to complete this survey.</P>
                <P>
                    <E T="03">Who Must Report:</E>
                     (a) Reports are required from U.S. ocean carriers that had total reportable revenues or total reportable expenses that were $500,000 or more during the prior year, or are expected to be $500,000 or more during the current year.
                </P>
                <P>(b) Entities required to report will be contacted individually by BEA. Entities not contacted by BEA have no reporting responsibilities.</P>
                <P>
                    <E T="03">What To Report:</E>
                     The survey collects information on U.S. ocean freight carriers' foreign revenues and expenses.
                </P>
                <P>
                    <E T="03">How To Report:</E>
                     Reports can be filed using BEA's electronic reporting system at 
                    <E T="03">www.bea.gov/efile.</E>
                     Copies of the survey forms and instructions, which contain complete information on reporting procedures and definitions, can be downloaded from 
                    <E T="03">www.bea.gov/ssb</E>
                     and submitted through mail or fax. Form BE-30 inquiries can be made by phone to BEA at (301) 278-9303 or by sending an email to 
                    <E T="03">be-30help@bea.gov.</E>
                </P>
                <P>
                    <E T="03">When To Report:</E>
                     Reports are due to BEA 45 days after the end of each calendar quarter.
                </P>
                <HD SOURCE="HD1">Paperwork Reduction Act Notice</HD>
                <P>
                    This data collection has been approved by the Office of Management and Budget (OMB) in accordance with the Paperwork Reduction Act and assigned control number 0608-0011. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid control number assigned by OMB. Public reporting burden for this collection of information is estimated to average 4 hours per response. Additional information regarding this burden estimate may be viewed at 
                    <E T="03">www.reginfo.gov;</E>
                     under the Information Collection Review tab, click on “Search” and use the above OMB control number to search for the current survey instrument. Send comments regarding this burden estimate to Director, Bureau of Economic Analysis (BE-1), U.S. Department of Commerce, 4600 Silver Hill Rd., Washington, DC 20233; and to the Office of Management and Budget, Paperwork Reduction Project 0608-0011, 725 17th Street NW, Washington, DC 20503, or via email at 
                    <E T="03">OIRA_Submission@omb.eop.gov.</E>
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>22 U.S.C. 3101-3108.</P>
                </AUTH>
                <SIG>
                    <NAME>Paul W. Farello,</NAME>
                    <TITLE>Associate Director for International Economics, Bureau of Economic Analysis.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09796 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3510-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Economic Analysis</SUBAGY>
                <DEPDOC>[Docket No. 190329300-9300-01]</DEPDOC>
                <RIN>RIN 0691-XC091</RIN>
                <SUBJECT>BE-11: Annual Survey of U.S. Direct Investment Abroad</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Economic Analysis, Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of reporting requirements.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>By this Notice, the Bureau of Economic Analysis (BEA), Department of Commerce, is informing the public that it is conducting the mandatory survey titled Annual Survey of U.S. Direct Investment Abroad (BE-11). The data collected on the BE-11 survey are needed to measure the size and economic significance of U.S. direct investment abroad and its impact on the U.S. and foreign economies. This survey is authorized by the International Investment and Trade in Services Survey Act.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ricardo Limés, Chief, Multinational Operations Branch (BE-49), Bureau of Economic Analysis, U.S. Department of Commerce, 4600 Silver Hill Road, Washington, DC 20233; phone (301) 278-9659; or via email at 
                        <E T="03">Ricardo.Limes@bea.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Through this Notice, BEA publishes the reporting requirements for the BE-11 survey form. As noted below, all entities required to respond to this mandatory survey will be contacted by BEA. A completed report covering the entity's fiscal year ending during the previous calendar year is due by May 31, 2019. This Notice is being issued in conformance with the rule BEA issued on April 24, 2012 (77 FR 24373), establishing guidelines for collecting data on international trade in services and direct investment through notices, rather than through rulemaking. Additional information about BEA's collection of data on international trade in services and direct investment can be found in the 2012 rule, the International Investment and Trade in Services Survey Act (22 U.S.C. 3101 
                    <E T="03">et seq.</E>
                    ), and 15 CFR part 801. Survey data on international trade in services and direct investment that are not collected pursuant to the 2012 rule are described separately in 15 CFR part 801. The BE-11 survey forms and instructions are available at 
                    <E T="03">www.bea.gov/dia.</E>
                </P>
                <HD SOURCE="HD1">Reporting</HD>
                <P>Notice of specific reporting requirements, including who is to report, the information to be reported, the manner of reporting, and the time and place of filing reports, will be mailed to those required to complete this survey.</P>
                <P>
                    <E T="03">Who Must Report:</E>
                     (a) Reports are required from each U.S. person that has a direct and/or indirect ownership interest of at least 10 percent of the voting stock in an incorporated foreign business enterprise, or an equivalent interest in an unincorporated foreign business enterprise, and that meets the additional conditions detailed in Form BE-11.
                </P>
                <P>(b) Entities required to report will be contacted individually by BEA. Entities not contacted by BEA have no reporting responsibilities.</P>
                <P>
                    <E T="03">What To Report:</E>
                     The survey collects information on the operations of U.S. parent companies and their foreign affiliates.
                </P>
                <P>
                    <E T="03">How To Report:</E>
                     Reports can be filed using BEA's electronic reporting system at 
                    <E T="03">www.bea.gov/efile.</E>
                     Copies of the survey forms and instructions, which contain complete information on reporting procedures and definitions, can be downloaded from 
                    <E T="03">www.bea.gov/dia</E>
                     and submitted through mail or fax. Form BE-11 inquiries can be made by phone to BEA at (301) 278-9418 or by sending an email to 
                    <E T="03">be10/11@bea.gov.</E>
                </P>
                <P>
                    <E T="03">When To Report:</E>
                     A completed report covering an entity's fiscal year ending during the previous calendar year is due by May 31, 2019.
                </P>
                <HD SOURCE="HD1">Paperwork Reduction Act Notice</HD>
                <P>
                    This data collection has been approved by the Office of Management and Budget (OMB) in accordance with the Paperwork Reduction Act and assigned control number 0608-0053. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid control number assigned by OMB. A complete response includes one BE-11A form (with an estimated average reporting burden of 7 hours) for reporting domestic operations and one or more BE-11B (12 hours), BE-11C (2 hours), or BE-10D (1 hour) forms for reporting foreign operations. Public reporting burden for this collection of information is estimated to average a total of 103.4 hours per complete response. Additional 
                    <PRTPAGE P="20852"/>
                    information regarding this burden estimate may be viewed at 
                    <E T="03">www.reginfo.gov;</E>
                     under the Information Collection Review tab, click on “Search” and use the above OMB control number to search for the current survey instrument. Send comments regarding this burden estimate to Director, Bureau of Economic Analysis (BE-1), U.S. Department of Commerce, 4600 Silver Hill Rd., Washington, DC 20233; and to the Office of Management and Budget, Paperwork Reduction Project 0608-0053, 725 17th Street NW, Washington, DC 20503, or via email at 
                    <E T="03">OIRA_Submission@omb.eop.gov.</E>
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>22 U.S.C. 3101-3108.</P>
                </AUTH>
                <SIG>
                    <NAME>Paul W. Farello,</NAME>
                    <TITLE>Associate Director for International Economics, Bureau of Economic Analysis.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09792 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3510-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Economic Analysis</SUBAGY>
                <DEPDOC>[Docket No. 190329312-9312-01]</DEPDOC>
                <RIN>RIN 0691-XC098</RIN>
                <SUBJECT>BE-185: Quarterly Survey of Financial Services Transactions Between U.S. Financial Services Providers and Foreign Persons</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Economic Analysis, Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of reporting requirements.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>By this Notice, the Bureau of Economic Analysis (BEA), Department of Commerce, is informing the public that it is conducting the mandatory survey titled Quarterly Survey of Financial Services Transactions between U.S. Financial Services Providers and Foreign Persons (BE-185). The data collected on the BE-185 survey are needed to measure U.S. trade in financial services and to analyze the impact of U.S. trade on the U.S. and foreign economies. This survey is authorized by the International Investment and Trade in Services Survey Act and by Section 5408 of the Omnibus Trade and Competitiveness Act of 1988.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Christopher Stein, Chief, Services Surveys Branch (BE-50), Balance of Payments Division, Bureau of Economic Analysis, U.S. Department of Commerce, 4600 Silver Hill Road, Washington, DC 20233; phone (301) 278-9189; or via email at 
                        <E T="03">Christopher.Stein@bea.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Through this Notice, BEA publishes the reporting requirements for the BE-185 survey form. As noted below, all entities required to respond to this mandatory survey will be contacted by BEA. Entities must submit the completed survey forms within 45 days after the end of each fiscal quarter, except for the final quarter of the entity's fiscal year when reports must be filed within 90 days. This Notice is being issued in conformance with the rule BEA issued on April 24, 2012 (77 FR 24373), establishing guidelines for collecting data on international trade in services and direct investment through notices, rather than through rulemaking. Additional information about BEA's collection of data on international trade in services and direct investment can be found in the 2012 rule, the International Investment and Trade in Services Survey Act (22 U.S.C. 3101 
                    <E T="03">et seq.</E>
                    ), and 15 CFR part 801, and by Section 5408 of the Omnibus Trade and Competitiveness Act of 1988 (Pub. L. 100-418, 15 U.S.C. 4908(b)). Survey data on international trade in services and direct investment that are not collected pursuant to the 2012 rule are described separately in 15 CFR part 801. The BE-185 survey form and instructions are available at 
                    <E T="03">www.bea.gov/ssb.</E>
                </P>
                <HD SOURCE="HD1">Reporting</HD>
                <P>Notice of specific reporting requirements, including who is to report, the information to be reported, the manner of reporting, and the time and place of filing reports, will be mailed to those required to complete this survey.</P>
                <P>
                    <E T="03">Who Must Report:</E>
                     (a) Reports are required from each U.S. person who had reportable sales of financial services to foreign persons that exceeded $20 million during the prior fiscal year, or are expected to exceed that amount during the current fiscal year; or had reportable purchases of financial services from foreign persons that exceeded $15 million during the prior fiscal year, or are expected to exceed that amount during the current fiscal year. Because the thresholds are applied separately to sales and purchases, the reporting requirements may apply only to sales, only to purchases, or to both.
                </P>
                <P>(b) Entities required to report will be contacted individually by BEA. Entities not contacted by BEA have no reporting responsibilities.</P>
                <P>
                    <E T="03">What To Report:</E>
                     The survey collects information on transactions in financial services between U.S. financial services providers and foreign persons.
                </P>
                <P>
                    <E T="03">How To Report:</E>
                     Reports can be filed using BEA's electronic reporting system at 
                    <E T="03">www.bea.gov/efile.</E>
                     Copies of the survey forms and instructions, which contain complete information on reporting procedures and definitions, can be downloaded from 
                    <E T="03">www.bea.gov/ssb</E>
                     and submitted through mail or fax. Form BE-185 inquiries can be made by phone to BEA at (301) 278-9303 or by sending an email to 
                    <E T="03">be-185help@bea.gov.</E>
                </P>
                <P>
                    <E T="03">When To Report:</E>
                     Reports are due to BEA 45 days after the end of each fiscal quarter, except for the final quarter of the entity's fiscal year when reports must be filed within 90 days.
                </P>
                <HD SOURCE="HD1">Paperwork Reduction Act Notice</HD>
                <P>
                    This data collection has been approved by the Office of Management and Budget (OMB) in accordance with the Paperwork Reduction Act and assigned control number 0608-0065. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid control number assigned by OMB. Public reporting burden for this collection of information is estimated to average 10 hours per response. Additional information regarding this burden estimate may be viewed at 
                    <E T="03">www.reginfo.gov;</E>
                     under the Information Collection Review tab, click on “Search” and use the above OMB control number to search for the current survey instrument. Send comments regarding this burden estimate to Director, Bureau of Economic Analysis (BE-1), U.S. Department of Commerce, 4600 Silver Hill Rd., Washington, DC 20233; and to the Office of Management and Budget, Paperwork Reduction Project 0608-0065, 725 17th Street NW, Washington, DC 20503, or via email at 
                    <E T="03">OIRA_Submission@omb.eop.gov.</E>
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>22 U.S.C. 3101-3108 and 15 U.S.C. 4908(b).</P>
                </AUTH>
                <SIG>
                    <NAME>Paul W. Farello,</NAME>
                    <TITLE>Associate Director for International Economics, Bureau of Economic Analysis.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09804 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Economic Analysis</SUBAGY>
                <DEPDOC>[Docket No. 190329309-9309-01]</DEPDOC>
                <RIN>RIN 0691-XC096</RIN>
                <SUBJECT>BE-45: Quarterly Survey of Insurance Transactions by U.S. Insurance Companies With Foreign Persons</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Economic Analysis, Commerce.</P>
                </AGY>
                <ACT>
                    <PRTPAGE P="20853"/>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of reporting requirements.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>By this Notice, the Bureau of Economic Analysis (BEA), Department of Commerce, is informing the public that it is conducting the mandatory survey titled Quarterly Survey of Insurance Transactions by U.S. Insurance Companies with Foreign Persons (BE-45). The data collected on the BE-45 survey are needed to measure U.S. trade in insurance services and to analyze the impact of U.S. trade on the U.S. and foreign economies. This survey is authorized by the International Investment and Trade in Services Survey Act.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Christopher Stein, Chief, Services Surveys Branch (BE-50), Balance of Payments Division, Bureau of Economic Analysis, U.S. Department of Commerce, 4600 Silver Hill Road, Washington, DC 20233; phone (301) 278-9189; or via email at 
                        <E T="03">Christopher.Stein@bea.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Through this Notice, BEA publishes the reporting requirements for the BE-45 survey form. As noted below, all entities required to respond to this mandatory survey will be contacted by BEA. Entities must submit the completed survey forms within 60 days after the end of each calendar quarter, except for the final quarter of the calendar year when reports must be filed within 90 days. This Notice is being issued in conformance with the rule BEA issued on April 24, 2012 (77 FR 24373), establishing guidelines for collecting data on international trade in services and direct investment through notices, rather than through rulemaking. Additional information about BEA's collection of data on international trade in services and direct investment can be found in the 2012 rule, the International Investment and Trade in Services Survey Act (22 U.S.C. 3101 
                    <E T="03">et seq.</E>
                    ), and 15 CFR part 801. Survey data on international trade in services and direct investment that are not collected pursuant to the 2012 rule are described separately in 15 CFR part 801. The BE-45 survey form and instructions are available at 
                    <E T="03">www.bea.gov/ssb.</E>
                </P>
                <HD SOURCE="HD1">Reporting</HD>
                <P>Notice of specific reporting requirements, including who is to report, the information to be reported, the manner of reporting, and the time and place of filing reports, will be mailed to those required to complete this survey.</P>
                <P>
                    <E T="03">Who Must Report:</E>
                     (a) Reports are required from U.S. persons whose reportable transactions exceeded $8 million (positive or negative) during the prior calendar year, or are expected to exceed that amount during the current calendar year. See BE-45 survey form for more details.
                </P>
                <P>(b) Entities required to report will be contacted individually by BEA. Entities not contacted by BEA have no reporting responsibilities.</P>
                <P>
                    <E T="03">What To Report:</E>
                     The survey collects information on cross-border insurance transactions between U.S. insurance companies and foreign persons.
                </P>
                <P>
                    <E T="03">How To Report:</E>
                     Reports can be filed using BEA's electronic reporting system at 
                    <E T="03">www.bea.gov/efile.</E>
                     Copies of the survey forms and instructions, which contain complete information on reporting procedures and definitions, can be downloaded from 
                    <E T="03">www.bea.gov/ssb</E>
                     and submitted through mail or fax. Form BE-45 inquiries can be made by phone to BEA at (301) 278-9303 or by sending an email to 
                    <E T="03">be-45help@bea.gov.</E>
                </P>
                <P>
                    <E T="03">When To Report:</E>
                     Reports are due to BEA 60 days after the end of each calendar quarter, except for the final quarter of the calendar year when reports must be filed within 90 days.
                </P>
                <HD SOURCE="HD1">Paperwork Reduction Act Notice</HD>
                <P>
                    This data collection has been approved by the Office of Management and Budget (OMB) in accordance with the Paperwork Reduction Act and assigned control number 0608-0066. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid control number assigned by OMB. Public reporting burden for this collection of information is estimated to average 9 hours per response. Additional information regarding this burden estimate may be viewed at 
                    <E T="03">www.reginfo.gov;</E>
                     under the Information Collection Review tab, click on “Search” and use the above OMB control number to search for the current survey instrument. Send comments regarding this burden estimate to Director, Bureau of Economic Analysis (BE-1), U.S. Department of Commerce, 4600 Silver Hill Rd., Washington, DC 20233; and to the Office of Management and Budget, Paperwork Reduction Project 0608-0066, 725 17th Street NW, Washington, DC 20503, or via email at 
                    <E T="03">OIRA_Submission@omb.eop.gov.</E>
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>22 U.S.C. 3101-3108.</P>
                </AUTH>
                <SIG>
                    <NAME>Paul W. Farello,</NAME>
                    <TITLE>Associate Director for International Economics, Bureau of Economic Analysis.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09808 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3510-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Economic Analysis</SUBAGY>
                <DEPDOC>[Docket No. 190401316-9316-01]</DEPDOC>
                <RIN>RIN 0691-XC100</RIN>
                <SUBJECT>BE-605: Quarterly Survey of Foreign Direct Investment in the United States—Transactions of U.S. Affiliate With Foreign Parent</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Economic Analysis, Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of reporting requirements.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>By this Notice, the Bureau of Economic Analysis (BEA), Department of Commerce, is informing the public that it is conducting the mandatory survey titled Quarterly Survey of Foreign Direct Investment in the United States—Transactions of U.S. Affiliate with Foreign Parent (BE-605). The data collected on the BE-605 survey are needed to measure the size and economic significance of foreign direct investment in the United States and its impact on the U.S. economy. This survey is authorized by the International Investment and Trade in Services Survey Act.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jessica Hanson, Chief, Direct Transactions and Positions Branch (BE-49), Bureau of Economic Analysis, U.S. Department of Commerce, 4600 Silver Hill Road, Washington, DC 20233; phone (301) 278-9595; or via email at 
                        <E T="03">Jessica.Hanson@bea.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Through this Notice, BEA publishes the reporting requirements for the BE-605 survey form. As noted below, all entities required to respond to this mandatory survey will be contacted by BEA. Entities must submit the completed survey forms within 30 days after the end of each calendar or fiscal quarter, or within 45 days if the report is for the final quarter of the financial reporting year. This Notice is being issued in conformance with the rule BEA issued on April 24, 2012 (77 FR 24373), establishing guidelines for collecting data on international trade in services and direct investment through notices, rather than through rulemaking. Additional information about BEA's collection of data on international trade in services and direct investment can be found in the 2012 rule, the International Investment and Trade in Services Survey Act (22 U.S.C. 3101 
                    <E T="03">et seq.</E>
                    ), and 15 CFR part 801. Survey data on international trade in services and direct investment that are not collected pursuant to the 2012 rule are described 
                    <PRTPAGE P="20854"/>
                    separately in 15 CFR part 801. The BE-605 survey forms and instructions are available at 
                    <E T="03">www.bea.gov/fdi.</E>
                </P>
                <HD SOURCE="HD1">Reporting</HD>
                <P>Notice of specific reporting requirements, including who is to report, the information to be reported, the manner of reporting, and the time and place of filing reports, will be mailed to those required to complete this survey.</P>
                <P>
                    <E T="03">Who Must Report:</E>
                     (a) Reports are required from each U.S. business enterprise in which a foreign person has a direct and/or indirect ownership interest of at least 10 percent of the voting stock in an incorporated business enterprise, or an equivalent interest in an unincorporated business enterprise, and that meets the additional conditions detailed in Form BE-605.
                </P>
                <P>(b) Entities required to report will be contacted individually by BEA. Entities not contacted by BEA have no reporting responsibilities.</P>
                <P>
                    <E T="03">What To Report:</E>
                     The survey collects information on transactions between parent companies and their affiliates and on direct investment positions (stocks).
                </P>
                <P>
                    <E T="03">How To Report:</E>
                     Reports can be filed using BEA's electronic reporting system at 
                    <E T="03">www.bea.gov/efile.</E>
                     Copies of the survey form and instructions, which contain complete information on reporting procedures and definitions, can be downloaded from 
                    <E T="03">www.bea.gov/fdi</E>
                     and submitted through mail or fax. Form BE-605 inquiries can be made by phone to BEA at (301) 278-9422 or by sending an email to 
                    <E T="03">be605@bea.gov.</E>
                </P>
                <P>
                    <E T="03">When To Report:</E>
                     Reports are due to BEA 30 days after the close of each calendar or fiscal quarter, or 45 days if the report is for the final quarter of the financial reporting year.
                </P>
                <HD SOURCE="HD1">Paperwork Reduction Act Notice</HD>
                <P>
                    This data collection has been approved by the Office of Management and Budget (OMB) in accordance with the Paperwork Reduction Act and assigned control number 0608-0009. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid control number assigned by OMB. Public reporting burden for this collection of information is estimated to average 1 hour per response. Additional information regarding this burden estimate may be viewed at 
                    <E T="03">www.reginfo.gov;</E>
                     under the Information Collection Review tab, click on “Search” and use the above OMB control number to search for the current survey instrument. Send comments regarding this burden estimate to Director, Bureau of Economic Analysis (BE-1), U.S. Department of Commerce, 4600 Silver Hill Rd., Washington, DC 20233; and to the Office of Management and Budget, Paperwork Reduction Project 0608-0009, 725 17th Street NW, Washington, DC 20503, or via email at 
                    <E T="03">OIRA_Submission@omb.eop.gov.</E>
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 22 U.S.C. 3101-3108.</P>
                </AUTH>
                <SIG>
                    <NAME>Paul W. Farello,</NAME>
                    <TITLE>Associate Director for International Economics, Bureau of Economic Analysis.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09818 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3510-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Economic Analysis</SUBAGY>
                <DEPDOC>[Docket No. 190329308-9308-01]</DEPDOC>
                <RIN>RIN 0691-XC095</RIN>
                <SUBJECT>BE-37: Quarterly Survey of U.S. Airline Operators' Foreign Revenues and Expenses</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Economic Analysis, Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of reporting requirements.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>By this Notice, the Bureau of Economic Analysis (BEA), Department of Commerce, is informing the public that it is conducting the mandatory survey titled Quarterly Survey of U.S. Airline Operators' Foreign Revenues and Expenses (BE-37). The data collected on the BE-37 survey are needed to measure U.S. trade in transport services and to analyze the impact of U.S. trade on the U.S. and foreign economies. This survey is authorized by the International Investment and Trade in Services Survey Act.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Christopher Stein, Chief, Services Surveys Branch (BE-50), Balance of Payments Division, Bureau of Economic Analysis, U.S. Department of Commerce, 4600 Silver Hill Road, Washington, DC 20233; phone (301) 278-9189; or via email at 
                        <E T="03">Christopher.Stein@bea.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Through this Notice, BEA publishes the reporting requirements for the BE-37 survey form. As noted below, all entities required to respond to this mandatory survey will be contacted by BEA. Entities must submit the completed survey forms within 45 days after the end of each calendar quarter. This Notice is being issued in conformance with the rule BEA issued on April 24, 2012 (77 FR 24373), establishing guidelines for collecting data on international trade in services and direct investment through notices, rather than through rulemaking. Additional information about BEA's collection of data on international trade in services and direct investment can be found in the 2012 rule, the International Investment and Trade in Services Survey Act (22 U.S.C. 3101 
                    <E T="03">et seq.</E>
                    ), and 15 CFR part 801. Survey data on international trade in services and direct investment that are not collected pursuant to the 2012 rule are described separately in 15 CFR part 801. The BE-37 survey form and instructions are available at 
                    <E T="03">www.bea.gov/ssb.</E>
                </P>
                <HD SOURCE="HD1">Reporting</HD>
                <P>Notice of specific reporting requirements, including who is to report, the information to be reported, the manner of reporting, and the time and place of filing reports, will be mailed to those required to complete this survey.</P>
                <P>
                    <E T="03">Who Must Report:</E>
                     (a) Reports are required from U.S. airline operators that had total reportable revenues or total reportable expenses that were $500,000 or more during the prior year, or are expected to be $500,000 or more during the current year.
                </P>
                <P>(b) Entities required to report will be contacted individually by BEA. Entities not contacted by BEA have no reporting responsibilities.</P>
                <P>
                    <E T="03">What To Report:</E>
                     The survey collects information on U.S. airline operators' foreign revenues and expenses.
                </P>
                <P>
                    <E T="03">How To Report:</E>
                     Reports can be filed using BEA's electronic reporting system at 
                    <E T="03">www.bea.gov/efile.</E>
                     Copies of the survey forms and instructions, which contain complete information on reporting procedures and definitions, can be downloaded from 
                    <E T="03">www.bea.gov/ssb</E>
                     and submitted through mail or fax. Form BE-37 inquiries can be made by phone to BEA at (301) 278-9303 or by sending an email to 
                    <E T="03">be-37help@bea.gov.</E>
                </P>
                <P>
                    <E T="03">When To Report:</E>
                     Reports are due to BEA 45 days after the end of each calendar quarter.
                </P>
                <HD SOURCE="HD1">Paperwork Reduction Act Notice</HD>
                <P>
                    This data collection has been approved by the Office of Management and Budget (OMB) in accordance with the Paperwork Reduction Act and assigned control number 0608-0011. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid control number assigned by OMB. Public reporting burden for this collection of information is estimated to average 4 hours per response. Additional information regarding this burden estimate may be 
                    <PRTPAGE P="20855"/>
                    viewed at 
                    <E T="03">www.reginfo.gov;</E>
                     under the Information Collection Review tab, click on “Search” and use the above OMB control number to search for the current survey instrument. Send comments regarding this burden estimate to Director, Bureau of Economic Analysis (BE-1), U.S. Department of Commerce, 4600 Silver Hill Rd., Washington, DC 20233; and to the Office of Management and Budget, Paperwork Reduction Project 0608-0011, 725 17th Street NW, Washington, DC 20503, or via email at 
                    <E T="03">OIRA_Submission@omb.eop.gov.</E>
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>22 U.S.C. 3101-3108.</P>
                </AUTH>
                <SIG>
                    <NAME>Paul W. Farello,</NAME>
                    <TITLE>Associate Director for International Economics, Bureau of Economic Analysis.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09802 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Economic Analysis</SUBAGY>
                <DEPDOC>[Docket No. 190329311-9311-01]</DEPDOC>
                <RIN>RIN 0691-XC097</RIN>
                <SUBJECT>BE-125: Quarterly Survey of Transactions in Selected Services and Intellectual Property With Foreign Persons</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Economic Analysis, Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of reporting requirements.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>By this Notice, the Bureau of Economic Analysis (BEA), Department of Commerce, is informing the public that it is conducting the mandatory survey titled Quarterly Survey of Transactions in Selected Services and Intellectual Property with Foreign Persons (BE-125). The data collected on the BE-125 survey are needed to measure U.S. trade in services and to analyze the impact of U.S. trade on the U.S. and foreign economies. This survey is authorized by the International Investment and Trade in Services Survey Act.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Christopher Stein, Chief, Services Surveys Branch (BE-50), Balance of Payments Division, Bureau of Economic Analysis, U.S. Department of Commerce, 4600 Silver Hill Road, Washington, DC 20233; phone (301) 278-9189; or via email at 
                        <E T="03">Christopher.Stein@bea.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Through this Notice, BEA publishes the reporting requirements for the BE-125 survey form. As noted below, all entities required to respond to this mandatory survey will be contacted by BEA. Entities must submit the completed survey forms within 45 days after the end of each fiscal quarter, except for the final quarter of the entity's fiscal year when reports must be filed within 90 days. This Notice is being issued in conformance with the rule BEA issued on April 24, 2012 (77 FR 24373), establishing guidelines for collecting data on international trade in services and direct investment through notices, rather than through rulemaking. Additional information about BEA's collection of data on international trade in services and direct investment can be found in the 2012 rule, the International Investment and Trade in Services Survey Act (22 U.S.C. 3101 
                    <E T="03">et seq.</E>
                    ), and 15 CFR part 801. Survey data on international trade in services and direct investment that are not collected pursuant to the 2012 rule are described separately in 15 CFR part 801. The BE-125 survey form and instructions are available at 
                    <E T="03">www.bea.gov/ssb.</E>
                </P>
                <HD SOURCE="HD1">Reporting</HD>
                <P>Notice of specific reporting requirements, including who is to report, the information to be reported, the manner of reporting, and the time and place of filing reports, will be mailed to those required to complete this survey.</P>
                <P>
                    <E T="03">Who Must Report:</E>
                     (a) Reports are required from each U.S. person who had combined reportable sales of services or intellectual property to foreign persons that exceeded $6 million during the prior fiscal year, or are expected to exceed that amount during the current fiscal year; or had combined reportable purchases of services or intellectual property from foreign persons that exceeded $4 million during the prior fiscal year, or are expected to exceed that amount during the current fiscal year. Because the thresholds are applied separately to sales and purchases, the reporting requirements may apply only to sales, only to purchases, or to both. See BE-125 survey form for more details.
                </P>
                <P>(b) Entities required to report will be contacted individually by BEA. Entities not contacted by BEA have no reporting responsibilities.</P>
                <P>
                    <E T="03">What To Report:</E>
                     The survey collects information on U.S. international trade in selected services and intellectual property.
                </P>
                <P>
                    <E T="03">How To Report:</E>
                     Reports can be filed using BEA's electronic reporting system at 
                    <E T="03">www.bea.gov/efile.</E>
                     Copies of the survey forms and instructions, which contain complete information on reporting procedures and definitions, can be downloaded from 
                    <E T="03">www.bea.gov/ssb</E>
                     and submitted through mail or fax. Form BE-125 inquiries can be made by phone to BEA at (301) 278-9303 or by sending an email to 
                    <E T="03">be-125help@bea.gov.</E>
                </P>
                <P>
                    <E T="03">When To Report:</E>
                     Reports are due to BEA 45 days after the end of each fiscal quarter, except for the final quarter of the entity's fiscal year when reports must be filed within 90 days.
                </P>
                <HD SOURCE="HD1">Paperwork Reduction Act Notice</HD>
                <P>
                    This data collection has been approved by the Office of Management and Budget (OMB) in accordance with the Paperwork Reduction Act and assigned control number 0608-0067. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid control number assigned by OMB. Public reporting burden for this collection of information is estimated to average 21 hours per response. Additional information regarding this burden estimate may be viewed at 
                    <E T="03">www.reginfo.gov;</E>
                     under the Information Collection Review tab, click on “Search” and use the above OMB control number to search for the current survey instrument. Send comments regarding this burden estimate to Director, Bureau of Economic Analysis (BE-1), U.S. Department of Commerce, 4600 Silver Hill Rd., Washington, DC 20233; and to the Office of Management and Budget, Paperwork Reduction Project 0608-0067, 725 17th Street NW, Washington, DC 20503, or via email at 
                    <E T="03">OIRA_Submission@omb.eop.gov.</E>
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>22 U.S.C. 3101-3108.</P>
                </AUTH>
                <SIG>
                    <NAME>Paul W. Farello,</NAME>
                    <TITLE>Associate Director for International Economics, Bureau of Economic Analysis.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09810 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3510-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Economic Analysis</SUBAGY>
                <DEPDOC>[Docket No. 190329301-9301-01]</DEPDOC>
                <RIN>RIN 0691-XC092</RIN>
                <SUBJECT>BE-15: Annual Survey of Foreign Direct Investment in the United States</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Economic Analysis, Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of reporting requirements.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        By this Notice, the Bureau of Economic Analysis (BEA), Department of Commerce, is informing the public that it is conducting the mandatory survey titled Annual Survey of Foreign Direct Investment in the United States 
                        <PRTPAGE P="20856"/>
                        (BE-15). The data collected on the BE-15 survey are needed to measure the size and economic significance of foreign direct investment in the United States and its impact on the U.S. economy. This survey is authorized by the International Investment and Trade in Services Survey Act.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ricardo Limés, Chief, Multinational Operations Branch (BE-49), Bureau of Economic Analysis, U.S. Department of Commerce, 4600 Silver Hill Road, Washington, DC 20233; phone (301) 278-9659; or via email at 
                        <E T="03">Ricardo.Limes@bea.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Through this Notice, BEA publishes the reporting requirements for the BE-15 survey form. As noted below, all entities required to respond to this mandatory survey will be contacted by BEA. A completed report covering the entity's fiscal year ending during the previous calendar year is due by May 31, 2019 (or by June 30 for reporting companies that use BEA's eFile system). This Notice is being issued in conformance with the rule BEA issued on April 24, 2012 (77 FR 24373), establishing guidelines for collecting data on international trade in services and direct investment through notices, rather than through rulemaking. Additional information about BEA's collection of data on international trade in services and direct investment can be found in the 2012 rule, the International Investment and Trade in Services Survey Act (22 U.S.C. 3101 
                    <E T="03">et seq.</E>
                    ), and 15 CFR part 801. Survey data on international trade in services and direct investment that are not collected pursuant to the 2012 rule are described separately in 15 CFR part 801. The BE-15 survey forms and instructions are available at 
                    <E T="03">www.bea.gov/fdi.</E>
                </P>
                <HD SOURCE="HD1">Reporting</HD>
                <P>Notice of specific reporting requirements, including who is to report, the information to be reported, the manner of reporting, and the time and place of filing reports, will be mailed to those required to complete this survey.</P>
                <P>
                    <E T="03">Who Must Report:</E>
                     (a) Reports are required from each U.S. business enterprise in which a foreign person has a direct and/or indirect ownership interest of at least 10 percent of the voting stock in an incorporated U.S. business enterprise, or an equivalent interest in an unincorporated U.S. business enterprise, and that meets the additional conditions detailed in Form BE-15.
                </P>
                <P>(b) Entities required to report will be contacted individually by BEA. Entities not contacted by BEA have no reporting responsibilities.</P>
                <P>
                    <E T="03">What To Report:</E>
                     The survey collects information on the operations of U.S. affiliates of foreign companies.
                </P>
                <P>
                    <E T="03">How To Report:</E>
                     Reports can be filed using BEA's electronic reporting system at 
                    <E T="03">www.bea.gov/efile.</E>
                     Copies of the survey forms and instructions, which contain complete information on reporting procedures and definitions, can be downloaded from 
                    <E T="03">www.bea.gov/fdi</E>
                     and submitted through mail or fax. Form BE-15 inquiries can be made by phone to BEA at (301) 278-9247 or by sending an email to 
                    <E T="03">be12/15@bea.gov.</E>
                </P>
                <P>
                    <E T="03">When To Report:</E>
                     A completed report covering an entity's fiscal year ending during the previous calendar year is due by May 31, 2019 (or by June 30 for reporting companies that use BEA's eFile system).
                </P>
                <HD SOURCE="HD1">Paperwork Reduction Act Notice</HD>
                <P>
                    This data collection has been approved by the Office of Management and Budget (OMB) in accordance with the Paperwork Reduction Act and assigned control number 0608-0034. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid control number assigned by OMB. Public reporting burden for this collection of information is estimated to average 19.7 hours per response. Additional information regarding this burden estimate may be viewed at 
                    <E T="03">www.reginfo.gov;</E>
                     under the Information Collection Review tab, click on “Search” and use the above OMB control number to search for the current survey instrument. Send comments regarding this burden estimate to Director, Bureau of Economic Analysis (BE-1), U.S. Department of Commerce, 4600 Silver Hill Rd., Washington, DC 20233; and to the Office of Management and Budget, Paperwork Reduction Project 0608-0034, 725 17th Street NW, Washington, DC 20503, or via email at 
                    <E T="03">OIRA_Submission@omb.eop.gov.</E>
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>22 U.S.C. 3101-3108.</P>
                </AUTH>
                <SIG>
                    <NAME>Paul W. Farello,</NAME>
                    <TITLE>Associate Director for International Economics, Bureau of Economic Analysis.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09794 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3510-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Economic Analysis</SUBAGY>
                <DEPDOC>[Docket No. 190329302-9302-01]</DEPDOC>
                <RIN>RIN 0691-XC093</RIN>
                <SUBJECT>BE-29: Annual Survey of Foreign Ocean Carriers' Expenses in the United States</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Economic Analysis, Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of reporting requirements.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>By this Notice, the Bureau of Economic Analysis (BEA), Department of Commerce, is informing the public that it is conducting the mandatory survey titled Annual Survey of Foreign Ocean Carriers' Expenses in the United States (BE-29). The data collected on the BE-29 survey are needed to measure U.S. trade in transport services and to analyze the impact of U.S. trade on the U.S. and foreign economies. This survey is authorized by the International Investment and Trade in Services Survey Act.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Christopher Stein, Chief, Services Surveys Branch (BE-50), Balance of Payments Division, Bureau of Economic Analysis, U.S. Department of Commerce, 4600 Silver Hill Road, Washington, DC 20233; phone (301) 278-9189; or via email at 
                        <E T="03">Christopher.Stein@bea.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Through this Notice, BEA publishes the reporting requirements for the BE-29 survey form. As noted below, all entities required to respond to this mandatory survey will be contacted by BEA. Entities must submit the completed survey forms within 90 days after the end of each calendar year. This Notice is being issued in conformance with the rule BEA issued on April 24, 2012 (77 FR 24373), establishing guidelines for collecting data on international trade in services and direct investment through notices, rather than through rulemaking. Additional information about BEA's collection of data on international trade in services and direct investment can be found in the 2012 rule, the International Investment and Trade in Services Survey Act (22 U.S.C. 3101 
                    <E T="03">et seq.</E>
                    ), and 15 CFR part 801. Survey data on international trade in services and direct investment that are not collected pursuant to the 2012 rule are described separately in 15 CFR part 801. The BE-29 survey form and instructions are available at 
                    <E T="03">www.bea.gov/ssb.</E>
                    <PRTPAGE P="20857"/>
                </P>
                <HD SOURCE="HD1">Reporting</HD>
                <P>Notice of specific reporting requirements, including who is to report, the information to be reported, the manner of reporting, and the time and place of filing reports, will be mailed to those required to complete this survey.</P>
                <P>
                    <E T="03">Who Must Report:</E>
                     (a) Reports are required from U.S. agents of foreign carriers who handle 40 or more foreign ocean carrier port calls in the reporting period, or had reportable expenses of $250,000 or more in the reporting period for all foreign ocean vessels handled by the U.S. Agent. See BE-29 survey form for more details.
                </P>
                <P>(b) Entities required to report will be contacted individually by BEA. Entities not contacted by BEA have no reporting responsibilities.</P>
                <P>
                    <E T="03">What To Report:</E>
                     The survey collects information on foreign ocean carriers' expenses in the United States.
                </P>
                <P>
                    <E T="03">How To Report:</E>
                     Reports can be filed using BEA's electronic reporting system at 
                    <E T="03">www.bea.gov/efile.</E>
                     Copies of the survey forms and instructions, which contain complete information on reporting procedures and definitions, can be downloaded from 
                    <E T="03">www.bea.gov/ssb</E>
                     and submitted through mail or fax. Form BE-29 inquiries can be made by phone to BEA at (301) 278-9303 or by sending an email to 
                    <E T="03">be-29help@bea.gov.</E>
                </P>
                <P>
                    <E T="03">When To Report:</E>
                     Reports are due to BEA 90 days after the end of each calendar year.
                </P>
                <HD SOURCE="HD1">Paperwork Reduction Act Notice</HD>
                <P>
                    This data collection has been approved by the Office of Management and Budget (OMB) in accordance with the Paperwork Reduction Act and assigned control number 0608-0012. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid control number assigned by OMB. Public reporting burden for this collection of information is estimated to average 3 hours per response. Additional information regarding this burden estimate may be viewed at 
                    <E T="03">www.reginfo.gov;</E>
                     under the Information Collection Review tab, click on “Search” and use the above OMB control number to search for the current survey instrument. Send comments regarding this burden estimate to Director, Bureau of Economic Analysis (BE-1), U.S. Department of Commerce, 4600 Silver Hill Rd., Washington, DC 20233; and to the Office of Management and Budget, Paperwork Reduction Project 0608-0012, 725 17th Street NW, Washington, DC 20503, or via email at 
                    <E T="03">OIRA_Submission@omb.eop.gov.</E>
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>22 U.S.C. 3101-3108.</P>
                </AUTH>
                <SIG>
                    <NAME>Paul W. Farello,</NAME>
                    <TITLE>Associate Director for International Economics, Bureau of Economic Analysis.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09795 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3510-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Foreign-Trade Zones Board</SUBAGY>
                <DEPDOC>[B-76-2018]</DEPDOC>
                <SUBJECT>Foreign-Trade Zone (FTZ) 70—Detroit, Michigan, Authorization of Production Activity, Fluid Equipment Development Company, LLC (Energy Recovery Turbines and Centrifugal Pumps), Monroe, Michigan</SUBJECT>
                <P>On November 28, 2018, the Greater Detroit Foreign-Trade Zone, Inc., grantee of FTZ 70, submitted a notification of proposed production activity to the FTZ Board on behalf of Fluid Equipment Development Company, LLC, within Site 77, in Monroe, Michigan.</P>
                <P>
                    The notification was processed in accordance with the regulations of the FTZ Board (15 CFR part 400), including notice in the 
                    <E T="04">Federal Register</E>
                     inviting public comment (83 FR 63154-63155, December 7, 2018). On May 7, 2019, the applicant was notified of the FTZ Board's decision that no further review of the activity is warranted at this time. The production activity described in the notification was authorized, subject to the FTZ Act and the FTZ Board's regulations, including Section 400.14.
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Andrew McGilvray,</NAME>
                    <TITLE>Executive Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09789 Filed 5-10-19; 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-570-954]</DEPDOC>
                <SUBJECT>Certain Magnesia Carbon Bricks From the People's Republic of China: Final Results of the Antidumping Duty Administrative Review; 2016-2017</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Commerce (Commerce) is issuing a final no shipments determination in the final results of the antidumping duty administrative review on certain magnesia carbon bricks (MCBs) from the People's Republic of China (China), for the September 1, 2016 through August 31, 2017 period of review (POR).</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Christian Llinas, AD/CVD Operations, Office V, Enforcement and Compliance, International Trade Administration, Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-4877.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On October 11, 2018, Commerce published the preliminary results of the seventh administrative review of the antidumping duty order on MCBs from China for the POR.
                    <SU>1</SU>
                    <FTREF/>
                     For a history of the events that occurred since the 
                    <E T="03">Preliminary Results,</E>
                     see the Issues and Decision Memorandum.
                    <SU>2</SU>
                    <FTREF/>
                     On January 28, 2019, Commerce tolled the deadlines in this case and the final results by 40 days.
                    <SU>3</SU>
                    <FTREF/>
                     On March 5, 2019, Commerce extended the deadline for the final results to May 7, 2019.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Certain Magnesia Carbon Bricks from the People's Republic of China; Preliminary Results of the Antidumping Duty Administrative Review; 2016-2017,</E>
                         83 FR 51435 (October 11, 2018) (
                        <E T="03">Preliminary Results</E>
                        ) and accompanying Preliminary Decision Memorandum.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Certain Magnesia Carbon Bricks from the People's Republic of China: Issues and Decision Memorandum for the Final Results of the 2016 Antidumping Duty Administrative Review,” which is dated concurrently with these final results and is hereby adopted by this notice (Issues and Decision Memorandum).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Memorandum to the Record, from Gary Taverman, Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations, performing the non-exclusive functions and duties of the Assistant Secretary for Enforcement and Compliance, “Deadlines Affected by the Partial Shutdown of the Federal Government,” dated January 28, 2019. All deadlines in this segment of the proceeding have been extended by 40 days.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         “Administrative Review of the Antidumping Duty Order on Certain Magnesia Carbon Bricks from the People's Republic of China: Extension of Deadline for the Final Results,” dated March 5, 2019.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Order</HD>
                <P>
                    The scope of the order includes certain chemically-bonded MCBs from China.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         For a complete description of the scope of the order, 
                        <E T="03">see</E>
                         “Certain Magnesia Carbon Bricks from the People's Republic of China: Issues and Decision Memorandum for the Final Results of the Seventh Antidumping Duty Administrative Review: 2016-2017,” dated concurrently with and hereby adopted by this notice (Issues and Decision Memorandum).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>
                    All issues raised by interested parties in their case and rebuttal briefs, and our analysis thereof, are addressed in the Issues and Decision Memorandum. The issues are identified in the Appendix to this notice. The Issues and Decision Memorandum is a public document and is on file in the Central Records Unit 
                    <PRTPAGE P="20858"/>
                    (CRU), Room B8024 of the main Department of Commerce building, as well as electronically via Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic Service System (ACCESS). ACCESS is available to registered users at 
                    <E T="03">http://access.trade.gov</E>
                     and in the CRU. In addition, a complete version of the Issues and Decision Memorandum can be accessed directly on the internet at 
                    <E T="03">http://enforcement.trade.gov/frn/index.html.</E>
                     The signed Issues and Decision Memorandum and the electronic version of the Issues and Decision Memorandum are identical in content.
                </P>
                <HD SOURCE="HD1">Final Determination of No Shipments</HD>
                <P>
                    Commerce preliminarily found that Fedmet, Fengchi Imp. and Exp. Co., Ltd. of Haicheng City, Fengchi Mining Co., Ltd. of Haicheng City, and Fengchi Refractories Co., of Haicheng City (collectively, Fengchi), and RHI Refractories Liaoning Co., Ltd. (RHI) had no reviewable entries, shipments, or sales of the subject merchandise to the United States during the POR.
                    <SU>6</SU>
                    <FTREF/>
                     After the 
                    <E T="03">Preliminary Results,</E>
                     with respect to Fengchi and RHI, no party commented on our preliminary no shipments finding, nor has any party submitted record evidence which would call this finding into question. Therefore, for the final results, we continue to find that Fengchi and RHI had no shipments of subject merchandise during the POR. With respect to Fedmet, we placed entry packages obtained from Customs and Border Protection (CBP) on the record of this review, and interested parties submitted comments on this information.
                    <SU>7</SU>
                    <FTREF/>
                     As discussed in the Issues and Decision Memorandum, we continue to find that Fedmet also did not have any reviewable entries, shipments, or sales of subject merchandise to the United States during the POR.
                    <SU>8</SU>
                    <FTREF/>
                     Consistent with our practice, we will issue appropriate instructions to U.S. Customs and Border Protection (CBP) based on our final results.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See Preliminary Results</E>
                         at “Preliminary Determination of No Shipments.”
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Memo to the File, “Placement of U.S. Customs and Border Protection (CBP) Entry Summary Packages Regarding Fedmet Resources Corporation on the Record of the Administrative Review,” dated December 4, 2018 (CBP Entry Package Memo); the petitioners' December 14, 2018 submission; Fedmet's December 14, 2018 submission.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Issues and Decision Memorandum.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Assessment Rates</HD>
                <P>
                    We have not calculated any assessment rates in this administrative review. Pursuant to Commerce's assessment practice, because we have determined that Fedmet, Fengchi, and RHI had no reviewable entries, shipments, or sales of the subject merchandise to the United States during the POR, any suspended entries that entered under their case numbers (
                    <E T="03">i.e.,</E>
                     at that exporter's rate) will be liquidated at the China-wide entity rate.
                    <SU>9</SU>
                    <FTREF/>
                     We will instruct CBP to liquidate entries from the China-wide entity at the current rate for the China-wide entity (
                    <E T="03">i.e.,</E>
                     236.00 percent). Commerce intends to issue appropriate assessment instructions to CBP 15 days after the publication date of the final results of this administrative review.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See Non-Market Economy Antidumping Proceedings: Assessment of Antidumping Duties,</E>
                         76 FR 65694 (October 24, 2011).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                <P>
                    The following cash deposit requirements will be effective upon publication of the final results of this administrative review for shipments of the subject merchandise from China entered, or withdrawn from warehouse, for consumption on or after the publication date of this notice, as provided by section 751(a)(2)(C) of the Act: (1) For previously investigated or reviewed Chinese and non-Chinese exporters that received a separate rate in a prior segment of this proceeding, the cash deposit rate will continue to be the existing exporter-specific rate published for the most recently completed period; (2) for all Chinese exporters of subject merchandise that have not been found to be entitled to a separate rate, the cash deposit rate will be the rate previously established for the China-wide entity (
                    <E T="03">i.e.,</E>
                     236.00 percent); and (3) for all non-Chinese exporters of subject merchandise which have not received their own rate, the cash deposit rate will be the rate applicable to the Chinese exporter that supplied that non-Chinese exporter. These deposit requirements, when imposed, shall remain in effect until further notice.
                </P>
                <HD SOURCE="HD1">Notification to Importers</HD>
                <P>This notice also serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f)(2) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period. Failure to comply with this requirement could result in Commerce's presumption that reimbursement of antidumping duties occurred and the subsequent assessment of double antidumping duties.</P>
                <HD SOURCE="HD1">Administrative Protective Orders</HD>
                <P>This notice also serves as the only reminder to parties subject to administrative protective order (APO) of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305(a)(3). Timely written notification of the return or destruction of APO materials or conversion to judicial protective order is hereby requested. Failure to comply with the regulations and terms of an APO is a violation subject to sanction. We are issuing and publishing this notice in accordance with sections 751(a)(1) and 777(1) of the Tariff Act of 1930, as amended, and 19 CFR 351.213(d)(4).</P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Jeffrey I. Kessler,</NAME>
                    <TITLE>Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
                <APPENDIX>
                    <HD SOURCE="HED">Appendix</HD>
                    <HD SOURCE="HD1">List of Topics Discussed in the Final Decision Memorandum</HD>
                    <FP SOURCE="FP-2">I. Summary</FP>
                    <FP SOURCE="FP-2">II. Background</FP>
                    <FP SOURCE="FP-2">III. Scope of the Order</FP>
                    <FP SOURCE="FP-2">IV. Discussion of the Issue</FP>
                    <FP SOURCE="FP-2">V. Discussion of the Issue: Treatment of Fedmet</FP>
                    <FP SOURCE="FP-2">VI. Recommendation</FP>
                </APPENDIX>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09785 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-201-820]</DEPDOC>
                <SUBJECT>Fresh Tomatoes From Mexico: Termination of Suspension Agreement, Rescission of Administrative Review, and Continuation of the Antidumping Duty Investigation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable May 13, 2019.</P>
                </DATES>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On February 6, 2019, the Department of Commerce (Commerce) gave 90 days' notice of intent to withdraw from the 2013 Suspension Agreement on Fresh Tomatoes from Mexico (2013 Agreement), terminate the 2013 Agreement, and continue the antidumping duty (AD) investigation initiated in 1996. Because a new suspension agreement has not been signed, Commerce is withdrawing from and terminating the suspension agreement, rescinding the administrative review of the 2013 
                        <PRTPAGE P="20859"/>
                        Agreement, and continuing the antidumping duty (AD) investigation.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sally C. Gannon or Rebecca Lee, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-0162 or (202) 482-6188, respectively.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On April 18, 1996, Commerce initiated an AD investigation to determine whether imports of fresh tomatoes from Mexico are being, or are likely to be, sold in the United States at less than fair value (LTFV).
                    <SU>1</SU>
                    <FTREF/>
                     On May 16, 1996, the United States International Trade Commission (ITC) notified Commerce of its affirmative preliminary injury determination.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Initiation of Antidumping Duty Investigation: Fresh Tomatoes from Mexico,</E>
                         61 FR 18377 (April 25, 1996).
                    </P>
                </FTNT>
                <P>
                    On October 10, 1996, Commerce and certain tomato growers/exporters from Mexico initialed a proposed agreement to suspend the AD investigation. On October 28, 1996, Commerce issued its 
                    <E T="03">1996 Preliminary Determination</E>
                     and found imports of fresh tomatoes from Mexico were being sold at LTFV in the United States.
                    <SU>2</SU>
                    <FTREF/>
                     On the same day, Commerce and producers/exporters accounting for substantially all imports of fresh tomatoes from Mexico signed an agreement to suspend the investigation (1996 Agreement).
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Notice of Preliminary Determination of Sales at Less Than Fair Value and Postponement of Final Determination: Fresh Tomatoes from Mexico,</E>
                         61 FR 56608 (November 1, 1996) (
                        <E T="03">1996 Preliminary Determination</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See Suspension of Antidumping Investigation: Fresh Tomatoes from Mexico,</E>
                         61 FR 56618 (November 1, 1996).
                    </P>
                </FTNT>
                <P>
                    On May 31, 2002, certain tomato growers/exporters from Mexico accounting for a significant percentage of all fresh tomatoes imported into the United States from Mexico provided written notice to Commerce of their withdrawal from the 1996 Agreement, effective July 30, 2002. Because the 1996 Agreement would no longer cover substantially all imports of fresh tomatoes from Mexico, effective July 30, 2002, Commerce terminated the 1996 Agreement, terminated the sunset review of the suspended investigation, and resumed the AD investigation.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See Notice of Termination of Suspension Agreement, Termination of Sunset Review, and Resumption of Antidumping Investigation: Fresh Tomatoes from Mexico,</E>
                         67 FR 50858 (August 6, 2002).
                    </P>
                </FTNT>
                <P>
                    On November 8, 2002, Commerce and certain tomato growers/exporters from Mexico initialed a proposed agreement suspending the resumed AD investigation on imports of fresh tomatoes from Mexico. On December 4, 2002, Commerce and producers/exporters accounting for substantially all imports of fresh tomatoes from Mexico signed a new suspension agreement (2002 Agreement).
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See Suspension of Antidumping Investigation: Fresh Tomatoes from Mexico,</E>
                         67 FR 77044 (December 16, 2002).
                    </P>
                </FTNT>
                <P>
                    On November 26, 2007, certain tomato growers/exporters from Mexico accounting for a significant percentage of all fresh tomatoes imported into the United States provided written notice to Commerce of their withdrawal from the 2002 Agreement, effective 90 days from the date of their withdrawal letter (
                    <E T="03">i.e.,</E>
                     February 24, 2008), or earlier, at Commerce's discretion.
                </P>
                <P>On November 28, 2007, Commerce and certain tomato growers/exporters from Mexico initialed a new proposed agreement to suspend the AD investigation on imports of fresh tomatoes from Mexico. On December 3, 2007, Commerce released the initialed agreement to interested parties for comment. On December 17 and 18, 2007, several interested parties filed comments in support of the initialed agreement.</P>
                <P>
                    Because the 2002 Agreement would no longer cover substantially all imports of fresh tomatoes from Mexico, Commerce published a notice of intent to terminate the 2002 Agreement, intent to terminate the five-year sunset review of the suspended investigation, and intent to resume the AD investigation.
                    <SU>6</SU>
                    <FTREF/>
                     On January 16, 2008, Commerce published a notice of termination of the 2002 Agreement, termination of the five-year sunset review of the suspended investigation, and resumption of the AD investigation, effective January 18, 2008.
                    <SU>7</SU>
                    <FTREF/>
                     On January 22, 2008, Commerce signed a new suspension agreement (2008 Agreement) with producers/exporters accounting for substantially all imports of fresh tomatoes from Mexico.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See Fresh Tomatoes from Mexico: Notice of Intent to Terminate Suspension Agreement, Intent to Terminate the Five-Year Sunset Review, and Intent to Resume Antidumping Investigation,</E>
                         72 FR 70820 (December 13, 2007).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See Fresh Tomatoes from Mexico: Notice of Termination of Suspension Agreement, Termination of Five-Year Sunset Review, and Resumption of Antidumping Investigation,</E>
                         73 FR 2887 (January 16, 2008).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See Suspension of Antidumping Investigation: Fresh Tomatoes from Mexico,</E>
                         73 FR 4831 (January 28, 2008).
                    </P>
                </FTNT>
                <P>
                    On August 15, 2012, certain growers/exporters of fresh tomatoes from Mexico filed a letter with Commerce requesting consultations under Section IV.G.
                    <SU>9</SU>
                    <FTREF/>
                     of the 2008 Agreement, and Commerce agreed to consult. As a result of these consultations, on February 2, 2013, Commerce and tomato growers/exporters from Mexico accounting for a significant percentage of all fresh tomatoes imported into the United States from Mexico initialed a draft agreement that would suspend a resumed AD investigation on fresh tomatoes from Mexico. On February 8, 2013, Commerce published a notice of intent to terminate the 2008 Agreement, intent to terminate the five-year sunset review of the suspended investigation, and intent to resume the AD investigation.
                    <SU>10</SU>
                    <FTREF/>
                     On March 1, 2013, Commerce issued a notice of termination of the 2008 Agreement, termination of the five-year sunset review of the suspended investigation, and resumption of the AD investigation.
                    <SU>11</SU>
                    <FTREF/>
                     On March 4, 2013, Commerce and producers/exporters accounting for substantially all imports of fresh tomatoes from Mexico signed a new suspension agreement (2013 Agreement).
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Section IV.G. of the 2008 Agreement states that Commerce will consult with signatory producers/exporters regarding the operations of the 2008 Agreement. A party may request such consultations in any April or September (
                        <E T="03">i.e.</E>
                         prior to the beginning of each season) following the first year of the signing of the 2008 Agreement.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See Fresh Tomatoes from Mexico: Intent To Terminate Suspension Agreement and Resume Antidumping Investigation and Intent To Terminate Sunset Review,</E>
                         78 FR 9366 (February 8, 2013).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See Fresh Tomatoes from Mexico: Termination of Suspension Agreement, Termination of Five-Year Sunset Review, and Resumption of Antidumping Investigation,</E>
                         78 FR 14771 (March 7, 2013).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See Fresh Tomatoes from Mexico: Suspension of Antidumping Investigation,</E>
                         78 FR 14967 (March 8, 2013).
                    </P>
                </FTNT>
                <P>
                    On January 9, 2018, Commerce issued a letter that formally opened consultations with the Mexican tomato growers/exporters to negotiate possible revisions to the 2013 Agreement.
                    <SU>13</SU>
                    <FTREF/>
                     Since that time, Commerce has continued to negotiate with representatives of the Mexican growers/exporters and, in parallel, has continually consulted with representatives of the domestic industry.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         Letter from Commerce to CAADES 
                        <E T="03">et al.,</E>
                         “Consultations on the 2013 Agreement Suspending the Antidumping Investigation on Fresh Tomatoes from Mexico,” dated January 9, 2018.
                    </P>
                </FTNT>
                <P>
                    On February 1, 2018, Commerce initiated a five-year sunset review of the suspended investigation.
                    <SU>14</SU>
                    <FTREF/>
                     On March 29, 2018, the Florida Tomato Exchange (FTE), a member of the U.S. petitioning industry, filed a request that Commerce conduct an administrative review on 
                    <PRTPAGE P="20860"/>
                    growers/exporters of fresh tomatoes from Mexico covered by the 2013 Agreement. On May 2, 2018, Commerce initiated the administrative review of the 2013 Agreement.
                    <SU>15</SU>
                    <FTREF/>
                     On August 27, 2018, Commerce published in the 
                    <E T="04">Federal Register</E>
                     the preliminary results of the five-year sunset review of the suspended investigation.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See Initiation of Five-Year (Sunset) Reviews,</E>
                         83 FR 4641 (February 1, 2018).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See Initiation of Antidumping and Countervailing Duty Administrative Reviews</E>
                         (
                        <E T="03">Initiation of Administrative Review</E>
                        ), 83 FR 19215 (May 2, 2018).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See Fresh Tomatoes from Mexico: Preliminary Results of the Five-Year Sunset Review of the 2013 Suspension Agreement on Fresh Tomatoes from Mexico,</E>
                         83 FR 43642 (August 27, 2018).
                    </P>
                </FTNT>
                <P>
                    On November 14, 2018, the FTE filed a request that Commerce terminate the 2013 Agreement and resume the AD investigation under Section VI.B of the 2013 Agreement.
                    <SU>17</SU>
                    <FTREF/>
                     Section VI.B of the 2013 Agreement states that “the signatories or the Department may withdraw from this Agreement upon ninety days written notice to the other party.” On November 27, 2018, the Fresh Produce Association of the Americas filed a rebuttal to FTE's request to terminate.
                    <SU>18</SU>
                    <FTREF/>
                     On November 26, 2018 and November 28, 2018, respectively, Confederación de Asociaciones Agrícolas del Estado de Sinaloa, A.C., Consejo Agrícola de Baja California, A.C., Asociación Mexicana de Horticultura Protegida, A.C., Asociación de Productores de Hortalizas del Yaqui y Mayo, and Sistema Producto Tomate (collectively, CAADES 
                    <E T="03">et al.</E>
                     or the Mexican growers) submitted responses to FTE's previous request for Commerce to terminate the 2013 Agreement.
                    <E T="51">19 20</E>
                    <FTREF/>
                     On December 18, 2018, NS Brands, Ltd (NatureSweet), a signatory to the 2013 Agreement, filed a letter in support of the November 28, 2018 response by the Mexican growers.
                    <SU>21</SU>
                    <FTREF/>
                     On December 27, 2018, Commerce published in the 
                    <E T="04">Federal Register</E>
                     the final results of the five-year sunset review of the suspended investigation on fresh tomatoes from Mexico, finding that termination of the suspended investigation would be likely to lead to continuation or recurrence of dumping.
                    <SU>22</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         Letter to Wilbur Ross, Secretary of Commerce, from the FTE, “Fresh Tomatoes from Mexico: Request to Terminate Antidumping Suspension Agreement,” dated November 14, 2018.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See</E>
                         Letter to Wilbur Ross, Secretary of Commerce, from the Fresh Produce Association of the Americas, “Re: Fresh Tomatoes from Mexico: FTE's Misleading Request to Terminate Agreement,” dated November 27, 2018.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         Letter to Wilbur Ross, Secretary of Commerce, from CAADES 
                        <E T="03">et al.,</E>
                         “2013 Suspension Agreement on Fresh Tomatoes from Mexico,” dated November 26, 2018.
                    </P>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See</E>
                         Letter to Wilbur Ross, Secretary of Commerce, from CAADES 
                        <E T="03">et al.,</E>
                         “2013 Suspension Agreement on Fresh Tomatoes from Mexico,” dated November 28, 2018.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         Letter to Wilbur Ross, Secretary of Commerce, from NS Brands, Ltd., “2013 Suspension Agreement on Fresh Tomatoes from Mexico: NS Brands' Response to Petitions Request to Terminate 2013 Suspension Agreement,” dated December 18, 2018.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See Fresh Tomatoes from Mexico: Final Results of the Full Sunset Review of the Suspended Antidumping Duty Investigation,</E>
                         83 FR 66680 (December 27, 2018).
                    </P>
                </FTNT>
                <P>
                    On February 6, 2019, in accordance with Section VI.B of the 2013 Agreement, Commerce notified Mexican signatories that Commerce intends to withdraw from the 2013 Agreement.
                    <SU>23</SU>
                    <FTREF/>
                     Since the notification, as noted above, Commerce has held consultations with representatives of the Mexican growers/exporters and the domestic industry to discuss a possible new suspension agreement.
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See Fresh Tomatoes from Mexico: Intent To Terminate Suspension Agreement, Rescind the Sunset and Administrative Reviews, and Resume the Antidumping Duty Investigation,</E>
                         84 FR 7872 (March 5, 2019).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Investigation</HD>
                <P>
                    The merchandise subject to the investigation is all fresh or chilled tomatoes (fresh tomatoes) which have Mexico as their origin, except for those tomatoes which are for processing. For purposes of this suspended investigation, processing is defined to include preserving by any commercial process, such as canning, dehydrating, drying, or the addition of chemical substances, or converting the tomato product into juices, sauces, or purees. Fresh tomatoes that are imported for cutting up, not further processing (
                    <E T="03">e.g.,</E>
                     tomatoes used in the preparation of fresh salsa or salad bars), are covered by the investigation.
                </P>
                <P>Commercially grown tomatoes, both for the fresh market and for processing, are classified as Lycopersicon esculentum. Important commercial varieties of fresh tomatoes include common round, cherry, grape, plum, greenhouse, and pear tomatoes, all of which are covered by this investigation.</P>
                <P>Tomatoes imported from Mexico covered by this investigation are classified under the following subheading of the Harmonized Tariff Schedule of the United States (HTSUS), according to the season of importation: 0702. Although the HTSUS numbers are provided for convenience and customs purposes, the written description of the scope of this investigation is dispositive.</P>
                <HD SOURCE="HD1">Termination of Suspension Agreement and Continuation of the AD Investigation</HD>
                <P>
                    In accordance with Section VI.B of the 2013 Agreement, Commerce is withdrawing from the 2013 Agreement, effective May 7, 2019, which is 90 days after our February 6, 2019 notice to the signatories. Accordingly, Commerce is terminating the 2013 Agreement, effective May 7, 2019, and continuing the underlying AD investigation. The statute does not identify the timing for completion of the investigation in this particular scenario. Therefore, we are looking to section 734(i)(1)(B) of the Tariff Act of 1930, as amended (the Act), for guidance. Consistent with section 734(i)(1)(B) of the Act, Commerce will continue the investigation as if it had published the affirmative preliminary determination under section 733(b) of the Act on the effective date of the termination, May 7, 2019. As explained in its 
                    <E T="03">1996 Preliminary Determination,</E>
                     Commerce previously postponed the final determination until the 135th day after the date of the preliminary determination.
                    <SU>24</SU>
                    <FTREF/>
                     Commerce, therefore, intends to issue its final determination in the investigation 135 days after the effective date of withdrawal from and termination of the 2013 Agreement, 
                    <E T="03">i.e.,</E>
                     by September 19, 2019, unless a new suspension agreement becomes effective prior to or on this date. If Commerce and producers/exporters accounting for substantially all imports of fresh tomatoes from Mexico sign a new suspension agreement, following the notice and comment period provided in accordance with section 734(c) of the Act, the continued investigation will be suspended.
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See 1996 Preliminary Determination</E>
                         at 56609.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Rescission of the Administrative Review</HD>
                <P>
                    On May 2, 2018, Commerce initiated an administrative review of the 2013 Agreement for the period March 1, 2017 through February 28, 2018.
                    <SU>25</SU>
                    <FTREF/>
                     Because Commerce has terminated the 2013 Agreement, there is no longer an agreement of which to conduct an administrative review. Therefore, Commerce is rescinding the administrative review of the 2013 Agreement, effective on the date of termination of the 2013 Agreement, 
                    <E T="03">i.e.,</E>
                     May 7, 2019.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See Initiation of Administrative Review,</E>
                         83 FR at 19217.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Period of Investigation</HD>
                <P>
                    The original period of investigation was March 1, 1995, through February 29, 1996. Due to the unusual procedural posture of this proceeding, in which we are terminating a suspension agreement and continuing an investigation that covers a period of investigation that dates back more than 23 years, 
                    <PRTPAGE P="20861"/>
                    Commerce will be requesting information corresponding to the most recent four full quarters, 
                    <E T="03">i.e.,</E>
                     April 1, 2018 through March 31, 2019.
                </P>
                <HD SOURCE="HD1">Respondent Selection</HD>
                <P>In light of the unusual procedural posture of this proceeding, Commerce finds it appropriate to reconsider respondent selection. Commerce intends to evaluate U.S. Customs and Border Protection (CBP) data for U.S. imports of fresh tomatoes from Mexico for the most recent four quarters under the appropriate Harmonized Tariff Schedule of the United States (HTSUS) numbers listed in the “Scope of the Investigation” section above and select mandatory respondents in accordance with section 777A(c) of the Act.</P>
                <P>We are releasing CBP data under Administrative Protective Order (APO) to all parties with access to information protected by APO concurrently with the issuance of this notice.</P>
                <P>
                    Interested parties wishing to comment on the CBP data must do so within two business days of the publication date of this notice. Comments must be filed electronically using Commerce's electronic records system, ACCESS at 
                    <E T="03">http://access.trade.gov</E>
                     in accordance with 19 CFR 351.303.
                    <SU>26</SU>
                    <FTREF/>
                     An electronically filed document must be received successfully in its entirety by ACCESS no later than 5:00 p.m. Eastern Time, two business days after the publication date of this notice.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See Antidumping and Countervailing Duty Proceedings: Electronic Filing Procedures; Administrative Protective Order Procedures,</E>
                         76 FR 39263 (July 6, 2011).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Suspension of Liquidation</HD>
                <P>Commerce will instruct U.S. Customs and Border Protection (CBP) to suspend liquidation of entries of fresh tomatoes from Mexico that are entered, or withdrawn from warehouse, for consumption on or after May 7, 2019, the effective date of the termination of the 2013 Suspension Agreement. CBP shall require antidumping duty cash deposits or bonds for entries of the subject merchandise based on the preliminary dumping margins, which are as follows:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,p7,7/8,i1" CDEF="s10,9">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Grower/exporter</CHED>
                        <CHED H="1">
                            Weighted-
                            <LI>average</LI>
                            <LI>percentage margin</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">San Vincente Camalu</ENT>
                        <ENT>4.16</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Exportadora Agricola Sacramento S.A. de C.V.
                            <SU>27</SU>
                        </ENT>
                        <ENT>11.89</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arturo Lomeli Villalobas S.A. de C.V</ENT>
                        <ENT>26.97</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Eco-Cultivos S.A. de C.V</ENT>
                        <ENT>188.45</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Productora Agricola Industrial del Noroeste, S.A. de C.V.
                            <SU>28</SU>
                        </ENT>
                        <ENT>10.26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Administradora Horticola del Tamazula</ENT>
                        <ENT>28.30</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Agricola Yory, S. de P.R. de R.I</ENT>
                        <ENT>11.95</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">All Others</ENT>
                        <ENT>17.56</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">International Trade Commission</HD>
                <P>
                    Commerce will notify 
                    <FTREF/>
                    the International Trade Commission (ITC) of its withdrawal from and termination of the 2013 Suspension Agreement and continuation of the AD investigation. If Commerce makes a final affirmative determination, the ITC is scheduled to make its final determination concerning injury within 45 days after publication of Commerce's final determination. If both Commerce's and the ITC's final determinations are affirmative, Commerce will issue an AD order.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         Exportadora Agricola Sacramento S.A. de C.V. (Sacramento) is formerly known as Ernesto Fernando Echavarria Salazar Grupo Solidario. 
                        <E T="03">See</E>
                         Commerce's verification agenda to Sacramento dated October 11, 2002, and the Sacramento verification report dated November 12, 2002, at Home Market Exhibit 1.
                    </P>
                    <P>
                        <SU>28</SU>
                         Productora Agricola Industrial del Noroeste, S.A. de C.V. (Noroeste) was formerly known as Ranchos Los Pinos S. de R.L. de C.V. 
                        <E T="03">See</E>
                         Noroeste's entry of appearance dated October 18, 2002, the Noroeste cost verification report dated November 12, 2002, at 3, and the Noroeste sales verification report dated November 13, 2002, at 1, 4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Filing Requirements</HD>
                <P>
                    All submissions to Commerce must be filed electronically using Enforcement and Compliance's Antidumping Duty and Countervailing Duty Centralized Electronic Service System (ACCESS).
                    <SU>29</SU>
                    <FTREF/>
                     An electronically filed document must be received successfully in its entirety by the time and date it is due. Documents exempted from the electronic submission requirements must be filed manually (
                    <E T="03">i.e.,</E>
                     in paper form) with Enforcement and Compliance's APO/Dockets Unit, Room 18022, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230, and stamped with the date and time of receipt by the applicable deadlines.
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See Antidumping and Countervailing Duty Proceedings: Electronic Filing Procedures; Administrative Protective Order Procedures,</E>
                         76 FR 39263 (July 6, 2011); 
                        <E T="03">see also Enforcement and Compliance; Change of Electronic Filing System Name,</E>
                         79 FR 69046 (November 20, 2014) for details of Commerce's electronic filing requirements, effective August 5, 2011. Information on help using ACCESS can be found at 
                        <E T="03">https://access.trade.gov/</E>
                        help.aspx and a handbook can be found at 
                        <E T="03">https://access.trade.gov/help/Handbook%20on%20Electronic%20Filling%20Procedures.pdf.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Certification Requirements</HD>
                <P>
                    Any party submitting factual information in an AD or CVD proceeding must certify to the accuracy and completeness of that information.
                    <SU>30</SU>
                    <FTREF/>
                     Parties must use the certification formats provided in 19 CFR 351.303(g).
                    <SU>31</SU>
                    <FTREF/>
                     Commerce intends to reject factual submissions if the submitting party does not comply with the applicable revised certification requirements.
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         
                        <E T="03">See</E>
                         section 782(b) of the Act.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">See also Certification of Factual Information to Import Administration During Antidumping and Countervailing Duty Proceedings,</E>
                         78 FR 42678 (July 17, 2013) (Final Rule). Answers to frequently asked questions regarding the Final Rule are available at 
                        <E T="03">http://enforcement.trade.gov/tlei/notices/factual_info_final_rule_FAQ_07172013.pdf.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Administrative Protective Order Access and Letters of Appearance</HD>
                <P>
                    Commerce will issue new administrative protective orders (APO) for the continued investigation that will supersede the previously issued firm-specific APOs. Those authorized applicants that were granted APOs during the original investigation, as indicated in the most recent APO service list on Commerce's website, will continue to have access to business proprietary information under APO. Any new APO applications or necessary amendments for changes in staff under the pre-existing APOs should be submitted promptly, and in accordance with the procedures outlined in Commerce's regulations at 19 CFR 351.305. These applications must be filed electronically using ACCESS at 
                    <E T="03">http://access.trade.gov.</E>
                     Those procedures apply to this continued investigation. Parties wishing to participate in this continued investigation should ensure that they meet the requirements of these procedures, 
                    <E T="03">e.g.,</E>
                     the filing of separate letters of appearance as discussed at 19 CFR 351.103(d).
                </P>
                <P>This determination is issued and published in accordance with section 733(f) and 777(i)(1) of the Act.</P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Jeffrey I. Kessler,</NAME>
                    <TITLE>Assistant Secretary for Enforcement and Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09786 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="20862"/>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <RIN>RIN 0648-GAR-A002</RIN>
                <SUBJECT>Atlantic Coastal Fisheries Cooperative Management Act Provisions; General Provisions for Domestic Fisheries; Application for Exempted Fishing Permits</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The NMFS Assistant Regional Administrator for Sustainable Fisheries, Greater Atlantic Region, has made a preliminary determination that an Exempted Fishing Permit application contains all of the required information and warrants further consideration. This Exempted Fishing Permit would allow five commercial lobster vessels to participate in a lobster growth and abundance study, under the direction of Massachusetts Division of Marine Fisheries in state waters off the coast of Massachusetts.</P>
                    <P>Regulations under the Magnuson-Stevens Fishery Conservation and Management Act and the Atlantic Coastal Fisheries Cooperative Management Act require publication of this notice to provide interested parties the opportunity to comment on Exempted Fishing Permit applications.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before May 28, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit written comments by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Email: NMFS.GAR.EFP@noaa.gov.</E>
                         Include in the subject line “Comments on MA DMF Lobster Study EFP.”
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Michael Pentony, Regional Administrator, NMFS, Greater Atlantic Regional Fisheries Office, 55 Great Republic Drive, Gloucester, MA 01930. Mark the outside of the envelope “Comments on MA DMF Lobster Study EFP.”
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Laura Hansen, Fishery Management Specialist, 978-281-9225.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Massachusetts Division of Marine Fisheries (MA DMF) submitted a complete renewal application for an Exempted Fishing Permit (EFP) to conduct a lobster abundance survey that Federal regulations would otherwise restrict. The purpose of this study is to provide fishery-independent data on lobster growth and abundance in Massachusetts state waters of statistical areas 514 and 538.</P>
                <P>This survey has occurred annually since 2006 in Massachusetts state waters. On average, 15,604 lobsters per year were sampled from 2007-2016. The EFP would authorize the five participating vessels to deploy three standard and three ventless traps per six-pot trawl. Stations would be sampled twice per month from June to October 2019. Sampling trips would occur after a soak time of 3 to 5 days and at least one MA DMF scientist would be on board for the sampling trips. MA DMF personnel would not be on board when traps are baited and deployed. All gear would be Atlantic Large Whale Take Reduction Plan compliant. Survey traps will be separate from each vessel's commercial lobster traps and would be tagged as, “MADMF Research Traps.”</P>
                <P>All catch during sampling trips would be retained temporarily to collect biological data. MA DMF staff may collect lobster and/or Jonah crab, including undersized, oversized,v-notched, and egg-bearing lobsters. Collected samples would be used for research projects on growth and maturity. No catch from the experimental trips would be landed for sale.</P>
                <P>If approved, MA DMF may request minor modifications and extensions to the EFP throughout the study. EFP modifications and extensions may be granted without further notice if they are deemed essential to facilitate completion of the proposed research and have minimal impacts that do not change the scope or impact of the initially approved EFP request. Any fishing activity conducted outside the scope of the exempted fishing activity would be prohibited.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        16 U.S.C. 1801 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: May 8, 2019.</DATED>
                    <NAME>Alan D. Risenhoover,</NAME>
                    <TITLE>Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09787 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Telecommunications and Information Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Proposed Information Collection; Comment Request; State and Local Implementation Grant Program 2.0 Closeout Documentation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Telecommunications and Information Administration, Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Commerce, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on proposed and/or continuing information collections, as required by the Paperwork Reduction Act of 1995.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments must be submitted on or before July 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all written comments to Jennifer Jessup, Departmental Paperwork Clearance Officer, Department of Commerce, (202) 482-0336, Department of Commerce, Room 6612, 1401 Constitution Avenue NW, Washington, DC 20230 (or via email at 
                        <E T="03">PRAcomments@doc.gov</E>
                        ).
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of the information collection instruments and instructions should be sent to Natalie Romanoff, Program Director, State and Local Implementation Grant Program 2.0, National Telecommunications and Information Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Room 4078, Washington, DC 20230 (or via email at 
                        <E T="03">nromanoff@ntia.gov</E>
                         or phone 202-482-2236).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Abstract</HD>
                <P>
                    The Middle Class Tax Relief and Job Creation Act of 2012 (Act) (Pub. L. 112-96, H.R. 3630, 126 Stat. 156) was enacted February 22, 2012.
                    <SU>1</SU>
                    <FTREF/>
                     The Act meets a long-standing national priority and critical infrastructure need to create a single, interoperable, nationwide public safety broadband network (NPSBN) that allows law enforcement officers, fire fighters, emergency medical service professionals, and other public safety officials to effectively communicate with each other across 
                    <PRTPAGE P="20863"/>
                    agencies and jurisdictions. Public safety responders have been hindered in their ability to respond in a crisis situation due to incompatible communications networks and often outdated communications equipment. Therefore, the design and deployment of this NPSBN, established by the Act, is critical to provide emergency responders the ability to communicate on a secure, reliable, and dedicated interoperable network during emergencies and to use technology to improve response time, keep communities safe, and save lives.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Middle Class Tax Relief and Job Creation Act of 2012, Public Law 112-96, 126 Stat. 156 (2012) (Act) (codified at 47 U.S.C. 1401 
                        <E T="03">et seq.</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    The Act established the First Responder Network Authority (FirstNet) as an independent authority within the National Telecommunications and Information Administration (NTIA) and authorized it to take all actions necessary to ensure the design, construction, and operation of a nationwide NPSBN, based on a single, national network architecture.
                    <SU>2</SU>
                    <FTREF/>
                     FirstNet's responsibilities are, at a minimum, to ensure nationwide standards for the use of and access to the network; issue open, transparent, and competitive requests for proposals (RFPs) to build, operate, and maintain the network; encourage these RFPs to leverage, to the maximum extent economically desirable, existing commercial wireless infrastructure to speed deployment of the network; and oversee contracts with non-federal entities to build, operate, and maintain the network.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         47 U.S.C. 1424, 1426(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         47 U.S.C. 1426(b)(1)(A)-(D).
                    </P>
                </FTNT>
                <P>
                    The Act also charged NTIA with establishing a grant program, the State and Local Implementation Grant Program (SLIGP), to assist State, regional, tribal, and local jurisdictions with identifying, planning, and implementing the most efficient and effective means to use and integrate the infrastructure, equipment, and other architecture associated with the NPSBN to satisfy the wireless broadband and data services needs of their jurisdictions.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         47 U.S.C. 1442(a).
                    </P>
                </FTNT>
                <P>
                    The Act's framework outlined that FirstNet closely coordinates its activities with State, regional, tribal, and local governments and imposed a statutory requirement that FirstNet consult with these entities as it takes all actions necessary to build, deploy, and operate the NPSBN.
                    <SU>5</SU>
                    <FTREF/>
                     Specifically, the Act requires FirstNet to consult with state, regional, tribal, and local governments about the distribution and expenditure of any amounts required to carry out its responsibilities to plan, build, operate, and maintain the NPSBN.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         47 U.S.C. 1422(b)(2)(B).
                    </P>
                </FTNT>
                <P>
                    Additionally, the Act specifies that these required consultations occur between FirstNet and the single point of contact (SPOC) that the state designated in its original SLIGP grant application.
                    <SU>6</SU>
                    <FTREF/>
                     The original SLIGP award provided recipients with funding to support their engagement in consultations as required of FirstNet under the Act.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         47 U.S.C. 1426(c)(2)(B); 47 U.S.C. 1442(d).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">SLIGP 2.0</HD>
                <P>In 2013, NTIA originally awarded $116.5 million in grant funds to 54 state and territorial recipients between July 2013 and June 2014. The original grants expired February 28, 2018, and many recipients spent less than expected, leaving leftover funds. NTIA leveraged excess funds of $33.3 million from the original SLIGP grants to make a second round of grant awards, SLIGP 2.0. The SLIGP 2.0 provides funding to assist State, regional, tribal, and local jurisdictions to engage effectively with FirstNet and provide it with information needed to continue with planning the NPSBN in an effective and timely manner, as required by the Act.</P>
                <P>SLIGP 2.0 recipients' periods of performance are currently scheduled to end in early 2020. Following the award end date, recipients will be required to complete grant closeout activities within 90 days. The purpose of closeout is to capture a final account of recipient activities and how these activities contributed to overall program goals. To ensure effective grant oversight and management, NTIA developed a closeout report form for SLIGP 2.0 recipients to complete as part of post-award monitoring and closeout activities at the end of the period of performance. The closeout report form serves as a summary of grant-funded recipient activities over the entire award period and ensures that recipients comply with all necessary closeout procedures. The closeout report form will ask recipients to aggregate their cumulative progress toward program priority areas identified in their quarterly performance progress reports (PPRs), including individuals sent to broadband conferences, staff hired, contracts executed, governance meetings held, and stakeholder events convened. Recipients will also be asked to report on their cumulative expenditures throughout the period of performance in each object class category, including personnel, fringe, travel, equipment, materials/supplies, contractual, other, and indirect costs.</P>
                <P>NTIA will use the collection of information to monitor and evaluate how SLIGP 2.0 grant recipients are achieving the core purposes of the program established by the Act. The information collected in the closeout report form will ensure that final data effectively assesses the success of SLIGP 2.0 recipients in implementing their project goals. The publication of this notice allows NTIA to begin the process to obtain the approval for the standard three years.</P>
                <HD SOURCE="HD1">II. Method of Collection</HD>
                <P>Recipients will complete the closeout report and submit the form to the SLIGP 2.0 Program Office via email.</P>
                <HD SOURCE="HD1">III. Data</HD>
                <P>
                    <E T="03">OMB Control Number:</E>
                     None.
                </P>
                <P>
                    <E T="03">Form Number(s):</E>
                     None.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Regular submission.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     State, regional, local, and tribal government organizations.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Once (at the end of the period of performance).
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     46.
                </P>
                <P>
                    <E T="03">Average Time per Response:</E>
                     Final closeout report, 25 hours.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     1,150 hours.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Cost to Public:</E>
                     $53.176.
                </P>
                <HD SOURCE="HD1">IV. Request for Comments</HD>
                <P>
                    <E T="03">Comments are invited on:</E>
                     (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; (b) the accuracy of the agency's estimate of the burden (including hours and cost) of the proposed collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology.
                </P>
                <P>Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval of this information collection; they will also become a matter of public record.</P>
                <SIG>
                    <NAME>Sheleen Dumas,</NAME>
                    <TITLE>Departmental Lead PRA Officer, Office of the Chief Information Officer, Commerce Department.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09766 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-60-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="20864"/>
                <AGENCY TYPE="N">BUREAU OF CONSUMER FINANCIAL PROTECTION</AGENCY>
                <DEPDOC>[Docket No. CFPB-2019-0026]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Consumer Financial Protection.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995 (PRA), the Bureau of Consumer Financial Protection (Bureau) is requesting to renew with change an existing information collection titled, “Policy to Encourage Trial Disclosure Programs.”</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments are encouraged and must be received on or before July 12, 2019 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by the title of the information collection, OMB Control Number (see below), and docket number (see above), by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Electronic:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Email: PRA_Comments@cfpb.gov.</E>
                         Include Docket No. CFPB-2019-0026 in the subject line of the message.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Comment Intake, Bureau of Consumer Financial Protection (Attention: PRA Office), 1700 G Street NW, Washington, DC 20552.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         Comment Intake, Bureau of Consumer Financial Protection (Attention: PRA Office), 1700 G Street NW, Washington, DC 20552.
                    </P>
                    <P>
                        <E T="03">Please note that comments submitted after the comment period will not be accepted.</E>
                         In general, all comments received will become public records, including any personal information provided. Sensitive personal information, such as account numbers or Social Security numbers, should not be included.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Documentation prepared in support of this information collection request is available at 
                        <E T="03">www.regulations.gov.</E>
                         Requests for additional information should be directed to Darrin King, PRA Officer, at (202) 435-9575, or email: 
                        <E T="03">CFPB_PRA@cfpb.gov.</E>
                         If you require this document in an alternative electronic format, please contact 
                        <E T="03">CFPB_Accessibility@cfpb.gov.</E>
                         Please do not submit comments to these email boxes.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title of Collection:</E>
                     Policy to Encourage Trial Disclosure Programs.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3170-0039.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of a currently approved information collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Businesses and other for-profit entities.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     10.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     100.
                </P>
                <P>
                    <E T="03">Abstract</E>
                     In subsection 1032(e) of the Dodd-Frank Act, 12 U.S.C. 5532(e), Congress gave the Bureau authority to provide certain legal protections to companies to conduct trial disclosure programs. This authority can be used to help further the Bureau's statutory objective, stated in subsection 1021(b)(5) of the Act, to “facilitate access and innovation” in the “markets for consumer financial products and services.” In accordance with this authority, the Bureau published its Policy to Encourage Trial Disclosure Programs (Policy) on October 10, 2013 (78 FR 64389). Under the Policy, an application for permission to conduct a trial disclosure program should include certain information. A supporting statement for the existing information collections under this control number may be found here at 
                    <E T="03">https://www.reginfo.gov/public/do/PRAViewDocument?ref_nbr=201605-3170-011.</E>
                     In addition the Bureau has published a notice in the 
                    <E T="04">Federal Register</E>
                     on September 10, 2018, 83 FR 45574 proposing revisions to the Policy (Proposal). The Proposal and comments thereon may be viewed at 
                    <E T="03">https://www.regulations.gov/docket?D=CFPB-2018-0023.</E>
                     The Bureau is currently reviewing those comments in as it contemplates any changes or revisions to the Proposal. 
                </P>
                <P>
                    <E T="03">Request for comments:</E>
                     Comments are invited on: (a) Whether the collection of information is necessary for the proper performance of the functions of the Bureau, including whether the information will have practical utility; (b) The accuracy of the Bureau's estimate of the burden of the collection of information, including the validity of the methods and the assumptions used; (c) Ways to enhance the quality, utility, and clarity of the information to be collected; and (d) Ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology. Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record.
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Darrin A. King,</NAME>
                    <TITLE>Paperwork Reduction Act Officer, Bureau of Consumer Financial Protection.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09720 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4810-AM-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">BUREAU OF CONSUMER FINANCIAL PROTECTION</AGENCY>
                <DEPDOC>[Docket No. CFPB-2019-0025]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Consumer Financial Protection.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995 (PRA), the Bureau of Consumer Financial Protection (Bureau) is requesting to renew the Office of Management and Budget (OMB) approval for an existing information collection titled, “Equal Access to Justice Act.”</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments are encouraged and must be received on or before July 12, 2019 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by the title of the information collection, OMB Control Number (see below), and docket number (see above), by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Electronic:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Email: PRA_Comments@cfpb.gov.</E>
                         Include Docket No. CFPB-2019-0025 in the subject line of the message.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Comment intake, Bureau of Consumer Financial Protection (Attention: PRA Office), 1700 G Street NW, Washington, DC 20552.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         Comment intake, Bureau of Consumer Financial Protection (Attention: PRA Office), 1700 G Street NW, Washington, DC 20552.
                    </P>
                    <P>
                        <E T="03">Please note that comments submitted after the comment period will not be accepted.</E>
                         In general, all comments received will become public records, including any personal information provided. Sensitive personal information, such as account numbers or Social Security numbers, should not be included.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Documentation prepared in support of this information collection request is available at 
                        <E T="03">www.regulations.gov.</E>
                         Requests for additional information should be directed to Darrin King, PRA Officer, at (202) 435-9575, or email: 
                        <E T="03">CFPB_PRA@cfpb.gov.</E>
                         If you require this 
                        <PRTPAGE P="20865"/>
                        document in an alternative electronic format, please contact 
                        <E T="03">CFPB_Accessibility@cfpb.gov.</E>
                         Please do not submit comments to these email boxes.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title of Collection:</E>
                     Equal Access to Justice Act.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3170-0040.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Renewal without change of an approved information collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or Households.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     3.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     15.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Equal Access to Justice Act (the Act) provides for payment of fees and expenses to eligible parties who have prevailed against the Bureau in certain administrative proceedings. In order to obtain an award, the statute and associated regulations require the filing of an application that shows that the party is a prevailing party and is eligible to receive an award under the Act. The Bureau regulations implementing the Act require the collection of information related to the application for an award are in 12 CFR part 1071, subparts B, C. This is a routine request for OMB to renew its approval of the collections of information currently approved under this OMB control number. The Bureau is not proposing any new or revised collections of information pursuant to this request.
                </P>
                <P>
                    <E T="03">Request for Comments:</E>
                     Comments are invited on: (a) Whether the collection of information is necessary for the proper performance of the functions of the Bureau, including whether the information will have practical utility; (b) The accuracy of the Bureau's estimate of the burden of the collection of information, including the validity of the methods and the assumptions used; (c) Ways to enhance the quality, utility, and clarity of the information to be collected; and (d) Ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology. Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record.
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Darrin A. King,</NAME>
                    <TITLE>Paperwork Reduction Act Officer, Bureau of Consumer Financial Protection.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09723 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4810-AM-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>Board of Visitors, National Defense University; Notice of Federal Advisory Committee Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Chairman Joint Chiefs of Staff, Department of Defense.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Federal Advisory Committee meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Defense (DoD) is publishing this notice to announce that the following Federal Advisory Committee meeting of the Board of Visitors, National Defense University will take place.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Tuesday, May 21, 2019 from 12:30 p.m. to 4:15 p.m. and Wednesday, May 22, 2019 from 11 a.m. to 11:45 a.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Normandy Hall, Joint Forces Staff College, 7800 Hampton Blvd., Naval Support Activity Hampton Roads, Norfolk, VA 23511-1702.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Dr. Brian R. Shaw, (202) 685-4685 (Voice), (202) 685-3920 (Facsimile), 
                        <E T="03">brian.r.shaw8.civ@mail.mil; brian.r.shaw.civ@ndu.edu; joycelyn.a.stevens.civ@mail.mil; stevensj7@ndu.edu</E>
                         (Email). Mailing address is National Defense University, Fort McNair Washington, DC 20319-5066. Website: 
                        <E T="03">http://www.ndu.edu/About/Board-of-Visitors/</E>
                        . The most up-to-date changes to the meeting agenda can be found on the website.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Due to circumstances beyond the control of the Department of Defense (DoD) and the Designated Federal Officer, the Board of Visitors, National Defense University was unable to provide public notification required by 41 CFR 102-3.150(a) concerning the meeting on May 21, 2019 through May 22, 2019 of the Board of Visitors, National Defense University. Accordingly, the Advisory Committee Management Officer for the Department of Defense, pursuant to 41 CFR 102-3.150(b), waives the 15-calendar day notification requirement.</P>
                <P>This meeting is being held under the provisions of the Federal Advisory Committee Act (FACA) of 1972 (5 U.S.C., Appendix, as amended), the Government in the Sunshine Act of 1976 (5 U.S.C. 552b, as amended), and 41 CFR 102-3.140 and 102-3.150.</P>
                <P>Pursuant to 5 U.S.C. 552b and 41 CFR 102-3.140 through 102-3.165, and the availability of space, this meeting is open to the public.</P>
                <P>
                    <E T="03">Purpose of the Meeting:</E>
                     The purpose of the meeting will include discussion on accreditation compliance, organizational management, strategic planning, resource management, and other matters of interest to the National Defense University.
                </P>
                <P>
                    <E T="03">Agenda:</E>
                     Tuesday, May 21, 2019 from 12:30 p.m. to 4:15 p.m.: Welcome and Administrative Notes; State of the University Address; Review of Past Meeting Minutes and the Chairman of the Joint Chiefs of Staff's Response to the Letter from the Board of Visitors; Updates on Information and Educational Technology, NDU Facilities and the NDU Budget and Project 2024. Wednesday, May 22, 2019 from 11 a.m. to 11:45 a.m.: Public Comment; Board of Visitors Member Feedback and Wrap-up and Closing Remarks.
                </P>
                <P>
                    <E T="03">Meeting Accessibility:</E>
                     Limited space is available for observers and will be allocated on a first come, first served basis. Meeting location is handicap accessible. Visitors must enter Naval Support Activity Hampton Roads via Gate A from Terminal Blvd. &amp; Meredith St.
                </P>
                <P>
                    <E T="03">Base Access Requirements:</E>
                     All visitors without U.S. Department of Defense Common Access Cards (CACs) must be vetted in advance in order to gain entry onto the base. Visitors must complete and sign, the Department of the Navy Local Population ID Card/Base Access Pass Registration (Form SECNAV 5512). To download the form, please visit 
                    <E T="03">https://forms.documentservices.dla.mil/order/</E>
                    .
                </P>
                <P>
                    Once on the site, to locate SECNAV 5512/1, go to the Search Criteria (top of page). Click the down arrow to choose “Form Number” and type in “SECNAV 5512”. When the list comes up, either open the form by clicking on the disc icon to the left of the form and save to your desktop; or right-click on the disc icon, then save the link to save the form to your desktop. Please fax the completed form to CDR Brandy McNabb, Operations Officer at (757) 443-6033. 
                    <E T="03">Please note vetting may take 5-14 working days.</E>
                </P>
                <P>
                    To find out if you have been cleared for base access go to CNIC website at 
                    <E T="03">https://www.cnic.navy.mil/regions/cnrma.html.</E>
                     Go to popular links bottom right corner, click on DBIDS/Day Visitor list. Visitors who successfully complete vetting and identity proofing will be issued a DBIDS credential or paper access pass.
                </P>
                <P>
                    The pass can be picked up the day prior or morning of the meeting at the Pass &amp; ID Office at Norfolk Naval Station, 9040 Hampton Blvd., CD9, Norfolk, VA 23511. Please bring your ID. Additional supporting documents (including directions to Normandy Hall) are available at 
                    <E T="03">http://www.ndu.edu/About/Board-of-Visitors/.</E>
                     For questions 
                    <PRTPAGE P="20866"/>
                    or additional information, you may contact CDR McNabb at (757) 443-6269.
                </P>
                <P>
                    <E T="03">Vehicle Search:</E>
                     Non-DoD/nonfederally affiliated visitors' vehicles are subject to search.
                </P>
                <P>
                    <E T="03">Building Access to Normandy Hall:</E>
                     Directions to Normandy Hall will be provided at Gate A, Naval Support Activity Hampton Roads. Visitors should report to the Front Security Desk in the lobby and from there, they will be directed to the meeting room.
                </P>
                <P>
                    <E T="03">Written Statements:</E>
                     Pursuant to 41 CFR 102-3.105(j) and 102-3.140, and section 10(a)(3) of the Federal Advisory Committee Act of 1972, written statements to the committee may be submitted to the committee at any time or in response to a stated planned meeting agenda by FAX or email to Ms. Joycelyn Stevens at (202) 685-0079, Fax (202) 685-3920 or 
                    <E T="03">StevensJ7@ndu.edu.</E>
                </P>
                <SIG>
                    <DATED>Dated: May 8, 2019.</DATED>
                    <NAME>Aaron T. Siegel,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09780 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 5001-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE </AGENCY>
                <SUBAGY>Office of the Secretary </SUBAGY>
                <SUBJECT>Defense Business Board; Notice of Federal Advisory Committee Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Chief Management Officer, Department of Defense. ACTION: Notice of Federal Advisory Committee meeting. </P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Defense (DoD) is publishing this notice to announce that the following Federal Advisory Committee meeting of the Defense Business Board (“the Board”) will take place. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Closed to the public Wednesday, May 8, 2019 from 7:20 a.m. to 9:45 a.m. Open to the public Wednesday, May 8, 2019 from 10:00 a.m. to 11:30 a.m. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The closed and open portions of the meeting will be in Room 3E869 in the Pentagon, Washington, DC. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Roma Laster, (703) 695-7563 (Voice), (703) 614-4365 (Facsimile), 
                        <E T="03">roma.k.laster.civ@mail.mil</E>
                         (Email). Mailing address is Defense Business Board, 1155 Defense Pentagon, Room 5B1088A, Washington, DC 20301-1155. Website: 
                        <E T="03">http://dbb.defense.gov/.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Due to circumstances beyond the control of the Department of Defense (DoD) and the Designated Federal Officer, the Defense Business Board was unable to provide public notification required by 41 CFR 102-3.150(a) concerning its May 8, 2019 meeting of the Defense Business Board. Accordingly, the Advisory Committee Management Officer for the Department of Defense, pursuant to 41 CFR 102-3.150(b), waives the 15-calendar day notification requirement.</P>
                <P>This meeting is being held under the provisions of the Federal Advisory Committee Act (FACA) (5 U.S.C. Appendix), the Government in the Sunshine Act (5 U.S.C. 552b), and 41 CFR 102-3.140 and 102-3.150. </P>
                <P>
                    <E T="03">Purpose of the Meeting:</E>
                     The mission of the Board is to examine and advise the Secretary of Defense on overall DoD management and governance. The Board provides independent advice which reflects an outside private sector perspective on proven and effective best business practices that can be applied to DoD. 
                </P>
                <P>
                    <E T="03">Agenda:</E>
                     The meeting will begin in a Closed Session where the Board will receive a classified briefing on 5G technology and a classified Indo-Pacific foreign area briefing. The meeting will then move to a Public Session where the Board will provide an update on current DBB activities; present, deliberate, and vote on its Defense Acquisition Industry-Government Exchange study; and provide an overview of the Board's support to DoD reform efforts.
                </P>
                <P>
                    <E T="03">Meeting Agenda:</E>
                </P>
                <HD SOURCE="HD3">Closed Session</HD>
                <FP SOURCE="FP1-2">7:20 a.m.-8:15 a.m.—(TS) 5G Technology Brief</FP>
                <FP SOURCE="FP1-2">8:15 a.m.-9:45 a.m.—(TS) Indo-Pacific Foreign Area Brief</FP>
                <HD SOURCE="HD3">Public Session</HD>
                <FP SOURCE="FP-2">10:00 a.m.-10:05 a.m.—Opening remarks—Board Designated Federal Officer</FP>
                <FP SOURCE="FP-2">10:05 a.m.-10:20 a.m.—Update on Current Board Activities</FP>
                <FP SOURCE="FP-2">10:20 a.m.-11:00 a.m.—DBB Study: “Defense Acquisition Industry-Government Exchange”</FP>
                <FP SOURCE="FP-2">11:00 a.m.-11:30 a.m.—Overview of Board Support to DoD Reform Efforts</FP>
                <FP SOURCE="FP-2">11:30 a.m.-Closing remarks—Board Designated Federal Officer</FP>
                <P>
                    <E T="03">Meeting Accessibility:</E>
                     In accordance with section 10(d) of the FACA and 41 CFR 102-3.155, the DoD has determined that the Board's meeting will be partially closed to the public. Specifically, the CMO, in consultation with the DoD Office of General Counsel, has determined in writing that a portion of the meeting will be closed to the public because it will consider classified information and other matters covered by 5 U.S.C. 552b(c)(1). The 5 U.S.C. 552b(c)(1) determination is based on the consideration that the 5G technology and foreign area briefings will involve classified matters of national defense or foreign policy. Such classified material is so intertwined with the unclassified material that it cannot reasonably be segregated into separate discussions without disclosing secret or otherwise classified material.
                </P>
                <P>Pursuant to FACA and 41 CFR 102-3.140, that portion of the meeting from 10:00 a.m. to 11:30 a.m. is open to the public. Public attendees requiring escort should arrive at the Pentagon Visitor Center (adjacent to the Pentagon Metro Entrance) with sufficient time to complete security screening no later than 9:15 a.m. on May 8, 2019. To complete security screening, come prepared to present two forms of identification one of which must be a pictured identification card.</P>
                <P>
                    <E T="03">Written Statements:</E>
                     Written comments may be submitted to the Designated Federal Officer (DFO) via email to mailbox address: 
                    <E T="03">osd.pentagon.odam.mbx.defense-business-board@mail.mil</E>
                     in either Adobe Acrobat or Microsoft Word format. Please note that since the Board operates under the provisions of the FACA, all submitted comments and public presentations will be treated as public documents and will be made available for public inspection, including, but not limited to, being posted on the Board's website.
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Aaron T. Siegel, </NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09737 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 5001-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEFENSE NUCLEAR FACILITIES SAFETY BOARD</AGENCY>
                <SUBJECT>Sunshine Act Meetings</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND DATE:</HD>
                    <P>1:00 p.m.-3:00 p.m., May 22, 2019.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE: Defense</HD>
                    <P>Nuclear Facilities Safety Board, 625 Indiana Avenue NW, Suite 700, Washington, DC 20004.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS:</HD>
                    <P>
                        Closed. During the closed meeting, the Board Members will discuss issues dealing with potential Recommendations to the Secretary of Energy. The Board is invoking the exemptions to close a meeting described in 5 U.S.C. 552b(c)(3) and (9)(B) and 10 CFR 1704.4(c) and (h). The Board has determined that it is necessary to close the meeting since conducting an open meeting is likely to disclose matters that are specifically exempted from disclosure by statute, and/or be likely to 
                        <PRTPAGE P="20867"/>
                        significantly frustrate implementation of a proposed agency action. In this case, the deliberations will pertain to potential Board Recommendations which, under 42 U.S.C. 2286d(b) and (h)(3), may not be made publicly available until after they have been received by the Secretary of Energy or the President, respectively.
                    </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>
                    <P>
                        The meeting will proceed in accordance with the closed meeting agenda which is posted on the Board's public website at 
                        <E T="03">www.dnfsb.gov.</E>
                         Technical staff may present information to the Board. The Board Members are expected to conduct deliberations regarding potential Recommendations to the Secretary of Energy.
                    </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION:</HD>
                    <P>Glenn Sklar, General Manager, Defense Nuclear Facilities Safety Board, 625 Indiana Avenue NW, Suite 700, Washington, DC 20004-2901, (800) 788-4016. This is a toll-free number.</P>
                </PREAMHD>
                <SIG>
                    <DATED>Dated: May 9, 2019.</DATED>
                    <NAME>Bruce Hamilton,</NAME>
                    <TITLE>Chairman.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09884 Filed 5-9-19; 11:15 am]</FRDOC>
            <BILCOD> BILLING CODE 3670-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
                <DEPDOC>[Docket No. ED-2019-ICCD-0065]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Comment Request; Significant Disproportionality State Survey</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Special Education and Rehabilitative Services (OSERS), 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 of 1995, ED is proposing a new information collection.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested persons are invited to submit comments on or before July 12, 2019.</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-2019-ICCD-0065. 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, ED 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. 
                        <E T="03">Please note that comments submitted by fax or email and those submitted after the comment period will not be accepted.</E>
                         Written requests for information or comments submitted by postal mail or delivery should be addressed to the Director of the Information Collection Clearance Division, U.S. Department of Education, 550 12th Street SW, PCP, Room 9086, Washington, DC 20202-0023.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For specific questions related to collection activities, please contact Mary Louise Dirrigl, 202-245-7324.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Department of Education (ED), 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. ED is soliciting comments on the proposed information collection request (ICR) that is described below. The Department of Education 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>
                     Significant Disproportionality State Survey.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1820-NEW.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     A new information collection.
                </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>
                     50.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Burden Hours:</E>
                     100.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This new collection will collect detailed information on the State's use of the standard methodology, or another methodology based upon risk ratios and risk ratio thresholds, to identify significant disproportionality in the LEAs of the State. The Department will use this information to support States and LEAs in their efforts to comply with the statutory requirement at section 618(d) of the IDEA. Specifically, the collection will include information about the extent to which each State has implemented the standard methodology, and steps necessary for States to be in compliance with the December 2016 regulation, including anticipated obstacles States will face and the extent to which States have considered safeguards to ensure compliance with federal law and the U.S. Constitution. This information will allow the Department to determine the appropriate time and manner for the States to report their standards required under 34 CFR § 300.647(b)(7), and to fulfill its role of monitoring and enforcement for reasonableness under 34 CFR § 300.647(b)(1)(iii).
                </P>
                <SIG>
                    <DATED>Dated: May 8, 2019.</DATED>
                    <NAME>Kate Mullan,</NAME>
                    <TITLE>PRA Coordinator, Information Collection Clearance Program, Information Management Branch, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09811 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4000-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF EDUCATION</AGENCY>
                <DEPDOC>[Docket No.: ED-2019-ICCD-0063</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Comment Request; Educational Opportunity Centers Program (EOC) Annual Performance Report</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Postsecondary Education (OPE), 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 of 1995, ED is proposing an extension of an existing information collection.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested persons are invited to submit comments on or before July 12, 2019.</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-2019-ICCD-0063. 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, 
                        <PRTPAGE P="20868"/>
                        commercial delivery, or hand delivery. If the 
                        <E T="03">regulations.gov</E>
                         site is not available to the public for any reason, ED 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. 
                        <E T="03">Please note that comments submitted by fax or email and those submitted after the comment period will not be accepted.</E>
                         Written requests for information or comments submitted by postal mail or delivery should be addressed to the Director of the Information Collection Clearance Division, U.S. Department of Education, 550 12th Street SW, PCP, Room 9086, Washington, DC 20202-0023.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For specific questions related to collection activities, please contact Rachael Wiley, 202-453-6078.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Department of Education (ED), 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. ED is soliciting comments on the proposed information collection request (ICR) that is described below. The Department of Education 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>
                     Educational Opportunity Centers Program (EOC) Annual Performance Report.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1840-0830.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     An extension of an existing information collection.
                </P>
                <P>
                    <E T="03">Respondents/Affected Public:</E>
                     State, Local, and Tribal Governments; Private Sector.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Responses:</E>
                     140.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Burden Hours:</E>
                     1,120.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Educational Opportunity Centers Program (EOC) grantees must submit the report annually. The report provides the Department of Education with information needed to evaluate a grantee's performance and compliance with program requirements and to award prior experience points in accordance with the program regulations. The data collection is also aggregated to provide information on project participants and program outcomes.
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Kate Mullan,</NAME>
                    <TITLE>PRA Coordinator, Information Collection Clearance Program, Information Management Branch, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09722 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4000-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBJECT>DOE Response to Recommendation 2019-1 of the Defense Nuclear Facilities Safety Board, Uncontrolled Hazard Scenarios and 10 CFR 830 Implementation at the Pantex Plant</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Energy.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On February 20, 2019, the Defense Nuclear Facilities Safety Board issued Recommendation 2019-1, 
                        <E T="03">Uncontrolled Hazard Scenarios and 10 CFR 830 Implementation at the Pantex Plant,</E>
                         to the Department of Energy. In accordance with the Atomic Energy Act of 1954, the Secretary of Energy's response to the Recommendation is provided in this notice.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments, data, views, or arguments concerning the Secretary's response are due on or before June 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Please send to: Defense Nuclear Facilities Safety Board, 625 Indiana Avenue NW, Suite 700, Washington, DC 20004.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Christopher Chaves, Office of the Departmental Representative to the Defense Nuclear Facilities Safety Board, Office of Environment, Health, Safety and Security, U.S. Department of Energy, 1000 Independence Avenue SW, Washington, DC 20585, or telephone number (301) 903-5999, or email 
                        <E T="03">Christopher.Chaves@hq.doe.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On February 20, 2019, the Defense Nuclear Facilities Safety Board issued Recommendation 2019-1, 
                    <E T="03">Uncontrolled Hazard Scenarios and 10 CFR 830 Implementation at the Pantex Plant,</E>
                     to the Department of Energy. Recommendation 2019-1 was published in the 
                    <E T="04">Federal Register</E>
                     on March 19, 2019 (84 FR 10196). In accordance with section 315(c) of the Atomic Energy Act of 1954 (42 U.S.C. 2286d(c)), the Secretary of Energy's response to the Recommendation is printed in full at the conclusion of this notice.
                </P>
                <SIG>
                    <DATED>Signed in Washington, DC, on May 6, 2019.</DATED>
                    <NAME>Joe Olencz,</NAME>
                    <TITLE>Departmental Representative to the Defense Nuclear Facilities Safety Board, Office of Environment, Health, Safety and Security.</TITLE>
                </SIG>
                <FP SOURCE="FP-1">April 16, 2019</FP>
                <FP SOURCE="FP-1">The Honorable Bruce Hamilton</FP>
                <FP SOURCE="FP-1">Chairman</FP>
                <FP SOURCE="FP-1">Defense Nuclear Facilities Safety Board</FP>
                <FP SOURCE="FP-1">625 Indiana Avenue, NW, Suite 700</FP>
                <FP SOURCE="FP-1">Washington, DC 20004</FP>
                <P>Dear Chairman Hamilton:</P>
                <P>
                    The Department of Energy (DOE) acknowledges receipt of Defense Nuclear Facilities Safety Board (Board) Recommendation 2019-1, 
                    <E T="03">Uncontrolled Hazard Scenarios and 10 CFR 830 Implementation at the Pantex Plant</E>
                    , which was published in the Federal Register on March 19, 2019.
                </P>
                <P>
                    The Department shares the Board's view that we should continue to improve the configuration management and implementation of the safety basis for nuclear explosive operations at the Pantex Plant. Processes are in place at the Pantex Plant to ensure all nuclear explosive operations are planned and executed in a manner that protects the environment, the public, and the worker. I accept Recommendation 2019-1, which aligns with improvement actions that the Department of Energy's National Nuclear Security Administration (DOE/NNSA) has already taken as outlined in the DOE/NNSA Administrator's January 28, 2019, response to Draft Recommendation 2018-1, 
                    <E T="03">Uncontrolled Hazard Scenarios and 10 CFR 830 Implementation at the Pantex Plant</E>
                     (see enclosure). We look forward to briefing the Board on improvement actions planned and underway.
                </P>
                <P>
                    The Department is committed to the safe operation of its nuclear facilities consistent with the principles of Integrated Safety Management and the Department's nuclear safety requirements. We will continue to prioritize Pantex safety basis efforts and maintain a dialogue with your staff. I have assigned Geoffrey L. Beausoleil, Manager, DOE/NNSA Production Office, 
                    <PRTPAGE P="20869"/>
                    to be the Department's responsible manager for this recommendation.
                </P>
                <P>If you have any questions, please contact Mr. Geoffrey L. Beausoleil at (865) 576-0752</P>
                <P>Sincerely,</P>
                <P>Lisa E. Gordon-Hagerty</P>
                <P>Enclosure</P>
                <HD SOURCE="HD3">ENCLOSURE</HD>
                <P>
                    Department of Energy's National Nuclear Security Administration's (DOE/NNSA) Administrator January 28, 2019, Response to DNFSB Draft Recommendation 2018-1, 
                    <E T="03">Uncontrolled Hazard Scenarios and 10 CFR 830 Implementation at the Pantex Plant</E>
                    .
                </P>
                <HD SOURCE="HD2">General Comments</HD>
                <P>Throughout last year, DOE/NNSA and Consolidated Nuclear Security (CNS), the Pantex Management &amp; Operating Contractor, have taken numerous actions aimed at improving the quality, configuration management, and implementation of the Pantex Plant (Pantex) safety basis. Key actions during this period include the following:</P>
                <P> In September 2018, DOE/NNSA approved a Safety Basis Supplement (SBS) by CNS that fulfilled two primary objectives. First, the SBS provides a framework for analyzing and addressing legacy issues in the Pantex safety basis associated with scenarios previously determined not to require application of safety controls because they were evaluated to be “sufficiently unlikely.“ Requirements have been established to assure “sufficiently unlikely“ scenarios are identified and resolved. Second, the SBS included significant improvements in safety protocols through the identification of compensatory measures for preventing events that could result from “Falling Man“ scenarios. CNS has implemented the new “Falling Man“ compensatory measures in all active nuclear explosive cells and bays.</P>
                <P> In October 2018, DOE/NNSA initiated a project to identify options for “redesigning“ the Pantex safety basis, with the goal of reducing the complexity of the safety basis activities and documents; simplifying development, review, approval, and maintenance of the documents; and correspondingly improving implementation of the identified safety controls. Members of this project team include representatives from DOE/NNSA, the production plants, the national laboratories, and the Nevada National Security Site. This initiative will take substantial effort to achieve, but is essential for ensuring the long-term success of the Pantex national security mission.</P>
                <P> DOE/NNSA approved a comprehensive Corrective Action Plan by CNS that includes numerous actions for improving the Pantex safety basis development process and addressing legacy-improvement opportunities in the current documents. Execution of this plan will drive significant progress in the overall quality of the Pantex safety basis within the next two years. To date, CNS has completed all actions on schedule.</P>
                <P>
                    Several elements of the DNFSB's Draft Recommendation arise from inconsistencies between long-standing Pantex practices and DOE guidance documents. Examples include DNFSB concerns related to the structure of the Pantex Unreviewed Safety Question (USQ) procedure, the longevity of some Justifications for Continued Operations, and the frequency within which safety control implementation is re-verified. By definition, the referenced DOE Guides (e.g., DOE Guide 423.1-1B, 
                    <E T="03">Implementation Guide for Use in Developing Technical Safety Requirements</E>
                    , and DOE Guide 424.1-1B, 
                    <E T="03">Implementation Guide for Use in Addressing Unreviewed Safety Question Requirements</E>
                    ) provide supplemental information that DOE/NNSA uses to encourage performance of operations and activities across the complex with a focus on best practices. Similarly, several of the concerns in the DNFSB's Draft Recommendation related to Special Tooling are understood to be suggestions to adopt industry best practices rather than reflecting deficiencies against DOE regulations or requirements. DOE/NNSA identified similar issues with the Special Tooling program as part of our oversight activities. DOE/NNSA will ensure the DNFSB suggestions are evaluated as it continues to develop additional improvement actions, but do not believe the issues result in challenging adequate protection of public health or safety.
                </P>
                <HD SOURCE="HD2">Safety Controls Associated With Low-Probability/High-Consequent Events</HD>
                <P>The DNFSB raised concerns that some scenarios determined to be “sufficiently unlikely“ (i.e., expected to occur between once-in-a-million and once-in-a-billion years) in the applicable Pantex safety basis documents did not have clearly identified safety controls for preventing or mitigating the potentially high consequences (e.g., worker fatality, environmental radiological contamination, or public radiological exposure). DOE/NNSA provides the following perspective regarding these concerns:</P>
                <P>
                     As noted in the DNFSB's Draft Recommendation, questions associated with “new information“ related to potential accident scenarios are evaluated via the Pantex Problem Identification and Evaluation process and the requirements in DOE-NA-STD-3016-2018, 
                    <E T="03">Hazard Analysis reports for Nuclear Explosive Operations</E>
                    . This process ensures that appropriate operational restrictions or compensatory measures are implemented while resolving any potential safety issues associated with the adequacy of safety controls. During the past year, DOE/NNSA has verified this process has been effectively executed by CNS, and has driven improvements to the process as warranted.
                </P>
                <P> One of the concerns raised by the DNFSB, associated with the adequacy of safety controls for “sufficiently unlikely“ scenarios, was reliance on Key Elements of Safety Management Programs to prevent high-consequences during potential “Falling Man“ scenarios. In September 2018, the DOE/NNSA approved a SBS that identified additional “Falling Man“ controls, which are structured, credited, and protected as Specific Administrative Controls (SACs) rather than programmatic Key Elements. As noted above, CNS implemented these “Falling Man“ SACs in all active nuclear explosive cells and bays.</P>
                <P> Other than the control adequacy issues discussed above, the remaining control adequacy concerns generally relate to weaknesses in the safety basis documentation. The two most common examples are (a) controls that are already implemented in the field but are not specifically linked to and credited for scenarios in the safety basis that were dispositioned as “sufficiently unlikely“ and (b) scenarios that were inappropriately deemed as “sufficiently unlikely“ in the safety basis where, lacking sufficient technical bases, they are not credible (e.g., the scenario would require deliberate or malicious procedural violations).</P>
                <P>
                    The aforementioned SBS provides a framework for evaluating and categorizing these documentation-related issues. CNS developed a Corrective Action Plan that DOE/NNSA approved in November 2018 that includes commitments to perform extent-of-condition reviews of 
                    <E T="03">all</E>
                     Pantex safety basis documents by the end of 2019, with the objective of identifying and correcting all instances of these documentation-related issues. To date, CNS has executed on schedule the actions captured in this Corrective Action Plan.
                </P>
                <HD SOURCE="HD2">Configuration Management of the Pantex Safety Basis</HD>
                <P>
                    The DNFSB raised concerns related to the processes used to maintain 
                    <PRTPAGE P="20870"/>
                    configuration management of the Pantex safety basis. Specifically, the DNFSB expressed concern that: (a) updates to Pantex safety basis documents are not always completed on an annual basis; (b) the Pantex USQ procedure allows discrepant-as-found conditions to be corrected without suspending impacted operations or making necessary notifications; and (c) some Justifications for Continued Operations (JCOs) are extended beyond a year. DOE/NNSA provides the following perspectives regarding these concerns:
                </P>
                <P> The DNFSB's concern related to the timeliness of updating safety basis documents appears to be based on data collected during 2017. The vast majority of Pantex safety basis documents were updated on-time in 2018, the lone exception being the update associated with the Site-wide Safety Analysis Report. CNS is committed to updating this document by March 2019. The aforementioned Corrective Action Plan, approved by DOE/NNSA in November 2018, includes actions to revise the administrative procedures for developing and revising Pantex safety basis documents. These actions specifically identify improving configuration management of safety basis documents as an objective, which, when executed effectively, should preclude similar issues from occurring in the future.</P>
                <P> The DNFSB's Draft Recommendation states that “the Pantex USQ procedures allow three days to correct discrepant-as-found conditions... without stopping operations, notifying DOE, or initiating the Pantex process for addressing a potential inadequacy of the safety analysis.“ While the Pantex USQ procedure does allow three days to correct a discrepant-as-found condition prior to declaring a Potential Inadequacy of the Safety Analysis, and given that 10 CFR 830 Subpart B does not have rules for specific numeric durations (other than “as appropriate”) Pantex procedures require: (a) suspending operations whenever a safety question is raised (e.g., discovery of discrepant-as-found conditions); (b) making appropriate notifications to the DOE/NNSA Production Office (NPO); and (c) initiating the DOE-Approved Pantex USQ process. Therefore, we believe the proper safety control is in place.</P>
                <P> The DNFSB's Draft Recommendation includes a concern with the processes for handling JCOs and the extension of some for an extended period of time. The goal in the Pantex USQ procedure of addressing JCOs in less than a year is derived from guidance in DOE Guide 424.1-1B. The intent is to ensure JCOs and their compensatory measures are used to address temporary changes to the safety basis until permanent solutions can be identified and incorporated. While one year is a viable goal for limiting use of a JCO, it is not always practical to resolve issues in nuclear or nuclear explosive operations in that time frame. Many of the issues identified in JCOs involve complex operations or hazard scenarios where a permanent solution cannot be developed without extensive analysis or physical changes to facilities, systems, or equipment. Several JCO extensions were to allow additional time to develop permanent solutions, instead of incorporating compensatory measures into the safety basis only to revise the documents again once the permanent solution was developed. Each extension was approved by the Safety Basis Approval Authority after NPO fully evaluated the JCO conditions and compensatory measures, and concluded operations could be continued safely with implementation of the JCO compensatory measures.</P>
                <HD SOURCE="HD2">Special Tooling Program</HD>
                <P>The DNFSB expressed concerns that deficiencies exist within the Pantex Special Tooling Program. Examples of the identified deficiencies include: (a) inconsistencies between Pantex tooling procedures and site practices; (b) additional Non-Destructive Evaluation techniques being used to inspect welds on tooling; (c) reliance on worker knowledge and skill-of-the-craft during tooling inspection, maintenance, and testing activities; ( d) tool-specific performance criteria not being listed in the Pantex safety basis; and ( e) weaknesses in analysis and testing for mechanical impact scenarios involving tooling. DOE/NNSA provides the following perspectives regarding these concerns:</P>
                <P> Subsequent to the DNFSB's September 2017 review, tooling-specific deviations from Pantex procedures were reviewed and confirmed that continued use of the subject tools meets applicable requirements. Additional corrective actions have been taken to prevent recurrence of the inconsistencies.</P>
                <P> Subsequent to the DNFSB's September 2017 review, CNS engaged an outside expert to review the Pantex welding program, who concluded that Pantex processes meet expectations. That is, welds are performed and inspected by qualified welders in accordance with applicable industry standards.</P>
                <P> Pantex tools are maintained and tested by trained and qualified journeymen mechanics in accordance with programmatic and tool-specific requirements.</P>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09782 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 6450-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBJECT>Agency Information Collection Extension</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Department of Energy.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Energy (DOE), pursuant to the Paperwork Reduction Act of 1995, intends to extend for three years an information collection request with the Office of Management and Budget (OMB).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments regarding this proposed information collection must be received on or before July 12, 2019. If you anticipate difficulty in submitting comments within that period, contact the person listed below as soon as possible.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments may be sent to Scott Whiteford at (202) 287-1563 or by fax at (202) 287-1656 or by email at 
                        <E T="03">scott.whiteford@hq.doe.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of the information collection instrument and instructions should be directed to Scott Whiteford at (202) 287-1563 or by email at 
                        <E T="03">scott.whiteford@hq.doe.gov.</E>
                         Information for the Excess Personal Property Furnished to Non-Federal Recipients and the Exchange/Sale Report is collected using GSA's Personal Property Reporting Tool and can be found at the following link: 
                        <E T="03">https://gsa.inl.gov/property/</E>
                        .
                    </P>
                    <P>
                        Information for the Federal Fleet Report is collected using the Federal Automotive Statistical Tool and can be found at the following link: 
                        <E T="03">https://fastweb.inel.gov/</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Comments are invited on: (a) Whether the extended collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; (b) the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the 
                    <PRTPAGE P="20871"/>
                    use of automated collection techniques or other forms of information technology.
                </P>
                <P>
                    This information collection request contains: (1) 
                    <E T="03">OMB No.</E>
                     1910-1000; (2) 
                    <E T="03">Information Collection Request Title:</E>
                     Exchange/Sale Report, Excess Personal Property Furnished to Non-Federal Recipients, Federal Automotive Statistical Tool Report; (3) 
                    <E T="03">Type of Review:</E>
                     Renewal; (4) 
                    <E T="03">Purpose:</E>
                     The information being collected is data required in order to submit annual personal property reports as required by 41 CFR part 102 and the Office of Management and Budget. Respondents to this information collection request will be the Department of Energy's Management and Operating Contractor and other major site contractors; (5) 
                    <E T="03">Respondents:</E>
                     92 respondents for each of the three reports equals 276 total respondents; (6) 
                    <E T="03">Estimated number of burden hours:</E>
                     The total estimated number of burden hours is 1,656. A breakout of burden hours for each report is listed below:
                </P>
                <P>○ The burden hours for responding to the Exchange/Sale Report are estimated at 2 hours for each of the 92 estimated respondents, for a total of 184 burden hours.</P>
                <P>○ The burden hours for responding to the Excess Personal Property Furnished to Non-Federal Recipients are estimated at 2 hours for each of the 184 estimated respondents, for a total of 184 burden hours.</P>
                <P>○ The burden hours for responding to the Federal Automotive Statistical Tool at 18 hours for each of the 92 estimated respondents, for a total of 1,656 burden hours.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> (A) 41 CFR 102-39.85, (B) 41 CFR 102-36.295 and 102-36.300, (C) OMB Circular A-11 section 25.5, (D) 41 CFR 102-34.335.</P>
                </AUTH>
                <SIG>
                    <DATED>Signed in Washington, DC, on April 25, 2019.</DATED>
                    <NAME>Scott Whiteford,</NAME>
                    <TITLE>Director, Office of Asset Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09783 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 6450-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>National Nuclear Security Administration</SUBAGY>
                <SUBJECT>Defense Programs Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Defense Programs, National Nuclear Security Administration, Department of Energy.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of closed meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice announces a closed meeting of the Defense Programs Advisory Committee (DPAC). The Federal Advisory Committee Act requires that public notice of meetings be announced in the 
                        <E T="04">Federal Register</E>
                        . Due to national security considerations, the meeting will be closed to the public and matters to be discussed are exempt from public disclosure under Executive Order 13526 and the Atomic Energy Act of 1954.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>May 20-21, 2019 8:30 a.m. to 5:00 p.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>U.S. Department of Energy, 1000 Independence Ave. SW, Washington, DC 20585.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Dana Hunter, Office of RDT&amp;E (NA-11), National Nuclear Security Administration, U.S. Department of Energy, 1000 Independence Ave. SW, Washington, DC 20585, (202) 287-6287 or Email: 
                        <E T="03">Dana.Hunter@NNSA.Doe.Gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Background:</E>
                     The DPAC provides advice and recommendations to the Deputy Administrator for Defense Programs on the stewardship and maintenance of the Nation's nuclear deterrent.
                </P>
                <P>
                    <E T="03">Purpose of the Meeting:</E>
                     The purpose of this meeting of the DPAC is to discuss programmatic updates, the current status of the High Performance Computing Subcommittee, and review the charter for Stockpile Responsiveness Subcommittee.
                </P>
                <P>
                    <E T="03">Type of Meeting:</E>
                     In the interest of national security, the meeting will be closed to the public. The Federal Advisory Committee Act, 5 U.S.C. App. 2, section 10(d), and the Federal Advisory Committee Management Regulation, 41 CFR 102-3.155, incorporate by reference the Government in the Sunshine Act, 5 U.S.C. 552b, which, at 552b(c)(1) and (c)(3) permits closure of meetings where restricted data or other classified matters will be discussed. Such data and matters will be discussed at this meeting.
                </P>
                <P>
                    <E T="03">Tentative Agenda:</E>
                     New Member Swearing In; Annual Ethics Training; Defense Programs Programmatic Updates; Update on High Performance Computing Subcommittee; Update on SRP Review Subcommittee; Conclusion.
                </P>
                <P>
                    <E T="03">Public Participation:</E>
                     There will be no public participation in this closed meeting. Those wishing to provide written comments or statements to the Committee are invited to send them to Dana Hunter at the address listed above.
                </P>
                <P>
                    <E T="03">Minutes:</E>
                     The meeting minutes will not be available.
                </P>
                <SIG>
                    <DATED>Signed in Washington, DC, on May 7, 2019.</DATED>
                    <NAME>Antionette M. Watkins,</NAME>
                    <TITLE>Acting Deputy Committee Management Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09762 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 6450-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket Nos. CP17-66-000; CP17-67-000]</DEPDOC>
                <SUBJECT>Venture Global Plaquemines LNG, LLC and Venture Global Gator Express, LLC; Notice of Availability of the Final Environmental Impact Statement for the Proposed Plaquemines LNG and Gator Express Pipeline Project</SUBJECT>
                <P>The staff of the Federal Energy Regulatory Commission (FERC or Commission) has prepared a final environmental impact statement (EIS) for the Plaquemines LNG and Gator Express Pipeline Project, proposed by Venture Global Plaquemines LNG, LLC and Venture Global Gator Express, LLC in the above-referenced dockets. Venture Global requests authorization to construct and operate a new liquefied natural gas (LNG) export terminal and associated facilities along the west bank of the Mississippi River in Plaquemines Parish, Louisiana (Terminal) and to construct and operate two new 42-inch-diameter natural gas pipeline laterals that would connect to the LNG Terminal. The new liquefaction facilities would have a nameplate production capacity of 20.0 million metric tons per annum (MTPA) of LNG and peak production capacity of 24 MTPA.</P>
                <P>The final EIS assesses the potential environmental effects of the construction and operation of the Plaquemines LNG and Gator Express Pipeline Project in accordance with the requirements of the National Environmental Policy Act (NEPA). The FERC staff concludes that approval of the proposed project, with the mitigation measures recommended in the final EIS, would have some adverse environmental impacts. These impacts would be reduced to less-than-significant levels with the implementation of Venture Global's proposed mitigation measures and the additional measures recommended in the final EIS.</P>
                <P>
                    The U.S. Army Corps of Engineers, U.S. Coast Guard, U.S. Department of Energy, U.S. Environmental Protection Agency, and U.S. Department of Transportation participated as cooperating agencies in the preparation 
                    <PRTPAGE P="20872"/>
                    of the EIS. Cooperating agencies have jurisdiction by law or special expertise with respect to resources potentially affected by the proposal and participate in the NEPA analysis. Although the cooperating agencies provided input to the conclusions and recommendations presented in the EIS, the agencies will present their own conclusions and recommendations in their respective Records of Decision for the project.
                </P>
                <P>The final EIS addresses the potential environmental effects of the construction and operation of the following project facilities:</P>
                <P>
                    • 
                    <E T="03">LNG Terminal:</E>
                     Construction and operation of various liquefaction, LNG distribution, and appurtenant facilities within the boundaries of the site leased by Venture Global on the Mississippi River, including:
                </P>
                <P>○ Six pretreatment facilities (three in each phase);</P>
                <P>○ a liquefaction plant with 18 integrated single-mixed refrigerant blocks and support facilities (otherwise referred to as liquefaction blocks or blocks) to be constructed in two phases (nine blocks in each phase);</P>
                <P>○ four 200,000-cubic-meter aboveground LNG storage tanks;</P>
                <P>○ three LNG loading docks within a common LNG berthing area; and</P>
                <P>○ air-cooled electric power generation facilities.</P>
                <P>
                    • 
                    <E T="03">Pipeline System:</E>
                     Construction and operation of two parallel 42-inch-diameter natural gas pipelines that share one right-of-way corridor for the majority of their respective routes and appurtenant aboveground facilities, including the following:
                </P>
                <P>○ 15.1-mile-long Southwest Lateral Tennessee Gas Pipeline, LLC (TGP) Pipeline;</P>
                <P>○ 11.7-mile-long Southwest Lateral Texas Eastern Transmission, LP (TETCO) Pipeline;</P>
                <P>○ TGP metering and regulation station; and</P>
                <P>○ TETCO metering and regulation station.</P>
                <P>
                    The Commission mailed a copy of the 
                    <E T="03">Notice of Availability</E>
                     to federal, state, and local government representatives and agencies; elected officials; environmental and public interest groups; Native American tribes; potentially affected landowners and other interested individuals and groups; and newspapers and libraries in the project area. The final EIS is only available in electronic format. It may be viewed and downloaded from the FERC's website (
                    <E T="03">www.ferc.gov</E>
                    ), on the Environmental Documents page (
                    <E T="03">https://www.ferc.gov/industries/gas/enviro/eis.asp</E>
                    ). In addition, the final EIS may be accessed by using the eLibrary link on the FERC's website. Click on the eLibrary link (
                    <E T="03">https://www.ferc.gov/docs-filing/elibrary.asp</E>
                    ), click on General Search, and enter the docket number in the “Docket Number” field, excluding the last three digits (
                    <E T="03">i.e.,</E>
                     CP17-66 or CP17-67). Be sure you have selected an appropriate date range. For assistance, please contact FERC Online Support at 
                    <E T="03">FercOnlineSupport@ferc.gov</E>
                     or toll free at (866) 208-3676, or for TTY, contact (202) 502-8659.
                </P>
                <P>
                    Additional information about the project is available from the Commission's Office of External Affairs, at (866) 208-FERC, or on the FERC website (
                    <E T="03">www.ferc.gov</E>
                    ) using the eLibrary link. The eLibrary link also provides access to the texts of all formal documents issued by the Commission, such as orders, notices, and rulemakings.
                </P>
                <P>
                    In addition, the Commission offers a free service called eSubscription that allows you to keep track of all formal issuances and submittals in specific dockets. This can reduce the amount of time you spend researching proceedings by automatically providing you with notification of these filings, document summaries, and direct links to the documents. Go to 
                    <E T="03">www.ferc.gov/docs-filing/esubscription.asp.</E>
                </P>
                <SIG>
                    <DATED>Dated: May 3, 2019.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09719 Filed 5-10-19; 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. ER19-1781-000]</DEPDOC>
                <SUBJECT>MeterGenius, Inc.; Supplemental Notice That Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization</SUBJECT>
                <P>This is a supplemental notice in the above-referenced MeterGenius, Inc.'s application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability.</P>
                <P>Any person desiring to intervene or to protest should file with the Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant.</P>
                <P>Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability, is May 27, 2019.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov.</E>
                     To facilitate electronic service, persons with internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.
                </P>
                <P>Persons unable to file electronically should submit an original and 5 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426.</P>
                <P>
                    The filings in the above-referenced proceeding are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for electronic review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the website that enables subscribers to receive email notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please email 
                    <E T="03">FERCOnlineSupport@ferc.gov.</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: May 6, 2019.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09706 Filed 5-10-19; 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>
                     CP17-458-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midship Pipeline Company, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Abbreviated Application for Certificate Authority of Midship Pipeline Company, LLC.
                    <PRTPAGE P="20873"/>
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/1/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190501-5445.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/22/19.
                </P>
                <P>
                    <E T="03">Docket Number:</E>
                     PR19-58-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Bayonne Energy Center, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff filing per 284.224/.123: Baseline Refiling to be effective 10/1/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/1/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     201905015318.
                </P>
                <P>
                    <E T="03">Comments/Protests Due:</E>
                     5 p.m. ET5/22/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP19-1185-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Alliance Pipeline L.P.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Operational Purchases and Sales Report of Alliance Pipeline L.P. under RP19-1185.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     4/30/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190430-5451.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/13/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP19-423-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Tallgrass Interstate Gas Transmission, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Pre-Arranged/Pre-Agreed (Petition for Approval of Settlement) Filing, et al. of Tallgrass Interstate Gas Transmission, LLC under RP19-423.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/1/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190501-5451.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/13/19.
                </P>
                <P>The filings are accessible in the Commission's eLibrary system by clicking on the links or querying the docket number.</P>
                <P>Any person desiring to intervene or protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Regulations (18 CFR 385.211 and 385.214) on or before 5:00 p.m. Eastern time on the specified date(s). Protests may be considered, but intervention is necessary to become a party to the proceeding.</P>
                <P>
                    eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at: 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>
                     For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: May 6, 2019.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09714 Filed 5-10-19; 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>
                     RP19-1213-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Total Peaking Services, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing TPS Order No. 587-Y Compliance Filing Changes to be effective 8/1/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5137.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/20/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP19-257-003.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Gas Storage Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing SWG Cost and Revenue Study in Compliance.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5061.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/20/19.
                </P>
                <P>The filings are accessible in the Commission's eLibrary system by clicking on the links or querying the docket number.</P>
                <P>Any person desiring to intervene or protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Regulations (18 CFR 385.211 and 385.214) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.</P>
                <P>
                    eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at: 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>
                     For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09772 Filed 5-10-19; 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. EL19-70-000]</DEPDOC>
                <SUBJECT>Indicated Generation Owners; Notice of Petition for Declaratory Order</SUBJECT>
                <P>
                    Take notice that on May 3, 2019, pursuant to Rule 207 of the Federal Energy Regulatory Commission's (Commission) Rules of Practice and Procedure, 18 CFR 385.207 (2017), Indicated Generation Owners 
                    <SU>1</SU>
                    <FTREF/>
                     (collectively Petitioners), filed a petition for a declaratory order regarding proposed revenue requirements and cost-based rates for merchant generators providing reactive power service to the PJM Interconnection, L.L.C. market, as more fully explained in the petition.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Ares EIF Management, LLC, Competitive Power Ventures, Inc., Invenergy Thermal Development LLC, J-POWER USA Development Co., Ltd., Panda Power Generation Infrastructure Fund, LLC, Tenaska, Inc., Vistra Energy Corp.
                    </P>
                </FTNT>
                <P>Any person desiring to intervene or to protest this filing must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211, 385.214). Protests will be considered by the Commission in determining the appropriate action to be taken, but will not serve to make protestants parties to the proceeding. Any person wishing to become a party must file a notice of intervention or motion to intervene, as appropriate. Such notices, motions, or protests must be filed on or before the comment date. Anyone filing a motion to intervene or protest must serve a copy of that document on the Petitioner.</P>
                <P>
                    The Commission encourages electronic submission of 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 should submit an original and 5 copies of the protest or intervention to the Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426.
                </P>
                <P>
                    This filing is accessible on-line at 
                    <E T="03">http://www.ferc.gov,</E>
                     using the “eLibrary” link and is available for review in the Commission's Public Reference Room in Washington, DC. There is an “eSubscription” link on the website that enables subscribers to receive email notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please email 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5:00 p.m. Eastern time on June 3, 2019.
                </P>
                <SIG>
                    <DATED>Dated: May 3, 2019.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09708 Filed 5-10-19; 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 corporate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EC19-84-000.
                    <PRTPAGE P="20874"/>
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Oregon Trail Wind Park, LLC, Payne's Ferry Wind Park, LLC, Pilgrim Stage Station Wind Park, LLC, Yahoo Creek Wind Park, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Application for Authorization Under Section 203 of the Federal Power Act, et al.  of Oregon Trail Wind Park, LLC, et al. 
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/2/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190502-5140.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/23/19.
                </P>
                <P>Take notice that the Commission received the following exempt wholesale generator filings: </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EG19-95-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Glen Ullin Energy Center, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Self-Certification of EG or FC of Glen Ullin Energy Center, LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5112.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>Take notice that the Commission received the following electric rate filings: </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER10-2718-032; ER10-2719-032.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Cogen Technologies Linden Venture, L.P., East Coast Power Linden Holding, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Supplement to November 26, 2018 Notice of Non-Material Change in Status of Cogen Technologies Linden Venture, L.P., 
                    <E T="03">et al.</E>
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5084.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER17-1531-003.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     CPV Fairview, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Supplement to January 17, 2019 Notice of Change in Status of CPV Fairview, LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5100.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1153-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     California Independent System Operator Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 2019-05-03 Deficiency Filing Inverter-Based Interconnection Requirements to be effective 4/30/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5081.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19. 
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1339-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Duke Energy Progress, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Clarifying Amendment to Recovery of Storm Rates and Reqt for Expedited Action to be effective 5/15/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5066.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/10/19. 
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1374-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 2019-05-02_SA 3271 Bondurant-Montezuma 345kV Structure Replacement Sub MPFCA to be effective 3/20/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/2/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190502-5095.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/13/19. 
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1375-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc..
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 2019-05-03_SA 3273 150 Mvar Cap Bank at Blackhawk 345kV Sub MPFCA to be effective 3/20/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5036.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/13/19. 
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1378-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 2019-05-03_SA 3274 1x50 Mvar Cap Bank at Midport 161 kV MPFCA Sub to be effective 3/20/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5096.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/13/19. 
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1639-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     South Peak Wind LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Amendment to market-based rate application to be effective 6/21/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5042.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19. 
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1771-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     GridLiance Heartland LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Limited Revisions to Attachment O Formula Rate Template and Implementation Protocols of GridLiance Heartland LLC..
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/2/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190502-5139.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/23/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1772-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Amendment to ISA, Service Agreement No. 4121, Queue No. NQ113 to be effective 2/25/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5041.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1773-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Alabama Power Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Three Rocks Solar (Evergreen Solar) LGIA Filing to be effective 4/22/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5043.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1774-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Alabama Power Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Turkey Run LGIA Filing to be effective 4/22/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5044.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1775-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southern California Edison Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: SCE Recollation of TO Tariff Filing 2b of 3 to be effective 5/1/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5048.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1776-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southern California Edison Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Cancellation: Notice of Cancellation GIA &amp; DSA Dwight ES 1 Project SA Nos. 1055-1056 to be effective 4/29/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5062.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1777-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midwest Energy, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Petition for Temporary Waiver of Midwest Energy, Inc.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5063.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1778-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Glen Ullin Energy Center, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Baseline eTariff Filing: Market-Based Rate Application to be effective 5/6/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5092.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1779-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 2019-05-03_SA 1632 ITC Midwest-Osceola Windpower 3rd Rev GIA (G426 G538) to be effective 4/19/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5094.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1780-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 3550 WAPA &amp; City of Moorhead MN Interconnection Agreement to be effective 5/2/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5114.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>The filings are accessible in the Commission's eLibrary system by clicking on the links or querying the docket number.</P>
                <P>
                    Any person desiring to intervene or protest in any of the above proceedings 
                    <PRTPAGE P="20875"/>
                    must file in accordance with Rules 211 and 214 of the Commission's Regulations (18 CFR 385.211 and 385.214) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.
                </P>
                <P>
                    eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at: 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>
                     For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: May 3, 2019.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09718 Filed 5-10-19; 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. CP19-218-000]</DEPDOC>
                <SUBJECT>Equitrans, L.P.; Notice of Request Under Blanket Authorization</SUBJECT>
                <P>
                    Take notice that on April 24, 2019, Equitrans, L.P., 2200 Energy Drive Canonsburg, PA 15317, filed a prior notice application pursuant to sections 157.205, 157.208(c), and 157.216(b) of the Federal Energy Regulatory Commission's (Commission) regulations under the Natural Gas Act (NGA), and Equitrans blanket certificate issued in Docket No. CP96-532-000. Equitrans requests authorization to abandon and replace two segments of its TP-4555 pipeline (Bare Pipe Replacement Project), one of the pipelines which comprises Equitrans' Allegheny Valley Connector System. The replacement segments, which are located in Westmoreland County, Pennsylvania, total approximately 3.92 miles, all as more fully set forth in the application, which is open to the public for inspection. The filing may also be viewed on the web at 
                    <E T="03">http://www.ferc.gov</E>
                     using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field to access the document. For assistance, contact FERC at 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or call toll-free, (866) 208-3676 or TTY, (202) 502-8659.
                </P>
                <P>Specifically, Equitrans is proposing to abandon approximately 3.85 miles of 20-inch diameter pipeline on the TP-4555 pipeline and replace it with approximately 3.92 miles of 20-inch diameter pipeline. The TP-4555 pipeline is part of Equitrans' Allegheny Valley Connector System.</P>
                <P>
                    Any questions regarding this application should be directed to Matthew Eggerding Assistant General Counsel, 2200 Energy Drive, Canonsburg, PA 15317, or call (412) 553-5786, or by email: 
                    <E T="03">meggerding@equitransmidstream.com</E>
                    .
                </P>
                <P>Any person or the Commission's staff may, within 60 days after issuance of the instant notice by the Commission, file pursuant to Rule 214 of the Commission's Procedural Rules (18 CFR 385.214) a motion to intervene or notice of intervention and pursuant to Section 157.205 of the regulations under the NGA (18 CFR 157.205), a protest to the request. If no protest is filed within the time allowed therefore, the proposed activity shall be deemed to be authorized effective the day after the time allowed for filing a protest. If a protest is filed and not withdrawn within 30 days after the allowed time for filing a protest, the instant request shall be treated as an application for authorization pursuant to section 7 of the NGA.</P>
                <P>Pursuant to section 157.9 of the Commission's rules, 18 CFR 157.9, within 90 days of this Notice the Commission staff will either: Complete its environmental assessment (EA) and place it into the Commission's public record (eLibrary) for this proceeding, or issue a Notice of Schedule for Environmental Review. If a Notice of Schedule for Environmental Review is issued, it will indicate, among other milestones, the anticipated date for the Commission staff's issuance of the final environmental impact statement (FEIS) or EA for this proposal. The filing of the EA in the Commission's public record for this proceeding or the issuance of a Notice of Schedule for Environmental Review will serve to notify federal and state agencies of the timing for the completion of all necessary reviews, and the subsequent need to complete all federal authorizations within 90 days of the date of issuance of the Commission staff's FEIS or EA.</P>
                <P>Persons who wish to comment only on the environmental review of this project should submit an original and two copies of their comments to the Secretary of the Commission. Environmental commenters will be placed on the Commission's environmental mailing list, and will be notified of any meetings associated with the Commission's environmental review process. Environmental commenters will not be required to serve copies of filed documents on all other parties. However, the non-party commenter will not receive copies of all documents filed by other parties or issued by the Commission and will not have the right to seek court review of the Commission's final order.</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 should submit an original and 3 copies of the protest or intervention to the Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426.
                </P>
                <SIG>
                    <DATED>Dated: May 3, 2019.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09707 Filed 5-10-19; 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. ER19-1778-000]</DEPDOC>
                <SUBJECT>Glen Ullin Energy Center, LLC.; Supplemental Notice That Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization</SUBJECT>
                <P>This is a supplemental notice in the above-referenced proceeding of Glen Ullin Energy Center, LLC's application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability.</P>
                <P>Any person desiring to intervene or to protest should file with the Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant.</P>
                <P>Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability, is May 28, 2019.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov.</E>
                     To facilitate electronic service, persons with internet access who will eFile a document and/or be listed as a contact for an intervenor 
                    <PRTPAGE P="20876"/>
                    must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.
                </P>
                <P>Persons unable to file electronically should submit an original and 5 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426.</P>
                <P>
                    The filings in the above-referenced proceeding are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for electronic review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the website that enables subscribers to receive email notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please email 
                    <E T="03">FERCOnlineSupport@ferc.gov.</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: May 6, 2019.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09705 Filed 5-10-19; 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 corporate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EC19-85-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Convergent Energy and Power LP, Hazle Spindle, LLC, Stephentown Spindle, LLC, ECP ControlCo, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Joint Application for Authorization Under Section 203 of the Federal Power Act, et al. of Convergent Energy and Power LP, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5160.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1066-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Nevada Power Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: OATT Revision To Tariffs 05.03.19 to be effective 12/31/9998.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5000.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1379-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 2019-05-06_SA 3275 J438 POI Add 25 Mvar Cap Bank Sub MPFCA to be effective 3/20/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5097.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/16/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1405-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Precept Power LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: ADMENDMENT TO INITIAL TARIFF, WAIVERS AND BLANKET AUTHORITY to be effective 6/1/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5001.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1535-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Lower Mount Bethel Energy, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Supplement to April 8, 2019 Lower Mount Bethel Energy, LLC tariff filing.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/2/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190502-5152.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/23/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1695-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     California Transmission Project Corp.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Amended Request for One-Time Limited Waiver, et al. of California Transmission Project Corp.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5174.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1781-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     MeterGenius, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Baseline eTariff Filing: MeterGenius Market Base Rate Inital Tariff Filing to be effective 6/2/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5140.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1782-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Pacific Gas and Electric Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Amendment to the IA for the Stockton Port District (TO SA 117) to be effective 7/3/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/3/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190503-5142.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/24/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1783-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southern California Edison Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: SCE Recollation of WDAT Filing 7 of 9 to be effective 5/1/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5002.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1784-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Public Service Company of Colorado.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: PSCo-BLDR-T-2018-1-FASA&amp;EDA-522-0.0.0 to be effective 5/7/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5056.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1785-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Original Upgrade CSA, SA No. 5357; Queue No. NQ-J468 to be effective4/4/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5060.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1786-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Duke Energy Progress, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: DEP-Revised Rate Schedule No. 180 (Haywood EMC) to be effective11/1/2018.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5087.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1787-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Riverhead Solar Farm, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Baseline eTariff Filing: Riverhead Shared Facilities Agreement to be effective 5/7/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5089.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1788-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Duke Energy Progress, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: DEP-Revised Rate Schedule No. 172 (Piedmont EMC) to be effective11/1/2018.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5090.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1789-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Duke Energy Carolinas, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: DEC-Amended Rate Schedule Nos. 315, 316, 317, and 335) to be effective 1/1/2018.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5094.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>The filings are accessible in the Commission's eLibrary system by clicking on the links or querying the docket number.</P>
                <P>Any person desiring to intervene or protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Regulations (18 CFR 385.211 and 385.214) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.</P>
                <P>
                    eFiling is encouraged. More detailed information relating to filing 
                    <PRTPAGE P="20877"/>
                    requirements, interventions, protests, service, and qualifying facilities filings can be found at: 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>
                     For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: May 6, 2019.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09713 Filed 5-10-19; 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 corporate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EC19-86-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Kendall Green Energy LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Application for Authorization Under Section 203 of the Federal Power Act, et al. of Kendall Green Energy LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5149.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER10-2564-009; ER10-2600-009; ER10-2289-009; EL19-44-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Tucson Electric Power Company, UNS Electric, Inc., UniSource Energy Development Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Response to March 8, 2019 Order to Show Cause of Tucson Electric Power Company, UNS Electric, Inc., and UniSource Energy Development Company.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5160.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1425-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 2019-05-06_SA 3284 Hankinson Wahpeton 230 kV Line Sub MPFCA to be effective 3/26/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5117.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/16/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1429-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 2019-05-07_SA 3285 Big Stone Terminal Upgrade Sub MPFCA (J488 J493 J526) to be effective 3/26/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/7/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190507-5065.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/17/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1432-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: 2019-05-07_SA 3286 Blair Terminal Equip and Disconnects Sub MPFCA to be effective 3/26/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/7/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190507-5082.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/17/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1790-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     El Paso Electric Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Service Agreement No. 316, EPE LGIA with Great Divide Wind Farm to be effective 7/6/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5121.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1791-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Riverhead Solar Farm, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Riverhead MBR Change in Status to be effective 8/29/2018.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/6/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190506-5122.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1792-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Frontier Utilities Northeast LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Frontier Utilities Northeast LLC Notification of Change in Status to be effective 5/7/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/7/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190507-5000.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1793-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Valcour Altona Windpark, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Notice of Succession &amp; Clarification of Category Seller Status to be effective5/8/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/7/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190507-5092.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1794-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     California Independent System Operator Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 2019-05-07 EIM Implementation Agreement—Public Service Company of New Mexico to be effective 7/7/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/7/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190507-5095.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1795-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Valcour Bliss Windpark, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Notice of Succession &amp; Clarification of Category Seller Status to be effective5/8/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/7/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190507-5101.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-1796-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Valcour Chateaugay Windpark, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Notice of Succession &amp; Clarification of Category Seller Status to be effective5/8/2019.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     5/7/19.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20190507-5102.
                </P>
                <P>
                    <E T="03">Comments Due:</E>
                     5 p.m. ET 5/28/19.
                </P>
                <P>The filings are accessible in the Commission's eLibrary system by clicking on the links or querying the docket number.</P>
                <P>Any person desiring to intervene or protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Regulations (18 CFR 385.211 and 385.214) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.</P>
                <P>
                    eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at: 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>
                     For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09773 Filed 5-10-19; 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. OR19-23-000]</DEPDOC>
                <SUBJECT>TransMontaigne Partners L.P., Metroplex Energy, Inc. v. Colonial Pipeline Company; Notice of Complaint</SUBJECT>
                <P>
                    Take notice that on May 1, 2019, pursuant to sections 3, 6, 13(1), and 15(1) of the Interstate Commerce Act,
                    <SU>1</SU>
                    <FTREF/>
                     Rule 206 of the Rules of Practice and Procedure of the Federal Energy Regulatory Commission (Commission),
                    <SU>2</SU>
                    <FTREF/>
                     and Rules 343.1(a) and 343.2(c) of the Commission's Procedural Rules Applicable to Oil Pipeline Proceedings,
                    <SU>3</SU>
                    <FTREF/>
                     TransMontaigne Partners L.P. and Metroplex Energy, Inc. (collectively, 
                    <PRTPAGE P="20878"/>
                    Complainants) filed a formal complaint against Colonial Pipeline Company (Colonial or Respondent) challenging the lawfulness of the rate structure and terms and conditions of service by Colonial for transportation of refined petroleum products, including those practices contained in Colonial's FERC Tariff No. 99.46.0; Colonial's FERC Tariff No. 98.37.0; and Colonial's Shipper Manual, as more fully explained in the complaint.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         49 U.S.C. App. 3, 6, 13(1), and 15(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         18 CFR 385.206 (2018).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         18 CFR 343.1(a) and 343.2(c) (2018).
                    </P>
                </FTNT>
                <P>The Complainant certify that a copy of the complaint was served on the contacts for the Respondent as listed on the official service list.</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>
                    The Commission encourages electronic submission of 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 should submit an original and 5 copies of the protest or intervention to the Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426.
                </P>
                <P>
                    This filing is accessible on-line at 
                    <E T="03">http://www.ferc.gov,</E>
                     using the “eLibrary” link and is available for electronic review in the Commission's Public Reference Room in Washington, DC There is an “eSubscription” link on the website that enables subscribers to receive email notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please email 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5:00 p.m. Eastern Time May 31, 2019.
                </P>
                <SIG>
                    <DATED>Dated: May 3, 2019.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09709 Filed 5-10-19; 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. EL19-69-000]</DEPDOC>
                <SUBJECT>Alternative Transmission Inc.; Notice of Petition for Declaratory Order</SUBJECT>
                <P>Take notice that on May 2, 2019, pursuant to Rule 207 (a)(2) of the Federal Energy Regulatory Commission's (Commission) Rules of Practice and Procedure, 18 CFR 385.207(a)(2) (2017), Alternative Transmission Inc., (Alternative Transmission Inc. or Petitioner) filed a petition for a declaratory order petition stating that (1) the facilities and services described in the petition provide transmission of electric energy in interstate commerce subject to the Commission's jurisdiction under Parts II and III of the Federal Power Act (FPA) and (2) Alternative Transmission Inc., as the owner or operator of the described facilities that provide transmission of electric energy in interstate commerce, will be a public utility under Parts II and III of the FPA, as more fully explained in the petition.</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. Such notices, motions, or protests must be filed on or before the comment date. Anyone filing a motion to intervene or protest must serve a copy of that document on the Petitioner.</P>
                <P>
                    The Commission encourages electronic submission of 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 should submit an original and 5 copies of the protest or intervention to the Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426
                </P>
                <P>
                    This filing is accessible on-line at 
                    <E T="03">http://www.ferc.gov,</E>
                     using the “eLibrary” link and is available for review in the Commission's Public Reference Room in Washington, DC. There is an “eSubscription” link on the website that enables subscribers to receive email notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please email 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5:00 p.m. Eastern time on June 3, 2019.
                </P>
                <SIG>
                    <DATED>Dated: May 6, 2019.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09716 Filed 5-10-19; 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. CP19-220-000]</DEPDOC>
                <SUBJECT>National Fuel Gas Supply Corporation; Notice of Request Under Blanket Authorization</SUBJECT>
                <P>
                    Take notice that on April 24, 2019, National Fuel Gas Supply Corporation (National Fuel), 6363 Main Street, Williamsville, New York 14221, filed in Docket No. CP19-220-000, a Prior Notice Request pursuant to sections 157.205, 157.208, 157.210, and 157.216 of the Commission's regulations under the Natural Gas Act (NGA), and National Fuel's blanket certificate issued in Docket No. CP83-4-000, requesting authorization to abandon and replace 9.6 miles of 12-inch-diameter bare steel pipeline (Line FM100) and construct certain related natural gas facilities located in Jefferson and Elk Counties, Pennsylvania, as part of its Brockway Modernization Project. National Fuel states the proposed replacement is part of a multi-year modernization program to enhance the reliability and safety of its system, all as more fully described in the application which is on file with the Commission and open to public inspection. The filing may also be viewed on the web at 
                    <E T="03">http://www.ferc.gov</E>
                     using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field to access the document. For assistance, contact FERC at 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or call toll-free, (866) 208-3676 or TTY, (202) 502-8659.
                </P>
                <P>
                    Any questions regarding this prior notice should be directed to Jeffrey B. Same, Attorney, National Fuel Gas Supply Corporation, 6363 Main Street, Williamsville, New York 14221-5887, by telephone at (716) 857-7507, or by email at 
                    <E T="03">samej@natfuel.com.</E>
                </P>
                <P>
                    Specifically, National Fuel proposes that the replacement project will include: (i) The installation of approximately 9.7 miles of 12-inch-diameter coated steel pipeline; (ii) the 
                    <PRTPAGE P="20879"/>
                    installation of approximately 0.4 miles of 6-inch-diameter pipeline lateral; (iii) the installation of a remote controlled mainline block valve; (iv) the installation of a new pig launcher/receiver; and (v) modifications to an existing metering station. National Fuel plans to begin construction commencing in summer 2019 and anticipates the facilities will be placed in-service by December 2019. National Fuel estimates the cost of the Brockway Modernization Project to be $24.2 million.
                </P>
                <P>Any person or the Commission's staff may, within 60 days after issuance of the instant notice by the Commission, file pursuant to Rule 214 of the Commission's Procedural Rules (18 CFR 385.214) a motion to intervene or notice of intervention and pursuant to section 157.205 of the regulations under the NGA (18 CFR 157.205), a protest to the request. If no protest is filed within the time allowed therefore, the proposed activity shall be deemed to be authorized effective the day after the time allowed for filing a protest. If a protest is filed and not withdrawn within 30 days after the allowed time for filing a protest, the instant request shall be treated as an application for authorization pursuant to section 7 of the NGA.</P>
                <P>Pursuant to section 157.9 of the Commission's rules, 18 CFR 157.9, within 90 days of this Notice the Commission staff will either: Complete its environmental assessment (EA) and place it into the Commission's public record (eLibrary) for this proceeding; or issue a Notice of Schedule for Environmental Review. If a Notice of Schedule for Environmental Review is issued, it will indicate, among other milestones, the anticipated date for the Commission staff's issuance of the EA for this proposal. The filing of the EA in the Commission's public record for this proceeding or the issuance of a Notice of Schedule for Environmental Review will serve to notify federal and state agencies of the timing for the completion of all necessary reviews, and the subsequent need to complete all federal authorizations within 90 days of the date of issuance of the Commission staff's EA.</P>
                <P>Persons who wish to comment only on the environmental review of this project should submit an original and two copies of their comments to the Secretary of the Commission. Environmental commenters will be placed on the Commission's environmental mailing list and will be notified of any meetings associated with the Commission's environmental review process. Environmental commenters will not be required to serve copies of filed documents on all other parties. However, the non-party commenters will not receive copies of all documents filed by other parties or issued by the Commission and will not have the right to seek court review of the Commission's final order.</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 should submit an original and 3 copies of the protest or intervention to the Federal Energy regulatory Commission, 888 First Street NE, Washington, DC 20426.
                </P>
                <SIG>
                    <DATED>Dated: May 6, 2019.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09715 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-R09-OAR-2016-0580; FRL-9993-50-Region 9]</DEPDOC>
                <SUBJECT>General Permit Under the Federal Indian Country Minor New Source Review Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of final permit.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Environmental Protection Agency (EPA), Region IX is issuing a general permit for use in Indian country within California pursuant to the Clean Air Act (CAA) Federal Indian Country Minor New Source Review (NSR) program for new and modified minor sources. The general permit is for a single source category, gasoline dispensing facilities (GDFs), and will be available in certain areas of Indian country that are within the geographical boundaries of California. This includes areas located in an Indian reservation or in another area of Indian country over which an Indian tribe, or the EPA, has demonstrated that the tribe has jurisdiction and where there is no EPA-approved minor NSR program in place. The EPA is finalizing this general permit as a streamlined option that owners or operators may elect to use for the CAA minor NSR preconstruction permitting of certain minor sources that construct or modify in Indian country and belong to the GDF source category.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This permit becomes effective, and available for sources to request coverage, June 12, 2019, unless a petition for review of the final permit is properly and timely filed with the EPA Environmental Appeals Board (EAB) per 40 CFR 49.159(d). In that case, the permit's effectiveness will be stayed and construction cannot be authorized under this permit until agency review procedures are exhausted under 40 CFR 49.159(d) and the Regional Administrator subsequently issues a final permit. The general permit becomes effective and applicable as to a particular stationary source upon issuance by the reviewing authority of an Approval of the Request for Coverage for that particular stationary source.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Documents relevant to the above-referenced permit are available for public inspection during normal business hours at the following address: U.S. Environmental Protection Agency, Region IX, 75 Hawthorne Street, San Francisco, CA 94105-3901. To arrange for viewing of these documents, call Lisa Beckham at (415) 972-3811. Due to building security procedures, at least 24 hours advance notice is required.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Lisa Beckham, EPA Region IX, (415) 972-3811, 
                        <E T="03">beckham.lisa@epa.gov.</E>
                         Key portions of the administrative record for this decision, including the general permit, Technical Support Document, and Request for Coverage form, are available through a link at EPA Region IX's website at 
                        <E T="03">https://www.epa.gov/caa-permitting/california-tribal-gasoline-permits.</E>
                         The administrative record for this action is available through 
                        <E T="03">www.regulations.gov</E>
                         (Docket ID #EPA-R09-OAR-2016-0580).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Final Decision</HD>
                <P>
                    The EPA, Region IX is issuing a general permit for use in Indian country within California pursuant to the CAA Federal Indian Country Minor NSR program for new and modified minor sources at 40 CFR 49.151 through 49.161. The general permit is for a single source category, gasoline dispensing facilities (GDFs), and will be available in certain areas of Indian country that are within the geographical boundaries of California. This includes areas located in an Indian reservation or in another area of Indian country (as defined in 18 U.S.C. 1151) over which an Indian tribe, or the EPA, has demonstrated that the tribe has jurisdiction and where there is no EPA-approved minor NSR program in place. The EPA is issuing this general permit as a streamlined option that owners or operators may elect to use for CAA minor NSR preconstruction permitting of certain minor sources that construct or modify in Indian country and belong to the GDF source category.
                    <PRTPAGE P="20880"/>
                </P>
                <P>A gasoline dispensing facility, or GDF, is any stationary source, such as a gas station, that dispenses gasoline into the fuel tank of a motor vehicle, motor vehicle engine, nonroad vehicle or nonroad engine. Types of GDFs that potentially may use this general permit include, but are not limited to, facilities that dispense gasoline into on- and off-road, street, or highway motor vehicles, lawn equipment, boats, test engines, landscaping equipment, generators, pumps, and other gasoline-fueled engines and equipment. New or modified GDF sources with the potential to emit regulated NSR pollutants over thresholds specified in the Federal Indian Country Minor NSR program regulations at 40 CFR 49.153, and located within the geographic boundaries of California and on an Indian reservation or in another area of Indian country over which an Indian tribe or the EPA has demonstrated that the tribe has jurisdiction, are currently subject to permitting requirements under this EPA minor NSR program.</P>
                <P>The general permit that is the subject of this notice is intended to provide a streamlined permitting option for owners and operators of qualifying GDFs to use to meet the requirements of this EPA minor NSR program. However, owners and operators of such GDFs may choose to apply to the EPA for a traditional source-specific permit to meet the preconstruction requirements of this permitting program in lieu of requesting coverage under the general permit.</P>
                <P>
                    The primary pollutant of concern for GDFs that may use this general permit is volatile organic compounds (VOC), which are emitted from storage tanks and gasoline dispensing units at GDFs. Some GDFs may also have emergency engines, which emit VOC, nitrogen oxides, carbon monoxide, particulate matter (PM), PM less than or equal to 10 µm in diameter (PM
                    <E T="52">10</E>
                    ), and PM less than or equal to 2.5 μm in diameter (PM
                    <E T="52">2.5</E>
                    ). Except for VOC emissions, emissions of all other regulated NSR pollutants from new or modified GDF sources that may use the general permit are expected to be below the minor NSR permitting thresholds in 40 CFR 49.153.
                </P>
                <P>
                    This general permit regulates VOC emissions from GDFs and includes emission limitations that require each GDF to control emissions from storage tanks during unloading of the gasoline cargo from the tanker truck, using what are known as Stage I controls. In addition, the general permit requires GDFs in ozone nonattainment areas classified as serious, severe, or extreme to limit VOC emissions caused from vehicle refueling by using pump-based controls known as Stage II controls. There are also limits on the amount of gasoline each GDF can dispense in a 12-month period: 25,000,000 million gallons in ozone attainment/unclassifiable areas, marginal ozone nonattainment areas, and moderate ozone nonattainment areas; and 15,000,000 gallons in serious, severe, and extreme ozone nonattainment areas. The emission limitations in the general permit are expected to generally limit emissions of VOC from a new or modified GDF to less than 30 tons per year (tpy) in attainment areas and marginal or moderate ozone nonattainment areas and 9 tpy in serious, severe, and extreme ozone nonattainment areas. The detailed emission limitations are included in the general permit and discussed in detail in our Technical Support Document. These and other key documents related to this general permit are available online here: 
                    <E T="03">https://www.epa.gov/caa-permitting/california-tribal-gasoline-permits.</E>
                </P>
                <HD SOURCE="HD1">Public Comments</HD>
                <P>
                    The public comment period started on September 30, 2016 and ended on January 31, 2017. A public hearing was held on November 30, 2016 at the 
                    <E T="03">EPA Region IX offices in San Francisco, California.</E>
                     The EPA considered all comments received during the public comment period in making its final permit decision. The submitted comments and the EPA's responses are available as part of the administrative record for this action.
                </P>
                <HD SOURCE="HD1">Administrative Record</HD>
                <P>
                    The final general permit and all other supporting information are available through 
                    <E T="03">www.regulations.gov</E>
                     under Docket ID No. EPA-R09-OAR-2016-0580.The administrative record for this action may also be viewed in person, Monday through Friday (excluding Federal holidays) from 9:00 a.m. to 4:00 p.m., at the EPA Region IX address above. Due to building security procedures, please call Lisa Beckham at (415) 972-3811 at least 24 hours in advance to arrange a visit. Lisa Beckham can also be reached through EPA Region IX's toll-free general information line at (866) 372-9378.
                </P>
                <HD SOURCE="HD1">Permit Appeal</HD>
                <P>In accordance with 40 CFR 49.159, within 30 days after a final permit decision has been issued, any person who filed comments on the draft permit or participated in the public hearing may petition the EAB to review any condition of the permit decision. Any person who failed to file comments or to participate in the public hearing may petition for administrative review only to the extent that the changes from the draft to the final permit or other new grounds were not reasonably ascertainable during the public comment period. The 30-day period within which a person may request review under this section begins with service of notice of the final permit decision. A petition to the EAB is a prerequisite to seeking judicial review of the final agency action under Section 307(b) of the CAA. For purposes of judicial review, final agency action occurs when we deny or issue a final permit and agency review procedures are exhausted. Following an appeal to the EAB, the EPA will issue a final permit decision as specified in 40 CFR 49.159(d)(8).</P>
                <HD SOURCE="HD1">Additional Information</HD>
                <P>
                    If you have questions, or if you wish to obtain further information, please contact Lisa Beckham at (415) 972-3811, toll-free at (866) 372-9378, via email at 
                    <E T="03">R9airpermits@epa.gov,</E>
                     or at the mailing address above. If you would like to be added to our mailing list to receive future information about this general permit or other permit decisions issued by EPA Region IX, please contact Lisa Beckham, or visit the EPA Region IX website at 
                    <E T="03">http://www2.epa.gov/caa-permitting/tribal-nsr-permits-region-9.</E>
                </P>
                <P>Please bring the foregoing notice to the attention of all persons who would be interested in this matter.</P>
                <SIG>
                    <DATED>Dated: May 1, 2019.</DATED>
                    <NAME>Elizabeth J. Adams,</NAME>
                    <TITLE>Director, Air Division, Region IX.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09831 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OAR-2003-0041; FRL-9993-35-OAR]</DEPDOC>
                <SUBJECT>Proposed Information Collection Request; Comment Request; RadNet (Renewal)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Environmental Protection Agency is planning to submit an information collection request (ICR), “RadNet” (EPA ICR No. 0877.14, OMB Control No. 2060-0015) to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act (44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        ). Before doing so, EPA is 
                        <PRTPAGE P="20881"/>
                        soliciting public comments on specific aspects of the proposed information collection as described below. This is a proposed extension of the ICR, which is currently approved through January 31, 2020. An Agency may not conduct or sponsor and a person is not required to respond to a collection of information unless it displays a currently valid OMB control number.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before July 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments, referencing Docket ID No. EPA-HQ-OAR-2003-0041, online using 
                        <E T="03">www.regulations.gov</E>
                         (our preferred method), or by mail to: EPA Docket Center, Environmental Protection Agency, Mail Code 28221T, 1200 Pennsylvania Ave. NW, Washington, DC 20460.
                    </P>
                    <P>EPA's policy is that all comments received will be included in the public docket without change including any personal information provided, unless the comment includes profanity, threats, information claimed to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        John Griggs, OAR/ORIA/NAREL, Environmental Protection Agency, National Analytical Radiation Environmental Laboratory, 540 South Morris Ave., Montgomery, AL 36115; telephone number: (334) 270-3400; fax number: (334) 270-3450; email address: 
                        <E T="03">griggs.john@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Supporting documents which explain in detail the information that the EPA will be collecting are available in the public docket for this ICR. The docket can be viewed online at 
                    <E T="03">www.regulations.gov</E>
                     or in person at the EPA Docket Center, WJC West, Room 3334, 1301 Constitution Ave. NW, Washington, DC. The telephone number for the Docket Center is 202-566-1744. For additional information about EPA's public docket, visit 
                    <E T="03">http://www.epa.gov/dockets.</E>
                </P>
                <P>
                    Pursuant to section 3506(c)(2)(A) of the PRA, EPA is soliciting comments and information to enable it to: (i) Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the Agency, including whether the information will have practical utility; (ii) evaluate the accuracy of the Agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; (iii) enhance the quality, utility, and clarity of the information to be collected; and (iv) minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses. EPA will consider the comments received and amend the ICR as appropriate. The final ICR package will then be submitted to OMB for review and approval. At that time, EPA will issue another 
                    <E T="04">Federal Register</E>
                     notice to announce the submission of the ICR to OMB and the opportunity to submit additional comments to OMB.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     RadNet is a national network of stations collecting environmental media that include air, precipitation, and drinking water. Samples are sent to EPA's National Analytical Radiation Environmental Lab (NAREL) in Montgomery, Alabama, where they are analyzed for radioactivity. RadNet provides emergency response/homeland security and ambient monitoring information on levels of environmental radiation across the nation. All stations operators participate in RadNet voluntarily. Station operators complete information forms that accompany the samples. The forms request information pertaining to sample type, sample location, start and stop date and times for sampling, length of sampling period, and volume represented. Data from RadNet are made available regularly on the Agency websites—Envirofacts and the EPA website 
                    <E T="03">www.epa.gov/radnet.</E>
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     RadNet Air Particulate Sample (EPA Form 5900-24); RadNet Precipitation Report Form (EPA Form 5900-27); RadNet Drinking Water Report Form (EPA Form 5900-29); and RadNet Supply Request Form (EPA Form 5900-23).
                </P>
                <P>
                    <E T="03">Respondents/affected entities:</E>
                     Primarily State and Local Officials.
                </P>
                <P>
                    <E T="03">Respondent's obligation to respond:</E>
                     Voluntary.
                </P>
                <P>
                    <E T="03">Estimated number of respondents:</E>
                     237.
                </P>
                <P>
                    <E T="03">Frequency of response:</E>
                     Varies depending upon sample media type. Responses vary from twice weekly to quarterly.
                </P>
                <P>
                    <E T="03">Total estimated burden:</E>
                     3721 hours (per year). Burden is defined at 5 CFR 1320.03(b).
                </P>
                <P>
                    <E T="03">Total estimated cost:</E>
                     $2,510,235 (per year), includes annualized capital costs, operational costs, and maintenance costs.
                </P>
                <P>
                    <E T="03">Changes in estimates:</E>
                     There is a decrease of five hours in the total estimated respondent burden compared with the ICR currently approved by OMB. This decrease is minimal and shows the program is in maturity and is expected to operate with minimal change.
                </P>
                <SIG>
                    <DATED>Dated: April 30, 2019.</DATED>
                    <NAME>Jonathan D. Edwards,</NAME>
                    <TITLE>Director, Office of Radiation and Indoor Air.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09833 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[FRL-9993-46-Region 1]</DEPDOC>
                <SUBJECT>2019 Spring Joint Meeting of the Ozone Transport Commission and the Mid-Atlantic Northeast Visibility Union</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The United States Environmental Protection Agency (EPA) is announcing the joint 2019 Spring Meeting of the Ozone Transport Commission (OTC) and the Mid-Atlantic Northeast Visibility Union (MANE-VU). The meeting agenda will include topics regarding reducing ground-level ozone precursors and matters relative to Regional Haze and visibility improvement in Federal Class I areas in a multi-pollutant context.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held on June 11, 2019 starting at 9:30 a.m. and ending at 4:00 p.m.</P>
                    <P>
                        <E T="03">Location:</E>
                         Hotel DuPont, 42 West 11th Street, Wilmington, DE 21202, 302-594-3100.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P SOURCE="NPAR">
                        <E T="03">For documents and press inquiries contact:</E>
                         Ozone Transport Commission, 800 Maine Avenue SW, Suite 200, Washington, DC 20024; (202) 318-0190; email: 
                        <E T="03">ozone@otcair.org;</E>
                         website: 
                        <E T="03">http://www.otcair.org.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Clean Air Act Amendments of 1990 contain Section 184 provisions for the Control of Interstate Ozone Air Pollution. Section 184(a) establishes an Ozone Transport Region (OTR) comprised of the States of Connecticut, Delaware, Maine, Maryland, Massachusetts, New Hampshire, New Jersey, New York, Pennsylvania, Rhode Island, Vermont, parts of Virginia and the District of Columbia. The purpose of the OTC is to address ground-level ozone formation, transport, and control within the OTR.</P>
                <P>
                    The Mid-Atlantic/Northeast Visibility Union (MANE-VU) was formed at in 2001, in response to EPA's issuance of the Regional Haze rule. MANE-VU's members include: Connecticut, Delaware, the District of Columbia, Maine, Maryland, Massachusetts, New 
                    <PRTPAGE P="20882"/>
                    Hampshire, New Jersey, New York, Pennsylvania, Rhode Island, Vermont, the Penobscot Indian Nation, the St. Regis Mohawk Tribe along with EPA and Federal Land Managers.
                </P>
                <P>
                    <E T="03">Type of Meeting:</E>
                     Open.
                </P>
                <P>
                    <E T="03">Agenda:</E>
                     Copies of the final agenda will be available from the OTC office (202) 318-0190; by email: 
                    <E T="03">ozone@otcair.org</E>
                     or via the OTC website at 
                    <E T="03">http://www.otcair.org.</E>
                </P>
                <SIG>
                    <DATED>Dated: May 6, 2019.</DATED>
                    <NAME>Deborah Szaro,</NAME>
                    <TITLE>Acting Regional Administrator, EPA Region 1.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09774 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OECA-2019-0204; FRL-9992-91-OECA]</DEPDOC>
                <SUBJECT>Enforcement and Compliance: Enhancing EPA-State Planning and Communication</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Environmental Protection Agency (EPA) is soliciting public comment on its policy of 
                        <E T="03">Enhancing Planning and Communication Between the EPA and States in Civil Enforcement and Compliance Assurance Work.</E>
                         The draft Policy is available for review at 
                        <E T="03">https://www.epa.gov/sites/production/files/2019-04/documents/guidance-enhancingregionalstatecommunicationoncompliance-190422.pdf.</E>
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before June 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may send comments, identified by Docket ID No. EPA-HQ-OECA-2019-0204; to 
                        <E T="03">https://www.regulations.gov.</E>
                         Follow the online instructions for submitting comments.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the Docket ID No. for this notice. Comments received will be posted without change to 
                        <E T="03">https://www.regulations.gov/,</E>
                         including any personal information provided. For detailed instructions on sending comments and additional information on the notice process, see the “Written Comments” heading of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kathleen H. Johnson, Senior Policy Advisor, Mail Code: 2261A, Environmental Protection Agency, 1200 Pennsylvania Ave. NW, Washington, DC 20460; telephone number: (202) 564-5401; fax number: (202) 501-3842; email address: 
                        <E T="03">Johnson.Kathleen@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In January 2018, the Office of Enforcement and Compliance Assurance issued an Interim Guidance document to help move the Agency toward a more collaborative partnership between EPA and states, with the expectation that the guidance would be later updated. The interim document may be viewed at 
                    <E T="03">https://www.epa.gov/sites/production/files/2018-01/documents/guidance-enhancingregionalstatecommunicationoncompliance.pdf.</E>
                </P>
                <P>The EPA is seeking comments on a policy that would replace that Interim Guidance and would set out expectations and procedures for enhancing planning and communication on civil enforcement work between the EPA and States that are implementing Federal environmental programs. While this policy is focused on the EPA's work with States that are approved to implement Federal programs, the EPA also is seeking comments on applying these planning and communication practices when working with federally-recognized Indian tribes, territories, and local governments that have received approval to implement Federal programs. This is an Agency planning document and would not impose any legally binding requirements on EPA or any outside parties.</P>
                <P>
                    Submit your comments, identified by Docket ID No. EPA-HQ-OECA-2019-0204; at 
                    <E T="03">https://www.regulations.gov.</E>
                     Once submitted, comments cannot be edited or removed from 
                    <E T="03">Regulations.gov.</E>
                     The EPA may publish any comment received to its public docket. Do not submit electronically any information you consider to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Multimedia submissions (audio, video, etc.) must be accompanied by a written comment. The written comment is considered the official comment and should include discussion of all points you wish to make. The EPA will generally not consider comments or comment contents located outside of the primary submission (
                    <E T="03">i.e.,</E>
                     on the web, cloud, or other file sharing system). For additional submission methods, the full EPA public comment policy, information about CBI or multimedia submissions, and general guidance on making effective comments, please visit 
                    <E T="03">https://www.epa.gov/dockets/commenting-epa-dockets.</E>
                </P>
                <P>The EPA will consider all timely-submitted public comments in determining whether and how to finalize this policy statement.</P>
                <SIG>
                    <DATED>Dated: April 25, 2019.</DATED>
                    <NAME>Susan Parker Bodine,</NAME>
                    <TITLE>Assistant Administrator, Office of Enforcement and Compliance Assurance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09764 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OPP-2018-0014; FRL-9993-14]</DEPDOC>
                <SUBJECT>Product Cancellation Order for Certain Pesticide Registrations and Amendments To Terminate Uses</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice announces EPA's order for the cancellations and amendments to terminate uses, voluntarily requested by the registrants and accepted by the Agency, of the products listed in Table 1, Table 1A and Table 2 of Unit II, pursuant to the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA). This cancellation order follows a March 5, 2019 
                        <E T="04">Federal Register</E>
                         Notice of Receipt of Requests from the registrants listed in Table 3 of Unit II to voluntarily cancel and amend to terminate uses of these product registrations. In the March 5, 2019 notice, EPA indicated that it would issue an order implementing the cancellations and amendments to terminate uses, unless the Agency received substantive comments within the 30-day comment period that would merit its further review of these requests, or unless the registrants withdrew their requests. The Agency received two comments on the notice, to remove their registrations from the cancellation order notice. The registrants for 4959-16, 4959-36 and 33753-31, requested via letter to withdraw their registrations from this notice. Accordingly, EPA hereby issues in this notice a cancellation order granting the requested cancellations and amendments to terminate uses. Any distribution, sale, or use of the products subject to this cancellation order is permitted only in accordance with the terms of this order, including any existing stocks provisions.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The cancellations and amendments are effective May 13, 2019.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Christopher Green, Information Technology and Resources Management 
                        <PRTPAGE P="20883"/>
                        Division (7502P), Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Ave. NW, Washington, DC 20460-0001; telephone number: (703) 341-0367; email address: 
                        <E T="03">green.christopher@epa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. General Information</HD>
                <HD SOURCE="HD2">A. Does this action apply to me?</HD>
                <P>This action is directed to the public in general, and may be of interest to a wide range of stakeholders including environmental, human health, and agricultural advocates; the chemical industry; pesticide users; and members of the public interested in the sale, distribution, or use of pesticides. Since others also may be interested, the Agency has not attempted to describe all the specific entities that may be affected by this action.</P>
                <HD SOURCE="HD2">B. How can I get copies of this document and other related information?</HD>
                <P>
                    The docket for this action, identified by docket identification (ID) number EPA-HQ-OPP-2018-0014, is available at 
                    <E T="03">http://www.regulations.gov</E>
                     or at the Office of Pesticide Programs Regulatory Public Docket (OPP Docket) in the Environmental Protection Agency Docket Center (EPA/DC), West William Jefferson Clinton Bldg., Rm. 3334, 1301 Constitution Ave. NW, Washington, DC 20460-0001. The Public Reading Room is open from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. The telephone number for the Public Reading Room is (202) 566-1744, and the telephone number for the OPP Docket is (703) 305-5805. Please review the visitor instructions and additional information about the docket available at 
                    <E T="03">http://www.epa.gov/dockets</E>
                    .
                </P>
                <HD SOURCE="HD1">II. What action is the Agency taking?</HD>
                <P>This notice announces the cancellations and amendments to terminate uses, as requested by registrants, of products registered under FIFRA section 3 (7 U.S.C. 136a).</P>
                <P>These registrations are listed in sequence by registration number in Tables 1, 1A and 2 of this unit.</P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="xs60,12,r50,r75">
                    <TTITLE>Table 1—Product Cancellations</TTITLE>
                    <BOXHD>
                        <CHED H="1">Registration No.</CHED>
                        <CHED H="1">Company No.</CHED>
                        <CHED H="1">Product name</CHED>
                        <CHED H="1">Active ingredients</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">279-9532</ENT>
                        <ENT>279</ENT>
                        <ENT>Appeal EC Herbicide</ENT>
                        <ENT>Fluthiacet-methyl.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">279-9559</ENT>
                        <ENT>279</ENT>
                        <ENT>F9878-1 Termite Bait</ENT>
                        <ENT>Lufenuron.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">352-596</ENT>
                        <ENT>352</ENT>
                        <ENT>DuPont Canopy SP Herbicide</ENT>
                        <ENT>Metribuzin &amp; Chlorimuron.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">352-843</ENT>
                        <ENT>352</ENT>
                        <ENT>DuPont Leadoff (MP) Herbicide</ENT>
                        <ENT>Thifensulfuron &amp; Rimsulfuron.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">432-1415</ENT>
                        <ENT>432</ENT>
                        <ENT>Allectus SC Insecticide</ENT>
                        <ENT>Bifenthrin &amp; Imidacloprid.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">432-1578</ENT>
                        <ENT>432</ENT>
                        <ENT>Lineage Clearstand</ENT>
                        <ENT>Metsulfuron &amp; Imazapyr.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">875-185</ENT>
                        <ENT>875</ENT>
                        <ENT>Pro-Kleen</ENT>
                        <ENT>Phosphoric acid &amp; Dodecylbenzenesulfonic acid.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1258-1276</ENT>
                        <ENT>1258</ENT>
                        <ENT>Endure</ENT>
                        <ENT>Boron sodium oxide (B4Na2O7), pentahydrate.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1769-287</ENT>
                        <ENT>1769</ENT>
                        <ENT>Everbrite Germicidal Cleaner</ENT>
                        <ENT>Alkyl* dimethyl benzyl ammonium chloride *(60%C14, 30%C16, 5%C18, 5%C12) &amp; Alkyl* dimethyl ethylbenzyl ammonium chloride *(68%C12, 32%C14).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3525-90</ENT>
                        <ENT>3525</ENT>
                        <ENT>Coastal Cal Jet Algaecide Tablets</ENT>
                        <ENT>Dodecylbenzyl trimethyl ammonium chloride.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3525-92</ENT>
                        <ENT>3525</ENT>
                        <ENT>Coastal Pinetex Disinfectant Coef. 5</ENT>
                        <ENT>Alkyl* dimethyl benzyl ammonium chloride *(58%C14, 28%C16, 14%C12).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3862-186</ENT>
                        <ENT>3862</ENT>
                        <ENT>805 Sanitizer Cleaner for Soft Ice Cream Freezers</ENT>
                        <ENT>Sodium hypochlorite.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5185-299</ENT>
                        <ENT>5185</ENT>
                        <ENT>Bio-Chlor LB-1000</ENT>
                        <ENT>Sodium hypochlorite.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9428-6</ENT>
                        <ENT>9428</ENT>
                        <ENT>Sun-Pine 8.7% Pine Oil Disinfectant Cleaner</ENT>
                        <ENT>Pine oil.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10324-16</ENT>
                        <ENT>10324</ENT>
                        <ENT>Maquat MQ 2525-80%</ENT>
                        <ENT>Alkyl* dimethyl benzyl ammonium chloride *(60%C14, 30%C16, 5%C18, 5%C12) &amp; Alkyl* dimethyl ethylbenzyl ammonium chloride *(50%C12, 30%C14, 17%C16, 3%C18).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10324-182</ENT>
                        <ENT>10324</ENT>
                        <ENT>Maquat MQ2525M-50 DWP</ENT>
                        <ENT>Alkyl* dimethyl ethylbenzyl ammonium chloride *(68%C12, 32%C14) &amp; Alkyl* dimethyl benzyl ammonium chloride *(60%C14, 30%C16, 5%C18, 5%C12).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">33981-10</ENT>
                        <ENT>33981</ENT>
                        <ENT>Sodium Hypochlorite Solution 16% EP</ENT>
                        <ENT>Sodium hypochlorite.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">33981-11</ENT>
                        <ENT>33981</ENT>
                        <ENT>Sodium Hypochlorite MP16%</ENT>
                        <ENT>Sodium hypochlorite.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">33981-20001</ENT>
                        <ENT>33981</ENT>
                        <ENT>Sodium Hypochlorite Solution</ENT>
                        <ENT>Sodium hypochlorite.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">33981-20002</ENT>
                        <ENT>33981</ENT>
                        <ENT>Sodium Hypochlorite Solution 10%</ENT>
                        <ENT>Sodium hypochlorite.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">33981-20003</ENT>
                        <ENT>33981</ENT>
                        <ENT>Sodium Hypochlorite Solution 9.2%</ENT>
                        <ENT>Sodium hypochlorite.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">33981-20004</ENT>
                        <ENT>33981</ENT>
                        <ENT>Sodium Hypochlorite Solution 5.25%</ENT>
                        <ENT>Sodium hypochlorite.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">45309-3</ENT>
                        <ENT>45309</ENT>
                        <ENT>Aqua Clear Liqui-Clear</ENT>
                        <ENT>Sodium hypochlorite.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">45309-95</ENT>
                        <ENT>45309</ENT>
                        <ENT>Aqua Clear Cal-Chlor</ENT>
                        <ENT>Calcium hypochlorite.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">47371-106</ENT>
                        <ENT>47371</ENT>
                        <ENT>Jaq Swimming Pool Algaecide</ENT>
                        <ENT>Alkyl* dimethyl benzyl ammonium chloride *(95%C14, 3%C12, 2%C16).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">65331-7</ENT>
                        <ENT>65331</ENT>
                        <ENT>Certifect for Dogs</ENT>
                        <ENT>Amitraz; S-Methoprene &amp; Fipronil.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">67262-6</ENT>
                        <ENT>67262</ENT>
                        <ENT>Aqua Chem Balanced for Clean Pools Liquid Chlorinizor</ENT>
                        <ENT>Sodium hypochlorite.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">70506-239</ENT>
                        <ENT>70506</ENT>
                        <ENT>Bonfire Herbicide</ENT>
                        <ENT>Paraquat dichloride.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">70529-3</ENT>
                        <ENT>70529</ENT>
                        <ENT>Aqua Chlor Sodium Hypochlorite 12.5%</ENT>
                        <ENT>Sodium hypochlorite.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">75341-14</ENT>
                        <ENT>75341</ENT>
                        <ENT>MP400-EXT (Alternate), ORD-X240 (Active)</ENT>
                        <ENT>Borax (B4Na2O7.10H2O); Bifenthrin; Tebuconazole &amp; Copper, bis(8-quinolinolato-N1,O8)-,</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FL-180003</ENT>
                        <ENT>100</ENT>
                        <ENT>A13617V Turf Herbicide</ENT>
                        <ENT>Pinoxaden.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OR-070018</ENT>
                        <ENT>66222</ENT>
                        <ENT>Diazinon AG500</ENT>
                        <ENT>Diazinon.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OR-170013</ENT>
                        <ENT>80286</ENT>
                        <ENT>Splat LBAM HD-O</ENT>
                        <ENT>(E)-11-Tetradecen-1-ol acetate &amp; (E,E)-9,11-Tetradecadien-1-ol acetate.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WI-130011</ENT>
                        <ENT>50534</ENT>
                        <ENT>Bravo ZN</ENT>
                        <ENT>Chlorothalonil.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WI-130013</ENT>
                        <ENT>50534</ENT>
                        <ENT>Bravo 720</ENT>
                        <ENT>Chlorothalonil.</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="20884"/>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="xs60,12,r50,r75">
                    <TTITLE>Table 1A—Product Cancellation</TTITLE>
                    <BOXHD>
                        <CHED H="1">Registration No.</CHED>
                        <CHED H="1">Company No.</CHED>
                        <CHED H="1">Product name</CHED>
                        <CHED H="1">Active ingredients</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">58185-34</ENT>
                        <ENT>58185</ENT>
                        <ENT>Revoke Pre-Emergent Herbicide</ENT>
                        <ENT>Pendimethalin &amp; Oxadiazon.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The registrant of the request in Table 1A, requests to cancel the registration at the Federal level by December 31, 2019.</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="xs60,12,r50,r50,r75">
                    <TTITLE>Table 2—Product Registration Amendments To Terminate Uses</TTITLE>
                    <BOXHD>
                        <CHED H="1">Registration No.</CHED>
                        <CHED H="1">Company No.</CHED>
                        <CHED H="1">Product name</CHED>
                        <CHED H="1">Active ingredients</CHED>
                        <CHED H="1">Uses to be terminated</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1381-255</ENT>
                        <ENT>1381</ENT>
                        <ENT>Saddle Up</ENT>
                        <ENT>2,4-D &amp; Dicamba</ENT>
                        <ENT>Forest management use pattern.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">45385-99</ENT>
                        <ENT>45385</ENT>
                        <ENT>Cenol 0.5% Multipurpose Insecticide</ENT>
                        <ENT>Permethrin</ENT>
                        <ENT>Food animals (livestock).</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Table 3 of this unit includes the names and addresses of record for all registrants of the products in Tables 1, 1A and 2 of this unit, in sequence by EPA company number. This number corresponds to the first part of the EPA registration numbers of the products listed above.</P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="xs60,r200">
                    <TTITLE>Table 3—Registrants of Cancelled and Amended Products</TTITLE>
                    <BOXHD>
                        <CHED H="1">EPA company No.</CHED>
                        <CHED H="1">Company name and address</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">100</ENT>
                        <ENT>Syngenta Crop Protection, LLC, 410 Swing Road, P.O. Box 18300, Greensboro, NC 27419-8300.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">279</ENT>
                        <ENT>FMC Corporation, 2929 Walnut Street, Philadelphia, PA 19104.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">352</ENT>
                        <ENT>E.I. Du Pont De Nemours &amp; Company, Attn: Manager, US Registration, DuPont Crop Protection, Chestnut Run Plaza (CRP 720/2E5), 974 Centre Rd., Wilmington, DE 19805.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">432</ENT>
                        <ENT>Bayer Environmental Science, A Division of Bayer CropScience, LP, 5000 CentreGreen Way, Suite 400, Cary, NC 27513.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">875</ENT>
                        <ENT>Diversey, Inc., P.O. Box 19747, Charlotte, NC 28219-0747.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1258</ENT>
                        <ENT>Arch Chemicals, Inc., 1200 Bluegrass Lakes Parkway, Alpharetta, GA 30004.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1381</ENT>
                        <ENT>Winfield Solutions, LLC, P.O. Box 64589, St. Paul, MN 55164-0589.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1769</ENT>
                        <ENT>NCH Corp, 2727 Chemsearch Blvd., Irving, TX 75062.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3525</ENT>
                        <ENT>Qualco, Inc., 225 Passaic St., Passaic, NJ 07055.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3862</ENT>
                        <ENT>ABC Compounding Co., Inc., P.O. Box 80729, Conyers, GA 30013.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5185</ENT>
                        <ENT>Bio-Lab, Inc., P.O. Box 300002, Lawrenceville, GA 30049-1002.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9428</ENT>
                        <ENT>Sun-Pine Corporation, P.O. Box 287, Brandon, MS 39043.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10324</ENT>
                        <ENT>Mason Chemical Company, 2744 E. Kemper Rd., Cincinnati, OH 45241.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">33981</ENT>
                        <ENT>K.A. Steel Chemicals, Inc., Agent Name: Delta Analytical Corporation, 12510 Prosperity Drive, Suite 160, Silver Spring, MD 20904.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">45309</ENT>
                        <ENT>Aqua Clear Industries, LLC, P.O. Box 2456, Suwanee, GA 30024-0980.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">45385</ENT>
                        <ENT>CTX-Cenol, Inc., 1393 East Highland Rd., Twinsburg, OH 44087.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">47371</ENT>
                        <ENT>H&amp;S Chemicals Division of Lonza, Inc., 412 Mount Kemble Avenue, Suite 200S, Morristown, NJ 07960.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">50534</ENT>
                        <ENT>GB Biosciences, LLC, 410 Swing Road, P.O. Box 18300, Greensboro, NC 27419-8300.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">58185</ENT>
                        <ENT>Everris NA, Inc., P.O. Box 3310, Dublin, OH 43016.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">65331</ENT>
                        <ENT>Merial, Inc., 3239 Satellite Blvd., Bldg. 600, Office 6558-B, Duluth, GA 30096.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">66222</ENT>
                        <ENT>Makhteshim Agan of North America, Inc., D/B/A Adama, 3120 Highwoods Blvd., Suite 100, Raleigh, NC 27604.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">67262</ENT>
                        <ENT>Recreational Water Products, Inc., D/B/A Recreational Water Products, P.O. Box 1449, Buford, GA 30515-1449.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">70506</ENT>
                        <ENT>UPL NA, Inc., 630 Freedom Business Center, Suite 402, King of Prussia, PA 19406.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">70529</ENT>
                        <ENT>Chemical Formulators, Inc., Attn: Jim Palmer, 3901 NW 115 Avenue, Miami, FL 33178.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">75341</ENT>
                        <ENT>Osmose Utilities Services, Inc., 635 Hwy., 74 S., Peachtree City, GA 30269.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80286</ENT>
                        <ENT>ISCA Technologies, Inc., 1230 W. Spring Street, Riverside, CA 92507.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">III. Summary of Public Comments Received and Agency Response to Comments</HD>
                <P>The Agency received two comments on the notice, to remove their registrations from the cancellation order notice. West Agro, Inc., registrant of 4959-16 and 4959-36 and BASF Corporation, registrant of 33753-31, requested via letter to remove their registrations from this cancellation order because the requests were published in error and request that the registrations not be cancelled. For this reason, the Agency will not cancel these three registrations and the registrations have been removed from this notice.</P>
                <HD SOURCE="HD1">IV. Cancellation Order</HD>
                <P>
                    Pursuant to FIFRA section 6(f) (7 U.S.C. 136d(f)(1)), EPA hereby approves the requested cancellations and amendments to terminate uses of the registrations identified in Tables 1, 1A and 2 of Unit II. Accordingly, the Agency hereby orders that the product registrations identified in Tables 1, 1A and 2 of Unit II are canceled and amended to terminate the affected uses. The effective date of the cancellations that are subject of this notice is May 13, 2019. Any distribution, sale, or use of existing stocks of the products identified in Tables 1, 1A and 2 of Unit II in a manner inconsistent with any of the provisions for disposition of existing 
                    <PRTPAGE P="20885"/>
                    stocks set forth in Unit VI, will be a violation of FIFRA.
                </P>
                <HD SOURCE="HD1">V. What is the Agency's authority for taking this action?</HD>
                <P>
                    Section 6(f)(1) of FIFRA (7 U.S.C. 136d(f)(1)) provides that a registrant of a pesticide product may at any time request that any of its pesticide registrations be canceled or amended to terminate one or more uses. FIFRA further provides that, before acting on the request, EPA must publish a notice of receipt of any such request in the 
                    <E T="04">Federal Register</E>
                    . Thereafter, following the public comment period, the EPA Administrator may approve such a request. The notice of receipt for this action was published for comment in the 
                    <E T="04">Federal Register</E>
                     of March 05, 2019 (84 FR 7896) (FRL-9988-66). The comment period closed on April 04, 2019.
                </P>
                <HD SOURCE="HD1">VI. Provisions for Disposition of Existing Stocks</HD>
                <P>Existing stocks are those stocks of registered pesticide products which are currently in the United States and which were packaged, labeled, and released for shipment prior to the effective date of the action. The existing stocks provision for the products subject to this order is as follows.</P>
                <HD SOURCE="HD2">A. For Product: 432-1415</HD>
                <P>The registrant has requested to the Agency via letter to sell existing stocks for an 18-month period from the date of their letter dated, September 20, 2018, until March 20, 2020, for product 432-1415.</P>
                <HD SOURCE="HD2">B. For Product: 432-1578</HD>
                <P>The registrant has requested to the Agency via letter dated, November 14, 2017, to sell existing stocks for an 18-month period, until June 1, 2019, for product 432-1578.</P>
                <HD SOURCE="HD2">C. For Products: 10324-16 and 10324-182</HD>
                <P>The registrant has requested to the Agency via letter, to sell existing stocks for an 18-month period for products 10324-16 and 10324-182.</P>
                <P>
                    For all other voluntary cancellations, the registrants may continue to sell and distribute existing stocks of products listed in Table 1 and Table 1A until May 13, 2020, which is 1 year after publication of this cancellation order in the 
                    <E T="04">Federal Register</E>
                    . Thereafter, the registrants are prohibited from selling or distributing products listed in Table 1 and Table 1A of Unit II, except for export in accordance with FIFRA section 17 (7 U.S.C. 136o) or for proper disposal.
                </P>
                <P>
                    Now that EPA has approved product labels reflecting the requested amendments to terminate uses, registrants are permitted to sell or distribute products listed in Table 2 of Unit II, under the previously approved labeling until November 12, 2020, a period of 18 months after publication of the cancellation order in this 
                    <E T="04">Federal Register</E>
                    , unless other restrictions have been imposed. Thereafter, registrants will be prohibited from selling or distributing the products whose labels include the terminated uses identified in Table 2 of Unit II, except for export consistent with FIFRA section 17 or for proper disposal.
                </P>
                <P>Persons other than the registrant may sell, distribute, or use existing stocks of canceled products and products whose labels include the terminated uses until supplies are exhausted, provided that such sale, distribution, or use is consistent with the terms of the previously approved labeling on, or that accompanied, the canceled products and terminated uses.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        7 U.S.C. 136 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: May 6, 2019.</DATED>
                    <NAME>Delores Barber,</NAME>
                    <TITLE>Director, Information Technology and Resources Management Division, Office of Pesticide Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09778 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OPP-2017-0720; FRL-9993-04]</DEPDOC>
                <SUBJECT>Registration Review; Draft Human Health and/or Ecological Risk Assessments for Several Pesticides; Notice of Availability</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces the availability of EPA's draft human health and/or ecological risk assessments for the registration review of 2,4-DP-p, clopyralid, flumioxazin, and thiabendazole.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before July 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit your comments, to the docket identification (ID) number for the specific pesticide of interest provided in the Table in Unit IV, by one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov</E>
                        . Follow the online instructions for submitting comments. Do not submit electronically any information you consider to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         OPP Docket, Environmental Protection Agency Docket Center (EPA/DC), (28221T), 1200 Pennsylvania Ave. NW, Washington, DC 20460-0001.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         To make special arrangements for hand delivery or delivery of boxed information, please follow the instructions at 
                        <E T="03">http://www.epa.gov/dockets/contacts.html</E>
                        .
                    </P>
                    <P>
                        Additional instructions on commenting or visiting the docket, along with more information about dockets generally, are available at 
                        <E T="03">http://www.epa.gov/dockets</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P SOURCE="NPAR">
                        <E T="03">For pesticide specific information contact:</E>
                         The Chemical Review Manager for the pesticide of interest identified in the Table in Unit IV.
                    </P>
                    <P>
                        <E T="03">For general questions on the registration review program, contact:</E>
                         Dana Friedman, Pesticide Re-Evaluation Division (7508P), Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Ave. NW, Washington, DC 20460-0001; telephone number: (703) 347-8827; email address: 
                        <E T="03">friedman.dana@epa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. General Information</HD>
                <HD SOURCE="HD2">A. Does this action apply to me?</HD>
                <P>This action is directed to the public in general and may be of interest to a wide range of stakeholders including environmental, human health, farm worker, and agricultural advocates; the chemical industry; pesticide users; and members of the public interested in the sale, distribution, or use of pesticides. Since others also may be interested, the Agency has not attempted to describe all the specific entities that may be affected by this action. If you have any questions regarding the applicability of this action to a particular entity, consult the Chemical Review Manager identified in the Table in Unit IV.</P>
                <HD SOURCE="HD2">B. What should I consider as I prepare my comments for EPA?</HD>
                <P>
                    1. 
                    <E T="03">Submitting CBI.</E>
                     Do not submit this information to EPA through 
                    <E T="03">regulations.gov</E>
                     or email. Clearly mark the part or all of the information that you claim to be CBI. For CBI information in a disk or CD-ROM that you mail to EPA, mark the outside of the disk or CD-ROM as CBI and then identify electronically within the disk or CD-ROM the specific information that is claimed as CBI. In addition to one complete version of the comment that includes information claimed as CBI, a copy of the comment that does not 
                    <PRTPAGE P="20886"/>
                    contain the information claimed as CBI must be submitted for inclusion in the public docket. Information so marked will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.
                </P>
                <P>
                    2. 
                    <E T="03">Tips for preparing your comments.</E>
                     When preparing and submitting your comments, see the commenting tips at 
                    <E T="03">http://www.epa.gov/dockets/comments.html</E>
                    .
                </P>
                <P>
                    3. 
                    <E T="03">Environmental justice.</E>
                     EPA seeks to achieve environmental justice, the fair treatment and meaningful involvement of any group, including minority and/or low-income populations, in the development, implementation, and enforcement of environmental laws, regulations, and policies. To help address potential environmental justice issues, the Agency seeks information on any groups or segments of the population who, as a result of their location, cultural practices, or other factors, may have atypical or disproportionately high and adverse human health impacts or environmental effects from exposure to the pesticides discussed in this document, compared to the general population.
                </P>
                <HD SOURCE="HD1">II. Background</HD>
                <P>Registration review is EPA's periodic review of pesticide registrations to ensure that each pesticide continues to satisfy the statutory standard for registration, that is, the pesticide can perform its intended function without unreasonable adverse effects on human health or the environment. As part of the registration review process, the Agency has completed comprehensive draft human health and/or ecological risk assessments for all pesticides listed in the Table in Unit IV. After reviewing comments received during the public comment period, EPA may issue a revised risk assessment, explain any changes to the draft risk assessment, and respond to comments and may request public input on risk mitigation before completing a proposed registration review decision for the pesticides listed in the Table in Unit IV. Through this program, EPA is ensuring that each pesticide's registration is based on current scientific and other knowledge, including its effects on human health and the environment.</P>
                <HD SOURCE="HD1">III. Authority</HD>
                <P>EPA is conducting its registration review of the chemicals listed in the Table in Unit IV pursuant to section 3(g) of the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA) and the Procedural Regulations for Registration Review at 40 CFR part 155, subpart C. Section 3(g) of FIFRA provides, among other things, that the registrations of pesticides are to be reviewed every 15 years. Under FIFRA, a pesticide product may be registered or remain registered only if it meets the statutory standard for registration given in FIFRA section 3(c)(5) (7 U.S.C. 136a(c)(5)). When used in accordance with widespread and commonly recognized practice, the pesticide product must perform its intended function without unreasonable adverse effects on the environment; that is, without any unreasonable risk to man or the environment, or a human dietary risk from residues that result from the use of a pesticide in or on food.</P>
                <HD SOURCE="HD1">IV. What action is the Agency taking?</HD>
                <P>Pursuant to 40 CFR 155.58, this notice announces the availability of EPA's human health and/or ecological risk assessments for the pesticides shown in the following table and opens a 60-day public comment period on the risk assessments.</P>
                <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="s50,xs120,r50">
                    <TTITLE>Table—Draft Risk Assessments Being Made Available for Public Comment</TTITLE>
                    <BOXHD>
                        <CHED H="1">Registration review case name and No.</CHED>
                        <CHED H="1">Docket ID No.</CHED>
                        <CHED H="1">Chemical review manager and contact information</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">2,4-DP-p, Case 0294</ENT>
                        <ENT>EPA-HQ-OPP-2013-0726</ENT>
                        <ENT>
                            Lauren Bailey, 
                            <E T="03">bailey.lauren@epa.gov,</E>
                             (703) 347-0374.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Clopyralid, Case 7212</ENT>
                        <ENT>EPA-HQ-OPP-2014-0167</ENT>
                        <ENT>
                            Veronica Dutch, 
                            <E T="03">dutch.veronica@epa.gov,</E>
                             (703) 308-8585.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Flumioxazin, Case 7244</ENT>
                        <ENT>EPA-HQ-OPP-2011-0176</ENT>
                        <ENT>
                            Susan Bartow, 
                            <E T="03">bartow.susan@epa.gov,</E>
                             (703) 603-0065.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Thiabendazole and Salts, Case 2670</ENT>
                        <ENT>EPA-HQ-OPP-2014-0175</ENT>
                        <ENT>
                            Margaret Hathaway, 
                            <E T="03">hathaway.margaret@epa.gov,</E>
                             (703) 305-5076.
                        </ENT>
                    </ROW>
                </GPOTABLE>
                <P>Pursuant to 40 CFR 155.53(c), EPA is providing an opportunity, through this notice of availability, for interested parties to provide comments and input concerning the Agency's draft human health and/or ecological risk assessments for the pesticides listed in the Table in Unit IV. The Agency will consider all comments received during the public comment period and make changes, as appropriate, to a draft human health and/or ecological risk assessment. EPA may then issue a revised risk assessment, explain any changes to the draft risk assessment, and respond to comments.</P>
                <P>
                    <E T="03">Information submission requirements.</E>
                     Anyone may submit data or information in response to this document. To be considered during a pesticide's registration review, the submitted data or information must meet the following requirements:
                </P>
                <P>• To ensure that EPA will consider data or information submitted, interested persons must submit the data or information during the comment period. The Agency may, at its discretion, consider data or information submitted at a later date.</P>
                <P>• The data or information submitted must be presented in a legible and useable form. For example, an English translation must accompany any material that is not in English and a written transcript must accompany any information submitted as an audiographic or videographic record. Written material may be submitted in paper or electronic form.</P>
                <P>• Submitters must clearly identify the source of any submitted data or information.</P>
                <P>• Submitters may request the Agency to reconsider data or information that the Agency rejected in a previous review. However, submitters must explain why they believe the Agency should reconsider the data or information in the pesticide's registration review.</P>
                <P>As provided in 40 CFR 155.58, the registration review docket for each pesticide case will remain publicly accessible through the duration of the registration review process; that is, until all actions required in the final decision on the registration review case have been completed.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        7 U.S.C. 136 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <PRTPAGE P="20887"/>
                    <DATED>Dated: April 30, 2019.</DATED>
                    <NAME>Charles Smith,</NAME>
                    <TITLE>Acting Director, Pesticide Re-Evaluation Division, Office of Pesticide Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09777 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-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 listed in this notice have applied to the Board for approval, pursuant to the Bank Holding Company Act of 1956 (12 U.S.C. 1841 
                    <E T="03">et seq.</E>
                    ) (BHC Act), Regulation Y (12 CFR part 225), and all other applicable statutes and regulations to become a bank holding company and/or to acquire the assets or the ownership of, control of, or the power to vote shares of a bank or bank holding company and all of the banks and nonbanking companies owned by the bank holding company, including the companies listed below.
                </P>
                <P>The applications listed below, as well as other related filings required by the Board, are available for immediate inspection at the Federal Reserve Bank indicated. The applications will also be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing on the standards enumerated in the BHC Act (12 U.S.C. 1842(c)). If the proposal also involves the acquisition of a nonbanking company, the review also includes whether the acquisition of the nonbanking company complies with the standards in section 4 of the BHC Act (12 U.S.C. 1843). Unless otherwise noted, nonbanking activities will be conducted throughout the United States.</P>
                <P>Unless otherwise noted, comments regarding each of these applications must be received at the Reserve Bank indicated or the offices of the Board of Governors not later than June 10, 2019.</P>
                <P>
                    <E T="03">A. Federal Reserve Bank of St. Louis</E>
                     (David L. Hubbard, Senior Manager) P.O. Box 442, St. Louis, Missouri 63166-2034. Comments can also be sent electronically to 
                    <E T="03">Comments.applications@stls.frb.org:</E>
                </P>
                <P>
                    1. 
                    <E T="03">Chambers Bancshares, Inc., Danville, Arkansas;</E>
                     to merge with Bank of Dardanelle Bankshares, Inc., Dardanelle, Arkansas, and thereby indirectly acquire River Town Bank, Dardanelle, Arkansas.
                </P>
                <SIG>
                    <DATED>Board of Governors of the Federal Reserve System, May 8, 2019.</DATED>
                    <NAME>Yao-Chin Chao,</NAME>
                    <TITLE>Assistant Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09791 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Change in Bank Control Notices; Acquisitions of Shares of a Bank or Bank Holding Company</SUBJECT>
                <P>The notificants listed below have applied under the Change in Bank Control Act (“Act”) (12 U.S.C. 1817(j)) and § 225.41 of the Board's Regulation Y (12 CFR 225.41) to acquire shares of a bank or bank holding company. The factors that are considered in acting on the notices are set forth in paragraph 7 of the Act (12 U.S.C. 1817(j)(7)).</P>
                <P>The notices are available for immediate inspection at the Federal Reserve Bank indicated. The notices also will be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing to the Reserve Bank indicated for that notice or to the offices of the Board of Governors. Comments must be received not later than May 30, 2019.</P>
                <P>
                    <E T="03">A. Federal Reserve Bank of Chicago</E>
                     (Colette A. Fried, Assistant Vice President) 230 South LaSalle Street, Chicago, Illinois 60690-1414:
                </P>
                <P>
                    1. 
                    <E T="03">Second James L. Moss Revocable Trust, James L. Moss Trustee, and Second Joyce A. Moss Revocable Trust, Joyce A. Moss Trustee, all of Lansing, Iowa, as a group acting in concert;</E>
                     to retain voting shares of FNB BanShares, Inc. and thereby indirectly retain shares of Bank 1st, both of West Union, Iowa.
                </P>
                <SIG>
                    <DATED>Board of Governors of the Federal Reserve System, May 8, 2019.</DATED>
                    <NAME>Yao-Chin Chao,</NAME>
                    <TITLE>Assistant Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09793 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL TRADE COMMISSION</AGENCY>
                <SUBJECT>Granting of Requests for Early Termination of the Waiting Period Under the Premerger Notification Rules</SUBJECT>
                <P>
                    Section 7A of the Clayton Act, 15 U.S.C. 18a, as added by Title II of the Hart-Scott- Rodino Antitrust Improvements Act of 1976, requires persons contemplating certain mergers or acquisitions to give the Federal Trade Commission and the Assistant Attorney General advance notice and to wait designated periods before consummation of such plans. Section 7A(b)(2) of the Act permits the agencies, in individual cases, to terminate this waiting period prior to its expiration and requires that notice of this action be published in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>The following transactions were granted early termination—on the dates indicated—of the waiting period provided by law and the premerger notification rules. The listing for each transaction includes the transaction number and the parties to the transaction. The grants were made by the Federal Trade Commission and the Assistant Attorney General for the Antitrust Division of the Department of Justice. Neither agency intends to take any action with respect to these proposed acquisitions during the applicable waiting period.</P>
                <GPOTABLE COLS="3" OPTS="L2,p1,8/9,i1" CDEF="xs48,xls12,r200">
                    <TTITLE>Early Terminations Granted April 1, 2019 Thru April 30, 2019</TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/02/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20190942</ENT>
                        <ENT>G</ENT>
                        <ENT>AIF IX (PMC Equity AIV), L.P.; Brian W. Brady; AIF IX (PMC Equity AIV), L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20190974</ENT>
                        <ENT>G</ENT>
                        <ENT>Starboard Value and Opportunity Fund Ltd.; Zayo Group Holdings, Inc.; Starboard Value and Opportunity Fund Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191000</ENT>
                        <ENT>G</ENT>
                        <ENT>General Electric Company; GE Aero Power LLC; General Electric Company.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191001</ENT>
                        <ENT>G</ENT>
                        <ENT>Baker Hughes, a GE company; GE Aero Power LLC; Baker Hughes, a GE company.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191002</ENT>
                        <ENT>G</ENT>
                        <ENT>Topco; Pure Power Technologies, LLC; Topco.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191011</ENT>
                        <ENT>G</ENT>
                        <ENT>LeBaronBrown Industries LLC; Aceto Corporation; LeBaronBrown Industries LLC.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191020</ENT>
                        <ENT>G</ENT>
                        <ENT>Levine Leichtman Capital Partners VI, L.P.; Northlane Capital Partners I, LP; Levine Leichtman Capital Partners VI, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191023</ENT>
                        <ENT>G</ENT>
                        <ENT>Performance Food Group Company; Thomas G. Wake; Performance Food Group Company.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191024</ENT>
                        <ENT>G</ENT>
                        <ENT>Performance Food Group Company; Richard W. Wake; Performance Food Group Company.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191027</ENT>
                        <ENT>G</ENT>
                        <ENT>Nippon Telegraph and Telephone Corporation; WhiteHat Security, Inc.; Nippon Telegraph and Telephone Corporation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191032</ENT>
                        <ENT>G</ENT>
                        <ENT>Peak Rock Capital Fund II LP; The Kroger Co.; Peak Rock Capital Fund II LP.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191033</ENT>
                        <ENT>G</ENT>
                        <ENT>Envestnet, Inc.; Robert D. Curtis &amp; Karla B. Curtis; Envestnet, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191034</ENT>
                        <ENT>G</ENT>
                        <ENT>Robert D. Curtis &amp; Karla B. Curtis; Envestnet, Inc.; Robert D. Curtis &amp; Karla B. Curtis.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191035</ENT>
                        <ENT>G</ENT>
                        <ENT>RCP Vega Co-Invest, L.P.; Providence Equity Partners VI L.P.; RCP Vega Co-Invest, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20888"/>
                        <ENT I="01">20191036</ENT>
                        <ENT>G</ENT>
                        <ENT>Biohaven Pharmaceutical Holding Co. Ltd.; GW Pharmaceuticals plc; Biohaven Pharmaceutical Holding Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191037</ENT>
                        <ENT>G</ENT>
                        <ENT>TPG VIII DE AIV II, L.P.; Goodnight Water Solutions, LLC; TPG VIII DE AIV II, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191043</ENT>
                        <ENT>G</ENT>
                        <ENT>Equitrans Midstream Corporation; North Haven Infrastructure Partners II AIV-I L.P.; Equitrans Midstream Corporation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191044</ENT>
                        <ENT>G</ENT>
                        <ENT>William G. Davis; SED Holdings, LLC; William G. Davis.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191045</ENT>
                        <ENT>G</ENT>
                        <ENT>Atlas Capital Resources III LP; International Wire Group Holdings, Inc.; Atlas Capital Resources III LP.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191049</ENT>
                        <ENT>G</ENT>
                        <ENT>TCV IX, L.P.; Peloton Interactive, Inc.; TCV IX, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191051</ENT>
                        <ENT>G</ENT>
                        <ENT>Hiroshi Mikitani; Rakuten Medical, Inc.; Hiroshi Mikitani.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20191055</ENT>
                        <ENT>G</ENT>
                        <ENT>Educational Media Foundation; Cumulus Media Inc.; Educational Media Foundation.</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/04/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="s">
                        <ENT I="01">20191007 </ENT>
                        <ENT>G </ENT>
                        <ENT>BB&amp;T Corporation; SunTrust Banks, Inc.; BB&amp;T Corporation</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/08/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20191059</ENT>
                        <ENT>G</ENT>
                        <ENT>CJP TC Holdings, L.P.; Mr. Naoyuki Soga; CJP TC Holdings, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191060</ENT>
                        <ENT>G</ENT>
                        <ENT>Green Equity Investors Side VII, L.P.; Wrench Ultimate Holdings, Inc.; Green Equity Investors Side VII, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191061</ENT>
                        <ENT>G</ENT>
                        <ENT>One Equity Partners VII, L.P.; Melrose Industries PLC; One Equity Partners VII, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191062</ENT>
                        <ENT>G</ENT>
                        <ENT>Thomas Milton Duff; Bridgestone Corporation; Thomas Milton Duff.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191063</ENT>
                        <ENT>G</ENT>
                        <ENT>James Ernest Duff and Sherry G. Duff; Bridgestone Corporation; James Ernest Duff and Sherry G. Duff.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191064</ENT>
                        <ENT>G</ENT>
                        <ENT>YS Topco Limited; Jim Kim; YS Topco Limited.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191068</ENT>
                        <ENT>G</ENT>
                        <ENT>NFP Ultimate Holdings, LLC; Sir Evelyn de Rothschild; NFP Ultimate Holdings, LLC.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191069</ENT>
                        <ENT>G</ENT>
                        <ENT>NFP Ultimate Holdings, LLC; Matthew Bronfman; NFP Ultimate Holdings, LLC.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191070</ENT>
                        <ENT>G</ENT>
                        <ENT>Madison Dearborn Capital Partners VI-A, L.P.; BioScrip, Inc.; Madison Dearborn Capital Partners VI-A, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191072</ENT>
                        <ENT>G</ENT>
                        <ENT>Murray Energy Holdings Co.; Mission Coal Company, LLC; Murray Energy Holdings Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191076</ENT>
                        <ENT>G</ENT>
                        <ENT>One Rock Capital Partners II, LP; Newell Brands Inc.; One Rock Capital Partners II, LP.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191077</ENT>
                        <ENT>G</ENT>
                        <ENT>DP World PLC; Hyperloop Technologies, Inc.; DP World PLC.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191078</ENT>
                        <ENT>G</ENT>
                        <ENT>BlackRock, Inc.; Bridgepoint Europe IV 2 FCPR; BlackRock, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191079</ENT>
                        <ENT>G</ENT>
                        <ENT>TCV X L.P.; K3 Private Investors, L.P.; TCV X L.P.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20191086</ENT>
                        <ENT>G</ENT>
                        <ENT>Lear Corporation; Xevo Inc.; Lear Corporation.</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/10/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20190989</ENT>
                        <ENT>G</ENT>
                        <ENT>MasterCard Incorporated; Trans-Fast Remittance LLC; MasterCard Incorporated.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191031</ENT>
                        <ENT>G</ENT>
                        <ENT>Roper Technologies, Inc.; The Foundry Topco No. 2 Limited; Roper Technologies, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191084</ENT>
                        <ENT>G</ENT>
                        <ENT>Genstar Capital Partners VI, L.P.; Joseph M. Brodner; Genstar Capital Partners VI, L.P.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20191085</ENT>
                        <ENT>G</ENT>
                        <ENT>Genstar Capital Partners VI, L.P.; John R. Brodner and Leslie C. Brodner; Genstar Capital Partners VI, L.P.</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/11/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="s">
                        <ENT I="01">20190998 </ENT>
                        <ENT>G </ENT>
                        <ENT>MasterCard Incorporated; Ethoca Solutions Inc.; MasterCard Incorporated.</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/15/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20191053</ENT>
                        <ENT>G</ENT>
                        <ENT>OpCapita Consumer Opportunities Fund II, L.P.; Ascena Retail Group, Inc.; OpCapita Consumer Opportunities Fund II, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191094</ENT>
                        <ENT>G</ENT>
                        <ENT>Church &amp; Dwight Co., Inc.; Anand Khubani; Church &amp; Dwight Co., Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191096</ENT>
                        <ENT>G</ENT>
                        <ENT>TCV X L.P.; Toast, Inc.; TCV X L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191099</ENT>
                        <ENT>G</ENT>
                        <ENT>Madison Dearborn Capital Partners VII-A, L.P.; InMoment, Inc.; Madison Dearborn Capital Partners VII-A, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191100</ENT>
                        <ENT>G</ENT>
                        <ENT>The E.W. Scripps Company; Nexstar Media Group, lnc.; The E.W. Scripps Company.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191104</ENT>
                        <ENT>G</ENT>
                        <ENT>Koninklijke Philips N.V.; Onex Partners II LP; Koninklijke Philips N.V.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191106</ENT>
                        <ENT>G</ENT>
                        <ENT>Berwind Holding Corp.; Harbour Group Investments VI, L.P.; Berwind Holding Corp.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191107</ENT>
                        <ENT>G</ENT>
                        <ENT>Great Hill Equity Partners VI, L.P.; Customink, LLC; Great Hill Equity Partners VI, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191108</ENT>
                        <ENT>G</ENT>
                        <ENT>The IDEAL Industries, Inc. Voting Trust; Cree, Inc.; The IDEAL Industries, Inc. Voting Trust.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191109</ENT>
                        <ENT>G</ENT>
                        <ENT>SJW Group; Connecticut Water Service, Inc.; SJW Group.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191110</ENT>
                        <ENT>G</ENT>
                        <ENT>Progress Software Corporation; Roger Greene; Progress Software Corporation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191111</ENT>
                        <ENT>G</ENT>
                        <ENT>Wingtech Technology Co., Ltd.; Hefei Yuxin Holding Co. Ltd.; Wingtech Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191113</ENT>
                        <ENT>G</ENT>
                        <ENT>Thunder Bridge Acquisition LLC; Corsair IV Payment Holdings Investors L.P.; Thunder Bridge Acquisition LLC.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191118</ENT>
                        <ENT>G</ENT>
                        <ENT>Gridiron Capital Fund III, L.P.; LaMi Holdings, LLC; Gridiron Capital Fund III, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191119</ENT>
                        <ENT>G</ENT>
                        <ENT>Bain Capital Europe Fund V, SCSp; Maesa Expansion SAS; Bain Capital Europe Fund V, SCSp.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191121</ENT>
                        <ENT>G</ENT>
                        <ENT>Accenture plc; David Droga; Accenture plc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191126</ENT>
                        <ENT>G</ENT>
                        <ENT>Jones Lang LaSalle Incorporated; HFF, Inc.; Jones Lang LaSalle Incorporated.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20191128</ENT>
                        <ENT>G</ENT>
                        <ENT>Pamlico Capital IV, L.P.; BNI Holdings, LLC; Pamlico Capital IV, L.P.</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/16/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20191129</ENT>
                        <ENT>G</ENT>
                        <ENT>TPG VIII DE AIV II, L.P.; GEP Administrative Services, Inc. ESO Trust; TPG VIII DE AIV II, L.P.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20191132</ENT>
                        <ENT>G</ENT>
                        <ENT>Stichting Administratiekantoor Westend; Meow Wolf, Inc.; Stichting Administratiekantoor Westend.</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/17/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20191047</ENT>
                        <ENT>G</ENT>
                        <ENT>BG LLH, LLC; Fenway Partners Capital Fund III, L.P.; BG LLH, LLC.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20191048</ENT>
                        <ENT>G</ENT>
                        <ENT>Blucora, Inc.; Stephen A. Batman; Blucora, Inc.</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <PRTPAGE P="20889"/>
                        <ENT I="21">
                            <E T="02">04/19/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20191039</ENT>
                        <ENT>G</ENT>
                        <ENT>Barrick Gold Corporation; JV Company; Barrick Gold Corporation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191091</ENT>
                        <ENT>G</ENT>
                        <ENT>Rockwell Automation, Inc.; Sensia U.S.; Rockwell Automation, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191112</ENT>
                        <ENT>G</ENT>
                        <ENT>Joyvio Agricultural Development Co., Ltd.; Isidoro Ernesto Quiroga Moreno; Joyvio Agricultural Development Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191114</ENT>
                        <ENT>G</ENT>
                        <ENT>Knighthead Offshore Fund, Ltd.; PG&amp;E Corporation; Knighthead Offshore Fund, Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191120</ENT>
                        <ENT>G</ENT>
                        <ENT>Stonepeak Infrastucture Fund III (AIV I) LP; Oryx Midstream Services LLC; Stonepeak Infrastucture Fund III (AIV I) LP.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191122</ENT>
                        <ENT>G</ENT>
                        <ENT>Stonepeak Infrastucture Fund III (AIV I) LP; Oryx Midstream Services II, LLC; Stonepeak Infrastucture Fund III (AIV I) LP.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191127</ENT>
                        <ENT>G</ENT>
                        <ENT>Christopher Hutter; Hannibal Industries, Inc.; Christopher Hutter.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191130</ENT>
                        <ENT>G</ENT>
                        <ENT>Thomas Flohr; Clearlake Capital Partners IV, L.P.; Thomas Flohr.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191131</ENT>
                        <ENT>G</ENT>
                        <ENT>Madison Dearborn Capital Partners VII-B, L.P.; Robert E. McCarthy and Judith T. McCarthy; Madison Dearborn Capital Partners VII-B, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191133</ENT>
                        <ENT>G</ENT>
                        <ENT>Naspers Limited; Udemy, Inc.; Naspers Limited.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191135</ENT>
                        <ENT>G</ENT>
                        <ENT>Paul Douglass; Hannibal Industries, Inc.; Paul Douglass.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191138</ENT>
                        <ENT>G</ENT>
                        <ENT>AEA Investors Fund VI AIV LP; JFL Equity Investors IV, L.P.; AEA Investors Fund VI AIV LP.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191139</ENT>
                        <ENT>G</ENT>
                        <ENT>Stanley C. Middleman; The J.G. Wentworth Company; Stanley C. Middleman.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191141</ENT>
                        <ENT>G</ENT>
                        <ENT>Francisco Partners V, L.P.; Warburg Pincus Private Equity XI, L.P.; Francisco Partners V, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191142</ENT>
                        <ENT>G</ENT>
                        <ENT>The Baring Asia Private Equity Fund VII, L.P.; NIIT Technologies Limited; The Baring Asia Private Equity Fund VII, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191144</ENT>
                        <ENT>G</ENT>
                        <ENT>Lighthouse Holdings, Inc.; Spire Capital Partners III, L.P.; Lighthouse Holdings, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191145</ENT>
                        <ENT>G</ENT>
                        <ENT>Encompass Health Corporation; Alacare Home Health Services, Inc.; Encompass Health Corporation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191146</ENT>
                        <ENT>G</ENT>
                        <ENT>Nordic Capital VIII Beta, L.P.; Timothy Jenison; Nordic Capital VIII Beta, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191148</ENT>
                        <ENT>G</ENT>
                        <ENT>KKR Special Situations (EEA) Fund II, L.P.; Gibson Brands, Inc.; KKR Special Situations (EEA) Fund II, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191149</ENT>
                        <ENT>G</ENT>
                        <ENT>Cove Hill Partners Fund I, L.P.; Bessemer Venture Partners VIII Institutional L.P.; Cove Hill Partners Fund I, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191152</ENT>
                        <ENT>G</ENT>
                        <ENT>American Family Insurance Mutual Holding Company; Ameriprise Financial, Inc.; American Family Insurance Mutual Holding Company.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20191159</ENT>
                        <ENT>G</ENT>
                        <ENT>MTY Food Group Inc.; Papa Murphy's Holdings, Inc.; MTY Food Group Inc.</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/22/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20191134</ENT>
                        <ENT>G</ENT>
                        <ENT>FUJIFILM Holdings Corporation; Biogen Inc.; FUJIFILM Holdings Corporation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191136</ENT>
                        <ENT>G</ENT>
                        <ENT>ON Semiconductor Corporation; Quantenna Communications, Inc.; ON Semiconductor Corporation.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20191158</ENT>
                        <ENT>G</ENT>
                        <ENT>Clearlake Capital Partners V, L.P.; Alert Holding Company, Inc.; Clearlake Capital Partners V, L.P.</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/23/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20191095</ENT>
                        <ENT>G</ENT>
                        <ENT>National Grid plc; Geronimo Energy Holdings, LLC; National Grid plc.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20191098</ENT>
                        <ENT>G</ENT>
                        <ENT>National Grid plc; Emerald Energy Venture, LLC; National Grid plc.</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/24/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20191097</ENT>
                        <ENT>G</ENT>
                        <ENT>Pilot Corporation; RBJ &amp; Associates, L.P.; Pilot Corporation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191153</ENT>
                        <ENT>G</ENT>
                        <ENT>Giovanni Ferrero; Kellogg Company; Giovanni Ferrero.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20191157</ENT>
                        <ENT>G</ENT>
                        <ENT>Omni Investor Holdings, LLC; Michael &amp; Kathleen Entzminger; Omni Investor Holdings, LLC.</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/26/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20191071</ENT>
                        <ENT>G</ENT>
                        <ENT>Fidelity National Information Services, Inc.; Worldpay, Inc.; Fidelity National Information Services, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191161</ENT>
                        <ENT>G</ENT>
                        <ENT>CrossAmerica Partners LP; Alimentation Couche-Tard Inc.; CrossAmerica Partners LP.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191168</ENT>
                        <ENT>G</ENT>
                        <ENT>Connect Topco Limited; Inmarsat plc; Connect Topco Limited.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20191169</ENT>
                        <ENT>G</ENT>
                        <ENT>Duffle Series, L.P.; C-III Capital Partners LLC; Duffle Series, L.P.</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/29/2019</E>
                              
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20191101</ENT>
                        <ENT>G</ENT>
                        <ENT>Thermo Fisher Scientific Inc.; Ampersand 2014 Limited Partnership; Thermo Fisher Scientific Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191181</ENT>
                        <ENT>G</ENT>
                        <ENT>Arbor Investments IV, L.P.; Block Note, Inc.; Arbor Investments IV, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191182</ENT>
                        <ENT>G</ENT>
                        <ENT>CCP III AIV VI, L.P.; International Business Machines Corporation; CCP III AIV VI, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191184</ENT>
                        <ENT>G</ENT>
                        <ENT>Olympus Growth Fund VII, L.P.; 3D Holdings, Inc.; Olympus Growth Fund VII, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191186</ENT>
                        <ENT>G</ENT>
                        <ENT>Willis Towers Watson plc; Clayton, Dubilier &amp; Rice Fund IX, L.P.; Willis Towers Watson plc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191188</ENT>
                        <ENT>G</ENT>
                        <ENT>Clayton Dubilier &amp; Rice Fund IX, L.P.; Willis Towers Watson plc; Clayton Dubilier &amp; Rice Fund IX, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191190</ENT>
                        <ENT>G</ENT>
                        <ENT>Capitol Investment Corp. IV; NESCO Holdings, LP; Capitol Investment Corp. IV.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191191</ENT>
                        <ENT>G</ENT>
                        <ENT>Qorvo, Inc.; Active-Semi International Inc.; Qorvo, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191194</ENT>
                        <ENT>G</ENT>
                        <ENT>Lyndon Lea; AP VIII CEC Holdings, L.P.; Lyndon Lea.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191195</ENT>
                        <ENT>G</ENT>
                        <ENT>Robert Darwent; AP VIII CEC Holdings, L.P.; Robert Darwent.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">20191196</ENT>
                        <ENT>G</ENT>
                        <ENT>SoftBank Vision Fund (AIV M2) L.P.; Doordash, Inc.; SoftBank Vision Fund (AIV M2) L.P.</ENT>
                    </ROW>
                    <ROW EXPSTB="02" RUL="s">
                        <ENT I="21">
                            <E T="02">04/30/2019</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">20191192</ENT>
                        <ENT>G</ENT>
                        <ENT>LEP Realization Feeder, L.P.; Captive Resources Holding Company, LLC; LEP Realization Feeder, L.P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20191202</ENT>
                        <ENT>G</ENT>
                        <ENT>Genstar Capital Partners VII, L.P.; Mr. and Mrs. Joseph Schneerson; Genstar Capital Partners VII, L.P.</ENT>
                    </ROW>
                </GPOTABLE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Theresa Kingsberry, Program Support Specialist, Federal Trade Commission Premerger Notification Office, Bureau of Competition, Room CC-5301, Washington, DC 20024, (202) 326-3100.</P>
                    <SIG>
                        <PRTPAGE P="20890"/>
                        <P>By direction of the Commission.</P>
                        <NAME>April Tabor,</NAME>
                        <TITLE>Acting Secretary.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09815 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6750-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Agency for Healthcare Research and Quality</SUBAGY>
                <SUBJECT>Patient Safety Organizations: Voluntary Relinquishment From the AABB Center for Patient Safety</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Agency for Healthcare Research and Quality (AHRQ), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of delisting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Patient Safety and Quality Improvement Final Rule (Patient Safety Rule) authorizes AHRQ, on behalf of the Secretary of HHS, to list as a patient safety organization (PSO) an entity that attests that it meets the statutory and regulatory requirements for listing. A PSO can be “delisted” by the Secretary if it is found to no longer meet the requirements of the Patient Safety and Quality Improvement Act of 2005 (Patient Safety Act) and Patient Safety Rule, when a PSO chooses to voluntarily relinquish its status as a PSO for any reason, or when a PSO's listing expires. AHRQ has accepted a notification of voluntary relinquishment from the AABB Center for Patient Safety, PSO number P0032, of its status as a PSO, and has delisted the PSO accordingly.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The delisting was effective at 12:00 Midnight ET (2400) on April 30, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The directories for both listed and delisted PSOs are ongoing and reviewed weekly by AHRQ. Both directories can be accessed electronically at the following HHS website: 
                        <E T="03">http://www.pso.ahrq.gov/listed.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Cathryn Bach, Center for Quality Improvement and Patient Safety, AHRQ, 5600 Fishers Lane, MS 06N100B, Rockville, MD 20857; Telephone (toll free): (866) 403-3697; Telephone (local): (301) 427-1111; TTY (toll free): (866) 438-7231; TTY (local): (301) 427-1130; Email: 
                        <E T="03">pso@ahrq.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The Patient Safety Act, 42 U.S.C. 299b-21 to 299b-26, and the related Patient Safety Rule, 42 CFR part 3, published in the 
                    <E T="04">Federal Register</E>
                     on November 21, 2008, 73 FR 70732-70814, establish a framework by which individuals and entities that meet the definition of provider in the Patient Safety Rule may voluntarily report information to PSOs listed by AHRQ, on a privileged and confidential basis, for the aggregation and analysis of patient safety events.
                </P>
                <P>The Patient Safety Act authorizes the listing of PSOs, which are entities or component organizations whose mission and primary activity are to conduct activities to improve patient safety and the quality of health care delivery.</P>
                <P>HHS issued the Patient Safety Rule to implement the Patient Safety Act. AHRQ administers the provisions of the Patient Safety Act and Patient Safety Rule relating to the listing and operation of PSOs. The Patient Safety Rule authorizes AHRQ to list as a PSO an entity that attests that it meets the statutory and regulatory requirements for listing. A PSO can be “delisted” if it is found to no longer meet the requirements of the Patient Safety Act and Patient Safety Rule, when a PSO chooses to voluntarily relinquish its status as a PSO for any reason, or when a PSO's listing expires. Section 3.108(d) of the Patient Safety Rule requires AHRQ to provide public notice when it removes an organization from the list of federally approved PSOs.</P>
                <P>AHRQ has accepted a notification from AABB Center for Patient Safety, a component entity of the American Association of Blood Banks (AABB), to voluntarily relinquish its status as a PSO. Accordingly, AABB Center for Patient Safety, P0032, was delisted effective at 12:00 Midnight ET (2400) on April 30, 2019.</P>
                <P>AABB Center for Patient Safety has patient safety work product (PSWP) in its possession. The PSO will meet the requirements of section 3.108(c)(2)(i) of the Patient Safety Rule regarding notification to providers that have reported to the PSO and of section 3.108(c)(2)(ii) regarding disposition of PSWP consistent with section 3.108(b)(3). According to section 3.108(b)(3) of the Patient Safety Rule, the PSO has 90 days from the effective date of delisting and revocation to complete the disposition of PSWP that is currently in the PSO's possession.</P>
                <P>
                    More information on PSOs can be obtained through AHRQ's PSO website at 
                    <E T="03">http://www.pso.ahrq.gov.</E>
                </P>
                <SIG>
                    <NAME>Gopal Khanna,</NAME>
                    <TITLE>Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09788 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-90-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                <DEPDOC>[Document Identifier: CMS-10105 and CMS-10407]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid 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 (the PRA), federal agencies are required to publish notice in the 
                        <E T="04">Federal Register</E>
                         concerning each proposed collection of information (including each proposed extension or reinstatement of an existing collection of information) and to allow 60 days for public comment on the proposed action. Interested persons are invited to send comments regarding our burden estimates or any other aspect of this collection of information, including the necessity and utility of the proposed information collection for the proper performance of the agency's functions, the accuracy of the estimated burden, ways to enhance the quality, utility, and clarity of the information to be collected, and the use of automated collection techniques or other forms of information technology to minimize the information collection burden.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by July 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>When commenting, please reference the document identifier or OMB control number. To be assured consideration, comments and recommendations must be submitted in any one of the following ways:</P>
                    <P>
                        1. 
                        <E T="03">Electronically.</E>
                         You may send your comments electronically to 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the instructions for “Comment or Submission” or “More Search Options” to find the information collection document(s) that are accepting comments.
                    </P>
                    <P>
                        2. 
                        <E T="03">By regular mail.</E>
                         You may mail written comments to the following address: CMS, Office of Strategic Operations and Regulatory Affairs, Division of Regulations Development, Attention: Document Identifier/OMB Control Number ____, Room C4-26-05, 7500 Security Boulevard, Baltimore, Maryland 21244-1850.
                        <PRTPAGE P="20891"/>
                    </P>
                    <P>To obtain copies of a supporting statement and any related forms for the proposed collection(s) summarized in this notice, you may make your request using one of following:</P>
                    <P>
                        1. Access CMS' website address at 
                        <E T="03">https://www.cms.gov/Regulations-and-Guidance/Legislation/PaperworkReductionActof1995/PRA-Listing.html.</E>
                    </P>
                    <P>
                        2. Email your request, including your address, phone number, OMB number, and CMS document identifier, to 
                        <E T="03">Paperwork@cms.hhs.gov.</E>
                    </P>
                    <P>3. Call the Reports Clearance Office at (410) 786-1326.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>William N. Parham at (410) 786-4669.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Contents</HD>
                <P>
                    This notice sets out a summary of the use and burden associated with the following information collections. More detailed information can be found in each collection's supporting statement and associated materials (see 
                    <E T="02">ADDRESSES</E>
                    ).
                </P>
                <FP SOURCE="FP-1">CMS-10105 National Implementation of the In-Center Hemodialysis CAHPS Survey</FP>
                <FP SOURCE="FP-1">CMS-10407 Summary of Benefits and Coverage and Uniform Glossary</FP>
                <P>
                    Under the PRA (44 U.S.C. 3501-3520), federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. The term “collection of information” is defined in 44 U.S.C. 3502(3) and 5 CFR 1320.3(c) and includes agency requests or requirements that members of the public submit reports, keep records, or provide information to a third party. Section 3506(c)(2)(A) of the PRA requires federal agencies to publish a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each proposed extension or reinstatement of an existing collection of information, before submitting the collection to OMB for approval. To comply with this requirement, CMS is publishing this notice.
                </P>
                <HD SOURCE="HD1">Information Collection</HD>
                <P>
                    1. 
                    <E T="03">Type of Information Collection Request:</E>
                     Extension without change of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     National Implementation of the In-Center Hemodialysis CAHPS Survey; 
                    <E T="03">Use:</E>
                     The Centers for Medicare &amp; Medicaid Services (CMS) is requesting clearance from the Office of Management and Budget (OMB) to continue the In-center Hemodialysis CAHPS (ICH CAHPS) Survey to measure patients' experience of care with in-center hemodialysis (ICH) facilities. Data collected in the national implementation of the ICH CAHPS Survey are used for the following purposes: To provide a source of information from which selected measures can be publicly reported to beneficiaries as a decision aid for dialysis facility selection; to aid facilities with their internal quality improvement efforts and external benchmarking with other facilities; to provide CMS with information for monitoring and public reporting purposes; and to support the ESRD value-based purchasing program. 
                    <E T="03">Form Number:</E>
                     CMS-10105 (OMB control number: 0938-0926); 
                    <E T="03">Frequency:</E>
                     Yearly; 
                    <E T="03">Affected Public:</E>
                     State, Local, or Tribal Governments; 
                    <E T="03">Number of Respondents:</E>
                     108,800; 
                    <E T="03">Total Annual Responses:</E>
                     108,800; 
                    <E T="03">Total Annual Hours:</E>
                     58,753. (For policy questions regarding this collection contact Julia Zucco at 410-786-6677.)
                </P>
                <P>
                    <E T="03">2. Type of Information Collection Request:</E>
                     Reinstatement with change of a previously approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Summary of Benefits and Coverage and Uniform Glossary; 
                    <E T="03">Use:</E>
                     This information collection will ensure that consumers shopping for or enrolled in private, individually purchased, or non-federal governmental group health plan coverage receive the consumer protections of the Affordable Care Act. Employers, employees, and individuals will use this information to compare coverage options prior to selecting coverage and to understand the terms of, and extent of medical benefits offered by, their coverage (or exceptions to such coverage or benefits) once they have coverage. CMS recently received OMB approval for a non-substantive change to the SBC calculator. Specifically, CMS requested that issuers begin using an updated 2020 SBC calculator starting on or after January 1, 2020. However, at this time, CMS is alerting issuers to immediately discontinue use of the 2020 calculator. Until further notice from CMS, issuers should revert back to using the 2017 SBC Calculator and all associated materials (including the 2017 SBC Calculator Excel file, the Guides and Narratives for the coverage examples, and the calculator instructions) to calculate coverage example costs for the SBC. 
                    <E T="03">Form Number:</E>
                     CMS-10407 (OMB control number: 0938-1146); 
                    <E T="03">Frequency:</E>
                     Yearly; 
                    <E T="03">Affected Public:</E>
                     Private Sector—Business or other for-profits and not-for-profit institutions; 
                    <E T="03">Number of Respondents:</E>
                     128,511; 
                    <E T="03">Total Annual Responses:</E>
                     24,433,233; 
                    <E T="03">Total Annual Hours:</E>
                     41,551. (For policy questions regarding this collection contact Jessica Weinberg at 301-492-4404.)
                </P>
                <SIG>
                    <DATED>Dated: May 8, 2019.</DATED>
                    <NAME>William N. Parham, III,</NAME>
                    <TITLE>Director, Paperwork Reduction Staff, Office of Strategic Operations and Regulatory Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09781 Filed 5-10-19; 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>Proposed Information Collection Activity; Procedural Justice-Informed Alternatives to Contempt Demonstration Project Data Collection (OMB #0970-0505)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Child Support Enforcement; Administration for Children and Families; HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for public comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Office of Child Support Enforcement (OCSE), Administration for Children and Families (ACF), U.S. Department of Health and Human Services (HHS), is proposing to collect data as part of the rigorous evaluation of the 
                        <E T="03">Procedural Justice-Informed Alternatives to Contempt</E>
                         (PJAC) demonstration.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments due by July 12, 2019. In compliance with the requirements of Section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Administration for Children and Families is soliciting public comment on the specific aspects of the information collection described above.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Copies of the proposed collection of information can be obtained and comments may be forwarded by emailing 
                        <E T="03">infocollection@acf.hhs.gov</E>
                        . Alternatively, copies can also be obtained by writing to the Administration for Children and Families, Office of Planning, Research, and Evaluation, 330 C Street SW, Washington, DC 20201, Attn: OPRE Reports Clearance Officer. All requests, emailed or written, should be identified by the title of the information collection.
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Description:</E>
                     The Office of Child Support Enforcement (OCSE) within the Administration for Children and Families (ACF) is proposing a data collection activity as part of the Procedural Justice-Informed Alternatives to Contempt (PJAC) 
                    <PRTPAGE P="20892"/>
                    Demonstration. In September 2016, OCSE issued grants to five state child support agencies to provide alternative approaches to the contempt process with the goal of increasing noncustodial parents' compliance with child support orders by building trust and confidence in the child support agency and its processes. OCSE also awarded a grant to support a rigorous evaluation of PJAC. The PJAC Demonstration is a five-year project that allows grantees and OCSE to learn whether incorporating principles of procedural justice into child support business practices increases reliable child support payments, reduces arrears, minimizes the need for continued enforcement actions and sanctions, and reduces the use of contempt proceedings.
                </P>
                <P>The PJAC demonstration will yield information about the efficacy of applying procedural justice principles via a set of alternative services to the current use of a civil contempt process to address nonpayment of child support. It will generate knowledge regarding how the PJAC intervention operates, the effects the alternative services have, and whether the benefits of this approach exceed the costs. The information gathered will help inform future policy decisions related to the contempt process within the field of child support enforcement.</P>
                <P>PJAC demonstration will include three interconnected evaluation components:</P>
                <P>1. Implementation Study. The implementation study will provide a detailed description of the PJAC intervention—how it is implemented, whether it was implemented as intended, participant characteristics, the contexts in which it is operated, how treatment differed from the status quo, and the implications of PJAC practices. The study will identify the intervention features and conditions necessary for effective replication or improvement of the intervention. Key elements of the implementation study include: A Management Information System (MIS) for random assignment and data collection on participant engagement in PJAC activities; semi-structured interviews with staff from child support agencies and selected partner organizations; separate semi-structured interviews with study participants and the custodial parents connected to their child support case to learn about their experiences with and perceptions of the child support program; and a staff questionnaire to gather quantitative information on the implementation of PJAC services and staff experiences.</P>
                <P>2. Impact Study. The impact study will provide rigorous estimates of the effectiveness of the PJAC intervention using an experimental research design. Noncustodial parents whose cases are being referred to the contempt process will be randomly assigned to either a program group that is offered PJAC services or to a control group that is offered business-as-usual services. Random assignment will require child support program staff to complete a brief data entry protocol. The impact study will rely on administrative data from state and county child support programs, court records, criminal justice records, and data from the National Directory of New Hires. Administrative records data will be used to estimate impacts on child support payments, enforcement actions, contempt proceedings, and jail stays.</P>
                <P>3. Benefit-Cost Study. The benefit-cost study will estimate the costs and benefits associated with the implementation and impact of the PJAC interventions. The study will examine the costs and benefits from the perspective of the government, noncustodial parents, custodial parents, and society. Pertinent benefits and costs will be added together to determine the net value of the program for each perspective. Key outcomes to be assessed include the cost of PJAC interventions, costs for contempt actions, child support payments from noncustodial parents (program and control), court costs, and jail time, among others. The benefit-cost study will rely on the results of the impact study, analysis of participation data from the MIS, and results of a staff time study to quantify various PJAC-related costs and benefits.</P>
                <P>This notice is specific to the following data collection activities: The noncustodial parent participant interviews (these interview topic guides were approved under a previous submission and require content modification which also significantly lowers the collective public burden hours); the staff survey; the staff time study; and the custodial parent interviews. Data collection activities that were previously approved by OMB, following public comment, are the staff data entry on participant baseline information, study MIS to track receipt of services, staff and community partner interview topic guide, the participant interview topic guide, and the participant survey tracking letter. A participant survey has been eliminated from the data collections plans, so the OMB-approved participant survey tracking letter will no longer be used.</P>
                <P>
                    <E T="03">Respondents:</E>
                     Respondents include study participants, child support program staff at the six PJAC demonstration sites, custodial parents associated with study participants, and the federal Office of Child Support Enforcement.
                </P>
                <GPOTABLE COLS="05" OPTS="L2,i1" CDEF="s75,12,12,12,12">
                    <TTITLE>Annual Burden Estimates</TTITLE>
                    <BOXHD>
                        <CHED H="1">Instrument</CHED>
                        <CHED H="1">Total number of respondents</CHED>
                        <CHED H="1">Total number of responses per respondent</CHED>
                        <CHED H="1">
                            Average
                            <LI>burden hours</LI>
                            <LI>per response</LI>
                        </CHED>
                        <CHED H="1">Total burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Noncustodial parent participant interview</ENT>
                        <ENT>60</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>60</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Staff Survey</ENT>
                        <ENT>20</ENT>
                        <ENT>1</ENT>
                        <ENT>.5</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Staff time study</ENT>
                        <ENT>30</ENT>
                        <ENT>1</ENT>
                        <ENT>1.5</ENT>
                        <ENT>45</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Custodial parent interview</ENT>
                        <ENT>60</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>60</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     175
                </P>
                <P>
                    <E T="03">Comments:</E>
                     The Department specifically requests comments on (a) whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; (b) the accuracy of the agency's estimate of the burden of the proposed collection of information; (c) the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology. Consideration will be given to comments and suggestions submitted within 60 days of this publication.
                </P>
                <AUTH>
                    <PRTPAGE P="20893"/>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>42 U.S.C. 1315.</P>
                </AUTH>
                <SIG>
                    <NAME>Mary B. Jones,</NAME>
                    <TITLE>ACF/OPRE Certifying Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09756 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4184-41-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2019-N-1875]</DEPDOC>
                <SUBJECT>Financial Transparency and Efficiency of the Prescription Drug User Fee Act, Biosimilar User Fee Act, and Generic Drug User Fee Amendments; Public Meeting; Request for Comments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public meeting; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA, the Agency, or we) is announcing the following public meeting entitled “Financial Transparency and Efficiency of the Prescription Drug User Fee Act, Biosimilar User Fee Act, and Generic Drug User Fee Amendments.” The purpose of the public meeting is to meet performance commitments included in the Prescription Drug User Fee Act (PDUFA) VI, Biosimilar User Fee Act (BsUFA) II, and Generic Drug User Fee Amendments (GDUFA) II. The public meeting will include presentations from FDA on the 5-year plans for the PDUFA VI, BsUFA II, and GDUFA II; the Agency's progress in implementing resource capacity planning and modernized time reporting; and the results of the fiscal year (FY) 2018 evaluation of PDUFA, BsUFA, and GDUFA resource management. The Agency will also address the impact of the modernized fee structure changes on the PDUFA and BsUFA programs and report on the contribution of the BsUFA spending trigger to the BsUFA program.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The public meeting will be held on June 7, 2019, from 9 a.m. to 12 p.m. Submit either electronic or written comments on this public meeting by July 8, 2019. See the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for registration date and information.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The public meeting will be held at FDA's White Oak Campus, 10903 New Hampshire Ave., Bldg. 31 Conference Center, the Great Room (Rm. 1503), Silver Spring, MD 20993. Entrance for the public meeting participants (non-FDA employees) is through Building 1 where routine security check procedures will be performed. For parking and security information, please refer to 
                        <E T="03">https://www.fda.gov/AboutFDA/WorkingatFDA/BuildingsandFacilities/WhiteOakCampusInformation/ucm241740.htm.</E>
                    </P>
                    <P>
                        You may submit comments as follows. Please note that late, untimely filed comments will not be considered. Electronic comments must be submitted on or before July 8, 2019. 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 July 8, 2019. Comments received by mail/hand delivery/courier (for written/paper submissions) will be considered timely if they are postmarked or the delivery service acceptance receipt is on or before that date.
                    </P>
                </ADD>
                <HD SOURCE="HD2">Electronic Submissions</HD>
                <P>Submit electronic comments in the following way:</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal: https://www.regulations.gov.</E>
                     Follow the instructions for submitting comments. Comments submitted electronically, including attachments, to 
                    <E T="03">https://www.regulations.gov</E>
                     will be posted to the docket unchanged. Because your comment will be made public, you are solely responsible for ensuring that your comment does not include any confidential information that you or a third party may not wish to be posted, such as medical information, your or anyone else's Social Security number, or confidential business information, such as a manufacturing process. Please note that if you include your name, contact information, or other information that identifies you in the body of your comments, that information will be posted on 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <P>• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).</P>
                <HD SOURCE="HD2">Written/Paper Submissions</HD>
                <P>Submit written/paper submissions as follows:</P>
                <P>
                    • 
                    <E T="03">Mail/Hand delivery/Courier (for written/paper submissions):</E>
                     Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <P>• For written/paper comments submitted to the Dockets Management Staff, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”</P>
                <P>
                    <E T="03">Instructions:</E>
                     All submissions received must include the Docket No. FDA-2019-N-1875 for “Financial Transparency and Efficiency of the Prescription Drug User Fee Act, Biosimilar User Fee Act, and Generic Drug User Fee Amendments; Public Meeting; Request for Comments.” Received comments, those filed in a timely manner (see 
                    <E T="02">ADDRESSES</E>
                    ), will be placed in the docket and, except for those submitted as “Confidential Submissions,” publicly viewable at 
                    <E T="03">https://www.regulations.gov</E>
                     or at the Dockets Management Staff between 9 a.m. and 4 p.m., Monday through Friday.
                </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.gpo.gov/fdsys/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.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Graham Thompson, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New 
                        <PRTPAGE P="20894"/>
                        Hampshire Ave., Bldg. 51, Rm. 1146, Silver Spring, MD 20993-0002, 301-796-5003, Fax: 301-847-8443, 
                        <E T="03">Graham.Thompson@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>This public meeting is intended to satisfy FDA's commitment to host an annual public meeting in the third quarter of each fiscal year beginning in FY 2019 (II.B.3 of PDUFA VI (p. 38), IV.B.3 of BsUFA II (p. 28), and VI.B.4 of GDUFA II (p.22)). These user fee programs were reauthorized as part of the Food and Drug Administration Reauthorization Act of 2017, signed by the President on August 18, 2017. The complete set of performance goals for each program are available at:</P>
                <P>
                    • 
                    <E T="03">PDUFA VI program: https://www.fda.gov/downloads/ForIndustry/UserFees/PrescriptionDrugUserFee/UCM511438.pdf</E>
                </P>
                <P>
                    • 
                    <E T="03">BsUFA II program: https://www.fda.gov/downloads/forindustry/userfees/biosimilaruserfeeactbsufa/ucm521121.pdf</E>
                </P>
                <P>
                    • 
                    <E T="03">GDUFA II program: https://www.fda.gov/downloads/forindustry/userfees/genericdruguserfees/ucm525234.pdf</E>
                </P>
                <P>Each of these user fee programs included a set of commitments related to financial management. These included commitments to publish a 5-year financial plan that should be updated annually, develop resource capacity planning capability and modernize time reporting practices, and have a third-party evaluation of resource management practices for these user fee programs. In addition, each user fee program includes a commitment to host a public meeting in the third quarter of each fiscal year, beginning in FY 2019, to discuss specific topics.</P>
                <HD SOURCE="HD1">II. Topics for Discussion at the Public Meeting</HD>
                <P>This public meeting will provide FDA the opportunity to update interested public stakeholders on topics related to the financial management of PDUFA VI, BsUFA II, and GDUFA II. FDA will present the 5-year financial plans for each of these programs and discuss the vision for the resource capacity planning capability, as well as update participants on the progress towards implementing resource capacity planning and modernizing its time reporting approach. FDA will also address the impact of the fee structure changes on PDUFA VI and BsUFA II, as well as the contribution of the BsUFA spending trigger to the BsUFA program. Finally, the meeting will include a presentation from representatives of the MITRE Corporation or Grant Thornton on their evaluation of PDUFA, BsUFA, and GDUFA resource management during FY 2018 and FDA's response to this evaluation.</P>
                <HD SOURCE="HD1">III. Participating in the Public Meeting</HD>
                <P>
                    <E T="03">Registration:</E>
                     To register for the public meeting, please visit the following website: 
                    <E T="03">https://fdafinancemeeting.eventbrite.com.</E>
                     If you are unable to attend the meeting in person, you can register to view a live webcast of the meeting. You will be asked to indicate in your registration if you plan to attend in person or via webcast. Please provide complete contact information for each attendee, including name, title, affiliation, address, email, and telephone.
                </P>
                <P>Registration is free and based on space availability, with priority given to early registrants. Persons interested in attending this public meeting must register by June 3, 2019, at 11:59 p.m. Eastern Time. Early registration is recommended because seating is limited; therefore, FDA may limit the number of participants from each organization. Registrants will receive confirmation once they have been accepted. If time and space permit, onsite registration on the day of the public meeting will be provided beginning at 8 a.m. We will let registrants know if registration closes before the day of the public meeting.</P>
                <P>If you need special accommodations due to a disability, please contact Graham Thompson no later than June 3, 2019, 11:59 p.m. Eastern Time.</P>
                <P>
                    <E T="03">Streaming Webcast of the Public Meeting:</E>
                     This public meeting will also be webcast. Please register for the webcast by visiting 
                    <E T="03">https://fdafinancemeeting.eventbrite.com.</E>
                </P>
                <P>
                    If you have never attended a Connect Pro event before, test your connection at 
                    <E T="03">https://collaboration.fda.gov/common/help/en/support/meeting_test.htm.</E>
                     To get a quick overview of the Connect Pro program, visit 
                    <E T="03">https://www.adobe.com/go/connectpro_overview.</E>
                     FDA has verified the website addresses in this document, as of the date this document publishes in the 
                    <E T="04">Federal Register,</E>
                     but websites are subject to change over time.
                </P>
                <P>
                    <E T="03">Transcripts:</E>
                     Please be advised that as soon as a transcript of the public meeting is available, it will be accessible at 
                    <E T="03">https://www.regulations.gov.</E>
                     It may be viewed at the Dockets Management Staff (see 
                    <E T="02">ADDRESSES</E>
                    ).
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Lowell J. Schiller,</NAME>
                    <TITLE>Principal Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09803 Filed 5-10-19; 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-2017-E-6549]</DEPDOC>
                <SUBJECT>Determination of Regulatory Review Period for Purposes of Patent Extension; GORE VIABAHN VBX BALLOON EXPANDABLE ENDOPROSTHESIS</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA or the Agency) has determined the regulatory review period for the GORE VIABAHN VBX BALLOON EXPANDABLE ENDOPROSTHESIS and is publishing this notice of that determination as required by law. FDA has made the determination because of the submission of an application to the Director of the U.S. Patent and Trademark Office (USPTO), Department of Commerce, for the extension of a patent which claims that medical device.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Anyone with knowledge that any of the dates as published (see the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section) are incorrect may submit either electronic or written comments and ask for a redetermination by July 12, 2019. Furthermore, any interested person may petition FDA for a determination regarding whether the applicant for extension acted with due diligence during the regulatory review period by November 12, 2019. See “Petitions” in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for more information.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments as follows. Please note that late, untimely filed comments will not be considered. Electronic comments must be submitted on or before July 12, 2019. 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 July 12, 2019. Comments received by mail/hand delivery/courier (for written/paper submissions) will be considered timely if they are postmarked or the delivery service acceptance receipt is on or before that date.
                    </P>
                </ADD>
                <HD SOURCE="HD2">Electronic Submissions</HD>
                <P>Submit electronic comments in the following way:</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal:</E>
                      
                    <E T="03">https://www.regulations.gov.</E>
                     Follow the instructions for submitting comments. Comments submitted electronically, 
                    <PRTPAGE P="20895"/>
                    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-E-6549 for “Determination of Regulatory Review Period for Purposes of Patent Extension; GORE VIABAHN VBX BALLOON EXPANDABLE ENDOPROSTHESIS.” Received comments, those filed in a timely manner (see 
                    <E T="02">ADDRESSES</E>
                    ), will be placed in the docket and, except for those submitted as “Confidential Submissions,” publicly viewable at 
                    <E T="03">https://www.regulations.gov</E>
                     or at the Dockets Management Staff between 9 a.m. and 4 p.m., Monday through Friday.
                </P>
                <P>
                    • Confidential Submissions—To submit a comment with confidential information that you do not wish to be made publicly available, submit your comments only as a written/paper submission. You should submit two copies total. One copy will include the information you claim to be confidential with a heading or cover note that states “THIS DOCUMENT CONTAINS CONFIDENTIAL INFORMATION.” The Agency will review this copy, including the claimed confidential information, in its consideration of comments. The second copy, which will have the claimed confidential information redacted/blacked out, will be available for public viewing and posted on 
                    <E T="03">https://www.regulations.gov.</E>
                     Submit both copies to the Dockets Management Staff. If you do not wish your name and contact information to be made publicly available, you can provide this information on the cover sheet and not in the body of your comments and you must identify this information as “confidential.” Any information marked as “confidential” will not be disclosed except in accordance with § 10.20 (21 CFR 10.20) and other applicable disclosure law. For more information about FDA's posting of comments to public dockets, see 80 FR 56469, September 18, 2015, or access the information at: 
                    <E T="03">https://www.gpo.gov/fdsys/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.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Beverly Friedman, Office of Regulatory Policy, Food and Drug Administration, 10903 New Hampshire Ave. Bldg. 51, Rm. 6250, Silver Spring, MD 20993, 301-796-3600.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Background</HD>
                <P>The Drug Price Competition and Patent Term Restoration Act of 1984 (Pub. L. 98-417) and the Generic Animal Drug and Patent Term Restoration Act (Pub. L. 100-670) generally provide that a patent may be extended for a period of up to 5 years so long as the patented item (human drug product, animal drug product, medical device, food additive, or color additive) was subject to regulatory review by FDA before the item was marketed. Under these acts, a product's regulatory review period forms the basis for determining the amount of extension an applicant may receive.</P>
                <P>A regulatory review period consists of two periods of time: a testing phase and an approval phase. For medical devices, the testing phase begins with a clinical investigation of the device and runs until the approval phase begins. The approval phase starts with the initial submission of an application to market the device and continues until permission to market the device is granted. Although only a portion of a regulatory review period may count toward the actual amount of extension that the Director of USPTO may award (half the testing phase must be subtracted as well as any time that may have occurred before the patent was issued), FDA's determination of the length of a regulatory review period for a medical device will include all of the testing phase and approval phase as specified in 35 U.S.C. 156(g)(3)(B).</P>
                <P>FDA has approved for marketing the medical device GORE VIABAHN VBX BALLOON EXPANDABLE ENDOPROSTHESIS. GORE VIABAHN VBX BALLOON EXPANDABLE ENDOPROSTHESIS is indicated for the treatment of de novo or restenotic lesions found in iliac arteries with reference vessel diameters ranging from 5 millimeters (mm) to 13 mm and lesion lengths up to 110 mm, including lesions at the aortic bifurcation. Subsequent to this approval, the USPTO received a patent term restoration application for the GORE VIABAHN VBX BALLOON EXPANDABLE ENDOPROSTHESIS (U.S. Patent No. 6,461,665) from W.L. Gore &amp; Associates, Inc., and the USPTO requested FDA's assistance in determining this patent's eligibility for patent term restoration. In a letter dated February 6, 2018, FDA advised the USPTO that this medical device had undergone a regulatory review period and that the approval of the GORE VIABAHN VBX BALLOON EXPANDABLE ENDOPROSTHESIS represented the first permitted commercial marketing or use of the product. Thereafter, the USPTO requested that FDA determine the product's regulatory review period.</P>
                <HD SOURCE="HD1">II. Determination of Regulatory Review Period</HD>
                <P>FDA has determined that the applicable regulatory review period for the GORE VIABAHN VBX BALLOON EXPANDABLE ENDOPROSTHESIS is 1,136 days. Of this time, 931 days occurred during the testing phase of the regulatory review period, while 205 days occurred during the approval phase. These periods of time were derived from the following dates:</P>
                <P>
                    1. 
                    <E T="03">The date an exemption under section 520(g) of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) (21 U.S.C. 360j(g)) involving this device became effective:</E>
                     December 20, 2013. FDA has verified the applicant's claim that the date the investigational device exemption required under section 520(g) of the FD&amp;C Act for human tests 
                    <PRTPAGE P="20896"/>
                    to begin became effective was December 20, 2013.
                </P>
                <P>
                    2. 
                    <E T="03">The date an application was initially submitted with respect to the device under section 515 of the FD&amp;C Act (21 U.S.C. 360e):</E>
                     July 7, 2016. FDA has verified the applicant's claim that the premarket approval application (PMA) for the GORE VIABAHN VBX BALLOON EXPANDABLE ENDOPROSTHESIS (PMA P160021) was initially submitted July 7, 2016.
                </P>
                <P>
                    3. 
                    <E T="03">The date the application was approved:</E>
                     January 27, 2017. FDA has verified the applicant's claim that PMA P160021 was approved on January 27, 2017.
                </P>
                <P>This determination of the regulatory review period establishes the maximum potential length of a patent extension. However, the USPTO applies several statutory limitations in its calculations of the actual period for patent extension. In its application for patent extension, this applicant seeks 669 days of patent term extension.</P>
                <HD SOURCE="HD1">III. Petitions</HD>
                <P>
                    Anyone with knowledge that any of the dates as published are incorrect may submit either electronic or written comments and, under 21 CFR 60.24, ask for a redetermination (see 
                    <E T="02">DATES</E>
                    ). Furthermore, as specified in § 60.30 (21 CFR 60.30), any interested person may petition FDA for a determination regarding whether the applicant for extension acted with due diligence during the regulatory review period. To meet its burden, the petition must comply with all the requirements of § 60.30, including but not limited to: must be timely (see 
                    <E T="02">DATES</E>
                    ), must be filed in accordance with § 10.20, must contain sufficient facts to merit an FDA investigation, and must certify that a true and complete copy of the petition has been served upon the patent applicant. (See H. Rept. 857, part 1, 98th Cong., 2d sess., pp. 41-42, 1984.) Petitions should be in the format specified in 21 CFR 10.30.
                </P>
                <P>
                    Submit petitions electronically to 
                    <E T="03">https://www.regulations.gov</E>
                     at Docket No. FDA-2013-S-0610. Submit written petitions (two copies are required) to the Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Lowell J. Schiller,</NAME>
                    <TITLE>Principal Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09817 Filed 5-10-19; 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-2017-E-6509]</DEPDOC>
                <SUBJECT>Determination of Regulatory Review Period for Purposes of Patent Extension; AUSTEDO</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA or the Agency) has determined the regulatory review period for AUSTEDO and is publishing this notice of that determination as required by law. FDA has made the determination because of the submission of an application to the Director of the U.S. Patent and Trademark Office (USPTO), Department of Commerce, for the extension of a patent which claims that human drug product.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Anyone with knowledge that any of the dates as published (see the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section) are incorrect may submit either electronic or written comments and ask for a redetermination by July 12, 2019. Furthermore, any interested person may petition FDA for a determination regarding whether the applicant for extension acted with due diligence during the regulatory review period by November 12, 2019. See “Petitions” in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for more information.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments as follows. Please note that late, untimely filed comments will not be considered. Electronic comments must be submitted on or before July 12, 2019. 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 July 12, 2019. Comments received by mail/hand delivery/courier (for written/paper submissions) will be considered timely if they are postmarked or the delivery service acceptance receipt is on or before that date.
                    </P>
                </ADD>
                <HD SOURCE="HD2">Electronic Submissions</HD>
                <P>Submit electronic comments in the following way:</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal: https://www.regulations.gov.</E>
                     Follow the instructions for submitting comments. Comments submitted electronically, including attachments, to 
                    <E T="03">https://www.regulations.gov</E>
                     will be posted to the docket unchanged. Because your comment will be made public, you are solely responsible for ensuring that your comment does not include any confidential information that you or a third party may not wish to be posted, such as medical information, your or anyone else's Social Security number, or confidential business information, such as a manufacturing process. Please note that if you include your name, contact information, or other information that identifies you in the body of your comments, that information will be posted on 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <P>• If you want to submit a comment with confidential information that you do not wish to be made available to the public, submit the comment as a written/paper submission and in the manner detailed (see “Written/Paper Submissions” and “Instructions”).</P>
                <HD SOURCE="HD2">Written/Paper Submissions</HD>
                <P>Submit written/paper submissions as follows:</P>
                <P>
                    • 
                    <E T="03">Mail/Hand delivery/Courier (for written/paper submissions):</E>
                     Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <P>• For written/paper comments submitted to the Dockets Management Staff, FDA will post your comment, as well as any attachments, except for information submitted, marked and identified, as confidential, if submitted as detailed in “Instructions.”</P>
                <P>
                    <E T="03">Instructions:</E>
                     All submissions received must include the Docket No. FDA-2017-E-6509 for “Determination of Regulatory Review Period for Purposes of Patent Extension; AUSTEDO.” Received comments, those filed in a timely manner (see 
                    <E T="02">ADDRESSES</E>
                    ), will be placed in the docket and, except for those submitted as “Confidential Submissions,” publicly viewable at 
                    <E T="03">https://www.regulations.gov</E>
                     or at the Dockets Management Staff between 9 a.m. and 4 p.m., Monday through Friday.
                </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 
                    <PRTPAGE P="20897"/>
                    both copies to the Dockets Management Staff. If you do not wish your name and contact information to be made publicly available, you can provide this information on the cover sheet and not in the body of your comments and you must identify this information as “confidential.” Any information marked as “confidential” will not be disclosed except in accordance with § 10.20 (21 CFR 10.20) and other applicable disclosure law. For more information about FDA's posting of comments to public dockets, see 80 FR 56469, September 18, 2015, or access the information at: 
                    <E T="03">https://www.gpo.gov/fdsys/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.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Beverly Friedman, Office of Regulatory Policy, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 6250, Silver Spring, MD 20993, 301-796-3600.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>The Drug Price Competition and Patent Term Restoration Act of 1984 (Pub. L. 98-417) and the Generic Animal Drug and Patent Term Restoration Act (Pub. L. 100-670) generally provide that a patent may be extended for a period of up to 5 years so long as the patented item (human drug product, animal drug product, medical device, food additive, or color additive) was subject to regulatory review by FDA before the item was marketed. Under these acts, a product's regulatory review period forms the basis for determining the amount of extension an applicant may receive.</P>
                <P>A regulatory review period consists of two periods of time: A testing phase and an approval phase. For human drug products, the testing phase begins when the exemption to permit the clinical investigations of the drug becomes effective and runs until the approval phase begins. The approval phase starts with the initial submission of an application to market the human drug product and continues until FDA grants permission to market the drug product. Although only a portion of a regulatory review period may count toward the actual amount of extension that the Director of USPTO may award (for example, half the testing phase must be subtracted as well as any time that may have occurred before the patent was issued), FDA's determination of the length of a regulatory review period for a human drug product will include all of the testing phase and approval phase as specified in 35 U.S.C. 156(g)(1)(B).</P>
                <P>FDA has approved for marketing the human drug product, AUSTEDO (deutetrabenazine) indicated for treatment of chorea associated with Huntington's disease. Subsequent to this approval, the USPTO received a patent term restoration application for AUSTEDO (U.S. Patent No. 8,524,733) from Auspex Pharmaceuticals, Inc. and the USPTO requested FDA's assistance in determining the patent's eligibility for patent term restoration. In a letter dated February 2, 2018, FDA advised the USPTO that this human drug product had undergone a regulatory review period and that the approval of AUSTEDO represented the first permitted commercial marketing or use of the product. Thereafter, the USPTO requested that FDA determine the product's regulatory review period.</P>
                <HD SOURCE="HD1">II. Determination of Regulatory Review Period</HD>
                <P>FDA has determined that the applicable regulatory review period for AUSTEDO is 1,736 days. Of this time, 1,060 days occurred during the testing phase of the regulatory review period, while 676 days occurred during the approval phase. These periods of time were derived from the following dates:</P>
                <P>
                    1. 
                    <E T="03">The date an exemption under section 505(i) of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act) (21 U.S.C. 355(i)) became effective:</E>
                     July 3, 2012. FDA has verified the applicant's claim that the date the investigational new drug application became effective was July 3, 2012.
                </P>
                <P>
                    2. 
                    <E T="03">The date the application was initially submitted with respect to the human drug product under section 505 of the FD&amp;C Act:</E>
                     May 29, 2015. FDA has verified the applicant's claim that the new drug application (NDA) for AUSTEDO (NDA 208082) was initially submitted on May 29, 2015.
                </P>
                <P>
                    3. 
                    <E T="03">The date the application was approved:</E>
                     April 3, 2017. FDA has verified the applicant's claim that NDA 208082 was approved on April 3, 2017.
                </P>
                <P>This determination of the regulatory review period establishes the maximum potential length of a patent extension. However, the USPTO applies several statutory limitations in its calculations of the actual period for patent extension. In its application for patent extension, this applicant seeks 8 days of patent term extension.</P>
                <HD SOURCE="HD1">III. Petitions</HD>
                <P>
                    Anyone with knowledge that any of the dates as published are incorrect may submit either electronic or written comments and, under 21 CFR 60.24, ask for a redetermination (see 
                    <E T="02">DATES</E>
                    ). Furthermore, as specified in § 60.30 (21 CFR 60.30), any interested person may petition FDA for a determination regarding whether the applicant for extension acted with due diligence during the regulatory review period. To meet its burden, the petition must comply with all the requirements of § 60.30, including but not limited to: Must be timely (see 
                    <E T="02">DATES</E>
                    ), must be filed in accordance with § 10.20, must contain sufficient facts to merit an FDA investigation, and must certify that a true and complete copy of the petition has been served upon the patent applicant. (See H. Rept. 857, part 1, 98th Cong., 2d sess., pp. 41-42, 1984.) Petitions should be in the format specified in 21 CFR 10.30.
                </P>
                <P>
                    Submit petitions electronically to 
                    <E T="03">https://www.regulations.gov</E>
                     at Docket No. FDA-2013-S-0610. Submit written petitions (two copies are required) to the Dockets Management Staff (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Lowell J. Schiller,</NAME>
                    <TITLE>Principal Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09805 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4164-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Health Resources and Services Administration</SUBAGY>
                <SUBJECT>Testing Services and Scores for Foreign Health Care Workers To Demonstrate English Language Proficiency</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Health Resources and Services Administration (HRSA), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for comments; notice of public meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        HRSA announces a request for comments and notice of a public meeting to receive feedback on proposed updates to the list of testing services and scores for foreign health care workers to demonstrate English language proficiency pursuant to section 343 of the Illegal Immigration Reform 
                        <PRTPAGE P="20898"/>
                        and Immigrant Responsibility Act of 1996 (IIRIRA).
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P> </P>
                    <P>• The public meeting will be held on May 28, 2019, 1:00 p.m.-4:00 p.m. ET.</P>
                    <P>• Comments should be submitted by June 11, 2019, 11:59 p.m. ET.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The public may attend the public meeting via teleconference and in-person. The conference call-in number is (888) 455-4758; Participant Passcode is 3016308. The address for the public meeting is 5600 Fishers Lane, Room 5N54, Rockville, Maryland 20857.</P>
                    <P>
                        Comments should be sent to 
                        <E T="03">HRSAComments@hrsa.gov</E>
                         with the subject line: “Testing Services and Scores for Foreign Health Care Workers”.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        LCDR Charlie Darr, Office of Global Health, HRSA, 5600 Fishers Lane, Rockville, Maryland 20857; via email: 
                        <E T="03">OGHpublicmeeting@hrsa.gov;</E>
                         or phone: (301) 443-2741.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Background</HD>
                <P>The purpose of this request for comments and notice of public meeting is to elicit stakeholder feedback to HRSA regarding its proposed updates to the list of approved testing services and passing scores pursuant to section 343 of the IIRIRA and implementing regulations promulgated by the Department of Homeland Security (DHS). Specifically, HRSA is seeking comments regarding the current and proposed list of approved standardized tests and passing scores, required for certification of foreign health care workers seeking to demonstrate English language proficiency under section 343 of the IIRIRA and implementing regulations.</P>
                <P>Under the authority of section 343 of IIRIRA, Public Law 104-208 (8 U.S.C. 1182(a)(5)(C)), as implemented by the Department of Homeland Security (DHS) at 8 CFR 212.15(g), standards for these English language requirements, as shown by an appropriate minimum score on one or more nationally recognized, commercially available, standardized assessments of the applicant's ability to speak and write, are set by the Secretary of HHS. Demonstration of English language proficiency is an element of the certification requirements for foreign health care workers seeking admission to the United States for the primary purpose of performing labor in a covered health care occupation. DHS implementing regulations authorize HHS to notify DHS of additions and deletions to the approved list of testing services and scores.</P>
                <P>HRSA, under authority delegated by HHS, reviews and evaluates studies and other supporting materials presented to evaluate English language proficiency tests and language scoring level for the health occupations described in 8 CFR 212.15. Accordingly, HRSA is seeking public comment on proposed additions and deletions to the list of testing services and passing scores, including comments that address studies, methodologies, and analysis of such tests and passing scores.</P>
                <HD SOURCE="HD1">Below is a Description of the HRSA-Proposed Updates to the Tests Listed in the Regulation at 8 CFR 212.15</HD>
                <FP SOURCE="FP-2">
                    <E T="03">HRSA is not proposing changes to the current standardized tests and scores for the following tests listed in the DHS regulation:</E>
                </FP>
                <FP SOURCE="FP1-2">• Paper-delivered version of the Electronic Testing Service (ETS), Test of English as a Foreign Language (TOEFL-Paper-delivered Test);</FP>
                <FP SOURCE="FP1-2">• Test of English in International Communication (TOEIC); and</FP>
                <FP SOURCE="FP1-2">• International English Language Testing System</FP>
                <FP SOURCE="FP-2">
                    <E T="03">HRSA is proposing to add the following standardized tests (with indicated passing scores) to the tests currently listed in the DHS regulation:</E>
                </FP>
                <FP SOURCE="FP1-2">• Internet-based version of the ETS TOEFL Test</FP>
                <P>The ETS TOEFL test, delivered via the internet, measures the test-taker's ability to use and understand English by evaluating combined reading, listening, speaking, and writing skills. Each section of the test (Reading, Listening, Speaking, and Writing) has a maximum score of 30 points, with a maximum total score of 120 points. The proposed overall passing score for occupational therapists and physical therapists is 89, including an aggregate minimum score of 63 on the Reading, Listening, and Writing sections, and a minimum score of 26 on the Speaking section. The proposed overall passing score for registered nurses and other foreign-educated health care workers whose occupations require attainment of a baccalaureate degree is 81, including an aggregate minimum score of 57 on the Reading, Listening, and Writing sections, and a minimum score of 24 on the Speaking section. The proposed overall passing score for occupations requiring less than a baccalaureate degree is 77, including an aggregate minimum score of 53 on the Reading, Listening, and Writing sections, and a minimum score of 24 on the Speaking section.  </P>
                <FP SOURCE="FP-2">• TOEIC Speaking and Writing Tests</FP>
                <P>ETS has eliminated the Test of Spoken English and the Test of Written English from its currently available offerings and added the TOEIC Speaking Test and Writing Tests. Both the TOEIC Speaking and Writing tests are scored on a scale of 0-200. HRSA proposes a passing score of 160 on the TOEIC Speaking Test and 150 on the TOEIC Writing Test for registered nurses and other health care occupations requiring attainment of a baccalaureate degree, in addition to passing scores on the TOEIC test measuring Listening and Reading comprehension (passing score of 725 remains unchanged from current IIRIRA regulations). For health care occupations requiring less than a baccalaureate degree, HRSA proposes a passing score of 160 on the TOEIC Speaking Test and 150 on the TOEIC Writing Test; in addition to passing scores on the TOEIC test measuring Listening and Reading comprehension (passing score of 700 remains unchanged from current IIRIRA regulations).</P>
                <FP SOURCE="FP-2">• Pearson Test of English Academic (PTE Academic)</FP>
                <P>PTE Academic is a computer-based, internationally recognized, commercially available, standardized assessment of written and spoken English that measures the reading, writing, listening, and speaking abilities of test takers. The test includes an overall score (the Global Scale of English) that ranges from 10-90 and shows the overall English academic language ability of a test taker. Each test assesses an individual's communicative and enabling skills in sections (listening, reading, speaking, writing, grammar oral fluency, pronunciation, spelling, vocabulary, and written discourse) from a range of 10-90. HRSA proposes to add PTE Academic to the list of approved tests for registered nurses and other health care occupations requiring attainment of a baccalaureate degree, and for health care occupations requiring less than a baccalaureate degree. HRSA proposes a passing score of 55 with no individual communicative or enabling skills score below 50.</P>
                <FP SOURCE="FP-2">
                    <E T="03">HRSA is proposing to delete the following standardized tests (which are no longer in use) from the tests currently listed in the DHS regulation:</E>
                </FP>
                <FP SOURCE="FP1-2">
                    • 
                    <E T="03">ETS:</E>
                     Test of Spoken English and Test of Written English—Eliminated from the current available offerings by ETS.
                </FP>
                <FP SOURCE="FP1-2">
                    • TOEFL Computer-based Test—Discontinued by ETS.
                    <PRTPAGE P="20899"/>
                </FP>
                <HD SOURCE="HD1">II. Format</HD>
                <P>
                    <E T="03">Request for Comment:</E>
                     Comments should be submitted to HRSA by June 11, 2019, 11:59 p.m. ET. Email comments to 
                    <E T="03">HRSAComments@hrsa.gov</E>
                     with the subject line: “Testing Services and Scores for Foreign Health Care Workers”.
                </P>
                <P>
                    <E T="03">Public Meeting:</E>
                     This meeting is open to the public. Attendance can be by teleconference or in person. To register for either the teleconference or in person attendance, please provide complete contact information for each attendee, including name, title, affiliation, address, email, telephone number, and indicate teleconference or in person attendance to 
                    <E T="03">OGHpublic meeting@hrsa.gov</E>
                     by 11:59 p.m. on Tuesday, May 14, 2019. Registration is free. Registrants will receive a registration confirmation once accepted via email.
                </P>
                <P>
                    <E T="03">Requests for Oral Presentations:</E>
                     During registration, you may request to present at the public meeting, and specify which topic(s) you wish to address. Individuals and organizations with common interests are urged to consolidate or coordinate their presentations, and request time for a joint presentation. All requests to make oral presentations are due by the close of registration on Tuesday, May 14, 2019.
                </P>
                <P>
                    Individuals who plan to attend and need special assistance or another reasonable accommodation should notify LCDR Charlie Darr (see the 
                    <E T="02">For Further Information Contact</E>
                     section) at least 10 business days prior to the meeting. Since this meeting occurs in a federal government building, attendees must go through a security check to enter the building. Non-U.S. citizen attendees must notify HRSA of their planned attendance at least 20 business days prior to the meeting in order to facilitate their entry into the building. All attendees are required to present government-issued identification prior to entry.
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>George Sigounas,</NAME>
                    <TITLE>Administrator.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09730 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4165-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute on Aging; Amended Notice of Meeting</SUBJECT>
                <P>
                    Notice is hereby given of a change in the meeting of the Behavior and Social Science of Aging Review Committee, June 05, 2019, 11:00 a.m. to June 06, 2019, 11:00 a.m., Hotel Kabuki, 1625 Post Street, San Francisco, CA 94155 which was published in the 
                    <E T="04">Federal Register</E>
                     on February 27, 2019, 84 FR 6405.
                </P>
                <P>The meeting notice is amended to change the two-day meetings' starting and ending times on June 5, 2019 to 9:00 a.m.-5:00 p.m. and on June 6, 2019 to 8:30 a.m.-3:00 p.m. The meetings are closed to the public.</P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Melanie J. Pantoja,</NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09738 Filed 5-10-19; 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 Diabetes and Digestive and Kidney Diseases; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) 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>
                         National Institute of Diabetes and Digestive and Kidney Diseases Initial Review Group; Diabetes, Endocrinology and Metabolic Diseases B Subcommittee.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 4-6, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         5:30 p.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>
                         The Westin St. Francis, 335 Powell Street, San Francisco, CA 94102.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         John F. Connaughton, Ph.D., Chief, Scientific Review Branch, Review Branch, DEA, NIDDK, National Institutes of Health, Room 7007, 6707 Democracy Boulevard, Bethesda, MD 20892-5452, (301) 594-7797, 
                        <E T="03">connaughtonj@extra.niddk.nih.gov.</E>
                          
                    </P>
                    <P>This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle. </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Diabetes and Digestive and Kidney Diseases Initial Review Group; Kidney, Urologic and Hematologic Diseases D Subcommittee.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 19-20, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8: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>
                         Hyatt Regency Bethesda, One Bethesda Metro Center, 7400 Wisconsin Avenue, Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Barbara A. Woynarowska, Ph.D., Scientific Review Administrator, Review Branch, DEA, NIDDK, National Institutes of Health, Room 7007, 6707 Democracy Boulevard, Bethesda, MD 20892-5452, (301) 402-7172, 
                        <E T="03">woynarowskab@niddk.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Diabetes and Digestive and Kidney Diseases Initial Review Group; Digestive Diseases and Nutrition C Subcommittee.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 19-21, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         6:00 p.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>
                         Bethesda North Marriott Hotel &amp; Conference Center, 5701 Marinelli Road, Bethesda, MD 20852.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Maria E. Davila-Bloom, Ph.D., Scientific Review Officer, Review Branch, DEA, NIDDK, National Institutes of Health, Room 7017, 6707 Democracy Boulevard, Bethesda, MD 20892-5452, (301) 594-7637, 
                        <E T="03">davila-bloomm@extra.niddk.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.847, Diabetes, Endocrinology and Metabolic Research; 93.848, Digestive Diseases and Nutrition Research; 93.849, Kidney Diseases, Urology and Hematology Research, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Melanie J. Pantoja,</NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09740 Filed 5-10-19; 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 Center for Complementary &amp; Integrative Health; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended, notice is hereby given of the following meeting.</P>
                <P>
                    The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The 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 
                    <PRTPAGE P="20900"/>
                    would constitute a clearly unwarranted invasion of personal privacy.
                </P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Center for Complementary and Integrative Health Special Emphasis Panel; Promoting Research on Music and Health.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 19, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:00 a.m. to 6:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Bethesda North Marriott Hotel &amp; Conference Center, Salon H, 5701 Marinelli Road, Rockville, MD 20852.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Pamela Eugenia Jeter, Ph.D., Scientific Review Officer, Office of Scientific Review, Division of Extramural Activities, NCCIH, NIH, 6707 Democracy Boulevard, Suite 401, Bethesda, MD 20892—547, 301-435-2591, 
                        <E T="03">pamela.jeter@nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.213, Research and Training in Complementary and Alternative Medicine, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Ronald J. Livingston, Jr.,</NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09739 Filed 5-10-19; 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>Office of the Director, National Institutes of Health; Amended Notice of Meeting</SUBJECT>
                <P>
                    Notice is hereby given of a change in the meeting of the Council of Councils, May 17, 2019, 08:15 a.m. to May 17, 2019, 04:00 p.m., National Institutes of Health, The Cloisters Building, 1 Cloisters Court, Bethesda, MD 20892 which was published in the 
                    <E T="04">Federal Register</E>
                     on February 08, 2019, 84 FR 2889.
                </P>
                <P>The meeting notice is amended to change the open and closed session meeting times as follows: The morning open session end time will change from 12:00 p.m. to 11:30 a.m.; the closed session will change from 12:00 p.m.-1:30 p.m. to 11:45 a.m.-12:15 p.m.; and the afternoon open session start time will change from 1:30 p.m. to 1:15 p.m.</P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Ronald J. Livingston, Jr.,</NAME>
                    <TITLE> Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09734 Filed 5-10-19; 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 Cancer Institute; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) 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 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 Cancer Institute Special Emphasis Panel; NCI R38 Review.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 21, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:30 a.m. to 1:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         NCI Shady Grove, 9609 Medical Center Drive, Room 7W110, Rockville, MD 20850 (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Sanita Bharti, Ph.D. Scientific Review Officer,  Research Programs Review Branch, Division of Extramural Activities, National Cancer Institute, NIH 9609 Medical Center Drive, Room 7W122 Bethesda, MD 20892-9750 240-276-5909 
                        <E T="03">sanita.bharti@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Cancer Institute Special Emphasis Panel Validation of Cancer Markers (UH2/UH3).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 26, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         12:00 p.m. to 1:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         NCI Shady Grove, 9609 Medical Center Drive, Room 7W244, Rockville, MD 20850 (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         John P. Cairns, Ph.D. Scientific Review Officer,  Research Programs Review Branch, Division of Extramural Activities, National Cancer Institute, NIH 9609 Medical Center Drive, Room 7W244 Bethesda, MD 20892-9750 240-276-5415 
                        <E T="03">paul.cairns@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Cancer Institute Special Emphasis Panel; SEP-7: NCI Clinical and Translational R21 and Omnibus R03.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 28, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         11:00 a.m. to 3:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         NCI Shady Grove, 9609 Medical Center Drive, Room 7W640, Rockville, MD 20850 (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Saejeong J. Kim, Ph.D. Scientific Review Officer,  Special Review Branch, Division of Extramural Activities, National Cancer Institute, NIH 9609 Medical Center Drive, Room 7W640 Bethesda, MD 20892-9750 240-276-5179 
                        <E T="03">saejeong.kim@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Cancer Institute Special Emphasis Panel; UE4/U24 Review.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 9, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         1:00 p.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>
                         NCI Shady Grove, 9609 Medical Center Drive, Room 7W110, Rockville, MD 20850 (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Robert E. Bird, Ph.D. Scientific Review Officer,  Research Program Review Branch, Division of Extramural Activities, National Cancer Institute, NIH 9609 Medical Center Drive, Room 7W110 Bethesda, MD 20892-9750 240-276-6344 
                        <E T="03">birdr@mail.nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Cancer Institute Special Emphasis Panel; Advancing Cancer Immunotherapy by Mitigating-Immune related adverse events.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 17, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8: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>
                         Hilton Washington/Rockville, 1750 Rockville Pike Rockville, MD 20852.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Shari W. Campbell, DPM, MSHS Scientific Review Officer, Resources and Training Review Branch, Division of Extramural Activities, National Cancer Institute, NIH 9609 Medical Center Drive, Room 7W612 Bethesda, MD 20892-9750 240-276-7381 
                        <E T="03">shari.campbell@nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.392, Cancer Construction; 93.393, Cancer Cause and Prevention Research; 93.394, Cancer Detection and Diagnosis Research; 93.395, Cancer Treatment Research; 93.396, Cancer Biology Research; 93.397, Cancer Centers Support; 93.398, Cancer Research Manpower; 93.399, Cancer Control, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Melanie J. Pantoja,</NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09736 Filed 5-10-19; 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 Diabetes and Digestive and Kidney Diseases; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) 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., 
                    <PRTPAGE P="20901"/>
                    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 Institute of Diabetes and Digestive and Kidney Diseases Special Emphasis Panel, NIDDK Biostatistics Research Centers.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         May 29, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 11:45 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, Two Democracy Plaza, 6707 Democracy Boulevard, Bethesda, MD 20892 (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Elena Sanovich, Ph.D., Scientific Review Officer, Review Branch, DEA, NIDDK, National Institutes of Health, Room 7351, 6707 Democracy Boulevard, Bethesda, MD 20892-2542, 301-594-8886, 
                        <E T="03">sanoviche@mail.nih.gov.</E>
                    </P>
                    <P>This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle.</P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Diabetes and Digestive and Kidney Diseases Special Emphasis Panel, Fellowships in Digestive Diseases and Nutrition.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 6-7, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8: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>
                         Residence Inn Bethesda, 7335 Wisconsin Avenue, Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Jian Yang, Ph.D., Scientific Review Officer, Review Branch, DEA, NIDDK, National Institutes of Health, Room 7111, 6707 Democracy Boulevard, Bethesda, MD 20892-5452, (301) 594-7799, 
                        <E T="03">yangj@extra.niddk.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Diabetes and Digestive and Kidney Diseases Special Emphasis Panel, NIDDK DDK-D Member COI SEP.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 7, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8: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>
                         Embassy Suites Alexandria Old Town, 1900 Diagonal Road, Alexandria, VA 22314.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Xiaodu Guo, MD, Ph.D., Scientific Review Officer, Review Branch, DEA, NIDDK, National Institutes of Health, Room 7023, 6707 Democracy Boulevard, Bethesda, MD 20892-5452, (301) 594-4719, 
                        <E T="03">guox@extra.niddk.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Diabetes and Digestive and Kidney Diseases Special Emphasis Panel, NIDDK KUH Fellowship Review.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 7, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:00 a.m. to 2:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Embassy Suites Alexandria Old Town, 1900 Diagonal Road, Alexandria, VA 22314.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Xiaodu Guo, MD, Ph.D., Scientific Review Officer, Review Branch, DEA, NIDDK, National Institutes of Health, Room 7023, 6707 Democracy Boulevard, Bethesda, MD 20892-5452, (301) 594-4719, 
                        <E T="03">guox@extra.niddk.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Diabetes and Digestive and Kidney Diseases Special Emphasis Panel, DDK-C Member Conflicts.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 7, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8: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>
                         Residence Inn Bethesda, 7335 Wisconsin Avenue, Bethesda, MD 20814 (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Jian Yang, Ph.D., Scientific Review Officer, Review Branch, DEA, NIDDK, National Institutes of Health, Room 7111, 6707 Democracy Boulevard, Bethesda, MD 20892-5452, (301) 594-7799, 
                        <E T="03">yangj@extra.niddk.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.847, Diabetes, Endocrinology and Metabolic Research; 93.848, Digestive Diseases and Nutrition Research; 93.849, Kidney Diseases, Urology and Hematology Research, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Melanie J. Pantoja,</NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09733 Filed 5-10-19; 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 &amp; Human Development; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) 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>
                         National Institute of Child Health and Human Development Initial Review; Group Health, Behavior, and Context Subcommittee.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 10, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8: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>
                         Bethesda Residence Inn Downtown, 7335 Wisconsin Ave., Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Kimberly L. Houston, MD, Scientific Review Officer, Eunice Kennedy Shriver National Institute of Children Health and Human Development, 6701B Rockledge Drive, Room 2127B, Bethesda, MD 20892, 301-827-4902, 
                        <E T="03">kimberly.houston@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Child Health and Human Development Initial Review; Pediatrics Subcommittee.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 14, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8: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>
                         Bethesda Residence Inn Downtown, 7335 Wisconsin Ave., Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Rita Anand, Ph.D., Scientific Review Officer, Eunice Kennedy Shriver National Institute of Children Health and Human Development, 6701B Rockledge Drive, Bethesda, MD 20892, (301) 496-1487, 
                        <E T="03">anandr@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Child Health and Human Development Initial Review, Obstetrics and Maternal-Fetal Biology Subcommittee.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 21, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8: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>
                         Bethesda Residence Inn Downtown, 7335 Wisconsin Ave., Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Peter Zelazowski, Ph.D., Scientific Review Officer, Eunice Kennedy Shriver National Institute of Children Health and Human Development, 6701B Rockledge Drive, Bethesda, MD 20892, 301-435-6902, 
                        <E T="03">PETER.ZELAZOWSKI@NIH.GOV.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Child Health and Human Development Initial Review; Reproduction, Andrology and Gynecology (RAG) Subcommittee.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 28, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8: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>
                         Bethesda North Marriott Hotel &amp; Conference Center, 5701 Marinelli Road, Bethesda, MD 20852.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Helen Huang, Scientific Review Officer, Eunice Kennedy Shriver National Institute of Children Health and Human Development, 6701B Rockledge Drive, Bethesda, MD 20892, 301-435-8207, 
                        <E T="03">helen.huang@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Child Health and Human Development Special Emphasis Panel; HEAL Initiative: Antenatal Opioid Exposure Longitudinal Study Consortium (PL1 Clinical Trial Not Allowed).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 18, 2019.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8: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>
                         Residence Inn Bethesda, 7335 Wisconsin Avenue, Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Peter Zelazowski, Ph.D., Scientific Review Officer, Eunice Kennedy Shriver National Institute of Children Health and Human Development, 6701B Rockledge Drive, Bethesda, MD 20892, 301-435-6902, 
                        <E T="03">peter.zelazowski@nih.gov.</E>
                    </P>
                    <PRTPAGE P="20902"/>
                    <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: May 7, 2019.</DATED>
                    <NAME>Ronald J. Livingston, Jr.,</NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09735 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <DEPDOC>[Docket No. USCG-2019-0263]</DEPDOC>
                <SUBJECT>Information Collection Request to Office of Management and Budget; OMB Control Number: 1625-0077</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Sixty-day notice requesting comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In compliance with the Paperwork Reduction Act of 1995, the U.S. Coast Guard intends to submit an Information Collection Request (ICR) to the Office of Management and Budget (OMB), Office of Information and Regulatory Affairs (OIRA), requesting an extension of its approval for the following collection of information: 1625-0077, Security Plans for Ports, Vessels, Facilities, and Outer Continental Shelf Facilities and Other Security-Related Requirements, without change. Our ICR describes the information we seek to collect from the public. Before submitting this ICR to OIRA, the Coast Guard is inviting comments as described below.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must reach the Coast Guard on or before July 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments identified by Coast Guard docket number [USCG-2019-0263] to the Coast Guard using the Federal eRulemaking Portal at 
                        <E T="03">https://www.regulations.gov.</E>
                         See the “Public participation and request for comments” portion of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for further instructions on submitting comments.
                    </P>
                    <P>
                        A copy of the ICR is available through the docket on the internet at 
                        <E T="03">https://www.regulations.gov.</E>
                         Additionally, copies are available from: Commandant (CG-612), ATTN: Paperwork Reduction Act Manager, U.S. Coast Guard, 2703 Martin Luther King Jr; Ave. SE, STOP 7710, Washington, DC 20593-7710.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION:</HD>
                    <P>Contact Mr. Anthony Smith, Office of Information Management, telephone 202-475-3532, or fax 202-372-8405, for questions on these documents.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Public Participation and Request for Comments</HD>
                <P>This notice relies on the authority of the Paperwork Reduction Act of 1995; 44 U.S.C. Chapter 35, as amended. An ICR is an application to OIRA seeking the approval, extension, or renewal of a Coast Guard collection of information (Collection). The ICR contains information describing the Collection's purpose, the Collection's likely burden on the affected public, an explanation of the necessity of the Collection, and other important information describing the Collection. There is one ICR for each Collection.</P>
                <P>The Coast Guard invites comments on whether this ICR should be granted based on the Collection being necessary for the proper performance of Departmental functions. In particular, the Coast Guard would appreciate comments addressing: (1) The practical utility of the Collection; (2) the accuracy of the estimated burden of the Collection; (3) ways to enhance the quality, utility, and clarity of information subject to the Collection; and (4) ways to minimize the burden of the Collection on respondents, including the use of automated collection techniques or other forms of information technology. Consistent with the requirements of Executive Order 13771, Reducing Regulation and Controlling Regulatory Costs, and Executive Order 13777, Enforcing the Regulatory Reform Agenda, the Coast Guard is also requesting comments on the extent to which this request for information could be modified to reduce the burden on respondents. In response to your comments, we may revise this ICR or decide not to seek an extension of approval for the Collection. We will consider all comments and material received during the comment period.</P>
                <P>We encourage you to respond to this request by submitting comments and related materials. Comments must contain the OMB Control Number of the ICR and the docket number of this request, [USCG-2019-0263], and must be received by July 12, 2019.</P>
                <HD SOURCE="HD1">Submitting Comments</HD>
                <P>
                    We encourage you to submit comments through the Federal eRulemaking Portal at 
                    <E T="03">https://www.regulations.gov.</E>
                     If your material cannot be submitted using 
                    <E T="03">https://www.regulations.gov,</E>
                     contact the person in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this document for alternate instructions. Documents mentioned in this notice, and all public comments, are in our online docket at 
                    <E T="03">https://www.regulations.gov</E>
                     and can be viewed by following that website's instructions. Additionally, if you go to the online docket and sign up for email alerts, you will be notified when comments are posted.
                </P>
                <P>
                    We accept anonymous comments. All comments received will be posted without change to 
                    <E T="03">https://www.regulations.gov</E>
                     and will include any personal information you have provided. For more about privacy and the docket, you may review a Privacy Act notice regarding the Federal Docket Management System in the March 24, 2005, issue of the 
                    <E T="04">Federal Register</E>
                     (70 FR 15086).
                </P>
                <HD SOURCE="HD1">Information Collection Request</HD>
                <P>
                    <E T="03">Title:</E>
                     Security Plans for Ports, Vessels, Facilities, and Outer Continental Shelf Facilities and Other Security-Related Requirements.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1625-0077.
                </P>
                <P>
                    <E T="03">Summary:</E>
                     This information collection is associated with the maritime security requirements mandated by the Maritime Transportation Security Act (MTSA) of 2002. Security assessments, security plans and other security-related requirements are in Title 33 CFR Pars 101 through 106.
                </P>
                <P>
                    <E T="03">Need:</E>
                     This information is needed to determine if vessels and facilities are in compliance with certain security standards.
                </P>
                <P>
                    <E T="03">Forms:</E>
                     CG-6025, Facility Vulnerability and Security Measures Summary, and CG-6025A, Vulnerability and Security Measures Addendum.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Vessel and Facility owners and operators.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Hour Burden Estimate:</E>
                     The estimated burden has increased from 1,127,500 hours to 1,198,530 hours a year, due to an increase in the estimated annual number of responses.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>The Paperwork Reduction Act of 1995; 44 U.S.C. Chapter 35, as amended.</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>James D. Roppel,</NAME>
                    <TITLE>U.S. Coast Guard, Chief, Office of Information Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09754 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 9110-04-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="20903"/>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
                <SUBJECT>Accreditation and Approval of AmSpec LLC (Texas City, TX) as a Commercial Gauger and Laboratory</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Customs and Border Protection, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of accreditation and approval of AmSpec LLC (Texas City, TX), as a commercial gauger and laboratory.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, pursuant to CBP regulations, that AmSpec LLC (Texas City, TX), has been approved to gauge petroleum and certain petroleum products and accredited to test petroleum and certain petroleum products for customs purposes for the next three years as of September 26, 2018.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>AmSpec LLC (Texas City, TX) was approved and accredited as a commercial gauger and laboratory as of September 26, 2018. The next triennial inspection date will be scheduled for September 2021.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dr. Justin Shey, Laboratories and Scientific Services, U.S. Customs and Border Protection, 1300 Pennsylvania Avenue NW, Suite 1500N, Washington, DC 20229, tel. 202-344-1060.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is hereby given pursuant to 19 CFR 151.12 and 19 CFR 151.13, that AmSpec LLC, 3208 5th Avenue South, Texas City, TX 77590, has been approved to gauge petroleum and certain petroleum products and accredited to test petroleum and certain petroleum products for customs purposes, in accordance with the provisions of 19 CFR 151.12 and 19 CFR 151.13.</P>
                <P>AmSpec LLC (Texas City, TX) is approved for the following gauging procedures for petroleum and certain petroleum products from the American Petroleum Institute (API):</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="xs54,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">API chapters</CHED>
                        <CHED H="1">Title</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">3</ENT>
                        <ENT>Tank Gauging.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7</ENT>
                        <ENT>Temperature Determination.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8</ENT>
                        <ENT>Sampling.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">11</ENT>
                        <ENT>Physical Properties Data.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12</ENT>
                        <ENT>Calculations.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">17</ENT>
                        <ENT>Maritime Measurement.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>AmSpec LLC (Texas City, TX) is accredited for the following laboratory analysis procedures and methods for petroleum and certain petroleum products set forth by the U.S. Customs and Border Protection Laboratory Methods (CBPL) and American Society for Testing and Materials (ASTM):</P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="xs54,xls30,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">CBPL No.</CHED>
                        <CHED H="1">ASTM</CHED>
                        <CHED H="1">Title</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">27-03</ENT>
                        <ENT>D4006</ENT>
                        <ENT>Standard Test Method for Water in Crude Oil by Distillation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-04</ENT>
                        <ENT>D95</ENT>
                        <ENT>Standard Test Method for Water in Petroleum Products and Bituminous Materials by Distillation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-05</ENT>
                        <ENT>D4928</ENT>
                        <ENT>Standard Test Method for Water in Crude Oils by Coulometric Karl Fischer Titration.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-06</ENT>
                        <ENT>D473</ENT>
                        <ENT>Standard Test Method for Sediment in Crude Oils and Fuel Oils by the Extraction Method.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-08</ENT>
                        <ENT>D86</ENT>
                        <ENT>Standard Test Method for Distillation of Petroleum Products at Atmospheric Pressure.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-11</ENT>
                        <ENT>D445</ENT>
                        <ENT>Standard Test Method for Kinematic Viscosity of Transparent and Opaque Liquids (and Calculation of Dynamic Viscosity).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-13</ENT>
                        <ENT>D4294</ENT>
                        <ENT>Standard Test Method for Sulfur in Petroleum and Petroleum Products by Energy-Dispersive X-ray Fluorescence Spectrometry.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-14</ENT>
                        <ENT>D2622</ENT>
                        <ENT>Standard Test Method for Sulfur in Petroleum Products by Wavelength Dispersive X-Ray Fluorescence Spectrometry.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-46</ENT>
                        <ENT>D5002</ENT>
                        <ENT>Standard Test Method for Density, Relative Density, and API Gravity of Crude Oils by Digital Density Analyzer.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-48</ENT>
                        <ENT>D4052</ENT>
                        <ENT>Standard Test Method for Density and Relative Density of Liquids by Digital Density Meter.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-50</ENT>
                        <ENT>D93</ENT>
                        <ENT>Standard Test Methods for Flash-Point by Pensky-Martens Closed Cup Tester.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-53</ENT>
                        <ENT>D2709</ENT>
                        <ENT>Standard Test Method for Water and Sediment in Middle Distillate Fuels by Centrifuge.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-54</ENT>
                        <ENT>D1796</ENT>
                        <ENT>Standard Test Method for Water and Sediment in Fuel Oils by the Centrifuge Method.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-58</ENT>
                        <ENT>D5191</ENT>
                        <ENT>Standard Test Method for Vapor Pressure of Petroleum Products (Mini Method).</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Anyone wishing to employ this entity to conduct laboratory analyses and gauger services should request and receive written assurances from the entity that it is accredited or approved by the U.S. Customs and Border Protection to conduct the specific test or gauger service requested. Alternatively, inquiries regarding the specific test or gauger service this entity is accredited or approved to perform may be directed to the U.S. Customs and Border Protection by calling (202) 344-1060. The inquiry may also be sent to 
                    <E T="03">CBPGaugersLabs@cbp.dhs.gov.</E>
                     Please reference the website listed below for a complete listing of CBP approved gaugers and accredited laboratories: 
                    <E T="03">http://www.cbp.gov/about/labs-scientific/commercial-gaugers-and-laboratories</E>
                    .
                </P>
                <SIG>
                    <DATED>Dated: May 3, 2019.</DATED>
                    <NAME>Patricia Hawes Coleman,</NAME>
                    <TITLE>Acting Executive Director, Laboratories and Scientific Services Directorate.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09832 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 9111-14-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
                <SUBJECT>Accreditation and Approval of AmSpec LLC (Savannah, GA) as a Commercial Gauger and Laboratory</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Customs and Border Protection, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of accreditation and approval of AmSpec LLC (Savannah, GA), as a commercial gauger and laboratory.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, pursuant to CBP regulations, that AmSpec LLC (Savannah, GA), has been approved to gauge petroleum and certain petroleum products and accredited to test petroleum and certain petroleum products for customs purposes for the next three years as of September 6, 2018.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>AmSpec LLC (Savannah, GA) was approved and accredited as a commercial gauger and laboratory as of September 6, 2018. The next triennial inspection date will be scheduled for September 2021.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dr. Justin Shey, Laboratories and Scientific Services, U.S. Customs and Border Protection, 1300 Pennsylvania Avenue NW, Suite 1500N, Washington, DC 20229, tel. 202-344-1060.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Notice is hereby given pursuant to 19 CFR 151.12 
                    <PRTPAGE P="20904"/>
                    and 19 CFR 151.13, that AmSpec LLC, 4117 Montgomery St., Savannah, GA 31405, has been approved to gauge petroleum and certain petroleum products and accredited to test petroleum and certain petroleum products for customs purposes, in accordance with the provisions of 19 CFR 151.12 and 19 CFR 151.13.
                </P>
                <P>AmSpec LLC (Savannah, GA) is approved for the following gauging procedures for petroleum and certain petroleum products from the American Petroleum Institute (API):</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="xs54,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">API chapters</CHED>
                        <CHED H="1">Title</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">3</ENT>
                        <ENT>Tank Gauging.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7</ENT>
                        <ENT>Temperature Determination.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8</ENT>
                        <ENT>Sampling.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">11</ENT>
                        <ENT>Physical Properties Data.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12</ENT>
                        <ENT>Calculations.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">17</ENT>
                        <ENT>Maritime Measurement.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>AmSpec LLC (Savannah, GA) is accredited for the following laboratory analysis procedures and methods for petroleum and certain petroleum products set forth by the U.S. Customs and Border Protection Laboratory Methods (CBPL) and American Society for Testing and Materials (ASTM):</P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="xs54,xls30,r100">
                    <BOXHD>
                        <CHED H="1">CBPL No.</CHED>
                        <CHED H="1">ASTM</CHED>
                        <CHED H="1">Title</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">27-01</ENT>
                        <ENT>D287</ENT>
                        <ENT>Standard Test Method for API Gravity of Crude Petroleum and Petroleum Products (Hydrometer Method).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-02</ENT>
                        <ENT>D1298</ENT>
                        <ENT>Standard Test Method for Density, Relative Density (Specific Gravity), or API Gravity of Crude Petroleum and Liquid Petroleum Products by Hydrometer Method.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-03</ENT>
                        <ENT>D4006</ENT>
                        <ENT>Standard Test Method for Water in Crude Oil by Distillation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-04</ENT>
                        <ENT>D95</ENT>
                        <ENT>Standard Test Method for Water in Petroleum Products and Bituminous Materials by Distillation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-05</ENT>
                        <ENT>D4928</ENT>
                        <ENT>Standard Test Method for Water in Crude Oils by Coulometric Karl Fischer Titration.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-06</ENT>
                        <ENT>D473</ENT>
                        <ENT>Standard Test Method for Sediment in Crude Oils and Fuel Oils by the Extraction Method.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-08</ENT>
                        <ENT>D86</ENT>
                        <ENT>Standard Test Method for Distillation of Petroleum Products at Atmospheric Pressure.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-11</ENT>
                        <ENT>D445</ENT>
                        <ENT>Standard Test Method for Kinematic Viscosity of Transparent and Opaque Liquids (and Calculation of Dynamic Viscosity).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-13</ENT>
                        <ENT>D4294</ENT>
                        <ENT>Standard Test Method for Sulfur in Petroleum and Petroleum Products by Energy-Dispersive X-ray Fluorescence Spectrometry.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-48</ENT>
                        <ENT>D4052</ENT>
                        <ENT>Standard Test Method for Density and Relative Density of Liquids by Digital Density Meter.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-50</ENT>
                        <ENT>D93</ENT>
                        <ENT>Standard Test Methods for Flash-Point by Pensky-Martens Closed Cup Tester.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-53</ENT>
                        <ENT>D2709</ENT>
                        <ENT>Standard Test Method for Water and Sediment in Middle Distillate Fuels by Centrifuge.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-54</ENT>
                        <ENT>D1796</ENT>
                        <ENT>Standard Test Method for Water and Sediment in Fuel Oils by the Centrifuge Method.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27-58</ENT>
                        <ENT>D5191</ENT>
                        <ENT>Standard Test Method for Vapor Pressure of Petroleum Products (Mini Method).</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Anyone wishing to employ this entity to conduct laboratory analyses and gauger services should request and receive written assurances from the entity that it is accredited or approved by the U.S. Customs and Border Protection to conduct the specific test or gauger service requested. Alternatively, inquiries regarding the specific test or gauger service this entity is accredited or approved to perform may be directed to the U.S. Customs and Border Protection by calling (202) 344-1060. The inquiry may also be sent to 
                    <E T="03">CBPGaugersLabs@cbp.dhs.gov.</E>
                     Please reference the website listed below for a complete listing of CBP approved gaugers and accredited laboratories: 
                    <E T="03">http://www.cbp.gov/about/labs-scientific/commercial-gaugers-and-laboratories.</E>
                </P>
                <SIG>
                    <DATED>Dated: May 3, 2019.</DATED>
                    <NAME>Patricia Hawes Coleman,</NAME>
                    <TITLE>Acting Executive Director, Laboratories and Scientific Services Directorate.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09835 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 9111-14-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
                <SUBJECT>Approval of Freeboard International (Linden, NJ), as a Commercial Gauger</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Customs and Border Protection, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of approval of Freeboard International (Linden, NJ), as a commercial gauger.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, pursuant to CBP regulations, that Freeboard International (Linden, NJ), has been approved to gauge petroleum and certain petroleum products for customs purposes for the next three years as of August 7, 2018.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Freeboard International (Linden, NJ) was approved, as a commercial gauger as of August 7, 2018. The next triennial inspection date will be scheduled for August 2021.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dr. Justin Shey, Laboratories and Scientific Services Directorate, U.S. Customs and Border Protection, 1300 Pennsylvania Avenue NW, Suite 1500N, Washington, DC 20229, tel. 202-344-1060.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is hereby given pursuant to 19 CFR 151.13, that Freeboard International, 2500 Brunswick Ave., Linden, NJ 07036 has been approved to gauge petroleum and certain petroleum products for customs purposes, in accordance with the provisions of 19 CFR 151.13. Freeboard International (Linden, NJ) is approved for the following gauging procedures for petroleum and certain petroleum products from the American Petroleum Institute (API):</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="xs54,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">API chapters</CHED>
                        <CHED H="1">Title</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1</ENT>
                        <ENT>Vocabulary.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3</ENT>
                        <ENT>Tank Gauging.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7</ENT>
                        <ENT>Temperature Determination.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8</ENT>
                        <ENT>Sampling.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12</ENT>
                        <ENT>Calculations.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">17</ENT>
                        <ENT>Marine Measurement.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Anyone wishing to employ this entity to conduct gauger services should request and receive written assurances from the entity that it is approved by the U.S. Customs and Border Protection to conduct the specific gauger service requested. Alternatively, inquiries regarding the specific gauger service this entity is accredited or approved to perform may be directed to the U.S. Customs and Border Protection by calling (202) 344-1060. The inquiry may also be sent to 
                    <E T="03">CBPGaugersLabs@cbp.dhs.gov.</E>
                     Please reference the website listed below for a complete listing of CBP approved gaugers and accredited laboratories: 
                    <E T="03">
                        http://
                        <PRTPAGE P="20905"/>
                        www.cbp.gov/about/labs-scientific/commercial-gaugers-and-laboratories.
                    </E>
                </P>
                <SIG>
                    <DATED>Dated: May 3, 2019.</DATED>
                    <NAME>Patricia Hawes Coleman,</NAME>
                    <TITLE>Acting Executive Director, Laboratories and Scientific Services Directorate.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09834 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 9111-14-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-6166-N-01]</DEPDOC>
                <SUBJECT>Mortgage and Loan Insurance Programs Under the National Housing Act—Debenture Interest Rates</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Housing, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This Notice announces changes in the interest rates to be paid on debentures issued with respect to a loan or mortgage insured by the Federal Housing Administration under the provisions of the National Housing Act (the Act). The interest rate for debentures issued under Section 221(g)(4) of the Act during the 6-month period beginning January 1, 2019, is 3
                        <FR>1/8</FR>
                         percent. The interest rate for debentures issued under any other provision of the Act is the rate in effect on the date that the commitment to insure the loan or mortgage was issued, or the date that the loan or mortgage was endorsed (or initially endorsed if there are two or more endorsements) for insurance, whichever rate is higher. The interest rate for debentures issued under these other provisions with respect to a loan or mortgage committed or endorsed during the 6-month period beginning January 1, 2019, is 3
                        <FR>3/8</FR>
                         percent.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Elizabeth Olazabal, Department of Housing and Urban Development, 451 Seventh Street SW, Room 5146, Washington, DC 20410-8000; telephone (202) 402-4608 (this is not a toll-free number). Individuals with speech or hearing impairments may access this number through TTY by calling the toll-free Federal Information Relay Service at (800) 877-8339.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Section 224 of the National Housing Act (12 U.S.C. 1715o) provides that debentures issued under the Act with respect to an insured loan or mortgage (except for debentures issued pursuant to Section 221(g)(4) of the Act) will bear interest at the rate in effect on the date the commitment to insure the loan or mortgage was issued, or the date the loan or mortgage was endorsed (or initially endorsed if there are two or more endorsements) for insurance, whichever rate is higher. This provision is implemented in HUD's regulations at 24 CFR 203.405, 203.479, 207.259(e)(6), and 220.830. These regulatory provisions state that the applicable rates of interest will be published twice each year as a notice in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>Section 224 further provides that the interest rate on these debentures will be set from time to time by the Secretary of HUD, with the approval of the Secretary of the Treasury, in an amount not in excess of the annual interest rate determined by the Secretary of the Treasury pursuant to a statutory formula based on the average yield of all outstanding marketable Treasury obligations of maturities of 15 or more years.</P>
                <P>
                    The Secretary of the Treasury (1) has determined, in accordance with the provisions of Section 224, that the statutory maximum interest rate for the period beginning January 1, 2019, is 3
                    <FR>3/8</FR>
                     percent; and (2) has approved the establishment of the debenture interest rate by the Secretary of HUD at 3
                    <FR>3/8</FR>
                     percent for the 6-month period beginning January 1, 2019. This interest rate will be the rate borne by debentures issued with respect to any insured loan or mortgage (except for debentures issued pursuant to Section 221(g)(4)) with insurance commitment or endorsement date (as applicable) within the first 6 months of 2019.
                </P>
                <P>For convenience of reference, HUD is publishing the following chart of debenture interest rates applicable to mortgages committed or endorsed since January 1, 1980:</P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s25,r25,r25">
                    <BOXHD>
                        <CHED H="1">
                            Effective
                            <LI>interest rate </LI>
                        </CHED>
                        <CHED H="1">on or after </CHED>
                        <CHED H="1">prior to</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            9
                            <FR>1/2</FR>
                        </ENT>
                        <ENT>Jan. 1, 1980</ENT>
                        <ENT>July 1, 1980.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            9
                            <FR>7/8</FR>
                        </ENT>
                        <ENT>July 1, 1980</ENT>
                        <ENT> Jan. 1, 1981.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            11
                            <FR>3/4</FR>
                        </ENT>
                        <ENT>Jan. 1, 1981 </ENT>
                        <ENT>July 1, 1981.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            12
                            <FR>7/8</FR>
                        </ENT>
                        <ENT>July 1, 1981</ENT>
                        <ENT>Jan. 1, 1982.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            12
                            <FR>3/4</FR>
                        </ENT>
                        <ENT>Jan. 1, 1982</ENT>
                        <ENT>Jan. 1, 1983.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            10
                            <FR>1/4</FR>
                        </ENT>
                        <ENT>Jan. 1, 1983</ENT>
                        <ENT>July 1, 1983.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            10
                            <FR>3/8</FR>
                        </ENT>
                        <ENT>July 1, 1983 </ENT>
                        <ENT>Jan. 1, 1984.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            11
                            <FR>1/2</FR>
                        </ENT>
                        <ENT>Jan. 1, 1984</ENT>
                        <ENT>July 1, 1984.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            13
                            <FR>3/8</FR>
                        </ENT>
                        <ENT>July 1, 1984 </ENT>
                        <ENT>Jan. 1, 1985.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            11
                            <FR>5/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 1985</ENT>
                        <ENT>July 1, 1985.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            11
                            <FR>1/8</FR>
                        </ENT>
                        <ENT>July 1, 1985</ENT>
                        <ENT>Jan. 1, 1986.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            10
                            <FR>1/4</FR>
                        </ENT>
                        <ENT>Jan. 1, 1986</ENT>
                        <ENT>July 1, 1986.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            8
                            <FR>1/4</FR>
                        </ENT>
                        <ENT>July 1, 1986 </ENT>
                        <ENT>Jan. 1 1987.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8 </ENT>
                        <ENT>Jan. 1, 1987</ENT>
                        <ENT>July 1, 1987.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9 </ENT>
                        <ENT>July 1, 1987</ENT>
                        <ENT>Jan. 1, 1988.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            9
                            <FR>1/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 1988 </ENT>
                        <ENT>July 1, 1988.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            9
                            <FR>3/8</FR>
                        </ENT>
                        <ENT>July 1, 1988</ENT>
                        <ENT>Jan. 1, 1989.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            9
                            <FR>1/4</FR>
                        </ENT>
                        <ENT>Jan. 1, 1989 </ENT>
                        <ENT>July 1, 1989.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9 </ENT>
                        <ENT>July 1, 1989 </ENT>
                        <ENT>Jan. 1, 1990.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            8
                            <FR>1/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 1990 </ENT>
                        <ENT>July 1, 1990.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9 </ENT>
                        <ENT>July 1, 1990 </ENT>
                        <ENT>Jan. 1, 1991.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            8
                            <FR>3/4</FR>
                        </ENT>
                        <ENT>Jan. 1, 1991</ENT>
                        <ENT>July 1, 1991.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            8
                            <FR>1/2</FR>
                        </ENT>
                        <ENT>July 1, 1991 </ENT>
                        <ENT>Jan. 1, 1992.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8 </ENT>
                        <ENT>Jan. 1, 1992 </ENT>
                        <ENT>July 1, 1992.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8 </ENT>
                        <ENT>July 1, 1992</ENT>
                        <ENT>Jan. 1, 1993.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            7
                            <FR>3/4</FR>
                        </ENT>
                        <ENT>Jan. 1, 1993 </ENT>
                        <ENT>July 1, 1993.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7 </ENT>
                        <ENT>July 1, 1993 </ENT>
                        <ENT>Jan. 1, 1994.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            6
                            <FR>5/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 1994</ENT>
                        <ENT>July 1, 1994.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            7
                            <FR>3/4</FR>
                        </ENT>
                        <ENT>July 1, 1994 </ENT>
                        <ENT>Jan. 1, 1995.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            8
                            <FR>3/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 1995</ENT>
                        <ENT>July 1, 1995.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            7
                            <FR>1/4</FR>
                        </ENT>
                        <ENT>July 1, 1995 </ENT>
                        <ENT>Jan. 1, 1996.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            6
                            <FR>1/2</FR>
                        </ENT>
                        <ENT>Jan. 1, 1996</ENT>
                        <ENT>July 1, 1996.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            7
                            <FR>1/4</FR>
                        </ENT>
                        <ENT>July 1, 1996</ENT>
                        <ENT>Jan. 1, 1997.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            6
                            <FR>3/4</FR>
                        </ENT>
                        <ENT>Jan. 1, 1997 </ENT>
                        <ENT>July 1, 1997.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            7
                            <FR>1/8</FR>
                        </ENT>
                        <ENT>July 1, 1997</ENT>
                        <ENT>Jan. 1, 1998.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            6
                            <FR>3/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 1998 </ENT>
                        <ENT>July 1, 1998.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            6
                            <FR>1/8</FR>
                        </ENT>
                        <ENT>July 1, 1998 </ENT>
                        <ENT>Jan. 1, 1999.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            5
                            <FR>1/2</FR>
                        </ENT>
                        <ENT>Jan. 1, 1999 </ENT>
                        <ENT>July 1, 1999.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            6
                            <FR>1/8</FR>
                        </ENT>
                        <ENT>July 1, 1999</ENT>
                        <ENT>Jan. 1, 2000.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            6
                            <FR>1/2</FR>
                        </ENT>
                        <ENT>Jan. 1, 2000</ENT>
                        <ENT>July 1, 2000.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            6
                            <FR>1/2</FR>
                        </ENT>
                        <ENT>July 1, 2000</ENT>
                        <ENT>Jan. 1, 2001.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6 </ENT>
                        <ENT>Jan. 1, 2001 </ENT>
                        <ENT>July 1, 2001.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            5
                            <FR>7/8</FR>
                        </ENT>
                        <ENT>July 1, 2001 </ENT>
                        <ENT>Jan. 1, 2002.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            5
                            <FR>1/4</FR>
                        </ENT>
                        <ENT>Jan. 1, 2002</ENT>
                        <ENT>July 1, 2002.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            5
                            <FR>3/4</FR>
                        </ENT>
                        <ENT>July 1, 2002</ENT>
                        <ENT>Jan. 1, 2003.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5 </ENT>
                        <ENT>Jan. 1, 2003 </ENT>
                        <ENT>July 1, 2003.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            4
                            <FR>1/2</FR>
                        </ENT>
                        <ENT>July 1, 2003</ENT>
                        <ENT>Jan. 1, 2004.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            5
                            <FR>1/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 2004 </ENT>
                        <ENT>July 1, 2004.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            5
                            <FR>1/2</FR>
                        </ENT>
                        <ENT>July 1, 2004</ENT>
                        <ENT>Jan. 1, 2005.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            4
                            <FR>7/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 2005</ENT>
                        <ENT>July 1, 2005.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            4
                            <FR>1/2</FR>
                        </ENT>
                        <ENT>July 1, 2005</ENT>
                        <ENT>Jan. 1, 2006.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            4
                            <FR>7/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 2006 </ENT>
                        <ENT>July 1, 2006.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            5
                            <FR>3/8</FR>
                        </ENT>
                        <ENT>July 1, 2006 </ENT>
                        <ENT>Jan. 1, 2007.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            4
                            <FR>3/4</FR>
                        </ENT>
                        <ENT>Jan. 1, 2007 </ENT>
                        <ENT>July 1, 2007.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5 </ENT>
                        <ENT>July 1, 2007 </ENT>
                        <ENT>Jan. 1, 2008.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            4
                            <FR>1/2</FR>
                        </ENT>
                        <ENT>Jan. 1, 2008 </ENT>
                        <ENT>July 1, 2008.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            4
                            <FR>5/8</FR>
                        </ENT>
                        <ENT>July 1, 2008 </ENT>
                        <ENT>Jan. 1, 2009.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            4
                            <FR>1/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 2009 </ENT>
                        <ENT>July 1, 2009.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            4
                            <FR>1/8</FR>
                        </ENT>
                        <ENT>July 1, 2009 </ENT>
                        <ENT>Jan. 1, 2010.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            4
                            <FR>1/4</FR>
                        </ENT>
                        <ENT>Jan. 1, 2010</ENT>
                        <ENT>July 1, 2010.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            4
                            <FR>1/8</FR>
                        </ENT>
                        <ENT>July 1, 2010</ENT>
                        <ENT>Jan. 1, 2011.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            3
                            <FR>7/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 2011 </ENT>
                        <ENT>July 1, 2011.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            4
                            <FR>1/8</FR>
                        </ENT>
                        <ENT>July 1, 2011</ENT>
                        <ENT>Jan. 1, 2012.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            2
                            <FR>7/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 2012</ENT>
                        <ENT>July 1, 2012.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            2
                            <FR>3/4</FR>
                        </ENT>
                        <ENT>July 1, 2012</ENT>
                        <ENT>Jan. 1, 2013.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            2
                            <FR>1/2</FR>
                        </ENT>
                        <ENT>Jan. 1, 2013</ENT>
                        <ENT>July 1, 2013.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            2
                            <FR>7/8</FR>
                        </ENT>
                        <ENT>July 1, 2013</ENT>
                        <ENT>Jan. 1, 2014.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            3
                            <FR>5/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 2014 </ENT>
                        <ENT>July 1, 2014.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            3
                            <FR>1/4</FR>
                        </ENT>
                        <ENT>July 1, 2014</ENT>
                        <ENT>Jan. 1, 2015.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3 </ENT>
                        <ENT>Jan. 1, 2015</ENT>
                        <ENT>July 1, 2015.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            2
                            <FR>7/8</FR>
                        </ENT>
                        <ENT>July 1, 2015</ENT>
                        <ENT>Jan. 1, 2016.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            2
                            <FR>7/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 2016 </ENT>
                        <ENT>July 1, 2016.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            2
                            <FR>1/2</FR>
                        </ENT>
                        <ENT>July 1, 2016 </ENT>
                        <ENT>Jan. 1, 2017.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            2
                            <FR>3/4</FR>
                        </ENT>
                        <ENT>Jan. 1, 2017 </ENT>
                        <ENT>July 1, 2017.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            2
                            <FR>7/8</FR>
                        </ENT>
                        <ENT>July 1, 2017 </ENT>
                        <ENT>Jan. 1, 2018.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            2
                            <FR>3/4</FR>
                        </ENT>
                        <ENT>Jan. 1, 2018 </ENT>
                        <ENT>July 1, 2018.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            3
                            <FR>1/8</FR>
                        </ENT>
                        <ENT>July 1, 2018 </ENT>
                        <ENT>Jan. 1, 2019.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            3
                            <FR>3/8</FR>
                        </ENT>
                        <ENT>Jan. 1, 2019</ENT>
                        <ENT>July 1, 2019.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Section 215 of Division G, Title II of Public Law 108-199, enacted January 23, 2004 (HUD's 2004 Appropriations Act) amended Section 224 of the Act, to change the debenture interest rate for purposes of calculating certain insurance claim payments made in cash. Therefore, for all claims paid in cash on mortgages insured under Section 203 or 234 of the National Housing Act and endorsed for insurance after January 23, 2004, the debenture interest rate will be the monthly average yield, for the month in which the default on the mortgage occurred, on United States Treasury Securities adjusted to a constant maturity of 10 years, as found 
                    <PRTPAGE P="20906"/>
                    in Federal Reserve Statistical Release H-15. The Federal Housing Administration has codified this provision in HUD regulations at 24 CFR 203.405(b) and 24 CFR 203.479(b).
                </P>
                <P>Section 221(g)(4) of the Act provides that debentures issued pursuant to that paragraph (with respect to the assignment of an insured mortgage to the Secretary) will bear interest at the “going Federal rate” in effect at the time the debentures are issued. The term “going Federal rate” is defined to mean the interest rate that the Secretary of the Treasury determines, pursuant to a statutory formula based on the average yield on all outstanding marketable Treasury obligations of 8- to 12-year maturities, for the 6-month periods of January through June and July through December of each year. Section 221(g)(4) is implemented in the HUD regulations at 24 CFR 221.255 and 24 CFR 221.790.</P>
                <P>
                    The Secretary of the Treasury has determined that the interest rate to be borne by debentures issued pursuant to Section 221(g)(4) during the 6-month period beginning January 1, 2019, is 3
                    <FR>1/8</FR>
                     percent.
                </P>
                <P>The subject matter of this notice falls within the categorical exemption from HUD's environmental clearance procedures set forth in 24 CFR 50.19(c)(6). For that reason, no environmental finding has been prepared for this notice.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> Sections 211, 221, 224, National Housing Act, 12 U.S.C. 1715b, 1715l, 1715o; Section 7(d), Department of HUD Act, 42 U.S.C. 3535(d).</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: May 6, 2019.</DATED>
                    <NAME>Brian D. Montgomery,</NAME>
                    <TITLE>Assistant Secretary for Housing—Federal Housing Commissioner.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09828 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Fish and Wildlife Service</SUBAGY>
                <DEPDOC>[FWS-R4-ES-2019-0047; FXES11130400000EA-123-FF04EF1000]</DEPDOC>
                <SUBJECT>Receipt of Incidental Take Permit Application and Proposed Habitat Conservation Plan for the Scrub-Jay and Eastern Indigo Snake, Volusia County, FL; Categorical Exclusion</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability; request for comments and information.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We, the Fish and Wildlife Service (Service), announce receipt of an application from Duke Energy Florida, LLC (applicant) for an incidental take permit (ITP) under the Endangered Species Act. The applicant requests the ITP to take the federally listed scrub-jay and eastern indigo snake incidental to construction in Volusia County, Florida. We request public comment on the application, which includes the applicant's proposed habitat conservation plan (HCP) and the Service's preliminary determination that this HCP qualifies as “low-effect,” categorically excluded, under the National Environmental Policy Act. To make this determination, we used our environmental action statement and low-effect screening form, both of which are also available for review.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We must receive your written comments on or before June 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P> </P>
                    <P>
                        <E T="03">Obtaining Documents:</E>
                         You may obtain copies of the documents online in Docket No. FWS-R4-ES-2019-0047 at 
                        <E T="03">http://www.regulations.gov.</E>
                    </P>
                    <P>
                        <E T="03">Submitting Comments:</E>
                         If you wish to submit comments on any of the documents, you may do so in writing by any of the following methods:
                    </P>
                    <P>
                        • 
                        <E T="03">Online: http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments on Docket No. FWS-R4-ES-2019-0047.
                    </P>
                    <P>
                        • 
                        <E T="03">U.S. mail or hand-delivery:</E>
                         Public Comments Processing, Attn: Docket No. FWS-R4-ES-2019-0047, U.S. Fish and Wildlife Service, MS: BPHC, 5275 Leesburg Pike, Falls Church, VA 22041-3803.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Erin M. Gawera, by telephone at (904) 731-3121 or via email at 
                        <E T="03">erin_gawera@fws.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    We, the Fish and Wildlife Service (Service), announce receipt of an application from Duke Energy Florida, LLC (applicant) for an incidental take permit (ITP) under the Endangered Species Act of 1973, as amended (ESA; 16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ). The applicant requests the ITP to take the federally listed scrub-jay (
                    <E T="03">Aphelocoma coerulescens</E>
                    ) and eastern indigo snake (
                    <E T="03">Drymarchon couperi</E>
                    ) incidental to the construction of a solar power plant (project) in Volusia County, Florida. We request public comment on the application, which includes the applicant's proposed habitat conservation plan (HCP) and the Service's preliminary determination that this HCP qualifies as “low-effect,” categorically excluded, under the National Environmental Policy Act (NEPA; 42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ). To make this determination, we used our environmental action statement and low-effect screening form, both of which are also available for public review.
                </P>
                <HD SOURCE="HD1">Project</HD>
                <P>The applicant requests a 10-year ITP to take the scrub-jay and eastern indigo snake incidental to the conversion of approximately 13.45 acres of occupied scrub-jay and 307.1 acres of occupied snake foraging and sheltering habitat for the construction of a solar power plant located on a 916.2-acre parcel, Parcel ID numbers 802900000050, 802800000020, 802000000030, 802000000070, 802000000050, 802000000060, 802100000010, 802100000080, 802100000012, 802000000020, 802000000010, and 801600000032, in Sections 16, 17, 20, 21, 28, 29, 32, and 33, Township 18 South, Range 30 East, Volusia County, Florida. The applicant proposes to mitigate for take of the scrub-jay through the contribution of $412,296.30 to the Florida Scrub-jay Conservation Fund administered by The Nature Conservancy and to mitigate for take of the eastern indigo snake through a contribution of $50,000.00 to the Wildlife Foundation of Florida's Eastern Indigo Snake Conservation Fund.</P>
                <HD SOURCE="HD1">Public Availability of Comments</HD>
                <P>Before including your address, phone number, email address, or other personal identifying information in your comment, be aware that your entire comment—including your personal identifying information—may be made available to the public. While you may request that we withhold your personal identifying information from public review, we cannot guarantee that we will be able to do so.</P>
                <HD SOURCE="HD1">Our Preliminary Determination</HD>
                <P>
                    The Service has made a preliminary determination that the applicant's project, including land clearing, infrastructure building, landscaping, and the proposed mitigation and minimization measures, would individually and cumulatively have a minor or negligible effect on the scrub-jay, the eastern indigo snake, and the environment. Therefore, we have preliminarily concluded that the ITP for this project would qualify for categorical exclusion and the HCP is low effect under our NEPA regulations at 43 CFR 46.205 and 46. 210. A low-effect HCP is one that would result in (1) minor or negligible effects on federally listed, proposed, and candidate species and their habitats; (2) minor or negligible effects on other environmental values or resources; and (3) impacts that, when considered together with the impacts of other past, present, and reasonably foreseeable similarly situated projects, 
                    <PRTPAGE P="20907"/>
                    would not over time result in significant cumulative effects to environmental values or resources.
                </P>
                <HD SOURCE="HD1">Next Steps</HD>
                <P>The Service will evaluate the application and the comments received to determine whether to issue the requested permit. We will also conduct an intra-Service consultation pursuant to section 7 of the ESA to evaluate the effects of the proposed take. After considering the above findings, we will determine whether the permit issuance criteria of section 10(a)(1)(B) of the ESA have been met. If met, the Service will issue ITP number TE 21556D-0 to Duke Energy Florida, LLC.</P>
                <HD SOURCE="HD1">Authority</HD>
                <P>The Service provides this notice under section 10(c) (16 U.S.C. 1539(c)) of the ESA and NEPA regulation 40 CFR 1506.6.</P>
                <SIG>
                    <NAME>Jay B. Herrington,</NAME>
                    <TITLE>Field Supervisor, Jacksonville Field Office, Southeast Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09710 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4333-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Fish and Wildlife Service</SUBAGY>
                <DEPDOC>[Docket No. FWS-R4-ES-2019-0028; FXES11130400000EA-123-FF04EF1000]</DEPDOC>
                <SUBJECT>Endangered and Threatened Wildlife; Receipt of Incidental Take Permit Application and Proposed Habitat Conservation Plan for the Sand Skink, Lake County, FL; Categorical Exclusion</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability; request for comment and information.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We, the Fish and Wildlife Service (Service), have received an application from the City of Groveland, Florida (applicant), to amend an incidental take permit under the Endangered Species Act. The 10-year ITP authorizes take of the federally listed sand skink incidental to the construction of a fire station and parking lot in Lake County, Florida. We request public comment on the application and on our preliminary determination that the proposed amendment of the habitat conservation plan (HCP) qualifies as “low-effect” under the National Environmental Policy Act. To make this determination, we used our environmental action statement and low-effect screening form, which are also available for review.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We must receive your written comments by June 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">Obtaining Documents:</E>
                         You may obtain copies of the documents online in Docket No. FWS-R4-ES-2019-0028 at 
                        <E T="03">http://www.regulations.gov.</E>
                    </P>
                    <P>
                        <E T="03">Submitting Comments:</E>
                         You may submit comments by one of the following methods:
                    </P>
                    <P>
                        • 
                        <E T="03">Online: http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments on Docket No. FWS-R4-ES-2019-0028.
                    </P>
                    <P>
                        • 
                        <E T="03">U.S. mail or hand-delivery:</E>
                         Public Comments Processing; Attn: Docket No. FWS-R4-ES-2019-0028; U.S. Fish and Wildlife Service, MS: BPHC; 5275 Leesburg Pike; Falls Church, VA 22041-3803.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Erin M. Gawera, by telephone at 904-731-3121, via the Federal Relay Service at 800-877-8339, or via email at 
                        <E T="03">erin_gawera@fws.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    We, the Fish and Wildlife Service (Service), have received an application from the City of Groveland, Florida (applicant), to amend an incidental take permit no. TE69161C-0 (ITP) under the Endangered Species Act of 1973, as amended, (ESA; 16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ). The 10-year ITP authorizes take of the federally listed sand skink (
                    <E T="03">Neoseps reynoldsi</E>
                    ) incidental to the construction of a fire station and parking lot in Lake County, Florida. We request public comment on the application, which includes the proposed habitat conservation plan (HCP), and on our preliminary determination that the proposed amendment of the HCP qualifies as “low-effect” under the National Environmental Policy Act (NEPA; 42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ). To make this determination, we used our environmental action statement and low-effect screening form, which are also available for review.
                </P>
                <P>We issued ITP TE69161C-0 to the applicant authorizing take of the sand skink incidental to the conversion of approximately 1.57 acres of occupied foraging and sheltering habitat for the construction of a fire station and parking lot. The station will be constructed within a 4.61-acre project site located on parcel Number 19-22-25-000100005200 in Section 19, Township 22 South, Range 25 East, Lake County, Florida.</P>
                <P>The applicant is requesting that the Service amend its ITP to authorize additional take of the sand skink through the conversion of another 0.41 acre (totaling approximately 1.98 acres) of occupied foraging and sheltering habitat incidental to the project. The project includes clearing, infrastructure building, and landscaping associated with construction. To mitigate for take under the ITP, the applicant agreed to purchase 3.14 mitigation credits in the Backbone Conservation Bank or another Service-approved sand skink bank. The applicant proposes to purchase an additional .82 credit (totaling 3.96 credits) in the conservation bank to mitigate for additional take of the species.</P>
                <HD SOURCE="HD1">Public Availability of Comments</HD>
                <P>
                    All comments, whether received electronically or via hard copy, will be posted on 
                    <E T="03">http://regulations.gov</E>
                     and become part of the decision record associated with this action. Before including your address, phone number, email address, or other personal identifying information in your comment, be aware that your entire comment—including your personal identifying information—may be made available to the public. While you can request that we withhold your personal identifying information, we cannot guarantee that we will be able to do so.
                </P>
                <HD SOURCE="HD1">Our Preliminary Determination</HD>
                <P>We have determined that the applicant's proposal, including the proposed mitigation and minimization measures, would have minor or negligible effects on the sand skinks and the environment. Therefore, we have preliminarily determined that amendment of the ITP would be “low effect” and qualify for categorical exclusion under NEPA. A low-effect HCP is one involving (1) minor or negligible effects on federally listed or candidate species and their habitats, and (2) minor or negligible effects on other environmental values or resources.</P>
                <HD SOURCE="HD1">Next Steps</HD>
                <P>The Service will evaluate the application to amend the ITP and consider all comments received to determine whether to amend the ITP application. We will also conduct an intra-Service consultation pursuant to section 7 of the ESA. After considering the above findings, we will determine whether the requirements of section 10(a)(1)(B) of the ESA and 50 CFR 13.23 have been met. If met, the Service will issue an amended ITP no. TE69161C-1 to the applicant for incidental take of the sand skink.</P>
                <HD SOURCE="HD1">Authority</HD>
                <P>
                    The Service provides this notice under section 10 of the ESA (16 U.S.C. 
                    <PRTPAGE P="20908"/>
                    1539) and NEPA regulation 40 CFR 1506.6.
                </P>
                <SIG>
                    <NAME>Jay B. Herrington,</NAME>
                    <TITLE>Field Supervisor, Jacksonville, FL Field Office, Southeast Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09711 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4333-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Fish and Wildlife Service</SUBAGY>
                <DEPDOC>[FWS-R4-ES-2019-0046; FXES11130400000EA-123-FF04EF1000]</DEPDOC>
                <SUBJECT>Receipt of Incidental Take Permit Application and Proposed Habitat Conservation Plan for the Sand Skink, Orange County, FL; Categorical Exclusion</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability; request for comment and information.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We, the Fish and Wildlife Service (Service), announce receipt of an application from Orange County Utilities (applicant) for an incidental take permit (ITP) under the Endangered Species Act. The applicant requests the ITP to take the federally listed sand skink incidental to construction in Orange County, Florida. We request public comment on the application, which includes the applicant's proposed habitat conservation plan (HCP) and the Service's preliminary determination that this HCP qualifies as “low-effect,” categorically excluded, under the National Environmental Policy Act. To make this determination, we used our environmental action statement and low-effect screening form, both of which are also available for public review.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We must receive your written comments on or before June 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P> </P>
                    <P>
                        <E T="03">Obtaining Documents:</E>
                         You may obtain copies of the documents online in Docket No. FWS-R4-ES-2019-0046 at 
                        <E T="03">http://www.regulations.gov.</E>
                    </P>
                    <P>
                        <E T="03">Submitting Comments:</E>
                         If you wish to submit comments on any of the documents, you may do so in writing by any of the following methods:
                    </P>
                    <P>
                        • 
                        <E T="03">Online: http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments on Docket No. FWS-R4-ES-2019-0046.
                    </P>
                    <P>
                        • 
                        <E T="03">U.S. mail or hand-delivery:</E>
                         Public Comments Processing, Attn: Docket No. FWS-R4-ES-2019-0046, U.S. Fish and Wildlife Service, MS: BPHC, 5275 Leesburg Pike, Falls Church, VA 22041-3803.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Erin M. Gawera, by telephone at (904) 731-3121 or via email at 
                        <E T="03">erin_gawera@fws.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    We, the Fish and Wildlife Service (Service), announce receipt of an application from Orange County Utilities (applicant) for an incidental take permit (ITP) under the Endangered Species Act of 1973, as amended (ESA; 16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ). The applicant requests the ITP to take the federally listed sand skink (
                    <E T="03">Neoseps reynoldsi</E>
                    ) incidental to the construction of a water reclamation facility (project) in Orange County, Florida. We request public comment on the application, which includes the applicant's proposed habitat conservation plan (HCP) and the Service's preliminary determination that this HCP qualifies as “low-effect,” categorically excluded, under the National Environmental Policy Act (NEPA; 42 U.S.C. 4231 
                    <E T="03">et seq.</E>
                    ). To make this determination, we used our environmental action statement and low-effect screening form, both of which are also available for public review.
                </P>
                <HD SOURCE="HD1">Project</HD>
                <P>Orange County Utilities requests a 20-year ITP to take sand skinks incidental to the conversion of approximately 8.84 acres of occupied skink foraging and sheltering habitat for the construction of a water reclamation facility located on a 49.18-acre parcel in Sections 16 and 17, Township 23 South, Range 27 East, Orange County, Florida. The applicant proposes to mitigate for take of the skinks by purchasing 17.68 credits in the Lake Wales Ridge Conservation Bank and/or another Service-approved sand skink bank. The Service would require the applicant to purchase the credits prior to engaging in activities associated with the project on the parcel.</P>
                <HD SOURCE="HD1">Public Availability of Comments</HD>
                <P>Before including your address, phone number, email address, or other personal identifying information in your comment, be aware that your entire comment—including your personal identifying information—may be made available to the public. While you may request that we withhold your personal identifying information, we cannot guarantee that we will be able to do so.</P>
                <HD SOURCE="HD1">Our Preliminary Determination</HD>
                <P>The Service has made a preliminary determination that the applicant's project, including land clearing, infrastructure building, landscaping, and the proposed mitigation measures, would individually and cumulatively have a minor or negligible effect on the skinks and the environment. Therefore, we have preliminarily concluded that the ITP for this project would qualify for categorical exclusion and the HCP is low effect under our NEPA regulations at 43 CFR 46.205 and 46.210. A low-effect HCP is one that would result in (1) minor or negligible effects on federally listed, proposed, and candidate species and their habitats; (2) minor or negligible effects on other environmental values or resources; and, (3) impacts that, when considered together with the impacts of other past, present, and reasonably foreseeable similarly situated projects, would not over time result in significant cumulative effects to environmental values or resources.</P>
                <HD SOURCE="HD1">Next Steps</HD>
                <P>The Service will evaluate the application and the comments received to determine whether to issue the requested permit. We will also conduct an intra-Service consultation pursuant to section 7 of the ESA to evaluate the effects of the proposed take. After considering the above findings, we will determine whether the permit issuance criteria of section 10(a)(1)(B) of the ESA have been met. If met, the Service will issue ITP number TE 21560D-0 to Orange County Utilities.</P>
                <HD SOURCE="HD1">Authority</HD>
                <P>The Service provides this notice under section 10(c) (16 U.S.C. 1539(c)) of the ESA and NEPA regulation 40 CFR 1506.6.</P>
                <SIG>
                    <NAME>Jay B. Herrington,</NAME>
                    <TITLE>Field Supervisor, Jacksonville Field Office, Southeast Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09712 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4333-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—American Society of Mechanical Engineers</SUBJECT>
                <P>
                    Notice is hereby given that, on April 22, 2019, pursuant to Section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), the American Society of Mechanical Engineers (“ASME”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing additions or changes to its standards development activities. The notifications were filed 
                    <PRTPAGE P="20909"/>
                    for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, since September 4, 2018, ASME has published two new standards, added one consensus committee charter, and initiated five new standards activities within the general nature and scope of ASME's standards development activities, as specified in its original notification. More detail regarding these changes can be found at 
                    <E T="03">www.asme.org.</E>
                </P>
                <P>
                    On September 15, 2004, ASME filed its original notification pursuant to Section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to Section 6(b) of the Act on October 13, 2004 (69 FR 60895).
                </P>
                <P>
                    The last notification with the Attorney General was filed on January 28, 2019. A notice was filed in the 
                    <E T="04">Federal Register</E>
                     on February 12, 2019 (84 FR 3492).
                </P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Chief, Premerger and Division Statistics Unit, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09702 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-11-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—DirectTrust Standards</SUBJECT>
                <P>
                    Notice is hereby given that, on April 22, 2019, pursuant to Section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), DirectTrust Standards (“DirectTrust”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing (1) the name and principal place of business of the standards development organization and (2) the nature and scope of its standards development activities. The notifications were filed for the purpose of invoking the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances.
                </P>
                <P>Pursuant to Section 6(b) of the Act, the name and principal place of business of the standards development organization is: DirectTrust Standards, Washington, DC. The nature and scope of DirectTrust's standards development activities are: To develop and maintain standards that enable and promote healthcare interoperability using Direct exchange and trust frameworks. DirectTrust received ANSI Accreditation as to develop American National Standards in compliance with the DirectTrust Standards Operating Procedures.</P>
                <SIG>
                    <NAME>Suzanne Morris,</NAME>
                    <TITLE>Chief, Premerger and Division Statistics Unit, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09698 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4410-11-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Federal Bureau of Investigation</SUBAGY>
                <DEPDOC>[OMB Number 1110-0004]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Proposed eCollection; eComments Requested; Revision of a Currently Approved Collection; Number of Full-Time Law Enforcement Employees as of October 31</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Bureau of Investigation, Department of Justice.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>30-Day notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Justice (DOJ), Federal Bureau of Investigation (FBI), Criminal Justice Information Services Division (CJIS), will be submitting the following information collection request to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act of 1995.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments are encouraged and will be accepted for an additional 30 days until June 12, 2019.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Written comments and/or suggestions regarding the items contained in this notice, especially the estimated public burden and associated response time, should be directed to Ms. Amy Blasher, Unit Chief, Federal Bureau of Investigation, CJIS Division, Module E-3, 1000 Custer Hollow Road, Clarksburg, West Virginia 26306; facsimile (304) 625-3566. Written comments and/or suggestions can also be sent to the Office of Management and Budget, Office of Information and Regulatory Affairs, Attention Department of Justice Desk Officer, Washington, DC 20503 or sent to 
                        <E T="03">OIRA_submissions@omb.eop.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Written comments and suggestions from the public and affected agencies concerning the proposed collection of information are encouraged. Your comments should address one or more of the following four points:</P>
                <FP SOURCE="FP-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;</FP>
                <FP SOURCE="FP-1">—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;</FP>
                <FP SOURCE="FP-1">—Enhance the quality, utility, and clarity of the information to be collected; and</FP>
                <FP SOURCE="FP-1">
                    —Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </FP>
                <HD SOURCE="HD1">Overview of This Information Collection</HD>
                <P>
                    (1) 
                    <E T="03">Type of Information Collection:</E>
                     Revision of a currently approved collection.
                </P>
                <P>
                    (2) 
                    <E T="03">Title of the Form/Collection:</E>
                     Number of Full-time Law Enforcement Employees as of October 31.
                </P>
                <P>
                    (3) 
                    <E T="03">Agency form number, if any, and the applicable component of the Department sponsoring the collection:</E>
                     Agency form number: 1-711. Sponsoring component: Department of Justice, Federal Bureau of Investigation, Criminal Justice Information Services Division.
                </P>
                <P>
                    (4) 
                    <E T="03">Affected public who will be asked or required to respond, as well as a brief abstract:</E>
                     Primary: City, county, state, federal, and tribal law enforcement agencies. Abstract: Under Title 28, U.S. Code, Section 534, Acquisition, Preservation, and Exchange of Identification Records; and Appointment of Officials, 1930, this collection requests the number of full and part-time law enforcement employees by race/ethnicity for both officers and civilians, from city, county, state, tribal, and federal law enforcement agencies in order for the FBI UCR Program to serve as the national clearinghouse for the collection and dissemination of police employee data and to publish these statistics in Crime in the United States.
                </P>
                <P>
                    (5) 
                    <E T="03">An estimate of the total number of respondents and the amount of time estimated for an average respondent to respond/reply:</E>
                     There are approximately 18,482 law enforcement agency respondents that submit once a year for a total of 18,482 responses with an estimated response time of 8 minutes per response.
                </P>
                <P>
                    (6) 
                    <E T="03">
                        An estimate of the total public burden (in hours) associated with the 
                        <PRTPAGE P="20910"/>
                        collection:
                    </E>
                     There are an estimated 2,464 hours, annual burden, associated with this information collection.
                </P>
                <FP>If additional information is required contact: Melody Braswell, Department Clearance Officer, United States Department of Justice, Justice Management Division, Policy and Planning Staff, Two Constitution Square, 145 N Street NE, Suite 3E.405B, Washington, DC 20530.</FP>
                <SIG>
                    <DATED>Dated: May 8, 2019.</DATED>
                    <NAME>Melody Braswell,</NAME>
                    <TITLE>Department Clearance Officer, PRA, U.S. Department of Justice.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09769 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBJECT>Notice of Lodging of Proposed Fourth Amended Consent Decree Under the Comprehensive Environmental Response, Compensation, and Liability Act</SUBJECT>
                <P>
                    On May 7, 2019, the Department of Justice lodged a proposed Fourth Amended Consent Decree with the United States District Court for the Western District of Washington in the lawsuit entitled 
                    <E T="03">United States</E>
                     v. 
                    <E T="03">Point Ruston, LLC,</E>
                     Case No. 91-CV-05528-RJB.
                </P>
                <P>This amended Consent Decree extends various remedial action deadlines and forgives certain payments due under the Third Amended Consent Decree in exchange for the disposition of contaminated soil from an adjacent parcel. Under the terms of this amendment: (1) Point Ruston will temporarily manage and dispose of the contaminated soil from the Metropolitan Parks Waterfront Phase I parcel pursuant to a Soil Management Plan; (2) Point Ruston's obligation to pay the remaining amount due under Paragraph 69 of the Third Amended Consent Decree is extinguished; (3) certain remedial action deadlines set forth in the Construction Management Plans are extended for six months; and (4) a legal citation in the “Access and Institutional Controls” section of the Third Amended Consent Decree is updated to reflect a change in Washington state law.</P>
                <P>
                    The publication of this notice opens a period for public comment on the Fourth Amended Consent Decree. Comments should be addressed to the Assistant Attorney General, Environment and Natural Resources Division, and should refer to 
                    <E T="03">United States</E>
                     v. 
                    <E T="03">Point Ruston, LLC,</E>
                     Case No. 91-CV-05528-RJB, D.J. Ref. No. 90-11-2-698/2. All comments must be submitted no later than thirty (30) days after the publication date of this notice. Comments may be submitted either by email or by mail:
                </P>
                <GPOTABLE COLS="02" OPTS="L2,tp0,i1" CDEF="xs50,r50">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1" O="L">
                            <E T="03">To submit comments:</E>
                        </CHED>
                        <CHED H="1" O="L">
                            <E T="03">Send them to:</E>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">By e-mail</ENT>
                        <ENT>
                            <E T="03">pubcomment-ees.enrd@usdoj.gov</E>
                            .
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">By mail</ENT>
                        <ENT>Assistant Attorney General, U.S. DOJ—ENRD, P.O. Box 7611, Washington, D.C. 20044-7611.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    During the public comment period, the Fourth Amended Consent Decree may be examined and downloaded at this Justice Department website: 
                    <E T="03">https://www.justice.gov/enrd/consent-decrees</E>
                    . We will provide a paper copy of the Fourth Amended Consent Decree upon written request and payment of reproduction costs. Please mail your request and payment to: Consent Decree Library, U.S. DOJ—ENRD, P.O. Box 7611, Washington, DC 20044-7611.
                </P>
                <P>Please enclose a check or money order for $2.25 (25 cents per page reproduction cost) payable to the United States Treasury.</P>
                <SIG>
                    <NAME>Susan M. Akers,</NAME>
                    <TITLE>Assistant Section Chief, Environmental Enforcement Section, Environment and Natural Resources Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09771 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">LEGAL SERVICES CORPORATION</AGENCY>
                <SUBJECT>Sunshine Act Meetings</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">DATE AND TIME:</HD>
                    <P>The Legal Services Corporation's Board of Directors will meet telephonically on Tuesday, May 21, 2019. The meeting will commence at 3:00 p.m., EDT, and will continue until the conclusion of the Board's agenda.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE:</HD>
                    <P>John N. Erlenborn Conference Room, Legal Services Corporation Headquarters, 3333 K Street NW, Washington, DC 20007.</P>
                    <P>
                        <E T="03">Public Observation:</E>
                         Members of the public who are unable to attend in person but wish to listen to the public proceedings may do so by following the telephone call-in directions provided below.
                    </P>
                    <P>
                        <E T="03">Call-In Directions for Open Sessions:</E>
                    </P>
                    <P>• Call toll-free number: 1-866-451-4981;</P>
                    <P>• When prompted, enter the following numeric pass code: 5907707348</P>
                    <P>• When connected to the call, please immediately “MUTE” your telephone.</P>
                    <P>Members of the public are asked to keep their telephones muted to eliminate background noises. To avoid disrupting the meeting, please refrain from placing the call on hold if doing so will trigger recorded music or other sound. From time to time, the Chair may solicit comments from the public.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS:</HD>
                    <P>Open.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>
                    <P/>
                </PREAMHD>
                <HD SOURCE="HD1">Board of Directors</HD>
                <FP SOURCE="FP-2">1. Approval of agenda</FP>
                <FP SOURCE="FP-2">2. Consider and act on the Board of Directors' transmittal to accompany the Inspector General's Semiannual Report to Congress for the period of October 1, 2018 through March 31, 2019</FP>
                <FP SOURCE="FP-2">3. Public comment</FP>
                <FP SOURCE="FP-2">4. Consider and act on other business</FP>
                <FP SOURCE="FP-2">5. Consider and act on adjournment of meeting</FP>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION:</HD>
                    <P>
                        Katherine Ward, Executive Assistant to the Vice President &amp; General Counsel, at (202) 295-1500. Questions may be sent by electronic mail to 
                        <E T="03">FR_NOTICE_QUESTIONS@lsc.gov.</E>
                    </P>
                    <P>
                        <E T="03">Accessibility:</E>
                         LSC complies with the Americans with Disabilities Act and Section 504 of the 1973 Rehabilitation Act. Upon request, meeting notices and materials will be made available in alternative formats to accommodate individuals with disabilities. Individuals needing other accommodations due to disability in order to attend the meeting in person or telephonically should contact Katherine Ward, at (202) 295-1500 or 
                        <E T="03">FR_NOTICE_QUESTIONS@lsc.gov,</E>
                         at least 2 business days in advance of the meeting. If a request is made without advance notice, LSC will make every effort to accommodate the request but cannot guarantee that all requests can be fulfilled.
                    </P>
                </PREAMHD>
                <SIG>
                    <DATED>Dated: May 9, 2019.</DATED>
                    <NAME>Katherine Ward,</NAME>
                    <TITLE>Executive Assistant to the Vice President for Legal Affairs and General Counsel.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09918 Filed 5-9-19; 4:15 pm]</FRDOC>
            <BILCOD> BILLING CODE 7050-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL AERONAUTICS AND SPACE ADMINISTRATION</AGENCY>
                <DEPDOC>[Notice (19-029)]</DEPDOC>
                <SUBJECT>National Environmental Policy Act; Wallops Flight Facility; Site-Wide</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Aeronautics and Space Administration (NASA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>
                        Notice of availability of the Final Site-wide Programmatic Environmental Impact Statement (PEIS) for improvement of infrastructure and 
                        <PRTPAGE P="20911"/>
                        services at Wallops Flight Facility (WFF), Accomack County, Virginia.
                    </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the National Environmental Policy Act (NEPA), as amended, the Council on Environmental Quality Regulations for Implementing the Procedural Provisions of NEPA, and NASA's NEPA policy and procedures, NASA has prepared a Final PEIS for the improvement of infrastructure and services at WFF. The Federal Aviation Administration's Air Traffic Organization and the Office of Commercial Space Transportation; the Federal Highway Administration; the National Oceanic and Atmospheric Administration's (NOAA) National Environmental Satellite, Data, and Information Service; the U.S. Army Corps of Engineers; the U.S. Coast Guard; the U.S. Fish and Wildlife Service; the U.S. Navy, Naval Sea Systems Command; the U.S. Navy, Naval Air Systems Command; U.S. Navy, U.S. Fleet Forces Command; the U.S. Environmental Protection Agency (EPA); the U.S. Air Force Space Command/Space and Missile Systems Center; and Virginia Commercial Space Flight Authority have served as Cooperating Agencies in preparing the Final PEIS as they either have permanent facilities or missions at WFF or possess regulatory authority or specialized expertise pertaining to the Proposed Action.</P>
                    <P>The purpose of this notice is to apprise interested agencies, organizations, tribal governments, and individuals of the availability of the Final PEIS.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        NASA will issue a Record of Decision (ROD) based on the Final PEIS no sooner than 30 days from the date of publication in the 
                        <E T="04">Federal Register</E>
                         of the U.S. Environmental Protection Agency's Notice of Availability of the Final PEIS.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The Final PEIS may be viewed at the following locations:</P>
                    <FP SOURCE="FP-1">(a) Chincoteague Island Library, Chincoteague, Virginia, 23336 (757) 336-3460</FP>
                    <FP SOURCE="FP-1">(b) NASA Wallops Visitor Center, Wallops Island, Virginia, 23337 (757) 824-1344</FP>
                    <FP SOURCE="FP-1">(c) Eastern Shore Public Library, Accomac, Virginia, 23301 (757) 787-3400</FP>
                    <FP SOURCE="FP-1">(d) Northampton Free Library, Nassawadox, Virginia, 23413 (757) 414-0010</FP>
                    <P>
                        A limited number of hard copies of the Final PEIS are available, on a first request basis, by contacting the NASA point of contact listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        . The Final PEIS is available on the internet in Adobe® portable document format at 
                        <E T="03">https://code200-external.gsfc.nasa.gov/250-wff/site-wide_eis</E>
                        . NASA's ROD will be made available, once issued, on the same website as above and by request to the contact provided above.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Shari Miller, Site-wide PEIS, NASA Goddard Space Flight Center's Wallops Flight Facility, Mailstop: 250.W, Wallops Island, Virginia 23337; telephone (757) 824-2327; email: 
                        <E T="03">Shari.A.Miller@nasa.gov</E>
                        . A toll-free telephone number, (800) 521-3415, is also available for persons outside the local calling area. When using the toll-free number, please follow the menu options and enter the “pound sign (#)” followed by extension number “2327.” Additional information about NASA's WFF may be found on the internet at 
                        <E T="03">http://www.nasa.gov/centers/wallops/home/index.html</E>
                        . Information regarding the NEPA process for this proposal and supporting documents (as available) are located at 
                        <E T="03">https://code200-external.gsfc .nasa.gov/250-wff/site-wide_eis</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>WFF is a NASA Goddard Space Flight Center field installation located in northern Accomack County on the Eastern Shore of Virginia. The facility consists of three distinct landmasses—the Main Base, Wallops Mainland, and Wallops Island. WFF operates the oldest active launch range in the continental U.S. and the only range completely under NASA management. For over 70 years, WFF has flown thousands of research vehicles in the quest for information on the characteristics of airplanes, rockets, and spacecraft, and to increase the knowledge of the Earth's upper atmosphere and the near space environment. The flight programs and projects conducted by WFF range from small sounding and suborbital rockets, unmanned scientific balloons, unmanned aerial systems, manned aircraft, and orbital spacecraft to next-generation launch vehicles and small- and medium-classed launch vehicles.</P>
                <P>In keeping with the principles, goals, and guidelines of the 2010 U.S. National Space Policy, as updated by the 2013 U.S. National Space Transportation Policy and the 2017 Presidential Memorandum on Reinvigorating America's Human Space Exploration Program, NASA is proposing to improve its service capability at WFF to support a growing mission base in the areas of civil, defense, and academic aerospace. One guiding principle of the National Space Policy is for Federal agencies to facilitate the commercial space industry. The Mid-Atlantic Regional Spaceport, a commercial launch site on Wallops Island, is a real-world example of WFF's commitment to making commercial access to space a reality. Accordingly, it is expected that a commercial presence at WFF will continue to expand in the coming years.</P>
                <P>
                    The National Space Policy also instructs Federal agencies to improve their partnerships through cooperation, collaboration, information sharing, and/or alignment of common pursuits with each other. WFF supports aeronautical research, and science, technology, engineering, and math (STEM) education programs by providing other NASA centers and other U.S. government agencies access to resources such as special use (
                    <E T="03">i.e.,</E>
                     controlled/restricted) airspace, runways, and launch pads. WFF regularly facilitates a wide array of U.S. Department of Defense (DoD) research, development, testing, and evaluation; training missions, including target and missile launches; and aircraft pilot training. Similar to its forecasted commercial growth at WFF, NASA also expects an increase in DoD presence at WFF in the foreseeable future.
                </P>
                <P>Finally, the National Space Policy directs NASA to fulfill various key civil space roles regarding space science, exploration, and discovery; a number of which have been priorities at WFF for decades. NASA's need to ensure continued growth while preserving the ability to safely conduct its historical baseline of services is a key component of facilitating future projects and new missions at WFF.</P>
                <HD SOURCE="HD1">Related Environmental Documents</HD>
                <P>
                    In January 2005, NASA issued a Final Site-Wide Environmental Assessment (EA) and Finding of No Significant Impact (FONSI) for its operations and institutional support at WFF. Since then, substantial growth has occurred and NASA, and its Cooperating Agencies, have prepared multiple supplemental NEPA documents including the 2008 EA/FONSI for the Wallops Research Park; the 2009 EA/FONSI for the Expansion of the Wallops Flight Facility Launch Range; the 2010 PEIS/Record of Decision for the Shoreline Restoration and Infrastructure Protection Program; the 2011 EA/FONSI for the Alternative Energy Project; the 2011 EA/FONSI for the Main Entrance Reconfiguration; the 2011 NOAA EA/FONSI for Electrical and Operational Upgrade, Space Addition, and Geostationary Operational Environmental Satellite Installation; the 2012 EA/FONSI for the North Wallops Island Unmanned Aerial Systems Airstrip Project; the U.S. Fleet Force 
                    <PRTPAGE P="20912"/>
                    Command's 2013 EA/FONSI for E-2/C-2 Field Carrier Landing Practice at WFF; the Navy's 2014 EA/FONSI for the Testing of Hypervelocity Projectiles and an Electromagnetic Railgun; the 2015 Supplemental EA/FONSI for Antares 200 Configuration Expendable Launch Vehicle at WFF; the 2016 EA/FONSI for Establishment of Restricted Area Airspace R-6604 C/D/E; the Navy's 2017 EA/FONSI for and the Installation and Operation of Air and Missile Defense Radar AN/SPY-6; the 2017 U.S. Air Force's EA/FONSI for the Instrumentation Tower on Wallops Island; and the Navy's 2018 EIS/Overseas EIS/ROD for Atlantic Fleet Training and Testing.
                </P>
                <HD SOURCE="HD1">Need for Preparing a PEIS</HD>
                <P>Since the 2005 WFF Site-wide EA, NASA, NOAA, and the Navy have updated their Master Plans for Wallops Island; which propose new facilities and numerous infrastructure improvements to enable a growing mission base. Additionally, during reviews of the post-2005 Site-wide EA NEPA documents, resource agencies have expressed concerns regarding cumulative environmental effects and a desire for NASA to consider all reasonably foreseeable future projects at WFF in a consolidated NEPA document. NASA determined that preparing a single Site-wide PEIS not only would assist in its decision-making process for future mission growth at WFF but also address concerns regarding cumulative environmental effects. Therefore, the Site-wide PEIS considers all reasonably foreseeable future actions at WFF; those proposed by NASA along with those proposed by its tenants and partners.</P>
                <HD SOURCE="HD1">Cooperating Agency Actions</HD>
                <P>The Site-wide PEIS will serve as a decision-making tool not only for NASA but also for its Cooperating Agencies. Given the potential for their undertaking actions related to NASA's actions, each of these agencies has been involved closely in NASA's NEPA process.</P>
                <HD SOURCE="HD1">Alternatives</HD>
                <P>The PEIS evaluates the environmental consequences of a range of reasonable alternatives that meet NASA's need to ensure continued growth at WFF while also preserving the ability to safely conduct its historical baseline of services. The planning horizon for actions in the PEIS is 20 years.</P>
                <P>
                    The PEIS considers a Proposed Action and a No Action alternative. The Proposed Action, NASA's preferred alternative, would support a number of facility projects ranging from new construction, demolition, and renovation; the replacement of the Wallops causeway bridge; maintenance dredging between the boat docks at the Main Base and Wallops Island; development of a deep-water port and operations area on North Wallops Island; construction and operation of an additional medium to heavy class launch site; the introduction of new NASA and DoD programs at WFF; the expansion of the launch vehicle services with liquid-fueled intermediate class and solid fueled heavy class launch vehicles; and the consideration of commercial human spaceflight missions and the return of launch vehicles to the launch site. Under the No Action Alternative, WFF and its partners would continue the existing operations and programs previously discussed in the 2005 Site-Wide EA and the subsequent NEPA documents identified under 
                    <E T="03">Related Environmental Documents</E>
                    .
                </P>
                <HD SOURCE="HD1">Review of the Draft PEIS</HD>
                <P>
                    NASA sought public comments on the analysis and findings presented in the Draft Site-wide PEIS during the 45-day public comment period which ran from May 4 through June 18, 2018. An NOA was placed in the 
                    <E T="04">Federal Register</E>
                     on May 4, 2018, and public notices were published in the 
                    <E T="03">Eastern Shore News, Chincoteague Beacon, Eastern Shore Post,</E>
                     and 
                    <E T="03">The Daily Times</E>
                    .
                </P>
                <P>A public meeting was held at the NASA Wallops Flight Facility Visitor Center on May 23, 2018, from 6:00 to 8:00 p.m. A total of nine comment letters were received. Appendix I of the Final PEIS provides the public notices, meeting materials, and comment letters received during the public review period.</P>
                <P>
                    In accordance with 15 CFR 930.2, the Virginia Department of Environmental Quality (VDEQ) invited the public to participate in the review of the Federal Consistency Determination submitted for NASA's proposed action. A public notice was published in the VDEQ's Office of Environmental Impact Review Program Newsletter and on the VDEQ website from May 11 through June 21, 2018. No public comments were received in response to the notice. In accordance with 40 CFR 1506.9, EPA published an NOA of the Draft PEIS in the 
                    <E T="04">Federal Register</E>
                     on May 4, 2018. No public comments were received in response to the notice.
                </P>
                <P>In summary, notice of the availability of the Final PEIS is hereby given.</P>
                <SIG>
                    <NAME>Cheryl E. Parker,</NAME>
                    <TITLE>Federal Liaison Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09763 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7510-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL SCIENCE FOUNDATION</AGENCY>
                <SUBJECT>Agency Information Collection Activities: Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Science Foundation.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Submission for OMB review; comment request.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The National Science Foundation (NSF) has submitted the following information collection requirement to OMB for review and clearance under the Paperwork Reduction Act of 1995. This is the second notice for public comment; the first was published in the 
                        <E T="04">Federal Register</E>
                        , and no comments were received. NSF is forwarding the proposed submission to the Office of Management and Budget (OMB) for clearance simultaneously with the publication of this second notice. The full submission may be found at: 
                        <E T="03">http://www.reginfo.gov/public/do/PRAMain.</E>
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments regarding this information collection are best assured of having their full effect if received by June 12, 2019.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Office of Information and Regulatory Affairs of OMB, Attention: Desk Officer for National Science Foundation, 725 17th Street NW, Room 10235, Washington, DC 20503, and Suzanne H. Plimpton, Reports Clearance Officer, National Science Foundation, 2415 Eisenhower Avenue, Alexandria, VA 22314, or send email to 
                        <E T="03">splimpto@nsf.gov.</E>
                         Individuals who use a telecommunications device for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 1-800-877-8339, which is accessible 24 hours a day, 7 days a week, 365 days a year (including federal holidays).
                    </P>
                    <P>Copies of the submission(s) may be obtained by calling 703-292-7556.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>NSF 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>
                <P>
                    Comments regarding (a) 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; (b) the accuracy of the agency's estimate of burden including the validity of the methodology and assumptions used; (c) ways to enhance the quality, utility and clarity of the 
                    <PRTPAGE P="20913"/>
                    information to be collected; (d) 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 should be addressed to the points of contact in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section.
                </P>
                <P>
                    <E T="03">Title of Collection:</E>
                     Antarctic emergency response plan and environmental protection information.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     3145-0180.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The NSF, pursuant to the Antarctic Conservation Act of 1978 (16 U.S.C. 2401 
                    <E T="03">et seq.</E>
                    ) (“ACA”) regulates certain non-governmental activities in Antarctica. The ACA was amended in 1996 by the Antarctic Science, Tourism, and Conservation Act. On September 7, 2001, NSF published a final rule in the 
                    <E T="04">Federal Register</E>
                     (66 FR 46739) implementing certain of these statutory amendments. The rule requires non-governmental Antarctic expeditions using non-U.S. flagged vessels to ensure that the vessel owner has an emergency response plan. The rule also requires persons organizing a non-governmental expedition to provide expedition members with information on their environmental protection obligations under the Antarctic Conservation Act.
                </P>
                <P>
                    <E T="03">Expected Respondents:</E>
                     Respondents may include non-profit organizations and small and large businesses. The majority of respondents are anticipated to be U.S. tour operators, currently estimated to number fifteen.
                </P>
                <P>
                    <E T="03">Burden on the Public:</E>
                     The Foundation estimates that a one-time paperwork and recordkeeping burden of 40 hours or less, at a cost of $500 to $1,400 per respondent, will result from the emergency response plan requirement contained in the rule. Presently, all respondents have been providing expedition members with a copy of the Guidance for Visitors to the Antarctic (prepared and adopted at the Eighteenth Antarctic Treaty Consultative Meeting as Recommendation XVIII-1). Because this Antarctic Treaty System document satisfies the environmental protection information requirements of the rule, no additional burden shall result from the environmental information requirements in the proposed rule.
                </P>
                <SIG>
                    <DATED>Dated: May 7, 2019.</DATED>
                    <NAME>Suzanne H. Plimpton,</NAME>
                    <TITLE>Reports Clearance Officer, National Science Foundation.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09741 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 7555-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">POSTAL REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket Nos. CP2018-242; CP2019-148]</DEPDOC>
                <SUBJECT>New Postal Product</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>
                         May 15, 2019.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments electronically via the Commission's Filing Online system at 
                        <E T="03">http://www.prc.gov.</E>
                         Those who cannot submit comments electronically should contact the person identified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section by telephone for advice on filing alternatives.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David A. Trissell, General Counsel, at 202-789-6820.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Introduction</FP>
                    <FP SOURCE="FP-2">II. Docketed Proceeding(s)</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>The Commission gives notice that the Postal Service filed request(s) for the Commission to consider matters related to negotiated service agreement(s). The request(s) may propose the addition or removal of a negotiated service agreement from the market dominant or the competitive product list, or the modification of an existing product currently appearing on the market dominant or the competitive product list.</P>
                <P>Section II identifies the docket number(s) associated with each Postal Service request, the title of each Postal Service request, the request's acceptance date, and the authority cited by the Postal Service for each request. For each request, the Commission appoints an officer of the Commission to represent the interests of the general public in the proceeding, pursuant to 39 U.S.C. 505 (Public Representative). Section II also establishes comment deadline(s) pertaining to each request.</P>
                <P>
                    The public portions of the Postal Service's request(s) can be accessed via the Commission's website (
                    <E T="03">http://www.prc.gov</E>
                    ). Non-public portions of the Postal Service's request(s), if any, can be accessed through compliance with the requirements of 39 CFR 3007.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 3010, and 39 CFR part 3020, 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 3015, and 39 CFR part 3020, 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>
                     CP2018-242; 
                    <E T="03">Filing Title:</E>
                     USPS Notice of Amendment to Priority Mail Contract 444, Filed Under Seal; 
                    <E T="03">Filing Acceptance Date:</E>
                     May 7, 2019; 
                    <E T="03">Filing Authority:</E>
                     39 U.S.C. 3642, 39 CFR 3020.30 
                    <E T="03">et seq.,</E>
                     and 39 CFR 3015.5; 
                    <E T="03">Public Representative:</E>
                     Christopher C. Mohr; 
                    <E T="03">Comments Due:</E>
                     May 15, 2019.
                </P>
                <P>
                    2. 
                    <E T="03">Docket No(s).:</E>
                     CP2019-148; 
                    <E T="03">Filing Title:</E>
                     Notice of United States Postal Service of Filing a Functionally Equivalent Global Reseller Expedited Package 2 Negotiated Service Agreement and Application for Non-Public Treatment of Materials Filed Under Seal; 
                    <E T="03">Filing Acceptance Date:</E>
                     May 7, 2019; 
                    <E T="03">Filing Authority:</E>
                     39 CFR 3015.5; 
                    <E T="03">Public Representative:</E>
                     Christopher C. Mohr
                    <E T="03">; Comments Due:</E>
                     May 15, 2019.
                </P>
                <P>
                    This Notice will be published in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <NAME>Stacy L Ruble,  </NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09816 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 7710-FW-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">RAILROAD RETIREMENT BOARD</AGENCY>
                <SUBJECT>Sunshine Act Meetings</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND DATE:</HD>
                    <P>10:00 a.m., May 22, 2019.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE:</HD>
                    <P>8th Floor Board Conference Room, 844 North Rush Street, Chicago, Illinois, 60611.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS:</HD>
                    <P>Parts of this meeting will be open to the public. The rest of this the meeting will be closed to the public.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>
                    <P/>
                </PREAMHD>
                <PREAMHD>
                    <PRTPAGE P="20914"/>
                    <HD SOURCE="HED">PORTIONS OPEN TO THE PUBLIC:</HD>
                    <P/>
                    <P>(1) Follow up on Board meetings of May 14-15 in Washington DC.</P>
                    <P>(2) Status update from appropriate staff on information gathering activities relating to the SCOTUS Wisconsin Central decision.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PORTIONS CLOSED TO THE PUBLIC:</HD>
                    <P/>
                    <P>(1) Status update on internal personnel matter.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION:</HD>
                    <P>Stephanie Hillyard, Secretary to the Board, Phone No. 312-751-4920.</P>
                </PREAMHD>
                <SIG>
                    <DATED>Dated: May 9, 2019.</DATED>
                    <NAME>Stephanie Hillyard,</NAME>
                    <TITLE>Secretary to the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09950 Filed 5-9-19; 4:15 pm]</FRDOC>
            <BILCOD> BILLING CODE 7905-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <SUBJECT>Proposed Collection; Comment Request</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>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        <E T="03">Extension:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Rule 12d1-3, SEC File No. 270-116, OMB Control No. 3235-0109</FP>
                </EXTRACT>
                <P>
                    Notice is hereby given that, pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), the Securities and Exchange Commission (“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>Exchange Act Rule 12d1-3 (17 CFR 240.12d1-3) requires a certification that a security has been approved by an exchange for listing and registration pursuant to Section 12(d) of the Securities Exchange Act of 1934 (15 U.S.C. 78l(d)) to be filed with the Commission. The information required under Rule 12d1-3 must be filed with the Commission and is publicly available. We estimate that it takes approximately one-half hour per response to provide the information required under Rule 12d1-3 and that the information is filed by approximately 688 respondents for a total annual reporting burden of 344 hours (0.5 hours per response × 688 responses).</P>
                <P>
                    <E T="03">Written comments are invited on:</E>
                     (a) Whether this proposed collection of information is necessary for the performance of the functions of the agency, including whether the information will have practical utility; (b) the accuracy of the agency's estimate of the burden imposed by 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 in writing within 60 days of this publication.
                </P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid control number.</P>
                <P>
                    Please direct your written comment to Charles Riddle, Acting Director/Chief Information Officer, Securities and Exchange Commission, c/o Candace Kenner, 100 F Street NE, Washington, DC 20549 or send an email to: 
                    <E T="03">PRA_Mailbox@sec.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: May 8, 2019.</DATED>
                    <NAME>Eduardo A. Aleman,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09799 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Investment Company Act Release No. 33468; 812-14894]</DEPDOC>
                <SUBJECT>ALPS Variable Investment Trust, et al.</SUBJECT>
                <DATE>May 7, 2019.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Securities and Exchange Commission (“Commission”).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <P>Notice of an application under section 6(c) of the Investment Company Act of 1940 (“Act”) for an exemption from section 15(a) of the Act and rule 18f-2 under the Act, as well as from certain disclosure requirements in rule 20a-1 under the Act, Item 19(a)(3) of Form N-1A, Items 22(c)(1)(ii), 22(c)(1)(iii), 22(c)(8) and 22(c)(9) of Schedule 14A under the Securities Exchange Act of 1934, and sections 6-07(2)(a), (b), and (c) of Regulation S-X (“Disclosure Requirements”). The requested exemption would permit an investment adviser to hire and replace certain sub-advisers without shareholder approval and grant relief from the Disclosure Requirements as they relate to fees paid to the sub-advisers.</P>
                <PREAMHD>
                    <HD SOURCE="HED">Applicants:</HD>
                    <P> ALPS Variable Investment Trust, ALPS ETF Trust, and Financial Investors Trust (each a “Trust” and collectively, the “Trusts”), each a Delaware statutory trust registered under the Act as an open-end management investment company that offers or will offer one or more series (each a “Series,” and collectively, the “Series”), and ALPS Advisors, Inc. (the “Advisor”), a Colorado corporation registered as an investment adviser under the Investment Advisers Act of 1940.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Filing Dates:</HD>
                    <P> The application was filed on April 9, 2018 and amended on October 2, 2018, and January 9, 2019.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Hearing or Notification of Hearing:</HD>
                    <P> An order granting the application will be issued unless the Commission orders a hearing. Interested persons may request a hearing by writing to the Commission's Secretary and serving applicants with a copy of the request, personally or by mail. Hearing requests should be received by the Commission by 5:30 p.m. on May 31, 2019, and should be accompanied by proof of service on applicants, in the form of an affidavit or, for lawyers, a certificate of service. Pursuant to rule 0-5 under the Act, hearing requests should state the nature of the writer's interest, any facts bearing upon the desirability of a hearing on the matter, the reason for the request, and the issues contested. Persons who wish to be notified of a hearing may request notification by writing to the Commission's Secretary.</P>
                </PREAMHD>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Secretary, U.S. Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090. Applicants, 1290 Broadway, Suite 1100, Denver, CO 80203.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Christine Y. Greenlees, Senior Counsel, at (202) 551-6879, or Andrea Ottomanelli Magovern, Branch Chief, at (202) 551-6821 (Division of Investment Management, Chief Counsel's Office).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The following is a summary of the application. The complete application may be obtained via the Commission's website by searching for the file number, or for an applicant using the Company name box, at 
                    <E T="03">http://www.sec.gov/search/search.htm</E>
                     or by calling (202) 551-8090.
                </P>
                <HD SOURCE="HD1">Summary of the Application</HD>
                <P>
                    1. The Advisor serves or will serve as the investment adviser to each Sub-Advised Series pursuant to an investment advisory agreement with each Trust (the “Investment Management Agreement” and together, the “Investment Management 
                    <PRTPAGE P="20915"/>
                    Agreements”).
                    <SU>1</SU>
                    <FTREF/>
                     Under the terms of each Investment Management Agreement, the Advisor, subject to the supervision of the board of trustees of each Trust (“Board”), provides continuous investment management of the assets of each Sub-Advised Series. Consistent with the terms of each Investment Management Agreement, the Advisor may, subject to the approval of the applicable Board, delegate portfolio management responsibilities of all or a portion of the assets of a Sub-Advised Series to one or more Sub-Advisors.
                    <SU>2</SU>
                    <FTREF/>
                     The Advisor will continue to have overall responsibility for the management and investment of the assets of each Sub-Advised Series. The Advisor will evaluate, select, and recommend Sub-Advisors to manage the assets of a Sub-Advised Series and will oversee, monitor and review the Sub-Advisors and their performance and recommend the removal or replacement of Sub-Advisors.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Applicants request relief with respect to the Series, as well as to any future series of the Trusts and any other existing or future registered open-end management investment company or series thereof that, in each case, is advised by the Advisor, its successors, or any entity controlling, controlled by, or under common control with, the Advisor or its successors (each, also an “Advisor”), uses the multi-manager structure described in the application, and complies with the terms and conditions set forth in the application (each, a “Sub-Advised Series”). For purposes of the requested order, “successor” is limited to an entity that results from a reorganization into another jurisdiction or a change in the type of business organization. Future Sub-Advised Series may be operated as a master-feeder structure pursuant to section 12(d)(1)(E) of the Act. In such a structure, certain Series (each, a “Feeder Fund”) may invest substantially all of their assets in a Sub-Advised Series (a “Master Fund”) pursuant to section 12(d)(1)(E) of the Act. No Feeder Fund will engage any sub-advisers other than through approving the engagement of one or more of the Master Fund's sub-advisers.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         As used herein, a “Sub-Advisor” for a Sub-Advised Series is (1) an indirect or direct “wholly-owned subsidiary” (as such term is defined in the Act) of the Advisor for that Sub-Advised Series, or (2) a sister company of the Advisor for that Sub-Advised Series that is an indirect or direct “wholly-owned subsidiary” of the same company that, indirectly or directly, wholly owns the Advisor (each of (1) and (2) a “Wholly-Owned Sub-Advisor” and collectively, the “Wholly-Owned Sub-Advisors”), or (3) not an “affiliated person” (as such term is defined in section 2(a)(3) of the Act) of the Sub-Advised Series, any Feeder Fund invested in a Master Fund, the Trusts, or the Advisor, except to the extent that an affiliation arises solely because the Sub-Advisor serves as a sub-adviser to a Sub-Advised Series (“Non-Affiliated Sub-Advisors”).
                    </P>
                </FTNT>
                <P>
                    2. Applicants request an order to permit the Advisor, subject to Board approval, to enter into investment sub-advisory agreements with the Sub-Advisors (each, a “Sub-Advisory Agreement”) and materially amend such Sub-Advisory Agreements without obtaining the shareholder approval required under section 15(a) of the Act and rule 18f-2 under the Act.
                    <SU>3</SU>
                    <FTREF/>
                     Applicants also seek an exemption from the Disclosure Requirements to permit a Sub-Advised Series to disclose (as both a dollar amount and a percentage of the Sub-Advised Series' net assets): (a) the aggregate fees paid to the Advisor and any Wholly-Owned Sub-Advisor; (b) the aggregate fees paid to Non-Affiliated Sub-Advisors; and (c) the fee paid to each Affiliated Sub-Advisor (collectively, Aggregate Fee Disclosure”).
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The requested relief will not extend to any sub-adviser, other than a Wholly-Owned Sub-Advisor, who is an affiliated person, as defined in section 2(a)(3) of the Act, of the Sub-Advised Series, of any Feeder Fund, or of the Advisor, other than by reason of serving as a sub-adviser to one or more of the Sub-Advised Series (“Affiliated Sub-Advisor”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         For any Sub-Advised Series that is a Master Fund, the relief would also permit any Feeder Fund invested in that Master Fund to disclose Aggregate Fee Disclosure.
                    </P>
                </FTNT>
                <P>3. Applicants agree that any order granting the requested relief will be subject to the terms and conditions stated in the application. Such terms and conditions provide for, among other safeguards, appropriate disclosure to Sub-Advised Series' shareholders and notification about sub-advisory changes and enhanced Board oversight to protect the interests of the Sub-Advised Series' shareholders.</P>
                <P>4. Section 6(c) of the Act provides that the Commission may exempt any person, security, or transaction or any class or classes of persons, securities, or transactions from any provisions of the Act, or any rule thereunder, if such relief is necessary or appropriate in the public interest and consistent with the protection of investors and purposes fairly intended by the policy and provisions of the Act. Applicants believe that the requested relief meets this standard because, as further explained in the application, the Investment Management Agreements will remain subject to shareholder approval, while the role of the Sub-Advisors is substantially equivalent to that of individual portfolio managers, so that requiring shareholder approval of Sub-Advisory Agreements would impose unnecessary delays and expenses on the Sub-Advised Series.</P>
                <P>Applicants believe that the requested relief from the Disclosure Requirements meets this standard because it will improve the Advisor's ability to negotiate fees paid to the Sub-Advisors that are more advantageous for the Sub-Advised Series.</P>
                <SIG>
                    <P>For the Commission, by the Division of Investment Management, under delegated authority.</P>
                    <NAME>Eduardo A. Aleman,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09721 Filed 5-10-19; 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-85800; File No. SR-CboeEDGX-2019-026]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe EDGX Exchange, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change Relating to Amend Rule 11.11 and Rule 11.16, as Well as Its Fee Schedule, To Delete References to the SWPB Routing Option</SUBJECT>
                <DATE>May 7, 2019.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (the “Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on April 25, 2019, Cboe EDGX Exchange, Inc. (the “Exchange” or “ “EDGX” ”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the Exchange. The Exchange filed the proposal as a “non-controversial” proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>3</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>4</SU>
                    <FTREF/>
                     The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         17 CFR 240.19b-4(f)(6).
                    </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 Rule 11.11 and Rule 11.16, as well as its Fee Schedule, to delete references to the SWPB routing option. 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.
                    <PRTPAGE P="20916"/>
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the Exchange included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant aspects of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>The Exchange proposes to amend Rule 11.11(g) (Routing Options) to delete the SWPB routing option under subparagraph (g)(10), as well as references to the SWPB routing option under Rule 11.16(e) (Limit Up-Limit Down Mechanism). The Exchange also proposes to amend its fee schedule to delete references to the SWPB routing options under fee code SW and under footnote 8. The Exchange intends to implement the proposed rule changes on May 1, 2019.</P>
                <P>
                    Currently, Rule 11.11(g) provides for a variety of routing away options under which the System 
                    <SU>5</SU>
                    <FTREF/>
                     will consider the quotations only of accessible Trading Centers. The term “System routing table” refers to the proprietary process for determining the specific trading venues to which the System routes orders and the order in which it routes them.
                    <SU>6</SU>
                    <FTREF/>
                     Rule 11.13(g)(10) currently provides for SWPB as one of such routing options. SWPB is a routing option under which an order checks the System for available shares and then is sent to only Protected Quotations and only for displayed size. To the extent that any portion of the routed order is unexecuted, the remainder is posted to the EDGX Book at the order's limit price, unless otherwise instructed by the User.
                    <SU>7</SU>
                    <FTREF/>
                     Also, if at the time of entry, there is an insufficient share quantity in the SWPB order to fulfill the displayed size of all Protected Quotations, then the entire SWPB order will be cancelled back to the User immediately. Currently, Rule 11.16 provides for the Regulation NMS Plan to Address Extraordinary Market Volatility (the “Plan”) during a pilot period. Specifically, Rule 11.16(e)(5)(D)(2) provides a description of how the two current SWP routing strategies, SWPA and SPWB, are handled in accordance with the Plan when an order to buy utilizing an SWP routing strategy has a limit price that is greater than the Upper Price Band or if a sell order utilizing an SWP routing strategy has a limit price that is less than the Lower Price Band. Additionally, current fee code SW is yielded on orders routed using SWPA or SWPB routing strategies, except for removal of liquidity from the New York Stock Exchange (“NYSE”).
                    <SU>8</SU>
                    <FTREF/>
                     Current footnote 8 provides that fee code D will be yielded on orders routed using SWPA or SWPB if such strategy removes liquidity from NYSE.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The “System” is the Exchange's electronic communications and trading facility designated by the Board through which securities orders of Users are consolidated for ranking, execution and, when applicable, routing away. 
                        <E T="03">See</E>
                         Exchange Rule 1.5(cc).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The Exchange reserves the right to maintain a different System routing table for different routing options and to modify the System routing table at any time without notice. 
                        <E T="03">See</E>
                         Exchange Rule 11.11(g).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The term “User” is defined as “any Member or Sponsored Participant who is authorized to obtain access to the System pursuant to Rule 11.3.” 
                        <E T="03">See</E>
                         Exchange Rule 1.5(ee).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Orders that yield fee code SW receive a discounted fee of $0.0031 per share at or above $1.00 and 0.30% of Dollar Value per share below $1.00.
                    </P>
                </FTNT>
                <P>
                    The Exchange has determined that because few Users elect the SWPB routing option, which often experiences no usage for extended periods of time, the current demand does not warrant the infrastructure and ongoing maintenance expenses required to support these products. Therefore, the Exchange now proposes to delete SWPB as a routing option under Rule 11.11(g)(10) and references to the SWPB routing option under Rule 11.16(e)(5)(D)(2). The Exchange proposes to amend Rule 11.11(g) formatting accordingly, changing the numbering of current subparagraphs (g)(11) through (g)(14) to subparagraphs (g)(10) through (g)(13). The Exchange also proposes to amend its fee schedule to delete references to the SWPB routing option under fee code SW, as well as under footnote 8. The Exchange notes that Users seeking to route only to Protected Quotations for displayed size may use the other SWP routing option, SWPA.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Exchange Rule 11.11(g)(9).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes the proposed rule change is consistent with the Securities Exchange Act of 1934 (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>10</SU>
                    <FTREF/>
                     Specifically, the Exchange believes the proposed rule change is consistent with the Section 6(b)(5) 
                    <SU>11</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>12</SU>
                    <FTREF/>
                     requirement that the rules of an exchange not be designed to permit unfair discrimination between customers, issuers, brokers, or dealers.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    In particular, The Exchange does not believe that this proposal will permit unfair discrimination among customers, brokers, or dealers because the SWPB routing options will no longer be available to all Users. Also, the Exchange believes the proposed rule change to remove references to SWPB will remove impediments to the mechanism of a free and open market, thereby protecting investors and the public interest. As stated, the Exchange noted that few Users elect the SWPB routing option and has determined that the current demand does not warrant the infrastructure and ongoing maintenance expense required to support these products. Therefore, the Exchange is discontinuing this routing option. The Exchange notes that routing through the Exchange is voluntary and Users are free to designate the alternative SWP routing option, SWPA, currently offered by the Exchange.
                    <SU>13</SU>
                    <FTREF/>
                     In addition, the SWPB routing option is not a core product offering by the Exchange, nor is the Exchange required by the Act to offer such a product. By removing references to a routing option that will no longer be offered by the Exchange, the Exchange believes the proposed rule change will remove impediments to the mechanism of a free and open market and protect investors by providing investors with increased transparency regarding rules that reflect routing options currently available on the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See supra</E>
                         note 9.
                    </P>
                </FTNT>
                <PRTPAGE P="20917"/>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed rule change to remove SWPB is not designed to address any competitive issues but rather to increase transparency by eliminating the SWPB routing option that is to be discontinued by the Exchange.</P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>The Exchange neither solicited nor received comments on the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The Exchange has filed the proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>14</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>15</SU>
                    <FTREF/>
                     thereunder. Because the foregoing proposed rule change does not: (i) Significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative for 30 days from the date on which it was filed, or such shorter time as the Commission may designate, it has become effective pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>16</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>17</SU>
                    <FTREF/>
                     thereunder.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6)(iii) requires the Exchange to give the Commission written notice of the Exchange's intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    A proposed rule change filed under Rule 19b-4(f)(6) normally does not become operative for 30 days after the date of the filing. However, Rule 19b-4(f)(6)(iii) 
                    <SU>18</SU>
                    <FTREF/>
                     permits the Commission to designate a shorter time if such action is consistent with the protection of investors and the public interest. The Exchange has asked the Commission to waive the 30-day operative delay. In support of its waiver request, the Exchange stated its belief that waiving the operative delay would allow the Exchange to modify its rules in a timely manner by eliminating rules that account for a service the Exchange intends to discontinue on May 1, 2019. The Commission believes that waiver of the operative delay is consistent with the protection of investors and the public interest, and accordingly, the Commission hereby waives the 30-day operative delay and designates the proposed rule change operative upon filing.
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         17 CFR 240.19b-4(f)(6)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         For purposes only of waiving the 30-day operative delay, the Commission has also considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <P>At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission will institute proceedings to determine whether the proposed rule change should be approved or disapproved.</P>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-CboeEDGX-2019-026 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-
                    <E T="03">2019-026.</E>
                     This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of 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:00 a.m. and 3:00 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change. Persons submitting comments are cautioned that we do not redact or edit personal identifying information from comment submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-CboeEDGX-2019-026 and should be submitted on or before June 3, 2019.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>20</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Eduardo A. Aleman,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09726 Filed 5-10-19; 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-85799; File No. SR-CboeEDGA-2019-008)</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe EDGA Exchange, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change Relating To Amend Rule 11.11 and Rule 11.16, as Well as Its Fee Schedule, To Delete References to the SWPB Routing Option</SUBJECT>
                <DATE>May 7, 2019.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (the “Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on April 25, 2019, Cboe EDGA Exchange, Inc. (the “Exchange” or “EDGA”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the Exchange. The Exchange filed the proposal as a “non-controversial” proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>3</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>4</SU>
                    <FTREF/>
                     The 
                    <PRTPAGE P="20918"/>
                    Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>Cboe EDGA Exchange, Inc. (the “Exchange” or “EDGA”) proposes to amend Rule 11.11 and Rule 11.16, as well as its Fee Schedule, to delete references to the SWPB routing option. The text of the proposed rule change is provided in Exhibit 5.</P>
                <P>
                    The text of the proposed rule change is also available on the Exchange's website (
                    <E T="03">http://markets.cboe.com/us/equities/regulation/rule_filings/edga/</E>
                    ), at the Exchange's Office of the Secretary, and at the Commission's Public Reference Room.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the Exchange included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant aspects of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>The Exchange proposes to amend Rule 11.11(g) (Routing Options) to delete the SWPB routing option under subparagraph (g)(10), as well as references to the SWPB routing option under Rule 11.16(e) (Limit Up-Limit Down Mechanism). The Exchange also proposes to amend its fee schedule to delete references to the SWPB routing options under fee code SW and under footnote 3. The Exchange intends to implement the proposed rule changes on May 1, 2019.</P>
                <P>
                    Currently, Rule 11.11(g) provides for a variety of routing away options under which the System 
                    <SU>5</SU>
                    <FTREF/>
                     will consider the quotations only of accessible Trading Centers. The term “System routing table” refers to the proprietary process for determining the specific trading venues to which the System routes orders and the order in which it routes them.
                    <SU>6</SU>
                    <FTREF/>
                     Rule 11.13(g)(10) currently provides for SWPB as one of such routing options. SWPB is a routing option under which an order checks the System for available shares and then is sent to only Protected Quotations and only for displayed size. To the extent that any portion of the routed order is unexecuted, the remainder is posted to the EDGA Book at the order's limit price, unless otherwise instructed by the User.
                    <SU>7</SU>
                    <FTREF/>
                     Also, if at the time of entry, there is an insufficient share quantity in the SWPB order to fulfill the displayed size of all Protected Quotations, then the entire SWPB order will be cancelled back to the User immediately. Currently, Rule 11.16 provides for the Regulation NMS Plan to Address Extraordinary Market Volatility (the “Plan”) during a pilot period. Specifically, Rule 11.16(e)(5)(D)(ii) provides a description of how the two current SWP routing strategies, SWPA and SPWB, are handled in accordance with the Plan when an order to buy utilizing an SWP routing strategy has a limit price that is greater than the Upper Price Band or if a sell order utilizing an SWP routing strategy has a limit price that is less than the Lower Price Band. Additionally, current fee code SW is yielded on orders routed using SWPA or SWPB routing strategies, except for removal of liquidity from the New York Stock Exchange (“NYSE”).
                    <SU>8</SU>
                    <FTREF/>
                     Current footnote 3 provides that fee code D will be yielded on orders routed using SWPA or SWPB if such strategy removes liquidity from NYSE.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The “System” is the Exchange's electronic communications and trading facility designated by the Board through which securities orders of Users are consolidated for ranking, execution and, when applicable, routing away. 
                        <E T="03">See</E>
                         Exchange Rule 1.5(cc).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The Exchange reserves the right to maintain a different System routing table for different routing options and to modify the System routing table at any time without notice. 
                        <E T="03">See</E>
                         Exchange Rule 11.11(g).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The term “User” is defined as “any Member or Sponsored Participant who is authorized to obtain access to the System pursuant to Rule 11.3.” 
                        <E T="03">See</E>
                         Exchange Rule 1.5(ee).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Orders that yield fee code SW receive a discounted fee of $0.0031 per share at or above $1.00 and 0.30% of Dollar Value per share below $1.00.
                    </P>
                </FTNT>
                <P>
                    The Exchange has determined that because few Users elect the SWPB routing option, which often experiences no usage for extended periods of time, the current demand does not warrant the infrastructure and ongoing maintenance expenses required to support these products. Therefore, the Exchange now proposes to delete SWPB as a routing option under Rule 11.11(g)(10) and references to the SWPB routing option under Rule 11.16(e)(5)(D)(ii). The Exchange proposes to amend Rule 11.11(g) formatting accordingly, changing the numbering of current subparagraphs (g)(11) through (g)(16) to subparagraphs (g)(10) through (g)(15). The Exchange also proposes to amend its fee schedule to delete references to the SWPB routing option under fee code SW, as well as under footnote 3. The Exchange notes that Users seeking to route only to Protected Quotations for displayed size may use the other SWP routing option, SWPA.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Exchange Rule 11.11(g)(9).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes the proposed rule change is consistent with the Securities Exchange Act of 1934 (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>10</SU>
                    <FTREF/>
                     Specifically, the Exchange believes the proposed rule change is consistent with the Section 6(b)(5) 
                    <SU>11</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>12</SU>
                    <FTREF/>
                     requirement that the rules of an exchange not be designed to permit unfair discrimination between customers, issuers, brokers, or dealers.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    In particular, The Exchange does not believe that this proposal will permit unfair discrimination among customers, brokers, or dealers because the SWPB routing options will no longer be available to all Users. Also, the Exchange believes the proposed rule change to remove references to SWPB will remove impediments to the mechanism of a free and open market, thereby protecting investors and the public interest. As stated, the Exchange noted that few Users elect the SWPB routing option and has determined that the current demand does not warrant the infrastructure and ongoing maintenance expense required to support these products. Therefore, the Exchange is discontinuing this routing option. The Exchange notes that routing through the Exchange is voluntary and 
                    <PRTPAGE P="20919"/>
                    Users are free to designate the alternative SWP routing option, SWPA, currently offered by the Exchange.
                    <SU>13</SU>
                    <FTREF/>
                     In addition, the SWPB routing option is not a core product offering by the Exchange, nor is the Exchange required by the Act to offer such a product. By removing references to a routing option that will no longer be offered by the Exchange, the Exchange believes the proposed rule change will remove impediments to the mechanism of a free and open market and protect investors by providing investors with increased transparency regarding rules that reflect routing options currently available on the Exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See supra</E>
                         note 9.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed rule change to remove SWPB is not designed to address any competitive issues but rather to increase transparency by eliminating the SWPB routing option that is to be discontinued by the Exchange.</P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>The Exchange neither solicited nor received comments on the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The Exchange has filed the proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>14</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>15</SU>
                    <FTREF/>
                     thereunder. Because the foregoing proposed rule change does not: (i) Significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative for 30 days from the date on which it was filed, or such shorter time as the Commission may designate, it has become effective pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>16</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>17</SU>
                    <FTREF/>
                     thereunder.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6)(iii) requires the Exchange to give the Commission written notice of the Exchange's intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    A proposed rule change filed under Rule 19b-4(f)(6) normally does not become operative for 30 days after the date of the filing. However, Rule 19b-4(f)(6)(iii) 
                    <SU>18</SU>
                    <FTREF/>
                     permits the Commission to designate a shorter time if such action is consistent with the protection of investors and the public interest. The Exchange has asked the Commission to waive the 30-day operative delay. In support of its waiver request, the Exchange stated its belief that waiving the operative delay would allow the Exchange to modify its rules in a timely manner by eliminating rules that account for a service the Exchange intends to discontinue on May 1, 2019. The Commission believes that waiver of the operative delay is consistent with the protection of investors and the public interest, and accordingly, the Commission hereby waives the 30-day operative delay and designates the proposed rule change operative upon filing.
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         17 CFR 240.19b-4(f)(6)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         For purposes only of waiving the 30-day operative delay, the Commission has also considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <P>At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission will institute proceedings to determine whether the proposed rule change should be approved or disapproved.</P>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-CboeEDGA-2019-008 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>
                <P>
                    All submissions should refer to File Number SR-CboeEDGA-2019-008. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">http://www.sec.gov/rules/sro.shtml).</E>
                     Copies of 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:00 a.m. and 3:00 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change. Persons submitting comments are cautioned that we do not redact or edit personal identifying information from comment submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-CboeEDGA-2019-008 and should be submitted on or before June 3, 2019.
                </P>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>20</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Eduardo A. Aleman,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09725 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <SUBJECT>Proposed Collection; Comment Request</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-02736
                </FP>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        <E T="03">Extension:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Form 18-K, SEC File No. 270-108, OMB Control No. 3235-0120</FP>
                </EXTRACT>
                <PRTPAGE P="20920"/>
                <P>
                    Notice is hereby given that, pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), the Securities and Exchange Commission (“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>Form 18-K (17 CFR 249.318) is an annual report form used by foreign governments or political subdivisions of foreign governments that have securities listed on a United States exchange. The information to be collected is intended to ensure the adequacy and public availability of information available to investors. We estimate that Form 18-K takes approximately 8 hours to prepare and is filed by approximately 36 respondents for a total annual reporting burden of 288 hours (8 hours per response × 36 responses).</P>
                <P>
                    <E T="03">Written comments are invited on:</E>
                     (a) Whether this proposed collection of information is necessary for the performance of the functions of the agency, including whether the information will have practical utility; (b) the accuracy of the agency's estimate of the burden imposed by 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 in writing within 60 days of this publication.
                </P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid control number.</P>
                <P>
                    Please direct your written comment to Charles Riddle, Acting Director/Chief Information Officer, Securities and Exchange Commission, c/o Candace Kenner, 100 F Street NE, Washington, DC 20549 or send an email to: 
                    <E T="03">PRA_Mailbox@sec.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: May 8, 2019.</DATED>
                    <NAME>Eduardo A. Aleman,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09801 Filed 5-10-19; 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-85797; File No. SR-CboeEDGX-2019-027]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe EDGX Exchange, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change Relating To Amend the Exchange's Opening Process and Add a Global Trading Hours Session for XSP Options</SUBJECT>
                <DATE>May 7, 2019.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (the “Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on April 26, 2019, Cboe EDGX Exchange, Inc. (the “Exchange” or “EDGX”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the Exchange. The Exchange filed the proposal as a “non-controversial” proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>3</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>4</SU>
                    <FTREF/>
                     The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         17 CFR 240.19b-4(f)(6).
                    </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 Options”) proposes to amend the Exchange's opening process, add a global trading hours session (“Global Trading Hours” or “GTH”) for options on the Mini-SPX Index (“XSP options”) and make corresponding changes, modify trading hours for certain equity and index options, update its Rules regarding order cancellation, clarify the manner in which the Exchange announces determinations it makes under the Rules, and make other conforming and nonsubstantive changes. 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 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>In 2016, the Exchange's parent company, Cboe Global Markets, Inc. (“Cboe Global”), which is also the parent company of Cboe Exchange, Inc. (“Cboe Options”) and Cboe C2 Exchange, Inc. (“C2”), acquired the Exchange, Cboe EDGA Exchange, Inc. (“EDGA”), Cboe BZX Exchange, Inc. (“BZX or BZX Options”), and Cboe BYX Exchange, Inc. (“BYX” and, together with C2, Cboe Options, EDGA, and BZX, the “Cboe Affiliated Exchanges”). The Cboe Affiliated Exchanges are working to align certain system functionality, retaining only intended differences between the Cboe Affiliated Exchanges, in the context of a technology migration. Cboe Options intends to migrate its technology to the same trading platform used by the Exchange, C2, and BZX Options in the fourth quarter of 2019. The proposal set forth below is intended to add certain functionality to the Exchange's System that is more similar to functionality offered by Cboe Options in order to ultimately provide a consistent technology offering for market participants who interact with the Cboe Affiliated Exchanges. Although the Exchange intentionally offers certain features that differ from those offered by its affiliates and will continue to do so, the Exchange believes that offering similar functionality to the extent practicable will reduce potential confusion for Users.</P>
                <HD SOURCE="HD3">Global Trading Hours</HD>
                <P>
                    The proposed rule change adds a GTH trading session to the Rules. Currently, transactions in equity options, which includes options on individual stocks, exchange-traded funds (“Fund Shares” 
                    <SU>5</SU>
                    <FTREF/>
                    ), exchange-traded notes 
                    <PRTPAGE P="20921"/>
                    (“Index-Linked Securities” 
                    <SU>6</SU>
                    <FTREF/>
                    ), and other securities) may occur from 9:30 a.m. to 4:00 p.m.
                    <SU>7</SU>
                    <FTREF/>
                    , except for options on Fund Shares, Index-Linked Securities, and broad-based indexes, which will close at 4:15 p.m.
                    <SU>8</SU>
                    <FTREF/>
                     As proposed, these hours are referred to as “Regular Trading Hours.” 
                    <SU>9</SU>
                    <FTREF/>
                     Regular Trading Hours are consistent with the regular trading hours of the most other U.S. options exchanges. Cboe Options has a global trading hours session during which trading in certain option classes, which trading session occurs from 3:00 a.m. to 9:15 a.m.
                    <SU>10</SU>
                    <FTREF/>
                     Additionally, many U.S. stock and futures exchanges, which allow for trading in some of their listed products for various periods of time outside of Regular Trading Hours.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Rule 19.3(i).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Rule 19.3(l).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         All times are Eastern time unless otherwise noted.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         current Rule 21.2(a). The proposed rule change moves the rule provision in current Rule 21.2(b) into proposed Rule 21.2(b)(1), so that all rule provisions regarding Regular Trading Hours of equity options are included in the same place.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See also</E>
                         proposed Rule 16.1, definition of Regular Trading Hours or RTH (the trading session consisting of the regular hours during which transactions in options may be effected on the Exchange, as set forth in Rule 21.2); and Cboe Options Rule 1.1 (definition of Regular Trading Hours). The proposed rule change makes nonsubstantive changes to Rule 16.1 to alphabetize the definitions in that rule, delete the paragraph heading “(a)” since that is the only paragraph in the rule and delete subparagraph numbering, and add headings for each defined term.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         Cboe Options Rule 6.1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See, e.g.,</E>
                         BZX Rule 1.5(c), (r), (w), and (ee) (regular trading hours from 9:30 a.m. until 4:00 p.m. Eastern time, two early trading sessions (Early Trading Session and Pre-Opening Session) from 7:00 a.m. until 9:30 a.m. and an After Hours Trading Session from 4:00 p.m. to 8:00 p.m. Eastern time); NASDAQ Stock Market LLC Rule 4617 (regular trading hours from 9:30 a.m. until 4:00 p.m. Eastern time and extended trading hours from 4:00 a.m. until 9:30 a.m. and 4:00 p.m. to 8:00 p.m. Eastern time); and New York Stock Exchange LLC Series 900 (providing for an off-hours trading facility to operate outside of the regular 9:30 a.m. to 4:00 p.m. Eastern time trading session); 
                        <E T="03">see also, e.g.,</E>
                         Chicago Board of Trade Extended Trading Hours for Grain, Oilseeds and Ethanol—Frequently Asked Questions (indicating that certain agricultural commodity products are available for electronic trading 21 hours a day on the CME Globex trading platform); and Intercontinental Exchange, Inc. Regular Trading &amp; Support Hours (indicating that many of its listed products are available for trading for periods of time outside of Regular Trading Hours, including overnight sessions).
                    </P>
                </FTNT>
                <P>
                    As noted above, many U.S. stock exchanges allow for trading in stocks before and after the regular trading hours of 9:30 a.m. to 4:00 p.m., including stocks that comprise the Dow Jones Industrial Average. It is common for investors to engage in hedging and other investment strategies that involve index options and some of the stocks that comprise the underlying index. Currently, this investment activity on the Exchange would be limited to Regular Trading Hours. Additionally, securities trading is a global industry, and investors located outside of the United States generally operate during hours outside of Regular Trading Hours. The Exchange believes there may be global demand from investors for options on XSP, which may be exclusively listed 
                    <SU>12</SU>
                    <FTREF/>
                     on Cboe Affiliated Exchanges and which the Exchange plans to list during the proposed Global Trading Hours (as defined below), as alternatives for hedging and other investment purposes. Given that XSP options are currently only eligible to trade during Regular Trading Hours, it is difficult for non-U.S. investors to obtain the benefits of trading in this option. It is also difficult for U.S. investors that trade in non-U.S. markets to use these products as part of their global investment strategies. To meet this demand, and to keep pace with the continuing internationalization of securities markets, the Exchange proposes to offer trading in XSP options from 8:30 a.m. to 9:15 a.m. Monday through Friday (“Global Trading Hours” or “GTH”).
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         An “exclusively listed option” is an option that trades exclusively on an exchange (or exchange group) because the exchange has an exclusive license to list and trade the option or has the proprietary rights in the interest underlying the option. An exclusively listed option is different than a “singly listed option,” which is an option that is not an “exclusively listed option” but that is listed by one exchange and not by any other national securities.
                    </P>
                </FTNT>
                <P>
                    Proposed Rule 21.2(c) states except under unusual conditions as may be determined by the Exchange, Global Trading Hours are from 8:30 a.m. to 9:15 a.m. on Monday through Friday.
                    <SU>13</SU>
                    <FTREF/>
                     While this trading session will be shorter than the global trading hours session on Cboe Options and various stock exchanges, the Exchange believes this proposed trading session will increase the time during which Options Members may implement these investment strategies. This GTH trading session will allow market participants to engage in trading these options in conjunction with extended trading hours on U.S. stock exchanges for securities that comprise the index underlying XSP options and in conjunction with part of regular European trading hours. The proposed rule change also adds to Rule 16.1 a definition of trading session, which means the hours during which the Exchange is open for trading for Regular Trading Hours or Global Trading Hours (each of which may be referred to as a trading session), each as defined in proposed Rule 21.2. Unless otherwise specified in the Rules or the context indicates otherwise, all Rules apply in the same manner during each trading session.
                    <SU>14</SU>
                    <FTREF/>
                     As discussed below, the Exchange may not permit certain order types to be applied to orders during Global Trading Hours that it does permit during Regular Trading Hours.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See also</E>
                         proposed Rule 16.1, definition of Global Trading Hours or GTH (the trading session consisting of the hours outside of Regular Trading Hours during which transactions in options may be effected on the Exchange and are set forth in Rule 6.1); and Cboe Options Rule 1.1 (definition of Global Trading Hours).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         This includes business conduct rules in Chapter XVIII and rules related to doing business with the public in Chapter XXVI. Additionally a broker-dealer's due diligence and best execution obligations apply during Global Trading Hours. 
                        <E T="03">See also</E>
                         Cboe Options Rule 6.1A(a).
                    </P>
                </FTNT>
                <P>
                    Proposed Rule 21.2(c)(1) provides the Exchange with authority to designate as eligible for trading during Global Trading Hours any exclusively listed index option designated for trading under Chapter XXIX.
                    <SU>15</SU>
                    <FTREF/>
                     If the Exchange so designates a class, then transactions in options in that class may be made on the Exchange during Global Trading Hours.
                    <SU>16</SU>
                    <FTREF/>
                     As indicated above, the Exchange has approved XSP options for trading on the Exchange during Global Trading Hours. The Exchange may list for trading during Global Trading Hours any series in eligible classes that it may list pursuant to Rule 19.6.
                    <SU>17</SU>
                    <FTREF/>
                     Any series in eligible classes that are expected to be open for trading during Regular Trading Hours will be open for trading during Global Trading Hours on the same trading day (subject to Rule 21.7 (as proposed to be amended, as discussed below), which sets forth procedures for the opening of trading).
                    <SU>18</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         A class that the Exchange lists for trading during RTH only will be referred to as an “RTH class,” and a class the Exchange lists for trading during both GTH and RTH will be referred to as an “All Sessions class.” 
                        <E T="03">See</E>
                         Rule 16.1, proposed definitions of “All Sessions classes” and “RTH classes.”
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         The Exchange believes it is appropriate to retain flexibility to determine whether to operate during Global Trading Hours so that it can complete all system work on other preparations prior to implementing Global Trading Hours in a class, and so that the Exchange can evaluate trading activity during Global Trading Hours once implemented and determine whether to continue or modify the trading session (subject to applicable rule filings).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See also</E>
                         Cboe Options Rule 6.1A(c).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See also</E>
                         Cboe Options Rule 6.1A(c).
                    </P>
                </FTNT>
                <P>
                    The proposed rule change defines a “business day” or “trading day” as a day on which the Exchange is open for trading during Regular Trading Hours (this is consistent with the current concept of trading day used but not defined in the Rules).
                    <SU>19</SU>
                    <FTREF/>
                     A business day 
                    <PRTPAGE P="20922"/>
                    or trading day will include both trading sessions on that day. In other words, if the Exchange is not open for Regular Trading Hours on a day (for example, because it is an Exchange holiday), then it will not be open for Global Trading Hours on that day. Cboe Options has the same definition of business day and trading day.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         The proposed rule change makes corresponding changes to the definitions of market open and market close in Rule 16.1 to provide that 
                        <PRTPAGE/>
                        each term specifies the start or end, respectively, of a trading session.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See</E>
                         Cboe Options Rule 1.1.
                    </P>
                </FTNT>
                <P>
                    Global Trading Hours will be a separate trading session from Regular Trading Hours. However, GTH will use the same Exchange servers and hardware as those used during RTH.
                    <SU>21</SU>
                    <FTREF/>
                     All Options Members may participate in Global Trading Hours. Options Members do not need to apply or take any additional steps to participate in Global Trading Hours. Additionally, because the Exchange will use the same servers and hardware during Global Trading Hours as it uses for Regular Trading Hours, Options Members may use the same ports and connections to the Exchange for all trading sessions.
                    <SU>22</SU>
                    <FTREF/>
                     The Book used during Regular Trading Hours will be the same Book used during Global Trading Hours.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         This is different than the trading sessions on Cboe Options, which uses different servers and hardware for each trading session.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         Only Options Members will be able to access the System during any trading session. Cboe Options Trading Permit Holders must obtain a separate permit and use different connections to participate in global trading hours. 
                        <E T="03">See</E>
                         Cboe Options Rules 3.1 and 6.1A(d).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         proposed Rule 16.1, which amends the definition of EDGX Options Book to mean the electronic book of simple orders and quotes maintained by the System on which orders and quotes may execute during the applicable trading session. The Book during GTH may be referred to as the “GTH Book,” and the Book during RTH may be referred to as the “RTH Book.” The additional language regarding the execution of orders and quotes is intended to distinguish the Book from the Queuing Book, on which orders and quotes may not execute, as discussed below. With respect to complex orders, the same complex order book (“COB”) will be used for all trading sessions. 
                        <E T="03">See</E>
                         proposed Rule 21.20(a) (definition of COB). This is different than Cboe Options, which uses separate books for each trading session, which are not connected.
                    </P>
                </FTNT>
                <P>
                    As further discussed below, the Exchange expects there to be reduced liquidity, higher volatility, and wider markets during Global Trading Hours, and investors may not want their orders or quotes to execute during Global Trading Hours given those trading conditions. To provide investors with flexibility to have their orders and quotes execute only during RTH, or both RTH and GTH, the proposed rule change adds an All Sessions order and an RTH Only order. An “All Sessions” order is an order a User designates as eligible to trade during both GTH and RTH. An unexecuted All Sessions order on the GTH Book at the end of a GTH trading session enters the RTH Queuing Book and becomes eligible for execution during the RTH opening rotation and trading session on the same trading day, subject to a User's instructions (for example, a User may cancel the order).
                    <SU>24</SU>
                    <FTREF/>
                     An “RTH Only” order is an order a User designates as eligible to trade only during RTH or not designated as All Sessions. An unexecuted RTH Only order with a Time-in-Force of GTC or GTD on the RTH Book at the end of an RTH trading session enters the RTH Queuing Book and becomes eligible for execution during the RTH opening rotation and trading session on the following trading day (but not during the GTH trading session on the following trading day), subject to a User's instructions.
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See</E>
                         proposed Rule 21.1(d)(13).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See</E>
                         proposed Rule 21.1(d)(14). The RTH Only and All Sessions order instructions will also be available for complex orders. 
                        <E T="03">See</E>
                         proposed Rule 21.20(b)(7) and (8).
                    </P>
                </FTNT>
                <P>Because trading sessions are completely separate on Cboe Options, there are not distinct order types corresponding to the proposed RTH Only and All Sessions order instructions. An order or quote submitted to GTH on Cboe Options may only execute during GTH, and an order or quote submitted to RTH on Cboe Options may only execute during RTH. The proposed RTH Only order is equivalent to any order submitted to RTH on Cboe Options. While the Exchange is not proposing an equivalent to an order submitted to GTH on Cboe Options, and instead is proposing an All Sessions order, Users may still submit an equivalent to a “GTH only” order by submitting an All Sessions order with a good-til-date Time-in-Force, with a time to cancel before the RTH market open. Therefore, Users can submit orders to participate in either trading session, or both, and thus the proposed rule change provides Users with additional flexibility and control regarding in which trading sessions their orders and quotes may be eligible to trade.</P>
                <P>
                    Generally, trading during the GTH trading session will occur in the same manner as it occurs during the RTH trading session. However, because the GTH market may have different characteristics than the RTH market (such as lower trading levels, reduced liquidity, and fewer participants), the Exchange may deem it appropriate to make different determinations for trading rules for each trading session. Proposed Rule 16.3(b) states to the extent the Rules allow the Exchange to make a determination, including on a class-by-class or series-by-series basis, the Exchange may make a determination for GTH that differs from the determination it makes for RTH. The Exchange maintains flexibility with respect to certain rules so that it may apply different settings and parameters to address the specific characteristics of that class and its market. For example, Rule 21.8(d) allows the Exchange to apply priority overlays to the pro-rata allocation method on a class-by-class basis; and Rule 21.20(b) allows the Exchange to determine when complex order types are available.
                    <SU>26</SU>
                    <FTREF/>
                     Proposed rule 21.1(a) and (d) allow the Exchange to make certain order types and Times-in-Force, respectively, not available for all Exchange systems or classes (and unless stated in the Rules or the context indicates otherwise, as proposed).
                    <SU>27</SU>
                    <FTREF/>
                     This proposed rule change will provide the Exchange with appropriate flexibility to address different trading characteristics, market models, and investor base of each class. Because trading characteristics during RTH may be different than those during GTH (such as lower trading levels, reduced liquidity, and fewer participants), the Exchange believes it is appropriate to extend this flexibility to each trading session. The Exchange represents that it will have appropriate personnel available during GTH to make any determinations that Rules provide the Exchange or Exchange personnel will make (such as trading halts, opening series, and obvious errors).
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         Therefore, the priority overlays that applies to a class during RTH may differ from the allocation algorithm that apply to that class during GTH.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         The proposed rule change amends these rules to explicitly state that the Exchange may make these determinations on a trading session basis. The proposed rule change also clarifies in the Rules that Rule 21.20 sets forth the order types the Exchange may make available for complex orders.
                    </P>
                </FTNT>
                <P>
                    The proposed rule change amends Rules 22.2 and 22.3 to provide that a Designated Primary Market Maker's and Market Maker's, respectively, selected class appointment applies to classes during all trading sessions. In order words, if a Market Maker selects an appointment in XSP options, that appointment would apply during both GTH and RTH (and thus, the Market-Maker would have an appointment to make markets in XSP during both GTH and RTH). As a result, a Market-Maker continuous quoting obligations set forth in Rule 22.6(d) would apply to the class for an entire trading day (including both trading sessions), which is comprised of 7.5 hours.
                    <SU>28</SU>
                    <FTREF/>
                     Pursuant to Rule 22.6(d), a 
                    <PRTPAGE P="20923"/>
                    Market-Maker must enter continuous bids and offers in 60% of the cumulative number of seconds, or such higher percentage as the Exchange may announce in advance, for which that Market-Maker's appointed classes are open for trading, excluding any adjusted series, any intra-day add-on series on the day during which such series are added for trading, any Quarterly Option Series, and any series with an expiration of greater than 270 days. The Exchange calculates this requirement by taking the total number of seconds the Market-Maker disseminates quotes in each appointed class (excluding the series noted above), and dividing that time by the eligible total number of seconds each appointed class is open for trading that day.
                    <SU>29</SU>
                    <FTREF/>
                     As proposed, the 45 minutes that comprise Global Trading Hours during which the Exchange will list series of XSP options 
                    <SU>30</SU>
                    <FTREF/>
                     will be included in the denominator of this calculation. The Exchange expects to list 4,302 series of XSP options, 312 of which with expirations of greater than 270 days and 660 with quarterly expirations. Therefore, 3,330 series will be counted for purposes of determining a Market Maker's continuous quoting obligation for the number of minutes the series are open during Global Trading Hours.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See</E>
                         proposed Rule 22.6(d). This is different from Cboe Options, which applies Market-Maker 
                        <PRTPAGE/>
                        appointments separately to each trading session. 
                        <E T="03">See</E>
                         Cboe Options Rules 6.1A(e) and 8.7(d).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         The proposed rule change clarifies that the time the Exchange is open for trading on a trading day (including all trading sessions) will be considered when determining a Market Maker's satisfaction of this obligation.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         This is the number of XSP series currently listed on Cboe Options.
                    </P>
                </FTNT>
                <P>
                    For example, suppose a Market Maker has appointments in ten classes. Assume there are 2,000 series (excluding series with quarterly expirations and expirations of greater than 270 days) in each class, for a total of 20,000 series, and all series in each of those ten classes are open for trading from 9:30:30 to 4:00:00. That would create an eligible total number of seconds for each series of 23,370 seconds (and thus, a total of 467,400,000 seconds for all appointed classes in the aggregate) each trading day. To satisfy its continuous quoting obligation, the Market Maker would need to be quoting for 60% of that time in any combination of series across those classes (or a total of at least 280,440,000 seconds). Suppose when the Exchange begins listing XSP options on the Exchange for both GTH and RTH, the Market-Maker selects an XSP appointment, and the Exchange lists 3,330 series of XSP options that do not have quarterly expirations or expirations of greater than 270 days. Assume all series in XSP are open for trading from 8:30:30 to 9:15:00 and 9:30:30 to 4:15:00. That would create an eligible total number of seconds of 8,891,100 seconds during GTH and 80,819,100 seconds during RTH, for a total of 89,710,200 seconds, for XSP during the trading day). If XSP were only listed during RTH, the total eligible quoting time would be 548,219,100 seconds across the eleven classes, and a Market Maker would be required to quote 328,931,460 seconds in series across those classes. If XSP were listed in both RTH and GTH, the total eligible quoting time would be 557,110,200 seconds during a trading day across all eleven classes, and the Market Maker would be required to quote 334,266,120 seconds across series in the eleven classes. Therefore, extending the XSP continuous quoting obligation for a Market Maker with appointments in a total of eleven classes, including XSP, would increase a Market Maker's required quoting time by 5,334,660 seconds, or 1.62%. The Market Maker could determine to satisfy this increase during RTH or GTH in any of its appointed classes. For example, if a Market Maker selects an XSP appointment but does not want to participate during GTH, the Market Maker could add this quoting time during RTH (
                    <E T="03">e.g.,</E>
                     given the total of 23,330 series across its 11 appointed classes, the Market Maker could quote an additional 485 seconds (just over 8 minutes) in each of 11,000 of those series (fewer than half of its appointed series) on a trading day, it could satisfy its continuous quoting obligation without quoting in any XSP series during any portion of GTH.
                </P>
                <P>As the above example demonstrates, while the proposed rule change will increase the total time during which a Market Maker with an XSP appointment must quote, this increase is de minimis given that a Market Maker's compliance with its continuous quoting obligation is based on all classes in which it has an appointment in the aggregate. Selecting an appointment in XSP options will be optional and within the discretion of a Market Maker. Additionally, the Exchange is providing Market Makers with the opportunity to quote during GTH (and receive the benefits of acting as a Market Maker with respect to transactions it effects during that time) without creating additional connections to the Exchange or undertaking separate membership requirements (as is required on Cboe Options). Given this ease of access to the GTH trading session, the Exchange believes Market Makers may be encouraged to quote during that trading session. The Exchange believes Market Makers will have an incentive to quote in XSP options during Global Trading Hours given the significance of the S&amp;P 500 Index within the financial markets, the expected demand, and given that the stocks underlying the index are also trading during those hours (which may permit execution of certain hedging strategies). Extending a Market Maker's appointment to Global Trading Hours will enhance liquidity during that trading session, which benefits all investors during those hours. Therefore, the Exchange believes the proposed rule change provides customer trading interest with a net benefit, and continues to maintain a balance of Market Maker benefits and obligations.</P>
                <P>
                    The proposed rule change amends the definitions of all-or-none orders, market orders, stop orders, and stop-limit orders to state that those order types may not be applied to orders designated as All Sessions order (
                    <E T="03">i.e.,</E>
                     all-or-none, market, stop, and stop-limit orders will not be eligible for trading during GTH).
                    <SU>31</SU>
                    <FTREF/>
                     The Exchange expects reduced liquidity, higher volatility, and wider spreads during GTH. Therefore, the Exchange believes it is appropriate to not allow these orders to participate in GTH trading in order to protect customers should wide price fluctuations occur due to the potential illiquid and volatile nature of the market or other factors that could impact market activity.
                    <SU>32</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         The proposed rule change also amends the introductory language to Rule 6.10(c) to provide that certain restrictions on the use of order types may be set forth in the Rules (such as the proposed restrictions on the use of market orders, stop orders, and stop-limit orders during GTH).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         Cboe Options Rule 6.1A(f) also prohibits these orders from participating in GTH trading. Cboe Options Rule 6.1A(f) also prohibits good-til-cancelled orders from participating during GTH. However, because the Exchange will use the same Book for all trading sessions, and thus any GTC orders that do not trade during GTH may become eligible for trading during RTH, the Exchange does not believe it is necessary to restrict use of this time-in-force.
                    </P>
                </FTNT>
                <P>
                    Proposed Rule 21.1(c)(3) provides that no current index value underlying an index option trading during Global Trading Hours will be disseminated during or at the close of that trading session. The value of the underlying index will not be recalculated during or at the close of Global Trading Hours. The closing value of the index from the previous trading day will be available for Options Members that trade during Global Trading Hours. However, the Exchange does not believe it would be useful or efficient to disseminate to Options Members the same value repeatedly at frequent intervals, as it does during Regular Trading Hours 
                    <PRTPAGE P="20924"/>
                    (when that index value is being updated).
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         Rules 29.3(b)(11), 29.6(b)(10), and 29.6(d)(8) provide that underlying index values will be disseminated at least once every 15 seconds. Proposed Rule 21.2(c)(3) supersedes those provisions with respect to Global Trading Hours. Cboe Options Rule 24.3 also states that dissemination of the current index value will occur after the close of Regular Trading Hours (and, thus, not after the close of Global Trading Hours, as no new index value will have been calculated during that trading session) and from time-to-time on days on which transactions are made on the Exchange.
                    </P>
                </FTNT>
                <P>Proposed Rule 17.5 requires Options Members to make certain disclosures to customers regarding material trading risks that exist during Global Trading Hours. The Exchange expects overall lower levels of trading during Global Trading Hours compared to Regular Trading Hours. While trading processes during Global Trading Hours will be substantially similar to trading processes during Regular Trading Hours (as noted above), the Exchange believes it is important for investors, particularly public customers, to be aware of any differences and risks that may result from lower trading levels and thus requires these disclosures. Proposed Rule 17.5 provides that no Options Member may accept an order from a customer for execution during Global Trading Hours without disclosing to that customer that trading during Global Trading Hours involves material trading risks, including the possibility of lower liquidity (including fewer Market-Makers quoting), higher volatility, changing prices, an exaggerated effect from news announcements, wider spreads, the absence of an updated underlying index or portfolio value or intraday indicative value and lack of regular trading in the securities underlying the index or portfolio and any other relevant risk. The proposed rule provides an example of these disclosures. The Exchange believes that requirement Options Members to disclose these risks to non-TPH customers will facilitate informed participation in Global Trading Hours.</P>
                <P>The Exchange also intends to distribute to Options Members and make available on its website a Regulatory Circular regarding Global Trading Hours that discloses, among other things, that (1) the current underlying index value may not be updated during Global Trading Hours, (2) that lower liquidity during Global Trading Hours may impact pricing, (3) that higher volatility during Global Trading Hours may occur, (4) that wider spreads may occur during Global Trading Hours, (5) the circumstances that may trigger trading halts during Global Trading Hours, (6) required customer disclosures (as described above), and (7) suitability requirements. The Exchange believes that, with this disclosure, Global Trading Hours are appropriate and beneficial notwithstanding the absence of a disseminated updated index value during those hours.</P>
                <P>As set forth above, the differences in the Rules between the trading process during RTH and during GTH is that certain order types and instructions will not be available during GTH, no values for indexes underlying index options will be disseminated during GTH, and Options Members that accept orders from customers during GTH will be required to make certain disclosures to those customers. As noted above, other rules will apply in the same manner, but the Exchange may make different determinations between RTH and GTH. The Exchange believes these differences are consistent with the differences between the characteristics of each trading session. The Exchange also notes the following:</P>
                <P>• All Options Members may, but will not be required to, participate during Global Trading Hours. As noted above, while a Market-Maker's appointment to an All Sessions class will apply to that class whether it quotes in series in that class or not during GTH, the Exchange believes any additional burden related to the application of a Market-Maker's quoting obligation to the additional 45 minutes will be de minimis. The Exchange believes even if a Market-Maker elects to not quote during GTH, its ability to satisfy its continuous quoting obligation will not be substantially obligated given the short length of GTH and the few series that will be listed for trading during GTH.</P>
                <P>
                    • The Exchange expects Options Members that want to trading during GTH to have minimal preparation. The Exchange will use the same connection lines, message formats, and feeds during RTH and GTH.
                    <SU>34</SU>
                    <FTREF/>
                     Options Members may use the same ports and EFIDs for each trading session.
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         The same telecommunications lines used by Options Members during Regular Trading Hours may be used during Global Trading Hours, and these lines will be connected to the same application serve at the Exchange during both trading sessions. This is different from Cboe Options, which connects its telecommunications lines to a separate application serve during each trading session.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         An Options Member may elect to have separate ports or EFID for each trading session, but the Exchange will not require that. This is different from Cboe Options, which requires Options Members to use separate log-ins and acronyms (the equivalent of ports and EFIDs) for each trading session.
                    </P>
                </FTNT>
                <P>• The same opening process (as amended below) will be used to open each trading session.</P>
                <P>• Order processing will operate in the same manner during Global Trading Hours as it does during Regular Trading Hours. There will be no changes to the ranking, display, or allocation algorithms rules (as noted above, the Exchange will have authority to apply a different allocation algorithm to a class during Global Trading Hours than it applies to that class during Regular Trading Hours).</P>
                <P>
                    • There will be no changes to the processes for clearing, settlement, exercise, and expiration.
                    <SU>36</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         The Exchange has held discussions with the Options Clearing Corporation, which is responsible for clearance and settlement of all listed options transactions and has informed the Exchange that it will be able to clear and settle all transactions that occur on the Exchange and handle exercises of options during Extended Trading Hours.
                    </P>
                </FTNT>
                <P>
                    • The Exchange will report the Exchange best bid and offer and executed trades to the Options Price Reporting Authority (“OPRA”) during Global Trading Hours in the same manner they are reported during Regular Trading Hours. Exchange proprietary data feeds will also be disseminated during Global Trading Hours using the same formats and delivery mechanisms with which the Exchange disseminates them during Regular Trading Hours. Use of these proprietary data wills during Global Trading Hours will be optional (as they are during Regular Trading Hours).
                    <SU>37</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         Any fees related to receipt of the OPRA data feed during Global Trading Hours will be included on the OPRA fee schedule. Any fees related to receipt of the Exchange's proprietary data feeds during Global Trading Hours will be included on the Exchange's fee schedule (and will be included in a separate rule filing) or the Exchange's market data website, as applicable.
                    </P>
                </FTNT>
                <P>
                    • The same Options Members that are required to maintain connectivity to a backup trading facility during Regular Trading Hours will be required to do so during Global Trading Hours.
                    <SU>38</SU>
                    <FTREF/>
                     Because the same connections and serves will be used for both trading sessions, a Options Member will not be required to take any additional action to comply with this requirement, regardless of whether the Options Member chooses to trade during Global Trading Hours.
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         Currently, Options Members with accounts for 5% or more of the executed volume, measured on a quarterly basis, the Exchange must connect to the Exchange's backup facilities and participate in testing. The same test will be used for all trading sessions. 
                        <E T="03">See</E>
                         EDGX Options Regulatory Circular 18-011 (July 3, 2018); and Rule 2.4.
                    </P>
                </FTNT>
                <P>
                    • The Exchange will process all clearly erroneous trade breaks during Global Trading Hours in the same manner it does during Regular Trading Hours and will have Exchange officials 
                    <PRTPAGE P="20925"/>
                    available to do so (the same officials that do so during Regular Trading Hours).
                </P>
                <P>• The Exchange will perform all necessary surveillance coverage during Global Trading Hours.</P>
                <P>
                    • The Exchange may halt trading during Global Trading Hours in the interests of a fair and orderly market in the same manner it may during Regular Trading Hours pursuant to Rule 29.10 (as proposed to be amended, as described below). The proposed rule change amends current Rule 29.10(e) (proposed Rule 29.10(d)) to provide that during Global Trading Hours, Rule 29.10(a)(1) through (3), (b), and (c) (as proposed) do not apply. As discussed above, Global Trading Hours will not coincide with the hours of trading of the underlying primary securities market. Generally, the Exchange considers halting trading only in response to unusual conditions or circumstances, as it wants to interrupt trading as infrequently as possible and only if necessary to maintain a fair and orderly market. During Regular Trading Hours, it would be unusual, for example, for stocks or options underlying an index to not be trading or the current calculation of the index to not be available. However, as discussed above, there will be no calculation of underlying indexes during Global Trading Hours, and Global Trading Hours do not coincide with the regular trading hours of the underlying stock or options (there may be some overlap with trading of certain underlying stocks, as mentioned above 
                    <SU>39</SU>
                    <FTREF/>
                    ). Thus, the factors described in proposed Rule 29.10(a) are not unusual for Global Trading Hours, and thus the Exchange does not believe it is necessary to consider these as reasons for halting trading during that trading session. Exclusion of Global Trading Hours from those provisions will allow trading during that trading session to occur despite the existence of those conditions (if the Exchange considered the existence of those conditions during Global Trading Hours, trading during Global Trading Hours could be halted every day). It is appropriate for the Exchange to consider any unusual conditions or circumstances detrimental to the maintenance of a fair and orderly market during Global Trading Hours, which may, for example, include whether the underlying primary securities market was halted at the close of the previous trading day (in which case the Exchange will evaluate whether the condition that led to the halt has been resolved or would not impact trading during Global Trading Hours) or significant events that occur during Global Trading Hours.
                    <SU>40</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         
                        <E T="03">See supra</E>
                         note 11.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         The proposed rule change adds reasons to proposed Rule 29.10(e) (current paragraph (f)) why pricing will be determined by OCC. Currently, settlement values are determined by OCC when pricing is not available in these circumstances. The proposed rule change makes corresponding changes to the headings for Rule 29.10(d) and (e).
                    </P>
                </FTNT>
                <P>
                    Pursuant to Rule 20.5(c), the Exchange will halt trading in all options when a market-wide trading halt known as a circuit breaker is initiated on the New York Stock Exchange in response to extraordinary market conditions. Pursuant to the proposed rule change, Rule 20.5(c) will not apply during Global Trading Hours. The Exchange believes that, even if stock trading was halted at the close of the previous trading day, the length of time between that time and the beginning of Global Trading Hours is significant (over 16 hours), and the condition that led to the halt is likely to have been resolved. The proposed rule change allows the Exchange to consider unusual conditions or circumstances when determining whether to halt trading during Global Trading Hours. To the extent a circuit breaker caused a stock market to be closed at the end of the prior trading day, the Exchange could consider, for example, whether it received notice from stock exchanges that trading was expected to resume (or not) the next trading day in determining whether to halt trading during Global Trading Hours. Because the stock markets would not begin trading until after Global Trading Hours opens, the Exchange believes it should be able to open Global Trading Hours rather than waiting to see whether stock markets open to allow investors to participate in Global Trading Hours if the Exchange believes such trading can occur in a fair and orderly manner based on then-existing circumstances, not circumstances that existed numerous hours earlier. Additionally, Cboe Options has the same rule provision.
                    <SU>41</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         
                        <E T="03">See</E>
                         Cboe Options Rule 24.7(d).
                    </P>
                </FTNT>
                <P>
                    Certain rules currently include general phrases related to a day or trading, such as market close. The proposed rule change makes technical changes to Rules 21.1(f)(3) (definition of “Day”), 21.6(b),
                    <SU>42</SU>
                    <FTREF/>
                     21.9, and 21.20(c)(2)(A) to incorporate the terminology included in this proposed rule change to specify the appropriate trading session(s) being referenced in those rules.
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         The proposed rule change modifies the name of Rule 21.6 to account for the fact that it applies to the cancellation, as well as the entry, of orders.
                    </P>
                </FTNT>
                <P>
                    The Exchange will disseminate last sale and quotation information during Global Trading Hours through OPRA pursuant to the Plan for Reporting of Consolidated Options Last Sale Reports and Quotation Information (the “OPRA Plan”), as it does during Regular Trading Hours.
                    <SU>43</SU>
                    <FTREF/>
                     The Exchange will also disseminate an opening quote and trade price through OPRA for Global Trading Hours (as it does for Regular Trading Hours). Therefore, all Options Members that trade during Global Trading Hours will have access to quote and last sale information during that trading session.
                </P>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         The OPRA Plan provides for the collection and dissemination of last sale and quotation information on options that are trading on the participant exchanges. The OPRA Plan is a national market system plan approved by the Commission pursuant to Section 11A of the Act and Rule 608 thereunder. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 17638 (March 18, 1981). The full text of the OPRA Plan is available at 
                        <E T="03">http:www.opradata.com.</E>
                         All operating U.S. options exchanges participate in the OPRA Plan. The operator of OPRA informed the Exchange that it intends to add a modifier to the information disseminated during Global Trading Hours (as it does for Cboe Options).
                    </P>
                </FTNT>
                <P>
                    The Exchange understands that systems and other issues may arise and is committed to resolving those issues as quickly as possible, including during Global Trading Hours. Thus, the Exchange will have appropriate staff on-site and otherwise available as necessary during Global Trading Hours to handle any technical and support issues that may arise during those hours. Additionally, the Exchange will have personnel available to address any trading issues that may arise during Global Trading Hours.
                    <SU>44</SU>
                    <FTREF/>
                     The Exchange is also committed to fulfilling its obligations as a self-regulatory organization at all times, including during Global Trading Hours, and will have appropriately trained, qualified regulatory staff in place during Global Trading Hours to the extent it deems necessary to satisfy those obligations. The Exchange's surveillance procedures will be revised as necessary to incorporate transactions that occur and orders and quotations that are submitted during Global Trading Hours. The Exchange believes its surveillance procedures are adequate to properly 
                    <PRTPAGE P="20926"/>
                    monitor trading of XSP options during Global Trading Hours.
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         The Exchange notes that, to conduct trading during Global Trading Hours, persons that are not Options Members, such as employees of affiliates of Options Members located outside of the United States, may be transmitting orders and quotes during Global Trading Hours (such non-Options Members would not have direct access to the Exchange, and thus those orders and quotes would be submitted to the Exchange through Options Members' systems subject to applicable laws, rules, and regulations). Options Members may authorize (in a form and manner determined by the Exchange) individuals at these non-Options Member entities to contact the Exchange during Global Trading Hours to address any issues.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Opening Process</HD>
                <P>
                    Rule 21.7 sets forth the opening process the Exchange uses to open series on the Exchange at the market open each trading day (and after trading halts). Pursuant to the current opening process, the System determines and opening price for a series based on the NBBO 
                    <SU>45</SU>
                    <FTREF/>
                     and crosses any interest on the book that is marketable at that price. The proposed rule change adopts an opening auction process, substantially similar to the Cboe Options opening auction process.
                    <SU>46</SU>
                    <FTREF/>
                     The Exchange believes an opening auction process will enhance the openings of series on the Exchange by providing an opportunity for price discovery based on then-current market conditions. Pursuant to the proposed opening auction process, the Exchange will have a Queuing Period, during which the System will accept orders and quotes and disseminates expected opening information; will initiate an opening rotation upon the occurrence of certain triggers; will conduct an opening rotation during which the System matches and executes orders and quotes against each other in order to establish an opening Exchange best bid and offer and trade price, if any, for each series, subject to certain price protections; and will open series for trading.
                    <SU>47</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         The opening price (if not outside the NBBO and no more than a specified minimum amount away from the NBBO) is either the midpoint of the NBBO, the last disseminated transaction price after 9:30 a.m., or the last transaction price from the previous trading day. 
                        <E T="03">See</E>
                         current 21.7(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         
                        <E T="03">See</E>
                         Cboe Options Rule 6.2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         The order of events that comprise this proposed opening auction process corresponds to the opening auction process on Cboe Options. 
                        <E T="03">See</E>
                         Cboe Options Rule 6.2.
                    </P>
                </FTNT>
                <P>
                    Proposed Rule 21.7(a) sets forth the definitions of the following terms for purposes of the opening auction process in proposed Rule 21.7: 
                    <SU>48</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         A term defined elsewhere in the Rules has the same meaning with respect to Rule 21.7, unless otherwise defined in Rule 21.7.
                    </P>
                </FTNT>
                <P>
                    • 
                    <E T="03">Composite Market:</E>
                     The term “Composite Market” means the market for a series comprised of (1) the higher of the then-current best appointed Market Maker bulk message bid on the Queuing Book and the away best bid (“ABB”) (if there is an ABB) and (2) the lower of the then-current best appointed Market Maker bulk message offer on the Queuing Book and the away best offer (“ABO”) (if there is an ABO). The term “Composite Bid (Offer)” means the bid (offer) used to determine the Composite Market.
                    <SU>49</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         Cboe Options similarly considers the Exchange's best quote bid and best quote offer when determining whether the Exchange's market is too wide. On Cboe Options, the term “quote” corresponds to the term “bulk message” on the Exchange. Cboe Options also considers quotes from any away markets, if it has activated Hybrid Agency Liaison (“HAL”) at the open. The Exchange has a Step-Up Mechanism (“SUM”) that corresponds to HAL, but does not have it activated at the open as Cboe Options does. However, the Exchange believes considering any quotes from away markets in addition to quotes on its own market when determining whether to open a series will enhance the opening auction price by considering all available pricing information.
                    </P>
                </FTNT>
                <P>
                    • 
                    <E T="03">Composite Width:</E>
                     The term “Composite Width” means the width of the Composite Market (
                    <E T="03">i.e.,</E>
                     the width between the Composite Bid and the Composite Offer) of a series.
                </P>
                <P>
                    • 
                    <E T="03">Maximum Composite Width:</E>
                     The term “Maximum Composite Width” means the amount that the Composite Width of a series may generally not be greater than for the series to open (subject to certain exceptions, as described below). The Exchange determines this amount on a class and Composite Bid basis, which amount the Exchange may modify during the opening auction process (which modifications the Exchange disseminates to all subscribers to the Exchange's data feeds that deliver opening auction updates).
                    <SU>50</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         The Maximum Composite Width corresponds to the opening exchange prescribed width range (“OEPW”) on Cboe Options. 
                        <E T="03">See</E>
                         Cboe Options Rule 6.2(d)(i)(A). The Exchange will determine the Maximum Composite Width in a slightly different manner than Cboe Options determines the OEPW; however, both are based on appointed Market-Maker quotes and are intended to create a reasonable range to ensure the market does not open at extreme prices. Additionally, as proposed, the Maximum Composite Width will factor in away prices in addition to quotes on the Exchange (unlike Cboe Options which considers only quotes on the Exchange).
                    </P>
                </FTNT>
                <P>
                    • 
                    <E T="03">Opening Auction Updates:</E>
                     The term “opening auction updates” means Exchange-disseminated messages that contain information regarding the expected opening of a series based on orders and quotes in the Queuing Book for the applicable trading session and, if applicable, the GTH Book,
                    <SU>51</SU>
                    <FTREF/>
                     including the expected opening price, the then-current cumulative size on each side at or more aggressive than the expected opening price, and whether the series would open (and any reason why a series would not open).
                </P>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         In other words, for the RTH opening auction in an All Sessions class, the expected opening information to be disseminated in opening auction updates prior to the conclusion of the GTH trading session will be based on orders and quotes in the RTH Queuing Book (
                        <E T="03">i.e.,</E>
                         RTH Only orders) and in the GTH Book (
                        <E T="03">i.e.,</E>
                         All Sessions orders).
                    </P>
                </FTNT>
                <P>
                    • 
                    <E T="03">Opening Collar:</E>
                     The term “Opening Collar” means the price range that establishes limits at or inside of which the System determines the Opening Trade Price for a series. The Exchange determines the width of this price range on a class and Composite Bid basis, which range the Exchange may modify during the opening auction process (which modifications the Exchange disseminates to all subscribers to the Exchange's data feeds that deliver opening auction updates.
                    <SU>52</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         Cboe Options uses the OEPW as the range within which the opening price must be. 
                        <E T="03">See</E>
                         Cboe Options Rule 6.2(d)(i)(C). The Exchange will determine the Opening Collar in a slightly different manner than Cboe Options determines the OEPW; however, both are based on appointed Market-Maker quotes and are intended to create a reasonable range to ensure the market does not open at extreme prices. Additionally, as proposed, the Opening Collar will factor in away prices in addition to quotes on the Exchange (unlike Cboe Options which considers only quotes on the Exchange).
                    </P>
                </FTNT>
                <P>
                    • 
                    <E T="03">Opening Trade Price:</E>
                     The term “Opening Trade Price” means the price at which the System executes opening trades in a series during the opening rotation.
                    <SU>53</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         
                        <E T="03">See</E>
                         current Rule 21.7(c).
                    </P>
                </FTNT>
                <P>
                    • 
                    <E T="03">Queuing Book:</E>
                     The term “Queuing Book” means the book into which Users may submit orders and quotes (and onto which GTC and GTD orders remaining on the Book from the previous trading session or trading day, as applicable, are entered) during the Queuing Period for participation in the application opening rotation.
                    <SU>54</SU>
                    <FTREF/>
                     Orders and quotes on the Queuing Book may not execute until the opening rotation. The Queuing Book for the GTH opening auction process may be referred to as the “GTH Queuing Book,” and the Queuing Book for the RTH opening auction process may be referred to as the “RTH Queuing Book.”
                </P>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         In other words, at 7:30 a.m., All Sessions orders will rest on the GTH Queuing Book and be eligible to participate in the GTH opening auction process, and RTH Only orders will rest on the RTH Queuing Book and be eligible to participate in the RTH opening auction process.
                    </P>
                </FTNT>
                <P>
                    • 
                    <E T="03">Queuing Period:</E>
                     The term “Queueing Period” means the time period prior to the initiation of an opening rotation during which the System accepts orders and quotes for participation in the opening rotation for the applicable trading session.
                    <SU>55</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         
                        <E T="03">See</E>
                         current Rule 21.7(a)(1) (the current rule does not use the term “Queuing Period”; however, it does provide for an order entry period prior to the opening of a series during which the System accepts orders and quotes). The proposed rule change moves the rule provisions regarding the opening process following a halt to proposed paragraph (g), with no substantive changes.
                    </P>
                </FTNT>
                <P>
                    Proposed paragraph (b) describes the Queuing Period. The Queuing Period begins at 7:30 a.m. for all class.
                    <SU>56</SU>
                    <FTREF/>
                     This is the same time at which the System begins accepting orders and quotes today. Therefore, Users will have the same amount of time to submit orders and quotes prior to the RTH opening. 
                    <PRTPAGE P="20927"/>
                    Additionally, Users will have one hour to submit orders and quotes in GTH classes prior to the GTH opening. The Exchange believes this is sufficient given that the Exchange will list fewer classes (one class, as proposed) during GTH.
                    <SU>57</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         
                        <E T="03">See</E>
                         proposed Rule 21.7(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>57</SU>
                         Pursuant to Cboe Options Rule 6.2(a), the pre-opening period (equivalent to the proposed Queuing Period) begins no earlier than 2:00 a.m. Central time for regular trading hours and no later than 4:00 p.m. on the previous day for global trading hours (as global trading hours on Cboe Options begins at 2:00 a.m. Central time). The Exchange does not propose to have flexibility as Cboe Options has, and believes the proposed time period for the Queuing Period is sufficient.
                    </P>
                </FTNT>
                <P>Proposed subparagraph (b)(2) clarifies that orders and quotes on the Queuing Book are not eligible for execution until the opening rotation pursuant to proposed paragraph (e), as described below. This is consistent with current order entry period, pursuant to which orders and quotes entered for inclusion in the opening process do not execute until the opening trade pursuant to current paragraph (d). The System accepts all orders and quotes that are available for a class and trading session pursuant to Rule 21.1 during the Queuing Period, which are eligible for execution during the opening rotation, except as follows:</P>
                <P>
                    • the System rejects IOC and FOK orders during the Queuing Period; 
                    <SU>58</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>58</SU>
                         
                        <E T="03">See</E>
                         current paragraph (a) and proposed subparagraph (a)(2)(A); 
                        <E T="03">see also</E>
                         Cboe Options Rule 6.2(a)(i).
                    </P>
                </FTNT>
                <P>
                    • The System accepts orders and quotes with MTP Modifiers during the Queuing Period, but does not enforce them during the opening rotation; 
                    <SU>59</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>59</SU>
                         
                        <E T="03">See</E>
                         proposed subparagraph (a)(2)(B). This is consistent with current functionality, and the detail is being added to the Rules. 
                        <E T="03">See also</E>
                         C2 Rule 6.11(a)(1). Cboe Options has Market-Maker trade prevention orders, which it does not accept prior to the opening. 
                        <E T="03">See</E>
                         Cboe Options Rule 6.2(a)(i).
                    </P>
                </FTNT>
                <P>
                    • the System accepts all-or-none, stop, and stop-limit orders 
                    <SU>60</SU>
                    <FTREF/>
                     during the Queuing Period, but they do not participate during the opening rotation. The System enters any of these orders it receives during the Queuing Period into the Book following completion of the opening rotation (in time priority); 
                    <SU>61</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>60</SU>
                         Pursuant to Rule 21.1(d)(11) and (12), stop and stop-limit orders are triggered based on the consolidated last sale price. Not participating in the opening process is consistent with this requirement, as the Exchange needs to be open (and thus have an opening trade occur) in order for there to be a consolidated last sale price that can trigger these orders. Current Rule 21.7(a) provides that all-or-none orders do not participate in the opening process.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>61</SU>
                         This is consistent with current functionality, and the proposed rule change is adding this detail to the Rules. 
                        <E T="03">See also</E>
                         Cboe Options Rule 6.2(c)(i)(B) (which states that order with a stop contingency do not participate in the opening rotation).
                    </P>
                </FTNT>
                <P>
                    • the System converts all ISOs received prior to the completion of the opening rotation into non-ISOs; 
                    <SU>62</SU>
                    <FTREF/>
                     and
                </P>
                <FTNT>
                    <P>
                        <SU>62</SU>
                         
                        <E T="03">See</E>
                         current paragraph (a) and proposed subparagraph (a)(2)(D); 
                        <E T="03">see also</E>
                         Cboe Options Rule 6.2(a)(i) (which does not permit ISOs to be entered during the Cboe Options pre-opening period).
                    </P>
                </FTNT>
                <P>
                    • complex orders do not participate in the opening auction described in Rule 21.7 and instead may participate in the COB Opening Process pursuant to Rule 21.20(c)(2)(A).
                    <SU>63</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>63</SU>
                         
                        <E T="03">See</E>
                         Rule 21.20(c)(2)(A) and proposed subparagraph (a)(2)(E); 
                        <E T="03">see also</E>
                         Cboe Options Rule 6.2(c)(i)(B).
                    </P>
                </FTNT>
                <P>
                    Proposed paragraph (c) describes the opening auction updates the Exchange will disseminate as part of the opening auction process. As noted above, opening auction updates contain information regarding the expected opening of a series. These messages provide market participants with information that may contribute to enhanced liquidity and price discovery during the opening auction process. Beginning at a time (determined by the Exchange) no earlier than one hour prior to the expected initiation of the opening rotation for a trading session and until the conclusion of the opening rotation for a series, the Exchange disseminates opening auction updates for the series.
                    <SU>64</SU>
                    <FTREF/>
                     The Exchange disseminates opening auction updates at regular intervals of time (the length of which the Exchange determines for each trading session), or less frequently if there are no updates to the opening information since the previously disseminated update, to all subscribers to the Exchange's data feeds that deliver these messages until a series opens.
                    <SU>65</SU>
                    <FTREF/>
                     If there have been no changes since the previous update, the Exchange does not believe it is necessary to disseminate duplicate updates to market participants at the next interval of time.
                </P>
                <FTNT>
                    <P>
                        <SU>64</SU>
                         The Exchange only begins disseminating updates for series with locked or crossed interest or if the series needs Market Maker bulk messages. There can only be an expected opening price to disseminate if these conditions have been met, and thus no updates will be disseminated if these conditions do not exist. 
                        <E T="03">See also</E>
                         Cboe Options Rule 6.2(a)(ii) (which provides that Cboe Options may begin disseminated expected opening information (“EOIs”) messages (which correspond to opening auction updates)). Cboe Options currently begins disseminating EOIs at 7:30 a.m. or 8:00 a.m. Central time (depending on the class), which is consistent with the proposed rule change to begin dissemination of opening auction messages no earlier than one hour prior to the expected initiation of the opening rotation for a series. The Exchange believes market participants generally want to receive this information closer to the opening of trading.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>65</SU>
                         
                        <E T="03">See also</E>
                         Cboe Options Rule 6.2(a)(ii) (Cboe Options will similarly disseminate EOIs at regular intervals or less frequently if there are no updates, and will not disseminate EOIs in certain circumstances, including if there is no locked or crossed interest (because there would be no expected opening price or size)).
                    </P>
                </FTNT>
                <P>
                    Proposed paragraph (d) describes the events that will trigger the opening rotation for a class. Pursuant to current paragraph (b), the System will automatically open a related equity option series after the first transaction on the primary listing market after 9:30 a.m. in the securities underlying the options as reported on the first print disseminated pursuant to an effective national market system plan (with respect to equity options). Pursuant to current paragraph (c), the System automatically opens a related index option series after an away options exchange(s) disseminates a quote in an index option series (with respect to index options). As proposed for Regular Trading Hours, after a time period (which the Exchange determines for all classes) following the System's observation after 9:30 a.m. of the first disseminated (1) transaction price for the security underlying an equity option or (2) index value for the index underlying an index option, the System will initiate the opening rotation for the series in that class, and the Exchange disseminates message to market participants indicating the initiation of the opening rotation.
                    <SU>66</SU>
                    <FTREF/>
                     For Global Trading Hours, the System will initiate the opening rotation at 8:30 a.m.
                    <SU>67</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>66</SU>
                         Pursuant to current paragraphs (b) and (c), the opening is currently triggered upon the occurrence of similar events. While not specified in the current Rules, pursuant to current functionality, the System waits for a certain time period following the occurrence of such an event to open a series. 
                        <E T="03">See also</E>
                         C2 Rule 6.11(a)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>67</SU>
                         
                        <E T="03">See also</E>
                         Cboe Options Rule 6.2(b). Unlike Cboe Options, the opening rotation will be triggered in all equity classes by observation of the first transaction in the underlying security (rather than some classes being triggered by a timer), and the opening rotation will be triggered in all index classes by observation of the first index value (rather than some classes being triggered by a timer). The Exchange does not believe it needs this flexibility.
                    </P>
                </FTNT>
                <P>
                    Proposed paragraph (e) describes the opening rotation process, during which the System will determine whether the Composite Market for a series is not wider than a maximum width, will determine the opening price, and open series.
                    <SU>68</SU>
                    <FTREF/>
                     The Maximum Composite Width Check and Opening Collar are intended to ensure that series open in a fair and orderly manner and at prices consistent with the current market 
                    <PRTPAGE P="20928"/>
                    conditions for the series and not at extreme prices, while taking into consideration prices disseminated from other options exchanges that may be better than the Exchange's at the open.
                </P>
                <FTNT>
                    <P>
                        <SU>68</SU>
                         
                        <E T="03">See also</E>
                         Cboe Options Rule 6.2(d) (pursuant to which Cboe Options will generally not open a series if the width is wider than an acceptable price range or if the opening trade price is outside of an acceptable price range). The Exchange will similarly have a maximum quote width and acceptable opening price range, however, they may be calculated differently. Cboe Options has additional opening conditions that the Exchange does not propose to adopt.
                    </P>
                </FTNT>
                <P>Proposed subparagraph (e)(1) describes the Maximum Composite Width Check.</P>
                <P>• If the Composite Width of a series is less than or equal to the Maximum Composite Width, the series is eligible to open (and the System determines the Opening Price as described below).</P>
                <P>
                    • If the Composite Width of a series is greater than the Maximum Composite Width, but there are no non-M Capacity 
                    <SU>69</SU>
                    <FTREF/>
                     market orders or buy (sell) limit orders with prices higher (lower) than the Composite Bid (Offer) and there are no locked or crossed orders or quotes, the series is eligible to open (and the System determines the Opening Price as described below).
                </P>
                <FTNT>
                    <P>
                        <SU>69</SU>
                         Capacity M is used for orders for the account of a Market Maker (with an appointment in the class). 
                        <E T="03">See</E>
                         U.S. Options Binary Order Entry Specifications, at 28 (definition of Capacity), available at 
                        <E T="03">http://cdn.cboe.com/resources/membership/US_Options_BOE_Specification.pdf.</E>
                    </P>
                </FTNT>
                <P>
                    • If neither of the conditions above are satisfied for a series, the series is ineligible to open. The Queuing Period for the series continues (including the dissemination of opening auction updates) until one of the above conditions for the series is satisfied.
                    <SU>70</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>70</SU>
                         
                        <E T="03">See</E>
                         Cboe Options Rule 6.2(c)(iii) (pursuant to which the opening rotation period on Cboe Options continues, including dissemination of EOIs, until the opening conditions are satisfied). The Exchange may also open a series pursuant to current paragraph (f) (proposed paragraph (h)), which permits the Exchange to deviate from the standard manner of the opening auction process, including adjusting the timing of the opening rotation in any class, modifying any time periods described in Rule 6.11, and delaying or compelling the opening of a series if the opening width is wider than Maximum Width, when it believes it is necessary in the interests of a fair and orderly market. The proposed rule change specifies additional ways in which the Exchange may deviate from the standard of opening (which it has the authority to do under the current rule). 
                        <E T="03">See also</E>
                         Cboe Options Rule 6.2(e) (pursuant to which Cboe Options may deviate from the standard manner of the opening auction process for the same reasons). Pursuant to the proposed rule change, the Exchange will make and maintain records to document all determinations to deviate from the standard manner of the opening auction process, and periodically reviews these determinations for consistency with the interests of a fair and orderly market (which, while not specified in the current Rules, the Exchange does today).
                    </P>
                </FTNT>
                <P>
                    The Exchange will use the Maximum Composite Width Check as a price protection measure to prevent orders from executing at extreme prices at the open. If the width of the Composite Market (which represents the best market, as it is comprised of the better of Market Maker bulk messages on the Exchange or any away market quotes) is no greater than the Maximum Composite Width, the Exchange believes it is appropriate to open a series under these circumstances and provide marketable orders with an opportunity to execute at a reasonable opening price (as discussed below), because there is minimal risk of execution at an extreme price. However, if the Composite Width is greater than the Maximum Composite Width but there are no non-M Capacity orders 
                    <SU>71</SU>
                    <FTREF/>
                     that lock or cross the opposite-side widest point of the Composite Market (and thus not marketable at a price at which the Exchange would open, as described below), there is similarly no risk of an order executing at an extreme price on the open. Because the risk that the Maximum Composite Width Check is intended to address is not present in this situation, the Exchange believes it is appropriate to open a series in either of these conditions. However, if neither of these conditions is satisfied, the Exchange believes there may be risk that orders would execute at an extreme price if the series open, and therefore the Exchange will not open a series.
                </P>
                <FTNT>
                    <P>
                        <SU>71</SU>
                         Market Maker bulk messages are considered when determining the Composite Market. The Exchange believes it is appropriate to consider Market-Maker bulk messages when determining an opening quote to ensure there will be liquidity in a series when it opens. Additionally, while it is possible for Market Makers to submit M orders, the Exchange believes there is less risk of a Market Maker inputting an order at an extreme price given that Market Makers are generally responsible for pricing the market.
                    </P>
                </FTNT>
                <P>Proposed subparagraph (e)(2) describes how the System determines the Opening Trade Price for a series after it satisfies the Maximum Composite Width Check described above.</P>
                <P>• The Opening Trade Price is the price that is not outside the Opening Collar and:</P>
                <P>
                    ○ The price at which the largest number of contracts can execute (
                    <E T="03">i.e.,</E>
                     the volume-maximizing price);
                </P>
                <P>
                    ○ if there are multiple volume-maximizing prices, the price at which the fewest number of contracts remain unexecuted (
                    <E T="03">i.e.,</E>
                     the imbalance-minimizing price); or
                </P>
                <P>○ if there are multiple volume-maximizing, imbalance-minimizing prices, (1) the highest (lowest) price, if there is a buy (sell) imbalance, or (2) the price at or nearest to the midpoint of the Opening Collar, if there is no imbalance.</P>
                <P>
                    • There is no Opening Trade Price if there are no locked or crossed orders or quotes at a price not outside the Opening Collar.
                    <SU>72</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>72</SU>
                         
                        <E T="03">See</E>
                         current Rule 21.7(e).
                    </P>
                </FTNT>
                <P>
                    The Exchange believes the proposed volume-maximizing, imbalance-minimizing procedure is reasonable, as it will provide for the largest number of contracts in the Queuing Book that can execute, leaving as few as possible bids and offers in the Book that cannot execute.
                    <SU>73</SU>
                    <FTREF/>
                     The Exchange will use the Opening Collar as a price protection measure to prevent orders from executing at extreme prices at the open. If the Opening Trade Price is not outside the Opening Collar (which will be based on the best then-current market), the Exchange believes it is appropriate to open a series at that price, because there is minimal risk of execution at an extreme price. However, if the Opening Trade Price would be outside of the Opening Collar, the Exchange believes there may be risk that orders would execute at an extreme price if the series open, and therefore the Exchange will not open a series.
                </P>
                <FTNT>
                    <P>
                        <SU>73</SU>
                         
                        <E T="03">See also</E>
                         Cboe Options Rule 6.2(c)(i)(A) (pursuant to which Cboe Options will open at the market-clearing price, and if there are multiple prices at which the same number of contracts would clear, Cboe Options will use similar tie-breakers).
                    </P>
                </FTNT>
                <P>The following examples show the application of the Maximum Composite Width Check:</P>
                <HD SOURCE="HD3">Example #1</HD>
                <P>Suppose the Maximum Composite Width for a class is 0.50, and the Composite Market is 1.00 × 2.00, comprised of an appointed Market Maker bulk message bid of 2.00 and an appointed Market Maker bulk message offer of 1.00. There is no other interest in the Queuing Book. The series is not eligible to open, because the width of the Composite Market is greater than the Maximum Composite Width but there are locked orders or quotes in the series. The Queuing Period for the series will continue until the series satisfies the Maximum Composite Width Check.</P>
                <HD SOURCE="HD3">Example #2</HD>
                <P>Suppose the Maximum Composite Width for a class is 0.50, and the Composite Market is 1.00 × 2.00, comprised of an appointed Market Maker bulk message bid of 1.00 and an appointed Market Maker bulk message offer of 2.00. There is no other interest in the Queuing Book. The series is eligible to open, because the width of the Composite Market is greater than the Maximum Composite Width and there are no locked orders or quotes in the series or non-M Capacity orders. The System will then determine the Opening Trade Price.</P>
                <HD SOURCE="HD3">Example #3</HD>
                <P>
                    Suppose the Maximum Composite Width for a class is 0.50, and the 
                    <PRTPAGE P="20929"/>
                    Composite Market is 1.00 × 2.00, comprised of an appointed Market Maker bulk message bid of 1.00 and an appointed Market-Maker bulk message offer of 2.00. There is a non-M Capacity limit order to buy for $1.99 in Queuing Book. The series is not eligible to open, because the width of the Composite Market is greater than the Maximum Composite Width, and there is a non-M Capacity order at a price inside of the Composite Market. The Queuing Period for the series will continue until the series satisfies the Maximum Composite Width Check.
                </P>
                <P>
                    Pursuant to proposed subparagraph (e)(3), if the System establishes an Opening Trade Price, the System will execute orders and quotes in the Queuing Book at the Opening Trade Price. The System will prioritize orders and quotes in the following order: Market orders, limit orders and quotes with prices better than the Opening Trade Price, and orders and quotes at the Opening Trade Price.
                    <SU>74</SU>
                    <FTREF/>
                     The System allocates orders and quotes at the same price pursuant to the allocation algorithm that applies to a class intraday (in accordance with Rule 21.8), unless the Exchange determines to apply a different allocation algorithm from Rule 21.8 to a class during the opening rotation.
                    <SU>75</SU>
                    <FTREF/>
                     If there is no Opening Trade Price, the System opens a series without a trade.
                </P>
                <FTNT>
                    <P>
                        <SU>74</SU>
                         
                        <E T="03">See</E>
                         current Rule 21.7(d) (which states the System matches (in accordance with Rule 21.8) orders and quotes in the System priced equal to or more aggressively than the Opening Price); 
                        <E T="03">see also</E>
                         Cboe Options Rule 6.2(c)(i)(C). The Exchange believes it is appropriate to prioritize orders with the most aggressive prices, as it provides market participants with incentive to submit their best-priced orders.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>75</SU>
                         
                        <E T="03">See</E>
                         Cboe Options Rule 6.2, Interpretation and Policy .04. While the allocation algorithm used during the opening rotation for a class will default to and generally be the same as the one used for that class intraday, the Exchange believes the flexibility is appropriate so that it can facilitate a robust opening with sufficient liquidity in all classes. Cboe Options may apply a different allocation algorithm for series that open at a minimum price increment due to a sell market order imbalance. The Exchange does not believe it needs this flexibility.
                    </P>
                </FTNT>
                <P>
                    Pursuant to proposed subparagraph (f), as is the case today, following the conclusion of the opening rotation, the System enters any unexecuted orders and quotes (or remaining portions) from the Queuing Book into the EDGX Options Book in time sequence (subject to a User's instructions—for example, a User may cancel an order), where they may be processed in accordance with Rule 21.8.
                    <SU>76</SU>
                    <FTREF/>
                     Consistent with the OPG contingency (and current functionality), the System cancels any unexecuted OPG orders (or remaining portions) following the conclusion of the opening rotation.
                </P>
                <FTNT>
                    <P>
                        <SU>76</SU>
                         The proposed rule change corrects an error in the current Rule, which references Rule 21.9 rather than Rule 21.8.
                    </P>
                </FTNT>
                <P>
                    The proposed rule change adds paragraph (i), which provides if the underlying security for a class is in a limit up-limit down state when the opening rotation begins for that class, then the System cancels or rejects all market orders. In addition, if the opening rotation has already begun for a class when a limit up-limit down state initiates for the underlying security of that class, market and limit orders will continue through the end of the opening rotation.
                    <SU>77</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>77</SU>
                         This is consistent with the definition of market orders in Rule 21.1(d). 
                        <E T="03">See also</E>
                         C2 Rule 6.11(d); and Cboe Options Rule 6.2, Interpretation and Policy .07.
                    </P>
                </FTNT>
                <P>
                    Currently, if an order enters the Book following the Opening Process (which would include any GTC or GTD orders that reenter the Book from the prior trading day) and becomes subject to the drill-through protection pursuant to Rule 21.17(d), the NBO (NBB) that existed at the time it enters (or reenters) the Book would be used when determining the drill-through price. Proposed Rule 21.17(d)(1) provides that if an order that enters the EDGX Options Book following the Opening Auction Process and becomes subject to the drill-through protection, the bid (offer) limit of the Opening Collar plus (minus) the buffer amount will be the drill-through price.
                    <SU>78</SU>
                    <FTREF/>
                     As discussed above, the Opening Collar is a price protection, and the Exchange would execute orders at the open at prices at or within the Opening Collar (as it would execute orders at or within the NBBO). Therefore, the Exchange believes the Opening Collar limit price points are reasonable to use when determining the drill-through price for orders that are unable to execute during the opening rotation.
                </P>
                <FTNT>
                    <P>
                        <SU>78</SU>
                         The proposed rule change makes corresponding changes to proposed Rule 21.17(d)(2).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Other Changes</HD>
                <P>
                    Proposed Rule 16.3 states the Exchange announces to Trading Permit Holders all determinations it makes pursuant to the Rules via (a) specifications, Notices, or Regulatory Circulars with appropriate advanced notice, which will be posted on the Exchange's website, or as otherwise provided in the Rules, (b) electronic message, or (c) other communication method as provided in the Rules. Current Rules state the Exchange will generally announce determinations by Regulatory Circular, and the proposed rule expands the different type of documents that may be used to announce determinations, consistent with EDGX. Proposed Rule 16.3 makes clear this information will be available on the Exchange's website in an easily accessible manner, regardless of the manner in which the Exchange announces it. Additionally, certain determinations are made more real-time pursuant to electronic message received by Options Members. This single rule simplifies the Rules by eliminating the need to repeatedly state in the rules how the Exchange will announce determinations.
                    <SU>79</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>79</SU>
                         Proposed Rule 16.3 is the same as C2 Rule 1.2.
                    </P>
                </FTNT>
                <P>The proposed rule change adds Rule 21.2(a), which states the System accepts orders and quotes at the times set forth in Rule 21.6. This is consistent with the provisions in current Rule 21.6, and will help consolidate all rules regarding hours into a single rule.</P>
                <P>
                    Current Rule 21.2(c) states the Exchange will not be open for business on any holiday observed by the Exchange. Proposed Rule 21.2(d) lists all of the holidays on which the Exchange will not be open for business, and describes on which day the Exchange will not be open if a holiday observed falls on a Saturday or Sunday.
                    <SU>80</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>80</SU>
                         Proposed Rule 21.2(c) is the same as C2 Rule 6.1(c).
                    </P>
                </FTNT>
                <P>
                    The proposed rule change permits the Exchange to designate certain index options to end trading at 4:00 p.m.
                    <SU>81</SU>
                    <FTREF/>
                     The Exchange believes this flexibility is appropriate, for example, if it were to list for trading an index option for which it expected investors to use the prices of underlying stocks rather than corresponding index futures to price the index options, and those stocks end trading at 4:00 p.m. The proposed rule change moves rule provisions from current Rules 29.10(a) 
                    <SU>82</SU>
                    <FTREF/>
                     and 29.11(j)(4) regarding index option trading hours into proposed Rule 21.2(b)(2) so that all rule provisions regarding trading hours are included in the same rule.
                    <SU>83</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>81</SU>
                         
                        <E T="03">See</E>
                         proposed Rule 21.2(b)(2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>82</SU>
                         The proposed rule change modifies the name of Rule 29.10, as it only applies to trading halts as proposed.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>83</SU>
                         The proposed rule change makes corresponding changes to paragraph lettering in Rule 29.10.
                    </P>
                </FTNT>
                <P>
                    The Exchange also proposes to clarify that only options on Fund Shares and Index-Linked Securities designated by the Exchange would remain open beyond 4:00 p.m. but no later than 4:15 p.m.
                    <SU>84</SU>
                    <FTREF/>
                     Because Fund Shares and Index-Linked Securities are often based on the same indexes on which the Exchange lists options, and the rules permit index 
                    <PRTPAGE P="20930"/>
                    options to trade until 4:00 p.m. or 4:15 p.m., the Exchange believes it is appropriate to have similar flexibility with respect to the Regular Trading Hours of options on Fund Shares and Index-Linked Securities. Other options exchanges have similar flexibility regarding trading hours.
                    <SU>85</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>84</SU>
                         
                        <E T="03">See</E>
                         proposed Rule 21.2(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>85</SU>
                         
                        <E T="03">See, e.g.,</E>
                         C2 Rule 6.1(a).
                    </P>
                </FTNT>
                <P>Proposed Rule 21.6(f) states after the RTH market close, Users may cancel orders with Time-in-Force of GTC or GTC that remain on the Book until 4:45 p.m. This proposed change provides Users with additional flexibility to manage their orders that remain in the Book following the market close. Cancelling a GTC or GTD order at 4:30 p.m. has the same effect as cancelling that order at 7:30 a.m. the following day—ultimately, it accommodates the User's goal of cancelling an order prior to it potentially executing during the Opening Auction Process the following morning.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes the proposed rule change is consistent with the Securities Exchange Act of 1934 (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>86</SU>
                    <FTREF/>
                     Specifically, the Exchange believes the proposed rule change is consistent with the Section 6(b)(5) 
                    <SU>87</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>88</SU>
                    <FTREF/>
                     requirement that the rules of an exchange not be designed to permit unfair discrimination between customers, issuers, brokers, or dealers.
                </P>
                <FTNT>
                    <P>
                        <SU>86</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>87</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>88</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>In particular, the proposed rule change to adopt Global Trading Hours will remove impediments to and perfect the mechanism of a free and open market and a national market system. Global Trading Hours is a competitive initiative designed to improve the Exchange's marketplace for the benefit of investors. The proposed rule change provides a new investment opportunity within the options trading industry that is consistent with the continued globalization of the securities markets and closer aligns the Exchange's trading hours with extended trading hours of stock exchanges. The Exchange believes the proposed rule change will enhance competition by providing a service to investors that most other options exchanges currently are not providing. The Exchange believes the competition among exchanges ultimately benefits the entire marketplace. Given the robust competition among the options exchanges, innovative trading mechanisms are consistent with the above-mentioned goals of the Exchange Act.</P>
                <P>The proposed rule change also provides a mechanism for the Exchange to more effectively compete with exchanges located outside of the United States. Global markets have become increasingly interdepending and linked, both psychologically and through improved communications technology. This has been accompanied by an increased desire among investors to have access to U.S.-listed exchange products outside of Regular Trading Hours, and the Exchange believes this desire extends to its exclusively listed products. The Exchange believes that the proposed rule change is reasonably designed to provide an appropriate mechanism for trading outside of Regular Trading Hours while providing for appropriate Exchange oversight pursuant to the Act, trade reporting, and surveillance.</P>
                <P>While only one other options exchange is currently open for trading outside of Regular Trading Hours, the Commission has authorized stock exchanges to be open for trading outside of these hours pursuant to the Act. Additionally, futures exchanges also operate outside of those hours. Thus, the proposed rule change to adopt Global Trading Hours is not novel or unique. The Exchange has currently authorized one class to list for trading during Global Trading Hours. As the proposed rule change is a new Exchange initiative, the Exchange believes it is reasonable to trade a limited number of classes upon implementation for which demand is believed to be the highest during Global Trading Hours.</P>
                <P>The vast majority of the Exchange's trading rules will apply during Global Trading Hours in the same manner as during Regular Trading Hours, which rules have all be previously filed with the Commission as being consistent with the goals of the Act. Rules that will apply equally during Global Trading Hours include rules that protect public customers, impose best execution requirements on Options Members, and prohibit acts and practices that are inconsistent with just and equitable principles of trade as well as fraudulent and manipulative practices. The proposed rule change also provides opportunities for price improvement during Global Trading Hours and applies the same allocation and priority rules that are available to the Exchange during Regular Trading Hours. The Exchange believes, therefore, that the rules that will apply during Global Trading Hours will continue to promote just and equitable principles of trade and prevent fraudulent and manipulative acts.</P>
                <P>The proposed rule change clearly identifies the ways in which trading during Regular Trading Hours will different from trading during Global Trading Hours (such as identifying order types and instructions that will not be available during Global Trading Hours). This ensures that investors are aware of any differences among trading sessions. The Exchange believes the differences are consistent with the expected differences in liquidity, participation, and trading activity between Regular Trading Hours and Global Trading Hours. The flexibility provided to the Exchange to make determinations for each trading session will allow the Exchange to apply settings and parameters to address the different market conditions that may be present during each trading session. Additionally, to further protect investors from any additional risks related to trading during Global Trading Hours, the proposed rule change requires that disclosures be made to customers describing these potential risks. The proposed All Sessions order and RTH Only order will protect investors by permitting investors who do not wish to trade during Global Trading Hours from having orders or quotes execute during those orders. Consistent with the goal of investor protection, the Exchange will not allow market orders during Global Trading Hours due to the expected increased volatility and decreased liquidity during these hours.</P>
                <P>
                    Additionally, the Exchange believes that the proposed rule change will foster cooperation and coordination with persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in securities, as the Exchange will ensure that adequate staffing is available during Global Trading Hours to provide appropriate trading support during those hours, as well as Exchange officials to make any necessary 
                    <PRTPAGE P="20931"/>
                    determinations under the rules during Global Trading Hours (such as trading halts and trade nullification for obvious errors). The Exchange is also committed to fulfilling its obligations as a self-regulatory organization at all times, including during Global Trading Hours. The Exchange's surveillance procedures will also be revised to incorporate transactions that occur and orders and quotations that are submitted during Global Trading Hours. The Exchange believes its surveillance procedures are adequate to properly monitor trading in XSP options during Global Trading Hours. Clearing and settlement processes will be the same for Global Trading Hours as they are for Regular Trading Hours transactions.
                </P>
                <P>The proposed rule change further removes impediments to a free and open market and does not unfairly discriminate among market participants, as all Options Members with access to the Exchange may trade during Global Trading Hours using the same connection lines, message formats data feeds, and EFIDs they use during Regular Trading Hours, minimizing any preparation efforts necessary to participate during Global Trading Hours. Options Members will not be required to trade during Global Trading Hours.</P>
                <P>As demonstrated above, while the proposed rule change increases the total time during which a Market Maker with XSP appointment must quote, this increase is de minimis given that a Market Maker's compliance with its continuous quoting obligation is based on all classes in which it has an appointment in the aggregate. Selecting an appointment in XSP options will be optional and within the discretion of a Market Maker. Additionally, the Exchange is providing Market Makers with the opportunity to quote during GTH (and receive the benefits of acting as a Market Maker with respect to transactions it effects during that time) without creating additional connections to the Exchange or undertaking separate membership requirements (as is required on Cboe Options). The Exchange believes Market Makers will have an incentive to quote in XSP options during Global Trading Hours given the significance of the S&amp;P 500 Index within the financial markets, the expected demand, and given that the stocks underlying the index are also trading during those hours (which may permit execution of certain hedging strategies). Extending a Market Maker's appointment to Global Trading Hours will enhance liquidity during that trading session, which benefits all investors during those hours. The Exchange believes that the slight additional burden of extending the continuous quoting obligation to the GTH trading session in one class is outweighed by the Exchange's efforts to add liquidity in All Sessions classes, the minimal preparation a Market Maker may require to participate in the GTH trading session, and the benefits to investors that may result from that liquidity. Therefore, the Exchange believes the proposed rule change provides customer trading interest with a net benefit, and continues to maintain a balance of Market Maker benefits and obligations.</P>
                <P>
                    The proposed rule change is also consistent with Section 11A of the Act and Regulation NMS thereunder, because it provides for the dissemination of transaction and quotation information during Global Trading Hours through OPRA, pursuant to the OPRA Plan, which Commission approved and indicated to be consistent with the Act. While Section 11A and Regulation NMS contemplate an integrated system for trading securities, they also envision competition between markets, and innovation that provides marketplace benefits to attract order flow to an exchange does not result in unfair competition if other markets are free to compete in the same manner.
                    <SU>89</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>89</SU>
                         
                        <E T="03">See</E>
                         Exchange Act Release Nos. 73704 (November 28, 2014), 79 FR 72044 (December 4, 2014) (SR-CBOE-2014-062) (approval of proposed rule change for Cboe Options to extend its trading hours outside of Regular Trading Hours); and 29237 (May 24, 1991), 46 FR 24853 (May 31, 1991) (SR-NYSE-1990-052 and SR-NYSE-1990-053) (approval of proposed rule change for NYSE to extend its trading hours outside of Regular Trading Hours). The Exchange also notes that no other U.S. options exchange provides for trading XSP options outside of Regular Trading Hours, so there is currently no need for intermarket linkage during Global Trading Hours. If another Cboe Affiliated Exchange lists XSP options outside of Regular Trading Hours, trading of XSP options on the Exchange would comply with linkage rules.
                    </P>
                </FTNT>
                <P>
                    The proposed rule change will remove impediments to and perfect the mechanism of a free and open market and a national market system because, as noted above, another options exchange currently offers a Global Trading Hours session.
                    <SU>90</SU>
                    <FTREF/>
                     While there are some differences among the proposed rule change and the Cboe Options Global Trading Hours session, such as the length of the session (Cboe Options GTH trading session begins at 3:00 a.m. and the proposed Exchange GTH trading session begins at 8:30 a.m.), the participation (while all TPHs on Cboe Options will have the opportunity to participate, as all TPHs on the Exchange will, Cboe Options requires TPHs to obtain a separate GTH trading permit, log-ins, and Market Maker appointments to participate in GTH while the Exchange will not), the proposed Exchange GTH trading session is similar to the Cboe Options GTH trading session.
                </P>
                <FTNT>
                    <P>
                        <SU>90</SU>
                         
                        <E T="03">See</E>
                         Cboe Options Rules 6.1 and 6.1A.
                    </P>
                </FTNT>
                <P>
                    The Exchange believes the proposed rule change to adopt an opening auction will protect investors, because it will enhance the openings of series on the Exchange by providing an opportunity for price discovery based on then-current market conditions. The proposed Queuing Period is substantively the same as the current Order Entry Period on the Exchange. The proposed detail regarding the Queuing Period provide additional transparency regarding the handling of orders and quotes submitted during that time, and will thus benefit investors. The proposed rule change, including orders that are not permitted during the Queuing Period or orders that are not eligible to trade during the opening rotation, is also similar to the pre-opening period on Cboe Options.
                    <SU>91</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>91</SU>
                         
                        <E T="03">See</E>
                         Cboe Options Rule 6.2(a). Cboe Options provides a longer pre-opening period than the proposed rule change. However, the Exchange is not proposing to change the time at which it begins to accept orders and quotes, believes the time period is sufficient for market participants to submit orders and quotes to participate in the opening rotation.
                    </P>
                </FTNT>
                <P>The proposed rule change will protect investors by ensuring they have access to information regarding the opening of a series, which will provide them with transparency that will permit them to participate in the opening auction process and contribute to, and benefit from, the price discovery the auction may provide. The proposed opening auction updates are not designed to permit unfair discrimination between customers, issuers, brokers, or dealers, as all market participants may subscribe to the Exchange's data feeds that deliver these messages, and thus all market participants may have access to this information.</P>
                <P>
                    The proposed opening rotation triggers are substantially similar to the current events that will trigger series openings on the Exchange. The proposed trigger events will remove impediments to and perfect the mechanism of a free and open market and a national market system, as they ensure that during Regular Trading Hours, the underlying securities will have begun trading, or the underlying index values will have begun being disseminated, before the System opens a series for trading. As this information will not be available during Global Trading Hours, the Exchange believes it is appropriate to begin the opening 
                    <PRTPAGE P="20932"/>
                    rotation for Global Trading Hours at a specified time (as Cboe Options does).
                </P>
                <P>The proposed Maximum Composite Width Check and Opening Collar will protect investors by providing price protection measures to prevent orders from executing at extreme prices at the open. The Exchange believes it is appropriate to open a series under the proposed circumstances and provide marketable orders with an opportunity to execute at a reasonable opening price (as discussed below), because there is minimal risk of execution at an extreme price. These proposed price protections incorporate all available pricing information, including Market Maker bulk messages (which are generally used to price markets for series) and any quotes disseminated from away markets, and thus may lead to a more accurate Opening Trade Price based on then-current market conditions. As noted above, Cboe Options applies similar price protections during its opening rotation. Cboe Options similarly considers Market Maker quotes (the equivalent of Market Maker bulk message on the Exchange), and in certain classes, quotes of away exchanges, and whether there are crossing orders or quotes when determining whether the opening width and trade price are reasonable. The Exchange proposes to calculate the maximum width and opening price range in a different, but reasonable manner intended to ensure a fair and orderly opening.</P>
                <P>
                    The proposed priority with respect to trades during the opening rotation are consistent with current priority principles that protect investors, which are to provide priority to more aggressively priced orders and quotes. Orders and quotes will be subject to the same allocation algorithms that the Exchange may apply during the trading day. The proposed priority and allocation of orders and quotes at the opening trade is substantially similar to the priority and allocation of orders and quotes at the opening of Cboe Options.
                    <SU>92</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>92</SU>
                         
                        <E T="03">See</E>
                         Cboe Options Rule 6.2(c)(i)(C) and Interpretation and Policy .04.
                    </P>
                </FTNT>
                <P>
                    The Exchange believes the proposed opening auction process is designed to ensure sufficient liquidity in a series when it opens and ensure series open at prices consistent with then-current market conditions, and thus will ensure a fair and orderly opening process. Additionally, as noted above, the proposed opening auction process is substantially similar to the opening auction process of Cboe Options.
                    <SU>93</SU>
                    <FTREF/>
                     As described above and below, the differences between proposed Rule 21.7 and Cboe Options Rule 6.2 primarily relate to differences between the exchanges, including functionality Cboe Options offers that the Exchange does not and products Cboe Options lists for trading that the Exchange does not.
                </P>
                <FTNT>
                    <P>
                        <SU>93</SU>
                         
                        <E T="03">See</E>
                         Cboe Options Rule 6.2.
                    </P>
                </FTNT>
                <P>The proposed rule change to provide the Exchange with flexibility regarding trading hours for index options, options on Fund Shares, and options on Index-Linked Securities will 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. This flexibility will permit the Exchange to modify trading hours to ensure that options are trading when instruments that investors use to price such options are also trading.</P>
                <P>The proposed rule change is generally intended to align system functionality currently offered by the Exchange with Cboe Options functionality in order to provide a consistent technology offering for the Cboe Affiliated Exchanges. A consistent technology offering, in turn, will simplify the technology implementation, changes, and maintenance by Users of the Exchange that are also participants on Cboe Affiliated Exchanges. The Exchange believes this consistency will promote a fair and orderly national options market system. When Cboe Options migrates to the same technology as that of the Exchange and other Cboe Affiliated Exchanges, Users of the Exchange and other Cboe Affiliated Exchanges will have access to similar functionality on all Cboe Affiliated Exchanges. As such, the proposed rule change would foster cooperation and coordination with persons engaged in facilitating transactions in securities and would remove impediments to and perfect the mechanism of a free and open market and a national market system.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The Exchange does not believe that the proposed rule change to adopt Global Trading Hours will impose any burden on intramarket competition that is not necessary or appropriate in furtherance of the purposes of the Act, because all Options Members will be able, but not be required, to participate during Global Trading Hours, and will be able to do so using the same connectivity as they use during Regular Trading Hours. Participation in GTH will be voluntary and within the discretion of Options Members. While the proposed rule change increases the total time during which a Market Maker with XSP appointment must quote, this increase is de minimis given that a Market Maker's compliance with its continuous quoting obligation is based on all classes in which it has an appointment in the aggregate. Selecting an appointment in XSP options will be optional and within the discretion of a Market Maker. Additionally, the Exchange is providing Market Makers with the opportunity to quote during GTH (and receive the benefits of acting as a Market Maker with respect to transactions it effects during that time) without creating additional connections to the Exchange or undertaking separate membership requirements (as is required on Cboe Options). Extending a Market Maker's appointment to Global Trading Hours will enhance liquidity during that trading session, which benefits all investors during those hours. The Exchange believes that the slight additional burden of extending the continuous quoting obligation to the GTH trading session in one class is outweighed by the Exchange's efforts to add liquidity in All Sessions classes, the minimal preparation a Market Maker may require to participate in the GTH trading session, and the benefits to investors that may result from that liquidity. Therefore, the Exchange believes the proposed rule change provides customer trading interest with a net benefit, and continues to maintain a balance of Market Maker benefits and obligations.</P>
                <P>
                    The Exchange does not believe that the proposed rule change to adopt Global Trading Hours will impose any burden on intermarket competition that is not necessary or appropriate in furtherance of the purposes of the Act, because the proposed rule change is competitive initiative that will benefit the marketplace and investors. The Exchange believes the proposed rule change will enhance competition by providing a service to investors that only one other options exchange current provides. Additionally, all options exchanges are free to compete in the same manner. The Exchange further believes that the same level of competition among options exchanges will continue during Regular Trading Hours. Because the Exchange proposes to make only exclusively listed products available for trading during Global Trading Hours, and because any All Sessions orders that do not trade during GTH will be eligible to trade during the RTH trading session in the same manner 
                    <PRTPAGE P="20933"/>
                    as all other orders during Regular Trading Hours, the proposed rule change will have no effect on the national best prices or trading during Regular Trading Hours. The Exchange also believes the proposed rule change could increase its competitive position outside of the United States by providing investors with an additional investment vehicle with respect to their global trading strategies during times that correspond with parts of regular trading hours outside of the United States.
                </P>
                <P>The Exchange does not believe that the proposed rule change to adopt an opening auction process will impose any burden on intramarket competition that is not necessary or appropriate in furtherance of the purposes of the Act, because it will apply to orders and quotes of all market participants in the same manner. The same order types that are not currently accepted prior to the opening, and that do not participate in the opening process, will similarly not be accepted during the Queuing Period or be eligible for trading during the opening rotation.</P>
                <P>
                    The Exchange does not believe that the proposed rule change to adopt an opening auction process will impose any burden on intermarket competition that is not necessary or appropriate in furtherance of the purposes of the Act, because it is designed to open series on the Exchange in a fair and orderly manner. The Exchange believes an opening auction process will enhance the openings of series on the Exchange by providing an opportunity for price discovery based on then-current market conditions. The proposed auction process will provide an opportunity for price discovery when a series opens ensure there sufficient liquidity in a series when it opens, and ensure series open at prices consistent with then-current market conditions (at the Exchange and other exchanges) rather than extreme prices that could result in unfavorable executions to market participants. Additionally, as discussed above, the proposed opening auction process is substantially similar to the Cboe Options opening auction process.
                    <SU>94</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>94</SU>
                         
                        <E T="03">See</E>
                         Cboe Options Rule 6.2.
                    </P>
                </FTNT>
                <P>
                    The proposed rule change to provide the Exchange with flexibility regarding trading hours for certain products will not impose any burden on competition not necessary or appropriate under the Act, as another options exchange has the same flexibility.
                    <SU>95</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>95</SU>
                         
                        <E T="03">See</E>
                         C2 Rule 6.1.
                    </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>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>
                    Because the foregoing proposed rule change does not: (i) Significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative for 30 days from the date on which it was filed, or such shorter time as the Commission may designate, it has become effective pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>96</SU>
                    <FTREF/>
                     and subparagraph (f)(6) of Rule 19b-4 thereunder.
                    <SU>97</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>96</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>97</SU>
                         17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6)(iii) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings to determine whether the proposed rule should be approved or disapproved.</P>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-CboeEDGX-2019-027 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to File Number SR-CboeEDGX-2019-027. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">http://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:00 a.m. and 3:00 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change. Persons submitting comments are cautioned that we do not redact or edit personal identifying information from comment submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-CboeEDGX-2019-027 and should be submitted
                    <FTREF/>
                     on or before June 3, 2019.
                </FP>
                <FTNT>
                    <P>
                        <SU>98</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>98</SU>
                    </P>
                    <NAME>Eduardo A. Aleman,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09729 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Investment Company Act Release No. 33469; 812-14996]</DEPDOC>
                <SUBJECT>Toroso Investments, LLC and Tidal ETF Trust; Notice of Application</SUBJECT>
                <DATE>May 8, 2019.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Securities and Exchange Commission (“Commission”).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <P>
                    Notice of an application under section 6(c) of the Investment Company Act of 1940 (“Act”) for an exemption from section 15(a) of the Act and rule 18f-2 
                    <PRTPAGE P="20934"/>
                    under the Act, as well as from certain disclosure requirements in rule 20a-1 under the Act, Item 19(a)(3) of Form N-1A, Items 22(c)(1)(ii), 22(c)(1)(iii), 22(c)(8) and 22(c)(9) of Schedule 14A under the Securities Exchange Act of 1934, and Sections 6-07(2)(a), (b), and (c) of Regulation S-X (“Disclosure Requirements”). The requested exemption would permit an investment adviser to hire and replace certain sub-advisers without shareholder approval and grant relief from the Disclosure Requirements as they relate to fees paid to the sub-advisers.
                </P>
                <PREAMHD>
                    <HD SOURCE="HED">Applicants:</HD>
                    <P>Tidal ETF Trust (the “Trust”), a Delaware statutory trust registered under the Act as an open-end management investment company with multiple series, and Toroso Investments, LLC (the “Initial Adviser”), a Delaware limited liability company registered as an investment adviser under the Investment Advisers Act of 1940.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Filing Dates:</HD>
                    <P>The application was filed on January 9, 2019.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Hearing or Notification of Hearing:</HD>
                    <P>An order granting the application will be issued unless the Commission orders a hearing. Interested persons may request a hearing by writing to the Commission's Secretary and serving applicants with a copy of the request, personally or by mail. Hearing requests should be received by the Commission by 5:30 p.m. on June 3, 2019, and should be accompanied by proof of service on applicants, in the form of an affidavit or, for lawyers, a certificate of service. Pursuant to rule 0-5 under the Act, hearing requests should state the nature of the writer's interest, any facts bearing upon the desirability of a hearing on the matter, the reason for the request, and the issues contested. Persons who wish to be notified of a hearing may request notification by writing to the Commission's Secretary.</P>
                </PREAMHD>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Secretary, U.S. Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090. Applicants: Toroso Investments, LLC and Tidal ETF Trust, 898 N Broadway, Suite 2, Massapequa, New York 11758.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jill Corrigan, Senior Counsel, at (202) 551-8929, or Parisa Haghshenas, Branch Chief, at (202) 551-6723 (Division of Investment Management, Chief Counsel's Office).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The following is a summary of the application. The complete application may be obtained via the Commission's website by searching for the file number, or for an applicant using the Company name box, at 
                    <E T="03">http://www.sec.gov/search/search.htm</E>
                     or by calling (202) 551-8090.
                </P>
                <HD SOURCE="HD1">Summary of the Application</HD>
                <P>
                    1. The Initial Adviser is the investment adviser to the Aware Ultra-Short Duration Enhanced Income ETF (the “Initial Fund”), a series of the Trust, pursuant to an investment management agreement with the Trust (“Investment Management Agreement”).
                    <SU>1</SU>
                    <FTREF/>
                     Under the terms of the Investment Management Agreement, the Adviser, subject to the supervision of the board of trustees of the Trust (“Board”), will provide continuous investment management of the assets of each Subadvised Fund. Consistent with the terms of the Investment Management Agreement, the Adviser may, subject to the approval of the Board, delegate portfolio management responsibilities of all or a portion of the assets of a Subadvised Fund to one or more Sub-Advisers.
                    <SU>2</SU>
                    <FTREF/>
                     The Adviser will continue to have overall responsibility for the management and investment of the assets of each Subadvised Fund. The Adviser will evaluate, select, and recommend Sub-Advisers to manage the assets of a Subadvised Fund and will oversee, monitor and review the Sub-Advisers and their performance and recommend the removal or replacement of Sub-Advisers.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Applicants request relief with respect to the Initial Fund, as well as to any future series of the Trust and any other existing or future registered open-end management investment company or series thereof that, in each case, is advised by the Initial Adviser or any entity controlling, controlled by, or under common control with, the Initial Adviser or its successors (each, also an “Adviser”), uses the multi-manager structure described in the application, and complies with the terms and conditions set forth in the application (each, a “Subadvised Fund”). For purposes of the requested order, “successor” is limited to an entity that results from a reorganization into another jurisdiction or a change in the type of business organization. Future Subadvised Funds may be operated as a master-feeder structure pursuant to section 12(d)(1)(E) of the Act. In such a structure, certain series of the Trust (each, a “Feeder Fund”) may invest substantially all of their assets in a Subadvised Fund (a “Master Fund”) pursuant to section 12(d)(1)(E) of the Act. No Feeder Fund will engage any sub-advisers other than through approving the engagement of one or more of the Master Fund's sub-advisers.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         As used herein, a “Sub-Adviser” for a Subadvised Fund is (1) an indirect or direct “wholly owned subsidiary” (as such term is defined in the Act) of the Adviser for that Subadvised Fund, or (2) a sister company of the Adviser for that Subadvised Fund that is an indirect or direct “wholly-owned subsidiary” of the same company that, indirectly or directly, wholly owns the Adviser (each of (1) and (2) a “Wholly-Owned Sub-Adviser” and collectively, the “Wholly-Owned Sub-Advisers”), or (3) not an “affiliated person” (as such term is defined in section 2(a)(3) of the Act) of the Subadvised Fund, any Feeder Fund invested in a Master Fund, the Trust, or the Adviser, except to the extent that an affiliation arises solely because the Sub-Adviser serves as a sub-adviser to a Subadvised Fund (“Non-Affiliated Sub-Advisers”).
                    </P>
                </FTNT>
                <P>
                    2. Applicants request an exemption to permit the Adviser, subject to Board approval, to hire certain Sub-Advisers pursuant to Sub-Advisory Agreements and materially amend existing Sub-Advisory Agreements without obtaining the shareholder approval required under section 15(a) of the Act and rule 18f-2 under the Act.
                    <SU>3</SU>
                    <FTREF/>
                     Applicants also seek an exemption from the Disclosure Requirements to permit a Subadvised Fund to disclose (as both a dollar amount and a percentage of the Subadvised Fund's net assets): (a) The aggregate fees paid to the Adviser and any Wholly-Owned Sub-Adviser; (b) the aggregate fees paid to Non-Affiliated Sub-Advisers; and (c) the fee paid to each Affiliated Sub-Adviser (collectively, Aggregate Fee Disclosure”).
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The requested relief will not extend to any sub-adviser, other than a Wholly-Owned Sub-Adviser, who is an affiliated person, as defined in section 2(a)(3) of the Act, of the Subadvised Fund, of any Feeder Fund, or of the Adviser, other than by reason of serving as a sub-adviser to one or more of the Subadvised Funds (“Affiliated Sub-Adviser”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         For any Subadvised Fund that is a Master Fund, the relief would also permit any Feeder Fund invested in that Master Fund to disclose Aggregate Fee Disclosure.
                    </P>
                </FTNT>
                <P>3. Applicants agree that any order granting the requested relief will be subject to the terms and conditions stated in the application. Such terms and conditions provide for, among other safeguards, appropriate disclosure to Subadvised Funds' shareholders and notification about sub-advisory changes and enhanced Board oversight to protect the interests of the Subadvised Funds' shareholders.</P>
                <P>
                    4. Section 6(c) of the Act provides that the Commission may exempt any person, security, or transaction or any class or classes of persons, securities, or transactions from any provisions of the Act, or any rule thereunder, if such relief is necessary or appropriate in the public interest and consistent with the protection of investors and purposes fairly intended by the policy and provisions of the Act. Applicants believe that the requested relief meets this standard because, as further explained in the application, the Investment Management Agreement will remain subject to shareholder approval, while the role of the Sub-Advisers is substantially equivalent to that of individual portfolio managers, so that requiring shareholder approval of Sub-Advisory Agreements would impose unnecessary delays and expenses on the Subadvised Funds. Applicants believe that the requested relief from the 
                    <PRTPAGE P="20935"/>
                    Disclosure Requirements meets this standard because it will improve the Adviser's ability to negotiate fees paid to the Sub-Advisers that are more advantageous for the Subadvised Funds.
                </P>
                <SIG>
                    <P>For the Commission, by the Division of Investment Management, under delegated authority.</P>
                    <NAME>Eduardo A. Aleman,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09800 Filed 5-10-19; 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-85794; File No. SR-CboeBYX-2019-007]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe BYX Exchange, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change Amending Rule 11.13 (Order Execution and Routing) and Fee Schedule To Delete References to TRIM2 and SWPB Routing Options</SUBJECT>
                <DATE>May 7, 2019.</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 April 29, 2019, Cboe BYX Exchange, Inc. (“Exchange” or “BYX”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the Exchange. The Exchange filed the proposal as a “non-controversial” proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>3</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>4</SU>
                    <FTREF/>
                     The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>Cboe BYX Exchange, Inc. (the “Exchange” or “BYX”) proposes to amend Rule 11.13 (Order Execution and Routing), as well as its Fee Schedule, to delete references to the TRIM2 and SWPB routing options. The text of the proposed rule change is provided in Exhibit 5.</P>
                <P>
                    The text of the proposed rule change is also available on the Exchange's website (
                    <E T="03">http://markets.cboe.com/us/equities/regulation/rule_filings/byx/</E>
                    ), at the Exchange's Office of the Secretary, and at the Commission's Public Reference Room.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the Exchange included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant aspects of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>The Exchange proposes to amend Rule 11.13(b)(3)(G) (Other Routing Strategies) to delete the TRIM2 routing option. The Exchange also proposes to amend its fee schedule to delete references to the TRIM2 routing options under fee codes BJ and C, as well as the “Routing Tier” under footnote 3. Additionally, the Exchange proposes to amend Rule 11.13(b)(3)(I) (SWP) to delete the SWPB routing option and to delete references to SWPB in the fee schedule under fee code SW and under footnote 9. The Exchange intends to implement the proposed rule changes on May 1, 2019.</P>
                <P>
                    Currently, Rule 11.13(b)(3)(G) provides for the routing options under which an order checks the System 
                    <SU>5</SU>
                    <FTREF/>
                     for available shares if so instructed by the entering User 
                    <SU>6</SU>
                    <FTREF/>
                     and then is sent to destinations on the applicable System routing table. The term “System routing table” refers to the proprietary process for determining the specific trading venues to which the System routes orders and the order in which it routes them.
                    <SU>7</SU>
                    <FTREF/>
                     Rule 11.13(b)(3)(G) currently includes TRIM2 as one of such routing options.
                    <SU>8</SU>
                    <FTREF/>
                     In addition, current fee code BJ is yielded on orders routed to EDGA using TRIM, TRIM2 or SLIM routing strategy 
                    <SU>9</SU>
                    <FTREF/>
                     and fee code C is yielded on orders routed to BX using Destination Specific, TRIM, TRIM2 or SLIM routing strategy.
                    <SU>10</SU>
                    <FTREF/>
                     Also, current footnote 3 provides for additional rebate per share for orders yielding fee code C (thus inclusive of a TRIM2 routing strategy) if a Member achieves certain criteria.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The “System” is the Exchange's electronic communications and trading facility designated by the Board through which securities orders of Users are consolidated for ranking, execution and, when applicable, routing away. 
                        <E T="03">See</E>
                         Exchange Rule 1.5(aa).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The term “User” is defined as “any Member or Sponsored Participant who is authorized to obtain access to the System pursuant to Rule 11.3.” 
                        <E T="03">See</E>
                         Exchange Rule 1.5(cc).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The Exchange reserves the right to maintain a different System routing table for different routing options and to modify the System routing table at any time without notice. 
                        <E T="03">See</E>
                         Exchange Rule 11.13(b)(3).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         TRIM2 routing strategy currently sends orders to: BYX + DRT + BX + EDGA. 
                        <E T="03">See also</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Orders that yield fee code BJ receive a rebate of $0.0024 per share.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Orders that yield fee code C receive a rebate of $0.0010 per share.
                    </P>
                </FTNT>
                <P>
                    Current Rule 11.13(b)(3)(I) provides for SWP routing options. SWP is a routing option under which an order checks the System for available displayed shares and then is sent to destinations on the System routing table. SWP orders route only to Protected Quotations and only for displayed size. Specifically, the current rule provides for two forms of SWP routing, SWPA and SWPB. A SWPA order routes to destinations on the System routing table even if at the time of entry there is an insufficient share quantity in the SWPA order to fulfill the displayed size of all Protected Quotations, whereas an entire SWPB order will be cancelled back to a User immediately if at the time of entry there is an insufficient share quantity in the SWPB order to fulfill the displayed size of all Protected Quotations. Moreover, current fee code SW is yielded on orders routed using Parallel T, SWPA or SWPB routing strategies,
                    <SU>11</SU>
                    <FTREF/>
                     and current footnote 9 describes the fees charged for orders yielding fee code SW that remove liquidity in securities priced below $1.00 for Parallel T, SWPA or SWPB routed executions.
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Orders that yield fee code SW receive a discounted fee of $0.0033 per share.
                    </P>
                </FTNT>
                <P>
                    The Exchange has determined that because few Users elect the TRIM2 routing option and the SWPB routing option, which often experiences no usage for extended periods of time, the current demand does not warrant the infrastructure and ongoing maintenance expenses required to support these products. Therefore, the Exchange now proposes to delete TRIM2 as a routing option under Rule 11.13(b)(3)(G)(v) and SWPB as a routing option under Rule 11.13(b)(3)(I). The Exchange proposes to amend the Rule formatting accordingly, changing current subparagraph (b)(3)(G)(vi) to subparagraph 11.13(b)(3)(G)(v). The Exchange also proposes to amend its fee schedule to delete references to the TRIM2 routing option under fee codes BJ and C, as well 
                    <PRTPAGE P="20936"/>
                    as within the “Routing Tier” under footnote 3, and to delete references to the SWPB routing option under fee code SW and footnote 9. Users seeking to route to other trading centers may use alternative methods, such as utilizing other routing strategies offered by the Exchange, or connecting to those venues directly or through a third party service provider.
                </P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes the proposed rule change is consistent with the Securities Exchange Act of 1934 (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>12</SU>
                    <FTREF/>
                     Specifically, the Exchange believes the proposed rule change is consistent with the Section 6(b)(5) 
                    <SU>13</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>14</SU>
                    <FTREF/>
                     requirement that the rules of an exchange not be designed to permit unfair discrimination between customers, issuers, brokers, or dealers.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>In particular, The Exchange does not believe that this proposal will permit unfair discrimination among customers, brokers, or dealers because the TRIM2 and SWPB routing options will no longer be available to all Users. Also, the Exchange believes the proposed rule change to remove references to TRIM2 and SWPB will remove impediments to the mechanism of a free and open market, thereby protecting investors and the public interest. As stated, the Exchange noted that few Users elect the TRIM2 or SWPB routing options and has determined that the current demand does not warrant the infrastructure and ongoing maintenance expense required to support these products. Therefore, the Exchange is discontinuing these routing options. The Exchange notes that routing through the Exchange is voluntary and alternative routing options offered by the Exchange as well as other methods remain available to Users that wish to route to other trading centers. In addition, neither the TRIM2 nor the SWPB routing option are core product offerings by the Exchange, nor is the Exchange required by the Act to offer such products. By removing references to routing options that will no longer be offered by the Exchange, the Exchange believes the proposed rule change will remove impediments to the mechanism of a free and open market and protect investors by providing investors with rules that accurately reflect routing options currently available.</P>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed rule change to remove TRIM2 and SWPB is not designed to address any competitive issues but rather to delete the TRIM2 and SWPB routing options that are rarely used on the Exchange.</P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>The Exchange neither solicited nor received comments on the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The foregoing rule change has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>15</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>16</SU>
                    <FTREF/>
                     thereunder because the proposal does not: (i) Significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) by its terms, become operative for 30 days from the date on which it was filed, or such shorter time as the Commission may designate if consistent with the protection of investors and the public interest.
                    <SU>17</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         In addition, Rule 19b-4(f)(6)(iii) requires the Exchange to give the Commission written notice of the Exchange's intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    A proposed rule change filed under Rule 19b-4(f)(6) normally may not become operative prior to 30 days after the date of filing. However, Rule 19b-4(f)(6)(iii) 
                    <SU>18</SU>
                    <FTREF/>
                     permits the Commission to designate a shorter time if such action is consistent with the protection of investors and the public interest. The Exchange has requested that the Commission waive the 30-day operative delay period. The Commission believes that waiver of the 30-day operative delay period is consistent with the protection of investors and the public interest. Specifically, the Commission believes that the proposal would accurately reflect routing options that are currently available on the Exchange and delete routing options no longer offered by the Exchange. For these reasons, the Commission believes that waiving the 30-day operative delay is consistent with the protection of investors and the public interest, and designates the proposed rule change to be operative upon filing with the Commission.
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         17 CFR 240.19b-4(f)(6)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         For purposes only of waiving the operative delay for this proposal, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         15 U.S.C. 78s(b)(3)(C).
                    </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">http://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-CboeBYX-2019-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-CboeBYX-2019-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 
                    <PRTPAGE P="20937"/>
                    post all comments on the Commission's internet website (
                    <E T="03">http://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:00 a.m. and 3:00 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change. Persons submitting comments are cautioned that we do not redact or edit personal identifying information from comment submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-CboeBYX-2019-007 and should be submitted on or before June
                    <FTREF/>
                     3, 2019.
                </FP>
                <FTNT>
                    <P>
                        <SU>21</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>21</SU>
                    </P>
                    <NAME>Eduardo A. Aleman,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09727 Filed 5-10-19; 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-85795; File No. SR-CboeBZX-2019-037]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe BZX Exchange, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change Amending Rule 11.13 (Order Execution and Routing) and the Fee Schedule To Delete References to the TRIM2 and SWPB Routing Options</SUBJECT>
                <DATE>May 7, 2019.</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 April 29, 2019, Cboe BZX Exchange, Inc. (“Exchange” or “BZX”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the Exchange. The Exchange filed the proposal as a “non-controversial” proposed rule change pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>3</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>4</SU>
                    <FTREF/>
                     The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>Cboe BZX Exchange, Inc. (the “Exchange” or “BZX”) proposes to amend Rule 11.13 (Order Execution and Routing), as well as its Fee Schedule, to delete references to the TRIM2 and SWPB routing options. The Exchange also proposes to amend Rule 11.13 to update references to the TRIM routing strategy. The text of the proposed rule change is provided in Exhibit 5.</P>
                <P>
                    The text of the proposed rule change is also available on the Exchange's website (
                    <E T="03">http://markets.cboe.com/us/equities/regulation/rule_filings/bzx/</E>
                    ), at the Exchange's Office of the Secretary, and at the Commission's Public Reference Room.
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the Exchange included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant aspects of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>The Exchange proposes to amend Rule 11.13(b)(3)(G) (Other Routing Strategies) to delete the TRIM2 routing option, as well as add language codifying User designation of the TRIM routing option. The Exchange also proposes to amend its fee schedule to delete references to the TRIM2 routing options under fee codes BJ, BY and TV. The Exchange also proposes to amend Rule 11.13(b)(3)(I) (SWP) to delete the SWPB routing option and to delete references to SWPB in the fee schedule under fee code SW and under footnote 9. The Exchange intends to implement the proposed rule changes on May 1, 2019.</P>
                <HD SOURCE="HD3">TRIM Routing Strategies</HD>
                <P>
                    Currently, Rule 11.13(b)(3)(G) provides for the routing options under which an order checks the System 
                    <SU>5</SU>
                    <FTREF/>
                     for available shares if so instructed by the entering User 
                    <SU>6</SU>
                    <FTREF/>
                     and then is sent to destinations on the applicable System routing table. The term “System routing table” refers to the proprietary process for determining the specific trading venues to which the System routes orders and the order in which it routes them.
                    <SU>7</SU>
                    <FTREF/>
                     Rule 11.13(b)(3)(G) currently includes TRIM2 as one of such routing options.
                    <SU>8</SU>
                    <FTREF/>
                     In addition, current fee code BJ is yielded on orders routed to EDGA using TRIM,
                    <SU>9</SU>
                    <FTREF/>
                     TRIM2 or SLIM routing strategy,
                    <SU>10</SU>
                    <FTREF/>
                     fee code BY is yielded on orders routed to BYX using Destination Specific, TRIM, TRIM2 or SLIM routing strategy,
                    <SU>11</SU>
                    <FTREF/>
                     and fee code TV is yielded on orders routed to BX using TRIM, TRIM2, or SLIM routing strategy.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The “System” is the Exchange's electronic communications and trading facility designated by the Board through which securities orders of Users are consolidated for ranking, execution and, when applicable, routing away. 
                        <E T="03">See</E>
                         Exchange Rule 1.5(aa).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The term “User” is defined as “any Member or Sponsored Participant who is authorized to obtain access to the System pursuant to Rule 11.3.” 
                        <E T="03">See</E>
                         Exchange Rule 1.5(cc).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The Exchange reserves the right to maintain a different System routing table for different routing options and to modify the System routing table at any time without notice. 
                        <E T="03">See</E>
                         Exchange Rule 11.13(b)(3).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         TRIM2 routing strategy currently sends orders to: BZX + BYX + DRT Venues + BX + EDGA + EDGA. 
                        <E T="03">See also</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         TRIM routing strategy currently sends orders to: BZX + BYX + EDGA + NYSE National + BX + NYSE American + DRT Venues. 
                        <E T="03">See also</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Orders that yield fee code BJ receive a rebate of $0.0024 per share.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Orders that yield fee code BY receive a rebate of $0.0015 per share.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         Orders that yield fee code TV receive a rebate of $0.0010 per share.
                    </P>
                </FTNT>
                <P>
                    The Exchange has determined that because few Users elect the TRIM2 routing option, the current demand does not warrant the infrastructure and ongoing maintenance expenses required to support the product. Therefore, the Exchange now proposes to delete TRIM2 as a routing option under Rule 11.13(b)(3)(G)(v).
                    <SU>13</SU>
                    <FTREF/>
                     The Exchange also proposes to amend its fee schedule to delete references to the TRIM2 routing option under fee codes BJ, BY and TV. Users seeking to route to other trading 
                    <PRTPAGE P="20938"/>
                    centers may use alternative methods, such as utilizing other routing strategies offered by the Exchange, or connecting to those venues directly or through a third party service provider.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         The Exchange also proposes to update the subsequent numbering as a result of this proposed deletion.
                    </P>
                </FTNT>
                <P>
                    The Exchange also proposes to specify under Rule 11.13(b)(3)(G) that in connection with TRIM, 
                    <SU>14</SU>
                    <FTREF/>
                     a routing option currently available to all Users and provided for under current subparagraph (b)(3)(G)(iv), a User may designate that an order first routes to Cboe BYX Exchange, Inc. (“BYX”), checks the System for available shares, and then routes to other destinations on the System routing table. This proposed rule change does not create a new routing strategy, but rather codifies a routing strategy that is already offered on the Exchange.
                    <SU>15</SU>
                    <FTREF/>
                     The Exchange notes that TRIM also has a variant routing strategy (TRIM-) in that a User may designate an order to skip the Exchange and otherwise send orders to the same venues as TRIM. The TRIM routing strategy and its variation are focused on seeking execution of orders while minimizing execution costs by routing to certain low cost execution venues on the Exchange's System routing table. TRIM currently offers Users more flexibility in routing orders consistent with Regulation NMS. No changes to the functionality of the TRIM routing strategy are proposed by this filing.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See supra</E>
                         note 9.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">Available at:</E>
                          
                        <E T="03">https://cdn.cboe.com/resources/features/Cboe_USE_RoutingStrategies.pdf. See also</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See supra</E>
                         note 7.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">SWPB Routing Strategy</HD>
                <P>
                    Currently, Rule 11.13(b)(3)(I) provides for SWP routing options. SWP is a routing option under which an order checks the System for available displayed shares and then is sent to destinations on the System routing table. SWP orders route only to Protected Quotations and only for displayed size. Specifically, the current rule provides for two forms of SWP routing, SWPA and SWPB. A SWPA order routes to destinations on the System routing table even if at the time of entry there is an insufficient share quantity in the SWPA order to fulfill the displayed size of all Protected Quotations, whereas an entire SWPB order will be cancelled back to a User immediately if at the time of entry there is an insufficient share quantity in the SWPB order to fulfill the displayed size of all Protected Quotations. Moreover, current fee code SW is yielded on orders routed using Parallel T, SWPA or SWPB routing strategies,
                    <SU>17</SU>
                    <FTREF/>
                     and current footnote 9 describes the fees charged for orders yielding fee code SW that remove liquidity in securities priced below $1.00 for Parallel T, SWPA or SWPB routed executions.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         Orders that yield fee code SW receive a discounted fee of $0.0033 per share.
                    </P>
                </FTNT>
                <P>
                    Like that of TRIM2, the Exchange has determined that due to diminished User election of the SWPB routing option, which often experiences no usage for extended periods of time, the current demand does not warrant the infrastructure and ongoing maintenance expenses required to support the product. Therefore, the Exchange is decommissioning SWPB routed orders on the Exchange.
                    <SU>18</SU>
                    <FTREF/>
                     As a result, the Exchange now proposes to delete the SWPB routing option under Rule 11.3(b)(3)(I), amending the language as necessary to provide only for SWPA orders. The Exchange also proposes to delete references to SWPB under fee code SW and its accompanying footnote 9.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         The Exchange notes that its affiliated exchanges, BYX, EDGA, and Cboe EDGX Exchange, Inc. (“EDGX”), are simultaneously proposing to decommission the SWPB routing option.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes the proposed rule change is consistent with the Securities Exchange Act of 1934 (the “Act”) and the rules and regulations thereunder applicable to the Exchange and, in particular, the requirements of Section 6(b) of the Act.
                    <SU>19</SU>
                    <FTREF/>
                     Specifically, the Exchange believes the proposed rule change is consistent with the Section 6(b)(5) 
                    <SU>20</SU>
                    <FTREF/>
                     requirements that the rules of an exchange be designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in securities, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest. Additionally, the Exchange believes the proposed rule change is consistent with the Section 6(b)(5) 
                    <SU>21</SU>
                    <FTREF/>
                     requirement that the rules of an exchange not be designed to permit unfair discrimination between customers, issuers, brokers, or dealers.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>In particular, The Exchange does not believe that this proposal will permit unfair discrimination among customers, brokers, or dealers because the TRIM2 routing option and the SWPB routing option will no longer be available to all Users. Also, the Exchange believes the proposed rule change to remove references to TRIM2 and SWPB will remove impediments to the mechanism of a free and open market, thereby protecting investors and the public interest. As stated, the Exchange has noted that few Users elect the TRIM2 and SWPB routing options and has determined that the current demand does not warrant the infrastructure and ongoing maintenance expense required to support these products. Therefore, the Exchange is discontinuing these routing options. The Exchange notes that routing through the Exchange is voluntary and alternative routing options offered by the Exchange as well as other methods remain available to Users that wish to route to other trading centers. In addition, neither the TRIM2 nor the SWPB routing options are core product offerings by the Exchange, nor is the Exchange required by the Act to offer such products. By removing references to routing options that will no longer be offered by the Exchange, the Exchange believes the proposed rule change will remove impediments to the mechanism of a free and open market and protect investors by providing investors with rules that accurately reflect routing options currently available on the Exchange.</P>
                <P>
                    Additionally, the Exchange believes that the amendment to codify User designation of the TRIM routing strategy, which is already available to Users,
                    <SU>22</SU>
                    <FTREF/>
                     will also benefit investors by providing investors with rules reflecting the routing strategies currently offered by the Exchange. The Exchange notes that the TRIM routing strategy (and its variant strategy) is available to all Users, thereby benefitting all Users equally.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See supra</E>
                         note 15.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. The proposed rule change to remove TRIM2 and SWPB is not designed to address any competitive issues but rather to delete the TRIM2 and SWPB routing options that are rarely used on the Exchange and codify the User designation regarding an existing strategy currently provided for on the Exchange.
                    <PRTPAGE P="20939"/>
                </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>The Exchange neither solicited nor received comments on the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The foregoing rule change has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>23</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>24</SU>
                    <FTREF/>
                     thereunder because the proposal does not: (i) Significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) by its terms, become operative for 30 days from the date on which it was filed, or such shorter time as the Commission may designate if consistent with the protection of investors and the public interest.
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         In addition, Rule 19b-4(f)(6)(iii) requires the Exchange to give the Commission written notice of the Exchange's intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    A proposed rule change filed under Rule 19b-4(f)(6) normally may not become operative prior to 30 days after the date of filing. However, Rule 19b-4(f)(6)(iii) 
                    <SU>26</SU>
                    <FTREF/>
                     permits the Commission to designate a shorter time if such action is consistent with the protection of investors and the public interest. The Exchange has requested that the Commission waive the 30-day operative delay period. The Commission believes that waiver of the 30-day operative delay period is consistent with the protection of investors and the public interest. Specifically, the Commission believes that the proposal would accurately reflect the routing options currently available on the Exchange and how those routing options would operate. For these reasons, the Commission believes that waiving the 30-day operative delay is consistent with the protection of investors and the public interest, and designates the proposed rule change to be operative upon filing with the Commission.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         17 CFR 240.19b-4(f)(6)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         For purposes only of waiving the operative delay for this proposal, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act.
                    <SU>28</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         15 U.S.C. 78s(b)(3)(C).
                    </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">http://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-CboeBZX-2019-037 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to File Number SR-CboeBZX-2019-037. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of 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:00 a.m. and 3:00 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change. Persons submitting comments are cautioned that we do not redact or edit personal identifying information from comment submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-CboeBZX-2019-037 and should be submitted on or before June 3, 2019.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>29</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Eduardo A. Aleman,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09728 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <SUBJECT>Proposed Collection; Comment Request</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>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        <E T="03">Extension:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Regulation A (Form 1-A), SEC File No. 270-110, OMB Control No. 3235-0286</FP>
                </EXTRACT>
                <P>
                    Notice is hereby given that, pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), the Securities and Exchange Commission (“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>
                    Regulation A (17 CFR 230.251 through 230.263) provides an exemption from registration under the Securities Act of 1933 (15 U.S.C. 77a 
                    <E T="03">et seq.</E>
                    ) for certain limited offerings of securities by issuers who do not otherwise file reports with the Commission. Form 1-A is an offering statement filed under Regulation A. The paperwork burden from Regulation A is imposed through the forms that are subject to the disclosure requirements in Regulation A and is reflected in the analysis of the form. To avoid a Paperwork Reduction Act inventory reflecting duplicative burdens, for administrative convenience we estimate the burden imposed by Regulation A to be a total of one hour. We estimate that approximately 179 issuers file Forms 1-A. We estimate that Form 1-A takes approximately 732.28 hours to prepare. We estimate that 75% of the 732.28 hours per response (549.21 hours) is prepared by the company for a total annual burden of 98,309 hours (549.21 hours per response × 179 responses).
                </P>
                <P>
                    <E T="03">Written comments are invited on:</E>
                     (a) Whether this proposed collection of 
                    <PRTPAGE P="20940"/>
                    information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (b) the accuracy of the agency's estimate of the burden imposed by 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 in writing within 60 days of this publication.
                </P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid control number.</P>
                <P>
                    Please direct your written comments to Charles Riddle, Acting Director/Chief Information Officer, Securities and Exchange Commission, c/o Candace Kenner, 100 F Street NE, Washington, DC 20549 or send an email to: 
                    <E T="03">PRA_Mailbox@sec.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: May 8, 2019.</DATED>
                    <NAME>Eduardo A. Aleman,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09797 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <SUBJECT>Proposed Collection; Comment Request</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>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        <E T="03">Extension:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Form F-7, SEC File No. 270-331, OMB Control No. 3235-0383</FP>
                </EXTRACT>
                <P>
                    Notice is hereby given that, pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), the Securities and Exchange Commission (“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>
                    Form F-7 (17 CFR 239.37) is a registration statement under the Securities Act of 1933 (15 U.S.C. 77a 
                    <E T="03">et seq.</E>
                    ) used to register securities that are offered for cash upon the exercise of rights granted to a registrant's existing security holders to purchase or subscribe such securities. The information collected is intended to ensure that the information required to be filed by the Commission permits verification of compliance with securities law requirements and assures the public availability of such information. Form F-7 takes approximately 4 hours per response to prepare and is filed by approximately 5 respondents. We estimate that 25% of 4 hours per response (one hour) is prepared by the company for a total annual reporting burden of 5 hours (one hour per response × 5 responses).
                </P>
                <P>
                    <E T="03">Written comments are invited on:</E>
                     (a) Whether this proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (b) the accuracy of the agency's estimate of the burden imposed by 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 in writing within 60 days of this publication.
                </P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid control number.</P>
                <P>
                    Please direct your written comment to Charles Riddle, Acting Director/Chief Information Officer, Securities and Exchange Commission, c/o Candace Kenner, 100 F Street NE, Washington, DC 20549 or send an email to: 
                    <E T="03">PRA_Mailbox@sec.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: May 8, 2019.</DATED>
                    <NAME>Eduardo A. Aleman,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09798 Filed 5-10-19; 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-85798; File No. SR-BOX-2019-15]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; BOX Exchange LLC; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Modify the Criteria for Listing an Option on an Underlying Covered Security</SUBJECT>
                <DATE>May 7, 2019.</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 April 25, 2019, BOX Exchange LLC (“Exchange” or “BOX”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule from interested persons.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to amend BOX Rule 5020 (Criteria for Underlying Securities) to modify the criteria for listing an option on an underlying covered security. The text of the proposed rule change is available from the principal office of the Exchange, at the Commission's Public Reference Room and also on the Exchange's internet website at 
                    <E T="03">http://boxoptions.com.</E>
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The self-regulatory organization has prepared summaries, set forth in Sections A, B, and C below, of the most significant aspects of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    The Exchange proposes to amend BOX Rule 5020 (Criteria for Underlying Securities) to modify the criteria for listing an option on an underlying covered security. This is a competitive filing that is based on a proposal submitted by NASDAQ PHLX LLC (“Phlx”) and approved by the Commission.
                    <SU>3</SU>
                    <FTREF/>
                     The Exchange proposes to modify Rule 5020(b)(5)(i) to permit the listing of an option on an underlying covered security that has a market price of at least $3.00 for the previous three 
                    <PRTPAGE P="20941"/>
                    consecutive business days preceding the date on which the Exchange submits a certificate to the Options Clearing Corporation (“OCC”) for listing and trading. The Exchange does not intend to amend any other criteria for listing options on an underlying security in Rule 5020.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 34-82474 (January 9, 2018) (Order Approving SR-Phlx-2017-75).
                    </P>
                </FTNT>
                <P>Currently, the underlying covered security must have a closing market price of at least $3.00 per share for the previous five consecutive business days preceding the date on which the Exchange submits a listing certificate to the OCC. In the proposed amendment, the market price will still be measured by the closing price reported in the primary market in which the underlying covered security is traded, but the measurement will be the price over the prior three consecutive business day period preceding the submission of the listing certificate to OCC, instead of the prior five business day period.</P>
                <P>
                    The Exchange acknowledges that the Options Listing Procedures Plan 
                    <SU>4</SU>
                    <FTREF/>
                     requires that the listing certificate be provided to OCC no earlier than 12:01 a.m. and no later than 11:00 a.m. (Chicago time) on the trading day prior to the day on which trading is to begin.
                    <SU>5</SU>
                    <FTREF/>
                     The proposed amendment will still comport with that requirement. For example, if an initial public offering (“IPO”) occurs at 11 a.m. on Monday, the earliest date the Exchange could submit its listing certificate to OCC would be on Thursday by 12:01 a.m. (Chicago time), with the market price determined by the closing price over the three-day period from Monday through Wednesday. The option on the IPO would then be eligible for trading on the Exchange on Friday. The proposed amendment would essentially enable options trading within four business days of an IPO becoming available instead of six business days (five consecutive days plus the day the listing certificate is submitted to OCC).
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The Plan for the Purpose of Developing and Implementing procedures Designed to Facilitate the Listing and Trading of Standardized Options Submitted Pursuant to Section 11a(2)(3)(B) of the Securities Exchange Act of 1934 (a/k/a the Options Listing Procedures Plan (“OLPP”)) is a national market system plan that, among other things, sets forth procedures governing the listing of new options series.
                    </P>
                    <P>
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 44521 (July 6, 2001), 66 FR 36809 (July 13, 2001) (Order approving OLPP). The sponsors of OLPP include Phlx; OCC; BATS Exchange, Inc.; BOX Options Exchange LLC; C2 Options Exchange, Incorporated; Chicago Board Options Exchange, Incorporated; EDGX Exchange, Inc.; Miami International Securities Exchange, LLC; MIAX PEARL, LLC; The NASDAQ Stock Market LLC; NASDAQ BX, Inc.; Nasdaq GEMX, LLC; Nasdaq ISE, LLC; Nasdaq MRX, LLC; NYSE American, LLC; and NYSE Arca, Inc.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         OLPP at page 3.
                    </P>
                </FTNT>
                <P>
                    At the time the Exchange adopted the “look back” period of five consecutive business days, it determined that the five-day period was sufficient to protect against attempts to manipulate the market price of the underlying security and would provide a reliable test for stability.
                    <SU>6</SU>
                    <FTREF/>
                     Surveillance technologies and procedures concerning manipulation have evolved since then to provide adequate prevention or detection of rule or securities law violations within the proposed time frame, and the Exchange represents that its existing trading surveillances are adequate to monitor the trading of options on the Exchange.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release Nos. 47190 (January 15, 2003), 68 FR 3072 (January 22, 2003) (SR-CBOE-2002-62); 47352 (February 11, 2003), 68 FR 8319 (February 20, 2003) (SR-PCX-2003-06); 47483 (March 11, 2003), 68 FR 13352 (March 19,2003) (SR-ISE-2003-04); 47613 (April 1, 2003), 68 FR 17120 (April 8, 2003) (SR-Amex-2003-19); and 47794 (May 5, 2003), 68 FR 25076 (May 9, 2003) (SR-Phlx-2003-27)
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Such surveillance procedures generally focus on detecting securities trading subject to opening price manipulation, closing price manipulation, layering, spoofing or other unlawful activity impacting an underlying security, the option, or both. The Exchange, through the Financial Industry Regulatory Authority (“FINRA”), has price movement alerts, unusual market activity and order book alerts active for all trading symbols. These real time patterns are active for the new security as soon as the IPO begins trading.
                    </P>
                </FTNT>
                <P>Furthermore, the Exchange notes that the scope of its surveillance program also includes cross market surveillance for trading that is not just limited to the Exchange. In particular, the Financial Industry Regulatory Authority (“FINRA”), pursuant to a regulatory services agreement, operates a range of cross-market equity surveillance patterns on behalf of the Exchange to look for potential manipulative behavior, including spoofing, algorithm gaming, marking the close and open, and momentum ignition strategies, as well as more general, abusive behavior related to front running, wash shales, quoting/routing, and Reg SHO violations. These cross-market patterns incorporate relevant data from various markets beyond the Exchange, including data from the New York Stock Exchange (“NYSE”) and from the Nasdaq Stock Market (“Nasdaq”).</P>
                <P>
                    Additionally, for options, the Exchange, through FINRA, utilizes an array of patterns that monitor manipulation of options, or manipulation of equity securities (regardless of venue) for the purpose of impacting options prices on BOX options facility (
                    <E T="03">i.e.,</E>
                     mini-manipulation strategies). Accordingly, the Exchange believes that the cross market surveillance performed by FINRA on behalf of the Exchange, coupled with the Exchange staff's real-time monitoring of similarly violative activity on the exchange as described herein, reflects a comprehensive surveillance program that is adequate to monitor for manipulation of the underlying security and overlying option within the proposed three-day look back period.
                </P>
                <P>
                    Furthermore, the Exchange notes that the proposed listing criteria would still require that the underlying security be listed on NYSE, the American Stock Exchange (now known as NYSE American), or the National Market System of The Nasdaq Stock Market (now known as the Nasdaq Global Market) (collectively, the “Named Markets”), as provided for in the definition of “covered security” from Section 18(b)(1)(A) of the 1933 Act.
                    <SU>8</SU>
                    <FTREF/>
                     Accordingly, the Exchange believes that the proposed rule change would still ensure that the underlying security meets the high listing standards of a Named Market, and would also ensure that the underlying is covered by the regulatory protections (including market surveillance, investigation and enforcement) offered by these exchanges for trading in covered securities conducted on their facilities.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         15 U.S.C. 77r(b)(1)(A).
                    </P>
                </FTNT>
                <P>
                    Furthermore, according to Phlx's approved proposal, the Nasdaq, had no cases, within a five year period ending in 2018, where an IPO-related issue for which it had pricing information qualified for the $3.00 price requirement during the first three (3) days of trading and did not qualify for the $3.00 price requirement during the first five (5) days.
                    <SU>9</SU>
                    <FTREF/>
                     In other words, none of these qualifying issues fell below the $3.00 threshold within the first three (3) or five (5) days of trading. As such, the Exchange believes that its existing surveillance technologies and procedures, coupled with Nasdaq's findings related to the IPO-related issues as described herein, adequately address potential concerns regarding possible manipulation or price stability within the proposed timeframe.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         There were over 750 IPO-related issues on Nasdaq within the past five years. Out of all of the issues with pricing information, there was only one issue that had a price below $3.00 during the first five consecutive business days. The Exchange notes, however, that Nasdaq allows for companies to list on the Nasdaq Capital Market at $2.00 or $3.00 per share in some instances, which was the case for this particular issue. 
                        <E T="03">See</E>
                         Nasdaq Rule 5500 Series for initial listing standards on the Nasdaq Capital Market. 
                        <E T="03">See also</E>
                         supra note 3.
                    </P>
                </FTNT>
                <P>
                    The Exchange also believes that the proposed look back period can be implemented in connection with the other initial listing criteria for 
                    <PRTPAGE P="20942"/>
                    underlying covered securities. In particular, the Exchange recognizes that it may be difficult to verify the number of shareholders in the days immediately following an IPO due to the fact that stock trades generally clear within two business days (T+2) of their trade date and therefore the shareholder count will generally not be known until T+2.
                    <SU>10</SU>
                    <FTREF/>
                     The Exchange notes that the current T+2 settlement cycle was recently reduced from T+3 on September 5, 2017 in connection with the Commission's amendments to Exchange Rule 15c6-1(a) to adopt the shortened settlement cycle,
                    <SU>11</SU>
                    <FTREF/>
                     and the look back period of three (3) consecutive business days proposed herein reflects this shortened T+2 settlement period. As proposed, stock trades would clear within T+2 of their trade date (
                    <E T="03">i.e.,</E>
                     within three (3) business days) and therefore the number of shareholders could be verified within three (3) business days, thereby enabling options trading within four (4) business days of an IPO (three (3) consecutive business days plus the day the listing certificate is submitted to OCC).
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         The number of shareholders of record can be validated by large clearing agencies such as the Depository Trust and Clearing Corporation (“DTCC”) upon the settlement date (
                        <E T="03">i.e.,</E>
                         T+2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release no. 78962 (September 28, 2016), 81 FR 69240 (October 5, 2016) (Amendment to Securities Transaction Settlement Cycle) (File No. S7-22-16).
                    </P>
                </FTNT>
                <P>Furthermore, the Exchange notes that various brokerage firms that have a large retail customer clientele can confirm the number of individual customers who have a position in new issues. The earliest that these firms can provide confirmation is usually the day after the first day of trading (T+1) on an unsettled basis, while others can confirm on the third day of trading (T+2). For the foregoing reasons, the Exchange believes that basing the proposed three (3) business day look back period on the T+2 settlement cycle would allow for sufficient verification of the number of shareholders.</P>
                <P>
                    The proposed rule change will apply to all covered securities that meet the criteria of Rule 5020. Pursuant to Rule 5020, the Exchange establishes guidelines to be considered in evaluating the potential underlying securities for Exchange option transactions.
                    <SU>12</SU>
                    <FTREF/>
                     However, the fact that a particular security may meet the guidelines established by the Exchange does not necessarily mean that it will be approved as an underlying security.
                    <SU>13</SU>
                    <FTREF/>
                     As part of the established criteria, the issuer must be in compliance with any applicable requirement of the Securities Exchange Act of 1934.
                    <SU>14</SU>
                    <FTREF/>
                     Additionally, in considering the underlying security, the Exchange relies on information made publicly available by the issuer and/or the markets in which the security is traded.
                    <SU>15</SU>
                    <FTREF/>
                     Even if the proposed option meets the objective criteria, the Exchange may decide not to list, or place limitations or conditions upon listing.
                    <SU>16</SU>
                    <FTREF/>
                     The Exchange believes that these measures, together with its existing surveillance procedures, provide adequate safeguards in the review of any covered security that may meet the proposed criteria for consideration of the option within the timeframe contained in this proposal.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         Exchange Rule 5020. The Exchange established specific criteria to be considered in evaluating potential underlying securities for Exchange option transactions.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         Exchange Rule 5020(b)(3).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         Exchange Rule 5020(d).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See</E>
                         Exchange Rule 5020(b).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that the proposal is consistent with the requirements of Section 6(b) of the Securities Exchange Act of 1934 (the “Act”),
                    <SU>17</SU>
                    <FTREF/>
                     in general, and Section 6(b)(5) of the Act,
                    <SU>18</SU>
                    <FTREF/>
                     in particular, in that it is designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in facilitating transactions in securities, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general to protect investors and the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>
                    In particular, the Exchange believes that the proposed changes to its listing standards for covered securities would allow the Exchange to more quickly list options on a qualifying covered security that has met the $3.00 eligibility price without sacrificing investor protection. As discussed above, the Exchange believes that its existing trading surveillances provide a sufficient measure of protection against potential price manipulation within the proposed three (3) consecutive business day timeframe. The Exchange also believes that the proposed three (3) consecutive business day timeframe would continue to be a reliable test for price stability in light of Nasdaq's findings that none of the IPO-related issues on Nasdaq, within a five year time period ending in 2018, qualified for the $3.00 per share price standard during the first three trading days fell below the $3.00 threshold during the fourth or fifth trading day. Furthermore, the established guidelines to be considered by the Exchange in evaluating the potential underlying securities for Exchange option transactions,
                    <SU>19</SU>
                    <FTREF/>
                     together with existing trading surveillances, provide adequate safeguards in the review of any covered security that may meet the proposed criteria for consideration of the option within the proposed timeframe.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         notes 12-16 above.
                    </P>
                </FTNT>
                <P>
                    In addition, the Exchange believes that basing the proposed timeframe on the T+2 settlement cycle adequately addresses the potential difficulties in confirming the number of shareholders of the underlying covered security. For the foregoing reasons, the Exchange believes that the proposed amendments will remove impediments and perfect the mechanism of a free and open market and a national market system by providing an avenue for investors to swiftly hedge their investment in the stock in a shorter amount of time than what is currently in place.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         This proposed rule change does not alter any obligations of issuers or other investors of an IPO that may be subject to a lock-up or other restrictions on trading related securities.
                    </P>
                </FTNT>
                <P>
                    Finally, it should be noted that a price/time standard for the underlying security was first adopted when the listed options market was in its infancy, and was intended to prevent the proliferation of options being listed on low-priced securities that presented special manipulation concerns and/or lacked liquidity needed to maintain fair and orderly markets.
                    <SU>21</SU>
                    <FTREF/>
                     When options trading commenced in 1973, the Commission determined that it was necessary for securities underlying options to meet certain minimum standards regarding both the quality of the issuer and the quality of the market for a particular security.
                    <SU>22</SU>
                    <FTREF/>
                     These standards, including a price/time standard, were imposed to ensure that those issuers upon whose securities options were to be traded were widely-held, financially sound companies whose shares had trading volume and float substantial enough so as not to be readily susceptible to manipulation.
                    <SU>23</SU>
                    <FTREF/>
                     At the time, the Commission determined that the imposition of these standards was reasonable in view of the pilot nature of options trading and the 
                    <PRTPAGE P="20943"/>
                    limited experience of investors with options trading.
                    <SU>24</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 29628 (August 29, 1991), 56 FR 43949-01 (September 5, 1991) (SR-AMEX-86-21; SR-CBOE-86-15; SR-NYSE-86-20; SR-PSE86-15; and SR-PHLX-86-21) (“1991 Approval Order”) at 43949 (discussing the Commission's concerns when options trading initially commenced in 1973).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See</E>
                         1991 Approval Order at 43949.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    Now more than 40 years later, the listed options market has evolved into a mature market with sophisticated investors. In view of this evolution, the Commission has approved various exchange proposals to relax some of these initial listing standards throughout the years,
                    <SU>25</SU>
                    <FTREF/>
                     including reducing the price/time standard in 2003 from $7.50 per share for the majority of business days over a three month period to the current $3.00 per share/five business day standard (“2003 Proposal”).
                    <SU>26</SU>
                    <FTREF/>
                     It has been over sixteen years since the Commission approved the 2003 proposal, and both the listed options market and exchange technologies have continued to evolve since then. In this instance, the Exchange is only proposing a modest reduction of the current five (5) business day standard to three (3) business days to correspond to the securities industry's move to a T+2 standard settlement cycle.
                    <SU>27</SU>
                    <FTREF/>
                     The $3.00 per share standard and all other initial options listing criteria in Rule 5020 will remain unchanged by this proposal. For the reasons discussed herein, the Exchange therefore believes that the proposed three (3) business day period will be beneficial to the marketplace without sacrificing investor protections.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See e.g.,</E>
                         1991 Approval Order (modifying a number of initial listing criteria, including the reduction of the price/time standard from $10 per share each day during the preceding three calendar months to $7.50 per share for the majority of days during the same period).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release Nos. 47190 (January 15, 2003), 68 FR 3072 (January 22, 2003) (SR-CBOE-2002-62); 47352 (February 11, 2003), 68 FR 8319 (February 20, 2003) (SR-PCX-2003-06); 47483 (March 11, 2003), 68 FR 13352 (March 19, 2003) (SR-ISE-2003-04); 47613 (April 1, 2003), 68 FR 17120 (April 8, 2003) (SRAmex-2003-19); and 47794 (May 5, 2003), 68 FR 25076 (May 9, 2003) (SR-Phlx-200327).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See supra</E>
                         note 11.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>
                    The Exchange does not believe that the proposed rule change will impose any burden on competition not necessary or appropriate in furtherance of the purposes of the Act. In this regard and as indicated above, the Exchange notes that the rule change is being proposed as a competitive response to a filing submitted by Phlx that was approved by the Commission.
                    <SU>28</SU>
                    <FTREF/>
                     The proposed rule change will reduce the number of days to list options on an underlying security, and is intended to bring new options listings to the marketplace quicker.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See supra,</E>
                         note 3.
                    </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>The Exchange has neither solicited nor received comments on the proposed rule change.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    Because the foregoing proposed rule change does not: (i) Significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative for 30 days from the date on which it was filed, or such shorter time as the Commission may designate, it has become effective pursuant to Section 19(b)(3)(A)(iii) of the Act 
                    <SU>29</SU>
                    <FTREF/>
                     and subparagraph (f)(6) of Rule 19b-4 thereunder.
                    <SU>30</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6)(iii) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change, along with a brief description and the text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.
                    </P>
                </FTNT>
                <P>
                    A proposed rule change filed under Rule 19b-4(f)(6) 
                    <SU>31</SU>
                    <FTREF/>
                     normally does not become operative prior to 30 days after the date of the filing. However, Rule 19b-4(f)(6)(iii) 
                    <SU>32</SU>
                    <FTREF/>
                     permits the Commission to designate a shorter time if such action is consistent with the protection of investors and the public interest. The Exchange has asked the Commission to waive the 30-day operative delay so that the proposal may become operative immediately upon filing. The Exchange states that the waiver of the operative delay will ensure fair competition among the exchanges by allowing the Exchange to modify the criteria for listing an option on an underlying covered security which is currently allowed on other options exchanges. The Commission believes that waiver of the 30-day operative delay is consistent with the protection of investors and the public interest. Accordingly, the Commission hereby waives the operative delay and designates the proposed rule change as operative upon filing.
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         17 CFR 240.19b-4(f)(6)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         For purposes only of waiving the 30-day operative delay, the Commission has also considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <P>At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is: (i) Necessary or appropriate in the public interest; (ii) for the protection of investors; or (iii) otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings to determine whether the proposed rule should be approved or disapproved.</P>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-BOX-2019-15 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE, Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to File Number SR-BOX-2019-15. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's internet website (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of 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:00 a.m. and 3:00 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change. Persons submitting comments are cautioned that we do not redact or edit 
                    <PRTPAGE P="20944"/>
                    personal identifying information from comment submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-BOX-2019-15 and should be submitted on or before June 3, 2019.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>34</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>34</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Eduardo A. Aleman,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09724 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <SUBJECT>Sunshine Act Meetings</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">FEDERAL REGISTER CITATION OF PREVIOUS ANNOUNCEMENT:</HD>
                    <P>84 FR 19979, 7 May 2019.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PREVIOUSLY ANNOUNCED TIME AND DATE OF THE MEETING:</HD>
                    <P>Thursday, May 9, 2019 at 9:00 a.m.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CHANGES IN THE MEETING:</HD>
                    <P>The following item will not be considered during the Open Meeting on Thursday, May 9, 2019:</P>
                    <P>• Whether to propose certain rule amendments and interpretive guidance regarding the cross-border application of certain security-based swap requirements under the Securities Exchange Act of 1934 that were added by Title VII of the Dodd-Frank Wall Street Reform and Consumer Protection Act.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION:</HD>
                    <P>For further information and to ascertain what, if any, matters have been added, deleted or postponed, please contact the Office of the Secretary at (202) 551-5400.</P>
                </PREAMHD>
                <SIG>
                    <DATED>Dated: May 8, 2019.</DATED>
                    <NAME>Vanessa A. Countryman,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09894 Filed 5-9-19; 11:15 am]</FRDOC>
            <BILCOD> BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <SUBJECT>Administrator's Line of Succession Designation, No. 1-A, Revision 37</SUBJECT>
                <P>This document replaces and supersedes “Line of Succession Designation No. 1-A, Revision 36”.</P>
                <P>Line of Succession Designation No. 1-A, Revision 37:</P>
                <P>Effective immediately, the Administrator's Line of Succession Designation is as follows:</P>
                <P>(a) In the event of my inability to perform the functions and duties of my position, or my absence from the office, the Deputy Administrator will assume all functions and duties of the Administrator. In the event the Deputy Administrator and I are both unable to perform the functions and duties of the position or are absent from our offices, I designate the officials in listed order below, if they are eligible to act as Administrator under the provisions of the Federal Vacancies Reform Act of 1998 (5 U.S.C. 3345-3349d), to serve as Acting Administrator with full authority to perform all acts which the Administrator is authorized to perform:</P>
                <P>(1) Chief of Staff;</P>
                <P>(2) General Counsel;</P>
                <P>(3) Associate Administrator, Office of Capital Access;</P>
                <P>(4) Associate Administrator, Office of Disaster Assistance;</P>
                <P>(5) Regional Administrator for Region IX; and</P>
                <P>(6) Regional Administrator for Region VIII.</P>
                <P>Notwithstanding the provisions of SBA Standard Operating Procedure 00 01 2, “absence from the office,” as used in reference to myself in paragraph (a) above, means the following:</P>
                <P>(1) I am not present in the office and cannot be reasonably contacted by phone or other electronic means, and there is an immediate business necessity for the exercise of my authority; or</P>
                <P>(2) I am not present in the office and, upon being contacted by phone or other electronic means, I determine that I cannot exercise my authority effectively without being physically present in the office.</P>
                <P>(b) An individual serving in an acting capacity in any of the positions listed in subparagraphs (a)(1) through (6), unless designated as such by the Administrator, is not also included in this Line of Succession. Instead, the next non-acting incumbent in the Line of Succession shall serve as Acting Administrator.</P>
                <P>(c) This designation shall remain in full force and effect until revoked or superseded in writing by the Administrator, or by the Deputy Administrator when serving as Acting Administrator.</P>
                <P>(d) Serving as Acting Administrator has no effect on the officials listed in subparagraphs (a)(1) through (6), above, with respect to the authorities, duties, and responsibilities of their full-time positions (except that such official cannot both recommend and approve an action).</P>
                <SIG>
                    <NAME>Christopher M. Pilkerton,</NAME>
                    <TITLE>Acting Administrator.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09775 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF STATE</AGENCY>
                <DEPDOC>[Public Notice: 10768]</DEPDOC>
                <SUBJECT>Advisory Committee for the Study of Eastern Europe and the Independent States of the Former Soviet Union (Title VIII) Public Meeting Notice</SUBJECT>
                <P>The Advisory Committee for the Study of Eastern Europe and the Independent States of the Former Soviet Union (Advisory Committee) will convene on Wednesday, June 26, from 1:30 p.m. until approximately 3:30 p.m. The meeting will take place at the U.S. Department of State, Harry S Truman Building, 2201 C Street NW, Washington, DC, in Room 1485.</P>
                <P>
                    The Advisory Committee will recommend grant recipients for the 2019 funding opportunity for the Program for the Study of Eastern Europe and the Independent States of the Former Soviet Union, in accordance with the Research and Training for Eastern Europe and the Independent States of the Former Soviet Union Act of 1983, Public Law 98-164, as amended. The agenda will include opening statements by the chairperson and members of the committee. The committee will provide an overview and discussion of grant proposals from “national organizations with an interest and expertise in conducting research and training concerning the countries of Eastern Europe and the Independent States of the Former Soviet Union,” based on the guidelines set forth in the June request for proposals published on 
                    <E T="03">Grants.gov</E>
                     and SAMS Domestic (
                    <E T="03">mygrants.service-now.com</E>
                    ). Following committee deliberation, interested members of the public may make oral statements concerning the Title VIII program.
                </P>
                <P>
                    This meeting will be open to the public; however, attendance is limited to available seating. Entry into the Harry S Truman building is controlled and must be arranged in advance of the meeting. Those planning to attend should notify the Title VIII Program Officer at the U.S. Department of State at 
                    <E T="03">TitleVIII@state.gov,</E>
                     subject: Public Meeting RSVP, no later than close of business, Tuesday, June 25, 2019.
                </P>
                <P>
                    For pre-clearance into the Harry S Truman building, the Title VIII Program Officer will request identifying data pursuant to Public Law 99-399 
                    <PRTPAGE P="20945"/>
                    (Omnibus Diplomatic Security and Antiterrorism Act of 1986), as amended; Public Law 107-56 (USA PATRIOT Act); and Executive Order 13356. This information is being collected pursuant to 22 U.S.C. 2651a and 22 U.S.C. 4802 for the purpose of screening and pre-clearing participants to enter the host venue at the U.S. Department of State, in line with standard security procedures for events of this size. The Department of State will use this information consistent with the routine uses set forth in the System of Records Notices for Security Records (State-36). Provision of this information is voluntary, but failure to provide accurate information may impede your ability to register for the event. Please see the Security Records System of Records Notice (State-36) at 
                    <E T="03">https://www.state.gov/documents/organization/242611.pdf</E>
                     for additional information.
                </P>
                <P>All attendees must use the 2201 C Street entrance and must arrive no later than 12:30 p.m. to pass through security before entering the building. The Program Officer cannot admit visitors who arrive without prior notification or without photo identification.</P>
                <SIG>
                    <NAME>Sidni J. Dechaine, </NAME>
                    <TITLE>Designated Federal Officer, Advisory Committee for Study of Eastern Europe and the Independent States of the Former Soviet Union. U.S Department of State. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09784 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4710-32-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF STATE</AGENCY>
                <DEPDOC>[Public Notice 10767]</DEPDOC>
                <SUBJECT>30-Day Notice of Proposed Information Collection: Request for Commodity Jurisdiction Determination</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for public comment and submission to OMB of proposed collection of information.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of State has submitted the information collection described below to the Office of Management and Budget (OMB) for approval. In accordance with the Paperwork Reduction Act of 1995 we are requesting comments on this collection from all interested individuals and organizations. The purpose of this Notice is to allow 30 days for public comment.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments directly to the Office of Management and Budget (OMB) up to June 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Direct comments to the Department of State Desk Officer in the Office of Information and Regulatory Affairs at the Office of Management and Budget (OMB). You may submit comments by the following methods:</P>
                    <P>
                        • 
                        <E T="03">Email: oira_submission@omb.eop.gov.</E>
                         You must include the DS form number, information collection title, and the OMB control number in the subject line of your message.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         202-395-5806. Attention: Desk Officer for Department of State.
                    </P>
                    <P>You must include the information collection title (Request for Commodity Jurisdiction Determination), form number (DS-4076), and the OMB control number (1405-0163) in all correspondence.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Direct requests for additional information regarding the collection listed in this notice, including requests for copies of the proposed collection instrument and supporting documents, to Andrea Battista, who may be reached at 
                        <E T="03">battistaal@state.gov</E>
                         via email or 202-663-3136 via phone.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P SOURCE="NPAR">
                    • 
                    <E T="03">Title of Information Collection:</E>
                     Request for Commodity Jurisdiction Determination.
                </P>
                <P>
                    • 
                    <E T="03">OMB Control Number:</E>
                     1405-0163.
                </P>
                <P>
                    • 
                    <E T="03">Type of Request:</E>
                     Revision of a Currently Approved Collection.
                </P>
                <P>
                    • 
                    <E T="03">Originating Office:</E>
                     Directorate of Defense Trade Controls (PM/DDTC).
                </P>
                <P>
                    • 
                    <E T="03">Form Number:</E>
                     DS-4076.
                </P>
                <P>
                    • 
                    <E T="03">Respondents:</E>
                     Any person requesting a commodity jurisdiction determination.
                </P>
                <P>
                    • 
                    <E T="03">Estimated Number of Respondents:</E>
                     600.
                </P>
                <P>
                    • 
                    <E T="03">Estimated Number of Responses:</E>
                     600.
                </P>
                <P>
                    • 
                    <E T="03">Average Time per Response:</E>
                     4 hours.
                </P>
                <P>
                    • 
                    <E T="03">Total Estimated Burden Time:</E>
                     2,400 annual hours.
                </P>
                <P>
                    • 
                    <E T="03">Frequency:</E>
                     On occasion.
                </P>
                <P>
                    • 
                    <E T="03">Obligation to Respond:</E>
                     Voluntary.
                </P>
                <P>We are soliciting public comments to permit the Department to:</P>
                <P>• Evaluate whether the proposed information collection is necessary for the proper functions of the Department.</P>
                <P>• Evaluate the accuracy of our estimate of the time and cost burden for this proposed collection, including the validity of the methodology and assumptions used.</P>
                <P>• Enhance the quality, utility, and clarity of the information to be collected.</P>
                <P>• Minimize the reporting burden on those who are to respond, including the use of automated collection techniques or other forms of information technology.</P>
                <P>Please note that comments submitted in response to this Notice are public record. Before including any detailed personal information, you should be aware that your comments as submitted, including your personal information, will be available for public review.</P>
                <HD SOURCE="HD1">Abstract of Proposed Collection</HD>
                <P>Pursuant to ITAR § 120.4, a person, as defined by ITAR § 120.14, may request a written determination from the Department of State stating whether a particular article or service is covered by the United States Munitions List (USML). Form DS-4076 is the means by which respondents may submit this request. Information submitted via DS-4076 will be shared with the Department of Defense, Department of Commerce, and other USG agencies, as needed, during the commodity jurisdiction process. Determinations will be made on a case-by-case basis based on the commodity's form, fit, function, and performance capability.</P>
                <HD SOURCE="HD1">Methodology</HD>
                <P>
                    Respondents must submit the DS-4076 electronically through DDTC's electronic system. Respondents may access the DS-4076 on DDTC's website, 
                    <E T="03">www.pmddtc.state.gov,</E>
                     under Commodity Jurisdictions (CJs).
                </P>
                <SIG>
                    <NAME>Karen M. Wrege,</NAME>
                    <TITLE>Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09827 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4710-25-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <DEPDOC>[Summary Notice No. 2019-23]</DEPDOC>
                <SUBJECT>Petition for Exemption; Summary of Petition Received; Bell Helicopter Textron</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice contains a summary of a petition seeking relief from specified requirements of Federal Aviation Regulations. The purpose of this notice is to improve the public's awareness of, and participation in, the FAA's exemption process. Neither publication of this notice nor the inclusion or omission of information in the summary is intended to affect the legal status of the petition or its final disposition.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on this petition must identify the petition docket number and must be received on or before June 3, 2019.</P>
                </DATES>
                <ADD>
                    <PRTPAGE P="20946"/>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send comments identified by docket number FAA-2018-0997 using any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov</E>
                         and follow the 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 20590-0001, 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">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">http://www.regulations.gov,</E>
                         as described in the system of records notice (DOT/ALL-14 FDMS), which can be reviewed at 
                        <E T="03">http://www.dot.gov/privacy.</E>
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         Background documents or comments received may be read at 
                        <E T="03">http://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 20590-0001, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jake Troutman, (202) 683-7788, Office of Rulemaking, Federal Aviation Administration, 800 Independence Avenue SW, Washington, DC 20591.</P>
                    <P>This notice is published pursuant to 14 CFR 11.85.</P>
                    <SIG>
                        <DATED>Issued in Washington, DC, on May 2, 2019.</DATED>
                        <NAME>Lirio Liu,</NAME>
                        <TITLE>Executive Director, Office of Rulemaking.</TITLE>
                    </SIG>
                    <HD SOURCE="HD1">Petition for Exemption</HD>
                    <P>
                        <E T="03">Docket No.:</E>
                         FAA-2018-0997.
                    </P>
                    <P>
                        <E T="03">Petitioner:</E>
                         Bell Helicopter Textron.
                    </P>
                    <P>
                        <E T="03">Section(s) of 14 CFR Affected:</E>
                         §§ 45.23(b); 45.27(a); 45.29; 61.113(a) &amp; (b); 91.9(b)(2); 91.119(c); 91.121; 91.151(b); &amp; 91.203(a) &amp; (b).
                    </P>
                    <P>
                        <E T="03">Description of Relief Sought:</E>
                         The proposed exemption, if granted, would allow the petitioner to operate the xFold DragonH vertical takeoff and landing unmanned aircraft system, with a maximum takeoff gross weight of 480 pounds. The operation will be in conjunction with a special airworthiness certificate in order to conduct operations for experimental research and development purposes at altitudes not greater than 400 feet above ground level, Class G airspace, within visual line of sight, and above an area of Palo Pinto County, Texas.
                    </P>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09824 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <DEPDOC>[Docket No. FAA-2019-0362]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Requests for Comments; Clearance of Renewed Approval of Information Collection: Renewal, Maintenance, Preventive Maintenance, Rebuilding, and Alteration</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, FAA invites public comments about our intention to request the Office of Management and Budget (OMB) approval to renew an information collection. The Information to be collected is necessary to insure the safety of the flying public. Documentation of maintenance repair actions record who, what, when, where and how of the task performed. All maintenance actions as well as documentation are required. This collection focuses on the Form 337 which is collected by the FAA. Other records for preventative maintenance, and logbook entries are not collected by the FAA serve as a responsibility of the owner to maintain in case of verification of airworthiness when seeking approvals or sale of the aircraft. This insures proper certification of personnel; proper tooling is utilized and accurate measures to insure safety. Total form 337s submitted in 2017 is 54,237. Total aircraft registrations on file is 289,490. It is estimated by the numbers collected one in every five aircraft have a 337 form submitted for major alteration and repairs performed. Each 337 takes approximately 1 hour.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be submitted by July 12, 2019.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Please send written comments:</P>
                    <P>
                        <E T="03">By Electronic Docket: www.regulations.gov</E>
                         (Enter docket number into search field).
                    </P>
                    <P>
                        <E T="03">By email:</E>
                         Jude Sellers, @
                        <E T="03">jude.n.sellers@faa.gov.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspect of this information collection, including (a) Whether the proposed collection of information is necessary for FAA's performance; (b) the accuracy of the estimated burden; (c) ways for FAA to enhance the quality, utility and clarity of the information collection; and (d) ways that the burden could be minimized without reducing the quality of the collected information. The agency will summarize and/or include your comments in the request for OMB's clearance of this information collection.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2120-0020.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Maintenance, Preventive Maintenance, Rebuilding, and Alteration.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     Aircraft maintenance logbooks and form 337.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Renewal of information collection.
                </P>
                <P>
                    <E T="03">Background:</E>
                     Title 14 CFR part 43 mandates information to be provided when an alteration or major repair is performed on an aircraft of United Sates registry. Submission of Form 337 is required for capture in the aircraft permanent records for current and future owners to substantiate the requirements of the regulations, prior to operation of the aircraft. Aircraft owners have the responsibility of documentation and submission of all maintenance records performed to their aircraft.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     289,490 Aircraft owners.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Response:</E>
                     1 hour.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     Industry Annual burden 54,237 man hours.
                </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on May 8, 2019.</DATED>
                    <NAME>Jude Sellers,</NAME>
                    <TITLE>Aviation Safety Inspector, AFS-350 General Aviation Maintenance Branch.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09770 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="20947"/>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. NHTSA-2018-0010, Notice 1]</DEPDOC>
                <SUBJECT>Spartan Motors USA, Inc, 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>
                        Spartan Motors USA, Inc (Spartan), has determined that certain model year (MY) 2015-2019 Spartan Specialty MM and K2 motorhome chassis do not fully comply with Federal Motor Vehicle Safety Standard (FMVSS) No. 121, 
                        <E T="03">Air Brake Systems.</E>
                         Spartan filed a noncompliance report dated December 18, 2017, subsequently petitioned NHTSA on January 15, 2018, for a decision that the subject noncompliance is inconsequential as it relates to motor vehicle safety. This document announces receipt of petition and offers the opportunity for public comment.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The closing date for comments on the petition is June 12, 2019.</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 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>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P SOURCE="NPAR">
                    <E T="03">I. Overview:</E>
                     Spartan has determined that certain MY 2015-2019 Spartan Specialty MM and K2 motorhome chassis do not fully comply with paragraph S5.1.2.1 of FMVSS No. 121, 
                    <E T="03">Air Brake Systems</E>
                     (49 CFR 571.121). Spartan filed a noncompliance report dated December 18, 2017, pursuant to 49 CFR part 573, 
                    <E T="03">Defect and Noncompliance Responsibility and Reports.</E>
                     Spartan subsequently petitioned NHTSA on January 15, 2018, 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 Noncompli</E>
                    ance.
                </P>
                <P>This notice of receipt of Spartan's petition is published under 49 U.S.C. 30118 and 30120 and does not represent any agency decision or other exercise of judgement concerning the merits of the petition.</P>
                <P>
                    <E T="03">II. Vehicles Involved:</E>
                     Approximately 414 MY 2015-2019 Spartan Specialty MM and K2 motorhome chassis manufactured between February 12, 2014, and December 11, 2017, are potentially involved.
                </P>
                <P>
                    <E T="03">III. Noncompliance:</E>
                     Spartan described the noncompliance as the combined volume of air in the service and supply reservoirs in the air brake system does not meet the required minimum of twelve times the combined volume of air from all service brake chambers as specified in paragraph S5.1.2.1 of FMVSS No. 121.
                </P>
                <P>
                    <E T="03">IV. Rule Requirements:</E>
                     Paragraph S5.1.2.1 of FMVSS No. 121, titled “
                    <E T="03">Air Brake Systems”</E>
                     includes the requirements relevant to this petition. The combined volume of all service reservoirs and supply reservoirs shall be at least 12 times the combined volume of all service brake chambers.
                </P>
                <P>
                    <E T="03">V. Summary Spartan's of Petition:</E>
                     Spartan described the subject noncompliance and stated its belief that the noncompliance is inconsequential as it related to motor vehicle safety.
                </P>
                <P>In support of its petition, Spartan submitted the following reasoning:</P>
                <P>1. Paragraph S5.1.2.1 of FMVSS No. 121, requires the combined volume of all service reservoirs and supply reservoirs to be at least 12 times the combined volume of all service brake chambers. The chassis affected by this condition are equipped with a T-24 brake chamber on the steer axle, T-30 brake chamber on the drive axle and T-16 brake chamber on the tag axle. In using the values in Table V of FMVSS No. 121, the cumulative air capacity of these brake chambers would be 404 cubic inches. Multiplying by 12, the needed air reservoir capacity would be 4,848 cubic inches. To better illustrate the issue, refer to the table below:</P>
                <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s50,12,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Brake chamber size</CHED>
                        <CHED H="1">FMVSS No. 121 Cu. In. (Table V)</CHED>
                        <CHED H="1">Number of chambers total Cu. In.</CHED>
                        <CHED H="1">Total Cu. In.</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">T-24</ENT>
                        <ENT>67</ENT>
                        <ENT>2</ENT>
                        <ENT>134</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">T-30</ENT>
                        <ENT>89</ENT>
                        <ENT>2</ENT>
                        <ENT>178</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <PRTPAGE P="20948"/>
                        <ENT I="01">T-16</ENT>
                        <ENT>46</ENT>
                        <ENT>2</ENT>
                        <ENT>92</ENT>
                    </ROW>
                    <ROW EXPSTB="02">
                        <ENT I="03">Total Chamber Cu. In.</ENT>
                        <ENT>404</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="05">Required Air Reservoir Capacity (using 12X Multiplier) Cu. In.</ENT>
                        <ENT>4,848</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="07">Spartan Actual Reservoir Capacity (Cu. In.)</ENT>
                        <ENT>4,674</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="09">Additional Capacity Needed (Cu. In.)</ENT>
                        <ENT>174</ENT>
                    </ROW>
                    <TNOTE>Cubic Inch—Cu. In.</TNOTE>
                </GPOTABLE>
                <P>In paragraph S5.1.1 of FMVSS No. 121, the vehicle is to be equipped with an air compressor of sufficient capacity to increase air pressure in the supply and service reservoirs from 85 psi to 100 psi when the engine is operating at the vehicle manufacturer's maximum recommended revolutions per minute (r.p.m.) within a time, in seconds, determined by the quotient (actual reservoir capacity × 25)/required reservoir capacity). In using this equation, vehicles subject to the condition represented in the table above, the air pressure would be required to go from 85 psi to 100 psi within 24 seconds (4,674 * 25)/4,848). Using the same equation and the required air reservoir capacity of 4848 cubic inches, the air pressure would need to increase from 85 psi to 100 psi within 25 seconds. Vehicles subject to the condition that has resulted in the non-compliance to paragraph S5.1.2.1 could increase air pressure from 85 psi to 100 psi in less than 6 seconds, well within the requirement of 25 seconds. Further, vehicles subject to this condition have a cut in pressure set at, or greater than, the minimum requirement of 100 psi.</P>
                <P>The impact of having 3.5 percent less air reservoir capacity than required, the difference in the cut in pressure requirement of only 1 second would appear to have an adverse consequence of a slight increase in air compressor cycling. However, this would be dependent on application of the service brakes.</P>
                <P>Motorhomes have a similar duty cycle to that of a tractor-trailer where they are driven at highway speeds with infrequent brake applications during such drives. Motorhomes also are largely driven from owner residences to campground locations throughout the traveling season.</P>
                <P>Given these brake applications would appear to be less frequent than those in stop and go applications. The lower than required capacity, with the one second difference time to increase air pressure, may not be noticeable by the driver and would not impact the braking performance of the vehicle.</P>
                <P>
                    2. 
                    <E T="03">Air System Warning:</E>
                     The completed motorhomes subject to this condition are equipped with two air gauges that monitor the air system pressure in both system 1 and system 2. In addition to the air gauges, there are both a warning light and audible alarm to alert the driver in the event of a low air condition.
                </P>
                <P>
                    In conclusion, Spartan stated that the actual air reservoir capacity in the affected motorhome chassis may be 3.5 percent less (174 cubic inches) than the calculated required amount. However, due to the duty cycle of a motorhome and the air compressor cycling, that is well within the required time using the equation from FMVSS No. 121, Spartan believes the noncompliance is inconsequential as it relates to motor vehicle safety. The less than required capacity does not appear to impact vehicle braking performance (
                    <E T="03">e.g.,</E>
                     stopping distance, brake application, and release timing). The completed vehicles are equipped with dual air gauges, a visual and audible warning system to alert the driver to a loss of air in the air brake system. Given the aforementioned, Spartan expressed the belief that the subject noncompliance is inconsequential as it relates to motor vehicle safety, and that 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, this decision only applies to the subject vehicles that Spartan no longer controlled at the time it determined that the noncompliance existed. However, the granting of 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 Spartan 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. 2019-09752 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4910-59-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. NHTSA-2017-0073; Notice 2; Docket No. NHTSA-2017-0100; Notice 2]</DEPDOC>
                <SUBJECT>FCA US LLC and Volkswagen Group of America, Inc., Grant of Petitions for Decision of Inconsequential Noncompliance</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration (NHTSA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Grant of petitions.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        FCA US LLC (FCA US), (formally known as: Chrysler Group LLC) and Volkswagen Group of America, Inc. (Volkswagen), have determined that certain Mopar Service seat belt assemblies sold to FCA dealers and Volkswagen dealers as replacement equipment in certain model year (MY) 1992-2018 FCA US motor vehicles and certain MY 2009-2018 Volkswagen Routan motor vehicles, do not fully comply with Federal Motor Vehicle Safety Standard (FMVSS) No. 209, 
                        <E T="03">Seat Belt Assemblies.</E>
                         The petitioners have requested that NHTSA deem the subject noncompliance inconsequential to motor vehicle safety. This document grants both petitions in full.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jack Chern, Office of Vehicle Safety 
                        <PRTPAGE P="20949"/>
                        Compliance, NHTSA, telephone 202-366-0661, facsimile 202-366-3081.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    I. 
                    <E T="03">Overview:</E>
                     FCA US has determined that certain Mopar Service seat belt assemblies sold to FCA dealers as replacement equipment in certain MY 1992-2018 FCA US motor vehicles do not fully comply with paragraphs S4.1(k) and S4.1(l) of FMVSS No. 209, 
                    <E T="03">Seat Belt Assemblies</E>
                     (49 CFR 571.209). FCA US filed a noncompliance report dated July 25, 2017, pursuant to 49 CFR part 573, 
                    <E T="03">Defect and Noncompliance Responsibility and Reports.</E>
                     FCA US also petitioned NHTSA on August 17, 2017, 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) &amp; 30120(h) and 49 CFR part 556, 
                    <E T="03">Exemption for Inconsequential Defect or Noncompliance.</E>
                     Notice of receipt of FCA US's petition was published with a 30-day public comment period, on December 7, 2017, in the 
                    <E T="04">Federal Register</E>
                     (82 FR 57814). No comments were received.
                </P>
                <P>
                    Volkswagen has determined that certain Mopar Service seat belt assemblies sold to Volkswagen dealers as replacement equipment in certain MY 2009-2018 Volkswagen Routan motor vehicles do not fully comply with paragraphs S4.1(k) and S4.1(l) of FMVSS No. 209. Volkswagen filed a noncompliance report dated November 8, 2017, pursuant to 49 CFR part 573. Volkswagen petitioned NHTSA on November 29, 2017, 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) &amp; 30120(h) and 49 CFR part 556. Notice of receipt of Volkswagen's petition was published with a 30-day public comment period, on March 21, 2018, in the 
                    <E T="04">Federal Register</E>
                     (83 FR 12458). No comments were received.
                </P>
                <P>
                    II. 
                    <E T="03">Equipment Involved:</E>
                     Approximately 1,900 replacement seat belt assemblies manufactured between June 25, 2008, and October 25, 2013 for installation in certain MY 2009-2018 Volkswagen Routan motor vehicles are potentially involved.
                </P>
                <P>Approximately 728,100 Mopar Service seat belt assemblies sold to FCA dealers as replacement equipment for use in the following FCA motor vehicles are potentially involved:</P>
                <FP SOURCE="FP-1">• 2010-2017 Ram 3500 Cab Chassis (“DD”)</FP>
                <FP SOURCE="FP-1">• 2016-2017 Ram 3500 Cab Chassis (“DF”)</FP>
                <FP SOURCE="FP-1">• 2010-2017 Ram 2500 (“DJ”)</FP>
                <FP SOURCE="FP-1">• 2010-2017 Ram 4500/5500 Cab Chassis (“DP”)</FP>
                <FP SOURCE="FP-1">• 2009-2017 Ram 1500 (“DS”)</FP>
                <FP SOURCE="FP-1">• 2010-2017 Ram 3500 (“D2”)</FP>
                <FP SOURCE="FP-1">• 2012-2017 Fiat 500 (“FF”)</FP>
                <FP SOURCE="FP-1">• 2009-2017 Dodge Journey (“JC”)</FP>
                <FP SOURCE="FP-1">• 2007-2017 Jeep Wrangler (“JK”)</FP>
                <FP SOURCE="FP-1">• 2014-2017 Jeep Cherokee (“KL”)</FP>
                <FP SOURCE="FP-1">• 2015-2017 Dodge Challenger (“LA”)</FP>
                <FP SOURCE="FP-1">• 2012-2017 Chrysler 300 (“LX”)</FP>
                <FP SOURCE="FP-1">• 2012-2017 Dodge Charger (“LD”)</FP>
                <FP SOURCE="FP-1">• 2008-2017 Jeep Compass (“MK”)</FP>
                <FP SOURCE="FP-1">• 2008-2017 Jeep Patriot (“MK”)</FP>
                <FP SOURCE="FP-1">• 2012-2017 Dodge Dart (“PF”)</FP>
                <FP SOURCE="FP-1">• 2015-2017 Chrysler 200 (“UF”)</FP>
                <FP SOURCE="FP-1">• 2008-2017 Chrysler Town &amp; Country (“RT”)</FP>
                <FP SOURCE="FP-1">• 2008-2017 Dodge Grand Caravan (“RT”)</FP>
                <FP SOURCE="FP-1">• 2017 Chrysler Pacifica (“RU”)</FP>
                <FP SOURCE="FP-1">• 2011-2017 Dodge Durango (“WD”)</FP>
                <FP SOURCE="FP-1">• 2011-2017 Jeep Grand Cherokee (“WK”)</FP>
                <FP SOURCE="FP-1">• 2013-2017 Dodge SRT Viper (“ZD”)</FP>
                <FP SOURCE="FP-1">• 2002-2008 Dodge Ram 1500 (“DR”)</FP>
                <FP SOURCE="FP-1">• 2004-2010 Dodge Durango (“HB”)</FP>
                <FP SOURCE="FP-1">• 2007-2010 Chrysler Aspen (“HG”)</FP>
                <FP SOURCE="FP-1">• 2005-2012 Dodge Dakota (“ND”)</FP>
                <FP SOURCE="FP-1">• 1994-2002 Dodge Ram 1500 (“BR”)</FP>
                <FP SOURCE="FP-1">• 1993-2004 Dodge Intrepid (“LH”)</FP>
                <FP SOURCE="FP-1">• 1993-2004 Chrysler Concorde (“LH”)</FP>
                <FP SOURCE="FP-1">• 1993-2004 Chrysler 300M (“LH”)</FP>
                <FP SOURCE="FP-1">• 1995-2005 Dodge Neon (“PL”)</FP>
                <FP SOURCE="FP-1">• 2006-2012 Dodge Caliber (“PM”)</FP>
                <FP SOURCE="FP-1">• 1997-2000 Plymouth Prowler (“PR”)</FP>
                <FP SOURCE="FP-1">• 2001-2002 Chrysler Prowler (“PR”)</FP>
                <FP SOURCE="FP-1">• 2001-2010 Chrysler PT Cruiser (“PT”)</FP>
                <FP SOURCE="FP-1">• 1992-2002 Dodge Viper (“SR”)</FP>
                <FP SOURCE="FP-1">• 2003-2010 Dodge Viper (“ZB”)</FP>
                <FP SOURCE="FP-1">• 1993-1998 Jeep Grand Cherokee (“ZJ”)</FP>
                <FP SOURCE="FP-1">• 2014-2018 Ram ProMaster (“VF”)</FP>
                <FP SOURCE="FP-1">• 2015-2018 Ram ProMaster City (“VM”)</FP>
                <FP SOURCE="FP-1">• 2015-2018 Jeep Renegade (“BU”)</FP>
                <FP SOURCE="FP-1">• 2015-2017 Fiat 500x (“FB”)</FP>
                <FP SOURCE="FP-1">• 2014-2017 Fiat 500L (“BF”)</FP>
                <FP SOURCE="FP-1">• 2016-2017 Alfa Romeo Giulia (“GA”)</FP>
                <FP SOURCE="FP-1">• 2015-2017 Alfa Romeo 4C (“4C”)</FP>
                <FP SOURCE="FP-1">• 2017 Fiat 124 Spider (“BA”)</FP>
                <P>
                    III. 
                    <E T="03">Noncompliance:</E>
                     The petitioners explain that the subject noncompliance involves the Mopar Service Seat Belt assemblies sold to both FCA US and Volkswagen dealerships for use or for subsequent resale to dealers, for repairs by dealership service technicians, or dealership retail customers for installation and replacement parts in certain FCA US and Volkswagen vehicles. Specifically, the subject seat belt assemblies were sold without the proper inclusion of the “I-Sheets” (
                    <E T="03">i.e.,</E>
                     “Installation instructions” and “Usage and maintenance instructions”), and therefore, do not meet all applicable requirements specified in paragraphs S4.1(k) and 4.1(l) of FMVSS No. 209.
                </P>
                <P>
                    IV. 
                    <E T="03">Rule Text:</E>
                     Paragraph S4.1(k) and S4.1(l) of FMVSS No. 209 includes the requirements relevant to this petition:
                </P>
                <EXTRACT>
                    <P>• A seat belt assembly, other than a seat belt assembly installed in a motor vehicle by an automobile manufacturer, shall be accompanied by an instruction sheet providing sufficient information for installing the assembly in a motor vehicle.</P>
                    <P>• The installation instructions shall state whether the assembly is for universal installation or for installation only in specifically stated motor vehicles, and shall include at least those items specified in SAE Recommended Practice J800c (1973) (incorporated by reference, see § 571.5).</P>
                    <P>• If the assembly is for use only in specifically stated motor vehicles, the assembly shall either be permanently and legibly marked or labeled with the following statement, or the instruction sheet shall include the following statement:</P>
                    <P>
                        ○ This seat belt assembly is for use only in [insert specific seating position(s), 
                        <E T="03">e.g.,</E>
                         “front right”] in [insert specific vehicle make(s) and model(s)].
                    </P>
                    <P>• A seat belt assembly or retractor shall be accompanied by written instructions for the proper use of the assembly, stressing particularly the importance of wearing the assembly snugly and properly located on the body, and on the maintenance of the assembly and periodic inspection of all components.</P>
                    <P>• The instructions shall show the proper manner of threading webbing in the hardware of seat belt assemblies in which the webbing is not permanently fastened. Instructions for a nonlocking retractor shall include a caution that the webbing must be fully extended from the retractor during use of the seat belt assembly unless the retractor is attached to the free end of webbing which is not subjected to any tension during restraint of an occupant by the assembly. Instructions for Type 2a shoulder belt shall include a warning that the shoulder belt is not to be used without a lap belt.</P>
                </EXTRACT>
                <P>
                    V. 
                    <E T="03">Summary of Petitions:</E>
                     The petitioners described the subject noncompliance and stated their belief that the noncompliance is, in each case, inconsequential as it relates to motor vehicle safety.
                </P>
                <P>In support, the petitioners submitted the following arguments:</P>
                <P>1. The subject seat belt assemblies are only sold to FCA US and Volkswagen authorized dealerships for installation as replacement seat belts in certain FCA US and Volkswagen motor vehicles. These assemblies are not sold to aftermarket auto parts distributors or retail outlets.</P>
                <P>
                    2. The subject seat belt assemblies are clearly labeled and identifiable by part number in both the FCA US part system and Volkswagen's parts catalogue for use on specific make, model, and model 
                    <PRTPAGE P="20950"/>
                    year vehicles, and for specific seating positions.
                </P>
                <P>3. In order to purchase these parts, the buyer would need to supply either the part assembly number or make, model, model year and seating position of the vehicle, thus, only the proper assembly would be sold to the end user.</P>
                <P>4. Installation of the seat belt assembly is a complex process in the modern motor vehicle, unlike the vehicles in the past that the provisions [paragraph S4.1 of FMVSS No. 209] were intended to address. The method of identification and the physical differences between belt retractors and attachment hardware, as well as the vehicle installation environment, preclude the misinstallation of seat belt assemblies.</P>
                <P>5. FCA US states that the proper installation procedure for all Mopar Service Seat Belt assemblies are clearly described in FCA US service manuals, which are also available online through DealerCONNECT and sold to the public through Mopar and FCA US brand websites. With respect to seat belt usage and installation instructions, FCA US stated that consumers who have purchased the seat belt assemblies in the past can contact the Parts Department at their dealer for a copy of the Instruction Sheets at no cost. FCA US also stated that instructions and information regarding proper usage, proper maintenance, and periodic inspection for damaged seat belts are included in the vehicle's Owner's Manual.</P>
                <P>6. Volkswagen stated that their seat belt assembly installation instructions are included in Volkswagen Service Manuals and are available to independent repair shops and to individual owners, who can also purchase the Service Manual (which is a paid subscription) or seek dealer assistance and obtain copies of the installation instructions free of charge, if necessary. The instructions are also available on Parts on Command (POC) and can be printed, in house, at the dealership free of charge for the customers. In most cases, reference to the installation instructions will not be necessary because the seat belt installation will be to replace an existing belt and the installation procedure will just be the reverse of the removal procedure. With respect to seat belt usage and maintenance instructions, Volkswagen also stated that they have been included in all Volkswagen owners' manuals.</P>
                <P>7. FCA US has notified its dealer of the existence of the noncompliance and the dealer will be automatically prompted to include the Service Instructions Sheets at the time when a customer purchases a seat belt assembly.</P>
                <P>8. Volkswagen stated that the packaging for the supplied service seat belts should have been accompanied by the instruction sheet, however, because there was insufficient information to confirm that the instruction sheet accompanied the affected service parts. Volkswagen has determined to notify its dealers of the existence of the noncompliance. Volkswagen also stated that the instructions are now available on Parts on Command (POC) and can be printed free of charge at the dealership. These instruction sheets are required to be provided with every safety belt assembly or safety belt buckle sold- whether it be retail, wholesale, or in the shop.</P>
                <P>9. The petitioners are not aware of any incidents or consumer complaints relating to the absence of the I-Sheet and use instructions with the sale of any of the subject seat belt assemblies.</P>
                <P>FCA US and Volkswagen stated that there have been many instances of similar documentation omissions where the agency has granted inconsequential treatment. The petitioners cited the following examples: Mitsubishi Motors North America, Inc. (77 FR 24762, April 25, 2012); Bentley Motors, Inc. (75 FR 35877, September 20, 2011); Hyundai Motor Company (73 FR 49238, March 2, 2009); Ford Motor Company (73 FR 11462, March 3, 2008); Mazda North America Operations (73 FR 11464, March 3, 2008); Ford Motor Company (73 FR 63051, October 22, 2008); and TRW, Inc. (58 FR 7171, February 4, 1993).</P>
                <P>FCA stated that the most notable grant of inconsequential treatment is Subaru of America, Inc. (65 FR 67471, November 9, 2000), where the agency made the following succinct observations:</P>
                <EXTRACT>
                    <P>There seems to be little need for the installation instructions with replacements for original equipment seat belts. The SAE J800c Recommended Practice incorporated in FMVSS No. 209 appears to have been written as a guide on how to install a seat belt where one does not exist. The Recommended Practice discusses such things as how to determine the correct location for anchorages, how to create adequate anchorages and how to properly attach webbing to the newly installed anchorages. These instructions do not apply to today's replacement market. Additionally, vehicle manufacturers provide service manuals on how seat belts should be replaced. NHTSA does not believe the “how to” instructions are necessary in this case. Next, we note that the subject seat belt assemblies were distributed without the required 'usage and maintenance instructions' specified in FMVSS No. 209, S4.1(l), which requires that seat belt assemblies sold as replacement equipment have owner instructions on how to wear the seat belt and how to properly thread the webbing on seat belts where the webbing is not permanently attached. NHTSA believes that the proper usage is adequately described in the vehicle owner's manual. NHTSA does not believe that instructions about the proper threading of webbing is applicable to modern original equipment automobile seat belt systems. This second instruction sheet is either duplicated in the owner's manual or not applicable.</P>
                </EXTRACT>
                <P>
                    The FCA US understands that while they may believe FMVSS No. 209 S4.1(k) and S4.1(l) are somewhat antiquated, it is nevertheless required to fully comply with this safety standard. In this regard, the petitioners have made process changes to ensure that hard copies of the I-Sheets will be included with all seat belt assemblies shipped to its dealers. FCA US has implemented changes in its part ordering process to ensure that all I-Sheets for Mopar Service Seat Belt assemblies affected by recall T49 (NHTSA 17E-039) have been uploaded to online resources (StarParts
                    <E T="51">TM</E>
                     and DealerCONNECT) and directly linked to the specific Mopar Service Seat Belt part numbers. Going forward, this hard copy and on-line mating of the service parts and S4.1(k) and S4.1(l) instructions will ensure that the documentation requirement of FMVSS No. 209 will be met.
                </P>
                <P>The petitioners concluded by expressing the belief that the subject noncompliance is inconsequential as it relates to motor vehicle safety, and that their petitions 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>
                    VI. 
                    <E T="03">NHTSA's Analysis:</E>
                     To help ensure proper installation, usage, and maintenance of seat belt assemblies, paragraphs S4.1(k) and S4.1(l) of FMVSS No. 209 require that installation, usage, and maintenance instructions be provided with seat belt assemblies other than those installed by an automobile manufacturer.
                </P>
                <P>
                    First, with respect to the need to allow consumers to select the correct seat belt for their vehicle, we note that the subject seat belt assemblies are only made available to FCA US and Volkswagen authorized dealerships for their use or subsequent resale. Because the parts ordering process used by FCA US and Volkswagen authorized dealerships clearly identifies the correct service part by a vehicle's model, model year, and seating position, NHTSA believes that it is unlikely that an inappropriate seat belt assembly will be 
                    <PRTPAGE P="20951"/>
                    sold by the FCA US and Volkswagen dealership for a specific seating position within a vehicle.
                </P>
                <P>Second, NHTSA recognizes the importance of having installation instructions available to installers as well as use and maintenance instructions available to consumers. The risk created by this noncompliance is that someone who purchased an assembly is unable to obtain the necessary installation information and therefore incorrectly installs the seat belt assembly. We note that technicians at dealerships have access to the seat belt assembly installation instructions in vehicle Service Manuals. Installers other than dealership technicians can obtain a copy of the installation instructions, free of charge, through the dealerships' network. The installation instructions are also available in the docket because they were submitted with the manufacture's petitions. FCA US and Volkswagen also stated that the subject seat belt assemblies can only be properly installed in the correct seat position of their intended vehicles. Thus, we conclude that installers have reasonable opportunities to locate installation instructions which would permit a proper installation, and that the instructions can be obtained free of charge.</P>
                <P>In addition, NHTSA takes this opportunity to clarify prior statements concerning SAE Recommended Practice J800c. Paragraph S4.1(k) of FMVSS No. 209 requires “at least those items specified in SAE Recommended Practice J800c” be included in seat belt assembly instructions. As stated in SAE J800c, the “minimum instruction requirements may be supplemented by more specific manufacturer's instructions, if they are necessary to provide installation instructions in a particular vehicle.” Although mainly containing universal seat belt assembly installation instructions, SAE J800c acknowledges seat belt assemblies intended for installation in specific vehicles may require additional installation instructions. Also, per FMVSS No. 209, seat belt assembly intended for installation in specific vehicles must also have installation instructions provided when a seat belt assembly is not sold as an original item on a motor vehicle. To fulfill this intent, we conclude, as detailed in the previous paragraph, that installers should be able to obtain installation instructions which would permit a proper installation, and that the instructions can be obtained free of charge.</P>
                <P>With respect to seat belt usage and maintenance instructions, we note that this information is readily available in the vehicle owner's manuals. In addition, consumers can also obtain this information, free of charge, through the vehicle's dealership networks. Thus, with respect to usage and maintenance instructions, it appears that there are satisfactory alternatives to meeting the intent of S4.1(l) of FMVSS No. 209.</P>
                <P>NHTSA has granted similar petitions for failure to comply with requirements pertaining to seat belt assembly installation and usage instruction. Refer to Ford Motor Company (73 FR 11462, March 3, 2008); Mazda North America Operations (73 FR 11464, March 3, 2008); Ford Motor Company (73 FR 63051, October 22, 2008); Subaru of America, Inc. (65 FR 67471, November 9, 2000); Bombardier Motor Corporation of America, Inc. (65 FR 60238, October 10, 2000); TRW, Inc. (58 FR 7171, February 4, 1993); and Chrysler Corporation, (57 FR 45865, October 5, 1992).</P>
                <P>
                    VII. 
                    <E T="03">NHTSA's Decision:</E>
                     In consideration of the foregoing, NHTSA finds that both FCA US and Volkswagen have met their burden of persuasion that the FMVSS No. 209 noncompliance is inconsequential as it relates to motor vehicle safety. Accordingly, FCA US and Volkswagen's petitions are hereby granted and FCA US and Volkswagen are consequently exempted from the obligation to provide notification of, and remedy for, the subject noncompliance under 49 U.S.C. 30118 and 30120.
                </P>
                <P>NHTSA notes that the statutory provisions (49 U.S.C. 30118(d) and 30120(h)) that permit manufacturers to file petitions for a determination of inconsequentiality allows NHTSA to exempt manufacturers only from the duties found in sections 30118 and 30120, respectively, to notify owners, purchasers, and dealers of a defect or noncompliance and to remedy the defect or noncompliance. Therefore, this decision only applies to the subject equipment that FCA US and Volkswagen no longer controlled at the time it determined that the noncompliance existed. However, the granting of this petition does not relieve equipment distributors and dealers of the prohibitions on the sale, offer for sale, or introduction or delivery for introduction into interstate commerce of the noncompliant equipment under their control after FCA US and Volkswagen notified them that the subject noncompliance existed.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> (49 U.S.C. 30118, 30120: delegations of authority at 49 CFR 1.95 and 501.8)</P>
                </AUTH>
                <SIG>
                    <NAME>Otto G. Matheke III,</NAME>
                    <TITLE>Director, Office of Vehicle Safety Compliance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09751 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4910-59-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. NHTSA-2018-0004; Notice 1]</DEPDOC>
                <SUBJECT>Daimler Trucks North America, LLC, 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>
                        Daimler Trucks North America, LLC (DTNA), has determined that certain model year (MY) 2013-2018 Thomas Built Buses do not fully comply with Federal Motor Vehicle Safety Standard (FMVSS) No. 222, 
                        <E T="03">School Bus Passenger Seating and Crash Protection</E>
                        . DTNA filed a noncompliance report dated November 27, 2017. DTNA in Collaboration with SynTec Seating Solutions, LLC “SynTec” (the seating manufacturer), subsequently petitioned NHTSA on December 15, 2017, and later updated it on September 21, 2018, for a decision that the subject noncompliance is inconsequential as it relates to motor vehicle safety. This document announces receipt of DTNA's petition.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The closing date for comments on the petition is June 12, 2019.</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 number cited in the title of this notice and 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 
                        <PRTPAGE P="20952"/>
                        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>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">I. Overview:</E>
                     DTNA has determined that certain MY 2013-2018 Thomas Built Buses do not fully comply with paragraph S5.3.1.3 of FMVSS No. 222, 
                    <E T="03">School Bus Passenger Seating and Crash Protection</E>
                     (49 CFR 571.222). DTNA filed a noncompliance report dated November 27, 2017, pursuant to 49 CFR part 573, 
                    <E T="03">Defect and Noncompliance Responsibility and Reports</E>
                    . DTNA subsequently petitioned NHTSA on December 15, 2017, and later amended it on September 21, 2018, 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 Noncompliance or Defect</E>
                    .
                </P>
                <P>This notice of receipt, of DTNA's petition, is published under 49 U.S.C. 30118 and 30120 and does not represent any agency decision or other exercise of judgment concerning the merits of the petition.</P>
                <P>
                    <E T="03">II. Buses Involved:</E>
                     Affected are approximately 3,222 MY 2013-2018 versions of the following Thomas Built Buses, manufactured between August 24, 2012, and May 1, 2017, specifically:
                </P>
                <FP SOURCE="FP-1">• Thomas Built Buses Saf-T-Liner C2</FP>
                <FP SOURCE="FP-1">• Thomas Built Buses Saf-T-Liner EFX</FP>
                <FP SOURCE="FP-1">• Thomas Built Buses Saf-T-Liner HDX</FP>
                <FP SOURCE="FP-1">• Thomas Built Buses Minotour DRW</FP>
                <P>
                    <E T="03">III. Noncompliance:</E>
                     DTNA explains that the noncompliance is that the subject buses are equipped with seats that have Type 2 (lap/shoulder) seat belts, manufactured by SynTec Seating Solutions, LLC (SynTec), that do not meet the head form force distribution impact requirement as specified in paragraph S5.3.1.3 of FMVSS No. 222. Specifically, the Type 2 seat belts include a plastic bezel, where the seat belt is routed through the seat, located within the head protection zone.
                </P>
                <P>
                    <E T="03">IV. Rule Requirements:</E>
                     Paragraph S5.3.1.3 of FMVSS No. 222, titled “Head form force distribution” includes the requirements relevant to this petition:
                </P>
                <EXTRACT>
                    <P>• When any contactable surface of the vehicle within the zones specified in paragraph S5.3.1.1 is impacted from any direction at 6.7 m/s by the head form described in paragraph S6.6, the energy necessary to deflect the impacted material shall be not less than 4.5 joules before the force level on the head form exceeds 667 N.</P>
                    <P>
                        • When any contactable surface within such zones is impacted by the head form from any direction at 1.5 m/s the contact area on the head form surface shall be not less than 1,935 mm
                        <SU>2</SU>
                        .
                    </P>
                </EXTRACT>
                <P>
                    <E T="03">V. Summary of DTNA's Petition:</E>
                     DTNA described the subject noncompliance and stated its belief that the noncompliance is inconsequential as it relates to motor vehicle safety.
                </P>
                <P>DTNA provided the following background information:</P>
                <P>1. In January 2011, SynTec introduced the M2K lap/shoulder seat in order to provide a number of additional safety features to passengers. The company sold 2,272 M2K lap/shoulder seats to Thomas Built Buses before discontinuing the product in 2012. SynTec then improved upon the M2K lap/shoulder seat design with the S3C seat, which the Company introduced in 2012. The back of these seats are substantially higher than earlier school bus passenger seats and are equipped with lap/shoulder seat belts. The seat also includes: Color coding and key buckles to prevent improper buckling, a fixed buckle anchorage to prevent side occupant incursion, flip up buckles in pockets to be out of the way from debris, high shoulder anchorage, and contoured seat cushion. The plastic “bezel” (the location from which the lap/shoulder harness exits the seat back) was intentionally set high on the seat fronts to provide protection to the maximum range of occupants. Some M2K and S3C seats also are equipped with an integrated child seat.</P>
                <P>2. To ensure that the Affected Seats complied with all laws and regulations, SynTec contracted with a third party, MGA Research Corporation (“MGA”), to conduct certification testing under FMVSS No. 222. Specifically, MGA conducted tests on the M2K seat in June 2011, and on the S3C seat in August 2012. The M2K and S3C complied with FMVSS No. 222 requirements with respect to the back of the seat. Consistent with the industry norm and MGA's past practice, MGA did not test targets on the front of the seat. Based on its interactions and conversations with MGA, SynTec understood that back seat-only testing represents the industry norm. Front of the seat testing is not conducted due to the low risk of harm from the front, and because the small head impact zone makes it impossible to conduct the test per the recommended test procedure. Indeed, as referenced above, the testing was designed to ensure that the back of the seat was an energy absorber and that various hazards were eliminated from the top. Nonetheless, these early MGA tests results, specifically, the product's head injury criterion (HIC) values and the strong contact area and impact velocity scores on the back of the seat, highlighted the improved safety benefits of SynTec's new seat design.</P>
                <P>In support of its petition, DTNA provided the following:</P>
                <P>1. The S5.3.1.3 tests are outmoded for the front of the seat and the equipment's HIC scores represent the most accurate accounting of the seat's safety.</P>
                <P>
                    2. As highlighted above, the original intent of the contact surface test was to precipitate the elimination of metal grab bars and other hostile objects above the passenger seats that could come into contact with the occupant's head in the event of a crash. 
                    <E T="03">See</E>
                     38 FR 4776 (Feb. 22, 1973) (Proposed Rule) (stating the goal of “eliminating exposed metal bars and similar designs and making the seat itself a significant energy absorber.”) Likewise, the energy deflection analysis 
                    <PRTPAGE P="20953"/>
                    was designed to ensure that the seat would depress and distribute the force of impact in a manner that could not be achieved with exposed metal surfaces on the seat.
                </P>
                <P>3. Although SynTec was noncompliant with these two tests, the requirements are now outmoded with respect to the front of the affected seats because the various hazards they are seeking to guard against no longer exist. Indeed, the noncompliance did not occur because of a hazard that the regulations were designed to protect against. Rather, as explained below, the noncompliance resulted from a high-placed bezel that actually makes the affected seats safer for more occupants. The two tests were crafted for a school bus seat design that was substantially different and less safe than the superior versions that exist in the market today.</P>
                <P>
                    4. Given that these tests are outmoded, the most accurate measure of head safety for the front of the seat is the product's HIC value. The HIC is the most widely accepted measure of head injury in use today. Indeed, it is the standard measure of head injury throughout the FMVSSs. 
                    <E T="03">See, e.g.,</E>
                     FMVSS No. 201 and 208. Similarly, HIC is the metric used by NHTSA's New Car Assessment Program. 
                    <E T="03">See</E>
                     80 FR 78522, 78533 (2015) (noting that the HIC value “is currently in use in FMVSS No. 208 and frontal NCAP tests.”) The HIC measure is particularly valuable since it accounts for energy absorption and contact area by measuring the deceleration of the head form over time.
                </P>
                <P>5. Over the past few years, both SynTec and NHTSA, internally and at accredited external test agencies, have conducted HIC testing on the front of the affected seats. During testing, the seats were positioned at various angles, and impacts were performed on multiple locations of the seat within the head protection zone “hits”, including on the portion of the plastic bezel that protrudes into the top 76 mm on the front. These test results always produced a HIC value well below 1,000. For instance, since March 2017 SynTec has conducted 253 “hits” on the front of the seat. The average HIC value during these tests was 114.1, with a low score of 51.7 and a high HIC value of 311.8. Even the product's highest HIC value falls far short of the 1,000 maximum requirement. These values illustrate the safety of SynTec's product and the inconsequentiality of the noncompliance with the other FMVSS No. 222 test requirements.</P>
                <P>
                    6. Simply stated, the tests which prompted DTNA and SynTec's 573 Reports, are searching for hazards on the front of the seat that do not exist in the affected seats. 
                    <E T="03">See</E>
                     38 FR 4776 (Feb. 22, 1973) (Proposed Rule). As the product's HIC values show, the technical noncompliance of the SynTec seats on these two tests is not relevant to the product's safety. Accordingly, NHTSA should grant this petition for inconsequentiality.
                </P>
                <P>7. The source of SynTec's noncompliance enhances the product's safety. SynTec's seats are safer than regulators could have envisioned in 1976. Indeed, the cause of the noncompliance, the location of the plastic bezel, renders the seat safer than it would be with a bezel that was not placed in the head protection zone. This higher positioning combined with higher seat backs provides a belt for a maximum range of occupants and keeps hard objects away from the most vulnerable passengers. SynTec utilized automotive best practices and BELFIT software from the Motor Industry Research Association to determine the optimum geometric place for the belt position. SynTec's objective was to provide maximum protection, taking into account the wide range of occupant sizes riding on a school bus. Based on this analysis, it placed the bezel at the higher portion of the seat. The position also allowed for more adjustment by the d-ring, for better torso restraint, and for a more comfortable fit (thereby encouraging use).</P>
                <P>8. The higher shoulder harnesses also keep hard surfaces away from small occupants who are most vulnerable. A typical occupant in the vehicle would have a greater chance of coming into contact with a lower bezel. In seats with lap/shoulder belts with a lower bezel, the bezel would land in a smaller occupant's head area. Similarly, most designs that include an integrated child seat, have a hard surface that sits behind a smaller occupant's head. In contrast, the affected seat's higher bezel location places the bezel outside of a smaller occupant's head area. Likewise, for smaller occupants using integrated child seats, the bezel also falls outside of the occupant head area. Essentially, the higher bezel ensures better protection for the most vulnerable riders. Rather than cause any safety issues, the noncompliance, which occurred because of the location of the plastic bezels, makes the affected seats safer.</P>
                <P>9. The noncompliance at issue relates to front-of-seat tests designed to address features that are no longer present in school buses, such as metal bars at the top of seat backs and low seat backs. Therefore, DTNA believes the noncompliance is inconsequential as it relates to school bus safety. Moreover, the location of the plastic bezel on the lap/shoulder belts, which is the source of the noncompliance, is actually a safety improvement, in that its high position allows for maximum occupant ranges and fit, and protects the smallest seat occupants. A typical occupant in the vehicle would have a greater chance of coming into contact with a compliant lower bezel.</P>
                <P>10. Thus, the design represents an enhanced level of safety for school bus occupants, especially younger passengers who are more vulnerable in the event of a crash. Consistent with the enhanced safety design of the lap/shoulder belt, DTNA is not aware of any complaints, injuries or reports of safety concerns regarding this issue.</P>
                <P>
                    11. 
                    <E T="03">NHTSA Precedents</E>
                    —DTNA notes that NHTSA has previously granted petitions for decisions of inconsequential noncompliance for a wide range of issues where a technical non-compliance exists, but does not create a negative impact on safety. In the case detailed within this petition, the lap/shoulder belt is an optional feature on the vast majority of school buses. When added, lap/shoulder belts increase the safety of the occupants as compared to a bus without passenger seatbelts. Also, the high bezel increases the child protection performance requirements by reducing the likelihood of an occupant coming into contact with the hard surface. The following examples are petitions for inconsequentiality that were granted by NHTSA and are described within this petition to support DTNA's argument that, while technically non-compliant, NHTSA has previously granted inconsequentiality for cases where an additional level of safety above the requirements of the standard is provided.
                </P>
                <P>
                    12. 
                    <E T="03">See</E>
                     70 FR 24464 (May 9, 2005), Docket No. NHTSA 2005-20545 (Grant of Petition for IC Corporation) for an example of a petition for inconsequentiality that was granted by NHTSA. In this instance, school buses were manufactured that were not compliant with FMVSS 217, but it was deemed inconsequential because it did not compromise safety. “. . . The Agency agrees with IC that in this case the noncompliance does not compromise safety in terms of emergency exit capability in proportion to maximum occupant capacity, access to side emergency doors, visibility of the exits, or the ability of bus occupants to exit after an accident.”
                </P>
                <P>
                    13. 
                    <E T="03">See also 63 FR 32694 (June 15, 1998),</E>
                     Docket No. NHTSA 98-3791 (Grant of Petition for New Flyer of America, Inc.) for another example of a petition for inconsequentiality that was 
                    <PRTPAGE P="20954"/>
                    granted. In this case, non-school buses were manufactured that were not compliant with FMVSS 217, but were granted inconsequentiality because the buses had additional safety features that were not required in the standard. The following quote is from NHTSA's notice granting the petition: “Thus, the buses have the minimum number of emergency exits required by FMVSS No. 217. However, these exits were not distributed properly. Instead of a second emergency exit on the right side, these buses have an additional roof exit. This additional roof exit would provide for much need emergency exit openings should the bus occupants need to evacuate due to a rollover incident. While this additional roof exit is not required by the standard, it does provide for an additional level of safety in the above situation. In consideration of the foregoing, NHTSA has decided that the applicant has met its burden of persuasion that the noncompliance it described above is inconsequential to motor vehicle safety.” Id.
                </P>
                <P>DTNA expressed the belief that the subject noncompliance is inconsequential as it relates to motor vehicle safety, and that 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 DTNA 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 DTNA 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. 2019-09753 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <SUBJECT>Quarterly Publication of Individuals, Who Have Chosen To Expatriate, as Required by Section 6039G</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice is provided in accordance with IRC section 6039G of the Health Insurance Portability and Accountability Act (HIPPA) of 1996, as amended. This listing contains the name of each individual losing United States citizenship (within the meaning of section 877(a) or 877A) with respect to whom the Secretary received information during the quarter ending March 31, 2019. For purposes of this listing, long-term residents, as defined in section 877(e)(2), are treated as if they were citizens of the United States who lost citizenship.</P>
                </SUM>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s75,r75,r75">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Last name</CHED>
                        <CHED H="1">First name</CHED>
                        <CHED H="1">Middle name/initials</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">ABDULSALAM</ENT>
                        <ENT>ABDULAZIZ</ENT>
                        <ENT>MOHAMMAD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ADAM</ENT>
                        <ENT>OMER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ADAMS</ENT>
                        <ENT>BONNIE</ENT>
                        <ENT>LEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ADAMS</ENT>
                        <ENT>JAMES</ENT>
                        <ENT>RUSSELL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ADAMS</ENT>
                        <ENT>SHARON</ENT>
                        <ENT>LORRAINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AGARI</ENT>
                        <ENT>KAZUMI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AGUR</ENT>
                        <ENT>ELLA</ENT>
                        <ENT>ARYIELA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AHERN</ENT>
                        <ENT>IAN</ENT>
                        <ENT>BRUCE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AHLI</ENT>
                        <ENT>MANAL</ENT>
                        <ENT>ALI MOHAMMAD DOAYA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AHN</ENT>
                        <ENT>GINA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AIRTH</ENT>
                        <ENT>KIMBERLY</ENT>
                        <ENT>DOREEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AJMONE-MARSAN</ENT>
                        <ENT>COSIMO</ENT>
                        <ENT>MARCO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AL HASHEM</ENT>
                        <ENT>ABDULMOHSEN</ENT>
                        <ENT>SHUKRI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ALCALA</ENT>
                        <ENT>SHERRY</ENT>
                        <ENT>EVE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ALDAEAJ</ENT>
                        <ENT>ABDULLAH</ENT>
                        <ENT>HAMAD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AL-JASER</ENT>
                        <ENT>SHAKIR</ENT>
                        <ENT>AHMAK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ALKEMA</ENT>
                        <ENT>SJOERD</ENT>
                        <ENT>CHRISTOPH MARTY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ALLAN</ENT>
                        <ENT>ROSS</ENT>
                        <ENT>BRUCE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ALLEN</ENT>
                        <ENT>ROBIN</ENT>
                        <ENT>RENEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ALMUHANNA</ENT>
                        <ENT>AHMAD</ENT>
                        <ENT>NABEEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ALOSHBAN</ENT>
                        <ENT>GHASSAN</ENT>
                        <ENT>ABDUL-AZIZ</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AL-SALEH</ENT>
                        <ENT>HASHIM</ENT>
                        <ENT>ADNAN ABDULLAH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ALTENBURG</ENT>
                        <ENT>LORENZ</ENT>
                        <ENT>BERNARDEAU</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ALURWAR</ENT>
                        <ENT>ANJALI</ENT>
                        <ENT>ANADRAO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AMBERG</ENT>
                        <ENT>CARLETON</ENT>
                        <ENT>STARK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AMBROSIONI</ENT>
                        <ENT>PIERLUCA</ENT>
                        <ENT>MARIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDERSON</ENT>
                        <ENT>CHIARA</ENT>
                        <ENT>LENA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDERSON</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>BRIAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDERSON</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>MICHAEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDERSON</ENT>
                        <ENT>MEGAN</ENT>
                        <ENT>P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDERSON-KNIGHT</ENT>
                        <ENT>HANNAH</ENT>
                        <ENT>E.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANGELL</ENT>
                        <ENT>BARBARA</ENT>
                        <ENT>JOY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANGLETON</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT>NICHOLAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANLIKER</ENT>
                        <ENT>VERENA</ENT>
                        <ENT>GERTRUDE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANSEL</ENT>
                        <ENT>TRUDY</ENT>
                        <ENT>MARGIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANSLOW</ENT>
                        <ENT>JUNE</ENT>
                        <ENT>ARLENE</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20955"/>
                        <ENT I="01">AOKI</ENT>
                        <ENT>MASAHIKO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ARIVAZHAGAN</ENT>
                        <ENT>KUGAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ARKIN</ENT>
                        <ENT>FATIMA</ENT>
                        <ENT>MALCAMPO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ASHTON</ENT>
                        <ENT>MICHELE</ENT>
                        <ENT>ANN HESKETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AVIAD</ENT>
                        <ENT>JACOB</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AWWAD</ENT>
                        <ENT>SARA</ENT>
                        <ENT>ABDELKARIM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BAIER</ENT>
                        <ENT>KRYSTAL</ENT>
                        <ENT>ROSE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BAIRD</ENT>
                        <ENT>DAYLE</ENT>
                        <ENT>ROBIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BAKER</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>LUTHER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BALAZ</ENT>
                        <ENT>BRIGITTA</ENT>
                        <ENT>ELFRIEDE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BALLANTINE</ENT>
                        <ENT>TANIA</ENT>
                        <ENT>NICOLE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BALLESTER, JR</ENT>
                        <ENT>RAUL</ENT>
                        <ENT>ELISEO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BARIL</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BARLIEB</ENT>
                        <ENT>YASMINE</ENT>
                        <ENT>NATHALIE F.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BARNES</ENT>
                        <ENT>SARA</ENT>
                        <ENT>KELLY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BARROS</ENT>
                        <ENT>RODRIGO</ENT>
                        <ENT>JUAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BARTHOLOMEW</ENT>
                        <ENT>GALINA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BARTOLOME PRIETO</ENT>
                        <ENT>MARIA</ENT>
                        <ENT>VICTORIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BASU</ENT>
                        <ENT>KAJARI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BAUMGARTNER</ENT>
                        <ENT>ELISABETH</ENT>
                        <ENT>NATHALIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BAX-GARMAN</ENT>
                        <ENT>TRICIA</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BAYLISS</ENT>
                        <ENT>CYNTHIA</ENT>
                        <ENT>S.M.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BECKER</ENT>
                        <ENT>BRADLEY</ENT>
                        <ENT>WILLIAMSON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BECK-OLIVER</ENT>
                        <ENT>KATHRYN</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BEGIN</ENT>
                        <ENT>GENEVIEVE</ENT>
                        <ENT>FRANCOISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BELAIEFF</ENT>
                        <ENT>WILSON</ENT>
                        <ENT>ANDREW</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BELISLE</ENT>
                        <ENT>KEVIN</ENT>
                        <ENT>VICTOR</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BENOIT</ENT>
                        <ENT>BEATRICE</ENT>
                        <ENT>ELAINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BERG</ENT>
                        <ENT>CELINE</ENT>
                        <ENT>ANNIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BERG</ENT>
                        <ENT>JASMINE</ENT>
                        <ENT>SOFIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BERNARD</ENT>
                        <ENT>MARIE</ENT>
                        <ENT>THERESA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BERNARDI</ENT>
                        <ENT>LEANDRO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BERNTHALER</ENT>
                        <ENT>NICKLAS</ENT>
                        <ENT>FLOYD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BERTHEAS</ENT>
                        <ENT>ALEXANDRE</ENT>
                        <ENT>EMMANUEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BEUTLER</ENT>
                        <ENT>THOMAS</ENT>
                        <ENT>CHRISTIAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BEZERRA</ENT>
                        <ENT>VICTORIA</ENT>
                        <ENT>DE MORAES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BHASIN</ENT>
                        <ENT>RAJESH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BIANCHI</ENT>
                        <ENT>WALTER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BIGOURET</ENT>
                        <ENT>VANESSA</ENT>
                        <ENT>MILLER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BLACKBURN</ENT>
                        <ENT>AVERIL</ENT>
                        <ENT>BRONWEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BLACKBURN</ENT>
                        <ENT>GEORGE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BLANC</ENT>
                        <ENT>CYRIL</ENT>
                        <ENT>ANDRE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BLANCO-HOUSTON</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>PATRICK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BOANO</ENT>
                        <ENT>JULIE</ENT>
                        <ENT>MARTINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BOHNERT</ENT>
                        <ENT>CHRISTINE</ENT>
                        <ENT>BARBARA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BOHNERT</ENT>
                        <ENT>UTE</ENT>
                        <ENT>IRENE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BOLLIGER</ENT>
                        <ENT>KATHARINA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BOLTON</ENT>
                        <ENT>ALAN</ENT>
                        <ENT>JAMES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BORAGNO</ENT>
                        <ENT>MARY</ENT>
                        <ENT>GLENN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BORAGNO</ENT>
                        <ENT>WILLIAM</ENT>
                        <ENT>REMO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BOREL</ENT>
                        <ENT>CORINNE</ENT>
                        <ENT>CHRISTIANE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BORES</ENT>
                        <ENT>MELANIE</ENT>
                        <ENT>CHARLOTTE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BOTTING</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BOUSCHER</ENT>
                        <ENT>KEITH</ENT>
                        <ENT>BRIAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BOUTIN</ENT>
                        <ENT>BARBARA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BOWERING</ENT>
                        <ENT>NORBERT</ENT>
                        <ENT>R.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRAGAGNOLO</ENT>
                        <ENT>BRITNEY</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRAGG</ENT>
                        <ENT>NATHAN</ENT>
                        <ENT>RIDGLEY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRAIN</ENT>
                        <ENT>IMOGEN</ENT>
                        <ENT>EMMA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRAMLEY</ENT>
                        <ENT>DONNA</ENT>
                        <ENT>PATRICIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRANDES</ENT>
                        <ENT>SIMEON</ENT>
                        <ENT>ETHAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BREMER</ENT>
                        <ENT>ELENA</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRENT</ENT>
                        <ENT>GAIL</ENT>
                        <ENT>FERRINGTON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BREVAL</ENT>
                        <ENT>PATRICK</ENT>
                        <ENT>CHARLES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRICKSON</ENT>
                        <ENT>REBECCA</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRIDGMAN</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>MITCHELL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRIND'AMOUR RIFFOU</ENT>
                        <ENT>CAMELIA</ENT>
                        <ENT>MACKENZIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BROCHU</ENT>
                        <ENT>DIANE</ENT>
                        <ENT>GISELE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRODERICK</ENT>
                        <ENT>SHANNON</ENT>
                        <ENT>LYNN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BROOKS</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>DEXTER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BROWN</ENT>
                        <ENT>GREGORY</ENT>
                        <ENT>SCOTT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRUGGMANN</ENT>
                        <ENT>RAPHAEL</ENT>
                        <ENT>LAWRENCE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRUSH</ENT>
                        <ENT>GARY</ENT>
                        <ENT>EUGENE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BUCHANAN</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>S.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20956"/>
                        <ENT I="01">BUCHWALD</ENT>
                        <ENT>KURT</ENT>
                        <ENT>ALEXANDER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BUNTON</ENT>
                        <ENT>ANTHONY</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BUNTON</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>PETER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BURCKHARDT</ENT>
                        <ENT>STEFAN</ENT>
                        <ENT>JURG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BURGI</ENT>
                        <ENT>CHRISTIAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BURKHARD</ENT>
                        <ENT>JENNIFER</ENT>
                        <ENT>BEATRIX</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BURKOM</ENT>
                        <ENT>BERNARD</ENT>
                        <ENT>LEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BURMANN</ENT>
                        <ENT>KATJA</ENT>
                        <ENT>MARIKA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BURNETT</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>GARY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BURTON</ENT>
                        <ENT>THOMAS</ENT>
                        <ENT>ELLIOT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BUTCHER</ENT>
                        <ENT>HARVEY</ENT>
                        <ENT>RAYMOND</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BUTLER</ENT>
                        <ENT>LORRAINE</ENT>
                        <ENT>SUE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BUURMAN</ENT>
                        <ENT>MARIA</ENT>
                        <ENT>WILHELMINA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BYRNE</ENT>
                        <ENT>FRANCIS</ENT>
                        <ENT>MICHAEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CAHILL</ENT>
                        <ENT>JENNIFER</ENT>
                        <ENT>MARGARET</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CALLENDER</ENT>
                        <ENT>LESLIE</ENT>
                        <ENT>LAUREN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CAMPBELL</ENT>
                        <ENT>SHAYNA</ENT>
                        <ENT>RAE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CAPALDI</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>WILLIAM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CAPE</ENT>
                        <ENT>HUNTER</ENT>
                        <ENT>ROBERT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CAPRIOTTI</ENT>
                        <ENT>JOSEPH</ENT>
                        <ENT>A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARLAN-RIDDELL</ENT>
                        <ENT>SHANNA</ENT>
                        <ENT>KIM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARTER</ENT>
                        <ENT>SANDRA</ENT>
                        <ENT>FRIEDERIKE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CASTELLI</ENT>
                        <ENT>CAROLINE</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CAUSER</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT>NORMAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHAMMAS</ENT>
                        <ENT>EDWARD</ENT>
                        <ENT>EMILE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHAN</ENT>
                        <ENT>JOANNA</ENT>
                        <ENT>MAN JUNG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHAN</ENT>
                        <ENT>PAUL</ENT>
                        <ENT>WAI BUN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHAN</ENT>
                        <ENT>STEPHANIE</ENT>
                        <ENT>WING KWAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHAPMAN</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>EUGENE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHARBONNEAU III</ENT>
                        <ENT>HERBERT</ENT>
                        <ENT>RAYMOND</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHARNOCK</ENT>
                        <ENT>ANGELA</ENT>
                        <ENT>HARRIET</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHARRON</ENT>
                        <ENT>DIANE</ENT>
                        <ENT>LORI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHASE</ENT>
                        <ENT>MONICA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHAURASIA</ENT>
                        <ENT>HARI</ENT>
                        <ENT>PRASAD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHAWORTH-MUSTERS</ENT>
                        <ENT>TESSA</ENT>
                        <ENT>MARY CATHERINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHEN</ENT>
                        <ENT>ANDREW</ENT>
                        <ENT>DEAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHEN</ENT>
                        <ENT>DEREK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHEN</ENT>
                        <ENT>LIAN</ENT>
                        <ENT>YUI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHENG</ENT>
                        <ENT>PI</ENT>
                        <ENT>YING CHARLOTTE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHEUNG</ENT>
                        <ENT>DENNIS</ENT>
                        <ENT>CHI KUN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHEW</ENT>
                        <ENT>ROSEMARY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHIRATHIVAT</ENT>
                        <ENT>BANGONCHOM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHO</ENT>
                        <ENT>ELAINE</ENT>
                        <ENT>KYUNGJA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHOI</ENT>
                        <ENT>CLIFF</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHOI</ENT>
                        <ENT>EUGENE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHONG</ENT>
                        <ENT>KAREN</ENT>
                        <ENT>KAM YEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHOQUARD</ENT>
                        <ENT>NOELLE</ENT>
                        <ENT>CATHERINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHORZEMPA</ENT>
                        <ENT>DANIEL</ENT>
                        <ENT>WALTER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHOW</ENT>
                        <ENT>GARY</ENT>
                        <ENT>EDWARD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHUAH</ENT>
                        <ENT>EDWIN</ENT>
                        <ENT>TZE YONG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHUN</ENT>
                        <ENT>ELYSE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHUNG</ENT>
                        <ENT>HAROLD</ENT>
                        <ENT>CHOI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHUNG</ENT>
                        <ENT>JULIANA</ENT>
                        <ENT>WENDY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CICERCHIA</ENT>
                        <ENT>EDITH</ENT>
                        <ENT>E.I.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CICERCHIA</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>ANTHONY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CLARK</ENT>
                        <ENT>REBECCA</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CLARK</ENT>
                        <ENT>SHEILA</ENT>
                        <ENT>E.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CLEGG</ENT>
                        <ENT>LAUREN</ENT>
                        <ENT>ELIZABETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CLEMENTS</ENT>
                        <ENT>BARBARA</ENT>
                        <ENT>V.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">COBBAN</ENT>
                        <ENT>PAUL</ENT>
                        <ENT>ARTHUR</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CODERRE</ENT>
                        <ENT>KIRBY</ENT>
                        <ENT>DANIEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CODERRE</ENT>
                        <ENT>PATRICIA</ENT>
                        <ENT>KAY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">COHEN</ENT>
                        <ENT>BAT-SHEVA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">COLEMAN</ENT>
                        <ENT>LORNA</ENT>
                        <ENT>MAE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">COLLIER</ENT>
                        <ENT>LESLIE</ENT>
                        <ENT>HELEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">COLONNELLO</ENT>
                        <ENT>DANIELE</ENT>
                        <ENT>CLAUDIO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CONLIN</ENT>
                        <ENT>ALISON</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CONNELLY</ENT>
                        <ENT>BUNGORN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CONNER</ENT>
                        <ENT>BRYAN</ENT>
                        <ENT>KEITH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CONNOLLY</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>FRANCIS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CONRADS</ENT>
                        <ENT>HANS-GEORG</ENT>
                        <ENT>PETER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CONSIDINE</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>M.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">COOKE</ENT>
                        <ENT>GRAHAM</ENT>
                        <ENT>ROLAND JAMESON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">COPTI</ENT>
                        <ENT>GEORGES</ENT>
                        <ENT>GABRIEL</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20957"/>
                        <ENT I="01">CORTELLI</ENT>
                        <ENT>GEORGIANA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">COUNIHAN</ENT>
                        <ENT>TIMOTHY</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">COWAN</ENT>
                        <ENT>EMILY</ENT>
                        <ENT>ROSE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">COX</ENT>
                        <ENT>MARTIN</ENT>
                        <ENT>ALLEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CRAIG</ENT>
                        <ENT>ANDREW</ENT>
                        <ENT>GORDON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CRANSTON</ENT>
                        <ENT>ROSS</ENT>
                        <ENT>DOUGLAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CRAWFORD</ENT>
                        <ENT>THOMAS</ENT>
                        <ENT>KEITH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CRESCI</ENT>
                        <ENT>BETTINA</ENT>
                        <ENT>ODETTE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CROMBEEN</ENT>
                        <ENT>BRANDON</ENT>
                        <ENT>JAMES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CRONKHITE</ENT>
                        <ENT>MELISSA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CROOK</ENT>
                        <ENT>NIKITA</ENT>
                        <ENT>ALICE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CROWLEY</ENT>
                        <ENT>ERIK</ENT>
                        <ENT>WIKSTROM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CROWTHER</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>RICHARD G.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CUNNINGHAM</ENT>
                        <ENT>MARY</ENT>
                        <ENT>CAROL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CUPERUS</ENT>
                        <ENT>ANN</ENT>
                        <ENT>REESER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CYPHER</ENT>
                        <ENT>RAYMOND</ENT>
                        <ENT>AARON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DAHN</ENT>
                        <ENT>JEFFERY</ENT>
                        <ENT>RAYMOND</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DANIEL</ENT>
                        <ENT>KIMBERLY</ENT>
                        <ENT>BETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DANIEL</ENT>
                        <ENT>MARK</ENT>
                        <ENT>JEFFREY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DANIEL</ENT>
                        <ENT>WENDY</ENT>
                        <ENT>JEAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">D'ARAGONA</ENT>
                        <ENT>ROBERTO</ENT>
                        <ENT>BILOTTI RUGGI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DE BOISSESON</ENT>
                        <ENT>VERONIQUE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DE CORDIER</ENT>
                        <ENT>JOELLE</ENT>
                        <ENT>KIRIT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DE COULON</ENT>
                        <ENT>ANDRE</ENT>
                        <ENT>ALAIN GUSTAVE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DE GRAZIA</ENT>
                        <ENT>MARCO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DE JESUS</ENT>
                        <ENT>FRANCESCA</ENT>
                        <ENT>KASANDRA TIU-LAUREL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DE JONGE</ENT>
                        <ENT>LODEWIJK</ENT>
                        <ENT>DANIEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DE LEEUW</ENT>
                        <ENT>MATTHEW</ENT>
                        <ENT>LEMUEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DE MOL VAN OTTERLOO</ENT>
                        <ENT>SCIPIO</ENT>
                        <ENT>ALEXANDER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DE SANTIS</ENT>
                        <ENT>MATTHEW</ENT>
                        <ENT>XAVIER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DE VILLA PUCKETT</ENT>
                        <ENT>AUDRA</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DECLUDT</ENT>
                        <ENT>AMAURY</ENT>
                        <ENT>ROBERT EMMANUEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DEHAAS</ENT>
                        <ENT>JOHANNES</ENT>
                        <ENT>JACOBUS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DEL GIUDICE VILLENA</ENT>
                        <ENT>SALVATORE</ENT>
                        <ENT>SIMON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DEL RICCIO</ENT>
                        <ENT>COSTANTINO</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DELARUE</ENT>
                        <ENT>CHRISTINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DELORME</ENT>
                        <ENT>CHLOE</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DEMENS</ENT>
                        <ENT>GORDON</ENT>
                        <ENT>PATRICK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DEMETRAKOPOULOS</ENT>
                        <ENT>DEMETRIOS</ENT>
                        <ENT>YORGO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DESAI</ENT>
                        <ENT>KEVIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DEWERPE</ENT>
                        <ENT>SARAH</ENT>
                        <ENT>KHANOUM SAOUD BECK SALAAM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DI LORENZO</ENT>
                        <ENT>MARGO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DICK</ENT>
                        <ENT>PHILIPPE</ENT>
                        <ENT>LUIZ</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DICKIE</ENT>
                        <ENT>SEAN</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DIETRICH BRAGG</ENT>
                        <ENT>ANNE</ENT>
                        <ENT>CATHERINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DIMMOCK</ENT>
                        <ENT>DANIEL</ENT>
                        <ENT>KENNETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DIMMOCK</ENT>
                        <ENT>NATASHA</ENT>
                        <ENT>LEIGH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DITLOVE</ENT>
                        <ENT>MARK</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DO</ENT>
                        <ENT>PETER</ENT>
                        <ENT>DUY DAT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DOEKSEN</ENT>
                        <ENT>THOMAS</ENT>
                        <ENT>VOLKERT FRISO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DOLLOIS</ENT>
                        <ENT>ANNE</ENT>
                        <ENT>MARIE MADELEINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DONNELLY</ENT>
                        <ENT>ANTHONY</ENT>
                        <ENT>FRANCIS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DORE</ENT>
                        <ENT>KATHRYN</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DOUGLAS</ENT>
                        <ENT>DANNY</ENT>
                        <ENT>V.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DOVELL</ENT>
                        <ENT>ANDREW</ENT>
                        <ENT>CLEMENT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DOYLE</ENT>
                        <ENT>SUSAN</ENT>
                        <ENT>KAYE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DREW</ENT>
                        <ENT>ELIZABETH</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DUGGAN</ENT>
                        <ENT>CAROL</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DUIJN</ENT>
                        <ENT>WOUTER</ENT>
                        <ENT>CHRISTIAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DUNCAN</ENT>
                        <ENT>JENNIFER</ENT>
                        <ENT>APRIL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DUNN</ENT>
                        <ENT>MATTHEW</ENT>
                        <ENT>GORDON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DUNNE</ENT>
                        <ENT>MARCELA</ENT>
                        <ENT>ISABEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DUNNETT</ENT>
                        <ENT>BRADLEY</ENT>
                        <ENT>RANDAL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DURAN</ENT>
                        <ENT>VICTOR</ENT>
                        <ENT>VLADIMIRO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DUTHOIT</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>PETER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ECKLER</ENT>
                        <ENT>SIBYLLE</ENT>
                        <ENT>MARIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EDAMURA</ENT>
                        <ENT>CAREN</ENT>
                        <ENT>MARGARET</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EING</ENT>
                        <ENT>PATRICIA</ENT>
                        <ENT>SOPHIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ELFORD</ENT>
                        <ENT>KIMBERLY</ENT>
                        <ENT>JOY-ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ELISIO</ENT>
                        <ENT>LUCIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ELLIOT</ENT>
                        <ENT>MARY</ENT>
                        <ENT>CLARE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ELSTE</ENT>
                        <ENT>DILLON</ENT>
                        <ENT>JEREMY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ENGELHARDT</ENT>
                        <ENT>LINDA</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ENJERGHOLI</ENT>
                        <ENT>SIROON</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20958"/>
                        <ENT I="01">ERDMANN-JONSSON</ENT>
                        <ENT>LARKEN</ENT>
                        <ENT>NOAH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ERICKSON</ENT>
                        <ENT>TIMOTHY</ENT>
                        <ENT>NEIL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ETTER</ENT>
                        <ENT>AUDREY</ENT>
                        <ENT>RENEE GARROW</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ETZKORN</ENT>
                        <ENT>WILLIAM</ENT>
                        <ENT>GEORGE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EVANS</ENT>
                        <ENT>ALICE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EVANS</ENT>
                        <ENT>MICHELE</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EZZ-ELARAB</ENT>
                        <ENT>OMAR</ENT>
                        <ENT>MOHAMED</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FABBRI</ENT>
                        <ENT>MARTA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FANDINO</ENT>
                        <ENT>ANSELMO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FARNSWORTH</ENT>
                        <ENT>RICHARD</ENT>
                        <ENT>T.D.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FASSLER</ENT>
                        <ENT>ELISABETH</ENT>
                        <ENT>CORNELIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FAURO-BOSSA</ENT>
                        <ENT>MARILISA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FEE</ENT>
                        <ENT>ERIC</ENT>
                        <ENT>PHILLIPS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FELTHAM</ENT>
                        <ENT>TAMMARA</ENT>
                        <ENT>SHERISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FERRARO</ENT>
                        <ENT>CHRISTOPHER</ENT>
                        <ENT>PETER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FIALA</ENT>
                        <ENT>EDWARD</ENT>
                        <ENT>CHESTER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FILA</ENT>
                        <ENT>JOANNA</ENT>
                        <ENT>CAROLINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FIORE</ENT>
                        <ENT>ANTHONY</ENT>
                        <ENT>ALBERT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FISK</ENT>
                        <ENT>MICHELE</ENT>
                        <ENT>MAUREEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FISZBAJN</ENT>
                        <ENT>AVITAL</ENT>
                        <ENT>RANA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FITZMARTYN</ENT>
                        <ENT>CHERYL</ENT>
                        <ENT>JOANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FLEISCHMANN</ENT>
                        <ENT>JULIE</ENT>
                        <ENT>THERESE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FLETCHER</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT>GORDON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FORCIER</ENT>
                        <ENT>STEPHANE</ENT>
                        <ENT>CLAUDE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FORD</ENT>
                        <ENT>JILL</ENT>
                        <ENT>ELIZABETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FORD</ENT>
                        <ENT>KAREN</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FORMANOY</ENT>
                        <ENT>ELIZABETH</ENT>
                        <ENT>C.E.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FORSYTHE</ENT>
                        <ENT>ALASDAIR</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FORTE</ENT>
                        <ENT>MARCUS</ENT>
                        <ENT>ALEXANDER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FRACCHIA</ENT>
                        <ENT>HELENA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FRANCONI</ENT>
                        <ENT>GIOVANNA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FRANK</ENT>
                        <ENT>LUCY</ENT>
                        <ENT>ELIZABETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FRASER-HARRIS</ENT>
                        <ENT>AYAME</ENT>
                        <ENT>HARMONY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FRECH</ENT>
                        <ENT>KAREN</ENT>
                        <ENT>JEAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FREDERICK</ENT>
                        <ENT>MARY</ENT>
                        <ENT>JO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FREI-HOFMANNER</ENT>
                        <ENT>KAREN</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FRIEDLICH</ENT>
                        <ENT>JANICE</ENT>
                        <ENT>CAROL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FRIEDMAN</ENT>
                        <ENT>TAMAR</ENT>
                        <ENT>KIM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FRIEDSON</ENT>
                        <ENT>WILLIAM</ENT>
                        <ENT>ANTHONY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FRITSCHI</ENT>
                        <ENT>TOBIAS</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FRITZ</ENT>
                        <ENT>PATRICK</ENT>
                        <ENT>ARTHUR</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FROEHLICH</ENT>
                        <ENT>STEVEN</ENT>
                        <ENT>WALTER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FURMAN</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>NOE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GADIENT-HOFMANN</ENT>
                        <ENT>ARLENE</ENT>
                        <ENT>DENISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GAGNON</ENT>
                        <ENT>CHANTAL</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GAGNON</ENT>
                        <ENT>LYNE</ENT>
                        <ENT>CHRISTINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GAGNON</ENT>
                        <ENT>PATRICK</ENT>
                        <ENT>MICHAEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GAILLARD</ENT>
                        <ENT>RICHARD</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GAM</ENT>
                        <ENT>GABRIEL</ENT>
                        <ENT>SHIH YEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GAMARD</ENT>
                        <ENT>SYLVAIN</ENT>
                        <ENT>LAURENT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GAMSGAARD</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>PATRICK DONOVAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GAMSGAARD</ENT>
                        <ENT>PETER</ENT>
                        <ENT>JOSEPH DONOVAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GARCIA-VEGA</ENT>
                        <ENT>LUIS</ENT>
                        <ENT>DANIEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GEHRING</ENT>
                        <ENT>THOMAS</ENT>
                        <ENT>CLAUDE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GEORGE</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>HILLES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GEORGE</ENT>
                        <ENT>KATHRYN</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GEORGE</ENT>
                        <ENT>MATTHEW</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GERATZ</ENT>
                        <ENT>THERESA</ENT>
                        <ENT>JEAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GERMAN</ENT>
                        <ENT>GREGORY</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GIBBS</ENT>
                        <ENT>GARY</ENT>
                        <ENT>CRISTOFER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GIBSON</ENT>
                        <ENT>MARIE</ENT>
                        <ENT>LORRAINE GABRIELLE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GIDDENS</ENT>
                        <ENT>JONATHAN</ENT>
                        <ENT>LEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GIFFORD</ENT>
                        <ENT>JAMIE</ENT>
                        <ENT>ANDREW</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GIGNAC</ENT>
                        <ENT>JEROME</ENT>
                        <ENT>AARON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GILDER</ENT>
                        <ENT>FIRUZEH</ENT>
                        <ENT>ARDESHIR</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GILLIS</ENT>
                        <ENT>MARY</ENT>
                        <ENT>BERNADETTE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GIOVANNETTI</ENT>
                        <ENT>JOANNE</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GLAZIER</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>ROSS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GLEESON</ENT>
                        <ENT>SEAMAS</ENT>
                        <ENT>PROINSIAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GLINZ</ENT>
                        <ENT>SVEN</ENT>
                        <ENT>SEBASTIAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GMOEHLING</ENT>
                        <ENT>THOMAS</ENT>
                        <ENT>WERNER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GO</ENT>
                        <ENT>FRANKLIN</ENT>
                        <ENT>LEELIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GO JR</ENT>
                        <ENT>FREDDIE</ENT>
                        <ENT>LEELIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GOETZINGER</ENT>
                        <ENT>CHESTER</ENT>
                        <ENT>WARREN</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20959"/>
                        <ENT I="01">GOFF</ENT>
                        <ENT>BERNICE</ENT>
                        <ENT>THERESA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GOGOLA</ENT>
                        <ENT>COLLEEN</ENT>
                        <ENT>CAROLINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GOLDSTEIN</ENT>
                        <ENT>MELVIN</ENT>
                        <ENT>EARL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GOMEZ</ENT>
                        <ENT>MARIA</ENT>
                        <ENT>ALEJANDRA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GONDER</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>THOMAS BURDICK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GOOD</ENT>
                        <ENT>BONNIE</ENT>
                        <ENT>B.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GOOD</ENT>
                        <ENT>JERRY</ENT>
                        <ENT>PAUL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GOOD</ENT>
                        <ENT>MARION</ENT>
                        <ENT>E.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GOOD GINGRICH</ENT>
                        <ENT>LUANN</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GORMAN</ENT>
                        <ENT>CATHERINE</ENT>
                        <ENT>EVA E.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GORYN</ENT>
                        <ENT>MINNA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GOUNTCHEV</ENT>
                        <ENT>TOMISLAV</ENT>
                        <ENT>IIKOV</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRAF</ENT>
                        <ENT>JOHANNES</ENT>
                        <ENT>KARL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRAMAGLIA</ENT>
                        <ENT>ANTOINE</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRATWOHL EGG</ENT>
                        <ENT>STEPHANIE</ENT>
                        <ENT>ELISABETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRECO-VOGELBACHER</ENT>
                        <ENT>CHANEL</ENT>
                        <ENT>DESIREE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GREEN</ENT>
                        <ENT>GEORGE</ENT>
                        <ENT>DAVID ARMSTRONG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GREEN</ENT>
                        <ENT>MARY</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GREENE</ENT>
                        <ENT>JUSTIS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GREENSPOON</ENT>
                        <ENT>FERN</ENT>
                        <ENT>RUTH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRENIER</ENT>
                        <ENT>JOSEPH</ENT>
                        <ENT>ROCH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRIFFITHS</ENT>
                        <ENT>LAWRENCE</ENT>
                        <ENT>RAYMOND DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GROSSMANN</ENT>
                        <ENT>SVENJA</ENT>
                        <ENT>KATHARINA SOPHIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GROVE</ENT>
                        <ENT>CYNTHIA</ENT>
                        <ENT>LOUISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GROVIT</ENT>
                        <ENT>FELIX</ENT>
                        <ENT>TIMUR ISMAIL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRUBAN</ENT>
                        <ENT>PATRICK</ENT>
                        <ENT>THOMAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRUNER-HEGGE</ENT>
                        <ENT>NICOLAI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GUDAITIS</ENT>
                        <ENT>ELIZABETH</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GUDAITIS</ENT>
                        <ENT>VITALIUS</ENT>
                        <ENT>VYTAUTAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GUDDAT-MORGEN</ENT>
                        <ENT>STEPHANIE</ENT>
                        <ENT>CHRISTINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GUILBERT</ENT>
                        <ENT>LARRY</ENT>
                        <ENT>JOE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GUILBERT</ENT>
                        <ENT>SANDRA</ENT>
                        <ENT>MAC NEY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GUNTHER</ENT>
                        <ENT>PHYLLIS</ENT>
                        <ENT>SONDRA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GURNEY</ENT>
                        <ENT>ALICIA</ENT>
                        <ENT>FRANCES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GUTIERREZ</ENT>
                        <ENT>SERGIO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GWILT</ENT>
                        <ENT>RICHARD</ENT>
                        <ENT>LLOYD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GWIN</ENT>
                        <ENT>MORRIS</ENT>
                        <ENT>KENT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HABECKER</ENT>
                        <ENT>DIANA</ENT>
                        <ENT>BERLY STEINSTO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HADLEY</ENT>
                        <ENT>JACOB</ENT>
                        <ENT>SINDING</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HALPERIN</ENT>
                        <ENT>ROSS</ENT>
                        <ENT>MARK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HAMMOND</ENT>
                        <ENT>KIMBERLY</ENT>
                        <ENT>GAY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HAN</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>JAI-YUN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HARMAN</ENT>
                        <ENT>AIMEE</ENT>
                        <ENT>NICOLE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HARMON</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>BARRY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HARTMAN</ENT>
                        <ENT>DANIEL</ENT>
                        <ENT>KARSTEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HARTNAGEL</ENT>
                        <ENT>JULIA</ENT>
                        <ENT>LYNN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HARTONAS-GARMHAUSEN</ENT>
                        <ENT>VASILIKI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HATHAWAY</ENT>
                        <ENT>CAROL</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HAWKSWORTH</ENT>
                        <ENT>LTA</ENT>
                        <ENT>JEAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HAYDICKY</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>PHILLIP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HAYDICKY</ENT>
                        <ENT>PHILLIP</ENT>
                        <ENT>JOSEPH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HAYES</ENT>
                        <ENT>MEGAN</ENT>
                        <ENT>EMILY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HAYHOE</ENT>
                        <ENT>RHONDA</ENT>
                        <ENT>LYNN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HAYTER</ENT>
                        <ENT>MARTHA</ENT>
                        <ENT>DEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HAYWARD</ENT>
                        <ENT>MARY</ENT>
                        <ENT>A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HECHTENTHAL</ENT>
                        <ENT>SARA</ENT>
                        <ENT>DAWN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HEFTI BLUM</ENT>
                        <ENT>ELIZABETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HEINEN</ENT>
                        <ENT>JOCELIN</ENT>
                        <ENT>DENIS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HEINZ</ENT>
                        <ENT>AGNES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HELLINGA</ENT>
                        <ENT>FRISO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HEMINGSON</ENT>
                        <ENT>DONNA</ENT>
                        <ENT>JUNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HENZ</ENT>
                        <ENT>LAURA</ENT>
                        <ENT>AUDREY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HERBERT</ENT>
                        <ENT>BENJAMIN</ENT>
                        <ENT>CADOC</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HERBOLD</ENT>
                        <ENT>PHILLIP</ENT>
                        <ENT>ARNOLD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HERRON</ENT>
                        <ENT>BRIAN</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HETZER</ENT>
                        <ENT>STEVEN</ENT>
                        <ENT>EDWARD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HEW</ENT>
                        <ENT>SHIRLEY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HILL</ENT>
                        <ENT>MARLENE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HILTI-BAYER</ENT>
                        <ENT>FLORIN</ENT>
                        <ENT>NICO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HILTON</ENT>
                        <ENT>ALEXANDER</ENT>
                        <ENT>PHILIP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HILTON</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>JAMES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HILTON</ENT>
                        <ENT>SAMANTHA</ENT>
                        <ENT>DAVIES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HILTZ</ENT>
                        <ENT>SARAH</ENT>
                        <ENT>CHRISTINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HIRST</ENT>
                        <ENT>CASSIUS</ENT>
                        <ENT>ATTICUS BAT</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20960"/>
                        <ENT I="01">HO</ENT>
                        <ENT>CATHY</ENT>
                        <ENT>CHIN HUA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HO</ENT>
                        <ENT>MICHELLE</ENT>
                        <ENT>MUN YEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HO</ENT>
                        <ENT>SOO</ENT>
                        <ENT>TENG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOCHSTRASSER</ENT>
                        <ENT>SUSAN</ENT>
                        <ENT>MARGARET</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HODEL</ENT>
                        <ENT>CHRISTOPHER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOFF-HACKER</ENT>
                        <ENT>ELLEN</ENT>
                        <ENT>LOUISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOFFMAN</ENT>
                        <ENT>GABRIELLE</ENT>
                        <ENT>MIKO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOFSTAETTER</ENT>
                        <ENT>THOMAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOGAN</ENT>
                        <ENT>CORMAC</ENT>
                        <ENT>NOEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOLME</ENT>
                        <ENT>MITCHELL</ENT>
                        <ENT>BRUCE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOMMEL</ENT>
                        <ENT>JOEL</ENT>
                        <ENT>PATRICK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HORGAN</ENT>
                        <ENT>MARY</ENT>
                        <ENT>FRANCES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HORLACHER</ENT>
                        <ENT>ZOE</ENT>
                        <ENT>HUFUMIAO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOSHINO</ENT>
                        <ENT>SAKI</ENT>
                        <ENT>KATHIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOSHINO</ENT>
                        <ENT>STEVEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOUSE</ENT>
                        <ENT>LORRAINE</ENT>
                        <ENT>GAIL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOUSEMAN</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>KEVIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOWARD</ENT>
                        <ENT>RONDA</ENT>
                        <ENT>LYN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUANG</ENT>
                        <ENT>JEFF</ENT>
                        <ENT>LITCHEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUANG</ENT>
                        <ENT>ZHI</ENT>
                        <ENT>HAO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUBER</ENT>
                        <ENT>HEIDI</ENT>
                        <ENT>LISA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUENI</ENT>
                        <ENT>NORA</ENT>
                        <ENT>JOSETTE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUGHES</ENT>
                        <ENT>ANDREA</ENT>
                        <ENT>KEDDIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HUMBEL</ENT>
                        <ENT>RUDOLF</ENT>
                        <ENT>NIKLAUS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HWANG</ENT>
                        <ENT>HYUNMEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">IJSSELHOP-BLAAUW</ENT>
                        <ENT>CLAIRE</ENT>
                        <ENT>B.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">INDERBITZIN</ENT>
                        <ENT>NIKLAUS</ENT>
                        <ENT>JOSHUA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">INOUE</ENT>
                        <ENT>YOSHIKO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">IRELAND</ENT>
                        <ENT>ALLYSON</ENT>
                        <ENT>J.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">IRVINE</ENT>
                        <ENT>BRENDON</ENT>
                        <ENT>ROBERT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">IRVINE</ENT>
                        <ENT>EVA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">IRWIN</ENT>
                        <ENT>SUSAN</ENT>
                        <ENT>MAREE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ISHIKAWA</ENT>
                        <ENT>KAZUKI</ENT>
                        <ENT>KEVIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ITEN-CANNIZZO</ENT>
                        <ENT>MARILYN</ENT>
                        <ENT>ANNA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ITHARAT</ENT>
                        <ENT>JILLIAN</ENT>
                        <ENT>L.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">IYENGAR</ENT>
                        <ENT>PRAKASH</ENT>
                        <ENT>KRISHNASWAMY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JABRE</ENT>
                        <ENT>JULIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JAEGER</ENT>
                        <ENT>JOLENE</ENT>
                        <ENT>MICHELLE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JAIN</ENT>
                        <ENT>ADINA</ENT>
                        <ENT>ALYCE KUMARI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JAMES</ENT>
                        <ENT>LESLIE</ENT>
                        <ENT>CAMERON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JANES</ENT>
                        <ENT>CHRISTINE</ENT>
                        <ENT>MARINA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JANSEN</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>ALAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JARZEBOWSKI</ENT>
                        <ENT>JERZY</ENT>
                        <ENT>MICHAL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JOHNSON</ENT>
                        <ENT>DARREN</ENT>
                        <ENT>WADE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JOHNSON</ENT>
                        <ENT>DOUGLAS</ENT>
                        <ENT>HUGH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JOHNSON</ENT>
                        <ENT>NADEAN</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JOHNSON</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT>LEON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JOHNSON-DEAN</ENT>
                        <ENT>CHRISTINA</ENT>
                        <ENT>BETTS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JOLY</ENT>
                        <ENT>KRISTINA</ENT>
                        <ENT>ISABEL MJELLEM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JONCKERS</ENT>
                        <ENT>MIRJAM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JONES</ENT>
                        <ENT>YANCY</ENT>
                        <ENT>DAMON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JORGENSEN</ENT>
                        <ENT>CATHERINE</ENT>
                        <ENT>A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JOST</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>ALFRED JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JUDELSON</ENT>
                        <ENT>AVILA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JULIEN</ENT>
                        <ENT>CHERYL</ENT>
                        <ENT>LANE COOPER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KAISER</ENT>
                        <ENT>LINDA</ENT>
                        <ENT>DIANE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KAM</ENT>
                        <ENT>JEFFREY</ENT>
                        <ENT>MAN-KIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KAMIYA</ENT>
                        <ENT>RYOHEI</ENT>
                        <ENT>CHRIS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KANE</ENT>
                        <ENT>JONATHAN</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KARLSEN</ENT>
                        <ENT>HAAKON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KATZ</ENT>
                        <ENT>ANNA</ENT>
                        <ENT>CAROLYN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KAUR</ENT>
                        <ENT>MANISHA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KAY</ENT>
                        <ENT>MATTHEW</ENT>
                        <ENT>RYAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KEEGAN</ENT>
                        <ENT>KAREN</ENT>
                        <ENT>TERESE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KELLOGG</ENT>
                        <ENT>SARAH</ENT>
                        <ENT>JACKSON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KELLY</ENT>
                        <ENT>WENDY</ENT>
                        <ENT>DAWN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KEMPE</ENT>
                        <ENT>PATRICIA</ENT>
                        <ENT>HOWE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KENNERLEY</ENT>
                        <ENT>STEVEN</ENT>
                        <ENT>WAYNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KENNETT</ENT>
                        <ENT>SHAUN</ENT>
                        <ENT>ALEXANDER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KHAN</ENT>
                        <ENT>SADAF</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KHOURI</ENT>
                        <ENT>JOHNNY</ENT>
                        <ENT>NABIH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KILLEWALD</ENT>
                        <ENT>SUSAN</ENT>
                        <ENT>KIMBERLY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KILPELA</ENT>
                        <ENT>CARLA</ENT>
                        <ENT>IRENE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KIM</ENT>
                        <ENT>HYEWON</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20961"/>
                        <ENT I="01">KIM</ENT>
                        <ENT>IN SOOK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KIM</ENT>
                        <ENT>IRENE</ENT>
                        <ENT>STEPHANIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KIM</ENT>
                        <ENT>JAY</ENT>
                        <ENT>SOO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KIM</ENT>
                        <ENT>PHILIP</ENT>
                        <ENT>YOUNG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KIM</ENT>
                        <ENT>PYONG</ENT>
                        <ENT>CHIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KIM</ENT>
                        <ENT>SONMI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KIM</ENT>
                        <ENT>TAE</ENT>
                        <ENT>HOON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KINGFISHER</ENT>
                        <ENT>CATHERINE</ENT>
                        <ENT>PELISSIER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KIRKNESS</ENT>
                        <ENT>LUCY</ENT>
                        <ENT>EMMA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KLASNER</ENT>
                        <ENT>AARON</ENT>
                        <ENT>MICHAEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KLEINENBERG</ENT>
                        <ENT>WILLEM</ENT>
                        <ENT>DOUWE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KLINE</ENT>
                        <ENT>GREGORY</ENT>
                        <ENT>ALAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KNAPP</ENT>
                        <ENT>DONALD</ENT>
                        <ENT>MORGAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KNAPPE</ENT>
                        <ENT>CAROLYN</ENT>
                        <ENT>HILDEGARD ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KNAUER</ENT>
                        <ENT>BRUCE</ENT>
                        <ENT>DOUGLAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KNAUER</ENT>
                        <ENT>JEFFREY</ENT>
                        <ENT>DONALD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KNOTT</ENT>
                        <ENT>CHERYL</ENT>
                        <ENT>LYNN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KNOTT, JR</ENT>
                        <ENT>JASON</ENT>
                        <ENT>EDWARD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KNUTTILA</ENT>
                        <ENT>MARIA</ENT>
                        <ENT>INEZ</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KO</ENT>
                        <ENT>KWANG</ENT>
                        <ENT>HYO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KOH</ENT>
                        <ENT>JARED</ENT>
                        <ENT>SIANG HAO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KOLSTER</ENT>
                        <ENT>MARITA</ENT>
                        <ENT>CLAIRE EMELY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KOMOROWSKI</ENT>
                        <ENT>ROMAN</ENT>
                        <ENT>J.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KONG</ENT>
                        <ENT>CAROLINE</ENT>
                        <ENT>SUNG-AH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KOO</ENT>
                        <ENT>VIVIAN</ENT>
                        <ENT>HUI LIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KOTZBAUER</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>HARALD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KOZAR, JR</ENT>
                        <ENT>DANIEL</ENT>
                        <ENT>PAUL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KREDA</ENT>
                        <ENT>JANET</ENT>
                        <ENT>LYNNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KREMB</ENT>
                        <ENT>AYLA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KRETLOW</ENT>
                        <ENT>JANIS</ENT>
                        <ENT>ELAIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KROG</ENT>
                        <ENT>BRONWYN</ENT>
                        <ENT>MARY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KRONE</ENT>
                        <ENT>JOACHIM</ENT>
                        <ENT>DIETER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KRONENTHAL</ENT>
                        <ENT>LINDA</ENT>
                        <ENT>HOPE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KRUEGER</ENT>
                        <ENT>DONALD</ENT>
                        <ENT>RAY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KRUEGER</ENT>
                        <ENT>ELAINE</ENT>
                        <ENT>SCHUMAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KRUEGER</ENT>
                        <ENT>LISA</ENT>
                        <ENT>GOMI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KUBO</ENT>
                        <ENT>TAKEHITO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KUNIMOTO</ENT>
                        <ENT>BRENDEN</ENT>
                        <ENT>COREY MASAYUKI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KUNIMOTO</ENT>
                        <ENT>DANIKA</ENT>
                        <ENT>CAROLINE RYOKO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KURILECZ</ENT>
                        <ENT>KATHLEEN</ENT>
                        <ENT>E.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KWAN</ENT>
                        <ENT>HENRY</ENT>
                        <ENT>JOSEPH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KWEON</ENT>
                        <ENT>HYUCK-JUN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAFUGE</ENT>
                        <ENT>MARINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAISSUE</ENT>
                        <ENT>WENDY</ENT>
                        <ENT>MICHELE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LALLI</ENT>
                        <ENT>CAROL</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAM</ENT>
                        <ENT>CALVIN</ENT>
                        <ENT>KIN-HENG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAPHAM CASHMAN</ENT>
                        <ENT>ROSEMARY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LARKIN</ENT>
                        <ENT>SEAN</ENT>
                        <ENT>PATRICK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAU</ENT>
                        <ENT>GAM</ENT>
                        <ENT>YONG NG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAU</ENT>
                        <ENT>TONY</ENT>
                        <ENT>TAK YIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAUKKANEN</ENT>
                        <ENT>TAHVO</ENT>
                        <ENT>DYLAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAURENT</ENT>
                        <ENT>ALEXIS</ENT>
                        <ENT>EMMANUEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAUXMANN</ENT>
                        <ENT>MARTIN</ENT>
                        <ENT>ALEXANDER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAW</ENT>
                        <ENT>ANITA</ENT>
                        <ENT>JILL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LE COCQ</ENT>
                        <ENT>MARIANA</ENT>
                        <ENT>LUCIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LE ROUX</ENT>
                        <ENT>REMI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEAMING</ENT>
                        <ENT>KENNETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEBOW</ENT>
                        <ENT>PHILLIP</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>CHEN</ENT>
                        <ENT>HUI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>CRYSTAL</ENT>
                        <ENT>LI-YONG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>DANIEL</ENT>
                        <ENT>SEUNG-KYU</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>GLORIA</ENT>
                        <ENT>RUNG BE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>HUN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>JONG</ENT>
                        <ENT>WOOK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>KA LAM</ENT>
                        <ENT>GARY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>PRISCILLA</ENT>
                        <ENT>YAN WEI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>SHERLYN</ENT>
                        <ENT>SHER LIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>WANDA</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LELONG</ENT>
                        <ENT>DOMINIQUE</ENT>
                        <ENT>CLAUDE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEONARD</ENT>
                        <ENT>ISAAC</ENT>
                        <ENT>EDWARD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEONARD</ENT>
                        <ENT>SARAH</ENT>
                        <ENT>M.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEVESQUE</ENT>
                        <ENT>PAUL</ENT>
                        <ENT>L.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEVI</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>ROBERT</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20962"/>
                        <ENT I="01">LEVINSON</ENT>
                        <ENT>JOSEPH</ENT>
                        <ENT>JAY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEVY</ENT>
                        <ENT>SUSAN</ENT>
                        <ENT>JESSICA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEWICKE</ENT>
                        <ENT>JUSTIN</ENT>
                        <ENT>CRYAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LIM</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>WARREN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LIN</ENT>
                        <ENT>CHAO-MEI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LIN</ENT>
                        <ENT>RICHARD</ENT>
                        <ENT>HSIOU</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LINDE</ENT>
                        <ENT>TEAL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LINK</ENT>
                        <ENT>LISA</ENT>
                        <ENT>LAYNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LIPTON</ENT>
                        <ENT>MITCHELL</ENT>
                        <ENT>GOODMAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LIT</ENT>
                        <ENT>HIU</ENT>
                        <ENT>YEUNG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LIYEUNG</ENT>
                        <ENT>LEO</ENT>
                        <ENT>L.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LOEHRL</ENT>
                        <ENT>VALENTINA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LOESCH</ENT>
                        <ENT>LARS</ENT>
                        <ENT>JUERGEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LOETTGEN</ENT>
                        <ENT>LUKAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LOEWER</ENT>
                        <ENT>SEBASTIAN</ENT>
                        <ENT>MATTHIAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LOGOZ</ENT>
                        <ENT>ANNETTE</ENT>
                        <ENT>CECILE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LOH</ENT>
                        <ENT>CHUNG</ENT>
                        <ENT>KIT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LOPEZ</ENT>
                        <ENT>ASHLEY</ENT>
                        <ENT>STAMLEY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LORZ</ENT>
                        <ENT>AXEL</ENT>
                        <ENT>CURT HELMUT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LU</ENT>
                        <ENT>JEAN</ENT>
                        <ENT>MARTINA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LU</ENT>
                        <ENT>MARK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LUBELL</ENT>
                        <ENT>JANICE</ENT>
                        <ENT>EILEEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LUBELL</ENT>
                        <ENT>SUSAN</ENT>
                        <ENT>ELIZABETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LUI</ENT>
                        <ENT>HO</ENT>
                        <ENT>CHUNG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LYE</ENT>
                        <ENT>CORA</ENT>
                        <ENT>KATHRYN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MACDONALD</ENT>
                        <ENT>HUNTER</ENT>
                        <ENT>BANFORD BULMER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MACKENZIE</ENT>
                        <ENT>IAN</ENT>
                        <ENT>BROUARDE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MACMARTIN</ENT>
                        <ENT>SARA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MACRANDER</ENT>
                        <ENT>CATHRYN</ENT>
                        <ENT>M.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MAIKLEM</ENT>
                        <ENT>ANDREA</ENT>
                        <ENT>KIRSTEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MAJID</ENT>
                        <ENT>ARSHAD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MAJID</ENT>
                        <ENT>SIDRAH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MAJITHIA</ENT>
                        <ENT>NISHANT</ENT>
                        <ENT>RAJENDRA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MAK</ENT>
                        <ENT>CLEMENT</ENT>
                        <ENT>KA YIU</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MANCILLA</ENT>
                        <ENT>BLANCA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MANDIC</ENT>
                        <ENT>ALBERT</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MANLEY</ENT>
                        <ENT>BRIAN</ENT>
                        <ENT>PATRICK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MANNING</ENT>
                        <ENT>KIM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MANOSA</ENT>
                        <ENT>MARIA</ENT>
                        <ENT>ALEXANDRA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MANSELL</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>EDWARD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MARCUS</ENT>
                        <ENT>LESLIE</ENT>
                        <ENT>GLENN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MARET</ENT>
                        <ENT>NIICOLAS</ENT>
                        <ENT>LEVON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MARGOLIS</ENT>
                        <ENT>JESSIE</ENT>
                        <ENT>LAUREN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MARSHALL</ENT>
                        <ENT>ETHEL</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MARTENS</ENT>
                        <ENT>GRACE</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MARTIN</ENT>
                        <ENT>JANE</ENT>
                        <ENT>THERESA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MARTIN-BEILNER</ENT>
                        <ENT>MICHELINE</ENT>
                        <ENT>CAROLA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MASLO</ENT>
                        <ENT>KARL</ENT>
                        <ENT>GEORG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MASON</ENT>
                        <ENT>GREGORY</ENT>
                        <ENT>PAUL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MASS</ENT>
                        <ENT>ANTHONY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MATHISEN</ENT>
                        <ENT>LAURA</ENT>
                        <ENT>JANE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MAVIN</ENT>
                        <ENT>KEITH</ENT>
                        <ENT>GORDON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MAYFIELD</ENT>
                        <ENT>KARLA</ENT>
                        <ENT>SUE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MAZET</ENT>
                        <ENT>PHILIPPE</ENT>
                        <ENT>JACQUES OLIVIER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MAZUR</ENT>
                        <ENT>JENNIFER</ENT>
                        <ENT>ELLEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MC CLUNG</ENT>
                        <ENT>CORY</ENT>
                        <ENT>ROBERT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MC GEHEE</ENT>
                        <ENT>MARY</ENT>
                        <ENT>DARCY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MCAULEY</ENT>
                        <ENT>JOAN</ENT>
                        <ENT>FREEMAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MCBRIDE</ENT>
                        <ENT>DONALD</ENT>
                        <ENT>EUGENE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MCCOLLUM</ENT>
                        <ENT>DIANA</ENT>
                        <ENT>MARY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MCDOWELL</ENT>
                        <ENT>DOUGLAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MCLELLAN</ENT>
                        <ENT>DEBORA</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MCPHERSON</ENT>
                        <ENT>KIRK</ENT>
                        <ENT>LEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MCRAE</ENT>
                        <ENT>JILL</ENT>
                        <ENT>ELIZABETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MCSORLEY</ENT>
                        <ENT>ELEANOR</ENT>
                        <ENT>ADELE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MEERTENS</ENT>
                        <ENT>NAOMI</ENT>
                        <ENT>MARCIA KIKI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MEHRING</ENT>
                        <ENT>CARSTEN</ENT>
                        <ENT>RALF</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MEIER</ENT>
                        <ENT>DENISE</ENT>
                        <ENT>K.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MEINARDI</ENT>
                        <ENT>HERMELYN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MELHUS</ENT>
                        <ENT>PAMELA</ENT>
                        <ENT>CHRIS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MELLO</ENT>
                        <ENT>ANNE</ENT>
                        <ENT>E.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MENADA</ENT>
                        <ENT>CLAUDIA</ENT>
                        <ENT>P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MERRITT</ENT>
                        <ENT>THOMAS</ENT>
                        <ENT>CHRISTOPHER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MEYER-HEINE</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20963"/>
                        <ENT I="01">MICHALOWSKI</ENT>
                        <ENT>ALEXANDER</ENT>
                        <ENT>JAN-ZYGMUNT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MILLER</ENT>
                        <ENT>CARL</ENT>
                        <ENT>JASON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MILLER</ENT>
                        <ENT>SCOTT</ENT>
                        <ENT>GORDON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MILLS</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>E. WHITCRAFT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MILONA</ENT>
                        <ENT>LAMBROS</ENT>
                        <ENT>JAMES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MILTON</ENT>
                        <ENT>ALEXANDRA</ENT>
                        <ENT>CECILE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MINNINGS</ENT>
                        <ENT>ATLANTIS</ENT>
                        <ENT>WINDSOR</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MITCHELL</ENT>
                        <ENT>CHRISTIAN</ENT>
                        <ENT>SEGUR AKINER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MITSUMOTO</ENT>
                        <ENT>ERI</ENT>
                        <ENT>KAREN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MOHRHAUER</ENT>
                        <ENT>FRANK</ENT>
                        <ENT>OLAF</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MOLINA</ENT>
                        <ENT>ANTONIO</ENT>
                        <ENT>PASCUA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MOMEN</ENT>
                        <ENT>ABDUL</ENT>
                        <ENT>A.K.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MONDAL</ENT>
                        <ENT>RADHIKA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MONKS</ENT>
                        <ENT>KELLY</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MOORE</ENT>
                        <ENT>RODERICK</ENT>
                        <ENT>JAMES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MORALES GIRBAU</ENT>
                        <ENT>OMAR</ENT>
                        <ENT>R.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MORAWITZ</ENT>
                        <ENT>RAYMOND</ENT>
                        <ENT>LOUIS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MORGAN</ENT>
                        <ENT>MOLLY</ENT>
                        <ENT>FELICE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MORGAN</ENT>
                        <ENT>RONNIE</ENT>
                        <ENT>ALBERT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MORGAN JONKER</ENT>
                        <ENT>CECILY</ENT>
                        <ENT>CATHARINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MORGEN</ENT>
                        <ENT>KATRIN</ENT>
                        <ENT>ELISABETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MOROZOVA</ENT>
                        <ENT>ELINA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MORRIS</ENT>
                        <ENT>JAMES</ENT>
                        <ENT>HYWEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MOXON</ENT>
                        <ENT>FANK</ENT>
                        <ENT>HOYT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MUHLBAUER</ENT>
                        <ENT>PEGGY</ENT>
                        <ENT>ADRIANE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MUKUNTHARAO</ENT>
                        <ENT>MONEESHAU</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MULDER</ENT>
                        <ENT>PETER</ENT>
                        <ENT>WILLIAM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MUPPANA</ENT>
                        <ENT>PRATIK</ENT>
                        <ENT>VASPRAD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MURCH</ENT>
                        <ENT>SEAN</ENT>
                        <ENT>MACLENNAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MURPHY</ENT>
                        <ENT>TIMOTHY</ENT>
                        <ENT>LEIGH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MURRAY</ENT>
                        <ENT>CHLOE</ENT>
                        <ENT>CAMILLE MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MYERS</ENT>
                        <ENT>JASON</ENT>
                        <ENT>NATHANIEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NAGLE</ENT>
                        <ENT>SYDNEY</ENT>
                        <ENT>ROBIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NAI</ENT>
                        <ENT>HAO RAN</ENT>
                        <ENT>ASHLEY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NAIRNE</ENT>
                        <ENT>JAMES</ENT>
                        <ENT>ANDREW JOHNSTONE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NAVARRE</ENT>
                        <ENT>PIERRE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NEGLIA</ENT>
                        <ENT>GERMAN</ENT>
                        <ENT>ARTURO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NEGRYCH</ENT>
                        <ENT>SHERRYL</ENT>
                        <ENT>DIANE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NELSON</ENT>
                        <ENT>PAUL</ENT>
                        <ENT>MICHAEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NESBITT</ENT>
                        <ENT>MARK</ENT>
                        <ENT>CHRISTOPHER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NESSEL</ENT>
                        <ENT>TODD</ENT>
                        <ENT>ALLAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NEUMAN</ENT>
                        <ENT>GREGORY</ENT>
                        <ENT>RAYMOND</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NEUMANN</ENT>
                        <ENT>AVROHOM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NEWLAND</ENT>
                        <ENT>MARVIN</ENT>
                        <ENT>EARL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NEWMAN</ENT>
                        <ENT>MAYNARD</ENT>
                        <ENT>SIMONS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NG</ENT>
                        <ENT>XIDENG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NGUYEN</ENT>
                        <ENT>GEOFFREY</ENT>
                        <ENT>CHRISTOPHER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NICHOLAS</ENT>
                        <ENT>BETH</ENT>
                        <ENT>KATHLEEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NICHOLS</ENT>
                        <ENT>CLARE</ENT>
                        <ENT>ELIZABETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NICOLAISSEN</ENT>
                        <ENT>BJORN</ENT>
                        <ENT>OTTO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NICOLAUS</ENT>
                        <ENT>KAJA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NICOLAUS</ENT>
                        <ENT>MAIKA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NISHINO</ENT>
                        <ENT>EMIKO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NISHINO</ENT>
                        <ENT>KO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NISSEN</ENT>
                        <ENT>PEGGY</ENT>
                        <ENT>LOUISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NIXON</ENT>
                        <ENT>NATASHA</ENT>
                        <ENT>INDIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NOALL</ENT>
                        <ENT>JONAS</ENT>
                        <ENT>ERICH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NOLAN</ENT>
                        <ENT>EDMOND</ENT>
                        <ENT>PATRICK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NORRIS</ENT>
                        <ENT>GREGORY</ENT>
                        <ENT>BLAIR</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NORTON</ENT>
                        <ENT>NATALIA</ENT>
                        <ENT>BEATRICE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NUSSBAUMER</ENT>
                        <ENT>RALPH</ENT>
                        <ENT>ERNST</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NYE-COCCIARDI</ENT>
                        <ENT>DESIREE</ENT>
                        <ENT>LEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NYMAN</ENT>
                        <ENT>GEORGE</ENT>
                        <ENT>ALFRED</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OBERHOLTZER</ENT>
                        <ENT>WILLIAM</ENT>
                        <ENT>EARL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OCAMPO DESIONGCO</ENT>
                        <ENT>PATRICIA</ENT>
                        <ENT>YVETTE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OGUNYEMI</ENT>
                        <ENT>BOLUWAJI</ENT>
                        <ENT>AKHIGBE B.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OKE</ENT>
                        <ENT>CAROLYN</ENT>
                        <ENT>LOUISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OKISHIO</ENT>
                        <ENT>TAKAO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OLIVER</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ONG</ENT>
                        <ENT>HWEI</ENT>
                        <ENT>MIN LISA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OPELZ</ENT>
                        <ENT>HENRIK</ENT>
                        <ENT>JOHANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OPHEL</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>LEWIS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OPPERMAN</ENT>
                        <ENT>SHERRY</ENT>
                        <ENT>RUTH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OSUCH</ENT>
                        <ENT>ELIZABETH</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20964"/>
                        <ENT I="01">OTT</ENT>
                        <ENT>STEFANIE</ENT>
                        <ENT>DOROTHEA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OTTERLING</ENT>
                        <ENT>JACOB</ENT>
                        <ENT>KARL EDVIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PADUA</ENT>
                        <ENT>FABRIZIO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PAGRATIS</ENT>
                        <ENT>VANESSA</ENT>
                        <ENT>CAROLINA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PALIOTTA</ENT>
                        <ENT>DONATELLA</ENT>
                        <ENT>SYLVIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PALMER</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PANTUSO</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>ALLAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PAQUETTE</ENT>
                        <ENT>SARA</ENT>
                        <ENT>RANKIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PARK</ENT>
                        <ENT>ANDREW</ENT>
                        <ENT>KIM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PARK</ENT>
                        <ENT>YOUNG</ENT>
                        <ENT>HO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PARKAR</ENT>
                        <ENT>SUJATA</ENT>
                        <ENT>PRABHAKAR</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PATEL</ENT>
                        <ENT>HIRAL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PAXON</ENT>
                        <ENT>GEORGE</ENT>
                        <ENT>ALEXANDER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PEBAY</ENT>
                        <ENT>CAROLE</ENT>
                        <ENT>A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PECKAN</ENT>
                        <ENT>LI</ENT>
                        <ENT>ELIZABETH MOWAT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PEDRETTI</ENT>
                        <ENT>ROSSANA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PEIRCE</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>NORTON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PELHAM</ENT>
                        <ENT>GEORGE</ENT>
                        <ENT>SACKVILLE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PELLERIN</ENT>
                        <ENT>MARC</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PELLERIN-LORING</ENT>
                        <ENT>JENNY</ENT>
                        <ENT>DIANE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PELLETIER</ENT>
                        <ENT>FRANCIS</ENT>
                        <ENT>JEFFRY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PELZER</ENT>
                        <ENT>KRISTEN</ENT>
                        <ENT>RUTH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PENNER</ENT>
                        <ENT>KIMBRE</ENT>
                        <ENT>JAYE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PENNER</ENT>
                        <ENT>MARGARET</ENT>
                        <ENT>EDA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PERCIBALLI</ENT>
                        <ENT>SERGIO</ENT>
                        <ENT>GINO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PERONI</ENT>
                        <ENT>MARIO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PERPERE</ENT>
                        <ENT>HUGO</ENT>
                        <ENT>ETIENNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PERRET</ENT>
                        <ENT>DANIEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PERRY</ENT>
                        <ENT>NANCY</ENT>
                        <ENT>GARRISON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PERRY</ENT>
                        <ENT>PETER</ENT>
                        <ENT>BARTHEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PETERS</ENT>
                        <ENT>REMCO</ENT>
                        <ENT>THEODOOR</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PHILLIPS</ENT>
                        <ENT>ASHA</ENT>
                        <ENT>SUZANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PIAMTHIPMANUS</ENT>
                        <ENT>ATTAKRIT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PIERRO</ENT>
                        <ENT>SOPHIA</ENT>
                        <ENT>MARIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PILZ</ENT>
                        <ENT>JOAN</ENT>
                        <ENT>CHUNGCHIH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PINET</ENT>
                        <ENT>RICHARD</ENT>
                        <ENT>GEORGE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PITTET</ENT>
                        <ENT>CATHERINE</ENT>
                        <ENT>NICOLE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PIVA</ENT>
                        <ENT>DARIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PLACKE</ENT>
                        <ENT>REBECCA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PLATTNER</ENT>
                        <ENT>ALEXANDRA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PLENTER-VOWLES</ENT>
                        <ENT>KATHERINA</ENT>
                        <ENT>CORNELIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">POND</ENT>
                        <ENT>CAROLE</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">POWELL</ENT>
                        <ENT>BARBARA</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">POWER</ENT>
                        <ENT>MARK</ENT>
                        <ENT>BERNARD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PREDONZANI</ENT>
                        <ENT>LUISA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PRICE</ENT>
                        <ENT>KENT</ENT>
                        <ENT>ADRIAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PRINCE</ENT>
                        <ENT>ANTHONY</ENT>
                        <ENT>ALLEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PUNNETT</ENT>
                        <ENT>CHRISTPHER</ENT>
                        <ENT>RAYMOND</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PURIBHAT</ENT>
                        <ENT>SIRILUK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PYFROM</ENT>
                        <ENT>JEROME</ENT>
                        <ENT>ELLIOTT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PYKE</ENT>
                        <ENT>TIMOTHY</ENT>
                        <ENT>JAMES HAYWARD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">QIAN</ENT>
                        <ENT>DIANA</ENT>
                        <ENT>MENGMIAO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RACH NORREY</ENT>
                        <ENT>ALISA</ENT>
                        <ENT>KIMBERLY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RADCLIFFE</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>DOUGLAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RADIX</ENT>
                        <ENT>MAXENCE</ENT>
                        <ENT>BRIAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RAGSDALE</ENT>
                        <ENT>JAMES</ENT>
                        <ENT>WEBB</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RANDAZZO</ENT>
                        <ENT>PETER</ENT>
                        <ENT>RANDY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RAYMOND</ENT>
                        <ENT>EDWARD</ENT>
                        <ENT>ANTHONY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RAYNE</ENT>
                        <ENT>MAIHAA</ENT>
                        <ENT>K.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REAVELY</ENT>
                        <ENT>AMANDA</ENT>
                        <ENT>LYNN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REBECCHINI</ENT>
                        <ENT>GAETANO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REBETZ GHARBI</ENT>
                        <ENT>SABRINA</ENT>
                        <ENT>MARIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REBONATI</ENT>
                        <ENT>MICHEL</ENT>
                        <ENT>JEROME</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REDDY</ENT>
                        <ENT>ARUN</ENT>
                        <ENT>KATANGURU</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REDENBACH</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REED</ENT>
                        <ENT>SHAWN</ENT>
                        <ENT>RONALD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REICHERT</ENT>
                        <ENT>DANIEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REICHL</ENT>
                        <ENT>SONIA</ENT>
                        <ENT>YANNA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REIF</ENT>
                        <ENT>JONATHAN</ENT>
                        <ENT>WERNER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REILLY</ENT>
                        <ENT>MONICA</ENT>
                        <ENT>FRANCOISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REITSMA</ENT>
                        <ENT>ELSE</ENT>
                        <ENT>CHRISTINE LOUISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RIBAS</ENT>
                        <ENT>JUAN</ENT>
                        <ENT>MOANA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RIBAS-CADLE</ENT>
                        <ENT>DIEGO</ENT>
                        <ENT>MATEO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RIBAS-CADLE</ENT>
                        <ENT>LUISA</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20965"/>
                        <ENT I="01">RILEY</ENT>
                        <ENT>ELLIOT</ENT>
                        <ENT>DANIEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RINGLE-HARRIS</ENT>
                        <ENT>MARCIA</ENT>
                        <ENT>JANE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RITTER</ENT>
                        <ENT>SANDRA</ENT>
                        <ENT>DIANA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROBLES</ENT>
                        <ENT>MICHELLE</ENT>
                        <ENT>ADRIANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROBSON IV</ENT>
                        <ENT>ARTHUR</ENT>
                        <ENT>W.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROEMER</ENT>
                        <ENT>STEFAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROESLER</ENT>
                        <ENT>GRETCHEN</ENT>
                        <ENT>DORENE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROGERS</ENT>
                        <ENT>PATRICIA</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROGERS NANNARONE</ENT>
                        <ENT>MOLLY</ENT>
                        <ENT>ELLEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROOT</ENT>
                        <ENT>ANNE</ENT>
                        <ENT>CAROLINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROSS</ENT>
                        <ENT>PAUL</ENT>
                        <ENT>JENS PETER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROSS</ENT>
                        <ENT>PAUL</ENT>
                        <ENT>STEPHEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROTHENBERGER</ENT>
                        <ENT>YTANN</ENT>
                        <ENT>ZACCARIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROTHFELS</ENT>
                        <ENT>ELISHA</ENT>
                        <ENT>DEONNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROUTLEDGE</ENT>
                        <ENT>JAN</ENT>
                        <ENT>LAWRENCE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROUX</ENT>
                        <ENT>SERGE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RUCHKALL</ENT>
                        <ENT>BARBARA</ENT>
                        <ENT>LYNNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RUDDOCK</ENT>
                        <ENT>JAMES</ENT>
                        <ENT>ANDREW</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RUSHTON</ENT>
                        <ENT>NICHOLE</ENT>
                        <ENT>LYNNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RUTLEDGE</ENT>
                        <ENT>JANA</ENT>
                        <ENT>MICHELLE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RYAN</ENT>
                        <ENT>LAURIE</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SABO</ENT>
                        <ENT>JASON</ENT>
                        <ENT>WAYNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SADLER</ENT>
                        <ENT>SHERRI</ENT>
                        <ENT>JO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SAKAMOTO</ENT>
                        <ENT>HATSUYOSHI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SAKASHITA</ENT>
                        <ENT>MADELEINE</ENT>
                        <ENT>EVANS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SALABERRY</ENT>
                        <ENT>ANGELYN</ENT>
                        <ENT>DAWN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SALABERRY</ENT>
                        <ENT>PEGGY</ENT>
                        <ENT>THERESE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SALIBRA</ENT>
                        <ENT>LAWRENCE</ENT>
                        <ENT>ANTHONY TERZ0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SALSBURY JR</ENT>
                        <ENT>THOMAS</ENT>
                        <ENT>APPEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SANDERS</ENT>
                        <ENT>EMILY</ENT>
                        <ENT>SARA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SANDOR</ENT>
                        <ENT>GARY</ENT>
                        <ENT>BRIAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SANGHANI</ENT>
                        <ENT>JIGNESH</ENT>
                        <ENT>VINODKANT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SANGHVI</ENT>
                        <ENT>DEVIKA</ENT>
                        <ENT>DIPAL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SANHEDRAI</ENT>
                        <ENT>POPPY</ENT>
                        <ENT>SARIEL C</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SANTAMATO</ENT>
                        <ENT>LORENZO</ENT>
                        <ENT>GIOVANNI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SANTI</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT>LUCIEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SARDAR</ENT>
                        <ENT>HASINA</ENT>
                        <ENT>BEGUM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SAYN-WITTGENSTEIN</ENT>
                        <ENT>CHRISTIAN</ENT>
                        <ENT>GEORG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCARLETTS</ENT>
                        <ENT>MOREAH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHAERER</ENT>
                        <ENT>ALAN</ENT>
                        <ENT>CHRISTOPH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHAURTE-KUEPPERS</ENT>
                        <ENT>CAROLIN</ENT>
                        <ENT>B.H.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHILL</ENT>
                        <ENT>DANIELA</ENT>
                        <ENT>CARMEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHMIDT</ENT>
                        <ENT>EVA</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHNEIDER</ENT>
                        <ENT>ANNE</ENT>
                        <ENT>VIRGINIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHRAM</ENT>
                        <ENT>CARRIE</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHRIBER</ENT>
                        <ENT>BARBARA</ENT>
                        <ENT>SUSANNA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHROEDER</ENT>
                        <ENT>MANFRED</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHUMACHER</ENT>
                        <ENT>UTE.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHWAB</ENT>
                        <ENT>KELLY</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHWEIGER</ENT>
                        <ENT>EMILY</ENT>
                        <ENT>MARGARET</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCRIVEN</ENT>
                        <ENT>JOEL</ENT>
                        <ENT>NICHOLAS HAMILTON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SEACREST</ENT>
                        <ENT>PHILIP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SEITZ</ENT>
                        <ENT>MURRAY</ENT>
                        <ENT>WADE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SETTE</ENT>
                        <ENT>VIVIANA</ENT>
                        <ENT>P.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SEYBOLD</ENT>
                        <ENT>CLAIRE</ENT>
                        <ENT>IRIS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHAHANI</ENT>
                        <ENT>SOMANSH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHALGI</ENT>
                        <ENT>RAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHAPIRO</ENT>
                        <ENT>MARC</ENT>
                        <ENT>J.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHAW</ENT>
                        <ENT>CHERYL</ENT>
                        <ENT>KAY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHAW-LUIGI</ENT>
                        <ENT>RIMA</ENT>
                        <ENT>OLGA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHEY</ENT>
                        <ENT>LINDSEY</ENT>
                        <ENT>ELIZABETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHI</ENT>
                        <ENT>HUMA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHILLABEER</ENT>
                        <ENT>DONNA</ENT>
                        <ENT>JEAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHIPTON</ENT>
                        <ENT>CHRISTINE</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SIDENIUS</ENT>
                        <ENT>PETER</ENT>
                        <ENT>KELVIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SIEBEN-KRETZERS</ENT>
                        <ENT>PATRICIA</ENT>
                        <ENT>ELIZABETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SILVIA</ENT>
                        <ENT>ELIZABETH</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SIMMONS</ENT>
                        <ENT>DANIEL</ENT>
                        <ENT>ROBERT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SIMMONS</ENT>
                        <ENT>HELEN</ENT>
                        <ENT>MARY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SIMONI</ENT>
                        <ENT>LUCA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SKETCHES</ENT>
                        <ENT>DENISE</ENT>
                        <ENT>RUTH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SKOWRONSKI</ENT>
                        <ENT>ANDREW</ENT>
                        <ENT>JOSHUA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SLOT</ENT>
                        <ENT>ERIK</ENT>
                        <ENT>GUSTAAF</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SMITH</ENT>
                        <ENT>HEATHER</ENT>
                        <ENT>RENAE</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20966"/>
                        <ENT I="01">SMITH</ENT>
                        <ENT>TIMOTHY</ENT>
                        <ENT>AARON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SOARES</ENT>
                        <ENT>JENNIFER</ENT>
                        <ENT>LYNN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SODERLING</ENT>
                        <ENT>SCOTT</ENT>
                        <ENT>DREW</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SOFER</ENT>
                        <ENT>AMIT</ENT>
                        <ENT>JAMES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SOGOLO</ENT>
                        <ENT>SAMANTHA</ENT>
                        <ENT>ONORIEVARA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SOKOLOWSKI</ENT>
                        <ENT>COREY</ENT>
                        <ENT>CLARKE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SOLEM</ENT>
                        <ENT>MONICA</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SOLOMONS</ENT>
                        <ENT>THOMAS</ENT>
                        <ENT>A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SOMMERVILLE</ENT>
                        <ENT>JULIE</ENT>
                        <ENT>MAREE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SONSTEGARD</ENT>
                        <ENT>VALERIE</ENT>
                        <ENT>LYNN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SOPCAK</ENT>
                        <ENT>JENNY</ENT>
                        <ENT>KATHERINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SORENSEN</ENT>
                        <ENT>JAMES</ENT>
                        <ENT>COMUMBAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SORENSEN</ENT>
                        <ENT>MAIREAD</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STAUDER</ENT>
                        <ENT>BERND</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STEIGER</ENT>
                        <ENT>LAURA</ENT>
                        <ENT>CATHERINA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STEINKE</ENT>
                        <ENT>LINDA</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STEINMETZ VILELA</ENT>
                        <ENT>BERTHA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STEWART</ENT>
                        <ENT>ANNE</ENT>
                        <ENT>MARGARET</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STILL</ENT>
                        <ENT>SAMUEL</ENT>
                        <ENT>HARRISON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STORTI</ENT>
                        <ENT>LETTERIO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STRAJA</ENT>
                        <ENT>ANDRE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STRAKER</ENT>
                        <ENT>PATRICIA</ENT>
                        <ENT>SUE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STRAW</ENT>
                        <ENT>ROSEMARY</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STRONG</ENT>
                        <ENT>DWAYNE</ENT>
                        <ENT>DONALD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STUBBS</ENT>
                        <ENT>MATTHEW</ENT>
                        <ENT>JAMES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STULBERG</ENT>
                        <ENT>LEV</ENT>
                        <ENT>ISAACOVICH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SUMAR</ENT>
                        <ENT>FRANCISCO</ENT>
                        <ENT>EDUARDO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SUNDICH</ENT>
                        <ENT>NICHOLAS</ENT>
                        <ENT>ALEXANDER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SUSIE</ENT>
                        <ENT>CHRISTOPHER</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SZIKMAN</ENT>
                        <ENT>GLORIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAKAHARA</ENT>
                        <ENT>ASAHI</ENT>
                        <ENT>THOMAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAKAHASHI</ENT>
                        <ENT>NAOTO</ENT>
                        <ENT>ANDREW</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAKAI</ENT>
                        <ENT>KENTARO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAM</ENT>
                        <ENT>DENISE</ENT>
                        <ENT>HOK YUN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAN</ENT>
                        <ENT>EDNA</ENT>
                        <ENT>L.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAN</ENT>
                        <ENT>HWEE</ENT>
                        <ENT>SIAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAN</ENT>
                        <ENT>KATHERINE</ENT>
                        <ENT>LEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAN</ENT>
                        <ENT>YEE</ENT>
                        <ENT>LIANG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TANG</ENT>
                        <ENT>SAI</ENT>
                        <ENT>HO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TARRING</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAY</ENT>
                        <ENT>SANDY</ENT>
                        <ENT>GUAT SEANG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TEFFT</ENT>
                        <ENT>MARIANNE</ENT>
                        <ENT>LOUISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TELFORD</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT>BRUCE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TEO</ENT>
                        <ENT>JEREMY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TESLUK</ENT>
                        <ENT>CEILIDH</ENT>
                        <ENT>MADELEINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TETREAULT</ENT>
                        <ENT>LORRAINE</ENT>
                        <ENT>ALICE ROLLANDE MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THALMANN</ENT>
                        <ENT>AMANDA</ENT>
                        <ENT>DANIELLE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THIO</ENT>
                        <ENT>CELINE</ENT>
                        <ENT>SARA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THOMAS</ENT>
                        <ENT>SHENANDOAH</ENT>
                        <ENT>WOUTER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THOMAS-FASOULIDIS</ENT>
                        <ENT>MARIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THOMASSEN</ENT>
                        <ENT>NICHOLAS</ENT>
                        <ENT>ANTHONY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THOMPSON</ENT>
                        <ENT>GEOFFREY</ENT>
                        <ENT>BRYANS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THORNLEY</ENT>
                        <ENT>ASLI</ENT>
                        <ENT>PINAR</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TOLLER</ENT>
                        <ENT>USCHI</ENT>
                        <ENT>KAI ANLAUF</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TRACCI</ENT>
                        <ENT>HENRY</ENT>
                        <ENT>ROBERT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TREMBLAY</ENT>
                        <ENT>PHILLIP</ENT>
                        <ENT>ALAIN NATHO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TREMTHTHANMOR</ENT>
                        <ENT>CHRYS</ENT>
                        <ENT>EVNATH TRISTAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TRIPLETT</ENT>
                        <ENT>ROY</ENT>
                        <ENT>LENNY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TRISIC</ENT>
                        <ENT>STEVAN</ENT>
                        <ENT>PETAR</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TRUSCOTT</ENT>
                        <ENT>BARBARA</ENT>
                        <ENT>JEAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TSAI</ENT>
                        <ENT>EMILY</ENT>
                        <ENT>S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TUCKER</ENT>
                        <ENT>CATHERINE</ENT>
                        <ENT>JANE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ULLMAN</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>EDWARD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">URBAN</ENT>
                        <ENT>CHONG</ENT>
                        <ENT>SUK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VADHULAS</ENT>
                        <ENT>DIVYA</ENT>
                        <ENT>MURALIDHAR</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VALLARINO</ENT>
                        <ENT>PEDRO</ENT>
                        <ENT>MANUEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VAN DEN BOS</ENT>
                        <ENT>LIESBETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VAN DER EERDEN</ENT>
                        <ENT>CINDY</ENT>
                        <ENT>MARGARETHA MARIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VAN DER MEER</ENT>
                        <ENT>PHYLLIS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VAN DER VORST</ENT>
                        <ENT>GUILAINE</ENT>
                        <ENT>MARIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VAN DOREN</ENT>
                        <ENT>SIMONETTE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VAN ETTEN</ENT>
                        <ENT>MATTHEW</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VAN NOORT</ENT>
                        <ENT>BERNARDUS</ENT>
                        <ENT>JOZEF RUDOLF</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VAN OTTERLOO</ENT>
                        <ENT>MATTHEW</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20967"/>
                        <ENT I="01">VAN REMUNDT</ENT>
                        <ENT>ANNA</ENT>
                        <ENT>TARA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VANDEN BRINK</ENT>
                        <ENT>JENNIFER</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VANDENDOOREN</ENT>
                        <ENT>PIERRE</ENT>
                        <ENT>JACQUES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VANHERK</ENT>
                        <ENT>ALLISON</ENT>
                        <ENT>ELISABETH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VARLAAM</ENT>
                        <ENT>CAROLINE</ENT>
                        <ENT>FRENCH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VERNON</ENT>
                        <ENT>VERONICA</ENT>
                        <ENT>RITA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VIGNET</ENT>
                        <ENT>FREDERIC</ENT>
                        <ENT>LOUIS ACHILLE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VIKEN</ENT>
                        <ENT>KAY</ENT>
                        <ENT>LOUISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VIPPERMAN</ENT>
                        <ENT>WALTER</ENT>
                        <ENT>BRYCE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VISENTIN</ENT>
                        <ENT>VERONICA</ENT>
                        <ENT>MARY LOUISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VISSER</ENT>
                        <ENT>DANIEL</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VISSER</ENT>
                        <ENT>JANNY</ENT>
                        <ENT>LOUISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VISSER</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>JACK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VOGT</ENT>
                        <ENT>SIMON</ENT>
                        <ENT>THOMAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VON QUAST</ENT>
                        <ENT>ALEXANDER</ENT>
                        <ENT>PHILIP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WACHMANN</ENT>
                        <ENT>MARC</ENT>
                        <ENT>CONSTANTIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WACHTERS</ENT>
                        <ENT>EUGENIA</ENT>
                        <ENT>APOLLONIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WAGENHOFFER</ENT>
                        <ENT>MELANIE</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WAGNER</ENT>
                        <ENT>KATHERINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WAKIM</ENT>
                        <ENT>ABRAHIM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WALLER</ENT>
                        <ENT>LUKAS</ENT>
                        <ENT>GERHARD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WALSCHOT</ENT>
                        <ENT>MICHELLE</ENT>
                        <ENT>RENEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WALTERS</ENT>
                        <ENT>JULIAN</ENT>
                        <ENT>ROGER FORD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WANG</ENT>
                        <ENT>YU-CHUNG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WARNER</ENT>
                        <ENT>SCOTT</ENT>
                        <ENT>ANDREW</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WATT</ENT>
                        <ENT>CHARLES</ENT>
                        <ENT>HENRY WILLIAM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WATTS</ENT>
                        <ENT>KELI</ENT>
                        <ENT>RYAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WATTS</ENT>
                        <ENT>SUSAN</ENT>
                        <ENT>LOUISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WEAVER</ENT>
                        <ENT>MELANIE</ENT>
                        <ENT>JEAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WEIDER</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>JOSEF</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WEINER</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>JOEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WEMPLE</ENT>
                        <ENT>CLARISSA</ENT>
                        <ENT>KIM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WERT</ENT>
                        <ENT>WILLIAM</ENT>
                        <ENT>FREDERICK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WESPI</ENT>
                        <ENT>PASCALE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WESTLER</ENT>
                        <ENT>SHARON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WEYHERS</ENT>
                        <ENT>JAN-HENDRIK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WEYRAUCH</ENT>
                        <ENT>SUSANNE</ENT>
                        <ENT>MELANIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHITE</ENT>
                        <ENT>MARGARET</ENT>
                        <ENT>JANE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WHYTE</ENT>
                        <ENT>EILEEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WIDJAJA</ENT>
                        <ENT>TORA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WIGHT</ENT>
                        <ENT>DEREK</ENT>
                        <ENT>LONERGAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILCKE</ENT>
                        <ENT>JONATHON</ENT>
                        <ENT>CHAD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILHELMSEN</ENT>
                        <ENT>HANNAH</ENT>
                        <ENT>ESHETE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILLIAMS</ENT>
                        <ENT>JARON</ENT>
                        <ENT>JOSEPH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILLIAMS</ENT>
                        <ENT>JERROLD</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILLIAMS</ENT>
                        <ENT>LISA</ENT>
                        <ENT>ELLEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILLIAMS</ENT>
                        <ENT>RICHARD</ENT>
                        <ENT>GEORGE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILSON</ENT>
                        <ENT>BROOKE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILSON</ENT>
                        <ENT>CODY</ENT>
                        <ENT>LANE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILSON</ENT>
                        <ENT>JAMES</ENT>
                        <ENT>HENRY ST. JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILSON</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>PAUL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILSON</ENT>
                        <ENT>KENNETH</ENT>
                        <ENT>RANDALL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILSON</ENT>
                        <ENT>RACHEL</ENT>
                        <ENT>JANE PAINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WISKOTT</ENT>
                        <ENT>KIM</ENT>
                        <ENT>AURORA-FRANCOISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WOLF</ENT>
                        <ENT>KAREN</ENT>
                        <ENT>LYNN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WOLF</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>THORNTON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WOLFSBERGER</ENT>
                        <ENT>BRIGITTE</ENT>
                        <ENT>MARIE-ANGE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WONG</ENT>
                        <ENT>LILLIAS</ENT>
                        <ENT>JOSEPHINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WONG</ENT>
                        <ENT>NATALIE</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WOOD</ENT>
                        <ENT>JUSTIN</ENT>
                        <ENT>TRENT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WOOD</ENT>
                        <ENT>RONALD</ENT>
                        <ENT>BURWELL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WOOD-OSTERWALD</ENT>
                        <ENT>ALEXANDER</ENT>
                        <ENT>JAMES GETTY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WOODS</ENT>
                        <ENT>VALEIE</ENT>
                        <ENT>TERESA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WU</ENT>
                        <ENT>MI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WU</ENT>
                        <ENT>YUNQI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YABUSHITA</ENT>
                        <ENT>FUYUKO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YACOWAR</ENT>
                        <ENT>MARLA</ENT>
                        <ENT>SUSAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YAMADA</ENT>
                        <ENT>RINO</ENT>
                        <ENT>JULIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YAMMINE</ENT>
                        <ENT>JAMES</ENT>
                        <ENT>KABALAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YAP</ENT>
                        <ENT>MAYBELLINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YAROSHEVICH</ENT>
                        <ENT>YAN</ENT>
                        <ENT>ALEXANDER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YAU</ENT>
                        <ENT>EDWIN</ENT>
                        <ENT>WAI WING</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YE</ENT>
                        <ENT>GEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YEO</ENT>
                        <ENT>SHERYL</ENT>
                        <ENT>ZHAO LING</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="20968"/>
                        <ENT I="01">YIN</ENT>
                        <ENT>XIAO</ENT>
                        <ENT>DONG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YIP</ENT>
                        <ENT>DIANA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YOO</ENT>
                        <ENT>SU</ENT>
                        <ENT>RIM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YOON</ENT>
                        <ENT>WAE</ENT>
                        <ENT>SUK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YOONG</ENT>
                        <ENT>KIMBERLY</ENT>
                        <ENT>YU YING</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YOUMANS</ENT>
                        <ENT>CRAIG</ENT>
                        <ENT>CORNELL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YOUNG</ENT>
                        <ENT>LUKE</ENT>
                        <ENT>DOUGLAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YUE</ENT>
                        <ENT>ANSON</ENT>
                        <ENT>WEI YUE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZACOUR</ENT>
                        <ENT>GEOFFREY</ENT>
                        <ENT>CHARLES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZAHID</ENT>
                        <ENT>AMAL</ENT>
                        <ENT>ALI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZAINAL</ENT>
                        <ENT>HAFSA</ENT>
                        <ENT>NASSER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZEKVELD</ENT>
                        <ENT>LEVI</ENT>
                        <ENT>HARRISON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZERBY</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>VINCENT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZHANG</ENT>
                        <ENT>XIAO</ENT>
                        <ENT>ZHU</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZHU</ENT>
                        <ENT>DEREK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZILTENER</ENT>
                        <ENT>VALERIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZIMMERMAN</ENT>
                        <ENT>RENA</ENT>
                        <ENT>SHELLEY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZINDEL</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZOLESIO</ENT>
                        <ENT>ROSA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZOLTU</ENT>
                        <ENT>MICAH</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <DATED>Dated: May 1, 2019.</DATED>
                    <NAME>Diane Costello,</NAME>
                    <TITLE>Manager Classification Team 82413, Examinations Operations—Philadelphia Compliance Services.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2019-09731 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <SUBJECT>Privacy Act of 1974; Matching Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Veterans Affairs (VA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a new matching program.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Veterans Affairs (VA) has an 18 month computer matching agreement (CMA) agreement with the Department of Defense (DoD) regarding Veterans who have returned to active duty and are also in receipt of compensation and pension benefits. The purpose of this CMA is to re-establish the agreement between VA, Veterans Benefits Administration (VBA) and the DoD, Defense Manpower Data Center (DMDC). DoD will disclose information about individuals who have returned to active duty. VBA will use this information as a match for recipients of Compensation and Pension benefits for adjustments of awards.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Comments on this matching program must be received no later than June 12, 2019. If no public comment is received during the period allowed for comment or unless otherwise published in the 
                        <E T="04">Federal Register</E>
                         by VA, the new agreement will become effective a minimum of 30 days after date of publication in the 
                        <E T="04">Federal Register</E>
                        . If VA receives public comments, VA shall review the comments to determine whether any changes to the notice are necessary. This matching program will be valid for 18 months from the effective date of this notice.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments may be submitted through 
                        <E T="03">www.Regulations.gov</E>
                        ; by mail or hand-delivery to Director, Regulation Policy and Management (00REG), Department of Veterans Affairs, 810 Vermont Ave. NW, Room 1064, Washington, DC 20420; or by fax to (202) 273-9026 (not a toll-free number). Comments should indicate that they are submitted in response to CMA VA/VBA) and DoD, DoD/DMDC. Copies of comments received will be available for public inspection in the Office of Regulation Policy and Management, Room 1063B, between the hours of 8:00 a.m. and 4:30 p.m., Monday through Friday (except holidays). Please call (202) 461-4902 for an appointment. (This is not a toll-free number.) In addition, comments may be viewed online at 
                        <E T="03">www.Regulations.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Eric Robinson (VBA), 202-443-6016, 
                        <E T="03">eric.robinson3@va.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This agreement continues an arrangement for a periodic computer-matching program between the United States Department of Veterans Affairs (VA), Veterans Benefits Administration (VBA) as the matching recipient agency and the Department of Defense (DoD), Defense Manpower Data Center (DMDC) as the matching source agency. This agreement sets forth the responsibilities of VBA and DoD with respect to information disclosed pursuant to this agreement and takes into account both agencies' responsibilities under the Privacy Act of 1974, 5 U.S.C. 552a, as amended by the Computer Matching and Privacy Protection Act of 1988, as amended, and the regulations promulgated thereunder, including computer matching portions of a revision of OMB Circular No.A-130, 65 FR 77677 dated December 12, 2000.</P>
                <P>
                    <E T="03">Participating Agencies:</E>
                     The United States Department of Veterans Affairs (VA), Veterans Benefits Administration (VBA) as the matching recipient agency and the Department of Defense (DoD), Defense Manpower Data Center (DMDC) as the matching source agency.
                </P>
                <P>
                    <E T="03">Authority for Conducting the Matching Program:</E>
                     The legal authority for conducting the matching program for use in the administration of VA's Compensation and Pension Benefits Programs is contained in 38 U.S.C. 5304(c), Prohibition Against Duplication of Benefits, which precludes pension, compensation, or retirement pay on account of any person's own service, for any period for which he receives active duty pay. The head of any Federal department or agency shall provide, pursuant to 38 U.S.C. 5106, such information as requested by VA for the purpose of determining eligibility for, or amount of benefits, or verifying other information with respect thereto.
                </P>
                <P>
                    <E T="03">Purpose(s):</E>
                     The purpose of this matching program between VBA and DoD is to identify those veterans and VA beneficiaries who are in receipt of certain VA benefit payments and have returned to active duty. VBA has the obligation to reduce or suspend compensation and pension benefit payments to veterans who have returned to active duty. VBA will use the DoD records provided in the match to update the master records of veterans and VA beneficiaries receiving benefits and to 
                    <PRTPAGE P="20969"/>
                    adjust their VA benefits, accordingly, if needed.
                </P>
                <P>
                    <E T="03">Categories of Individuals:</E>
                </P>
                <P>1. Veterans who have applied for compensation for service-connected disability under 38 U.S.C. Chapter 11.</P>
                <P>2. Veterans who have applied for nonservice-connected disability under 38 U.S.C. Chapter 15.</P>
                <P>3. Veterans entitled to burial benefits under 38 U.S.C. Chapter 23.</P>
                <P>4. Surviving spouses and children who have claimed pensions based on nonservice-connected death of a veteran under 38 U.S.C. Chapter 15.</P>
                <P>5. Surviving spouses and children who have claimed death compensation based on service-connected death of a veteran under 38 U.S.C. Chapter 11.</P>
                <P>6. Surviving spouses and children who have claimed dependency and indemnity compensation for service connected death of a veteran under 38 U.S.C. Chapter 13.</P>
                <P>7. Parents who have applied for death compensation based on service connected death of a veteran under 38 U.S.C. Chapter 11.</P>
                <P>8. Parents who have applied for dependency and indemnity compensation for service-connected death of a veteran under 38 U.S.C. Chapter 13.</P>
                <P>9. Individuals who applied for educational assistance benefits administered by VA under title 38 of the U.S. Code.</P>
                <P>10. Individuals who applied for educational assistance benefits maintained by the Department of Defense under title 10 of the U.S. Code that are administered by VA.</P>
                <P>11. Veterans who apply for training and employers who apply for approval of their programs under the provisions of the Emergency Veterans' Job Training Act of 1983, Public Law 98-77.</P>
                <P>12. Any VA employee who generates or finalizes adjudicative actions using the Benefits Delivery Network (BDN) or the Veterans Service Network (VETSNET) computer processing systems.</P>
                <P>13. Veterans who apply for training and employers who apply for approval of their programs under the provisions of the Service Members Occupational Conversion and Training Act of 1992, Public Law 102-484.</P>
                <P>14. Representatives of individuals covered by the system.</P>
                <P>
                    <E T="03">Categories of Records:</E>
                </P>
                <P>The record, or information contained in the record, may include:</P>
                <P>
                    1. Identifying information (
                    <E T="03">e.g.,</E>
                     name, address. social security number);
                </P>
                <P>
                    2. Military service and active duty separation information (
                    <E T="03">e.g.,</E>
                     name, service number, date of birth, rank, sex, total amount of active service, branch of service, character of service, pay grade, assigned separation reason, service period, whether veteran was discharged with a disability, reenlisted, received a Purple Heart or other military decoration);
                </P>
                <P>
                    3. Payment information (
                    <E T="03">e.g.,</E>
                     veteran payee name, address, dollar amount of readjustment service pay, amount of disability or pension payments, number of non-pay days, any amount of indebtedness (accounts receivable) arising from title 38 U.S.C. benefits and which are owed to the VA);
                </P>
                <P>
                    4. Medical information (
                    <E T="03">e.g.,</E>
                     medical and dental treatment in the Armed Forces including type of service-connected disability, medical facilities, or medical or dental treatment by VA health care personnel or received from private hospitals and health care personnel relating to a claim for VA disability benefits or medical or dental treatment);
                </P>
                <P>
                    5. Personal information (
                    <E T="03">e.g.,</E>
                     marital status, name and address of dependents, occupation, amount of education of a veteran or a dependent, dependent's relationship to veteran);
                </P>
                <P>
                    6. Education benefit information (
                    <E T="03">e.g.,</E>
                     information arising from utilization of training benefits such as a veteran trainee's induction, reentrance or dismissal from a program or progress and attendance in an education or training program);
                </P>
                <P>
                    7. Applications for compensation, pension, education and vocational rehabilitation benefits and training—which may contain identifying information, military service and active duty separation information, payment information, medical and dental information, personal and education benefit information relating to a veteran or beneficiary's incarceration in a penal institution (
                    <E T="03">e.g.,</E>
                     name of incarcerated veteran or beneficiary, claims folder number, name and address of penal institution, date of commitment, type of offense, scheduled release date, veteran's date of birth, beneficiary relationship to veteran and whether veteran or beneficiary is in a work release or half-way house program, on parole or has been released from incarceration);
                </P>
                <P>8. VA employee's BDN or VETSNET identification numbers, the number and kind of actions generated and/or finalized by each such employee, the compilation of cases returned for each employee.</P>
                <P>
                    <E T="03">System(s) of Records:</E>
                     Compensation, Pension, Education, and Vocational Rehabilitation and Employment Records—VA (58 VA 21/22/28), published at 74 FR 29275 (June 19, 2009), last amended at 77 FR 42593 on July 19, 2012. Justice/BOP-005, published on June 7, 1984 (48 FR 2371 1), republished on May 9, 2002 (67 FR 31371), January 25, 2007 (72 FR 3410) and April 26, 2012 (77 FR 24982) and last modified on February 19, 2013 (78 FR 1 1575), routine use (i).
                </P>
                <P>The Senior Agency Official for Privacy, or designee, approved this document and authorized the undersigned to sign and submit the document to the Office of the Federal Register for publication electronically as an official document of the Department of Veterans Affairs. James P. Gfrerer, Assistant Secretary for Information and Technology and Chief Information Officer, Department of Veterans Affairs approved this document on April 5, 2019 for publication.</P>
                <SIG>
                    <DATED>Dated: May 8, 2019.</DATED>
                    <NAME>Amy L. Rose,</NAME>
                    <TITLE>Program Analyst, VA Privacy Service, Department of Veterans Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2019-09757 Filed 5-10-19; 8:45 am]</FRDOC>
            <BILCOD> BILLING CODE P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>84</VOL>
    <NO>92</NO>
    <DATE>Monday, May 13, 2019</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="20971"/>
            <PARTNO>Part II</PARTNO>
            <AGENCY TYPE="P"> Bureau of Consumer Financial Protection</AGENCY>
            <CFR>12 CFR Part 1003</CFR>
            <TITLE> Home Mortgage Disclosure (Regulation C); Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="20972"/>
                    <AGENCY TYPE="S">BUREAU OF CONSUMER FINANCIAL PROTECTION</AGENCY>
                    <CFR>12 CFR Part 1003</CFR>
                    <DEPDOC>[Docket No. CFPB-2019-0021]</DEPDOC>
                    <RIN>RIN 3170-AA76</RIN>
                    <SUBJECT>Home Mortgage Disclosure (Regulation C)</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Bureau of Consumer Financial Protection.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule with request for public comment.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The Bureau of Consumer Financial Protection (Bureau) is proposing two alternatives to amend Regulation C to increase the threshold for reporting data about closed-end mortgage loans so that institutions originating fewer than either 50 closed-end mortgage loans, or alternatively 100 closed-end mortgage loans, in either of the two preceding calendar years would not have to report such data as of January 1, 2020. The proposed rule would also adjust the threshold for reporting data about open-end lines of credit by extending to January 1, 2022, the current temporary threshold of 500 open-end lines of credit and setting the threshold at 200 open-end lines of credit upon the expiration of the proposed extension of the temporary threshold. The Bureau is also proposing to incorporate into Regulation C the interpretations and procedures from the interpretive and procedural rule that the Bureau issued on August 31, 2018, and to implement further section 104(a) of the Economic Growth, Regulatory Relief, and Consumer Protection Act.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Comments on the proposed rule must be received on or before June 12, 2019, except that comments on the Paperwork Reduction Act analysis in part VIII of the Supplementary Information must be received on or before July 12, 2019.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>You may submit responsive information and other comments, identified by Docket No. CFPB-2019-0021 or RIN 3170-AA76, by any of the following methods:</P>
                        <P>
                            • 
                            <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                             Follow the instructions for submitting comments.
                        </P>
                        <P>
                            • 
                            <E T="03">Email: 2019-NPRM-HMDAThresholds@cfpb.gov.</E>
                             Include Docket No. CFPB-2019-0021 or RIN 3170-AA76 in the subject line of the message.
                        </P>
                        <P>
                            • 
                            <E T="03">Mail:</E>
                             Comment Intake, Bureau of Consumer Financial Protection, 1700 G Street NW, Washington, DC 20552.
                        </P>
                        <P>
                            • 
                            <E T="03">Hand Delivery/Courier:</E>
                             Comment Intake, Bureau of Consumer Financial Protection, 1700 G Street NW, Washington, DC 20552.
                        </P>
                        <P>
                            <E T="03">Instructions:</E>
                             The Bureau encourages the early submission of comments. All submissions should include the agency name and docket number or Regulatory Information Number (RIN) for this rulemaking. Because paper mail in the Washington, DC area and at the Bureau is subject to delay, commenters are encouraged to submit comments electronically. In general, all comments received will be posted without change to 
                            <E T="03">http://www.regulations.gov.</E>
                             In addition, comments will be available for public inspection and copying at 1700 G Street NW, Washington, DC 20552, on official business days between the hours of 10:00 a.m. and 5:00 p.m. Eastern Time. You can make an appointment to inspect the documents by telephoning 202-435-7275.
                        </P>
                        <P>All comments, including attachments and other supporting materials, will become part of the public record and subject to public disclosure. Proprietary information or sensitive personal information, such as account numbers or Social Security numbers, or names of other individuals, should not be included. Comments will not be edited to remove any identifying or contact information.</P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Jaydee DiGiovanni or Shaakira Gold-Ramirez, Counsels; or Amanda Quester or Alexandra Reimelt, Senior Counsels, Office of Regulations, at 202-435-7700 or 
                            <E T="03">https://reginquiries.consumerfinance.gov/.</E>
                             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. Summary</HD>
                    <P>
                        Regulation C, 12 CFR part 1003, implements the Home Mortgage Disclosure Act (HMDA), 12 U.S.C. 2801 through 2810, and includes institutional and transactional coverage thresholds that determine whether financial institutions are required to collect, record, and report any HMDA data on closed-end mortgage loans or open-end lines of credit (collectively, coverage thresholds).
                        <SU>1</SU>
                        <FTREF/>
                         In the Economic Growth, Regulatory Relief, and Consumer Protection Act (EGRRCPA),
                        <SU>2</SU>
                        <FTREF/>
                         Congress added partial exemptions from HMDA's requirements that exempt certain insured depository institutions and insured credit unions from reporting some but not all HMDA data for certain transactions. The proposed rule both adjusts Regulation C's institutional and transactional coverage thresholds and implements the new, separate EGRRCPA partial exemptions.
                        <SU>3</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             HMDA requires financial institutions to collect, record, and report data. To simplify review of this document, the Bureau generally refers herein to the obligation to report data instead of listing all of these obligations in each instance.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             Public Law 115-174, 132 Stat. 1296 (2018).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             When amending commentary, the Office of the Federal Register requires reprinting of certain subsections being amended in their entirety rather than providing more targeted amendatory instructions. The sections of regulatory text and commentary included in this document show the language of those sections if the Bureau adopts its changes as proposed. In addition, the Bureau is releasing an unofficial, informal redline to assist industry and other stakeholders in reviewing the changes that it is proposing to make to the regulatory text and commentary of Regulation C. This redline can be found on the Bureau's regulatory implementation page for the HMDA Rule at 
                            <E T="03">https://www.consumerfinance.gov/policy-compliance/guidance/hmda-implementation/.</E>
                             If any conflicts exist between the redline and the text of Regulation C or this proposal, the documents published in the 
                            <E T="04">Federal Register</E>
                             and the Code of Federal Regulations are the controlling documents.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Coverage thresholds adjustments:</E>
                         In an October 2015 final rule (2015 HMDA Rule), the Bureau established institutional and transactional coverage thresholds in Regulation C, and these thresholds affect whether a financial institution needs to report any information under HMDA for a transaction.
                        <SU>4</SU>
                        <FTREF/>
                         The 2015 HMDA Rule set the closed-end threshold at 25 loans in each of the two preceding calendar years, and the open-end threshold at 100 open-end lines of credit in each of the two preceding calendar years. In 2017, the Bureau temporarily increased the open-end threshold to 500 open-end lines of credit for two years (calendar years 2018 and 2019). The proposed rule provides two alternatives that would permanently raise the closed-end institutional and transactional coverage threshold to either 50 or 100 closed-end mortgage loans in each of the preceding two calendar years. The proposed rule would also extend to January 1, 2022, the current temporary threshold of 500 open-end lines of credit for open-end institutional and transactional coverage. Once that temporary extension expires, the proposed rule would set the open-end threshold permanently at 200 open-end lines of credit in each of the preceding two calendar years. The Bureau is proposing that the change to the closed-end coverage threshold and the temporary extension of the open-end coverage threshold would take effect on January 1, 2020, and the increase in the open-end coverage threshold to 200 open-end lines of credit would take effect on January 1, 2022.
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             Home Mortgage Disclosure (Regulation C), 80 FR 66128 (Oct. 28, 2015).
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Implementation of partial exemptions:</E>
                         The proposed rule also 
                        <PRTPAGE P="20973"/>
                        implements the partial exemptions from HMDA's requirements that the EGRRCPA recently added to HMDA. In August 2018, the Bureau issued an interpretive and procedural rule to implement and clarify the EGRRCPA amendments to HMDA (2018 HMDA Rule).
                        <SU>5</SU>
                        <FTREF/>
                         The 2018 HMDA Rule clarifies that insured depository institutions and insured credit unions covered by a partial exemption have the option of reporting exempt data fields as long as they report all data fields within any exempt data point for which they report data; clarifies that only loans and lines of credit that are otherwise HMDA reportable count toward the thresholds for the partial exemptions; clarifies which of the data points in Regulation C are covered by the partial exemptions; designates a non-universal loan identifier for partially exempt transactions for institutions that choose not to report a universal loan identifier; and clarifies the exception to the partial exemptions for insured depository institutions with less than satisfactory examination histories under the Community Reinvestment Act of 1977 (CRA). The proposed rule incorporates into Regulation C these interpretations and procedures, with minor adjustments, by adding new § 1003.3(d) relating to the partial exemptions and making various amendments to the data compilation requirements in § 1003.4. The proposed rule further implements the EGRRCPA by addressing certain additional interpretive issues relating to the partial exemptions that the 2018 HMDA Rule did not specifically address, such as how to determine whether a partial exemption applies to a transaction after a merger or acquisition. The Bureau is proposing that the amendments implementing the EGRRCPA would take effect on January 1, 2020.
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             Partial Exemptions from the Requirements of the Home Mortgage Disclosure Act Under the Economic Growth, Regulatory Relief, and Consumer Protection Act (Regulation C), 83 FR 45325 (Sept. 7, 2018).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">II. Background</HD>
                    <HD SOURCE="HD2">A. HMDA and Regulation C</HD>
                    <P>
                        HMDA requires certain depository institutions and for-profit nondepository institutions to report data about originations and purchases of mortgage loans, as well as mortgage loan applications that do not result in originations (for example, applications that are denied or withdrawn). The purposes of HMDA are to provide the public with loan data that can be used: (i) To help determine whether financial institutions are serving the housing needs of their communities; (ii) to assist public officials in distributing public-sector investment so as to attract private investment to areas where it is needed; and (iii) to assist in identifying possible discriminatory lending patterns and enforcing antidiscrimination statutes.
                        <SU>6</SU>
                        <FTREF/>
                         Prior to enactment of the Dodd-Frank Wall Street Reform and Consumer Protection Act (Dodd-Frank Act), Regulation C required reporting of 22 data points and allowed for optional reporting of reasons an institution denied an application.
                        <SU>7</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             12 CFR 1003.1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             As used in this proposed rule, the term “data point” refers to items of information that entities are required to compile and report, generally listed in separate paragraphs in Regulation C. Some data points are reported using multiple data fields.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Dodd-Frank Act</HD>
                    <P>
                        In 2010, Congress enacted the Dodd-Frank Act, which amended HMDA and transferred HMDA rulemaking authority and other functions from the Board of Governors of the Federal Reserve System (Board) to the Bureau.
                        <SU>8</SU>
                        <FTREF/>
                         Among other changes, the Dodd-Frank Act expanded the scope of information relating to mortgage applications and loans that institutions must compile, maintain, and report under HMDA. Specifically, the Dodd-Frank Act amended HMDA section 304(b)(4) by adding one new data point, the age of loan applicants and mortgagors. The Dodd-Frank Act also added new HMDA section 304(b)(5) and (6), which requires the following additional new data points: Information relating to the total points and fees payable at origination (total loan costs or total points and fees); the difference between the annual percentage rate (APR) associated with the loan and a benchmark rate or rates for all loans (rate spread); the term of any prepayment penalty; the value of real property to be pledged as collateral; the term of the loan and of any introductory interest rate on the loan; the presence of contract terms allowing non-amortizing payments; the channel through which the application was made; and the credit scores of applicants and mortgagors.
                        <SU>9</SU>
                        <FTREF/>
                         New HMDA section 304(b)(6) in addition authorizes the Bureau to require, “as [it] may determine to be appropriate,” a unique identifier that identifies the loan originator, a universal loan identifier (ULI), and the parcel number that corresponds to the real property pledged as collateral for the mortgage loan.
                        <SU>10</SU>
                        <FTREF/>
                         New HMDA section 304(b)(5)(D) and (6)(J) further provides the Bureau with the authority to mandate reporting of “such other information as the Bureau may require.” 
                        <SU>11</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             Public Law 111-203, 124 Stat. 1376, 1980, 2035-38, 2097-101 (2010).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             Dodd-Frank Act section 1094(3), 
                            <E T="03">amending</E>
                             HMDA section 304(b), 12 U.S.C. 2803(b).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">C. 2015 HMDA Rule</HD>
                    <P>
                        In October 2015, the Bureau issued the 2015 HMDA Rule implementing the Dodd-Frank Act amendments to HMDA.
                        <SU>12</SU>
                        <FTREF/>
                         Most of the 2015 HMDA Rule took effect on January 1, 2018.
                        <SU>13</SU>
                        <FTREF/>
                         The 2015 HMDA Rule implemented the new data points specified in the Dodd-Frank Act,
                        <SU>14</SU>
                        <FTREF/>
                         added a number of additional data points pursuant to the Bureau's discretionary authority under HMDA section 304(b)(5) and (6),
                        <SU>15</SU>
                        <FTREF/>
                         and made revisions to certain pre-existing data points to clarify their requirements, provide greater specificity in reporting, and align certain data points more closely with industry data standards,
                        <SU>16</SU>
                        <FTREF/>
                         among other changes.
                    </P>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             80 FR 66128 (Oct. 28, 2015).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             
                            <E T="03">Id.</E>
                             at 66128, 66256-58.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             The following 12 data points in 12 CFR 1003.4(a) implement specific provisions in HMDA section 304(b)(5)(A) through (C) or (b)(6)(A) through (I): ULI (1003.4(a)(1)(i)); property address (1003.4(a)(9)(i)); rate spread (1003.4(a)(12)); credit score (1003.4(a)(15)); total loan costs or total points and fees (1003.4(a)(17)); prepayment penalty term (1003.4(a)(22)); loan term (1003.4(a)(25)); introductory rate period (1003.4(a)(26)); non-amortizing features (1003.4(a)(27)); property value (1003.4(a)(28)); application channel (1003.4(a)(33)); and mortgage loan originator identifier (1003.4(a)(34)). 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             For example, the 2015 HMDA Rule added a requirement to report debt-to-income ratio in § 1003.4(a)(23). 
                            <E T="03">Id.</E>
                             at 66218-20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             For example, the 2015 HMDA Rule replaced property type with number of total units and construction method in § 1003.4(a)(5) and (31). 
                            <E T="03">Id.</E>
                             at 66180-81, 66227. It also requires disaggregation of ethnicity and race information in § 1003.4(a)(10)(i). 
                            <E T="03">Id.</E>
                             at 66187-94.
                        </P>
                    </FTNT>
                    <P>The 2015 HMDA Rule requires some financial institutions to report data on certain dwelling-secured, open-end lines of credit, including home-equity lines of credit. Prior to the 2015 HMDA Rule, Regulation C allowed, but did not require, reporting of home-equity lines of credit.</P>
                    <P>
                        The 2015 HMDA Rule also established institutional coverage thresholds based on loan volume that limit the definition of “financial institution” to include only those institutions that either originated at least 25 closed-end mortgage loans in each of the two preceding calendar years or originated at least 100 open-end lines of credit in each of the two preceding calendar years.
                        <SU>17</SU>
                        <FTREF/>
                         The 2015 
                        <PRTPAGE P="20974"/>
                        HMDA Rule separately established transactional coverage thresholds that are part of the test for determining which loans are excluded from coverage and were designed to work in tandem with the institutional coverage thresholds.
                        <SU>18</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             
                            <E T="03">Id.</E>
                             at 66148-50, 66309 (codified at 12 CFR 1003.2(g)(1)(v)). The 2015 HMDA Rule excludes certain transactions from the definition of covered loans, and those excluded transactions do not count towards the threshold. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             
                            <E T="03">Id.</E>
                             at 66173, 66310, 66322 (codified at 12 CFR 1003.3(c)(11) and (12)).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">D. 2017 HMDA Rule and December 2017 Statement</HD>
                    <P>
                        In April 2017, the Bureau issued a notice of proposed rulemaking to address certain technical errors in the 2015 HMDA Rule, ease the burden of reporting certain data requirements, and clarify key terms to facilitate compliance with Regulation C.
                        <SU>19</SU>
                        <FTREF/>
                         In July 2017, the Bureau issued a notice of proposed rulemaking (July 2017 HMDA Proposal) to increase temporarily the 2015 HMDA Rule's open-end coverage threshold of 100 for both institutional and transactional coverage, so that institutions originating fewer than 500 open-end lines of credit in either of the two preceding calendar years would not have to commence collecting or reporting data on their open-end lines of credit until January 1, 2020.
                        <SU>20</SU>
                        <FTREF/>
                         In August 2017, the Bureau issued the 2017 HMDA Rule, which, inter alia, temporarily increased the open-end threshold to 500 open-end lines of credit for calendar years 2018 and 2019.
                        <SU>21</SU>
                        <FTREF/>
                         In doing so, the Bureau indicated that the two-year period would allow time for the Bureau to decide, through an additional rulemaking, whether any permanent adjustments to the open-end threshold are needed.
                        <SU>22</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             Technical Corrections and Clarifying Amendments to the Home Mortgage Disclosure (Regulation C) October 2015 Final Rule, 82 FR 19142 (Apr. 25, 2017).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             Home Mortgage Disclosure (Regulation C) Temporary Increase in Institutional and Transactional Coverage Thresholds for Open-End Lines of Credit, 82 FR 33455 (July 20, 2017).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             Home Mortgage Disclosure (Regulation C), 82 FR 43088 (Sept. 13, 2017).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             
                            <E T="03">Id.</E>
                             at 43095. The 2017 HMDA Rule also, among other things, replaced “each” with “either” in § 1003.3(c)(11) and (12) to correct a drafting error and to ensure that the exclusion provided in that section mirrors the loan-volume threshold for financial institutions in § 1003.2(g). 
                            <E T="03">Id.</E>
                             at 43100, 43102.
                        </P>
                    </FTNT>
                    <P>
                        Recognizing the significant systems and operations challenges needed to adjust to the revised regulation, the Bureau issued a statement in December 2017 (December 2017 Statement) indicating that, for HMDA data collected in 2018 and reported in 2019, the Bureau does not intend to require data resubmission unless data errors are material.
                        <SU>23</SU>
                        <FTREF/>
                         The December 2017 Statement also explained that the Bureau does not intend to assess penalties with respect to errors in data collected in 2018 and reported in 2019.
                        <SU>24</SU>
                        <FTREF/>
                         As explained in the statement, any supervisory examinations of 2018 HMDA data would be diagnostic to help institutions identify compliance weaknesses and would credit good-faith compliance efforts. In its December 2017 Statement, the Bureau indicated that it intended to engage in a rulemaking to reconsider various aspects of the 2015 HMDA Rule, such as the institutional and transactional coverage tests and the rule's discretionary data points. The Board, the Federal Deposit Insurance Corporation (FDIC), the National Credit Union Administration (NCUA), and the Office of the Comptroller of the Currency (OCC) released similar statements relating to their supervisory examinations.
                        <SU>25</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             Bureau of Consumer Fin. Prot., “Statement with Respect to HMDA Implementation” (Dec. 21, 2017), 
                            <E T="03">https://files.consumerfinance.gov/f/documents/cfpb_statement-with-respect-to-hmda-implementation_122017.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                             The statement also indicated that collection and submission of the 2018 HMDA data will provide financial institutions an opportunity to identify any gaps in their implementation of amended Regulation C and make improvements in their HMDA compliance management systems for future years. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>25</SU>
                             As part of its spring 2018 Call for Evidence series of Requests for Information, the Bureau issued a Request for Information Regarding the Bureau's Adopted Regulations and New Rulemaking Authorities, 83 FR 12286 (Mar. 21, 2018) (RFI on Adopted Regulations) and a Request for Information Regarding the Bureau's Inherited Regulations and Inherited Rulemaking Authorities, 83 FR 12881 (Mar. 26, 2018). The RFI on Adopted Regulations did not request feedback on the 2015 HMDA Rule nor that rule's subsequent amendments because the Bureau had previously announced in the December 2017 Statement that it intended to engage in a rulemaking process to reconsider the 2015 HMDA Rule. However, as noted below in the section-by-section analysis of § 1003.2(g)(1)(v) in part IV, the Bureau received a few comments relating to HMDA in response to the RFI on Adopted Regulations. The Bureau has considered these comments as well as other input it has received from stakeholders through its efforts to monitor and support industry implementation of the 2015 HMDA Rule and the 2017 HMDA Rule in developing this proposal and the Advance Notice of Proposed Rulemaking that the Bureau released simultaneously with this proposal. The Advance Notice of Proposed Rulemaking (FR Doc. 2019-08979) published in the 
                            <E T="04">Federal Register</E>
                             on May 8, 2019.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">E. EGRRCPA and 2018 HMDA Rule</HD>
                    <P>
                        On May 24, 2018, the President signed into law the EGRRCPA.
                        <SU>26</SU>
                        <FTREF/>
                         Section 104(a) of the EGRRCPA amends HMDA section 304(i) by adding partial exemptions from HMDA's requirements for certain insured depository institutions and insured credit unions.
                        <SU>27</SU>
                        <FTREF/>
                         New HMDA section 304(i)(1) provides that the requirements of HMDA section 304(b)(5) and (6) shall not apply with respect to closed-end mortgage loans of an insured depository institution or insured credit union if it originated fewer than 500 closed-end mortgage loans in each of the two preceding calendar years. New HMDA section 304(i)(2) provides that the requirements of HMDA section 304(b)(5) and (6) shall not apply with respect to open-end lines of credit of an insured depository institution or insured credit union if it originated fewer than 500 open-end lines of credit in each of the two preceding calendar years. Notwithstanding the new partial exemptions, new HMDA section 304(i)(3) provides that an insured depository institution must comply with HMDA section 304(b)(5) and (6) if it has received a rating of “needs to improve record of meeting community credit needs” during each of its two most recent examinations or a rating of “substantial noncompliance in meeting community credit needs” on its most recent examination under section 807(b)(2) of the CRA.
                        <SU>28</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>26</SU>
                             Public Law 115-174, 132 Stat. 1296 (2018).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>27</SU>
                             For purposes of HMDA section 104, the EGRRCPA provides that the term “insured credit union” has the meaning given the term in section 101 of the Federal Credit Union Act, 12 U.S.C. 1752, and the term “insured depository institution” has the meaning given the term in section 3 of the Federal Deposit Insurance Act, 12 U.S.C. 1813.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>28</SU>
                             12 U.S.C. 2906(b)(2).
                        </P>
                    </FTNT>
                    <P>
                        On August 31, 2018, the Bureau issued an interpretive and procedural rule (2018 HMDA Rule) to implement and clarify section 104(a) of the EGRRCPA and effectuate the purposes of the EGRRCPA and HMDA.
                        <SU>29</SU>
                        <FTREF/>
                         The 2018 HMDA Rule clarifies that insured depository institutions and insured credit unions covered by a partial exemption have the option of reporting exempt data fields as long as they report all data fields within any exempt data point for which they report data; clarifies that only loans and lines of credit that are otherwise HMDA reportable count toward the thresholds 
                        <PRTPAGE P="20975"/>
                        for the partial exemptions; clarifies which of the data points in Regulation C are covered by the partial exemptions; designates a non-universal loan identifier for partially exempt transactions for institutions that choose not to report a ULI; and clarifies the exception to the partial exemptions for insured depository institutions with less than satisfactory CRA examination histories. The 2018 HMDA Rule also explains that, because the EGRRCPA does not provide a specific effective date for section 104(a) and because there are no other statutory indications that section 104(a) becomes effective upon regulatory action or some other event or condition, the best interpretation is that section 104(a) took effect when the EGRRCPA became law on May 24, 2018. In the 2018 HMDA Rule, the Bureau stated that it anticipated that, at a later date, it would initiate a notice-and-comment rulemaking to incorporate the interpretations and procedures into Regulation C and further implement the EGRRCPA. This proposal commences that rulemaking. The Bureau also issued concurrently an Advance Notice of Proposed Rulemaking to solicit comment, data, and information from the public about the data points that the 2015 HMDA Rule added to Regulation C or revised to require additional information and Regulation C's coverage of certain business- or commercial-purpose transactions. The Advance Notice of Proposed Rulemaking (FR Doc. 2019-08979) published in the 
                        <E T="04">Federal Register</E>
                         on May 8, 2019.
                    </P>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             83 FR 45325 (Sept. 7, 2018). Prior to issuing the 2018 HMDA Rule, the Bureau, the Board, the FDIC, the NCUA, and the OCC released statements on July 5, 2018, reiterating or referring to their December 2017 compliance statements and providing information about formatting and submission of 2018 loan/application registers. 
                            <E T="03">See, e.g.,</E>
                             Bureau of Consumer Fin. Prot., “Statement on the Implementation of the Economic Growth, Regulatory Relief, and Consumer Protection Act Amendments to the Home Mortgage Disclosure Act” (July 25, 2018), 
                            <E T="03">https://www.consumerfinance.gov/about-us/newsroom/bureau-consumer-financial-protection-issues-statement-implementation-economic-growth-regulatory-relief-and-consumer-protection-act-amendments-home-mortgage-disclosure-act/.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">F. HMDA Coverage Under Current Regulation C</HD>
                    <P>
                        The Bureau's estimates of HMDA coverage and the sources used in deriving those estimates are explained in detail in the Bureau's analysis under Dodd-Frank Act section 1022(b) in part VI below.
                        <SU>30</SU>
                        <FTREF/>
                         As explained in more detail in part VI.E.3 and table 3 below, the Bureau estimates that currently there are about 4,960 financial institutions required to report their closed-end mortgage loans and applications under HMDA. The Bureau estimates that approximately 4,263 of these current reporters are depository institutions and approximately 697 are non-depository institutions. The Bureau estimates that together, these financial institutions originated about 7.0 million closed-end mortgage loans in calendar year 2017. The Bureau estimates that among those 4,960 financial institutions that are currently required to report closed-end mortgage loans under HMDA, about 3,300 insured depository institutions and insured credit unions are partially exempt for closed-end mortgage loans under the EGRRCPA and the 2018 HMDA Rule, and thus are not required to report a subset of the data points currently required by Regulation C for these transactions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>30</SU>
                             
                            <E T="03">See infra</E>
                             part VI.D.1 &amp; n.155.
                        </P>
                    </FTNT>
                    <P>As explained in more detail in part VI.E.4 and table 4 below, under the temporary 500 open-end line of credit coverage threshold set in the 2017 HMDA Rule, the Bureau estimates that currently there are about 333 financial institutions required to report about 1.23 million open-end lines of credit under HMDA. Of these institutions, approximately 318 are depository institutions and approximately 15 are nondepository institutions. None of these 333 institutions are partially exempt.</P>
                    <P>In comparison, if the open-end coverage threshold adjusts to 100 on January 1, 2020 pursuant to the 2017 HMDA Rule, the Bureau estimates that the number of reporters would be about 1,014, who in total originate about 1.41 million open-end lines of credit. The Bureau estimates that approximately 972 of these open-end reporters would be depository institutions and approximately 42 would be nondepository institutions. The Bureau estimates that, among the 1,014 financial institutions that would be required to report open-end lines of credit under a threshold of 100, about 618 insured depository institutions and insured credit unions are partially exempt for open-end lines of credit under the EGRRCPA and the 2018 HMDA Rule, and thus would not be required to report a subset of the data points currently required by Regulation C for these transactions.</P>
                    <HD SOURCE="HD1">III. Legal Authority</HD>
                    <P>
                        The Bureau is issuing this proposal pursuant to its authority under the Dodd-Frank Act and HMDA. Section 1061 of the Dodd-Frank Act transferred to the Bureau the “consumer financial protection functions” previously vested in certain other Federal agencies, including the Board.
                        <SU>31</SU>
                        <FTREF/>
                         The term “consumer financial protection function” is defined to include “all authority to prescribe rules or issue orders or guidelines pursuant to any Federal consumer financial law, including performing appropriate functions to promulgate and review such rules, orders, and guidelines.” 
                        <SU>32</SU>
                        <FTREF/>
                         Section 1022(b)(1) of the Dodd-Frank Act authorizes the Bureau's Director to prescribe rules “as may be necessary or appropriate to enable the Bureau to administer and carry out the purposes and objectives of the Federal consumer financial laws, and to prevent evasions thereof.” 
                        <SU>33</SU>
                        <FTREF/>
                         Both HMDA and title X of the Dodd-Frank Act are Federal consumer financial laws.
                        <SU>34</SU>
                        <FTREF/>
                         Accordingly, the Bureau has authority to issue regulations to implement HMDA.
                    </P>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             12 U.S.C. 5581. Section 1094 of the Dodd-Frank Act also replaced the term “Board” with “Bureau” in most places in HMDA. 12 U.S.C. 2803 
                            <E T="03">et seq.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             12 U.S.C. 5581(a)(1)(A).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>33</SU>
                             12 U.S.C. 5512(b)(1).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>34</SU>
                             Dodd-Frank Act section 1002(14), 12 U.S.C. 5481(14) (defining “Federal consumer financial law” to include the “enumerated consumer laws” and the provisions of title X of the Dodd-Frank Act); Dodd-Frank Act section 1002(12), 12 U.S.C. 5481(12) (defining “enumerated consumer laws” to include HMDA).
                        </P>
                    </FTNT>
                    <P>
                        HMDA section 305(a) broadly authorizes the Bureau to prescribe such regulations as may be necessary to carry out HMDA's purposes.
                        <SU>35</SU>
                        <FTREF/>
                         These regulations may include classifications, differentiations, or other provisions, and may provide for such adjustments and exceptions for any class of transactions, as in the judgment of the Bureau are necessary and proper to effectuate the purposes of [HMDA], and prevent circumvention or evasion thereof, or to facilitate compliance therewith.
                        <SU>36</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>35</SU>
                             12 U.S.C. 2804(a).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>36</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">IV. Section-by-Section Analysis</HD>
                    <HD SOURCE="HD2">Section 1003.2 Definitions</HD>
                    <HD SOURCE="HD3">2(g) Financial Institution</HD>
                    <P>
                        Regulation C requires financial institutions to report HMDA data. Section 1003.2(g) defines financial institution for purposes of Regulation C and sets forth Regulation C's institutional coverage criteria for depository financial institutions and nondepository financial institutions.
                        <SU>37</SU>
                        <FTREF/>
                         In the 2015 HMDA Rule, the Bureau adjusted the institutional coverage criteria under Regulation C so that depository institutions and nondepository institutions are required to report HMDA data if they: (1) Originated at least 25 closed-end mortgage loans or 100 open-end lines of credit in each of the two preceding calendar years, and (2) meet all of the other applicable criteria for reporting. In the 2017 HMDA Rule, the Bureau amended § 1003.2(g) and related commentary to increase temporarily from 100 to 500 the number of open-end originations required to trigger reporting responsibilities.
                        <SU>38</SU>
                        <FTREF/>
                         For the reasons discussed below, the Bureau proposes (1) to amend §§ 1003.2(g)(1)(v)(A) and 
                        <PRTPAGE P="20976"/>
                        (g)(2)(ii)(A) and 1003.3(c)(11) and related commentary to raise the closed-end coverage threshold to either 50 or 100 closed-end mortgage loans, and (2) to amend §§ 1003.2(g)(1)(v)(B) and (g)(2)(ii)(B) and 1003.3(c)(12) and related commentary to extend to January 1, 2022, the current temporary open-end coverage threshold of 500 open-end lines of credit and then to set the threshold permanently at 200 open-end lines of credit beginning in calendar year 2022. The Bureau is also seeking comment on whether other closed- and open-end coverage thresholds may be appropriate. These proposed changes are discussed below in the order in which they appear in the proposed regulation text and commentary.
                    </P>
                    <FTNT>
                        <P>
                            <SU>37</SU>
                             12 CFR 1003.2(g)(1) (definition of depository financial institution); § 1003.2(g)(2) (definition of nondepository financial institution).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>38</SU>
                             82 FR 43088, 43095 (Sept. 13, 2017).
                        </P>
                    </FTNT>
                    <P>
                        In the 2015 HMDA Rule, the Bureau adopted the thresholds for certain depository institutions in § 1003.2(g)(1) pursuant to its authority under section 305(a) of HMDA to provide for such adjustments and exceptions for any class of transactions that in the judgment of the Bureau are necessary and proper to effectuate the purposes of HMDA. Pursuant to section 305(a) of HMDA, for the reasons given in the 2015 HMDA Rule, the Bureau found that the exception in § 1003.2(g)(1) is necessary and proper to effectuate the purposes of and facilitate compliance with HMDA. The Bureau found that the provision, by reducing burden on financial institutions and establishing a consistent loan-volume test applicable to all financial institutions, would facilitate compliance with HMDA's requirements.
                        <SU>39</SU>
                        <FTREF/>
                         Additionally, as discussed in the 2015 HMDA Rule, the Bureau adopted the thresholds for certain nondepository institutions in § 1003.2(g)(2) pursuant to its interpretation of HMDA sections 303(3)(B) and 303(5), which require persons other than banks, savings associations, and credit unions that are “engaged for profit in the business of mortgage lending” to report HMDA data. The Bureau stated that it interprets these provisions, as the Board also did, to evince the intent to exclude from coverage institutions that make a relatively small number of mortgage loans.
                        <SU>40</SU>
                        <FTREF/>
                         Pursuant to its authority under HMDA section 305(a), and for the reasons discussed below, the Bureau believes that the proposed threshold changes in § 1003.2(g)(1) and (2) would be necessary and proper to effectuate the purposes of HMDA and facilitate compliance with HMDA by reducing burden and establishing a consistent loan-volume test.
                    </P>
                    <FTNT>
                        <P>
                            <SU>39</SU>
                             80 FR 66128, 66150 (Oct. 28, 2015).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>40</SU>
                             
                            <E T="03">Id.</E>
                             at 66153.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2(g)(1) Depository Financial Institution</HD>
                    <HD SOURCE="HD3">2(g)(1)(v)</HD>
                    <HD SOURCE="HD3">2(g)(1)(v)(A)</HD>
                    <HD SOURCE="HD3">Closed-End Mortgage Loan Threshold for Institutional Coverage of Depository Institutions</HD>
                    <P>
                        HMDA and its implementing regulation, Regulation C, require certain depository institutions (banks, savings associations, and credit unions) to report data about originations and purchases of mortgage loans, as well as mortgage loan applications that do not result in originations (for example, applications that are denied or withdrawn). In the 2015 HMDA Rule, the Bureau added the 25 closed-end coverage threshold to the preexisting regulatory coverage scheme for depository institutions.
                        <SU>41</SU>
                        <FTREF/>
                         In adopting this threshold, the Bureau stated that it believed that the institutional coverage criteria should balance the burden on financial institutions of reporting HMDA data against the value of the data reported and that a threshold should be set that did not impair HMDA's ability to achieve its purposes but also did not impose burden on institutions if their data are of limited value.
                        <SU>42</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>41</SU>
                             Prior to the 2015 HMDA Rule, a bank, savings association, or credit union was covered under Regulation C if: (1) On the preceding December 31, it satisfied an asset-size threshold; (2) on the preceding December 31, it had a home or branch office in a Metropolitan Statistical Area (MSA); (3) during the previous calendar year, it originated at least one home purchase loan or refinancing of a home purchase loan secured by a first lien on a one- to four-unit dwelling; and (4) the institution is federally insured or regulated, or the mortgage loan referred to in item (3) was insured, guaranteed, or supplemented by a Federal agency or intended for sale to the Federal National Mortgage Association or the Federal Home Loan Mortgage Corporation. 12 CFR 1003.2 (2016).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>42</SU>
                             80 FR 66128, 66147 (Oct. 28, 2015).
                        </P>
                    </FTNT>
                    <P>
                        In the 2015 HMDA Rule, the Bureau also stated that in adopting the 25 closed-end coverage threshold, it would meaningfully reduce burden by relieving an estimated 1,400 depository institutions, or 22 percent of depository institutions that previously reported HMDA data, of their obligations to report HMDA data on closed-end mortgage loans.
                        <SU>43</SU>
                        <FTREF/>
                         The Bureau acknowledged that it would be possible to maintain reporting of a significant percentage of the national mortgage market with a closed-end coverage threshold set higher than 25 loans annually and that data reported by some institutions that would satisfy the 25 closed-end coverage threshold may not be as useful for statistical analysis as data reported by institutions with much higher loan volumes.
                        <SU>44</SU>
                        <FTREF/>
                         However, the Bureau determined that a higher closed-end coverage threshold would have a material negative impact on the availability of data about patterns and trends at the local level and the data about local communities are essential to achieve HMDA's purposes.
                        <SU>45</SU>
                        <FTREF/>
                         The Bureau concluded that, if it were to set the closed-end coverage threshold higher than 25, the resulting loss of data at the local level would substantially impede the public's and public officials' ability to understand access to credit in their communities.
                        <SU>46</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>43</SU>
                             
                            <E T="03">Id.</E>
                             at 66148, 66277.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>44</SU>
                             
                            <E T="03">Id.</E>
                             at 66147.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>45</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>46</SU>
                             
                            <E T="03">Id.</E>
                             at 66148.
                        </P>
                    </FTNT>
                    <P>
                        However, since issuing the 2015 HMDA Rule and 2017 HMDA Rule, the Bureau has heard concerns that lower-volume institutions continue to experience significant burden at the 25 closed-end coverage threshold.
                        <SU>47</SU>
                        <FTREF/>
                         Various industry stakeholders have advocated for an increase to the coverage threshold in order to reduce burden on additional lower-volume financial institutions. For example, although the 2015 HMDA Rule was outside the scope of the Bureau's 2018 Request for Information Regarding the Bureau's Adopted Regulations and New Rulemaking Authorities (RFI on Adopted Regulations),
                        <SU>48</SU>
                        <FTREF/>
                         several depository institutions recommended in that context that the Bureau use its exemption authority to increase the 25-loan closed-end coverage threshold and stated that the costs associated with HMDA reporting and its impact on the operations of lower-volume financial institutions do not justify the small amount of data such institutions would report. The closed-end coverage threshold should not be so high as to impair HMDA's ability to achieve its purposes; however, the threshold should not be so low that institutions bear the burden of reporting data that would be of limited value. In light of the recent concerns expressed by industry stakeholders regarding the considerable burden associated with reporting the 
                        <PRTPAGE P="20977"/>
                        new data points required by the 2015 HMDA Rule on closed-end mortgage loans, the Bureau is reconsidering whether the current 25-loan closed-end coverage threshold for depository institutions appropriately balances the benefits of the HMDA data reported by lower-volume depository institutions in furthering HMDA's purposes with the burden on such institutions associated with reporting closed-end data. The Bureau believes that increasing the closed-end coverage threshold may provide meaningful burden relief for lower-volume depository institutions without reducing substantially the data reported under HMDA. Accordingly, based on its evaluation of more recent available data, the Bureau is proposing two alternative increases to the closed-end coverage threshold and seeking comment on whether either of these alternatives, or some other alternative, would more appropriately balance the benefits and burdens of covering institutions based on their closed-end lending.
                    </P>
                    <FTNT>
                        <P>
                            <SU>47</SU>
                             The Bureau temporarily raised the threshold for open-end lines of credit in the 2017 HMDA Rule because of concerns that the Bureau may have underestimated in the 2015 HMDA Rule the number of institutions that would be required to report open-end lines of credit under the threshold adopted and that it also may have underestimated the cost of reporting. However, the Bureau declined to raise the threshold for closed-end mortgage loans and stated that in developing the 2015 HMDA Rule, it had robust data to make a determination about the number of transactions that would be reported at the 25 closed-end coverage threshold as well as the one-time and ongoing costs to industry. 82 FR 43088, 43095-96 (Sept. 13, 2017).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>48</SU>
                             83 FR 12286, 12288 (Mar. 21, 2018).
                        </P>
                    </FTNT>
                    <P>The Bureau recognizes that in the EGRRCPA, Congress provided a partial exemption to institutions that would be affected by this proposed increase to the threshold so that the benefit in terms of reduced burden would be less than it would have been absent the EGRRCPA. Even so, the Bureau believes that, for the depository institutions that would be relieved of all reporting obligations under either of the alternatives in this proposal, the burden reduction would be substantial and would outweigh the limited value of their data in achieving HMDA's purposes. The Bureau has also heard feedback suggesting that—consistent with its own estimates—a modest increase in the closed-end coverage threshold likely would have very little impact on the overall HMDA data, because the amount of data reported by the lower-volume depository institutions that would be excluded at such a higher threshold is insignificant as compared to the total HMDA data reported annually. The Bureau now believes a higher closed-end coverage threshold may more appropriately balance the burden on lower-volume depository institutions while at the same time maintaining sufficient reporting to achieve HMDA's purposes.</P>
                    <P>
                        As discussed below, the Bureau is proposing two alternatives to the closed-end coverage threshold. These proposed alternatives would maintain a uniform loan-volume threshold for depository and nondepository institutions.
                        <SU>49</SU>
                        <FTREF/>
                         Alternative 1 proposes to set the closed-end coverage threshold at 50 while Alternative 2 proposes to set the closed-end coverage threshold at 100. The Bureau reviewed multiple data sources, including recent HMDA data 
                        <SU>50</SU>
                        <FTREF/>
                         and Reports of Condition and Income (Call Reports) and developed estimates for each proposal as described below.
                        <SU>51</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>49</SU>
                             For a discussion on the proposed closed-end coverage threshold for nondepository institutions, see the section-by-section analysis of § 1003.2(g)(2)(ii)(A) below.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>50</SU>
                             As discussed further in the analysis under Dodd-Frank Act section 1022(b) in part VI, note 155, these estimates are based on HMDA data collected in 2016 and 2017 and other sources. The Bureau intends to review the 2018 HMDA data more closely in connection with this rulemaking once the 2018 submissions are more complete.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>51</SU>
                             The estimates described in each alternative proposal in this section cover only depository institutions. Estimates for nondepository institutions are described in the section-by-section analysis of § 1003.2(g)(2)(ii)(A). For estimates that are comprehensive of depository and nondepository institutions, see part VI.E.3 below.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Alternative 1: Threshold Set at 50</HD>
                    <P>The Bureau estimates that if the closed-end coverage threshold were increased from 25 to 50 loans, approximately 3,518 out of approximately 4,263 depository institutions covered under the current rule (or approximately 83 percent) would continue to be required to report HMDA data on closed-end mortgage loans. Approximately 745 depository institutions covered under the current rule (or approximately 17 percent) would be relieved of their HMDA reporting responsibilities for closed-end mortgage loans. Further, the Bureau estimates that, with the proposed increase from 25 to 50 loans in the closed-end coverage threshold, about 99 percent of total originations of closed-end mortgage loans reported by depository institutions under the current Regulation C coverage criteria, or approximately 3.54 million closed-end mortgage loan originations under the current market conditions, would continue to be reported.</P>
                    <P>
                        The Bureau noted in the 2015 HMDA Rule that any loan-volume threshold will affect individual markets differently, depending on the extent to which smaller creditors service individual markets and the market share of those creditors. In the 2015 HMDA Rule, the Bureau examined the extent to which varying thresholds would cause a loss of data at the census tract level. For this proposal the Bureau also reviewed estimates at varying closed-end coverage thresholds to examine the potential effect on available data at the census tract level.
                        <SU>52</SU>
                        <FTREF/>
                         The Bureau estimates that, with the proposed increase to the closed-end coverage threshold from 25 to 50, just under 300 out of approximately 74,000 total census tracts, or less than one-half of 1 percent of the total number of census tracts, would lose at least 20 percent of reportable HMDA data on closed-end mortgage loans relative to the current threshold.
                        <SU>53</SU>
                        <FTREF/>
                         With respect to low-to-moderate income census tracts, the Bureau estimates that relative to the current threshold, there would be at least a 20 percent loss of reportable HMDA data on closed-end mortgage loans in less than 1 percent of such tracts if the closed-end coverage threshold were increased from 25 to the proposed 50. In addition, the Bureau examined the effects on rural census tracts and estimates that relative to the current threshold, there would be at least a 20 percent loss of reportable HMDA data on closed-end mortgage loans in less than one-half of 1 percent of such tracts.
                    </P>
                    <FTNT>
                        <P>
                            <SU>52</SU>
                             The estimates of the effect on reportable HMDA data at the census tract level comprise both depository institutions and nondepository institutions. The effect of a closed-end coverage threshold set at 100 on reportable HMDA data at the census tract level is discussed in Alternative 2 below.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>53</SU>
                             The Bureau estimates that at least 80 percent of reportable HMDA data would be retained in over 73,500 tracts. In certain tracts, substantially more than 80 percent of reportable HMDA data would be retained.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Ongoing cost reduction from proposed Alternative 1: Threshold set at 50.</E>
                         The proposed increase in the closed-end coverage threshold from 25 to 50 would relieve institutions that originate between 25 and 49 closed-end mortgage loans of the ongoing costs associated with reporting such loans that they might otherwise incur if the closed-end coverage threshold remained at the current 25. The Bureau estimates that the proposed increase in the closed-end coverage threshold to 50 would result in aggregate savings on the operational costs associated with reporting closed-end mortgage loans of approximately $2.2 million per year.
                        <SU>54</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>54</SU>
                             These cost estimates reflect the combined ongoing reduction in costs for depository and nondepository institutions. These estimates also take into account the enactment of the EGRRCPA, which created partial exemptions from HMDA's requirements that certain insured depository institutions and insured credit unions may now use. See part VI.E.3 below for a more comprehensive analysis on cost estimates.
                        </P>
                    </FTNT>
                    <P>
                        Therefore, the Bureau believes that if the closed-end coverage threshold were raised from 25 to the proposed 50, the loss in data from these depository institutions and for this relatively small number of census tracts may be justified by the significant reduction in compliance costs for the approximately 745 lower-volume depository 
                        <PRTPAGE P="20978"/>
                        institutions that would no longer be required to report HMDA data.
                    </P>
                    <HD SOURCE="HD3">Alternative 2: Threshold Set at 100</HD>
                    <P>The Bureau estimates that if the closed-end coverage threshold were increased from 25 to 100 loans, approximately 2,581 out of about 4,263 depository institutions covered under the current rule (or approximately 61 percent) would continue to be required to report HMDA data on closed-end mortgage loans. Approximately 1,682 depository institutions covered under the current rule (or approximately 39 percent) would be relieved of their HMDA reporting responsibilities with respect to closed-end mortgage loans. The Bureau estimates that with this proposed increase to the closed-end coverage threshold, approximately 96 percent of total originations of closed-end mortgage loans reported by depository institutions under the current coverage criteria, or approximately 3.43 million closed-end mortgage loan originations under the current market conditions, would continue to be reported.</P>
                    <P>
                        With respect to the potential effect on available data at the census tract level, the Bureau estimates that if the closed-end coverage threshold were increased from 25 to the proposed 100, there would be a loss of at least 20 percent of reportable HMDA data in about 1,100 out of approximately 74,000 total census tracts, or 1.5 percent of the total number of census tracts, relative to the current threshold.
                        <SU>55</SU>
                        <FTREF/>
                         For low-to-moderate income census tracts, the Bureau estimates that if the closed-end coverage threshold were increased from 25 to the proposed 100, there would be at least a 20 percent loss of reportable HMDA data in 3 percent of such tracts if the closed-end coverage threshold were set at the proposed 100. In addition, the Bureau examined the effects on rural census tracts and estimates that relative to the current threshold, there would be at least a 20 percent loss of reportable HMDA data in less than 3 percent of such tracts.
                    </P>
                    <FTNT>
                        <P>
                            <SU>55</SU>
                             The Bureau estimates that at least 80 percent of reportable HMDA data would be retained in approximately 73,000 tracts. In certain tracts, substantially more than 80 percent of reportable HMDA data would be retained.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Ongoing cost reduction from proposed Alternative 2: Threshold set at 100.</E>
                         The proposed increase in the closed-end coverage threshold from 25 to 100 would relieve institutions that originate between 25 and 99 closed-end mortgage loans of the ongoing costs associated with reporting such loans that they might otherwise incur if the closed-end coverage threshold remained at the current 25. The Bureau estimates that the proposed increase in the closed-end coverage threshold to 100 would result in aggregate savings on the operational costs associated with reporting closed-end mortgage loans of approximately $8.1 million per year.
                        <SU>56</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>56</SU>
                             These cost estimates reflect the combined ongoing reduction in costs for depository and nondepository institutions. These estimates also take into account the enactment of the EGRRCPA, which created partial exemptions from HMDA's requirements that certain insured depository institutions and insured credit unions may now use. See part VI.E.3 below for a more comprehensive analysis on cost estimates.
                        </P>
                    </FTNT>
                    <P>Therefore, the Bureau believes that if the closed-end coverage threshold were set at the proposed 100 the loss in data from these depository institutions and for this relatively small number of census tracts, although greater than at the proposed 50 closed-end coverage threshold, may be justified by the significant reduction in compliance costs for the approximately 1,682 lower-volume depository institutions that would no longer be required to report HMDA data relative to the current threshold.</P>
                    <HD SOURCE="HD3">Estimates for Other Closed-End Coverage Thresholds</HD>
                    <P>The Bureau also generated estimates for closed-end coverage thresholds higher than the ones in the proposed alternatives. These estimates reflect that the decrease in the number of depository institutions that would be required to report HMDA data and the resulting decrease in the HMDA data that would be reported becomes more pronounced at thresholds higher than 100. For example, if the closed-end coverage threshold were increased from 25 to 250 loans, the Bureau estimates that approximately 1,413 out of approximately 4,263 depository institutions would continue to report HMDA data and approximately 2,850 depository institutions, or approximately 67 percent of depository institutions covered under the current rule, would be relieved of their HMDA reporting responsibilities. The Bureau estimates that with an increase in the closed-end coverage threshold from 25 to 250, approximately 90 percent of total originations of closed-end mortgage loans reported by depository institutions under the current coverage criteria, or approximately 3.21 million closed-end mortgage loan originations under the current market conditions, would continue to be reported.</P>
                    <P>Further, if the closed-end coverage threshold were increased from 25 to 500 loans, the Bureau estimates that approximately 798 out of 4,263 depository institutions would continue to be required to report HMDA data and approximately 3,465 depository institutions, or approximately 81 percent of depository institutions covered under the current coverage criteria, would be relieved of their HMDA reporting responsibilities. The Bureau estimates that with an increase in the closed-end coverage threshold to 500, approximately 83 percent of total originations of closed-end mortgage loans reported by depository institutions under the current Regulation C coverage criteria, or approximately 2.97 million closed-end mortgage loan originations under the current market conditions, would continue to be reported.</P>
                    <P>
                        The Bureau's estimates also reflect that the effect on data available at the census tract level would become more pronounced at closed-end mortgage loan coverage thresholds above 100. For example, the Bureau estimates that increasing the closed-end coverage threshold from 25 to 250 loans would result in a loss of at least 20 percent of reportable HMDA data on closed-end mortgage loans in over 4,000 out of approximately 74,000 total census tracts, or 5.4 percent of the total number census tracts. Of the approximately 4,000 census tracts where there would be a loss of at least 20 percent of reportable HMDA data on closed-end mortgage loans at such threshold, about 14 percent are rural tracts 
                        <SU>57</SU>
                        <FTREF/>
                         and just over 8 percent are low-to-moderate income tracts. Further, the Bureau estimates that increasing the closed-end coverage threshold from 25 to 500 loans would result in a loss of at least 20 percent of reportable HMDA data on closed-end mortgage loans in approximately 11,000 out of approximately 74,000 total census tracts, or 14.9 percent of the total number of census tracts. Of the approximately 11,000 census tracts where there would be a loss of at least 20 percent of reportable HMDA data on closed-end mortgage loans at such threshold, about 32 percent are rural tracts and about 17 percent are low-to-moderate income tracts.
                    </P>
                    <FTNT>
                        <P>
                            <SU>57</SU>
                             As discussed in part VI.F.2 below, recent research suggests that financial institutions that serve rural areas are generally not HMDA reporters. HMDA data do, however, contain information about some covered loans involving properties in rural areas and these higher thresholds would thus result in decreased information on such lending activity.
                        </P>
                    </FTNT>
                    <P>
                        The Bureau is not proposing these higher thresholds because of concerns that the resulting reduction in HMDA's overall coverage of the mortgage market may affect the usefulness of the HMDA data. For example, a reduction in 
                        <PRTPAGE P="20979"/>
                        HMDA data may affect bank regulators' and the public's ability to use HMDA data to evaluate a depository institution's performance under the CRA. HMDA data are also used for identifying possible discriminatory lending patterns and potential violations of antidiscrimination statutes, such as the Equal Credit Opportunity Act and Fair Housing Act, including through redlining analyses, which aim to compare lenders and their peers. As noted in the 2015 HMDA Rule, data about local communities is essential to achieve HMDA's purposes.
                        <SU>58</SU>
                        <FTREF/>
                         Among other things, public officials, community advocates, and researchers use HMDA data to analyze access to credit at the neighborhood level and to target programs to assist underserved communities and consumers.
                        <SU>59</SU>
                        <FTREF/>
                         A reduction in HMDA's overall coverage of the mortgage market could thus reduce the usefulness of HMDA data for identifying opportunities for public and private investment, and for assessing whether lenders are meeting the housing needs of their communities.
                        <SU>60</SU>
                        <FTREF/>
                         Therefore, the Bureau believes that if the closed-end coverage threshold were increased from 25 loans to a level above 100 loans, the more notable decrease in the number of institutions required to report HMDA data and the loss of reportable HMDA data, particularly at the local level, available to serve HMDA's purposes may not be justified by the significant reduction in compliance costs for the depository institutions that would no longer be required to report HMDA data at such higher thresholds.
                    </P>
                    <FTNT>
                        <P>
                            <SU>58</SU>
                             80 FR 66128, 66147 (Oct. 28, 2015). The 2015 HMDA Rule explained that public officials, community advocates, and researchers rely on HMDA data to analyze access to credit at the neighborhood level and to target programs to assist underserved communities and consumers. It explained that, for example, local and state officials have used HMDA data to identify and target relief to localities impacted by high-cost lending or discrimination. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>59</SU>
                             
                            <E T="03">Id.</E>
                             at 66280.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>60</SU>
                             
                            <E T="03">Id.</E>
                             at 66276.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Request for Feedback</HD>
                    <P>
                        For the reasons discussed above, the Bureau proposes to increase the closed-end coverage threshold for depository institutions in § 1003.2(g)(1)(v)(A) from 25 to 50 in Alternative 1 or from 25 to 100 in Alternative 2, and to make conforming amendments to comments (2)(g)-1 and -5. The Bureau seeks comment on whether the data that would be reported at thresholds of 50 or 100 closed-end mortgage loans would achieve the purposes of HMDA.
                        <SU>61</SU>
                        <FTREF/>
                         The Bureau also seeks comment on whether the value of the data that would be reported by institutions that originate between 25 and 50 closed-end mortgage loans, or alternatively between 25 and 100 closed-end mortgage loans, is outweighed by the burden on those institutions of reporting HMDA data and undergoing examinations to validate the accuracy of their submissions. The Bureau seeks comment on these alternative proposals as well as any other closed-end coverage threshold, including any threshold significantly above 100, that would more appropriately balance the burden of reporting with the value of the data reported to achieving the purposes of HMDA. Specifically, the Bureau seeks comment on: (1) How the proposed increase to the closed-end coverage threshold to 50, 100, or another number would affect the number of depository institutions required to report data on closed-end mortgage loans; (2) the significance of the data that would not be available for achieving HMDA's purposes as a result of the proposed increase to the closed-end coverage threshold to 50, 100, or another number, including (a) whether, and under what circumstances, the proposed increase would prevent public officials and the public from understanding if depository institutions excluded by the proposed 50, 100, or another closed-end coverage threshold are serving the needs of their community, (b) whether, and under what circumstances, the proposed increase to the closed-end coverage threshold to 50, 100, or another number would negatively impact the ability of public officials to make determinations with respect to the distribution of public sector investments in a manner designed to improve the private investment environment, and (c) whether, and under what circumstances, the proposed 50, 100, or another number for the closed-end coverage threshold would exclude data that would be valuable for identifying possible fair lending violations or enforcing antidiscrimination laws; and (3) the reduction in burden that would result from the proposed increase for institutions that would not be required to report (addressing separately the burden reduction for depository institutions that are eligible for the EGRRCPA's partial exemption for closed-end mortgage loans and the burden reduction for depository institutions that are not).
                    </P>
                    <FTNT>
                        <P>
                            <SU>61</SU>
                             As originally adopted, HMDA identifies its purposes as providing the public and public officials with information to help determine whether financial institutions are serving the housing needs of the communities in which they are located, and assisting public officials in their determination of the distribution of public sector investments in a manner designed to improve the private investment environment. Following Congress's expansion of HMDA, the Board recognized a third purpose of identifying possible discriminatory lending patterns and enforcing antidiscrimination statutes.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2(g)(1)(v)(B)</HD>
                    <HD SOURCE="HD3">Background on Reporting Data Concerning Open-End Lines of Credit Under the 2015 HMDA Rule and the 2017 HMDA Rule</HD>
                    <P>
                        By its terms, the definition of “mortgage loan” in HMDA covers all loans secured by residential real property and home improvement loans whether open- or closed-end.
                        <SU>62</SU>
                        <FTREF/>
                         However, home-equity lines of credit were uncommon in the 1970s and early 1980s when Regulation C was first issued, and the Board's definition covered only closed-end loans. In 2000, in response to the increasing importance of open-end lending in the housing market, the Board proposed to revise Regulation C to require mandatory reporting of all home-equity lines of credit, which were optionally reported.
                        <SU>63</SU>
                        <FTREF/>
                         However, the Board's 2002 final rule left open-end reporting voluntary, as the Board determined that the benefits of mandatory reporting relative to other then proposed changes (such as collecting information about higher-priced loans) did not justify the increased burden.
                        <SU>64</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>62</SU>
                             HMDA section 303(2), 12 U.S.C. 2802(2).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>63</SU>
                             65 FR 78656, 78659-60 (Dec. 15, 2000). In 1988, the Board had amended Regulation C to permit, but not require, financial institutions to report certain home-equity lines of credit. 53 FR 31683, 31685 (Aug. 19, 1988).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>64</SU>
                             67 FR 7222, 7225 (Feb. 15, 2002).
                        </P>
                    </FTNT>
                    <P>
                        As discussed in the 2015 HMDA Rule, open-end mortgage lending continued to increase in the years following the Board's 2002 final rule, particularly in areas with high home-price appreciation.
                        <SU>65</SU>
                        <FTREF/>
                         In light of that development and the role that open-end lines of credit played in contributing to the financial crisis,
                        <SU>66</SU>
                        <FTREF/>
                         the Bureau decided in the 2015 HMDA Rule to require reporting of dwelling-secured, consumer purpose open-end lines of credit,
                        <SU>67</SU>
                        <FTREF/>
                         concluding that doing so was a 
                        <PRTPAGE P="20980"/>
                        reasonable interpretation of “mortgage loan” in HMDA and necessary and proper to effectuate the purposes of HMDA and prevent evasions thereof.
                        <SU>68</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>65</SU>
                             80 FR 66128, 66160 (Oct. 28, 2015).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>66</SU>
                             
                            <E T="03">Id.</E>
                             As the Bureau explained in the 2015 HMDA Rule, research indicated that some real estate investors used open-end, home-secured lines of credit to purchase non-owner occupied properties, which correlated with higher first-mortgage defaults and home-price depreciation during the financial crisis. 
                            <E T="03">Id.</E>
                             In the years leading up to the crisis, such home-equity lines of credit often were made and fully drawn more or less simultaneously with first-lien home purchase loans, essentially creating high loan-to-value home purchase transactions that were not visible in the HMDA dataset. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>67</SU>
                             The Bureau also required reporting of applications for, and originations of, dwelling-
                            <PRTPAGE/>
                            secured commercial-purpose lines of credit for home purchase, home improvement, or refinancing purposes. 
                            <E T="03">Id.</E>
                             at 66171.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>68</SU>
                             
                            <E T="03">Id.</E>
                             at 66157-62. HMDA and Regulation C are designed to provide citizens and public officials sufficient information about mortgage lending to ensure that financial institutions are serving the housing needs of their communities, to assist public officials in distributing public-sector investment so as to attract private investment to areas where it is needed, and to assist in identifying possible discriminatory lending patterns and enforcing antidiscrimination statutes. The Bureau believes that collecting information about all dwelling-secured, consumer-purpose open-end lines of credit serves these purposes.
                        </P>
                    </FTNT>
                    <P>
                        As noted in the 2015 HMDA Rule, in expanding coverage to include mandatory reporting of open-end lines of credit, the Bureau recognized that doing so would impose one-time and ongoing operational costs on reporting institutions; that the one-time costs of modifying processes and systems and training staff to begin open-end line of credit reporting likely would impose significant costs on some institutions; and that institutions' ongoing reporting costs would increase as a function of their open-end lending volume.
                        <SU>69</SU>
                        <FTREF/>
                         The Bureau sought to avoid imposing these costs on small institutions with limited open-end lending, where the benefits of reporting the data do not justify the costs of reporting.
                        <SU>70</SU>
                        <FTREF/>
                         In seeking to draw such a line, the Bureau acknowledged that it was handicapped by the lack of available data concerning open-end lending.
                        <SU>71</SU>
                        <FTREF/>
                         This created challenges both in estimating the distribution of open-end origination volume across financial institutions and in estimating the one-time and ongoing costs that institutions of various sizes would incur in reporting data on open-end lending.
                    </P>
                    <FTNT>
                        <P>
                            <SU>69</SU>
                             80 FR 66128, 66161 (Oct. 28, 2015).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>70</SU>
                             
                            <E T="03">Id.</E>
                             at 66149.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>71</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        To estimate the one-time and ongoing costs of reporting data under HMDA in the 2015 HMDA Rule, the Bureau identified seven “dimensions” of compliance operations and used those to define three broadly representative financial institutions according to the overall level of complexity of their compliance operations: “tier 1” (high-complexity); “tier 2” (moderate-complexity); and “tier 3” (low-complexity).
                        <SU>72</SU>
                        <FTREF/>
                         The Bureau then sought to estimate one-time and ongoing costs for a representative institution in each tier.
                        <SU>73</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>72</SU>
                             
                            <E T="03">Id.</E>
                             at 66261, 66269-70. In the 2015 HMDA Rule and the 2017 HMDA Rule, the Bureau assigned financial institutions to tiers by adopting cutoffs based on the estimated open-end line of credit volume. 
                            <E T="03">Id.</E>
                             at 66285; 82 FR 43088, 43128 (Sept. 13, 2017). Specifically, the Bureau assumed the lenders that originated fewer than 200 but more than 100 open-end lines of credit were tier 3 (low-complexity) open-end reporters; lenders that originate between 200 and 7,000 open-lines of credit were tier 2 (moderate-complexity) open-end reporters; and lenders that originated more than 7,000 open-end lines of credit were tier 1 (high-complexity) open-end reporters. 80 FR 66128, 66285 (Oct. 28, 2015); 82 FR 43088, 43128 (Sept. 13, 2017). As explained below in part VI.D.1, for purposes of this proposal, the Bureau has used a more precise methodology to assign eligible financial institutions to tiers 2 and 3 for their open-end reporting, which relies on constraints relating to the estimated numbers of impacted institutions and loan/application register records for the applicable provision.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>73</SU>
                             80 FR 66128, 66264-65 (Oct. 28, 2015); 
                            <E T="03">see also id.</E>
                             at 66284.
                        </P>
                    </FTNT>
                    <P>
                        The Bureau recognized in the 2015 HMDA Rule that the one-time cost of reporting open-end lines of credit could be substantial because most financial institutions had not reported open-end lines of credit and thus would have to develop completely new systems to begin reporting these data. As a result, there would be one-time costs to create processes and systems for open-end lines of credit.
                        <SU>74</SU>
                        <FTREF/>
                         However, for tier 3, low-complexity institutions, the Bureau believed that the additional one-time costs of open-end reporting would be relatively low. Because these institutions are less reliant on information technology systems for HMDA reporting and they may process open-end lines of credit on the same system and in the same business unit as closed-end mortgage loans, their one-time costs would be derived mostly from new training and procedures adopted for the overall changes in the final rule, not distinct from costs related to changes in reporting of closed-end mortgage loans.
                        <SU>75</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>74</SU>
                             
                            <E T="03">Id.</E>
                             at 66264; 
                            <E T="03">see also id.</E>
                             at 66284-85.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>75</SU>
                             
                            <E T="03">Id.</E>
                             at 66265; 
                            <E T="03">see also id.</E>
                             at 66284.
                        </P>
                    </FTNT>
                    <P>
                        The Bureau acknowledged in the 2015 HMDA Rule that ongoing costs for open-end reporting vary by institutions due to many factors, such as size, operational structure, and product complexity, and that this variance exists on a continuum that was impossible to capture fully.
                        <SU>76</SU>
                        <FTREF/>
                         At the same time, the Bureau stated it believed that the HMDA reporting process and ongoing operational cost structure for open-end reporting would be fundamentally similar to closed-end reporting.
                        <SU>77</SU>
                        <FTREF/>
                         Thus, using the ongoing cost estimates developed for closed-end reporting, the Bureau estimated that for a representative tier 1 institution the ongoing operational costs would be $273,000 per year; for a representative tier 2 institution $43,400 per year; and for a representative tier 3 institution $8,600 per year.
                        <SU>78</SU>
                        <FTREF/>
                         These translated into costs per HMDA record of approximately $9, $43, and $57 respectively.
                        <SU>79</SU>
                        <FTREF/>
                         The Bureau acknowledged that, precisely because no good source of publicly available data exists concerning open-end lines of credit, it was difficult to predict the accuracy of the Bureau's cost estimates but also stated its belief that these estimates were reasonably reliable.
                        <SU>80</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>76</SU>
                             
                            <E T="03">Id.</E>
                             at 66285.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>77</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>78</SU>
                             
                            <E T="03">Id.</E>
                             at 66264, 66286.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>79</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>80</SU>
                             
                            <E T="03">Id.</E>
                             at 66162.
                        </P>
                    </FTNT>
                    <P>
                        Drawing on all of these estimates, the Bureau decided in the 2015 HMDA Rule to establish an open-end coverage threshold that would require institutions that originate 100 or more open-end lines of credit in each of the two preceding calendar years to report data on such lines of credit. The Bureau estimated that this threshold would avoid imposing the burden of establishing mandatory open-end reporting on approximately 3,000 predominantly smaller-sized institutions with low-volume open-end lending 
                        <SU>81</SU>
                        <FTREF/>
                         and would require reporting by 749 financial institutions, all but 24 of which would also report data on their closed-end mortgage lending.
                        <SU>82</SU>
                        <FTREF/>
                         The Bureau explained that it believed this threshold appropriately balanced the benefits and burdens of covering institutions based on their open-end mortgage lending.
                        <SU>83</SU>
                        <FTREF/>
                         However, as discussed in the 2017 HMDA Rule, the Bureau lacked robust data for the estimates that it used to establish the open-end threshold in the 2015 HMDA Rule.
                        <SU>84</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>81</SU>
                             
                            <E T="03">Id.</E>
                             The estimate of the number of institutions that would be excluded from reporting open-end lines of credit by the transactional coverage threshold was relative to the number that would have been covered under the Bureau's proposal that led to the 2015 HMDA Rule. Under that proposal, a financial institution would have been required to report its open-end lines of credit if it had originated at least 25 closed-end mortgage loans in each of the preceding two years without regard to how many open-end lines of credit the institution originated. 
                            <E T="03">See</E>
                             Home Mortgage Disclosure (Regulation C), 79 FR 51732 (Aug. 29, 2014).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>82</SU>
                             80 FR 66128, 66281 (Oct. 28, 2015).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>83</SU>
                             
                            <E T="03">Id.</E>
                             at 66162.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>84</SU>
                             82 FR 43088, 43094 (Sept. 13, 2017).
                        </P>
                    </FTNT>
                    <P>
                        The 2017 HMDA Rule explained that, between 2013 and 2017, the number of dwelling-secured open-end lines of credit financial institutions originated had increased by 36 percent.
                        <SU>85</SU>
                        <FTREF/>
                         The Bureau noted that, to the extent institutions that had been originating fewer than 100 open-end lines of credit shared in that growth, the number of institutions at the margin that would be required to report under an open-end threshold of 100 lines of credit would 
                        <PRTPAGE P="20981"/>
                        also increase.
                        <SU>86</SU>
                        <FTREF/>
                         Additionally, in the 2017 HMDA Rule, the Bureau explained that information received by the Bureau since issuing the 2015 HMDA Rule had caused the Bureau to question its assumption that certain low-complexity institutions 
                        <SU>87</SU>
                        <FTREF/>
                         process home-equity lines of credit on the same data platforms as closed-end mortgages, on which the Bureau based its assumption that the one-time costs for these institutions would be minimal.
                        <SU>88</SU>
                        <FTREF/>
                         After issuing the 2015 HMDA Rule, the Bureau had heard anecdotes suggesting that one-time costs to begin reporting open-end lines of credit could be as high as $100,000 for such institutions.
                        <SU>89</SU>
                        <FTREF/>
                         The Bureau likewise had heard anecdotes suggesting that the ongoing costs for these institutions to report open-end lines of credit, which the Bureau estimated would be under $10,000 per year and add under $60 per line of credit, could be at least three times higher than the Bureau had estimated.
                        <SU>90</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>85</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>86</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>87</SU>
                             
                            <E T="03">See supra</E>
                             notes 72-75 and accompanying text.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>88</SU>
                             82 FR 43088, 43094 (Sept. 13, 2017).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>89</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>90</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Based on this information regarding one-time and ongoing costs and new data indicating that more institutions would have reporting responsibilities under the 100-loan open-end threshold than estimated in the 2015 HMDA Rule, the Bureau proposed in 2017 to increase temporarily the open-end threshold to 500 for two years, until January 1, 2020.
                        <SU>91</SU>
                        <FTREF/>
                         This temporary increase was intended to allow for additional data collection and assessment as to what threshold would best balance the benefits and burdens of covering institutions based on their open-end mortgage lending. The Bureau finalized the proposal after notice and comment in the 2017 HMDA Rule.
                        <SU>92</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>91</SU>
                             82 FR 33455 (July 20, 2017).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>92</SU>
                             82 FR 43088 (Sept. 13, 2017). Comments received on the July 2017 HMDA Proposal to change temporarily the open-end threshold are discussed in the 2017 HMDA Rule. 
                            <E T="03">Id.</E>
                             at 43094-95.
                        </P>
                    </FTNT>
                    <P>Since the Bureau issued the 2017 HMDA Rule, various trade associations and smaller financial institutions have urged the Bureau to increase permanently the open-end line of credit coverage threshold in order to reduce the burden on smaller institutions. For example, some Federal credit unions suggested in response to the Bureau's March 2018 RFI on Adopted Regulations that the Bureau consider increasing both the open- and closed-end thresholds that trigger the applicability of HMDA requirements to credit unions.</P>
                    <HD SOURCE="HD3">Open-End Line of Credit Threshold for Institutional Coverage of Depository Institutions</HD>
                    <P>
                        As explained above, the 2015 HMDA Rule established an institutional coverage threshold in § 1003.2(g) for open-end lines of credit of at least 100 open-end lines of credit in each of the two preceding calendar years.
                        <SU>93</SU>
                        <FTREF/>
                         In the 2017 HMDA Rule, the Bureau amended § 1003.2(g)(1)(v)(B) and comments 2(g)-3 and -5, effective January 1, 2018, to increase temporarily the open-end threshold from 100 to 500 and, effective January 1, 2020, to restore a permanent threshold of 100.
                        <SU>94</SU>
                        <FTREF/>
                         For the reasons discussed below, the Bureau now proposes to amend § 1003.2(g)(1)(v)(B) and comments 2(g)-3 and -5, effective January 1, 2020, to extend until January 1, 2022, the temporary open-end institutional coverage threshold for depository institutions of 500 open-end lines of credit. When this temporary threshold expires, the Bureau is proposing to set a permanent threshold at 200 open-end lines of credit. The Bureau is also proposing conforming changes to the institutional coverage threshold for nondepository institutions in § 1003.2(g)(2)(ii)(B) and to the transactional coverage threshold in § 1003.3(c)(12), as discussed below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>93</SU>
                             The 2015 HMDA Rule established complementary thresholds that determine whether a financial institution is required to report data on closed-end mortgage loans or open-end lines of credit, respectively. 80 FR 66128, 66146, 66149, 66162 (Oct. 28, 2015). The 2017 HMDA Rule corrected a drafting error to ensure the institutional coverage threshold and the transactional coverage threshold were complementary. 82 FR 43088, 43100, 43102 (Sept. 13, 2017). These institutional and transactional coverage thresholds are distinct from the thresholds for the EGRRCPA partial exemptions in proposed § 1003.3(d)(2) and (3).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>94</SU>
                             82 FR 43088, 43094 (Sept. 13, 2017). In the 2015 HMDA Rule and 2017 HMDA Rule, the Bureau declined to retain optional reporting of open-end lines of credit, after concluding that improved visibility into this segment of the mortgage market is critical because of the risks posed by these products to consumers and local markets and the lack of other publicly available data about these products. 
                            <E T="03">Id.</E>
                             at 43095; 80 FR 66128, 66160-61 (Oct. 28, 2015). However, Regulation C as amended by the 2017 HMDA Rule permits voluntary reporting by financial institutions that do not meet the open-end threshold. 12 CFR 1003.3(c)(12).
                        </P>
                    </FTNT>
                    <P>
                        Several developments since the Bureau issued the 2015 HMDA Rule have affected the Bureau's analyses of the costs and benefits associated with the open-end line of credit coverage threshold. As the 2017 HMDA Rule explained, the Bureau is concerned that, in establishing a 100-loan threshold for open-end lines of credit in the 2015 HMDA Rule, it may have underestimated the number of institutions that would be covered and the reporting burden on smaller covered institutions. In the 2017 HMDA Rule, the Bureau noted that there had been a 36 percent increase in the number of dwelling-secured open-end lines of credit originated between 2013 (the most recent data cited by the Bureau for its analysis of the 2015 HMDA Rule) and 2016.
                        <SU>95</SU>
                        <FTREF/>
                         The number of dwelling-secured open-end line of credit originations in 2018 was again approximately 36 percent higher than the number of such originations in 2013.
                        <SU>96</SU>
                        <FTREF/>
                         Table 4 in the Bureau's analysis under Dodd-Frank Act section 1022(b) in part VI.E.4 below provides the Bureau's updated coverage estimates for reporting thresholds of 100, 200, and 500 open-end lines of credit.
                        <SU>97</SU>
                        <FTREF/>
                         As explained in more detail in part VI.E.4, the Bureau's updated coverage estimates indicate that the total number of institutions exceeding the open-end coverage threshold of 100 open-end lines of credit in 2018 would be approximately 1,014, which is significantly higher than the estimate of 749 in the 2015 HMDA Rule that was based on 2013 data.
                        <SU>98</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>95</SU>
                             82 FR 43088, 43094 (Sept. 13, 2017) (citing July 2017 HMDA Proposal, 82 FR 33455, 33459 (July 20, 2017)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>96</SU>
                             Experian-Oliver Wyman Market Intelligence Reports show that in 2013 there were 1.14 million home-equity lines of credit originated. Experian &amp; Oliver Wyman, 2015 Q1 Experian-Oliver Wyman Market Intelligence Report: Home Equity Lines Report, at 6 fig. 1 (2015). In 2018 that number grew to 1.555 million. Experian &amp; Oliver Wyman, 2018 Q4 Experian-Oliver Wyman Market Intelligence Report: Home Equity Lines Report, at 6 fig. 1 (2019).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>97</SU>
                             As discussed further in the analysis under Dodd-Frank Act section 1022(b) in part VI, in note 172 below, the Bureau's analyses in this proposal are based on HMDA data collected in 2016 and 2017 and other sources. The Bureau intends to review the 2018 HMDA data more closely in connection with this rulemaking once the 2018 submissions are more complete.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>98</SU>
                             82 FR 43088, 43094 (Sept. 13, 2017).
                        </P>
                    </FTNT>
                    <P>
                        As explained in more detail in part VI below, the estimates the Bureau used in the 2015 HMDA Rule may understate the burden that open-end reporting would impose on smaller institutions if they were required to begin reporting on January 1, 2020. For example, in developing the one-time cost estimates for open-end lines of credit in the 2015 HMDA Rule, the Bureau had envisioned that there would be cost sharing between the line of business that conducts open-end lending and the line of business that conducts closed-end lending at the corporate level, as the implementation of open-end reporting that became mandatory under the 2015 HMDA Rule would coincide with the implementation of the changes to closed-end reporting under the 2015 HMDA Rule. However, this type of cost 
                        <PRTPAGE P="20982"/>
                        sharing is less likely now since financial institutions have already implemented almost all of the closed-end reporting changes required under the 2015 HMDA Rule.
                    </P>
                    <P>
                        Another development since the Bureau finalized the 2015 HMDA Rule is the enactment of the EGRRCPA, which created partial exemptions from HMDA's requirements that certain insured depository institutions and insured credit unions may now use.
                        <SU>99</SU>
                        <FTREF/>
                         The partial exemption for open-end lines of credit under the EGRRCPA relieves certain insured depository institutions and insured credit unions that originated fewer than 500 open-end mortgage loans in each of the two preceding calendar years of the obligation to report many of the data points generally required by Regulation C.
                        <SU>100</SU>
                        <FTREF/>
                         The partial exemptions are available to the vast majority of the financial institutions that would be excluded by the proposed increases in the open-end coverage threshold.
                        <SU>101</SU>
                        <FTREF/>
                         The EGRRCPA has thus changed the costs and benefits associated with different possible coverage thresholds, as discussed in more detail below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>99</SU>
                             Public Law 115-174, 132 Stat. 1296 (2018).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>100</SU>
                             See the section-by-section analysis of § 1003.3(d) in part IV above.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>101</SU>
                             
                            <E T="03">See infra</E>
                             part VI.E.4.
                        </P>
                    </FTNT>
                    <P>
                        The Bureau has considered the appropriate open-end threshold in light of these developments and believes that the proposed changes to the open-end threshold would reduce one-time and ongoing costs and provide other benefits, while still providing significant market coverage. These considerations are discussed in turn below, and additional explanation of the Bureau's cost estimates is provided in the Bureau's analysis under Dodd-Frank Act section 1022(b) in part VI.E.4 below.
                        <SU>102</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>102</SU>
                             As explained in part VI below, the Bureau derived these estimates using estimates of savings for open-end lines of credit for representative financial institutions.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">One-time cost reduction from proposed threshold of 200.</E>
                         The Bureau's proposed increase of the open-end coverage threshold to 200 open-end lines of credit after the proposed temporary extension expires in 2022 would avoid imposing one-time costs of reporting open-end lines of credit on institutions originating between 100 and 199 open-end lines of credit. The Bureau estimates that setting the coverage threshold at 200 rather than 100 would exclude 401 institutions from reporting open-end lines of credit starting in 2022. According to the Bureau's estimates, about 391 of those 401 financial institutions are low-complexity tier 3 open-end reporters, about 10 are moderate-complexity tier 2 open-end reporters, and none are high-complexity tier 1 reporters.
                        <SU>103</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>103</SU>
                             For an explanation of the Bureau's assumptions in assigning institutions to tiers 1, 2, and 3, see 
                            <E T="03">supra</E>
                             note 72 and 
                            <E T="03">infra</E>
                             part VI.D.1.
                        </P>
                    </FTNT>
                    <P>The Bureau recognizes that many financial institutions, especially larger and more complex institutions, process applications for open-end lines of credit in their consumer lending departments using procedures, policies, and data systems that are separate from those used for closed-end loans. Some institutions that would have to report with a threshold of 100 after the proposed extension of the temporary threshold of 500 expires in 2022 do not currently report open-end lines of credit. These institutions might have to develop completely new reporting infrastructures to comply with mandatory reporting if the threshold of 100 lines of credit were to take effect. As a result, these institutions would incur one-time costs to create processes and systems for open-end lines of credit in addition to the one-time costs to modify processes and systems used for other mortgage products. As explained in part VI below, the Bureau estimates that increasing the open-end coverage threshold from 100 to 200 starting in 2022 would result in an aggregate savings of about $3.8 million in avoided one-time costs associated with open-end lines of credit.</P>
                    <P>
                        <E T="03">Ongoing cost reduction from proposed threshold of 200.</E>
                         The proposed increase of the open-end coverage threshold from 100 to 200 starting in 2022 would permanently relieve institutions that originate between 100 and 199 open-end lines of credit of the ongoing costs associated with reporting open-end lines of credit that they might otherwise incur if the 2017 HMDA Rule's permanent threshold of 100 were to take effect. The Bureau estimates that the proposed increase in the permanent threshold would result in aggregate savings on the operational costs associated with open-end lines of credit of about $2.1 million per year starting in 2022.
                    </P>
                    <P>
                        <E T="03">Benefits of two-year extension.</E>
                         The proposed two-year extension of the temporary coverage threshold of 500 open-end lines of credit would ensure that any institutions that would be required to report under the proposed threshold of 200 open-end lines of credit but that are not required to report under the current temporary threshold of 500 would have time to adapt their systems and prepare for compliance. The Bureau estimates that there are 280 institutions that fall within this category. Industry stakeholders provided feedback in connection with the 2015 HMDA Rule and the 2017 HMDA Rule indicating that they strongly prefer a long implementation period when coverage changes result in new institutions having open-end reporting obligations under HMDA. The Bureau believes that the two-year extension of the temporary threshold of 500 lines of credit would provide any newly covered institutions with sufficient time to revise and update policies and procedures, implement any necessary systems changes, and train staff before the proposed threshold of 200 lines of credit would take effect in 2022.
                    </P>
                    <P>The proposed extension of the temporary coverage threshold would also provide the Bureau with additional time to assess how a requirement to report open-end lines of credit would affect institutions whose origination volume falls just above the proposed threshold of 200 open-end lines of credit. The Bureau is reviewing HMDA data on open-end lines of credit submitted in 2019 by financial institutions that originated 500 or more open-end lines of credit in 2016 and 2017 and invites comment on financial institutions' experiences with collecting and reporting these open-end data. The Bureau will also continue to monitor HMDA data in the future. A two-year temporary extension of the current coverage threshold would ensure the Bureau has time to consider further the open-end data submitted for 2018 and 2019 and any additional information stakeholders provide before any permanent threshold established through this rulemaking takes effect.</P>
                    <P>The proposed extension of the temporary coverage threshold would also relieve institutions that originate between 100 and 499 open-end lines of credit of ongoing costs associated with reporting open-end lines of credit over the next two years. In total, the Bureau estimates that extending the temporary open-end coverage threshold for two years would reduce operational costs for institutions by about $5.6 million per year in the years 2020 and 2021.</P>
                    <P>
                        <E T="03">Effect on market coverage.</E>
                         While the proposed permanent and temporary threshold increases would reduce market coverage, information about a sizeable portion of the market would still be available in the next two years under the proposed temporary threshold of 500 and thereafter under the proposed threshold of 200. The Bureau has used multiple data sources, including credit union Call Reports, Call Reports for banks and thrifts, HMDA 
                        <PRTPAGE P="20983"/>
                        data, and Consumer Credit Panel data, in order to develop updated estimates for this proposal about open-end originations for institutions that are active in the market and to assess the impact of various thresholds on the numbers of institutions which report and the number of loans about which they report under various scenarios.
                        <SU>104</SU>
                        <FTREF/>
                         Based on this information, the Bureau estimates that, as of 2018, approximately 613 financial institutions originated at least 200 open-end lines of credit in both of the two preceding years, as compared to approximately 333 financial institutions that originated at least 500 open-end lines of credit in both of the two preceding years, and about 1,014 financial institutions that originated at least 100 open-end lines of credit in both of the two preceding years.
                        <SU>105</SU>
                        <FTREF/>
                         Under the temporary 500-loan open-end threshold, the Bureau estimates about 1.23 million lines of credit or approximately 78 percent of origination volume would reported by about 5 percent of all institutions in the open-end line of credit market.
                        <SU>106</SU>
                        <FTREF/>
                         Under a permanent 200-loan open-end threshold, the Bureau estimates about 1.34 million lines of credit or approximately 84 percent of origination volume would be reported by approximately 9 percent of all institutions in the open-end line of credit market.
                        <SU>107</SU>
                        <FTREF/>
                         As compared to a 100-loan threshold, the 200-loan threshold would reduce the number of institutions reporting by approximately 40 percent (from 1,014 to 613), while reducing coverage of originations by approximately 5 percentage points from approximately 89 percent to 84 percent.
                    </P>
                    <FTNT>
                        <P>
                            <SU>104</SU>
                             Because collection of data on open-end lines of credit only became mandatory starting in 2018 under the 2015 HMDA Rule and 2017 HMDA Rule, no single data source exists as of the time of this proposal that can accurately capture the number of originations of open-end lines of credit in the entire market and by lenders. For information about the HMDA data used in updating the Bureau estimates, see 
                            <E T="03">infra</E>
                             note 172.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>105</SU>
                             
                            <E T="03">See infra</E>
                             part VI.E.4 at Table 4 for estimates of coverage among all lenders that are active in the open-end line of credit market at various open-end coverage thresholds.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>106</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>107</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>Extending the temporary threshold of 500 open-end lines of credit for two years and raising the open-end threshold from 100 to 200 after the temporary threshold expires in 2022 would decrease visibility into the open-end line of credit market relative to the visibility that would be obtained if the Bureau were to allow the 100-loan threshold to take effect on January 1, 2020. However, the effect of these threshold increases would be limited, because the EGRRCPA now provides a partial exemption that exempts almost all of the institutions that the proposed increases would affect from any obligation to report many of the data points generally required by Regulation C for their open-end lines of credit. In light of the EGRRCPA's partial exemption from reporting certain data for open-end lines of credit for certain insured depository institutions and insured credit unions, increasing the open-end line of credit coverage threshold to 500 temporarily and to 200 permanently would result in a much smaller loss of data than the Bureau anticipated when it adopted a permanent threshold of 100 open-end lines of credit in the 2015 HMDA Rule or when it revisited the open-end line of credit coverage threshold in the 2017 HMDA Rule. The Bureau believes that the limited decrease in visibility occasioned by the proposed adjustments to the open-end threshold would appear to be justified by the benefits discussed above of reducing the burden on smaller institutions. This burden reduction is greater than the Bureau anticipated in the 2015 HMDA Rule, because the number of institutions affected and the costs per institution associated with reporting are higher than anticipated, as explained above and in part VI below. The Bureau now proposes to set the open-end line of credit coverage threshold at 200 after a two-year extension of the temporary increase. Using a threshold of 200 as compared to 100 loans would better balance the benefits and burdens of covering institutions based on their open-end mortgage lending. As noted above, the Bureau is particularly interested in comments on how a requirement to report open-end lines of credit would affect institutions whose origination volume falls just above the proposed threshold of 200 open-end lines of credit.</P>
                    <P>For the reasons discussed above, the Bureau proposes to amend § 1003.2(g)(1)(v)(B) and comments 2(g)-3 and -5, to set the open-end institutional coverage threshold for depository institutions at 500, effective January 1, 2020, and at 200, effective January 1, 2022. The Bureau seeks comment on whether it should extend the temporary institutional coverage threshold of 500 open-end lines of credit as proposed and, if so, for how long. The Bureau also seeks comment on whether to increase permanently the open-end institutional coverage threshold when the proposed temporary extension expires and, if so, whether a threshold of 200 or another threshold would most appropriately balance the benefits and burdens of covering institutions based on their open-end lending beginning in 2022. The Bureau also seeks comment specifically on: (1) How the proposed temporary and permanent increases would affect the number of financial institutions required to report data on open-end lines of credit; (2) the significance of the data that would not be available as a result of the proposed temporary and permanent increases (including (a) whether, and under what circumstances, the proposed temporary and permanent increases would prevent public officials and the public from understanding if financial institutions excluded by the proposed temporary and permanent increases are serving the needs of their community, (b) whether, and under what circumstances, the proposed temporary and permanent increases would negatively impact the ability of public officials to make determinations with respect to the distribution of public sector investments in a manner designed to improve the private investment environment, and (c) whether, and under what circumstances, the proposed temporary and permanent increases would exclude data that would be valuable for identifying possible fair lending violations or enforcing antidiscrimination laws); and (3) the reduction in burden that would result from the proposed temporary and permanent increases for institutions that would not be required to report their open-end lines of credit (addressing separately the burden reduction for institutions that are eligible for the EGRRCPA's partial exemption for open-end lines of credit and for institutions that are not).</P>
                    <HD SOURCE="HD3">2(g)(2) Nondepository Financial Institution</HD>
                    <HD SOURCE="HD3">2(g)(2)(ii)(A)</HD>
                    <HD SOURCE="HD3">Closed-End Mortgage Loan Threshold for Institutional Coverage of Nondepository Institutions</HD>
                    <P>
                        HMDA extends reporting responsibilities to certain nondepository institutions, defined as any person engaged for profit in the business of mortgage lending other than a bank, savings association, or credit union.
                        <SU>108</SU>
                        <FTREF/>
                         HMDA section 309(a) authorizes the Bureau to adopt an exemption for covered nondepository institutions that are comparable within their respective industries to banks, savings associations, and credit unions with $10 
                        <PRTPAGE P="20984"/>
                        million or less in assets in the previous fiscal year.
                        <SU>109</SU>
                        <FTREF/>
                         Regulation C implements HMDA's coverage criteria for nondepository institutions in § 1003.2(g)(2). The Bureau revised the coverage criteria for nondepository institutions in the 2015 HMDA Rule by requiring such institutions to report HMDA data if they met the statutory location test and exceeded either the closed-end or open-end line of credit coverage thresholds.
                        <SU>110</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>108</SU>
                             HMDA section 303(5) (defining “other lending institutions”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>109</SU>
                             HMDA section 309(a), 12 U.S.C. 2808(a).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>110</SU>
                             Prior to the 2015 HMDA Rule, for-profit nondepository institutions that met the location test only had to report if: (1) In the preceding calendar year, the institution originated home purchase loans, including refinancings of home purchase loans, that equaled either at least 10 percent of its loan-origination volume, measured in dollars, or at least $25 million; and (2) On the preceding December 31, the institution had total assets of more than $10 million, counting the assets of any parent corporation; or in the preceding calendar year, the institution originated at least 100 home purchase loans, including refinancings of home purchase loans. 12 CFR 1003.2 (2017).
                        </P>
                    </FTNT>
                    <P>
                        HMDA sections 303(3)(B) and 303(5) require persons other than banks, savings associations, and credit unions that are “engaged for profit in the business of mortgage lending” to report HMDA data. As the Bureau stated in the 2015 HMDA Rule, the Bureau interpreted these provisions, as the Board also did, to evince the intent to exclude from coverage institutions that make a relatively small volume of mortgage loans.
                        <SU>111</SU>
                        <FTREF/>
                         In the 2015 HMDA Rule, the Bureau interpreted “engaged for profit in the business of mortgage lending” to include nondepository institutions that originated at least 25 closed-end mortgage loans or 100 open-end lines of credit in each of the two preceding calendar years. Due to the questions raised about potential risks posed to applicants and borrowers by nondepository institutions and the lack of other publicly available data sources about nondepository institutions, the Bureau believed that requiring additional nondepository institutions to report HMDA data would better effectuate HMDA's purposes. The Bureau estimated in 2015 that these changes could result in HMDA coverage for up to an additional 450 nondepository institutions. The Bureau stated in the 2015 HMDA Rule its belief that it was important to increase visibility into the lending practices of nondepository institutions because of their history of making riskier loans than depository institutions, including their role in the financial crisis and lack of available data about the mortgage lending practices of lower-volume nondepository institutions. The Bureau also stated that expanded coverage of nondepository institutions would ensure more equal visibility into the practices of nondepository institutions and depository institutions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>111</SU>
                             80 FR 66128, 66153 (Oct. 28, 2015) (citing 54 FR 51356, 51358-59 (Dec. 15, 1989)).
                        </P>
                    </FTNT>
                    <P>
                        Since issuing the 2015 Final Rule and 2017 HMDA Rule, the Bureau has heard concerns that lower-volume institutions continue to experience significant burden at a 25 closed-end coverage threshold.
                        <SU>112</SU>
                        <FTREF/>
                         Various industry stakeholders have advocated for an increase to the closed-end coverage threshold in order to reduce burden on additional lower-volume financial institutions. In light of the concerns raised by industry stakeholders, the Bureau is considering whether a higher closed-end coverage threshold would more appropriately cover nondepository institutions that are “engaged for profit in the business of mortgage lending” and maintain sufficient visibility into the lending practices of such institutions. The Bureau believes that increasing the closed-end coverage threshold may provide meaningful burden relief for lower-volume nondepository institutions without reducing substantially the data reported under HMDA, and more appropriately exclude lower-volume mortgage lenders. Therefore, the Bureau seeks comment on whether an increase to this threshold would more appropriately balance the benefits and burdens of covering lower-volume nondepository institutions based on their closed-end lending.
                    </P>
                    <FTNT>
                        <P>
                            <SU>112</SU>
                             The Bureau temporarily raised the threshold for open-end lines of credit in the 2017 HMDA Rule because of concerns that the Bureau may have underestimated in the 2015 HMDA Rule the number of institutions that would be required to report open-end lines of credit under the threshold adopted and that it also may have underestimated the cost of reporting. However, the Bureau declined to raise the threshold for closed-end mortgage loans and stated that in developing the 2015 HMDA Rule, it had robust data to make a determination about the number of transactions that would be reported at the 25 closed-end coverage threshold as well as the one-time and ongoing costs to industry. 82 FR 43088, 43095-96 (Sept. 13, 2017).
                        </P>
                    </FTNT>
                    <P>
                        As discussed below, the Bureau is proposing two alternatives to the closed-end mortgage loan coverage threshold. These proposals would maintain a uniform closed-end coverage threshold for depository and nondepository institutions.
                        <SU>113</SU>
                        <FTREF/>
                         Alternative 1 proposes to set the closed-end coverage threshold at 50 while Alternative 2 proposes to set the closed-end coverage threshold at 100. The Bureau reviewed multiple data sources, including recent HMDA data 
                        <SU>114</SU>
                        <FTREF/>
                         and Call Reports and developed estimates for each proposal as described below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>113</SU>
                             For a discussion on the proposed closed-end coverage threshold for depository institutions, see the section-by-section analysis of § 1003.2(g)(1)(v)(A) above.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>114</SU>
                             For further discussion of the recent HMDA data used, see 
                            <E T="03">infra</E>
                             note 155.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Alternative 1: Threshold Set at 50</HD>
                    <P>The Bureau estimates that if the closed-end coverage threshold were increased from 25 to 50 loans, approximately 683 out of about 697 nondepository institutions covered under the current rule (or approximately 98 percent) would continue to be required to report HMDA data on closed-end mortgage loans. Approximately 14 nondepository institutions covered under the current rule (or approximately 2 percent) would be relieved of their HMDA reporting responsibilities on closed-end mortgage loans. Further, the Bureau estimates that with this proposed increase to the closed-end coverage threshold, over 99 percent of total originations of closed-end mortgage loans reported by nondepository institutions under the current coverage criteria, or approximately 3.44 million closed-end mortgage loan originations under the current market conditions, would continue to be reported. The loss of data from these approximately 14 nondepository institutions would amount to an estimated 1,000 closed-end mortgage loan originations or less than one-half of 1 percent of closed-end mortgage loan originations reportable under the current market conditions.</P>
                    <P>
                        At the census tract level the Bureau estimates that, as noted above in the section-by section analysis of § 1003.2(g)(1)(v)(A), increasing the closed-end coverage threshold from 25 to the proposed 50 loans for both depository and nondepository institutions would result in a loss of at least 20 percent of reportable HMDA data in just under 300 out of approximately 74,000 total census tracts, or less than one-half of 1 percent of the total number of census tracts.
                        <SU>115</SU>
                        <FTREF/>
                         With respect to low-to-moderate income census tracts, the Bureau estimates if the closed-end threshold were increased from 25 to 50 loans, there would be at least a 20 percent loss of reportable HMDA data in less than 1 percent of such tracts. In addition, the Bureau examined the effects of an increase in the closed-end threshold from 25 to 50 loans and estimates that such a change would result in at least a 20 percent loss 
                        <PRTPAGE P="20985"/>
                        of reportable HMDA data in less than one-half of 1 percent of such tracts.
                    </P>
                    <FTNT>
                        <P>
                            <SU>115</SU>
                             The estimates of the effect on reportable HMDA data at the census tract level comprise both depository institutions and nondepository institutions. The Bureau estimates that at least 80 percent of reportable HMDA data would be retained in over 73,500 tracts. In certain tracts, substantially more than 80 percent of reportable HMDA data would be retained.
                        </P>
                    </FTNT>
                    <P>Therefore, the Bureau believes that it is reasonable to interpret “engaged for profit in the business of mortgage lending” to include nondepository institutions that originated at least 50 closed-end mortgage loans in each of the two preceding calendar years. The Bureau believes that the proposed increase to the closed-end coverage threshold for nondepository institutions would effectuate the purposes of HMDA by ensuring significant coverage of nondepository mortgage lending, while facilitating compliance with HMDA by reducing burden on smaller institutions and excluding nondepository institutions that are not engaged for profit in the business of mortgage lending. The Bureau believes that the reasons provided for the proposed changes to the closed-end coverage threshold for depository institutions in the section-by-section analysis of § 1003.2(g)(1)(v)(A) above apply to the threshold for nondepository institutions as well. Additionally, the proposed increase to the closed-end coverage threshold would promote consistency by subjecting nondepository institutions to the same threshold that applies to depository institutions.</P>
                    <HD SOURCE="HD3">Alternative 2: Threshold Set at 100</HD>
                    <P>The Bureau estimates that if the closed-end mortgage loan threshold were increased from 25 to 100, approximately 661 out of about 697 nondepository institutions covered under the current rule (or approximately 95 percent) would continue to be required to report HMDA data on closed-end mortgage loans. Approximately 36 nondepository institutions covered under the current rule (or approximately 5 percent) would be relieved of their HMDA reporting responsibilities on closed-end mortgage loans. In terms of the effect on the total number of originations, the Bureau estimates that with an increase in the closed-end mortgage threshold from 25 to the proposed 100 loans, over 99 percent of total originations of closed-end mortgage loans reported by nondepository institutions under the current Regulation C coverage criteria, or approximately 3.44 million closed-end mortgage loan originations under the current market conditions, would continue to be reported. The loss of data from these approximately 36 nondepository institutions would amount to about 3,000 closed-end mortgage originations under the current market conditions, or less than 1 percent of closed-end mortgage loan originations reportable under the current market conditions.</P>
                    <P>
                        With respect to the potential effect on available data at the census tract level and as noted above in the section-by section analysis of § 1003.2(g)(1)(v)(A), the Bureau estimates that if the closed-end coverage threshold were increased from 25 to the proposed 100, there would be a loss of at least 20 percent of reportable HMDA data in about 1,100 out of approximately 74,000 total census tracts, or 1.5 percent of the total number of census tracts.
                        <SU>116</SU>
                        <FTREF/>
                         For low-to-moderate income census tracts, the Bureau estimates that if the closed-end threshold were increased from 25 to 100 loans, there would be a loss of at least 20 percent of reportable HMDA data in approximately 3 percent of such tracts. In addition, the Bureau examined the effects on rural census tracts and estimates that relative to the current threshold, there would be at least a 20 percent loss of reportable HMDA data in less than 3 percent of such tracts.
                    </P>
                    <FTNT>
                        <P>
                            <SU>116</SU>
                             The Bureau estimates that at least 80 percent of reportable HMDA data would be retained in approximately 73,000 tracts. In certain tracts, substantially more than 80 percent of reportable HMDA data would be retained.
                        </P>
                    </FTNT>
                    <P>Therefore, the Bureau believes that it is reasonable to interpret “engaged for profit in the business of mortgage lending” to include nondepository institutions that originated at least 100 closed-end mortgage loans in each of the two preceding calendar years. The Bureau believes that the proposed increase to the closed-end coverage threshold for nondepository institutions would effectuate the purposes of HMDA by ensuring significant coverage of nondepository mortgage lending, while facilitating compliance with HMDA by reducing burden on smaller institutions and excluding nondepository institutions that are not engaged for profit in the business of mortgage lending. The Bureau believes that the reasons provided for the proposed changes to the closed-end coverage threshold for depository institutions in the section-by-section analysis of § 1003.2(g)(1)(v)(A) above apply to the threshold for nondepository institutions as well. Additionally, the proposed increase to the threshold would promote consistency by subjecting nondepository institutions to the same threshold that applies to depository institutions.</P>
                    <HD SOURCE="HD3">Estimates for Other Closed-End Coverage Thresholds</HD>
                    <P>
                        The Bureau also generated estimates for closed-end coverage thresholds higher than those in the proposed alternatives. Similar to the estimates for depository institutions, these estimates reflect that the decrease in the number of nondepository institutions that would be required to report HMDA data becomes more pronounced at thresholds higher than 100. Moreover, such thresholds would decrease visibility into nondepository institutions relative to the coverage criteria that pre-dated the 2015 HMDA Rule.
                        <SU>117</SU>
                        <FTREF/>
                         For example, if the closed-end coverage threshold were increased from 25 to 250 loans, the Bureau estimates that approximately 573 out of about 697 nondepository institutions would continue to be required to report HMDA data and approximately 124 nondepository institutions, or about 18 percent of nondepository institutions covered under the current rule, would be relieved of their HMDA reporting responsibilities. The Bureau estimates that with an increase in the closed-end coverage threshold to 250, about 99 percent of total originations of closed-end mortgage loans reported by nondepository institutions under the current Regulation C coverage criteria, or approximately 3.42 million closed-end mortgage loan originations under the current market conditions, would continue to be reported.
                    </P>
                    <FTNT>
                        <P>
                            <SU>117</SU>
                             The Bureau noted in the 2015 HMDA Rule that any closed-end reporting threshold set at 100 loans would not provide enhanced insight into lending practices of nondepository institutions and that a threshold above 100 closed-end mortgage loans would decrease visibility into nondepository institutions' practices. At the time, the Bureau explained its belief that, due to the questions raised about potential risks posed to applicants and borrowers by nondepository institutions and the lack of other publicly available data sources about nondepository institutions, requiring additional nondepository institutions to report HMDA data will better effectuate HMDA's purposes. 80 FR 66128, 66153, 66281 (Oct. 28, 2015).
                        </P>
                    </FTNT>
                    <P>Further, if the closed-end coverage threshold were increased from 25 to 500 loans, for example, the Bureau estimates that approximately 477 out of about 697 nondepository institutions would continue to be required to report HMDA data and approximately 220 nondepository institutions, or about 32 percent of nondepository institutions covered under the current coverage criteria, would be relieved of their HMDA reporting responsibilities. The Bureau estimates that with an increase of the closed-end coverage threshold to 500, about 98 percent of total originations of closed-end mortgage loans reported by nondepository institutions under the current Regulation C coverage criteria, or approximately 3.38 million closed-end mortgage loan originations under the current market conditions, would continue to be reported.</P>
                    <P>
                        The Bureau's estimates also reflect that the effect on data available at the 
                        <PRTPAGE P="20986"/>
                        census tract level would become more pronounced at closed-end mortgage loan coverage thresholds above 100. For example, the Bureau estimates that increasing the closed-end coverage threshold from 25 to 250 would result in a loss of at least 20 percent of reportable HMDA data in over 4,000 out of approximately 74,000 total census tracts, or 5.4 percent of the total number census tracts. Of the approximately 4,000 census tracts where there would be a loss of at least 20 percent of reportable HMDA data at such threshold, about 14 percent are rural tracts and just over 8 percent are low-to-moderate income tracts. Further, the Bureau estimates that increasing the closed-end coverage threshold from 25 to 500 would result in a loss of at least 20 percent of reportable HMDA data in approximately 11,000 out of approximately 74,000 total census tracts, or 14.9 percent of the total number census tracts. Of the approximately 11,000 census tracts where there would be a loss of at least 20 percent of reportable HMDA data at such threshold, about 32 percent are rural tracts and about 17 percent are low-to-moderate income tracts.
                    </P>
                    <P>Although the estimates for these higher closed-end coverage thresholds reflect that a high percentage of total originations of closed-end mortgage loans would continue to be reported by nondepository institutions, the Bureau believes that the decrease in coverage of nondepository institutions relative to the level of coverage that pre-dated the 2015 HMDA Rule could make it more difficult for the public and public officials to analyze whether lower-volume nondepository institutions are serving the housing needs of their communities. Therefore, the Bureau believes that if the closed-end coverage threshold were increased to a level above 100 loans, the loss of visibility into nondepository lending and the loss of reportable HMDA data at the census tract level available to serve HMDA's purposes may not be justified by the significant reduction in compliance costs for the nondepository institutions that would no longer be required to report HMDA data at such higher thresholds.</P>
                    <HD SOURCE="HD3">Request for Feedback</HD>
                    <P>For the reasons discussed above, the Bureau proposes to increase the closed-end mortgage loan-volume threshold in § 1003.2(g)(2)(ii)(A) from 25 to 50 in Alternative 1, or from 25 to 100 in Alternative 2, and to make conforming amendments to comments 2(g)-1 and -5. The Bureau requests comment on the proposed changes to the closed-end coverage threshold for institutional coverage of nondepository institutions in § 1003.2(g)(2)(ii)(A).</P>
                    <P>Specifically, the Bureau solicits feedback on the proposed increase, including comments on: (1) How the proposed increase to the closed-end coverage threshold to 50, 100, or another number, including any threshold significantly above 100, would affect the number of nondepository financial institutions required to report data on closed-end mortgage loans; (2) the significance of the data that would not be available as a result of the proposed increase to the closed-end coverage threshold to 50, 100, or another number, including (a) whether, and under what circumstances, the proposed increase would prevent public officials and the public from understanding if nondepository financial institutions excluded by the proposed 50, 100, or another closed-end coverage threshold are serving the needs of their community, (b) whether, and under what circumstances, the proposed increase to the closed-end coverage threshold to 50, 100, or another number would negatively impact the ability of public officials to make determinations with respect to the distribution of public sector investments in a manner designed to improve the private investment environment, and (c) whether, and under what circumstances, the proposed increase to the closed-end coverage threshold would exclude data that would be valuable for identifying possible fair lending violations or enforcing antidiscrimination laws; and (3) the reduction in burden that would result from the proposed increase to the closed-end coverage threshold for institutions that would not be required to report.</P>
                    <HD SOURCE="HD3">2(g)(2)(ii)(B)</HD>
                    <HD SOURCE="HD3">Open-End Line of Credit Threshold for Institutional Coverage of Nondepository Institutions</HD>
                    <P>
                        The 2015 HMDA Rule established a coverage threshold of 100 open-end lines of credit in § 1003.2(g)(2)(ii)(B) as part of the definition of nondepository financial institution. As discussed in more detail in the section-by-section analysis of § 1003.2(g)(1)(v)(B) above, the 2017 HMDA Rule amended §§ 1003.2(g)(1)(v)(B) and (g)(2)(ii)(B) and 1003.3(c)(12) and related commentary to raise temporarily the open-end coverage threshold to 500 loans for calendar years 2018 and 2019.
                        <SU>118</SU>
                        <FTREF/>
                         For the reasons discussed in the section-by-section analysis of § 1003.2(g)(1)(v)(B), and to ensure the thresholds are consistent for depository and nondepository institutions, the Bureau is now proposing to extend to January 1, 2022, Regulation C's temporary open-end threshold of 500 open-end lines of credit for institutional and transactional coverage of both depository and nondepository institutions and then set the threshold at 200 open-end lines of credit upon the expiration in 2022 of the proposed extension of the temporary threshold. The Bureau is therefore proposing to set the open-end line of credit threshold for institutional coverage of nondepository institutions in § 1003.2(g)(2)(ii)(B) at 500 effective January 1, 2020, and then at 200 effective January 1, 2022. These changes would conform to the changes that the Bureau is proposing with respect to the open-end threshold for institutional coverage for depository institutions in § 1003.2(g)(1)(v)(B) and the open-threshold for transactional coverage in § 1003.3(c)(12).
                    </P>
                    <FTNT>
                        <P>
                            <SU>118</SU>
                             82 FR 43088, 43095 (Sept. 13, 2017).
                            <E T="03"/>
                        </P>
                    </FTNT>
                    <P>
                        The Bureau believes that these proposed changes to the threshold in § 1003.2(g)(2)(ii)(B) would effectuate the purposes of HMDA by ensuring significant coverage of nondepository mortgage lending, while facilitating compliance with HMDA by reducing burden on smaller institutions and excluding nondepository institutions that are not engaged for profit in the business of mortgage lending. The Bureau believes that the reasons provided for the proposed changes to the open-end threshold for depository institutions in the section-by-section analysis of § 1003.2(g)(1)(v)(B) above apply to the threshold for nondepository institutions as well. Additionally, the proposed changes to the threshold in § 1003.2(g)(2)(ii)(B) would promote consistency by subjecting nondepository institutions to the same threshold that applies to the depository institutions that make up the bulk of the open-end line of credit market. According to the Bureau's estimates, nondepository institutions account for only a small percentage of the institutions and loans in the open-end line of credit market.
                        <SU>119</SU>
                        <FTREF/>
                         Table 4 in the Bureau's analysis under Dodd-Frank Act section 1022(b) in part VI.E.4 below provides coverage estimates for nondepository institutions at the current temporary threshold of 500 open-end lines of credit that the Bureau proposes to extend and at the proposed threshold of 200 open-end lines of credit that would take effect when the temporary threshold expires. 
                        <PRTPAGE P="20987"/>
                        The Bureau requests comment on the proposed changes to the open-end line of credit threshold for institutional coverage of nondepository institutions in § 1003.2(g)(2)(ii)(B).
                    </P>
                    <FTNT>
                        <P>
                            <SU>119</SU>
                             See 
                            <E T="03">infra</E>
                             part VI.E.4 at Table 4.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">Section 1003.3 Exempt Institutions and Excluded and Partially Exempt Transactions</HD>
                    <HD SOURCE="HD3">3(c) Excluded Transactions</HD>
                    <HD SOURCE="HD3">3(c)(11)</HD>
                    <P>
                        As adopted in the 2015 HMDA Rule, § 1003.3(c)(11) provides an exclusion from the requirement to report closed-end mortgage loans for institutions that did not originate at least 25 closed-end mortgage loans in each of the two preceding calendar years. This transactional coverage threshold was intended to complement a closed-end mortgage loan reporting threshold included in the definition of financial institution in § 1003.2(g). The 2017 HMDA Rule replaced “each” with “either” in § 1003.3(c)(11) to correct a drafting error and to ensure that the exclusion provided in that section mirrors the loan-volume threshold for financial institutions in § 1003.2(g).
                        <SU>120</SU>
                        <FTREF/>
                         For the reasons discussed in the section-by-section analysis of § 1003.2(g), the Bureau is now proposing to increase Regulation C's closed-end threshold for institutional and transactional coverage from 25 to 50 under Alternative 1 and from 25 to 100 under Alternative 2. Therefore, the Bureau proposes to increase the closed-end threshold for transactional coverage from 25 to 50 under Alternative 1 in § 1003.3(c)(11) and comments 3(c)(11)-1 and -2, and from 25 to 100 under Alternative 2 in § 1003.3(c)(11) and comments 3(c)(11)-1 and -2. This proposed change would conform to the related changes the Bureau is proposing with respect to the closed-end threshold for institutional coverage in § 1003.2(g).
                    </P>
                    <FTNT>
                        <P>
                            <SU>120</SU>
                             82 FR 43088, 43100 (Sept. 13, 2017).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3(c)(12)</HD>
                    <P>
                        As adopted in the 2015 HMDA Rule, § 1003.3(c)(12) provides an exclusion from the requirement to report open-end lines of credit for institutions that did not originate at least 100 such loans in each of the two preceding calendar years. This transactional coverage threshold was intended to complement an open-end reporting threshold included in the definition of financial institution in § 1003.2(g), which sets forth Regulation C's institutional coverage. The 2017 HMDA Rule replaced “each” with “either” in § 1003.3(c)(12) to correct a drafting error and to ensure that the exclusions provided in that section mirror the loan-volume thresholds for financial institutions in § 1003.2(g).
                        <SU>121</SU>
                        <FTREF/>
                         As discussed in more detail in the section-by-section analysis of § 1003.2(g), in the 2017 HMDA Rule the Bureau also amended §§ 1003.2(g) and 1003.3(c)(12) and related commentary to raise temporarily the open-end threshold in those provisions to 500 loans for calendar years 2018 and 2019.
                        <SU>122</SU>
                        <FTREF/>
                         For the reasons discussed in the section-by-section analysis of § 1003.2(g), the Bureau is now proposing to extend to January 1, 2022, Regulation C's current temporary open-end threshold for institutional and transactional coverage of 500 open-end lines of credit and then to set the threshold at 200 open-end lines of credit upon the expiration of the proposed extension of the temporary threshold. The Bureau therefore proposes to adjust the open-end line of credit threshold for transactional coverage in § 1003.3(c)(12) and comments 3(c)(12)-1 and -2 to 500 effective January 1, 2020, and to 200 effective January 1, 2022.
                        <SU>123</SU>
                        <FTREF/>
                         These changes would conform to the changes that the Bureau is proposing with respect to the open-end threshold for institutional coverage in § 1003.2(g).
                    </P>
                    <FTNT>
                        <P>
                            <SU>121</SU>
                             82 FR 43088, 43102 (Sept. 13, 2017).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>122</SU>
                             
                            <E T="03">Id.</E>
                             at 43095.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>123</SU>
                             The proposal would also make minor changes to an example in comment 3(c)(12)-1 effective January 1, 2020, to conform to the proposed change to the closed-end coverage threshold that is discussed in the section-by-section analysis of § 1003.2(g)(1)(v)(A) above.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3(d) Partially Exempt Transactions</HD>
                    <P>
                        Section 104(a) of the EGRRCPA amended HMDA section 304(i) by adding partial exemptions from HMDA's requirements that apply to certain transactions of eligible insured depository institutions and insured credit unions. In the 2018 HMDA Rule, the Bureau implemented and clarified HMDA section 304(i) by addressing a set of interpretive and procedural questions relating to the partial exemptions. Proposed § 1003.3(d) and related commentary would incorporate the partial exemptions and the interpretations and procedures from the 2018 HMDA Rule into Regulation C and further implement HMDA section 304(i) by addressing additional questions that have arisen with respect to the partial exemptions.
                        <SU>124</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>124</SU>
                             This proposed rule includes related amendments in § 1003.4 and its commentary referencing § 1003.3(d) that are discussed in the section-by-section analysis of § 1003.4. The Filing Instructions Guide for HMDA Data Collected in 2019 (2019 FIG) provides guidance to financial institutions on how to indicate in their HMDA submissions if they are invoking a partial exemption. 
                            <E T="03">See</E>
                             Fed. Fin. Insts. Examination Council (FFIEC), “Filing Instructions Guide for HMDA Data Collected in 2019,” at 21-54 (Oct. 2018), 
                            <E T="03">https://s3.amazonaws.com/cfpb-hmda-public/prod/help/2019-hmda-fig.pdf.</E>
                        </P>
                    </FTNT>
                    <P>Proposed § 1003.3(d)(1) sets forth definitions relating to the partial exemptions, including a definition of optional data that delineates which data points are covered by the partial exemptions. Proposed § 1003.3(d)(2) and (3) provides the general tests for when the partial exemptions apply for closed-end mortgage loans and open-end lines of credit, respectively. Proposed § 1003.3(d)(4) addresses voluntary reporting of data that are covered by a partial exemption for a partially exempt transaction. Proposed § 1003.3(d)(5) relates to the non-universal loan identifier that financial institutions must report for a partially exempt transaction if a ULI is not provided. Proposed § 1003.3(d)(6) implements the statutory exception to the partial exemptions for insured depository institutions with certain less than satisfactory examination histories under the CRA. Each of these paragraphs and related commentary are discussed in more detail below.</P>
                    <P>The loan thresholds added by the EGRRCPA to HMDA section 304(i) resemble in many respects the loan thresholds that determine institutional and transactional coverage in Regulation C. For example, both sets of thresholds relate to originations (rather than applications or purchases) and apply separately to closed-end mortgage loans and open-end lines of credit. In light of these similarities, the Bureau has used the institutional and transactional coverage thresholds in existing Regulation C as a model in interpreting certain aspects of the partial exemption thresholds in both the 2018 HMDA Rule and this proposed rule. The Bureau recognizes that there are advantages to industry stakeholders and others from using consistent language to describe similar requirements and therefore has used language in the proposed rule that parallels language in existing Regulation C wherever appropriate.</P>
                    <P>
                        Proposed comments 3(d)-1 through -5 address certain issues relating to the partial exemptions that the 2018 HMDA Rule does not specifically discuss. Proposed comments 3(d)-1 through -3 explain how to determine whether a partial exemption applies to a transaction after a merger or acquisition. Proposed comment 3(d)-1 describes the application of the partial exemption thresholds to a surviving or newly formed institution. Proposed comment 3(d)-2 describes how CRA examination history is handled in the event of a 
                        <PRTPAGE P="20988"/>
                        merger or acquisition for purposes of proposed § 1003.3(d)(6), which implements the exception to the partial exemptions for certain less than satisfactory CRA examination histories in HMDA section 304(i)(3). Proposed comment 3(d)-3 describes the applicability of partial exemptions during the calendar year of a merger or acquisition and provides various examples. These proposed comments are modeled closely on existing comments 2(g)-3 and -4, which explain how to determine whether an institution satisfies the definition of financial institution in § 1003.2(g) after a merger or acquisition.
                    </P>
                    <P>
                        Proposed comment 3(d)-4 relates to whether activities with respect to a particular closed-end mortgage loan or open-end line of credit constitute an origination for purposes of the partial exemption loan thresholds. Given the similarities between the coverage thresholds currently in Regulation C 
                        <SU>125</SU>
                        <FTREF/>
                         and the partial exemption thresholds under the EGRRCPA, the Bureau believes that the same guidance for determining whether activities constitute an origination that applies for purposes of the coverage thresholds in Regulation C's definition of financial institution should apply with respect to the partial exemption thresholds. Consistent with the approach taken in existing comment 2(g)-5 for the definition of financial institution, proposed comment 3(d)-4 refers to comments 4(a)-2 through -4 for guidance on this issue in the context of the partial exemptions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>125</SU>
                             
                            <E T="03">See</E>
                             12 CFR 1003.2(g)(1)(v) and (g)(2)(ii) and 1003.3(c)(11) and (12).
                        </P>
                    </FTNT>
                    <P>
                        Proposed comment 3(d)-5 addresses questions about whether a financial institution that does not itself meet the requirements for a partial exemption can claim an exemption if an affiliate or parent company meets the requirements. It clarifies that a financial institution that is not itself an insured credit union or an insured depository institution 
                        <SU>126</SU>
                        <FTREF/>
                         is not eligible for a partial exemption under § 1003.3(d)(2) and (3), even if it is owned by or affiliated with an insured credit union or an insured depository institution. This approach is consistent with HMDA section 304(i)(1) and (2), which by its terms applies “[w]ith respect to an insured depository institution or insured credit union” as defined in HMDA section 304(o). To clarify further the EGRRCPA's partial exemptions, the proposed comment also provides an example describing when a subsidiary of an insured credit union or insured depository institution could claim a partial exemption under § 1003.3(d) for its closed-end mortgage loans.
                    </P>
                    <FTNT>
                        <P>
                            <SU>126</SU>
                             For purposes of this proposed comment, insured credit union and insured depository institution are defined in proposed § 1003.3(d)(1)(i) and (ii), which, as explained below, mirrors how those terms are defined in HMDA section 304(o).
                        </P>
                    </FTNT>
                    <P>The Bureau requests comment on these proposed additions and the other proposed provisions of § 1003.3(d) that are discussed below, including whether these amendments appropriately implement section 104(a) of the EGRRCPA and whether there are any additional issues under the EGRRCPA that the Bureau should address in Regulation C.</P>
                    <HD SOURCE="HD3">3(d)(1)</HD>
                    <P>Proposed § 1003.3(d)(1) and proposed comment 3(d)(1)(iii)-1 define terms related to the partial exemptions for purposes of proposed § 1003.3(d). Proposed § 1003.3(d)(1)(i) defines the term “insured credit union” to mean an insured credit union as defined in section 101 of the Federal Credit Union Act (12 U.S.C. 1752), and proposed § 1003.3(d)(1)(ii) defines the term “insured depository institution” to mean an insured depository institution as defined in section 3 of the Federal Deposit Insurance Act (12 U.S.C. 1813). These definitions are consistent with the way HMDA section 304(o) defines the two terms for purposes of HMDA section 304.</P>
                    <P>Proposed § 1003.3(d)(1)(iii) and proposed comment 3(d)(1)(iii)-1 define the term “optional data” for purposes of proposed § 1003.3(d). For the reasons discussed below, proposed § 1003.3(d)(1)(iii) generally defines optional data as the data identified in § 1003.4(a)(1)(i), (a)(9)(i), and (a)(12), (15) through (30), and (32) through (38). Proposed comment 3(d)(1)(iii)-1 explains that the definition of optional data in § 1003.3(d)(1)(iii) identifies the data that are covered by the partial exemptions for certain transactions of insured depository institutions and insured credit unions under § 1003.3(d). It also clarifies that, if a transaction is not partially exempt under § 1003.3(d)(2) or (3), a financial institution must collect, record, and report optional data as otherwise required under part 1003.</P>
                    <P>The EGRRCPA added partial exemptions to HMDA section 304(i), and the definition of optional data in proposed § 1003.3(d)(1)(iii) specifies the data points covered by the partial exemptions. As the 2018 HMDA Rule explains, if a transaction qualifies for one of the EGRRCPA's partial exemptions, HMDA section 304(i) provides that the requirements of HMDA section 304(b)(5) and (6) shall not apply. In the 2018 HMDA Rule, the Bureau interpreted the requirements of HMDA section 304(b)(5) and (6) to include the 26 data points listed in Table 1 in the 2018 HMDA Rule, which are found in § 1003.4(a)(1)(i), (a)(9)(i), and (a)(12), (15) through (30), and (32) through (38).</P>
                    <P>
                        The Dodd-Frank Act added HMDA section 304(b)(5) and (6), which requires reporting of certain data points and provides the Bureau discretion to require additional data points.
                        <SU>127</SU>
                        <FTREF/>
                         In the 2015 HMDA Rule, the Bureau implemented the new data points specified in the Dodd-Frank Act (including those added in HMDA section 304(b)(5) and (6)), added a number of additional data points pursuant to the Bureau's discretionary authority, and made revisions to certain pre-existing data points to clarify their requirements, provide greater specificity in reporting, and align certain data points more closely with industry data standards.
                    </P>
                    <FTNT>
                        <P>
                            <SU>127</SU>
                             HMDA section 304(b)(5) requires disclosure of the number and dollar amount of mortgage loans grouped according to measurements of:
                        </P>
                        <P>• The total points and fees payable at origination in connection with the mortgage as determined by the Bureau;</P>
                        <P>• The difference between the APR associated with the loan and a benchmark rate or rates for all loans;</P>
                        <P>• The term in months of any prepayment penalty or other fee or charge payable on repayment of some portion of principal or the entire principal in advance of scheduled payments; and</P>
                        <P>• Such other information as the Bureau may require.</P>
                        <P>HMDA section 304(b)(6) requires disclosure of the number and dollar amount of mortgage loans and completed applications grouped according to measurements of:</P>
                        <P>• The value of the real property pledged or proposed to be pledged as collateral;</P>
                        <P>• The actual or proposed term in months of any introductory period after which the rate of interest may change;</P>
                        <P>• The presence of contractual terms or proposed contractual terms that would allow the mortgagor or applicant to make payments other than fully amortizing payments during any portion of the loan term;</P>
                        <P>• The actual or proposed term in months of the mortgage loan;</P>
                        <P>• The channel through which application was made;</P>
                        <P>• As the Bureau may determine to be appropriate, a unique identifier that identifies the loan originator as set forth in section 5102 of this title;</P>
                        <P>• As the Bureau may determine to be appropriate, a universal loan identifier;</P>
                        <P>• As the Bureau may determine to be appropriate, the parcel number that corresponds to the real property pledged or proposed to be pledged as collateral;</P>
                        <P>• The credit score of mortgage applicants and mortgagors, in such form as the Bureau may prescribe; and</P>
                        <P>• Such other information as the Bureau may require.</P>
                    </FTNT>
                    <P>
                        As explained in the 2018 HMDA Rule, the Bureau interprets the requirements 
                        <PRTPAGE P="20989"/>
                        of HMDA section 304(b)(5) and (6) for purposes of HMDA section 304(i) to include the 12 data points that the Bureau added to Regulation C in the 2015 HMDA Rule to implement data points specifically identified in HMDA section 304(b)(5)(A) through (C) or (b)(6)(A) through (I), which are the following: ULI; property address; rate spread; credit score; total loan costs or total points and fees; prepayment penalty term; loan term; introductory rate period; non-amortizing features; property value; application channel; and mortgage loan originator identifier.
                        <SU>128</SU>
                        <FTREF/>
                         As the 2018 HMDA Rule explains, the Bureau also interprets the requirements of HMDA section 304(b)(5) and (6) to include the 14 data points that were not found in Regulation C prior to the Dodd-Frank Act and that the Bureau required in the 2015 HMDA Rule citing its discretionary authority under HMDA section 304(b)(5)(D) and (b)(6)(J). Specifically, these data points are the following: The total origination charges associated with the loan; the total points paid to the lender to reduce the interest rate of the loan (discount points); the amount of lender credits; the interest rate applicable at closing or account opening; the debt-to-income ratio; the ratio of the total amount of debt secured by the property to the value of the property (combined loan-to-value ratio); for transactions involving manufactured homes, whether the loan or application is or would have been secured by a manufactured home and land or by a manufactured home and not land (manufactured home secured property type); the land property interest for loans or applications related to manufactured housing (manufactured home land property interest); the number of individual dwellings units that are income-restricted pursuant to Federal, State, or local affordable housing programs (multifamily affordable units); information related to the automated underwriting system used in evaluating an application and the result generated by the automated underwriting system; whether the loan is a reverse mortgage; whether the loan is an open-end line of credit; whether the loan is primarily for a business or commercial purpose; and the reasons for denial of a loan application, which were optionally reported under the Board's rule but became mandatory in the 2015 HMDA Rule.
                        <SU>129</SU>
                        <FTREF/>
                         The 2018 HMDA Rule indicates that insured depository institutions and insured credit unions need not report these 26 data points for transactions that qualify for a partial exemption, unless otherwise required by their regulator.
                        <SU>130</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>128</SU>
                             12 CFR 1003.4(a)(1)(i), (a)(9)(i), and (a)(12), (15), (17), (22), (25) through (28), and (33) and (34).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>129</SU>
                             12 CFR 1003.4(a)(16), (18) through (21), (23) and (24), (29) and (30), (32), and (35) through (38).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>130</SU>
                             Financial institutions regulated by the OCC are required to report reasons for denial on their HMDA loan/application registers pursuant to 12 CFR 27.3(a)(1)(i) and 128.6. Similarly, pursuant to regulations transferred from the Office of Thrift Supervision, certain financial institutions supervised by the FDIC are required to report reasons for denial on their HMDA loan/application registers. 12 CFR 390.147.
                        </P>
                    </FTNT>
                    <P>
                        As the 2018 HMDA Rule explains, the Bureau interprets the requirements of HMDA section 304(b)(5) and (6) not to include four other data points that are similar or identical to data points added to Regulation C by the Board and that the Bureau re-adopted in the 2015 HMDA Rule: Lien status of the subject property; whether the loan is subject to the Home Ownership and Equity Protection Act of 1994 (HOEPA); construction method for the dwelling related to the subject property; and the total number of individual dwelling units contained in the dwelling related to the loan (number of units).
                        <SU>131</SU>
                        <FTREF/>
                         The 2015 HMDA Rule did not alter the pre-existing Regulation C HOEPA status and lien status data requirements.
                        <SU>132</SU>
                        <FTREF/>
                         Construction method and total units, together, replaced the pre-existing Regulation C property type data point; the information required by the new data points is very similar to what the Board required, but institutions now must report the precise number of units rather than categorizing dwellings into one- to four-family dwellings and multifamily dwellings.
                        <SU>133</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>131</SU>
                             12 CFR 1003.4(a)(5), (13) and (14), and (31).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>132</SU>
                             The 2015 HMDA Rule extended the requirement to report lien status to purchased loans and no longer requires reporting of information about unsecured loans. 80 FR 66128, 66201 (Oct. 28, 2015).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>133</SU>
                             Prior to 2018, Regulation C required reporting of property type as one- to four-family dwelling (other than manufactured housing), manufactured housing, or multifamily dwelling, whereas the current rule requires reporting of whether the dwelling is site-built or a manufactured home, together with the number of individual dwelling units.
                        </P>
                    </FTNT>
                    <P>
                        The Board adopted its versions of these data points before HMDA section 304(b)(5) and (6) was added to HMDA by the Dodd-Frank Act, pursuant to HMDA authority that pre-existed section 304(b)(5) and (6). Although the Bureau cited HMDA section 304(b)(5) and (6) as additional support for these four data points in the 2015 HMDA Rule, the Bureau relied on HMDA section 305(a), which pre-dates the Dodd-Frank Act and independently provides legal authority for their adoption.
                        <SU>134</SU>
                        <FTREF/>
                         Given that these data points were not newly added by the Dodd-Frank Act or the Bureau, the Bureau concluded in the 2018 HMDA Rule that the EGRRCPA's amendments to HMDA section 304 do not affect them.
                        <SU>135</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>134</SU>
                             80 FR 66128, 66180-81, 66199-201, 66227 (Oct. 28, 2015).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>135</SU>
                             This interpretation is consistent with the EGRRCPA's legislative history, which suggests that Congress was focused on relieving regulatory burden associated with the Dodd-Frank Act. 
                            <E T="03">See, e.g.,</E>
                             164 Cong. Rec. S1423-24 (daily ed. Mar. 7, 2018) (statement of Sen. Crapo), S1529-30 (statement of Sen. McConnell), S1532-33 (statement of Sen. Cornyn), S1537-39 (statement of Sen. Lankford), S1619-20 (statement of Sen. Cornyn).
                        </P>
                    </FTNT>
                    <P>
                        The requirements of HMDA section 304(b)(5) and (6), and thus the partial exemptions, also do not include 17 other data points included in the 2015 HMDA Rule that are similar or identical to pre-existing Regulation C data points established by the Board and that were not required by HMDA section 304(b)(5) and (6) or promulgated by the Bureau using discretionary authority under HMDA section 304(b)(5)(D) and (b)(6)(J). These are: The Legal Entity Identifier (which replaced the pre-existing respondent identifier); application date; loan type; loan purpose; preapproval; occupancy type; loan amount; action taken; action taken date; State; county; census tract; ethnicity; race; sex; income; and type of purchaser.
                        <SU>136</SU>
                        <FTREF/>
                         Additionally, the requirements of HMDA section 304(b)(5) and (6), and thus the partial exemptions, do not include age because the Dodd-Frank Act added that requirement instead to HMDA section 304(b)(4).
                        <SU>137</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>136</SU>
                             12 CFR 1003.4(a)(1)(ii), (a)(2) through (4) and (6) through (8), (a)(9)(ii), and (a)(10) and (11) and 1003.5(a)(3).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>137</SU>
                             Dodd-Frank Act section 1094(3)(A)(i).
                        </P>
                    </FTNT>
                    <P>Consistent with the scope of the new partial exemptions as explained in the 2018 HMDA Rule, the proposed general definition of optional data in § 1003.3(d)(1)(iii) encompasses 26 of the 48 data points currently set forth in Regulation C.</P>
                    <P>For ease of reference throughout § 1003.3(d), proposed § 1003.3(d)(1)(iv) defines partially exempt transaction as a covered loan or application that is partially exempt under § 1003.3(d)(2) or (3).</P>
                    <HD SOURCE="HD3">3(d)(2)</HD>
                    <P>
                        HMDA section 304(i)(1) provides that the requirements of HMDA section 304(b)(5) and (6) shall not apply with respect to closed-end mortgage loans of an insured depository institution or insured credit union if it originated fewer than 500 closed-end mortgage loans in each of the two preceding calendar years. Proposed § 1003.3(d)(2) and proposed comment 3(d)(2)-1 implement this provision. Proposed 
                        <PRTPAGE P="20990"/>
                        § 1003.3(d)(2) states that, except as provided in § 1003.3(d)(6), an insured depository institution or insured credit union that, in each of the two preceding calendar years, originated fewer than 500 closed-end mortgage loans that are not excluded from part 1003 pursuant to § 1003.3(c)(1) through (10) or (c)(13) is not required to collect, record, or report optional data as defined in § 1003.3(d)(1)(iii) for applications for closed-end mortgage loans that it receives, closed-end mortgage loans that it originates, and closed-end mortgage loans that it purchases.
                    </P>
                    <P>
                        The EGRRCPA and HMDA do not define the term “closed-end mortgage loan” for purposes of HMDA section 304(i). They also do not specify whether the term includes loans that would otherwise not be subject to HMDA reporting under Regulation C, such as loans used primarily for agricultural purposes.
                        <SU>138</SU>
                        <FTREF/>
                         The Bureau explained in the 2018 HMDA Rule that the term “closed-end mortgage loan” as used in HMDA section 304(i) is best interpreted to include only those closed-end mortgage loans that would otherwise be reportable under HMDA. This interpretation is consistent with how loans are counted for purposes of the thresholds in Regulation C's existing institutional and transactional coverage provisions, which are independent of the new partial exemptions and unaffected by the EGRRCPA.
                        <SU>139</SU>
                        <FTREF/>
                         Accordingly, in the 2018 HMDA Rule, the Bureau interpreted the term “closed-end mortgage loan” to include any closed-end mortgage loan as defined in § 1003.2(d) that is not excluded from Regulation C pursuant to § 1003.3(c)(1) through (10) or (c)(13). Proposed § 1003.3(d)(2) would incorporate that interpretation into Regulation C.
                    </P>
                    <FTNT>
                        <P>
                            <SU>138</SU>
                             12 CFR 1003.3(c)(9).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>139</SU>
                             As discussed above in the section-by-section analysis of §§ 1003.2(g) and 1003.3(c), the current definition of “depository financial institution” in § 1003.2(g)(1)(v) is limited to institutions that either (1) originated in each of the two preceding calendar years at least 25 closed-end mortgage loans that are not excluded from Regulation C pursuant to § 1003.3(c)(1) through (10) or (c)(13); or (2) originated in each of the two preceding calendar years at least 500 open-end lines of credit that are not excluded from Regulation C pursuant to § 1003.3(c)(1) through (10). 
                            <E T="03">See also</E>
                             12 CFR 1003.3(c)(11), (12) (excluding closed-end mortgage loans from the requirements of Regulation C if the financial institution originated fewer than 25 closed-end mortgage loans in either of the two preceding calendar years, and excluding open-end lines of credit from the requirements of Regulation C if the financial institution originated fewer than 500 open-end lines of credit in either of the two preceding calendar years). The threshold of 500 open-end lines of credit for institutional and transactional coverage in Regulation C is temporary.
                        </P>
                    </FTNT>
                    <P>Proposed comment 3(d)(2)-1 provides an illustrative example of how the closed-end partial exemption threshold works. For the reasons stated in the section-by-section analysis of § 1003.3(d) above, proposed comment 3(d)(2)-1 also provides a cross-reference to comments 4(a)-2 through -4 for guidance about the activities that constitute an origination.</P>
                    <HD SOURCE="HD3">3(d)(3)</HD>
                    <P>HMDA section 304(i)(2) provides that the requirements of HMDA section 304(b)(5) and (6) shall not apply with respect to open-end lines of credit of an insured depository institution or insured credit union if it originated fewer than 500 open-end lines of credit in each of the two preceding calendar years. Proposed § 1003.3(d)(3) and proposed comment 3(d)(3)-1 implement this provision. Proposed § 1003.3(d)(3) provides that, except as provided in § 1003.3(d)(6), an insured depository institution or insured credit union that, in each of the two preceding calendar years, originated fewer than 500 open-end lines of credit that are not excluded from part 1003 pursuant to § 1003.3(c)(1) through (10) is not required to collect, record, report, or disclose optional data as defined in § 1003.3(d)(1)(iii) for applications for open-end lines of credit that it receives, open-end lines of credit that it originates, and open-end lines of credit that it purchases.</P>
                    <P>
                        The EGRRCPA and HMDA do not define the term “open-end line of credit” for purposes of HMDA section 304(i). They also do not specify whether the term includes lines of credit that would otherwise not be subject to HMDA reporting under Regulation C, such as loans used primarily for agricultural purposes.
                        <SU>140</SU>
                        <FTREF/>
                         The Bureau explained in the 2018 HMDA Rule its belief that the term “open-end line of credit” as used in HMDA section 304(i) is best interpreted to include only those open-end lines of credit that would otherwise be reportable under HMDA. This interpretation is consistent with how lines of credit are counted for purposes of the thresholds in Regulation C's existing institutional and transactional coverage provisions, which are independent of the new partial exemptions and unaffected by the EGRRCPA. Accordingly, in the 2018 HMDA Rule, the Bureau interpreted the term “open-end line of credit” to include any open-end line of credit as defined in § 1003.2(o) that is not excluded from Regulation C pursuant to § 1003.3(c)(1) through (10). Proposed § 1003.3(d)(3) would incorporate that interpretation into Regulation C.
                    </P>
                    <FTNT>
                        <P>
                            <SU>140</SU>
                             
                            <E T="03">See</E>
                             12 CFR 1003.3(c)(9).
                        </P>
                    </FTNT>
                    <P>Proposed comment 3(d)(3)-1 provides a cross-reference to § 1003.3(c)(12) and comments 3(c)(12)-1 and -2, which provide an exclusion for certain open-end lines of credit from Regulation C and permit voluntary reporting of such transactions under certain circumstances. While the temporary threshold of 500 open-end lines of credit is in place for institutional and transactional coverage, all of the open-end lines of credit that are covered by the partial exemption for open-end lines of credit in HMDA section 304(i)(2) are completely excluded from the requirements of part 1003 under current §§ 1003.2(g)(1)(v) and 1003.3(c)(12). For the reasons stated in the section-by-section analysis of § 1003.3(d) above, proposed comment 3(d)(3)-1 also provides a cross-reference to comments 4(a)-2 through -4 for guidance about the activities that constitute an origination.</P>
                    <HD SOURCE="HD3">3(d)(4)</HD>
                    <P>Some data points required under Regulation C are reported using multiple data fields, such as the property address data point, which consists of street address, city, State, and Zip Code data fields. The 2018 HMDA Rule provides that insured depository institutions and insured credit unions covered by a partial exemption have the option of reporting exempt data fields as long as they report all data fields within any exempt data point for which they report data. Proposed § 1003.3(d)(4) and proposed comments 3(d)(4)-1 to -3 and 3(d)(4)(i)-1 would incorporate this aspect of the 2018 HMDA Rule into Regulation C and provide additional clarity regarding voluntary reporting of the property address data point.</P>
                    <P>
                        As the 2018 HMDA Rule explains, whether a partial exemption applies to an institution's lending activity for a particular calendar year depends on an institution's origination activity in each of the preceding two years and, in some cases, cannot be determined until just before data collection must begin for that particular calendar year. For example, whether a partial exemption applies to closed-end mortgage loans for which final action is taken in 2020 depends on the number of closed-end mortgage loans originated by the insured depository institution or insured credit union in 2018 and 2019. Thus, an insured depository institution or insured credit union might not know until the end of 2019 what information it needs to collect in 2020 and report in 2021. Some insured depository institutions and insured credit unions 
                        <PRTPAGE P="20991"/>
                        eligible for a partial exemption under the EGRRCPA may therefore find it less burdensome to report all of the data, including the exempt data points, than to separate the exempt data points from the required data points and exclude the exempt data points from their submissions.
                        <SU>141</SU>
                        <FTREF/>
                         Even when insured depository institutions and insured credit unions have had time to adjust their systems to implement the partial exemptions, some may still find it less burdensome to report data covered by a partial exemption, especially if their loan volumes tend to fluctuate just above or below the threshold from year to year. The Bureau concluded in the 2018 HMDA Rule that section 104(a) is best interpreted as permitting optional reporting of data covered by the EGRRCPA's partial exemptions. Section 104(a) provides that certain requirements do not apply to affected institutions but does not prohibit those affected institutions from voluntarily reporting data. This interpretation is consistent not only with the statutory text but also with the apparent congressional intent to reduce burden on certain institutions. Accordingly, the Bureau interpreted the EGRRCPA in the 2018 HMDA Rule to permit insured depository institutions and insured credit unions voluntarily to report data that are covered by the partial exemptions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>141</SU>
                             The Bureau recognized in the 2018 HMDA Rule that this might be particularly true with respect to data submission in 2019, as collection of 2018 data was already underway when the EGRRCPA took effect, and system changes implementing the new partial exemptions may take time to complete. In the 2018 HMDA Rule, the Bureau interpreted the EGRRCPA to apply to data that are collected or reported under HMDA on or after May 24, 2018. Because data collected from January 1, 2018, to May 23, 2018, would not be reported until early 2019, the EGRRCPA relieves insured depository institutions and insured credit unions that are eligible for a partial exemption of the obligation to report certain data in 2019 that may have been collected before May 24, 2018. If optional reporting of data covered by a partial exemption were not permitted, such institutions would have had to remove exempt data previously collected before submitting their 2018 data in early 2019, a process that could have been burdensome for some institutions.
                        </P>
                    </FTNT>
                    <P>
                        Aspects of the Bureau's current HMDA platform used for receiving HMDA submissions, including edit checks 
                        <SU>142</SU>
                        <FTREF/>
                         performed on incoming submissions, are set up with the expectation that HMDA reporters will provide data for an entire data point when data are reported for any data field within that data point. The Bureau explained in the 2018 HMDA Rule that adjusting the HMDA platform to accept submissions in which affected institutions report some, but not all, data fields in a data point covered by a partial exemption for a specific transaction would increase operational complexity and costs associated with changing the HMDA edits in the Filing Instructions Guide for HMDA Data Collected. Doing so would result in a less efficient implementation and submission process for the Bureau, HMDA reporters, their vendors, and other key stakeholders. Accordingly, the Bureau indicated in the 2018 HMDA Rule that the HMDA platform would continue to accept submissions of a data field that is covered by a partial exemption under the EGRRCPA for a specific loan or application as long as insured depository institutions and insured credit unions that choose to voluntarily report the data include all other data fields that the data point comprises.
                    </P>
                    <FTNT>
                        <P>
                            <SU>142</SU>
                             The HMDA edit checks are rules to assist filers in checking the accuracy of HMDA data prior to submission. The 2019 FIG, a compendium of resources to help financial institutions file HMDA data collected in 2019 with the Bureau in 2020, explains that there are four types of edit checks: Syntactical, validity, quality, and macro quality. Table 2 (Loan/Application Register) in the 2019 FIG identifies the data fields currently associated with each data point. 
                            <E T="03">See</E>
                             FFIEC, “Filing Instructions Guide for HMDA Data Collected in 2019,” at 15-65 (Oct. 2018), 
                            <E T="03">https://s3.amazonaws.com/cfpb-hmda-public/prod/help/2019-hmda-fig.pdf.</E>
                        </P>
                    </FTNT>
                    <P>Proposed § 1003.3(d)(4) incorporates the voluntary reporting interpretations and procedures from the 2018 HMDA Rule into Regulation C. Since issuing the 2018 HMDA Rule, the Bureau has also received questions relating to voluntary reporting of property address under § 1003.4(a)(9)(i) because the property address data point under § 1003.4(a)(9)(i) is covered by the partial exemptions and includes State as a data field, and State is also a separate data point under § 1003.4(a)(9)(ii)(A) that is not covered by the partial exemptions. To address possible confusion, the Bureau has included additional detail in proposed § 1003.3(d)(4) and proposed comment 3(d)(4)(i)-1 about voluntary reporting of property address.</P>
                    <P>Proposed § 1003.3(d)(4) provides that a financial institution eligible for a partial exemption under § 1003.3(d)(2) or (3) may collect, record, and report optional data as defined in § 1003.3(d)(1)(iii) for a partially exempt transaction as though the institution were required to do so, provided that: (i) If the institution reports the street address, city name, or Zip Code for the property securing a covered loan, or in the case of an application, proposed to secure a covered loan pursuant to § 1003.4(a)(9)(i), it reports all data that would be required by § 1003.4(a)(9)(i) if the transaction were not partially exempt; and (ii) If the institution reports any data for the transaction pursuant to § 1003.4(a)(15), (16), (17), (27), (33), or (35), it reports all data that would be required by § 1003.4(a)(15), (16), (17), (27), (33), or (35), respectively, if the transaction were not partially exempt.</P>
                    <P>Proposed comment 3(d)(4)-1 provides an example of voluntary reporting that is permitted under proposed § 1003.3(d)(4). Proposed comment 3(d)(4)-2 addresses how financial institutions may handle partially exempt transactions within the same loan/application register. It explains that a financial institution may collect, record, and report optional data for some partially exempt transactions under § 1003.3(d) in the manner specified in § 1003.3(d)(4), even if it does not collect, record, and report optional data for other partially exempt transactions under § 1003.3(d).</P>
                    <P>
                        Proposed comment 3(d)(4)-3 addresses how to handle a transaction that is partially exempt pursuant to § 1003.3(d) and for which a particular requirement to report optional data is not applicable to the transaction. The proposed comment explains that, in that circumstance, the insured depository institution or insured credit union complies with the particular requirement by reporting either that the transaction is exempt from the requirement or that the requirement is not applicable.
                        <SU>143</SU>
                        <FTREF/>
                         It also explains that an institution is considered as reporting data in a data field for purposes of § 1003.3(d)(4)(i) and (ii) if it reports not applicable for that data field for a partially exempt transaction. The proposed comment also provides examples.
                    </P>
                    <FTNT>
                        <P>
                            <SU>143</SU>
                             As noted above, the 2019 FIG provides guidance to financial institutions on how to indicate in their HMDA submissions if they are invoking a partial exemption. 
                            <E T="03">See supra</E>
                             note 124.
                        </P>
                    </FTNT>
                    <P>
                        Proposed comment 3(d)(4)(i)-1 explains that, if an institution eligible for a partial exemption under § 1003.3(d)(2) or (3) reports the street address, city name, or Zip Code for a partially exempt transaction pursuant to § 1003.4(a)(9)(i), it reports all data that would be required by § 1003.4(a)(9)(i) if the transaction were not partially exempt, including the State. The proposed comment also explains that an insured depository institution or insured credit union that reports the State pursuant to § 1003.4(a)(9)(ii) or comment 4(a)(9)(ii)-1 for a partially exempt transaction without reporting any other data required by § 1003.4(a)(9)(i) is not required to report the street address, city name, or Zip Code pursuant to § 1003.4(a)(9)(i). The Bureau believes that this proposed comment would help to clarify that, even though State is a property address 
                        <PRTPAGE P="20992"/>
                        data field under § 1003.4(a)(9)(i), reporting State does not trigger the requirement to report other property address data fields under § 1003.3(d)(4)(i), because State is also a stand-alone data point under § 1003.4(a)(9)(ii)(A) that is not covered by the partial exemptions.
                    </P>
                    <HD SOURCE="HD3">3(d)(5)</HD>
                    <P>
                        Pursuant to HMDA section 304(i), insured depository institutions and insured credit unions are not required to report a ULI for partially exempt transactions.
                        <SU>144</SU>
                        <FTREF/>
                         To ensure that partially exempt transactions can be identified in the HMDA data, the 2018 HMDA Rule requires financial institutions to provide a non-universal loan identifier (NULI) that meets certain requirements for any partially exempt transaction for which they do not report a ULI. For the reasons that follow, proposed § 1003.3(d)(5) and proposed comments 3(d)(5)-1 and -2 would incorporate the NULI requirements from the 2018 HMDA Rule into Regulation C, with minor adjustments for clarity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>144</SU>
                             Prior to the passage of the Dodd-Frank Act, the Board required reporting of an identifying number for the loan or application but did not require that the identifier be universal. HMDA section 304(b)(6)(G) requires reporting of, “as the Bureau may determine to be appropriate, a universal loan identifier.”
                        </P>
                    </FTNT>
                    <P>
                        In the 2015 HMDA Rule, the Bureau interpreted ULI as used in HMDA section 304(b)(6)(G) to mean an identifier that is unique within the industry and required that the ULI include the Legal Entity Identifier of the institution that assigned the ULI. Although the EGRRCPA exempts certain transactions from the ULI requirement, loans and applications must be identifiable in the HMDA data to ensure proper HMDA submission, processing, and compliance.
                        <SU>145</SU>
                        <FTREF/>
                         The EGRRCPA did not change this baseline component of data reporting, which pre-dates the Dodd-Frank Act's HMDA amendments and existed under Regulation C prior to the 2015 HMDA Rule. Accordingly, while insured depository institutions and insured credit unions do not have to report a ULI for a partially exempt transaction, they must continue to provide certain information so that each loan and application they report for HMDA purposes is identifiable. The ability to identify individual loans and applications is necessary to facilitate efficient and orderly submission of HMDA data and communications between the institution, the Bureau, and other applicable regulators. For example, identification of loans and applications is necessary to ensure that it is possible to address problems identified when edit checks are done upon submission or questions that arise when HMDA submissions are otherwise reviewed by regulators.
                    </P>
                    <FTNT>
                        <P>
                            <SU>145</SU>
                             HMDA requires that covered loans and applications be “itemized in order to clearly and conspicuously disclose” the applicable data for each loan or application. 12 U.S.C. 2803(a)(2).
                        </P>
                    </FTNT>
                    <P>To ensure the orderly administration of the HMDA program, proposed § 1003.3(d)(5) and proposed comments 3(d)(5)-1 and -2 would incorporate the NULI requirements of the 2018 HMDA Rule into Regulation C with minor adjustments. As the 2018 HMDA Rule explains, a NULI does not need to be unique within the industry and therefore does not need to include a Legal Entity Identifier as the ULI does. A check digit is not required as part of a NULI, as it is for a ULI under § 1003.4(a)(1)(i)(C), but may be voluntarily included in a NULI provided that the NULI, including the check digit, does not exceed 22 characters. Beyond these important differences, there are a number of similarities between the requirements for the ULI and those for the NULI. To the extent that NULI requirements resemble requirements for the ULI, the Bureau has attempted to conform proposed § 1003.3(d)(5) and its proposed commentary to the corresponding text of existing § 1003.4(a)(1)(i) and its commentary for ease of reference and consistency.</P>
                    <P>Proposed § 1003.3(d)(5) provides that, if, pursuant to § 1003.3(d)(2) or (3), a financial institution does not report a ULI pursuant to § 1003.4(a)(1)(i) for an application for a covered loan that it receives, a covered loan that it originates, or a covered loan that it purchases, the financial institution shall assign and report a NULI. It further provides that, to identify the covered loan or application, the NULI must be composed of up to 22 characters, which:</P>
                    <P>• May be letters, numerals, or a combination of letters and numerals;</P>
                    <P>• Must be unique within the annual loan/application register in which the covered loan or application is included; and</P>
                    <P>• Must not include any information that could be used to directly identify the applicant or borrower.</P>
                    <P>Proposed comment 3(d)(5)-1 explains the requirement that the NULI must be unique within the annual loan/application register in which the covered loan or application is included. Proposed comment 3(d)(5)-2 clarifies the scope of information that could be used to directly identify the applicant or borrower for purposes of § 1003.3(d)(5)(iii), using the same language that appears in comment 4(a)(1)(i)-2 with respect to the ULI.</P>
                    <P>
                        The proposed rule's requirements for the NULI are consistent with those in the 2018 HMDA Rule. However, the 2018 HMDA Rule states that the NULI must be “unique within the insured depository institution or credit union,” whereas proposed § 1003.3(d)(5)(ii) states that the NULI must be “unique within the annual loan/application register in which the covered loan or application is included.” This adjustment and similar adjustments that appear in proposed comment 3(d)(5)-1 are intended to clarify that the NULI must be unique within a financial institution's yearly HMDA submission but the NULI does not need to be unique across reporting years. For the same reason, the proposed rule does not incorporate the portion of the 2018 HMDA Rule stating that a financial institution may not use a NULI previously reported if the institution reinstates or reconsiders an application that was reported in a prior calendar year.
                        <SU>146</SU>
                        <FTREF/>
                         Thus, the proposed rule would allow a financial institution to use the same NULI for a partially exempt transaction in its 2021 loan/application register that the institution used for a different partially exempt transaction in its 2020 loan/application register. Because final action on an application may be taken in a different year than the year in which a NULI is assigned (for example, for applications received late in the year), insured depository institutions and insured credit unions may opt not to reassign NULIs that they have assigned previously in order to ensure that all NULIs included in their annual loan/application register are unique within that annual loan/application register.
                    </P>
                    <FTNT>
                        <P>
                            <SU>146</SU>
                             83 FR 45325, 45330 (Sept. 7, 2018).
                        </P>
                    </FTNT>
                    <P>The Bureau recognizes that some insured depository institutions and insured credit unions may prefer to report a ULI for partially exempt transactions even if they are not required to do so. As explained in the 2018 HMDA Rule and in the section-by-section analysis of § 1003.3(d)(4) above and of § 1003.4(a)(1)(i) below, voluntary reporting of ULIs for partially exempt transactions is permissible under the EGRRCPA, and no NULI is required if a ULI is provided.</P>
                    <HD SOURCE="HD3">3(d)(6)</HD>
                    <P>
                        Notwithstanding the EGRRCPA's partial exemptions, new HMDA section 304(i)(3) provides that an insured depository institution shall comply with HMDA section 304(b)(5) and (6) if the insured depository institution has received a rating of “needs to improve record of meeting community credit 
                        <PRTPAGE P="20993"/>
                        needs” during each of its two most recent examinations or a rating of “substantial noncompliance in meeting community credit needs” on its most recent examination under section 807(b)(2) of the CRA. To implement this provision, proposed § 1003.3(d)(6) provides that § 1003.3(d)(2) and (3) do not apply to an insured depository institution that, as of the preceding December 31, had received a rating of “needs to improve record of meeting community credit needs” during each of its two most recent examinations or a rating of “substantial noncompliance in meeting community credit needs” on its most recent examination under section 807(b)(2) of the CRA.
                    </P>
                    <P>
                        As the Bureau explained in the 2018 HMDA Rule, the EGRRCPA does not specify the date as of which an insured depository institution's two most recent CRA examinations must be assessed for purposes of the exception in HMDA section 304(i)(3). In the 2018 HMDA Rule, the Bureau interpreted HMDA section 304(i)(3) to require that this assessment be made as of December 31 of the preceding calendar year. This timing is consistent with the timing for assessing Regulation C's asset-size threshold and requirement that a financial institution have a home or branch office located in a Metropolitan Statistical Area (MSA), which are both assessed as of the preceding December 31.
                        <SU>147</SU>
                        <FTREF/>
                         It also ensures that financial institutions can determine before they begin collecting information in any given calendar year whether they are eligible for a partial exemption for information collected for certain transactions in that year. Proposed § 1003.3(d)(6) would incorporate this interpretation into Regulation C.
                    </P>
                    <FTNT>
                        <P>
                            <SU>147</SU>
                             12 CFR 1003.2(g)(1)(i) and (ii) and (g)(2)(i); comment 2(g)-1.
                        </P>
                    </FTNT>
                    <P>Proposed comment 3(d)(6)-1 explains that the preceding December 31 means the December 31 preceding the current calendar year. It includes the same example that was provided in the 2018 HMDA Rule to illustrate how the exception works, with minor wording changes for clarity.</P>
                    <HD SOURCE="HD2">Section 1003.4 Compilation of Reportable Data</HD>
                    <HD SOURCE="HD3">4(a) Data Format and Itemization</HD>
                    <P>Section 1003.4(a) requires financial institutions to collect specific data about covered loans, applications for covered loans, and purchases of covered loans. The EGRRCPA provides partial exemptions from this requirement for certain transactions of insured depository institutions and insured credit unions. To conform to the EGRRCPA, the Bureau proposes to amend the introductory paragraph of § 1003.4(a) to indicate that the requirement to collect the data identified in § 1003.4(a) is applicable except as specified in proposed § 1003.3(d), which implements the new partial exemptions. The proposed rule would also make a similar change to comment 4(a)-1. The Bureau requests comment on these proposed amendments and the other proposed amendments to § 1003.4(a) relating to the partial exemptions that are discussed below, including whether these amendments would appropriately implement section 104(a) of the EGRRCPA and whether there are any additional issues under the EGRRCPA that the Bureau should address in § 1003.4(a).</P>
                    <HD SOURCE="HD3">4(a)(1)(i)</HD>
                    <P>Section 1003.4(a)(1)(i) generally requires a financial institution to assign and report a ULI for the covered loan or application that can be used to identify and retrieve the covered loan or application file. As explained in the 2018 HMDA Rule and the section-by-section analysis of § 1003.3(d)(5) above, a financial institution is not required to assign and report a ULI for a partially exempt transaction if it instead assigns and reports a NULI. The Bureau therefore proposes to amend § 1003.4(a)(1)(i) to indicate that, for a partially exempt transaction under § 1003.3(d), the data collected shall include either a ULI or a NULI as described in § 1003.3(d)(5), and that a financial institution does not need to assign and report a ULI for a partially exempt transaction for which a NULI is assigned and reported under § 1003.3(d).</P>
                    <P>The Bureau also proposes to amend comment 4(a)(1)(i)-3 to indicate that the requirement to report the same ULI that was previously assigned or reported for purchased covered loans does not apply if the purchase of the covered loan is a partially exempt transaction under § 1003.3(d). Because the partial exemptions are only available to insured depository institutions that are not disqualified by their CRA examination histories and insured credit unions for certain transactions as set forth in § 1003.3(d), it is possible that a financial institution's purchase of a covered loan that was partially exempt when originated would not be a partially exempt transaction and that the purchasing financial institution would therefore need to assign a ULI. Comment 4(a)(1)(i)-3 would therefore clarify that a financial institution that purchases a covered loan and is ineligible for a partial exemption with respect to the purchased covered loan must assign a ULI and record and submit it in its loan/application register pursuant to § 1003.5(a)(1) if the financial institution that originated the loan did not assign a ULI. Consistent with the 2018 HMDA Rule, the proposed amendment to comment 4(a)(1)(i)-3 would clarify that this may occur, for example, if the loan was assigned a NULI under § 1003.3(d)(5) rather than a ULI by the loan originator.</P>
                    <P>The Bureau also proposes to amend comment 4(a)(1)(i)-4 to clarify the example provided in that comment of how ULIs are assigned if a financial institution reconsiders an application that was reported in a prior calendar year. The amendments clarify that the example assumes that the financial institution reported a ULI rather than a NULI in 2020 for the initial denied application and that the financial institution then made an origination that is not partially exempt when it reconsidered in 2021 the previously denied application.</P>
                    <P>The Bureau also proposes to add a new comment 4(a)(1)(i)-6 explaining that, for a partially exempt transaction under § 1003.3(d), a financial institution may report a ULI or a NULI. The proposed comment cross-references § 1003.3(d)(5) and comments 3(d)(5)-1 and -2 for guidance on the NULI. The Bureau believes that these proposed changes would help clarify financial institutions' responsibilities in assigning identifiers to partially exempt transactions.</P>
                    <HD SOURCE="HD3">4(a)(1)(ii)</HD>
                    <P>Section 1003.4(a)(1)(ii) generally requires financial institutions to collect the date the application was received or the date shown on the application form. Comment 4(a)(1)(ii)-3 explains that, if, within the same calendar year, an applicant asks a financial institution to reinstate a counteroffer that the applicant previously did not accept (or asks the institution to reconsider an application that was denied, withdrawn, or closed for incompleteness), the institution may treat that request as the continuation of the earlier transaction using the same ULI or as a new transaction with a new ULI. The Bureau believes that it is appropriate to apply the same approach with respect to NULIs. The Bureau is therefore proposing to amend comment 4(a)(1)(ii)-3 to reference both ULIs and NULIs.</P>
                    <HD SOURCE="HD3">4(a)(9)</HD>
                    <P>
                        Section 1003.4(a)(9) generally requires a financial institution to report the 
                        <PRTPAGE P="20994"/>
                        property address of the location of the property securing a covered loan or, in the case of an application, proposed to secure a covered loan (property address), as well as the State, the county, and in some cases the census tract of the property if the property is located in an MSA or Metropolitan Division (MD) in which the financial institution has a home or branch office, or if the institution is subject to § 1003.4(e). Comment 4(a)(9)-2 addresses situations involving multiple properties with more than one property taken as security. The comment explains that, if an institution is required to report specific information about the property identified in § 1003.4(a)(9) by another section of Regulation C such as, for example, § 1003.4(a)(29) or (30), the institution reports the information that relates to the property identified in § 1003.4(a)(9). The Bureau proposes to amend comment 4(a)(9)-2 to clarify that, in this circumstance, if the transaction is partially exempt under § 1003.3(d) and no data are reported pursuant to § 1003.4(a)(9), the institution reports the information that relates to the property that the institution would have identified in § 1003.4(a)(9) if the transaction were not partially exempt. This would mean that, for a partially exempt transaction in which more than one property is taken as security and no data are reported under § 1003.4(a)(9), a financial institution should choose one of the properties taken as a security that contains a dwelling and provide information about that property if the institution is required to report specific information about the property identified in § 1003.4(a)(9) by one or more other sections of Regulation C. The Bureau believes that this proposed amendment would assist financial institutions in applying comment 4(a)(9)-2 to partially exempt transactions.
                    </P>
                    <HD SOURCE="HD3">4(a)(9)(i)</HD>
                    <P>Section 1003.4(a)(9)(i) generally requires a financial institution to report the property address. To implement the EGRRCPA's partial exemptions, the Bureau proposes to amend comment 4(a)(9)(i)-1 to clarify that the requirement to report property address does not apply to partially exempt transactions under § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(12)</HD>
                    <P>Section 1003.4(a)(12) generally requires a financial institution to report the rate spread for covered loans and applications that are approved but not accepted, and that are subject to Regulation Z, 12 CFR part 1026, other than assumptions, purchased covered loans, and reverse mortgages. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(12)-7 to provide that § 1003.4(a)(12) does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(15)</HD>
                    <P>Section 1003.4(a)(15) generally requires financial institutions to report the credit score or scores relied on in making the credit decision and information about the scoring model used to generate each score. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(15)-1 to clarify that the requirement to report the credit score or scores relied on in making the credit decision and information about the scoring model used to generate each score does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(16)</HD>
                    <P>Section 1003.4(a)(16) generally requires financial institutions to report the principal reason(s) for denial of an application. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(16)-4 to clarify that the requirement to report the principal reason(s) for denial of an application does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(17)</HD>
                    <P>Section 1003.4(a)(17) generally requires that, for covered loans subject to Regulation Z § 1026.43(c), a financial institution shall report the amount of total loan costs if a disclosure is provided for the covered loan pursuant to Regulation Z § 1026.19(f), or the total points and fees charged in connection with the covered loan if the covered loan is not subject to the disclosure requirements in Regulation Z § 1026.19(f). To implement the EGRRCPA's partial exemptions, the proposed rule would amend comments 4(a)(17)(i)-1 and (ii)-1 to clarify that the requirement to report total loan costs or total points and fees, as applicable, does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(18)</HD>
                    <P>Section 1003.4(a)(18) generally requires financial institutions to report, for covered loans subject to the disclosure requirements in Regulation Z § 1026.19(f), the total of all borrower-paid origination charges. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(18)-1 to clarify that the requirement to report borrower-paid origination charges does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(19)</HD>
                    <P>Section 1003.4(a)(19) generally requires financial institutions to report, for covered loans subject to the disclosure requirements in Regulation Z § 1026.19(f), the points paid to the creditor to reduce the interest rate. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(19)-1 to clarify that the requirement to report discount points does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(20)</HD>
                    <P>Section 1003.4(a)(20) generally requires financial institutions to report, for covered loans subject to the disclosure requirements in Regulation Z § 1026.19(f), the amount of lender credits. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(20)-1 to clarify that the requirement to report lender credits does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(21)</HD>
                    <P>Section 1003.4(a)(21) generally requires financial institutions to report the interest rate applicable to the approved application or to the covered loan at closing or account opening. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(21)-1 to clarify that the requirement to report interest rate does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(22)</HD>
                    <P>Section 1003.4(a)(22) generally requires financial institutions to report the term in months of any prepayment penalty for covered loans or applications subject to Regulation Z, 12 CFR part 1026. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(22)-1 to clarify that the requirement to report the term of any prepayment penalty does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(23)</HD>
                    <P>
                        Section 1003.4(a)(23) generally requires financial institutions to report 
                        <PRTPAGE P="20995"/>
                        the ratio of the applicant's or borrower's total monthly debt to the total monthly income relied on in making the credit decision (debt-to-income ratio). To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(23)-1 to clarify that the requirement to report the debt-to-income ratio does not apply to transactions that are partially exempt under proposed § 1003.3(d).
                    </P>
                    <HD SOURCE="HD3">4(a)(24)</HD>
                    <P>Section 1003.4(a)(24) generally requires financial institutions to report the ratio of the total amount of debt secured by the property to the value of the property relied on in making the credit decision (combined loan-to-value ratio). To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(24)-1 to clarify that the requirement to report the combined loan-to-value ratio does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(25)</HD>
                    <P>Section 1003.4(a)(25) generally requires financial institutions to report the scheduled number of months after which the legal obligation will mature or terminate or would have matured or terminated (loan term). To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(25)-5 to clarify that the requirement to report loan term does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(26)</HD>
                    <P>Section 1003.4(a)(26) generally requires financial institutions to report the number of months, or proposed number of months in the case of an application, from the closing or account opening until the first date the interest rate may change. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(26)-1 to clarify that the requirement to report the number of months, or proposed number of months in the case of an application, from closing or account opening until the first date the interest rate may change does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(27)</HD>
                    <P>Section 1003.4(a)(27) generally requires financial institutions to report contractual features that would allow payments other than fully amortizing payments. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(27)-1 to clarify that the requirement to report contractual features that would allow payments other than fully amortizing payments does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(28)</HD>
                    <P>Section 1003.4(a)(28) generally requires financial institutions to report the value of the property securing the covered loan or, in the case of an application, proposed to secure the covered loan relied on in making the credit decision. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(28)-1 to clarify that the requirement to report the property value relied on in making the credit decision does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(29)</HD>
                    <P>Section 1003.4(a)(29) generally requires financial institutions to report whether a covered loan or application is or would have been secured by a manufactured home and land or by a manufactured home and not land. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(29)-4 to clarify that the requirement to report whether a covered loan or application is or would have been secured by a manufactured home and land or by a manufactured home and not land does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(30)</HD>
                    <P>Section 1003.4(a)(30) generally requires financial institutions to report whether the applicant or borrower owns the land on which a manufactured home is or will be located through a direct or indirect ownership interest or leases the land through a paid or unpaid leasehold interest. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(30)-6 to clarify that the requirement to report ownership or leasing information on the manufactured home land property interest does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(32)</HD>
                    <P>Section 1003.4(a)(32) generally requires financial institutions to report information on the number of individual dwelling units in multifamily dwellings that are income-restricted pursuant to Federal, State, or local affordable housing programs. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(32)-6 to clarify that the requirement to report information on the number of individual dwelling units in multifamily dwellings that are income-restricted pursuant to Federal, State, or local affordable housing programs does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(33)</HD>
                    <P>Section 1003.4(a)(33) generally requires financial institutions to report whether the applicant or borrower submitted the application for the covered loan directly to the financial institution and whether the obligation arising from the covered loan was, or in the case of an application, would have been initially payable to the financial institution. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comments 4(a)(33)(i)-1 and 4(a)(33)(ii)-1 to clarify that the requirement for financial institutions to report whether the applicant or borrower submitted the application for the covered loan directly to the financial institution and whether the obligation arising from the covered loan was, or in the case of an application, would have been initially payable to the financial institution, does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(34)</HD>
                    <P>Section 1003.4(a)(34) generally requires financial institutions to report the unique identifier assigned by the Nationwide Mortgage Licensing System and Registry (NMLSR ID) for the mortgage loan originator. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(34)-1 to clarify that the requirement for financial institutions to report the NMLSR ID does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(35)</HD>
                    <P>
                        Section 1003.4(a)(35) generally requires financial institutions to report the name of the automated underwriting system (AUS) used by the financial institution to evaluate the application and the result generated by that AUS. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(35)-1 to clarify that the requirement for financial institutions to report the name of the AUS used to evaluate the application and the result generated by that AUS does not apply to transactions that are 
                        <PRTPAGE P="20996"/>
                        partially exempt under proposed § 1003.3(d).
                    </P>
                    <HD SOURCE="HD3">4(a)(37)</HD>
                    <P>Section 1003.4(a)(37) requires financial institutions to identify whether the covered loan or the application is for an open-end line of credit. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(37)-1 to clarify that the requirement for financial institutions to identify whether the covered loan or the application is for an open-end line of credit does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(a)(38)</HD>
                    <P>Section 1003.4(a)(38) requires financial institutions to identify whether the covered loan is, or the application is for a covered loan that will be, made primarily for a business or commercial purpose. To implement the EGRRCPA's partial exemptions, the proposed rule would amend comment 4(a)(38)-1 to clarify that the requirement for financial institutions to identify whether the covered loan is, or the application is for a covered loan that will be, made primarily for a business or commercial purpose does not apply to transactions that are partially exempt under proposed § 1003.3(d).</P>
                    <HD SOURCE="HD3">4(e) Data Reporting for Banks and Savings Associations That Are Required To Report Data on Small Business, Small Farm, and Community Development Lending Under CRA</HD>
                    <P>
                        Section 1003.4(e) provides that banks and savings associations that are required to report data on small business, small farm, and community development lending under regulations that implement the CRA shall also collect the information required by § 1003.4(a)(9) for property located outside MSAs and MDs in which the institution has a home or branch office, or outside any MSA. Section 1003.4(e) requires collection only of the information required by § 1003.4(a)(9)(ii) regarding the location of the property by State, county, and census tract because § 1003.4(a)(9)(i) itself requires collection of property address regardless of whether the property is located in an MSA or MD.
                        <SU>148</SU>
                        <FTREF/>
                         The proposed rule would amend § 1003.4(e) by changing the cross-reference from § 1003.4(a)(9) to § 1003.4(a)(9)(ii) in order to clarify that § 1003.4(e) only relates to the information required by § 1003.4(a)(9)(ii) without making any substantive changes. The Bureau believes that this proposed clarification of § 1003.4(e) would assist financial institutions and other stakeholders by making it clear that § 1003.4(e) does not require reporting of property address information required by § 1003.4(a)(9)(i) when a partial exemption applies.
                    </P>
                    <FTNT>
                        <P>
                            <SU>148</SU>
                             When the Board added § 1003.4(e) to Regulation C, the property address information that is now specified in § 1003.4(a)(9)(i) was not yet required. 
                            <E T="03">See</E>
                             80 FR 66128, 66186 (Oct. 28, 2015) (noting that § 1003.4(e) predates the 2015 HMDA Rule, which added the property address requirement now in § 1003.4(a)(9)(i)).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">V. Effective Dates for Proposed Rule</HD>
                    <P>
                        The Bureau proposes that the amendments included in this proposal take effect in stages, as provided in the proposed amendatory instructions below. The Bureau proposes that the proposed amendments that incorporate the interpretations and procedures from the 2018 HMDA Rule into Regulation C and further implement section 104(a) of the EGRRCPA take effect on January 1, 2020. This would allow stakeholders to benefit without significant delay from the additional certainty and clarity that the Regulation C amendments will provide regarding the EGRRCPA partial exemptions that are already in effect.
                        <SU>149</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>149</SU>
                             As noted, many of the proposed amendments would merely incorporate into Regulation C provisions of the EGRRCPA and the 2018 HMDA Rule that are already in effect. If the proposed rule is finalized, compliance with such amendments prior to the proposed rule's effective date would not violate Regulation C.
                        </P>
                    </FTNT>
                    <P>The Bureau proposes that the proposed adjustment to the closed-end threshold for institutional and transactional coverage take effect on January 1, 2020. Making this adjustment at the beginning of the calendar year would assist lenders in complying with data collection requirements, and making this adjustment at the beginning of 2020 would result in a decrease sooner in the significant compliance burden associated with data reporting for closed-end mortgage loans than if the adjustment were to be made in 2021 or later years. The Bureau proposes that the proposed temporary threshold of 500 open-end lines of credit for institutional and transactional coverage take effect on January 1, 2020. This effective date corresponds to the date when the initial temporary open-end coverage threshold established in the 2017 HMDA Rule is otherwise set to expire. The Bureau proposes that the threshold of 200 open-end lines of credit for institutional and transactional coverage take effect when the proposed temporary threshold expires on January 1, 2022, to allow affected institutions time to prepare to begin reporting and to provide the Bureau with additional time to assess how a requirement to report open-end lines of credit would affect institutions whose origination volume falls just above the proposed threshold of 200 open-end lines of credit.</P>
                    <P>The Bureau solicits comment on the proposed effective dates.</P>
                    <HD SOURCE="HD1">VI. Dodd-Frank Act Section 1022(b) Analysis of Proposed Rule</HD>
                    <P>
                        The Bureau is considering the potential benefits, costs, and impacts of this proposed rule.
                        <SU>150</SU>
                        <FTREF/>
                         The Bureau requests comment on the preliminary discussion presented below as well as submissions of additional data that could inform the Bureau's consideration of the benefits, costs, and impacts of this proposed rule. In developing this proposed rule, the Bureau has consulted with or offered to consult with the prudential regulators (the Board, the FDIC, the NCUA, and the OCC), the Department of Agriculture, the Department of Housing and Urban Development (HUD), the Department of Justice, the Department of the Treasury, the Department of Veterans Affairs, the Federal Housing Finance Agency, the Federal Trade Commission, and the Securities and Exchange Commission regarding, among other things, consistency with any prudential, market, or systemic objectives administered by such agencies.
                    </P>
                    <FTNT>
                        <P>
                            <SU>150</SU>
                             Specifically, section 1022(b)(2)(A) of the Dodd-Frank Act calls for the Bureau to consider the potential benefits and costs of a regulation to consumers and covered persons, including the potential reduction of access by consumers to consumer financial products or services; the impact on depository institutions and credit unions with $10 billion or less in total assets as described in section 1026 of the Dodd-Frank Act; and the impact on consumers in rural areas.
                        </P>
                    </FTNT>
                    <P>
                        As discussed in greater detail elsewhere throughout this supplementary information, in this proposed rulemaking the Bureau is proposing to incorporate into Regulation C, which implements HMDA, the interpretations and procedures from the 2018 HMDA Rule and to implement further section 104(a) of the EGRRCPA. The Bureau is also proposing to amend Regulation C, effective January 1, 2020, to increase the threshold for reporting data about closed-end mortgage loans to either 50 or 100 originated closed-end mortgage loans in each of the two preceding years. The Bureau in addition is proposing to amend Regulation C to extend for a period of two additional years the current data reporting threshold of 500 open-end lines of credit and then to set that threshold at 200 open-end lines of credit beginning in calendar year 2022. As a result, financial institutions originating fewer 
                        <PRTPAGE P="20997"/>
                        than 500 open-end lines of credit in either of the preceding two years but at least 200 open-end lines of credit in each of the two preceding years would not be required to collect such data until calendar year 2022 and financial institutions originating fewer than 200 open-end lines of credit in either of the preceding two years would be excluded from reporting data on open-end lines of credit.
                    </P>
                    <HD SOURCE="HD2">A. Provisions To Be Analyzed</HD>
                    <P>The proposal contains regulatory or commentary language (proposed provisions). The discussion below considers the benefits, costs, and impacts of the following major proposed provisions to:</P>
                    <P>1. Incorporate the interpretations and procedures from the 2018 HMDA Rule into Regulation C and further implement section 104(a) of the EGRRCPA, which grants eligible financial institutions partial exemptions from HMDA's requirements for certain transactions;</P>
                    <P>2. Increase the threshold for reporting data about closed-end mortgage loans from 25 to 50 or 100 originations in each of the two preceding calendar years; and</P>
                    <P>3. Extend for a period of two years, specifically calendar years 2020 and 2021, the current data reporting threshold of 500 open-end lines of credit in each of the two preceding calendar years and permanently set the threshold for reporting data about open-end lines of credit at 200 open-end lines of credit in each of the two preceding calendar years starting in calendar year 2022.</P>
                    <P>With respect to each major proposed provision, the discussion considers the benefits, costs, and impacts to consumers and covered persons. The discussion also addresses certain alternative provisions that were considered by the Bureau in the development of this proposed rule. The Bureau requests comment on the consideration of the potential benefits, costs, and impacts of this proposed rule.</P>
                    <HD SOURCE="HD2">B. Baselines for Consideration of Costs and Benefits</HD>
                    <P>The Bureau has discretion in any rulemaking to choose an appropriate scope of analysis with respect to potential benefits, costs, and impacts and an appropriate baseline. Each of the three sets of provisions included in this proposed rule are distinct from the others and hence the Bureau has chosen a different baseline for each of the three provisions: (1) To avoid double counting the impacts assessed for each of the three sets of provisions, and (2) to provide the clearest exposition of the effects of the Bureau's actions in this proposed rule and in implementing the EGRRCPA in the 2018 HMDA Rule. However, summed together, the impact estimates for each of the three sets of provisions as analyzed in this part form the total estimated impact for the proposed rule corresponding to a baseline where the 2015 HMDA Rule and the 2017 HMDA Rule were in effect but prior to the EGRRCPA.</P>
                    <P>
                        The first set of provisions under consideration would incorporate the interpretations and procedures from the 2018 HMDA Rule into Regulation C and further implement section 104(a) of the EGRRCPA, which grants eligible financial institutions partial exemptions from HMDA's requirements for certain transactions. In the analysis under section 1022(b) of the Dodd-Frank Act in the 2018 HMDA Rule, the Bureau adopted a post-statute baseline to assess the impact of the 2018 HMDA Rule because that rule merely interprets and provides guidance regarding what Congress required in section 104(a) of the EGRRCPA and provides procedures related to applying those requirements.
                        <SU>151</SU>
                        <FTREF/>
                         By contrast, the Bureau is proposing in this rulemaking to use its legislative rulemaking authority to amend Regulation C to implement the statutory provisions. For the consideration of benefits and costs of the first set of provisions in this proposed rule, the Bureau is therefore using a pre-statute baseline, 
                        <E T="03">i.e.,</E>
                         evaluating the benefits, costs, and impacts of the provisions implementing the EGRRCPA as compared to the state of the world prior to when the EGRRCPA took effect. The Bureau believes such a pre-statute baseline provides the public and the Bureau a more complete picture of the impacts of the EGRRCPA changes that were implemented by the Bureau's 2018 HMDA Rule and would be further implemented by the relevant provisions in this proposed rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>151</SU>
                             The Bureau has discretion in any rulemaking to choose an appropriate scope of analysis with respect to potential benefits, costs, and impacts and an appropriate baseline. In the 2018 HMDA Rule, the Bureau noted that it anticipated an upcoming notice-and-comment rulemaking and expected that the accompanying analysis under Dodd-Frank Act section 1022(b) would assess the benefits, costs, and impacts of the statute as well as the implementing regulation. 83 FR 45325, 45332 n.57 (Sept. 7, 2018).
                        </P>
                    </FTNT>
                    <P>The second set of provisions in this proposed rule would increase the closed-end loan coverage threshold from 25 originations to either 50 or 100 originations in each of the two preceding calendar years. Because the EGRRCPA predates this proposed provision, and the burden reduction from this provision, if adopted, would be in addition to, and would not replace the burden reduction for financial institutions already implemented under the EGRRCPA, the Bureau believes the appropriate baseline for this provision is a post-EGRRCPA world in which eligible financial institutions under the EGRRCPA are already partially exempt from the reporting of certain data points for closed-end mortgages.</P>
                    <P>The third set of provisions in this proposed rule would extend for two years, until January 1, 2022, the current temporary threshold for reporting data about open-end lines of credit of 500 open-end lines of credit in each of the two preceding calendar years, and set the permanent threshold for reporting data about open-end lines of credit at 200 open-end lines of credit in each of the two preceding calendar years when the temporary threshold expires. In the 2017 HMDA Rule, the Bureau granted two-year temporary relief (specifically, for 2018 and 2019) for financial institutions that originate fewer than 500 open-end lines of credit in either of the two preceding calendar years. The 2017 HMDA Rule provides that, absent any future rulemaking, the open-end coverage threshold will revert to 100 open-end lines of credit, as in the 2015 HMDA Rule, starting in 2020. This proposed rule proposes to extend the current temporary coverage threshold for open-end lines of credit of 500 for two more years (specifically, 2020 and 2021) and then set the coverage threshold for open-end lines of credit at 200 permanently.</P>
                    <P>Meanwhile, the EGRRCPA's partial exemption for open-end lines of credit of eligible insured depository institutions and insured credit unions took effect on May 24, 2018. Because the temporary increase in the open-end coverage threshold adopted in the 2017 HMDA Rule would automatically expire without this or other rulemaking effort and some insured depository institutions and insured credit unions are now eligible for a partial exemption for open-end lines of credit, for the consideration of benefits and costs of this provision the Bureau is adopting a baseline in which the open-end coverage threshold starting in year 2020 is reset at 100 open-end lines of credit in each of the two preceding calendar years with some depository institutions and credit unions partially exempt under the EGRRCPA.</P>
                    <HD SOURCE="HD2">C. Coverage of the Proposed Rule</HD>
                    <P>
                        Each set of proposed provisions applies to certain financial institutions and relieves these financial institutions from HMDA's requirements for either all or certain data points regarding closed-
                        <PRTPAGE P="20998"/>
                        end mortgage loans or open-end lines of credit that they originate or purchase, or for which they receive applications, as described further in each section below. In short, the implementation of the EGRRCPA would affect certain insured depository institutions and insured credit unions with origination volumes below certain thresholds, while the rest of the proposed rule would affect all financial institutions below certain thresholds and not just insured depository institutions and insured credit unions.
                    </P>
                    <HD SOURCE="HD2">D. Basic Approach of the Bureau's Consideration of Benefits and Costs and Data Limitations</HD>
                    <P>This discussion relies on data that the Bureau has obtained from industry, other regulatory agencies, and publicly available sources. However, as discussed further below, the Bureau's ability to fully quantify the potential costs, benefits, and impacts of this proposed rule is limited in some instances by a scarcity of necessary data.</P>
                    <HD SOURCE="HD3">1. Benefits to Covered Persons</HD>
                    <P>This proposed rule relates to which financial institutions, transactions, and data points are exempted or excluded from HMDA's reporting requirements. All three sets of provisions in this proposed rule are designed to reduce the regulatory burdens on covered persons while maintaining sufficient HMDA data to serve the statute's purposes. Therefore, the benefits of these proposed provisions to covered persons are mainly the reduction of the costs to covered persons relative to the compliance costs the covered persons would have to incur under each baseline scenario. The costs to covered persons and others derive from the diminished availability of data to address the statutory purposes of HMDA.</P>
                    <P>
                        The Bureau's 2015 HMDA Rule, as well as the 2014 proposed rule for the 2015 HMDA Rule and the material provided to the Small Business Review Panel leading to the 2015 HMDA Rule, presented a basic framework of analyzing compliance costs for HMDA reporting, including ongoing costs and one-time costs of financial institutions. Based on the Bureau's study of the HMDA compliance process and costs, with the help of additional information gathered and verified through the Small Business Review Panel process, the Bureau classified the operational activities that financial institutions use for HMDA data collection and reporting into 18 discrete compliance “tasks” which can be grouped into four “primary tasks.” 
                        <SU>152</SU>
                        <FTREF/>
                         Recognizing that the cost per loan of complying with HMDA's requirements differs by financial institution, the Bureau further identified seven key dimensions of compliance operations that were significant drivers of compliance costs, including the reporting system used, the degree of system integration, the degree of system automation, the compliance program, and the tools for geocoding, performing completeness checks, and editing. The Bureau found that financial institutions tended to have similar levels of complexity in compliance operations across all seven dimensions. For example, if a given financial institution had less system integration, then it tended to use less automation and less complex tools for geocoding. Financial institutions generally did not use less complex approaches on one dimension and more complex approaches on another. The small entity representatives validated this perspective during the Small Business Review Panel meeting convened under the Small Business Regulatory Enforcement Fairness Act.
                        <SU>153</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>152</SU>
                             These tasks include: (1) Data collection: Transcribing data, resolving reportability questions, and transferring data to HMDA Management System (HMS); (2) Reporting and resubmission: Geocoding, standard annual edit and internal checks, researching questions, resolving question responses, checking post-submission edits, filing post-submission documents, creating modified loan/application register, distributing modified loan/application register, distributing disclosure statement, and using vendor HMS software; (3) Compliance and internal audits: Training, internal audits, and external audits; and (4) HMDA-related exams: Examination preparation and examination assistance.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>153</SU>
                             
                            <E T="03">See</E>
                             Bureau of Consumer Fin. Prot., “Final Report of the Small Business Review Panel on the CFPB's Proposals Under Consideration for the Home Mortgage Disclosure Act (HMDA) Rulemaking” 22, 37 (Apr. 24, 2014), 
                            <E T="03">http://files.consumerfinance.gov/f/201407_cfpb_report_hmda_sbrefa.pdf.</E>
                        </P>
                    </FTNT>
                    <P>The Bureau realizes that costs vary by institution due to many factors, such as size, operational structure, and product complexity, and that this variance exists on a continuum that is impossible to fully represent. To consider costs in a practical and meaningful way, in the 2015 HMDA Rule the Bureau adopted an approach that focused on three representative tiers of financial institutions. In particular, to capture the relationships between operational complexity and compliance cost, the Bureau used these seven dimensions to define three broadly representative financial institutions according to the overall level of complexity of their compliance operations. Tier 1 denotes a representative financial institution with the highest level of complexity, tier 2 denotes a representative financial institution with a moderate level of complexity, and tier 3 denotes a representative financial institution with the lowest level of complexity. For each tier, the Bureau developed a separate set of assumptions and cost estimates.</P>
                    <P>
                        Table 1 below provides an overview of all three representative tiers across the seven dimensions of compliance operations: 
                        <SU>154</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>154</SU>
                             The Bureau notes this description has taken into account the operational improvements the Bureau has implemented regarding HMDA reporting since issuing the 2015 HMDA Rule and differs slightly from the original taxonomy in the 2015 HMDA Rule that reflected the technology at the time of the study.
                        </P>
                    </FTNT>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="xs90,r100,r100,r100">
                        <TTITLE>
                            Table 1—Types of HMDA Reporters 
                            <SU>1</SU>
                        </TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1" O="L">Tier 3 FIs tend to . . .</CHED>
                            <CHED H="1" O="L">Tier 2 FIs tend to . . .</CHED>
                            <CHED H="1" O="L">Tier 1 FIs tend to . . .</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Systems</ENT>
                            <ENT>Enter data in Excel LAR Formatting Tool</ENT>
                            <ENT>Use LOS and HMS; Submit data via the HMDA Platform</ENT>
                            <ENT>Use multiple LOS, central SoR, HMS; Submit data via the HMDA Platform.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Integration</ENT>
                            <ENT>(None)</ENT>
                            <ENT>Have forward integration (LOS to HMS)</ENT>
                            <ENT>Have backward and forward integration; Integration with public HMDA APIs.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Automation</ENT>
                            <ENT>Manually enter data into LAR Formatting Tool; review and verify edits in the HMDA Platform</ENT>
                            <ENT>LAR file produced by HMS; review edits in HMS and HMDA platform; verify edits via HMDA Platform</ENT>
                            <ENT>LAR file produced by HMS; high automation compiling file and reviewing edits; verify edits via the HMDA platform.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="20999"/>
                            <ENT I="01">Geocoding</ENT>
                            <ENT>Use FFIEC tool (manual)</ENT>
                            <ENT>Use batch processing</ENT>
                            <ENT>Use batch processing with multiple sources.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Completeness Checks</ENT>
                            <ENT>Check in HMDA Platform only</ENT>
                            <ENT>Use LOS, which includes completeness checks</ENT>
                            <ENT>Use multiple stages of checks.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Edits</ENT>
                            <ENT>Use FFIEC Edits only</ENT>
                            <ENT>Use FFIEC and customized edits</ENT>
                            <ENT>Use FFIEC and customized edits run multiple times.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Compliance Program</ENT>
                            <ENT>Have a joint compliance and audit office</ENT>
                            <ENT>Have basic internal and external accuracy audit</ENT>
                            <ENT>Have in-depth accuracy and fair lending audit.</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             FI is “financial institution”; LOS is “Loan Origination System”; HMS is “HMDA Data Management Software”; SoR is “System of Record.”
                        </TNOTE>
                    </GPOTABLE>
                    <P>For a representative institution in each tier, in the 2015 HMDA Rule, the Bureau produced a series of estimates of the costs of compliance, including the ongoing costs that financial institutions incurred prior to the implementation of the 2015 HMDA Rule, and the changes to the ongoing costs due to the 2015 HMDA Rule. The Bureau further provided the breakdown of the changes to the ongoing costs due to each major provision in the 2015 HMDA Rule, which includes the changes to the scope of the institutional coverage, the change to the scope of the transactional coverage, the revisions to the existing data points (as before the 2015 HMDA Rule) and the addition of new data points by the 2015 HMDA Rule.</P>
                    <P>For the impact analysis in this proposed rule, the Bureau is utilizing the cost estimates provided in the 2015 HMDA Rule for the representative financial institution in each of the three tiers, with some updates, mainly to reflect the inflation rate, and in the case of the set of provisions implementing the partial exemptions under the EGRRCPA, to align the partially exempt data points (and data fields used to report these data points) with the cost impact analyses discussed in the impact analyses for the 2015 HMDA Rule. The Bureau's analyses below also take into account the operational improvements that have been implemented by the Bureau regarding HMDA reporting since the issuance of the 2015 HMDA Rule. The details of such analyses are contained in the following sections addressing all three major sets of provisions of this proposed rule. The Bureau emphasizes that through the issuance of this proposal it is soliciting information relating to the costs financial institutions incurred in collecting and reporting 2018 data in compliance with the 2015 HMDA Rule and that such information may be valuable in estimating costs in the Dodd-Frank Act section 1022(b) analysis issued with the final rule.</P>
                    <P>
                        The next step of the Bureau's consideration of the reduction of costs for covered persons involved aggregating the institution-level estimates of the cost reduction under each set of proposed provisions up to the market-level. This aggregation required estimates of the total number of potentially impacted financial institutions and the total number of loan/application register records by those potentially impacted institutions. The Bureau used a wide range of data in conducting this task, including recent HMDA data,
                        <SU>155</SU>
                        <FTREF/>
                         Call Reports, and Consumer Credit Panel data. These analyses were challenging, because no single data source provided complete coverage of all the financial institutions that could be impacted and because there is varying data quality among the different sources.
                    </P>
                    <FTNT>
                        <P>
                            <SU>155</SU>
                             The majority of the analyses in this section were conducted prior to the official submission deadline of the 2018 HMDA data on March 1, 2019. As of the date of the issuance of this proposed rule, the modified HMDA aggregate file is not ready for public release, as the Bureau is still processing the 2018 HMDA loan/application register submissions and checking data quality. Some financial institutions are continuing to revise and resubmit their 2018 HMDA data, and the modified loan/application register for 2018, which was first made public on March 29, 2019, will be updated on a rolling basis for resubmissions and subject to change. The Bureau intends to review the 2018 HMDA data more closely in connection with this rulemaking once the 2018 submissions are more complete. The most recent year of HMDA data the Bureau has used for these analyses is from the 2017 HMDA data. The Bureau notes the market may fluctuate from year to year and the Bureau's rulemaking is not geared towards such transitory changes on an annual basis. The Bureau does not expect large differences from these estimates had the 2018 HMDA data been used for this cost-benefit analysis, because the Bureau has considered past years' data and taken into account other market data in its estimates.
                        </P>
                    </FTNT>
                    <P>
                        To perform the aggregation, the Bureau mapped the potentially impacted financial institutions to the three tiers described above. For each of the three major proposed provisions analyzed, the Bureau assumed none of the proposed changes would affect the high-complexity tier 1 reporters. The Bureau then assigned the potentially impacted financial institutions to either tier 2 or tier 3. In doing so, the Bureau relied on two constraints: (1) The estimated number of impacted institutions in tiers 2 and 3, combined, must equal the estimated number of impacted institutions for the applicable provision, and (2) the number of loan/application register records submitted annually by the impacted financial institutions in tiers 2 and 3, combined, must equal the estimated number of loan/application register records for the applicable provision. As in the 2015 HMDA Rule, the Bureau assumed for closed-end reporting that a representative low-complexity, tier 3 financial institution has 50 closed-end mortgage loan HMDA loan/application register records per year and a representative tier 2 financial institution has 1,000 closed-end mortgage loan HMDA loan/application register records per year. Similarly, the Bureau assumed for open-end reporting that a representative low-complexity, tier 3 financial institution has 150 open-end HMDA loan/application register records per year and a representative tier 2 financial institution has 1,000 open-end HMDA loan/application register records per year. Constraining the total number of impacted institutions and the number of impacted loan/application register records across tier 2 and tier 3 to the aggregate estimates thus enables the Bureau to calculate the approximate numbers of impacted institutions in tiers 2 and 3 for each set of provisions.
                        <SU>156</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>156</SU>
                             
                            <E T="03">See supra</E>
                             note 72.
                        </P>
                    </FTNT>
                    <P>Multiplying the impact estimates for representative financial institutions in each tier by the estimated number of impacted institutions, the Bureau arrived at the market-level estimates.</P>
                    <HD SOURCE="HD3">2. Costs to Covered Persons</HD>
                    <P>
                        In general all three sets of provisions in this proposed rule, if adopted, would reduce the ongoing costs associated with HMDA reporting for the affected covered persons. The set of provisions relating to the open-end thresholds would also delay for two additional years the one-time costs that excluded 
                        <PRTPAGE P="21000"/>
                        institutions would otherwise incur if the 500 open-end coverage threshold were restored to 100 open-end lines of credit in 2020 absent this proposed rule. Those proposed provisions would also ultimately remove the one-time costs for excluded institutions that originated fewer than 200 open-end lines of credit but more than 100 open-end lines of credit in either of the two preceding calendar years starting in 2022. In the interim, it is possible that to adapt to the rule, covered persons may incur certain one-time costs. Such one-time costs are mostly related to training and system changes in covered persons' HMDA reporting/loan origination systems. Based on the Bureau's outreach to industry, however, the Bureau believes that such one-time costs are fairly small.
                    </P>
                    <HD SOURCE="HD3">3. Benefits to Consumers</HD>
                    <P>
                        Having generated estimates of the changes in ongoing costs and one-time costs to covered financial institutions, the Bureau then can attempt to estimate the potential pass-through of such cost reduction from these institutions to consumers, which could benefit consumers. According to economic theory, in a perfectly competitive market where financial institutions are profit maximizers, the affected financial institutions would pass on to consumers the marginal, 
                        <E T="03">i.e.,</E>
                         variable, cost savings per application or origination, and absorb the one-time and increased fixed costs of complying with the rule. The Bureau estimated in the 2015 HMDA Rule the impacts on the variable costs of the representative financial institutions in each tier due to various provisions of that rule. Similarly, the estimates of the pass-through effect from covered persons to consumers due to the provisions under this proposed rule are based on the relevant estimates of the changes to the variable costs in the 2015 HMDA Rule with some updates. The Bureau notes that the market structure in the consumer mortgage lending markets may differ from that of a perfectly competitive market in which case the pass-through to the consumers would most likely be smaller than the pass-through under the perfect competition assumption. The Bureau seeks additional comments on the potential pass-through from financial institutions to consumers due to the reduction in reporting costs.
                    </P>
                    <HD SOURCE="HD3">4. Cost to Consumers</HD>
                    <P>
                        HMDA is a sunshine statute. The purposes of HMDA are to provide the public with loan data that can be used: (i) To help determine whether financial institutions are serving the housing needs of their communities; (ii) to assist public officials in distributing public-sector investment so as to attract private investment to areas where it is needed; and (iii) to assist in identifying possible discriminatory lending patterns and enforcing antidiscrimination statutes.
                        <SU>157</SU>
                        <FTREF/>
                         The provisions in this proposed rule, if adopted, would lessen the reporting requirements for eligible financial institutions by either completely relieving them of the obligation to report all data points related to closed-end mortgage loans or open-end lines of credit or by implementing the partial exemptions from reporting certain data points for certain transactions for some covered persons as provided by the EGRRCPA. As a sunshine statute regarding data reporting and disclosure, most of the benefits of HMDA are realized indirectly. With less data required to be collected and reported under HMDA, the HMDA data available to serve HMDA's statutory purposes would decline.
                        <SU>158</SU>
                        <FTREF/>
                         However, to quantify the reduction of such benefits to consumers presents substantial challenges. The Bureau seeks comment on the magnitude of the loss of HMDA benefits from these changes to the available data and/or methodologies for measuring these effects.
                    </P>
                    <FTNT>
                        <P>
                            <SU>157</SU>
                             12 CFR 1003.1(b).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>158</SU>
                             The changes in this proposal would generally either relieve financial institutions from their reporting requirements under Regulation C or implement the reduction in the data fields required to be reported for certain transactions of certain financial institutions as provided by the EGRRCPA. The data fields covered by the EGRRCPA include information about the type of loans and the types of borrowers applying for and being granted credit, which can help determine whether financial institutions are serving the housing needs of their communities and assist in identifying possible discriminatory lending patterns and enforcing antidiscrimination statutes. Similarly, raising the reporting thresholds so that fewer institutions report data would reduce the public information regarding whether financial institutions are serving the needs of their communities. To the extent that these data are used for other purposes, the loss of data could result in other costs.
                        </P>
                    </FTNT>
                    <P>Because quantifying and monetizing benefits of HMDA to consumers would require identifying all possible uses of HMDA data, establishing causal links to the resulting public benefits, and then quantifying the magnitude of these benefits, the Bureau mostly presented qualitative analyses regarding HMDA benefits in the 2015 HMDA Rule. For instance, quantification would require measuring the impact of increased transparency on financial institution behavior, the need for public and private investment, the housing needs of communities, the number of financial institutions potentially engaging in discriminatory or predatory behavior, and the number of consumers currently being unfairly disadvantaged and the level of quantifiable damage from such disadvantage. Similarly for the impact analyses of this proposed rule, the Bureau is unable to readily quantify the loss of some of the HMDA benefits to consumers with precision, both because the Bureau does not have the data to quantify all HMDA benefits and because the Bureau is not able to assess completely how this proposed rule will reduce those benefits.</P>
                    <P>
                        In light of these data limitations, the discussion below generally provides a qualitative consideration of the costs, 
                        <E T="03">i.e.,</E>
                         the potential loss of HMDA benefits to consumers from the proposed rule. The Bureau seeks comment on the appropriateness of the approach described above, including additional data relevant to the benefits and costs to consumers and covered persons.
                    </P>
                    <HD SOURCE="HD2">E. Potential Benefits and Costs to Consumers and Covered Persons</HD>
                    <HD SOURCE="HD3">1. Overall Summary</HD>
                    <P>In this section, the Bureau presents a concise, high-level table summarizing the benefits and costs considered in the remainder of the discussion. This table is not intended to capture all details and nuances that are provided both in the rest of the analysis and in the section-by-section discussion above, but rather to provide an overview of the major benefits and costs of the proposed rule, including the provisions to be analyzed, the baseline chosen for each set of provisions, the sub-provisions to be analyzed, the actual or proposed implementation dates of the sub-provisions, the annual savings on the operational costs of covered persons due to the sub-provision, the changes to the one-time costs of covered persons due to the sub-provision, and generally how the proposed provisions affect HMDA's benefits.</P>
                    <GPH SPAN="3" DEEP="344">
                        <PRTPAGE P="21001"/>
                        <GID>EP13MY19.000</GID>
                    </GPH>
                    <HD SOURCE="HD3">2. Provisions To Implement the EGRRCPA</HD>
                    <HD SOURCE="HD3">Scope of the Provisions</HD>
                    <P>
                        The proposed rule would incorporate the 2018 HMDA Rule into Regulation C and further implement the EGRRCPA provision that adds partial exemptions from HMDA's requirements for certain insured depository institutions and insured credit unions.
                        <SU>159</SU>
                        <FTREF/>
                         With respect to closed-end mortgage loans, HMDA section 304(i)(1) as amended by the EGRRCPA provides that, if an insured depository institution or insured credit union originated fewer than 500 closed-end mortgage loans in each of the two preceding calendar years, the insured depository institution or insured credit union is generally exempt from reporting certain data points on the closed-end mortgage loans that it would have otherwise reported under HMDA. Similarly, with respect to open-end lines of credit, HMDA section 304(i)(1) as amended by the EGRRCPA provides that, if an insured depository institution or insured credit union originated fewer than 500 open-end lines of credit in each of the two preceding calendar years, the insured depository institution or insured credit union is generally exempt from reporting certain data points on the open-end lines of credit that it would have otherwise reported under HMDA.
                        <SU>160</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>159</SU>
                             For purposes of HMDA section 104, the EGRRCPA provides that the term “insured credit union” has the meaning given the term in section 101 of the Federal Credit Union Act, 12 U.S.C. 1752, and the term “insured depository institution” has the meaning given the term in section 3 of the Federal Deposit Insurance Act, 12 U.S.C. 1813.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>160</SU>
                             Notwithstanding the new partial exemptions, new HMDA section 304(i)(3) provides that an insured depository institution must comply with HMDA section 304(b)(5) and (6) if it has received a rating of “needs to improve record of meeting community credit needs” during each of its two most recent examinations or a rating of “substantial noncompliance in meeting community credit needs” on its most recent examination under section 807(b)(2) of the CRA.
                        </P>
                    </FTNT>
                    <P>
                        For the closed-end mortgage loans, after applying all current HMDA reporting requirements, including Regulation C's existing complete exclusion for institutions that originated fewer than 25 closed-end mortgage loans in either of the two preceding calendar years, the Bureau estimates that section 104(a) of the EGRRCPA, as implemented by the 2018 HMDA Rule and further implemented by this proposed rule, provides a partial exemption with respect to collection, recording, and reporting of 2018 HMDA data to approximately 3,300 institutions.
                        <SU>161</SU>
                        <FTREF/>
                         As a point of reference, 5,852 institutions reported 2017 HMDA data. The Bureau estimates that the insured depository institutions and insured credit unions that are eligible for a partial exemption for some or all of their covered loans and applications consist of about 56 percent of all reporting institutions, and 63 percent of all depository institutions and credit unions that reported HMDA data for 2017. The Bureau estimates that the total number of closed-end mortgage loans originated by these partially 
                        <PRTPAGE P="21002"/>
                        exempt institutions would be about 531,000 per year.
                    </P>
                    <FTNT>
                        <P>
                            <SU>161</SU>
                             To generate this estimate, the Bureau first identified all depository institutions (including credit unions) that met all reporting requirements and reported 2017 HMDA data in 2018. From this set of depository institutions, the Bureau then excluded all depository institutions that do not have to report 2018 HMDA data in 2019 because they originated fewer than 25 closed-end mortgage loans in either 2016 or 2017. Of the remaining depository institutions, approximately 3,300 originated fewer than 500 closed-end mortgage loans in each of 2016 and 2017. For purposes of this estimate, the Bureau assumes that these institutions are insured, do not have a less than satisfactory CRA examination history, and thus estimates that they are partially exempt.
                        </P>
                    </FTNT>
                    <P>For the open-end lines of credit, the 2017 HMDA Rule grants a complete exclusion for two years (specifically, 2018 and 2019) for open-end lines of credit for all institutions that originated fewer than 500 open-end lines of credit in either of the two preceding calendar years. As such, insured depository institutions or insured credit unions that originated fewer than 500 open-end lines of credit in each of the two preceding calendar years and are partially exempt under the EGRRCPA are already completely excluded from HMDA's requirements for open-end lines of credit during 2018 and 2019 under the 2017 HMDA Rule. In other words, for the years 2018 to 2019, the partial exemption regarding open-end lines of credit under the EGRRCPA would have no immediate effects given the 2017 HMDA Rule.</P>
                    <P>The 2017 HMDA Rule provides that, absent any future rulemaking, the open-end coverage threshold will revert to 100 open-end lines of credit as established in the 2015 HMDA Rule, starting in 2020. Therefore, with the 2017 HMDA Rule and pre-EGRRCPA as the baseline, the effects of the EGRRCPA on open-end reporting would manifest starting in 2020. The Bureau estimates that, by 2020, about 595 insured depository institutions or credit unions would have been required to report open-end lines of credit at the 100 open-end coverage threshold and are eligible for a partial exemption under the EGRRCPA. This is before this proposed rule's proposal to extend the coverage threshold for open-end lines of credit at 500 for calendar years 2020 and 2021 and set the coverage threshold for open-end lines of credit at 200 starting in 2022, which is analyzed separately in another section.</P>
                    <HD SOURCE="HD3">Benefits to Covered Persons</HD>
                    <HD SOURCE="HD3">Partial Exemption for Closed-End Mortgage Loans</HD>
                    <P>The partial exemption for closed-end mortgage loans in the EGRRCPA that would be implemented by this proposed rule conveys a direct benefit to the covered persons who are eligible for such exemption by reducing the ongoing costs of having to report certain data points that were previously required.</P>
                    <P>
                        The Bureau's 2015 HMDA Rule and 2017 HMDA Rule, which define the rules under the baseline for the analyses of this set of provisions, require financial institutions to report a total of 48 data points beginning with the data collected in 2018 and reported in 2019. These data points contain 110 data fields.
                        <SU>162</SU>
                        <FTREF/>
                         The EGRRCPA grants partial exemptions for certain transactions of eligible financial institutions from reporting 26 of the 48 data points, which consist of 54 of the 110 data fields. Because this proposed rule would require insured depository institutions and insured credit unions to provide a NULI if they opt not to report a ULI for a partially exempt transaction, the actual reduction in the number of data fields that financial institutions need to report for partially exempt transactions would be 53. In addition, even though property address is a partially exempt data point, financial institutions must still report the State in which the property that secures the covered loan (or, in the case of an application, is proposed to secure the loan) is located for partially exempt transactions, because State is an individual data point that is not exempt under the EGRRCPA in addition to being one of the data fields associated with property address, which is exempt under the EGRRCPA. Therefore the total number of data fields that the eligible covered person must report for a partially exempt transaction would be reduced by 52.
                    </P>
                    <FTNT>
                        <P>
                            <SU>162</SU>
                             
                            <E T="03">See</E>
                             FFIEC, “Filing Instructions Guide for HMDA Data Collected in 2019,” at 13-65 (Oct. 2018), 
                            <E T="03">https://s3.amazonaws.com/cfpb-hmda-public/prod/help/2019-hmda-fig.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        With the exception of denial reasons (which were previously optionally reported prior to the 2015 HMDA Rule, except that certain financial institutions supervised by the OCC and the FDIC were required to report denial reasons) and rate spread, all of the data points (and data fields) that are partially exempt under the EGRRCPA as implemented by the 2018 HMDA Rule and this proposal correspond to data points (and data fields) that the Bureau added to the HMDA reporting as mandated by the Dodd-Frank Act or with the Bureau's discretionary authority granted under the Dodd-Frank Act.
                        <SU>163</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>163</SU>
                             On the other hand, as explained in the section-by-section analysis of § 1003(d)(1)(i) in part IV above, age and number of units are not partially exempt under the EGRRCPA even though they were added to Regulation C in the 2015 HMDA Rule.
                        </P>
                    </FTNT>
                    <P>
                        The analysis under section 1022(b) of the Dodd-Frank Act in the 2015 HMDA Rule noted that the Bureau was adding 50 new data fields with new data points that previously did not exist under Regulation C. To estimate the costs that financial institutions would incur in collecting and reporting these data, the Bureau used a cost-accounting, case-study methodology which involved an extensive set of interviews with financial institutions and their vendors through which the Bureau identified 18 component tasks involved in collecting and reporting HMDA data and estimated the number of person-hours required and the costs of each task for institutions of various levels of complexity. The Bureau augmented this information through the Small Business Review Panel process and through notice and comment on its proposed cost estimates, as well as through a review of academic literature and public data. Based on the information gathered in this process, the Bureau estimated that the impact of the additional 50 data fields on annual operational costs of covered person for closed-end reporting would be approximately $2,100, $10,900, and $31,000 per year for representative tier 3, tier 2, and tier 1 financial institutions, respectively, after accounting for the operational improvements that the Bureau was planning to implement regarding how the Bureau receives and processes submitted data.
                        <SU>164</SU>
                        <FTREF/>
                         Since issuing the 2015 HMDA Rule, the Bureau has modernized the HMDA submission system, improved its regulatory HMDA help functions, and made other operational changes that were initially discussed in the impact analyses of the 2015 HMDA Rule. The Bureau has not obtained new information with respect to the component tasks or costs set forth in the 2015 HMDA Rule. Therefore, it is reasonable to adopt these cost estimates, which reflect the operational improvements described in the 2015 HMDA Rule, with certain adjustments that reflect the newly proposed rule. To do so, the Bureau takes the 2015 estimates on the annual ongoing costs associated with the new additional data points added in the 2015 HMDA Rule, prorates the amount to account for the reduced number of data fields required due to the EGRRCPA partial exemptions, adjusts those for inflation, and arrives at a set of estimates for the savings on the operational costs due to the partial exemptions for representative firms in each of the three tiers.
                        <FTREF/>
                        <SU>165</SU>
                          
                        <PRTPAGE P="21003"/>
                        Specifically the Bureau estimates that the savings on annual operational costs from not reporting the 52 data fields for closed-end mortgage loans that are exempt under the EGRRCPA and this proposed rule would be approximately $2,300, $11,900, and $33,900 per year for representative tier 3, tier 2, and tier 1 financial institutions that are eligible for the partial exemption. The Bureau specifically requests information relating to the costs financial institutions incurred in collecting and reporting 2018 data in compliance with the 2015 HMDA Rule that may be valuable in estimating costs in the Dodd-Frank Act section 1022(b) analysis issued with the final rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>164</SU>
                             For example, the Bureau planned to create a web-based submission tool with automated edit checks and to otherwise streamline the submission and editing process to make it more efficient for filers. In addition, the Bureau planned to consolidate the outlets for assistance, provide implementation support, and improve points of contact processes for help inquiries. These changes were implemented in 2018 for the 2017 filing year. The Bureau has received feedback from reporting entities on the new systems, which generally indicate substantial costs savings.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>165</SU>
                             The Bureau used a wage rate of $33 per hour in its 2015 HMDA Rule impact analyses, which is the national average wage for compliance officers based on the National Compensation Survey from the Bureau of Labor Statistics in May 2014. The 
                            <PRTPAGE/>
                            May 2017 National Compensation Survey reported an average wage rate for compliance officers of $34.39. The Bureau has used a wage rate of $34 for the impact analyses for the proposed rule.
                        </P>
                    </FTNT>
                    <P>In the 2015 HMDA Rule, the Bureau assumed a representative low-complexity, tier 3 financial institution that reports closed-end mortgage loans had 50 HMDA loan/application register records per year, a representative medium-complexity, tier 2 financial institution had 1,000 HMDA loan/application register records per year, while a high-complexity, tier 1 financial institution had 50,000 HMDA loan/application register records per year. The partial exemption for closed-end mortgage loans granted under the EGRRCPA and implemented by this proposed rule only applies to insured depository institutions and insured credit unions that originated less than 500 closed-end mortgage loans in each of the two preceding calendar years prior to the HMDA collection year. Given that and the Bureau's characterization of representative financial institutions in the three tiers, the Bureau believes that none of the tier 1 institutions are partially exempt for closed-end reporting. Some of the estimated 3,300 partially exempt covered persons would be low-complexity/tier 3 institutions, while some would belong to tier 2. The Bureau estimates that approximately 2,640 institutions eligible for the partial exemption from closed-end reporting are similar to the representative tier 3 financial institutions and approximately 660 eligible institutions belong to tier 2. Based on these counts, the Bureau estimates that the aggregate savings in ongoing costs for covered persons due to the EGRRCPA's partial exemption from closed-end reporting would be approximately $13.9 million annually.</P>
                    <HD SOURCE="HD3">Partial Exemption for Open-End Lines of Credit</HD>
                    <P>
                        Starting in 2020,
                        <SU>166</SU>
                        <FTREF/>
                         absent the changes to the open-end coverage threshold in this proposal, which will be analyzed separately, the partial exemption for open-end lines of credit in the EGRRCPA that would be implemented by this proposed rule would convey a direct benefit to covered persons who are eligible for such exemption by reducing the ongoing costs of having to report certain data points that were previously required.
                    </P>
                    <FTNT>
                        <P>
                            <SU>166</SU>
                             As noted above, for the years 2018 and 2019, the partial exemption regarding open-end lines of credit would have no immediate effects given the temporary coverage threshold of 500 open-end lines of credit established in the 2017 HMDA Rule.
                        </P>
                    </FTNT>
                    <P>In the impact analysis of the 2015 HMDA Rule, the Bureau estimated that, accounting for the Bureau's planned operational improvements, the estimated impact of the 2015 HMDA Rule on ongoing operational costs on open-end reporters would be approximately $8,600, $43,400, and $273,000 per year, for representative low-, moderate-, and high-complexity financial institutions, respectively. The Bureau takes such 2015 estimates on the annual ongoing costs associated with open-end reporting, prorates the amount to account for the reduced number of data fields required due to the EGRRCPA partial exemption, adjusts those for inflation, and arrives at a set of estimates for the savings on the operational costs of reporting information on open-end lines of credit due to the partial exemption for representative firms in each of the three tiers. Specifically the Bureau estimates that the impact on the savings on annual operational costs from not reporting the 52 data fields for open-end mortgage loans that are exempt under the EGRRCPA would be approximately $4,500, $22,800, and $144,000 per year for representative tier 3, tier 2, and tier 1 open-end reporting financial institutions that are eligible for the partial exemption.</P>
                    <P>The Bureau estimates that, absent the changes to the open-end coverage in this proposal, about 595 financial institutions would be partially exempt from reporting certain data points on open-end lines of credit under the EGRRCPA. According to the Bureau's estimates, about 545 of those 595 partially-exempt open-end reporters are low-complexity tier 3 open-end reporters, about 50 are moderate-complexity tier 2 open-end reporters, and none are high-complexity tier 1 reporters. Using these estimates, the Bureau estimates that by granting a partial exemption to most insured depository institutions and insured credit unions that originate fewer than 500 open-end lines of credit in each of two preceding years, absent the proposed changes in the open-end coverage threshold in this proposal that would take effect starting in 2020, the EGRRCPA would provide an aggregate reduction in operational costs associated with open-end lines of credit for eligible financial institutions of about $3.6 million per year. The Bureau notes that these impacts would not begin until 2020, given the temporary provisions in the 2017 HMDA Rule.</P>
                    <HD SOURCE="HD3">Costs to Covered Persons</HD>
                    <P>It is possible that, like any new regulation or revision to the existing regulations, financial institutions would incur certain one-time costs adapting to the changes of the proposed rule. Based on the Bureau's early outreach to stakeholders, the Bureau understands that most such one-time costs would result from interpreting and implementing the regulatory changes, but not from purchasing software upgrades or turning off the existing reporting functionality that the eligible institutions already built or purchased prior to the EGRRCPA taking effect.</P>
                    <P>The Bureau seeks comment on any costs to eligible financial institutions associated with the proposals relating to the incorporation of the EGRRCPA into Regulation C.</P>
                    <HD SOURCE="HD3">Benefits to Consumers</HD>
                    <P>
                        Having generated estimates of the reduction in ongoing costs for closed-end mortgage loans on financial institutions due to the EGRRCPA partial exemption for closed-end mortgage loans implemented in this proposed rule, the Bureau can estimate the potential pass-through of such cost reduction from these institutions to consumers,
                        <SU>167</SU>
                        <FTREF/>
                         which could benefit consumers. According to economic theory, in a perfectly competitive market where financial institutions are profit maximizers, the affected financial institutions would pass on to consumers the marginal, 
                        <E T="03">i.e.,</E>
                         variable, cost savings per application or origination, and 
                        <PRTPAGE P="21004"/>
                        absorb the one-time and increased fixed costs of complying with the rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>167</SU>
                             Note that throughout this cost-benefit analysis, the Bureau discusses such pass-through in order to present a complete picture of the benefits that are the result of the proposal. However, such pass-through from the financial institution to consumers as a result of the proposal is a direct flow from the savings to the financial institutions, and should not be interpreted as a gain in addition to the savings to the financial institutions from a general equilibrium perspective for the calculation of total social benefit.
                        </P>
                    </FTNT>
                    <P>
                        The Bureau estimated in the 2015 HMDA Rule that the 50 data fields of the new data points required under the 2015 HMDA Rule would add variable costs per application for closed-end mortgage loans of approximately $22 for a representative tier 3 financial institution, $0.62 for a representative tier 2 financial institution, and $0.05 for a representative tier 1 financial institution.
                        <SU>168</SU>
                        <FTREF/>
                         As explained above, the partial exemption in the EGRRCPA and this proposed rule will reduce the number of data fields that have to be reported by 52 and almost all those partially exempt data fields correspond to data fields for new data points added by the 2015 HMDA Rule. Adjusting these figures to account for the difference in the number of the data fields that are partially exempt under the EGRRCPA and the number of data fields of new data points added by the 2015 HMDA Rule, and adjusting for inflation, the Bureau estimates that the partial exemption under the EGRRCPA and this proposed rule would reduce the variable cost per closed-end mortgage loan application for a representative tier 3 financial institution by about $24 and for a representative tier 2 financial institution by about $0.68. This potential reduction in the expense facing consumers when applying for a closed-end mortgage will be amortized over the life of the loan and represents a very small decrease in the cost of a mortgage loan. Therefore, the Bureau does not anticipate any material effect on credit access in the long or short term if financial institutions pass on these cost savings to consumers.
                    </P>
                    <FTNT>
                        <P>
                            <SU>168</SU>
                             80 FR 66128, 66291 (Oct. 28, 2015).
                        </P>
                    </FTNT>
                    <P>Similarly, having generated estimates of the reduction in ongoing costs for open-end mortgage loans on financial institutions due to the EGRRCPA partial exemption for open-end lines of credit implemented in this proposed rule, the Bureau can estimate the potential pass-through of such cost reduction from these institutions to consumers, which could benefit consumers.</P>
                    <P>The Bureau estimated in the 2015 HMDA Rule that the rule would increase variable costs by $41.50 per open-end line of credit application for representative low-complexity institutions and $6.20 per open-end line of credit application for representative moderate-complexity institutions. Accounting for the difference in the number of the data fields that are partially exempt under the EGRRCPA and the total number of data fields that comprise all data points under the 2015 HMDA Rule, and adjusting for inflation, the Bureau estimates that the partial exemption under the EGRRCPA and this proposed rule would reduce the variable cost per open-end line of credit application for a representative tier 3 financial institution by about $22 and for a representative tier 2 financial institution by about $3. These savings on the variable costs by the partially-exempt open-end reporters could potentially be passed through to consumers, under the assumption of a perfectly competitive market with profit maximizing firms. These expenses will be amortized over the life of a loan and represent a very small amount relative to the cost of a mortgage loan. The Bureau notes that the market structure in the consumer mortgage lending market may differ from that of a perfectly competitive market in which case the pass-through to the consumers would most likely be smaller than the pass-through under the perfect competition assumption. Therefore, the Bureau does not anticipate any material effect on credit access in the long or short term even if financial institutions pass on these reduced costs to consumers.</P>
                    <HD SOURCE="HD3">Costs to Consumers</HD>
                    <P>The partial exemptions under the EGRRCPA and further implemented through this proposed rule remove the reporting requirements for 26 data points for certain transactions of eligible insured depository institutions and insured credit unions. As a result, regulators, public officials, and members of the public will lose some insights into the credit offered by these partially exempt institutions and overall credit in the communities they serve. The decreased insight into partially exempt financial institutions may lead to adverse outcomes for some consumers. For instance, some of the exempt data points could have helped the regulators and public officials better understand the type of funds that are flowing from lenders to consumers and the needs of consumers for mortgage credit. Additionally, some exempt data points could improve the processes used to identify possible discriminatory lending patterns and enforce antidiscrimination statutes. In addition, without the exempt data regarding, for example, underwriting and pricing, some lenders with low fair lending risk may be initially misidentified as high risk, potentially increasing their associated compliance burden. Finally, to the extent that some covered persons may use the information reported by other financial institutions for market research purposes, the partial exemptions may potentially lead to less vigorous competition from these institutions.</P>
                    <HD SOURCE="HD3">3. Provisions To Increase the Closed-End Coverage Threshold</HD>
                    <HD SOURCE="HD3">Scope of the Provisions</HD>
                    <P>This proposal would increase the thresholds for reporting data about closed-end mortgage loans so that financial institutions originating fewer than either 50 closed-end mortgage loans, or alternatively 100 closed-end mortgage loans, in either of the two preceding calendar years would be excluded from HMDA's requirements for closed-end mortgage loans starting in 2020.</P>
                    <P>The 2015 HMDA Rule requires institutions that originated at least 25 closed-end mortgage loans in each of the two preceding calendar years and meet all other reporting criteria to report their closed-end mortgage applications and loans. The EGRRCPA provides a partial exemption for insured depository institutions and insured credit unions that originated fewer than 500 closed-end mortgage loans in each of the two preceding years. This proposed rule contains provisions that incorporate the 2018 HMDA Rule into Regulation C and further implement the EGRRCPA. The previous section in this impact analysis specifically addresses the partial exemptions under the EGRRCPA. This section considers increasing the closed-end loan coverage threshold to either 50 or 100 so that only financial institutions that originated at least 50 or 100 closed-end mortgage loans in each of the two preceding years must report data on their closed-end mortgage applications and loans under HMDA.</P>
                    <P>
                        Using data from various sources, including past HMDA submissions, Call Reports, Credit Union Call Reports, Summary of Deposits, and the National Information Center (NIC), the Bureau applied all current HMDA reporting requirements, including Regulation C's existing complete regulatory exclusion for institutions that originated fewer than 25 closed-end mortgage loans in either of the two preceding calendar years, and estimates that currently there are about 4,960 financial institutions required to report their closed-end mortgage loans and applications under HMDA. Together, these financial institutions originated about 7.0 million closed-end mortgage loans in calendar year 2017. The Bureau observes that the total number of financial institutions that were engaged in closed-mortgage lending in 2017, regardless of whether they met all HMDA reporting criteria, is 
                        <PRTPAGE P="21005"/>
                        about 12,700, and the total number of closed-end mortgage originations in 2017 was about 8.2 million. In other words, under the current 25 closed-end loan coverage threshold, about 39 percent of all mortgage lenders are required to report HMDA data, and they account for about 85.6 percent of all closed-end mortgage originations in the country. The Bureau estimates that among those 4,960 financial institutions that are currently required to report closed-end mortgage loans under HMDA, about 3,300 insured depository institutions and insured credit unions are partially exempt for closed-end mortgage loans under the EGRRCPA and the 2018 HMDA Rule, and thus are not required to report a subset of the data points currently required by Regulation C for these transactions.
                    </P>
                    <HD SOURCE="HD3">Alternative 1: 50 Closed-End Coverage Threshold</HD>
                    <P>The Bureau estimates that if the closed-end loan coverage threshold were increased to 50, under one of the two options proposed in this proposed rule, the total number of financial institutions that would be required to report closed-end mortgages would drop to about 4,200, a decrease of about 760 financial institutions compared to the current level. These 760 newly excluded institutions originated about 37,000 closed-end mortgage loans in 2017. There would be about 6.98 million closed-end mortgage originations reported under the 50 closed-end loan coverage threshold, which would account for about 85.1 percent of all closed-end mortgage loan originations in the entire mortgage market.</P>
                    <P>
                        The Bureau further estimates that all but about 20 
                        <SU>169</SU>
                        <FTREF/>
                         of the 760 newly excluded closed-end mortgage reporters under the proposed 50 closed-end loan coverage threshold would be eligible for a partial exemption for closed-end mortgage loans as provided by the EGRRCPA and the 2018 HMDA Rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>169</SU>
                             Those financial institutions either had a closed-end loan origination volume of 500 or more in at least one of the preceding two calendar years or are not insured depository institutions or insured credit unions, and therefore are not eligible for a partial exemption for closed-end mortgage loans as provided by the EGRRCPA and the 2018 HMDA Rule.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Alternative 2: 100 Closed-End Coverage Threshold</HD>
                    <P>The Bureau estimates that if the closed-end loan coverage threshold were increased to 100, as another of the two options proposed in this proposed rule, the total number of financial institutions that would be required to report closed-end mortgages would drop to about 3,240, a decrease of about 1,720 financial institutions compared to the current level. These 1,720 newly excluded institutions originated about 147,000 closed-end mortgage loans in 2017. There would be about 6.87 million closed-end mortgage loan originations reported under the 100 closed-end loan coverage threshold, which would account for about 83.7 percent of all closed-end mortgage originations in the entire mortgage market.</P>
                    <P>The Bureau further estimates that all but about 50 of the 1,720 newly excluded closed-end mortgage loan reporters that would be excluded under the proposed 100 closed-end coverage threshold would be eligible for a partial exemption for closed-end mortgage loans as provided by the EGRRCPA and the 2018 HMDA Rule.</P>
                    <P>
                        Table 3 below shows the Bureau's estimates of the number of closed-end reporters that would be required to report under various potential thresholds, and the number of closed-end originations reported by these financial institutions, both in total and broken down by the type of financial institution and HMDA submission agency as was done in the 2015 HMDA Rule.
                        <SU>170</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>170</SU>
                             Regulation C applies to financial institutions as defined in § 1003.2(g) and requires a financial institution to submit data to the appropriate Federal agency for the financial institution. 
                            <E T="03">See</E>
                             12 CFR 1003.1(c); 1003.5(a). (Nondepository institutions generally designate HUD as their appropriate Federal agency, while depository institutions and their subsidiaries designate one of the other federal regulators as their appropriate Federal agency.) For more information about determining the appropriate Federal agency for a financial institution, 
                            <E T="03">see</E>
                             § 1003.5(a)(4). The numbers in tables 3 and 4 reflect the estimated number of institutions that would designate each agency as their appropriate Federal agency for data submission under Regulation C (
                            <E T="03">see</E>
                             § 1003.5(a)(3)(iv)). These tables are limited to that narrow purpose and do not attempt to determine whether any of these institutions may otherwise be subject to the rulemaking, supervisory, or enforcement authorities of multiple regulators.
                        </P>
                    </FTNT>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s25,12,12,12">
                        <TTITLE>Table 3</TTITLE>
                        <BOXHD>
                            <CHED H="1">Agency</CHED>
                            <CHED H="1">Closed-End Reporting Threshold</CHED>
                            <CHED H="2">&gt;=25</CHED>
                            <CHED H="2">&gt;=50</CHED>
                            <CHED H="2">&gt;=100</CHED>
                        </BOXHD>
                        <ROW EXPSTB="03" RUL="s">
                            <ENT I="21">
                                <E T="02">Number of Reporting Financial Institutions by Submission Agency</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Total</ENT>
                            <ENT>4,960</ENT>
                            <ENT>4,201</ENT>
                            <ENT>3,242</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CFPB</ENT>
                            <ENT>107</ENT>
                            <ENT>105</ENT>
                            <ENT>101</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FDIC</ENT>
                            <ENT>1,769</ENT>
                            <ENT>1,442</ENT>
                            <ENT>1,039</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FRS</ENT>
                            <ENT>441</ENT>
                            <ENT>378</ENT>
                            <ENT>298</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">NCUA</ENT>
                            <ENT>1,329</ENT>
                            <ENT>1,073</ENT>
                            <ENT>764</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">OCC</ENT>
                            <ENT>617</ENT>
                            <ENT>520</ENT>
                            <ENT>379</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">HUD</ENT>
                            <ENT>697</ENT>
                            <ENT>683</ENT>
                            <ENT>661</ENT>
                        </ROW>
                        <ROW EXPSTB="03" RUL="s">
                            <ENT I="21">
                                <E T="02">Number of Reported Loans (in 1000's) by Submission Agency</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Total</ENT>
                            <ENT>7,019</ENT>
                            <ENT>6,982</ENT>
                            <ENT>6,872</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CFPB</ENT>
                            <ENT>1,693</ENT>
                            <ENT>1,693</ENT>
                            <ENT>1,669</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FDIC</ENT>
                            <ENT>763</ENT>
                            <ENT>748</ENT>
                            <ENT>713</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">FRS</ENT>
                            <ENT>260</ENT>
                            <ENT>258</ENT>
                            <ENT>250</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">NCUA</ENT>
                            <ENT>562</ENT>
                            <ENT>548</ENT>
                            <ENT>519</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">OCC</ENT>
                            <ENT>300</ENT>
                            <ENT>295</ENT>
                            <ENT>283</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">HUD</ENT>
                            <ENT>3,440</ENT>
                            <ENT>3,439</ENT>
                            <ENT>3,437</ENT>
                        </ROW>
                    </GPOTABLE>
                    <PRTPAGE P="21006"/>
                    <HD SOURCE="HD3">Benefits to Covered Persons</HD>
                    <P>The complete exclusion from closed-end mortgage reporting for institutions that originated fewer than 50 or 100 closed-end mortgage loans in either of the two preceding calendar years, as proposed in this proposed rule, would convey a direct benefit to the covered persons who are eligible for such exclusion by reducing the ongoing costs of having to report closed-end mortgage loans and applications that were previously required.</P>
                    <P>
                        In the impact analysis of the 2015 HMDA Rule, prior to the adoption of the changes in the 2015 HMDA Rule and implementation of the Bureau's operational improvements, the Bureau estimated that the annual operational costs for financial institutions of reporting under HMDA were approximately $2,500 for a representative low-complexity financial institution with a loan/application register size of 50 records; $35,600 for a representative moderate-complexity financial institution with a loan/application register size of 1,000 records; and $313,000 for a representative high-complexity financial institution with a loan/application register size of 50,000 records. The Bureau estimated that accounting for the operational improvements, the net impact of the 2015 HMDA Rule on ongoing operational costs for closed-end reporters would be approximately $1,900, $7,800, and $20,000 
                        <SU>171</SU>
                        <FTREF/>
                         per year, for representative low-, moderate-, and high-complexity financial institutions, respectively. This means that with all components of the 2015 HMDA Rule implemented and accounting for the Bureau's operational improvements, the estimated annual operational costs for closed-end mortgage reporting would be approximately $4,400 for a representative tier 3 reporter, $43,400 for a representative tier 2 reporter, and $333,000 for a representative tier 1 reporter. Updating these numbers with inflation, the Bureau estimates that if a financial institution is required to report under the 2015 HMDA Rule and is not partially exempt under the EGRRCPA, 
                        <E T="03">i.e.,</E>
                         it must report all data points specified in Regulation C for its closed-end mortgage loans, the savings on the annual operational costs from not reporting any closed-end mortgage data if it were completely excluded under one of two proposed loan thresholds, would be approximately $4,500 for a representative low-complexity tier 3 institution, $44,700 for a representative moderate-complexity tier 2 institution, and $343,000 for a representative high-complexity tier 1 institution. On the other hand, as explained in the previous section, the Bureau estimates that had a financial institution been eligible for a partial exemption on its closed-end mortgage loans under the EGRRCPA and 2018 HMDA Rule, the annual savings in the ongoing costs from the partial exemption alone would be approximately $2,300 for a representative tier 3 institution, $11,900 for a representative tier 2 institution and $33,900 for a representative tier 1 institution. Therefore, the Bureau estimates that if a financial institution is required to report under the 2015 HMDA Rule, but is partially exempt under the EGRRCPA, 
                        <E T="03">i.e.,</E>
                         it only needs to report a subset of all Regulation C data points for its closed-end mortgage loans, the savings in the annual operational costs from not reporting any closed-end mortgage data, if it is completely excluded, would be approximately $2,200 for a representative low-complexity tier 3 institution, $32,800 for a representative moderate-complexity tier 2 institution, and $309,000 for a representative high-complexity tier 1 institution. These estimates have already been adjusted for inflation.
                    </P>
                    <FTNT>
                        <P>
                            <SU>171</SU>
                             This does not include the costs of quarterly reporting for financial institutions that have annual origination volume greater than 60,000. Those quarterly reporters are all high-complexity tier 1 institutions, and the Bureau estimates none of the quarterly reporters would be excluded under this proposal.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">Alternative 1: 50 Closed-End Coverage Threshold</HD>
                    <P>Using the methodology discussed above in part VI.D.1, the Bureau estimates that with the proposed 50 closed-end coverage threshold, about 760 institutions would be completely excluded from reporting closed-end mortgage data compared to the current level. All but about 20 of these 760 institutions would be eligible for a partial exemption under the EGRRCPA and the 2018 HMDA Rule.</P>
                    <P>The Bureau estimates that, of the approximately 740 financial institutions that are (1) required to report closed-end mortgages under the 2015 HMDA Rule, (2) partially exempt under the EGRRCPA, and (3) completely excluded under the proposed 50 loan threshold, about 727 are similar to the representative low-complexity tier 3 institution and about 13 are similar to the representative moderate-complexity tier 2 institution. Of the approximately 20 remaining financial institutions that are required to report closed-end mortgages under the 2015 HMDA Rule and are not partially exempt under the EGRRCPA but would be completely excluded under the proposed 50 closed-end coverage threshold, about 19 are similar to the representative low-complexity tier 3 institution and only one is similar to the representative moderate-complexity tier 2 institution.</P>
                    <P>Based on the estimates of the savings of annual ongoing costs for closed-end reporting per representative institution, grouped by whether or not it is partially exempt for closed-end reporting under the EGRRCPA, and the estimated tier distribution of these institutions that would be excluded under the proposed 50 closed-end loan coverage threshold, the Bureau estimates that, the total savings in annual ongoing costs from HMDA reporting by fully excluded institutions that are already partially exempt under the EGRRCPA would be about $2 million, and the total savings in the annual ongoing costs from HMDA reporting by fully excluded firms that previously were not eligible for a partial exemption under the EGRRCPA would be about $140,000. Together the annual savings in the operational costs of firms excluded under the proposed 50 closed-end loan coverage threshold would be about $2.2 million.</P>
                    <HD SOURCE="HD3">Alternative 2: 100 Closed-End Coverage Threshold</HD>
                    <P>Using methodology discussed above in part VI.D.1, the Bureau estimates that with the proposed 100 closed-end coverage threshold, about 1,720 institutions would be completely excluded from reporting closed-end mortgage data compared to the current level. All but about 50 of the 1,720 would be eligible for the partial exemption for closed-end mortgage loans under the EGRRCPA and the 2018 HMDA Rule.</P>
                    <P>
                        The Bureau estimates that, of the approximately 1,670 institutions that are (1) required to report closed-end mortgage loans under the 2015 HMDA Rule, (2) partially exempt under the EGRRCPA, and (3) completely excluded under the proposed 100 closed-end coverage threshold, about 1,540 are similar to the representative low-complexity tier 3 institution and about 130 are similar to the representative moderate-complexity tier 2 institution. Of the approximately 50 remaining institutions that are required to report closed-end mortgage data under the 2015 HMDA Rule and are not partially exempt under the EGRRCPA but would be completely excluded under the proposed 100 closed-end coverage threshold, about 45 are similar to the representative low-complexity tier 3 institution and only five are similar to the representative moderate-complexity tier 2 institution.
                        <PRTPAGE P="21007"/>
                    </P>
                    <P>Based on the estimates of the savings of annual ongoing costs for closed-end reporting per representative institution, grouped by whether or not it is partially exempt under the EGRRCPA, and the estimated tier distribution of these financial institutions that would be excluded under the proposed 100 closed-end loan coverage threshold, the Bureau estimates that, the total savings in the annual ongoing costs from HMDA reporting by excluded firms that are already partially exempt for closed-end mortgage loans under the EGRRCPA would be about $7.7 million, and the total savings in the annual ongoing costs from HMDA reporting by fully excluded firms that are not eligible for a partial exemption under the EGRRCPA would be about $400,000. Together the annual savings in the operational costs of firms newly excluded under the proposed 100 closed-end coverage threshold would be about $8.1 million.</P>
                    <HD SOURCE="HD3">Costs to Covered Persons</HD>
                    <P>It is possible that, like any new regulation or revision to an existing regulation, financial institutions would incur certain one-time costs adapting to the changes to the regulation. Based on the Bureau's early outreach to stakeholders, the Bureau understands that most of these one-time costs consists of interpreting and implementing the regulatory changes and not from purchasing software upgrades or turning off the existing reporting functionality that the newly excluded institutions already built or purchased prior to the new changes taking effect.</P>
                    <P>The Bureau seeks comments on any costs to institutions that would be newly excluded under either of the alternative proposed increases to the closed-end coverage threshold.</P>
                    <HD SOURCE="HD3">Benefits to Consumers</HD>
                    <P>
                        Having generated estimates of the reduction in ongoing costs on covered financial institutions due to the proposed increase in the closed-end loan coverage threshold, the Bureau then attempts to estimate the potential pass-through of such cost reduction from these institutions to consumers, which could benefit consumers. According to economic theory, in a perfectly competitive market where financial institutions are profit maximizers, the affected financial institutions would pass on to consumers the marginal, 
                        <E T="03">i.e.,</E>
                         variable, cost savings per application or origination, and absorb the one-time and increased fixed costs of complying with the rule.
                    </P>
                    <P>The Bureau estimated in the 2015 HMDA Rule that the final rule would increase variable costs by $23 per closed-end mortgage application for representative low-complexity institutions and $0.20 per closed-end mortgage application for representative moderate-complexity institutions. The Bureau estimated that prior to the 2015 HMDA Rule, the variable costs of HMDA reporting were about $18 per closed-end mortgage application for representative low-complexity institutions, $6 per closed-end mortgage application for representative moderate-complexity institutions, and $3 per closed-end mortgage application for representative high-complexity institutions. Adjusting for inflation, the Bureau estimates the savings on the variable cost per closed-end application for a representative tier 3 financial institution that is not partially exempt under the EGRRCPA but excluded from closed-end reporting under this proposal would be about $42 per application; the savings on the variable cost per application for a representative tier 2 financial institution that is not partially exempt under the EGRRCPA but excluded from closed-end reporting under this proposal would be about $6.40 per application.</P>
                    <P>The Bureau estimates that the partial exemption for closed-end mortgage loans under the EGRRCPA for eligible insured depository institutions and insured credit unions would reduce the variable costs of HMDA reporting by approximately $24 per closed-end mortgage application for representative low-complexity institutions, $0.68 per closed-end mortgage application for representative moderate-complexity institutions, and $0.05 per closed-end mortgage application for representative high-complexity institutions. The savings on the variable cost per application for a representative tier 3 financial institution that is partially exempt under the EGRRCPA and fully excluded from closed-end reporting under this proposal would be about $18.30 per application. The savings on the variable cost per application for a representative tier 2 financial institution that is partially exempt under the EGRRCPA and fully excluded from closed-end reporting under this proposal would be about $5.70 per application. These are the cost reductions that excluded institutions under this proposed rule might pass through to their consumers and assuming the market is perfectly competitive. This potential reduction in the expense consumers face when applying for a mortgage would be amortized over the life of the loan and would represent a very small amount relative to the cost of a mortgage loan. The Bureau notes that the market structure in the consumer mortgage lending market may differ from that of a perfectly competitive market in which case the pass-through to the consumers would most likely be smaller than the pass-through under the perfect competition assumption. Therefore, the Bureau does not anticipate any material effect on credit access in the long or short term if financial institutions pass on these cost savings to consumers.</P>
                    <HD SOURCE="HD3">Costs to Consumers</HD>
                    <P>The proposed increase to the closed-end coverage threshold would relieve eligible financial institutions from the reporting requirements for all closed-end mortgage loans and applications. As a result, HMDA data on these institutions' closed-end mortgage loans and applications would no longer be available to regulators, public officials, and members of the public. The decreased insight into excluded institutions may lead to adverse outcomes for some consumers. For instance, HMDA data, if reported, could help regulators and public officials better understand the type of funds that are flowing from lenders to consumers and consumers' needs for mortgage credit. The data may also help improve the processes used to identify possible discriminatory lending patterns and enforce antidiscrimination statutes.</P>
                    <P>The Bureau recognizes that the costs to consumers would be higher if the closed-end coverage threshold were increased to 100 loans rather than if it were increased to 50 loans, but currently lacks sufficient data to quantify such loss other than the estimated numbers of covered loans and covered institutions under the two alternative proposed thresholds, as reported in Table 3. The Bureau seeks comment on the costs to consumers associated with the proposed alternative increases to the closed-end coverage threshold.</P>
                    <HD SOURCE="HD3">4. Provisions To Increase the Open-End Coverage Threshold</HD>
                    <HD SOURCE="HD3">Scope of the Provisions</HD>
                    <P>The proposed rule would extend the temporary open-end coverage threshold of 500 open-end lines of credit for two additional years (2020 and 2021), and permanently set the threshold for reporting data about open-end lines of credit at 200 open-end lines of credit in each of the preceding two calendar years starting in 2022.</P>
                    <P>
                        The 2015 HMDA Rule generally requires financial institutions that originated at least 100 open-end lines of 
                        <PRTPAGE P="21008"/>
                        credit in each of the two preceding years to report data about their open-end lines of credit and applications. The 2017 HMDA Rule temporarily increased the open-end coverage threshold to 500 for two years, meaning only financial institutions that originated at least 500 open-end lines of credit in each of the two preceding years are subject to HMDA's requirements for their open-end lines of credit for 2018 and 2019. The EGRRCPA generally provides a partial exemption for insured depository institutions and insured credit unions that originated less than 500 open-end lines of credit in each of the two preceding years. However, for 2018 and 2019, all insured depository institutions and insured credit unions that are granted a partial exemption for open-end lines of credit by the EGRRCPA are fully excluded from HMDA's requirements for their open-end lines of credit by the 2017 HMDA Rule. Absent any further changes via a rulemaking process, according to the 2015 HMDA Rule and the 2017 HMDA Rule, starting in 2020 the open-end coverage threshold will adjust to 100, and institutions that exceed the coverage threshold of 100 open-end lines of credit will be able to use the EGRRCPA's open-end partial exemption if they originated less than 500 open-end lines of credit in each of the two preceding years. Thus, the appropriate baseline for the consideration of benefits and costs of the proposed changes to the open-end coverage threshold, including the two-year extension of the temporary threshold of 500 open-end lines of credit and then setting the permanent threshold at 200 starting in 2022, is a situation starting in 2020 in which the open-end coverage threshold is set at 100 for each of two preceding years and the partial exemption with a threshold of 500 open-end lines of credit applies.
                    </P>
                    <P>
                        Because collection of data on open-end lines of credit only became mandatory starting in 2018 under the 2015 HMDA Rule and 2017 HMDA Rule, no single data source exists as of the time of this proposal that can accurately report the number of originations of open-end lines of credit in the entire market and by lender.
                        <SU>172</SU>
                        <FTREF/>
                         The Bureau therefore has used multiple data sources, including credit union Call Reports, Call Reports for banks and thrifts, HMDA data, and Consumer Credit Panel data, to develop estimates about open-end originations for lenders that offer open-end lines of credit and assess the impact of various thresholds on the numbers of reporters and market coverage under various scenarios.
                        <SU>173</SU>
                        <FTREF/>
                         The Table below provides estimates of coverage among all lenders that are active in the open-end line of credit market at various open-end coverage thresholds broken down by submission agency as was done in the 2015 HMDA Rule.
                        <SU>174</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>172</SU>
                             As discussed 
                            <E T="03">supra</E>
                             note 155, the most recent year of HMDA data the Bureau has used for these analyses is the 2017 HMDA data. The Bureau intends to review the 2018 HMDA data more closely in connection with this rulemaking once the 2018 submissions are more complete. The 2018 HMDA data is the first year where open-end lines of credit were required to be reported, unlike in previous years when open-end lines of credit were reported only voluntarily. Even so, the Bureau does not expect large differences from these estimates had the 2018 HMDA data been used for this cost-benefit analysis, because the Bureau has taken into account other market data in its estimates.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>173</SU>
                             In general, credit union Call Reports provide the number of originations of open-end lines of credit secured by real estate but exclude lines of credit in the first-lien status. Call Reports for banks and thrifts report only the balance of the home-equity lines of credit at the end of the reporting period but not the number of originations in the period.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>174</SU>
                             
                            <E T="03">See supra</E>
                             note 170.
                        </P>
                    </FTNT>
                    <GPH SPAN="3" DEEP="499">
                        <PRTPAGE P="21009"/>
                        <GID>EP13MY19.001</GID>
                    </GPH>
                    <P>The Bureau estimates that there were about 1.59 million open-end lines of credit originated in 2017 by about 6,615 lenders. Under the temporary 500 open-end line of credit coverage threshold set in the 2017 HMDA Rule, there would be about 1.23 million open-end lines of credit reported by about 333 financial institutions. This would represent about 77.4 percent of all originations and 5 percent of all lenders in the open-end line of credit market. In comparison, if the open-end coverage threshold were set at 100, the Bureau estimates that the number of reporters would be about 1,014, who in total originate about 1.41 million open-end lines of credit, representing about 88.7 percent of all originations and 15.3 percent of all lenders in the market. In other words, if the coverage threshold is increased to 500 for another two years (in 2020 and 2021) as proposed by this proposed rule, in comparison to the default baseline where the threshold is set at 100 in 2020, the Bureau estimates that the number of institutions affected would be about 681, who in total originated about 177,000 open-end lines of credit. Among those 681 open-end lines of credit lenders, the Bureau estimates that about 618 already qualify for a partial exemption for their open-end lines of credit under the EGRRCPA and in total they originate about 136,000 open-end lines of credit.</P>
                    <P>
                        If the permanent open-end line of credit coverage threshold is set at 200, for 2022 and beyond, as proposed, the Bureau estimates there would be about 1.34 million open-end lines of credit reported by about 613 reporters. In terms of market coverage, this would represent about 84.2 percent of all originations and 9.2 percent of all lenders in the open-end line of credit market. In other words, if the coverage threshold is increased to 200 for year 
                        <PRTPAGE P="21010"/>
                        2022 and beyond as proposed, in comparison to a baseline threshold set at 100, the Bureau estimates that 401 reporters, who in total originated about 69,000 open-end lines of credit, would be affected. Among the 401 institutions that the 200 loan threshold would completely exclude, the Bureau estimates that about 378 already qualify for a partial exemption for their open-end lines of credit under the EGRRCPA and in total they originate about 61,000 open-end lines of credit.
                    </P>
                    <HD SOURCE="HD3">Benefits to Covered Persons</HD>
                    <P>The proposed extension of the temporary open-end coverage threshold of 500 for two additional years, as compared to having the threshold adjust to 100, conveys a direct benefit to covered persons that originated fewer than 500 open-end lines of credit in either of the two preceding years but originated no less than 100 open-end lines of credit in each of the two preceding years in reducing the ongoing costs associated with open-end lines of credit during 2020 and 2021.</P>
                    <P>In the impact analysis of the 2015 HMDA Rule, the Bureau estimated that, accounting for Bureau's planned operational improvements, the ongoing operational costs on open-end reporters for all data points required under the 2015 HMDA Rule would be approximately $8,600, $43,400, and $273,000 per year, for representative low-, moderate-, and high-complexity financial institutions, respectively. Adjusting for inflation, this is equivalent to approximately $8,800, $44,700, and $281,100 per year currently. On the other hand, accounting for the reduced number of required data points and inflation, the Bureau now estimates that the ongoing costs of open-end reporting would be about $4,300, $21,900, and $138,000 per year, for representative low-, moderate-, and high-complexity financial institutions, respectively that are eligible for a partial exemption for open-end lines of credit under the EGRRCPA.</P>
                    <P>The Bureau estimates that, with the proposed coverage threshold increased to 500 as compared to reverting to 100 for 2020 and 2021, about 681 financial institutions would be excluded from reporting open-end lines of credit during the two years. About 618 of those 681 financial institutions would be eligible for the partial exemption for open-end lines of credit under the EGRRCPA and further implemented by the 2018 HMDA Rule and this proposed rule if adopted, and about 63 of them would not have been eligible for the partial exemption for open-end lines of credit because in one of the preceding two years their open-end origination volume exceeded 500. Of the 618 institutions that are already eligible for a partial exemption under the EGRRCPA but would be fully excluded for two additional years from open-end reporting by this proposed rule, the Bureau estimates that about 567 are low-complexity tier 3 open-end reporters, about 51 are moderate-complexity tier 2 open-end reporters, and none are high-complexity tier 1 reporters. In addition, of the 63 institutions that are not eligible for the partial exemption under the EGRRCPA but would be fully excluded for two additional years from open-end reporting by this proposed rule, the Bureau estimates that about 26 are low-complexity tier 3 open-end reporters, about 37 are moderate-complexity tier 2 open-end reporters, and none are high-complexity tier 1 reporters. Using the estimates of savings on ongoing costs for open-end lines of credit for representative financial institutions, grouped by whether the lender is already eligible for the partial exemption under the EGRRCPA, as described above, the Bureau estimates that by extending the temporary 500 open-end coverage threshold for two years, the eligible financial institutions that are already partially exempt under the EGRRCPA would receive an aggregate reduction in operational cost associated with open-end lines of credit of about $3.5 million per year in the years 2020 and 2021, while the eligible financial institutions that are not already partially exempt under the EGRRCPA would receive an aggregate reduction in operational cost associated with open-end lines of credit of about $2.1 million per year in the years 2020 and 2021. In total extending the 500 loan threshold for two additional years would result in operational cost savings of about $5.6 million per year in the years 2020 and 2021.</P>
                    <P>The proposed increase of the permanent open-end coverage threshold to 200 open-end lines of credit in each of the two preceding calendar years starting in 2022, as compared to having the threshold adjust to 100, conveys a direct benefit to covered persons that originated fewer than 200 open-end lines of credit in either of the two preceding years but originated no less than 100 open-end lines of credit in each of the two preceding years in reducing the ongoing costs of having to report their open-end lines of credit.</P>
                    <P>The Bureau estimates that, with the proposed coverage threshold increased to 200 as compared to reverting to 100 starting in 2022, about 401 financial institutions would be excluded from reporting open-end lines of credit starting in 2022. About 378 of those 401 financial institutions are eligible for the partial exemption for open-end lines of credit under the EGRRCPA, and about 23 of them are not eligible for the partial exemption for open-end lines of credit because in one of the preceding two years its open-end origination volume exceeded 500. Of the 378 institutions that are already partially exempt under the EGRRCPA but would be fully excluded from open-end reporting starting in 2022 under the proposal, the Bureau estimates that about 373 are low-complexity tier 3 open-end reporters, about five are moderate-complexity tier 2 open-end reporters, and none are high-complexity tier 1 reporters. In addition, of the 23 institutions that are not eligible for the partial exemption under the EGRRCPA but would be fully excluded from open-end reporting starting in 2022 by this proposed rule, the Bureau estimates that about 18 are low-complexity tier 3 open-end reporters, about five are moderate-complexity tier 2 open-end reporters, and none are high-complexity tier 1 reporters. Using the estimates of savings on ongoing costs for open-end lines of credit for representative financial institutions, grouped by whether the lender is already eligible for the partial exemption under the EGRRCPA, as described above, the Bureau estimates that by raising the open-end coverage threshold to 200 open-end lines of credit starting in 2022, the eligible financial institutions that are already partially exempt under the EGRRCPA would receive an aggregate reduction in operational cost associated with open-end lines of credit of about $1.7 million per year starting in 2022, while the eligible financial institutions that are not already partially exempt under the EGRRCPA would receive an aggregate reduction in operational cost associated with open-end lines of credit of about $38,000 per year starting in 2022. In total, increasing the open-end threshold from 100 to 200 would result in savings on the operational costs associated with open-end lines of credit of about $2.1 million per year starting in 2022.</P>
                    <P>
                        The proposed increase of the open-end coverage threshold to 200 starting in calendar year 2022, as compared to having the threshold adjust to 100, would also convey a direct benefit to covered persons that originated fewer than 200 open-end lines of credit in either of the two preceding years but originated no less than 100 open-end lines of credit in each of the two preceding years in removing the one-time costs of having to report their open-end lines of credit, had the 
                        <PRTPAGE P="21011"/>
                        reporting threshold adjusted to 100 according to the 2017 HMDA Rule.
                    </P>
                    <P>It is the Bureau's understanding that most of the financial institutions that were temporarily excluded for 2018 and 2019 under the 2017 HMDA rule have not fully prepared for open-end reporting because they are waiting for the Bureau to decide on the open-end reporting threshold that would apply after the temporary threshold of 500 loans expires in 2020. Under the baseline in this impact analysis, absent this proposed rule, those financial institutions would have to start reporting their open-end lines of credit starting in 2020, and hence incur one-time costs to create processes and systems for open-end lines of credit. The proposed extension of the 500 open-end coverage threshold for 2020 and 2021 in this proposal would delay incurrence of such one-time costs for two more years. If the second proposal to increase the open-end threshold to 200 starting in 2022 is not finalized, financial institutions that originated fewer than 200 open-end lines of credit in either of the two preceding years but originated no less than 100 open-end lines of credit in each of the two preceding years would eventually incur one-time costs of having to report their open-end lines of credit, once the reporting threshold reverted to the permanent threshold of 100.</P>
                    <P>As noted in the 2015 HMDA Rule, the Bureau recognizes that many financial institutions, especially larger and more complex institutions, process applications for open-end lines of credit in their consumer lending departments using procedures, policies, and data systems separate from those used for closed-end loans.</P>
                    <P>In the 2015 HMDA Rule, the Bureau assumed that the one-time costs for reporting information on open-end lines of credit required under the Rule would be roughly equal to 50 percent of the one-time costs of reporting information on closed-end mortgages. This translates to one-time costs of about $400,000 and $125,000 for open-end reporting for representative high- and moderate-complexity financial institutions, respectively, that will be required to report open-end lines of credit while also reporting closed-end mortgage loans. This assumption accounted for the fact that reporting open-end lines of credit will require some new systems, extra start-up training, and new compliance procedures and manuals, while recognizing that some fixed, one-time costs would need to be incurred anyway in making systemic changes to bring institutions into compliance with Regulation C and could be shared with closed-end lines of business. The assumption was consistent with the Bureau's estimate that an overwhelming majority of open-end reporters would also be reporting simultaneously closed-end mortgage loans and applications. In the 2015 HMDA Rule, the Bureau also assumed that the additional one-time costs of open-end reporting would be relatively low for low-complexity financial institutions because they are less reliant on information technology systems for HMDA reporting and may process open-end lines of credit on the same system and in the same business unit as closed-end mortgage loans. Therefore, for low-complexity financial institutions, the Bureau had assumed that the additional one-time cost created by open-end reporting is minimal and is derived mostly from new training and procedures adopted for the overall changes in the 2015 HMDA Rule.</P>
                    <P>In the proposal leading to the 2015 HMDA Rule, the Bureau had asked for public comments and specific data regarding the one-time cost of reporting open-end lines of credit. Although some commenters provided generic feedback on the additional burden of reporting data on these products, very few provided specific estimates of the potential one-time costs of reporting open-end lines of credit. Since issuing the 2015 HMDA Rule, the Bureau has heard anecdotal reports that one-time costs to begin reporting information on open-end lines of credit could be higher than the Bureau's estimates in the 2015 HMDA Rule. The Bureau has reviewed the 2015 estimates and believes that the one-time cost estimates for open-end lines of credit provided in 2015, if applied to this proposed rule, would most likely be underestimates, for two reasons.</P>
                    <P>
                        First, in developing the one-time cost estimates for open-end lines of credit in the 2015 HMDA Rule, the Bureau had envisioned that there would be cost sharing between the line of business that conducts open-end lending and the line of business that conducts closed-end lending at the corporate level, as the implementation of open-end reporting that became mandatory under the 2015 HMDA Rule would coincide with the implementation of the changes to closed-end reporting under the 2015 HMDA Rule. For instance, the resources of the corporate compliance department and information technology department could be shared and utilized simultaneously across different lines of business within the same lender in its efforts to set up processes and systems adapting to the 2015 HMDA Rule. Therefore the Bureau assumed the one-time cost due to open-end reporting would be about one-half of the one-time costs due to closed-end reporting, in order to both reasonably count for the costs for open-end lines of credit and avoid double counting. However, the circumstances have somewhat changed due to the 2017 HMDA Rule and would be changed further under this proposed rule. The 2017 HMDA Rule temporarily increased the open-end lines of credit threshold from 100 to 500 for two years. This proposal would further extend the temporary threshold of 500 for two additional years. Thus, there would be a considerable lag between the implementation of closed-end reporting changes under the 2015 HMDA Rule and the implementation of mandatory open-end reporting for those open-end lenders that have been temporarily excluded under the 2017 HMDA Rule and would be excluded for two more years under the proposal, but would be required to comply with HMDA's requirements for their open-end lines of credit starting in 2022 with the proposed 200 origination threshold taking effect. As a result, the efficiency gain from one-time cost sharing between the closed-end and open-end reporting that was envisioned in the cost-benefit analysis of the 2015 HMDA Rule likely would not be applicable, if some of the temporarily excluded open-end reporters under the 2017 HMDA Rule and the proposal were to start preparing for open-end reporting several years after the implementation of closed-end changes. Therefore the Bureau now believes the one-time costs of starting reporting information on open-end lines of credit, if the financial institution is to start reporting open-end lines of credit in 2022 and beyond, would be higher than the Bureau's initial estimates of one-time costs of open-end reporting provided in the HMDA 2015 Rule. For this impact analysis, hence the Bureau assumes for a representative tier 2 open-end reporters, the one-time costs of starting open-end reporting in 2022 would be approximately equal to the one-time cost estimate for closed-end reporting that Bureau estimated in the 2015 HMDA Rule, instead of being about one half of the one-time cost estimate for closed-end reporting. This translates to about $250,000 per representative tier 2 open-end reporter, instead of $125,000 as the Bureau estimated in the 2015 HMDA Rule regarding the one-time costs of open-end reporting. This is the case regardless whether the open-end reporters also report closed-end mortgage loans under HMDA. The Bureau notes that the tier 2 financial institutions that would be permanently 
                        <PRTPAGE P="21012"/>
                        excluded from open-end reporting under this proposal would no longer have to incur such one-time costs, if it is adopted.
                    </P>
                    <P>Secondly, the delay in open-end reporting for those tier 3 financial institutions that originated between 100 and 499 open-end lines of credit in either of the two preceding years as the result of the 2017 HMDA Rule would mean that, those institution would have to restart the training process for staff directly responsible for open-end data collection reporting and update compliance procedures and manuals, if the open-end threshold is set to 100 starting in 2020, and incur a one-time cost. In the 2015 HMDA Rule, the Bureau estimated the total one-time cost estimate for low-complexity financial institutions would be approximately $3,000 regardless of whether the financial institution reports open-end lines of credit. Under this proposal, the Bureau assumes that the low-complexity financial institutions that would be completely excluded from open-end reporting hence would be able to avoid incurring a one-time cost of about $3,000.</P>
                    <P>The Bureau estimates that, with the proposed coverage threshold increased to 200 starting in 2022 as compared to reverting to 100, about 401 more institutions would be excluded from reporting open-end lines of credit starting in 2022. About 391 of those 401 institutions are low-complexity tier 3 open-end reporters, about 10 are moderate-complexity tier 2 open-end reporters, and none are high-complexity tier 1 reporters. Using the estimates of savings on one-time costs for open-end lines of credit for representative financial institutions discussed above, the Bureau estimates that with the proposed increase in the open-end coverage threshold to 200 starting in 2022, the eligible institutions would receive an aggregate savings in avoided one-time cost associated with open-end lines of credit of about $3.8 million.</P>
                    <HD SOURCE="HD3">Costs To Covered Persons</HD>
                    <P>It is possible that, like any new regulation or revision to the existing regulations, financial institutions may incur certain one-time costs adapting to the changes to the regulation. Based on the Bureau's early outreach to stakeholders, the Bureau understands that most of such one-time costs would result from interpreting and implementing the regulatory changes, but not from purchasing software upgrades or turning off the existing reporting functionality that the eligible institutions already built or purchased prior to the new changes taking its effect.</P>
                    <P>The Bureau seeks comment on the costs and benefits to institutions that would be excluded pursuant to the proposed increases to the open-end coverage threshold.</P>
                    <HD SOURCE="HD3">Benefits to Consumers</HD>
                    <P>
                        Having generated estimates of the reduction in ongoing costs on covered financial institutions due to the proposed temporary increase in the open-end coverage threshold, the Bureau then attempts to estimate the potential pass-through of such cost reduction from the lenders to consumers, which could benefit consumers. According to economic theory, in a perfectly competitive market where financial institutions are profit maximizers, the affected financial institutions would pass on to consumers the marginal, 
                        <E T="03">i.e.</E>
                         variable, cost savings per application or origination, and absorb the one-time and increased fixed costs of complying with the rule.
                    </P>
                    <P>The Bureau estimated in the 2015 HMDA Rule that the rule would increase variable costs by $41.50 per open-end line of credit application for representative low-complexity institutions and $6.20 per open-end line of credit application for representative moderate-complexity institutions. These savings on variable costs by the excluded open-end reporters could potentially be passed through to the consumers, if the market is perfectly competitive. These expenses will be amortized over the life of a loan and represent a negligible reduction in the cost of a mortgage loan. The Bureau notes that the market structure in the consumer mortgage lending market may differ from that of a perfectly competitive market in which case the pass-through to the consumers would most likely be smaller than the pass-through under the perfect competition assumption. Therefore, the Bureau does not anticipate any material effect on credit access in the long or short term even if financial institutions pass on these reduced costs to consumers.</P>
                    <HD SOURCE="HD3">Costs to Consumers</HD>
                    <P>The proposed extension of the temporary coverage threshold of 500 for open-end lines of credit for 2020 and 2021 and setting the proposed permanent open-end threshold at 200 starting in 2022 would reduce the open-end data submitted under HMDA. As a result, HMDA data on these institutions' open-end loans and applications would no longer be available to regulators, public officials, and members of the public. The decreased oversight over affected financial institutions may lead to adverse outcomes for some consumers. For instance, reporting data on open-end line of credit applications and originations and on certain demographic characteristics of applicants and borrowers could help the regulators and public officials better understand the type of funds that are flowing from lenders to consumers and consumers' need for mortgage credit. Open-end line of credit data that may be relevant to underwriting decisions may also help improve the processes used to identify possible discriminatory lending patterns and enforce antidiscrimination statutes.</P>
                    <HD SOURCE="HD2">F. Potential Specific Impacts of the Proposed Rule</HD>
                    <HD SOURCE="HD3">1. Depository Institutions and Credit Unions With $10 Billion or Less in Total Assets, as Described in Section 1026</HD>
                    <P>As discussed above, the proposed rule would incorporate the interpretations and procedures from the 2018 HMDA Rule into Regulation C and further implement section 104(a) of the EGRRCPA, which grants eligible financial institutions partial exemptions from HMDA's requirements for certain transactions; increase the threshold for reporting data about closed-end mortgage loans from 25 to either 50 or 100 originations in both of the preceding two calendar years; and extend for a period of two years the current temporary threshold for reporting data about open-end lines of credit of 500 open-end lines of credit and increase the permanent threshold for reporting data about open-end lines of credit from 100 to 200 open-end lines of credit in both of the preceding two calendar years starting in 2022.</P>
                    <P>All three sets of proposed provisions focus on burden reduction for smaller institutions. Therefore, the Bureau believes that the benefits of this proposed rule to depository institutions and credit unions with $10 billion or less in total assets will be similar to the benefit to creditors as a whole, as discussed above.</P>
                    <P>
                        Specifically the Bureau estimates that the reduction in annual operational costs from the partial exemption for closed-end reporting under the EGRRCPA and further implemented by the 2018 HMDA Rule and this proposed rule if adopted would be approximately $2,300, $11,900, and $33,900 per year for representative tier 3, tier 2, and tier 1 depository institutions and credit unions with $10 billion or less in total assets that are eligible for the partial exemptions of closed-end reporting. The Bureau estimates that all but about eight 
                        <PRTPAGE P="21013"/>
                        of the approximately 3,300 institutions that are eligible for the partial exemption from closed-end reporting are small depository institutions or credit unions with assets at or below $10 billion. About 2,672 of the partially-exempt closed-end reporting small depository institutions or credit unions are low-complexity tier 3 closed-end reporters, with the rest being moderate-complexity tier 2 closed-end reporters, and none are high-complexity tier 1 reporters. Based on these calculations, the Bureau estimates that the aggregate savings on ongoing costs for these institutions would be approximately $13.5 million annually.
                    </P>
                    <P>The Bureau estimates that the reduction in annual operational costs starting in calendar year 2020 from the partial exemption from open-end reporting under the EGRRCPA, absent the proposed open-end threshold changes, would be approximately $4,500, $22,800, and $144,000 per year for representative tier 3, tier 2, and tier 1 depository institutions and credit unions with $10 billion or less in total assets that are eligible for the partial exemptions of open-end reporting. The Bureau estimates that about 578 out of the 595 financial institutions that would be partially exempt from reporting certain data points on open-end lines of credit under the EGRRCPA are small depository institutions or credit unions with assets at or below $10 billion. According to the Bureau's estimates, about 531 of those 578 partially-exempt small depository institutions or credit union are low-complexity tier 3 open-end reporters, about 47 are moderate-complexity tier 2 open-end reporters, and none are high-complexity tier 1 reporters. Based on these counts, the Bureau estimates that the aggregate savings on ongoing costs for these small depository institutions or credit unions due to the partial exemption from open-end reporting would be approximately $3.5 million annually, starting in calendar year 2020.</P>
                    <P>For the closed-end coverage threshold proposed provision, the Bureau estimates that for depository institutions and credit unions with $10 billion in assets or less that would have been required to report under the 2015 HMDA Rule, and are not partially exempt under the EGRRCPA, the savings on the annual operational costs from being excluded from closed-end reporting under the proposal would be approximately $4,500 for a representative low-complexity tier 3 institution, $44,700 for a representative moderate-complexity tier 2 institution, and $343,000 for a representative high-complexity tier 1 institution that fall below the proposed coverage threshold of either 50 or 100, whichever is adopted in the final rule. For depository institutions and credit unions with $10 billion in assets or less that would have been required to report under the 2015 HMDA Rule, but are partially exempt under the EGRRCPA, the savings on the annual operational costs from not reporting any closed-end mortgage data under the proposal, would be approximately $2,200 for a representative low-complexity tier 3 institution, $32,800 for a representative moderate-complexity tier 2 institution, and $309,000 for a representative high-complexity tier 1 institution. The Bureau estimates that about 738 of the approximately 760 institutions that would be excluded from the proposed 50 loan closed-end reporting threshold are small depository institutions or credit unions with assets at or below $10 billion, and all but one of them are already partially exempt under the EGRRCPA and 2018 HMDA Rule. About 724 of them are similar to representative low-complexity tier 3 institution, with the rest being moderate-complexity tier 2 institutions. Combined, the annual saving on operational costs for depository institutions and credit unions with $10 billion or less in assets newly excluded under the proposed 50 closed-end threshold would be about $1.9 million. Similarly, the Bureau estimates that about 1,666 of the approximately 1,720 institutions that would be excluded from the proposed alternative 100 loan closed-end reporting threshold are small depository institutions or credit unions with assets at or below $10 billion, and all but two of them are already partially exempt under the EGRRCPA and 2018 HMDA Rule. About 1,573 of them are similar to representative low-complexity tier 3 institution, with the rest being moderate-complexity tier 2 institutions. Combined, the annual saving on operational costs for depository institutions and credit unions with $10 billion or less in assets newly excluded under the proposed 100 closed-end threshold would be about $4.8 million.</P>
                    <P>For the proposed open-end coverage threshold provision, the Bureau estimates that for depository institutions and credit unions with $10 billion in assets or less that would not have to report open-end lines of credit under the proposal, the reduction in annual ongoing operational costs for the excluded institutions not eligible for the partial exemption for open-end lines of credit under the EGRRCPA would be approximately $8,800, $44,700, and $28,100 per year, for representative low-, moderate-, and high-complexity financial institutions, respectively, and the reduction in annual ongoing operational costs for excluded institutions already partially exempt for open-end lines of credit under the EGRRCPA would be approximately $4,300, $21,900, and $138,000 annually, for representative low-, moderate-, and high-complexity financial institutions, respectively. The Bureau estimates that about 633 of the approximately 681 institutions that would be temporarily excluded from open-end reporting in 2020 and 2021 under this proposed rule are small depository institutions or credit unions with assets at or below $10 billion, and about 578 of them are already partially exempt under the EGRRCPA. Combined, the Bureau estimates that the annual saving on operational costs for depository institutions and credit unions with $10 billion or less in assets receiving the temporary exclusion for open-end reporting for two additional years under the proposed rule would be about $5 million per year in the years 2020 and 2021. Similarly, the Bureau estimates that about 378 of the approximately 400 institutions that would be excluded from open-end reporting starting in 2022 under the proposal are small depository institutions or credit unions with assets at or below $10 billion, and about 372 of them are already partially exempt under the EGRRCPA. Combined, the Bureau estimates that the annual saving on operational costs for depository institutions and credit unions with $10 billion or less in assets receiving the temporary exclusion for open-end reporting for two additional years under this proposed rule would be about $1.9 million per year starting in 2022. Using the estimates of savings on one-time costs for open-end lines of credit for representative financial institutions discussed above, the Bureau further estimates that by increasing the open-end coverage threshold to 200 starting in 2022, the eligible depository institutions and credit unions with $10 billion or less in assets would receive an aggregate savings in avoided one-time cost associated with open-end lines of credit of about $3.8 million.</P>
                    <HD SOURCE="HD3">2. Impact of the Proposed Provisions on Consumers in Rural Areas</HD>
                    <P>
                        The proposed provisions will not directly impact consumers in rural areas. However, as with all consumers, consumers in rural areas may be impacted indirectly. This would occur if financial institutions serving rural areas are HMDA reporters (in which case the proposal will lead to decreased information in rural areas) and if these 
                        <PRTPAGE P="21014"/>
                        institutions pass on some or all of the cost reduction to consumers (in which case, some consumers could benefit).
                    </P>
                    <P>
                        Recent research suggests that financial institutions that primarily serve rural areas are generally not HMDA reporters.
                        <SU>175</SU>
                        <FTREF/>
                         The Housing Assistance Council (HAC) suggests that the current asset and geographic coverage criteria already in place disproportionately exempt small lenders operating in rural communities. For example, HAC uses 2009 Call Report data to show that approximately 700 FDIC-insured lending institutions had assets totaling less than the HMDA institutional coverage threshold and were headquartered in rural communities. These institutions, which would not be HMDA reporters, may represent one of the few sources of credit for many rural areas. Research by economists at the Board also suggests that HMDA's coverage of rural areas is limited, especially areas further from MSAs.
                        <SU>176</SU>
                        <FTREF/>
                         If a large portion of the rural housing market is serviced by financial institutions that are already not HMDA reporters, any indirect impact of the proposed changes on consumers in rural areas would be limited, as the proposed changes directly involve none of those financial institutions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>175</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Keith Wiley, “What Are We Missing? HMDA Asset-Excluded Filers,” Hous. Assistance Council (2011), 
                            <E T="03">http://ruralhome.org/storage/documents/smallbanklending.pdf</E>
                            ; Lance George &amp; Keith Wiley, “Improving HMDA: A Need to Better Understand Rural Mortgage Markets,” Hous. Assistance Council (2010), 
                            <E T="03">http://www.ruralhome.org/storage/documents/notehmdasm.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>176</SU>
                             
                            <E T="03">See</E>
                             Robert B. Avery et al., “Opportunities and Issues in Using HMDA Data,” 29 J. of Real Est. Res. 352 (2007).
                        </P>
                    </FTNT>
                    <P>However, although some research suggests that HMDA currently does not cover a significant number of financial institutions serving the rural housing market, HMDA data do contain information for some covered loans involving properties in rural areas. These data can be used to estimate the number of HMDA reporters servicing rural areas, and the number of consumers in rural areas that might potentially be affected by the proposed changes to Regulation C. For this analysis, the Bureau uses non-MSA areas as a proxy for rural areas, with the understanding that portions of MSAs and non-MSAs may contain urban and rural territory and populations. In 2017, 5,207 HMDA reporters reported applications or purchased loans for property located in geographic areas outside of an MSA. In total, these 5,207 financial institutions reported 1,794,248 applications or purchased loans for properties in non-MSA areas. This number provides an upper-bound estimate of the number of consumers in rural areas that could be impacted indirectly by the proposed changes. In general, individual financial institutions report small numbers of covered loans from non-MSAs, as approximately 72 percent reported fewer than 100 covered loans from non-MSAs.</P>
                    <P>
                        Following microeconomic principles, the Bureau believes that financial institutions will pass on reduced variable costs to future mortgage applicants, but absorb one-time costs and increased fixed costs if financial institutions are profit maximizers and the market is perfectly competitive.
                        <SU>177</SU>
                        <FTREF/>
                         The Bureau defines variable costs as costs that depend on the number of applications received. Based on initial outreach efforts, the following five operational steps affect variable costs: Transcribing data, resolving reportability questions, transferring data to an HMS, geocoding, and researching questions. The primary impact of the proposed rule on these operational steps is a reduction in time spent per task. Overall, the Bureau estimates that the impact of the proposed rule on variable costs per application is to reduce variable costs by no more than $42 for a representative tier 3 financial institution, $6 for a representative tier 2 financial institution, and $3 for a representative tier 1 financial institution.
                        <SU>178</SU>
                        <FTREF/>
                         The 5,507 financial institutions that serviced rural areas could attempt to pass these reduced variable costs on to all future mortgage customers, including the estimated 1.8 million consumers from rural areas. Amortized over the life of the loan, this expense would represent a negligible reduction in the cost of a mortgage loan. The Bureau notes that the market structure in the consumer mortgage lending market may differ from that of a perfectly competitive market in which case the pass-through to the consumers would most likely be smaller than the pass-through under the perfect competition assumption. Therefore, the Bureau does not anticipate any material adverse effect on credit access in the long or short term even if these financial institutions pass on these reduced costs to consumers.
                    </P>
                    <FTNT>
                        <P>
                            <SU>177</SU>
                             If markets are not perfectly competitive or financial institutions are not profit maximizers then what financial institutions pass on may differ. For example, they may attempt to pass on one-time costs and increases in fixed costs, or they may not be able to pass on variable costs.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>178</SU>
                             These cost estimates represent the highest estimates among the estimates presented in previous sections and form the upper bound of possible savings.
                        </P>
                    </FTNT>
                    <P>Given the differences between rural and non-rural markets in structure, demand, supply, and competition level, consumers in rural areas may experience benefits and costs from the proposed rule that are different than those experienced by consumers in general. To the extent that the impacts of the proposal on creditors differ by type of creditor, this may affect the costs and benefits of the proposal on consumers in rural areas. The Bureau will further consider the impact of the proposed rule on consumers in rural areas. The Bureau therefore asks interested parties to provide data, research results, and other factual information on the impact of the proposed rule on consumers in rural areas. For example, this would include any evidence and supporting information indicating that access to credit would increase or the cost of credit would fall.</P>
                    <HD SOURCE="HD2">G. Additional Analysis Being Considered and Request for Information</HD>
                    <P>The Bureau will further consider the benefits, costs and impacts of the proposed provisions and additional alternatives before finalizing the proposed rule. As noted above, there are a number of areas where additional information would allow the Bureau to better estimate the benefits, costs, and impacts of this proposed rule and more fully inform the rulemaking. The Bureau asks interested parties to provide comment or data on various aspects of the proposed rule, as detailed in the section-by-section analysis.</P>
                    <HD SOURCE="HD1">VII. Regulatory Flexibility Act Analysis</HD>
                    <P>
                        The Regulatory Flexibility Act 
                        <SU>179</SU>
                        <FTREF/>
                         as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 
                        <SU>180</SU>
                        <FTREF/>
                         (RFA) requires each agency to consider the potential impact of its regulations on small entities, including small businesses, small governmental units, and small not-for-profit organizations.
                        <SU>181</SU>
                        <FTREF/>
                         The RFA defines a “small business” as a business that meets the size standard developed by 
                        <PRTPAGE P="21015"/>
                        the Small Business Administration pursuant to the Small Business Act.
                        <SU>182</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>179</SU>
                             Public Law 96-354, 94 Stat. 1164 (1980).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>180</SU>
                             Public Law 104-21, section 241, 110 Stat. 847, 864-65 (1996).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>181</SU>
                             5 U.S.C. 601-612. The term “ `small organization' means any not-for-profit enterprise which is independently owned and operated and is not dominant in its field, unless an agency establishes [an alternative definition under notice and comment].” 5 U.S.C. 601(4). The term “ `small governmental jurisdiction' means governments of cities, counties, towns, townships, villages, school districts, or special districts, with a population of less than fifty thousand, unless an agency establishes [an alternative definition after notice and comment].” 5 U.S.C. 601(5).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>182</SU>
                             5 U.S.C. 601(3). The Bureau may establish an alternative definition after consulting with the Small Business Administration and providing an opportunity for public comment. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        The RFA generally requires an agency to conduct an initial regulatory flexibility analysis (IRFA) and a final regulatory flexibility analysis (FRFA) of any rule subject to notice-and-comment rulemaking requirements, unless the agency certifies that the rule will not have a significant economic impact on a substantial number of small entities.
                        <SU>183</SU>
                        <FTREF/>
                         The Bureau also is subject to certain additional procedures under the RFA involving the convening of a panel to consult with small business representatives prior to proposing a rule for which an IRFA is required.
                        <SU>184</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>183</SU>
                             5 U.S.C. 601-612.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>184</SU>
                             5 U.S.C. 609.
                        </P>
                    </FTNT>
                    <P>As discussed above, this proposal would incorporate the interpretations and procedures from the 2018 HMDA Rule into Regulation C and further implement section 104(a) of the EGRRCPA, which grants eligible financial institutions partial exemptions from HMDA's requirements for certain transactions; it would increase the threshold for reporting data about closed-end mortgage loans from 25 to 50 or 100 originations in each of the two preceding calendar years; and it would extend the temporary threshold of 500 open-end lines of credit for reporting data about open-end lines of credit for two years and then would set the permanent open-end threshold at 200 when the proposed temporary threshold expires. The section 1022(b)(2) analysis above describes how, if adopted, this proposal would reduce the costs and burdens on covered persons, including small entities. Additionally, as described in the analysis above, a small entity that is in compliance with the law at such time when this proposal might be adopted would not need to take any additional action to remain in compliance other than choosing to switch off all or parts of reporting systems and functions. Based on these considerations, the proposed rule would not have a significant economic impact on any small entities.</P>
                    <P>Accordingly, the undersigned hereby certifies that this proposed rule, if adopted, would not have a significant economic impact on a substantial number of small entities. Thus, neither an IRFA nor a small business review panel is required for this proposal. The Bureau requests comments on this analysis and any relevant data.</P>
                    <HD SOURCE="HD1">VIII. Paperwork Reduction Act</HD>
                    <P>
                        Under the Paperwork Reduction Act of 1995 (PRA), 44 U.S.C. 3501 
                        <E T="03">et seq.,</E>
                         Federal agencies are generally required to seek approval from the Office of Management and Budget (OMB) for information collection requirements prior to implementation. Under the PRA, the Bureau may not conduct or sponsor, and, notwithstanding any other provision of law, a person is not required to respond to, an information collection unless the information collection displays a valid control number assigned by OMB.
                    </P>
                    <P>The proposed rule would amend 12 CFR part 1003 (Regulation C), which implements HMDA. The Bureau's OMB control number for Regulation C is 3170-0008. This proposed rule would revise the information collection requirements contained in Regulation C that are currently approved by OMB under that OMB control number as follows: (1) The proposed rule would adjust Regulation C's institutional and transactional coverage thresholds, and (2) implement the new, separate EGRRCPA partial exemptions that apply to some HMDA reporting requirements.</P>
                    <P>The proposed rule contains revised information collection requirements regarding:</P>
                    <HD SOURCE="HD2">12 CFR 1003.4 et seq. Reporting, Recordkeeping, and Disclosure Requirements</HD>
                    <P>
                        The collections of information contained in this proposed rule, and identified as such, have been submitted to OMB for review under section 3507(d) of the PRA. A complete description of the information collection requirements, including the burden estimate methods, is provided in the information collection request (ICR) that the Bureau has submitted to OMB under the requirements of the PRA. Please send your comments to the Office of Information and Regulatory Affairs, OMB, Attention: Desk Officer for the Bureau of Consumer Financial Protection. Send these comments by email to 
                        <E T="03">oira_submission@omb.eop.gov</E>
                         or by fax to 202-395-6974. If you wish to share your comments with the Bureau, please send a copy of these comments to the Bureau at 
                        <E T="03">PRA_Comments@cfpb.gov.</E>
                         The ICR submitted to OMB requesting approval under the PRA for the information collection requirements contained herein is available at 
                        <E T="03">www.regulations.gov</E>
                         as well as OMB's public-facing docket at 
                        <E T="03">www.reginfo.gov.</E>
                    </P>
                    <P>
                        <E T="03">Title of Collection:</E>
                         Home Mortgage Disclosure Act (Regulation C).
                    </P>
                    <P>
                        <E T="03">OMB Control Number:</E>
                         3170-0008.
                    </P>
                    <P>
                        <E T="03">Type of Review:</E>
                         Revision of a currently approved information collection.
                    </P>
                    <P>
                        <E T="03">Affected Public:</E>
                         Private Sector.
                    </P>
                    <P>
                        <E T="03">Estimated Number of Respondents:</E>
                         105.
                    </P>
                    <P>
                        <E T="03">Estimated Total Annual Burden Hours:</E>
                         1,290,000.
                    </P>
                    <P>
                        <E T="03">Comments are invited on:</E>
                         (a) Whether the collection of information is necessary for the proper performance of the functions of the Bureau, including whether the information will have practical utility; (b) the accuracy of the Bureau's estimate of the burden of the collection of information, including the validity of the methods and the assumptions used; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology. Comments submitted in response to this document will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record. If applicable, the notice of final rulemaking will display the control number assigned by OMB to any information collection requirements proposed herein and adopted in the final rule.
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 12 CFR Part 1003</HD>
                        <P>Banks, Banking, Credit unions, Mortgages, National banks, Reporting and recordkeeping requirements, Savings associations. </P>
                    </LSTSUB>
                    <HD SOURCE="HD1">Authority and Issuance</HD>
                    <P>For the reasons set forth above, the Bureau proposes to amend Regulation C, 12 CFR part 1003, as set forth below:</P>
                    <PART>
                        <HD SOURCE="HED">PART 1003—HOME MORTGAGE DISCLOSURE (REGULATION C)</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 1003 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>12 U.S.C. 2803, 2804, 2805, 5512, 5581.</P>
                    </AUTH>
                    <EXTRACT>
                        <P>[The following amendments would be effective January 1, 2020, further amending the part as amended at September 13, 2017, at 82 FR 43088, effective January 1, 2020.]</P>
                    </EXTRACT>
                    <AMDPAR>2. Section 1003.2 is amended by revising paragraphs (g)(1)(v) and (g)(2)(ii) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1003.2 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>(g) * * *</P>
                        <P>
                            (1) * * *
                            <PRTPAGE P="21016"/>
                        </P>
                        <HD SOURCE="HD1">Alternative 1—Paragraphs (g)(1)(v) and (g)(2)(ii)</HD>
                        <P>(v) Meets at least one of the following criteria:</P>
                        <P>(A) In each of the two preceding calendar years, originated at least 50 closed-end mortgage loans that are not excluded from this part pursuant to § 1003.3(c)(1) through (10) or (c)(13); or</P>
                        <P>(B) In each of the two preceding calendar years, originated at least 500 open-end lines of credit that are not excluded from this part pursuant to § 1003.3(c)(1) through (10); and</P>
                        <P>(2) * * *</P>
                        <P>(ii) Meets at least one of the following criteria:</P>
                        <P>(A) In each of the two preceding calendar years, originated at least 50 closed-end mortgage loans that are not excluded from this part pursuant to § 1003.3(c)(1) through (10) or (c)(13); or</P>
                        <P>(B) In each of the two preceding calendar years, originated at least 500 open-end lines of credit that are not excluded from this part pursuant to § 1003.3(c)(1) through (10).</P>
                        <HD SOURCE="HD1">Alternative 2—Paragraphs (g)(1)(v) and (g)(2)(ii)</HD>
                        <P>(v) Meets at least one of the following criteria:</P>
                        <P>(A) In each of the two preceding calendar years, originated at least 100 closed-end mortgage loans that are not excluded from this part pursuant to § 1003.3(c)(1) through (10) or (c)(13); or</P>
                        <P>(B) In each of the two preceding calendar years, originated at least 500 open-end lines of credit that are not excluded from this part pursuant to § 1003.3(c)(1) through (10); and</P>
                        <P>(2) * * *</P>
                        <P>(ii) Meets at least one of the following criteria:</P>
                        <P>(A) In each of the two preceding calendar years, originated at least 100 closed-end mortgage loans that are not excluded from this part pursuant to § 1003.3(c)(1) through (10) or (c)(13); or</P>
                        <P>(B) In each of the two preceding calendar years, originated at least 500 open-end lines of credit that are not excluded from this part pursuant to § 1003.3(c)(1) through (10).</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>3. Section 1003.3 is amended by revising the section heading and paragraphs (c)(11) and (12) and adding paragraph (d) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1003.3 </SECTNO>
                        <SUBJECT>Exempt institutions and excluded and partially exempt transactions.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <HD SOURCE="HD1">Alternative 1—Paragraph (c)(11)</HD>
                        <P>(11) A closed-end mortgage loan, if the financial institution originated fewer than 50 closed-end mortgage loans in either of the two preceding calendar years; a financial institution may collect, record, report, and disclose information, as described in §§ 1003.4 and 1003.5, for such an excluded closed-end mortgage loan as though it were a covered loan, provided that the financial institution complies with such requirements for all applications for closed-end mortgage loans that it receives, closed-end mortgage loans that it originates, and closed-end mortgage loans that it purchases that otherwise would have been covered loans during the calendar year during which final action is taken on the excluded closed-end mortgage loan;</P>
                        <HD SOURCE="HD1">Alternative 2—Paragraph (c)(11)</HD>
                        <P>(11) A closed-end mortgage loan, if the financial institution originated fewer than 100 closed-end mortgage loans in either of the two preceding calendar years; a financial institution may collect, record, report, and disclose information, as described in §§ 1003.4 and 1003.5, for such an excluded closed-end mortgage loan as though it were a covered loan, provided that the financial institution complies with such requirements for all applications for closed-end mortgage loans that it receives, closed-end mortgage loans that it originates, and closed-end mortgage loans that it purchases that otherwise would have been covered loans during the calendar year during which final action is taken on the excluded closed-end mortgage loan;</P>
                        <P>(12) An open-end line of credit, if the financial institution originated fewer than 500 open-end lines of credit in either of the two preceding calendar years; a financial institution may collect, record, report, and disclose information, as described in §§ 1003.4 and 1003.5, for such an excluded open-end line of credit as though it were a covered loan, provided that the financial institution complies with such requirements for all applications for open-end lines of credit that it receives, open-end lines of credit that it originates, and open-end lines of credit that it purchases that otherwise would have been covered loans during the calendar year during which final action is taken on the excluded open-end line of credit; or</P>
                        <STARS/>
                        <P>
                            (d) 
                            <E T="03">Partially exempt transactions.</E>
                             (1) For purposes of this paragraph (d), the following definitions apply:
                        </P>
                        <P>
                            (i) 
                            <E T="03">Insured credit union</E>
                             means an insured credit union as defined in section 101 of the Federal Credit Union Act (12 U.S.C. 1752).
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Insured depository institution</E>
                             means an insured depository institution as defined in section 3 of the Federal Deposit Insurance Act (12 U.S.C. 1813).
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Optional data</E>
                             means the data identified in § 1003.4(a)(1)(i), (a)(9)(i), and (a)(12), (15) through (30), and (32) through (38).
                        </P>
                        <P>
                            (iv) 
                            <E T="03">Partially exempt transaction</E>
                             means a covered loan or application that is partially exempt under paragraph (d)(2) or (3) of this section.
                        </P>
                        <P>(2) Except as provided in paragraph (d)(6) of this section, an insured depository institution or insured credit union that, in each of the two preceding calendar years, originated fewer than 500 closed-end mortgage loans that are not excluded from this part pursuant to paragraphs (c)(1) through (10) or paragraph (c)(13) of this section is not required to collect, record, or report optional data as defined in paragraph (d)(1)(iii) of this section for applications for closed-end mortgage loans that it receives, closed-end mortgage loans that it originates, and closed-end mortgage loans that it purchases.</P>
                        <P>(3) Except as provided in paragraph (d)(6) of this section, an insured depository institution or insured credit union that, in each of the two preceding calendar years, originated fewer than 500 open-end lines of credit that are not excluded from this part pursuant to paragraphs (c)(1) through (10) of this section is not required to collect, record, or report optional data as defined in paragraph (d)(1)(iii) of this section for applications for open-end lines of credit that it receives, open-end lines of credit that it originates, and open-end lines of credit that it purchases.</P>
                        <P>(4) A financial institution eligible for a partial exemption under paragraph (d)(2) or (3) of this section may collect, record, and report optional data as defined in paragraph (d)(1)(iii) of this section for a partially exempt transaction as though the institution were required to do so, provided that:</P>
                        <P>(i) If the institution reports the street address, city name, or Zip Code for the property securing a covered loan, or in the case of an application, proposed to secure a covered loan pursuant to § 1003.4(a)(9)(i), it reports all data that would be required by § 1003.4(a)(9)(i) if the transaction were not partially exempt;</P>
                        <P>(ii) If the institution reports any data for the transaction pursuant to § 1003.4(a)(15), (16), (17), (27), (33), or (35), it reports all data that would be required by § 1003.4(a)(15), (16), (17), (27), (33), or (35), respectively, if the transaction were not partially exempt.</P>
                        <P>
                            (5) If, pursuant to paragraph (d)(2) or (3) of this section, a financial institution 
                            <PRTPAGE P="21017"/>
                            does not report a universal loan identifier (ULI) pursuant to § 1003.4(a)(1)(i) for an application for a covered loan that it receives, a covered loan that it originates, or a covered loan that it purchases, the financial institution shall assign and report a non-universal loan identifier (NULI). The NULI must be composed of up to 22 characters to identify the covered loan or application, which:
                        </P>
                        <P>(i) May be letters, numerals, or a combination of letters and numerals;</P>
                        <P>(ii) Must be unique within the annual loan/application register in which the covered loan or application is included; and</P>
                        <P>(iii) Must not include any information that could be used to directly identify the applicant or borrower.</P>
                        <P>(6) Paragraphs (d)(2) and (3) of this section do not apply to an insured depository institution that, as of the preceding December 31, had received a rating of “needs to improve record of meeting community credit needs” during each of its two most recent examinations or a rating of “substantial noncompliance in meeting community credit needs” on its most recent examination under section 807(b)(2) of the Community Reinvestment Act of 1977 (12 U.S.C. 2906(b)(2)).</P>
                    </SECTION>
                    <AMDPAR>4. Section 1003.4 is amended by revising paragraphs (a) introductory text, (a)(1)(i) introductory text, and (e) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1003.4 </SECTNO>
                        <SUBJECT>Compilation of reportable data.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Data format and itemization.</E>
                             A financial institution shall collect data regarding applications for covered loans that it receives, covered loans that it originates, and covered loans that it purchases for each calendar year. A financial institution shall collect data regarding requests under a preapproval program, as defined in § 1003.2(b)(2), only if the preapproval request is denied, is approved by the financial institution but not accepted by the applicant, or results in the origination of a home purchase loan. Except as provided in § 1003.3(d), the data collected shall include the following items:
                        </P>
                        <P>(1)(i) A universal loan identifier (ULI) or, for a partially exempt transaction under § 1003.3(d), either a ULI or a non-universal loan identifier (NULI) as described in § 1003.3(d)(5) for the covered loan or application that can be used to identify and retrieve the covered loan or application file. Except for a purchased covered loan or application described in paragraphs (a)(1)(i)(D) and (E) of this section or a partially exempt transaction for which a NULI is assigned and reported under § 1003.3(d), the financial institution shall assign and report a ULI that:</P>
                        <STARS/>
                        <P>
                            (e) 
                            <E T="03">Data reporting for banks and savings associations that are required to report data on small business, small farm, and community development lending under CRA.</E>
                             Banks and savings associations that are required to report data on small business, small farm, and community development lending under regulations that implement the Community Reinvestment Act of 1977 (12 U.S.C. 2901 
                            <E T="03">et seq.</E>
                            ) shall also collect the information required by paragraph (a)(9)(ii) of this section for property located outside MSAs and MDs in which the institution has a home or branch office, or outside any MSA.
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>5. In supplement I to part 1003:</AMDPAR>
                    <AMDPAR>
                        a. Under 
                        <E T="03">Section 1003.2—Definitions,</E>
                         revise 
                        <E T="03">2(g) Financial Institution.</E>
                    </AMDPAR>
                    <AMDPAR>
                        b. Revise the heading to 
                        <E T="03">Section 1003.3.</E>
                    </AMDPAR>
                    <AMDPAR>
                        c. Under 
                        <E T="03">Section 1003.3:</E>
                    </AMDPAR>
                    <AMDPAR>
                        i. Revise 
                        <E T="03">Paragraph 3(c)(11)</E>
                         and 
                        <E T="03">Paragraph 3(c)(12).</E>
                    </AMDPAR>
                    <AMDPAR>
                        iii. Add 
                        <E T="03">3(d) Partially exempt transactions</E>
                         after 
                        <E T="03">Paragraph 3(c)(13).</E>
                    </AMDPAR>
                    <AMDPAR>
                        d. Under 
                        <E T="03">Section 1003.4—Compilation of Reportable Data,</E>
                         revise 
                        <E T="03">4(a) Data Format and Itemization.</E>
                    </AMDPAR>
                    <P>The revisions and addition read as follows:</P>
                    <HD SOURCE="HD1">Supplement I to Part 1003—Official Interpretations</HD>
                    <EXTRACT>
                        <STARS/>
                        <HD SOURCE="HD2">Section 1003.2—Definitions</HD>
                        <STARS/>
                        <HD SOURCE="HD3">2(g) Financial Institution</HD>
                        <HD SOURCE="HD1">Alternative 1—Paragraph 2(g)-1</HD>
                        <P>
                            1. 
                            <E T="03">Preceding calendar year and preceding December 31.</E>
                             The definition of financial institution refers both to the preceding calendar year and the preceding December 31. These terms refer to the calendar year and the December 31 preceding the current calendar year. For example, in 2020, the preceding calendar year is 2019 and the preceding December 31 is December 31, 2019. Accordingly, in 2020, Financial Institution A satisfies the asset-size threshold described in § 1003.2(g)(1)(i) if its assets exceeded the threshold specified in comment 2(g)-2 on December 31, 2019. Likewise, in 2020, Financial Institution A does not meet the loan-volume test described in § 1003.2(g)(1)(v)(A) if it originated fewer than 50 closed-end mortgage loans during either 2018 or 2019.
                        </P>
                        <HD SOURCE="HD1">Alternative 2—Paragraph 2(g)-1</HD>
                        <P>
                            1. 
                            <E T="03">Preceding calendar year and preceding December 31.</E>
                             The definition of financial institution refers both to the preceding calendar year and the preceding December 31. These terms refer to the calendar year and the December 31 preceding the current calendar year. For example, in 2020, the preceding calendar year is 2019 and the preceding December 31 is December 31, 2019. Accordingly, in 2020, Financial Institution A satisfies the asset-size threshold described in § 1003.2(g)(1)(i) if its assets exceeded the threshold specified in comment 2(g)-2 on December 31, 2019. Likewise, in 2020, Financial Institution A does not meet the loan-volume test described in § 1003.2(g)(1)(v)(A) if it originated fewer than 100 closed-end mortgage loans during either 2018 or 2019.
                        </P>
                        <P>2. [Reserved]</P>
                        <P>
                            3. 
                            <E T="03">Merger or acquisition—coverage of surviving or newly formed institution.</E>
                             After a merger or acquisition, the surviving or newly formed institution is a financial institution under § 1003.2(g) if it, considering the combined assets, location, and lending activity of the surviving or newly formed institution and the merged or acquired institutions or acquired branches, satisfies the criteria included in § 1003.2(g). For example, A and B merge. The surviving or newly formed institution meets the loan threshold described in § 1003.2(g)(1)(v)(B) if the surviving or newly formed institution, A, and B originated a combined total of at least 500 open-end lines of credit in each of the two preceding calendar years. Likewise, the surviving or newly formed institution meets the asset-size threshold in § 1003.2(g)(1)(i) if its assets and the combined assets of A and B on December 31 of the preceding calendar year exceeded the threshold described in § 1003.2(g)(1)(i). Comment 2(g)-4 discusses a financial institution's responsibilities during the calendar year of a merger.
                        </P>
                        <P>
                            4. 
                            <E T="03">Merger or acquisition—coverage for calendar year of merger or acquisition.</E>
                             The scenarios described below illustrate a financial institution's responsibilities for the calendar year of a merger or acquisition. For purposes of these illustrations, a “covered institution” means a financial institution, as defined in § 1003.2(g), that is not exempt from reporting under § 1003.3(a), and “an institution that is not covered” means either an institution that is not a financial institution, as defined in § 1003.2(g), or an institution that is exempt from reporting under § 1003.3(a).
                        </P>
                        <P>i. Two institutions that are not covered merge. The surviving or newly formed institution meets all of the requirements necessary to be a covered institution. No data collection is required for the calendar year of the merger (even though the merger creates an institution that meets all of the requirements necessary to be a covered institution). When a branch office of an institution that is not covered is acquired by another institution that is not covered, and the acquisition results in a covered institution, no data collection is required for the calendar year of the acquisition.</P>
                        <P>
                            ii. A covered institution and an institution that is not covered merge. The covered institution is the surviving institution, or a new covered institution is formed. For the calendar year of the merger, data collection is required for covered loans and applications handled in the offices of the merged institution that was previously covered and is optional for covered loans and 
                            <PRTPAGE P="21018"/>
                            applications handled in offices of the merged institution that was previously not covered. When a covered institution acquires a branch office of an institution that is not covered, data collection is optional for covered loans and applications handled by the acquired branch office for the calendar year of the acquisition.
                        </P>
                        <P>iii. A covered institution and an institution that is not covered merge. The institution that is not covered is the surviving institution, or a new institution that is not covered is formed. For the calendar year of the merger, data collection is required for covered loans and applications handled in offices of the previously covered institution that took place prior to the merger. After the merger date, data collection is optional for covered loans and applications handled in the offices of the institution that was previously covered. When an institution remains not covered after acquiring a branch office of a covered institution, data collection is required for transactions of the acquired branch office that take place prior to the acquisition. Data collection by the acquired branch office is optional for transactions taking place in the remainder of the calendar year after the acquisition.</P>
                        <P>iv. Two covered institutions merge. The surviving or newly formed institution is a covered institution. Data collection is required for the entire calendar year of the merger. The surviving or newly formed institution files either a consolidated submission or separate submissions for that calendar year. When a covered institution acquires a branch office of a covered institution, data collection is required for the entire calendar year of the merger. Data for the acquired branch office may be submitted by either institution.</P>
                        <HD SOURCE="HD1">Alternative 1—Paragraph 2(g)-5</HD>
                        <P>
                            5. 
                            <E T="03">Originations.</E>
                             Whether an institution is a financial institution depends in part on whether the institution originated at least 50 closed-end mortgage loans in each of the two preceding calendar years or at least 500 open-end lines of credit in each of the two preceding calendar years. Comments 4(a)-2 through -4 discuss whether activities with respect to a particular closed-end mortgage loan or open-end line of credit constitute an origination for purposes of § 1003.2(g).
                        </P>
                        <HD SOURCE="HD1">Alternative 2—Paragraph 2(g)-5</HD>
                        <P>
                            5. 
                            <E T="03">Originations.</E>
                             Whether an institution is a financial institution depends in part on whether the institution originated at least 100 closed-end mortgage loans in each of the two preceding calendar years or at least 500 open-end lines of credit in each of the two preceding calendar years. Comments 4(a)-2 through -4 discuss whether activities with respect to a particular closed-end mortgage loan or open-end line of credit constitute an origination for purposes of § 1003.2(g).
                        </P>
                        <P>
                            6. 
                            <E T="03">Branches of foreign banks—treated as banks.</E>
                             A Federal branch or a State-licensed or insured branch of a foreign bank that meets the definition of a “bank” under section 3(a)(1) of the Federal Deposit Insurance Act (12 U.S.C. 1813(a)) is a bank for the purposes of § 1003.2(g).
                        </P>
                        <P>
                            7. 
                            <E T="03">Branches and offices of foreign banks and other entities—treated as nondepository financial institutions.</E>
                             A Federal agency, State-licensed agency, State-licensed uninsured branch of a foreign bank, commercial lending company owned or controlled by a foreign bank, or entity operating under section 25 or 25A of the Federal Reserve Act, 12 U.S.C. 601 and 611 (Edge Act and agreement corporations) may not meet the definition of “bank” under the Federal Deposit Insurance Act and may thereby fail to satisfy the definition of a depository financial institution under § 1003.2(g)(1). An entity is nonetheless a financial institution if it meets the definition of nondepository financial institution under § 1003.2(g)(2).
                        </P>
                        <STARS/>
                        <HD SOURCE="HD2">Section 1003.3—Exempt Institutions and Excluded and Partially Exempt Transactions</HD>
                        <STARS/>
                        <HD SOURCE="HD3">3(c) Excluded Transactions</HD>
                        <STARS/>
                        <HD SOURCE="HD3">Paragraph 3(c)(11)</HD>
                        <HD SOURCE="HD1">Alternative 1—Paragraph 3(c)(11)-1</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Section 1003.3(c)(11) provides that a closed-end mortgage loan is an excluded transaction if a financial institution originated fewer than 50 closed-end mortgage loans in either of the two preceding calendar years. For example, assume that a bank is a financial institution in 2020 under § 1003.2(g) because it originated 600 open-end lines of credit in 2018, 650 open-end lines of credit in 2019, and met all of the other requirements under § 1003.2(g)(1). Also assume that the bank originated 30 and 45 closed-end mortgage loans in 2018 and 2019, respectively. The open-end lines of credit that the bank originated or purchased, or for which it received applications, during 2020 are covered loans and must be reported, unless they otherwise are excluded transactions under § 1003.3(c). However, the closed-end mortgage loans that the bank originated or purchased, or for which it received applications, during 2020 are excluded transactions under § 1003.3(c)(11) and need not be reported. See comments 4(a)-2 through -4 for guidance about the activities that constitute an origination.
                        </P>
                        <HD SOURCE="HD1">Alternative 2—Paragraph 3(c)(11)-1</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Section 1003.3(c)(11) provides that a closed-end mortgage loan is an excluded transaction if a financial institution originated fewer than 100 closed-end mortgage loans in either of the two preceding calendar years. For example, assume that a bank is a financial institution in 2020 under § 1003.2(g) because it originated 600 open-end lines of credit in 2018, 650 open-end lines of credit in 2019, and met all of the other requirements under § 1003.2(g)(1). Also assume that the bank originated 75 and 90 closed-end mortgage loans in 2018 and 2019, respectively. The open-end lines of credit that the bank originated or purchased, or for which it received applications, during 2020 are covered loans and must be reported, unless they otherwise are excluded transactions under § 1003.3(c). However, the closed-end mortgage loans that the bank originated or purchased, or for which it received applications, during 2020 are excluded transactions under § 1003.3(c)(11) and need not be reported. See comments 4(a)-2 through -4 for guidance about the activities that constitute an origination.
                        </P>
                        <HD SOURCE="HD1">Alternative 1—Paragraph 3(c)(11)-2</HD>
                        <P>
                            2. 
                            <E T="03">Optional reporting.</E>
                             A financial institution may report applications for, originations of, or purchases of closed-end mortgage loans that are excluded transactions because the financial institution originated fewer than 50 closed-end mortgage loans in either of the two preceding calendar years. However, a financial institution that chooses to report such excluded applications for, originations of, or purchases of closed-end mortgage loans must report all such applications for closed-end mortgage loans that it receives, closed-end mortgage loans that it originates, and closed-end mortgage loans that it purchases that otherwise would be covered loans for a given calendar year. Note that applications which remain pending at the end of a calendar year are not reported, as described in comment 4(a)(8)(i)-14.
                        </P>
                        <HD SOURCE="HD1">Alternative 2—Paragraph 3(c)(11)-2</HD>
                        <P>
                            2. 
                            <E T="03">Optional reporting.</E>
                             A financial institution may report applications for, originations of, or purchases of closed-end mortgage loans that are excluded transactions because the financial institution originated fewer than 100 closed-end mortgage loans in either of the two preceding calendar years. However, a financial institution that chooses to report such excluded applications for, originations of, or purchases of closed-end mortgage loans must report all such applications for closed-end mortgage loans that it receives, closed-end mortgage loans that it originates, and closed-end mortgage loans that it purchases that otherwise would be covered loans for a given calendar year. Note that applications which remain pending at the end of a calendar year are not reported, as described in comment 4(a)(8)(i)-14.
                        </P>
                        <HD SOURCE="HD3">Paragraph 3(c)(12)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Section 1003.3(c)(12) provides that an open-end line of credit is an excluded transaction if a financial institution originated fewer than 500 open-end lines of credit in either of the two preceding calendar years. For example, assume that a bank is a financial institution in 2020 under § 1003.2(g) because it originated 100 closed-end mortgage loans in 2018, 175 closed-end mortgage loans in 2019, and met all of the other requirements under § 1003.2(g)(1). Also assume that the bank originated 75 and 85 open-end lines of credit in 2018 and 2019, respectively. The closed-end mortgage loans that the bank originated or purchased, or for which it received applications, during 2020 are covered loans and must be reported, unless they otherwise are excluded transactions under § 1003.3(c). However, the open-end lines of credit that the bank originated or purchased, or for which it received applications, during 2020 are excluded transactions under § 1003.3(c)(12) and need not be reported. See comments 4(a)-2 through -4 for guidance about the activities that constitute an origination.
                        </P>
                        <P>
                            2. 
                            <E T="03">Optional reporting.</E>
                             A financial institution may report applications for, 
                            <PRTPAGE P="21019"/>
                            originations of, or purchases of open-end lines of credit that are excluded transactions because the financial institution originated fewer than 500 open-end lines of credit in either of the two preceding calendar years. However, a financial institution that chooses to report such excluded applications for, originations of, or purchases of open-end lines of credit must report all such applications for open-end lines of credit which it receives, open-end lines of credit that it originates, and open-end lines of credit that it purchases that otherwise would be covered loans for a given calendar year. Note that applications which remain pending at the end of a calendar year are not reported, as described in comment 4(a)(8)(i)-14.
                        </P>
                        <STARS/>
                        <HD SOURCE="HD3">3(d) Partially Exempt Transactions</HD>
                        <P>
                            1. 
                            <E T="03">Merger or acquisition—application of partial exemption thresholds to surviving or newly formed institution.</E>
                             After a merger or acquisition, the surviving or newly formed institution falls below the loan threshold described in § 1003.3(d)(2) or (3) if it, considering the combined lending activity of the surviving or newly formed institution and the merged or acquired institutions or acquired branches, falls below the loan threshold described in § 1003.3(d)(2) or (3). For example, A and B merge. The surviving or newly formed institution falls below the loan threshold described in § 1003.3(d)(2) if the surviving or newly formed institution, A, and B originated a combined total of fewer than 500 closed-end mortgage loans that are not excluded from this part pursuant to § 1003.3(c)(1) through (10) or (13) in each of the two preceding calendar years. Comment 3(d)-3 discusses eligibility for partial exemptions during the calendar year of a merger.
                        </P>
                        <P>
                            2. 
                            <E T="03">Merger or acquisition—Community Reinvestment Act examination history.</E>
                             After a merger or acquisition, the surviving or newly formed institution is deemed to be ineligible for the partial exemptions pursuant to § 1003.3(d)(6) if either it or any of the merged or acquired institutions received a rating of “needs to improve record of meeting community credit needs” during each of its two most recent examinations or a rating of “substantial noncompliance in meeting community credit needs” on its most recent examination under section 807(b)(2) of the Community Reinvestment Act of 1977 (12 U.S.C. 2906(b)(2)). Comment 3(d)-3.iii discusses eligibility for partial exemptions during the calendar year of a merger when an institution that is eligible for a partial exemption merges with an institution that is ineligible for the partial exemption (including, for example, an institution that is ineligible for the partial exemptions pursuant to § 1003.3(d)(6)) and the surviving or newly formed institution is ineligible for the partial exemption.
                        </P>
                        <P>
                            3. 
                            <E T="03">Merger or acquisition—applicability of partial exemptions during calendar year of merger or acquisition.</E>
                             The scenarios described below illustrate the applicability of partial exemptions under § 1003.3(d) during the calendar year of a merger or acquisition. For purposes of these illustrations, “institution” means a financial institution, as defined in § 1003.2(g), that is not exempt from reporting under § 1003.3(a). Although the scenarios below refer to the partial exemption for closed-end mortgage loans under § 1003.3(d)(2), the same principles apply with respect to the partial exemption for open-end lines of credit under § 1003.3(d)(3).
                        </P>
                        <P>i. Assume two institutions that are eligible for the partial exemption for closed-end mortgage loans merge and the surviving or newly formed institution meets all of the requirements for the partial exemption. The partial exemption for closed-end mortgage loans applies for the calendar year of the merger.</P>
                        <P>ii. Assume two institutions that are eligible for the partial exemption for closed-end mortgage loans merge and the surviving or newly formed institution does not meet the requirements for the partial exemption. Collection of optional data for closed-end mortgage loans is permitted but not required for the calendar year of the merger (even though the merger creates an institution that does not meet the requirements for the partial exemption for closed-end mortgage loans). When a branch office of an institution that is eligible for the partial exemption is acquired by another institution that is eligible for the partial exemption, and the acquisition results in an institution that is not eligible for the partial exemption, data collection for closed-end mortgage loans is permitted but not required for the calendar year of the acquisition.</P>
                        <P>iii. Assume an institution that is eligible for the partial exemption for closed-end mortgage loans merges with an institution that is ineligible for the partial exemption and the surviving or newly formed institution is ineligible for the partial exemption. For the calendar year of the merger, collection of optional data as defined in § 1003.3(d)(1)(iii) for closed-end mortgage loans is required for covered loans and applications handled in the offices of the merged institution that was previously ineligible for the partial exemption. For the calendar year of the merger, collection of optional data for closed-end mortgage loans is permitted but not required for covered loans and applications handled in the offices of the merged institution that was previously eligible for the partial exemption. When an institution that is ineligible for the partial exemption for closed-end mortgage loans acquires a branch office of an institution that is eligible for the partial exemption, collection of optional data for closed-end mortgage loans is permitted but not required for covered loans and applications handled by the acquired branch office for the calendar year of the acquisition.</P>
                        <P>iv. Assume an institution that is eligible for the partial exemption for closed-end mortgage loans merges with an institution that is ineligible for the partial exemption and the surviving or newly formed institution is eligible for the partial exemption. For the calendar year of the merger, collection of optional data for closed-end mortgage loans is required for covered loans and applications handled in the offices of the previously ineligible institution that took place prior to the merger. After the merger date, collection of optional data for closed-end mortgage loans is permitted but not required for covered loans and applications handled in the offices of the institution that was previously ineligible for the partial exemption. When an institution remains eligible for the partial exemption for closed-end mortgage loans after acquiring a branch office of an institution that is ineligible for the partial exemption, collection of optional data for closed-end mortgage loans is required for transactions of the acquired branch office that take place prior to the acquisition. Collection of optional data for closed-end mortgage loans by the acquired branch office is permitted but not required for transactions taking place in the remainder of the calendar year after the acquisition.</P>
                        <P>
                            4. 
                            <E T="03">Originations.</E>
                             Whether applications for covered loans that an insured depository institution or insured credit union receives, covered loans that it originates, or covered loans that it purchases are partially exempt transactions under § 1003.3(d) depends, in part, on whether the institution originated fewer than 500 closed-end mortgage loans that are not excluded from this part pursuant to § 1003.3(c)(1) through (10) or (c)(13) in each of the two preceding calendar years or fewer than 500 open-end lines of credit that are not excluded from this part pursuant to § 1003.3(c)(1) through (10) in each of the two preceding calendar years. See comments 4(a)-2 through -4 for guidance about the activities that constitute an origination for purposes of § 1003.3(d).
                        </P>
                        <P>
                            5. 
                            <E T="03">Affiliates.</E>
                             A financial institution that is not itself an insured credit union or an insured depository institution as defined in § 1003.3(d)(1)(i) and (ii) is not eligible for the partial exemptions under § 1003.3(d)(1) through (3), even if it is owned by or affiliated with an insured credit union or an insured depository institution. For example, an institution that is a subsidiary of an insured credit union or insured depository institution may not claim a partial exemption under § 1003.3(d) for its closed-end mortgage loans unless the subsidiary institution itself:
                        </P>
                        <P>i. Is an insured credit union or insured depository institution,</P>
                        <P>ii. In each of the two preceding calendar years originated fewer than 500 closed-end mortgage loans that are not excluded from this part pursuant to § 1003.3(c)(1) through (10) or (c)(13), and</P>
                        <P>iii. If the subsidiary is an insured depository institution, had not received as of the preceding December 31 a rating of “needs to improve record of meeting community credit needs” during each of its two most recent examinations or a rating of “substantial noncompliance in meeting community credit needs” on its most recent examination under section 807(b)(2) of the Community Reinvestment Act of 1977 (12 U.S.C. 2906(b)(2)).</P>
                        <HD SOURCE="HD3">Paragraph 3(d)(1)(iii)</HD>
                        <P>
                            1. 
                            <E T="03">Optional data.</E>
                             The definition of optional data in § 1003.3(d)(1)(iii) identifies the data that are covered by the partial exemptions for certain transactions of insured depository institutions and insured credit unions under § 1003.3(d). If a transaction is not partially exempt under § 1003.3(d)(2) or (3), a 
                            <PRTPAGE P="21020"/>
                            financial institution must collect, record, and report optional data as otherwise required under this part.
                        </P>
                        <HD SOURCE="HD3">Paragraph 3(d)(2)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Section 1003.3(d)(2) provides that, except as provided in § 1003.3(d)(6), an insured depository institution or insured credit union that, in each of the two preceding calendar years, originated fewer than 500 closed-end mortgage loans that are not excluded from this part pursuant to § 1003.3(c)(1) through (10) or (c)(13) is not required to collect, record, or report optional data as defined in § 1003.3(d)(1)(iii) for applications for closed-end mortgage loans that it receives, closed-end mortgage loans that it originates, and closed-end mortgage loans that it purchases. For example, assume that an insured credit union is a financial institution in 2020 under § 1003.2(g) and originated, in 2018 and 2019 respectively, 100 and 200 closed-end mortgage loans that are not excluded from this part pursuant to § 1003.3(c)(1) through (10) or (c)(13). The closed-end mortgage loans that the insured credit union originated or purchased, or for which it received applications, during 2020 are not excluded transactions under § 1003.3(c)(11). However, due to the partial exemption in § 1003.3(d)(2), the insured credit union is not required to collect, record, or report optional data as defined in § 1003.3(d)(1)(iii) for the closed-end mortgage loans that it originated or purchased, or for which it received applications, for which final action is taken during 2020. See comments 4(a)-2 through -4 for guidance about the activities that constitute an origination.
                        </P>
                        <HD SOURCE="HD3">Paragraph 3(d)(3)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Section 1003.3(d)(3) provides that, except as provided in § 1003.3(d)(6), an insured depository institution or insured credit union that, in each of the two preceding calendar years, originated fewer than 500 open-end lines of credit that are not excluded from this part pursuant to § 1003.3(c)(1) through (10) is not required to collect, record, or report optional data as defined in § 1003.3(d)(1)(iii) for applications for open-end lines of credit that it receives, open-end lines of credit that it originates, and open-end lines of credit that it purchases. See § 1003.3(c)(12) and comments 3(c)(12)-1 and -2, which provide an exclusion for certain open-end lines of credit from this part and permit voluntary reporting of such transactions under certain circumstances. See also comments 4(a)-2 through -4 for guidance about the activities that constitute an origination.
                        </P>
                        <HD SOURCE="HD3">Paragraph 3(d)(4)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Section 1003.3(d)(4) provides that an insured depository institution or insured credit union may collect, record, and report optional data as defined in § 1003.3(d)(1)(iii) for a partially exempt transaction as though the institution were required to do so, provided that, if an institution voluntarily reports any data pursuant to any of the seven paragraphs identified in § 1003.3(d)(4)(i) and (ii) (§ 1003.4(a)(9)(i) and (a)(15), (16), (17), (27), (33), and (35)), it also must report all other data for the covered loan or application that would be required by that applicable paragraph if the transaction were not partially exempt. For example, an insured depository institution or insured credit union may voluntarily report the existence of a balloon payment for a partially exempt transaction pursuant to § 1003.4(a)(27), but, if it does so, it must also report all other data for the transaction that would be required by § 1003.4(a)(27) if the transaction were not partially exempt (
                            <E T="03">i.e.,</E>
                             whether the transaction has interest-only payments, negative amortization, or other non-amortizing features).
                        </P>
                        <P>
                            2. 
                            <E T="03">Partially exempt transactions within the same loan/application register.</E>
                             A financial institution may collect, record, and report optional data for some partially exempt transactions under § 1003.3(d) in the manner specified in § 1003.3(d)(4), even if it does not collect, record, and report optional data for other partially exempt transactions under § 1003.3(d).
                        </P>
                        <P>
                            3. 
                            <E T="03">Exempt or not applicable.</E>
                             i. If a financial institution would otherwise report that a transaction is partially exempt pursuant to § 1003.3(d) and a particular requirement to report optional data is not applicable to the transaction, the insured depository institution or insured credit union complies with the particular requirement by reporting either that the transaction is exempt from the requirement or that the requirement is not applicable. For example, assume that an insured depository institution or insured credit union originates a partially exempt reverse mortgage. The requirement to report lender credits is not applicable to reverse mortgages, as comment 4(a)(20)-1 explains. Accordingly, the institution could report either exempt or not applicable for lender credits for the reverse mortgage transaction.
                        </P>
                        <P>ii. An institution is considered as reporting data in a data field for purposes of § 1003.3(d)(4)(i) and (ii) when it reports not applicable for that data field for a partially exempt transaction. For example, assume an insured depository institution or insured credit union originates a covered loan that is eligible for a partial exemption and is made primarily for business or commercial purposes. The requirement to report total loan costs or total points and fees is not applicable to loans made primarily for business or commercial purposes, as comments 4(a)(17)(i)-1 and (ii)-1 explain. The institution can report not applicable for both total loan costs and total points and fees, or it can report exempt for both total loan costs and total points and fees for the loan. Pursuant to § 1003.3(d)(4)(ii), the institution is not permitted to report not applicable for total loan costs and report exempt for total points and fees for the business or commercial purpose loan.</P>
                        <HD SOURCE="HD3">Paragraph 3(d)(4)(i)</HD>
                        <P>
                            1. 
                            <E T="03">State.</E>
                             Section 1003.3(d)(4)(i) provides that if an institution eligible for a partial exemption under § 1003.3(d)(2) or (3) reports the street address, city name, or Zip Code for a partially exempt transaction pursuant to § 1003.4(a)(9)(i), it reports all data that would be required by § 1003.4(a)(9)(i) if the transaction were not partially exempt, including the State. An insured depository institution or insured credit union that reports the State pursuant to § 1003.4(a)(9)(ii) or comment 4(a)(9)(ii)-1 for a partially exempt transaction without reporting any other data required by § 1003.4(a)(9)(i) is not required to report the street address, city name, or Zip Code pursuant to § 1003.4(a)(9)(i).
                        </P>
                        <HD SOURCE="HD3">Paragraph 3(d)(5)</HD>
                        <P>
                            1. 
                            <E T="03">NULI—uniqueness.</E>
                             For a partially exempt transaction under § 1003.3(d), a financial institution may report a ULI or a NULI. Section 1003.3(d)(5)(ii) requires an insured depository institution or insured credit union that assigns a NULI to a covered loan or application to ensure that the character sequence it assigns is unique within the institution's annual loan/application register in which it appears. A financial institution should assign only one NULI to any particular covered loan or application within each annual loan/application register, and each NULI should correspond to a single application and ensuing loan within the annual loan/application register in which the NULI appears in the case that the application is approved and a loan is originated. A financial institution may use a NULI more than once within an annual loan/application register only if the NULI refers to the same loan or application or a loan that ensues from an application referred to elsewhere in the annual loan/application register. Refinancings or applications for refinancing that are included in same annual loan/application register as the loan that is being refinanced should be assigned a different NULI than the loan that is being refinanced. An insured depository institution or insured credit union with multiple branches must ensure that its branches do not use the same NULI to refer to multiple covered loans or applications within the institution's same annual loan/application register.
                        </P>
                        <P>
                            2. 
                            <E T="03">NULI—privacy.</E>
                             Section 1003.3(d)(5)(iii) prohibits an insured depository institution or insured credit union from including information in the NULI that could be used to directly identify the applicant or borrower. Information that could be used to directly identify the applicant or borrower includes, but is not limited to, the applicant's or borrower's name, date of birth, Social Security number, official government-issued driver's license or identification number, alien registration number, government passport number, or employer or taxpayer identification number.
                        </P>
                        <HD SOURCE="HD3">Paragraph 3(d)(6)</HD>
                        <P>
                            1. 
                            <E T="03">Preceding calendar year.</E>
                             Section 1003.3(d)(6) refers to the preceding December 31, which means the December 31 preceding the current calendar year. For example, in 2020, the preceding December 31 is December 31, 2019. Assume that, as of December 31, 2019, an insured depository institution received ratings of “needs to improve record of meeting community credit needs” during its two most recent examinations under section 807(b)(2) of the Community Reinvestment Act (12 U.S.C. 2906(b)(2)) in 2018 and 2014. Accordingly, in 2020, the insured depository institution's transactions are not partially exempt pursuant to § 1003.3(d).
                            <PRTPAGE P="21021"/>
                        </P>
                        <HD SOURCE="HD2">Section 1003.4—Compilation of Reportable Data</HD>
                        <HD SOURCE="HD3">4(a) Data Format and Itemization</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Except as otherwise provided in § 1003.3, § 1003.4(a) describes a financial institution's obligation to collect data on applications it received, on covered loans that it originated, and on covered loans that it purchased during the calendar year covered by the loan/application register.
                        </P>
                        <P>i. A financial institution reports these data even if the covered loans were subsequently sold by the institution.</P>
                        <P>ii. A financial institution reports data for applications that did not result in an origination but on which actions were taken-for example, an application that the institution denied, that it approved but that was not accepted, that it closed for incompleteness, or that the applicant withdrew during the calendar year covered by the loan/application register. A financial institution is required to report data regarding requests under a preapproval program (as defined in § 1003.2(b)(2)) only if the preapproval request is denied, results in the origination of a home purchase loan, or was approved but not accepted.</P>
                        <P>iii. If a financial institution acquires covered loans in bulk from another institution (for example, from the receiver for a failed institution), but no merger or acquisition of an institution, or acquisition of a branch office, is involved, the acquiring financial institution reports the covered loans as purchased loans.</P>
                        <P>iv. A financial institution reports the data for an application on the loan/application register for the calendar year during which the application was acted upon even if the institution received the application in a previous calendar year.</P>
                        <P>
                            2. 
                            <E T="03">Originations and applications involving more than one institution.</E>
                             Section 1003.4(a) requires a financial institution to collect certain information regarding applications for covered loans that it receives and regarding covered loans that it originates. The following provides guidance on how to report originations and applications involving more than one institution. The discussion below assumes that all of the parties are financial institutions as defined by § 1003.2(g). The same principles apply if any of the parties is not a financial institution. Comment 4(a)-3 provides examples of transactions involving more than one institution, and comment 4(a)-4 discusses how to report actions taken by agents.
                        </P>
                        <P>i. Only one financial institution reports each originated covered loan as an origination. If more than one institution was involved in the origination of a covered loan, the financial institution that made the credit decision approving the application before closing or account opening reports the loan as an origination. It is not relevant whether the loan closed or, in the case of an application, would have closed in the institution's name. If more than one institution approved an application prior to closing or account opening and one of those institutions purchased the loan after closing, the institution that purchased the loan after closing reports the loan as an origination. If a financial institution reports a transaction as an origination, it reports all of the information required for originations, even if the covered loan was not initially payable to the financial institution that is reporting the covered loan as an origination.</P>
                        <P>ii. In the case of an application for a covered loan that did not result in an origination, a financial institution reports the action it took on that application if it made a credit decision on the application or was reviewing the application when the application was withdrawn or closed for incompleteness. It is not relevant whether the financial institution received the application from the applicant or from another institution, such as a broker, or whether another financial institution also reviewed and reported an action taken on the same application.</P>
                        <P>
                            3. 
                            <E T="03">Examples—originations and applications involving more than one institution.</E>
                             The following scenarios illustrate how an institution reports a particular application or covered loan. The illustrations assume that all of the parties are financial institutions as defined by § 1003.2(g). However, the same principles apply if any of the parties is not a financial institution.
                        </P>
                        <P>i. Financial Institution A received an application for a covered loan from an applicant and forwarded that application to Financial Institution B. Financial Institution B reviewed the application and approved the loan prior to closing. The loan closed in Financial Institution A's name. Financial Institution B purchased the loan from Financial Institution A after closing. Financial Institution B was not acting as Financial Institution A's agent. Since Financial Institution B made the credit decision prior to closing, Financial Institution B reports the transaction as an origination, not as a purchase. Financial Institution A does not report the transaction.</P>
                        <P>ii. Financial Institution A received an application for a covered loan from an applicant and forwarded that application to Financial Institution B. Financial Institution B reviewed the application before the loan would have closed, but the application did not result in an origination because Financial Institution B denied the application. Financial Institution B was not acting as Financial Institution A's agent. Since Financial Institution B made the credit decision, Financial Institution B reports the application as a denial. Financial Institution A does not report the application. If, under the same facts, the application was withdrawn before Financial Institution B made a credit decision, Financial Institution B would report the application as withdrawn and Financial Institution A would not report the application.</P>
                        <P>iii. Financial Institution A received an application for a covered loan from an applicant and approved the application before closing the loan in its name. Financial Institution A was not acting as Financial Institution B's agent. Financial Institution B purchased the covered loan from Financial Institution A. Financial Institution B did not review the application before closing. Financial Institution A reports the loan as an origination. Financial Institution B reports the loan as a purchase.</P>
                        <P>iv. Financial Institution A received an application for a covered loan from an applicant. If approved, the loan would have closed in Financial Institution B's name. Financial Institution A denied the application without sending it to Financial Institution B for approval. Financial Institution A was not acting as Financial Institution B's agent. Since Financial Institution A made the credit decision before the loan would have closed, Financial Institution A reports the application. Financial Institution B does not report the application.</P>
                        <P>
                            v. Financial Institution A reviewed an application and made the credit decision to approve a covered loan using the underwriting criteria provided by a third party (
                            <E T="03">e.g.,</E>
                             another financial institution, Fannie Mae, or Freddie Mac). The third party did not review the application and did not make a credit decision prior to closing. Financial Institution A was not acting as the third party's agent. Financial Institution A reports the application or origination. If the third party purchased the loan and is subject to Regulation C, the third party reports the loan as a purchase whether or not the third party reviewed the loan after closing. Assume the same facts, except that Financial Institution A approved the application, and the applicant chose not to accept the loan from Financial Institution A. Financial Institution A reports the application as approved but not accepted and the third party, assuming the third party is subject to Regulation C, does not report the application.
                        </P>
                        <P>vi. Financial Institution A reviewed and made the credit decision on an application based on the criteria of a third-party insurer or guarantor (for example, a government or private insurer or guarantor). Financial Institution A reports the action taken on the application.</P>
                        <P>vii. Financial Institution A received an application for a covered loan and forwarded it to Financial Institutions B and C. Financial Institution A made a credit decision, acting as Financial Institution D's agent, and approved the application. The applicant did not accept the loan from Financial Institution D. Financial Institution D reports the application as approved but not accepted. Financial Institution A does not report the application. Financial Institution B made a credit decision, approving the application, the applicant accepted the offer of credit from Financial Institution B, and credit was extended. Financial Institution B reports the origination. Financial Institution C made a credit decision and denied the application. Financial Institution C reports the application as denied.</P>
                        <P>
                            4. 
                            <E T="03">Agents.</E>
                             If a financial institution made the credit decision on a covered loan or application through the actions of an agent, the institution reports the application or origination. State law determines whether one party is the agent of another. For example, acting as Financial Institution A's agent, Financial Institution B approved an application prior to closing and a covered loan was originated. Financial Institution A reports the loan as an origination.
                        </P>
                        <P>
                            5. 
                            <E T="03">Purchased loans.</E>
                             i. A financial institution is required to collect data 
                            <PRTPAGE P="21022"/>
                            regarding covered loans it purchases. For purposes of § 1003.4(a), a purchase includes a repurchase of a covered loan, regardless of whether the institution chose to repurchase the covered loan or was required to repurchase the covered loan because of a contractual obligation and regardless of whether the repurchase occurs within the same calendar year that the covered loan was originated or in a different calendar year. For example, assume that Financial Institution A originates or purchases a covered loan and then sells it to Financial Institution B, who later requires Financial Institution A to repurchase the covered loan pursuant to the relevant contractual obligations. Financial Institution B reports the purchase from Financial Institution A, assuming it is a financial institution as defined under § 1003.2(g). Financial Institution A reports the repurchase from Financial Institution B as a purchase.
                        </P>
                        <P>ii. In contrast, for purposes of § 1003.4(a), a purchase does not include a temporary transfer of a covered loan to an interim funder or warehouse creditor as part of an interim funding agreement under which the originating financial institution is obligated to repurchase the covered loan for sale to a subsequent investor. Such agreements, often referred to as “repurchase agreements,” are sometimes employed as functional equivalents of warehouse lines of credit. Under these agreements, the interim funder or warehouse creditor acquires legal title to the covered loan, subject to an obligation of the originating institution to repurchase at a future date, rather than taking a security interest in the covered loan as under the terms of a more conventional warehouse line of credit. To illustrate, assume Financial Institution A has an interim funding agreement with Financial Institution B to enable Financial Institution B to originate loans. Assume further that Financial Institution B originates a covered loan and that, pursuant to this agreement, Financial Institution A takes a temporary transfer of the covered loan until Financial Institution B arranges for the sale of the covered loan to a subsequent investor and that Financial Institution B repurchases the covered loan to enable it to complete the sale to the subsequent investor (alternatively, Financial Institution A may transfer the covered loan directly to the subsequent investor at Financial Institution B's direction, pursuant to the interim funding agreement). The subsequent investor could be, for example, a financial institution or other entity that intends to hold the loan in portfolio, a GSE or other securitizer, or a financial institution or other entity that intends to package and sell multiple loans to a GSE or other securitizer. In this example, the temporary transfer of the covered loan from Financial Institution B to Financial Institution A is not a purchase, and any subsequent transfer back to Financial Institution B for delivery to the subsequent investor is not a purchase, for purposes of § 1003.4(a). Financial Institution B reports the origination of the covered loan as well as its sale to the subsequent investor. If the subsequent investor is a financial institution under § 1003.2(g), it reports a purchase of the covered loan pursuant to § 1003.4(a), regardless of whether it acquired the covered loan from Financial Institution B or directly from Financial Institution A.</P>
                        <HD SOURCE="HD3">Paragraph 4(a)(1)(i)</HD>
                        <P>
                            1. 
                            <E T="03">ULI—uniqueness.</E>
                             Section 1003.4(a)(1)(i)(B)(
                            <E T="03">2</E>
                            ) requires a financial institution that assigns a universal loan identifier (ULI) to each covered loan or application (except as provided in § 1003.4(a)(1)(i)(D) and (E)) to ensure that the character sequence it assigns is unique within the institution and used only for the covered loan or application. A financial institution should assign only one ULI to any particular covered loan or application, and each ULI should correspond to a single application and ensuing loan in the case that the application is approved and a loan is originated. A financial institution may use a ULI that was reported previously to refer only to the same loan or application for which the ULI was used previously or a loan that ensues from an application for which the ULI was used previously. A financial institution may not report an application for a covered loan in 2030 using the same ULI that was reported for a covered loan that was originated in 2020. Similarly, refinancings or applications for refinancing should be assigned a different ULI than the loan that is being refinanced. A financial institution with multiple branches must ensure that its branches do not use the same ULI to refer to multiple covered loans or applications.
                        </P>
                        <P>
                            2. 
                            <E T="03">ULI—privacy.</E>
                             Section 1003.4(a)(1)(i)(B)(
                            <E T="03">3</E>
                            ) prohibits a financial institution from including information that could be used to directly identify the applicant or borrower in the identifier that it assigns for the application or covered loan of the applicant or borrower. Information that could be used to directly identify the applicant or borrower includes, but is not limited to, the applicant's or borrower's name, date of birth, Social Security number, official government-issued driver's license or identification number, alien registration number, government passport number, or employer or taxpayer identification number.
                        </P>
                        <P>
                            3. 
                            <E T="03">ULI—purchased covered loan.</E>
                             If a financial institution has previously assigned a covered loan with a ULI or reported a covered loan with a ULI under this part, a financial institution that purchases that covered loan must report the same ULI that was previously assigned or reported unless the purchase of the covered loan is a partially exempt transaction under § 1003.3(d). For example, if a financial institution that submits an annual loan/application register pursuant to § 1003.5(a)(1)(i) originates a covered loan that is purchased by a financial institution that also submits an annual loan/application register pursuant to § 1003.5(a)(1)(i), the financial institution that purchases the covered loan must report the purchase of the covered loan using the same ULI that was reported by the originating financial institution if the purchase is not a partially exempt transaction. If a financial institution that originates a covered loan has previously assigned the covered loan with a ULI under this part but has not yet reported the covered loan, a financial institution that purchases that covered loan must report the same ULI that was previously assigned if the purchase is not a partially exempt transaction. For example, if a financial institution that submits an annual loan/application register pursuant to § 1003.5(a)(1)(i) (Institution A) originates a covered loan that is purchased by a financial institution that submits a quarterly loan/application register pursuant to § 1003.5(a)(1)(ii) (Institution B) and Institution A assigned a ULI to the loan, then unless the purchase is a partially exempt transaction Institution B must report the ULI that was assigned by Institution A on Institution B's quarterly loan/application register pursuant to § 1003.5(a)(1)(ii), even though Institution A has not yet submitted its annual loan/application register pursuant to § 1003.5(a)(1)(i). A financial institution that purchases a covered loan and is ineligible for a partial exemption with respect to the purchased covered loan must assign it a ULI pursuant to § 1003.4(a)(1)(i) and report it pursuant to § 1003.5(a)(1)(i) or (ii), whichever is applicable, if the covered loan was not assigned a ULI by the financial institution that originated the loan because, for example, the loan was originated prior to January 1, 2018, the loan was originated by an institution not required to report under this part, or the loan was assigned a non-universal loan identifier (NULI) under § 1003.3(d)(5) rather than a ULI by the loan originator.
                        </P>
                        <P>
                            4. 
                            <E T="03">ULI—reinstated or reconsidered application.</E>
                             A financial institution may, at its option, report a ULI previously reported under this part if, during the same calendar year, an applicant asks the institution to reinstate a counteroffer that the applicant previously did not accept or asks the financial institution to reconsider an application that was previously denied, withdrawn, or closed for incompleteness. For example, if a financial institution reports a denied application in its second-quarter 2020 data submission, pursuant to § 1003.5(a)(1)(ii), but then reconsiders the application, resulting in an origination in the third quarter of 2020, the financial institution may report the origination in its third-quarter 2020 data submission using the same ULI that was reported for the denied application in its second-quarter 2020 data submission, so long as the financial institution treats the origination as the same transaction for reporting. However, a financial institution may not use a ULI previously reported if it reinstates or reconsiders an application that was reported in a prior calendar year. For example, if a financial institution reports a denied application that is not partially exempt in its fourth-quarter 2020 data submission, pursuant to § 1003.5(a)(1)(ii), but then reconsiders the application, resulting in an origination that is not partially exempt in the first quarter of 2021, the financial institution reports a denied application under the original ULI in its fourth-quarter 2020 data submission and an origination with a different ULI in its first-quarter 2021 data submission, pursuant to § 1003.5(a)(1)(ii).
                        </P>
                        <P>
                            5. 
                            <E T="03">ULI—check digit.</E>
                             Section 1003.4(a)(1)(i)(C) requires that the two right-most characters in the ULI represent the check digit. Appendix C prescribes the 
                            <PRTPAGE P="21023"/>
                            requirements for generating a check digit and validating a ULI.
                        </P>
                        <P>
                            6. 
                            <E T="03">NULI.</E>
                             For a partially exempt transaction under § 1003.3(d), a financial institution may report a ULI or a NULI. See § 1003.3(d)(5) and comments 3(d)(5)-1 and -2 for guidance on the NULI.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(1)(ii)</HD>
                        <P>
                            1. 
                            <E T="03">Application date—consistency.</E>
                             Section 1003.4(a)(1)(ii) requires that, in reporting the date of application, a financial institution report the date it received the application, as defined under § 1003.2(b), or the date shown on the application form. Although a financial institution need not choose the same approach for its entire HMDA submission, it should be generally consistent (such as by routinely using one approach within a particular division of the institution or for a category of loans). If the financial institution chooses to report the date shown on the application form and the institution retains multiple versions of the application form, the institution reports the date shown on the first application form satisfying the application definition provided under § 1003.2(b).
                        </P>
                        <P>
                            2. 
                            <E T="03">Application date—indirect application.</E>
                             For an application that was not submitted directly to the financial institution, the institution may report the date the application was received by the party that initially received the application, the date the application was received by the institution, or the date shown on the application form. Although an institution need not choose the same approach for its entire HMDA submission, it should be generally consistent (such as by routinely using one approach within a particular division of the institution or for a category of loans).
                        </P>
                        <P>
                            3. 
                            <E T="03">Application date—reinstated application.</E>
                             If, within the same calendar year, an applicant asks a financial institution to reinstate a counteroffer that the applicant previously did not accept (or asks the institution to reconsider an application that was denied, withdrawn, or closed for incompleteness), the institution may treat that request as the continuation of the earlier transaction using the same ULI or NULI or as a new transaction with a new ULI or NULI. If the institution treats the request for reinstatement or reconsideration as a new transaction, it reports the date of the request as the application date. If the institution does not treat the request for reinstatement or reconsideration as a new transaction, it reports the original application date.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(2)</HD>
                        <P>
                            1. 
                            <E T="03">Loan type—general.</E>
                             If a covered loan is not, or in the case of an application would not have been, insured by the Federal Housing Administration, guaranteed by the Department of Veterans Affairs, or guaranteed by the Rural Housing Service or the Farm Service Agency, an institution complies with § 1003.4(a)(2) by reporting the covered loan as not insured or guaranteed by the Federal Housing Administration, Department of Veterans Affairs, Rural Housing Service, or Farm Service Agency.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(3)</HD>
                        <P>
                            1. 
                            <E T="03">Purpose—statement of applicant.</E>
                             A financial institution may rely on the oral or written statement of an applicant regarding the proposed use of covered loan proceeds. For example, a lender could use a check-box or a purpose line on a loan application to determine whether the applicant intends to use covered loan proceeds for home improvement purposes. If an applicant provides no statement as to the proposed use of covered loan proceeds and the covered loan is not a home purchase loan, cash-out refinancing, or refinancing, a financial institution reports the covered loan as for a purpose other than home purchase, home improvement, refinancing, or cash-out refinancing for purposes of § 1003.4(a)(3).
                        </P>
                        <P>
                            2. 
                            <E T="03">Purpose—refinancing and cash-out refinancing.</E>
                             Section 1003.4(a)(3) requires a financial institution to report whether a covered loan is, or an application is for, a refinancing or a cash-out refinancing. A financial institution reports a covered loan or an application as a cash-out refinancing if it is a refinancing as defined by § 1003.2(p) and the institution considered it to be a cash-out refinancing in processing the application or setting the terms (such as the interest rate or origination charges) under its guidelines or an investor's guidelines. For example:
                        </P>
                        <P>i. Assume a financial institution considers an application for a loan product to be a cash-out refinancing under an investor's guidelines because of the amount of cash received by the borrower at closing or account opening. Assume also that under the investor's guidelines, the applicant qualifies for the loan product and the financial institution approves the application, originates the covered loan, and sets the terms of the covered loan consistent with the loan product. In this example, the financial institution would report the covered loan as a cash-out refinancing for purposes of § 1003.4(a)(3).</P>
                        <P>ii. Assume a financial institution does not consider an application for a covered loan to be a cash-out refinancing under its own guidelines because the amount of cash received by the borrower does not exceed a certain threshold. Assume also that the institution approves the application, originates the covered loan, and sets the terms of the covered loan consistent with its own guidelines applicable to refinancings other than cash-out refinancings. In this example, the financial institution would report the covered loan as a refinancing for purposes of § 1003.4(a)(3).</P>
                        <P>iii. Assume a financial institution does not distinguish between a cash-out refinancing and a refinancing under its own guidelines, and sets the terms of all refinancings without regard to the amount of cash received by the borrower at closing or account opening, and does not offer loan products under investor guidelines. In this example, the financial institution reports all covered loans and applications for covered loans that are defined by § 1003.2(p) as refinancings for purposes of § 1003.4(a)(3).</P>
                        <P>
                            3. 
                            <E T="03">Purpose—multiple-purpose loan.</E>
                             Section 1003.4(a)(3) requires a financial institution to report the purpose of a covered loan or application. If a covered loan is a home purchase loan as well as a home improvement loan, a refinancing, or a cash-out refinancing, an institution complies with § 1003.4(a)(3) by reporting the loan as a home purchase loan. If a covered loan is a home improvement loan as well as a refinancing or cash-out refinancing, but the covered loan is not a home purchase loan, an institution complies with § 1003.4(a)(3) by reporting the covered loan as a refinancing or a cash-out refinancing, as appropriate. If a covered loan is a refinancing or cash-out refinancing as well as for another purpose, such as for the purpose of paying educational expenses, but the covered loan is not a home purchase loan, an institution complies with § 1003.4(a)(3) by reporting the covered loan as a refinancing or a cash-out refinancing, as appropriate. 
                            <E T="03">See</E>
                             comment 4(a)(3)-2. If a covered loan is a home improvement loan as well as for another purpose, but the covered loan is not a home purchase loan, a refinancing, or cash-out refinancing, an institution complies with § 1003.4(a)(3) by reporting the covered loan as a home improvement loan. 
                            <E T="03">See</E>
                             comment 2(i)-1.
                        </P>
                        <P>
                            4. 
                            <E T="03">Purpose—other.</E>
                             If a covered loan is not, or an application is not for, a home purchase loan, a home improvement loan, a refinancing, or a cash-out refinancing, a financial institution complies with § 1003.4(a)(3) by reporting the covered loan or application as for a purpose other than home purchase, home improvement, refinancing, or cash-out refinancing. For example, if a covered loan is for the purpose of paying educational expenses, the financial institution complies with § 1003.4(a)(3) by reporting the covered loan as for a purpose other than home purchase, home improvement, refinancing, or cash-out refinancing. Section 1003.4(a)(3) also requires an institution to report a covered loan or application as for a purpose other than home purchase, home improvement, refinancing, or cash-out refinancing if it is a refinancing but, under the terms of the agreement, the financial institution was unconditionally obligated to refinance the obligation subject to conditions within the borrower's control.
                        </P>
                        <P>
                            5. 
                            <E T="03">Purpose—business or commercial purpose loans.</E>
                             If a covered loan primarily is for a business or commercial purpose as described in § 1003.3(c)(10) and comment 3(c)(10)-2 and is a home purchase loan, home improvement loan, or a refinancing, § 1003.4(a)(3) requires the financial institution to report the applicable loan purpose. If a loan primarily is for a business or commercial purpose but is not a home purchase loan, home improvement loan, or a refinancing, the loan is an excluded transaction under § 1003.3(c)(10).
                        </P>
                        <P>
                            6. 
                            <E T="03">Purpose—purchased loans.</E>
                             For purchased covered loans where origination took place prior to January 1, 2018, a financial institution complies with § 1003.4(a)(3) by reporting that the requirement is not applicable.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(4)</HD>
                        <P>
                            1. 
                            <E T="03">Request under a preapproval program.</E>
                             Section 1003.4(a)(4) requires a financial institution to report whether an application or covered loan involved a request for a preapproval of a home purchase loan under a preapproval program as defined by § 1003.2(b)(2). If an application or covered loan did not involve a request for a 
                            <PRTPAGE P="21024"/>
                            preapproval of a home purchase loan under a preapproval program as defined by § 1003.2(b)(2), a financial institution complies with § 1003.4(a)(4) by reporting that the application or covered loan did not involve such a request, regardless of whether the institution has such a program and the applicant did not apply through that program or the institution does not have a preapproval program as defined by § 1003.2(b)(2).
                        </P>
                        <P>
                            2. 
                            <E T="03">Scope of requirement.</E>
                             A financial institution reports that the application or covered loan did not involve a preapproval request for a purchased covered loan; an application or covered loan for any purpose other than a home purchase loan; an application for a home purchase loan or a covered loan that is a home purchase loan secured by a multifamily dwelling; an application or covered loan that is an open-end line of credit or a reverse mortgage; or an application that is denied, withdrawn by the applicant, or closed for incompleteness.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(5)</HD>
                        <P>
                            1. 
                            <E T="03">Modular homes and prefabricated components.</E>
                             Covered loans or applications related to modular homes should be reported with a construction method of site-built, regardless of whether they are on-frame or off-frame modular homes. Modular homes comply with local or other recognized buildings codes rather than standards established by the National Manufactured Housing Construction and Safety Standards Act, 42 U.S.C. 5401 
                            <E T="03">et seq.</E>
                             Modular homes are not required to have HUD Certification Labels under 24 CFR 3280.11 or data plates under 24 CFR 3280.5. Modular homes may have a certification from a State licensing agency that documents compliance with State or other applicable building codes. On-frame modular homes are constructed on permanent metal chassis similar to those used in manufactured homes. The chassis are not removed on site and are secured to the foundation. Off-frame modular homes typically have floor construction similar to the construction of other site-built homes, and the construction typically includes wooden floor joists and does not include permanent metal chassis. Dwellings built using prefabricated components assembled at the dwelling's permanent site should also be reported with a construction method of site-built.
                        </P>
                        <P>
                            2. 
                            <E T="03">Multifamily dwelling.</E>
                             For a covered loan or an application for a covered loan related to a multifamily dwelling, the financial institution should report the construction method as site-built unless the multifamily dwelling is a manufactured home community, in which case the financial institution should report the construction method as manufactured home.
                        </P>
                        <P>
                            3. 
                            <E T="03">Multiple properties.</E>
                             See comment 4(a)(9)-2 regarding transactions involving multiple properties with more than one property taken as security.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(6)</HD>
                        <P>
                            1. 
                            <E T="03">Multiple properties.</E>
                             See comment 4(a)(9)-2 regarding transactions involving multiple properties with more than one property taken as security.
                        </P>
                        <P>
                            2. 
                            <E T="03">Principal residence.</E>
                             Section 1003.4(a)(6) requires a financial institution to identify whether the property to which the covered loan or application relates is or will be used as a residence that the applicant or borrower physically occupies and uses, or will occupy and use, as his or her principal residence. For purposes of § 1003.4(a)(6), an applicant or borrower can have only one principal residence at a time. Thus, a vacation or other second home would not be a principal residence. However, if an applicant or borrower buys or builds a new dwelling that will become the applicant's or borrower's principal residence within a year or upon the completion of construction, the new dwelling is considered the principal residence for purposes of applying this definition to a particular transaction.
                        </P>
                        <P>
                            3. 
                            <E T="03">Second residences.</E>
                             Section 1003.4(a)(6) requires a financial institution to identify whether the property to which the loan or application relates is or will be used as a second residence. For purposes of § 1003.4(a)(6), a property is a second residence of an applicant or borrower if the property is or will be occupied by the applicant or borrower for a portion of the year and is not the applicant's or borrower's principal residence. For example, if a person purchases a property, occupies the property for a portion of the year, and rents the property for the remainder of the year, the property is a second residence for purposes of § 1003.4(a)(6). Similarly, if a couple occupies a property near their place of employment on weekdays, but the couple returns to their principal residence on weekends, the property near the couple's place of employment is a second residence for purposes of § 1003.4(a)(6).
                        </P>
                        <P>
                            4. 
                            <E T="03">Investment properties.</E>
                             Section 1003.4(a)(6) requires a financial institution to identify whether the property to which the covered loan or application relates is or will be used as an investment property. For purposes of § 1003.4(a)(6), a property is an investment property if the borrower does not, or the applicant will not, occupy the property. For example, if a person purchases a property, does not occupy the property, and generates income by renting the property, the property is an investment property for purposes of § 1003.4(a)(6). Similarly, if a person purchases a property, does not occupy the property, and does not generate income by renting the property, but intends to generate income by selling the property, the property is an investment property for purposes of § 1003.4(a)(6). Section 1003.4(a)(6) requires a financial institution to identify a property as an investment property if the borrower or applicant does not or will not occupy the property, even if the borrower or applicant does not consider the property as owned for investment purposes. For example, if a corporation purchases a property that is a dwelling under § 1003.2(f), that it does not occupy, but that is for the long-term residential use of its employees, the property is an investment property for purposes of § 1003.4(a)(6), even if the corporation considers the property as owned for business purposes rather than investment purposes, does not generate income by renting the property, and does not intend to generate income by selling the property at some point in time. If the property is for transitory use by employees, the property would not be considered a dwelling under § 1003.2(f). 
                            <E T="03">See</E>
                             comment 2(f)-3.
                        </P>
                        <P>
                            5. 
                            <E T="03">Purchased covered loans.</E>
                             For purchased covered loans, a financial institution may report principal residence unless the loan documents or application indicate that the property will not be occupied as a principal residence.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(7)</HD>
                        <P>
                            1. 
                            <E T="03">Covered loan amount—counteroffer.</E>
                             If an applicant accepts a counteroffer for an amount different from the amount for which the applicant applied, the financial institution reports the covered loan amount granted. If an applicant does not accept a counteroffer or fails to respond, the institution reports the amount initially requested.
                        </P>
                        <P>
                            2. 
                            <E T="03">Covered loan amount—application approved but not accepted or preapproval request approved but not accepted.</E>
                             A financial institution reports the covered loan amount that was approved.
                        </P>
                        <P>
                            3. 
                            <E T="03">Covered loan amount—preapproval request denied, application denied, closed for incompleteness or withdrawn.</E>
                             For a preapproval request that was denied, and for an application that was denied, closed for incompleteness, or withdrawn, a financial institution reports the amount for which the applicant applied.
                        </P>
                        <P>
                            4. 
                            <E T="03">Covered loan amount—multiple-purpose loan.</E>
                             A financial institution reports the entire amount of the covered loan, even if only a part of the proceeds is intended for home purchase, home improvement, or refinancing.
                        </P>
                        <P>
                            5. 
                            <E T="03">Covered loan amount—closed-end mortgage loan.</E>
                             For a closed-end mortgage loan, other than a purchased loan, an assumption, or a reverse mortgage, a financial institution reports the amount to be repaid as disclosed on the legal obligation. For a purchased closed-end mortgage loan or an assumption of a closed-end mortgage loan, a financial institution reports the unpaid principal balance at the time of purchase or assumption.
                        </P>
                        <P>
                            6. 
                            <E T="03">Covered loan amount—open-end line of credit.</E>
                             For an open-end line of credit, a financial institution reports the entire amount of credit available to the borrower under the terms of the open-end plan, including a purchased open-end line of credit and an assumption of an open-end line of credit, but not for a reverse mortgage open-end line of credit.
                        </P>
                        <P>
                            7. 
                            <E T="03">Covered loan amount—refinancing.</E>
                             For a refinancing, a financial institution reports the amount of credit extended under the terms of the new debt obligation.
                        </P>
                        <P>
                            8. 
                            <E T="03">Covered loan amount—home improvement loan.</E>
                             A financial institution reports the entire amount of a home improvement loan, even if only a part of the proceeds is intended for home improvement.
                        </P>
                        <P>
                            9. 
                            <E T="03">Covered loan amount—non-federally insured reverse mortgage.</E>
                             A financial institution reports the initial principal limit of a non-federally insured reverse mortgage as set forth in § 1003.4(a)(7)(iii).
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(8)(i)</HD>
                        <P>
                            1. 
                            <E T="03">Action taken—covered loan originated.</E>
                             A financial institution reports that the covered loan was originated if the financial 
                            <PRTPAGE P="21025"/>
                            institution made a credit decision approving the application before closing or account opening and that credit decision results in an extension of credit. The same is true for an application that began as a request for a preapproval that subsequently results in a covered loan being originated. 
                            <E T="03">See</E>
                             comments 4(a)-2 through -4 for guidance on transactions in which more than one institution is involved.
                        </P>
                        <P>
                            2. 
                            <E T="03">Action taken—covered loan purchased.</E>
                             A financial institution reports that the covered loan was purchased if the covered loan was purchased by the financial institution after closing or account opening and the financial institution did not make a credit decision on the application prior to closing or account opening, or if the financial institution did make a credit decision on the application prior to closing or account opening, but is repurchasing the loan from another entity that the loan was sold to. 
                            <E T="03">See</E>
                             comment 4(a)-5. 
                            <E T="03">See</E>
                             comments 4(a)-2 through -4 for guidance on transactions in which more than one financial institution is involved.
                        </P>
                        <P>
                            3. 
                            <E T="03">Action taken—application approved but not accepted.</E>
                             A financial institution reports application approved but not accepted if the financial institution made a credit decision approving the application before closing or account opening, subject solely to outstanding conditions that are customary commitment or closing conditions, but the applicant or the party that initially received the application fails to respond to the financial institution's approval within the specified time, or the closed-end mortgage loan was not otherwise consummated or the account was not otherwise opened. 
                            <E T="03">See</E>
                             comment 4(a)(8)(i)-13.
                        </P>
                        <P>
                            4. 
                            <E T="03">Action taken—application denied.</E>
                             A financial institution reports that the application was denied if it made a credit decision denying the application before an applicant withdraws the application or the file is closed for incompleteness. 
                            <E T="03">See</E>
                             comments 4(a)-2 through -4 for guidance on transactions in which more than one institution is involved.
                        </P>
                        <P>
                            5. 
                            <E T="03">Action taken—application withdrawn.</E>
                             A financial institution reports that the application was withdrawn when the application is expressly withdrawn by the applicant before the financial institution makes a credit decision denying the application, before the financial institution makes a credit decision approving the application, or before the file is closed for incompleteness. A financial institution also reports application withdrawn if the financial institution provides a conditional approval specifying underwriting or creditworthiness conditions, pursuant to comment 4(a)(8)(i)-13, and the application is expressly withdrawn by the applicant before the applicant satisfies all specified underwriting or creditworthiness conditions. A preapproval request that is withdrawn is not reportable under HMDA. 
                            <E T="03">See</E>
                             § 1003.4(a).
                        </P>
                        <P>
                            6. 
                            <E T="03">Action taken—file closed for incompleteness.</E>
                             A financial institution reports that the file was closed for incompleteness if the financial institution sent a written notice of incompleteness under Regulation B, 12 CFR 1002.9(c)(2), and the applicant did not respond to the request for additional information within the period of time specified in the notice before the applicant satisfies all underwriting or creditworthiness conditions. 
                            <E T="03">See</E>
                             comment 4(a)(8)(i)-13. If a financial institution then provides a notification of adverse action on the basis of incompleteness under Regulation B, 12 CFR 1002.9(c)(1)(i), the financial institution may report the action taken as either file closed for incompleteness or application denied. A preapproval request that is closed for incompleteness is not reportable under HMDA. 
                            <E T="03">See</E>
                             § 1003.4(a) and comment 4(a)-1.ii.
                        </P>
                        <P>
                            7. 
                            <E T="03">Action taken—preapproval request denied.</E>
                             A financial institution reports that the preapproval request was denied if the application was a request for a preapproval under a preapproval program as defined in § 1003.2(b)(2) and the institution made a credit decision denying the preapproval request.
                        </P>
                        <P>
                            8. 
                            <E T="03">Action taken—preapproval request approved but not accepted.</E>
                             A financial institution reports that the preapproval request was approved but not accepted if the application was a request for a preapproval under a preapproval program as defined in § 1003.2(b)(2) and the institution made a credit decision approving the preapproval request but the application did not result in a covered loan originated by the financial institution.
                        </P>
                        <P>
                            9. 
                            <E T="03">Action taken—counteroffers.</E>
                             If a financial institution makes a counteroffer to lend on terms different from the applicant's initial request (for example, for a shorter loan maturity, with a different interest rate, or in a different amount) and the applicant declines to proceed with the counteroffer or fails to respond, the institution reports the action taken as a denial on the original terms requested by the applicant. If the applicant agrees to proceed with consideration of the financial institution's counteroffer, the financial institution reports the action taken as the disposition of the application based on the terms of the counteroffer. For example, assume a financial institution makes a counteroffer, the applicant agrees to proceed with the terms of the counteroffer, and the financial institution then makes a credit decision approving the application conditional on satisfying underwriting or creditworthiness conditions, and the applicant expressly withdraws before satisfying all underwriting or creditworthiness conditions and before the institution denies the application or closes the file for incompleteness. The financial institution reports that the action taken as application withdrawn in accordance with comment 4(a)(8)(i)-13.i. Similarly, assume a financial institution makes a counteroffer, the applicant agrees to proceed with consideration of the counteroffer, and the financial institution provides a conditional approval stating the conditions to be met to originate the counteroffer. The financial institution reports the action taken on the application in accordance with comment 4(a)(8)(i)-13 regarding conditional approvals.
                        </P>
                        <P>
                            10. 
                            <E T="03">Action taken—rescinded transactions.</E>
                             If a borrower rescinds a transaction after closing and before a financial institution is required to submit its loan/application register containing the information for the transaction under § 1003.5(a), the institution reports the transaction as an application that was approved but not accepted.
                        </P>
                        <P>
                            11. 
                            <E T="03">Action taken—purchased covered loans.</E>
                             An institution reports the covered loans that it purchased during the calendar year. An institution does not report the covered loans that it declined to purchase, unless, as discussed in comments 4(a)-2 through -4, the institution reviewed the application prior to closing, in which case it reports the application or covered loan according to comments 4(a)-2 through -4.
                        </P>
                        <P>
                            12. 
                            <E T="03">Action taken—repurchased covered loans.</E>
                             See comment 4(a)-5 regarding reporting requirements when a covered loan is repurchased by the originating financial institution.
                        </P>
                        <P>
                            13. 
                            <E T="03">Action taken—conditional approvals.</E>
                             If an institution issues an approval other than a commitment pursuant to a preapproval program as defined under § 1003.2(b)(2), and that approval is subject to the applicant meeting certain conditions, the institution reports the action taken as provided below dependent on whether the conditions are solely customary commitment or closing conditions or if the conditions include any underwriting or creditworthiness conditions.
                        </P>
                        <P>
                            i. 
                            <E T="03">Action taken examples.</E>
                             If the approval is conditioned on satisfying underwriting or creditworthiness conditions and they are not met, the institution reports the action taken as a denial. If, however, the conditions involve submitting additional information about underwriting or creditworthiness that the institution needs to make the credit decision, and the institution has sent a written notice of incompleteness under Regulation B, 12 CFR 1002.9(c)(2), and the applicant did not respond within the period of time specified in the notice, the institution reports the action taken as file closed for incompleteness. 
                            <E T="03">See</E>
                             comment 4(a)(8)(i)-6. If the conditions are solely customary commitment or closing conditions and the conditions are not met, the institution reports the action taken as approved but not accepted. If all the conditions (underwriting, creditworthiness, or customary commitment or closing conditions) are satisfied and the institution agrees to extend credit but the covered loan is not originated, the institution reports the action taken as application approved but not accepted. If the applicant expressly withdraws before satisfying all underwriting or creditworthiness conditions and before the institution denies the application or closes the file for incompleteness, the institution reports the action taken as application withdrawn. If all underwriting and creditworthiness conditions have been met, and the outstanding conditions are solely customary commitment or closing conditions and the applicant expressly withdraws before the covered loan is originated, the institution reports the action taken as application approved but not accepted.
                        </P>
                        <P>
                            ii. 
                            <E T="03">Customary commitment or closing conditions.</E>
                             Customary commitment or closing conditions include, for example: a clear-title requirement, an acceptable property survey, acceptable title insurance 
                            <PRTPAGE P="21026"/>
                            binder, clear termite inspection, a subordination agreement from another lienholder, and, where the applicant plans to use the proceeds from the sale of one home to purchase another, a settlement statement showing adequate proceeds from the sale.
                        </P>
                        <P>
                            iii. 
                            <E T="03">Underwriting or creditworthiness conditions.</E>
                             Underwriting or creditworthiness conditions include, for example: conditions that constitute a counter-offer, such as a demand for a higher down-payment; satisfactory debt-to-income or loan-to-value ratios, a determination of need for private mortgage insurance, or a satisfactory appraisal requirement; or verification or confirmation, in whatever form the institution requires, that the applicant meets underwriting conditions concerning applicant creditworthiness, including documentation or verification of income or assets.
                        </P>
                        <P>
                            14. 
                            <E T="03">Action taken—pending applications.</E>
                             An institution does not report any covered loan application still pending at the end of the calendar year; it reports that application on its loan/application register for the year in which final action is taken.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(8)(ii)</HD>
                        <P>
                            1. 
                            <E T="03">Action taken date—general.</E>
                             A financial institution reports the date of the action taken.
                        </P>
                        <P>
                            2. 
                            <E T="03">Action taken date—applications denied and files closed for incompleteness.</E>
                             For applications, including requests for a preapproval, that are denied or for files closed for incompleteness, the financial institution reports either the date the action was taken or the date the notice was sent to the applicant.
                        </P>
                        <P>
                            3. 
                            <E T="03">Action taken date—application withdrawn.</E>
                             For applications withdrawn, the financial institution may report the date the express withdrawal was received or the date shown on the notification form in the case of a written withdrawal.
                        </P>
                        <P>
                            4. 
                            <E T="03">Action taken date—approved but not accepted.</E>
                             For a covered loan approved by an institution but not accepted by the applicant, the institution reports any reasonable date, such as the approval date, the deadline for accepting the offer, or the date the file was closed. Although an institution need not choose the same approach for its entire HMDA submission, it should be generally consistent (such as by routinely using one approach within a particular division of the institution or for a category of covered loans).
                        </P>
                        <P>
                            5. 
                            <E T="03">Action taken date—originations.</E>
                             For covered loan originations, including a preapproval request that leads to an origination by the financial institution, an institution generally reports the closing or account opening date. For covered loan originations that an institution acquires from a party that initially received the application, the institution reports either the closing or account opening date, or the date the institution acquired the covered loan from the party that initially received the application. If the disbursement of funds takes place on a date later than the closing or account opening date, the institution may use the date of initial disbursement. For a construction/permanent covered loan, the institution reports either the closing or account opening date, or the date the covered loan converts to the permanent financing. Although an institution need not choose the same approach for its entire HMDA submission, it should be generally consistent (such as by routinely using one approach within a particular division of the institution or for a category of covered loans). Notwithstanding this flexibility regarding the use of the closing or account opening date in connection with reporting the date action was taken, the institution must report the origination as occurring in the year in which the origination goes to closing or the account is opened.
                        </P>
                        <P>
                            6. 
                            <E T="03">Action taken date—loan purchased.</E>
                             For covered loans purchased, a financial institution reports the date of purchase.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(9)</HD>
                        <P>
                            1. 
                            <E T="03">Multiple properties with one property taken as security.</E>
                             If a covered loan is related to more than one property, but only one property is taken as security (or, in the case of an application, proposed to be taken as security), a financial institution reports the information required by § 1003.4(a)(9) for the property taken as or proposed to be taken as security. A financial institution does not report the information required by § 1003.4(a)(9) for the property or properties related to the loan that are not taken as or proposed to be taken as security. For example, if a covered loan is secured by property A, and the proceeds are used to purchase or rehabilitate (or to refinance home purchase or home improvement loans related to) property B, the institution reports the information required by § 1003.4(a)(9) for property A and does not report the information required by § 1003.4(a)(9) for property B.
                        </P>
                        <P>
                            2. 
                            <E T="03">Multiple properties with more than one property taken as security.</E>
                             If more than one property is taken or, in the case of an application, proposed to be taken as security for a single covered loan, a financial institution reports the covered loan or application in a single entry on its loan/application register and provides the information required by § 1003.4(a)(9) for one of the properties taken as security that contains a dwelling. A financial institution does not report information about the other properties taken as security. If an institution is required to report specific information about the property identified in § 1003.4(a)(9), the institution reports the information that relates to the property identified in § 1003.4(a)(9) (or, if the transaction is partially exempt under § 1003.3(d) and no data are reported pursuant to § 1003.4(a)(9), the property that the institution would have identified in § 1003.4(a)(9) if the transaction were not partially exempt). For example, Financial Institution A originated a covered loan that is secured by both property A and property B, each of which contains a dwelling. Financial Institution A reports the loan as one entry on its loan/application register, reporting the information required by § 1003.4(a)(9) for either property A or property B. If Financial Institution A elects to report the information required by § 1003.4(a)(9) about property A, Financial Institution A also reports the information required by § 1003.4(a)(5), (6), (14), (29), and (30) related to property A. For aspects of the entries that do not refer to the property identified in § 1003.4(a)(9) (
                            <E T="03">i.e.,</E>
                             § 1003.4(a)(1) through (4), (7), (8), (10) through (13), (15) through (28), and (31) through (38)), Financial Institution A reports the information applicable to the covered loan or application and not information that relates only to the property identified in § 1003.4(a)(9).
                        </P>
                        <P>
                            3. 
                            <E T="03">Multifamily dwellings.</E>
                             A single multifamily dwelling may have more than one postal address. For example, three apartment buildings, each with a different street address, comprise a single multifamily dwelling that secures a covered loan. For the purposes of § 1003.4(a)(9), a financial institution reports the information required by § 1003.4(a)(9) in the same manner described in comment 4(a)(9)-2.
                        </P>
                        <P>
                            4. 
                            <E T="03">Loans purchased from another institution.</E>
                             The requirement to report the property location information required by § 1003.4(a)(9) applies not only to applications and originations but also to purchased covered loans.
                        </P>
                        <P>
                            5. 
                            <E T="03">Manufactured home.</E>
                             If the site of a manufactured home has not been identified, a financial institution complies by reporting that the information required by § 1003.4(a)(9) is not applicable.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(9)(i)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Except for partially exempt transactions under § 1003.3(d), § 1003.4(a)(9)(i) requires a financial institution to report the property address of the location of the property securing a covered loan or, in the case of an application, proposed to secure a covered loan. The address should correspond to the property identified on the legal obligation related to the covered loan. For applications that did not result in an origination, the address should correspond to the location of the property proposed to secure the loan as identified by the applicant. For example, assume a loan is secured by a property located at 123 Main Street, and the applicant's or borrower's mailing address is a post office box. The financial institution should not report the post office box, and should report 123 Main Street.
                        </P>
                        <P>
                            2. 
                            <E T="03">Property address—format.</E>
                             A financial institution complies with the requirements in § 1003.4(a)(9)(i) by reporting the following information about the physical location of the property securing the loan.
                        </P>
                        <P>
                            i. 
                            <E T="03">Street address.</E>
                             When reporting the street address of the property, a financial institution complies by including, as applicable, the primary address number, the predirectional, the street name, street prefixes and/or suffixes, the postdirectional, the secondary address identifier, and the secondary address, as applicable. For example, 100 N Main ST Apt 1.
                        </P>
                        <P>
                            ii. 
                            <E T="03">City name.</E>
                             A financial institution complies by reporting the name of the city in which the property is located.
                        </P>
                        <P>
                            iii. 
                            <E T="03">State name.</E>
                             A financial institution complies by reporting the two letter State code for the State in which the property is located, using the U.S. Postal Service official State abbreviations.
                            <PRTPAGE P="21027"/>
                        </P>
                        <P>
                            iv. 
                            <E T="03">Zip Code.</E>
                             A financial institution complies by reporting the five or nine digit Zip Code in which the property is located.
                        </P>
                        <P>
                            3. 
                            <E T="03">Property address—not applicable.</E>
                             A financial institution complies with § 1003.4(a)(9)(i) by reporting that the requirement is not applicable if the property address of the property securing the covered loan is not known. For example, if the property did not have a property address at closing or if the applicant did not provide the property address of the property to the financial institution before the application was denied, withdrawn, or closed for incompleteness, the financial institution complies with § 1003.4(a)(9)(i) by reporting that the requirement is not applicable.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(9)(ii)</HD>
                        <P>
                            1. 
                            <E T="03">Optional reporting.</E>
                             Section 1003.4(a)(9)(ii) requires a financial institution to report the State, county, and census tract of the property securing the covered loan or, in the case of an application, proposed to secure the covered loan if the property is located in an MSA or MD in which the financial institution has a home or branch office or if the institution is subject to § 1003.4(e). Section 1003.4(a)(9)(ii)(C) further limits the requirement to report census tract to covered loans secured by or applications proposed to be secured by properties located in counties with a population of more than 30,000 according to the most recent decennial census conducted by the U.S. Census Bureau. For transactions for which State, county, or census tract reporting is not required under § 1003.4(a)(9)(ii) or (e), financial institutions may report that the requirement is not applicable, or they may voluntarily report the State, county, or census tract information.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(9)(ii)(A)</HD>
                        <P>
                            1. 
                            <E T="03">Applications—State not provided.</E>
                             When reporting an application, a financial institution complies with § 1003.4(a)(9)(ii)(A) by reporting that the requirement is not applicable if the State in which the property is located was not known before the application was denied, withdrawn, or closed for incompleteness.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(9)(ii)(B)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             A financial institution complies by reporting the five-digit Federal Information Processing Standards (FIPS) numerical county code.
                        </P>
                        <P>
                            2. 
                            <E T="03">Applications—county not provided.</E>
                             When reporting an application, a financial institution complies with § 1003.4(a)(9)(ii)(B) by reporting that the requirement is not applicable if the county in which the property is located was not known before the application was denied, withdrawn, or closed for incompleteness.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(9)(ii)(C)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Census tract numbers are defined by the U.S. Census Bureau. A financial institution complies with § 1003.4(a)(9)(ii)(C) if it uses the boundaries and codes in effect on January 1 of the calendar year covered by the loan/application register that it is reporting.
                        </P>
                        <P>
                            2. 
                            <E T="03">Applications—census tract not provided.</E>
                             When reporting an application, a financial institution complies with § 1003.4(a)(9)(ii)(C) by reporting that the requirement is not applicable if the census tract in which the property is located was not known before the application was denied, withdrawn, or closed for incompleteness.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(10)(i)</HD>
                        <P>
                            1. 
                            <E T="03">Applicant data—general.</E>
                             Refer to appendix B to this part for instructions on collection of an applicant's ethnicity, race, and sex.
                        </P>
                        <P>
                            2. 
                            <E T="03">Transition rule for applicant data collected prior to January 1, 2018.</E>
                             If a financial institution receives an application prior to January 1, 2018, but final action is taken on or after January 1, 2018, the financial institution complies with § 1003.4(a)(10)(i) and (b) if it collects the information in accordance with the requirements in effect at the time the information was collected. For example, if a financial institution receives an application on November 15, 2017, collects the applicant's ethnicity, race, and sex in accordance with the instructions in effect on that date, and takes final action on the application on January 5, 2018, the financial institution has complied with the requirements of § 1003.4(a)(10)(i) and (b), even though those instructions changed after the information was collected but before the date of final action. However, if, in this example, the financial institution collected the applicant's ethnicity, race, and sex on or after January 1, 2018, § 1003.4(a)(10)(i) and (b) requires the financial institution to collect the information in accordance with the amended instructions.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(10)(ii)</HD>
                        <P>
                            1. 
                            <E T="03">Applicant data—completion by financial institution.</E>
                             A financial institution complies with § 1003.4(a)(10)(ii) by reporting the applicant's age, as of the application date under § 1003.4(a)(1)(ii), as the number of whole years derived from the date of birth as shown on the application form. For example, if an applicant provides a date of birth of 01/15/1970 on the application form that the financial institution receives on 01/14/2015, the institution reports 44 as the applicant's age.
                        </P>
                        <P>
                            2. 
                            <E T="03">Applicant data—co-applicant.</E>
                             If there are no co-applicants, the financial institution reports that there is no co-applicant. If there is more than one co-applicant, the financial institution reports the age only for the first co-applicant listed on the application form. A co-applicant may provide an absent co-applicant's age on behalf of the absent co-applicant.
                        </P>
                        <P>
                            3. 
                            <E T="03">Applicant data—purchased loan.</E>
                             A financial institution complies with § 1003.4(a)(10)(ii) by reporting that the requirement is not applicable when reporting a purchased loan for which the institution chooses not to report the age.
                        </P>
                        <P>
                            4. 
                            <E T="03">Applicant data—non-natural person.</E>
                             A financial institution complies with § 1003.4(a)(10)(ii) by reporting that the requirement is not applicable if the applicant or co-applicant is not a natural person (for example, a corporation, partnership, or trust). For example, for a transaction involving a trust, a financial institution reports that the requirement to report the applicant's age is not applicable if the trust is the applicant. On the other hand, if the applicant is a natural person, and is the beneficiary of a trust, a financial institution reports the applicant's age.
                        </P>
                        <P>
                            5. 
                            <E T="03">Applicant data—guarantor.</E>
                             For purposes of § 1003.4(a)(10)(ii), if a covered loan or application includes a guarantor, a financial institution does not report the guarantor's age.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(10)(iii)</HD>
                        <P>
                            1. 
                            <E T="03">Income data—income relied on.</E>
                             When a financial institution evaluates income as part of a credit decision, it reports the gross annual income relied on in making the credit decision. For example, if an institution relies on an applicant's salary to compute a debt-to-income ratio but also relies on the applicant's annual bonus to evaluate creditworthiness, the institution reports the salary and the bonus to the extent relied upon. If an institution relies on only a portion of an applicant's income in its determination, it does not report that portion of income not relied on. For example, if an institution, pursuant to lender and investor guidelines, does not rely on an applicant's commission income because it has been earned for less than 12 months, the institution does not include the applicant's commission income in the income reported. Likewise, if an institution relies on the verified gross income of the applicant in making the credit decision, then the institution reports the verified gross income. Similarly, if an institution relies on the income of a cosigner to evaluate creditworthiness, the institution includes the cosigner's income to the extent relied upon. An institution, however, does not include the income of a guarantor who is only secondarily liable.
                        </P>
                        <P>
                            2. 
                            <E T="03">Income data—co-applicant.</E>
                             If two persons jointly apply for a covered loan and both list income on the application, but the financial institution relies on the income of only one applicant in evaluating creditworthiness, the institution reports only the income relied on.
                        </P>
                        <P>
                            3. 
                            <E T="03">Income data—loan to employee.</E>
                             A financial institution complies with § 1003.4(a)(10)(iii) by reporting that the requirement is not applicable for a covered loan to, or an application from, its employee to protect the employee's privacy, even though the institution relied on the employee's income in making the credit decision.
                        </P>
                        <P>
                            4. 
                            <E T="03">Income data—assets.</E>
                             A financial institution does not include as income amounts considered in making a credit decision based on factors that an institution relies on in addition to income, such as amounts derived from underwriting calculations of the potential annuitization or depletion of an applicant's remaining assets. Actual distributions from retirement accounts or other assets that are relied on by the financial institution as income should be reported as income. The interpretation of income in this paragraph does not affect § 1003.4(a)(23), which requires, except for purchased covered loans, the collection of the ratio of the applicant's or borrower's total monthly debt to the total monthly income relied on in making the credit decision.
                            <PRTPAGE P="21028"/>
                        </P>
                        <P>
                            5. 
                            <E T="03">Income data—credit decision not made.</E>
                             Section 1003.4(a)(10)(iii) requires a financial institution to report the gross annual income relied on in processing the application if a credit decision was not made. For example, assume an institution received an application that included an applicant's self-reported income, but the application was withdrawn before a credit decision that would have considered income was made. The financial institution reports the income information relied on in processing the application at the time that the application was withdrawn or the file was closed for incompleteness.
                        </P>
                        <P>
                            6. 
                            <E T="03">Income data—credit decision not requiring consideration of income.</E>
                             A financial institution complies with § 1003.4(a)(10)(iii) by reporting that the requirement is not applicable if the application did not or would not have required a credit decision that considered income under the financial institution's policies and procedures. For example, if the financial institution's policies and procedures do not consider income for a streamlined refinance program, the institution reports that the requirement is not applicable, even if the institution received income information from the applicant.
                        </P>
                        <P>
                            7. 
                            <E T="03">Income data—non-natural person.</E>
                             A financial institution reports that the requirement is not applicable when the applicant or co-applicant is not a natural person (
                            <E T="03">e.g.,</E>
                             a corporation, partnership, or trust). For example, for a transaction involving a trust, a financial institution reports that the requirement to report income data is not applicable if the trust is the applicant. On the other hand, if the applicant is a natural person, and is the beneficiary of a trust, a financial institution is required to report the information described in § 1003.4(a)(10)(iii).
                        </P>
                        <P>
                            8. 
                            <E T="03">Income data—multifamily properties.</E>
                             A financial institution complies with § 1003.4(a)(10)(iii) by reporting that the requirement is not applicable when the covered loan is secured by, or application is proposed to be secured by, a multifamily dwelling.
                        </P>
                        <P>
                            9. 
                            <E T="03">Income data—purchased loans.</E>
                             A financial institution complies with § 1003.4(a)(10)(iii) by reporting that the requirement is not applicable when reporting a purchased covered loan for which the institution chooses not to report the income.
                        </P>
                        <P>
                            10. 
                            <E T="03">Income data—rounding.</E>
                             A financial institution complies by reporting the dollar amount of the income in thousands, rounded to the nearest thousand ($500 rounds up to the next $1,000). For example, $35,500 is reported as 36.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(11)</HD>
                        <P>
                            1. 
                            <E T="03">Type of purchaser—loan-participation interests sold to more than one entity.</E>
                             A financial institution that originates a covered loan, and then sells it to more than one entity, reports the “type of purchaser” based on the entity purchasing the greatest interest, if any. For purposes of § 1003.4(a)(11), if a financial institution sells some interest or interests in a covered loan but retains a majority interest in that loan, it does not report the sale.
                        </P>
                        <P>
                            2. 
                            <E T="03">Type of purchaser—swapped covered loans.</E>
                             Covered loans “swapped” for mortgage-backed securities are to be treated as sales; the purchaser is the entity receiving the covered loans that are swapped.
                        </P>
                        <P>
                            3. 
                            <E T="03">Type of purchaser—affiliate institution.</E>
                             For purposes of complying with § 1003.4(a)(11), the term “affiliate” means any company that controls, is controlled by, or is under common control with, another company, as set forth in the Bank Holding Company Act of 1956 (12 U.S.C. 1841 
                            <E T="03">et seq.</E>
                            ).
                        </P>
                        <P>
                            4. 
                            <E T="03">Type of purchaser—private securitizations.</E>
                             A financial institution that knows or reasonably believes that the covered loan it is selling will be securitized by the entity purchasing the covered loan, other than by one of the government-sponsored enterprises, reports the purchasing entity type as a private securitizer regardless of the type or affiliation of the purchasing entity. Knowledge or reasonable belief could, for example, be based on the purchase agreement or other related documents, the financial institution's previous transactions with the purchaser, or the purchaser's role as a securitizer (such as an investment bank). If a financial institution selling a covered loan does not know or reasonably believe that the purchaser will securitize the loan, and the seller knows that the purchaser frequently holds or disposes of loans by means other than securitization, then the financial institution should report the covered loan as purchased by, as appropriate, a commercial bank, savings bank, savings association, life insurance company, credit union, mortgage company, finance company, affiliate institution, or other type of purchaser.
                        </P>
                        <P>
                            5. 
                            <E T="03">Type of purchaser—mortgage company.</E>
                             For purposes of complying with § 1003.4(a)(11), a mortgage company means a nondepository institution that purchases covered loans and typically originates such loans. A mortgage company might be an affiliate or a subsidiary of a bank holding company or thrift holding company, or it might be an independent mortgage company. Regardless, a financial institution reports the purchasing entity type as a mortgage company, unless the mortgage company is an affiliate of the seller institution, in which case the seller institution should report the loan as purchased by an affiliate institution.
                        </P>
                        <P>
                            6. 
                            <E T="03">Purchases by subsidiaries.</E>
                             A financial institution that sells a covered loan to its subsidiary that is a commercial bank, savings bank, or savings association, should report the covered loan as purchased by a commercial bank, savings bank, or savings association. A financial institution that sells a covered loan to its subsidiary that is a life insurance company, should report the covered loan as purchased by a life insurance company. A financial institution that sells a covered loan to its subsidiary that is a credit union, mortgage company, or finance company, should report the covered loan as purchased by a credit union, mortgage company, or finance company. If the subsidiary that purchases the covered loan is not a commercial bank, savings bank, savings association, life insurance company, credit union, mortgage company, or finance company, the seller institution should report the loan as purchased by other type of purchaser. The financial institution should report the covered loan as purchased by an affiliate institution when the subsidiary is an affiliate of the seller institution.
                        </P>
                        <P>
                            7. 
                            <E T="03">Type of purchaser—bank holding company or thrift holding company.</E>
                             When a financial institution sells a covered loan to a bank holding company or thrift holding company (rather than to one of its subsidiaries), it should report the loan as purchased by other type of purchaser, unless the bank holding company or thrift holding company is an affiliate of the seller institution, in which case the seller institution should report the loan as purchased by an affiliate institution.
                        </P>
                        <P>
                            8. 
                            <E T="03">Repurchased covered loans.</E>
                             See comment 4(a)-5 regarding reporting requirements when a covered loan is repurchased by the originating financial institution.
                        </P>
                        <P>
                            9. 
                            <E T="03">Type of purchaser—quarterly recording.</E>
                             For purposes of recording the type of purchaser within 30 calendar days after the end of the calendar quarter pursuant to § 1003.4(f), a financial institution records that the requirement is not applicable if the institution originated or purchased a covered loan and did not sell it during the calendar quarter for which the institution is recording the data. If the financial institution sells the covered loan in a subsequent quarter of the same calendar year, the financial institution records the type of purchaser on its loan/application register for the quarter in which the covered loan was sold. If a financial institution sells the covered loan in a succeeding year, the financial institution should not record the sale.
                        </P>
                        <P>
                            10. 
                            <E T="03">Type of purchaser—not applicable.</E>
                             A financial institution reports that the requirement is not applicable for applications that were denied, withdrawn, closed for incompleteness or approved but not accepted by the applicant; and for preapproval requests that were denied or approved but not accepted by the applicant. A financial institution also reports that the requirement is not applicable if the institution originated or purchased a covered loan and did not sell it during that same calendar year.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(12)</HD>
                        <P>
                            1. 
                            <E T="03">Average prime offer rate.</E>
                             Average prime offer rates are annual percentage rates derived from average interest rates and other loan pricing terms offered to borrowers by a set of creditors for mortgage loans that have low-risk pricing characteristics. Other loan pricing terms may include commonly used indices, margins, and initial fixed-rate periods for variable-rate transactions. Relevant pricing characteristics may include a consumer's credit history and transaction characteristics such as the loan-to-value ratio, owner-occupant status, and purpose of the transaction. To obtain average prime offer rates, the Bureau uses creditor data by transaction type.
                        </P>
                        <P>
                            2. 
                            <E T="03">Bureau tables.</E>
                             The Bureau publishes tables of current and historic average prime offer rates by transaction type on the FFIEC's website (
                            <E T="03">http://www.ffiec.gov/hmda</E>
                            ) and the Bureau's website (
                            <E T="03">https://www.consumerfinance.gov</E>
                            ). The Bureau calculates an annual percentage rate, consistent with Regulation Z (
                            <E T="03">see</E>
                             12 CFR 1026.22 and 12 CFR part 1026, appendix J), 
                            <PRTPAGE P="21029"/>
                            for each transaction type for which pricing terms are available from the creditor data described in comment 4(a)(12)-1. The Bureau uses loan pricing terms available in the creditor data and other information to estimate annual percentage rates for other types of transactions for which the creditor data are limited or not available. The Bureau publishes on the FFIEC's website and the Bureau's website the methodology it uses to arrive at these estimates. A financial institution may either use the average prime offer rates published by the Bureau or determine average prime offer rates itself by employing the methodology published on the FFIEC's website and the Bureau's website. A financial institution that determines average prime offer rates itself, however, is responsible for correctly determining the rates in accordance with the published methodology.
                        </P>
                        <P>
                            3. 
                            <E T="03">Rate spread calculation—annual percentage rate.</E>
                             The requirements of § 1003.4(a)(12)(i) refer to the covered loan's annual percentage rate. For closed-end mortgage loans, a financial institution complies with § 1003.4(a)(12)(i) by relying on the annual percentage rate for the covered loan, as calculated and disclosed pursuant to Regulation Z, 12 CFR 1026.18 or 1026.38. For open-end lines of credit, a financial institution complies with § 1003.4(a)(12)(i) by relying on the annual percentage rate for the covered loan, as calculated and disclosed pursuant to Regulation Z, 12 CFR 1026.6. If multiple annual percentage rates are calculated and disclosed pursuant to Regulation Z, 12 CFR 1026.6, a financial institution relies on the annual percentage rate in effect at the time of account opening. If an open-end line of credit has a variable-rate feature and a fixed-rate and -term payment option during the draw period, a financial institution relies on the annual percentage rate in effect at the time of account opening under the variable-rate feature, which would be a discounted initial rate if one is offered under the variable-rate feature. See comment 4(a)(12)-8 for guidance regarding the annual percentage rate a financial institution relies on in the case of an application or preapproval request that was approved but not accepted.
                        </P>
                        <P>
                            4. 
                            <E T="03">Rate spread calculation—comparable transaction.</E>
                             The rate spread calculation in § 1003.4(a)(12)(i) is defined by reference to a comparable transaction, which is determined according to the covered loan's amortization type (
                            <E T="03">i.e.,</E>
                             fixed- or variable-rate) and loan term. For covered loans that are open-end lines of credit, § 1003.4(a)(12)(i) requires a financial institution to identify the most closely comparable closed-end transaction. The tables of average prime offer rates published by the Bureau (see comment 4(a)(12)-2) provide additional detail about how to identify the comparable transaction.
                        </P>
                        <P>
                            i. 
                            <E T="03">Fixed-rate transactions.</E>
                             For fixed-rate covered loans, the term for identifying the comparable transaction is the transaction's maturity (
                            <E T="03">i.e.,</E>
                             the period until the last payment will be due under the closed-end mortgage loan contract or open-end line of credit agreement). If an open-end credit plan has a fixed rate but no definite plan length, a financial institution complies with § 1003.4(a)(12)(i) by using a 30-year fixed-rate loan as the most closely comparable closed-end transaction. Financial institutions may refer to the table on the FFIEC website entitled “Average Prime Offer Rates-Fixed” when identifying a comparable fixed-rate transaction.
                        </P>
                        <P>
                            ii. 
                            <E T="03">Variable-rate transactions.</E>
                             For variable-rate covered loans, the term for identifying the comparable transaction is the initial, fixed-rate period (
                            <E T="03">i.e.,</E>
                             the period until the first scheduled rate adjustment). For example, five years is the relevant term for a variable-rate transaction with a five-year, fixed-rate introductory period that is amortized over thirty years. Financial institutions may refer to the table on the FFIEC website entitled “Average Prime Offer Rates-Variable” when identifying a comparable variable-rate transaction. If an open-end line of credit has a variable rate and an optional, fixed-rate feature, a financial institution uses the rate table for variable-rate transactions.
                        </P>
                        <P>
                            iii. 
                            <E T="03">Term not in whole years.</E>
                             When a covered loan's term to maturity (or, for a variable-rate transaction, the initial fixed-rate period) is not in whole years, the financial institution uses the number of whole years closest to the actual loan term or, if the actual loan term is exactly halfway between two whole years, by using the shorter loan term. For example, for a loan term of ten years and three months, the relevant term is ten years; for a loan term of ten years and nine months, the relevant term is 11 years; for a loan term of ten years and six months, the relevant term is ten years. If a loan term includes an odd number of days, in addition to an odd number of months, the financial institution rounds to the nearest whole month, or rounds down if the number of odd days is exactly halfway between two months. The financial institution rounds to one year any covered loan with a term shorter than six months, including variable-rate covered loans with no initial, fixed-rate periods. For example, if an open-end covered loan has a rate that varies according to an index plus a margin, with no introductory, fixed-rate period, the transaction term is one year.
                        </P>
                        <P>
                            iv. 
                            <E T="03">Amortization period longer than loan term.</E>
                             If the amortization period of a covered loan is longer than the term of the transaction to maturity, § 1003.4(a)(12)(i) requires a financial institution to use the loan term to determine the applicable average prime offer rate. For example, assume a financial institution originates a closed-end, fixed-rate loan that has a term to maturity of five years and a thirty-year amortization period that results in a balloon payment. The financial institution complies with § 1003.4(a)(12)(i) by using the five-year loan term.
                        </P>
                        <P>
                            5. 
                            <E T="03">Rate-set date.</E>
                             The relevant date to use to determine the average prime offer rate for a comparable transaction is the date on which the interest rate was set by the financial institution for the final time before final action is taken (
                            <E T="03">i.e.,</E>
                             the application was approved but not accepted or the covered loan was originated).
                        </P>
                        <P>
                            i. 
                            <E T="03">Rate-lock agreement.</E>
                             If an interest rate is set pursuant to a “lock-in” agreement between the financial institution and the borrower, then the date on which the agreement fixes the interest rate is the date the rate was set. Except as provided in comment 4(a)(12)-5.ii, if a rate is reset after a lock-in agreement is executed (for example, because the borrower exercises a float-down option or the agreement expires), then the relevant date is the date the financial institution exercises discretion in setting the rate for the final time before final action is taken. The same rule applies when a rate-lock agreement is extended and the rate is reset at the same rate, regardless of whether market rates have increased, decreased, or remained the same since the initial rate was set. If no lock-in agreement is executed, then the relevant date is the date on which the institution sets the rate for the final time before final action is taken.
                        </P>
                        <P>
                            ii. 
                            <E T="03">Change in loan program.</E>
                             If a financial institution issues a rate-lock commitment under one loan program, the borrower subsequently changes to another program that is subject to different pricing terms, and the financial institution changes the rate promised to the borrower under the rate-lock commitment accordingly, the rate-set date is the date of the program change. However, if the financial institution changes the promised rate to the rate that would have been available to the borrower under the new program on the date of the original rate-lock commitment, then that is the date the rate is set, provided the financial institution consistently follows that practice in all such cases or the original rate-lock agreement so provided. For example, assume that a borrower locks a rate of 2.5 percent on June 1 for a 30-year, variable-rate loan with a five-year, fixed-rate introductory period. On June 15, the borrower decides to switch to a 30-year, fixed-rate loan, and the rate available to the borrower for that product on June 15 is 4.0 percent. On June 1, the 30-year, fixed-rate loan would have been available to the borrower at a rate of 3.5 percent. If the financial institution offers the borrower the 3.5 percent rate (
                            <E T="03">i.e.,</E>
                             the rate that would have been available to the borrower for the fixed-rate product on June 1, the date of the original rate-lock) because the original agreement so provided or because the financial institution consistently follows that practice for borrowers who change loan programs, then the financial institution should use June 1 as the rate-set date. In all other cases, the financial institution should use June 15 as the rate-set date.
                        </P>
                        <P>
                            iii. 
                            <E T="03">Brokered loans.</E>
                             When a financial institution has reporting responsibility for an application for a covered loan that it received from a broker, as discussed in comment 4(a)-2 (
                            <E T="03">e.g.,</E>
                             because the financial institution makes a credit decision prior to closing or account opening), the rate-set date is the last date the financial institution set the rate with the broker, not the date the broker set the borrower's rate.
                        </P>
                        <P>
                            6. 
                            <E T="03">Compare the annual percentage rate to the average prime offer rate.</E>
                             Section 1003.4(a)(12)(i) requires a financial institution to compare the covered loan's annual percentage rate to the most recently available average prime offer rate that was in effect for the comparable transaction as of the rate-set date. For purposes of § 1003.4(a)(12)(i), the most recently available 
                            <PRTPAGE P="21030"/>
                            rate means the average prime offer rate set forth in the applicable table with the most recent effective date as of the date the interest rate was set. However, § 1003.4(a)(12)(i) does not permit a financial institution to use an average prime offer rate before its effective date.
                        </P>
                        <P>
                            7. 
                            <E T="03">Rate spread—scope of requirement.</E>
                             If the covered loan is an assumption, reverse mortgage, a purchased loan, or is not subject to Regulation Z, 12 CFR part 1026, a financial institution complies with § 1003.4(a)(12) by reporting that the requirement is not applicable. If the application did not result in an origination for a reason other than the application was approved but not accepted by the applicant, a financial institution complies with § 1003.4(a)(12) by reporting that the requirement is not applicable. For partially exempt transactions under § 1003.3(d), an insured depository institution or insured credit union is not required to report the rate spread. See § 1003.3(d) and related commentary.
                        </P>
                        <P>
                            8. 
                            <E T="03">Application or preapproval request approved but not accepted.</E>
                             In the case of an application or preapproval request that was approved but not accepted, § 1003.4(a)(12) requires a financial institution to report the applicable rate spread. In such cases, the financial institution would provide early disclosures under Regulation Z, 12 CFR 1026.18 or 1026.37 (for closed-end mortgage loans), or 1026.40 (for open-end lines of credit), but might never provide any subsequent disclosures. In such cases where no subsequent disclosures are provided, a financial institution complies with § 1003.4(a)(12)(i) by relying on the annual percentage rate for the application or preapproval request, as calculated and disclosed pursuant to Regulation Z, 12 CFR 1026.18 or 1026.37 (for closed-end mortgage loans), or 1026.40 (for open-end lines of credit), as applicable. For transactions subject to Regulation C for which no disclosures under Regulation Z are required, a financial institution complies with § 1003.4(a)(12)(i) by reporting that the requirement is not applicable.
                        </P>
                        <P>
                            9. 
                            <E T="03">Corrected disclosures.</E>
                             In the case of a covered loan or an application that was approved but not accepted, if the annual percentage rate changes because a financial institution provides a corrected version of the disclosures required under Regulation Z, 12 CFR 1026.19(a), pursuant to 12 CFR 1026.19(a)(2), under 12 CFR 1026.19(f), pursuant to 12 CFR 1026.19(f)(2), or under 12 CFR 1026.6(a), the financial institution complies with § 1003.4(a)(12)(i) by comparing the corrected and disclosed annual percentage rate to the most recently available average prime offer rate that was in effect for a comparable transaction as of the rate-set date, provided that the corrected disclosure was provided to the borrower prior to the end of the reporting period in which final action is taken. For purposes of § 1003.4(a)(12), the date the corrected disclosure was provided to the borrower is the date the disclosure was mailed or delivered to the borrower in person; the financial institution's method of delivery does not affect the date provided. For example, where a financial institution provides a corrected version of the disclosures required under 12 CFR 1026.19(f), pursuant to 12 CFR 1026.19(f)(2), the date provided is the date disclosed pursuant to Regulation Z, 12 CFR 1026.38(a)(3)(i). The provision of a corrected disclosure does not affect how a financial institution determines the rate-set date. 
                            <E T="03">See</E>
                             comment 4(a)(12)-5. For example:
                        </P>
                        <P>i. In the case of a financial institution's annual loan/application register submission made pursuant to § 1003.5(a)(1)(i), if the financial institution provides a corrected disclosure pursuant to Regulation Z, 12 CFR 1026.19(f)(2)(v), that reflects a corrected annual percentage rate, the financial institution reports the difference between the corrected annual percentage rate and the most recently available average prime offer rate that was in effect for a comparable transaction as of the rate-set date only if the corrected disclosure was provided to the borrower prior to the end of the calendar year in which final action is taken.</P>
                        <P>ii. In the case of a financial institution's quarterly submission made pursuant to § 1003.5(a)(1)(ii), if the financial institution provides a corrected disclosure pursuant to Regulation Z, 12 CFR 1026.19(f)(2)(v), that reflects a corrected annual percentage rate, the financial institution reports the difference between the corrected annual percentage rate and the most recently available average prime offer rate that was in effect for a comparable transaction as of the rate-set date only if the corrected disclosure was provided to the borrower prior to the end of the quarter in which final action is taken. The financial institution does not report the difference between the corrected annual percentage rate and the most recently available average prime offer rate that was in effect for a comparable transaction as of the rate-set date if the corrected disclosure was provided to the borrower after the end of the quarter in which final action is taken, even if the corrected disclosure was provided to the borrower prior to the deadline for timely submission of the financial institution's quarterly data. However, the financial institution reports the difference between the corrected annual percentage rate and the most recently available average prime offer rate that was in effect for a comparable transaction as of the rate-set date on its annual loan/application register, provided that the corrected disclosure was provided to the borrower prior to the end of the calendar year in which final action is taken.</P>
                        <HD SOURCE="HD3">Paragraph 4(a)(13)</HD>
                        <P>
                            1. 
                            <E T="03">HOEPA status—not applicable.</E>
                             If the covered loan is not subject to the Home Ownership and Equity Protection Act of 1994, as implemented in Regulation Z, 12 CFR 1026.32, a financial institution complies with § 1003.4(a)(13) by reporting that the requirement is not applicable. If an application did not result in an origination, a financial institution complies with § 1003.4(a)(13) by reporting that the requirement is not applicable.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(14)</HD>
                        <P>
                            1. 
                            <E T="03">Determining lien status for applications and covered loans originated and purchased.</E>
                             i. Financial institutions are required to report lien status for covered loans they originate and purchase and applications that do not result in originations (preapproval requests that are approved but not accepted, preapproval requests that are denied, applications that are approved but not accepted, denied, withdrawn, or closed for incompleteness). For covered loans purchased by a financial institution, lien status is determined by reference to the best information readily available to the financial institution at the time of purchase. For covered loans that a financial institution originates and applications that do not result in originations, lien status is determined by reference to the best information readily available to the financial institution at the time final action is taken and to the financial institution's own procedures. Thus, financial institutions may rely on the title search they routinely perform as part of their underwriting procedures—for example, for home purchase loans. Regulation C does not require financial institutions to perform title searches solely to comply with HMDA reporting requirements. Financial institutions may rely on other information that is readily available to them at the time final action is taken and that they reasonably believe is accurate, such as the applicant's statement on the application or the applicant's credit report. For example, where the applicant indicates on the application that there is a mortgage on the property or where the applicant's credit report shows that the applicant has a mortgage—and that mortgage will not be paid off as part of the transaction—the financial institution may assume that the loan it originates is secured by a subordinate lien. If the same application did not result in an origination—for example, because the application was denied or withdrawn—the financial institution would report the application as an application for a subordinate-lien loan.
                        </P>
                        <P>ii. Financial institutions may also consider their established procedures when determining lien status for applications that do not result in originations. For example, assume an applicant applies to a financial institution to refinance a $100,000 first mortgage; the applicant also has an open-end line of credit for $20,000. If the financial institution's practice in such a case is to ensure that it will have first-lien position—through a subordination agreement with the holder of the lien securing the open-end line of credit—then the financial institution should report the application as an application for a first-lien covered loan.</P>
                        <P>
                            2. 
                            <E T="03">Multiple properties.</E>
                             See comment 4(a)(9)-2 regarding transactions involving multiple properties with more than one property taken as security.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(15)</HD>
                        <P>
                            1. 
                            <E T="03">Credit score—relied on.</E>
                             Except for purchased covered loans and partially exempt transactions under § 1003.3(d), § 1003.4(a)(15) requires a financial institution to report the credit score or scores relied on in making the credit decision and information about the scoring model used to generate each score. A financial institution relies on a credit score in making the credit decision if the credit score was a factor in the credit decision even if it was not a 
                            <PRTPAGE P="21031"/>
                            dispositive factor. For example, if a credit score is one of multiple factors in a financial institution's credit decision, the financial institution has relied on the credit score even if the financial institution denies the application because one or more underwriting requirements other than the credit score are not satisfied.
                        </P>
                        <P>
                            2. 
                            <E T="03">Credit score—multiple credit scores.</E>
                             When a financial institution obtains or creates two or more credit scores for a single applicant or borrower but relies on only one score in making the credit decision (for example, by relying on the lowest, highest, most recent, or average of all of the scores), the financial institution complies with § 1003.4(a)(15) by reporting that credit score and information about the scoring model used. When a financial institution uses more than one credit scoring model and combines the scores into a composite credit score that it relies on, the financial institution reports that score and reports that more than one credit scoring model was used. When a financial institution obtains or creates two or more credit scores for an applicant or borrower and relies on multiple scores for the applicant or borrower in making the credit decision (for example, by relying on a scoring grid that considers each of the scores obtained or created for the applicant or borrower without combining the scores into a composite score), § 1003.4(a)(15) requires the financial institution to report one of the credit scores for the applicant or borrower that was relied on in making the credit decision. In choosing which credit score to report in this circumstance, a financial institution need not use the same approach for its entire HMDA submission, but it should be generally consistent (such as by routinely using one approach within a particular division of the institution or for a category of covered loans). In instances such as these, the financial institution should report the name and version of the credit scoring model for the score reported.
                        </P>
                        <P>
                            3. 
                            <E T="03">Credit score—multiple applicants or borrowers.</E>
                             In a transaction involving two or more applicants or borrowers for whom the financial institution obtains or creates a single credit score and relies on that credit score in making the credit decision for the transaction, the institution complies with § 1003.4(a)(15) by reporting that credit score for the applicant and reporting that the requirement is not applicable for the first co-applicant or, at the financial institution's discretion, by reporting that credit score for the first co-applicant and reporting that the requirement is not applicable for the applicant. Otherwise, a financial institution complies with § 1003.4(a)(15) by reporting a credit score for the applicant that it relied on in making the credit decision, if any, and a credit score for the first co-applicant that it relied on in making the credit decision, if any. To illustrate, assume a transaction involves one applicant and one co-applicant and that the financial institution obtains or creates two credit scores for the applicant and two credit scores for the co-applicant. Assume further that the financial institution relies on a single credit score that is the lowest, highest, most recent, or average of all of the credit scores obtained or created to make the credit decision for the transaction. The financial institution complies with § 1003.4(a)(15) by reporting that credit score and information about the scoring model used for the applicant and reporting that the requirement is not applicable for the first co-applicant or, at the financial institution's discretion, by reporting the data for the first co-applicant and reporting that the requirement is not applicable for the applicant. Alternatively, assume a transaction involves one applicant and one co-applicant and that the financial institution obtains or creates three credit scores for the applicant and three credit scores for the co-applicant. Assume further that the financial institution relies on the middle credit score for the applicant and the middle credit score for the co-applicant to make the credit decision for the transaction. The financial institution complies with § 1003.4(a)(15) by reporting both the middle score for the applicant and the middle score for the co-applicant.
                        </P>
                        <P>
                            4. 
                            <E T="03">Transactions for which no credit decision was made.</E>
                             If a file was closed for incompleteness or the application was withdrawn before a credit decision was made, the financial institution complies with § 1003.4(a)(15) by reporting that the requirement is not applicable, even if the financial institution had obtained or created a credit score for the applicant or co-applicant. For example, if a file is closed for incompleteness and is so reported in accordance with § 1003.4(a)(8), the financial institution complies with § 1003.4(a)(15) by reporting that the requirement is not applicable, even if the financial institution had obtained or created a credit score for the applicant or co-applicant. Similarly, if an application was withdrawn by the applicant before a credit decision was made and is so reported in accordance with § 1003.4(a)(8), the financial institution complies with § 1003.4(a)(15) by reporting that the requirement is not applicable, even if the financial institution had obtained or created a credit score for the applicant or co-applicant.
                        </P>
                        <P>
                            5. 
                            <E T="03">Transactions for which no credit score was relied on.</E>
                             If a financial institution makes a credit decision without relying on a credit score for the applicant or borrower, the financial institution complies with § 1003.4(a)(15) by reporting that the requirement is not applicable.
                        </P>
                        <P>
                            6. 
                            <E T="03">Purchased covered loan.</E>
                             A financial institution complies with § 1003.4(a)(15) by reporting that the requirement is not applicable when the covered loan is a purchased covered loan.
                        </P>
                        <P>
                            7. 
                            <E T="03">Non-natural person.</E>
                             When the applicant and co-applicant, if applicable, are not natural persons, a financial institution complies with § 1003.4(a)(15) by reporting that the requirement is not applicable.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(16)</HD>
                        <P>
                            1. 
                            <E T="03">Reason for denial—general.</E>
                             A financial institution complies with § 1003.4(a)(16) by reporting the principal reason or reasons it denied the application, indicating up to four reasons. The financial institution should report only the principal reason or reasons it denied the application, even if there are fewer than four reasons. For example, if a financial institution denies the application because of the applicant's credit history and debt-to-income ratio, the financial institution need only report these two principal reasons. The reasons reported must be specific and accurately describe the principal reason or reasons the financial institution denied the application.
                        </P>
                        <P>
                            2. 
                            <E T="03">Reason for denial—preapproval request denied.</E>
                             Section 1003.4(a)(16) requires a financial institution to report the principal reason or reasons it denied the application. A request for a preapproval under a preapproval program as defined by § 1003.2(b)(2) is an application. If a financial institution denies a preapproval request, the financial institution complies with § 1003.4(a)(16) by reporting the reason or reasons it denied the preapproval request.
                        </P>
                        <P>
                            3. 
                            <E T="03">Reason for denial—adverse action model form or similar form.</E>
                             If a financial institution chooses to provide the applicant the reason or reasons it denied the application using the model form contained in appendix C to Regulation B (Form C-1, Sample Notice of Action Taken and Statement of Reasons) or a similar form, § 1003.4(a)(16) requires the financial institution to report the reason or reasons that were specified on the form by the financial institution, which includes reporting the “Other” reason or reasons that were specified on the form by the financial institution, if applicable. If a financial institution chooses to provide a disclosure of the applicant's right to a statement of specific reasons using the model form contained in appendix C to Regulation B (Form C-5, Sample Disclosure of Right to Request Specific Reasons for Credit Denial) or a similar form, or chooses to provide the denial reason or reasons orally under Regulation B, 12 CFR 1002.9(a)(2)(ii), the financial institution complies with § 1003.4(a)(16) by entering the principal reason or reasons it denied the application.
                        </P>
                        <P>
                            4. 
                            <E T="03">Reason for denial—scope of requirement.</E>
                             A financial institution complies with § 1003.4(a)(16) by reporting that the requirement is not applicable if the action taken on the application, pursuant to § 1003.4(a)(8), is not a denial. For example, a financial institution complies with § 1003.4(a)(16) by reporting that the requirement is not applicable if the loan is originated or purchased by the financial institution, or the application or preapproval request was approved but not accepted, or the application was withdrawn before a credit decision was made, or the file was closed for incompleteness. For partially exempt transactions under § 1003.3(d), an insured depository institution or insured credit union is not required to report the principal reason or reasons it denied an application. See § 1003.3(d) and related commentary.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(17)(i)</HD>
                        <P>
                            1. 
                            <E T="03">Total loan costs—scope of requirement.</E>
                             Section 1003.4(a)(17)(i) does not require financial institutions to report the total loan costs for applications, or for transactions not subject to Regulation Z, 12 CFR 1026.43(c), and 12 CFR 1026.19(f), such as open-end lines of credit, reverse mortgages, or loans or lines of credit made primarily for business or commercial purposes. In these cases, a 
                            <PRTPAGE P="21032"/>
                            financial institution complies with § 1003.4(a)(17)(i) by reporting that the requirement is not applicable to the transaction. For partially exempt transactions under § 1003.3(d), an insured depository institution or insured credit union is not required to report the total loan costs. See § 1003.3(d) and related commentary.
                        </P>
                        <P>
                            2. 
                            <E T="03">Purchased loans—applications received prior to the integrated disclosure effective date.</E>
                             For purchased covered loans subject to this reporting requirement for which applications were received by the selling entity prior to the effective date of Regulation Z, 12 CFR 1026.19(f), a financial institution complies with § 1003.4(a)(17)(i) by reporting that the requirement is not applicable to the transaction.
                        </P>
                        <P>
                            3. 
                            <E T="03">Corrected disclosures.</E>
                             If the amount of total loan costs changes because a financial institution provides a corrected version of the disclosures required under Regulation Z, 12 CFR 1026.19(f), pursuant to 12 CFR 1026.19(f)(2), the financial institution complies with § 1003.4(a)(17)(i) by reporting the corrected amount, provided that the corrected disclosure was provided to the borrower prior to the end of the reporting period in which closing occurs. For purposes of § 1003.4(a)(17)(i), the date the corrected disclosure was provided to the borrower is the date disclosed pursuant to Regulation Z, 12 CFR 1026.38(a)(3)(i). For example:
                        </P>
                        <P>i. In the case of a financial institution's annual loan/application register submission made pursuant to § 1003.5(a)(1)(i), if the financial institution provides a corrected disclosure to the borrower to reflect a refund made pursuant to Regulation Z, 12 CFR 1026.19(f)(2)(v), the financial institution reports the corrected amount of total loan costs only if the corrected disclosure was provided to the borrower prior to the end of the calendar year in which closing occurs.</P>
                        <P>ii. In the case of a financial institution's quarterly submission made pursuant to § 1003.5(a)(1)(ii), if the financial institution provides a corrected disclosure to the borrower to reflect a refund made pursuant to Regulation Z, 12 CFR 1026.19(f)(2)(v), the financial institution reports the corrected amount of total loan costs only if the corrected disclosure was provided to the borrower prior to the end of the quarter in which closing occurs. The financial institution does not report the corrected amount of total loan costs in its quarterly submission if the corrected disclosure was provided to the borrower after the end of the quarter in which closing occurs, even if the corrected disclosure was provided to the borrower prior to the deadline for timely submission of the financial institution's quarterly data. However, the financial institution reports the corrected amount of total loan costs on its annual loan/application register, provided that the corrected disclosure was provided to the borrower prior to the end of the calendar year in which closing occurs.</P>
                        <HD SOURCE="HD3">Paragraph 4(a)(17)(ii)</HD>
                        <P>
                            1. 
                            <E T="03">Total points and fees—scope of requirement.</E>
                             Section 1003.4(a)(17)(ii) does not require financial institutions to report the total points and fees for transactions not subject to Regulation Z, 12 CFR 1026.43(c), such as open-end lines of credit, reverse mortgages, or loans or lines of credit made primarily for business or commercial purposes, or for applications or purchased covered loans. In these cases, a financial institution complies with § 1003.4(a)(17)(ii) by reporting that the requirement is not applicable to the transaction. For partially exempt transactions under § 1003.3(d), an insured depository institution or insured credit union is not required to report the total points and fees. See § 1003.3(d) and related commentary.
                        </P>
                        <P>
                            2. 
                            <E T="03">Total points and fees cure mechanism.</E>
                             For covered loans subject to this reporting requirement, if a financial institution determines that the transaction's total points and fees exceeded the applicable limit and cures the overage pursuant to Regulation Z, 12 CFR 1026.43(e)(3)(iii) and (iv), a financial institution complies with § 1003.4(a)(17)(ii) by reporting the correct amount of total points and fees, provided that the cure was effected during the same reporting period in which closing occurred. For example, in the case of a financial institution's quarterly submission, the financial institution reports the revised amount of total points and fees only if it cured the overage prior to the end of the quarter in which closing occurred. The financial institution does not report the revised amount of total points and fees in its quarterly submission if it cured the overage after the end of the quarter, even if the cure was effected prior to the deadline for timely submission of the financial institution's quarterly data. However, the financial institution reports the revised amount of total points and fees on its annual loan/application register.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(18)</HD>
                        <P>
                            1. 
                            <E T="03">Origination charges—scope of requirement.</E>
                             Section 1003.4(a)(18) does not require financial institutions to report the total borrower-paid origination charges for applications, or for transactions not subject to Regulation Z, 12 CFR 1026.19(f), such as open-end lines of credit, reverse mortgages, or loans or lines of credit made primarily for business or commercial purposes. In these cases, a financial institution complies with § 1003.4(a)(18) by reporting that the requirement is not applicable to the transaction. For partially exempt transactions under § 1003.3(d), an insured depository institution or insured credit union is not required to report the total borrower-paid origination charges. See § 1003.3(d) and related commentary.
                        </P>
                        <P>
                            2. 
                            <E T="03">Purchased loans—applications received prior to the integrated disclosure effective date.</E>
                             For purchased covered loans subject to this reporting requirement for which applications were received by the selling entity prior to the effective date of Regulation Z, 12 CFR 1026.19(f), a financial institution complies with § 1003.4(a)(18) by reporting that the requirement is not applicable to the transaction.
                        </P>
                        <P>
                            3. 
                            <E T="03">Corrected disclosures.</E>
                             If the total amount of borrower-paid origination charges changes because a financial institution provides a corrected version of the disclosures required under Regulation Z, 12 CFR 1026.19(f), pursuant to 12 CFR 1026.19(f)(2), the financial institution complies with § 1003.4(a)(18) by reporting the corrected amount, provided that the corrected disclosure was provided to the borrower prior to the end of the reporting period in which closing occurs. For purposes of § 1003.4(a)(18), the date the corrected disclosure was provided to the borrower is the date disclosed pursuant to Regulation Z, 12 CFR 1026.38(a)(3)(i). For example:
                        </P>
                        <P>i. In the case of a financial institution's annual loan/application register submission made pursuant to § 1003.5(a)(1)(i), if the financial institution provides a corrected disclosure to the borrower to reflect a refund made pursuant to Regulation Z, 12 CFR 1026.19(f)(2)(v), the financial institution reports the corrected amount of borrower-paid origination charges only if the corrected disclosure was provided to the borrower prior to the end of the calendar year in which closing occurs.</P>
                        <P>ii. In the case of a financial institution's quarterly submission made pursuant to § 1003.5(a)(1)(ii), if the financial institution provides a corrected disclosure to the borrower to reflect a refund made pursuant to Regulation Z, 12 CFR 1026.19(f)(2)(v), the financial institution reports the corrected amount of borrower-paid origination charges only if the corrected disclosure was provided to the borrower prior to the end of the quarter in which closing occurs. The financial institution does not report the corrected amount of borrower-paid origination charges in its quarterly submission if the corrected disclosure was provided to the borrower after the end of the quarter in which closing occurs, even if the corrected disclosure was provided to the borrower prior to the deadline for timely submission of the financial institution's quarterly data. However, the financial institution reports the corrected amount of borrower-paid origination charges on its annual loan/application register, provided that the corrected disclosure was provided to the borrower prior to the end of the calendar year in which closing occurs.</P>
                        <HD SOURCE="HD3">Paragraph 4(a)(19)</HD>
                        <P>
                            1. 
                            <E T="03">Discount points—scope of requirement.</E>
                             Section 1003.4(a)(19) does not require financial institutions to report the discount points for applications, or for transactions not subject to Regulation Z, 12 CFR 1026.19(f), such as open-end lines of credit, reverse mortgages, or loans or lines of credit made primarily for business or commercial purposes. In these cases, a financial institution complies with § 1003.4(a)(19) by reporting that the requirement is not applicable to the transaction. For partially exempt transactions under § 1003.3(d), an insured depository institution or insured credit union is not required to report the discount points. See § 1003.3(d) and related commentary.
                        </P>
                        <P>
                            2. 
                            <E T="03">Purchased loans—applications received prior to the integrated disclosure effective date.</E>
                             For purchased covered loans subject to this reporting requirement for which applications were received by the selling entity prior to the effective date of Regulation Z, 12 CFR 1026.19(f), a financial institution complies with § 1003.4(a)(19) by reporting that the requirement is not applicable to the transaction.
                            <PRTPAGE P="21033"/>
                        </P>
                        <P>
                            3. 
                            <E T="03">Corrected disclosures.</E>
                             If the amount of discount points changes because a financial institution provides a corrected version of the disclosures required under Regulation Z, 12 CFR 1026.19(f), pursuant to 12 CFR 1026.19(f)(2), the financial institution complies with § 1003.4(a)(19) by reporting the corrected amount, provided that the corrected disclosure was provided to the borrower prior to the end of the reporting period in which closing occurs. For purposes of § 1003.4(a)(19), the date the corrected disclosure was provided to the borrower is the date disclosed pursuant to Regulation Z, 12 CFR 1026.38(a)(3)(i). For example:
                        </P>
                        <P>i. In the case of a financial institution's annual loan/application register submission made pursuant to § 1003.5(a)(1)(i), if the financial institution provides a corrected disclosure to the borrower to reflect a refund made pursuant to Regulation Z, 12 CFR 1026.19(f)(2)(v), the financial institution reports the corrected amount of discount points only if the corrected disclosure was provided to the borrower prior to the end of the calendar year in which closing occurred.</P>
                        <P>ii. In the case of a financial institution's quarterly submission made pursuant to § 1003.5(a)(1)(ii), if the financial institution provides a corrected disclosure to the borrower to reflect a refund made pursuant to Regulation Z, 12 CFR 1026.19(f)(2)(v), the financial institution reports the corrected amount of discount points only if the corrected disclosure was provided to the borrower prior to the end of the quarter in which closing occurred. The financial institution does not report the corrected amount of discount points in its quarterly submission if the corrected disclosure was provided to the borrower after the end of the quarter in which closing occurred, even if the corrected disclosure was provided to the borrower prior to the deadline for timely submission of the financial institution's quarterly data. However, the financial institution reports the corrected amount of discount points on its annual loan/application register, provided that the corrected disclosure was provided to the borrower prior to the end of the calendar year in which closing occurred.</P>
                        <HD SOURCE="HD3">Paragraph 4(a)(20)</HD>
                        <P>
                            1. 
                            <E T="03">Lender credits—scope of requirement.</E>
                             Section 1003.4(a)(20) does not require financial institutions to report lender credits for applications, or for transactions not subject to Regulation Z, 12 CFR 1026.19(f), such as open-end lines of credit, reverse mortgages, or loans or lines of credit made primarily for business or commercial purposes. In these cases, a financial institution complies with § 1003.4(a)(20) by reporting that the requirement is not applicable to the transaction. For partially exempt transactions under § 1003.3(d), an insured depository institution or insured credit union is not required to report lender credits. See § 1003.3(d) and related commentary.
                        </P>
                        <P>
                            2. 
                            <E T="03">Purchased loans—applications received prior to the integrated disclosure effective date.</E>
                             For purchased covered loans subject to this reporting requirement for which applications were received by the selling entity prior to the effective date of Regulation Z, 12 CFR 1026.19(f), a financial institution complies with § 1003.4(a)(20) by reporting that the requirement is not applicable to the transaction.
                        </P>
                        <P>
                            3. 
                            <E T="03">Corrected disclosures.</E>
                             If the amount of lender credits changes because a financial institution provides a corrected version of the disclosures required under Regulation Z, 12 CFR 1026.19(f), pursuant to 12 CFR 1026.19(f)(2), the financial institution complies with § 1003.4(a)(20) by reporting the corrected amount, provided that the corrected disclosure was provided to the borrower prior to the end of the reporting period in which closing occurred. For purposes of § 1003.4(a)(20), the date the corrected disclosure was provided to the borrower is the date disclosed pursuant to Regulation Z, 12 CFR 1026.38(a)(3)(i). For example:
                        </P>
                        <P>i. In the case of a financial institution's annual loan/application register submission made pursuant to § 1003.5(a)(1)(i), if the financial institution provides a corrected disclosure to the borrower to reflect a refund made pursuant to Regulation Z, 12 CFR 1026.19(f)(2)(v), the financial institution reports the corrected amount of lender credits only if the corrected disclosure was provided to the borrower prior to the end of the calendar year in which closing occurred.</P>
                        <P>ii. In the case of a financial institution's quarterly submission made pursuant to § 1003.5(a)(1)(ii), if the financial institution provides a corrected disclosure to the borrower to reflect a refund made pursuant to Regulation Z, 12 CFR 1026.19(f)(2)(v), the financial institution reports the corrected amount of lender credits only if the corrected disclosure was provided to the borrower prior to the end of the quarter in which closing occurred. The financial institution does not report the corrected amount of lender credits in its quarterly submission if the corrected disclosure was provided to the borrower after the end of the quarter in which closing occurred, even if the corrected disclosure was provided to the borrower prior to the deadline for timely submission of the financial institution's quarterly data. However, the financial institution reports the corrected amount of lender credits on its annual loan/application register, provided that the corrected disclosure was provided to the borrower prior to the end of the calendar year in which closing occurred.</P>
                        <HD SOURCE="HD3">Paragraph 4(a)(21)</HD>
                        <P>
                            1. 
                            <E T="03">Interest rate—disclosures.</E>
                             Except for partially exempt transactions under § 1003.3(d), § 1003.4(a)(21) requires a financial institution to identify the interest rate applicable to the approved application, or to the covered loan at closing or account opening. For covered loans or applications subject to the integrated mortgage disclosure requirements of Regulation Z, 12 CFR 1026.19(e) and (f), a financial institution complies with § 1003.4(a)(21) by reporting the interest rate disclosed on the applicable disclosure. For covered loans or approved applications for which disclosures were provided pursuant to both the early and the final disclosure requirements in Regulation Z, 12 CFR 1026.19(e) and (f), a financial institution reports the interest rate disclosed pursuant to 12 CFR 1026.19(f). A financial institution may rely on the definitions and commentary to the sections of Regulation Z relevant to the disclosure of the interest rate pursuant to 12 CFR 1026.19(e) or (f). If a financial institution provides a revised or corrected version of the disclosures required under Regulation Z, 12 CFR 1026.19(e) or (f), pursuant to 12 CFR 1026.19(e)(3)(iv) or (f)(2), as applicable, the financial institution complies with § 1003.4(a)(21) by reporting the interest rate on the revised or corrected disclosure, provided that the revised or corrected disclosure was provided to the borrower prior to the end of the reporting period in which final action is taken. For purposes of § 1003.4(a)(21), the date the revised or corrected disclosure was provided to the borrower is the date disclosed pursuant to Regulation Z, 12 CFR 1026.37(a)(4) or 1026.38(a)(3)(i), as applicable.
                        </P>
                        <P>
                            2. 
                            <E T="03">Applications.</E>
                             In the case of an application, § 1003.4(a)(21) requires a financial institution to report the applicable interest rate only if the application has been approved by the financial institution but not accepted by the borrower. In such cases, a financial institution reports the interest rate applicable at the time that the application was approved by the financial institution. A financial institution may report the interest rate appearing on the disclosure provided pursuant to 12 CFR 1026.19(e) or (f) if such disclosure accurately reflects the interest rate at the time the application was approved. For applications that have been denied or withdrawn, or files closed for incompleteness, a financial institution reports that no interest rate was applicable to the application.
                        </P>
                        <P>
                            3. 
                            <E T="03">Adjustable rate—interest rate unknown.</E>
                             Except as provided in comment 4(a)(21)-1, for adjustable-rate covered loans or applications, if the interest rate is unknown at the time that the application was approved, or at closing or account opening, a financial institution reports the fully-indexed rate based on the index applicable to the covered loan or application. For purposes of § 1003.4(a)(21), the fully-indexed rate is the index value and margin at the time that the application was approved, or, for covered loans, at closing or account opening.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(22)</HD>
                        <P>
                            1. 
                            <E T="03">Prepayment penalty term—scope of requirement.</E>
                             Section 1003.4(a)(22) does not require financial institutions to report the term of any prepayment penalty for transactions not subject to Regulation Z, 12 CFR part 1026, such as loans or lines of credit made primarily for business or commercial purposes, or for reverse mortgages or purchased covered loans. In these cases, a financial institution complies with § 1003.4(a)(22) by reporting that the requirement is not applicable to the transaction. For partially exempt transactions under § 1003.3(d), an insured depository institution or insured credit union is not required to report the term of any prepayment penalty. See § 1003.3(d) and related commentary.
                        </P>
                        <P>
                            2. 
                            <E T="03">Transactions for which no prepayment penalty exists.</E>
                             For covered loans or applications that have no prepayment penalty, a financial institution complies with 
                            <PRTPAGE P="21034"/>
                            § 1003.4(a)(22) by reporting that the requirement is not applicable to the transaction. A financial institution may rely on the definitions and commentary to Regulation Z, 12 CFR 1026.32(b)(6)(i) or (ii) in determining whether the terms of a transaction contain a prepayment penalty.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(23)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             For covered loans that are not purchased covered loans and that are not partially exempt under § 1003.3(d), § 1003.4(a)(23) requires a financial institution to report the ratio of the applicant's or borrower's total monthly debt to total monthly income (debt-to-income ratio) relied on in making the credit decision. For example, if a financial institution calculated the applicant's or borrower's debt-to-income ratio twice—once according to the financial institution's own requirements and once according to the requirements of a secondary market investor—and the financial institution relied on the debt-to-income ratio calculated according to the secondary market investor's requirements in making the credit decision, § 1003.4(a)(23) requires the financial institution to report the debt-to-income ratio calculated according to the requirements of the secondary market investor.
                        </P>
                        <P>
                            2. 
                            <E T="03">Transactions for which a debt-to-income ratio was one of multiple factors.</E>
                             A financial institution relies on the ratio of the applicant's or borrower's total monthly debt to total monthly income (debt-to-income ratio) in making the credit decision if the debt-to-income ratio was a factor in the credit decision even if it was not a dispositive factor. For example, if the debt-to-income ratio was one of multiple factors in a financial institution's credit decision, the financial institution has relied on the debt-to-income ratio and complies with § 1003.4(a)(23) by reporting the debt-to-income ratio, even if the financial institution denied the application because one or more underwriting requirements other than the debt-to-income ratio were not satisfied.
                        </P>
                        <P>
                            3. 
                            <E T="03">Transactions for which no credit decision was made.</E>
                             If a file was closed for incompleteness, or if an application was withdrawn before a credit decision was made, a financial institution complies with § 1003.4(a)(23) by reporting that the requirement is not applicable, even if the financial institution had calculated the ratio of the applicant's total monthly debt to total monthly income (debt-to-income ratio). For example, if a file was closed for incompleteness and was so reported in accordance with § 1003.4(a)(8), the financial institution complies with § 1003.4(a)(23) by reporting that the requirement is not applicable, even if the financial institution had calculated the applicant's debt-to-income ratio. Similarly, if an application was withdrawn by the applicant before a credit decision was made, the financial institution complies with § 1003.4(a)(23) by reporting that the requirement is not applicable, even if the financial institution had calculated the applicant's debt-to-income ratio.
                        </P>
                        <P>
                            4. 
                            <E T="03">Transactions for which no debt-to-income ratio was relied on.</E>
                             Section 1003.4(a)(23) does not require a financial institution to calculate the ratio of an applicant's or borrower's total monthly debt to total monthly income (debt-to-income ratio), nor does it require a financial institution to rely on an applicant's or borrower's debt-to-income ratio in making a credit decision. If a financial institution made a credit decision without relying on the applicant's or borrower's debt-to-income ratio, the financial institution complies with § 1003.4(a)(23) by reporting that the requirement is not applicable since no debt-to-income ratio was relied on in connection with the credit decision.
                        </P>
                        <P>
                            5. 
                            <E T="03">Non-natural person.</E>
                             A financial institution complies with § 1003.4(a)(23) by reporting that the requirement is not applicable when the applicant and co-applicant, if applicable, are not natural persons.
                        </P>
                        <P>
                            6. 
                            <E T="03">Multifamily dwellings.</E>
                             A financial institution complies with § 1003.4(a)(23) by reporting that the requirement is not applicable for a covered loan secured by, or an application proposed to be secured by, a multifamily dwelling.
                        </P>
                        <P>
                            7. 
                            <E T="03">Purchased covered loans.</E>
                             A financial institution complies with § 1003.4(a)(23) by reporting that the requirement is not applicable when reporting a purchased covered loan.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(24)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Except for purchased covered loans and partially exempt transactions under § 1003.3(d), § 1003.4(a)(24) requires a financial institution to report the ratio of the total amount of debt secured by the property to the value of the property (combined loan-to-value ratio) relied on in making the credit decision. For example, if a financial institution calculated a combined loan-to-value ratio twice—once according to the financial institution's own requirements and once according to the requirements of a secondary market investor—and the financial institution relied on the combined loan-to-value ratio calculated according to the secondary market investor's requirements in making the credit decision, § 1003.4(a)(24) requires the financial institution to report the combined loan-to-value ratio calculated according to the requirements of the secondary market investor.
                        </P>
                        <P>
                            2. 
                            <E T="03">Transactions for which a combined loan-to-value ratio was one of multiple factors.</E>
                             A financial institution relies on the ratio of the total amount of debt secured by the property to the value of the property (combined loan-to-value ratio) in making the credit decision if the combined loan-to-value ratio was a factor in the credit decision, even if it was not a dispositive factor. For example, if the combined loan-to-value ratio is one of multiple factors in a financial institution's credit decision, the financial institution has relied on the combined loan-to-value ratio and complies with § 1003.4(a)(24) by reporting the combined loan-to-value ratio, even if the financial institution denies the application because one or more underwriting requirements other than the combined loan-to-value ratio are not satisfied.
                        </P>
                        <P>
                            3. 
                            <E T="03">Transactions for which no credit decision was made.</E>
                             If a file was closed for incompleteness, or if an application was withdrawn before a credit decision was made, a financial institution complies with § 1003.4(a)(24) by reporting that the requirement is not applicable, even if the financial institution had calculated the ratio of the total amount of debt secured by the property to the value of the property (combined loan-to-value ratio). For example, if a file is closed for incompleteness and is so reported in accordance with § 1003.4(a)(8), the financial institution complies with § 1003.4(a)(24) by reporting that the requirement is not applicable, even if the financial institution had calculated a combined loan-to-value ratio. Similarly, if an application was withdrawn by the applicant before a credit decision was made and is so reported in accordance with § 1003.4(a)(8), the financial institution complies with § 1003.4(a)(24) by reporting that the requirement is not applicable, even if the financial institution had calculated a combined loan-to-value ratio.
                        </P>
                        <P>
                            4. 
                            <E T="03">Transactions for which no combined loan-to-value ratio was relied on.</E>
                             Section 1003.4(a)(24) does not require a financial institution to calculate the ratio of the total amount of debt secured by the property to the value of the property (combined loan-to-value ratio), nor does it require a financial institution to rely on a combined loan-to-value ratio in making a credit decision. If a financial institution makes a credit decision without relying on a combined loan-to-value ratio, the financial institution complies with § 1003.4(a)(24) by reporting that the requirement is not applicable since no combined loan-to-value ratio was relied on in making the credit decision.
                        </P>
                        <P>
                            5. 
                            <E T="03">Purchased covered loan.</E>
                             A financial institution complies with § 1003.4(a)(24) by reporting that the requirement is not applicable when the covered loan is a purchased covered loan.
                        </P>
                        <P>
                            6. 
                            <E T="03">Property.</E>
                             A financial institution reports the combined loan-to-value ratio relied on in making the credit decision, regardless of which property or properties it used in the combined loan-to-value ratio calculation. The property used in the combined loan-to-value ratio calculation does not need to be the property identified in § 1003.4(a)(9) and may include more than one property and non-real property. For example, if a financial institution originated a covered loan for the purchase of a multifamily dwelling, the loan was secured by the multifamily dwelling and by non-real property, such as securities, and the financial institution used the multifamily dwelling and the non-real property to calculate the combined loan-to-value ratio that it relied on in making the credit decision, § 1003.4(a)(24) requires the financial institution to report the relied upon ratio. Section 1003.4(a)(24) does not require a financial institution to use a particular combined loan-to-value ratio calculation method but instead requires financial institutions to report the combined loan-to-value ratio relied on in making the credit decision.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(25)</HD>
                        <P>
                            1. 
                            <E T="03">Amortization and maturity.</E>
                             For a fully amortizing covered loan, the number of months after which the legal obligation matures is the number of months in the amortization schedule, ending with the final 
                            <PRTPAGE P="21035"/>
                            payment. Some covered loans do not fully amortize during the maturity term, such as covered loans with a balloon payment; such loans should still be reported using the maturity term rather than the amortization term, even in the case of covered loans that mature before fully amortizing but have reset options. For example, a 30-year fully amortizing covered loan would be reported with a term of “360,” while a five year balloon covered loan would be reported with a loan term of “60.”
                        </P>
                        <P>
                            2. 
                            <E T="03">Non-monthly repayment periods.</E>
                             If a covered loan or application includes a schedule with repayment periods measured in a unit of time other than months, the financial institution should report the covered loan or application term using an equivalent number of whole months without regard for any remainder.
                        </P>
                        <P>
                            3. 
                            <E T="03">Purchased loans.</E>
                             For a covered loan that was purchased, a financial institution reports the number of months after which the legal obligation matures as measured from the covered loan's origination.
                        </P>
                        <P>
                            4. 
                            <E T="03">Open-end line of credit.</E>
                             For an open-end line of credit with a definite term, a financial institution reports the number of months from origination until the account termination date, including both the draw and repayment period.
                        </P>
                        <P>
                            5. 
                            <E T="03">Loan term—scope of requirement.</E>
                             For a covered loan or application without a definite term, such as a reverse mortgage, a financial institution complies with § 1003.4(a)(25) by reporting that the requirement is not applicable. For partially exempt transactions under § 1003.3(d), an insured depository institution or insured credit union is not required to report the loan term. See § 1003.3(d) and related commentary.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(26)</HD>
                        <P>
                            1. 
                            <E T="03">Types of introductory rates.</E>
                             Except for partially exempt transactions under § 1003.3(d), § 1003.4(a)(26) requires a financial institution to report the number of months, or proposed number of months in the case of an application, from closing or account opening until the first date the interest rate may change. For example, assume an open-end line of credit contains an introductory or “teaser” interest rate for two months after the date of account opening, after which the interest rate may adjust. In this example, the financial institution complies with § 1003.4(a)(26) by reporting the number of months as “2.” Section 1003.4(a)(26) requires a financial institution to report the number of months based on when the first interest rate adjustment may occur, even if an interest rate adjustment is not required to occur at that time and even if the rates that will apply, or the periods for which they will apply, are not known at closing or account opening. For example, if a closed-end mortgage loan with a 30-year term has an adjustable-rate product with an introductory interest rate for the first 60 months, after which the interest rate is permitted, but not required to vary, according to the terms of an index rate, the financial institution complies with § 1003.4(a)(26) by reporting the number of months as “60.” Similarly, if a closed-end mortgage loan with a 30-year term is a step-rate product with an introductory interest rate for the first 24 months, after which the interest rate will increase to a different known interest rate for the next 36 months, the financial institution complies with § 1003.4(a)(26) by reporting the number of months as “24.”
                        </P>
                        <P>
                            2. 
                            <E T="03">Preferred rates.</E>
                             Section 1003.4(a)(26) does not require reporting of introductory interest rate periods based on preferred rates unless the terms of the legal obligation provide that the preferred rate will expire at a certain defined date. Preferred rates include terms of the legal obligation that provide that the initial underlying rate is fixed but that it may increase or decrease upon the occurrence of some future event, such as an employee leaving the employ of the financial institution, the borrower closing an existing deposit account with the financial institution, or the borrower revoking an election to make automated payments. In these cases, because it is not known at the time of closing or account opening whether the future event will occur, and if so, when it will occur, § 1003.4(a)(26) does not require reporting of an introductory interest rate period.
                        </P>
                        <P>
                            3. 
                            <E T="03">Loan or application with a fixed rate.</E>
                             A financial institution complies with § 1003.4(a)(26) by reporting that the requirement is not applicable for a covered loan with a fixed rate or an application for a covered loan with a fixed rate.
                        </P>
                        <P>
                            4. 
                            <E T="03">Purchased loan.</E>
                             A financial institution complies with § 1003.4(a)(26) by reporting that requirement is not applicable when the covered loan is a purchased covered loan with a fixed rate.
                        </P>
                        <P>
                            5. 
                            <E T="03">Non-monthly introductory periods.</E>
                             If a covered loan or application includes an introductory interest rate period measured in a unit of time other than months, the financial institution complies with § 1003.4(a)(26) by reporting the introductory interest rate period for the covered loan or application using an equivalent number of whole months without regard for any remainder. For example, assume an open-end line of credit contains an introductory interest rate for 50 days after the date of account opening, after which the interest rate may adjust. In this example, the financial institution complies with § 1003.4(a)(26) by reporting the number of months as “1.” The financial institution must report one month for any introductory interest rate period that totals less than one whole month.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(27)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Except for partially exempt transactions under § 1003.3(d), § 1003.4(a)(27) requires reporting of contractual features that would allow payments other than fully amortizing payments. Section 1003.4(a)(27) defines the contractual features by reference to Regulation Z, 12 CFR part 1026, but without regard to whether the covered loan is consumer credit, as defined in § 1026.2(a)(12), is extended by a creditor, as defined in § 1026.2(a)(17), or is extended to a consumer, as defined in § 1026.2(a)(11), and without regard to whether the property is a dwelling as defined in § 1026.2(a)(19). For example, assume that a financial institution originates a business-purpose transaction that is exempt from Regulation Z pursuant to 12 CFR 1026.3(a)(1), to finance the purchase of a multifamily dwelling, and that there is a balloon payment, as defined by Regulation Z, 12 CFR 1026.18(s)(5)(i), at the end of the loan term. The multifamily dwelling is a dwelling under § 1003.2(f), but not under Regulation Z, 12 CFR 1026.2(a)(19). In this example, the financial institution should report the business-purpose transaction as having a balloon payment under § 1003.4(a)(27)(i), assuming the other requirements of this part are met. Aside from these distinctions, financial institutions may rely on the definitions and related commentary provided in the appropriate sections of Regulation Z referenced in § 1003.4(a)(27) of this part in determining whether the contractual feature should be reported.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(28)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Except for partially exempt transactions under § 1003.3(d), § 1003.4(a)(28) requires a financial institution to report the property value relied on in making the credit decision. For example, if the institution relies on an appraisal or other valuation for the property in calculating the loan-to-value ratio, it reports that value; if the institution relies on the purchase price of the property in calculating the loan-to-value ratio, it reports that value.
                        </P>
                        <P>
                            2. 
                            <E T="03">Multiple property values.</E>
                             When a financial institution obtains two or more valuations of the property securing or proposed to secure the covered loan, the financial institution complies with § 1003.4(a)(28) by reporting the value relied on in making the credit decision. For example, when a financial institution obtains an appraisal, an automated valuation model report, and a broker price opinion with different values for the property, it reports the value relied on in making the credit decision. Section § 1003.4(a)(28) does not require a financial institution to use a particular property valuation method, but instead requires a financial institution to report the valuation relied on in making the credit decision.
                        </P>
                        <P>
                            3. 
                            <E T="03">Transactions for which no credit decision was made.</E>
                             If a file was closed for incompleteness or the application was withdrawn before a credit decision was made, the financial institution complies with § 1003.4(a)(28) by reporting that the requirement is not applicable, even if the financial institution had obtained a property value. For example, if a file is closed for incompleteness and is so reported in accordance with § 1003.4(a)(8), the financial institution complies with § 1003.4(a)(28) by reporting that the requirement is not applicable, even if the financial institution had obtained a property value. Similarly, if an application was withdrawn by the applicant before a credit decision was made and is so reported in accordance with § 1003.4(a)(8), the financial institution complies with § 1003.4(a)(28) by reporting that the requirement is not applicable, even if the financial institution had obtained a property value.
                        </P>
                        <P>
                            4. 
                            <E T="03">Transactions for which no property value was relied on.</E>
                             Section 1003.4(a)(28) does not require a financial institution to obtain a property valuation, nor does it 
                            <PRTPAGE P="21036"/>
                            require a financial institution to rely on a property value in making a credit decision. If a financial institution makes a credit decision without relying on a property value, the financial institution complies with § 1003.4(a)(28) by reporting that the requirement is not applicable since no property value was relied on in making the credit decision.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(29)</HD>
                        <P>
                            1. 
                            <E T="03">Classification under State law.</E>
                             A financial institution should report a covered loan that is or would have been secured only by a manufactured home but not the land on which it is sited as secured by a manufactured home and not land, even if the manufactured home is considered real property under applicable State law.
                        </P>
                        <P>
                            2. 
                            <E T="03">Manufactured home community.</E>
                             A manufactured home community that is a multifamily dwelling is not considered a manufactured home for purposes of § 1003.4(a)(29).
                        </P>
                        <P>
                            3. 
                            <E T="03">Multiple properties.</E>
                             See comment 4(a)(9)-2 regarding transactions involving multiple properties with more than one property taken as security.
                        </P>
                        <P>
                            4. 
                            <E T="03">Scope of requirement.</E>
                             A financial institution reports that the requirement is not applicable for a covered loan where the dwelling related to the property identified in § 1003.4(a)(9) is not a manufactured home. For partially exempt transactions under § 1003.3(d), an insured depository institution or insured credit union is not required to report the information specified in § 1003.4(a)(29). See § 1003.3(d) and related commentary.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(30)</HD>
                        <P>
                            1. 
                            <E T="03">Indirect land ownership.</E>
                             Indirect land ownership can occur when the applicant or borrower is or will be a member of a resident-owned community structured as a housing cooperative in which the occupants own an entity that holds the underlying land of the manufactured home community. In such communities, the applicant or borrower may still have a lease and pay rent for the lot on which his or her manufactured home is or will be located, but the property interest type for such an arrangement should be reported as indirect ownership if the applicant is or will be a member of the cooperative that owns the underlying land of the manufactured home community. If an applicant resides or will reside in such a community but is not a member, the property interest type should be reported as a paid leasehold.
                        </P>
                        <P>
                            2. 
                            <E T="03">Leasehold interest.</E>
                             A leasehold interest could be formalized in a lease with a defined term and specified rent payments, or could arise as a tenancy at will through permission of a land owner without any written, formal arrangement. For example, assume a borrower will locate the manufactured home in a manufactured home community, has a written lease for a lot in that park, and the lease specifies rent payments. In this example, a financial institution complies with § 1003.4(a)(30) by reporting a paid leasehold. However, if instead the borrower will locate the manufactured home on land owned by a family member without a written lease and with no agreement as to rent payments, a financial institution complies with § 1003.4(a)(30) by reporting an unpaid leasehold.
                        </P>
                        <P>
                            3. 
                            <E T="03">Multiple properties.</E>
                             See comment 4(a)(9)-2 regarding transactions involving multiple properties with more than one property taken as security.
                        </P>
                        <P>
                            4. 
                            <E T="03">Manufactured home community.</E>
                             A manufactured home community that is a multifamily dwelling is not considered a manufactured home for purposes of § 1003.4(a)(30).
                        </P>
                        <P>
                            5. 
                            <E T="03">Direct ownership.</E>
                             An applicant or borrower has a direct ownership interest in the land on which the dwelling is or is to be located when it has a more than possessory real property ownership interest in the land such as fee simple ownership.
                        </P>
                        <P>
                            6. 
                            <E T="03">Scope of requirement.</E>
                             A financial institution reports that the requirement is not applicable for a covered loan where the dwelling related to the property identified in § 1003.4(a)(9) is not a manufactured home. For partially exempt transactions under § 1003.3(d), an insured depository institution or insured credit union is not required to report the information specified in § 1003.4(a)(30). See § 1003.3(d) and related commentary.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(31)</HD>
                        <P>
                            1. 
                            <E T="03">Multiple properties.</E>
                             See comment 4(a)(9)-2 regarding transactions involving multiple properties with more than one property taken as security.
                        </P>
                        <P>
                            2. 
                            <E T="03">Manufactured home community.</E>
                             For an application or covered loan secured by a manufactured home community, the financial institution should include in the number of individual dwelling units the total number of manufactured home sites that secure the loan and are available for occupancy, regardless of whether the sites are currently occupied or have manufactured homes currently attached. A financial institution may include in the number of individual dwelling units other units such as recreational vehicle pads, manager apartments, rental apartments, site-built homes or other rentable space that are ancillary to the operation of the secured property if it considers such units under its underwriting guidelines or the guidelines of an investor, or if it tracks the number of such units for its own internal purposes. For a loan secured by a single manufactured home that is or will be located in a manufactured home community, the financial institution should report one individual dwelling unit.
                        </P>
                        <P>
                            3. 
                            <E T="03">Condominium and cooperative projects.</E>
                             For a covered loan secured by a condominium or cooperative property, the financial institution reports the total number of individual dwelling units securing the covered loan or proposed to secure the covered loan in the case of an application. For example:
                        </P>
                        <P>i. Assume that a loan is secured by the entirety of a cooperative property. The financial institution would report the number of individual dwelling units in the cooperative property.</P>
                        <P>ii. Assume that a covered loan is secured by 30 individual dwelling units in a condominium property that contains 100 individual dwelling units and that the loan is not exempt from Regulation C under § 1003.3(c)(3). The financial institution reports 30 individual dwelling units.</P>
                        <P>
                            4. 
                            <E T="03">Best information available.</E>
                             A financial institution may rely on the best information readily available to the financial institution at the time final action is taken and on the financial institution's own procedures in reporting the information required by § 1003.4(a)(31). Information readily available could include, for example, information provided by an applicant that the financial institution reasonably believes, information contained in a property valuation or inspection, or information obtained from public records.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(32)</HD>
                        <P>
                            1. 
                            <E T="03">Affordable housing income restrictions.</E>
                             For purposes of § 1003.4(a)(32), affordable housing income-restricted units are individual dwelling units that have restrictions based on the income level of occupants pursuant to restrictive covenants encumbering the property. Such income levels are frequently expressed as a percentage of area median income by household size as established by the U.S. Department of Housing and Urban Development or another agency responsible for implementing the applicable affordable housing program. Such restrictions are frequently part of compliance with programs that provide public funds, special tax treatment, or density bonuses to encourage development or preservation of affordable housing. Such restrictions are frequently evidenced by a use agreement, regulatory agreement, land use restriction agreement, housing assistance payments contract, or similar agreement. Rent control or rent stabilization laws, and the acceptance by the owner or manager of a multifamily dwelling of Housing Choice Vouchers (24 CFR part 982) or other similar forms of portable housing assistance that are tied to an occupant and not an individual dwelling unit, are not affordable housing income-restricted dwelling units for purposes of § 1003.4(a)(32).
                        </P>
                        <P>
                            2. 
                            <E T="03">Federal affordable housing sources.</E>
                             Examples of Federal programs and funding sources that may result in individual dwelling units that are reportable under § 1003.4(a)(32) include, but are not limited to:
                        </P>
                        <P>i. Affordable housing programs pursuant to Section 8 of the United States Housing Act of 1937 (42 U.S.C. 1437f);</P>
                        <P>ii. Public housing (42 U.S.C. 1437a(b)(6));</P>
                        <P>iii. The HOME Investment Partnerships program (24 CFR part 92);</P>
                        <P>iv. The Community Development Block Grant program (24 CFR part 570);</P>
                        <P>v. Multifamily tax subsidy project funding through tax-exempt bonds or tax credits (26 U.S.C. 42; 26 U.S.C. 142(d));</P>
                        <P>vi. Project-based vouchers (24 CFR part 983);</P>
                        <P>vii. Federal Home Loan Bank affordable housing program funding (12 CFR part 1291); and</P>
                        <P>viii. Rural Housing Service multifamily housing loans and grants (7 CFR part 3560).</P>
                        <P>
                            3. 
                            <E T="03">State and local government affordable housing sources.</E>
                             Examples of State and local sources that may result in individual dwelling units that are reportable under 
                            <PRTPAGE P="21037"/>
                            § 1003.4(a)(32) include, but are not limited to: State or local administration of Federal funds or programs; State or local funding programs for affordable housing or rental assistance, including programs operated by independent public authorities; inclusionary zoning laws; and tax abatement or tax increment financing contingent on affordable housing requirements.
                        </P>
                        <P>
                            4. 
                            <E T="03">Multiple properties.</E>
                             See comment 4(a)(9)-2 regarding transactions involving multiple properties with more than one property taken as security.
                        </P>
                        <P>
                            5. 
                            <E T="03">Best information available.</E>
                             A financial institution may rely on the best information readily available to the financial institution at the time final action is taken and on the financial institution's own procedures in reporting the information required by § 1003.4(a)(32). Information readily available could include, for example, information provided by an applicant that the financial institution reasonably believes, information contained in a property valuation or inspection, or information obtained from public records.
                        </P>
                        <P>
                            6. 
                            <E T="03">Scope of requirement.</E>
                             A financial institution reports that the requirement is not applicable if the property securing the covered loan or, in the case of an application, proposed to secure the covered loan is not a multifamily dwelling. For partially exempt transactions under § 1003.3(d), an insured depository institution or insured credit union is not required to report the information specified in § 1003.4(a)(32). See § 1003.3(d) and related commentary.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(33)</HD>
                        <P>
                            1. 
                            <E T="03">Agents.</E>
                             If a financial institution is reporting actions taken by its agent consistent with comment 4(a)-4, the agent is not considered the financial institution for the purposes of § 1003.4(a)(33). For example, assume that an applicant submitted an application to Financial Institution A, and Financial Institution A made the credit decision acting as Financial Institution B's agent under State law. A covered loan was originated and the obligation arising from a covered loan was initially payable to Financial Institution A. Financial Institution B purchased the loan. Financial Institution B reports the origination and not the purchase, and indicates that the application was not submitted directly to the financial institution and that the transaction was not initially payable to the financial institution.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(33)(i)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Except for partially exempt transactions under § 1003.3(d), § 1003.4(a)(33)(i) requires a financial institution to indicate whether the applicant or borrower submitted the application directly to the financial institution that is reporting the covered loan or application. The following scenarios demonstrate whether an application was submitted directly to the financial institution that is reporting the covered loan or application.
                        </P>
                        <P>i. The application was submitted directly to the financial institution if the mortgage loan originator identified pursuant to § 1003.4(a)(34) was an employee of the reporting financial institution when the originator performed the origination activities for the covered loan or application that is being reported.</P>
                        <P>
                            ii. The application was also submitted directly to the financial institution reporting the covered loan or application if the reporting financial institution directed the applicant to a third-party agent (
                            <E T="03">e.g.,</E>
                             a credit union service organization) that performed loan origination activities on behalf of the financial institution and did not assist the applicant with applying for covered loans with other institutions.
                        </P>
                        <P>iii. If an applicant contacted and completed an application with a broker or correspondent that forwarded the application to a financial institution for approval, an application was not submitted to the financial institution.</P>
                        <HD SOURCE="HD3">Paragraph 4(a)(33)(ii)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Except for partially exempt transactions under § 1003.3(d), § 1003.4(a)(33)(ii) requires financial institutions to report whether the obligation arising from a covered loan was or, in the case of an application, would have been initially payable to the institution. An obligation is initially payable to the institution if the obligation is initially payable either on the face of the note or contract to the financial institution that is reporting the covered loan or application. For example, if a financial institution reported an origination of a covered loan that it approved prior to closing, that closed in the name of a third-party, such as a correspondent lender, and that the financial institution purchased after closing, the covered loan was not initially payable to the financial institution.
                        </P>
                        <P>
                            2. 
                            <E T="03">Applications.</E>
                             A financial institution complies with § 1003.4(a)(33)(ii) by reporting that the requirement is not applicable if the institution had not determined whether the covered loan would have been initially payable to the institution reporting the application when the application was withdrawn, denied, or closed for incompleteness.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(34)</HD>
                        <P>
                            1. 
                            <E T="03">NMLSR ID.</E>
                             Except for partially exempt transactions under § 1003.3(d), § 1003.4(a)(34) requires a financial institution to report the Nationwide Mortgage Licensing System and Registry unique identifier (NMLSR ID) for the mortgage loan originator, as defined in Regulation G, 12 CFR 1007.102, or Regulation H, 12 CFR 1008.23, as applicable. The NMLSR ID is a unique number or other identifier generally assigned to individuals registered or licensed through NMLSR to provide loan originating services. For more information, see the Secure and Fair Enforcement for Mortgage Licensing Act of 2008, title V of the Housing and Economic Recovery Act of 2008 (S.A.F.E. Act), 12 U.S.C. 5101 
                            <E T="03">et seq.,</E>
                             and its implementing regulations (12 CFR part 1007 and 12 CFR part 1008).
                        </P>
                        <P>
                            2. 
                            <E T="03">Mortgage loan originator without NMLSR ID.</E>
                             An NMLSR ID for the mortgage loan originator is not required by § 1003.4(a)(34) to be reported by a financial institution if the mortgage loan originator is not required to obtain and has not been assigned an NMLSR ID. For example, certain individual mortgage loan originators may not be required to obtain an NMLSR ID for the particular transaction being reported by the financial institution, such as a commercial loan. However, some mortgage loan originators may have obtained an NMLSR ID even if they are not required to obtain one for that particular transaction. If a mortgage loan originator has been assigned an NMLSR ID, a financial institution complies with § 1003.4(a)(34) by reporting the mortgage loan originator's NMLSR ID regardless of whether the mortgage loan originator is required to obtain an NMLSR ID for the particular transaction being reported by the financial institution. In the event that the mortgage loan originator is not required to obtain and has not been assigned an NMLSR ID, a financial institution complies with § 1003.4(a)(34) by reporting that the requirement is not applicable.
                        </P>
                        <P>
                            3. 
                            <E T="03">Multiple mortgage loan originators.</E>
                             If more than one individual associated with a covered loan or application meets the definition of a mortgage loan originator, as defined in Regulation G, 12 CFR 1007.102, or Regulation H, 12 CFR 1008.23, a financial institution complies with § 1003.4(a)(34) by reporting the NMLSR ID of the individual mortgage loan originator with primary responsibility for the transaction as of the date of action taken pursuant to § 1003.4(a)(8)(ii). A financial institution that establishes and follows a reasonable, written policy for determining which individual mortgage loan originator has primary responsibility for the reported transaction as of the date of action taken complies with § 1003.4(a)(34).
                        </P>
                        <P>
                            4. 
                            <E T="03">Purchased loans.</E>
                             If a financial institution purchases a covered loan that satisfies the coverage criteria of Regulation Z, 12 CFR 1026.36(g), and that was originated prior to January 10, 2014, the financial institution complies with § 1003.4(a)(34) by reporting that the requirement is not applicable. In addition, if a financial institution purchases a covered loan that does not satisfy the coverage criteria of Regulation Z, 12 CFR 1026.36(g), and that was originated prior to January 1, 2018, the financial institution complies with § 1003.4(a)(34) by reporting that the requirement is not applicable. Purchasers of both such types of covered loans may report the NMLSR ID.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(35)</HD>
                        <P>
                            1. 
                            <E T="03">Automated underwriting system data—general.</E>
                             Except for purchased covered loans and partially exempt transactions under § 1003.3(d), § 1003.4(a)(35) requires a financial institution to report the name of the automated underwriting system (AUS) used by the financial institution to evaluate the application and the result generated by that AUS. The following scenarios illustrate when a financial institution reports the name of the AUS used by the financial institution to evaluate the application and the result generated by that AUS.
                        </P>
                        <P>
                            i. A financial institution that uses an AUS, as defined in § 1003.4(a)(35)(ii), to evaluate an application, must report the name of the AUS used by the financial institution to evaluate the application and the result generated by that system, regardless of whether the AUS was used in its 
                            <PRTPAGE P="21038"/>
                            underwriting process. For example, if a financial institution uses an AUS to evaluate an application prior to submitting the application through its underwriting process, the financial institution complies with § 1003.4(a)(35) by reporting the name of the AUS it used to evaluate the application and the result generated by that system.
                        </P>
                        <P>ii. A financial institution that uses an AUS, as defined in § 1003.4(a)(35)(ii), to evaluate an application, must report the name of the AUS it used to evaluate the application and the result generated by that system, regardless of whether the financial institution intends to hold the covered loan in its portfolio or sell the covered loan. For example, if a financial institution uses an AUS developed by a securitizer to evaluate an application and intends to sell the covered loan to that securitizer but ultimately does not sell the covered loan and instead holds the covered loan in its portfolio, the financial institution complies with § 1003.4(a)(35) by reporting the name of the securitizer's AUS that the institution used to evaluate the application and the result generated by that system. Similarly, if a financial institution uses an AUS developed by a securitizer to evaluate an application to determine whether to originate the covered loan but does not intend to sell the covered loan to that securitizer and instead holds the covered loan in its portfolio, the financial institution complies with § 1003.4(a)(35) by reporting the name of the securitizer's AUS that the institution used to evaluate the application and the result generated by that system.</P>
                        <P>iii. A financial institution that uses an AUS, as defined in § 1003.4(a)(35)(ii), that is developed by a securitizer to evaluate an application, must report the name of the AUS it used to evaluate the application and the result generated by that system, regardless of whether the securitizer intends to hold the covered loan it purchased from the financial institution in its portfolio or securitize the covered loan. For example, if a financial institution uses an AUS developed by a securitizer to evaluate an application and the financial institution sells the covered loan to that securitizer but the securitizer holds the covered loan it purchased in its portfolio, the financial institution complies with § 1003.4(a)(35) by reporting the name of the securitizer's AUS that the institution used to evaluate the application and the result generated by that system.</P>
                        <P>iv. A financial institution, which is also a securitizer, that uses its own AUS, as defined in § 1003.4(a)(35)(ii), to evaluate an application, must report the name of the AUS it used to evaluate the application and the result generated by that system, regardless of whether the financial institution intends to hold the covered loan it originates in its portfolio, purchase the covered loan, or securitize the covered loan. For example, if a financial institution, which is also a securitizer, has developed its own AUS and uses that AUS to evaluate an application that it intends to originate and hold in its portfolio and not purchase or securitize the covered loan, the financial institution complies with § 1003.4(a)(35) by reporting the name of its AUS that it used to evaluate the application and the result generated by that system.</P>
                        <P>
                            2. 
                            <E T="03">Definition of automated underwriting system.</E>
                             A financial institution must report the information required by § 1003.4(a)(35)(i) if the financial institution uses an automated underwriting system (AUS), as defined in § 1003.4(a)(35)(ii), to evaluate an application. To be covered by the definition in § 1003.4(a)(35)(ii), a system must be an electronic tool that has been developed by a securitizer, Federal government insurer, or a Federal government guarantor of closed-end mortgage loans or open-end lines of credit. A person is a securitizer, Federal government insurer, or Federal government guarantor of closed-end mortgage loans or open-end lines of credit, respectively, if it has securitized, provided Federal government insurance, or provided a Federal government guarantee for a closed-end mortgage loan or open-end line of credit at any point in time. A person may be a securitizer, Federal government insurer, or Federal government guarantor of closed-end mortgage loans or open-end lines of credit, respectively, for purposes of § 1003.4(a)(35) even if it is not actively securitizing, insuring, or guaranteeing closed-end mortgage loans or open-end lines of credit at the time a financial institution uses the AUS to evaluate an application. Where the person that developed the electronic tool has never been a securitizer, Federal government insurer, or Federal government guarantor of closed-end mortgage loans or open-end lines of credit, respectively, at the time a financial institution uses the tool to evaluate an application, the financial institution complies with § 1003.4(a)(35) by reporting that the requirement is not applicable because an AUS was not used to evaluate the application. If a financial institution has developed its own proprietary system that it uses to evaluate an application and the financial institution is also a securitizer, then the financial institution complies with § 1003.4(a)(35) by reporting the name of that system and the result generated by that system. On the other hand, if a financial institution has developed its own proprietary system that it uses to evaluate an application and the financial institution is not a securitizer, then the financial institution is not required by § 1003.4(a)(35) to report the use of that system and the result generated by that system. In addition, for an AUS to be covered by the definition in § 1003.4(a)(35)(ii), the system must provide a result regarding both the credit risk of the applicant and the eligibility of the covered loan to be originated, purchased, insured, or guaranteed by the securitizer, Federal government insurer, or Federal government guarantor that developed the system being used to evaluate the application. For example, if a system is an electronic tool that provides a determination of the eligibility of the covered loan to be originated, purchased, insured, or guaranteed by the securitizer, Federal government insurer, or Federal government guarantor that developed the system being used by a financial institution to evaluate the application, but the system does not also provide an assessment of the creditworthiness of the applicant—such as an evaluation of the applicant's income, debt, and credit history—then that system does not qualify as an AUS, as defined in § 1003.4(a)(35)(ii). A financial institution that uses a system that is not an AUS, as defined in § 1003.4(a)(35)(ii), to evaluate an application does not report the information required by § 1003.4(a)(35)(i).
                        </P>
                        <P>
                            3. 
                            <E T="03">Reporting automated underwriting system data—multiple results.</E>
                             When a financial institution uses one or more automated underwriting systems (AUS) to evaluate the application and the system or systems generate two or more results, the financial institution complies with § 1003.4(a)(35) by reporting, except for purchased covered loans, the name of the AUS used by the financial institution to evaluate the application and the result generated by that AUS as determined by the following principles. To determine what AUS (or AUSs) and result (or results) to report under § 1003.4(a)(35), a financial institution follows each of the principles that is applicable to the application in question, in the order in which they are set forth below.
                        </P>
                        <P>i. If a financial institution obtains two or more AUS results and the AUS generating one of those results corresponds to the loan type reported pursuant to § 1003.4(a)(2), the financial institution complies with § 1003.4(a)(35) by reporting that AUS name and result. For example, if a financial institution evaluates an application using the Federal Housing Administration's (FHA) Technology Open to Approved Lenders (TOTAL) Scorecard and subsequently evaluates the application with an AUS used to determine eligibility for a non-FHA loan, but ultimately originates an FHA loan, the financial institution complies with § 1003.4(a)(35) by reporting TOTAL Scorecard and the result generated by that system. If a financial institution obtains two or more AUS results and more than one of those AUS results is generated by a system that corresponds to the loan type reported pursuant to § 1003.4(a)(2), the financial institution identifies which AUS result should be reported by following the principle set forth below in comment 4(a)(35)-3.ii.</P>
                        <P>ii. If a financial institution obtains two or more AUS results and the AUS generating one of those results corresponds to the purchaser, insurer, or guarantor, if any, the financial institution complies with § 1003.4(a)(35) by reporting that AUS name and result. For example, if a financial institution evaluates an application with the AUS of Securitizer A and subsequently evaluates the application with the AUS of Securitizer B, but the financial institution ultimately originates a covered loan that it sells within the same calendar year to Securitizer A, the financial institution complies with § 1003.4(a)(35) by reporting the name of Securitizer A's AUS and the result generated by that system. If a financial institution obtains two or more AUS results and more than one of those AUS results is generated by a system that corresponds to the purchaser, insurer, or guarantor, if any, the financial institution identifies which AUS result should be reported by following the principle set forth below in comment 4(a)(35)-3.iii.</P>
                        <P>
                            iii. If a financial institution obtains two or more AUS results and none of the systems 
                            <PRTPAGE P="21039"/>
                            generating those results correspond to the purchaser, insurer, or guarantor, if any, or the financial institution is following this principle because more than one AUS result is generated by a system that corresponds to either the loan type or the purchaser, insurer, or guarantor, the financial institution complies with § 1003.4(a)(35) by reporting the AUS result generated closest in time to the credit decision and the name of the AUS that generated that result. For example, if a financial institution evaluates an application with the AUS of Securitizer A, subsequently again evaluates the application with Securitizer A's AUS, the financial institution complies with § 1003.4(a)(35) by reporting the name of Securitizer A's AUS and the second AUS result. Similarly, if a financial institution obtains a result from an AUS that requires the financial institution to underwrite the loan manually, but the financial institution subsequently processes the application through a different AUS that also generates a result, the financial institution complies with § 1003.4(a)(35) by reporting the name of the second AUS that it used to evaluate the application and the AUS result generated by that system.
                        </P>
                        <P>iv. If a financial institution obtains two or more AUS results at the same time and the principles in comment 4(a)(35)-3.i through .iii do not apply, the financial institution complies with § 1003.4(a)(35) by reporting the name of all of the AUSs used by the financial institution to evaluate the application and the results generated by each of those systems. For example, if a financial institution simultaneously evaluates an application with the AUS of Securitizer A and the AUS of Securitizer B, the financial institution complies with § 1003.4(a)(35) by reporting the name of both Securitizer A's AUS and Securitizer B's AUS and the results generated by each of those systems. In any event, however, the financial institution does not report more than five AUSs and five results. If more than five AUSs and five results meet the criteria in this principle, the financial institution complies with § 1003.4(a)(35) by choosing any five among them to report.</P>
                        <P>
                            4. 
                            <E T="03">Transactions for which an automated underwriting system was not used to evaluate the application.</E>
                             Section 1003.4(a)(35) does not require a financial institution to evaluate an application using an automated underwriting system (AUS), as defined in § 1003.4(a)(35)(ii). For example, if a financial institution only manually underwrites an application and does not use an AUS to evaluate the application, the financial institution complies with § 1003.4(a)(35) by reporting that the requirement is not applicable since an AUS was not used to evaluate the application.
                        </P>
                        <P>
                            5. 
                            <E T="03">Purchased covered loan.</E>
                             A financial institution complies with § 1003.4(a)(35) by reporting that the requirement is not applicable when the covered loan is a purchased covered loan.
                        </P>
                        <P>
                            6. 
                            <E T="03">Non-natural person.</E>
                             When the applicant and co-applicant, if applicable, are not natural persons, a financial institution complies with § 1003.4(a)(35) by reporting that the requirement is not applicable.
                        </P>
                        <P>
                            7. 
                            <E T="03">Determination of securitizer, Federal government insurer, or Federal government guarantor.</E>
                             Section 1003.4(a)(35)(ii) provides that an “automated underwriting system” means an electronic tool developed by a securitizer, Federal government insurer, or Federal government guarantor of closed-end mortgage loans or open-end lines of credit that provides a result regarding the credit risk of the applicant and whether the covered loan is eligible to be originated, purchased, insured, or guaranteed by that securitizer, Federal government insurer, or Federal government guarantor. A person is a securitizer, Federal government insurer, or Federal government guarantor of closed-end mortgage loans or open-end lines of credit, respectively, if it has ever securitized, insured, or guaranteed a closed-end mortgage loan or open-end line of credit. If a financial institution knows or reasonably believes that the system it is using to evaluate an application is an electronic tool that has been developed by a securitizer, Federal government insurer, or Federal government guarantor of closed-end mortgage loans or open-end lines of credit, then the financial institution complies with § 1003.4(a)(35) by reporting the name of that system and the result generated by that system. Knowledge or reasonable belief could, for example, be based on a sales agreement or other related documents, the financial institution's previous transactions or relationship with the developer of the electronic tool, or representations made by the developer of the electronic tool demonstrating that the developer of the electronic tool is a securitizer, Federal government insurer, or Federal government guarantor of closed-end mortgage loans or open-end lines of credit. If a financial institution does not know or reasonably believe that the system it is using to evaluate an application is an electronic tool that has been developed by a securitizer, Federal government insurer, or Federal government guarantor of closed-end mortgage loans or open-end lines of credit, the financial institution complies with § 1003.4(a)(35) by reporting that the requirement is not applicable, provided that the financial institution maintains procedures reasonably adapted to determine whether the electronic tool it is using to evaluate an application meets the definition in § 1003.4(a)(35)(ii). Reasonably adapted procedures include attempting to determine with reasonable frequency, such as annually, whether the developer of the electronic tool is a securitizer, Federal government insurer, or Federal government guarantor of closed-end mortgage loans or open-end lines of credit. For example:
                        </P>
                        <P>i. In the course of renewing an annual sales agreement the developer of the electronic tool represents to the financial institution that it has never been a securitizer, Federal government insurer, or Federal government guarantor of closed-end mortgage loans or open-end lines of credit. On this basis, the financial institution does not know or reasonably believe that the system it is using to evaluate an application is an electronic tool that has been developed by a securitizer, Federal government insurer, or Federal government guarantor of closed-end mortgage loans or open-end lines of credit and complies with § 1003.4(a)(35) by reporting that the requirement is not applicable.</P>
                        <P>ii. Based on their previous transactions a financial institution is aware that the developer of the electronic tool it is using to evaluate an application has securitized a closed-end mortgage loan or open-end line of credit in the past. On this basis, the financial institution knows or reasonably believes that the developer of the electronic tool is a securitizer and complies with § 1003.4(a)(35) by reporting the name of that system and the result generated by that system.</P>
                        <HD SOURCE="HD3">Paragraph 4(a)(37)</HD>
                        <P>
                            1. 
                            <E T="03">Open-end line of credit.</E>
                             Except for partially exempt transactions under § 1003.3(d), § 1003.4(a)(37) requires a financial institution to identify whether the covered loan or the application is for an open-end line of credit. See comments 2(o)-1 and -2 for a discussion of open-end line of credit and extension of credit.
                        </P>
                        <HD SOURCE="HD3">Paragraph 4(a)(38)</HD>
                        <P>
                            1. 
                            <E T="03">Primary purpose.</E>
                             Except for partially exempt transactions under § 1003.3(d), § 1003.4(a)(38) requires a financial institution to identify whether the covered loan is, or the application is for a covered loan that will be, made primarily for a business or commercial purpose. See comment 3(c)(10)-2 for a discussion of how to determine the primary purpose of the transaction and the standard applicable to a financial institution's determination of the primary purpose of the transaction. See comments 3(c)(10)-3 and -4 for examples of excluded and reportable business- or commercial-purpose transactions.
                        </P>
                    </EXTRACT>
                    <STARS/>
                    <EXTRACT>
                        <FP>[The following amendments would be effective January 1, 2022, further amending the part as proposed to be amended as of January 1, 2020.]</FP>
                    </EXTRACT>
                    <AMDPAR>6. Section 1003.2 is amended by revising paragraphs (g)(1)(v)(B) and (g)(2)(ii)(B) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1003.2 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>(g)  * * * </P>
                        <P>(1)  * * * </P>
                        <P>(v)  * * * </P>
                        <P>(B) In each of the two preceding calendar years, originated at least 200 open-end lines of credit that are not excluded from this part pursuant to § 1003.3(c)(1) through (10); and</P>
                        <P>(2)  * * * </P>
                        <P>(ii)  * * * </P>
                        <P>(B) In each of the two preceding calendar years, originated at least 200 open-end lines of credit that are not excluded from this part pursuant to § 1003.3(c)(1) through (10).</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>7. Section 1003.3 is amended by revising paragraph (c)(12) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1003.3 </SECTNO>
                        <SUBJECT>Exempt institutions and excluded and partially exempt transactions.</SUBJECT>
                        <STARS/>
                        <P>
                            (c)  * * * 
                            <PRTPAGE P="21040"/>
                        </P>
                        <P>(12) An open-end line of credit, if the financial institution originated fewer than 200 open-end lines of credit in either of the two preceding calendar years; a financial institution may collect, record, report, and disclose information, as described in §§ 1003.4 and 1003.5, for such an excluded open-end line of credit as though it were a covered loan, provided that the financial institution complies with such requirements for all applications for open-end lines of credit that it receives, open-end lines of credit that it originates, and open-end lines of credit that it purchases that otherwise would have been covered loans during the calendar year during which final action is taken on the excluded open-end line of credit; or</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>8. In supplement I to part 1003:</AMDPAR>
                    <AMDPAR>
                        a. Under 
                        <E T="03">Section 1003.2—Definitions,</E>
                         revise 
                        <E T="03">2(g) Financial Institution</E>
                        ; and
                    </AMDPAR>
                    <AMDPAR>
                        b. Under 
                        <E T="03">Section 1003.3—Exempt Institutions and Excluded and Partially Exempt Transactions,</E>
                         under 
                        <E T="03">3(c) Excluded Transactions,</E>
                         revise 
                        <E T="03">Paragraph 3(c)(12)</E>
                        .
                    </AMDPAR>
                    <P>The revisions read as follows:</P>
                    <HD SOURCE="HD1">Supplement I to Part 1003—Official Interpretations</HD>
                    <EXTRACT>
                        <STARS/>
                        <HD SOURCE="HD2">Section 1003.2—Definitions</HD>
                        <STARS/>
                        <HD SOURCE="HD3">2(g) Financial Institution</HD>
                        <P>
                            1. 
                            <E T="03">Preceding calendar year and preceding December 31.</E>
                             The definition of financial institution refers both to the preceding calendar year and the preceding December 31. These terms refer to the calendar year and the December 31 preceding the current calendar year. For example, in 2019, the preceding calendar year is 2018 and the preceding December 31 is December 31, 2018. Accordingly, in 2019, Financial Institution A satisfies the asset-size threshold described in § 1003.2(g)(1)(i) if its assets exceeded the threshold specified in comment 2(g)-2 on December 31, 2018. Likewise, in 2020, Financial Institution A does not meet the loan-volume test described in § 1003.2(g)(1)(v)(A) if it originated fewer than 25 closed-end mortgage loans during either 2018 or 2019.
                        </P>
                        <P>2. [Reserved]</P>
                        <P>
                            3. 
                            <E T="03">Merger or acquisition—coverage of surviving or newly formed institution.</E>
                             After a merger or acquisition, the surviving or newly formed institution is a financial institution under § 1003.2(g) if it, considering the combined assets, location, and lending activity of the surviving or newly formed institution and the merged or acquired institutions or acquired branches, satisfies the criteria included in § 1003.2(g). For example, A and B merge. The surviving or newly formed institution meets the loan threshold described in § 1003.2(g)(1)(v)(B) if the surviving or newly formed institution, A, and B originated a combined total of at least 200 open-end lines of credit in each of the two preceding calendar years. Likewise, the surviving or newly formed institution meets the asset-size threshold in § 1003.2(g)(1)(i) if its assets and the combined assets of A and B on December 31 of the preceding calendar year exceeded the threshold described in § 1003.2(g)(1)(i). Comment 2(g)-4 discusses a financial institution's responsibilities during the calendar year of a merger.
                        </P>
                        <P>
                            4. 
                            <E T="03">Merger or acquisition—coverage for calendar year of merger or acquisition.</E>
                             The scenarios described below illustrate a financial institution's responsibilities for the calendar year of a merger or acquisition. For purposes of these illustrations, a “covered institution” means a financial institution, as defined in § 1003.2(g), that is not exempt from reporting under § 1003.3(a), and “an institution that is not covered” means either an institution that is not a financial institution, as defined in § 1003.2(g), or an institution that is exempt from reporting under § 1003.3(a).
                        </P>
                        <P>i. Two institutions that are not covered merge. The surviving or newly formed institution meets all of the requirements necessary to be a covered institution. No data collection is required for the calendar year of the merger (even though the merger creates an institution that meets all of the requirements necessary to be a covered institution). When a branch office of an institution that is not covered is acquired by another institution that is not covered, and the acquisition results in a covered institution, no data collection is required for the calendar year of the acquisition.</P>
                        <P>ii. A covered institution and an institution that is not covered merge. The covered institution is the surviving institution, or a new covered institution is formed. For the calendar year of the merger, data collection is required for covered loans and applications handled in the offices of the merged institution that was previously covered and is optional for covered loans and applications handled in offices of the merged institution that was previously not covered. When a covered institution acquires a branch office of an institution that is not covered, data collection is optional for covered loans and applications handled by the acquired branch office for the calendar year of the acquisition.</P>
                        <P>iii. A covered institution and an institution that is not covered merge. The institution that is not covered is the surviving institution, or a new institution that is not covered is formed. For the calendar year of the merger, data collection is required for covered loans and applications handled in offices of the previously covered institution that took place prior to the merger. After the merger date, data collection is optional for covered loans and applications handled in the offices of the institution that was previously covered. When an institution remains not covered after acquiring a branch office of a covered institution, data collection is required for transactions of the acquired branch office that take place prior to the acquisition. Data collection by the acquired branch office is optional for transactions taking place in the remainder of the calendar year after the acquisition.</P>
                        <P>iv. Two covered institutions merge. The surviving or newly formed institution is a covered institution. Data collection is required for the entire calendar year of the merger. The surviving or newly formed institution files either a consolidated submission or separate submissions for that calendar year. When a covered institution acquires a branch office of a covered institution, data collection is required for the entire calendar year of the merger. Data for the acquired branch office may be submitted by either institution.</P>
                        <HD SOURCE="HD1">Alternative 1—Paragraph 2(g)-5</HD>
                        <P>
                            5. 
                            <E T="03">Originations.</E>
                             Whether an institution is a financial institution depends in part on whether the institution originated at least 50 closed-end mortgage loans in each of the two preceding calendar years or at least 200 open-end lines of credit in each of the two preceding calendar years. Comments 4(a)-2 through -4 discuss whether activities with respect to a particular closed-end mortgage loan or open-end line of credit constitute an origination for purposes of § 1003.2(g).
                        </P>
                        <HD SOURCE="HD1">Alternative 2—Paragraph 2(g)-5</HD>
                        <P>
                            5. 
                            <E T="03">Originations.</E>
                             Whether an institution is a financial institution depends in part on whether the institution originated at least 100 closed-end mortgage loans in each of the two preceding calendar years or at least 200 open-end lines of credit in each of the two preceding calendar years. Comments 4(a)-2 through -4 discuss whether activities with respect to a particular closed-end mortgage loan or open-end line of credit constitute an origination for purposes of § 1003.2(g).
                        </P>
                        <P>
                            6. 
                            <E T="03">Branches of foreign banks—treated as banks.</E>
                             A Federal branch or a State-licensed or insured branch of a foreign bank that meets the definition of a “bank” under section 3(a)(1) of the Federal Deposit Insurance Act (12 U.S.C. 1813(a)) is a bank for the purposes of § 1003.2(g).
                        </P>
                        <P>
                            7. 
                            <E T="03">Branches and offices of foreign banks and other entities—treated as nondepository financial institutions.</E>
                             A Federal agency, State-licensed agency, State-licensed uninsured branch of a foreign bank, commercial lending company owned or controlled by a foreign bank, or entity operating under section 25 or 25A of the Federal Reserve Act, 12 U.S.C. 601 and 611 (Edge Act and agreement corporations) may not meet the definition of “bank” under the Federal Deposit Insurance Act and may thereby fail to satisfy the definition of a depository financial institution under § 1003.2(g)(1). An entity is nonetheless a financial institution if it meets the definition of nondepository financial institution under § 1003.2(g)(2).
                        </P>
                        <STARS/>
                        <HD SOURCE="HD2">Section 1003.3—Exempt Institutions and Excluded and Partially Exempt Transactions</HD>
                        <HD SOURCE="HD3">3(c) Excluded Transactions</HD>
                        <STARS/>
                        <HD SOURCE="HD3">Paragraph 3(c)(12)</HD>
                        <P>
                            1. 
                            <E T="03">General.</E>
                             Section 1003.3(c)(12) provides that an open-end line of credit is an excluded transaction if a financial institution originated fewer than 200 open-end lines of 
                            <PRTPAGE P="21041"/>
                            credit in either of the two preceding calendar years. For example, assume that a bank is a financial institution in 2022 under § 1003.2(g) because it originated 100 closed-end mortgage loans in 2020, 175 closed-end mortgage loans in 2021, and met all of the other requirements under § 1003.2(g)(1). Also assume that the bank originated 75 and 85 open-end lines of credit in 2020 and 2021, respectively. The closed-end mortgage loans that the bank originated or purchased, or for which it received applications, during 2022 are covered loans and must be reported, unless they otherwise are excluded transactions under § 1003.3(c). However, the open-end lines of credit that the bank originated or purchased, or for which it received applications, during 2022 are excluded transactions under § 1003.3(c)(12) and need not be reported. See comments 4(a)-2 through -4 for guidance about the activities that constitute an origination.
                        </P>
                        <P>
                            2. 
                            <E T="03">Optional reporting.</E>
                             A financial institution may report applications for, originations of, or purchases of open-end lines of credit that are excluded transactions because the financial institution originated fewer than 200 open-end lines of credit in either of the two preceding calendar years. However, a financial institution that chooses to report such excluded applications for, originations of, or purchases of open-end lines of credit must report all such applications for open-end lines of credit which it receives, open-end lines of credit that it originates, and open-end lines of credit that it purchases that otherwise would be covered loans for a given calendar year. Note that applications which remain pending at the end of a calendar year are not reported, as described in comment 4(a)(8)(i)-14.
                        </P>
                        <STARS/>
                    </EXTRACT>
                    <SIG>
                        <DATED> Dated: April 26, 2019.</DATED>
                        <NAME>Kathleen L. Kraninger,</NAME>
                        <TITLE>Director, Bureau of Consumer Financial Protection.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2019-08983 Filed 5-10-19; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4810-AM-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>84</VOL>
    <NO>92</NO>
    <DATE>Monday, May 13, 2019</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="21043"/>
            <PARTNO>Part III</PARTNO>
            <AGENCY TYPE="P"> Commodity Futures Trading Commission</AGENCY>
            <CFR>17 CFR Parts 23, 43, 45, and 49</CFR>
            <TITLE>Certain Swap Data Repository and Data Reporting Requirements; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="21044"/>
                    <AGENCY TYPE="S">COMMODITY FUTURES TRADING COMMISSION</AGENCY>
                    <CFR>17 CFR Parts 23, 43, 45, and 49</CFR>
                    <RIN>RIN Number 3038-AE32</RIN>
                    <SUBJECT>Certain Swap Data Repository and Data Reporting Requirements</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Commodity Futures Trading Commission.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice of proposed rulemaking.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The Commodity Futures Trading Commission (“Commission” or “CFTC”) is proposing amendments to parts 23, 43, 45, and 49 of the Commission's regulations to improve the accuracy of data reported to, and maintained by, swap data repositories (“SDRs”). Among other changes, the proposed amendments would modify existing requirements for SDRs to establish policies and procedures to confirm the accuracy of swap data with both counterparties to a swap. The proposed amendments would further require reporting counterparties to verify the accuracy of swap data pursuant to those SDR procedures. The Commission is also proposing certain amendments to parts 23, 43, 45, and 49 to provide enhanced and streamlined oversight over SDRs and data reporting generally.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Comments must be received on or before July 29, 2019.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>You may submit comments, identified by RIN number 3038-AE32, by any of the following methods:</P>
                        <P>
                            • The agency's website, at 
                            <E T="03">http://comments.cftc.gov.</E>
                             Follow the instructions for submitting comments through the website.
                        </P>
                        <P>
                            • 
                            <E T="03">Mail:</E>
                             Secretary of the Commission, Commodity Futures Trading Commission, Three Lafayette Centre, 1155 21st Street NW, Washington, DC 20581.
                        </P>
                        <P>
                            • 
                            <E T="03">Hand Delivery/Courier:</E>
                             Same as Mail above.
                        </P>
                        <P>Please submit your comments using only one method.</P>
                        <P>
                            All comments must be submitted in English, or if not, accompanied by an English translation. Comments will be posted as received to 
                            <E T="03">http://www.cftc.gov.</E>
                             You should submit only information that you wish to make available publicly. If you wish the Commission to consider information that you believe is exempt from disclosure under the Freedom of Information Act, a petition for confidential treatment of the exempt information may be submitted according to the procedures established in § 145.9 of the Commission's regulations.
                            <SU>1</SU>
                            <FTREF/>
                        </P>
                        <FTNT>
                            <P>
                                <SU>1</SU>
                                 17 CFR 145.9.
                            </P>
                        </FTNT>
                        <P>
                            The Commission reserves the right, but shall have no obligation, to review, pre-screen, filter, redact, refuse or remove any or all of your submission from 
                            <E T="03">http://www.cftc.gov</E>
                             that it may deem to be inappropriate for publication, such as obscene language. All submissions that have been redacted or removed that contain comments on the merits of the rulemaking will be retained in the public comment file and will be considered as required under the Administrative Procedure Act and other applicable laws, and may be accessible under the Freedom of Information Act.
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Benjamin DeMaria, Special Counsel, 202-418-5988, 
                            <E T="03">bdemaria@cftc.gov</E>
                             or Meghan Tente, Lead Attorney-Advisor, 202-418-5785, 
                            <E T="03">mtente@cftc.gov,</E>
                             Division of Market Oversight, Data and Reporting Branch, Commodity Futures Trading Commission, Three Lafayette Centre, 1151 21st Street NW, Washington, DC 20581.
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P/>
                    <HD SOURCE="HD1">Table of Contents</HD>
                    <EXTRACT>
                        <FP SOURCE="FP-2">I. Background</FP>
                        <FP SOURCE="FP1-2">A. Introduction</FP>
                        <FP SOURCE="FP1-2">B. Statutory Authority</FP>
                        <FP SOURCE="FP1-2">C. Regulatory History—Final Rulemakings</FP>
                        <FP SOURCE="FP-2">II. Proposed Amendments to Part 49</FP>
                        <FP SOURCE="FP1-2">A. § 49.2—Definitions</FP>
                        <FP SOURCE="FP1-2">B. § 49.3—Procedures for Registration</FP>
                        <FP SOURCE="FP1-2">C. § 49.5—Equity Interest Transfers</FP>
                        <FP SOURCE="FP1-2">D. § 49.6—Request for Transfer of Registration</FP>
                        <FP SOURCE="FP1-2">E. § 49.9—Open Swaps Reports Provided to the Commission</FP>
                        <FP SOURCE="FP1-2">F. § 49.10—Acceptance of Data</FP>
                        <FP SOURCE="FP1-2">G. § 49.11—Verification of Swap Data Accuracy</FP>
                        <FP SOURCE="FP1-2">H. § 49.12—Swap Data Repository Recordkeeping Requirements</FP>
                        <FP SOURCE="FP1-2">I. § 49.13—Monitoring, Screening, and Analyzing Data</FP>
                        <FP SOURCE="FP1-2">J. § 49.15—Real-Time Public Reporting by Swap Data Repositories</FP>
                        <FP SOURCE="FP1-2">K. § 49.16—Privacy and Confidentiality Requirements of Swap Data Repositories</FP>
                        <FP SOURCE="FP1-2">L. § 49.17—Access to SDR Data</FP>
                        <FP SOURCE="FP1-2">M. § 49.18—Confidentiality Arrangement</FP>
                        <FP SOURCE="FP1-2">N. § 49.20—Governance Arrangements (Core Principle 2)</FP>
                        <FP SOURCE="FP1-2">O. § 49.22—Chief Compliance Officer</FP>
                        <FP SOURCE="FP1-2">P. § 49.24—System Safeguards</FP>
                        <FP SOURCE="FP1-2">Q. § 49.25—Financial Resources</FP>
                        <FP SOURCE="FP1-2">R. § 49.26—Disclosure Requirements of Swap Data Repositories</FP>
                        <FP SOURCE="FP1-2">S. § 49.28—Operating Hours of Swap Data Repositories</FP>
                        <FP SOURCE="FP1-2">T. § 49.29—Information Relating to Swap Data Repository Compliance</FP>
                        <FP SOURCE="FP1-2">U. § 49.30—Form and Manner of Reporting and Submitting Information to the Commission</FP>
                        <FP SOURCE="FP1-2">V. § 49.31—Delegation of Authority to the Director of the Division of Market Oversight Relating to Certain Part 49 Matters</FP>
                        <FP SOURCE="FP-2">III. Proposed Amendments to Part 45</FP>
                        <FP SOURCE="FP1-2">A. § 45.2—Swap Recordkeeping</FP>
                        <FP SOURCE="FP1-2">B. § 45.14—Verification of Swap Data Accuracy and Correcting Errors and Omissions in Swap Data</FP>
                        <FP SOURCE="FP-2">IV. Proposed Amendments to Part 43</FP>
                        <FP SOURCE="FP1-2">A. § 43.3—Method and Timing for Real-Time Public Reporting</FP>
                        <FP SOURCE="FP-2">V. Proposed Amendments to Part 23</FP>
                        <FP SOURCE="FP1-2">A. § 23.204—Reports to Swap Data Repositories</FP>
                        <FP SOURCE="FP1-2">B. § 23.205—Real-Time Public Reporting</FP>
                        <FP SOURCE="FP-2">VI. Request for Comments</FP>
                        <FP SOURCE="FP-2">VII. Related Matters</FP>
                        <FP SOURCE="FP1-2">A. Regulatory Flexibility Act</FP>
                        <FP SOURCE="FP1-2">B. Paperwork Reduction Act</FP>
                        <FP SOURCE="FP1-2">C. Cost-Benefit Considerations</FP>
                        <FP SOURCE="FP1-2">D. Anti-Trust Considerations</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">I. Background</HD>
                    <HD SOURCE="HD2">A. Introduction</HD>
                    <P>
                        Pursuant to the Dodd-Frank Act,
                        <SU>2</SU>
                        <FTREF/>
                         beginning in 2011, the Commission adopted parts 45 and 49 of its regulations to implement a swap data reporting and recordkeeping regime along with registration requirements and duties for SDRs.
                        <SU>3</SU>
                        <FTREF/>
                         In 2012, the Commission adopted part 23 of its regulations, which sets forth requirements for swap dealers (“SDs”) and major swap participants (“MSPs”) related to the timely and accurate reporting, confirmation, and processing of swaps.
                        <SU>4</SU>
                        <FTREF/>
                         The regulations the Commission is proposing to amend with this release concern data reporting and recordkeeping duties generally and other duties for SDRs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             
                            <E T="03">See</E>
                             Dodd-Frank Wall Street Reform and Consumer Protection Act, Public Law 111-203, 124 Stat. 1376 (2010), 
                            <E T="03">available at https://www.gpo.gov/fdsys/pkg/PLAW-111publ203/pdf/PLAW-111publ203.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             Swap Data Repositories: Registration Standards, Duties and Core Principles, 76 FR 54538 (Sept. 1, 2011) (“Part 49 Adopting Release”); Swap Data Recordkeeping and Reporting Requirements, 77 FR 2136 (Jan. 13, 2012) (“Part 45 Adopting Release”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             
                            <E T="03">See</E>
                             Swap Dealer and Major Swap Participant Recordkeeping, Reporting, and Duties Rules; Futures Commission Merchant and Introducing Broker Conflicts of Interest Rules; and Chief Compliance Officer Rules for Swap Dealers, Major Swap Participants, and Futures Commission Merchants, 77 FR 20128 (Apr. 3, 2012) (“Part 23 Adopting Release”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Statutory Authority</HD>
                    <P>
                        Section 727 of the Dodd-Frank Act added section 2(a)(13)(G) to the Commodity Exchange Act (“CEA” or “Act”), which requires all swaps—whether cleared or uncleared—to be reported to SDRs,
                        <SU>5</SU>
                        <FTREF/>
                         which are registered 
                        <PRTPAGE P="21045"/>
                        entities created by section 728 of the Dodd-Frank Act.
                        <SU>6</SU>
                        <FTREF/>
                         Section 728 of the Dodd-Frank Act added section 21 to the CEA,
                        <SU>7</SU>
                        <FTREF/>
                         which governs registration and regulation of SDRs, and directs the Commission to promulgate rules concerning those duties and responsibilities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             Section 721 of the Dodd-Frank Act amended section 1a of the CEA to add the definition of SDR. Pursuant to section 1a(48) of the CEA, the term SDR “means any person that collects and maintains information or records with respect to transactions or positions in, or the terms and conditions of, swaps entered into by third parties for the purpose 
                            <PRTPAGE/>
                            of providing a centralized recordkeeping facility for swaps.” 7 U.S.C. 1a(48).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             The Commission notes that there are currently three SDRs provisionally registered with the Commission: CME Inc., DTCC Data Repository (U.S.) LLC (“DDR”), and ICE Trade Vault, LLC (“ICE”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             7 U.S.C. 24a.
                        </P>
                    </FTNT>
                    <P>
                        To register and maintain registration with the Commission, SDRs are required to comply with specific duties and core principles enumerated in CEA section 21 as well as other requirements that the Commission may prescribe by rule. In particular, CEA section 21(c) mandates that SDRs: (1) Accept data; (2) confirm with both counterparties the accuracy of submitted data; (3) maintain data according to standards prescribed by the Commission; (4) provide direct electronic access to the Commission or any designee of the Commission (including another registered entity); (5) provide public reporting of data in the form and frequency required by the Commission; (6) establish automated systems for monitoring, screening, and analyzing data (including the use of end-user clearing exemptions) at the direction of the Commission; (7) maintain data privacy; (8) make data available to other specified regulators, on a confidential basis, pursuant to section 8 of the CEA,
                        <SU>8</SU>
                        <FTREF/>
                         upon request and after notifying the Commission; and (9) establish and maintain emergency and business continuity-disaster recovery (“BC-DR”) procedures. CEA section 21(f)(4)(C) further requires the Commission to establish additional duties for SDRs to minimize conflicts of interest, protect data, ensure compliance, and guarantee the safety and security of the SDR.
                        <SU>9</SU>
                        <FTREF/>
                         Section 21(b) of the CEA also directs the Commission to prescribe standards for data recordkeeping and reporting that apply to both registered entities and reporting counterparties.
                        <SU>10</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             7 U.S.C. 12(e).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             Pursuant to this provision, the Commission may develop one or more additional duties applicable to SDRs. 7 U.S.C. 24a(f)(4). This provision is referred to as “Core Principle 4.”
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             
                            <E T="03">See</E>
                             7 U.S.C. 24a(b)(1)(B).
                        </P>
                    </FTNT>
                    <P>
                        Section 4s(f) of the CEA,
                        <SU>11</SU>
                        <FTREF/>
                         added by section 731 of the Dodd-Frank Act, established recordkeeping and reporting requirements for SDs and MSPs. CEA section 4s(f)(1)(A) 
                        <SU>12</SU>
                        <FTREF/>
                         requires SDs and MSPs, among other things, to provide transaction and position reports that the Commission requires by rule or regulation. CEA section 4s(f)(2) 
                        <SU>13</SU>
                        <FTREF/>
                         requires the Commission to adopt rules governing, among other things, recordkeeping and reporting by SDs and MSPs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             7 U.S.C. 6s(f).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             7 U.S.C. 6s(f)(1)(A).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             7 U.S.C. 6s(f)(2).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">C. Regulatory History—Final Rulemakings</HD>
                    <P>
                        On August 4, 2011, the Commission adopted part 49 of the Commission's regulations.
                        <SU>14</SU>
                        <FTREF/>
                         Part 49 implements the requirements of section 21 of the CEA by setting forth the specific duties that SDRs are required to comply with to be initially registered as an SDR and maintain such registration as an SDR with the Commission. As part of the Part 49 Adopting Release, the Commission, among other sections, adopted § 49.11 regarding the confirmation of data accuracy.
                    </P>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             
                            <E T="03">See</E>
                             Part 49 Adopting Release.
                        </P>
                    </FTNT>
                    <P>
                        Pursuant to CEA section 4s(f)(2), the Commission promulgated swap reporting rules for SDs and MSPs, including §§ 23.204-205, which were both adopted on April 3, 2012.
                        <SU>15</SU>
                        <FTREF/>
                         Section 23.204(a) requires SDs and MSPs to report all information and swap data in accordance with part 45. Section 23.204(b) requires SDs and MSPs to have the procedures and electronic systems necessary to report all information and swap data required to be reported in accordance with part 45. Sections 23.205(a) and (b) establish parallel requirements for SDs and MSPs with respect to the real-time reporting requirements of part 43.
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             
                            <E T="03">See</E>
                             Part 23 Adopting Release.
                        </P>
                    </FTNT>
                    <P>
                        Since the Commission adopted part 49 in 2011, Commission staff has led many efforts to evaluate and improve reporting issues relating to data accuracy. Commission staff leads or participates in several international regulatory working groups concentrating on harmonization of data reporting and is incorporating in this release lessons learned from these undertakings and best practices from the international regulatory community. Commission staff's efforts have also included the formation of an interdivisional staff working group to identify, and make recommendations to resolve, reporting challenges associated with certain swap data recordkeeping and reporting provisions.
                        <SU>16</SU>
                        <FTREF/>
                         The Commission has also requested comments from the public on reporting issues.
                        <SU>17</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             
                            <E T="03">See</E>
                             Press Release, CFTC to Form an Interdivisional Working Group to Review Regulatory Reporting (Jan. 21, 2014), 
                            <E T="03">available at http://www.cftc.gov/PressRoom/PressReleases/pr6837-14.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             
                            <E T="03">See, e.g.,</E>
                             Review of Swap Data Recordkeeping and Reporting Requirements, Request for Comment, 79 FR 16689 (Mar. 26, 2014).
                        </P>
                    </FTNT>
                    <P>
                        Throughout these ongoing efforts, the Commission has generally adhered to the view that verification of data accuracy can be achieved through: (i) SDR processes confirming the accuracy of data submitted; (ii) data reconciliation exercises by entities that reported data; and (iii) the prompt reporting of errors and omissions when discovered.
                        <SU>18</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             
                            <E T="03">See id.</E>
                             at 16695.
                        </P>
                    </FTNT>
                    <P>
                        Most recently, based in part on information received during the ongoing efforts described above, Commission staff announced a comprehensive review of swap reporting regulations and released the Roadmap to Achieve High Quality Swap Data (“Roadmap”) 
                        <SU>19</SU>
                        <FTREF/>
                         to solicit feedback on improvements to data reporting and how the Commission's regulatory goals may be achieved without imposing unnecessary burdens on market participants. Commission staff requested comments in response to the Roadmap (“Roadmap Request for Comment”) and received a number of comment letters that addressed data accuracy and confirmation of data reported to SDRs, among other subjects.
                        <SU>20</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             
                            <E T="03">See</E>
                             CFTC Letter 17-33, Division of Market Oversight Announces Review of Swap Reporting Rules in Parts 43, 45, and 49 of Commission Regulations (July 10, 2017), 
                            <E T="03">available at http://www.cftc.gov/idc/groups/public/@lrlettergeneral/documents/letter/17-33.pdf;</E>
                             Roadmap to Achieve High Quality Swap Data, 
                            <E T="03">available at http://www.cftc.gov/idc/groups/public/@newsroom/documents/file/dmo_swapdataplan071017.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             These comment letters are 
                            <E T="03">available at https://comments.cftc.gov/PublicComments/CommentList.aspx?id=1824.</E>
                        </P>
                    </FTNT>
                    <P>
                        References to “commenters” in this release refer to those who submitted comment letters in response to the Roadmap Request for Comment. Summaries and a discussion of the relevant comments submitted by those commenters appear in the appropriate section in this release.
                        <SU>21</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             
                            <E T="03">See</E>
                             section II.G.1.
                        </P>
                    </FTNT>
                    <P>
                        The revisions and additions proposed in this release are intended to address the SDR Operations Review goals of the Roadmap related to confirming the accuracy of swap data,
                        <SU>22</SU>
                        <FTREF/>
                         to improve the clarity and consistency of regulations governing SDRs, and to bolster the Commission's oversight of SDRs. This proposal is the first of three anticipated Roadmap rulemakings that, when all of 
                        <PRTPAGE P="21046"/>
                        the planned rulemakings are complete, should achieve the Roadmap's overall goals of improving the quality, accuracy, and completeness of the data reported to the Commission, streamlining data reporting, and clarifying obligations for market participants.
                        <SU>23</SU>
                        <FTREF/>
                         When the Commission proposes the next two rulemakings, the Commission anticipates re-opening the comment period for this proposal to provide market participants with an opportunity to comment collectively on the three rulemakings together, because the proposals address interconnected issues. As the Roadmap rulemakings must all work in tandem to achieve these goals, the Commission also anticipates that key provisions of each rulemaking would have the same compliance date, regardless of when each rulemaking is released in final form. The Commission intends to provide a sufficient implementation period for these various rulemakings in order to give SDRs and market participants enough time to implement and test the changes that would be required.
                    </P>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             
                            <E T="03">See</E>
                             Roadmap, p. 6 (stating the Commission's intent to “Identify the most efficient and effective solution for swap counterparty(ies) to confirm the accuracy and completeness of data held in an SDR.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             
                            <E T="03">See id.</E>
                             at 3 (describing the Commission's goals for the review of reporting regulations).
                        </P>
                    </FTNT>
                    <P>
                        Where possible, in creating the proposed regulations set forth in this release, the Commission has taken into consideration certain pertinent rules adopted by other regulators, including the European Securities and Markets Authority (“ESMA”) and the U.S. Securities and Exchange Commission (“SEC”).
                        <SU>24</SU>
                        <FTREF/>
                         This is particularly the case for the SEC's regulations relating to the registration, duties, and core principles of Security-Based Swap Data Repositories (“SBSDRs”) 
                        <SU>25</SU>
                        <FTREF/>
                         and reporting requirements for Security-Based Swaps (“SBSs”) set forth in Regulation SBSR (“Regulation SBSR”).
                        <SU>26</SU>
                        <FTREF/>
                         The Commission notes that there are similarities between the regulatory framework for SBSDRs and the SDR regulations that are the subject of this proposal.
                    </P>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                             The Commission has also reviewed the SEC's recent proposed rule on risk mitigation techniques for uncleared security-based swaps, which addresses issues related to reconciling security-based swap transactions and confirming the transaction data. 
                            <E T="03">See generally</E>
                             Risk Mitigation Techniques for Uncleared Security-Based Swaps, 84 FR 4614 (Feb. 15, 2019).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>25</SU>
                             
                            <E T="03">See generally</E>
                             Security-Based Swap Data Repository Registration, Duties and Core Principles, 80 FR 11438 (Mar. 19, 2015) (“SBSDR Adopting Release”). The SEC adopted Rules 13n-1 through 13n-12 (17 CFR 240n-1 through 240n-12) under the Securities Exchange Act of 1934 (“Exchange Act”) relating to the registration and operation of SBSDRs.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>26</SU>
                             
                            <E T="03">See generally</E>
                             Regulation SBSR—Reporting and Dissemination of Security-Based Swap Information, 80 FR 14740 (Mar. 19, 2015) (“SBSR Adopting Release”). The SEC adopted Regulation SBSR (Rules 900 through 909, 17 CFR 242.900 through 909) to create a reporting framework for SBSs. The SEC has also adopted additional regulations regarding the reporting and dissemination of certain information related to SBSs. 
                            <E T="03">See generally</E>
                             81 FR 53546 (Aug. 12, 2016).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">II. Proposed Amendments to Part 49</HD>
                    <HD SOURCE="HD2">A. § 49.2—Definitions</HD>
                    <HD SOURCE="HD3">1. Formatting Change to § 49.2(a)</HD>
                    <P>
                        The defined terms in § 49.2(a) currently are numbered and arranged in alphabetical order. The Commission is proposing to remove the numbering and instead arrange the defined terms in § 49.2(a) solely in alphabetical order. Arranging the defined terms in § 49.2(a) solely in alphabetical order would require the Commission to make fewer conforming changes to § 49.2(a) and other regulations when adding or removing defined terms in the future, as the Commission currently proposes to do.
                        <SU>27</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>27</SU>
                             The Office of the Federal Register prefers the solely alphabetical approach to definitions sections. 
                            <E T="03">See</E>
                             Office of the Federal Register, Document Drafting Handbook May 2017 Update, Revision 5, 2-31 (2017) (“
                            <E T="03">Definitions.</E>
                             In sections or paragraphs containing only definitions, we recommend that you do not use paragraph designations if you list the terms in alphabetical order.”).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Proposed Changes to § 49.2</HD>
                    <HD SOURCE="HD3">i. Conforming and Ministerial Changes to Some Definitions</HD>
                    <P>
                        The Commission proposes non-substantive conforming and ministerial changes to certain definitions to provide clarity and for consistency with other Commission regulations.
                        <SU>28</SU>
                        <FTREF/>
                         Specifically, the Commission is proposing the following changes to definitions in § 49.2(a):
                    </P>
                    <FTNT>
                        <P>
                            <SU>28</SU>
                             Other than removing subsection numbering and ministerial corrections as discussed above in section II.A.1, the Commission is not proposing any substantive changes to the definitions of “affiliate,” “control,” “foreign regulator,” “independent perspective,” “position,” or “section 8 material,” as those terms are defined in current § 49.2(a).
                        </P>
                    </FTNT>
                    <P>
                        • “Asset class”: Modify the definition to conform the wording to the definition of “asset class” used in part 43.
                        <SU>29</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.2 (Asset class means a broad category of commodities including, without limitation, any “excluded commodity” as defined in section 1a(19) of the Act, with common characteristics underlying a swap. The asset classes include interest rate, foreign exchange, credit, equity, other commodity and such other asset classes as may be determined by the Commission.).
                        </P>
                    </FTNT>
                    <P>• “Commercial use”: Modify the definition to use active instead of passive voice, and to change use of swap data for regulatory purposes and/or responsibilities to use of SDR data for regulatory purposes and/or to perform its regulatory responsibilities.</P>
                    <P>• “Market participant”: Change the term “swaps execution facilities” to “swap execution facilities,” to conform to section 5h of the Act and other Commission regulations, and make the term counterparty singular.</P>
                    <P>• “Non-affiliated third party”: Clarify paragraph (3) to identify “a person jointly employed” by an SDR and any affiliate.</P>
                    <P>• “Person associated with a swap data repository”: Clarify that paragraph (3) includes a “jointly employed person.”</P>
                    <P>• “Swap data”: Modify the definition to more closely match the related definitions of “SDR data” and “swap transaction and pricing data” that are being added to § 49.2(a) and to incorporate the requirements to provide swap data to the Commission pursuant to part 49.</P>
                    <P>Finally, the Commission proposes to remove the term “capitalized” from § 49.2(b), to reflect that most defined terms used in part 49 are not capitalized in the text of part 49. The Commission does not consider any of the above changes to be substantive.</P>
                    <HD SOURCE="HD3">ii. “As Soon As Technologically Practicable”</HD>
                    <P>
                        The Commission proposes to add the term “as soon as technologically practicable” as a defined term to standardize the meaning and use of this term across the Commission's swap reporting regulations. The term as soon as technologically practicable would mean as soon as possible, taking into consideration the prevalence, implementation, and use of technology by comparable market participants. The term is intended to be identical to the use of the term as it is used in parts 43 and 45 of the Commission's regulations.
                        <SU>30</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>30</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.2 (defining of as soon as technologically practicable). Part 45 of the Commission's regulations also uses the term “as soon as technologically practicable” in the same way as part 43 and this proposed definition, but does not define the term.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iii. “Non-Swap Dealer/Major Swap Participant/Derivatives Clearing Organization Reporting Counterparty”</HD>
                    <P>
                        The Commission proposes to add the term “non-swap dealer/major swap participant/derivatives clearing organization reporting counterparty,” defined to mean a reporting counterparty that is not a swap dealer, major swap participant, derivatives clearing organization, or exempt derivatives clearing organization. The Commission believes the defined term would provide clarity in part 49.
                        <PRTPAGE P="21047"/>
                    </P>
                    <HD SOURCE="HD3">iv. “Open Swap”</HD>
                    <P>
                        The Commission proposes to add the term “open swap” as a defined term and to define the term as an executed swap transaction that has not reached maturity or the final contractual settlement date, and has not been exercised, closed out, or terminated. The Commission considers an “open swap” to mean a swap that is still in force or “alive.” This definition is intended to function the same as the definitions of “open swap” 
                        <SU>31</SU>
                        <FTREF/>
                         and “closed swap” 
                        <SU>32</SU>
                        <FTREF/>
                         in part 20, but provides more clarity as to the Commission's meaning of the term.
                    </P>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             
                            <E T="03">See</E>
                             17 CFR 20.1 (Open swap or swaption means a swap or swaption that has not been closed.).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             
                            <E T="03">See</E>
                             17 CFR 20.1 (Closed swap or closed swaption means a swap or swaption that has been settled, exercised, closed out, or terminated.).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">v. “Reporting Counterparty”</HD>
                    <P>
                        The Commission proposes to add the term “reporting counterparty” as a defined term to standardize its meaning and use across the Commission's swap reporting regulations. Reporting counterparty would mean the counterparty responsible for reporting SDR data to an SDR pursuant to parts 43, 45, or 46 of the Commission's regulations. The term is intended to be functionally equivalent to the term “reporting party,” as defined in part 43,
                        <SU>33</SU>
                        <FTREF/>
                         the term “reporting counterparty,” as defined in part 45,
                        <SU>34</SU>
                        <FTREF/>
                         and the term “reporting counterparty,” as defined in part 46.
                        <SU>35</SU>
                        <FTREF/>
                         The Commission notes that the reporting counterparty may not always be the entity reporting SDR data to the SDR, particularly for transactions executed on swap execution facilities (“SEFs”) or designated contract markets (“DCMs”), but it is the counterparty responsible for the initial and subsequent SDR data reporting, as determined by parts 43, 45, or 46 of the Commission's regulations, as applicable to a particular swap.
                    </P>
                    <FTNT>
                        <P>
                            <SU>33</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.2 (Reporting party means the party to a swap with the duty to report a publicly reportable swap transaction in accordance with part 43 and section 2(a)(13)(F) of the CEA.).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>34</SU>
                             
                            <E T="03">See</E>
                             17 CFR 45.1 (Reporting counterparty means the counterparty required to report swap data pursuant to part 45, selected as provided in § 45.8.).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>35</SU>
                             
                            <E T="03">See</E>
                             17 CFR 46.1 (Reporting counterparty means the counterparty required to report swap data pursuant to part 46, selected as provided in § 46.5.).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">vi. “SDR Data”</HD>
                    <P>The Commission proposes to add the term “SDR data” as a defined term. SDR data would mean the specific data elements and information required to be reported to an SDR or disseminated by an SDR, pursuant to two or more of parts 43, 45, 46, and/or 49, as applicable. The Commission notes that in this context, “disseminated” would include SDRs making swap data available to the Commission as required by part 49.</P>
                    <P>The term SDR data would refer to multiple sources of data reported to the SDR or disseminated by the SDR. For example, SDR data could refer to all data reported or disseminated pursuant to parts 43, 45, and 46, or may refer to data reported or disseminated pursuant to parts 45 and 46, depending on the context in which the term is used. This is in contrast with the proposed term “swap transaction and pricing data,” discussed below, which would only refer to data reported to the SDR or publicly disseminated by the SDR pursuant to part 43 and the term “swap data,” which would only refer to data reported to the SDR or made available to the Commission pursuant to part 45. The Commission believes that consolidating references to the different types of data that must be reported to an SDR and data the SDR must make available to the public or to the Commission into a single term would provide clarity throughout part 49.</P>
                    <HD SOURCE="HD3">vii. “SDR Information”</HD>
                    <P>
                        The Commission proposes to amend the existing definition of “SDR information” to add “related to the business of the swap data repository that is not SDR data” to the end of the current definition. The Commission believes this change would make clear that the scope of SDR information is limited to information that the SDR receives or maintains related to its business that is not the SDR data reported to or disseminated by the SDR. SDR information would include, for example, SDR policies and procedures created pursuant to part 49.
                        <SU>36</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>36</SU>
                             This clarification is particularly relevant for the SDR recordkeeping obligations in the proposed amendments to § 49.12, discussed below in section II.H.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">viii. “Swap Transaction and Pricing Data” and “As Soon as Technologically Practicable”</HD>
                    <P>The Commission proposes to add the terms “swap transaction and pricing data” and “as soon as technologically practicable” as defined terms from part 43. Swap transaction and pricing data would mean the data elements and information required to be reported to an SDR or publicly disseminated by an SDR, as applicable, pursuant to part 43. Though this phrase is not currently defined in part 43, it is used throughout that part to refer to the data that must be reported to an SDR and publicly disseminated by an SDR pursuant to part 43, and the meaning of the term added here is identical. The Commission is proposing to adopt the same definition of as soon as technologically practicable defined in part 43, which means as soon as possible, taking into consideration the prevalence, implementation, and use of technology by comparable market participants. The Commission is proposing to add both phrases as defined terms in part 49 to increase consistency in terminology used in the Commission's swap reporting regulations.</P>
                    <HD SOURCE="HD3">ix. Removal of “Reporting Entity”</HD>
                    <P>
                        The Commission proposes to remove the term “reporting entity” from part 49. The Commission believes that “reporting entity” is no longer necessary with the proposed addition of the defined term for “reporting counterparty,” because reporting counterparties are also reporting entities under the current definition.
                        <SU>37</SU>
                        <FTREF/>
                         SEFs and DCMs are the only entities that may have the responsibility to report data that are not included in the proposed definition of “reporting counterparty.” The Commission notes that this proposed rule would retain most requirements related to reporting entities, but would update the terminology used to describe the requirements. As a result, most obligations for reporting entities would still exist under the proposed amendments.
                    </P>
                    <FTNT>
                        <P>
                            <SU>37</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.2(a)(12) (defining “reporting entity” as those entities that are required to report swap data to a registered swap data repository which includes derivatives clearing organizations, swap dealers, major swap participants and certain non-swap dealer/non-major swap participant counterparties.).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">x. Removal of “Registered Swap Data Repository”</HD>
                    <P>
                        The Commission proposes to remove the term “registered swap data repository” from part 49. The Commission believes the term “registered swap data repository” is not needed in part 49 because the defined term “swap data repository” already exists in § 1.3.
                        <SU>38</SU>
                        <FTREF/>
                         The definition of “swap data repository” in § 1.3 is identical to the definition contained in section 1a(48) of the CEA.
                        <SU>39</SU>
                        <FTREF/>
                         This definition of 
                        <PRTPAGE P="21048"/>
                        “swap data repository” therefore already applies, and would continue to apply, to part 49 and all other Commission regulations and, when combined with § 49.1,
                        <SU>40</SU>
                        <FTREF/>
                         removes the need for a separate defined term for “registered swap data repository.” The inclusion of the word “registered” in “registered swap data repository” and the definition of the term 
                        <SU>41</SU>
                        <FTREF/>
                         also creates unnecessary confusion as to when the requirements of part 49 apply to entities that are in the process of registering as SDRs or are provisionally registered as SDRs under the requirements of § 49.3(b).
                        <SU>42</SU>
                        <FTREF/>
                         Finally, the removal of the term “registered swap data repository” would decrease inconsistency in terms within part 49 and would also increase consistency between part 49 and other Commission regulations, which overwhelmingly use the term “swap data repository.” The Commission emphasizes that removing the defined term “registered swap data repository” is a non-substantive amendment that would not in any way modify the requirements applicable to current or future SDRs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>38</SU>
                             
                            <E T="03">See</E>
                             17 CFR 1.3 (defining “swap data repository” as “any person that collects and maintains information or records with respect to transactions or positions in, or the terms and conditions of, swaps entered into by third parties for the purpose of providing a centralized recordkeeping facility for swaps.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>39</SU>
                             
                            <E T="03">See</E>
                             7 U.S.C. 1a(48) (“The term `swap data repository' means any person that collects and maintains information or records with respect to 
                            <PRTPAGE/>
                            transactions or positions in, or the terms and conditions of, swaps entered into by third parties for the purpose of providing a centralized recordkeeping facility for swaps.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>40</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.1 (“The provisions of this part apply to any swap data repository as defined under Section 1a(48) of the [CEA] which is registered or is required to register as such with the Commission pursuant to Section 21(a) of the [CEA].”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>41</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.2(a)(11) (“The term `
                            <E T="03">registered swap data repository</E>
                            ' means a swap data repository that is registered under Section 21 of the [CEA].”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>42</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.3(b) (creating standards for granting provisional registration to an SDR).
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of the proposed changes to § 49.2. The Commission also invites specific comment on the following:
                    </P>
                    <P>(1) Are there any proposed amendments to definitions in existing regulations in part 49 that are unclear or inaccurate?</P>
                    <HD SOURCE="HD2">B. § 49.3—Procedures for Registration</HD>
                    <P>
                        Section 49.3 of the Commission's regulations establishes procedural and substantive requirements for SDR registration. In relevant part, § 49.3 requires persons seeking SDR registration to file an application for registration on Form SDR 
                        <SU>43</SU>
                        <FTREF/>
                         and to amend it periodically.
                        <SU>44</SU>
                        <FTREF/>
                         Specifically, current § 49.3(a)(5) requires that if any information in Form SDR or any amendment becomes inaccurate for any reason, whether before or after the registration application has been granted, the SDR shall promptly file an amendment on Form SDR updating such information. In addition, § 49.3(a)(5) requires the SDR to submit an annual amendment to Form SDR within sixty days after the end of the SDR's fiscal year.
                    </P>
                    <FTNT>
                        <P>
                            <SU>43</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.3(a)(1).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>44</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.3(a)(5).
                        </P>
                    </FTNT>
                    <P>The Commission is proposing to amend § 49.3(a)(5) to remove the requirement for SDRs to: (i) File an annual amendment to Form SDR; and (ii) amend Form SDR after the registration application has been granted pursuant to § 49.3(a). Accordingly, as proposed, § 49.3(a)(5) would simply require an SDR to amend Form SDR to correct inaccuracies until its application for registration has been granted.</P>
                    <P>
                        The Commission no longer believes that the requirement to amend Form SDR after registration is needed because the SDRs registered under § 49.3(a) will have demonstrated the ability to meet initial registration and compliance requirements in order to receive registration and the registered SDRs will still submit changes to many of the items in Form SDR as rule filings under part 40.
                        <SU>45</SU>
                        <FTREF/>
                         The Commission is also proposing new § 49.29, which would permit the Commission to request that SDRs produce information demonstrating compliance with the Commission's regulations, as discussed further in section II.T. The Commission does, however, believe that updates to Form SDR are still necessary prior to the granting of registration under § 49.3(a), because the application would still be active and the applicant would still need to demonstrate the ability to meet initial registration and compliance requirements.
                    </P>
                    <FTNT>
                        <P>
                            <SU>45</SU>
                             
                            <E T="03">See</E>
                             17 CFR 40.1, 40.5, and 40.6 (containing the filing and review provisions applicable to rules under the Commission's regulations).
                        </P>
                    </FTNT>
                    <P>
                        Consistent with the above proposed amendments, the Commission is also proposing to amend Form SDR to remove the references to annual amendments and amendments after SDR registration.
                        <SU>46</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>46</SU>
                             The Commission is proposing various non-substantive amendments to Form SDR. These amendments include making terminology consistent throughout Form SDR, fixing incorrect references and misspellings, and fixing grammatical and style errors.
                        </P>
                    </FTNT>
                    <P>As discussed below in section II.O, current § 49.22(f)(2) requires that the annual compliance report be provided to the Commission concurrently with the filing of the annual amendment to Form SDR that must be submitted to the Commission pursuant to § 49.3(a)(5) of this part. The Commission is proposing removing the reference to § 49.3(a)(5) from § 49.22(f)(2), to reflect the removal of the annual amendment requirement from § 49.3(a)(5).</P>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of the proposed changes to § 49.3(a)(5).
                    </P>
                    <HD SOURCE="HD2">C. § 49.5—Equity Interest Transfers</HD>
                    <P>The Commission is proposing to amend § 49.5 to streamline the requirements for equity interest transfers for SDRs. The Commission believes that the amendments to § 49.5 simplify the notification and timing requirements associated with transfers of equity interest for SDRs.</P>
                    <HD SOURCE="HD3">1. Notification of Intended Equity Interest Transfer—Proposed § 49.5(a)</HD>
                    <P>Current § 49.5(a) establishes the requirement for SDRs to provide the Commission an equity transfer notification. Specifically, current § 49.5(a) requires that: (i) Upon entering into any agreement that could result in an equity interest transfer of ten percent or more in the SDR, the SDR shall file a notification with the Secretary of the Commission in the manner specified by the Secretary, no later than the business day following the date on which the SDR enters into a firm obligation to transfer the equity interest; and (ii) that the SDR amend any information that is no longer accurate on Form SDR consistent with the procedures set forth in § 49.3.</P>
                    <P>Proposed § 49.5 would revise current § 49.5(a) in several respects. First, proposed § 49.5 would make clear that the proposed rule would apply to both the direct and indirect transfers of ten percent or more of the equity interest in the SDR. The Commission believes that including both direct and indirect transfers of equity ownership in proposed § 49.5 is necessary for the Commission to properly oversee SDRs and to address any compliance concerns that may arise from the indirect transfer of equity interest in an SDR through transactions involving an SDR's direct or indirect parent company, but not the SDR itself.</P>
                    <P>
                        Second, proposed § 49.5 would require that the SDR file the equity transfer notification at the earliest possible time but no later than the open of business ten business days following the date upon which a firm obligation is made to transfer, directly or indirectly, ten percent or more of the equity interest in the SDR. The Commission believes SDRs may need additional time to file the necessary documents, and ten business days would provide greater flexibility to SDRs without sacrificing the 
                        <PRTPAGE P="21049"/>
                        information the Commission needs to conduct effective oversight of SDRs.
                    </P>
                    <P>
                        Third, proposed § 49.5 would specify that the equity transfer notification be filed electronically with the Secretary of the Commission and the Director of the Division of Market Oversight (“DMO”) via email. The Commission is also proposing to remove the requirement to amend information that is no longer accurate on Form SDR due to the equity interest transfer because the requirement is duplicative in light of the requirements of both current and proposed § 49.3(a)(5).
                        <SU>47</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>47</SU>
                             Proposed § 49.5(a) would continue to apply the requirement to update information in Form SDR that is no longer accurate due to an equity interest transfer to an SDR whose application for registration has not been granted under § 49.3(a).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Documentation Requirements—Proposed § 49.5(b)</HD>
                    <P>Current § 49.5(b) sets forth the documentation requirements for the equity transfer notice. Current § 49.5(b) requires that: (i) The notification include any relevant agreements, corporate documents, charts outlining new ownership or corporate or organizational structure, a brief description of the purpose and any impact of the transfer, and a representation from the SDR that it meets all of the requirements of section 21 of the Act and Commission regulations; (ii) the SDR keep the Commission apprised of the projected date that the transaction will be consummated, and provide the Commission any new agreements or modifications to the original agreements filed pursuant to § 49.5; and (iii) the SDR notify the Commission of the consummation of the transaction on the day it occurs.</P>
                    <P>The Commission is proposing to simplify current § 49.5(b) and instead simply provide that the Commission may, upon receiving an equity transfer notification from an SDR, request that the SDR provide supporting documentation for the transaction. The Commission believes that reserving the authority to request supporting documentation rather than compelling specific production would satisfy the Commission's need for information without placing unnecessary burdens on SDRs.</P>
                    <HD SOURCE="HD3">3. Notification of Completed Equity Interest Transfer—Proposed § 49.5(c)</HD>
                    <P>Current § 49.5(c) requires that, upon the transfer, the SDR file with the Secretary of the Commission a certification that the registered SDR meets all of the requirements of section 21 of the Act and Commission regulations, and state whether changes to any aspects of the SDR's operations were made as a result of such change in ownership, with a description of any such change. The certification may rely on and be supported by reference to an SDR registration application or prior filings made pursuant to a rule submission requirement, along with any necessary new filings, including material updates of prior submissions. The certification must be filed within two business days of the date on which the equity interest was acquired.</P>
                    <P>Proposed § 49.5(c) would instead require that upon the transfer of the equity interest, whether directly or indirectly, the SDR shall file electronically with the Secretary of the Commission and DMO a certification that the SDR meets all of the requirements of section 21 of the Act and Commission regulations, no later than two business days following the date on which the equity interest of ten percent or more was acquired. The Commission believes proposed § 49.5(a) and (c) would provide the Commission with the pertinent information it needs to assess the impact of an equity interest transfer on the SDR's operations.</P>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of the proposed changes to § 49.5.
                    </P>
                    <HD SOURCE="HD2">D. § 49.6—Request for Transfer of Registration</HD>
                    <P>The Commission is proposing amendments to streamline the requirements for the transferring of SDR registration to a successor entity in § 49.6. As part of these amendments, the Commission is proposing to retitle the section “Request for transfer of registration,” to more accurately reflect the subject of the regulation.</P>
                    <P>Proposed § 49.6(a) would require that an SDR seeking to transfer its registration from its legal entity as a result of a corporate change that creates a new legal entity file a request for approval to transfer such registration with the Secretary of the Commission in the form and manner specified by the Commission. Examples of such corporate changes could include, but are not limited to, re-organizations, mergers, acquisitions, bankruptcy, or other similar events that result in the creation of a new legal entity for the SDR.</P>
                    <P>Proposed § 49.6(b) would specify that an SDR file a request for transfer of registration as soon as practicable prior to the anticipated corporate change.</P>
                    <P>Proposed § 49.6(c) would set forth the information that must be included in the request for transfer of registration, including the underlying documentation that governs the corporate change, governance documents, and representations by the transferee entity, among other information. Proposed § 49.6(d) would specify that upon review of a request for transfer of registration, the Commission, as soon as practicable, shall issue an order either approving or denying the request for transfer of registration.</P>
                    <P>Current § 49.6(a) requires that in the event of a corporate transaction that creates a new entity, an SDR must request a transfer of its registration, rules, and other matters no later than 30 days after the succession. Current § 49.6(a) also specifies that the registration shall be deemed to remain effective as the registration of the successor if the successor, within 30 days after such succession, files a Form SDR application for registration, and the predecessor files a Form SDR request for vacation, provided, however, that the registration of the predecessor SDR shall cease to be effective 90 days after the Form SDR registration application is filed by the successor SDR.</P>
                    <P>Current § 49.6(b) requires that if the succession is based solely on a change in the predecessor's date or state of incorporation, form of organization, or composition of a partnership, the successor may, within 30 days after the succession, amend the registration of the predecessor SDR on Form SDR to reflect these changes. The amendment shall be an application for registration filed by the predecessor and adopted by the successor.</P>
                    <P>The Commission believes that the amendments to § 49.6 would simplify the process for requesting a transfer of SDR registration. The Commission believes the requirement, timing, content of requests, and format of a Commission determination in proposed § 49.6(a), (b), (c), and (d) respectively, would achieve the Commission's information needs when an SDR seeks to transfer registration. These requirements would streamline the requirements for SDRs by setting forth a clear process for transfer that focuses on informing the Commission of changes relevant to the Commission in carrying out its oversight responsibilities, as opposed to requiring SDRs to file new Forms SDR, which would likely duplicate most of the transferor's current Form SDR.</P>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of the proposed changes to § 49.6.
                        <PRTPAGE P="21050"/>
                    </P>
                    <HD SOURCE="HD2">E. § 49.9—Open Swaps Reports Provided to the Commission</HD>
                    <P>
                        The Commission is proposing to replace current § 49.9 with requirements for SDRs to provide open swaps reports to the Commission.
                        <SU>48</SU>
                        <FTREF/>
                         The Commission proposes renaming § 49.9 “Open swaps reports provided to the Commission” to reflect this change.
                    </P>
                    <FTNT>
                        <P>
                            <SU>48</SU>
                             As discussed above in section II.A, the Commission is proposing to define an open swap as an executed swap transaction that has not reached maturity or the final contractual settlement date, and has not been exercised, closed out, or terminated.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.9(a) would require SDRs to provide the Commission with open swaps reports that contain an accurate reflection of the swap data for every swap data field required to be reported under part 45 for every open swap maintained by the SDR, organized by the unique identifier created pursuant to § 45.5 of the Commission's regulations associated with each open swap,
                        <SU>49</SU>
                        <FTREF/>
                         as of the time the SDR compiles the open swaps report.
                    </P>
                    <FTNT>
                        <P>
                            <SU>49</SU>
                             Proposed § 49.11 would also require SDRs to distribute open swaps reports to reporting counterparties. While a distinct report and separate requirement from proposed § 49.9, the Commission expects that the swap data contained in the open swaps reports provided to the Commission under proposed § 49.9 and the swap data provided to reporting counterparties under proposed § 49.11 would be identical, except for any data that is required to be kept confidential, if both reports reflect data as of the same moment. 
                            <E T="03">See</E>
                             section II.G below.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.9(b) would require SDRs to transmit all open swaps reports to the Commission as instructed by the Commission, and notes that such instructions may include, but would not be limited to, the method, timing, and frequency of transmission, as well as the format of the swap data to be transmitted.
                        <SU>50</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>50</SU>
                             As discussed below in section II.V, proposed § 49.31 would delegate the Commission's authority in proposed § 49.9, including the authority to create instructions for transmitting open swaps reports to the Commission, to the Director of DMO.
                        </P>
                    </FTNT>
                    <P>
                        Current § 49.9 lists and briefly summarizes the duties of SDRs. Current § 49.9 does not contain any unique regulatory requirements, but instead references where the duties are found in other sections of part 49.
                        <SU>51</SU>
                        <FTREF/>
                         The Commission believes that current § 49.9 is superfluous because all of the SDR duties listed in § 49.9 are also contained, in much greater detail, in the other sections of part 49. The Commission notes that removing current § 49.9 would be a non-substantive change that would not affect the requirements for SDRs found in the other sections of part 49, including the sections currently referenced in § 49.9.
                    </P>
                    <FTNT>
                        <P>
                            <SU>51</SU>
                             As discussed below in section II.Q, the Commission is proposing conforming amendments to § 49.25 to remove references to amended § 49.9.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that regularly receiving accurate and up-to-date information on the open swaps maintained by each SDR is necessary for the Commission to perform its regulatory functions. While the specific requirements in proposed § 49.9 are new to part 49, SDRs currently send open swaps reports to the Commission on a regular basis. The Commission currently uses open swaps reports to produce a weekly swaps report that is made available to the public 
                        <SU>52</SU>
                        <FTREF/>
                         and for entity-netted notional calculations.
                        <SU>53</SU>
                        <FTREF/>
                         The Commission also uses open swaps to perform market risk and position calculations, and for additional market research projects.
                    </P>
                    <FTNT>
                        <P>
                            <SU>52</SU>
                             The Commission's various public reports, including the weekly swaps reports, are 
                            <E T="03">available at http://www.cftc.gov/MarketReports/index.htm.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>53</SU>
                             
                            <E T="03">See</E>
                             “Introducing ENNs: A Measure of the Size of Interest Rate Swaps Markets,” Jan. 2018, 
                            <E T="03">available at https://www.cftc.gov/sites/default/files/idc/groups/public/@economicanalysis/documents/file/oce_enns0118.pdf.</E>
                        </P>
                    </FTNT>
                    <P>SDRs currently provide open swaps reports that use different calculation approaches and different formats. These variations among SDRs reduce the Commission's ability to effectively use the swap data. The Commission notes that the proposed regulations would standardize a type of report the SDRs already create for the Commission. The Commission believes that providing standards for how the swap data in open swaps reports should be provided to the Commission would help remedy issues the Commission faces in trying to reconcile open swaps reports across the SDRs.</P>
                    <P>
                        The Commission notes that it would have the ability to instruct SDRs as to all aspects of transmitting the open swaps reports to the Commission under proposed § 49.9. These instructions may include the method of transmission (
                        <E T="03">e.g.,</E>
                         file types and methods used for transmission), the timing of transmission, the frequency of transmission, and the formatting of the swap data included in the reports. The Commission believes that retaining the flexibility to determine how SDRs would provide open swaps reports to the Commission and the ability to modify the requirements over time as needed would allow the Commission to use the information in the reports to fulfill its regulatory responsibilities while not requiring unnecessary effort on the part of the SDRs.
                    </P>
                    <P>The Commission intends to work with the SDRs before creating or modifying any instructions pursuant to proposed § 49.9 and would provide a reasonable amount of time for SDRs to adjust their systems before any instructions take effect. The Commission notes that it currently works with SDRs to implement changes to open swaps reports, with SDRs being given time to update their systems as needed. The Commission anticipates using a similar process when working with the SDRs on the new requirements for open swaps reports.</P>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of the proposed changes to § 49.9.
                    </P>
                    <HD SOURCE="HD2">F. § 49.10—Acceptance of Data</HD>
                    <P>
                        The Commission proposes amending § 49.10 to add a new paragraph (e) to address correction of errors and omissions in SDR data. SDRs are currently required to publicly disseminate cancellations and corrections to swap transaction and pricing data as soon as technologically practicable after receipt of any cancellation or correction,
                        <SU>54</SU>
                        <FTREF/>
                         and transmit corrections to errors and omissions in swap data previously transmitted to the Commission in the same format as the erroneous or omitted swap data was originally transmitted.
                        <SU>55</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>54</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.3(e)(1), (3), and (4) (requiring an SDR to publicly disseminate corrections and cancellations to data and containing requirements for cancellation and correction).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>55</SU>
                             
                            <E T="03">See</E>
                             17 CFR 45.14(c) (requiring corrections to be transmitted to the Commission in the same format as the data was originally transmitted, unless otherwise approved).
                        </P>
                    </FTNT>
                    <P>
                        Swap counterparties, SEFs, and DCMs currently have obligations to report errors and omissions to the reporting counterparty, SEF, DCM, or SDR, depending on whether they are reporting swap transaction and pricing data or swap data.
                        <SU>56</SU>
                        <FTREF/>
                         The Commission is proposing to move the obligations for SDRs in correcting errors and omissions to § 49.10(e), to place all obligations for SDRs in part 49.
                        <SU>57</SU>
                        <FTREF/>
                         The Commission believes proposed § 49.10(e) is consistent with the SDRs' duty to correct errors and omissions that already exists in the CEA and current Commission regulations.
                    </P>
                    <FTNT>
                        <P>
                            <SU>56</SU>
                             
                            <E T="03">See</E>
                             § 43.3(e) for swap transaction and pricing data, discussed below in section IV.A, and § 45.14 for swap data, discussed below in section III.B. The obligations for swap counterparties, SEFs, and DCMs to report errors and omissions in swap transaction and pricing data and swap data would remain in their current sections.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>57</SU>
                             Parts 43 and 45, while containing provisions related to SDR acceptance and dissemination of data, concentrate on the reporting and dissemination of data by all market participants, while part 49 contains provisions that govern the registration and operations of SDRs more generally.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.10(e) would set forth the general requirement that an SDR correct errors and omissions in SDR 
                        <PRTPAGE P="21051"/>
                        data that was previously reported to the SDR or was not previously reported to the SDR as required,
                        <SU>58</SU>
                        <FTREF/>
                         regardless of the state of the swap that is the subject of the SDR data.
                    </P>
                    <FTNT>
                        <P>
                            <SU>58</SU>
                             The Commission notes that the failure to perform the initial data reporting as required under parts 43, 45, or 46 is an “omission” for the purposes of those parts and proposed § 49.10. The SDR would be required to correct the omission pursuant to proposed § 49.10, just as it would be required to correct any other error or omission, regardless of the state of the swap, and disseminate the corrected data as required in proposed § 49.10.
                        </P>
                    </FTNT>
                    <P>Proposed § 49.10(e)(1)-(4) would set forth the specific requirements SDRs would need to meet to fulfill the general requirement in § 49.10(e). Proposed § 49.10(e)(1) would require an SDR to accept corrections for errors and omissions reported to the SDR pursuant to parts 43, 45, and 46.</P>
                    <P>Proposed § 49.10(e)(2) would require each SDR to correct the reported errors and omissions as soon as technologically practicable after the SDR receives a report of errors or omissions.</P>
                    <P>
                        Proposed § 49.10(e)(3) would require an SDR to disseminate corrected SDR data to the public and the Commission, as applicable, as soon as technologically practicable after the SDR corrects the SDR data. Proposed § 49.10(e)(4) would require SDRs to establish, maintain, and enforce policies and procedures designed for the SDR to fulfill its responsibilities under § 49.10(e)(1)-(3).
                        <SU>59</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>59</SU>
                             The Commission notes that the policies and procedures for reporting corrections to the SDR created pursuant to § 49.10(e) would be subject to disclosure to SEFs, DCMs, and reporting counterparties under proposed § 49.26(j). 
                            <E T="03">See</E>
                             section II.R below. The Commission is aware of previous instances where market participants were not provided with SDR policies and procedures related to the reporting or correction of data and were unaware of the SDR's requirements, which unnecessarily interfered with the reporting and correction processes. The requirements of proposed § 49.10(e)(4) and proposed § 49.26(j) are intended to prevent a similar situation from occurring in the context of data corrections.
                        </P>
                    </FTNT>
                    <P>
                        As noted above, new § 49.10(e) is designed to complement the correction provisions of other parts of the Commission's swap reporting regulations that apply to the entities reporting errors and omissions to SDRs, including proposed § 45.14(b), to ensure that errors and omissions in SDR data are corrected and disseminated as soon as possible.
                        <SU>60</SU>
                        <FTREF/>
                         The Commission also notes that SDRs currently have the duty to correct all SDR data previously reported, and all SDR data that was erroneously not reported as required, and to properly disseminate the corrections as required, including making the corrected SDR data available to the Commission as instructed,
                        <SU>61</SU>
                        <FTREF/>
                         which will continue pursuant to proposed § 49.17.
                        <SU>62</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>60</SU>
                             
                            <E T="03">See</E>
                             section III.B below.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>61</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.3(e) (correction and dissemination requirements for swap transaction and pricing data); 17 CFR 45.14 (correction and dissemination requirements for swap data); 
                            <E T="03">see also</E>
                             17 CFR 49.13(a) (requiring SDRs to transmit all swap data requested by the Commission to the Commission in an electronic file in a format acceptable to the Commission.).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>62</SU>
                             
                            <E T="03">See</E>
                             section II.L below. As discussed in that section, SDRs are currently required to provide the Commission with direct electronic access to SDR data, including scheduled data transfers to the Commission.
                        </P>
                    </FTNT>
                    <P>
                        Finally, the Commission notes that, as specified in § 49.10(e), the requirements of new § 49.10(e) would apply regardless of the state of the swap, meaning SDRs would have to correct and disseminate SDR data for swaps that have matured or were otherwise terminated and are no longer open swaps. The Commission believes this requirement is necessary for SDRs to continue to maintain and disseminate SDR data that accurately reflects market activity to the public 
                        <SU>63</SU>
                        <FTREF/>
                         and regulators. Further, SDRs currently do regularly make and disseminate corrections to previously-reported SDR data and SDR data that was not initially reported as required, including SDR data for previously matured or terminated swaps.
                    </P>
                    <FTNT>
                        <P>
                            <SU>63</SU>
                             The Commission understands that market participants use the real-time swap transaction and pricing data disseminated by SDRs pursuant to part 43 for a variety of purposes, including modeling of the swaps markets that impacts their decisions related to transacting in swaps.
                        </P>
                    </FTNT>
                    <P>In general, the Commission believes that specifying SDRs' responsibilities to receive corrections to SDR data from market participants, make the corrections to the SDR data, and to provide the corrected SDR data to the public and the Commission, as applicable, would further the Commission's goal of having accurate and complete SDR data available to both the Commission and the public by clearly delineating the SDRs' responsibilities in the process.</P>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of proposed § 49.10(e).
                    </P>
                    <HD SOURCE="HD2">G. § 49.11—Verification of Swap Data Accuracy</HD>
                    <P>
                        The Commission proposes to revise the current requirements of § 49.11 that set forth SDRs' responsibilities to confirm the accuracy and completeness of swap data reported to SDRs. At the same time, the Commission is proposing to revise the requirements of § 45.14 for reporting counterparties, SEFs, and DCMs to verify swap data and correct errors in swap data.
                        <SU>64</SU>
                        <FTREF/>
                         The Commission believes that revised § 49.11 and § 45.14 would provide SDRs, reporting counterparties, SEFs, and DCMs with a clear understanding of their respective responsibilities for verifying swap data.
                    </P>
                    <FTNT>
                        <P>
                            <SU>64</SU>
                             
                            <E T="03">See</E>
                             section III.B below.
                        </P>
                    </FTNT>
                    <P>
                        The Commission is proposing to change the name of § 49.11 to “Verification of swap data accuracy” from “Confirmation of data accuracy” in order to reduce the number of differing uses of the word “confirmation” within the Commission's regulations. The Commission uses different tenses of the word “verify” 
                        <SU>65</SU>
                        <FTREF/>
                         for the proposed requirement for the same reason.
                    </P>
                    <FTNT>
                        <P>
                            <SU>65</SU>
                             The Commission recognizes that CEA section 21(c)(2) uses the term “confirm,” but for the reasons stated above believes “verification” and “verify” are necessary to avoid confusion.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">1. General Requirement To Verify Swap Data Accuracy—Proposed § 49.11(a)</HD>
                    <P>
                        The Commission proposes to amend § 49.11(a) to include a general requirement that SDRs verify the accuracy and completeness of swap data that the SDRs receive from SEFs, DCMs, and reporting counterparties, or third-party service providers acting on their behalf.
                        <SU>66</SU>
                        <FTREF/>
                         Revised § 49.11(a) would also require each SDR to establish, maintain, and enforce policies and procedures reasonably designed to verify the accuracy and completeness of swap data that it receives from SEFs, DCMs, reporting counterparties, or third-party service providers.
                        <SU>67</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>66</SU>
                             The Commission notes that an SDR may receive swap data from any SEF, DCM, or reporting counterparty, as defined in proposed § 49.2, but that the SDR would, under the proposed regulations, verify the accuracy and completeness of swap data with the reporting counterparty for a given swap, as discussed in this section. Likewise, under proposed § 45.14(a), the reporting counterparty would be required to verify the accuracy and completeness of swap data as required by that section.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>67</SU>
                             SDRs would be required make their policies and procedures created pursuant to proposed § 49.11(a) available to their users and potential users under the requirements of proposed § 49.26(j).
                        </P>
                    </FTNT>
                    <P>
                        As noted above, proposed § 45.14(a) contains companion requirements to proposed § 49.11(a) that would require reporting counterparties to verify swap data with SDRs and to conform to the relevant SDR's verification policies and procedures in fulfilling their verification responsibilities.
                        <SU>68</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>68</SU>
                             
                            <E T="03">See</E>
                             section III.B below.
                        </P>
                    </FTNT>
                    <P>
                        Section 21(c)(2) of the CEA requires SDRs to confirm with both counterparties to the swap the accuracy of the data that was submitted.
                        <SU>69</SU>
                        <FTREF/>
                         The Commission implemented section 21(c)(2) through adopting current § 49.11. Current § 49.11(a) requires that SDRs establish and adopt policies and procedures to ensure the accuracy of 
                        <PRTPAGE P="21052"/>
                        swap data and other regulatory information that is reported to an SDR. Current § 49.11(b) generally requires an SDR to confirm the accuracy and completeness of all swap data submitted pursuant to part 45. The Commission provided an exception to the requirement that SDRs confirm with both counterparties to the swap the accuracy of the data that was submitted in § 49.11(b)(1)(ii) for swap creation data and § 49.11(b)(2)(ii) for swap continuation data when swap data is received from a SEF, DCM, derivatives clearing organization (“DCO”), or from a third-party service provider acting on behalf of the swap counterparty, under certain conditions.
                        <SU>70</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>69</SU>
                             7 U.S.C. 24a(c)(2).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>70</SU>
                             In these cases, §§ 49.11(b)(1)(ii) and 49.11(b)(2)(ii) relax the general requirement that the SDR affirmatively notify both counterparties directly if: (1) The SDR has formed a reasonable belief that the swap data is accurate; (2) the swap data or accompanying information reflect that both counterparties agreed to the swap data; and (3) the counterparties were provided with a 48-hour correction period.
                        </P>
                    </FTNT>
                    <P>
                        SDRs are required under current § 49.11(b)(1)(i) and § 49.11(b)(2)(i) to notify both counterparties to a swap when swap data is submitted directly via a swap counterparty, such as an SD, MSP, or non-SD/MSP counterparty, and not by a SEF, DCM, DCO, or a third-party service provider.
                        <SU>71</SU>
                        <FTREF/>
                         However, because counterparties do not currently have a corollary obligation to respond to the SDRs' notifications, SDRs have adopted rules based on the concept of negative affirmation: Reported swap data is presumed accurate and confirmed if a counterparty does not inform the SDR of errors or omissions or otherwise make modifications to a trade record for a certain period of time.
                        <SU>72</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>71</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.11(b).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>72</SU>
                             
                            <E T="03">See, e.g.,</E>
                             CME Rules 604.A and 604.B; DTCC Data Repository (U.S.) LLC Rule 3.3.3.3; and ICE Trade Vault Rules 4.6 and 4.7.
                        </P>
                    </FTNT>
                    <P>
                        When the Commission adopted current § 49.11, it did not believe that requiring an SDR to affirmatively communicate with both counterparties to a swap was necessary when the swap data was submitted to the SDR by a SEF, DCM, DCO, or third-party service provider.
                        <SU>73</SU>
                        <FTREF/>
                         However, based on the Commission's experience with swap data submitted by SEFs, DCMs, DCOs, and third-party service providers since the rule was adopted, the Commission believes that such swap data has not been consistently complete and accurate in some instances, and the swap data accuracy is not sufficient to justify the exception to the requirement that SDRs confirm the reported swap data's accuracy with swap counterparties. The current requirements have had a negative effect on swap data accuracy and consistency, which has hampered the Commission's ability to carry out its regulatory responsibilities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>73</SU>
                             
                            <E T="03">See</E>
                             Part 49 Adopting Release at 54547 (describing the requirements of § 49.11).
                        </P>
                    </FTNT>
                    <P>
                        Commission staff received many comments on confirmation requirements for swap data reported to SDRs in response to the Roadmap Request for Comment.
                        <SU>74</SU>
                        <FTREF/>
                         In general, the SDRs commented that they cannot meet their obligation to confirm data with both counterparties because non-reporting counterparties are not required to confirm data reported to the SDR under current regulations.
                        <SU>75</SU>
                        <FTREF/>
                         The SDRs also stated that they often have no way to contact non-reporting counterparties because non-reporting counterparties are not obligated to connect to the SDRs' services.
                        <SU>76</SU>
                        <FTREF/>
                         SDRs also commented that the obligation to confirm data accuracy should generally reside with the entities that are in the best position to know whether the reported data is accurate and complete (
                        <E T="03">i.e.,</E>
                         the parties to the swap, not the SDRs).
                        <SU>77</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>74</SU>
                             The following organizations submitted comments related to confirmation and reconciliation for data reported to SDRs: American Counsel of Life Insurers (“ACLI”); Commercial Energy Working Group (“CEWG”); Chatham Financial (“Chatham”); CME Group (“CME”); Coalition for Derivatives End-Users (“Coalition”); Depository Trust &amp; Clearing Corporation (“DTCC”); Eurex Clearing AG (“Eurex”); a joint comment letter from BSDR LLC, Chicago Mercantile Exchange Inc., and ICE Trade Vault (“Joint SDR”); Global Financial Markets Association (“GFMA”); ICE Trade Vault (“ICE”); International Energy Credit Association (“IECA”); a joint letter comment letter from International Swaps and Derivatives Association, Inc. and the Securities Industry and Financial Markets Association (“ISDA/SIFMA”); Japanese Bankers Association (“JBA”); Natural Gas Supply Association (“NGSA”); a joint comment letter from National Rural Electric Cooperative Association and American Public Power Association (“NRECA/APPA”); and Securities Industry and Financial Markets Association Asset Management Group (“SIFMA AMG”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>75</SU>
                             Joint SDR Letter at 5; ICE Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>76</SU>
                             Joint SDR Letter at 5; DTCC Letter at 3; ICE Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>77</SU>
                             Joint SDR Letter at 5 (listing CME and ICE as supporting this belief); CME Letter at 2; DTCC Letter at 3.
                        </P>
                    </FTNT>
                    <P>
                        As a result, many SDRs advocated for removing some or all SDR obligations from § 49.11 of the Commission's regulations.
                        <SU>78</SU>
                        <FTREF/>
                         The Joint SDR letter commented that the Commission should clearly define the obligations of counterparties to confirm the accuracy and completeness of reported data, including requiring non-reporting counterparties to on-board with every SDR and to follow the SDRs' processes and procedures, if the non-reporting counterparties have confirmation obligations.
                        <SU>79</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>78</SU>
                             Joint SDR Letter at 5; CME Letter at 2; ICE Letter at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>79</SU>
                             Joint SDR Letter at 5 (listing CME and ICE as providing this recommendation).
                        </P>
                    </FTNT>
                    <P>
                        Other commenters, including end-user groups, opposed confirmation requirements for non-reporting counterparties.
                        <SU>80</SU>
                        <FTREF/>
                         Chatham stated that non-reporting parties are rarely the cause of errors in the swap data and that reconciliation by reporting counterparties in conjunction with more robust validation of swap data would render reconciliation by non-reporting counterparties unnecessary.
                        <SU>81</SU>
                        <FTREF/>
                         CEWG advocated against any periodic reconciliation, and suggested that if reconciliation is required, it only be required for position data.
                        <SU>82</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>80</SU>
                             Coalition Letter at 4 (noting that end-users do not have the dedicated systems, personnel, or resources to confirm swap details with SDRs); IECA Letter at 2; NRECA/APPA Letter at 3; Chatham Letter at 3-4; JBA Letter at 1-2; NGSA Letter at 3; ISDA/SIFMA Letter at 6; ACLI Letter at 2-3; SIFMA AMG Letter at 1-2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>81</SU>
                             Chatham Letter at 3-4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>82</SU>
                             CEWG Letter at 3.
                        </P>
                    </FTNT>
                    <P>
                        The Commission's proposed revisions to § 49.11 and § 45.14(a) 
                        <SU>83</SU>
                        <FTREF/>
                         should provide more detail on the responsibilities of SDRs, working in conjunction with reporting counterparties, to verify the accuracy and completeness of swap data. As described in the discussions of proposed § 49.11(b)-(d) below, the Commission is proposing that SDRs only verify swap data with reporting counterparties because the Commission believes this would be the most practical approach to verification. The Commission understands that SDRs are not parties to swaps and are therefore unable to verify the accuracy and completeness of swap data without the assistance of a swap counterparty.
                    </P>
                    <FTNT>
                        <P>
                            <SU>83</SU>
                             
                            <E T="03">See</E>
                             section III.B.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes reporting counterparties are in the best position to verify swap data with SDRs. The CEA's swap reporting framework is based on reporting counterparties reporting swap data on behalf of non-reporting counterparties.
                        <SU>84</SU>
                        <FTREF/>
                         Because of the data reporting requirements for reporting counterparties, reporting counterparties are connected to SDRs for reporting, while non-reporting counterparties, especially those that are not SDs/MSPs, often lack such connections.
                        <SU>85</SU>
                        <FTREF/>
                         For 
                        <PRTPAGE P="21053"/>
                        entities that never serve as reporting counterparties, such a requirement would mean the expense of building, maintaining, and operating systems to connect to SDRs purely for the purposes of verifying swap data. The Commission believes this outcome would be inconsistent with the CEA's goal of placing swap data reporting responsibilities on reporting counterparties.
                    </P>
                    <FTNT>
                        <P>
                            <SU>84</SU>
                             As discussed in the Part 45 Adopting Release, in designating reporting counterparties to report on behalf of non-reporting counterparties, Congress made a policy choice to place lesser burdens on non-reporting counterparties. 
                            <E T="03">See</E>
                             77 FR 2136, 2166 (discussing the reporting counterparty hierarchy in CEA section 4r(a)(3)).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>85</SU>
                             The Commission notes that under current and proposed § 45.14(b), a non-reporting counterparty's correction responsibilities are limited to notifying 
                            <PRTPAGE/>
                            the reporting counterparty of the errors and omissions, as opposed to notifying the SDR. 
                            <E T="03">See</E>
                             17 CFR 45.14(b); section III.B below. Requiring non-reporting counterparties to verify swap data would be the only instance where a non-reporting counterparty has swap data responsibilities with SDRs outside of corrections.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Distribution of Open Swaps Reports—Proposed § 49.11(b)</HD>
                    <P>
                        To meet the requirement to verify swap data accuracy in proposed § 49.11(a), proposed § 49.11(b) would require an SDR to distribute to each reporting counterparty on a regular basis an open swaps report detailing the swap data maintained by the SDR for all open swaps.
                        <SU>86</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>86</SU>
                             Under proposed § 45.14(a), a reporting counterparty would then compare its books and records related to each swap for which it is the reporting counterparty against the report to determine if the swap data the SDR maintains is complete and accurate. 
                            <E T="03">See</E>
                             section III.B below.
                        </P>
                    </FTNT>
                    <P>
                        The Commission notes that the open swaps report would contain the same type of information that would be provided to the Commission in an open swaps report under proposed § 49.9, as of the time the SDR compiles the open swaps report, but limited to the open swaps for which the recipient of the open swaps report is the reporting counterparty.
                        <SU>87</SU>
                        <FTREF/>
                         The Commission notes that an SDR would not be required to provide an open swaps report to an entity that does not have any open swaps at the time the SDR compiles a particular open swaps report, even if the entity has been the reporting counterparty for swaps previously maintained by the SDR. For example, if all of the swaps for which an entity was the reporting counterparty were terminated before the SDR begins compiling an open swaps report, the SDR need not provide an open swaps report to that reporting counterparty. The SDR would need to provide subsequent open swaps reports to the entity if the entity becomes the reporting counterparty for any swaps that are open as of the time of a subsequent regular compiling of open swaps reports.
                    </P>
                    <FTNT>
                        <P>
                            <SU>87</SU>
                             The Commission anticipates that, because the SDR would be required to regularly distribute the open swaps report on the same day during the verification period for each individual reporting counterparty under proposed § 49.11(b)(1)-(2), the SDR would begin to compile the open swaps report at the same time before each distribution.
                        </P>
                    </FTNT>
                    <P>The Commission also notes that it is not proposing to prescribe how an SDR must distribute the open swaps reports to reporting counterparties. Commission staff understands some SDRs “push” or actively send information to reporting counterparties, while other SDRs typically have customers “pull” information by having those customers connect to SDR systems to retrieve the information. The Commission would not have a preference between these two approaches, provided that the SDR has instructed its customers on when and how the SDR would distribute the open swaps reports in the SDR's swap data verification policies and procedures that it makes available to market participants pursuant to proposed § 49.26(j), such that the SDR's customers are able to effectively access and utilize the open swaps reports.</P>
                    <P>The Commission also notes that it does not have a preference as to the communication methods, such as file types and data languages, that the SDRs and reporting counterparties use when distributing the open swaps reports, as long as the communication methods are made clear in the SDR's swap data verification policies and procedures and the entities can effectively communicate regarding the contents of each open swaps report, including accounting for all necessary automated systems, mapping of data fields, and potential data translation between data languages. The Commission would expect SDRs and reporting counterparties to work together to devise efficient and effective methods for successfully distributing the open swaps reports, with particular attention paid to creating a distribution system that minimizes the burden of distribution for non-SD/MSP/DCO reporting counterparties. Reporting counterparties are already connected to SDRs to fulfill their reporting responsibilities under part 45 and therefore the Commission anticipates that SDRs and reporting counterparties would be able to communicate easily, potentially through existing infrastructure for reporting swap data.</P>
                    <HD SOURCE="HD3">3. Content of Open Swaps Reports—Proposed § 49.11(b)(1)</HD>
                    <P>Proposed § 49.11(b)(1) would require an SDR to distribute an open swaps report that contains an accurate reflection of the swap data for every swap data field required to be reported for swaps pursuant to part 45 for every open swap maintained by the SDR for which the recipient of the report is the reporting counterparty, organized by the unique identifier created pursuant to § 45.5 of the Commission's regulations associated with every open swap, as of the time the SDR compiles the open swaps report.</P>
                    <P>
                        The Commission notes that the swap data to be included in the open swaps report would need to include every data field required to be reported for swaps under part 45, unless access to a particular data field is prohibited by other Commission regulations.
                        <SU>88</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>88</SU>
                             The Commission notes that the confidentiality requirements, particularly § 49.17(f), would apply to the open swaps reports. Under § 49.17(f), for example, an SDR may not include the identity or legal entity identifier of the non-reporting counterparty to the swap (or the non-reporting counterparty's clearing member for the swap) if the swap was executed anonymously on a SEF or DCM and cleared in accordance with the Commission regulations referenced in § 49.17(f)(2). 
                            <E T="03">See</E>
                             17 CFR 49.17(f)(2) (providing the exception to the general prohibition on market participant access to swap data maintained by SDRs).
                        </P>
                    </FTNT>
                    <P>The Commission believes that having every reporting counterparty review the swap data and respond to the SDR as required in proposed § 45.14 would improve the quality of swap data by facilitating the discovery and correction of errors and omissions. Proposed § 49.11(b)(1) would facilitate this review by requiring the SDRs to provide the swap data for all of a reporting counterparty's open swaps on a regular basis. The Commission anticipates this process would be largely automated and would become more efficient over time as reporting counterparties and SDRs gain experience with verification.</P>
                    <P>
                        The Commission is not proposing specific requirements for the formatting of the open swaps report provided pursuant to proposed § 49.11(b)(1), but the Commission expects that the swap data included in the open swaps report would be identical to the swap data provided to the Commission pursuant to proposed § 49.9 in all instances where the two reports reflect swap data as of the same time, except for any data that is required to be kept confidential.
                        <SU>89</SU>
                        <FTREF/>
                         The Commission believes it is important that the reporting counterparty would be able to review the same swap data that is provided to the Commission as of the moment the SDR compiled the open swaps report, to help ensure data consistency.
                    </P>
                    <FTNT>
                        <P>
                            <SU>89</SU>
                             
                            <E T="03">See</E>
                             section II.E above (discussing the proposed requirements for providing open swaps reports to the Commission).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">4. Frequency of Open Swaps Reports for SD, MSP, and DCO Reporting Counterparties—Proposed § 49.11(b)(2)</HD>
                    <P>
                        Proposed § 49.11(b)(2) would require SDRs to distribute the open swaps reports to all SD/MSP/DCO reporting counterparties on a weekly basis, no 
                        <PRTPAGE P="21054"/>
                        later than 11:59 p.m. Eastern Time 
                        <SU>90</SU>
                        <FTREF/>
                         on the day of the week that the SDR chooses to regularly distribute the open swaps reports. The Commission notes that it is not prescribing the day that the SDR chooses to distribute the open swaps report, but would require that the SDR use the same day of the week for each distribution. The Commission would also require that the SDR distribute all of the open swaps reports to the relevant reporting counterparties on the same day. Distributing the open swaps reports irregularly may create the unnecessary risk of confusion and/or missed reports, and may lead to swap data not being properly verified. Regular distribution would also allow reporting counterparties to prepare for when they would be required to fulfill their verification responsibilities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>90</SU>
                             The Commission is specifying a time under proposed § 49.11 for consistency purposes. SDRs would need to account for the adjustments to Eastern Time that occur during the year in their verification policies and procedures and reporting counterparties would need to accommodate these adjustments in their verification practices.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that SDs, MSPs, and DCOs, as large, sophisticated Commission-registered entities that are accustomed to swap data regulatory compliance, and as the most likely entities to serve as reporting counterparties,
                        <SU>91</SU>
                        <FTREF/>
                         can efficiently verify swap data on a weekly basis. Further, as SDs, MSPs, and DCOs are the reporting counterparty for the overwhelming majority of swaps,
                        <SU>92</SU>
                        <FTREF/>
                         requiring these entities to review the swap data maintained for their open swaps on a weekly basis would ensure that the large majority of open swaps would be verified within a week of execution, which would also facilitate the prompt correction of any errors or omissions in the swap data for these swaps.
                    </P>
                    <FTNT>
                        <P>
                            <SU>91</SU>
                             Any swap involving at least one SD, MSP, or DCO as a counterparty will have a reporting counterparty that is a SD, MSP, or DCO. 
                            <E T="03">See</E>
                             17 CFR 45.8 (providing the requirements for determining which counterparty to a swap is the reporting counterparty).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>92</SU>
                             
                            <E T="03">See</E>
                             De Minimis Exception to the Swap Dealer Definition, 83 FR 56666, 56674 (Nov. 13, 2018) (stating that, in 2017, approximately 98 percent of swap transactions involved at least one registered SD).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">5. Frequency of Open Swaps Reports for Non-SD/MSP/DCO Reporting Counterparties—Proposed § 49.11(b)(3)</HD>
                    <P>Proposed § 49.11(b)(3) would require SDRs to distribute the open swaps reports to non-SD/MSP/DCO reporting counterparties on a monthly basis, no later than 11:59 p.m. Eastern Time on the day of the month that the SDR chooses to regularly distribute the open swaps reports. For the reasons discussed above with respect to proposed § 49.11(b)(2), the Commission is not prescribing the day of the month that the SDR chooses to distribute the open swaps reports, but does require that the SDR use the same day of the month for each distribution. The Commission is also proposing to require that the SDR distribute all of the open swaps reports to the relevant reporting counterparties on the same day.</P>
                    <P>
                        The Commission believes that monthly distribution would satisfy the Commission's need for accurate swap data. The Commission is aware that non-SD/MSP/DCO counterparties tend to be less active in the swaps markets with fewer resources to devote to regulatory compliance. The Commission understands that this is particularly true of swaps end-users that use swaps infrequently and are more likely to engage in swaps for hedging purposes. Non-SD/MSP/DCO counterparties are also the reporting counterparties for relatively few swaps; 
                        <SU>93</SU>
                        <FTREF/>
                         therefore, the Commission believes that there would not be a significant risk of errors associated with less frequent verification for these reporting counterparties.
                    </P>
                    <FTNT>
                        <P>
                            <SU>93</SU>
                             
                            <E T="03">See id.</E>
                             (finding that, during the examination period, 98 percent of swap transactions involved at least one SD/MSP counterparty).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">6. Receipt of Verification of Data Accuracy or Notice of Discrepancy—Proposed § 49.11(c)</HD>
                    <P>
                        Proposed § 49.11(c) would require SDRs to receive from each reporting counterparty to which it sends an open swaps report, in response to the open swaps report, either a verification of data accuracy indicating that the swap data contained in the open swaps report distributed pursuant to § 49.11(b) is accurate and complete or a notice of discrepancy indicating that the data contained in an open swaps report contains one or more discrepancies.
                        <SU>94</SU>
                        <FTREF/>
                         Proposed § 49.11(c) would also require SDRs to establish, maintain, and enforce policies and procedures reasonably designed for the SDR to successfully receive the verification of data accuracy or the notice of discrepancy.
                    </P>
                    <FTNT>
                        <P>
                            <SU>94</SU>
                             The Commission notes that an SDR receiving a notice of discrepancy should expect to—and be prepared to—receive corrections for the errors and omissions in the swap data close in time to when it receives the notice of discrepancy, due to the requirements of proposed § 45.14(b).
                        </P>
                    </FTNT>
                    <P>The Commission notes that an SDR would not fully satisfy the requirements of proposed § 49.11 until it receives the verification of data accuracy or notice of discrepancy. The Commission believes that proposed § 49.11(c) would help ensure that the reporting counterparty has received and reviewed the open swaps report, which would aid the data correction process and improve the quality of swap data. The Commission also believes that proof of compliance would assist the SDRs and the Commission with any necessary compliance reviews.</P>
                    <P>The requirement to establish, maintain, and enforce policies and procedures regarding this stage of verification would help ensure that the SDR is fully prepared to perform its verification duties and, because the policies and procedures would be made available to reporting counterparties pursuant to proposed § 49.26(j), would help ensure that the verification process is clear and efficient for reporting counterparties and SDRs. The Commission notes that it is not prescribing the methods for how SDRs fulfill their responsibilities under proposed § 49.11(c), but does expect that the SDRs would be reasonable in the requirements of their policies and would utilize methods that are as low-cost and efficient as possible. The Commission particularly encourages SDRs to be accommodating for non-SD/MSP/DCO reporting counterparties.</P>
                    <P>The Commission notes that proposed § 45.14 includes corresponding requirements for reporting counterparties to verify the accuracy and completeness of swap data in response to the open swaps reports and for reporting counterparties to follow an SDR's verification policies and procedures in fulfilling their verification responsibilities, including analyzing and responding to open swaps reports. These corresponding requirements would help ensure that reporting counterparties respond to the open swaps reports in a timely and efficient manner, such that SDRs can fulfill their responsibilities under proposed § 49.11(c).</P>
                    <P>
                        The Commission also clarifies that, given the separate proposed companion requirements for reporting counterparties, an SDR would not be responsible for failing to satisfy the requirements of § 49.11 in the instance where an SDR made a full, good-faith effort to comply with proposed § 49.11, and followed its policies and procedures created pursuant to proposed § 49.11 in doing so, but was prevented from fulfilling the requirements because of a reporting counterparty failing to meet its responsibilities to respond to the open swaps report as required under proposed § 45.14(a). In such a situation, the reporting counterparty would be held responsible for its failure to satisfy the requirements of proposed § 45.14.
                        <PRTPAGE P="21055"/>
                    </P>
                    <HD SOURCE="HD3">7. Amending Verification Policies and Procedures—Proposed § 49.11(d)</HD>
                    <P>
                        Proposed § 49.11(d) would require SDRs to comply with the requirements under part 40 of the Commission's regulations when adopting or amending their verification policies and procedures.
                        <SU>95</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>95</SU>
                             Verification policies and procedures would be considered “rules” for the purposes of part 40 requirements. 
                            <E T="03">See</E>
                             17 CFR 40.1, 40.5, and 40.6 (containing the filing and review provisions applicable to rules under the Commission's regulations).
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of proposed § 49.11. The Commission also invites specific comment on the following:
                    </P>
                    <P>(2) Is the Commission's proposed approach, which does not involve non-reporting counterparties in the verification process, an effective approach to verification? Why or why not? Are there additional benefits or costs to involving non-reporting counterparties in the verification process that have not been considered? Please be specific.</P>
                    <P>(3) Should the Commission be more prescriptive in how the SDRs must distribute the open swaps reports to reporting counterparties pursuant to proposed § 49.11(b)? If so, what should be the requirements included in the prescribed approach? Please be specific.</P>
                    <P>(4) Should the Commission be more prescriptive for the distribution timing and formatting for the open swaps reports the SDRs would provide to the reporting counterparties pursuant to proposed § 49.11(b)(2) and (3)? If so, what should be the requirements in the prescribed approach? Please be specific.</P>
                    <P>(5) Should the Commission prescribe any aspect of how SDRs must receive verifications of accuracy or notices of discrepancy pursuant to proposed § 49.11(c)? If so, what should be the requirements in the prescribed approach? Please be specific.</P>
                    <P>(6) Should the Commission require the verification of all swap data messages, as opposed to open swaps reports? Please explain why or why not. If so, what would be the costs and benefits associated with requiring the verification of all swap data messages? Please be specific.</P>
                    <P>(7) Should the Commission require verification of open swaps reports more or less frequently than weekly for reporting counterparties that are SDs, MSPs, or DCOs? If so, please explain why and suggest a more appropriate verification frequency.</P>
                    <P>(8) Should the Commission require verification of open swaps reports more or less frequently than monthly for reporting counterparties that are not SDs, MSPs, or DCOs? If so, please explain why and suggest a more appropriate verification frequency.</P>
                    <P>(9) Should reporting counterparties also be required to verify the completeness and accuracy of swap transaction and pricing data submitted pursuant to part 43? Please explain why or why not.</P>
                    <HD SOURCE="HD2">H. § 49.12—Swap Data Repository Recordkeeping Requirements</HD>
                    <P>
                        Current recordkeeping requirements for SDRs are found in §§ 49.12, 45.2(f), and 45.2(g) of the Commission's regulations. Current § 49.12 contains recordkeeping requirements for SDRs, which include both specific provisions and references to the recordkeeping requirements for SDRs included in parts 43 and 45.
                        <SU>96</SU>
                        <FTREF/>
                         The Commission is proposing amendments to the SDR recordkeeping rules to clarify ambiguities, resolve inconsistencies, and move requirements for SDRs currently in part 45 to part 49.
                    </P>
                    <FTNT>
                        <P>
                            <SU>96</SU>
                             
                            <E T="03">See generally</E>
                             17 CFR 43.3(h)(4), 17 CFR 45.2.
                        </P>
                    </FTNT>
                    <P>Proposed § 49.12(a) would require that SDRs keep full, complete, and systematic records, together with all pertinent data and memoranda, of all activities relating to the business of the SDR, including, but not limited to, all SDR information and all SDR data that is reported to the SDR.</P>
                    <P>Proposed § 49.12(b) would specify separate recordkeeping requirements for SDR information in proposed § 49.12(b)(1) and SDR data reported to the SDR in proposed § 49.12(b)(2). Proposed § 49.12(b)(1) would require that an SDR maintain all SDR information, including, but not limited to, all documents, policies, and procedures required to be kept by the Act and the Commission's regulations, correspondence, memoranda, papers, books, notices, accounts, and other such records made or received by the SDR in the course of its business. All SDR information would be maintained in accordance with § 1.31 of this chapter.</P>
                    <P>
                        Proposed § 49.12(b)(2) would require an SDR to maintain all SDR data and timestamps reported to or created by the SDR, and all messages related to such reporting, throughout the existence of the swap that is the subject of the SDR data and for five years following final termination of the swap, during which time the records would be readily accessible by the SDR and available to the Commission via real-time electronic access, and for a period of at least ten additional years in archival storage from which such records are retrievable by the SDR within three business days.
                        <SU>97</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>97</SU>
                             The propose retention period is the current requirement for SDR records retention. 
                            <E T="03">See</E>
                             17 CFR 45.2(g) (requiring that all records required to be kept by an SDR be kept readily accessible and electronically available to the Commission throughout the existence of the swap and for five years after final termination of the swap and then kept in archival storage for an additional period of at least ten years).
                        </P>
                    </FTNT>
                    <P>Proposed § 49.12(c) would require SDRs to create and maintain records of SDR validation errors and SDR data reporting errors and omissions. Proposed § 49.12(c)(1) would require an SDR to create and maintain an accurate record of all reported SDR data that fails to satisfy the SDR's data validation procedures. The records would include, but would not be limited to, records of all of the SDR data reported to the SDR that failed to satisfy the SDR data validation procedures, all SDR validation errors, and all related messages and timestamps.</P>
                    <P>Proposed § 49.12(c)(2) would require an SDR to create and maintain an accurate record of all SDR data errors and omissions reported to the SDR and all corrections disseminated by the SDR pursuant to parts 43, 45, and 46. SDRs would be required to make the records available to the Commission on request.</P>
                    <P>The Commission is proposing to amend § 49.12(d) by replacing it with a revised version of current § 49.12(c) that would require that: (i) All records required to be kept pursuant to part 49 must be open to inspection upon request by any representative of the Commission or any representative of the U.S. Department of Justice; and (ii) an SDR must produce any record required to be kept, created, or maintained by the SDR in accordance with § 1.31.</P>
                    <P>Finally, the Commission is proposing a technical change to move the current requirements of § 49.12(e) to the proposed revised requirements of SDRs to monitor, screen, and analyze SDR data in § 49.13, as discussed further below in section II.I.</P>
                    <P>
                        Current § 49.12 
                        <SU>98</SU>
                        <FTREF/>
                         contains recordkeeping requirements for SDRs, which include both specific provisions and references to the recordkeeping requirements for SDRs included in parts 43 and 45.
                        <SU>99</SU>
                        <FTREF/>
                         Current § 49.12(a) requires an SDR to maintain its books and records in accordance with the recordkeeping requirements of part 45.
                        <SU>100</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>98</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>99</SU>
                             
                            <E T="03">See generally</E>
                             17 CFR 49.12, 17 CFR 45.2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>100</SU>
                             The recordkeeping requirements of part 45 for SDRs are found in § 45.2(f) and (g). 
                            <E T="03">See</E>
                             17 CFR 45.2(f) and (g).
                        </P>
                    </FTNT>
                    <P>
                        Current § 49.12(b) requires the SDR to maintain swap data (including historical 
                        <PRTPAGE P="21056"/>
                        positions) throughout the existence of the swap and for five years following the final termination of the swap, during which time the records must be readily accessible by the SDR, available to the Commission via real-time electronic access, and in archival storage from which the data is retrievable by the SDR within three business days.
                        <SU>101</SU>
                        <FTREF/>
                         Current § 49.12(b) however does not fully account for the requirements of § 45.2(g)(2).
                        <SU>102</SU>
                        <FTREF/>
                         Additionally, the sections of part 45 applicable to SDRs apply to all records, as opposed to current § 49.12(b), which only applies to swap data.
                    </P>
                    <FTNT>
                        <P>
                            <SU>101</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.12(b).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>102</SU>
                             Section 45.2(g)(2) requires that all records required to be kept by an SDR must be kept in archival storage for ten years after the initial § 45.2(g)(1) retention period. Current § 49.12(b) only includes the initial retention period.
                        </P>
                    </FTNT>
                    <P>Current § 49.12(c) requires all records that are required to be kept pursuant to part 49 be open to inspection upon request by any representative of the Commission and the U.S. Department of Justice. Current § 49.12(c) also requires that copies of all SDR records will be provided, at the expense of the SDR or person required to keep such records, to any representative of the Commission upon request, either by electronic means or in hard copy, or both, as requested by the Commission.</P>
                    <P>Current § 49.12(d) requires an SDR to comply with the real time public reporting and recordkeeping requirements of § 49.15 and part 43. Current § 49.12(e) requires an SDR to establish policies and procedures to calculate positions for position limits and for any other purpose as required by the Commission.</P>
                    <P>
                        The Commission's proposed amendments to § 49.12(a) incorporate the provisions of current § 45.2(f). Current § 49.12(a) implies that the recordkeeping requirements only apply to swap data 
                        <SU>103</SU>
                        <FTREF/>
                         while § 45.2(f) clearly states that its requirements apply to records, not only data reported to the SDR.
                        <SU>104</SU>
                        <FTREF/>
                         As discussed in section III.A, coupled with the deletion of § 45.2(f) and (g), this amendment would reduce confusion that may arise from having separate SDR recordkeeping requirements in two different rules. This amendment would also clearly state that an SDR is required to keep records beyond just the swap data that is reported to the SDR, which is consistent with the requirements of current § 45.2(f). The Commission notes that, despite the amendment to § 49.12(a), the actual requirements for an SDR would remain the same, because the amendments to § 49.12(a) are merely reproducing the § 45.2(f) requirements, which have applied to SDRs since the effective date for part 45 in 2012.
                    </P>
                    <FTNT>
                        <P>
                            <SU>103</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.12(a) (regarding the swap data required to be reported to the swap data repository).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>104</SU>
                             
                            <E T="03">See</E>
                             17 CFR 45.2(f) (Each swap data repository registered with the Commission shall keep full, complete, and systematic records, together with all pertinent data and memoranda, of all activities relating to the business of the swap data repository and all swap data reported to the swap data repository, as prescribed by the Commission.).
                        </P>
                    </FTNT>
                    <P>
                        The Commission is proposing to amend current § 49.12(b) because: (i) Current § 49.12(b) only applies to swap data,
                        <SU>105</SU>
                        <FTREF/>
                         as opposed to all records required to be kept by an SDR; 
                        <SU>106</SU>
                        <FTREF/>
                         (ii) current § 49.12(b) only fully includes the record retention and retrieval requirements of § 45.2(g)(1),
                        <SU>107</SU>
                        <FTREF/>
                         though the requirements of § 45.2(g)(2) 
                        <SU>108</SU>
                        <FTREF/>
                         also apply to all SDR records; and (iii) neither current § 49.12(b) nor § 45.2 distinguish between records of data related to swaps and other records required to be kept by SDRs in regards to the retention periods. Current § 49.12(b) and § 45.2 use the existence of the swap as the basis for the record retention timeframes, but this offers no guidance on how long to keep a record of SDR information, such as SDR policies and procedures. The Commission proposes to remove these inconsistencies and to clarify the scope of SDR recordkeeping, while also consolidating SDR recordkeeping obligations in one regulation.
                    </P>
                    <FTNT>
                        <P>
                            <SU>105</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.12(b) (A registered swap data repository shall maintain swap data).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>106</SU>
                             
                            <E T="03">See</E>
                             17 CFR 45.2(f) (Stating that SDRs are required to keep full, complete, and systematic records, together with all pertinent data and memoranda, of all activities relating to the business of the swap data repository and all swap data reported to the swap data repository).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>107</SU>
                             
                            <E T="03">See</E>
                             17 CFR 45.2(g)(1) (Throughout the existence of the swap and for five years following the final termination of the swap, during which time the records must be readily accessible by the swap data repository and available to the Commission via real time electronic access.).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>108</SU>
                             
                            <E T="03">See</E>
                             17 CFR 45.2(g)(2) (Thereafter, for a period of at least ten additional years in archival storage from which they are retrievable by the swap data repository within three business days.).
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.12(b)(1) also requires that the SDR information be maintained in accordance with § 1.31.
                        <SU>109</SU>
                        <FTREF/>
                         The proposed changes to § 49.12(b) would also help harmonize the Commission's regulations with the SEC's regulations.
                        <SU>110</SU>
                        <FTREF/>
                         The SDR information listed in the proposed changes to § 49.12(b)(1) largely matches the SEC's requirement for SBSDR recordkeeping 
                        <SU>111</SU>
                        <FTREF/>
                         and the retention provisions of § 1.31 of this chapter largely match the requirement for SBSDRs.
                        <SU>112</SU>
                        <FTREF/>
                         Further, any SDR that also registers with the SEC as an SBSDR would have to comply with § 49.12 and § 240.13n-7, and therefore consistency between the recordkeeping provisions would be particularly beneficial to these SDRs. The SDR information records requirement is also similar to recordkeeping obligations for DCMs,
                        <SU>113</SU>
                        <FTREF/>
                         SEFs,
                        <SU>114</SU>
                        <FTREF/>
                         and DCOs.
                        <SU>115</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>109</SU>
                             Section 1.31 of the Commission's regulations is the Commission's general recordkeeping provision, which requires, among other requirements, that all regulatory records that do not pertain to specific transactions and are not retained oral communications be kept for no less than five years from the creation date of the record. 
                            <E T="03">See</E>
                             17 CFR 1.31(b)(3).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>110</SU>
                             The concept of separate recordkeeping requirements for information similar to SDR information and for SDR data reported to an SDR has already been adopted by the SEC in its regulations governing SBSDRs. 
                            <E T="03">See</E>
                             17 CFR 240.13n-7(b) (listing recordkeeping requirements for SBSDRs); 17 CFR 240.13n-7(d) (excluding “transaction data and positions” from the recordkeeping requirements and instead referring to 17 CFR 240.13n-5 for this recordkeeping).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>111</SU>
                             
                            <E T="03">See</E>
                             17 CFR 240.13n-7(b)(1) (Every security-based swap data repository shall keep and preserve at least one copy of all documents, including all documents and policies and procedures required by the Securities Exchange Act and the rules and regulations thereunder, correspondence, memoranda, papers, books, notices, accounts, and other such records as shall be made or received by it in the course of its business as such.).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>112</SU>
                             
                            <E T="03">Compare</E>
                             17 CFR 1.31(b)(3) (A records entity shall keep each regulatory record for a period of not less than five years from the date on which the record was created.) 
                            <E T="03">and</E>
                             17 CFR 1.31(b)(4) (A records entity shall keep regulatory records exclusively created and maintained on paper readily accessible for no less than two years. A records entity shall keep electronic regulatory records readily accessible for the duration of the required record keeping period.) 
                            <E T="03">with</E>
                             17 CFR 240.13n-7(b)(2) (Every SBSDR shall keep all such documents for a period of not less than five years, the first two years in a place that is immediately available to representative of the Securities and Exchange Commission for inspection and examination.).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>113</SU>
                             
                            <E T="03">See</E>
                             17 CFR 38.951.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>114</SU>
                             
                            <E T="03">See</E>
                             17 CFR 37.1001.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>115</SU>
                             
                            <E T="03">See</E>
                             17 CFR 39.20.
                        </P>
                    </FTNT>
                    <P>
                        By specifically requiring records to be kept for all SDR data reported to the SDR, including all timestamps and messages to or from the SDR related to the reported SDR data, as opposed to only swap data,
                        <SU>116</SU>
                        <FTREF/>
                         and requiring that the records be kept for ten years in archival storage,
                        <SU>117</SU>
                        <FTREF/>
                         proposed § 49.12(b)(2) would reorganize current § 49.12(b). These “new” requirements are however already applicable to SDR recordkeeping by virtue of their inclusion in § 45.2(f) and (g).
                        <FTREF/>
                        <SU>118</SU>
                          
                        <PRTPAGE P="21057"/>
                        Proposed § 49.12(b)(2) would reproduce the requirements of § 45.2(f) and (g) in part 49 to minimize the number of regulatory sections that contain recordkeeping and retention requirements for SDRs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>116</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.12(b) (A registered swap data repository shall maintain swap data throughout the existence of the swap and for five years following final termination of the swap).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>117</SU>
                             Current § 49.12(b) does not specifically include the ten-year requirement, though current § 49.12(a) does state that books and records must be kept in accordance with the requirements of part 45, which does include the ten-year requirement. 
                            <E T="03">See</E>
                             17 CFR 49.12(a) and (b); 17 CFR 45.2(g)(2).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>118</SU>
                             
                            <E T="03">See</E>
                             17 CFR 45.2(f) and (g). Though the term “swap data” is defined in § 49.2(a) to mean the specific data elements and information set forth in 
                            <PRTPAGE/>
                            part 45 of this chapter, the Commission notes that the term “swap data” is not currently defined in part 45. Section 45.2(f) requires the SDR to keep full, complete, and systematic records, together with all pertinent data and memoranda, of all activities related to the business of the swap data repository and all swap data reported to the swap data repository, as prescribed by the Commission. This expansive requirement for “all pertinent data and memoranda” for all activities related to the business of the swap data repository and all swap data reported to the swap data repository shows that § 45.2(g) requires the SDRs to keep records of data from activities beyond reporting pursuant to part 45 of this chapter, including, for example, all of the required swap transaction and pricing data reporting pursuant to part 43 of this chapter. The “full, complete, and systematic records” that must be kept for “all activities related to the business” of the SDR also include all messages related to the reported data, including all messages sent from the SDR and to the SDR. This recordkeeping obligation on SDRs is analogous to recordkeeping obligations on DCMs, SEFs, and DCOs. 
                            <E T="03">See</E>
                             17 CFR 38.950, 37.1001, and 39.20(a).
                        </P>
                    </FTNT>
                    <P>The Commission notes that though the Commission is specifically proposing recordkeeping requirements for SDR data validation errors and SDR data reporting errors in this proposed § 49.12(c), this would not in any way limit the scope of recordkeeping requirements in proposed § 49.12 to these records. The recordkeeping discussed in proposed § 49.12(c) would also be required under the more general recordkeeping provisions of proposed § 49.12.</P>
                    <P>The Commission notes that it believes SDRs already receive the data validations information that would be required in proposed § 49.12(c) via regular interaction with SEFs, DCMs, and reporting counterparties, but emphasizes that it must be maintained in order to allow for assessments of reporting compliance, including the initial reporting and the correction of the SDR data. The Commission also notes that because the records addressed by proposed § 49.12(c) are all comprised of or relate to SDR data reported to SDRs, all records created and maintained by the SDR pursuant to proposed § 49.12(c) would be subject to the requirements of proposed § 49.12(b)(2).</P>
                    <P>
                        The Commission notes that current § 49.12(d) 
                        <SU>119</SU>
                        <FTREF/>
                         is redundant because its requirements that an SDR comply with the real time public reporting and recordkeeping requirements prescribed in § 49.15 and part 43 are also required by revised §§ 49.12(b)(2) and 49.15, as well as part 43. The Commission further notes that though current § 49.12(d) is proposed to be removed, SDRs would still be subject to the real time public reporting and recordkeeping requirements of § 49.15 and part 43.
                    </P>
                    <FTNT>
                        <P>
                            <SU>119</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.12(d) (A registered swap data repository shall comply with the real time public reporting and recordkeeping requirements prescribed in § 49.15 and part 43 of this chapter.).
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of proposed § 49.12. The Commission also invites specific comment on the following:
                    </P>
                    <P>(10) Would SDRs be substantially impacted by changing the archival storage requirements of current § 45.2(g)(2) and proposed § 49.12(b)(2) from ten years to a different period of time? If so, what would be the correct length of time, and how would this change impact the SDRs? Please include specific facts and figures when providing comments.</P>
                    <HD SOURCE="HD2">I. § 49.13—Monitoring, Screening, and Analyzing Data</HD>
                    <P>
                        Section 21(c)(5) of the CEA specifically requires SDRs to, at the direction of the Commission, establish automated systems for monitoring, screening, and analyzing swap data, including compliance and frequency of end-user clearing exemption claims by individuals and affiliated entities.
                        <SU>120</SU>
                        <FTREF/>
                         The Commission believes, based on the text of section 21(c)(5) of the CEA, that SDRs function not only as repositories for swap data, but also as providers of data support for the Commission's oversight of swaps markets and swap market participants. To implement section 21(c)(5), the Commission adopted current § 49.13 and § 49.14.
                    </P>
                    <FTNT>
                        <P>
                            <SU>120</SU>
                             7 U.S.C. 24a(c)(5).
                        </P>
                    </FTNT>
                    <P>Current § 49.13 requires SDRs to: (i) Monitor, screen, and analyze all swap data in their possession as the Commission may require, including for the purpose of any standing swap surveillance objectives that the Commission may establish as well as ad hoc requests; and (ii) develop systems and maintain sufficient resources as necessary to execute any monitoring, screening, or analyzing functions assigned by the Commission.</P>
                    <P>
                        In the Part 49 Adopting Release, the Commission received comments relating to §§ 49.13(a) and 49.14 indicating concerns that the then-proposed regulations did not sufficiently describe the specific tasks SDRs are expected to perform.
                        <SU>121</SU>
                        <FTREF/>
                         In response, the Commission specifically stated that its intention in adopting §§ 49.13(a) and 49.14 was to codify the statutory requirements in CEA section 21(c)(5) and later establish specific monitoring, screening, and analyzing duties when its knowledge of the swaps markets was more fully-developed.
                        <SU>122</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>121</SU>
                             
                            <E T="03">See</E>
                             letters from: (1) Americans for Financial Reform on February 22, 2011; (2) Chris Barnard on May 25, 2011; (3) Better Markets on February 22, 2011; (4) CME Group on February 22, 2011; (5) Depository Trust &amp; Clearing Corporation on February 22, 2011; (6) Reval on February 18, 2011; (7) SunGard Energy &amp; Commodities on February 22, 2011; and (8) TriOptima on February 22, 2011 
                            <E T="03">available at http://comments.cftc.gov/PublicComments/CommentList.aspx?id=939.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>122</SU>
                             
                            <E T="03">See</E>
                             Part 49 Adopting Release at 54548.
                        </P>
                    </FTNT>
                    <P>The Commission has worked with SDRs to implement the Commission's swap reporting regulations since 2011. In that time, SDRs have worked with Commission staff to produce reports that enable the Commission to perform oversight and monitoring of the swaps market. For instance, Commission staff uses the open swaps reports to monitor risk. In addition, reports on clearing exception elections provide the Commission with information on which entities are claiming exemptions from the Commission's mandatory clearing requirement for swaps.</P>
                    <P>As noted in the Part 49 Adopting Release, the Commission intended to establish specific monitoring, screening, and analyzing duties for SDRs separately. The Commission believes that, based on its experience working with SDRs to monitor, screen, and analyze swap data as directed by CEA section 21(c)(5) thus far, it is prepared to identify the specific duties. The Commission expects specifying these topic areas would not impose substantial new fixed costs on SDRs because SDRs have already established the technology and related infrastructure designed to monitor, screen, and analyze data at the request of the Commission as required under current § 49.13(a).</P>
                    <P>Finally, the Commission notes that the requested tasks would only be performed by SDRs to provide the Commission with data and reports related to the listed topic areas that would assist the Commission in performing its regulatory functions. The Commission would not expect SDRs to perform any of the Commission's regulatory functions or to provide recommendations to the Commission.</P>
                    <P>
                        The Commission proposes to amend § 49.13 to provide more detail on the monitoring, screening, and analyzing tasks that SDRs may be required to perform as directed by the Commission. The Commission is also proposing to amend § 49.13 to make clear that the requirements of proposed § 49.13 would apply to SDR data reported to the SDR pursuant to parts 43, 45, and 46. CEA section 21(c)(5) requires SDRs to 
                        <PRTPAGE P="21058"/>
                        establish automated systems for monitoring, screening, and analyzing swap data, but the term “swap data” is not defined in the CEA. The Commission believes that monitoring, screening, and analyzing tasks could be incomplete if limited to only swap data, as defined in § 49.2.
                        <SU>123</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>123</SU>
                             Current and proposed § 49.2 limit “swap data” to data reported to an SDR pursuant to part 45. 
                            <E T="03">See</E>
                             17 CFR 49.2(a)(15). The proposed amendments to § 49.2(a) do not substantively change the definition of “swap data” for the purposes of part 49.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.13(a) would generally require that an SDR: (i) Establish automated systems for monitoring, screening, and analyzing all relevant SDR data in its possession in the form and manner as directed by the Commission, and (ii) routinely monitor, screen, and analyze relevant SDR data at the request of the Commission.
                        <SU>124</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>124</SU>
                             As discussed further below, proposed § 49.13(a) would more closely track the language of CEA section 21(c)(5) that requires SDRs to at the direction of the Commission, establish automated systems for monitoring, screening, and analyzing swap data, including compliance and frequency of end-user clearing exemption claims by individual and affiliated entities.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.13(a)(1) would require SDRs to utilize relevant SDR data maintained by the SDR to provide information to the Commission concerning such relevant SDR data. Proposed § 49.13(a)(1) would state that monitoring, screening, and analyzing requests may require the SDRs to compile and/or calculate the requested information within discrete categories, including comparing information among categories, and lists potential topics areas for which the Commission could request related data and reports: (i) The accuracy, timeliness, and quality of SDR data; (ii) updates and corrections to, and verification of the accuracy of, SDR data; (iii) currently open swaps and the consistency of SDR data related to individual swaps; (iv) the calculation of market participants' swap positions, including for purposes of position limit compliance, risk assessment, and compliance with other regulatory requirements; 
                        <SU>125</SU>
                        <FTREF/>
                         (v) swap counterparty exposure to other counterparties and standard market risk metrics; (vi) swap valuations and margining activities; (vii) audit trails for individual swaps, including post-transaction events such as allocation, novation, and compression, and all related messages; (viii) compliance with Commission regulations; (ix) market surveillance; (x) the use of clearing exemptions and exceptions; and/or (xi) statistics on swaps market activity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>125</SU>
                             The Commission notes that the Commission regulations currently require SDRs to establish policies and procedures to calculate swap positions in § 49.12(e). The Commission is proposing to incorporate the current § 49.12(e) into proposed § 49.13(a), without substantively modifying the requirements for SDRs to calculate swap positions.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.13(a)(2) would state that all monitoring, screening, and analyzing requests shall be at the discretion of the Commission, which includes, but is not limited to, the content, scope, and frequency of each required response, and require that all information provided pursuant to a request conform to the form and manner requirements established for the request pursuant to proposed § 49.30.
                        <SU>126</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>126</SU>
                             The Commission, as discussed below in section II.U, is proposing to adopt § 49.30 to establish a “form and manner” regulation applicable to how information reported to, and maintained by, SDRs would be formatted and delivered to the Commission. The term “formatted” refers to how the information would be presented and could include, but is not limited to, attributes such as data messaging standards, allowable values, and levels of precision, as well as instructions on how the information would be transmitted, including, but not limited to, direct electronic access by Commission staff or by the SDR sending the information to the Commission, and the frequency and timing of delivery.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.13(a)(3) would require that all monitoring, screening, and analyzing requests be fulfilled within the time specified by the Commission for the particular request.
                        <SU>127</SU>
                        <FTREF/>
                         Proposed § 49.13(b) would require that SDRs establish, and at all times maintain, sufficient information technology, staff, and other resources to fulfill the requirements in § 49.13 in the manner prescribed by the Commission.
                    </P>
                    <FTNT>
                        <P>
                            <SU>127</SU>
                             The Commission anticipates working with the SDRs and providing a reasonable time to fulfill each request based on the specific circumstances, including the volume of information requested and the complexity of the request.
                        </P>
                    </FTNT>
                    <P>
                        The Commission is also proposing to create a new § 49.13(c) that would incorporate current § 49.15(c) 
                        <SU>128</SU>
                        <FTREF/>
                         but also expand it to require SDRs to promptly notify the Commission of any swap transaction for which the SDR is aware that it did not receive swap data according to part 45, or data according to part 46, in addition to the current requirement to notify the Commission of any swap transaction and pricing data not received according to part 43.
                    </P>
                    <FTNT>
                        <P>
                            <SU>128</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.15(c) (Duty to Notify the Commission of Untimely Data. A registered swap data repository must notify the Commission of any swap transaction for which the real-time swap data was not received by the swap data repository in accordance with part 43 of this chapter.). As discussed further below, the Commission believes moving § 49.15(c) to § 49.13 would help consolidate the information SDRs need to send to the Commission into one part.
                        </P>
                    </FTNT>
                    <P>The Commission is providing the following list of examples of monitoring, screening, and analyzing tasks that the Commission could request in the future pursuant to proposed § 49.13(a)(1). All of the examples would fall under at least one of the topic areas included in proposed § 49.13(a)(1). The Commission emphasizes that the following list is merely examples, is not exhaustive, and does not limit the Commission's ability to request that SDRs perform other monitoring, screening, and analyzing tasks that would fall under the topics listed in proposed § 49.13(a).</P>
                    <P>Examples of potential future monitoring, screening, and analyzing activities include reports or information concerning: (i) The reporting (or corrected non-reporting) of swap transactions and any subsequent changes related to the swap, such as life cycle events, as defined in part 45; (ii) the timeliness of reporting through the tracking of execution and reporting timestamps; (iii) the altering or amending of swap terms after the initial public reporting of the swap transaction and pricing data; (iv) the application of the SDR's data validation procedures and information regarding data validation errors; (v) the identification and treatment of duplicate records; (vi) net and gross positions relating to unique product identifiers; (vii) positions of swap counterparties on an aggregate basis, including futures-equivalent positions identified with the legal entity to which a legal entity identifier is assigned; (viii) swap cancellations; (ix) accuracy and quality of reported SDR data; and (x) the positions of swap counterparties.</P>
                    <P>The Commission notes that an information request under § 49.13(a)(1) could require an SDR to review a market participant's open swap positions for swaps where that market participant elected a clearing exemption. Such a request would combine categories in § 49.13(a)(1)(iii) and (x). Proposed § 49.13(a)(1) also states that such monitoring, screening, and analyzing requests could require SDRs to provide information comparing certain metrics over a period of time. For instance, an information request could require SDRs to compare the accuracy, timeliness, and quality of SDR data submitted by one or more SEFs, DCMs, or reporting counterparties over a defined period of time. Finally, information requests could require SDRs to compare two or more categories of information across a defined period of time.</P>
                    <P>
                        The Commission understands that SDRs can only be expected to perform monitoring, screening, and analyzing tasks based on the SDR data available to each SDR and that the results of any task would be limited to the SDR data for swaps reported to each SDR. The Commission also expects that SDRs and Commission staff would work together 
                        <PRTPAGE P="21059"/>
                        to design each task before a task is prescribed, as is current practice.
                    </P>
                    <P>Finally, the Commission believes that expanding the notice requirements of current § 49.15(c) under new proposed § 49.13(c) would improve the Commission's ability to monitor compliance with its regulations and increase the Commission's ability to efficiently respond to compliance issues by helping the Commission learn of compliance issues as soon as possible so that the issues can be remedied. SDRs are often in the best position to know of non-compliance with the data reporting requirements because of the information they receive from market participants. For example, SDRs would quickly know if a reporting counterparty has reported swap data pursuant to part 45 in an untimely manner because the SDR receives the swap data, including the execution timestamp, and can quickly compare when the swap was executed and when the swap data was received. The Commission acknowledges that SDRs can only identify and notify the Commission of SDR data reporting non-compliance based on the SDR data they receive and does not expect SDRs to inform the Commission of reporting issues of which they are not aware. Expanding the notice requirement to noncompliance with parts 45 and 46 would help the Commission to learn of a wider range of compliance issues when they first arise, which in turn would help the Commission to work with market participants and SDRs to fix issues as quickly as possible.</P>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of proposed § 49.13. The Commission also invites specific comment on the following:
                    </P>
                    <P>(11) Should the Commission require SDRs to calculate positions for market participants? Are there technological and/or regulatory limitations that would make such tasks difficult to perform and unlikely to achieve the desired results? Please be specific.</P>
                    <P>(12) Should the SDRs create a process whereby the counterparties whose positions have been calculated based on data contained in the SDR have the opportunity to review and subsequently challenge and/or correct the results? Please explain why or why not.</P>
                    <P>(13) Are there specific reports or sets of data that the Commission should consider obtaining from SDRs to monitor risk exposures of individual counterparties to swap transactions, to monitor concentrations of risk exposures, or for other purposes? Please be specific.</P>
                    <P>(14) Are there specific reports or sets of data that the Commission should consider obtaining from SDRs to evaluate systemic risk or that could be used for prudential supervision? Are there any other reports or sets of data that the Commission should consider obtaining from SDRs that would not be included in the categories listed in proposed § 49.13(a)(1)? Please be specific.</P>
                    <P>(15) Are there any other tasks or functions that SDRs could perform related to swap data that could help the Commission better assess individual market participant risks and market risks generally? Please be specific.</P>
                    <P>(16) Would any of the specific monitoring, screening, or analyzing topic areas enumerated under proposed § 49.13(a)(1) impose new or substantial costs on SDRs that are not present under the requirements of current § 49.13 and section 21(c)(5) of the CEA? If so, please describe and quantify these costs.</P>
                    <P>(17) Is it sufficiently clear in this proposal that the Commission intends for SDRs to provide data and information under proposed § 49.13 solely to assist the Commission in performing its regulatory functions, rather than expecting SDRs to perform any direct oversight of market participants? If not, how should the Commission clarify that proposed § 49.13 would require SDRs to provide data and information solely to assist the Commission in performing its regulatory functions?</P>
                    <HD SOURCE="HD2">J. § 49.15—Real-Time Public Reporting by Swap Data Repositories</HD>
                    <P>The Commission proposes to amend § 49.15 to conform to the proposed amended definitions in § 49.2 as described in section II.A. As discussed above in section II.I, the Commission is also proposing to move current § 49.15(c) to § 49.13(c). The Commission also proposes to amend current § 49.15(a) and § 49.15(b) to remove the term “swap data,” which is defined as part 45 data, and replace it with language clarifying that § 49.15 pertains to swap transaction and pricing data submitted to a registered SDR pursuant to part 43. These non-substantive changes do not affect the existing requirements of § 49.15.</P>
                    <HD SOURCE="HD2">K. § 49.16—Privacy and Confidentiality Requirements of Swap Data Repositories</HD>
                    <P>
                        In connection with the proposed amendments to multiple definitions in § 49.2,
                        <SU>129</SU>
                        <FTREF/>
                         the Commission proposes to make conforming amendments to § 49.16. The Commission proposes to amend § 49.16(a)(1) to clarify that the policy and procedure requirements of § 49.16 apply to SDR information and to any SDR data that is not swap transaction and pricing data disseminated under part 43. Such policies and procedures must include, but are not limited to, policies and procedures to protect the privacy and confidentiality of any and all SDR information and all SDR data (except for swap transaction and pricing data disseminated under part 43) that the SDR shares with affiliates and non-affiliated third parties.
                    </P>
                    <FTNT>
                        <P>
                            <SU>129</SU>
                             
                            <E T="03">See</E>
                             section II.A above.
                        </P>
                    </FTNT>
                    <P>The Commission is also making conforming amendments related to the proposed removal of the term “reporting entity” and the proposed definitions of “SDR data” and “swap data.”</P>
                    <P>The Commission notes that these proposed amendments are non-substantive and would not affect the existing requirements or applicability of § 49.16.</P>
                    <HD SOURCE="HD2">L. § 49.17—Access to SDR Data</HD>
                    <P>The Commission is proposing to amend § 49.17 to clarify some of the regulation's requirements with respect to the Commission's access to SDR data. Current § 49.17 sets forth the procedures by which the CFTC and other regulators may access SDR data.</P>
                    <HD SOURCE="HD3">1. Direct Electronic Access Definition—§ 49.17(b)</HD>
                    <P>The Commission proposes to amend the § 49.17(b)(3) definition of “direct electronic access” to mean an electronic system, platform, framework, or other technology that provides internet-based or other form of access to real-time SDR data that is acceptable to the Commission and also provides scheduled data transfers to Commission electronic systems.</P>
                    <P>Current § 49.17(b)(3) defines direct electronic access as an electronic system, platform or framework that provides internet or Web-based access to real-time swap transaction data and also provides scheduled data transfers to Commission electronic systems. Currently, § 49.17(b)(3) does not include the possibility of other types of technology and does not leave the Commission any discretion over access to the data. The Commission believes its proposed changes to the definition would allow more flexibility in regards to the potential methods and forms of direct electronic access that may be provided to the Commission, and would remove any confusion over the type of data to which the term “direct electronic access” applies.</P>
                    <P>
                        The Commission believes that adding “other technology” to the existing list of methods would make clear that the Commission may decide to accept other 
                        <PRTPAGE P="21060"/>
                        methods of access, as long as the method is able to efficiently provide real-time access to SDR data and scheduled SDR data transfers to the Commission. The Commission believes flexibility in terms of the technology SDRs use to provide direct electronic access could accommodate rapid advances in technology and would not inadvertently prevent the use of future technological innovations that may provide more efficient direct electronic access to SDR data.
                    </P>
                    <P>In addition, the Commission proposes to change the current § 49.17(b)(3) text that provides internet or Web-based access to real-time swap transaction data to that provides internet-based or other forms of access to real-time SDR data. The Commission considers the removal of “Web-based” to be a non-substantive change, as the term is redundant with “internet-based.” The addition of “or other form of access” is, as with the addition of “other technology,” intended to provide more flexibility for providing direct electronic access to the Commission by making clear that the Commission may decide to accept other forms of access that are not internet-based, as long as the access to SDR data is real-time and provides for scheduled SDR data transfers to the Commission.</P>
                    <P>The Commission believes that requiring that the method(s) and form(s) of direct electronic access be “acceptable to the Commission” would make it clear that the Commission anticipates working with SDRs to decide the acceptable methods and forms of direct electronic access. This amendment would codify the Commission's current practice of working with SDRs to implement changes, as discussed above in section II.E. The Commission and SDRs routinely work together to provide both real-time internet-based access to SDR data and scheduled transfers of SDR data to the Commission. The Commission believes that the most important consideration in whether a form of access may be acceptable to the Commission would be whether the Commission can successfully utilize the method or form of access. The Commission believes this is necessary to help ensure that the direct electronic access provided is useful to the Commission and to help ensure that an SDR cannot unilaterally change the method or form of direct electronic access in a way that may prevent the Commission from performing its regulatory functions. Though the Commission intends to be flexible in regards to the methods and forms of direct electronic access, especially in the context of technological advancement, the Commission believes it is important to retain the ability to decide the acceptable methods and forms for direct electronic access at its sole discretion.</P>
                    <P>Nothing in the proposed revisions to § 49.17(b)(3) would prevent the SDRs from incorporating new technology into their systems for collecting SDR data or maintaining the SDR data within their own systems, as long as the SDR data is collected by the SDRs and provided to the Commission as required. The Commission would however expect SDRs to provide reporting counterparties with commonly-used methods for reporting SDR data to the SDR and not to force reporting counterparties to unnecessarily expend resources on the latest technology by unreasonably limiting available reporting methods. The Commission would also expect SDRs to be particularly accommodating of non-SD/MSP/DCO reporting counterparties that may not have the resources to spend on technology.</P>
                    <P>
                        Finally, the current definition of “direct electronic access” includes an SDR providing access to “real-time swap transaction data.” 
                        <SU>130</SU>
                        <FTREF/>
                         The correct defined term for the data being referenced is “SDR data.” In order to remove any confusion and increase the consistent use of terms, the Commission proposes to remove the word “transaction” and replace “swap” with “SDR” so that the phrase is instead “real-time SDR data.” 
                        <SU>131</SU>
                        <FTREF/>
                         This non-substantive change does not change the current requirements or current SDR practice for providing the Commission with direct electronic access to SDR data.
                    </P>
                    <FTNT>
                        <P>
                            <SU>130</SU>
                             17 CFR 49.17(b)(3).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>131</SU>
                             The Commission notes that the phrase “real-time” is often used to reference swap transaction and pricing data that is publicly reported pursuant to part 43. In this instance, the term refers to direct electronic access requiring that SDR data be available in real time to the entity granted direct electronic access (
                            <E T="03">i.e.,</E>
                             the Commission or its designee).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Commission Access—§ 49.17(c)</HD>
                    <P>
                        The Commission proposes to amend § 49.17(c) by incorporating the requirements of current § 45.13(a),
                        <SU>132</SU>
                        <FTREF/>
                         along with additional clarifications to consolidate the requirements for Commission access to SDR data and to describe the SDRs' responsibilities to provide SDR data to the Commission. The Commission is also proposing non-substantive edits to § 49.17 to conform terms used in the section with the rest of the Commission's regulations (
                        <E T="03">e.g.,</E>
                         replacing “swap data and SDR Information” with “SDR data and SDR Information”).
                    </P>
                    <FTNT>
                        <P>
                            <SU>132</SU>
                             The Commission is not proposing to modify current § 45.13(a) in this rulemaking. The Commission expects that subsequent rulemakings based on the Roadmap would modify the requirements of § 45.13 in ways that are not inconsistent with proposed § 49.17.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.17(c) would require SDRs to provide access to the Commission for all SDR data maintained by the SDR.
                        <SU>133</SU>
                        <FTREF/>
                         Proposed § 49.17(c) would also incorporate all of the current requirements of § 49.17(c)(1). Current § 49.17(c)(1) requires SDRs to provide direct electronic access to the Commission or the Commission's designee, including another registered entity, in order for the Commission to carry out its legal and statutory responsibilities under the Act and related regulations. The proposal would retain current § 49.17(c)(1) as § 49.17(c) and incorporate a modified version of current § 45.13(a).
                    </P>
                    <FTNT>
                        <P>
                            <SU>133</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.17(c)(1) (Direct Electronic Access. A registered swap data repository shall provide direct electronic access to the Commission or the Commission's designee, including another registered entity, in order for the Commission to carry out its legal and statutory responsibilities under the Act and related regulations.).
                        </P>
                    </FTNT>
                    <P>Specifically, proposed § 49.17(c)(1) would also require SDRs to maintain all SDR data reported to the SDR in a format acceptable to the Commission, and to transmit all SDR data requested by the Commission to the Commission as instructed by the Commission. Proposed § 49.17(c)(1) would also provide that the instructions may include, but are not limited to, the method, timing, and frequency of transmission, as well as the format and scope of the SDR data to be transmitted.</P>
                    <P>
                        Proposed § 49.17(c)(1) would change the requirements of current § 45.13(a) from maintaining and transmitting “swap data” to maintaining and transmitting “SDR data,” to make clear that the SDRs must maintain all SDR data reported to the SDRs in a format acceptable to the Commission and transmit all SDR data requested by the Commission, not just swap data.
                        <SU>134</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>134</SU>
                             The Commission does not believe this revision is a change from current SDR practice.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.17(c)(1) would also broaden the requirements of current § 45.13(a) from transmit all swap data requested by the Commission to the Commission in an electronic file in a format acceptable to the Commission 
                        <SU>135</SU>
                        <FTREF/>
                         to transmit all SDR data requested by the Commission to the Commission as instructed by the Commission, and 
                        <PRTPAGE P="21061"/>
                        explains what these instructions may include.
                    </P>
                    <FTNT>
                        <P>
                            <SU>135</SU>
                             17 CFR 45.13(a).
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that these revisions would make clear that the Commission's ability to set the parameters of SDR data transmission is not limited to requiring electronic transfers in a particular format, as could be inferred from current § 45.13(a).
                        <SU>136</SU>
                        <FTREF/>
                         The Commission believes it needs the ability to instruct SDRs as to all aspects of SDR data transfers to the Commission. These instructions could include, but are not necessarily limited to, method of transmission (
                        <E T="03">e.g.,</E>
                         electronic or non-electronic transmission and file types used for transmission), the timing of data transmission, the frequency of data transmission, the formatting of the data to be transmitted (
                        <E T="03">e.g.,</E>
                         data feeds or batch transmission), and the actual SDR data to be transmitted.
                    </P>
                    <FTNT>
                        <P>
                            <SU>136</SU>
                             
                            <E T="03">See id.</E>
                             (stating that SDRs shall transmit all swap data requested by the Commission to the Commission in an electronic file in a format acceptable to the Commission.).
                        </P>
                    </FTNT>
                    <P>
                        While these revisions may appear to broaden the scope of the Commission's ability to define the terms of data transfer to the Commission, current § 45.13(a) gives the Commission broad discretion in instructing SDRs on how to send data to the Commission to enable the Commission to perform its regulatory functions, increase market transparency, and mitigate systemic risk.
                        <SU>137</SU>
                        <FTREF/>
                         Current SDR practice also reflects the Commission's wide discretion in instructing SDRs in how to send data to the Commission, as the SDRs currently send large amounts of data to the Commission on a regular basis in various formats, based on instructions provided by the Commission. The Commission also believes incorporating the current § 45.13(a) requirements in § 49.17(c) would help SDRs by locating more of their SDR responsibilities located in part 49.
                    </P>
                    <FTNT>
                        <P>
                            <SU>137</SU>
                             
                            <E T="03">See</E>
                             Part 45 Adopting Release at 2169 (requiring an SDR to maintain all swap data reported to it in a format acceptable to the Commission, and to transmit all swap data requested by the Commission to the Commission in an electronic file in a format acceptable to the Commission); 
                            <E T="03">see also</E>
                             Part 49 Adopting Release at 54552 (stating that the Commission does not believe that SDRs should have the discretion or ability to determine the appropriate data sets that should be provided to the Commission).
                        </P>
                    </FTNT>
                    <P>Though SDRs may need to update their systems in response to changing Commission instructions over time, the Commission expects to work with the SDRs to ensure that any changes are practical and reasonable, and provide time for the SDRs to adjust their systems.</P>
                    <HD SOURCE="HD3">3. Technical Correction—§ 49.17(f)(2)</HD>
                    <P>
                        The Commission proposes to amend § 49.17 to replace an incorrect reference to “37.12(b)(7)” at the end of paragraph (f)(2) with the correct reference to “39.12(b)(7)” of the Commission's regulations, as there is no § 37.12(b)(7) in the Commission's regulations.
                        <SU>138</SU>
                        <FTREF/>
                         The Commission also proposes non-substantive amendments to § 49.17(f)(2) to incorporate proposed changes in terminology used in § 49.17(f)(2) in order for the terms used to be consistent with the terms listed in proposed § 49.2(a).
                    </P>
                    <FTNT>
                        <P>
                            <SU>138</SU>
                             
                            <E T="03">See</E>
                             17 CFR 37.12(b).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">4. Delegation of Authority—§ 49.17(i)</HD>
                    <P>The Commission proposes to move the delegation of authority in current § 49.17(i) to § 49.31(a)(7). Current § 49.17(i) delegates to the Director of DMO the authority reserved to the Commission in current § 49.17. This includes the authority to instruct SDRs on how to transmit SDR data to the Commission. As discussed further below in section II.V, the Commission is proposing to include as many delegations of authority as possible for part 49 in proposed § 49.31, including the delegation of authorities reserved to the Commission in § 49.17, to improve consistency within the part and remove confusion that may arise from listing delegations of authority in multiple sections. The Commission emphasizes that this change would not affect the current delegation of authority, as all functions reserved to the Commission in § 49.17 would still be delegated to the Director of DMO in proposed § 49.31.</P>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of proposed § 49.17. The Commission also invites specific comment on the following:
                    </P>
                    <P>(18) Is there a need to further clarify any of the requirements of the revised paragraphs of proposed § 49.17? If so, which requirements and what information need to be clarified? Please be specific.</P>
                    <P>(19) Are there any aspects of current or proposed § 49.17 that would inhibit or in any way prevent experimentation with or development of new technological approaches to SDR operations or providing SDR data to the Commission? If so, what are these inhibitors and how can they be mitigated?</P>
                    <HD SOURCE="HD2">M. § 49.18—Confidentiality Arrangement</HD>
                    <P>The Commission is proposing to move the delegation of authority in current § 49.18(e) to § 49.31(a)(8). Current § 49.18(e) delegates to the Director of DMO all functions reserved to the Commission in § 49.18, including the authority to specify the form of confidentiality arrangements required prior to disclosure of swap data by an SDR to an appropriate domestic or foreign regulator, and the authority to limit, suspend, or revoke such appropriate domestic or foreign regulators' access to swap data held by an SDR.</P>
                    <P>As discussed further below in section II.V, the Commission believes market participants would benefit by being able to locate most delegations of authority in proposed § 49.31. All functions reserved to the Commission in current § 49.18 would continue to be delegated to the Director of DMO under this proposed amendment.</P>
                    <HD SOURCE="HD2">N. § 49.20—Governance Arrangements (Core Principle 2)</HD>
                    <P>The Commission proposes to amend citations to § 49.2 within § 49.20 to conform to proposed changes in the numbering of the definitions contained in proposed § 49.2, as discussed above in section II.A. The Commission also proposes to make conforming changes to reflect the proposed changes to definitions in § 49.2. The Commission is proposing to amend current citations to § 49.2(a)(14) in § 49.20(b)(2)(v) and to § 49.2(a)(1) in § 49.20(c)(1)(ii)(B) to citations to § 49.2(a). The Commission also proposes to update these paragraphs and § 49.20(b)(2)(vii) to reflect proposed changes related to the definitions of “SDR data,” “SDR information,” “registered swap data repository,” and “reporting entity.” These non-substantive changes do not affect the existing requirements of § 49.20.</P>
                    <HD SOURCE="HD2">O. § 49.22—Chief Compliance Officer</HD>
                    <P>The Commission is proposing to amend § 49.22 to clarify obligations, make technical corrections and non-substantive changes, and remove unnecessary requirements.</P>
                    <P>
                        The Commission is proposing to define senior officer in § 49.22(a) as the chief executive officer or other equivalent officer of the SDR.
                        <SU>139</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>139</SU>
                             The Commission notes that this amendment would define a term that is currently used throughout § 49.22.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.22(b)(1)(i) would specify that the chief compliance officer (“CCO”) of an SDR shall have the authority and resources to develop, in consultation with the board of directors or senior officer, the policies and procedures of the SDR and enforce such policies and procedures to fulfill the 
                        <PRTPAGE P="21062"/>
                        duties set forth for CCOs in the CEA and Commission regulations.
                    </P>
                    <P>Proposed § 49.22(c)(1) would clarify that only the SDR's board of directors or senior officer may appoint the CCO, and require that SDRs notify the Commission within two business days of the appointment, whether interim or permanent. Proposed § 49.22(c)(2) would require that the CCO report directly to the board of directors or the senior officer of the SDR. Proposed § 49.22(c)(3) would specify that only the board of directors or the senior officer may remove the CCO, and that the SDR shall notify the Commission within two business days of the removal, whether interim or permanent.</P>
                    <P>Proposed § 49.22(c)(4) would contain the requirement currently found in § 49.22(c)(1) for the CCO to meet with the board of directors or senior officer of the SDR at least annually.</P>
                    <P>Proposed § 49.22(d)(2) would provide more detail on conflicts of interest obligations by making clear that CCOs must take “reasonable steps,” in consultation with the board of directors or the senior officer of the SDR, to resolve any “material” conflicts of interest that may arise, and would no longer list specific types of conflicts. Proposed § 49.22(d)(4) would remove an unnecessary reference to § 49.18. Proposed § 49.22(d)(5)-(6) would specify that SDRs must establish procedures reasonably designed to handle, respond, remediate, retest, and resolve noncompliance issues identified by the CCO through any means, including any compliance office review, look-back, internal or external audit finding, self-reported error, or validated compliant, and establish and administer a compliance manual designed to promote compliance with the applicable laws, rules, and regulations and a written code of ethics for the SDR designed to prevent ethical violations and to promote honesty and ethical conduct by SDR personnel.</P>
                    <P>Proposed § 49.22(e) would streamline, clarify, and rearrange the requirements of the SDR annual compliance report. The Commission is proposing to streamline and combine current § 49.22(e)(1) and (2) into proposed § 49.22(e)(1). The Commission is also proposing to remove many of the examples of how material compliance issues can be identified from current § 49.22(e)(5) so as not to imply any limits on the material compliance matters that must be described. Finally, the Commission proposes to add “in all material aspects” to the end of current § 49.22(e)(6) in proposed § 49.22(e)(5), in order to reduce CCOs' concerns with certifying the annual compliance report's accuracy.</P>
                    <P>
                        Proposed § 49.22(f)(1) would remove the requirement for any discussion of the annual compliance report after submission to the board of directors or senior officer to be recorded in the board minutes or other similar record as evidence of compliance with the submission requirement.
                        <SU>140</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>140</SU>
                             The Commission notes that, even with the removal of this requirement, the Commission may still require an SDR to provide a demonstration of compliance with the requirements of proposed § 49.22(f) under proposed § 49.29. 
                            <E T="03">See</E>
                             section II.T below.
                        </P>
                    </FTNT>
                    <P>Proposed § 49.22(f)(2) would increase the amount of time that SDRs have to submit the annual compliance report to the Commission from 60 days to 90 calendar days after the end of the SDR's fiscal year. As discussed above in section II.B, the Commission is also proposing to remove the annual amendment requirement in § 49.3(a)(5). The Commission is therefore also proposing to remove the reference to § 49.3(a)(5) from § 49.22(f)(2).</P>
                    <P>
                        Proposed § 49.22(f)(3) would include a requirement that, where an amendment to the annual compliance report must be submitted to the Commission, the CCO also submit the amended annual compliance report to the SDR's board of directors or the senior officer.
                        <SU>141</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>141</SU>
                             The Commission is also proposing a change to § 49.22(f)(3) to correct the inaccurate reference to § 49.22(e)(67). There is no § 49.22(e)(67) and the proposed amendment would instead reference the correct § 49.22(e)(5). This technical amendment does not affect the existing requirements of § 49.22(f)(3).
                        </P>
                    </FTNT>
                    <P>Proposed § 49.22(f)(4) would allow the Commission to more easily grant requests for an extension of time to file the annual compliance report by removing the requirement that SDRs must show “substantial, undue” hardship.</P>
                    <P>Proposed § 49.22(g) would simplify the language and organization of the recordkeeping requirements for records related to the SDRs' policies and records created related to the annual compliance report, and would no longer contain specific examples of records, but would still require the same records be maintained in accordance with proposed § 49.12.</P>
                    <P>Current § 49.22 sets forth the requirements for SDR CCOs, including: Their designation and qualifications; their appointment, supervision, and removal; their duties; and their responsibilities with respect to the annual compliance report and recordkeeping.</P>
                    <P>The Commission believes that the amendments discussed above would clarify and streamline the requirements for, and responsibilities of, CCOs in a manner that balances the Commission's interest in providing CCOs discretion in fulfilling their duties against clearly specifying their responsibilities. The large majority of proposed amendments are non-substantive changes that would clarify the requirements, simplify the wording of the requirements, reorganize the requirements into a more logical order, or remove unnecessary text.</P>
                    <P>
                        Proposed § 49.22(d)(2) would change the duties for CCOs related to conflicts of interest to a more practical requirement. Current § 49.22(d)(2) implies that a CCO should resolve all conflicts of interest, regardless of their potential effect on the operations of the SDR.
                        <SU>142</SU>
                        <FTREF/>
                         The Commission does not believe a CCO should be required to expend resources to resolve every conceivable conflict of interest that may affect an SDR and instead proposes to require CCOs to take reasonable steps to resolve any material conflicts of interest that may arise. This proposed requirement for taking reasonable steps to resolve material conflicts of interest reflects the CCO's practical ability to detect and resolve conflicts. Moreover, the proposed amendment reflects the Commission's belief that a CCO is well positioned to assess whether a potential conflict of interest is material to his or her SDR's ability to comply with the Act and the Commission's regulations. The Commission believes that proposed § 49.22(d)(2) would allow SDRs to address conflicts of interest while mitigating the burdens associated with addressing the conflicts.
                    </P>
                    <FTNT>
                        <P>
                            <SU>142</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.22(d)(2) (requiring the CCO to, in consultation with the board of directors or senior officer, resolve any conflicts of interest that may arise).
                        </P>
                    </FTNT>
                    <P>
                        The Commission notes that, while proposed § 49.22(d)(2) removes the three examples of potential conflicts of interest from current § 49.22(d)(2)(i)-(iii),
                        <SU>143</SU>
                        <FTREF/>
                         these three examples would still need to be addressed if they rise to the level of a material conflict of interest.
                    </P>
                    <FTNT>
                        <P>
                            <SU>143</SU>
                             
                            <E T="03">See id.</E>
                             (including conflicts between (i) business considerations and compliance requirements, (ii) business considerations and the requirement that the SDR provide fair and open access, and (iii) SDR management and members of the SDR's board of directors as examples of conflicts of interest to be addressed by the SDR's CCO).
                        </P>
                    </FTNT>
                    <P>
                        The Commission also proposes to streamline the requirements on SDRs in preparing the annual compliance report in proposed § 49.22(e)(1). Proposed § 49.22(e)(1) would remove the current § 49.22(e)(2) 
                        <SU>144</SU>
                        <FTREF/>
                         required comparison of all applicable Commission regulations and CEA requirements with each SDR 
                        <PRTPAGE P="21063"/>
                        policy designed to satisfy each requirement and assessment of the effectiveness of each policy and areas for improvement. Proposed § 49.22(e)(1) would replace this requirement with a more targeted requirement to describe and assess the effectiveness of SDR policies and procedures designed to reasonably ensure compliance with the Act and applicable Commission regulations. Based on its experience in reviewing annual compliance reports, the Commission believes this more targeted requirement would focus on the most important and useful information in the annual compliance report and reduce the burden on SDRs in creating the assessment for the annual compliance report without any detrimental effects on SDR compliance or the Commission's ability to perform its oversight functions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>144</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.22(e)(2).
                        </P>
                    </FTNT>
                    <P>The Commission notes that it would also have the ability to request copies of any SDR policies and procedures and to request a demonstration of compliance with any SDR obligations under the Act or Commission regulations under proposed § 49.29.</P>
                    <P>The Commission also believes that multiple proposed changes to § 49.22(f) would simplify requirements and reduce compliance burdens on SDRs related to submitting the annual compliance reports. The proposed amendments would remove the requirement to record the submission of the annual compliance report and any subsequent discussion of the report in the board minutes (proposed § 49.22(f)(1)) as this requirement would be incorporated into the general recordkeeping requirement in proposed § 49.22(g); extend the time to submit the annual compliance report to the Commission from 60 to 90 days (proposed § 49.22(f)(2)) in recognition that the CCO has to prepare other year-end reports, such as the fourth quarter financial report; and allow reasonable requests for additional time to file an annual compliance report to be granted (proposed § 49.22(f)(4)) to provide more flexibility. Each of these amendments would simplify requirements or reduce compliance burdens on SDRs, without any substantial effect on the Commission's ability to oversee SDRs.</P>
                    <P>
                        Finally, the Commission notes that the proposed changes to § 49.22(g) would simplify the wording of the recordkeeping requirement by removing the lengthy examples of records to be kept.
                        <SU>145</SU>
                        <FTREF/>
                         This proposed change does not, however, in any way limit the records that must be preserved under proposed § 49.22(g). All of the records listed in current § 49.22(g) would still be required to be kept pursuant to proposed § 49.22(g) and proposed § 49.12(b)(1), along with any other qualifying records that are not listed.
                    </P>
                    <FTNT>
                        <P>
                            <SU>145</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.22(g).
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of the proposed amendments to § 49.22. The Commission also invites specific comment on the following:
                    </P>
                    <P>(20) Has the § 49.22(b)(2)(ii) prohibition on a CCO also serving as an SDR's general counsel or as a member of the SDR's legal department presented SDRs with any challenges or raised concerns that could be fixed by a change to the prohibition?</P>
                    <P>(21) Does proposed § 49.22(d)(2) provide CCOs with sufficient clarity as to the conflicts of interest that are within the scope of their responsibilities under the proposed rule?</P>
                    <P>(22) Does proposed § 49.22(d)(2) provide CCOs with sufficient authority to resolve any conflicts of interest that may arise as required by section 21(e)(2)(C) of the Act?</P>
                    <HD SOURCE="HD3">P. § 49.24—System Safeguards</HD>
                    <P>The Commission proposes to make non-substantive amendments to § 49.24. Current § 49.24(d) governs SDR BC-DR plans, resources, and procedures. The proposed amendments to § 49.24 provide more detail as to the duties and obligations that SDRs must fulfill by expanding the non-exhaustive list of duties and obligations to include specific reference to §§ 49.10 to 49.21, § 49.23, and §§ 49.25 to 49.27. The Commission emphasizes that this list is provided merely for clarity purposes and would not in any way excuse any SDR from any of the duties and obligations included in other sections of the Commission's regulations. As the duties and obligations of these sections currently apply to SDRs and would continue to apply to SDRs, this non-substantive change would not affect the requirements applicable to SDRs.</P>
                    <P>The Commission also proposes to make technical amendments to § 49.24(i), to remove a reference to § 45.2. As described above in section II.H, the Commission is moving the SDR recordkeeping requirements contained in current § 45.2(f) and (g) to § 49.12 for consistence and clarity purposes. This proposed technical change would conform § 49.24(i) to the proposed changes to § 45.2 and § 49.12, but would not change any of the requirements applicable to SDRs.</P>
                    <HD SOURCE="HD3">Q. § 49.25—Financial Resources</HD>
                    <P>As discussed above in section II.E, the Commission proposes conforming changes to § 49.25 to remove the reference to § 49.9 and to core principle obligations identified in § 49.19. Proposed § 49.25(a) would instead refer to SDR obligations under “this chapter,” to be broadly interpreted as any regulatory or statutory obligation specified in part 49. These technical changes do not impact existing obligations on SDRs.</P>
                    <P>The Commission is proposing one specific change to § 49.25(f)(3). Current § 49.25(f)(3) requires SDRs to submit their financial resources reports no later than 17 business days after the end of the SDR's fiscal quarter, or a later time that the Commission permits upon request. The Commission is proposing to amend § 49.25(f)(3) to extend the time SDRs have to submit their quarterly financial resources reports to not later than 40 calendar days after the end of the SDR's first three fiscal quarters, and not later than 90 calendar days after the end of the SDR's fourth fiscal quarter, or such later time as the Commission may permit in its discretion.</P>
                    <P>
                        The Commission believes aligning the 90 calendar day deadline with the amended timeframe for SDRs submitting CCO reports in § 49.22(f)(2) 
                        <SU>146</SU>
                        <FTREF/>
                         would help SDRs in planning their yearly compliance obligations.
                    </P>
                    <FTNT>
                        <P>
                            <SU>146</SU>
                             Discussed above in section II.O.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of the proposed amendments to § 49.25.
                    </P>
                    <HD SOURCE="HD3">R. § 49.26—Disclosure Requirements of Swap Data Repositories</HD>
                    <P>The Commission proposes to amend § 49.26 to conform defined terms with the proposed amendments to § 49.2 discussed above in section II.A. The Commission also proposes to make updates to the introductory paragraph of § 49.26 to reflect updates to the terms “SDR data,” “registered swap data repository,” and “reporting entity.” Current § 49.26 requires SDRs to furnish SEFs, DCMs, and reporting counterparties with an SDR disclosure document that sets forth the risks and costs associated with using the services of the SDR, and contains the information enumerated in § 49.26(a) through (i). These non-substantive amendments would not change the current requirements of § 49.26.</P>
                    <P>
                        The Commission also proposes to add new § 49.26(j), which would require that the SDR disclosure document set forth the SDR's policies and procedures regarding the reporting of SDR data to the SDR, including the SDR data validation procedures, swap data verification procedures, and procedures 
                        <PRTPAGE P="21064"/>
                        for correcting SDR data errors and omissions.
                    </P>
                    <P>The Commission believes that § 49.26(j) would assist market participants with acquiring information regarding SDR operations that would help inform their decision-making in regards to choosing which SDRs to use for swaps reporting. Disclosing the SDR data reporting policies and procedures, the SDR data validation procedures, the swap data verification procedures, and the SDR data correction procedures would also increase data quality by helping reduce the number of data errors and omissions by providing the SEFs, DCMs, and reporting counterparties with the information needed to properly design their reporting systems before any reporting occurs. The Commission notes that the requirements to provide the policies and procedures for reporting, validations, verification, and corrections would apply for all SDR data to be reported, as applicable.</P>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of proposed § 49.26. The Commission also invites specific comment on the following:
                    </P>
                    <P>(23) Should the Commission require any other specific information be disclosed by SDRs to facilitate market participants' informed decision making? If so, please describe what other information should be disclosed and why. Please be specific.</P>
                    <HD SOURCE="HD3">S. § 49.28—Operating Hours of Swap Data Repositories</HD>
                    <P>The Commission is proposing to add new § 49.28 to provide more detail on SDRs' responsibilities with respect to hours of operation. The proposed amendments reflect the Commission's belief that SDRs should operate as continuously as possible while still being afforded the opportunity to perform necessary testing, maintenance, and upgrades of their systems.</P>
                    <HD SOURCE="HD3">1. General Requirements—§ 49.28(a)</HD>
                    <P>Proposed § 49.28(a) would require an SDR to have systems in place to continuously accept and promptly record all SDR data reported to the SDR, and, as applicable, publicly disseminate all swap transaction and pricing data reported to the SDR as required under part 43.</P>
                    <P>
                        Proposed § 49.28(a)(1) would allow an SDR to establish normal closing hours to perform system maintenance during periods when, in the SDR's reasonable estimation, the SDR typically receives the least amount of SDR data.
                        <SU>147</SU>
                        <FTREF/>
                         Under proposed § 49.28(a)(1), an SDR would also have to provide reasonable advance notice of its normal closing hours to market participants and to the public.
                    </P>
                    <FTNT>
                        <P>
                            <SU>147</SU>
                             The Commission notes that this would be a minor change from the existing requirements of § 43.3(f)(2), which prescribes that SDRs avoiding scheduling closing hours during the time when the SDR reasonably estimates that the swaps markets are most active. The Commission believes times when SDRs receive less SDR data would be a better measure of when to schedule normal closing hours for SDRs.
                        </P>
                    </FTNT>
                    <P>Proposed § 49.28(a)(2) would allow an SDR to declare, on an ad hoc basis, special closing hours to perform system maintenance that cannot wait until normal closing hours. Similar to proposed § 49.28(a)(1), proposed § 49.28(a)(2) instructs SDRs to schedule special closing hours during periods when, in the SDR's reasonable estimation, the special closing hours would, to the extent possible given the circumstances prompting the special closing hours, be least disruptive to the SDR's SDR data reporting responsibilities. Proposed § 49.28(a)(2) would also require the SDRs to provide reasonable advance notice of the special closing hours to market participants and the public whenever possible, and, if advance notice is not reasonably possible, to give notice to the public as soon as is reasonably possible after declaring special closing hours.</P>
                    <P>
                        Current § 43.3(f) regulates the hours during which SDRs that accept and publicly disseminate swap transaction and pricing data must operate. Current § 43.3(f) reflects the Commission's beliefs that the global nature of the swaps market requires that SDRs be able to publicly disseminate swap transaction and pricing data at all times and that SDRs that publicly disseminate swap transaction and pricing data should generally be fully operational 24 hours a day, 7 days a week.
                        <SU>148</SU>
                        <FTREF/>
                         While the Commission strongly encourages SDRs to adopt redundant systems to allow public reporting during closing hours, current § 43.3(f) allows SDRs to schedule downtime to perform system maintenance. Current § 43.3(g) addresses SDRs' obligations regarding swap transaction and pricing data sent to an SDR for publicly reportable swap transactions during closing hours.
                    </P>
                    <FTNT>
                        <P>
                            <SU>148</SU>
                             
                            <E T="03">See</E>
                             Real-Time Public Reporting of Swap Transaction Data, 77 FR 1182, 1204 (Jan. 9, 2012) (The Commission agrees that the global nature of the swaps market requires that an SDR be able to publicly disseminate swap transaction and pricing data at all times and believes that SDRs that publicly disseminate swap transaction and pricing data should be fully operational 24 hours a day, 7 days a week.).
                        </P>
                    </FTNT>
                    <P>The Commission proposes to include the requirements of current § 43.3(f) and § 43.3(g) in proposed § 49.28 and to expand the operating hours requirement beyond public reporting of swap transaction and pricing data to also explicitly include fulfilling an SDR's responsibilities under parts 45, 46, and 49. This proposed change is intended to make clear that the obligations of SDRs to operate near continuously is not limited to the receipt and dissemination of swap transaction and pricing data pursuant to part 43, but instead SDRs must be able to continuously perform all of their data-related responsibilities required under the Commission's regulations.</P>
                    <P>
                        The Commission also believes that it would help SDRs and market participants to move all SDR operating hours requirements to part 49. The proposed requirements discussed above would also include many of the requirements of the SEC's operating hours regulations governing SBSDRs to increase consistency between the regulations for SDRs and SBSDRs.
                        <SU>149</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>149</SU>
                             The SEC's operating hours regulations are contained in 17 CFR 242.904. While current § 43.3(f) allows SDRs to schedule closing hours while avoiding the times that, in an SDR's estimation, U.S. markets and major foreign markets are most active, and requires the SDRs to provide advance notice of closing hours to market participants and the public, current § 43.3(f) does not make a distinction between regular closing hours and special closing hours. The distinction is present, however, in operating hours requirements for SBSDRs, and proposed § 49.28(a)(1)-(2) would largely adopt the SBSDR requirement. These requirements would make clear that an SDR may establish both normal and special closing hours and would allow an SDR that also registers with the SEC as an SBSDR to effectively follow the same operating hours requirements.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Part 40 Requirement for Closing Hours—§ 49.28(b)</HD>
                    <P>
                        Proposed § 49.28(b) would require SDRs to comply with the requirements under part 40 of the Commission's regulations when adopting or amending normal closing hours and special closing hours.
                        <SU>150</SU>
                        <FTREF/>
                         The Commission anticipates that, due to the unexpected and emergency nature of special closing hours, rule filings related to special closing hours would typically qualify for the emergency rule certification provisions of § 40.6(a)(6).
                        <SU>151</SU>
                        <FTREF/>
                         This requirement is already applicable to SDRs pursuant to current § 43.3(f)(3).
                        <SU>152</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>150</SU>
                             Closing hours would be considered “rules” for the purposes of part 40 requirements. 
                            <E T="03">See</E>
                             17 CFR 40.1, 
                            <E T="03">et. seq.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>151</SU>
                             
                            <E T="03">See</E>
                             17 CFR 40.6(a)(6) (containing the requirements for establishing standards for responding to an emergency and for emergency rule filings); 
                            <E T="03">see also</E>
                             17 CFR 40.1(h) (defining “emergency” for the purposes of part 40).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>152</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.3(f)(3) (A registered swap data repository shall comply with the requirements under part 40 of this chapter in setting closing hours and shall provide advance notice of its 
                            <PRTPAGE/>
                            closing hours to market participants and the public.).
                        </P>
                    </FTNT>
                    <PRTPAGE P="21065"/>
                    <HD SOURCE="HD3">3. Acceptance of SDR Data During Closing Hours—§ 49.28(c)</HD>
                    <P>
                        Proposed § 49.28(c) would require an SDR to have the capability to accept and hold in queue any and all SDR data reported to the SDR during normal closing hours and special closing hours. The Commission believes this requirement would help to avoid the loss of any SDR data that is reported to an SDR during closing hours and to facilitate the SDR's prompt fulfillment of its data reporting responsibilities, including public dissemination of swap transaction and pricing data, as applicable, once the SDR reopens from closing hours. Proposed § 49.28(c) would expand the similar existing requirements for swap transaction and pricing data in § 43.3(g)
                        <SU>153</SU>
                        <FTREF/>
                         to all SDR data and would largely follow the SBSDR requirements to receive and hold in queue information regarding security-based swaps.
                        <SU>154</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>153</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.3(g) (During closing hours, a registered swap data repository shall have the capability to receive and hold in queue any data regarding publicly reportable swap transactions pursuant to this part.).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>154</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.904(c) (During normal closing hours, and to the extent reasonably practicable during special closing hours, a registered security-based swap data repository shall have the capability to receive and hold in queue information regarding security-based swaps that has been reported pursuant to §§ 242.900 through 242.909.).
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.28(c)(1) would require an SDR, on reopening from normal or special closing hours, to promptly process all SDR data received during the closing hours and, pursuant to part 43, to publicly disseminate swap transaction and pricing data reported to the SDR that was held in queue during the closing hours. Proposed § 49.28(c)(1) would expand the similar existing requirements for the SDRs to disseminate swap transaction and pricing data pursuant to § 43.3(g)(1) 
                        <SU>155</SU>
                        <FTREF/>
                         to also include the prompt processing of all other SDR data received and held in queue during closing hours. The proposed requirements would also largely follow the SBSDR requirements for disseminating transaction reports after reopening following closing hours.
                        <SU>156</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>155</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.3(g)(1) (Upon reopening after closing hours, a registered swap data repository shall promptly and publicly disseminate the swap transaction and pricing data of swaps held in queue, in accordance with the requirements of this part.).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>156</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.904(d) (When a registered security-based swap data repository re-opens following normal closing hours or special closing hours, it shall disseminate transaction reports of security-based swaps held in queue, in accordance with the requirements of § 242.902.).
                        </P>
                    </FTNT>
                    <P>The Commission believes SDR closing hours should disrupt the data reporting process as little as possible, and therefore believes that the SDRs should be responsible for receiving, holding, and then disseminating SDR data as required, as opposed to disrupting the reporting systems of SEFs, DCMs, and reporting counterparties.</P>
                    <P>
                        Proposed § 49.28(c)(2) would require SDRs to immediately issue notice to all SEFs, DCMs, reporting counterparties, and the public in the event that an SDR is unable to receive and hold in queue any SDR data reported during normal closing hours or special closing hours. Proposed § 49.28(c)(2) would also require SDRs to issue notice to all SEFs, DCMs, reporting counterparties, and the public that the SDR has resumed normal operations immediately on reopening.
                        <SU>157</SU>
                        <FTREF/>
                         Proposed § 49.28(c)(2) would then require a SEF, DCM, or reporting counterparty that was not able to report SDR data to an SDR because of the SDR's inability to receive and hold in queue any SDR data to immediately report the SDR data to the SDR.
                    </P>
                    <FTNT>
                        <P>
                            <SU>157</SU>
                             Consistent with the current requirements under part 43, an SDR may issue such notices to its participants and the public by publicizing the notices that the SDR is unable to receive and hold in queue any SDR data and that the SDR has resumed normal operations in a conspicuous place on the SDR's website. 
                            <E T="03">See</E>
                             77 FR at 1205, n. 208 (allowing SDRs to provide reasonable advance notice of its closing hours to participants and the public by providing notices directly to its participants or publicizing its closing hours in a conspicuous place on its website).
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.28(c)(2) would expand the similar existing requirements for swap transaction and pricing data in § 43.3(g)(2) 
                        <SU>158</SU>
                        <FTREF/>
                         to all SDR data and would largely follow the SBSDR requirements to receive and hold in queue information regarding security-based swaps.
                        <SU>159</SU>
                        <FTREF/>
                         The Commission emphasizes that it would expect SDRs to be able to accept and hold in queue SDR data that is reported during closing hours. The inability to accept and hold in queue SDR data would need to be a rare occurrence that results from unanticipated emergency situations. The provisions in § 49.28(c)(2) would only be included as a last resort to prevent data loss.
                    </P>
                    <FTNT>
                        <P>
                            <SU>158</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.3(g)(2) (If at any time during closing hours a registered swap data repository is unable to receive and hold in queue swap transaction and pricing data pursuant to this part, then the registered swap data repository shall immediately upon reopening issue notice that it has resumed normal operations. Any registered swap execution facility, designated contract market or reporting party that is obligated under this section to report data to the registered swap data repository shall report the data to the registered swap data repository immediately after receiving such notice.).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>159</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.904(e) (If a registered security-based swap data repository could not receive and hold in queue transaction information that was required to be reported pursuant to §§ 242.900 through 242.909, it must immediately upon re-opening send a message to all participants that it has resumed normal operations. Thereafter, any participant that had an obligation to report information to the registered security-based swap data repository pursuant to §§ 242.900 through 242.909, but could not do so because of the registered security-based swap data repository's inability to receive and hold in queue data, must promptly report the information to the registered security-based swap data repository.).
                        </P>
                    </FTNT>
                    <P>Though proposed § 49.28 would apply to all SDR data, as opposed to only swap transaction and pricing data reported pursuant to part 43, the Commission believes that proposed § 49.28 would have little impact on the operations of SDRs. Proposed § 49.28 largely encompasses the requirements of current § 43.3(f) and (g), which already apply to SDRs, and the sections that largely conform to SEC regulations governing SBSDRs would allow an SDR that also registers with the SEC as an SBSDR to effectively comply with one set of regulations. The Commission also understands that SDRs currently routinely receive and hold in queue all SDR data submitted during declared SDR closing hours, regardless of whether that data is being submitted pursuant to part 43 or another Commission regulation. As a result, the Commission believes that expanding the operating hours requirements to all SDR data would have little practical impact on current SDR operations.</P>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of proposed § 49.28. The Commission also invites specific comment on the following:
                    </P>
                    <P>(24) Does proposed § 49.28 provide SDRs sufficient flexibility to conduct necessary maintenance on their electronic systems while still facilitating the availability of SDR data for the Commission and the public? Please be specific.</P>
                    <HD SOURCE="HD2">T. § 49.29—Information Relating to Swap Data Repository Compliance</HD>
                    <P>The Commission is proposing to add new § 49.29 to provide for information requests from the Commission to SDRs regarding information the Commission needs to perform its duties and regarding SDR compliance with regulatory duties and core principles.</P>
                    <P>
                        Proposed § 49.29(a) would require SDRs, upon request by the Commission, to file certain information related to its business as an SDR or other such information as the Commission determines to be necessary or appropriate for the Commission to perform its regulatory duties. The SDRs would be required to provide the requested information in the form and 
                        <PRTPAGE P="21066"/>
                        manner and within the time specified by the Commission in its request.
                    </P>
                    <P>Proposed § 49.29(b) would require SDRs, upon request by the Commission, to demonstrate compliance with their obligations under the CEA and Commission regulations, as specified in the request. The Commission notes that the requests may include, but are not limited to, demonstrating compliance with the core principles applicable to SDRs under section 21(f) of the CEA and part 49. SDRs would be required to provide the requested information in the form and manner and within the time specified by the Commission in its request.</P>
                    <P>
                        The Commission notes that these requests may be made for any Commission oversight purpose. For example, the Commission may request SDRs to provide information relating to their operations or their practices in connection with their compliance with particular regulatory duties and core principles, other conditions of their registration, or in connection with the Commission's general oversight responsibilities under the CEA. Proposed § 49.29 is based on existing Commission requirements applicable to SEFs and DCMs.
                        <SU>160</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>160</SU>
                             
                            <E T="03">See, e.g.,</E>
                             17 CFR 37.5 and 38.5.
                        </P>
                    </FTNT>
                    <P>The Commission notes that proposed § 49.29 facilitates the removal of the requirement for annual Form SDR updates from § 49.3(a)(5), as the Commission would be able to request the same information that would be contained in Form SDR and its exhibits as needed without the need for a regular full Form SDR update.</P>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of proposed § 49.29.
                    </P>
                    <HD SOURCE="HD2">U. § 49.30—Form and Manner of Reporting and Submitting Information to the Commission</HD>
                    <P>The Commission is proposing to add new § 49.30 to place the various requirements for form and manner requests to SDRs from the Commission in one section. The proposed changes to part 49 of the Commission's regulations set forth in this proposal contain various regulatory provisions that would require SDRs to provide reports and other information to the Commission in “the form and manner” requested or directed by the Commission. In particular, proposed §§ 49.13(a) and 49.29 would require SDRs to provide reports and certain other information to the Commission in the “form and manner” requested or directed by the Commission.</P>
                    <P>Proposed § 49.30 would establish the broad parameters of the “form and manner” requirement. Unless otherwise instructed by the Commission, an SDR would have to submit SDR data reports and any other information required under part 49 to the Commission, within the time specified, using the format, coding structure, and electronic data transmission procedures approved in writing by the Commission. The “form and manner” requirement proposed in § 49.30 would not supplement or expand upon existing substantive provisions of part 49, but instead, would only allow the Commission to specify how existing information reported to, and maintained by, SDRs should be formatted and delivered to the Commission.</P>
                    <P>
                        Proposed § 49.30 provides that the Commission would specify, in writing, the format, coding structure, and electronic data transmission procedures for various reports and submissions that are required to be provided to the Commission under part 49. The Commission notes that these written instructions would include the most recent, and any future, “guidebooks” or other technical specifications published on the Commission's website, as applicable.
                        <SU>161</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>161</SU>
                             The Commission's current published “guidebooks” include those published for reporting required by parts 15, 16, 17, 18, and 20 of the Commission's regulations relating to ownership and control reports, large traders reports, and data reporting. These guidebooks are available on the Commission's website at 
                            <E T="03">http://www.cftc.gov/Forms/index.htm.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of proposed § 49.30. The Commission also invites specific comment on the following:
                    </P>
                    <P>(25) Should the Commission provide a single format or coding structure for each SDR to deliver reports and other information in a consistent manner? Are existing standards and formats sufficient for providing the Commission with requested information? Please explain why or why not.</P>
                    <P>(26) Should the Commission require specific electronic data transmission methods and/or protocols for SDRs to disseminate reports and other information to the Commission? Please explain why or why not.</P>
                    <HD SOURCE="HD2">V. § 49.31—Delegation of Authority to the Director of the Division of Market Oversight Relating to Certain Part 49 Matters</HD>
                    <P>The Commission is proposing to add new § 49.31 to consolidate delegations of authority for part 49. Current part 49 and many amendments to part 49 proposed in this release include provisions that require SDRs to perform various functions at the request of the Commission or to provide information as prescribed by the Commission or as instructed by the Commission. The Commission proposes to delegate the authority to exercise most of the listed part 49 functions to the Director of DMO to facilitate the Commission's ability to respond to changes in the swaps market and technological developments, and to ensure the Commission's ability to quickly and efficiently access information and data from the SDRs in order to efficiently fulfill its market surveillance responsibilities and other regulatory obligations.</P>
                    <P>The Commission is proposing to delegate the functions in the below current and proposed regulations to the Director of DMO, and to such members of the Commission's staff acting under his or her direction as he or she may see fit from time to time.</P>
                    <P>
                        Proposed § 49.31(a)(1) would delegate to the Director of DMO the authority to request documentation related to an SDR equity interest transfer pursuant to § 49.5.
                        <SU>162</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>162</SU>
                             
                            <E T="03">See</E>
                             section II.C above.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.31(a)(2) would delegate to the Director of DMO the authority to instruct SDRs on how to transmit open swaps reports to the Commission pursuant to § 49.9.
                        <SU>163</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>163</SU>
                             
                            <E T="03">See</E>
                             section II.E above.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.31(a)(3) would delegate to the Director of DMO the authority to modify the requirement for an SDR to accept all data from all swaps in an asset class once the SDR includes the asset class in its application for registration pursuant to § 49.10.
                        <SU>164</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>164</SU>
                             
                            <E T="03">See</E>
                             section II.F above.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.31(a)(4) would delegate to the Director of DMO the authority to request records pursuant to § 49.12.
                        <SU>165</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>165</SU>
                             
                            <E T="03">See</E>
                             section II.H above.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.31(a)(5) would delegate to the Director of DMO the authority to request SDRs monitor, screen, and analyze SDR data pursuant to § 49.13.
                        <SU>166</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>166</SU>
                             
                            <E T="03">See</E>
                             section II.I above.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.31(a)(6) would delegate to the Director of DMO the authority to request SDRs disclose aggregated SDR data in the form and manner prescribed by the Commission pursuant to § 49.16.
                        <SU>167</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>167</SU>
                             
                            <E T="03">See</E>
                             section II.K above.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.31(a)(7) would delegate to the Director of DMO the authority to prescribe the form of direct electronic access that SDRs make available to the Commission, prescribe the format by which SDRs maintain SDR data, to request SDRs transmit SDR data to the 
                        <PRTPAGE P="21067"/>
                        Commission, and to instruct SDRs on transmitting SDR data to the Commission pursuant to § 49.17.
                        <SU>168</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>168</SU>
                             
                            <E T="03">See</E>
                             section II.L above.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.31(a)(8) would delegate to the Director of DMO the authority to permit SDRs to accept alternative forms of confidentiality arrangements and the ability to direct SDRs to limit, suspend, or revoke access to swap data pursuant to § 49.18.
                        <SU>169</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>169</SU>
                             
                            <E T="03">See</E>
                             section II.M above.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.31(a)(9) would delegate to the Director of DMO the authority to grant extensions to the annual compliance report deadline pursuant to § 49.22.
                        <SU>170</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>170</SU>
                             
                            <E T="03">See</E>
                             section II.O above.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.31(a)(10) would delegate to the Director of DMO the authority to require SDRs to exercise emergency authority or provide the documentation underlying an SDR's decision to exercise its emergency authority pursuant to § 49.23.
                        <SU>171</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>171</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.23.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.31(a)(11) would delegate to the Director of DMO the authority to determine an SDR to be a “critical SDR” and to request copies of BC-DR books and records, assessments, test results, plans, and reports pursuant to § 49.24.
                        <SU>172</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>172</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.24.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.31(a)(12) would delegate to the Director of DMO the authority to determine the amount, value, and types of financial resources SDRs must maintain to perform their statutory duties set forth in part 49 and request reports of financial resources pursuant to § 49.25.
                        <SU>173</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>173</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.25.
                        </P>
                    </FTNT>
                    <P>
                        Similar to provisions relating to demonstrations of compliance by SEFs,
                        <SU>174</SU>
                        <FTREF/>
                         proposed § 49.31(a)(13) would delegate to the Director of DMO the authority to request information from SDRs related to their business as SDRs or information the Commission determines is necessary or appropriate to perform its statutory and regulatory responsibilities in the form and manner specified by the Commission, as well as written demonstrations of compliance by in the form and manner specified by the Commission pursuant to § 49.29.
                        <SU>175</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>174</SU>
                             
                            <E T="03">See</E>
                             17 CFR 37.5 (containing requirements for demonstrations of compliance by SEFs and delegating the authority contained in the section to the Director of DMO).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>175</SU>
                             
                            <E T="03">See</E>
                             section II.T above.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.31(a)(14) would delegate to the Director of DMO the authority to establish such format, coding structure, and electronic data transmission procedures for SDR data reports and any other information required by the Commission under part 49 pursuant to § 49.30.
                        <SU>176</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>176</SU>
                             
                            <E T="03">See</E>
                             section II.U above.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">III. Proposed Amendments to Part 45</HD>
                    <HD SOURCE="HD2">A. § 45.2—Swap Recordkeeping</HD>
                    <P>
                        The Commission is proposing a non-substantive change to remove current § 45.2(f) and (g). Current § 45.2 lists the general recordkeeping requirements of part 45, with § 45.2(f) and (g) applying specifically to SDRs.
                        <SU>177</SU>
                        <FTREF/>
                         Current § 45.2(f) contains the SDR recordkeeping requirements and current § 45.2(g) includes the SDR record retention requirements.
                    </P>
                    <FTNT>
                        <P>
                            <SU>177</SU>
                             
                            <E T="03">See generally</E>
                             17 CFR 45.2.
                        </P>
                    </FTNT>
                    <P>
                        Part 45 generally focuses on duties to report swap data to SDRs, while part 49 addresses obligation of SDRs. Part 49 is therefore the more logical location for SDR recordkeeping requirements. As described above, the Commission is proposing to expand on the SDR recordkeeping requirements in § 49.12, which includes incorporating the requirements of current § 45.2(f) and (g), among other amendments.
                        <SU>178</SU>
                        <FTREF/>
                         Current § 45.2(f) and (g) would be redundant, as their provisions are subsumed in proposed § 49.12, and keeping the paragraphs in part 45 could cause confusion as to the recordkeeping requirements that apply to SDRs. The Commission notes that all of the actual requirements contained in current § 45.2(f) and (g) would continue to apply to SDRs, because the requirements are included in proposed § 49.12.
                    </P>
                    <FTNT>
                        <P>
                            <SU>178</SU>
                             
                            <E T="03">See</E>
                             section II.H above.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. § 45.14—Verification of Swap Data Accuracy and Correcting Errors and Omissions in Swap Data</HD>
                    <P>The Commission is proposing to amend § 45.14 to facilitate the verification of swap data by reporting counterparties and to simplify and improve the requirements for correcting errors and omissions in swap data previously reported or erroneously not reported as required by Commission regulations. As discussed above in section II.G, the Commission is also amending the SDRs' responsibilities to verify the accuracy and completeness of swap data reported to SDRs. The Commission believes that revised § 49.11 and proposed § 45.14(b) would provide SDRs, swap counterparties, SEFs, and DCMs with a clear understanding of their respective responsibilities in having errors or omissions in swap data corrected.</P>
                    <HD SOURCE="HD3">1. Verification of Swap Data Accuracy to a Swap Data Repository—§ 45.14(a)</HD>
                    <P>The Commission is proposing to move the requirements in current § 45.14(a) to § 45.14(b). In its place, the Commission is proposing the new requirements for reporting counterparties to verify swap data.</P>
                    <P>
                        Proposed § 45.14(a) would generally require that reporting counterparties verify the accuracy and completeness of swap data for swaps for which they are the reporting counterparty.
                        <SU>179</SU>
                        <FTREF/>
                         Proposed § 45.14(a)(1) would require that a reporting counterparty reconcile its internal books and records for each open swap for which it is the reporting counterparty with every open swaps report provided to the reporting counterparty by an SDR pursuant to proposed § 49.11. Proposed § 45.14(a)(1) would further require that reporting counterparties conform to the swap data verification policies and procedures created by an SDR pursuant to proposed § 49.11.
                    </P>
                    <FTNT>
                        <P>
                            <SU>179</SU>
                             This paragraph is the counterpart to the verification requirements for SDRs contained in proposed § 49.11. 
                            <E T="03">See</E>
                             section II.G above. The SDRs would provide their verification policies and procedures to their users and potential users pursuant to proposed § 49.26(j).
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 45.14(a)(2) would require that reporting counterparties submit either a verification of data accuracy or a notice of discrepancy in response to every open swaps report received from an SDR within the following timeframes: (i) 48 hours of the SDR providing the open swaps report if the reporting counterparty is an SD, MSP, or DCO; or (ii) 96 hours of the SDR providing the open swaps report for non-SD/MSP/DCO reporting counterparties.
                        <SU>180</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>180</SU>
                             As explained above in section II.G, non-SD/MSP/DCO reporting counterparties tend to be entities that are less active in the swaps markets and tend to have fewer resources that can be devoted to regulatory compliance, including verification systems, than would be expected for a larger registered entity such as an SD, MSP, or DCO. The Commission believes that requiring non-SD/MSP/DCO reporting counterparties to respond to an open swaps report within 96 hours would fulfill the Commission's needs to have swap data verified (and corrected, as needed) while also minimizing the burden on these reporting counterparties in a way that does not compromise swap data or the Commission's ability to perform its regulatory functions.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 45.14(a)(3) would require that, if a reporting counterparty finds no discrepancies between the accurate and current swap data for a swap according to the reporting counterparty's internal books and records and the swap data for the swap contained in the open swaps report provided by the SDR, the reporting counterparty submit a verification of data accuracy indicating 
                        <PRTPAGE P="21068"/>
                        that the swap data is complete and accurate to the SDR in the form and manner required by the SDR's swap data verification policies and procedures created pursuant to § 49.11.
                    </P>
                    <P>Finally, proposed § 45.14(a)(4) would require that, if a reporting counterparty finds any discrepancy between the accurate and current swap data for a swap according to the reporting counterparty's internal books and records and the swap data for the swap contained in the open swaps report provided by the SDR, including, but not limited to, any over-reporting or under-reporting of swap data for any swap, the reporting counterparty submit a notice of discrepancy to the SDR in the form and manner required by the SDR's swap data verification policies and procedures created pursuant to § 49.11.</P>
                    <P>The Commission is proposing the new verification rules in § 45.14(a) to help improve swap data quality by facilitating the resolution of any discrepancies between the reporting counterparties' records of their open swaps and the swap data maintained by an SDR. The Commission believes the most effective way to accomplish verification is by having reporting counterparties compare their own records for each open swap as of the moment captured in the open swaps report with the swap data included for each swap in an open swaps report. The Commission believes that these requirements would help ensure that reporting counterparties perform the reconciliation promptly and provide a response to the SDR, which would ensure that swap data is reviewed in a timely manner and that SDRs can fulfill their verification responsibilities under proposed § 49.11.</P>
                    <P>
                        The Commission notes that a reporting counterparty would be required to perform this reconciliation for every open swap included in each open swaps report provided to the reporting counterparty by any SDR.
                        <SU>181</SU>
                        <FTREF/>
                         The Commission also notes that not receiving an expected open swaps report from an SDR that the reporting counterparty believes maintains swap data for open swaps for which it is the reporting counterparty would constitute an error or omission that the reporting counterparty must correct with the SDR pursuant to proposed § 45.14(b). Likewise, receiving an open swaps report for swaps that are no longer open would also constitute an error that would require correction under proposed § 45.14(b).
                    </P>
                    <FTNT>
                        <P>
                            <SU>181</SU>
                             The SDRs would provide open swaps reports to the individual reporting counterparties in accordance with the frequency and timing requirements included in proposed § 49.11. An entity would only be required to verify the accuracy and completeness of swap data for open swaps to which it is the reporting counterparty, such that if a reporting counterparty did not have any open swaps with an SDR, it would not receive an open swaps report from that SDR and would not be required to verify swap data with that SDR.
                        </P>
                    </FTNT>
                    <P>The Commission also notes that for all reporting counterparties the timing requirement of proposed § 45.14(a) is based on when the SDR makes the open swaps report available to the reporting counterparty, not when the reporting counterparty receives or accesses the open swaps report. A reporting counterparty's failure to receive or access, and analyze, an open swaps report that was properly provided by an SDR would not excuse the reporting counterparty from the requirements of proposed § 45.14(a). This standard would help ensure that reporting counterparties maintain properly functioning systems for the timely receipt and review of open swaps reports that conform to SDR verification policies and procedures.</P>
                    <P>The Commission is not proposing a form or manner for the verification of data accuracy in proposed § 45.14(a)(3) or the notice of discrepancy in proposed § 45.14(a)(4), but is instead proposing that the reporting counterparty provide a verification or notice that meets the requirements of the SDR's verification policies and procedures created pursuant to § 49.11. This requirement would help ensure that reporting counterparties provide verifications of data accuracy or notices of discrepancy to the SDRs that the SDRs can use to complete the verification process. As reporting counterparties already report information to SDRs under other Commission regulations, the Commission expects that SDRs and reporting counterparties would work together to design the method for submitting verifications and notifications that is the most efficient and convenient for both parties, with particular attention to creating a system that is not unnecessarily burdensome for non-SD/MSP/DCO reporting counterparties.</P>
                    <P>The Commission notes that the notice of discrepancy is not the means by which the reporting counterparty would correct errors or omissions in swap data. The process of error correction would be governed by proposed § 45.14(b), as discussed below. The notice of discrepancy would merely be a notice that the reporting counterparty does not believe that one or more elements of swap data contained, or missing, in the open swaps report are correct. Finding any discrepancy in the swap data would however prompt a reporting counterparty's responsibility to correct all discrepancies in the swap data pursuant to proposed § 45.14(b).</P>
                    <P>The Commission emphasizes the importance of robust and thorough verification processes under proposed § 45.14(a). For clarity, examples of unsatisfactory verification would include, but are not limited to: (i) Failure to perform the verification in a timely manner as required by proposed § 45.14(a); and (ii) providing a verification of data accuracy indicating that the swap data was complete and accurate for swap data that was not correct when verified. The Commission would consider any error or omission that reasonably could have been discovered during the verification process to have been discovered by the reporting counterparty, and therefore providing a verification of data accuracy in response to an open swaps report that contains an error or omission would not comply with the proposed requirements. The Commission also notes that each incorrect verification, including the failure to recognize the same error or omission in swap data over time and allowing the error or omission to persist over multiple open swaps reports and verifications, would also not comply with the proposed requirements.</P>
                    <P>Finally, the Commission expects that a reporting counterparty repeatedly discovering errors or omissions in the open swaps reports, especially if there is a discernable pattern in the errors or omissions, would prompt the reporting counterparty to evaluate its reporting systems to discover any potential systemic errors or omissions, including working with the SDR to improve its data reporting, as needed. The Commission notes that a pattern of failures may implicate other requirements for further action and disclosure of non-compliance by registered entities, such as SDs, MSPs, SEFs, DCMs, or DCOs.</P>
                    <HD SOURCE="HD3">2. Corrections of Errors and Omissions in Swap Data—§ 45.14(b)</HD>
                    <P>
                        The Commission is proposing amendments to the § 45.14(b) requirements for correcting errors and omissions in swap data that was previously reported to an SDR or that was not reported as required.
                        <SU>182</SU>
                        <FTREF/>
                         These 
                        <PRTPAGE P="21069"/>
                        error and omission correction requirements are effectively the same as the correction requirement in current § 45.14, but the Commission is proposing to clarify which entities have the correction reporting responsibilities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>182</SU>
                             The Commission notes that the failure to perform the initial reporting of swap data as required under § 45.3 is an “omission” for the purposes of current and proposed § 45.14. The omission must be corrected pursuant to the same requirements as any other error or omission, regardless of the state of the swap, by reporting the swap data as soon as technologically practicable after discovery of the failure to report. This includes reporting the omitted swap data to the SDR as 
                            <PRTPAGE/>
                            required by the SDR for an initial report of swap data.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 45.14(b)(1) would require any SEF, DCM, or reporting counterparty that by any means becomes aware of any error or omission in swap data previously reported to an SDR by the SEF, DCM, or reporting counterparty to submit corrected swap data to the SDR.
                        <SU>183</SU>
                        <FTREF/>
                         Proposed § 45.14(b)(1) would also require any SEF, DCM, or reporting counterparty that by any means becomes aware of any swap data not reported to an SDR by the SEF, DCM, or reporting counterparty as required to submit corrected swap data to the SDR.
                        <SU>184</SU>
                        <FTREF/>
                         Awareness of errors and omissions to be corrected would include, but would not be limited to, errors or omissions present in the swap data in the open swaps reports provided as part of the verification process specified in proposed § 45.14(a).
                        <SU>185</SU>
                        <FTREF/>
                         The error and omission correction requirements would apply regardless of the state of the swap, and include the correction of swaps that are no longer open or “alive.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>183</SU>
                             
                            <E T="03">See</E>
                             17 CFR 45.14(a) (Each registered entity and swap counterparty required by this part to report swap data to a swap data repository, to any other registered entity or swap counterparty, or to the Commission shall report any errors and omissions in the data so reported.).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>184</SU>
                             The Commission notes that successful reporting of swap data that was not previously reported as required would entail the relevant SEF, DCM, or reporting counterparty completing the reporting process for the omitted swap data as instructed in the relevant SDR's policies and procedures for reporting omitted swap data created pursuant to proposed § 49.10(e).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>185</SU>
                             This would include any open swaps that should be in the open swaps report but were omitted or swaps that are no longer open but still remain listed in the report, in addition to any errors or omissions in the swap data contained in the report. The requirement would also include, for example, a SEF, DCM, or reporting counterparty being informed of errors or omissions by an outside source, such as a non-reporting counterparty, a SEF or DCM, or the Commission; errors or omissions discovered by a SEF, DCM, or reporting counterparty during a review of its own records or voluntary review of swap data maintained by the SDR, including the discovery of any over- or under-reporting of swap data; and the discovery of errors or omissions during the investigation of a separate issue.
                        </P>
                    </FTNT>
                    <P>Proposed § 45.14(b)(1)(i) would retain the current § 45.14(a)(2) requirement that SEFs, DCMs, and reporting counterparties correct swap data “as soon as technologically practicable following discovery of the errors or omissions,” but would backstop “as soon as technologically practicable” for corrections at three business days after discovery of the error or omission.</P>
                    <P>
                        Proposed § 45.14(b)(1)(ii) would require that if a SEF, DCM, or reporting counterparty is unable to correct errors or omissions within three business days of discovery, the SEF, DCM, or reporting counterparty must immediately inform the Director of DMO, or such other Commission employees whom the Director of DMO may designate, in writing, of the errors or omissions and provide an initial assessment of the scope of the errors or omissions 
                        <SU>186</SU>
                        <FTREF/>
                         and an initial remediation plan for correcting the errors or omissions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>186</SU>
                             The Commission anticipates that this would include the causes of the errors or omissions, the number of swaps affected, the USIs for the affected swaps, and the date range for the affected swaps, among other information.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 45.14(b)(1)(iii) would require that a SEF, DCM, or reporting counterparty conform to the SDR's policies and procedures for corrections of errors and omissions that the SDRs would be required to create under proposed § 49.10.
                        <SU>187</SU>
                        <FTREF/>
                         By following the relevant SDR's policies and procedures for swap data correction, provided to users by the SDRs pursuant to proposed § 49.26(j), SEFs, DCMs, and reporting counterparties would be able to correct swap data with as little effort as necessary.
                    </P>
                    <FTNT>
                        <P>
                            <SU>187</SU>
                             
                            <E T="03">See</E>
                             section II.F above. The Commission expects that SEFs, DCMs, reporting counterparties, and SDRs would work together to devise effective correction policies, with particular attention paid to minimizing the effort needed to correct swap data for non-SD/MSP/DCO reporting counterparties.
                        </P>
                    </FTNT>
                    <P>Proposed § 45.14(b)(2) would require a non-reporting counterparty that by any means becomes aware of any error or omission in swap data previously reported to an SDR, or the omission of swap data for a swap that was not previously reported to an SDR as required, to notify the reporting counterparty for the swap of the errors or omissions as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days following the discovery of the errors or omissions.</P>
                    <P>
                        Proposed § 45.14(b)(2) would also specify that a non-reporting counterparty that does not know the identity of the reporting counterparty for a swap must notify the SEF or DCM where the swap was executed of the errors or omissions as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days after the discovery. Proposed § 45.14(b)(2) would also require that if the reporting counterparty, SEF, or DCM, as applicable, and the non-reporting counterparty agree that the swap data for a swap is incorrect or incomplete, the reporting counterparty, SEF, or DCM, as applicable, must correct the swap data in accordance with proposed § 45.14(b)(1).
                        <SU>188</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>188</SU>
                             This requirement is largely the same as the requirements of current § 45.14(b). 
                            <E T="03">See</E>
                             17 CFR 45.14(b) (Upon receiving such notice, the reporting counterparty shall report a correction of each such error or omission to the swap data repository as provided in paragraph (a) of this section.).
                        </P>
                    </FTNT>
                    <P>Current § 45.14(a) generally requires that each registered entity and swap counterparty required to report swap data must also report any errors and omissions discovered in the swap data as soon as technologically practicable after the errors or omissions are discovered and contains specific instructions for reporting errors or omissions in continuation data reported using the snapshot method.</P>
                    <P>Current § 45.14(b) requires the non-reporting counterparty to promptly notify the reporting counterparty of any errors or omissions and requires the reporting counterparty to correct the errors or omissions under the terms of current § 45.14(a).</P>
                    <P>Current § 45.14(c) requires: (i) Registered entities or swap counterparties to report corrections in the same format as the original reporting of the swap data, unless otherwise approved by the Commission's Chief Information Officer (“CIO”); and (ii) the SDR to transmit the corrections for errors and omissions in swap data in the same format used to originally disseminate the swap data, unless otherwise approved by the Commission's CIO.</P>
                    <P>The Commission is proposing to clarify that swap data must be corrected “regardless of the state of the swap that is the subject of the swap data” so market participants are aware that all incorrect or omitted swap data must be corrected, even if the swap that the swap data described has been terminated, matured, or otherwise ceased to be an open swap. The Commission does not believe this is a new requirement, as the current correction requirements of § 45.14 do not have time restrictions. Many of the Commission's regulatory responsibilities involve using swap data for swaps that were executed months or years earlier, including terminated, matured, or otherwise no-longer-open swaps. Incorrect swap data for these swaps, or a lack of any required reporting, would interfere with the Commission's ability to generate holistic, accurate, data-driven policies, analyses, and reports.</P>
                    <P>
                        The requirement to correct all swap data, regardless of status, also helps 
                        <PRTPAGE P="21070"/>
                        ensure that SEFs, DCMs, and reporting counterparties would establish and maintain properly functioning reporting systems to prevent reporting errors or omissions, as correcting swap data for swaps, including terminated swaps, would require effort that can be avoided by initially reporting correct swap data. Proper and thorough system design and testing during the implementation process for these proposed rules would benefit market participants in the form of less time and resources spent on later error and omission corrections. The Commission expects that, as swap data reporting improves over time, the resources needed to correct swap data would decrease.
                    </P>
                    <P>As with the verification requirements discussed above, the Commission also expects that a SEF, DCM, or reporting counterparty that repeatedly discovers errors or omissions, especially repeated errors or omissions that follow a pattern, such as the reporting for a certain type of swap regularly resulting in errors, would evaluate its reporting systems to discover and correct any issues. This would include working with the relevant SDR to address any reporting issues. A SEF, DCM, or reporting counterparty that fails to perform such an evaluation and improvement in light of repeated errors may not be in compliance with the Commission's regulations.</P>
                    <P>The Commission is aware that some errors or omissions may not be able to be corrected within three business days of discovery, depending on the gravity and complexity of the reporting problems. The Commission believes having the SEF, DCM, or reporting counterparty notify the Commission of such errors and omissions pursuant to proposed § 45.14(b)(1)(ii), formulate a plan to correct the errors or omissions, and perform the corrections as soon as possible would help alert the Commission to swap data that is unreliable, particularly if it may be unreliable for an extended period of time, and facilitates the fastest correction of the swap data. The Commission also believes that the requirements of proposed § 45.14(b)(1)(ii) would incentivize SEFs, DCMs, and reporting counterparties to fix reporting errors and omissions as quickly as possible, and to invest the resources to prevent reporting errors and omissions from occurring in the first place. The Commission notes that these proposed requirements are similar to current industry practice, as SEFs, DCMs, and reporting counterparties regularly inform Commission staff of reporting errors or omissions and work with Commission staff as they correct the errors and omissions, which typically includes detailed remediation plans and specific timelines for completion.</P>
                    <P>
                        The Commission is retaining the requirement from current § 45.14(b) that the non-reporting counterparty inform the reporting counterparty of the errors or omissions, instead of the non-reporting counterparty reporting the errors or omissions itself.
                        <SU>189</SU>
                        <FTREF/>
                         The Commission believes that it is not necessary for a non-reporting counterparty to undertake reporting corrections to an SDR because the non-reporting counterparty is often not a user of the SDR or any SDR, and may never serve as a reporting counterparty for swaps. In contrast, the reporting counterparties would already be users of the relevant SDR, and would have continuation data reporting responsibilities for the swap. The reporting counterparty is therefore the logical counterparty to perform the error and omission corrections without the need for the non-reporting counterparty to expend resources on error and omission reporting.
                    </P>
                    <FTNT>
                        <P>
                            <SU>189</SU>
                             
                            <E T="03">See</E>
                             17 CFR 45.14(b) (Each counterparty to a swap that is not the reporting counterparty . . . and that discovers any error or omission with respect to any swap data reported to a swap data repository for that swap, shall promptly notify the reporting counterparty of such error or omission.).
                        </P>
                    </FTNT>
                    <P>The Commission notes that the proposed requirement for the reporting counterparty and non-reporting counterparty to agree that the swap data is incorrect or incomplete before the reporting counterparty must correct errors discovered by the non-reporting counterparty is included in § 45.14(b)(2) to reduce the likelihood of the reporting of corrections when there is a legitimate dispute over whether swap data contains an error or omission. Neither party may arbitrarily or falsely withhold agreement that an error or omission exists, particularly if a reporting counterparty is withholding agreement in order to avoid its responsibility to correct errors or omissions. The parties would be expected to resolve any dispute before the error or omission is corrected.</P>
                    <P>Similarly, when the non-reporting counterparty does not know the identity of the reporting counterparty and instead reports the errors or omissions to the SEF or DCM, if the SEF or DCM and the non-reporting counterparty agree that the relevant swap data is incorrect or incomplete, then the SEF or DCM would correct the errors or omissions in accordance with proposed § 45.14(b)(2). Also, no SEF, DCM, or non-reporting counterparty may arbitrarily or falsely withhold agreement that an error or omission exists, particularly if the SEF or DCM is withholding agreement to avoid its responsibility to correct errors or omissions. The entities would be expected to resolve any dispute with each other before the error or omission is corrected. The Commission expects that a SEF of DCM, when necessary, would be capable of contacting a reporting counterparty to confirm whether the error or omission reported by the non-reporting counterparty exists without revealing the identity of the non-reporting counterparty to the reporting counterparty.</P>
                    <P>
                        The Commission is also proposing to remove the Commission's ability under current § 45.14(c) to approve the use of different data formats for corrections because the Commission does not believe that the use of different data formats for corrections is necessary and believes that the possibility adds uncertainty and potential delays to the correction process. SEFs, DCMs, reporting counterparties, and SDRs are all capable of reporting corrections using the same format as initial swap data reporting and would all know the correct format in advance of reporting under the requirements of proposed §§ 49.17 
                        <SU>190</SU>
                        <FTREF/>
                         and 49.26(j).
                        <SU>191</SU>
                        <FTREF/>
                         Additionally, proposed § 45.14(b)(1)(iii) would require SEFs, DCMs, and reporting counterparties to report corrections of errors or omissions in conformity with the SDR's policies and procedures for correcting errors and omissions created pursuant to proposed § 49.10, which would include how to properly format swap data in order for the SDR to successfully complete the correction process. The Commission believes that this approach would be more flexible than the current requirements, as the SDRs would be able to require a different format for reporting errors and omissions without requiring approval from the Commission.
                    </P>
                    <FTNT>
                        <P>
                            <SU>190</SU>
                             
                            <E T="03">See</E>
                             section II.L above.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>191</SU>
                             
                            <E T="03">See</E>
                             section II.R above.
                        </P>
                    </FTNT>
                    <P>
                        Finally, the current § 45.14(c) requirement for an SDR to transmit corrections to errors or omissions in swap data in the same format as the SDR typically transmits swap data to the Commission would be redundant, because the requirement does still effectively apply to all SDRs under proposed § 49.17, which requires SDRs to transmit all SDR data requested by the Commission to the Commission as instructed by the Commission.
                        <SU>192</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>192</SU>
                             
                            <E T="03">See</E>
                             section II.L above (describing the proposed requirements for SDRs to transmit data to the Commission).
                        </P>
                    </FTNT>
                    <PRTPAGE P="21071"/>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of proposed § 45.14. The Commission also invites specific comment on the following:
                    </P>
                    <P>(27) Should the Commission be more prescriptive in how reporting counterparties must complete the verification process? If so, please describe in detail.</P>
                    <HD SOURCE="HD1">IV. Proposed Amendments to Part 43</HD>
                    <HD SOURCE="HD2">A. § 43.3—Method and Timing for Real-Time Public Reporting</HD>
                    <HD SOURCE="HD3">1. Correction of Errors and Omissions in Swap Transaction and Pricing Data—§ 43.3(e)</HD>
                    <P>The Commission is proposing to amend the error and omission correction requirements for swap transaction and pricing data under § 43.3(e) to conform with the proposed amendments to § 45.14(b) for swap data discussed above in section III.B.</P>
                    <P>
                        Proposed § 43.3(e)(1) would require any SEF, DCM, or reporting counterparty that by any means becomes aware of any errors or omissions in swap transaction and pricing data previously reported to an SDR by the SEF, DCM, or reporting counterparty to submit corrected swap transaction and pricing data to the SDR. Proposed § 43.3(e)(1) would also require any SEF, DCM, or reporting counterparty that by any means becomes aware of the omission 
                        <SU>193</SU>
                        <FTREF/>
                         of swap transaction and pricing data previously not reported to an SDR by the SEF, DCM, or reporting counterparty as required, to submit corrected swap transaction and pricing data to the SDR.
                        <SU>194</SU>
                        <FTREF/>
                         As with proposed § 45.14(b), the error and omission correction requirements would apply regardless of the state of the swap, and include the correction of swaps that are no longer open or “alive.” 
                        <SU>195</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>193</SU>
                             The Commission notes that the failure to perform the initial reporting of swap transaction and pricing data as required under current and proposed § 43.3 is an “omission” for the purposes of both current and proposed § 43.3(e). The omission must be corrected pursuant to the same requirements as any other error or omission, regardless of the state of the swap, by reporting the swap transaction and pricing data as soon as technologically practicable after discovery of the failure to report. This includes reporting the omitted swap transaction and pricing data to the SDR as required by the SDR for an initial report of swap transaction and pricing data.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>194</SU>
                             The Commission notes that successful reporting of swap transaction and pricing data that was erroneously not previously reported as required would entail the relevant SEF, DCM, or reporting counterparty completing the reporting process for the omitted swap data as instructed in the relevant SDR's policies and procedures created pursuant to proposed § 49.10(e).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>195</SU>
                             This requirement is effectively the same as current § 43.3(e)(1).
                        </P>
                    </FTNT>
                    <P>Proposed § 43.3(e)(1)(i) would adopt the same timing requirements as proposed § 45.14(b)(1)(i) for SEFs, DCMs, and reporting counterparties to correct swap transaction and pricing data “as soon as technologically practicable following discovery of the errors or omissions,” with a three business day backstop following the discovery of the errors or omissions.</P>
                    <P>
                        Similar to proposed § 45.14(b)(1)(ii), proposed § 43.3(e)(1)(ii) would provide that if a SEF, DCM, or reporting counterparty is unable to correct the errors or omissions within three business days following discovery of the errors or omissions, the SEF, DCM, or reporting counterparty must immediately inform the Director of DMO, or such other employees of the Commission that the Director of DMO may designate, in writing, of such errors or omissions and provide an initial assessment of the scope of the errors or omissions 
                        <SU>196</SU>
                        <FTREF/>
                         and an initial remediation plan for correcting the errors or omissions.
                        <SU>197</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>196</SU>
                             The Commission anticipates that this would include the causes of the errors or omissions, the number of swaps affected, the USIs for the affected swaps, the date range for the affected swaps, among other information.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>197</SU>
                             The Commission needs to know as soon as possible if swap transaction and pricing data is unreliable, particularly if for an extended period of time, so that the Commission may alert the public as needed.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 43.3(e)(1)(iii) would require that a SEF, DCM, or reporting counterparty conform to an SDR's policies and procedures for corrections of errors and omissions in previously reported swap transaction and pricing data and reporting of omitted swap transaction and pricing data that the SDRs would be required to create under proposed § 49.10.
                        <SU>198</SU>
                        <FTREF/>
                         By following the relevant SDR's policies and procedures for swap data correction, which would be provided to users by the SDRs pursuant to proposed § 49.26(j), the Commission expects that SEFs, DCMs, or reporting counterparties would know how to correct swap data before correction is required and would be able to properly correct swap data with as little effort as necessary.
                        <SU>199</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>198</SU>
                             
                            <E T="03">See</E>
                             section II.F above.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>199</SU>
                             The Commission expects that SEFs, DCMs, reporting counterparties, and SDRs would work together to devise effective correction policies, with particular attention paid to minimizing the effort needed to correct swap data for non-SD/MSP/DCO reporting counterparties.
                        </P>
                    </FTNT>
                    <P>Proposed § 43.3(e)(2) would require a non-reporting counterparty that by any means becomes aware of any error or omission in swap transaction and pricing data previously reported to an SDR, or the omission of swap transaction and pricing data for a swap that was not previously reported to an SDR as required, to notify the reporting counterparty for the swap of the errors and omissions as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days following the discovery of the errors or omissions.</P>
                    <P>Proposed § 43.3(e)(2) would also specify that a non-reporting counterparty that does not know the identity of the reporting counterparty for a swap must notify the SEF or DCM where the swap was executed of the errors and omissions as soon as technologically practicable after discovery of the errors or omissions, but no later than three business days after the discovery. Proposed § 43.3(e)(2) would also require that, if the reporting counterparty, SEF, or DCM, as applicable, and the non-reporting counterparty agree that the swap transaction and pricing data for a swap is incorrect or incomplete, the reporting counterparty, SEF, or DCM, as applicable, must correct the swap transaction and pricing data in accordance with proposed § 43.3(e)(1).</P>
                    <P>The Commission believes that the amendments to § 43.3(e) would help ensure that errors or omissions in swap transaction and pricing data are corrected as soon as possible. The proposed rule would also clarify that swap transaction and pricing data must be corrected regardless of the state of the swap that is the subject of the swap transaction and pricing data to ensure that all incorrect or omitted swap transaction and pricing data is corrected, even if the swap that the swap transaction and pricing data relates to has been terminated, matured, or otherwise ceased to be an open swap. This is not a new requirement, as the current correction requirements in § 43.3(e) do not have time restrictions. The Commission also believes that proposed § 43.3(e) would help ensure that the public has access to the most accurate and complete swap transaction and pricing data possible. Incorrect swap transaction and pricing data harms market integrity and price discovery, long after the swap has been executed.</P>
                    <P>
                        The requirement to correct all swap transaction and pricing data, regardless of status, also helps ensure that SEFs, DCMs, and reporting counterparties would maintain properly functioning reporting systems to prevent reporting errors or omissions, as correcting swap transaction and pricing data for swaps, including terminated swaps, would require effort that can be avoided by initially reporting correct swap transaction and pricing data. Proper and 
                        <PRTPAGE P="21072"/>
                        thorough system design and testing during the implementation process for these proposed regulations would benefit market participants in the form of less time and resources spent on error corrections in the future. The Commission expects that, as data reporting improves over time, the resources needed to correct swaps, including swaps that are no longer open, would diminish.
                    </P>
                    <P>The Commission also notes that the discovery of errors under proposed § 43.3(e)(1) includes any errors or omissions revealed when reporting counterparties are reconciling swap data during the verification process required under proposed § 45.14(a) that would also be errors or omissions in swap transaction and pricing data. The means of discovery are unlimited, however, and would also include, for example, a SEF, DCM, or reporting counterparty being informed of errors or omissions by an outside source, such as a non-reporting counterparty, an exchange, or the Commission; errors or omissions discovered by a SEF, DCM, or reporting counterparty during a review of its own records or voluntary review of swap transaction and pricing data maintained by the SDR, including the discovery of any over- or under-reporting of swap transaction and pricing data; and the of discovery of errors or omissions during the investigation of a separate issue.</P>
                    <P>The Commission expects that a SEF, DCM, or reporting counterparty that repeatedly discovers errors or omissions, especially repeated errors or omissions that follow a pattern, such as the reporting for a certain type of swap regularly resulting in errors, would evaluate its reporting systems to attempt to find and promptly correct any issues discovered. This would include working with the relevant SDR to address any reporting issues. A SEF, DCM, or reporting counterparty that fails to perform such an evaluation and improvement in light of repeated errors may not be in compliance with the Commission's regulations.</P>
                    <P>The Commission is aware that some errors and omissions may not be able to be corrected within three business days of discovery. The Commission believes having the SEF, DCM, or reporting counterparty notify the Commission of such errors and omissions pursuant to proposed § 43.3(e)(1)(ii), formulate a plan to correct the errors and omissions, and to perform the corrections as soon as possible would help alert the Commission to swap transaction and pricing data that is unreliable, particularly if it may be unreliable for an extended period of time, and facilitates the fastest correction of swap transaction and pricing data. The Commission also believes that proposed § 43.3(e)(1)(ii) would incentivize SEFs, DCMs, and reporting counterparties to fix reporting errors and omissions as quickly as possible. The Commission notes that these proposed requirements are consistent with industry practice, as SEFs, DCMs, and reporting counterparties regularly inform Commission staff of reporting errors or omissions and work with Commission staff as they correct the errors and omissions, which typically includes remediation plans and timelines for completion.</P>
                    <P>The Commission is proposing to require, as with proposed § 45.14(b)(2), that the non-reporting counterparty inform the reporting counterparty of the errors or omissions. The Commission believes that it is not necessary for a non-reporting counterparty to undertake the burden of reporting corrections to an SDR because the non-reporting counterparty is often not a user of the SDR, and may never serve as a reporting counterparty for any swaps. In contrast, reporting counterparties would already by definition be users of the relevant SDR, and would have continuation data reporting responsibilities for the swap. The reporting counterparty is therefore the logical counterparty to perform the error and omission corrections without the need for the non-reporting counterparty to use additional resources on error and omission reporting.</P>
                    <P>The Commission notes that the proposed requirement for the reporting counterparty and non-reporting counterparty to agree that the swap transaction and pricing data is incorrect or incomplete before the reporting counterparty must correct errors discovered by the non-reporting counterparty is included to avoid the reporting of corrections when there is a legitimate dispute over whether the swap transaction and pricing data contains an error or omission. Neither party may arbitrarily or falsely withhold agreement that an error or omission exists, particularly if a reporting counterparty is withholding agreement in order to avoid its responsibility to correct errors or omissions. The parties would be expected to resolve any dispute with each other before the error or omission is corrected.</P>
                    <P>Similarly, in the instance where the non-reporting counterparty does not know the identity of the reporting counterparty and instead reports the errors or omissions to the SEF or DCM, if the SEF or DCM and the non-reporting counterparty agree that the relevant swap transaction and pricing data is incorrect or incomplete, then the SEF or DCM must correct the errors or omissions in accordance with proposed § 43.3(e)(1). No SEF, DCM, or non-reporting counterparty may arbitrarily or falsely withhold agreement that an error or omission exists, particularly if the SEF or DCM is withholding agreement to avoid its responsibility to correct errors or omissions. The entities would be expected to resolve any dispute with each other before the error or omissions is corrected. The Commission expects that a SEF or DCM, when necessary, would be capable of contacting a reporting counterparty to confirm whether the error or omission reported by the non-reporting counterparty exists without revealing the identity of the non-reporting counterparty to the reporting counterparty.</P>
                    <HD SOURCE="HD3">2. Proposed Deletions—§ 43.3(f) and (g)</HD>
                    <P>
                        The Commission is proposing to delete current § 43.3(f) and (g). The Commission is proposing to include the operating hours requirements for SDRs in new § 49.28,
                        <SU>200</SU>
                        <FTREF/>
                         which includes incorporating the requirements of current § 43.3(f) and (g). Current § 43.3(f) contains the hours of operations requirements 
                        <SU>201</SU>
                        <FTREF/>
                         and current § 43.3(g) contains the requirements for SDRs to accept swap transaction and pricing data during closing hours.
                        <SU>202</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>200</SU>
                             
                            <E T="03">See</E>
                             section II.S above.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>201</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.3(f).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>202</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.3(g).
                        </P>
                    </FTNT>
                    <P>Keeping the paragraphs in part 43 could also cause confusion as to the requirements that apply to SDRs, because proposed § 49.28 would apply to all SDR data and also incorporates provisions from SBSDR operating hours requirements. The Commission notes that most of the requirements contained in current § 43.3(f) and (g) would continue to apply to SDRs, because the requirements are included in proposed § 49.28.</P>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all aspects of proposed § 43.3.
                    </P>
                    <HD SOURCE="HD1">V. Proposed Amendments to Part 23</HD>
                    <HD SOURCE="HD2">A. § 23.204—Reports to Swap Data Repositories</HD>
                    <P>
                        Proposed § 23.204(c) would require each SD and MSP to establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure that the SD or MSP complies with all obligations to report swap data to an SDR consistent with part 45. Proposed § 23.204(c) also would require an SD or MSP to review its policies and procedures on an annual basis and to update its policies and procedures as 
                        <PRTPAGE P="21073"/>
                        needed to reflect the requirements in part 45.
                    </P>
                    <P>
                        As part of the SD/MSP requirements set forth in part 23 of the Commission's regulations, the Commission currently requires SDs/MSPs to report all information and swap data required for swap transactions as set forth in part 45.
                        <SU>203</SU>
                        <FTREF/>
                         The Commission also currently requires that SDs/MSPs have in place the electronic systems and procedures necessary to transmit electronically all information and swap data required to be reported in accordance with part 45.
                        <SU>204</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>203</SU>
                             
                            <E T="03">See</E>
                             17 CFR 23.204(a).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>204</SU>
                             
                            <E T="03">See</E>
                             17 CFR 23.204(b).
                        </P>
                    </FTNT>
                    <P>
                        The Commission notes that, pursuant to other Commission regulations, SDs and MSPs are already expected to establish policies and procedures related to their swap market activities, including but not limited to, swaps reporting obligations.
                        <SU>205</SU>
                        <FTREF/>
                         The proposed amendments would make that expectation explicit with respect to swap data reporting obligations.
                    </P>
                    <FTNT>
                        <P>
                            <SU>205</SU>
                             
                            <E T="03">See, e.g.,</E>
                             17 CFR 3.3(d)(1)(requiring a chief compliance officer to administer each of the registrant's policies and procedures relating to its business as an SD/MSP that are required to be establish pursuant to the Act and the Commission's regulations); 17 CFR 3.2(c)(3)(ii) (requiring the National Futures Association to assess whether an entity's SD/MSP documentation demonstrates compliance with the Section 4s Implementing Regulation to which it pertains which includes § 23.204 and § 23.205).
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that the annual review requirement in proposed § 23.204(c) would help ensure that SD/MSP policies and procedures remain current and effective over time. The proposal is also substantially similar to the requirements that the SEC has enacted for SBSDs and SBS MSPs.
                        <SU>206</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>206</SU>
                             
                            <E T="03">See</E>
                             SBSDR Adopting Release at 14647-14648; 
                            <E T="03">see also</E>
                             17 CFR 242.906(c).
                        </P>
                    </FTNT>
                    <P>
                        As part of the goal to increase the reliability, accuracy, and completeness of SDR data reported to and maintained by SDRs, the Commission believes that it is important to make clear the responsibilities of SDs and MSPs to ensure proper reporting of swaps for which they act as reporting counterparties. Accordingly, the Commission proposes that SDs/MSPs that report to an SDR should be explicitly required to adopt policies and procedures reasonably designed to ensure compliance with their reporting obligations under parts 43 and 45.
                        <SU>207</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>207</SU>
                             The amendments for part 43 reporting are discussed below in section IV.A.
                        </P>
                    </FTNT>
                    <P>The policies and procedures required by proposed § 23.204(c) should address how the SD or MSP would comply with the requirements of part 45, including, but not necessarily limited to: (i) The reporting process and designation of responsibility for reporting swap data; (ii) reporting system outages or malfunctions, and when and how back-up systems are to be used in connection with required reporting; (iii) verification of all swap data reported to an SDR pursuant to proposed § 45.14(a) and in accordance with the policies and procedures of such SDR established under proposed § 49.11; (iv) a training program for employees responsible for swap data reporting; (v) control procedures relating to swap data reporting and designation of personnel responsible for testing and verifying such policies and procedures; and (vi) reviewing and assessing the performance and operational capability of any third party that carries out any duty required by part 45 on behalf of the SD or MSP.</P>
                    <P>
                        These issues are also generally the issues that the SEC contemplated being addressed by SBSDs and SBS MSPs in their policies and procedures adopted pursuant to the SBSR Adopting Release.
                        <SU>208</SU>
                        <FTREF/>
                         In conjunction with “know your counterparty” obligations under current § 23.402(b), such policies should also ensure that the SD/MSP would have all necessary counterparty information, including, but not limited to, legal entity identifier (“LEI”) or acceptable counterparty identifier, U.S. Person status, and SD/MSP status, to accurately report all swap data required by part 45 for swaps for which the SD/MSP has reporting obligations.
                    </P>
                    <FTNT>
                        <P>
                            <SU>208</SU>
                             
                            <E T="03">See</E>
                             SBSDR Adopting Release at 14648; 
                            <E T="03">see also</E>
                             17 CFR 242.906(c).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. § 23.205—Real-Time Public Reporting</HD>
                    <P>
                        Similar to the requirements of proposed § 23.204(c) discussed above in section V.A, the Commission is proposing § 23.205(c), which would require SDs and MSPs to establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure that the SD or MSP complies with any obligations to report swap transaction and pricing data to an SDR consistent with part 43 of the Commission's regulations. As with swap data under § 23.204(c), proposed § 23.205(c) is intended to promote complete and accurate reporting of swap transaction and pricing data by SDs and MSPs, consistent with their obligations under part 43 and the CEA.
                        <SU>209</SU>
                        <FTREF/>
                         The Commission believes that the addition of this proposed requirement would help to improve the extent and quality of overall compliance with the reporting requirements of part 43. Similar to proposed § 23.204(c), proposed § 23.205(c) would require an SD or MSP to review its policies and procedures on an annual basis and to update its policies and procedures as needed to reflect the requirements of part 43. The periodic review requirement would help ensure that these policies and procedures remain current and effective over time. The proposal is also substantially similar to the requirements that the SEC has enacted for SBSDs and SBS MSPs.
                        <SU>210</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>209</SU>
                             Section 2(a)(13) of the CEA directs the Commission to adopt regulations for the public availability of swap transaction and pricing data. 
                            <E T="03">See</E>
                             7 U.S.C. 2(a)(13).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>210</SU>
                             
                            <E T="03">See</E>
                             SBSDR Adopting Release at 14647-14648.
                        </P>
                    </FTNT>
                    <P>
                        The SD/MSP recordkeeping and reporting requirements in part 23 also currently require SDs/MSPs to report all information and swap transaction and pricing data required in accordance with the real-time public reporting requirements as set forth in part 43.
                        <SU>211</SU>
                        <FTREF/>
                         The Commission also requires that SDs/MSPs have in place the electronic systems and procedures necessary to transmit electronically all information and swap transaction and pricing data required to be reported in accordance with part 43.
                        <SU>212</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>211</SU>
                             
                            <E T="03">See</E>
                             17 CFR 23.205(a).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>212</SU>
                             
                            <E T="03">See</E>
                             17 CFR 23.205(b).
                        </P>
                    </FTNT>
                    <P>
                        The policies and procedures required by proposed § 23.205(c) should address how the SD or MSP will comply with the requirements of part 43, including, but not necessarily limited to: (i) The reporting process and designation of responsibility for reporting swap transaction and pricing data; (ii) reporting system outages or malfunctions, and when and how back-up systems are to be used in connection with required reporting; (iii) a training program for employees responsible for real-time reporting; (iv) control procedures relating to real-time reporting and designation of personnel responsible for testing and verifying such policies and procedures; (v) reviewing and assessing the performance and operational capability of any third party that carries out any duty required by part 43 of the Commission's regulations on behalf of the SD or MSP; and (vi) the determination of whether a new swap transaction or amendment, cancelation, novation, termination, or other lifecycle event of an existing swap, is subject to the real time reporting requirements of part 43. These issues are a subset of the general issues that the SEC contemplated being addressed by SBSDs and SBS MSPs in their policies and procedures adopted pursuant to the SBSR Adopting Release.
                        <SU>213</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>213</SU>
                             
                            <E T="03">See</E>
                             SBSDR Adopting Release at 14648.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Request for Comment.</E>
                         The Commission requests comment on all 
                        <PRTPAGE P="21074"/>
                        aspects of proposed §§ 23.204(c) and 23.205(c). The Commission also invites specific comment on the following:
                    </P>
                    <P>(28) Should proposed § 23.204(c) and § 23.205(c) specify the elements to be included in the required policies and procedures? If so, what specific elements should be included in the proposed regulation, and why? Please be specific.</P>
                    <HD SOURCE="HD1">VI. Request for Comments</HD>
                    <P>The Commission requests comments concerning all aspects of the proposed regulations, including, without limitation, all of the aspects of the proposed regulations on which comments have been requested specifically herein. The Commission also invites comments on the following:</P>
                    <P>
                        (29) Please describe the nature of any changes necessary, 
                        <E T="03">i.e.,</E>
                         operational, technological, administrative, etc., for SDRs, other registered entities, and swap counterparties to comply with the regulations proposed in this release, including the length of time needed to implement each type of change, whether a phase-in period is needed, and how any phase in of any final rules should be structured. Please describe how any changes to systems made by one type of entity, such as the SDRs, would require changes to systems by other entities within the swaps reporting environment, and what sequencing of changes would need to occur.
                    </P>
                    <P>(30) Would the proposed amendments and additions to parts 23, 43, 45, and 49 adequately improve the data quality and accuracy of reported SDR data maintained by SDRs? If not, please explain.</P>
                    <P>(31) Are additional changes necessary to parts 23, 43, 45, and 49 (or other parts of the regulations) to ensure the quality of reported SDR data held and maintained by SDRs? If so, please explain.</P>
                    <HD SOURCE="HD1">VII. Related Matters</HD>
                    <HD SOURCE="HD2">A. Regulatory Flexibility Act</HD>
                    <P>
                        The Regulatory Flexibility Act (“RFA”) requires federal agencies, in promulgating rules, to consider the impact of those rules on small entities.
                        <SU>214</SU>
                        <FTREF/>
                         The Commission has previously established certain definitions of “small entities” to be used by the Commission in evaluating the impact of its rules on small entities in accordance with the RFA.
                        <SU>215</SU>
                        <FTREF/>
                         The amendments to part 49 proposed herein would have a direct effect on the operations of SDRs. The Commission has previously certified that SDRs are not small entities for purpose of the RFA.
                        <SU>216</SU>
                        <FTREF/>
                         Proposed §§ 23.204(c) and 23.205(c), which require SDs and MSPs to have policies and procedures to ensure compliance with requirements of parts 45 and 43, respectively, would have a direct impact on the operation of SDs and MSPs. The Commission has previously certified that SDs and MSPs are also not small entities for purpose of the RFA.
                        <SU>217</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>214</SU>
                             
                            <E T="03">See</E>
                             5 U.S.C. 601 
                            <E T="03">et seq.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>215</SU>
                             
                            <E T="03">See</E>
                             Policy Statement and Establishment of “Small Entities” for purposes of the Regulatory Flexibility Act, 47 FR 18618, 18618-21 (Apr. 30, 1982).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>216</SU>
                             
                            <E T="03">See</E>
                             Swap Data Repositories, Proposed Rule, 75 FR 80898, 80926 (Dec. 23, 2010) (basing determination in part on the central role of SDRs in swaps reporting regime, and on the financial resource obligations imposed on SDRs).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>217</SU>
                             
                            <E T="03">See</E>
                             Swap Dealer and Major Swap Participant Recordkeeping, Reporting, and Duties Rules, Final Rule, 77 FR 20128, 20194 (Apr. 3, 2012) (basing determination in part on minimum capital requirements).
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 45.14(a), which requires all reporting counterparties to verify the accuracy of swap data with the SDR, would have a direct impact on all reporting counterparties. These reporting counterparties may include SDs, MSPs, DCOs,
                        <SU>218</SU>
                        <FTREF/>
                         and non-SD/MSP/DCO counterparties. Regarding whether non-SD/MSP/DCO reporting counterparties are small entities for RFA purposes, the Commission notes that section 2(e) of the Act prohibits entities from entering into swaps unless the entity qualifies as an eligible contract participant (“ECP”), except for swaps executed on or pursuant to the rules of a DCM.
                        <SU>219</SU>
                        <FTREF/>
                         The Commission has previously certified that ECPs are not small entities for purposes of the RFA.
                        <SU>220</SU>
                        <FTREF/>
                         The vast majority of swap are not conducted on DCMs, and therefore must involve ECPs. A recent Commission staff review of swap data, including swaps executed on or pursuant to the rules of a DCM, identified nearly 1,600 non-SD/MSP/DCO reporting counterparties. Based on its review of publicly available data, the Commission believes that the overwhelming majority of these non-SD/MSP/DCO reporting counterparties are either ECPs or do not meet the definition of “small entity” established in the RFA. Accordingly, the Commission does not believe the proposed rule would affect a substantial number of small entities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>218</SU>
                             The Commission has previously certified that DCOs are not small entities for purposes of the RFA. 
                            <E T="03">See</E>
                             Derivatives Clearing Organization General Provisions and Core Principles, Final Rule, 76 FR 69334, 69428 (Nov. 8, 2011).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>219</SU>
                             
                            <E T="03">See</E>
                             7 U.S.C. 2(e).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>220</SU>
                             
                            <E T="03">See</E>
                             Opting Out of Segregation, Final Rule, 66 FR 20740, 20743 (Apr. 25, 2001). The Commission also notes that this determination was based on the definition of ECP as provided in the Commodity Futures Modernization Act of 2000. The Dodd-Frank Act amended the definition of ECP as to the threshold for individuals to qualify as ECPs, changing an individual who has total assets in an amount in excess of to an individual who has amounts invested on a discretionary basis, the aggregate of which is in excess of. Therefore, the threshold for ECP status is currently higher than was in place when the Commission certified that ECPs are not small entities for RFA purposes, meaning that there are likely fewer entities that could qualify as ECPs than when the Commission first made the determination.
                        </P>
                    </FTNT>
                    <P>Therefore, the Chairman, on behalf of the Commission, pursuant to 5 U.S.C. 605(b), hereby certifies that the proposed rules will not have a significant economic impact on a substantial number of small entities.</P>
                    <HD SOURCE="HD2">B. Paperwork Reduction Act</HD>
                    <P>
                        The Paperwork Reduction Act of 1995 (“PRA”) 
                        <SU>221</SU>
                        <FTREF/>
                         imposes certain requirements on federal agencies, including the Commission, in connection with their conducting or sponsoring any collection of information, as defined by the PRA. This proposed rulemaking would result in the collection of information within the meaning of the PRA, as discussed below. The proposed rulemaking contains collections of information for which the Commission has previously received three control numbers from OMB: (1) OMB Control Number 3038-0096 (relating to swap data recordkeeping and reporting by market participants); (2) OMB Control Number 3038-0070 (relating to real-time swap transaction and pricing data); and (3) OMB Control Number 3038-0086 (relating to obligations of SDRs).
                    </P>
                    <FTNT>
                        <P>
                            <SU>221</SU>
                             
                            <E T="03">See</E>
                             44 U.S.C. 3501.
                        </P>
                    </FTNT>
                    <P>The Commission is proposing to amend information collections 3038-0096, 3038-0070, and 3038-0086 to accommodate new information collection requirements for swap market participants and SDRs that require approval from OMB under the PRA. The following amendments to the obligations of market participants and SDRs are expected to modify the existing annual burden for complying with the requirements of parts 43, 45, and 49.</P>
                    <P>
                        The proposed amendments to § 45.2 would move the requirements of paragraphs (f) and (g) to proposed § 49.12, in order to better organize regulations related to SDRs. The proposed amendments to § 45.14 would require reporting counterparties to verify swap data reported to an SDR pursuant to the policies and procedures established by that SDR and would require SEFs, DCMs, and reporting counterparties to provide additional information to the Commission regarding correction of errors and 
                        <PRTPAGE P="21075"/>
                        omissions in swap data in certain circumstances. The proposed amendments to § 43.3 would require SEFs, DCMs, and reporting counterparties to provide additional information to the Commission regarding correction of errors and omissions in swap transaction and pricing data in certain circumstances and would move the requirements of paragraphs (f) and (g) to proposed § 49.28. The proposed amendments to part 49 would require SDRs to: (i) Continue to amend Form SDR as required, but remove the annual amendment requirement and limit the amendment requirement to before an application for registration is granted, as set forth in proposed § 49.3(a)(5); (ii) provide notifications and certifications to the Commission related to equity interest transfers, as set forth in proposed § 49.5; (iii) request transfer of registration, as set forth in proposed § 49.6; (iv) provide open swaps reports to the Commission, as set forth in proposed § 49.9; (v) correct errors and omissions in SDR data and create policies and procedures to accomplish the corrections, as set forth in proposed § 49.10(e); (vi) compile and distribute to each applicable reporting counterparty an open swaps report and to receive a response to each open swaps report, as set forth in proposed § 49.11; (vii) establish automated systems for monitoring, screening, and analyzing all SDR data in their possession in the form and manner as may be directed by the Commission under proposed § 49.13(a); (viii) provide SDR users and potential users with SDR policies and procedures related to reporting SDR data, as provided in proposed § 49.26(j); (ix) operate continuously, except for normal closing hours and special closing hours, as provided in proposed § 49.28; and (x) provide the Commission with information related to their business as an SDR and such information as the Commission determines to be necessary to perform its duties under the CEA and Commission regulations and provide the Commission with information and/or SDR data as requested to demonstrate SDR compliance with the CEA and Commission regulations, as set forth in proposed § 49.29.
                    </P>
                    <P>
                        The Commission therefore is submitting this proposal to the Office of Management and Budget (“OMB”) for its review in accordance with 44 U.S.C. 3507(d) and 5 CFR 1320.11. Responses to this collection of information would be mandatory. The Commission will protect proprietary information according to the Freedom of Information Act (“FOIA”) and 17 CFR 145, “Commission Records and Information.” In addition, section 8(a)(1) of the CEA strictly prohibits the Commission, unless specifically authorized by the Act, from making public data and information that would separately disclose the business transactions or market positions of any person and trade secrets or names of customers.
                        <SU>222</SU>
                        <FTREF/>
                         The Commission is also required to protect certain information contained in a government system of records according to the Privacy Act of 1974.
                        <SU>223</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>222</SU>
                             7 U.S.C. 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>223</SU>
                             5 U.S.C. 552a.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">1. Revisions to Collection 3038-0096 (Swap Data Reporting)</HD>
                    <HD SOURCE="HD3">i. Amended § 45.2</HD>
                    <P>The Commission is proposing to remove paragraphs (f) and (g) from § 45.2 in order to move the requirements of these paragraphs to proposed § 49.12. Paragraphs (f) and (g) contain recordkeeping requirements specific to SDRs. Current § 49.12 already incorporates the requirements of current § 45.2(f) and (g), and proposed § 49.12 would include the same requirements, but this proposed deletion and move is intended to better organize regulations for SDRs by locating as many SDR requirements as possible in part 49 of the Commission's regulations. Moving the requirements would however modify collection 3038-0096 because it would remove these recordkeeping requirements from part 45 of the Commission's regulations. As a result, the Commission estimates that moving these requirements would result in a reduction of 50 annual burden hours for each SDR in collection 3038-0096, for a total reduction of 150 annual burden hours across all three SDRs.</P>
                    <HD SOURCE="HD3">ii. Amended § 45.14</HD>
                    <P>
                        Proposed § 45.14(a) would require all reporting counterparties to verify the accuracy and completeness of all swap data for all open swaps to which they are the reporting counterparty. Reporting counterparties would comply with this provision by conforming to the verification policies and procedures of the relevant SDR(s) established pursuant to proposed § 49.11(a), including receiving and responding to the open swaps reports provided by the SDR(s). Section 21(c)(2) 
                        <SU>224</SU>
                        <FTREF/>
                         of the Act requires SDRs to confirm the accuracy of reported swap data with the counterparties to the swap. Compliance with proposed § 45.14(a) would constitute a collection of information not currently included in collection 3038-0096, and therefore would require a revision of that collection.
                    </P>
                    <FTNT>
                        <P>
                            <SU>224</SU>
                             7 U.S.C. 24a(c)(2).
                        </P>
                    </FTNT>
                    <P>Compliance with proposed § 45.14(a) would be based on compliance with SDR verification policies and procedures, but would require reporting counterparties to receive and respond to open swaps reports on a weekly or monthly basis, depending on the registration status of the reporting counterparty. The Commission expects that compliance with this section would include: (1) A one-time hours burden to establish internal systems needed to perform their verification responsibilities, and (2) an ongoing hours burden to complete the verification process for each report provided by an SDR.</P>
                    <P>In order to comply with the relevant SDR verification policies and procedures as required to complete the verification process, the Commission believes that reporting counterparties would be required to create their own verification systems or modify their existing connections to the SDRs. The Commission estimates that each reporting counterparty would incur an initial, one-time burden of 100 hours to build, test, and implement their verification systems based on SDR instructions. This burden may be reduced, if complying with SDR verification requirements only requires reporting counterparties to make small modifications to their existing SDR reporting systems, but the Commission is estimating the burden based on the creation of a new system. The Commission also estimates an ongoing annual burden of 10 hours per reporting counterparty to maintain their verification systems and to make any needed updates to verification systems to conform to any changes to SDR verification policies and procedures. As there are approximately 1,702 reporting counterparties based on data available to the Commission, the Commission estimates a one-time overall hours burden of 170,200 hours to build reporting counterparty verification systems and an ongoing annual overall hours burden of 17,020 hours to maintain the reporting counterparty verification systems.</P>
                    <P>
                        Proposed § 45.14(a) would also require reporting counterparties to reconcile the swap data in their internal books and records with the swap data in each open swaps report provided by an SDR and to respond to each open swaps report with a verification of data accuracy or a notice of discrepancy, as instructed by the relevant SDR verification policies and procedures. For SD, MSP, or DCO reporting counterparties, data verification would 
                        <PRTPAGE P="21076"/>
                        be at most a weekly occurrence for each SDR where the reporting counterparty maintains any open swaps. For non-SD/MSP/DCO reporting counterparties, data verification would be at most a monthly occurrence for each SDR where the reporting counterparty maintains any opens swaps. The Commission also expects, based on discussions with SDRs and reporting counterparties, that the verification process will be largely automated for all parties involved. The Commission is therefore estimating an ongoing average burden of two hours per open swaps report per reporting counterparty.
                    </P>
                    <P>
                        As there are 117 SDs, MSPs, or DCOs that clear swaps registered with the Commission, the Commission estimates
                        <SU>225</SU>
                        <FTREF/>
                         that these 117 reporting counterparties would, at maximum, be required to verify data 52 times per year, for an overall additional annual hours burden of 12,168 ongoing burden hours related to the verification process for these reporting counterparties. The Commission also estimates, based on data available to the Commission, that there are 1,585 non-SD/MSP/DCO reporting counterparties.
                        <SU>226</SU>
                        <FTREF/>
                         The Commission estimates that these 1,585 reporting counterparties would be required to, at maximum, verify data 12 times per year, for an overall additional annual hours burden of 38,040 burden hours related to verification process for these reporting counterparties.
                    </P>
                    <FTNT>
                        <P>
                            <SU>225</SU>
                             Though there are 117 SDs, MSPs, or DCOs that clear swaps registered with the Commission that could be a reporting counterparty, not all potential reporting counterparties would be performing data verification for any given verification cycle. Only those reporting counterparties with open swaps as of the moment the SDRs create the open swaps reports would perform data verification for that verification cycle.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>226</SU>
                             Though there are 1,585 non-SD/MSP/DCOs that could be a reporting counterparty, not all potential reporting counterparties would be performing data verification for any given verification cycle. Only those reporting counterparties with open swaps as of the moment the SDRs create the open swaps reports would perform data verification for that verification cycle.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 45.14(b) would, similar to current § 45.14, require SEFs, DCMs, and reporting counterparties to correct errors and omissions in swap data previously reported to an SDR, or erroneously not reported to an SDR as required, as soon as technologically practicable after discovery of the errors or omissions. Proposed § 45.14(b) would also require a non-reporting counterparty to report a discovered error or omission to the relevant SEF, DCM, or reporting counterparty as soon as technologically practicable after discovery of the error or omission.
                        <SU>227</SU>
                        <FTREF/>
                         These proposed requirements, being effectively the same as the requirements in current § 45.14, do not require amendments to the collection.
                    </P>
                    <FTNT>
                        <P>
                            <SU>227</SU>
                             The Commission notes that proposed § 45.14(b)(2) does add provisions that are not present in current § 45.14(b) to address the situation where a non-reporting counterparty does not know the identity of the reporting counterparty. The Commission does not believe that these additions have PRA implications, as the amount of information the non-reporting counterparty must provide and the frequency with which it must be provided remain the same and are de minimis. The only change is the requirement that non-reporting counterparties inform the SEF or DCM of errors, instead of the reporting counterparty. SEFs and DCMs have correction responsibilities under current § 45.14(b) and proposed § 45.14(b)(2) does not change these responsibilities.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 45.14(b)(1)(ii) does, however, include the new requirement for SEFs, DCMs, and reporting counterparties to notify the Director of DMO when errors or omissions cannot be corrected within three business days and, in such case, to provide the Director of DMO with an initial assessment of the errors and omissions and an initial remediation plan. This requirement would constitute a new collection of information. The Commission estimates that each SEF, DCM, and reporting counterparty would, on average need to provide notice and initial assessments to the Commission under proposed § 45.14(b)(1)(ii) once per year and that each instance would require 30 burden hours.
                        <SU>228</SU>
                        <FTREF/>
                         As there are approximately 1,729 SEFs, DCMs, and reporting counterparties that handle swaps, the Commission estimates an overall additional annual hours burden of 51,870 hours related to this requirement. This estimate is based on the Commission's experience with the current practices of SEFs, DCMs, and reporting counterparties regarding the reporting of errors and omissions, including the initial assessments and remediation plans that SEFs, DCMs, and reporting counterparties provide to the Commission under current practice. The Commission does not anticipate any one-time, initial burdens related to proposed § 45.14(b)(1)(ii).
                    </P>
                    <FTNT>
                        <P>
                            <SU>228</SU>
                             The Commission notes that, currently, it receives significantly less than one notice and initial assessment of reporting errors and omissions per SEF, DCM, or reporting counterparty per year, but is estimating one notice and initial assessment here, as the proposed requirements of § 45.14(a) may reveal more reporting errors to reporting counterparties that would then prompt corrections pursuant to proposed § 45.14(b).
                        </P>
                    </FTNT>
                    <P>The Commission therefore estimates that the overall burden for updated Information Collection 3038-0096 will be as follows:</P>
                    <P>
                        <E T="03">Estimated number of respondents affected:</E>
                         1,732 SEFs, DCMs, DCOs, SDRs, and reporting counterparties.
                    </P>
                    <P>
                        <E T="03">Estimated annual number of responses per respondent:</E>
                         257,595.
                    </P>
                    <P>
                        <E T="03">Estimated total annual responses:</E>
                         446,154,518.
                    </P>
                    <P>
                        <E T="03">Estimated burden hours per response:</E>
                         0.005.
                    </P>
                    <P>
                        <E T="03">Estimated total annual burden hours per respondent:</E>
                         1,316.
                    </P>
                    <P>
                        <E T="03">Estimated aggregate total burden hours for all respondents:</E>
                         2,279,202.
                    </P>
                    <HD SOURCE="HD3">2. Revisions to Collection 3038-0070 (Real-Time Transaction Reporting)—Amended § 43.3</HD>
                    <P>
                        Proposed § 43.3(e) would, as with swap data under proposed § 45.14(b), require SEFs, DCMs, and reporting counterparties to correct errors and omissions in swap transaction and pricing data previous reported to an SDR or erroneously not reported to an SDR as soon as technologically practicable after discovery of the errors or omissions. Proposed § 43.3(e) would also require a non-reporting counterparty to report a discovered error or omission to the relevant SEF, DCM, or reporting counterparty as soon as technologically practicable after discovery of the error or omission. These proposed requirements are intend to match the requirements in proposed § 45.14(b), but are also effectively the same as the requirements of current § 43.3(e).
                        <SU>229</SU>
                        <FTREF/>
                         These proposed requirements therefore do not require amendments to the collection.
                    </P>
                    <FTNT>
                        <P>
                            <SU>229</SU>
                             The Commission notes that proposed § 43.3(e)(2) does add provisions that are not present in current § 43.3(e)(1) to address the situation where a non-reporting counterparty does not know the identity of the reporting counterparty. The Commission does not believe that these additions have PRA implications, as the amount of information the non-reporting counterparty must provide and the frequency with which it must be provided remain the same as the current requirement and are de minimis. The only change is the requirement that non-reporting counterparties inform the SEF or DCM of errors, instead of the reporting counterparty. SEFs and DCMs have correction responsibilities under current § 43.3(e)(1) and proposed § 43.3(e)(2) does not change these responsibilities.
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 43.3(e)(1)(ii) does, however, include the new requirement for SEFs, DCMs, and reporting counterparties to notify the Director of DMO when errors or omissions cannot be corrected within three business days and, in such case, to provide the Director of DMO with an initial assessment of the errors and omissions and an initial remediation plan. This requirement would constitute a new collection of information. The Commission estimates that each SEF, DCM, and reporting counterparty would, on average need to provide notice and initial assessments to the Commission under proposed 
                        <PRTPAGE P="21077"/>
                        § 43.3(e)(1)(ii) once per year and that each instance would require 30 burden hours.
                        <SU>230</SU>
                        <FTREF/>
                         As there are approximately 1,729 SEFs, DCMs, and reporting counterparties that handle swaps, the Commission estimates an overall additional annual hours burden of 51,870 hours related to this requirement. This estimate is based on the Commission's experience with SEFs, DCMs, and reporting counterparties current practices regarding the reporting of errors and omissions, including the initial assessments and remediation plans that SEFs, DCMs, and reporting counterparties provide to the Commission under current practice. The Commission does not anticipate any one-time, initial burdens related to proposed § 43.3(e)(1)(ii).
                    </P>
                    <FTNT>
                        <P>
                            <SU>230</SU>
                             The Commission notes that, currently, it receives significantly less than one notice and initial assessment of reporting errors and omissions per SEF, DCM, or reporting counterparty per year, but is conservatively estimating one notice and initial assessment annually here, as the proposed requirements of § 45.14(a) may reveal more reporting errors to reporting counterparties that would then prompt corrections pursuant to proposed § 43.3(e).
                        </P>
                    </FTNT>
                    <P>The Commission is also proposing to remove paragraphs (f) and (g) from § 43.3 in order to move the requirements of these paragraphs to proposed § 49.28. Paragraphs (f) and (g) contain requirements for SDRs related to their operating hours. Proposed § 49.28 would include all of the current § 43.3(f) and (g) requirements, because this proposed deletion and move is intended to better organize regulations for SDRs by locating as many SDR requirements as possible in part 49 of the Commission's regulations. Moving the requirements would modify collections 3038-0070 and 3038-0086 because it will remove these recordkeeping requirements from part 43 of the Commission's regulations and add them to part 49 of the Commission's regulations. The Commission estimates that the public notice requirements of § 43.3(f) and (g) require SDRs to issue three notices per year and spend five hours creating and disseminating each notice, for a total of 15 hours annually for each SDR, for a total of 45 annual burden hours being moved across all three SDRs. As a result, the Commission estimates that moving these requirements would result in a total reduction of 45 annual burden hours for SDRs in collection 3038-0070.</P>
                    <P>The Commission therefore estimates that the total overall burdens for updated Information Collection 3038-0070 will be as follows:</P>
                    <P>
                        <E T="03">Estimated number of respondents affected:</E>
                         1,732 SEFs, DCMs, DCOs, SDRs, and reporting counterparties.
                    </P>
                    <P>
                        <E T="03">Estimated annual number of responses per respondent:</E>
                         21,247.
                    </P>
                    <P>
                        <E T="03">Estimated total annual responses:</E>
                         36,799,804.
                    </P>
                    <P>
                        <E T="03">Estimated burden hours per response:</E>
                         0.033.
                    </P>
                    <P>
                        <E T="03">Estimated total annual burden hours per respondent:</E>
                         701.
                    </P>
                    <P>
                        <E T="03">Estimated aggregate total burden hours for all respondents:</E>
                         1,214,392.
                    </P>
                    <HD SOURCE="HD3">
                        3. Revisions to Collection 3038-0086 (SDR Registration and Regulatory Requirements) 
                        <SU>231</SU>
                        <FTREF/>
                    </HD>
                    <FTNT>
                        <P>
                            <SU>231</SU>
                             The Commission is also proposing to reduce the number of SDRs used in collection 3038-0086 to calculate burdens and costs from 4 to 3. There are currently three SDRs provisionally registered with the Commission. The Commission has not received any applications for SDR registration since 2012.
                        </P>
                    </FTNT>
                    <P>The Commission proposes to revise collection 3038-0086 to account for changes in certain SDR responsibilities under proposed amendments to §§ 49.3, 49.5, 49.6, 49.9, 49.10, 49.11, 49.13, and 49.26, and to the proposed addition of §§ 49.28, 49.29, and 49.30. The estimated hours burdens and costs provided below would be in addition to or subtracted from the existing hours burdens and costs in collection 3038-0086. The Commission also describes a number of proposed changes to sections that do not have PRA implications below, for clarity purposes.</P>
                    <P>The Commission will also reduce the estimated number of SDRs from four to three, as there are currently three SDRs provisionally registered with the Commission that would be subject to the proposed collection requirements.</P>
                    <HD SOURCE="HD3">i. Amended § 49.3</HD>
                    <P>
                        The proposed amendments to § 49.3(a)(5) would remove the requirement for each SDR to file an annual amendment to its Form SDR and, once an SDR's application for registration is granted, the requirement for SDRs to amend the Form SDR whenever any of the information in the Form SDR becomes inaccurate. The proposed amendments would reduce the PRA burden for SDRs by lowering the number of filings required for each SDR. The Commission estimates that the PRA burden for each SDR would remain at 15 hours per filing, but that the number of filings per year would be reduced from three to two, meaning that the proposed amendments to § 49.3(a)(5) would reduce the burden on SDRs by 15 hours per year, for a total reduction of 45 annual burden hours across all three SDRs. This estimate is based on the Commission's experience with current SDR practices and the original supporting statement for collection 3038-0086.
                        <SU>232</SU>
                        <FTREF/>
                         The Commission does not anticipate any one-time, initial burden changes related to proposed § 49.3(a)(5).
                    </P>
                    <FTNT>
                        <P>
                            <SU>232</SU>
                             The original supporting statement for collection 3038-0086 estimated that the requirements of current § 49.3(a)(5) would necessitate three filings per year and 15 hours per filing.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">ii. Amended § 49.5</HD>
                    <P>The proposed amendments to § 49.5 would require SDRs to file a notification with the Commission for each transaction involving the direct or indirect transfer of ten percent or more of the equity interest in the SDR within ten business days of the firm obligation to transfer the equity interest, to provide the Commission with supporting documentation for the transaction on request, and to file a certification with the Commission that the SDR will meet all of its obligations under the Act and the Commission's regulations within two business days of the completion of the equity interest transfer. The Commission estimates that the requirements of proposed § 49.5 would create a burden of 15 hours per SDR for each qualifying equity interest transfer. Equity interest transfers for SDR are rare, so the Commission conservatively estimates that each SDR would provide information pursuant to proposed § 49.5 no more often than once every three years. As a result, the estimated average annual PRA burden related to proposed § 49.5 would be 5 hours per SDR, or 15 hours total for all three SDRs. The Commission does not anticipate any one-time, initial burdens related to proposed § 49.5.</P>
                    <HD SOURCE="HD3">iii. Amended § 49.6</HD>
                    <P>
                        The proposed amendments to § 49.6 would require an SDR seeking to transfer its registration to another legal entity due to a corporate change to file a request for approval with the Commission before the anticipated corporate change, including the specific documents and information listed in proposed § 49.6(c). The Commission estimates that the requirements of proposed § 49.6 would create a burden of 15 hours per SDR for each transfer of registration. Transfers of registration for SDR are rare, so the Commission conservatively estimates that each SDR would provide information pursuant to proposed § 49.6 no more often than once every three years. As a result, the estimated average annual PRA burden related to proposed § 49.6 would be 5 hours per SDR, or 15 hours total for all three SDRs. The Commission does not anticipate any one-time, initial burdens related to proposed § 49.6.
                        <PRTPAGE P="21078"/>
                    </P>
                    <HD SOURCE="HD3">iv. Amended § 49.9</HD>
                    <P>The proposed amendments to § 49.9 would remove the current text of the section and replace it with requirements related to SDRs providing open swaps reports to the Commission. The new § 49.9 would require SDRs to provide reports to the Commission with swap data for every open swap an SDR maintains, as instructed by the Commission. The instructions may include the method, timing, frequency, and format of the open swaps reports.</P>
                    <P>The Commission estimates that SDRs would incur a one-time initial burden of 250 hours per SDR for SDRs to create or modify their systems to provide the open swaps reports to the Commission as instructed, for a total estimated hours burden of 750 hours. This burden may be mitigated by the fact that SDRs currently have systems in place to provide similar information to the Commission, which would reduce the effort needed to create or modify SDR systems. The Commission additionally estimates 30 hours per SDR annually to perform any needed maintenance or adjustments to SDR reporting systems.</P>
                    <P>The Commission expects that the process for providing the open swaps reports to the Commission would be largely automated and therefore estimates a burden on the SDRs of 2 hours per report. Though the Commission is not prescribing the frequency of the open swaps reports at this time, the Commission estimates, only for the purposes of this burden calculation, that the SDRs would provide the Commission with 365 open swaps reports per year, meaning that the estimated ongoing annual additional hours burden for generating the open swaps reports and providing the reports to the Commission is 730 hours per SDR.</P>
                    <P>The Commission therefore estimates a total ongoing additional annual hours burden related to proposed § 49.9 of 760 hours per SDR, for a total estimated ongoing annual burden of 2,280 hours.</P>
                    <HD SOURCE="HD3">v. Amended § 49.10</HD>
                    <P>Proposed § 49.10(e) would require SDRs to accept, process, and disseminate corrections to SDR data errors and omissions. Proposed § 49.10(e) would also require SDRs to have policies and procedures in place to accomplish the corrections.</P>
                    <P>The Commission estimates that SDRs would incur a one-time initial burden of 100 hours per SDR to update and implement the systems, policies, and procedures necessary to complete the corrections process, for a total increased initial hours burden of 300 hours across all three SDRs. This burden may be mitigated by the fact that SDRs already have systems, policies, and procedures in place to accomplish corrections to SDR data and that the SDRs currently make such corrections on a regular basis. The Commission additionally estimates 30 hours per SDR annually to perform any needed maintenance on correction systems and to update corrections policies and procedures as needed.</P>
                    <P>The Commission anticipates that the process for SDRs to perform corrections would be largely automated, as this is the case with current SDR corrections. Based on swap data available to the Commission and discussions with the SDRs, the Commission estimates that an SDR would perform an average of approximately 2,652,000 data corrections per year. Based on the same information, the Commission estimates that performing each correction would require 2 seconds from an SDR. As a result, the Commission estimates that the ongoing burden of performing the actual corrections to SDR data would be approximately 1,473 hours per SDR annually, on average.</P>
                    <P>The Commission therefore estimates a total additional ongoing hours burden related to proposed § 49.10(e) of 1,503 hours per SDR annually, for a total estimated ongoing burden of 4,509 hours.</P>
                    <HD SOURCE="HD3">vi. Amended § 49.11</HD>
                    <P>
                        The proposed amendments to § 49.11 modify the existing obligations on SDRs to confirm the accuracy and completeness of swap data. Proposed § 49.11(b) would require SDRs to distribute open swaps reports to reporting counterparties on a weekly or monthly basis, depending on the registration status of a reporting counterparty. Proposed § 49.11(c) would require SDRs to receive a verification of data accuracy or a notice of discrepancy from the reporting counterparties in order to complete the verification process. Proposed § 49.11(a) and § 49.11(d) 
                        <SU>233</SU>
                        <FTREF/>
                         do not have PRA implications beyond the burdens discussed for paragraphs (b) and (c) below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>233</SU>
                             The Commission notes that requirements of part 40 of the Commission's regulations would apply to SDRs amending their verification policies and procedures regardless of proposed § 49.11(d), because verification policies and procedures would fall under the part 40 definition of a “rule.” 
                            <E T="03">See</E>
                             17 CFR 40.1(i) (definition of rule for the purposes of part 40). PRA implications for proposed § 49.11(d) would be included under the existing approved PRA collection for part 40 of the Commission's regulations.
                        </P>
                    </FTNT>
                    <P>While SDRs are already required to confirm the accuracy and completeness of swap data under current § 49.11, the Commission anticipates that the requirements in proposed § 49.11 would impose different burdens on the SDRs than the current regulation. The Commission estimates that each SDR would incur an initial, one-time burden of 500 hours to build, test, and implement updated verification systems that would generate and disseminate the open swaps reports and receive the verifications of data accuracy or notices of discrepancy, for a total of 1,500 initial burden hours across all SDRs. The Commission also estimates 50 hours per SDR annually for SDRs to maintain their verification systems and make any needed updates to verification policies and procedures required under proposed § 49.11(a) and (c).</P>
                    <P>Currently, SDRs are required to confirm swap data by contacting both counterparties for swaps that are not submitted by a SEF, DCM, DCO, or third-party service provider every time the SDR receives swap data related to the swap. For swaps reported by a SEF, DCM, DCO, or third-party service provider, the SDRs must currently assess the swap data to form a reasonable belief that the swap data is accurate every time swap data is submitted for a swap. Under proposed § 49.11(b) and (c), SDRs would only generate the open swaps reports at most once a week for any reporting counterparty, regardless of how often swap data is submitted for an open swap, and would only be required to provide the open swaps reports to the reporting counterparties, without needing to contact the non-reporting counterparty or evaluate the swap data. The Commission also anticipates, based on discussions with SDRs and other market participants, that the verification process would be largely automated once the processes are in place.</P>
                    <P>At maximum, the SDRs would be required to create open swaps reports for the 117 SD/MSP/DCO reporting counterparties every week (6,084 reports per year) and open swaps reports for the 1,585 non-SD/MSP/DCO reporting counterparties every month (19,020 reports per year) for a total of 25,104 reports per year overall. The Commission estimates that creating each report would require 2 hours, for a total of 50,208 hours per SDR per year or 150,624 hours overall across all SDRs.</P>
                    <HD SOURCE="HD3">vii. Amended § 49.12</HD>
                    <P>
                        Proposed amendments to § 49.12(a) and (b) would incorporate existing SDR recordkeeping obligations from § 45.2(f) and (g) respectively, which are already applicable to SDRs under current § 49.12(a). As the recordkeeping 
                        <PRTPAGE P="21079"/>
                        requirements being moved from § 45.2 already apply to SDRs under current § 49.12, the Commission does not believe that amended § 49.12(a) or (b) would require any revision to hours burden related to § 49.12 already included in collection 3038-0086. Proposed amendments to § 49.12(c) would require SDRs to maintain records of data validation errors and of data reporting errors, which would include records of data subsequently corrected by a SEF, DCM, or reporting counterparty pursuant to parts 43, 45, and 46. Proposed § 49.12(c) does not however add any new requirement to part 49, as all of the records to be kept would already be required to be kept by existing recordkeeping obligations as data submitted under parts 43, 45, or 46. As a result, the Commission does not believe that amended § 49.12(c) would require an additional PRA burden beyond that already included in collection 3038-0086.
                    </P>
                    <HD SOURCE="HD3">viii. Amended § 49.13</HD>
                    <P>Proposed § 49.13(a) would require SDRs to monitor, screen, and analyze SDR data in the form and manner determined by the Commission. This would involve generating reports and other information at the request of the Commission by calculating or compiling information and SDR data maintained by the SDR. Proposed § 49.13(b) would require SDRs to have sufficient resources to perform such obligations. The Commission proposes to amend existing collection 3038-0086 to account for any burdens associated with responding to Commission requests to monitor, screen, and analyze SDR data. While SDRs are currently required to perform monitoring, screening, and analyzing tasks as required by the Commission, the proposed amendments would facilitate more frequent requests from the Commission, which may increase the burden on SDRs. The Commission anticipates that requests would be both one-time requests and requests to establish periodic reports. The Commission estimates that it would make 10 new requests per SDR per year, and that each request would require an average of 40 hours to respond, for a total burden of 400 hours per SDR per year, or 1,200 hours per year overall. The Commission anticipates that the number of new requests would decrease over time as the Commission's resources for utilizing SDR data improve. The Commission does not anticipate any one-time, initial burdens related to proposed § 49.13(a).</P>
                    <P>Proposed § 49.13(c) would require SDRs to notify the Commission of any SDR data that the SDR receives that is not reported in accordance with parts 43, 45, or 46, as applicable. Currently, under § 49.15(c), SDRs are only required to notify the Commission when swap transaction and pricing data is not reported in compliance with the obligations under part 43. Proposed § 49.13(c) would expand this obligation to also include SDRs notifying the Commission when a transaction is reported that is not in accordance with part 45 or part 46. The Commission anticipates that the notification provisions in proposed § 49.13(c) would create little or no PRA burden on SDRs beyond those existing under current § 49.15(c), as the SDRs would already have the necessary systems and procedures in place due to the existing requirements in current § 49.15(c).</P>
                    <HD SOURCE="HD3">ix. Amended § 49.26</HD>
                    <P>Proposed new § 49.26(j) would require SDRs to provide their users and potential users with the SDR's policies and procedures on reporting SDR data, including SDR data validation procedures, swap data verification procedures, and SDR data correction procedures. The Commission anticipates that SDRs would incur a one-time burden of 20 burden hours to draft written documents that they would provide to their users and potential users, for a total increase of 60 one-time burden hours across SDRs. The Commission also anticipates that SDRs would update their policies once per year and incur a recurring burden of 10 hours annually from providing any updated reporting policies and procedures to their users and potential users, as needed, for a total increase of 30 ongoing burden hours across SDRs.</P>
                    <HD SOURCE="HD3">x. New § 49.28</HD>
                    <P>Proposed new § 49.28 incorporates existing provisions of § 43.3(f) and (g) with respect to hours of operation with minor changes and clarifications. Proposed § 49.28 extends the provisions of current § 43.3(f) and (g) to include all SDR data and clarifies the different treatment of regular closing hours and special closing hours. SDRs currently have closing hours systems, policies, and procedures that apply to all SDR functions and all SDR data under the current requirements. The proposed requirements related to declaring regular closing hours and special closing hours would also effectively follow current requirements, without necessitating changes to current SDR systems or practices. The Commission does however anticipate that the SDRs would need to issue notices to the public related to closing hours under proposed § 49.28(a) and (c). The Commission estimates that each SDR would issue three notices per year and spend five hours creating and disseminating each notice, for a total of 15 hours per year preparing and providing public notices per SDR, and a total of 45 hours per year across all SDRs.</P>
                    <HD SOURCE="HD3">xi. New § 49.29</HD>
                    <P>Proposed new § 49.29 would require each SDR to provide, upon request by the Commission, information relating to its business as an SDR, and such other information that the Commission needs to perform its regulatory duties. This provision also requires each SDR, upon request by the Commission, to provide a written demonstration of compliance with the SDR core principles and other regulatory obligations. The PRA burden associated with such responses is dependent on the number of requests made and the complexity of such requests. Based on its experience with requests to DCMs, the Commission would estimate that each SDR would likely receive on average between three and five requests per year, considering that an SDR is a newer type of registered entity than a DCM. The Commission anticipates that the number of requests would decrease over time. The Commission also anticipates that each such request would require the SDR to spend 20 hours to gather information and formulate a response, and bases its estimate of burden hours assuming five such requests per year, for a total additional hours burden of 100 hours per SDR per year, or 300 hours per year across all SDRs. The Commission does not anticipate that SDRs would incur any one-time hours burden or costs in complying with this regulation.</P>
                    <P>The Commission therefore estimates that the total overall burdens for updated Information Collection 3038-0086 will be as follows:</P>
                    <P>
                        <E T="03">Estimated number of respondents affected:</E>
                         3 SDRs.
                    </P>
                    <P>
                        <E T="03">Estimated annual number of responses per respondent:</E>
                         154,327,169.
                    </P>
                    <P>
                        <E T="03">Estimated total annual responses:</E>
                         462,981,508.
                    </P>
                    <P>
                        <E T="03">Estimated burden hours per response:</E>
                         0.0006.
                    </P>
                    <P>
                        <E T="03">Estimated total annual burden hours per respondent:</E>
                         99,197.
                    </P>
                    <P>
                        <E T="03">Estimated aggregate total burden hours for all respondents:</E>
                         297,526.
                    </P>
                    <HD SOURCE="HD3">4. Request for Comment</HD>
                    <P>
                        The Commission invites the public and other Federal agencies to comment on any aspect of the proposed information collection requirements discussed above. The Commission will 
                        <PRTPAGE P="21080"/>
                        consider public comments on this proposed collection of information in:
                    </P>
                    <P>(1) Evaluating whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information will have a practical use;</P>
                    <P>(2) evaluating the accuracy of the estimated burden of the proposed collection of information, including the degree to which the methodology and the assumptions that the Commission employed were valid;</P>
                    <P>(3) enhancing the quality, utility, and clarity of the information proposed to be collected; and</P>
                    <P>
                        (4) minimizing the burden of the proposed information collection requirements on registered entities, including through the use of appropriate automated, electronic, mechanical, or other technological information collection techniques, 
                        <E T="03">e.g.,</E>
                         permitting electronic submission of responses.
                    </P>
                    <P>
                        Copies of the submission from the Commission to OMB are available from the CFTC Clearance Officer, 1155 21st Street NW, Washington, DC 20581, (202) 418-5160 or from 
                        <E T="03">http://RegInfo.gov.</E>
                         Organizations and individuals desiring to submit comments on the proposed information collection requirements should send those comments to:
                    </P>
                    <P>• The Office of Information and Regulatory Affairs, Office of Management and Budget, Room 10235, New Executive Office Building, Washington, DC 20503, Attn: Desk Officer of the Commodity Futures Trading Commission;</P>
                    <P>• (202) 395-6566 (fax); or</P>
                    <P>
                        • 
                        <E T="03">OIRAsubmissions@omb.eop.gov</E>
                         (email).
                    </P>
                    <P>
                        Please provide the Commission with a copy of submitted comments so that all comments can be summarized and addressed in the final rulemaking, and please refer to the 
                        <E T="02">ADDRESSES</E>
                         section of this rulemaking for instructions on submitting comments to the Commission. OMB is required to make a decision concerning the proposed information collection requirements between 30 and 60 days after publication of this Release in the 
                        <E T="04">Federal Register</E>
                        . Therefore, a comment to OMB is best assured of receiving full consideration if OMB receives it within 30 calendar days of publication of this Release. Nothing in the foregoing affects the deadline enumerated above for public comment to the Commission on the proposed rules.
                    </P>
                    <HD SOURCE="HD2">C. Cost-Benefit Considerations</HD>
                    <HD SOURCE="HD3">1. Introduction</HD>
                    <P>
                        Section 15(a) 
                        <SU>234</SU>
                        <FTREF/>
                         of the CEA requires the Commission to consider the costs and benefits of its actions before promulgating a regulation under the CEA or issuing certain orders. Section 15(a) further specifies that the costs and benefits shall be evaluated in light of five broad areas of market and public concern: (1) Protection of market participants and the public; (2) efficiency, competitiveness, and financial integrity of markets; (3) price discovery; (4) sound risk management practices; and (5) other public interest considerations. The Commission considers the costs and benefits resulting from its discretionary determinations with respect to the section 15(a) factors.
                    </P>
                    <FTNT>
                        <P>
                            <SU>234</SU>
                             7 U.S.C. 19(a).
                        </P>
                    </FTNT>
                    <P>
                        In this release, the Commission is proposing revisions to existing regulations in parts 23, 43, 45, and 49. The Commission also is proposing new regulations in part 49. Together, these proposed revisions and additions are intended to address swap data verification and to improve the quality of data reporting generally. Some of the proposed amendments are substantive. A number of amendments, however, are non-substantive or technical, and therefore would not have associated cost-benefits implications.
                        <SU>235</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>235</SU>
                             The Commission believes there are no cost-benefit implications for proposed §§ 49.2, 49.15, 49.16, 49.18, 49.20, 49.24, and 49.31.
                        </P>
                    </FTNT>
                    <P>To the extent costs are quantifiable, they have been discussed in two places: The PRA section in this release and in the PRA-related information collection requests filed with OMB. In general, however, given the small number of existing SDRs and their differences in size and operations, many of the costs associated with this proposed rulemaking were not readily quantifiable without relying on and potentially divulging confidential information. The Commission therefore specifically requests comments to help quantify the costs of this rulemaking.</P>
                    <HD SOURCE="HD3">2. Background</HD>
                    <P>In 2011, the Commission issued the Part 49 Adopting Release. The duties and requirements included in the Part 49 Adopting Release require SDRs to, among other requirements, accept and confirm data reported to the SDRs. The Commission also believed that the Commission would be better able to monitor the overall swaps market and individual market participants through SDR collection and maintenance of swap data as required in parts 45 and 49. Before the adoption of the Dodd-Frank Act and its implementing regulations, the swaps market generally, and transactions and positions of individual market participants in particular, were not transparent to regulators or to the public.</P>
                    <P>
                        Due to these requirements for SDRs to collect and maintain SDR data, the Commission has now had the opportunity to work directly with SDR data reported to, and held by, SDRs. Based on its experience working with SDR data, along with extensive feedback received from market participants, the Commission believes that improving data quality would help enhance the data's usefulness. In this release, the Commission has focused on the operation and implementation of CEA section 21,
                        <SU>236</SU>
                        <FTREF/>
                         which contains requirements related to SDRs, including the requirement to confirm data.
                        <SU>237</SU>
                        <FTREF/>
                         The Commission is also proposing to modify a number of other regulations for clarity and consistency and to enhance the Commission's ability to monitor and supervise the swaps market.
                    </P>
                    <FTNT>
                        <P>
                            <SU>236</SU>
                             
                            <E T="03">See</E>
                             7 U.S.C. 24a.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>237</SU>
                             
                            <E T="03">See</E>
                             7 U.S.C. 24a(c)(2).
                        </P>
                    </FTNT>
                    <P>Prior to discussing the proposed rule changes, the Commission describes below the current environment that would be impacted by these changes. Three SDRs are currently provisionally registered with the Commission: CME, DDR, and ICE.</P>
                    <P>Each SDR has unique characteristics and structures that determine how the proposed rule changes would impact its operations. For example, SDRs affiliated with DCOs tend to receive a large proportion of their SDR data from swaps cleared through those affiliated DCOs, while independent SDRs tend to receive SDR data from a wider range of market participants.</P>
                    <P>The current reporting environment also involves third-party service providers. These entities assist market participants with fulfilling the applicable data reporting requirements, though the reporting requirements do not apply to third-party service providers directly.</P>
                    <P>
                        Given that data quality depends on the underlying data reporting requirements, the proposed changes should be considered in context with other planned improvements to parts 43 and 45. As discussed in the Roadmap, the Commission is in the process of improving data reporting requirements, including modifying the requirements to be more clear and consistent with other regulators' requirements. The amendments proposed in this 
                        <PRTPAGE P="21081"/>
                        rulemaking are one part of this larger effort to ensure that better-quality data is available to market participants and the Commission.
                    </P>
                    <P>
                        Current regulations have not created results that meet the Commission's expectations for data quality. For example, current regulations do not include a specific affirmative obligation for swap counterparties to review reported swap data for errors, but instead require swap counterparties to correct errors and omissions only after the discovery of inaccurate data.
                        <SU>238</SU>
                        <FTREF/>
                         The result has been that market participants too often have not acted to review and correct reported swap data. It is not uncommon for Commission staff to find discrepancies between open swaps information available to the Commission and reported data for the same swaps. In the processing of swap data to generate the CFTC's Weekly Swaps Report,
                        <SU>239</SU>
                        <FTREF/>
                         for example, there are instances when the notional amount differs between the Commission's open swaps information and the swap data reported for the same swap. Other common examples of discrepancies include incorrect references to an underlying currency, such as a notional value incorrectly linked to U.S. dollars instead of Japanese Yen. These examples, among others, strongly suggest a need for better verification of reported swap data. Improved verification could lead to these errors being discovered and corrected in a timely manner.
                    </P>
                    <FTNT>
                        <P>
                            <SU>238</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.3(e); 17 CFR 45.14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>239</SU>
                             
                            <E T="03">See</E>
                             CFTC's Weekly Swaps Report, 
                            <E T="03">https://www.cftc.gov/MarketReports/SwapsReports/index.htm.</E>
                        </P>
                    </FTNT>
                    <P>
                        SDR policies and procedures have also created additional challenges for swap data accuracy. As discussed above, certain SDR policies and procedures for swap data have been based on negative affirmation, 
                        <E T="03">i.e.,</E>
                         predicated on the concept that reported swap data is accurate and confirmed if a reporting counterparty does not inform the SDR of errors or omissions, or otherwise make subsequent modifications to data reported for a swap within a certain period of time.
                        <SU>240</SU>
                        <FTREF/>
                         As reporting counterparties are typically not reviewing their reported swap data maintained by the SDRs, the data is effectively assumed to be accurate and errors and omissions are not sufficiently discovered and corrected. As described in more detail in the section VII.C.8.iii discussion of price discovery below, the volume of inaccurate swap data that is discovered by market participants or the Commission shows that current regulations are insufficient to produce the quality of swap data the Commission expects and needs to fulfill its regulatory responsibilities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>240</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.11(b)(1)(ii) and (b)(2)(ii).
                        </P>
                    </FTNT>
                    <P>Based on its experience with data reporting, the Commission believes that certain regulations, particularly in parts 43, 45, and 49, should be amended to improve swap data accuracy and completeness. The regulatory changes being proposed to meet this objective include requiring SDRs and reporting counterparties to verify the accuracy and completeness of reported swap data. Many of the proposed regulations have costs and benefits that must be considered. These will be discussed individually below.</P>
                    <P>This release also includes amendments to part 49 to improve and streamline the Commission's oversight of SDRs. These proposed regulations include allowing the Commission to request demonstrations of compliance and other reports from SDRs.</P>
                    <P>
                        For each proposed amendment discussed below, the Commission summarizes the changes,
                        <SU>241</SU>
                        <FTREF/>
                         and identifies and discusses the costs and benefits attributable to the proposed changes. The Commission then considers alternatives to the rules proposed in this release. Finally, the Commission considers the costs and benefits of all of the proposed rules jointly in light of the five public interest considerations in CEA section 15(a).
                    </P>
                    <FTNT>
                        <P>
                            <SU>241</SU>
                             As described throughout this release, the Commission is also proposing a number of non-substantive, conforming rule amendments in this release, such as renumbering certain provisions and modifying the wording of existing provisions. Non-substantive amendments of this nature may be described in the cost-benefit portion of this release, but the Commission will note that there are no costs or benefits to consider.
                        </P>
                    </FTNT>
                    <P>
                        The Commission notes that this consideration of costs and benefits is based on the understanding that the swaps market functions internationally. Many swaps transactions involving U.S. firms occur across international borders and some Commission registrants are organized outside of the United States, with leading industry members often conducting operations both within and outside the United States, and with market participants commonly following substantially similar business practices wherever located. Where the Commission does not specifically refer to matters of location, the discussion of costs and benefits refers to the proposed rules' effects on all swaps activity, whether by virtue of the activity's physical location in the United States or by virtue of the activity's connection with or effect on U.S. commerce under CEA section 2(i).
                        <SU>242</SU>
                        <FTREF/>
                         The Commission contemplated this cross-border perspective in 2011 when it adopted § 49.7, which applies to trade repositories located in foreign jurisdictions.
                        <SU>243</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>242</SU>
                             
                            <E T="03">See</E>
                             7 U.S.C. 2(i). CEA section 2(i) limits the applicability of the CEA provisions enacted by the Dodd-Frank Act, and Commission regulations promulgated under those provisions, to activities within the U.S., unless the activities have a direct and significant connection with activities in, or effect on, commerce of the U.S.; or contravene such rules or regulations as the Commission may prescribe or promulgate as are necessary or appropriate to prevent the evasion of any provision of the CEA enacted by Dodd-Frank Act. Application of section 2(i)(1) to the existing regulations under part 45 with respect to SDs/MSPs and non-SD/MSP counterparties is discussed in the Commission's Interpretive Guidance and Policy Statement Regarding Compliance With Certain Swap Regulations, 78 FR 45292 (July 26, 2013).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>243</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.7.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Baseline</HD>
                    <P>There are separate baselines for the costs and benefits that might arise from the proposed regulations in this release. The Commission believes that for proposed paragraphs (c) added to §§ 23.204 and 23.205, the baseline is the current practice. The baseline for proposed § 45.14 is current § 45.14. The baseline for proposed amendments to current part 49 regulations is the existing part 49 and current practices. For proposed § 49.12, the baseline is current § 49.12, as well as § 45.2(f) and (g), which would be replaced by proposed § 49.12. For proposed § 49.17, the baseline is current §§ 49.17 and 45.13.</P>
                    <P>In this release, the Commission is proposing to adopt four new regulations: §§ 49.28, 49.29, 49.30, and 49.31. For proposed new § 49.28 the baseline is current § 43.3(f) and (g), because the requirements in § 43.3(f) and (g) are being moved to proposed § 49.28. For proposed new §§ 49.29 and 49.30, the baselines are current practices. Proposed new § 49.31 concerns internal Commission practices and is not subject to consideration of costs and benefits.</P>
                    <HD SOURCE="HD3">4. Costs and Benefits of Proposed Amendments to Part 49</HD>
                    <HD SOURCE="HD3">i. § 49.3—Procedures for Registration</HD>
                    <P>
                        The Commission is proposing to amend § 49.3 to remove the requirements for SDRs to: (i) file an annual amendment to Form SDR; and (ii) amend Form SDR after the Commission grants the application for registration under § 49.3(a), as required in current § 49.3(a)(5). The Commission believes the annual filing requirement and the requirement to continuously update Form SDR once the application 
                        <PRTPAGE P="21082"/>
                        for registration has been granted currently in § 49.3(a)(5) are unnecessary for the Commission to successfully perform its regulatory functions.
                    </P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>The proposed amendments to § 49.3(a)(5) would benefit SDRs by reducing the amount of information that SDRs must provide to the Commission and the frequency with which the SDRs must provide the information. By removing the annual Form SDR amendment requirement and the requirement to update Form SDR after registration is granted, SDRs would be required to expend fewer resources to provide this information to the Commission. The Commission believes that current § 49.3(a)(5) is unnecessary as SDRs already submit much of the information in Form SDR in rule filings under part 40 or as required per other SDR regulations. The Commission also believes that this requirement would be unnecessary with new proposed § 49.29, which would provide the Commission with the ability to request the same information on an as-needed basis.</P>
                    <P>The costs of proposed § 49.3(a)(5) would not be significant and would largely be associated with any needed adjustments to SDRs policies and procedures related to reducing the number of updates to Form SDR.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.3(a)(5). Are there additional costs or benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of these benefits.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.3(a)(5). Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">ii. § 49.5—Equity Interest Transfers</HD>
                    <P>Proposed § 49.5(a) would require that SDRs: (i) Notify the Commission of each transaction involving the direct or indirect transfer of ten percent or more of the equity interest in the SDR; and (ii) provide the Commission with supporting documentation upon request.</P>
                    <P>Proposed § 49.5(b) would require that the notice in § 49.5(a) be filed electronically with the Secretary of the Commission and DMO at the earliest possible time but in no event later than the open of business ten business days following the date upon which a firm obligation is made for the equity interest transfer.</P>
                    <P>Proposed § 49.5(c) would require that upon the transfer, whether directly or indirectly, the SDR shall file electronically with the Secretary of the Commission and DMO a certification that the SDR meets all of the requirements of section 21 of the CEA and the Commission regulations, no later than two business days following the date on which the equity interest was acquired.</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>The Commission believes that the proposed amendments would benefit SDRs by lowering the burdens related to notifying the Commission of equity interest transfers and by extending the time SDRs have to file transfer-related materials with the Commission. The proposed changes lower the burdens by removing the obligations in current § 49.5(a) to update Form SDR for an SDR that has been granted registration under § 49.3(a) and in current § 49.5(b) to provide specific information to the Commission with the equity interest transfer notification and replacing them with the ability for the Commission to request supporting documentation for the transfer as needed under proposed § 49.5(a). This would likely result in SDRs only providing the information the Commission deems necessary for any particular equity interest transfer, which may not include all of the documents or information required by current § 49.5. The proposed amendments also lower the burdens on SDRs by extending the notification timing requirement under current § 49.5(a) from one business day to ten business days. More time would allow SDRs more flexibility in time and resources needed to file the required notice.</P>
                    <P>The costs of proposed § 49.5 would be lower than the current requirements and would largely be associated with any needed adjustments to SDRs policies and procedures related to notification of equity interest transfer and the resources needed to provide the Commission with requested documentation. The costs would also include any additional costs stemming from the inclusion of “indirect transfers” of equity ownership in proposed § 49.5. This could increase the costs to SDRs, if the inclusion of indirect transfers results in more frequent equity interest transfers and the associated need to provide information to the Commission, but the inclusion of indirect transfers would benefit the Commission by providing more insight into equity interest transfers that could affect the business of an SDR, even though the equity interest transfer does not involve the SDR directly. As equity interest transfers are rare occurrences and the Commission does not anticipate that including indirect transfers would result in substantially more equity interest transfers, the Commission expects these potential additional costs to be small.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.5. Are there additional costs or benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of these benefits.</P>
                    <P>The Commission requests comment on its consideration of alternatives to proposed § 49.5. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">iii. § 49.6—Request for Transfer of Registration</HD>
                    <P>Proposed § 49.6(a) would require an SDR seeking to transfer its SDR registration following a corporate change to file a request for approval to transfer the registration with the Secretary of the Commission in the form and manner specified by the Commission.</P>
                    <P>Proposed § 49.6(b) would specify that an SDR file a request for transfer of registration as soon as practicable before the anticipated corporate change. Proposed § 49.6(c) would set forth the information that must be included in the request for transfer of registration, including the documentation underlying the corporate change, the impact of the change on the SDR, governance documents, updated rulebooks, and representations by the transferee entity, among other things.</P>
                    <P>Proposed § 49.6(d) would specify that upon review of a request for transfer of registration, the Commission, as soon as practicable, shall issue an order either approving or denying the request for transfer of registration.</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>
                        The Commission believes that proposed § 49.6 would benefit SDRs by reducing the burdens on SDRs for successfully transferring an SDR registration to a successor entity. Proposed § 49.6 would require a more limited scope of information and representations from the transferor and 
                        <PRTPAGE P="21083"/>
                        transferee entities than current § 49.6, which requires a full application for registration on Form SDR, including all Form SDR exhibits. This limited scope of information and representations would require less time and resources to prepare and submit than the current requirements.
                    </P>
                    <P>The Commission does not believe that proposed § 49.6 would impose any additional costs on SDRs compared to the current requirement.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.6. Are there additional costs or benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of these benefits.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.6. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">iv. § 49.9—Open Swaps Reports Provided to the Commission</HD>
                    <P>Proposed § 49.9(a) would require SDRs to provide the Commission with open swaps reports that contain an accurate reflection of the swap data for every swap data field required to be reported under part 45 for every open swap maintained by the SDR. Proposed § 49.9(b) would require SDRs to transmit all open swaps reports to the Commission as instructed by the Commission.</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>The costs imposed by this proposed requirement would include the resources SDRs must use to develop the infrastructure to create and deliver the open swaps reports as instructed by the Commission. In practice, the costs are expected to be mitigated by the fact that SDRs currently send open swaps reports to the Commission on a regular basis, which would help limit the costs. The SDRs may incur some costs from needing to provide open swaps reports in the standardized format required by the Commission, but the Commission does not expect the format of these reports to change frequently.</P>
                    <P>The Commission believes the proposed amendments would standardize the reports SDRs already provide, which would ensure that the reports will be delivered in a usable format, which will assist the Commission's regulatory oversight efforts. The Commission believes the largest cost imposed by these amendments would be the upfront costs to implement open swaps reporting systems, with incremental costs to maintain or modify SDR systems on an ongoing basis. The underlying information contained in the reports would also be similar to information SDRs would be required to send to reporting counterparties for verification purposes under proposed § 49.11(b).</P>
                    <P>The Commission currently uses open swaps reports to create and publish Commission papers and reports, including the weekly swaps report. These reports benefit market participants by analyzing SDR data sourced directly from the SDRs. This information on open swaps is unique because it is not available to the public until the Commission publishes its reports. The Commission also believes that market participants would indirectly benefit from the improved data quality of open swaps that would result from proposed § 49.9, as the information in the reports would help the Commission to better perform its regulatory functions.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.9. Are there additional costs or benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of these benefits.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.9. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">v. § 49.10—Acceptance of Data</HD>
                    <P>New § 49.10(e) would require SDRs to correct errors and omissions in SDR data that was previously reported, or erroneously not reported, to SDRs. Proposed § 49.10(e)(1)-(4) would set forth the specific requirements SDRs would need to meet to fulfill the general requirement in § 49.10(e): (i) Accept corrections for errors and omissions reported to, or erroneously not reported to, the SDR; (ii) correct errors and omissions as soon as technologically practicable after receiving a report of the errors or omissions; (iii) disseminate corrected SDR data to the public and the Commission, as applicable, as soon as technologically practicable after correcting the SDR data; and (iv) establish, maintain, and enforce policies and procedures designed to fulfill its correction responsibilities under § 49.10(e)(1)-(3).</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>
                        Proposed § 49.10(e) could impose some costs on SDRs, but the Commission believes that the costs would not be significant and largely related to any needed updates to their error and omission correction systems. SDRs are currently required to identify cancellations, corrections, and omissions under parts 43 and 45.
                        <SU>244</SU>
                        <FTREF/>
                         Proposed § 49.10(e) is largely clarifying the SDRs' existing duties, and, for organizational purposes, placing the obligations in part 49, which is the Commission's main regulations governing SDRs. The costs of the proposed paragraph would be mitigated by the fact that SDRs currently routinely correct data errors and omissions and disseminate the corrections as required.
                    </P>
                    <FTNT>
                        <P>
                            <SU>244</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.3(e)(1), (3), (4); 17 CFR 45.14(c).
                        </P>
                    </FTNT>
                    <P>The Commission also expects there would be costs associated with establishing, maintaining, and enforcing the policies and procedures required by the proposed paragraph, but believes that these costs would not be significant and would be limited to initial creation costs and update costs for the policies and procedures as needed.</P>
                    <P>The Commission believes that one of the benefits from proposed § 49.10(e) is improved data quality resulting from collecting and disseminating accurate swap data. Proposed § 49.10(e) is intended to work in concert with proposed § 45.14 and proposed § 49.11, along with the data correction requirements of § 43.3(e). The Commission believes that market participants and the public would benefit from more complete and accurate swap transaction and pricing data that enhances price discovery. In addition, the Commission uses swap transaction and pricing data to produce public information on the swaps markets, such as the weekly swaps reports. The Commission also believes that market participants would benefit from the Commission using more accurate data to inform swaps markets policy and perform its other regulatory functions. SDRs would also benefit from greater clarity in their requirements to correct errors and omissions in SDR data.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>
                        The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.10. Are there additional costs and benefits that the Commission should 
                        <PRTPAGE P="21084"/>
                        consider? Commenters are encouraged to include both qualitative and quantitative assessments of these costs and benefits.
                    </P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.10. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">vi. § 49.11—Verification of Swap Data Accuracy</HD>
                    <P>Proposed § 49.11(a) would generally require that SDRs: (i) Verify the accuracy and completeness of swap data that the SDRs receive from SEFs, DCMs, and reporting counterparties, or third-party service providers acting on their behalf; and (ii) establish, maintain, and enforce policies and procedures reasonably designed to verify the accuracy and completeness of that swap data.</P>
                    <P>Proposed § 49.11(b) would require SDRs to regularly distribute to each reporting counterparty an open swaps report detailing the swap data maintained by the SDR that contains the same information provided to the Commission in an open swaps report under proposed § 49.9. Proposed § 49.11(b)(1) would require SDRs to distribute open swaps reports that accurately reflect the swap data the SDR maintains for each of a particular reporting counterparty's open swaps, unless other Commission regulations prohibit the disclosure of certain swap data.</P>
                    <P>Proposed § 49.11(b)(2) would require SDRs to distribute the open swaps reports to SD/MSP/DCO reporting counterparties on a weekly basis, no later than 11:59 p.m. Eastern Time on the day of the week that the SDR chooses to regularly distribute the open swaps reports. Proposed § 49.11(b)(3) would require SDRs to distribute the open swaps reports to non-SD/MSP/DCO reporting counterparties on a monthly basis, no later than 11:59 p.m. Eastern Time on the day of the month that the SDR chooses to regularly distribute the open swaps reports.</P>
                    <P>Proposed § 49.11(c) would require SDRs to receive from each reporting counterparty to which it sends an open swaps report, in response to the open swaps report, either a verification of data accuracy signifying that the swap data contained in the distributed open swaps report is accurate and complete or a notice of discrepancy signifying that the swap data in the open swaps report contains one or more errors or omissions. Proposed § 49.11(c) would also require SDRs to establish, maintain, and enforce policies and procedures reasonably designed for the SDR to receive the notices.</P>
                    <P>Proposed § 49.11(d) would require SDRs to comply with the requirements under part 40 of the Commission's regulations when creating and amending their verification policies and procedures.</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>The costs associated with the proposed amendments to § 49.11 would largely be borne by the three existing SDRs. The Commission expects that SDRs would incur initial costs from establishing systems to generate open swaps reports and to successfully distribute these reports to all reporting counterparties. The Commission also expects SDR to incur recurring costs related to any needed adjustments to their systems over time and to accommodate the arrival or departure of reporting counterparties. SDRs would also incur the cost of generating and distributing the particular open swaps reports, and receiving the responses from the reporting counterparties, but does not believe these changes would be significant because, based on discussions with the SDRs and other market participants, the Commission believes SDRs would largely automate the verification process.</P>
                    <P>The Commission believes that the benefits of the proposed amendments to § 49.11 would result from verification improving data accuracy and completeness. When paired with the proposed requirements of § 45.14 and the correction requirements of § 43.3(e), verification would alert reporting counterparties to errors and omission in SDR data for their open swaps. Reporting counterparties would be required to correct any errors or omissions discoverable in the open swaps reports the SDRs provide, including errors in trade-specific details, such as notional amounts and price. The Commission believes that SDRs and reporting counterparties would benefit from having clearer regulations.</P>
                    <P>The Commission also believes that the proposed verification requirements would improve the Commission's ability to monitor, measure, and regulate the swaps market, such as using more accurate data to improve monitoring for potential systemic risks and surveillance for potential threats to market integrity.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.11. Are there additional costs and benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of these costs and benefits.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.11. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">vii. § 49.12—Swap Data Repository Recordkeeping Requirements</HD>
                    <P>Proposed § 49.12(a) would require that SDRs keep full, complete, and systematic records, together with all pertinent data and memoranda, of all activities relating to the business of the SDR, including, but not limited to, all SDR information and all SDR data reported to the SDR.</P>
                    <P>Proposed § 49.12(b)(1) would require that an SDR maintain all SDR information received by the SDR in the course of its business. Proposed § 49.12(b)(2) would require an SDR to maintain all SDR data and timestamps, and all messages to and from an SDR related to SDR data reported to the SDR throughout the existence of the swap to which the SDR data relates and for five years following final termination of the swap, during which time the records must be readily accessible by the SDR and available to the Commission via real-time electronic access, and then for an additional period of at least ten years in archival storage from which such records are retrievable by the SDR within three business days.</P>
                    <P>Proposed § 49.12(c) would require SDRs to create and maintain records of errors related to SDR data validations and errors related to SDR data reporting. Proposed § 49.12(c)(1) would require an SDR to create and maintain an accurate record of all SDR data that fails to satisfy the SDR's data validation procedures. Proposed § 49.12(c)(2) would require an SDR to create and maintain an accurate record of all SDR data errors and omissions reported to the SDR and all corrections disseminated by the SDR pursuant to parts 43, 45, and 46. SDRs must make the records available to the Commission on request.</P>
                    <P>
                        Proposed § 49.12(d) would contain the requirements of current § 49.12(c) and would require that: (i) All records required to be kept pursuant to part 49 must be open to inspection upon request by any representative of the Commission or any representative of the U.S. Department of Justice; and (ii) an SDR must produce any record required 
                        <PRTPAGE P="21085"/>
                        to be kept, created, or maintained by the SDR in accordance with § 1.31.
                    </P>
                    <P>Finally, the Commission is proposing a non-substantive change to incorporate the current requirements of § 49.12(e) into the revised requirements of SDRs to monitor, screen, and analyze SDR data under § 49.13. This non-substantive change does not have any cost or benefit implications.</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>The costs of proposed amendments to § 49.12 would primarily be incurred by the three existing SDRs as they make any needed adjustments to create and maintain all required records. The Commission does not believe these costs would be significant, as the recordkeeping requirements in proposed § 49.12 are largely similar to the requirements in current § 49.12 and current § 45.2(f) and (g). The proposed § 49.12(c) requirements are intended to serve as specific examples of records required to be created and maintained pursuant to current requirements and proposed § 49.12, in order to emphasize the importance of retaining records related to reporting errors, and would include such information as all reported SDR data and reports of errors and omissions. Proposed § 49.12(d) further specifies that SDRs must make all records included in proposed § 49.12 available to the Commission on request, which is the current requirement applicable to SDR in current § 45.2(h) and current § 49.12(c).</P>
                    <P>
                        Finally, the proposed amendments to § 49.12 related to SDR information would be substantially similar to the SEC's requirements for its SBSDRs.
                        <SU>245</SU>
                        <FTREF/>
                         The Commission expects that there would be substantial overlap in these requirements for SDRs that are also SBSDRs and these entities would be able to leverage resources to reduce any duplicative costs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>245</SU>
                             
                            <E T="03">See</E>
                             17 CFR 240.13n-7 (detailing the SBSDR recordkeeping requirements).
                        </P>
                    </FTNT>
                    <P>The Commission believes that the proposed amendments to § 49.12 would provide greater clarity to SDRs in regards to their recordkeeping responsibilities and would allow for improvements in tracking errors in data reporting and the collecting of records related to SDR information. Better recordkeeping related to SDR data should lead to increased awareness for the SDRs and the Commission of any reporting issues experienced by reporting counterparties. Data recordkeeping should lead to better quality data by allowing the SDRs and the Commission to look for patterns in records that may lead to adjustments to SDR systems or future data reporting requirements. The availability of quality records is also crucial for the Commission to effectively perform its market surveillance and enforcement functions, which benefit the public by protecting market integrity and identifying risks within the swaps markets.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.12. Are there additional costs and benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of these costs and benefits.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.12. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">viii. § 49.13—Monitoring, Screening, and Analyzing Data</HD>
                    <P>Proposed § 49.13(a) would generally require: (i) SDRs to establish automated systems for monitoring, screening, and analyzing all relevant SDR data in their possession in the form and manner as directed by the Commission; and (ii) SDRs to routinely monitor, screen, and analyze relevant SDR data at the request of the Commission.</P>
                    <P>Proposed § 49.13(a)(1) would: (i) Specify that the requirements for monitoring, screening, and analyzing SDR data require SDRs to utilize relevant SDR data maintained by the SDR to provide information to the Commission concerning the SDR data; and (ii) state that monitoring, screening, and analyzing requests may require the SDRs to compile or calculate information within certain categories, or to compare information among categories, and lists the potential topic areas for requests. Proposed § 49.13(a)(1) also provides a list of topic areas for monitoring, screening, and analyzing tasks that the Commission may require.</P>
                    <P>Proposed § 49.13(a)(2) would specify that all monitoring, screening, and analyzing requests are at the discretion of the Commission and require that all information provided pursuant to a request conform to the form and manner requirements established for the request pursuant to proposed § 49.30. Proposed § 49.13(a)(3) would require that all monitoring, screening, and analyzing requests be fulfilled within a time specified by the Commission for the particular request.</P>
                    <P>Proposed § 49.13(b) would require SDRs to establish and at all times maintain sufficient technology, staff, and resources to fulfill the requirements in § 49.13 in the manner prescribed by the Commission.</P>
                    <P>Proposed § 49.13(c) would incorporate current § 49.15(c) but also expand it to require SDRs to promptly notify the Commission of any swap transaction for which the SDR is aware that it did not receive SDR data in accordance with the requirements of parts 43, 45, and 46.</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>The costs imposed by the proposed amendments to § 49.13 would largely be borne by the three SDRs. The Commission expects these SDRs to incur costs as they may need to develop or modify and maintain the requisite automated systems to monitor, screen, and analyze the reported SDR data to respond to requests from the Commission. Each requested task would need to be evaluated independently to determine the SDRs' ability to perform the task and then to determine the exact content of the report and the delivery requirements. The Commission is not prescribing any specific tasks with this proposal.</P>
                    <P>
                        Section 21(c)(5) of the CEA currently requires SDRs to “at the direction of the Commission, establish automated systems for monitoring, screening, and analyzing” the data maintained by the SDRs,
                        <SU>246</SU>
                        <FTREF/>
                         and current § 49.13(a) codifies this requirement by requiring the SDRs to monitor, screen, and analyze all data in their possession as the Commission may require for ongoing data surveillance activities or ad hoc requests.
                        <SU>247</SU>
                        <FTREF/>
                         Proposed § 49.13(a) retains this general requirement, but also provides broad topic areas for tasks that the Commission may request in order to provide SDRs with more information for the monitoring, screening, and analyzing requirement. The Commission expects that the costs for SDRs would vary depending on the scope and frequency of the data requested. The Commission also expects that the costs would be mitigated by the fact that SDRs currently perform monitoring, screening, and analyzing tasks at the request of Commission staff and therefore have systems and resources in place that may be leveraged for any new requests.
                    </P>
                    <FTNT>
                        <P>
                            <SU>246</SU>
                             7 U.S.C. 24a(c)(5).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>247</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.13(a).
                        </P>
                    </FTNT>
                    <P>
                        Current § 49.13(b) also requires SDRs to maintain sufficient information technology to carry out their duties to monitor, screen, and analyze the data 
                        <PRTPAGE P="21086"/>
                        they collect. SDRs also currently routinely perform monitoring, screening, and analyzing tasks at the request of Commission staff. While the Commission expects that the SDRs may incur costs to modify and maintain their systems to comply with the requirements of proposed § 49.13 and to respond to requests from the Commission, the Commission believes that the incremental costs would not be significant compared to the applicable baseline of the current requirements to perform monitoring, screening, and analyzing tasks. These costs would also be mitigated by the fact that SDRs are currently performing a variety of monitoring, screening, and analyzing tasks at the request of Commission staff, and therefore already have resources devoted to monitoring, screening, and analyzing SDR data that could be leveraged for any additional requests.
                    </P>
                    <P>The Commission acknowledges that the cost burdens of the proposed changes for any specific SDR would depend on the current systems established and maintained by the SDR. While current § 49.13 includes requirements to monitor, screen, and analyze data and establish and maintain sufficient information technology, staff, and other resources, the resources expended by an SDR necessarily depends on the parameters of the specific requests. The Commission does not expect SDRs to expend resources without a pending request from the Commission. SDRs currently perform tasks, such as tracking the timeliness of swaps reporting, but costs from other tasks facilitated by the proposed rule may require new or modified systems to perform requested tasks.</P>
                    <P>The Commission further acknowledges that costs related to each task would likely vary with the complexity of the requested task. The costs associated with responding to each task would depend on the information requested and the frequency of the reports. The Commission expects the requests would be reasonable based on available SDR resources and would take into account an understanding of what is possible given the data maintained by the SDRs. The Commission understands that SDRs can only be expected to perform monitoring, screening, and analyzing tasks based on the SDR data available to each SDR and that the results of any task would be limited to the SDR data for swaps reported to each SDR. The Commission also expects that SDRs and Commission staff would work together to design each task before a task is prescribed, as is current practice. </P>
                    <P>This may also be a source of costs for SDRs, as each pending request may require multiple conversations between SDRs and the Commission to design each task based on the Commission's needs and what is feasible given the SDRs' abilities and the available SDR data.</P>
                    <P>After the costs have been incurred for any initial development or updates to SDR automated systems related to any specific task, the Commission expects recurring costs as SDRs' systems would need to be monitored and adjusted as needed. Given that the Commission expects most requested tasks would be largely automated, the per-report production costs would not be substantial.</P>
                    <P>In addition, because the information submitted to the Commission must reflect and adhere to established form and manner specifications pursuant to proposed § 49.30, the Commission anticipates many of the reports resulting from the tasks would share a common form and manner, which would result in reduced incremental costs for additional reports.</P>
                    <P>Proposed § 49.13(c) would not create any costs other than those associated with the requirement to promptly notify the Commission. The Commission believes those costs would not be significant, because SDRs have already established systems to send electronic information to the Commission and the Commission is not requiring SDRs to actively search for reporting noncompliance as part of this proposed section.</P>
                    <P>The Commission expects amended § 49.13 would improve data quality and enhance the Commission's surveillance and other regulatory capabilities. Market participants and the public would benefit from these improvements. As SDRs analyze the SDR data to complete requested tasks, for example, inconsistencies and anomalies within the data would become more apparent, which may lead to improvements in market practices, data quality, and Commission regulations. The reports may also assist the Commission with timely analyses that would help the Commission perform its regulatory functions. To the extent that the tasks enable the Commission to act more quickly, or with greater accuracy, to identify abusive market practices, compliance issues, or systemic risks, and address these concerns more quickly and with greater precision, market participants and the public would benefit. These monitoring, screening, and analyzing tasks should lead to more robust, improved analyses performed by or available to the Commission staff, and the findings from such analyses should help the Commission better perform its regulatory functions, improve its policy decisions, and allow the Commission to better inform the public about the swaps markets.</P>
                    <P>The Commission recognizes that not detailing specific tasks in the rule text may create certain costs for SDRs, as the tasks the Commission requests them to perform may change over time and therefore may not be perfectly predictable. At the same time, the Commission believes that not assigning tasks in the rule text itself would encourage the SDRs and the Commission to work together to devise the best approaches for any needed tasks. Adding specific tasks to the rule text would also curtail the Commission's ability to remove or modify the task in the future, as the Commission's needs and the SDRs' capabilities change. Allowing more flexibility by not including tasks in the proposed rulemaking would benefit both the SDRs and the Commission, and is the Commission's preferred approach. Additionally, the examples of the types of tasks the Commission envisions asking of SDRs provide above should help reduce any costs associated with uncertainty.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.13. Are there additional costs and benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of these costs and benefits.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.13. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <P>Please describe the qualitative and quantitative costs (including, but not limited to, personnel costs, technological costs, and costs related to on-going discussions with Commission staff) that SDRs may incur in needing to make any updates to current systems related to the proposed changes to § 49.13.</P>
                    <P>
                        Please describe (both qualitatively and quantitatively) how costs or benefits (including, but not limited to, personnel costs, technological costs, and costs related to on-going discussions with Commission staff) may change depending on whether more or fewer categories are included in § 49.13(a)(1). Are there additional categories that the Commission should include or are there 
                        <PRTPAGE P="21087"/>
                        categories that the Commission should remove? If so, please explain in detail.
                    </P>
                    <P>Please describe (both qualitatively and quantitatively) how costs and benefits (including, but not limited to, personnel costs, technological costs, and costs related to on-going discussions with Commission staff) may change depending on the length of time period to be analyzed for a task or the frequency of repetition for a task.</P>
                    <HD SOURCE="HD3">ix. § 49.17—Access to SDR Data</HD>
                    <P>The Commission proposes to amend the § 49.17(b)(3) definition of “direct electronic access” to mean an electronic system, platform, framework, or other technology that provides internet-based or other form of access to real-time SDR data that is acceptable to the Commission and also provides scheduled data transfers to Commission electronic systems.</P>
                    <P>Proposed § 49.17(c) would require SDRs to provide access to the Commission for all SDR data maintained by the SDR pursuant to the Commission's regulations. Proposed § 49.17(c)(1) would require that SDRs provide direct electronic access to the Commission or its designee in order for the Commission to carry out its legal and statutory responsibilities under the CEA and Commission regulations. Proposed § 49.17(c)(1) would also require that SDRs maintain all SDR data reported to the SDR in a format acceptable to the Commission, and transmit all SDR data requested by the Commission to the Commission as instructed by the Commission.</P>
                    <P>Proposed § 49.17(c)(1) would amend the requirements of current § 45.13(a) from maintaining and transmitting “swap data” to maintaining and transmitting “SDR data,” to make clear that the SDRs must maintain all SDR data reported to the SDRs in a format acceptable to the Commission and transmit all SDR data requested by the Commission, not just swap data.</P>
                    <P>Proposed § 49.17(c)(1) would also broaden the requirements of current § 45.13(a) from “transmit all swap data requested by the Commission to the Commission in an electronic file in a format acceptable to the Commission” to “transmit all SDR data requested by the Commission to the Commission as instructed by the Commission,” and explains what these instructions may include.</P>
                    <P>The Commission proposes to amend § 49.17(f) to correct the incorrect reference to “37.12(b)(7)” at the end of paragraph (f)(2) with a correct reference to “39.12(b)(7)” of the Commission's regulations, as there is no § 37.12(b)(7) in the Commission's regulations.</P>
                    <P>The Commission proposes to move the delegation of authority in current § 49.17(i) to proposed § 49.31(a)(7).</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>
                        The costs imposed by the proposed changes to § 49.17(c) would fall mainly on SDRs, because the SDRs would incur costs to provide the Commission with direct electronic access to all SDR data and to provide access to SDR data as instructed. The costs associated with the use of the term “direct electronic access” in proposed § 49.17(c) are negligible, as the definition is being modified to allow the SDR's more flexibility in providing the Commission with direct electronic access to SDR data, subject to the Commission's approval. The other proposed amendments to § 49.17(c) grant the Commission greater flexibility to instruct SDRs on how to transfer SDR data to the Commission at the Commission's request. The SDRs may experience some costs based on the need to update systems to be able to transfer SDR data to the Commission as instructed. These incremental costs would not be significant because SDRs are already required to provide scheduled data transfers to the Commission under current § 49.17(b)(3) and (c)(1) and are required to transmit all swap data requested by the Commission to the Commission in an electronic file in a format acceptable to the Commission under current § 45.13(a). It is also current market practice for SDRs to regularly provide SDR data to the Commission as instructed by Commission staff. The Commission expects that the SDRs would continue to work with Commission staff to devise the most efficient and effective ways to meet the Commission's data needs.
                        <SU>248</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>248</SU>
                             The proposed changes to § 49.17(f)(2) and (i) are non-substantive and do not have cost-benefit implications.
                        </P>
                    </FTNT>
                    <P>The Commission believes that the proposed amendments to § 49.17 would provide clarity and certainty to SDRs regarding their responsibilities to the Commission, by including the data access requirements in one section and by more clearly stating the Commission's ability to instruct SDRs on all aspects of providing SDR data to the Commission. This clarity would help the SDRs work with Commission staff to devise the most efficient and effective ways for the SDRs to transfer data to the Commission, ensuring that the Commission would have the SDR data that it needs to perform its regulatory functions without undue burden on SDRs.</P>
                    <P>The proposed changes to § 49.17(b)(3) that modify the definition of “direct electronic access” to allow for more technological flexibility would reduce future costs for SDRs because the amendment allows the Commission to consider any technology that may provide direct electronic access more efficiently than the current requirement. This would allow the Commission to adapt to changing technology more quickly and may allow the SDRs to save costs by having more efficient technology and processes approved in the future.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.17. Are there additional costs and benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of the costs and benefits, as well as other information to support such assessments.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.17. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">x. § 49.22—Chief Compliance Officer</HD>
                    <P>The Commission proposes to amend § 49.22 to reduce regulatory compliance burdens on SDRs and to make a number of non-substantive organizational and conforming changes.</P>
                    <P>
                        The Commission is proposing a non-substantive change to define “senior officer” in proposed § 49.22(a). Both current § 49.22 and the CEA 
                        <SU>249</SU>
                        <FTREF/>
                         use the term “senior officer” in the context of CCO requirements. Proposed § 49.22(a) also makes non-substantive organizational changes to the paragraph.
                    </P>
                    <FTNT>
                        <P>
                            <SU>249</SU>
                             
                            <E T="03">See</E>
                             7 U.S.C. 24a(e).
                        </P>
                    </FTNT>
                    <P>Proposed § 49.22(b) removes an unnecessary reference establishing the position of CCO from § 49.22(b)(1) and adds in consultation with the board of directors or senior officer to § 49.22(b)(1)(i), along with other conforming changes to terminology.</P>
                    <P>
                        Proposed § 49.22(c) rearranges some parts of the section and simplifies the wording of current § 49.22(c) in order to clarify the requirements related to the appointment, supervision, and removal of the CCO, but makes few substantive changes to the current requirements. Proposed § 49.22(c)(3)(i) clarifies that the senior officer can also remove a CCO, in addition to the board of 
                        <PRTPAGE P="21088"/>
                        directors, in order to provide more flexibility to the SDRs.
                    </P>
                    <P>
                        Proposed § 49.22(d) rearranges some parts of the section and simplifies the wording of current § 49.22(d), while also making a few substantive changes related to CCO duties. Proposed § 49.22(d)(2) changes “any conflicts of interest that may arise” to “any material conflicts of interest” to contain a more practical requirement on SDRs than having CCOs resolve every potential conflict of interest, which would also reduce burdens. The proposed changes also remove the three examples of conflicts of interest from current § 49.22(d)(2) 
                        <SU>250</SU>
                        <FTREF/>
                         in order to not imply a limit as to the types of material conflicts of interest that may arise. The Commission notes that material conflict of interest may still arise in the three areas listed in current § 49.22(d)(2), and the CCO would have to address such material conflicts, even with the examples removed from proposed § 49.22(d).
                    </P>
                    <FTNT>
                        <P>
                            <SU>250</SU>
                             
                            <E T="03">See</E>
                             17 CFR 49.22(d)(2)(i)-(iii).
                        </P>
                    </FTNT>
                    <P>Proposed § 49.22(e) rearranges some parts of the section and simplifies the wording of current § 49.22(e), while making a few substantive changes related to the preparation of the annual compliance report. The Commission is proposing to curtail the line-by-line review of Commission regulations and the CEA requirements with SDR policies, as required by current § 49.22(e)(2), in order to streamline the SDRs' preparation of the annual compliance report. The Commission notes, however, that proposed § 49.22(e)(1) and (e)(2) would focus on the most important and useful information in the annual compliance report based on the Commission's experience. The Commission is also proposing to remove many of the examples of how material compliance issues can be identified from current § 49.22(e)(5) so as not to imply any limits on the material compliance matters that must be described. The Commission notes that removing the examples from current § 49.22(e)(5) in proposed § 49.22(e)(4) does not in any way limit the material compliance matters that must be described, regardless of how the matter are identified. Finally, the Commission proposes to add “in all material aspects” to the end of current § 49.22(e)(6) in proposed § 49.22(e)(5), in order to reduce CCOs' concerns with certifying the annual compliance report's accuracy.</P>
                    <P>The Commission is proposing to remove the requirement in current § 49.22(f)(1) that requires the submission of the annual compliance report to the SDR's board of directors or the senior officer and any subsequent discussion of the report to be recorded in the board minutes or other similar record as evidence of compliance with the submission requirement, as this requirement would be incorporated into the general recordkeeping requirement in proposed § 49.22(g).</P>
                    <P>The Commission is proposing to amend § 49.22(f)(2) by increasing the amount of time that SDRs have to submit the annual compliance report to the Commission from 60 days to 90 calendar days after the end of the SDR's fiscal year. The Commission is also proposing to remove the annual Form SDR amendment requirement in § 49.3(a)(5) and is therefore proposing to remove the reference to § 49.3(a)(5) from § 49.22(f)(2).</P>
                    <P>The Commission proposes to amend § 49.22(f)(3) to include a requirement that, in the instance where an amendment to the annual compliance report must be submitted to the Commission, the CCO must also submit the amended annual compliance report to the SDR's board of directors or the senior officer.</P>
                    <P>The Commission is proposing to amend § 49.22(f)(4) to allow the Commission to more easily grant requests for an extension of time to file the annual compliance report by removing the requirement that SDRs must show “substantial, undue” hardship. The Commission believes this current requirement is too strict and is instead proposing to allow the Commission to grant extensions based on “reasonable and valid requests.”</P>
                    <P>The Commission is proposing to amend § 49.22(g) to simplify the recordkeeping requirements for records related to the SDRs' policies and records created related to the annual compliance report. The Commission is removing the specific examples of records listed in current § 49.22(g) from proposed § 49.22(g), but proposed § 49.22(g) still requires all of the same records to be maintained in accordance with proposed § 49.12. As a result, the proposed amendments to § 49.22(g) are non-substantive.</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>The proposed amendments to § 49.22(a), (b), and (g) are non-substantive and therefore do not have cost-benefit implications. Similarly, the conforming amendments related to the terms proposed in § 49.2, the rearranging of paragraphs within proposed § 49.22, and other changes to text that do not substantively change the requirements of § 49.22 do not have cost-benefit implications.</P>
                    <P>The only substantive change in proposed § 49.22(c) is the addition of the senior officer's ability to remove the CCO. The Commission believes that adding the senior officer to this provision would benefit SDRs by allowing more flexibility in how the SDRs manage their personnel and their compliance activities. The Commission believes that any costs associated with proposed § 49.22(c) would not be significant and consist of any resources needed to update SDR policies and procedures, if the SDRs choose to enable the senior officer to remove the CCO.</P>
                    <P>The Commission believes that the proposed change to the conflicts of interest provision in proposed § 49.22(d)(2) would benefit SDRs by including a more practical requirement while still requiring important conflicts of interest to be addressed. By changing the requirement from “resolving any conflicts of interest that may arise” to “taking reasonable steps . . . to resolve any material conflicts of interest that may arise,” an SDR's CCO would not need to spend resources to address every conceivable conflict of interest and can instead concentrate resources on resolving conflicts of interest that have a material effect on an SDR's operations. The Commission does not expect the SDRs to incur any significant costs as a result of these proposed changes.</P>
                    <P>The Commission believes that the changes to the requirements for the information to be included in the annual compliance report in proposed § 49.22(e)(1) would benefit SDRs by allowing SDRs to focus on the most important and useful information in the annual compliance report, which would also reduce their burdens. The Commission believes that the proposed removal of the assessment of all applicable Commission regulations and CEA requirements with SDR policies and replacement with a more general requirement to describe and assess the SDR's policies and procedures would save SDRs effort without detrimental effects on the Commission's ability to perform its oversight functions. The Commission does not believe there are any incremental costs associated with this proposed amendment. The remaining changes to § 49.22(e) are not substantive and do not have cost-benefit implications.</P>
                    <P>
                        The Commission believes that the proposed amendments to § 49.22(f) would benefit SDRs by simplifying requirements or reducing the costs on SDRs to submit annual compliance reports to the Commission. By providing 
                        <PRTPAGE P="21089"/>
                        more time to submit the annual compliance report and by reducing the burden to request a further extension in time to file an annual compliance report, the amendments to § 49.22(f)(2) and (4) would reduce the cost of complying and submitting the report for SDRs. Requirements are also simplified by removing the board or meeting minutes requirement in proposed § 49.22(f)(1), as this requirement would be incorporated into the general recordkeeping requirement in proposed § 49.22(g). The requirement to submit an amended annual compliance report to the board of directors or senior officer may slightly increase costs for SDRs, but only in the sense of the time burden required to submit the amended report. This cost is further mitigated by the fact that CCOs are already capable of submitting the annual compliance reports to their board of directors or senior officer because of existing requirements.
                    </P>
                    <P>The benefits of the proposed amendments for SDRs would result from the lower burdens related to annual compliance reports. The SDRs would have more time to complete the annual compliance reports and the Commission would be more able to grant requests for extensions of filing time, which should make complying and submitting annual compliance reports easier for SDRs. Removing the requirement to record the submission and discussions of the annual compliance reports from board of directors meeting minutes and similar documents would streamline the requirements as this requirement would be incorporated into the general recordkeeping requirement in proposed § 49.22(g). Overall, the amendments would make the submission process for annual compliance reports under § 49.22(f) easier for SDRs.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.22. Are there additional costs and benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of the costs and benefits.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.22. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">xi. § 49.25—Financial Resources</HD>
                    <P>The Commission proposes conforming changes to § 49.25 to remove the reference to § 49.9 and to core principle obligations identified in § 49.19. Proposed § 49.25(a) would instead refer to SDR obligations under “this chapter,” to be broadly interpreted as any regulatory or statutory obligation specified in part 49. The Commission considers these to be non-substantive changes that do not impact existing obligations on SDRs, and therefore have no cost-benefit implications.</P>
                    <P>The Commission is also proposing to amend § 49.25(f)(3) to extend the time SDRs have to submit their quarterly financial resources reports to 40 calendar days after the end of the SDR's first three fiscal quarters, and 90 days after the end of the SDR's fourth fiscal quarter, or a later time that the Commission permits upon request.</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>The Commission believes that giving SDRs more time to file their quarterly financial resources reports would benefit SDRs with little impact on the Commission's oversight of SDRs. In addition, the Commission notes that the 90 calendar day deadline for fourth quarter financial reports would align with the amended timeframe for SDRs submitting annual compliance reports in proposed § 49.22(f)(2). The Commission believes that SDRs would benefit from extended, harmonized deadlines.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.25. Are there additional costs and benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of the costs and benefits.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.25. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">xii. § 49.26—Disclosure Requirements of Swap Data Repositories</HD>
                    <P>The Commission proposes to amend § 49.26 to make updates to the introductory paragraph of § 49.26 to reflect updates to the terms “SDR data,” “registered swap data repository,” and “reporting entity” in proposed § 49.2. The Commission also proposes to update other defined terms used in the section to conform to the proposed amendments to § 49.2. These non-substantive amendments do not change the requirements of § 49.26 and do not have cost-benefit implications.</P>
                    <P>The Commission also proposes to add § 49.26(j) that would require that the SDR disclosure document set forth the SDR's policies and procedures regarding the reporting of SDR data to the SDR, including the SDR data validation and swap data verification procedures implemented by the SDR and the SDR's procedures for correcting SDR data errors and omissions (including the failure to report SDR data as required pursuant to the Commission's regulations).</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>The Commission believes that costs of proposed § 49.26 would not be significant. The costs would entail the costs of adding the information required under proposed § 49.26(j) to the required SDR disclosure document and updating the document as needed.</P>
                    <P>The Commission expects that the proposed addition of § 49.26(j) would benefit market participants by providing clearer information regarding data reporting to SDR users, which should improve data reporting by providing SDR users with information that would allow them to align their data reporting systems with the SDRs' data reporting systems before using the SDRs' services, thereby reducing reporting errors and potential confusion.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.26. Are there additional costs and benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of the costs and benefits.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.26. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">xiii. § 49.28—Operating Hours of Swap Data Repositories</HD>
                    <P>
                        The Commission is proposing to add new § 49.28 to provide more detail on the SDRs' responsibilities with respect to hours of operation. Proposed § 49.28(a) would require an SDR to have systems in place to continuously accept, promptly record, and, as applicable pursuant to part 43, publicly disseminate all SDR data reported to the SDR. Proposed § 49.28(a)(1) would 
                        <PRTPAGE P="21090"/>
                        allow an SDR to establish normal closing hours to perform system maintenance when, in the SDRs' reasonable estimation, the SDR typically receives the least amount of SDR data, as long as the SDR provides reasonable advance notice of its normal closing hours to market participants and the public.
                    </P>
                    <P>Proposed § 49.28(a)(2) would allow an SDR to declare, on an ad hoc basis, special closing hours to perform system maintenance that cannot wait until normal closing hours. Proposed § 49.28(a)(2) instructs SDRs to schedule special closing hours during periods when, in an SDR's reasonable estimation, the special closing hours would, to the extent possible, be least disruptive to the SDR's SDR data reporting responsibilities. Proposed § 49.28(a)(2) would also require the SDRs to provide reasonable advance notice of the special closing hours to market participants and the public whenever possible, and, if advance notice is not reasonably possible, to give notice to the public as soon as is reasonably possible after declaring special closing hours.</P>
                    <P>
                        Proposed § 49.28(b) would require SDRs to comply with the requirements under part 40 of the Commission's regulations when adopting or amending normal closing hours or special closing hours.
                        <SU>251</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>251</SU>
                             This requirement already applies to SDRs pursuant to current § 43.3(f)(3). 
                            <E T="03">See</E>
                             17 CFR 43.3(f)(3).
                        </P>
                    </FTNT>
                    <P>
                        Proposed § 49.28(c) would require an SDR to have the capability to accept and hold in queue any and all SDR data reported to the SDR during normal closing hours and special closing hours 
                        <SU>252</SU>
                        <FTREF/>
                         Proposed § 49.28(c)(1) would require an SDR, on reopening from normal or special closing hours, to promptly process all SDR data received during the closing hours and, pursuant to part 43, publicly disseminate swap transaction and pricing data reported to the SDR that was held in queue during the closing hours.
                        <SU>253</SU>
                        <FTREF/>
                         Proposed § 49.28(c)(2) would require SDRs to immediately issue notice to all SEFs, DCMs, reporting counterparties, and the public in the event that an SDR is unable to receive and hold in queue any SDR data reported during normal closing hours or special closing hours. Proposed § 49.28(c)(2) would also require SDRs to issue notice to all SEFs, DCMs, reporting counterparties, and the public that the SDR has resumed normal operations immediately on reopening. Proposed § 49.28(c)(2) would then require a SEF, DCM, or reporting counterparty that was not able to report SDR data to an SDR because of the SDR's inability to receive and hold in queue SDR data to immediately report the SDR data to the SDR.
                        <SU>254</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>252</SU>
                             Proposed § 49.28(c) would expand the similar existing requirements for swap transaction and pricing data in current § 43.3(g) to all SDR data and would largely follow the SBSDR requirements to receive and hold in queue information regarding security-based swaps.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>253</SU>
                             Proposed § 49.28(c)(1) would expand the similar existing requirements for the SDRs to disseminate swap transaction and pricing data pursuant to current § 43.3(g)(1) to also include the prompt processing of all other SDR data received and held in queue during closing hours. The proposed requirements would also largely follow the SBSDR requirements for disseminating transaction reports after reopening following closing hours.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>254</SU>
                             Proposed § 49.28(c)(2) would expand the similar existing requirements for swap transaction and pricing data in current § 43.3(g)(2) to all SDR data and would largely follow the SBSDR requirements to receive and hold in queue information regarding security-based swaps.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>The Commission believes that the above requirements, which are largely based on existing rule text found in current § 43.3(f) and (g), would not have significant cost implications for SDRs. The costs would be those associated with any needed modification to SDR systems to accommodate all SDR data during closing hours, as opposed to only swap transaction and pricing data. These costs would not be significant because all SDRs currently have policies, procedures, and systems in place to accommodate all SDR data during closing hours because of the current requirements.</P>
                    <P>The SDRs, market participants, and the public benefit from proposed § 49.28 because the requirements for setting closing hours and handling SDR data during closing hours would be clearer. Proposed § 49.28 also removes discrepancies between current requirements for SDRs and SBSDRs related to closing hours, which would allow SDRs that are also registered as SBSDRs to comply with one requirement.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.28. Are there additional costs and benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of the costs and benefits.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.28. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">xiv. § 49.29—Information Relating To Swap Data Repository Compliance</HD>
                    <P>The Commission is proposing to add new § 49.29 to provide for information requests to SDRs regarding compliance with an SDR's regulatory duties and core principles.</P>
                    <P>Proposed § 49.29(a) would require SDRs, upon request of the Commission, to file certain information related to its business as an SDR or other such information as the Commission determines to be necessary or appropriate for the Commission to perform its regulatory duties. The SDRs would be required to provide the requested information in the form and manner and within the time specified by the Commission in its request.</P>
                    <P>Proposed § 49.29(b) would require SDRs, upon the request of the Commission, to demonstrate compliance with their obligations under the CEA and Commission regulations, as specified in the request. SDRs would be required to provide the requested information in the form and manner and within the time specified by the Commission in its request.</P>
                    <P>
                        Proposed § 49.29 is based on existing Commission requirements applicable to SEFs and DCMs.
                        <SU>255</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>255</SU>
                             
                            <E T="03">See, e.g.,</E>
                             17 CFR 37.5 and 38.5.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>
                        The costs associated with responding to requests for information would include the staff hours required to prepare and submit materials related to the requests. These costs would vary among SDRs depending upon the nature and frequency of Commission inquiries. The Commission expects these requests to be limited in both size and scope, which would constrain the cost burden on SDRs. While proposed § 49.29 allows the Commission to make requests on an ad hoc basis, the Commission expects that the need for these requests would decrease over time as data quality and SDR compliance with Commission regulations improves.
                        <SU>256</SU>
                        <FTREF/>
                         The Commission acknowledges that there would be an incremental cost for each response, given the time required by the SDR to collect and/or summarize the requested information. The Commission believes that these costs would be mitigated by the fact that current practice is for SDRs to provide similar information to the Commission on 
                        <PRTPAGE P="21091"/>
                        request and that the SDRs do so regularly.
                    </P>
                    <FTNT>
                        <P>
                            <SU>256</SU>
                             The Commission currently exercises similar authority fewer than ten times per year in total with other registered entities, such as SEFs, DCMs, and DCOs.
                        </P>
                    </FTNT>
                    <P>Information submitted to the Commission would be required to reflect and adhere to form and manner specifications established pursuant to proposed § 49.30. The Commission expects that clearly defining the form and manner for each response would mitigate the cost burden to the SDRs from any uncertainty as to the information to be provided.</P>
                    <P>Benefits attributed to proposed § 49.29 would include improving the Commission's oversight of SDRs. The Commission expects that this oversight would lead to improved data quality and SDR compliance with Commission regulations due to Commission inquiries. Better data quality should improve the Commission's ability to fulfill its regulatory responsibilities and help to increase the Commission's understanding of the swaps market. These improvements are expected to benefit the public through more accurate and complete SDR data reporting, improved Commission analyses and oversight of the swaps markets, and increased market integrity due to the Commission's improved ability to detect and investigate noncompliance issues and oversee their correction.</P>
                    <P>Proposed § 49.29 would also help the Commission to obtain the information it needs to perform its regulatory functions as needed, as opposed to requiring the information on a set schedule, such as with the proposed removal of the requirement for annual Form SDR updates in proposed § 49.3(a)(5). Proposed § 49.29 would allow the Commission to request the same information that would be contained in Form SDR and its exhibits when the Commission needs the information, as opposed to requiring the SDRs to update Form SDR and the exhibits annually. This would reduce the burden on SDRs from annual filings for any information that the Commission requests less frequently than annually.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.29. Are there additional costs and benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of these costs and benefits, as well as other information to support such assessments.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.29. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">xv. § 49.30—Form and Manner of Reporting and Submitting Information to the Commission</HD>
                    <P>The Commission is proposing to add new § 49.30 to address the form and manner of information the Commission requests from SDRs.</P>
                    <P>Proposed § 49.30 would establish the broad parameters of the “form and manner” requirements found throughout part 49 in different regulations. The “form and manner” requirement proposed in § 49.30 would not supplement or expand upon existing substantive provisions of part 49, but instead, would only allow the Commission to specify how existing information reported to, and maintained by, SDRs should be formatted and delivered to the Commission. Proposed § 49.30 would provide that the Commission would specify, in writing, the format, coding structure, and electronic data transmission procedures for various reports and submissions that are required to be provided to the Commission under part 49.</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>The Commission believes that the form and manner requirements would have costs associated with conforming reports and information to Commission specifications, including labor, time, and potentially technology costs for formatting reports. In practice, the incremental costs are not likely to be significant, because SDRs have extensive experience working with Commission staff to deliver data and reports in the form and manner requested by Commission staff. The Commission believes that, in practice, this experience would significantly mitigate the costs of this amendment.</P>
                    <P>The Commission believes that the Commission would benefit through increased standardization of information provided by SDRs, thereby aiding the Commission in the performance of its regulatory obligations by ensuring the provided information is useable by the Commission and allowing the Commission to alter the form and manner over time, as standards and technologies change. The ability to standardize the form and manner of information provided to the Commission would also help SDRs to efficiently fulfill their obligations to provide this information to the Commission.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 49.30. Are there additional costs and benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of the costs and benefits, as well as other information to support such assessments.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 49.30. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">5. Costs and Benefits of Proposed Amendments to Part 45</HD>
                    <HD SOURCE="HD3">i. § 45.2—Swap Recordkeeping</HD>
                    <P>The Commission is proposing to move current § 45.2(f) and (g) (SDR recordkeeping and SDR records retention, respectively) to proposed new § 49.12. As such, all costs and benefits associated with this change are discussed above in section 4.viii regarding proposed new § 49.12.</P>
                    <HD SOURCE="HD3">ii. § 45.14—Verification of Swap Data Accuracy and Correcting Errors and Omissions in Swap Data</HD>
                    <P>Proposed § 45.14(a) would generally require that reporting counterparties verify the accuracy and completeness of swap data for swaps for which they are the reporting counterparty. Proposed § 45.14(a)(1) would require that a reporting counterparty reconcile its internal books and records for each open swap for which it is the reporting counterparty with every open swaps report provided to the reporting counterparty by an SDR pursuant to proposed § 49.11. Proposed § 45.14(a)(1) would further require that reporting counterparties conform to the verification policies and procedures created by an SDR pursuant to § 49.11 for swap data verification.</P>
                    <P>Proposed § 45.14(a)(2) would require that reporting counterparties submit either a verification of data accuracy or a notice of discrepancy in response to every open swaps report received from an SDR within the following timeframes: (i) 48 hours of the SDR providing the open swaps report if the reporting counterparty is an SD, MSP, or DCO; or (ii) 96 hours of the SDR providing the open swaps report for non-SD/MSP/DCO reporting counterparties.</P>
                    <P>
                        Proposed § 45.14(a)(3) would require that when a reporting counterparty does 
                        <PRTPAGE P="21092"/>
                        not find any discrepancies between the swap data it reported to an SDR according to its internal books and records for the swaps included in the open swaps report and the swap data provided by the SDR in the open swaps report, the reporting counterparty would submit a verification of data accuracy to the SDR indicating that the swap data is complete and accurate, within the timeframe applicable to the reporting counterparty under proposed § 45.14(a)(2).
                    </P>
                    <P>Proposed § 45.14(a)(4) would require that when a reporting counterparty finds discrepancies between the swap data it reported to an SDR according to its internal books and records for the swap data included, or erroneously not included, in an open swaps report and the swap data provided by the SDR in the open swaps report, the reporting counterparty must submit a notice of discrepancy to the SDR in the form and manner required by the SDR's policies and procedures created pursuant to § 49.11, within the timeframe applicable to the reporting counterparty under proposed § 45.14(a)(2).</P>
                    <P>Proposed § 45.14(b)(1) would require any SEF, DCM, or reporting counterparty that by any means becomes aware of any errors or omissions in swap data previously reported to an SDR by the SEF, DCM, or reporting counterparty to submit corrected swap data to the SDR. Proposed § 45.14(b)(1) would also require any SEF, DCM, or reporting counterparty that by any means becomes aware of any swap data not reported to an SDR by the SEF, DCM, or reporting counterparty as required to submit the omitted swap data to the SDR. The error and omission correction requirements include, but are not limited to, errors or omissions present during the verification process specified in § 45.14(a). These error and omission correction requirements also apply regardless of the state of the swap.</P>
                    <P>Proposed § 45.14(b)(1)(i) would require that SEFs, DCMs, and reporting counterparties correct swap data as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days after discovery of the error or omission.</P>
                    <P>Proposed § 45.14(b)(1)(ii) would require that if a SEF, DCM, or reporting counterparty is unable to correct errors or omissions within three business days of discovery, the SEF, DCM, or reporting counterparty must immediately inform the Director of DMO, or such other Commission employees whom the Director of DMO may designate, in writing, of the errors or omissions and provide an initial assessment of the scope of the errors or omissions and an initial remediation plan for correcting the errors or omissions.</P>
                    <P>Proposed § 45.14(b)(1)(iii) would require that a SEF, DCM, or reporting counterparty conform to the SDR's policies and procedures for corrections of errors and omissions.</P>
                    <P>Proposed § 45.14(b)(2) would require a non-reporting counterparty that by any means becomes aware of any error or omission in swap data previously reported to an SDR, or the omission of swap data for a swap that was not previously reported to an SDR as required, to notify the reporting counterparty for the swap of the errors or omissions as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days following the discovery of the errors or omissions.</P>
                    <P>Proposed § 45.14(b)(2) would also specify that a non-reporting counterparty that does not know the identity of the reporting counterparty for a swap must notify the SEF or DCM where the swap was executed of the errors or omissions as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days after the discovery. Proposed § 45.14(b)(2) would also require that if the reporting counterparty and the non-reporting counterparty agree that the swap data for a swap is incorrect or incomplete, the reporting counterparty, SEF, or DCM must correct the swap data in accordance with proposed § 45.14(b)(1).</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>
                        The proposed changes to § 45.14 would result in administrative and compliance costs for reporting counterparties to establish technological systems to review and reconcile open swaps reports provided by SDRs. To verify open swaps, the reporting counterparties would be required to maintain records of all data elements reported pursuant to part 45. This is already a requirement under parts 23 (for SD and MSP reporting counterparties) and 45 of the Commission's regulations and as such, the Commission does not believe maintaining such records would produce additional costs.
                        <SU>257</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>257</SU>
                             
                            <E T="03">See</E>
                             17 CFR 23.201 (listing the recordkeeping requirements for SDs and MSPs, including transaction records); 17 CFR 45.2 (listing recordkeeping requirements for swaps, including requiring SDs and MSPs to keep all records required to be kept pursuant to part 23).
                        </P>
                    </FTNT>
                    <P>The Commission is not proposing to require particular methods for reporting counterparties to complete the verification process, but based on discussions with market participants, the Commission anticipates that the process would be largely automated. Reporting counterparties would incur costs in creating these automated systems to receive the open swaps reports and to complete the verification process in a timely fashion, but once the verification systems are in place, the additional costs stemming from the verification process would not be significant and would be confined to maintaining and updating the verification system as needed.</P>
                    <P>
                        A few commenters to the Commission's Roadmap suggested that commercial end-users and other non-SD/MSP/DCO reporting counterparties would incur greater costs for reporting and verifying swap data because swaps are not their primary business.
                        <SU>258</SU>
                        <FTREF/>
                         The Commission has taken these comments into account and has proposed different requirements for non-SD/MSP/DCO reporting counterparties that would provide them with more time to complete the verification process than is permitted for SD or MSP reporting counterparties.
                    </P>
                    <FTNT>
                        <P>
                            <SU>258</SU>
                             
                            <E T="03">See, e.g.,</E>
                             NRECA/APPA Letter at 3, 5; IECA Letter at 3. These commenters did not provide details on the additional costs.
                        </P>
                    </FTNT>
                    <P>
                        Reporting counterparties may also incur costs in meeting the requirements of proposed § 45.14(b)(1), which is largely similar to current § 45.14(a), but with more specific requirements related to timing. Additional costs may be incurred by SEFs, DCMs, or reporting counterparties from correcting errors and omissions within three business days of discovery and from informing the Director of DMO in writing with a remediation plan, if necessary. The Commission believes that these costs would not be significant, however, because the three business day requirement merely adds a timeframe to the current “as soon as technologically practicable after discovery” requirement,
                        <SU>259</SU>
                        <FTREF/>
                         and reporting counterparties already typically provide a remediation plan to the Commission for reporting errors and omissions as part of current practice, which would mitigate the costs of the proposed requirement, as many reporting counterparties will have experience with creating and providing remediation plans. SEFs, DCMs, and reporting counterparties may also incur costs from updating their error and omission reporting systems or practices in order to maintain consistency with SDR error and omission policies and procedures created pursuant to proposed § 49.10(e).
                    </P>
                    <FTNT>
                        <P>
                            <SU>259</SU>
                             
                            <E T="03">See</E>
                             17 CFR 45.14(a).
                        </P>
                    </FTNT>
                    <PRTPAGE P="21093"/>
                    <P>
                        Non-reporting counterparties may also incur additional costs related to the requirements in proposed § 45.14(b)(2), which are effectively the same as current § 45.14(b), except for the inclusion of the three business day time limit for informing the reporting counterparty or SEF or DCM of discovered errors or omissions and the additional requirement to inform the SEF or DCM when the non-reporting counterparty does not know the identity of the reporting counterparty. The time limit merely adds a boundary to the current “promptly” requirement for informing the reporting counterparty of discovered errors and omissions.
                        <SU>260</SU>
                        <FTREF/>
                         The additional requirement to inform a SEF or DCM is intended to accommodate the non-reporting counterparties in fulfilling their role in the data correction process for swaps executed anonymously and the Commission expects that non-reporting counterparties would not incur many costs for notifying a SEF or DCM of errors and omissions beyond the cost currently incurred when notifying reporting counterparties.
                    </P>
                    <FTNT>
                        <P>
                            <SU>260</SU>
                             
                            <E T="03">See</E>
                             17 CFR 45.14(b).
                        </P>
                    </FTNT>
                    <P>The Commission believes verification of swap data accuracy helps ensure that the Commission has access to the most accurate and complete swap data possible to fulfill its various regulatory responsibilities. Accurate swap data enables the Commission to monitor and surveil market activity and risks within the swaps markets, as well as provide assessments of the swaps markets to the public. Additionally, the Commission believes that complete and accurate swap data is necessary for effective risk management for swap counterparties, and the proposed verification and correction requirements would assist swap counterparties with ensuring that the data they possess is accurate and complete. The Commission believes that complete and accurate swap data would benefit market participants and the public by improving the Commission's ability to monitor the swaps markets and maintain market integrity through market oversight, analysis, and providing information to the public.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 45.14. Are there additional costs and benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of these costs and benefits.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 45.14. Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">6. Costs and Benefits of Proposed Amendments to Part 43</HD>
                    <HD SOURCE="HD3">i. § 43.3—Method and Timing for Real-Time Public Reporting</HD>
                    <P>The Commission is proposing to amend the error and omission correction requirements of current § 43.3(e) to make the requirements consistent with the error and omissions correction requirements in proposed § 45.14(b). The Commission believes these amendments would create consistency between the error and omission correction requirements for swap data and swap transaction and pricing data, which would reduce confusion surrounding the error and omissions corrections process.</P>
                    <P>Proposed § 43.3(e)(1) would require any SEF, DCM, or reporting counterparty that by any means becomes aware of any errors or omissions in swap transaction and pricing data previously reported to an SDR by the SEF, DCM, or reporting counterparty to submit corrected swap transaction and pricing data to the SDR, regardless of the state of the swap. Proposed § 43.3(e)(1) would also require any SEF, DCM, or reporting counterparty that by any means becomes aware of the omission of swap transaction and pricing data previously not reported to an SDR by the SEF, DCM, or reporting counterparty as required, to submit corrected swap transaction and pricing data to the SDR regardless of the state of the swap.</P>
                    <P>Proposed § 43.3(e)(1)(i) would require SEFs, DCMs, and reporting counterparties to correct swap transaction and pricing data as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days following the discovery of the error or omission.</P>
                    <P>Proposed § 43.3(e)(1)(ii) would provide that if a SEF, DCM, or reporting counterparty is unable to correct the errors or omissions within three business days following discovery of the errors or omissions, the SEF, DCM, or reporting counterparty must immediately inform the Director of DMO, or his or her designee, in writing, of such errors or omissions and provide an initial assessment of the scope of the errors or omissions and an initial remediation plan for correcting the errors or omissions.</P>
                    <P>Proposed § 43.3(e)(1)(iii) would require that a SEF, DCM, or reporting counterparty conform to an SDR's policies and procedures for corrections of errors and omissions in previously reported swap transaction and pricing data and reporting of omitted swap transaction and pricing data.</P>
                    <P>Proposed § 43.3(e)(2) would require a non-reporting counterparty that by any means becomes aware of any error or omission in swap transaction and pricing data previously reported to an SDR, or the omission of swap transaction and pricing data for a swap that was not previously reported to an SDR as required, to notify the reporting counterparty as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days following the discovery of the errors or omissions.</P>
                    <P>Proposed § 43.3(e)(2) would also require that a non-reporting counterparty that does not know the identity of the reporting counterparty for a swap to notify the SEF or DCM where the swap was executed of the errors and omissions as soon as technologically practicable after discovery of the errors or omissions, but no later than three business days after the discovery. Proposed § 43.3(e)(2) would also require that, if the non-reporting counterparty and the reporting counterparty, SEF, or DCM, as applicable, agree that the swap transaction and pricing data for a swap is incorrect or incomplete, the reporting counterparty, SEF, or DCM, as applicable, must correct the swap transaction and pricing data in accordance with proposed § 43.3(e)(1).</P>
                    <P>The Commission is proposing to move all of the requirements of current § 43.3(f) and (g) to proposed new § 49.28. As such, all costs and benefits associated with this change are discussed above in section VII.C.4.xiii.</P>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>
                        The costs and benefits for the proposed changes to § 43.3(e) are similar to the costs and benefits previously discussed for the proposed changes to § 45.14(b), as the proposed changes to each section are intended to be consistent in all respects, aside from the verification requirements. Therefore, the proposed changes to § 43.3(e) may also result in administrative and compliance costs for reporting counterparties. These costs would, however, be mitigated by the fact that the requirements of proposed § 43.3(e) are similar to the requirements of current § 43.3(e).
                        <PRTPAGE P="21094"/>
                    </P>
                    <P>
                        Additional costs may be incurred by SEFs, DCMs, or reporting counterparties from correcting errors and omissions within three business days of discovery and from informing the Director of DMO in writing with an initial assessment and initial remediation plan if necessary under proposed § 43.3(e)(1)(i) and (ii). The Commission believes that these costs would not be significant, however, because the three-day requirement merely adds a specific timeframe to the current “promptly” requirement,
                        <SU>261</SU>
                        <FTREF/>
                         and reporting counterparties typically provide a remediation plan to the Commission for reporting errors and omissions as part of current practice. SEFs, DCMs, and reporting counterparties may also incur costs from updating their error and omission reporting systems or practices in order to maintain consistency with SDR error and omission policies and procedures created pursuant to proposed § 49.10(e), as would be required under proposed § 43.3(e)(1)(iii).
                    </P>
                    <FTNT>
                        <P>
                            <SU>261</SU>
                             
                            <E T="03">See generally</E>
                             17 CFR 43.3(e).
                        </P>
                    </FTNT>
                    <P>
                        Non-reporting counterparties may also incur additional costs related to the requirements in proposed § 43.3(e)(2), which are similar to the requirements of current § 43.3(e)(1)(i), except for the proposed inclusion of the three business day time limit for informing the reporting counterparty, SEF, or DCM of discovered errors or omissions and the additional requirement to inform the SEF or DCM when the non-reporting counterparty does not know the identity of the reporting counterparty. The time limit merely adds a boundary to the current “promptly” requirement for informing the reporting counterparty of discovered errors and omissions.
                        <SU>262</SU>
                        <FTREF/>
                         The additional requirement to inform a SEF or DCM is intended to accommodate the non-reporting counterparties in fulfilling their role in the data correction process for swaps executed anonymously and the Commission expects that non-reporting counterparties would not incur many costs for notifying a SEF or DCM of errors and omissions beyond the cost currently incurred when notifying reporting counterparties.
                    </P>
                    <FTNT>
                        <P>
                            <SU>262</SU>
                             
                            <E T="03">See</E>
                             17 CFR 43.3(e)(i).
                        </P>
                    </FTNT>
                    <P>As with the benefits described above in section 5.ii, the Commission believes consistent error and omission correction requirements for swap data and swap transaction and pricing data helps ensure that the Commission has access to the most accurate and complete swap transaction and pricing data possible to fulfill its various regulatory responsibilities. Accurate swap transaction and pricing data helps the Commission to monitor and surveil market activity and risks within the swaps markets. Accurate and complete swap transaction and pricing data is also beneficial to market participants and the public who rely on the data in their swaps-related decision-making. Additionally, the Commission believes that complete and accurate swap transaction and pricing data is necessary for effective risk management for swap counterparties, and the proposed correction requirements would assist swap counterparties with ensuring that the swap transaction and pricing data they possess is accurate and complete.</P>
                    <P>SDRs and counterparties also benefit from proposed § 43.3(e) creating consistency between the error and omission correction requirements for swap data and for swap transaction and pricing data. Inconsistent requirements could lead to confusion, improper correction, and unnecessary effort for counterparties and SDRs. The consistency created by the proposed amendments to § 43.3(e) would help avoid those issues.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to § 43.3(e). Are there additional costs and benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of these costs and benefits.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed § 43.3(e). Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">7. Costs and Benefits of Proposed Amendments to Part 23</HD>
                    <HD SOURCE="HD3">i. §§ 23.204 and 23.205—Reports to Swap Data Repositories and Real-Time Public Reporting</HD>
                    <P>Proposed amendments to §§ 23.204 and 23.205 add a paragraph (c) to each section requiring SDs and MSPs to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that SDs and MSPs comply with their swap reporting obligations pursuant to parts 45 and 43, respectively. The proposed amendments also require SDs and MSPs to perform annual reviews of these policies and procedures.</P>
                    <P>
                        For proposed § 23.204, the policies and procedures related to reporting under part 45 of the Commission's regulations would need to contain details related to their responsibilities to verify swap data. This would include policies and procedures related to regularly accepting open swap reports from SDRs, cross-checking with internal records to ensure the swap data is accurate and complete, and responding to the SDR, as required. SDs and MSPs are already responsible for keeping up-to-date records on all swaps to which they are a counterparty under parts 23 and 45 of the Commission's regulations.
                        <SU>263</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>263</SU>
                             
                            <E T="03">See</E>
                             17 CFR 23.201-23.203 (detailing the recordkeeping requirements for SDs and MSPs); 17 CFR 45.2 (containing swap recordkeeping requirements for SDs and MSPs and referencing the part 23 recordkeeping requirements).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">(A) Costs and Benefits</HD>
                    <P>
                        The Commission believes that the costs associated with the proposed amendment to §§ 23.204 and 23.205 for SDs and MSPs 
                        <SU>264</SU>
                        <FTREF/>
                         would be associated with creating and enforcing the policies and procedures, and would consist mostly of administrative efforts to draft, review, implement, and update policies and procedures. The Commission expects that SDs and MSPs that are participants of more than one SDR may incur higher associated costs than those entities that are participants of only one SDR, as the SD and MSP policies and procedures would need to contemplate the reporting requirements for each SDR.
                        <SU>265</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>264</SU>
                             There are 103 provisionally-registered SDs as of February 28, 2019, all of which are expected to be a participant on at least one of the three existing SDRs. 
                            <E T="03">See https://www.nfa.futures.org/NFA-swaps-information/regulatory-info-sd-and-msp/SD-MSP-registry.HTML.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>265</SU>
                             For additional discussion of the costs and benefits related to part 23, 
                            <E T="03">see generally</E>
                             Part 23 Adopting Release.
                        </P>
                    </FTNT>
                    <P>
                        Even though SDs and MSPs may incur upfront costs related to the proposed amendments, the Commission believes that these financial outlays would be mitigated for two reasons. First, SDs and MSPs have experience with establishing and enforcing policies and procedures related to other Commission regulations.
                        <SU>266</SU>
                        <FTREF/>
                         Second, the proposed amendments to §§ 23.204 and 23.205 are substantially similar to the SEC's requirements for its security-based SDs/MSPs.
                        <SU>267</SU>
                        <FTREF/>
                         While not all SDs and MSPs covered by the proposed amendments would be subject to these SEC requirements, the Commission expects that there would be significant overlap. 
                        <PRTPAGE P="21095"/>
                        Consequently, these SDs and MSPs should be able to leverage resources and reduce duplicative costs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>266</SU>
                             
                            <E T="03">See, e.g.,</E>
                             17 CFR 23.501 (confirmations with counterparty); 17 CFR 23.504 (counterparty onboarding documentation); 17 CFR 23.602 (supervision policies).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>267</SU>
                             
                            <E T="03">See</E>
                             17 CFR 242.906 (requiring security-based SDs and security-based MSPs to establish, maintain, and enforce policies and procedures reasonably designed to ensure compliance with reporting requirements).
                        </P>
                    </FTNT>
                    <P>The Commission believes the proposed amendments would also provide important benefits. SD and MSP policies and procedures reasonably designed to ensure compliance with the reporting requirements of parts 43 and 45 would help improve compliance with the reporting rules. For example, policies and procedures designating the responsibility for reporting swap transactions should reduce confusion as to who within the organizations is responsible for reporting the required SDR data, according to the reporting procedures of the different SDRs. The Commission expects that there would also likely be fewer reporting errors (and less subsequent ad hoc work, with its associated costs, by SD/MSP staff to correct these errors) because SD/MSP employees would be able to follow the policies and procedures to perform their functions correctly.</P>
                    <P>The Commission also expects that the proposed amendments would help lead to enhanced communication between reporting counterparties and SDRs. Increased communication that is focused on improving the accuracy of SDR data would help to identify areas that require special attention that might not be specifically addressed in these proposed regulations. Hence, this enhanced working relationship between market participants and SDRs may lead to improved data reporting beyond that specifically contemplated by the regulations.</P>
                    <P>
                        The Commission also believes that, because SDs and MSPs submit the large majority of the reported SDR data, the requirements for policies and procedures related to reporting would improve the overall quality of reported data. SDs and MSPs generate a considerable majority of the total number of transactions reported to SDRs and serve as the reporting counterparty for the overwhelming majority of swaps.
                        <SU>268</SU>
                        <FTREF/>
                         A Commission analysis of SDR data indicates that from January 1, 2017 through December 31, 2017, almost all swap transactions involved at least one registered SD as a counterparty—greater than 99 percent for interest rate, credit default, foreign exchange, and equity swaps. For non-financial commodity swaps, approximately 86 percent of transactions involved at least one registered SD as a counterparty. Overall, approximately 98 percent of transactions involved at least one registered SD.
                        <SU>269</SU>
                        <FTREF/>
                         The Commission expects that these additional requirements for SDs and MSPs, and the attendant benefits to data quality, would have a substantial impact on the overall quality of the data reported to SDRs because of the important role these reporting counterparties perform in the swaps market.
                    </P>
                    <FTNT>
                        <P>
                            <SU>268</SU>
                             Based on the requirements of § 45.8, any swap with at least one SD or MSP counterparty will have an SD or MSP serving as the reporting counterparty. 
                            <E T="03">See</E>
                             17 CFR 45.8 (detailing the requirements for determining which counterparty must report swap data).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>269</SU>
                             83 FR at 56674.
                        </P>
                    </FTNT>
                    <P>The Commission also expects that the requirement for SDs and MSPs to have policies and procedures relating to real-time reporting under part 43 would improve swap transaction and pricing information that SDRs would then provide the public. Hence, the Commission believes the proposed amendments would also improve transparency in the swaps markets and provide benefits to market participants and the public in general.</P>
                    <HD SOURCE="HD3">(B) Request for Comment</HD>
                    <P>The Commission requests comment on its considerations of the costs and benefits of the proposed amendments to §§ 23.204(c) and 23.205(c). Are there additional costs and benefits that the Commission should consider? Commenters are encouraged to include both qualitative and quantitative assessments of these costs and benefits.</P>
                    <P>The Commission requests comments on its consideration of alternatives to proposed §§ 23.204(c) and 23.205(c). Are there any other alternatives that may provide preferable costs or benefits than the costs and benefits related to the proposed amendments?</P>
                    <HD SOURCE="HD3">8. Section 15(a) Factors</HD>
                    <P>
                        The Dodd-Frank Act sought to promote the financial stability of the United States, in part, by improving financial system accountability and transparency. More specifically, Title VII of the Dodd-Frank Act directs the Commission to promulgate regulations to increase swaps markets' transparency and thereby reduce the potential for counterparty and systemic risk.
                        <SU>270</SU>
                        <FTREF/>
                         Transaction-based reporting is a fundamental component of the legislation's objectives to increase transparency, reduce risk, and promote market integrity within the financial system generally, and the swaps market in particular. The SDRs and the SEFs, DCMs, and reporting counterparties that submit data to SDRs are central to achieving the legislation's objectives related to swap reporting.
                    </P>
                    <FTNT>
                        <P>
                            <SU>270</SU>
                             
                            <E T="03">See</E>
                             Congressional Research Service Report for Congress, The Dodd-Frank Wall Street Reform and Consumer Protection Act: Title VII, Derivatives, by Mark Jickling and Kathleen Ann Ruane (August 30, 2010); Dep't of the Treasury, Financial Regulatory Reform: A New Foundation: Rebuilding Financial Supervision and Regulation 1 (June 17, 2009) at 47-48.
                        </P>
                    </FTNT>
                    <P>Section 15(a) of the Act requires the Commission to consider the costs and benefits of the proposed amendments to parts 23, 43, 45, and 49 with respect to the following factors:</P>
                    <P>• Protection of market participants and the public;</P>
                    <P>• Efficiency, competitiveness, and financial integrity of markets;</P>
                    <P>• Price discovery;</P>
                    <P>• Sound risk management practices; and</P>
                    <P>• Other public interest considerations.</P>
                    <P>A discussion of these proposed amendments in light of section 15(a) factors is set out immediately below.</P>
                    <HD SOURCE="HD3">i. Protection of Market Participants and the Public</HD>
                    <P>In the Part 49 Adopting Release, the Commission noted that it believed that the registration and regulation of SDRs would serve to better protect market participants by providing the Commission and other regulators with important oversight tools to monitor, measure, and comprehend the swaps markets. Inaccurate and incomplete data reporting hinders the Commission's ability to oversee the swaps market. The Commission believes that the adoption of all the proposed amendments to parts 23, 43, 45, and 49 would improve the quality of the data reported, increase transparency, and enhance the Commission's ability to fulfill its regulatory responsibilities, including its market surveillance and enforcement capabilities. In addition, the Commission believes that monitoring of potential risks to financial stability would be more effective with more accurate data. More accurate data would therefore lead to improved protection of market participants and the public.</P>
                    <HD SOURCE="HD3">ii. Efficiency, Competitiveness, and Financial Integrity of Markets</HD>
                    <P>
                        The Commission believes that the adoption of the proposed amendments to parts 23, 43, 45, and 49, together with the swap data recordkeeping and reporting requirements in parts 43 and 45, would provide a robust source of information on the swaps market that is expected to promote increased efficiency and competition. The Commission believes that more accurate swap transaction and pricing data would lead to greater efficiencies for market participants executing swap transactions due to a better understanding of their overall positions 
                        <PRTPAGE P="21096"/>
                        within the context of the broader market. This improved understanding would be facilitated by two distinct channels. First, amendments that result in improved part 43 swap transaction and pricing data being made available to the public would improve the ability of market participants to monitor real-time activity by other participants and to respond appropriately. Second, amendments that result in improved swap data would improve the Commission's ability to monitor the swaps markets for abusive practices and improve the Commission's ability to create policies that ensure the integrity of the swaps markets. This improvement would be facilitated by the Commission's oversight and enforcement capabilities and the reports and studies published by the Commission's research and information programs.
                    </P>
                    <P>In particular, the proposed amendments to §§ 23.204, 45.14, 49.2, 49.10, 49.11, 49.12, 49.13, and 49.26 would help improve the financial integrity of markets. For example, the verification and correction of swap data would improve the accuracy and completeness of swap data available to the Commission and would assist the Commission with, among other things, improving monitoring of risk exposures of individual counterparties, monitoring concentrations of risk exposure, and evaluating systemic risk. In addition, the SDRs' requirement to perform monitoring, screening, and analyzing tasks, as proposed in the amendments to § 49.13, would support the Commission's other regulatory functions, including market surveillance. The efficient oversight and accurate data reporting enabled by these proposed amendments would improve the financial integrity of the swaps markets.</P>
                    <P>
                        In the Part 49 Adopting Release, the Commission expected that the introduction of SDRs would further automate the reporting of swap data. The Commission expected that automation would benefit market participants and reduce transactional risks through the SDRs and other service providers offering important ancillary services, such as confirmation and matching services, valuations, pricing, reconciliation functions, position limits management, and dispute resolution. These benefits to market participants and related service providers also enhance the efficiency, competitiveness, and financial integrity of markets.
                        <SU>271</SU>
                        <FTREF/>
                         The proposed amendments would help to further enhance these benefits.
                    </P>
                    <FTNT>
                        <P>
                            <SU>271</SU>
                             
                            <E T="03">See</E>
                             Part 49 Adopting Release at 54573.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iii. Price Discovery</HD>
                    <P>The CEA requires that swap transaction and pricing data be made publicly available. The CEA and its existing implementing regulations in part 43 also require swap transaction and pricing data to be available to the public in real-time. Combined, parts 23, 43, and 49 achieve the statutory objective of providing transparency and enhanced price discovery to swap markets in a timely manner. The proposed amendments to §§ 23.205, 43.3, 49.2, 49.10, 49.11, 49.12, 49.13, and 49.26 improve the fulfillment of these objectives. The proposed amendments would both directly and indirectly upgrade the quality of real-time public reporting of swap transaction and pricing data by improving the quality of information that is reported to the SDRs and disseminated to the public.</P>
                    <P>
                        As with the swap data reported for use by regulators, the Commission believes that inaccurate and incomplete swap transaction and pricing data hinders the public's use of the data, which harms transparency and price discovery. The Commission is aware of at least three publicly available studies that support this point. The studies examined data and remarked on incomplete, inaccurate, and unreliable data. The first study analyzed the potential impact of the Dodd-Frank Act on OTC transaction costs and liquidity using real-time CDS trade data and stated that more than 5,000 reports had missing prices and more than 15,000 reports included a price of zero, leaving a usable sample of 180,149 reports.
                        <SU>272</SU>
                        <FTREF/>
                         The second study reported a number of fields that were routinely null or missing making it difficult to analyze swap market volumes.
                        <SU>273</SU>
                        <FTREF/>
                         The third study assessed the size of the agricultural swaps market and described problems identifying the underlying commodity as well as other errors in the reported data that made some data unusable, including, for example, swaps with a reported notional quantity roughly equal to the size of the entire U.S. soybean crop.
                        <SU>274</SU>
                        <FTREF/>
                         Market participants would be better able to analyze swap transaction and pricing data because it is more accurate and complete due to the proposed amendments, and as a result, transparency and price discovery should improve.
                    </P>
                    <FTNT>
                        <P>
                            <SU>272</SU>
                             Y.C. Loon, Z. (Ken) Zhong, “Does Dodd-Frank affect OTC transaction costs and liquidity? Evidence from real-time trade reports,” 
                            <E T="03">Journal of Financial Economics</E>
                             (2016), 
                            <E T="03">available at http://dx.doi.org/10.1016/j.jfineco.2016.01.019.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>273</SU>
                             
                            <E T="03">See</E>
                             Financial Stability Report, Office of Financial Research (Dec. 15, 2015) at 84-85, 
                            <E T="03">available at https://financialresearch.gov/financial-stability-reports/files/OFR_2015-Financial-Stability-Report_12-15-2015.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>274</SU>
                             Peterson, P.E. 2014. “How Large is the Agricultural Swaps Market?” Proceedings of the NCCC-134 Conference on Applied Commodity Price Analysis, Forecasting, and Market Risk Management. St. Louis, MO, 
                            <E T="03">available at http://www.farmdoc.illinois.edu/nccc134.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iv. Sound Risk Management Practices</HD>
                    <P>
                        In the Part 49 Adopting Release, the Commission stated that part 49 and part 45 would greatly strengthen the risk management practices of the swaps market.
                        <SU>275</SU>
                        <FTREF/>
                         Prior to the adoption of the Dodd-Frank Act, participants in the swaps markets operated without obligations to disclose transactions to regulators or to the public. The Dodd-Frank Act specifically changed the transparency of the swaps market with the adoption of CEA section 21 and the establishment of SDRs as the entities to which swap data and swap transaction and pricing data is reported and maintained for use by regulators or disseminated to the public. The Commission believes that the improved reporting of SDR data to SDRs would serve to improve risk management practices by market participants. To the extent that better swap transaction and pricing data improves the ability of market participants to gauge their risks in the context of the overall market, risk management practices should improve. Earlier and more informed discussions between relevant market participants and regulators regarding systemic risk facilitated by accurate swap data would also lead to improved risk management outcomes. Market participants should also see improvements in their risk management practices, as improved swap data allows for more accurate and timely market analyses that are publicly disseminated by the Commission.
                    </P>
                    <FTNT>
                        <P>
                            <SU>275</SU>
                             
                            <E T="03">See</E>
                             Part 49 Adopting Release at 54574.
                        </P>
                    </FTNT>
                    <P>
                        The Commission believes that the proposed amendments to parts 23, 43, 45, and 49 would improve the quality of SDR data reported to SDRs and, hence, improve the Commission's ability to monitor the swaps market, react to potential market emergencies, and fulfill its regulatory responsibilities generally. The Commission believes that regulator access to high-quality SDR data is essential for appropriate risk management and is especially important for regulators' ability to monitor the swaps market for systemic risk. Moreover, the Commission expects that efforts to improve data quality would increase market participants' confidence in the SDR data and therefore their 
                        <PRTPAGE P="21097"/>
                        confidence in any subsequent analyses based on the data.
                    </P>
                    <HD SOURCE="HD3">v. Other Public Interest Considerations</HD>
                    <P>The Commission believes that the increased transparency resulting from improvements to the SDR data collected by SDRs via the proposed amendments to parts 23, 43, 45, and 49 has other public interest considerations including:</P>
                    <P>• Creating greater understanding for the public, market participants, and the Commission of the interaction between the swaps market, other financial markets, and the overall economy;</P>
                    <P>• Improved regulatory oversight and enforcement capabilities; and</P>
                    <P>• More information for regulators so that they may establish more effective public policies to reduce overall systemic risk.</P>
                    <HD SOURCE="HD3">9. Request for Comment</HD>
                    <P>The Commission requests comment on all aspects of the proposed rules. Beyond specific questions interspersed throughout this discussion, the Commission generally requests comment on all aspects of its consideration of costs and benefits, including: identification and assessment of any costs and benefits not discussed herein; the potential costs and benefits of the alternatives that the Commission discussed in this release; data and any other information to assist or otherwise inform the Commission's ability to quantify or qualitatively describe the benefits and costs of the proposed rules; and substantiating data, statistics, and any other information to support statements by commenters with respect to the Commission's consideration of costs and benefits. Commenters also may suggest other alternatives to the proposed approach where the commenters believe that the alternatives would be appropriate under the CEA and provide a superior cost-benefit profile.</P>
                    <HD SOURCE="HD2">D. Anti-trust Considerations</HD>
                    <P>Section 15(b) of the CEA requires the Commission to take into consideration the public interest to be protected by the antitrust laws and endeavor to take the least anticompetitive means of achieving the objectives of the CEA, in issuing any order or adopting any Commission rule or regulation.</P>
                    <P>The Commission does not anticipate that the proposed amendments to parts 23, 43, 45, and 49 would result in anti-competitive behavior. However, the Commission encourages comments from the public on any aspect of the proposal that may have the potential to be inconsistent with the anti-trust laws or anti-competitive in nature.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects</HD>
                        <CFR>17 CFR Part 23</CFR>
                        <P>Swap dealers and major swap participants.</P>
                        <CFR>17 CFR Part 43</CFR>
                        <P>Real-time public swap reporting.</P>
                        <CFR>17 CFR Part 45</CFR>
                        <P>Swaps; data recordkeeping requirements; data reporting requirements.</P>
                        <CFR>17 CFR Part 49</CFR>
                        <P>Swap data repositories; registration and regulatory requirements.</P>
                    </LSTSUB>
                    <P>For the reasons stated in the preamble, the Commodity Futures Trading Commission proposes to amend 17 CFR parts 23, 43, 45, and 49 as set forth below:</P>
                    <PART>
                        <HD SOURCE="HED">PART 23—SWAP DEALERS AND MAJOR SWAP PARTICIPANTS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 23 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 7 U.S.C. 1a, 2, 6, 6a, 6b, 6b-1, 6c, 6p, 6r, 6s, 6t, 9, 9a, 12, 12a, 13b, 13c, 16a, 18, 19, 21, and 24a as amended by Pub. L. 111-203, 124 Stat. 1376 (2010)</P>
                    </AUTH>
                    <PART>
                        <HD SOURCE="HED">PART 23 [AMENDED]</HD>
                    </PART>
                    <AMDPAR>2. In the table below, for each section indicated in the left column, remove the term indicated in the middle column from wherever it appears in the section, and add in its place the term indicated in the right column:</AMDPAR>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s50,r100,r100">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Section</CHED>
                            <CHED H="1">Remove</CHED>
                            <CHED H="1">Add</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">23.204(a)</ENT>
                            <ENT>swap transaction data</ENT>
                            <ENT>swap data.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">23.204(a)</ENT>
                            <ENT>information and data</ENT>
                            <ENT>swap data.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">23.204(b)</ENT>
                            <ENT>swap transaction data</ENT>
                            <ENT>swap data.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">23.204(b)</ENT>
                            <ENT>information and data</ENT>
                            <ENT>swap data.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">23.205(a)</ENT>
                            <ENT>information and swap transaction and pricing data</ENT>
                            <ENT>swap transaction and pricing data.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">23.205(a)</ENT>
                            <ENT>public recording</ENT>
                            <ENT>public reporting.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">23.205(b)</ENT>
                            <ENT>swap transaction data</ENT>
                            <ENT>swap transaction and pricing data.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">23.205(b)</ENT>
                            <ENT>information and data</ENT>
                            <ENT>swap transaction and pricing data.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <AMDPAR>3. In § 23.204, add paragraph (c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 23.204 </SECTNO>
                        <SUBJECT> Reports to swap data repositories.</SUBJECT>
                        <STARS/>
                        <P>(c) Each swap dealer and major swap participant shall establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure that it complies with all obligations to report swap data to a swap data repository in accordance with part 45 of this chapter. Each such swap dealer and major swap participant shall review its policies and procedures at least annually and update the policies and procedures to reflect the requirements of part 45 of this chapter as needed.</P>
                    </SECTION>
                    <AMDPAR>4. In § 23.205, add paragraph (c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 23.205 </SECTNO>
                        <SUBJECT> Real-time public reporting.</SUBJECT>
                        <STARS/>
                        <P>(c) Each swap dealer and major swap participant shall establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure that it complies with all obligations to report swap transaction and pricing data to a swap data repository in accordance with part 43 of this chapter. Each such swap dealer and major swap participant shall review its policies and procedures at least annually and update the policies and procedures to reflect the requirements of part 43 of this chapter as needed.</P>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 43—REAL-TIME PUBLIC REPORTING</HD>
                    </PART>
                    <AMDPAR>5. The authority citation for Part 43 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>7 U.S.C. 2(a), 12a(5), and 24a, as amended by Pub. L. 111-203, 124 Stat. 1376 (2010).</P>
                    </AUTH>
                    <AMDPAR>6. In § 43.3 revise paragraph (e) and remove and reserve paragraphs (f) and (g) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 43.3 </SECTNO>
                        <SUBJECT> Method and timing for real-time public reporting.</SUBJECT>
                        <STARS/>
                        <P>
                            (e) 
                            <E T="03">Correction of errors and omissions in swap transaction and pricing data.</E>
                              
                            <PRTPAGE P="21098"/>
                            (1) Any swap execution facility, designated contract market, or reporting counterparty that by any means becomes aware of any error or omission in swap transaction and pricing data previously reported to a swap data repository by the swap execution facility, designated contract market, or reporting counterparty, or of the omission of swap transaction and pricing data for a swap that was not previously reported to a swap data repository as required under this part by the swap execution facility, designated contract market, or reporting counterparty, shall, as applicable, submit corrected swap transaction and pricing data to the swap data repository that maintains the swap transaction and pricing data for the relevant swap or correctly report swap transaction and pricing data for a swap that was not previously reported to a swap data repository as required under this part, regardless of the state of the swap that is the subject of the swap transaction and pricing data.
                        </P>
                        <P>(i) The swap execution facility, designated contract market, or reporting counterparty shall submit the corrections for errors or submit the omitted swap transaction and pricing data to the swap data repository as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days following the discovery of the errors or omissions.</P>
                        <P>(ii) If the swap execution facility, designated contract market, or reporting counterparty is unable to correct the errors or omissions within three business days following discovery of the errors or omissions, the swap execution facility, designated contract market, or reporting counterparty shall immediately inform the Director of the Division of Market Oversight, or such other employee or employees of the Commission as the Director may designate from time to time, in writing, of such errors or omissions and provide an initial assessment of the scope of the errors or omissions and an initial remediation plan for correcting the errors or omissions.</P>
                        <P>(iii) In order to satisfy the requirements of this section, a swap execution facility, designated contract market, or reporting counterparty shall conform to a swap data repository's policies and procedures created pursuant to § 49.10 of this chapter for correction of errors and omissions in previously-reported swap transaction and pricing data and reporting of omitted swap transaction and pricing data.</P>
                        <P>(2) Any non-reporting counterparty that by any means becomes aware of any error or omission in swap transaction and pricing data previously reported to a swap data repository, or of the omission of swap transaction and pricing data for a swap that was not previously reported to a swap data repository as required under this part, for a swap to which it is the non-reporting counterparty shall notify the reporting counterparty for the swap of the errors or omissions as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days following the discovery of the errors or omissions. If the non-reporting counterparty does not know the identity of the reporting counterparty, the non-reporting counterparty shall notify the swap execution facility or designated contract market where the swap was executed of the errors or omissions as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days following the discovery of the errors or omissions. If, as applicable, the reporting counterparty and non-reporting counterparty, or the swap execution facility or designated contract market and non-reporting counterparty, agree that the swap transaction and pricing data for a swap is incorrect or incomplete, the reporting counterparty, swap execution facility, or designated contract market, as applicable, shall correct the swap transaction and pricing data in accordance with paragraph (e)(1) of this section.</P>
                        <STARS/>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 45—SWAP DATA RECORDKEEPING AND REPORTING REQUIREMENTS</HD>
                    </PART>
                    <AMDPAR>7. The authority citation for Part 45 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 7 U.S.C. 6r, 7, 7a-1, 7b-3, 12a, and 24a, as amended by Title VII of the Wall Street Reform and Consumer Protection Act of 2010, Pub. L. 111-203, 124 Stat. 1376 (2010), unless otherwise noted.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 45.2 </SECTNO>
                        <SUBJECT> [Amended].</SUBJECT>
                    </SECTION>
                    <AMDPAR>8. In § 45.2, remove and reserve paragraphs (f) and (g</AMDPAR>
                    <AMDPAR>9. Revise § 45.14 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 45.14 </SECTNO>
                        <SUBJECT> Verification of swap data accuracy and correcting errors and omissions in swap data.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Verification of swap data accuracy to a swap data repository.</E>
                             A reporting counterparty shall verify the accuracy and completeness of swap data for swaps for which it is the reporting counterparty in accordance with this paragraph (a).
                        </P>
                        <P>(1) In order to verify the accuracy and completeness of swap data for swaps for which it is the reporting counterparty as required by this section, a reporting counterparty shall reconcile its internal books and records for each open swap for which it is the reporting counterparty with every open swaps report provided to the reporting counterparty by a swap data repository pursuant to § 49.11 of this chapter. In order to satisfy the requirements of this section, a reporting counterparty shall conform to a swap data repository's policies and procedures created pursuant to § 49.11 of this chapter for verification of swap data.</P>
                        <P>(2) For every open swaps report provided to a reporting counterparty by a swap data repository pursuant to § 49.11 of this chapter, the reporting counterparty shall submit to the swap data repository either a verification of data accuracy in accordance with paragraph (3) of this section or a notice of discrepancy in accordance with paragraph (4) of this section within:</P>
                        <P>(i) 48 hours of the swap data repository providing the open swaps report to the reporting counterparty pursuant to § 49.11 of this chapter, if the reporting counterparty is a swap dealer, major swap participant, or a derivatives clearing organization; or</P>
                        <P>(ii) 96 hours of the swap data repository providing the open swaps report to the reporting counterparty pursuant to § 49.11 of this chapter, if the reporting counterparty is not a swap dealer, major swap participant, or a derivatives clearing organization.</P>
                        <P>(3) If a reporting counterparty finds no discrepancies between the accurate and current swap data for a swap according to the reporting counterparty's internal books and records and the swap data for the swap contained in the open swaps report provided by the swap data repository, the reporting counterparty shall submit a verification of data accuracy indicating that the swap data is complete and accurate to the swap data repository in the form and manner required by the swap data repository's policies and procedures created pursuant to § 49.11 of this chapter.</P>
                        <P>
                            (4) If the reporting counterparty finds any discrepancy between the accurate and current swap data for a swap according to the reporting counterparty's internal books and records and the swap data for the swap contained in the open swaps report provided by the swap data repository, including, but not limited to, any over-reporting or under-reporting of swap data for any swap, the reporting counterparty shall submit a notice of discrepancy to the swap data repository 
                            <PRTPAGE P="21099"/>
                            in the form and manner required by the swap data repository's policies and procedures created pursuant to § 49.11 of this chapter.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Correction of errors and omissions in swap data.</E>
                             (1) Any swap execution facility, designated contract market, or reporting counterparty that by any means becomes aware of any error or omission in swap data previously reported to a swap data repository by the swap execution facility, designated contract market, or reporting counterparty, or of the omission of swap data for a swap that was not previously reported to a swap data repository as required under this part by the swap execution facility, designated contract market, or reporting counterparty, including, but not limited to, errors or omissions present during the verification process specified in paragraph (a) of this section, shall, as applicable, submit corrected swap data to the swap data repository that maintains the swap data for the relevant swap or correctly report swap data for a swap that was not previously reported to a swap data repository as required under this part, regardless of the state of the swap that is the subject of the swap data.
                        </P>
                        <P>(i) The swap execution facility, designated contract market, or reporting counterparty shall submit the corrections for errors or submit the omitted swap data to the swap data repository as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days following the discovery of the errors or omissions.</P>
                        <P>(ii) If the swap execution facility, designated contract market, or reporting counterparty is unable to correct the errors or omissions within three business days following discovery of the errors or omissions, the swap execution facility, designated contract market, or reporting counterparty shall immediately inform the Director of the Division of Market Oversight, or such other employee or employees of the Commission as the Director may designate from time to time, in writing, of such errors or omissions and provide an initial assessment of the scope of the errors or omissions and an initial remediation plan for correcting the errors or omissions.</P>
                        <P>(iii) In order to satisfy the requirements of this section, a swap execution facility, designated contract market, or reporting counterparty shall conform to a swap data repository's policies and procedures created pursuant to § 49.10 of this chapter for correction of errors or omissions in previously-reported swap data and reporting of omitted swap data.</P>
                        <P>(2) Any non-reporting counterparty that by any means becomes aware of any error or omission in swap data previously reported to a swap data repository, or of the omission of swap data for a swap that was not previously reported to a swap data repository as required under this part, for a swap to which it is the non-reporting counterparty, shall notify the reporting counterparty for the swap of the errors or omissions as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days following the discovery of the errors or omissions. If the non-reporting counterparty does not know the identity of the reporting counterparty, the non-reporting counterparty shall notify the swap execution facility or designated contract market where the swap was executed of the errors or omissions as soon as technologically practicable following discovery of the errors or omissions, but no later than three business days following the discovery of the errors or omissions. If, as applicable, the reporting counterparty and non-reporting counterparty, or the swap execution facility or designated contract market and non-reporting counterparty, agree that the swap data for a swap is incorrect or incomplete, the reporting counterparty, swap execution facility, or designated contract market, as applicable, shall correct the swap data in accordance with paragraph (b)(1) of this section.</P>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 49—SWAP DATA REPOSITORIES</HD>
                    </PART>
                    <AMDPAR>10. The authority citation for Part 49 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 7 U.S.C. 1a, 2(a), 6r, 12a, and 24a, as amended by Title VII of the Wall Street Reform and Consumer Protection Act of 2010, Pub. L. 111-203, 124 Stat. 1376 (Jul. 21, 2010), unless otherwise noted.</P>
                    </AUTH>
                    <PART>
                        <HD SOURCE="HED">PART 49 [AMENDED]</HD>
                    </PART>
                    <AMDPAR>11. In part 49:</AMDPAR>
                    <AMDPAR>a. Remove the phrase to “registered swap data repository” and add in its place “swap data repository”;</AMDPAR>
                    <AMDPAR>b. Remove the phrase “Registered Swap Data Repository” and add in its place “Swap Data Repository”; and</AMDPAR>
                    <AMDPAR>c. Remove the phrase “registered swap data repositories” and add in its place “swap data repositories.”</AMDPAR>
                    <AMDPAR>12. In the table below, for each section and paragraph indicated in the left column, remove the term indicated in the middle column from wherever it appears in the section or paragraph, and add in its place the term indicated in the right column:</AMDPAR>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s75,xl150,r150">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Section</CHED>
                            <CHED H="1">Remove</CHED>
                            <CHED H="1">Add</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">49.3(d)</ENT>
                            <ENT>swap transaction data</ENT>
                            <ENT>SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.3(d)</ENT>
                            <ENT>§ 40.1(e)</ENT>
                            <ENT>§ 40.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.4(c) (heading)</ENT>
                            <ENT>
                                <E T="03">Revocation of Registration for False Application.</E>
                            </ENT>
                            <ENT>
                                <E T="03">Revocation of registration for false application.</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.16(a)(2)(i)</ENT>
                            <ENT>Section 8 Material</ENT>
                            <ENT>section 8 material</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.16(a)(2)(ii)</ENT>
                            <ENT>Other SDR Information</ENT>
                            <ENT>other SDR information or SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.16(a)(2)(iii)</ENT>
                            <ENT>Intellectual</ENT>
                            <ENT>intellectual</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.16(a)(2)(iii)</ENT>
                            <ENT>person associated with the swap data repository</ENT>
                            <ENT>person associated with a swap data repository</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.16(a)(2)(iii)(A)</ENT>
                            <ENT>Section 8 Material</ENT>
                            <ENT>section 8 material</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.16(a)(2)(iii)(A)</ENT>
                            <ENT>other SDR Information</ENT>
                            <ENT>SDR information or SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.16(a)(2)(iii)(B)</ENT>
                            <ENT>persons associated with the swap data repository</ENT>
                            <ENT>persons associated with a swap data repository</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(a)</ENT>
                            <ENT>swap data</ENT>
                            <ENT>SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(a)</ENT>
                            <ENT>Section 8 of the Act</ENT>
                            <ENT>section 8 of the Act</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(b)(1)(heading)</ENT>
                            <ENT>
                                <E T="03">Appropriate Domestic Regulator.</E>
                            </ENT>
                            <ENT>
                                <E T="03">Appropriate domestic regulator.</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(b)(1)</ENT>
                            <ENT>
                                The term “
                                <E T="03">Appropriate Domestic Regulator”</E>
                                 shall mean:
                            </ENT>
                            <ENT>
                                The term “
                                <E T="03">appropriate domestic regulator”</E>
                                 shall mean:
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(b)(2)(heading)</ENT>
                            <ENT>
                                <E T="03">Appropriate Foreign Regulator.</E>
                            </ENT>
                            <ENT>
                                <E T="03">Appropriate foreign regulator.</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(b)(2)</ENT>
                            <ENT>
                                The term “
                                <E T="03">Appropriate Foreign Regulator”</E>
                                 shall mean
                            </ENT>
                            <ENT>
                                The term “
                                <E T="03">appropriate foreign regulator”</E>
                                 shall mean
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(b)(2)</ENT>
                            <ENT>those Foreign Regulators</ENT>
                            <ENT>those foreign regulators</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(c)(2)</ENT>
                            <ENT>analyzing of swap data</ENT>
                            <ENT>analyzing of SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(c)(2)</ENT>
                            <ENT>transfer of data</ENT>
                            <ENT>transfer of SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(c)(3)</ENT>
                            <ENT>swap data provided</ENT>
                            <ENT>SDR data provided</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(c)(3)</ENT>
                            <ENT>authorizedusers</ENT>
                            <ENT>authorized users</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="21100"/>
                            <ENT I="01">49.17(d)(1)(heading)</ENT>
                            <ENT>
                                <E T="03">General Procedure for Gaining Access to Registered Swap Data Repository Data.</E>
                            </ENT>
                            <ENT>
                                <E T="03">General procedure for gaining access to swap data repository swap data.</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(1)(i)</ENT>
                            <ENT>Appropriate Domestic Regulator</ENT>
                            <ENT>appropriate domestic regulator</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(1)(i)</ENT>
                            <ENT>Appropriate Foreign Regulator</ENT>
                            <ENT>appropriate foreign regulator</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(1)(ii)</ENT>
                            <ENT>Appropriate Domestic Regulators and Appropriate Foreign Regulators seeking</ENT>
                            <ENT>Appropriate domestic regulators and appropriate foreign regulators seeking</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(1)(ii)</ENT>
                            <ENT>applicable to Appropriate Domestic Regulators and Appropriate Foreign Regulators</ENT>
                            <ENT>applicable to appropriate domestic regulators and appropriate foreign regulators</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(3)(heading)</ENT>
                            <ENT>
                                <E T="03">Foreign Regulator</E>
                            </ENT>
                            <ENT>
                                <E T="03">Foreign regulator</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(3)</ENT>
                            <ENT>Foreign Regulator</ENT>
                            <ENT>foreign regulator</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(3)</ENT>
                            <ENT>Foreign Regulator's</ENT>
                            <ENT>foreign regulator's</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(4)(heading)</ENT>
                            <ENT>
                                <E T="03">requests for data access</E>
                            </ENT>
                            <ENT>
                                <E T="03">requests for swap data access</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(4)(i)</ENT>
                            <ENT>Appropriate Domestic Regulator or Appropriate Foreign Regulator</ENT>
                            <ENT>appropriate domestic regulator or appropriate foreign regulator</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(4)(i)</ENT>
                            <ENT>Appropriate Domestic Regulator's or Appropriate Foreign Regulator's</ENT>
                            <ENT>appropriate domestic regulator's or appropriate foreign regulator's</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(4)(iii)</ENT>
                            <ENT>Appropriate Domestic Regulator or Appropriate Foreign Regulator</ENT>
                            <ENT>appropriate domestic regulator or appropriate foreign regulator</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(4)(iii)</ENT>
                            <ENT>Appropriate Domestic Regulator's or Appropriate Foreign Regulator's</ENT>
                            <ENT>appropriate domestic regulator's or appropriate foreign regulator's</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(5)(heading)</ENT>
                            <ENT>
                                <E T="03">Timing; Limitation, Suspension or Revocation of Swap Data Access.</E>
                            </ENT>
                            <ENT>
                                <E T="03">Timing, limitation, suspension, or revocation of swap data access.</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(5)</ENT>
                            <ENT>Appropriate Domestic Regulator or Appropriate Foreign Regulator</ENT>
                            <ENT>appropriate domestic regulator or appropriate foreign regulator</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(6)(heading)</ENT>
                            <ENT>
                                <E T="03">Confidentiality Arrangement.</E>
                            </ENT>
                            <ENT>
                                <E T="03">Confidentiality arrangement.</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(d)(6)</ENT>
                            <ENT>Appropriate Domestic Regulator or Appropriate Foreign Regulator</ENT>
                            <ENT>appropriate domestic regulator or appropriate foreign regulator</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(e)</ENT>
                            <ENT>swap data and SDR Information</ENT>
                            <ENT>SDR data and SDR information</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(e)(1)</ENT>
                            <ENT>swap data and SDR Information</ENT>
                            <ENT>SDR data and SDR information</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(e)(2)</ENT>
                            <ENT>swap data or SDR Information</ENT>
                            <ENT>SDR data or SDR information</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(e)(2)</ENT>
                            <ENT>swap data and SDR Information</ENT>
                            <ENT>SDR data and SDR information</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(f)(1)</ENT>
                            <ENT>swap data maintained</ENT>
                            <ENT>SDR data maintained</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(g) (heading)</ENT>
                            <ENT>Commercial uses of data</ENT>
                            <ENT>Commercial uses of SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(g)</ENT>
                            <ENT>Swap data accepted</ENT>
                            <ENT>SDR data accepted</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(g)(1)</ENT>
                            <ENT>swap data required</ENT>
                            <ENT>SDR data required</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(g)(2)(A)</ENT>
                            <ENT>The swap dealer, counterparty, or any other registered entity</ENT>
                            <ENT>The swap execution facility, designated contract market, or reporting counterparty</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(g)(2)(A)</ENT>
                            <ENT>swap data maintained</ENT>
                            <ENT>SDR data maintained</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(g)(2)(B)</ENT>
                            <ENT>swap transaction data</ENT>
                            <ENT>SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(g)(2)(B)</ENT>
                            <ENT>reporting party</ENT>
                            <ENT>swap execution facility, designated contract market, or reporting counterparty</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(g)(2)(B)</ENT>
                            <ENT>any reported data</ENT>
                            <ENT>any reported SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(g)(3)</ENT>
                            <ENT>real-time swap data</ENT>
                            <ENT>swap transaction and pricing data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(h)(3)</ENT>
                            <ENT>CEA section 21(c)(7)</ENT>
                            <ENT>section 21(c)(7) of the Act</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.17(h)(4)</ENT>
                            <ENT>Appropriate Domestic Regulator or Appropriate Foreign Regulator</ENT>
                            <ENT>appropriate domestic regulator or appropriate foreign regulator</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.18(a)(heading)</ENT>
                            <ENT>
                                <E T="03">Appropriate Domestic Regulator or Appropriate Foreign Regulator.</E>
                            </ENT>
                            <ENT>
                                <E T="03">appropriate domestic regulator or appropriate foreign regulator.</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.18(a)</ENT>
                            <ENT>Appropriate Domestic Regulator or Appropriate Foreign Regulator</ENT>
                            <ENT>appropriate domestic regulator or appropriate foreign regulator</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.18(a)</ENT>
                            <ENT>Appropriate Domestic Regulator's or Appropriate Foreign Regulator's</ENT>
                            <ENT>appropriate domestic regulator's or appropriate foreign regulator's</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.18(d)</ENT>
                            <ENT>Appropriate Domestic Regulator or Appropriate Foreign Regulator</ENT>
                            <ENT>appropriate domestic regulator or appropriate foreign regulator</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.18(d)</ENT>
                            <ENT>Appropriate Domestic Regulator's or Appropriate Foreign Regulator's</ENT>
                            <ENT>appropriate domestic regulator's or appropriate foreign regulator's</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.19(a)</ENT>
                            <ENT>paragraph</ENT>
                            <ENT>section</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.20(b)(heading)</ENT>
                            <ENT>
                                <E T="03">Transparency of Governance Arrangements.</E>
                            </ENT>
                            <ENT>
                                <E T="03">Transparency of governance arrangements.</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.20(c)(1)(i)</ENT>
                            <ENT>Regulation</ENT>
                            <ENT>section</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.20(c)(1)(i)(A)(2)</ENT>
                            <ENT>Independent Perspective</ENT>
                            <ENT>independent perspective</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.20(c)(1)(i)(B)</ENT>
                            <ENT>Independent Perspective</ENT>
                            <ENT>independent perspective</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.20(c)(5)</ENT>
                            <ENT>Regulation</ENT>
                            <ENT>section</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.23(a)</ENT>
                            <ENT>swap transaction data</ENT>
                            <ENT>SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.23(e)(heading)</ENT>
                            <ENT>commission</ENT>
                            <ENT>Commission</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.24(a)</ENT>
                            <ENT>all swap data in its custody</ENT>
                            <ENT>all SDR data in its custody</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.24(e)(3)(i)</ENT>
                            <ENT>dissemination of swap data</ENT>
                            <ENT>dissemination of SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.24(e)(3)(ii)</ENT>
                            <ENT>normal swap data reporting,</ENT>
                            <ENT>normal SDR data reporting,</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.24(f)(2)</ENT>
                            <ENT>all swap data contained</ENT>
                            <ENT>all SDR data contained</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.24(j)(1) Definition of “Controls”</ENT>
                            <ENT>data and information</ENT>
                            <ENT>SDR data and SDR information</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.24(j)(1) Definition of “Enterprise technology risk assessment”</ENT>
                            <ENT>data and information</ENT>
                            <ENT>SDR data and SDR information</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="21101"/>
                            <ENT I="01">49.24(j)(1) Definition of “Security incident”</ENT>
                            <ENT>integrity of data</ENT>
                            <ENT>integrity of SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.24(k)(1)</ENT>
                            <ENT>report swap data</ENT>
                            <ENT>report SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.24(k)(2)</ENT>
                            <ENT>report swap data</ENT>
                            <ENT>report SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.24(l)(3)</ENT>
                            <ENT>any data related to</ENT>
                            <ENT>any SDR data related to</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.24(m)</ENT>
                            <ENT>Board of Directors</ENT>
                            <ENT>board of directors</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.26(a)</ENT>
                            <ENT>swap data maintained</ENT>
                            <ENT>SDR data maintained</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.26(c)</ENT>
                            <ENT>safeguarding of swap data</ENT>
                            <ENT>safeguarding of SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.26(d)</ENT>
                            <ENT>any and all swap data</ENT>
                            <ENT>any and all SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.26(d)</ENT>
                            <ENT>reporting entity</ENT>
                            <ENT>swap execution facility, designated contract market, or reporting counterparty</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.26(e)</ENT>
                            <ENT>swap data that it receives</ENT>
                            <ENT>SDR data that it receives</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.26(e)</ENT>
                            <ENT>market participant, any registered entity, or any other person;</ENT>
                            <ENT>swap execution facility, designated contract market, or reporting counterparty;</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.26(h)</ENT>
                            <ENT>rebates; and</ENT>
                            <ENT>rebates;</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.26(i)</ENT>
                            <ENT>arrangements.</ENT>
                            <ENT>arrangements; and</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.27(a)(2)</ENT>
                            <ENT>Regulation</ENT>
                            <ENT>section</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">49.27(b)</ENT>
                            <ENT>reporting of swap data</ENT>
                            <ENT>reporting of SDR data</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Part 49, App. B (heading)</ENT>
                            <ENT>Registered Swap Data Respositories</ENT>
                            <ENT>Swap Data Repositories</ENT>
                        </ROW>
                    </GPOTABLE>
                    <AMDPAR>13. Revise § 49.2 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.2 </SECTNO>
                        <SUBJECT> Definitions.</SUBJECT>
                        <P>(a) As used in this part:</P>
                        <P>
                            <E T="03">Affiliate.</E>
                             The term “
                            <E T="03">affiliate”</E>
                             means a person that directly, or indirectly, controls, is controlled by, or is under common control with, the swap data repository.
                        </P>
                        <P>
                            <E T="03">As soon as technologically practicable.</E>
                             The term “
                            <E T="03">as soon as technologically practicable”</E>
                             means as soon as possible, taking into consideration the prevalence, implementation, and use of technology by comparable market participants.
                        </P>
                        <P>
                            <E T="03">Asset class.</E>
                             The term “
                            <E T="03">asset class”</E>
                             means a broad category of commodities including, without limitation, any “excluded commodity” as defined in section 1a(19) of the Act, with common characteristics underlying a swap. The asset classes include interest rate, foreign exchange, credit, equity, other commodity, and such other asset classes as may be determined by the Commission.
                        </P>
                        <P>
                            <E T="03">Commercial use.</E>
                             The term “
                            <E T="03">commercial use”</E>
                             means the use of SDR data held and maintained by a swap data repository for a profit or business purposes. A swap data repository's use of SDR data for regulatory purposes and/or to perform its regulatory responsibilities would not be considered a commercial use regardless of whether the swap data repository charges a fee for reporting such SDR data.
                        </P>
                        <P>
                            <E T="03">Control.</E>
                             The term “
                            <E T="03">control”</E>
                             (including the terms “
                            <E T="03">controlled by”</E>
                             and “
                            <E T="03">under common control with”</E>
                            ) means the possession, direct or indirect, of the power to direct or cause the direction of the management and policies of a person, whether through the ownership of voting securities, by contract, or otherwise.
                        </P>
                        <P>
                            <E T="03">Foreign regulator.</E>
                             The term “
                            <E T="03">foreign regulator”</E>
                             means a foreign futures authority as defined in section 1a(26) of the Act, foreign financial supervisors, foreign central banks, foreign ministries, and other foreign authorities.
                        </P>
                        <P>
                            <E T="03">Independent perspective.</E>
                             The term “
                            <E T="03">independent perspective”</E>
                             means a viewpoint that is impartial regarding competitive, commercial, or industry concerns and contemplates the effect of a decision on all constituencies involved.
                        </P>
                        <P>
                            <E T="03">Market participant.</E>
                             The term “
                            <E T="03">market participant”</E>
                             means any person participating in the swap market, including, but not limited to, designated contract markets, derivatives clearing organizations, swap execution facilities, swap dealers, major swap participants, and any other counterparty to a swap transaction.
                        </P>
                        <P>
                            <E T="03">Non-affiliated third party.</E>
                             The term “
                            <E T="03">non-affiliated third party”</E>
                             means any person except:
                        </P>
                        <P>(1) The swap data repository;</P>
                        <P>(2) The swap data repository's affiliate; or</P>
                        <P>(3) A person jointly employed by a swap data repository and any entity that is not the swap data repository's affiliate (the term “non-affiliated third party” includes such entity that jointly employs the person).</P>
                        <P>
                            <E T="03">Non-swap dealer/major swap participant/derivatives clearing organization reporting counterparty.</E>
                             The term “
                            <E T="03">non-swap dealer/major swap participant/derivatives clearing organization reporting counterparty”</E>
                             means a reporting counterparty that is not a swap dealer, major swap participant, derivatives clearing organization, or exempt derivatives clearing organization.
                        </P>
                        <P>
                            <E T="03">Open swap.</E>
                             The term “
                            <E T="03">open swap”</E>
                             means an executed swap transaction that has not reached maturity or the final contractual settlement date, and has not been exercised, closed out, or terminated.
                        </P>
                        <P>
                            <E T="03">Person associated with a swap data repository.</E>
                             The term “
                            <E T="03">person associated with a swap data repository”</E>
                             means:
                        </P>
                        <P>(1) Any partner, officer, or director of such swap data repository (or any person occupying a similar status or performing similar functions);</P>
                        <P>(2) Any person directly or indirectly controlling, controlled by, or under common control with such swap data repository; or</P>
                        <P>(3) Any person employed by such swap data repository, including a jointly employed person.</P>
                        <P>
                            <E T="03">Position.</E>
                             The term “
                            <E T="03">position”</E>
                             means the gross and net notional amounts of open swap transactions aggregated by one or more attributes, including, but not limited to, the:
                        </P>
                        <P>(1) Underlying instrument;</P>
                        <P>(2) Index, or reference entity;</P>
                        <P>(3) Counterparty;</P>
                        <P>(4) Asset class;</P>
                        <P>(5) Long risk of the underlying instrument, index, or reference entity; and</P>
                        <P>(6) Short risk of the underlying instrument, index, or reference entity.</P>
                        <P>
                            <E T="03">Reporting counterparty.</E>
                             The term “
                            <E T="03">reporting counterparty”</E>
                             means the counterparty responsible for reporting SDR data to a swap data repository pursuant to parts 43, 45, or 46 of this chapter.
                        </P>
                        <P>
                            <E T="03">SDR data.</E>
                             The term “
                            <E T="03">SDR data”</E>
                             means the specific data elements and information required to be reported to a swap data repository or disseminated by a swap data repository pursuant to two or more of parts 43, 45, 46, and/or 49 
                            <PRTPAGE P="21102"/>
                            of this chapter, as applicable in the context.
                        </P>
                        <P>
                            <E T="03">SDR information.</E>
                             The term “
                            <E T="03">SDR information”</E>
                             means any information that the swap data repository receives or maintains related to the business of the swap data repository that is not SDR data.
                        </P>
                        <P>
                            <E T="03">Section 8 material.</E>
                             The term “
                            <E T="03">section 8 material”</E>
                             means the business transactions, SDR data, or market positions of any person and trade secrets or names of customers.
                        </P>
                        <P>
                            <E T="03">Swap data.</E>
                             The term “
                            <E T="03">swap data”</E>
                             means the specific data elements and information required to be reported to a swap data repository pursuant to part 45 of this chapter or made available to the Commission pursuant to this part, as applicable.
                        </P>
                        <P>
                            <E T="03">Swap transaction and pricing data.</E>
                             The term “
                            <E T="03">swap transaction and pricing data”</E>
                             means the specific data elements and information required to be reported to a swap data repository or publicly disseminated by a swap data repository pursuant to part 43 of this chapter, as applicable.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Other defined terms.</E>
                             Terms not defined in this part have the meanings assigned to the terms in § 1.3 of this chapter.
                        </P>
                    </SECTION>
                    <AMDPAR>14. In § 49.3, revise paragraph (a)(5) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.3 </SECTNO>
                        <SUBJECT> Procedures for registration.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>
                            (5) 
                            <E T="03">Amendments.</E>
                             If any information reported on Form SDR or in any amendment thereto is or becomes inaccurate for any reason before the application for registration has been granted under this paragraph (a), the swap data repository shall promptly file an amendment on Form SDR updating such information.
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>15. Revise § 49.5 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.5 </SECTNO>
                        <SUBJECT> Equity interest transfers.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Equity interest transfer notification.</E>
                             A swap data repository shall file with the Commission a notification of each transaction involving the direct or indirect transfer of ten percent or more of the equity interest in the swap data repository. The Commission may, upon receiving such notification, request that the swap data repository provide supporting documentation of the transaction.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Timing of notification.</E>
                             The equity interest transfer notice described in paragraph (a) of this section shall be filed electronically with the Secretary of the Commission at its Washington, DC headquarters at 
                            <E T="03">submissions@cftc.gov</E>
                             and the Division of Market Oversight at 
                            <E T="03">DMOSubmissions@cftc.gov,</E>
                             at the earliest possible time but in no event later than the open of business ten business days following the date upon which a firm obligation is made to transfer, directly or indirectly, ten percent or more of the equity interest in the swap data repository.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Certification.</E>
                             Upon a transfer, whether directly or indirectly, of an equity interest of ten percent or more in a swap data repository, the swap data repository shall file electronically with the Secretary of the Commission at its Washington, DC headquarters at 
                            <E T="03">submissions@cftc.gov</E>
                             and the Division of Market Oversight at 
                            <E T="03">DMOSubmissions@cftc.gov,</E>
                             a certification that the swap data repository meets all of the requirements of section 21 of the Act and the Commission regulations adopted thereunder, no later than two business days following the date on which the equity interest of ten percent or more was acquired.
                        </P>
                    </SECTION>
                    <AMDPAR>16. Revise § 49.6 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.6 </SECTNO>
                        <SUBJECT> Request for transfer of registration.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Request for approval.</E>
                             A swap data repository seeking to transfer its registration from its current legal entity to a new legal entity as a result of a corporate change shall file a request for approval to transfer such registration with the Secretary of the Commission in the form and manner specified by the Commission.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Timing for filing a request for transfer of registration.</E>
                             A swap data repository shall file a request for transfer of registration as soon as practicable prior to the anticipated corporate change.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Required information.</E>
                             The request for transfer of registration shall include the following:
                        </P>
                        <P>(1) The underlying documentation that governs the corporate change;</P>
                        <P>(2) A description of the corporate change, including the reason for the change and its impact on the swap data repository, including the swap data repository's governance and operations, and its impact on the rights and obligations of market participants;</P>
                        <P>(3) A discussion of the transferee's ability to comply with the Act, including the core principles applicable to swap data repositories and the Commission's regulations;</P>
                        <P>(4) The governance documents adopted by the transferee, including a copy of any constitution; articles or certificate of incorporation, organization, formation, or association with all amendments thereto; partnership or limited liability agreements; and any existing bylaws, operating agreement, or rules or instruments corresponding thereto;</P>
                        <P>(5) The transferee's rules marked to show changes from the current rules of the swap data repository; and</P>
                        <P>(6) A representation by the transferee that it:</P>
                        <P>(i) Will be the surviving entity and successor-in-interest to the transferor swap data repository and will retain and assume the assets and liabilities of the transferor, except if otherwise indicated in the request;</P>
                        <P>(ii) Will assume responsibility for complying with all applicable provisions of the Act and the Commission's regulations; and</P>
                        <P>(iii) Will notify market participants of all changes to the transferor's rulebook prior to the transfer, including those changes that may affect the rights and obligations of market participants, and will further notify market participants of the concurrent transfer of the registration to the transferee upon Commission approval and issuance of an order permitting the transfer.</P>
                        <P>
                            (d) 
                            <E T="03">Commission determination.</E>
                             Upon review of a request for transfer of registration, the Commission, as soon as practicable, shall issue an order either approving or denying the request for transfer of registration.
                        </P>
                    </SECTION>
                    <AMDPAR>17. Revise § 49.9 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.9 </SECTNO>
                        <SUBJECT> Open swaps reports provided to the Commission.</SUBJECT>
                        <P>Each swap data repository shall provide reports of open swaps to the Commission in accordance with this section.</P>
                        <P>
                            (a) 
                            <E T="03">Content of the open swaps report.</E>
                             In order to satisfy the requirements of this section, each swap data repository shall provide the Commission with open swaps reports that contain an accurate reflection of the swap data for every swap data field required to be reported for swaps pursuant to part 45 of this chapter for every open swap maintained by the swap data repository, organized by the unique identifier created pursuant to § 45.5 of this chapter associated with each open swap, as of the time the swap data repository compiles the open swaps report.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Transmission of the open swaps report.</E>
                             A swap data repository shall transmit all open swaps reports to the Commission as instructed by the Commission. Such instructions may include, but are not limited to, the method, timing, and frequency of transmission as well as the format of the swap data to be transmitted.
                        </P>
                    </SECTION>
                    <AMDPAR> 18. In § 49.10, add paragraph (e) to read as follows:</AMDPAR>
                    <SECTION>
                        <PRTPAGE P="21103"/>
                        <SECTNO>§ 49.10 </SECTNO>
                        <SUBJECT> Acceptance of data.</SUBJECT>
                        <STARS/>
                        <P>
                            (e) 
                            <E T="03">Errors and omissions.</E>
                             In accordance with this paragraph (e), a swap data repository shall correct errors and omissions in SDR data previously reported to the swap data repository pursuant to parts 43, 45, and 46 of this chapter and shall correct omissions in reporting SDR data for swaps that were not previously reported to the swap data repository as required under parts 43, 45, or 46 of this chapter, regardless of the state of the swap that is the subject of the SDR data.
                        </P>
                        <P>(1) A swap data repository shall accept corrections for errors and omissions reported to the swap data repository pursuant to parts 43, 45, or 46 of this chapter.</P>
                        <P>(2) A swap data repository shall correct the reported errors and omissions as soon as technologically practicable after the swap data repository receives a report of errors or omissions.</P>
                        <P>(3) A swap data repository shall disseminate corrected SDR data to the public and the Commission, as applicable, in accordance with this chapter, as soon as technologically practicable after the swap data repository corrects the SDR data.</P>
                        <P>(4) A swap data repository shall establish, maintain, and enforce policies and procedures designed for the swap data repository to accept corrections for errors and omissions, to correct the errors and omissions as soon as technologically practicable after the swap data repository receives a report of errors or omissions, and to disseminate such corrected SDR data to the public and to the Commission, as applicable, in accordance with this chapter.</P>
                    </SECTION>
                    <AMDPAR>19. Revise § 49.11 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.11 </SECTNO>
                        <SUBJECT> Verification of swap data accuracy.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">General requirement.</E>
                             Each swap data repository shall verify the accuracy and completeness of swap data that it receives from swap execution facilities, designated contract markets, or reporting counterparties, or third-party service providers acting on their behalf, in accordance with paragraph (b) of this section. A swap data repository shall also establish, maintain, and enforce policies and procedures reasonably designed to verify the accuracy and completeness of swap data that it receives from swap execution facilities, designated contract markets, or reporting counterparties, or third-party service providers acting on their behalf.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Distribution of open swaps reports.</E>
                             In order to verify the accuracy and completeness of swap data as required by this section, a swap data repository shall, on a regular basis, distribute to each reporting counterparty an open swaps report detailing the swap data maintained by the swap data repository for all open swaps as of the time the swap data repository compiles the open swaps report for which the recipient of the open swaps report is the reporting counterparty.
                        </P>
                        <P>
                            (1) 
                            <E T="03">Content of open swaps reports.</E>
                             In order to satisfy the requirements of this section, the swap data repository shall distribute an open swaps report that contains an accurate reflection of the swap data for every swap data field required to be reported for swaps pursuant to part 45 of this chapter, unless access to a particular data field is prohibited by other Commission regulations, for every open swap maintained by the swap data repository for which the recipient of the report is the reporting counterparty, organized by the unique identifier created pursuant to § 45.5 of this chapter associated with every open swap, as of the time the swap data repository compiles the open swaps report.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Frequency of open swaps reports for swap dealer, major swap participant, and derivatives clearing organization reporting counterparties.</E>
                             In order to satisfy the requirements of this section, the swap data repository shall distribute an open swaps report to all reporting counterparties that are swap dealers, major swap participants, or derivatives clearing organizations on a weekly basis, no later than 11:59 p.m. Eastern time on the day of the week that the swap data repository chooses to regularly distribute the open swaps reports. The swap data repository shall distribute all open swaps reports on the same day of the week.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Frequency of open swaps reports for non-swap dealer/major swap participant/derivatives clearing organization reporting counterparties.</E>
                             In order to satisfy the requirements of this section, the swap data repository shall distribute an open swaps report to all non-swap dealer/major swap participant/derivatives clearing organization reporting counterparties on a monthly basis, no later than 11:59 p.m. Eastern time on the day of the month that the swap data repository chooses to regularly distribute the open swaps report. The swap data repository shall distribute all open swaps reports on the same day of the month.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Receipt of verification of data accuracy or notice of discrepancy.</E>
                             In order to satisfy the requirements of this section, the swap data repository shall receive from each reporting counterparty for each open swaps report (i) a verification of data accuracy indicating that the swap data contained in an open swaps report distributed pursuant to paragraph (b) of this section is accurate and complete or (ii) a notice of discrepancy indicating that the swap data contained in an open swaps report contains one or more discrepancies, in accordance with § 45.14 of this chapter. The swap data repository shall establish, maintain, and enforce policies and procedures reasonably designed for the swap data repository to successfully receive the verification of data accuracy or notice of discrepancy.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Amending verification policies and procedures.</E>
                             A swap data repository shall comply with the requirements under part 40 of this chapter in adopting or amending the policies and procedures required by this section.
                        </P>
                    </SECTION>
                    <AMDPAR>20. Revise § 49.12 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.12 </SECTNO>
                        <SUBJECT> Swap data repository recordkeeping requirements.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">General requirement.</E>
                             A swap data repository shall keep full, complete, and systematic records, together with all pertinent data and memoranda, of all activities relating to the business of the swap data repository, including, but not limited to, all SDR information and all SDR data that is reported to the swap data repository pursuant to this chapter.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Maintenance of records.</E>
                             A swap data repository shall maintain all records required to be kept by this section in accordance with this paragraph (b).
                        </P>
                        <P>(1) A swap data repository shall maintain all SDR information, including, but not limited to, all documents, policies, and procedures required by the Act and the Commission's regulations, correspondence, memoranda, papers, books, notices, accounts, and other such records made or received by the swap data repository in the course of its business. All SDR information shall be maintained in accordance with § 1.31 of this chapter.</P>
                        <P>
                            (2) A swap data repository shall maintain all SDR data and timestamps reported to or created by the swap data repository pursuant to this chapter, and all messages related to such reporting, throughout the existence of the swap that is the subject of the SDR data and for five years following final termination of the swap, during which time the records shall be readily accessible by the swap data repository and available to the Commission via real-time electronic access, and for a period of at least ten additional years in archival storage from which such records are retrievable by the swap data repository within three business days.
                            <PRTPAGE P="21104"/>
                        </P>
                        <P>
                            (c) 
                            <E T="03">Records of data errors and omissions.</E>
                             A swap data repository shall create and maintain records of data validation errors and SDR data reporting errors and omissions in accordance with this paragraph (c).
                        </P>
                        <P>(1) A swap data repository shall create and maintain an accurate record of all reported SDR data that fails to satisfy the swap data repository's data validation procedures including, but not limited to, all SDR data reported to the swap data repository that fails to satisfy the data validation procedures, all data validation errors, and all related messages and timestamps. A swap data repository shall make these records available to the Commission on request.</P>
                        <P>(2) A swap data repository shall create and maintain an accurate record of all SDR data errors and omissions reported to the swap data repository and all corrections disseminated by the swap data repository pursuant to parts 43, 45, and 46 of this chapter. A swap data repository shall make these records available to the Commission on request.</P>
                        <P>
                            (d) 
                            <E T="03">Availability of records.</E>
                             All records required to be kept pursuant to this part shall be open to inspection upon request by any representative of the Commission or the United States Department of Justice in accordance with the provisions of § 1.31 of this chapter. A swap data repository required to keep, create, or maintain records pursuant to this section shall provide such records in accordance with the provisions of § 1.31 of this chapter, unless otherwise provided in this part.
                        </P>
                    </SECTION>
                    <AMDPAR>21. Revise § 49.13 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.13 </SECTNO>
                        <SUBJECT> Monitoring, screening, and analyzing data.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Duty to monitor, screen, and analyze data.</E>
                             A swap data repository shall establish automated systems for monitoring, screening, and analyzing all relevant SDR data in its possession in the form and manner as may be directed by the Commission. A swap data repository shall routinely monitor, screen, and analyze relevant SDR data at the request of the Commission.
                        </P>
                        <P>
                            (1) 
                            <E T="03">Monitoring, screening, and analyzing.</E>
                             Monitoring, screening, and analyzing requirements shall include utilizing relevant SDR data maintained by the swap data repository to provide information to the Commission concerning such relevant SDR data. Monitoring, screening, and analyzing requests may require the compiling and/or calculation of requested information within discrete categories and/or over periods of time, including the comparison of information from different categories and/or over multiple periods of time. Requests for monitoring, screening, and analyzing may require swap data repositories to provide information to the Commission related to:
                        </P>
                        <P>(i) The accuracy, timeliness, and quality of SDR data reported pursuant to this chapter;</P>
                        <P>(ii) Updates and corrections to, and verification of the accuracy of, SDR data reported pursuant to this chapter;</P>
                        <P>(iii) Currently open swaps and the consistency of SDR data related to individual swaps;</P>
                        <P>(iv) The calculation of market participant swap positions, including for purposes of position limit compliance, risk assessment, and compliance with other regulatory requirements;</P>
                        <P>(v) Swap counterparty exposure to other counterparties and standard market risk metrics;</P>
                        <P>(vi) Swap valuations and margining activities;</P>
                        <P>(vii) Audit trails for individual swaps, including post-transaction events such as allocation, novation, and compression, and all related messages;</P>
                        <P>(viii) Compliance with Commission regulations;</P>
                        <P>(ix) Market surveillance;</P>
                        <P>(x) The use of clearing exemptions and exceptions; and/or</P>
                        <P>(xi) Statistics on swaps market activity.</P>
                        <P>
                            (2) 
                            <E T="03">Discretion of the Commission.</E>
                             All monitoring, screening, and analyzing requests shall be at the discretion of the Commission. Such discretion includes, but is not limited to, the content, scope, and frequency of each required response. All information provided by a swap data repository pursuant to this section shall conform to the form and manner requirements established pursuant to § 49.30 for a particular request.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Timing.</E>
                             All monitoring, screening, and analyzing requests shall be fulfilled within the time specified by the Commission for the particular request.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Capacity to monitor, screen, and analyze SDR data.</E>
                             A swap data repository shall establish and at all times maintain sufficient information technology, staff, and other resources to fulfill the requirements in this section in the manner prescribed by the Commission.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Duty to notify the Commission of noncompliance.</E>
                             A swap data repository shall promptly notify the Commission of any swap transaction for which the swap data repository is aware that:
                        </P>
                        <P>(1) The swap transaction and pricing data was not received by the swap data repository in accordance with part 43 of this chapter;</P>
                        <P>(2) The swap data was not received by the swap data repository in accordance with part 45 of this chapter; or</P>
                        <P>(3) Data was not received by the swap data repository in accordance with part 46 of this chapter.</P>
                    </SECTION>
                    <AMDPAR>22. Revise § 49.15 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.15 </SECTNO>
                        <SUBJECT> Real-time public reporting by swap data repositories.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Scope.</E>
                             The provisions of this section apply to the real-time public reporting of swap transaction and pricing data submitted to a swap data repository pursuant to part 43 of this chapter.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Systems to accept and disseminate data in connection with real-time public reporting.</E>
                             A swap data repository shall establish such electronic systems as are necessary to accept and publicly disseminate swap transaction and pricing data submitted to the swap data repository pursuant to part 43 of this chapter in order to meet the real-time public reporting obligations of part 43 of this chapter. Any electronic system established for this purpose shall be capable of accepting and ensuring the public dissemination of all data fields required by part 43 this chapter.
                        </P>
                    </SECTION>
                    <AMDPAR>23. Amend § 49.16 by revising paragraphs (a)(1), (b), and (c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.16 </SECTNO>
                        <SUBJECT> Privacy and confidentiality requirements of swap data repositories.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(1) Establish, maintain, and enforce written policies and procedures reasonably designed to protect the privacy and confidentiality of any and all SDR information and all SDR data that is not swap transaction and pricing data disseminated under part 43 of this chapter. Such policies and procedures shall include, but are not limited to, policies and procedures to protect the privacy and confidentiality of any and all SDR information and all SDR data (except for swap transaction and pricing data disseminated under part 43 of this chapter) that the swap data repository shares with affiliates and non-affiliated third parties; and</P>
                        <STARS/>
                        <P>(b) A swap data repository shall not, as a condition of accepting SDR data from any swap execution facility, designated contract market, or reporting counterparty, require the waiver of any privacy rights by such swap execution facility, designated contract market, or reporting counterparty.</P>
                        <P>
                            (c) Subject to section 8 of the Act, a swap data repository may disclose aggregated SDR data on a voluntary basis or as requested, in the form and manner prescribed by the Commission.
                            <PRTPAGE P="21105"/>
                        </P>
                    </SECTION>
                    <AMDPAR>24. In § 49.17, revise paragraph (b)(3), the introductory text of paragraph (c), paragraphs (c)(1) and (f)(2) to read as follows and remove paragraph (i).</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.17 </SECTNO>
                        <SUBJECT> Access to SDR data.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>
                            (3) 
                            <E T="03">Direct electronic access.</E>
                             For the purposes of this section, the term “
                            <E T="03">direct electronic access”</E>
                             shall mean an electronic system, platform, framework, or other technology that provides internet-based or other form of access to real-time SDR data that is acceptable to the Commission and also provides scheduled data transfers to Commission electronic systems.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Commission access.</E>
                             A swap data repository shall provide access to the Commission for all SDR data maintained by the swap data repository pursuant to this chapter in accordance with this paragraph (c).
                        </P>
                        <P>
                            (1) 
                            <E T="03">Direct electronic access requirements.</E>
                             A swap data repository shall provide direct electronic access to the Commission or the Commission's designee, including another registered entity, in order for the Commission to carry out its legal and statutory responsibilities under the Act and the Commission's regulations thereunder. A swap data repository shall maintain all SDR data reported to the swap data repository in a format acceptable to the Commission, and shall transmit all SDR data requested by the Commission to the Commission as instructed by the Commission. Such instructions may include, but are not limited to, the method, timing, and frequency of transmission, as well as the format and scope of the SDR data to be transmitted.
                        </P>
                        <STARS/>
                        <P>(f) * * *</P>
                        <P>
                            (2) 
                            <E T="03">Exception.</E>
                             SDR data and SDR information related to a particular swap transaction that is maintained by the swap data repository may be accessed by either counterparty to that particular swap. However, the SDR data and SDR information maintained by the swap data repository that may be accessed by either counterparty to a particular swap shall not include the identity or the legal entity identifier (as such term is used in part 45 of this chapter) of the other counterparty to the swap, or the other counterparty's clearing member for the swap, if the swap is executed anonymously on a swap execution facility or designated contract market, and cleared in accordance with §§ 1.74, 23.610, and 39.12(b)(7) of this chapter.
                        </P>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 49.18 </SECTNO>
                        <SUBJECT> [Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>25. Amend § 49.18 by removing paragraph (e).</AMDPAR>
                    <AMDPAR>26. In § 49.20, revise paragraphs (b)(2)(v), (b)(2)(vii), and (c)(1)(ii)(B) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.20 </SECTNO>
                        <SUBJECT> Governance arrangements (Core Principle 2).</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(2) * * *</P>
                        <P>(v) A description of the manner in which the board of directors, as well as any committee referenced in paragraph (b)(2)(ii) of this section, considers an independent perspective in its decision-making process, as § 49.2(a) defines such term;</P>
                        <STARS/>
                        <P>(vii) Summaries of significant decisions impacting the public interest, the rationale for such decisions, and the process for reaching such decisions. Such significant decisions shall include decisions relating to pricing of repository services, offering of ancillary services, access to SDR data, and use of section 8 material, SDR information, and intellectual property (as referenced in § 49.16). Such summaries of significant decisions shall not require the swap data repository to disclose section 8 material or, where appropriate, information that the swap data repository received on a confidential basis from a swap execution facility, designated contract market, or reporting counterparty.</P>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(1) * * *</P>
                        <P>(ii) * * *</P>
                        <P>(B) A description of the relationship, if any, between such members and the swap data repository or any swap execution facility, designated contract market, or reporting counterparty user thereof (or, in each case, affiliates thereof, as § 49.2(a) defines such term); and</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>27. In § 49.22 revise paragraph (a), (b)(1) introductory text, paragraphs (b)(1)(i), (c), (d)(2) through (6), (e), (f), and (g) to read as follows and remove paragraph (d)(7).</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.22 </SECTNO>
                        <SUBJECT> Chief compliance officer.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Definitions.</E>
                             For purposes of this section, the term—
                        </P>
                        <P>
                            <E T="03">Board of directors</E>
                             means the board of directors of a swap data repository, or for those swap data repositories whose organizational structure does not include a board of directors, a body performing a function similar to a board of directors.
                        </P>
                        <P>
                            <E T="03">Senior officer</E>
                             means the chief executive officer or other equivalent officer of the swap data repository.
                        </P>
                        <P>(b) * * *</P>
                        <P>
                            (1) 
                            <E T="03">Chief compliance officer required.</E>
                             Each swap data repository shall designate an individual to serve as a chief compliance officer.
                        </P>
                        <P>(i) The position of chief compliance officer shall carry with it the authority and resources to develop, in consultation with the board of directors or senior officer, the policies and procedures of the swap data repository and enforce such policies and procedures to fulfill the duties set forth for chief compliance officers in the Act and Commission regulations.</P>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Appointment, supervision, and removal of chief compliance officer.</E>
                             (1) 
                            <E T="03">Appointment and compensation of chief compliance officer.</E>
                             (i) Only the board of directors or senior officer may appoint the chief compliance officer.
                        </P>
                        <P>(ii) The board of directors or senior officer shall approve the compensation of the chief compliance officer.</P>
                        <P>(iii) The swap data repository shall notify the Commission within two business days of the appointment, whether interim or permanent, of a chief compliance officer.</P>
                        <P>
                            (2) 
                            <E T="03">Supervision of chief compliance officer.</E>
                             The chief compliance officer shall report directly to the board of directors or the senior officer of the swap data repository.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Removal of chief compliance officer.</E>
                             (i) Only the board of directors or the senior officer may remove the chief compliance officer.
                        </P>
                        <P>(ii) The swap data repository shall notify the Commission within two business days of the removal, whether interim or permanent, of a chief compliance officer.</P>
                        <P>
                            (4) 
                            <E T="03">Annual meeting with the chief compliance officer.</E>
                             The chief compliance officer shall meet with the board of directors or senior officer of the swap data repository at least annually.
                        </P>
                        <P>(d) * * *</P>
                        <P>(2) Taking reasonable steps, in consultation with the board of directors or the senior officer of the swap data repository, to resolve any material conflicts of interest that may arise;</P>
                        <P>(3) Establishing and administering written policies and procedures reasonably designed to prevent violations of the Act and the rules of the Commission;</P>
                        <P>
                            (4) Taking reasonable steps to ensure compliance with the Act and Commission regulations relating to agreements, contracts, or transactions, and with Commission regulations 
                            <PRTPAGE P="21106"/>
                            created pursuant to section 21 of the Act;
                        </P>
                        <P>(5) Establish procedures reasonably designed to handle, respond, remediate, retest, and resolve noncompliance issues identified by the chief compliance officer through any means, including any compliance office review, look-back, internal or external audit finding, self-reported error, or validated compliant; and</P>
                        <P>(6) Establishing and administering a compliance manual designed to promote compliance with the applicable laws, rules, and regulations and a written code of ethics for the swap data repository designed to prevent ethical violations and to promote honesty and ethical conduct by swap data repository personnel.</P>
                        <P>
                            (e) 
                            <E T="03">Preparation of annual compliance report.</E>
                             The chief compliance officer shall, not less than annually, prepare and sign an annual compliance report that covers the prior fiscal year. The report shall, at a minimum, contain:
                        </P>
                        <P>(1) A description and self-assessment of the effectiveness of the written policies and procedures of the swap data repository, including the code of ethics and conflict of interest policies, designed to reasonably ensure compliance with the Act and applicable Commission regulations;</P>
                        <P>(2) A list of any material changes made to compliance policies and procedures during the coverage period for the report and any areas of improvement or recommended changes to the compliance program;</P>
                        <P>(3) A description of the financial, managerial, and operational resources set aside for compliance with the Act and applicable Commission regulations;</P>
                        <P>(4) A description of any material non-compliance matters identified and an explanation of the corresponding action taken to resolve such non-compliance matters; and</P>
                        <P>(5) A certification by the chief compliance officer that, to the best of his or her knowledge and reasonable belief, and under penalty of law, the annual compliance report is accurate and complete in all material respects.</P>
                        <P>
                            (f) 
                            <E T="03">Submission of annual compliance report and related matters—</E>
                            (1) 
                            <E T="03">Furnishing the annual compliance report prior to submission to the Commission.</E>
                             Prior to submission to the Commission, the chief compliance officer shall provide the annual compliance report for review to the board of directors of the swap data repository or, in the absence of a board of directors, to the senior officer of the swap data repository. Members of the board of directors and the senior officer shall not require the chief compliance officer to make any changes to the annual compliance report.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Submission of annual compliance report to the Commission.</E>
                             The annual compliance report shall be submitted electronically to the Commission not later than 90 calendar days after the end of the swap data repository's fiscal year. The swap data repository shall concurrently file the annual compliance report with the fourth quarter financial report pursuant to § 49.25(f)(3).
                        </P>
                        <P>
                            (3) 
                            <E T="03">Amendments to annual compliance report.</E>
                             Promptly upon discovery of any material error or omission made in a previously filed annual compliance report, the chief compliance officer shall file an amendment with the Commission to correct the material error or omission. The chief compliance officer shall submit the amended annual compliance report to the board of directors, or in the absence of a board of directors, to the senior officer of the swap data repository, pursuant to paragraph (f)(1) of this section. An amendment shall contain the certification required under paragraph (e)(5) of this section.
                        </P>
                        <P>
                            (4) 
                            <E T="03">Requests for extension.</E>
                             A swap data repository may request an extension of time to file its annual compliance report from the Commission. Reasonable and valid requests for extensions of the filing deadline may be granted at the discretion of the Commission.
                        </P>
                        <P>
                            (g) 
                            <E T="03">Recordkeeping.</E>
                             The swap data repository shall maintain all records demonstrating compliance with the duties of the chief compliance officer and the preparation and submission of annual compliance reports consistent with § 49.12(b)(1).
                        </P>
                    </SECTION>
                    <AMDPAR>28. In § 49.24, revise paragraphs (d), the introductory text of (i), and (i)(5) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.24 </SECTNO>
                        <SUBJECT> System safeguards.</SUBJECT>
                        <STARS/>
                        <P>(d) A swap data repository shall maintain a business continuity-disaster recovery plan and business continuity-disaster recovery resources, emergency procedures, and backup facilities sufficient to enable timely recovery and resumption of its operations and resumption of its ongoing fulfillment of its duties and obligations as a swap data repository following any disruption of its operations. Such duties and obligations include, without limitation, the duties set forth in §§ 49.10 to 49.18, § 49.23, and the core principles set forth in §§ 49.19 to 49.21 and 49.25 to 49.27, and maintenance of a comprehensive audit trail. The swap data repository's business continuity-disaster recovery plan and resources generally should enable resumption of the swap data repository's operations and resumption of ongoing fulfillment of the swap data repository's duties and obligation during the next business day following the disruption. A swap data repository shall update its business continuity-disaster recovery plan and emergency procedures at a frequency determined by an appropriate risk analysis, but at a minimum no less frequently than annually.</P>
                        <STARS/>
                        <P>(i) As part of a swap data repository's obligation to produce books and records in accordance with § 1.31 of this chapter and § 49.12, a swap data repository shall provide to the Commission the following system safeguards-related books and records, promptly upon the request of any Commission representative:</P>
                        <P>* * *</P>
                        <P>(5) Nothing in paragraph (i) of this section shall be interpreted as reducing or limiting in any way a swap data repository's obligation to comply with § 1.31 of this chapter or with § 49.12.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>29. In § 49.25, revise paragraphs (a)(1) and (f)(3) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.25 </SECTNO>
                        <SUBJECT> Financial resources.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(1) A swap data repository shall maintain sufficient financial resources to perform its statutory and regulatory duties set forth in this chapter.</P>
                        <STARS/>
                        <P>(f) * * *</P>
                        <P>(3) The reports and any supporting documentation required by this section shall be filed not later than 40 calendar days after the end of the swap data repository's first three fiscal quarters, and not later than 90 calendar days after the end of the swap data repository's fourth fiscal quarter, or at such later time as the Commission may permit, in its discretion, upon request by the swap data repository.</P>
                    </SECTION>
                    <AMDPAR>30. In § 49.26,</AMDPAR>
                    <AMDPAR>a. Revise the introductory text; and</AMDPAR>
                    <AMDPAR>b. Add paragraph (j).</AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 49.26 </SECTNO>
                        <SUBJECT> Disclosure requirements of swap data repositories.</SUBJECT>
                        <P>
                            Before accepting any SDR data from a swap execution facility, designated contract market, or reporting counterparty; or upon a swap execution facility's, designated contract market's, or reporting counterparty's request; a swap data repository shall furnish to the swap execution facility, designated contract market, or reporting counterparty a disclosure document that 
                            <PRTPAGE P="21107"/>
                            contains the following written information, which shall reasonably enable the swap execution facility, designated contract market, or reporting counterparty to identify and evaluate accurately the risks and costs associated with using the services of the swap data repository:
                        </P>
                        <STARS/>
                        <P>(j) The swap data repository's policies and procedures regarding the reporting of SDR data to the swap data repository, including the swap data repository's SDR data validation procedures, swap data verification procedures, and procedures for correcting SDR data errors and omissions.</P>
                    </SECTION>
                    <AMDPAR>31. Add § 49.28 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.28 </SECTNO>
                        <SUBJECT> Operating hours of swap data repositories.</SUBJECT>
                        <P>(a) Except as otherwise provided in this paragraph (a), a swap data repository shall have systems in place to continuously accept and promptly record all SDR data reported to the swap data repository as required in this chapter and, as applicable, publicly disseminate all swap transaction and pricing data reported to the swap data repository as required in part 43 of this chapter.</P>
                        <P>(1) A swap data repository may establish normal closing hours to perform system maintenance during periods when, in the reasonable estimation of the swap data repository, the swap data repository typically receives the least amount of SDR data. A swap data repository shall provide reasonable advance notice of its normal closing hours to market participants and to the public.</P>
                        <P>(2) A swap data repository may declare, on an ad hoc basis, special closing hours to perform system maintenance that cannot wait until normal closing hours. A swap data repository shall schedule special closing hours during periods when, in the reasonable estimation of the swap data repository in the context of the circumstances prompting the special closing hours, the special closing hours will be the least disruptive to the swap data repository's SDR data reporting responsibilities. A swap data repository shall provide reasonable advance notice of its special closing hours to market participants and to the public whenever possible, and, if advance notice is not reasonably possible, shall provide notice of its special closing hours to market participants and to the public as soon as reasonably possible after declaring special closing hours.</P>
                        <P>(b) A swap data repository shall comply with the requirements under part 40 of this chapter in adopting or amending normal closing hours and special closing hours.</P>
                        <P>(c) During normal closing hours and special closing hours, a swap data repository shall have the capability to accept and hold in queue any and all SDR data reported to the swap data repository during the normal closing hours or special closing hours.</P>
                        <P>(1) Upon reopening after normal closing hours or special closing hours, a swap data repository shall promptly process all SDR data received during normal closing hours or special closing hours, as required pursuant to this chapter, and, pursuant to part 43 of this chapter, publicly disseminate all swap transaction and pricing data reported to the swap data repository that was held in queue during the normal closing hours or special closing hours.</P>
                        <P>(2) If at any time during normal closing hours or special closing hours a swap data repository is unable to receive and hold in queue any SDR data reported pursuant to this chapter, then the swap data repository shall immediately issue notice to all swap execution facilities, designated contract markets, reporting counterparties, and the public that it is unable to receive and hold in queue SDR data. Immediately upon reopening, the swap data repository shall issue notice to all swap execution facilities, designated contract markets, reporting counterparties, and the public that it has resumed normal operations. Any swap execution facility, designated contract market, or reporting counterparty that was obligated to report SDR data pursuant to this chapter to the swap data repository, but could not do so because of the swap data repository's inability to receive and hold in queue SDR data, shall report the SDR data to the swap data repository immediately after receiving such notice.</P>
                    </SECTION>
                    <AMDPAR>32. Add § 49.29 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.29 </SECTNO>
                        <SUBJECT> Information relating to swap data repository compliance.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Requests for information.</E>
                             Upon the Commission's request, a swap data repository shall file with the Commission information related to its business as a swap data repository and such information as the Commission determines to be necessary or appropriate for the Commission to perform the duties of the Commission under the Act and regulations thereunder. The swap data repository shall file the information requested in the form and manner and within the time period the Commission specifies in the request.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Demonstration of compliance.</E>
                             Upon the Commission's request, a swap data repository shall file with the Commission a written demonstration, containing supporting data, information, and documents, that it is in compliance with its obligations under the Act and the Commission's regulations thereunder, as the Commission specifies in the request. The swap data repository shall file the written demonstration in the form and manner and within the time period the Commission specifies in the request.
                        </P>
                    </SECTION>
                    <AMDPAR>33. Add § 49.30 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.30 </SECTNO>
                        <SUBJECT> Form and manner of reporting and submitting information to the Commission.</SUBJECT>
                        <P>Unless otherwise instructed by the Commission, a swap data repository shall submit SDR data reports and any other information required under this part to the Commission, within the time specified, using the format, coding structure, and electronic data transmission procedures approved in writing by the Commission.</P>
                    </SECTION>
                    <AMDPAR>34. Add § 49.31 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 49.31 </SECTNO>
                        <SUBJECT> Delegation of authority to the Director of the Division of Market Oversight relating to certain part 49 matters.</SUBJECT>
                        <P>(a) The Commission hereby delegates, until such time as the Commission orders otherwise, the following functions to the Director of the Division of Market Oversight and to such members of the Commission staff acting under his or her direction as he or she may designate from time to time:</P>
                        <P>(1) All functions reserved to the Commission in § 49.5.</P>
                        <P>(2) All functions reserved to the Commission in § 49.9.</P>
                        <P>(3) All functions reserved to the Commission in § 49.10.</P>
                        <P>(4) All functions reserved to the Commission in § 49.12.</P>
                        <P>(5) All functions reserved to the Commission in § 49.13.</P>
                        <P>(6) All functions reserved to the Commission in § 49.16.</P>
                        <P>(7) All functions reserved to the Commission in § 49.17.</P>
                        <P>(8) All functions reserved to the Commission in § 49.18.</P>
                        <P>(9) All functions reserved to the Commission in § 49.22.</P>
                        <P>(10) All functions reserved to the Commission in § 49.23.</P>
                        <P>(11) All functions reserved to the Commission in § 49.24.</P>
                        <P>(12) All functions reserved to the Commission in § 49.25.</P>
                        <P>(13) All functions reserved to the Commission in § 49.29.</P>
                        <P>(14) All functions reserved to the Commission in § 49.30.</P>
                        <P>
                            (b) The Director of the Division of Market Oversight may submit to the Commission for its consideration any 
                            <PRTPAGE P="21108"/>
                            matter that has been delegated under paragraph (a) of this section.
                        </P>
                        <P>(c) Nothing in this section may prohibit the Commission, at its election, from exercising the authority delegated in this section.</P>
                    </SECTION>
                    <AMDPAR>35. Revise Appendix A to Part 49 to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Appendix A to Part 49—Form SDR</HD>
                    <EXTRACT>
                        <HD SOURCE="HD1">
                            <E T="7462">COMMODITY FUTURES TRADING COMMISSION</E>
                        </HD>
                        <HD SOURCE="HD1">FORM SDR</HD>
                        <HD SOURCE="HD3">SWAP DATA REPOSITORY APPLICATION OR AMENDMENT TO APPLICATION FOR REGISTRATION</HD>
                        <HD SOURCE="HD1">
                            <E T="7462">REGISTRATION INSTRUCTIONS</E>
                        </HD>
                        <FP>
                            <E T="7462">Intentional misstatements or omissions of material fact may constitute federal criminal violations (7 U.S.C. 13 and 18 U.S.C. 1001) or grounds for disqualification from registration.</E>
                        </FP>
                        <HD SOURCE="HD1">DEFINITIONS</HD>
                        <FP>Unless the context requires otherwise, all terms used in this Form SDR have the same meaning as in the Commodity Exchange Act, as amended (“Act”), and in the General Rules and Regulations of the Commodity Futures Trading Commission (“Commission”) thereunder (17 CFR chapter I).</FP>
                        <FP>For the purposes of this Form SDR, the term “Applicant” shall include any applicant for registration as a swap data repository or any applicant amending a pending application.</FP>
                        <HD SOURCE="HD1">GENERAL INSTRUCTIONS</HD>
                        <FP SOURCE="FP-2">1. This Form SDR, which includes instructions, a Cover Sheet, and required Exhibits (together “Form SDR”), is to be filed with the Commission by all Applicants, pursuant to section 21 of the Act and the Commission's regulations thereunder. Upon the filing of an application for registration in accordance with the instructions provided herein, the Commission will publish notice of the filing and afford interested persons an opportunity to submit written comments concerning such application. No application for registration shall be effective unless the Commission, by order, grants such registration.</FP>
                        <FP SOURCE="FP-2">2. Individuals' names, except the executing signature, shall be given in full (Last Name, First Name, Middle Name).</FP>
                        <FP SOURCE="FP-2">
                            3. Signatures on all copies of the Form SDR filed with the Commission can be executed electronically. If this Form SDR is filed by a corporation, it shall be signed in the name of the corporation by a principal officer duly authorized; if filed by a limited liability company, it shall be signed in the name of the limited liability company by a manager or member duly authorized to sign on the limited liability company's behalf; if filed by a partnership, it shall be signed in the name of the partnership by a general partner duly authorized; if filed by an unincorporated organization or association that is not a partnership, it shall be signed in the name of such organization or association by the managing agent, 
                            <E T="03">i.e.,</E>
                             a duly authorized person who directs manages or who participates in the directing or managing of its affairs.
                        </FP>
                        <FP SOURCE="FP-2">4. If this Form SDR is being filed as an application for registration, all applicable items must be answered in full. If any item is inapplicable, indicate by “none,” “not applicable,” or “N/A,” as appropriate.</FP>
                        <FP SOURCE="FP-2">5. Under section 21 of the Act and the Commission's regulations thereunder, the Commission is authorized to solicit the information required to be supplied by this Form SDR from any Applicant seeking registration as a swap data repository. Disclosure by the Applicant of the information specified in this Form SDR is mandatory prior to the start of the processing of an application for registration as a swap data repository. The information provided in this Form SDR will be used for the principal purpose of determining whether the Commission should grant or deny registration to an Applicant. The Commission may determine that additional information is required from an Applicant in order to process its application. A Form SDR that is not prepared and executed in compliance with applicable requirements and instructions may be returned as not acceptable for filing. Acceptance of this Form SDR, however, shall not constitute a finding that the Form SDR has been filed as required or that the information submitted is true, current, or complete.</FP>
                        <FP SOURCE="FP-2">6. Except in cases where confidential treatment is requested by the Applicant and granted by the Commission pursuant to the Freedom of Information Act and Commission Regulation § 145.9, information supplied on this Form SDR will be included in the public files of the Commission and will be available for inspection by any interested person. The Applicant must identify with particularity the information in these exhibits that will be subject to a request for confidential treatment and supporting documentation for such request pursuant to Commission Regulations § 40.8 and § 145.9.</FP>
                        <HD SOURCE="HD1">APPLICATION AMENDMENTS</HD>
                        <FP SOURCE="FP-2">1. An Applicant amending a pending application for registration as a swap data repository shall file an amended Form SDR electronically with the Secretary of the Commission in the manner specified by the Commission.</FP>
                        <FP SOURCE="FP-2">2. When filing this Form SDR for purposes of amending a pending application, an Applicant must re-file the entire Cover Sheet, amended if necessary, include an executing signature, and attach thereto revised Exhibits or other materials marked to show any amendments. The submission of an amendment to a pending application represents that all unamended items and Exhibits remain true, current, and complete as previously filed.</FP>
                        <HD SOURCE="HD1">WHERE TO FILE</HD>
                        <FP>This Form SDR shall be filed electronically with the Secretary of the Commission in the manner specified by the Commission.</FP>
                        <BILCOD>BILLING CODE 6351-01-P</BILCOD>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="21109"/>
                            <GID>EP13MY19.002</GID>
                        </GPH>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="21110"/>
                            <GID>EP13MY19.003</GID>
                        </GPH>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="21111"/>
                            <GID>EP13MY19.004</GID>
                        </GPH>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="21112"/>
                            <GID>EP13MY19.005</GID>
                        </GPH>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="21113"/>
                            <GID>EP13MY19.006</GID>
                        </GPH>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="21114"/>
                            <GID>EP13MY19.007</GID>
                        </GPH>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="21115"/>
                            <GID>EP13MY19.008</GID>
                        </GPH>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="21116"/>
                            <GID>EP13MY19.009</GID>
                        </GPH>
                        <GPH SPAN="3" DEEP="184">
                            <PRTPAGE P="21117"/>
                            <GID>EP13MY19.010</GID>
                        </GPH>
                        <BILCOD>BILLING CODE 6351-01-C</BILCOD>
                        <SIG>
                            <DATED>Issued in Washington, DC, on April 25, 2019, by the Commission.</DATED>
                            <NAME>Robert Sidman,</NAME>
                            <TITLE>Deputy Secretary of the Commission.</TITLE>
                        </SIG>
                        <NOTE>
                            <HD SOURCE="HED">Note: </HD>
                            <P>The following appendices will not appear in the Code of Federal Regulations.</P>
                        </NOTE>
                        <HD SOURCE="HD1">Appendices to Proposed Amendments to the Commission's Regulations Relating to Certain Swap Data Repository and Data Reporting Requirements</HD>
                        <HD SOURCE="HD1">Appendix 1—Commission Voting Summary</HD>
                        <P>On this matter, Chairman Giancarlo and Commissioners Quintenz and Berkovitz voted in the affirmative. Commissioners Behnam and Stump voted to concur. No Commissioner voted in the negative.</P>
                    </EXTRACT>
                    <HD SOURCE="HD1">Appendix 2—Statement of Chairman J. Christopher Giancarlo</HD>
                    <EXTRACT>
                        <P>A critical component of the 2008 financial crisis was the inability of regulators to assess and quantify the counterparty credit risk of large banks and swaps dealers. To address this shortcoming, the Dodd-Frank Act gave the CFTC broad responsibility to enhance regulatory transparency and price discovery for market participants through trade reporting to swap data repositories (SDRs).</P>
                        <P>In 2011 and 2012, the CFTC adopted rules for swap data reporting, recordkeeping and SDRs. Unfortunately, these initial rules lacked technological detail and specification. Under my direction in 2017, CFTC staff began the process of assessing the effectiveness of the swap reporting rules in Parts 43, 45, and 49 of the CFTC's regulations. The 2017 Roadmap to Achieve High Quality Swaps Data (Roadmap) outlined a series of steps to improve data reporting requirements. The CFTC received a wide range of feedback on the Roadmap, via written comments and discussions with SDRs and market participants.</P>
                        <P>I am pleased to see the first part of the Roadmap, the proposed changes to Part 49, issued today. These proposed changes update the requirements for SDRs and swap counterparties to verify the accuracy and completeness of swap data reported to SDRs. Completion of these and the other changes proposed by the Roadmap will result in more complete, more accurate, and higher-quality data available to the CFTC and to the public; streamline data reporting; and help the CFTC perform its regulatory responsibilities. The time has come to revisit this important post-crisis reform and ensure the CFTC is fulfilling its commitments.</P>
                    </EXTRACT>
                    <HD SOURCE="HD1">Appendix 3—Statement of Concrrence of Commissioner Rostin Behnam</HD>
                    <EXTRACT>
                        <P>
                            I respectfully concur with the Commodity Futures Trading Commission's (the “Commission” or “CFTC”) approval of its proposed rule regarding amendments to the Commission's Regulations Relating to Certain Swap Data Repository and Swap Data Reporting Requirements (the “Proposal”). In 2011, the Commission adopted part 49 of the Commission's Regulations 
                            <SU>1</SU>
                            <FTREF/>
                             to implement the requirements of section 21 of the Commodity Exchange Act (the “Act” or “CEA”).
                            <SU>2</SU>
                            <FTREF/>
                             Section 21 describes the registration regime for and operation of swap data repositories (“SDRs”) by setting out applicable registration rules, data standards, duties, core principles, and requirements regarding confidentiality and chief compliance officers as envisioned by Congress in the Dodd-Frank Act to implement the key trade reporting provisions laid out at the 2009 G20 Pittsburgh Summit.
                            <SU>3</SU>
                            <FTREF/>
                             Similarly, part 49 builds out a regulatory framework aimed at ensuring the legal and operational stability and soundness of SDRs in support of post-trade transparency in the swaps market. The Proposal aims to improve upon the quality, accuracy, and completeness of swap data reported to the Commission via SDRs and generally follows a plan laid out in the Commission's 2017 Roadmap to Achieve High Quality Swap Data.
                            <SU>4</SU>
                            <FTREF/>
                             This Proposal purports to be the first step in following that Roadmap. While true, I prefer to view this as a part of the Commission's ongoing duties to regularly review its Regulations to increase efficiencies and avoid unintended consequences, and to be certain that our SDR rules further the goals of increasing transparency and identifying risk.
                        </P>
                        <FTNT>
                            <P>
                                <SU>1</SU>
                                 Swap Data Repositories: Registration Standards, Duties and Core Principles, 76 FR 54538 (Sept. 1, 2011).
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>2</SU>
                                 7 U.S.C. 24a.
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>3</SU>
                                 
                                <E T="03">Id.</E>
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>4</SU>
                                 Roadmap to Achieve High Quality Swap Data, 
                                <E T="03">available at http://www.cftc.gov/idc/groups/public/@newsroom/documents/file/dmo_swapdataplan071017.pdf.</E>
                            </P>
                        </FTNT>
                        <P>
                            As I have stated several times during my tenure as a Commissioner, as we engage in strategic regulatory decisions, our policy goals from 2010 remain unchanged. As we endeavor to provide surgical flexibility and a more principles-based approach, I will continue to oppose any roll backs of Dodd-Frank initiatives.
                            <SU>5</SU>
                            <FTREF/>
                             While I do not believe that today's Proposal would be considered a rollback per se, I would like to call attention to a section of the Proposal where we deviate from the language of section 21 regarding the role of the chief compliance officer (“CCO”) at an SDR.
                        </P>
                        <FTNT>
                            <P>
                                <SU>5</SU>
                                 Rostin Behnam, Commissioner, U.S. Comm. Fut. Trading Comm'n, Remarks of Rostin Behnam before FIA/SIFMA Asset Management Group, Asset Management Derivatives Forum 2018, Dana Point, California (Feb. 8, 2018), 
                                <E T="03">https://www.cftc.gov/PressRoom/SpeechesTestimony/opabehnam2.</E>
                            </P>
                        </FTNT>
                        <P>Section 21(e)(2)(C) affirmatively requires an SDR's CCO, in consultation with the board of directors or similar body, to “resolve any conflicts of interest that may arise.” The Commission's current part 49 rules mirror the language of the CEA exactly. Regulation 49.22(d)(2) affirmatively requires an SDR's CCO to “resolve any conflicts of interest that may arise,” using precisely the same language as the Act.</P>
                        <P>
                            However, today's Proposal would amend 49.22(d)(2) in a way that deviates from the plain language of the statute. While the statute requires that CCOs actually resolve any conflicts of interest, today's Proposal would simply require a CCO to take “reasonable steps” to resolve any conflict of interest. In addition, the Proposal would only apply to “material” conflicts of interest. Neither this new reasonableness standard nor this new materiality standard appear in the language of the statute. My concern is that adding these new standards may deviate from Congressional intent. This potentially dilutes the CCO's obligation to address conflicts of interest, but perhaps more importantly, it dilutes the CCO's ability to do 
                            <PRTPAGE P="21118"/>
                            so. Under the language of the Act and the current Regulation, a CCO can point to their statutory obligation in working to resolve conflicts of interest. Imposing a new reasonableness standard may have the real world impact of making it more difficult for a CCO to actually resolve conflicts of interest.
                        </P>
                        <P>
                            I note that the same statutory language appears elsewhere in the Act regarding CCO resolution of conflicts of interest at other types of Commission registrants, and the Commission has issued a final rule implementing the same new reasonableness and materiality standards regarding CCOs of futures commission merchants, swap dealers and major swap participants.
                            <SU>6</SU>
                            <FTREF/>
                             The Commission also has recently proposed adding these new standards for CCOs of swap execution facilities.
                            <SU>7</SU>
                            <FTREF/>
                             However, in contrast, this week the Commission is issuing amendments to the Part 39 regulations for Derivatives Clearing Organizations (“DCO”) (the “Part 39 Proposal”). Current regulation 39.10(c)(2)(ii) requires a DCO's CCO to resolve conflicts of interest. Regulation 39.10(c)(2)(ii) exactly follows the language of Section 5b(i)(2)(C). While the Part 39 Proposal makes amendments to 39.10, the Commission does not alter the CCO's current duty to resolve conflicts of interest. In other words, for DCOs the Commission is choosing to maintain the statutory language. I believe that this may be the more appropriate approach for CCOs generally.
                        </P>
                        <FTNT>
                            <P>
                                <SU>6</SU>
                                 Chief Compliance Officer Duties and Annual Report Requirements for Futures Commission Merchants, Swap Dealers, and Major Swap Participants, 83 FR 43510 (Aug. 27, 2018).
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>7</SU>
                                 Swap Execution Facilities and Trade Execution Requirement, 83 FR 61946 (Nov. 30, 2018).
                            </P>
                        </FTNT>
                        <P>The Commission has, of late, begun a practice of re-interpreting statutory provisions with a somewhat flippant regard for their underlying purpose and rationales in order to lessen the burdens that are rarely substantiated by anything more than a call for change. While it is not out of the ordinary for an independent agency to reexamine whether its regulatory approach remains fit for purpose, I believe that we should be mindful that our role is not to bend too easily to unsupported claims of burden or complexity. This is particularly true when the re-interpretation seems to be at odds with the express language of the statute itself. I look forward to reading the comments on this CCO issue. I am particularly interested to learn whether various stakeholders believe that the statute itself is diluted by the addition of the reasonableness and materiality standards to CCO obligations in this and other rulemakings.</P>
                    </EXTRACT>
                    <HD SOURCE="HD1">Appendix 4—Statement of Concurrence of Commissioner Dawn D. Stump</HD>
                    <EXTRACT>
                        <P>The Commission is publishing for public comment “Proposed Amendments to the Commission's Regulations Relating to Certain Swap Data Repository and Swap Data Reporting Requirements” (Proposal). Accurate swap data reporting is vital to our ability to make appropriate policy choices. I very much look forward to receiving feedback from all parties impacted by this Proposal to assure that the Commission has robust and accurate data, which is a lynchpin of future Commission decision-making.</P>
                        <P>However, a Latin proverb reads: Qui tacet consentire videtur, ubi loqui debuit ac potuit (he who is silent, when he ought to have spoken and was able to, is taken to agree). While I share the Commission's desire for accurate swap data, I do not agree with all the policy and procedural choices in this Proposal. I question certain of the underlying assumptions driving these policy changes, and the promulgation of this rulemaking in isolation and without corresponding changes to other swap data reporting rules. I am uncomfortable with the lack of details and nebulous description of certain obligations in many parts of the Proposal, which I believe will make it difficult for the public to comment in an informed fashion. And I disagree with imposing immense additional burdens on swap data repositories (SDRs) and all types of reporting counterparties (RCPs), particularly without commensurate streamlining of regulatory obligations in the rest of the Commission's swap data reporting rule set.</P>
                        <P>
                            Because I share the Commission's ultimate goal of accurate swaps data, I support the Proposal going out for comment, with the caveat that the other aspects of the swaps data “Roadmap” 
                            <SU>1</SU>
                            <FTREF/>
                             are published in quick succession. I look forward to feedback from all interested parties as to how that goal can best be achieved in light of my concerns about the Proposal discussed below and other options that may be at the Commission's disposal to enhance data accuracy while appropriately balancing costs and benefits.
                        </P>
                        <FTNT>
                            <P>
                                <SU>1</SU>
                                 
                                <E T="03">See</E>
                                 Roadmap to Achieve High Quality Swaps Data (DMO July 10, 2017), 
                                <E T="03">available at https://www.cftc.gov/sites/default/files/idc/groups/public/@newsroom/documents/file/dmo_swapdataplan071017.pdf, published with</E>
                                 CFTC Letter 17-33, Division of Market Oversight Announces Review of Swap Reporting Rules in Parts 43, 45, and 49 of Commission Regulations (DMO July 10, 2017), 
                                <E T="03">available at https://www.cftc.gov/sites/default/files/idc/groups/public/@lrlettergeneral/documents/letter/17-33.pdf.</E>
                            </P>
                        </FTNT>
                        <HD SOURCE="HD2">I. Verification: Solution in Search of a Problem?</HD>
                        <P>
                            This Proposal is predicated upon a view that new verification procedures are needed because the swap data currently being reported to SDRs is substantially wrong and inaccurate. Yet, the Commission has recently proffered positive reviews of the role of SDR data in enhancing its understanding of swaps markets, citing the “more complete information now available regarding certain portions of the swap market, [and] the data analytical capabilities developed since the [swap dealer] regulations were adopted” 
                            <SU>2</SU>
                            <FTREF/>
                             as supporting its policy decision making. Specifically, the Commission cited analysis based upon a year of SDR data sourced from data reported to the registered SDRs in its recent rulemaking concerning the 
                            <E T="03">de minimis</E>
                             exception to the swap dealer definition relating to insured depository institutions (IDIs).
                            <SU>3</SU>
                            <FTREF/>
                             Given that the Commission has not voiced concern about widespread discrepancies or inaccuracies in swaps data reported to SDRs in relying upon that data in our rulemakings, I am not convinced that it is necessary to add new layers of complexity to swaps data reporting and create new burdens on market participants via the steps outlined in the Proposal.
                        </P>
                        <FTNT>
                            <P>
                                <SU>2</SU>
                                 De Minimis Exception to the Swap Dealer Definition—Swaps Entered Into by Insured Depository Institutions in Connection With Loans to Customers, 81 FR 12450, 12452 (April 1, 2019) (IDI 
                                <E T="03">De Minimis</E>
                                 Rulemaking).
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>3</SU>
                                 
                                <E T="03">Id.</E>
                                 at 12454 and n.59 (“The Commission believes that end-users would primarily benefit from the IDI De Minimis Provision by entering into [interest rate swaps, or `IRS'], [foreign exchange, or `FX'] swaps, and [non-financial commodity, or `NFC'] swaps with IDIs to hedge loan-related risks. SDR data indicates that IDIs that have between $1 billion and $50 billion in [aggregate gross notional amount, or `AGNA'] of swaps activity primarily enter into IRS, FX swaps, and NFC swaps, as measured by AGNA and transaction count.
                            </P>
                        </FTNT>
                        <P>
                            Taken in isolation, asking RCPs to verify the accuracy of data reported to SDRs is appealing. But how does the Commission know that a substantial portion of that data is actually incorrect? The Proposal attempts to depict a data accuracy problem by referencing that it is not uncommon for discrepancies to be found in SDR data. However, from the universe of reported swap data that contains millions of swap transactions and exponentially more messages sent to SDRs over the course of the last five years, the Proposal mentions only two examples of errors: “In the processing of swap data to generate the CFTC's Weekly Swaps Report, for example, there are instances when the notional amount differs between the Commission's open swaps information and the swap data reported for the same swap. Other common examples of discrepancies include incorrect references to an underlying currency, such as a notional value incorrectly linked to U.S. dollars instead of Japanese Yen.” 
                            <SU>4</SU>
                            <FTREF/>
                             I would expect a much more extensive and egregious list of systemic, recurring errors in reported swaps data to warrant the expansive new obligations contained in the Proposal.
                        </P>
                        <FTNT>
                            <P>
                                <SU>4</SU>
                                 Proposal, text accompanying n.239.
                            </P>
                        </FTNT>
                        <P>
                            The Proposal strains to quantify the number of inaccuracies in reported SDR data by opining that, “[b]ased on swap data available to the Commission and discussions with the SDRs, the Commission estimates that an SDR would perform an average of approximately 2,652,000 data corrections per year.” 
                            <SU>5</SU>
                            <FTREF/>
                             The Proposal does not explain exactly how this figure was derived, identify the interaction between SDRs and RCPs referenced in its corrections estimate, indicate whether the “correction” refers to incomplete or inaccurate data,
                            <SU>6</SU>
                            <FTREF/>
                             or provide critical context as to the percentage of messages that this number represents. Indeed, it is impossible to know for certain that an RCP was intending to correct erroneously reported data based on the data schema utilized by SDRs to address changes in swaps data—which include actions such as “snapshot,” “amendment,” and 
                            <PRTPAGE P="21119"/>
                            “modify,” 
                            <SU>7</SU>
                            <FTREF/>
                             but may not actually include a category of “correction” messages.
                        </P>
                        <FTNT>
                            <P>
                                <SU>5</SU>
                                 
                                <E T="03">Id.,</E>
                                 at section VII.B.3.v.
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>6</SU>
                                 
                                <E T="03">Incomplete</E>
                                 data is not the same things as 
                                <E T="03">inaccurate</E>
                                 data. Thus, “corrections” of incomplete data would not be relevant to the verification with respect to inaccurate data that is the subject of this Proposal.
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>7</SU>
                                 DTCC SDR templates, for instance, include the following message and action types. The modify action type allows for the valid modification or correction to an existing trade that has previously been reported by the submitting party. However, firms could reflect a correction using other methods. The snapshot message allows participants to report the current state of the swap in their portfolio as a “point-in-time” view of the position. The reported position should reflect all post-trade events and non-position forming amendments that the submitter may wish to reflect on their trade record. The amendment transaction type could be utilized as an indication of a confirmable amendment, via a negotiated agreement, to a previously confirmed and reported trade. As a result, it would be difficult to conclude with any certainty the actual number of corrections without a critical review of contrasting terms related to a particular trade on each type of action, message, or transaction type submission.
                            </P>
                        </FTNT>
                        <P>
                            While the Proposal posits the annual number of corrections across all SDRs to be about 8 million “corrections” (3 provisionally registered SDRs * 2,652,000 annual data corrections per SDR), it lacks the total number of data submissions that are received by the SDRs. The Paperwork Reduction Act portion of the Proposal does provide one potentially related data point, as it includes an estimate of 462,981,508 total annual responses across all SDRs for the relevant information collection.
                            <SU>8</SU>
                            <FTREF/>
                             Without the benefit of further clarity, the corrections could apply to the entire universe of the collections associated with the Proposal. If the figures are roughly rounded for the sake of simplicity, and it is stipulated for the sake of argument that all the corrections cited by the Proposal reveal data inaccuracies, then does this suggest that only approximately 2% (400 million responses/8 million corrections) of all messages might be inaccurate? In my opinion, the burdens that this Proposal would impose on SDRs and RCPs (including commercial end users) may be difficult to justify if the problem the Commission is attempting to rectify may equate to 2% of all messages delivered to SDRs.
                        </P>
                        <FTNT>
                            <P>
                                <SU>8</SU>
                                 Proposal at section VII.B.3.xi.
                            </P>
                        </FTNT>
                        <P>
                            I share the view that has been stated by some of my colleagues recently that the Commission should strive to make data-driven policy determinations and should avoid relying on assumptions or anecdotes when engaged in rulemaking activity.
                            <SU>9</SU>
                            <FTREF/>
                             Yet, the same is true when it comes to imposing costs and burdens on market participants that are already heavily encumbered by a broad swath of regulatory obligations that continue to shift and expand. Our recent rulemakings have referenced data driven policy making, learning from experience with Dodd-Frank implementation, and demonstrating supporting evidence for regulatory change, but the verification provisions of this Proposal deviate from that approach. The Commission should delay this rulemaking until the other aspects of the Roadmap critical to improving swaps data reporting and lessening unnecessary regulatory burdens were ready to be proposed. But, short of that, I welcome public comment and data evaluating the breadth and depth of inaccuracies in SDR data.
                            <SU>10</SU>
                            <FTREF/>
                             Such information would help to determine how much reported SDR data is actually incorrect before the Commission requires SDRs and RCPs to build additional systems and undertake significant new compliance burdens and obligations to address an accuracy problem that, at this point, has not been proved. I look forward to comments and data that demonstrate the actual need for the proposed changes.
                        </P>
                        <FTNT>
                            <P>
                                <SU>9</SU>
                                 
                                <E T="03">See, e.g.,</E>
                                 IDI 
                                <E T="03">De Minimis</E>
                                 Rulemaking at 12467 (Statement of Chairman J. Christopher Giancarlo) (“As I have said many times before, I believe that CFTC policy is best when it is driven by data and not assumptions.”).
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>10</SU>
                                 The cost-benefit consideration in the Proposal loosely references and mischaracterizes information contained in three public studies that allude to challenges in SDR data. Unfortunately, these studies are from 2015 or earlier and are based upon data from the initial roll-out of SDR reporting. These studies address incomplete rather than inaccurate data and do not belong in this Proposal that focuses on verification of data. 
                                <E T="03">See</E>
                                 fn. 6, 
                                <E T="03">supra.</E>
                                 The Roadmap explained that validations should be utilized to reject swap data reports with missing data fields, and these issues would be better served by a holistic implementation of the Roadmap and do not require the onerous verification aspects of the Proposal. Furthermore, some of these identified issues also would be resolved by the technical specification detailed in the Roadmap and, again, if proposed in unison, would provide RCPs with clear definition, form and manner, and allowable values. The reference to the third study also fails to mention that the two soybean swaps referred to were removed from a universe of 39,622 agricultural swaps.
                            </P>
                        </FTNT>
                        <HD SOURCE="HD1">II. Insufficient Level of Detail for Appropriate Public Comment and Cost-Benefit Consideration</HD>
                        <P>
                            The Administrative Procedure Act (APA) requires that, in issuing its rules, the Commission “examine the relevant data and articulate a satisfactory explanation for its action including a rational connection between the facts found and the choices made.” 
                            <SU>11</SU>
                            <FTREF/>
                             Section 15(a) of the Commodity Exchange Act (CEA) further requires that in doing so, the Commission must consider the costs and benefits of its proposed action.
                            <SU>12</SU>
                            <FTREF/>
                             A notice of proposed rulemaking affords the Commission the opportunity to gather information and build a record that will provide the reasons for the conclusions that it ultimately draws when final rules are issued. If the Commission fails to properly exercise this responsibility, we risk having our rules set aside as arbitrary and capricious agency action.
                            <SU>13</SU>
                            <FTREF/>
                        </P>
                        <FTNT>
                            <P>
                                <SU>11</SU>
                                 
                                <E T="03">Motor Vehicle Mfrs. Ass'n of U.S., Inc.</E>
                                 v. 
                                <E T="03">State Farm Mut. Auto Ins. Co.,</E>
                                 463 U.S. 29, 43 (1983).
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>12</SU>
                                 7 U.S.C. 19(a).
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>13</SU>
                                 
                                <E T="03">See</E>
                                 APA, 7 U.S.C. 706(2)(A).
                            </P>
                        </FTNT>
                        <P>While I support the purposes and intent underlying the Proposal, I am concerned that some of the proposed rules are too vague to enable the public to provide the Commission with information necessary to adopt a sound final rule set. For RCPs, the Proposal informs them of their general obligations, but leaves a tremendous amount of the details to future action by the Commission (often delegated to staff) and the SDRs to dictate the operational work flows that RCPs will have to adhere to in order to comply with the Commission's rules. RCPs reading the proposed rules still would not know what changes are being proposed in what they have to report, when they must report by, and how they are to deliver that information to SDRs. The proposed rules are often amorphous, lacking specificity as to the actual processes and procedures to be imposed, with RCPs left to comment without really knowing what much of this would actually require of them in the future.</P>
                        <P>The same is true for SDRs. For example, proposed § 49.9 covering open swaps reports to be provided to the Commission is quite opaque, and provides no detail as to any potential future instructions from the Commission that “may include, but are not limited to, the method, timing, and frequency of transmission as well as the format of the swap data to be transmitted.” Similarly, proposed § 49.17(c)(1) would require an SDR to transmit all swap data requested by the Commission, but provides that the SDR will receive instructions that may include, but are not limited to, the method, timing, and frequency of transmission, and the format and scope of the SDR data to be transmitted, at a later time.</P>
                        <P>How can RCPs and SDRs prepare for, budget, build, test, and implement systems to comply with these requirements without ample information ahead of time as to what these requirements entail? Indeed, it is not clear to me how RCPs and SDRs can even meaningfully comment on either the merits or the costs and benefits of the proposed rules when these critical elements of the requirements are left for future determination.</P>
                        <P>
                            But the proposed rule that troubles me most in this regard is proposed § 49.13, which addresses an SDR's duty to monitor, screen, and analyze data upon the request of the Commission. The Proposal explains that in its original consideration of current Regulation 49.13,
                            <SU>14</SU>
                            <FTREF/>
                             the Commission received comments that the rule does not sufficiently describe the specific tasks that SDRs are expected to perform. The Commission decided to later establish specific monitoring, screening, and analyzing duties when its knowledge was more fully developed, and that is where we find ourselves presently. Yet, despite the Commission's experience with swaps data over the last five plus years, this Proposal still fails to delineate specific duties that would enable an SDR to provide appropriate budget, technological development, and staff resources to assure an ability to comply with the demands that may be made upon it.
                        </P>
                        <FTNT>
                            <P>
                                <SU>14</SU>
                                 17 CFR 49.13.
                            </P>
                        </FTNT>
                        <P>
                            Proposed § 49.13(a)(1) requires SDRs to be prepared to comply with Commission requests for monitoring, screening, and analyzing of data. Several of the tasks alluded to in the proposal rule could impose significant, albeit wholly undefined, obligations on SDRs. For example, proposed § 49.13(a)(1)(iv) contemplates assessments of risk, which is not particularly an SDR function and which can be a very complicated exercise that is defined and calculated differently by different market participants. Proposed § 49.13(a)(1)(viii) would appear to render SDRs an arm of the Commission's enforcement program, as it would require them to provide information 
                            <PRTPAGE P="21120"/>
                            about compliance with Commission regulations without clarifying how SDRs could do so, and despite the fact that SDRs are not self-regulatory organizations.
                        </P>
                        <P>Proposed § 49.13(b), in turn, requires SDRs to “establish and at all times maintain sufficient information technology, staff, and other resources to fulfill” these Commission requests. Yet, proposed § 49.13(a)(2) provides that the content, scope, and frequency of all monitoring, screening, and analyzing requests shall be at the discretion of the Commission (to be exercised by staff pursuant to delegated authority); further, in addition to the 11 types of potential Commission requests identified in the proposal, SDRs also would have to be prepared to comply with other, unspecified, types of requests for monitoring, screening, and analyzing as well. How can an SDR be expected to efficiently allocate capital and meet the standards of proposed § 49.13(b) with respect to information technology, staff, and “other” (undefined) resources when it does not know what the actual requirements will be, when it will be expected to deliver, at what frequency, and the exact form and manner of the deliverable?</P>
                        <P>Finally, proposed § 49.30 would mandate that “a swap data repository shall submit SDR data reports and any other information required under this part to the Commission, within the time specified, using the format, coding structure, and electronic data transmission procedures approved in writing by the Commission.” I cannot begin to fathom the uncomfortable (and unenviable) position of an SDR under rules whereby the Commission can ask for almost anything under proposed § 49.13, and then demand its submission whenever and however it wishes under proposed § 49.30.</P>
                        <P>
                            The Proposal states, somewhat incredibly, that it “expects specifying these topic areas [in proposed § 49.13] would not impose substantial new fixed costs on SDRs. . .” 
                            <SU>15</SU>
                            <FTREF/>
                             It is wishful thinking to claim that the extensive list of undefined, open-ended tasks hypothesized in proposed § 49.13(a)(1) that SDRs must prepare to build and deliver will not represent a meaningful burden. Although it is not clear how SDRs could quantify the costs of compliance with such vague obligations, it is likely that the costs incurred by SDRs will be significant—and that their clients, including commercial end-users, ultimately will pay the price.
                        </P>
                        <FTNT>
                            <P>
                                <SU>15</SU>
                                 Proposal at section II.I.
                            </P>
                        </FTNT>
                        <P>I appreciate that it is not possible to foresee all future circumstances when proposing a rulemaking, and I recognize the need for flexibility in aspects of the Commission's day-to-day administration of the Dodd-Frank swap regulatory regime. Nevertheless, I am concerned that the Proposal fails to inform the public as to the full nature of the responsibilities that the Commission intends to impose upon RCPs and SDRs so that they can provide appropriate comment and feedback to drive the best final rule outcome possible. I wonder how the Commission can produce a complete cost-benefit consideration without specifying the actual scope and technical details of the requirements it is proposing to impose, particularly with respect to requests to SDRs to be made via proposed § 49.13. In sum, I fear that in proposing several rules where critical elements are left for future specification (often by staff), the Commission will not receive informed and meaningful public comments (including comments on costs and benefits) that are necessary to provide the foundation on which our rules ultimately must rest.</P>
                        <HD SOURCE="HD1">III. Suboptimal Policy Choices</HD>
                        <P>Certain elements of the Proposal rest on questionable policy choices that I wish to highlight in order to garner public input as part of the comment process.</P>
                        <P>
                            First, the Proposal would remove a longstanding market practice of trusted sources when it comes to verification of data accuracy without demonstrating why such a change is necessary, or appropriate. The Proposal states: “The Commission provided an exception to the requirement that SDRs `confirm with both counterparties to the swap the accuracy of the data that was submitted' in § 49.11(b)(1)(ii) for swap creation data and § 49.11(b)(2)(ii) for swap continuation data when swap data is received from a [swap execution facility, or `SEF'], [designated contract market, or `DCM'], derivatives clearing organization (`DCO'), or from a third-party service provider acting on behalf of the swap counterparty, under certain conditions.” 
                            <SU>16</SU>
                            <FTREF/>
                             The Proposal's departure from this policy means that SDRs would no longer be able to rely on an exception from the requirement to affirmatively confirm with both counterparties where (1) the SDR forms a reasonable belief that the data is accurate, (2) the reporting identifies that both counterparties agreed to the data submitted, and (3) the SDR provides both counterparties with a 48-hour correction window.
                        </P>
                        <FTNT>
                            <P>
                                <SU>16</SU>
                                 
                                <E T="03">Id.,</E>
                                 text accompanying n.70.
                            </P>
                        </FTNT>
                        <P>
                            The Proposal argues, without citing any evidence, that, “based on the Commission's experience with swap data submitted by SEFs, DCMs, DCOs, and third-party service providers since the rule was adopted, the Commission believes that such swap data has not been consistently complete and accurate in some instances, and the swap data accuracy is not sufficient to justify the exception to the requirement that SDRs confirm the reported swap data's accuracy with swap counterparties. The current requirements have had a negative effect on swap data accuracy and consistency, which has hampered the Commission's ability to carry out its regulatory responsibilities.” 
                            <SU>17</SU>
                            <FTREF/>
                             I do not believe that trading venues, which value execution certainty and must deliver accurate trade details to clients, or clearing organizations, which must have verified trade details available for risk management purposes, would report systematically or consistently inaccurate swaps data to SDRs, given their level of technological expertise and concern for reputational risk. At a minimum, I would not eliminate the existing exception absent evidence establishing that this is the case.
                        </P>
                        <FTNT>
                            <P>
                                <SU>17</SU>
                                 
                                <E T="03">Id.,</E>
                                 text immediately following n.73.
                            </P>
                        </FTNT>
                        <P>Second, the Proposal would mandate in proposed §§ 43.3(e) and 45.14(b) that corrections of errors and omissions be performed by SEFs, DCMs, and RCPs “regardless of the state of the swap that is the subject of the swap data.” The Proposal defines an “open swap” as “an executed swap transaction that has not reached maturity or the final contractual settlement date, and has not been exercised, closed out, or terminated.” Thus, the Proposal is requiring additional reporting for “dead” swaps without demonstrating a relevant use-case to warrant such a requirement.</P>
                        <P>It is more difficult for RCPs to correct dead/expired swaps that are no longer on their books and records. SDRs also face additional challenges and complexity in modifying swaps that are no longer what the Proposal defines as an “open swap.” The Proposal does not identify a Commission or public use-case that justifies the increased burden and challenge associated with correcting data on dead/expired swaps. The financial crisis that precipitated Dodd-Frank was not caused by, nor could it have been prevented by, regulatory oversight of dead swaps, but rather was the result of active risk. Again, absent an identified justification with evidentiary support, I do not support imposing additional regulatory burdens that force market participants to shift resources from the management of active risks to the reporting of dead swaps.</P>
                        <P>Third, I would prefer a more sensible approach to the duration of the recordkeeping requirements for SDRs. Proposed § 49.12(b)(2) would require SDR records—including SDR data, timestamps, and messages—to be readily accessible following final termination of the swap for five years, and then for a period of ten additional years in archival storage, which, of course, has an associated cost. Unless the Commission can clearly articulate the use-case and regulatory purpose that would justify requiring archival storage up to 15 years after the expiration of the swap, I believe the Commission should consider reducing the recordkeeping time frame for SDRs.</P>
                        <HD SOURCE="HD1">IV. Process Foul To Address Only One Aspect of the Complex Swap Data Reporting Puzzle</HD>
                        <P>I also am uncomfortable with the sequencing of this Proposal and the rush to publication on a stand-alone basis rather than as part of the contemplated overhaul of all the swaps data reporting rules.</P>
                        <P>
                            I expressed a similar view about the application of a holistic approach to interrelated regulations during last November's Open Meeting concerning SEFs when I noted that “I would prefer that the Commission be able to opine on a final SEF rule and a final rule on name give-up at the same time. Acting on all aspects impacting SEF trading contemporaneously would benefit all entities involved.” 
                            <SU>18</SU>
                            <FTREF/>
                             The same principles apply to swap data reporting, as both the public and the Commission would benefit from holistically addressing the 
                            <PRTPAGE P="21121"/>
                            entirety of the swap data reporting universe. Unfortunately, the Commission continues to propose regulations that are interrelated and that would govern the same activity in an inefficient, piecemeal manner.
                        </P>
                        <FTNT>
                            <P>
                                <SU>18</SU>
                                 
                                <E T="03">See</E>
                                 Opening Statement of Commissioner Dawn D. Stump before the CFTC Open Meeting, November 5, 2018, 
                                <E T="03">available at https://www.cftc.gov/PressRoom/SpeechesTestimony/stumpstatement110518.</E>
                            </P>
                        </FTNT>
                        <P>Swap data reporting is a complex web of interrelated processes and systems that must all work in sync in order to generate complete and accurate data in a timely and cost effective manner. Many tasks in reporting are sequential in nature, and it takes all participants in the reporting ecosystem to coordinate and cooperate with a complete understanding of all the swap data reporting regulations from the Commission. For example, SDRs have to scope out and create policies and procedures and build systems/templates for any new requirement. RCPs cannot adequately prepare for, much less build and test, systems on how to comply until they receive final feedback and instructions from the SDR. For this reason, implementing reporting changes—which invariably is quite costly to both SDRs and RCPs in terms of the expenditure of time, energy, and money—must be orchestrated and timed very carefully.</P>
                        <P>
                            SDRs and RCPs have previously expressed to the Commission the importance of being made aware of anticipated future modifications to reporting so that they can understand the expected end-game that the Commission has in mind.
                            <SU>19</SU>
                            <FTREF/>
                             Market participants also have commented on the need to understand the entire policy idea and all the associated pieces before committing time and energy to provide the Commission with meaningful comments and input.
                            <SU>20</SU>
                            <FTREF/>
                        </P>
                        <FTNT>
                            <P>
                                <SU>19</SU>
                                 In late 2015, CFTC staff issued a request for comment on draft technical specifications for certain prioritized swap data elements and sought input on 80 enumerated questions addressing 120 data elements for several swap data reporting topics. 
                                <E T="03">See</E>
                                 Draft Technical Specifications for Certain Swap Data Elements (December 22, 2015), 
                                <E T="03">available at https://www.cftc.gov/sites/default/files/idc/groups/public/@newsroom/documents/file/specificationsswapdata122215.pdf and https://www.cftc.gov/PressRoom/PressReleases/pr7298-15.</E>
                                 In responding to staff's request for comment, SIFMA stated that it “view[s] the Draft Technical Specifications as one component of a broader initiative to enhance swap data reporting” and that the “interrelationships among the Draft Technical Specifications and these other workstreams, as well as their shared dependencies on the same technology and human resources, necessitate a well-planned and sequenced approach to enhancing swap data reporting requirements. Prioritizing among the various enhancements under consideration will help to avoid inadvertent inconsistencies and associated potential for erroneous data and unnecessary infrastructure costs.” Letter from Kyle Brandon, SIFMA, at 2 (March 7, 2016), 
                                <E T="03">available at https://comments.cftc.gov/PublicComments/ViewComment.aspx?id=60702&amp;SearchText=.</E>
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>20</SU>
                                 SIFMA and ISDA jointly commented on the swaps data Roadmap and suggested that the Commission align the anticipated timeframes for swaps data reporting changes: “[G]iven the interconnection between SDR functions and the counterparties' reporting workflows, we believe that any proposed rule amendments and final rules associated with Tranche 1 and Tranche 2 should be issued at the same time.” Their letter then went on to comment: “Alternatively, should the Commission decide to publish the proposed rule amendments to the SDR rules first in Tranche 1, then we recommend that the public comment period for this release remain open for at least 90 days following publication of the proposed rule amendments to the reporting workflow rules in Tranche 2. This extended comment period would provide market participants with a comprehensive and holistic understanding of whether the two proposals achieve the desired policy outcomes and account for operational costs and possible additional builds to comply with a modified reporting regime.” Letter from Steven Kennedy, ISDA, and Kyle Brandon, SIFMA, at 3-4 (August 21, 2017) (footnote omitted), 
                                <E T="03">available at https://comments.cftc.gov/PublicComments/ViewComment.aspx?id=61288&amp;SearchText=.</E>
                            </P>
                        </FTNT>
                        <P>
                            I appreciate that the Proposal states that “[w]hen the Commission proposes the next two rulemakings, the Commission anticipates re-opening the comment period for this proposal to provide market participants with an opportunity to comment collectively on the three rulemakings together, because the proposals address interconnected issues.” 
                            <SU>21</SU>
                            <FTREF/>
                             But I do not see the benefit of proceeding in such an inefficient manner. Issuing the Proposal now does provide notice of the Commission's intentions with respect to one piece of the swaps data Roadmap, but no notice of what else from the Roadmap might come to pass. Such “partial notice” does not enable parties to evaluate, and comment upon, the full picture of their new compliance obligations, including their costs and burdens.
                            <SU>22</SU>
                            <FTREF/>
                             Under these circumstances, I would not be surprised if market participants simply waited for all of the reporting rules to be proposed before providing feedback to the Commission on the whole of what is being proposed.
                        </P>
                        <FTNT>
                            <P>
                                <SU>21</SU>
                                 Proposal, text immediately following n.23.
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>22</SU>
                                 The Commission's disjointed delivery of proposed changes to its swap data reporting rules also raises questions as to its consideration of relevant costs and benefits. Cost-benefit considerations, by their very nature, must evaluate the proposed changes in comparison to the status quo—including the present state of other relevant regulations. As a result, the cost-benefit portion of the Proposal could be deemed obsolete to the extent it does not incorporate any of the modifications to other swap data reporting requirements in parts 43 and 45 of the Commission's regulations that the Commission intends to propose and act upon. The failure to propose all the swaps data reporting rule amendments in unison would seem to necessitate a refresh of the accompanying cost-benefit portion of this Proposal, and further public comment.
                            </P>
                        </FTNT>
                        <P>In addition, if, as the Proposal suggests, there actually is a significant problem with inaccurate swap data being reported to SDRs, the piecemeal issuance of these rulemakings makes it more difficult for the Commission to evaluate whether that problem can be rectified by allowing other facets of the swaps data Roadmap to gain traction. Query whether the Commission generating a technical specification removing uncertainty as to what must be reported and how, harmonizing with other regulators and implementing unique identifiers (Unique Transaction Identifiers and Unique Product Identifiers) and critical data elements from CPMI-IOSCO work streams, minimizing the number of fields required to be reported, and affording RCPs more time to report would organically resolve a large proportion of any inaccurate data reporting problem that may exist. The manner in which the Commission has elected to proceed will make it challenging for SDRs and RCPs to comment appropriately on these questions, and I fear will place the Commission in a predicament as it attempts to make informed policy decisions on how best to proceed.</P>
                        <HD SOURCE="HD1">V. Lack of Harmonization With the SEC</HD>
                        <P>
                            Market participants of all shapes-and-sizes—even those that are often on opposing sides of most regulatory debates—all agree on a common theme that has been repeatedly urged upon the Commission via every imaginable medium since the enactment of Dodd-Frank: The Commission and the Securities and Exchange Commission (SEC) should coordinate and harmonize their respective derivatives regulations to the maximum extent possible, and especially concerning entities that have already incurred systems and compliance costs in connection with the corresponding requirements of the related agency. All types of market participants have implored both the Commission and the SEC to minimize compliance burdens on potential dual registrants in connection with the derivatives rules, such as swap data reporting. And yet, notwithstanding the current emphasis on CFTC-SEC harmonization,
                            <SU>23</SU>
                            <FTREF/>
                             the Commission is proposing a swap data reporting rule that appears to take an approach that is the opposite of, and in direct contrast to, the SEC's thinking on the same issue.
                        </P>
                        <FTNT>
                            <P>
                                <SU>23</SU>
                                 
                                <E T="03">See, e.g.,</E>
                                 Memorandum of Understanding Between the U.S. Securities and Exchange Commission and the U.S. Commodity Futures Trading Commission Regarding Coordination in Areas of Common Regulatory Interest and Information Sharing (July 11, 2018) (specifically addressing the regulatory regime for swaps and security-based swaps), 
                                <E T="03">available at https://www.cftc.gov/sites/default/files/2018-07/CFTC_MOU_InformationSharing062818.pdf and https://www.cftc.gov/PressRoom/PressReleases/7745-18.</E>
                            </P>
                        </FTNT>
                        <P>
                            The SEC published a proposed rulemaking in December 2018 
                            <SU>24</SU>
                            <FTREF/>
                             that specifically discusses, among other things, verification of the terms of reported security-based swaps—as does the Proposal. Yet, while the Proposal would increase regulatory burdens on all entities in its amended regulatory reporting scheme, the SEC is considering a more pragmatic approach. The SEC, in its proposal, “believes it to be an appropriate time to revisit and request comment on an issue previously identified in connection with the rules . . . [that] require[] each registered SDR to `confirm with both counterparties to the security-based swap the accuracy of the data that was submitted.' ” 
                            <SU>25</SU>
                            <FTREF/>
                        </P>
                        <FTNT>
                            <P>
                                <SU>24</SU>
                                 Risk Mitigation Techniques for Uncleared Security-Based Swaps, 84 FR 4614 (February 15, 2019) (proposed rules).
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>25</SU>
                                 
                                <E T="03">Id.</E>
                                 at 4633-4634 (footnote omitted).
                            </P>
                        </FTNT>
                        <P>
                            Specifically, the SEC in its proposal states that “SDRs may be able to reasonably rely on certain third parties to address the accuracy of the transaction data. For example, the Commission previously stated that if an SDR develops reasonable policies and procedures that rely on confirmations completed by another entity, such as a third-party confirmation provider, as long as such reliance is reasonable the SDR could use such confirmation to fulfill its obligations under certain SDR rules. Because the two 
                            <PRTPAGE P="21122"/>
                            relevant provisions that we are proposing today generally relate to the obligation of [Security-Based Swap, or `SBS'] Entities to take certain steps in the reconciliation and documentation processes related specifically to the reporting of the relevant security-based swap data to an SDR . . . the Commission believes that . . . these measures, taken together, could provide an SDR with a set of factors to assess the reasonableness of relying on an SBS Entity's ability to independently provide the definitive report of a given security-based swap position, thereby providing a basis for the SDR to satisfy its statutory and regulatory obligations to verify the accuracy of the reported data when the SBS Entity's counterparty is not a member of the SDR.” 
                            <SU>26</SU>
                            <FTREF/>
                        </P>
                        <FTNT>
                            <P>
                                <SU>26</SU>
                                 
                                <E T="03">Id.</E>
                                 at 4634 (footnotes omitted).
                            </P>
                        </FTNT>
                        <P>In other words, the SEC is considering whether the reconciliation process undertaken by security-based swap dealers of their swaps portfolios could satisfy the statutory obligation to confirm the accuracy of data reported to SDRs. This sensible approach being considered demonstrates deference to trusted sources for swap data accuracy when a third-party service provider is employed to address the confirmation of swaps data, similar to the exceptions in Regulations 49.11(b)(1)(ii) and 49.11(b)(2)(ii) that the Proposal would eliminate.</P>
                        <P>
                            As discussed more fully in Section VI below, based on the Commission's reporting hierarchy in Regulation 45.8,
                            <SU>27</SU>
                            <FTREF/>
                             swap dealers (SDs) are the RCP and transmit required swap data elements to an SDR for the vast preponderance of swap transactions. These same SDs are already subject to another regulatory obligation relating to verification of the terms of their swap transactions, as they must conduct a portfolio reconciliation exercise on a regularly recurring basis via Regulation 23.502.
                            <SU>28</SU>
                            <FTREF/>
                             Portfolio reconciliation forces the “[e]xchange [of] the material terms of all swaps in the swap portfolio between the counterparties” and requires the parties to “[r]esolve any discrepancy in material terms and valuations.” 
                            <SU>29</SU>
                            <FTREF/>
                             Since SDs already must check the accuracy of their portfolios through a reconciliation exercise, and since SDs report almost all swaps, then the Commission, like the SEC, should consider leveraging this existing process and afford SDs that undertake such an exercise enough time for it to run its course and then submit that same accurate and verified data set for SDR reporting purposes. Leveraging this existing regulatory process, rather than creating yet another process that compliance officers and operations staff must adhere to, may offer a “good government” solution, assuming the existence of a systemic problem with SDR data accuracy. If SDs represent that the same data reconciled with counterparties per Rule 23.502 is reported to SDRs, then the Commission might not need to impose the burdensome new requirements set out in the Proposal.
                        </P>
                        <FTNT>
                            <P>
                                <SU>27</SU>
                                 17 CFR 45.8.
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>28</SU>
                                 17 CFR 23.502.
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>29</SU>
                                 17 CFR 23.500(i)(1), (3).
                            </P>
                        </FTNT>
                        <P>It is unfortunate that the Commission did not propose—or even request comment on—the less burdensome approach to verification that the SEC is considering in light of our stated commitment to harmonizing the agencies' derivatives rules. And it is even more mystifying to me why we are proposing these rule amendments in the inefficient, piecemeal manner described above when delaying the issuance of this Proposal would not only enable us to issue the various proposed amendments to our swap data reporting rules as a unified package, but also to learn from comments on the SEC's data verification discussion (the comment period closed on April 16) whether the SEC may have identified a better option for fostering accurate reported swaps data.</P>
                        <HD SOURCE="HD1">VI. Outsized Burden Placed Upon SDRs and RCPs, Including End-Users</HD>
                        <P>
                            Swap market participants have repeatedly emphasized to the Commission that the swap data reporting rules are overly complicated, difficult to implement, and a significant operational burden and compliance challenge for all concerned, including end-users.
                            <SU>30</SU>
                            <FTREF/>
                             Yet, the Proposal would add more layers of complexity to reporting workflows, and require SDRs and RCPs to commit more time and money to submit more reports and undertake additional obligations.
                        </P>
                        <FTNT>
                            <P>
                                <SU>30</SU>
                                 In responding to staff's request for comment on the Draft Technical Specifications, 
                                <E T="03">see</E>
                                 fn. 19, 
                                <E T="03">supra,</E>
                                 ISDA stated: “End‐users which either have reporting obligations or which would be compelled to provide data to the reporting counterparty necessitated by the proposed fields would be particularly burdened by the requirements and many will lack the technological capability to capture, transform and report or provide data as required. The small to mid‐sized commodity producers, processors, merchants and other end‐users that use swaps to mitigate commodity, interest rates, foreign exchange or other price risks will require additional technology, compliance and legal support in order to accommodate additional reporting requirements. This will impose significant, unjustified costs to end-users . . . . ISDA, on behalf of commercial end‐users, requests the CFTC to avoid imposing changes and additional reporting requirements on end‐users by maintaining their obligations under the current Reporting Regulations to the greatest extent possible.” Letter from Tara Kruse, ISDA, at 7-8 (March 7, 2016), 
                                <E T="03">available at https://comments.cftc.gov/PublicComments/ViewComment.aspx?id=60713&amp;SearchText=.</E>
                                 ISDA continued to advocate against placing additional burdens on end-users through its joint comment letter with SIFMA to the Swap Data Roadmap and suggested the Commission “should not require non-reporting counterparties, end-users, and smaller firms to perform reconciliations because these entities generally do not have the resources to effectively validate their swap transactions.” 
                                <E T="03">See</E>
                                 fn. 20, 
                                <E T="03">supra,</E>
                                 at 6.
                            </P>
                        </FTNT>
                        <P>In particular, the Commission has heard from many end-users about the immense nature of their reporting burdens, how regulatory capture on end-users has impacted their business models and their ability to hedge via derivatives markets, and the unintended consequences of the initial implementation of the Dodd-Frank swap reporting regime. In response, the Commission, commendably, has made considerable progress in addressing reporting issues and limiting burdens on end-users via the various tools at our disposal when consistent with our regulatory responsibilities. It is not clear to me why this Proposal would break from those efforts and go in the opposite direction by placing new and burdensome swap data reporting obligations on end-users.</P>
                        <P>
                            End-user RCPs would bear several onerous obligations under this Proposal. End-user RCPs would have to commit considerable resources to create more sophisticated and elaborate reporting systems in order to be compliant. The Proposal estimates that 1,585 RCPs are neither SDs, major swap participants (MSPs), nor DCOs.
                            <SU>31</SU>
                            <FTREF/>
                             As a result of the Proposal, all of these end-user RCPs would have to acquire or build additional processes and hire more staff to comply with these new reporting regulations, regardless of the number, notional amount, asset class, or risk profile of the swaps for which they are the RCP. To provide some perspective, staff has indicated that of new transactions in January 2019, trades with at least one SD counterparty (which would serve as the RCP) per asset class represented 99.6183% of the 22,446 CDS trades; 98.2466% of the 137,499 IRS trades; 97.0540% of the 603,696 FX trades; 99.9998% of the 471,657 Equity trades; and 85.3056% of the 60,021 Commodity trades. In other words, the 1,585 RCPs that are not SDs, MSPs, or DCOs reported, at most, 86 CDS, 2,454 IRS, 18,325 FX, 1 Equity, and 10,339 Commodity swaps during this time period. Given the limited number of swaps for which end-users are RCPs compared to the overall swaps market, I question whether imposing on all end-users that may serve as an RCP the additional burdens of preparing for compliance with the requirements of this Proposal reflects an appropriate consideration of costs and benefits.
                        </P>
                        <FTNT>
                            <P>
                                <SU>31</SU>
                                 Proposal, text accompanying n.226.
                            </P>
                        </FTNT>
                        <P>The Commission has made strides post the initial roll-out of its Dodd-Frank rulemakings to fix unintended consequences of its swap data reporting rules and minimize the burdens on end-users where appropriate. This Proposal, unfortunately, errs in the other direction. I welcome suggestions via the public comment process on the appropriate role for end-user RCPs to play in assuring the accuracy of reported swap data short of imposing the burdens set out in the Proposal.</P>
                        <HD SOURCE="HD1">VII. Alternate Approaches for Further Consideration</HD>
                        <P>To be clear, my concern with the Proposal is not simply that it would impose costs on market participants; all necessary regulatory requirements do so. Rather, my concern is with the extent of the burdens that the Proposal would impose on market participants, including end-users, in light of the prospects that the Proposal will meaningfully improve the quality of reported swap data. As discussed above, the Proposal does not establish that there actually is a systemic problem in that regard. But assuming that to be the case, consider the following fact pattern and whether any errors would be found and rectified under the Proposal:</P>
                        <P>• RCP submits data to an SDR from its regulatory reporting databases;</P>
                        <P>
                            • SDR creates Open Swaps reports based upon the data received;
                            <PRTPAGE P="21123"/>
                        </P>
                        <P>• SDR provides a mechanism for the RCP to verify the accuracy of the Open Swaps report; and</P>
                        <P>• RCP checks the Open Swaps report against the data that it submitted to the SDR.</P>
                        <P>
                            In other words, if the original data set utilized by the RCP contains an inaccuracy, the Proposal could simply impose a futile exercise based on circular logic. The end result of the new burdens placed upon RCPs and SDRs would merely be a false positive in this scenario. If the RCP's data is inaccurate in the first place, then the Proposal would be successful only in making swap data reporting more complicated and expensive, without actually improving the accuracy of the data reported to the SDR.
                            <SU>32</SU>
                            <FTREF/>
                        </P>
                        <FTNT>
                            <P>
                                <SU>32</SU>
                                 To be sure, the Proposal might identify situations in which the SDR inexplicably alters the data that it receives from an RCP. But current Regulation 49.10(c), 17 CFR 49.10(c), already prohibits such activity since an SDR “shall establish policies and procedures reasonably designed to prevent any provision in a valid swap from being invalidated or modified through the confirmation or recording process of the swap data repository. The policies and procedures must ensure that the swap data repository's user agreements are designed to prevent any such invalidation or modification.”
                            </P>
                        </FTNT>
                        <P>Accurately reported swap data is, of course, crucial to the Commission's performance of its regulatory responsibilities and the effective operation of the Dodd-Frank swap regime. That is why I am concurring in the issuance of the Proposal—because I support the Commission's efforts to determine whether appropriate improvements can be made to its swap data reporting rule set.</P>
                        <P>This Proposal provides an opportunity for the public to suggest other, perhaps better, solutions to more efficiently produce the desired outcome of accurate swap data for purposes of conducting the Commission's work, facilitating risk oversight and management, and fostering robust swaps markets. I strongly encourage SDRs, SDs, DCOs, end-users, and the public in general to take advantage of this opportunity and provide not only feedback on the Proposal, but also their ideas on how to appropriately balance the need for accurately reported swap data with the costs and burdens associated with obtaining it. The Commission should consider any alternate approaches that can satisfy the policy goal of improving the quality of SDR data while limiting the impact on market participants already saturated with complex and repetitive reporting obligations.</P>
                        <P>
                            I would like to offer, and invite comment on, a few alternatives with respect to RCPs. CEA Section 21(c)(2) provides that SDRs shall “confirm with both counterparties to the swap the accuracy of the data that was submitted.” 
                            <SU>33</SU>
                            <FTREF/>
                             As a result, a clear obligation exists as to what SDRs must do. The statute is less clear on what RCPs must do, if anything.
                        </P>
                        <FTNT>
                            <P>
                                <SU>33</SU>
                                 7 U.S.C. 24a(c)(2).
                            </P>
                        </FTNT>
                        <P>Under the Commission's current regulations, all RCPs must submit hundreds of fields per transaction to their respective SDRs. Some RCPs have thousands of open swaps that would be captured under this Proposal and require recurring verification. I hope that commenters will address whether a smaller number of swaps and/or a limited subset of essential fields that must be verified would enable the Commission to conduct its regulatory functions without indiscriminately requiring verification of all swap data elements.</P>
                        <P>
                            Another option on which public comment would be helpful is requiring RCPs to verify only the accuracy of a statistically significant portion of their Open Swaps report and then decide, based on the level of accuracy, whether the entirety of Open Swaps must be analyzed. Still another option might be to require verification of only a limited set of the most important fields required to understand the basic terms of plain-vanilla swap transactions. Finally, commenters could address a possible 
                            <E T="03">de minimis</E>
                             level that must be exceeded before the new reporting obligations in this Proposal would apply. For example, if an RCP has less than X swaps per year, or less than Y notional transacted per year, then it would not have to perform these verification functions.
                        </P>
                        <P>With respect to end-user RCPs in particular, where the ability to build reporting systems and the cost of doing so on a per swap basis is much different than for SDs, MSPs, and DCOs, comment would be beneficial on whether end-user RCPs should have more time than proposed, both for replying to Open Swaps reports with a “verification” or “notification of discrepancy” message and correcting errors and omissions. Also, commenters may wish to address the frequency of how often end-user RCPs should be required to participate in this labor-intensive process. I recognize that the Proposal includes less stringent obligations on end-user RCPs in comparison to SDs, MSPs, and DCOs that are RCPs, but I welcome comment on whether the Commission should strive to do more in this regard.</P>
                        <P>As written, the Proposal would impose a number of new, often undefined, obligations with respect to swap data reporting. The potential alternatives noted above, together with others that commenters may suggest, could represent a common sense approach to addressing concerns regarding swap data accuracy while appropriately calibrating the costs and burdens associated with verification of SDR data.</P>
                    </EXTRACT>
                    <HD SOURCE="HD1">Appendix 5—Statement of Commissioner Dan. M. Berkovitz</HD>
                    <EXTRACT>
                        <P>
                            I am pleased to support the Commission's notice of proposed rulemaking (“NPRM”) to amend its rules for swap data repositories (“SDRs”) and data reporting requirements.
                            <SU>1</SU>
                            <FTREF/>
                             The proposed amendments reflect the Commission's commitment to accurate, detailed, and timely swaps data for regulators, market participants, and the public through enhanced data verification and error correction procedures, among other amendments. They are an important step in achieving the Dodd-Frank Act's mandate of swap data reporting as an integral part of OTC derivatives reform and financial market stability. 
                            <SU>2</SU>
                            <FTREF/>
                        </P>
                        <FTNT>
                            <P>
                                <SU>1</SU>
                                 The NPRM notes that it is the first of three rulemakings anticipated pursuant to the Commission's 2017 “Roadmap to Achieve High Quality Swaps Data” (“Roadmap”). 
                                <E T="03">See</E>
                                 NPRM section I(C). Information regarding the Roadmap is available in CFTC Letter 17-33 (Division of Market Oversight Announces Review of Swap Reporting Rules in Parts 43, 45, and 49 of Commission Regulations) (July 10, 2017), available at 
                                <E T="03">http://www.cftc.gov/idc/groups/public/@lrlettergeneral/documents/letter/17-33.pdf.</E>
                                 The Roadmap itself is available at 
                                <E T="03">http://www.cftc.gov/idc/groups/public/@newsroom/documents/file/dmo_swapdataplan071017.pdf.</E>
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>2</SU>
                                 
                                <E T="03">See also</E>
                                 G20, Leaders' Statement: The Pittsburgh Summit (Sept. 24-25, 2009), paragraph 13, available at 
                                <E T="03">https://www.treasury.gov/resource-center/international/g7-g20/Documents/pittsburgh_summit_leaders_statement_250909.pdf.</E>
                            </P>
                        </FTNT>
                        <P>
                            The Dodd-Frank Act codified important new swap data reporting obligations, 
                            <SU>3</SU>
                            <FTREF/>
                             and established SDRs as the vehicles for reporting and retaining swaps data. 
                            <SU>4</SU>
                            <FTREF/>
                             It recognized the role of regulatory reporting and real-time public reporting in enhancing transparency and reducing systemic risk in the U.S. financial system. Consistent with these foundational principles, the Commission has focused on swap data reporting since the very inception of its Dodd-Frank efforts. In 2011, it began finalizing a series of coordinated reporting rules that provide for both regulatory and real-time public reporting of swap transaction and pricing data (Parts 45 and 43); 
                            <SU>5</SU>
                            <FTREF/>
                             establish SDRs to receive data and make it available to regulators and the public (Part 49); 
                            <SU>6</SU>
                            <FTREF/>
                             and define certain swap dealer and major swap participant reporting obligations (Part 23). 
                            <SU>7</SU>
                            <FTREF/>
                        </P>
                        <FTNT>
                            <P>
                                <SU>3</SU>
                                 
                                <E T="03">See</E>
                                 Dodd-Frank Wall Street Reform and Consumer Protection Act, section 727, Public Law 111-203, 124 Stat. 1376 (2010) (the “Dodd-Frank Act”), available at 
                                <E T="03">https://www.gpo.gov/fdsys/pkg/PLAW-111publ203/pdf/PLAW-111publ203.pdf.</E>
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>4</SU>
                                 
                                <E T="03">See</E>
                                 Dodd-Frank Act, section 728.
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>5</SU>
                                 Swap Data Recordkeeping and Reporting Requirements, 77 FR 2136 (Jan. 13, 2012) (“Part 45 Adopting Release”) and Real-Time Public Reporting of Swap Transaction Data, 77 FR 1182 (“Part 43 Adopting Release”).
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>6</SU>
                                 Swap Data Repositories: Registration Standards, Duties and Core Principles, 76 FR 54538 (Sept. 1, 2011).
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>7</SU>
                                 Swap Dealer and Major Swap Participant Recordkeeping, Reporting, and Duties Rules; Futures Commission Merchant and Introducing Broker Conflicts of Interest Rules; and Chief Compliance Officer Rules for Swap Dealers, Major Swap Participants, and Futures Commission Merchants, 77 FR 20128 (Apr. 3, 2012).
                            </P>
                        </FTNT>
                        <P>
                            The Commission's regulations leverage real-time public reporting to help increase transparency, fairness, and efficiency in swaps markets, 
                            <SU>8</SU>
                            <FTREF/>
                             while regulatory reporting assists the Commission and other financial regulators in market oversight and systemic risk mitigation. 
                            <SU>9</SU>
                            <FTREF/>
                             In this regard, SDRs provide a more consolidated view 
                            <SU>10</SU>
                            <FTREF/>
                             of market 
                            <PRTPAGE P="21124"/>
                            participants' exposures across their swaps portfolios, and can help to identify concentrations and other potential risks that are dispersed across individual portfolios, trading platforms, and clearinghouses. Accurate, complete, and timely information is therefore vital to any successful swaps data reporting regime. These objectives were central to post-crisis reform efforts, and they must remain the primary considerations as the Commission moves to enhance its reporting rules.
                        </P>
                        <FTNT>
                            <P>
                                <SU>8</SU>
                                 
                                <E T="03">See</E>
                                 Part 43 Adopting Release, 77 FR 1182, 1183.
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>9</SU>
                                 
                                <E T="03">See</E>
                                 Part 45 Adopting Release, 77 FR 2136, 2138.
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>10</SU>
                                 However, in a jurisdiction with multiple SDRs, such as the United States, regulators' view into market participants' swap positions is not fully consolidated. The presence of different SDRs in jurisdictions across the globe also impinges on full consolidation. These limitations give added import to standardizing data reporting, data fields, and regulators' access to data. Aggregation by regulators in a jurisdiction with multiple SDRs, for example, is greatly facilitated by agreed reporting conventions.
                            </P>
                        </FTNT>
                        <P>
                            It is important to note that the existing reporting rules have already achieved important successes. Currently, three provisionally registered SDRs 
                            <SU>11</SU>
                            <FTREF/>
                             facilitate regulatory reporting and real-time public reporting, and CFTC staff estimates that SDRs processed approximately 13 million unique swaps in 2018. SDRs provide online systems where any member of the public can track transaction-by-transaction information as swaps are executed and publicly reported. SDRs have also designed portals and other resources to provide CFTC staff with more complete regulatory access.
                        </P>
                        <FTNT>
                            <P>
                                <SU>11</SU>
                                 Chicago Mercantile Exchange Inc. Swap Data Repository; DTCC Data Repository (U.S.); and ICE Trade Vault.
                            </P>
                        </FTNT>
                        <P>
                            While building on this solid foundation, the NPRM and the proposed amendments acknowledge areas where the Commission's existing swap data reporting rules are not working as effectively as they might. Registered swap dealers began reporting swap data on December 31, 2012, and the proposed amendments are therefore based on over six years of Commission experience with SDRs and swap data reporting. In this regard, the NPRM addresses several areas that the Commission identified for improvement in its 2017 Roadmap. For example, the NPRM addresses swap data verification and the prompt correction of errors or omissions in previously reported data. It proposes to clarify and strengthen the obligations of SDRs and reporting counterparties by requiring SDRs to provide reporting counterparties with regular reports on open swaps to “verify the accuracy and completeness of swap data reported to SDRs.” 
                            <SU>12</SU>
                            <FTREF/>
                             In turn, reporting counterparties must respond affirmatively by indicating that the records in the reports they receive are accurate, or otherwise correcting any errors or omissions.
                            <SU>13</SU>
                            <FTREF/>
                             Reporting counterparties must respond within timeframes specified in the NPRM, and they must do so pursuant to standards established by SDRs.
                        </P>
                        <FTNT>
                            <P>
                                <SU>12</SU>
                                 
                                <E T="03">See</E>
                                 NPRM section II(G) (discussing proposed section 49.11).
                            </P>
                        </FTNT>
                        <FTNT>
                            <P>
                                <SU>13</SU>
                                 
                                <E T="03">See</E>
                                 NPRM section III(B) (discussing proposed section 45.14).
                            </P>
                        </FTNT>
                        <P>
                            The NPRM also proposes that SDRs provide open swap reports to the Commission. SDRs must provide such reports pursuant to timing, method, frequency, content, and other instructions that the Commission may issue.
                            <SU>14</SU>
                            <FTREF/>
                             While working with SDRs, open swaps reports will help the Commission to perform its regulatory functions more effectively and efficiently through reports that SDRs standardize in content, format, calculation methods, and other variables.
                        </P>
                        <FTNT>
                            <P>
                                <SU>14</SU>
                                 
                                <E T="03">See</E>
                                 NRPM section II(E) (discussing proposed section 49.9).
                            </P>
                        </FTNT>
                        <P>In addition to these important data-focused amendments, the NPRM also proposes amendments to rules in Part 49 of the Commission's regulations that govern the internal operations of SDRs, particularly as they pertain to an SDR's chief compliance officer (“CCO”), conflicts of interest, and annual compliance reports. I am interested in receiving comments regarding these proposed amendments, including areas where the Commission's existing CCO-related rules for SDRs are working well and where they could be improved. In this regard, the Commission should be vigilant that changes to compliance or other requirements made in the name of efficiency do not diminish the self-regulatory foundation of the Commission's oversight of derivatives markets.</P>
                        <P>I thank the staff of the Division of Market Oversight for their dedicated work on both this NPRM and potential future proposals related to swaps data reporting. I also thank staff for their responsiveness to questions and comments from my office, including their willingness to consider changes that have improved the NPRM before the Commission today. While swap data reporting is not always the most glamorous area of the Commission's work, it is vitally important that we get it right. I look forward to public comments on the NPRM, and to continued efforts by market participants and the Commission to achieve the most effective swap data reporting possible.</P>
                    </EXTRACT>
                </SUPLINF>
                <FRDOC>[FR Doc. 2019-08788 Filed 5-10-19; 8:45 am]</FRDOC>
                <BILCOD> BILLING CODE 6351-01-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>84</VOL>
    <NO>92</NO>
    <DATE>Monday, May 13, 2019</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="21125"/>
            <PARTNO>Part IV</PARTNO>
            <AGENCY TYPE="P">Department of Commerce</AGENCY>
            <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
            <HRULE/>
            <CFR>50 CFR Part 218</CFR>
            <TITLE>Taking and Importing Marine Mammals; Taking Marine Mammals Incidental to the U.S. Navy Training and Testing Activities in the Atlantic Fleet Training and Testing Study Area; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="21126"/>
                    <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                    <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                    <CFR>50 CFR Part 218</CFR>
                    <DEPDOC>[Docket No. 190220145-9145-01]</DEPDOC>
                    <RIN>RIN 0648-BI85</RIN>
                    <SUBJECT>Taking and Importing Marine Mammals; Taking Marine Mammals Incidental to the U.S. Navy Training and Testing Activities in the Atlantic Fleet Training and Testing Study Area</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule; request for comment.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>NMFS has received a request from the U.S. Navy (Navy) to extend the time period from November 2023 to November 2025 for Marine Mammal Protection Act (MMPA) regulations authorizing the take of marine mammals incidental to Navy training and testing activities conducted in the Atlantic Fleet Training and Testing (AFTT) Study Area. In August 2018, the MMPA was amended by the John S. McCain National Defense Authorization Act (NDAA) for Fiscal Year 2019 to allow for seven-year authorizations for military readiness activities, as compared to the previously allowed five years. The Navy's activities qualify as military readiness activities pursuant to the MMPA as amended by the NDAA for Fiscal Year 2004. In making the request to extend the time period covered by the MMPA AFTT regulations from five to seven years, the Navy proposes no changes to their specified activities, the geographical region in which those activities would be conducted, mitigation measures, monitoring, or reporting over the longer seven-year period. Pursuant to the MMPA, NMFS is requesting comments on the proposed seven-year rule and associated Letters of Authorization (LOAs) to cover the same activities covered by the existing 2018 AFTT regulations. NMFS will consider all public comments prior to issuing any final rule and making final decisions on the issuance of the requested LOAs, and agency responses will be summarized in the notice of the final decision.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Comments and information must be received no later than June 12, 2019.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>You may submit comments on this document, identified by NOAA-NMFS-2019-0050, by any of the following methods:</P>
                        <P>
                            • 
                            <E T="03">Electronic submission:</E>
                             Submit all electronic public comments via the federal e-Rulemaking Portal. Go to 
                            <E T="03">www.regulations.gov/#!docketDetail;D=NOAA-NMFS-2019-0050,</E>
                            click the “Comment Now!” icon, complete the required fields, and enter or attach your comments.
                        </P>
                        <P>
                            • 
                            <E T="03">Mail:</E>
                             Submit written comments to Jolie Harrison, Chief, Permits and Conservation Division, Office of Protected Resources, National Marine Fisheries Service, 1315 East West Highway, Silver Spring, MD 20910.
                        </P>
                        <P>
                            <E T="03">Instructions:</E>
                             Comments sent by any other method, to any other address or individual, or received after the end of the comment period, may not be considered by NMFS. All comments received are a part of the public record and will generally be posted for public viewing on 
                            <E T="03">www.regulations.gov</E>
                             without change. All personal identifying information (
                            <E T="03">e.g.,</E>
                             name, address), confidential business information, or otherwise sensitive information submitted voluntarily by the sender will be publicly accessible. NMFS will accept anonymous comments (enter “N/A” in the required fields if you wish to remain anonymous). Attachments to electronic comments will be accepted in Microsoft Word, Excel, or Adobe PDF file formats only.
                        </P>
                        <P>
                            A copy of the Navy's applications, NMFS' proposed and final rules and subsequent LOAs for the existing regulations, and other supporting documents and documents cited herein may be obtained online at: 
                            <E T="03">www.fisheries.noaa.gov/national/marine-mammal-protection/incidental-take-authorizations-military-readiness-activities.</E>
                             In case of problems accessing these documents, please use the contact listed here (see 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                            ).
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Wendy Piniak, Office of Protected Resources, NMFS, (301) 427-8401.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">Purpose of Regulatory Action</HD>
                    <P>
                        These proposed regulations, issued under the authority of the MMPA (16 U.S.C. 1361 
                        <E T="03">et seq.</E>
                        ), would extend the framework for authorizing the take of marine mammals incidental to the Navy's training and testing activities (which qualify as military readiness activities) from the use of sonar and other transducers, in-water detonations, air guns, impact pile driving/vibratory extraction, and the movement of vessels throughout the AFTT Study Area, which includes areas of the western Atlantic Ocean along the East Coast of North America, portions of the Caribbean Sea, and the Gulf of Mexico.
                    </P>
                    <P>NMFS received an application from the Navy requesting to extend NMFS' existing MMPA regulations (50 CFR part 218, subpart I; hereafter “2018 AFTT regulations”) that authorize the take of marine mammals incidental to Navy training and testing activities conducted in the AFTT Study Area to cover seven years of the Navy's activities, instead of five. Take is anticipated to occur by Level A harassment and Level B harassment as well as a very small number of serious injuries or mortalities incidental to the Navy's training and testing activities.</P>
                    <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 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 issued or, if the taking is limited to harassment, a notice of a proposed incidental take authorization is provided to the public for review and the opportunity to submit comments.</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 stocks and will not have an unmitigable adverse impact on the availability of the species or stocks 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 such species or stocks for taking for certain subsistence uses (referred to in this rule as “mitigation measures”); and requirements pertaining to the monitoring and reporting of such takings. The MMPA defines “take” to mean to harass, hunt, capture, or kill, or attempt to harass, hunt, capture, or kill any marine mammal. The 
                        <E T="03">Preliminary Analysis and Negligible Impact Determination</E>
                         section below discusses the definition of “negligible impact.”
                    </P>
                    <P>
                        The NDAA for Fiscal Year 2004 (2004 NDAA) (Pub. L. 108-136) amended section 101(a)(5) of the MMPA to remove the “small numbers” and “specified geographical region” provisions indicated above and amended the definition of “harassment” 
                        <PRTPAGE P="21127"/>
                        as it applies to a “military readiness activity” to read as follows (Section 3(18)(B) of the MMPA): (i) Any act that injures or has the significant potential to injure a marine mammal or marine mammal stock in the wild (Level A Harassment); or (ii) Any act that disturbs or is likely to disturb a marine mammal or marine mammal stock in the wild by causing disruption of natural behavioral patterns, including, but not limited to, migration, surfacing, nursing, breeding, feeding, or sheltering, to a point where such behavioral patterns are abandoned or significantly altered (Level B Harassment). In addition, the 2004 NDAA amended the MMPA as it relates to military readiness activities such that least practicable adverse impact shall include consideration of personnel safety, practicality of implementation, and impact on the effectiveness of the military readiness activity.
                    </P>
                    <P>More recently, section 316 of the NDAA for Fiscal Year 2019 (2019 NDAA) (Pub. L. 115-232), signed on August 13, 2018, amended the MMPA to allow incidental take rules for military readiness activities under section 101(a)(5)(A) to be issued for up to seven years. Prior to this amendment, all incidental take rules under section 101(a)(5)(A) were limited to five years.</P>
                    <HD SOURCE="HD1">Summary of Request</HD>
                    <P>On November 14, 2018, NMFS issued a five-year final rule governing the taking of marine mammals incidental to Navy training and testing activities conducted in the AFTT Study Area (83 FR 57076; hereafter “2018 AFTT final rule”). Previously on August 13, 2018, and towards the end of the time period in which NMFS was processing the Navy's request for the 2018 regulations, the 2019 NDAA amended the MMPA for military readiness activities to allow incidental take regulations to be issued for up to seven years instead of the previous five years. The Navy's training and testing activities conducted in the AFTT Study Area qualify as military readiness activities pursuant to the MMPA, as amended by the 2004 NDAA. On November 16, 2018, the Navy submitted an application requesting that NMFS extend the 2018 AFTT regulations and associated LOAs such that they would cover take incidental to seven years of training and testing activities instead of five, extending the expiration date from November 13, 2023 to November 13, 2025. A revised application correcting the estimated takes due to ship shock trials (Table 5.1-2) was submitted to NMFS by the Navy on January 18, 2019.</P>
                    <P>
                        In its 2019 application, the Navy proposes no changes to the nature of the specified activities covered by the 2018 AFTT final rule, the level of activity within and between years would be consistent with that previously analyzed in the 2018 AFTT final rule, and all activities would be conducted within the same boundaries of the AFTT Study Area identified in the 2018 AFTT final rule. Therefore, the training and testing activities (
                        <E T="03">e.g.,</E>
                         equipment and sources used, exercises conducted) and the mitigation, monitoring, and reporting measures are identical to those described and analyzed in the 2018 AFTT final rule. The only changes included in the Navy's request are to conduct those same activities in the same region for an additional two years. In its request, the Navy included all information necessary to identify the type and amount of incidental take that may occur in the two additional years so NMFS could determine whether the analyses and conclusions regarding the impacts of the proposed activities on marine mammal species and stocks previously reached for five years of activities remain the same for seven years of identical activity.
                    </P>
                    <P>The Navy's mission is to organize, train, equip, and maintain combat-ready naval forces capable of winning wars, deterring aggression, and maintaining freedom of the seas. This mission is mandated by federal law (10 U.S.C. 8062), which ensures the readiness of the naval forces of the United States. The Navy executes this responsibility by establishing and executing training programs, including at-sea training and exercises, and ensuring naval forces have access to the ranges, operating areas (OPAREAs), and airspace needed to develop and maintain skills for conducting naval activities.</P>
                    <P>
                        The Navy proposes to continue conducting training and testing activities within the AFTT Study Area. The Navy's January 18, 2019, rulemaking and LOA extension application (hereafter “2019 Navy application”) reflects the same compilation of training and testing activities presented in the Navy's June 16, 2017, initial rulemaking and LOA application (hereafter “2017 Navy application”) and the 2018 AFTT regulations that were subsequently promulgated, which can be found at: 
                        <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/incidental-take-authorizations-military-readiness-activities.</E>
                         These activities are deemed by the Navy necessary to accomplish military readiness requirements and are anticipated to continue into the reasonably foreseeable future. The 2019 Navy application and this rule cover training and testing activities that would occur over seven years, including the five years already authorized under the 2018 AFTT regulations, with the regulations valid from the publication date of the final rule (if issued) through November 13, 2025.
                    </P>
                    <HD SOURCE="HD1">Summary of the Proposed Regulations</HD>
                    <P>
                        NMFS is proposing to extend the incidental take regulations and associated LOAs through November 13, 2025 to cover the same Navy activities covered by the 2018 AFTT regulations. The 2018 AFTT final rule was only recently published and its analysis remains current and valid. In its 2019 application, the Navy proposes no changes to the nature (
                        <E T="03">e.g.,</E>
                         equipment and sources used, exercises conducted) or level of the specified activities within or between years or to the boundaries of the AFTT Study Area. The mitigation, monitoring, and reporting measures would be identical to those described and analyzed in the 2018 AFTT final rule. The proposed regulatory language included at the end of this proposed rule, which would be published at 50 CFR part 218, subpart I, also is the same as that under the AFTT 2018 regulations, except for a small number of minor, technical changes. No new information has been received from the Navy, or otherwise become available to NMFS, since publication of the 2018 AFTT final rule that significantly changes the analyses supporting the 2018 findings. Where there is any new information pertinent to the descriptions, analyses, or findings required to authorize incidental take for military readiness activities under MMPA section 101(a)(5)(A), that information is provided in the appropriate sections below.
                    </P>
                    <P>
                        Because the activities included in the 2019 Navy application have not changed and the analyses and findings included in the documents provided and produced in support of the recently published 2018 AFTT final rule remain current and applicable, this proposed rule relies heavily on and references to the applicable information and analyses in those documents. Below is a list of the regulatory documents referenced in this proposed rule. The list indicates the short name by which the document is referenced in this proposed rule, as well as the full titles of the cited documents. All of the documents can be found at: 
                        <E T="03">www.fisheries.noaa.gov/national/marine-mammal-protection/incidental-take-authorizations-military-readiness-activities</E>
                         and 
                        <E T="03">http://www.aftteis.com/.</E>
                        <PRTPAGE P="21128"/>
                    </P>
                    <P>• NMFS March 13, 2018, Atlantic Fleet Training and Testing (AFTT) proposed rule (83 FR 10954; hereafter “2018 AFTT proposed rule”);</P>
                    <P>• NMFS November 14, 2018, Atlantic Fleet Training and Testing (AFTT) final rule (83 FR 57076; hereafter “2018 AFTT final rule”);</P>
                    <P>• NMFS December 27, 2018, Hawaii-Southern California Training and Testing (HSTT) Study Area final rule (83 FR 66846; hereafter “2018 HSTT final rule”);</P>
                    <P>• Navy June 16, 2017, MMPA rulemaking and LOA application (hereafter “2017 Navy application”);</P>
                    <P>• Navy January 18, 2019, MMPA rulemaking and LOA extension application (hereafter “2019 Navy application”); and</P>
                    <P>• September 14, 2018, Atlantic Fleet Training and Testing (AFTT) Final Environmental Impact Statement/Overseas Environmental Impact Statement (FEIS/OEIS) (hereafter “2018 AFTT FEIS/OEIS”).</P>
                    <HD SOURCE="HD1">Description of the Specified Activity</HD>
                    <P>The Navy requests authorization to take marine mammals incidental to conducting training and testing activities. The Navy has determined that acoustic and explosives stressors are most likely to result in impacts on marine mammals that could rise to the level of harassment. Detailed descriptions of these activities are provided in Chapter 2 of the 2018 AFTT FEIS/OEIS and in the 2017 and 2019 Navy applications.</P>
                    <HD SOURCE="HD2">Overview of Training and Testing Activities</HD>
                    <P>
                        The Navy routinely trains in the AFTT Study Area in preparation for national defense missions. Training and testing activities and components covered in the 2019 Navy application are described in detail in the 
                        <E T="03">Overview of Training and Testing Activities</E>
                         sections of the 2018 AFTT proposed rule and the 2018 AFTT final rule and Chapter 2 of the 2018 AFTT FEIS/OEIS (
                        <E T="03">http://www.aftteis.com/</E>
                        ). Each military training and testing activity described meets mandated Fleet requirements to deploy ready forces. The Navy proposes no changes to the specified activities described and analyzed in the 2018 AFTT final rule. The boundaries of the AFTT Study Area (see Figure 1.2-1 of the 2019 Navy application); the training and testing activities (
                        <E T="03">e.g.,</E>
                         equipment and sources used, exercises conducted); manner of or amount of vessel movement; and standard operating procedures presented in this proposed rule are identical to those described and analyzed in the 2018 AFTT final rule.
                    </P>
                    <HD SOURCE="HD2">Dates and Duration</HD>
                    <P>
                        The specified activities would occur at any time during the seven-year period of validity of the regulations. The proposed number of training and testing activities are described in the 
                        <E T="03">Detailed Description of the Specified Activities</E>
                         section (Tables 1 through 4).
                    </P>
                    <HD SOURCE="HD2">Specified Geographical Region</HD>
                    <P>
                        The Navy proposes no changes to the geographic extent of the AFTT Study Area as described in the 2018 AFTT final rule. The AFTT Study Area (see Figure 2-1 of the 2019 Navy application) includes areas of the western Atlantic Ocean along the east coast of North America, the Gulf of Mexico, and portions of the Caribbean Sea. The AFTT Study Area begins at the mean high tide line along the U.S. coast and extends east to the 45-degree west longitude line, north to the 65-degree north latitude line, and south to approximately the 20-degree north latitude line. The AFTT Study Area also includes Navy pierside locations, bays, harbors, and inland waterways, and civilian ports where training and testing occurs. The AFTT Study Area generally follows the Commander Task Force 80 area of operations, covering approximately 2.6 million nautical miles squared (nmi
                        <SU>2</SU>
                        ) of ocean area, and includes designated Navy range complexes and associated operating areas (OPAREAs) and special use airspace. While the AFTT Study Area itself is very large, the vast majority of Navy training and testing occurs in designated range complexes and testing ranges.
                    </P>
                    <P>
                        A Navy range complex consists of geographic areas that encompass a water component (above and below the surface) and airspace, and may encompass a land component where training and testing of military platforms, tactics, munitions, explosives, and electronic warfare systems occur. Range complexes include established OPAREAs, which may be further divided to provide better control of the area for safety reasons. Additional detail on range complexes and testing ranges was provided in the 
                        <E T="03">Duration and Location</E>
                         section of the 2018 AFTT proposed rule; please see the 2018 AFTT proposed rule or the 2017 Navy application for more information.
                    </P>
                    <HD SOURCE="HD2">Description of Acoustic and Explosive Stressors</HD>
                    <P>
                        The Navy uses a variety of sensors, platforms, weapons, and other devices, including ones used to ensure the safety of Sailors and Marines, to meet its mission. Training and testing with these systems may introduce acoustic (sound) energy or shock waves from explosives into the environment. The specific components that could act as stressors by having direct or indirect impacts on the environment are described in detail in the 
                        <E T="03">Description of Acoustic and Explosive Stressors</E>
                         section of the 2018 AFTT final rule and Chapter 2 of the 2018 AFTT FEIS/OEIS. The Navy proposes no changes to the nature of the specified activities and, therefore, the acoustic and explosive stressors are identical to those described and analyzed in the 2018 AFTT final rule.
                    </P>
                    <HD SOURCE="HD2">Other Stressor—Vessel Strike</HD>
                    <P>Vessel strikes are not specific to any particular training or testing activity, but rather a limited, sporadic, and incidental result of Navy vessel movement within the AFTT Study Area. Navy vessels transit at speeds that are optimal for fuel conservation or to meet training and testing requirements. The average speed of large Navy ships ranges between 10 and 15 knots and submarines generally operate at speeds in the range of 8-13 knots, while a few specialized vessels can travel at faster speeds. By comparison, this is slower than most commercial vessels where full speed for a container ship is typically 24 knots (Bonney and Leach, 2010).</P>
                    <P>
                        Should a vessel strike occur, it would likely result in incidental take from serious injury and/or mortality and, accordingly, for the purposes of the analysis we assume that any ship strike would result in serious injury or mortality. The Navy proposes no changes to the nature of the specified activities, the training and testing activities, the manner of or amount of vessel movement, and standard operating procedures. Therefore, the description of vessel strikes as a stressor is the same as those presented in the 
                        <E T="03">Other Stressor—Vessel Strike</E>
                         sections of the 2018 AFTT proposed rule and 2018 AFTT final rule.
                    </P>
                    <HD SOURCE="HD2">Detailed Description of the Specified Activities</HD>
                    <P>
                        The Navy's proposed activities are presented and analyzed as a representative year of training to account for the natural fluctuation of training cycles and deployment schedules in any seven-year period. In the 2018 AFTT final rule, NMFS analyzed activities based on the Navy conducting three years of a representative level of activity and two years of a maximum level of activity. For the purposes of this rulemaking, the Navy proposes that the additional two 
                        <PRTPAGE P="21129"/>
                        years of training and testing would consist of one additional year of maximum training tempo and one representative year of training tempo consistent with the pattern set forth in the 2018 AFTT final rule, the 2018 AFTT FEIS/OEIS, and the 2017 Navy application.
                    </P>
                    <HD SOURCE="HD3">Proposed Training Activities</HD>
                    <P>
                        The number of proposed training activities that could occur annually and the duration of those activities remains identical to those presented in Table 4 of the 2018 AFTT final rule, and are not repeated here. The number of proposed training activities that could occur over the seven-year period are presented in Table 1. The table is organized according to primary mission areas and includes the activity name, associated stressors applicable to these proposed regulations, sound source bin, number of proposed activities, and locations of those activities in the AFTT Study Area. For further information regarding the primary platform used (
                        <E T="03">e.g.</E>
                        , ship or aircraft type) see Appendix A (Navy Activity Descriptions) of the 2018 AFTT FEIS/OEIS.
                    </P>
                    <GPOTABLE COLS="6" OPTS="L2,p6,6/7,i1" CDEF="xs60,r25,r75,r25,12,xs90">
                        <TTITLE>Table 1—Proposed Training Activities Analyzed for Seven-Year Period in the AFTT Study Area</TTITLE>
                        <BOXHD>
                            <CHED H="1">Stressor category</CHED>
                            <CHED H="1">Activity name</CHED>
                            <CHED H="1">Activity description</CHED>
                            <CHED H="1">Source bin</CHED>
                            <CHED H="1">
                                7-Year
                                <LI>number of</LI>
                                <LI>
                                    activities 
                                    <SU>1</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                Location 
                                <SU>2</SU>
                            </CHED>
                        </BOXHD>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Major Training Exercise—Large Integrated Anti-Submarine Warfare</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Composite Training Unit Exercise</ENT>
                            <ENT>Aircraft carrier and its associated aircraft integrate with surface and submarine units in a challenging multi-threat operational environment in order to certify them for deployment</ENT>
                            <ENT>ASW1, ASW2, ASW3, ASW4, ASW5, HF1, LF6, MF1, MF3, MF4, MF5, MF11, MF12</ENT>
                            <ENT>17</ENT>
                            <ENT>
                                VACAPES RC; Navy Cherry
                                <LI>Point RC; JAX RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Major Training Exercises—Medium Integrated Anti-Submarine Warfare</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Fleet Exercises/Sustainment Exercise</ENT>
                            <ENT>Aircraft carrier and its associated aircraft integrates with surface and submarine units in a challenging multi-threat operational environment in order to maintain their ability to deploy</ENT>
                            <ENT>ASW1, ASW2, ASW3, ASW4, HF1, LF6, MF1, MF3, MF4, MF5, MF11, MF12</ENT>
                            <ENT>
                                28
                                <LI>14</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Integrated/Coordinated Training—Small Integrated Anti-Submarine Warfare Training</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Naval Undersea Warfare Training Assessment Course</ENT>
                            <ENT>Multiple ships, aircraft, and submarines integrate the use of their sensors to search for, detect, classify, localize, and track a threat submarine in order to launch an exercise torpedo</ENT>
                            <ENT>ASW1, ASW3, ASW4, HF1, LF6, MF1, MF3, MF4, MF5, MF12</ENT>
                            <ENT>
                                42
                                <LI>21</LI>
                                <LI>21</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Integrated/Coordinated Training—Medium Coordinated Anti-Submarine Warfare Training</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Anti-Submarine Warfare Tactical Development Exercise</ENT>
                            <ENT>Surface ships, aircraft, and submarines coordinate to search for, detect, and track submarines</ENT>
                            <ENT>ASW1, ASW3, ASW4, HF1, LF6, MF1, MF3, MF4, MF5, MF11, MF12</ENT>
                            <ENT>
                                14
                                <LI>7</LI>
                                <LI>7</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Integrated/Coordinated Training—Small Coordinated Anti-Submarine Warfare Training</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Group Sail</ENT>
                            <ENT>Surface ships and helicopters search for, detect, and track threat submarines</ENT>
                            <ENT>ASW2, ASW3, ASW4, HF1, MF1, MF3, MF4, MF5, MF11, MF12</ENT>
                            <ENT>
                                28
                                <LI>28</LI>
                                <LI>35</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Amphibious Warfare</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Naval Surface Fire Support Exercise—At Sea</ENT>
                            <ENT>Surface ship crews use large-caliber guns to support forces ashore; however, the land target is simulated at sea. Rounds are scored by passive acoustic buoys located at or near the target area</ENT>
                            <ENT>E5</ENT>
                            <ENT>
                                28
                                <LI>84</LI>
                                <LI>14</LI>
                                <LI>266</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Anti-Submarine Warfare</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Anti-submarine Warfare Torpedo Exercise—Helicopter</ENT>
                            <ENT>Helicopter aircrews search for, track, and detect submarines. Recoverable air launched torpedoes are employed against submarine targets</ENT>
                            <ENT>MF4, MF5, TORP1</ENT>
                            <ENT>
                                98
                                <LI>28</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Anti-submarine Warfare Torpedo Exercise—Maritime Patrol Aircraft</ENT>
                            <ENT>Maritime patrol aircraft aircrews search for, track, and detect submarines. Recoverable air launched torpedoes are employed against submarine targets</ENT>
                            <ENT>MF5, TORP1</ENT>
                            <ENT>
                                98
                                <LI>28</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Anti-Submarine Warfare Torpedo Exercise—Ship</ENT>
                            <ENT>Surface ship crews search for, track, and detect submarines. Exercise torpedoes are used</ENT>
                            <ENT>ASW3, MF1, TORP1</ENT>
                            <ENT>
                                112
                                <LI>35</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Anti-Submarine Warfare Torpedo Exercise—Submarine</ENT>
                            <ENT>Submarine crews search for, track, and detect submarines. Exercise torpedoes are used</ENT>
                            <ENT>ASW4, HF1, MF3, TORP2</ENT>
                            <ENT>
                                84
                                <LI>42</LI>
                                <LI>14</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>Northeast RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Anti-Submarine Warfare Tracking Exercise—Helicopter</ENT>
                            <ENT>Helicopter aircrews search for, track, and detect submarines</ENT>
                            <ENT>MF4, MF5</ENT>
                            <ENT>
                                168
                                <LI>2,590</LI>
                                <LI>84</LI>
                                <LI>56</LI>
                            </ENT>
                            <ENT>
                                Other AFTT Areas.
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Anti-Submarine Warfare Tracking Exercise—Maritime Patrol Aircraft</ENT>
                            <ENT>Maritime patrol aircraft aircrews search for, track, and detect submarines</ENT>
                            <ENT>ASW5, ASW2, MF5</ENT>
                            <ENT>
                                630
                                <LI>1,232</LI>
                                <LI>3,675</LI>
                                <LI>322</LI>
                            </ENT>
                            <ENT>
                                Northeast RC.
                                <LI>VACAPES RC.</LI>
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <PRTPAGE P="21130"/>
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Anti-Submarine Warfare Tracking Exercise—Ship</ENT>
                            <ENT>Surface ship crews search for, track, and detect submarines</ENT>
                            <ENT>ASW1, ASW3, MF1, MF11, MF12</ENT>
                            <ENT>
                                * 35
                                <LI>* 770</LI>
                                <LI>* 35</LI>
                                <LI>* 3,080</LI>
                                <LI>* 385</LI>
                                <LI>* 1,540</LI>
                            </ENT>
                            <ENT>
                                Northeast RC.
                                <LI>Other AFTT Areas.</LI>
                                <LI>GOMEX RC.</LI>
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Anti-Submarine Warfare Tracking Exercise—Submarine</ENT>
                            <ENT>Submarine crews search for, track, and detect submarines</ENT>
                            <ENT>ASW4, HF1, MF3</ENT>
                            <ENT>
                                308
                                <LI>91</LI>
                                <LI>7</LI>
                                <LI>126</LI>
                                <LI>42</LI>
                            </ENT>
                            <ENT>
                                Other AFTT Areas.
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>Northeast RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Expeditionary Warfare</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Maritime Security Operations—Anti-Swimmer Grenades</ENT>
                            <ENT>Small boat crews engage in force protection activities by using anti-swimmer grenades to defend against hostile divers</ENT>
                            <ENT>E2</ENT>
                            <ENT>
                                14
                                <LI>14</LI>
                                <LI>14</LI>
                                <LI>28</LI>
                                <LI>35</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>Northeast RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Mine Warfare</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Airborne Mine Countermeasure—Mine Detection</ENT>
                            <ENT>Helicopter aircrews detect mines using towed or laser mine detection systems</ENT>
                            <ENT>HF4</ENT>
                            <ENT>
                                462
                                <LI>2,219</LI>
                                <LI>2,597</LI>
                                <LI>1,708</LI>
                                <LI>10,780</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>NSWC Panama City.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic, Explosive</ENT>
                            <ENT>Civilian Port Defense—Homeland Security Anti-Terrorism/Force Protection Exercise</ENT>
                            <ENT>Maritime security personnel train to protect civilian ports against enemy efforts to interfere with access to those ports</ENT>
                            <ENT>HF4, SAS2, E2, E4</ENT>
                            <ENT>4</ENT>
                            <ENT>Beaumont, TX; Boston, MA; Corpus Christi, TX; Delaware Bay, DE; Earle, NJ; GOMEX RC; Hampton Roads, VA; JAX RC; Kings Bay, GA; NS Mayport; Morehead City, NC; Port Canaveral, FL; Savannah, GA; Tampa Bay, FL; VACAPES RC; Wilmington, NC.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Coordinated Unit Level Helicopter Airborne Mine Countermeasure Exercise</ENT>
                            <ENT>A detachment of helicopter aircrews train as a unit in the use of airborne mine countermeasures, such as towed mine detection and neutralization systems</ENT>
                            <ENT>HF4</ENT>
                            <ENT>
                                14
                                <LI>14</LI>
                                <LI>14</LI>
                                <LI>14</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic, Explosive</ENT>
                            <ENT>Mine Countermeasures—Mine Neutralization—Remotely Operated Vehicle</ENT>
                            <ENT>Ship, small boat, and helicopter crews locate and disable mines using remotely operated underwater vehicles</ENT>
                            <ENT>HF4, E4</ENT>
                            <ENT>
                                924
                                <LI>497</LI>
                                <LI>497</LI>
                                <LI>4,410</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Mine Countermeasures—Ship Sonar</ENT>
                            <ENT>Ship crews detect and avoid mines while navigating restricted areas or channels using active sonar</ENT>
                            <ENT>HF4</ENT>
                            <ENT>
                                154
                                <LI>371</LI>
                                <LI>371</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Mine Neutralization—Explosive Ordnance Disposal</ENT>
                            <ENT>Personnel disable threat mines using explosive charges</ENT>
                            <ENT>E4, E5, E6, E7</ENT>
                            <ENT>
                                42
                                <LI>112</LI>
                                <LI>140</LI>
                                <LI>119</LI>
                                <LI>112</LI>
                                <LI>3,668</LI>
                            </ENT>
                            <ENT>
                                Lower Chesapeake Bay.
                                <LI>GOMEX RC.</LI>
                                <LI>JAX RC.</LI>
                                <LI>Key West RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Surface Warfare</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Bombing Exercise Air-to-Surface</ENT>
                            <ENT>Fixed-wing aircrews deliver bombs against surface targets</ENT>
                            <ENT>E9, E10, E12</ENT>
                            <ENT>
                                469
                                <LI>3,038</LI>
                                <LI>756</LI>
                                <LI>2,303</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Gunnery Exercise Surface-to-Surface Boat Medium-Caliber</ENT>
                            <ENT>Small boat crews fire medium-caliber guns at surface targets</ENT>
                            <ENT>E1</ENT>
                            <ENT>
                                42
                                <LI>182</LI>
                                <LI>896</LI>
                                <LI>14</LI>
                                <LI>1,820</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>Northeast RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Gunnery Exercise Surface-to-Surface Ship Large-Caliber</ENT>
                            <ENT>Surface ship crews fire large-caliber guns at surface targets</ENT>
                            <ENT>E3, E5</ENT>
                            <ENT>
                                70
                                <LI>63</LI>
                                <LI>357</LI>
                                <LI>245</LI>
                                <LI>525</LI>
                            </ENT>
                            <ENT>
                                Other AFTT Areas.
                                <LI>GOMEX RC.</LI>
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Gunnery Exercise Surface-to-Surface Ship Medium-Caliber</ENT>
                            <ENT>Surface ship crews fire medium-caliber guns at surface targets</ENT>
                            <ENT>E1</ENT>
                            <ENT>
                                287
                                <LI>231</LI>
                                <LI>1,127</LI>
                                <LI>504</LI>
                                <LI>2,247</LI>
                            </ENT>
                            <ENT>
                                Other AFTT Areas.
                                <LI>GOMEX RC.</LI>
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Integrated Live Fire Exercise</ENT>
                            <ENT>Naval forces defend against a swarm of surface threats (ships or small boats) with bombs, missiles, rockets, and small-, medium- , and large-caliber guns</ENT>
                            <ENT>E1, E3, E6, E10</ENT>
                            <ENT>
                                14
                                <LI>14</LI>
                            </ENT>
                            <ENT>
                                VACAPES RC.
                                <LI>JAX RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <PRTPAGE P="21131"/>
                            <ENT I="01">Explosive</ENT>
                            <ENT>Missile Exercise Air-to-Surface</ENT>
                            <ENT>Fixed-wing and helicopter aircrews fire air-to-surface missiles at surface targets</ENT>
                            <ENT>E6, E8, E10</ENT>
                            <ENT>
                                714
                                <LI>364</LI>
                                <LI>616</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Missile Exercise Air-to-Surface—Rocket</ENT>
                            <ENT>Helicopter aircrews fire both precision-guided and unguided rockets at surface targets</ENT>
                            <ENT>E3</ENT>
                            <ENT>
                                70
                                <LI>714</LI>
                                <LI>70</LI>
                                <LI>644</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Missile Exercise Surface-to-Surface</ENT>
                            <ENT>Surface ship crews defend against surface threats (ships or small boats) and engage them with missiles</ENT>
                            <ENT>E6, E10</ENT>
                            <ENT>
                                112
                                <LI>84</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic, Explosive</ENT>
                            <ENT>Sinking Exercise</ENT>
                            <ENT>Aircraft, ship, and submarine crews deliberately sink a seaborne target, usually a decommissioned ship (made environmentally safe for sinking according to U.S. Environmental Protection Agency standards), with a variety of munitions</ENT>
                            <ENT>TORP2, E5, E8, E9, E10, E11</ENT>
                            <ENT>7</ENT>
                            <ENT>SINKEX Box.</ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Other Training Activities</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Elevated Causeway System</ENT>
                            <ENT>A temporary pier is constructed off the beach. Supporting pilings are driven into the sand and then later removed</ENT>
                            <ENT>Impact hammer or vibratory extractor</ENT>
                            <ENT>
                                7
                                <LI>7</LI>
                            </ENT>
                            <ENT>
                                Lower Chesapeake Bay.
                                <LI>Navy Cherry Point RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Submarine Navigation</ENT>
                            <ENT>Submarine crews operate sonar for navigation and object detection while transiting into and out of port during reduced visibility</ENT>
                            <ENT>HF1, MF3</ENT>
                            <ENT>
                                1,183
                                <LI>21</LI>
                                <LI>21</LI>
                                <LI>588</LI>
                                <LI>161</LI>
                            </ENT>
                            <ENT>
                                NSB New London.
                                <LI>NSB Kings Bay.</LI>
                                <LI>NS Mayport.</LI>
                                <LI>NS Norfolk.</LI>
                                <LI>Port Canaveral, FL.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Submarine Sonar Maintenance</ENT>
                            <ENT>Maintenance of submarine sonar systems is conducted pierside or at sea</ENT>
                            <ENT>MF3</ENT>
                            <ENT>
                                84
                                <LI>462</LI>
                                <LI>63</LI>
                                <LI>14</LI>
                                <LI>238</LI>
                                <LI>602</LI>
                                <LI>14</LI>
                                <LI>88</LI>
                                <LI>326</LI>
                            </ENT>
                            <ENT>
                                Other AFTT Areas.
                                <LI>NSB New London.</LI>
                                <LI>JAX RC.</LI>
                                <LI>NSB Kings Bay.</LI>
                                <LI>NS Norfolk.</LI>
                                <LI>Northeast RC.</LI>
                                <LI>Port Canaveral, FL.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Submarine Under Ice Certification</ENT>
                            <ENT>Submarine crews train to operate under ice. Ice conditions are simulated during training and certification events</ENT>
                            <ENT>HF1</ENT>
                            <ENT>
                                21
                                <LI>21</LI>
                                <LI>63</LI>
                                <LI>63</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>Northeast RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Surface Ship Object Detection</ENT>
                            <ENT>Surface ship crews operate sonar for navigation and object detection while transiting in and out of port during reduced visibility</ENT>
                            <ENT>HF8, MF1K</ENT>
                            <ENT>
                                532
                                <LI>1,134</LI>
                            </ENT>
                            <ENT>
                                NS Mayport.
                                <LI>NS Norfolk.</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Surface Ship Sonar Maintenance</ENT>
                            <ENT>Maintenance of surface ship sonar systems is conducted pierside or at sea</ENT>
                            <ENT>HF8, MF1</ENT>
                            <ENT>
                                350
                                <LI>350</LI>
                                <LI>840</LI>
                                <LI>1,645</LI>
                                <LI>840</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>NS Mayport.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>NS Norfolk.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             The number of proposed training activities that could occur annually and the duration of those activities remains identical to those presented in Table 4 of the 2018 AFTT final rule.
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             Locations given are areas where activities typically occur. However, activities could be conducted in other locations within the Study Area. Where multiple locations are provided within a single cell, the number of activities could occur in any of the locations, not in each of the locations.
                        </TNOTE>
                        <TNOTE>* For Anti-Submarine Warfare Tracking Exercise—Ship, 50 percent of requirements are met through synthetic training or other training exercises.</TNOTE>
                        <TNOTE>
                            <E T="02">Notes:</E>
                             GOMEX: Gulf of Mexico; JAX: Jacksonville; NS: Naval Station; NSB: Naval Submarine Base; NSWC: Naval Surface Warfare Center; RC: Range Complex; VACAPES: Virginia Capes.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Proposed Testing Activities</HD>
                    <P>The number of proposed testing activities that could occur annually and the duration of those activities are identical to those presented in Tables 5 through 7 of the 2018 AFTT final rule, and are not repeated here. Similar to the 2017 Navy application, the Navy's proposed testing activities here are based on the level of testing activities anticipated to be conducted into the reasonably foreseeable future, with adjustments that account for changes in the types and tempo (increases or decreases) of testing activities to meet current and future military readiness requirements. The number of proposed testing activities that could occur for the seven-year period are presented in Tables 2 through 4. The number of ship shock trials for the seven-year period would remain the same as the number authorized under the 2018 AFTT final rule.</P>
                    <HD SOURCE="HD2">Naval Air Systems Command</HD>
                    <P>The proposed Naval Air Systems Command testing activities that could occur over the seven-year period within the AFTT Study Area are presented in Table 2.</P>
                    <GPOTABLE COLS="6" OPTS="L2,p6,6/7,i1" CDEF="xs60,r25,r75,r25,12,xs90">
                        <TTITLE>Table 2—Proposed Naval Air Systems Command Testing Activities Analyzed for Seven-Year Period in the AFTT Study Area</TTITLE>
                        <BOXHD>
                            <CHED H="1">Stressor category</CHED>
                            <CHED H="1">Activity name</CHED>
                            <CHED H="1">Activity description</CHED>
                            <CHED H="1">Source bin</CHED>
                            <CHED H="1">
                                7-Year
                                <LI>number of</LI>
                                <LI>
                                    activities 
                                    <SU>1</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                Location 
                                <SU>2</SU>
                            </CHED>
                        </BOXHD>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Anti-Submarine Warfare</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Anti-Submarine Warfare Torpedo Test</ENT>
                            <ENT>
                                This event is similar to the training event torpedo exercise. Test evaluates anti-submarine warfare systems onboard rotary-wing (
                                <E T="03">e.g.,</E>
                                 helicopter) and fixed-wing aircraft and the ability to search for, detect, classify, localize, track, and attack a submarine or similar target
                            </ENT>
                            <ENT>MF5, TORP1</ENT>
                            <ENT>
                                209
                                <LI>523</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <PRTPAGE P="21132"/>
                            <ENT I="01">Acoustic, Explosive</ENT>
                            <ENT>Anti-Submarine Warfare Tracking Test—Helicopter</ENT>
                            <ENT>This event is similar to the training event anti-submarine warfare tracking exercise—helicopter. The test evaluates the sensors and systems used to detect and track submarines and to ensure that helicopter systems used to deploy the tracking system perform to specifications</ENT>
                            <ENT>MF4, MF5, E3</ENT>
                            <ENT>
                                34
                                <LI>36</LI>
                                <LI>64</LI>
                                <LI>442</LI>
                                <LI>1,368</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>Key West RC.</LI>
                                <LI>Northeast RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic, Explosive</ENT>
                            <ENT>Anti-Submarine Warfare Tracking Test—Maritime Patrol Aircraft</ENT>
                            <ENT>The test evaluates the sensors and systems used by maritime patrol aircraft to detect and track submarines and to ensure that aircraft systems used to deploy the tracking systems perform to specifications and meet operational requirements</ENT>
                            <ENT>ASW2, ASW5, E1, E3, MF5, MF6</ENT>
                            <ENT>
                                85
                                <LI>133</LI>
                                <LI>76</LI>
                                <LI>101</LI>
                                <LI>279</LI>
                                <LI>175</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>Key West RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>Northeast RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Kilo Dip</ENT>
                            <ENT>Functional check of a helicopter deployed dipping sonar system prior to conducting a testing or training event using the dipping sonar system</ENT>
                            <ENT>MF4</ENT>
                            <ENT>
                                22
                                <LI>12</LI>
                                <LI>12</LI>
                                <LI>12</LI>
                                <LI>200</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>Key West RC.</LI>
                                <LI>Northeast RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic, Explosive</ENT>
                            <ENT>Sonobuoy Lot Acceptance Test</ENT>
                            <ENT>Sonobuoys are deployed from surface vessels and aircraft to verify the integrity and performance of a production lot or group of sonobuoys in advance of delivery to the fleet for operational use</ENT>
                            <ENT>ASW2, ASW5, HF5, HF6, LF4, MF5, MF6, E1, E3, E4</ENT>
                            <ENT>1,120</ENT>
                            <ENT>Key West RC.</ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Mine Warfare</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Airborne Dipping Sonar Minehunting Test</ENT>
                            <ENT>A mine-hunting dipping sonar system that is deployed from a helicopter and uses high-frequency sonar for the detection and classification of bottom and moored mines</ENT>
                            <ENT>HF4</ENT>
                            <ENT>
                                144
                                <LI>66</LI>
                            </ENT>
                            <ENT>
                                NSWC Panama City.
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Airborne Mine Neutralization System Test</ENT>
                            <ENT>A test of the airborne mine neutralization system evaluates the system's ability to detect and destroy mines from an airborne mine countermeasures capable helicopter. The airborne mine neutralization system uses up to four unmanned underwater vehicles equipped with high-frequency sonar, video cameras, and explosive and non-explosive neutralizers</ENT>
                            <ENT>E4</ENT>
                            <ENT>
                                154
                                <LI>215</LI>
                            </ENT>
                            <ENT>
                                NSWC Panama City.
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Airborne Sonobuoy Minehunting Test</ENT>
                            <ENT>A mine-hunting system made up of a field of sonobuoys deployed by a helicopter. A field of sonobuoys, using high-frequency sonar, is used to detect and classify bottom and moored mines</ENT>
                            <ENT>HF6</ENT>
                            <ENT>
                                364
                                <LI>168</LI>
                            </ENT>
                            <ENT>
                                NSWC Panama City.
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Surface Warfare</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Air-to-Surface Bombing Test</ENT>
                            <ENT>This event is similar to the training event bombing exercise air-to-surface. Fixed-wing aircraft test the delivery of bombs against surface maritime targets with the goal of evaluating the bomb, the bomb carry and delivery system, and any associated systems that may have been newly developed or enhanced</ENT>
                            <ENT>E9</ENT>
                            <ENT>140</ENT>
                            <ENT>VACAPES RC.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Air-to-Surface Gunnery Test</ENT>
                            <ENT>This event is similar to the training event gunnery exercise air-to-surface. Fixed-wing and rotary-wing aircrews evaluate new or enhanced aircraft guns against surface maritime targets to test that the guns, gun ammunition, or associated systems meet required specifications or to train aircrews in the operation of a new or enhanced weapon system</ENT>
                            <ENT>E1</ENT>
                            <ENT>
                                295
                                <LI>890</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Air-to-Surface Missile Test</ENT>
                            <ENT>This event is similar to the training event missile exercise air-to-surface. Test may involve both fixed-wing and rotary-wing aircraft launching missiles at surface maritime targets to evaluate the weapon system or as part of another system's integration test</ENT>
                            <ENT>E6, E9, E10</ENT>
                            <ENT>
                                30
                                <LI>234</LI>
                                <LI>928</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Rocket Test</ENT>
                            <ENT>Rocket tests evaluate the integration, accuracy, performance, and safe separation of guided and unguided 2.75-inch rockets fired from a hovering or forward-flying helicopter</ENT>
                            <ENT>E3</ENT>
                            <ENT>
                                121
                                <LI>233</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Other Testing Activities</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Undersea Range System Test</ENT>
                            <ENT>Following installation of a Navy underwater warfare training and testing range, tests of the nodes (components of the range) will be conducted to include node surveys and testing of node transmission functionality</ENT>
                            <ENT>MF9, BB4</ENT>
                            <ENT>66</ENT>
                            <ENT>JAX RC.</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             The number of proposed testing activities that could occur annually and the duration of those activities are identical to those presented in Table 5 of the 2018 AFTT final rule.
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             Locations given are areas where activities typically occur. However, activities could be conducted in other locations within the Study Area.
                        </TNOTE>
                        <TNOTE>
                            <E T="02">Notes:</E>
                             GOMEX: Gulf of Mexico; JAX: Jacksonville; NSWC: Naval Surface Warfare Center; RC: Range Complex; VACAPES: Virginia Capes.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD2">Naval Sea Systems Command</HD>
                    <P>
                        The proposed Naval Sea Systems Command testing activities that could occur over the seven-year period within the AFTT Study Area are presented in Table 3.
                        <PRTPAGE P="21133"/>
                    </P>
                    <GPOTABLE COLS="6" OPTS="L2,p6,6/7,i1" CDEF="xs60,r25,r75,r25,12,xs90">
                        <TTITLE>Table 3—Proposed Naval Sea Systems Command Testing Activities Analyzed for Seven-Year Period in the AFTT Study Area.</TTITLE>
                        <BOXHD>
                            <CHED H="1">Stressor category</CHED>
                            <CHED H="1">Activity name</CHED>
                            <CHED H="1">Activity description</CHED>
                            <CHED H="1">Source bin</CHED>
                            <CHED H="1">
                                7-Year 
                                <LI>number of </LI>
                                <LI>
                                    activities 
                                    <SU>1</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                Location 
                                <SU>2</SU>
                            </CHED>
                        </BOXHD>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Anti-Submarine Warfare</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Anti-Submarine Warfare Mission Package Testing</ENT>
                            <ENT>
                                Ships and their supporting platforms (
                                <E T="03">e.g.,</E>
                                 helicopters, unmanned aerial systems) detect, localize, and attack submarines
                            </ENT>
                            <ENT>ASW1, ASW2, ASW3, ASW5, MF1, MF4, MF5, MF12, TORP1</ENT>
                            <ENT>
                                294
                                <LI>28</LI>
                                <LI>28</LI>
                                <LI>182</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>Newport, RI.</LI>
                                <LI>NUWC Newport.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Acoustic</ENT>
                            <ENT>At-Sea Sonar Testing</ENT>
                            <ENT>At-sea testing to ensure systems are fully functional in an open ocean environment</ENT>
                            <ENT>ASW3, ASW4, HF1, LF5, M3, MF1, MF1K, MF3, MF5, MF9, MF11, TORP2</ENT>
                            <ENT>14</ENT>
                            <ENT>JAX RC; Navy Cherry Point RC; Northeast RC; VACAPES RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>7</ENT>
                            <ENT>JAX RC; Navy Cherry Point RC; VACAPES RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>14</ENT>
                            <ENT>offshore Fort Pierce, FL; GOMEX RC; JAX RC; SFOMF; Northeast RC; VACAPES RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>28</ENT>
                            <ENT>JAX RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>14</ENT>
                            <ENT>Navy Cherry Point RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>56</ENT>
                            <ENT>NUWC Newport.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>84</ENT>
                            <ENT>VACAPES RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Pierside Sonar Testing</ENT>
                            <ENT>Pierside testing to ensure systems are fully functional in a controlled pierside environment prior to at-sea test activities</ENT>
                            <ENT>ASW3, HF1, HF3, HF8, M3, MF1, MF1K, MF3, MF9, MF10</ENT>
                            <ENT>7</ENT>
                            <ENT>NSB New London; NS Norfolk; Port Canaveral, FL</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>77</ENT>
                            <ENT>Bath, ME.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>35</ENT>
                            <ENT>NSB New London.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>28</ENT>
                            <ENT>NSB Kings Bay.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>56</ENT>
                            <ENT>Newport, RI.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>91</ENT>
                            <ENT>NS Norfolk.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>14</ENT>
                            <ENT>Pascagoula, MS.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>21</ENT>
                            <ENT>Port Canaveral, FL.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>14</ENT>
                            <ENT>PNS.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Submarine Sonar Testing/Maintenance</ENT>
                            <ENT>Pierside testing of submarine systems occurs periodically following major maintenance periods and for routine maintenance</ENT>
                            <ENT>HF1, HF3, M3, MF3</ENT>
                            <ENT>
                                112
                                <LI>168</LI>
                            </ENT>
                            <ENT>
                                Norfolk, VA.
                                <LI>PNS.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Surface Ship Sonar Testing/Maintenance</ENT>
                            <ENT>Pierside and at-sea testing of ship systems occur periodically following major maintenance periods and for routine maintenance</ENT>
                            <ENT>ASW3, MF1, MF1K, MF9, MF10</ENT>
                            <ENT>
                                7
                                <LI>7</LI>
                                <LI>21</LI>
                                <LI>21</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>NS Mayport.</LI>
                                <LI>NS Norfolk.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Acoustic, Explosive</ENT>
                            <ENT>Torpedo (Explosive) Testing</ENT>
                            <ENT>Air, surface, or submarine crews employ explosive and non-explosive torpedoes against artificial targets</ENT>
                            <ENT>ASW3, HF1, HF5, HF6, MF1, MF3, MF4, MF5, MF6, TORP1, TORP2, E8, E11</ENT>
                            <ENT>28</ENT>
                            <ENT>GOMEX RC; offshore Fort Pierce, FL; Key West RC; Navy Cherry Point RC; Northeast RC; VACAPES RC.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>14</ENT>
                            <ENT>GOMEX RC; JAX RC; Northeast RC; VACAPES RC.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Torpedo (Non-Explosive) Testing</ENT>
                            <ENT>Air, surface, or submarine crews employ non-explosive torpedoes against submarines or surface vessels. When performed on a testing range, these torpedoes may be launched from a range craft or fixed structures and may use artificial targets</ENT>
                            <ENT>ASW3, ASW4, HF1, HF6, MF1, MF3, MF4, MF5, MF6, TORP1, TORP2, TORP 3</ENT>
                            <ENT>
                                49
                                <LI>77 </LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>offshore Fort Pierce, FL. </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>12</ENT>
                            <ENT>JAX, RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>49</ENT>
                            <ENT>Navy Cherry Point RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>54</ENT>
                            <ENT>Northeast RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>210</ENT>
                            <ENT>NUWC Newport.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>77</ENT>
                            <ENT>VACAPES RC.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Countermeasure Testing</ENT>
                            <ENT>Countermeasure testing involves the testing of systems that will detect, localize, track, and attack incoming weapons including marine vessel targets. Testing includes surface ship torpedo defense systems and marine vessel stopping payloads</ENT>
                            <ENT>ASW3, HF5, TORP1, TORP2</ENT>
                            <ENT>35</ENT>
                            <ENT>GOMEX RC; JAX RC; NUWC Newport; VACAPES RC; Key West RC. </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>20</ENT>
                            <ENT>GOMEX RC; JAX RC; Northeast RC; VACAPES RC.</ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Mine Warfare</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Acoustic, Explosive</ENT>
                            <ENT>Mine Countermeasure and Neutralization Testing</ENT>
                            <ENT>Air, surface, and subsurface vessels neutralize threat mines and mine-like objects</ENT>
                            <ENT>E4, E11</ENT>
                            <ENT>
                                91
                                <LI>42</LI>
                            </ENT>
                            <ENT>
                                NSWC Panama City.
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic, Explosive</ENT>
                            <ENT>Mine Countermeasure Mission Package Testing</ENT>
                            <ENT>Vessels and associated aircraft conduct mine countermeasure operations</ENT>
                            <ENT>HF4, SAS2, E4</ENT>
                            <ENT>
                                133
                                <LI>70</LI>
                                <LI>77</LI>
                                <LI>14</LI>
                                <LI>35</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>NSWC Panama City.</LI>
                                <LI>SFOMF.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Mine Detection and Classification Testing</ENT>
                            <ENT>Air, surface, and subsurface vessels and systems detect, classify, and avoid mines and mine-like objects. Vessels also assess their potential susceptibility to mines and mine-like objects</ENT>
                            <ENT>HF1, HF4, HF8, MF1, MF1K, MF9</ENT>
                            <ENT>
                                42
                                <LI>70 </LI>
                            </ENT>
                            <ENT>
                                GOMEX RC. 
                                <LI>Navy Cherry Point RC. </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>359</ENT>
                            <ENT>NSWC Panama City.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>66</ENT>
                            <ENT>Riviera Beach, FL.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>28</ENT>
                            <ENT>SFOMF.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <PRTPAGE P="21134"/>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>21</ENT>
                            <ENT>VACAPES RC.</ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Surface Warfare</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Gun Testing—Large Caliber</ENT>
                            <ENT>Crews defend against targets with large-caliber guns</ENT>
                            <ENT>E3, E5</ENT>
                            <ENT>84</ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>Key West RC.</LI>
                                <LI>Navy Cherry Point RC.</LI>
                                <LI>Northeast RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>7</ENT>
                            <ENT>GOMEX RC;</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>7</ENT>
                            <ENT>JAX RC;</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>7</ENT>
                            <ENT>Key West RC;</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>7</ENT>
                            <ENT>Navy Cherry Point RC;</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>7</ENT>
                            <ENT>Northeast RC;</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>231</ENT>
                            <ENT>NSWC Panama City.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>35</ENT>
                            <ENT>VACAPES RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Explosive</ENT>
                            <ENT>Gun Testing—Medium-Caliber</ENT>
                            <ENT>Airborne and surface crews defend against targets with medium-caliber guns</ENT>
                            <ENT>E1</ENT>
                            <ENT>84</ENT>
                            <ENT>GOMEX RC; JAX RC; Key West RC; Navy Cherry Point RC; Northeast RC; VACAPES RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>
                                714
                                <LI>34</LI>
                            </ENT>
                            <ENT>
                                NSWC Panama City.
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Explosive</ENT>
                            <ENT>Missile and Rocket Testing</ENT>
                            <ENT>Missile and rocket testing includes various missiles or rockets fired from submarines and surface combatants. Testing of the launching system and ship defense is performed</ENT>
                            <ENT>E6, E10</ENT>
                            <ENT>91</ENT>
                            <ENT>GOMEX RC; JAX RC; Key West RC; Navy Cherry Point RC; Northeast RC; VACAPES RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>7</ENT>
                            <ENT>GOMEX RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>14</ENT>
                            <ENT>JAX RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>35</ENT>
                            <ENT>Northeast RC.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>154</ENT>
                            <ENT>VACAPES RC.</ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Unmanned Systems</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Acoustic, Explosive</ENT>
                            <ENT>Unmanned Underwater Vehicle Testing</ENT>
                            <ENT>Testing involves the development or upgrade of unmanned underwater vehicles. This may include testing of mine detection capabilities, evaluating the basic functions of individual platforms, or complex events with multiple vehicles</ENT>
                            <ENT>ASW4, FLS2, HF1, HF4, HF5, HF6, HF7, LF5, MF9, MF10, SAS1, SA2, SAS3, VHF1, E8</ENT>
                            <ENT>112 </ENT>
                            <ENT>GOMEX RC; JAX RC; NUWC Newport.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>287</ENT>
                            <ENT>GOMEX RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>175</ENT>
                            <ENT>JAX RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>1,018  </ENT>
                            <ENT>NSWC Panama City.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>2,158  </ENT>
                            <ENT>NUWC Newport.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>63</ENT>
                            <ENT>Riviera Beach, FL.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>294</ENT>
                            <ENT>SFOMF.</ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Vessel Evaluation</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Large Ship Shock Trial</ENT>
                            <ENT>Underwater detonations are used to test new ships or major upgrades</ENT>
                            <ENT>E17</ENT>
                            <ENT>1</ENT>
                            <ENT>GOMEX RC; JAX RC; VACAPES RC.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Surface Warfare Testing</ENT>
                            <ENT>Tests capability of shipboard sensors to detect, track, and engage surface targets. Testing may include ships defending against surface targets using explosive and non-explosive rounds, gun system structural test firing and demonstration of the response to Call for Fire against land-based targets (simulated by sea-based locations)</ENT>
                            <ENT>E1, E5, E8</ENT>
                            <ENT>
                                14
                                <LI>91</LI>
                                <LI>7</LI>
                                <LI>70</LI>
                                <LI>63</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>JAX RC.</LI>
                                <LI>Key West RC.</LI>
                                <LI>Northeast RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Undersea Warfare Testing</ENT>
                            <ENT>Ships demonstrate capability of countermeasure systems and underwater surveillance, weapons engagement, and communications systems. This tests ships' ability to detect, track, and engage underwater targets</ENT>
                            <ENT>ASW3, ASW4, HF4, HF8, MF1, MF1K, MF4, MF5, MF9, MF10, TORP1, TORP2</ENT>
                            <ENT>14</ENT>
                            <ENT>JAX RC; VACAPES RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>6</ENT>
                            <ENT>JAX RC; Navy Cherry Point RC; SFOMF; VACAPES RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>14</ENT>
                            <ENT>GOMEX RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>42</ENT>
                            <ENT>JAX RC.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>14</ENT>
                            <ENT>VACAPES RC.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Explosive</ENT>
                            <ENT>Small Ship Shock Trial</ENT>
                            <ENT>Underwater detonations are used to test new ships or major upgrades</ENT>
                            <ENT>E16</ENT>
                            <ENT>3</ENT>
                            <ENT>JAX RC; VACAPES RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Submarine Sea Trials—Weapons System Testing</ENT>
                            <ENT>Submarine weapons and sonar systems are tested at-sea to meet integrated combat system certification requirements</ENT>
                            <ENT>HF1, M3, MF3, MF9, MF10, TORP2</ENT>
                            <ENT>14</ENT>
                            <ENT>Offshore Fort Pierce, FL; GOMEX RC; JAX RC; SFOMF; Northeast RC; VACAPES RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>28</ENT>
                            <ENT>JAX RC.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>28</ENT>
                            <ENT>Northeast RC.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>28</ENT>
                            <ENT>VACAPES RC.</ENT>
                        </ROW>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Other Testing Activities</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Insertion/Extraction</ENT>
                            <ENT>Testing of submersibles capable of inserting and extracting personnel and payloads into denied areas from strategic distances</ENT>
                            <ENT>MF3, MF9</ENT>
                            <ENT>
                                28
                                <LI>1,848</LI>
                            </ENT>
                            <ENT>
                                Key West RC. 
                                <LI>NSWC Panama City.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Acoustic Component Testing</ENT>
                            <ENT>Various surface vessels, moored equipment, and materials are tested to evaluate performance in the marine environment</ENT>
                            <ENT>FLS2, HF5, HF7, LF5, MF9, SAS2</ENT>
                            <ENT>231</ENT>
                            <ENT>SFOMF.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <PRTPAGE P="21135"/>
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Semi-Stationary Equipment Testing</ENT>
                            <ENT>
                                Semi-stationary equipment (
                                <E T="03">e.g.,</E>
                                 hydrophones) is deployed to determine functionality
                            </ENT>
                            <ENT>AG, ASW3, ASW4, HF5, HF6, LF4, LF5, MF9, MF10, SD1, SD2</ENT>
                            <ENT>
                                28
                                <LI>77</LI>
                                <LI>1,330</LI>
                            </ENT>
                            <ENT>
                                Newport, RI.
                                <LI>NSWC Panama City.</LI>
                                <LI>NUWC Newport.</LI>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Towed Equipment Testing</ENT>
                            <ENT>Surface vessels or unmanned surface vehicles deploy and tow equipment to determine functionality of towed systems</ENT>
                            <ENT>HF6, LF4, MF9</ENT>
                            <ENT>252</ENT>
                            <ENT>NUWC Newport.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Signature Analysis Operations</ENT>
                            <ENT>Surface ship and submarine testing of electromagnetic, acoustic, optical, and radar signature measurements</ENT>
                            <ENT>ASW2, HF1, LF4, LF5, LF6, M3, MF9, MF10</ENT>
                            <ENT>
                                7
                                <LI>413</LI>
                            </ENT>
                            <ENT>
                                JAX RC. 
                                <LI>SFOMF.</LI>
                            </ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             The number of proposed testing activities that could occur annually and the duration of those activities are identical to those presented in Table 6 of the 2018 AFTT final rule.
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             Locations given are areas where activities typically occur. However, activities could be conducted in other locations within the Study Area. Where multiple locations are provided within a single cell, the number of activities could occur in any of the locations, not in each of the locations.
                        </TNOTE>
                        <TNOTE>
                            <E T="02">Notes:</E>
                             JEB LC-FS: Joint Expeditionary Base Little Creek-Fort Story; NS: Naval Station; NSB: Naval Submarine Base; NSWC: Naval Surface Warfare Center; NUWC: Naval Undersea Warfare Center; PNS: Portsmouth Naval Shipyard; SFOMF: South Florida Ocean Measurement Facility Testing Range.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD2">Office of Naval Research</HD>
                    <P>The proposed Office of Naval Research testing activities that could occur over the seven-year period within the AFTT Study Area are presented in Table 4.</P>
                    <GPOTABLE COLS="6" OPTS="L2,nj,p6,6/7,i1" CDEF="xs60,r50,r100,r50,9,xs60">
                        <TTITLE>Table 4—Proposed Office of Naval Research Testing Activities Analyzed for Seven-Year Period in the AFTT Study Area</TTITLE>
                        <BOXHD>
                            <CHED H="01">Stressor category</CHED>
                            <CHED H="01">Activity name</CHED>
                            <CHED H="01">Activity description</CHED>
                            <CHED H="01">Source bin</CHED>
                            <CHED H="01">
                                7-Year 
                                <LI>number of </LI>
                                <LI>
                                    activities 
                                    <SU>1</SU>
                                </LI>
                            </CHED>
                            <CHED H="01">Location</CHED>
                        </BOXHD>
                        <ROW EXPSTB="05" RUL="s">
                            <ENT I="21">
                                <E T="02">Acoustic and Oceanographic Science and Technology</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Acoustic, Explosive</ENT>
                            <ENT>Acoustic and Oceanographic Research</ENT>
                            <ENT>Research using active transmissions from sources deployed from ships and unmanned underwater vehicles. Research sources can be used as proxies for current and future Navy systems</ENT>
                            <ENT>AG, ASW2, BB4, BB5, BB6, BB7, LF3, LF4, LF5, MF8, MF9, MF14, E1</ENT>
                            <ENT>
                                30
                                <LI>60</LI>
                                <LI>16</LI>
                                <LI>14</LI>
                            </ENT>
                            <ENT>
                                GOMEX RC.
                                <LI>Northeast RC.</LI>
                                <LI>VACAPES RC.</LI>
                                <LI>Other AFTT Areas.</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Acoustic</ENT>
                            <ENT>Emerging Mine Countermeasure Technology Research</ENT>
                            <ENT>Test involves the use of broadband acoustic sources on unmanned underwater vehicles</ENT>
                            <ENT>BB1, BB2, SAS4</ENT>
                            <ENT>
                                7
                                <LI>14</LI>
                                <LI>7</LI>
                            </ENT>
                            <ENT>
                                JAX RC.
                                <LI>Northeast RC.</LI>
                                <LI>VACAPES RC.</LI>
                            </ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             The number of proposed testing activities that could occur annually and the duration of those activities are identical to those presented in Table 7 of the 2018 AFTT final rule.
                        </TNOTE>
                        <TNOTE>
                            <E T="02">Notes:</E>
                             GOMEX: Gulf of Mexico; JAX: Jacksonville, Florida; RC: Range Complex; VACAPES: Virginia Capes.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD2">Summary of Acoustic and Explosive Sources Analyzed for Training and Testing</HD>
                    <P>Tables 5 through 8 show the acoustic source classes and numbers, explosive source bins and numbers, airgun sources, and pile driving and removal activities associated with the Navy's proposed training and testing activities over a seven-year period in the AFTT Study Area that were analyzed in the 2019 Navy application and for this proposed rule. The annual numbers for acoustic source classes, explosive source bins, and airgun sources, as well as the annual pile driving and removal activities associated with Navy training and testing activities in the AFTT Study Area are identical to those presented in Tables 8 through 11 of the 2018 AFTT final rule, and are not repeated here. Consistent with the periodicity in the 2018 AFTT final rule, the Navy proposes the addition of two pile driving/extraction activities for each of the two additional years.</P>
                    <P>
                        Table 5 describes the acoustic source classes (
                        <E T="03">i.e.,</E>
                         low-frequency (LF), mid-frequency (MF), and high-frequency (HF)) that could occur over seven years under the proposed training and testing activities. Acoustic source bin use in the proposed activities would vary annually. The seven-year totals for the proposed training and testing activities take into account that annual variability.
                    </P>
                    <GPOTABLE COLS="6" OPTS="L2,nj,i1" CDEF="s50,xls48,r50,6C,12,12">
                        <TTITLE>Table 5—Acoustic Source Classes Analyzed and Number Used for Seven-Year Period for Training and Testing Activities in the AFTT Study Area</TTITLE>
                        <BOXHD>
                            <CHED H="1">Source class category</CHED>
                            <CHED H="1">Bin</CHED>
                            <CHED H="1">Description</CHED>
                            <CHED H="1">
                                Unit 
                                <SU>1</SU>
                            </CHED>
                            <CHED H="1">
                                7-Year total 
                                <SU>2</SU>
                            </CHED>
                            <CHED H="2">Training</CHED>
                            <CHED H="2">Testing</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Low-Frequency (LF):</E>
                                 Sources that produce signals less than 1 kHz
                            </ENT>
                            <ENT>
                                LF3
                                <LI>LF4</LI>
                            </ENT>
                            <ENT>
                                LF sources greater than 200 dB
                                <LI>LF sources equal to 180 dB and up to 200 dB</LI>
                            </ENT>
                            <ENT>
                                H
                                <LI>H</LI>
                                <LI>C</LI>
                            </ENT>
                            <ENT>
                                0
                                <LI>0</LI>
                                <LI>0</LI>
                            </ENT>
                            <ENT>
                                9,156
                                <LI>6,797</LI>
                                <LI>140</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>LF5</ENT>
                            <ENT>LF sources less than 180 dB</ENT>
                            <ENT>H</ENT>
                            <ENT>60</ENT>
                            <ENT>12,264</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>LF6</ENT>
                            <ENT>LF sources greater than 200 dB with long pulse lengths</ENT>
                            <ENT>H</ENT>
                            <ENT>1,104</ENT>
                            <ENT>280</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Mid-Frequency (MF):</E>
                                 Tactical and non-tactical sources that produce signals between 1-10 kHz
                            </ENT>
                            <ENT>MF1</ENT>
                            <ENT>
                                Hull-mounted surface ship sonars (
                                <E T="03">e.g.,</E>
                                 AN/SQS-53C and AN/SQS-61)
                            </ENT>
                            <ENT>H</ENT>
                            <ENT>36,833</ENT>
                            <ENT>23,358</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>MF1K</ENT>
                            <ENT>Kingfisher mode associated with MF1 sonars</ENT>
                            <ENT>H</ENT>
                            <ENT>819</ENT>
                            <ENT>1,064</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="21136"/>
                            <ENT I="22"> </ENT>
                            <ENT>MF3</ENT>
                            <ENT>
                                Hull-mounted submarine sonars (
                                <E T="03">e.g.,</E>
                                 AN/BQQ-10)
                            </ENT>
                            <ENT>H</ENT>
                            <ENT>14,604</ENT>
                            <ENT>8,799</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>MF4</ENT>
                            <ENT>
                                Helicopter-deployed dipping sonars (
                                <E T="03">e.g.,</E>
                                 AN/AQS-22 and AN/AQS-13)
                            </ENT>
                            <ENT>H</ENT>
                            <ENT>4,196</ENT>
                            <ENT>3,797</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>MF5</ENT>
                            <ENT>
                                Active acoustic sonobuoys (
                                <E T="03">e.g.,</E>
                                 DICASS)
                            </ENT>
                            <ENT>C</ENT>
                            <ENT>47,340</ENT>
                            <ENT>38,663</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>MF6</ENT>
                            <ENT>
                                Active underwater sound signal devices (
                                <E T="03">e.g.,</E>
                                 MK84)
                            </ENT>
                            <ENT>C</ENT>
                            <ENT>0</ENT>
                            <ENT>8,986</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>MF8</ENT>
                            <ENT>Active sources (greater than 200 dB) not otherwise binned</ENT>
                            <ENT>H</ENT>
                            <ENT>0</ENT>
                            <ENT>2,436</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">High-Frequency (HF):</E>
                                 Tactical and non-tactical sources that produce signals between 10-100 kHz
                            </ENT>
                            <ENT>MF9</ENT>
                            <ENT>Active sources (equal to 180 dB and up to 200 dB) not otherwise binned</ENT>
                            <ENT>H</ENT>
                            <ENT>0</ENT>
                            <ENT>52,128</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>MF10</ENT>
                            <ENT>Active sources (greater than 160 dB, but less than 180 dB) not otherwise binned</ENT>
                            <ENT>H</ENT>
                            <ENT>6,088</ENT>
                            <ENT>39,830</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>MF11</ENT>
                            <ENT>Hull-mounted surface ship sonars with an active duty cycle greater than 80%</ENT>
                            <ENT>H</ENT>
                            <ENT>6,495</ENT>
                            <ENT>9,968</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>MF12</ENT>
                            <ENT>Towed array surface ship sonars with an active duty cycle greater than 80%</ENT>
                            <ENT>H</ENT>
                            <ENT>2,658</ENT>
                            <ENT>9,716</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>MF14</ENT>
                            <ENT>Oceanographic MF sonar</ENT>
                            <ENT>H</ENT>
                            <ENT>0</ENT>
                            <ENT>10,080</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>HF1</ENT>
                            <ENT>
                                Hull-mounted submarine sonars (
                                <E T="03">e.g.,</E>
                                 AN/BQQ-10)
                            </ENT>
                            <ENT>H</ENT>
                            <ENT>13,504</ENT>
                            <ENT>2,772</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>HF3</ENT>
                            <ENT>Other hull-mounted submarine sonars (classified)</ENT>
                            <ENT>H</ENT>
                            <ENT>34,275</ENT>
                            <ENT>215</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>HF4</ENT>
                            <ENT>
                                Mine detection, classification, and neutralization sonar (
                                <E T="03">e.g.,</E>
                                 AN/SQS-20)
                            </ENT>
                            <ENT>H</ENT>
                            <ENT>41,717</ENT>
                            <ENT>179,516</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>HF5</ENT>
                            <ENT>Active sources (greater than 200 dB) not otherwise binned</ENT>
                            <ENT>
                                H
                                <LI>C</LI>
                            </ENT>
                            <ENT>
                                0
                                <LI>0</LI>
                            </ENT>
                            <ENT>
                                13,624
                                <LI>280</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>HF6</ENT>
                            <ENT>Active sources (equal to 180 dB and up to 200 dB) not otherwise binned</ENT>
                            <ENT>H</ENT>
                            <ENT>0</ENT>
                            <ENT>15,254</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>HF7</ENT>
                            <ENT>Active sources (greater than 160 dB, but less than 180 dB) not otherwise binned</ENT>
                            <ENT>H</ENT>
                            <ENT>0</ENT>
                            <ENT>8,568</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>HF8</ENT>
                            <ENT>
                                Hull-mounted surface ship sonars (
                                <E T="03">e.g.,</E>
                                 AN/SQS-61)
                            </ENT>
                            <ENT>H</ENT>
                            <ENT>140</ENT>
                            <ENT>14,587</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">
                                <E T="03">Very High-Frequency Sonars (VHF):</E>
                                 Non-tactical sources that produce signals between 100-200 kHz
                            </ENT>
                            <ENT>VHF1</ENT>
                            <ENT>VHF sources greater than 200 dB</ENT>
                            <ENT>H</ENT>
                            <ENT>0</ENT>
                            <ENT>84</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">
                                <E T="03">Anti-Submarine Warfare (ASW):</E>
                                 Tactical sources (
                                <E T="03">e.g.,</E>
                                 active sonobuoys and acoustic counter-measures systems) used during ASW training and testing activities
                            </ENT>
                            <ENT>
                                ASW1
                                <LI>ASW2</LI>
                            </ENT>
                            <ENT>
                                MF systems operating above 200 dB
                                <LI>
                                    MF Multistatic Active Coherent sonobuoy (
                                    <E T="03">e.g.,</E>
                                     AN/SSQ-125)
                                </LI>
                            </ENT>
                            <ENT>
                                H
                                <LI>C</LI>
                            </ENT>
                            <ENT>
                                4,251
                                <LI>10,572</LI>
                            </ENT>
                            <ENT>
                                5,740
                                <LI>35,842</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>ASW3</ENT>
                            <ENT>
                                MF towed active acoustic countermeasure systems (
                                <E T="03">e.g.,</E>
                                 AN/SLQ-25)
                            </ENT>
                            <ENT>H</ENT>
                            <ENT>34,275</ENT>
                            <ENT>21,737</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>ASW4</ENT>
                            <ENT>
                                MF expendable active acoustic device countermeasures (
                                <E T="03">e.g.,</E>
                                 MK 3)
                            </ENT>
                            <ENT>C</ENT>
                            <ENT>2,994</ENT>
                            <ENT>24,043</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>ASW5</ENT>
                            <ENT>MF sonobuoys with high duty cycles</ENT>
                            <ENT>H</ENT>
                            <ENT>4,244</ENT>
                            <ENT>4,316</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">
                                <E T="03">Torpedoes (TORP):</E>
                                 Source classes associated with the active acoustic signals produced by torpedoes
                            </ENT>
                            <ENT>TORP1</ENT>
                            <ENT>
                                Lightweight torpedo (
                                <E T="03">e.g.,</E>
                                 MK 46, MK 54, or Anti-Torpedo Torpedo)
                            </ENT>
                            <ENT>C</ENT>
                            <ENT>399</ENT>
                            <ENT>6,122</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>TORP2</ENT>
                            <ENT>
                                Heavyweight torpedo (
                                <E T="03">e.g.,</E>
                                 MK 48)
                            </ENT>
                            <ENT>C</ENT>
                            <ENT>560</ENT>
                            <ENT>2,600</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>TORP3</ENT>
                            <ENT>
                                Heavyweight torpedo (
                                <E T="03">e.g.,</E>
                                 MK 48)
                            </ENT>
                            <ENT>C</ENT>
                            <ENT>0</ENT>
                            <ENT>640</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">
                                <E T="03">Forward Looking Sonar (FLS):</E>
                                 Forward or upward looking object avoidance sonars used for ship navigation and safety
                            </ENT>
                            <ENT>FLS2</ENT>
                            <ENT>HF sources with short pulse lengths, narrow beam widths, and focused beam patterns</ENT>
                            <ENT>H</ENT>
                            <ENT>0</ENT>
                            <ENT>8,568</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">
                                <E T="03">Acoustic Modems (M):</E>
                                 Systems used to transmit data through the water
                            </ENT>
                            <ENT>M3</ENT>
                            <ENT>MF acoustic modems (greater than 190 dB)</ENT>
                            <ENT>H</ENT>
                            <ENT>0</ENT>
                            <ENT>4,436</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <PRTPAGE P="21137"/>
                            <ENT I="01">
                                <E T="03">Swimmer Detection Sonars (SD):</E>
                                 Systems used to detect divers and sub- merged swimmers
                            </ENT>
                            <ENT>SD1-SD2</ENT>
                            <ENT>HF and VHF sources with short pulse lengths, used for the detection of swimmers and other objects for the purpose of port security</ENT>
                            <ENT>H</ENT>
                            <ENT>0</ENT>
                            <ENT>1,232</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">
                                <E T="03">Synthetic Aperture Sonars (SAS):</E>
                                 Sonars in which active acoustic signals are post-processed to form high-resolution images of the seafloor
                            </ENT>
                            <ENT>
                                SAS1
                                <LI>SAS2</LI>
                                <LI>SAS3</LI>
                                <LI>SAS4</LI>
                            </ENT>
                            <ENT>
                                MF SAS systems
                                <LI>HF SAS systems</LI>
                                <LI>VHF SAS systems</LI>
                                <LI>MF to HF broadband mine coiuntermeasure sonar</LI>
                            </ENT>
                            <ENT>
                                H
                                <LI>H</LI>
                                <LI>H</LI>
                                <LI>H</LI>
                            </ENT>
                            <ENT>
                                0
                                <LI>33,600</LI>
                                <LI>0</LI>
                                <LI>0</LI>
                            </ENT>
                            <ENT>
                                6,720
                                <LI>24,584</LI>
                                <LI>6,720</LI>
                                <LI>6,720</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Broadband Sound Sources (BB):</E>
                                 Sonar systems with large frequency spectra, used for various purposes
                            </ENT>
                            <ENT>
                                BB1
                                <LI>BB2</LI>
                                <LI>BB4</LI>
                                <LI>BB5</LI>
                                <LI>BB6</LI>
                                <LI>BB7</LI>
                            </ENT>
                            <ENT>
                                MF to HF mine countermeasure sonar
                                <LI>HF to VHF mine countermeasure sonar</LI>
                                <LI>LF to MF oceanographic source</LI>
                                <LI>LF to MF oceanographic source</LI>
                                <LI>HF oceanographic source</LI>
                                <LI>LF oceanographic source</LI>
                            </ENT>
                            <ENT>
                                H
                                <LI>H</LI>
                                <LI>H</LI>
                                <LI>H</LI>
                                <LI>H</LI>
                                <LI>C</LI>
                            </ENT>
                            <ENT>
                                0
                                <LI>0</LI>
                                <LI>0</LI>
                                <LI>0</LI>
                                <LI>0</LI>
                                <LI>0</LI>
                            </ENT>
                            <ENT>
                                6,720
                                <LI>6,720</LI>
                                <LI>10,884</LI>
                                <LI>4,704</LI>
                                <LI>4,704</LI>
                                <LI>840</LI>
                            </ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             H = hours; C = count (
                            <E T="03">e.g.,</E>
                             number of individual pings or individual sonobuoys).
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             The annual numbers for acoustic source classes associated with Navy training and testing activities in the AFTT Study Area are identical to those presented in Table 8 in the 2018 AFTT final rule.
                        </TNOTE>
                        <TNOTE>
                            <E T="02">Note:</E>
                             dB = decibel.
                        </TNOTE>
                    </GPOTABLE>
                    <P>Table 6 describes the number of air gun shots that could occur over seven years under the proposed training and testing activities.</P>
                    <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s100,12C,12C,12C,12C">
                        <TTITLE>Table 6—Training and Testing Air Gun Sources Quantitatively Analyzed in the AFTT Study Area</TTITLE>
                        <BOXHD>
                            <CHED H="1">Source class category</CHED>
                            <CHED H="1">Bin</CHED>
                            <CHED H="1">
                                Unit 
                                <SU>1</SU>
                            </CHED>
                            <CHED H="1">
                                7-Year total 
                                <SU>2</SU>
                            </CHED>
                            <CHED H="2">Training</CHED>
                            <CHED H="2">Testing</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Air Guns (AG):</E>
                                 Small underwater air guns
                            </ENT>
                            <ENT>AG</ENT>
                            <ENT>C</ENT>
                            <ENT>0</ENT>
                            <ENT>4,228</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             C = count. One count (C) of AG is equivalent to 100 air gun firings.
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             The annual numbers for airgun sources associated with Navy training and testing activities in the AFTT Study Area are identical to those presented in Table 9 in the 2018 AFTT final rule.
                        </TNOTE>
                    </GPOTABLE>
                    <P>Table 7 summarizes the impact pile driving and vibratory pile removal activities that would occur during a 24-hour period. Annually, for impact pile driving, the Navy would drive 119 piles, two times a year for a total of 238 piles. Over the seven-year period of the rule, the Navy would drive a total of 1,666 piles by impact pile driving. Annually, for vibratory pile removal, the Navy would remove 119 piles, two times a year for a total of 238 piles. Over the seven-year period of the rule, the Navy would remove a total of 1,666 piles by vibratory pile removal.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s100,12,12,12">
                        <TTITLE>Table 7—Summary of Pile Driving and Removal Activities per 24-Hour Period in the AFTT Study Area</TTITLE>
                        <BOXHD>
                            <CHED H="1">Method</CHED>
                            <CHED H="1">
                                Piles per 
                                <LI>24-hour </LI>
                                <LI>period</LI>
                            </CHED>
                            <CHED H="1">
                                Time per pile 
                                <LI>(minutes)</LI>
                            </CHED>
                            <CHED H="1">
                                Total 
                                <LI>estimated </LI>
                                <LI>time of </LI>
                                <LI>noise per </LI>
                                <LI>24-hour period </LI>
                                <LI>(minutes)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Pile Driving (Impact)</ENT>
                            <ENT>6</ENT>
                            <ENT>15 </ENT>
                            <ENT>90 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pile Removal (Vibratory)</ENT>
                            <ENT>12</ENT>
                            <ENT>6 </ENT>
                            <ENT>72 </ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>
                        Table 8 describes the number of in-water explosives that could be used in any year under the proposed training and testing activities. Under the proposed activities bin use would vary annually, and the seven-year totals for the proposed training and testing activities take into account that annual variability.
                        <PRTPAGE P="21138"/>
                    </P>
                    <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="xs60,r50,r50,12,12">
                        <TTITLE>Table 8—Explosive Source Bins Analyzed and Number Used for Seven-Year Period for Training and Testing Activities Within the AFTT Study Area</TTITLE>
                        <BOXHD>
                            <CHED H="1">Bin</CHED>
                            <CHED H="1">
                                Net explosive weight 
                                <SU>1</SU>
                                <LI>(lb.)</LI>
                            </CHED>
                            <CHED H="1">Example explosive source</CHED>
                            <CHED H="1">
                                7-Year total 
                                <SU>2</SU>
                            </CHED>
                            <CHED H="2">Training</CHED>
                            <CHED H="2">Testing</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">E1</ENT>
                            <ENT>0.1-0.25</ENT>
                            <ENT>Medium-caliber projectile</ENT>
                            <ENT>53,900</ENT>
                            <ENT>160,880</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E2</ENT>
                            <ENT>&gt;0.25-0.5</ENT>
                            <ENT>Medium-caliber projectile</ENT>
                            <ENT>1,486</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E3</ENT>
                            <ENT>&gt;0.5-2.5</ENT>
                            <ENT>Large-caliber projectile</ENT>
                            <ENT>32,144</ENT>
                            <ENT>20,162</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E4</ENT>
                            <ENT>&gt;2.5-5</ENT>
                            <ENT>Mine neutralization charge</ENT>
                            <ENT>913</ENT>
                            <ENT>5,330</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E5</ENT>
                            <ENT>&gt;5-10</ENT>
                            <ENT>5-inch projectile</ENT>
                            <ENT>10,052</ENT>
                            <ENT>9,275</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E6</ENT>
                            <ENT>&gt;10-20</ENT>
                            <ENT>Hellfire missile</ENT>
                            <ENT>4,214</ENT>
                            <ENT>276</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E7</ENT>
                            <ENT>&gt;20-60</ENT>
                            <ENT>Demo block/shaped charge</ENT>
                            <ENT>28</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E8</ENT>
                            <ENT>&gt;60-100</ENT>
                            <ENT>Light-weight torpedo</ENT>
                            <ENT>154</ENT>
                            <ENT>231</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E9</ENT>
                            <ENT>&gt;100-250</ENT>
                            <ENT>500 lb. bomb</ENT>
                            <ENT>462</ENT>
                            <ENT>28</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E10</ENT>
                            <ENT>&gt;250-500</ENT>
                            <ENT>Harpoon missile</ENT>
                            <ENT>630</ENT>
                            <ENT>566</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E11</ENT>
                            <ENT>&gt;500-650</ENT>
                            <ENT>650 lb. mine</ENT>
                            <ENT>7</ENT>
                            <ENT>70</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E12</ENT>
                            <ENT>&gt;650-1,000</ENT>
                            <ENT>2,000 lb. bomb</ENT>
                            <ENT>126</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                E16 
                                <SU>2</SU>
                            </ENT>
                            <ENT>&gt;7,250-14,500</ENT>
                            <ENT>Littoral Combat Ship full ship shock trial</ENT>
                            <ENT>0</ENT>
                            <ENT>12</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                E17 
                                <SU>2</SU>
                            </ENT>
                            <ENT>&gt;14,500-58,000</ENT>
                            <ENT>Aircraft carrier full ship shock trial</ENT>
                            <ENT>0</ENT>
                            <ENT>4</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             Net Explosive Weight refers to the equivalent amount of Trinitrotoluene (TNT) the actual weight of a munition may be larger due to other components.
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             The annual numbers for explosive source bins associated with Navy training and testing activities in the AFTT Study Area are identical to those presented in Table 11 in the 2018 AFTT final rule.
                        </TNOTE>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Shock trials consist of four explosions each. In any given year there could be 0-3 small ship shock trials (E16) and 0-1 large ship shock trials (E17). Over a 7-year period, there could be three small ship shock trials (E16) and one large ship shock trial (E17) which is the same amount of ship shock trial events that could occur over the original five-year period. Therefore, there is no increase in ship shock trial events under the proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD2">Vessel Movement</HD>
                    <P>Vessel movements associated with the proposed activities include both surface and sub-surface operations. Vessels used as part of the proposed activities include ships, submarines, unmanned vessels, and boats ranging in size from small, 22 feet (ft.) (7 meters (m)) rigid hull inflatable boats to aircraft carriers with lengths up to 1,092 ft. (333 m). Large Navy ships greater than 60 ft (18 m) generally operate at speeds in the range of 10 to 15 kn for fuel conservation. Submarines generally operate at speeds in the range of 8 to 13 kn in transits and less than those speeds for certain tactical maneuvers. Small craft, less than 60 ft (18 m) in length, have much more variable speeds (dependent on the mission). For small craft types, sizes and speeds vary during training and testing. Speeds generally range from 10 to 14 kn. While these speeds for large and small crafts are representative of most events, some vessels need to temporarily operate outside of these parameters. A full description of Navy vessels that are used during training and testing activities can be found in the 2017 Navy application and Chapter 2 of the 2018 AFTT FEIS/OEIS.</P>
                    <P>The Navy proposes no changes to the manner in which Navy vessels would be used during training and testing activities, the speeds at which they operate, the number of vessels that would be used during various activities, or the locations in which Navy vessel movement would be concentrated within the AFTT Study Area from those analyzed in the 2018 AFTT final rule. The only change related to the Navy's request regarding Navy vessel movement is the vessel use associated with the additional two years of Navy activities.</P>
                    <HD SOURCE="HD2">Standard Operating Procedures</HD>
                    <P>For training and testing to be effective, personnel must be able to safely use their sensors and weapon systems as they are intended to be used in a real-world situation and to their optimum capabilities. While standard operating procedures are designed for the safety of personnel and equipment and to ensure the success of training and testing activities, their implementation often yields additional benefits on environmental, socioeconomic, public health and safety, and cultural resources. Because standard operating procedures are essential to safety and mission success, the Navy considers them to be part of the proposed activities and has included them in the environmental analysis. Details on standard operating procedures were provided in the 2018 AFTT proposed rule; please see the 2018 AFTT proposed rule, the 2017 Navy application, and Chapter 2 of the 2018 AFTT FEIS/OEIS for more information. The Navy proposes no changes to the Standard Operating Procedures from those included in the 2018 AFTT final rule.</P>
                    <HD SOURCE="HD1">Description of Marine Mammals and Their Habitat in the Area of the Specified Activities</HD>
                    <P>Marine mammal species and their associated stocks that have the potential to occur in the AFTT Study Area are presented in Table 9 along with the best/minimum abundance estimate and associated coefficient of variation value. Some marine mammal species, such as manatees, are not managed by NMFS, but by the U.S. Fish and Wildlife Service and therefore not discussed below. Consistent with the 2018 AFTT final rule, the Navy still anticipates the take of individuals of 39 marine mammal species by Level A harassment and B harassment incidental to training and testing activities from the use of sonar and other transducers, in-water detonations, air guns, and impact pile driving/vibratory extraction activities. The Navy requested authorization for nine serious injuries or mortalities combined from four marine mammal stocks during ship shock trials, and four takes of large whales by serious injury or mortality from vessel strikes over the seven-year period.</P>
                    <P>
                        We presented a detailed discussion of marine mammals and their occurrence in the AFTT Study Area, inclusive of important marine mammal habitat (
                        <E T="03">e.g.,</E>
                         critical habitat), biologically important areas (BIAs), national marine sanctuaries (NMSs), and unusual mortality events (UMEs) in the 2018 AFTT proposed rule and 2018 AFTT final rule; please see these rules and the 2017 and 2019 Navy applications for 
                        <PRTPAGE P="21139"/>
                        additional information. There have been no changes to important marine mammal habitat, BIAs, NMSs, or Endangered Species Act (ESA) designated critical habitat since the issuance of the 2018 AFTT final rule; therefore the information that supports our determinations here can be found in the 2018 AFTT proposed and final rules. NMFS has reviewed the most recent Stock Assessment Reports (SARs), which have not been revised since the publication of the 2018 AFTT final rule); information on relevant UMEs; and other scientific literature, and determined that none of these nor any other new information changes our determination of which species or stocks have the potential to be affected by the Navy's activities or the pertinent information in the 
                        <E T="03">Description of the Marine Mammals in the Area of Specified Activities</E>
                         section in the 2018 AFTT proposed and final rules. Therefore the information presented in those sections of the 2018 proposed and final rules remains current and valid.
                    </P>
                    <P>
                        As described in the 2018 AFTT final rule, the species carried forward for analysis are those likely to be found in the AFTT Study Area based on the most recent data available, and do not include stocks or species that may have once inhabited or transited the area but have not been sighted in recent years and therefore are extremely unlikely to occur in the AFTT Study Area (
                        <E T="03">e.g.,</E>
                         species which were extirpated because of factors such as nineteenth and twentieth century commercial exploitation).
                    </P>
                    <P>
                        The species not carried forward for analysis (addressed in more detail in the 
                        <E T="03">Description of Marine Mammals and Their Habitat in the Area of the Specified Activities</E>
                         section of the 2018 AFTT rule) include the bowhead whale, beluga whale, and narwhal as these would be considered extralimital and are not part of the AFTT seasonal species assemblage. Additionally, for multiple bottlenose dolphin stocks, there was no potential for overlap with any stressors from Navy activities; therefore, there would be no adverse effects (or takes), and those stocks were not considered further. Specifically, with the exception of the Mississippi Sound, Lake Borgne, Bay Boudreau stock of bottlenose dolphins (which is addressed in the 
                        <E T="03">Analysis and Negligible Impact Determination</E>
                         section of the 2018 AFTT final rule), there is no potential for overlap of any Navy stressor with any other Northern Gulf of Mexico Bay, Sound, and Estuary stocks. Also, the following bottlenose dolphin stocks for the Atlantic do not have any potential for overlap with Navy activity stressors (or take), and therefore are not considered further: Northern South Carolina Estuarine System, Charleston Estuarine System, Northern Georgia/Southern South Carolina Estuarine System, Central Georgia Estuarine System, Southern Georgia Estuarine System, Biscayne Bay, and Florida Bay stocks. For the same reason, bottlenose dolphins off the coasts of Puerto Rico and the U.S. Virgin Islands were also not considered further.
                        <PRTPAGE P="21140"/>
                    </P>
                    <GPOTABLE COLS="8" OPTS="L2,nj,p6,6/7,i1" CDEF="s50,r50,r50,xs84,xs74,r50,r100,r100">
                        <TTITLE>Table 9—Marine Mammals Present in the AFTT Study Area</TTITLE>
                        <BOXHD>
                            <CHED H="1">Common name</CHED>
                            <CHED H="1">
                                Scientific name 
                                <SU>1</SU>
                            </CHED>
                            <CHED H="1">
                                Stock 
                                <SU>2</SU>
                            </CHED>
                            <CHED H="1">
                                ESA/MMPA status 
                                <SU>3</SU>
                            </CHED>
                            <CHED H="1">
                                Stock abundance 
                                <SU>4</SU>
                                  
                                <LI>best/minimum population</LI>
                            </CHED>
                            <CHED H="1">
                                Occurrence in AFTT Study Area 
                                <SU>5</SU>
                            </CHED>
                            <CHED H="2">Open ocean</CHED>
                            <CHED H="2">Large marine ecosystems</CHED>
                            <CHED H="2">Inland waters</CHED>
                        </BOXHD>
                        <ROW EXPSTB="07" RUL="s">
                            <ENT I="21">
                                <E T="02">Order Cetacea—Suborder Mysticeti (baleen whales)</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="22">
                                <E T="03">Family Balaenidae (right whales):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bowhead whale</ENT>
                            <ENT>
                                <E T="03">Balaena mysticetus</E>
                            </ENT>
                            <ENT>Eastern Canada-West Greenland</ENT>
                            <ENT>Endangered, strategic, depleted</ENT>
                            <ENT>
                                7,660 (4,500-11,100) 
                                <SU>6</SU>
                            </ENT>
                            <ENT>Labrador Current</ENT>
                            <ENT>Newfoundland-Labrador Shelf, West Greenland Shelf, Northeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">North Atlantic right whale</ENT>
                            <ENT>
                                <E T="03">Eubalaena glacialis</E>
                            </ENT>
                            <ENT>Western</ENT>
                            <ENT>Endangered, strategic, depleted</ENT>
                            <ENT>451 (0)/445</ENT>
                            <ENT>Gulf Stream, Labrador Current, North Atlantic Gyre</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf, Gulf of Mexico (extralimital)</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Balaenop- teridae (rorquals):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Blue whale</ENT>
                            <ENT>
                                <E T="03">Balaenoptera musculus</E>
                            </ENT>
                            <ENT>Western North Atlantic (Gulf of St. Lawrence)</ENT>
                            <ENT>Endangered, strategic, depleted</ENT>
                            <ENT>
                                Unknown/440 
                                <SU>11</SU>
                            </ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre, Labrador Current</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf, Southeast U.S. Continental Shelf, Caribbean Sea, and Gulf of Mexico (strandings only)</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bryde's whale</ENT>
                            <ENT>
                                <E T="03">Balaenoptera brydei/edeni</E>
                            </ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>Endangered, strategic</ENT>
                            <ENT>33 (1.07)/16</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Fin whale</ENT>
                            <ENT>
                                <E T="03">Balaenoptera physalus</E>
                            </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>Endangered, strategic, depleted</ENT>
                            <ENT>1,618 (0. 33)/1,234</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre, Labrador Current</ENT>
                            <ENT>Caribbean Sea, Gulf of Mexico, Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>West Greenland</ENT>
                            <ENT>Endangered, strategic, depleted</ENT>
                            <ENT>
                                4,468 (1,343-14,871) 
                                <SU>9</SU>
                            </ENT>
                            <ENT>Labrador Current</ENT>
                            <ENT>West Greenland Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Gulf of St. Lawrence</ENT>
                            <ENT>Endangered, strategic, depleted</ENT>
                            <ENT>
                                328 (306-350) 
                                <SU>10</SU>
                            </ENT>
                            <ENT/>
                            <ENT>Newfoundland-Labrador Shelf, Scotian Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Humpback whale</ENT>
                            <ENT>
                                <E T="03">Megaptera novaeangliae</E>
                            </ENT>
                            <ENT>Gulf of Maine</ENT>
                            <ENT>NA</ENT>
                            <ENT>896 (0)/896</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre, Labrador Current</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea, Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Minke whale</ENT>
                            <ENT>
                                <E T="03">Balaenoptera acutorostrata</E>
                            </ENT>
                            <ENT>Canadian Eastern Coastal</ENT>
                            <ENT>NA</ENT>
                            <ENT>2,591 (0.81)/1,425</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre, Labrador Current</ENT>
                            <ENT>Caribbean Sea, Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                West Greenland 
                                <SU>7</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                16,609 (7,172-38,461)/NA 
                                <SU>7</SU>
                            </ENT>
                            <ENT>Labrador Current</ENT>
                            <ENT>West Greenland Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Sei whale</ENT>
                            <ENT>
                                <E T="03">Balaenoptera borealis</E>
                            </ENT>
                            <ENT>Nova Scotia</ENT>
                            <ENT>Endangered, strategic, depleted</ENT>
                            <ENT>357 (0.52)/236</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea, Southeast Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Labrador Sea</ENT>
                            <ENT>Endangered, strategic, depleted</ENT>
                            <ENT>
                                Unknown 
                                <SU>8</SU>
                            </ENT>
                            <ENT>Labrador Current</ENT>
                            <ENT>Newfoundland-Labrador Shelf, West Greenland Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW EXPSTB="07" RUL="s">
                            <ENT I="21">
                                <E T="02">Suborder Odontoceti (toothed whales)</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="22">
                                <E T="03">Family Physeteridae (sperm whale):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Sperm whale</ENT>
                            <ENT>
                                <E T="03">Physeter macrocephalus</E>
                            </ENT>
                            <ENT>North Atlantic</ENT>
                            <ENT>Endangered, strategic, depleted</ENT>
                            <ENT>2,288 (0.28)/1,815</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre, Labrador Current</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>Endangered, strategic, depleted</ENT>
                            <ENT>763 (0.38)/560</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Puerto Rico and U.S. Virgin Islands</ENT>
                            <ENT>Endangered, strategic, depleted</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>North Atlantic Gyre</ENT>
                            <ENT>Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW EXPSTB="07" RUL="s">
                            <ENT I="21">
                                <E T="02">Family Kogiidae (sperm whales)</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="03">Pygmy and dwarf sperm whales</ENT>
                            <ENT>
                                <E T="03">Kogia breviceps</E>
                                 and
                                <E T="03"> Kogia sima</E>
                            </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                3,785 (0.47)/2,598 
                                <SU>12</SU>
                            </ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                186 (1.04)/90 
                                <SU>12</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW EXPSTB="07" RUL="s">
                            <PRTPAGE P="21141"/>
                            <ENT I="21">
                                <E T="02">Family Monodontidae (beluga whale and narwhal)</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="03">Beluga whale</ENT>
                            <ENT>
                                <E T="03">Delphinapterus leucas</E>
                            </ENT>
                            <ENT>
                                Eastern High Arctic/Baffin Bay 
                                <SU>13</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                21,213 (10,985-32,619) 
                                <SU>13</SU>
                            </ENT>
                            <ENT>Labrador Current</ENT>
                            <ENT>West Greenland Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                West Greenland 
                                <SU>14</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                10,595 (4.904-24,650) 
                                <SU>14</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>West Greenland Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="03">Narwhal</ENT>
                            <ENT>
                                <E T="03">Monodon monoceros</E>
                            </ENT>
                            <ENT>
                                NA 
                                <SU>15</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                NA 
                                <SU>15</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>Newfoundland-Labrador Shelf, West Greenland Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW EXPSTB="07" RUL="s">
                            <ENT I="21">
                                <E T="02">Family Ziphiidae (beaked whales)</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="03">Blainville's beaked whale</ENT>
                            <ENT>
                                <E T="03">Mesoplodon densirostris</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                7,092 (0.54)/4,632 
                                <SU>17</SU>
                            </ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre, Labrador Current</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                149 (0.91)/77 
                                <SU>18</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Cuvier's beaked whale</ENT>
                            <ENT>
                                <E T="03">Ziphius cavirostris</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>6,532 (0.32)/5,021</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>74 (1.04)/36</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Puerto Rico and U.S. Virgin Islands</ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Gervais' beaked whale</ENT>
                            <ENT>
                                <E T="03">Mesoplodon europaeus</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                7,092 (0.54)/4,632 
                                <SU>17</SU>
                            </ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast United States Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                149 (0.91)/77 
                                <SU>18</SU>
                            </ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Northern bottlenose whale</ENT>
                            <ENT>
                                <E T="03">Hyperoodon ampullatus</E>
                            </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>NA</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre, Labrador Current</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Sowerby's beaked whale</ENT>
                            <ENT>
                                <E T="03">Mesoplodon bidens</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                7,092 (0.54)/4,632 
                                <SU>17</SU>
                            </ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="03">True's beaked whale</ENT>
                            <ENT>
                                <E T="03">Mesoplodon mirus</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                7,092 (0.54)/4,632 
                                <SU>17</SU>
                            </ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW EXPSTB="07" RUL="s">
                            <ENT I="21">
                                <E T="02">Family Delphinidae (dolphins)</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="03">Atlantic spotted dolphin</ENT>
                            <ENT>
                                <E T="03">Stenella frontalis</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>44,715 (0.43)/31,610</ENT>
                            <ENT>Gulf Stream</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>NA</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Puerto Rico and U.S. Virgin Islands</ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Atlantic white-sided dolphin</ENT>
                            <ENT>
                                <E T="03">Lagenorhynchus acutus</E>
                            </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>NA</ENT>
                            <ENT>48,819 (0.61)/30,403</ENT>
                            <ENT>Gulf Steam, Labrador Current</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Clymene dolphin</ENT>
                            <ENT>
                                <E T="03">Stenella clymene</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>Gulf Stream</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>129 (1.0)/64</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Common bottlenose dolphin Common bottlenose dolphin</ENT>
                            <ENT>
                                <E T="03">Tursiops truncatus</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic Offshore 
                                <SU>19</SU>
                            </ENT>
                            <ENT>Strategic, depleted</ENT>
                            <ENT>77,532 (0.40)/56,053</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf, Scotian Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Western North Atlantic Northern Migratory Coastal 
                                <SU>20</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>6,639 (0.41)/4,759</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf</ENT>
                            <ENT>Long Island Sound, Sandy Hook Bay, Lower Chesapeake Bay, James River, Elizabeth River.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Western North Atlantic Southern Migratory Coastal 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic, depleted</ENT>
                            <ENT>3,751 (0.06)/2,353</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>Lower Chesapeake Bay, James River, Elizabeth River, Beaufort Inlet, Cape Fear River, Kings Bay, St. Johns River.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Western North Atlantic South Carolina/Georgia Coastal 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic, depleted</ENT>
                            <ENT>6,027 (0.34)/4,569</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>Kings Bay, St. Johns River.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern North Carolina Estuarine System 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>823 (0.06)/782</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf</ENT>
                            <ENT>Beaufort Inlet, Cape Fear River.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Southern North Carolina Estuarine System 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>Beaufort Inlet, Cape Fear River.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern South Carolina Estuarine System 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Charleston Estuarine System 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="21142"/>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Georgia/Southern South Carolina Estuarine System 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Central Georgia Estuarine System 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>192 (0.04)/185</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Southern Georgia Estuarine System 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>194 (0.05)/185</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>Kings Bay, St. Johns River.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Western North Atlantic Northern Florida Coastal 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic, depleted</ENT>
                            <ENT>877 (0.49)/595</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>Kings Bay, St. Johns River.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Jacksonville Estuarine System 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>Kings Bay, St. Johns River.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Western North Atlantic Central Florida Coastal 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic, depleted</ENT>
                            <ENT>1,218 (0.35)/913</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>Port Canaveral.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Indian River Lagoon Estuarine System 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>Port Canaveral.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Biscayne Bay 
                                <SU>16</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Florida Bay 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico Continental Shelf 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Na</ENT>
                            <ENT>51,192 (0.10)/46,926</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Gulf of Mexico Eastern Coastal 
                                <SU>20</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>12,388 (0.13)/11,110</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Gulf of Mexico Northern Coastal 
                                <SU>20</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>7,185 (0.21)/6,044</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>St. Andrew Bay, Pascagoula River.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Gulf of Mexico Western Coastal 
                                <SU>20</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>20,161 (0.17)/17,491</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>Corpus Christi Bay, Galveston Bay.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico Oceanic 
                                <SU>20</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>5,806 (0.39)/4,230</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Laguna Madre 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>80 (1.57)/Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Nueces Bay/Corpus Christi Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>58 (0.61)/Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Copano Bay/Aransas Bay/San Antonio Bay/Redfish Bay/Espiritu Santo Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>55 (0.82)/Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Matagorda Bay/Tres Palacios Bay/Lavaca Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>61 (0.45)/Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                West Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>48 (0.03)/46</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Galveston Bay/East Bay/Trinity Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>152 (0.43)/Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Sabine Lake 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>0</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Calcasieu Lake 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>0</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Vermilion Bay/West Cote Blanche Bay/Atchafalaya Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>0</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Terrebonne Bay/Timbalier Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>3,870 (0.15)/3,426</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Barataria Bay Estuarine System 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>2,306 (0.09)/2,138</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Mississippi River Delta 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>332 (0.93)/170</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Mississippi Sound, Lake Borgne, Bay Boudreau 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>3,046 (0.06)/2,896</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Mobile Bay/Bonsecour Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>122 (0.34)/Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Perdido Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>0</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Pensacola Bay/East Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>33 (0.80)/Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Choctawhatchee Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>179 (0.04)/Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                St. Andrew Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>124 (0.57)/Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                St. Joseph Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>152 (0.08)/Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="21143"/>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                St. Vincent Sound/Apalachicola Bay/St. George Sound 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>439 (0.14)/Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Apalachee Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>491 (0.39)/Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Waccasassa Bay/Withlacoochee Bay/Crystal Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                St. Joseph Sound/Clearwater Harbor 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Tampa Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Sarasota Bay/Little Sarasota Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>158 (0.27)/126</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Pine Island Sound/Charlotte Harbor/Gasparilla Sound/Lemon Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>826 (0.09)/Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Caloosahatchee River 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>0</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Estero Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Chokoloskee Bay/Ten Thousand Islands/Gullivan Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Whitewater Bay 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Florida Keys (Bahia Honda to Key West) 
                                <SU>20</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Puerto Rico and U.S. Virgin Islands</ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">False killer whale</ENT>
                            <ENT>
                                <E T="03">Pseudorca crassidens</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>22</SU>
                            </ENT>
                            <ENT>Strategic</ENT>
                            <ENT>442 (1.06)/212</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Fraser's dolphin</ENT>
                            <ENT>
                                <E T="03">Lagenodelphis hosei</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>23</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>Gulf Stream</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Southeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Killer Whale</ENT>
                            <ENT>
                                <E T="03">Orcinus orca</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>22</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre, Labrador Current</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast United States Continental Shelf, Scotian Shelf, Newfoundland—Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>28 (1.02)/14</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Long-finned pilot whale</ENT>
                            <ENT>
                                <E T="03">Globicephala melas</E>
                            </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>NA</ENT>
                            <ENT>5,636 (0.63)/3,464</ENT>
                            <ENT>Gulf Stream</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Melon-headed Whale</ENT>
                            <ENT>
                                <E T="03">Peponocephala electra</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>23</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>2,235 (0.75)/1,274</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pantropical spotted-dolphin</ENT>
                            <ENT>
                                <E T="03">Stenella attenuate</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>3,333 (0.91)/1,733</ENT>
                            <ENT>Gulf Stream</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico 
                                <SU>22</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>50,880 (0.27)/40,699</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pygmy Killer Whales</ENT>
                            <ENT>
                                <E T="03">Feresa attenuata</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Southeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>152 (1.02)/75</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Risso's dolphin</ENT>
                            <ENT>
                                <E T="03">Grampus griseus</E>
                            </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>NA</ENT>
                            <ENT>18,250 (0.46)/12,619</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast United States Continental Shelf, Scotian Shelf, Newfoundland—Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>NA</ENT>
                            <ENT>2,442 (0.57)/1,563</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Rough-toothed dolphin</ENT>
                            <ENT>
                                <E T="03">Steno bredanensis</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>136 (1.00)/67</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Caribbean Sea Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>NA</ENT>
                            <ENT>624 (0.99)/311</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Short-finned pilot whale</ENT>
                            <ENT>
                                <E T="03">Globicephala macrorhynchus</E>
                            </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>NA</ENT>
                            <ENT>28,924 (0.24)/23,637</ENT>
                            <ENT>NA</ENT>
                            <ENT>Northeast Continental Shelf, Southeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico 
                                <SU>22</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>2,415 (0.66)/1,456</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Puerto Rico and U.S. Virgin Islands</ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Spinner dolphin</ENT>
                            <ENT>
                                <E T="03">Stenella longirostris</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>Gulf Stream, North Atlantic Gyre</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="21144"/>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>11,441 (0.83)/6,221</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>Puerto Rico and U.S. Virgin Islands</ENT>
                            <ENT>Strategic</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Striped dolphin</ENT>
                            <ENT>
                                <E T="03">Stenella coeruleoalba</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>54,807 (0.30)/42,804</ENT>
                            <ENT>Gulf Stream</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Scotian Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Northern Gulf of Mexico 
                                <SU>16</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>1,849 (0.77)/1,041</ENT>
                            <ENT>NA</ENT>
                            <ENT>Gulf of Mexico, Caribbean Sea</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Short-beaked common dolphin</ENT>
                            <ENT>
                                <E T="03">Delphinus delphis</E>
                            </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>NA</ENT>
                            <ENT>70,184 (0.28)/55,690</ENT>
                            <ENT>Gulf Stream</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="03">White-beaked dolphin</ENT>
                            <ENT>
                                <E T="03">Lagenorhynchus albirostris</E>
                            </ENT>
                            <ENT>
                                Western North Atlantic 
                                <SU>23</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>2,003 (0.94)/1,023</ENT>
                            <ENT>Labrador Current</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Phocoenidae (porpoises):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Harbor porpoise</ENT>
                            <ENT>
                                <E T="03">Phocoena phocoena</E>
                            </ENT>
                            <ENT>Gulf of Maine/Bay of Fundy</ENT>
                            <ENT>NA</ENT>
                            <ENT>79,883 (0.32)/61,415</ENT>
                            <ENT>NA</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>Narragansett Bay, Rhode Island Sound, Block Island Sound, Buzzards Bay, Vineyard Sound, Long Island Sound, Piscataqua River, Thames River, Kennebec River.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Gulf of St. Lawrence 
                                <SU>24</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                Unknown 
                                <SU>24</SU>
                            </ENT>
                            <ENT>Labrador Current</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Newfoundland 
                                <SU>25</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                Unknown 
                                <SU>25</SU>
                            </ENT>
                            <ENT>Labrador Current</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT>
                                Greenland 
                                <SU>26</SU>
                            </ENT>
                            <ENT>NA</ENT>
                            <ENT>
                                Unknown 
                                <SU>26</SU>
                            </ENT>
                            <ENT>Labrador Current</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf, West Greenland Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW EXPSTB="07" RUL="s">
                            <ENT I="21">
                                <E T="02">Order Carnivora—Suborder Pinnipedia</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="22">
                                <E T="03">Family Phocidae (true seals):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Gray seal</ENT>
                            <ENT>
                                <E T="03">Halichoerus grypus</E>
                            </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>NA</ENT>
                            <ENT>27,131 (0.19)/23,158</ENT>
                            <ENT>NA</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>Narragansett Bay, Rhode Island Sound, Block Island Sound, Buzzards Bay, Vineyard Sound, Long Island Sound, Piscataqua River, Thames River, Kennebeck River.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Harbor seal</ENT>
                            <ENT>
                                <E T="03">Phoca vitulina</E>
                            </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>NA</ENT>
                            <ENT>75,834 (0.15)/66,884</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>Chesapeake Bay, Narragansett Bay, Rhode Island Sound, Block Island Sound, Buzzards Bay, Vineyard Sound, Long Island Sound, Piscataqua River, Thames River, Kennebeck River.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Harp seal</ENT>
                            <ENT>
                                <E T="03">Pagophilus groenlandicus</E>
                            </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>NA</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf</ENT>
                            <ENT>NA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Hooded seal</ENT>
                            <ENT>
                                <E T="03">Cystophora cristata</E>
                            </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>NA</ENT>
                            <ENT>Unknown</ENT>
                            <ENT>NA</ENT>
                            <ENT>Southeast U.S. Continental Shelf, Northeast U.S. Continental Shelf, Scotian Shelf, Newfoundland-Labrador Shelf, West Greenland Shelf</ENT>
                            <ENT>Narragansett Bay, Rhode Island Sound, Block Island Sound, Buzzards Bay, Vineyard Sound, Long Island Sound, Piscataqua River, Thames River, Kennebec River.</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Notes:</E>
                             CV: Coefficient of variation; ESA: Endangered Species Act; MMPA: Marine Mammal Protection Act; NA: Not applicable.
                        </TNOTE>
                        <TNOTE>
                            <SU>1</SU>
                             Taxonomy follows (Committee on Taxonomy, 2016).
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             Stock designations for the U.S. EEZ and abundance estimates are from Atlantic and Gulf of Mexico SARs prepared by NMFS 
                            <E T="03">(Hayes et al.,</E>
                             2017) and the draft 2018 SARs, unless specifically noted.
                        </TNOTE>
                        <TNOTE>
                            <SU>3</SU>
                             Populations or stocks defined by the MMPA as “strategic” for one of the following reasons: (1) The level of direct human-caused mortality exceeds the potential biological removal level; (2) based on the best available scientific information, numbers are declining and species are likely to be listed as threatened species under the ESA within the foreseeable future; (3) species are listed as threatened or endangered under the ESA; (4) species are designated as depleted under the MMPA.
                        </TNOTE>
                        <TNOTE>
                            <SU>4</SU>
                             Stock abundance, CV, and minimum population are numbers provided by the Stock Assessment Reports (SARs; Hayes 
                            <E T="03">et al</E>
                            ., 2017). The stock abundance is an estimate of the number of animals within the stock. The CV is a statistical metric used as an indicator of the uncertainty in the abundance estimate. The minimum population estimate is either a direct count (
                            <E T="03">e.g.,</E>
                             pinnipeds on land) or the lower 20th percentile of a statistical abundance estimate.
                        </TNOTE>
                        <TNOTE>
                            <SU>5</SU>
                             Occurrence in the AFTT Study Area includes open ocean areas—Labrador Current, North Atlantic Gyre, Gulf Stream, and coastal/shelf waters of seven large marine ecosystems—West Greenland Shelf, Newfoundland-Labrador Shelf, Scotian Shelf, and Northeast U.S. Continental Shelf, Southeast U.S. Continental Shelf, Caribbean Sea, Gulf of Mexico, and inland waters of Kennebec River, Piscataqua River, Thames River, Narragansett Bay, Rhode Island Sound, Block Island Sound, Buzzards Bay, Vineyard Sound, Long Island Sound, Sandy Hook Bay, Lower Chesapeake Bay, James River, Elizabeth River, Beaufort Inlet, Cape Fear River, Kings Bay, St. Johns River, Port Canaveral, St. Andrew Bay, Pascagoula River, Sabine Lake, Corpus Christi Bay, and Galveston Bay.
                        </TNOTE>
                        <TNOTE>
                            <SU>6</SU>
                             The bowhead whale population off the West Coast of Greenland is not managed by NMFS and, therefore, does not have an associated Stock Assessment Report. Abundance and 95 percent highest density interval were presented in (Frasier 
                            <E T="03">et al.,</E>
                             2015).
                        </TNOTE>
                        <TNOTE>
                            <SU>7</SU>
                             The West Greenland stock of minke whales is not managed by NMFS and, therefore, does not have an associated Stock Assessment Report. Abundance and 95 percent confidence interval were presented in (Heide-Jørgensen 
                            <E T="03">et al.,</E>
                             2010).
                        </TNOTE>
                        <TNOTE>
                            <SU>8</SU>
                             The Labrador Sea stock of sei whales is not managed by NMFS and, therefore, does not have an associated Stock Assessment Report. Information was obtained in (Prieto 
                            <E T="03">et al.,</E>
                             2014).
                        </TNOTE>
                        <TNOTE>
                            <SU>9</SU>
                             The West Greenland stock of fin whales is not managed by NMFS and, therefore, does not have an associated Stock Assessment Report. Abundance and 95 percent confidence interval were presented in (Heide-Jørgensen 
                            <E T="03">et al.,</E>
                             2010).
                        </TNOTE>
                        <TNOTE>
                            <SU>10</SU>
                             The Gulf of St. Lawrence stock of fin whales is not managed by NMFS and, therefore, does not have an associated Stock Assessment Report. Abundance and 95 percent confidence interval were presented in (Ramp 
                            <E T="03">et al.,</E>
                             2014).
                        </TNOTE>
                        <TNOTE>
                            <SU>11</SU>
                             Photo identification catalogue count of 440 recognizable blue whale individuals from the Gulf of St. Lawrence is considered a minimum population estimate for the western North Atlantic stock (Waring 
                            <E T="03">et al.,</E>
                             2010).
                        </TNOTE>
                        <TNOTE>
                            <SU>12</SU>
                             Estimates include both the pygmy and dwarf sperm whales in the western North Atlantic (Waring 
                            <E T="03">et al.,</E>
                             2014) and the northern Gulf of Mexico (Waring 
                            <E T="03">et al.,</E>
                             2013).
                        </TNOTE>
                        <TNOTE>
                            <SU>13</SU>
                             Beluga whales in the Atlantic are not managed by NMFS and have no associated Stock Assessment Report. Abundance and 95 percent confidence interval for the Eastern High Arctic/Baffin Bay stock were presented in (Innes 
                            <E T="03">et al.,</E>
                             2002).
                        </TNOTE>
                        <TNOTE>
                            <SU>14</SU>
                             Beluga whales in the Atlantic are not managed by NMFS and have no associated Stock Assessment Report. Abundance and 95 percent confidence interval for the West Greenland stock were presented in (Heide-Jørgensen 
                            <E T="03">et al.,</E>
                             2009).
                            <PRTPAGE P="21145"/>
                        </TNOTE>
                        <TNOTE>
                            <SU>15</SU>
                             NA = Not applicable. Narwhals in the Atlantic are not managed by NMFS and have no associated Stock Assessment Report.
                        </TNOTE>
                        <TNOTE>
                            <SU>16</SU>
                             Estimates for these western North Atlantic stocks are from Waring 
                            <E T="03">et al.</E>
                             (2014) and the northern Gulf of Mexico stock are from (Waring 
                            <E T="03">et al.,</E>
                             2013) as applicable.
                        </TNOTE>
                        <TNOTE>
                            <SU>17</SU>
                             Estimate includes undifferentiated Mesoplodon species.
                        </TNOTE>
                        <TNOTE>
                            <SU>18</SU>
                             Estimate includes Gervais' and Blainville's beaked whales.
                        </TNOTE>
                        <TNOTE>
                            <SU>19</SU>
                             Estimate may include sightings of the coastal form.
                        </TNOTE>
                        <TNOTE>
                            <SU>20</SU>
                             Estimates for these Gulf of Mexico stocks are from SARs.
                        </TNOTE>
                        <TNOTE>
                            <SU>21</SU>
                             NMFS is in the process of writing individual stock assessment reports for each of the 32 bay, sound, and estuary stocks.
                        </TNOTE>
                        <TNOTE>
                            <SU>22</SU>
                             Estimates for these stocks are from Waring 
                            <E T="03">et al.,</E>
                             (2015).
                        </TNOTE>
                        <TNOTE>
                            <SU>23</SU>
                             Estimates for these western North Atlantic stocks are from (Waring 
                            <E T="03">et al.,</E>
                             2007).
                        </TNOTE>
                        <TNOTE>
                            <SU>24</SU>
                             Harbor porpoise in the Gulf of St. Lawrence are not managed by NMFS and have no associated Stock Assessment Report.
                        </TNOTE>
                        <TNOTE>
                            <SU>25</SU>
                             Harbor porpoise in Newfoundland are not managed by NMFS and have no associated Stock Assessment Report.
                        </TNOTE>
                        <TNOTE>
                            <SU>26</SU>
                             Harbor porpoise in Greenland are not managed by NMFS and have no associated Stock Assessment Report.
                        </TNOTE>
                    </GPOTABLE>
                    <PRTPAGE P="21146"/>
                    <HD SOURCE="HD1">Potential Effects of Specified Activities on Marine Mammals and Their Habitat</HD>
                    <P>
                        We provided a full discussion of the potential effects of the specified activities on marine mammals and their habitat in our 2018 AFTT proposed rule and 2018 AFTT final rule. In the 
                        <E T="03">Potential Effects of Specified Activities on Marine Mammals and Their Habitat</E>
                         section of the 2018 AFTT proposed and final rules, NMFS provided a description of the ways marine mammals may be affected by the same activities that the Navy will be conducting during the seven-year period analyzed in this rule in the form of serious injury or mortality, physical trauma, sensory impairment (permanent and temporary threshold shifts and acoustic masking), physiological responses (particularly stress responses), behavioral disturbance, or habitat effects. Therefore, we do not repeat the information here, all of which remains current and applicable, but refer the reader to those rules and the 2018 AFTT FEIS/OEIS (Chapter 3, Section 3.7 
                        <E T="03">Marine Mammals, http://www.aftteis.com/</E>
                        ), which NMFS participated in the development of via our cooperating agency status and adopted to meet our NEPA requirements.
                    </P>
                    <P>In addition, NMFS has reviewed information in relevant SARs (which have not been revised since the publication of the 2018 AFTT final rule) any new information on active UMEs and from the scientific literature. Summaries of current UMEs and new scientific literature since publication of the 2018 AFTT final rule are presented below.</P>
                    <HD SOURCE="HD2">Unusual Mortality Events</HD>
                    <P>A UME is defined under section 410(6) of the MMPA as a stranding that is unexpected; involves a significant die-off of any marine mammal population; and demands immediate response. The five active UMEs with ongoing investigations in the AFTT Study Area that inform our analysis are discussed below. The impacts to Barataria Bay bottlenose dolphins from the closed Northern Gulf of Mexico UME (discussed in the 2018 AFTT proposed rule) associated with the Deep Water Horizon oil spill in the Gulf of Mexico are thought to be persistent and continue to inform population analyses. The other more recent UMEs closed several years ago, and little is known about how the effects of those events might be appropriately applied to an impact assessment several years later.</P>
                    <HD SOURCE="HD3">North Atlantic Right Whale (NARW) UME</HD>
                    <P>
                        NOAA declared an UME for NARWs from January 1, 2017, to the present. The current total number of mortalities included in the event is 20 whales, including 12 NARW carcasses from Canada in 2017 and eight carcasses in the United States (5 in 2017; 3 in 2018). There have been no carcasses reported in 2019. In 2017, 17 right whale mortalities were documented, and in 2018, an additional three whales were found dead. Of the 12 NARW carcasses found in Canadian waters in 2017, six were necropsied and died as a direct result of human activities (either confirmed, probable, or suspect), from either rope entanglements (2) or vessel strikes (4) (Daoust 
                        <E T="03">et al.,</E>
                         2017). Of the eight carcasses found in U.S. waters in 2017-2018, the cause of death was determined in six whales, with deaths attributable to either rope entanglement (5) or vessel strikes (1). Eight carcasses were not able to be examined. Daoust 
                        <E T="03">et al.</E>
                         (2018) also concluded there were no oil and gas seismic surveys authorized in the months prior to or during the period over which these mortalities occurred, as well as no blasting or major marine development projects. Navy was consulted as to sonar use and they confirmed none was used in the vicinity of any of the strandings.
                    </P>
                    <P>
                        As part of the UME investigation process for NARW, NOAA assembled an independent team of scientists (Investigative Team) that coordinates with the Working Group on Marine Mammal Unusual Mortality Events to review the data collected, sample future whales that strand, and determine the next steps for the investigation. For more information on this UME, please refer to 
                        <E T="03">https://www.fisheries.noaa.gov/national/marine-life-distress/2017-2019-north-atlantic-right-whale-unusual-mortality-event#causes-of-the-north-atlantic-right-whale-ume.</E>
                    </P>
                    <P>
                        While data are not yet available to statistically estimate the population's trend beyond 2015, three lines of evidence indicate the population is still in decline. First, calving rates in 2016, 2017, and 2018 were low. Only five new calves were documented in 2017 (Pettis 
                        <E T="03">et al.,</E>
                         2017a), well below the number needed to compensate for expected mortalities (Pace 
                        <E T="03">et al.,</E>
                         2017), and no new calves were reported for 2018. Long-term photographic identification data indicate new calves rarely go undetected, so these years likely represent a continuation of the low calving rates that began in 2012 (Kraus 
                        <E T="03">et al.,</E>
                         2007; Pace 
                        <E T="03">et al.,</E>
                         2017). So far in 2019, seven calves have been documented. Second, as noted above, the preliminary abundance estimate for 2016 is 451 individuals, down approximately 1.5 percent from 458 in 2015. Third, since June 2017, at least 20 NARWs have died in what has been declared an UME as discussed above, and at least one calf died in April 2017 (Meyer-Gutbrod 
                        <E T="03">et al.,</E>
                         2018; NMFS, 2017).
                    </P>
                    <HD SOURCE="HD3">Humpback Whale UME Along the Atlantic Coast</HD>
                    <P>
                        NOAA declared an UME for humpback whales from January 1, 2016, to the present, along the Atlantic coast from Maine through Florida. As of April 1, 2019, 92 humpback strandings have occurred (26, 34, 25, and 9 whales in 2016, 2017, 2018 and 2019 respectively). As of April 2019, partial or full necropsy examinations have been conducted on 43 cases, or approximately half of the 92 strandings (at that time). Of the 43 whales examined, approximately 20 had evidence of blunt force trauma or pre-mortem propeller wounds indicative of vessel strike and approximately 6 had evidence of entanglements. NOAA, in coordination with our stranding network partners, continues to investigate the recent mortalities and environmental conditions, and conduct population monitoring to better understand the recent humpback whale mortalities. At this time, vessel parameters (including size) are not known for each vessel-whale collision that led to the death of a whale. Therefore, NOAA considers all sizes of vessels to be a potential risk for whale species in highly trafficked areas. The Navy has investigated potential strikes and confirmed that it had none. Please refer to 
                        <E T="03">https://www.fisheries.noaa.gov/national/marine-life-distress/2016-2019-humpback-whale-unusual-mortality-event-along-atlantic-coast</E>
                         for more information on this UME.
                    </P>
                    <HD SOURCE="HD3">Minke Whale UME Along the Atlantic Coast</HD>
                    <P>
                        NOAA declared an UME for minke whales from January 1, 2017, to the present, along the Atlantic coast from Maine through Florida. As of April 1, 2019, 59 strandings have occurred (27, 20, and 2 whales in 2017, 2018 and 2019, respectively). As of April 1, 2019, full or partial necropsy examinations have been conducted on 33 whales. Preliminary findings on several of the whales have shown evidence of human interactions, primarily fisheries interactions, or infectious disease. These findings are not consistent across all of the whales examined, and final diagnostic results are still pending for 
                        <PRTPAGE P="21147"/>
                        many of the cases. Please refer to 
                        <E T="03">https://www.fisheries.noaa.gov/national/marine-life-distress/2017-2019-minke-whale-unusual-mortality-event-along-atlantic-coast</E>
                         for more information on this UME.
                    </P>
                    <HD SOURCE="HD3">Northeast Pinniped UME Along the Atlantic Coast</HD>
                    <P>
                        NOAA declared an UME on August 30, 2018, to the present due to increased numbers of harbor seal and gray seal strandings along the U.S. coasts of Maine, New Hampshire, and Massachusetts during July and August of 2018. Strandings have remained elevated in these three states and expanded south to Virginia with cases on-going. Recently, harp and hooded seals have begun stranding as they migrate from Canada into U.S. waters and have been included in the investigation. From July 1, 2018, to March 28, 2019, more than 2,062 seals have stranded with 95 percent of the seals stranding in Maine, New Hampshire, and Massachusetts. Full or partial necropsy examinations have been conducted on many of the seals and samples have been collected for testing. Based on testing conducted so far, the main pathogen found in the seals is phocine distemper virus. Please refer to 
                        <E T="03">https://www.fisheries.noaa.gov/new-england-mid-atlantic/marine-life-distress/2018-2019-pinniped-unusual-mortality-event-along</E>
                         for more information on this UME.
                    </P>
                    <HD SOURCE="HD3">Southwest Florida Bottlenose Dolphin UME Along the Gulf of Mexico</HD>
                    <P>
                        NOAA declared a UME in 2018 to the present due to elevated bottlenose dolphin mortalities occurring along the Southwest coast of Florida including Collier, Lee, Charlotte, Sarasota, Manatee, Hillsborough, and Pinellas counties. From July 1, 2018, to March 27, 2019, 159 dolphins have been confirmed stranded in this event. Our stranding network partners have conducted full or partial necropsy examinations on several dolphins, with positive results for the red tide toxin (brevetoxin) indicating this UME is related to the severe bloom of a red tide that has been ongoing since November 2017. Please refer to 
                        <E T="03">https://www.fisheries.noaa.gov/southeast/marine-life-distress/2018-2019-bottlenose-dolphin-unusual-mortality-event-southwest</E>
                         for more information on this UME.
                    </P>
                    <HD SOURCE="HD2">New Pertinent Science Since Publication of the 2018 AFTT Final Rule</HD>
                    <P>
                        Southall 
                        <E T="03">et al.</E>
                         (2019a) evaluated Southall 
                        <E T="03">et al.</E>
                         (2007) and used updated scientific information to propose revised noise exposure criteria to predict onset of auditory effects in marine mammals (
                        <E T="03">i.e.,</E>
                         PTS and TTS onset). Southall 
                        <E T="03">et al.</E>
                         (2019) note that the quantitative processes described and the resulting exposure criteria (
                        <E T="03">i.e.,</E>
                         thresholds and auditory weighting functions) are largely identical to those in Finneran (2016) and NMFS (2016 and 2018). However they differ in that the Southall 
                        <E T="03">et al.</E>
                         (2019a) exposure criteria are more broadly applicable as they include all marine mammal species (rather than those only under NMFS jurisdiction) for all noise exposures (both in air and underwater for amphibious species), and that while the hearing group compositions are identical they renamed the hearing groups.
                    </P>
                    <P>
                        Recent studies on the behavioral responses of cetaceans to sonar examine and continue to demonstrate the importance of not only sound source parameters, but exposure context (
                        <E T="03">e.g.,</E>
                         behavioral state, presence of other animals and social relationships, prey abundance, distance to source, presence of vessels, environmental parameters, etc.) in determining or predicting a behavioral response. Kastelein 
                        <E T="03">et al.</E>
                         (2018) examined the role of sound pressure level (SPL) and duty cycle on the behavior of two captive harbor porpoises when exposed to simulated Navy mid-frequency sonar (53C, 3.5 to 4.1 kHz). Neither harbor porpoise responded to the low duty cycle (2.7 percent) at any of the five SPLs presented, even at the maximum received SPL (143 dB re: 1 µPa). At the higher duty cycle (96 percent), one porpoise responded by increasing his respiration rate at a received SPL of greater than or equal to 119 dB re: 1 µPa, and moved away from the transducer at a received SPL of 143 dB re: 1 µPa. Kastelein 
                        <E T="03">et al.</E>
                         (2018) observed that at the same received SPL and duty cycle, harbor porpoises respond less to 53C sonar sounds than 1-2 kHz, 6-7 kHz, and 25 kHz sonar signals observed in previous studies, but noted that when examining behavioral responses it is important to take into account the spectrum and temporal structure of the signal, the duty cycle, and the psychological interpretation by the animal. Wensveen 
                        <E T="03">et al.</E>
                         (2019) examined the role of sound source (simulated sonar pulses) distance and received level in northern bottlenose whales in an environment without frequent sonar activity using multi-scaled controlled exposure experiments. They observed behavioral avoidance of the sound source over a wide range of distances (0.8-28 km) and estimated avoidance thresholds ranging from received SPLs of 117-126 dB re: 1 µPa. The behavioral response characteristics and avoidance thresholds were comparable to those previously observed in beaked whale studies; however, they did not observe an effect of distance on behavioral response and found that onset and intensity of behavioral response were better predicted by received SPL. When conducting controlled exposure experiments on blue whales Southall 
                        <E T="03">et al.</E>
                         (2019b) observed that after exposure to simulated and operational mid-frequency active sonar, more than 50 percent of blue whales in deep-diving states responded to the sonar, while no behavioral response was observed in shallow-feeding blue whales. The behavioral responses they observed were generally brief, of low to moderate severity, and highly dependent on exposure context (behavioral state, source-to-whale horizontal range, and prey availability). Blue whale response did not follow a simple exposure-response model based on received sound exposure level. In a review of the potential impacts of sonar on beaked whales, Bernaldo de Quirós 
                        <E T="03">et al.</E>
                         (2019) suggested that the effect of mid-frequency active sonar on beaked whales varies among individuals or populations, and that predisposing conditions such as previous exposure to sonar and individual health risk factors may contribute to individual outcomes (such as decompression sickness).
                    </P>
                    <P>Having considered this information, we have preliminarily determined that there is no new information that substantively affects our analysis of impacts on marine mammals and their habitat that appeared in the 2018 AFTT final rule, all of which remains applicable and valid for our assessment of the effects of the Navy's activities during the seven-year period of this rule.</P>
                    <HD SOURCE="HD1">Estimated Take of Marine Mammals</HD>
                    <P>
                        This section indicates the number of takes that NMFS is proposing to authorize, which are based on the amount of take that NMFS anticipates could occur or is likely to occur, depending on the type of take and the methods used to estimate it, as described below. NMFS coordinated closely with the Navy in the development of their incidental take application, and preliminarily agrees that the methods the Navy has put forth described herein and in the 2018 AFTT proposed and final rules to estimate take (including the model, thresholds, and density estimates), and the resulting numbers are based on the best available science and appropriate for 
                        <PRTPAGE P="21148"/>
                        authorization. The number and type of incidental takes that could occur or are likely to occur annually remain identical to those authorized in the 2018 AFTT regulations.
                    </P>
                    <P>Takes are predominantly in the form of harassment, but a small number of serious injuries or mortalities are also possible. For military readiness activities, the MMPA defines “harassment” as (i) Any act that injures or has the significant potential to injure a marine mammal or marine mammal stock in the wild (Level A harassment); or (ii) Any act that disturbs or is likely to disturb a marine mammal or marine mammal stock in the wild by causing disruption of natural behavioral patterns, including, but not limited to, migration, surfacing, nursing, breeding, feeding, or sheltering, to a point where such behavioral patterns are abandoned or significantly altered (Level B harassment).</P>
                    <P>
                        Proposed authorized takes would primarily be in the form of Level B harassment, as use of the acoustic and explosive sources (
                        <E T="03">i.e.,</E>
                         sonar, air guns, pile driving, explosives) is more likely to result in behavioral disruption (rising to the level of a take as described above) or temporary threshold shift (TTS) for marine mammals than other forms of take. There is also the potential for Level A harassment, however, in the form of auditory injury and/or tissue damage (the latter from explosives only) to result from exposure to the sound sources utilized in training and testing activities. Lastly, a limited number of serious injuries or mortalities could occur for four species of mid-frequency cetaceans during ship shock trials and no more than four serious injuries or mortalities total (over the seven-year period) of mysticetes (except for blue whales, Bryde's whales, and North Atlantic right whales) and North Atlantic sperm whales could occur through vessel collisions. Although we analyze the impacts of these potential serious injuries or mortalities that are proposed to be authorized, the required mitigation and monitoring measures are expected to minimize the likelihood that ship strike or these high level explosive exposures (and the associated serious injury or mortality) actually occur.
                    </P>
                    <P>Generally speaking, for acoustic impacts we estimate the amount and type of harassment by considering: (1) Acoustic thresholds above which NMFS believes the best available science indicates marine mammals will be taken by Level B harassment (in this case, as defined in the military readiness definition of Level B harassment included above) or incur some degree of temporary or permanent hearing impairment; (2) the area or volume of water that will be ensonified above these levels in a day or event; (3) the density or occurrence of marine mammals within these ensonified areas; and (4) and the number of days of activities or events.</P>
                    <HD SOURCE="HD2">Acoustic Thresholds</HD>
                    <P>Using the best available science, NMFS, in coordination with the Navy, has established acoustic thresholds that identify the most appropriate received level of underwater sound above which marine mammals exposed to these sound sources could be reasonably expected to experience a disruption in behavior patterns to a point where they are abandoned or significantly altered, or to incur TTS (equated to Level B harassment) or permanent threshold shift (PTS) of some degree (equated to Level A harassment). Thresholds have also been developed to identify the pressure levels above which animals may incur non-auditory injury from exposure to pressure waves from explosive detonation.</P>
                    <P>
                        Despite the quickly evolving science, there are still challenges in quantifying expected behavioral responses that qualify as Level B harassment, especially where the goal is to use one or two predictable indicators 
                        <E T="03">(e.g.,</E>
                         received level and distance) to predict responses that are also driven by additional factors that cannot be easily incorporated into the thresholds (
                        <E T="03">e.g.,</E>
                         context). So, while the new behavioral Level B harassment thresholds have been refined here to better consider the best available science (
                        <E T="03">e.g.,</E>
                         incorporating both received level and distance), they also still, accordingly, have some built-in conservative factors to address the challenge noted. For example, while duration of observed responses in the data are now considered in the thresholds, some of the responses that are informing take thresholds are of a very short duration, such that it is possible some of these responses might not always rise to the level of disrupting behavior patterns to a point where they are abandoned or significantly altered. We describe the application of this Level B harassment threshold as identifying the maximum number of instances in which marine mammals could be reasonably expected to experience a disruption in behavior patterns to a point where they are abandoned or significantly altered. In summary, we believe these behavioral Level B harassment thresholds are the most appropriate method for predicting behavioral Level B harassment given the best available science and the associated uncertainty.
                    </P>
                    <P>
                        We described these acoustic thresholds, none of which have changed, in detail in the 
                        <E T="03">Acoustic Thresholds</E>
                         section and Tables 13 through 22 of the 2018 AFTT final rule; please see the 2018 AFTT final rule for detailed information.
                    </P>
                    <HD SOURCE="HD2">Navy's Acoustic Effects Model</HD>
                    <P>The Navy proposes no changes to the Acoustic Effects Model as described in the 2018 AFTT final rule and there is no new information that would affect the applicability or validity of the Model. Please see the 2018 AFTT final rule for detailed information.</P>
                    <HD SOURCE="HD2">Range to Effects</HD>
                    <P>
                        The Navy proposes no changes from the 2018 AFTT final rule to the type and nature of the specified activities to be conducted during the seven-year period analyzed in this proposed rule, including equipment and sources used and exercises conducted. There is also no new information that would affect the applicability or validity of the ranges to effects previously analyzed for these activities.Therefore the ranges to effects in this proposed rule are identical to those described and analyzed in the 2018 AFTT final rule, including received sound levels that may cause onset of significant behavioral response and TTS and PTS in hearing for each source type or explosives that may cause non-auditory injury. Please see the 
                        <E T="03">Range to Effects</E>
                         section and Tables 23 through 38 of the 2018 AFTT final rule for detailed information.
                    </P>
                    <HD SOURCE="HD2">Marine Mammal Density</HD>
                    <P>The Navy proposes no changes to the methods used to estimate marine mammal density described in the 2018 AFTT final rule and there is no new information that would affect the applicability or validity of these methods. Please see the 2018 AFTT final rule for detailed information.</P>
                    <HD SOURCE="HD2">Take Requests</HD>
                    <P>As in the 2018 AFTT final rule, in its 2019 application, the Navy determined that the three stressors below could result in the incidental taking of marine mammals. NMFS has reviewed the Navy's data and analysis and determined that it is complete and accurate, and NMFS agrees that the following stressors have the potential to result in takes of marine mammals from the Navy's planned activities:</P>
                    <P>
                        • Acoustics (sonar and other transducers; air guns; pile driving/extraction);
                        <PRTPAGE P="21149"/>
                    </P>
                    <P>• Explosives (explosive shock wave and sound, assumed to encompass the risk due to fragmentation); and</P>
                    <P>• Physical Disturbance and Strike (vessel strike).</P>
                    <P>NMFS reviewed and agrees with the Navy's conclusion that acoustic and explosive sources have the potential to result in incidental takes of marine mammals by harassment, serious injury, or mortality. NMFS carefully reviewed the Navy's analysis and conducted its own analysis of vessel strikes, determining that the likelihood of any particular species of large whale being struck is quite low. Nonetheless, NMFS agrees that vessel strikes have the potential to result in incidental take from serious injury or mortality for certain species of large whales and the Navy has specifically requested coverage for these species. Therefore, the likelihood of vessel strikes, and later the effects of the incidental take that is being proposed to be authorized, has been fully analyzed and is described below.</P>
                    <P>Regarding the quantification of expected takes from acoustic and explosive sources (by Level A and Level B harassment, as well as mortality resulting from exposure to explosives), the number of takes are based directly on the level of activities (days, hours, counts, etc., of different activities and events) in a given year. In the 2018 AFTT final rule, take estimates across the five-years were based on the Navy conducting three years of a representative level of activity and two years of maximum level of activity. Consistent with the pattern set forth in the 2017 application, the 2018 AFTT FEIS/OEIS, and the 2018 AFTT final rule, the Navy proposes to add one additional representative year and one additional maximum year to determine the predicted take numbers in this rule. Specifically, as in the 2018 AFTT final rule, here the Navy proposes to use the maximum annual level to calculate annual takes (which would remain identical to what was determined in the 2018 AFTT final rule), and the sum of all years (four representative and three maximum) to calculate the seven-year totals for this rule. The Navy is not proposing to conduct any additional ship shock activities, and therefore both the total number and annual number of ship shock takes estimated and requested for the seven-year period is the same as the number requested in the five-year period under the 2018 AFTT final rule.</P>
                    <P>
                        The quantitative analysis process used for the 2018 AFTT FEIS/OEIS and the 2017 and 2019 Navy applications to estimate potential exposures to marine mammals resulting from acoustic and explosive stressors is detailed in the technical report titled 
                        <E T="03">Quantifying Acoustic Impacts on Marine Mammals and Sea Turtles: Methods and Analytical Approach for Phase III Training and Testing</E>
                         (U.S. Department of the Navy, 2018). The Navy Acoustic Effects Model estimates acoustic and explosive effects without taking mitigation into account; therefore, the model overestimates predicted impacts on marine mammals within mitigation zones. To account for mitigation for marine species in the take estimates, the Navy conducts a quantitative assessment of mitigation. The Navy conservatively quantifies the manner in which procedural mitigation is expected to reduce model-estimated PTS to TTS for exposures to sonar and other transducers, and reduces model-estimated mortality to injury for exposures to explosives. For a complete explanation of the process for assessing the effects of mitigation, see the 2017 Navy application and the 2018 AFTT final rule. The extent to which the mitigation areas reduce impacts on the affected species and stocks is addressed separately in the 
                        <E T="03">Preliminary Analysis and Negligible Impact Determination</E>
                         section.
                    </P>
                    <P>
                        No changes have been made to the quantitative analysis process to estimate potential exposures to marine mammals resulting from acoustic and explosive stressors and calculate take estimates. In addition, there is no new information that would call into question the validity of the Navy's quantitative analysis process. Please see the documents described in the paragraph above, the 2018 AFTT proposed rule, and the 2018 AFTT final rule for detailed descriptions of these analyses. In summary, we believe the Navy's methods, including the method for incorporating mitigation and avoidance, are the most appropriate methods for predicting PTS, TTS, and behavioral disruption. But even with the consideration of mitigation and avoidance, given some of the more conservative components of the methodology (
                        <E T="03">e.g.,</E>
                         the thresholds do not consider ear recovery between pulses), we would describe the application of these methods as identifying the maximum number of instances in which marine mammals would be reasonably expected to be taken through PTS, TTS, or behavioral disruption.
                    </P>
                    <HD SOURCE="HD3">Summary of Requested Take From Training and Testing Activities</HD>
                    <P>
                        Based on the methods discussed in the previous sections and the Navy's model and quantitative assessment of mitigation, the Navy provided its take estimate and request for authorization of takes incidental to the use of acoustic and explosive sources for training and testing activities both annually (based on the maximum number of activities that could occur per 12-month period) and over the seven-year period covered by the 2019 Navy application. Annual takes (based on the maximum number of activities that could occur per 12-month period) are identical to those presented in Tables 39 through 41 in the 
                        <E T="03">Take Requests</E>
                         section of the 2018 AFTT final rule. The 2019 Navy application also includes the Navy's take estimate and request for vessel strikes due to vessel movement in the AFTT Study Area and individual small and large ship shock trials over a seven-year period. The Navy proposes no additional ship shock trials, so the estimated and requested takes from ship shock trials are the same as those authorized in the 2018 AFTT final rule. NMFS has reviewed the Navy's data, methodology, and analysis and determined that it is complete and accurate. NMFS agrees that the estimates for incidental takes by harassment from all sources as well as the incidental takes by serious injury or mortality from explosives requested for authorization are reasonably expected to occur. NMFS also agrees that the takes by serious injury or mortality as a result of vessel strikes could occur. The total amount of estimated incidental take over the seven years covered by the 2019 Navy application is less than the sum total of each year because although the annual estimates are based on the maximum number of activities per year and therefore the maximum estimated takes, the seven-year take estimates are based on the sum of three maximum years and four representative years.
                    </P>
                    <HD SOURCE="HD3">Estimated Harassment Take From Training Activities</HD>
                    <P>
                        For training activities, Table 10 summarizes the Navy's take estimate and request and the maximum amount and type of Level A and Level B harassment for the seven-year period covered by the 2019 Navy application that NMFS concurs is reasonably expected to occur by species or stock. For the estimated amount and type of Level A harassment and Level B harassment annually, see Table 39 in the 2018 AFTT final rule. Note that take by Level B harassment includes both behavioral disruption and TTS. Navy Figures 6.4-10 through 6.5-39 in Section 6 of the 2017 Navy application illustrate the comparative amounts of TTS and behavioral disruption for each species annually, noting that if a modeled marine mammal was “taken” 
                        <PRTPAGE P="21150"/>
                        through exposure to both TTS and behavioral disruption in the model, it was recorded as a TTS.
                    </P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r50,12,12">
                        <TTITLE>Table 10—Seven-Year Total Species- and Stock-Specific Take Estimates Proposed for Authorization From Acoustic and Explosive Sound Source Effects for All Training Activities</TTITLE>
                        <BOXHD>
                            <CHED H="1">Species</CHED>
                            <CHED H="1">Stock</CHED>
                            <CHED H="1">
                                7-Year total 
                                <SU>1</SU>
                            </CHED>
                            <CHED H="2">Level B</CHED>
                            <CHED H="2">Level A</CHED>
                        </BOXHD>
                        <ROW EXPSTB="03" RUL="s">
                            <ENT I="21">
                                <E T="0714">Suborder Mysticeti (baleen whales)</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="22">
                                <E T="03">Family Balaenidae (right whales):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">North Atlantic right whale *</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>1,644</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Balaenopteridae (roquals):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Blue whale *</ENT>
                            <ENT>Western North Atlantic (Gulf of St. Lawrence)</ENT>
                            <ENT>171</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bryde's whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>5</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>No Stock Designation</ENT>
                            <ENT>1,351</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Minke whale</ENT>
                            <ENT>Canadian East Coast</ENT>
                            <ENT>15,824</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Fin whale *</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>10,225</ENT>
                            <ENT>19</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Humpback whale</ENT>
                            <ENT>Gulf of Maine</ENT>
                            <ENT>1,564</ENT>
                            <ENT>4</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="03">Sei whale *</ENT>
                            <ENT>Nova Scotia</ENT>
                            <ENT>1,964</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW EXPSTB="03" RUL="s">
                            <ENT I="21">
                                <E T="0714">Suborder Odontoceti (toothed whales)</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="22">
                                <E T="03">Family Physeteridae (sperm whale):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Sperm whale *</ENT>
                            <ENT>Gulf of Mexico Oceanic</ENT>
                            <ENT>167</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>North Atlantic</ENT>
                            <ENT>96,479</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Kogiidae (sperm whales):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Dwarf sperm whale</ENT>
                            <ENT>Gulf of Mexico Oceanic</ENT>
                            <ENT>103</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>56,060</ENT>
                            <ENT>68</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pygmy sperm whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>103</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>56,060</ENT>
                            <ENT>68</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Ziphiidae (beaked whales):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Blainville's beaked whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>244</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>85,661</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Cuvier's beaked whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>242</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>317,180</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Gervais' beaked whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>244</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>85,661</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Northern bottlenose whale</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>7,504</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Sowersby's beaked whale</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>85,661</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">True's beaked whale</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>85,661</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Delphinidae (dolphins):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Atlantic spotted dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>6,584</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>804,058</ENT>
                            <ENT>64</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Atlantic white-sided dolphin</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>99,615</ENT>
                            <ENT>3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bottlenose dolphin</ENT>
                            <ENT>Choctawhatchee Bay</ENT>
                            <ENT>46</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Gulf of Mexico Eastern Coastal</ENT>
                            <ENT>166</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Gulf of Mexico Northern Coastal</ENT>
                            <ENT>1,524</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Gulf of Mexico Western Coastal</ENT>
                            <ENT>16,778</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Indian River Lagoon Estuarine System</ENT>
                            <ENT>1,980</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Jacksonville Estuarine System</ENT>
                            <ENT>589</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Mississippi Sound, Lake Borgne, Bay Boudreau</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Northern Gulf of Mexico Continental Shelf</ENT>
                            <ENT>10,918</ENT>
                            <ENT>13</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Northern Gulf of Mexico Oceanic</ENT>
                            <ENT>1,356</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Northern North Carolina Estuarine System</ENT>
                            <ENT>16,089</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Southern North Carolina Estuarine System</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic Northern Florida Coastal</ENT>
                            <ENT>6,060</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic Central Florida Coastal</ENT>
                            <ENT>35,861</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic Northern Migratory Coastal</ENT>
                            <ENT>175,237</ENT>
                            <ENT>30</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic Offshore</ENT>
                            <ENT>2,062,942</ENT>
                            <ENT>269</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic South Carolina/Georgia Coastal</ENT>
                            <ENT>28,814</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic Southern Migratory Coastal</ENT>
                            <ENT>81,155</ENT>
                            <ENT>14</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Clymene dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>694</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>463,220</ENT>
                            <ENT>19</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">False killer whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>291</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>54,818</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Fraser's dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>418</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>26,155</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Killer whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>5</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>522</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Long-finned pilot whale</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>116,412</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Melon-headed whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>493</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>246,178</ENT>
                            <ENT>4</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="21151"/>
                            <ENT I="03">Pantropical spotted dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>3,959</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>964,072</ENT>
                            <ENT>16</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pygmy killer whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>118</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>43,009</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Risso's dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>276</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>140,368</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Rough-toothed dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>606</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>129,594</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Short-beaked common dolphin</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>1,467,625</ENT>
                            <ENT>87</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Short-finned pilot whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>251</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>210,736</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Spinner dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>1,593</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>487,644</ENT>
                            <ENT>9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Striped dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>471</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>631,680</ENT>
                            <ENT>22</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">White-beaked dolphin</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>269</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Phocoenidae (porpoises):</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="03">Harbor porpoise</ENT>
                            <ENT>Gulf of Maine/Bay of Fundy</ENT>
                            <ENT>206,071</ENT>
                            <ENT>1,121</ENT>
                        </ROW>
                        <ROW EXPSTB="03" RUL="s">
                            <ENT I="21">
                                <E T="0714">Suborder Pinnipedia</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="22">
                                <E T="03">Family Phocidae (true seals):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Gray seal</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>10,038</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Harbor seal</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>16,277</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Harp seal</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>59,063</ENT>
                            <ENT>6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Hooded seal</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>882</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             The estimated amount and type of Level A harassment and Level B harassment annually are identical to those presented in Table 39 in the 2018 AFTT final rule.
                        </TNOTE>
                        <TNOTE>* ESA-listed species (all stocks) within the AFTT Study Area.</TNOTE>
                        <TNOTE>
                            <E T="0731">†</E>
                             NSD: No stock designated.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Estimated Harassment Take From Testing Activities</HD>
                    <P>For testing activities (excluding ship shock trials), Table 11 summarizes the Navy's take estimate and request and the maximum amount and type of Level A harassment and Level B harassment for the seven-year period covered by the 2019 Navy application that NMFS concurs is reasonably expected to occur by species or stock. For the estimated amount and type of Level A harassment and Level B harassment annually, see Table 40 in the 2018 AFTT final rule. Note that take by Level B harassment includes both behavioral disruption and TTS. Navy Figures 6.4-10 through 6.5-39 in Section 6 of the 2017 Navy application illustrate the comparative amounts of TTS and behavioral disruption for each species annually, noting that if a “taken” animat was exposed to both TTS and behavioral disruption in the model, it was recorded as a TTS.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r50,12,12">
                        <TTITLE>Table 11—Seven-Year Total Species and Stock-Specific Take Estimates Proposed for Authorization From Acoustic and Explosive Sound Source Effects for All Testing Activities (Excluding Ship Shock Trials)</TTITLE>
                        <BOXHD>
                            <CHED H="1">Species</CHED>
                            <CHED H="1">Stock</CHED>
                            <CHED H="1">
                                7-Year total 
                                <SU>1</SU>
                            </CHED>
                            <CHED H="2">Level B</CHED>
                            <CHED H="2">Level A</CHED>
                        </BOXHD>
                        <ROW EXPSTB="03" RUL="s">
                            <ENT I="21">
                                <E T="0714">Suborder Mysticeti (baleen whales)</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">
                                <E T="03">Family Balaenidae (right whales):</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="03">North Atlantic right whale *</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>1,528</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Balaenopteridae (roquals):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Blue whale *</ENT>
                            <ENT>Western North Atlantic (Gulf of St. Lawrence)</ENT>
                            <ENT>127</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bryde's whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>358</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>No Stock Designation</ENT>
                            <ENT>856</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Minke whale</ENT>
                            <ENT>Canadian East Coast</ENT>
                            <ENT>11,155</ENT>
                            <ENT>9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Fin whale *</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>24,808</ENT>
                            <ENT>22</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Humpback whale</ENT>
                            <ENT>Gulf of Maine</ENT>
                            <ENT>3,380</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="03">Sei whale *</ENT>
                            <ENT>Nova Scotia</ENT>
                            <ENT>3,262</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW EXPSTB="03" RUL="s">
                            <ENT I="21">
                                <E T="0714">Suborder Odontoceti (toothed whales)</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="22">
                                <E T="03">Family Physeteridae (sperm whale):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Sperm whale *</ENT>
                            <ENT>Gulf of Mexico Oceanic</ENT>
                            <ENT>7,315</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="21152"/>
                            <ENT I="22"> </ENT>
                            <ENT>North Atlantic</ENT>
                            <ENT>71,820</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Kogiidae (sperm whales):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Dwarf sperm whale</ENT>
                            <ENT>Gulf of Mexico Oceanic</ENT>
                            <ENT>4,787</ENT>
                            <ENT>38</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>29,368</ENT>
                            <ENT>91</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pygmy sperm whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>4,787</ENT>
                            <ENT>38</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>29,368</ENT>
                            <ENT>91</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Ziphiidae (beaked whales):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Blainville's beaked whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>9,368</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>68,738</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Cuvier's beaked whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>9,757</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>252,367</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Gervais' beaked whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>9,368</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>68,738</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Northern bottlenose whale</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>6,231</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Sowersby's beaked whale</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>68,903</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">True's beaked whale</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>68,903</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Delphinidae (dolphins):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Atlantic spotted dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>473,262</ENT>
                            <ENT>18</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>708,931</ENT>
                            <ENT>72</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Atlantic white-sided dolphin</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>210,578</ENT>
                            <ENT>8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bottlenose dolphin</ENT>
                            <ENT>Choctawhatchee Bay</ENT>
                            <ENT>6,297</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Gulf of Mexico Eastern Coastal</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Gulf of Mexico Northern Coastal</ENT>
                            <ENT>108,154</ENT>
                            <ENT>7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Gulf of Mexico Western Coastal</ENT>
                            <ENT>25,200</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Indian River Lagoon Estuarine System</ENT>
                            <ENT>21</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Jacksonville Estuarine System</ENT>
                            <ENT>20</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Mississippi Sound, Lake Borgne, Bay Boudreau</ENT>
                            <ENT>5</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Northern Gulf of Mexico Continental Shelf</ENT>
                            <ENT>841,076</ENT>
                            <ENT>56</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Northern Gulf of Mexico Oceanic</ENT>
                            <ENT>95,044</ENT>
                            <ENT>8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Northern North Carolina Estuarine System</ENT>
                            <ENT>746</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Southern North Carolina Estuarine System</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic Northern Florida Coastal</ENT>
                            <ENT>2,263</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic Central Florida Coastal</ENT>
                            <ENT>15,409</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic Northern Migratory Coastal</ENT>
                            <ENT>79,042</ENT>
                            <ENT>20</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic Offshore</ENT>
                            <ENT>794,581</ENT>
                            <ENT>161</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic South Carolina/Georgia Coastal</ENT>
                            <ENT>11,232</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic Southern Migratory Coastal</ENT>
                            <ENT>29,176</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Clymene dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>27,841</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>234,001</ENT>
                            <ENT>12</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">False killer whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>12,788</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>24,580</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Fraser's dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>7,452</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>8,270</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Killer whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>212</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>264</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Long-finned pilot whale</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>131,095</ENT>
                            <ENT>11</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Melon-headed whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>20,324</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>109,192</ENT>
                            <ENT>6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pantropical spotted dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>169,678</ENT>
                            <ENT>6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>495,207</ENT>
                            <ENT>26</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pygmy killer whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>4,771</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>18,609</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Risso's dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>10,929</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>132,141</ENT>
                            <ENT>9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Rough-toothed dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>26,033</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>58,008</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Short-beaked common dolphin</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>2,351,361</ENT>
                            <ENT>101</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Short-finned pilot whale</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>12,041</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>111,326</ENT>
                            <ENT>10</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Spinner dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>51,039</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>218,786</ENT>
                            <ENT>10</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Striped dolphin</ENT>
                            <ENT>Northern Gulf of Mexico</ENT>
                            <ENT>16,344</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>652,197</ENT>
                            <ENT>32</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">White-beaked dolphin</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>300</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Phocoenidae (porpoises):</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="03">Harbor porpoise</ENT>
                            <ENT>Gulf of Maine/Bay of Fundy</ENT>
                            <ENT>811,201</ENT>
                            <ENT>1,405</ENT>
                        </ROW>
                        <ROW EXPSTB="03" RUL="s">
                            <PRTPAGE P="21153"/>
                            <ENT I="21">
                                <E T="0714">Suborder Pinnipedia</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="22">
                                <E T="03">Family Phocidae (true seals):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Gray seal</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>6,130</ENT>
                            <ENT>14</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Harbor seal</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>9,941</ENT>
                            <ENT>23</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Harp seal</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>53,646</ENT>
                            <ENT>17</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Hooded seal</ENT>
                            <ENT>Western North Atlantic</ENT>
                            <ENT>5,335</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             The estimated amount and type of Level A harassment and Level B harassment annually are identical to those presented in Table 40 in the 2018 AFTT final rule.
                        </TNOTE>
                        <TNOTE>* ESA-listed species (all stocks) within the AFTT Study Area.</TNOTE>
                        <TNOTE>
                            <E T="0731">†</E>
                             NSD: No stock designated.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Estimated Take From Ship Shock</HD>
                    <P>For ship shock trials, Table 12 summarizes the Navy's take estimate and request and the maximum amount and type of Level A and Level B harassment and serious injury/mortality for the seven-year period covered by the Navy application that NMFS concurs is reasonably expected to occur by species or stock per small and large ship shock events. For the estimated amount and type of Level A harassment, Level B harassment, and serious injury/mortality annually, see Table 41 in the 2018 AFTT final rule. The Navy proposed no additional ship shock trials over the additional two years covered by the 2019 Navy application, so the estimated and requested takes are the same as those authorized in the 2018 AFTT final rule.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,12,12">
                        <TTITLE>Table 12—Seven-Year Total Species and Stock-Specific Take Estimates Proposed for Authorization From Ship Shock Trials</TTITLE>
                        <BOXHD>
                            <CHED H="1">Species</CHED>
                            <CHED H="1">
                                7-Year total 
                                <SU>1</SU>
                            </CHED>
                            <CHED H="2">Level B</CHED>
                            <CHED H="2">Level A</CHED>
                            <CHED H="2">Mortality</CHED>
                        </BOXHD>
                        <ROW EXPSTB="03" RUL="s">
                            <ENT I="21">
                                <E T="0714">Suborder Mysticeti (baleen whales)</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="22">
                                <E T="03">Family Balaenidae (right whales):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">North Atlantic right whale *</ENT>
                            <ENT>5</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Balaenopteridae (roquals):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Blue whale *</ENT>
                            <ENT>1</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bryde's whale</ENT>
                            <ENT>15</ENT>
                            <ENT>1</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Minke whale</ENT>
                            <ENT>96</ENT>
                            <ENT>6</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Fin whale *</ENT>
                            <ENT>627</ENT>
                            <ENT>36</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Humpback whale</ENT>
                            <ENT>44</ENT>
                            <ENT>2</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="03">Sei whale *</ENT>
                            <ENT>63</ENT>
                            <ENT>7</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW EXPSTB="03" RUL="s">
                            <ENT I="21">
                                <E T="0714">Suborder Odontoceti (toothed whales)</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Physeteridae (sperm whale):</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="03">Sperm whale *</ENT>
                            <ENT>6</ENT>
                            <ENT>7</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Kogiidae (sperm whales):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Dwarf sperm whale</ENT>
                            <ENT>229</ENT>
                            <ENT>154</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pygmy sperm whale</ENT>
                            <ENT>229</ENT>
                            <ENT>154</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Ziphiidae (beaked whales):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Blainville's beaked whale</ENT>
                            <ENT>4</ENT>
                            <ENT>1</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Cuvier's beaked whale</ENT>
                            <ENT>8</ENT>
                            <ENT>6</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Gervais' beaked whale</ENT>
                            <ENT>4</ENT>
                            <ENT>1</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Northern bottlenose whale</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Sowersby's beaked whale</ENT>
                            <ENT>4</ENT>
                            <ENT>1</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">True's beaked whale</ENT>
                            <ENT>4</ENT>
                            <ENT>1</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Delphinidae (dolphins):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Atlantic spotted dolphin</ENT>
                            <ENT>26</ENT>
                            <ENT>24</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Atlantic white-sided dolphin</ENT>
                            <ENT>6</ENT>
                            <ENT>12</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bottlenose dolphin</ENT>
                            <ENT>55</ENT>
                            <ENT>54</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Clymene dolphin</ENT>
                            <ENT>15</ENT>
                            <ENT>23</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">False killer whale</ENT>
                            <ENT>2</ENT>
                            <ENT>1</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Fraser's dolphin</ENT>
                            <ENT>2</ENT>
                            <ENT>3</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Killer whale</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Long-finned pilot whale</ENT>
                            <ENT>11</ENT>
                            <ENT>12</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Melon-headed whale</ENT>
                            <ENT>8</ENT>
                            <ENT>7</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pantropical spotted dolphin</ENT>
                            <ENT>31</ENT>
                            <ENT>29</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pygmy killer whale</ENT>
                            <ENT>1</ENT>
                            <ENT>1</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="21154"/>
                            <ENT I="03">Risso's dolphin</ENT>
                            <ENT>6</ENT>
                            <ENT>4</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Rough-toothed dolphin</ENT>
                            <ENT>6</ENT>
                            <ENT>2</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Short-beaked common dolphin</ENT>
                            <ENT>187</ENT>
                            <ENT>260</ENT>
                            <ENT>6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Short-finned pilot whale</ENT>
                            <ENT>10</ENT>
                            <ENT>11</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Spinner dolphin</ENT>
                            <ENT>46</ENT>
                            <ENT>48</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Striped dolphin</ENT>
                            <ENT>22</ENT>
                            <ENT>36</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">White-beaked dolphin</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Family Phocoenidae (porpoises):</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="03">Harbor porpoise</ENT>
                            <ENT>249</ENT>
                            <ENT>204</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW EXPSTB="03" RUL="s">
                            <ENT I="21">
                                <E T="0714">Suborder Pinnipedia</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="22">
                                <E T="03">Family Phocidae (true seals):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Gray seal</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Harbor seal</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Harp seal</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Hooded seal</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             The estimated amount and type of Level A harassment and Level B harassment and serious injury/mortality annually are identical to those presented in Table 41 in the 2018 AFTT final rule.
                        </TNOTE>
                        <TNOTE>* ESA-listed species (all stocks) within the AFTT Study Area.</TNOTE>
                        <TNOTE>
                            <E T="0731">†</E>
                             NSD: No stock designated.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD3">Estimated Take From Vessel Strikes</HD>
                    <P>
                        Vessel strikes from commercial, recreational, and military vessels are known to affect large whales and have resulted in serious injury and occasional fatalities to cetaceans (Berman-Kowalewski 
                        <E T="03">et al.,</E>
                         2010; Calambokidis, 2012; Douglas 
                        <E T="03">et al.,</E>
                         2008; Laggner 2009; Lammers 
                        <E T="03">et al.,</E>
                         2003). Records of collisions date back to the early 17th century, and the worldwide number of collisions appears to have increased steadily during recent decades (Laist 
                        <E T="03">et al.,</E>
                         2001; Ritter, 2012).
                    </P>
                    <P>
                        Numerous studies of interactions between surface vessels and marine mammals have demonstrated that free-ranging marine mammals often, but not always (
                        <E T="03">e.g.,</E>
                         McKenna 
                        <E T="03">et al.,</E>
                         2015), engage in avoidance behavior when surface vessels move toward them. It is not clear whether these responses are caused by the physical presence of a surface vessel, the underwater noise generated by the vessel, or an interaction between the two (Amaral and Carlson, 2005; Au and Green, 2000; Bain 
                        <E T="03">et al.,</E>
                         2006; Bauer 1986; Bejder 
                        <E T="03">et al.,</E>
                         1999; Bejder and Lusseau, 2008; Bejder 
                        <E T="03">et al.,</E>
                         2009; Bryant 
                        <E T="03">et al.,</E>
                         1984; Corkeron, 1995; Erbe, 2002; Félix, 2001; Goodwin and Cotton, 2004; Lemon 
                        <E T="03">et al.,</E>
                         2006; Lusseau, 2003; Lusseau, 2006; Magalhaes 
                        <E T="03">et al.,</E>
                         2002; Nowacek 
                        <E T="03">et al.,</E>
                         2001; Richter 
                        <E T="03">et al.,</E>
                         2003; Scheidat 
                        <E T="03">et al.,</E>
                         2004; Simmonds, 2005; Watkins, 1986; Williams 
                        <E T="03">et al.,</E>
                         2002; Wursig 
                        <E T="03">et al.,</E>
                         1998). Several authors suggest that the noise generated during motion is probably an important factor (Blane and Jaakson, 1994; Evans 
                        <E T="03">et al.,</E>
                         1992; Evans 
                        <E T="03">et al.,</E>
                         1994). Water disturbance may also be a factor. These studies suggest that the behavioral responses of marine mammals to surface vessels are similar to their behavioral responses to predators. Avoidance behavior is expected to be even stronger in the subset of instances that the Navy is conducting training or testing activities using active sonar or explosives.
                    </P>
                    <P>
                        The marine mammals most vulnerable to vessel strikes are those that spend extended periods of time at the surface in order to restore oxygen levels within their tissues after deep dives (
                        <E T="03">e.g.,</E>
                         the sperm whale). In addition, some baleen whales, such as the NARW seem generally unresponsive to vessel sound, making them more susceptible to vessel collisions (Nowacek 
                        <E T="03">et al.,</E>
                         2004). These species are primarily large, slower moving whales.
                    </P>
                    <P>
                        Some researchers have suggested the relative risk of a vessel strike can be assessed as a function of animal density and the magnitude of vessel traffic (
                        <E T="03">e.g.,</E>
                         Fonnesbeck 
                        <E T="03">et al.,</E>
                         2008; Vanderlaan 
                        <E T="03">et al.,</E>
                         2008). Differences among vessel types also influence the probability of a vessel strike. The ability of any ship to detect a marine mammal and avoid a collision depends on a variety of factors, including environmental conditions, ship design, size, speed, and personnel, as well as the behavior of the animal. Vessel speed, size, and mass are all important factors in determining if injury or death of a marine mammal is likely due to a vessel strike. For large vessels, speed and angle of approach can influence the severity of a strike. For example, Vanderlaan and Taggart (2007) found that between vessel speeds of 8.6 and 15 knots, the probability that a vessel strike is lethal increases from 0.21 to 0.79. Large whales also do not have to be at the water's surface to be struck. Silber 
                        <E T="03">et al.</E>
                         (2010) found when a whale is below the surface (about one to two times the vessel draft), there is likely to be a pronounced propeller suction effect. This suction effect may draw the whale into the hull of the ship, increasing the probability of propeller strikes. 
                    </P>
                    <P>
                        There are some key differences between the operation of military and non-military vessels, which make the likelihood of a military vessel striking a whale lower than some other vessels (
                        <E T="03">e.g.,</E>
                         commercial merchant vessels). Key differences include:
                    </P>
                    <P>• Many military ships have their bridges positioned closer to the bow, offering better visibility ahead of the ship (compared to a commercial merchant vessel).</P>
                    <P>• There are often aircraft associated with the training or testing activity (which can serve as Lookouts), which can more readily detect cetaceans in the vicinity of a vessel or ahead of a vessel's present course before crew on the vessel would be able to detect them.</P>
                    <P>
                        • Military ships are generally more maneuverable than commercial merchant vessels, and if cetaceans are spotted in the path of the ship, could be capable of changing course more quickly.
                        <PRTPAGE P="21155"/>
                    </P>
                    <P>• The crew size on military vessels is generally larger than merchant ships, allowing for stationing more trained Lookouts on the bridge. At all times when vessels are underway, trained Lookouts and bridge navigation teams are used to detect objects on the surface of the water ahead of the ship, including cetaceans. Additional Lookouts, beyond those already stationed on the bridge and on navigation teams, are positioned as Lookouts during some activities.</P>
                    <P>• When submerged, submarines are generally slow moving (to avoid detection) and therefore marine mammals at depth with a submarine are likely able to avoid collision with the submarine. When a submarine is transiting on the surface, there are Lookouts serving the same function as they do on surface ships.</P>
                    <P>Vessel strike to marine mammals is not associated with any specific training or testing activity but is rather an extremely limited and sporadic, but possible, accidental result of Navy vessel movement within the AFTT Study Area or while in transit.</P>
                    <P>
                        There have been three recorded Navy vessel strikes (one in 2011 and two in 2012) of large whales in the AFTT Study Area from 2009 through 2018 (ten years), the period in which the Navy began implementing effective mitigation measures to reduce the likelihood of vessel strikes. Two of the vessel strikes occurred in the Virginia Capes Range Complex and one occurred in the lower Chesapeake Bay. One of the whales in 2012 had features suggesting it was most likely a humpback whale. Note that while the Navy is generally unable to identify the species of whale is it unlikely the unidentified whales were NARW as the strikes occurred in areas where, or times of year when, NARW are not known to be present. In order to account for the accidental nature of vessel strikes to large whales in general, and the potential risk from any vessel movement within the AFTT Study Area within the seven-year period, the Navy requested incidental takes based on probabilities derived from a Poisson distribution using ship strike data between 2009 and 2018 in the AFTT Study Area (the time period from when current mitigation measures were instituted until the Navy conducted the analysis for the 2019 Navy application, with no new ship strikes occurring since this analysis), as well as historical at-sea days in the AFTT Study Area from 2009-2018 and estimated potential at-sea days for the period from 2018 to 2025 covered by the requested regulations. This distribution predicted the probabilities of a specific number of strikes (n=0, 1, 2, etc.) over the period from 2018 to 2025. The analysis is described in detail in Chapter 6 of the Navy's 2017 and 2019 applications (and further refined in the Navy's revised ship strike analysis posted on NMFS' website 
                        <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/incidental-take-authorizations-military-readiness-activities</E>
                        ).
                    </P>
                    <P>For the same reasons listed above describing why a Navy vessel strike is comparatively unlikely, it is highly unlikely that a Navy vessel would strike a whale, dolphin, porpoise, or pinniped without detecting it and, accordingly, NMFS is confident that the Navy's reported strikes are accurate and appropriate for use in the analysis. Specifically, Navy ships have multiple Lookouts, including on the forward part of the ship that can visually detect a hit animal, in the unlikely event ship personnel do not feel the strike (which has occasionally occurred). Navy's strict internal procedures and mitigation requirements include reporting of any vessel strikes of marine mammals, and the Navy's discipline, extensive training (not only for detecting marine mammals, but for detecting and reporting any potential navigational obstruction), and strict chain of command give NMFS a high level of confidence that all strikes actually get reported.</P>
                    <P>The Navy used the three whale strikes since 2009 in their calculations to determine the number of strikes likely to result from their activities (although worldwide strike information, from all Navy activities and other strikes, was used to inform the species that may be struck). The Navy evaluated data beginning in 2009, as that was the start of the Navy's Marine Species Awareness Training and adoption of additional mitigation measures to address ship strike, which will remain in place along with additional mitigation measures during the seven years of this rule.</P>
                    <P>The updated probability analysis in the 2019 Navy application concluded that there was a 12 percent chance that zero whales would be struck by Navy vessels over the next seven years in the AFTT Study Area, indicating an 88 percent chance that at least one whale would be struck over the next seven years. The analysis also concludes that there is a 10 percent chance of striking four whales over the seven-year period. Based on the revised analysis, the Navy requests coverage for one additional large whale mortality not previously included in the 2018 AFTT final rule bringing the total from three vessel strikes over five years to four vessel strikes over seven years. NMFS agrees that there is some probability that the Navy could strike, and take by serious injury or mortality, up to four large whales incidental to training and testing activities within the AFTT Study Area over the course of the seven years covered by this proposed rule.</P>
                    <P>
                        Small delphinids, porpoises, and pinnipeds are not expected to be struck by Navy vessels. In addition to the reasons listed above that make it unlikely that the Navy will hit a large whale (more maneuverable ships, larger crew, etc.), the following are additional reasons that vessel strike of dolphins, small whales, porpoises, and pinnipeds is very unlikely. Dating back more than 20 years and for as long as it has kept records, the Navy has no records of individuals of these groups being struck by a vessel as a result of Navy activities and, further, their smaller size and maneuverability make a strike unlikely. Also, NMFS has never received any reports from other authorized activities indicating that these species have been struck by vessels. Worldwide ship strike records show little evidence of strikes of these groups from the shipping sector and larger vessels, and the majority of the Navy's activities involving faster-moving vessels (that could be considered more likely to hit a marine mammal) are located in offshore areas where smaller delphinid, porpoise, and pinniped densities are lower. Based on this information, NMFS concurs with the Navy's assessment and recognizes the potential for incidental take by vessel strike of large whales only (
                        <E T="03">i.e.,</E>
                         no dolphins, small whales, porpoises, or pinnipeds) over the course of the seven-year period analyzed here from training and testing activities.
                    </P>
                    <P>
                        Taking into account the available information regarding how many of any given stock could be struck and therefore should be proposed for authorization for take NMFS considered two factors in addition to those considered in the Navy's request: (1) The relative likelihood of hitting one stock versus another based on available strike data from all vessel types as denoted in the SARs and (2) whether the Navy has ever definitively struck an individual from a particular stock and, if so, how many times. To address number (1) above, NMFS compiled information from NMFS' SARs on detected annual rates of large whale serious injury and mortality from vessel collisions (Table 13). The annual rates of large whale serious injury and mortality from vessel collisions from the SARs help inform the relative susceptibility of large whale species to vessel strike in the Atlantic Ocean and the Gulf of Mexico. We summed the annual rates of mortality and serious 
                        <PRTPAGE P="21156"/>
                        injury from vessel collisions as reported in the SARs, then divided each species' annual rate by this sum to get the relative likelihood. To estimate the percent likelihood of striking a particular species of large whale, we multiplied the relative likelihood of striking each species by the total probability of striking a whale (
                        <E T="03">i.e.,</E>
                         88 percent, as described by the Navy's probability analysis). We also calculated the percent likelihood of striking a particular species of large whale twice by squaring the value estimated for the probability of striking a particular species of whale once (
                        <E T="03">i.e.,</E>
                         to calculate the probability of an event occurring twice, multiply the probability of the first event by the second). We note that these probabilities vary from year to year as the average annual mortality for a given five-year window changes (and we include the annual averages from 2017 and 2018 draft SARs in Table 13 to illustrate); however, over the years and through changing SARs, stocks tend to consistently maintain a relatively higher or relatively lower likelihood of being struck. The analysis indicates that there is a very low percent chance of striking any particular species or stock more than once except for humpback whales, as shown in Table 13. The probabilities calculated as described above are then considered in combination with the information indicating the species that the Navy has definitively hit in the AFTT Study Area since 1995 (since they started tracking consistently). Accordingly, stocks that have no record of ever having been struck by any vessel are considered unlikely to be struck by the Navy in the seven-year period of the rule. Stocks that have never been struck by the Navy, have rarely been struck by other vessels, and have a low percent likelihood based on the SAR calculation and a low relative abundance are also considered unlikely to be struck by the Navy during the seven-year rule.
                    </P>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,12,12,12,12,12,12">
                        <TTITLE>Table 13—Annual Rates of Mortality and Serious Injury (M/SI) From Vessel Collisions Compiled From NMFS Draft 2018 Stock Assessment Reports (SARs) and Estimated Percent Chance of Striking Each Large Whale Species in the AFTT Study Area Over a Seven-Year Period</TTITLE>
                        <BOXHD>
                            <CHED H="1">
                                Species 
                                <LI>
                                    (stock) 
                                    <SU>1</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                Annual rate of M/SI from 
                                <LI>vessel collision </LI>
                                <LI>(2017 SARs)</LI>
                            </CHED>
                            <CHED H="1">
                                Annual rate of M/SI from 
                                <LI>vessel collision (2018 draft SARs)</LI>
                            </CHED>
                            <CHED H="1">Percent chance of ONE strike</CHED>
                            <CHED H="1">Percent chance of TWO strikes</CHED>
                            <CHED H="1">
                                Annual 
                                <LI>proposed take</LI>
                            </CHED>
                            <CHED H="1">Potential take proposed over 7 years</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Fin whale (Western North Atlantic)</ENT>
                            <ENT>1.6</ENT>
                            <ENT>1.4</ENT>
                            <ENT>19.51</ENT>
                            <ENT>3.81</ENT>
                            <ENT>0.14</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sei whale (Nova Scotia)</ENT>
                            <ENT>0.8</ENT>
                            <ENT>0.8</ENT>
                            <ENT>11.15</ENT>
                            <ENT>1.24</ENT>
                            <ENT>0.14</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Minke whale (Canadian East Coast)</ENT>
                            <ENT>1.4</ENT>
                            <ENT>1</ENT>
                            <ENT>13.94</ENT>
                            <ENT>1.94</ENT>
                            <ENT>0.14</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Humpback whale (Gulf of Maine)</ENT>
                            <ENT>1.8</ENT>
                            <ENT>2.7</ENT>
                            <ENT>37.63</ENT>
                            <ENT>14.16</ENT>
                            <ENT>0.29</ENT>
                            <ENT>2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sperm (North Atlantic)</ENT>
                            <ENT>0.2</ENT>
                            <ENT>0.2</ENT>
                            <ENT>2.79</ENT>
                            <ENT>0.08</ENT>
                            <ENT>0.14</ENT>
                            <ENT>
                                <SU>2</SU>
                                 1
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Bryde's whale (Northern Gulf of Mexico)</ENT>
                            <ENT>0.2</ENT>
                            <ENT>0.2</ENT>
                            <ENT>2.79</ENT>
                            <ENT>0.08</ENT>
                            <ENT>0</ENT>
                            <ENT>
                                <SU>3</SU>
                                 0
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sperm (Gulf of Mexico)</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0.00</ENT>
                            <ENT>0.00</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Blue whale (Western North Atlantic)</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0.00</ENT>
                            <ENT>0.00</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             North Atlantic right whales are not included in this analysis as NARWs are not anticipated to be struck due to the additional extensive mitigation the Navy implements to minimize the risk of striking this particular species. In addition, the Navy has not struck this species since prior to 2009 when the Navy's current vessel movement mitigation, reporting, and monitoring requirements have been in place.
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             The analysis indicates only a very small likelihood (less than 3 percent) that a North Atlantic sperm whale would be struck over the seven years, however, the Navy has struck a sperm whale previously in the Atlantic, which may indicate a higher possibility that it could occur and suggests that authorizing one mortality over the seven years would be appropriate.
                        </TNOTE>
                        <TNOTE>
                            <SU>3</SU>
                             Due to their low population abundance within the Study Area and lack of previous vessel strikes by the Navy, along with the Navy's enhanced mitigation measures in the Bryde's Whale Mitigation Area, Bryde's whales are not anticipated to be struck therefore and have zero mortality/serious injury takes.
                        </TNOTE>
                    </GPOTABLE>
                    <P>For the reasons discussed in detail in the 2018 AFTT final rule and discussed further below, due to enhanced mitigation measures, NARWs are not anticipated to be struck by Navy vessels and are anticipated to have zero mortality/serious injury takes over the seven years of the rule. In addition, based on the quantitative method described above, blue whales and Gulf of Mexico sperm whales have a zero percent chance of being struck. After considering this result, along with additional factors discussed below, the Navy found that any vessel strike of these two stocks is highly unlikely. After fully considering all relevant information, NMFS agreed with this conclusion. Finally, the quantitative analysis outlined above indicates only a very small likelihood the Navy would strike a Bryde's whale (3 percent). Due to their low population abundance and lack of previous vessel strikes by the Navy, Bryde's whales are also unlikely to be struck and we have proposed to authorize zero mortality/serious injury takes. Alternately, the quantitative analysis discussed above also indicates only a very small likelihood that the Navy would strike a North Atlantic sperm whale over the seven years covered by the 2019 Navy application (less than 3 percent), however, the Navy has struck a sperm whale previously in the Atlantic (2005), which points to a higher possibility that it could occur and suggests that authorizing a single mortality/serious injury would be appropriate. Additional discussion relevant to our determinations for North Atlantic blue whales, Gulf of Mexico sperm whale, NARW, and Bryde's whale is included below.</P>
                    <P>
                        In addition to the zero probability predicted by the quantitative model, there are no recent confirmed records of vessel collision to blue whales in the U.S. waters, although there is one older historical record pointing to a ship strike that likely occurred beyond the U.S. Atlantic EEZ (outside of where most Navy activities occur, so less relevant) and one 1998 record of a dead 20 m (66 ft) male blue whale brought into Rhode Island waters on the bow of a tanker. The cause of death was determined to be ship strike; however, some of the injuries were difficult to explain from the necropsy. As noted previously, the Navy has been conducting Marine Species Awareness Training and implementing additional mitigation measures to protect against vessel strikes since 2009. Therefore, given the absence of any strikes in the recent past since the Navy has implemented its current mitigation measures, the very low abundance of North Atlantic blue whales throughout the AFTT Study Area (Nmin = 440 for the Western North Atlantic stock, 
                        <PRTPAGE P="21157"/>
                        Waring 
                        <E T="03">et al.,</E>
                         2010), and the very low number of blue whales ever known to be struck in the area by any type of vessel (and none struck by Navy vessels), we believe the likelihood of the Navy hitting a blue whale is discountable.
                    </P>
                    <P>In addition to the zero probability of hitting a sperm whale in the Gulf of Mexico predicted by the quantitative model, there have been no vessel strikes of sperm whales by any entity since 2009 in the Gulf of Mexico per the SAR (2009-2013) and no Navy strikes of any large whales since 1995 (based on our records, which include Navy's records) in the Gulf of Mexico. Further, the Navy has comparatively fewer steaming days in the Gulf of Mexico and there is a fairly low abundance of sperm whales occurring there. As noted previously, the Navy has been conducting Marine Species Awareness Training and implementing additional mitigation measures to protect against vessel strikes since 2009. Therefore, NMFS believes that the likelihood of the Navy hitting a Gulf of Mexico sperm whale is discountable.</P>
                    <P>Although the quantitative analysis would indicate that NARWs do have a low probability of being struck one time within the seven-year period when vessel strikes across all activity types (including non-Navy) are considered (annual mortality and serious injury, hereafter abbreviated as M/SI) from vessel strikes is calculated as 0.41 in the 2018 SAR), when the enhanced mitigation measures (discussed below) that the Navy has been implementing and would continue to implement for NARWs are considered in combination with this low probability, a vessel strike is highly unlikely. Therefore, lethal take of NARWs was not requested by the Navy and is not proposed to be authorized by NMFS. We further note that while there have been two strikes of unidentified whales by the Navy since 2009, it is unlikely they were NARW as the strikes occurred in areas where, or times of year when, NARW are not known to be present.</P>
                    <P>
                        Regarding the Bryde's whale, due to the fact that the Navy has not struck a Bryde's whale (as no Navy strikes have occurred in the Gulf of Mexico), the very low abundance numbers (Nbest = 33 individuals, Hayes 
                        <E T="03">et al.,</E>
                         2018), and the limited Navy ship traffic that overlaps with Bryde's whale habitat, neither the Navy nor NMFS anticipate any vessel-strike takes, and none were requested or are proposed for authorization. The Navy is now also limiting activities (
                        <E T="03">i.e.,</E>
                         200 hr cap on hull-mounted MFAS) and will not use explosives (except during mine warfare activities) in the Bryde's Whale Mitigation Area. For a complete discussion and analysis of these mitigation areas, see the 
                        <E T="03">Mitigation Measures</E>
                         section in the 2018 AFTT final rule along with a summary in the 
                        <E T="03">Mitigation Measures</E>
                         section of this proposed rule; see also Chapter 5 (Mitigation) of the 2018 AFTT FEIS/OEIS.
                    </P>
                    <P>
                        In addition to procedural mitigation, the Navy would continue to implement measures in mitigation areas used by NARW for foraging, calving, and migration. For a complete discussion and analysis of these mitigation areas, see the 
                        <E T="03">Mitigation Measures</E>
                         section in the 2018 AFTT final rule along with a summary in the 
                        <E T="03">Mitigation Measures</E>
                         section of this proposed rule; see also Chapter 5 (Mitigation) of the 2018 AFTT FEIS/OEIS. These measures, which go above and beyond those focused on other species (
                        <E T="03">e.g.,</E>
                         funding of and communication with sightings systems, implementation of speed reductions during applicable circumstances in certain areas) have succeeded in the Navy avoiding strike of a NARW during training and testing activities in the past and essentially eliminate the potential for vessel strikes to occur during the seven-year period of this rule. In particular, the mitigation pertaining to vessels, including the continued participation in and sponsoring of the Early Warning System, would help Navy vessels avoid NARW during transits and training and testing activities. The Early Warning System is a comprehensive information exchange network dedicated to reducing the risk of vessel strikes to NARW off the southeast United States from all mariners (
                        <E T="03">i.e.,</E>
                         Navy and non-Navy vessels). Navy participants include the Fleet Area Control and Surveillance Facility, Jacksonville; Commander, Naval Submarine Forces, Norfolk, Virginia; and Naval Submarine Support Command. The Navy, U.S. Coast Guard, U.S. Army Corps of Engineers, and NMFS collaboratively sponsor daily aerial surveys from December 1 through March 31 (weather permitting) to observe for NARW from the shoreline out to approximately 30-35 nmi offshore. Aerial surveyors relay sightings information to all mariners transiting within the NARW calving habitat (
                        <E T="03">e.g.,</E>
                         commercial vessels, recreational boaters, and Navy ships).
                    </P>
                    <P>
                        In the Northeast NARW Mitigation Area, before all vessel transits, the Navy conducts a web query or email inquiry of NOAA's NARW Sighting Advisory System to obtain the latest NARW sightings information. Navy vessels currently use and would continue to use the obtained sightings information to reduce potential interactions with NARW during transits and prevent ship strikes. In this mitigation area, vessels would continue to implement speed reductions after they observe a NARW; if they are within 5 nmi of the location of a sighting reported to the NARW Sighting Advisory System within the past week; and when operating at night or during periods of reduced visibility. During transits and normal firing involving non-explosive torpedos activities, the Navy ships would continue to maintain a speed of no more than 10 kn. During submarine target firing, ships would maintain speeds of no more than 18 kn. During vessel target firing, vessel speeds would exceed 18 kn for only brief periods of time (
                        <E T="03">e.g.</E>
                        , 10-15 min).
                    </P>
                    <P>
                        In the Southeast NARW Mitigation Area, before transiting or conducting training or testing activities within the mitigation area, the Navy would continue to initiate communication with the Fleet Area Control and Surveillance Facility, Jacksonville to obtain Early Warning System NARW whale sightings data. The Fleet Area Control and Surveillance Facility, Jacksonville would continue to advise vessels of all reported whale sightings in the vicinity to help vessels and aircraft reduce potential interactions with NARWs and prevent ship strikes. Commander Submarine Force U.S. Atlantic Fleet would coordinate any submarine activities that may require approval from the Fleet Area Control and Surveillance Facility, Jacksonville. Vessels would continue to use the sightings information to reduce potential interactions with NARW during transits and prevent ship strikes. Vessels would also implement speed reductions after they observe a NARW, if they are within 5 nmi of a sighting reported within the past 12 hours (hrs), or when operating in the mitigation area at night or during periods of poor visibility. To the maximum extent practicable, vessels would continue to minimize north-south transits in the mitigation area. Finally, the Navy would continue to broadcast awareness notification messages with NARW Dynamic Management Area information (
                        <E T="03">e.g.,</E>
                         location and dates) to applicable Navy vessels operating in the vicinity of the Dynamic Management Area. The information would continue to alert assets to the possible presence of a NARW to maintain safety of navigation and further reduce the potential for a vessel strike. Navy platforms would use the information to assist their visual observation of applicable mitigation zones during training and testing 
                        <PRTPAGE P="21158"/>
                        activities and to aid in the implementation of procedural mitigation, including but not limited to, mitigation for vessel movement.
                    </P>
                    <P>Implementation of these measures is expected to significantly reduce the possibility of striking NARWs during the seven-year period of the rule. Ship strikes are a fluke encounter for which the probability will never be zero for any vessel. The probability for any particular ship to strike a marine mammal is primarily a product of the ability of the ship to detect a marine mammal and the ability to effectively act to avoid it. Navy combat ships are inherently among the best at both of these because compared to large commercial vessels, they have trained Lookouts which have received specialized Marine Mammal Observer (MMO) training, and they are the most maneuverable ships, which means that they are more likely to sight a marine mammal and more likely to be able to maneuver to avoid it in the available time—both of which decrease the probability of striking a marine mammal below what it would have been in the absence of those abilities. In the case of the NARW, the extensive communication/detection network described above, which is in use in the areas of highest NARW occurrence and where they may be more susceptible to strike, further increases the likelihood of detecting a NARW and thereby avoiding it, which further reduces the probability of NARW strike. Further, detection of NARW in some areas/times is associated with reduced speed requirements, which in some cases may reduce the strike probability further by slightly increasing the time within which an operator has to maneuver away from a whale. Because of these additional mitigation measures combined with the already low probability that a NARW will be struck, it is extremely unlikely the Navy would strike a NARW, and mortality/serious injury of a NARW from vessel strike is neither anticipated nor proposed to be authorized.</P>
                    <P>
                        In conclusion, although it is generally unlikely that any whales will be struck in a year, based on the information and analysis above, NMFS anticipates that no more than four whales have the potential to be taken by serious injury or mortality over the seven-year period of the rule. Of those four whales over the seven years, no more than two would be humpback whales (Gulf of Maine stock) and no more than one would come from any of the four following stocks: Fin whale (Western North Atlantic stock), minke (Canadian East Coast stock), sperm whale (North Atlantic stock), and sei whale (Nova Scotia stock). Accordingly in the 
                        <E T="03">Preliminary Analysis and Negligible Impact Determination</E>
                         section, NMFS has evaluated under the negligible impact standard the serious injury or mortality of 0.14 whales annually from each of these species or stocks (
                        <E T="03">i.e.,</E>
                         1 take over the 7 years divided by 7 to get the annual number), except for the humpback whale (North Atlantic stock) for which we used 0.29 (
                        <E T="03">i.e.,</E>
                         2 takes over the 7 years divided by 7 to get the annual number) along with other expected harassment incidental take.
                    </P>
                    <HD SOURCE="HD1">Proposed Mitigation Measures</HD>
                    <P>
                        Under section 101(a)(5)(A) of the MMPA, NMFS must set forth the permissible methods of taking pursuant to such activity, and other means of effecting the least practicable adverse impact on such species or stock and its habitat, paying particular attention to rookeries, mating grounds, and areas of similar significance, and on the availability of such species or stock for subsistence uses (“least practicable adverse impact”). NMFS does not have a regulatory definition for least practicable adverse impact. The 2004 NDAA amended the MMPA as it relates to military readiness activities and the incidental take authorization process such that a determination of “least practicable adverse impact” shall include consideration of personnel safety, practicality of implementation, and impact on the effectiveness of the “military readiness activity.” For the full discussion of how NMFS interprets least practicable adverse impact, including how it relates to the negligible-impact standard, see the 
                        <E T="03">Mitigation Measures</E>
                         section in the 2018 AFTT final rule.
                    </P>
                    <P>
                        Section 101(a)(5)(A)(i)(II) requires NMFS to issue, in conjunction with its authorization, binding—and enforceable—restrictions (in the form of regulations) setting forth how the activity must be conducted, thus ensuring the activity has the “least practicable adverse impact” on the affected species or stocks. In situations where mitigation is specifically needed to reach a negligible impact determination, section 101(a)(5)(A)(i)(II) also provides a mechanism for ensuring compliance with the “negligible impact” requirement. Finally, we reiterate that the least practicable adverse impact standard also requires consideration of measures for marine mammal habitat, with particular attention to rookeries, mating grounds, and other areas of similar significance, and for subsistence impacts, whereas the negligible impact standard is concerned solely with conclusions about the impact of an activity on annual rates of recruitment and survival.
                        <SU>1</SU>
                        <FTREF/>
                         In evaluating what mitigation measures are appropriate, NMFS considers the potential impacts of the Specified Activities, the availability of measures to minimize those potential impacts, and the practicability of implementing those measures, as we describe below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             Outside of the military readiness context, mitigation may also be appropriate to ensure compliance with the “small numbers” language in MMPA sections 101(a)(5)(A) and (D).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">Implementation of Least Practicable Adverse Impact Standard</HD>
                    <P>Our evaluation of potential mitigation measures includes consideration of two primary factors:</P>
                    <P>(1) The manner in which, and the degree to which, implementation of the potential measure(s) is expected to reduce adverse impacts to marine mammal species or stocks, their habitat, and their availability for subsistence uses (where relevant). This analysis considers such things as the nature of the potential adverse impact (such as likelihood, scope, and range), the likelihood that the measure will be effective if implemented, and the likelihood of successful implementation; and</P>
                    <P>(2) The practicability of the measures for applicant implementation. Practicability of implementation may consider such things as cost, impact on activities, and, in the case of a military readiness activity, specifically considers personnel safety, practicality of implementation, and impact on the effectiveness of the military readiness activity. 16 U.S.C. 1371(a)(5)(A)(iii).</P>
                    <P>While the language of the least practicable adverse impact standard calls for minimizing impacts to affected species or stocks, we recognize that the reduction of impacts to those species or stocks accrues through the application of mitigation measures that limit impacts to individual animals. Accordingly, NMFS' analysis focuses on measures that are designed to avoid or minimize impacts on individual marine mammals that are likely to increase the probability or severity of population-level effects.</P>
                    <P>
                        While direct evidence of impacts to species or stocks from a specified activity is rarely available, and additional study is still needed to understand how specific disturbance events affect the fitness of individuals of certain species, there have been improvements in understanding the process by which disturbance effects are translated to the population. With 
                        <PRTPAGE P="21159"/>
                        recent scientific advancements (both marine mammal energetic research and the development of energetic frameworks), the relative likelihood or degree of impacts on species or stocks may often be inferred given a detailed understanding of the activity, the environment, and the affected species or stocks—and the best available science has been used here. This same information is used in the development of mitigation measures and helps us understand how mitigation measures contribute to lessening effects (or the risk thereof) to species or stocks. We also acknowledge that there is always the potential that new information, or a new recommendation could become available in the future and necessitate reevaluation of mitigation measures (which may be addressed through adaptive management) to see if further reductions of population impacts are possible and practicable.
                    </P>
                    <P>
                        In the evaluation of specific measures, the details of the specified activity will necessarily inform each of the two primary factors discussed above (expected reduction of impacts and practicability), and are carefully considered to determine the types of mitigation that are appropriate under the least practicable adverse impact standard. Analysis of how a potential mitigation measure may reduce adverse impacts on a marine mammal stock or species, consideration of personnel safety, practicality of implementation, and consideration of the impact on effectiveness of military readiness activities are not issues that can be meaningfully evaluated through a yes/no lens. The manner in which, and the degree to which, implementation of a measure is expected to reduce impacts, as well as its practicability in terms of these considerations, can vary widely. For example, a time/area restriction could be of very high value for decreasing population-level impacts (
                        <E T="03">e.g.,</E>
                         avoiding disturbance of feeding females in an area of established biological importance) or it could be of lower value (
                        <E T="03">e.g.,</E>
                         decreased disturbance in an area of high productivity but of less firmly established biological importance). Regarding practicability, a measure might involve restrictions in an area or time that impede the Navy's ability to certify a strike group (higher impact on mission effectiveness), or it could mean delaying a small in-port training event by 30 minutes to avoid exposure of a marine mammal to injurious levels of sound (lower impact). A responsible evaluation of “least practicable adverse impact” will consider the factors along these realistic scales. Accordingly, the greater the likelihood that a measure will contribute to reducing the probability or severity of adverse impacts to the species or stock or their habitat, the greater the weight that measure is given when considered in combination with practicability to determine the appropriateness of the mitigation measure, and vice versa. In the evaluation of specific measures, the details of the specified activity will necessarily inform each of the two primary factors discussed above (expected reduction of impacts and practicability), and will be carefully considered to determine the types of mitigation that are appropriate under the least practicable adverse impact standard. For more detail on how we apply these factors, see the discussion in the 
                        <E T="03">Mitigation Measures</E>
                         section of the 2018 AFTT final rule.
                    </P>
                    <P>NMFS fully reviewed the Navy's specified activities and the mitigation measures for the 2018 AFTT rulemaking and determined that the mitigation measures would result in the least practicable adverse impact on marine mammals. There is no change in either the activities or the mitigation measures for this rule. See the 2019 Navy application and the 2018 AFTT final rule for detailed information on the Navy's mitigation measures. NMFS worked with the Navy in the development of the Navy's initially proposed measures, which were informed by years of implementation and monitoring. A complete discussion of the Navy's evaluation process used to develop, assess, and select mitigation measures, which was informed by input from NMFS, can be found in Chapter 5 (Mitigation) of the 2018 AFTT FEIS/OEIS. The process described in Chapter 5 (Mitigation) of the 2018 AFTT FEIS/OEIS robustly supported NMFS' independent evaluation of whether the mitigation measures would meet the least practicable adverse impact standard. The Navy has implemented the mitigation measures under the 2018 AFTT regulations and would be required to continue implementation of the mitigation measures identified in this rule for the full seven years it covers to avoid or reduce potential impacts from acoustic, explosive, and physical disturbance and ship strike stressors.</P>
                    <P>In its 2019 application, the Navy proposes no changes to the mitigation measures in the 2018 AFTT final rule and there is no new information that affects NMFS' assessment of the applicability or effectiveness of those measures over the new seven-year period. See the 2018 AFTT proposed rule and the 2018 AFTT final rule for our full assessment of these measures. In summary, the Navy has agreed to procedural mitigation measures that will reduce the probability and/or severity of impacts expected to result from acute exposure to acoustic sources or explosives, ship strike, and impacts to marine mammal habitat. Specifically, the Navy will use a combination of delayed starts, powerdowns, and shutdowns to minimize or avoid serious injury or mortality, minimize the likelihood or severity of PTS or other injury, and reduce instances of TTS or more severe behavioral disruption caused by acoustic sources or explosives. The Navy also will implement multiple time/area restrictions (several of which were added in the 2018 AFTT final rule since the previous AFTT MMPA incidental take rule) that would reduce take of marine mammals in areas or at times where they are known to engage in important behaviors, such as feeding or calving, where the disruption of those behaviors would have a higher probability of resulting in impacts on reproduction or survival of individuals that could lead to population-level impacts. Summaries of the Navy's procedural mitigation measures and mitigation areas for the AFTT Study Area are provided in Tables 14 and 15.</P>
                    <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s100,r200">
                        <TTITLE>Table 14—Summary of Procedural Mitigation</TTITLE>
                        <BOXHD>
                            <CHED H="1">Stressor or activity</CHED>
                            <CHED H="1">Mitigation zones sizes and other requirements</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Environmental Awareness and Education</ENT>
                            <ENT>○ Afloat Environmental Compliance Training program for applicable personnel.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Active Sonar</ENT>
                            <ENT>
                                Depending on sonar source:
                                <LI O="oi3">○ 1,000 yd. power down, 500 yd. power down, and 200 yd. shut down.</LI>
                                <LI O="oi3">○ 200 yd. shut down.</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Air Guns</ENT>
                            <ENT O="oi3">○ 150 yd.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pile Driving</ENT>
                            <ENT O="oi3">○ 100 yd.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Weapons Firing Noise</ENT>
                            <ENT O="oi3">○ 30° on either side of the firing line out to 70 yd.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="21160"/>
                            <ENT I="01">Explosive Sonobuoys</ENT>
                            <ENT O="oi3">○ 600 yd.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Explosive Torpedoes</ENT>
                            <ENT O="oi3">○ 2,100 yd.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Explosive Medium-Caliber and Large-Caliber Projectiles.</ENT>
                            <ENT O="oi3">
                                ○ 1,000 yd. (large-caliber projectiles).
                                <LI O="oi3">○ 600 yd. (medium-caliber projectiles during surface-to-surface activities).</LI>
                                <LI O="oi3">○ 200 yd. (medium-caliber projectiles during air-to-surface activities).</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Explosive Missiles and Rockets</ENT>
                            <ENT O="oi3">
                                ○ 2,000 yd. (21-500 lb. net explosive weight).
                                <LI O="oi3">○ 900 yd. (0.6-20 lb. net explosive weight).</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Explosive Bombs</ENT>
                            <ENT O="oi3">○ 2,500 yd.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sinking Exercises</ENT>
                            <ENT O="oi3">○ 2.5 NM.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Explosive Mine Countermeasure and Neutralization Activities</ENT>
                            <ENT O="oi3">
                                ○ 2,100 yd. (6-650 lb. net explosive weight).
                                <LI O="oi3">○ 600 yd. (0.1-5 lb. net explosive weight).</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Explosive Mine Neutralization Activities Involving Navy Divers</ENT>
                            <ENT O="oi3">
                                ○ 1,000 yd. (21-60 lb. net explosive weight for positive control charges and charges using time-delay fuses).
                                <LI O="oi3">○ 500 yd. (0.1-20 lb. net explosive weight for positive control charges).</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Maritime Security Operations—Anti-Swimmer Grenades</ENT>
                            <ENT O="oi3">○ 200 yd.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Line Charge Testing</ENT>
                            <ENT O="oi3">○ 900 yd.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Ship Shock Trials</ENT>
                            <ENT O="oi3">○ 3.5 NM.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Vessel Movement</ENT>
                            <ENT O="oi3">
                                ○ 500 yd. (whales).
                                <LI O="oi3">○ 200 yd. (other marine mammals).</LI>
                                <LI O="oi3">○ North Atlantic right whale Dynamic Management Area notification messages.</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Towed In-Water Devices</ENT>
                            <ENT O="oi3">○ 250 yd.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Small-, Medium-, and Large-Caliber Non-Explosive Practice Munitions</ENT>
                            <ENT O="oi3">○ 200 yd.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Non-Explosive Missiles and Rockets</ENT>
                            <ENT O="oi3">○ 900 yd.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Non-Explosive Bombs and Mine Shapes</ENT>
                            <ENT O="oi3">○ 1,000 yd.</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Notes:</E>
                             lb: pounds; nmi: nautical miles; yd: yards.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="1" OPTS="L2,i1" CDEF="s200">
                        <TTITLE>Table 15—Summary of Mitigation Areas for Marine Mammals</TTITLE>
                        <BOXHD>
                            <CHED H="1">Summary of mitigation area requirements</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Northeast North Atlantic Right Whale Mitigation Area:</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ The Navy will report the total hours and counts of active sonar and in-water explosives used in the mitigation area in its annual training and testing activity reports.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ The Navy will minimize use of active sonar to the maximum extent practicable and will not use explosives that detonate in the water.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ The Navy will conduct non-explosive torpedo testing during daylight hours in Beaufort sea state 3 or less using three Lookouts (one on a vessel, two in an aircraft during aerial surveys) and an additional Lookout on the submarine when surfaced; during transits, ships will maintain a speed of no more than 10 knots; during firing, ships will maintain a speed of no more than 18 knots except brief periods of time during vessel target firing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ Vessels will obtain the latest North Atlantic right whale sightings data and implement speed reductions after they observe a North Atlantic right whale, if within 5 NM of a sighting reported within the past week, and when operating at night or during periods of reduced visibility.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Gulf of Maine Planning Awareness Mitigation Area:</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ The Navy will report the total hours and counts of active sonar and in-water explosives used in the mitigation area in its annual training and testing activity reports.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ The Navy will not conduct major training exercises and will not conduct &gt;200 hours of hull-mounted mid-frequency active sonar per year.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Northeast Planning Awareness Mitigation Areas and Mid-Atlantic Planning Awareness Mitigation Areas:</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ Navy will avoid conducting major training exercises to the maximum extent practicable.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ The Navy will not conduct more than four major training exercises per year.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Southeast North Atlantic Right Whale Mitigation Area (November 15-April 15):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ The Navy will report the total hours and counts of active sonar and in-water explosives used in the mitigation area in its annual training and testing activity reports.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ The Navy will not use active sonar except as necessary for navigation training, object detection training, and dipping sonar.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ The Navy will not expend explosive or non-explosive ordnance.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ Vessels will obtain the latest North Atlantic right whale sightings data; will implement speed reductions after they observe a North Atlantic right whale, if within 5 NM of a sighting reported within the past 12 hours, and when operating at night or during periods of reduced visibility; and will minimize north-south transits to the maximum extent practicable.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Jacksonville Operating Area (November 15-April 15):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ Navy units conducting training or testing activities in the Jacksonville Operating Area will obtain and use Early Warning System North Atlantic right whale sightings data as they plan specific details of events to minimize potential interactions with North Atlantic right whales to the maximum extent practicable. The Navy will use the reported sightings information to assist visual observations of applicable mitigation zones and to aid in the implementation of procedural mitigation.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Southeast North Atlantic Right Whale Critical Habitat Special Reporting Area (November 15-April 15):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ The Navy will report the total hours and counts of active sonar and in-water explosives used in the mitigation area in its annual training and testing activity reports.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Navy Cherry Point Range Complex Nearshore Mitigation Area (March-September):</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ The Navy will not conduct explosive mine neutralization activities involving Navy divers in the mitigation area.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ To the maximum extent practicable, the Navy will not use explosive sonobuoys, explosive torpedoes, explosive medium-caliber and large-caliber projectiles, explosive missiles and rockets, explosive bombs, explosive mines during mine countermeasure and neutralization activities, and anti-swimmer grenades in the mitigation area.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Bryde's Whale Mitigation Area:</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="21161"/>
                            <ENT I="03">○ The Navy will report the total hours and counts of active sonar and in-water explosives used in the mitigation area in its annual training and testing activity reports.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">○ The Navy will not conduct &gt;200 hours of hull-mounted mid-frequency active sonar per year and will not use explosives (except during explosive mine warfare activities).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="03">Gulf of Mexico Planning Awareness Mitigation Areas</E>
                            </ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Notes:</E>
                             min.: minutes; nmi: nautical miles.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD2">Mitigation Conclusions</HD>
                    <P>
                        NMFS has carefully evaluated the Navy's proposed mitigation measures—many of which were developed with NMFS' input during the previous phases of Navy training and testing authorizations and none of which have changed since our evaluation during the 2018 AFTT rulemaking—and considered a broad range of other measures (
                        <E T="03">i.e.,</E>
                         the measures considered but eliminated in the Navy's 2018 FEIS/OEIS, which reflect many of the comments that have arisen via NMFS or public input in past years) in the context of ensuring that NMFS prescribes the means of effecting the least practicable adverse impact on the affected marine mammal species and stocks and their habitat. Our evaluation of potential measures included consideration of the following factors in relation to one another: The manner in which, and the degree to which, the successful implementation of the mitigation measures is expected to reduce the likelihood and/or magnitude of adverse impacts to marine mammal species and stocks and their habitat; the proven or likely efficacy of the measures; and the practicability of the measures for applicant implementation, including consideration of personnel safety, practicality of implementation, and impact on the effectiveness of the military readiness activity. There is no new information that affects our analysis from the 2018 AFTT rulemaking, all of which remains applicable and valid for our assessment of the appropriateness of the mitigation measures during the seven-year period of this rule.
                    </P>
                    <P>Based on our evaluation of the Navy's proposed measures (which are being implemented under the 2018 AFTT regulations), as well as other measures considered by the Navy and NMFS, NMFS has preliminarily determined that the Navy's proposed mitigation measures (which are identical to those in the 2018 AFTT final rule) are appropriate means of effecting the least practicable adverse impacts on marine mammal species or stocks and their habitat, paying particular attention to rookeries, mating grounds, and areas of similar significance, and considering specifically personnel safety, practicality of implementation, and impact on the effectiveness of the military readiness activity. Additionally, as described in more detail below, the 2018 AFTT final rule includes an adaptive management provision, which the Navy proposes to extend, which ensures that mitigation is regularly assessed and provides a mechanism to improve the mitigation, based on the factors above, through modification as appropriate.</P>
                    <P>The proposed rule comment period provides the public an opportunity to submit recommendations, views, and/or concerns regarding the Navy's activities and the proposed mitigation measures. While NMFS has preliminarily determined that the Navy's proposed mitigation measures would effect the least practicable adverse impact on the affected species or stocks and their habitat, NMFS will consider all public comments to help inform our final decision. Consequently, the proposed mitigation measures may be refined, modified, removed, or added to prior to the issuance of the final rule based on public comments received, and where appropriate, further analysis of any additional mitigation measures.</P>
                    <HD SOURCE="HD1">Proposed Monitoring</HD>
                    <P>Section 101(a)(5)(A) of the MMPA states that in order to authorize incidental take for an activity, 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 incidental take 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.</P>
                    <P>
                        In its 2019 application, the Navy proposes no changes to the monitoring described in the 2018 AFTT final rule. They would continue implementation of the robust Integrated Comprehensive Monitoring Program and Strategic Planning Process described in the 2018 AFTT final rule. The Navy's monitoring strategy, currently required by the 2018 AFTT regulations, is well-designed to work across Navy ranges to help better understand the impacts of the Navy's activities on marine mammals and their habitat by focusing on learning more about marine mammal occurrence in different areas and exposure to Navy stressors, marine mammal responses to different sound sources, and the consequences of those exposures and responses on marine mammal populations. Similarly, the proposed seven-year regulations would include identical adaptive management provisions and reporting requirements as the 2018 AFTT regulations. There is no new information that would indicate that the monitoring measures put in place under the 2018 AFTT final rule would not remain applicable and appropriate for the seven-year period of this proposed rule. See the 
                        <E T="03">Monitoring</E>
                         section of the 2018 AFTT final rule for more details on the monitoring that would be required under this rule. In addition, please see the 2019 Navy application, which references Chapter 13 of the 2017 Navy application for full details on the monitoring and reporting proposed by the Navy.
                    </P>
                    <HD SOURCE="HD1">Adaptive Management</HD>
                    <P>
                        The 2018 AFTT regulations governing the take of marine mammals incidental to Navy training and testing activities in the AFTT Study Area contain an adaptive management component. Our understanding of the effects of Navy training and testing activities (
                        <E T="03">e.g.,</E>
                         acoustic and explosive stressors) on marine mammals continues to evolve, which makes the inclusion of an adaptive management component both valuable and necessary within the context of seven-year regulations. The 2019 Navy application proposes no changes to the adaptive management component included in the 2018 AFTT final rule.
                    </P>
                    <P>
                        The reporting requirements associated with this rule are designed to provide NMFS with monitoring data from the previous year to allow NMFS to 
                        <PRTPAGE P="21162"/>
                        consider whether any changes to existing mitigation and monitoring requirements are appropriate. The use of adaptive management allows NMFS to consider new information from different sources to determine (with input from the Navy regarding practicability) on an annual or biennial basis if mitigation or monitoring measures should be modified (including additions or deletions). Mitigation measures could be modified if new data suggests that such modifications would have a reasonable likelihood of more effectively accomplishing the goals of the mitigation and monitoring and if the measures are practicable. If the modifications to the mitigation, monitoring, or reporting measures are substantial, NMFS will publish a notice of the planned LOA in the 
                        <E T="04">Federal Register</E>
                         and solicit public comment.
                    </P>
                    <P>
                        The following are some of the possible sources of applicable data to be considered through the adaptive management process: (1) Results from monitoring and exercises reports, as required by MMPA authorizations; (2) compiled results of Navy funded research and development studies; (3) results from specific stranding investigations; (4) results from general marine mammal and sound research; and (5) any information which reveals that marine mammals may have been taken in a manner, extent, or number not authorized by these regulations or subsequent LOAs. The results from monitoring reports and other studies may be viewed at 
                        <E T="03">https://www.navymarinespeciesmonitoring.us/.</E>
                    </P>
                    <HD SOURCE="HD1">Reporting</HD>
                    <P>
                        In order to issue incidental take authorization for an activity, section 101(a)(5)(A) of the MMPA states that NMFS must set forth requirements pertaining to the monitoring and reporting of such taking. Effective reporting is critical both to compliance as well as ensuring that the most value is obtained from the required monitoring. Reports from individual monitoring events, results of analyses, publications, and periodic progress reports for specific monitoring projects will be posted to the Navy's Marine Species Monitoring web portal: 
                        <E T="03">http://www.navymarinespeciesmonitoring.us.</E>
                         The 2019 Navy application proposes no changes to the reporting requirements identified in the 2018 AFTT final rule. Reporting requirements would remain identical to those described in the 2018 AFTT final rule, and there is no new information that would indicate that the reporting requirements put in place under the 2018 AFTT final rule would not remain applicable and appropriate for the seven-year period of this proposed rule. See the 
                        <E T="03">Reporting</E>
                         section of the 2018 AFTT final rule for more details on the reporting that would be required under this rule.
                    </P>
                    <HD SOURCE="HD1">Preliminary Analysis and Negligible Impact 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 mortality, serious injury, and Level A or Level B harassment (as presented in Tables 10-13), NMFS considers other factors, such as the likely nature of any responses (
                        <E T="03">e.g.,</E>
                         intensity, duration), the context of any responses (
                        <E T="03">e.g.,</E>
                         critical reproductive time or location, migration), 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 environmental baseline (
                        <E T="03">e.g.,</E>
                         as reflected in the regulatory status of the species, population size and growth rate where known, other ongoing sources of human-caused mortality, ambient noise levels, and specific consideration of take by Level A harassment or M/SI previously authorized for other NMFS activities).
                    </P>
                    <P>
                        In the 
                        <E T="03">Estimated Take of Marine Mammals</E>
                         sections of this proposed rule and the 2018 AFTT final rule (where the activities, species and stocks, potential effects, and mitigation measures are the same as for this rule), we identified the subset of potential effects that would be expected to rise to the level of takes both annually and over the seven-year period covered by this rule, and then identified the number of each of those mortality takes that we believe could occur or the maximum number of harassment takes that are reasonably expected to occur based on the methods described. The impact that any given take will have is dependent on many case-specific factors that need to be considered in the negligible impact analysis (
                        <E T="03">e.g.,</E>
                         the context of behavioral exposures such as duration or intensity of a disturbance, the health of impacted animals, the status of a species that incurs fitness-level impacts to individuals, etc.). For this proposed rule we evaluated the likely impacts of the enumerated maximum number of harassment takes that are proposed for authorization and reasonably expected to occur, in the context of the specific circumstances surrounding these predicted takes. We also assessed M/SI takes that have the potential to occur, as well as considering the traits and statuses of the affected species and stocks. Last, we collectively evaluated this information, as well as other more taxa-specific information and mitigation measure effectiveness, in group-specific assessments that support our negligible impact conclusions for each stock.
                    </P>
                    <P>
                        The Navy proposes no changes to the nature or level of the specified activities or the boundaries of the AFTT Study Area, and therefore the training and testing activities (
                        <E T="03">e.g.,</E>
                         equipment and sources used, exercises conducted) are the same as those analyzed in the 2018 AFTT final rule. In addition, the mitigation, monitoring, and reporting measures are identical to those described and analyzed in the 2018 AFTT final rule. As described above, there is no new information available since the publication of the 2018 AFTT final rule regarding the impacts of the specified activities on marine mammals, the status and distribution of any of the affected marine mammal species or stocks, or the effectiveness of the mitigation and monitoring measures that would change our analyses.
                    </P>
                    <HD SOURCE="HD2">Harassment</HD>
                    <P>
                        As described in the 
                        <E T="03">Estimated Takes of Marine Mammals</E>
                         section, the annual number of takes proposed for authorization and reasonably expected to occur by Level A harassment and Level B harassment (based on the maximum number of activities per 12-month period) are identical to those presented in Tables 39 through 41 in the 
                        <E T="03">Take Requests</E>
                         section of the 2018 AFTT final rule. As such the negligible impact analyses and determinations of the effects of the estimated Level A harassment and Level B harassment takes on annual rates of recruitment or survival for each species and stock are identical to that presented in the 2018 AFTT final rule. The only difference is that the annual levels of take and the associated effects on reproduction or survival would occur for the seven-year 
                        <PRTPAGE P="21163"/>
                        period of the proposed rule instead of the five-year period of the 2018 AFTT final rule, which would make no difference in effects on annual rates of recruitment or survival. For detailed discussion of the impacts that affected individuals may experience given the specific characteristics of the specified activities and required mitigation (
                        <E T="03">e.g.,</E>
                         from behavioral harassment, masking, and temporary or permanent threshold shift), along with the effects of the expected Level A harassment and Level B harassment take on reproduction and survival, see the applicable subsections in the 
                        <E T="03">Analysis and Negligible Impact Determination</E>
                         section of the 2018 AFTT final rule (83 FR 57211-57217).
                    </P>
                    <HD SOURCE="HD2">Serious Injury or Mortality</HD>
                    <P>
                        In its 2019 application, the Navy proposes no additional ship shock trials during the seven-year period of the proposed rule to those covered by the existing 2018 AFTT regulations, so the expected and requested total takes by M/SI due to explosives over seven years are the same as those authorized in the existing 2018 AFTT regulations. There is no new information that affects the methodology or results of the ship-shock analysis presented in the 2018 AFTT final rule. But as these same activities would occur over seven years rather than five years, the estimated annual take is calculated as the number of total takes divided by seven. For each of the dolphin species or stocks listed in Table 16 there would be an annual take of 0.14 dolphins (
                        <E T="03">i.e.,</E>
                         for those species or stocks where one take could occur divided by seven years to get the annual number of M/SIs) or 0.86 dolphins in the case of short-beaked common dolphin (
                        <E T="03">i.e.,</E>
                         where six takes could occur divided by seven years to get the annual number of M/SIs). This is a decrease from the annual take of 0.2 dolphins (for the three species where one lethal take could occur) and annual take of 1.2 short-beaked dolphins (where six lethal takes could occur) over the five-year period of the 2018 AFTT regulations, as shown in Table 70 in the 2018 AFTT final rule. As the proposed annual number is less than that analyzed and authorized in the 2018 AFTT final rule and no other relevant information about the status, abundance, or effects of mortality on each species or stock has changed, the analysis of the effects of take from ship shock trials mirrors that presented in the 2018 AFTT final rule.
                    </P>
                    <GPOTABLE COLS="10" OPTS="L2,p6,6/7,i1" CDEF="s25,9,9,9,12,9,10,9,9C,r25">
                        <TTITLE>Table 16—Summary Information Related to AFTT Serious Injury or Mortality From Explosive</TTITLE>
                        <TDESC>[(Ship Shock Trials), 2018-2025]</TDESC>
                        <BOXHD>
                            <CHED H="1">
                                Species
                                <LI>(stock)</LI>
                            </CHED>
                            <CHED H="1">
                                Stock
                                <LI>abundance</LI>
                                <LI>(Nbest) *</LI>
                            </CHED>
                            <CHED H="1">
                                Annual
                                <LI>estimated</LI>
                                <LI>take by</LI>
                                <LI>serious</LI>
                                <LI>injury or</LI>
                                <LI>mortality</LI>
                                <LI>
                                    (M/SI) 
                                    <SU>1</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                Total
                                <LI>annual</LI>
                                <LI>
                                    M/SI * 
                                    <SU>2</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                Fisheries
                                <LI>interactions</LI>
                                <LI>(Y/N);</LI>
                                <LI>annual rate</LI>
                                <LI>of M/SI from</LI>
                                <LI>fisheries</LI>
                                <LI>interactions *</LI>
                            </CHED>
                            <CHED H="1">PBR *</CHED>
                            <CHED H="1">
                                NEFSC
                                <LI>authorized</LI>
                                <LI>take</LI>
                                <LI>(annual)</LI>
                            </CHED>
                            <CHED H="1">
                                Residual
                                <LI>PBR—</LI>
                                <LI>PBR minus</LI>
                                <LI>annual</LI>
                                <LI>M/SI and</LI>
                                <LI>NEFSC</LI>
                                <LI>authorized</LI>
                                <LI>
                                    take 
                                    <SU>3</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                Stock
                                <LI>
                                    trend * 
                                    <SU>4</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                UME
                                <LI>(Y/N);</LI>
                                <LI>number</LI>
                                <LI>and year</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Atlantic white-sided dolphin (Western N. Atlantic)</ENT>
                            <ENT>48,819</ENT>
                            <ENT>0.14</ENT>
                            <ENT>30</ENT>
                            <ENT>30</ENT>
                            <ENT>304</ENT>
                            <ENT>0.6</ENT>
                            <ENT>273.4</ENT>
                            <ENT>?</ENT>
                            <ENT>N.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pantropical spotted dolphin (Northern GOMEX)</ENT>
                            <ENT>50,880</ENT>
                            <ENT>0.14</ENT>
                            <ENT>4.4</ENT>
                            <ENT>4.4</ENT>
                            <ENT>407</ENT>
                            <ENT>0</ENT>
                            <ENT>402.6</ENT>
                            <ENT>?</ENT>
                            <ENT>Y; 3 in 2010-2014.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Short-beaked common dolphin (Western N. Atlantic)</ENT>
                            <ENT>70,184</ENT>
                            <ENT>0.86</ENT>
                            <ENT>406</ENT>
                            <ENT>406</ENT>
                            <ENT>557</ENT>
                            <ENT>2</ENT>
                            <ENT>149</ENT>
                            <ENT>?</ENT>
                            <ENT>N.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Spinner dolphin (Northern GOMEX)</ENT>
                            <ENT>11,441</ENT>
                            <ENT>0.14</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>62</ENT>
                            <ENT>0</ENT>
                            <ENT>62</ENT>
                            <ENT>?</ENT>
                            <ENT>Y; 7 in 2010-2014.</ENT>
                        </ROW>
                        <TNOTE>* Presented in the draft 2018 SARS.</TNOTE>
                        <TNOTE>
                            <SU>1</SU>
                             This column represents the annual take by M/SI during ship shock trials and was calculated by the number of mortalities planned for authorization divided by seven years (the length of the rule and LOAs).
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             This column represents the total number of incidents of M/SI that could potentially accrue to the specified species or stock. This number comes from the SAR, but deducts the takes accrued from either Navy or NEFSC takes as noted in the SARs to ensure they are not double-counted against PBR. However, for these species, there were no were no takes from either Navy or NEFSC as noted in the SARs to deduct that would be considered double-counting.
                        </TNOTE>
                        <TNOTE>
                            <SU>3</SU>
                             This value represents the calculated PBR less the average annual estimate of ongoing anthropogenic mortalities (
                            <E T="03">i.e.,</E>
                             total annual human-caused M/SI, which is presented in the draft 2018 SARs) and authorized take for NEFSC.
                        </TNOTE>
                        <TNOTE>
                            <SU>4</SU>
                             See relevant SARs for more information regarding stock status and trends.
                        </TNOTE>
                    </GPOTABLE>
                    <P>
                        The other facet of the analysis for which there is a quantitative change from the 2018 AFTT final rule is the number of potential mortalities due to ship strike proposed to be authorized over the seven-year period. First, based on the information and methods discussed in the 
                        <E T="03">Estimated Take of Marine Mammals</E>
                         section (which are identical to those used in the 2018 AFTT final rule), NMFS has predicted that mortal takes of four large whales over the course of the seven-year rule could occur (as compared to three large whales over five years in the 2018 AFTT final rule). Second, while no more than one whale over the seven years of any species of fin whale, sei whale, minke whale, or sperm whale (North Atlantic stock) would occur (which is the same as in the five-year 2018 AFTT final rule), as described above in the 
                        <E T="03">Estimated Take of Marine Mammals</E>
                         section, the number of potential mortality takes of humpback whales has increased from one to two. This means an annual average of 0.29 humpback whales and an annual average of 0.14 whales from each of the other four species or stocks as described in Table 17 (
                        <E T="03">i.e.,</E>
                         one, or two, take(s) over seven years divided by seven to get the annual number) are expected to potentially occur and are proposed for authorization. As this annual number is less than that analyzed and authorized in the 2018 AFTT final rule for fin whale, sei whale, minke whale, and sperm whale (North Atlantic stock), which was an annual average of 0.2 whales for the same four species and stocks, and no other relevant information about the status, abundance, or effects of mortality on each species or stock has changed, the analysis of the effects of vessel strike mirrors that presented in the 2018 AFTT final rule. For humpback whales, the annual number for potential mortality takes is slightly higher than in the 2018 AFTT final rule, but the number still falls below the insignificance threshold of 10 percent of residual Potential Biological Removal (PBR), which indicates an insignificant incremental increase in ongoing anthropogenic mortality that alone will not adversely affect annual rates of recruitment or survival. The analysis of the effects of this potential mortality on humpback whales, considered in combination with other estimated harassment takes, on annual rates of recruitment and survival appears in the 
                        <E T="03">Group and Species-Specific Analyses</E>
                         section for Mysticetes below.
                    </P>
                    <P>
                        See the 
                        <E T="03">Serious Injury and Mortality</E>
                         subsection in the 
                        <E T="03">Analysis and Negligible Impact Determination</E>
                         section of the 2018 AFTT final rule (83 FR 57217-57223) for detailed discussions of the impacts of M/SI, including a description of how the agency uses the PBR metric and other factors to inform our analysis, and an analysis of the 
                        <PRTPAGE P="21164"/>
                        impacts on each species and stock for which mortality is proposed for authorization including the relationship of potential mortality for each species to the insignificance threshold and residual PBR. Because the annual number of potential mortality takes for humpback whales remains below the insignificance threshold, the discussion for humpback whales (83 FR 57221-57222) remains fully applicable. For discussion specifically on the role of the calculated PBR in evaluating the effects of M/SI, see both the 2018 AFTT final rule and the 2018 HSTT final rule.
                    </P>
                    <GPOTABLE COLS="11" OPTS="L2,p6,6/7,i1" CDEF="s25,9,9,9,xs54,xs54,9,10,9,9C,r25">
                        <TTITLE>Table 17—Summary Information Related to AFTT Ship Strike, 2018-2025</TTITLE>
                        <BOXHD>
                            <CHED H="1">
                                Species
                                <LI>(stock)</LI>
                            </CHED>
                            <CHED H="1">
                                Stock
                                <LI>abundance</LI>
                                <LI>(Nbest) *</LI>
                            </CHED>
                            <CHED H="1">
                                Annual
                                <LI>estimated</LI>
                                <LI>take by</LI>
                                <LI>serious</LI>
                                <LI>injury or</LI>
                                <LI>mortality</LI>
                                <LI>
                                    (M/SI) 
                                    <SU>1</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                Total
                                <LI>annual</LI>
                                <LI>
                                    M/SI * 
                                    <SU>2</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                Fisheries
                                <LI>interactions</LI>
                                <LI>(Y/N);</LI>
                                <LI>annual rate</LI>
                                <LI>of M/SI from</LI>
                                <LI>fisheries</LI>
                                <LI>interactions *</LI>
                            </CHED>
                            <CHED H="1">
                                Vessel
                                <LI>collisions</LI>
                                <LI>(Y/N);</LI>
                                <LI>annual rate of M/SI from</LI>
                                <LI>vessel</LI>
                                <LI>collision *</LI>
                            </CHED>
                            <CHED H="1">PBR *</CHED>
                            <CHED H="1">
                                NEFSC
                                <LI>authorized</LI>
                                <LI>take</LI>
                                <LI>(annual)</LI>
                            </CHED>
                            <CHED H="1">
                                Residual
                                <LI>PBR—PBR minus</LI>
                                <LI>annual</LI>
                                <LI>M/SI and</LI>
                                <LI>NEFSC</LI>
                                <LI>authorized</LI>
                                <LI>
                                    take 
                                    <SU>3</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                Stock
                                <LI>
                                    trend * 
                                    <SU>4</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                UME
                                <LI>(Y/N);</LI>
                                <LI>number</LI>
                                <LI>
                                    and year 
                                    <SU>5</SU>
                                </LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Fin whale (Western North Atlantic)</ENT>
                            <ENT>1,618</ENT>
                            <ENT>0.14</ENT>
                            <ENT>2.5</ENT>
                            <ENT>Y; 1.1</ENT>
                            <ENT>Y; 1.4</ENT>
                            <ENT>2.5</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>?</ENT>
                            <ENT>N.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sei whale (Nova Scotia)</ENT>
                            <ENT>357</ENT>
                            <ENT>0.14</ENT>
                            <ENT>0.8</ENT>
                            <ENT>N; 0</ENT>
                            <ENT>
                                <E T="0731">†</E>
                                 Y; 0.8
                            </ENT>
                            <ENT>0.5</ENT>
                            <ENT>0</ENT>
                            <ENT>−0.3</ENT>
                            <ENT>?</ENT>
                            <ENT>N.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Minke Whale (Canadian East Coast)</ENT>
                            <ENT>2,591</ENT>
                            <ENT>0.14</ENT>
                            <ENT>7.5</ENT>
                            <ENT>Y; 6.5</ENT>
                            <ENT>
                                <E T="0731">†</E>
                                 Y; 1
                            </ENT>
                            <ENT>14</ENT>
                            <ENT>1</ENT>
                            <ENT>5.5</ENT>
                            <ENT>?</ENT>
                            <ENT>Y; 2 in 2019 as of 4/1/2019 (27 in 2017 and 20 in 2018).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Humpback whale (Gulf of Maine)</ENT>
                            <ENT>896</ENT>
                            <ENT>0.29</ENT>
                            <ENT>9.8</ENT>
                            <ENT>Y; 7.1</ENT>
                            <ENT>Y; 2.7</ENT>
                            <ENT>14.6</ENT>
                            <ENT>0</ENT>
                            <ENT>4.8</ENT>
                            <ENT>
                                <E T="73">&amp;uarr;</E>
                            </ENT>
                            <ENT>Y; 9 in 2019 as of 4/1/2019 (26 in 2016, 34 in 2017 and 25 in 2018).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sperm whale (North Atlantic)</ENT>
                            <ENT>2,288</ENT>
                            <ENT>0.14</ENT>
                            <ENT>0.8</ENT>
                            <ENT>Y; 0.6</ENT>
                            <ENT>Y; 0.2</ENT>
                            <ENT>3.6</ENT>
                            <ENT>0</ENT>
                            <ENT>2.8</ENT>
                            <ENT>?</ENT>
                            <ENT>?.</ENT>
                        </ROW>
                        <TNOTE>* Presented in the draft 2018 SARS.</TNOTE>
                        <TNOTE>
                            <E T="0731">†</E>
                             Value presented incorrectly in the 2018 AFTT final rule and corrected here.
                        </TNOTE>
                        <TNOTE>
                            <SU>1</SU>
                             This column represents the annual take by M/SI by vessel collision and was calculated by the number of mortalities planned for authorization divided by seven years (the length of the rule and LOAs).
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             This column represents the total number of incidents of M/SI that could potentially accrue to the specified species or stock. This number comes from the SAR, but deducts the takes accrued from either Navy strikes or NEFSC takes as noted in the SARs to ensure they are not double-counted against PBR. However, for these species, there were no takes from either Navy or NEFSC as noted in the SARs to deduct that would be considered double-counting.
                        </TNOTE>
                        <TNOTE>
                            <SU>3</SU>
                             This value represents the calculated PBR less the average annual estimate of ongoing anthropogenic mortalities (
                            <E T="03">i.e.,</E>
                             total annual human-caused M/SI, which is presented in the draft 2018 SARs) and authorized take for NEFSC.
                        </TNOTE>
                        <TNOTE>
                            <SU>4</SU>
                             See relevant SARs for more information regarding stock status and trends.
                        </TNOTE>
                        <TNOTE>
                            <SU>5</SU>
                             This column presents UME information updated since the 2018 AFTT final rule, as discussed in the earlier section 
                            <E T="03">Potential Effects of Specified Activities on Marine Mammals and their Habitat.</E>
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD2">Group and Species-Specific Analyses</HD>
                    <P>
                        In addition to broader analyses of the impacts of the Navy's activities on mysticetes, odontocetes, and pinnipeds, the 2018 AFTT final rule contained detailed analyses of the effects of the Navy's activities in the AFTT Study Area on each affected species and stock. All of that information and analyses remain applicable and valid for our analyses of the effects of the same Navy activities on the same species and stocks for the seven-year period of this proposed rule. See the 
                        <E T="03">Group and Species-Specific Analyses</E>
                         subsection in the 
                        <E T="03">Analysis and Negligible Impact Determination</E>
                         section of the 2018 AFTT final rule (83 FR 57223-57247). In addition, no new information has been received since the publication of the 2018 AFTT final rule that significantly changes the analyses on the effects of the Navy's activities on each species and stock presented in the 2018 AFTT final rule.
                    </P>
                    <P>
                        In the discussions below, the estimated Level B harassment takes represent instances of take, not the number of individuals taken (the much lower and less frequent Level A harassment takes are far more likely to be associated with separate individuals), and in many cases some individuals are expected to be taken more than one time, while in other cases a portion of individuals will not be taken at all. Below, we compare the total take numbers (including PTS, TTS, and behavioral disruption for stocks to their associated abundance estimates to evaluate the magnitude of impacts across the stock and to individuals. Specifically, when an abundance percentage comparison is below 100, it means that that percentage or less of the individuals in the stock will be affected (
                        <E T="03">i.e.,</E>
                         some individuals will not be taken at all), that the average for those taken is one day per year, and that we would not expect any individuals to be taken more than a few times in a year. When it is more than 100 percent, it means there will definitely be some number of repeated takes of individuals. For example, if the percentage is 300, the average would be each individual is taken on three days in a year if all were taken, but it is more likely that some number of individuals will be taken more than three times and some number of individuals fewer or not at all. While it is not possible to know the maximum number of days across which individuals of a stock might be taken, in acknowledgement of the fact that it is more than the average, for the purposes of this analysis, we assume a number approaching twice the average. For example, if the percentage of take compared to the abundance is 800, we estimate that some individuals might be taken as many as 16 times. Those comparisons are included in the sections below. For some stocks these numbers have been adjusted slightly (with these adjustments being in the single digits) so as to more consistently apply this approach, but these minor changes did not change the analysis or findings.
                    </P>
                    <P>
                        To assist in understanding what this analysis means, we clarify a few issues related to estimated takes and the analysis here. An individual that incurs a PTS or TTS take may sometimes, for example, also be behaviorally disturbed at the same time. As described in the 
                        <E T="03">Harassment</E>
                         subsection of the 
                        <E T="03">Negligible Impact Analysis</E>
                         section of the 2018 AFTT final rule, the degree of PTS, and the degree and duration of TTS, expected to be incurred from the Navy's activities are not expected to impact marine mammals such that their reproduction or survival could be affected. Similarly, data do not suggest that a single instance in which an animal accrues PTS or TTS and is also behaviorally harassed would result in impacts to reproduction or survival. Alternately, we recognize that if an individual is behaviorally harassed repeatedly for a longer duration and on consecutive days, effects could accrue to the point that reproductive success is jeopardized (as discussed below in the stock-specific summaries). Accordingly, in analyzing the number of takes and the likelihood of repeated and sequential takes (which could result in reproductive impacts), we consider the 
                        <PRTPAGE P="21165"/>
                        total takes, not just the behavioral Level B harassment takes, so that individuals potentially exposed to both threshold shift and behavioral disruption are appropriately considered. We note that the same reasoning applies with the potential addition of behavioral disruption (harassment) to tissue damage from explosives, the difference being that we do already consider the likelihood of reproductive impacts whenever tissue damage occurs. Further, the number of Level A harassment takes by either PTS or tissue damage are so low compared to abundance numbers that it is considered highly unlikely that any individual would be taken at those levels more than once.
                    </P>
                    <P>
                        Having considered all of the information and analyses previously presented in the 2018 AFTT final rule, including the information presented in the 
                        <E T="03">Overview,</E>
                         the 
                        <E T="03">Deepwater Horizon (DWH) Oil Spill</E>
                         discussion, and the 
                        <E T="03">Group and Species-Specific Analyses</E>
                         discussions organized by the different groups and species, below we present tables showing instances of total take as a percentage of stock abundance for each group, updated with the new vessel strike and ship shock calculations for some species. We then summarize the information for each species or stock, considering the analysis from the 2018 AFTT final rule and any new analysis. The analyses below in some cases address species collectively if they occupy the same functional hearing group (
                        <E T="03">i.e.,</E>
                         low, mid, and high-frequency cetaceans and pinnipeds in water), share similar life history strategies, and/or are known to behaviorally respond similarly to acoustic stressors. Because some of these groups or species share characteristics that inform the impact analysis similarly, it would be duplicative to repeat the same analysis for each species or stock. In addition, animals belonging to each stock within a species typically have the same hearing capabilities and behaviorally respond in the same manner as animals in other stocks within the species.
                    </P>
                    <HD SOURCE="HD3">Mysticetes</HD>
                    <P>
                        In Table 18 below for mysticetes, we indicate the total annual mortality, Level A and Level B harassment, and a number indicating the instances of total take as a percentage of abundance. Table 18 is unchanged from Table 72 in the 2018 AFTT final rule, except for updated information on mortality, as discussed above. For additional information and analysis supporting the negligible-impact analysis, see the 
                        <E T="03">Mysticetes</E>
                         discussion in the 
                        <E T="03">Group and Species-Specific Analyses</E>
                         section of the 2018 AFTT final rule, all of which remains applicable to this proposed rule unless specifically noted.
                    </P>
                    <GPH SPAN="3" DEEP="331">
                        <GID>EP13MY19.011</GID>
                    </GPH>
                    <P>Below we compile and summarize the information that supports our determination that the Navy's activities would not adversely affect any species or stocks through effects on annual rates of recruitment or survival for any of the affected mysticete species and stocks.</P>
                    <HD SOURCE="HD2">North Atlantic Right Whale (Western Stock)</HD>
                    <P>
                        As described in the 2018 AFTT final rule, the status of NARW is precarious and they are listed as endangered under the ESA. There is an active UME associated with the recent unusually high number of deaths, some of which have been attributed to entanglement or vessel strike, although no vessel strikes 
                        <PRTPAGE P="21166"/>
                        have been attributed to the Navy and no new NARW deaths have been documented since the 2018 AFTT final rule was published. The number of births in recent years has been unusually low and recent studies have reported individuals showing poor health or high stress levels. Accordingly, as described above and in the 2018 AFTT final rule, the Navy is implementing and would continue to implement a suite of mitigation measures that not only avoid the likelihood of ship strikes, but also minimize the severity of behavioral disruption by minimizing impacts in areas that are important for feeding and calving, thus ensuring that the relatively small number of Level B harassment takes that do occur are not expected to affect reproductive success or survivorship via detrimental impacts to energy intake or cow/calf interactions. Specifically, no mortality or Level A harassment is anticipated or proposed for authorization. Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances compared to the abundance (137 percent) combined with the fact that the AFTT Study Area overlaps most if not all of the range, suggests that many to most of the individuals in the stock will likely be taken, but only on one or two days per year, with no reason to think the days would likely be sequential. Regarding the severity of those individual takes by behavioral Level B harassment, as explained in the 2018 AFTT final rule, the duration of any exposure is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short), the received sound levels are largely below 172 dB with some lesser portion up to 178 dB (
                        <E T="03">i.e.,</E>
                         of a moderate or lower level, less likely to evoke a severe response), and because of the mitigation measures the exposures will not occur in areas or at times where impacts would be likely to affect feeding and energetics or important cow/calf interactions that could lead to reduced reproductive success or survival. Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level and of short duration and the associated lost opportunities and capabilities are not at a level that would impact reproduction or survival. 
                    </P>
                    <P>Altogether, any individual NARW is likely to be disturbed at a low-moderate level on no more than a couple of likely non-sequential days per year (and not in biologically important areas). Even given the fact that some of the affected individuals may have compromised health, there is nothing to suggest that such a low magnitude and severity of effects would result in impacts on reproduction or survival of any individual, much less annual rates of recruitment or survival for the stock. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on NARW. </P>
                    <HD SOURCE="HD2">Blue Whale (Western North Atlantic Stock)</HD>
                    <P>
                        This is a wide-ranging stock that is best considered as “an occasional visitor” to the U.S. EEZ, which may represent the southern limit of its feeding range (Hayes 
                        <E T="03">et al.,</E>
                         2018), though no specific feeding areas have been identified. For this reason, the abundances calculated by the Navy based on survey data in the U.S. EEZ are very low (9 and 104, in the U.S. EEZ and throughout the range respectively) and while NMFS' SAR does not predict an abundance, it does report an Nmin (minimum abundance) of 440. There is no currently reported trend for the population and there are no specific issues with the status of the stock that cause particular concern (
                        <E T="03">e.g.,</E>
                         no UMEs), although the species is listed as endangered under the ESA. We note, however, that this species was originally listed under the ESA as a result of the impacts from commercial whaling, which is no longer affecting the species. No mortality or Level A harassment is anticipated or proposed for authorization for blue whales. Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), given the number of total takes (47), the large range and wide-ranging nature of blue whales, and the minimum abundance identified in the SAR, there is no reason to think that any single animal will be taken by Level B harassment more than one time (though perhaps a few could be) and less than 10 percent of the population is likely to be impacted. Regarding the severity of those individual Level B harassment behavioral takes, as explained in the 2018 AFTT final rule, the duration of any exposure is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short) and the received sound levels are largely below 172 dB with a portion up to 178 dB (
                        <E T="03">i.e.,</E>
                         of a moderate or lower level, less likely to evoke a severe response). Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level and of short duration and the associated lost opportunities and capabilities not at a level that would impact reproduction or survival. 
                    </P>
                    <P>Altogether, less than 10 percent of the stock is likely to be impacted and any individual blue whale is likely to be disturbed at a low-moderate level on no more than a day or two days per year and not in any known biologically important areas. This low magnitude and severity of effects is unlikely to result in impacts on the reproduction or survival of any individual, much less annual rates of recruitment or survival for the stock. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on blue whales. </P>
                    <HD SOURCE="HD2">Bryde's Whale (Northern Gulf of Mexico Stock)</HD>
                    <P>The Northern Gulf of Mexico Bryde's whale is a small resident population and is listed as endangered under the ESA. Although there is no current UME, the small size of the population and its constricted range, combined with the lingering effects of exposure to oil from the DWH oil spill (which include adverse health effects on individuals, as well as population effects) are cause for considerable caution. Accordingly, as described above, the Navy is implementing and would continue to implement considerable time/area mitigation to minimize impacts within their limited range, including not planning major training exercises, which include the most powerful sound sources operating in a more concentrated area, limiting the hours of other sonar use, and not using explosives, with the exception of mine warfare activities, which has both reduced the amount of take and reduced the likely severity of impacts. No mortality or Level A harassment by tissue damage injury is anticipated or proposed for authorization, and only one Level A harassment by PTS take is estimated and proposed for authorization.</P>
                    <P>
                        Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances compared to the abundance (112 percent, Table 18) combined with the fact that the AFTT Study Area overlaps all of the small range, suggests that most to all of the individuals in the stock will likely be taken, but only on one or two days per year, with no reason to think the days would likely be sequential. Regarding the severity of those individual Level B harassment behavioral takes, as explained in the 2018 AFTT final rule, the duration of any exposure is expected to be between 
                        <PRTPAGE P="21167"/>
                        minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short); the received sound levels are largely below 172 dB with a portion up to 178 dB (
                        <E T="03">i.e.,</E>
                         of a moderate or lower level, less likely to evoke a severe response); and because of the mitigation the exposures will be of a less impactful nature. Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level and of short duration and the associated lost opportunities and capabilities not at a level that would impact reproduction or survival. For similar reasons the one estimated Level A harassment take by PTS for this stock is unlikely to have any effect on the reproduction or survival of that individual, even if it were to be experienced by an individual that also experiences one or more Level B harassment takes. 
                    </P>
                    <P>Altogether, any individual Bryde's whale is likely to be disturbed at a low-moderate level on no more than one or two days per year. Even given the fact that some of the affected individuals may have compromised health, there is nothing to suggest that such a low magnitude and severity of effects would result in impacts on the reproduction or survival of any individual, much less annual rates of recruitment or survival for the stock. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on the Gulf of Mexico stock of Bryde's whales. </P>
                    <HD SOURCE="HD2">Bryde's Whale (No Stock Designated—NSD)</HD>
                    <P>
                        These Bryde's whales span the mid- and southern Atlantic and have not been designated as a stock under the MMPA. There is no currently reported trend for the population and there are no specific issues with the status of the stock that cause particular concern (
                        <E T="03">e.g.,</E>
                         UMEs). No mortality or Level A harassment is anticipated or proposed for authorization. Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances compared to the abundance within the U.S. EEZ and both in and outside of the U.S. EEZ, respectively, is 626 percent and 60 percent (Table 18), though the percentages would be far lower if compared against the abundance of the entire range of this species in the Atlantic. This information suggests that only a portion of the stock is likely impacted (significantly less than 60 percent given the large range), but that there is likely some repeat exposure (5 to 12 days within a year) of some subset of individuals within the U.S. EEZ if some animals spend extended time within the U.S. EEZ. Regarding the severity of those individual Level B harassment behavioral takes, as explained in the 2018 AFTT final rule, the duration of any exposure is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short) and the received sound levels are largely below 172 dB with a portion up to 178 dB (
                        <E T="03">i.e.,</E>
                         of a moderate or lower level, less likely to evoke a severe response). Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level and of short duration and the associated lost opportunities and capabilities not at a level that would impact reproduction or survival. 
                    </P>
                    <P>Altogether, only a portion of the population is impacted and any individual Bryde's whale is likely to be disturbed at a low to moderate level, with likely many animals exposed only once or twice and a subset potentially disturbed across 5 to 12 likely non-sequential days not in any known biologically important areas. This low magnitude and severity of effects is not expected to result in impacts on annual rates of recruitment or survival for the stock. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on the NSD stock of Bryde's whales. </P>
                    <HD SOURCE="HD2">Minke Whale (Canadian East Coast Stock)</HD>
                    <P>This stock of minke whales spans the East Coast and far into Northern Canada waters. Minke whales in the Atlantic are currently experiencing a UME wherein there have been unexpectedly elevated deaths along the Atlantic Coast, some of which have been preliminarily attributed to human interaction (primarily fisheries interactions) or infectious disease. Two whales have stranded in 2019 (20 whales stranded in 2018 and 27 whales stranded in 2017). Because the most recent population estimate is based only on surveys in U.S. waters and slightly into Canada, and did not cover the habitat of the entire Canadian East Coast stock, the abundance is underestimated in the SAR and is likely significantly greater than what is reflected in the current SAR. NMFS proposes to authorize one mortality in seven years, and the resulting 0.14 annual mortality which falls below 10 percent of residual PBR (0.55), remains under the insignificance threshold, and would be considerably even lower if compared against a more appropriate PBR.</P>
                    <P>
                        Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances compared to the abundance within the U.S. EEZ and both in and outside of the U.S. EEZ, respectively, is 536 percent and 53 percent (Table 18). This information suggests that something less than half of the individuals are likely impacted, but that there is likely some repeat exposure (5 to 10 days within a year) of some subset of individuals within the U.S. EEZ if some animals spend extended time within the U.S. EEZ. Regarding the severity of those individual takes by behavioral Level B harassment, as explained in the 2018 AFTT final rule, the duration of any exposure is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short) and the received sound levels largely below 172 dB, with a portion up to 178 dB (
                        <E T="03">i.e.,</E>
                         of a moderate or lower level, less likely to evoke a severe response). Also, the Navy currently implements and would continue to implement time/area mitigation in the Northeast that minimizes major training exercises and total sonar hours in an area that significantly overlaps an important feeding area for minke whales. This mitigation will reduce the severity of impacts to minke whales by reducing interference in feeding that could result in lost feeding opportunities or necessitate additional energy expenditure to find other good foraging opportunities. Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level and of short duration and the associated lost opportunities and capabilities not at a level that would impact reproduction or survival. For similar reasons the five estimated Level A harassment takes by PTS for this stock are unlikely to have an effect on the reproduction or survival of any individual, even if PTS were to be experienced by an individual that also experiences one or more Level B harassment takes. 
                    </P>
                    <P>
                        Altogether, only a portion of the stock would be impacted and any individual minke whale is likely to be disturbed at a low to moderate level, with likely many animals exposed only once or twice and a subset potentially disturbed across 5 to 10 likely non-sequential days, minimized in biologically important areas. Even given the potential for compromised health of some individuals, this low magnitude and severity of effects is not expected to result in impacts on the reproduction or survival of individuals, nor are these harassment takes combined with the 
                        <PRTPAGE P="21168"/>
                        potential mortality expected to adversely affect this stock through impacts on annual rates of recruitment or survival for the stock. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on minke whales. 
                    </P>
                    <HD SOURCE="HD2">Fin Whale (Western North Atlantic Stock)</HD>
                    <P>
                        This stock spans the East Coast north into the Newfoundland waters of Canada. There is no currently reported trend for the population and there are no specific issues with the status of the stock that cause particular concern (
                        <E T="03">e.g.,</E>
                         no UMEs), although the species is listed as endangered under the ESA. NMFS proposes to authorize one mortality over the seven years of the rule, or 0.14 annually. With the addition of this 0.14 annual mortality, residual PBR is exceeded, which means the total human-caused mortality would exceed residual PBR by 0.14. However, as explained in the 2018 AFTT final rule, this does not mean that the stock is not at or increasing toward its optimum sustainable population level (OSP) or that one lethal take by the Navy over the seven years covered by this rule would adversely affect the stock through effects on annual rates of reproduction or survival. Consideration of all applicable information indicates that the proposed authorized mortality would not result in more than a negligible impact on this stock.
                    </P>
                    <P>
                        The abundance of fin whales is likely significantly greater than what is reflected in the current SAR because, as noted in the SAR, the most recent population estimate is based only on surveys in U.S. waters and slightly into Canada which does not include the habitat of the entire stock as it extends over a very large additional area into Nova Scotian and Newfoundland waters. Accordingly, if the PBR in the SAR reflected the actual abundance across the entire range of the stock, residual PBR would be notably higher. Additionally, the current abundance estimate does not account for availability bias due to submerged animals (
                        <E T="03">i.e.,</E>
                         estimates are not corrected to account for the fact that given X number of animals seen at the surface, we can appropriately assume that Y number were submerged and not counted). Without a correction for this bias, the abundance estimate is likely further biased low. Because of these limitations, the current calculated PBR is not a reliable indicator of how removal of animals will affect the stock's ability to reach or maintain OSP. We note that, generally speaking, while the abundance may be underestimated in this manner for some stocks due to the lack of surveys in areas outside of the U.S. EEZ, it is also possible that the human-caused mortality could be underestimated in the un-surveyed area. However, in the case of fin whales, most mortality is caused by entanglement in gear that is deployed relatively close to shore and, therefore, unrecorded mortality offshore would realistically be proportionally less as compared to the unsurveyed abundance and therefore the premise that PBR is likely underestimated still holds. Given the small amount by which residual PBR is exceeded and more significant degree (proportionally) to which abundance is likely underestimated, it is reasonable to conclude that if a more realistic PBR were used, the anticipated total human-caused mortality would be notably under it.
                    </P>
                    <P>We also note that 0.14 mortalities/serious injuries means one mortality/serious injury in one of the seven years and zero mortalities/serious injuries in six of the seven years. Therefore residual PBR would not be exceeded in 86 percent of the years covered by this rule. In situations where mortality/serious injury is fractional, consideration must be given to the lessened impacts due to the absence of mortality in six of the seven years. Further, as described in the 2018 AFTT final rule, the Atlantic Large Whale Take Reduction Plan directs multiple efforts and requirements towards reducing mortality from commercial fishing (via gear modifications, area closures, and other mechanisms) and NOAA Office of Law Enforcement has reported high compliance rates. Nonetheless, the exceedance of residual PBR calls for close attention to the remainder of impacts on fin whales from this activity to ensure that the total authorized impacts would be negligible.</P>
                    <P>
                        Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances compared to the abundance within the U.S. EEZ and both in and outside of the U.S. EEZ, respectively, is 323 percent and 37 percent (Table 18). This information suggests that something less than a third of the individuals are likely impacted, but that there is likely some repeat exposure (2-6 days within a year) of some subset of individuals within the U.S. EEZ if some animals spend extended time within the U.S. EEZ. Regarding the severity of those individual takes by behavioral Level B harassment, as explained in the 2018 AFTT final rule, the duration of any exposure is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short) and the received sound levels largely below 172 dB (
                        <E T="03">i.e.,</E>
                         of a moderate or lower level, less likely to evoke a severe response). Also, the Navy currently implements, and would continue to implement time/area mitigation in the Northeast that minimizes major training exercises and total sonar hours in an area that significantly overlaps an important BIA feeding area for fin whales. This mitigation will reduce the severity of impacts to fin whales by reducing interference in feeding that could result in lost feeding opportunities or necessitate additional energy expenditure to find other good opportunities. Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level, of short duration, and mostly not in a frequency band that would be expected to interfere with fin whale communication or other important low-frequency cues, and the associated lost opportunities and capabilities are not at a level that would impact reproduction or survival. For these same reasons (low level and frequency band), while a small permanent loss of hearing sensitivity may include some degree of energetic costs for compensating or may mean some small loss of opportunities or detection capabilities, at the expected scale the 33 estimated Level A harassment takes by PTS for fin whales would be unlikely to impact behaviors, opportunities, or detection capabilities to a degree that would interfere with reproductive success or survival of any individuals, even if PTS were experienced by an individual that also experiences one or more Level B harassment takes. 
                    </P>
                    <P>
                        Altogether, only a portion of the stock would be impacted and any individual fin whale is likely to be disturbed at a low to moderate level, with likely many animals exposed only once or twice and a subset potentially disturbed across approximately six likely non-sequential days, minimized in biologically important areas. This low magnitude and severity of effects is not expected to result in impacts on reproduction or survival of individuals, nor are these harassment takes combined with the single potential mortality expected to adversely affect this stock through impacts on annual rates of recruitment or survival for the stock. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on fin whales. 
                        <PRTPAGE P="21169"/>
                    </P>
                    <HD SOURCE="HD2">Humpback Whale (Gulf of Maine Stock)</HD>
                    <P>
                        This feeding group stock of humpback whales is one of several associated with the larger, and increasing, West Indies DPS. The Gulf of Maine stock is reported in the SAR as increasing in abundance. Nonetheless, humpback whales in the Atlantic are currently experiencing a UME in which a portion of the whales have shown evidence of entanglement or vessel strike. There have been nine strandings so far in 2019 (2018 had 25 total strandings and 2017 had 24 total strandings). NMFS proposes authorizing two mortalities over the seven-year period (versus the one mortality over the five-year period of the 2018 AFTT Final Rule), as described in the 
                        <E T="03">Estimated Take of Marine Mammals</E>
                         section above. Though an increase from the 2018 AFTT final rule, this amount of mortality (0.29 per year) still falls below the insignificance threshold of 10 percent of residual PBR (0.48) for the Gulf of Maine stock based on a stock abundance of 896 from the 2018 draft SAR. Also, importantly, deaths of humpback whales along the Atlantic coast (whether by ship strike or other source) must be considered within the context of the larger West Indies DPS, as animals along the coast could come from the Gulf of Maine stock or any of three or more other associated feeding groups. Specifically, the West Indies DPS numbers in excess of 10,000 whales and has an increasing growth trend of 3.1 percent (Bettridge 
                        <E T="03">et al.,</E>
                         2015), with an associated PBR, if calculated, much larger than that presented for the Gulf of Maine stock. Further, as described in the 2018 AFTT final rule, the Atlantic Large Whale Take Reduction Plan directs multiple efforts and requirements towards reducing mortality from commercial fishing (via gear modifications, area closures, and other mechanisms) and NOAA Office of Law Enforcement has reported high compliance rates. Therefore, even though the potential for M/SI from the Navy's activities has increased since the 2018 AFTT final rule, there is no information to indicate that the loss of two whales over seven years, even if it were to occur, would adversely affect the stock through effects on annual rates of recruitment or survival. See the 
                        <E T="03">Humpback Whale</E>
                         section in the 2018 AFTT final rule for additional supporting information. 
                    </P>
                    <P>
                        Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances (of any humpbacks) compared to the abundance within the U.S. EEZ and both in and outside of the U.S. EEZ, respectively, is 141 percent and 16 percent (Table 18). This suggests that only a small portion of the humpback whales in the AFTT Study Area would be likely impacted, with perhaps some individuals taken on a few days of the year. It would be impossible to determine exactly what portion of the takes are from the Gulf of Maine stock. However, based on information in the 2018 AFTT final rule, which indicated about one third of the humpback whales traversing the Atlantic Coast likely come from the Gulf of Maine stock, we estimate that approximately 250 of the 749 total humpback whale takes might be from the Gulf of Maine stock. Two hundred and fifty represents about 28 percent of the minimum population estimate for the Gulf of Maine humpback whale abundance in NMFS' draft 2018 SAR, equating to an expectation that few animals would be exposed more than one time. The remaining approximately 499 Level B harassment takes would affect individuals from the much larger West Indies DPS, with a relatively small percentage of individuals affected as the estimated abundance is greater than 10,000. Regarding the severity of those individual takes by behavioral Level B harassment, as explained in the 2018 AFTT final rule, the duration of any exposure is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short) and the received sound levels largely below 172 dB with a portion above 178 dB (
                        <E T="03">i.e.,</E>
                         of a moderate or lower level, less likely to evoke a severe response). Also, the Navy currently implements and would continue to implement time/area mitigation in the Northeast that minimizes major training exercises and total sonar hours in an area that significantly overlaps with an important feeding area for humpbacks. This mitigation will reduce the severity of impacts to humpbacks by reducing interference in feeding that could result in lost feeding opportunities or necessitate additional energy expenditure to find other good opportunities. Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level and of short duration and the associated lost opportunities and capabilities not at a level that would impact reproduction or survival. For similar reasons the three estimated Level A harassment takes by PTS for this stock are unlikely to have any effect on the reproduction or survival of any individual, even if PTS were to be experienced by an individual that also experiences one or more Level B harassment takes. 
                    </P>
                    <P>Altogether, only a portion of the stock or DPS is impacted and any individual humpback whale would likely be disturbed at a low-moderate level, with most animals exposed only once or twice, and minimized in biologically important areas. This low magnitude and severity of effects is not expected to result in impacts on the reproduction or survival of any individuals, nor are these harassment takes combined with the proposed authorized mortalities expected to adversely affect this stock through impacts on annual rates of recruitment or survival for the stock. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on humpback whales. </P>
                    <HD SOURCE="HD2">Sei Whale (Nova Scotia Stock)</HD>
                    <P>
                        This stock spans the northern East Coast and up to southern Newfoundland. There is no currently reported trend for the population and there are no specific issues with the status of the stock that cause particular concern (
                        <E T="03">e.g.,</E>
                         no UMEs), although the species is listed as endangered under the ESA. NMFS would authorize one mortality over the seven years of the rule, or 0.14 annually. With the addition of this 0.14 annual mortality, residual PBR is exceeded, which means the total human-caused mortality would exceed residual PBR by 0.44. However, as explained in the 2018 AFTT final rule, this does not mean that the stock is not at or increasing toward its OSP or that one lethal take by the Navy over the seven years covered by this rule would adversely affect the stock through effects on annual rates of reproduction or survival. Consideration of all applicable information indicates that the proposed authorized mortality would not result in more than a negligible impact on this stock.
                    </P>
                    <P>
                        As noted in the SAR, the abundance of sei whales is likely significantly greater than what is reflected in the current SAR because the population estimate is based only on surveys in U.S. waters and slightly into Canada, which does not cover the habitat of the entire stock, as it extends over a large additional area around to the south of Newfoundland. Accordingly, if a PBR were calculated based on an appropriately enlarged abundance, it would be higher. Additionally, the current abundance estimate does not account for availability bias due to submerged animals (
                        <E T="03">i.e.,</E>
                         estimates are not corrected to account for the fact that given X number of animals seen at the surface, we can appropriate assume that 
                        <PRTPAGE P="21170"/>
                        Y number were submerged and not counted). Without a correction for this bias, the abundance estimate is likely biased low. Because of these limitations, the current calculated PBR is not a reliable indicator of how removal of animals will affect the stock's ability to reach or maintain OSP. We note that, generally speaking, while the abundance may be underestimated in this manner for some stocks due to the lack of surveys in areas outside of the U.S. EEZ, it is also possible that the human-caused mortality could be underestimated in the un-surveyed area. However, in the case of sei whales, most mortality is caused by ship strike and the density of ship traffic is higher the closer you are to shore (making strikes more likely closer to shore) and, therefore, unrecorded mortality offshore would realistically be proportionally less as compared to the unsurveyed abundance and therefore the premise that PBR is likely underestimated still holds.
                    </P>
                    <P>Given the small amount by which residual PBR is exceeded and more significant degree (proportionally) to which abundance is likely underestimated, it is reasonable to think that if a more realistic PBR were used, the anticipated total human-caused mortality would be notably under residual PBR. We also note that 0.14 mortalities/serious injuries means one mortality/serious injury in one of the seven years and zero mortalities/serious injuries in six of the seven years. Further, as described in the 2018 AFTT final rule the Atlantic Large Whale Take Reduction Plan directs multiple efforts and requirements towards reducing mortality from commercial fishing (via gear modifications, area closures, and other mechanisms) and NOAA Office of Law Enforcement has reported high compliance rates.</P>
                    <P>
                        Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances compared to the abundance within the U.S. EEZ and both in and outside of the U.S. EEZ, respectively, is 317 percent and 7 percent (Table 18). This information suggests that only a very small portion of individuals in the stock would be likely impacted, but that there would likely be some repeat exposure (several days within a year) of some subset of individuals within the U.S. EEZ if some animals spend extended time within the U.S. EEZ. Regarding the severity of those individual takes by behavioral Level B harassment, as explained in the 2018 AFTT final rule, the duration of any exposure is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short) and the received sound levels largely below 172 dB with a portion up to 178 dB (
                        <E T="03">i.e.,</E>
                         of a moderate or lower level, less likely to evoke a severe response). Also, the Navy implements time/area mitigation in the Northeast that minimizes major training exercises and total sonar hours in an area that significantly overlaps an important BIA feeding area for sei whales, which will reduce the severity of impacts to sei whales by reducing interference in feeding that could result in lost feeding opportunities or necessitate additional energy expenditure to find other good opportunities. Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level and of short duration and the associated lost opportunities and capabilities not at a level that would impact reproduction or survival. For similar reasons the four estimated Level A harassment takes by PTS for this stock are unlikely to have any effect on the reproduction or survival of any individual, even if PTS were to be experienced by an individual that also experiences one or more Level B harassment takes. 
                    </P>
                    <P>Altogether, only a small portion of the stock would be impacted and any individual sei whale would likely be disturbed at a low-moderate level, with likely many animals exposed only once or twice and a subset potentially disturbed across a few days, minimized in biologically important areas. This low magnitude and severity of harassment effects is not expected to result in impacts on individual reproduction or survival, nor are these harassment takes combined with the single potential mortality expected to adversely affect this stock through impacts on annual rates of recruitment or survival. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on sei whales.</P>
                    <HD SOURCE="HD3">Odontocetes</HD>
                    <HD SOURCE="HD2">Sperm Whales, Dwarf Sperm Whales, and Pygmy Sperm Whales</HD>
                    <P>
                        In Table 19 below for sperm whale, dwarf sperm whales, and pygmy sperm whales, we indicate the total annual mortality, Level A and Level B harassment, and a number indicating the instances of total take as a percentage of abundance. Table 19 is unchanged from Table 73 in the 2018 AFTT final rule, except for updated information on mortality, as discussed above. For additional information and analysis supporting the negligible-impact analysis, see the 
                        <E T="03">Odontocetes</E>
                         discussion as well as the 
                        <E T="03">Sperm Whales, Dwarf Sperm Whales, and Pygmy Sperm Whales</E>
                         discussion in the 
                        <E T="03">Group and Species-Specific Analyses</E>
                         section of the 2018 AFTT final rule, all of which remains applicable to this proposed rule unless specifically noted.
                    </P>
                    <GPH SPAN="3" DEEP="323">
                        <PRTPAGE P="21171"/>
                        <GID>EP13MY19.012</GID>
                    </GPH>
                    <P>Below we compile and summarize the information that supports our determination that the Navy's activities would not adversely affect any species or stocks through effects on annual rates of recruitment or survival for any of the affected species and stocks addressed in this section. </P>
                    <HD SOURCE="HD3">Sperm Whale (North Atlantic Stock)</HD>
                    <P>
                        This stock spans the East Coast out into oceanic waters well beyond the U.S. EEZ. There is no currently reported trend for the stock and, although the species is listed as endangered under the ESA, there are no specific issues with the status of the stock that cause particular concern (
                        <E T="03">e.g.,</E>
                         no UMEs). NMFS proposes to authorize one mortality over the seven years covered by this rule, and the resulting 0.14 annual mortality which falls below 10 percent of residual PBR (0.28), remains below the PBR insignificance threshold. As discussed in the 2018 AFTT final rule, there are no known factors, information, or unusual circumstances that indicate that this potential M/SI below the insignificance threshold could have adverse effects on the stock through effects on annual rates of recruitment or survival. One Level A harassment take by tissue damage is also estimated and proposed for authorization which, as discussed in the 2018 AFTT final rule, could range in impact from minor to something just less than M/SI that could seriously impact fitness. However, given the Navy's mitigation and the sperm whale's large size, which improves detection by Lookouts, exposure at the closer to the source and more severe end of the spectrum is less likely, and we cautiously assume some moderate impact for this single take that could lower one individual's fitness within the year such that a female (assuming a 50 percent chance of the one take being a female) might forego reproduction for one year. As discussed in the 2018 AFTT final rule, foregone reproduction has less of an impact on population rates than death (especially for one year) and one instance would not be expected to impact annual rates of recruitment or survival, even if it were a female.
                    </P>
                    <P>
                        Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances of harassment compared to the abundance within the U.S. EEZ and both in and outside of the U.S. EEZ, respectively, is 544 percent and 41 percent (Table 19). This information, combined with the known range of the stock, suggests that something less than one half of the individuals in the stock would likely be impacted, but that there would likely be some repeat exposure (2-11 days within a year) of some subset of individuals that remain within the U.S. EEZ for an extended time. Regarding the severity of those individual takes by behavioral Level B harassment, as explained in the 2018 AFTT final rule, the duration of any exposure response is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short) and the received sound levels largely between 160 and 172 dB (
                        <E T="03">i.e.,</E>
                         of a lower, to occasionally moderate, level). Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level and of short duration and the associated lost opportunities and capabilities not at a level that would impact reproduction or survival. For similar reasons three estimated Level A harassment takes by PTS for this stock is unlikely to have any effect on the reproduction or survival of any individual, even if PTS were to be experienced by an individual that also experiences one or more Level B harassment takes. 
                    </P>
                    <P>
                        Altogether, only a small portion of the stock would be impacted and any individual sperm whale would likely be disturbed at a low-moderate level, with the majority of animals likely disturbed 
                        <PRTPAGE P="21172"/>
                        once or not at all, and a subset potentially disturbed across 2-11 likely non-sequential days. Even for an animal disturbed at the high end of this range (11 days over a year), given the low to moderate impact from each incident, and the fact that few days with take would likely be sequential, no impacts to individual fitness are expected. This low to occasionally moderate magnitude and severity of effects is not expected to result in impacts on reproduction or survival, and nor are these harassment takes combined with the single proposed authorized mortality and one possible instance of foregone reproduction expected to adversely affect the stock through annual rates of recruitment or survival. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on North Atlantic sperm whales. 
                    </P>
                    <HD SOURCE="HD3">Sperm Whale, Dwarf Sperm Whale, and Pygmy Sperm Whale (Gulf of Mexico Stocks)</HD>
                    <P>
                        These stocks suffer from lingering health issues from the DWH oil spill (6-7 percent of individuals of these stocks with adverse health effects), which means that some could be more susceptible to exposure to other stressors, and negative population effects (21-42 years until the DWH oil-injured population trajectory is projected to catch up with the baseline population trajectory (
                        <E T="03">i.e.,</E>
                         in the absence of DWH, reported as years to recovery). Neither mortality nor tissue damage from explosives is anticipated or proposed to be authorized for any of these three stocks, and sperm whales are not expected to incur PTS. Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances of harassment compared to the abundance is 54-78 percent (Table 19), which suggests that for each of the three species/stocks either this percentage of the individuals in these stocks would all be taken by harassment on a single day, or a small subset may be taken on a few days and the remainder not taken at all. Regarding the severity of those individual takes by behavioral Level B harassment, as explained in the 2018 AFTT final rule, the duration of any exposure response is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short) and the received sound levels are largely between 160 and 172 dB (
                        <E T="03">i.e.,</E>
                         of a lower level, less likely to evoke a severe response). Additionally, the Navy is currently implementing and would continue to implement mitigation areas for sperm whales that are expected to reduce impacts in important feeding areas, further lessening the severity of impacts. Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level, of short duration, and mostly not in a frequency band that would be expected to interfere significantly with conspecific communication, echolocation, or other important low-frequency cues. Also, there is no reason to believe that any individual would incur these TTS takes more than a few days in a year, and the associated lost opportunities and capabilities would not be expected to impact reproduction or survival. For these same reasons (low level and frequency band), while a small permanent loss of hearing sensitivity may include some degree of energetic costs for compensating or may mean some small loss of opportunities or detection capabilities, 70 estimated Level A harassment takes by PTS for each of the two Kogia stocks in the Gulf of Mexico would be unlikely to impact behaviors, opportunities, or detection capabilities to a degree that would interfere with reproductive success or survival of any individual, even if PTS were to be experienced by an animal that also experiences one or more Level B harassment takes. 
                    </P>
                    <P>Altogether, only a portion of these stocks would be impacted and any individual sperm, dwarf sperm, or pygmy sperm whale is likely to be disturbed at a low to occasionally moderate level and no more than a few days per year. Even given the fact that some of the affected individuals may have compromised health, there is nothing to suggest that such a low magnitude and severity of effects would result in impacts on the reproduction or survival of individuals, much less annual rates of recruitment or survival for any of the stocks. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on the Gulf of Mexico stocks of sperm whales, dwarf sperm whales, and pygmy sperm whales. </P>
                    <HD SOURCE="HD3">Pygmy and Dwarf Sperm Whales (Western North Atlantic Stocks)</HD>
                    <P>These stocks span the deeper waters of the East Coast north to Canada and out into oceanic waters beyond the U.S. EEZ. There is no currently reported trend for these populations and there are no specific issues with the status of the stocks that cause particular concern. Neither mortality nor tissue damage from explosives is anticipated or proposed to be authorized for these stocks. Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances of harassment compared to the abundance within the U.S. EEZ and both in and outside of the U.S. EEZ, respectively, is 2,105 percent and 360 percent (Table 19). This information, combined with the known range of the stock, suggests that while not all of the individuals in these stocks would most likely be taken (because they span well into oceanic waters) of those that are taken, most would be taken over several repeated days (though likely not sequential) and some subset that spends extended time within the U.S. EEZ would likely be taken over a larger amount of days (likely 15-42 days during a year), some of which could be sequential.</P>
                    <P>
                        Regarding the severity of the individual takes by behavioral Level B harassment, as explained in the 2018 AFTT final rule, the duration of any exposure response is expected to be between minutes and hours (and likely not more than 24 hours) and the received sound levels are largely between 160 and 172 dB (
                        <E T="03">i.e.,</E>
                         of a lower level, less likely to evoke a severe response). Additionally, while interrupted feeding bouts are a known response and concern for odontocetes, we also know that there are often viable alternative habitat options in the relative vicinity. Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level, of short duration and mostly not in a frequency band that would be expected to interfere significantly with conspecific communication, echolocation, or other important low-frequency cues. Also, there is no reason to believe that any individual would incur these TTS takes more than a few days in a year, and the associated lost opportunities and capabilities would not be expected to impact reproduction or survival. For these same reasons (low level and frequency band), while a small permanent loss of hearing sensitivity may include some degree of energetic costs for compensating or may mean some small loss of opportunities or detection capabilities, at the expected scale the 94 estimated Level A harassment takes by PTS for each of the two Kogia stocks in the North Atlantic would be unlikely to impact behaviors, opportunities, or detection capabilities to a degree that would interfere with reproductive success or survival of any individual, even if PTS were to be experienced by an individual that also 
                        <PRTPAGE P="21173"/>
                        experiences one or more Level B harassment takes.
                    </P>
                    <P>Altogether, most of the stock would likely be taken (at a low to occasionally moderate level) over several days a year, and some smaller portion of the stock would likely be taken on a relatively moderate to high number of days across the year, some of which could be sequential days. Though the majority of impacts are expected to be of a lower to sometimes moderate severity, the larger number of takes (in total and for certain individuals) makes it more likely (probabilistically) that a small number of individuals could be interrupted during foraging in a manner and amount such that impacts to the energy budgets of females (from either losing feeding opportunities or expending considerable energy to find alternative feeding options) could cause them to forego reproduction for a year (energetic impacts to males generally have little impact on population rates unless they cause death, and it takes extreme energy deficits beyond what would ever be likely to result from these activities to cause the death of an adult marine mammal). As noted previously and discussed more fully in the 2018 AFTT final rule, however, foregone reproduction (especially for one year) has far less of an impact on population rates than mortality, and a small number of instances of foregone reproduction would not be expected to adversely impact annual rates of recruitment or survival, especially given that PBR for both of these stocks is 21. For these reasons, in consideration of all of the effects of the Navy's activities combined, we have preliminarily determined that the proposed authorized take would have a negligible impact on the Western North Atlantic stocks of pygmy and dwarf sperm whales. </P>
                    <HD SOURCE="HD2">Dolphins and Small Whales</HD>
                    <P>
                        In Table 20 below for dolphins and small whales, we indicate the total annual mortality, Level A and Level B harassment, and a number indicating the instances of total take as a percentage of abundance. Table 20 is unchanged from Table 74 in the 2018 AFTT final rule, except for updated information on mortality, as discussed above. For additional information and analysis supporting the negligible-impact analysis, see the 
                        <E T="03">Odontocetes</E>
                         discussion as well as the 
                        <E T="03">Dolphins and Small Whales</E>
                         discussion in the 
                        <E T="03">Group and Species-Specific Analyses</E>
                         section of the 2018 AFTT final rule, all of which remains applicable to this proposed rule unless specifically noted.
                    </P>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="21174"/>
                        <GID>EP13MY19.013</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="124">
                        <PRTPAGE P="21175"/>
                        <GID>EP13MY19.014</GID>
                    </GPH>
                    <P>Below we compile and summarize the information that supports our determination that the Navy's activities would not adversely affect any species or stocks through effects on annual rates of recruitment or survival for any of the affected species or stocks addressed in this section. </P>
                    <HD SOURCE="HD3">Atlantic White-Sided Dolphin and Short-Beaked Common Dolphin (Western North Atlantic Stocks)</HD>
                    <P>
                        There is no currently reported trend for these stocks and there are no specific issues with the status of these stocks that cause particular concern (
                        <E T="03">e.g.,</E>
                         no UMEs). We anticipate and therefore propose to authorize one and six mortalities over the course of seven years for these two stocks, which is 0.14 and 0.86 annual mortalities for each stock, respectively. Given the large residual PBR values for these stocks (248 and 148), this number of mortalities falls well under the insignificance threshold. There are no known factors, information, or unusual circumstances that indicate that this estimated M/SI below the insignificance threshold could have adverse effects on these stocks through effects on annual rates of recruitment or survival. Some Level A harassment take by tissue damage from explosives has also been estimated and proposed to be authorized for these stocks (3 and 36, respectively). As discussed previously and in the 2018 AFTT final rule, tissue damage effects could range in impact from minor to something just less than M/SI that could seriously impact fitness. However, given the Navy's mitigation, which makes exposure at the closer to the source and more severe end of the spectrum less likely, we cautiously assume some moderate impact for this category of take that could lower an individual's fitness within the year such that females (assuming a 50 percent chance that a take is a female) might forego reproduction for one year. As noted previously, foregone reproduction has less of an impact on population rates than death (especially for one year) and the number of takes anticipated for each stock would not be expected to impact annual rates of recruitment or survival, even if all of the takes were females (which would be highly unlikely), especially given the high residual PBRs of these stocks. In other words, if the stocks can absorb the numbers of mortalities indicated through each stock's residual PBR without impacting ability to approach OSP, they could absorb the significantly lesser effects of a small number of one-year delay in calving.
                    </P>
                    <P>
                        Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances of harassment compared to the abundance within the U.S. EEZ and both in and outside of the U.S. EEZ for these two stocks, respectively, is 308-777 percent and 34-110 percent (Table 20). This information suggests that some portion of these stocks would likely not be taken at all, but that there would likely be some repeat exposure (2-15 days within a year) of some subset of individuals. Regarding the severity of those individual takes by behavioral Level B harassment, as explained in the 2018 AFTT final rule, the duration of any exposure response is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short) and the received sound levels largely below 172 dB (
                        <E T="03">i.e.,</E>
                         of a lower level, less likely to evoke a severe response). Additionally, while we do not have a specific reason to expect that these takes would occur sequentially on more than several days in a row or be more severe in nature, the probability of this occurring increases the higher the total take numbers. While interrupted feeding bouts are a known response and concern for odontocetes, we also know that there are often viable alternative habitat options in the relative vicinity. Given the higher number of takes and the associated abundances (especially for short-beaked common dolphin) we acknowledge the possibility that some smaller subset of individuals could experience behavioral disruption of a degree that impacts energetic budgets such that reproduction could be delayed for a year. However, considering the potential reproductive effects from tissue damage and from these levels of take by behavioral Level B harassment, in combination with the estimated mortality, this degree of effect on the small subset of individuals that could be affected is still not expected to adversely affect the stocks through effects on annual rates of recruitment or survival.
                    </P>
                    <P>Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level, of short duration, and not in a frequency band that would be expected to significantly interfere with dolphin communication, or echolocation or other important low-frequency cues. Therefore, the associated lost opportunities and capabilities would not be expected to impact reproduction or survival of any individuals. For these same reasons (low level and the likely frequency band), while a small permanent loss of hearing sensitivity may include some degree of energetic costs for compensating or may mean some small loss of opportunities or detection capabilities, the estimated Level A harassment takes by PTS for the two dolphin stocks (7 and 101, respectively) would be unlikely to impact behaviors, opportunities, or detection capabilities to a degree that would interfere with reproductive success or survival of any individual, even if PTS were to be experienced by an animal that also experiences one or more Level B harassment takes.</P>
                    <P>
                        Altogether, individual dolphins would likely be taken at a low level, with some animals likely taken once or not at all, many potentially disturbed at low levels across 2-15 predominantly non-sequential days, and a small number potentially experiencing a level of effects that could result in curtailed reproduction for one year. This magnitude and severity of effects, including consideration of the estimated mortality, is not expected to result in impacts on annual rates of recruitment 
                        <PRTPAGE P="21176"/>
                        or survival for either of the stocks, especially given the status of the stocks. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on these two Western North Atlantic stocks of dolphins. 
                    </P>
                    <HD SOURCE="HD3">Pantropical Spotted Dolphin and Spinner Dolphin (Gulf of Mexico Stocks)</HD>
                    <P>As described in the 2018 AFTT final rule, the Gulf of Mexico dolphin stocks indicated in Table 20 suffer from lingering health issues resulting from the DWH oil spill (7 and 17 percent of individuals of these stocks, respectively, have adverse health effects), which means that some of them could be more susceptible to exposure to other stressors, as well as negative population effects (predicting it will take up to 39 and 105 years, respectively, for stocks to return to population growth rates predicted in the absence of DWH effects). We propose to authorize one mortality over the course of seven years for each of these two stocks, respectively, which is 0.14 annual mortalities for each stock. Given the large residual PBR values for these stocks (402 and 62, respectively), this number of mortalities falls well under the insignificance threshold. As discussed in the 2018 AFTT final rule, there are no known factors, information, or unusual circumstances that indicate that this estimated M/SI below the insignificance threshold could have adverse effects on these stocks through effects on annual rates of recruitment or survival. Some Level A harassment take by tissue damage from explosives has also been estimated and proposed to be authorized for these stocks (6 and 14, respectively). As noted previously, tissue damage effects could range in impact from minor to something just less than M/SI that could seriously impact fitness. However, given the Navy's mitigation, which makes exposure at the closer to the source and more severe end of the spectrum less likely, we cautiously assume some moderate impact for this category of take that could lower an individual's fitness within the year such that females (assuming a 50 percent chance that a take is a female) might forego reproduction for one year. As noted previously, foregone reproduction has less of an impact on population rates than death (especially for one year) and the number of takes anticipated for each stock would not be expected to impact annual rates of recruitment or survival, even if all of the takes were females (which would be highly unlikely), especially given the high residual PBRs of these stocks. In other words, if the stocks can absorb the numbers indicated through each stock's residual PBR without impacting ability to approach OSP, they can absorb the significantly lesser effect of a very small number of one-year delay in calving. </P>
                    <P>
                        Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances of harassment compared to the abundance is 32 percent and 60 percent, respectively, reflecting that only a subset of each stock would be taken by behavioral Level B harassment within a year. Of that subset, those taken would likely be taken one time, but if taken more than that, the 2 or 3 days would not likely be sequential (Table 20). Regarding the severity of those individual takes by behavioral Level B harassment, as explained in the 2018 AFTT final rule, the duration of any exposure response is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short) and the received sound levels largely below 172 dB (
                        <E T="03">i.e.,</E>
                         of a lower to occasionally moderate severity). 
                    </P>
                    <P>Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level, of short duration, and not in a frequency band that would be expected to significantly interfere with dolphin communication, or echolocation or other important low-frequency cues. Therefore, the associated lost opportunities and capabilities are not expected to impact reproduction or survival. For these same reasons (low level and the likely frequency band), while a small permanent loss of hearing sensitivity may include some degree of energetic costs for compensating or may mean some small loss of opportunities or detection capabilities, the estimated Level A harassment takes by PTS for the dolphin stocks addressed here (15 and 31, respectively) would be unlikely to impact behaviors, opportunities, or detection capabilities to a degree that would interfere with reproductive success or survival of any individuals. </P>
                    <P>Altogether, any individual dolphin would likely be taken at a low to occasionally moderate level, with most animals likely not taken at all and with a subset of animals being taken up to a few non-sequential days. Even given the fact that some of the affected individuals may have compromised health, there is nothing to suggest that such a low magnitude and severity of effects, including the potential tissue damage, would result in impacts on annual rates of recruitment or survival for either of these two stocks. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on the Gulf of Mexico stocks of pantropical spotted dolphins and spinner dolphins. </P>
                    <HD SOURCE="HD3">Western North Atlantic Dolphin Stocks (All Stocks in Table 20 Except Atlantic White-Sided Dolphin and Short-Beaked Common Dolphin)</HD>
                    <P>
                        There are no specific issues with the status of these stocks that cause particular concern (
                        <E T="03">e.g.,</E>
                         no UMEs). No mortality is expected nor it proposed for authorization for these stocks. For some of these stocks, some tissue damage has been estimated and proposed to be authorized (1-9 depending on the stock). As discussed previously, tissue damage effects could range in impact from minor to something just less than M/SI that could seriously impact fitness. However, given the Navy's mitigation, which makes exposure at the closer to the source and more severe end of the spectrum less likely, we cautiously assume some moderate impact for all these takes that could lower an individual's fitness within the year such that a small number of females (assuming a 50 percent chance of being a female) might forego reproduction for one year. As noted previously, foregone reproduction has less of an impact on population rates than death (especially for one year) and one to a few instances would not be expected to impact annual rates of recruitment or survival, even if all of the takes were females (which would be highly unlikely), especially given the higher residual PBRs, which is known for the majority of stocks. For stocks with no calculated residual PBR or where abundance is unknown, the limited information available on population size indicates that the very low number of females who might forego reproduction would have no effect on annual rates of recruitment or survival. 
                    </P>
                    <P>
                        Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances of harassment compared to the abundance ranges up to 984 percent inside the U.S. EEZ (though some are significantly lower) and is generally much lower across the whole range of most stocks, reflecting that for many stocks only a subset of the stock will be impacted—although alternately for a few of the smaller bay stocks all individuals are expected to be taken across multiple days (Table 20). Generally, individuals of most stocks (especially bottlenose dolphins) might 
                        <PRTPAGE P="21177"/>
                        be taken no more than several times each, while the other species in this group will only accrue takes to a portion of the stock, but individuals might be taken across 2-20 days within a year. Regarding the severity of those individual takes by behavioral Level B harassment, as explained in the 2018 AFTT final rule, the duration of any exposure response is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short) and the received sound levels largely below 172 dB (
                        <E T="03">i.e.,</E>
                         of a lower level, less likely to evoke a severe response). While we do not have reason to expect that these takes would occur sequentially on more than several days in a row or be more severe in nature, the probability of this occurring increases the higher the total take numbers. Given higher percentages when compared to abundances, and especially where the absolute number of takes is higher (
                        <E T="03">e.g.,</E>
                         spinner dolphin), we acknowledge the possibility that some smaller subset of individuals (especially in the larger stocks with higher total take numbers) could experience behavioral disruption of a degree that impacts energetic budgets such that reproduction could be delayed for a year. However, considering the very small number of potential reproductive effects from Level A harassment by tissue damage (1-9 depending on stock and assuming all individuals are female, which is very unlikely) in addition to the possible reproductive effect on a small subset of individuals from the takes by behavioral Level B harassment, this degree of effects on a small subset of individuals is still not expected to adversely affect annual rates of recruitment or survival. For the smaller Estuarine stocks with the potential repeated days of disturbance, we note that as described in the 2018 AFTT final rule, the activities that the Navy conducts in inland areas (not MTEs, etc.) are expected to generally result in lower severity responses, further decreasing the likelihood that they would cause effects on reproduction or survival, even if accrued over several sequential days. 
                    </P>
                    <P>Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level, of short duration, and not in a frequency band that would be expected to significantly interfere with dolphin communication, or echolocation or other important low-frequency cues. Therefore, the associated lost opportunities and capabilities would not be expected to impact reproduction or survival. For these same reasons (low level and the likely frequency band), while a small permanent loss of hearing sensitivity may include some degree of energetic costs for compensating or may mean some small loss of opportunities or detection capabilities, the estimated Level A harassment takes by PTS for the dolphin stocks addressed here (between 1 and 77) would be unlikely to impact behaviors, opportunities, or detection capabilities to a degree that would interfere with reproductive success or survival of any individual, even if PTS were to be experienced by an individual that also experiences one or more Level B harassment takes. </P>
                    <P>Altogether, any individual dolphin would likely be taken at a low to occasionally moderate level, with some animals likely taken once or not at all, a subset potentially disturbed across 2-20 predominantly non-sequential days, and a small number potentially experiencing a level of effects that could curtail reproduction for one year. The magnitude and severity of effects described is not expected to result in impacts on annual rates of recruitment or survival for any of the stocks. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on these Western North Atlantic stocks of dolphins. </P>
                    <HD SOURCE="HD3">Gulf of Mexico Dolphin Stocks (All of the Stocks Indicated in Table 20 Except Pantropical Spotted Dolphin and Spinner Dolphin)</HD>
                    <P>
                        As mentioned above and discussed in the 2018 AFTT final rule, the Gulf of Mexico stocks indicated in Table 20 suffer from lingering health issues resulting from the DWH oil spill (3-30 percent of individuals of these stocks have adverse health effects), which means that some of them could be more susceptible to exposure to other stressors, as well as negative population effects (predicting it will take up to 76 years, with that number varying across stocks, for stocks to return to population growth rates predicted in the absence of DWH effects). Of note, the Northern Coastal bottlenose dolphin adverse effect statistics are about twice as high as the others (
                        <E T="03">i.e.,</E>
                         all other stocks are below 17 percent). No mortality has been estimated or proposed to be authorized for these stocks, however a few Level A harassment takes by tissue damage from explosives (zero for most, 1-2 for a few, and 6 for the Atlantic spotted dolphin stock) are estimated and proposed to be authorized. As noted previously, tissue damage effects could range in impact from minor to something just less than M/SI that could seriously impact fitness. However, given the Navy's mitigation, which makes exposure at the closer to the source and more severe end of the spectrum less likely, we cautiously assume some moderate impact for these Level A harassment takes that could lower an individual's fitness within the year such that a female (assuming a 50 percent chance of being a female) might forego reproduction for one year. As noted previously, foregone reproduction has less of an impact on population rates than death (especially for one year) and a few instances, even up to six for the Atlantic spotted dolphin stock, would not be expected to impact annual rates of recruitment or survival, even if all of the takes were of females (which is highly unlikely). 
                    </P>
                    <P>
                        Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances of harassment compared to the abundance ranges up to 177 percent, but is generally much lower for most stocks, reflecting that generally only a subset of each stock would be taken, with those in the subset taken only a few non-sequential days of the year (Table 20). Regarding the severity of those individual takes by Level B behavioral harassment, as explained in the 2018 AFTT final rule, the duration of any exposure response is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short) and the received sound levels largely below 172 dB (
                        <E T="03">i.e.,</E>
                         of a lower to occasionally moderate severity). 
                    </P>
                    <P>
                        Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level, of short duration, and not in a frequency band that would be expected to significantly interfere with dolphin communication, or echolocation or other important low-frequency cues. Therefore, the associated lost opportunities and capabilities would not be expected to impact reproduction or survival. For these same reasons (low level and the likely frequency band), while a small permanent loss of hearing sensitivity may include some degree of energetic costs for compensating or may mean some small loss of opportunities or detection capabilities, the estimated Level A harassment takes by PTS for the dolphin stocks addressed here (all 3 or below, with the exception of three stocks with much larger abundances with 4, 8, and 15 PTS takes) would be unlikely to impact behaviors, opportunities, or detection capabilities to a degree that would interfere with reproductive success or survival of any individual, even if PTS were to be experienced by an animal that also 
                        <PRTPAGE P="21178"/>
                        experiences one or more Level B harassment takes. 
                    </P>
                    <P>Altogether, any individual dolphin would likely be taken at a low to occasionally moderate level, with many animals likely not taken at all and with a subset of animals being taken up to a few times. A very small number could potentially experience tissue damage that could curtail reproduction for one year. Even given the fact that some of the affected individuals may have compromised health, there is nothing to suggest that such a low magnitude and severity of effects would result in impacts on annual rates of recruitment or survival for any of the Gulf of Mexico stocks indicated in Table 20. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on these Gulf of Mexico stocks of dolphins.</P>
                    <HD SOURCE="HD2">Harbor Porpoise</HD>
                    <P>
                        In Table 21 below for porpoises, we indicate the total annual mortality, Level A and Level B harassment, and a number indicating the instances of total take as a percentage of abundance. Table 21 is unchanged from Table 75 in the 2018 AFTT final rule. For additional information and analysis supporting the negligible-impact analysis, see the 
                        <E T="03">Odontocetes</E>
                         discussion as well as the 
                        <E T="03">Harbor Porpoise</E>
                         discussion in the 
                        <E T="03">Group and Species-Specific Analyses</E>
                         section of the 2018 AFTT final rule, all of which remains applicable to this proposed rule unless specifically noted.
                    </P>
                    <P>Table 21. Annual estimated takes by Level B harassment, Level A harassment, and mortality for porpoises in the AFTT Study Area and number indicating the instances of total take as a percentage of stock abundance.</P>
                    <P>
                        Note: In the table we compare estimated takes to abundance estimates generated from the same underlying density estimate (as described in the 
                        <E T="03">Estimated Take of Marine Mammals</E>
                         section of the 2018 AFTT final rule), versus abundance estimates directly from NMFS' SARs, which are not based on the same data and would not be appropriate for this purpose. Note that comparisons are made both within the U.S. EEZ only (where density estimates have lesser uncertainty) and across the whole Study Area (which offers a more comprehensive comparison for many stocks).
                    </P>
                    <P>Total takes inside and outside U.S. EEZ represent the sum of annual Level A and Level B harassment from training and testing plus harassment take from one large ship shock trial.</P>
                    <GPH SPAN="3" DEEP="202">
                        <GID>EP13MY19.015</GID>
                    </GPH>
                    <P>Below we compile and summarize the information that supports our determination that the Navy's activities would not adversely affect harbor porpoises through effects on annual rates of recruitment or survival.</P>
                    <P>
                        The Gulf of Maine/Bay of Fundy stock of harbor porpoise is found predominantly in northern U.S. coastal waters (&lt;150 m depth) and up into Canada's Bay of Fundy. No mortality or tissue damage by explosives are anticipated or proposed for authorization for this stock and there are no specific issues with the status of the stock that cause particular concern (
                        <E T="03">e.g.,</E>
                         no UMEs). Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances compared to the abundance within the U.S. EEZ and both in and outside of the U.S. EEZ, respectively, is 941 percent and 80 percent (Table 21). This information, combined with the known range of the stock, suggests that only a portion of the individuals in the stock would likely be impacted (
                        <E T="03">i.e.,</E>
                         notably less than 80 percent given the likely repeats; in other words more than 20 percent would be taken zero times), but that there would likely be some amount of repeat exposures across days (perhaps 6-19 days within a year) for some subset of individuals that spend extended times within the U.S. EEZ. Regarding the severity of those individual takes by behavioral Level B harassment, as explained in the 2018 AFTT final rule, the duration of any exposure response is expected to be from minutes to hours and not likely exceeding 24 hrs, and the received sound levels of the MF1 bin are largely between 154 and 166 dB, which, for a harbor porpoise (which have a lower behavioral Level B harassment threshold) would mostly be considered a moderate level. 
                    </P>
                    <P>
                        Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level, of short duration, and not in a frequency band that would be expected to significantly interfere with harbor porpoise communication, or echolocation or other important low-frequency cues. Therefore, the associated lost opportunities and capabilities would not be expected to impact reproduction or survival. For these same reasons (low level and the likely frequency band), while a small permanent loss of hearing sensitivity 
                        <PRTPAGE P="21179"/>
                        may include some degree of energetic costs for compensating or may mean some small loss of opportunities or detection capabilities, the estimated 454 Level A harassment takes by PTS for harbor porpoise would be unlikely to impact behaviors, opportunities, or detection capabilities to a degree that would interfere with reproductive success or survival for most individuals, even if PTS were to be experienced by an individual that also experiences one or more Level B harassment takes. Because of the high number of PTS takes, we acknowledge that a few animals could potentially incur permanent hearing loss of a higher degree that could potentially interfere with their successful reproduction and growth. However, given the status of the stock (high abundance and residual PBR of 451), even if this occurred, it would not adversely impact rates of recruitment or survival. 
                    </P>
                    <P>Altogether, because harbor porpoises are particularly sensitive, it is likely that a fair number of the responses would be of a moderate nature. Additionally, as noted, some portion of the stock may be taken repeatedly on up to 19 days within a year, with some of those being sequential. Given this and the larger number of total takes (both to the stock and to individuals), it is more likely (probabilistically) that some small number of individuals could be interrupted during foraging in a manner and amount such that impacts to the energy budgets of females (from either losing feeding opportunities or expending considerable energy to find alternative feeding options) could cause them to forego reproduction for a year (energetic impacts to males generally have limited impact on population rates unless they cause death, and it takes extreme energy deficits beyond what would ever be likely to result from these activities to cause the death of an adult marine mammal). As noted previously, however, foregone reproduction (especially for one year) has far less of an impact on population rates than mortality and a small number of instances would not be expected to adversely impact annual rates of recruitment or survival, especially given that the residual PBR of harbor porpoises is 451. All indications are that the number of times in which reproduction would be likely to be foregone would not affect the stock's annual rates of recruitment or survival. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on harbor porpoises.</P>
                    <HD SOURCE="HD2">Beaked Whales</HD>
                    <P>
                        In Table 22 below for beaked whales, we indicate the total annual mortality, Level A and Level B harassment, and a number indicating the instances of total take as a percentage of abundance. Table 22 is unchanged from Table 76 in the 2018 AFTT final rule. For additional information and analysis supporting the negligible-impact analysis, see the 
                        <E T="03">Odontocetes</E>
                         discussion as well as the 
                        <E T="03">Beaked Whales</E>
                         discussion in the 
                        <E T="03">Group and Species-Specific Analyses</E>
                         section of the 2018 AFTT final rule, all of which remains applicable to this proposed rule unless specifically noted.
                    </P>
                    <GPH SPAN="3" DEEP="239">
                        <GID>EP13MY19.016</GID>
                    </GPH>
                    <P>Below we compile and summarize the information that supports our determination that the Navy's activities would not adversely affect any species or stocks through effects on annual rates of recruitment or survival for any of the affected species or stocks addressed in this section.</P>
                    <HD SOURCE="HD3">Beaked Whales, Including Northern Bottlenose Whale (Western North Atlantic Stocks)</HD>
                    <P>
                        These stocks span the deeper waters of the East Coast of the U.S. north to Canada and out into oceanic waters beyond the U.S. EEZ. There is no currently reported trend for these populations and there are no specific issues with the status of the stocks that cause particular concern. Neither mortality nor tissue damage from explosives is anticipated or proposed for authorization for these stocks. Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances of harassment compared to the abundance within the U.S. EEZ and both in and outside of the U.S. EEZ is 1,567-1,836 percent and 148-297 percent, respectively (Table 22). This information, combined with the known 
                        <PRTPAGE P="21180"/>
                        range of the stocks, suggests that while not all of the individuals in these stocks would most likely be taken (because they span well into oceanic waters), of those that are, most would be taken over a few days (though likely not sequential) and some subset that spends extended time within the U.S. EEZ would likely be taken over a larger amount of days (maybe 15-37), some of which could be sequential. Regarding the severity of those individual takes by behavioral Level B harassment, as explained in the 2018 AFTT final rule, the duration of any exposure response is expected to generally be between minutes and hours and largely between 148 and 160 dB, though with beaked whales, which are considered somewhat more sensitive, this could mean that some individuals will leave preferred habitat for a day or two. However, while interrupted feeding bouts are a known response and concern for odontocetes, we also know that there are often viable alternative habitat options in the relative vicinity in the Western North Atlantic.
                    </P>
                    <P>Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level, of short duration, and not in a frequency band that would adversely affect communication, inhibit echolocation, or otherwise interfere with other low-frequency cues. Therefore any associated lost opportunities and capabilities would not impact reproduction or survival. For the same reasons (low level and frequency band) the one to three estimated Level A harassment takes by PTS for these stocks are unlikely to have any effect on the reproduction or survival of any individual, even if PTS were to be experienced by an individual that also experiences one or more Level B harassment takes. </P>
                    <P>Altogether, a small portion of the stock would likely be taken (at a relatively moderate level) on a relatively moderate to high number of days across the year, some of which could be sequential. Though the majority of impacts are expected to be of a sometimes low, but more likely, moderate magnitude and severity, the sensitivity of beaked whales and larger number of takes makes it more likely (probabilistically) that a small number of individuals could be interrupted during foraging in a manner and amount such that impacts to the energy budgets of females (from either losing feeding opportunities or expending considerable energy to find alternative feeding options) could cause them to forego reproduction for a year (energetic impacts to males generally have limited impact on population rates unless they cause death, and it takes extreme energy deficits beyond what would ever be likely to result from these activities to cause the death of an adult marine mammal). As noted previously, however, foregone reproduction (especially for one year) has far less of an impact on population rates than mortality and a small number of instances would not be expected to adversely impact annual rates of recruitment or survival. Based on the abundance of these stocks in the area and the evidence of little, if any, known human-caused mortality, all indications are that the small number of times in which reproduction would be likely to be foregone would not affect the stocks' annual rates of recruitment or survival. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on the Western North Atlantic stocks of beaked whales. </P>
                    <HD SOURCE="HD3">Beaked Whales (Gulf of Mexico Stocks)</HD>
                    <P>The animals in these stocks suffer from lingering health issues resulting from the DWH oil spill (four percent of individuals of these stocks have adverse health effects), which means that some of them could be more susceptible to exposure to other stressors, and negative population effects (10 years for their growth rate to recover to the rate predicted for the stocks if they had not incurred spill impacts). Neither mortality nor tissue damage from explosives is anticipated or proposed for authorization for these stocks. Level A harassment take from PTS is also unlikely to occur. Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances of harassment compared to the abundance is 148-155 percent (Table 22). This information indicates that either the individuals in these stocks would all be taken by harassment one or two days within a year, or that a subset would not be taken at all and a small subset may be taken several times. Regarding the severity of those individual takes, as explained in the 2018 AFTT final rule, the duration of any exposure response is expected to generally be between minutes and hours and largely between 148 and 160 dB, though with beaked whales, which are considered somewhat more sensitive, this could mean that some individuals will leave preferred habitat for a day or two. However, while interrupted feeding bouts are a known response and concern for odontocetes, we also know that there are often viable alternative habitat options in the relative vicinity in the Gulf of Mexico. Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level, of short duration, and not in a frequency band that would adversely affect communication, inhibit echolocation, or otherwise interfere with other low frequency cues. Therefore any associated lost opportunities and capabilities would not impact reproduction or survival.</P>
                    <P>Altogether, likely only a portion of these stocks would be impacted and any individual beaked whale likely would be disturbed at a moderate level for no more than a few days per year. Even given the fact that some of the affected individuals may have compromised health, there is nothing to suggest that this magnitude and severity of effects would result in impacts on annual rates of recruitment or survival for any of the stocks. For these reasons, we have preliminarily determined, in consideration of all of the effects of the Navy's activities combined, that the proposed authorized take would have a negligible impact on the Gulf of Mexico stocks of beaked whales included in Table 22.</P>
                    <HD SOURCE="HD2">Pinnipeds</HD>
                    <P>
                        In Table 23 below for pinnipeds, we indicate the total annual mortality, Level A and Level B harassment, and a number indicating the instances of total take as a percentage of abundance. Table 23 is unchanged from Table 77 in the 2018 AFTT final rule. For additional information and analysis supporting the negligible-impact analysis, see the 
                        <E T="03">Pinnipeds</E>
                         discussion in the 
                        <E T="03">Group and Species-Specific Analyses</E>
                         section of the 2018 AFTT final rule, all of which remains applicable to this proposed rule unless specifically noted.
                    </P>
                    <GPH SPAN="3" DEEP="253">
                        <PRTPAGE P="21181"/>
                        <GID>EP13MY19.017</GID>
                    </GPH>
                    <P>Below we compile and summarize the information that supports our determination that the Navy's activities would not adversely affect any pinnipeds through effects on annual rates of recruitment or survival for any of the affected species or stocks addressed in this section.</P>
                    <P>
                        The Western North Atlantic pinniped (harp seal, harbor seal, hooded seal, and gray seal) stocks are northern, but highly migratory species. While harp seals are limited to the northern portion of the U.S. EEZ, gray and harbor seals may be found as far south as the Chesapeake Bay in late fall and hooded seals migrate as far south as Puerto Rico. A UME has been designated for seals from Maine to Virginia and the main pathogen found in the seals that have been tested is phocine distemper virus. Neither mortality nor tissue damage from explosives is anticipated or proposed for authorization for any of these stocks. Regarding the magnitude of Level B harassment takes (TTS and behavioral disruption), the number of estimated instances of harassment compared to the abundance that is expected within the AFTT Study Area is 34-225 percent, which suggests that only a subset of the animals in the AFTT Study Area would be taken, but that a few might be taken on several days within the year (1-5 days), but not likely on sequential days. When the fact that some of these seals are residing in areas near Navy activities is considered, we can estimate that perhaps some of those individuals might be taken some higher number of days within the year (up to approximately 10 days), but still with no reason to think that these takes would occur on sequential days, which means that we would not expect effects on reproduction or survival. Regarding the severity of those individual behavioral Level B harassment takes, as explained in the 2018 AFTT final rule, the duration of any exposure response is expected to be between minutes and hours (
                        <E T="03">i.e.,</E>
                         relatively short) and the received sound levels are largely below 172 dB, with some up to 178 dB (
                        <E T="03">i.e.,</E>
                         of a lower to moderate level, less likely to evoke a severe response) and therefore there is no indication that the expected takes by behavioral Level B harassment would have any effect on annual rates of recruitment or survival. 
                    </P>
                    <P>Regarding the severity of TTS takes, as explained in the 2018 AFTT final rule, they are expected to be low-level, of short duration, and not in a frequency band that would adversely affect communication or otherwise interfere with other low-frequency cues. Therefore any associated lost opportunities and capabilities would not impact reproduction or survival. For the same reasons (low level and frequency band) the two to four estimated Level A harassment takes by PTS for these stocks are unlikely to have any effect on the reproduction or survival of any individual, even if PTS were to be experienced by an animal that also experiences one or more Level B harassment takes. </P>
                    <P>
                        Even given the fact that some of the affected harbor seal individuals may have compromised health due to the UME, there is nothing to suggest that such a low magnitude and severity of effects would result in impacts on annual rates of recruitment or survival, especially given that the stock abundance in the SAR is 75,839 with a residual PBR of 1,651. Similarly, given the low magnitude and severity of effects, there is no indication that these activities would affect reproduction or survival of harp or hooded seals, much less adversely affect rates of recruitment or survival, especially given that harp seal abundance is estimated at 6.9 million and hooded seal residual PBR is 13,950. Gray seals are experiencing a UME as well as an exceedance of more than 4,299 M/SI above PBR. The NMFS SAR notes that the U.S. portion of average annual human-caused M/SI in U.S. waters does not exceed the portion of PBR in U.S. waters, and that while the status of the gray seal population relative to OSP in U.S. Atlantic EEZ waters is unknown the stock abundance appears to be increasing in U.S. and Canadian waters (Hayes 
                        <E T="03">et al.,</E>
                         2018). Also, given the low magnitude (take compared to abundance is 95 percent, meaning the subset of individuals taken may be taken a few times on non-sequential days) and low to occasionally moderate severity of impacts, no impacts to individual reproduction or survival are expected and therefore no effects on annual rates of recruitment or survival would occur. For these reasons, in consideration of all of the effects of the Navy's activities combined, we have preliminarily determined that the proposed authorized take would have a 
                        <PRTPAGE P="21182"/>
                        negligible impact on the Western North Atlantic stocks of gray seals, harbor seals, hooded seals, and harp seals.
                    </P>
                    <HD SOURCE="HD2">Determination</HD>
                    <P>The 2018 AFTT final rule included a detailed discussion of all of the anticipated impacts on the affected species and stocks from serious injury and mortality, Level A harassment, and Level B harassment; impacts on habitat; and how the Navy's mitigation and monitoring measures reduced the number and/or severity of adverse effects. We evaluated how these impacts and mitigation measures are expected to combine, annually, to affect individuals of each stock. Those effects were then evaluated in the context of whether they are reasonably likely to impact reproductive success or survivorship of individuals and then, if so, further analyzed to determine whether there would be effects on annual rates of recruitment or survival that would adversely affect the species or stock.</P>
                    <P>As described above, the basis for the negligible impact determination is the assessment of effects on annual rates of recruitment and survival. Accordingly, the analysis included in the 2018 AFTT final rule used annual activity levels, the best available science, and approved methods to predict the annual impacts to marine mammals, which were then analyzed in the context of whether each species or stock would incur more than a negligible impact based on anticipated adverse impacts to annual rates of recruitment or survival. As we have described above, none of the factors upon which the annually-based conclusions in the 2018 AFTT final rule were based have changed in a manner that would change our determinations. Therefore, even though this proposed rule includes two additional years, because our findings are based on annual rates of recruitment and survival, and nothing has changed in a manner that would change our 2018 AFTT rule annual analyses, it is appropriate to rely on those analyses, as well as the information and analysis discussed above, for this proposed rule.</P>
                    <P>Based on the applicable information and analysis from the 2018 AFTT final rule as updated with the information and analysis contained herein on the potential and likely effects of the specified activities on the affected marine mammals and their habitat, and taking into consideration the implementation of the monitoring and mitigation measures, NMFS preliminarily finds that the incidental take from the specified activities will have a negligible impact on all affected marine mammal species and stocks.</P>
                    <HD SOURCE="HD1">Subsistence Harvest of Marine Mammals</HD>
                    <P>There are no subsistence uses or harvest of marine mammals in the geographic area affected by the specified activities. Therefore, NMFS has determined that the total taking affecting species or stocks would not have an unmitigable adverse impact on the availability of such species or stocks for taking for subsistence purposes.</P>
                    <HD SOURCE="HD1">ESA</HD>
                    <P>
                        There are six marine mammal species under NMFS jurisdiction that are listed as endangered or threatened under the ESA with confirmed or possible occurrence in the AFTT Study Area: Blue whale (Western North Atlantic stock), fin whale (Western North Atlantic stock), sei whale (Nova Scotia stock), sperm whale (Gulf of Mexico Oceanic stock and North Atlantic stock), North Atlantic right whale (Western North Atlantic stock), and Bryde's whale (Northern Gulf of Mexico stock). The Navy consulted with NMFS pursuant to section 7 of the ESA for AFTT activities. NMFS also consulted internally on the issuance of the 2018 AFTT regulations and LOAs under section 101(a)(5)(A) of the MMPA. NMFS issued a Biological and Conference Opinion on October 22, 2018 concluding that the issuance of the 2018 AFTT final rule and subsequent LOAs are not likely to jeopardize the continued existence of the threatened and endangered species under NMFS’ jurisdiction and are not likely to result in the destruction or adverse modification of critical habitat in the AFTT Study Area. The Biological and Conference Opinion for this action is available at 
                        <E T="03">https://www.fisheries.noaa.gov/national/marine-mammal-protection/incidental-take-authorizations-military-readiness-activities.</E>
                         NMFS’ Permits and Conservation Division is currently discussing the 2019 Navy application with NMFS’ ESA Interagency Cooperation Division.
                    </P>
                    <HD SOURCE="HD1">National Marine Sanctuaries Act</HD>
                    <P>Federal agency actions that are likely to injure national marine sanctuary resources are subject to consultation with the Office of National Marine Sanctuaries (ONMS) under section 304(d) of the National Marine Sanctuaries Act (NMSA).</P>
                    <P>On December 15, 2017, the Navy initiated consultation with ONMS and submitted a Sanctuary Resource Statement (SRS) that discussed the effects of the Navy's AFTT activities in the vicinity of Stellwagen Bank, Gray's Reef, and Florida Keys National Marine Sanctuaries on sanctuary resources. NMFS worked with the Navy in the development of the SRS to ensure that it could serve jointly as an SRS for NMFS’ action under the MMPA as well.</P>
                    <P>On December 20, 2017, NMFS initiated consultation with ONMS on MMPA incidental take regulations for the Navy's AFTT activities. NMFS requested that ONMS consider the description and assessment of the effects of the Navy's activities, which included an assessment of the effects on marine mammals, included in the joint SRS submitted by the Navy as satisfying NMFS’ need to provide an SRS.</P>
                    <P>ONMS reviewed the SRS, as well as an addendum the Navy provided on April 3, 2018. On April 12, 2018, ONMS found the SRS addendum sufficient for the purposes of making an injury determination to develop recommended alternatives as required by the NMSA. On May 15, 2018, ONMS recommended two reasonable and prudent measures to Navy and NMFS (one of which applied to NMFS) to minimize injury and to protect sanctuary resources. ONMS subsequently provided a slight modification of those recommendations to the Navy and NMFS on August 1, 2018. On August 17, 2018, the Navy agreed to implement both ONMS recommendations and on October 30, 2018, NMFS agreed to implement the recommendation that applied to NMFS. NMFS' Permits and Conservation Division is currently discussing the 2019 Navy application with ONMS.</P>
                    <HD SOURCE="HD1">NEPA</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 evaluate our proposed actions and alternatives with respect to potential impacts on the human environment. NMFS participated as a cooperating agency on the 2018 AFTT FEIS/OEIS (published on September 14, 2018, 
                        <E T="03">http://www.aftteis.com</E>
                        ) which evaluated impacts from Navy training and testing activities in the AFTT Study Area for the reasonably foreseeable future. In accordance with 40 CFR 1506.3, NMFS independently reviewed and evaluated the 2018 AFTT FEIS/OEIS and determined that it was adequate and sufficient to meet our responsibilities under NEPA for the issuance of the 2018 AFTT final rule and associated LOAs. NOAA therefore adopted the 2018 AFTT FEIS/OEIS. In accordance with 40 CFR 1502.9 and the information and analysis contained in this proposed rule, the Navy and NMFS as a 
                        <PRTPAGE P="21183"/>
                        cooperating agency have made a preliminary determination that this proposed rule and any subsequent LOAs would not result in impacts that were not fully considered in the 2018 AFTT FEIS/OEIS. As indicated in this proposed rule, the Navy has made no substantial changes to the proposed action nor are there significant new circumstances or information relevant to environmental concerns or its impacts. NMFS will make a final NEPA determination prior to a decision whether to issue a final rule.
                    </P>
                    <HD SOURCE="HD1">Classification</HD>
                    <P>The Office of Management and Budget has determined that this proposed rule is not significant for purposes of Executive Order 12866.</P>
                    <P>Pursuant to the Regulatory Flexibility Act (RFA), the Chief Counsel for Regulation of the Department of Commerce has certified to the Chief Counsel for Advocacy of the Small Business Administration that this proposed rule, if adopted, would not have a significant economic impact on a substantial number of small entities. The RFA requires Federal agencies to prepare an analysis of a rule's impact on small entities whenever the agency is required to publish a notice of proposed rulemaking. However, a Federal agency may certify, pursuant to 5 U.S.C. 605(b), that the action will not have a significant economic impact on a substantial number of small entities. The Navy is the sole entity that would be affected by this rulemaking, and the Navy is not a small governmental jurisdiction, small organization, or small business, as defined by the RFA. Any requirements imposed by an LOA issued pursuant to these regulations, and any monitoring or reporting requirements imposed by these regulations, would be applicable only to the Navy. NMFS does not expect the issuance of these regulations or the associated LOAs to result in any impacts to small entities pursuant to the RFA. Because this action, if adopted, would directly affect the Navy and not a small entity, NMFS concludes the action would not result in a significant economic impact on a substantial number of small entities.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 50 CFR Part 218</HD>
                        <P>Exports, Fish, Imports, Incidental take, Indians, Labeling, Marine mammals, Navy, Penalties, Reporting and recordkeeping requirements, Seafood, Sonar, Transportation.</P>
                    </LSTSUB>
                    <SIG>
                        <DATED>Dated: May 6, 2019.</DATED>
                        <NAME>Samuel D. Rauch III,</NAME>
                        <TITLE>Deputy Assistant Administrator for Regulatory Programs, National Marine Fisheries Service.</TITLE>
                    </SIG>
                    <P>For reasons set forth in the preamble, 50 CFR part 218 is proposed to be amended as follows:</P>
                    <PART>
                        <HD SOURCE="HED">PART 218—REGULATIONS GOVERNING THE TAKING AND IMPORTING OF MARINE MAMMALS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 218 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED"> Authority:</HD>
                        <P>
                             16 U.S.C. 1361 
                            <E T="03">et seq.,</E>
                             unless otherwise noted.
                        </P>
                    </AUTH>
                    <AMDPAR>2. Revise subpart I of part 218 to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Subpart I—Taking and Importing Marine Mammals; U.S. Navy's Atlantic Fleet Training and Testing (AFTT)</HD>
                    <CONTENTS>
                        <SECHD>Sec.</SECHD>
                        <SECTNO>218.80 </SECTNO>
                        <SUBJECT>Specified activity and specified geographical region.</SUBJECT>
                        <SECTNO>218.81 </SECTNO>
                        <SUBJECT>Effective dates.</SUBJECT>
                        <SECTNO>218.82 </SECTNO>
                        <SUBJECT>Permissible methods of taking.</SUBJECT>
                        <SECTNO>218.83 </SECTNO>
                        <SUBJECT>Prohibitions.</SUBJECT>
                        <SECTNO>218.84 </SECTNO>
                        <SUBJECT>Mitigation requirements.</SUBJECT>
                        <SECTNO>218.85 </SECTNO>
                        <SUBJECT>Requirements for monitoring and reporting.</SUBJECT>
                        <SECTNO>218.86 </SECTNO>
                        <SUBJECT>Letters of Authorization.</SUBJECT>
                        <SECTNO>218.87 </SECTNO>
                        <SUBJECT>Renewals and modifications of Letters of Authorization.</SUBJECT>
                        <SECTNO>218.88-218.89 </SECTNO>
                        <SUBJECT>[Reserved]</SUBJECT>
                    </CONTENTS>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart I—Taking and Importing Marine Mammals; U.S. Navy's Atlantic Fleet Training and Testing (AFTT)</HD>
                        <SECTION>
                            <SECTNO>§ 218.80 </SECTNO>
                            <SUBJECT> Specified activity and geographical region.</SUBJECT>
                            <P>(a) Regulations in this subpart apply only to the U.S. Navy for the taking of marine mammals that occurs in the area described in paragraph (b) of this section and that occurs incidental to the activities listed in paragraph (c) of this section.</P>
                            <P>(b) The taking of marine mammals by the Navy under this subpart may be authorized in Letters of Authorization (LOAs) only if it occurs within the Atlantic Fleet Training and Testing (AFTT) Study Area, which includes areas of the western Atlantic Ocean along the East Coast of North America, portions of the Caribbean Sea, and the Gulf of Mexico. The AFTT Study Area begins at the mean high tide line along the U.S. East Coast and extends east to the 45-degree west longitude line, north to the 65-degree north latitude line, and south to approximately the 20-degree north latitude line. The AFTT Study Area also includes Navy pierside locations, bays, harbors, and inland waterways, and civilian ports where training and testing occurs.</P>
                            <P>(c) The taking of marine mammals by the Navy is only authorized if it occurs incidental to the Navy conducting training and testing activities, including:</P>
                            <P>
                                (1) 
                                <E T="03">Training.</E>
                                 (i) Amphibious warfare;
                            </P>
                            <P>(ii) Anti-submarine warfare;</P>
                            <P>(iii) Electronic warfare;</P>
                            <P>(iv) Expeditionary warfare;</P>
                            <P>(v) Mine warfare;</P>
                            <P>(vi) Surface warfare, and</P>
                            <P>(vii) Pile driving.</P>
                            <P>
                                (2) 
                                <E T="03">Testing.</E>
                                 (i) Naval Air Systems Command Testing Activities;
                            </P>
                            <P>(ii) Naval Sea System Command Testing Activities; and</P>
                            <P>(iii) Office of Naval Research Testing Activities.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 218.81 </SECTNO>
                            <SUBJECT> Effective dates.</SUBJECT>
                            <P>
                                Regulations in this subpart are effective from [DATE OF PUBLICATION OF FINAL RULE IN THE 
                                <E T="04">Federal Register</E>
                                ] through November 13, 2025.
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 218.82 </SECTNO>
                            <SUBJECT> Permissible methods of taking.</SUBJECT>
                            <P>(a) Under LOAs issued pursuant to §§ 216.106 of this chapter and 218.86, the Holder of the LOAs (hereinafter “Navy”) may incidentally, but not intentionally, take marine mammals within the area described in § 218.80(b) by Level A harassment and Level B harassment associated with the use of active sonar and other acoustic sources and explosives as well as serious injury or mortality associated with ship shock trials and vessel strikes, provided the activity is in compliance with all terms, conditions, and requirements of these regulations in this subpart and the applicable LOAs.</P>
                            <P>(b) The incidental take of marine mammals by the activities listed in § 218.80(c) is limited to the following species:</P>
                            <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s100,r100">
                                <TTITLE>Table 1 to § 218.82</TTITLE>
                                <BOXHD>
                                    <CHED H="1">Species</CHED>
                                    <CHED H="1">Stock</CHED>
                                </BOXHD>
                                <ROW RUL="s" EXPSTB="01">
                                    <ENT I="21">
                                        <E T="02">Suborder Mysticeti (baleen whales)</E>
                                    </ENT>
                                </ROW>
                                <ROW EXPSTB="00">
                                    <ENT I="22">
                                        <E T="03">Family Balaenidae (right whales):</E>
                                    </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">North Atlantic right whale *</ENT>
                                    <ENT>Western.</ENT>
                                </ROW>
                                <ROW>
                                    <PRTPAGE P="21184"/>
                                    <ENT I="22">
                                        <E T="03">Family Balaenopteridae (roquals):</E>
                                    </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Blue whale *</ENT>
                                    <ENT>Western North Atlantic (Gulf of St. Lawrence).</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Bryde's whale *</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>NSD.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Minke whale</ENT>
                                    <ENT>Canadian East Coast.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Fin whale *</ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Humpback whale</ENT>
                                    <ENT>Gulf of Maine.</ENT>
                                </ROW>
                                <ROW RUL="s">
                                    <ENT I="03">Sei whale *</ENT>
                                    <ENT>Nova Scotia.</ENT>
                                </ROW>
                                <ROW RUL="s" EXPSTB="01">
                                    <ENT I="21">
                                        <E T="02">Suborder Odontoceti (toothed whales)</E>
                                        .
                                    </ENT>
                                </ROW>
                                <ROW EXPSTB="00">
                                    <ENT I="22">
                                        <E T="03">Family Physeteridae (sperm whale):</E>
                                    </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Sperm whale *</ENT>
                                    <ENT>Gulf of Mexico Oceanic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22">
                                        <E T="03">Family Kogiidae (sperm whales):</E>
                                    </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Dwarf sperm whale.</ENT>
                                    <ENT>Gulf of Mexico Oceanic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Pygmy sperm whale</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22">
                                        <E T="03">Family Ziphiidae (beaked whales):</E>
                                    </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Blainville's beaked whale</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Cuvier's beaked whale</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Gervais' beaked whale</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Northern bottlenose whale</ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Sowersby's beaked whale</ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">True's beaked whale</ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22">
                                        <E T="03">Family Delphinidae (dolphins)</E>
                                    </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Atlantic spotted dolphin</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Atlantic white-sided dolphin</ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Bottlenose dolphin</ENT>
                                    <ENT>Choctawhatchee Bay.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Gulf of Mexico Eastern Coastal.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Gulf of Mexico Northern Coastal.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Gulf of Mexico Western Coastal.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Indian River Lagoon Estuarine System.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Jacksonville Estuarine System.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Mississippi Sound, Lake Borgne, Bay Boudreau.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Northern Gulf of Mexico Continental Shelf.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Northern Gulf of Mexico Oceanic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Northern North Carolina Estuarine System.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Southern North Carolina Estuarine System.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic Northern Florida Coastal.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic Central Florida Coastal.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic Northern Migratory Coastal.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic Offshore.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic South Carolina/Georgia Coastal.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic Southern Migratory Coastal.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Clymene dolphin</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">False killer whale</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Fraser's dolphin</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Killer whale</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Long-finned pilot whale</ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Melon-headed whale</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Pantropical spotted dolphin</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Pygmy killer whale</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Risso's dolphin</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Rough-toothed dolphin</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Short-beaked common dolphin</ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Short-finned pilot whale</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <PRTPAGE P="21185"/>
                                    <ENT I="03">Spinner dolphin</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Striped dolphin</ENT>
                                    <ENT>Northern Gulf of Mexico.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">White-beaked dolphin</ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22">
                                        <E T="03">Family Phocoenidae (porpoises):</E>
                                    </ENT>
                                </ROW>
                                <ROW RUL="s">
                                    <ENT I="03">Harbor porpoise</ENT>
                                    <ENT>Gulf of Maine/Bay of Fundy.</ENT>
                                </ROW>
                                <ROW RUL="s" EXPSTB="01">
                                    <ENT I="21">
                                        <E T="02">Suborder Pinnipedia</E>
                                    </ENT>
                                </ROW>
                                <ROW EXPSTB="00">
                                    <ENT I="22">
                                        <E T="03">Family Phocidae (true seals):</E>
                                    </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Gray seal</ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Harbor seal</ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Harp seal</ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">Hooded seal</ENT>
                                    <ENT>Western North Atlantic.</ENT>
                                </ROW>
                            </GPOTABLE>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 218.83 </SECTNO>
                            <SUBJECT> Prohibitions.</SUBJECT>
                            <P>Notwithstanding incidental takings contemplated in § 218.82(a) and authorized by LOAs issued under §§ 216.106 of this chapter and 218.86, no person in connection with the activities listed in § 218.80(c) may:</P>
                            <P>(a) Violate, or fail to comply with the terms, conditions, and requirements of this subpart or an LOA issued under § 216.106 of this chapter and § 218.86;</P>
                            <P>(b) Take any marine mammal not specified in § 218.82(b);</P>
                            <P>(c) Take any marine mammal specified § 218.82(b) in any manner other than as specified in the LOAs; or</P>
                            <P>(d) Take a marine mammal specified § 218.82(b) if NMFS determines such taking results in more than a negligible impact on the species or stocks of such marine mammal.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 218.84 </SECTNO>
                            <SUBJECT> Mitigation requirements.</SUBJECT>
                            <P>When conducting the activities identified in § 218.80(c), the mitigation measures contained in any LOAs issued under §§ 216.106 of this chapter and 218.86 must be implemented. These mitigation measures include, but are not limited to:</P>
                            <P>
                                (a) 
                                <E T="03">Procedural mitigation.</E>
                                 Procedural mitigation is mitigation that the Navy must implement whenever and wherever an applicable training or testing activity takes place within the AFTT Study Area for each applicable activity category or stressor category and includes acoustic stressors (
                                <E T="03">i.e.,</E>
                                 active sonar, air guns, pile driving, weapons firing noise), explosive stressors (
                                <E T="03">i.e.,</E>
                                 sonobuoys, torpedoes, medium-caliber and large-caliber projectiles, missiles and rockets, bombs, sinking exercises, mines, anti-swimmer grenades, line charge testing and ship shock trials), and physical disturbance and strike stressors (
                                <E T="03">i.e.,</E>
                                 vessel movement; towed in-water devices; small-, medium-, and large-caliber non-explosive practice munitions; non-explosive missiles and rockets; non-explosive bombs and mine shapes).
                            </P>
                            <P>
                                (1) 
                                <E T="03">Environmental awareness and education.</E>
                                 Appropriate personnel (including civilian personnel) involved in mitigation and training or testing activity reporting under the specified activities must complete one or more modules of the U.S. Navy Afloat Environmental Compliance Training Series, as identified in their career path training plan. Modules include: Introduction to the U.S. Navy Afloat Environmental Compliance Training Series, Marine Species Awareness Training, U.S. Navy Protective Measures Assessment Protocol, and U.S. Navy Sonar Positional Reporting System and Marine Mammal Incident Reporting.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Active sonar.</E>
                                 Active sonar includes low-frequency active sonar, mid-frequency active sonar, and high-frequency active sonar. For vessel-based active sonar activities, mitigation applies only to sources that are positively controlled and deployed from manned surface vessels (
                                <E T="03">e.g.,</E>
                                 sonar sources towed from manned surface platforms). For aircraft-based active sonar activities, mitigation applies only to sources that are positively controlled and deployed from manned aircraft that do not operate at high altitudes (
                                <E T="03">e.g.,</E>
                                 rotary-wing aircraft). Mitigation does not apply to active sonar sources deployed from unmanned aircraft or aircraft operating at high altitudes (
                                <E T="03">e.g.,</E>
                                 maritime patrol aircraft).
                            </P>
                            <P>
                                (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 (A) 
                                <E T="03">Hull-mounted sources.</E>
                                 One Lookout for platforms with space or manning restrictions while underway (at the forward part of a small boat or ship) and platforms using active sonar while moored or at anchor (including pierside); two Lookouts for platforms without space or manning restrictions while underway (at the forward part of the ship); and four Lookouts for pierside sonar testing activities at Port Canaveral, Florida and Kings Bay, Georgia.
                            </P>
                            <P>
                                (B) 
                                <E T="03">Sources that are not hull-mounted sources.</E>
                                 One Lookout on the ship or aircraft conducting the activity.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zones and requirements.</E>
                                 During the activity, at 1,000 yard (yd) Navy personnel must power down 6 decibels (dB), at 500 yd Navy personnel must power down an additional 4 dB (for a total of 10 dB), and at 200 yd Navy personnel must shut down for low-frequency active sonar ≥200 dB and hull-mounted mid-frequency active sonar; or at 200 yd Navy personnel must shut down for low-frequency active sonar &lt;200 dB, mid-frequency active sonar sources that are not hull-mounted, and high-frequency active sonar.
                            </P>
                            <P>
                                (A) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 when maneuvering on station), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must relocate or delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must relocate or delay the start of active sonar transmission.
                            </P>
                            <P>
                                (B) During low-frequency active sonar at or above 200 dB and hull-mounted mid-frequency active sonar, Navy personnel must observe the mitigation zone for marine mammals and power down active sonar transmission by 6 dB if marine mammals are observed within 1,000 yd of the sonar source; power down by an additional 4 dB (10 dB total) if marine mammals are observed within 500 yd of the sonar source; and cease transmission if marine mammals are observed within 200 yd of the sonar source.
                                <PRTPAGE P="21186"/>
                            </P>
                            <P>(C) During low-frequency active sonar below 200 dB, mid-frequency active sonar sources that are not hull mounted, and high-frequency active sonar, Navy personnel must observe the mitigation zone for marine mammals and cease active sonar transmission if marine mammals are observed within 200 yd of the sonar source.</P>
                            <P>(D) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing or powering up active sonar transmission) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the sonar source; the mitigation zone has been clear from any additional sightings for 10 minutes (min) for aircraft-deployed sonar sources or 30 min for vessel-deployed sonar sources; for mobile activities, the active sonar source has transited a distance equal to double that of the mitigation zone size beyond the location of the last sighting; or for activities using hull-mounted sonar where a dolphin(s) is observed in the mitigation zone, the Lookout concludes that the dolphin(s) is deliberately closing in on the ship to ride the ship's bow wave, and is therefore out of the main transmission axis of the sonar (and there are no other marine mammal sightings within the mitigation zone).</P>
                            <P>
                                (3) 
                                <E T="03">Air guns.</E>
                                 (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be positioned on a ship or pierside.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 150 yd around the air gun.
                            </P>
                            <P>
                                (A) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 when maneuvering on station), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must relocate or delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must relocate or delay the start of air gun use.
                            </P>
                            <P>(B) During the activity, Navy personnel must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must cease use of air guns.</P>
                            <P>(C) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing air gun use) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the air gun; the mitigation zone has been clear from any additional sightings for 30 min; or for mobile activities, the air gun has transited a distance equal to double that of the mitigation zone size beyond the location of the last sighting.</P>
                            <P>
                                (4) 
                                <E T="03">Pile driving.</E>
                                 Pile driving and pile extraction sound during Elevated Causeway System training.
                            </P>
                            <P>
                                (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be positioned on the shore, the elevated causeway, or a small boat.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 100 yd around the pile driver.
                            </P>
                            <P>(A) Prior to the initial start of the activity (for 30 min), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must delay the start of pile driving or vibratory pile extraction.</P>
                            <P>(B) During the activity, Navy personnel must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must cease impact pile driving or vibratory pile extraction.</P>
                            <P>(C) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing pile driving or pile extraction) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the pile driving location; or the mitigation zone has been clear from any additional sightings for 30 min.</P>
                            <P>
                                (5) 
                                <E T="03">Weapons firing noise.</E>
                                 Weapons firing noise associated with large-caliber gunnery activities.
                            </P>
                            <P>
                                (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be positioned on the ship conducting the firing. Depending on the activity, the Lookout could be the same as the one provided for under Explosive medium-caliber and large-caliber projectiles or under Small-, medium-, and large-caliber non-explosive practice munitions in paragraph (a)(8)(i) and (a)(19)(i) of this section.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 Thirty degrees on either side of the firing line out to 70 yd from the muzzle of the weapon being fired.
                            </P>
                            <P>(A) Prior to the initial start of the activity, Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must relocate or delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must relocate or delay the start of weapons firing.</P>
                            <P>(B) During the activity, Navy personnel must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must cease weapons firing.</P>
                            <P>(C) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing weapons firing) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the firing ship; the mitigation zone has been clear from any additional sightings for 30 min; or for mobile activities, the firing ship has transited a distance equal to double that of the mitigation zone size beyond the location of the last sighting.</P>
                            <P>
                                (6) 
                                <E T="03">Explosive Sonobuoys.</E>
                                 (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be positioned in an aircraft or on small boat. If additional platforms are participating in the activity, personnel positioned in those assets (
                                <E T="03">e.g.,</E>
                                 safety observers, evaluators) must support observing the mitigation zone for marine mammals and other applicable biological resources while performing their regular duties.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 600 yd around an explosive sonobuoy.
                            </P>
                            <P>
                                (A) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 during deployment of a sonobuoy field, which typically lasts 20-30 min), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must relocate 
                                <PRTPAGE P="21187"/>
                                or delay the start until the mitigation zone is clear. Navy personnel must conduct passive acoustic monitoring for marine mammals and use information from detections to assist visual observations. Navy personnel also must visually observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must relocate or delay the start of sonobuoy or source/receiver pair detonations.
                            </P>
                            <P>(B) During the activity, Navy personnel must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must cease sonobuoy or source/receiver pair detonations.</P>
                            <P>
                                (C) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing detonations) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the sonobuoy; or the mitigation zone has been clear from any additional sightings for 10 min when the activity involves aircraft that have fuel constraints (
                                <E T="03">e.g.,</E>
                                 helicopter), or 30 min when the activity involves aircraft that are not typically fuel constrained.
                            </P>
                            <P>
                                (D) After completion of the activity (
                                <E T="03">e.g.,</E>
                                 prior to maneuvering off station)—when practical (
                                <E T="03">e.g.,</E>
                                 when platforms are not constrained by fuel restrictions or mission-essential follow-on commitments), Navy personnel must observe for marine mammals in the vicinity of where detonations occurred; if any injured or dead marine mammals are observed, Navy personnel must follow established incident reporting procedures. If additional platforms are supporting this activity (
                                <E T="03">e.g.,</E>
                                 providing range clearance), these Navy assets must assist in the visual observation of the area where detonations occurred.
                            </P>
                            <P>
                                (7) 
                                <E T="03">Explosive torpedoes.</E>
                                 (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout positioned in an aircraft. If additional platforms are participating in the activity, Navy personnel positioned in those assets (
                                <E T="03">e.g.,</E>
                                 safety observers, evaluators) must support observing the mitigation zone for marine mammals and other applicable biological resources while performing their regular duties.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 2,100 yd around the intended impact location.
                            </P>
                            <P>
                                (A) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 during deployment of the target), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, relocate or delay the start until the mitigation zone is clear. Navy personnel also must conduct passive acoustic monitoring for marine mammals and use the information from detections to assist visual observations. Navy personnel must visually observe the mitigation zone for marine mammals and jellyfish aggregations; if marine mammals or jellyfish aggregations are observed, Navy personnel must relocate or delay the start of firing.
                            </P>
                            <P>(B) During the activity, Navy personnel must observe for marine mammals and jellyfish aggregations; if marine mammals or jellyfish aggregations are observed, Navy personnel must cease firing.</P>
                            <P>(C) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing firing) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the intended impact location; or the mitigation zone has been clear from any additional sightings for 10 min when the activity involves aircraft that have fuel constraints, or 30 min when the activity involves aircraft that are not typically fuel constrained.</P>
                            <P>
                                (D) After completion of the activity (
                                <E T="03">e.g.,</E>
                                 prior to maneuvering off station)—when practical (
                                <E T="03">e.g.,</E>
                                 when platforms are not constrained by fuel restrictions or mission-essential follow-on commitments), Navy personnel must observe for marine mammals in the vicinity of where detonations occurred; if any injured or dead marine mammals are observed, Navy personnel must follow established incident reporting procedures. If additional platforms are supporting this activity (
                                <E T="03">e.g.,</E>
                                 providing range clearance), these Navy assets must assist in the visual observation of the area where detonations occurred.
                            </P>
                            <P>
                                (8) 
                                <E T="03">Explosive medium-caliber and large-caliber projectiles.</E>
                                 Gunnery activities using explosive medium-caliber and large-caliber projectiles. Mitigation applies to activities using a surface target.
                            </P>
                            <P>
                                (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be on the vessel or aircraft conducting the activity. For activities using explosive large-caliber projectiles, depending on the activity, the Lookout could be the same as the one described in Weapons Firing Noise in paragraph (a)(5)(i) of this section. If additional platforms are participating in the activity, Navy personnel positioned in those assets (
                                <E T="03">e.g.,</E>
                                 safety observers, evaluators) must support observing the mitigation zone for marine mammals and other applicable biological resources while performing their regular duties.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 (A) 200 yd around the intended impact location for air-to-surface activities using explosive medium-caliber projectiles.
                            </P>
                            <P>(B) 600 yd around the intended impact location for surface-to-surface activities using explosive medium-caliber projectiles.</P>
                            <P>(C) 1,000 yd around the intended impact location for surface-to-surface activities using explosive large-caliber projectiles.</P>
                            <P>
                                (D) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 when maneuvering on station), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must relocate or delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must relocate or delay the start of firing.
                            </P>
                            <P>(E) During the activity, Navy personnel must observe for marine mammals; if marine mammals are observed, Navy personnel must cease firing.</P>
                            <P>
                                (F) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing firing) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the intended impact location; the mitigation zone has been clear from any additional sightings for 10 min for aircraft-based firing or 30 min for vessel-based firing; or for activities using mobile targets, the intended impact location has transited a distance equal to double that of the mitigation zone size beyond the location of the last sighting.
                                <PRTPAGE P="21188"/>
                            </P>
                            <P>
                                (G) After completion of the activity (
                                <E T="03">e.g.,</E>
                                 prior to maneuvering off station)—when practical (
                                <E T="03">e.g.,</E>
                                 when platforms are not constrained by fuel restrictions or mission-essential follow-on commitments), Navy personnel must observe for marine mammals in the vicinity of where detonations occurred; if any injured or dead marine mammals are observed, Navy personnel must follow established incident reporting procedures. If additional platforms are supporting this activity (
                                <E T="03">e.g.,</E>
                                 providing range clearance), these Navy assets must assist in the visual observation of the area where detonations occurred.
                            </P>
                            <P>
                                (9) 
                                <E T="03">Explosive missiles and rockets.</E>
                                 Aircraft-deployed explosive missiles and rockets. Mitigation applies to activities using a surface target.
                            </P>
                            <P>
                                (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be positioned in an aircraft. If additional platforms are participating in the activity, Navy personnel positioned in those assets (
                                <E T="03">e.g.,</E>
                                 safety observers, evaluators) must support observing the mitigation zone for marine mammals and other applicable biological resources while performing their regular duties.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 (A) 900 yd around the intended impact location for missiles or rockets with 0.6-20 lb net explosive weight.
                            </P>
                            <P>(B) 2,000 yd around the intended impact location for missiles with 21-500 lb net explosive weight.</P>
                            <P>
                                (C) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 during a fly-over of the mitigation zone), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must relocate or delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must relocate or delay the start of firing.
                            </P>
                            <P>(D) During the activity, Navy personnel must observe for marine mammals; if marine mammals are observed, Navy personnel must cease firing.</P>
                            <P>(E) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing firing) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the intended impact location; or the mitigation zone has been clear from any additional sightings for 10 min when the activity involves aircraft that have fuel constraints, or 30 min when the activity involves aircraft that are not typically fuel constrained.</P>
                            <P>
                                (F) After completion of the activity (
                                <E T="03">e.g.,</E>
                                 prior to maneuvering off station)—when practical (
                                <E T="03">e.g.,</E>
                                 when platforms are not constrained by fuel restrictions or mission-essential follow-on commitments), Navy personnel must observe for marine mammals in the vicinity of where detonations occurred; if any injured or dead marine mammals are observed, Navy personnel must follow established incident reporting procedures. If additional platforms are supporting this activity (
                                <E T="03">e.g.,</E>
                                 providing range clearance), these Navy assets must assist in the visual observation of the area where detonations occurred.
                            </P>
                            <P>
                                (10) 
                                <E T="03">Explosive bombs.</E>
                                 (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be positioned in an aircraft conducting the activity. If additional platforms are participating in the activity, Navy personnel positioned in those assets (
                                <E T="03">e.g.,</E>
                                 safety observers, evaluators) must support observing the mitigation zone for marine mammals and other applicable biological resources while performing their regular duties.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 2,500 yd around the intended target.
                            </P>
                            <P>
                                (A) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 when arriving on station), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must relocate or delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must relocate or delay the start of bomb deployment.
                            </P>
                            <P>
                                (B) During the activity (
                                <E T="03">e.g.,</E>
                                 during target approach), Navy personnel must observe for marine mammals; if marine mammals are observed, Navy personnel must cease bomb deployment.
                            </P>
                            <P>(C) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing bomb deployment) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the intended target; the mitigation zone has been clear from any additional sightings for 10 min; or for activities using mobile targets, the intended target has transited a distance equal to double that of the mitigation zone size beyond the location of the last sighting.</P>
                            <P>
                                (D) After completion of the activity (
                                <E T="03">e.g.,</E>
                                 prior to maneuvering off station)—when practical (
                                <E T="03">e.g.,</E>
                                 when platforms are not constrained by fuel restrictions or mission-essential follow-on commitments), Navy personnel must observe for marine mammals in the vicinity of where detonations occurred; if any injured or dead marine mammals are observed, Navy personnel must follow established incident reporting procedures. If additional platforms are supporting this activity (
                                <E T="03">e.g.,</E>
                                 providing range clearance), these Navy assets must assist in the visual observation of the area where detonations occurred.
                            </P>
                            <P>
                                (11) 
                                <E T="03">Sinking exercises.</E>
                                 (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 Two Lookouts (one must be positioned in an aircraft and one must be positioned on a vessel). If additional platforms are participating in the activity, Navy personnel positioned in those assets (
                                <E T="03">e.g.,</E>
                                 safety observers, evaluators) must support observing the mitigation zone for marine mammals and other applicable biological resources while performing their regular duties.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 2.5 nautical miles (nmi) around the target ship hulk.
                            </P>
                            <P>(A) Prior to the initial start of the activity (90 min prior to the first firing), Navy personnel must conduct aerial observations of the mitigation zone for floating vegetation; if floating vegetation is observed Navy personnel must delay the start until the mitigation zone is clear. Navy personnel also must conduct aerial observations of the mitigation zone for marine mammals and jellyfish aggregations; if marine mammals or jellyfish aggregations are observed, Navy personnel must delay the start of firing.</P>
                            <P>
                                (B) During the activity, Navy personnel must conduct passive acoustic monitoring for marine mammals and use information from detections to assist visual observations. Navy personnel must visually observe the mitigation zone for marine mammals from the vessel; if marine mammals are observed, Navy personnel must cease firing. Immediately after any planned or unplanned breaks in weapons firing of longer than two hours, Navy personnel must observe the mitigation zone for marine mammals from the aircraft and vessel; if marine mammals are observed, 
                                <PRTPAGE P="21189"/>
                                Navy personnel must delay recommencement of firing.
                            </P>
                            <P>(C) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing firing) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the target ship hulk; or the mitigation zone has been clear from any additional sightings for 30 min.</P>
                            <P>
                                (D) After completion of the activity (for two hours after sinking the vessel or until sunset, whichever comes first), Navy personnel must observe for marine mammals in the vicinity of where detonations occurred; if any injured or dead marine mammals are observed, Navy personnel must follow established incident reporting procedures. If additional platforms are supporting this activity (
                                <E T="03">e.g.,</E>
                                 providing range clearance), these Navy assets must assist in the visual observation of the area where detonations occurred.
                            </P>
                            <P>
                                (12) 
                                <E T="03">Explosive mine countermeasure and neutralization activities.</E>
                                 (
                                <E T="03">i</E>
                                ) Number of Lookouts and observation platform. (A) One Lookout must be positioned on a vessel or in an aircraft when implementing the smaller mitigation zone defined at paragraph (a)(12)(ii)(A) of this section (using 0.1-5 lb net explosive weight charges).
                            </P>
                            <P>(B) Two Lookouts (one must be in an aircraft and one must be on a small boat) when implementing the larger mitigation zone defined at paragraph (a)(12)(ii)(B) of this section (using 6-650 lb net explosive weight charges).</P>
                            <P>
                                (C) If additional platforms are participating in the activity, Navy personnel positioned in those assets (
                                <E T="03">e.g.,</E>
                                 safety observers, evaluators) must support observing the mitigation zone for marine mammals and other applicable biological resources while performing their regular duties.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 (A) 600 yd around the detonation site for activities using 0.1-5 lb net explosive weight.
                            </P>
                            <P>(B) 2,100 yd around the detonation site for activities using 6-650 lb net explosive weight (including high explosive target mines).</P>
                            <P>
                                (C) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 when maneuvering on station; typically, 10 min when the activity involves aircraft that have fuel constraints, or 30 min when the activity involves aircraft that are not typically fuel constrained), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must relocate or delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must relocate or delay the start of detonations.
                            </P>
                            <P>(D) During the activity, Navy personnel must observe the mitigation zone for marine mammals; if marine mammals are observed, the Navy must cease detonations.</P>
                            <P>(E) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing detonations) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to detonation site; or the mitigation zone has been clear from any additional sightings for 10 min when the activity involves aircraft that have fuel constraints, or 30 min when the activity involves aircraft that are not typically fuel constrained.</P>
                            <P>
                                (F) After completion of the activity (typically 10 min when the activity involves aircraft that have fuel constraints, or 30 min when the activity involves aircraft that are not typically fuel constrained), Navy personnel must observe for marine mammals in the vicinity of where detonations occurred; if any injured or dead marine mammals are observed, Navy personnel must follow established incident reporting procedures. If additional platforms are supporting this activity (
                                <E T="03">e.g.,</E>
                                 providing range clearance), these Navy assets must assist in the visual observation of the area where detonations occurred.
                            </P>
                            <P>
                                (13) 
                                <E T="03">Explosive mine neutralization activities involving navy divers</E>
                                —(i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 (A) Two Lookouts must be positioned (two small boats with one Lookout each, or one Lookout must be on a small boat and one must be in a rotary-wing aircraft) when implementing the smaller mitigation zone defined at paragraph (a)(13)(ii)(A) of this section.
                            </P>
                            <P>(B) Four Lookouts must be positioned (two small boats with two Lookouts each), and a pilot or member of an aircrew must serve as an additional Lookout if aircraft are used during the activity, when implementing the larger mitigation zone defined at paragraph (a)(13)(ii)(B) of this section.</P>
                            <P>(C) All divers placing the charges on mines must support the Lookouts while performing their regular duties and must report applicable sightings to their supporting small boat or Range Safety Officer.</P>
                            <P>
                                (D) If additional platforms are participating in the activity, Navy personnel positioned in those assets (
                                <E T="03">e.g.,</E>
                                 safety observers, evaluators) must support observing the mitigation zone for marine mammals and other applicable biological resources while performing their regular duties.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 (A) 500 yd around the detonation site during activities under positive control using 0.1-20 lb net explosive weight.
                            </P>
                            <P>(B) 1,000 yd around the detonation site during all activities using time-delay fuses (0.1-20 lb net explosive weight) and during activities under positive control using 21-60 lb net explosive weight charges.</P>
                            <P>
                                (C) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 when maneuvering on station for activities under positive control; 30 min for activities using time-delay firing devices), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must relocate or delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must relocate or delay the start of detonation or fuse initiation.
                            </P>
                            <P>
                                (D) During the activity, Navy personnel must observe for marine mammals; if marine mammals are observed, Navy personnel must cease detonation or fuse initiation. To the maximum extent practicable depending on mission requirements, safety, and environmental conditions, boats must position themselves near the mid-point of the mitigation zone radius (but outside of the detonation plume and human safety zone), must position themselves on opposite sides of the detonation location (when two boats are used), and must travel in a circular pattern around the detonation location with one Lookout observing inward toward the detonation site and the other observing outward toward the perimeter of the mitigation zone. If used, aircraft must travel in a circular pattern around the detonation location to the maximum extent practicable. Navy personnel must not set time-delay firing devices (0.1-20 lb. net explosive weight) to exceed 10 min.
                                <PRTPAGE P="21190"/>
                            </P>
                            <P>(E) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing detonations) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the detonation site; or the mitigation zone has been clear from any additional sightings for 10 min during activities under positive control with aircraft that have fuel constraints, or 30 min during activities under positive control with aircraft that are not typically fuel constrained and during activities using time-delay firing devices.</P>
                            <P>
                                (F) After completion of an activity (for 30 min), Navy personnel must observe for marine mammals in the vicinity of where any detonations have occurred; if any injured or dead marine mammals are observed, Navy personnel must follow established incident reporting procedures. If additional platforms are supporting this activity (
                                <E T="03">e.g.,</E>
                                 providing range clearance), these Navy assets must assist in the visual observation of the area where detonations occurred.
                            </P>
                            <P>
                                (14) 
                                <E T="03">Maritime security operations—anti-swimmer grenades</E>
                                —(i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be positioned on the small boat conducting the activity. If additional platforms are participating in the activity, Navy personnel positioned in those assets (
                                <E T="03">e.g.,</E>
                                 safety observers, evaluators) must support observing the mitigation zone for marine mammals and other applicable biological resources while performing their regular duties.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 200 yd around the intended detonation location.
                            </P>
                            <P>
                                (A) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 when maneuvering on station), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must relocate or delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must relocate or delay the start of detonation.
                            </P>
                            <P>(B) During the activity, Navy personnel must observe for marine mammals; if marine mammals are observed, Navy personnel must cease detonation.</P>
                            <P>(C) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing detonations) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the intended detonation location; the mitigation zone has been clear from any additional sightings for 30 min; or the intended detonation location has transited a distance equal to double that of the mitigation zone size beyond the location of the last sighting.</P>
                            <P>
                                (D) After completion of the activity (
                                <E T="03">e.g.,</E>
                                 prior to maneuvering off station), when practical (
                                <E T="03">e.g.,</E>
                                 when platforms are not constrained by fuel restrictions or mission-essential follow-on commitments), Navy personnel must observe for marine mammals in the vicinity of where detonations occurred; if any injured or dead marine mammals are observed, Navy personnel must follow established incident reporting procedures. If additional platforms are supporting this activity (
                                <E T="03">e.g.,</E>
                                 providing range clearance), these Navy assets must assist in the visual observation of the area where detonations occurred.
                            </P>
                            <P>
                                (15) 
                                <E T="03">Line charge testing</E>
                                —(i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be positioned on a vessel. If additional platforms are participating in the activity, Navy personnel positioned in those assets (
                                <E T="03">e.g.,</E>
                                 safety observers, evaluators) must support observing the mitigation zone for marine mammals and other applicable biological resources while performing their regular duties.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 900 yd around the intended detonation location.
                            </P>
                            <P>
                                (A) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 when maneuvering on station), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must delay the start of detonations.
                            </P>
                            <P>(B) During the activity, Navy personnel must observe for marine mammals; if marine mammals are observed, Navy personnel must cease detonations.</P>
                            <P>(C) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing detonations) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the intended detonation location; or the mitigation zone has been clear from any additional sightings for 30 min.</P>
                            <P>
                                (D) After completion of the activity (
                                <E T="03">e.g.,</E>
                                 prior to maneuvering off station), when practical (
                                <E T="03">e.g.,</E>
                                 when platforms are not constrained by fuel restrictions or mission-essential follow-on commitments), Navy personnel must observe for marine mammals in the vicinity of where detonations occurred; if any injured or dead marine mammals are observed, Navy personnel must follow established incident reporting procedures. If additional platforms are supporting this activity (
                                <E T="03">e.g.,</E>
                                 providing range clearance), these Navy assets must assist in the visual observation of the area where detonations occurred.
                            </P>
                            <P>
                                (16) 
                                <E T="03">Ship shock trials</E>
                                —(i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 (A) A minimum of ten Lookouts or trained marine species observers (or a combination thereof) must be positioned either in an aircraft or on multiple vessels (
                                <E T="03">i.e.,</E>
                                 a Marine Animal Response Team boat and the test ship).
                            </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) If aircraft are used, Lookouts or trained marine species observers must be in an aircraft and on multiple vessels.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) If aircraft are not used, a sufficient number of additional Lookouts or trained marine species observers must be used to provide vessel-based visual observation comparable to that achieved by aerial surveys.
                            </P>
                            <P>
                                (B) If additional platforms are participating in the activity, Navy personnel positioned in those assets (
                                <E T="03">e.g.,</E>
                                 safety observers, evaluators) must support observing the mitigation zone for marine mammals and other applicable biological resources while performing their regular duties.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 3.5 nmi around the ship hull.
                            </P>
                            <P>(A) The Navy must not conduct ship shock trials in the Jacksonville Operating Area during North Atlantic right whale calving season from November 15 through April 15.</P>
                            <P>
                                (B) The Navy must develop detailed ship shock trial monitoring and mitigation plans approximately one-year 
                                <PRTPAGE P="21191"/>
                                prior to an event and must continue to provide these to NMFS for review and approval.
                            </P>
                            <P>(C) Pre-activity planning must include selection of one primary and two secondary areas where marine mammal populations are expected to be the lowest during the event, with the primary and secondary locations located more than 2 nmi from the western boundary of the Gulf Stream for events in the Virginia Capes Range Complex or Jacksonville Range Complex.</P>
                            <P>
                                (D) If it is determined during pre-activity surveys that the primary area is environmentally unsuitable (
                                <E T="03">e.g.,</E>
                                 observations of marine mammals or presence of concentrations of floating vegetation), the shock trial can be moved to a secondary site in accordance with the detailed mitigation and monitoring plan provided to NMFS.
                            </P>
                            <P>(E) Prior to the initial start of the activity at the shock trial location (in intervals of 5 hrs, 3 hrs, 40 min, and immediately before the detonation), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must delay triggering the detonation.</P>
                            <P>(F) During the activity, Navy personnel must observe for marine mammals, large schools of fish, jellyfish aggregations, and flocks of seabirds; if marine mammals, large schools of fish, jellyfish aggregations, and flocks of seabirds are observed, Navy personnel must cease triggering the detonation. After completion of each detonation, Navy personnel must observe the mitigation zone for marine mammals; if any injured or dead marine mammals are observed, Navy personnel must follow established incident reporting procedures and halt any remaining detonations until Navy personnel can consult with NMFS and review or adapt the mitigation, if necessary.</P>
                            <P>(G) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing detonations) until one of the following conditions has been met: the animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the ship hull; or the mitigation zone has been clear from any additional sightings for 30 min.</P>
                            <P>
                                (H) After completion of the activity (during the following two days at a minimum, and up to seven days at a maximum), Navy personnel must observe for marine mammals in the vicinity of where detonations occurred; if any injured or dead marine mammals are observed, Navy personnel must follow established incident reporting procedures. If additional platforms are supporting this activity (
                                <E T="03">e.g.,</E>
                                 providing range clearance), these Navy assets must assist in the visual observation of the area where detonations occurred.
                            </P>
                            <P>
                                (17) 
                                <E T="03">Vessel movement.</E>
                                 The mitigation must not be applied if: The vessel's safety is threatened; the vessel is restricted in its ability to maneuver (
                                <E T="03">e.g.,</E>
                                 during launching and recovery of aircraft or landing craft, during towing activities, when mooring, etc.); or the vessel is operated autonomously.
                            </P>
                            <P>
                                (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be on the vessel that is underway.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 (A) 500 yd around whales.
                            </P>
                            <P>(B) 200 yd around all other marine mammals (except bow-riding dolphins and pinnipeds hauled out on man-made navigational structures, port structures, and vessels).</P>
                            <P>(C) During the activity, when underway, Navy personnel must observe the mitigation zone for marine mammals; if any marine mammals are observed, Navy personnel must maneuver to maintain distance.</P>
                            <P>
                                (D) Additionally, Navy personnel must broadcast awareness notification messages with North Atlantic right whale Dynamic Management Area information (
                                <E T="03">e.g.,</E>
                                 location and dates) to applicable Navy assets operating in the vicinity of the Dynamic Management Area. The information will alert assets to the possible presence of a North Atlantic right whale to maintain safety of navigation and further reduce the potential for a vessel strike. Platforms must use the information to assist their visual observation of applicable mitigation zones during training and testing activities and to aid in the implementation of procedural mitigation, including but not limited to, mitigation for vessel movement. If a marine mammal vessel strike occurs, Navy personnel must follow the established incident reporting procedures.
                            </P>
                            <P>
                                (18) 
                                <E T="03">Towed in-water devices.</E>
                                 Mitigation applies to devices that are towed from a manned surface platform or manned aircraft. The mitigation will not be applied if the safety of the towing platform or in-water device is threatened.
                            </P>
                            <P>
                                (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be positioned on a manned towing platform.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 250 yd around marine mammals. During the activity, when towing an in-water device, Navy personnel must observe for marine mammals; if marine mammals are observed, Navy personnel must maneuver to maintain distance.
                            </P>
                            <P>
                                (19) 
                                <E T="03">Small-, medium-, and large-caliber non-explosive practice munitions.</E>
                                 Mitigation applies to activities using a surface target.
                            </P>
                            <P>
                                (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be positioned on the platform conducting the activity. Depending on the activity, the Lookout could be the same as the one described for Weapons Firing Noise in paragraph (a)(5)(i) of this section.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 200 yd around the intended impact location.
                            </P>
                            <P>
                                (A) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 when maneuvering on station), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must relocate or delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must relocate or delay the start of firing.
                            </P>
                            <P>(B) During the activity, Navy personnel must observe for marine mammals; if marine mammals are observed, Navy personnel must cease firing.</P>
                            <P>
                                (C) Commencement/recommencement conditions after a marine mammal sighting before or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing firing) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the intended impact location; the mitigation zone has been clear from any additional sightings for 10 min for aircraft-based firing or 30 min for vessel-based firing; or for activities using a mobile target, the intended impact location has transited a distance equal to double that of the mitigation zone size beyond the location of the last sighting.
                                <PRTPAGE P="21192"/>
                            </P>
                            <P>
                                (20) 
                                <E T="03">Non-explosive missiles and rockets.</E>
                                 Aircraft-deployed non-explosive missiles and rockets. Mitigation applies to activities using a surface target.
                            </P>
                            <P>
                                (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be positioned in an aircraft.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 900 yd around the intended impact location.
                            </P>
                            <P>
                                (A) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 during a fly-over of the mitigation zone), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must relocate or delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must relocate or delay the start of firing.
                            </P>
                            <P>(B) During the activity, Navy personnel must observe for marine mammals; if marine mammals are observed, Navy personnel must cease firing.</P>
                            <P>(C) Commencement/recommencement conditions after a marine mammal sighting prior to or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing firing) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the intended impact location; or the mitigation zone has been clear from any additional sightings for 10 min when the activity involves aircraft that have fuel constraints, or 30 min when the activity involves aircraft that are not typically fuel constrained.</P>
                            <P>
                                (21) 
                                <E T="03">Non-explosive bombs and mine shapes.</E>
                                 Non-explosive bombs and non-explosive mine shapes during mine laying activities.
                            </P>
                            <P>
                                (i) 
                                <E T="03">Number of Lookouts and observation platform.</E>
                                 One Lookout must be positioned in an aircraft.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Mitigation zone and requirements.</E>
                                 1,000 yd around the intended target.
                            </P>
                            <P>
                                (A) Prior to the initial start of the activity (
                                <E T="03">e.g.,</E>
                                 when arriving on station), Navy personnel must observe the mitigation zone for floating vegetation; if floating vegetation is observed, Navy personnel must relocate or delay the start until the mitigation zone is clear. Navy personnel also must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must relocate or delay the start of bomb deployment or mine laying.
                            </P>
                            <P>
                                (B) During the activity (
                                <E T="03">e.g.,</E>
                                 during approach of the target or intended minefield location), Navy personnel must observe the mitigation zone for marine mammals; if marine mammals are observed, Navy personnel must cease bomb deployment or mine laying.
                            </P>
                            <P>(C) Commencement/recommencement conditions after a marine mammal sighting prior to or during the activity: Navy personnel must allow a sighted marine mammal to leave the mitigation zone prior to the initial start of the activity (by delaying the start) or during the activity (by not recommencing bomb deployment or mine laying) until one of the following conditions has been met: The animal is observed exiting the mitigation zone; the animal is thought to have exited the mitigation zone based on a determination of its course, speed, and movement relative to the intended target or minefield location; the mitigation zone has been clear from any additional sightings for 10 min; or for activities using mobile targets, the intended target has transited a distance equal to double that of the mitigation zone size beyond the location of the last sighting.</P>
                            <P>
                                (b) 
                                <E T="03">Mitigation areas.</E>
                                 In addition to procedural mitigation, the Navy must implement mitigation measures within mitigation areas to avoid potential impacts on marine mammals.
                            </P>
                            <P>
                                (1) 
                                <E T="03">Mitigation areas off the Northeastern United States for sonar, explosives, and physical disturbance and strikes.</E>
                                 (i) 
                                <E T="03">Mitigation area requirements.</E>
                                 (A) 
                                <E T="03">Northeast North Atlantic Right Whale Mitigation Area (year-round):</E>
                            </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Navy personnel must report the total hours and counts of active sonar and in-water explosives used in the mitigation area (which includes North Atlantic right whale ESA-designated critical habitat) in its annual training and testing activity reports submitted to NMFS.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Navy personnel must minimize the use of low-frequency active sonar, mid-frequency active sonar, and high-frequency active sonar to the maximum extent practicable within the mitigation area.
                            </P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) Navy personnel must not use Improved Extended Echo Ranging sonobuoys in or within 3 nmi of the mitigation area or use explosive and non-explosive bombs, in-water detonations, and explosive torpedoes within the mitigation area.
                            </P>
                            <P>
                                (
                                <E T="03">4</E>
                                ) For activities using non-explosive torpedoes within the mitigation area, Navy personnel must conduct activities during daylight hours in Beaufort sea state 3 or less. The Navy must use three Lookouts (one positioned on a vessel and two positioned in an aircraft during dedicated aerial surveys) to observe the vicinity of the activity. An additional Lookout must be positioned on the submarine, when surfaced. Immediately prior to the start of the activity, Navy personnel must observe for floating vegetation and marine mammals; if floating vegetation or marine mammals are observed, Navy personnel must not commence the activity until the vicinity is clear or the activity is relocated to an area where the vicinity is clear. During the activity, Navy personnel must observe for marine mammals; if observed, Navy personnel must cease the activity. To allow a sighted marine mammal to leave the area, Navy personnel must not recommence the activity until one of the following conditions has been met: The animal is observed exiting the vicinity of the activity; the animal is thought to have exited the vicinity of the activity based on a determination of its course, speed, and movement relative to the activity location; or the area has been clear from any additional sightings for 30 min. During transits and normal firing, ships must maintain a speed of no more than 10 knots (kn). During submarine target firing, ships must maintain speeds of no more than 18 kn. During vessel target firing, vessel speeds may exceed 18 kn for brief periods of time (
                                <E T="03">e.g.,</E>
                                 10-15 min).
                            </P>
                            <P>
                                (
                                <E T="03">5</E>
                                ) For all activities, before a vessel transits within the mitigation area, Navy personnel must conduct a web query or email inquiry to the National Oceanographic and Atmospheric Administration Northeast Fisheries Science Center's North Atlantic Right Whale Sighting Advisory System to obtain the latest North Atlantic right whale sightings information. Navy personnel on vessels must use the sightings information to reduce potential interactions with North Atlantic right whales during transits. Navy personnel on vessels must implement speed reductions within the mitigation area after observing a North Atlantic right whale, if transiting within 5 nmi of a sighting reported to the North Atlantic Right Whale Sighting Advisory System within the past week, and if transiting at night or during periods of reduced visibility.
                            </P>
                            <P>
                                (B) 
                                <E T="03">Gulf of Maine Planning Awareness Mitigation Area (year-round):</E>
                            </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Navy personnel must report the total hours and counts of active sonar and in-water explosives used in the mitigation area in its annual training 
                                <PRTPAGE P="21193"/>
                                and testing activity reports submitted to NMFS.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Navy personnel must not conduct greater than 200 hrs of hull-mounted mid-frequency active sonar per year within the mitigation area.
                            </P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) Navy personnel must not conduct major training exercises (Composite Training Unit Exercises or Fleet Exercises/Sustainment Exercises) within the mitigation area. If the Navy needs to conduct a major training exercise within the mitigation area in support of training requirements driven by national security concerns, Navy personnel must confer with NMFS to verify that potential impacts are adequately addressed.
                            </P>
                            <P>
                                (C) 
                                <E T="03">Northeast Planning Awareness Mitigation Areas (year-round):</E>
                                 (
                                <E T="03">1</E>
                                ) Navy personnel will avoid planning major training exercises (Composite Training Unit Exercises or Fleet Exercises/Sustainment Exercises) within the mitigation area to the maximum extent practicable.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Navy personnel must not conduct more than four major training exercises per year (all or a portion of the exercise) within the mitigation area.
                            </P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) If the Navy needs to conduct additional major training exercises in the mitigation area in support of training requirements driven by national security concerns, Navy personnel must provide NMFS with advance notification and include the information in its annual training and testing activity reports submitted to NMFS.
                            </P>
                            <P>(ii) [Reserved]</P>
                            <P>
                                (2) 
                                <E T="03">Mitigation areas off the Mid-Atlantic and Southeastern United States for sonar, explosives, and physical disturbance and strikes.</E>
                            </P>
                            <P>
                                (i) 
                                <E T="03">Mitigation area requirements.</E>
                                 (A) 
                                <E T="03">Southeast North Atlantic Right Whale Mitigation Area (November 15 through April 15):</E>
                            </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Navy personnel must report the total hours and counts of active sonar and in-water explosives used in the mitigation area in its annual training and testing activity reports submitted to NMFS.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) The Navy must not conduct: Low-frequency active sonar (except as noted in paragraph (b)(2)(i)(A)(
                                <E T="03">3</E>
                                ) of this section), mid-frequency active sonar (except as noted in paragraph (b)(2)(i)(A)(
                                <E T="03">3</E>
                                ) of this section), high-frequency active sonar, missile and rocket activities (explosive and non-explosive), small-, medium-, and large-caliber gunnery activities, Improved Extended Echo Ranging sonobuoy activities, explosive and non-explosive bombing activities, in-water detonations, and explosive torpedo activities within the mitigation area.
                            </P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) To the maximum extent practicable, Navy personnel must minimize the use of: helicopter dipping sonar, low-frequency active sonar and hull-mounted mid-frequency active sonar used for navigation training, and low-frequency active sonar and hull-mounted mid-frequency active sonar used for object detection exercises within the mitigation area.
                            </P>
                            <P>
                                (
                                <E T="03">4</E>
                                ) Before transiting or conducting training or testing activities within the mitigation area, Navy personnel must initiate communication with the Fleet Area Control and Surveillance Facility, Jacksonville to obtain Early Warning System North Atlantic right whale sightings data. The Fleet Area Control and Surveillance Facility, Jacksonville must advise Navy personnel on vessels of all reported whale sightings in the vicinity to help Navy personnel on vessels and aircraft reduce potential interactions with North Atlantic right whales. Commander Submarine Force U.S. Atlantic Fleet must coordinate any submarine activities that may require approval from the Fleet Area Control and Surveillance Facility, Jacksonville. Navy personnel on vessels must use the sightings information to reduce potential interactions with North Atlantic right whales during transits.
                            </P>
                            <P>
                                (
                                <E T="03">5</E>
                                ) Navy personnel on vessels must implement speed reductions after they observe a North Atlantic right whale, if they are within 5 nmi of a sighting reported within the past 12 hrs, or when operating in the mitigation area at night or during periods of poor visibility.
                            </P>
                            <P>
                                (
                                <E T="03">6</E>
                                ) To the maximum extent practicable, Navy personnel on vessels must minimize north-south transits in the mitigation area.
                            </P>
                            <P>
                                (B) 
                                <E T="03">Southeast North Atlantic Right Whale Critical Habitat Special Reporting Area (November 15 through April 15):</E>
                            </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Navy personnel must report the total hours and counts of active sonar and in-water explosives used in the Special Reporting Area (which includes southeast North Atlantic right whale ESA-designated critical habitat) in its annual training and testing activity reports submitted to NMFS.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) [Reserved]
                            </P>
                            <P>
                                (C) 
                                <E T="03">Jacksonville Operating Area (November 15 through April 15):</E>
                            </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Navy units conducting training or testing activities in the Jacksonville Operating Area must initiate communication with the Fleet Area Control and Surveillance Facility, Jacksonville to obtain Early Warning System North Atlantic right whale sightings data. The Fleet Area Control and Surveillance Facility, Jacksonville must advise Navy personnel on vessels of all reported whale sightings in the vicinity to help Navy personnel on vessels and aircraft reduce potential interactions with North Atlantic right whales. Commander Submarine Force U.S. Atlantic Fleet must coordinate any submarine activities that may require approval from the Fleet Area Control and Surveillance Facility, Jacksonville. Navy personnel must use the reported sightings information as they plan specific details of events (
                                <E T="03">e.g.,</E>
                                 timing, location, duration) to minimize potential interactions with North Atlantic right whales to the maximum extent practicable. Navy personnel must use the reported sightings information to assist visual observations of applicable mitigation zones and to aid in the implementation of procedural mitigation.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) [Reserved]
                            </P>
                            <P>
                                (D) 
                                <E T="03">Navy Cherry Point Range Complex Nearshore Mitigation Area (March through September):</E>
                            </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Navy personnel must not conduct explosive mine neutralization activities involving Navy divers in the mitigation area.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) To the maximum extent practicable, Navy personnel must not use explosive sonobuoys, explosive torpedoes, explosive medium-caliber and large-caliber projectiles, explosive missiles and rockets, explosive bombs, explosive mines during mine countermeasure and neutralization activities, and anti-swimmer grenades in the mitigation area.
                            </P>
                            <P>
                                (E) 
                                <E T="03">Mid-Atlantic Planning Awareness Mitigation Areas (year-round):</E>
                            </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Navy personnel will avoid planning major training exercises (Composite Training Unit Exercises or Fleet Exercises/Sustainment Exercises) to the maximum extent practicable.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Navy personnel must not conduct more than four major training exercises per year (all or a portion of the exercise) within the mitigation area.
                            </P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) If the Navy needs to conduct additional major training exercises in the mitigation area in support of training requirements driven by national security concerns, Navy personnel must provide NMFS with advance notification and include the information in its annual training and testing activity reports submitted to NMFS.
                            </P>
                            <P>(ii) [Reserved]</P>
                            <P>
                                (3) 
                                <E T="03">Mitigation areas in the Gulf of Mexico for sonar and explosives.</E>
                                 (i) 
                                <E T="03">Mitigation area requirements.</E>
                                 (A) 
                                <E T="03">Gulf of Mexico Planning Awareness Mitigation Areas (year-round):</E>
                            </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Navy personnel must not conduct major training exercises within the mitigation area (all or a portion of the exercise).
                                <PRTPAGE P="21194"/>
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) If the Navy needs to conduct a major training exercise within the mitigation areas in support of training requirements driven by national security concerns, Navy personnel must confer with NMFS to verify that potential impacts are adequately addressed.
                            </P>
                            <P>
                                (B) 
                                <E T="03">Bryde's Whale Mitigation Area (year-round):</E>
                            </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Navy personnel must report the total hours and counts of active sonar and in-water explosives used in the mitigation area in its annual training and testing activity reports submitted to NMFS.
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Navy personnel must not conduct greater than 200 hrs of hull-mounted mid-frequency active sonar per year within the mitigation area.
                            </P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) Navy personnel must not use explosives (except during mine warfare activities) within the mitigation area.
                            </P>
                            <P>(ii) [Reserved]</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 218.85 </SECTNO>
                            <SUBJECT> Requirements for monitoring and reporting.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Unauthorized take.</E>
                                 The Navy must notify NMFS immediately (or as soon as operational security considerations allow) if the specified activity identified in § 218.80 is thought to have resulted in the mortality or serious injury of any marine mammals, or in any Level A or Level B harassment take of marine mammals not identified in this subpart.
                            </P>
                            <P>
                                (b) 
                                <E T="03">Monitoring and reporting under the LOAs.</E>
                                 The Navy must conduct all monitoring and required reporting under the LOAs, including abiding by the AFTT Study Area monitoring program. Details on program goals, objectives, project selection process, and current projects are available at 
                                <E T="03">www.navymarinespeciesmonitoring.us.</E>
                            </P>
                            <P>
                                (c) 
                                <E T="03">Notification of injured, live stranded, or dead marine mammals.</E>
                                 The Navy must consult the Notification and Reporting Plan, which sets out notification, reporting, and other requirements when dead, injured, or live stranded marine mammals are detected. The Notification and Reporting Plan is available at 
                                <E T="03">www.fisheries.noaa.gov/national/marine-mammal-protection/incidental-take-authorizations-military-readiness-activities.</E>
                            </P>
                            <P>
                                (d) 
                                <E T="03">Annual AFTT Study Area marine species monitoring report.</E>
                                 The Navy must submit an annual report of the AFTT Study Area monitoring describing the implementation and results from the previous calendar year. Data collection methods must be standardized across range complexes and study areas to allow for comparison in different geographic locations. The report must be submitted to the Director, Office of Protected Resources of NMFS either within 90 days after the calendar year, or within 90 days after the conclusion of the monitoring year to be determined by the Adaptive Management process. This report will describe progress of knowledge made with respect to monitoring plan study questions across all Navy ranges associated with the Integrated Comprehensive Monitoring Program. Similar study questions must be treated together so that progress on each topic can be summarized across all Navy ranges. The report need not include analyses and content that does not provide direct assessment of cumulative progress on the monitoring plan study questions.
                            </P>
                            <P>
                                (e) 
                                <E T="03">Annual AFTT Study Area training and testing reports.</E>
                                 Each year, the Navy must submit a preliminary report (Quick Look Report) detailing the status of authorized sound sources within 21 days after the anniversary of the date of issuance of each LOA to the Director, Office of Protected Resources, NMFS. Each year, the Navy must submit a detailed report within 3 months after the anniversary of the date of issuance of each LOA to the Director, Office of Protected Resources, NMFS. The annual reports must contain information on Major Training Exercises (MTEs), Sinking Exercise (SINKEX) events, and a summary of all sound sources used, including within specified mitigation reporting areas, as described in paragraph (e)(3) of this section. The analysis in the detailed report must be based on the accumulation of data from the current year's report and data collected from the previous report. The detailed reports must contain information identified in paragraphs (e)(1) through (5) of this section.
                            </P>
                            <P>
                                (1) 
                                <E T="03">Major Training Exercises (MTEs).</E>
                                 This section of the report must contain the following information for MTEs conducted in the AFTT Study Area:
                            </P>
                            <P>(i) Exercise information (for each MTE):</P>
                            <P>(A) Exercise designator;</P>
                            <P>(B) Date that exercise began and ended;</P>
                            <P>(C) Location;</P>
                            <P>(D) Number and types of active sonar sources used in the exercise;</P>
                            <P>(E) Number and types of passive acoustic sources used in exercise;</P>
                            <P>(F) Number and types of vessels, aircraft, and other platforms participating in exercise;</P>
                            <P>(G) Total hours of all active sonar source operation;</P>
                            <P>(H) Total hours of each active sonar source bin; and</P>
                            <P>(I) Wave height (high, low, and average) during exercise.</P>
                            <P>(ii) Individual marine mammal sighting information for each sighting in each exercise where mitigation was implemented:</P>
                            <P>(A) Date/time/location of sighting;</P>
                            <P>(B) Species (if not possible, indication of whale/dolphin/pinniped);</P>
                            <P>(C) Number of individuals;</P>
                            <P>
                                (D) Initial detection sensor (
                                <E T="03">e.g.,</E>
                                 sonar, Lookout);
                            </P>
                            <P>(E) Indication of specific type of platform observation made from (including, for example, what type of surface vessel or testing platform);</P>
                            <P>(F) Length of time observers maintained visual contact with marine mammal;</P>
                            <P>(G) Sea state;</P>
                            <P>(H) Visibility;</P>
                            <P>(I) Sound source in use at the time of sighting;</P>
                            <P>(J) Indication of whether animal was less than 200 yd, 200 to 500 yd, 500 to 1,000 yd, 1,000 to 2,000 yd, or greater than 2,000 yd from sonar source;</P>
                            <P>
                                (K) Mitigation implementation (
                                <E T="03">e.g.,</E>
                                 whether operation of sonar sensor was delayed, or sonar was powered or shut down, and how long the delay was);
                            </P>
                            <P>(L) If source in use was hull-mounted, true bearing of animal from the vessel, true direction of vessel's travel, and estimation of animal's motion relative to vessel (opening, closing, parallel); and</P>
                            <P>(M) Lookouts must report, in plain language and without trying to categorize in any way, the observed behavior of the animal(s) (such as animal closing to bow ride, paralleling course/speed, floating on surface and not swimming, etc.) and if any calves were present.</P>
                            <P>(iii) An evaluation (based on data gathered during all of the MTEs) of the effectiveness of mitigation measures designed to minimize the received level to which marine mammals may be exposed. This evaluation must identify the specific observations that support any conclusions the Navy reaches about the effectiveness of the mitigation.</P>
                            <P>
                                (2) 
                                <E T="03">Sinking exercises (SINKEXs).</E>
                                 This section of the report must include the following information for each SINKEX completed that year:
                            </P>
                            <P>(i) Exercise information (gathered for each SINKEX):</P>
                            <P>(A) Location;</P>
                            <P>(B) Date and time exercise began and ended;</P>
                            <P>(C) Total hours of observation by Lookouts before, during, and after exercise;</P>
                            <P>(D) Total number and types of explosive source bins detonated;</P>
                            <P>(E) Number and types of passive acoustic sources used in exercise;</P>
                            <P>
                                (F) Total hours of passive acoustic search time;
                                <PRTPAGE P="21195"/>
                            </P>
                            <P>(G) Number and types of vessels, aircraft, and other platforms participating in exercise;</P>
                            <P>(H) Wave height in feet (high, low, and average) during exercise; and</P>
                            <P>(I) Narrative description of sensors and platforms utilized for marine mammal detection and timeline illustrating how marine mammal detection was conducted.</P>
                            <P>(ii) Individual marine mammal sighting information for each sighting where mitigation was implemented:</P>
                            <P>(A) Date/time/location of sighting;</P>
                            <P>(B) Species (if not possible, indicate whale, dolphin, or pinniped);</P>
                            <P>(C) Number of individuals;</P>
                            <P>
                                (D) Initial detection sensor (
                                <E T="03">e.g.,</E>
                                 sonar or Lookout);
                            </P>
                            <P>(E) Length of time observers maintained visual contact with marine mammal;</P>
                            <P>(F) Sea state;</P>
                            <P>(G) Visibility; and</P>
                            <P>(H) Whether sighting was before, during, or after detonations/exercise, and how many minutes before or after.</P>
                            <P>
                                (I) Distance of marine mammal from actual detonations (
                                <E T="03">e.g.</E>
                                 less than 200 yd, 200 to 500 yd, 500 to 1,000 yd, 1,000 to 2,000 yd, or greater than 2,000 yd, or target spot if not yet detonated).
                            </P>
                            <P>(J) Lookouts must report, in plain language and without trying to categorize in any way, the observed behavior of the animal(s) (such as animal closing to bow ride, paralleling course/speed, floating on surface and not swimming etc.), including speed and direction and if any calves were present.</P>
                            <P>(K) Resulting mitigation implementation: The report must indicate whether explosive detonations were delayed, ceased, modified, or not modified due to marine mammal presence and for how long.</P>
                            <P>(L) If observation occurred while explosives were detonating in the water, indicate munition type in use at time of marine mammal detection.</P>
                            <P>
                                (3) 
                                <E T="03">Summary of sources used.</E>
                                 This section must include the following information summarized from the authorized sound sources used in all training and testing events:
                            </P>
                            <P>(i) Total annual hours or quantity (per the LOA) of each bin of sonar or other acoustic sources (pile driving and air gun activities); and</P>
                            <P>(ii) Total annual expended/detonated ordnance (missiles, bombs, sonobuoys, etc.) for each explosive bin.</P>
                            <P>
                                (4) 
                                <E T="03">Geographic information presentation.</E>
                                 The reports must present an annual (and seasonal, where practical) depiction of training and testing bin usage (as well as pile driving activities) geographically across the AFTT Study Area.
                            </P>
                            <P>
                                (5) 
                                <E T="03">Sonar exercise notification.</E>
                                 The Navy must submit to NMFS (contact as specified in the LOA) an electronic report within fifteen calendar days after the completion of any MTE indicating:
                            </P>
                            <P>(i) Location of the exercise;</P>
                            <P>(ii) Beginning and end dates of the exercise; and</P>
                            <P>(iii) Type of exercise.</P>
                            <P>
                                (f) 
                                <E T="03">Seven-year close-out comprehensive training and testing report.</E>
                                 This report must be included as part of the 2025 annual training and testing report. This report must provide the annual totals for each sound source bin with a comparison to the annual allowance and the seven-year total for each sound source bin with a comparison to the seven-year allowance. Additionally, if there were any changes to the sound source allowance, this report must include a discussion of why the change was made and include the analysis to support how the change did or did not result in a change in the EIS and final rule determinations. The draft report must be submitted within three months after the expiration of this subpart to the Director, Office of Protected Resources, NMFS. NMFS must submit comments on the draft close-out report, if any, within three months of receipt. The report will be considered final after the Navy has addressed NMFS' comments, or 3 months after the submittal of the draft if NMFS does not provide comments.
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 218.86 </SECTNO>
                            <SUBJECT> Letters of Authorization.</SUBJECT>
                            <P>(a) To incidentally take marine mammals pursuant to the regulations in this subpart, the Navy must apply for and obtain Letters of Authorization (LOAs) in accordance with § 216.106 of this chapter.</P>
                            <P>(b) LOAs, unless suspended or revoked, may be effective for a period of time not to exceed the expiration date of the regulations in this subpart.</P>
                            <P>(c) If an LOA expires prior to the expiration date of the regulations in this subpart, the Navy may apply for and obtain a renewal of the LOA.</P>
                            <P>(d) In the event of projected changes to the activity or to mitigation, monitoring, or reporting (excluding changes made pursuant to the adaptive management provision of § 218.87(c)(1) as required by an LOA issued under this subpart, the Navy must apply for and obtain a modification of the LOA as described in § 218.87.</P>
                            <P>(e) Each LOA will set forth:</P>
                            <P>(1) Permissible methods of incidental taking;</P>
                            <P>(2) Specified geographic areas for incidental taking;</P>
                            <P>
                                (3) Means of effecting the least practicable adverse impact (
                                <E T="03">i.e.,</E>
                                 mitigation) on the species or stocks of marine mammals and their habitat; and
                            </P>
                            <P>(4) Requirements for monitoring and reporting.</P>
                            <P>(f) Issuance of the LOA(s) will be based on a determination that the level of taking must be consistent with the findings made for the total taking allowable under the regulations in this subpart.</P>
                            <P>
                                (g) Notice of issuance or denial of the LOA(s) will be published in the 
                                <E T="04">Federal Register</E>
                                 within 30 days of a determination.
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 218.87 </SECTNO>
                            <SUBJECT> Renewals and modifications of Letters of Authorization.</SUBJECT>
                            <P>(a) An LOA issued under §§ 216.106 of this subchapter and 218.86 may be renewed or modified upon request by the applicant, provided that:</P>
                            <P>(1) The planned specified activity and mitigation, monitoring, and reporting measures, as well as the anticipated impacts, are the same as those described and analyzed for the regulations in this subpart (excluding changes made pursuant to the adaptive management provision in paragraph (c)(1) of this section); and</P>
                            <P>(2) NMFS determines that the mitigation, monitoring, and reporting measures required by the previous LOA(s) under the regulations in this subpart were implemented.</P>
                            <P>
                                (b) For LOA modification or renewal requests by the applicant that include changes to the activity or to the mitigation, monitoring, or reporting measures (excluding changes made pursuant to the adaptive management provision in paragraph (c)(1) of this section) that do not change the findings made for the regulations or result in no more than a minor change in the total estimated number of takes (or distribution by species or stock or years), NMFS may publish a notice of planned LOA in the 
                                <E T="04">Federal Register</E>
                                , including the associated analysis of the change, and solicit public comment before issuing the LOA.
                            </P>
                            <P>(c) An LOA issued under §§ 216.106 of this subchapter and 218.86 may be modified by NMFS under the following circumstances:</P>
                            <P>
                                (1) 
                                <E T="03">Adaptive management.</E>
                                 After consulting with the Navy regarding the practicability of the modifications, NMFS may modify (including adding or removing measures) the existing mitigation, monitoring, or reporting measures if doing so creates a reasonable likelihood of more effectively accomplishing the goals of the mitigation and monitoring.
                            </P>
                            <P>
                                (i) Possible sources of data that could contribute to the decision to modify the 
                                <PRTPAGE P="21196"/>
                                mitigation, monitoring, or reporting measures in an LOA include:
                            </P>
                            <P>(A) Results from the Navy's monitoring from the previous year(s);</P>
                            <P>(B) Results from other marine mammal and/or sound research or studies; or</P>
                            <P>(C) Any information that reveals marine mammals may have been taken in a manner, extent, or number not authorized by the regulations in this subpart or subsequent LOAs.</P>
                            <P>
                                (ii) If, through adaptive management, the modifications to the mitigation, monitoring, or reporting measures are substantial, NMFS will publish a notice of planned LOA in the 
                                <E T="04">Federal Register</E>
                                 and solicit public comment.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Emergencies.</E>
                                 If NMFS determines that an emergency exists that poses a significant risk to the well-being of the species or stocks of marine mammals specified in LOAs issued pursuant to §§ 216.106 of this chapter and 218.86, an LOA may be modified without prior notice or opportunity for public comment. Notice would be published in the 
                                <E T="04">Federal Register</E>
                                 within thirty days of the action.
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ § 218.88-218.89 </SECTNO>
                            <SUBJECT> [Reserved]</SUBJECT>
                        </SECTION>
                    </SUBPART>
                </SUPLINF>
                <FRDOC>[FR Doc. 2019-09541 Filed 5-10-19; 8:45 am]</FRDOC>
                <BILCOD> BILLING CODE 3510-22-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>84</VOL>
    <NO>92</NO>
    <DATE>Monday, May 13, 2019</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="21197"/>
            <PARTNO>Part V</PARTNO>
            <AGENCY TYPE="P">Department of the Treasury</AGENCY>
            <SUBAGY> Internal Revenue Service</SUBAGY>
            <HRULE/>
            <CFR>21 CFR Part 1</CFR>
            <TITLE> Withholding of Tax and Information Reporting With Respect to Interests in Partnerships Engaged in the Conduct of a U.S. Trade or Business; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="21198"/>
                    <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                    <SUBAGY>Internal Revenue Service</SUBAGY>
                    <CFR>26 CFR Part 1</CFR>
                    <DEPDOC>[REG-105476-18]</DEPDOC>
                    <RIN>RIN 1545-BO60</RIN>
                    <SUBJECT>Withholding of Tax and Information Reporting With Respect to Interests in Partnerships Engaged in the Conduct of a U.S. Trade or Business</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.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>This document contains proposed regulations implementing certain sections of the Internal Revenue Code, including sections added to the Internal Revenue Code by the Tax Cuts and Jobs Act, that relate to the withholding of tax and information reporting with respect to certain dispositions of interests in partnerships engaged in the conduct of a trade or business within the United States. The proposed regulations affect certain foreign persons that recognize gain or loss from the sale or exchange of an interest in a partnership that is engaged in the conduct of a trade or business within the United States, and persons that acquire those interests. The proposed regulations also affect partnerships that, directly or indirectly, have foreign persons as partners.</P>
                    </SUM>
                    <DATES>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Written or electronic comments and requests for a public hearing must be received by July 12, 2019.</P>
                    </DATES>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            Send submissions to: CC:PA:LPD:PR (REG-105476-18), Internal Revenue Service, Room 5203, P.O. Box 7604, Ben Franklin Station, Washington, DC 20044. Submissions may be hand-delivered Monday through Friday between the hours of 8 a.m. and 4 p.m. to CC:PA:LPD:PR (REG-105476-18), Courier's Desk, Internal Revenue Service, 1111 Constitution Avenue NW, Washington, DC 20224, or sent electronically via the Federal eRulemaking Portal at 
                            <E T="03">http://www.regulations.gov</E>
                             (IRS REG-105476-18).
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Concerning the proposed regulations, Chadwick Rowland, 202-317-6937; concerning submissions of comments or requests for a public hearing, Regina L. Johnson (202) 317-6901 (not toll-free numbers).</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P/>
                    <HD SOURCE="HD1">Background</HD>
                    <HD SOURCE="HD1">I. Section 1446(f)</HD>
                    <P>Section 1446(f), which was added to the Internal Revenue Code (the “Code”) by section 13501 of the Tax Cuts and Jobs Act, Public Law 115-97 (2017) (the “Act”), provides rules for withholding on the transfer of a partnership interest described in section 864(c)(8). Section 1446(f)(1) provides that, except as otherwise provided in section 1446(f), if a portion of the gain (if any) on any disposition of an interest in a partnership would be treated under section 864(c)(8) as effectively connected with the conduct of a trade or business within the United States, the transferee is required to deduct and withhold a tax equal to 10 percent of the amount realized on the disposition.</P>
                    <P>Section 1446(f)(2)(A) provides an exception to the general withholding requirement described in section 1446(f)(1) if the transferor furnishes an affidavit to the transferee stating, under penalties of perjury, the transferor's United States taxpayer identification number and that the transferor is not a foreign person. Section 1446(f)(2)(B)(i) provides that the exception to withholding described in section 1446(f)(2)(A) will not apply if the transferee has actual knowledge that the affidavit furnished is false, or if the transferee receives a notice from a transferor's agent or transferee's agent that the affidavit is false.</P>
                    <P>Section 1446(f)(3) provides that, at the request of the transferor or transferee, the Secretary may prescribe a reduced amount to be withheld under this section if the Secretary determines that reducing the amount to be withheld will not jeopardize the collection of tax on gain treated under section 864(c)(8) as effectively connected with the conduct of a trade or business within the United States.</P>
                    <P>Section 1446(f)(4) provides that if a transferee fails to withhold any amount required to be withheld under section 1446(f)(1) then the partnership must deduct and withhold from distributions to the transferee a tax in an amount equal to the amount the transferee failed to withhold, plus interest.</P>
                    <P>Section 1446(f)(6) generally provides that the Secretary shall prescribe such regulations as may be necessary to carry out the purposes of section 1446(f), including regulations providing for exceptions from the provisions of section 1446(f). Section 1446(f) is effective for sales, exchanges, and other dispositions after December 31, 2017.</P>
                    <P>On December 29, 2017, the Department of the Treasury (the “Treasury Department”) and the Internal Revenue Service (the “IRS”) released Notice 2018-08, 2018-7 I.R.B. 352, which temporarily suspends the requirement to withhold on amounts realized in connection with the sale, exchange, or disposition of certain interests in a publicly traded partnership not treated as a corporation under section 7704 and the regulations thereunder. On April 2, 2018, the Treasury Department and the IRS released Notice 2018-29, 2018-16 I.R.B. 495, which provides temporary guidance and announces an intent to issue proposed regulations under section 1446(f) with respect to the sale, exchange, or disposition of certain interests in non-publicly traded partnerships. Notice 2018-29, and section 1446(f)(1) generally, rely on the principles contained within the section 1445 withholding regime. Under section 1445, if a foreign person disposes of a United States real property interest (“U.S. real property interest”), as defined in section 897(c), a withholding obligation is imposed on the transferee of the interest.</P>
                    <P>
                        On December 27, 2018, the Treasury Department and the IRS published in the 
                        <E T="04">Federal Register</E>
                         a notice of proposed rulemaking at 83 FR 66647 (REG-113604-18) under section 864(c)(8) (the “proposed section 864(c)(8) regulations”). The proposed section 864(c)(8) regulations provide rules for determining the amount of gain or loss treated as effectively connected with the conduct of a trade or business within the United States (“effectively connected gain” or “effectively connected loss”) described in section 864(c)(8), including rules coordinating section 864(c)(8) with sections 741 and 751 (relating to the character of gain or loss realized in connection with the sale or exchange of an interest in a partnership). They also provide rules for coordination of section 864(c)(8) with section 897 (relating to amounts treated as effectively connected gain or loss with respect to U.S. real property interests), tiered partnerships, and U.S. income tax treaties.
                    </P>
                    <HD SOURCE="HD1">II. Rules for Withholding Under Section 1446(a) on Distributions by Publicly Traded Partnerships</HD>
                    <P>
                        Generally, withholding under section 1446(a) is required by a partnership when effectively connected taxable income (“ECTI”) is allocable to a foreign person. 
                        <E T="03">See</E>
                         §§ 1.1446-2 and 1.1446-3. However, withholding on ECTI earned by a publicly traded partnership is required when the ECTI is distributed to the foreign person. 
                        <E T="03">See</E>
                         § 1.1446-4. Often, an interest in the publicly traded partnership is held by a nominee, such 
                        <PRTPAGE P="21199"/>
                        as a domestic financial institution that holds the publicly traded partnership interest as a custodian for a foreign partner. Section 1.1446-4 provides rules for applying the withholding tax under section 1446(a) to distributions by publicly traded partnerships. Under those rules, when a publicly traded partnership provides a qualified notice (within the meaning of § 1.1446-4(b)(4)), a nominee, which must be a domestic person, may be treated as a withholding agent with respect to a distribution. 
                        <E T="03">See</E>
                         § 1.1446-4(b)(4) and 1.1446-4(d). The qualified notice must be given in accordance with notice requirements with respect to dividends under regulations under the Securities Exchange Act of 1934. Section 1.1445-8(f) provides similar qualified notice rules that apply to certain distributions subject to withholding when attributable to the disposition of a U.S. real property interest.
                    </P>
                    <P>Section 1.1446-4(f)(3) provides an ordering rule for situations in which the distribution is attributable to multiple types of income (such as amounts attributable to income described in section 1441 or 1442 or amounts subject to withholding under section 1446). However, no rule is provided for situations in which a qualified notice does not provide information regarding the types of income being distributed.</P>
                    <HD SOURCE="HD1">Explanation of Provisions</HD>
                    <P>
                        The proposed regulations provide rules for withholding, reporting, and paying tax under section 1446(f) upon the sale, exchange, or other disposition of an interest in a partnership described in section 864(c)(8) and proposed § 1.864(c)(8)-1.
                        <SU>1</SU>
                        <FTREF/>
                         The proposed regulations would, when finalized, adopt many of the rules that were described in Notice 2018-29, with certain modifications provided, in part, in response to comments. In addition, the proposed regulations provide reporting rules relating to section 864(c)(8) and rules implementing withholding under section 1446(f)(4). They also contain rules clarifying the reporting rules applicable to transfers of partnership interests subject to section 6050K. Further, the proposed regulations provide rules implementing withholding by brokers on transfers of certain interests in publicly traded partnerships subject to section 1446(f)(1), and make related changes to the reporting rules and procedures for adjusting withholding under sections 1461, 1463, and 1464. They also make changes to the rules regarding withholding on distributions by publicly traded partnerships under § 1.1446-4, including the rules that apply to qualified notices and nominees. Finally, the proposed regulations provide rules coordinating withholding under section 1446(f) with other withholding regimes to prevent overwithholding of tax.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             § 1.864(c)(8)-1 was proposed to be added on December 27, 2018; 83 FR 66647, 66651.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">I. Reporting Requirements for Foreign Transferors and Partnerships With Foreign Transferors</HD>
                    <P>
                        A partnership that is engaged in the conduct of a trade or business within the United States is required to file an annual information return, Form 1065, 
                        <E T="03">U.S. Return of Partnership Income,</E>
                         and also provide information to its partners on Schedule K-1 (Form 1065), 
                        <E T="03">Partner's Share of Income, Deductions, Credits, etc.,</E>
                         with respect to each partner's distributive share of partnership items and other information. 
                        <E T="03">See</E>
                         section 6031 and §§ 1.6031(a)-1 and 1.6031(b)-1T. Domestic partners generally report the information from the Schedule K-1 (Form 1065) on their income tax return, typically Form 1040, 
                        <E T="03">U.S. Individual Income Tax Return,</E>
                         for an individual, or Form 1120, 
                        <E T="03">U.S. Corporation Income Tax Return,</E>
                         for a corporation. A foreign partner with a U.S. income tax return filing obligation generally files Form 1040NR, 
                        <E T="03">U.S. Nonresident Alien Income Tax Return,</E>
                         or Form 1120-F, 
                        <E T="03">U.S. Income Tax Return of a Foreign Corporation.</E>
                    </P>
                    <P>
                        A partner (foreign or domestic) that transfers an interest in a partnership in an exchange described in section 751(a) (relating to an exchange of an interest in a partnership that holds unrealized receivables or inventory) generally has an obligation both to inform the partnership of the transfer and to include a statement with respect to the exchange on the partner's income tax return under § 1.751-1(a)(3). 
                        <E T="03">See</E>
                         section 6050K(c) and § 1.6050K-1(d). A partnership also has an obligation to provide information with respect to the exchange to the transferee and transferor under section 6050K(c) and § 1.6050K-1(c). 
                        <E T="03">See also</E>
                         Form 8308, 
                        <E T="03">Report of a Sale or Exchange of Certain Partnership Interests.</E>
                    </P>
                    <P>Because section 864(c)(8) requires a deemed sale at the partnership level to determine a foreign partner's effectively connected gain or loss, a foreign person that transfers its partnership interest generally will not be able to compute its income tax liability under section 864(c)(8) unless the partnership provides certain information to the foreign partner. The proposed regulations therefore provide rules that facilitate the transfer of information between a foreign partner and the partnership for purposes of section 864(c)(8).</P>
                    <P>
                        The proposed regulations generally provide that a notifying transferor (generally, any foreign person and certain domestic partnerships that have a foreign person as a direct or indirect partner) that transfers (within the meaning of proposed § 1.864(c)(8)-1(g)(5)) an interest in a partnership (other than certain interests in a publicly traded partnership) in a transaction described in section 864(c)(8) must notify the partnership within 30 days of the transfer by providing a statement that includes information relevant to the partnership for making calculations under section 864(c)(8), including the date on which the notifying transferor transferred its interest, and other identifying information regarding the transferor and transferee. 
                        <E T="03">See</E>
                         proposed § 1.864(c)(8)-2(a). This rule generally parallels § 1.6050K-1, including the content of the information and when it must be provided.
                    </P>
                    <P>
                        Proposed § 1.864(c)(8)-2(b) requires a specified partnership (generally, a partnership that is engaged in the conduct of a trade or business within the United States or a partnership that owns, directly or indirectly, an interest in a partnership so engaged) to furnish to a notifying transferor the information necessary for the transferor to comply with section 864(c)(8) by the due date of the Schedule K-1 (Form 1065) for the tax year of the partnership in which the transfer occurred. Proposed § 1.864(c)(8)-2(b) applies if a specified partnership receives the notification described in proposed § 1.864(c)(8)-2(a), or otherwise knows that a relevant transfer has occurred, and the notifying transferor would have had a distributive share of deemed sale EC gain or deemed sale EC loss (within the meaning of proposed § 1.864(c)(8)-1(c)) at the time of the transfer. For these purposes, a notifying transferor that is a partnership is treated as a nonresident alien. Proposed § 1.864(c)(8)-2(b) provides that, for purposes of the reporting requirements described in proposed § 1.864(c)(8)-2, a partnership that makes a distribution to a transferor that qualifies as a transfer under section 864(c)(8) and proposed § 1.864(c)(8)-1(b) will be treated as having actual knowledge that a transfer occurred, thereby triggering the reporting requirement of proposed § 1.864(c)(8)-2(b) to the extent that the transferee would have had a distributive share of deemed sale EC gain or deemed sale EC loss within the meaning of proposed § 1.864(c)(8)-1(c).
                        <PRTPAGE P="21200"/>
                    </P>
                    <P>
                        Relatedly, the proposed regulations clarify that the information a partnership must provide under section 6050K upon being notified of a transfer includes the information necessary for a transferor to make the transferor's required statement under § 1.751-1(a)(3). 
                        <E T="03">See</E>
                         proposed § 1.6050K-1(c)(2).
                    </P>
                    <HD SOURCE="HD1">II. Definitions and General Rules of Applicability</HD>
                    <HD SOURCE="HD2">A. Definitions</HD>
                    <P>
                        For purposes of the proposed regulations under section 1446(f), the term “transfer” means a sale, exchange, or other disposition, and includes a distribution from a partnership to a partner. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-1(b)(9). A “transferee” is any person, foreign or domestic, that acquires a partnership interest through a transfer. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-1(b)(10). The term “transferor” generally means any person, foreign or domestic, that transfers a partnership interest, and therefore refers to the person that directly owns the interest in the partnership. For a trust, to the extent all or a portion of the trust is treated as owned by the grantor or another person under sections 671 through 679 (such trust, “a grantor trust”), the term “transferor” means the grantor or other person. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-1(b)(11). 
                        <E T="03">See also</E>
                         Rev. Rul. 85-13, 1985-1 C.B. 184.
                    </P>
                    <HD SOURCE="HD2">B. Certifications and Books and Records</HD>
                    <P>
                        Similar to the approach described in Notice 2018-29, the proposed regulations provide various exceptions to withholding and procedures for determining the amount to withhold. Under these rules, the person required to withhold may generally rely on information provided in certifications that it receives or that is contained in its own books and records. The general rules of applicability provide the requirements for providing a valid certification and for retaining certifications or information in books and records. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-1(c)(2). A certification includes any documents associated with the certification, such as statements from the partnership, IRS forms, withholding certificates, withholding statements, certifications, or other documentation. 
                        <E T="03">Id.</E>
                    </P>
                    <HD SOURCE="HD2">C. Determination Dates</HD>
                    <P>
                        Notice 2018-29 required determinations to be made as of the date of transfer when applying many of its rules and exceptions. Because it may be difficult to make these determinations on the precise date of transfer, the proposed regulations generally allow the choice of one of several dates solely for purposes of making determinations under section 1446(f)(1) with regard to a transfer. This date is referred to as the determination date. It is chosen on a transfer-by-transfer basis and must be used for a transfer for all purposes of section 1446(f). The determination date must be one of the following: the date of the transfer, any date no more than 60 days before the transfer, or, with respect to a transferor that is not a controlling partner, the later of either the first day of the partnership's taxable year in which the transfer occurs or the date before the transfer of the most recent revaluation described in § 1.704-1(b)(2)(iv)(
                        <E T="03">f</E>
                        )(
                        <E T="03">5</E>
                        ) or 1.704-1(b)(2)(iv)(
                        <E T="03">s</E>
                        )(
                        <E T="03">1</E>
                        ). 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-1(c)(4). As the determination date applies only for purposes of determining the withholding obligation under section 1446(f), the calculation of tax resulting from the application of section 864(c)(8) and the reporting requirements under proposed § 1.864(c)(8)-2 are determined based on the date of the transfer.
                    </P>
                    <HD SOURCE="HD2">D. IRS Forms and Instructions</HD>
                    <P>Proposed § 1.1446(f)-1(c)(5) provides that any reference in the proposed regulations to an IRS form includes its successor form and that any form must be filed in the manner provided in the instructions to the forms or in other guidance. The IRS intends to modify publications, instructions and forms (including forms discussed in this Explanation of Provisions) as appropriate to take into account sections 864(c)(8) and 1446(f).</P>
                    <HD SOURCE="HD2">E. Coordination With Other Withholding Rules</HD>
                    <P>
                        Proposed § 1.1446(f)-1(d) provides a rule coordinating section 1446(f)(1) with section 1445. Specifically, the rule provides that if a transferee is required to withhold under section 1445(e)(5) or § 1.1445-11T(d)(1) and section 1446(f)(1), then the transferee will be subject to the payment and reporting requirements of section 1445 only. This rule clarifies that even though proposed § 1.864(c)(8)-1(d) provides that section 897(g) does not apply to a transfer that is also subject to section 864(c)(8), the withholding regime provided in section 1445 and the regulations thereunder applies under these circumstances, rather than the rules described in section 1446(f)(1). Thus, if a foreign transferor disposes of an interest in a partnership that is engaged in the conduct of a trade or business within the United States (not taking into account the application of section 897(a)) and in which fifty percent or more of the value of the gross assets consist of U.S. real property interests, and ninety percent or more of the value of the gross assets consist of U.S. real property interests plus any cash or cash equivalents, a transferee must generally withhold under section 1445(a) (at 15 percent of the amount realized) and not section 1446(f). However, this rule applies only if the transferor has not applied for a withholding certificate under § 1.1445-11T(d)(1). 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-1(d). If the transferor has applied for a withholding certificate, then the transferee must withhold the greater of the amounts required under section 1445(e)(5) or section 1446(f)(1).
                    </P>
                    <P>
                        Because gain that an upper-tier partnership recognizes on the transfer of an interest in a lower-tier partnership engaged in the conduct of a trade or business within the United States is included when calculating the upper-tier partnership's ECTI, the proposed regulations also provide a coordination rule that allows a partnership that is withheld upon under section 1446(f)(1) (in its capacity as a transferor) to claim a credit for the amount withheld against its withholding tax liability under section 1446(a) (if any). 
                        <E T="03">See</E>
                         proposed § 1.1446-3(c)(4). 
                        <E T="03">See also</E>
                         § 1.1446-3(d)(2) for rules on how the partnership or its partners may claim a credit or refund for tax paid under section 1446.
                    </P>
                    <HD SOURCE="HD1">III. Withholding on the Transfer of a Non-Publicly Traded Partnership Interest by a Foreign Person</HD>
                    <HD SOURCE="HD2">A. In General</HD>
                    <P>
                        Under section 1446(f)(1), a transferee of a partnership interest must withhold a tax equal to 10 percent of the amount realized on any disposition when the disposition results in gain that is treated as effectively connected with the conduct of a trade or business within the United States under section 864(c)(8). Proposed § 1.1446(f)-2(a) implements this rule by requiring any transferee to withhold a tax equal to 10 percent of the amount realized on any transfer of a partnership interest (other than certain publicly traded partnership interests) under section 1446(f)(1), unless an exception to withholding applies under proposed § 1.1446(f)-2(b). If an exception does not apply and withholding is required, proposed § 1.1446(f)-2(c) provides rules for determining and adjusting the amount required to be withheld under section 1446(f)(1). The exceptions and determination procedures in the proposed regulations apply solely for purposes of section 1446(f)(1) and do not affect a foreign person's filing obligation under the Code or a foreign 
                        <PRTPAGE P="21201"/>
                        person's tax liability resulting from the application of section 864(c)(8).
                    </P>
                    <HD SOURCE="HD2">B. Exceptions to Withholding</HD>
                    <HD SOURCE="HD3">1. In General</HD>
                    <P>
                        The proposed regulations provide six exceptions to withholding by a transferee under section 1446(f)(1). These exceptions generally allow the transferee to rely on certain certifications that it receives from the transferor or partnership unless it has actual knowledge that the certifications are incorrect or unreliable. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(b)(1). When the partnership is a transferee because it makes a distribution, it may instead rely on its books and records unless it knows, or has reason to know, that the information is incorrect or unreliable. 
                        <E T="03">Id.</E>
                    </P>
                    <HD SOURCE="HD3">2. Certification of Non-Foreign Status by Transferor</HD>
                    <P>
                        Consistent with section 6.01 of Notice 2018-29, proposed § 1.1446(f)-2(b)(2) provides the requirements for a certification of non-foreign status (including the requirement that it include the transferor's TIN), and clarifies that a valid Form W-9, 
                        <E T="03">Request for Taxpayer Identification Number and Certification,</E>
                         may be used for this purpose, including a Form W-9 for the transferor that is already in the transferee's possession. The proposed regulations also clarify that a Form W-9 may be used to establish non-foreign status of a transferor for purposes of section 1445. 
                        <E T="03">See</E>
                         proposed §§ 1.1445-2(b)(2)(v) and 1.1445-5(b)(3)(iv).
                    </P>
                    <HD SOURCE="HD3">3. No Realized Gain by Transferor</HD>
                    <P>Section 1446(f)(1) applies only when there is gain described in section 864(c)(8) on the transfer of a partnership interest. Consistent with section 6.02 of Notice 2018-29, the proposed regulations provide that a transferee is not required to withhold if the transferor provides the transferee with a certification stating that the transferor would not realize any gain on the transfer of the partnership interest determined as if the transfer occurred on the determination date. Proposed § 1.1446(f)-2(b)(3)(i) provides that this certification of no realized gain must take into account any ordinary income arising from application of section 751(a) and the regulations thereunder. Therefore, a transferor may not provide the certification if section 751(a) and the regulations thereunder require the transferor to realize ordinary income, even if the transferor would realize an overall loss on the transfer.</P>
                    <P>
                        A similar rule in proposed § 1.1446(f)-2(b)(3)(ii) applies to partnership distributions. Section 731 generally provides that if a distribution of money to a partner exceeds the partner's adjusted basis in its interest in the partnership, then gain will be recognized to the extent of the difference between the money distributed and the partner's basis. That gain or loss is considered as gain or loss from the sale or exchange of the partnership interest of the distributee partner. 
                        <E T="03">See</E>
                         section 731(a). Consistent with section 9 of Notice 2018-29, proposed § 1.1446(f)-2(b)(3)(ii) provides that for purposes of determining whether withholding is required on a distribution, a partnership is permitted to rely on its books and records or on a certification provided by the transferor (the distributee partner) to determine if there is realized gain to the distributee partner.
                    </P>
                    <HD SOURCE="HD3">4. Effectively Connected Gain Upon a Partnership's Deemed Sale</HD>
                    <P>To make the determination of whether there is a transfer to which withholding applies more administrable for transferors and transferees, proposed § 1.1446(f)-2(b)(4) provides that no withholding is required if the transferee receives a certification from the partnership stating that if the partnership sold all of its assets at fair market value, the amount of net effectively connected gain resulting from the deemed sale would be less than 10 percent of the total net gain. Section 6.04 of Notice 2018-29 provided a similar rule, but at a threshold of 25 percent. Proposed § 1.1446(f)-2(b)(4) lowers the percentage threshold in accordance with section 2 of Notice 2018-29, which stated that the Treasury Department and the IRS intend to provide future guidance reducing the percentage threshold provided in section 6.04 of Notice 2018-29. The proposed regulations also allow a partnership that is a transferee because it makes a distribution to use this exception when it determines that the 10-percent test is satisfied from its books and records.</P>
                    <P>
                        To make it easier for the partnership to calculate its effectively connected gain from the deemed sale, the proposed regulations allow this amount to be determined as of the determination date. Further, the proposed regulations allow a partnership to make this determination when no gain on the deemed sale would have been effectively connected with the conduct of a trade or business within the United States (for example, when the deemed sale would result in a loss that would have been effectively connected with the conduct of a trade or business within the United States). 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(b)(4)(i)(B).
                    </P>
                    <HD SOURCE="HD3">5. Allocable Share of ECTI</HD>
                    <P>
                        Section 6.03 of Notice 2018-29 provided an exception to withholding under section 1446(f)(1) for situations in which a transferor's distributive share of ECTI during the previous three taxable years was less than 25 percent of the transferor's total distributive share of income in each year (the “three-year ECTI exception”). Section 2 of Notice 2018-29 provided that the Treasury Department and the IRS intended to lower the three-year ECTI exception's 25 percent threshold in proposed regulations, and that other limitations for this rule were under consideration. 
                        <E T="03">See also</E>
                         section III.B.4 of this Explanation of Provisions (describing modifications to the threshold set forth in section 6.04 of Notice 2018-29).
                    </P>
                    <P>The three-year ECTI exception was intended to relieve potentially significant overwithholding that could arise when a partner transfers an interest in a partnership, recognizes relatively little effectively connected gain under section 864(c)(8), but cannot obtain information from the partnership at the time of the transfer necessary to qualify for the deemed sale exception described in section III.B.4 of this Explanation of Provisions. The three-year ECTI exception uses a transferor's allocable share of ECTI as a proxy for distributive share of effectively connected gain recognized in connection with a deemed sale described in section 864(c)(8)(B). The Treasury Department and the IRS are aware that the amount of a partner's recent allocable share of ECTI may not accurately indicate whether, and to what extent, the partner would recognize gain taxable under section 864(c)(8) and proposed § 1.864(c)(8)-1. For example, a partnership may recognize relatively little effectively connected income for several years while nonetheless holding assets with significant built-in gain that would be taxable as effectively connected gain. The three-year ECTI exception may in certain cases increase compliance and collection risks if foreign partners with limited connections to the United States and significant tax liability under section 864(c)(8) are not withheld on under section 1446(f)(1).</P>
                    <P>
                        In the interest of striking the appropriate balance between the risk of noncompliance and the potential for overwithholding, the proposed regulations adopt the three-year ECTI exception from Notice 2018-29 with the 
                        <PRTPAGE P="21202"/>
                        modifications described in this section III.B.5 of this Explanation of Provisions. The Treasury Department and the IRS continue to study whether the three-year ECTI exception is appropriate in light of the risk of noncompliance, and request comments on the utility of the rule and modifications to the rule that would reduce that risk.
                    </P>
                    <P>
                        Accordingly, proposed § 1.1446(f)-2(b)(5)(i) provides that no withholding is required if a transferee receives a certification from a transferor stating that the transferor was at all times a partner in the partnership for the immediately prior taxable year and the two taxable years that precede it and that the transferor's allocable share of ECTI for each of those taxable years was less than 10 percent of the transferor's total distributive share of the partnership's net income for that year. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(b)(5)(i)(A) and (C). In addition, a transferor must certify that, in the immediately prior taxable year and the two that preceded it, the transferor's allocable share of ECTI was less than $1 million (including ECTI allocated to certain persons related to the transferor). 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(b)(5)(i)(B). A transferor must also certify that its distributive share of income or gain that is effectively connected with the conduct of a trade or business within the United States or deductions or losses properly allocated and apportioned to that income in each of the taxable years described in proposed § 1.1446(f)-2(b)(5)(i)(A) has been reported on a Federal income tax return (filed on or before the due date (including extensions) for filing the return (and all amounts due with respect to the return are timely paid)) for each of the three preceding taxable years, if required to be filed, before the date on which the transferor furnishes the certification. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(b)(5)(i)(D). For this purpose, if the transferor is a nonresident alien individual or foreign corporation, the Federal income tax return is the transferor's Form 1040NR or Form 1120-F; if the transferor is a partnership, the Federal income tax returns are the Forms 1040NR or 1120-F of the direct or indirect partners of the transferor.
                    </P>
                    <P>
                        For purposes of this rule, the immediately prior taxable year is the transferor's most recent taxable year with or within which a taxable year of the partnership ended and for which a Schedule K-1 (Form 1065) was due or furnished (if earlier) before the date of the transfer. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(b)(5)(ii). Consistent with the three-year ECTI exception described in Notice 2018-29, a transferor does not satisfy this requirement if for any of the relevant years it did not receive Form 8805, 
                        <E T="03">Foreign Partner's Information Statement of Section 1446 Withholding Tax,</E>
                         unless the transferor was allocated an item of deduction or loss that is effectively connected with the conduct of a trade or business within the United States, in which case it is treated as having an allocable share of ECTI for that year of zero. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(b)(5)(iii).
                    </P>
                    <P>
                        When a transferor has had neither ECTI nor a net distributive share of income allocated to it in the previous three taxable years, the composition of the income the partnership allocates to the transferor does not provide any indication of the amount of effectively connected gain realized by the transferor in connection with the transfer. Accordingly, the proposed regulations also provide that a transferor does not qualify for the exception provided in proposed § 1.1446(f)-2(b)(5) if the transferor did not have a net distributive share of income allocated to it in any of its previous three taxable years. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(b)(5)(iv).
                    </P>
                    <P>
                        Section 6.03 of Notice 2018-29 provided that the three-year ECTI exception does not apply when a partnership is a transferee by reason of making a distribution. Comments noted that, particularly in tiered partnership structures, a distributing partnership may not be able to obtain the information necessary to use the deemed sale exception described in section 6.04 of Notice 2018-29, such that the partnership would be required to withhold under section 1446(f)(1) in cases in which there was relatively limited effectively connected income earned by the partnership. In response to the comments, the proposed regulations allow a distributing partnership to use this exception when it determines that the three-year ECTI exception is applicable based on its books and records, provided that it receives a representation from the transferor stating that income tax returns have been filed, and tax has been paid, for each of the relevant years for which the transferor was allocated effectively connected income (or loss). 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(b)(5)(v).
                    </P>
                    <P>Finally, proposed § 1.1446(f)-2(b)(5)(vi) provides that a transferor may not make the certification if it has actual knowledge that the information relevant to the certification that is reported by the partnership on any Form 8805 or Schedule K-1 (Form 1065) is incorrect.</P>
                    <HD SOURCE="HD3">6. Nonrecognition by Transferor</HD>
                    <P>Section 864(c)(8) and proposed § 1.864(c)(8)-1 provide that gain from the transfer of a partnership interest that is treated as effectively connected with the conduct of a trade or business within the United States is limited to gain otherwise recognized under the Code. If a nonrecognition provision of the Code applies to all of the gain realized on a transfer, withholding under section 1446(f)(1) does not apply. Accordingly, section 6.05 of Notice 2018-29 provided an exception to withholding for certain nonrecognition transactions if the transferee receives a notice from the transferor describing the application of a nonrecognition provision. This exception was based on the rules in § 1.1445-2(d)(2).</P>
                    <P>
                        Consistent with the rule provided in Notice 2018-29, the proposed regulations generally permit a transferee to rely on a certification of nonrecognition from the transferor. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(b)(6). The certification provided by the transferor must include a brief description of the transfer and the relevant law and facts relating to the application of the nonrecognition provision.
                    </P>
                    <P>If only a portion of the gain realized on the transfer is subject to a nonrecognition provision, an adjustment to the amount required to be withheld may be permitted under proposed § 1.1446(f)-2(c)(4), discussed in section III.C.4 of this Explanation of Provisions (describing the rules in proposed § 1.1446(f)-2(c)(4)(vi) for the certification of maximum tax liability that may be relied upon in these situations).</P>
                    <HD SOURCE="HD3">7. Claim of Treaty Benefits</HD>
                    <P>
                        Notice 2018-29 did not contain specific rules addressing the application of income tax treaties, instead including them in section 6.05 by adopting a modified version of § 1.1445-2(d) (providing an exception from withholding under section 1445 when the transferor certifies that it is not required to recognize gain either under a provision of the Code or under a treaty). The proposed regulations provide an exception to withholding under section 1446(f)(1) when a transferor certifies that it is not subject to tax on any gain from the transfer pursuant to an income tax treaty in effect between the United States and a foreign country. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(b)(7)(i). This exception applies only when a transferor (as opposed to owners of an interest in the transferor, including partners in a partnership that is a transferor) qualifies 
                        <PRTPAGE P="21203"/>
                        for the benefits of an income tax treaty in order to reduce the burden on a transferee of reviewing documentation from multiple persons. The certification to the transferee must include a valid Form W-8BEN,
                        <E T="03"> Certificate of Foreign Status of Beneficial Owner for United States Tax Withholding and Reporting (Individuals),</E>
                         or W-8BEN-E, 
                        <E T="03">Certificate of Status of Beneficial Owner for United States Tax Withholding and Reporting (Entities)</E>
                         (as applicable), that contains the information necessary to support the claim for treaty benefits, and the transferee must mail a copy of the certification to the IRS by the 30th day after the date of the transfer in order to rely upon it. 
                        <E T="03">Id. See also</E>
                         Form 8833, 
                        <E T="03">Treaty-Based Return Position Disclosure Under Section 6114 or 7701(b),</E>
                         and the instructions to the form regarding the requirement for the transferor to disclose a claim for treaty benefits with a return.
                    </P>
                    <P>
                        To ensure that these procedures are followed for claims involving treaty benefits, this exception is the sole method by which a transferor may claim an exception to withholding by reason of a claim of treaty benefits. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(b)(7)(iii). For claims involving transfers with respect to which treaty benefits apply to only a portion of the gain from the transfer, see section III.C.4 of this Explanation of Provisions (describing the rules in proposed § 1.1446(f)-2(c)(4)(vi) for the certification of maximum tax liability that that may be relied upon in these situations).
                    </P>
                    <HD SOURCE="HD2">C. Determining the Amount To Withhold</HD>
                    <HD SOURCE="HD3">1. In General</HD>
                    <P>
                        The proposed regulations provide certain procedures for determining the amount to withhold under section 1446(f)(1). The rules are intended to provide administrable procedures for transferees to determine the amount to withhold, and in some cases, provide procedures intended to better reflect the amount of the transferor's actual tax liability under section 864(c)(8). When applicable, these procedures generally allow the transferee to rely on certifications that it receives from the transferor (or, in certain cases, from the partnership) to determine the amount to withhold unless it has actual knowledge that the certification is incorrect or unreliable. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(c)(1). In cases in which a partnership is the transferee because it makes a distribution, it may instead rely on its books and records unless it knows, or has reason to know, that the information is incorrect or unreliable. 
                        <E T="03">Id.</E>
                    </P>
                    <HD SOURCE="HD3">2. Amount Realized</HD>
                    <HD SOURCE="HD3">i. In General</HD>
                    <P>
                        The amount required to be withheld under section 1446(f)(1) is determined by reference to the transferor's amount realized on the transfer. 
                        <E T="03">See</E>
                         section 1446(f)(1). The proposed regulations provide that the amount realized for purposes of proposed § 1.1446(f)-2 is determined under section 1001 and the regulations thereunder and section 752 and the regulations thereunder. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(c)(2)(i); 
                        <E T="03">see also</E>
                         §§ 1.752-1(h) and 1.1001-2.
                    </P>
                    <P>
                        The proposed regulations also clarify that in the case of a distribution, the amount realized is the sum of the amount of cash distributed (or to be distributed), the fair market value of property distributed (or to be distributed), and the reduction in the transferor's share of partnership liabilities. 
                        <E T="03">Id.</E>
                    </P>
                    <HD SOURCE="HD3">ii. Procedures To Determine Share of Partnership Liabilities</HD>
                    <P>Comments stated that the allocation of liabilities to a partner under section 752 is not information that normally would be available to a transferee and may be difficult for a transferor to determine as of the date of transfer. To address these issues, section 7.02 of Notice 2018-29 provided that a transferee may in certain cases rely on a certification from the transferor as to the amount of the transferor's share of partnership liabilities reported on the transferor's most recently received Schedule K-1 (Form 1065), provided that the form was for a partnership taxable year that closed no more than 10 months before the date of transfer and the transferor is not a controlling partner. Section 7.03 of Notice 2018-29 allowed a transferee to rely on a certification from the partnership that provided the transferor's share of partnership liabilities as reflected on the most recently prepared Schedule K-1 (Form 1065).</P>
                    <P>
                        The proposed regulations provide procedures similar to sections 7.02 and 7.03 of Notice 2018-29 that allow a transferee to rely on a certification from the transferor or the partnership. Proposed § 1.1446(f)-2(c)(2)(ii)(B) provides that a transferee may generally rely on a certification from a transferor that provides the amount of the transferor's share of partnership liabilities reported on the most recent Schedule K-1 (Form 1065) issued by the partnership. In response to comments stating that a transferor may not possess a Schedule K-1 (Form 1065) that satisfies the 10 month requirement in Notice 2018-29 because of the timing of the extended due date for Schedule K-1 (Form 1065), the proposed regulations provide that a transferee may generally rely on a certification if the last day of the partnership taxable year for which the Schedule K-1 (Form 1065) was provided was no more than 22 months before the date of the transfer. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(c)(2)(ii)(B). Consistent with Notice 2018-29, a transferor that is a controlling partner may not provide this certification because it will generally be able to require the partnership to provide a partnership-level certification as to the controlling partner's share of partnership liabilities. 
                        <E T="03">Id.</E>
                    </P>
                    <P>
                        Proposed § 1.1446(f)-2(c)(2)(ii)(C) allows a transferee to rely on a certification from the partnership that provides the amount of the transferor's share of partnership liabilities. However, unlike the rule in Notice 2018-29, the partnership is required to make this determination as of the determination date rather than relying on its most recently prepared Schedule K-1 (Form 1065). 
                        <E T="03">Id.</E>
                         The proposed regulations also provide a new procedure that allows a partnership that is a transferee because it makes a distribution to rely on its books and records to determine the transferor's share of partnership liabilities as of the determination date. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(c)(2)(iii).
                    </P>
                    <P>If a transferee does not use one of these determination procedures, the reduction in the transferor's share of partnership liabilities must be determined as of the date of the transfer for purposes of computing the amount realized.</P>
                    <HD SOURCE="HD3">iii. Modified Amount Realized for Foreign Partnerships</HD>
                    <P>
                        As discussed in section III.B of this Explanation of Provisions, section 1446(f)(2) and proposed § 1.1446(f)-2(b)(2) provide an exception to withholding when the transferor is not a foreign person. A transferor that is a foreign partnership may not rely on this exception even though it may have U.S. persons (which are not subject to tax under section 864(c)(8)) as its partners. To avoid overwithholding when a foreign partnership transfers its interest in a partnership, proposed § 1.1446(f)-2(c)(2)(iv) provides a procedure to limit the amount realized for withholding purposes to the portion of the amount realized that is attributable to foreign persons. For this purpose, the portion of the amount realized attributable to a direct or indirect partner is determined based on the percentage of gain allocable to that partner. Any partner that does not provide a valid 
                        <PRTPAGE P="21204"/>
                        certification of non-foreign status (including a Form W-9) is treated as a foreign person for this purpose.
                    </P>
                    <P>
                        To make the certification for a modified amount realized, the transferor must provide to the transferee a Form W-8IMY,
                        <E T="03"> Certificate of Foreign Intermediary, Foreign Flow-Through Entity, or Certain U.S. Branches for United States Tax Withholding and Reporting,</E>
                         that includes a certification of non-foreign status for each partner that is treated as a U.S. person. It must also include a withholding statement that provides the percentage of gain allocable to each direct or indirect partner and that indicates whether that person is a U.S. person or is treated as a foreign person.
                    </P>
                    <HD SOURCE="HD3">3. Lack of Money or Property or Lack of Knowledge Regarding Liabilities</HD>
                    <P>
                        As described in section 8 of Notice 2018-29, in some cases, a reduction in the transferor's share of partnership liabilities may cause the amount otherwise required to be withheld to exceed the cash or other property that the transferee actually pays to the transferor. In other cases, a transferee may have not received, or cannot rely upon, a certification regarding the transferor's share of partnership liabilities, and may not otherwise know the transferor's share of partnership liabilities. In these situations, the proposed regulations generally provide that the amount required to be withheld is equal to the amount realized determined without regard to the decrease in the transferor's share of partnership liabilities. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(c)(3).
                    </P>
                    <HD SOURCE="HD3">4. Certification of Maximum Tax Liability</HD>
                    <P>
                        To more closely align the amount to withhold with the transferor's tax liability under section 864(c)(8), the proposed regulations provide a procedure to determine the amount to withhold that is intended to estimate the amount of tax the transferor is required to pay under section 864(c)(8). 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(c)(4).
                    </P>
                    <P>
                        For this procedure to apply, a transferee must receive a certification from the transferor containing certain information relating to the transferor and the transfer. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(c)(4)(iii). One of the requirements for this certification is for the transferor to identify the amount of outside capital gain and outside ordinary gain that would be treated as effectively connected gain on the determination date. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(c)(4)(iii)(E). Further, to provide this certification, the transferor must represent that it has obtained a statement from the partnership that includes, among other things, information relating to the transferor's distributive share of effectively connected gain in connection with a deemed sale described in section 864(c)(8)(B) as of the determination date. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(c)(4)(iii)(G).
                    </P>
                    <P>
                        When a transferor provides a transferee this information, proposed § 1.1446(f)-2(c)(4)(i) allows the transferee to withhold based on the transferor's maximum tax liability on the transfer. The transferor's maximum tax liability is the amount of the transferor's effectively connected gain multiplied by the applicable percentage. 
                        <E T="03">See</E>
                         section 1446(b) and § 1.1446-3(a)(2). The applicable percentage applies the highest rate of tax for each particular type of income or gain allocable to a foreign person. 
                        <E T="03">Id.</E>
                    </P>
                    <P>
                        Special rules apply for a transfer in which only a portion of the gain is subject to tax under section 864(c)(8) because a nonrecognition provision of the Code or an income tax treaty in effect between the United States and a foreign country applies (for example, when the partnership carries on one trade or business through a U.S. permanent establishment, and another trade or business that is not carried on through a U.S. permanent establishment). 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(c)(4)(v) and (vi). These rules provide that the transferor must, in addition to providing the maximum tax liability certification, comply with the procedural requirements that would otherwise apply when claiming a full exception to withholding based on a nonrecognition provision or treaty benefits.
                    </P>
                    <HD SOURCE="HD2">D. Reporting and Paying Withheld Amounts</HD>
                    <HD SOURCE="HD3">1. In General</HD>
                    <P>
                        A transferee required to withhold must report and pay any tax withheld by the 20th day after the date of the transfer. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(d)(1). To report and pay the amount withheld, the proposed regulations direct the transferee to use Forms 8288, 
                        <E T="03">U.S. Withholding Tax Return for Dispositions by Foreign Persons of U.S. Real Property Interests,</E>
                         and 8288-A, 
                        <E T="03">Statement of Withholding on Dispositions by Foreign Persons of U.S. Real Property Interests.</E>
                         The IRS will stamp a valid Form 8288-A to show receipt and mail a copy to the transferor.
                    </P>
                    <HD SOURCE="HD3">2. Transferee's Obligation To Certify the Amount Withheld to the Partnership</HD>
                    <P>
                        As discussed in section IV of this Explanation of Provisions, a partnership must withhold on distributions to a transferee under section 1446(f)(4) to the extent the transferee fails to properly withhold under section 1446(f)(1) and proposed § 1.1446(f)-2(a). 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-3. In order for the partnership to determine whether it must withhold under these rules, proposed § 1.1446(f)-2(d)(2) requires a transferee to timely furnish certain information regarding its compliance with section 1446(f)(1) to the partnership.
                    </P>
                    <P>Specifically, proposed § 1.1446(f)-2(d)(2) requires a transferee (other than a partnership that is a transferee because it makes a distribution) to furnish, no later than 10 days after the transfer, a certification to the partnership that either includes a copy of the Form 8288-A that it files with the IRS, or states the amount realized on the transfer and any amount withheld by the transferee. The certification must also include any underlying certifications that the transferee has relied upon that claim an exception or adjustment to withholding. As discussed in section IV.B of this Explanation of Provisions, the partnership must conduct its own review of the certification provided by the transferee, including any underlying certifications. Therefore, a transferee that has relied on a certification claiming an exception or adjustment to withholding may want to ensure that the partnership has determined the certification to be correct and reliable before the due date for payment of any withheld amounts to the IRS.</P>
                    <HD SOURCE="HD2">E. Effect of Withholding on Transferor</HD>
                    <P>
                        Proposed § 1.1446(f)-2(e) states that a foreign person must file a U.S. tax return and pay any tax due with respect to a transfer that is subject to section 864(c)(8) regardless of whether there is withholding under section 1446(f)(1) and proposed § 1.1446(f)-2. To claim a credit under section 33, a transferor that is an individual or corporation must attach to its return the stamped copy of Form 8288-A, as referenced in section III.D of this Explanation of Provisions. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-2(e)(2)(i). If a stamped copy of Form 8288-A has not been provided to the transferor by the IRS, proposed § 1.1446(f)-2(e)(3) provides that a transferor may establish the amount of tax withheld by furnishing substantial evidence of the amount. For a discussion of the rule regarding a transferor that is a foreign 
                        <PRTPAGE P="21205"/>
                        partnership claiming a credit for withholding under section 1446(f)(1), see section II.E of this Explanation of Provisions.
                    </P>
                    <HD SOURCE="HD1">IV. Partnership's Requirement To Withhold Under Section 1446(f)(4) on Distributions to Transferee</HD>
                    <HD SOURCE="HD2">A. In General</HD>
                    <P>Proposed § 1.1446(f)-3 provides rules under section 1446(f)(4) that would implement the partnership's requirement to withhold on distributions to a transferee on any amount that the transferee failed to properly withhold under section 1446(f)(1), plus any interest on this amount. The rules, when made applicable as final rules, would end the suspension of section 1446(f)(4) withholding provided in section 11 of Notice 2018-29.</P>
                    <HD SOURCE="HD2">B. Requirement To Withhold</HD>
                    <P>
                        The proposed regulations provide that, if a transferee fails to withhold any amount required to be withheld under proposed § 1.1446(f)-2 in connection with the transfer of a partnership interest, the partnership must withhold from any distributions made to the transferee in accordance with the rules in proposed § 1.1446(f)-3. Under the general rule, a partnership determines whether a transferee has withheld the amount required to be withheld under proposed § 1.1446(f)-2 by relying on the certification described in proposed § 1.1446(f)-2(d)(2) that it receives from the transferee. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-3(a)(1). The partnership may rely on this certification unless it knows, or has reason to know, that the certification is incorrect or unreliable. 
                        <E T="03">Id.</E>
                         Therefore, the partnership must review the certification received from the transferee, which includes any underlying certifications that the transferee relied on to reduce or eliminate withholding. Because the partnership may have information that may not be available to the transferee (for example, information in its books and records), a partnership may know, or have reason to know, that an underlying certification is incorrect or unreliable even though the transferee properly relied on the certification. In this case, the partnership would be required to withhold on the transferee under section 1446(f)(4) to the extent required in proposed § 1.1446(f)-3.
                    </P>
                    <P>
                        If the partnership timely receives (within 10 days from the transfer), and may rely on, a certification from the transferee stating that an exception to withholding applies or establishing that the transferee has withheld the amount required to be withheld under proposed § 1.1446(f)-2, then the partnership is not required to withhold under the general rule in proposed § 1.1446(f)-3(a)(1). 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-3(b)(1). For this purpose, the amount required to be withheld may take into account any adjustment procedures under § 1.1446(f)-2(c) (for which any documents, including underlying certifications, are attached to the certification provided by the transferee). The proposed regulations thus reduce the burden imposed by section 1446(f)(4) by allowing transferees and partnerships to rely on the information produced under the regulations implementing section 1446(f)(1).
                    </P>
                    <P>
                        The proposed regulations provide an additional rule that allows the IRS, in limited circumstances, to require a partnership to withhold under section 1446(f)(4) when the IRS notifies the partnership that it has determined that the transferee has provided incorrect information on the certification described in proposed § 1.1446(f)-2(d)(2) regarding the amount realized or the amount withheld, or that the transferee failed to pay the amounts reported as withheld to the IRS. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-3(a)(2). This rule is meant to induce the transferee to properly determine the amount realized on transfer (in accordance with the rules in proposed § 1.1446(f)-2(c)(2)), and to correctly report to the partnership the amount of tax withheld and paid to the IRS.
                    </P>
                    <P>
                        Under the proposed regulations, withholding under section 1446(f)(4) does not apply when a partnership is a transferee because it makes a distribution. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-3(b)(3). Section 1446(f)(4) imposes a withholding obligation on a secondary party, the partnership, when the transferee fails to withhold under section 1446(f)(1). When the partnership is the transferee because it made a distribution and failed to withhold under section 1446(f)(1) and proposed § 1.1446(f)-2, imposing a section 1446(f)(4) withholding obligation on it does not provide an additional party to ensure the 1446(f) liability is paid. Furthermore, the partnership remains liable for its failure to withhold in its capacity as a transferee. 
                        <E T="03">See</E>
                         section VI.A of this Explanation of Provisions.
                    </P>
                    <P>
                        A publicly traded partnership generally is also not required to withhold on distributions made to a transferee under section 1446(f)(4). 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-3(b)(2)(i). As described in section V of this Explanation of Provisions, it would be administratively difficult for a publicly traded partnership to determine when a transfer of its interest has occurred, and whether the correct amount has been withheld under section 1446(f)(1). However, the proposed regulations do require a publicly traded partnership to withhold under section 1446(f)(4) in certain limited instances. Specifically, a publicly traded partnership may publish a qualified notice that states that withholding under section 1446(f)(1) does not apply with respect to a distribution. 
                        <E T="03">See</E>
                         section V.B.2 and 3 of this Explanation of Provisions. To ensure that publicly traded partnerships exercise due diligence when publishing these qualified notices, proposed § 1.1446(f)-3(b)(2)(ii) provides that the exception from section 1446(f)(4) withholding applicable to publicly traded partnerships does not apply if a publicly traded partnership determines (including by reason of having received notification from the IRS) that it has published a qualified notice that falsely states that an exemption applied. When a publicly traded partnership makes this determination, it must withhold on distributions to the transferees an amount equal to the amount that any brokers failed to withhold under proposed § 1.1446(f)-4 due to reliance on the qualified notice, plus interest.
                    </P>
                    <HD SOURCE="HD2">C. Withholding Rules</HD>
                    <P>
                        A partnership that does not receive, or cannot rely on, a timely certification from a transferee stating that an exception to withholding applies or that the proper amount has been withheld must begin to withhold under the general rule on distributions made to the transferee on the later of the date that is 30 days after the transfer or the date that is 15 days after the partnership acquires actual knowledge of the transfer. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-3(c)(1)(i).
                    </P>
                    <P>
                        The partnership must withhold on the entire amount of each distribution made to the transferee until it may rely on a certification from the transferee that states that an exception to withholding applies or that provides the information necessary to determine the amount required to be withheld. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-3(c)(1)(ii). The partnership may rely on this certification to determine its withholding obligation regardless of whether it is provided within the time prescribed in proposed § 1.1446(f)-2(d)(2). If the partnership has not already satisfied the amount required to be withheld, as determined from the certification from the transferee, it must continue to withhold on distributions to the transferee until it has done so. 
                        <E T="03">Id.</E>
                         However, the partnership may stop withholding if the transferee disposes of all of its interest 
                        <PRTPAGE P="21206"/>
                        in the partnership, unless the partnership has actual knowledge that any successor to the transferee is related to the transferee or the transferor from which the transferee acquired the interest. 
                        <E T="03">Id.</E>
                    </P>
                    <P>
                        The amount required to be withheld under proposed § 1.1446(f)-3(a)(1), as determined from the certification provided by the transferee, is a tax equal to 10 percent of the amount realized on the transfer, reduced by any amount already withheld by the transferee, plus any computed interest. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-3(c)(2)(i). The proposed regulations provide that a partnership that is required to withhold under proposed § 1.1446(f)-3(a)(1) may not take into account any adjustment procedures that would otherwise affect the amount required to be withheld under proposed § 1.1446(f)-2(c)(2)(i). 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-3(c)(2)(i)(A). Thus, for example, a partnership may not reduce the amount that it is required to withhold under the procedures described in proposed § 1.1446(f)-2(c)(4) (adjusting the amount subject to withholding based on a transferor's maximum tax liability). The Treasury Department and the IRS have determined that it would be inappropriate to permit adjustments that may reduce the amount required to be withheld under section 1446(f)(4). Withholding on distributions to transferees under section 1446(f)(4) applies only after the transferee has either failed to properly withhold under section 1446(f)(1) or has not complied with the applicable procedural requirements in the proposed regulations. Accordingly, permitting adjustments to the amount a partnership is required to withhold under section 1446(f)(4) would reduce transferees' incentive to comply with their obligations under section 1446(f)(1) while potentially increasing the partnership's administrative burden associated with that withholding.
                    </P>
                    <P>Proposed § 1.1446(f)-3(c)(2)(ii) provides rules for the partnership to compute interest on the amount that the transferee failed to withhold. Proposed § 1.1446(f)-3(c)(3) provides that any amount required to be withheld on a distribution under any other withholding provision in the Code is not required to be withheld under section 1446(f)(4). For example, if a partnership is required to withhold $30 under section 1441 on a $100 distribution, the maximum amount required to be withheld on that distribution under section 1446(f)(4) is $70.</P>
                    <P>
                        Proposed § 1.1446(f)-3(d) provides that a partnership required to withhold under section 1446(f)(4) must report and pay the tax withheld using Forms 8288, 
                        <E T="03">U.S. Withholding Tax Return for Dispositions by Foreign Persons of U.S. Real Property Interests,</E>
                         and 8288-C, 
                        <E T="03">Statement of Withholding Under Section 1446(f)(4) for Withholding on Dispositions by Foreign Persons of Partnership Interests,</E>
                         as provided in forms, instructions, or other guidance.
                    </P>
                    <HD SOURCE="HD2">D. Effect of Withholding on the Transferor and Transferee</HD>
                    <P>
                        The withholding of tax under section 1446(f)(4) does not relieve a nonresident alien individual or foreign corporation subject to tax under section 864(c)(8) from filing a U.S. income tax return with respect to the transfer and paying any tax due with the return. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-3(e)(1). Because this tax is withheld from the transferee rather than from the transferor, the transferor is not allowed a credit under section 33. 
                        <E T="03">Id.</E>
                         However, the proposed regulations clarify that tax will not be collected from the transferor to the extent it has already been collected from another person under these rules. 
                        <E T="03">See</E>
                         section VI.A of this Explanation of Provisions. Therefore, the transferor will not be required to pay tax to the extent the tax (but not any portion treated as interest) has been paid through withholding on the transferee.
                    </P>
                    <P>
                        A transferee remains liable under section 1446(f)(1) even when the partnership is required to withhold under section 1446(f)(4). However, the transferee is treated as satisfying this withholding tax liability under section 1446(f)(1) to the extent that it is withheld upon under section 1446(f)(4). 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-3(e)(2). Any amount withheld that is treated as interest is not treated as satisfying the transferee's liability under section 1446(f)(1), but that amount will instead be treated as interest paid by the transferee with respect to its section 1446(f)(1) liability. 
                        <E T="03">Id.</E>
                         Under the proposed regulations, if the amount of tax withheld from the transferee exceeds its liability under section 1446(f)(1), only the partnership may claim a refund on behalf of the transferee for the excess amount. 
                        <E T="03">Id.</E>
                         This rule is meant to make the refund process more administrable by having the partnership act on behalf of each of its transferees for purposes of claiming any excess amounts withheld under section 1446(f)(4). The Treasury Department and the IRS anticipate that partnerships and transferees will make arrangements by contract so that the transferees may be reimbursed for amounts refunded to the partnership. The Treasury Department and the IRS request comments on this issue.
                    </P>
                    <HD SOURCE="HD1">V. Withholding on the Transfer of a Publicly Traded Partnership Interest by a Foreign Person</HD>
                    <P>The proposed regulations provide rules for withholding and reporting on the transfer of an interest in a publicly traded partnership if the interest is publicly traded on an established securities market or is readily tradable on a secondary market or the substantial equivalent thereof (such interests, “PTP interests”). The rules, when made applicable as final rules, would end the suspension of section 1446(f)(1) withholding on the disposition of PTP interests provided in Notice 2018-08.</P>
                    <HD SOURCE="HD2">A. In General</HD>
                    <P>
                        A transfer of a PTP interest raises unique issues for withholding under section 1446(f). For example, when a transfer of a PTP interest is effected through one or more brokers, the transferee will generally not know the identity of the transferor. Accordingly, the Conference Report for the Act acknowledged that transfers involving PTP interests could require withholding rules different from those that apply to transfers involving non-PTP interests. 
                        <E T="03">See</E>
                         Conference Report on H.R. 1, Tax Cuts and Jobs Act, H. Rep. No. 115-466, at 511 (“[T]he Secretary may provide guidance permitting a broker, as agent of the transferee, to deduct and withhold the tax . . . such guidance may provide that if an interest in a publicly traded partnership is sold by a foreign partner through a broker, the broker may deduct and withhold the 10-percent tax on behalf of the transferee.”).
                    </P>
                    <P>
                        Consistent with the Conference Report, proposed § 1.1446(f)-4(a)(1) provides that if a transfer of a PTP interest is effected through one or more brokers, the transferee is not required to withhold, and the withholding obligation is instead imposed on certain brokers involved with the transfer. Generally, the proposed regulations define a broker to include any person, foreign or domestic, that in the ordinary course of a trade or business during the calendar year stands ready to effect sales made by others, and that, in connection with a transfer of a PTP interest, receives all or a portion of the amount realized on behalf of the transferor. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-1(b)(1). For example, when a transfer of a PTP interest occurs through a cash on delivery account, a delivery versus payment account, or other similar account or transaction, this definition would include a broker that receives an amount realized from the sale against delivery of the PTP interest and any other broker that receives an amount 
                        <PRTPAGE P="21207"/>
                        realized from that broker. Therefore, the withholding obligation under proposed § 1.1446(f)-4 is generally limited to brokers that receive proceeds from the sale and act on behalf of the transferor. The definition of broker also includes any clearing organization that effects a transfer of a PTP interest on behalf of the transferor. While comments have stated that clearing organizations may not have the capability to complete the withholding required under section 1446(f), the Treasury Department and the IRS anticipate that clearing organizations will make arrangements to ensure that, when effecting the transfer of a PTP interest on behalf of foreign brokers, they act on behalf of brokers that assume withholding responsibility when clearing sales of PTP interests (such as a qualified intermediary (“QI”)).
                    </P>
                    <P>If a transfer of a PTP interest is effected through multiple brokers, proposed § 1.1446(f)-4(a)(2) provides rules that specify which broker or brokers have a withholding obligation. Under proposed § 1.1446(f)-4(a)(2)(i), a broker that pays the amount realized to a foreign broker is required to withhold unless the foreign broker is either a U.S branch treated as a U.S. person or a QI that assumes primary withholding responsibility for the payment. Consistent with this rule, the Treasury Department and the IRS intend to modify the QI agreement provided in Revenue Procedure 2017-15, 2017-3 I.R.B. 437, to allow QIs to assume primary withholding responsibility on the amount realized. Proposed § 1.1446(f)-4(a)(2)(ii) provides an additional rule requiring the broker that effects a transfer for the transferor as its customer to satisfy the withholding obligation. This rule ensures that withholding will be completed on payment of the amount realized to the transferor when another broker has not already satisfied the withholding.</P>
                    <P>To avoid withholding by multiple brokers, proposed § 1.1446(f)-4(a)(2)(iii) provides the general rule that a broker is not required to withhold when it knows that the withholding obligation has been satisfied by another broker. Proposed § 1.1446(f)-4(a)(2)(iv) provides that a broker must treat another broker as a foreign person unless it obtains documentation (including a certification of non-foreign status) establishing that the other broker is a U.S. person.</P>
                    <P>If the transfer of a PTP interest is not effected through one or more brokers, then proposed § 1.1446(f)-4 does not apply, and the general rules of section 1446(f)(1) and proposed § 1.1446(f)-2 apply. A transfer that is effected through a broker includes a distribution with respect to a PTP interest held through an account with a broker.</P>
                    <HD SOURCE="HD2">B. Exceptions to Withholding</HD>
                    <P>The proposed regulations provide five exceptions to withholding that apply to the transfer of a PTP interest. The exceptions are intended to both reduce the compliance burden placed on brokers and provide rules that are administrable.</P>
                    <HD SOURCE="HD3">1. Certification of Non-Foreign Status</HD>
                    <P>
                        As mentioned in section III.B.2 of this Explanation of Provisions, withholding under section 1446(f)(1) is limited to transfers by foreign partners. Accordingly, a broker is not required to withhold to the extent that it relies on a certification of non-foreign status that it receives from the transferor that claims an exception to withholding. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-4(b)(2). For purposes of proposed § 1.1446(f)-4, a certification of non-foreign status means a Form W-9, or valid substitute form, that meets the requirements of § 1.1441-1(d)(2). A broker may rely on a valid Form W-9 that it already possesses, and in certain cases, may instead rely on a certification that it receives from another broker that states the TIN and status of the transferor when that other broker acts as an agent for the transferor and possesses the Form W-9 (for example, from an introducing broker). A broker will not qualify for the exception provided in proposed § 1.1446(f)-4(b)(2) if it has actual knowledge that the certification is incorrect or unreliable.
                    </P>
                    <HD SOURCE="HD3">2. 10-Percent Exception</HD>
                    <P>The proposed regulations include an exception to withholding that may apply if, on a deemed sale of the assets of the publicly traded partnership the interest in which is transferred, the amount of effectively connected gain would be less than 10 percent of the total gain. Specifically, proposed § 1.1446(f)-4(b)(3) provides that a broker is not required to withhold under proposed § 1.1446(f)-4 if it properly relies on a qualified notice stating that the 10-percent exception applies.</P>
                    <P>
                        The 10-percent exception applies if a hypothetical sale by the publicly traded partnership of all of its assets at fair market value on a specified date would result in an amount of gain effectively connected with the conduct of a trade or business within the United States that is less than 10 percent of the total gain. The specified date must be a date designated by the publicly traded partnership that is within the 92-day period ending on the date that it posts a qualified notice. Unlike the similar exception described in section III.B.4 of this Explanation of Provisions that applies to transfers of non-PTP interests, this rule requires a publicly traded partnership to designate a date for this purpose that generally occurs within the most recent calendar quarter. 
                        <E T="03">Cf.</E>
                         proposed § 1.1446(f)-2(b)(4) (permitting the deemed sale computation to occur on a determination date, which would allow the deemed sale date to be determined as of the first day of a partnership's taxable year in which the transfer occurred in certain cases). The Treasury Department and the IRS have determined that it is appropriate to limit the availability of this exception to cases in which a publicly traded partnership has designated a deemed sale date occurring within the most recent calendar quarter because publicly traded partnerships are in a better position to determine the value of their assets, and in some cases determine the basis of their assets, on a quarterly basis. The proposed regulations limit reliance on a qualified notice depending on its date of posting. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-4(b)(3)(iii).
                    </P>
                    <P>For a discussion of rules regarding when a publicly traded partnership may be liable under section 1446(f)(4) because it falsely states on a qualified notice that this exception applies, see section IV.B of this Explanation of Provisions. For a discussion of the proposed changes to existing qualified notice rules, see section VII of this Explanation of Provisions.</P>
                    <HD SOURCE="HD3">3. Qualified Current Income Distributions</HD>
                    <P>As discussed in section III.B.3 of this Explanation of Provisions, the proposed regulations allow a transferor of a non-PTP interest to provide a certification stating that the transferor would not realize any gain on the transfer. Because it would be administratively difficult for a broker to timely obtain this type of certification from the transferor of a PTP interest, and difficult for the transferor to determine its basis in the PTP interest, the proposed regulations do not provide a similar exception for transfers of PTP interests.</P>
                    <P>
                        The Treasury Department and the IRS have determined, however, that it would be appropriate to eliminate withholding under section 1446(f)(1) on distributions (the full amount of which is generally treated as an amount realized under the proposed regulations) by a publicly traded partnership when it is likely that the transferor would realize no gain. In general, under section 705(a)(1), a partner's basis in its interest is increased by its distributive share of income for the taxable year, such that a distribution by the partnership not in 
                        <PRTPAGE P="21208"/>
                        excess of that income generally does not result in the recognition of gain under section 731(a)(1). Accordingly, the proposed regulations provide that when a qualified notice posted by a publicly traded partnership indicates that the distribution does not exceed the net income the partnership earned since the record date of the partnership's last distribution, no withholding is required with respect to the distribution. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-4(b)(4).
                    </P>
                    <HD SOURCE="HD3">4. Proceeds Subject to Withholding Under Section 3406</HD>
                    <P>A broker may also be required to withhold on gross proceeds from the transfer of a PTP interest under section 3406 when a payment is treated as being made to a non-exempt U.S. recipient. To prevent withholding twice on the same payment, proposed § 1.1446(f)-4(b)(5) provides an exception to withholding under section 1446(f)(1) if the amount realized is subject to withholding under section 3406.</P>
                    <HD SOURCE="HD3">5. Claim of Treaty Benefits</HD>
                    <P>
                        The proposed regulations provide an exception similar to the one described in section III.B.6 of this Explanation of Provisions when a transferor states that it is not subject to tax on any gain from the transfer pursuant to an income tax treaty in effect between the United States and a foreign country. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-4(b)(6). The exception also requires the transferor to furnish a valid Form W-8 with the information necessary to support the claim. 
                        <E T="03">Id.</E>
                         Unlike the exception for non-PTP interests, a broker is not required to mail the certification to the IRS because under the proposed regulations brokers are required to file a Form 1042-S, 
                        <E T="03">Foreign Person's U.S. Source Income Subject to Withholding,</E>
                         to report a transfer of a PTP interest that includes information about the claim of treaty benefits. 
                        <E T="03">See</E>
                         section V.D of this Explanation of Provisions for reporting requirements with respect to transfers of PTP interests.
                    </P>
                    <HD SOURCE="HD2">C. Determining the Amount To Withhold</HD>
                    <HD SOURCE="HD3">1. Amount Realized</HD>
                    <HD SOURCE="HD3">i. In General</HD>
                    <P>A broker that is required to withhold under proposed § 1.1446(f)-4(a) must withhold 10 percent of the amount realized on the transfer of a PTP interest. As explained in section III.C.2 of this Explanation of Provisions, a reduction in a partner's share of partnership liabilities is treated as an amount realized under proposed § 1.1446(f)-2(c). However, because of the difficulties involved with requiring a broker to timely determine a transferor's share of partnership liabilities, proposed § 1.1446(f)-4(c)(2)(i) provides a special rule that treats the amount realized on the transfer of a PTP interest as the amount of gross proceeds (as defined in § 1.6045-1(d)(5)) paid or credited to the customer or another broker (as applicable). If a publicly traded partnership makes a distribution to a partner, the amount realized is the amount of cash distributed (or to be distributed) and the fair market value of property distributed (or to be distributed).</P>
                    <HD SOURCE="HD3">ii. Modified Amount Realized for Foreign Partnerships</HD>
                    <P>
                        Consistent with the rule described in section III.C.2.iii of this Explanation of Provisions that applies to transfers of non-PTP interests, the proposed regulations include a rule that allows brokers to rely on a certification from a foreign partnership to modify the amount realized based on the extent to which the amount realized is attributable to persons who are (or are presumed to be) foreign persons. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-4(c)(2)(ii).
                    </P>
                    <HD SOURCE="HD2">D. Reporting and Paying Withheld Amounts</HD>
                    <P>
                        A broker required to withhold under § 1.1446(f)-4 must pay the withheld tax pursuant to the deposit rules in § 1.6302-2, and report the withholding on Forms 1042, 
                        <E T="03">Annual Withholding Tax Return for U.S. Source Income of Foreign Persons,</E>
                         and 1042-S pursuant to the procedures in § 1.1461-1(b) and (c). The proposed regulations treat as a recipient for Form 1042-S reporting purposes a partner that receives an amount realized from a transfer of a PTP interest subject to § 1.1446(f)-4. 
                        <E T="03">See</E>
                         proposed § 1.1461-1(c)(1)(ii)(A)(8). This rule also clarifies that a foreign partnership is treated as a recipient for this purpose to ensure that the foreign partnership receives a Form 1042-S that it may use to claim credit for any withholding under proposed § 1.1446(f)-4 against its tax liability under section 1446(a). 
                        <E T="03">See</E>
                         section II.E of this Explanation of Provisions for discussion of the general coordination rule.
                    </P>
                    <P>
                        To implement the reporting requirements, the proposed regulations add to the list of amounts subject to reporting on Form 1042-S an amount realized on the transfer of a PTP interest subject to § 1.1446(f)-4 (with limited exceptions). 
                        <E T="03">See</E>
                         proposed § 1.1461-1(c)(2). The proposed regulations also add to this list any distributions of effectively connected income by a publicly traded partnership subject to § 1.1446-4 to clarify that these amounts are reportable on Form 1042-S. 
                        <E T="03">Id.</E>
                    </P>
                    <HD SOURCE="HD2">E. Effect of Withholding on Transferor</HD>
                    <P>
                        As mentioned in section III.E of this Explanation of Provisions, the proposed regulations neither relieve a transferor of its substantive tax liability under section 864(c)(8), nor relieve a transferor subject to section 864(c)(8) from its filing obligation. 
                        <E T="03">See</E>
                         proposed § 1.1446(f)-4(e)(1). However, a transferor is allowed a credit under section 33 for the amount withheld under section 1446(f)(1) and proposed § 1.1446(f)-4. 
                        <E T="03">Id.</E>
                         To claim the credit, the transferor must attach to its return a copy of the Form 1042-S that includes the transferor's TIN. 
                        <E T="03">Id.</E>
                         For a discussion of the rules regarding a transferor that is a foreign partnership claiming a credit for withholding under section 1446(f)(1), see section II.E of this Explanation of Provisions.
                    </P>
                    <HD SOURCE="HD2">F. Procedures To Adjust Overwithholding</HD>
                    <P>Section 1.1461-2(a) allows a withholding agent that overwithheld under chapter 3 of the Code, and made a deposit of tax as provided in § 1.6302-2(a), to adjust the overwithheld amount using either a reimbursement or a set-off procedure. Because these rules are meant to allow withholding agents to adjust overwithholding for any deposited amounts that are reportable on Forms 1042 and 1042-S, the proposed regulations modify § 1.1461-2(a) to allow use of the adjustment procedures for amounts withheld by a broker pursuant to proposed § 1.1446(f)-4 (which are reported on Forms 1042 and 1042-S, as noted in section V.D. of this Explanation of Provisions).</P>
                    <HD SOURCE="HD2">G. Procedures To Adjust Underwithholding</HD>
                    <P>
                        In general, § 1.1461-2(b) allows a withholding agent that underwithheld on a beneficial owner under chapter 3 of the Code to withhold from future payments made to the beneficial owner, or satisfy the tax from property or additional contributions of the beneficial owner, before the earlier of the due date for filing Form 1042 or the date on which the form is actually filed. The proposed regulations amend this provision to allow the use of this procedure by brokers that underwithheld under proposed § 1.1446(f)-4 on the transfer of a PTP interest.
                        <PRTPAGE P="21209"/>
                    </P>
                    <HD SOURCE="HD2">H. Refunds and Credits</HD>
                    <P>
                        Section 1.1464-1 generally provides that if an overpayment of tax has actually been withheld from the beneficial owner of the income, any refund or credit will be made to that beneficial owner. If, however, the tax was not withheld at source, but was instead paid by the withholding agent, the refund or credit will be made to the withholding agent. The proposed regulations clarify that these rules apply for purposes of section 1446(f). 
                        <E T="03">See</E>
                         proposed § 1.1464-1(a).
                    </P>
                    <HD SOURCE="HD1">VI. Liability for Failure To Withhold</HD>
                    <HD SOURCE="HD2">A. In General</HD>
                    <P>Proposed § 1.1446(f)-5(a) provides that every person required to deduct and withhold tax under section 1446(f), including under proposed §§ 1.1446(f)-2 through 1.1446(f)-4, but that fails to do so is liable under section 1461. If the tax required to be withheld is paid by another person required to withhold, or by the nonresident alien individual or foreign corporation subject to tax under section 864(c)(8), section 1463 and the proposed regulations clarify that the tax will only be collected once. However, the satisfaction of this liability does not relieve a person that failed to withhold under section 1446(f) from any interest, penalties, or additions to tax that would otherwise apply. The proposed regulations also provide that a partnership that fails to withhold under proposed § 1.1446(f)-3 is liable under section 1461 only for the amount of tax that it failed to withhold, and not any interest computed under § 1.1446(f)-3(c)(2)(ii). This rule ensures that interest will be computed and assessed only once with respect to the same underlying tax liability.</P>
                    <HD SOURCE="HD2">B. Liability of Agents</HD>
                    <P>Proposed § 1.1446(f)-5(b) provides rules for the liability of agents, which generally require an agent of a transferor or transferee to notify the transferee (or other person required to withhold) if it has knowledge that a certification furnished to that person is false. A person that receives notice from an agent may not rely on the certification to apply an exception to withholding or for determining the amount to withhold. Proposed § 1.1446(f)-5(b)(2) provides procedural rules regarding the timing and content of the notice, and requires the agent to furnish a copy of the notice to the IRS. An agent that fails to provide the required notice is liable for the tax that the person that should have received the notice would have been required to withhold under section 1446(f). However, under proposed § 1.1446(f)-5(b)(4), this liability is limited to the amount of compensation that the agent derives from the transaction (and any civil or criminal penalties that may apply). The proposed regulations clarify that brokers required to withhold under § 1.1446(f)-4 are not treated as agents for purposes of this rule, and are instead liable for any failure to withhold under the rules described in section V of this Explanation of Provisions.</P>
                    <HD SOURCE="HD1">VII. Amendments to Existing Section 1446 Regulations Relating to Distributions by Publicly Traded Partnerships</HD>
                    <P>In response to comments received outside the context of section 1446(f), the proposed regulations also contain changes to the existing qualified notice rules that apply to distributions that publicly traded partnerships make to foreign partners. The Treasury Department and the IRS are aware that in certain cases nominees receive notices of distribution from publicly traded partnerships that do not provide detailed information regarding the amounts of income comprising the distribution as specified in § 1.1446-4(f)(3) (such as amounts described in section 1441 or section 1442 or subject to withholding under section 1446). The term “qualified notice” under § 1.1446-4(b)(4) is currently defined by reference to the reporting requirements of 17 CFR 240.10b-17(b)(1) or (3), which do not include a requirement to report information regarding the types of income comprising the distribution. Unless a notice provides that information, however, a nominee will not have the information necessary to apply the ordering rule of § 1.1446-4(f)(3) to the distribution for purposes of determining the amount required to be withheld.</P>
                    <P>The proposed regulations make two changes to resolve this issue. First, proposed § 1.1446-4(b)(4) revises the method for a publicly traded partnership to provide a nominee a qualified notice by requiring that the notice be posted in a readily accessible format in an area of the primary public website of the publicly traded partnership that is dedicated to this purpose. Second, proposed § 1.1446-4(d) creates a default withholding rule subjecting gross distributions to the higher of the withholding percentage required under sections 1441 and 1442 or the applicable percentage under section 1446(b)(2), unless a qualified notice provides the nominee sufficient detail to determine the types of income distributed and the appropriate withholding rates to apply. Thus, if a publicly traded partnership is unable to determine the makeup of a distribution when it is made, the nominee must withhold at the highest applicable rate.</P>
                    <P>The proposed regulations also expand the definition of a nominee for withholding under § 1.1446-4 to include certain foreign persons that agree to assume primary withholding responsibility. Therefore, a QI or a U.S. branch treated as a U.S. person that assumes primary withholding responsibility for a distribution by a publicly traded partnership under proposed § 1.1446-4(b)(3) can act as a nominee with respect to the distribution. The Treasury Department and the IRS intend to modify the QI agreement provided in Revenue Procedure 2017-15 to allow QIs to assume primary withholding responsibility for distributions by publicly traded partnerships under section 1446(a).</P>
                    <P>
                        The proposed regulations also make changes to the qualified notice rules applicable to publicly traded partnerships, publicly traded trusts, and real estate investment trusts (“REITs”) under section 1445 that conform to proposed § 1.1446-4(b)(4) so that those rules also provide more readily available information for nominees. 
                        <E T="03">See</E>
                         proposed § 1.1445-8(f).
                    </P>
                    <P>
                        As discussed in sections V.F and V.G of this Explanation of Provisions, the proposed regulations modify § 1.1461-2(a) and (b) to allow use of procedures to adjust overwithholding and underwithholding for amounts withheld by a broker pursuant to proposed § 1.1446(f)-4. The proposed regulations also amend § 1.1461-2(a) to allow the use of reimbursement and set-off procedures with respect to amounts withheld under section 1446(a) on distributions of ECTI by publicly traded partnerships (which are reported on Forms 1042 and 1042-S, as opposed to Forms 8804, 
                        <E T="03">Annual Return for Partnership Withholding Tax (Section 1446),</E>
                         and 8805 used by non-publicly traded partnerships to report withholding on ECTI allocable to foreign partners). They also amend § 1.1461-2(b) to clarify that the existing reference to “distributions of effectively connected income under section 1446” is meant to apply only to those distributions that are made by publicly traded partnerships.
                    </P>
                    <HD SOURCE="HD1">Applicability Dates</HD>
                    <P>
                        Proposed § 1.864(c)(8)-2(a) and proposed § 1.6050K-1(d)(3) apply to transfers that occur on or after the date that these regulations are published as final regulations in the 
                        <E T="04">Federal Register</E>
                         (the “finalization date”). Proposed 
                        <PRTPAGE P="21210"/>
                        § 1.864(c)(8)-2(b) and (c) and proposed § 1.6050K-1(c)(2) and (c)(3) apply to returns filed on or after the finalization date. Proposed § 1.864(c)(8)-2(d) applies beginning on the finalization date.
                    </P>
                    <P>Proposed §§ 1.1445-2(b)(2)(v) and 1.1445-5(b)(3)(iv) apply to certifications provided on or after May 7, 2019, except that a taxpayer may apply those provisions with respect to certifications provided before that date. A taxpayer may rely on the proposed amendments to §§ 1.1445-2 and 1.1445-5 with respect to any period before the finalization date. Proposed § 1.1445-8(f)(1) applies to distributions made on or after the date that is 60 days after the finalization date.</P>
                    <P>Proposed § 1.1446-3(c)(4) applies to partnership taxable years that include transfers that occur on or after the date that is 60 days after the finalization date. Proposed § 1.1446-4(b)(2), (b)(3), (c), (d), and (f) apply to distributions made on or after the date that is 60 days after the finalization date.</P>
                    <P>Proposed §§ 1.1446(f)-1 through 1.1446(f)-5 apply to transfers that occur on or after the date that is 60 days after the finalization date. For transfers that occur before the date that is 60 days after the finalization date, taxpayers may apply the rules described in Notice 2018-08 and Notice 2018-29. Alternatively, instead of applying the rules described in Notice 2018-29, taxpayers and other affected persons may choose to apply §§ 1.1446(f)-1, 1.1446(f)-2, and 1.1446(f)-5 of the proposed regulations in their entirety to all transfers as if they were final regulations.</P>
                    <P>The proposed amendments to § 1.1461-1(a)(1), (c)(1)(i), (c)(1)(ii), (c)(2)(i) and (c)(4) apply with respect to returns for transfers occurring on or after the date that is 60 days after the finalization date. The proposed amendments to § 1.1461-2(a)(1) and (b) apply to transfers occurring on or after the date that is 60 days after the finalization date. The proposed amendments to § 1.1461-3 apply to returns for transfers occurring on or after the date that is 60 days after the finalization date.</P>
                    <P>The proposed amendments to § 1.1463-1(a) apply to transfers that occur on or after the date that is 60 days after the finalization date.</P>
                    <P>The proposed amendments to § 1.1464-1(a) apply to transfers that occur on or after the date that is 60 days after the finalization date.</P>
                    <P>The Treasury Department and the IRS intend to obsolete Notice 2018-08 and Notice 2018-29 effective on the date that is 60 days after the finalization date.</P>
                    <HD SOURCE="HD1">Special Analyses</HD>
                    <HD SOURCE="HD1">I.  Regulatory Planning and Review </HD>
                    <P>This regulation is not subject to review under section 6(b) of Executive Order 12866 pursuant to the Memorandum of Agreement (April 11, 2018) between the Treasury Department and the Office of Management and Budget regarding review of tax regulations.</P>
                    <HD SOURCE="HD1">II.  Paperwork Reduction Act </HD>
                    <P>The collection of information in these proposed regulations is in proposed § 1.864(c)(8)-2 regarding reporting for transactions described in section 864(c)(8) and proposed § 1.864(c)(8)-1, and proposed §§ 1.1446(f)-1, 1.1446(f)-2, 1.1446(f)-3, and 1.1446(f)-4 regarding the withholding, reporting, and paying of tax under section 1446(f) following the transfer of an interest described in section 864(c)(8) and proposed § 1.864(c)(8)-1. Section II.1 of this Special Analyses discusses the collections of information that will be conducted using IRS forms. The information collections that will not be conducted through IRS forms are discussed in section II.2 of this Special Analyses.</P>
                    <HD SOURCE="HD2">A.  Collections of Information—Forms 1042, 1042-S, 8288, 8288-A, 8288-C, W-8IMY, W-8BEN, and W-8BEN-E </HD>
                    <P>Under proposed §§ 1.1446(f)-2(b)(2) and 1.1446(f)-4(b)(2), a transferor qualifies for an exception from withholding if it provides to the transferee or broker (as applicable) a certification of non-foreign status, which includes a valid Form W-9 (at the transferor's option). The IRS has determined that Form W-9 is not a collection of information under 5 CFR 1320.3(h)(1) and is exempt from the Paperwork Reduction Act of 1995 (44 U.S.C. 3507(d)) (“PRA”).</P>
                    <P>The collection of information in proposed § 1.1446(f)-2(b)(7) is provided by the transferor by submitting a certification and Form W-8BEN or W-8BEN-E to the transferee and is optional. The information will be used by the transferor to determine whether an exception to withholding applies based on an income tax treaty.</P>
                    <P>The information in proposed § 1.1446(f)-2(c)(2)(iv)(C) by the transferor to the transferee is provided on Form W-8IMY and is optional. This information will be used by the transferee to determine the modified amount realized.</P>
                    <P>The collection of information in proposed § 1.1446(f)-2(d)(1) will be provided on Forms 8288 and 8288-A by the transferee to the IRS and is mandatory if the transferee withholds tax under section 1446(f)(1). These forms will be used by the transferee to report and pay any tax under section 1446(f)(1) and proposed § 1.1446(f)-2.</P>
                    <P>The information provided in proposed § 1.1446(f)-3(d) by the partnership to the IRS will be used by the partnership to report and pay any tax under section 1446(f)(4) and proposed § 1.1446(f)-3 and will be provided on new Form 8288-C. The IRS anticipates that the burden associated with this collection of information will be reflected in OMB control number 1545-0902.</P>
                    <P>The collection of information provided in proposed § 1.1446(f)-4(a)(2)(i) from certain U.S. branches of foreign persons and qualified intermediaries to the broker that effected the transfer of an interest described in section 864(c)(8) and proposed § 1.1446(f)-4 will be provided on Form W-8IMY. This information will be used by the broker to determine its withholding obligation under section 1446(f)(1) and proposed § 1.1446(f)-4.</P>
                    <P>The collection of information in proposed § 1.1446(f)-4(b)(6) is provided by the transferor by submitting a certification and Form W-8BEN or W-8BEN-E to the broker and is optional. The information will be used by the broker to determine whether an exception to withholding applies based on an income tax treaty.</P>
                    <P>The information in proposed § 1.1446(f)-4(c)(2)(ii)(C) by the transferor to the broker is provided on Form W-8IMY and is optional. This information will be used by the broker to determine the modified amount realized.</P>
                    <P>The information in proposed § 1.1446(f)-4(d) will be provided on Forms 1042 and 1042-S submitted by the broker to the IRS and is mandatory if the broker withholds tax under section 1446(f)(1) or if it applies the exception described in proposed § 1.1446(f)-4(b)(6). These forms will be used to report and pay any tax under section 1446(f)(1) and proposed § 1.1446(f)-4.</P>
                    <P>The information in proposed § 1.1446(f)-4(e)(2) provided by the transferor to the IRS will be used to claim a credit for an amount withheld under section 1446(f)(1) and proposed § 1.1446(f)-4, and will be satisfied by submitting Form 1042-S with an income tax return (Form 1040NR or 1120-F) to the IRS.</P>
                    <P>
                        The Treasury Department and the IRS intend that the information collection requirements described in this section II.1 will be set forth in the forms and instructions identified in the Revision of 
                        <PRTPAGE P="21211"/>
                        Existing Forms and New Forms table. As a result, for purposes of the PRA, the reporting burdens associated with the collections of information in those forms will be reflected in the PRA submissions associated with those forms.
                    </P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="xs54,12C,12C,12C">
                        <TTITLE>Revision of Existing Forms and New Forms</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">New</CHED>
                            <CHED H="1">
                                Revision of 
                                <LI>existing form</LI>
                            </CHED>
                            <CHED H="1">
                                Number of 
                                <LI>additional </LI>
                                <LI>respondents </LI>
                                <LI>(estimated, </LI>
                                <LI>rounded to </LI>
                                <LI>nearest 1,000)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Form 1042-S</ENT>
                            <ENT/>
                            <ENT>Y</ENT>
                            <ENT>&lt;6,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Form 8288</ENT>
                            <ENT/>
                            <ENT>Y</ENT>
                            <ENT>&lt;70,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Form 8288-A</ENT>
                            <ENT/>
                            <ENT>Y</ENT>
                            <ENT>&lt;70,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Form 8288-C</ENT>
                            <ENT>Y</ENT>
                            <ENT/>
                            <ENT>&lt;70,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Form W-8BEN</ENT>
                            <ENT/>
                            <ENT>Y</ENT>
                            <ENT>&lt;70,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Form W-8BEN-E</ENT>
                            <ENT/>
                            <ENT>Y</ENT>
                            <ENT>&lt;70,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Form W-8IMY</ENT>
                            <ENT/>
                            <ENT>Y</ENT>
                            <ENT>&lt;70,000</ENT>
                        </ROW>
                        <TNOTE>Source: RAAS:CDW and SOI.</TNOTE>
                    </GPOTABLE>
                    <P>The numbers of respondents in the Revision of Existing Forms and New Forms table were estimated by the Research, Applied Analytics and Statistics Division of the IRS from the Compliance Data Warehouse and Statistics of Income, using tax years 2013 through 2015. Data for each of the Forms 1042, 1042-S, 8288, 8288-A, W-8BEN, W-8BEN-E, and W-8IMY represent preliminary estimates of the total number of additional taxpayers that are expected to file these forms. The tax data for 2016 and 2017 are not yet available. Data for Forms 8288, 8288-A, W-8BEN, W-8BEN-E, and W-8IMY represent preliminary estimates of the total number of interests in partnerships, other than publicly traded partnership interests, engaged in the conduct of a trade or business in the United States that will be transferred by foreign persons. Data for Form 8288-C represent preliminary estimates of the total number of transferees on whom partnerships must withhold tax under section 1446(f)(4) if the transferees do not fully withhold tax under section 1446(f)(1). Data for Form 1042-S represent preliminary estimates of the total number of interests in publicly traded partnership engaged in the conduct of a trade or business in the United States that will be transferred by foreign persons.</P>
                    <P>The current status of the PRA submissions related to the tax forms that will be used to conduct the information collections in the proposed regulations is provided in the Current Status of PRA Submissions table. The overall burden estimates provided for the OMB control numbers below are aggregate amounts that relate to the entire package of forms associated with the applicable OMB control number and will in the future include, but not isolate, the estimated burden of the tax forms that will be created or revised as a result of the information collections in the proposed regulations. These numbers are therefore unrelated to the future calculations needed to assess the burden imposed by the proposed regulations. No burden estimates specific to the forms affected by the proposed regulations are currently available. The Treasury Department and the IRS have not estimated the burden, including that of any new information collections, related to the requirements under the proposed regulations. The Treasury Department and the IRS request comments on all aspects of information collection burdens related to the proposed regulations, including estimates for how much time it would take to comply with the paperwork burdens described above for each relevant form and ways for the IRS to minimize the paperwork burden.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r50,12,r50">
                        <TTITLE>Current Status of PRA Submissions</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Type of filer</CHED>
                            <CHED H="1">OMB No.(s)</CHED>
                            <CHED H="1">Status</CHED>
                        </BOXHD>
                        <ROW RUL="s">
                            <ENT I="01">Form 1042, Form 1042-S</ENT>
                            <ENT>All filers (Legacy Model)</ENT>
                            <ENT>1545-0096</ENT>
                            <ENT>Approved 12/27/2016 until 12/31/2019.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT A="02">
                                <E T="03">Link: https://www.reginfo.gov/public/do/PRAViewICR?ref_nbr=201606-1545-025.</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Form 8288, Form 8288-A</ENT>
                            <ENT>All filers (Legacy system)</ENT>
                            <ENT>1545-0902</ENT>
                            <ENT>Approved 1/2/2017 until 1/31/2020.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT A="02">
                                <E T="03">Link: https://www.reginfo.gov/public/do/PRAViewICR?ref_nbr=201608-1545-015.</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Form W-8BEN, Form W-8BEN-E, Form W-8IMY</ENT>
                            <ENT>Business (NEW Model)</ENT>
                            <ENT>1545-0123</ENT>
                            <ENT>Approved 12/21/2018 until 12/31/2019.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT A="02">
                                <E T="03">Link: https://www.reginfo.gov/public/do/PRAViewICR?ref_nbr=201805-1545-019.</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>All other filers (Legacy system)</ENT>
                            <ENT>1545-1621</ENT>
                            <ENT>Approved 12/19/18 until 12/31/2021.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT A="02">
                                <E T="03">Link: https://www.reginfo.gov/public/do/PRAViewICR?ref_nbr=201708-1545-002.</E>
                            </ENT>
                        </ROW>
                    </GPOTABLE>
                    <PRTPAGE P="21212"/>
                    <HD SOURCE="HD2">B. Collections of Information—Proposed §§ 1.864(c)(8)-2(a) and (b), 1.1446(f)-1(c)(3), 1.1446(f)-2(b)(2) Through (7), (c)(2), and (c)(4), 1.1446(f)-4(b)(2) and (6), 1.1446(f)-4(b)(3) and (4), and 1.1446(f)-2(d)(2)</HD>
                    <P>These proposed regulations contain collections of information that are not on existing or new IRS forms. These collections of information include:</P>
                    <P>(a) Notification by a transferor to a partnership that a transfer has occurred (proposed § 1.864(c)(8)-2(a));</P>
                    <P>(b) Statement provided by a partnership to a transferor necessary for the transferor to calculate its tax liability (proposed § 1.864(c)(8)-2(b));</P>
                    <P>(c) Retention of information by partnership in its books and records (proposed § 1.1446(f)-1(c)(3));</P>
                    <P>(d) Certifications from a transferor (or partnership) to a transferee for an exception from withholding or adjustment to amount realized (proposed § 1.1446(f)-2(b)(2) through (7), (c)(2), and (c)(4));</P>
                    <P>(e) Certification from a transferee to partnership regarding the transferee's withholding (proposed § 1.1446(f)-2(d)(2)).</P>
                    <P>(f) Certifications from a transferor to a broker to apply an exception from withholding (proposed § 1.1446(f)-4(b)(2) and (6)); and</P>
                    <P>(g) Information provided by a publicly traded partnership to a broker (proposed § 1.1446(f)-4(b)(3) and (4)).</P>
                    <P>The collections of information contained in this notice of proposed rulemaking has been submitted to the Office of Management and Budget for review in accordance with the PRA. Comments on the collection of information should be sent to the Office of Management and Budget, Attn: Desk Officer for the Department of the Treasury, Office of Information and Regulatory Affairs, Washington, DC 20503, with copies to the Internal Revenue Service, Attn: IRS Reports Clearance Officer, SE:W:CAR:MP:T:T:SP, Washington, DC 20224. Comments on the collection of information should be received by July 12, 2019. Comments are specifically requested concerning:</P>
                    <P>Whether the proposed collection of information is necessary for the proper performance of the IRS, including whether the information will have practical utility;</P>
                    <P>The accuracy of the estimated burden associated with the proposed collection of information (including underlying assumptions and methodology);</P>
                    <P>How the quality, utility, and clarity of the information to be collected may be enhanced;</P>
                    <P>How the burden of complying with the proposed collections of information may be minimized, including through the application of automated collection techniques or other forms of information technology; and</P>
                    <P>Estimates of capital or start-up costs and costs of operation, maintenance, and purchase of service to provide information.</P>
                    <P>The collections of information provided in proposed § 1.864(c)(8)-2 will be used by both the partnership engaged in the conduct of a trade or business in the United States and the foreign partner that transfers an interest in the partnership and are mandatory. The notification provided to the partnership by the foreign transferor in proposed § 1.864(c)(8)-2(a) will serve as notice to the partnership that a transfer described in section 864(c)(8) and proposed § 1.864(c)(8)-1 occurred. The statement provided to the foreign transferor by the partnership in proposed § 1.864(c)(8)-2(b) is necessary for the foreign transferor to determine its effectively connected gain or loss as described in proposed § 1.864(c)(8)-1(b) and (c).</P>
                    <P>The collection of information provided in proposed § 1.1446(f)-1(c)(3) requires a partnership to retain certain identified information in its books and records regarding its obligation to withhold under section 1446(f). The identified information will be used by a partnership to determine the application, and the extent, of withholding under section 1446(f).</P>
                    <P>The collections of information provided in proposed § 1.1446(f)-2(b)(2) through (7), (c)(2), and (c)(4) from the transferor of an interest described in section 1446(f), or from the partnership whose interest is transferred, to the transferee of the interest will be used by the transferee to determine whether an exception applies or to determine the amount realized. These collections of information are optional. The certification in proposed § 1.1446(f)-2(b)(7) includes the submission of Form W-8BEN or W-8BEN-E and is also discussed in section II.1 of this Special Analyses.</P>
                    <P>The information provided in proposed § 1.1446(f)-2(d)(2) by the transferee to the partnership will be used by the partnership to determine whether it has a withholding obligation under section 1446(f)(4) and proposed § 1.1446(f)-3.</P>
                    <P>The collection of information provided in proposed § 1.1446(f)-4(b)(6) by the transferor to the broker will be used by the broker to determine if an exception applies that relieves the broker from its withholding obligation under section 1446(f)(1) and proposed § 1.1446(f)-4. The certification in proposed § 1.1446(f)-4(b)(6) includes the submission of Form W-8BEN or W-8BEN-E and is also discussed in section II.1 of this Special Analyses.</P>
                    <P>
                        <E T="03">Estimated total annual reporting burden:</E>
                         50,920 hours.
                    </P>
                    <P>
                        <E T="03">Estimated average annual burden hours per respondent:</E>
                         Approximately 0.67 hours (40 minutes).
                    </P>
                    <P>
                        <E T="03">Estimated cost per respondent ($2016):</E>
                         $26.00.
                    </P>
                    <P>
                        <E T="03">Estimated total annual monetized cost ($2016):</E>
                         $1,827,938.00.
                    </P>
                    <P>
                        <E T="03">Estimated number of respondents:</E>
                         76,000.
                    </P>
                    <P>
                        <E T="03">Estimated annual frequency of responses:</E>
                         0.4 (as the collections of information do not occur on an annual basis).
                    </P>
                    <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid control number assigned by the Office of Management and Budget.</P>
                    <P>Books or records relating to a collection of information must be retained as long as their contents may become material in the administration of any internal revenue law. Generally, tax returns and tax return information are confidential, as required by 26 U.S.C. 6103.</P>
                    <HD SOURCE="HD1">III.  Regulatory Flexibility Act </HD>
                    <P>It is hereby certified that this notice of proposed rulemaking will not have a significant economic impact on a substantial number of small entities within the meaning of section 601(6) of the Regulatory Flexibility Act (5 U.S.C. chapter 6).</P>
                    <P>The proposed regulations affect (i) foreign persons that recognize gain or loss from the sale or exchange of an interest in a partnership that is engaged in the conduct of a trade or business within the United States, and who are not subject to the Regulatory Flexibility Act, (ii) U.S. persons that are transferors providing Forms W-9 to transferees to certify that they are not foreign persons, (iii) persons who acquire those interests, (iv) partnerships that, directly or indirectly, have foreign persons as partners, and (v) brokers that effect transfers of interests in publicly traded partnerships.</P>
                    <P>
                        The Treasury Department and the IRS do not have data readily available to assess the number of small entities potentially affected by the proposed regulations. However, entities potentially affected by these proposed regulations are generally not small entities, because of the resources and investment necessary to acquire a 
                        <PRTPAGE P="21213"/>
                        partnership interest from a foreign person or to directly, or indirectly, have foreign persons as partners. Therefore, the Treasury Department and the IRS do not believe that a substantial number of domestic small entities will be subject to the proposed regulation's information collections. Consequently, the Treasury Department and the IRS certify that the proposed regulations will not have a significant economic impact on a substantial number of small entities. The IRS invites the public to comment on the impact of these regulations on small entities.
                    </P>
                    <P>Pursuant to section 7805(f) of the Code, these regulations will be submitted to the Chief Counsel for Advocacy of the Small Business Administration for comment on their impact on small businesses.</P>
                    <HD SOURCE="HD1">Comments and Requests for Public Hearing</HD>
                    <P>
                        Before the proposed regulations are adopted as final regulations, consideration will be given to any comments that are submitted timely to the IRS as prescribed in this preamble under the 
                        <E T="02">ADDRESSES</E>
                         heading. The Treasury Department and the IRS request comments on all aspects of the proposed rules. All comments will be available at 
                        <E T="03">www.regulations.gov</E>
                         or upon request. A public hearing will be scheduled if requested in writing by any person that timely submits written comments. If a public hearing is scheduled, notice of the date, time, and place for the public hearing will be published in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                    <HD SOURCE="HD1">Drafting Information</HD>
                    <P>The principal authors of the proposed regulations are Subin Seth, Ronald M. Gootzeit, and Chadwick Rowland, Office of Associate Chief Counsel (International). However, other personnel from the Treasury Department and the IRS participated in their development.</P>
                    <HD SOURCE="HD1">Statement of Availability of IRS Documents</HD>
                    <P>
                        IRS Revenue Procedures, Revenue Rulings, notices, and other guidance cited in this document are published in the Internal Revenue Bulletin and are available from the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402, or by visiting the IRS website at 
                        <E T="03">http://www.irs.gov.</E>
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 26 CFR Part 1</HD>
                        <P>Income taxes, Reporting and recordkeeping requirements.</P>
                    </LSTSUB>
                    <HD SOURCE="HD1">Proposed Amendments to the Regulations</HD>
                    <P>Accordingly, 26 CFR part 1 is proposed to be amended as follows:</P>
                    <PART>
                        <HD SOURCE="HED">PART 1—INCOME TAXES</HD>
                    </PART>
                    <AMDPAR>
                        <E T="04">Paragraph 1.</E>
                         The authority citation for part 1 is amended by adding sectional authorities for §§ 1.864(c)(8)-2, 1.1445-5, 1.1445-8, 1.1446-3 through 1.1446-4, 1.1446(f)-1 through 1.1446(f)-5, and 1.6050K-1 in numerical order to read in part as follows:
                    </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 26 U.S.C. 7805 * * *</P>
                    </AUTH>
                    <EXTRACT>
                        <P>Section 1.864(c)(8)-2 also issued under 26 U.S.C. 864(c)(8)(E), 6001 and 6031(b).</P>
                        <STARS/>
                        <P>Section 1.1445-5 also issued under 26 U.S.C. 1445(e)(7).</P>
                        <STARS/>
                        <P>Section 1.1445-8 also issued under 26 U.S.C. 1445(e)(7).</P>
                        <STARS/>
                        <P>Section 1.1446-3 also issued under 26 U.S.C. 1446(g).</P>
                        <STARS/>
                        <P>Section 1.1446-4 also issued under 26 U.S.C. 1446(g).</P>
                        <STARS/>
                        <P>Section 1.1446(f)-1 also issued under 26 U.S.C. 1446(f)(6) and 1446(g).</P>
                        <STARS/>
                        <P>Section 1.1446(f)-2 also issued under 26 U.S.C. 1446(f)(6) and 1446(g).</P>
                        <STARS/>
                        <P>Section 1.1446(f)-3 also issued under 26 U.S.C. 1446(f)(6) and 1446(g).</P>
                        <STARS/>
                        <P>Section 1.1446(f)-4 also issued under 26 U.S.C. 1446(f)(6) and 1446(g).</P>
                        <STARS/>
                        <P>Section 1.1446(f)-5 also issued under 26 U.S.C. 1446(f)(6) and 1446(g).</P>
                        <STARS/>
                        <P>Section 1.6050K-1 also issued under 26 U.S.C. 6050K(a).</P>
                        <STARS/>
                    </EXTRACT>
                    <AMDPAR>
                        <E T="04">Par. 2.</E>
                         Section 1.864(c)(8)-2 is added to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.864(c)(8)-2 </SECTNO>
                        <SUBJECT>Notification and reporting requirements.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Notification by foreign transferor</E>
                            —(1) 
                            <E T="03">In general.</E>
                             Except as provided in paragraph (a)(2) of this section, a notifying transferor that transfers an interest in a specified partnership must notify the partnership of the transfer in writing within 30 days of the transfer. The notification must include—
                        </P>
                        <P>(i) The names and addresses of the notifying transferor and the transferee or transferees;</P>
                        <P>(ii) The U.S. taxpayer identification number (TIN) of the notifying transferor and, if known, of the transferee or transferees; and</P>
                        <P>(iii) The date of the transfer.</P>
                        <P>
                            (2) 
                            <E T="03">Exceptions</E>
                            —(i) 
                            <E T="03">Certain interests in publicly traded partnerships.</E>
                             Paragraph (a)(1) of this section does not apply to a notifying transferor that transfers an interest in a publicly traded partnership if the interest is publicly traded on an established securities market or is readily tradable on a secondary market (or the substantial equivalent thereof).
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Certain distributions.</E>
                             Paragraph (a)(1) of this section does not apply to a notifying transferor that is treated as transferring an interest in a specified partnership because it received a distribution from that specified partnership.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Section 6050K.</E>
                             The notification described in paragraph (a)(1) of this section may be combined with or provided at the same time as the notification described in § 1.6050K-1(d), provided that it satisfies the requirements of both sections.
                        </P>
                        <P>
                            (4) 
                            <E T="03">Other guidance.</E>
                             The notification described in paragraph (a)(1) of this section must also include any information required in forms, instructions, or other guidance.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Reporting by specified partnerships with notifying transferor</E>
                            —(1) 
                            <E T="03">In general.</E>
                             (i) A specified partnership must provide to a notifying transferor the statement described in paragraph (b)(2) of this section if—
                        </P>
                        <P>(A) The partnership receives the notice described in paragraph (a) of this section, or otherwise has actual knowledge that there has been a transfer of an interest in the partnership by a notifying transferor; and</P>
                        <P>(B) At the time of the transfer, the notifying transferor would have had a distributive share of deemed sale EC gain or deemed sale EC loss within the meaning of § 1.864(c)(8)-1(c).</P>
                        <P>
                            (ii) 
                            <E T="03">Distributions.</E>
                             For purposes of paragraph (b)(1)(i)(B) of this section, a partnership that is a transferee because it makes a distribution is treated as having actual knowledge of that transfer.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Contents of statement.</E>
                             The statement required to be furnished by the specified partnership under paragraph (b)(1) of this section must include—
                        </P>
                        <P>(i) The items described in § 1.864(c)(8)-1(c)(3)(ii) (foreign transferor's aggregate deemed sale EC items, which includes items derived from lower-tier partnerships); and</P>
                        <P>(ii) Any other information as provided in forms, instructions, or other guidance.</P>
                        <P>
                            (3) 
                            <E T="03">Time for furnishing statement.</E>
                             The specified partnership must furnish the required information on or before the due date (with extensions) for issuing 
                            <PRTPAGE P="21214"/>
                            Schedule K-1 (Form 1065), 
                            <E T="03">Partner's Share of Income, Deductions, Credits, etc.,</E>
                             or its successor, to the transferor for the year of the transfer. 
                            <E T="03">See</E>
                             § 1.6031(b)-1T(b).
                        </P>
                        <P>
                            (4) 
                            <E T="03">Manner of furnishing statement.</E>
                             No specific format is required for the information except as provided in any forms, instructions, or other guidance.
                        </P>
                        <P>
                            (5) 
                            <E T="03">Partnership notifying transferor.</E>
                             For purposes of this paragraph (b), a specified partnership must treat a notifying transferor that is a partnership as a nonresident alien individual.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Statement may be provided to agent.</E>
                             A partnership may provide a statement required under paragraph (b)(2) of this section to a person other than the notifying transferor if the person is described in § 1.6031(b)-1T(c).
                        </P>
                        <P>
                            (d) 
                            <E T="03">Definitions.</E>
                             The following definitions apply for purposes of this section.
                        </P>
                        <P>
                            (1) 
                            <E T="03">Notifying transferor.</E>
                             The term 
                            <E T="03">notifying transferor</E>
                             means any foreign person, any domestic partnership that has a foreign person as a direct partner, and any domestic partnership that has actual knowledge that a foreign person indirectly holds, through one or more partnerships, an interest in the domestic partnership.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Specified partnership.</E>
                             The term 
                            <E T="03">specified partnership</E>
                             means a partnership that is engaged in the conduct of a trade or business within the United States or that owns (directly or indirectly) an interest in a partnership that is engaged in the conduct of a trade or business within the United States, and may include a publicly traded partnership as defined in section 7704 and §§ 1.7704-1 through 1.7704-4, but does not include a publicly traded partnership treated as a corporation under that section.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Transfer.</E>
                             The term 
                            <E T="03">transfer</E>
                             has the meaning provided in § 1.864(c)(8)-1(g)(5).
                        </P>
                        <P>
                            (e) 
                            <E T="03">Applicability dates.</E>
                             Paragraph (a) of this section applies to transfers that occur on or after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            . Paragraphs (b) and (c) of this section apply to returns filed on or after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            . Paragraph (d) of this section applies beginning on the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 3.</E>
                         Section 1.1445-2 is amended by adding paragraph (b)(2)(v) and a sentence to the end of paragraph (e) to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.1445-2 </SECTNO>
                        <SUBJECT>Situations in which withholding is not required under section 1445(a).</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(2) * * *</P>
                        <P>
                            (v) 
                            <E T="03">Form W-9.</E>
                             For purposes of paragraph (b)(2)(i) of this section, a certification of non-foreign status includes a valid Form W-9, 
                            <E T="03">Request for Taxpayer Identification Number and Certification,</E>
                             or its successor, submitted to the transferee by the transferor.
                        </P>
                        <STARS/>
                        <P>
                            (e) 
                            <E T="03">Applicability dates.</E>
                             * * * Paragraph (b)(2)(v) of this section applies to certifications provided on or after May 7, 2019, except that a taxpayer may apply it with respect to certifications provided before that date.
                        </P>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 4.</E>
                         Section 1.1445-5 is amended by adding paragraph (b)(3)(iv) and a sentence to the end of paragraph (h) to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.1445-5</SECTNO>
                        <SUBJECT> Special rules concerning distributions and other transactions by corporations, partnerships, trusts, and estates.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(3) * * *</P>
                        <P>
                            (iv) 
                            <E T="03">Form W-9.</E>
                             For purposes of paragraph (b)(3)(i) of this section, a certification of non-foreign status includes a valid Form W-9, 
                            <E T="03">Request for Taxpayer Identification Number and Certification,</E>
                             or its successor, submitted to the transferee by the transferor.
                        </P>
                        <STARS/>
                        <P>
                            (h) 
                            <E T="03">Applicability dates.</E>
                             * * * Paragraph (b)(3)(iv) of this section applies to certifications provided on or after May 7, 2019, except that a taxpayer may apply it with respect to certifications provided before that date.
                        </P>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 5.</E>
                         Section 1.1445-8 is amended by revising paragraph (f) to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.1445-8 </SECTNO>
                        <SUBJECT>Special rules regarding publicly traded partnerships, publicly traded trusts and real estate investment trusts (REITs).</SUBJECT>
                        <STARS/>
                        <P>
                            (f) 
                            <E T="03">Qualified notice</E>
                            —(1) 
                            <E T="03">In general.</E>
                             A qualified notice for purposes of paragraph (b)(3)(iv) of this section is a notice provided in the manner described in § 1.1446-4(b)(4) by a partnership, trust, or REIT regarding a distribution that is attributable to the disposition of a United States real property interest. In the case of a REIT, a qualified notice is only a notice of a distribution, all or any portion of which the REIT actually designates, or characterizes in accordance with paragraph (c)(2)(ii)(C) of this section, as a capital gain dividend in the manner described in § 1.1446-4(b)(4), with respect to each share or certificate of beneficial interest. A deemed designation under paragraph (c)(2)(ii)(A) of this section may not be the subject of a qualified notice under this paragraph (f). A person described in paragraph (b)(3) of this section is treated as receiving a qualified notice when the notice is provided in accordance with § 1.1446-4(b)(4).
                        </P>
                        <P>
                            (2) 
                            <E T="03">Applicability dates.</E>
                             Paragraph (f)(1) of this section applies to distributions made on or after the date that is 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 6.</E>
                         Section 1.1446-3 is amended:
                    </AMDPAR>
                    <AMDPAR>1. In the first sentence of paragraph (a)(2)(i), by removing “section 11(b)(1)” and adding in its place “section 11(b)”.</AMDPAR>
                    <AMDPAR>2. By adding paragraph (c)(4).</AMDPAR>
                    <P>The addition reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1.1446-3 </SECTNO>
                        <SUBJECT>Time and manner of calculating and paying the 1446 tax.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>
                            (4) 
                            <E T="03">Coordination with section 1446(f).</E>
                             A partnership that is directly or indirectly subject to withholding under section 1446(f)(1) during its taxable year may credit the amount withheld under section 1446(f)(1) against its section 1446 tax liability for that taxable year only to the extent the amount is allocable to foreign partners.
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 7.</E>
                         Section 1.1446-4 is amended by:
                    </AMDPAR>
                    <AMDPAR>1. By revising paragraphs (b)(3) and (4).</AMDPAR>
                    <AMDPAR>2. By removing the second sentence of paragraph (c).</AMDPAR>
                    <AMDPAR>3. By revising paragraphs (d) and (f)(3).</AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1.1446-4 </SECTNO>
                        <SUBJECT>Publicly traded partnerships.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>
                            (3) 
                            <E T="03">Nominee.</E>
                             For purposes of this section, the term nominee means a person that holds an interest in a publicly traded partnership on behalf of a foreign person and that is either a U.S. person, a qualified intermediary (as defined in § 1.1441-1(e)(5)(ii)) that assumes primary withholding responsibility for a payment, or a U.S. branch of a foreign person that agrees to be treated as a U.S. person (as described in § 1.1441-1(b)(2)(iv)) with respect to a payment.
                        </P>
                        <P>
                            (4) 
                            <E T="03">Qualified notice.</E>
                             For purposes of this section, a qualified notice is a notice posted by a publicly traded partnership that states the amount of a 
                            <PRTPAGE P="21215"/>
                            distribution that is attributable to each type of income described in paragraphs (f)(3)(i) through (v) of this section. A qualified notice may also include the information described in § 1.1446(f)-4(b)(3), relating to an exception from withholding under section 1446(f)(1) for transfers of certain partnership interests. The notice must be posted in a readily accessible format in an area of the primary public website of the publicly traded partnership that is dedicated to this purpose. A qualified notice must be posted by the date required for providing notice with respect to dividends described in 17 CFR 240.10b-17(b)(1) or (3) (or any successor regulation) issued pursuant to the Securities Exchange Act of 1934 (15 U.S.C. 78a) and contain the information described therein as it would relate to the distribution. The publicly traded partnership must keep the notice accessible to the public for ten years on its primary public website or the primary public website of any successor organization. No specific format is required unless provided in forms, instructions, or other guidance. See paragraph (d) of this section regarding when a nominee is considered to have received a qualified notice.
                        </P>
                        <STARS/>
                        <P>
                            (d) 
                            <E T="03">Rules for designation of nominees to withhold tax under section 1446.</E>
                             A nominee that receives a distribution from a publicly traded partnership subject to withholding under this section, and which is to be paid to (or for the account of) any foreign person, may be treated as a withholding agent under this section. A nominee is treated as receiving a qualified notice on the date that the notice is posted in accordance with paragraph (b)(4) of this section. When a nominee is treated as a withholding agent with respect to a foreign partner of the partnership, the obligation to withhold on distributions to the foreign partner in accordance with the rules of this section is imposed solely on the nominee. A nominee responsible for withholding under the rules of this section is subject to liability under sections 1461 and 6655, as well as all applicable penalties and interest, as if the nominee were a partnership responsible for withholding under this section. A nominee may rely on a qualified notice that meets the requirements in paragraph (b)(4) of this section to determine the amounts on which it must withhold. If a notice a publicly traded partnership issues relating to its distribution does not meet the requirements in paragraph (b)(4) of this section, the nominee must withhold on the distribution with respect to—
                        </P>
                        <P>(1) Foreign partners that are corporations, at the greater of the highest rate of tax specified in section 11(b) or section 881; and</P>
                        <P>(2) Foreign partners that are not corporations, at the greater of the highest rate of tax specified in section 1 or section 871.</P>
                        <STARS/>
                        <P>(f) * * *</P>
                        <P>
                            (3) 
                            <E T="03">Ordering rule relating to distributions.</E>
                             Distributions from publicly traded partnerships are deemed to be paid out of the following types of income in the order indicated—
                        </P>
                        <P>(i) Amounts attributable to income described in section 1441 or 1442 that are not effectively connected with the conduct of a trade or business in the United States but are subject to withholding, before taking into account any treaty exemptions;</P>
                        <P>(ii) Amounts attributable to income described in section 1441 or 1442 that are not effectively connected with the conduct of a trade or business in the United States and are not subject to withholding because of an exemption under a provision of the Code;</P>
                        <P>(iii) Amounts attributable to income effectively connected with the conduct of a trade or business in the United States that are not subject to withholding under §§ 1.1446-1 through 1.1446-6 (for example, amounts exempt by treaty);</P>
                        <P>(iv) Amounts subject to withholding under §§ 1.1446-1 through 1.1446-6; and</P>
                        <P>(v) Amounts not listed in paragraphs (f)(3)(i) through (iv) of this section.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 8.</E>
                         Section 1.1446-7 is amended by revising the section heading and adding two sentences at the end of the section to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.1446-7</SECTNO>
                        <SUBJECT> Applicability dates.</SUBJECT>
                        <P>
                            * * * The addition of § 1.1446-3(c)(4) applies to partnership taxable years that include transfers that occur on or after the date that is 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            . The revisions to § 1.1446-4(b)(3) and (4), the removal of the second sentence of § 1.1446-4(c), and the revisions to § 1.1446-4(d) and (f)(3) apply to distributions made on or after the date that is 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 9.</E>
                         Sections 1.1446(f)-1 through 1.1446(f)-5 are added to read as follows:
                    </AMDPAR>
                    <CONTENTS>
                        <SECHD>Sec.</SECHD>
                        <STARS/>
                        <SECTNO>1.1446(f)-1 </SECTNO>
                        <SUBJECT>General rules.</SUBJECT>
                        <SECTNO>1.1446(f)-2 </SECTNO>
                        <SUBJECT>Withholding on the transfer of a non-publicly traded partnership interest.</SUBJECT>
                        <SECTNO>1.1446(f)-3 </SECTNO>
                        <SUBJECT>Partnership's requirement to withhold under section 1446(f)(4) on distributions to transferee.</SUBJECT>
                        <SECTNO>1.1446(f)-4 </SECTNO>
                        <SUBJECT>Withholding on the transfer of a publicly traded partnership interest.</SUBJECT>
                        <SECTNO>1.1446(f)-5 </SECTNO>
                        <SUBJECT>Liability for failure to withhold.</SUBJECT>
                    </CONTENTS>
                    <STARS/>
                    <SECTION>
                        <SECTNO>§ 1.1446(f)-1 </SECTNO>
                        <SUBJECT>General rules.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Overview.</E>
                             These regulations provide rules for withholding, reporting, and paying tax under section 1446(f) upon the sale, exchange, or other disposition of certain interests in partnerships. This section provides definitions and general rules of applicability that apply for purposes of section 1446(f). Section 1.1446(f)-2 provides withholding rules for the transfer of a non-publicly traded partnership interest under section 1446(f)(1). Section 1.1446(f)-3 provides rules that apply when a partnership is required to withhold under section 1446(f)(4) on distributions made to the transferee in an amount equal to the amount that the transferee failed to withhold plus interest. Section 1.1446(f)-4 provides special rules for the sale, exchange, or disposition of publicly traded partnership interests, for which the withholding obligation under section 1446(f)(1) is generally imposed on certain brokers that act on behalf of the transferor. Section 1.1446(f)-5 provides rules that address the liability for failure to withhold under section 1446(f) and rules regarding the liability of a transferor's or transferee's agent.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Definitions.</E>
                             This paragraph (b) provides definitions that apply for purposes of §§ 1.1446(f)-1 through 1.1446(f)-5.
                        </P>
                        <P>
                            (1) The term 
                            <E T="03">broker</E>
                             means any person, foreign or domestic, that, in the ordinary course of a trade or business during the calendar year, stands ready to effect sales made by others, and that, in connection with a transfer of a PTP interest, receives all or a portion of the amount realized on behalf of the transferor. The term broker also includes any clearing organization (as defined in § 1.1471-1(b)(21)) that effects the transfer of a PTP interest on behalf of the transferor. The term broker does not include an escrow agent that effects no sales other than such transactions that are incidental to the purpose of escrow (such as sales to collect on collateral).
                        </P>
                        <P>
                            (2) The term 
                            <E T="03">controlling partner</E>
                             means a partner that, together with any person that bears a relationship described in sections 267(b) or 707(b)(1) to the partner, owns directly or indirectly a 50 percent or greater 
                            <PRTPAGE P="21216"/>
                            interest in the capital, profits, deductions, or losses of the partnership in the 12 months before the determination date.
                        </P>
                        <P>
                            (3) The term 
                            <E T="03">effect</E>
                             has the meaning provided in § 1.6045-1(a)(10).
                        </P>
                        <P>
                            (4) The term 
                            <E T="03">foreign person</E>
                             means a person that is not a United States person.
                        </P>
                        <P>
                            (5) The term 
                            <E T="03">PTP interest</E>
                             means an interest in a publicly traded partnership if the interest is publicly traded on an established securities market or is readily tradable on a secondary market (or the substantial equivalent thereof).
                        </P>
                        <P>
                            (6) The term 
                            <E T="03">publicly traded partnership</E>
                             has the same meaning as in section 7704 and §§ 1.7704-1 through 1.7704-4 but does not include a publicly traded partnership treated as a corporation under that section.
                        </P>
                        <P>
                            (8) The term 
                            <E T="03">TIN</E>
                             means the tax identifying number assigned to a person under section 6109.
                        </P>
                        <P>
                            (9) The term 
                            <E T="03">transfer</E>
                             means a sale, exchange, or other disposition, and includes a distribution from a partnership to a partner.
                        </P>
                        <P>
                            (10) The term 
                            <E T="03">transferee</E>
                             means any person, foreign or domestic, that acquires a partnership interest through a transfer, and includes a partnership that makes a distribution.
                        </P>
                        <P>
                            (11) Except as otherwise provided in this paragraph, the term 
                            <E T="03">transferor</E>
                             means any person, foreign or domestic, that transfers a partnership interest. In the case of a trust, to the extent all or a portion of the income of the trust is treated as owned by the grantor or another person under sections 671 through 679 (such trust, a grantor trust), the term transferor means the grantor or other person.
                        </P>
                        <P>
                            (12) The term 
                            <E T="03">transferor's agent</E>
                             or 
                            <E T="03">transferee's agent</E>
                             means any person who represents the transferor or transferee (respectively) in any negotiation with another person relating to the transaction or in settling the transaction. A person will not be treated as a transferor's agent or a transferee's agent solely because it performs one or more of the activities described in § 1.1445-4(f)(3) (relating to activities of settlement officers and clerical personnel).
                        </P>
                        <P>
                            (13) The term 
                            <E T="03">United States person</E>
                             or 
                            <E T="03">U.S. person</E>
                             means a person described in section 7701(a)(30).
                        </P>
                        <P>
                            (c) 
                            <E T="03">General rules of applicability</E>
                            —(1) 
                            <E T="03">In general.</E>
                             This paragraph (c) provides general rules that apply for purposes of §§ 1.1446(f)-1 through 1.1446(f)-5.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Certifications</E>
                            —(i) 
                            <E T="03">In general.</E>
                             This paragraph (c)(2) provides rules that are applicable to certifications described in §§ 1.1446(f)-1 through 1.1446(f)-5, except as otherwise provided therein, or in forms, instructions, or other guidance. A certification must provide the name and address of the person providing it. A certification must also be signed under penalties of perjury and, if the certification is provided by the transferor, must include a TIN if the transferor has, or is required to have, a TIN. A transferee (or other person required to withhold) may not rely on a certification if it knows that a transferor has, or is required to have, a TIN, and that TIN has not been provided with the certification. A certification includes any documents associated with the certification, such as statements from the partnership, IRS forms, withholding certificates, withholding statements, certifications, or other documentation. Documents associated with the certification form an integral part of the certification, and the penalties of perjury statement provided on the certification also applies to the documents. A certification (other than the certification described in § 1.1446(f)-2(d)(2)) may not be relied upon if it is obtained earlier than 30 days before the transfer or any time after the transfer.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Penalties of perjury.</E>
                             A certification signed under penalties of perjury must provide the following: “Under penalties of perjury, I declare that I have examined the information on this document, and to the best of my knowledge and belief, it is true, correct, and complete.”
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Authority to sign certifications on behalf of a business entity.</E>
                             A certification provided by a business entity must be signed by an individual who is an officer, director, general partner, or managing member of the entity, or, if the general partner or managing member is itself a business entity, an individual who is an officer, director, or managing member of the entity that is the general partner or managing member.
                        </P>
                        <P>
                            (iv) 
                            <E T="03">Electronic submission.</E>
                             A certification may be sent electronically, including as text in an email, an image embedded in an email, or a Portable Document Format (.pdf) attached to an email. An electronic certification, however, may not be relied upon if the person receiving the submission knows that the certification was transmitted by a person not authorized to do so by the person required to execute the certification.
                        </P>
                        <P>
                            (v) 
                            <E T="03">Retention period.</E>
                             Any person that relies on a certification pursuant to §§ 1.1446(f)-1 through 1.1446(f)-5 must retain the certification (including any documentation) for the longer of five calendar years following the close of the last calendar year in which it relied on the certification or for as long as it may be relevant to the determination of its withholding obligation under section 1446(f) or its withholding tax liability under section 1461.
                        </P>
                        <P>
                            (vi) 
                            <E T="03">Submission to IRS.</E>
                             Except as provided in § 1.1446(f)-2(b)(7) and 1.1446(f)-2(c)(4)(vi) (involving certifications relating to an income tax treaty), or in any forms, instructions, or other guidance, the recipient of a certification is not required to mail a copy to the IRS.
                        </P>
                        <P>
                            (vii) 
                            <E T="03">Grantor trusts.</E>
                             A certification provided by a transferor that is a grantor or other owner of a grantor trust must identify the portion of the amount realized that is attributable to the grantor or other owner.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Books and records.</E>
                             A partnership that relies on its books and records pursuant to §§ 1.1446(f)-1 through 1.1446(f)-5 (including for purposes of providing a certification or other statement) must identify in its books and records the date on which the transfer occurred, the information on which the partnership relied, and the provisions of §§ 1.1446(f)-1 through 1.1446(f)-5 supporting an exception from, or adjustment to, the partnership's obligation to withhold. The identification required by this paragraph (c)(3) must be made no later than 30 days after the date of the transfer. The partnership must retain the identified information in its books and records for the longer of five calendar years following the close of the last calendar year in which it relied on the information or for as long as it may be relevant to the determination of its withholding obligation under section 1446(f) or its withholding tax liability under section 1461.
                        </P>
                        <P>
                            (4) 
                            <E T="03">Determination date</E>
                            —(i) 
                            <E T="03">In general.</E>
                             This paragraph (c)(4) provides rules for the determination date. The same determination date must be used for all purposes with respect to a transfer. Any statement, certification, or books and records with regard to a transfer must state the determination date. The determination date of a transfer must be one of the following—
                        </P>
                        <P>(A) The date of the transfer;</P>
                        <P>(B) Any date that is no more than 60 days before the date of the transfer; or</P>
                        <P>(C) The date that is the later of—</P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) The first day of the partnership's taxable year in which the transfer occurs, as determined under section 706; or
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) The date, before the date of the transfer, of the most recent event described in § 1.704-1(b)(2)(iv)(
                            <E T="03">f</E>
                            )(
                            <E T="03">5</E>
                            ) or § 1.704-1(b)(2)(iv)(
                            <E T="03">s</E>
                            )(
                            <E T="03">1</E>
                            ) (revaluation event), irrespective of whether the capital accounts of the partners are 
                            <PRTPAGE P="21217"/>
                            adjusted in accordance with § 1.704-1(b)(2)(iv)(
                            <E T="03">f</E>
                            ).
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Controlling partner.</E>
                             The determination date for a transferor that is a controlling partner is determined without regard to paragraph (c)(4)(i)(C) of this section.
                        </P>
                        <P>
                            (5) 
                            <E T="03">IRS forms and instructions.</E>
                             Any reference to an IRS form includes its successor form. Any form must be filed in the manner provided in the instructions to the forms or in other guidance.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Coordination with section 1445.</E>
                             A transferee that is otherwise required to withhold under section 1445(e)(5) or § 1.1445-11T(d)(1) with respect to the amount realized, as well as under section 1446(f)(1), will be subject to the payment and reporting requirements of section 1445 only, and not section 1446(f)(1), with respect to that amount. However, if the transferor has applied for a withholding certificate under the last sentence of § 1.1445-11T(d)(1), the transferee must withhold the greater of the amounts required under section 1445(e)(5) or section 1446(f)(1). A transferee that has complied with the withholding requirements under either section 1445(e)(5) or section 1446(f)(1), as applicable under this paragraph (d), will be deemed to satisfy the other withholding requirement.
                        </P>
                        <P>
                            (e) 
                            <E T="03">Applicability date.</E>
                             This section applies to transfers that occur on or after the date that is 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1.1446(f)-2</SECTNO>
                        <SUBJECT> Withholding on the transfer of a non-publicly traded partnership interest.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Transferee's obligation to withhold.</E>
                             Except as otherwise provided in this section, a transferee is required to withhold under section 1446(f)(1) a tax equal to 10 percent of the amount realized on any transfer of a partnership interest. This section does not apply to a transfer of a PTP interest that is effected through one or more brokers, including a distribution made with respect to a PTP interest held in an account with a broker. For rules regarding those transfers, see § 1.1446(f)-4.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Exceptions to withholding</E>
                            —(1) 
                            <E T="03">In general.</E>
                             A transferee is not required to withhold under this section if it properly relies on a certification or its books and records as described in this paragraph (b). A transferee may not rely on a certification if it has actual knowledge that the certification is incorrect or unreliable. A partnership that is a transferee because it makes a distribution may not rely on its books and records if it knows, or has reason to know, that the information is incorrect or unreliable.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Certification of non-foreign status by transferor.</E>
                             A transferee may rely on a certification of non-foreign status from the transferor that states that the transferor is not a foreign person, states the transferor's name, TIN, and address, and is signed under penalties of perjury. For this purpose, a certification of non-foreign status includes a valid Form W-9, 
                            <E T="03">Request for Taxpayer Identification Number and Certification.</E>
                             For purposes of this paragraph (b)(2), a transferee may rely on a valid Form W-9 from the transferor that it already possesses if the form meets these requirements.
                        </P>
                        <P>
                            (3) 
                            <E T="03">No realized gain by transferor</E>
                            —(i) 
                            <E T="03">In general.</E>
                             A transferee (other than a partnership that is a transferee because it makes a distribution) may rely on a certification from the transferor that states that the transfer of the partnership interest would not result in any realized gain (including ordinary income arising from application of section 751 § 1.751-1) to the transferor as of the determination date. See paragraph (b)(6) of this section for rules that apply when the transferor realizes gain but is not required to recognize the gain under a provision of the Internal Revenue Code.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Partnership distributions.</E>
                             A partnership that is a transferee because it makes a distribution may rely on its books and records, or on a certification from the transferor, to determine that the distribution would not result in any realized gain to the transferor as of the determination date.
                        </P>
                        <P>
                            (4) 
                            <E T="03">Less than 10 percent effectively connected gain</E>
                            —(i) 
                            <E T="03">In general.</E>
                             A transferee (other than a partnership that is a transferee because it makes a distribution) may rely on a certification from the partnership that states that if the partnership sold all of its assets at fair market value as of the determination date in the manner described in § 1.864(c)(8)-1(c), either—
                        </P>
                        <P>(A) The amount of net gain that would have been effectively connected with the conduct of a trade or business within the United States would be less than 10 percent of the total net gain; or</P>
                        <P>(B) No gain would have been effectively connected with the conduct of a trade or business within the United States.</P>
                        <P>
                            (ii) 
                            <E T="03">Partnership distributions.</E>
                             A partnership that is a transferee because it makes a distribution may rely on its books and records to determine that as of the determination date either paragraph (b)(4)(i)(A) or (B) of this section is satisfied.
                        </P>
                        <P>
                            (5) 
                            <E T="03">Less than 10 percent effectively connected taxable income</E>
                            —(i) 
                            <E T="03">In general.</E>
                             A transferee (other than a partnership making a distribution) may rely on a certification from the transferor that states that—
                        </P>
                        <P>(A) For the transferor's immediately prior taxable year and the two preceding taxable years, the transferor was at all times a partner in the partnership;</P>
                        <P>
                            (B) The transferor's allocable share of effectively connected taxable income determined under § 1.1446-2 (as provided on Form 8805, 
                            <E T="03">Foreign Partner's Information Statement of Section 1446 Withholding Tax</E>
                            ) (ECTI), including any ECTI allocable to a partner that bears a relationship to the transferor described in sections 267(b) or 707(b)(1), was less than $1 million in each of the taxable years described in paragraph (b)(5)(i)(A) of this section;
                        </P>
                        <P>
                            (C) The transferor's allocable share of ECTI in each of the taxable years described in paragraph (b)(5)(i)(A) of this section was less than 10 percent of the transferor's total distributive share of net income from the partnership for that year as determined under subchapter K of the Internal Revenue Code (as provided on Schedule K-1 (Form 1065), 
                            <E T="03">Partner's Share of Income, Deductions, Credits, etc.</E>
                            ); and
                        </P>
                        <P>(D) The transferor's distributive share of income or gain that is effectively connected with the conduct of a trade or business within the United States or deductions or losses properly allocated and apportioned to that income in each of the taxable years described in paragraph (b)(5)(i)(A) of this section has been reported on a Federal income tax return (either filed by the transferor or, in the case of transferor that is a partnership, filed by its direct or indirect nonresident alien individual or foreign corporate partners) on or before the due date (including extensions), and all amounts due with respect to the reported amounts has been timely paid to the IRS, provided that the return was required to be filed when the transferor furnishes the certification (taking into account any extensions of time to file).</P>
                        <P>
                            (ii) 
                            <E T="03">Immediately prior taxable year</E>
                            —(A) 
                            <E T="03">In general.</E>
                             The transferor's immediately prior taxable year is the transferor's most recent taxable year—
                        </P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) With or within which a taxable year of the partnership ended; and
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) For which a Schedule K-1 (Form 1065) was due (including extensions) or furnished (if earlier) before the transfer.
                        </P>
                        <P>
                            (B) 
                            <E T="03">Limitation.</E>
                             A transferee may not rely on a certification that is provided before the transferor's receipt of the Schedule K-1 (Form 1065) described in paragraph (b)(5)(ii)(A) of this section.
                        </P>
                        <P>
                            (iii) 
                            <E T="03">No Form 8805</E>
                            —(A) 
                            <E T="03">In general.</E>
                             Except as provided in paragraph (b)(5)(iii)(B) of this section, a transferor that does not receive Form 8805 because 
                            <PRTPAGE P="21218"/>
                            it had no ECTI for which the partnership paid section 1446 tax (within the meaning in § 1.1446-2(a)) in any of the years described in paragraph (b)(5)(i)(A) of this section may not make the certification provided in this paragraph (b)(5).
                        </P>
                        <P>
                            (B) 
                            <E T="03">Exception.</E>
                             If, in any of the years described in paragraph (b)(5)(i)(A) of this section, a transferor has an allocable share of loss that is effectively connected with the conduct of a trade or business within the United States, or has deductions properly allocated and apportioned to income that is effectively connected with the conduct of a trade or business within the United States from the partnership, paragraph (b)(5)(iii)(A) of this section does not apply by reason of a lack of Form 8805 with respect to that year, and the transferor is treated as having an allocable share of ECTI of zero in that year for purposes of paragraph (b)(5)(i)(C) of this section.
                        </P>
                        <P>
                            (iv) 
                            <E T="03">No net distributive share of income.</E>
                             A transferor that did not have a net distributive share of income in any year described in paragraph (b)(5)(i)(A) of this section cannot provide the certification described in this paragraph (b)(5).
                        </P>
                        <P>
                            (v) 
                            <E T="03">Partnership distributions.</E>
                             A partnership that is a transferee by reason of making a distribution may rely on its books and records to determine that the requirements in paragraphs (b)(5)(i)(A) through (C) of this section have been satisfied (subject to the rules in paragraphs (b)(5)(ii) through (iv) of this section). The partnership must also obtain a representation from the transferor stating that the requirement in paragraph (b)(5)(i)(D) of this section has been satisfied.
                        </P>
                        <P>
                            (vi) 
                            <E T="03">No certification when reporting is incorrect.</E>
                             A transferor may not make the certification described in this paragraph (b)(5) if it has actual knowledge that the information relevant to the certification that is reported by the partnership on any Form 8805 or Schedule K-1 (Form 1065) is incorrect.
                        </P>
                        <P>
                            (6) 
                            <E T="03">Certification of nonrecognition by transferor</E>
                            —(i) 
                            <E T="03">In general.</E>
                             A transferee may rely on a certification from the transferor that states that by reason of the operation of a nonrecognition provision of the Internal Revenue Code the transferor is not required to recognize any gain or loss with respect to the transfer. The certification must briefly describe the transfer and provide the relevant law and facts relating to the certification.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Partial nonrecognition.</E>
                             Paragraph (b)(6)(i) of this section does not apply if only a portion of the gain realized on the transfer is subject to a nonrecognition provision. However, see paragraph (c)(4)(v) of this section for rules applicable to a transferor's claim for partial nonrecognition.
                        </P>
                        <P>
                            (7) 
                            <E T="03">Income tax treaties</E>
                            —(i) 
                            <E T="03">In general.</E>
                             A transferee may rely on a certification from the transferor that states that the transferor is not subject to tax on any gain from the transfer pursuant to an income tax treaty in effect between the United States and a foreign country if the requirements of this paragraph (b)(7) are met. The transferor must include with the certification a withholding certificate (on a Form W-8BEN, 
                            <E T="03">Certificate of Foreign Status of Beneficial Owner for United States Tax Withholding and Reporting (Individuals),</E>
                             or Form W-8BEN-E, 
                            <E T="03">Certificate of Status of Beneficial Owner for United States Tax Withholding and Reporting (Entities)</E>
                            ) that meets the requirements for validity under § 1.1446-1(c)(2)(iv) (or an applicable substitute form that meets the requirements under § 1.1446-1(c)(5)) and that contains the information necessary to support the claim for treaty benefits. A transferee may rely on a certification of treaty benefits only if, within 30 days after the date of the transfer, the transferee mails a copy of the certification to the Internal Revenue Service, at the address provided in § 1.1445-1(g)(10), together with a cover letter providing the name, TIN, and address of the transferee and the partnership in which an interest was transferred.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Treaty claim for less than all of the gain.</E>
                             Paragraph (b)(7)(i) of this section does not apply if treaty benefits apply to only a portion of the gain from the transfer. However, see paragraph (c)(4)(vi) of this section for rules applicable to situations in which treaty benefits apply to only a portion of the gain.
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Exclusive means to claim an exception from withholding based on treaty benefits.</E>
                             A transferor claiming treaty benefits with respect to all of the gain from the transfer must use the exception in this paragraph (b)(6) and not any other exception or determination procedure in paragraphs (b) and (c) of this section to claim an exception to withholding by reason of a claim of treaty benefits.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Determining the amount to withhold</E>
                            —(1) 
                            <E T="03">In general.</E>
                             A transferee that is required to withhold under this section must withhold 10 percent of the amount realized on the transfer of the partnership interest, except as otherwise provided in this paragraph (c). Any procedures in this paragraph (c) apply solely for purposes of determining the amount to withhold under section 1446(f)(1) and this section. A transferee may not rely on a certification if it has actual knowledge that the certification is incorrect or unreliable. A partnership that is a transferee because it makes a distribution may not rely on its books and records if it knows, or has reason to know, that the information is incorrect or unreliable.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Amount realized</E>
                            —(i) 
                            <E T="03">In general.</E>
                             The amount realized on the transfer of the partnership interest is determined under section 1001 (including §§ 1.1001-1 through 1.1001-5) and section 752 (including § 1.752-1 through 1.752-7). Thus, the amount realized includes the amount of cash paid (or to be paid), the fair market value of other property transferred (or to be transferred), the amount of any liabilities assumed by the transferee or to which the partnership interest is subject, and the reduction in the transferor's share of partnership liabilities. In the case of a distribution, the amount realized is the sum of the amount of cash distributed (or to be distributed), the fair market value of property distributed (or to be distributed), and the reduction in the transferor's share of partnership liabilities.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Alternative procedures for transferee to determine share of partnership liabilities</E>
                            —(A) 
                            <E T="03">In general.</E>
                             A transferee (other than a partnership that is a transferee because it makes a distribution), as an alternative to determining the share of partnership liabilities under paragraph (c)(2)(i) of this section, may use the procedures of this paragraph (c)(2)(ii) to determine the extent to which a reduction in partnership liabilities is included in the amount realized.
                        </P>
                        <P>
                            (B) 
                            <E T="03">Certification of liabilities by transferor.</E>
                             Except as otherwise provided in this section, a transferee may rely on a certification from a transferor, other than a controlling partner, that provides the amount of the transferor's share of partnership liabilities reported on the most recent Schedule K-1 (Form 1065) issued by the partnership. If the transferor's actual share of liabilities at the time of the transfer differs from the amount reported on that Schedule K-1 (Form 1065), the certification will not be treated as incorrect or unreliable if the transferor also certifies that it does not have actual knowledge of any events occurring after receiving the Schedule K-1 (Form 1065) that would cause the amount of the transferor's share of partnership liabilities at the time of the transfer to differ by more than 25 percent from the amount shown on the Schedule K-1 (Form 1065). A transferee may not rely on a certification if the last 
                            <PRTPAGE P="21219"/>
                            day of the partnership taxable year for which the Schedule K-1 (Form 1065) was provided was more than 22 months before the date of the transfer.
                        </P>
                        <P>
                            (C) 
                            <E T="03">Certification of liabilities by partnership.</E>
                             A transferee may rely on a certification from a partnership that provides the amount of the transferor's share of partnership liabilities on the determination date. If the transferor's actual share of liabilities at the time of the transfer differs from the amount on the certification, the certification will not be treated as incorrect or unreliable if the partnership also certifies that it does not have actual knowledge of any events occurring after the determination date that would cause the amount of the transferor's share of partnership liabilities at the time of the transfer to differ by more than 25 percent from the amount shown on the certification by the partnership for the determination date.
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Partnership's determination of partnership liabilities for distributions.</E>
                             A partnership that is a transferee because it makes a distribution may rely on its books and records to determine the extent to which the transferor's share of partnership liabilities on the determination date are included in the amount realized. The information in the books and records will not be treated as incorrect or unreliable unless the partnership has actual knowledge, on or before the date of the distribution, of any events occurring after the determination date that would cause the amount of the transferor's share of partnership liabilities at the time of the transfer to differ by more than 25 percent from the amount determined by the partnership as of the determination date.
                        </P>
                        <P>
                            (iv) 
                            <E T="03">Certification by a foreign partnership of non-foreign status of its partners</E>
                            —(A) 
                            <E T="03">In general.</E>
                             When a transferor is a foreign partnership, a transferee may use the procedures of this paragraph (c)(2)(iv) to determine the amount realized. For this purpose, the transferee may rely on a certification from the transferor providing the modified amount realized, and may treat the modified amount realized as the amount realized.
                        </P>
                        <P>
                            (B) 
                            <E T="03">Determining modified amount realized.</E>
                             The modified amount realized is determined by multiplying the amount realized (as determined under this paragraph (c)(2), without regard to this paragraph (c)(2)(iv)) by the aggregate percentage computed as of the determination date. The aggregate percentage is the percentage of the gain (if any) arising from the transfer that would be allocated to presumed foreign persons. For this purpose, a presumed foreign person is any direct or indirect partner of the transferor that has not provided a certification of non-foreign status that meets the requirements of paragraph (b)(2) of this section. For purposes of this paragraph (c)(2)(iv), an indirect partner is a person that owns an interest in the transferor indirectly through one or more foreign partnerships.
                        </P>
                        <P>
                            (C) 
                            <E T="03">Certification.</E>
                             The certification is made by providing a withholding certificate (on Form W-8IMY, 
                            <E T="03">Certificate of Foreign Intermediary, Foreign Flow-Through Entity, or Certain U.S. Branches for United States Tax Withholding and Reporting</E>
                            ) and a withholding statement that provides the percentage of gain allocable to each direct or indirect partner and that provides whether each such person is a United States person or presumed foreign person. The certification must also include a certification of non-foreign status that meets the requirements of paragraph (b)(2) of this section from each of the United States persons that are direct or indirect partners of the transferor that are identified as a United States person on the withholding statement.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Lack of money or property or lack of knowledge regarding liabilities.</E>
                             The amount to withhold equals the amount realized determined without regard to any decrease in the transferor's share of partnership liabilities if—
                        </P>
                        <P>(i) The amount otherwise required to be withheld under this paragraph (c) would exceed the amount realized determined without regard to the decrease in the transferor's share of partnership liabilities; or</P>
                        <P>(ii) The transferee is unable to determine the amount realized because it does not have actual knowledge of the transferor's share of partnership liabilities (and has not received or cannot rely on a certification described in paragraph (c)(2)(ii)(B) or (C) of this section).</P>
                        <P>
                            (4) 
                            <E T="03">Certification of maximum tax liability</E>
                            —(i) 
                            <E T="03">In general.</E>
                             A transferee may use the procedures of this paragraph (c)(4) for determining the amount to withhold for purposes of section 1446(f)(1) and paragraph (a) of this section. A transferee (other than a partnership that is a transferee because it makes a distribution) may rely on a certification from a transferor that is a foreign corporation, a nonresident alien individual or a foreign partnership regarding the transferor's maximum tax liability as described in paragraph (c)(4)(ii) of this section. A partnership that is a transferee because it makes a distribution may instead rely on its books and records to determine the transferor's maximum tax liability if the books and records includes the information required by paragraphs (c)(4)(iii) and (c)(4)(iv) of this section. A transferor that is a foreign partnership is treated as a nonresident alien individual for purposes of determining the transferor's maximum tax liability.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Maximum tax liability.</E>
                             For purposes of this paragraph (c)(4), the term 
                            <E T="03">maximum tax liability</E>
                             means the amount of the transferor's effectively connected gain (as determined under paragraph (c)(4)(iii)(E) of this section) multiplied by the applicable percentage, as defined in § 1.1446-3(a)(2).
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Required information.</E>
                             The certification must include—
                        </P>
                        <P>(A) A statement that the transferor is either a nonresident alien individual, a foreign corporation, or a foreign partnership;</P>
                        <P>(B) The transferor's adjusted basis in the transferred interest on the determination date;</P>
                        <P>(C) The transferor's amount realized (determined in accordance with paragraph (c)(2) of this section) on the determination date;</P>
                        <P>(D) Whether the transferor remains a partner immediately after the transfer;</P>
                        <P>(E) The amount of outside ordinary gain and outside capital gain that would be recognized and treated as effectively connected gain under § 1.864(c)(8)-1(b) on the determination date (effectively connected gain);</P>
                        <P>(F) The transferor's maximum tax liability on the determination date;</P>
                        <P>(G) A representation from the transferor that the transferor determined the amounts described in paragraph (c)(4)(iii)(E) of this section based on the statement described in paragraph (c)(4)(iv) of this section; and</P>
                        <P>(H) A representation from the transferor that it has provided the transferee with a copy of the statement described in paragraph (c)(4)(iv) of this section.</P>
                        <P>
                            (iv) 
                            <E T="03">Partnership statement.</E>
                             A transferor may make the representation in paragraph (c)(4)(iii)(G) of this section only if the partnership provides to the transferor a statement (that meets the requirements for a certification under the general rules for applicability in § 1.1446(f)-1(c)) that includes—
                        </P>
                        <P>(A) The partnership's name, address, and TIN; and</P>
                        <P>
                            (B) The transferor's aggregate deemed sale EC ordinary gain, within the meaning of § 1.864(c)(8)-1(c)(3)(ii)(A) (if any) and the transferor's aggregate deemed sale EC capital gain, within the meaning of § 1.864(c)(8)-1(c)(3)(ii)(B) (if any), in each case, on the determination date.
                            <PRTPAGE P="21220"/>
                        </P>
                        <P>
                            (v) 
                            <E T="03">Partial nonrecognition.</E>
                             If a nonrecognition provision applies to only a portion of the gain realized on the transfer, a certification described in this paragraph (c)(4) may be relied upon only if the certification also includes the information required in paragraph (b)(6) of this section.
                        </P>
                        <P>
                            (vi) 
                            <E T="03">Income tax treaties.</E>
                             If only a portion of the gain on the transfer is not subject to tax pursuant to an income tax treaty in effect between the United States and a foreign country, a certification described in paragraph (c)(4)(i) of this section may be relied upon only if the certification also complies with the requirements of paragraph (b)(7) of this section, including the requirement that the determination that gain from the transfer is not subject to tax pursuant to an income tax treaty be made with respect to the transferor, and that the transferee mail a copy of the relevant certification described in this paragraph (c)(4) to the IRS.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Reporting and paying withheld amounts</E>
                            —(1) 
                            <E T="03">In general.</E>
                             A transferee required to withhold under this section must report and pay any tax withheld by the 20th day after the date of the transfer using Forms 8288, 
                            <E T="03">U.S. Withholding Tax Return for Dispositions by Foreign Persons of U.S. Real Property Interests,</E>
                             and 8288-A, 
                            <E T="03">Statement of Withholding on Dispositions by Foreign Persons of U.S. Real Property Interests,</E>
                             in accordance with the instructions to those forms. The IRS will stamp Form 8288-A to show receipt and mail a stamped copy to the transferor (at the address reported on the form). 
                            <E T="03">See</E>
                             paragraph (e)(2) of this section for the procedures for the transferor to claim a credit for amounts withheld. Forms 8288 and 8288-A must include the TINs of both the transferor and the transferee. If any required TIN is not provided, the transferee must still report and pay any tax withheld on Form 8288.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Certification of withholding to partnership for purposes of section 1446(f)(4).</E>
                             A transferee (other than a partnership that is a transferee because it makes a distribution) must certify to the partnership the extent to which it has satisfied its obligation to withhold under this section no later than 10 days after the transfer. The certification must either include a copy of Form 8288-A that the transferee files with respect to the transfer, or state the amount realized and the amount withheld on the transfer of the partnership interest. The certification must also include any certifications that the transferee relied on to apply an exception to withholding under paragraph (b) of this section or to determine the amount to withhold under paragraph (c) of this section. See § 1.1446(f)-3 for rules regarding a partnership's obligation to withhold on distributions to a transferee when this certification establishes only partial satisfaction of the required amount, is not provided, or cannot be relied upon.
                        </P>
                        <P>
                            (e) 
                            <E T="03">Effect of withholding on transferor—</E>
                            (1) 
                            <E T="03">In general.</E>
                             The withholding of tax by a transferee under this section does not relieve a foreign person from filing a U.S. tax return with respect to the transfer. See §§ 1.6012-1(b)(1), 1.6012-2(g)(1), and 1.6031(a)-1. Further, the withholding of tax by a transferee does not relieve a nonresident alien individual or foreign corporation subject to tax under section 864(c)(8) from paying any tax due with the return that has not been fully satisfied through withholding.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Manner of obtaining credit</E>
                            —(i) 
                            <E T="03">Individuals and corporations.</E>
                             Except as provided in paragraph (e)(3) of this section, an individual or corporation may claim a credit under section 33 for the amount withheld under this section by attaching to its applicable return the stamped copy of Form 8288-A provided to it under paragraph (d)(1) of this section. 
                            <E T="03">See also</E>
                             § 1.1462-1.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Partnerships.</E>
                             For a rule allowing a foreign partnership that is a transferor to claim a credit for the amount withheld under this section against its tax liability under section 1446(a), see § 1.1446-3(c)(4).
                        </P>
                        <P>
                            (3) 
                            <E T="03">Failure to receive Form 8288-A.</E>
                             If a stamped copy of Form 8288-A has not been provided to the transferor by the IRS, the transferor may establish the amount of tax withheld by the transferee by attaching to its return substantial evidence of the amount. The transferor must attach to its return a statement that includes all of the information otherwise required to be provided on Form 8288-A.
                        </P>
                        <P>
                            (f) 
                            <E T="03">Applicability date.</E>
                             This section applies to transfers that occur on or after the date that is 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1.1446(f)-3 </SECTNO>
                        <SUBJECT>Partnership's requirement to withhold under section 1446(f)(4) on distributions to transferee.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Partnership's obligation to withhold amounts not withheld by the transferee</E>
                            —(1) 
                            <E T="03">In general.</E>
                             If a transferee fails to withhold any amount required to be withheld under § 1.1446(f)-2, the partnership in which the interest was transferred must withhold from any distributions made to the transferee pursuant to this section. To determine its withholding obligation under this paragraph (a)(1), a partnership may rely on a certification received from the transferee described in § 1.1446(f)-2(d)(2) unless it knows, or has reason to know, that the certification is incorrect or unreliable.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Notification by IRS.</E>
                             A partnership that receives notification from the IRS that a transferee has provided incorrect information regarding the amount realized or amount withheld on the certification described in § 1.1446(f)-2(d)(2), or has failed to pay the IRS the amount reported as withheld on the certification, must withhold the amount prescribed in the notification on distributions to the transferee made on or after the date that is 15 days after it receives the notification. For this purpose, the amount realized is not treated as incorrect if the transferee properly relied on a certification to compute the amount realized pursuant to § 1.1446(f)-2(c)(2).
                        </P>
                        <P>
                            (b) 
                            <E T="03">Exceptions to withholding</E>
                            —(1) 
                            <E T="03">Withholding has been satisfied by transferee.</E>
                             A partnership is not required to withhold under paragraph (a)(1) of this section if it relies on a certification described in § 1.1446(f)-2(d)(2) received from the transferee (within the time prescribed in that section) that states that an exception to withholding described in § 1.1446(f)-2(b) applies or that the transferee withheld the full amount required to be withheld (taking into account any adjustments under § 1.1446(f)-2(c)) under § 1.1446(f)-2.
                        </P>
                        <P>
                            (2) 
                            <E T="03">PTP interests</E>
                            —(i) 
                            <E T="03">In general.</E>
                             Except as provided in paragraph (b)(2)(ii) of this section, a partnership is not required to withhold under this section on distributions made with respect to a PTP interest.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Exception for a false qualified notice.</E>
                             If a publicly traded partnership determines (including by reason of notification from the IRS) that it has published a qualified notice that falsely states that either the exception described in § 1.1446(f)-4(b)(3) (the 10-percent exception) or the exception described in § 1.1446(f)-4(b)(4) (the qualified current income exception) applies, the publicly traded partnership must withhold under this section on distributions to the transferee in an amount equal to the amount that a broker failed to withhold under § 1.1446(f)-4 due to reliance on the qualified notice, plus interest.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Distributing partnerships.</E>
                             A partnership that is a transferee because it makes a distribution is not required to withhold under this section.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Withholding rules</E>
                            —(1) 
                            <E T="03">Timing of withholding</E>
                            —(i) 
                            <E T="03">In general.</E>
                             A partnership required to withhold under paragraph (a)(1) of this section must withhold on distributions made to the transferee beginning on the later of—
                            <PRTPAGE P="21221"/>
                        </P>
                        <P>(A) The date that is 30 days after the date of transfer; or</P>
                        <P>(B) The date that is 15 days after the date on which the partnership acquires actual knowledge that the transfer has occurred.</P>
                        <P>
                            (ii) 
                            <E T="03">Satisfaction of withholding obligation.</E>
                             A partnership is treated as satisfying its withholding obligation under paragraph (a)(1) of this section and may stop withholding on distributions to the transferee on the earlier of—
                        </P>
                        <P>(A) The date on which the partnership completes withholding and paying the amount required to be withheld under paragraph (c)(2) of this section;</P>
                        <P>(B) The date on which the partnership receives and may rely on a certification from the transferee described in § 1.1446(f)-2(d)(2) (without regard to whether the certification is received by the time prescribed in that section) that claims an exception to withholding under § 1.1446(f)-2(b); or</P>
                        <P>(C) If a partnership interest is not a PTP interest, the date on which the transferee no longer owns an interest in the partnership, unless the partnership has actual knowledge that any successor to the transferee is a person that bears a relationship described in section 267(b) or 707(b)(1) with respect to the transferee or the transferor from which the transferee acquired the interest.</P>
                        <P>
                            (2) 
                            <E T="03">Amount to withhold</E>
                            —(i) 
                            <E T="03">In general.</E>
                             A partnership required to withhold under paragraph (a)(1) of this section must withhold the full amount of each distribution made to the transferee until it has withheld—
                        </P>
                        <P>(A) A tax of 10 percent of the amount realized (determined solely under § 1.1446(f)-2(c)(2)(i) or, in the case of a publicly traded partnership, solely under § 1.1446(f)-4(c)(2)(i)) on the transfer, reduced by any amount withheld by the transferee, plus</P>
                        <P>(B) Any interest computed under paragraph (c)(2)(ii) of this section.</P>
                        <P>
                            (ii) 
                            <E T="03">Computation of interest.</E>
                             The amount of interest required to be withheld under paragraph (a)(1) of this section is the amount of interest that would be required to be paid under section 6601 and § 301.6601-1 if the amount that should have been withheld by the transferee was considered an underpayment of tax. For this purpose, interest is payable between the date that is 20 days after the date of the transfer and the date on which the tax due under paragraph (a)(1) of this section is paid to the IRS.
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Certifications required.</E>
                             For purposes of paragraph (c)(2)(i)(A) of this section, a partnership must determine the amount realized on the transfer and any amount withheld by the transferee based on a certification from the transferee described in § 1.1446(f)-2(d)(2), without regard to whether the certification is received by the time prescribed in that section. A partnership that does not receive or cannot rely on a certification from the transferee described in § 1.1446(f)-2(d)(2) must withhold tax equal to the full amount of each distribution made to the transferee until it receives a certification that it can rely on.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Coordination with other withholding provisions.</E>
                             Any amount required to be withheld on a distribution under any other provision of the Internal Revenue Code is not also required to be withheld under section 1446(f)(4) or this section.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Reporting and paying withheld amounts.</E>
                             The partnership must report and pay the tax withheld using Forms 8288, 
                            <E T="03">U.S. Withholding Tax Return for Dispositions by Foreign Persons of U.S. Real Property Interests,</E>
                             and 8288-C, 
                            <E T="03">Statement of Withholding Under Section 1446(f)(4) for Withholding on Dispositions by Foreign Persons of Partnership Interests,</E>
                             as provided in forms, instructions, or other guidance.
                        </P>
                        <P>
                            (e) 
                            <E T="03">Effect of withholding on transferor and transferee</E>
                            —(1) 
                            <E T="03">Transferor.</E>
                             The withholding of tax by a partnership under this section does not relieve a foreign person from filing a U.S. income tax return with respect to the transfer. See §§ 1.6012-1(b)(1), 1.6012-2(g)(1), and 1.6031(a)-1. Further, the withholding of tax by a partnership does not relieve a nonresident alien individual or foreign corporation subject to tax under section 864(c)(8) from paying any tax due with the return that has not been fully satisfied through withholding. An individual or corporation is not allowed a credit under section 33 for amounts withheld on distributions to the transferee under this section. See, however, §§ 1.1446(f)-5(a) and 1.1463-1(a), which generally provide that tax will not be recollected if paid by another person.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Transferee.</E>
                             A transferee is treated as satisfying its withholding tax liability under § 1.1446(f)-2 to the extent that a partnership withholds tax (which does not include interest) from the transferee under this section. Interest computed under paragraph (c)(2)(ii) of this section that is withheld by the partnership from the transferee is treated as interest paid by the transferee with respect to its withholding tax liability under § 1.1446(f)-2. A transferee may not obtain a refund when the amount of tax withheld under this section exceeds the transferee's withholding tax liability under § 1.1446(f)-2. Instead, only the partnership may claim a refund on behalf of the transferee for the excess amount under this section.
                        </P>
                        <P>
                            (f) 
                            <E T="03">Applicability date.</E>
                             This section applies to transfers that occur on or after the date that is 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1.1446(f)-4 </SECTNO>
                        <SUBJECT>Withholding on the transfer of a publicly traded partnership interest.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Broker's obligation to withhold on a transfer of a PTP interest</E>
                            —(1) 
                            <E T="03">In general.</E>
                             If a transfer of a PTP interest is effected through one or more brokers, the transferee is not required to withhold under section 1446(f)(1) and § 1.1446(f)-2. Rather, any broker required to withhold under paragraph (a)(2) of this section must withhold a tax equal to 10 percent of the amount realized (as defined in paragraph (c)(2) of this section) on the transfer of a PTP interest, except as otherwise provided in this section. For rules regarding the application of section 1446(f)(4) and § 1.1446(f)-3 to a publicly traded partnership, see § 1.1446(f)-3(b)(2).
                        </P>
                        <P>
                            (2) 
                            <E T="03">Broker's requirement to withhold</E>
                            —(i) 
                            <E T="03">Payments to foreign brokers.</E>
                             A broker that pays the amount realized from the transfer of a PTP interest to another broker that is a foreign person must withhold under this section unless the foreign person is—
                        </P>
                        <P>(A) A qualified intermediary (as defined in § 1.1441-1(e)(5)(ii)) that provides a valid qualified intermediary withholding certificate (as described in § 1.1441-1(e)(3)(ii)) that states that it assumes primary withholding responsibility under chapter 3; or</P>
                        <P>(B) A U.S. branch of a foreign person (as described in § 1.1441-1(b)(2)(iv)) that provides a valid U.S. branch withholding certificate (as described in § 1.1441-1(e)(3)(v)) that states that it agrees to be treated as a U.S. person with respect to any payment associated with the certificate.</P>
                        <P>
                            (ii) 
                            <E T="03">Brokers with customer relationship with transferor.</E>
                             A broker that effects the transfer for the transferor as its customer (as defined in § 1.6045-1(a)(2)) is required to withhold under this section.
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Exception.</E>
                             A broker is not required to withhold under this section if it knows that the withholding obligation has already been satisfied.
                        </P>
                        <P>
                            (iv) 
                            <E T="03">Determination of foreign broker's status.</E>
                             For purposes of paragraph (a)(2)(i) of this section, a broker must treat another broker as a foreign person unless it obtains documentation (including a certification of non-foreign status) establishing that the other broker is a U.S. person.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Exceptions to withholding</E>
                            —(1) 
                            <E T="03">In general.</E>
                             A broker is not required to 
                            <PRTPAGE P="21222"/>
                            withhold under this section if it properly relies on a certification described in paragraph (b)(2) or (b)(6) of this section, a qualified notice described in paragraph (b)(3) or (b)(4) of this section, or if the exception described in paragraph (b)(5) of this section applies. A broker may not rely on a certification described in this paragraph (b) if it has actual knowledge that the certification is incorrect or unreliable.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Certification of non-foreign status.</E>
                             A broker may rely on a certification of non-foreign status that it obtains from the transferor. A certification of non-foreign status under this section means a Form W-9, 
                            <E T="03">Request for Taxpayer Identification Number and Certification,</E>
                             or valid substitute form, that meets the requirements of § 1.1441-1(d)(2). For this purpose, a broker may rely on a valid form that it already possesses from the transferor. A broker may instead rely on certification from a second broker (as defined in § 1.6045-1(a)(1)) that acts as an agent for the transferor when the second broker does not receive the amount realized from the transfer of the PTP interest. This certification must state that the second broker has collected a valid certification of non-foreign status (within the meaning of this paragraph (b)(2)) from the transferor, and it must include the transferor's TIN and status as a foreign or U.S. person.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Less than 10 percent effectively connected gain by partnership</E>
                            —(i) 
                            <E T="03">In general.</E>
                             A broker may rely on a qualified notice described in paragraph (b)(3)(iii) of this section that states that the 10-percent exception applies, as determined under paragraph (b)(3)(ii) of this section.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">10-percent exception</E>
                            —(A) 
                            <E T="03">In general.</E>
                             The 10-percent exception applies to a transfer if, on the PTP designated date described in paragraph (b)(3)(ii)(B) of this section, had the publicly traded partnership sold all of its assets at fair market value in the manner described in § 1.864(c)(8)-1(c), either—
                        </P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) The amount of gain that would have been effectively connected with the conduct of a trade or business within the United States would be less than 10 percent of the total gain; or
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) No gain would have been effectively connected with the conduct of a trade or business within the United States.
                        </P>
                        <P>
                            (B) 
                            <E T="03">PTP designated date.</E>
                             The PTP designated date for a transfer is any date for a deemed sale determination that is designated by the publicly traded partnership in a qualified notice described in paragraph (b)(3)(iii) of this section, provided that the PTP designated date occurs on or after the date that is 92 days before the date on which the publicly traded partnership posted the qualified notice naming the PTP designated date.
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Qualified notice</E>
                            —(A) 
                            <E T="03">In general.</E>
                             Except as provided in paragraph (b)(3)(iii)(B) and (C) of this section, a qualified notice described in this paragraph (b)(3)(iii) is the most recent qualified notice (within the meaning of § 1.1446-4(b)(4)) posted by the publicly traded partnership.
                        </P>
                        <P>
                            (B) 
                            <E T="03">Qualified notice posting date requirement.</E>
                             A qualified notice is described in this paragraph (b)(3)(iii) only if the publicly traded partnership has posted it within the 92-day period ending on the date of the transfer.
                        </P>
                        <P>
                            (C) 
                            <E T="03">Recent posting of qualified notice.</E>
                             If the most recent qualified notice posted by the publicly traded partnership was posted during the 10-day period ending on the date of the transfer, a broker may instead rely on the immediately preceding qualified notice (within the meaning of § 1.1446-4(b)(4)) posted by the publicly traded partnership, provided that it satisfies the condition described in paragraph (b)(3)(iii)(B) of this section.
                        </P>
                        <P>
                            (4) 
                            <E T="03">Distribution made from current income</E>
                            —(i) 
                            <E T="03">In general.</E>
                             A broker is not required to withhold under this section on a distribution by a publicly traded partnership if the entire amount of a distribution is designated, on a qualified notice (within the meaning of § 1.1446-4(b)(4)) posted with respect to that distribution, as a qualified current income distribution (within the meaning of paragraph (b)(4)(ii) of this section).
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Qualified current income distribution.</E>
                             A qualified current income distribution is a distribution that does not exceed the net income of the publicly traded partnership since the record date (within the meaning of 17 CFR 240.14a-1(h) or its successor provision) of the immediately preceding distribution made by the publicly traded partnership.
                        </P>
                        <P>
                            (5) 
                            <E T="03">Amount subject to withholding under section 3406.</E>
                             A broker is not required to withhold under this section if the amount realized from the transfer of the PTP interest is subject to withholding under § 31.3406(b)(3)-2 of this chapter.
                        </P>
                        <P>
                            (6) 
                            <E T="03">Income tax treaties.</E>
                             A broker may rely on a certification from the transferor that states that the transferor is not subject to tax on any gain from the transfer pursuant to an income tax treaty in effect between the United States and a foreign country if the requirements of this paragraph (b)(6) are met. The transferor must include with the certification a withholding certificate (on a Form W-8BEN, 
                            <E T="03">Certificate of Foreign Status of Beneficial Owner for United States Tax Withholding and Reporting (Individuals),</E>
                             or Form W-8BEN-E, 
                            <E T="03">Certificate of Status of Beneficial Owner for United States Tax Withholding and Reporting (Entities)</E>
                            ) that meets the requirements for validity under § 1.1446-1(c)(2)(iv) (or an applicable substitute form that meets the requirements under § 1.1446-1(c)(5)) and that contains the information necessary to support the claim for treaty benefits. For purposes of this paragraph (b)(6), a broker may rely on a withholding certificate that it already possesses from the transferor unless it has actual knowledge that the information is incorrect or unreliable. This exception does not apply if treaty benefits apply to only a portion of the gain from the transfer.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Determining the amount to withhold</E>
                            —(1) 
                            <E T="03">In general.</E>
                             A broker that is required to withhold under this section must withhold 10 percent of the amount realized on the transfer of the PTP interest, except as provided in this paragraph (c). Any procedures in this paragraph (c) apply solely for purposes of determining the amount to withhold under section 1446(f)(1) and this section. A broker may not rely on a certification described in this paragraph (c) if it has actual knowledge that the certification is incorrect or unreliable.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Amount realized</E>
                            —(i) 
                            <E T="03">In general.</E>
                             Solely for purposes of this section, the amount realized is the amount of gross proceeds (as defined in § 1.6045-1(d)(5)) paid or credited upon the transfer to the customer or other broker (as applicable), or, in the case of a distribution, the amount of cash distributed (or to be distributed) and the fair market value of property distributed (or to be distributed).
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Certification by a foreign partnership of non-foreign status of its partners</E>
                            —(A) 
                            <E T="03">In general.</E>
                             When a transferor is a foreign partnership, a broker may use the procedures of this paragraph (c)(2)(ii) to determine the amount realized. For this purpose, the broker may rely on a certification from the transferor providing the modified amount realized, and may treat the modified amount realized as the amount realized.
                        </P>
                        <P>
                            (B) 
                            <E T="03">Determining modified amount realized.</E>
                             The modified amount realized is determined by multiplying the amount realized (as determined under this paragraph (c)(2), without regard to this paragraph (c)(2)(ii)) by the aggregate percentage computed as of the determination date. The aggregate percentage is the percentage of the gain 
                            <PRTPAGE P="21223"/>
                            (if any) arising from the transfer that would be allocated to presumed foreign persons. For this purpose, a presumed foreign person is any direct or indirect partner of the transferor that has not provided a certification of non-foreign status that meets the requirements of paragraph (b)(2) of this section. For purposes of this paragraph (c)(2)(ii), an indirect partner is a person that owns an interest in the transferor indirectly through one or more foreign partnerships.
                        </P>
                        <P>
                            (C) 
                            <E T="03">Certification.</E>
                             The certification is made by providing a withholding certificate (on Form W-8IMY, 
                            <E T="03">Certificate of Foreign Intermediary, Foreign Flow-Through Entity, or Certain U.S. Branches for United States Tax Withholding and Reporting</E>
                            ) and a withholding statement that provides the percentage of gain allocable to each direct or indirect partner and that provides whether each such person is a United States person or presumed foreign person. The certification must also include a certification of non-foreign status that meets the requirements of paragraph (b)(2) of this section from each of the United States persons that are direct or indirect partners of the transferor that are identified as a United States person on the withholding statement. For purposes of this paragraph (c)(2)(ii), a broker may rely on a withholding certificate and withholding statement that it already possesses from the partnership unless it has actual knowledge that the information is incorrect or unreliable.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Reporting and paying withheld amounts.</E>
                             A broker that is required to withhold under this section must pay the withheld tax pursuant to the deposit rules in § 1.6302-2. For rules regarding reporting on Forms 1042, 
                            <E T="03">Annual Withholding Tax Return for U.S. Source Income of Foreign Persons,</E>
                             and 1042-S, 
                            <E T="03">Foreign Person's U.S. Source Income Subject to Withholding,</E>
                             that apply to a broker that withholds under this section, see § 1.1461-1(b) and (c). For rules regarding when an amount realized on the transfer of a PTP interest is an amount subject to reporting, see § 1.1461-1(c)(2)(i)(Q). A broker that pays the amount realized to a foreign partnership must issue a Form 1042-S directly to the partnership rather than issuing a form to each of the partners of the partnership. 
                            <E T="03">See</E>
                             § 1.1461-1(c)(1)(ii)(A)(
                            <E T="03">8</E>
                            ) (treating the foreign partnership as a recipient for reporting purposes). A broker making a payment to a U.S. branch treated as a U.S. person must not treat the branch as a U.S. person for purposes of reporting the payment made to the branch. Therefore, a payment to that U.S. branch must be reported on Form 1042-S. 
                            <E T="03">See</E>
                             § 1.1461-1(c). A Form 1042-S issued directly to the transferor must include the TIN of the transferor unless the broker does not know the TIN at the time of issuance.
                        </P>
                        <P>
                            (e) 
                            <E T="03">Effect of withholding on transferor</E>
                            —(1) 
                            <E T="03">In general.</E>
                             The withholding of tax under this section does not relieve a foreign person from filing a U.S. tax return with respect to the transfer. 
                            <E T="03">See</E>
                             §§ 1.6012-1(b)(1), 1.6012-2(g)(1), and 1.6031(a)-1. Further, the withholding of tax by a broker does not relieve a nonresident alien individual or foreign corporation subject to tax under section 864(c)(8) from paying any tax due with the return that has not been fully satisfied through withholding.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Manner of obtaining credit</E>
                            —(i) 
                            <E T="03">Individuals and corporations.</E>
                             An individual or corporation may claim a credit under section 33 for the amount withheld under this section by attaching to its applicable return a copy of a Form 1042-S that includes its TIN.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Partnerships.</E>
                             For a rule allowing a foreign partnership that is a transferor to claim a credit for the amount withheld under this section against its obligation to withhold under section 1446(a), see § 1.1446-3(c)(4).
                        </P>
                        <P>
                            (f) 
                            <E T="03">Applicability date.</E>
                             This section applies to transfers that occur on or after the date that is 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1.1446(f)-5 </SECTNO>
                        <SUBJECT>Liability for failure to withhold.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Liability for failure to withhold.</E>
                             Every person required to withhold and pay tax under section 1446(f), but that fails to do so, is liable for the tax under section 1461. Under section 1463, if the tax required to be withheld is paid by another person required to withhold under section 1446(f) or by the nonresident alien individual or foreign corporation subject to tax under section 864(c)(8), the tax will not be recollected. However, any person that failed to withhold under section 1446(f) is in no case relieved from liability for any interest, penalties, or additions to tax that would otherwise apply. A partnership that failed to withhold and pay tax under § 1.1446(f)-3 is only liable for the amount of tax that it failed to collect (but not any interest computed on that amount under § 1.1446(f)-3(c)(2)(ii)), plus any interest, penalties, or additions to tax with regard to the partnership's failure to withhold.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Liability of agents</E>
                            —(1) 
                            <E T="03">Duty to provide notice of false certification.</E>
                             A transferee's or transferor's agent (other than a broker required to withhold under § 1.1446(f)-4) must provide notice to a transferee (or other person required to withhold) if that person is furnished with a certification described in §§ 1.1446(f)-1 through 1.1446(f)-4 and the agent knows that the certification is false. A person required to withhold may not rely on a certification if it receives the notice described in this paragraph (b)(1).
                        </P>
                        <P>
                            (2) 
                            <E T="03">Procedural requirements.</E>
                             Any agent who is required to provide notice under paragraph (b)(1) of this section must do so in writing (including by electronic submission) as soon as possible after learning of the false certification. If the agent first learns of the false certification before the date of transfer, notice must be given by the third day following that discovery but no later than the date of transfer (before the transferee's payment of consideration). If an agent first learns of a false certification after the date of transfer, notice must be given by the third day following that discovery. The notice must also explain the possible consequences to the recipient of a failure to withhold. The notice need not disclose the information on which the agent's statement is based. The agent must also furnish a copy of the notice to the IRS by the date on which the notice is required to be given to the recipient. The copy of the notice must be delivered to the address provided in § 1.1445-1(g)(10) and must be accompanied by a cover letter stating that the copy is being filed pursuant to the requirements of § 1.1446(f)-5(b)(2).
                        </P>
                        <P>
                            (3) 
                            <E T="03">Failure to provide notice.</E>
                             Any agent who is required to provide notice under paragraph (b)(1) of this section, but fails to do so in the manner required in paragraph (b)(2) of this section, is liable for the tax that the person who should have been provided notice in accordance with paragraph (b)(2) of this section was required to withhold under section 1446(f) if the notice had been given.
                        </P>
                        <P>
                            (4) 
                            <E T="03">Limitation on liability.</E>
                             An agent's liability under paragraph (b)(3) of this section is limited to the amount of compensation that the agent derives from the transaction. In addition, an agent that assists in the preparation of, or fails to disclose knowledge of, a false certification may be liable for civil and criminal penalties.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Applicability date.</E>
                             This section applies to transfers that occur on or after the date that is 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 10.</E>
                         Section 1.1461-1 is amended:
                    </AMDPAR>
                    <AMDPAR>
                        1. As proposed to be amended December 18, 2018, at 83 FR 64757:
                        <PRTPAGE P="21224"/>
                    </AMDPAR>
                    <AMDPAR>i. Paragraph (a)(1) is further amended by revising the sixth, seventh, and eighth sentences.</AMDPAR>
                    <AMDPAR>ii. Paragraph (c)(1)(i)(A) is further amended by revising the second and third sentences.</AMDPAR>
                    <AMDPAR>
                        2. By revising paragraph (c)(1)(ii)(A)(
                        <E T="03">8</E>
                        ).
                    </AMDPAR>
                    <AMDPAR>
                        3. By adding paragraph (c)(1)(ii)(B)(
                        <E T="03">5</E>
                        ).
                    </AMDPAR>
                    <AMDPAR>4. In paragraph (c)(2)(i) introductory text, by revising the first and second sentences.</AMDPAR>
                    <AMDPAR>5. In paragraph (c)(2)(i)(N), by removing the word “and” that follows the semi-colon.</AMDPAR>
                    <AMDPAR>6. In paragraph (c)(2)(i)(O), by removing the period at the end of the paragraph and adding “; and” in its place.</AMDPAR>
                    <AMDPAR>7. By adding paragraphs (c)(2)(i)(P) and (Q).</AMDPAR>
                    <AMDPAR>8. By adding a sentence at the end of paragraph (c)(4)(ii)(A).</AMDPAR>
                    <AMDPAR>9. Revising paragraph (i).</AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1.1461-1 </SECTNO>
                        <SUBJECT>Payment and returns of tax withheld.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>
                            (1) 
                            <E T="03">Deposits of tax.</E>
                             * * * With respect to withholding under section 1446, this section shall apply only to publicly traded partnerships and nominees that withhold under § 1.1446-4 and brokers that withhold under § 1.1446(f)-4 on transfers of publicly traded partnership interests. See § 1.1461-3 for penalties that apply for failure to withhold under section 1446(a) on effectively connected taxable income allocable to foreign partners or under section 1446(f) on transfers of partnership interests by foreign partners. The references in the previous two sentences to § 1.1446(f)-4 and section 1446(f) shall apply to transfers of partnership interests that occur on or after 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(1) * * *</P>
                        <P>(i) * * *</P>
                        <P>
                            (A) 
                            <E T="03">In general.</E>
                             * * * Notwithstanding the preceding sentence, any person that withholds or is required to withhold an amount under sections 1441, 1442, 1443, § 1.1446-4(a) (applicable to publicly traded partnerships required to pay tax under section 1446(a) on distributions), or § 1.1446(f)-4(a) (applicable to brokers required to withhold on transfers of publicly traded partnership interests) must file a Form 1042-S for the payment withheld upon whether or not that person is engaged in the conduct of a trade or business and whether or not the payment is an amount subject to reporting. The reference in the previous sentence to § 1.1446(f)-4(a) shall apply with respect to returns for transfers that occur on or after 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            . * * *
                        </P>
                        <STARS/>
                        <P>(ii) * * *</P>
                        <P>(A) * * *</P>
                        <P>
                            (
                            <E T="03">8</E>
                            ) A partner (including a foreign partnership) receiving a distribution from a publicly traded partnership subject to withholding under section 1446(a) and § 1.1446-4 on distributions of effectively connected income, and a partner (including a foreign partnership) receiving an amount realized from a transfer of a publicly traded partnership interest subject to withholding under section 1446(f)(1) and § 1.1446(f)-4. The references in this paragraph (c)(1)(ii)(A)(
                            <E T="03">8</E>
                            ) to section 1446(f)(1) and § 1.1446(f)-4 shall apply with respect to returns for transfers that occur on or after 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                        <STARS/>
                        <P>(B) * * *</P>
                        <P>
                            (
                            <E T="03">5</E>
                            ) A foreign broker withheld upon under § 1.1446(f)-4(a)(2)(i) by another broker paying an amount realized from the transfer of a PTP interest.
                        </P>
                        <STARS/>
                        <P>(2) * * *</P>
                        <P>
                            (i) 
                            <E T="03">In general.</E>
                             Subject to the exceptions described in paragraph (c)(2)(ii) of this section, amounts subject to reporting on Form 1042-S are amounts paid to a foreign payee or partner (including persons presumed to be foreign) that are amounts subject to withholding as defined in § 1.1441-2(a), § 1.1446-4(a) (addressing publicly traded partnerships required to pay withholding tax under section 1446(a) on distributions of effectively connected income), or § 1.1446(f)-4(a) (addressing brokers required to withhold and pay tax on the amount realized on the transfer of an interest in a publicly traded partnership). The reference in the previous sentence to withholding under § 1.1446-4(f) shall apply with respect to returns for transfers that occur on or after 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            . * * *
                        </P>
                        <STARS/>
                        <P>(P) The amount of any distribution made by a publicly traded partnership that is an amount subject to withholding under § 1.1446-4, or that is paid to a qualified intermediary that assumes primary withholding responsibility for the payment or a U.S. branch of a foreign person that agrees to be treated as a U.S. person described in § 1.1446-4(b)(2); and</P>
                        <P>(Q) An amount realized on the transfer of a publicly traded partnership interest subject to § 1.1446(f)-4 (unless an exception to withholding applies under § 1.1446(f)-4(b)(2) through (5)).</P>
                        <STARS/>
                        <P>(4) * * *</P>
                        <P>(ii) * * *</P>
                        <P>
                            (A) 
                            <E T="03">Amounts paid to a nonqualified intermediary, a flow-through entity, and certain U.S. branches.</E>
                             * * * For a payment to a foreign partnership on the transfer of a publicly traded partnership interest subject to § 1.1446(f)-4(a), see paragraph (c)(1)(ii)(A)(
                            <E T="03">8</E>
                            ) of this section (treating the foreign partnership as a recipient).
                        </P>
                        <STARS/>
                        <P>
                            (i) 
                            <E T="03">Applicability date</E>
                            —(1) 
                            <E T="03">In general.</E>
                             Except as provided in paragraph (i)(2) of this section, this section applies to returns required for payments made on or after January 6, 2017. For payments made after June 30, 2014, and before January 6, 2017, see this section as in effect and contained in 26 CFR part 1, as revised April 1, 2016. For payments made after December 31, 2000, and before July 1, 2014, see this section as in effect and contained in 26 CFR part 1, as revised April 1, 2013.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Exceptions.</E>
                             Paragraphs (a)(1), (c)(1)(i)(A), (c)(1)(ii)(A)(
                            <E T="03">8</E>
                            ), (c)(2)(i), and (c)(2)(iii) of this section apply as provided in those paragraphs. Paragraphs (c)(1)(ii)(A)(
                            <E T="03">11</E>
                            ), (c)(1)(ii)(B)(
                            <E T="03">5</E>
                            ), (c)(2)(i)(P) and (Q), and (c)(4)(ii)(A) apply with respect to returns for transfers that occur on or after 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 11.</E>
                         Section 1.1461-2 is amended:
                    </AMDPAR>
                    <AMDPAR>1. By revising paragraph (a)(1).</AMDPAR>
                    <AMDPAR>2. As proposed to be amended April 13, 2016, at 81 FR 21795, by revising the first and last sentences of paragraph (b).</AMDPAR>
                    <P>The revisions and addition read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1.1461-2 </SECTNO>
                        <SUBJECT>Adjustments for overwithholding or underwithholding of tax.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>
                            (1) 
                            <E T="03">In general.</E>
                             Except as otherwise provided in this paragraph (a)(1), a withholding agent that has overwithheld under chapter 3 of the Internal Revenue Code, and made a deposit of the tax as provided in § 1.6302-2(a), may adjust the overwithheld amount either pursuant to the reimbursement procedure described in paragraph (a)(2) of this section or pursuant to the set-off procedure 
                            <PRTPAGE P="21225"/>
                            described in paragraph (a)(3) of this section. These rules do not apply to partnerships or nominees required to withhold under section 1446(a), other than on a distribution by a publicly traded partnership subject to withholding under § 1.1446-4(a) and a payment of an amount realized on the transfer of an interest in a publicly traded partnership subject to § 1.1446(f)-4. The reference in the previous sentence to withholding under § 1.1446-4(f) shall apply with respect to returns for transfers that occur on or after 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                        <STARS/>
                        <P>
                            (b) * * * A withholding agent may withhold from future payments (including distributions of effectively connected income subject to withholding under § 1.1446-4 and the amount realized from the transfer of a partnership interest subject to § 1.1446(f)-4) made to a beneficial owner the tax that should have been withheld from previous payments to that beneficial owner under chapter 3 of the Code. * * * The reference in this paragraph (b) to withholding under § 1.1446-4(f)-4 shall apply with respect to returns for transfers that occur on or after 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 12.</E>
                         Section 1.1461-3 is amended by revising the first sentence and last sentences to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.1461-3</SECTNO>
                        <SUBJECT> Withholding under section 1446.</SUBJECT>
                        <P>
                            For rules relating to the withholding tax liability of a partnership, nominee, or transferee under section 1446, see §§ 1.1446-1 through 1.1446-7 and 1.1446(f)-1 through 1.1446(f)-5. * * * The references in this section to §§ 1.1446-1 through 1.1446-7 apply to partnership taxable years beginning after May 18, 2005, or such earlier time as the regulations under §§ 1.1446-1 through 1.1446-5 apply by reason of an election under § 1.1446-7, and the references in this section to § 1.1446(f)-1 through 1.1446(f)-5 shall apply with respect to returns for transfers that occur on or after 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 13.</E>
                         Section 1.1463-1 is amended by revising the fourth and fifth sentences of paragraph (a) to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.1463-1 </SECTNO>
                        <SUBJECT>Tax paid by recipient of income.</SUBJECT>
                        <P>
                            (a) * * * See §§ 1.1446-3(e), 1.1446-3(f) and 1.1446(f)-5(a) for application of the rule of this paragraph (a), and for additional rules, in which the withholding tax was required to be paid under section 1446. The references in the previous sentence to § 1.1446-3(e) and 1.1446-3(f) apply to partnership taxable years beginning after May 18, 2005, or such earlier time as the regulations under §§ 1.1446-1 through 1.1446-5 apply by reason of an election under § 1.1446-7, and the reference in the previous sentence to § 1.1446(f)-5(a) shall apply to the tax required to be withheld under section 1446(f) for transfers that occur on or after 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 14.</E>
                         Section 1.1464-1 is amended by revising the last sentence of paragraph (a) and by revising paragraph (c) to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.1464-1</SECTNO>
                        <SUBJECT> Refunds or credits.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">In general.</E>
                             * * * With respect to section 1446 (other than section 1446(f)), this section applies only to a publicly traded partnership described in § 1.1446-4.
                        </P>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Applicability date.</E>
                             The last sentence of paragraph (a) applies to publicly traded partnerships described in § 1.1446-4 for partnership taxable years beginning after April 29, 2008, and to brokers required to withhold under § 1.1446(f)-4 on transfers that occur on or after the date that is 60 days after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 15.</E>
                         Section 1.6050K-1 is amended by:
                    </AMDPAR>
                    <AMDPAR>1. Redesignating the introductory text of paragraph (c) and paragraphs (c)(1) through (3) as the introductory text of paragraph (c)(1) and paragraphs (c)(1)(i) through (iii), respectively.</AMDPAR>
                    <AMDPAR>2. Adding a subject heading to newly-redesignated paragraph (c)(1).</AMDPAR>
                    <AMDPAR>3. Adding paragraphs (c)(2) and (3), (d)(3), and (h).</AMDPAR>
                    <P>The revision and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1.6050K-1 </SECTNO>
                        <SUBJECT>Returns relating to sales or exchanges of certain partnership interests.</SUBJECT>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Statements to be furnished to transferor and transferee</E>
                            —(1) 
                            <E T="03">In general.</E>
                             * * *
                        </P>
                        <P>
                            (2) 
                            <E T="03">Information to be provided to transferors.</E>
                             The statement a partnership must provide to a transferor partner pursuant to paragraph (c)(1) of this section must also include the information necessary for the transferor to make the transferor's required statement under § 1.751-1(a)(3).
                        </P>
                        <P>
                            (3) 
                            <E T="03">Transfers of partnership interests by foreign persons.</E>
                             For additional information required to be provided by the partnership if section 864(c)(8) applies to the transfer of a partnership interest by a foreign person, see § 1.864(c)(8)-2(b).
                        </P>
                        <P>(d) * * *</P>
                        <P>
                            (3) 
                            <E T="03">Transfers of partnership interests by foreign persons.</E>
                             For notifications required by foreign transferors of partnership interests, see § 1.864(c)(8)-2(a).
                        </P>
                        <STARS/>
                        <P>
                            (h) 
                            <E T="03">Applicability date.</E>
                             Paragraphs (c)(2) and (3) of this section apply to returns filed on or after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            . Paragraph (d)(3) of this section applies to transfers that occur on or after the date that these regulations are published as final regulations in the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                    </SECTION>
                    <SIG>
                        <NAME>Kirsten Wielobob,</NAME>
                        <TITLE>Deputy Commissioner for Services and Enforcement.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2019-09515 Filed 5-7-19; 4:15 pm]</FRDOC>
                <BILCOD> BILLING CODE 4830-01-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>84</VOL>
    <NO>92</NO>
    <DATE>Monday, May 13, 2019</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="21227"/>
            <PARTNO>Part VI</PARTNO>
            <PRES>The President</PRES>
            <PROC>Proclamation 9880—Addressing Mass Migration Through the Southern Border of the United States</PROC>
        </PTITLE>
        <PRESDOCS>
            <PRESDOCU>
                <PROCLA>
                    <TITLE3>Title 3—</TITLE3>
                    <PRES>
                        The President
                        <PRTPAGE P="21229"/>
                    </PRES>
                    <PROC>Proclamation 9880 of May 8, 2019</PROC>
                    <HD SOURCE="HED">Addressing Mass Migration Through the Southern Border of the United States</HD>
                    <PRES>By the President of the United States of America</PRES>
                    <PROC>A Proclamation</PROC>
                    <FP>In Proclamation 9822 of November 9, 2018 (Addressing Mass Migration Through the Southern Border of the United States), I found that our immigration and asylum system is in crisis as a consequence of the mass migration of aliens across the border between the United States and Mexico (southern border). Accordingly, pursuant to sections 212(f) and 215(a) of the Immigration and Nationality Act (INA) (8 U.S.C. 1182(f) and 1185(a), respectively), I found that the unlawful entry of aliens through that border is detrimental to the interests of the United States and suspended and limited entry of such aliens. I exempted from the scope of Proclamation 9822 any alien who entered the United States at a port of entry and properly presented for inspection, as well as any lawful permanent resident of the United States. In Proclamation 9842 of February 7, 2019 (Addressing Mass Migration Through the Southern Border of the United States), I extended Proclamation 9822 for 90 days because I found that “the problem of large numbers of aliens traveling through Mexico to enter our country unlawfully or without proper documentation has not materially improved, and indeed in several respects has worsened, since November 9, 2018.”</FP>
                    <FP>Section 2(d) of Proclamation 9842 directed the Secretary of State, the Attorney General, and the Secretary of Homeland Security jointly to submit to me a recommendation on whether a further extension or renewal of the suspension or limitation on entry in Proclamation 9822 is in the interests of the United States. Those officials have jointly recommended extending the suspension and limitation for an additional 90 days beyond the date when the United States obtains relief from the preliminary injunction of the interim final rule titled “Aliens Subject to a Bar on Entry Under Certain Presidential Proclamations; Procedures for Protection Claims” that was promulgated by the Departments of Justice and Homeland Security on November 9, 2018.</FP>
                    <FP>As that recommendation reflects, the situation along the southern border has continued to deteriorate. In November 2018, a daily average of approximately 2,000 inadmissible aliens attempted entry into the United States. Today that average has risen to approximately 3,900. United States Border Patrol (USBP) apprehensions, which occur between ports of entry, have more than doubled from January to April of this year. From January through April, USBP apprehensions at the southern border are projected to reach approximately 460,000, a 4-month total that exceeds the totals from 8 of the last 10 fiscal years. The high percentage of children and families among these apprehensions places additional strain on the resources devoted to defense of the southern border. Moreover, large, organized groups of aliens continue to travel through Mexico toward the United States with the reported intention to enter the United States unlawfully or without proper documentation.</FP>
                    <FP>
                        The ability of the United States to address these problems continues to be hampered by a nationwide injunction issued by a United States District Court judge in the Northern District of California. That injunction currently prevents the Attorney General and the Secretary of Homeland Security from 
                        <PRTPAGE P="21230"/>
                        implementing an interim final rule that would render any alien who enters the country in contravention of a proclamation limiting or suspending entry at the southern border, including Proclamation 9822, ineligible to be granted asylum. The United States is appealing that injunction. Should the injunction be lifted, aliens who enter the United States unlawfully through the southern border in contravention of this proclamation will be ineligible to be granted asylum under that interim final rule.
                    </FP>
                    <FP>As President, I must act to protect the national interest and to maintain an effectively functioning asylum system for legitimate asylum seekers who demonstrate that they have fled persecution and warrant the many special benefits associated with being granted asylum. In view of the foregoing circumstances, and the joint recommendation from the Secretary of State, the Attorney General, and the Secretary of Homeland Security, I have determined to extend the suspension and limitation, as set forth below, on entry into the United States through the southern border established by Proclamation 9822 and extended by Proclamation 9842.</FP>
                    <FP>NOW, THEREFORE, I, DONALD J. TRUMP, by the authority vested in me by the Constitution and the laws of the United States of America, including sections 212(f) and 215(a) of the INA, hereby find that, absent the measures set forth in this proclamation, the entry into the United States of persons described in section 1 of this proclamation would be detrimental to the interests of the United States, and that their entry should be subject to certain restrictions, limitations, and exceptions. I therefore hereby proclaim the following:</FP>
                    <FP>
                        <E T="04">Section 1</E>
                        . 
                        <E T="03">Suspension and Limitation on Entry.</E>
                         The entry of any alien into the United States across the international boundary between the United States and Mexico is hereby suspended and limited, subject to section 2 of this proclamation. That suspension and limitation shall expire 90 days after the date on which the United States obtains relief from all injunctions that prevent full implementation of the interim final rule promulgated by the Departments of Justice and Homeland Security on November 9, 2018, or the date on which an agreement permits the United States to remove aliens to Mexico in compliance with the terms of section 208(a)(2)(A) of the INA (8 U.S.C. 1158(a)(2)(A)), whichever is earlier.
                    </FP>
                    <FP>
                        <E T="04">Sec. 2</E>
                        . 
                        <E T="03">Scope and Implementation of Suspension and Limitation on Entry.</E>
                         (a) The suspension and limitation on entry pursuant to section 1 of this proclamation shall apply only to aliens who enter the United States after the date of this proclamation.
                    </FP>
                    <P>(b) The suspension and limitation on entry pursuant to section 1 of this proclamation shall not apply to any alien who enters the United States at a port of entry and properly presents for inspection, or to any lawful permanent resident of the United States.</P>
                    <P>(c) Nothing in this proclamation shall limit an alien entering the United States from being considered for withholding of removal under section 241(b)(3) of the INA (8 U.S.C. 1231(b)(3)) or protection pursuant to the regulations promulgated under the authority of the implementing legislation regarding the Convention Against Torture and Other Cruel, Inhuman or Degrading Treatment or Punishment, or limit the statutory processes afforded to unaccompanied alien children upon entering the United States under section 279 of title 6, United States Code, and section 1232 of title 8, United States Code.</P>
                    <P>
                        (d) No later than 75 days after the date when the United States obtains relief from all injunctions that prevent full implementation of the interim final rule promulgated by the Departments of Justice and Homeland Security on November 9, 2018, the Secretary of State, the Attorney General, and the Secretary of Homeland Security shall jointly submit to the President, through the Assistant to the President for National Security Affairs, a recommendation on whether the suspension or limitation on entry in section 1 of this proclamation continues to be in the interests of the United States. If, at the time that all injunctions are lifted, the Secretary of State, the 
                        <PRTPAGE P="21231"/>
                        Attorney General, and the Secretary of Homeland Security are of the view that circumstances no longer warrant the suspension or limitation on entry, they shall so advise me.
                    </P>
                    <FP>
                        <E T="04">Sec. 3</E>
                        . 
                        <E T="03">Interdiction.</E>
                         The Secretary of State and the Secretary of Homeland Security shall continue to consult with the Government of Mexico regarding appropriate steps—consistent with applicable law and the foreign policy, national security, and public-safety interests of the United States—to address the approach of large groups of aliens traveling through Mexico with the intent of entering the United States unlawfully, including efforts to deter, dissuade, and return such aliens before they physically enter United States territory through the southern border.
                    </FP>
                    <FP>
                        <E T="04">Sec. 4</E>
                        . 
                        <E T="03">Severability.</E>
                         It is the policy of the United States to enforce this proclamation to the maximum extent possible to advance the interests of the United States. Accordingly:
                    </FP>
                    <P>(a) if any provision of this proclamation, or the application of any provision to any person or circumstance, is held to be invalid, the remainder of this proclamation and the application of its other provisions to any other persons or circumstances shall not be affected thereby; and</P>
                    <P>(b) if any provision of this proclamation, or the application of any provision to any person or circumstance, is held to be invalid because of the failure to follow certain procedures, the relevant executive branch officials shall implement those procedural requirements to conform with existing law and with any applicable court orders.</P>
                    <FP>
                        <E T="04">Sec. 5</E>
                        . 
                        <E T="03">General Provisions.</E>
                         (a) Nothing in this proclamation shall be construed to impair or otherwise affect:
                    </FP>
                    <FP SOURCE="FP1">(i) the authority granted by law to an executive department or agency, or the head thereof; or</FP>
                    <FP SOURCE="FP1">(ii) the functions of the Director of the Office of Management and Budget relating to budgetary, administrative, or legislative proposals.</FP>
                    <P>(b) This proclamation shall be implemented consistent with applicable law and subject to the availability of appropriations.</P>
                    <P>(c) This proclamation is not intended to, and does not, create any right or benefit, substantive or procedural, enforceable at law or in equity by any party against the United States, its departments, agencies, or entities, its officers, employees, or agents, or any other person.</P>
                    <P>IN WITNESS WHEREOF, I have hereunto set my hand this eighth day of May, in the year of our Lord two thousand nineteen, and of the Independence of the United States of America the two hundred and forty-third.</P>
                    <GPH SPAN="1" DEEP="80" HTYPE="RIGHT">
                        <GID>Trump.EPS</GID>
                    </GPH>
                    <PSIG> </PSIG>
                    <FRDOC>[FR Doc. 2019-09992 </FRDOC>
                    <FILED>Filed 5-10-19; 11:15 am]</FILED>
                    <BILCOD>Billing code 3295-F9-P</BILCOD>
                </PROCLA>
            </PRESDOCU>
        </PRESDOCS>
    </NEWPART>
</FEDREG>
