<?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>65</VOL>
    <NO>102</NO>
    <DATE>Thursday, May 25, 2000</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>Agricultural</EAR>
            <PRTPAGE P="iii"/>
            <HD>Agricultural Marketing Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>National Organic Standards Board, </SJDOC>
                    <PGS>33802</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13289</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Agriculture</EAR>
            <HD>Agriculture Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Agricultural Marketing Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Animal and Plant Health Inspection Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Rural Utilities Service</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Animal</EAR>
            <HD>Animal and Plant Health Inspection Service</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Noxious weed lists:</SJ>
                <SJDENT>
                    <SJDOC>Update, </SJDOC>
                    <PGS>33741-33743</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="3">00-13158</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Arts</EAR>
            <HD>Arts and Humanities, National Foundation</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Foundation on the Arts and the Humanities</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Centers</EAR>
            <HD>Centers for Disease Control and Prevention</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Grants and cooperative agreements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Pediatric and pregnancy nutrition surveillance systems data items enhancement program, </SJDOC>
                    <PGS>33818-33820</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="3">00-13132</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Public Health Laboratory Sciences Training Program for Hispanic and Native American Students, </SJDOC>
                    <PGS>33820-33823</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="4">00-13131</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Coast Guard</EAR>
            <HD>Coast Guard</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Ports and waterways safety:</SJ>
                <SJDENT>
                    <SJDOC>OPSAIL 2000/International Naval Review 2000; Port of New York/New Jersey, </SJDOC>
                    <PGS>33760-33770</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="11">00-12641</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>OpSail Miami 2000, Port of Miami, FL, </SJDOC>
                    <PGS>33770-33772</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="3">00-13195</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Foreign-Trade Zones Board</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> International Trade Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Institute of Standards and Technology</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Oceanic and Atmospheric Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Defense</EAR>
            <HD>Defense Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Federal Acquisition Regulation (FAR):</SJ>
                <SUBSJ>Agency information collection activities—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Submission for OMB review; comment request, </SUBSJDOC>
                    <PGS>33810-33811</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13145</FRDOCBP>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13146</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Education</EAR>
            <HD>Education Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Reports and guidance documents; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Income Contingent Repayment (ICR) Plan formula 2000, </SJDOC>
                    <PGS>34005-34007</PGS>
                    <FRDOCBP T="25MYN4.sgm" D="3">00-13101</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Employment</EAR>
            <HD>Employment and Training Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Grants and cooperative agreements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>National Farmworker Jobs Program, </SJDOC>
                    <PGS>33828-33830</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="3">00-13154</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Work Incentive Grants, </SJDOC>
                    <PGS>33830-33841</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="12">00-13153</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Energy</EAR>
            <HD>Energy Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Energy Regulatory Commission</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>EPA</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Air pollutants, hazardous; national emission standards:</SJ>
                <SJDENT>
                    <SJDOC>Major sources; requirements for control technology determinations, </SJDOC>
                    <PGS>34009-34012</PGS>
                    <FRDOCBP T="25MYR2.sgm" D="4">00-13196</FRDOCBP>
                    <FRDOCBP T="25MYR2.sgm" D="2">00-13197</FRDOCBP>
                </SJDENT>
                <SJ>Air quality implementation plans; approval and promulgation; various States:</SJ>
                <SJDENT>
                    <SJDOC>Oregon, </SJDOC>
                    <PGS>33772-33774</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="3">00-13070</FRDOCBP>
                </SJDENT>
                <SJ>Hazardous waste program authorizations:</SJ>
                <SJDENT>
                    <SJDOC>Minnesota, </SJDOC>
                    <PGS>33774-33778</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="5">00-12953</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Hazardous waste program authorizations:</SJ>
                <SJDENT>
                    <SJDOC>Minnesota, </SJDOC>
                    <PGS>33797-33798</PGS>
                    <FRDOCBP T="25MYP1.sgm" D="2">00-12954</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Executive</EAR>
            <HD>Executive Office of the President</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Management and Budget Office</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Presidential Documents</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Trade Representative, Office of United States</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Farm</EAR>
            <HD>Farm Credit Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Farm credit system:</SJ>
                <SUBSJ>Loan policies and operations—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Paricipations in loans from non-System lenders, </SUBSJDOC>
                    <PGS>33743</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="1">00-13191</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>FAA</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Air carrier certification and operations:</SJ>
                <SJDENT>
                    <SJDOC>International aviation saftey assessment program, </SJDOC>
                    <PGS>33751-33753</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="3">00-13179</FRDOCBP>
                </SJDENT>
                <SJ>Air traffic operating and flight rules, etc.:</SJ>
                <SUBSJ>Grand Canyon National Park, AZ; special flight rules in vicinity—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Special flight rules area and flight free zones; modification of dimensions; correction, </SUBSJDOC>
                    <PGS>33751</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="1">00-12819</FRDOCBP>
                </SSJDENT>
                <SJ>Airworthiness directives:</SJ>
                <SJDENT>
                    <SJDOC>Eurocopter France, </SJDOC>
                    <PGS>33743-33745</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="3">00-12351</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>New Piper Aircraft, Inc., </SJDOC>
                    <PGS>33745-33748</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="4">00-13083</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Class D airspace, </DOC>
                    <PGS>33749-33750</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="2">00-13173</FRDOCBP>
                    <FRDOCBP T="25MYR1.sgm" D="1">00-13176</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Class E airspace, </DOC>
                    <PGS>33750-33751</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="2">00-13174</FRDOCBP>
                    <FRDOCBP T="25MYR1.sgm" D="1">00-13177</FRDOCBP>
                    <FRDOCBP T="25MYR1.sgm" D="1">00-13178</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Class E airspace, </DOC>
                    <PGS>33796-33797</PGS>
                    <FRDOCBP T="25MYP1.sgm" D="2">00-13175</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>RTCA, Inc., </SJDOC>
                    <PGS>33868</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13182</FRDOCBP>
                </SJDENT>
                <SJ>Passenger facility charges; applications, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Austin-Bergstrom International Airport, TX, </SJDOC>
                    <PGS>33868-33869</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13181</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Fayetteville Regional Airport, NC, </SJDOC>
                    <PGS>33869-33870</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13180</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>FCC</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Radio stations; table of assignments:</SJ>
                <SJDENT>
                    <SJDOC>Arizona and Colorado, </SJDOC>
                    <PGS>33779</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="1">00-13135</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>New York, </SJDOC>
                    <PGS>33778-33779</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="2">00-13137</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Texas, </SJDOC>
                    <PGS>33778</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="1">00-13138</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Radio stations; table of assignments:</SJ>
                <SJDENT>
                    <SJDOC>California, </SJDOC>
                    <PGS>33799</PGS>
                    <FRDOCBP T="25MYP1.sgm" D="1">00-13139</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Colorado, </SJDOC>
                    <PGS>33798</PGS>
                    <FRDOCBP T="25MYP1.sgm" D="1">00-13141</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Hawaii, </SJDOC>
                    <PGS>33798</PGS>
                    <FRDOCBP T="25MYP1.sgm" D="1">00-13140</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Texas, </SJDOC>
                    <PGS>33799</PGS>
                    <FRDOCBP T="25MYP1.sgm" D="1">00-13136</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <PRTPAGE P="iv"/>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Reporting and recordkeeping requirements, </SJDOC>
                    <PGS>33817-33818</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13142</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Energy</EAR>
            <HD>Federal Energy Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Hydroelectric applications, </DOC>
                    <PGS>33814-33816</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13109</FRDOCBP>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13110</FRDOCBP>
                </DOCENT>
                <SJ>Oil pipelines:</SJ>
                <SJDENT>
                    <SJDOC>Producer price index for finished goods, minus one percent; annual change, </SJDOC>
                    <PGS>33816</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13115</FRDOCBP>
                </SJDENT>
                <SJ>Practice and procedure:</SJ>
                <SJDENT>
                    <SJDOC>Exempt and prohibited off-the-record communications; receipt, </SJDOC>
                    <PGS>33816-33817</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13104</FRDOCBP>
                </SJDENT>
                <SJ>
                    <E T="03">Applications, hearings, determinations, etc.:</E>
                </SJ>
                <SJDENT>
                    <SJDOC>California Independent System Operator Corp., </SJDOC>
                    <PGS>33811</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13114</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>East Tennessee Natural Gas Co., </SJDOC>
                    <PGS>33811-33812</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13105</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Indianapolis Power &amp; Light Co., </SJDOC>
                    <PGS>33812</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13107</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Koch Gateway Pipeline Co., </SJDOC>
                    <PGS>33812-33813</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13113</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Midwestern Gas Transmission Co., </SJDOC>
                    <PGS>33813</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13112</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Pacific Gas &amp; Electric Co., </SJDOC>
                    <PGS>33813</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13108</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>SkyGen Energy LLC et. al, </SJDOC>
                    <PGS>33813-33814</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13106</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Tennessee Gas Pipeling Co., </SJDOC>
                    <PGS>33814</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13111</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Highway</EAR>
            <HD>Federal Highway Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Intelligent transportation system architecture and standards, </DOC>
                    <PGS>33993-34000</PGS>
                    <FRDOCBP T="25MYP4.sgm" D="8">00-13023</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Statewide and metropolitan transportation planning, </DOC>
                    <PGS>33921-33958</PGS>
                    <FRDOCBP T="25MYP2.sgm" D="38">00-13021</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Transportation decisionmaking; National Environmental Protection Act procedures; public parks, wildlife and waterfowl refuges, and historic sites protection, </DOC>
                    <PGS>33959-33992</PGS>
                    <FRDOCBP T="25MYP3.sgm" D="34">00-13022</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Office</EAR>
            <HD>Federal Housing Enterprise Oversight Office</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Freedom of Information Act; implementation:</SJ>
                <SJDENT>
                    <SJDOC>Releasing information, </SJDOC>
                    <PGS>33790-33796</PGS>
                    <FRDOCBP T="25MYP1.sgm" D="7">00-13194</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>FMC</EAR>
            <HD>Federal Maritime Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agreements filed, etc., </DOC>
                    <PGS>33818</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13089</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Reserve</EAR>
            <HD>Federal Reserve System</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Banks and bank holding companies:</SJ>
                <SJDENT>
                    <SJDOC>Change in bank control, </SJDOC>
                    <PGS>33818</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13129</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Formations, acquisitions, and mergers, </SJDOC>
                    <PGS>33818</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13128</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Transit</EAR>
            <HD>Federal Transit Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Statewide and metropolitan transportation planning, </DOC>
                    <PGS>33921-33958</PGS>
                    <FRDOCBP T="25MYP2.sgm" D="38">00-13021</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Transportation decisionmaking; National Environmental Protection Act procedures; public parks, wildlife and waterfowl refuges, and historic sites protection, </DOC>
                    <PGS>33959-33992</PGS>
                    <FRDOCBP T="25MYP3.sgm" D="34">00-13022</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>National ITS Architecture Consistency Policy for project development; comment request, </DOC>
                    <PGS>34001-34004</PGS>
                    <FRDOCBP T="25MYN3.sgm" D="4">00-12913</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fish</EAR>
            <HD>Fish and Wildlife Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>National Wildlife Refuge System Improvement Act of 1997; implementation:</SJ>
                <SJDENT>
                    <SJDOC>Refuge planning policy; requirements and guidance, </SJDOC>
                    <PGS>33891-33919</PGS>
                    <FRDOCBP T="25MYN2.sgm" D="29">00-12931</FRDOCBP>
                </SJDENT>
                <SJ>Natural resource damage assessment plans; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Lower Fox River/Green Bay, WI, </SJDOC>
                    <PGS>33823</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13133</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Foreign</EAR>
            <HD>Foreign-Trade Zones Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>
                    <E T="03">Applications, hearings, determinations, etc.:</E>
                </SJ>
                <SUBSJ>Florida</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>RP Scherer Corp.; gelatin capsule manufacturing facilities, </SUBSJDOC>
                    <PGS>33802-33803</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13098</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>GAO</EAR>
            <HD>General Accounting Office</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Claims, waiver of claims and transportation issues; CFR parts removed, </DOC>
                    <PGS>33737-33738</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="2">00-13192</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>GSA</EAR>
            <HD>General Services Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Federal Management Regulation:</SJ>
                <SUBSJ>Excess personal property; disposition</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Correction, </SUBSJDOC>
                    <PGS>33889</PGS>
                    <FRDOCBP T="25MYCX.sgm" D="1">C0-11921</FRDOCBP>
                    <PGS>33778</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="1">00-13147</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Acquisition regulations:</SJ>
                <SJDENT>
                    <SJDOC>Tax adjustment, </SJDOC>
                    <PGS>33799-33801</PGS>
                    <FRDOCBP T="25MYP1.sgm" D="3">00-13157</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Federal Acquisition Regulation (FAR):</SJ>
                <SUBSJ>Agency information collection activities—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Submission for OMB review; comment request, </SUBSJDOC>
                    <PGS>33810-33811</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13145</FRDOCBP>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13146</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health</EAR>
            <HD>Health and Human Services Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Centers for Disease Control and Prevention</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Housing</EAR>
            <HD>Housing and Urban Development Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Housing Enterprise Oversight Office</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Interior</EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Fish and Wildlife Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Land Management Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Minerals Management Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Park Service</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>IRS</EAR>
            <HD>Internal Revenue Service</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Income taxes:</SJ>
                <SJDENT>
                    <SJDOC>Consolidated return regulations; limitations on use of certain credits, </SJDOC>
                    <PGS>33753-33760</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="8">00-11901</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International</EAR>
            <HD>International Trade Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Antidumping:</SJ>
                <SUBSJ>Bulk aspirin from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>China, </SUBSJDOC>
                    <PGS>33805-33807</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="3">00-13095</FRDOCBP>
                </SSJDENT>
                <SUBSJ>Polyester staple fiber from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Korea and Taiwan, </SUBSJDOC>
                    <PGS>33807-33808</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13096</FRDOCBP>
                </SSJDENT>
                <SJ>Antidumping and countervailing duties:</SJ>
                <SUBSJ>Small diameter carbon and alloy seamless standard, line, and pressure pipe from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Czech Republic, </SUBSJDOC>
                    <PGS>33803-33805</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="3">00-13097</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International</EAR>
            <PRTPAGE P="v"/>
            <HD>International Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Import investigations:</SJ>
                <SJ>
                    Sub-Saharan Africa; U.S. trade and investment [
                    <E T="04">Editorial Note:</E>
                     This document, which printed in the May 24, 2000, 
                    <E T="04">Federal Register</E>
                     on pages 33577-33578, was inadvertently missing from the Table of Contents.]
                </SJ>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Labor</EAR>
            <HD>Labor Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Employment and Training Administration</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Submission for OMB review; comment request, </SJDOC>
                    <PGS>33827-33828</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13155</FRDOCBP>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13156</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Land</EAR>
            <HD>Land Management Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SUBSJ>Resource Advisory Councils—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Dakotas, </SUBSJDOC>
                    <PGS>33823-33824</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13122</FRDOCBP>
                </SSJDENT>
                <SSJDENT>
                    <SUBSJDOC>Sierra Front/Northwestern Great Basin, </SUBSJDOC>
                    <PGS>33824</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13165</FRDOCBP>
                </SSJDENT>
                <SJ>Public land orders:</SJ>
                <SJDENT>
                    <SJDOC>Idaho, </SJDOC>
                    <PGS>33823</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13163</FRDOCBP>
                </SJDENT>
                <SJ>Resource management plans, etc.:</SJ>
                <SJDENT>
                    <SJDOC>King Range National Conservation Area, CA, </SJDOC>
                    <PGS>33824-33825</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13134</FRDOCBP>
                </SJDENT>
                <SJ>Withdrawal and reservation of lands:</SJ>
                <SJDENT>
                    <SJDOC>Oregon, </SJDOC>
                    <PGS>33825</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13170</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Legal</EAR>
            <HD>Legal Services Corporation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Grants and cooperative agreements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Civil legal services to poor, </SJDOC>
                    <PGS>33842-33849</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="8">00-13189</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Management</EAR>
            <HD>Management and Budget Office</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Budget rescissions and deferrals</SJ>
                <SJDENT>
                    <SJDOC>Cumulative reports, </SJDOC>
                    <PGS>33851-33854</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="4">00-13123</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Minerals</EAR>
            <HD>Minerals Management Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Proposed collection; comment request, </SJDOC>
                    <PGS>33826-33827</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13166</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>NASA</EAR>
            <HD>National Aeronautics and Space Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Federal Acquisition Regulation (FAR):</SJ>
                <SUBSJ>Agency information collection activities—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Submission for OMB review; comment request, </SUBSJDOC>
                    <PGS>33810-33811</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13145</FRDOCBP>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13146</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Foundation</EAR>
            <HD>National Foundation on the Arts and the Humanities</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Humanities Panel, </SJDOC>
                    <PGS>33849</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13102</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Highway</EAR>
            <HD>National Highway Traffic Safety Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Grants and cooperative agreements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Crash outcome data evaluation systems development, </SJDOC>
                    <PGS>33870-33875</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="6">00-13100</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Innovative projests designed to increase sealt belt use rates, </SJDOC>
                    <PGS>33875-33882</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="8">00-13099</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Institute</EAR>
            <HD>National Institute of Standards and Technology</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Computer System Security and Privacy Advisory Board, </SJDOC>
                    <PGS>33808-33809</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13144</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>NOAA</EAR>
            <HD>National Oceanic and Atmospheric Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Endangered and threatened species:</SJ>
                <SUBSJ>Sea turtle conservation; shrimp trawling requirements—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Leatherback Conservation Zone; turtle excluder devices, </SUBSJDOC>
                    <PGS>33779-33780</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="2">00-13092</FRDOCBP>
                </SSJDENT>
                <SJ>Fishery conservation and management:</SJ>
                <SUBSJ>Alaska; fisheries of Exclusive Econonmic Zone—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>At-sea scales; Community Development Quota (CDQ), </SUBSJDOC>
                    <PGS>33780-33784</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="5">00-13185</FRDOCBP>
                </SSJDENT>
                <SJ>Marine mammals:</SJ>
                <SUBSJ>Incidental taking—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Beaufort Sea, AK; construction and operation of offshore oil and gas facilities, </SUBSJDOC>
                    <PGS>34013-34032</PGS>
                    <FRDOCBP T="25MYR3.sgm" D="20">00-13184</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Gulf of Mexico Fishery Management Council, </SJDOC>
                    <PGS>33801</PGS>
                    <FRDOCBP T="25MYP1.sgm" D="1">00-13187</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>New England Fishery Management Council, </SJDOC>
                    <PGS>33809-33810</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13186</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Park</EAR>
            <HD>National Park Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Reports and guidance documents; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Structural Fire Management Program; Director's Order, </SJDOC>
                    <PGS>33827</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13143</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Science</EAR>
            <HD>National Science Foundation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>U.S. National Assessment Synthesis Team, </SJDOC>
                    <PGS>33849-33850</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13160</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Nuclear</EAR>
            <HD>Nuclear Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>
                    <E T="03">Applications, hearings, determinations, etc.:</E>
                </SJ>
                <SJDENT>
                    <SJDOC>Plateau Resources Limited, </SJDOC>
                    <PGS>33850-33851</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13159</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Office</EAR>
            <HD>Office of Federal Housing Enterprise Oversight</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Housing Enterprise Oversight Office</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Office</EAR>
            <HD>Office of Management and Budget</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Management and Budget Office</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Office of U.S. Trade</EAR>
            <HD>Office of United States Trade Representative</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Trade Representative, Office of United States</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Personnel</EAR>
            <HD>Personnel Management Office</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Excepted service, career conditional employment system, and promotion and internal placement:</SJ>
                <SJDENT>
                    <SJDOC>Senior Executive Service; career and limited appointments, </SJDOC>
                    <PGS>33738-33741</PGS>
                    <FRDOCBP T="25MYR1.sgm" D="4">00-13053</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Pay administration:</SJ>
                <SJDENT>
                    <SJDOC>Grade and pay retention; discretionary authority by agencies, </SJDOC>
                    <PGS>33785-33787</PGS>
                    <FRDOCBP T="25MYP1.sgm" D="3">00-13052</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Postal</EAR>
            <HD>Postal Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>33851</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13308</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Presidential</EAR>
            <HD>Presidential Documents</HD>
            <CAT>
                <HD>EXECUTIVE ORDERS</HD>
                <SJ>Government agencies, and employees:</SJ>
                <SJDENT>
                    <SJDOC>Women-owned businesses, increasing opportunities (EO 13157), </SJDOC>
                    <PGS>34035-34037</PGS>
                    <FRDOCBP T="25MYE0.sgm" D="3">00-13367</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Public</EAR>
            <HD>Public Health Service</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Centers for Disease Control and Prevention</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Research</EAR>
            <PRTPAGE P="vi"/>
            <HD>Research and Special Programs Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>International standards on the transport of dangerous goods, </SJDOC>
                    <PGS>33882</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13183</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>RUS</EAR>
            <HD>Rural Utilities Service</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Telecommunications loans:</SJ>
                <SJDENT>
                    <SJDOC>General policies, types of loans, and loan requirements, </SJDOC>
                    <PGS>33787-33790</PGS>
                    <FRDOCBP T="25MYP1.sgm" D="4">00-12657</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>SEC</EAR>
            <HD>Securities and Exchange Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Self-regulatory organizations; proposed rule changes:</SJ>
                <SJDENT>
                    <SJDOC>National Association of Securities Dealers, Inc., </SJDOC>
                    <PGS>33854-33855</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13148</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>SBA</EAR>
            <HD>Small Business Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>National Small Business Development Center Advisory Board, </SJDOC>
                    <PGS>33855</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13094</FRDOCBP>
                </SJDENT>
                <SJ>Meetings; district and regional advisory councils:</SJ>
                <SJDENT>
                    <SJDOC>Florida, </SJDOC>
                    <PGS>33855</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13093</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>State</EAR>
            <HD>State Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Grants and cooperative agreements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Romania; Civic Education Curriculum Development and Teacher Training Program, </SJDOC>
                    <PGS>33855-33858</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="4">00-12939</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Shipping Coordinating Committee, </SJDOC>
                    <PGS>33858</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13193</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Surface</EAR>
            <HD>Surface Transportation Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Railroad operation, acquisition, construction, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Georgia, </SJDOC>
                    <PGS>33882-33883</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13171</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Trade</EAR>
            <HD>Trade Representative, Office of United States</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Generalized System of Preferences:</SJ>
                <SUBSJ>African Growth and Opportunity Act—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Product designation for beneficiaries; timetable review and public hearing, </SUBSJDOC>
                    <PGS>33858-33867</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="10">00-13169</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Transportation</EAR>
            <HD>Transportation Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Coast Guard</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Aviation Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Highway Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Transit Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Highway Traffic Safety Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Research and Special Programs Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Surface Transportation Board</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Internal Revenue Service</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Submission for OMB review; comment request, </SJDOC>
                    <PGS>33883-33887</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13116</FRDOCBP>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13117</FRDOCBP>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13118</FRDOCBP>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13119</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Veterans</EAR>
            <HD>Veterans Affairs Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Minority Veterans Advisory Committee, </SJDOC>
                    <PGS>33887-33888</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="2">00-13167</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Readjustment of Veterans Advisory Committee, </SJDOC>
                    <PGS>33888</PGS>
                    <FRDOCBP T="25MYN1.sgm" D="1">00-13168</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Department of Interior, Fish and Wildlife Service, </DOC>
                <PGS>33891-33919</PGS>
                <FRDOCBP T="25MYN2.sgm" D="29">00-12931</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Department of Transportation, Federal Highway Administration, FederalTransit Administration, </DOC>
                <PGS>33921-33958</PGS>
                <FRDOCBP T="25MYP2.sgm" D="38">00-13021</FRDOCBP>
            </DOCENT>
            <HD>Part IV</HD>
            <DOCENT>
                <DOC>Department of Transportation, Federal Highway Administration, Federal Transit Administration, </DOC>
                <PGS>33959-33992</PGS>
                <FRDOCBP T="25MYP3.sgm" D="34">00-13022</FRDOCBP>
            </DOCENT>
            <HD>Part V</HD>
            <DOCENT>
                <DOC>Department of Transportation, Federal Highway Administration, </DOC>
                <PGS>33993-34000</PGS>
                <FRDOCBP T="25MYP4.sgm" D="8">00-13023</FRDOCBP>
            </DOCENT>
            <HD>Part VI</HD>
            <DOCENT>
                <DOC>Department of Transportation, Federal Transit Administration, </DOC>
                <PGS>34001-34004</PGS>
                <FRDOCBP T="25MYN3.sgm" D="4">00-12913</FRDOCBP>
            </DOCENT>
            <HD>Part VII</HD>
            <DOCENT>
                <DOC>Department of Education, </DOC>
                <PGS>34005-34007</PGS>
                <FRDOCBP T="25MYN4.sgm" D="3">00-13101</FRDOCBP>
            </DOCENT>
            <HD>Part VIII</HD>
            <DOCENT>
                <DOC>Environmental Protection Agency, </DOC>
                <PGS>34009-34012</PGS>
                <FRDOCBP T="25MYR2.sgm" D="4">00-13196</FRDOCBP>
                <FRDOCBP T="25MYR2.sgm" D="2">00-13197</FRDOCBP>
            </DOCENT>
            <HD>Part IX</HD>
            <DOCENT>
                <DOC>Department of Commerce, National Oceanic and Atmospheric Administration, </DOC>
                <PGS>34013-34032</PGS>
                <FRDOCBP T="25MYR3.sgm" D="20">00-13184</FRDOCBP>
            </DOCENT>
            <HD>Part X</HD>
            <DOCENT>
                <DOC>The President, </DOC>
                <PGS>34033-34037</PGS>
                <FRDOCBP T="25MYE0.sgm" D="3">00-13367</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, reminders, and notice of recently enacted public laws.</P>
        </AIDS>
    </CNTNTS>
    <VOL>65</VOL>
    <NO>102</NO>
    <DATE>Thursday, May 25, 2000 </DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="33737"/>
                <AGENCY TYPE="F">GENERAL ACCOUNTING OFFICE </AGENCY>
                <CFR>4 CFR Chapter I </CFR>
                <SUBJECT>Claims, Waiver of Claims and Transportation Issues </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>General Accounting Office. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The General Accounting Office (GAO) is removing regulations which relate to the settlement of claims, settlement of accounts of deceased and incompetent individuals, transportation transactions, and waiver of claims for erroneous payments. The Legislative Branch Appropriations Act of 1996 transferred these functions to the executive branch, but these regulations were kept for a transition period. This final rule eliminates these regulations as unnecessary because the functions are no longer carried out by GAO but have been transferred to other federal agencies. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective May 25, 2000. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Barry L. Shillito, 202-512-4663; shillitob.ogc@gao.gov. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Claims Settlements Authority </HD>
                <P>In Subchapter C (Claims; General), Parts 30-36 set out the Comptroller General's regulations for the settlement of (1) claims and (2) accounts of certain deceased and incompetent individuals. The Legislative Branch Appropriations Act of 1996, Public Law 104-53, sec. 211(a), 109 Stat. 514, 535 (1996), transferred certain of the Comptroller General's authority to settle claims and accounts to the Director of the Office of Management and Budget (OMB), and provided for the Director of OMB to delegate this authority to other appropriate agencies. The Director of OMB delegated his authority to several executive branch agencies. Subsequently, the General Accounting Office Act of 1996, Public Law 104-316, 110 Stat. 3826 (1996), set out in detail, among other things, the authority given to the Director of OMB and other heads of agencies to settle the claims and accounts formerly subject to settlement by the Comptroller General. Section 202(n) of the GAO Act of 1996 made a conforming amendment to 31 U.S.C. 732 to set out the executive branch agencies to whom the Director of OMB delegated the authority to settle claims formerly within the authority of the Comptroller General. Additionally, section 103(c) of the GAO Act of 1996 transferred the Comptroller General's authority to promulgate regulations with respect to the designation of beneficiaries for certain deceased and incompetent persons to various specified officials in the three branches of government. </P>
                <P>The Director of OMB delegated to the Director of the Office of Personnel Management (OPM) the authority to settle claims against the United States involving Federal employee compensation and leave, deceased employees' compensation, and proceeds of canceled checks payable to deceased beneficiaries. Individuals with these types of claims should no longer contact GAO but should contact OPM. </P>
                <P>The Director of OMB delegated to the Administrator of General Services the authority to settle claims involving expenses incurred by Federal civilian employees for official travel and transportation and for relocation expenses incident to transfers of official duty station. Individuals with these type of claims should no longer contact GAO but should contact the General Services Administration. </P>
                <P>OMB delegated to the Secretary of Defense the authority to settle claims for military pay, allowances, travel, transportation, retired pay, and survivor benefits as well as claims by transportation carriers involving amounts collected from them for loss or damage incurred to property incident to shipment at Government expense. Individuals with these types of claims should no longer contact GAO but should contact the Department of Defense. </P>
                <P>Accordingly, the Comptroller General no longer has the authority to prescribe the regulations in 4 CFR parts 30-32, regarding claims settlement, and parts 33-36, regarding settlement of accounts for certain deceased and incompetent persons. </P>
                <HD SOURCE="HD1">Transportation </HD>
                <P>Sections 125 and 127(d) of the GAO Act of 1996, transferred the Comptroller General's authority to promulgate regulations for transportation transactions for use of U.S. flag carriers pursuant to the Merchant Marine Act of 1936, 46 U.S.C. 1241a, and the Fly America Act, 49 U.S.C. 40118(c), to the Administrator of General Services. Accordingly, the Comptroller General no longer has authority to prescribe the regulations found at 4 CFR part 52. With the removal of part 52, there is no further need for 4 CFR part 51. </P>
                <P>Section 202(o)(2) of the GAO Act of 1996 transferred the Comptroller General's authority to promulgate regulations governing the review of GSA transportation settlement actions pursuant to 31 U.S.C. 3726(g)(1) to the Administrator of General Services. Accordingly the Comptroller General no longer has authority to prescribe the regulations found at 4 CFR part 53. </P>
                <P>Section 202(o)(1) of the GAO Act of 1996, 110 Stat. 3826, 3844 (1996), removed the Comptroller General's authority to jointly prescribe standards, with the Secretary of Treasury, for advance payment of charges for transportation services pursuant to 31 U.S.C. 3726(f). Accordingly, the Comptroller General no longer has authority to prescribe the regulations found at 4 CFR part 56. </P>
                <P>Given the above discussion, there is no long current need for a subchapter devoted to transportation (Subchapter D). </P>
                <HD SOURCE="HD1">Waiver </HD>
                <P>
                    Sections 103 of the GAO Act of 1996 transferred the Comptroller General's authority to waive claims against civilian employees arising out of erroneous payments of pay and allowances, travel, transportation and relocation benefits to the head of an agency with respect to a legislative branch employee, or to the Director of OMB with respect to any other agency or employee. Further, the Comptroller General's authority over such claims against members of the military and the National Guard was transferred to the Director of OMB by sections 105(b) and 116 of the GAO Act of 1996. The Director of OMB has delegated his authority to the head of the agency that 
                    <PRTPAGE P="33738"/>
                    made the erroneous payment. Accordingly the Comptroller General no longer has authority to promulgate the regulations at 4 CFR parts 91 and 92 (Subchapter G—Standards for waiver of claims for erroneous payments of pay and allowances, and of travel, transportation, and relocation expenses and allowances). Individuals seeking a waiver should no longer contact GAO but should direct a request for waiver to their employing agency. 
                </P>
                <P>Accordingly, as set forth in the preamble and under the authority of Public Law 104-53, sec. 211(a), 109 Stat. 535, and secs. 103(c), 103(d), 105(b), 116, 125, and 127 of Public Law 104-316, 110 Stat. 3826, GAO amends 4 CFR Chapter I as follows: </P>
                <P>1. Subchapter C, consisting of parts 30 through 36, Subchapter D, consisting of parts 51 through 53 and part 56, and Subchapter G, consisting of parts 91 through 93, are removed and reserved. </P>
                <SIG>
                    <DATED>Dated: May 19, 2000. </DATED>
                    <NAME>Robert P. Murphy, </NAME>
                    <TITLE>General Counsel, General Accounting Office. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13192 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 1610-02-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">OFFICE OF PERSONNEL MANAGEMENT </AGENCY>
                <CFR>5 CFR Part 317 </CFR>
                <RIN>RIN 3206-A158</RIN>
                <SUBJECT>Employment in the Senior Executive Service </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Personnel Management. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Office of Personnel Management (OPM) is amending its regulations governing career and limited appointments to the Senior Executive Services (SES). The amended regulations emphasize the importance of executive leadership qualifications in agency SES selection criteria, strengthen merit principles, and increase SES staffing flexibilities to help agencies recruit the brightest and most diverse executive cadre possible. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>June 26, 2000. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Daliza Salas (202-606-1274, email desalas@opm.gov) or Marcia Staten (202-606-1832, email mkstaten@opm.gov). </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> The success of the Senior Executive Service (SES) rests on the ability of agencies to employ highly competent, motivated, and diverse professionals dedicated to public service who have the requisite leadership expertise to meet the challenges facing the Government and the Nation now and into the future. </P>
                <P>The final regulations and accompanying guidance to agencies are an outcome of extensive discussions with stakeholders about improving the SES. These discussions challenged stakeholders to think about the future and whether the way we develop, select, and manage the SES cadre produces the kind of executives the Government needs to meet the leadership challenges of the 21st century. Although stakeholder views varied widely, there was consensus on many ideas, including increasing agency flexibilities for SES staffing. Specifically, there was general support for improving the SES selection process to ensure that leadership and executive qualifications are the major selection criteria, reducing the paperwork burden on applicants and agencies, considering options for delegating QRB administration, and increasing agency authority to make limited terms appointments. </P>
                <P>
                    On July 30, 1999, OPM published a proposed rule in the 
                    <E T="04">Federal Register</E>
                     (64 CFR 41334) to amend the regulations governing career and limited appointments to the Senior Executive Service (SES) and Qualifications Review Board (QRB) certification. We received 24 written comments during the comment period: 16 from departments and agencies, 4 from professional organizations, and 4 from individuals. There was broad support for the changes, although some respondents had serious reservations about the proposal to delegate QRB administration to individual agencies via delegation agreement. 
                </P>
                <P>In addition to these regulatory changes, we have modified internal procedures and other requirements to streamline the SES application process, reduce paperwork requirements, and improve the QRB certification process. These modifications provide alternative methods for documenting executive qualifications for presentation to QRBs and improved guidance and instructions to QRBs to ensure that members fully understand their role and responsibilities. We have also suggested ways for agencies to improve their recruitment and selection procedures. OPM's administrative modifications and the suggested changes at the agency level will help agencies and candidates focus on substance rather than process and format, and they reinforce the goal of achieving a highly-qualified, diverse SES corps. We have summarized these procedural modifications and flexibilities in supplemental guidance to agencies. </P>
                <HD SOURCE="HD1">Emphasis on Executive Leadership </HD>
                <P>The key characteristic of an SES position is executive leadership, and therefore selection criteria should focus primarily on leadership qualifications. Further, the law at 5 U.S.C. 3393 requires agency Executive Resources Boards to conduct the merit staffing process for career entry into the SES, including reviewing the executive qualifications of each career SES candidate. </P>
                <P>During discussions on improving the SES, stakeholders confirmed that, in many agencies, the selection criteria focuses mainly on candidates' professional or technical qualifications, and therefore consideration of executive qualifications is not getting the full attention intended by the SES legislation. To strengthen that focus and encourage agencies to fully integrate consideration of executive leadership qualifications into their selection processes, the proposed regulations amended the current provisions to incorporate the statutory requirements. </P>
                <P>Most commenters supported the proposal. One agency felt there was not pressing need to revise the current wording, as what constitutes SES qualifications changes over time with new studies and emerging approaches and theories. We do not agree, given that the statute requires selection based on executive qualifications and our findings that many agencies are not considering executive expertise in their SES selections. An August 1999 survey of SES members reinforces these findings. Only 56 percent of the senior executives responding to the survey said that their agencies strongly emphasize executive qualifications in evaluating applications and use them as key factor in determining who is selected for the SES. Further, our research tells us that the emphasis on executive skills and expertise is even more critical than in the past and will continue to be of primary importance in the future. The survey findings supported this as well. When asked to rank qualifications for SES positions now and in five years, respondents rated executive qualifications as more important than technical qualifications today and even more important in five years. </P>
                <P>
                    One agency, while not opposing the proposal, was concerned that it might lead to overly prescriptive procedural requirements. This is not our intent. Agencies will continue to have the latitude to design merit staffing processes to meet their unique mission requirements, within the framework of 
                    <PRTPAGE P="33739"/>
                    law and regulations, including determining how to ensure that SES selections are based on consideration of executive qualifications. 
                </P>
                <P>One agency objected to the requirement that the appointing authority certify the candidate's executive and technical qualifications. The certification requirement is not new—it is included in current regulations at § 317.502(b). The same agency recommended adding a statement that the appointing authority can approve the appointment of a candidate who does not meet the executive qualifications but has special or unique qualities that indicate a likelihood of executive success. Selection of a candidate on this basis is already provided in statute (5 U.S.C. 3393(c)(2)) and current regulations (§ 317.502(c)).</P>
                <P>Two professional organizations recommended that we require equal consideration of executive and technical qualifications to ensure that technical qualifications are not favored over executive qualifications. Since the statute does not make this specification, we have not adopted the recommendation. Further, “equal consideration” would indicate that technical qualifications should carry the same weight in SES selections, which is not the case. Executive qualifications should be the primary factor. The final regulations concerning executive qualifications are adopted as proposed in order to reinforce the primacy of executive expertise and encourage agencies to fully integrate consideration of executive leadership qualifications into their selection processes.</P>
                <P>Three professional organizations recommended additional language to emphasize that recruitment and selection for initial SES career appointments should be achieved from the brightest and most diverse executive cadre possible. We have added language to the final regulations that stresses the importance of reaching out to women, minorities, and people with disabilities in SES recruitment and selection. We have also addressed this in the supplemental guidance to agencies on the staffing flexibilities and procedural modifications.</P>
                <HD SOURCE="HD1">Delegating QRB Administration</HD>
                <P>During stakeholder discussions on improving the SES, several agencies recommended delegating QRB administration to agencies to give them more flexibility to manage their executive resources. Some were critical of the paperwork and procedures connected with QRB certification and felt that agencies could make process improvements if the authority were delegated. OPM agreed to consider the recommendation, incorporated it into the proposed regulations, and formally asked for stakeholder views. The proposed regulatory changes provided for delegation of QRB administration to agencies, on an agency-by-agency basis via individual delegation agreements, provided that the focus on leadership and executive expertise would be maintained and merit system principles would be preserved.</P>
                <P>Two-thirds of those commenting on the proposal either supported or voiced no objections to the proposal. However, very few indicated an interest in pursuing a delegation agreement. Supporters favored the increased flexibility to manage and be held accountable for the SES appointment process. Another commented that agencies have long records of merit-based selections of individuals with well-demonstrated SES qualifications.</P>
                <P>A few supporters had some reservations. One stated that delegation might create undue pressure on QRB members to certify candidates. Another commented that fairness might be jeopardized under delegation and politicization heightened. A third commenter said that more benefit could be obtained through streamlining paperwork requirements than through QRB delegation.</P>
                <P>One agency, three professional organizations, and four individuals strongly opposed the proposal. Key reasons given were serious concerns about the ability of agencies to guarantee an independent peer review, the potential for abuse of the merit staffing process and politicization of the career SES, and the possible adverse impact on efforts to increase the diversity of the SES cadre. In addition, one professional organization questioned OPM's authority to delegate QRB administration. Regarding this issue, we have determined that OPM's broad statutory authority at 5 U.S.C. 1104 for delegating personnel management functions permits the delegation of QRB administration.</P>
                <P>Although more respondents supported the proposal than opposed it, the arguments against delegation were substantive and persuasive. The concerns about preserving the independence of QRB certification and the perceived potential for politicization of the career appointment process expressed by those opposed to the proposal outweighed comments in favor of delegation. Since the supporters did not offer compelling reasons for proceeding with the proposal, the final regulations do not include the proposed amendment to § 317.502 regarding QRB delegation.</P>
                <P>We will strengthen efforts to encourage senior executives from diverse backgrounds to serve as QRB members to ensure that the boards are representative of the Nation's diversity. In addition, we have modified the procedures and streamlined paperwork associated with QRB administration to address concerns that the process focuses on paper over substance and to provide more specific and detailed feedback to agencies on QRB disapprovals.</P>
                <HD SOURCE="HD1">Noncareer Conversion Restriction</HD>
                <P>The current regulation at § 317.502(e) precludes QRB certification of a noncareer SES employee for career appointment in the employee's current position or a successor to that position, because there is no bona-fide vacancy for which to hold competition. This regulation was intended to preserve the merit principle of fair and open competition in merit selections. Since the regulation was promulgated, however, questions have arisen about the definition of “noncareer SES employee.” The proposed regulation strengthens and clarifies the intent of the current regulation by expanding coverage to noncareer-type employees, including noncareer SES appointees and Schedule C appointees, or the equivalent. This generally refers to individuals in or from positions of a confidential, policy-determining, or policy-advocating nature.</P>
                <P>Commenters concurred with the proposed revision. One agency recommended adding certain limited appointees to those considered to be noncareer-type employees. These would be limited appointees not appointed under an agency's delegated authority at § 317.601(c)(1), which restricts use of the authority to individuals with career or career-conditional appointments. Since limited appointees, regardless of the method of appointment, are not considered noncareer-type employees within the meaning intended by this provision, we are not adopting the recommendation.</P>
                <P>One agency recommended that we delete “or equivalent” and restrict coverage to noncareer SES and Schedule C appointees only. We believe the additional language is needed to cover other categories that might meet the intent of the provision, so we have not adopted this recommendation. The final regulations are adopted as proposed.</P>
                <HD SOURCE="HD1">SES Probationary Period</HD>
                <P>
                    The proposal made two changes to the regulations governing the SES 
                    <PRTPAGE P="33740"/>
                    probationary period. One would require agencies to assess the performance of new career appointees before the end of the probationary period and make an official determination that the appointee is performing at the level of excellence expected of a senior executive. The second change would require that, during the probationary period, agencies address the executive development activities outlined in development plans used to support QRB certification based on special and unique qualifications. Both requirements were an outcome of stakeholder discussions about making more effective use of the probationary period. Stakeholders had serious concerns about the lack of attention paid to performance during probation. They also felt that, when a QRB certifies candidates on the basis of special and unique qualifications, stronger oversight is needed to verify that the executive development activities promised by the agency are accomplished.
                </P>
                <P>There was overall support for the proposals. One agency, while supporting the concepts, opposed placing the provisions in regulation. The agency felt that agencies should be trusted to manage their own executive resources effectively under their own administrative authority. Another supported the concepts, but said that the means should be left to each agency. Another agency opposed the provision, stating that performance issues can be addressed through the performance management system. While these views have merit, most stakeholders indicated that something more is needed to reinforce the importance of paying attention to performance during probation.</P>
                <P>One professional organization recommended requiring training in succession planning and diversity leadership during probation. These are important issues, and we are using other venues to bring their importance to that attention of agency leadership and human resources directors. The training needs of individual appointees vary widely. While some may need training in succession planning or diversity leadership, there are other equally critical areas where training might be necessary, such as managing information technology or measuring business results. Agencies should have the flexibility to assess these needs and determine how to address them.</P>
                <P>Two agencies recommended that the appointing authority be allowed to delegate the certification responsibility, and we agree. The final regulations provide that the appointing authority, or his or her designee, must certify that the appointee performed at the level of excellence expected of a senior executive during the probationary period.</P>
                <HD SOURCE="HD1">Pool of Limited Appointment Authorities</HD>
                <P>The proposed regulations would increase the pool of limited appointment authorities currently available to agencies from 2 percent to 3 percent of their total SES allocation. Use of this pool authority is restricted to appointments of individuals with career or career-type appointments outside the SES.</P>
                <P>Most commenters supported this provision. One agency recommended that the pool be increased to 5 percent. One professional organization opposed the provision, stating that it would encourage and facilitate more temporary SES appointments and would jeopardize OPM's traditional oversight role. However, Congress intended that a number of appointments in the SES be temporary, and set a maximum of 5 percent of the Governmentwide SES allocation to prevent excessive use of the authority. Since the SES was established in 1978, no more than 2.5 percent have been limited appointees, well within the congressional limit. Increasing the agency pool authority by 1 percent gives agencies some additional flexibility, while giving OPM enough reserves to address other limited appointment needs that cannot be met with the agencies' delegated authority. The final rule adopts the amendment as proposed.</P>
                <P>
                    In exercising this delegated authority, agencies must continue to comply with all other statutory and regulatory provisions affecting limited appointments, 
                    <E T="03">e.g.,</E>
                     that an appointment be made only to a general position; that the appointee meet the qualifications required for the position; and that the appointment is to a non-continuing, project-type position. OPM will continue to monitor use of this appointment authority to ensure compliance with the statutory 5 percent limit on SES limited appointments Governmentwide and that appointments are being  made in accordance with statutory and regulatory requirements.
                </P>
                <HD SOURCE="HD1">E.O. 12866, Regulatory Review</HD>
                <P>This rule has been reviewed by the Office of Management and Budget in accordance with E.O. 12866.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>I certify that these regulations will not have a significant economic impact on a substantial number of small entities because the regulations pertain only to Federal employees and agencies.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 5 CFR Part 317</HD>
                    <P>Government employees.</P>
                </LSTSUB>
                <SIG>
                    <FP>Office of Personnel Management.</FP>
                    <NAME>Janice R. Lachance,</NAME>
                    <TITLE>Director.</TITLE>
                </SIG>
                <REGTEXT TITLE="5" PART="317?">
                    <AMDPAR>Accordingly, OPM is amending 5 CFR Part 317 as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 317—EMPLOYMENT IN THE SENIOR EXECUTIVE SERVICE</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 317 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>5 U.S.C. 3392, 3393, 3393a, 3395, 3397, 3593 and 3596.</P>
                    </AUTH>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart E—Career Appointments</HD>
                    </SUBPART>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="317">
                    <AMDPAR>2. Amend § 317.501 by revising the section heading, the first sentence of paragraph (c)(2), and paragraph (c)(6), to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 317.501 </SECTNO>
                        <SUBJECT>Recruitment and selection for initial SEC career appointment be achieved from the brightest and most diverse pool possible.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(2) Provide that the ERB  consider the executive and technical qualifications of each candidate, other than those found ineligible because they do not meet the requirements of the vacancy announcement. * * *</P>
                        <STARS/>
                        <P>(6) Provide that the appointing authority select from among the candidates identified as best qualified by the ERB and certify the candidate's executive and technical qualifications.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="317">
                    <AMDPAR>3. Amend § 317.502 by revising paragraph (e) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 317.502 </SECTNO>
                        <SUBJECT>Qualifications Review Board certification.</SUBJECT>
                        <STARS/>
                        <P>(e) An action to convert a “noncareer-type” employee to a career SES appointment in the employee's current position or a successor to that position will not be forwarded to a QRB. A “noncareer-type” employee includes a noncareer SES appointee, a Schedule C appointee, or equivalent.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="317">
                    <AMDPAR>4. Amend § 317.403 by revising paragraph (a); redesignating paragraphs (b) through (f) as paragraphs (c) through (g), respectively; adding a new paragraph (b); and revising the last sentence in newly redesignated paragraph (f) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 317.503 </SECTNO>
                        <SUBJECT>Probationary period.</SUBJECT>
                        <P>
                            (a) An individual's initial appointment as an SES career appointee 
                            <PRTPAGE P="33741"/>
                            becomes final only after the individual has served a 1-year probationary period as a career appointee; there has been an assessment of the appointee's performance during the probationary period; and the appointing authority, or his or her designee, has certified that the appointee performed at the level of excellence expected of a senior executive during the probationary period.
                        </P>
                        <P>(b) When a career appointee's executive qualification have been certified by a Qualifications Review Board on the basis of special or unique qualities, as described in § 317.502(c), the probationary assessment must address any executive development activities the agency identified in support of the request for QRB certification.</P>
                        <STARS/>
                        <P>(f) * * * The individual, however, need not be recertified by a QRB unless the individual was removed for performance or disciplinary reasons.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="317">
                    <AMDPAR>5. In Subpart F, the heading for the subpart is revised to read as follows:</AMDPAR>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart F—Noncareer and Limited Appointments</HD>
                    </SUBPART>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="317">
                    <AMDPAR>6. Amend § 317.601, paragraph (c)(1), by revising the first sentence to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 317.601 </SECTNO>
                        <SUBJECT>Authorization.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(1) Agencies are provided a pool of limited appointment authorities equal to 3 percent of their Senior Executive Service (SES) position allocation, or one authority, whichever is greater. * * *</P>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13053 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6325-01-M</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service </SUBAGY>
                <CFR>7 CFR Parts 360 and 361 </CFR>
                <DEPDOC>[Docket No. 99-064-2] </DEPDOC>
                <SUBJECT>Noxious Weeds; Update of Weed and Seed Lists </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Animal and Plant Health Inspection Service, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        We are amending the noxious weeds regulations by adding 
                        <E T="03">Homeria</E>
                         spp. (cape tulips) to the list of terrestrial weeds. Listed noxious weeds may be moved into or through the United States or interstate only under a written permit and under conditions that would not involve a danger of dissemination of the weeds. This action is necessary to prevent the artificial spread of noxious weeds into noninfested areas of the United States. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>June 26, 2000. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. Polly Lehtonen, Botanist, Permits and Risk Assessment, PPQ, APHIS, 4700 River Road Unit 133, Riverdale, MD 20737-1236; (301) 734-8896. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>
                    The noxious weed regulations were promulgated under authority of the Federal Noxious Weed Act (FNWA) of 1974, as amended (7 U.S.C. 2801 
                    <E T="03">et seq.</E>
                    ), and are set forth in 7 CFR part 360. They contain restrictions on the movement of listed noxious weeds into or through the United States and interstate. 
                </P>
                <P>
                    Under the authority of the Federal Seed Act (FSA) of 1939, as amended (7 U.S.C. 1551 
                    <E T="03">et seq.</E>
                    ), the U.S. Department of Agriculture (USDA) regulates the importation and interstate movement of certain agricultural and vegetable seeds and screenings. Title III of the FSA, “Foreign Commerce,” requires shipments of imported agricultural and vegetable seeds to be labeled correctly and to be tested for the presence of the seeds of certain noxious weeds as a condition of entry into the United States. The Animal and Plant Health Inspection Service's (APHIS) regulations implementing the provisions of title III of the FSA are found in 7 CFR part 361. A list of noxious weed seeds is contained in § 361.6. Paragraph (a)(1) of § 361.6 lists species of noxious weed seeds with no tolerances applicable to their introduction into the United States. 
                </P>
                <P>
                    On December 27, 1999, we published in the 
                    <E T="04">Federal Register</E>
                     (64 FR 72293-72296, Docket No. 99-064-1) a proposal to amend the noxious weed regulations by adding Homeria spp. (cape tulips) to the list of terrestrial noxious weeds in § 360.200(c) and to the list of seeds with no tolerances applicable to their introduction in § 361.6(a)(1). 
                </P>
                <P>We held a public hearing on the proposed rule on February 1, 2000. No one came to speak about the proposed rule. We also solicited comments concerning our proposal for 60 days ending February 25, 2000. We received one comment by that date. The comment was from a representative of a foreign government. We carefully considered the comment, and have discussed its concerns below. </P>
                <P>
                    <E T="03">Comment:</E>
                     APHIS should conduct its own comprehensive review to assess the number of 
                    <E T="03">Homeria</E>
                     spp. already present in the United States and their distribution, by species. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     As stated in our proposed rule, APHIS has been unable to determine the number and distribution of 
                    <E T="03">Homeria</E>
                     spp. in the United States. Based on information available from literature and known herbarium collections, there are no known established, feral populations of 
                    <E T="03">Homeria</E>
                     spp. in the United States. In our proposed rule, we asked the public to provide us with information on what species of 
                    <E T="03">Homeria</E>
                     are being planted and where. Due to the limited resources available to fund monitoring and survey programs in regard to noxious weeds, we are unable to conduct additional reviews specific to 
                    <E T="03">Homeria</E>
                     spp. We will continue to monitor and conduct surveys at current levels, and as resources permit. If, in the future, we are able to determine that certain species of the genus 
                    <E T="03">Homeria</E>
                     have become widespread, then we will consider removing those particular species from the list of noxious weeds at that time. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     APHIS should assess the potential for 
                    <E T="03">Homeria</E>
                     spp. to set seeds under the U.S. cultural practices and the potential for 
                    <E T="03">Homeria</E>
                     spp. to become established as weeds in agricultural areas of the United States. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     APHIS has no reason to doubt that most species of 
                    <E T="03">Homeria</E>
                     will set seed in the United States. Using a simulation model for predicting the effects of climate on the distribution of plants, we matched locations of infestations of 
                    <E T="03">Homeria</E>
                     spp. in Australia to locations with similar climate in the United States. Based on the results of the simulation, we have reason to believe that 
                    <E T="03">Homeria</E>
                     spp. presents a significant risk of becoming established as a weed in certain areas of the United States, especially along the west coast and in Texas. 
                </P>
                <P>
                    Prolific seed production is only one indicator of high dispersal or spread potential. At least one species of the genus 
                    <E T="03">Homeria, H. miniata</E>
                    , does not produce viable seeds, but produces cormils in each leaf axil and around the developing corm at the base of the plant. The cormils may remain dormant and build up in established patches, serving as effective dispersal agents. If APHIS determines in the future that certain species of the genus 
                    <E T="03">Homeria</E>
                     do not produce seed or cormils, we will consider relieving restrictions on the importation of those species. 
                    <PRTPAGE P="33742"/>
                </P>
                <P>
                    <E T="03">Comment:</E>
                      
                    <E T="03">Homeria</E>
                     spp. may not present the same degree of risk in the United States as they have in South Africa and Australia, due probably to unique pasture and animal husbandry situations in these countries. APHIS could investigate whether 
                    <E T="03">Homeria</E>
                     spp. would cause any economic losses in U.S. pastures, particularly taking into account the pasture management and animal husbandry systems being used in the country. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     Again, APHIS has determined that several areas of the United States provide ideal climate conditions for the establishment of 
                    <E T="03">Homeria</E>
                     spp. As stated in our proposed rule, we believe there is a significant risk associated with the importation of seeds of 
                    <E T="03">Homeria</E>
                     spp. as contaminants of shipments of Australian oats or other varieties of seeds. We believe that such shipments provide a direct path for establishment of 
                    <E T="03">Homeria</E>
                     spp. in U.S. pastures, which could result in the poisoning of livestock, reduction of carrying capacity, and substantial losses for U.S. farmers. 
                </P>
                <P>
                    Further, our review of the scientific literature has revealed that species of the genus 
                    <E T="03">Homeria</E>
                     have escaped from garden plantings in Australia and New Zealand into surrounding areas. According to the literature, dispersal occurs by the movement of corms and seeds, aided by humans, animals, wind, and water. When plants dry out at the end of the growing season, they may break off at the soil level, with seed heads attached. The dry plants then may blow around the ground surface, scattering seeds. 
                </P>
                <P>
                    In the absence of any data regarding imported species of the genus 
                    <E T="03">Homeria</E>
                     that have become widely distributed in the United States or imported species that do not produce cormils or seeds, and for the reasons given in the proposed rule and in this document, we are adopting the proposed rule as a final rule, without change. 
                </P>
                <HD SOURCE="HD1">Executive Order 12866 and Regulatory Flexibility Act </HD>
                <P>This rule has been reviewed under Executive Order 12866. For this action, the Office of Management and Budget has waived its review process required by Executive Order 12866. </P>
                <P>In accordance with 5 U.S.C. 604, we have performed a final regulatory flexibility analysis, which is set forth below, regarding the economic effects of this rule on small entities. </P>
                <P>In accordance with the FNWA, the Secretary of Agriculture is authorized to promulgate regulations to prevent the movement of any noxious weed into the United States, or interstate, except under conditions prescribed by the Secretary. </P>
                <P>
                    This rule will add 
                    <E T="03">Homeria</E>
                     spp. (cape tulips) to the list of Federal noxious weeds and to the list of seeds with no tolerances applicable to their introduction. 
                </P>
                <P>
                    <E T="03">Homeria</E>
                     spp. (cape tulips) are not known to exist in the United States in the wild. However, 
                    <E T="03">Homeria</E>
                     spp. have been imported into the United States under the Bulb Preclearance Program since 1994, with increasing numbers of imports each year. We estimate that over 1.8 million corms of 
                    <E T="03">Homeria</E>
                     spp. were received in the United States between July 1994 and March 1999. However, data on the distribution of 
                    <E T="03">Homeria</E>
                     spp. are not available. Persons who import or purchase 
                    <E T="03">Homeria</E>
                     spp., including those in the nursery trade, could be affected by this rule. However, data on the number and location of persons who import or purchase 
                    <E T="03">Homeria</E>
                     spp. are not available. 
                </P>
                <P>
                    As stated above, 
                    <E T="03">Homeria</E>
                     spp. nursery stock has been imported into the United States for several years without restriction. Recently, APHIS inspectors found seeds of 
                    <E T="03">Homeria</E>
                     spp. in shipments of Australian oats to the United States. As a result of this finding, APHIS conducted a risk assessment to determine the potential effects of 
                    <E T="03">Homeria</E>
                     spp. on U.S. agriculture. The risk assessment revealed that 
                    <E T="03">Homeria</E>
                     spp. may present a high risk to U.S. agriculture and that 
                    <E T="03">Homeria</E>
                     spp. meet the criteria for listing as a Federal noxious weed. 
                </P>
                <P>
                    Since imported Australian oats are likely to be used as a feed for horses and other livestock, it is likely that the 
                    <E T="03">Homeria</E>
                     spp. seeds could be introduced into grazing lands and paddocks, where they could do the following: 
                </P>
                <P>• Poison livestock and/or humans. Livestock may die within 12 hours or less after ingesting the leaves. </P>
                <P>• Reproduce and persist in prolific fashion, thus crowding out desirable plants and competing with them for soil nutrients, reducing the carrying capacity of pastures and reducing crop yields. </P>
                <P>
                    Historical data show that, in the 1980's in South Africa, poisoning from 
                    <E T="03">Homeria</E>
                     spp. and a related genus resulted in losses of $2.5 to $3 million per year in livestock. All classes of livestock are susceptible, but cattle, sheep, goats, and donkeys are most likely to suffer poisoning under natural conditions. Further, since 
                    <E T="03">Homeria</E>
                     spp. could grow on cultivated land, they may be cut with forage and cause poisoning in stall-fed animals. If 
                    <E T="03">Homeria</E>
                     spp. are introduced into the United States via Australian oats, U.S. livestock producers could be expected to experience livestock losses similar to those experienced by South Africa in the 1980's. 
                </P>
                <HD SOURCE="HD1">Effects on Small Entities </HD>
                <P>
                    The unchecked spread of 
                    <E T="03">Homeria</E>
                     spp. into the United States can be expected to have a negative economic effect on livestock operations in the United States, whether small or large, given significant negative effects on the regions in Australia and South Africa where 
                    <E T="03">Homeria</E>
                     spp. are already established. In responding to the potential harm caused by 
                    <E T="03">Homeria</E>
                     spp. to livestock and grazing lands, one or more organizations or governmental jurisdictions in affected areas could incur control costs if the weed were to be introduced into the environment. Although the size and magnitude of such potential costs are not known, it is clear that this rule will help to prevent the need for such expenditures. 
                </P>
                <P>
                    We are aware that there are persons in the nursery trade who import and distribute 
                    <E T="03">Homeria</E>
                     spp. nursery stock, especially corms. We have no data available on the location, number, or size of those businesses; however, it is likely that the majority of those businesses could be classified as small entities. In our proposed rule, we requested that the public provide any available data relevant to volumes and distribution of imported 
                    <E T="03">Homeria</E>
                     spp. nursery stock. We received no relevant data in response to our request. Further, we asked the public to provide information on the current distribution and taxonomy of 
                    <E T="03">Homeria</E>
                     spp. in the United States in order to determine if certain species of 
                    <E T="03">Homeria</E>
                     spp. are widespread, and, therefore, should be excluded from the noxious weed regulations. We received no information in response to this request, and, therefore, are adopting our proposed rule as a final rule, without change. 
                </P>
                <P>
                    We believe that adding 
                    <E T="03">Homeria</E>
                     spp. to the list of Federal noxious weeds will help preclude potential economic and ecological consequences that could result from its spread. 
                </P>
                <HD SOURCE="HD1">Alternatives Considered </HD>
                <P>
                    We considered two alternatives to this rule. One alternative was to make no changes in the regulations; 
                    <E T="03">i.e.,</E>
                     to not add 
                    <E T="03">Homeria</E>
                     spp. to the list of Federal noxious weeds. We have rejected that alternative because of the potential economic and ecological consequences that we believe would result from the spread 
                    <E T="03">Homeria</E>
                     spp. We also considered exempting certain species of the genus 
                    <E T="03">Homeria</E>
                     from being listed as noxious weeds if we received information documenting that certain 
                    <PRTPAGE P="33743"/>
                    species had become widely distributed in the United States. We did not receive any information on the distribution of any species of the genus 
                    <E T="03">Homeria</E>
                    , and, therefore, could not select that alternative. 
                </P>
                <P>This final rule contains no new information collection or recordkeeping requirements. </P>
                <HD SOURCE="HD1">Executive Order 12372 </HD>
                <P>This program/activity is listed in the Catalog of Federal Domestic Assistance under No. 10.025 and is subject to Executive Order 12372, which requires intergovernmental consultation with State and local officials. (See 7 CFR part 3015, subpart V.) </P>
                <HD SOURCE="HD1">Executive Order 12988 </HD>
                <P>This final rule has been reviewed under Executive Order 12988, Civil Justice Reform. This rule: (1) Preempts all State and local laws and regulations that are inconsistent with this rule; (2) has no retroactive effect; and (3) does not require administrative proceedings before parties may file suit in court challenging this rule. </P>
                <HD SOURCE="HD1">Paperwork Reduction Act </HD>
                <P>
                    This final rule contains no new information collection or recordkeeping requirements under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ). 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects </HD>
                    <CFR>7 CFR Part 360 </CFR>
                    <P>Imports, Plants (Agriculture), Quarantine, Reporting and recordkeeping requirements, Transportation, Weeds. </P>
                    <CFR>7 CFR Part 361 </CFR>
                    <P>Agricultural commodities, Imports, Labeling, Quarantine, Reporting and recordkeeping requirements, Seeds, Vegetables, Weeds. </P>
                </LSTSUB>
                <REGTEXT TITLE="7" PART="360">
                    <AMDPAR>Accordingly, we are amending 7 CFR parts 360 and 361 as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 360—NOXIOUS WEED REGULATIONS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 360 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>7 U.S.C. 2803 and 2809; 7 CFR 2.22, 2.80, and 371.2(c). </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="360">
                    <SECTION>
                        <SECTNO>§ 360.200 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                    </SECTION>
                    <AMDPAR>
                        2. In § 360.200, paragraph (c) is amended by adding, in alphabetical order, an entry for “
                        <E T="03">Homeria</E>
                         spp.”. 
                    </AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="361">
                    <PART>
                        <HD SOURCE="HED">PART 361—IMPORTATION OF SEED AND SCREENINGS UNDER THE FEDERAL SEED ACT </HD>
                    </PART>
                    <AMDPAR>3. The authority citation for part 361 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>7 U.S.C. 1581-1610; 7 CFR 2.22, 2.80, and 371.2(c). </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="361">
                    <SECTION>
                        <SECTNO>§ 361.6 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                    </SECTION>
                    <AMDPAR>
                        4. In § 361.6, paragraph (a)(1) is amended by adding, in alphabetical order, an entry for “
                        <E T="03">Homeria</E>
                         spp.”. 
                    </AMDPAR>
                </REGTEXT>
                <SIG>
                    <DATED>Done in Washington, DC, this 19th day of May 2000. </DATED>
                    <NAME>Craig A. Reed, </NAME>
                    <TITLE>Administrator, Animal and Plant Health Inspection Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13158 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-34-U </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">FARM CREDIT ADMINISTRATION </AGENCY>
                <CFR>12 CFR Part 614 </CFR>
                <RIN>RIN 3052-AB87 </RIN>
                <SUBJECT>Loan Policies and Operations; Participations; Effective Date </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Farm Credit Administration. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of effective date. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Farm Credit Administration (FCA) published a final rule under part 614 on April 25, 2000 (65 FR 24101). This final rule deletes requirements for a Farm Credit System (Farm Credit or System) institution to provide notice to or seek consent from other System institutions when it buys participation interests in loans originated outside its chartered territory. Repealing these notice and consent requirements can help increase the flow and availability of agricultural credit and help diversify geographic and industry concentrations in the loan portfolios of Farm Credit banks and associations. As a result of this rule, a Farm Credit bank or association will no longer need approval from other System institutions when it buys participations in loans from non-System lenders. In accordance with 12 U.S.C. 2252, the effective date of the final rule is 30 days from the date of publication in the 
                        <E T="04">Federal Register</E>
                         during which either or both Houses of Congress are in session. Based on the records of the sessions of Congress, the effective date of the regulations is May 25, 2000. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>The regulation amending 12 CFR part 614 published on April 25, 2000 (65 FR 24101) is effective May 25, 2000.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P> </P>
                    <FP SOURCE="FP-1">S. Robert Coleman, Senior Policy Analyst, Office of Policy and Analysis, Farm Credit Administration, McLean, VA 22102-5090, (703) 883-4498; or</FP>
                    <FP SOURCE="FP-1">Richard A. Katz, Senior Attorney, Office of General Counsel, Farm Credit Administration, McLean, VA 22102-5090, (703) 883-4020, TDD (703) 883-4444. </FP>
                    <FP>(12 U.S.C. 2252(a)(9) and (10)) </FP>
                    <SIG>
                        <DATED>Dated: May 22, 2000.</DATED>
                        <NAME>Vivian L. Portis,</NAME>
                        <TITLE>Secretary, Farm Credit Administration Board.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13191 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6705-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <CFR>14 CFR Part 39 </CFR>
                <DEPDOC>[Docket No. 99-SW-04-AD; Amendment 39-11729; AD 2000-10-05] </DEPDOC>
                <RIN>RIN 2120-AA64 </RIN>
                <SUBJECT>Airworthiness Directives; Eurocopter France Model SE.3160, SA.316B, SA.316C, SA.319B, SA330F, SA330G, SA330J, SA341G, and SA342J Helicopters </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This amendment adopts a new airworthiness directive (AD) that applies to Eurocopter France Model SE.3160, SA.316B, SA.316C, SA.319B, SA330F, SA330G, SA330J, SA341G, and SA342J helicopters. This AD requires inspecting each inflation head and union nut on certain emergency flotation gear nitrogen cylinders and replacing each cracked inflation head with an airworthy inflation head. This amendment is prompted by the discovery of cracked inflation heads during routine maintenance inspections of emergency flotation systems. The actions specified by this AD are intended to prevent an emergency flotation gear nitrogen cylinder from exploding with resultant high velocity shrapnel, which could cause airframe damage or personal injury and subsequent loss of control of the helicopter. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective June 29, 2000. </P>
                    <P>The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of June 29, 2000. </P>
                </DATES>
                <ADD>
                    <PRTPAGE P="33744"/>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The service information referenced in this AD may be obtained from American Eurocopter Corporation, 2701 Forum Drive, Grand Prairie, Texas 75053-4005, telephone (972) 641-3460, fax (972) 641-3527. This information may be examined at the FAA, Office of the Regional Counsel, Southwest Region, 2601 Meacham Blvd., Room 663, Fort Worth, Texas 76137; or at the Office of the Federal Register, 800 North Capitol Street, NW., suite 700, Washington, DC. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Robert McCallister, Aviation Safety Engineer, FAA, Rotorcraft Directorate, Rotorcraft Standards Staff, 2601 Meacham Blvd., Fort Worth, Texas 76137, telephone (817) 222-5121, fax (817) 222-5961. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    A proposal to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) to include an AD that applies to Eurocopter France Model SE.3160, SA.316B, SA.316C, SA.319B, SA330F, SA330G, SA330J, SA341G, and SA342J helicopters was published in the 
                    <E T="04">Federal Register</E>
                     on December 10, 1999 (64 FR 69206). That action proposed to require inspecting each inflation head and union nut on certain emergency flotation gear nitrogen cylinders and replacing each cracked inflation head with an airworthy inflation head. 
                </P>
                <P>Interested persons have been afforded an opportunity to participate in the making of this amendment. No comments were received on the proposal or the FAA's determination of the cost to the public. The FAA has determined that air safety and the public interest require the adoption of the rule as proposed except for minor editorial changes. </P>
                <P>The FAA estimates that 114 helicopters of U.S. registry will be affected by this AD, that it will take approximately 4 work hours per helicopter to accomplish the required actions, and that the average labor rate is $60 per work hour. Required parts will cost approximately $2,138 per helicopter. Based on these figures, the total cost impact of the AD on U.S. operators is estimated to be $271,092. </P>
                <P>The regulations adopted herein 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. Therefore, it is determined that this final rule does not have federalism implications under Executive Order 13132. </P>
                <P>
                    For the reasons discussed above, I certify that this action (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) 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. A final evaluation has been prepared for this action and it is contained in the Rules Docket. A copy of it may be obtained from the Rules Docket at the location provided under the caption 
                    <E T="02">ADDRESSES</E>
                    .
                </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>
                <REGTEXT TITLE="14" PART="39">
                    <AMDPAR>Accordingly, pursuant to the authority delegated to me by the Administrator, the Federal Aviation Administration amends part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows: </AMDPAR>
                    <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>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="39">
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                    </SECTION>
                    <AMDPAR>2. Section 39.13 is amended by adding a new airworthiness directive to read as follows:</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">AD 2000-10-05 Eurocopter France:</E>
                             Amendment 39-11729. Docket No. 99-SW-04-AD. 
                        </FP>
                        <P>
                            <E T="03">Applicability:</E>
                             Model SE.3160, SA.316B, SA.316C, SA.319B, SA330F, SA330G, SA330J, SA341G, and SA342J helicopters with emergency flotation gear nitrogen cylinder, P/N ARZ 74921, with inflation head, part number (P/N) 74929, that has no serial number (S/N), or with a S/N lower than 12000, or has a union nut, P/N 75441 or 75834, installed, certificated in any category. 
                        </P>
                        <NOTE>
                            <HD SOURCE="HED">Note 1:</HD>
                            <P>This AD applies to each helicopter identified in the preceding applicability provision, regardless of whether it has been otherwise modified, altered, or repaired in the area subject to the requirements of this AD. For helicopters that have been modified, altered, or repaired so that the performance of the requirements of this AD is affected, the owner/operator must request approval for an alternative method of compliance in accordance with paragraph (d) of this AD. The request should include an assessment of the effect of the modification, alteration, or repair on the unsafe condition addressed by this AD; and, if the unsafe condition has not been eliminated, the request should include specific proposed actions to address it.</P>
                        </NOTE>
                        <P>
                            <E T="03">Compliance:</E>
                             Required as indicated, unless previously accomplished. 
                        </P>
                        <P>To prevent an emergency flotation gear nitrogen cylinder from exploding with resultant high velocity shrapnel, which could cause airframe damage or personal injury and subsequent loss of control of the helicopter, accomplish the following: </P>
                        <P>(a) For Model SE.3160, SA.316B, SA.316C, SA.319B, SA330F, SA330G, or SA330J helicopters, </P>
                        <P>(1) At the next scheduled emergency flotation gear maintenance inspection or 400 hours time-in-service (TIS), whichever occurs first, accomplish the following: </P>
                        <P>(i) Discharge each emergency flotation gear nitrogen cylinder (cylinder) in accordance with the “Discharge Procedure for the 74921G Cylinder” in Eurocopter France Service Bulletin 05.66, Revision 3, dated May 4, 1998 or Eurocopter France Service Bulletin 05.58, Revision 3, dated May 4, 1998. </P>
                        <P>(ii) Remove the inflation head and degrease the assembly. </P>
                        <P>(iii) Perform a dye penetrant inspection of each inflation head and union nut on each emergency flotation gear nitrogen cylinder. </P>
                        <P>(2) Thereafter, conduct a dye penetrant inspection of each inflation head and union nut on each cylinder at each scheduled emergency flotation gear maintenance inspection or at intervals of not more than 400 hours TIS, whichever occurs first. </P>
                        <P>(b) For Model SA341G or SA342J helicopters, </P>
                        <P>(1) At the next scheduled emergency flotation gear maintenance inspection or 520 hours time-in-service, whichever occurs first, accomplish the following: </P>
                        <P>(i) Discharge each emergency flotation gear nitrogen cylinder in accordance with the “Discharge Procedure for the 74921G Cylinder” in Eurocopter France Service Bulletin 05.19, Revision 3, dated May 4, 1998. </P>
                        <P>(ii) Remove the inflation head and degrease the assembly. </P>
                        <P>(iii) Perform a dye penetrant inspection of each inflation head and union nut on each cylinder. </P>
                        <P>(2) Thereafter, conduct a dye penetrant inspection of each inflation head and union nut on each cylinder at each scheduled emergency flotation gear maintenance inspection or at intervals of not more than 520 hours TIS, whichever occurs first. </P>
                        <P>(c) Before further flight, replace each cracked inflation head, P/N 74929, with an airworthy inflation head having S/N 12000 or higher. </P>
                        <P>(d) An alternative method of compliance or adjustment of the compliance time that provides an acceptable level of safety may be used if approved by the Manager, Regulations Group, Rotorcraft Directorate, FAA. Operators shall submit their requests through an FAA Principal Maintenance Inspector, who may concur or comment and then send it to the Manager, Regulations Group. </P>
                        <NOTE>
                            <HD SOURCE="HED">Note 2:</HD>
                            <P>Information concerning the existence of approved alternative methods of compliance with this AD, if any, may be obtained from the Regulations Group.</P>
                        </NOTE>
                        <P>
                            (e) Special flight permits may be issued in accordance with sections 21.197 and 21.199 of the Federal Aviation Regulations (14 CFR 21.197 and 21.199) to operate the helicopter to a location where the requirements of this AD can be accomplished. 
                            <PRTPAGE P="33745"/>
                        </P>
                        <P>(f) The discharge of each cylinder shall be done in accordance with the “Discharge Procedure for the 74921G Cylinder” in Eurocopter France Service Bulletin 05.66, Revision 3, dated May 4, 1998; Eurocopter France Service Bulletin 05.58, Revision 3, dated May 4, 1998; or Eurocopter France Service Bulletin 05.19, Revision 3, dated May 4, 1998. This incorporation by reference was approved by the Director of the Federal Register in accordance with 5 U.S.C. 552(a) and 1 CFR part 51. Copies may be obtained from American Eurocopter Corporation, 2701 Forum Drive, Grand Prairie, Texas 75053-4005, telephone (972) 641-3460, fax (972) 641-3527. Copies may be inspected at the FAA, Office of the Regional Counsel, Southwest Region, 2601 Meacham Blvd., Room 663, Fort Worth, Texas; or at the Office of the Federal Register, 800 North Capitol Street, NW., suite 700, Washington, DC. </P>
                        <P>(g) This amendment becomes effective on June 29, 2000. </P>
                        <NOTE>
                            <HD SOURCE="HED">Note 3:</HD>
                            <P>The subject of this AD is addressed in Direction Generale De L'Aviation Civile AD's 80-062-041(A) R2, 80-063-030(A) R2, and 80-061-028(A) R2, all dated July 15, 1998.</P>
                        </NOTE>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Fort Worth, Texas, on May 5, 2000. </DATED>
                    <NAME>Eric Bries, </NAME>
                    <TITLE>Acting Manager, Rotorcraft Directorate, Aircraft Certification Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-12351 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <CFR>14 CFR Part 39 </CFR>
                <DEPDOC>[Docket No. 98-CE-112-AD; Amendment 39-11747; AD 99-15-04 R1] </DEPDOC>
                <RIN>RIN 2120-AA64 </RIN>
                <SUBJECT>Airworthiness Directives; The New Piper Aircraft, Inc., Models PA-46-310P and PA-46-350P Airplanes </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This amendment revises Airworthiness Directive (AD) 99-15-04, which currently requires you to calibrate, inspect, and repair or replace portions of the turbine inlet temperature system on all The New Piper Aircraft, Inc. (New Piper) Models PA-46-310P and PA-46-350P airplanes (different actions for different airplane models). Information reveals that the AD should not apply to airplanes where the factory installed turbine inlet temperature gauge and associated probe have been replaced through supplemental type certificate (STC). This AD retains the actions of AD 99-15-04, and restricts the applicability accordingly. The actions specified by this AD are intended to prevent improper engine operation caused by improperly calibrated turbine inlet temperature indicators or defective turbine inlet temperature probes, which could result in engine damage/failure with consequent loss of control of the airplane. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>This AD becomes effective on July 28, 2000. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may examine information related to this AD at FAA, Central Region, Office of the Regional Counsel, Attention: Rules Docket No. 98-CE-112-AD, 901 Locust, Room 506, Kansas City, Missouri 64106. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Donald J. Young, Aerospace Engineer, FAA, Atlanta Aircraft Certification Office, One Crown Center, 1895 Phoenix Boulevard, Suite 450, Atlanta, Georgia 30349; telephone: (770) 703-6079; facsimile: (770) 703-6097; e-mail address: “Donald.Young@faa.gov”. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Events Leading to the Issuance of This AD </HD>
                <P>
                    <E T="03">Has FAA taken any action to this point?</E>
                     Field reports that indicated service accuracy problems with the existing turbine inlet temperature system on certain New Piper Models PA-46-310P and PA-46-350P airplanes caused FAA to issue AD 99-15-04, Amendment 39-11223. This AD currently requires you to accomplish the following: 
                </P>
                <P>1. Calibrate the turbine inlet temperature system to assure the accuracy of the existing turbine inlet temperature indicator and wiring on all airplanes; </P>
                <P>2. Repair or replace any turbine inlet temperature system that fails the calibration test on all airplanes; </P>
                <P>3. Repetitively replace the turbine inlet temperature probe on the Model PA-46-350P airplanes; and </P>
                <P>4. Insert a copy of the AD into the Pilot's Operating Handbook (POH) of certain airplanes. </P>
                <P>Since issuing AD 99-15-04, we have received information to show that the AD should not apply on airplanes where the factory installed turbine inlet temperature gauge and associated probe were replaced through supplemental type certificate (STC). </P>
                <P>
                    To address this issue, we issued a notice of proposed rulemaking (NPRM) to revise AD 99-15-04. This NPRM was published in the 
                    <E T="04">Federal Register</E>
                     on November 5, 1999 (64 FR 60383). The NPRM proposed to continue to require you to accomplish all the actions that AD 99-15-04 currently requires. Those airplanes that do not have a Lewis or Transicoil Turbine Inlet Temperature Gauge and associated probe installed, and where this system was replaced in accordance with an STC, would be excluded from the AD. Relief from the AD is available only if the gauge and probe are replaced through STC and not if a second turbine inlet temperature gauge was installed while retaining the Lewis or Transicoil gauge and probe. 
                </P>
                <P>
                    <E T="03">Was the public invited to comment on the NPRM?</E>
                     The FAA invited interested persons to participate in the making of the amendment. A summary of the comments and FAA's responses follows: 
                </P>
                <HD SOURCE="HD1">Comment Issue No. 1: Provide Justification for Indefinite Life of Probes Installed Through STC </HD>
                <P>
                    <E T="03">What is the commenter's concern?</E>
                     One commenter requests an explanation on how FAA determined that the turbine inlet temperature gauge and associated probe would last indefinitely if installed through STC. 
                </P>
                <P>
                    <E T="03">What is FAA's response to the concern?</E>
                     Our intent of this AD is not to life limit the turbine inlet temperature system. We are issuing the AD to assure that the system is calibrated correctly and assure that certain parts of this system are checked and replaced accordingly. We have not received any service history or other evidence of problems with those systems installed in accordance with an STC. We also have not received any evidence of inadequate maintenance instructions for any system installed in accordance with an STC. If an unsafe condition develops on airplanes with these systems installed per STC, we will issue an AD against airplanes with that specific configuration. 
                </P>
                <P>We are not changing the AD as a result of this comment. </P>
                <HD SOURCE="HD1">Comment Issue No. 2: Provide Specific STC Numbers and Holders </HD>
                <P>
                    <E T="03">What are the commenter's concerns?</E>
                     One commenter requests that FAA include a list of STC numbers and holders of those STC's that provide relief from this AD. This commenter also points out that relief should also be given if New Piper (the manufacturer) develops a new turbine temperature inlet system since we are allowing relief for any STC, whether currently-approved or approved in the future. 
                </P>
                <P>
                    <E T="03">What is FAA's response to the concerns?</E>
                     We have elected not to provide a list of STC's that provide relief because the FAA having to revise the AD every time a new STC was developed and certificated would make tracking of this AD action confusing and impractical. We acknowledge that New 
                    <PRTPAGE P="33746"/>
                    Piper could develop a system that could be eligible for relief from the actions in this AD. In this case, New Piper could request an alternative method of compliance to the AD. If we approve, then New Piper could include a statement in the maintenance instructions that installation of such a system is considered an alternative method of compliance to the AD per a specific FAA letter, or FAA could revise the AD to exclude such systems. 
                </P>
                <P>We are not changing the AD as a result of this comment. </P>
                <HD SOURCE="HD1">Comment Issue No. 3: Include Piper Service Bulletin No. 995A in the AD </HD>
                <P>
                    <E T="03">What is the commenter's concern?</E>
                     One commenter requests that FAA reference Piper Service Bulletin No. 995A, dated April 26, 1996, in the AD. 
                </P>
                <P>
                    <E T="03">What is FAA's response to the concern?</E>
                     Piper Service Bulletin No. 995A, dated April 26, 1996, contains information related to the subject of this AD. However, if you comply with this service bulletin, you have not accomplished all of the actions required by the AD. Therefore, we are not mandating compliance with the service bulletin. Instead we are including the following statement in the AD: “Piper Service Bulletin 995A, dated April 26, 1996, contains information related to the subject matter of this AD.” 
                </P>
                <HD SOURCE="HD1">The FAA's Determination </HD>
                <P>
                    <E T="03">What is FAA's final determination on this issue?</E>
                     After careful review of all available information related to the subject presented above, we have determined that air safety and the public interest require the adoption of the rule as proposed except for the following:
                </P>
                <FP SOURCE="FP-1">—the addition of the statement that Piper Service Bulletin No. 995A contains information related to the subject matter of this AD; and </FP>
                <FP SOURCE="FP-1">—minor editorial corrections.</FP>
                <P>
                    <E T="03">How does the addition and corrections affect the AD?</E>
                     We have determined that the addition and minor corrections will not change the meaning of the AD and will not add any additional burden upon the public than was already proposed. 
                </P>
                <HD SOURCE="HD1">Cost Impact </HD>
                <P>
                    <E T="03">How many airplanes does this AD impact?</E>
                     We estimate that this AD will affect 580 airplanes in the U.S. registry. 
                </P>
                <P>
                    <E T="03">What is the cost impact of the affected airplanes on the U.S. Register?</E>
                     We estimate 4 workhours per airplane to accomplish the calibration at an average labor rate of $60 an hour. Based on these figures, we estimate the cost impact of the calibration on U.S. operators at $139,200, or $240 per airplane. 
                </P>
                <P>We estimate 1 workhour per airplane to accomplish the initial turbine inlet temperature probe replacement at an average labor rate of $60 an hour. Parts cost approximately $518. We estimate the cost impact of the replacement on U.S. operators at $335,240, or $578 per airplane. </P>
                <P>
                    <E T="03">What about repetitive actions?</E>
                     These figures only take into account the initial replacement and do not take into account the cost of subsequent repetitive replacements. We have no way of determining the number of replacements each owner/operator will incur over the life of the affected airplanes. 
                </P>
                <P>
                    <E T="03">What is the cost impact difference between this AD and AD 99-15-04?</E>
                     The cost impact of this AD is the same as that specified in AD 99-15-04. The only difference between AD 99-15-04 and this AD is the exemption of certain airplanes from this AD if a certain turbine inlet temperature gauge and associated probe is installed. 
                </P>
                <HD SOURCE="HD1">Regulatory Impact </HD>
                <P>The regulations adopted herein 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. Therefore, it is determined that this final rule does not have federalism implications under Executive Order 13132. </P>
                <P>
                    The FAA has determined that this action: (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) will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. A copy of the final evaluation prepared for this action is contained in the Rules. We have placed a copy of the final regulatory evaluation prepared for this action in the Rules Docket. You may obtain a copy of it at the Rules Docket at the location provided under the caption 
                    <E T="02">ADDRESSES</E>
                    . 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39 </HD>
                    <P>Air transportation, Aircraft, Aviation safety, Safety.</P>
                </LSTSUB>
                <REGTEXT TITLE="14" PART="39">
                    <HD SOURCE="HD1">Adoption of the Amendment </HD>
                    <AMDPAR>Accordingly, under the authority delegated to me by the Administrator, the Federal Aviation Administration amends part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows: </AMDPAR>
                    <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>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="39">
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                    </SECTION>
                    <AMDPAR>2. FAA amends Section 39.13 by removing Airworthiness Directive (AD) 99-15-04, Amendment 39-11223 (64 FR 37699, July 13, 1999), and adding a new AD to read as follows:</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">99-15-04 R1 The New Piper Aircraft, Inc.:</E>
                             Amendment 39-11747; Docket No. 98-CE-112-AD; Revises AD 99-15-04, Amendment 39-11223.
                        </FP>
                        <P>
                            (a) 
                            <E T="03">What airplanes are affected by this AD?</E>
                             This AD applies to Models PA-46-310P and PA-46-350P airplanes, all serial numbers, that are: 
                        </P>
                        <P>(1) Certificated in any category; and </P>
                        <P>(2) Equipped with a Lewis or Transicoil Turbine Inlet Temperature Gauge and associated probe installed. Relief from the AD is available only if the gauge and probe are replaced through STC and not if a second turbine inlet temperature gauge was installed while retaining the Lewis or Transicoil gauge and probe. </P>
                        <P>
                            (b) 
                            <E T="03">Who must comply with this AD?</E>
                             Anyone who wishes to operate any of the above airplanes on the U.S. Register must comply with this AD. 
                        </P>
                        <P>
                            (c) 
                            <E T="03">What problem does this AD address?</E>
                             The actions required in this AD are intended to detect and correct improperly calibrated turbine inlet temperature indicators or defective turbine inlet temperature probes. This condition, if not detected and corrected, could result in improper engine operation and engine damage/failure with consequent loss of control of the airplane. 
                        </P>
                        <P>(d) What must I do to address this problem? To address this problem, you must accomplish the following actions:</P>
                    </EXTRACT>
                    <PRTPAGE P="33747"/>
                    <P>(1) For the Model PA-46-310P airplanes: </P>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,r100,r100">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">Compliance time </CHED>
                            <CHED H="1">Action </CHED>
                            <CHED H="1">In accordance with </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">(i) Within the next 100 hours time-in-service (TIS) after August 31, 1999 (the effective date of the AD 99-15-04)</ENT>
                            <ENT>(A) Perform the Turbine Inlet Temperature Gauge and Probe Cleaning and Inspection</ENT>
                            <ENT>The PA-46-310P/350P Maintenance Manual, Chapter 77-20-00 (section A.(1)(d), pages 1 and 2). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>(B) Accomplish the Turbine Inlet Temperature System Calibration</ENT>
                            <ENT>The PA-46-310P/350P Maintenance Manual, Chapter 77-20-00 (pages 3 and 4). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(ii) Prior to further flight after the above cleaning, inspection, and calibration</ENT>
                            <ENT>Repair or replace any failed parts (the turbine inlet temperature system indicator cannot be calibrated or the turbine inlet temperature probe fails the inspection) with serviceable parts that are listed in paragraph (e) of this AD</ENT>
                            <ENT>Equipment manufacturer instructions and the applicable maintenance manual. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(iii) Within the next 100 hours TIS after August 31, 1999 (the effective date of the AD 99-15-04), unless the applicable Pilot's Operating Handbook (POH) revision is incorporated as presented in paragraph (f) of this AD</ENT>
                            <ENT>
                                (A) Incorporate the emergency procedures presented in paragraph (g) of this AD into the POH 
                                <LI O="xl">(B) This may be accomplished by inserting a copy of this AD into the POH.</LI>
                            </ENT>
                            <ENT>Not applicable. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(iv) As of July 28, 2000 (the effective date of this AD)</ENT>
                            <ENT>Do not install one of the affected Lewis or Transicoil turbine inlet temperature gauges or probes without assuring that it is airworthy and properly calibrated</ENT>
                            <ENT>Use the procedures located in the previously referenced maintenance manual sections and pages. </ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>(2) For the Model PA-46-350P airplanes:</P>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,r100,r100">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">Compliance time </CHED>
                            <CHED H="1">Action </CHED>
                            <CHED H="1">In accordance with </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">(i) Within the next 100 hours TIS after August 31, 1999 (the effective date of AD 99-15-04)</ENT>
                            <ENT>(A) Perform the Turbine Inlet Temperature Gauge and Probe Cleaning and Inspection</ENT>
                            <ENT>For serial numbers 4622001 through 4622200 and 4636001 through 4636020, utilize the PA-46-350P Maintenance Manual, Chapter 77-20-00 (section 1.C, page 1). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"> </ENT>
                            <ENT>For all serial numbers beginning with 4636021, utilize the PA-46-350P Maintenance Manual, Chapter 77-20-00 (section 1.C, page 1). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>(B) Accomplish the Turbine Inlet Temperature System Calibration</ENT>
                            <ENT>For serial numbers 4622001 through 4622200 and 4636001 through 4636020, utilize the PA-46-350P Maintenance Manual, Chapter 77-20-00 (section 1.I, pages 4 through 7). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"> </ENT>
                            <ENT>For all serial numbers beginning with 4636021, calibration is not required. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(ii) Prior to further flight after the above cleaning, inspection, and calibration</ENT>
                            <ENT>Repair or replace any failed parts (the turbine inlet temperature system indicator cannot be calibrated or the turbine inlet temperature probe fails the inspection) with serviceable parts that are listed in paragraph (e) of this AD</ENT>
                            <ENT>Equipment manufacturer instructions and the applicable maintenance manual. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(iii) Upon accumulating 250 hours TIS on the currently installed turbine inlet temperature probe or within the next 100 hours TIS after August 31, 1999 (the effective date of AD 99-15-04), whichever occurs later, and thereafter at intervals not to exceed 250 hours TIS</ENT>
                            <ENT>Replace the turbine inlet temperature probe with a new part number 481-389 or 481-392 probe</ENT>
                            <ENT>Equipment manufacturer instructions and the applicable maintenance manual. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(iv) Within the next 100 hours TIS after August 31, 1999 (the effective date of the AD 99-15-04), unless the applicable Pilot's Operating Handbook (POH) revision is incorporated as presented in paragraph (f) of this AD</ENT>
                            <ENT>
                                (A) Incorporate the emergency procedures presented in paragraph (g) of this AD into the POH 
                                <LI O="xl">(B) This may be accomplished by inserting a copy of this AD into the POH.</LI>
                            </ENT>
                            <ENT>Not applicable. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(v) As of July 28, 2000 (the effective date of this AD)</ENT>
                            <ENT>Do not install one of the affected Lewis or Transicoil turbine inlet temperature gauges or probes without assuring that it is airworthy and properly calibrated</ENT>
                            <ENT>Use the procedures located in the previously referenced maintenance manual sections and pages. </ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>
                        (3) Operators of the Model PA-46-350P airplanes with over 150 hours TIS on the currently installed turbine inlet temperature probe will have to replace the probe as required in paragraph (d)(2)(iii) of this AD. In this case, the operator may want to accomplish the replacement prior to the Turbine Inlet Temperature Gauge and Probe Cleaning and Inspection, and Turbine Inlet Temperature System Calibration. 
                        <PRTPAGE P="33748"/>
                    </P>
                    <WIDE>
                        <P>
                            (e) 
                            <E T="03">What are the part numbers of the replacement parts referenced in paragraph (d)(2)(ii) of this AD?</E>
                        </P>
                        <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,r100">
                            <TTITLE>  </TTITLE>
                            <BOXHD>
                                <CHED H="1">Equipment name and manufacturer </CHED>
                                <CHED H="1">Part No. </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">(1) Lewis Turbine Inlet Temperature Analog Indicator</ENT>
                                <ENT>471-008. This is the only indicator that has a zero adjustment screw. </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(2) Lewis Turbine Inlet Temperature Digital Indicator</ENT>
                                <ENT>548-811. Since this indicator does not have a zero adjustment screw, you must return it to the factory for adjustment or replacement. </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">(3) Lewis Turbine Inlet Temperature Probe</ENT>
                                <ENT>471-009 for the Model PA-46-310P airplanes and 481-389 or 481-392 for the Model PA-46-350P airplanes. </ENT>
                            </ROW>
                        </GPOTABLE>
                        <P>
                            (f) 
                            <E T="03">What are the POH revisions that can be incorporated instead of the emergency procedures that this AD requires?</E>
                        </P>
                        <P>(1) For operators of the Model PA-46-310P airplanes: </P>
                    </WIDE>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="xs75,r50,r50">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">POH </CHED>
                            <CHED H="1">Revision/date </CHED>
                            <CHED H="1">Affected serial numbers </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">VB-1200</ENT>
                            <ENT>16/March 19, 1999</ENT>
                            <ENT>46-8408001 through 46-8608067 and 4608001 through 4608007. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">VB-1300</ENT>
                            <ENT>13/February 25, 1999</ENT>
                            <ENT>4608008 through 4608140. </ENT>
                        </ROW>
                    </GPOTABLE>
                    <WIDE>
                        <P>(2) For operators of the Model PA-46-350P airplanes: </P>
                        <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="xs75,r50,r50">
                            <TTITLE>  </TTITLE>
                            <BOXHD>
                                <CHED H="1">POH </CHED>
                                <CHED H="1">Revision/date </CHED>
                                <CHED H="1">Affected serial numbers </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">VB-1332</ENT>
                                <ENT>16/November 14, 1997</ENT>
                                <ENT>4622001 through 4622200. </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">VB-1609</ENT>
                                <ENT>1/November 21, 1997</ENT>
                                <ENT>463001 through 4636020.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">VB-1602</ENT>
                                <ENT>1/November 28, 1997</ENT>
                                <ENT>4636021 through 4636131. </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">VB-1446</ENT>
                                <ENT>New/December 3, 1997</ENT>
                                <ENT>4636132 through 4636195. </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">VB-1710</ENT>
                                <ENT>New/February 23, 1999</ENT>
                                <ENT>All serial numbers beginning with 4636196. </ENT>
                            </ROW>
                        </GPOTABLE>
                    </WIDE>
                    <P>
                        (g) 
                        <E T="03">What are the emergency procedures referenced in paragraphs (d)(1)(iii) and (d)(2)(iv) of this AD?</E>
                    </P>
                    <P>(1) For Model PA-46-310P airplanes: </P>
                    <P>(i) If the turbine inlet temperature indication fails during takeoff, climb, descent, or landing, maintain FULL RICH mixture to assure adequate fuel flow for engine cooling. </P>
                    <P>(ii) If the turbine inlet temperature indication fails after cruise power has been set, maintain cruise power setting and lean to 6 gallons per hour (GPH) fuel flow above that specified in the Power Setting Table in Section 5 of the AFM/POH. Continually monitor engine cylinder head and oil temperatures to avoid exceeding temperature limits. </P>
                    <P>(2) For Model PA-46-350P airplanes: </P>
                    <P>(i) If the turbine inlet temperature indication fails during takeoff, climb, descent or landing, set power per the POH Section 5 Power Setting Table and then lean to the approximate POH Power Setting Table fuel flow plus 4 GPH. </P>
                    <P>(ii) If the turbine inlet temperature indication fails after cruise power has been set, maintain the power setting and increase indicated fuel flow by 1 GPH. Continually monitor engine cylinder head and oil temperatures to avoid exceeding temperature limits. </P>
                    <P>
                        (h) 
                        <E T="03">Did The New Piper Aircraft, Inc. develop service information related to this subject?</E>
                         Piper Service Bulletin 995A, dated April 26, 1996, contains information that related to the subject matter of this AD. However, if you comply with this service bulletin, you have not accomplished all of the actions required by the AD. Therefore, we are not mandating compliance with the service bulletin. 
                    </P>
                    <P>
                        (i) 
                        <E T="03">Can the pilot accomplish the action?</E>
                         Anyone who holds at least a private pilot certificate, as authorized by section 43.7 of the Federal Aviation Regulations (14 CFR 43.7), may insert a copy of this AD into the POH, as required by this AD. You must make an entry into the aircraft records that shows compliance with this AD, in accordance with section 43.9 of the Federal Aviation Regulations (14 CFR 43.9). 
                    </P>
                    <P>
                        (j) 
                        <E T="03">Can I comply with this AD in any other way?</E>
                         You may use an alternative method of compliance or adjust the compliance time if: 
                    </P>
                    <P>(1)(i) Your alternative method of compliance provides an equivalent level of safety; and </P>
                    <P>(ii) The Manager, Atlanta Aircraft Certification Office (ACO), approves your alternative. Submit your request through an FAA Principal Maintenance Inspector, who may add comments and then send it to the Manager, Atlanta ACO. </P>
                    <P>(2) Alternative methods of compliance approved in accordance with AD 99-15-04 are approved as alternative methods of compliance for this AD. </P>
                    <NOTE>
                        <HD SOURCE="HED">Note:</HD>
                        <P>This AD applies to each airplane identified in paragraph (a) of this AD, regardless of whether it has been modified, altered, or repaired in the area subject to the requirements of this AD. For airplanes that have been modified, altered, or repaired so that the performance of the requirements of this AD is affected, the owner/operator must request approval for an alternative method of compliance in accordance with paragraph (j) of this AD. The request should include an assessment of the effect of the modification, alteration, or repair on the unsafe condition addressed by this AD; and, if you have not eliminated the unsafe condition, specific actions you propose to address it.</P>
                    </NOTE>
                    <P>
                        (k) 
                        <E T="03">Where can I get information about any already-approved alternative methods of compliance?</E>
                         Contact Donald Young, Aerospace Engineer, Atlanta Aircraft Certification Office, One Crown Center, 1895 Phoenix Boulevard, Suite 450, Atlanta, Georgia 30349; telephone: (770) 703-6079; facsimile: (770) 703-6097; e-mail address: “Donald.Young@faa.gov”. 
                    </P>
                    <P>
                        (l) 
                        <E T="03">What if I need to fly the aircraft to another location to comply with this AD?</E>
                         The FAA can issue a special flight permit under §§ 21.197 and 21.199 of the Federal Aviation Regulations (14 CFR 21.197 and 21.199) to operate your aircraft to a location where you can accomplish the requirements of this AD. 
                    </P>
                    <P>
                        (m) 
                        <E T="03">Does this AD action affect any existing AD actions?</E>
                         This amendment revises AD 99-15-04, Amendment 39-11223. 
                    </P>
                    <P>
                        (n) 
                        <E T="03">When does this amendment become effective?</E>
                         This amendment becomes effective on July 28, 2000. 
                    </P>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Kansas City, Missouri, on May 17, 2000. </DATED>
                    <NAME>Michael Gallagher, </NAME>
                    <TITLE>Manager, Small Airplane Directorate, Aircraft Certification Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13083 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <PRTPAGE P="33749"/>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Airspace Docket No. 2000-ASW-10]</DEPDOC>
                <SUBJECT>Revision of Class D Airspace, Alexandria England AFB, LA; Revocation of Class D Airspace, Alexandria Esler Regional Airport, LA; and Revision of Class E Airspace, Alexandria, LA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Direct final rule; confirmation of effective date.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice confirms the effective date of a direct final rule which revises Class D Airspace at Alexandria England AFB, LA; revokes Class D Airspace at Alexandria Esler Regional Airport, LA; and revises Class E Airspace at Alexandria, LA.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>The direct final rule published at 65 FR 15860 is effective 0901 UTC, August 10, 2000.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Donald J. Day, Airspace Branch, Air Traffic Division, Southwest Region, Federal Aviation Administration, Fort Worth, TX 76193-0520, telephone: 817-222-5593. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The FAA published this direct final rule with a request for comments in the 
                    <E T="04">Federal Register</E>
                     on March 24, 2000, (65 FR 15860). The FAA uses the direct final rulemaking procedure for a noncontroversial rule where the FAA believes that there will be no adverse public comment. This direct final rule advised the public that no adverse comments were anticipated, and that unless a written adverse comment, or a written notice of intent to submit such an adverse comment, were received within the comment period, the regulation would become effective on August 10, 2000. No adverse comments were received, and, thus, this action confirms that this direct final rule will be effective on that date.
                </P>
                <SIG>
                    <DATED>Issued in Fort Worth, TX, on May 16, 2000.</DATED>
                    <NAME>JoEllen Casilio,</NAME>
                    <TITLE>Assistant Manager, Air Traffic Division, Southwest Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13176 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Airspace Docket No. 99-AEA-07] </DEPDOC>
                <SUBJECT>Establishment of Class D Airspace; Salisbury, MD</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA) DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action establishes Class D airspace area at Salisbury, MD. The commissioning of a new Air Traffic Control Tower (ATCT) at the Salisbury-Ocean City, Wicomico Regional Airport (SBY) has made this proposal necessary. Controlled airspace extending upward from the surface to 2,500 feet Above Ground Level (AGL) is needed to accommodate Instrument Flight Rules (IFR) operations to the airport.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>0901 UTC, 13 July 2000.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Francis Jordan, Airspace Specialist, Airspace Branch, AEA-520, Air Traffic Division, Eastern Region, Federal Aviation Administration, Federal Building #111, John F. Kennedy International Airport, Jamaica, New York 11430, telephone: (718) 553-4521.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">History</HD>
                <P>
                    On June 7, 1999, a notice proposing to amend Part 71 of the Federal Aviation Regulations (14 CFR part 71) to establish Class D airspace at Salisbury, MD was published in the 
                    <E T="04">Federal Register</E>
                     (64 FR 30259-30260). A new Air Traffic Control Tower (ATCT) made this action necessary. Controlled airspace extending upward to 2,500 feet above Ground Level (AGL) is needed to contain IFR operations in controlled airspace during portions of the terminal operation and while transitioning between the en-route and terminal environments. The notice proposed to designate the entire Class E airspace that is now in existence to Class D airspace. Interested parties were invited to participate in this rulemaking proceeding by submitting written comments on the proposal to the FAA. Comments to the proposal were received which labeled the proposed Class D airspace excessive when it includes all of the Class E airspace assigned to Salisbury Airport area. After further review the airspace area is amended so that the established Class D airspace is only the area within a 6.6 mile radius of the airport.
                </P>
                <P>The coordinates for this airspace docket are based on North American Datum 83. </P>
                <P>Class D airspace areas designations for airspace extending upward from the surface to a specified level are published in paragraph 5000 of FAA Order 7400.9F, dated September 10, 1999, and effective September 16, 1999, which is incorporated by reference in 14 CFR 71.1. The Class D designation listed in this document will be published subsequently in the Order.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This amendment to Part 71 of the Federal Aviation Regulations (14 CFR part 71) establishes Class D airspace at Salisbury, MD extending upward from the surface to 2,500 feet AGL.</P>
                <P>The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. Therefore, this regulation—(1) Is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a Regulatory Evaluation as the anticipated impact is so minimal. Since this is a routine matter that will only affect air traffic procedures and air navigation it is certified that this rule will not have significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">Adoption of the Amendment</HD>
                <REGTEXT TITLE="14" PART="71">
                    <AMDPAR>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 71—[AMENDED]</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40103, 40113, 40120; EO 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="71">
                    <SECTION>
                        <SECTNO>§ 71.1 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of Federal Aviation Administration Order 7400.9F, Airspace Designations and Reporting Points, dated September 10, 1999, and effective September 16, 1999, is amended as follows:</AMDPAR>
                    <EXTRACT>
                        <PRTPAGE P="33750"/>
                        <HD SOURCE="HD2">Paragraph 5000 Class D airspace area consisting of specified airspace within which all aircraft operators are subject to operating rules and equipment requirements of Part 91 of the Federal Aviation Regulation.</HD>
                        <HD SOURCE="HD1">AEA MD D Salisbury, MD [Original]</HD>
                        <HD SOURCE="HD2">Salisbury-Ocean City, Wicomico County Regional Airport, MD.</HD>
                        <FP SOURCE="FP1-2">(Lat. 3820.26 N/long. 753062 W)</FP>
                        <FP SOURCE="FP-2">Salisbury VORTAC</FP>
                        <FP SOURCE="FP1-2">(Lat. 3820.70 N/long. 753064 W)</FP>
                        <P>That airspace extending upward from the surface to an including 2,500 feet MSL within a 6.6 mile radius of the Salisbury-Wicomico County Regional Airport. This Class D airspace area is effective during specific dates and times established in advance by a Notice to Airmen. The effective date and time will thereafter be continuously published in the Airport Facility Directory.</P>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Jamaica, New York on May 9, 2000.</DATED>
                    <NAME>Franklin D. Hatfield,</NAME>
                    <TITLE>Manager, Air Traffic Division, Eastern Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13173  Filed-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Airspace Docket No. 2000-ASW-08]</DEPDOC>
                <SUBJECT>Revision of Class E Airspace; Waco, TX</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Direct final rule; confirmation of effective date. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice confirms the effective date of a direct final rule which revises Class E airspace at Waco, TX.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>The direct final rule published at 65 FR 14856 is effective 0901 UTC, August 10, 2000.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Donald J. Day, Airspace Branch, Air Traffic Division, Southwest Region, Federal Aviation Administration, Fort Worth, TX 76193-0520, telephone: 817-222-5593.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The FAA published this direct final rule with a request for comments in the 
                    <E T="04">Federal Register</E>
                     on March 20, 2000, (65 FR 14856). The FAA uses the direct final rulemaking procedure for a noncontroversial rule where the FAA believes that there will be no adverse public comment. This direct final rule advised that public that no adverse comments were anticipated, and that unless a written adverse comment, or a written notice of intent to submit such an adverse comment, were received within the comment period, the regulation would become effective on August 10, 2000. No adverse comments were received, and, thus, this action confirms that this direct final rule will be effective on that date.
                </P>
                <SIG>
                    <DATED>Issued in Fort Worth, TX, on May 16, 2000.</DATED>
                    <NAME>JoEllen Casilio,</NAME>
                    <TITLE>Assistant Manager, Air Traffic Division, Southwest Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13178  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Airspace Docket No. 2000-ASW-09]</DEPDOC>
                <SUBJECT>Revision of Class E Airspace; Fort Stockton, TX</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Direct final rule; confirmation of effective date.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice confirms the effective date of a direct final rule which revises Class E airspace at Fort Stockton, TX.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>The direct final rule published at 65 FR 14855 is effective 0901 UTC, August 10, 2000.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Donald J. Day, Airspace Branch, Air Traffic Division, Southwest Region, Federal Aviation Administration, Fort Worth, TX 76193-0520, telephone: 817-222-5593.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The FAA published this direct final rule with a request for comments in the 
                    <E T="04">Federal Register</E>
                     on March 20, 2000, (65 FR 14855). The FAA uses the direct final rulemaking procedure for a noncontroversial rule where the FAA believes that there will be no adverse public comment. This direct final rule advised the public that no adverse comments were anticipated, and that unless a written adverse comment, or a written notice of intent to submit such an adverse comment, were received within the comment period, the regulation would become effective on August 10, 2000. No adverse comments were received, and, thus, this action confirms that this direct final rule will be effective on that date.
                </P>
                <SIG>
                    <DATED>Issued in Fort Worth, TX, on May 16, 2000.</DATED>
                    <NAME>JoEllen Casilio,</NAME>
                    <TITLE>Assistant Manager, Air Traffic Division, Southwest Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13177 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Airspace Docket No. 00-ANM-01]</DEPDOC>
                <SUBJECT>Revision of Class E Airspace, Englewood, CO</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P> Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action amends the Englewood, CO, Class E airspace to accommodate the revision of a Standard Instrument Approach Procedure (SIAP) at the Centennial Airport, Englewood, CO.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>0901 UTC, August 10, 2000.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Brian Durham, ANM-520.7, Federal Aviation Administration, Docket No. 00-ANM-01, 1601 Lind Avenue SW, Renton, Washington 98055-4056: telephone number: (425) 227-2527.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">History</HD>
                <P>On January 24, 2000, the FAA proposed to amend Title 14 Code of Federal Regulations, part 71 (14 CFR part 71) by revising a Class E airspace extension at Englewood, CO, in order to accommodate a revised SIAP to the Centennial Airport, Englewood, CO. This amendment provides a small amount of additional Class E4 airspace at Englewood, CO, to meet current criteria standards associated with the SIAP. The FAA establishes Class E airspace where necessary to contain aircraft transitioning between the terminal and en route enivornments. The intended effect of this proposal is designed to provide for the safe and efficient use of the navigable airspace. This rule promotes safe flight operations under Instrument Flight Rules (IFR) at the Centennial Airport and between the terminal and en route transition stages.</P>
                <P>
                    The area will be depicted on aeronautical charts for pilot reference. The coordinates for this airspace docket are based on North American Datum 83. Class E airspace areas designated as an extension to a Class D airspace area, are published in paragraph 6004, of FAA 
                    <PRTPAGE P="33751"/>
                    Order 7400.9G dated September 1, 1999, and effective September 16,1999, which is incorporated by reference in 14 CFR 71.1. The Class E airspace designation listed in this document will be published subsequently in the Order.
                </P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This amendment to Title 14 Code of Federal Regulations, part 71 (14 CFR part 71) revise Class E airspace extension at Englewood, CO, in order to accommodate a revised SIAP to the Centennial Airport, Englewood, CO. This amendment provides a small amount of additional Class E4 airspace at Englewood, CO, to meet current criteria standards associated with the SIAP. The FAA establishes Class E airspace where necessary to contain aircraft transitioning between the terminal and en route environments. This rule is designed to provide for the safe and efficient use of the navigable airspace and to promote safe flight operations under Instrument Flight Rules (IFR) at the Centennial Airport and between the terminal and en route transition stages.</P>
                <P>The area will be depicted on aeronautical charts for pilot reference. The coordinates for this airspace docket are based on North American Datum 83. Class E airspace areas designated as an extension to a Class D airspace area, are published Paragraph 6004, of FAA Order 7400.9G dated September 1, 1999, and effective September 16, 1999, which is incorporated by reference in 14 CFR 71.1. The Class E airspace designation listed in this document will be published subsequently in the Order.</P>
                <P>The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore: (1) Is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a Regulatory Evaluation as the anticipated impact is so minimal. Since this is a routine matter that will only affect air traffic procedures and air navigation, it is certified that this rule, will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <REGTEXT TITLE="14" PART="71">
                    <HD SOURCE="HD1">Adoption of the Amendment</HD>
                    <AMDPAR>In consideration of the foregoing, the Federal Aviation Administration  amends 14 CFR part 71 as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, CLASS B, CLASS C, CLASS D, AND CLASS E AIRSPACE AREAS; AIRWAYS; ROUTES; AND REPORTING POINTS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="71">
                    <SECTION>
                        <SECTNO>§ 71.1 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR> 2. The incorporation by reference in 14 CFR 71.1 of the Federal Aviation Administration Order 7400.9G, Airspace Designations and Reporting Points, dated September 1, 1999, and effective September 16, 1999, is amended as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 6004 Class E airspace areas designated as an extension to a Class D airspace area.</HD>
                        <STARS/>
                        <HD SOURCE="HD1">ANM CO E5 Englewood, CO [Revised]</HD>
                        <FP SOURCE="FP-2">Centennial Airport, CO</FP>
                        <FP SOURCE="FP1-2">(Lat. 39°34′13″ N, long. 104°50′58″ W)</FP>
                        <P>That airspace extending upward from the surface within 3.2-mile radius each side of the 178° bearing from the Centennial Airport extending from the 4.4-mile radius to 14.1 miles south of the airport, and within 2.1 miles each side of the 109° bearing from the Centennial Airport extending from the 4.4-mile radius to 5.5 miles southeast of the airport. This Class E airspace area is effective during the specific dates and times established in advance by a Notice to Airmen. The effective dates and times will thereafter be continuously published in the Airport/Facility Directory.</P>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Seattle, Washington, DC on May 12, 2000.</DATED>
                    <NAME>Daniel A. Boyle,</NAME>
                    <TITLE>Acting Manager, Air Traffic Division, Northwest Mountain Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13174 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Parts 91, 93, 121 and 135</CFR>
                <DEPDOC>[Docket No. FAA-1999-5926; Amendment Nos. 91-263, 93-80, 121-274 and 135-75]</DEPDOC>
                <RIN>RIN 2120-AG74</RIN>
                <SUBJECT>Modification of the Dimensions of the Grand Canyon National Park Special Flight Rules Area and Flight Free Zones; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; correction. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document contains a correction to the final rule, published in the 
                        <E T="04">Federal Register</E>
                         on April 4, 2000 (65 FR 17736). That final rule amends special operating rules and airspace for those persons operating aircraft in the area designated as the Grand Canyon National Park Special Flight Rules Area (SFRA). That rule assists the National Park Service in fulfilling the statutory mandate of substantial restoration of the natural quiet and experience of the park.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This correction is effective December 1, 2000. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Kevin C. Willis, (202) 267-8741.</P>
                    <HD SOURCE="HD1">Correction of Publication</HD>
                    <P>
                        In final rule FR Doc. 00-7950, beginning on page 17736 in the 
                        <E T="04">Federal Register</E>
                         issue of April 4, 2000, make the following correction: 
                    </P>
                    <P>1. On page 17736, in column 1, in the heading section, beginning on line 4, correct “Amendment No. 93-80” to read “Amendment Nos. 91-263, 93-80, 121-274 and 135-75”.</P>
                    <SIG>
                        <DATED>Issued in Washington, DC on May 15, 2000.</DATED>
                        <NAME>Donald P. Byrne,</NAME>
                        <TITLE>Assistant Chief Counsel, Regulations Division.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 00-12819  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 129</CFR>
                <SUBJECT>Changes to the International Aviation Safety Assessment (IASA) Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Policy statement. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice describes recent policy changes to the FAA's 
                        <PRTPAGE P="33752"/>
                        International Aviation Safety Assessment (IASA) program, which involves assessing whether another country's oversight of its air carriers that operate, or seek to operate, into the United States complies with minimum international standards for aviation safety. The FAA is making these changes as it commences a new phase of the IASA program following the completion of initial determinations on the safety oversight exercised by virtually all countries whose air carriers operate, or have applied to operate, to the United States. This notice modifies the IASA policies previously announced by the FAA.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This policy modification is effective May 25, 2000. Comments on this policy may be directed to the address below.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send comments to Federal Aviation Administration, Office of Public Affairs, 800 Independence Avenue, SW, Washington, DC 20591.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Lynn Jensen, International Liaison Staff, AFS-50, Flight Standards Service, Federal Aviation Administration, 800 Independence Avenue, SW, Washington, DC 20591; (202) 267-3719.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>The policy announced at 57 FR 38342, August 24, 1992, described how the FAA would assess whether a foreign civil aviation authority (CAA) complied with the minimum international standards for aviation safety oversight established by the International Civil Aviation Organization (ICAO). In obtaining information relevant to its assessment, the FAA meets with the foreign CAA responsible for providing the safety oversight to its carriers, reviews pertinent records and meets with officials of the subject foreign air carriers. The FAA then analyzes the collected information to determine whether the CAA complies with ICAO standards regarding the oversight provided to the air carriers under its authority. This determination is part of the basis for FAA recommended courses of action to the Department of Transportation on the initiation, continuation, or expansion of air service to the United States by the carriers overseen by that CAA. The IASA program applies to all foreign countries with air carriers proposing or have existing air service to the United States under an economic authority issued by the Department</P>
                <P>The policy announced at 59 FR 46332, September 8, 1994, concerned the FAA's decision to publicly disclose the results of FAA assessments. In connection with the public disclosure policy, the FAA established three categories of ratings for countries to signify the status of a CAA's compliance with minimum international safety standards: Category I (Acceptable), Category II (Conditional), and Category III (Unacceptable). Category II or III apply to countries whose CAAs are found not to be providing safety oversight in compliance with the minimum international standards established by ICAO. The FAA normally places a country in Category II if one of its carriers provided air service to the United States at the time of the FAA assessment. The FAA places a country in Category III if none of its carriers provided air service to the United States at the time of the FAA assessment. Carriers from Category II countries are permitted to maintain, but not expand, current levels of service under heightened FAA surveillance. Carriers from Category III countries are not permitted to commence service to the United States.</P>
                <HD SOURCE="HD1">Program and Public Disclosure Changes</HD>
                <HD SOURCE="HD2">Sources of Information on Safety Oversight</HD>
                <P>The FAA has a continuing obligation to ensure that CAAs comply with minimum international standards for safety oversight. In collecting information to support its assessment findings, the FAA will continue to rely, when necessary, on meetings with CAA and airline officials and reviewing pertinent documents. The FAA also will make use of other sources of information on CAA compliance with minimum international standards for safety oversight. These sources may include other qualified entities (e.g., the European Joint Aviation Authorities or ICAO) considered reliable by the FAA.</P>
                <HD SOURCE="HD2">Categorization of Results of FAA Assessments</HD>
                <P>As in the past, assessment determinations will continue to be publicly disclosed. However, FAA will only use two categories in the future, i.e., Category 1 (in compliance with minimum international standards for aviation safety) and Category 2 (not in compliance with minimum international standards for aviation safety). This change is being made to eliminate any confusion that has resulted from having two different categories regarding non-compliance with ICAO standards. We believe that there has been a misimpression created that being in Category II reflects a higher degree of compliance with ICAO standards than being in Category III. To correct this misimpression and make clear that no inferences should be drawn about relative degrees of ICAO compliance, we are deleting Category III and redefining Category II as follows:</P>
                <P>
                    <E T="03">Category 2.</E>
                     The Federal Aviation Administration assessed this country's civil aviation authority and determined that it does not provide safety oversight of its air carrier operators in accordance with the minimum safety oversight standards established by the International Civil Aviation Organization (ICAO). This rating is applied if one or more of the following deficiencies are identified: (1) The country lacks laws or regulations necessary to support the certification and oversight of air carriers in accordance with minimum international standards; (2) the CAA lacks the technical expertise, resources, and organization to license or oversee air carrier operations; (3) the CAA does not have adequately trained and qualified technical personnel; (4) the CAA does not provide adequate inspector guidance to ensure enforcement of, and compliance with, minimum international standards, and (5) the CAA has insufficient documentation and records of certification and inadequate continuing oversight and surveillance of air carrier operations. This category consists of two groups of countries.
                </P>
                <P>One group are countries that have air carriers with existing operations to the United States at the time of the assessment. While in Category 2 status, carriers from these countries will be permitted to continue operations at current levels under heightened FAA surveillance. Expansion or changes in services to the United States by such carriers are not permitted while in category 2, although new services will be permitted if operated using aircraft wet-leased from a duly authorized and properly supervised U.S. carrier or a foreign air carrier from a category 1 country that is authorized to serve the United States using its own aircraft.</P>
                <P>
                    The second group are countries that do not have air carriers with existing operations to the United States at the time of the assessment. Carriers from these countries will not be permitted to commerce service to the United States while in Category 2 status, although they may conduct services if operated using aircraft wet-leased from a duly authorized and properly supervised U.S. carrier or a foreign air carrier from a Category 1 country that is authorized to serve the United States with its own aircraft.
                    <PRTPAGE P="33753"/>
                </P>
                <P>No other difference is made between these two groups of countries while in a category 2 status.</P>
                <HD SOURCE="HD2">Transition to New IASA Categorization System</HD>
                <P>Countries in the former Category I will initially be placed in the new Category 1 (in compliance with ICAO Standards). Countries in the former Categories II and III will initially be placed in the new Category 2 (not in compliance with ICAO standards). For those countries not serving the U.S. at the time of the assessment, an asterisk “*” will be added to their Category 2 determination.</P>
                <P>The FAA will review the category determinations of all countries included in the IASA categorization scheme at least once every two years, or when new information becomes available which calls into question the country's ability to continue complying with minimum standards for aviation safety. The purpose of such reviews is to determine if a country's CAA continues to comply with minimum international standard for aviation safety (Category I) or is making sustainable progress toward compliance (Category 2). After each such review, the FAA will update the appropriate public disclosure.</P>
                <P>The FAA will continue to work with countries to improve safety oversight capabilities in cases where the assessment process has revealed deficiencies. When FAA determines that sustainable progress is not being made, or is not possible under the prevailing circumstances in the country, it may advise the Office of the Secretary that the subject country has not made significant progress in correcting its safety oversight deficiencies and recommend a course of action to review the status of all authorities issued to carriers of that country.</P>
                <P>Current IASA category determinations for countries included in the IASA categorization system are available on the FAA web-site at http://www.faa.gov/avr/isa.htm</P>
                <SIG>
                    <DATED>Issued in Washington, DC on May 15, 2000.</DATED>
                    <NAME>Thomas E. McSweeny,</NAME>
                    <TITLE>Associate Administrator for Regulation and Certification.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13179  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M</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 8884] </DEPDOC>
                <RIN>RIN 1545-AV88 </RIN>
                <SUBJECT>Consolidated Returns—Limitations on the Use of Certain Credits </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final regulations. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document contains final regulations regarding certain credits of corporations that become members of a consolidated group. The regulations provide rules for computing the limitation with respect to certain credits earned in a separate return limitation year (SRLY) and the carryover and carryback of those credits to consolidated and separate return years. The regulations also eliminate the application of the SRLY rules in certain circumstances in which the rules of section 383 also apply. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         These regulations are effective May 25, 2000. 
                    </P>
                    <P>
                        <E T="03">Applicability Dates:</E>
                         For dates of applicability, see the “Dates of Applicability” portion of this preamble. 
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Marie C. Milnes-Vasquez, (202) 622-7770 (not a toll-free number). </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background and Explanation of Provisions </HD>
                <HD SOURCE="HD2">A. In General </HD>
                <P>
                    On January 12, 1998, the IRS and Treasury published in the 
                    <E T="04">Federal Register</E>
                     a Treasury decision (TD 8751, 63 FR 1740) containing temporary regulations concerning the use of certain tax attributes by a consolidated group. In part, these regulations provided rules governing the absorption of general business credits and minimum tax credits carried from separate return limitation years (SRLYs), and eliminated SRLY restrictions with respect to recapture of overall foreign losses (OFLs) and on the use of foreign tax credits of corporations joining a group. Further, this Treasury decision contained a final regulation eliminating the limitation on credit carryovers following a consolidated return change of ownership (CRCO). 
                </P>
                <P>
                    A notice of proposed rulemaking cross-referencing the temporary regulations was published in the 
                    <E T="04">Federal Register</E>
                     on the same day (63 FR 1803). On March 16, 1998, the IRS and Treasury published temporary amendments to those consolidated return regulations (TD 8766, 63 FR 12641) and the corresponding notice of proposed rulemaking (63 FR 12717) modifying the general date of applicability contained in the January 12, 1998 temporary regulations. Per the amendment, the January 12, 1998 temporary regulations, as amended, are generally applicable for consolidated return years for which the due date of the return is after March 13, 1998. The amendments provided further guidance with respect to consolidated return years beginning on or after January 1, 1997, for which the income tax return is due on or before March 13, 1998. 
                </P>
                <P>On August 11, 1999, the IRS and Treasury issued final regulations relating to the recapture of OFLs (including elimination of any SRLY limitation on such recapture). (TD 8833, 64 FR 43613). </P>
                <P>
                    This Treasury decision adopts without substantive change the portions of the temporary regulations that were issued in 1998, relating to general business credits and minimum tax credits, with the addition of the “overlap rule”, discussed in 
                    <E T="03">Extension of 1999 Principles</E>
                     of this preamble. This Treasury decision also makes final the rules eliminating SRLY restrictions on the use of foreign tax credits, and the rules repealing the consolidated return change of ownership provisions pertaining to those credits. 
                </P>
                <HD SOURCE="HD2">B. Extension of 1999 Principles </HD>
                <P>
                    On July 2, 1999, the IRS and Treasury published in the 
                    <E T="04">Federal Register</E>
                     a Treasury decision (TD 8823, 64 FR 36092) containing final regulations providing rules governing the absorption of certain tax attribute carryovers and carrybacks from separate return limitation years (SRLYs). These tax attributes included net operating losses and net capital losses. The rules also governed the absorption of recognized built-in losses. These regulations, in part, eliminated the application of the SRLY rules in certain circumstances in which the rules of section 382 also apply (overlap rule). 
                </P>
                <P>
                    The IRS and Treasury believe that it is appropriate to apply a single set of SRLY principles to all attributes that are subject to SRLY limitations. Unnecessary complexity would result from applying different principles to different attributes. Accordingly, this document extends the principles of the overlap rule of the 1999 final regulations to the general business credit and the minimum tax credit. These final regulations adopt the mechanism of subgrouping and the 
                    <PRTPAGE P="33754"/>
                    overlap rule set forth in § 1.1502-21 (including the requirements of coextensive subgroups and contemporaneity). 
                </P>
                <HD SOURCE="HD2">C. Dates of Applicability </HD>
                <P>The final regulations generally are applicable to consolidated return years for which the due date of the income tax return (without extensions) is after March 13, 1998. However, there are some special effective dates. The rules contained in these final regulations (except the overlap rule) may be applied optionally to years beginning on or after January 1, 1997. Application of the overlap principles of § 1.1502-21(g) is generally effective for consolidated return years for which the return (without extensions) is due after May 25, 2000. </P>
                <HD SOURCE="HD1">Special Analyses </HD>
                <P>It has been determined that this Treasury decision is not a significant regulatory action as defined in Executive Order 12866. Therefore, a regulatory assessment is not required. It is hereby certified that these regulations do not have a significant economic impact on a substantial number of small entities. This certification is based on the fact that these regulations principally affect persons filing consolidated federal income tax returns that have carryover or carryback of credits from separate return limitation years. Available data indicates that many consolidated return filers are large companies (not small businesses). In addition, the data indicates that an insubstantial number of consolidated return filers that are smaller companies have credit carryovers or carrybacks, and thus even fewer of these filers have credit carryovers or carrybacks that are subject to the separate return limitation year rules. Therefore, a Regulatory Flexibility Analysis under the Regulatory Flexibility Act (5 U.S.C. chapter 6) is not required. Pursuant to section 7805(f) of the Internal Revenue Code, the notice of proposed rulemaking accompanying these regulations was sent to the Small Business Administration for comment on their impact on small businesses. </P>
                <HD SOURCE="HD1">Drafting Information </HD>
                <P>The principal author of these regulations is Marie C. Milnes-Vasquez of the Office of Assistant Chief Counsel (Corporate). Other personnel from the IRS and Treasury 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>
                <REGTEXT TITLE="26" PART="1">
                    <HD SOURCE="HD1">Adoption of Amendments to the Regulations </HD>
                    <AMDPAR>Accordingly, 26 CFR part 1 is amended as follows: </AMDPAR>
                    <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 removing the entries for sections 1.1502-3T and 1.1502-55T and adding entries 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.1502-3 also issued under 26 U.S.C. 1502. </P>
                        <P>Section 1.1502-4 also issued under 26 U.S.C. 1502. * * *. </P>
                        <P>Section 1.1502-55 also issued under 26 U.S.C. 1502. * * * </P>
                    </EXTRACT>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 2.</E>
                         Section 1.1502-3 is amended as follows: 
                    </AMDPAR>
                    <AMDPAR>1. The section heading is revised. </AMDPAR>
                    <AMDPAR>2. Paragraph (b)(3) is added. </AMDPAR>
                    <AMDPAR>3. Paragraphs (c), (d), and (e)(3) are revised. </AMDPAR>
                    <AMDPAR>The addition and revisions read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.1502-3 </SECTNO>
                        <SUBJECT>Consolidated tax credits. </SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>
                            (3) 
                            <E T="03">Example.</E>
                             The provisions of paragraphs (a) and (b) of this section may be illustrated by the following example: 
                        </P>
                        <EXAMPLE>
                            <HD SOURCE="HED">Example.</HD>
                            <P>(i) Corporation P is incorporated on January 1, 1966. On that same day P incorporates corporation S, a wholly owned subsidiary. P and S file consolidated returns for calendar years 1966 and 1967. P's and S's credit earned, the consolidated credit earned, and the consolidated limitation based on amount of tax for 1966 and 1967 are as follows: </P>
                            <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s50,15,15,15">
                                <TTITLE>  </TTITLE>
                                <BOXHD>
                                    <CHED H="1">  </CHED>
                                    <CHED H="1">Credit earned </CHED>
                                    <CHED H="1">Consolidated credit earned </CHED>
                                    <CHED H="1">Consolidated limitation based on amount of tax </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="22">1966: </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="02">P </ENT>
                                    <ENT>$60,000 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="02">S </ENT>
                                    <ENT>30,000 </ENT>
                                    <ENT>$90,000 </ENT>
                                    <ENT>$100,000 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22">1967: </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="02">P </ENT>
                                    <ENT>40,000 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="02">S </ENT>
                                    <ENT>25,000 </ENT>
                                    <ENT>65,000 </ENT>
                                    <ENT>50,000 </ENT>
                                </ROW>
                            </GPOTABLE>
                            <P>(ii) P's and S's credit earned for 1966 are aggregated, and the group's consolidated credit earned, $90,000, is allowable in full to the group as a credit under section 38 for 1966 since such amount is less than the consolidated limitation based on amount of tax for 1966, $100,000. </P>
                            <P>(iii) Since the consolidated limitation based on amount of tax for 1967 is $50,000, only $50,000 of the $65,000 consolidated credit earned for such year is allowable to the group under section 38 as a credit for 1967. The consolidated unused credit for 1967 of $15,000 ($65,000 less $50,000) is a consolidated investment credit carryback and carryover to the years prescribed in section 46(b). In this case the consolidated unused credit is a consolidated investment credit carryback to 1966 (since P and S were not in existence in 1964 and 1965) and a consolidated investment credit carryover to 1968 and subsequent years. The portion of the consolidated unused credit for 1967 which is allowable as a credit for 1966 is $10,000. This amount shall be added to the amount allowable as a credit to the group for 1966. The balance of the consolidated unused credit for 1967 to be carried to 1968 is $5,000. These amounts are computed as follows: </P>
                        </EXAMPLE>
                        <PRTPAGE P="33755"/>
                        <GPOTABLE COLS="4" OPTS="L2,tp0,p1,8/9,i1" CDEF="s50,10,10,10">
                            <TTITLE>  </TTITLE>
                            <BOXHD>
                                <CHED H="1">  </CHED>
                                <CHED H="1">  </CHED>
                                <CHED H="1">  </CHED>
                                <CHED H="1">  </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">Consolidated carryback to 1966 </ENT>
                                <ENT>  </ENT>
                                <ENT>  </ENT>
                                <ENT>$15,000 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="02">1966 consolidated limitation based on tax </ENT>
                                <ENT>  </ENT>
                                <ENT>$100,000 </ENT>
                                <ENT/>
                            </ROW>
                            <ROW>
                                <ENT I="01">Less: Consolidated credit earned for 1966 </ENT>
                                <ENT>$90,000 </ENT>
                            </ROW>
                            <ROW RUL="n,s">
                                <ENT I="02">Consolidated unused credits attributable to years preceding 1967 </ENT>
                                <ENT>0 </ENT>
                                <ENT>90,000 </ENT>
                                <ENT/>
                            </ROW>
                            <ROW RUL="n,s">
                                <ENT I="01">Limit on amount of 1967 consolidated unused credit which may be added as a credit for 1966 </ENT>
                                <ENT>  </ENT>
                                <ENT>  </ENT>
                                <ENT>10,000 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Balance of 1967 consolidated unused credit to be carried to 1968 </ENT>
                                <ENT>  </ENT>
                                <ENT/>
                                <ENT>5,000 </ENT>
                            </ROW>
                        </GPOTABLE>
                        <P>
                            (c) 
                            <E T="03">Limitation on investment credit carryovers and carrybacks from separate return limitation years applicable for consolidated return years for which the due date of the return is on or before March 13, 1998—(1) General rule.</E>
                             In the case of an unused credit of a member of the group arising in a separate return limitation year (as defined in § 1.1502-1(f)) of such member (and in a separate return limitation year of any predecessor of such member), the amount which may be included under paragraph (b) of this section (computed without regard to the limitation contained in paragraph (e) of this section) shall not exceed the amount determined under paragraph (c)(2) of this section. 
                        </P>
                        <P>
                            (2) 
                            <E T="03">Computation of limitation.</E>
                             The amount referred to in paragraph (c)(1) of this section with respect to a member of the group is the excess, if any, of— 
                        </P>
                        <P>(i) The limitation based on amount of tax of the group, minus such limitation recomputed by excluding the items of income, deduction, and foreign tax credit of such member; over </P>
                        <P>(ii) The sum of the investment credit earned by such member for such consolidated return year, and the unused credits attributable to such member which may be carried to such consolidated return year arising in unused credit years ending prior to the particular separate return limitation year. </P>
                        <P>
                            (3) 
                            <E T="03">Special effective date.</E>
                             This paragraph (c) applies to consolidated return years for which the due date of the income tax return (without extensions) is on or before March 13, 1998. See paragraph (d) of this section for the rule that limits the group's use of a section 38 credit carryover or carryback from a SRLY for a consolidated return year for which the due date of the income tax return (without extensions) is after March 13, 1998. See also paragraph (d)(4) of this section for an optional effective date rule (generally making the rules of this paragraph (c) inapplicable to a consolidated return year beginning after December 31, 1996, if the due date of the income tax return (without extensions) for such year is on or before March 13, 1998). 
                        </P>
                        <P>
                            (4) 
                            <E T="03">Examples.</E>
                             The provisions of this paragraph (c) may be illustrated by the following examples: 
                        </P>
                        <EXAMPLE>
                            <HD SOURCE="HED">
                                <E T="03">Example 1.</E>
                            </HD>
                            <P>(i) Assume the same facts as in the example contained in paragraph (b)(3) of this section, except that all the stock of corporation T, also a calendar year taxpayer, is acquired by P on January 1, 1968, and that P, S, and T file a consolidated return for 1968. In 1966, T had an unused credit of $10,000 which has not been absorbed and is available as an investment credit carryover to 1968. Such carryover is from a separate return limitation year. P's and S's credit earned for 1968 is $10,000 each, and T's credit earned is $8,000; the consolidated credit earned is therefore $28,000. The group's consolidated limitation based on amount of tax for 1968 is $50,000. Such limitation recomputed by excluding the items of income, deduction, and foreign tax credit of T is $30,000. Thus, the amount determined under paragraph (c)(2)(i) of this section is $20,000 ($50,000 minus $30,000). Accordingly, the limitation on the carryover of T's unused credit is $12,000, the excess of $20,000 over $8,000 (the sum of T's credit earned for the taxable year and any carryovers from prior unused credit years (none in this case)). Therefore T's $10,000 unused credit from 1966 may be carried over to the consolidated return year without limitation. </P>
                            <P>(ii) The group's consolidated credit earned for 1968, $28,000, is allowable in full as a credit under section 38 since such amount is less than the consolidated limitation based on amount of tax, $50,000. </P>
                            <P>(iii) The group's consolidated investment credit carryover to 1968 is $15,000, consisting of the consolidated unused credits of the group ($5,000) plus T's separate return year unused credit ($10,000). The entire $15,000 consolidated carryover shall be added to the amount allowable to the group as a credit under section 38 for 1968, since such amount is less than $22,000 (the excess of the consolidated limitation based on tax, $50,000, over the sum of the consolidated credit earned for 1968, $28,000, and unused credits arising in prior unused credit years, zero). </P>
                        </EXAMPLE>
                        <EXAMPLE>
                            <HD SOURCE="HED">Example 2.</HD>
                            <P>
                                Assume the same facts as in 
                                <E T="03">Example 1</E>
                                , except that the amount determined under paragraph (c)(2)(i) of this section is $12,000. Therefore, the limitation on the carryover of T's unused credit is $4,000. Accordingly, the consolidated investment credit carryover is only $9,000 since the amount of T's separate return year unused credit which may be added to the group's $ 5,000 consolidated unused credit is $4,000. These amounts are computed as follows:
                            </P>
                            <GPOTABLE COLS="4" OPTS="L2,tp0,p1,8/9,i1" CDEF="s50,10,10,10">
                                <TTITLE>  </TTITLE>
                                <BOXHD>
                                    <CHED H="1">  </CHED>
                                    <CHED H="1">  </CHED>
                                    <CHED H="1">  </CHED>
                                    <CHED H="1">  </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">T's carryover to 1968</ENT>
                                    <ENT/>
                                    <ENT/>
                                    <ENT>$10,000 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="02">Consolidated limitation based on amount of tax minus recomputed limitation </ENT>
                                    <ENT/>
                                    <ENT>$12,000</ENT>
                                    <ENT/>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Less: T's credit earned for 1968</ENT>
                                    <ENT>$8,000</ENT>
                                    <ENT>  </ENT>
                                    <ENT/>
                                </ROW>
                                <ROW RUL="n,s">
                                    <ENT I="02">Unused credits attributable to T arising in unused credit years preceding 1966</ENT>
                                    <ENT>0</ENT>
                                    <ENT>$8,000</ENT>
                                    <ENT/>
                                </ROW>
                                <ROW RUL="n,s">
                                    <ENT I="01">Limit on amount of 1966 unused credit of T which may be added to consolidated investment credit carryover</ENT>
                                    <ENT/>
                                    <ENT/>
                                    <ENT>4,000 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Balance of 1966 unused credit of T to be carried to 1969 (subject to the limitation contained in paragraph (c) of this section)</ENT>
                                    <ENT/>
                                    <ENT/>
                                    <ENT>6,000 </ENT>
                                </ROW>
                            </GPOTABLE>
                        </EXAMPLE>
                        <P>
                            (d) 
                            <E T="03">Limitation on tax credit carryovers and carrybacks from separate return limitation years applicable for consolidated return years for which the due date of the return is after March 13, 1998</E>
                            —(1) 
                            <E T="03">General rule.</E>
                             The aggregate of a member's unused section 38 credits arising in SRLYs that are included in the consolidated section 38 credits for all consolidated return years of the group may not exceed— 
                        </P>
                        <P>(i) The aggregate for all consolidated return years of the member's contributions to the consolidated section 38(c) limitation for each consolidated return year; reduced by </P>
                        <P>
                            (ii) The aggregate of the member's section 38 credits arising and absorbed in all consolidated return years (whether or not absorbed by the member). 
                            <PRTPAGE P="33756"/>
                        </P>
                        <P>
                            (2) 
                            <E T="03">Computational rules</E>
                            —(i) 
                            <E T="03">Member's contribution to the consolidated section 38(c) limitation.</E>
                             If the consolidated section 38(c) limitation for a consolidated return year is determined by reference to the consolidated tentative minimum tax (see section 38(c)(1)(A)), then a member's contribution to the consolidated section 38(c) limitation for such year equals the member's share of the consolidated net income tax minus the member's share of the consolidated tentative minimum tax. If the consolidated section 38(c) limitation for a consolidated return year is determined by reference to the consolidated net regular tax liability (see section 38(c)(1)(B)), then a member's contribution to the consolidated section 38(c) limitation for such year equals the member's share of the consolidated net income tax minus 25 percent of the quantity which is equal to so much of the member's share of the consolidated net regular tax liability less its portion of the $25,000 amount specified in section 38(c)(1)(B). The group computes the member's shares by applying to the respective consolidated amounts the principles of section 1552 and the percentage method under § 1.1502-33(d)(3), assuming a 100% allocation of any decreased tax liability. The group must make proper adjustments so that taxes and credits not taken into account in computing the limitation under section 38(c) are not taken into account in computing the member's share of the consolidated net income tax, etc. (See, for example, the taxes described in section 26(b) that are disregarded in computing regular tax liability.) Also, the group may apportion all or a part of the $25,000 amount (or lesser amount if reduced by section 38(c)(3)) for any year to one or more members. 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Years included in computation.</E>
                             For purposes of computing the limitation under this paragraph (d), the consolidated return years of the group include only those years, including the year to which a credit is carried, that the member has been continuously included in the group's consolidated return, but exclude— 
                        </P>
                        <P>(A) For carryovers, any years ending after the year to which the credit is carried; and </P>
                        <P>(B) For carrybacks, any years ending after the year in which the credit arose. </P>
                        <P>
                            (iii) 
                            <E T="03">Subgroups and successors.</E>
                             The SRLY subgroup principles under § 1.1502-21(c)(2) apply for purposes of this paragraph (d). The predecessor and successor principles under § 1.1502-21(f) also apply for purposes of this paragraph (d). 
                        </P>
                        <P>
                            (iv) 
                            <E T="03">Overlap with section 383.</E>
                             The principles under § 1.1502-21(g) apply for purposes of this paragraph (d). For example, an overlap of paragraph (d) of this section and the application of section 383 with respect to a credit carryover occurs if a corporation becomes a member of a consolidated group (the SRLY event) within six months of the change date of an ownership change giving rise to a section 383 credit limitation with respect to that carryover (the section 383 event), with the result that the limitation of this paragraph (d) does not apply. See §§ 1.1502-21(g)(2)(ii)(A) and 1.383-1; see also § 1.1502-21(g)(4) (subgroup rules). 
                        </P>
                        <P>
                            (3) 
                            <E T="03">Effective date</E>
                            —(i) 
                            <E T="03">In general.</E>
                             This paragraph (d) generally applies to consolidated return years for which the due date of the income tax return (without extensions) is after March 13, 1998. 
                        </P>
                        <P>
                            (A) 
                            <E T="03">Contribution years.</E>
                             Except as provided in paragraph (d)(4)(ii) of this section, a group does not take into account a consolidated taxable year for which the due date of the income tax return (without extensions) is on or before March 13, 1998, in determining a member's (or subgroup's) contributions to the consolidated section 38(c) limitation under this paragraph (d). 
                        </P>
                        <P>
                            (B) 
                            <E T="03">Special subgroup rule.</E>
                             In the event that the principles of § 1.1502-21(g)(1) do not apply to a particular credit carryover in the current group, then solely for purposes of applying paragraph (d) of this section to determine the limitation with respect to that carryover and with respect to which the SRLY register (the aggregate of the member's or subgroup's contribution to consolidated section 38(c) limitation reduced by the aggregate of the member's or subgroup's section 38 credits arising and absorbed in all consolidated return years) began in a taxable year for which the due date of the return is on or before May 25, 2000, the principles of § 1.1502-21(c)(2) shall be applied without regard to the phrase “or for a carryover that was subject to the overlap rule described in paragraph (g) of this section or § 1.1502-15(g) with respect to another group (the former group).” 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Overlap rule.</E>
                             Paragraph (d)(2)(iv) of this section (relating to overlap with section 383) applies to taxable years for which the due date (without extensions) of the consolidated return is after May 25, 2000. For purposes of paragraph (d)(2)(iv) of this section, only an ownership change to which section 383, as amended by the Tax Reform Act of 1986 (100 Stat. 2085), applies and which results in a section 383 credit limitation shall constitute a section 383 event. 
                        </P>
                        <P>
                            (4) 
                            <E T="03">Optional effective date of January 1, 1997.</E>
                             (i) For consolidated taxable years beginning on or after January 1, 1997, for which the due date of the income tax return (without extensions) is on or before March 13, 1998, in lieu of paragraphs (c) and (e)(3) of this section (relating to the general business credit), § 1.1502-4(f)(3) and (g)(3) (relating to the foreign tax credit), the next to last sentence of § 1.1502-9A(a)(2), § 1.1502-9A(b)(1)(v) (relating to overall foreign losses), and § 1.1502-55(h)(4)(iii) (relating to the alternative minimum tax credit), a consolidated group may apply the corresponding provisions as they appear in 1998-1 C.B. 655 through 661 (see § 601.601(d)(2) of this chapter) (treating references in such corresponding provisions to §§ 1.1502-9(b)(1)(ii), (iii), and (iv) as references to §§ 1.1502-9(b)(1)(ii), (iii), and (iv)). Also, in the case of a consolidated return change of ownership that occurs on or after January 1, 1997, in a taxable year for which the due date of the income tax return (without extensions) is on or before March 13, 1998, a consolidated group may choose not to apply paragraph (e) of this section and § 1.1502-4(g) to taxable years ending after December 31, 1996. A consolidated group making the choices described in the two preceding sentences generally must apply all such corresponding provisions (including not applying paragraph (e) of this section and § 1.1502-4(g)) for all relevant years. However, a consolidated group making the election provided in § 1.1502-9A(b)(1)(vi) (electing not to apply § 1.1502-9A(b)(1)(v) to years beginning before January 1, 1998) may nevertheless choose to apply all such corresponding provisions referred to in this paragraph (d)(4)(i) other than the provision corresponding to § 1.1502-9A(b)(1)(v) for all relevant years. 
                        </P>
                        <P>(ii) If a consolidated group chooses to apply the corresponding provisions referred to in paragraph (d)(4)(i) of this section, the consolidated group shall not take into account a consolidated taxable year beginning before January 1, 1997, in determining a member's (or subgroup's) contributions to the consolidated section 38(c) limitation under this paragraph (d). </P>
                        <P>
                            (5) 
                            <E T="03">Example.</E>
                             The following example illustrates the provisions of this paragraph (d): 
                        </P>
                        <EXAMPLE>
                            <HD SOURCE="HED">
                                <E T="03">Example.</E>
                            </HD>
                            <P>
                                (i) Individual A owns all of the stock of P and T. P is the common parent of the P group. P acquires all the stock of T at the beginning of Year 2. T carries over an 
                                <PRTPAGE P="33757"/>
                                unused section 38 general business credit from Year 1 of $100,000. The table in paragraph (i) of this Example shows the group's net consolidated income tax, consolidated tentative minimum tax, and consolidated net regular tax liabilities, and T's share of such taxes computed under the principles of section 1552 and the percentage method under § 1.1502-33(d)(3), assuming a 100% allocation of any decreased tax liability, for Year 2. (The effects of the lower section 11 brackets are ignored, there are no other tax credits affecting a group amount or member's share, and $1,000s are omitted.)
                            </P>
                        </EXAMPLE>
                        <BILCOD>BILLING CODE 4830-01-P </BILCOD>
                        <GPH SPAN="3" DEEP="419">
                            <GID>ER25MY00.002</GID>
                        </GPH>
                        <BILCOD>BILLING CODE 4830-01-C </BILCOD>
                        <EXTRACT>
                            <P>(ii) T's Year 1 is a SRLY with respect to the P group. See § 1.1502-1(f)(2)(ii). T did not undergo an ownership change giving rise to a section 383 credit limitation within 6 months of joining the P group. Thus, T's $100,000 general business credit arising in Year 1 is subject to a SRLY limitation in the P group. The amount of T's unused section 38 credits from Year 1 that are included in the consolidated section 38 credits for Year 2 may not exceed T's contribution to the consolidated section 38(c) limitation. For Year 2, the group determines the consolidated section 38(c) limitation by reference to consolidated tentative minimum tax for Year 2. Therefore, T's contribution to the consolidated section 38(c) limitation for Year 2 equals its share of consolidated net income tax minus its share of consolidated tentative minimum tax. T's contribution is $280,000 minus $160,000, or $120,000. However, because the group has a consolidated section 38 limitation of zero, it may not include any of T's unused section 38 credits in the consolidated section 38 credits for Year 2. </P>
                            <P>(iii) The following table shows similar information for the group for Year 3: </P>
                            <BILCOD>BILLING CODE 4830-01-P </BILCOD>
                            <GPH SPAN="3" DEEP="420">
                                <PRTPAGE P="33758"/>
                                <GID>ER25MY00.003</GID>
                            </GPH>
                            <BILCOD>BILLING CODE 4830-01-C</BILCOD>
                            <P>(iv) The amount of T's unused section 38 credits from Year 1 that are included in the consolidated section 38 credits for Year 3 may not exceed T's aggregate contribution to the consolidated section 38(c) limitation for Years 2 and 3. For Year 3, the group determines the consolidated section 38(c) limitation by reference to the consolidated tentative minimum tax for Year 3. Therefore, T's contribution to the consolidated section 38(c) limitation for Year 3 equals its share of consolidated net income tax minus its share of consolidated tentative minimum tax. Applying the principles of section 1552 and § 1.1502-33(d) (taking into account, for example, that T's positive earnings and profits adjustment under § 1.1502-33(d) reflects its losses actually absorbed by the group), T's contribution is $(105,000) minus $(40,000), or $(65,000). T's aggregate contributions to the consolidated section 38(c) limitation for Years 2 and 3 is $120,000 + $(65,000), or $55,000. The group may include $55,000 of T's Year 1 unused section 38 credits in its consolidated section 38 tax credit in Year 3.</P>
                        </EXTRACT>
                        <P>(e) * * * </P>
                        <P>
                            (3) 
                            <E T="03">Special effective date</E>
                            . This paragraph (e) applies only to a consolidated return change of ownership that occurred during a consolidated return year for which the due date of the income tax return (without extensions) is on or before March 13, 1998. See paragraph (d)(4) of this section for an optional effective date rule (generally making the rules of this paragraph (e) also inapplicable if the consolidated return change of ownership occurred on or after January 1, 1997, and during a consolidated return year for which the due date of the income tax return (without extensions) is on or before March 13, 1998). 
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <SECTION>
                        <SECTNO>§ 1.1502-3T </SECTNO>
                        <SUBJECT>[Removed] </SUBJECT>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 3.</E>
                         Section 1.1502-3T is removed. 
                    </AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 4.</E>
                         Section 1.1502-4 is amended by revising paragraphs (f)(3) and (g)(3) to read as follows: 
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.1502-4 </SECTNO>
                        <SUBJECT>Consolidated foreign tax credit. </SUBJECT>
                        <STARS/>
                        <P>(f)* * * </P>
                        <P>
                            (3) 
                            <E T="03">Limitation on unused foreign tax credit carryover or carryback from separate return limitation years.</E>
                             Paragraphs (f)(1) and (2) of this section do not apply for consolidated return years for which the due date of the income tax return (without extensions) is after March 13, 1998. For consolidated return years for which the due date of the income tax return (without extensions) is after March 13, 1998, a group shall include an unused foreign tax of a member arising in a SRLY without regard to the contribution of the member to consolidated tax liability for the consolidated return year. See also § 1.1502-3(d)(4) for an optional 
                            <PRTPAGE P="33759"/>
                            effective date rule (generally making the rules of paragraphs (f)(1) and (2) of this section also inapplicable to a consolidated return year beginning on or after January 1, 1997, if the due date of the income tax return (without extensions) for such year is on or before March 13, 1998). 
                        </P>
                        <P>(g)* * * </P>
                        <P>
                            (3) 
                            <E T="03">Special effective date for CRCO limitation.</E>
                             Paragraphs (g)(1) and (2) of this section apply only to a consolidated return change of ownership that occurred during a consolidated return year for which the due date of the income tax return (without extensions) is on or before March 13, 1998. See also § 1.1502-3(d)(4) for an optional effective date rule (generally making the rules of paragraph (g)(1) and (2) of this section also inapplicable if the consolidated return change of ownership occurred on or after January 1, 1997, and during a consolidated return year for which the due date of the income tax return (without extensions) is on or before March 13, 1998). 
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <SECTION>
                        <SECTNO>§ 1.1502-4T </SECTNO>
                        <SUBJECT>[Removed] </SUBJECT>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 5.</E>
                         Section 1.1502-4T is removed. 
                    </AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 6.</E>
                         Section 1.1502-21 is amended by revising paragraph (c)(2)(ix) to read as follows: 
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.1502-21 </SECTNO>
                        <SUBJECT>Net operating losses. </SUBJECT>
                        <STARS/>
                        <P>(c) * * * </P>
                        <P>(2) * * * </P>
                        <P>
                            (ix) 
                            <E T="03">Application to other than loss carryovers.</E>
                             Paragraph (g) of this section and the phrase “or for a carryover that was subject to the overlap rule described in paragraph (g) of this section or § 1.1502-15(g) with respect to another group (the former group)” in this paragraph (c)(2) apply only to carryovers of net operating losses, net capital losses, and for taxable years for which the due date (without extensions) of the consolidated return is after May 25, 2000, to carryovers of credits described in section 383(a)(2). Accordingly, as the context may require, if another regulation references this section and such other regulation does not concern a carryover of net operating losses, net capital losses, or for taxable years for which the due date (without extensions) of the consolidated return is after May 25, 2000, carryovers of credits described in section 383(a)(2), then such reference does not include a reference to such paragraph or phrase. 
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 7.</E>
                         Section 1.1502-55 is added to read as follows: 
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.1502-55 </SECTNO>
                        <SUBJECT>Computation of alternative minimum tax of consolidated groups. </SUBJECT>
                        <P>(a) through (h)(3) [Reserved]. </P>
                        <P>
                            (h)(4) 
                            <E T="03">Separate return year minimum tax credit.</E>
                        </P>
                        <P>(i) and (ii) [Reserved]. </P>
                        <P>
                            (iii)(A) 
                            <E T="03">Limitation on portion of separate return year minimum tax credit arising in separate return limitation years.</E>
                             The aggregate of a member's minimum tax credits arising in SRLYs that are included in the consolidated minimum tax credits for all consolidated return years of the group may not exceed— 
                        </P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) The aggregate for all consolidated return years of the member's contributions to the consolidated section 53(c) limitation for each consolidated return year; reduced by
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) The aggregate of the member's minimum tax credits arising and absorbed in all consolidated return years (whether or not absorbed by the member). 
                        </P>
                        <P>
                            (B) 
                            <E T="03">Computational rules</E>
                            —(
                            <E T="03">1</E>
                            ) 
                            <E T="03">Member's contribution to the consolidated section 53(c) limitation.</E>
                             Except as provided in the special rule of paragraph (h)(4)(iii)(B)(
                            <E T="03">2</E>
                            ) of this section, a member's contribution to the consolidated section 53(c) limitation for a consolidated return year equals the member's share of the consolidated net regular tax liability minus its share of consolidated tentative minimum tax. The group computes the member's shares by applying to the respective consolidated amounts the principles of section 1552 and the percentage method under § 1.1502-33(d)(3), assuming a 100% allocation of any decreased tax liability. The group makes proper adjustments so that taxes and credits not taken into account in computing the limitation under section 53(c) are not taken into account in computing the member's share of the consolidated net regular tax, etc. (See, for example, the taxes described in section 26(b) that are disregarded in computing regular tax liability.) 
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) 
                            <E T="03">Adjustment for year in which alternative minimum tax is paid.</E>
                             For a consolidated return year for which consolidated tentative minimum tax is greater than consolidated regular tax liability, the group reduces the member's share of the consolidated tentative minimum tax by the member's share of the consolidated alternative minimum tax for the year. The group determines the member's share of consolidated alternative minimum tax for a year using the same method it uses to determine the member's share of the consolidated minimum tax credits for the year. 
                        </P>
                        <P>
                            (
                            <E T="03">3</E>
                            ) 
                            <E T="03">Years included in computation.</E>
                             For purposes of computing the limitation under this paragraph (h)(4)(iii), the consolidated return years of the group include only those years, including the year to which a credit is carried, that the member has been continuously included in the group's consolidated return, but exclude any years after the year to which the credit is carried. 
                        </P>
                        <P>
                            (
                            <E T="03">4</E>
                            ) 
                            <E T="03">Subgroup principles.</E>
                             The SRLY subgroup principles under § 1.1502-21(c)(2) apply for purposes of this paragraph (h)(4)(iii). The predecessor and successor principles under § 1.1502-21(f) also apply for purposes of this paragraph (h)(4)(iii). 
                        </P>
                        <P>
                            (5) 
                            <E T="03">Overlap with section 383.</E>
                             The principles under § 1.1502-21(g) apply for purposes of this paragraph (h)(4)(iii). For example, an overlap of this paragraph (h)(4)(iii) and the application of section 383 with respect to a credit carryover occurs if a corporation becomes a member of a consolidated group (the SRLY event) within six months of the change date of an ownership change giving rise to a section 383 credit limitation with respect to that carryover (the section 383 event), with the result that the limitation of this paragraph (h)(4)(iii) does not apply. See §§ 1.1502-21(g)(2)(ii)(A) and 1.383-1; see also § 1.1502-21(g)(4) (subgroup rules). 
                        </P>
                        <P>
                            (C) 
                            <E T="03">Effective date</E>
                            —(1) 
                            <E T="03">In general.</E>
                             This paragraph (h)(4)(iii) generally applies to consolidated return years for which the due date of the income tax return (without extensions) is after March 13, 1998. See § 1.1502-3(d)(4) for an optional effective date rule (generally making this paragraph (h)(4)(iii) also applicable to a consolidated return year beginning on or after January 1, 1997, if the due date of the income tax return (without extensions) was on or before March 13, 1998). 
                        </P>
                        <P>
                            (i) 
                            <E T="03">Contribution years.</E>
                             In general, a group does not take into account a consolidated taxable year for which the due date of the income tax return (without extensions) is on or before March 13, 1998, in determining a member's (or subgroup's) contributions to the consolidated section 53(c) limitation under this paragraph (h)(4)(iii). However, if a consolidated group chooses to apply the optional effective date rule, the consolidated group shall not take into account a consolidated taxable year beginning before January 1, 1997 in determining a member's (or subgroup's) contributions to the consolidated section 53(c) limitation under this paragraph (h)(4)(iii). 
                            <PRTPAGE P="33760"/>
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Special subgroup rule.</E>
                             In the event that the principles of § 1.1502-21(g)(1) do not apply to a particular credit carryover in the current group, then solely for purposes of applying this paragraph (h)(4)(iii) to determine the limitation with respect to that carryover and with respect to which the SRLY register (the aggregate of the member's or subgroup's contribution to consolidated section 53(c) limitation reduced by the aggregate of the member's or subgroup's minimum tax credits arising and absorbed in all consolidated return years) began in a taxable year for which the due date of the return is on or before May 25, 2000, the principles of § 1.1502-21(c)(2) shall be applied without regard to the phrase “or for a carryover that was subject to the overlap rule described in paragraph (g) of this section or § 1.1502-15(g) with respect to another group (the former group).” 
                        </P>
                        <P>
                            (2) 
                            <E T="03">Overlap rule.</E>
                             Paragraph (h)(4)(iii)(B)(
                            <E T="03">5</E>
                            ) of this section (relating to overlap with section 383) applies to taxable years for which the due date (without extensions) of the consolidated return is after May 25, 2000. For purposes of paragraph (h)(4)(iii)(B)(
                            <E T="03">5</E>
                            ) of this section, only an ownership change to which section 383, as amended by the Tax Reform Act of 1986 (100 Stat. 2095), applies and which results in a section 383 credit limitation shall constitute a section 383 event. The optional effective date rule of § 1.1502-3(d)(4) (generally making this paragraph (h)(4)(iii) also applicable to a consolidated return year beginning on or after January 1, 1997, if the due date of the income tax return (without extensions) was on or before March 13, 1998) does not apply with respect to paragraph (h)(4)(iii)(B)(
                            <E T="03">5</E>
                            ) of this section (relating to the overlap rule). 
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <SECTION>
                        <SECTNO>§ 1.1502-55T </SECTNO>
                        <SUBJECT>[Removed] </SUBJECT>
                        <P>
                            <E T="04">Par. 8.</E>
                             Section 1.1502-55T is removed. 
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 9.</E>
                         Section 1.1502-98 is amended by adding a sentence immediately following the first sentence to read as follows: 
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.1502-98 </SECTNO>
                        <SUBJECT>Coordination with section 383. </SUBJECT>
                        <P>* * * For example, subgroups with respect to the carryover of general business credits, minimum tax credits, unused foreign tax, and net capital loss are determined by applying the principles of § 1.1502-91(d)(1). * * * </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <SECTION>
                        <SECTNO>§ 1.1502-9A </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                        <P>
                            <E T="04">Par. 10.</E>
                             Section 1.1502-9A is amended as follows: 
                        </P>
                    </SECTION>
                    <AMDPAR>1. In paragraph (a)(2), the last sentence is amended by removing the language “1.1502-3T(c)(4)” and adding “1.1502-3(d)(4)” in its place. </AMDPAR>
                    <AMDPAR>2. In paragraph (b)(1)(v), the last sentence is amended by removing the language “1.1502-3T(c)(4)” and adding “1.1502-3(d)(4)” in its place. </AMDPAR>
                </REGTEXT>
                <SIG>
                    <NAME>Robert E. Wenzel,</NAME>
                    <TITLE>Deputy Commissioner of Internal Revenue. </TITLE>
                    <APPR>Approved: May 8, 2000.</APPR>
                    <NAME>Jonathan Talisman, </NAME>
                    <TITLE>Deputy Assistant Secretary of the Treasury. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-11901 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Coast Guard </SUBAGY>
                <CFR>33 CFR Parts 100, 110, and 165 </CFR>
                <DEPDOC>[CGD01-99-050] </DEPDOC>
                <RIN>RIN 2115-AA97, AA98, AE46 </RIN>
                <SUBJECT>Temporary Regulations: OPSAIL 2000/International Naval Review 2000 (INR 2000), Port of New York/New Jersey </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is establishing temporary regulations in New York Harbor, Sandy Hook Bay, the Hudson and East Rivers, and the Kill Van Kull for OPSAIL 2000/INR 2000 activities. This action is necessary to provide for the safety of life on navigable waters during OPSAIL 2000/INR 2000. This action is intended to restrict vessel traffic in portions of New York Harbor, Sandy Hook Bay, the Hudson and East Rivers, and the Kill Van Kull. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective from 12 p.m. e.s.t. on June 29, 2000, until 12 p.m. e.s.t. on July 5, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments and material received from the public, as well as documents indicated in this preamble as being available in the docket, are part of docket CGD01-99-050 and are available for inspection or copying at room 205, of the Waterways Oversight Branch of Coast Guard Activities New York, between 8 a.m., e.s.t. and 3 p.m., e.s.t. Monday through Friday, except Federal holidays. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lieutenant J. Lopez, Waterways Oversight Branch, Coast Guard Activities New York (718) 354-4193. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Regulatory Information </HD>
                <P>
                    On February 7, 2000, we published a notice of proposed rulemaking (NPRM) entitled Temporary Regulations: OPSAIL 2000/International Naval Review 2000 (INR 2000), Port of New York/New Jersey in the 
                    <E T="04">Federal Register</E>
                     (65 FR 5833). On February 14, 2000, we published a correction to this NPRM entitled Temporary Regulations: OPSAIL 2000/International Naval Review 2000 (INR 2000), Port of New York/New Jersey in the 
                    <E T="04">Federal Register</E>
                     (65 FR 7333). We received no letters commenting on the proposed rule. No public hearing was requested, and none was held. 
                </P>
                <HD SOURCE="HD1">Background and Purpose </HD>
                <P>The U.S. Navy is sponsoring the International Naval Review. This event consists of the anchoring of approximately 50 U.S. and foreign naval vessels in line between the Verrazano-Narrows Bridge and the George Washington Bridge. A high level U.S. dignitary will transit aboard a U.S. Navy vessel along this line as a ceremonial review. Operation Sail, Inc. is sponsoring the seventh OPSAIL Parade of Tall Ships, as well as a fireworks display co-sponsored by Macy's Inc. Operation Sail consists of a parade of sailing vessels from the Verrazano-Narrows Bridge north past a reviewing stand aboard the U.S.S. John F. Kennedy (CV-67) anchored in Federal Anchorage 21B in Upper New York Bay. This parade will continue north to the George Washington Bridge where these vessels will turn south and go to berth throughout the Port of New York and New Jersey. These events are scheduled to take place on July 4, 2000, in the Port of New York/New Jersey, on the waters of New York Harbor, Sandy Hook Bay, the Hudson and East Rivers, and the Kill Van Kull. The Coast Guard expects a minimum of 40,000 spectator craft for these events. These regulations create temporary anchorage regulations, vessel movement controls, and two security zones. The regulations will be in effect at various times in the Port of New York and New Jersey during the period June 29, 2000 through July 5, 2000. The vessel congestion due to the large number of participating and spectator vessels poses a significant threat to the safety of life. This rulemaking is necessary to ensure the safety of life on the navigable waters of the United States. </P>
                <HD SOURCE="HD1">Regulated Areas </HD>
                <P>
                    The Coast Guard is establishing two regulated areas in New York Harbor that will be in effect from July 3-5, 2000. These two regulated areas are needed to protect the maritime public and participating vessels from possible hazards to navigation associated with; 
                    <PRTPAGE P="33761"/>
                    an International Naval Review conducted on the Hudson River and New York Harbor Upper Bay, a Parade of Tall Ships transiting the waters of Sandy Hook Bay, New York Harbor, and the Hudson River in close proximity; fireworks fired from 11-13 barges on the Hudson and East Rivers and in Upper New York Bay; and a large number of naval vessels, Tall Ships, and spectator craft anchored in close proximity throughout the duration of these events. These regulated areas include vessel anchoring and operating restrictions. 
                </P>
                <P>Regulated Area A covers all waters of New York Harbor Lower Bay and Sandy Hook Bay within the following boundaries: south of the Verrazano-Narrows Bridge; west of a line drawn shore to shore along 074°00′00″ W (NAD 1983) between Coney Island, New York, and Navesink, New Jersey; and east of a line drawn shore to shore along 074°03′12″ W (NAD 1983) between Fort Wadsworth, Staten Island, and Leonardo, New Jersey and all waters of Ambrose Channel shoreward of Ambrose Channel Entrance Lighted Gong Buoy 1 (LLNR 34800) and Ambrose Channel Entrance Lighted Bell Buoy 2 (LLNR 34805). Please see Chartlet I, depicting Regulated Area A, included with this Temporary final rule (TFR) for the convenience of the reader. This area is to be used as a staging area for vessels participating in the Parade of Tall Ships. This regulated area is effective from 6 a.m., e.s.t. July 3, until 4 p.m., e.s.t. on July 4, 2000. </P>
                <BILCOD>BILLING CODE 4910-15-U</BILCOD>
                <GPH SPAN="3" DEEP="512">
                    <GID>ER25MY00.006</GID>
                </GPH>
                <PRTPAGE P="33762"/>
                <P>Regulated Area B covers all waters of New York Harbor, Upper Bay, the Hudson, Harlem, and East Rivers, and the Kill Van Kull within the following boundaries: south of 40°52′39″ N (NAD 1983) on the Hudson River at Spuyten Duyvil Creek; west of the Throgs Neck Bridge on the East River; north of the Verrazano-Narrows Bridge; and east of a line drawn from shore to shore along 074°05′15″ W (NAD 1983) between New Brighton, Staten Island, and Constable Hook, New Jersey, in the Kill Van Kull. Please see Chartlet II, depicting Regulated Area B, included with this TFR for the convenience of the reader. This regulated area is for the International Naval Review, the Parade of Tall Ships, and the July 4th fireworks display. This regulated area is effective from 10 a.m., e.s.t. on July 3, 2000, until 10 a.m., e.s.t. on July 5, 2000. </P>
                <GPH SPAN="3" DEEP="547">
                    <GID>ER25MY00.007</GID>
                </GPH>
                <BILCOD>BILLING CODE 4910-15-C</BILCOD>
                <PRTPAGE P="33763"/>
                <P>Spectator vessels transiting Regulated Area A or B must do so at no wake speed or at speeds not to exceed 10 knots, whichever is less. No vessels other than OPSAIL 2000/INR 2000 vessels, their assisting tugs, and enforcement vessels, may enter or navigate within the boundaries of the Anchorage Channel or Hudson River in regulated Area B unless specifically authorized by the Coast Guard Captain of the Port, New York, or his on-scene representative. No vessel may anchor in the Anchorage Channel or Hudson River outside of the designated spectator anchorages in Regulated Area B at any time without authorization. The operation of seaplanes, including taxiing, landing, and taking off, is prohibited in Area B on July 3-4, 2000, without prior written authorization from the Captain of the Port. Ferry services may operate in Area B on July 3 and 5, 2000. On July 4, 2000 only those ferry services with prior written authorization from the Coast Guard Captain of the Port will be authorized to operate in this area. </P>
                <P>No vessel, other than OPSAIL 2000/INR 2000 vessels, their assisting tugs, and enforcement vessels, is permitted to transit the waters between Governors Island and The Battery in southern Manhattan from 7 a.m., e.s.t. July 4, 2000 until the end of the Parade of Sail. Vessels which must transit to or from the East River may only do so by using Buttermilk Channel unless otherwise authorized by the Coast Guard Captain of the Port, New York, or his on-scene representative. </P>
                <P>Regulated Area A contains three anchorage grounds for use by OPSAIL 2000/INR 2000 vessels only and it will also serve as a staging area for the vessels participating in the Parade of Sail. Regulated Area B contains anchorage grounds for OPSAIL 2000/INR 2000 vessels and spectator craft. It contains the International Naval Review of Ships on the Hudson River and New York Harbor's Upper Bay, from the Verrazano-Narrows Bridge to the George Washington Bridge (river mile 11.0). The International Naval Review will be conducted on the morning of July 4, 2000 and consists of a column of approximately 50 International Naval Ships anchored in the Hudson River and New York Harbor's Upper Bay along the western side of the Anchorage Channel. The U.S. Navy Review Ship will transit south along this column from the George Washington Bridge to the Verrazano-Narrows Bridge and conduct a review of all the participating naval ships. After the INR, approximately 300 vessels will participate in the Parade of Sailing Vessels which will take place in Area B between the Verrazano-Narrows Bridge and the George Washington Bridge (river mile 11.0) on the Hudson River. Additionally, Area B will contain 11-13 fireworks barges being used for the July 4th fireworks display. Fireworks barges will be located in the Hudson River between the Holland Tunnel Ventilators and West 65th Street in Manhattan, in the East River between the southern tip of Roosevelt Island and The Battery, east of Liberty Island, and in the Anchorage Channel north of the Verrazano-Narrows Bridge. </P>
                <HD SOURCE="HD1">Anchorage Regulations </HD>
                <P>The Coast Guard is also establishing temporary Anchorage Regulations for participating OPSAIL 2000/INR 2000 ships and spectator craft. Some current Anchorage Regulations in 33 CFR 110.155 are temporarily suspended by this regulation and new Anchorage Grounds and regulations are being temporarily established. Chartlets I, III, and IV illustrate the anchorage grounds and are included for the convenience of the reader. </P>
                <P>The anchorage regulations designate selected current or temporarily established Anchorage Grounds for spectator or OPSAIL 2000/INR 2000 participant vessel use only. They restrict all other vessels from using these Anchorage Grounds during a portion of the OPSAIL 2000/INR 2000 event. The Anchorage Grounds are needed to provide viewing areas for spectator vessels while maintaining a clear parade route for the participating OPSAIL/INR vessels and to protect boaters and spectator vessels from the hazards associated with the International Naval Review and the Parade of Tall Ships. </P>
                <P>The Coast Guard designates Anchorage Grounds 16, 17, and 18-A in the Hudson River in the vicinity of the George Washington Bridge (river mile 11.0); and the temporarily established Liberty Island Anchorage, Ellis Island Anchorage, Caven Point Anchorage, Jersey Flats Anchorage and Robbins Reef Anchorage in New York Harbor's Upper Bay, and a temporary Anchorage Ground from north of the Verrazano-Narrows Bridge to Owls Head Park along the Brooklyn shoreline exclusively for spectator vessel use from 12 p.m., e.s.t. on June 29, 2000, until 12 p.m., e.s.t. on July 5, 2000. The temporary Narrows Anchorage is being expanded to authorize a larger viewing area for spectator vessels between 25 meters (82 feet) and 60 meters (197 feet). The expanded area includes all waters of Anchorage Channel east of a line drawn between Gowanus Flats Lighted Bell Buoy 22 (LLNR 34945) and Bay Ridge Channel Lighted Buoy 2 (LLNR 36872) to the western boundary of the temporary Narrows Anchorage. </P>
                <P>The Coast Guard also designates Anchorage Grounds 21-B, 23-A, 23-B, and 24 in New York Harbor's Upper Bay for OPSAIL 2000/INR 2000 participant vessels. These regulations are effective from 3 a.m., e.s.t. July 1, 2000, through 6 p.m., e.s.t. July 5, 2000. Other vessels may be authorized to use these anchorages on July 1 and 2, 2000 as determined by the Captain of the Port, New York. </P>
                <P>Additionally, the Coast Guard designates Anchorage Ground 25 and a temporarily established Anchorage Ground covering portions of Anchorage Grounds 26, 49-F and 49G in Sandy Hook Bay for OPSAIL 2000/INR 2000 participant vessels. These proposed regulations are effective from 6 a.m., e.s.t. July 2, 2000, through 4 p.m., e.s.t. July 4, 2000. </P>
                <P>The eastern portions of the Jersey Flats and Robbins Reef Anchorages and the Narrows Temporary Anchorage Ground are for vessels between 25 meters (82 feet) and 60 meters (197 feet) in length. Anchorage 21-C is for vessels greater than 60 meters (197 feet). Positioning within these three anchorages will be controlled by the Captain of the Port, New York. Persons desiring to use these anchorages must have a permit from the Captain of the Port New York. A lottery was held to determine vessel anchorage locations and applications are no longer being accepted. </P>
                <BILCOD>BILLING CODE 4910-15-U</BILCOD>
                <GPH SPAN="3" DEEP="573">
                    <PRTPAGE P="33764"/>
                    <GID>ER25MY00.008</GID>
                </GPH>
                <GPH SPAN="3" DEEP="548">
                    <PRTPAGE P="33765"/>
                    <GID>ER25MY00.009</GID>
                </GPH>
                <BILCOD>BILLING CODE 4910-15-C</BILCOD>
                <PRTPAGE P="33766"/>
                <HD SOURCE="HD1">Security Zones </HD>
                <P>The Coast Guard is establishing a moving security zone for all waters within 500 yards of the Review Ship for the International Naval Review from 7 a.m., e.s.t. until 11 a.m., e.s.t. on July 4, 2000. The Review Ship will be the U.S. Navy vessel that is anchored the furthest north in the Hudson River at 7 a.m., e.s.t. on July 4, 2000. This ship will get underway and transit down the Hudson River and Upper New York Bay between the George Washington Bridge (river mile 11.0) and the Verrazano-Narrows Bridge. The Review Ship will be easily identifiable during its transit because it will be the only large U.S. Navy vessel that is underway at this time in the Port of New York, and it will be escorted by numerous U.S. Coast Guard small boats. </P>
                <P>A second security zone is established for all waters within 500 yards of the U.S.S. John F. Kennedy (CV-67), from 10 a.m., e.s.t. until 5 p.m., e.s.t. on July 4, 2000 while in Anchorage 21-B and while being used as the reviewing stand for the Parade of Sailing Vessels. Numerous dignitaries who require Secret Service protection will be onboard both Navy vessels. Due to the dignitaries' attendance, security zones are required to ensure the proper level of protection to prevent sabotage or other subversive acts, accidents, or other activities of a similar nature to the Port of New York/New Jersey. </P>
                <HD SOURCE="HD1">Discussion of Comments and Changes </HD>
                <P>We received no letters commenting on the proposed rule, but we did make two minor changes to it. The temporary Narrows Anchorage is being expanded to make a larger viewing area for spectator vessels between 25 meters (82 feet) and 60 meters (197 feet). The expanded area includes all waters of Anchorage Channel east of a line drawn between Gowanus Flats Lighted Bell Buoy 22 (LLNR 34945) and Bay Ridge Channel Lighted Buoy 2 (LLNR 36872) to the western boundary of the temporary Narrows Anchorage, and south of the current southern boundary of Federal Anchorage 21-C. This change increases the length of the temporary Narrows Anchorage by 1,450 yards. The increased anchorage length is necessary because it provides a greater area for spectator craft to anchor in. It is also easier to enforce as the western boundary is now aligned with the western boundary of Federal Anchorage No. 21-C. This will provide one straight boundary line to enforce as opposed to three boundary lines as originally planned. The expanded temporary Narrows Anchorage area will not have a negative impact on vessel traffic in the area because the expanded area does not include any navigable channels and it would not have been used by vessels. But it will have a positive impact because it provides space for five extra spectator craft that were alternate winners of the lottery drawing for anchorage spots in the area. </P>
                <P>We changed section 110.155's introductory note to emphasize the mariners' need to exercise caution while using the temporarily designated anchorage areas for OPSAIL 2000/INR 2000. While we are not aware of any safety problems associated with these temporary anchorage areas, we can not ensure the anchor holding capability of each area nor that the bottoms are free from obstructions. Consequently, we are advising mariners to take appropriate precautions including using all means available to ensure their vessels are not dragging anchor. But based on past experience with these temporary anchorage areas, we have no reason to believe they are not adequate for their intended use. </P>
                <HD SOURCE="HD1">Regulatory Evaluation </HD>
                <P>This rule is not a “significant regulatory action” under section 3(f) of Executive Order 12866 and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order. It is not “significant” under the regulatory policies and procedures of the Department of Transportation (DOT) (44 FR 11040, February 26, 1979). </P>
                <P>We expect the economic impact of this rule to be so minimal that a full Regulatory Evaluation under paragraph 10e of the regulatory policies and procedures of DOT is unnecessary. </P>
                <P>Although this regulation prevents traffic from transiting a portion of New York Harbor, Sandy Hook Bay, the Hudson and East Rivers, and the Kill Van Kull during the events, the effect of this regulation will not be significant for the following reasons: The limited duration that the regulated areas will be in effect and the extensive advance notifications that have been and will be made to the maritime community via the Local Notice to Mariners, facsimile, marine information broadcasts, New York Harbor Operations Committee meetings, and New York area newspapers, so mariners can adjust their plans accordingly. At no time will commercial shipping access to Port Newark/Port Elizabeth facilities be prohibited. Access to those areas may be accomplished using Raritan Bay, Arthur Kill, Kill Van Kull, and Newark Bay as an alternate route. This will allow the majority of the maritime industrial activity in the Port of New York/New Jersey to continue, relatively unaffected. Similar regulated areas were established for the 1986 and 1992 OPSAIL events. Based upon the Coast Guard's experiences learned from these previous events of a similar magnitude, these proposed regulations have been narrowly tailored to impose the least impact on maritime interests yet provide the level of safety deemed necessary. </P>
                <P>One substantive change is being made to the Temporary final rule. The temporary Narrows Anchorage is being expanded to authorize a larger viewing area for spectator vessels between 25 meters (82 feet) and 60 meters (197 feet). The expanded area includes all waters of Anchorage Channel east of a line drawn between Gowanus Flats Lighted Bell Buoy 22 (LLNR 34945) and Bay Ridge Channel Lighted Buoy 2 (LLNR 36872) to the western boundary of the temporary Narrows Anchorage, and south of the current southern boundary of Federal Anchorage 21-C. We expect this change to have no adverse economic impact as it increases the size of the available spectator craft viewing area in the Narrows Temporary anchorage without closing any portions of any navigable channels. As originally published in the NPRM, this area would not have been used by any vessels. </P>
                <HD SOURCE="HD1">Small Entities </HD>
                <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we considered whether this 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>
                    For the reasons discussed in the Regulatory Evaluation section above, the Coast Guard certifies under 5 U.S.C. 605(b) that this rule would not have a significant economic impact on a substantial number of small entities. This rule would affect the following entities, some of which might be small entities: The owners or operators of vessels intending to transit or anchor in portions of Lower and Upper New York Bay and the Hudson and East Rivers during various times from June 29-July 5, 2000. These regulations will not have a significant economic impact on a substantial number of small entities for the following additional reasons: Although these regulations will apply to a substantial portion of the Port of New York/New Jersey, designated areas for 
                    <PRTPAGE P="33767"/>
                    viewing the Parade of Sailing Vessels and the Fourth of July Fireworks are being established to allow for maximum use of the waterways by commercial tour boats that usually operate in the affected areas. Before the effective period, the Coast Guard will make notifications to the public via mailings, facsimiles, the Local Notice to Mariners and use of the sponsors Internet site. In addition, the sponsoring organization, OPSAIL Inc., is planning to publish information of the event in local newspapers, pamphlets, and television and radio broadcasts. 
                </P>
                <P>One substantive change is being made to the Temporary final rule. The temporary Narrows Anchorage is being expanded to authorize a larger viewing area for spectator vessels between 25 meters (82 feet) and 60 meters (197 feet). The expanded area includes all waters of Anchorage Channel east of a line drawn between Gowanus Flats Lighted Bell Buoy 22 (LLNR 34945) and Bay Ridge Channel Lighted Buoy 2 (LLNR 36872) to the western boundary of the temporary Narrows Anchorage, and south of the current southern boundary of Federal Anchorage 21-C. This will have a positive impact on small entities as it provides space for five more spectator craft to be awarded permits to anchor here in the lottery drawing. As originally published in the NPRM, this area would not have been used by any vessels. </P>
                <HD SOURCE="HD1">Assistance for Small Entities </HD>
                <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Public Law 104-121), we offered to assist small entities in understanding the rule so that they could better evaluate its effects on them and participate in the rulemaking process. We provided explanations of the effect of these regulations on the Port of New York/New Jersey to approximately 15 small entities. </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 Agricultural 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-800-REG-FAIR (1-888-734-3247). </P>
                <HD SOURCE="HD1">Collection of Information </HD>
                <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520). </P>
                <HD SOURCE="HD1">Federalism </HD>
                <P>We have analyzed this rule under Executive Order 13132 and have determined that this rule does not have implications for federalism under that Order. </P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act </HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) governs the issuance of Federal regulations that require unfunded mandates. An unfunded mandate is a regulation that requires a State, local, or tribal government or the private sector to incur direct costs without the Federal Government's having first provided the funds to pay those unfunded mandate costs. This rule will not impose an unfunded mandate. </P>
                <HD SOURCE="HD1">Taking of Private Property </HD>
                <P>This rule will not effect 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="HD1">Civil Justice Reform </HD>
                <P>This 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="HD1">Protection of Children </HD>
                <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not concern an environmental risk to health or risk to safety that may disproportionately affect children. </P>
                <HD SOURCE="HD1">Environment </HD>
                <P>
                    The Coast Guard considered the environmental impact of this rule, including the expansion of the Temporary Narrows Anchorage discussed in the Discussion of Comments and Changes section above, and concluded that, under figure 2-1, paragraph 34(f, g, and h), of Commandant Instruction M16475.1C, this rule is categorically excluded from further environmental documentation. These temporary regulations establish special local regulations, anchorage grounds, and security zones. A “Categorical Exclusion Determination” is available in the docket where indicated under 
                    <E T="02">ADDRESSES.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects </HD>
                    <CFR>33 CFR Part 100 </CFR>
                    <P>Marine safety, Navigation (water), Reporting and recordkeeping requirements, Waterways.</P>
                    <CFR>33 CFR Part 110 </CFR>
                    <P>Anchorage grounds. </P>
                    <CFR>33 CFR Part 165 </CFR>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <REGTEXT TITLE="38" PART="100">
                    <AMDPAR>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR Parts 100, 110, and 165 as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 100—MARINE EVENTS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 100 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>33 U.S.C. 1233 through 1236; 49 CFR 1.46; 33 CFR 100.35.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="100">
                    <AMDPAR>2. Add temporary § 100.T01-050 to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 100.T01-050 </SECTNO>
                        <SUBJECT>OPSAIL 2000/International Naval Review (INR) 2000, Port of New York/New Jersey. </SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Regulated Areas.</E>
                             (1) 
                            <E T="03">Regulated Area A.</E>
                             (i) 
                            <E T="03">Location.</E>
                             All waters of New York Harbor, Lower Bay and Sandy Hook Bay within the following boundaries: south of the Verrazano-Narrows Bridge; west of a line drawn shore to shore along 074°00″00 W (NAD 1983) between Coney Island, New York, and Navesink, New Jersey; and east of a line drawn shore to shore along 074°03′12″ W (NAD 1983) between Fort Wadsworth, Staten Island, and Leonardo, New Jersey, and all waters of Ambrose Channel shoreward of Ambrose Channel Entrance Lighted Gong Buoy 1 (LLNR 34800) and Ambrose Channel Entrance Lighted Bell Buoy 2 (LLNR 34805). 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Enforcement period.</E>
                             Paragraph (a)(1)(i) of this section is enforced from 6 a.m., e.s.t. July 3, until 4 p.m., e.s.t. on July 4, 2000. 
                        </P>
                        <P>
                            (2) 
                            <E T="03">Regulated Area B.</E>
                             (i) 
                            <E T="03">Location.</E>
                             All waters of New York Harbor, Upper Bay, the Hudson and East Rivers, and the Kill Van Kull within the following boundaries: south of 40°52′39″ N (NAD 1983) on the Hudson River at Spuyten Duyvil Creek; west of the Throgs Neck Bridge on the East River; north of the Verrazano-Narrows Bridge; and east of a line drawn from shore to shore along 074°05′15″ W (NAD 1983) between New Brighton, Staten Island, and Constable Hook, New Jersey, in the Kill Van Kull. 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Enforcement period.</E>
                             Paragraph (a)(2)(i) of this section is enforced from 10 a.m., e.s.t. on July 3, 2000, until 10 a.m., e.s.t. on July 5, 2000. 
                            <PRTPAGE P="33768"/>
                        </P>
                        <P>
                            (b) 
                            <E T="03">Special local regulations.</E>
                             (1) No vessel except OPSAIL 2000/INR 2000 participating vessels and their assisting tugs, spectator vessels, and those vessels exempt from the regulations in this section, may enter or navigate within Areas A and B, unless specifically authorized by the Coast Guard Captain of the Port, New York, or his on-scene representative. 
                        </P>
                        <P>(2) Vessels transiting Area B must do so at no wake speed or at speeds not to exceed 10 knots, whichever is less. </P>
                        <P>(3) Not withstanding paragraph (b)(1) of this section, no vessel, other than OPSAIL 2000/INR 2000 Vessels, their assisting tugs, and enforcement vessels, may enter or navigate within the boundaries of the main shipping channels in Area B unless they are specifically authorized to do so by Coast Guard Captain of the Port, New York, or his on-scene representative. No vessel in Area B is permitted to cross through the parade of sail, cross within 500 yards of the lead or last vessel in the parade of sail, or maneuver alongside within 100 yards of any OPSAIL 2000/INR 2000 Vessel unless authorized to do so by the Captain of the Port. </P>
                        <P>(4) No vessel is permitted to anchor in the Anchorage Channel or the Hudson River outside of the designated anchorages at any time without authorization. Vessels which need to anchor to maintain position will only do so in designated anchorage areas. </P>
                        <P>(5) No vessel, other than OPSAIL 2000/INR 2000 Vessels, their assisting tugs, and enforcement vessels, is permitted to transit the waters between Governors Island and The Battery in southern Manhattan from 7 a.m., e.s.t. July 4, 2000 until the end of the Parade of Sailing Vessels. Vessels which must transit to or from the East River may only do so by using Buttermilk Channel, unless otherwise authorized by the Coast Guard Captain of the Port, New York, or his designated on-scene representative. </P>
                        <P>(6) Ferry services may operate in Area B on July 3 and 5, 2000. On July 4, 2000 only those with prior written authorization from the Coast Guard Captain of the Port will be authorized to operate in this area. </P>
                        <P>(7) The operation of seaplanes, including taxiing, landing, and taking off, is prohibited in Area B on July 3-4, 2000, without prior written authorization from the Captain of the Port. </P>
                        <P>(8) All spectator vessels must maintain their position in the designated spectator craft anchorages during the fireworks display on July 4th scheduled from 9 p.m., e.s.t. until 10:45 p.m., e.s.t. </P>
                        <P>
                            (c) 
                            <E T="03">Effective period.</E>
                             This section is applicable from 6 a.m., e.s.t. on July 3, 2000, until 10 a.m., e.s.t. on July 5, 2000. 
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="110">
                    <PART>
                        <HD SOURCE="HED">PART 110—ANCHORAGE REGULATIONS </HD>
                    </PART>
                    <AMDPAR>3. The authority citation for part 110 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>33 U.S.C. 471, 1221 through 1236, 2030, 2035 and 2071; 49 CFR 1.46 and 33 CFR 1.05-1(g). </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="110">
                    <AMDPAR>4. Effective June 29, 2000 through July 5, 2000, § 110.155 is temporarily amended as follows: </AMDPAR>
                    <AMDPAR>a. Add introductory text to the beginning of the section; </AMDPAR>
                    <AMDPAR>b. Add new paragraphs (c)(1)(ii), (c)(2)(ii), (c)(3)(ii); </AMDPAR>
                    <AMDPAR>c. Paragraphs (d)(1) through (d)(5), (d)(7) through (d)(9), (d)(10)(i), (d)(12)(i) and the introductory text of paragraph (d)(16) are suspended and new paragraphs (d)(10)(ii), (d)(11)(iii), (d)(12)(iii) through (d)(12)(iv), (d)(13)(vi), (d)(14)(iv), (d)(15)(iii), and (d)(17) through (d)(20) are added; </AMDPAR>
                    <AMDPAR>d. Add new paragraph (e)(1)(iii); </AMDPAR>
                    <AMDPAR>e. The Note to paragraph (f)(1) introductory text is suspended; </AMDPAR>
                    <AMDPAR>f. Paragraphs (m)(2)(i) through (m)(2)(ii) and (m)(3)(i) are suspended and new paragraphs (m)(2)(iii) and (m)(3)(ii) are added; </AMDPAR>
                    <AMDPAR>g. Paragraph (n)(1) is suspended; and </AMDPAR>
                    <AMDPAR>h. Add new paragraphs (o) and (p). </AMDPAR>
                    <AMDPAR>The additions read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 110.155 </SECTNO>
                        <SUBJECT>Anchorage Grounds; Port of New York. </SUBJECT>
                        <P>The designated anchorage grounds in this section have not been specially surveyed or inspected and navigational charts may not show all seabed obstructions or shallowest depths. Additionally, the anchorages are in areas of substantial currents. Mariners who use these temporary anchorages should take appropriate precautions, including using all means available to ensure your vessel is not dragging anchor. Finally, these are not special anchorage areas. Thus vessels must display anchor lights, as required by the navigation rules. </P>
                        <STARS/>
                        <P>(c) * * * </P>
                        <P>(1) * * * </P>
                        <P>(ii) This anchorage is designated for the exclusive use of spectator vessels less than 25 meters (82 feet) in length on a first come, first served basis. </P>
                        <P>(2) * * * </P>
                        <P>(ii) See paragraph (c)(1)(ii) of this section. </P>
                        <P>(3) * * * </P>
                        <P>(ii) See paragraph (c)(1)(ii) of this section. </P>
                        <STARS/>
                        <P>(d) * * * </P>
                        <P>(10) * * * </P>
                        <P>(ii) This anchorage is for OPSAIL 2000 participating vessels only. </P>
                        <P>(11) * * * </P>
                        <P>(iii) This anchorage is reserved for OPSAIL 2000/INR 2000 participating vessels. No other vessel may anchor or operate in this area within 100 yards of OPSAIL 2000/INR 2000 participating vessels. </P>
                        <P>(12) * * * </P>
                        <P>(iii) This anchorage is for vessels greater than 60 meters (197 feet) in length. Persons desiring to use this anchorage must hold a permit from the Captain of the Port New York on their vessel. A lottery was held to determine vessel anchorage locations and applications are no longer being accepted. </P>
                        <P>(iv) This anchorage is available for vessels observing or participating in OPSAIL 2000/INR 2000 festivities and which have been authorized by the Coast Guard Captain of the Port, New York. No vessel may anchor within this area without authorization to do so. </P>
                        <P>(13) * * * </P>
                        <P>(vi) See paragraph (d)(12)(iv) of this section. </P>
                        <P>(14) * * * </P>
                        <P>(iv) See paragraph (d)(12)(iv) of this section. </P>
                        <P>(15) * * * </P>
                        <P>(iii) See paragraph (d)(12)(iv) of this section. </P>
                        <STARS/>
                        <P>(17) The anchorages in this paragraph (d)(17) are designated for the exclusive use of spectator vessels less than 25 meters (82 feet) in length on a first come, first served basis. </P>
                        <P>
                            (i) 
                            <E T="03">Ellis Island Anchorage.</E>
                             That area bound by the following points: 40°41′55″ N, 074°02′56″ W; 40°41′29.5″ N, 074°02′05″ W; 40°41′42″ N, 074°02′00.5″ W; 40°41′55″ N, 074°01′58″ W; 40°42′05″ N, 074°01′57″ W; 40°42′20.5″ N, 074°02′06″ W (NAD 1983); thence along the shoreline to the point of beginning. 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Liberty Island Anchorage.</E>
                             That area bound by the following points: 40°41′30.5″ N, 074°03′15.5″ W; 40°41′11.5″ N, 074°02′44″ W; 40°41′34″ N, 074°02′26.5″ W; 40°41′51.5″ N, 074°02′59.5″ W (NAD 1983); thence along the shoreline to the point of beginning. 
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Caven Point Anchorage.</E>
                             That area bound by the following points: 40°40′33″ N, 074°03′33″ W; 40°40′25″ N, 074°03′23″ W; 40°40′09.5″ N, 074°02′59″ W; 40°40′59.5″ N, 074°02′26.5″ W; 40°41′26″ N, 074°03′18″ W (NAD 1983); thence along the shoreline and the Caven Point Pier to the point of beginning. 
                            <PRTPAGE P="33769"/>
                        </P>
                        <P>
                            (18) 
                            <E T="03">Jersey Flats Anchorage.</E>
                             That area bound by the following points: 40°39′57″ N, 074°04′00″ W; 40°39′50″ N, 074°03′56″ W; 40°39′35″ N, 074°03′22″ W; 40°40′02.5″ N, 074°03′04″ W; 40°40′53″ N, 074°04′17″ W (NAD 1983); thence along the shoreline to the point of beginning. 
                        </P>
                        <P>(i) The area west of the eastern end of the Global Marine Terminal Pier is for the exclusive use of spectator vessels less than 25 meters (82 feet) in length on a first come, first served basis. The area east of the eastern end of the Global Marine Terminal Pier is for vessels between 25 meters (82 feet) and 60 meters (197 feet) in length. </P>
                        <P>(ii) Persons desiring to use this anchorage must hold a permit from the Captain of the Port New York on their vessel. A Lottery was held to determine vessel anchorage locations and applications are no longer being accepted. </P>
                        <P>
                            (19) 
                            <E T="03">Robbins Reef Anchorage.</E>
                             That area bound by the following points: 40°39′19.5″ N, 074°05′10″ W; 40°39′00″ N, 074°03′46″ W; 40°39′22″ N, 074°03′29″ W; 40°39′49.5″ N, 074°04′06″ W; (NAD 1983); thence along the shoreline to the point of beginning. 
                        </P>
                        <P>(i) The area west of the eastern end of the Military Ocean Terminal Pier is for the exclusive use of spectator vessels less than 25 meters (82 feet) in length on a first come, first served basis. The area east of the eastern end of the Military Ocean Terminal Pier is for vessels between 25 meters (82 feet) and 60 meters (197 feet) in length. </P>
                        <P>(ii) Persons desiring to use this anchorage must hold a permit from the Captain of the Port New York on their vessel. A lottery was held to determine vessel anchorage locations and applications are no longer being accepted. </P>
                        <P>(20) All vessels anchored in the anchorages described in paragraphs (d)(17) through (19) of this section must comply with the requirements in paragraphs (d)(16)(iii) through (vii) of this section. Any vessel anchored in or intending to anchor in Federal Anchorage 21-A through 21-C, 23-A, 23-B, 24 or 25 must comply with the requirements in paragraphs (d)(16)(i) through (x) of this section. </P>
                        <P>(e) * * * </P>
                        <P>(1) * * * </P>
                        <P>(iii) No vessel other than OPSAIL 2000/INR 2000 Vessels and their designated assist tugs may anchor and/or approach within 100 yards of any OPSAIL 2000/INR 2000 Vessel navigating or anchored in this area. </P>
                        <STARS/>
                        <P>(m) * * * </P>
                        <P>(2) * * * </P>
                        <P>(iii) Anchorage No. 49-F is reserved for vessels as set out in paragraph (o)(2) of this section. </P>
                        <P>(3) * * * </P>
                        <P>(ii) Anchorage No. 49-G is reserved for vessels as set out in paragraph (o)(2) of this section. </P>
                        <STARS/>
                        <P>
                            (o) 
                            <E T="03">Temporary Anchorage Grounds.</E>
                             (1) 
                            <E T="03">Narrows Anchorage.</E>
                             That area bound by the following points: 40°38′17″ N, 074°02′18.5″ W; 40°38′22″ N, 074°02′39″ W; 40°38′02.5″ N, 074°02′47.5″ W; 40°38′03″ N, 074°03′02″ W; 40°37′21.5″ N, 074°02′48.5″ W; 40°36′31″ N, 074°02′34″ W; 40°36′36.5″ N, 074°02′15.5″ W; 40°36′53.5″ N, 074°02′28.5″ W; 40°37′13″ N, 074°02′34″ W; 40°37′44″ N, 074°02′33″ W; thence to the point of beginning at 40°38′17″ N, 074°02′18.5″ W (NAD 1983). 
                        </P>
                        <P>(i) This anchorage is designated for the exclusive use of spectator vessels between 25 meters (82 feet) and 60 meters (197 feet) in length. Persons desiring to use this anchorage must hold a permit from the Captain of the Port New York on their vessel. A lottery was held to determine vessel anchorage locations and applications are no longer being accepted. </P>
                        <P>
                            (ii) 
                            <E T="03">Effective period.</E>
                             Paragraph (o)(1) of this section is applicable from 12 p.m., e.s.t. on July 2, 2000, through 12 noon on July 5, 2000. 
                        </P>
                        <P>
                            (2) 
                            <E T="03">Sandy Hook Bay Anchorage.</E>
                             That area bound by the following points: 40°28′30″ N, 074°01′42″ W; 40°27′56″ N, 074°01′35″ W; 40°27′54″ N, 074°01′25″ W; 40°26′00″ N, 074°00′58″ W; 40°26′00″ N, 074°02′00″ W; 40°26′29″ N, 074°02′51″ W; 40°27′29″ N, 074°02′10″ W; 40°27′40″ N, 074°02′36″ W; 40°28′07″ N, 074°02′19″ W (NAD 1983); thence along the shoreline to the point of beginning. 
                        </P>
                        <P>(i) This anchorage sets aside Anchorage No. 49-F and a portion of Anchorage No. 26, as described in paragraph (f)(1) of this section, for the exclusive use of OPSAIL 2000/INR 2000 Vessels. </P>
                        <P>(ii) No vessels other than OPSAIL 2000/INR 2000 naval and Tall Ships, their designated assist tugs, and enforcement vessels may anchor, loiter, or approach within 100 yards of any OPSAIL 2000/INR 2000 Vessel when it is navigating or at anchor in this area. </P>
                        <P>
                            (iii) 
                            <E T="03">Effective period.</E>
                             Paragraph (o)(2) of this section is applicable from 6 a.m., e.s.t. on July 2, 2000, through 4 p.m., e.s.t. on July 4, 2000. 
                        </P>
                        <P>
                            (p) 
                            <E T="03">Temporary amendment applicable dates and times.</E>
                             (1) From 12 noon on June 29, 2000 through 12 noon on July 5, 2000: 
                        </P>
                        <P>(i) The introductory text of this section is applicable. </P>
                        <P>(ii) The suspension of paragraphs (d)(1) through (5), (d)(10)(i), (n)(1), the introductory text of paragraph (d)(16), and the note to paragraph (f)(1) introductory text of this section is applicable. </P>
                        <P>(iii) Paragraphs (d)(10)(ii), (d)(17) through (20) and (p) of this section are applicable. </P>
                        <P>(2) The suspension of paragraphs (d)(7) through (9) of this section is applicable from 3 a.m., e.s.t. on July 3, 2000 through 12 noon on July 5, 2000. </P>
                        <P>(3) From 3 a.m., e.s.t. on July 3, 2000 through 6 a.m., e.s.t. on July 5, 2000: </P>
                        <P>(i) The suspension of paragraph (d)(12)(i) of this section is applicable. </P>
                        <P>(ii) Paragraphs (d)(11)(iii), (d)(12)(iii) and (iv), (d)(13)(vi), (d)(14)(iv), and (d)(15)(iii) of this section are applicable. </P>
                        <P>(4) From 6 a.m., e.s.t. on July 2, 2000 through 4 p.m., e.s.t. on July 4, 2000: </P>
                        <P>(i) The suspensions of paragraphs (m)(2)(i) and (ii), and (m)(3)(i) of this section are applicable. </P>
                        <P>(ii) Paragraphs (m)(2)(iii), (m)(3)(ii), and (e)(1)(iii) of this section are applicable. </P>
                        <P>(5) From 6 a.m., e.s.t. on July 2, 2000 through 12 noon on July 5, 2000, paragraph (o) of this section is applicable. </P>
                        <P>(6) From 12 noon on July 2, 2000 through 12 noon on July 5, 2000, paragraphs (c)(1)(ii), (c)(2)(ii), and (c)(3)(ii) of this section are applicable. </P>
                    </SECTION>
                </REGTEXT>
                <STARS/>
                <REGTEXT TITLE="33" PART="165">
                    <PART>
                        <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS </HD>
                    </PART>
                    <AMDPAR>5. The authority citation for Part 165 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>33 U.S.C. 1231; 50 U.S.C. 191; 33 CFR 1.05-1(g), 6.04-1, 6.04-6, 160.5; 49 CFR 1.46. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>6. Add temporary § 165.T01-050 to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T01-050 </SECTNO>
                        <SUBJECT>Security Zones: International Naval Review (INR) 2000, Hudson River and Upper New York Bay. </SUBJECT>
                        <P>(a) The following areas are established as security zones: </P>
                        <P>
                            (1) 
                            <E T="03">Security Zone A.</E>
                             (i) 
                            <E T="03">Location.</E>
                             This security zone includes all waters within 500 yards of the U.S. Navy review ship and the zone will move with the review ship as it transits the Hudson River and Upper New York Bay during the International Naval Review between the George Washington Bridge (river mile 11.0) and the Verrazano-Narrows Bridge. 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Enforcement period.</E>
                             Paragraph (a)(1)(i) of this section is enforced from 7 a.m., e.s.t. until 11 a.m., e.s.t. on July 4, 2000. 
                            <PRTPAGE P="33770"/>
                        </P>
                        <P>
                            (2) 
                            <E T="03">Security Zone B.</E>
                             (i) 
                            <E T="03">Location.</E>
                             All waters within 500 yards of the U.S.S. John F. Kennedy (CV-67), in Federal Anchorage 21B. 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Enforcement period.</E>
                             Paragraph (a)(2)(i) of this section is enforced from 10 a.m., e.s.t. until 5 p.m., e.s.t. on July 4, 2000. 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Effective period.</E>
                             This section is applicable from 7 a.m., e.s.t. on July 4, 2000, until 5 p.m., e.s.t. on July 4, 2000. 
                        </P>
                        <P>(c) All persons and vessels shall comply with the instructions of the Coast Guard Captain of the Port or the designated on-scene-patrol personnel. These personnel comprise commissioned, warrant, and petty officers of the Coast Guard. Upon being hailed by a U.S. Coast Guard vessel by siren, radio, flashing light, or other means, the operator of a vessel shall proceed as directed. </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: May 4, 2000. </DATED>
                    <NAME>Robert F. Duncan, </NAME>
                    <TITLE>Captain, U.S. Coast Guard, Acting Commander, First Coast Guard District. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-12641 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-15-U </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Coast Guard </SUBAGY>
                <CFR>33 CFR Part 165 </CFR>
                <DEPDOC>[COTP MIAMI 00-015] </DEPDOC>
                <RIN>RIN 2115-AA97 </RIN>
                <SUBJECT>Safety Zone: OpSail Miami 2000, Port of Miami.</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is establishing temporary regulations in the Port of Miami for OpSail Miami 2000 activities. This action is necessary to provide for the safety of life and property on navigable waters during OpSail Miami 2000. This action will restrict vessel traffic in portions of the Port of Miami. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective from 9 p.m. Eastern Daylight Time (EDT) on June 9, 2000 and terminates at 4 p.m. EDT on June 10, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Coast Guard Marine Safety Office Miami maintains the public docket for this rulemaking. Documents indicated in this preamble as being available in the docket, are available for inspection or copying at room 201, Coast Guard Marine Safety Office Miami, between 8 a.m. and 3 p.m., EDT Monday through Friday, except Federal holidays. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lieutenant Joseph Boudrow, Port Management and Response Department, Coast Guard Marine Safety Office Miami, (305) 535-8705. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Regulatory Information </HD>
                <P>
                    On December 17, 1999, the Coast Guard published an advanced notice of proposed rulemaking (ANPRM), and on March 17, 2000, the Coast Guard published a notice of proposed rulemaking (NPRM) entitled OPSAIL 2000 in the 
                    <E T="04">Federal Register</E>
                     (64 FR 70650 and 65 FR 14502). No comments were received during either comment period. No public hearing was requested and none was held. 
                </P>
                <P>
                    Under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    . Updated information regarding the fireworks display was recently received from the sponsor. Further, the proposed rule was well publicized in the ANPRM and the NPRM, and the event will be further publicized throughout the local community by the event sponsor. 
                </P>
                <HD SOURCE="HD1">Background and Purpose </HD>
                <P>The temporary regulations are for OpSail Miami 2000 events scheduled to be held in portions of the Port of Miami over the period of June 6-10, 2000. This rule will provide for the safety of life and property on navigable waters during OpSail Miami 2000 events on June 9, 2000 and June 10, 2000. </P>
                <HD SOURCE="HD1">Discussion of Rule </HD>
                <P>OpSail Miami 2000, Inc., is sponsoring OpSail Miami 2000 activities which consist of the arrival, display, and departure parade of numerous large U. S. and foreign flagged sail vessels. A fireworks display is planned for the evening prior to the final day of the sail vessel visit. Currently, approximately 20 Class A (175 feet or larger in length) and 20 smaller Class B (100 feet up to 175 feet) and C (up to 100 feet) sail vessels are expected to participate in OpSail Miami 2000. </P>
                <P>Participant sail vessels will begin arriving in the Port of Miami on June 6, 2000 and will moor alongside Dodge Island within the Port of Miami. These vessels will be open to the public during certain hours between June 7 and June 9, 2000. On June 9, 2000, fireworks displays will be conducted commencing approximately 9:00 p.m. EDT from the orchestra vessel POINT COUNTERPOINT II, a barge anchored in the turning basin at the west end of Main Channel, and the Watson Island bridge structure. On June 10, 2000, the sail vessels will make their departure from the Port of Miami in a parade commencing approximately 12 noon EDT and ending approximately 4 p.m. EDT. Participant sail vessels will proceed under auxiliary power from their moorings to the turning basin at the west end of the Main Channel. From the turning basin, they will proceed under auxiliary power in 300 to 500 yard intervals in a ocean-bound direction along the Main Channel, thence along Government Cut, thence along Bar Cut, thence along Outer Bar Cut, to the vicinity of Miami Lighted Bouy M (Light List Number (LLNR) 10455-895), located at 25 degrees, 46.0 minutes North latitude, 080 degrees, 05.0 minutes West longitude. The area of Miami Lighted Buoy M is the termination point for pilotage. As pilots disembark their vessels, the sail vessels will parade northward off the coastline, under sail, to the parade termination point in the general vicinity of the entrance to Port Everglades, Florida. </P>
                <P>Waterborne spectator areas have been designated by the event sponsor to be on either side of Bar Cut and Outer Bar Cut in the open ocean. These areas will be delineated by lines of marker floats placed by the sponsor. The marker floats will be round balls, orange in color, and spaced approximately 200 yards apart. They will be placed 100 yards out from the aids to navigation that mark each side of the channel. Spectator craft will be expected to remain behind the marker float lines for the duration of the parade. </P>
                <P>Because of the number of the sail vessels, fireworks displays, and the large number of spectator watercraft expected during the parade, the Coast Guard is establishing regulations for the creation of temporary safety zones and vessel movement controls in portions of the Port of Miami and its channels affected by these events. The regulations will be in effect on June 9 and 10, 2000. The vessel congestion due to the large number of participant and spectator vessels poses a significant threat to the safety of life and property. The Coast Guard has determined this rulemaking is necessary to ensure the safety of life and property on the navigable waters of the United States within portions of the Port of Miami affected by this event. </P>
                <HD SOURCE="HD1">Regulated Areas </HD>
                <P>
                    The Coast Guard is establishing temporary safety zones for fireworks displays on June 9, 2000 and the Parade of Sail on June 10, 2000. The safety zone for June 9, 2000 shall include all waters within 100 yards of the orchestra vessel 
                    <PRTPAGE P="33771"/>
                    POINT COUNTERPOINT II, and all waters bounded on the north by the Venetian Causeway West drawbridge, a line drawn from the southwest corner of Biscayne Island to the northwest corner of Watson Island, and a line drawn from the southwest corner of Watson Island near the seaplane ramp to the northeast corner of the American Airlines Arena property water frontage. 
                </P>
                <P>The safety zone for the June 10, 2000, Parade of Sail shall include all waters in the Port of Miami within the turning basin at the west end of Main Channel bounded by the bridges connecting Dodge Island and Watson Island to the mainland, the Main Channel, Lummus Island Cut east of a line drawn northward from the west end of Fisher Island, Government Cut, Bar Cut, Outer Bar Cut, and 100 yards on either side of the Bar Cut and Outer Bar Cut short range navigational aids, seaward to Miami Lighted Buoy M (LLNR 10455-895). </P>
                <P>Entry into these safety zones by non-participating vessels will be prohibited. The Coast Guard expects many spectator craft for this millennium event. These craft will be allowed to view the Parade of Sail vessels from viewing areas on either side of Bar Cut and Outer Bar Cut. These areas will delineated by marker floats placed by the sponsor of the event. </P>
                <HD SOURCE="HD1">Regulatory Evaluation </HD>
                <P>This rule is not a “significant regulatory action” under section 3(f) of Executive Order 12866 and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order. It is not significant under the regulatory policies and procedures of the Department of Transportation (DOT) (44 FR 11040; February 26, 1979). </P>
                <P>Although the rule prohibits all non-parade related traffic in the area of the temporary safety zone on Saturday, June 10, 2000, the effect of this regulation will not be significant for the following reasons: the regulation will be in effect for less than 6 hours; the maritime community will receive extensive advance notices through Local Notices to Mariners, facsimile, and marine information broadcasts, maritime association meetings, and Miami area newspapers; and specific viewing areas will be marked for spectator vessels. </P>
                <HD SOURCE="HD1">Small Entities </HD>
                <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we considered whether this 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 Coast Guard certifies under 5 U.S.C. 605(b) that this rule would not have a significant economic impact on a substantial number of small entities. We received no comments on this rule from small entities. However, this rule would affect the following entities, some of which might be small entities: the owners or operators of vessels intending to transit those portions of the Port of Miami during the two periods of safety zone enforcement. These regulations would not have a significant economic impact on a substantial number of small entities for the following reasons. Although these regulations would apply to a substantial portion of the Port of Miami, the periods of the regulatory enforcement will be of short duration. Before the effective periods, the Coast Guard will make notifications to the public via mailings, facsimilies, the Local Notice to Mariners, and use of the sponsor Internet site. In addition, OpSail Miami 2000, Inc., the sponsoring organization, is planning to publish information of the event in local newspapers, pamphlets, and television and radio broadcasts. </P>
                <HD SOURCE="HD1">Assistance for Small Entities </HD>
                <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we will 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 rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact Lieutenant Joe Boudrow, Coast Guard Marine Safety Office Miami at (305) 535-8705. </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="HD1">Collection of Information </HD>
                <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520). </P>
                <HD SOURCE="HD1">Federalism </HD>
                <P>We have analyzed this rule under Executive Order 13132 and have determined that this rule does not have implications for federalism under that order. </P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act </HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) governs the issuance of Federal regulations that require unfunded mandates. An unfunded mandate is a regulation that requires a State, local, or tribal government or the private sector to incur direct costs without the Federal Government's having first provided the funds to pay those costs. This rule would not impose on unfunded mandate. </P>
                <HD SOURCE="HD1">Taking of Private Property </HD>
                <P>This rule would not effect a taking of private property or otherwise have taking implications under E.O. 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights. </P>
                <HD SOURCE="HD1">Civil Justice Reform </HD>
                <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of E.O. 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden. </P>
                <HD SOURCE="HD1">Protection of Children </HD>
                <P>The Coast Guard has analyzed this rule under E.O. 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not concern an environmental risk to health or risk to safety that may disproportionately affect children. </P>
                <HD SOURCE="HD1">Environment </HD>
                <P>
                    We considered the environmental impact of this action and have determined under Figure 2-1, paragraph 34(g) of Commandant Instruction M16475.1C, that this rule is categorically excluded from further environmental documentation. A Categorical Exclusion Determination is available in the docket where indicated under 
                    <E T="02">ADDRESSES.</E>
                     By controlling vessel traffic during the event, this rule is intended to minimize environmental impacts of increased vessel traffic during the parade of sail. 
                </P>
                <LSTSUB>
                    <PRTPAGE P="33772"/>
                    <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>
                <REGTEXT TITLE="33" PART="165">
                    <HD SOURCE="HD1">Temporary Regulations</HD>
                    <AMDPAR>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR Part 165, as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 165—[AMENDED] </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for Part 165 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>33 U.S.C. 1231; 50 U.S.C. 191; 33 CFR 1.05-1(g), 6.04-1, 6.04-6, and 160.5; 49 CFR 1.46. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. A temporary § 165.T 07-015 is added to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T07-015 </SECTNO>
                        <SUBJECT>Safety zones; Miami, Florida. </SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Regulated areas.</E>
                             (1) 
                            <E T="03">Fireworks area.</E>
                             (i) 
                            <E T="03">Location.</E>
                             All waters within 100 yards of the M/V POINT COUNTERPOINT II; and, all waters within an area bounded on the north by the Venetian Causeway West drawbridge, a line drawn from the southwest corner of Biscayne Island to the northwest corner of Watson Island, and a line drawn from the southwest corner of Watson Island near the seaplane ramp to the northeast corner of the American Airlines Arena property water frontage. 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Regulations.</E>
                             In accordance with the general regulations in 165.23 of this part, no vessel shall enter the fireworks display fallout area during the enforcement period unless otherwise authorized by the U.S. Coast Guard Captain of the Port. 
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Enforcement period.</E>
                             This section becomes effective at 9 p.m. Eastern Daylight Time (EDT) and terminates at 11 p.m. EDT on June 9, 2000, unless terminated earlier by the U. S. Coast Guard Captain of the Port. 
                        </P>
                        <P>
                            (2) 
                            <E T="03">Parade of sail area.</E>
                            —(i) 
                            <E T="03">Location.</E>
                             A temporary safety zone is established to include all waters in the Port of Miami within the turning basin at the west end of Main Channel bounded by the bridges connecting Dodge and Watson Islands with the mainland, Main Channel, Lummus Island Cut east of a line extending northward from the west end of Fisher Island, Government Cut, Bar Cut, Outer Bar Cut, and 100 yards on either side of the Bar Cut and Outer Bar Cut short range navigational aids, seaward to Miami Lighted Buoy M (LLNR 10455-895). 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Regulations.</E>
                             In accordance with the general regulations in 165.23 of this part, entry into this zone is prohibited to all non-parade related vessels without the prior permission of the U. S. Coast Guard Captain of the Port. 
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Enforcement period.</E>
                             This section becomes effective at 10 a.m. EDT and terminates at 4 p.m. EDT on June 10, 2000, unless terminated earlier by the U.S. Coast Guard Captain of the Port. 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Dates.</E>
                             This section becomes effective at 9 p.m., EDT on June 9, 2000, and terminates at 4 p.m., EDT on June 10, 2000. 
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: May 17, 2000. </DATED>
                    <NAME>L.J. Bowling, </NAME>
                    <TITLE>Captain, U. S. Coast Guard, Captain of the Port, Miami Zone. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13195 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-15-U </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <CFR>40 CFR Part 52 </CFR>
                <DEPDOC>[OR 76-7291; FRL-6601-1] </DEPDOC>
                <SUBJECT>Approval and Promulgation of Implementation Plans: Oregon </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Pursuant to procedures described in the January 19, 1989 
                        <E T="04">Federal Register</E>
                        , the Environmental Protection Agency (EPA or we) recently approved a minor State Implementation Plan (SIP) revision submitted by the Oregon Department of Environmental Quality (ODEQ). This submittal includes the following changes to the Oregon Administrative Rules (OAR) 340-028-0110 (Definitions): a revision of the definition of Volatile Organic Compounds (VOC), typographical corrections, updated reference dates, and the renumbering of several definitions. The VOC definition was revised to delist parachlorobenzotriflouride (PCBTF) and cyclic, branched, or linear completely methylated siloxanes from the definition of VOC. This document lists the revision we approved and incorporates the relevant material into the Code of Federal Regulations.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective May 25, 2000.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Documents which are incorporated by reference are available for public inspection at the Air and Radiation Docket and Information Center, Environmental Protection Agency, 401 M Street SW, Washington, D.C. 20460. Copies of material submitted to EPA and other information supporting this action may be examined during normal business hours at the following locations: EPA, Region 10, Office of Air Quality (OAQ-107), 1200 Sixth Avenue, Seattle, Washington 98101 and Oregon Department of Environmental Quality, 811 SW Sixth Avenue, Portland, Oregon 97204-1390.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Debra Suzuki, EPA, Office of Air Quality (OAQ-107), 1200 Sixth Avenue, Seattle, Washington 98101, (206) 553-0985.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>We approved the following minor SIP revision request under section 110(a) of the Clean Air Act (Act):</P>
                <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="xs40,r150,15C,15C">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">State </CHED>
                        <CHED H="1">Subject matter </CHED>
                        <CHED H="1">
                            Date of 
                            <LI>submission </LI>
                        </CHED>
                        <CHED H="1">
                            Date of 
                            <LI>approval </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">OR </ENT>
                        <ENT>Definitions: Revised the definition of VOC (delist parachlorobenzotriflouride (PCBTF) and cyclic, branched, or linear completely methylated siloxanes) consistent with changes in the federal definition, made typographical corrections, updated reference dates, and incorporated the renumbering of several definitions </ENT>
                        <ENT>12-3-98 </ENT>
                        <ENT>6-16-99 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    We took no action on the definitions relating to the Compliance Assurance Monitoring (CAM) Rule and on Tables 1 through 3. Please note that since these SIP revisions were adopted by the state, other modifications to Oregon's rules may have been adopted by the Environmental Quality Commission and submitted to EPA for approval (
                    <E T="03">e.g.</E>
                     the rule recodification package). Approval of this SIP revision does not rescind any local rule amendments that were subsequently filed and submitted. We determined that this SIP revision complies with all applicable requirements of the Act and EPA policy and regulations concerning such revisions. Due to the minor nature of this revision, we concluded that conducting notice-and-comment rulemaking prior to approving this 
                    <PRTPAGE P="33773"/>
                    revision would have been “unnecessary and contrary to the public interest”, and therefore, was not required by the Administrative Procedure Act, 5 U.S.C. 553(b). This SIP approval became final and effective on the date of EPA approval listed above. 
                </P>
                <HD SOURCE="HD1">I. Administrative Requirements</HD>
                <HD SOURCE="HD2">A. Executive Order 12866</HD>
                <P>
                    A. Under Executive Order 12866 (58 FR 51735, October 4, 1993), this action is not a “significant regulatory action” and therefore is not subject to review by the Office of Management and Budget. This action merely approves state law as meeting federal requirements and imposes no additional requirements beyond those imposed by state law. Accordingly, the Administrator certifies that this rule will not have a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ). Because this rule approves pre-existing requirements under state law and does not impose any additional enforceable duty beyond that required by state law, it does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Public Law 104-4). For the same reason, this rule also does not significantly or uniquely affect the communities of tribal governments, as specified by Executive Order 13084 (63 FR 27655, May 10, 1998). This rule will not have substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government, as specified in Executive Order 13132 (64 FR 43255, August 10, 1999), because it merely approves a state rule implementing a federal standard, and does not alter the relationship or the distribution of power and responsibilities established in the Clean Air Act. This rule also is not subject to Executive Order 13045 (62 FR 19885, April 23, 1997), because it is not economically significant. 
                </P>
                <P>
                    In reviewing SIP submissions, EPA's role is to approve state choices, provided that they meet the criteria of the Clean Air Act. In this context, in the absence of a prior existing requirement for the State to use voluntary consensus standards (VCS), EPA has no authority to disapprove a SIP submission for failure to use VCS. It would thus be inconsistent with applicable law for EPA, when it reviews a SIP submission, to use VCS in place of a SIP submission that otherwise satisfies the provisions of the Clean Air Act. 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. As required by section 3 of Executive Order 12988 (61 FR 4729, February 7, 1996), 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. EPA has complied with Executive Order 12630 (53 FR 8859, March 15, 1988) 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 provisions of 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. 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>
                    . A major rule cannot take effect until 60 days after it is published in the 
                    <E T="04">Federal Register</E>
                    . This action is not a “major rule” as defined by 5 U.S.C. 804(2). This rule became effective on June 16, 1999.
                </P>
                <P>Under section 307(b)(1) of the Clean Air Act, petitions for judicial review of this action must be filed in the United States Court of Appeals for the appropriate circuit by July 24, 2000. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this rule for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. This action may not be challenged later in proceedings to enforce its requirements. (See section 307(b)(2).) </P>
                <HD SOURCE="HD2">B. Oregon Notice Provision </HD>
                <P>During EPA's review of a SIP revision involving Oregon's statutory authority, a problem was detected which affected the enforceability of point source permit limitations. EPA determined that, because the five-day advance notice provision required by ORS 468.126(1) (1991) bars civil penalties from being imposed for certain permit violations, ORS 468 fails to provide the adequate enforcement authority that a state must demonstrate to obtain SIP approval, as specified in section 110 of the Clean Air Act and 40 CFR 51.230. Accordingly, the requirement to provide such notice would preclude federal approval of a section 110 SIP revision.</P>
                <P>To correct the problem the Governor of Oregon signed into law new legislation amending ORS 468.126 on September 3, 1993. This amendment added paragraph ORS 468.126(2)(e) which provides that the five-day advance notice required by ORS 468.126(1) does not apply if the notice requirement will disqualify a state program from federal approval or delegation. ODEQ responded to EPA's understanding of the application of ORS 468.126(2)(e) and agreed that, because federal statutory requirements preclude the use of the five-day advance notice provision, no advance notice will be required for violations of SIP requirements contained in permits.</P>
                <HD SOURCE="HD2">C. Oregon Audit Privilege </HD>
                <P>Another enforcement issue concerns Oregon's audit privilege and immunity law. Nothing in this action should be construed as making any determination or expressing any position regarding Oregon's Audit Privilege Act, ORS 468.963 enacted in 1993, or its impact upon any approved provision in the SIP, including the revision at issue here. The action taken herein does not express or imply any viewpoint on the question of whether there are legal deficiencies in this or any other Clean Air Act Program resulting from the effect of Oregon's audit privilege and immunity law. A state audit privilege and immunity law can affect only state enforcement and cannot have any impact on federal enforcement authorities. EPA may at any time invoke its authority under the Clean Air Act, including, for example, sections 113, 167, 205, 211 or 213, to enforce the requirements or prohibitions of the state plan, independently of any state enforcement effort. In addition, citizen enforcement under section 304 of the Clean Air Act is likewise unaffected by a state audit privilege or immunity law. </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, Volatile organic compounds.</P>
                </LSTSUB>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>Incorporation by reference of the Implementation Plan for the State of Oregon was approved by the Director of the Office of Federal Register on July 1, 1982.</P>
                </NOTE>
                <SIG>
                    <PRTPAGE P="33774"/>
                    <DATED>Dated: March 16, 2000.</DATED>
                    <NAME>Chuck Clarke, </NAME>
                    <TITLE>Regional Administrator, Region 10. </TITLE>
                </SIG>
                <REGTEXT TITLE="40" PART="52">
                    <AMDPAR>Part 52, chapter I, title 40 of the Code of Federal Regulations is amended as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 52—[AMENDED] </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for Part 52 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            42 U.S.C. 7401 
                            <E T="03">et seq.</E>
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="52">
                    <SUBPART>
                        <HD SOURCE="HED">Subpart MM—Oregon </HD>
                    </SUBPART>
                    <AMDPAR>2. Section 52.1970 is amended by adding paragraph (c) (131) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 52.1970 </SECTNO>
                        <SUBJECT>Identification of plan. </SUBJECT>
                        <STARS/>
                        <P>(c) * * * </P>
                        <P>(131) On December 3, 1998, the Director of the Oregon Department of Environmental Quality (ODEQ) submitted a revision to the definition section of the Oregon Administrative Rules (OAR), as effective October 14, 1998. </P>
                        <P>(i) Incorporation by reference. </P>
                        <P>(A) OAR 340-028-0110, as effective October 14, 1998, except for the following: (16) Capture system, (25) Continuous compliance determination method, (27) Control device, (29) Data, (39)(b) Emission Limitation and Emission Standard, (47) Exceedance, (48) Excursion, (55) Inherent process equipment, (67) Monitoring, (86) Pollutant-specific emissions unit, (88) Predictive emission monitoring system (PEMS), Table 1, Table 2, and Table 3. </P>
                        <P>(B) Remove the following provision from the current incorporation by reference: OAR 340-028-0110, as effective October 6, 1995, except for Table 1, Table 2, and Table 3.</P>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13070 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <CFR>40 CFR Part 271 </CFR>
                <DEPDOC>[FRL-6704-7] </DEPDOC>
                <SUBJECT>Minnesota: Final Authorization of State Hazardous Waste Management Program Revisions </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Immediate final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Minnesota has applied to EPA for Final authorization of the changes to its hazardous waste program under the Resource Conservation and Recovery Act (RCRA). EPA has determined that these changes satisfy all requirements needed to qualify for Final authorization, and is authorizing the State's changes through this immediate final action. EPA is publishing this rule to authorize the changes without a prior proposal because we believe this action is not controversial and do not expect comments that oppose it. Unless we get written comments which oppose this authorization during the comment period, the decision to authorize Minnesota's changes to their hazardous waste program will take effect as provided below. If we get comments that oppose this action, we will publish a document in the 
                        <E T="04">Federal Register</E>
                         withdrawing this rule before it takes effect and a separate document in the proposed rules section of this 
                        <E T="04">Federal Register</E>
                         will serve as a proposal to authorize the changes. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        This Final authorization will become effective on August 23, 2000 unless EPA receives adverse written comment by June 26, 2000. If EPA receives such comment, it will publish a timely withdrawal of this immediate final rule in the 
                        <E T="04">Federal Register</E>
                         and inform the public that this authorization will not take effect. 
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send written comments referring to Docket Number Minnesota ARA 8, to Gary Westefer, Minnesota Regulatory Specialist, U.S. EPA Region 5, DM-7J, 77 West Jackson Boulevard, Chicago, Illinois 60604, (312) 886-7450. We must receive your comments by June 26, 2000. You can view and copy Minnesota's application from 9:00 am to 4:00 pm at the following addresses: Minnesota Pollution Control Agency, 520 Lafayette Road, North, St. Paul, Minnesota 55155, contact Nathan Cooley at (651) 297-7544; or EPA Region 5, contact Gary Westefer at the following address. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Gary Westefer, Minnesota Regulatory Specialist, U.S. EPA Region 5, DM-7J, 77 West Jackson Boulevard, Chicago, Illinois 60604, (312) 886-7450. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">A. Why Are Revisions to State Programs Necessary? </HD>
                <P>States which have received final authorization from EPA under RCRA section 3006(b), 42 U.S.C. 6926(b), must maintain a hazardous waste program that is equivalent to, consistent with, and no less stringent than the Federal program. As the Federal program changes, States must change their programs and ask EPA to authorize the changes. Changes to State programs may be necessary when Federal or State statutory or regulatory authority is modified or when certain other changes occur. Most commonly, States must change their programs because of changes to EPA's regulations in 40 Code of Federal Regulations (CFR) parts 124, 260 through 266, 268, 270, 273 and 279. </P>
                <HD SOURCE="HD1">B. What Decisions Have We Made in This Rule? </HD>
                <P>We conclude that Minnesota's application to revise its authorized program meets all of the statutory and regulatory requirements established by RCRA. Therefore, we grant Minnesota Final authorization to operate its hazardous waste program with the changes described in the authorization application. Minnesota has responsibility for permitting Treatment, Storage, and Disposal Facilities (TSDFs) within its borders (except in Indian Country) and for carrying out the aspects of the RCRA program described in its revised program application, subject to the limitations of the Hazardous and Solid Waste Amendments of 1984 (HSWA). New federal requirements and prohibitions imposed by Federal regulations that EPA promulgates under the authority of HSWA take effect in authorized States before they are authorized for the requirements. Thus, EPA will implement those requirements and prohibitions in Minnesota, including issuing permits, until the State is granted authorization to do so. </P>
                <HD SOURCE="HD1">C. What Is the Effect of Today's Authorization Decision? </HD>
                <P>The effect of this decision is that a facility in Minnesota subject to RCRA will now have to comply with the authorized State requirements instead of the equivalent federal requirements in order to comply with RCRA. Minnesota has enforcement responsibilities under its state hazardous waste program for violations of such program, but EPA maintains independent authority under RCRA sections 3007, 3008, 3013, and 7003, which include, among others, the authority to conduct inspections and require monitoring, tests, analyses or reports and to enforce RCRA requirements and suspend or revoke permits. </P>
                <P>
                    This action does not impose additional requirements on the regulated community because the regulations for which Minnesota is being authorized by today's action are already effective, and are not changed by today's action. 
                    <PRTPAGE P="33775"/>
                </P>
                <HD SOURCE="HD1">D. Why Wasn't There a Proposed Rule Before Today's Rule? </HD>
                <P>
                    EPA did not publish a proposal before today's rule because we view this as a routine program change and do not expect comments that oppose this approval. We are providing an opportunity for public comment now. In addition to this rule, in the proposed rules section of today's 
                    <E T="04">Federal Register</E>
                    , we are publishing a separate document that proposes to authorize the state program changes. 
                </P>
                <HD SOURCE="HD1">E. What Happens If EPA Receives Comments That Oppose This Action? </HD>
                <P>
                    If EPA receives appropriate comments that oppose this authorization, we will withdraw this rule by publishing a document in the 
                    <E T="04">Federal Register</E>
                     before the rule becomes effective. EPA will base any further decision on the authorization of the state program changes on the proposal mentioned in the previous paragraph. We will then address all public comments in a later final rule. You may not have another opportunity to comment. If you want to comment on this authorization, you must do so at this time. 
                </P>
                <P>
                    If we receive comments that oppose only the authorization of a particular change to the State hazardous waste program, we will withdraw that part of this rule, but the authorization of the program changes that the comments do not oppose will become effective on the date specified above. The 
                    <E T="04">Federal Register</E>
                     withdrawal document will specify which part of the authorization will become effective, and which part is being withdrawn. 
                </P>
                <HD SOURCE="HD1">F. What Has Minnesota Previously Been Authorized For? </HD>
                <P>Minnesota initially received Final authorization on January 28, 1985, effective February 11, 1985 (50 FR 3756), to implement the RCRA hazardous waste management program. We granted authorization for changes to their program on July 20, 1987, effective September 18, 1987 (52 FR 27199), on April 24, 1989, effective June 23, 1989 (54 FR 16361), amended June 28, 1989 (54 FR 27170), on June 15, 1990, effective August 14, 1990 (55 FR 24232), on June 24, 1991, effective August 23, 1991 (56 FR 28709), on March 19, 1992, effective May 18, 1992 (57 FR 9501), on March 17, 1993, effective May 17, 1993 (58 FR 14321), and on January 20, 1994, effective March 21, 1994 (59 FR 2998). </P>
                <HD SOURCE="HD1">G. What Changes Are We Authorizing With Today's Action? </HD>
                <P>On March 7, 2000, Minnesota submitted a final complete program revision application, seeking authorization of program changes in accordance with 40 CFR 271.21. EPA reviewed Minnesota's application, and we now make an immediate final decision, subject to receipt of adverse written comments that oppose this action, that Minnesota's hazardous waste program revision satisfies all of the requirements necessary to qualify for Final authorization. Therefore, we grant Minnesota Final authorization for the following program changes: </P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s75,r75,r75">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Description of Federal requirement </CHED>
                        <CHED H="1">
                            <E T="02">Federal Register</E>
                             date and page 
                            <E T="03">[and/or RCRA statutory authority]</E>
                        </CHED>
                        <CHED H="1">Analogous State authority </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Petroleum Refinery Primary and Secondary Oil/Water/Solids Separation Sludge Listings (F037 and F038) Checklist 81 as amended Checklist 81.1</ENT>
                        <ENT>
                            November 2, 1990, 55 FR 46354 
                            <LI O="xl">December 17, 1990, 55 FR 51707 </LI>
                        </ENT>
                        <ENT>Minnesota Rules 7045.0135, 7045.0139; effective March 1, 1994. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wood Preserving Listings Checklist 82 </ENT>
                        <ENT>December 6, 1990, 55 FR 50450 </ENT>
                        <ENT>Minnesota Rules 7045.0020, 7045.0120, 7045.0135, 7045.0139, 7045.0141, 7045.0145, 7045.0292, 7045.0528, 7045.0541, 7045.0552, 7045.0623, 7045.0628, 7045.0644; effective January 31, 1994, as amended October 2, 1995. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Organic Air Emission Standards for Process Vents and Equipment Leaks; Technical Amendment Checklist 87 </ENT>
                        <ENT>April 26, 1991, 56 FR 19290 </ENT>
                        <ENT>Minnesota Rules 7001.0625, 7001.0626, 7045.0547, 7045.0548, 7045.0564, 7045.0584, 7045.0647, 7045.0648; effective March 1, 1994. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Revision to F037 and F038 Listings Checklist 89 </ENT>
                        <ENT>May 13, 1991, 56 FR 21955 </ENT>
                        <ENT>Minnesota Rules 7045.0135 effective March 1, 1994. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wood Preserving Listing: Technical Correction Checklist 92 </ENT>
                        <ENT>July 1, 1991, 56 FR 30192 </ENT>
                        <ENT>Minnesota Rules 7001.0623 7045.0120, 7045.0145, 7045.0292, 7045.0541, 7045.0644; effective January 31, 1994 as amended October 2, 1995. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Second Correction to the Third Third Land Disposal Restrictions Checklist 102 </ENT>
                        <ENT>March 6, 1992, 57 FR 8086 </ENT>
                        <ENT>Minnesota Rules 7045.0458, 7045.0564, 7045.1305, 7045.1355, 7045.1360; effective March 1, 1994. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hazardous Debris Case-by-Case Capacity Variance Checklist 103 </ENT>
                        <ENT>May 15, 1992, 57 FR 20766 </ENT>
                        <ENT>Minnesota Rules 7045.1335; effective March 1, 1994. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lead-Bearing Hazardous Materials Case-by-Case Capacity Variance Checklist 106 </ENT>
                        <ENT>June 26, 1992, 57 FR 28628 </ENT>
                        <ENT>Minnesota Rules 7045.1335; effective March 1, 1994. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wood Preserving: Amendments to Listings and Technical Requirements Checklist 120 </ENT>
                        <ENT>December 24, 1992, 57 FR 61492 </ENT>
                        <ENT>Minnesota Rules 7045.0541, 7045.0644; effective January 31, 1994, as amended October 2, 1995. </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">H. Where Are the Revised State Rules Different From the Federal Rules? </HD>
                <P>In the changes currently being made to Minnesota's program, we consider the following State requirement to be more stringent than the Federal requirements: </P>
                <P>• Minnesota Rules 7001.0623, because the State does not allow for an exemption to Subpart F of 40 CFR part 264, as provided for in 40 CFR 270.26(b), making the State requirements more stringent.</P>
                <FP>More stringent rules are part of Minnesota's authorized program and are Federally enforceable. </FP>
                <P>
                    Broader-in-scope requirements are not part of the authorized program and EPA cannot enforce them. Although you must comply with these requirements in accordance with state law, they are not RCRA requirements. There are no broader-in-scope provisions in these changes. 
                    <PRTPAGE P="33776"/>
                </P>
                <HD SOURCE="HD1">I. Who Handles Permits After This Authorization Takes Effect? </HD>
                <P>Minnesota will issue permits for all the provisions for which it is authorized, and will administer the permits that it issues. EPA will continue to administer any RCRA hazardous waste permits, or portions of permits, that we issued prior to the effective date of this authorization until they expire or are terminated. We will not issue any more new permits or portions of permits for the provisions listed in the Table above after the effective date of this authorization. EPA will continue to implement and issue permits for HSWA requirements for which Minnesota is not yet authorized. </P>
                <HD SOURCE="HD1">J. How Does Today's Action Affect Indian Country (18 U.S.C. 1151) in Minnesota? </HD>
                <P>Minnesota is not authorized to carry out its hazardous waste program in Indian country within the State, as defined in 18 U.S.C. 1151. This includes: </P>
                <P>1. All lands within the exterior boundaries of the following Indian Reservations, located within or abutting the State of Minnesota: </P>
                <FP SOURCE="FP-1">a. Bois Forte Indian Reservation </FP>
                <FP SOURCE="FP-1">b. Fond Du Lac Indian Reservation </FP>
                <FP SOURCE="FP-1">c. Grand Portage Indian Reservation </FP>
                <FP SOURCE="FP-1">d. Leech Lake Indian Reservation </FP>
                <FP SOURCE="FP-1">e. Lower Sioux Indian Reservation </FP>
                <FP SOURCE="FP-1">f. Mille Lacs Indian Reservation </FP>
                <FP SOURCE="FP-1">g. Prairie Island Indian Reservation </FP>
                <FP SOURCE="FP-1">h. Red Lake Indian Reservation </FP>
                <FP SOURCE="FP-1">i. Shakopee Mdewankanton Indian Reservation </FP>
                <FP SOURCE="FP-1">j. Upper Sioux Indian Reservation </FP>
                <FP SOURCE="FP-1">k. White Earth Indian Reservation</FP>
                <P>2. Any land held in trust by the U.S. for an Indian tribe, and </P>
                <P>3. Any other land, whether on or off a reservation that qualifies as Indian country. </P>
                <P>Therefore, this action has no effect in Indian country where EPA will continue to implement and administer the RCRA program in these lands. </P>
                <HD SOURCE="HD1">K. What Is Codification and Is EPA Codifying Minnesota's Hazardous Waste Program as Authorized in This Rule? </HD>
                <P>Codification is the process of placing the State's statutes and regulations that comprise the State's authorized hazardous waste program into the Code of Federal Regulations. We do this by referencing the authorized State rules in 40 CFR part 272. The authorized Minnesota RCRA program was incorporated by reference into 40 CFR part 272 on May 15, 1989, effective July 14, 1989 (54 FR 20851). Minnesota's Incorporation by Reference was amended on March 16, 1990, effective May 15, 1990 (55 FR 9880), on October 15, 1992, effective December 14, 1992 (57 FR 47265), and on September 6, 1994, effective November 7, 1994 (59 FR 45986). </P>
                <P>We reserve the amendment of 40 CFR part 272, subpart Y for this authorization of Minnesota's program changes until a later date. </P>
                <HD SOURCE="HD1">L. Regulatory Analysis and Notices </HD>
                <HD SOURCE="HD2">Unfunded Mandates Reform Act </HD>
                <P>Title II of the Unfunded Mandates Reform Act of 1995 (UMRA), Public Law 104-4, establishes requirements for Federal agencies to assess the effects of their regulatory actions on State, local, and tribal governments and the private sector. Under section 202 of the UMRA, EPA generally must prepare a written statement, including a cost-benefit analysis, for proposed and final rules with “Federal mandates” that may result in expenditures to State, local, and tribal governments, in the aggregate, or to the private sector, of $100 million or more in any one year. Before promulgating an EPA rule for which a written statement is needed, section 205 of the UMRA generally requires EPA to identify and consider a reasonable number of regulatory alternatives and adopt the least costly, most cost-effective or least burdensome alternative that achieves the objectives of the rule. The provisions of section 205 do not apply when they are inconsistent with applicable law. Moreover, section 205 allows EPA to adopt an alternative other than the least costly, most cost-effective or least burdensome alternative if the Administrator publishes with the final rule an explanation why that alternative was not adopted. Before EPA establishes any regulatory requirements that may significantly or uniquely affect small governments, including tribal governments, it must have developed under section 203 of the UMRA a small government agency plan. The plan must provide for notifying potentially affected small governments, enabling officials of affected small governments to have meaningful and timely input in the development of EPA regulatory proposals with significant Federal intergovernmental mandates, and informing, educating, and advising small governments on compliance with the regulatory requirements. </P>
                <P>EPA has determined that section 202 and 205 requirements do not apply to today's action because this rule does not contain a Federal mandate that may result in annual expenditures of $100 million or more for State, local, and/or tribal governments in the aggregate, or the private sector. Costs to State, local and/or tribal governments already exist under the Minnesota program, and today's action does not impose any additional obligations on regulated entities. In fact, EPA's approval of State programs generally may reduce, not increase, compliance costs for the private sector. Further, as it applies to the State, this action does not impose a Federal intergovernmental mandate because UMRA does not include duties arising from participation in a voluntary federal program. </P>
                <P>The requirements of section 203 of UMRA also do not apply to today's action because this rule contains no regulatory requirements that might significantly or uniquely affect small governments. Although small governments may be hazardous waste generators, transporters, or own and/or operate TSDFs, they are already subject to the regulatory requirements under the existing State laws that are being authorized by EPA, and, thus, are not subject to any additional significant or unique requirements by virtue of this program approval. </P>
                <HD SOURCE="HD2">Certification Under the Regulatory Flexibility Act (RFA), as Amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA), 5 U.S.C. 601 et seq. </HD>
                <P>The RFA generally requires an agency to prepare a regulatory flexibility analysis of any rule subject to notice and comment rulemaking requirements under the Administrative Procedure Act or any other statute, unless the agency certifies that the rule will not have a significant economic impact on a substantial number of small entities. Small entities include small businesses, small organizations, and small governmental jurisdictions. </P>
                <P>For purposes of assessing the impacts of today's action on small entities, small entity is defined as: (1) a small business as specified in the Small Business Administration regulations; (2) a small governmental jurisdiction that is a government of a city, county, town, school district or special district with a population of less than 50,000; and (3) a small organization that is any not-for-profit enterprise which is independently owned and operated and is not dominant in its field. </P>
                <P>
                    After considering the economic impacts of this authorization on small entities, I certify that this action will not have a significant economic impact on a substantial number of small entities. This action does not impose any new requirements on small entities because small entities that are hazardous waste 
                    <PRTPAGE P="33777"/>
                    generators, transporters, or that own and/or operate TSDFs are already subject to the regulatory requirements under the State laws which EPA is now authorizing. This action merely authorizes, for the purpose of RCRA section 3006, those existing State requirements. 
                </P>
                <HD SOURCE="HD2">Submission to Congress and the Comptroller General </HD>
                <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. The 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 today's 
                    <E T="04">Federal Register</E>
                    . This rule is not a “major rule” as defined by 5 U.S.C. 804(2). 
                </P>
                <HD SOURCE="HD2">Compliance With Executive Order 12866 </HD>
                <P>The Office of Management and Budget has exempted this rule from the requirements of Executive Order 12866. </P>
                <HD SOURCE="HD2">Compliance With Executive Order 13132 (Federalism) </HD>
                <P>Executive Order 13132, entitled “Federalism” (64 FR 43255, August 10, 1999), requires EPA to develop an accountable process to ensure “meaningful and timely input by State and local officials in the development of regulatory policies that have federalism implications.” “Policies that have federalism implications” is defined in the Executive Order to include regulations that 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>
                <P>Under section 6 of Executive Order 13132, EPA may not issue a regulation that has federalism implications, that imposes substantial direct compliance costs, and that is not required by statute, unless the Federal government provides the funds necessary to pay the direct compliance costs incurred by State and local governments, or EPA consults with State and local officials early in the process of developing the proposed regulation. EPA also may not issue a regulation that has federalism implications and that preempts State law unless the Agency consults with State and local officials early in the process of developing the proposed regulation. </P>
                <P>This authorization does not have federalism implications. It will not have 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, as specified in Executive Order 13132, because this rule affects only one State. This action simply approves Minnesota's proposal to be authorized for updated requirements of the hazardous waste program that the State has voluntarily chosen to operate. Further, as a result of this action, newly authorized provisions of the State's program now apply in Minnesota in lieu of the equivalent Federal program provisions implemented by EPA under HSWA. Affected parties are subject only to those authorized State program provisions, as opposed to being subject to both Federal and State regulatory requirements. Thus, the requirements of section 6 of the Executive Order do not apply. </P>
                <HD SOURCE="HD2">Compliance With Executive Order 13045 </HD>
                <P>Executive Order 13045, “Protection of Children from Environmental Health Risks and Safety Risks,” applies to any rule that: (1) the Office of Management and Budget determines is “economically significant,” as defined under Executive Order 12866, and (2) concerns an environmental health or safety risk that EPA has reason to believe may have a disproportionate effect on children. If the regulatory action meets both criteria, the Agency must evaluate the environmental health or safety effects of the planned rule on children and explain why the planned regulation is preferable to other potentially effective and reasonably feasible alternatives considered by the Agency. </P>
                <P>EPA interprets Executive Order 13045 as applying only to those regulatory actions that are based on health or safety risks, such that the analysis required under section 5-501 of the Order has the potential to influence the regulation. This rule is not subject to Executive Order 13045 because it authorizes a State program. </P>
                <HD SOURCE="HD2">Compliance With Executive Order 13084 </HD>
                <P>Under Executive Order 13084, EPA may not issue a regulation that is not required by statute, that significantly or uniquely affects the communities of Indian tribal governments, and that imposes substantial direct compliance costs on those communities, unless the Federal government provides the funds necessary to pay the direct compliance costs incurred by the tribal governments, or EPA consults with those governments. If EPA complies with consulting, Executive Order 13084 requires EPA to provide to the Office of Management and Budget, in a separately identified section of the preamble to the rule, a description of the extent of EPA's prior consultation with representatives of affected tribal governments, a summary of the nature of their concerns, and a statement supporting the need to issue the regulation. In addition, Executive Order 13084 requires EPA to develop an effective process permitting elected officials and other representatives of Indian tribal governments “to provide meaningful and timely input in the development of regulatory policies on matters that significantly or uniquely affect their communities.” </P>
                <P>This rule is not subject to Executive Order 13084 because it does not significantly or uniquely affect the communities of Indian tribal governments. Minnesota is not authorized to implement the RCRA hazardous waste program in Indian country. This action has no effect on the hazardous waste program that EPA implements in the Indian country within the State. </P>
                <HD SOURCE="HD2">Paperwork Reduction Act </HD>
                <P>
                    Under the Paperwork Reduction Act, 44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    , Federal agencies must consider the paperwork burden imposed by any information request contained in a proposed rule or a final rule. This rule will not impose any information requirements upon the regulated community. 
                </P>
                <HD SOURCE="HD2">National Technology Transfer and Advancement Act </HD>
                <P>
                    Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (“NTTAA”), Public Law 104-113, 12(d) (15 U.S.C. 272 note) directs EPA to use voluntary consensus standards in its regulatory activities unless to do so would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are technical standards (
                    <E T="03">e.g.</E>
                    , materials specifications, test methods, sampling procedures, and business practices) that are developed or adopted by voluntary consensus standards bodies. The NTTAA directs EPA to provide Congress, through OMB, explanations when the Agency decides not to use available and applicable voluntary consensus standards. 
                    <PRTPAGE P="33778"/>
                </P>
                <P>This action does not involve technical standards. Therefore, EPA did not consider the use of any voluntary consensus standards. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 271 </HD>
                    <P>Environmental protection, Administrative practice and procedure, Confidential business information, Hazardous waste, Hazardous waste transportation, Indian lands, Intergovernmental relations, Penalties, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>This action is issued under the authority of sections 2002(a), 3006 and 7004(b) of the Solid Waste Disposal Act, as amended, 42 U.S.C. 6912(a), 6926, 6974(b). </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: May 3, 2000. </DATED>
                    <NAME>Elissa Speizman, </NAME>
                    <TITLE>Acting Regional Administrator, Region 5. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-12953 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">GENERAL SERVICES ADMINISTRATION </AGENCY>
                <CFR>41 CFR Part 102-36 </CFR>
                <DEPDOC>[FPMR Amendment H-205] </DEPDOC>
                <RIN>RIN 3090-AF39 </RIN>
                <SUBJECT>Disposition of Excess Personal Property; Correction </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Governmentwide Policy, GSA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; correction. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document corrects an error contained in a final rule appearing in Part III of the 
                        <E T="04">Federal Register</E>
                         of Tuesday, May 16, 2000 (64 FR 31218). The rule revised the Federal Property Management Regulations (FPMR) by moving coverage on the disposition of excess personal property into the Federal Management Regulation (FMR) and adding a cross-reference to the FPMR to direct readers to the coverage in the FMR. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>May 30, 2000. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Martha Caswell, Director, Personal Property Management Policy Division (MTP), 202-501-3828. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In rule document 00-11921 beginning on page 31218 in the issue of Tuesday, May 16, 2000, make the following correction: </P>
                <REGTEXT TITLE="41" PART="102">
                    <SECTION>
                        <SECTNO>§ 102-36.170 </SECTNO>
                        <SUBJECT>[Corrected] </SUBJECT>
                    </SECTION>
                    <AMDPAR>1. On page 31225, in the first column, in the second line, “in” should read “is”.</AMDPAR>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: May 19, 2000.</DATED>
                    <NAME>Sharon A. Kiser, </NAME>
                    <TITLE>Federal Acquisition Policy Division, Office of Governmentwide Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13147 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6820-24-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <CFR>47 CFR Part 73 </CFR>
                <DEPDOC>[DA 00-866; MM Docket No. 90-466; RM-7327, RM-7987, RM-7988, RM-8705]. </DEPDOC>
                <SUBJECT>Radio Broadcasting Services; Pleasanton, Bandera, Hondo, Hollywood Park, and Dilley, Texas</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; petition for reconsideration. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Commission dismisses as moot the Application for Review filed by Reding Broadcasting Company, requesting reconsideration of a dismissal of its proposal to substitute Channel 252A for Channel 253C2 at Pleasanton, TX, substitute Channel 253A for Channel 290A at Hondo, TX and Channel 252A for Channel 276A at Bandera, TX. Petitioner received requested relief in MM Docket No. 98-55. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Victoria M. McCauley, Mass Media Bureau, (202) 418-2180. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This is a synopsis of the Commission's Order, MM Docket No. 90-466 adopted April 12, 2000, and released April 14, 2000. The full text of this Commission decision is available for inspection and copying during normal business hours in the FCC Information Center (Room CY-A257), 445 12th Street, SW, Washington, DC. The complete text of this decision may also be purchased from the Commission's copy contractor, International Transcription Services, Inc., (202) 857-3800, 1231 20th Street, NW, Washington, DC 20036. </P>
                <SIG>
                    <FP>Federal Communications Commission. </FP>
                    <NAME>John A. Karousos,</NAME>
                    <TITLE> Chief, Allocations Branch, Policy and Rules Division, Mass Media Bureau. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13138 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6712-01-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <CFR>47 CFR Part 73 </CFR>
                <DEPDOC>[DA 00-945; MM Docket No. 99-83; RM-9500; RM-9722] </DEPDOC>
                <SUBJECT>Radio Broadcasting Services; Saranac Lake and Westport, NY </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Commission, at the request of Dana Puopolo, allots Channel 296A to Saranac Lake, NY, as the community's third local FM service. 
                        <E T="03">See</E>
                         64 FR 14422, March 25, 1999. At the request of Westport Broadcasting, the Commission substitutes Channel 275A for Channel 273A at Westport, NY, and modifies the license of Station WCLX to specify the alternate Class A channel. Channel 296A can be allotted to Saranac Lake in compliance with the Commission's minimum distance separation requirements, with respect to all domestic allotments, without the imposition of a site restriction, at coordinates 44-19-48 NL; 74-08-00 WL. Channel 275A can be allotted to Westport in compliance with the Commission's minimum distance separation requirements, with respect to all domestic allotments, with a site restriction of 4.6 kilometers (2.9 miles) northeast, at coordinates 44-13-16 NL; 73-24-42 WL, to accommodate WB's desired transmitter site. Both Saranac Lake and Westport are located within 320 kilometers (200 miles) of the U.S.-Canadian border and thus Canadian concurrence in the allotments is required. 
                        <E T="03">See</E>
                        <E T="02">Supplementary Information</E>
                        . 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective June 12, 2000. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Leslie K. Shapiro, Mass Media Bureau, (202) 418-2180. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a synopsis of the Commission's Report and Order, MM Docket No. 99-83, adopted April 19, 2000, and released April 28, 2000. The full text of this Commission decision is available for inspection and copying during normal business hours in the FCC Reference Center (Room 239), 445 12th Street, SW, Washington, DC. The complete text of this decision may also be purchased from the Commission's copy contractor, International Transcription Services, Inc., (202) 857-3800, 1231 20th Street, NW, Washington, DC 20036. In addition, Channel 296A at Saranac Lake will be short-spaced to Station CITE-FM, Channel 297C1, Montreal, Quebec, 
                    <PRTPAGE P="33779"/>
                    Canada, and Channel 275A at Westport will be short-spaced to Station CITE1, Channel 274C1, Sherbrooke, Quebec, Canada. Therefore, concurrence in these allotments, as specially-negotiated short-spaced allotments, was requested in October, 1999, but has not yet been received. However, rather than delay any further the opportunity to file applications for these channels, we will allot Channel 296A at Saranac Lake and Channel 275A at Westport at this time. If a construction permit is granted prior to the receipt of formal concurrence in the allotment by the Canadian Government, the construction permit will include the following condition: “Operation with the facilities specified herein is subject to modification, suspension, or termination without right to hearing, if found by the Commission to be necessary in order to conform to the Canada-United States FM Broadcast Agreement.” A filing window for Channel 296A at Saranac Lake will not be opened at this time. Instead, the issue of opening a filing window for this channel will be addressed by the Commission in a subsequent order. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Part 73 </HD>
                    <P>Radio broadcasting.</P>
                </LSTSUB>
                <REGTEXT TITLE="47" PART="73">
                    <AMDPAR>Part 73 of Title 47 of the Code of Federal Regulations is amended as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 73—[AMENDED] </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for Part 73 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>47 U.S.C. 154, 303, 334. 336. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="74" PART="73">
                    <SECTION>
                        <SECTNO>§ 73.202 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                    </SECTION>
                    <AMDPAR>2. Section 73.202(b), the Table of FM Allotments under New York, is amended by adding Channel 296A at Saranac Lake, and removing Channel 273A and adding Channel 275A at Westport.</AMDPAR>
                </REGTEXT>
                <SIG>
                    <FP>Federal Communications Commission. </FP>
                    <NAME>John A. Karousos, </NAME>
                    <TITLE>Chief, Allocations Branch, Policy and Rules Division, Mass Media Bureau.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13137 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6712-01-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <CFR>47 CFR Part 73 </CFR>
                <DEPDOC>[DA 00-920; MM Docket No. 99-103; RM-9506; RM-9829] </DEPDOC>
                <SUBJECT>Radio Broadcasting Services; Bayfield, CO and Teec Nos Pos, AZ </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>
                        This document allots Channel 223A, in lieu of previously proposed Channel 237A, to Bayfield, Colorado, as an additional local FM transmission service at that community in response to a petition for rule making filed by Mountain West Broadcasting (RM-9506). 
                        <E T="03">See</E>
                         64 FR 17141, April 8, 1999. Additionally, Channel 237C1 is allotted to Teec Nos Pos, Arizona, as that community's first local aural transmission service, in response to a counterproposal filed on behalf of Voice Ministries of Farmington, Inc. (RM-9829). Coordinates used for Channel 223A at Bayfield, Colorado, are 37-07-29 NL; 107-34-10 WL; coordinates used for Channel 237C1 at Teec Nos Pos, Arizona, are 36-54-36 NL; 109-06-00 WL. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective June 9, 2000. A filing window period for Channel 223A at Bayfield, Colorado, and for Channel 237C1 at Teec Nos Pos, Arizona, will not be opened at this time. Instead, the issue of opening a filing window for those channels will be addressed by the Commission in a subsequent Order. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Nancy Joyner, Mass Media Bureau, (202) 418-2180. Questions related to the application filing process should be addressed to the Audio Services Division, (202) 418-2700. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This is a synopsis of the Commission's Report and Order, MM Docket No. 99-103, adopted April 19, 2000, and released April 25, 2000. The full text of this Commission decision is available for inspection and copying during normal business hours in the FCC's Reference Information Center (Room CY-A257), 445 Twelfth Street, SW., Washington, DC. The complete text of this decision may also be purchased from the Commission's copy contractor, International Transcription Service, Inc., 1231 20th Street, NW., Washington, DC 20036, (202) 857-3800. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Part 73 </HD>
                    <P>Radio broadcasting.</P>
                </LSTSUB>
                <AMDPAR>Part 73 of Title 47 of the Code of Federal Regulations is amended as follows: </AMDPAR>
                <PART>
                    <HD SOURCE="HED">PART 73—[AMENDED] </HD>
                </PART>
                <AMDPAR>1. The authority citation for part 73 continues to read as follows: </AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>47 U.S.C. 154, 303, 334, 336. </P>
                </AUTH>
                <REGTEXT TITLE="47" PART="73">
                    <SECTION>
                        <SECTNO>§ 73.202 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                    </SECTION>
                    <AMDPAR>2. Section 73.202(b), the Table of FM Allotments under Arizona, is amended by adding Teec Nos Pos, Channel 237C1. </AMDPAR>
                    <AMDPAR>3. Section 73.202(b), the Table of FM Allotments under Colorado, is amended by adding Bayfield, Channel 223A. </AMDPAR>
                </REGTEXT>
                <SIG>
                    <FP>Federal Communications Commission. </FP>
                    <NAME>John A. Karousos, </NAME>
                    <TITLE>Chief, Allocations Branch, Policy and Rules Division, Mass Media Bureau. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13135 Filed 5-24-00; 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 Parts 222 and 223 </CFR>
                <DEPDOC>[Docket No. 000519147-0147-01; I.D. 051800C] </DEPDOC>
                <RIN>RIN 0648-AO22 </RIN>
                <SUBJECT>Sea Turtle Conservation; Restrictions Applicable to Shrimp Trawl Activities; Leatherback Conservation Zone </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; request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS is closing, for a 2 week period, all inshore waters and offshore waters out to 10 nautical miles (nm) (18.5 km) seaward of the COLREGS demarcation line, bounded by 32° N. lat. (approximately Tybee Island, Georgia) and 34° N. lat. (approximately Wilmington Beach, North Carolina) within the Leatherback Conservation Zone, to fishing by shrimp trawlers required to have a turtle excluder device (TED) installed in each net that is rigged for fishing, unless the TED has an escape opening large enough to exclude leatherback turtles, as specified in the regulations. This action is necessary to reduce mortality of endangered leatherback sea turtles incidentally captured in shrimp trawls. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This action is effective from May 19, 2000 through 11:59 p.m. (local time) on June 2, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments on this action should be addressed to the Chief, Endangered Species Division, Office of Protected Resources, NMFS, 1315 East-West Highway, Silver Spring, MD 20910. Comments may also be sent via fax to 301-713-0376. Comments will not be accepted if submitted via e-mail or the Internet. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Charles A. Oravetz, (727) 570-5312, (ph. 
                        <PRTPAGE P="33780"/>
                        727-570-5312, fax 727-570-5517, e-mail Chuck.Oravetz@noaa.gov), or Barbara A. Schroeder, (ph. 301-713-1401, fax 301-713-0376, e-mail Barbara.Schroeder@noaa.gov). 
                    </P>
                    <P>For assistance in modifying TED escape openings to exclude leatherback sea turtles, fishermen may contact gear specialists at the NMFS, Pascagoula, MS laboratory by phone (228) 762-4591 or fax (228) 769-8699. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Prohibitions to taking sea turtles are governed by regulations implementing the Endangered Species Act at 50 CFR parts 222 and 223. The incidental take of turtles during shrimp fishing in the Atlantic Ocean off the coast of the southeastern United States and in the Gulf of Mexico is excepted from the taking prohibition pursuant to sea turtle conservation regulations at 50 CFR 223.206, which include a requirement that shrimp trawlers have a NMFS-approved TED installed in each net rigged for fishing. The use of TEDs significantly reduces mortality of loggerhead, green, Kemp's ridley, and hawksbill sea turtles. Because leatherback turtles are larger than the escape openings of most NMFS-approved TEDs, use of these TEDs is not an effective means of protecting leatherback turtles. </P>
                <P>Through a final rule (60 FR 47713 September 14, 1995), NMFS established regulations to provide protection for leatherback turtles when they occur in locally high densities during their annual, spring northward migration along the Atlantic seaboard. Within the Leatherback Conservation Zone, NMFS may close an area for 2 weeks when leatherback sightings exceed 10 animals per 50 nm (92.6 km) during repeated aerial surveys pursuant to § 223.206(d)(2)(iv)(A) through (C). </P>
                <P>An aerial survey conducted on May 12, 2000, along the South Carolina coast documented 14 leatherback turtles over a total survey trackline of approximately 39.7 nm (73.6 km). The survey trackline was flown in a northeasterly direction commencing approximately 1 nm (1.9 km) offshore of Bull's Island (32°55′ N. lat., 080°39′ W. long.) and terminating approximately 1 nm (1.9 km) off of Winyah Bay (33°13′ N. lat., 080°11′ W. long.). A replicate survey conducted on May 16, 2000 sighted 12 leatherbacks in 46 nm (85.2 km) of trackline. This survey was flown in a northeasterly direction commencing approximately 1 nm (1.9 km) offshore of Isle of Palms (32°46′ N. lat., 080°46′ W. long.) and terminating approximately 1 nm (1.9 km) offshore of North Island (33°15′ N. lat., 080°11′ W. long.). Fishing effort appeared heavy at the time of the survey. One hundred and sixteen vessels (77 underway shrimp trawlers) were observed during the survey of the South Carolina coast. </P>
                <P>The Assistant Administrator for Fisheries, NOAA (AA), has determined that all inshore waters and offshore waters within 10 nm (18.5 km) seaward of the COLREGS demarcation line, bounded by 32° N. lat. and 34° N. lat., within the Leatherback Conservation Zone are closed to fishing by shrimp trawlers required to have a TED installed in each net that is rigged for fishing, unless the TED installed has an escape opening large enough to exclude leatherback turtles, meeting the specifications at 50 CFR 223.207(a)(7)(ii)(B) or 223.207(c)(1)(iv)(B). These regulations specify modifications that can be made to either single-grid hard TEDs or Parker soft TEDs to allow leatherbacks to escape. </P>
                <P>The regulations at 50 CFR 223.206(d)(2)(iv) also state that fishermen operating in the closed area with TEDs modified to exclude leatherback turtles must notify the NMFS Southeast Regional Administrator of their intentions to fish in the closed area. This aspect of the regulations does not have a current Office of Management and Budget (OMB) control number, issued pursuant to the Paperwork Reduction Act. Consequently, fishermen are not required to notify the Regional Administrator prior to fishing in the closed area, but they must still meet the gear requirements. </P>
                <HD SOURCE="HD1">Classification </HD>
                <P>This action has been determined to be not significant for purposes of Executive Order 12866. </P>
                <P>The AA is taking this action in accordance with the requirements of 50 CFR 223.206(d)(2)(iv) to provide protection for endangered leatherback sea turtles from incidental capture and drowning in shrimp trawls. Leatherback sea turtles are occurring in high concentrations in coastal waters in shrimp fishery statistical zones 32 and 33. This action allows shrimp fishing to continue in the affected area and informs fishermen of the gear changes that they can make to protect leatherback sea turtles. </P>
                <P>Pursuant to 5 U.S.C. 553(b)(B), the AA finds that there is good cause to waive prior notice and opportunity to comment on this action. It would be contrary to the public interest to provide prior notice and opportunity for comment because providing notice and comment would prevent the agency from implementing the necessary action in a timely manner to protect the endangered leatherback. Notice and opportunity to comment on the leatherback closure procedures was provided through the rulemaking establishing the closure procedures (60 FR 25663, May 12, 1995). </P>
                <P>
                    Pursuant to 5 U.S.C. 553(d)(3), the AA finds that there is good cause not to delay the effective date of this rule for 30 days. It would be contrary to the public interest to delay this action because such delay would prevent the agency from implementing the necessary action in a timely manner to protect the endangered leatherback. Accordingly, the AA is making the rule effective May 19, 2000 through June 2, 2000. This closure has been announced on the NOAA weather channel, in newspapers, and other media. Shrimp trawlers may also call (727) 570-5312 for updated area closure information. As prior notice and an opportunity for public comment are not required to be provided for this notification by 5 U.S.C. 553, or by any other law, the analytical requirements of 5 U.S.C. 601 
                    <E T="03">et</E>
                    . 
                    <E T="03">seq</E>
                    ., are inapplicable. 
                </P>
                <P>
                    The AA prepared an Environmental Assessment (EA) for the final rule requiring TED use in shrimp trawls and the regulatory framework for the Leatherback Conservation Zone (60 FR 47713, September 14, 1995). Copies of the EA are available (see 
                    <E T="02">ADDRESSES</E>
                    ). 
                </P>
                <SIG>
                    <DATED>Dated: May 19, 2000. </DATED>
                    <NAME>Penelope D. Dalton, </NAME>
                    <TITLE>Assistant Administrator for Fisheries, National Marine Fisheries Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13092 Filed 5-19-00; 4:55 pm] </FRDOC>
            <BILCOD>BILLING CODE 3510-22-F </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration </SUBAGY>
                <CFR>50 CFR Part 679 </CFR>
                <DEPDOC>[Docket No. 991108298-0145-02; I.D. 092199C] </DEPDOC>
                <RIN>RIN 0648-AL88 </RIN>
                <SUBJECT>Fisheries of the Exclusive Economic Zone Off Alaska; At-Sea Scales; Community Development Quota Program </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        NMFS issues a final rule to amend portions of the regulations 
                        <PRTPAGE P="33781"/>
                        implementing the equipment and operational requirements in the Community Development Quota (CDQ) fisheries for catch weight measurement, observer sampling stations, and observer transmission of data. After the first year of requiring scales and observer sampling stations on specified vessels participating in the CDQ fisheries, NMFS has identified aspects of the requirements that need further refinement and correction for effective implementation. This action is intended to effect those refinements. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective June 26, 2000. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Copies of the Regulatory Impact Review/Final Regulatory Flexibility Analysis (RIR/FRFA) prepared for this action may be obtained from the Sustainable Fisheries Division, Alaska Region, NMFS, P.O. Box 21668, Juneau, AK 99802-1668, Attn: Lori Gravel, or by calling the Alaska Region, NMFS, at 907-586-7228. A copy of the September 9, 1997, environmental assessment prepared for the Multispecies Community Development Quota (MS CDQ) Program can be obtained from the same address. </P>
                    <P>Comments involving the reporting burden estimates or any other aspects of the collection of information requirements contained in this final rule should be sent to both Lori Gravel, at the above address, and to the Office of Information and Regulatory Affairs, Office of Management and Budget (OMB), Washington, D.C. 20503 (ATTN: NOAA Desk Officer). Comments sent by e-mail or the Internet will not be accepted. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Alan Kinsolving, 907-586-7228 or alan.kinsolving@noaa.gov. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION: </HD>
                <HD SOURCE="HD1">Background </HD>
                <P>NMFS manages Fishing for groundfish by U.S. vessels in the exclusive economic zone of the Gulf of Alaska and the Bering Sea and Aleutian Islands Management Area according to the Fishery Management Plan for Groundfish of the Gulf of Alaska and the Fishery Management Plan for the Groundfish Fishery of the Bering Sea and Aleutian Islands Area (FMPs). The North Pacific Fishery Management Council (Council) prepared the FMPs under authority of the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act). Regulations implementing the FMPs at 50 CFR part 679 and subpart H of 50 CFR part 600 govern fishing by U.S. vessels. Equipment and operational requirements for catch weight measurement appear at 50 CFR 679.28 and equipment and operational requirements for transmission of observer data appear at 50 CFR 679.50. </P>
                <P>
                    This final rule makes numerous minor revisions to §§ 679.28 and 679.32. NMFS published a proposed rule to implement these revisions in the 
                    <E T="04">Federal Register</E>
                     on December 2, 1999 (64 FR 67555). The preamble to the proposed rule contains a full description of the revisions and their justification, which is not repeated here. The proposed rule also provided the public with a 30-day review and comment period. NMFS received no comments on the proposed rule. Although some editorial changes were made to the regulatory text in this final rule, no substantive changes were made from the proposed regulatory text. Though this action results in some substantive regulatory revisions, most changes are technical edits needed to clarify existing regulations. The substantive changes that alter existing regulations will: 
                </P>
                <P>1. Explicitly allow NMFS staff to inspect and approve scales for use at-sea; </P>
                <P>2. Allow the use of scale approval stickers or seals in lieu of maintaining a scale inspection report on board the vessel; </P>
                <P>3. Relax the annual certification requirements for the test weights that must accompany an approved observer platform scale; </P>
                <P>4. Allow scale manufacturers to use a computer-generated check number instead of a physical seal to protect adjustable scale components from fraudulent tampering; </P>
                <P>5. Relax the requirements for the daily printout of haul information for a vessel that must weigh all catch; </P>
                <P>6. Modify the requirements for visibility of the display on a total-catch weighing scale; </P>
                <P>7. Require operators of trawl catcher/processors to ensure that no removal of fish can take place between the bin and observer sampling station without the removal being visible to the observer; </P>
                <P>8. Define “tally area” and “collection point” for longline catcher/processors and specify requirements for their dimensions, location, and construction; </P>
                <P>9. Define the phrase “clear and unobstructed passage,” as used in the current regulations; </P>
                <P>10. Make the minimum work space requirements for the observer sampling station more flexible by giving a minimum area criterion in lieu of specific minimum station length and width requirements; </P>
                <P>11. Require that observer sampling station scales be mounted with the platform (i.e., the weighing surface) no more than 0.7 meter above the floor; </P>
                <P>12. Require that trawl catcher/processors provide at least 1 meter of belt space downstream from the total-catch weighing scale for the observer's use when processing samples; and </P>
                <P>13. Require that catcher/processors and motherships obtain, install, and maintain NMFS-provided data-entry software if participating in CDQ fisheries. </P>
                <HD SOURCE="HD1">Compliance Guide for Small Entities </HD>
                <P>The Small Business Regulatory Enforcement Fairness Act of 1996 requires that NMFS prepare a compliance guide that explains how small entities must comply with the regulations implemented in this final rule. This action revises the requirements for observer sampling stations, at-sea scales, and transmission of observer data. This action affects all small entities that are required to install and maintain NMFS-approved scales or observer sampling stations. Affected entities must comply with the regulations concerning at-sea scales and observer sampling stations at § 679.28 and the regulations concerning the transmission of observer data in the CDQ program at § 679.32. </P>
                <P>
                    Because this rule makes changes to the at-sea scales and observer sampling station programs, it is possible that a sampling station or scale that was acceptable when inspected in 1999 will not be acceptable now. NMFS recommends that small entities required to provide NMFS-approved scales or observer sampling stations contact Alan Kinsolving (see 
                    <E T="02">ADDRESSES</E>
                    ) prior to their next required scale or observer sampling station inspection to ensure that necessary modifications are made. 
                </P>
                <HD SOURCE="HD1">Classification </HD>
                <P>The Administrator, Alaska Region, NMFS (Regional Administrator), determined that this final rule is necessary for the conservation and management of the groundfish fisheries off Alaska. </P>
                <P>Notwithstanding any other provision of the law, no person is required to respond to, nor shall any person be subject to a penalty for failure to comply with, a collection of information subject to the requirements of the Paperwork Reduction Act (PRA), unless that collection of information displays a currently valid OMB control number. </P>
                <P>
                    This final rule contains collection-of-information requirements subject to the PRA that have been approved by OMB. The OMB control numbers and estimated response times for these requirements are: the submission of 
                    <PRTPAGE P="33782"/>
                    scale inspection reports is approved under 0648-0330 at 15 minutes per response; the retention of scale weight reports is approved under 0648-0330 at 3 minutes per response; the inspection of an observer sampling station is approved under 0648-0269 at 2 hours per response; and the electronic transmittal of observer data is approved under 0648-0307 at 10 minutes per response. 
                </P>
                <P>The estimates of response times given here include the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. </P>
                <P>
                    Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to NMFS (see 
                    <E T="02">ADDRESSES</E>
                    ) and to OMB (see 
                    <E T="02">ADDRESSES</E>
                    ). 
                </P>
                <P>NMFS prepared an FRFA for this final rule that describes the impact this action will have on small entities. A copy of this analysis is available from NMFS. No comments were received on the initial regulatory flexibility analysis prepared for this action. The Summary and Conclusions section of the FRFA states: </P>
                <EXTRACT>
                    <P>This action revises and clarifies the equipment and technical requirements for at-sea scales, observer sampling stations, and observer transmission of data by making numerous, minor revisions to the regulations implementing these programs. The action is necessary to ensure NMFS' ability to effectively manage these programs; to improve the clarity and consistency of the implementing regulations; and to reduce unnecessary regulatory burdens. It is being promulgated under the authority of the Magnuson-Stevens Act. This action will directly affect the 13 freezer longliners currently equipped with scales or observer sampling stations that may be small entities. The ownership characteristics of vessels that would be impacted by this action have not been analyzed to determine if they are independently owned and operated or affiliated with a larger parent company. This action will impose no new reporting or recordkeeping requirements nor will it duplicate, overlap, or conflict with existing Federal rules. NMFS estimates that this action will cost the owners of directly affected freezer longliners less than $8,500 distributed among the 13 vessels and in no case cost any one vessel more than $1,700. This represents less than .06 percent of the average per-vessel gross revenues for the affected vessels. In addition to the preferred alternative, the analysis considered two other alternatives: a “no action” alternative that would not revise the existing regulations; and a “partial implementation” alternative that would implement some of the proposed revisions. These alternatives were rejected because they would fail to make the changes necessary for successful management of these programs. NMFS cannot quantify measures to minimize economic impacts on small entities with this type of rulemaking, which is being implemented to ensure that the NMFS-certified observer on board a vessel is able to collect data in a reliable and unbiased manner within a safe working environment. However, the preferred alternatives selected were crafted to minimize costs to the industry and still achieve safety goals. </P>
                </EXTRACT>
                <P>
                    A copy of the RIR/FRFA can be obtained from NMFS (see 
                    <E T="02">ADDRESSES</E>
                    ). 
                </P>
                <P>This rule has been determined to be not significant for purposes of E.O. 12866. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 50 CFR Part 679 </HD>
                    <P>Alaska, Fisheries, Recordkeeping and reporting requirements.</P>
                </LSTSUB>
                <REGTEXT TITLE="50" PART="679">
                    <SIG>
                        <DATED>Dated: May 19, 2000. </DATED>
                        <NAME>Penelope D. Dalton, </NAME>
                        <TITLE>Assistant Administrator for Fisheries, National Marine Fisheries Service. </TITLE>
                    </SIG>
                    <P>For the reasons set out in the preamble, 50 CFR part 679 is amended as follows: </P>
                    <PART>
                        <HD SOURCE="HED">PART 679—FISHERIES OF THE EXCLUSIVE ECONOMIC ZONE OFF ALASKA </HD>
                    </PART>
                </REGTEXT>
                <REGTEXT TITLE="50" PART="679">
                    <AMDPAR>1. The authority citation for part 679 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            16 U.S.C. 773 
                            <E T="03">et</E>
                              
                            <E T="03">seq</E>
                            ., 1801 
                            <E T="03">et</E>
                              
                            <E T="03">seq</E>
                            . and 3631 
                            <E T="03">et</E>
                              
                            <E T="03">seq</E>
                            . 
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="50" PART="679">
                    <AMDPAR>2. In § 679.28, the section heading is revised; introductory text to paragraphs (b)(2)(iii), (b)(3), (b)(3)(ii)(B), (b)(5), and (d)(8), is revised; and paragraphs (b)(2)(vii), (b)(3)(ii)(A), (b)(5)(i), (b)(6), (d)(2), (d)(3), (d)(5) through (d)(7), and (d)(8)(i)(G) are revised to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 679.28</SECTNO>
                        <SUBJECT>Equipment and operational requirements. </SUBJECT>
                        <STARS/>
                        <P>(b) * * * </P>
                        <P>(2) * * * </P>
                        <P>
                            (iii) 
                            <E T="03">Who may perform scale inspections</E>
                            ? Scales must be inspected by either a NMFS staff scale inspector or a scale inspector employed by a weights and measures agency designated by NMFS to perform scale inspections on its behalf. A list of authorized scale inspectors is available from the Regional Administrator upon request. Scale inspections are paid for by NMFS. 
                        </P>
                        <STARS/>
                        <P>
                            (vii) 
                            <E T="03">Scale inspection report</E>
                            . (A) A scale is approved for use when the scale inspector completes and signs a scale inspection report verifying that the scale meets all of the requirements specified in this paragraph (b)(2) and appendix A to this part. 
                        </P>
                        <P>(B) The scale inspector must provide the original inspection report to the vessel owner and a copy to NMFS. </P>
                        <P>(C) The vessel owner must either: </P>
                        <P>(1) Maintain a copy of the report on board when use of the scale is required and make the report available to the observer, NMFS personnel, or an authorized officer, upon request, or; </P>
                        <P>(2) Display a valid NMFS-sticker on each approved scale. </P>
                        <P>(D) When in use, an approved scale must also meet the requirements described in paragraphs (b)(3) through (b)(6) of this section. </P>
                        <P>
                            (3) 
                            <E T="03">At-sea scale tests</E>
                            . To verify that the scale meets the MPEs specified in this paragraph (b)(3), the vessel operator must test each scale or scale system used to weigh total catch one time during each 24-hour period when use of the scale is required. The vessel owner must ensure that these tests are performed in an accurate and timely manner. 
                        </P>
                        <STARS/>
                        <P>(ii) * * * (A) The MPE for platform and hanging scales is plus or minus 0.5 percent of the known weight of the test material. </P>
                        <P>
                            (B) 
                            <E T="03">Test weights</E>
                            . Each test weight must have its weight stamped on or otherwise permanently affixed to it. The weight of each test weight must be annually certified by a National Institute of Standards and Technology approved metrology laboratory or approved for continued use by the NMFS authorized inspector at the time of the annual scale inspection. The amount of test weights that must be provided by the vessel owner is specified in paragraphs (b)(3)(ii)(B)(
                            <E T="03">1</E>
                            ) and (b)(3)(ii)(B)(
                            <E T="03">2</E>
                            ) of this section. 
                        </P>
                        <STARS/>
                        <P>
                            (5) 
                            <E T="03">Printed reports from the scale</E>
                             (not applicable to observer sampling scales). The vessel owner must ensure that the printed reports are provided as required by this paragraph. Printed reports from the scale must be maintained on board the vessel until the end of the year during which the reports were made and be made available to observers, NMFS personnel, or an authorized officer. In addition, printed reports must be retained by the vessel owner for 3 years after the end of the year during which the printouts were made. 
                        </P>
                        <P>
                            (i) 
                            <E T="03">Reports of catch weight and cumulative weight</E>
                            . Reports must be printed at least once every 24 hours when use of the scale is required. Reports must also be printed before any information stored in the scale computer memory is replaced. Scale weights must not be adjusted by the scale operator to account for the 
                            <PRTPAGE P="33783"/>
                            perceived weight of water, mud, debris, or other materials. Scale printouts must show: 
                        </P>
                        <P>(A) The vessel name and Federal fisheries or processor permit number; </P>
                        <P>(B) The haul or set number as recorded in the processor's DCPL (see § 679.5); </P>
                        <P>(C) The total weight of the haul or set; </P>
                        <P>(D) The total cumulative weight of all fish or other material weighed on the scale. </P>
                        <STARS/>
                        <P>
                            (6) 
                            <E T="03">Scale installation requirements</E>
                            . The scale display must be readable from where the observer collects unsorted catch. 
                        </P>
                        <STARS/>
                        <P>(d) * * * </P>
                        <P>
                            (2) 
                            <E T="03">Location</E>
                            —(i) 
                            <E T="03">Motherships and catcher/processors or catcher vessels using trawl gear</E>
                            . The observer sampling station must be located within 4 m of the location from which the observer collects unsorted catch. Clear, unobstructed passage must be provided between the observer sampling station and the location where the observer collects unsorted catch. When standing where unsorted catch is sampled, the observer must be able to see that no fish have been removed between the bin and the scale used to weigh total catch. 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Vessels using nontrawl gear</E>
                            . The observer sampling station must be located within 5 m of the collection area, described at § 679.28(d)(7)(ii)(B), unless any location within this distance is unsafe for the observer. Clear, unobstructed passage must be provided between the observer sampling station and the collection area. Access must be provided to the tally station, described at § 679.28(d)(7)(ii)(A). NMFS may approve an alternative location if the vessel owner submits a written proposal describing the alternative location and the reasons why a location within 5 m of where fish are brought on board the vessel is unsafe, and the proposed observer sampling station meets all other applicable requirements of this section. 
                        </P>
                        <P>
                            (iii) 
                            <E T="03">What is clear, unobstructed passage</E>
                            ? Where clear and unobstructed passage is required, passageways must be at least 65 cm wide at their narrowest point, be free of tripping hazards, and be at least 1.8 m high. Doorways or companionways must be free of obstacles. 
                        </P>
                        <P>
                            (3) 
                            <E T="03">Minimum work space</E>
                            . The observer must have a working area for sampling of at least 4.5 square meters. This working area includes the observer's sampling table. The observer must be able to stand upright and have a work area at least 0.9 m deep in the area in front of the table and scale. 
                        </P>
                        <STARS/>
                        <P>
                            (5) 
                            <E T="03">Observer sampling scale</E>
                            . The observer sampling station must include a NMFS-approved platform scale with a capacity of at least 50 kg located within 1 m of the observer's sampling table. The scale must be mounted so that the weighing surface is no more than 0.7 m above the floor. The scale must be approved by NMFS under paragraph (b) of this section and must meet the maximum permissible error requirement specified in paragraph (b)(3)(ii)(A) of this section when tested by the observer. 
                        </P>
                        <P>
                            (6) 
                            <E T="03">Other requirements</E>
                            . The sampling station must include flooring that prevents slipping and drains well (grating or other material where appropriate), adequate lighting, and a hose that supplies fresh or sea water to the observer. 
                        </P>
                        <P>
                            (7) 
                            <E T="03">Requirements for sampling catch</E>
                            —(i) 
                            <E T="03">Motherships and catcher/processors using trawl gear</E>
                            . The conveyor belt conveying unsorted catch must have a removable board to allow fish to be diverted from the belt directly into the observer's sampling baskets. The diverter board must be located downstream of the scale used to weigh total catch so that the observer can use this scale to weigh large samples. At least 1 m of accessible belt space, located downstream of the scale used to weigh total catch, must be available for the observer's use when sampling a haul. 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Catcher/processors using non-trawl gear</E>
                            . In addition to the sampling station, vessels using non-trawl gear must provide: (A) 
                            <E T="03">Tally station</E>
                            . A place where the observer can see the gear as it leaves the water and can count and identify fish. It must be within 5 m of where fish are brought aboard the vessel and in a location where the observer is not in danger of falling overboard or being injured during gear retrieval. Where exposed to wind or seas, it must be equipped with a railing at least 1.0 m high, grating or other non-slip material, and adequate lighting. 
                        </P>
                        <P>
                            (B) 
                            <E T="03">Collection area</E>
                            . A collection area is a place where the observer, or vessel crew under the observer's guidance, collects fish as they come off the line or are removed from pots. It must be located where the observer can see the gear when it leaves the water. Where exposed to wind or seas, it must be equipped with a railing at least 1.0 m high and grating or other non-slip material. 
                        </P>
                        <P>
                            (8) 
                            <E T="03">Inspection of the observer sampling station</E>
                            . Each observer sampling station must be inspected and approved by NMFS prior to its use for the first time and then one time each year within 12 months of the date of the most recent inspection with the following exceptions: If the observer sampling station is moved or if the space or equipment available to the observer is reduced or removed when use of the observer sampling station is required, the observer sampling station inspection report issued under this section is no longer valid, and the observer sampling station must be reinspected and approved by NMFS. Inspection of the observer sampling station is in addition to inspection of the at-sea scales by an authorized scale inspector required at paragraph (b)(2) of this section. 
                        </P>
                        <P>(i) * * * </P>
                        <P>(G) For catcher/processors using trawl gear and motherships, a diagram drawn to scale showing the location(s) where all catch will be weighed, the location where observers will sample unsorted catch, and the location of the observer sampling station as described at paragraph (d) of this section. </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="50" PART="679">
                    <AMDPAR>3. In § 679.32, paragraphs (c)(4)(iii) and (c)(4)(iv) are redesignated as paragraphs (c)(4)(iv) and (c)(4)(v) respectively, and a new paragraph (c)(4)(iii) is added to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 679.32</SECTNO>
                        <SUBJECT>Groundfish and halibut CDQ catch monitoring. </SUBJECT>
                        <STARS/>
                        <P>(c) * * * </P>
                        <P>(4) * * * </P>
                        <P>(iii) Obtain the data entry software provided by the Regional Administrator (“ATLAS software”) for use by the observer and ensure that observer data can be transmitted from the vessel to NMFS at any time while the vessel is receiving, catching or processing CDQ species. </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="50" PART="679">
                    <AMDPAR>
                        4. In appendix A to part 679, in section 2.3.1.8, paragraphs (a)(iv) and (a)(v), in section 3.3.1.7, paragraphs (a)(iv) and (a)(v), and in section 4.3.1.5, paragraph (iv) are removed; in section 2.3.1.8, paragraphs (a)(vi) through (a)(viii) are redesignated as paragraphs (a)(iv) through (a)(vi) respectively; in section 3.3.1.7, paragraphs (a)(vi) through (a)(viii) are redesignated as paragraphs (a)(iv) through (a)(vi) respectively; in section 4.3.1.5, paragraph (a)(v) is redesignated as paragraph (a)(iv); and the definition of “security seals or means” in section 5.0 is revised to read as follows:
                        <PRTPAGE P="33784"/>
                    </AMDPAR>
                    <HD SOURCE="HD1">APPENDIX A TO PART 679_PERFORMANCE AND TECHNICAL REQUIREMENTS FOR SCALES USED TO WEIGH CATCH AT SEA IN THE GROUNDFISH FISHERIES OFF ALASKA </HD>
                    <STARS/>
                    <HD SOURCE="HD2">5. Definitions </HD>
                    <STARS/>
                    <P>
                        <E T="03">Security seals or means</E>
                        —A physical seal such as a lead and wire seal that must be broken in order to change the operating or performance characteristics of the scale, or a number generated by the scale whenever a change is made to an adjustable component. The number must be sequential and it must not be possible for the scale operator to alter it. The number must be displayed whenever the scale is turned on. 
                    </P>
                    <STARS/>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13185 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-22-F </BILCOD>
        </RULE>
    </RULES>
    <VOL>65</VOL>
    <NO>102</NO>
    <DATE>Thursday, May 25, 2000</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="33785"/>
                <AGENCY TYPE="F">OFFICE OF PERSONNEL MANAGEMENT </AGENCY>
                <CFR>5 CFR Part 536 </CFR>
                <RIN>RIN 3206-AI88 </RIN>
                <SUBJECT>Grade and Pay Retention </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Personnel Management. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Office of Personnel Management is issuing proposed regulations giving agencies discretionary authority to grant pay retention to certain employees moving to positions under pay systems other than the General Schedule or the Federal Wage System. This new flexibility would allow agencies to prevent eligible employees from suffering a reduction in pay that would otherwise result from a management action. The proposed regulations also provide that grade retention will no longer apply to employees moving into the General Schedule or the Federal Wage System from noncovered pay systems. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before July 24, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments may be sent or delivered to Donald J. Winstead, Assistant Director for Compensation Administration, Workforce Compensation and Performance Service, Office of Personnel Management, Room 7H31, 1900 E Street NW., Washington, DC 20415-8200 (FAX: (202) 606-0824 or EMAIL: payleave@opm.gov) </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Sharon Herzberg (202) 606-2858 or FAX: (202) 606-0824 or EMAIL: 
                        <E T="03">payleave@opm.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under 5 U.S.C. 5361-5365, agencies may grant grade or pay retention to employees covered by the General Schedule (GS) pay system or the Federal Wage System (FWS) when a reduction in grade or pay is caused or influenced by a management action and certain other conditions are met. While the law expressly provides that these provisions apply to movements within or between those two covered pay schedules, the Office of Personnel Management (OPM) has provided by regulation that these provisions may also be applied to certain employees who move from a noncovered pay schedule to a covered pay schedule. (See definition of 
                    <E T="03">employee</E>
                     in 5 CFR 536.102.) This regulatory extension of the grade and pay retention provisions is authorized by 5 U.S.C. 5365(b)(1), which allows OPM to extend the application of “all or portions” of the grade and pay retention provisions to employees under noncovered pay schedules who move to a covered pay schedule. 
                </P>
                <P>The Department of Justice has requested that we extend pay retention to members of the Senior Executive Service (SES) who move to immigration judge (IJ) positions. While there is no provision in statute or regulation that permits management to direct the movement of a member of the SES to an IJ position, there are circumstances that have resulted in the movement of an SES member to a non-SES position that has a lower rate of pay. Examples include an SES member who voluntarily accepts a non-SES position following receipt of a notice of position abolishment or a notice of directed geographic reassignment (if there is no mobility agreement), or other management action that causes or influences the employee to move to a lower-paid position. </P>
                <P>Prior to the Illegal Immigration Reform and Immigrant Responsibility Act of 1996, Public Law 104-208, immigration judges were covered by the GS pay system. Before the statute was enacted, the Department of Justice was able to offer pay retention to an SES member who moved to an IJ position as a result of a management action, as described above. However, section 371 of the Act removed IJs from the GS pay system and established a unique IJ pay system with a top rate set at 92 percent of the rate of basic pay for SES level ES-5. As a result of the Act, immigration judges are no longer under a “covered pay system” and therefore are no longer eligible for pay retention. Because the statutory maximum IJ pay rate is less than the rates of pay for ES-5 and ES-6, an SES member who moves to an IJ position without pay retention could suffer a significant loss in pay. The inability to grant pay retention to employees who move between noncovered pay systems has deprived the Department of Justice of a needed degree of flexibility. </P>
                <P>At the request of the Department of Justice, we reviewed this issue and determined that we have authority under the law to extend grade and pay retention to employees who move to or within noncovered pay schedules. Under 5 U.S.C. 5365(b)(2), OPM is authorized to apply “all or portions” of the grade and pay retention provisions to “individuals to whom such provisions do not otherwise apply.” We further concluded that it would be appropriate as a matter of policy to amend our regulations to provide agencies with discretionary authority to grant pay retention to employees moving to or within noncovered pay schedules. Since these other pay schedules are generally not administered by OPM, we concluded that any use of the pay retention authority in these circumstances should be discretionary. We note that, under some circumstances, grade and pay retention benefits are already subject to an agency's discretion. (See 5 CFR 536.103(b) and 536.104(b).) </P>
                <P>
                    We concluded that this extension should not apply to grade retention, since that benefit was designed specifically for retention of grades under the GS and FWS pay systems. As explained above, the law allows OPM to selectively apply portions of the grade and pay retention provisions. Under current regulations, grade retention does not apply to members of the Senior Executive Service (SES) or employees in senior-level positions under 5 U.S.C. 5376 (SL/ST) even if they move to a covered pay schedule. (See 5 CFR 536.105(c).) However, the current regulations are silent regarding grade retention for administrative law judges (ALJs). Thus, it is possible for an ALJ who moves to a GS-14 position because of a management action to have GS-15 established as a retained grade. For consistency, we are proposing to amend the regulations to provide that grade retention does not apply to any employee who moves from, between, or within non-GS/FWS schedules—including the pay schedules for SES members, SL/ST positions, ALJs, and IJs. 
                    <PRTPAGE P="33786"/>
                </P>
                <P>We are proposing that the normal rules for adjusting a retained rate not be applied to employees covered by a regulatory extension of pay retention under 5 U.S.C. 5365(b) who are not in a GS or FWS position while receiving pay retention, or who are in a GS or FWS position but receiving a retained rate in excess of the maximum rate of the applicable basic pay schedule (GS or FWS). Under the normal rules, a GS or FWS employee's retained rate is adjusted by 50 percent of the dollar increase in the maximum rate for the employee's grade. However, other pay systems may not have the same type of grade-based pay structure or are subject to different annual pay adjustments. </P>
                <P>For example, many senior-level pay schedules are linked to the Executive Schedule, which sometimes has not been adjusted on an annual basis. This can result in anomalous situations. If an SES member at the ES-2 level (currently $107,100) moves to a GS-15 position and receives a retained rate, that retained rate subsequently could be increased to a rate above the ES-2 rate in effect at some future date. (Note: Retained rates for GS employees are capped at the rate for level V of the Executive Schedule, which limits this problem; however, agencies are required to adjust and maintain the “retained rate of record” without regard to the level V cap.) We are proposing to exercise our authority under 5 U.S.C. 5365(b) not to apply the retained rate adjustment portion of the statutory pay retention provisions for the categories of employees described above. Thus, these employees' retained rates would be frozen with no provision for any pay adjustment. </P>
                <P>
                    These proposed regulations would not impair any agency's independent authority to fix pay for employees under a pay schedule administered by that agency. The proposed extension of the pay retention provisions would be relevant only if the agency lacks any other authority to establish a saved rate for its employees. For example, the Department of Justice does not have authority to create a saved rate under the IJ pay system based on the former rate received by an SES member. The proposed regulations would allow the Department of Justice, at its discretion, to extend pay retention to an SES member moving to an IJ position. To be entitled to pay retention, an employee must also meet all other qualifying conditions (
                    <E T="03">e.g.,</E>
                     the pay reduction is caused or influenced by a management action, not at the employee's request or because of personal cause; there is no break in service; and there is no declination of a reasonable offer). 
                </P>
                <P>
                    To effect the policy change proposed here, we propose to add a new paragraph (d) to § 536.104 to give agencies discretionary authority to provide pay retention to any otherwise eligible Federal “employee,” as defined in 5 U.S.C. 2105. The definition of 
                    <E T="03">employee</E>
                     in § 536.102 would be broadened to include an “employee,” as defined in 5 U.S.C. 2105, to whom pay retention is granted under this discretionary authority. However, we are also proposing to add a sentence to § 530.102 that expressly excludes officials in or moving from an Executive Schedule position, since we believe pay retention is not appropriate for such officials. In addition, § 536.105(c), which excludes certain employees from grade retention, would be revised to exclude any employee who moves from a position not under a statutorily covered pay schedule to a position under a statutorily covered pay schedule. Also, we propose to remove paragraph (3) under the definition of 
                    <E T="03">representative rate</E>
                     and paragraph (b) of § 536.203, since grade retention would no longer apply to employees moving from noncovered pay schedules. 
                </P>
                <P>We also propose to revise § 536.205(c) to provide that an employee who moves from a noncovered pay schedule to a statutorily covered pay schedule and who receives a retained rate in excess of the maximum rate of the statutorily covered pay schedule is not entitled to any increase in basic pay when there is an increase in the scheduled rates. In addition, to clarify and simplify the regulations, we propose to delete the language in the existing § 536.205(g), which we believe is unnecessary in view of other provisions found elsewhere in parts 531, 532 and 536. </P>
                <P>Instead, we propose to revise § 536.205(g) to address how the rules for administering a retained rate apply to employees under an administratively covered pay schedule who were granted pay retention under § 536.104(d). Specifically, the proposed change provides that the retained rate of such an employee will be frozen and that the regular or normal rate to which the employee otherwise would be entitled (but for pay retention) must be treated as a single-rate range in applying paragraphs (b) and (d) of that section, including the provisions governing the 150 percent cap established by 5 U.S.C. 5363(b)(2). </P>
                <P>As noted above, eligibility for grade and pay retention is subject to certain exclusions, as provided in 5 CFR 536.105. Paragraph (a)(1) of that section bars grade or pay retention for employees who move from a position that is not in an “agency” as defined in 5 U.S.C. 5102. This definition of “agency,” which is located in paragraph (a) of section 5102, is used to exclude employees in certain agencies from coverage under the GS classification and pay system. Other employees are excluded from the GS system if they fall under one of the categories of employees listed in paragraph (c) of section 5102 or if they are excluded by some other provision of law. </P>
                <P>The exclusion in § 536.105(a)(1) is not statutory, but reflects a limitation OPM imposed simultaneous with the regulatory extension of grade and pay retention eligibility to employees moving to a covered pay schedule from a noncovered pay schedule. Recently OPM approved a variation to § 536.105(a)(1) at the request of the Department of Defense (DOD). (See Notice of OPM Variation, Notice No. 99-47, November 3, 1999.) While DOD is a covered agency under 5 U.S.C. 5102, several DOD subcomponents are expressly excluded from the definition of “agency” in 5 U.S.C. 5102(a)—namely, the National Security Agency, the Defense Intelligence Agency, and the National Imagery and Mapping Agency. Therefore, employees in these subcomponents are barred by § 536.105(a)(1) from receiving grade and pay retention upon movement to a covered pay schedule. DOD requested that OPM approve a variation to 5 CFR 536.105(a)(1) to allow otherwise eligible employees who move to GS or FWS positions from positions in these DOD subcomponents to receive grade or pay retention, even though these DOD subcomponents are excluded from the definition of an “agency” in 5 U.S.C. 5102(a). OPM agreed that a variation was warranted to ensure equal treatment of DOD employees. </P>
                <P>
                    Upon further consideration, we believe that the provision in § 536.105(a)(1) barring grade or pay retention for employees who move from a position that is not is an agency as defined in 5 U.S.C. 5102 should be removed altogether. The current rule results in inequitable treatment of employees by providing different benefits based on the specific method used to exclude an employee from coverage under the GS system. For pay retention purposes, we believe it should not matter whether an employee is excluded from the GS system under paragraph (a) or (c) of 5 U.S.C. 5102 or under some other provision of law. Therefore, we propose to remove the existing paragraph (a)(1) from § 536.105. This will extend pay retention eligibility to certain categories of non-GS employees. (Grade retention is not at issue, since we are already proposing to 
                    <PRTPAGE P="33787"/>
                    bar grade retention for all employees in or moving from non-GS/FWS pay systems.) 
                </P>
                <HD SOURCE="HD1">E.O. 12866, Regulatory Review </HD>
                <P>This rule has been reviewed by the Office of Management and Budget in accordance with Executive Order 12866. </P>
                <HD SOURCE="HD1">Regulatory Flexibility Act </HD>
                <P>I certify that these regulations would not have a significant economic impact on a substantial number of small entities because they would only apply to Federal agencies and employees. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 5 CFR Part 536 </HD>
                    <P>Administrative practice and procedure, Freedom of information, Government employees, Reporting and recordkeeping requirements, Wages.</P>
                </LSTSUB>
                <SIG>
                    <FP>U.S. Office of Personnel Management. </FP>
                    <NAME>Janice R. Lachance, </NAME>
                    <TITLE>Director. </TITLE>
                </SIG>
                <P>Accordingly, OPM is proposing to amend part 536 of title 5 of the Code of Federal Regulations as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 536—GRADE AND PAY RETENTION </HD>
                    <P>1. The authority citation for part 536 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>5 U.S.C. 5361-5366; sec. 7202(f) of the Omnibus Budget Reconciliation Act of 1990 (Pub. L. 101-508), 104 Stat. 1338-336; sec. 4 of the Performance Management and Recognition System Termination Act of 1993 (Pub. L. 103-89), 107 Stat. 981; § 536.307 also issued under 5 U.S.C. 552, Freedom of Information Act, Pub. L. 92-502. </P>
                    </AUTH>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart A—Definitions; Coverage and Applicability </HD>
                    </SUBPART>
                    <P>
                        2. In § 536.102, the definition of 
                        <E T="03">Representative rate</E>
                         is amended by adding “or” after the semicolon at the end of paragraph (1), removing the “or” at the end of paragraph (2), and replacing the semicolon with a period, and removing paragraph (3); and the definition of 
                        <E T="03">employee</E>
                         is revised to read as follows: 
                    </P>
                    <SECTION>
                        <SECTNO>§ 536.102 </SECTNO>
                        <SUBJECT>Definitions. </SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Employee</E>
                             means an employee as defined in 5 U.S.C. 5361 and also an individual who moves from a position which is not under a statutorily covered pay schedule to a position which is under a statutorily covered pay schedule, provided that the individual's employment immediately prior to the move was not on a temporary or term basis. 
                            <E T="03">Employee</E>
                             also means an employee as defined in 5 U.S.C. 2105 who is granted pay retention under § 536.104(d), subject to the limitations set forth in this part. However, 
                            <E T="03">employee</E>
                             does not include an official in or moving from an Executive Schedule position. 
                        </P>
                        <STARS/>
                        <P>3. In § 536.104, a new paragraph (d) is added to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 536.104 </SECTNO>
                        <SUBJECT>Coverage and applicability of pay retention. </SUBJECT>
                        <STARS/>
                        <P>(d) The head of an agency may apply the pay retention provisions of this part to an individual not under a statutorily covered pay schedule (as defined in 5 U.S.C. 5361) whose rate of basic pay would otherwise be reduced as the result of a management action, provided that individual is an employee as defined in 5 U.S.C. 2105 (excluding an official in or moving from an Executive Schedule position). Coverage is subject to all other qualifying conditions and limitations established in this part. </P>
                        <P>4. In § 536.105, paragraph (a)(1) is removed, paragraphs (a)(2) through (a)(5) are redesignated as (a)(1) through (a)(4), respectively, and paragraph (c) is revised to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 536.105 </SECTNO>
                        <SUBJECT>Exclusions. </SUBJECT>
                        <STARS/>
                        <P>(c) Grade retention under § 536.103 does not apply to an employee who— </P>
                        <P>(1) Moves to a position not under a statutorily covered pay schedule; or </P>
                        <P>(2) Moves from a position not under a statutorily covered pay schedule to a position under a statutorily covered pay schedule. </P>
                        <P>5. Section 536.203 is revised to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 536.203 </SECTNO>
                        <SUBJECT>Determination of retained grade. </SUBJECT>
                        <P>An employee who is in a position under a statutorily covered pay schedule immediately prior to the action that gives entitlement to grade retention shall retain the grade held immediately prior to the action. </P>
                        <P>6. In § 536.205, paragraphs (c) and (g) are revised to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 536.205 </SECTNO>
                        <SUBJECT>Determination of rate of basic pay. </SUBJECT>
                        <STARS/>
                        <P>(c) When an increase in the scheduled rates of the grade of the employee's position occurs while the employee is under pay retention, the employee is entitled to 50 percent of the amount of the increase in the maximum rate of basic pay payable for the grade of the employee's current position. This paragraph does not apply to employees who move from a noncovered pay schedule to a statutorily covered pay schedule and who are receiving a retained rate in excess of the maximum payable rate of the applicable covered pay schedule. </P>
                        <STARS/>
                        <P>(g) Notwithstanding paragraphs (b), (c), and (d) of this section, for an employee who is not in a position under a statutorily covered pay schedule while receiving a retained rate (as allowed by § 536.104(d))— </P>
                        <P>(1) The retained rate is compared to the rate of basic pay that otherwise would apply to the employee but for the retained rate (instead of comparing it to the maximum rate of the rate range for the employee's position) and is terminated when the retained rate falls below the employee's otherwise applicable rate; </P>
                        <P>(2) The retained rate is capped at 150 percent of the rate of basic pay that otherwise would apply to the employee but for the retained rate (instead of 150 percent of the maximum rate of the rate range for the employee's position); and </P>
                        <P>(3) The retained rate is frozen and may not be increased. </P>
                    </SECTION>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13052 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6325-01-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Rural Utilities Service </SUBAGY>
                <CFR>7 CFR Part 1735 </CFR>
                <RIN>RIN 0572-AB56 </RIN>
                <SUBJECT>General Policies, Types of Loans, Loan Requirements—Telecommunications Program </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Rural Utilities Service, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Supplemental proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Rural Utilities Service (RUS) is proposing to amend its regulations to update the criteria for determining “reasonably adequate service” levels for local exchange carriers and providers of specialized telecommunications service. This supplemental proposed rule is part of an ongoing RUS project to modernize agency policies in order to provide borrowers with the flexibility to continue providing reliable, modern telephone service at reasonable costs in rural areas, while maintaining the security and feasibility of the Government's loans. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments on this supplemental proposed rule must be received by RUS by or carry a postmark or equivalent of June 26, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit written comments on this supplemental proposed rule to Roberta D. Purcell, Assistant Administrator, Telecommunications 
                        <PRTPAGE P="33788"/>
                        Program, Rural Utilities Service, 1400 Independence Avenue, SW., Room 4056, STOP 1590, Washington, DC 20250-1590. RUS requires a signed original and three copies of all comments (7 CFR part 1700.4). All comments received will be available for public inspection in room 4056, South Building, U.S. Department of Agriculture, Washington, DC, between 8 a.m. and 4 p.m., Monday through Friday (7 CFR part 1.27(b)). 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jonathan P. Claffey, Deputy Assistant Administrator, Telecommunications Program, Rural Utilities Service, 1400 Independence Avenue, SW., Room 4056, STOP 1590, Washington, DC 20250-1590. Telephone: (202) 720-9556. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Executive Order 12866 </HD>
                <P>This proposed rule has been determined to be not significant and, therefore, has not been reviewed by the Office of Management and Budget (OMB) under Executive Order 12866. </P>
                <HD SOURCE="HD1">Executive Order 12988 </HD>
                <P>This proposed rule has been reviewed in accordance with Executive Order 12988, Civil Justice Reform. RUS has determined that this proposed rule meets the applicable standards provided in section 3 of that Executive Order. In addition, all State and local laws and regulations that are in conflict with this rule will be preempted; no retroactive effect will be given to this rule; and in accordance with section 212(e) of the Department of Agriculture Reorganization Act of 1994 (7 U.S.C. 6912(e)) administrative appeal procedures, if any are required, must be exhausted prior to initiating litigation against the Department or its agencies. </P>
                <HD SOURCE="HD1">Regulatory Flexibility Act Certification </HD>
                <P>
                    RUS has determined that this proposed rule will not have a significant economic impact on a substantial number of small entities, as defined by the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ). The RUS telecommunications loan program provides borrowers with loans at interest rates and terms that are more favorable than those generally available from the private sector. RUS borrowers, as a result of obtaining Federal financing, receive economic benefits that exceed any direct cost associated with complying with RUS regulations and requirements. 
                </P>
                <HD SOURCE="HD1">Information Collection and Recordkeeping Requirements </HD>
                <P>This proposed rule contains no new reporting or recordkeeping burdens, under OMB control number 0572-0079 that would require approval under the Paperwork Reduction Act of 1995 (44 U.S.C. chapter 35). </P>
                <P>Send questions or comments regarding this burden or any other aspect of these collections of information, including suggestions for reducing the burden to F. Lamont Heppe, Director, Program Development and Regulatory Analysis, Rural Utilities Service, 1400 Independence Avenue, SW., Room 4034, STOP 1522, Washington, DC 20250-1522. </P>
                <HD SOURCE="HD1">National Environmental Policy Act Certification </HD>
                <P>
                    The Administrator of RUS has determined that this proposed rule will not significantly affect the quality of the human environment as defined by the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ). Therefore, this action does not require an environmental impact statement or assessment. 
                </P>
                <HD SOURCE="HD1">Catalog of Federal Domestic Assistance </HD>
                <P>The program described by this proposed rule is listed in the Catalog of Federal Domestic Assistance programs under numbers 10.851, Rural Telephone Loans and Loan Guarantees, and 10.852, Rural Telephone Bank Loans. This catalog is available on a subscription basis from the Superintendent of Documents, the United States Government Printing Office, Washington, DC 20402-9325. Telephone: (202) 512-1800. </P>
                <HD SOURCE="HD1">Executive Order 12372 </HD>
                <P>This program is excluded from the scope of Executive Order 12372, Intergovernmental Consultation, which may require consultation with State and local officials. See the final rule related notice entitled “Department Programs and Activities Excluded from Executive Order 12372,” (50 FR 47034). </P>
                <HD SOURCE="HD1">Unfunded Mandates </HD>
                <P>This proposed rule contains no Federal mandates (under the regulatory provisions of title II of the Unfunded Mandates Reform Act of 1995) for State, local, and tribal governments or the private sector. Thus, this proposed rule is not subject to the requirements of sections 202 and 205 of the Unfunded Mandates Reform Act of 1995. </P>
                <HD SOURCE="HD1">Background </HD>
                <P>The telecommunications industry is becoming increasingly competitive. The Telecommunications Act of 1996 (Public Law 104-104) and regulatory actions by the Federal Communications Commission (FCC) are drastically altering the regulatory and business environment of all telecommunications systems, including RUS borrowers. At the same time, changes in overall business trends and technologies continue to place pressure on RUS-financed systems to offer a wider array of services and to operate more efficiently. </P>
                <P>The Telecommunications Act of 1996 mandates that universally available and affordable telecommunications services, including advanced services, be made available to all US citizens—whether in rural areas or city centers, affluent or poor communities. RUS supports this mandate and the goal that, with the assistance of advanced telecommunications technology, rural citizens be provided the same economic, educational, and health care benefits available in the larger metropolitan areas. RUS believes that the most expeditious way to bring the full range of telephone services to rural areas is to make certain providers of advanced services, in addition to providers of local exchange services, eligible for RUS financing. </P>
                <P>RUS regulations currently contain criteria for RUS to consider in determining whether telecommunications service is reasonably adequate (7 CFR 1735.12(c), Nonduplication). However, these criteria do not recognize certain technological and other factors that are currently employed to determine adequate service. RUS is proposing separate criteria for local exchange carriers and providers of specialized telecommunications service. These revised criteria for determining “reasonably adequate service” are derived primarily from RUS policies related to telecommunications carriers generally, the Telecommunications Act of 1996, and FCC rules and regulations. </P>
                <P>
                    Under the Telecommunications Act of 1996, all incumbent local exchange carriers (ILECs) are automatically considered eligible telecommunications carriers (ETCs). An ETC is certified by the regulatory commission having jurisdiction, which makes it eligible to receive universal service support. Each State regulatory commission will name at least one ETC for every area. In return for universal service support, the ETC must make available an FCC-specified level of service throughout a designated area. Furthermore, an ETC must agree to advertise basic services in a specific area and offer service to everyone in that area. 
                    <PRTPAGE P="33789"/>
                </P>
                <P>If a LEC that has not previously borrowed from RUS applies for financing, RUS is proposing to lend only to those LECs that are ETCs within the State or tribal jurisdiction in which their financed facilities are to be located, LECs that have made commitments, satisfactory to RUS, to become ETCs, or LECs that commits to act as ETCs with respect to the area coverage requirements as described in § 1735.11. ETCs are eligible for universal service support and have accepted the obligations of being an ETC. ETC status, therefore, both enhances loan feasibility and promotes area wide coverage. </P>
                <P>The Governor of RTB utilizes RUS policies in carrying out RTB's loan program. Therefore, these policy revisions would apply to loans made by RTB, as well. </P>
                <P>RUS proposed amending certain provisions of 7 CFR part 1735 in a Proposed Rule published on February 11, 2000 at 65 FR 6922. Subsequently, RUS continued to review and analyze the rapidly developing telecommunications environment and decided to propose further revisions of certain provisions of 7 CFR part 1735, including portions of §§ 1735.2, 1735.10(c), 1735.12, and 1735.14 as published on February 2, 2000. RUS requests comments on all provisions published in this Supplemental Proposed Rule. Those proposed amendments published first on February 11, 2000, but revised again by this supplement will be subject to the procedures, including those concerning public comments, applicable hereto. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 7 CFR Part 1735 </HD>
                    <P>Accounting, Loan programs—communications, Reporting and recordkeeping requirements, Rural areas, Telephone.</P>
                </LSTSUB>
                <P>For the reasons set forth in the preamble, 7 CFR chapter XVII is proposed to be amended as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 1735—GENERAL POLICIES, TYPES OF LOANS, LOAN REQUIREMENTS—TELECOMMUNICATIONS PROGRAM </HD>
                    <P>1. The authority citation for part 1735 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            7 U.S.C. 901 
                            <E T="03">et seq.</E>
                            , 1921 
                            <E T="03">et seq.</E>
                            , and 6941 
                            <E T="03">et seq.</E>
                              
                        </P>
                    </AUTH>
                    <P>2. In § 1735.2, as proposed to be amended February 11, 2000, at 65 FR 6923, revise the definition of Mobile telecommunications service and add the following definitions in alphabetical order to read as follows: </P>
                    <SECTION>
                        <SECTNO>§ 1735.2 </SECTNO>
                        <SUBJECT>Definitions. </SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Exchange access</E>
                             means the offering of access to telephone exchange services or facilities for the purpose of the origination or termination of telephone toll services. 
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Local exchange carrier (LEC)</E>
                             means an organization that is engaged in the provision of telephone exchange service or exchange access. 
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Mobile telecommunications service</E>
                             means radio communication voice service between mobile and land or fixed stations, or between mobile stations. 
                        </P>
                        <P>
                            <E T="03">Modernization Plan (State Telecommunications Modernization Plan)</E>
                             means a State plan, which has been approved by RUS, for improving the telecommunications network of those telecommunications providers covered by the plan. A Modernization Plan must conform to the provisions of 7 CFR part 1751, subpart B. 
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">RE Act</E>
                             means the Rural Electrification Act of 1936, as amended (7 U.S.C. 901 
                            <E T="03">et seq.</E>
                            ).
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Specialized telecommunications service</E>
                             means any telephone service other than telephone exchange service, exchange access, or mobile telecommunications service. 
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Telecommunications</E>
                             means the transmission or reception of voice, data, sounds, signals, pictures, writings, or signs of all kinds, by wire, fiber, radio, light, or other visual or electromagnetic means. 
                        </P>
                        <P>
                            <E T="03">Telephone exchange service</E>
                             means: (1) Service provided primarily to fixed locations within a telephone exchange, or within a connected system of telephone exchanges within the same exchange area operated to furnish to subscribers intercommunicating service of the character ordinarily furnished by a single exchange, and which is covered by the exchange service charge; or (2) Comparable service provided through a system of switches, transmission equipment, or other facilities (or combination thereof) by which a subscriber can originate and terminate a telecommunications service. 
                        </P>
                        <STARS/>
                        <P>3. Revise § 1735.10(c), as proposed to be revised February 11, 2000, at 65 FR 6923, to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1735.10 </SECTNO>
                        <SUBJECT>General. </SUBJECT>
                        <STARS/>
                        <P>(c) A borrower receiving a loan to provide mobile telecommunications services or special telecommunications services shall be considered to be participating in the state telecommunications plan (TMP) with respect to the particular loan so long as the loan funds are not used in a manner that, in RUS' opinion, is inconsistent with the borrower achieving the goals set forth in the plan, except that a borrower must comply with any portion of a TMP made applicable to the borrower by a state commission with jurisdiction. </P>
                        <STARS/>
                        <P>4. In § 1735.12, as proposed to be amended at 65 FR 6923, revise paragraph (c) and add paragraph (f) to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1735.12 </SECTNO>
                        <SUBJECT>Nonduplication. </SUBJECT>
                        <STARS/>
                        <P>(c) RUS shall consider the following criteria for any wireline local exchange service or similar fixed-station voice service provided by a local exchange carrier (LEC) in determining whether such service is reasonably adequate: </P>
                        <P>(1) The LEC is providing area coverage as described in § 1735.11. </P>
                        <P>
                            (2) The LEC is providing all one-party service or, if the State commission has mandated a lower grade of service, the LEC is eliminating that service in accordance with the requirements of the Telecommunications Act of 1996, 47 U.S.C. 151 
                            <E T="03">et seq.</E>
                        </P>
                        <P>(3) The LEC's network is capable of providing transmission and reception of data at a rate of at least 1,000,000 bits per second (1 Mbps) with reasonable modification to any subscriber who requests it. </P>
                        <P>(4) The LEC makes available custom calling features (at a minimum, call waiting, call forwarding, abbreviated dialing, and three-way calling). </P>
                        <P>(5) The LEC is able to provide E911 service to all subscribers, when requested by the government entity responsible for this service. </P>
                        <P>(6) The LEC is able to offer local service with blocked toll access to those subscribers who request it. </P>
                        <P>(7) The LEC's network is capable of accommodating Internet access at speeds of at least 28,800 bits per second (28.8 Kbps) via modem dial-up from any subscriber location. </P>
                        <P>(8) There is an absence of frequent service interruptions. </P>
                        <P>(9) The LEC is interconnected with the public switched network. </P>
                        <P>(10) No Federal or State regulatory commission having jurisdiction has determined that the quality, availability, or reliability of the service provided is inadequate. </P>
                        <P>
                            (11) Services are provided at reasonably affordable rates. 
                            <PRTPAGE P="33790"/>
                        </P>
                        <P>(12) Any other criteria the Administrator determines to be applicable to the particular case. </P>
                        <STARS/>
                        <P>(f) RUS shall consider the following criteria for any provider of a specialized telecommunications service in determining whether such service is reasonably adequate: </P>
                        <P>(1) The provider of a specialized telecommunications service is providing area coverage as described in § 1735.11. </P>
                        <P>(2) An adequate signal strength is provided throughout the largest practical portion of the service area. </P>
                        <P>(3) There is an absence of frequent service interruptions. </P>
                        <P>(4) The quality and variety of service provided is comparable to that provided in nonrural areas. </P>
                        <P>(5) The service provided complies with industry standards. </P>
                        <P>(6) No Federal, State, or local regulatory commission having jurisdiction has determined that the quality, availability, or reliability of the service provided is inadequate. </P>
                        <P>(7) Services are provided at reasonably affordable rates. </P>
                        <P>(8) Any other criteria the Administrator determines to be applicable to the particular case. </P>
                        <P>5. In § 1735.14, as proposed to be amended at 65 FR 6924, remove “and” at the end of paragraph (c)(1), remove the period at the end of paragraph (c)(2) and add “; and” in its place, and add new paragraph (c)(3) to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1735.14 </SECTNO>
                        <SUBJECT>Borrower eligibility. </SUBJECT>
                        <STARS/>
                        <P>(c) * * * </P>
                        <P>(3) If a local exchange carrier, must be either an eligible telecommunications carrier (ETC) within the State or tribal jurisdiction in which the RUS-financed facilities are to be located, a LEC that has made a commitment, satisfactory to RUS, to become an ETC within the State or tribal jurisdiction in which the financed facilities are to be located, or a LEC that commits to act as an ETC in such a manner as to meet the area coverage requirements as described in § 1735.11. </P>
                    </SECTION>
                    <SIG>
                        <DATED>Dated: May 12, 2000. </DATED>
                        <NAME>Jill Long Thompson, </NAME>
                        <TITLE>Under Secretary, Rural Development. </TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-12657 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-15-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT </AGENCY>
                <SUBAGY>Office of Federal Housing Enterprise Oversight </SUBAGY>
                <CFR>12 CFR Part 1710 </CFR>
                <RIN>RIN 2550-AA09 </RIN>
                <SUBJECT>Releasing Information; Electronic Freedom of Information Amendment </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Federal Housing Enterprise Oversight, HUD. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Office of Federal Housing Enterprise Oversight (OFHEO) is proposing to amend its regulations to reflect the changes to the Freedom of Information Act (FOIA) made by the Electronic Freedom of Information Act Amendments Act of 1996 (1996 Act) and to revise the method of computing fees. The proposal provides for: electronic FOIA requests; access to records published or released under FOIA in electronic format; expedited processing of FOIA requests upon a showing of compelling need; publication of responses to FOIA requests that are likely to become repeat requests; aggregation of clearly related requests by a single requester or group of requesters acting in concert; informing the requester of the volume of requested material withheld and the extent of deletions both in publicly available records and records released in response to a FOIA request; and a method for computing fees that is based upon the classification of the employee performing the work as executive, professional, or clerical. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments regarding the proposed rulemaking must be received by July 24, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        All comments concerning the proposed rule should be addressed to Alfred M. Pollard, General Counsel, Office of Federal Housing Enterprise Oversight, 1700 G Street NW, Fourth Floor, Washington, DC 20552. Alternatively, comments may be submitted via electronic mail to: 
                        <E T="03">RegComments@ofheo.gov.</E>
                         Copies of all communications received will be available for public inspection and copying at the address above. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dorothy J. Acosta, Associate General Counsel, 1700 G Street NW, Fourth Floor, Washington, DC 20552, telephone (202) 414-6924 (not a toll-free number). The telephone number for the Telecommunications Device for the Deaf is (800) 877-8339. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On December 23, 1998, OFHEO issued a final rule governing the release of information to the public, which, among other things, implemented the requirements of the Freedom of Information Act (FOIA). 63 FR 70998, Dec. 23, 1998. At the time of the publication of the final regulation, OFHEO noted that Congress had enacted the Electronic Freedom of Information Act Amendments of 1996 (1996 Act) 
                    <SU>1</SU>
                    <FTREF/>
                     to provide for public access to information in an electronic format and for other purposes and announced that these amendments would be implemented by a separate rulemaking. Although certain of the 1996 Act's amendments that did not involve access to records in an electronic format were included in the final regulation, such as the extension of the time limit for the initial agency response from ten (10) to 20 days, this proposed regulation implements the remainder of the amendments and proposes a new method for computing fees. The 1996 Act amendments that are reflected in this proposal are: (1) The requirement to make requested documents available in the form or format specified by the requester, provided the document is readily reproducible in that form or format; (2) the requirement to make publicly available copies of records released in response to FOIA requests that are likely to become the subject of subsequent requests for substantially the same records; (3) the requirement for electronic access to records required to be made public by 5 U.S.C. 552(a)(2) that were created after November 1, 1996; (4) the requirement to provide expedited processing of FOIA requests upon a showing of compelling need by the requester and in such other cases as the agency may determine; (5) the requirement to indicate the extent of any deletion made in released records and publicly available records; (6) the requirement to inform the requester of the estimated volume of material withheld; and (7) the provision for aggregating clearly related requests as a single request when such a request would constitute an “unusual circumstance” justifying an extension of the response time. Although the 1996 Act authorized agencies to promulgate regulations providing for multi-tracking of FOIA requests based on the amount of time or work (or both) involved in processing requests, OFHEO has elected not to propose such regulations at this time. Thus far, the volume of FOIA requests has not been so great that a multi-tracking system is needed. 
                    <PRTPAGE P="33791"/>
                    Although not required by the 1996 Act, the proposed regulation would allow requests to be made electronically. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Pub. L. 104-231, 110 Stat. 3048.
                    </P>
                </FTNT>
                <P>
                    The proposal would also revise the way fees are determined for personnel costs involved in processing a request. Currently, an hourly rate for actual time spent searching, reviewing, and duplicating is determined by the salary of the particular employee performing the work plus 16% of that amount to reflect the cost of benefits. In order to simplify the calculation of fees and provide a more transparent and predictable fee schedule for requesters, OFHEO proposes a method for computing fees that would charge one of three hourly rates for personnel costs associated with responding to a request, depending on whether the employee performing the work is classified as executive, professional, or clerical. An average of the actual compensation (salary and benefits) of all employees of OFHEO in a particular classification would determine the actual hourly fee for that classification. These fees would be adjusted periodically to reflect significant changes in average compensation. The current fee schedule would be available on OFHEO's website (
                    <E T="03">http://www.ofheo.gov/docs/</E>
                    ) and by mail. 
                </P>
                <HD SOURCE="HD1">Section-by-Section Analysis </HD>
                <HD SOURCE="HD2">Subpart A—General Definitions </HD>
                <P>The definition of “record” in § 1710.2(j) would be amended by inserting the phrase “regardless of form or format,” to clarify that a record may be electronic in form. </P>
                <HD SOURCE="HD2">Subpart B—Documents and Information Generally </HD>
                <P>
                    Subpart B contains general provisions relating to disclosure of documents and information in the possession of OFHEO. Section 1710.7(c) provides that if a requested record is available through routine distribution procedures, OFHEO will first refer the requester to those sources, and only if the requester is not satisfied will OFHEO treat the request as a FOIA request. The proposed regulation adds the OFHEO website, (
                    <E T="03">http://www.ofheo.gov</E>
                    ) to the list of routine distribution procedures. 
                </P>
                <HD SOURCE="HD2">Subpart C—Availability of Records of OFHEO </HD>
                <P>Section 1710.11 of subpart C provides, generally, for the release of OFHEO records. Paragraph (a) of this section addresses the release of records in response to requests and paragraph (b) addresses records required to be made publicly available, including current indexes to such records. The proposed regulation separates the provisions of existing § 1710.11 that relate to records required to be made publicly available pursuant to 5 U.S.C. 552(a)(2) from those that relate to the release of records upon request and relocates provisions related to records required to be made publicly available to § 1710.12. The existing provisions of § 1710.12 would be deleted, because they are made unnecessary by other amendments to the regulation. Specific changes to the existing text of §§ 1710.11 and 1710.12 are explained more fully below. </P>
                <P>Section 1710.11(a) would be amended to incorporate the substance of § 1710.11(c), which addresses copying costs, and to state that records will be made available in the form or format requested provided they are readily reproducible in that form or format with reasonable effort. “Readily reproducible” is defined to mean, with respect to electronic format, that the requested record or records can be downloaded or transferred intact to a computer disk, or other electronic medium using equipment currently in use by OFHEO. </P>
                <P>Section 1710.11(b), which addresses records required to be made publicly available under 5 U.S.C. 552(a)(2), would be redesignated as § 1710.12(a) and amended to: (1) Incorporate the substance of § 1710.11(c) addressing copying costs; (2) state that all publicly available documents are available by mail; (3) state that records created after November 1, 1996, including current indexes to all publicly available records regardless of when created, will be available on OFHEO's website; and (4) add to the list of records publicly available, copies of records that have been released under the FOIA that OFHEO believes are likely to become the subject of subsequent requests for substantially the same records. </P>
                <P>Section 1710.11(c), which relates to copying charges, would be deleted and its substance incorporated in §§ 1710.11(a) and 1710.12(a). </P>
                <P>
                    Section 1710.11(d), which sets forth FOIA exemptions, would then be redesignated as § 1710.11(b). This allows the regulatory designation for exemptions to be consistent with the statutory designation (
                    <E T="03">i.e.,</E>
                     (b)(1), (b)(2), (b)(3), etc. instead of (d)(1), (d)(2), (d)(3), 
                    <E T="03">etc.</E>
                    ) and avoids potential confusion arising from different statutory and regulatory designations. 
                </P>
                <P>Section 1710.11(e) would be redesignated as § 1710.1(c). </P>
                <P>Section 1710.11(f) would be redesignated as § 1710.11(d) and would be amended to require that the amount of any information deleted from a record released under FOIA be indicated on the released portion of the record (at the place the deletion is made, if technically feasible). </P>
                <P>Section 1710.11(g), which relates to permissible deletions in publicly available records, would be redesignated as § 1710.12(b) and amended to state that the extent of any deletions necessary to protect personal privacy will be indicated on the records that are publicly available under redesignated § 1710.12(a), at the place where the deletion is made if technically feasible, unless including the indication would harm an interest protected by the exemption on which the deletion is based. </P>
                <P>Section (h) would be redesignated as § 1710.11(e). </P>
                <P>Section 1710.12(a) currently states that the indexes that are required to be made available for public inspection and copying under 5 U.S.C. 552(a)(2) are available for inspection and copying at OFHEO's offices during regular business hours. This existing provision would be deleted because it is duplicative of the introductory language of existing § 1710.11(b), which would be redesignated as § 1710.12(a) and amended as described above. The heading of § 1710.12 would be revised to read “Publicly Available Records.” </P>
                <P>Section 1710.12(b) currently contains the Director's determination that, because of the lack of requests to date for records required to be indexed, such indexes do not need to be published quarterly. It states, however, that the indexes will be provided by mail upon request. Because OFHEO proposes to publish current indexes on its website, this finding is unnecessary and would be deleted. The statement that current indexes are available by mail would be relocated to § 1710.12(a). </P>
                <P>Section 1710.13 would be amended to permit requests to be made by facsimile or electronic mail and to require that the request include the submitter's name, address and telephone number, to enable the FOIA Officer to contact the requester about the request in the event that clarification is needed. </P>
                <P>Section 1710.14(c) would be amended to state that OFHEO is not required to create a record to respond to a request, replacing a statement that OFHEO will not create a record. While normally OFHEO will not create a record to respond to a request, there may be some circumstances in which it is easier to create a record than to redact a record or records in which the requested information is contained. </P>
                <P>
                    Section 1710.15, which prescribes the form and content of FOIA responses, would be amended by adding a 
                    <PRTPAGE P="33792"/>
                    requirement that a notice of denial of a FOIA request (in whole or in part) include an estimate of the volume of requested material withheld, unless providing it would harm an interest protected by the exemption on which the denial is based. 
                </P>
                <P>Section 1710.16 sets forth the process for appeal of denials. Paragraph (a) would be amended to clarify that the appeal procedures also apply to denials of requests for expedited processing. Paragraph (b) would be amended to permit appeals to be submitted electronically or by facsimile. Paragraph (g), which sets forth the right to judicial review, currently states that a requester will be deemed to have exhausted his or her administrative remedies if an administrative appeal has been denied or has not been acted on within 20 days of receipt. This paragraph would be amended to state that if OFHEO provides the requester an opportunity to limit the scope of the request or arrange an alternate time for processing the request, the requester's refusal to do either will be considered a factor in determining whether “exceptional circumstances” exist. A showing of exceptional circumstances and due diligence on the part of the agency allows a court in which judicial review is sought to grant a stay to allow the agency additional time to complete its review of the records. </P>
                <P>Section 1710.17 of the existing rule describes the time limits within which OFHEO will respond to initial requests and appeals of denials of requests. Paragraph (b) would be amended to state that appeals of denials of expedited processing will be acted on as expeditiously as practicable. Paragraph (c) would be amended by providing that if OFHEO extends the time limit stated in that paragraph and is unable to process the request by the date specified in the notice, OFHEO will offer the requester an opportunity to limit the scope of the request or arrange an alternate time frame for processing the request or a modified request. A new paragraph (d) would be added that provides for aggregating multiple requests involving clearly related matters made by a single requester, or group of requesters acting in concert, when such requests would, if considered as a single request, constitute an “unusual circumstance” justifying an extension of the response time. A new paragraph (e) would be added that provides for expedited processing upon a showing of compelling need by the requester and in such other cases as OFHEO may determine. A request for expedited processing must be accompanied by a statement, certified to be true and correct by the requester, that demonstrates compelling need. To show compelling need, the requester's statement must demonstrate that failure to obtain the requested records could reasonably be expected to pose an imminent threat to the life or physical safety of an individual, or, in the case of a requester whose main professional occupation or activity is the dissemination of information, that there is urgency to inform the public of the government activity involved in the request beyond the public's right to know of government activity generally. The requester must be notified within 10 working days of the disposition of the request, and any appeal of the denial must be acted on expeditiously. </P>
                <HD SOURCE="HD2">Subpart D—Fees for Provision of Information </HD>
                <P>Subpart D sets forth the fees that will be assessed for services rendered in responding to and processing requests for records under the FOIA. The definition of “direct costs” in § 1710.21(b) would be amended to include the costs of any automated searches and the cost of securing any contract services that may be necessary to respond to a FOIA request. To reflect the revised fee schedule set forth in the amended section 1710.22(b), a reference to that section is substituted for the reference to the actual salary of the person performing the work as a basis for the fees charged. </P>
                <P>Section 1710.21(f) would be amended by adding a requirement that the copy of the requested record be provided in the form or format requested, provided it is readily reproducible in that form or format with reasonable effort. </P>
                <P>
                    Section 1710.22 would be revised to reflect a new method for computing fees and to make minor technical changes to better accommodate the changes made in response to the 1996 Act. Instead of basing the fee on the actual salary rate of the employee performing the work plus 16% for benefits, OFHEO proposes to charge one of three hourly fees determined by whether the employee performing the work is classified as executive, professional, or clerical. The fee for each category would be determined by the average of the actual salaries and benefits of the employees in that category and would be adjusted periodically to reflect significant changes in average compensation of the class. The “executive” category refers to the senior management of the agency (
                    <E T="03">i.e.</E>
                     Director, Deputy Director, Associate Directors, and Deputy Associate Directors). The “clerical” category includes employees performing primarily secretarial, clerical or ministerial tasks. The “professional” category includes all other employees. A current fee schedule would be available on OFHEO's website or by mail. Conforming changes are made in paragraph (b)(1)(ii) of this section, § 1710.23(g), and § 1710.38(a) of this part. 
                </P>
                <P>Technical changes to § 1710.22 include substituting “computer equipment” for “central processing unit” and changing the heading in § 1710.22(b)(2) from “Duplication” to “Reproduction” to clarify that the paragraph applies both to duplicating a record in the same format and to reproducing a record in a different format, and by changing the word “reproduction” to “photocopied” in the first sentence to clarify that the per page charge applies only to photocopies of records. Conforming changes are made in § 1710.23. </P>
                <P>Throughout the regulation, minor, nonsubstantive syntactical changes are made in the revised sections and citations to sections of the Freedom of Information Act are replaced with citations to the sections of the regulation containing the relevant statutory provisions. Citations to 5 U.S.C. 552 are replaced with “the Freedom of Information Act.” These changes will allow the reader to understand the regulatory provisions without referring to the statute. </P>
                <HD SOURCE="HD1">Regulatory Impact </HD>
                <HD SOURCE="HD2">Executive Order 13132, Federalism </HD>
                <P>Executive Order 13132 requires that Executive departments and agencies identify regulatory actions that have significant federalism implications. A regulation has federalism implications if it has substantial direct effects on the States, on the relationship or distribution of power between the Federal Government and the States, or on the distribution of power and responsibilities among various levels of Government. OFHEO has determined that this rule has no federalism implications that warrant the preparation of a Federalism Assessment in accordance with Executive Order 13132. </P>
                <HD SOURCE="HD2">Executive Order 12866, Regulatory Planning and Review </HD>
                <P>
                    OMB has determined that rulemakings that amend FOIA regulations to implement the requirements of the Electronic Freedom of Information Act Amendments of l996 are not “significant” regulations for the purposes of Executive Order 12866. 
                    <PRTPAGE P="33793"/>
                </P>
                <HD SOURCE="HD2">Executive Order 12988, Civil Justice Reform </HD>
                <P>Executive Order 12988 sets forth guidelines to promote the just and efficient resolution of civil claims and to reduce the risk of litigation to the Federal Government. This final rule meets the applicable standards of sections 3(a) and (b) of Executive Order 12988. </P>
                <HD SOURCE="HD2">Unfunded Mandates Reform Act of 1995 </HD>
                <P>This rule does not include a Federal mandate that may result in the expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100,000,000 or more (adjusted annually for inflation) in any one year. Consequently, the rule does not warrant the preparation of an assessment statement in accordance with the Unfunded Mandates Reform Act of 1995. </P>
                <HD SOURCE="HD2">Regulatory Flexibility Act </HD>
                <P>
                    The Regulatory Flexibility Act, 5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    , requires that a regulation that has a significant economic impact on a substantial number of small entities, small businesses, or small organizations must include an initial regulatory flexibility analysis describing the regulation's impact on small entities. Such an analysis need not be undertaken if the agency has certified that the regulation will not have a significant economic impact on a substantial number of small entities. 5 U.S.C. 605(b). 
                </P>
                <P>OFHEO has considered the impact of the regulation under the Regulatory Flexibility Act. The General Counsel has certified that this final rule will not have significant economic impact on a substantial number of small entities. </P>
                <HD SOURCE="HD2">Paperwork Reduction Act </HD>
                <P>The Paperwork Reduction Act of 1995, 44 U.S.C. chapter 35, requires that regulations involving the collection of information receive clearance from OMB. This rule contains no such collection of information requiring OMB approval under the Paperwork Reduction Act. Consequently, no information has been submitted to OMB for review under the Paperwork Reduction Act. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 12 CFR Part 1710 </HD>
                    <P>Administrative practice and procedure, Confidential business information, Electronic products, Freedom of information.</P>
                </LSTSUB>
                  
                <P>Accordingly, for reasons set forth in the preamble, OFHEO proposes to amend 12 CFR part 1710 as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 1710—RELEASING INFORMATION </HD>
                    <P>1. The authority citation for part 1710 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>5 U.S.C. 301, 552; 12 U.S.C. 4513, 4522, 4526, 4639; E.O. 12600; 3 CFR, 1987 Comp., p. 235. </P>
                    </AUTH>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart A—General Definitions </HD>
                        <SECTION>
                            <SECTNO>§ 1710.2 </SECTNO>
                            <SUBJECT>[Amended] </SUBJECT>
                            <P>2. Amend § 1710.2(j) by adding “, regardless of form or format,” after “document”. </P>
                        </SECTION>
                    </SUBPART>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart B—Documents and Information Generally </HD>
                        <SECTION>
                            <SECTNO>§ 1710.7 </SECTNO>
                            <SUBJECT>[Amended] </SUBJECT>
                            <P>
                                3. Amend the first sentence of § 1710.7(c) by adding “or material offered on OFHEO's website (
                                <E T="03">http://www.ofheo.gov</E>
                                ),” after the comma following the parenthetical. 
                            </P>
                        </SECTION>
                    </SUBPART>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart C—Availability of Records of OFHEO </HD>
                    </SUBPART>
                    <P>4. Revise § 1710.11 to read as follows: </P>
                    <SECTION>
                        <SECTNO>§ 1710.11 </SECTNO>
                        <SUBJECT>Official records of OFHEO. </SUBJECT>
                        <P>(a) OFHEO shall, upon a written request for records that reasonably describes the information or records and is made in accordance with the provisions of this subpart, make the records available as promptly as practicable to any person for inspection and/or copying, except as provided in paragraph (b) of this section. OFHEO may charge a fee determined in accordance with subpart D of this part. OFHEO will make the record available in the form or format requested if the record is readily reproducible in that form or format with reasonable effort. “Readily reproducible” means, with respect to electronic format, that the requested record or records can be downloaded or transferred intact to a computer disk, tape, or other electronic medium using equipment currently in use by OFHEO. </P>
                        <P>
                            (b) 
                            <E T="03">Records not available.</E>
                             Except as otherwise provided in this part, or as may be specifically authorized by the Director, the following information and records, or portions thereof, are not available to requesters: 
                        </P>
                        <P>(1) Any record, or portion thereof, that is—</P>
                        <P>(i) Specifically authorized under criteria established by an Executive order to be kept secret in the interest of national defense or foreign policy, and </P>
                        <P>(ii) Is in fact properly classified pursuant to such Executive order. </P>
                        <P>(2) Any record, or portion thereof, related solely to the internal personnel rules and practices of OFHEO. </P>
                        <P>(3) Any record, or portion thereof that is specifically exempted from disclosure by statute (other than 5 U.S.C. 552b), provided that such statute— </P>
                        <P>(i) Requires that the matters be withheld from the public in such a manner as to leave no discretion on the issue, or </P>
                        <P>(ii) Establishes particular criteria for withholding or refers to particular types of matters to be withheld. </P>
                        <P>(4) Any matter that is a trade secret or that constitutes commercial or financial information obtained from a person and that is privileged or confidential. </P>
                        <P>(5) Any matter contained in inter-agency or intra-agency memoranda or letters that would not be available by law to a private party in litigation with OFHEO. </P>
                        <P>(6) Any information contained in personnel and medical files and similar files (including financial files) the disclosure of which would constitute a clearly unwarranted invasion of personal privacy. </P>
                        <P>(7) Any records or information compiled for law enforcement purposes, but only to the extent that the production of such law enforcement records or information— </P>
                        <P>(i) Could reasonably be expected to interfere with enforcement proceedings; </P>
                        <P>(ii) Would deprive a person of a right to fair trial or an impartial adjudication; </P>
                        <P>(iii) Could reasonably be expected to constitute an unwarranted invasion of personal privacy; </P>
                        <P>(iv) Could reasonably be expected to disclose the identity of a confidential source, including a State, local, or foreign agency or authority or any private institution or an Enterprise regulated and examined by OFHEO that furnished information on a confidential basis, and, in the case of a record of information compiled by a criminal law enforcement authority in the course of a criminal investigation or by an agency conducting a lawful national security intelligence investigation, information furnished by a confidential source; </P>
                        <P>(v) Would disclose techniques and procedures for law enforcement investigations or prosecutions, or would disclose guidelines for law enforcement investigations or prosecutions if such disclosure could reasonably be expected to risk circumvention of the law; or </P>
                        <P>(vi) Could reasonably be expected to endanger the life or physical safety of any individual. </P>
                        <P>(8) Any matter that is contained in or related to examination, operating, or condition reports that are prepared by, on behalf of, or for the use of OFHEO. </P>
                        <P>
                            (9) Any geological and geophysical information and data, including maps, concerning wells. 
                            <PRTPAGE P="33794"/>
                        </P>
                        <P>(c) Even if an exemption described in paragraph (b) of this section may be reasonably applicable to a requested record, or portion thereof, OFHEO may elect under the circumstances of any particular request not to apply the exemption to such requested record, or portion thereof. The fact that the exemption is not applied by OFHEO to any requested record, or portion thereof, has no precedential significance as to the application or nonapplication of the exemption to any other requested record, or portion thereof, no matter when the request is received. </P>
                        <P>(d) Any reasonably segregable portion of a record shall be provided to any person properly requesting such record after deletion of the portions which are exempt under this subpart. The amount of the information deleted shall be indicated on the released portion of the record, unless including that indication would harm an interest protected by the exemption in paragraph (b) of this section pursuant to which the deletion is made. If technically feasible, the amount of the information deleted shall be indicated at the place in the record where the deletion is made. </P>
                        <P>(e) This section does not authorize withholding of information or limit the availability of records to the public, except as specifically stated in this section. This section is not authority to withhold information from Congress. </P>
                        <P>5. Revise § 1710.12 to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1710.12 </SECTNO>
                        <SUBJECT>Publicly available records </SUBJECT>
                        <P>
                            (a) The records described in this paragraph are available for public inspection and copying, for a fee determined in accordance with subpart D of this part, at OFHEO's offices located at 1700 G Street, NW, Fourth Floor, Washington, DC 20552. Records created on or after November 1, 1996, and current indexes to all records described in paragraphs (a)(1), (a)(2), (a)(3), and (a)(4) of this section, including those created before November 1, 1996, are available electronically at 
                            <E T="03">http://www.ofheo.gov/docs/.</E>
                             The publicly available records include— 
                        </P>
                        <P>(1) Any final opinions issued by OFHEO, as well as orders made in adjudication of cases as set forth in § 1710.9 of subpart B of this part; </P>
                        <P>
                            (2) Any statements of policy and interpretation that have been adopted by OFHEO and have not been published in the 
                            <E T="04">Federal Register</E>
                            ; 
                        </P>
                        <P>(3) Any OFHEO administrative staff manuals and instructions to staff that affect a member of the public, and that are not exempt from disclosure under the Freedom of Information Act; </P>
                        <P>(4) Copies of all records released pursuant to this subpart that OFHEO determines have become or are likely to become the subject of subsequent requests for substantially the same records; and</P>
                        <P>(5) Current indexes to the records described in this paragraph. </P>
                        <P>(b) To the extent necessary to prevent an invasion of personal privacy, the Director may delete identifying details from a record described in paragraph (a) of this section. In each case of such deletion, the justification will be clearly explained in writing and the extent of such deletion indicated (at the place in the record where the deletion is made if technically feasible), unless including that indication would harm an interest protected by the exemption in § 1710.11(b) pursuant to which the deletion is made. </P>
                        <P>6. Revise § 1710.13(a) to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1710.13 </SECTNO>
                        <SUBJECT>Requests for records. </SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Addressing requests.</E>
                             Requests for records in the possession of OFHEO shall be made in writing but may be submitted by regular mail, electronic mail, or facsimile. If the request is sent by regular mail, the request shall be addressed to FOIA Officer, Office of Federal Housing Enterprise Oversight, 1700 G Street NW., Fourth Floor, Washington, DC 20552, with both the envelope and the letter marked “FOIA Request.” Electronic mail requests shall be addressed to 
                            <E T="03">foia_office@ofheo.gov,</E>
                             with “FOIA Request” in the subject line. Requests submitted by fax shall be sent to FOIA Officer at (202) 414-8917 and shall be clearly marked “FOIA Request.” All requests shall include the requester's name, address, and telephone number. An improperly addressed request will be deemed not to have been received for purposes of the 20-day time period set forth in § 1710.17(a) of this subpart until it is received, or would have been received with the exercise of due diligence, by the FOIA Officer. Records requested in conformance with this subpart that are not exempt records may be obtained in person, by regular mail, or by electronic mail, as specified in the request, provided the records are readily reproducible in the requested form or format with reasonable effort. Records to be obtained in person will be available for inspection or copying during business hours on a regular business day in the office of OFHEO. 
                        </P>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1710.14 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                        <P>7. Amend § 1710.14(c) by removing “will not” and adding “is not required to” in its place in the last sentence. </P>
                        <P>8. Amend § 1710.15(b) by redesignating paragraphs (b)(2) and (b)(3) as (b)(3) and (b)(4) respectively, and adding a new paragraph (b)(2) to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1710.15 </SECTNO>
                        <SUBJECT>Form and content of responses. </SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(2) An estimate of the volume of any requested matter that is withheld, unless providing the estimate would harm an interest protected by the exemption in § 1710.11 (b) pursuant to which the denial was made; </P>
                        <STARS/>
                        <P>9. Amend § 1710.16 by revising paragraphs (a), (b), and (d) to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1710.16 </SECTNO>
                        <SUBJECT>Appeals of denials. </SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Right of appeal.</E>
                             If a request, including a request for expedited processing, has been denied in whole or in part, the requester may appeal the denial to: FOIA Appeals Officer, Office of Federal Housing Enterprise Oversight, 1700 G Street, NW, Fourth Floor, Washington DC 20552. Electronic appeals shall be submitted to 
                            <E T="03">foia_appeals_office@ofheo.gov</E>
                             with “FOIA Appeal_ in the subject line. 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Letter of appeal.</E>
                             The appeal must be in writing and submitted within 30 days of receipt of the denial letter. The appeal shall be submitted in the manner described in § 1710.13, except that it shall be clearly marked “FOIA Appeal” instead of “FOIA Request.” An appeal shall include a copy of the initial request, a copy of the letter denying the request in whole or in part, and a statement of the circumstances, reasons, or arguments advanced in support of disclosure of the requested record. An improperly addressed appeal shall be deemed not to have been received for the purposes of the 20-day time period set forth in § 1710.17(b) until it is received, or would have been received with the exercise of due diligence, by the Appeals Officer. 
                        </P>
                        <STARS/>
                        <P>
                            (d) 
                            <E T="03">Judicial review.</E>
                             If the denial of the request for records is upheld in whole or in part, or, if a determination on the appeal has not been mailed at the end of the 20-day period or the last extension thereof, the requester is deemed to have exhausted his or her administrative remedies, giving rise to a right of judicial review under 5 U.S.C. 552(a)(4). However, a requester's refusal of OFHEO's offer of an opportunity to limit the scope of the request or arrange 
                            <PRTPAGE P="33795"/>
                            an alternate time frame for processing the request shall be considered as a factor in determining whether “exceptional circumstances” exist, which permits a court in which a requester has sought judicial review, to grant a stay to allow OFHEO to complete its review of the records. 
                        </P>
                        <P>10. Revise § 1710.17 to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1710.17 </SECTNO>
                        <SUBJECT>Time limits. </SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Initial request.</E>
                             Following receipt of a request for records, the FOIA Officer will determine whether to comply with the request and will notify the requester in writing of his or her determination within 20 days (excluding Saturdays, Sundays, and legal holidays) after receipt of the request. 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Appeal.</E>
                             A written determination on an appeal submitted in accordance with § 1710.16 of this subpart will be issued within 20 days (excluding Saturdays, Sundays, and legal holidays) after receipt of the appeal. However, determination of an appeal of a denial of expedited processing will be issued as expeditiously as practicable. When a determination cannot be mailed within the applicable time limit, the appeal will nevertheless be processed. In such case, upon the expiration of the time limit, the requester will be informed of the reason for the delay, of the date on which a determination may be expected to be mailed, and of that person's right to seek judicial review. The requester may be asked to forego judicial review until determination of the appeal. 
                        </P>
                        <P>
                            (c) 
                            <E T="03">Extension of time limits.</E>
                             The time limits specified in either paragraph (a) or (b) of this section may be extended in unusual circumstances after written notice to the requester setting forth the reasons for the extension and the date on which a determination is expected to be made. If the date specified for the extension is more than 10 days after the initial time allowed for response, OFHEO will provide the requester an opportunity to limit the scope of the request or arrange for an alternate time frame for processing the request. As used in this paragraph, 
                            <E T="03">unusual circumstances</E>
                             means that there is a need to—
                        </P>
                        <P>(1) Search for and collect the requested records from facilities that are separate from the office processing the request; </P>
                        <P>(2) Search for, collect, and appropriately examine a voluminous amount of separate and distinct records which are demanded in a single request; or </P>
                        <P>(3) Consult with another agency having a substantial interest in the determination of the request, or consult with various offices within OFHEO that have a substantial interest in the records requested. </P>
                        <P>
                            (d) 
                            <E T="03">Related requests.</E>
                             OFHEO may aggregate multiple requests involving clearly related matters made by a single requester, or a group of requesters acting in concert, if OFHEO reasonably believes that such requests actually constitute a single request that would qualify as an “unusual circumstance.” 
                        </P>
                        <P>
                            (e) 
                            <E T="03">Expedited processing.</E>
                             (1) Upon a demonstration of compelling need by the requester, OFHEO will grant a request for expedited processing of a FOIA request. If a request for expedited processing is granted, OFHEO will give the request priority and process it as soon as practicable. 
                        </P>
                        <P>(2) To show a compelling need for expedited processing, the requester shall provide a statement demonstrating that: </P>
                        <P>(i) The failure to obtain the requested records could reasonably be expected to pose an imminent threat to the life or physical safety of an individual; or </P>
                        <P>(ii) The requester's main professional occupation or activity is information dissemination and there is a particular urgency to inform the public of government activity involved in the request beyond the public's right to know about government activity generally. </P>
                        <P>(3) The requester's statement of compelling need must be certified to be true and correct to the best of his or her knowledge and belief and must explain in detail the basis for requesting expedited processing. The formality of the certification required to obtain expedited treatment may be waived by OFHEO in its discretion. </P>
                        <P>(4) A requester seeking expedited processing will be notified within ten (10) working days of the receipt of the request whether expedited processing has been granted. If the request for expedited processing is denied, OFHEO will act on any appeal expeditiously. </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1710.18 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                        <P>11. Amend § 1710.18 as follows: </P>
                        <P>a. In paragraph (b)(1), remove “Exemption 4 of the FOIA, 5 U.S.C. 552(b)(4)'' and add in its place “§ 1710.11(b)(4)”. </P>
                        <P>b. In paragraph (c), remove “Exemption 4 of the FOIA, 5 U.S.C. 552(b)(4)” and add in its place “§ 1710.11(b)(4)”. </P>
                        <P>c. In paragraph (d)(2), remove “5 U.S.C. 552(b)(4)” and add in its place “§ 1710.11(b)(4)”. </P>
                        <P>d. In paragraph (e)(1), remove “5 U.S.C. 552(b)(4)” and add in its place “§ 1710.11(b)(4)”. </P>
                        <P>e. In paragraph (i)(3), remove “5 U.S.C. 552” and add in its place “the Freedom of Information Act”. </P>
                    </SECTION>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart D—Fees for Provision of Information </HD>
                    </SUBPART>
                    <P>12. Amend § 1710.21 by revising paragraphs (b) and (f) to read as follows: </P>
                    <SECTION>
                        <SECTNO>§ 1710.21 </SECTNO>
                        <SUBJECT>Fees. </SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Direct costs</E>
                             means the expenditures actually incurred by OFHEO in searching for and reproducing records to respond to a request for information. In the case of a commercial use request, the term also means those expenditures OFHEO actually incurs in reviewing records to respond to the request. The direct costs shall include the cost of the time of the employee performing the work, determined in accordance with § 1710.22(b)(1)(i), the cost of any computer searches, determined in accordance with § 1710.22(b)(1)(ii), and the cost of operating duplication equipment. Not included in direct costs are overhead expenses such as costs of space, and heating or lighting the facility in which the records are stored. Direct costs also include the costs incurred by OFHEO for any contract services that may be needed to respond to a request. 
                        </P>
                        <STARS/>
                        <P>
                            (f) 
                            <E T="03">Reproduce</E>
                             and 
                            <E T="03">reproduction</E>
                             means the process of making a copy of a record necessary to respond to a request for information. Such copies take the form of paper copy, microfilm, audio-visual materials, or machine readable documentation, 
                            <E T="03">e.g.,</E>
                             magnetic tape or disk. The copy provided shall be in the form or format requested, provided the record is readily reproducible in that form or format with reasonable effort, and shall be in a form reasonably usable by the requesters. 
                        </P>
                        <STARS/>
                        <P>13. Revise § 1710.22 to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1710.22 </SECTNO>
                        <SUBJECT>Fees to be charged—general. </SUBJECT>
                        <P>
                            (a) Generally, the fees charged for requests for records pursuant to the Freedom of Information Act will cover the full allowable direct costs of searching for, reproducing, and reviewing records that are responsive to a request for information. Fees will be assessed according to the schedule contained in paragraph (b) of this section and the category of requesters described in § 1710.23 of this subpart for services rendered by OFHEO staff in responding to, and processing requests for, records under this part. Fees 
                            <PRTPAGE P="33796"/>
                            assessed shall be paid by check or money order payable to the Office of Federal Housing Enterprise Oversight. 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Types of charges.</E>
                             The types of charges that may be assessed in connection with the production of records in response to a FOIA request are as follows: 
                        </P>
                        <P>
                            (1) 
                            <E T="03">Searches.</E>
                             (i) 
                            <E T="03">Manual searches for records.</E>
                             OFHEO will charge for actual search time, billed in 15-minute segments, at a rate determined by whether the employee performing the work is classified as clerical, professional, or executive. The hourly fee for each classification is based on the average of the actual compensation (salary and benefits) of employees in the classification and is adjusted periodically to reflect significant changes in the average compensation of the class. The “executive” classification includes the senior management of OFHEO, 
                            <E T="03">i.e.</E>
                             Director, Deputy Director, Associate Directors and Deputy Associate Directors. The “clerical” classification includes employees performing primarily secretarial, clerical, or ministerial tasks. The “professional” classification includes all positions not classified as “executive” or “clerical.” A current fee schedule is available on electronically at http://www.ofheo.gov/docs/ or by regular mail. 
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Computer searches for records.</E>
                             Requesters will be charged at the actual direct costs of conducting a search using existing programming. These direct costs will include the cost of operating the computer equipment for that portion of operating time that is directly attributable to searching for records and the cost of the time of the employee performing the work, determined as described in paragraph (b)(1)(i) of this section. A charge will also be made for any substantial amounts of special supplies or materials used to contain, present, or make available the output of computers, based upon the prevailing levels of costs to OFHEO for the type and amount of such supplies of materials that are used. Nothing in this paragraph shall be construed to entitle any person or entity, as of right, to any services in connection with computerized records, other than services to which such person or entity may be entitled under the provisions of this subpart. 
                        </P>
                        <P>
                            (iii) 
                            <E T="03">Unproductive searches.</E>
                             OFHEO may charge search fees even if no records are found that are responsive to the request or if the records found are exempt from disclosure. 
                        </P>
                        <P>
                            (2) 
                            <E T="03">Reproduction.</E>
                             Records will be photocopied at a rate of $.15 per page. For copies prepared by computer, such as tapes or printouts, the requester will be charged the actual cost, including operator time, of production of the tape or printout. For other methods of reproduction, the actual direct costs of reproducing the record(s) will be charged. 
                        </P>
                        <P>
                            (3) 
                            <E T="03">Review.</E>
                             Only requesters who are seeking records for commercial use may be charged for time spent reviewing records to determine whether they are exempt from mandatory disclosure. Charges may be assessed only for initial review, 
                            <E T="03">i.e.,</E>
                             the review undertaken the first time OFHEO analyzes the applicability of a specific exemption to a particular record or portion of a record. Records or portions of records withheld in full under an exemption that is subsequently determined not to apply may be reviewed again to determine the applicability of other exemptions not previously considered. The costs for such a review are properly assessable. 
                        </P>
                        <P>
                            (4) 
                            <E T="03">Other services and materials.</E>
                             Where OFHEO elects, as a matter of administrative discretion, to comply with a request for a special service or materials, such as certifying that records are true copies or sending records by special methods, the actual direct costs of providing the service or materials will be charged. 
                        </P>
                        <P>14. Amend § 1710.23 by revising paragraph (g) to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 1710.23 </SECTNO>
                        <SUBJECT>Fees to be charged-categories of requesters. </SUBJECT>
                        <STARS/>
                        <P>
                            (g) For purposes of paragraph (e) of this section, the term “search time” has as its basis, manual search. To apply this term to searches made by computer, OFHEO will determine the hourly cost of operating the computer equipment and the operator's time determined as described in paragraph (b)(1)(i) of § 1710.22. When the cost of the search (including the operator's time and the cost of operating the computer equipment to process a request) equals the equivalent dollar amount of two hours of the time of the person performing the work, 
                            <E T="03">i.e.,</E>
                             the operator, OFHEO will begin assessing charges for the computer. 
                        </P>
                    </SECTION>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart E—Testimony and Production of Documents in Legal Proceedings in Which OFHEO Is Not a Named Party </HD>
                    </SUBPART>
                    <P>15. Amend § 1710.38 by revising paragraph (a) to read as follows: </P>
                    <SECTION>
                        <SECTNO>§ 1710.38 </SECTNO>
                        <SUBJECT>Fees. </SUBJECT>
                        <STARS/>
                        <P>
                            (a) 
                            <E T="03">Searches for documents.</E>
                             OFHEO will charge for the actual search time of the employee performing the work, billed in 15-minute segments, as described in § 1710.22(b)(i). 
                        </P>
                        <STARS/>
                    </SECTION>
                    <SIG>
                        <DATED>Dated: May 22, 2000.</DATED>
                        <NAME>Armando Falcon, Jr.,</NAME>
                        <TITLE>Director, Office of Federal Housing Enterprise Oversight. </TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13194 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4220-01-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Airspace Docket No. 00-ANM-07]</DEPDOC>
                <SUBJECT>Proposed Modification of Class E Airspace, Wenatchee, WA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P> Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice proposes to modify the Wenatchee, WA, Class E airspace to remove the Fancher Field airspace exclusion at the Panghorn Memorial Airport, Wenatchee, WA.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before July 10, 2000.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send comments on the proposal in triplicate to: Manger, Airspace Branch, ANM-520, Federal Aviation Administration, Docket No. 00-ANM-07, 1601 Lind Avenue SW, Renton, Washington 98055-4056.</P>
                    <P>The official docket may be examined in the Office of the Regional Chief Counsel for the Northwest Mountain Region at the same address.</P>
                    <P>An informal docket may also be examined during normal business hours in the office of the Manger, Air Traffic Division, Airspace Branch, at the address listed above.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Brian Durham, ANM-520.7, Federal Aviation Administration, Docket No. 00-ANM-07, 1601 Lind Avenue SW, Renton, Washington 98055-4056: telephone number: (425) 227-2527.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    Interested parties are invited to participate in this proposed rulemaking by submitting such written data, views, or arguments, as they may desire. Comments that provide the factual basis supporting the views and suggestions presented are particularly helpful in developing reasoned regulatory decisions on the proposal. Comments are specifically invited on the overall 
                    <PRTPAGE P="33797"/>
                    regulatory, aeronautical, economic, environmental, and energy related aspects of the proposal. Communications should identify the airspace docket number and be submitted in triplicate to the address listed above. Commenters wishing the FAA to acknowledge receipt of their comments on this notice must submit, with ethos comments, a self-addressed stamped postcard on which the following statement is made: “Comments to Airspace Docket No. 00-ANM-07.” The postcard will be date/time stamped and returned to the commenter. All communications received on or before the specified closing date for comments will be considered before taking action on the proposed rule. The proposal contained in this notice may be changed in the light of comments received. All comments submitted will be available for examination at the address listed above both before and after the closing date for comments. A report summarizing each substantive public contact with FAA personnel concerned with this rulemaking will be filed in the docket.
                </P>
                <HD SOURCE="HD1">Availability of NPRM's</HD>
                <P>Any person may obtain a copy of this NPRM by submitting a request to the Federal Aviation Administration, Airspace Branch, ANM-520, 1601 Lind Avenue SW, Renton, Washington 98055-4056. Communications must identify the notice number of this NPRM. Persons interest in being placed on a mailing list for future NPRM's should also request a copy of Advisory Circular No. 11-2A, which describes the application procedure.</P>
                <HD SOURCE="HD1">The Proposal</HD>
                <P>The FAA is considering an amendment to Title 14 Code of Federal Regulations, part 71 (14 CFR part 71) by modifying Class E airspace at Wenatchee, WA, in order to remove the Fancher Field airspace exclusion in the legal description for the Panghorn Memorial Airport, Wenatchee, WA. Fancher Field has been abandoned negating the requirement for it's Class E2 airspace exclusion. This airspace modification would delete the airspace requirement for Fanche Field and correct the legal description for Wenatchee, WA. The FAA establishes Class E airspace where necessary to contain aircraft transitioning between the terminal and en route environments. The intended effect of this proposal is designed to provide for the safe and efficient use of the navigable airspace. This proposal would promote safe flight operations under Instrument Flight Rules (IFR) at the Wenatchee Airport and between the terminal and en route transition stages.</P>
                <P>The area would be depicted on aeronautical charts for pilot reference. The coordinates for this airspace docket are based on North American Datum 83. Class E airspace areas extending upward from 700 feet or more above the surface of the earth, are published in Paragraph 6005, of FAA Order 7400.9G dated September 1, 1999, and effective September 16, 1999, which is incorporated by reference in 14 CFR 71.1. The Class E airspace designation listed in this document would be published subsequently in the Order.</P>
                <P>The FAA has determined that this proposed regulation only invokes an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore, (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a Regulatory Evaluation as the anticipated impact is so minimal. Since this is a routine matter that will only affect air traffic procedures and air navigation, it is certified that this rule, when promulgated, will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration proposes to amend 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, CLASS B, CLASS C, CLASS D, AND CLASS E AIRSPACE AREAS; AIRWAYS; ROUTES AND REPORTING POINTS</HD>
                    <P>1. The authority citation for 14 CFR part 71 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(g), 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 71.1 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. The incorporation by reference in 14 CFR 71.1 of the Federal Aviation Administration Order 7400.9G, Airspace Designations and Reporting Points, dated September 1, 1999, and effective September 16, 1999, is amended as follows:  </P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">Paragraph 6005 Class E airspace areas extending upward from 700 feet or more above the surface of the earth.</FP>
                            <STARS/>
                            <HD SOURCE="HD1">ANM WA E2 Wenatchee, WA</HD>
                            <FP SOURCE="FP-2">Wenatchee, Panghorn Memorial Airport, WA</FP>
                            <FP SOURCE="FP1-2">(Lat. 47°23′55″ N, long. 120°12′24″ W)</FP>
                            <P>Within a 4 mile radius of Panghorn Memorial Airport, and within a 2.7 miles each side of the Wenatchee VOR/DME 124° radial extending from the 4-mile radius to 7 miles southeast of the VOR/DME.</P>
                        </EXTRACT>
                        <STARS/>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Seattle, Washington, on May 12, 2000.</DATED>
                        <NAME>Daniel A. Boyle,</NAME>
                        <TITLE>Acting Manager, Air Traffic Division, Northwest Mountain Region.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13175 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <CFR>40 CFR Part 271 </CFR>
                <DEPDOC>[FRL-6704-8] </DEPDOC>
                <SUBJECT>Minnesota: Final Authorization of State Hazardous Waste Management Program Revisions </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>
                        Minnesota has applied to EPA for Final authorization of the changes to its hazardous waste program under the Resource Conservation and Recovery Act (RCRA). These changes include granting the State authority for the wood preserving rules, petroleum refinery sludge listings, and technical amendments to existing regulations. EPA proposes to grant final authorization to Minnesota. In the “Rules and Regulations” section of this 
                        <E T="04">Federal Register</E>
                        , EPA is authorizing the changes by an immediate final rule. EPA did not make a proposal prior to the immediate final rule because we believe this action is not controversial and do not expect comments that oppose it. We have explained the reasons for this authorization in the preamble to the immediate final rule. Unless we get written comments which oppose this authorization during the comment period, the immediate final rule will become effective on the date it establishes, and we will not take further action on this proposal. If we get comments that oppose this action, we will withdraw the immediate final rule and it will not take effect. We will then respond to public comments in a later final rule based on this proposal. You 
                        <PRTPAGE P="33798"/>
                        may not have another opportunity for comment. If you want to comment on this action, you must do so at this time. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Send your written comments by June 26, 2000.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send written comments referring to Docket Number Minnesota ARA 8, to Gary Westefer, Minnesota Regulatory Specialist, U.S. EPA Region 5, DM-7J, 77 West Jackson Boulevard, Chicago, Illinois 60604, (312) 886-7450. Please refer to Docket Number MN ARA 8. You can examine copies of the materials submitted by Minnesota during normal business hours at the following locations: Minnesota Pollution Control Agency, 520 Lafayette Road, North, St. Paul, Minnesota 55155, contact Nathan Cooley (651) 297-7544, and EPA Region 5, contact Gary Westefer, Minnesota Regulatory Specialist, U.S. EPA Region 5, DM-7J, 77 West Jackson Boulevard, Chicago, Illinois 60604, (312) 886-7450. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Gary Westefer at the above address and phone number.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    For additional information, please see the immediate final rule published in the “Rules and Regulations” section of this 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <DATED>Dated: May 3, 2000. </DATED>
                    <NAME>Elissa Speizman, </NAME>
                    <TITLE>Acting Regional Administrator, Region 5 . </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-12954 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <CFR>47 CFR Part 73 </CFR>
                <DEPDOC>[DA 00-999; MM Docket No. 00-74; RM-9862] </DEPDOC>
                <SUBJECT>Radio Broadcasting Services; Sterling, CO </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document requests comments on a petition for rule making filed on behalf of Ling Broadcasting requesting the allotment of Channel 248C3 to Sterling, Colorado, as that locality's third local FM transmission service. Coordinates used for this proposal are 40-37-32 NL and 103-12-25 WL. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be filed on or before June 26, 2000, and reply comments on or before July 11, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Secretary, Federal Communications Commission, Washington, DC 20554. In addition to filing comments with the FCC, interested parties should serve the petitioner's counsel, as follows: A. Wray Fitch, III, Esq., Gamon &amp; Grange, P.C., 8280 Greensboro Drive, 7th Floor, McLean, VA 22102-3807. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Nancy Joyner, Mass Media Bureau, (202) 418-2180. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This is a synopsis of the Commission's Notice of Proposed Rule Making, MM Docket No. 00-74, adopted April 26, 2000, and released May 5, 2000. The full text of this Commission decision is available for inspection and copying during normal business hours in the FCC's Reference Information Center (Room CY-A257), 445 Twelfth Street, SW., Washington, DC. The complete text of this decision may also be purchased from the Commission's copy contractor, International Transcription Service, Inc., 1231 20th Street, NW., Washington, DC 20036, (202) 857-3800. </P>
                <P>Provisions of the Regulatory Flexibility Act of 1980 do not apply to this proceeding. </P>
                <P>
                    Members of the public should note that from the time a Notice of Proposed Rule Making is issued until the matter is no longer subject to Commission consideration or court review, all 
                    <E T="03">ex parte</E>
                     contacts are prohibited in Commission proceedings, such as this one, which involve channel allotments. See 47 CFR 1.1204(b) for rules governing permissible 
                    <E T="03">ex parte</E>
                     contacts. 
                </P>
                <P>For information regarding proper filing procedures for comments, See 47 CFR 1.415 and 1.420. </P>
                <SIG>
                    <FP>Federal Communications Commission. </FP>
                    <NAME>John A. Karousos,</NAME>
                    <TITLE>Chief, Allocations Branch, Policy and Rules Division, Mass Media Bureau.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13141 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6712-01-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <CFR>47 CFR Part 73 </CFR>
                <DEPDOC>[DA 00-999; MM Docket No. 00-75; RM-9863] </DEPDOC>
                <SUBJECT>Radio Broadcasting Services; Kahului, HI </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document requests comments on a petition for rule making filed by New West Broadcasting requesting the allotment of Channel 223C2 to Kahului, HI, as that community's second local FM transmission service. Coordinates used for this proposal are 20-50-24 NL and 156-23-14 WL. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be filed on or before June 26, 2000, and reply comments on or before July 11, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Secretary, Federal Communications Commission, Washington, DC 20554. In addition to filing comments with the FCC, interested parties should serve the petitioner, as follows: New West Broadcasting, c/o Robin B. Thomas, President, 1001 Weatherby Drive, Cheyenne, WY 82007. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Nancy Joyner, Mass Media Bureau, (202) 418-2180. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This is a synopsis of the Commission's Notice of Proposed Rule Making, MM Docket No. 00-75, adopted April 26, 2000, and released May 5, 2000. The full text of this Commission decision is available for inspection and copying during normal business hours in the FCC's Reference Information Center (Room CY-A257), 445 Twelfth Street, SW., Washington, DC. The complete text of this decision may also be purchased from the Commission's copy contractor, International Transcription Service, Inc., 1231 20th Street, NW., Washington, DC 20036, (202) 857-3800. </P>
                <P>Provisions of the Regulatory Flexibility Act of l980 do not apply to this proceeding. </P>
                <P>
                    Members of the public should note that from the time a Notice of Proposed Rule Making is issued until the matter is no longer subject to Commission consideration or court review, all 
                    <E T="03">ex parte</E>
                     contacts are prohibited in Commission proceedings, such as this one, which involve channel allotments. See 47 CFR 1.1204(b) for rules governing permissible 
                    <E T="03">ex parte</E>
                     contacts. 
                </P>
                <P>For information regarding proper filing procedures for comments, See 47 CFR 1.415 and 1.420. </P>
                <SIG>
                    <FP>Federal Communications Commission. </FP>
                    <NAME>John A. Karousos,</NAME>
                    <TITLE>Chief, Allocations Branch, Policy and Rules Division, Mass Media Bureau. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13140 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6712-01-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="33799"/>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <CFR>47 CFR Part 73 </CFR>
                <DEPDOC>[DA 00-999; MM Docket No. 00-73; RM-9861] </DEPDOC>
                <SUBJECT>Radio Broadcasting Services; Hornbrook, CA </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document requests comments on a petition for rule making filed on behalf of Logan and Company requesting the allotment of Channel 255A to Hornbrook, California, as that locality's first local aural transmission service. As Hornbrook is not incorporated or listed in the U.S. Census, information is requested regarding the attributes of that locality to determine whether it is a 
                        <E T="03">bona fide</E>
                         community for allotment purposes. Coordinates used for this proposal are 41-53-06 NL and 122-35-03 WL. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be filed on or before June 26, 2000, and reply comments on or before July 11, 2000. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Secretary, Federal Communications Commission, Washington, DC 20554. In addition to filing comments with the FCC, interested parties should serve the petitioner's counsel, as follows: James A. Koerner, Esq., Koerner &amp; Olender, P.C., 5809 Nicholson Lane, Suite 124, North Bethesda, MD 20852. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Nancy Joyner, Mass Media Bureau, (202) 418-2180. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This is a synopsis of the Commission's Notice of Proposed Rule Making, MM Docket No. 00-73, adopted April 26, 2000, and released May 5, 2000. The full text of this Commission decision is available for inspection and copying during normal business hours in the FCC's Reference Information Center (Room CY-A257), 445 Twelfth Street, SW., Washington, DC. The complete text of this decision may also be purchased from the Commission's copy contractor, International Transcription Service, Inc., 1231 20th Street, NW., Washington, DC 20036, (202) 857-3800. </P>
                <P>Provisions of the Regulatory Flexibility Act of 1980 do not apply to this proceeding. </P>
                <P>
                    Members of the public should note that from the time a Notice of Proposed Rule Making is issued until the matter is no longer subject to Commission consideration or court review, all 
                    <E T="03">ex parte</E>
                     contacts are prohibited in Commission proceedings, such as this one, which involve channel allotments. See 47 CFR 1.1204(b) for rules governing permissible 
                    <E T="03">ex parte</E>
                     contacts. 
                </P>
                <P>For information regarding proper filing procedures for comments, See 47 CFR 1.415 and 1.420. </P>
                <SIG>
                    <FP>Federal Communications Commission. </FP>
                    <NAME>John A. Karousos, </NAME>
                    <TITLE>Chief, Allocations Branch, Policy and Rules Division, Mass Media Bureau. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13139 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6712-01-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <CFR>47 CFR Part 73 </CFR>
                <DEPDOC>[DA No. 00-946, MM Docket No. 99-237; RM-9663] </DEPDOC>
                <SUBJECT>Radio Broadcasting Services; Medina, TX </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule; dismissal. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document denies a petition for rule making filed by Medina Radio Broadcasting Company requesting the allotment of Channel 296A at Medina, Texas. 
                        <E T="03">See</E>
                         64 FR 36324, July 6, 1999. This document in this proceeding questioned community status and requested commenting parties to present the Commission with information demonstrating community status. Based on the totality of evidence submitted, we do not believe that Medina qualifies as a community for allotment purposes and that it would not serve the public interest to make a channel allotment in response to Medina Radio's proposal. 
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Kathleen Scheuerle, Mass Media Bureau, (202) 418-2180. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This is a summary of the Commission's Report and Order, MM Docket No. 99-237, adopted April 19, 2000, and released April 25, 2000. The full text of this Commission decision is available for inspection and copying during normal business hours in the Commission's Reference Center, 445 12th Street, SW, Washington, DC. The complete text of this decision may also be purchased from the Commission's copy contractors, International Transcription Services, Inc., 1231 20th Street, NW., Washington, DC. 20036, (202) 857-3800, facsimile (202) 857-3805. </P>
                <SIG>
                    <FP>Federal Communications Commission. </FP>
                    <NAME>John A. Karousos, </NAME>
                    <TITLE>Chief, Allocations Branch, Policy and Rules Division, Mass Media Bureau. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13136 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6712-01-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">GENERAL SERVICES ADMINISTRATION </AGENCY>
                <CFR>48 CFR Parts 552 and 570</CFR>
                <DEPDOC>[APD 2800.12B, Case No. GSAR 5-422] </DEPDOC>
                <RIN>RIN 3090-AH03</RIN>
                <SUBJECT>General Services Administration Acquisition Regulation: Tax Adjustment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Acquisition Policy, GSA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The General Services Administration (GSA) proposes to amend the General Services Administration Acquisition Regulation (GSAR) by adding a new clause Tax Adjustment, and by revising the section GSAR contract clauses.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments should be submitted on or before July 24, 2000 to be considered in the formulation of a final rule.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Interested parties should submit written comments to: General Services Administration, Office of Acquisition Policy, GSA Acquisition Policy Division (MVP), 1800 F Street, NW, Room 4027, Washington, DC 20405.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Cecelia L. Davis, GSA Acquisition Policy Division, (202) 219-0202.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <HD SOURCE="HD1">A. Background</HD>
                <P>GSA proposes to amend the GSAR by revising Parts 552 and 570 to prescribe and to incorporate a new clause 552.270-30, Tax Adjustment. The clause will be incorporated in acquisitions of leasehold interest in real property when GSA determined that a tax adjustment is necessary.</P>
                <HD SOURCE="HD1">B. Executive Order 12866</HD>
                <P>This regulatory action was not subject to Office of Management and Budget review under Executive Order 12866, dated September 30, 1993, and is not a major rule under 5 U.S.C. 804.</P>
                <HD SOURCE="HD1">C. Regulatory Flexibility Act</HD>
                <P>
                    GSA does not expect this proposed rule to have a significant economic impact on a substantial number of small 
                    <PRTPAGE P="33800"/>
                    entities within the meaning of the Regulatory Flexibility Act, 5 U.S.C. 601, 
                    <E T="03">et seq.,</E>
                     because the rule simply provides a mechanism for adjusting rent to account for changes in real estate taxes.
                </P>
                <HD SOURCE="HD1">D. Paperwork Reduction Act</HD>
                <P>
                    The Paperwork Reduction Act does not apply because the changes to the GSAR do not impose recordkeeping or information collection requirements, or otherwise collect information from offerors, contractors, or members of the public that require approval of the Office of Management and Budget under 44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subject in 48 CFR Part 552 and 570</HD>
                    <P>Government procurement.</P>
                </LSTSUB>
                <P>Accordingly, GSA proposes to amend 48 CFR Part 552 and 570 as follows:</P>
                <P>1. The authority citation for 48 CFR Parts 552 and 570 continues to read as follows:</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>40 U.S.C. 486(c).</P>
                </AUTH>
                <PART>
                    <HD SOURCE="HED">PART 552—SOLICITATION PROVISIONS AND CONTRACT CLAUSES</HD>
                    <P>2. Section 552.270-30 is added to read as follows:</P>
                    <SECTION>
                        <SECTNO>552.270-30 </SECTNO>
                        <SUBJECT>Tax Adjustment</SUBJECT>
                        <P>As prescribed in 570.603, inset the following clause:</P>
                        <EXTRACT>
                            <HD SOURCE="HD1">Tax Adjustment (Date)</HD>
                            <P>
                                (a) 
                                <E T="03">Definitions.</E>
                                 “Base year taxes,” as used in this clause, mean the real estate taxes for the first twelve (12) month period coincident with full assessment, or an amount negotiated by the parties that reflect an agreed on base for a fully assessed value of the property.
                            </P>
                            <P>“Full assessment,” as used in this clause, means that the taxing jurisdiction has considered all contemplated improvements to the assessed property in the valuation of the same. Partial assessments for newly constructed projects or for projects or for projects under construction, conversion, or renovation will not be used for establishing the Government's base year for taxes.</P>
                            <P>“Real estate taxes,” as used in this clause, mean only those taxes assessed against the building or the land on which the building is located, without regard to benefit to the property, for the purpose of funding general government services. Real estate taxes shall not include general or special assessments, business improvement district assessments, or any other present or future taxes or governmental charges imposed on Lessor or assessed against the building or the land upon which the building is located.</P>
                            <P>
                                (b) 
                                <E T="03">Adjustment for changes in real estate taxes.</E>
                                 This lease provides for adjustments due to changes in real estate taxes on land and buildings occupied by the Government under this lease. Adjustments shall apply to each tax year during the lease term after the base tax year. Under the procedures established in this clause, the Government shall either:
                            </P>
                            <P>(1) Make a single annual lump sum payment to the Lessor for its share of any increase in real estate taxes during the lease term over the amount established as the base year taxes.</P>
                            <P>(2) Receive an annual rental credit or lump sum payment from the Lessor for its share of any decreases in real estate taxes during the lease term below the amount established as the base year taxes.</P>
                            <P>
                                (c) 
                                <E T="03">Notices regarding real estate taxes.</E>
                                 The Lessor shall furnish the Contracting Officer with copies of each of the following within ten (10) calendar days of receipt:
                            </P>
                            <P>(1) Any notice which may affect the valuation of land and buildings covered by this lease for real estate tax purposes.</P>
                            <P>(2) Any notice of a tax credit or tax refund related to land and buildings covered by this lease.</P>
                            <P>(3) Each tax bill related to land and building covered by this lease.</P>
                            <P>
                                (d) 
                                <E T="03">Increases in real estate taxes.</E>
                                 The following procedures apply for any tax year in which the real estate taxes increase over the base year taxes.
                            </P>
                            <P>
                                (1) 
                                <E T="03">Invoice.</E>
                                 The Lessor shall submit a proper invoice (as described in the Prompt Payment clause of this lease, GSAR 552.232-75) for the tax adjustment. The invoice must include the calculation of the adjustment for the tax year. The Lessor must also provide a copy of all paid tax receipts for the tax year with the invoice. If the taxing authority does not give tax receipts, the Lessor must provide other similar evidence of payment acceptable to the Contract Officer. The Lessor must submit the invoice together with tax receipts or other evidence of payment no later than sixty (60) days after the date that the final tax payment for the year is due from the Lessor to the taxing authority.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Payment.</E>
                                 Upon receipt of a proper invoice and evidence of payment, the Government shall make payment no later than thirty (30) days after receipt of the invoice or thirty (30) days after the anniversary date of the lease, whichever is later. If the lease terminates before the end of a tax year, payment for the tax increase due will be prorated based on the number of days the Government occupied the space.
                            </P>
                            <P>
                                (3) 
                                <E T="03">Waiver of right to adjustment.</E>
                                 If the Lessor fails to submit a proper invoice and tax receipts or other evidence of payment within sixty (60) days after the date that the final tax payment for the year is due, then the Lessor waives its right to receive payment for the increased taxes under this clause.
                            </P>
                            <P>
                                (e) 
                                <E T="03">Decreases in real estate taxes.</E>
                                 The following procedures apply for any tax year in which the real estate taxes decrease from the base year taxes or during which the Lessor receives a refund or tax deduction for real estate taxes.
                            </P>
                            <P>(1) The Government shall be entitled to and shall receive a pro rata credit for the reduction in taxes, regardless of whether the Government has not yet made the tax payment for that year.</P>
                            <P>(2) During the lease term, the Government shall apply any credit as a deduction from the rent.</P>
                            <P>(3) For any credit due after the expiration or earlier termination of the lease, at the Contracting Officer's direction, the Lessor shall either make a lump sum payment to the Government or provide a rental credit under a succeeding lease. This includes, but is not limited to, credits resulting from a tax decrease pursuant to a tax credit due the Lessor, a reduction in the tax assessment, or a tax appeal proceeding for a year or a portion of the lease. If directed to remit a lump sum payment, the Lessor must make payment to the Government within fifteen (15) days of the Contracting Officer's direction. If the credit due the Government is not paid by the due date, interest shall accrue on the late payment at the rate established by the Secretary of the Treasury under Section 12 of the Contract Disputes Act of 1978 (41 U.S.C. 611) in effect on the day after the due date. The Government shall have the right to pursue the outstanding balance of any tax credit using all collection methods available to the United States to collect debts. Such collection rights survive the expiration of this lease.</P>
                            <P>
                                (f) 
                                <E T="03">Calculating tax share.</E>
                                 The Government shall pay its share of tax increases or receive its share of any tax decrease based on the ratio of the rentable square feet occupied by the Government to the total rentable square feet in the building or complex (percentage of occupancy). For this lease, the Government's percentage of occupancy as of the effective date of the lease is _%. This percentage shall take into account additions or reductions of the amount of space as may be contemplated in this lease or amendments hereto. The block and lot/parcel or other identification numbers for the property, building(s) and parking areas(s) occupied under this lease are __.
                            </P>
                            <P>
                                (g) 
                                <E T="03">Appeals to tax assessments.</E>
                                 The Government may direct the Lessor upon reasonable notice to initiate a tax appeal or the Government may decide to contest a tax assessment on behalf of both the Government and the Lessor or for the Government alone. The Lessor shall furnish to the Government information necessary for appeal of the tax assessment in accordance with the filing requirements on its own behalf or on behalf of both the Government and the Lessor, the Lessor shall cooperate and use all reasonable efforts including, but not limited to, affirming the accuracy of the documents, executing documents required for any legal proceeding, and taking such other actions as may be required. If the Lessor initiates an appeal on behalf of the Government, the Government and the Lessor will enter into an agreement to establish a method for sharing expenses and tax savings.
                            </P>
                            <FP>(End of Clause)</FP>
                        </EXTRACT>
                    </SECTION>
                </PART>
                <PART>
                    <HD SOURCE="HED">PART 570—ACQUIRING LEASEHOLD INTERESTS IN REAL PROPERTY</HD>
                    <P>3. Section 570.603 is amended by adding a new prescription at the end of the section to read as follows:</P>
                    <SECTION>
                        <SECTNO>570.603 </SECTNO>
                        <SUBJECT>GSAR contract clauses.</SUBJECT>
                        <STARS/>
                    </SECTION>
                    <SECTION>
                        <PRTPAGE P="33801"/>
                        <SECTNO>552.270-30 </SECTNO>
                        <SUBJECT>Tax Adjustment. Insert this clause in solicitations and contracts if you determine that a tax adjustment is necessary.</SUBJECT>
                    </SECTION>
                    <SIG>
                        <DATED>Dated: May 17, 2000.</DATED>
                        <NAME>Sue McIver,</NAME>
                        <TITLE>Acting Deputy Associated Administrator for Acquisition Policy.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13157  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6820-61-M</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration </SUBAGY>
                <CFR>50 CFR Part 622 </CFR>
                <DEPDOC>[I.D. 051600A] </DEPDOC>
                <SUBJECT>Gulf of Mexico Fishery Management Council; Public Hearings </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public hearings; request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Gulf of Mexico Fishery Management Council (Council) will convene public hearings to receive comments on its proposed Amendment 7 to the Fishery Management Plan for the Stone Crab Fishery of the Gulf of Mexico (FMP). Amendment 7 proposes to extend Florida's trap certificate program for the commercial stone crab fishery into Federal waters off the west coast of Florida. The objective of this program is to reduce, over time, the number of traps used in the fishery to an optimum number necessary to harvest the maximum sustainable yield (MSY). </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The Council will accept written comments on the proposed amendment through June 26, 2000. The public hearings will be held in June. See 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         for specific dates and times of the public hearings. 
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments should be sent to Wayne E. Swingle, Executive Director, Gulf of Mexico Fishery Management Council, 3018 U.S. Highway 301, North, Suite 1000, Tampa, Florida 33619. Copies of draft Amendment 7 are available from Mr. Wayne Swingle, Executive Director, Senior Fishery Biologist, Gulf of Mexico Fishery Management Council, 3018 U.S. Highway 301, North, Suite 1000, Tampa, Florida 33619; telephone: 813-228-2815; fax: 813-769-4520. See 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         for specific hearing locations. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Wayne Swingle, Executive Director, Senior Fishery Biologist, Gulf of Mexico Fishery Management Council, 3018 U.S. Highway 301, North, Suite 1000, Tampa, Florida 33619; telephone: 813-228-2815. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>There are about 1.4 million stone crab traps off Florida; the Florida Fish &amp; Wildlife Conservation Commission (FFWCC) estimates that it would take only 600,000 traps to take the MSY from this fishery. The FFWCC, after working with the stone crab industry and Council over the past 4 years, has adopted a rule, effective July 1, 2000, under which a State trap certificate program will gradually reduce the number of traps over a 30-year period. This is a certificate-based attrition program that “grandfathers” fishermen into the program with their present number of traps and then will reduce slowly the trap numbers to the optimum level by reducing the number of certificates whenever they are sold. The Florida Legislature recently authorized license and penalty fees for this certificate program. </P>
                <HD SOURCE="HD1">Time and Location for Public Hearings </HD>
                <P>Public hearings for Amendment 7 will be held at the following locations, dates, and times. </P>
                <P>1. June 6, 2000, 7 p.m., Naples Depot Civic Cultural Center, 1051 Fifth Avenue South, Naples, Florida 34102; telephone: 941-262-1776. </P>
                <P>2. June 7, 2000, 7 p.m., Banana Bay Resort &amp; Marina, 4590 Overseas Highway, Marathon, Florida 33050; telephone: 305-743-3500. </P>
                <P>3. June 13, 2000, 7 p.m., Jaycee Building, 501 SE 7th Avenue, Crystal River, Florida 34429; telephone: 352-795-4217. </P>
                <P>4. June 14, 2000, 7 p.m., Steinhatchee Elementary School, 1st Avenue South, Steinhatchee, Florida 32359; telephone: 352-498-3303. </P>
                <P>The Council will also hear public testimony before taking final action on Amendment 7 on July 12, 2000, at its meeting in Key Largo, Florida. </P>
                <HD SOURCE="HD1">Special Accommodations </HD>
                <P>
                    These meetings are physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to Anne Alford at the Council office (see 
                    <E T="02">ADDRESSES</E>
                    ) by May 30, 2000. 
                </P>
                <SIG>
                    <DATED>Dated: May 19, 2000. </DATED>
                    <NAME>Bruce Moorehead, </NAME>
                    <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13187 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-22-U </BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>65</VOL>
    <NO>102</NO>
    <DATE>Thursday, May 25, 2000 </DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="33802"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Agricultural Marketing Service </SUBAGY>
                <DEPDOC>[TM-00-06] </DEPDOC>
                <SUBJECT>Notice of Meeting of the National Organic Standards Board </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Agricultural Marketing Service, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Federal Advisory Committee Act, as amended, the Agricultural Marketing Service (AMS) announces a forthcoming meeting of the National Organic Standards Board (NOSB). </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>June 6, 2000, from 9 a.m. to 5 p.m., and June 7, 2000, 9 a.m. to 5 p.m. (Eastern Daylight Time each day). </P>
                </DATES>
                <PREAMHD>
                    <HD SOURCE="HED">Place:</HD>
                    <P>Hilton Crystal City at National Airport, 2399 Jefferson Davis Highway, Arlington, VA 22202, Telephone: (703) 418-6800. </P>
                </PREAMHD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Keith Jones, Program Manager, National Organic Program, USDA-AMS-TMP-NOP, Room 2945-So., Ag Stop 0268, P.O. Box 96456, Washington, D.C. 20090-6456, Telephone: (202) 720-3252. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Section 2119 (7 U.S.C. 6518) of the Organic Foods Production Act of 1990 (OFPA), as amended (7 U.S.C. Section 6501 
                    <E T="03">et seq.</E>
                    ) requires the establishment of the NOSB. The purpose of the NOSB is to assist in the development of standards for substances to be used in organic production and to advise the Secretary on any other aspects of the implementation of OFPA. The NOSB met for the first time in Washington, D.C., in March 1992 and currently has six committees working on various aspects of the program. The committees are: Crops Standards; Processing, Labeling and Packaging Standards; Livestock Standards; Accreditation; Materials; and International Issues. 
                </P>
                <P>In August of 1994, the NOSB provided its initial recommendations for the National Organic Program (NOP) to the Secretary of Agriculture. Since that time the NOSB has submitted 30 addenda to its recommendations and reviewed more than 170 substances for inclusion on the National List of Allowed and Prohibited Substances. The last meeting of the NOSB was held on March 21-22, 2000, in Buena Park, California. </P>
                <P>
                    The Department of Agriculture (USDA) published its re-proposed National Organic Program regulation in the 
                    <E T="04">Federal Register</E>
                     on March 13, 2000 (65 FR 13512). Comments are being accepted until June 12, 2000. Comments may be submitted to: Keith Jones, Program Manager, National Organic Program, USDA-AMS-TMP-NOP, Room 2945-So., Ag Stop 0275, PO Box 96456, Washington, DC 20090-6456. Comments also may be sent by fax to (703) 365-0760 or filed via the Internet through the NOP's homepage at: http://www.ams.usda.gov/nop. Comments should be identified with docket number TMD-00-02-PR. 
                </P>
                <HD SOURCE="HD1">Purpose and Agenda</HD>
                <P>The principal purposes of this meeting are to provide an opportunity for the NOSB to receive committee reports; approve the NOSB's comment to the re-proposed National Organic Program regulation; vote on whether to recommend the addition of ethylene gas and amino acids to the National List; elect new officers of the NOSB; and receive an update regarding certification of aquatic animals from the USDA. Copies of the NOSB final meeting agenda can be requested from Mrs. Toni Strother, USDA-AMS-TMP-NOP, Room 2510-So., Ag Stop 0268, P.O. Box 96456, Washington, D.C. 20090-6456; by phone at (202) 720-3252; or by accessing the NOP website at http://www.ams.usda.gov/nop after May 23, 2000. </P>
                <HD SOURCE="HD1">Type of Meeting</HD>
                <P>This meeting is open to the public. The NOSB has scheduled time for public input on Tuesday, June 6, 2000, from 1:30 p.m. until 4:00 p.m. at the Hilton Crystal City at National Airport, 2399 Jefferson Davis Highway, Arlington, VA 22202. Telephone: (703) 418-6800. Individuals and organizations wishing to make an oral presentation at the meeting should forward the request to Mrs. Strother at the above address or by FAX to (202) 205-7808 by close of business June 2, 2000. While persons wishing to make a presentation may sign up at the door, advance registration will ensure an opportunity to speak during the allotted time period and will help the NOSB to better manage the meeting and accomplish its agenda. Individuals or organizations will be given approximately 5 minutes to present their views. All persons making an oral presentation are requested to provide their comments in writing, if possible. Written submissions may supplement the oral presentation with additional material. Written comments may be submitted to the NOSB at the meeting or to Mrs. Strother after the meeting at the above address. </P>
                <SIG>
                    <DATED>Dated: May 23, 2000. </DATED>
                    <NAME>Sharon Bomer Lauritsen </NAME>
                    <TITLE>Acting Deputy Administrator, Transportation and Marketing </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13289 Filed 5-23-00; 1:35 pm] </FRDOC>
            <BILCOD>BILLING CODE 3410-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>Foreign-Trade Zones Board </SUBAGY>
                <DEPDOC>[Docket 2-2000] </DEPDOC>
                <SUBJECT>Foreign-Trade Zone 193-Pinellas County, FL; Application for Subzone Status, Amendment of Application—RP Scherer Corporation (Gelatin Capsules) </SUBJECT>
                <P>
                    Notice is hereby given that the application of the Pinellas County Board of County Commissioners, grantee of FTZ 193, requesting authority for special-purpose subzone status for the gelatin capsule manufacturing facilities of RP Scherer Corporation (Scherer) located in the St. Petersburg/Clearwater area, Pinellas County, Florida (65 FR 5308, 2/3/00), has been amended to expand the proposed use of zone procedures at the Scherer plant to include the manufacture of a new anti-AIDS drug, using foreign and domestic ingredients. The foreign ingredients include Lopinavir (HTSUS 2933.59.7000—9.3% duty rate). The finished product is classified under HTSUS 3004.70.9010 and is duty free. Scherer will be finishing and encapsulating the finished drug under contract for Abbott Laboratories, Inc., 
                    <PRTPAGE P="33803"/>
                    which has authority from the FTZ Board to produce the drug under zone procedures at its Chicago, Illinois, plant. 
                </P>
                <P>The application remains otherwise unchanged. </P>
                <P>The comment period is reopened until June 26, 2000. </P>
                <SIG>
                    <DATED>Dated: May 17, 2000. </DATED>
                    <NAME>Dennis Puccinelli, </NAME>
                    <TITLE>Acting Executive Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13098 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>International Trade Administration </SUBAGY>
                <DEPDOC>[A-851-802] </DEPDOC>
                <SUBJECT>Preliminary Determination of Critical Circumstances: Certain Small Diameter Carbon and Alloy Seamless Standard, Line and Pressure Pipe From the Czech Republic </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce. </P>
                </AGY>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>May 25, 2000. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>John Brinkmann or Dennis McClure, AD/CVD Enforcement, Office 6, Group II, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Ave, NW, Washington, DC 20230; telephone: (202) 482-4126 or 482-0984, respectively. </P>
                    <HD SOURCE="HD1">The Applicable Statute and Regulations </HD>
                    <P>Unless otherwise indicated, all citations to the statute are references to the provisions effective January 1, 1995, the effective date of the amendments made to the Tariff Act of 1930 (the Act) by the Uruguay Round Agreements Act. In addition, unless otherwise indicated, all citations to the Department's regulations are references to the provisions codified at 19 CFR part 351 (April 1999). </P>
                    <HD SOURCE="HD1">Background </HD>
                    <P>On February 4, 2000, the Department published the preliminary affirmative determination in the antidumping duty investigation on certain small diameter carbon and alloy seamless standard, line and pressure pipe (seamless pipe) from the Czech Republic, 65 FR 5599. On April 18, 2000, the petitioners alleged that there is a reasonable basis to believe or suspect that critical circumstances exist with respect to imports of seamless pipe from the Czech Republic. </P>
                    <HD SOURCE="HD1">Critical Circumstances </HD>
                    <P>Section 733(e)(1) of the Act provides that the Department will preliminarily determine that critical circumstances exist if there is a reasonable basis to believe or suspect that: (A)(i) There is a history of dumping and material injury by reason of dumped imports in the United States or elsewhere of the subject merchandise, or (ii) the person by whom, or for whose account, the merchandise was imported knew or should have known that the exporter was selling the subject merchandise at less than its fair value and that there was likely to be material injury by reason of such sales, and (B) there have been massive imports of the subject merchandise over a relatively short period. Section 351.206(h)(1) of the Department's regulations provides that, in determining whether imports of the subject merchandise have been “massive,” the Department normally will examine: (i) The volume and value of the imports; (ii) seasonal trends; and (iii) the share of domestic consumption accounted for by the imports. In addition, section 351.206(h)(2) of the Department's regulations provides that an increase in imports of 15 percent during the “relatively short period” of time may be considered “massive.” </P>
                    <P>
                        Section 351.206(i) of the Department's regulations defines “relatively short period” as normally being the period beginning on the date the proceeding begins (
                        <E T="03">i.e.</E>
                        , the date the petition is filed) and ending at least three months later. The regulations also provide, however, that if the Department finds that importers, or exporters or producers, had reason to believe, at some time prior to the beginning of the proceeding, that a proceeding was likely, the Department may consider a period of not less than three months from that earlier time. 
                    </P>
                    <HD SOURCE="HD1">History of Dumping and Importer Knowledge </HD>
                    <P>
                        Because we are aware of the European Union's (EU's) November 17, 1997, finding that the Czech Republic had sold similar products (
                        <E T="03">e.g.</E>
                        , seamless pipes, of iron or non-alloy steel) at less than fair value and had caused injury to the domestic industry, we find that a reasonable basis exists to believe or suspect that there is a history of dumping and material injury by reason of dumped imports in the United States or elsewhere of the subject merchandise, pursuant to section 733(e)(1)(A)(i) of the Act. Although the products investigated by the EU are not all identical to those covered by the scope of this investigation, we do not require the scope of our proceedings to match exactly the scope of the foreign proceeding. 
                        <E T="03">See Notice of Final Determination of Sales at Less Than Fair Value: Disposable Pocket Lighters From the People's Republic of China</E>
                        , 60 FR 22359, 22368 (May 5, 1995). In addition, the Department may look to the second criterion for determining importer knowledge of dumping. 
                    </P>
                    <P>
                        In determining whether there is a reasonable basis to believe or suspect that an importer knew or should have known that the exporter was selling the seamless pipe at less than fair value, pursuant to section 733(e)(1)(A)(ii) of the Act, the Department's normal practice is to consider margins of 25 percent or more for export price (EP) sales sufficient to impute knowledge of dumping. 
                        <E T="03">See Certain Cut-to-Length Carbon Steel Plate From the People's Republic of China</E>
                        , 62 FR 31972, 31978 (June 11, 1997). In the instant case, the respondent, Nova Hut, received a margin of 32.26 percent in the amended preliminary determination, 65 FR 12971. Therefore, we have imputed knowledge of dumping to importers of subject merchandise from Nova Hut. 
                    </P>
                    <P>
                        In determining whether there is a reasonable basis to believe or suspect that an importer knew or should have known that there was likely to be material injury by reason of dumped imports, under section 733(e)(1)(A)(ii) of the Act, the Department normally will look to the preliminary injury determination of the International Trade Commission (ITC). If the ITC finds a reasonable indication of present material injury to the relevant U.S. industry, the Department will determine that a reasonable basis exists to impute importer knowledge that there was likely to be material injury by reason of dumped imports. In this case, the ITC has found that a reasonable indication of present material injury due to dumping exists for all imports of seamless pipe from the Czech Republic. 
                        <E T="03">See Certain Seamless Carbon and Alloy Steel Standard, Line and Pressure Pipe from the Czech Republic, Japan, Mexico, Romania and South Africa</E>
                        , 64 FR 46953 (August 27, 1999). As a result, the Department has determined that there is a reasonable basis to believe or suspect that importers knew or should have known that there was likely to be material injury by reason of dumped imports of subject merchandise from the Czech Republic. 
                    </P>
                    <HD SOURCE="HD1">Massive Imports </HD>
                    <P>
                        In determining whether there are “massive imports” over a “relatively short period,” pursuant to 733(e)(1)(B) of the Act, the Department normally compares the import volume of the subject merchandise for three months immediately preceding and following the filing of the petition. Imports normally will be considered massive 
                        <PRTPAGE P="33804"/>
                        when imports have increased by 15 percent or more during this “relatively short period.”
                    </P>
                    <P>
                        We do not have verifiable data from Nova Hut because it withdrew from verification. Therefore, the Department must base its “massive imports” determination as to the company on the facts available, pursuant to section 776(a) of the Act.
                        <SU>1</SU>
                        <FTREF/>
                         Accordingly, we first examined U.S. Customs data 
                        <SU>2</SU>
                        <FTREF/>
                         on imports of seamless pipe from the Czech Republic for January through June 1999 (the six months preceding the June 30, 1999, filing of the petition) and from July through December 1999 (the six months following the filing of the petition).
                        <SU>3</SU>
                        <FTREF/>
                         We found that the total volume of imports of small diameter seamless pipe from the Czech Republic increased by 45.75 percent in the six-month period following the filing of the petition (July through December 1999), as compared to the total volume of such imports from January through June 1999. Second, we considered that Nova Hut, the sole respondent in the investigation, was the only company identified by both the petitioner and the Government of the Czech Republic as a Czech producer of merchandise under investigation. From this we infer that Nova Hut is a significant producer of the merchandise under investigation. As facts available, then, we also infer that a significant portion of the 45.75 percent increase in imports is attributable to Nova Hut. We recognize that some of the HTS categories analyzed to derive the 45.75 percent increase in imports are basket categories that may include non-scope merchandise. However, given that Nova Hut's refusal to supply verifiable data prevents the Department from doing a company-specific massive imports analysis, we are, pursuant to section 776(b) of the Act, making the adverse inference that the country-wide import data is representative of Nova Hut's import data. Moreover, the Department's practice has been to make an adverse inference concerning massive imports with respect to an uncooperative respondent even when country-wide data was not available or not considered. 
                        <E T="03">See, e.g., Notice of Final Determination of Sales at Less Than Fair Value: Collated Roofing Nails from Taiwan</E>
                        , 62 FR 51427, 51437 (October 1, 1997). We, therefore, find that Nova Hut had massive imports of the subject merchandise over a relatively short period of time, under section 733(e)(1)(B) of the Act and 19 CFR 351.206(h)(2). 
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             Because the respondent withdrew from verification, we considered the company non-cooperating and did not request monthly shipment data from the company.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             IM-145 import statistics on HTS numbers included within the scope of the investigation.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             As stated in 
                            <E T="03">Final Determination of Sales at Less Than Fair Value: Certain Cut-to-Length Carbon-Quality Steel Plate from Indonesia</E>
                             (64 FR 73164, December 29, 1999), the Department's practice is to use the longest period for which information is available from the month that the petition was submitted through the date of the preliminary determination.
                        </P>
                    </FTNT>
                    <P>Based on our determination that there is a reasonable basis to believe or suspect that there is a history of dumping and material injury by reason of dumped imports of the subject merchandise in the EU, as well as importer knowledge of dumping, and that there have been massive imports of seamless pipe from this producer over a relatively short period, we preliminarily determine that critical circumstances exist for imports from the Czech Republic of seamless pipe produced by Nova Hut. </P>
                    <HD SOURCE="HD1">All Other Exporters </HD>
                    <P>
                        In regard to the “all others” category, it is the Department's normal practice to conduct its critical circumstances analysis based on the experience of investigated companies. 
                        <E T="03">See Notice of Final Determination of Sales at Less Than Fair Value: Certain Steel Concrete Reinforcing Bars from Turkey (Rebars from Turkey)</E>
                        , 62 FR 9737, 9741 (March 4, 1997). In 
                        <E T="03">Rebars from Turkey</E>
                        , the Department determined that because it found critical circumstances existed for three out of the four companies investigated, critical circumstances also existed for companies covered by the “all others” rate. However, in 
                        <E T="03">Notice of Final Determination of Sales at Less Than Fair Value: Stainless Steel Sheet and Strip in Coils from Japan (Stainless Steel from Japan)</E>
                        , 64 FR 30574 (June 8, 1999), the Department did not extend its affirmative critical circumstances findings to the “all others” categories while finding affirmative critical circumstances for four of the five respondents, because the affirmative determinations were based on adverse facts available. 
                    </P>
                    <P>In the instant case, in our critical circumstances analysis for the one investigated company, Nova Hut, we determined that the EU's finding that the Czech Republic had sold similar products at less than fair value and had caused injury to the domestic industry provides reasonable basis to believe or suspect that there is a history of dumping and material injury by reason of dumped imports in this case. Consistent with our practice, we similarly extend this finding to the “all others” category. </P>
                    <P>
                        With respect to massive imports, however, we are unable to rely on our import level analysis for Nova Hut because it is based upon adverse facts available, and we have no verified data upon which to base a massive imports analysis. Instead, consistent with the approach taken in 
                        <E T="03">Notice of Final Determination of Sales at Less Than Fair Value: Hot-Rolled Flat-Rolled Carbon-Quality Steel Products from Japan</E>
                        , 64 FR 24239 (May 6, 1999) and 
                        <E T="03">Notice of Final Determinations of Sales at Less Than Fair Value: Certain Cold-Rolled Flat-Rolled Carbon-Quality Steel Products From Argentina, Japan and Thailand</E>
                         65 FR 5220, 5227 (February 4, 2000), we examined U.S. Customs data on overall imports from the Czech Republic for the six months preceding and the six months following the filing of the petition in order to see if we could ascertain whether an increase in shipments of greater than 15 percent or more occurred within a relatively short period following the point at which importers had reason to believe that a proceeding was likely. Information on the record indicates that there was a 45.75 percent increase in overall imports from the Czech Republic for the six months following the filing of the petition, as compared to the six months preceding the filing of the petition. However, these data cover numerous HTS categories that may include merchandise other than subject merchandise. Although we made an adverse inference based on this data with respect to Nova Hut, it is not appropriate to make a similar inference with respect to “all others.” Because we have no reliable data upon which to determine whether there were massive imports of seamless pipe from the producers included in the “all others” category, a necessary criterion for determining affirmative critical circumstances has not been met. Therefore, we have preliminarily determined that critical circumstances do not exist for imports from the Czech Republic of seamless pipe for companies in the “all others” category. 
                    </P>
                    <HD SOURCE="HD1">Suspension of Liquidation </HD>
                    <P>
                        In accordance with section 733(e)(2) of the Act, the Department will direct the Customs Service to suspend liquidation of all entries of seamless pipe from the Czech Republic produced by Nova Hut, that are entered, or withdrawn from warehouse, for consumption on or after November 6, 1999, which is 90 days prior to the date of publication in the 
                        <E T="04">Federal Register</E>
                         of our preliminary determination of sales at less than fair value. The Customs Service shall require a cash deposit or posting of a bond equal to the estimated preliminary dumping margin reflected 
                        <PRTPAGE P="33805"/>
                        in the preliminary determination of sales at less than fair value published in the 
                        <E T="04">Federal Register</E>
                        . This suspension of liquidation will remain in effect until further notice. The margin in the preliminary determination is as follows:
                    </P>
                    <FP>Nova Hut—32.26 percent. </FP>
                    <HD SOURCE="HD1">Final Critical Circumstances Determination </HD>
                    <P>We will make final critical circumstances determinations when we issue our final determination in the less-than-fair-value investigation, which is due to be made no later than June 19, 2000. </P>
                    <HD SOURCE="HD1">ITC Notification </HD>
                    <P>In accordance with section 733(f) of the Act, we have notified the ITC of our determination. </P>
                    <P>This notice is published pursuant to section 777(i) of the Act. </P>
                    <SIG>
                        <DATED>Dated: May 17, 2000. </DATED>
                        <NAME>Troy H. Cribb, </NAME>
                        <TITLE>Acting Assistant Secretary for Import Administration. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13097 Filed 5-24-00; 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-853] </DEPDOC>
                <SUBJECT>Notice of Final Determination of Sales at Less Than Fair Value: Bulk Aspirin From the People's Republic of China </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Commerce is conducting an antidumping duty investigation of Bulk Aspirin from the People's Republic of China. We determine that sales have been made at less than fair value. The estimated dumping margins are shown in the Continuation of Suspension of Liquidation section of this notice. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>May 25, 2000. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Rosa Jeong, Ryan Langan or Blanche Ziv, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue, NW., Washington, DC 20230; telephone: (202) 482-3853, 482-1279, or 482-4207, respectively. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">The Applicable Statute and Regulations </HD>
                <P>Unless otherwise indicated, all citations to the statute are references to the provisions effective January 1, 1995, the effective date of the amendments made to the Tariff Act of 1930 (“the Act”) by the Uruguay Round Agreements Act (“URAA”). In addition, unless otherwise indicated, all citations to the Department of Commerce's (“the Department's”) regulations refer to the regulations codified at 19 CFR part 351 (1998). </P>
                <HD SOURCE="HD1">Case History </HD>
                <P>
                    Since the preliminary determination (
                    <E T="03">see</E>
                     65 FR 116 (January 3, 2000) (“
                    <E T="03">Preliminary Determination</E>
                    ”)), the following events have occurred: 
                </P>
                <P>
                    On December 28, 1999, one of the respondents, Shandong Xinhua Pharmaceutical Factory (“Shandong”), requested a postponement of the final determination and, on January 4, 2000, requested an extension of provisional measures. On January 20, 2000, we published in the 
                    <E T="04">Federal Register</E>
                     a notice of postponement of the final determination and extension of provisional measures (65 FR 3204). 
                </P>
                <P>Supplemental information regarding surrogate values was submitted on February 14, 2000, by the petitioner and respondents. </P>
                <P>In February and March 2000, we conducted verification of the questionnaire responses submitted by Shandong and Jilin Pharmaceutical Import and Export Corporation (“Jilin”). We issued reports on our findings of these verifications on April 5, 2000. </P>
                <P>The petitioner and respondents filed case briefs and rebuttal briefs on April 12 and April 19, 2000, respectively. At the request of the petitioner and respondents, the Department held a public hearing on April 25, 2000. </P>
                <P>
                    We also received a case brief from Dastech International, Inc. (“Dastech”), an interested party in this investigation. After reviewing Dastech's comments, we determined that the information contained in Dastech's brief constituted factual information that was filed on an untimely basis as set forth in section 351.301 of the Department's regulations. Therefore, pursuant to section 351.302(d) of the Department's regulations, we removed Dastech's submission from the record, and did not consider the comments for the final determination. 
                    <E T="03">See</E>
                     “Rejection of Interested Party's Brief” Memorandum to Richard W. Moreland, Deputy Assistant Secretary, Import Administration, dated May 17, 2000. 
                </P>
                <HD SOURCE="HD1">Scope of the Investigation </HD>
                <P>
                    For purposes of this investigation, the product covered is bulk acetylsalicylic acid, commonly referred to as bulk aspirin, whether or not in pharmaceutical or compound form, not put up in dosage form (tablet, capsule, powders or similar form for direct human consumption). Bulk aspirin may be imported in two forms, as pure ortho-acetylsalicylic acid or as mixed ortho-acetylsalicylic acid. Pure ortho-acetylsalicylic acid can be either in crystal form or granulated into a fine powder (pharmaceutical form). This product has the chemical formula C
                    <E T="52">9</E>
                    H
                    <E T="52">8</E>
                    O
                    <E T="52">4</E>
                    . It is defined by the official monograph of the United States Pharmacopoeia (“USP”) 23. It is classified under the Harmonized Tariff Schedule of the United States (“HTSUS”) subheading 2918.22.1000. 
                </P>
                <P>
                    Mixed ortho-acetylsalicylic acid consists of ortho-acetylsalicylic acid combined with other inactive substances such as starch, lactose, cellulose, or coloring materials and/or other active substances. The presence of other active substances must be in concentrations less than that specified for particular nonprescription drug combinations of aspirin and active substances as published in the 
                    <E T="03">Handbook of Nonprescription Drugs</E>
                    , eighth edition, American Pharmaceutical Association. This product is classified under HTSUS subheading 3003.90.0000. Although the HTSUS subheadings are provided for convenience and customs purposes, the written description of the merchandise under investigation is dispositive. 
                </P>
                <HD SOURCE="HD1">Period of Investigation </HD>
                <P>The period of this investigation (“POI”) is October 1, 1998, through March 31, 1999. </P>
                <HD SOURCE="HD1">Nonmarket Economy Country and Market-Oriented Industry Status </HD>
                <P>
                    The Department has treated the People's Republic of China (“PRC”) as a nonmarket economy (“NME”) country in all past antidumping investigations. 
                    <E T="03">See, e.g., Notice of Final Determination of Sales at Less Than Fair Value: Certain Preserved Mushrooms from the People's Republic of China,</E>
                     63 FR 72255 (December 31, 1998) (“
                    <E T="03">Mushrooms</E>
                    ”). Under section 771(18)(C) of the Act, this NME designation remains in effect until it is revoked by the Department. 
                </P>
                <P>The respondents in this investigation have not requested a revocation of the PRC's NME status and no further information has been provided that would lead to such a revocation. Therefore, we have continued to treat the PRC as an NME in this investigation. </P>
                <P>
                    Furthermore, no interested party has requested that the bulk aspirin industry in the PRC be treated as a market-oriented industry and no further information has been provided that would lead to such a determination. Therefore, we have not treated the bulk 
                    <PRTPAGE P="33806"/>
                    aspirin industry in the PRC as a market-oriented industry in this investigation. 
                </P>
                <HD SOURCE="HD1">Separate Rates </HD>
                <P>
                    All responding companies have requested separate, company-specific antidumping duty rates. In our 
                    <E T="03">Preliminary Determination,</E>
                     we preliminarily found that all responding companies had met the criteria for the application of separate antidumping duty rates. 
                    <E T="03">See</E>
                     65 FR at 3204. At verification, we found no discrepancies with the information provided in the questionnaire responses of responding companies. We have not received any other information since the 
                    <E T="03">Preliminary Determination</E>
                     which would warrant reconsideration of our separate rates determinations with respect to these companies. We, therefore, determine that the responding companies in this investigation should be assigned individual dumping margins. 
                </P>
                <HD SOURCE="HD1">PRC-Wide Rate </HD>
                <P>As stated in the preliminary determination, information on the record of this investigation indicates that there are numerous producers/exporters of the subject merchandise in the PRC in addition to the companies participating in this investigation. U.S. import statistics show that the responding companies did not account for all imports of bulk aspirin into the United States from the PRC. Given this discrepancy, it appears that not all PRC exporters of bulk aspirin responded to our questionnaire. Accordingly, we are applying a single antidumping deposit rate (“the PRC-wide rate”) to all bulk aspirin exporters in the PRC except those specifically identified in the “Continuation of Suspension of Liquidation” section of this notice. </P>
                <HD SOURCE="HD1">Use of Facts Available </HD>
                <P>As explained in the preliminary determination, the PRC-wide antidumping rate is based on adverse facts available, in accordance with section 776 of the Act. Section 776(a)(2) of the Act provides that “if an interested party or any other person— (A) withholds information that has been requested by the administering authority or the Commission under this title, (B) fails to provide such information by the deadlines for submission of the information or in the form and manner requested, subject to subsections (c)(1) and (e) of section 782, (C) significantly impedes a proceeding under this title, or (D) provides such information but the information cannot be verified as provided in section 782(i), the administering authority and the Commission shall, subject to section 782(d), use the facts otherwise available in reaching the applicable determination under this title.” Use of facts available is warranted in this case because the producers/exporters other than those under investigation have failed to respond to the Department's questionnaire. </P>
                <P>Section 776(b) of the Act provides that adverse inferences may be used when a party has failed to cooperate by not acting to the best of its ability to comply with a request for information. The producers/exporters that decided not to respond in any form to the Department's questionnaire, failed to act to the best of their ability in this investigation. Further, absent a verifiable response from these firms, we must presume government control of these PRC companies. Thus, the Department has determined that, in selecting from among the facts otherwise available, an adverse inference is warranted and has assigned them a common, PRC-wide rate based on adverse inferences. </P>
                <P>
                    In accordance with our standard practice, as adverse facts available, we are assigning to the PRC-wide entity (
                    <E T="03">i.e.</E>
                    , those companies not receiving a separate rate), which did not cooperate in the investigation, the higher of: (1) the highest margin stated in the notice of initiation; or (2) the highest margin calculated for any respondent in this investigation. 
                    <E T="03">See, e.g., Notice of Final Determination of Sales at Less Than Fair Value: Stainless Steel Wire Rod From Japan</E>
                    , 63 FR 40434 (July 29, 1998). In this case, the adverse facts available margin is 144.02 percent, the margin from the petition, which is higher than the margin calculated for any respondent in this investigation. 
                </P>
                <P>
                    Section 776(c) of the Act provides that where the Department selects from among the facts otherwise available and relies on “secondary information,” such as the petition, the Department shall, to the extent practicable, corroborate that information from independent sources reasonably at the Department's disposal. The Statement of Administrative Action accompanying the URAA, H.R. Doc. No. 103-316 (1994) (“SAA”), states that “corroborate” means to determine that the information used has probative value. 
                    <E T="03">See</E>
                     SAA at 870. As discussed in the 
                    <E T="03">Preliminary Determination</E>
                    , we determine that the calculations set forth in the petition have probative value. 
                </P>
                <HD SOURCE="HD1">Analysis of Comments Received </HD>
                <P>All issues raised in the case and rebuttal briefs by parties to this investigation are addressed in the May 17, 2000, Decision Memorandum which is hereby adopted by this notice. Attached to this notice as an appendix is a list of the issues which parties have raised and to which we have responded in the Decision Memorandum. Parties can find a complete discussion of all issues raised in this investigation and the corresponding recommendations in this public memorandum which is on file in the Central Records Unit, Room B-099 of the Department. In addition, a complete version of the Decision Memorandum can be accessed directly on the internet at www.ita.doc.gov/import_admin/records/frn. The paper copy and electronic version of the Decision Memorandum are identical in content. </P>
                <HD SOURCE="HD1">Changes Since the Preliminary Determination </HD>
                <P>
                    Based on our analysis of comments received, we have made certain changes in the margin calculations. We have also corrected certain programming and clerical errors in our 
                    <E T="03">Preliminary Determination</E>
                    , where applicable. Any programming or clerical errors are discussed in the relevant sections of the Decision Memorandum or in the company-specific final determination calculation memoranda dated May 17, 2000. 
                </P>
                <HD SOURCE="HD1">Verification </HD>
                <P>As provided in section 782(i) of the Act, we verified the information submitted by respondents for use in our final determination. We used standard verification procedures including examination of relevant accounting and production records, and original source documents provided by respondents. </P>
                <HD SOURCE="HD1">Continuation of Suspension of Liquidation </HD>
                <P>
                    In accordance with section 735(c) of the Act, we are directing the U.S. Customs Service (“Customs”) to continue to suspend liquidation of all imports of the subject merchandise from the PRC, except for merchandise both produced and exported by Jilin (which had a zero margin at the 
                    <E T="03">Preliminary Determination</E>
                    ), that are entered, or withdrawn from warehouse, for consumption on or after January 3, 2000, the date of publication of the 
                    <E T="03">Preliminary Determination</E>
                     in the 
                    <E T="04">Federal Register</E>
                    . With respect to Jilin, Customs shall suspend liquidation of all imports of the subject merchandise from the PRC, produced and exported by Jilin that are entered, or withdrawn from warehouse, for consumption on or after the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <P>
                    Customs shall continue to require a cash deposit or the posting of a bond equal to the weighted-average amount 
                    <PRTPAGE P="33807"/>
                    by which the NV exceeds the EP or CEP, as appropriate, as indicated in the chart below. These suspension of liquidation instructions will remain in effect until further notice. 
                </P>
                <P>The weighted-average dumping margins are as follows: </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,8.2">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Exporter/manufacturer </CHED>
                        <CHED H="1">Weighted-average margin percentage </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Shandong Xinhua Pharmaceutical Factory </ENT>
                        <ENT>42.77 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Jilin Pharmaceutical Co., Ltd./ </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Jilin Pharmaceutical Import and Export Corporation </ENT>
                        <ENT>4.72 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PRC-wide Rate </ENT>
                        <ENT>144.02 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>The PRC-wide rate applies to all entries of the subject merchandise except for entries from exporters that are identified individually above. </P>
                <HD SOURCE="HD1">ITC Notification </HD>
                <P>In accordance with section 735(d) of the Act, we have notified the ITC of our determination. As our final determination is affirmative, the ITC will, within 45 days, determine whether these imports are materially injuring, or threaten material injury to, the U.S. industry. If the ITC determines that material injury, or threat of material injury does not exist, the proceeding will be terminated and all securities posted will be refunded or canceled. If the ITC determines that such injury does exist, the Department will issue an antidumping duty order directing Customs officials to assess antidumping duties on all imports of the subject merchandise entered for consumption on or after the effective date of the suspension of liquidation. </P>
                <P>This determination is issued and published in accordance with sections 735(d) and 777(i)(1) of the Act. </P>
                <SIG>
                    <DATED>Dated: May 17, 2000. </DATED>
                    <NAME>Troy H. Cribb, </NAME>
                    <TITLE>Acting Assistant Secretary for Import Adminstration.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix </HD>
                <HD SOURCE="HD2">List of Comments in the Issues and Decision Memorandum </HD>
                <FP SOURCE="FP-2">Comment 1: Valuation of Phenol </FP>
                <FP SOURCE="FP-2">Comment 2: Valuation of Caustic Soda </FP>
                <FP SOURCE="FP-2">Comment 3: Valuation of Carbon Dioxide </FP>
                <FP SOURCE="FP-2">Comment 4: Valuation of Overhead, Selling, General, Administrative Expenses and Profit </FP>
                <FP SOURCE="FP-2">Comment 5: Adjustments to Surrogate Ratios </FP>
                <FP SOURCE="FP-2">Comment 6: Valuation of Electricity </FP>
                <FP SOURCE="FP-2">Comment 7: Valuation of Water </FP>
                <FP SOURCE="FP-2">Comment 8: Valuation of Ocean Freight </FP>
                <FP SOURCE="FP-2">Comment 9: Returned Merchandise </FP>
                <FP SOURCE="FP-2">Comment 10: Separate Rates </FP>
                <FP SOURCE="FP-2">Comment 11: Shandong's Use of Technical-Grade Salicylic Acid </FP>
                <FP SOURCE="FP-2">Comment 12: Jilin's Raw Material Consumption </FP>
                <FP SOURCE="FP-2">Comment 13: Jilin's By-Product Offset </FP>
                <FP SOURCE="FP-2">Comment 14: Jilin's Inland Freight Costs for Materials </FP>
                <FP SOURCE="FP-2">Comment 15: Jilin's Multiple Shipments </FP>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13095 Filed 5-24-00; 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-580-839, A-583-833] </DEPDOC>
                <SUBJECT>Notice of Amended Final Determination of Sales at Less Than Fair Value: Certain Polyester Staple Fiber From the Republic of Korea and Antidumping Duty Orders: Certain Polyester Staple Fiber From the Republic of Korea and Taiwan </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce. </P>
                </AGY>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>May 25, 2000. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Craig Matney (Republic of Korea) or Cynthia Thirumalai (Taiwan), Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue, NW, Washington, DC 20230; telephone: (202) 482-1778 or (202) 482-4087, respectively. </P>
                    <HD SOURCE="HD1">Applicable Statute and Regulations </HD>
                    <P>Unless otherwise indicated, all citations to the Tariff Act of 1930, as amended (“the Act”), are references to the provisions effective January 1, 1995, the effective date of the amendments made to the Act by the Uruguay Round Agreements Act (“URAA”). In addition, unless otherwise indicated, all citations to the Department of Commerce's (“the Department's”) regulations are to the regulations codified at 19 CFR part 351 (1998). </P>
                    <HD SOURCE="HD1">Scope of Orders </HD>
                    <P>
                        The product covered by these orders is certain polyester staple fiber (“PSF”). Certain polyester staple fiber is defined as synthetic staple fibers, not carded, combed or otherwise processed for spinning, of polyesters measuring 3.3 decitex (3 denier, inclusive) or more in diameter. This merchandise is cut to lengths varying from one inch (25 mm) to five inches (127 mm). The merchandise subject to these orders may be coated, usually with a silicon or other finish, or not coated. PSF is generally used as stuffing in sleeping bags, mattresses, ski jackets, comforters, cushions, pillows, and furniture. Merchandise of less than 3.3 decitex (less than 3 denier) classified under the 
                        <E T="03">Harmonized Tariff Schedule of the United States</E>
                         (“HTSUS”) at subheading 5503.20.00.20 is specifically excluded from these orders. Also specifically excluded from these orders are polyester staple fibers of 10 to 18 denier that are cut to lengths of 6 to 8 inches (fibers used in the manufacture of carpeting). In addition, low-melt PSF is excluded from these orders. Low-melt PSF is defined as a bi-component fiber with an outer sheath that melts at a significantly lower temperature than its inner core. 
                    </P>
                    <P>The merchandise subject to these orders is classified in the HTSUS at subheadings 5503.20.00.40 and 5503.20.00.60. Although the HTSUS subheadings are provided for convenience and customs purposes, the written description of these orders is dispositive. </P>
                    <HD SOURCE="HD1">Amended Final Determination </HD>
                    <P>
                        In accordance with section 735(a) of the Act, on March 30, 2000, the Department published the final determination of the antidumping duty investigation of certain PSF from the Republic of Korea (“Korea”), in which we determined that U.S. sales of PSF from Korea were made at less than normal value (65 FR 16880 (“
                        <E T="03">Korea Final Determination</E>
                        ”)). On March 31 and April 4, 2000, we received ministerial error allegations, timely filed pursuant to § 351.224(c)(2) of the Department's regulations, from the petitioners E.I. DuPont de Nemours, Inc.; 
                        <SU>1</SU>
                        <FTREF/>
                         Arteva Specialities S.a.r.l.; d/b/a KoSa; Wellman, Inc.; and Intercontinental Polymers, Inc. (hereinafter collectively referred to as “the petitioners”) regarding the calculations for Geum Poong Corporation (“Geum Poong”) and Samyang Corporation (“Samyang”), respectively. On April 5, 2000, Sam Young Synthetics Co. (“Sam Young”) and Geum Poong timely filed ministerial allegations, and Geum Poong also commented on the petitioners' allegations. On April 6, 2000, Samyang filed a rebuttal to the petitioners' ministerial error allegations. We received comments from the petitioners concerning the respondents' clerical error allegations on April 10, 2000. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             E.I. DuPont de Nemours, Inc. is not a petitioner in the Taiwan case.
                        </P>
                    </FTNT>
                    <P>
                        We have determined in accordance with section 735(e) of the Act that ministerial errors were made in our final margin calculations. For a detailed 
                        <PRTPAGE P="33808"/>
                        discussion of the above-cited ministerial errors and the Department's analysis, see Memorandum to Richard W. Moreland, dated April 26, 2000. We are amending the final determination of the antidumping duty investigation of PSF from Korea to correct these ministerial errors. The revised final weighted-average dumping margins are as follows: 
                    </P>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,16,16">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">Exporter/manufacturer </CHED>
                            <CHED H="1">Original weighted-average margin percentage </CHED>
                            <CHED H="1">Revised weighted-average margin percentage </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Samyang Corporation </ENT>
                            <ENT>
                                0.14 
                                <LI>
                                    (
                                    <E T="03">*</E>
                                </LI>
                            </ENT>
                            <ENT>
                                0.14 
                                <LI>
                                    (
                                    <E T="03">*</E>
                                </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sam Young Synthetics Co.</ENT>
                            <ENT>7.96</ENT>
                            <ENT>7.91 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Geum Poong Corporation</ENT>
                            <ENT>14.10</ENT>
                            <ENT>14.10 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">All Others</ENT>
                            <ENT>11.38</ENT>
                            <ENT>11.35 </ENT>
                        </ROW>
                        <TNOTE>* de minimis.</TNOTE>
                    </GPOTABLE>
                    <P>
                        For Taiwan, we published 
                        <E T="03">Notice of Final Determination of Sales at Less Than Fair Value: Certain Polyester Staple Fiber from Taiwan</E>
                         65 FR 16877 (March 30, 2000) and 
                        <E T="03">Notice of Amended Final Determination of Sales at Less Than Fair Value: Certain Polyester Staple Fiber from Taiwan</E>
                         65 FR 24678 (April 27, 2000). 
                    </P>
                    <HD SOURCE="HD1">Antidumping Duty Orders </HD>
                    <P>On May 15, 2000, in accordance with section 735(d) of the Act, the U.S. International Trade Commission (“ITC”) notified the Department that an industry in the United States is “materially injured,” within the meaning of section 735(b)(1)(A) of the Act, by reason of less-than-fair-value imports of PSF from Korea and Taiwan. In its final determination, however, the ITC determined that two domestic like products exist for merchandise covered by the Department's investigation: (1) low-melt PSF and (2) all other types of PSF not specifically excluded. The ITC determined pursuant to section 735(b)(1) that a domestic industry in the United States is not materially injured or threatened with material injury by reason of imports of low-melt PSF from Korea and Taiwan. Accordingly, the scope of these antidumping duty orders has been amended from that used in the investigations to exclude low-melt PSF. </P>
                    <P>Sam Young and Geum Poong, the two respondents included in the Korea order, did not make sales of low-melt PSF during the period of investigation. Therefore, it was not necessary to recalculate the margins to exclude sales of low-melt PSF for these Korean respondents. However, we recalculated, for purposes of the Taiwan order, the estimated dumping margins for both respondents in Taiwan by excluding sales of low-melt PSF from our analysis. The revised estimated dumping margins for Taiwan are found below. </P>
                    <P>
                        The Department will direct the U.S. Customs Service to assess, upon further advice by the Department, antidumping duties equal to the amount by which the normal value of the subject merchandise exceeds the export price or constructed export price of the subject merchandise for all relevant entries of PSF from Korea and Taiwan, except for subject merchandise produced in Korea and imported from Samyang, which received a 
                        <E T="03">de minimis</E>
                         final margin. With respect to Korea, all bonds may be released and entries by Samyang may be liquidated without regard to antidumping duties. 
                    </P>
                    <P>
                        For all other manufacturers/exporters from Korea, antidumping duties will be assessed on all unliquidated entries of PSF, excluding low-melt PSF, entered, or withdrawn from warehouse, for consumption on or after November 8, 1999, the date of publication of the Department's preliminary determination in the 
                        <E T="04">Federal Register</E>
                         (64 FR 60776). For all other manufacturers/exporters in Taiwan other than Nan Ya Plastics Corporation, Ltd., antidumping duties will be assessed on all unliquidated entries of PSF, excluding low-melt PSF, entered, or withdrawn from warehouse, for consumption on or after March 30, 2000, the date of publication of the Department's final determination in the 
                        <E T="04">Federal Register</E>
                         (64 FR 60771). For Nan Ya Plastics Corporation, Ltd., antidumping duties will be assessed on all unliquidated entries of PSF from Taiwan, excluding low-melt PSF, entered, or withdrawn from warehouse, for consumption on or after April 27, 2000, the date of publication of the Department's amended final determination in the 
                        <E T="04">Federal Register</E>
                         (65 FR 24678 ). Furthermore, we will instruct Customs to refund all cash deposits, or bonds posted, for entries of subject merchandise from Korea imported from Samyang Corporation and for entries of low-melt PSF from both Taiwan and Korea. 
                    </P>
                    <P>
                        On or after the date of publication of this notice in the 
                        <E T="04">Federal Register</E>
                        , Customs officers must require, at the same time as importers would normally deposit estimated duties, cash deposits for the subject merchandise equal to the weighted-average antidumping duty margins as noted below: 
                    </P>
                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s30,10">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">Exporter/manufacturer </CHED>
                            <CHED H="1">Revised weighted-average margin percentage </CHED>
                        </BOXHD>
                        <ROW EXPSTB="01" RUL="s">
                            <ENT I="21">
                                <E T="02">Republic of Korea</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Samyang Corporation </ENT>
                            <ENT>Excluded </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sam Young Synthetics Co</ENT>
                            <ENT>7.91 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Geum Poong Corporation</ENT>
                            <ENT>14.10 </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">All Others </ENT>
                            <ENT>11.35 </ENT>
                        </ROW>
                        <ROW EXPSTB="01" RUL="s">
                            <ENT I="21">
                                <E T="02">Taiwan</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Far Eastern Corporation </ENT>
                            <ENT>11.50 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Nan Ya Plastics Corporation, Ltd </ENT>
                            <ENT>3.79 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">All Others </ENT>
                            <ENT>7.31 </ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>This notice constitutes the antidumping duty orders with respect to PSF from Korea and Taiwan, pursuant to section 735(a) of the Act. Interested parties may contact the Central Records Unit, Room B-099 of the Main Commerce Building for copies of an updated list of antidumping duty orders currently in effect. </P>
                    <P>These orders are published in accordance with sections 736(a) and 19 CFR 351.211. </P>
                    <SIG>
                        <DATED>Dated: May 18, 2000. </DATED>
                        <NAME>Troy H. Cribb, </NAME>
                        <TITLE>Acting Assistant Secretary for Import Administration. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13096 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Institute of Standards and Technology</SUBAGY>
                <SUBJECT>Announcing a Meeting of the Computer System Security and Privacy Advisory Board</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institute of Standards and Technology.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting. </P>
                </ACT>
                <SUM>
                    <PRTPAGE P="33809"/>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the Federal Advisory Committee Act, 5 U.S.C. App., notice is hereby given that the Computer System Security and Privacy Advisory Board (CSSPAB) will meet Tuesday, June 13, 2000, Wednesday, June 14, 2000, and Thursday, June 15, 2000, from 9:00 a.m. to 5:00 p.m. The Advisory Board was established by the Computer Security Act of 1987 (Pub. L. 100-235) to advise the Secretary of Commerce and the Director of NIST on security and privacy issues pertaining to federal computer systems. All sessions will be open to the public Details regarding the Board's activities are available at http://csrc.nist.gov/csspab/.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held on June 13-15, 2000, from 9 a.m. to 5 p.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will take place at the National Institute of Standards and Technology, North Campus, 820 West Diamond Avenue, Gaithersburg, MD in Lecture Room 152.</P>
                </ADD>
                <HD SOURCE="HD1">Agenda</HD>
                <P>As part of this meeting, a “security metrics” workshop will be held on June 13 and 14, 2000, to examine the approaches to measuring security. The following topics will be explored:</P>
                <FP SOURCE="FP-1">—Definitions of “metrics”</FP>
                <FP SOURCE="FP-1">—Measures of security against specific security threats</FP>
                <FP SOURCE="FP-1">—Measures of overall system security</FP>
                <FP SOURCE="FP-1">—Qualitative measures, e.g., adherence to “standards” or checklists of practices</FP>
                <FP SOURCE="FP-1">—Live, real-time measures of security in extended networks</FP>
                <FP SOURCE="FP-1">—Use of statistically-sampled data in measurement systems</FP>
                <FP SOURCE="FP-1">—Effective communications of metrics, assurance levels and risk management tradeoffs to executives, lawmakers, and the public so that risks and protections are properly understood in both business and public policy terms.</FP>
                <P>The first day of this workshop will be dedicated to presentations from the government, the private sector, and public sector organizations. The second day will consist of case studies presented by a government panel and an industry panel.</P>
                <P>The last day of the meeting, Thursday, June 15, 2000, the Board will review the progress of the workshop and, as appropriate, plan or recommend follow-on activity. The Board will also devote discussion period to develop the Board's future program and to identify key issues.</P>
                <HD SOURCE="HD1">Public Participation</HD>
                <P>The Board agenda will include a period of time, not to exceed thirty minutes, for oral comments and questions from the public. Each speaker will be limited to five minutes. Members of the public who are interested in speaking are asked to contact the Board Secretariat at the telephone number indicated below. In addition, written statements are invited and may be submitted to the Board. It would be appreciated if 35 copies of written material were available for distribution to the Board and attendees at the meeting no later than June 5, 2000. Approximately 15 seats will be available for the public and media.</P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Edward Roback, Board Secretariat, Information Technology Laboratory, National Institute of Standards and Technology, 100 Bureau Drive, Stop 8930, Gaithersburg, MD 20899-8930, telephone: (301) 975-3696.</P>
                    <SIG>
                        <DATED>Dated: May 18, 2000.</DATED>
                        <NAME>Jorge Urrutia,</NAME>
                        <TITLE>
                            <E T="03">Acting Director, NIST.</E>
                        </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13144  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-CN-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration </SUBAGY>
                <DEPDOC>[I.D. 051900B] </DEPDOC>
                <SUBJECT>New England Fishery Management Council; Public Meetings </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public meetings. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The New England Fishery Management Council (Council) is scheduling a public meeting of its Social Sciences Advisory Committee and a number of joint meetings of its Groundfish Oversight Committee and Groundfish Advisory Panel in June, 2000. Recommendations from the these groups will be brought to the full Council for formal consideration and action, if appropriate. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        See 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         for specific dates and times. 
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        See 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         for specific locations. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Paul J. Howard, Executive Director, New England Fishery Management Council; (978) 465-0492. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION: </HD>
                <HD SOURCE="HD1">Meeting Dates and Agendas </HD>
                <P>
                    <E T="03">June 8, 2000, 10:00 a.m.</E>
                    —Social Sciences Advisory Committee Meeting 
                </P>
                <P>Location: Holiday Inn, One Newbury Street (Rt. 1 North), Peabody, MA 01960; telephone: (978) 535-4600. </P>
                <P>The committee will discuss the social and economic issues associated with measures proposed for Amendment 10 to the Atlantic Sea Scallop Fishery Management Plan (FMP). The proposed measures include a rotational area management system for Atlantic sea scallops including possible access to the groundfish closed areas on Georges Bank and in Southern New England, modifications to trawl gear to require the same scallop selectivity as dredge gear, and a possible increase in the seven-person crew limit. The committee also will discuss the organization of workshops for improving social and economic analyses. Finally, the committee will receive an update on the work of the Council's Capacity Committee. </P>
                <P>
                    <E T="03">June 13, 2000, 9:30 a.m.</E>
                    —Joint Groundfish Committee and Advisory Panel Meeting 
                </P>
                <P>Location: Howard Johnson's Motor Lodge, Interstate Traffic Circle, Portsmouth, NH 03801; telephone: (603) 436-7600. </P>
                <P>The committee and advisors will conduct a joint meeting to continue development of management options for Amendment 13 to the Northeast Multispecies FMP. They also will consider options for developing an area management system, or for a sector allocation system. Work on these options will continue at all meetings to be held in June. In addition, the committee will continue to develop changes to current management measures that will improve the effectiveness of the existing management system. The goal is to develop management alternatives for review at public hearings in the fall of 2000. This same agenda will be followed for the following list of joint Groundfish Committee and Advisory Panel meetings. </P>
                <P>
                    <E T="03">June 20, 2000, 9:30 a.m.</E>
                    —Joint Groundfish Committee and Advisory Panel Meeting. 
                </P>
                <P>Location: Radisson Hotel, 35 Governor Winthrop Boulevard, New London, CT 06320; telephone: (860) 443-7000. </P>
                <P>
                    <E T="03">June 27, 2000, 9:30 a.m.</E>
                    —Joint Groundfish Committee and Advisory Panel Meeting. 
                </P>
                <P>Location: Sheraton Inn—Providence Airport, 1850 Post Road, Warwick, RI 02886; telephone: (401) 738-4000. </P>
                <P>
                    Although non-emergency issues not contained in this agenda may come before this Council for discussion, those issues may not be the subject of formal Council action during this meeting. 
                    <PRTPAGE P="33810"/>
                    Council action will be restricted to those issues specifically listed in this notice and any issues arising after publication of this notice that require emergency action under section 305(c) of the Magnuson-Stevens Act, provided the public has been notified of the Council's intent to take final action to address the emergency. 
                </P>
                <HD SOURCE="HD1">Special Accommodations </HD>
                <P>
                    This meeting is physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to Paul J. Howard (see 
                    <E T="02">ADDRESSES</E>
                    ) at least 5 days prior to the meeting dates. 
                </P>
                <SIG>
                    <DATED>Dated: May 22, 2000. </DATED>
                    <NAME>Richard W. Surdi, </NAME>
                    <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13186 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-22-F </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE </AGENCY>
                <AGENCY TYPE="O">GENERAL SERVICES ADMINISTRATION </AGENCY>
                <AGENCY TYPE="O">NATIONAL AERONAUTICS AND SPACE ADMINISTRATION </AGENCY>
                <DEPDOC>[OMB Control No. 9000-0149] </DEPDOC>
                <SUBJECT>Submission for OMB Review; Comment Request Entitled Subcontract Consent </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCIES:</HD>
                    <P>Department of Defense (DOD), General Services Administration (GSA), and National Aeronautics and Space Administration (NASA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for public comments regarding an extension to an existing OMB clearance (9000-0149). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Under the provisions of the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35), the Federal Acquisition Regulation (FAR) Secretariat has submitted to the Office of Management and Budget (OMB) a request to review and approve an extension of a currently approved information collection requirement concerning Subcontract Consent. A request for public comments was published at 65 FR 14950 on March 20, 2000. No comments were received. </P>
                    <P>Public comments are particularly invited on: Whether this collection of information is necessary for the proper performance of functions of the FAR, and whether it will have practical utility; whether our estimate of the public burden of this collection of information is accurate, and based on valid assumptions and methodology; ways to enhance the quality, utility, and clarity of the information to be collected; and ways in which we can minimize the burden of the collection of information on those who are to respond, through the use of appropriate technological collection techniques or other forms of information technology. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments may be submitted on or before June 26, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments including suggestions for reducing this burden, should be submitted to: FAR Desk Officer, OMB, Room 10102, NEOB, Washington, DC 20503, and a copy to the General Services Administration, FAR Secretariat (MVRS), Room 4035, 1800 F Street, NW, Washington, DC 20405. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Linda Klein, Office of Federal Acquisition Policy Division, GSA (202) 501-3775. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">A. Purpose </HD>
                <P>The objective to consent to subcontract, as discussed in FAR Part 44, is to evaluate the efficiency and effectiveness with which the contractor spends Government funds, and complies with Government policy when subcontracting. The consent package provides the administrative contracting officer a basis for granting, or withholding consent to subcontract. </P>
                <HD SOURCE="HD1">B. Annual Reporting Burden </HD>
                <FP SOURCE="FP-1">
                    <E T="03">Number of Respondents:</E>
                     4,252. 
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">Responses Per Respondent:</E>
                     3.61. 
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">Total Responses:</E>
                     15,349. 
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">Average Burden Hours Per Response:</E>
                     .87. 
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">Total Burden Hours:</E>
                     13,353.
                </FP>
                <P>
                    <E T="03">Obtaining Copies of Proposals:</E>
                     Requester may obtain a copy of the proposal from the General Services Administration, FAR Secretariat (MVRS), Room 4035, 1800 F Street, NW, Washington, DC 20405, telephone (202) 208-7312. Please cite OMB Control No. 9000-0149, Subcontract Consent, in all correspondence. 
                </P>
                <SIG>
                    <DATED>Dated: May 22, 2000. </DATED>
                    <NAME>Edward C. Loeb, </NAME>
                    <TITLE>Director, Federal Acquisition Policy Division. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13145 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6820-34-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE </AGENCY>
                <AGENCY TYPE="F">GENERAL SERVICES ADMINISTRATION </AGENCY>
                <AGENCY TYPE="F">NATIONAL AERONAUTICS AND SPACE ADMINISTRATION </AGENCY>
                <DEPDOC>[OMB Control No. 9000-0007] </DEPDOC>
                <SUBJECT>Submission for OMB Review; Comment Request Entitled Summary Subcontract Report </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCIES:</HD>
                    <P>Department of Defense (DOD), General Services Administration (GSA), and National Aeronautics and Space Administration (NASA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for public comments regarding an extension of an existing OMB clearance. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Under the provisions of the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35), the Federal Acquisition Regulation (FAR) Secretariat has submitted to the Office of Management and Budget (OMB) a request to review and approve an extension of a currently approved information collection requirement concerning Summary Subcontract Report. A request for public comments was published at 65 FR 14951, on March 20, 2000. No comments were received. </P>
                    <P>Public comments are particularly invited on: Whether this collection of information is necessary for the proper performance of functions of the FAR, and whether it will have practical utility; whether our estimate of the public burden of this collection of information is accurate, and based on valid assumptions and methodology; ways to enhance the quality, utility, and clarity of the information to be collected; and ways in which we can minimize the burden of the collection of information on those who are to respond, through the use of appropriate technological collection techniques or other forms of information technology. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments may be submitted on or before June 26, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments including suggestions for reducing this burden, should be submitted to: FAR Desk Officer, OMB, Room 10102, NEOB, Washington, DC 20503, and a copy to the General Services Administration, FAR Secretariat (MVRS), Room 4035, 1800 F Street, NW, Washington, DC 20405. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Victoria Moss, Office of Federal Acquisition Policy Division, GSA (202) 501-4764. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">
                    SUPPLEMENTARY INFORMATION:
                    <PRTPAGE P="33811"/>
                </HD>
                <HD SOURCE="HD1">A. Purpose </HD>
                <P>
                    In accordance with the Small Business Act (15 U.S.C. 631, 
                    <E T="03">et seq.</E>
                    ), contractors receiving a contract for more than $10,000 agree to have small and small disadvantaged business concerns participate in the performance of the contract as far as practicable. Contractors receiving a contract or a modification to a contract expected to exceed $500,000 ($1 million for construction) must submit a subcontracting plan that provides maximum practicable opportunities for small and small disadvantaged business concerns. Specific elements required to be included in the plan are specified in section 8(d) of the Small Business Act and are implemented in FAR 19.7. 
                </P>
                <HD SOURCE="HD1">B. Annual Reporting Burden </HD>
                <P>
                    <E T="03">Number of Respondents:</E>
                     4,253. 
                </P>
                <P>
                    <E T="03">Responses Per Respondent:</E>
                     1.66. 
                </P>
                <P>
                    <E T="03">Total Responses:</E>
                     7,098. 
                </P>
                <P>
                    <E T="03">Average Burden Hours Per Response:</E>
                     12.90. 
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     90,854. 
                </P>
                <P>
                    <E T="03">Obtaining Copies of Justifications:</E>
                     Requester may obtain a copy of the proposal from the General Services Administration, FAR Secretariat (MVRS), Room 4035, 1800 F Street, NW, Washington, DC 20405, telephone (202) 208-7312. Please cite OMB Control No. 9000-0007, Summary Subcontract Report, in all correspondence. 
                </P>
                <SIG>
                    <DATED>Dated: May 22, 2000. </DATED>
                    <NAME>Edward C. Loeb, </NAME>
                    <TITLE>Director, Federal Acquisition Policy Division. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13146 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6820-34-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. ER00-2383-000]</DEPDOC>
                <SUBJECT>California Independent System Operator Corporation; Notice of Filing</SUBJECT>
                <DATE>May 19, 2000.</DATE>
                <P>Take notice that on May 3, 2000, the California Independent System Operator Corporation (ISO), tendered for filing an correction regarding a proposed amendment (Amendment No. 29), to the ISO Tariff, which had been filed in the above-referenced docket on May 2, 2000. The correction provided tariff sheets containing Tariff sections that were “rolled over” to subsequent pages of the Tariff, as a result of changes and additions made in the Amendment No. 29 filing, and corrected an error in the section numbering on a certain Tariff sheet that was included in the Amendment No. 29 filing.</P>
                <P>The ISO states that this filing has been served upon the Public Utilities Commission of California, the California Energy Commission, the California Electricity Oversight Board, and all parties with effective Scheduling Coordinator Service Agreements under the ISO tariff.</P>
                <P>Any person desiring to be heard or to protest such filing should file a motion to intervene or protest with the Federal 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). All such motions and protests should be filed on or before May 30, 2000. Protests will be considered by the Commission to determine the appropriate action to be taken, but will not serve to make protestants parties to the proceedings. Any person wishing to become a party must file a motion to intervene. Copies of this filing are on file with the Commission and are available for public inspection. This filing may also be viewed on the Internet at http://www.ferc.fed.us/online/rims.htm (call 202-208-2222 for assistance).</P>
                <SIG>
                    <NAME>Linwood A. Watson, Jr.,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13114 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. CP00-51-001]</DEPDOC>
                <SUBJECT>East Tennessee Natural Gas Company; Notice of Amendment</SUBJECT>
                <DATE>May 19, 2000.</DATE>
                <P>Take notice that on May 10, 2000, East Tennessee Natural Gas Company (East Tennessee), 1001 Louisiana, Houston, Texas 77002, filed with the Commission in Docket NO. CP00-51-001 an amendment to the pending application filed on December 17, 1999, in Docket No. CP00-51-000, pursuant to Section 7(c) of the Natural Gas Act (NGA), to reflect change in the locations of meter stations, main line valves, and manifolds for which certificate authorization is sought, all as more fully set forth in the amendment which is open to the public for inspection.</P>
                <P>By the pending application in Docket No. CP00-51-000, East Tennessee proposes to construct, install, and operate: (1) 15.16 miles of 12-inch diameter pipeline looping in Washington, Smyth, and Wythe Counties, Virginia; (2) three meter stations in McGinn, Greene, and Roane Counties, Tennessee, and a modficiation to an existing meter station in Morgan County, Tennessee; (3) approximately 0.62 miles of 22-inch diameter replacement pipe on East Tennessee's 3100 Line in Smith and Overton Counties, Tennessee. Finally, East Tennessee's 3100 Line: and (4) approximately 450 feet of 10-inch and 12-inch diameter replacement pipeline, in addition to two mainline valves on East Tennessee's 3200 Line at the Tennessee River Crossing. Additionally, East Tennessee seeks certain other authorizations, including authorization to up rate four compressor units located at Station 3101 in Robertson County, Tennessee, and Station 3210 in Marion County, Tennessee, and authorization to hydrostatically test to increase the Maximum Allowable Operating Pressure (MAOP) of 26.42 miles of pipe on East Tennessee requests that the Commission authorize the abandonment of approximately 0.62 miles of pipe being replaced align East Tennessee's 3100 Line plus 250 feet of pipe, two mainline valve assemblies and miscellaneous fittings and appurtenances being replaced along the 3200 Line by the above-referenced replacement pipe. East Tennessee submits that these activities are necessary to provide additional firm transportation service to eight customers on the part of East Tennessee's pipeline system located in eastern Tennessee and southwestern Virginia (Rocky Top Expansion Project).</P>
                <P>
                    In the subject amendment, East Tennessee seeks to modify its original request for certificate authority by requesting authorization to, 
                    <E T="03">itner alia,</E>
                     change the locations of the proposed Lenior City and Etowah meter stations. East Tennessee now proposes to construct, install, and operate the Lenior City meter station at Mile Post 3.99, instead of at Mile Post 4.35 south of Main Line Valve 3112-1 as originally proposed, on its 3100 Line in Roane County, Tennessee. East Tennessee also proposes to construct, install, and operate the Etowah meter station at mile Post 3.59 south of Main Line Valve 3217-1 as originally proposed, but on the other side of the road, on its 3200 Line in McMinn County, Tennessee.
                </P>
                <P>
                    East Tennessee also proposes to modify its original proposal with various changes in work space requirements and construction rights-of-way to meet the Commission's template. East Tennessee's other proposed modifications include the following:
                    <PRTPAGE P="33812"/>
                </P>
                <P>(1) Additional temporay work spaces at Mainline Valve Section 3313, Virginia, and Mainline Valve Section 3105, Tennessee;</P>
                <P>(2) Seven new hydrostatic testing manifold location in the vicinity of Mainline Valve Section 3105, Tennessee, and six new hydrostatic testing manifold locations in the vicinity of Mainline Valve Section 3107, Tennessee;</P>
                <P>(3) Four new main line valves, replacement of main line valves, and one new relief valve in the vicinity of Mainline Valve Section 3105, Tennessee;</P>
                <P>(4) One new relief valve in vicinity of Mainline Valve Section 3107, Tennessee;</P>
                <P>(5) New access road in vicinity of Mainline Valve Section 3313, Virginia;</P>
                <P>(6) Five temporary access roads in vicinity of Mainline Valve Section 3105, Tennessee, and four temporary access roads in vicinity of Mainline Valve Section 3107, Virginia_eight of these temporary access roads would be constructed within existing permanent rights-of-way:</P>
                <P>(7) One temporary access road in vicinity of Tennessee River Crossing, Mainline valve Section 3213-1A1/1A2, Tennessee_this temporary access road would be constructed within an existing permanent right-of-way and existing road.</P>
                <P>Any person desiring to be heard or to make any protest with reference to said application should on or before June 9, 2000, file with the Federal Energy Regulatory Commission, 888 First Street, NE, Washington, DC 20426, a motion to intervene or a protest in accordance with the requirements of the Commission's Rules of Practice and Procedure (18 CFR 385.214 or 385.211) and the Regulations under the NGA (18 CFR 157.10) All protests filed with the Commission will be considered by it in determining the appropriate action to be taken but will not serve to make the protestants parties to the proceeding. Any person wishing to become a party to a proceeding or to participate as a party in any hearing therein must file a motion to intervene in accordance with the Commission's Rules.</P>
                <P>Any questions regarding the application should be directed to Susan T. Halbach, Senior Counsel, P.O. Box 2511, Houston, Texas 77252, phone number (713) 420-5751.</P>
                <P>A person obtaining intervenor status will be place on the service list maintained by the Secretary of the Commission and will receive copies of all documents issued by the Commission, filed by the applicant, or filed by all other intervenors. An intervenor can file for rehearing of any Commission order and can petition for court review of any such order. However, an intervenor must serve copies of comments or any other filing it makes with the Commission to every other intervenor in the proceeding, as well as filing an original and 14 copies with the Commission. A person does not have to intervene, however, in order to have comments considered. A person, instead, may submit two copies of such comments to the Secretary of the Commission. Commenters will be placed on the Commission's environmental mailing list, will receive copies of environmental documents, and will be able to participate in meetings associated with the Commission's environmental review process. Commenters will not be required to serve copies of filed document son all other parties. However, 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 rehearing or appeal the Commission's final order to a Federal court.</P>
                <P>Take further notice that, pursuant to the authority contained in and subject to the jurisdiction conferred upon the Federal Energy Regulatory Commission by Sections 7 and 15 of the NGA and the Commission's Rules of Practice and Procedure, a hearing will be held without further notice before the Commission or its designee on this application if no motion to intervene is filed within the time required herein, if the Commission on its own review of the matter finds that the proposal is required by the public convenience and necessity. If a motion for leave to intervene is timely filed, or if the Commission on its own motion believes that a formal hearing is required, further notice of such hearing will be duly given.</P>
                <P>Under the procedure herein provided for, unless otherwise advised, it will be unnecessary for East Tennessee to appear or be represented at the hearing.</P>
                <SIG>
                    <NAME>Linwood A. Watson, Jr.,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13105  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. OA00-4-002]</DEPDOC>
                <SUBJECT>Indianapolis Power &amp; Light Company; Notice of Filing</SUBJECT>
                <DATE>May 19, 2000.</DATE>
                <P>
                    Take notice that on May 1, 2000, Indianapolis Power &amp; Light Company (Indianapolis) submitted revised standards of conduct in response to the Commission's February 24, 2000 Order.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         90 FERC ¶ 61,174 (2000).
                    </P>
                </FTNT>
                <P>Indianapolis states that it served copies of the filing to all parties on the service list, to the Indiana Utility Regulatory Commission and others on the official service list in this proceeding.</P>
                <P>
                    Any person desiring to be heard or to protest said filing should file a motion to intervene or protest 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). All such motions or protests must be filed on or before June 5, 2000. Protests will be considered by the Commission to determine 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 motion to intervene. Copies of Indianapolis's filing are on file with the Commission and are available for public inspection. This filing may also be viewed on the Internet at 
                    <E T="03">http://www.ferc.fed.us/online/rims.htm</E>
                     (call 202-208-2222 for assistance).
                </P>
                <SIG>
                    <NAME>Linwood A. Watson, Jr.,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13107  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. RP00-286-000]</DEPDOC>
                <SUBJECT>Koch Gateway Pipeline Company; Notice of Proposed Changes to FERC Gas Tariff</SUBJECT>
                <DATE>May 19, 2000.</DATE>
                <P>Take notice that on May 16, 2000, Koch Gateway Pipeline Company (Koch) tendered for filing as part of its FERC Gas Tariff, the following tariff sheets, to become effective June 15, 2000:</P>
                <EXTRACT>
                    <PRTPAGE P="33813"/>
                    <HD SOURCE="HD2">Fifth Revised Volume No. 1</HD>
                    <FP SOURCE="FP-1">Seventh Revised Sheet No. 2</FP>
                    <FP SOURCE="FP-1">Fourth Revised Sheet No. 103</FP>
                    <FP SOURCE="FP-1">Fourth Revised Sheet No. 305</FP>
                    <FP SOURCE="FP-1">First Revised Sheet No. 606</FP>
                    <FP SOURCE="FP-1">Fourth Revised Sheet No. 719</FP>
                    <FP SOURCE="FP-1">Second Revised Sheet No. 1004</FP>
                    <FP SOURCE="FP-1">Fourth Revised Sheet No. 1410</FP>
                    <FP SOURCE="FP-1">Sixth Revised Sheet No. 1414</FP>
                    <FP SOURCE="FP-1">Second Revised Sheet No. 1502</FP>
                    <FP SOURCE="FP-1">Third Revised Sheet No. 1703</FP>
                    <FP SOURCE="FP-1">Seventh Revised Sheet No. 1808</FP>
                    <FP SOURCE="FP-1">Fourth Revised Sheet No. 1900</FP>
                    <FP SOURCE="FP-1">Second Revised Sheet No. 2002</FP>
                    <FP SOURCE="FP-1">Second Revised Sheet No. 2003</FP>
                    <FP SOURCE="FP-1">First Revised Sheet No. 2010</FP>
                    <FP SOURCE="FP-1">Ninth Revised Sheet No. 2700</FP>
                    <FP SOURCE="FP-1">Fourth Revised Sheet No. 2703</FP>
                    <FP SOURCE="FP-1">Fifth Revised Sheet No. 3702</FP>
                    <FP SOURCE="FP-1">First Revised Sheet No. 3900</FP>
                    <FP SOURCE="FP-1">Fourth Revised Sheet No. 5000</FP>
                    <FP SOURCE="FP-1">Tenth Revised Sheet No. 5200</FP>
                </EXTRACT>
                <P>Koch states that it has revised the above tariff sheets to reflect minor housekeeping changes for clarification of Koch's FERC Gas Tariff.</P>
                <P>Koch states that copies of this filing have been served upon Koch's customers, state commissions and other interested parties.</P>
                <P>Any person desiring to be heard or to protest said filing should file a motion to intervene or a protest with the Federal Energy Regulatory Commission, 888 First Street, NE, Washington, DC 20426, in accordance with Sections 385.214 or 385.211 of the Commission's Rules and Regulations. All such motions or protests must be filed in accordance with Section 154.210 of the Commission's Regulations. 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 proceedings. Any person wishing to become a party must file a motion to intervene. Copies of this filing are on file with the Commission and are available for public inspection in the Public Reference Room. This filing may be viewed on the web at http://www.ferc.fed.us/online/rims.htm (call 202-208-2222 for assistance).</P>
                <SIG>
                    <NAME>Linwood A. Watson, Jr.,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13113  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket Nos. RP97-14-006]</DEPDOC>
                <SUBJECT>Midwestern Gas Transmission Company; Notice of Negotiated Rate Filing</SUBJECT>
                <DATE>May 19, 2000.</DATE>
                <P>Take notice that on May 15, 2000, Midwestern Gas Transmission Company (Midwestern), tendered for filing certain Negotiated Rate Arrangements. Midwestern requests that the Commission approve the Negotiated Rate Arrangements effective November 1, 2000.</P>
                <P>Midwestern states that the filed Negotiated Rate Arrangements reflect negotiated rates between Midwestern and Nicor Gas (Nicor) for transportation under Rate Schedule FT-A beginning November 1, 2000.</P>
                <P>Any person desiring to be heard or to protest said filing should file a motion to intervene or a protest with the Federal Energy Regulatory Commission, 888 First Street, N.E., Washington, D.C. 20426, in accordance with Sections 385.214 or 385.211 of the Commission's Rules and Regulations. All such motions or protests must be filed in accordance with Section 154.210 of the Commission's Regulations. 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 proceedings. Any person wishing to become a party must file a motion to intervene. Copies of this filing are on file with the Commission and are available for public inspection in the Public Reference Room. This filing may be viewed on the web at http://www.ferc.fed.us/online/rims.htm (call 202-208-2222 for assistance).</P>
                <SIG>
                    <NAME>Linwood A. Watson, Jr.,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13112  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Project No. 1962-000]</DEPDOC>
                <SUBJECT>Pacific Gas &amp; Electric Company; Notice of Meeting</SUBJECT>
                <DATE>May 19, 2000.</DATE>
                <P>Take notice that there will be a full group meeting of the Rock Creek-Cresta Relicensing Collaborative on Monday, June 5, 2000, from 9 a.m. to 4 p.m. at the PG&amp;E offices, 2740 Gateway Oaks Drive, in Sacramento, California. Mark Robinson of the Commission's Office of Energy Projects has been invited to participate by phone for a brief update of the settlement status. Expected participants need to give their names to William Zemke (PG&amp;E) at (415) 973-1646 so that they can get through security.</P>
                <P>For further information, please contact Elizabeth Molloy at (202) 208-0771.</P>
                <SIG>
                    <NAME>Linwood A. Watson, Jr.,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13108  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. EL00-77-000]</DEPDOC>
                <SUBJECT>SkyGen Energy LLC v. Southern Company Services, Inc.; Notice of Complaint</SUBJECT>
                <DATE>May 19, 2000.</DATE>
                <P>Take notice that on May 18, 2000, SkyGen Energy LLC (Complainant) filed with the Federal Energy Regulatory Commission a complaint against Southern Company Services, Inc., as agent for Alabama Power Company, Georgia Power Company, Gulf Power Company, Mississippi Power Company, and Savannah Electric and Power Company (Respondent) pursuant to Rule 206 of the Commission's Rules of Practice and Procedure, 18 CFR 385.206. According to the Complaint, Respondent wrongfully denied a request made by SkyGen Energy Marketing, LLC on behalf of SkyGen and Santa Rosa Energy LLC (Santa Rosa Energy) under its Open Access Transmission Tariff (OATT) because that denial is based upon repudiation of the executed interconnection agreement between the Complainant and Respondent. The Complainant alleges that Respondent is denying Complainant interconnection service (the ability to access its electrical system) and its request for transmission service.</P>
                <P>
                    According to the Complainant, Respondent has planned the addition of its own generation to the Southwest Quadrant of its system while ignoring the addition of Complainant's Facility to the system already accomplished by the executed interconnection agreement. Now, on the basis that the Respondent cannot honor the Complainant's interconnection agreement by adding its 
                    <PRTPAGE P="33814"/>
                    Facility to the Southwest Quadrant, Respondent has denied Complainant's request for firm transmission service.
                </P>
                <P>Complainant also asserts that Respondent has failed to consider reassignment of transmission capacity reserved for native load use but not currently needed or used, operating restrictions and/or special protection systems, or redispatch to accommodate Complainant's request for firm transmission service. According to the Complaint, Respondent has refused to expeditiously use a Power System Stabilizer solution it has used in order to accommodate its own generation, and which has been demonstrated to be a means that can accommodate Respondent's request for firm transmission service.</P>
                <P>Questions concerning the Complaint may be directed to counsel for Complainant, Robert L. Daileader, Jr., Nixon Peabody LLP, Suite 700, One Thomas Circle, NW, Washington, DC 20005, Phone 202/457-5318, Fax 202/457-5355, e-mail rdaileader@nixonpeabody.com.</P>
                <P>Any person desiring to be heard or to protest this filing should file a motion to intervene or protest 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). All such motions or protests must be filed on or before May 31, 2000. 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 motion to intervene. Copies of this filing are on file with the Commission and are available for public inspection in the Public Reference Room. This filing may also be viewed on the Internet at ­ http:/www.ferc.fed.us/online/rims.htm (call 202-208-2222) for assistance. Answers to the complaint shall also be due on or before May 31, 2000.</P>
                <SIG>
                    <NAME>Linwood A. Watson, Jr.,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13106  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket Nos. RP96-312-028]</DEPDOC>
                <SUBJECT>Tennessee Gas Pipeline Company; Notice of Negotiated Rate Filing</SUBJECT>
                <DATE>May 19, 2000.</DATE>
                <P>Take notice that on May 15, 2000, Tennessee Gas Pipeline Company (Tennessee), tendered for filing certain Negotiated Rate Arrangement. Tennessee requests that the Commission approve the Negotiated Rate Arrangement effective November 1, 2000.</P>
                <P>Tennessee states that the filed Negotiated Rate Arrangement reflects negotiated rates between Tennessee and Nicor Gas (“Nicor”) for transportation under Rate Schedule FT-A beginning November 1, 2000.</P>
                <P>Any person desiring to be heard or to protest said filing should file a motion to intervene or a protest with the Federal Energy Regulatory Commission, 888 First Street, N.E., Washington, D.C. 20426, in accordance with Sections 385.214 or 385.211 of the Commission's Rules and Regulations. All such motions or protests must be filed in accordance with Section 154.210 of the Commission's Regulations. 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 proceedings. Any person wishing to become a party must file a motion to intervene. Copies of this filing are on file with the Commission and are available for public inspection in the Public Reference Room. This filing may be viewed on the web at http://www.ferc.fed.us/online/rims.htm (call 202-208-2222 for assistance).</P>
                <SIG>
                    <NAME>Linwood A. Watson, Jr.,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13111  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Notice of Dam Remediation Work and Soliciting Comments, Motions To Intervene, and Protests</SUBJECT>
                <DATE>May 19, 2000.</DATE>
                <P>Take notice that the following hydroelectric application has been filed with the Commission and is available for public inspection: </P>
                <P>
                    a. 
                    <E T="03">Application Type:</E>
                     Request to deviate from the target minimum flow required by article 39 below Blue Lake and Rucker Lake during necessary dam remediation.
                </P>
                <P>
                    b. 
                    <E T="03">Project No.</E>
                     2310-106.
                </P>
                <P>
                    c. 
                    <E T="03">Date Filed:</E>
                     May 9, 2000.
                </P>
                <P>
                    d. 
                    <E T="03">Applicant:</E>
                     Pacific Gas and Electric Company.
                </P>
                <P>
                    e. 
                    <E T="03">Name of Project:</E>
                     Drum-Spaulding Project.
                </P>
                <P>
                    f. 
                    <E T="03">Location:</E>
                     The project is located on the South Yuba and Bear Rivers in Nevada County and Placer County, California.
                </P>
                <P>
                    g. 
                    <E T="03">Filed Pursuant to:</E>
                     Section 12.39 of the Commission's Regulations.
                </P>
                <P>
                    h. 
                    <E T="03">Applicant Contact:</E>
                     Mr. Richard Doble, Pacific Gas and Electric Company (PG&amp;E), Mail Code N11C, P.O. Box 770000, San Francisco, CA 94177.
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     Any questions on this notice should be addressed to Diana Shannon at 202-208-7774, or e-mail address 
                    <E T="03">diana.shannon@ferc.fed.us.</E>
                </P>
                <P>
                    j. 
                    <E T="03">Deadline for filing comments and or motions:</E>
                     June 14, 2000.
                </P>
                <P>All documents (original and eight copies) should be filed with Mr. David P. Boergers, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE, Washington, DC 20426.</P>
                <P>Please reference the following number, P-2310-106, on any comments or motions filed.</P>
                <P>
                    k. 
                    <E T="03">Description of Proposal:</E>
                     Remediation of the existing dam at Blue Lake is necessary to improve the stability of the downstream slope. The work is required under Part 12 of the Commission's regulations. A drawdown of Blue Lake and a deviation from the target minimum flow, required by article 39, is necessary at Blue and Rucker Lakes (downstream of Blue Lake). Flow will be maintained at or above the allowable minimum stipulated in article 39. The work will be performed from July-October 2000. Refill of the lake will begin after completion of the work and may take up to three years due to the lake's small drainage area. The licensee has consulted with the FWS, CDFG, FS, and the Regional Water Quality Control Board regarding the necessary remediation.
                </P>
                <P>
                    l. 
                    <E T="03">Locations of the Application:</E>
                     A copy of the application is available for inspection and reproduction at the Commission's Public Reference Room, 888 First Street, NE, Room 2A, Washington, DC 20426, or call 202-208-1371. The application may be viewed on-line at http:
                    <E T="03">\\www.ferc.fed.us/online/rims.htm</E>
                     (call 202-208-2222 for assistance). A copy is also available for inspection and reproduction at the address in item h above.
                    <PRTPAGE P="33815"/>
                </P>
                <P>m. Individuals desiring to be included on the Commission's mailing list should so indicate by writing to the Secretary of the Commission.</P>
                <P>Comments, Protests, or Motions to Intervene—Anyone submit comments, a protest, or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, .211, .214. In determining the appropriate action to take, the Commission will consider all protests or other comments filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any comments, protests, or motions to intervene must be received on or before the specified comment date for the particular application.</P>
                <P>Filing and Service of Responsive Documents—Any filing must bear in all capital letters the title “COMMENTS”, “RECOMMENDATIONS FOR TERMS AND CONDITIONS”, “PROTEST”, OR “MOTION TO INTERVENE”, as applicable, and the Project Number of the particular application to which the filing refers. Any of the above-named documents must be filed by providing the original and the number of copies provided by the Commission's regulations to: The Secretary, Federal Energy Regulatory Commission, 888 First Street, NE, Washington, DC 20426. A copy of any motion to intervene must also be served upon each representative of the Applicant specified in the particular application.</P>
                <P>Agency Comments—Federal, state, and local agencies are invited to file comments on the described application. A copy of the application may be obtained by agencies directly from the Applicant. If an agency does not file comments within the time specified for filing comments, it will be presumed to have no comments. One copy of an agency's comments must also be sent to the Applicant's representatives.</P>
                <SIG>
                    <NAME>Linwood A. Watson, Jr.,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13109  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Notice of Application for Transfers of Licenses and Soliciting Comments, Motions To Intervene, and Protests</SUBJECT>
                <DATE>May 19, 2000.</DATE>
                <P>Take notice that the following hydroelectric application has been filed with the Commission and is available for public inspection:</P>
                <P>
                    a.
                    <E T="03"> Application Type:</E>
                     Transfers of Licenses.
                </P>
                <P>
                    b.
                    <E T="03"> Project Nos:</E>
                     2343-041, 2516-018, and 2517-004.
                </P>
                <P>
                    c.
                    <E T="03"> Date Filed:</E>
                     May 5, 2000.
                </P>
                <P>
                    d.
                    <E T="03"> Applicants:</E>
                     Potomac Edison Company, PE Transferring Agent, L.L.C. (to be formed), PE Genco (to be formed), and Allegheny Energy Supply Company, L.L.C.
                </P>
                <P>
                    e.
                    <E T="03"> Names and Locations of Projects:</E>
                     The Millville Project is on the Shenandoah River in Jefferson County, West Virginia and the Dam No. 4 and Dam No. 95. Hydro Stations are on the Potomac River in Berkeley County, West Virginia. The projects do not occupy federal or tribal lands.
                </P>
                <P>
                    f.
                    <E T="03"> Filed Pursuant to:</E>
                     Federal Power Act, 16 U.S.C. 791(a)-825(r).
                </P>
                <P>
                    g.
                    <E T="03"> Applicant Contacts:</E>
                     Mr. David C. Benson, Allegheny Energy Supply, RR 12, Box 1000, Roseytown Road, Greensburg, PA 15601, (724) 853-3790, and Mr. John A. Whittaker, IV, Winston &amp; Strawn, 1400 L Street, NW, Washington, DC 20005, (202) 371-5766.
                </P>
                <P>
                    h.
                    <E T="03"> FERC Contact:</E>
                     Any questions on this notice should be addressed to James Hunter at (202) 219-2839.
                </P>
                <P>
                    i.
                    <E T="03"> Deadline for filing comments and or motions:</E>
                     June 14, 2000.
                </P>
                <P>All documents (original and eight copies) should be filed with: David P. Boergers, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE, Washington DC 20426.</P>
                <P>Please include the noted project numbers on any comments or motions filed.</P>
                <P>
                    j.
                    <E T="03"> Description of Proposal:</E>
                     Applicants propose transfers of the licenses for these three projects from Potomac Edison Company to PE Transferring Agency, L.L.C., a soon-to-be-formed wholly-owned subsidiary of Potomac Edison; then to a yet-to-be-formed-and-named affiliate of Potomac Edison, referred to as PE Genco; and finally to Allegheny Energy Supply Company, L.L.C. Transfer is being sought as part of an intra-corporate reorganization of Potomac Edison's parent company, Allegheny Energy, Inc.
                </P>
                <P>The transfer application was filed within five years of the expiration of the licenses for Project Nos. 2516 and 2517. In Hydroelectric Relicensing Regulations Under the Federal Power Act (54 Fed. Reg. 23,756; FERC Stat. and Regs., Regs. Preambles 1986-1990 30,854 at p. 31,437), the Commission declined to forbid all license transfers during the last five years of an existing license, and instead indicated that it would scrutinize all such transfer requests to determine if the transfer's primary purpose was to give the transferee an advantage in relicensing (id. at p. 31,438 n. 318).</P>
                <P>
                    k.
                    <E T="03"> Locations of the application:</E>
                     A copy of the application is available for inspection and reproduction at the Commission's Public Reference Room, located at 888 First Street, NE, Room 2A, Washington, DC 20426, or by calling (202) 208-1371. The application may be viewed on the web at www.ferc.fed.us/online/rims.htm (Call (202) 208-2222 for assistance). A copy is also available for inspection and reproduction at the addresses in item g above.
                </P>
                <P>
                    l.
                    <E T="03"> Individuals desiring to be included on the Commission's mailing list should so indicate by writing to the Secretary of the Commission.</E>
                </P>
                <P>Comments, Protests, or Motions to Intervene—Anyone may submit comments, a protest, or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, .211, .214. In determining the appropriate action to take, the Commission will consider all protests or other comments filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any comments, protests, or motions to intervene must be received on or before the specified comment date for the particular application.</P>
                <P>Filing and Service of Responsive Documents—Any filings must bear in all capital letters the title “Comments”, “Recommendations for Terms and Conditions”, “Protest”, or “Motion to Intervene” as applicable, and the Project Number of the particular application to which the filing refers. Any of the above-named documents must be filed by providing the original and the number of copies provided by the Commission's regulations to: The Secretary, Federal Energy Regulatory Commission, 888 First Street, NE, Washington, DC 20426. A copy of any motion to intervene must also be served upon each representative of the Applicant specified in the particular application.</P>
                <P>
                    Agency Comments—Federal, state, and local agencies are invited to file comments on the described application. A copy of the application may be obtained by agencies directly from the Applicant. If an agency does not file  comments within the time specified for filing comments, it will be presumed to have no comments. One copy of an 
                    <PRTPAGE P="33816"/>
                    agency's comments must also be sent to the Applicant's representatives.
                </P>
                <SIG>
                    <NAME>Linwood A. Watson, Jr.,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13110 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. RM93-11-000]</DEPDOC>
                <SUBJECT>Revisions to Oil Pipeline Regulations Pursuant to the Energy Policy Act of 1992</SUBJECT>
                <DATE>May 19, 2000.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Energy Regulatory Commission, Department of Energy.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of annual change in the Producer Price Index for Finished Goods, minus one percent. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Commission is issuing the index that oil pipelines must apply to their July 1, 1999-June 30, 2000 index ceiling levels to compute their index ceiling levels for the period July 1, 2000 through June 30, 2001, in accordance with 18 CFR 342.3(d). This index, which is the percent change (expressed as a decimal) in the annual average Producer Price Index for Finished Goods from 1998 to 1999, minus one percent, is 0.007598. Oil pipelines must multiply their July 1, 1999-June 30, 2000 index ceiling levels by 1.007598 to compute their index ceiling levels for the period July 1, 2000 through June 30, 2001.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David Ulevich, Office of Markets, Tariffs, and Rates, Corporate Applications, Group 2, Federal Energy Regulatory Commission, 888 First Street, NE, Washington, DC 20426, (202) 208-0678.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the Internet through FERC's Home Page (
                    <E T="03">http://www./ferc./fed.us</E>
                    ) and in FERC's Public Reference Room during normal business hours (8:30 a.m. to 5:00 p.m. Eastern time) at 888 First Street, N.E., Room 2A, Washington, DC 20426.
                </P>
                <P>From FERC's Home Page on the Internet, this information is available in both the Commission Issuance Posting System (CIPS) and the Records and Information management System (RIMS).</P>
                <P>CIPS provides access to the texts of formal documents issued by the Commission since November 14, 1994. CIPS can be accessed using the CIPS link or the Energy Information Online icon. The full text of this document is available on CIPS in ASCII and WordPerfect 8.0 format for viewing, printing, and/or downloading.</P>
                <P>RIMS contains images of documents submitted to an issued by the Commission after November 16, 1981. Documents from November 1995 to the present can be viewed and printed from FERC's Home page using the RIMS link or the Energy Information Online icon. Descriptions of documents back to November 16, 1981, are also available from RIMS-on-the-Web; requests for copies of these and other older documents should be submitted to the Public Reference Room.</P>
                <P>
                    User assistance is available for RIMS, CIPS, and the Website during normal business hours from our Help line at (202) 208-222 (E-Mail to 
                    <E T="03">WebMaster@ferc.fed.us</E>
                    ) or the Public Reference at (202) 208-1371 (E-Mail to 
                    <E T="03">public.reference room@ferc.fed.us</E>
                    ).
                </P>
                <P>During normal business hours, documents can also be viewed and/or printed in FERC's Public Reference Room where RIMS, CIPS, and the FERC Website are available. User assistance is also available.</P>
                <P>The Commission's regulations include a methodology for oil pipelines to change their rates through use of an index system that establishes ceiling levels for such rates. The index system as set forth at 18 CFR 342.3 is based on the annual change in the Producer Price Index for Finished Goods (PPI-FG), minus one percent. The regulations provide that each year the Commission will publish an index reflecting the final change in the PPI-FG, minus one percent, after the final PPI-FG is made available by the Bureau of Labor Statistics in May of each calendar year.</P>
                <P>
                    The annual average PPI-FG index figure for 1998 was 130.7 and the annual average PPI-FG index figure for 1999 was 133.0.
                    <SU>1</SU>
                    <FTREF/>
                     Thus, the percent change (expressed as a decimal) in the annual average PPI-FG from 1998 to 1999, minus one percent is 0.007598.
                    <SU>2</SU>
                    <FTREF/>
                     Oil pipelines must multiply their July 1, 1999-June 30, 2000 index ceiling levels by 1.007598 
                    <SU>3</SU>
                    <FTREF/>
                     to compute their index ceiling levels for the period July 1, 2000, through June 30, 2001, in accordance with 18 CFR 342.3(d).
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The final figure for the annual average PPI-FG is published by the Bureau of Labor Statistics in mid-May of each year. This figure is publicly available from the Division of Industrial Prices and Price Indexes of the Bureau of Labor Statistics, at (202) 606-7705, and is available in print in August in Table 1 of the annual data supplement to the BLS publication 
                        <E T="03">Producer Price Indexes.</E>
                         The PPI data are also available via the Internet. The Internet address is 
                        <E T="03">http://www.fedstats.gov</E>
                        . This site contains data from a number of government agencies; to obtain the BLS data, click on agencies, then click on Bureau of Labor Statistics, then click on data, Most Requested Series, scroll to Producer Price Indexes-Commodities (Finished Goods), for the latest available data.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         [133.0-130.7]/130.7=0.017598-.01=0.007598.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         1+(0.007598)=1.007598.
                    </P>
                </FTNT>
                <P>
                    To obtain July 1, 1999-June 30, 2000 ceiling levels, pipelines must first calculate their ceiling levels for the January 1, 1995-June 30, 1995 index period, by multiplying their December 31, 1994 rates by 1.002175. Pipelines must then multiply those ceiling levels by 0.996415 to obtain the July 1, 1995-June 30, 1996 ceiling levels. Then pipelines must multiply their July 1, 1995-June 30, 1996 ceiling levels by 1.009124 to obtain the July 1, 1996-June 30, 1997 ceiling levels, and multiply the July 1, 1996-June 30, 1997 ceiling levels by 1.016583 to obtain the July 1, 1997-June 30, 1998 ceiling levels. Pipelines then must multiply the July 1, 1997-June 30, 1998 ceiling levels by 0.993808 to obtain the July 1, 1998-June 30, 1999 ceiling levels. Then, pipelines must multiply the July 1, 1998-June 30, 1999 ceiling levels by 0.981654 to obtain the July 1, 1999-June 30, 2000 ceiling levels. Finally, pipelines must multiply the July 1, 1999-June 30, 2000 ceiling levels by 1.007698 to obtain the July 1, 2000-June 30, 2001 ceiling levels. 
                    <E T="03">See Explorer Pipeline Company</E>
                    , 71 FERC 
                    <E T="8401">¶</E>
                     61,416 at n.6 (1995) for an explanation of how ceiling levels must be calculated.
                </P>
                <SIG>
                    <NAME>Linwood A. Watson, Jr.,</NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13115 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Docket No. RM98-1-000] </DEPDOC>
                <SUBJECT>Regulations Governing Off-the-Record Communications; Public Notice </SUBJECT>
                <DATE>May 19, 2000. </DATE>
                <P>This constitutes notice, in accordance with 18 CFR 385.2201(h), of the receipt of exempt and prohibited off-the-record communications. </P>
                <P>
                    Order No. 607 (64 FR 51222, September 22, 1999) requires Commission decisional employees, who make or receive an exempt or a prohibited off-the-record communication relevant to the merits of a contested on-the-record proceeding, 
                    <PRTPAGE P="33817"/>
                    the deliver a copy of the communication, if written, or summary of the substance of any oral communication, to the Secretary. 
                </P>
                <P>Prohibited communications will be included in a public, non-decisional file associated with, but not part of, the decisional record of the proceeding. Unless the Commission determines that the prohibited communication and any responses thereto should become part of the decisional record, the prohibited off-the-record communication will not be considered by the Commission in reaching its decision. Parties to a proceeding may seek the opportunity to respond to any facts or contentions made in a prohibited off-the-record communication, and may request that the Commission place the prohibited communication and responses thereto in the decisional record. The Commission will grant such requests only when in determines that fairness so requires. </P>
                <P>Exempt off-the-record communications will be included in the decisional record of the proceeding, unless the communication was with a cooperating agency as described by 40 CFR 1501.6, made under 18 CFR 385.2201(e)(1)(v). </P>
                <P>The following is a list of exempt and prohibited off-the-record communications received in the Office of the Secretary within the preceding 14 days. The document may be viewed on the Internet at http://www.ferc.fed.us/online/rims.htm (call 202-208-2222 for assistance). </P>
                <HD SOURCE="HD1">Exempt </HD>
                <GPOTABLE COLS="3" OPTS="L2,tp0,p1,8/9,i1" CDEF="s100,10,xls100">
                    <BOXHD>
                        <CHED H="1">  </CHED>
                        <CHED H="1">  </CHED>
                        <CHED H="1">  </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1. Project Nos. 2687, 2699, 2019</ENT>
                        <ENT>5-10-00</ENT>
                        <ENT>Frank Winchell. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2. CP00-14-000</ENT>
                        <ENT>5-1-00</ENT>
                        <ENT>Kim Jessen. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3. CP00-14-000</ENT>
                        <ENT>4-18-00</ENT>
                        <ENT>Janet Rowe. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4. CP00-14-000</ENT>
                        <ENT>4-11-00</ENT>
                        <ENT>Sneed Collard. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5. CP00-14-000</ENT>
                        <ENT>4-11-00</ENT>
                        <ENT>Sneed Collard. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6. CP00-36-000</ENT>
                        <ENT>5-1-00</ENT>
                        <ENT>Anne E. Haaker. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7. CP98-143-000</ENT>
                        <ENT>4-20-00</ENT>
                        <ENT>Clyde N. Thompson. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8. Project Nos. 11563, 2019 and 2699</ENT>
                        <ENT>5-10-00</ENT>
                        <ENT>Chuck Whatford. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="09">19. Project No. 2197-038</ENT>
                        <ENT>5-12-00</ENT>
                        <ENT>Steve Kartalia, FERC. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10. Project No. 2055-006</ENT>
                        <ENT>5-15-00</ENT>
                        <ENT>Dianne Rodman, FERC. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">11. CP00-14-000</ENT>
                        <ENT>5-2-00</ENT>
                        <ENT>Bill Sendelbach. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12. CP00-14-000</ENT>
                        <ENT>5-8-00</ENT>
                        <ENT>Joe Peterson. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">13. CP00-14-000</ENT>
                        <ENT>5-11-00</ENT>
                        <ENT>Joe Peterson. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">14. CP00-14-000</ENT>
                        <ENT>5-11-00</ENT>
                        <ENT>Todd Mattson. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15. CP00-14-000</ENT>
                        <ENT>5-11-00</ENT>
                        <ENT>Todd Mattson. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">16. CP00-14-000</ENT>
                        <ENT>4-24-00</ENT>
                        <ENT>James J. Slack. </ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <NAME>Linwood A. Watson, Jr., </NAME>
                    <TITLE>Acting Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13104  Filed  5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <SUBJECT>Public Information Collections Approved by Office of Management and Budget</SUBJECT>
                <DATE>May 19, 2000. </DATE>
                <P>The Federal Communications Commission (FCC) has received Office of Management and Budget (OMB) approval for the following public information collections pursuant to the Paperwork Reduction Act of 1995, Public Law 104-13. 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. For further information contact Shoko B. Hair, Federal Communications Commission, (202) 418-1379. </P>
                <HD SOURCE="HD1">Federal Communications Commission </HD>
                <P>
                    <E T="03">OMB Control No.:</E>
                     3060-0715. 
                </P>
                <P>
                    <E T="03">Expiration Date:</E>
                     06/30/2001. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Implementation of the Telecommunications Act of 1996: Telecommunications Carriers' Use of Customer Proprietary Network Information and Other Customer Information—CC Docket 96-115. 
                </P>
                <P>
                    <E T="03">Form No.:</E>
                     N/A. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for profit. 
                </P>
                <P>
                    <E T="03">Estimated Annual Burden:</E>
                     6832 respondents; 90.28 hours per response (avg). 616,817 total annual burden hours (for all collections under this control number). 
                </P>
                <P>
                    <E T="03">Estimated Annual Reporting and Recordkeeping Cost Burden:</E>
                     $229,520,000. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion; One-time requirement; Recordkeeping; Third party disclosure. 
                    <E T="03">Description:</E>
                     In the Order on Reconsideration in CC Docket No. 96-115 (released 9/3/99), the Commission reconsidered the previous CPNI Order, addressed petitions for forbearance from the requirements, and established rules to implement section 222. Among other things, carriers are permitted to use CPNI, without customer approval, under certain conditions. (Number of respondents: 4832; hours per response 39 hours; total annual burden: 188,448 hours). Carriers must obtain express customer approval to use CPNI to market service outside the customer's existing service relationship. (Number of respondents: 4832; hours per response: 30 minutes; total annual burden 2416 hours). Carriers must provide a one-time notification of customer's CPNI rights prior to any solicitation for approval. (Number of respondents: 4832; hours per response: 78 hours; total annual burden: 376,896 hours). Pursuant to this one-time notification requirement, these carriers must maintain a record of such notifications for a period of at least one year. (Number of respondents: 4832; hours per response: 30 minutes; total annual burden 2416 hours). Telecommunications carriers must establish a supervisory review process regarding carrier compliance with the rules in Part 64 for outbound marketing situations. (Number of respondents: 4832; hours per response: 15 minutes; total annual burden: 1208 hours). All telecommunications carriers must obtain on an annual basis a certification signed by a current officer attesting that he or she has personal knowledge that the carrier is in compliance with the Commission's rules and to create an accompanying statement explaining how the carriers are implementing the rules and safeguards. (Number of respondents: 4832; hours per response: 1 hour; total annual burden: 4832 hours). LECs must disclose aggregate customer information to others upon request, when they use or disclose the aggregate customer information for marketing service to which the customer does not subscribe. (Number of respondents: 1400; hours per response: 1 hours; total annual burden: 1400 hours). Section 22(c)(2) requires carriers 
                    <PRTPAGE P="33818"/>
                    when presented with a customer's affirmative written request, to provide that customer's CPNI to any person designated in the written authorization. (Number of respondents: 500; hours per response: 5 hours; total annual burden; 2500 hours). Obligation to respond: Mandatory. 
                </P>
                <P>Public reporting burden for the collection of information is as noted above. Send comments regarding the burden estimate or any other aspect of the collections of information, including suggestions for reducing the burden to Performance Evaluation and Records Management, Washington, DC 20554. </P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Magalie Roman Salas,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13142 Filed 5-25-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6712-01-U</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL MARITIME COMMISSION </AGENCY>
                <SUBJECT>Notice of Agreement(s) Filed </SUBJECT>
                <P>
                    The Commission hereby gives notice of the filing of the following agreement(s) under the Shipping Act of 1984. Interested parties can review or obtain copies of agreements at the Washington, DC offices of the Commission, 800 North Capitol Street NW, Room 962. Interested parties may submit comments on an agreement to the Secretary, Federal Maritime Commission, Washington, DC 20573, within 10 days of the date this notice appears in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <P>
                    <E T="03">Agreement No.:</E>
                     011512-003. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Slot Charter Agreement Between Hyundai Merchant Marine Co., Ltd. and MSC. 
                </P>
                <P>
                    <E T="03">Parties:</E>
                </P>
                <FP SOURCE="FP1-2">Hyundai Merchant Marine Co., Ltd. </FP>
                <FP SOURCE="FP1-2">Mediterranean Shipping Co., S.A. </FP>
                <P>
                    <E T="03">Synopsis:</E>
                     The proposed agreement modification clarifies and updates the parties' understandings under their currently effective agreement. 
                </P>
                <P>
                    <E T="03">Agreement No.:</E>
                     011709. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     CCNI/CTE Space Charter Agreement.
                </P>
                <P>
                    <E T="03">Parties:</E>
                </P>
                <FP SOURCE="FP1-2">Compania Chilena de Navegacion Interoceanica S.A. </FP>
                <FP SOURCE="FP1-2">Compania Transatlantica Espanola S.A. </FP>
                <P>
                    <E T="03">Synopsis:</E>
                     The proposed agreement authorizes the parties to charter vessel space to each other in the trade between Puerto Rico and ports in Europe, the Mediterranean, Chile, Peru, Ecuador, Colombia, Panama, and Venezuela. The parties request expedited review.
                </P>
                <P>
                    <E T="03">Agreement No.:</E>
                     201102. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     License Agreement Between SC State Ports Authority and Charleston International. 
                </P>
                <P>
                    <E T="03">Parties:</E>
                </P>
                <FP SOURCE="FP1-2">South Carolina State Ports Authority </FP>
                <FP SOURCE="FP1-2">Charleston International Ports, LLC. </FP>
                <P>
                    <E T="03">Synopsis:</E>
                     The agreement grants Charleston International a 30-year license to operate a breakbulk marine terminal. The parties have requested expedited handling for this agreement. 
                </P>
                <SIG>
                    <FP>By Order of the Federal Maritime Commission.</FP>
                    <DATED>Dated: May 19, 2000.</DATED>
                    <NAME>Bryant L. VanBrakle, </NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13089 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6730-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL RESERVE SYSTEM </AGENCY>
                <SUBJECT>Change in Bank Control Notices; Acquisitions of Shares of Banks or Bank Holding Companies </SUBJECT>
                <P>The notificants listed below have applied under the Change in Bank Control Act (12 U.S.C. 1817(j)) and § 225.41 of the Board's Regulation Y (12 CFR 225.41) to acquire 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 June 8, 2000. </P>
                <P>A. Federal Reserve Bank of Minneapolis (JoAnne F. Lewellen, Assistant Vice President) 90 Hennepin Avenue, Minneapolis, Minnesota 55480-0291: </P>
                <P>1. David C. Reiling, Minneapolis, Minnesota; to acquire voting shares of University Financial Corporation, Saint Paul, Minnesota, and thereby indirectly acquire voting shares of University National Bank, Saint Paul, Minnesota. </P>
                <SIG>
                    <DATED>Board of Governors of the Federal Reserve System, May 19, 2000. </DATED>
                    <NAME>Robert deV. Frierson, </NAME>
                    <TITLE>Associate Secretary of the Board. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13129 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6210-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM </AGENCY>
                <SUBJECT>Formations of, Acquisitions by, and Mergers of Bank Holding Companies </SUBJECT>
                <P>
                    The companies listed in this notice have applied to the Board for approval, pursuant to the Bank Holding Company Act of 1956 (12 U.S.C. 1841 
                    <E T="03">et seq.</E>
                    ) (BHC Act), Regulation Y (12 CFR part 225), and all other applicable statutes and regulations to become a bank holding company and/or to acquire the assets or the ownership of, control of, or the power to vote shares of a bank or bank holding company and all of the banks and nonbanking companies owned by the bank holding company, including the companies listed below. 
                </P>
                <P>The 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 application also will 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. Additional information on all bank holding companies may be obtained from the National Information Center website at www.ffiec.gov/nic/. </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 19, 2000. </P>
                <P>
                    <E T="04">A. Federal Reserve Bank of Minneapolis</E>
                     (JoAnne F. Lewellen, Assistant Vice President) 90 Hennepin Avenue, Minneapolis, Minnesota 55480-0291: 
                </P>
                <P>
                    <E T="03">1. MSB Financial, Inc.,</E>
                     Manhattan, Montana; to become a bank holding company by acquiring 100 percent of the voting shares of Manhattan State Bank, Manhattan, Montana. 
                </P>
                <SIG>
                    <DATED>Board of Governors of the Federal Reserve System, May 19, 2000. </DATED>
                    <NAME>Robert deV. Frierson, </NAME>
                    <TITLE>Associate Secretary of the Board. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13128 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6210-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="33819"/>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention </SUBAGY>
                <DEPDOC>[Program Announcement 00116] </DEPDOC>
                <SUBJECT>Cooperative Agreement to Enhance Pediatric and Pregnancy Nutrition Surveillance Systems Data Items; Notice of Availability of Funds </SUBJECT>
                <HD SOURCE="HD1">A. Purpose </HD>
                <P>The Centers for Disease Control and Prevention (CDC) announces the availability of fiscal year (FY) 2000 funds for a cooperative agreement program for the (1) Pediatric Nutrition Surveillance System (PedNSS), and (2)Pregnancy Nutrition Surveillance System (PNSS). </P>
                <P>CDC is committed to achieving the health promotion and disease prevention objectives of “Healthy People 2010” a national activity to reduce morbidity and mortality and improve the quality of life. This announcement is related to the focus areas of Public Health Infrastructure, Nutrition and Overweight; and Maternal, Infant, and Child Health. For the conference copy of “Healthy People 2010,” visit the internet site: &lt;http://www.health.gov/healthypeople&gt;. </P>
                <P>The purpose of this program is to improve the capacity to conduct continuous program-based pediatric and pregnancy nutrition surveillance by adding relevant data items to enhance the ability to monitor the health and nutrition-related problems of women and children. For additional background information see Attachment I. </P>
                <HD SOURCE="HD1">B. Eligible Applicants </HD>
                <P>Assistance will be provided only to the health departments of States or their bona fide agents that have submitted 1998 or 1999 PedNSS and/or PNSS files which are included in the national PedNSS and/or PNSS reports. Eligible applicants could include the District of Columbia, the Commonwealth of Puerto Rico, the Virgin Islands, the Commonwealth of the Northern Mariana Islands, American Samoa, Guam, federally recognized Indian tribal governments, the Federated States of Micronesia, the Republic of the Marshall Islands, and the Republic of Palau. </P>
                <HD SOURCE="HD1">C. Availability of Funds </HD>
                <P>Approximately $250,000 is available in FY 2000 to fund approximately 4 awards. It is expected that the average award will be $60,000, ranging from $45,000 to $65,000. It is expected that the awards will begin on or about September 30, 2000, and will be made for a 12-month budget period within a project period of 1 year. Funding estimates may change. </P>
                <HD SOURCE="HD2">Use of Funds </HD>
                <HD SOURCE="HD3">Funding Preferences </HD>
                <P>Funding preference will be given to eligible applicants that submit an application to add Core and Supplemental data items to both the PedNSS and PNSS (Record specifications, field explanations, and code definitions for data items are included in Attachment I). </P>
                <HD SOURCE="HD1">D. Program Requirements </HD>
                <P>
                    In conducting activities to achieve the purposes of this program, the recipient will be responsible for the activities under 
                    <E T="03">1. Recipient Activities</E>
                    , and CDC will be responsible for the activities under 
                    <E T="03">2. CDC Activities</E>
                    . 
                </P>
                <HD SOURCE="HD2">1. Recipient Activities </HD>
                <P>a. Expand the PedNSS and/or PNSS to include core and supplemental data items that are routinely collected in public health clinics. Applicants should be willing to include the following core data items in their nutrition surveillance system including: (1) Household Income, (2) Household Size, (3) Date of Height and Weight Measure, (4) Date of Hemoglobin/Hematocrit Measure, and (5) for PedNSS only, Date of Most Recent Breastfeeding Response. </P>
                <P>In addition, applicants participating in PedNSS shall be willing to add 3 of the 4 PedNSS supplemental data items including: (1) Zip Code, (2) Introduction to Supplementary Feeding, (3) TV/Video Viewing, and (4) Household smoking. </P>
                <P>Applicants participating in PNSS shall be willing to add 4 of the 5 PNSS supplemental data items including: (1) Zip Code, (2) Gestational Diabetes, (3) High Blood Pressure During Pregnancy, (4) Pre-pregnancy Multivitamin Consumption, and (5) Multivitamin Consumption During Pregnancy . </P>
                <P>b. Plan and implement procedures for ensuring the completeness and quality of the data, including training and data editing. </P>
                <P>c. Propose an evaluation strategy to assess the usefulness of the suggested core and supplemental data items for program planning </P>
                <P>d. Prepare and disseminate surveillance information through presentation and publication in appropriate forums. </P>
                <HD SOURCE="HD2">2. CDC Activities </HD>
                <P>a. Assist in the design of standardized data items, definitions, procedures, and methods to collect the desired surveillance information.</P>
                <P> b. Provide training and consultation on the rationale, code definitions and methods to collect new core and supplemental data items. </P>
                <P>c. Provide technical support for data processing or assist state participants in developing appropriate data-processing capabilities. </P>
                <P>d. Assist the recipient in evaluating the usefulness of the suggested core and supplemental data items. </P>
                <P>e. Assist the recipient in preparing and presenting Program-relevant surveillance findings to appropriate state and national audiences. </P>
                <HD SOURCE="HD1">E. Application Content </HD>
                <P>Use the information in the Program Requirements, Other Requirements, and Evaluation Criteria sections to develop the application content. Your application will be evaluated on the criteria listed, so it is important to follow them in laying out your program plan. The narrative should be no more than 15 double-spaced pages, printed on one side, with one inch margins, and unreduced font. </P>
                <HD SOURCE="HD2">1. Table of Contents </HD>
                <HD SOURCE="HD2">2. Plan </HD>
                <P>a. Define data items to be collected. List the core and supplemental data items that will be included in the revised PedNSS and PNSS transaction files (Record specifications, field explanations, and code definitions for data items are included in Attachment I). </P>
                <P>b. Describe the architecture and software of the WIC information system and identify key project staff that will update and test the revised transaction files for PedNSS and PNSS. Include the resume and job descriptions for key project staff in the supporting materials. </P>
                <P>c. Define methods to establish data collection for the new core or supplemental data items.</P>
                <P>d. Define the process for development and testing of the transaction file(s) to ensure completeness and accuracy of the file(s).</P>
                <P>e. Define the process for establishing routine submission of future files. </P>
                <P>f. Describe a plan to evaluate the usefulness of the suggested core and supplemental data items.</P>
                <P>g. Outline a time schedule for activities listed under c, d, e, and f. </P>
                <HD SOURCE="HD1">F. Submission and Deadline </HD>
                <P>
                    Submit the original and two copies of PHS 5161-1 (OMB Number 0937-0189). Forms are available at the following Internet address: www.cdc.gov...Forms, or in the application kit. On or before 
                    <PRTPAGE P="33820"/>
                    July 14, 2000, submit the application to the Grants Management Specialist identified in the “Where to Obtain Additional Information” section of this announcement. 
                </P>
                <P>
                    <E T="03">Deadline:</E>
                     Applications shall be considered as meeting the deadline if they are either: 
                </P>
                <P>(a) Received on or before the deadline date; or</P>
                <P>(b) Sent on or before the deadline date. (Applicants must request a legibly dated U.S. Postal Service postmark or obtain a legibly dated receipt from a commercial carrier or U.S. Postal Service. Private metered postmarks shall not be acceptable as proof of timely mailing.) </P>
                <P>
                    <E T="03">Late Applications:</E>
                     Applications which do not meet the criteria in (a) or (b) above are considered late applications, will not be considered, and will be returned to the applicant. 
                </P>
                <HD SOURCE="HD1">G. Evaluation Criteria (100 points) </HD>
                <P>Each application will be evaluated individually against the following criteria by an independent review group appointed by CDC. </P>
                <P>1. The extent to which the applicant states that they will collect and submit new core and supplemental PedNSS and PNSS data items. (10 points) </P>
                <P>2. The extent to which the applicant describes the procedures planned to develop and test the transaction files, including methods to establish data collection for any new core and supplemental data items not currently collected by the WIC information system. (30 points) </P>
                <P>3. Confirmation of applicant's intention to support future routine file submission. The extent to which the applicant details submission procedures. (20 points) </P>
                <P>4. Time schedule: Confirmation that project activities are sequential and will be completed in a timely fashion. (20 points) </P>
                <P>5. Capability: The extent to which the applicant demonstrates the organizational capacity and ability to develop and conduct proposed program activities, including the architecture and software of the WIC information system and the key project staff having the responsibility and authority to carry out the program activities, as evidenced by job descriptions and resumes.(20 points) </P>
                <P>If applicable, whether the plans for recruitment and outreach for study participants include the process of establishing partnerships with community(ies) and recognition of mutual benefits. </P>
                <P>6. Budget (not scored) </P>
                <P>The extent to which the budget is reasonable and the budget justification is consistent with the program objectives and purpose. </P>
                <P>7. Human Subjects Research (not scored) </P>
                <P>Does the application adequately address the requirements of Title 45 CFR Part 46 for the protection of human subjects? </P>
                <HD SOURCE="HD1">H. Other Requirements </HD>
                <HD SOURCE="HD2">Technical Reporting Requirements </HD>
                <P>Provide CDC with original plus two copies of: </P>
                <P>1. Progress reports (annual);</P>
                <P>2. Financial status report, no more than 90 days after the end of the budget period; and</P>
                <P>3. Final financial and performance reports, no more than 90 days after the end of the project period. </P>
                <P>Send all reports to the Grants Management Specialist identified in the “Where to Obtain Additional Information” section of this announcement. </P>
                <P>The following additional requirements are applicable to this program. For a complete description of each, see Attachment II in the application kit. </P>
                <FP SOURCE="FP-1"> AR-1  Human Subjects Requirements </FP>
                <FP SOURCE="FP-1"> AR-2 Requirements for Inclusion of Women and Racial and Ethnic Minorities in Research </FP>
                <FP SOURCE="FP-1"> AR-7 Executive Order 12372 Review </FP>
                <FP SOURCE="FP-1"> AR-9 Paperwork Reduction Act Requirements </FP>
                <FP SOURCE="FP-1"> AR-10 Smoke-Free Workplace Requirements </FP>
                <FP SOURCE="FP-1"> AR-11 Healthy People 2010 </FP>
                <FP SOURCE="FP-1"> AR-12 Lobbying Restrictions </FP>
                <HD SOURCE="HD1">I. Authority and Catalog of Federal Domestic Assistance Number </HD>
                <P>This program is authorized under sections 301(a) and 317(k)(2) of the Public Health Service Act, [42 U.S.C. section 241(a) and 42 U.S.C. 247b(k)(2),as amended. </P>
                <P>The Catalog of Federal Domestic Assistance number is 93.283. </P>
                <HD SOURCE="HD1">J. Where To Obtain Additional Information </HD>
                <P>This announcement and other CDC program announcements can be found on the CDC home page Internet address—http://www.cdc.gov. Click on “Funding” then “Grants and Cooperative Agreements.” </P>
                <P>To obtain additional information, contact: Cynthia Collins, Grants Management Specialist, Procurement and Grants Office, Grants Management Branch Announcement 00116, Centers for Disease Control and Prevention (CDC), 2920 Brandywine Road, Room 3000, Atlanta, GA 30341-4146, telephone (770) 488-2757, Email address coc9@cdc.gov. </P>
                <P>For program technical assistance, contact: Diane Clark, Deputy Branch Chief, Maternal and Child Nutrition Branch, Division of Nutrition and Physical Activity, National Center for Chronic Disease Prevention and Health Promotion, Centers for Disease Control and Prevention (CDC), 4770 Buford Highway, N.E., Atlanta, Georgia 30341-3717, Telephone (770) 488-5702, Email address: ldc2@cdc.gov.</P>
                <SIG>
                    <DATED>Dated: May 19, 2000. </DATED>
                    <NAME>John L. Williams, </NAME>
                    <TITLE>Director, Procurement and Grants Office, Center for Disease Control and Prevention (CDC). </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13132 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4163-18-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention </SUBAGY>
                <DEPDOC>[Program Announcement 00135] </DEPDOC>
                <SUBJECT>Public Health Laboratory Sciences Training Program for Hispanic and Native American Students Notice of Availability of Funds </SUBJECT>
                <HD SOURCE="HD1">A. Purpose </HD>
                <P>The Centers for Disease Control and Prevention (CDC) announces the availability of fiscal year (FY) 2000 funds for a cooperative agreement program for establishing a Public Health Laboratory Sciences Training Program for Hispanic and Native American Students. CDC is committed to achieving the health promotion and disease prevention objectives of “Healthy People 2010”, a national activity to reduce morbidity and mortality and improve the quality of life. This announcement is related to the focus areas of Environmental Health, Nutrition and Overweight, Tobacco Use, Substance Abuse, Diabetes, Heart Disease and Stroke, Cancer, Maternal, Infant and Child Health, and Education and Community-Based Programs. For the conference copy of “Healthy People 2010”, visit the internet site: http://www.health.gov/healthypeople. </P>
                <P>
                    The purpose of the program is to introduce Hispanic and Native American students to opportunities in public health and laboratory science through education and training, to include students from undergraduate, graduate, and post-doctoral levels. 
                    <PRTPAGE P="33821"/>
                </P>
                <HD SOURCE="HD1">B. Eligible Applicants </HD>
                <P>Applications may be submitted by public and private universities or colleges from the United States and its territories, offering undergraduate and postgraduate academic programs in the physical and/or biomedical sciences, and leading to degrees at the bachelors, masters, and doctorate levels. </P>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>Public Law 104-65 states that an organization described in section 501(c)(4) of the Internal Revenue Code of 1986 that engages in lobbying activities is not eligible to receive Federal funds constituting an award, grant, cooperative agreement, contract, loan, or any other form.</P>
                </NOTE>
                <HD SOURCE="HD1">C. Availability of Funds </HD>
                <P>Approximately $150,000 is available in FY 2000 to fund one award. It is expected that the award will begin on or about September 30, 2000, and will be made for a 12-month budget period within a project period of up to 5 years. Funding estimates may change. </P>
                <P>Continuation awards within an approved project period will be made on the basis of satisfactory progress as evidenced by required reports and the availability of funds. </P>
                <HD SOURCE="HD2">Use of Funds </HD>
                <P>Funds may be used for activities which support the goals and objectives of the fellowship program including travel expenses for program faculty and students for orientation and training, and to attend certain professional meetings for recruitment. Funds may be used for reporting results of fellowship research and the preparation and distribution of material to promote and announce the availability of this fellowship program. Funds may also be used to offset a portion of salaries of the recipient institution's faculty, staff, and graduate teaching assistants who spend time in support of the technical and administrative aspects of this program. Funds may be provided for student stipends, with payment scales determined by the recipient, based on the prior training, education and experience of the Fellow.</P>
                <P>Funds may not be used for the direct support of faculty research projects except for those aspects of such projects which directly benefit the specific training objectives of Fellows. </P>
                <HD SOURCE="HD1">D. Programmatic Interest </HD>
                <P>The mission of the funding agency includes the application of analytical laboratory procedures to measure substances in biological samples from humans. The purpose of these analyses is to assess human exposure to toxic substances, health effects from the exposure, risk factors for diseases, and effectiveness of public health interventions. In achieving this mission, the laboratory techniques and areas of scientific investigation include: </P>
                <P>1. Sample preparation techniques </P>
                <P>2. Liquid or gas chromatography </P>
                <P>3. Radio-immunoassay (RIA), enzyme linked immunoassay (EIA), or other immuno-assay techniques </P>
                <P>4. Polymerase chain reaction (PCR) and other molecular biology techniques </P>
                <P>5. Atomic absorption and atomic emission techniques </P>
                <P>6. Mass spectroscopic techniques </P>
                <P>7. Wet chemistry and UV-Visible and Infared spectroscopic techniques </P>
                <P>8. Analytical method development and evaluation procedures </P>
                <P>9. Routine analytical procedures and quality control </P>
                <P>10. Environmental chemistry, environmental health, and toxicology </P>
                <P>11. Nutritional Biochemistry, Diabetes, Cancer, Smoking and health l2. Introduction to epidemiology from a laboratory perspective </P>
                <P>13. Other laboratory techniques and scientific disciplines as appropriate and necessary </P>
                <HD SOURCE="HD1">E. Program Requirements </HD>
                <P>In conducting activities to achieve the purpose of this program, the recipient will be responsible for the activities under 1. Recipient Activities, and CDC will be responsible for the activities under 2. CDC Activities. </P>
                <HD SOURCE="HD2">1. Recipient Activities</HD>
                <P>a. Establish and manage a comprehensive program to recruit, select, compensate, mentor, and guide Native American and Hispanic students in the sciences for participation in a public health laboratory sciences training program. (The target number of students for this project is up to 6 per year. Typical fellowships at the undergraduate level will be for a maximum of 4 months. At the post-baccalaureate level (including the post-Masters and the post-Doctorate levels) typical fellowships will be for one year, renewable annually for a maximum of three years. Appointments of less than one year may be made under special circumstances). </P>
                <P>b. Provide a senior staff or faculty member to serve as fellowship director, who will be responsible for establishing and/or maintaining close working relationships with students. </P>
                <P>c. Identify students with interest and aptitude in specific scientific disciplines such as: chemistry and all sub-specialties of chemistry (clinical, analytical, and organic, etc.), biochemistry and all related sub-specialties (toxicology, neurotoxicology, biosensors, etc.), molecular biology, genetics, biostatistics, and data acquisition and instrument control systems design. </P>
                <P>d. Develop new, or modify existing, undergraduate and graduate level curricula in relevant academic departments of the recipient institution to complement this fellowship program. </P>
                <P>e. Establish working relationships with community colleges and secondary schools that serve significant populations of Native American and Hispanic students. </P>
                <P>f. Develop curricula that provide training in Environmental Chemistry and Environmental Health. </P>
                <P>g. Provide guidance to the project mentors on the unique cultural or educational needs of potential Fellows since these needs may have an impact on the success and retention of the students in this program. </P>
                <P>h. Provide preliminary training to potential Fellows in chemical and biological laboratory safety, including universal precautions for working with biological samples, use of protective equipment, work-site performance expectations, presentation skills, basic principles of laboratory quality control, and other training which helps build student confidence for encountering the differences between academic settings and the high-throughput laboratory setting they will encounter during the CDC-based portion of their fellowship and in future employment in the sciences. </P>
                <HD SOURCE="HD2">2. CDC Activities</HD>
                <P>a. Provide assistance, if needed, in the development of relevant curricula. </P>
                <P>b. Provide practical and relevant laboratory training, and work experience opportunities at the CDC Environmental Health Laboratory facilities in Atlanta, Georgia. </P>
                <P>c. Provide training oversight, coordination, and guidance for the Fellows and their selected research projects. (Refer to Programmatic Interest section of this announcement.) </P>
                <HD SOURCE="HD1">F. Application Content </HD>
                <P>Use the information in the Program Requirements, Other Requirements, and Evaluation Criteria sections to develop the application content. The applicant should include as part of the narrative or as a two to five page report at the beginning addressing the following information: </P>
                <P>1. Serve local populations of at least 100,000 Native Americans and/or Hispanics. </P>
                <P>
                    2. Annually enroll a total of at least 10,000 graduate and undergraduate students, with total enrollment by 
                    <PRTPAGE P="33822"/>
                    Hispanic, and Native Americans constituting at least 40% of the total undergraduate student body. 
                </P>
                <P>3. Have a demonstrated record of success in recruiting and retaining minority undergraduate science students through completion of their bachelors degree and continuation of post graduate training. (Please provide recent historical data on matriculation, retention, graduation, and post-graduate placement of minority students where available). </P>
                <P>4. Evidence of past successful activities which illustrate creativity and originality in establishing relationships with local community colleges serving Native American and Hispanic populations. </P>
                <P>5. An academic program and supporting faculty recognized in analytical, biomedical, and/or environmental chemistry.</P>
                <P>6. Provide plans for recruitment and outreach for Fellows to include the process of establishing partnerships with community(ies) and recognition of mutual benefits beyond those already demonstrated.</P>
                <P>7. Present estimates of the level of participation in the program in the first year and projections for future years.</P>
                <P>Your application will be evaluated on the criteria listed, so it is important to follow them in laying out your program plan. The narrative should be no more than twenty double-spaced pages printed on one side, with one inch margins, and unreduced font plus pre-printed attachments. The application must be submitted unstapled and unbound.</P>
                <HD SOURCE="HD1">G. Submission and Deadline </HD>
                <P>Submit the original and two copies of PHS-5161-1 (OMB Number 0937-0189). Forms are in the application kit. </P>
                <P>
                    On or before July 21, 2000, submit the application to the Grants Management Specialist identified in 
                    <E T="04">Where to Obtain Additional Information</E>
                     section of this announcement.
                </P>
                <P>Deadline: Applications shall be considered as meeting the deadline if they are either:</P>
                <P>(a) Received on or before the deadline date; or</P>
                <P>(b) Sent on or before the deadline date and received in time for submission to the Objective Review Panel. (Applicants must request a legibly dated U.S. Postal Service postmark or obtain a legibly dated receipt from a commercial carrier or U.S. Postal Service. Private metered postmarks shall not be acceptable as proof of timely mailing.)</P>
                <P>Late Applications: Applications which do not meet the criteria in (a) or (b) above are considered late applications, will not be considered, and will be returned to the applicant.</P>
                <HD SOURCE="HD1">H. Evaluation Criteria </HD>
                <P>Each application will be evaluated individually against the following criteria by an independent review group appointed by CDC.</P>
                <P>1. Understanding of the Objectives of the Project (20 percent)</P>
                <P>The extent to which the applicant demonstrates an understanding of the nature of the problem to be addressed. This specifically includes description of the unique training needs of Native American and Hispanic science students at the undergraduate and graduate levels and cultural barriers which may discourage them from pursuing academic programs in the sciences, and cultural or other factors which may affect the retention of Fellows in the program. Applicant should provide estimates (and sources of estimates) of the demographics of Native American and Hispanic enrollment in scientific higher education in the geographic areas served by the applicant and factors which may affect the validity of such estimates.</P>
                <HD SOURCE="HD2">2. Technical Approach (25 percent) </HD>
                <P>The extent to which the applicant describes in detail the academic institution's component of the proposed Fellowship program including, but not limited to a description of:</P>
                <P>a. An overview of the goals and objectives of the fellowship program.</P>
                <P>b. A comprehensive program to recruit, select, compensate, mentor, and guide Native American and Hispanic students in the sciences for participation in a public health laboratory sciences training program.</P>
                <P>c. Activities to establish close working relationships with students.</P>
                <P>d. The institution's undergraduate and graduate level curricula in relevant academic departments that may be reasonably expected to integrate with the purpose of this fellowship program.</P>
                <HD SOURCE="HD2">3. Ability To Carry Out the Project (25 percent)</HD>
                <P>The extent to which the applicant provides evidence of ability to carry out the proposed project and the extent to which the applicant demonstrates capability to achieve the objectives of the proposed program. This may include plans, time-lines, approaches, methods for conducting such a fellowship program, and may include collaborating with other universities or other health research agencies.</P>
                <HD SOURCE="HD2">4. Personnel (15 percent)</HD>
                <P>The extent to which professional personnel involved in this project are qualified, including evidence of experience similar to this project. </P>
                <HD SOURCE="HD2">5. Collaboration (5 percent) </HD>
                <P>The extent to which the applicant demonstrates the ability to collaborate and/or form partnerships with community colleges and secondary schools serving significant populations of Hispanic and Native American students. </P>
                <HD SOURCE="HD2">6. Plans for Administration (10 percent) </HD>
                <P>The extent to which the applicant describes the plans for administering the project. </P>
                <HD SOURCE="HD2">7. Budget (Not Scored) </HD>
                <P>The extent to which the applicant provides a detailed budget justification which is reasonable and consistent with the objectives of this program. </P>
                <HD SOURCE="HD1">I. Other Requirements </HD>
                <HD SOURCE="HD2">Technical Reporting Requirements </HD>
                <P>Provide CDC with original plus two copies of </P>
                <P>1. semi-annual progress reports, no more than 30 days after the end of the report period. </P>
                <P>2. financial status report, no more than 90 days after the end of the budget period; and </P>
                <P>3. final financial and performance reports, no more than 90 days after the end of the project period. Send all reports to the Grants Management Specialist identified in the “Where to Obtain Additional Information” section of this announcement. </P>
                <P>The following additional requirements are applicable to this program. For a complete description of each, see Attachment I in the application kit.</P>
                <FP SOURCE="FP-1">AR-10 Smoke-Free Workplace Requirements </FP>
                <FP SOURCE="FP-1">AR-11 Healthy People 2010 </FP>
                <FP SOURCE="FP-1">AR-12 Lobbying Restrictions </FP>
                <FP SOURCE="FP-1">AR-16 Security Clearance Requirement</FP>
                <P>Additional information can be attained as follows:</P>
                <FP SOURCE="FP-1">Executive Order 13021—Tribal Colleges—http://www.aipc.osmre.gov/EO13021.htm </FP>
                <FP SOURCE="FP-1">Executive Order 12900—Excellence in Education for Hispanic Americans—http://www.ioc.army.mil/others/minority/ex12900.HTML </FP>
                <HD SOURCE="HD1">J. Authority and Catalog of Federal Domestic Assistance Number </HD>
                <P>
                    This program is authorized under the Public Health Service Act, Section 301(a) and 317 [42 U.S.C. 241(a) and 
                    <PRTPAGE P="33823"/>
                    247(b) as amended]. The Catalog of Federal Domestic Assistance number is 93.283. 
                </P>
                <HD SOURCE="HD1">K. Where To Obtain Additional Information </HD>
                <P>This and other CDC Announcements can be found on the CDC homepage Internet address—http://www.cdc.gov. Click on “Funding” then “Grants and Cooperative Agreements”. To receive additional written information and to request an application kit, call 1-888-Grants4 (1-888-472-6874). You will be asked to leave your name and address and will be instructed to identify the Announcement number of interest. </P>
                <P>If you have questions after reviewing the contents of all the documents, business management technical assistance may be obtained from: Mattie B. Jackson, Grants Management Specialist, Grants Management Branch, Procurement and Grants Office, Centers for Disease Control and Prevention (CDC),Room 3000, 2920 Brandywine Road, Atlanta, GA 30341-4146, Telephone: (770) 488-2718, Email address: mij3@cdc.gov. </P>
                <P>For program technical assistance, contact: Dayton T. Miller, Ph.D., National Center for Environmental Health, Centers for Disease Control and Prevention, 4770 Buford Highway, NE (F-18), Atlanta, Georgia 30341-3724, Telephone: (770) 488-4452, Email address: dtm1@cdc.gov. </P>
                <SIG>
                    <DATED>Dated: May 19, 2000. </DATED>
                    <NAME>John L. Williams, </NAME>
                    <TITLE>Director, Procurement and Grants Office, Centers for Disease Control and Prevention (CDC).</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13131 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4163-18-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Fish and Wildlife Service</SUBAGY>
                <SUBJECT>Notice of Availability of Addendum #3 to the Assessment Plan: Lower Fox River/Green Bay Natural Resource Damage Assessment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of 30-day comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Notice is given that the document entitled: “Third Assessment Plan Addendum: Lower Fox River/Green Bay NRDA” (“The Addendum”) will be available for public review and comment on the date of publication in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                    <P>The U.S. Department of the Interior (“Department”), the U.S. National Oceanic and Atmospheric Administration, the Menominee Indian Tribe of Wisconsin, the Oneida Tribe of Indians of Wisconsin, and the Wisconsin Department of Natural Resources have asserted trusteeship for natural resources considered in this assessment, pursuant to subpart G of the National Oil and Hazardous Substances Pollution Contingency Plan, 40 CFR 300.600, 300.605, and 300.610, and Executive Order 12580, 52 F.R. 2923 (Jan. 23, 1987).</P>
                    <P>The assessment, including the activities addressed in this addendum, will be conducted in accordance with the Natural Resource Damage Assessment Regulations found at 43 CFR part 11, to the extent applicable. The public review of the Addendum announced by this Notice is provided for in 43 CFR 11.32(C).</P>
                    <P>Interested members of the public are invited to review and comment on the Addendum. Copies of the Addendum, and the “Assessment Plan: Lower Fox River/Green Bay NRDA” (“The Plan”) issued on August 23, 1996 (FR Doc. 96-21520), can be requested from the address listed below, or downloaded from the following web site: http://www.fws.gov/r3pao/nrda. All written comments will be considered and included in the Report of Assessment, at the conclusion of the assessment process.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments on the Addendum must be submitted on or before June 26,2000.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Requests for copies of the Addendum and/or the Plan may be made to: David Allen, U.S. Fish and Wildlife Service, 1015 Challenger Court, Green Bay, Wisconsin 54311.</P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The purpose of this natural resource damage assessment is to confirm and quantify the suspected injuries to natural resources in the Lower Fox River, Green Bay, and Lake Michigan environment resulting from exposure to hazardous substances released by area paper mills and other potential sources. It is suspected that this exposure has caused injury to trustee resources. The injury and resultant damages will be assessed under the Comprehensive Environmental Response, Compensation, and Liability Act, as amended, and the Clean Water Act, as amended.</P>
                <P>The objective of this Addendum is to initiate a process through which the governmental partners will attempt to arrive at a single coordinated Restoration and Compensation Determination Plan that integrates the ongoing state and federal/tribal natural resource damage assessments and to notify the public regarding this process.</P>
                <SIG>
                    <NAME>William F. Hartwig,</NAME>
                    <TITLE>Regional Director, Region 3, Fish and Wildlife Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13133  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-55-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Bureau of Land Management </SUBAGY>
                <DEPDOC>[ID-933-1430-ET; IDI-15630 et al.] </DEPDOC>
                <SUBJECT>Legal Description of Modification and Partial Revocation of Executive Orders; Idaho </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice corrects the total acreage figures of Public Land Order 7437 published in 65 FR 58, of March 24, 1000, on page 15917. The Summary of the Public Land Order should read: “This order modifies 5 Executive orders to established a 20-year term as to 8,040.07 acres of lands withdrawn for the Bureau of Land Management for use as Powersite Reserves. This order also partially revokes 3 of the Executive orders insofar as they affect 2,362.82 acres and opens 401.95 acres to surface entry. The remaining 1,960.87 acres have been conveyed out of Federal ownership. All of the lands in Federal ownership have been and will remain open to mining and mineral leasing.” Paragraph 2 lists 277.30 acres, that figure is corrected to 401.95 acres. Paragraph 3 lists 3,165.70 acres , that figure is corrected to 1,960.87 acres. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>May 25, 2000. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jackie Simmons, BLM Idaho State Office, 1387 S. Vinnell Way, Boise, Idaho 83709, 208-373-3867. </P>
                    <SIG>
                        <NAME>Jimmie Buxton, </NAME>
                        <TITLE>Branch Chief, Lands and Minerals. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13163 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-GG-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[MT-960-1150-PG] </DEPDOC>
                <SUBJECT>Dakotas Advisory Council Meeting </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, North Dakota Field Office, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting; Dakotas Advisory Council Meetings. </P>
                </ACT>
                <SUM>
                    <PRTPAGE P="33824"/>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>A meeting of the Dakotas Resource Advisory Council will be held July 10 &amp; 11, 2000, at the Travel Lodge, Dickinson, North Dakota. The session will convene at 8 a.m. on July 10th and resume at 8 a.m. on the 11th. Agenda items will include OHV followup, South Dakota Land Exchange, grazing permit renewal update, Schnell signing, Endangered Species (sage grouse and prairie dogs), Grasslands Stewardship Initiative, Field Trip to Schnell Recreation Area. </P>
                    <P>The meeting is open to the public and a public comment period is set for 8 a.m. on July 11th. The public may make oral statements before the Council or file written statements for the Council to consider. Depending on the number of persons wishing to make an oral statement, a per-person time limit may be established. Summary minutes of the meeting will be available for public inspection and copying. </P>
                    <P>The 15-member Council advises the Secretary of the Interior, through the BLM, on a variety of planning and management issues associated with public land management in the Dakotas. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Douglas Burger, Field Office Manager, North Dakota Field Office, 2933 3rd Ave. W., Dickinson, North Dakota. Telephone (701) 225-9148. </P>
                    <SIG>
                        <DATED>Dated: May 10, 2000. </DATED>
                        <NAME>Douglas J. Burger, </NAME>
                        <TITLE>Field Office Manager. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13122 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-$$-U </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Bureau of Land Management </SUBAGY>
                <DEPDOC>[NV-020-00-0777-XX] </DEPDOC>
                <SUBJECT>Sierra Front/Northwestern Great Basin Resource Advisory Council; Notice of Meeting Location and Time</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting location and time for the Sierra Front/Northwestern Great Basin Resource Advisory Council (Nevada). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Federal Land Policy and Management Act and the Federal Advisory Committee Act of 1972 (FACA), a meeting of the U.S. Department of the Interior, Bureau of Land Management (BLM) Sierra Front/Northwestern Great Basin Resource Advisory Council (Nevada) will be held as indicated below. The topic of discussion will be a review of the Black Rock Management Plan being prepared by the Winnemucca Field Office, and other topics the council may raise.</P>
                    <P>The meetings is open to the public. The public may present written and/or comments to the council. The public comment period for the council meeting will be at 4:00 p.m. on Wednesday, June 14th. Individuals who plan to attend and need special assistance such as sign language interpretation or other reasonable accommodations, or who desire a hard copy of the agenda, should contact Mike Holbert, Winnemucca Field Office, 5100 East Winnemucca Blvd., Winnemucca, NV 89445, telephone (775) 623-1514 no later than June 10, 2000.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The council will meet on Wednesday, June 14, 2000, from 9:00 a.m. to 5:00 p.m. at the Best Western Inn-Fernley, 1405 East Newlands Drive, Fernley, Nevada. Public comment on individual topics will be received at the discretion of the Council Chairperson, as meeting moderator, with a general public comment period on Wednesday, June 14, 2000, at 4:00 p.m.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mike Holbert, Associate Field Manager, Winnemucca Field Office, 5100 East Winnemucca Blvd., Winnemucca, NV 89445. Telephone (775) 623-1514.</P>
                    <SIG>
                        <DATED>Dated: May 12, 2000. </DATED>
                        <NAME>Michael R. Holbert, </NAME>
                        <TITLE>Associate Field Manager, Winnemucca Field Office. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13165 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-HC-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <DEPDOC>[CA-330-1220-AB] </DEPDOC>
                <SUBJECT>King Range National Conservation Area, California </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed establishment of supplementary rules. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Arcata Field Office is proposing the establishment of the following Supplementary Rules for the King Range National Conservation Area as provided for under title 43 Code of Federal Regulations subpart 8365.1-6. The implementation of fees is authorized under the Land and Water Conservation Fund Act of 1965 as Amended, and the Omnibus Consolidated Rescissions Act of 1996 as Amended (Pub. L. 104-134). </P>
                    <HD SOURCE="HD1">A. Camping Closure</HD>
                    <P>BLM administered lands within the following areas are closed to camping (overnight occupancy) outside of developed campsites: Public lands within 500 feet of the perimeter of the Mattole Campground. </P>
                    <HD SOURCE="HD1">B. Overnight Trail Head Parking Fees</HD>
                    <P>
                        An overnight trailhead parking fee will be implemented at the Mattole and Black Sands Beach Recreation Sites to meet the goals described in the supplementary information below. The fee will be set at $2 per night (any future fee changes would be published locally prior to implementation) and will be in effect from 
                        <FR>1/2</FR>
                         hour after sunset to 
                        <FR>1/2</FR>
                         hour before sunrise. There will be no fees for day use. 
                    </P>
                    <HD SOURCE="HD1">C. Overnight Camping Fees</HD>
                    <P>
                        Campground use fees of $5.00 per night are established for the Mattole and Honeydew Creek Campgrounds (any future fee changes would be published locally prior to implementation). Campsite occupancy is limited to two vehicles and 8 persons per site. Fees are in effect from 
                        <FR>1/2</FR>
                         hour after sunset to 
                        <FR>1/2</FR>
                         hour before sunrise at the Mattole Campground, and from 
                        <FR>1/2</FR>
                         hour after sunset until 8:00 a. m. at the Honeydew Creek Campground. 
                    </P>
                    <HD SOURCE="HD1">D. Black Sands Beach, Nighttime Use</HD>
                    <P>
                        This site is closed to all overnight camping. Nighttime occupancy is limited to vehicle parking for off-site backcountry use. For the purposes of this rule, off-site means traveling north of Telegraph Creek for camping/backpacking or other overnight uses. Use of the site itself is limited to 30 minutes for unloading/loading purposes during the nighttime restriction period. The nighttime restriction is in place from 
                        <FR>1/2</FR>
                         hour after sunset to 
                        <FR>1/2</FR>
                         hour before sunrise. This rule does not affect day-time use. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>These Supplementary Rules will be effective on July 1, 2000. </P>
                </EFFDATE>
                <HD SOURCE="HD1">Comment Period</HD>
                <P>The BLM is requesting comments concerning these supplemental rules. The comment period will be open for 30 days from the date of publication of this notice. </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lynda Roush, Bureau of Land Management, Arcata Field Office, 1695 Heindon Rd., Arcata, CA 95521. Phone (707) 825-2300. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The above supplementary rules are being proposed for the following purposes: </P>
                <HD SOURCE="HD1">A. Camping Closure</HD>
                <P>
                    The closure is intended to reduce resource damage and fire danger in the riparian area and beach dunes 
                    <PRTPAGE P="33825"/>
                    surrounding the Mattole Campground. It will also allow for enforcement of the site capacity limits at the Mattole Campground by requiring that visitors hike into the backcountry or travel to other available campgrounds when this site is full. Currently, visitors are impacting undeveloped areas immediately adjacent to the campground so they can camp nearby and use the facilities. 
                </P>
                <HD SOURCE="HD1">B. Overnight Parking Fees</HD>
                <P>The overnight parking fees will be implemented as a management tool for encouraging distribution of overnight use away from the crowded Black Sands Beach and Mattole trailheads, and to discourage large nighttime group gatherings at these trailheads. Neither facility is designed to accommodate large nighttime group events, and this use is not compatible with the goals of the King Range Management Program (1974) and King Range Visitor Services Plan (1992). All parking fees will be used within the King Range to cover maintenance costs of the sites and recreation opportunities that they support. Mattole Campground users will not have to pay the parking fee for vehicles (up to two) parked at their campsite. </P>
                <HD SOURCE="HD1">C. Camping Fees</HD>
                <P>Camping fees are established at Honeydew Creek and Mattole Campgrounds to cover a portion of the maintenance costs; to be commensurate with fees charged at other public and private camping areas in the region; and for use as a management tool to discourage nighttime group gatherings in the campgrounds. These nighttime group events are not compatible with the purpose of the site development and management as an overnight camping facility, nor with the goals of the King Range Management Program (1974) and King Range Visitor Services Plan (1992). </P>
                <HD SOURCE="HD1">D. Black Sands Beach Nighttime Use</HD>
                <P>The Black Sands Beach Recreation Site is designed to be a backcountry trailhead parking area and day use facility. This rule is intended to limit nighttime use of the trailhead facilities to a parking area for backcountry use only. The parking facilities are located immediately adjacent to a residential area, and nighttime use of the area as a destination would cause unreasonable noise within the neighborhood. This restriction would not affect overnight backcountry users who park at the site, and will also not affect day use. </P>
                <P>Violation of any of the above rules is punishable by a fine not to exceed $1000 and/or imprisonment not to exceed 12 months (43 CFR 8360.0-7). </P>
                <SIG>
                    <NAME>Daniel E. Averill,</NAME>
                    <TITLE>Acting Arcata Field Manager. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13134 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-40-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Bureau of Land Management </SUBAGY>
                <DEPDOC>[OR-958-6333-ET; GP0-0220; OR-55753] </DEPDOC>
                <SUBJECT>Proposed Withdrawal and Opportunity for Public Meeting; Oregon </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Forest Service, U.S. Department of Agriculture, proposes to withdraw approximately 960 acres of National Forest System lands, lying within the Siskiyou National Forest, to protect the recreation, fisheries, scenic, and water quality values of the Scenic section of the North Fork Smith Wild and Scenic River. This notice closes the lands for up to 2 years from surface entry and mining. The public lands have been and will remain open to mineral leasing. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>Comments and requests for a public meeting must be received by August 24, 2000. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments and meetings requests should be sent to the Oregon/Washington State Director, BLM, P.O. Box 2965, Portland, Oregon 97208-2965. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Charles R. Roy, BLM Oregon/Washington State Office, 503-952-6189. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On May 19, 2000, the Forest Service filed an application to withdraw the following described National Forest System lands from location and entry under the United States mining laws (30 U.S.C. Ch. 2 (1994)), but not the mineral leasing laws, subject to valid existing rights: </P>
                <HD SOURCE="HD1">Willamette Meridian </HD>
                <HD SOURCE="HD2">Siskiyou National Forest </HD>
                <P>
                    All lands lying on the right (west) bank of the river corridor, including the river bed, and extending 
                    <FR>1/4</FR>
                     mile from the centerline of the North Fork Smith River, from Horse Creek downstream 4.5 miles to the confluence of Baldface Creek, as described in the following: 
                </P>
                <EXTRACT>
                    <FP SOURCE="FP-1">T. 40 S., R. 11 W., unsurveyed</FP>
                    <FP SOURCE="FP1-2">
                        Sec. 15, SW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        ;
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 16, E
                        <FR>1/2</FR>
                        ;
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 21, E
                        <FR>1/2</FR>
                        E
                        <FR>1/2</FR>
                         and NW
                        <FR>1/4</FR>
                        SE
                        <FR>1/4</FR>
                        ; 
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 22, W
                        <FR>1/2</FR>
                        W
                        <FR>1/2</FR>
                         and SE
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        ; 
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 27, W
                        <FR>1/2</FR>
                        E
                        <FR>1/2</FR>
                        , E
                        <FR>1/2</FR>
                        W
                        <FR>1/2</FR>
                         and NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        ;
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 28, NE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        ;
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 34, W
                        <FR>1/2</FR>
                        E
                        <FR>1/2</FR>
                         and E
                        <FR>1/2</FR>
                        W
                        <FR>1/2</FR>
                        . 
                    </FP>
                    <FP SOURCE="FP-1">T. 41 S., R. 11 W.,</FP>
                    <FP SOURCE="FP1-2">
                        Sec. 2, W
                        <FR>1/2</FR>
                        ;
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 3, NE
                        <FR>1/4</FR>
                        ;
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 11, N
                        <FR>1/2</FR>
                        NW
                        <FR>1/4</FR>
                        . 
                    </FP>
                </EXTRACT>
                <P>
                    AND all lands lying on the left (east) bank of the river corridor, including the river bed, and extending 
                    <FR>1/4</FR>
                     mile from the centerline of the North Fork Smith River as described in the following:
                </P>
                <EXTRACT>
                    <FP SOURCE="FP-1">T. 41 S., R. 11 W.,</FP>
                    <FP SOURCE="FP1-2">
                        Sec. 2, those portions of the E
                        <FR>1/2</FR>
                        SW
                        <FR>1/4</FR>
                         and W
                        <FR>1/2</FR>
                        SE
                        <FR>1/4</FR>
                        , lying outside the boundaries of the Kalmiopsis Wilderness Area;
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 11, those portions of the NW
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                         and NE
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        , lying outside the boundaries of the Wild segment of the North Fork Smith Wild and Scenic River. 
                    </FP>
                    <P>The areas described aggregate approximately 960 acres in Curry County.</P>
                </EXTRACT>
                <P>The purpose of the proposed withdrawal is to protect the outstanding recreation, fisheries, scenic, and water quality values for which the North Fork Smith River was designated Wild and Scenic. </P>
                <P>For a period of 90 days from the date of publication of this notice, all persons who wish to submit comments, suggestions, or objections in connection with the proposed withdrawal may present their views in writing to the State Director at the address indicated above. </P>
                <P>
                    Notice is hereby given that an opportunity for a public meeting is afforded in connection with the proposed withdrawal. All interested parties who desire a public meeting for the purpose of being heard on the proposed withdrawal must submit a written request to the State Director at the address indicated above within 90 days from the publication of this notice. Upon determination by the authorized officer that a public meeting will be held, a notice of the time and place will be published in the 
                    <E T="04">Federal Register</E>
                     at least 30 days before the scheduled date of the meeting. 
                </P>
                <P>The application will be processed in accordance with the regulations set forth in 43 CFR 2300. </P>
                <P>
                    For a period of 2 years from the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                    , the lands will be segregated as specified above unless the application is denied or canceled or the withdrawal is approved prior to that date. The temporary land uses which may be permitted during this segregative period include licenses, permits, rights-of-way, and disposal of vegetative resources other than under the mining laws. 
                </P>
                <SIG>
                    <PRTPAGE P="33826"/>
                    <DATED>Dated: May 19, 2000. </DATED>
                    <NAME>Robert D. Deviney, Jr., </NAME>
                    <TITLE>Chief, Branch of Realty and Records Services. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13170 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-33-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Minerals Management Service </SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Minerals Management Service (MMS), Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of extension of a currently approved information collection (OMB Control Number 1010-0091). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>To comply with the requirements of the Paperwork Reduction Act of 1995 (PRA), we are inviting comments on an information collection request (ICR), titled “30 CFR Part 254, Oil-Spill Response Requirements for Facilities Located Seaward of the Coast Line.” We are preparing an ICR, which we will submit to the Office of Management and Budget (OMB) for review and approval. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written comments by July 24, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Mail or hand carry comments to the Department of the Interior; Minerals Management Service; Attention: Rules Processing Team; Mail Stop 4024; 381 Elden Street; Herndon, Virginia 20170-4817. Our practice is to make comments, including names and home addresses of respondents, available for public review during regular business hours. Individual respondents may request that we withhold their home address from the rulemaking record, which we will honor to the extent allowable by law. There may be circumstances in which we would withhold from the record a respondent's identity, as allowable by the law. If you wish us to withhold your name and/or address, you must state this prominently at the beginning of your comment. However, we will not consider anonymous comments. We will make all submissions from organizations or businesses, and from individuals identifying themselves as representatives or officials of organizations or businesses, available for public inspection in their entirety. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Alexis London, Rules Processing Team, telephone (703) 787-1600. You may also contact Alexis London to obtain a copy of the collection of information at no cost. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     30 CFR Part 254, Oil-Spill Response Requirements for Facilities Located Seaward of the Coast Line. 
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1010-0091. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Federal Water Pollution Control Act, as amended by the Oil Pollution Act of 1990 (OPA), requires that a spill-response plan be submitted for offshore facilities prior to February 18, 1993. The OPA specifies that after that date, an offshore facility may not handle, store, or transport oil unless a plan has been submitted. Regulations at 30 CFR part 254 establish requirements for spill-response plans for oil-handling facilities seaward of the coast line, including associated pipelines. 
                </P>
                <P>We use the information collected under 30 CFR part 254 to determine compliance with OPA by owners/operators. Specifically, MMS needs the information to: </P>
                <P>• determine effectiveness of the spill-response capability of owners/operators; </P>
                <P>• review plans prepared under the regulations of a State and submitted to MMS to satisfy the requirements of this rule to ensure that they meet minimum requirements of OPA; </P>
                <P>• verify that personnel involved in oil-spill response are properly trained and familiar with the requirements of the spill response plans and to witness spill-response exercises; </P>
                <P>• assess the sufficiency and availability of contractor equipment and materials;</P>
                <P>• verify that sufficient quantities of equipment are available and in working order;</P>
                <P>• oversee spill-response efforts and maintain official records of pollution events; and</P>
                <P>• assess the efforts of owners/operators to prevent oil spills or prevent substantial threats of such discharges.</P>
                <P>Responses are mandatory. No proprietary, confidential, or sensitive information is collected.</P>
                <P>
                    <E T="03">Frequency:</E>
                     The frequency varies by regulatory requirement, but is mostly annual or on occasion.
                </P>
                <P>
                    <E T="03">Estimated Number and Description of Respondents:</E>
                     Approximately 193 owners or operators of facilities located in both State and Federal waters seaward of the coast line.
                </P>
                <P>
                    <E T="03">Estimated Annual Reporting and Recordkeeping “Hour” Burden:</E>
                     The currently approved burden for this information collection is 47,439 hours. The major components of this burden are for:
                </P>
                <P>• Spill response plans for OCS or State water facilities (100 hours).</P>
                <P>• Revised spill response plans (16.5 hours). </P>
                <P>• Modified OCS spill response plan for facilities in State waters (45 hours). </P>
                <P>• Response plan for facilities in State waters using State requirements (93 hours). </P>
                <P>• Conduct of annual training; retain records for 2 years (40 hours).</P>
                <P>• Conduct of triennial response plan exercise; retain records for 3 years (110 hours). </P>
                <P>
                    <E T="03">Estimated Annual Reporting and Recordkeeping “Non-Hour Cost” Burden:</E>
                     We have identified no non-hour cost burdens for this collection.
                </P>
                <P>
                    <E T="03">Comments:</E>
                     The PRA (44 U.S.C. 3501, 
                    <E T="03">et seq.</E>
                    ) provides that 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. Section 3506(c)(2)(A) of the PRA requires each agency “* * * to provide notice * * * and otherwise consult with members of the public and affected agencies concerning each proposed collection of information * * *” 
                </P>
                <P>Agencies must specifically solicit comments to: (a) evaluate whether the proposed collection of information is necessary for the agency to perform its duties, including whether the information is useful; (b) evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information; (c) enhance the quality, usefulness, and clarity of the information to be collected; and (d) minimize the burden on the respondents, including the use of automated collection techniques or other forms of information technology.</P>
                <P>
                    The PRA also requires agencies to estimate the total annual reporting “non-hour cost” burden to respondents or recordkeepers resulting from the collection of information. We have not identified any non-hour cost burdens and need to know if you have other costs associated with the collection of this information for either total capital and startup cost components or annual operation, maintenance, and purchase of service components. Your estimates should consider the costs to generate, maintain, and disclose or provide the information. You should describe the methods you use to estimate major cost factors, including system and technology acquisition, expected useful life of capital equipment, discount rate(s), and the period over which you incur costs. Capital and startup costs include, among other items, computers and software you purchase to prepare for collecting information; monitoring, sampling, drilling, and testing equipment; and record storage facilities. Generally, your estimates should not include equipment or services purchased: (i) before October 1, 1995; (ii) to comply with requirements not 
                    <PRTPAGE P="33827"/>
                    associated with the information collection; (iii) for reasons other than to provide information or keep records for the Government; or (iv) as part of customary and usual business or private practices.
                </P>
                <P>We will summarize written responses to this notice and address them in our submission for OMB approval. As a result of your comments, we will make any necessary adjustments to the burden in our submission to OMB. In calculating the burden, we assumed that respondents perform certain requirements in the normal course of their activities. We consider these to be usual and customary and took that into account in estimating the burden.</P>
                <SIG>
                    <DATED>Dated: May 17, 2000. </DATED>
                    <NAME>John V. Mirabella, </NAME>
                    <TITLE>Acting Chief, Engineering and Operations Division. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13166 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-MR-W</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>National Park Service </SUBAGY>
                <SUBJECT>Notice of Availability of Draft Director's Order Concerning National Park Service Policies and Procedures Governing Its Structural Fire Management Program </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Park Service (NPS) has prepared a Director's Order setting forth its policies and procedures governing structural fire prevention, protection, and suppression. When adopted, the policies and procedures will apply to all units of the national park system, and will supersede and replace the policies and procedures issued in June 1987. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments will be accepted until June 26, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Draft Director's Order #58 is available on the Internet at http://www.nps.gov/refdesk/DOrders/index.htm. Requests for copies and written comments should be sent to Bill Oswald, NPS Structural Fire Program Manager, Fire Management Program Center, 3833 S. Development Avenue, Boise, Idaho 83705, or to his Internet address: 
                        <E T="03">bill_oswald@nps.gov.</E>
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The NPS is updating its current system of internal written instructions. When these documents contain new policy or procedural requirements that may affect parties outside the NPS, they are first made available for public review and comment before being adopted. The policies and procedures governing structural fire management have previously been published in the form of guideline NPS-58. That guideline will be superseded by the new Director's Order 58 (and a reference manual that will be issued subsequent to the Director's Order). The draft Director's Order covers topics such as fire management planning, safety and health, cultural resources, concessions, reporting, investigation, training, coordination, program review, preparedness, and funding. Director's Order #58 addresses only structural fire management; wildland fire management is addressed in Director's Order #18, approved November 17, 1998 (and is also available on the Internet site listed above). </P>
                <SIG>
                    <DATED>Dated: May 19, 2000. </DATED>
                    <NAME>Loran Fraser, </NAME>
                    <TITLE>Chief, Office of Policy. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13143 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-70-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <DATE>May 18, 2000.</DATE>
                <P>The Department of Labor (DOL) has submitted the following public information collection requests (ICRs) to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act of 1995 (Pub. L. 104-13, 44 U.S.C. Chapter 35). A copy of each individual ICR, with applicable supporting documentation, may be obtained by calling the Department of Labor. To obtain documentation for BLS, ETA, PWBA, and OASAM contact Karin Kurz ({202} 219-5096 ext. 159 or by E-mail to Kurz-Karin@dol.gov). To obtain documentation for ESA, MSHA, OSHA, and VETS contact Darrin King ({202} 219-5096 ext 151 or by E-Mail to King-Darrin@dol.gov).</P>
                <P>Comments should be sent to Office of Information and Regulatory Affairs, Attn: OMB Desk Officer for BLS, DM, ESA, ETA, MSHA, OSHA, PWBA, or VETS, Office of Management and Budget, Room 10235, Washington, DC 20503 ({202} 395-7316), on or before June 26, 2000.</P>
                <P>The OMB is particularly interested in comments which: </P>
                <P>• evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>• evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>• enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    • minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Agency:</E>
                     Employment and Training Administration.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Weekly Claims and Extended Benefits Data and Weekly Initial and Continued Claims Report.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1205-0028.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     State, Local, or Tribal Government.
                </P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s100,10,xls75,10,xls75,xls75">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Form </CHED>
                        <CHED H="1">Total respondents </CHED>
                        <CHED H="1">Frequency </CHED>
                        <CHED H="1">Total responses </CHED>
                        <CHED H="1">Average time per response </CHED>
                        <CHED H="1">Estimated total burden </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">ETA 538 </ENT>
                        <ENT>53 </ENT>
                        <ENT>Weekly </ENT>
                        <ENT>2,756 </ENT>
                        <ENT>30 min  </ENT>
                        <ENT>1,378 hours. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ETA 539 </ENT>
                        <ENT>53 </ENT>
                        <ENT>Weekly </ENT>
                        <ENT>2,756 </ENT>
                        <ENT>50 min </ENT>
                        <ENT>2,297 hours. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Totals </ENT>
                        <ENT>53 </ENT>
                        <ENT O="xl">  </ENT>
                        <ENT>5,512 </ENT>
                        <ENT>40 min </ENT>
                        <ENT>3,675 hours. </ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="33828"/>
                <P>
                    <E T="03">Total annualized capital/startup costs:</E>
                     $0.
                </P>
                <P>
                    <E T="03">Total annual costs (operating/maintaining systems or purchasing services):</E>
                     $0.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Data for the determination of the beginning, continuance, or termination of an Extended Benefit (EB) period in any State by reason of the EB trigger rate and the data on initial and continued claims used as economic indicators.
                </P>
                <SIG>
                    <NAME>Ira L. Mills,</NAME>
                    <TITLE>Departmental Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13155 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-30-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR </AGENCY>
                <SUBJECT>Office of the Secretary Submission for OMB Review; Comment Request </SUBJECT>
                <DATE>May 15, 2000.</DATE>
                <P>The Department of Labor (DOL) has submitted the following public information collection requests (ICRs) to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act of 1995 (Pub. L. 104-13, 44 U.S.C. Chapter 35). A copy of each individual ICR, with applicable supporting documentation, may be obtained by calling the Department of Labor. The obtain documentation for BLS, ETA, PWBA, and OASAM contact Karin Kurz ((202) 219-5096 ext. 159 or by E-mail to Kurz-Karin@dol.gov). To obtain documentation for ESA, MSHA, OSHA, and VETS contact Darrin King ((201) 219-5096 ext. 151 or by E-Mail to King-Darrin@dol.gov). </P>
                <P>Comments should be sent to Office of Information and Regulatory Affairs, Affairs, Attn: OMB Desk Officer for BLS, DM, ESA, ETA, MSHA, OSHA, PWBA, or VETS, Office of Management and Budget, Room 10235, Washington, DC 20503 ((202) 395-7316), on or before June 26, 2000. </P>
                <P>The OMB is particularly interested in comments which: </P>
                <P>• Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; </P>
                <P>• Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; </P>
                <P>• Enhance the quality, utility, and clarity of the information to be collected; and </P>
                <P>
                    • Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses. 
                </P>
                <P>
                    <E T="03">Agency:</E>
                     Employment Standards Administration (ESA). 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Wage Statement. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1215-0148. 
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occassion. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Farms, business or other for-profit, Individuals or households. 
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     1.4 million. 
                </P>
                <P>
                    <E T="03">Number of Annual Responses: </E>
                    34 million. 
                </P>
                <P>
                    <E T="03">Estimated Time Per Response: </E>
                    1 minute. 
                </P>
                <P>
                    <E T="03">Total Burden Hours: </E>
                    566,667. 
                </P>
                <P>
                    <E T="03">Total Annualized capital/startup costs:</E>
                     $0. 
                </P>
                <P>
                    <E T="03">Total annual costs (operating/maintaining systems or purchasing services):</E>
                     $0. 
                </P>
                <P>
                    <E T="03">Description: </E>
                    The Migrant and Seasonal Agricultural Protection Act require employers of agricultural workers to maintain records of certain payroll information given to each worker. 
                </P>
                <SIG>
                    <NAME>Ira L. Mills, </NAME>
                    <TITLE>Departmental Clearance Officer. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13156 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-27-M </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR </AGENCY>
                <SUBAGY>Employment and Training Administration </SUBAGY>
                <SUBJECT>Workforce Investment Act (WIA)(Section 167) National Farmworker Jobs Program (NFJP) </SUBJECT>
                <SUBJECT>Allocations </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Employment and Training Administration (ETA), Labor. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice: Announcement of Formula Allocations for the Program Year (PY) 2000 NFJP. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to Section 182(d) of the WIA, the ETA is publishing the PY 2000 allocations for the NFJP authorized under Section 167 of the WIA. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. Alicia Fernandez-Mott, Chief, Division of Seasonal Farmworker Programs. Her e-mail address is &lt;afernandez-mott@doleta.gov&gt;. Her telephone number is (202) 219-5500, ext. 121. (This is not a toll-free number.) </P>
                </FURINF>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>May 25, 2000. Comments must be submitted on or before June 26, 2000. </P>
                </EFFDATE>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On May 19, 1999, a Notice of the new formula for allocating funds available for the NFJP (formerly referred to as the Migrant and Seasonal Farmworker (MSFW) program) was published in the 
                    <E T="04">Federal Register</E>
                     at 64 FR 27390 (May 19, 1999). The Notice explains how the new formula achieves its purpose, which is to distribute funds geographically by State service area on the basis of each area's relative share of farmworkers who are eligible for enrollment in the NFJP. The new formula consists of a rational organization of multiple data sets selected to yield the relative share distribution of eligible farmworkers. The result is substantially more relevant to the purpose than the allotments determined by the prior formula. Because it is the best available allocation tool and to maintain consistency, the Department of Labor is using the new formula described in the May 19 Notice to allocate PY 2000 WIA section 167 funds. The rationale for the new allocation formula and underlying methodology on how the new formula realigns the NFJP allocations, is fully explained in the May 19 Notice. The Department of Labor invites comments on our decision to use this formula for allocating PY 2000 funds. 
                </P>
                <P>Implementing the new formula in PY 1999 gave rise to significant changes in relative funding levels. The magnitude of the realignment for some State service areas is substantial. This is attributable to the inherent weaknesses of the data sources used under the prior formula and also to the fact the sources had gradually become substantially date-stale. To provide for a smooth transition from the original distributions, to the distributions provided by the new formula, Part IV of the May 19, 1999 Notice provides a strategy for implementation of the new formula through four incremental “hold harmless” stages. The stages adjust the formula allocations by limiting the rate of reduction in relative funding levels to the four annual increments of 95 percent, 90 percent, 85 percent and 80 percent of the 1998 level—the last year under the old formula. Full implementation of the new (combined-data) formula is reached on the 5th year allocation. The May 19, 1999 Notice provides that for PY 2000, which is the second stage hold-harmless year, each State service area will receive no less than 90 percent of its PY 1998 allocation (64 FR 27390, 27399 § IV(2)). PY 2000 is the operating year that begins on July 1, 2000. </P>
                <P>
                    The Fiscal Year 2000 pre-recission appropriation for the MSFW programs 
                    <PRTPAGE P="33829"/>
                    under WIA Section 167 is $74,445,000. A portion of this amount is an addition to the Administration's budget request. This budget addition amount is designated in the Committee appropriation language for addressing two objectives. One objective applies to the state-by-state formula allocation of funds for the NFJP. The budget addition offsets the scheduled adjustment to those State service areas undergoing a reduction in funding, by financing the difference between their PY 1998 level and the PY 2000 hold-harmless adjusted level. The other is to provide additional funding to raise the discretionary support for the farmworker housing assistance grants from the 1998 level to a level of $3,000,000. The total budget addition amount is $ 3,428,000. The recission action on the appropriation for the WIA Section 167 is $250,000. All of the $250,000 recission amount is applied to reduce the budget addition. The final budget addition, after reduction for the recission amount, is $3,178,000. 
                </P>
                <P>In PY 2000, the base amount allocated under the formula is equal to the PY 1999 formula allocation amount of $67,596,408. The budget addition amount is applied to those state service areas that are allocated a declining relative share of funding under the second hold-harmless stage of the new formula. Had there been no recission action, the total cost of this offset would be $2,927,691. Application of the 7.293 percent budget recission, reduces the budget addition by $213,517 to the post-recission level of $2,714,174. The total amount allocated to the States for the NFJP is the base amount, plus the budget addition amount, less the applied recission amount, leaving a net total of $70,310,582. The effects of these steps for each State service area are shown in the last three columns of the “Allocation Table.” </P>
                <P>Under 20 CFR 669.240(a), at least 94 percent of the funds appropriated must be allocated to the State service areas for the NFJP grants. The total amount ($70,310,582) allocated for PY 2000 is 94.446 percent, thus exceeding the minimum requirement. The remaining amount of the appropriation is available for the other WIA Section 167 activities for farmworkers, which include the post recission amount of $2,963,543 for the PY 2000 farmworker housing assistance grants. </P>
                <HD SOURCE="HD1">Minimum Funding Provisions </HD>
                <P>
                    Part V of the 
                    <E T="04">Federal Register</E>
                     Notice (See 64 FR 27390, 27400 § V (May 19, 1999) provides that a State service area allocated less than $60,000 could be combined with an adjoining State service area. For PY 2000, the Rhode Island area allocation of $2,875 will be combined with the Connecticut area allocation. The incumbent grantee will not be required to amend its PY 2000 operating plan due to this action. 
                </P>
                <HD SOURCE="HD1">PY 2000 Allocations </HD>
                <P>The final (far right-hand) column of the “Allocation Table” provides the allotments for the NFJP in PY 2000. Grantees will use these figures in preparing the PY 2000 NFJP grant plans. </P>
                <SIG>
                    <DATED>Signed at Washington, DC, this 18th day of May, 2000. </DATED>
                    <NAME>Shirley M. Smith, </NAME>
                    <TITLE>Administrator,, Office of Adult Services. </TITLE>
                </SIG>
                <GPOTABLE COLS="8" OPTS="L2,i1" CDEF="s100,12,12,9,12,10,9,12">
                    <TTITLE>
                        <E T="04">Allocation Table for Program Year 2000 National Farmworker Jobs Program</E>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">State </CHED>
                        <CHED H="1">PY 1998 allotments </CHED>
                        <CHED H="1">Formula allocation w/o hold harmless adjustment </CHED>
                        <CHED H="1">
                            Formula percentage share w/o hold harmless 
                            <LI>(in percent) </LI>
                        </CHED>
                        <CHED H="1">PY 2000 allocation with hold harmless adjustment </CHED>
                        <CHED H="1">Cost to bring states to PY 1998 levels </CHED>
                        <CHED H="1">Recission action (7.293) </CHED>
                        <CHED H="1">PY 2000 allotments </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01"/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Alabama </ENT>
                        <ENT>$791,835 </ENT>
                        <ENT>$437,632 </ENT>
                        <ENT>0.67766 </ENT>
                        <ENT>$712,652 </ENT>
                        <ENT>$79,183 </ENT>
                        <ENT>$5,775 </ENT>
                        <ENT>$786,060 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arizona </ENT>
                        <ENT>1,519,645 </ENT>
                        <ENT>1,719,287 </ENT>
                        <ENT>2.66226 </ENT>
                        <ENT>1,646,953 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>1,646,953 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arkansas </ENT>
                        <ENT>1,167,409 </ENT>
                        <ENT>724,893 </ENT>
                        <ENT>1.12247 </ENT>
                        <ENT>1,050,668 </ENT>
                        <ENT>116,741 </ENT>
                        <ENT>8,514 </ENT>
                        <ENT>1,158,895 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">California </ENT>
                        <ENT>14,591,138 </ENT>
                        <ENT>20,067,526 </ENT>
                        <ENT>31.07392 </ENT>
                        <ENT>16,077,073 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>16,077,073 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Colorado </ENT>
                        <ENT>805,523 </ENT>
                        <ENT>992,449 </ENT>
                        <ENT>1.53678 </ENT>
                        <ENT>879,010 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>879,010 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Connecticut </ENT>
                        <ENT>206,024 </ENT>
                        <ENT>303,689 </ENT>
                        <ENT>0.47025 </ENT>
                        <ENT>228,511 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>228,511 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Delaware </ENT>
                        <ENT>118,334 </ENT>
                        <ENT>125,899 </ENT>
                        <ENT>0.19495 </ENT>
                        <ENT>125,899 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>125,899 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Florida </ENT>
                        <ENT>4,631,415 </ENT>
                        <ENT>2,465,700 </ENT>
                        <ENT>3.81806 </ENT>
                        <ENT>4,168,274 </ENT>
                        <ENT>463,141 </ENT>
                        <ENT>33,777 </ENT>
                        <ENT>4,597,638 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Georgia </ENT>
                        <ENT>1,711,615 </ENT>
                        <ENT>876,499 </ENT>
                        <ENT>1.35723 </ENT>
                        <ENT>1,540,454 </ENT>
                        <ENT>171,161 </ENT>
                        <ENT>12,483 </ENT>
                        <ENT>1,699,132 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Idaho </ENT>
                        <ENT>877,438 </ENT>
                        <ENT>1,079,184 </ENT>
                        <ENT>1.67108 </ENT>
                        <ENT>957,349 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>957,349 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Illinois </ENT>
                        <ENT>1,425,808 </ENT>
                        <ENT>1,424,912 </ENT>
                        <ENT>2.20643 </ENT>
                        <ENT>1,424,912 </ENT>
                        <ENT>896 </ENT>
                        <ENT>65 </ENT>
                        <ENT>1,425,743 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Indiana </ENT>
                        <ENT>781,615 </ENT>
                        <ENT>927,202 </ENT>
                        <ENT>1.43574 </ENT>
                        <ENT>850,271 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>850,271 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Iowa </ENT>
                        <ENT>1,314,394 </ENT>
                        <ENT>1,078,955 </ENT>
                        <ENT>1.67073 </ENT>
                        <ENT>1,182,955 </ENT>
                        <ENT>131,439 </ENT>
                        <ENT>9,586 </ENT>
                        <ENT>1,304,808 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kansas </ENT>
                        <ENT>697,839 </ENT>
                        <ENT>1,078,783 </ENT>
                        <ENT>1.67046 </ENT>
                        <ENT>777,719 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>777,719 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kentucky </ENT>
                        <ENT>1,352,613 </ENT>
                        <ENT>1,043,179 </ENT>
                        <ENT>1.61533 </ENT>
                        <ENT>1,217,352 </ENT>
                        <ENT>135,261 </ENT>
                        <ENT>9,865 </ENT>
                        <ENT>1,342,748 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Louisiana </ENT>
                        <ENT>796,032 </ENT>
                        <ENT>484,907 </ENT>
                        <ENT>0.75086 </ENT>
                        <ENT>716,429 </ENT>
                        <ENT>79,603 </ENT>
                        <ENT>5,805 </ENT>
                        <ENT>790,227 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Maine </ENT>
                        <ENT>327,397 </ENT>
                        <ENT>174,702 </ENT>
                        <ENT>0.27052 </ENT>
                        <ENT>294,657 </ENT>
                        <ENT>32,740 </ENT>
                        <ENT>2,388 </ENT>
                        <ENT>325,009 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Maryland </ENT>
                        <ENT>306,291 </ENT>
                        <ENT>363,789 </ENT>
                        <ENT>0.56332 </ENT>
                        <ENT>333,229 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>333,229 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Massachusetts </ENT>
                        <ENT>351,027 </ENT>
                        <ENT>298,012 </ENT>
                        <ENT>0.46146 </ENT>
                        <ENT>315,924 </ENT>
                        <ENT>35,103 </ENT>
                        <ENT>2,560 </ENT>
                        <ENT>348,467 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Michigan </ENT>
                        <ENT>878,641 </ENT>
                        <ENT>944,430 </ENT>
                        <ENT>1.46242 </ENT>
                        <ENT>944,430 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>944,430 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Minnesota </ENT>
                        <ENT>1,274,775 </ENT>
                        <ENT>879,095 </ENT>
                        <ENT>1.36125 </ENT>
                        <ENT>1,147,298 </ENT>
                        <ENT>127,477 </ENT>
                        <ENT>9,297 </ENT>
                        <ENT>1,265,478 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mississippi </ENT>
                        <ENT>1,449,044 </ENT>
                        <ENT>571,321 </ENT>
                        <ENT>0.88467 </ENT>
                        <ENT>1,304,140 </ENT>
                        <ENT>144,904 </ENT>
                        <ENT>10,568 </ENT>
                        <ENT>1,438,476 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Missouri </ENT>
                        <ENT>1,094,524 </ENT>
                        <ENT>976,379 </ENT>
                        <ENT>1.51189 </ENT>
                        <ENT>985,072 </ENT>
                        <ENT>109,452 </ENT>
                        <ENT>7,982 </ENT>
                        <ENT>1,086,542 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Montana </ENT>
                        <ENT>667,189 </ENT>
                        <ENT>461,861 </ENT>
                        <ENT>0.71518 </ENT>
                        <ENT>600,470 </ENT>
                        <ENT>66,719 </ENT>
                        <ENT>4,866 </ENT>
                        <ENT>662,323 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Nebraska </ENT>
                        <ENT>774,884 </ENT>
                        <ENT>1,092,397 </ENT>
                        <ENT>1.69154 </ENT>
                        <ENT>855,772 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>855,772 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Nevada </ENT>
                        <ENT>200,795 </ENT>
                        <ENT>159,091 </ENT>
                        <ENT>0.24635 </ENT>
                        <ENT>180,716 </ENT>
                        <ENT>20,079 </ENT>
                        <ENT>1,464 </ENT>
                        <ENT>199,331 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New Hampshire </ENT>
                        <ENT>112,600 </ENT>
                        <ENT>100,958 </ENT>
                        <ENT>0.15633 </ENT>
                        <ENT>101,340 </ENT>
                        <ENT>11,260 </ENT>
                        <ENT>821 </ENT>
                        <ENT>111,779 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New Jersey </ENT>
                        <ENT>400,038 </ENT>
                        <ENT>698,545 </ENT>
                        <ENT>1.08168 </ENT>
                        <ENT>451,763 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>451,763 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New Mexico </ENT>
                        <ENT>598,720 </ENT>
                        <ENT>934,978 </ENT>
                        <ENT>1.44778 </ENT>
                        <ENT>667,952 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>667,952 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New York </ENT>
                        <ENT>1,850,667 </ENT>
                        <ENT>1,088,774 </ENT>
                        <ENT>1.68593 </ENT>
                        <ENT>1,665,600 </ENT>
                        <ENT>185,067 </ENT>
                        <ENT>13,497 </ENT>
                        <ENT>1,837,170 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">North Carolina </ENT>
                        <ENT>3,006,003 </ENT>
                        <ENT>1,897,104 </ENT>
                        <ENT>2.93760 </ENT>
                        <ENT>2,705,403 </ENT>
                        <ENT>300,600 </ENT>
                        <ENT>21,923 </ENT>
                        <ENT>2,984,080 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">North Dakota </ENT>
                        <ENT>468,362 </ENT>
                        <ENT>609,496 </ENT>
                        <ENT>0.94379 </ENT>
                        <ENT>513,493 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>513,493 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ohio </ENT>
                        <ENT>904,951 </ENT>
                        <ENT>1,264,492 </ENT>
                        <ENT>1.95803 </ENT>
                        <ENT>998,582 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>998,582 </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="33830"/>
                        <ENT I="01">Oklahoma </ENT>
                        <ENT>608,145 </ENT>
                        <ENT>1,276,891 </ENT>
                        <ENT>1.97723 </ENT>
                        <ENT>702,695 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>702,695 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oregon </ENT>
                        <ENT>1,087,697 </ENT>
                        <ENT>1,452,311 </ENT>
                        <ENT>2.24886 </ENT>
                        <ENT>1,195,236 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>1,195,236 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pennsylvania </ENT>
                        <ENT>1,221,441 </ENT>
                        <ENT>1,549,985 </ENT>
                        <ENT>2.40010 </ENT>
                        <ENT>1,336,212 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>1,336,212 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Rhode Island </ENT>
                        <ENT>0 </ENT>
                        <ENT>38,832 </ENT>
                        <ENT>0.06013 </ENT>
                        <ENT>2,875 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>2,875 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">South Carolina </ENT>
                        <ENT>1,080,106 </ENT>
                        <ENT>391,046 </ENT>
                        <ENT>0.60552 </ENT>
                        <ENT>972,095 </ENT>
                        <ENT>108,011 </ENT>
                        <ENT>7,877 </ENT>
                        <ENT>1,072,229 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">South Dakota </ENT>
                        <ENT>692,869 </ENT>
                        <ENT>456,831 </ENT>
                        <ENT>0.70739 </ENT>
                        <ENT>623,582 </ENT>
                        <ENT>69,287 </ENT>
                        <ENT>5,053 </ENT>
                        <ENT>687,816 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tennessee </ENT>
                        <ENT>957,799 </ENT>
                        <ENT>720,217 </ENT>
                        <ENT>1.11523 </ENT>
                        <ENT>862,019 </ENT>
                        <ENT>95,780 </ENT>
                        <ENT>6,985 </ENT>
                        <ENT>950,814 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Texas </ENT>
                        <ENT>5,979,800 </ENT>
                        <ENT>6,697,752 </ENT>
                        <ENT>10.37126 </ENT>
                        <ENT>6,475,747 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>6,475,747 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Utah </ENT>
                        <ENT>245,354 </ENT>
                        <ENT>288,106 </ENT>
                        <ENT>0.44612 </ENT>
                        <ENT>266,687 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>266,687 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Vermont </ENT>
                        <ENT>213,134 </ENT>
                        <ENT>105,217 </ENT>
                        <ENT>0.16293 </ENT>
                        <ENT>191,821 </ENT>
                        <ENT>21,313 </ENT>
                        <ENT>1,554 </ENT>
                        <ENT>211,580 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Virginia </ENT>
                        <ENT>1,036,441 </ENT>
                        <ENT>708,789 </ENT>
                        <ENT>1.09754 </ENT>
                        <ENT>932,797 </ENT>
                        <ENT>103,644 </ENT>
                        <ENT>7,559 </ENT>
                        <ENT>1,028,882 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Washington </ENT>
                        <ENT>1,705,576 </ENT>
                        <ENT>2,262,216 </ENT>
                        <ENT>3.50297 </ENT>
                        <ENT>1,873,085 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>1,873,085 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">West Virginia </ENT>
                        <ENT>219,325 </ENT>
                        <ENT>100,275 </ENT>
                        <ENT>0.15527 </ENT>
                        <ENT>197,393 </ENT>
                        <ENT>21,932 </ENT>
                        <ENT>1,600 </ENT>
                        <ENT>217,725 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wisconsin </ENT>
                        <ENT>1,229,201 </ENT>
                        <ENT>953,157 </ENT>
                        <ENT>1.47593 </ENT>
                        <ENT>1,106,281 </ENT>
                        <ENT>122,920 </ENT>
                        <ENT>8,965 </ENT>
                        <ENT>1,220,236 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wyoming </ENT>
                        <ENT>201,911 </ENT>
                        <ENT>232,207 </ENT>
                        <ENT>0.35956 </ENT>
                        <ENT>219,105 </ENT>
                        <ENT>  </ENT>
                        <ENT>0 </ENT>
                        <ENT>219,105 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total Center United States </ENT>
                        <ENT>63,933,384 </ENT>
                        <ENT>64,579,952 </ENT>
                        <ENT>100.00 </ENT>
                        <ENT>64,579,952 </ENT>
                        <ENT>2,753,713 </ENT>
                        <ENT>200,828 </ENT>
                        <ENT>67,132,836 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Conterminous United States </ENT>
                        <ENT>63,933,384 </ENT>
                        <ENT>64,579,952</ENT>
                        <ENT>95.53755 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hawaii </ENT>
                        <ENT>251,607 </ENT>
                        <ENT>204,254 </ENT>
                        <ENT>4.16028 </ENT>
                        <ENT>204,254 </ENT>
                        <ENT>47,353 </ENT>
                        <ENT>3,453 </ENT>
                        <ENT>248,154 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Puerto Rico </ENT>
                        <ENT>2,938,827 </ENT>
                        <ENT>2,812,202 </ENT>
                        <ENT>.30217 </ENT>
                        <ENT>2,812,202 </ENT>
                        <ENT>126,625 </ENT>
                        <ENT>9,235 </ENT>
                        <ENT>2,929,592 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Subtot. (HI+PR) </ENT>
                        <ENT>3,190,434 </ENT>
                        <ENT>3,016,456 </ENT>
                        <ENT>4.46 </ENT>
                        <ENT>3,016,456 </ENT>
                        <ENT>173,978 </ENT>
                        <ENT>12,688 </ENT>
                        <ENT>3,177,746 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total United States </ENT>
                        <ENT>67,123,818 </ENT>
                        <ENT>67,596,408 </ENT>
                        <ENT>100.00 </ENT>
                        <ENT>67,596,408 </ENT>
                        <ENT>2,927,691 </ENT>
                        <ENT>213,517 </ENT>
                        <ENT>70,310,582 </ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13154 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4510-30-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR </AGENCY>
                <SUBAGY>Employment and Training Administration </SUBAGY>
                <SUBJECT>Work Incentive Grants </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Employment and Training Administration (ETA), DOL. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability of funds; Solicitation for Grant Applications (SGA). </P>
                </ACT>
                <HD SOURCE="HD2">This notice contains all of the necessary information and forms needed to apply for grant funding. </HD>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of Labor (DOL), Employment and Training Administration (ETA) announces the availability of $20 million to award competitive grants designed to enhance the employability, employment and career advancement of people with disabilities through enhanced service delivery in the new One-Stop delivery system established under the Workforce Investment Act of 1998. The Work Incentive Grant program will provide grant funds to consortia and/or partnerships of public and private non-profit entities working in coordination with a state and/or local One-Stop delivery system to augment the existing programs and services and ensure programmatic access and streamlined, seamless service delivery for people with disabilities. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applications will be accepted commencing on the date of publication. The closing date for receipt of applications under this announcement is Tuesday, August 1, 2000, at 4:00 p.m. Eastern Standard Time (EST) at the address below. Telefacsimile (fax), telegraphed, or electronic applications will not be honored. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Applications shall be mailed to the U.S. Department of Labor, Employment and Training Administration, Division of Federal Assistance, Attention: Ms. B. Jai Johnson, SGA/DFA 00-107, 200 Constitution Avenue, NW Room S-4203, Washington, DC 20210. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Questions should be faxed to Ms. B.Jai Johnson, Grants Management Specialist, Division of Federal Assistance, Fax (202) 219-8739. This is not a toll-free number. All inquiries should include the SGA number (DFA 00-107) and a contact name, fax and phone numbers. This solicitation is also being published on the Internet on the ETA's disability On-line Home Page at wdsc.org/disability, or the ETA homepage at doleta.gov. Award notifications will also be published on the ETA homepage. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Authority </HD>
                <P>
                    Provisions relating to the One-Stop delivery system are at Section 121, 134(c) of the Workforce Investment Act (29 USC 2841, 2864); Wagner-Peyser Act 53(c)(1) (29 USC 496(c)(1)) and Department of Labor Appropriations Act 2000 (Pub. L. 106-113). Regulations governing the Workforce Investment Act are at 20 CFR parts 660-671. An Interim Final Rule was published in the 
                    <E T="04">Federal Register</E>
                     at 64 FR 18662 (Apr. 19,1999) with issuance of final rule planned for the summer of 2000. 
                </P>
                <HD SOURCE="HD1">II. Background </HD>
                <P>The Workforce Investment Act of 1998 establishes comprehensive reform of existing Federal job training programs with amendments impacting service delivery under the Wagner Peyser Act, Adult Education and Literacy Act, the Rehabilitation Act and supersedes the Job Training Partnership Act. A number of other Federal programs are also identified as required partners under the One-Stop delivery system with the intention of providing comprehensive services for all Americans to access the information and resources available to them in the development and implementation of their career goals. The intention of the One-Stop system is to establish programs and providers in co-located, coordinated and integrated settings that are coherent and accessible for individuals and businesses alike in approximately 600 workforce investment areas which will be established throughout the nation. </P>
                <P>
                    The Workforce Investment Act establishes State and Local Workforce 
                    <PRTPAGE P="33831"/>
                    Investment Boards focused on strategic planning, policy development, and oversight of the workforce system with significant authority for the Governor and chief elected officials to build on existing reforms in order to implement innovative and comprehensive workforce investment systems. Although systemic change of the magnitude envisioned by the Workforce Investment Act is a long term process, State and local planning processes are required to be in place by July 1, 2000. The Work Incentive Grants will facilitate model service delivery for people with disabilities involving coordination of the multiple programs and agencies which frequently impact their ability to achieve self-sustaining employment, skill attainment and long range career opportunities. Recognizing that many One-Stop delivery systems may not currently have the capacity to provide comprehensive services to people with disabilities, the Work Incentive Grant is designed to provide seed monies for the enhancement of service delivery in the One-Stop delivery system. 
                </P>
                <P>Many people with disabilities are looking to the new workforce investment system to address their employment and training needs in a progressive, enlightened environment with cutting-edge technologies. They also expect the One-Stop delivery system to provide comprehensive services to meet multiple barriers which frequently limit their access to a productive, economically rewarding work life. These may include, but are not limited to, the availability of basic and skill development; vocational skill training or advanced educational opportunities; apprenticeship and entrepreneurial training; transportation assistance to reach training or employment; housing assistance or advise on retaining existing housing upon employment; and access to medical health coverage upon employment. </P>
                <HD SOURCE="HD2">Additional Background Information </HD>
                <P>There are approximately 50 million Americans with disabilities, 30 million of whom are of working age. Of the latter, many are relegated to lives of poverty and reliance on public assistance and supports. The economic boom of recent years has had little to no impact on the more than 70% of those with significant disabilities of working age who are not employed. In addition, many people have hidden disabilities which may or may not be recognized or officially diagnosed but which impact their ability to obtain, retain or advance in employment. </P>
                <P>Approximately 10 million people with disabilities are recipients or beneficiaries of Supplemental Security Income (SSI) or Social Security Disability Insurance (SSDI). Many other individuals with disabilities receive public assistance under the Temporary Assistance for Needy Families (TANF) program. The benefits or payments to these individuals are generally at or below Federal poverty income levels. </P>
                <P>Generally eligibility for Medicaid, access to subsidized housing and other benefits are automatically tied to receipt of SSI or TANF, while Medicare and some other public supports are closely linked to SSDI benefits. Public policy systems, particularly those related to necessary health coverage, have for many years encouraged dependency on income supports and created many obstacles to employment and economic independence. </P>
                <P>The loss of health care benefits and other structural disincentives to working and achieving self-sufficient, living wages have been partially addressed in the Ticket to Work and Work Incentives Improvement Act of 1999 (TWWIIA) [Public Law 106-170] which, among other provisions, encourages States to enact expanded and more readily accessible health care coverage for working age individuals with disabilities. Although not authorized under the TWWIIA, the Department of Labor intends for the Work Incentive Grant program to further support the employment objectives of TWWIIA for SSI and SSDI recipients by enhancing the State and local workforce investment system for all people with disabilities. </P>
                <P>The Department of Labor has worked with the Social Security Administration (SSA) and the Department of Health and Human Services (HHS) in designing the Work Incentive Grant program, in a coordinated and strategic effort to support the issuance and objectives of separate SSA's cooperative agreement and HHS's grant programs authorized under the TWWIIA. The SSA will be awarding $50,000 to $300,000 grants for a $23 million Planning, Assistance and Outreach program to establish the capacity to provide comprehensive information on work incentives to SSI and SSDI recipients throughout each State. Workforce Investment Boards and One-Stop systems, among other entities, are eligible applicants for the SSA Planning, Assistance and Outreach Cooperative Agreement program. The HHS Medicaid Infrastructure Grant program is authorized for five years with approximately $40 million to be awarded annually to State Medicaid Agencies for establishing Medicaid buy-in opportunities for individuals who are working. Each of the three grant programs is administered separately by its respective agency but are expected to be implemented in Fiscal Year 2000. </P>
                <P>The Department of Education also provided input for the requirements of this Solicitation for Grant Application. The Presidential Task Force on Employment of Adults with Disabilities, established under Executive Order 13078, facilitated and provided guidance to this multi-agency process as part of their charge to design a coordinated and aggressive national policy that will bring working-age individuals with disabilities into gainful employment at a rate approaching that of the general population. </P>
                <HD SOURCE="HD1">III. Submission of Applications </HD>
                <P>
                    <E T="03">Late Applications.</E>
                     Any application received after the exact date and time specified for receipt at the office designated in this notice will not be considered, unless it is received before awards are made and it—(a) was sent by U.S. Postal Service registered or certified mail not later than the fifth calendar day before the date specified for receipt of applications (
                    <E T="03">e.g.,</E>
                     an application submitted in response to a solicitation requiring receipt of applications by the 20th of the month must have been mailed/post marked by the 15th of that month); or (b) was sent by the U.S. Postal Service Express Mail Next Day Service to addressee not later than 5 p.m. the place of mailing two working days prior to the date specified for receipt of applications. The term “working days” excludes weekends and Federal holidays. “Post marked” means a printed, stamped or otherwise placed impression (exclusive of a postage meter machine impression) that is readily identifiable, without further action, as having been supplied or affixed on the date of mailing by an employee of the U.S. Postal Service. 
                </P>
                <P>
                    <E T="03">Withdrawal of Applications.</E>
                     Applications may be withdrawn by written notice or telegram (including mail gram) received at any time before an award is made. Applications may be withdrawn in person by the applicant or by an authorized representative thereof, if the representative's identity is made known and the representative signs a receipt of the proposal. 
                </P>
                <P>
                    <E T="03">Hand Delivered Proposals.</E>
                     It is preferred that applications be mailed at least five days prior to the closing date. To be considered for funding, hand-delivered applications must be received by 4 p.m., EST, August 1, 2000, at the specified address. Failure to adhere to the above instructions will be basis for a determination of nonresponsiveness. 
                    <PRTPAGE P="33832"/>
                    Overnight express mail from carriers other than the U.S. Postal Service will be considered hand-delivered applications and must be received by the above specified date and time. 
                </P>
                <HD SOURCE="HD1">IV. Funding Availability and Period of Performance </HD>
                <P>The Department of Labor anticipates awarding 20-40 grants ranging from $500,000 to $1.5 million. The period of performance will be approximately 30 months from the date of execution by the Department. The grant funds would be available for expenditure until June 30, 2003 when the authority for these funds will expire. The Department may make subsequent grant awards, which would extend grant objectives, to the original grantees based on satisfactory performance and the availability of funds. </P>
                <HD SOURCE="HD1">V. Eligible Applicants </HD>
                <P>Eligible applicants may be a State and/or Local Workforce Investment Board(s) (State Board/Local Board(s)) established under the Workforce Investment Act or other State/local public entities including, Vocational Rehabilitation, Mental Health, Mental Retardation/Developmental Disability, TANF; and/or a private non-profit organization including, but not limited to Centers for Independent Living (CILs), disability advocacy and provider organizations, federally-funded disability grant entities, and other non-profit organizations which provide services and/or advocacy for people with disabilities; or a consortium thereof. </P>
                <P>To the extent practicable and possible, the Department of Labor is encouraging consortia of entities to develop and submit applications under this grant program. If the applicant is not the State or Local Workforce Investment Board, the Board(s) must be a partner in the consortium. </P>
                <P>Applications can be statewide in scope. Statewide projects must propose strategies for enhancing and improving services to people with disabilities involving all local workforce investment areas in the State. State-wide grant projects should obtain and provide letters of commitment from local Workforce Investment Boards to the extent possible. However, a statewide project must include the State Workforce Investment Board as a consortium partner, with applicable letters of commitment provided in the application. </P>
                <P>Indian and Native American Tribal entities, or consortia of Tribes, may apply for Work Incentive Grants. These would involve coordination of services and enhancements to a One-Stop system approach for people with disabilities in a specific Indian community or covering multiple Tribal entities which may cut across multiple States and/or workforce investment areas. In such cases, letters of commitment from Local Boards may not be applicable. Grants to Indian and Native American tribal grantees are treated differently because of sovereignty and self-governance established under the Indian Self-Determination and Education Assistance Act allowing for the government to government relationship between the Federal and Tribal Governments. </P>
                <HD SOURCE="HD1">VI. Section Format Requirements for Grant Application </HD>
                <HD SOURCE="HD2">General Requirements </HD>
                <P>Applicants must submit four (4) copies of their proposal, with original signatures. The Application Narrative must be double-spaced, and on single-sided, numbered pages with the exception of format requirements for the Executive Summary. The Executive Summary must be limited to no more than two single-spaced, single sided pages. A font size of at least twelve (12) pitch is required throughout. </P>
                <P>There are three required sections of the application. Requirements for each section are provided in this application package. Applications that fail to meet the requirements will not be considered.</P>
                <EXTRACT>
                    <FP SOURCE="FP-1">Section I—Project Financial Plan;</FP>
                    <FP SOURCE="FP-1">Section II—Executive Summary—Project Synopsis</FP>
                    <FP SOURCE="FP-1">Section III—Project Narrative (including Appendices, not to exceed 40 pages) </FP>
                </EXTRACT>
                <HD SOURCE="HD2">Section I. Project Financial Plan</HD>
                <P>Section I of the application must include the following two required elements: (1) Standard Form (SF) 424, Application for Federal Assistance, and (2) Budget Information Form and budget narrative. All copies of the SF 424 MUST have original signatures of the legal entity applying for grant funding. Applicants shall indicate on the SF 424 the organization's IRS Status, if applicable. According to the Lobbying Disclosure Act of 1995, Section 18, an organization described in Section 501(c)4 of the Internal Revenue Code of 1986 which engages in lobbying activities shall not be eligible for the receipt of federal funds constituting an award, grant, or loan. The Catalog of Federal Domestic Assistance (CFDA) number is 17.207. Section I will not count against the application page limits. </P>
                <P>The financial plan must describe all costs associated with implementing the project that are to be covered with grant funds. All costs should be necessary and reasonable according to the Federal guidelines set forth in the “Uniform Administrative Requirements for Grants and Cooperative Agreements to State and Local Governments,” (also known as the “Common Rule”) codified at 29 CFR part 97 (97.22), and “Grants and Agreements with Institutes of Higher Education, Hospitals, and Other Non-Profit Organizations” (also known as OMB Circular A-110), codified at 29 CFR part 95 (95.27). </P>
                <P>The financial plan must contain the following parts:</P>
                <EXTRACT>
                    <FP SOURCE="FP-1">—Completed “SF 424—Application for Federal Assistance” (see Appendix A for required form.) </FP>
                    <FP SOURCE="FP-1">—Completed “Budget Information Form” by line item for all costs required to implement the project design effectively. (See Appendix B for these required forms.) </FP>
                    <FP SOURCE="FP-1">—Budget narrative/justification which provides sufficient information to support the reasonableness of the costs included in the budget in relation to the service strategy and planned outcomes.</FP>
                </EXTRACT>
                <P>
                    <E T="04">Please note:</E>
                     Work Incentive Grant project designs which incorporate development, procurement or implementation of information technologies involving linkage, and/or to assure accessible technologies in the One-Stop setting, must provide a 50 percent grantee match for those Work Incentive Grant funds which will be utilized for this (these) purposes. That is, if an applicant intends to use $50,000 in grant funds to develop, procure or implement information technology they must identify $50,000 to be provided by the applicant and/or consortium partner(s). Also, grant funds directed to development, procurement and implementation of these technologies cannot exceed 10% (not including matching funds) of the total grant award. Identification of these funds should be made noted in the remarks section of the Budget Information Sheet and described in the budget narrative/justification, including source of matching funds.
                </P>
                <HD SOURCE="HD2">Section II. Executive Summary—Project Synopsis</HD>
                <FP>[Format requirements limited to no more than two single-spaced, single-sided pages] </FP>
                <P>Each application shall provide a project synopsis which identifies the following: </P>
                <P>• The applicant; </P>
                <P>• The type of organization the applicant represents; </P>
                <P>• Identification of consortium partners and the type of organizations they represent; </P>
                <P>
                    • The project service area; 
                    <PRTPAGE P="33833"/>
                </P>
                <P>• Whether the service area is an entire local workforce investment area, more than one local area, and/or all local areas in a State; </P>
                <P>• The specific areas of focus in the announcement which are addressed by the project; </P>
                <P>• The amount of funds requested; </P>
                <P>• The planned period of performance; </P>
                <P>• The comprehensive strategy proposed for providing seamless service delivery, for addressing the multi-faceted barriers to training and employment which affect people with disabilities, and for improving access for people with disabilities in the generic workforce system; </P>
                <P>• The ways in which the proposal is coordinated with a State HHS grant and/or SSA benefits planner grant; </P>
                <P>• How counseling and other support needs will be addressed in the One-Stop Center system; </P>
                <P>• The actions already taken by the State or Local Workforce Investment Board to address the needs of people with disabilities in the One-Stop delivery system; </P>
                <P>• The extent to which the One-Stop facilities and satellite site incorporate physical access for people with disabilities; </P>
                <P>• The extent to which Vocational Rehabilitation is integrated or coordinated with the One-Stop delivery system; </P>
                <P>• Data on the extent to which people with disabilities have been served under the prior Job Training Partnership Act program and under the Wagner-Peyser Act; </P>
                <P>• The level of commitment the applicant and consortium members have to serving people with disabilities; and </P>
                <P>• The extent to which the needs of individuals with disabilities from diverse cultural and/or ethnic groups will be addressed. </P>
                <HD SOURCE="HD2">Section III. Project Narrative</HD>
                <FP>[Format requirements limited to no more than forty (40) double-spaced, single-sided, numbered pages] </FP>
                <P>Section III of the application, the project narrative, must not exceed forty (40) pages for the Government Requirements/Statement of Work section, as described below in the “Required Content for Work Incentive Grant Applications—Program Year 2000.” The forty (40) page limit includes any Attachments which are provided by the applicant. Letters of general support or recommendation for a proposal should NOT be submitted and will count against the page limits. However, letters of commitment are required from partner/consortia organizations, including State and/or Local Workforce Investment Board(s) clearly stating their intent to provide services and resources to the grant. </P>
                <HD SOURCE="HD1">VII. Program Scope and Objectives </HD>
                <P>The Department of Labor, in consultation with the President's Task Force on Employment of Adults with Disabilities, has designed the Work Incentive Grant program to achieve the following objectives: </P>
                <P>—Provide seamless service delivery within a One-Stop delivery system for people with a wide range of disabilities which may include both documented and undocumented physical, sensory, developmental/cognitive (e.g., mental retardation and learning disabilities, among others), mental and other health related functional disabilities. </P>
                <P>—Maintain a referral source of diverse services and information that commonly impact the employability of people with disabilities, such as transportation, housing, education and training programs, access to technology, and health care coverage; </P>
                <P>—Provide model One-Stop service delivery through availability of—</P>
                <P>• comprehensive services and programs designed to meet multiple needs and common employment barriers such as a procedures for identifying those individuals with hidden disabilities through appropriate screening and diagnostic testing; </P>
                <P>• state-of-the-art, fully accessible technologies and/or other accommodations that would be available for use in the One-Stop setting as well as establishing a process for the availability of accommodations in training settings; and </P>
                <P>• knowledgeable, experienced and skilled staff support on a broad range of disability issues. </P>
                <P>—Ensure access to knowledgeable benefits counselors who can do the following </P>
                <P>• provide information on education and training program options and opportunities available under a broad array of programs such as Adult Education; Individuals with Disability Education Act for those under 22 without a high school degree; Vocational Education and School-to-Work programs; </P>
                <P>• address the impact of employment on individual benefits such as SSDI, SSI, TANF, Medicaid, Medicare, subsidized housing, and food stamps; </P>
                <P>• provide accurate information on the availability of Social Security work incentive programs and Ticket-to-Work options available to SSDI and SSI recipients; </P>
                <P>• make available to employers detailed information on the array of tax benefits and incentives to employers of people with disabilities that provide financial support for workplace modifications and accommodations; and</P>
                <P>• leverage the diverse range of program resources that may be critical to successful employment, retention and career advancement such as medical or psychological testing or transportation subsidies available to One-Stop customers in local areas, as applicable. </P>
                <P>—Establish and carry out extensive and wide-ranging outreach to the disability community, including those with physical, sensory, developmental/cognitive (mental retardation and learning disabilities, among others), mental and other health related impairments, so that core and Title I workforce services are readily available and welcoming to customers with disabilities;</P>
                <P>—Ensure linkages and technical assistance to public and private providers of services to people with disabilities such as centers for independent living; State Developmental Disability Councils; State and local mental health agencies; Federal Social Security Agencies, State Medicaid Agencies, Mental Retardation/Developmental Disabilities Offices, TANF agencies; public special education and adult education programs, private schools and training programs designed to meet the needs of persons with disabilities, and other non-profit organizations which support integration into the One-Stop delivery system and which have knowledge regarding the benefits of employment and training information and services available through the workforce system. </P>
                <P>—Develop One-Stop capacity as a valued provider of choice for beneficiaries of SSDI and SSI, and to facilitate One-Stop eligibility to be an Employment Network provider established under provisions of the TWWIIA, which assumes responsibility for coordination and delivery of services under the Ticket to Work program, meets professional and educational qualifications, where applicable, and provides appropriate employment services, vocational rehabilitation services, or other support services either directly or by entering into agreement with a qualified entity. </P>
                <P>
                    • Leverage available funds and services, including TANF and public education resources, currently available to individuals with disabilities under a variety of public and private non-profit resources to achieve the individual objectives of these customers; and
                    <PRTPAGE P="33834"/>
                </P>
                <P>• Provides individual customer choice as a primary, key component of program availability and delivery which provide models for how Individual Training Accounts (ITAs) under Title I of WIA, SSA Ticket-to-Work vouchers, Vocational Rehabilitation resources, and other appropriate funding sources can be used to provide seamless service delivery that is responsive to the customer. </P>
                <P>—Implement information technologies which may be used to facilitate linkage or consolidation of information or services provided by existing State, local and other Federal program providers; and/or establish innovative accessible technologies in the workforce system to assure universal access to One-Stop information and resources for individuals with disabilities. Please note: Work Incentive Grant project designs which incorporate development, procurement or implementation of information technologies involving linkage, and/or to assure accessible technologies in the One-Stop setting, must provide a 50 percent grantee match for those Work Incentive Grant funds which will be utilized for this (these) purposes. Also, grant funds directed to development, procurement and implementation of these technologies cannot exceed 10% (not including matching funds) of the total grant award. </P>
                <P>To the extent appropriate and practicable, the applicant Work Incentive Grant proposals should be developed in coordination with SSA's Benefits Planning, Assistance, and Outreach Cooperative Agreement program and/or HHS's Medicaid Infrastructure Grant program as part of a multi-pronged approach to increase the employment rate of people with disabilities. For example, an applicant for the Work Incentive Grant might consider applying for the SSA Benefit Planning, Assistance and Outreach Cooperative Agreement program, or coordinate with entities who may be applying, with the intent of establishing benefits planning capacity in a One-Stop Center. However, there may be additional strategies to support the Medicaid infrastructure development. </P>
                <P>Likewise, the Department is encouraging coordination with formula and competitive Welfare-to-Work grant programs. Coordination should also occur with State/Local five year plans required under Title I of WIA. </P>
                <P>The SSA Benefits Planning, Assistance, and Outreach Cooperative Agreement Request for Proposal and HHS Medicaid Infrastructure Grant Request for Application requirements are accessible through ETA's disAbility Online homepage: http://wdsc.org/disability. Additional information and resources are also available at this website. </P>
                <HD SOURCE="HD1">VIII. Monitoring and Reporting </HD>
                <HD SOURCE="HD2">Monitoring </HD>
                <P>The Department shall be responsible for ensuring the effective implementation of each competitive grant project in accordance with the provisions of this announcement and the negotiated grant agreement. Applicants should assume that on-site project reviews will be conducted by Department staff, or their designees periodically throughout the implementation of the grant. Reviews will focus on the timely project implementation, performance in meeting the grant's programmatic goals and objectives, expenditure of grant funds on allowable activities, integration and coordination with other resources and service providers in the local area, and project management and administration in achieving project objectives. Work Incentive Grants may be subject to other additional reviews at the discretion of the Department. </P>
                <HD SOURCE="HD2">Reporting </HD>
                <P>Grantees will be required to submit periodic financial and participant reports under the Work Incentive Grant program covering the workforce area(s) included in the grant project design. Customer survey information will also be required. Specific reporting requirements have not been established at the time of issuance of this Solicitation for Grant Application. However, data collection will probably incorporate some detailed information about the people with disabilities being served under the grant, by the grant applicant and consortium partners where applicable. To the extent possible, reporting will be conducted electronically through web-based applications. </P>
                <P>1. Financial reports will be required on a quarterly basis. This will be the Standard Form 269—Financial Status Report (FSR). </P>
                <P>2. Customer Satisfaction Surveys: Customer satisfaction surveys will be required to be conducted with people with disabilities applying for services through the One-Stop delivery system(s) participating in the grant award. The Department of Labor will issue guidelines and reporting instructions related to the Customer Satisfaction Survey process at a later date. </P>
                <P>3. Other Reporting: The Department of Labor may require additional reporting requirements, including implementation progress reports and quarterly narrative and/or data reports on participants served in the workforce area(s) included in the grant for grant management and knowledge development purposes. The Department of Labor will issue guidelines and reporting instructions related to progress, narrative and participant reporting at a later date. </P>
                <HD SOURCE="HD1">IX. Government Requirements/Statement of Work—Project Narrative </HD>
                <P>The Project Narrative, or Section III, of the grant application should provide complete information on how the applicant will address government requirements and statement of work provisions outlined here, and not to exceed forty (40) double-spaced numbered pages, including appendices. The application should include information of the type described below, as appropriate. </P>
                <HD SOURCE="HD2">Description of Service Area and Consortium Configuration </HD>
                <P>Information provided in this section will be evaluated predominately under the “Statement of Need” criteria. </P>
                <P>—Identify the number of workforce areas in the State and the jurisdiction of each local workforce investment area(s) in the State. </P>
                <P>—Identify what local areas(s) in the State will be covered by the project and whether the project is Statewide, multiple local areas or a single local area. </P>
                <P>
                    —Identify consortium members if any, their primary mission irrespective of participation in the grant proposal, and what political and geographic jurisdictions (
                    <E T="03">e.g.,</E>
                     cities, counties, subsections of cities/counties) they cover. 
                </P>
                <P>—Identify the percent of people with disabilities in the State and/or local area, including the percentage of people who are beneficiaries of SSDI and/or SSI.</P>
                <P>—Identify the most recent unemployment rate(s) in the workforce investment area(s) covering the project. </P>
                <P>—Describe the significant deficiencies in the State or local workforce investment system that represent barriers to employment for people with disabilities. </P>
                <P>—Identify additional State and/or local funds and resources that will be used to support the overall objectives of the grant and which will assist in addressing the identified issues the grant project is addressing. </P>
                <P>
                    —For proposals targeted to a specific Indian community or covering multiple Tribal entities which may cut across multiple States and/or local areas, describe the overall approach of the 
                    <PRTPAGE P="33835"/>
                    project, identify the inadequacies and deficiencies of the service delivery to the applicable community, and how the project expects to address these. 
                </P>
                <HD SOURCE="HD2">Disability Related Knowledge and Skills </HD>
                <P>The Department will evaluate information provided in this section predominately under the “Comprehensive Action Plan/Statement of Need” criteria. </P>
                <P>—Describe how the project will address a primary objective of the Work Incentive Grant program to assure the integration of people with disabilities into the workforce investment system, including the availability of WIA Title I programs and services, as well as the many partner programs operating through the One-Stop delivery system. </P>
                <P>—Recognizing that the One-Stop delivery system may not have extensive knowledge or skills in working with people with disabilities, describe the level of expertise of the One-Stop system in the local area(s) addressed in the grant and the projects plans for addressing inadequacies. </P>
                <P>—Describe the overall status and actions taken to-date by the One-Stop delivery system to address services to people with disabilities. This should include actions to assure State and/or local facilities are physically and programmatically accessible, training provided to staff, the number and percent of people with disabilities receiving services under JTPA and Employment Service programs during the previous three years compared with that of people without disabilities, and plans to increase services to people with disabilities, if applicable. </P>
                <P>—Identify the provisions of the Memorandum of Understanding or other agreements between Title I of the WIA, State Vocational Rehabilitation (VR) Agency, the State Rehabilitation Council, and the State and/or local Workforce Investment Board in terms of the provision of services to people with disabilities; the plans for cost sharing; the arrangements for referral of people with disabilities between Title I of the WIA and VR as appropriate; the extent of integration and co-location of VR in One-Stop Centers, including sharing of MIS systems or participation in case management data base technologies; the extent to which there is joint funding of participant services or leveraging of funds to expand access to services; and utilization of Individual Training Accounts (ITA's) for people with disabilities. </P>
                <P>—Identify plans and strategies to develop the capacity of the comprehensive One-Stop Center to function as an Employment Network under the TWWIIA. Project plans in this regard should involve building the capacity of the WIA Title I program and One-Stop system so that more in-depth services and information will be readily available to individuals with disabilities. Additionally, the description of increased capacity should be as an adjunct to the State Vocational Rehabilitation Agency which is an automatic Employment Network provider under the TWWIIA. Descriptions may include the planned coordination, interaction and relationship between the universal One-Stop service delivery system and Vocational Rehabilitation services, planned memorandums of understanding on how the Ticket program may be implemented within the One-Stop system or in partnership with non-profit entities in the local area, and expectations for more services directed to SSI and SSDI recipients. </P>
                <P>—Identify whether assessment tools are utilized to identify individuals with learning disabilities in the One-Stop delivery system, including (1) whether assessment tools are utilized to identify individuals with learning disabilities in the One-Stop; (2) plans and processes to identify applicable assessment tools, train staff and incorporate such assessments as part of the service delivery structure; and (3) use of individualized, person-driven processes for identification of strengths, needs and desires related to employment. </P>
                <HD SOURCE="HD2">Summary of Strategy of Collaboration/Coordination </HD>
                <P>Information provided in this section will be evaluated predominately under the “Comprehensive Service Strategy” and “Collaboration and Coordination” criteria. This should include the identification and interaction of a variety of disability-related organizations and entities. These may include but should not be limited to the following: Independent Living Centers, State Mental Health, Mental Retardation/Developmental Disability Agencies, State Planning Councils on Developmental Disabilities, State Independent Living Councils (SILCs), State Rehabilitation Councils, State Governors' Committee, State Medicaid Agency, State and/or local TANF agency, Vocational Rehabilitation Agency and local Welfare-to-Work Programs. </P>
                <P>—Identify specific organizational/service provider capabilities that will be provided as a result of grant activities to ensure the full range of assistance required for receiving and participating in training, skill development, job development, job placement in unsubsidized employment, job retention services and career advancement opportunities for individuals with disabilities. </P>
                <P>—Describe the process that will be used to maintain and expand the service structure for individuals with disabilities accessing the workforce investment system after receipt of the grant funds. Describe what linkages are expected to occur that will be sustained over time and what resources various public and private entities will make available in the workforce system that ensure expanded services and integration of people with disabilities. </P>
                <P>—Describe the extent to which people with physical and mental disabilities are represented in the development and implementation of plans to improve and enhance One-Stop services for people with disabilities, plans for outreach and marketing to the disability community and organizations which represent or work with people with disabilities; and plans for training disability-related organizations on the resources and programs available to them in the One-Stop system. </P>
                <P>—Describe coordination and linkage with regional Disability Business and Technical Assistance Centers (DBTACs) and State Governor's Committees on Employment of People with Disabilities. Have DBTACs provided training to the One-Stop delivery system on the Americans with Disabilities Act (ADA), section 504 of the Rehabilitation Act, or other disability-related training? If not, are plans to do so incorporated into the applicant project? </P>
                <P>—Describe coordination and linkage with the State and local Independent Living Center (CIL) system. Are they part of the consortium membership? If not, what outreach is planned to establish linkage with them and their core constituency of people with disabilities? </P>
                <P>—Describe coordination and linkage with Mental Health Departments, Mental Retardation/Developmental Disability Agencies, State Councils on Developmental Disabilities, State Vocational Rehabilitation, and Councils on Employment, and other local provider or advocate organizations serving individuals with developmental and/or psychiatric disabilities. Are they part of the consortium membership? If not, what outreach is planned to establish linkage with them and their core constituency of people with disabilities? </P>
                <P>
                    —Describe coordination and linkage with Learning Disabilities and Training Dissemination hub centers established under grants from the Department of Education's Office of Vocational and 
                    <PRTPAGE P="33836"/>
                    Adult Education. Have these centers provided training to the One-Stop delivery system or are plans to do so incorporated into the applicant project? 
                </P>
                <P>
                    —Identify how State TANF programs and Welfare to Work (WtW) competitive grant projects will be linked or leveraged with objectives of the applicant's project. States and local areas have been in the process of implementing numerous WtW projects under formula and discretionary grants. Additionally, many TANF agencies have refocused resources on skill attainment and employment outcomes for TANF recipients. In addition to the fact that many TANF recipients have functional disabilities, many WtW and TANF projects address significant structural barriers to employment which are similar in nature to those facing most individuals with disabilities (
                    <E T="03">e.g.,</E>
                     health, housing, transportation). Systems which address these barriers for WtW and TANF recipients can be expanded or leveraged to address similar barriers for people with disabilities. 
                </P>
                <P>—Describe how the planned project will be coordinated with grant programs which are funded under the SSA Benefits Planning, Assistance and Outreach Cooperative Agreement and HHS Medicaid Infrastructure Grant programs, if applicable. </P>
                <HD SOURCE="HD2">Analysis of Barriers to Employment Impacting People With Disabilities in State/Local Workforce Investment Area </HD>
                <P>The Department will evaluate information provided in this section under “Statement of Need” and “Coordination and Collaboration” criteria. </P>
                <P>—Identify public and private non-profit provider entities participating in the grant program and what barriers to employment may be addressed by the programs and services that are contributing to the overall applicant proposal. Specifically, describe how the State or local area is addressing (1) health insurance benefits, including relevant Medicaid and/or Medicare provisions, required by many people with disabilities to enter and retain employment; (2) the current transportation infrastructure, the availability of public transportation, and how individuals with all types of disabilities will access training and employment; (3) housing, food stamps and other support services; and (4) assistive technology needs. </P>
                <P>—Describe how public supports needed by people with disabilities may be affected by their employment or training and State or local conditions and actions to sustain benefits and services following successful job placement. For example, does the State or local area have provisions to continue supported or Section 8A housing, where applicable, for individuals who enter unsubsidized employment? Has the State adopted Medicaid “buy-in” options, or are there Medicaid waivers which extend health care coverage for individuals who enter employment? </P>
                <P>—If the applicant's proposal does not incorporate the capacity for benefits counselors or planners, what coordination is planned that ensures that individuals with disabilities who access One-Stop Center services will be able to obtain accurate work incentive and benefits information from knowledgeable and skilled staff? </P>
                <HD SOURCE="HD2">Innovative Strategies and Model One-Stop Service Designs </HD>
                <P>The Department will evaluate information provided in this section predominately under the “Innovations and Model Services” criteria. </P>
                <P>—Describe how the project will provide innovative approaches to increasing competitive, unsubsidized employment to individuals with disabilities. </P>
                <P>
                    —Provide information on how the project adds value to the workforce system from a national perspective (
                    <E T="03">e.g.</E>
                    , fills a gap in policy or service approach), and the potential for replication and dissemination to the workforce system at large. 
                </P>
                <P>
                    —Describe investment plans, strategy and rationale for implementation of innovative technologies, whether to establish linkages with disability related entities or to implement innovative accessible technologies (
                    <E T="03">e.g.</E>
                    , video interpreting services for clients who are deaf), including the source(s) of the 50 percent match requirement discussed in Section VI under Project Financial Plan. 
                </P>
                <P>—Identify the scope of technology implementations, if applicable, and the extent to which implementation is comprehensive and across the workforce area(s) and/or statewide. </P>
                <P>—Identify individualized strategies that establish client control of training funds, VR funds, ITAs, or other funding sources to which these individuals may have access, and co-mingle funds in a seamless, customer friendly manner, including plans for obtaining waiver authority to the extent program requirements necessitate this. </P>
                <P>—Identify plans or strategies to deploy Ticket-to-Work voucher provisions for beneficiaries of SSDI and recipients of SSI. At the time of this Solicitation for Grant Application, the requirements for implementation of the Ticket will not have been drafted, nor will the number of pilot States participating in a pilot process known. Therefore, the Department recognizes that descriptions for implementing the Ticket may be limited. </P>
                <P>—Describe strategies to foster entrepreneurial and self-employment options utilizing ITAs, Plans for Achieving Self-Support (PASS) and other SSA work incentives, and Medicaid coverage for individuals with disabilities who start or return to work. </P>
                <P>—Describe strategies to transition youth with disabilities from school-to-work environments using existing systems such as School-to-Work and One-Stop system infrastructures. </P>
                <P>—Identify plans for ensuring competitive, unsubsidized employment for individuals with the most significant disabilities, including how the provision of job development, job carving, job coaching, supported employment, and personal assistance services will be addressed when applicable, and plans to integrate individuals with the most significant disabilities into mainstream workforce settings through individualized job development and placement strategies. </P>
                <P>—Provide information on how techniques such as job carving and individualized job development may be utilized under Title I of the WIA, or plans to expand this capability. </P>
                <HD SOURCE="HD2">Employer Related Linkages </HD>
                <P>The Department will evaluate this section predominately under the “Innovations and Model Services” criteria. </P>
                <P>—Describe specific approaches for developing relationships with and support of area employers which establish employment opportunities for individuals with disabilities accessing the One-Stop delivery system, including any commitments by employers to hire these individuals. </P>
                <P>—Describe opportunities for competitive employment for individuals with disabilities will be provided or developed within the local workforce investment area and how this is unique or different than what is normally performed by the applicant(s). </P>
                <P>—Identify available Federal and State tax incentives available to employers when hiring an individual with a disability; how this information will be marketed and disseminated to employers, the individual and workforce staff; and how employers may use such tax credits to address structural and technological accommodation needs. </P>
                <P>
                    —Describe opportunities for increasing integrated, competitive employment through use of strategies 
                    <PRTPAGE P="33837"/>
                    such as individualized job development for individuals with the most significant disabilities currently working in segregated facilities or waiting for employment services. 
                </P>
                <HD SOURCE="HD2">Implementation and Project Management Plan </HD>
                <P>The Department will evaluate this section predominately under the “Demonstrated Capability” criteria. Applicants must be able to document that they have systems capable of satisfying the administrative and grant management requirements for Work Incentive Grants. </P>
                <P>—Identify the critical activities, time frames and responsibilities for effectively implementing the project, including the management and evaluation process for assuring successful implementation of grant objectives. </P>
                <P>—Include a project organizational chart which identifies the staff with key management responsibilities, including a matrix of organizational responsibilities of key entities and participating consortium organizations, where applicable. </P>
                <P>—Describe the specific experience of the applicant(s) in serving people with disabilities, in providing workforce services, in addressing specific barriers to employment, in achieving expected outcomes in the delivery of such services/programs, and in implementing and administering specific project plans of the grant project. For example, such information might include the local Department of Transportation as a key partner agency addressing transportation barriers and how this entity has participated in similar efforts in the past and the success of these past efforts, and potential success of coordination on the applicant(s) grant project. </P>
                <HD SOURCE="HD1">X. Review Process and Evaluation Criteria </HD>
                <P>A careful evaluation of applications will be made by a technical review panel who will evaluate the applications against the criteria listed below. The panel results are advisory in nature and not binding on the Grant Officer. The Department may elect to award grants either with or without discussion with the offeror. In situations without discussions, an award will be based on the offeror's signature on the SF 424, which constitutes a binding offer. The Grant Officer may consider any information that is available and will make final award decisions based on what is most advantageous to the Government, considering factors such as: </P>
                <P>—Panel findings; </P>
                <P>—Geographic distribution of the competitive applications; </P>
                <P>—The availability of funds. </P>
                <HD SOURCE="HD2">Criteria </HD>
                <P>The following criteria, and the weights assigned to each, will apply to the review of the responsiveness of the information requested in this application to this announcement: </P>
                <P>1. “Statement of Need”, [15 points] which will consider the scope and targeting of the overall project design to address deficiencies and requirements of the current workforce delivery system. </P>
                <P>2. “Comprehensive Service Strategy”, [30 points] which will consider the extent and quality of the applicant's plan to improve and enhance workforce delivery services to people with disabilities. </P>
                <P>3. “Collaboration and Coordination”, [20 points] which shall consider the extent and quality of the consortium partnerships that are involved in, and making, substantial contributions to the project, including the commitment to maintain and expand the capacity to serve the target population with local and workforce resources over a sustained period of time. </P>
                <P>4. “Innovations and Model Services”, [20 points] which shall consider the extent and degree of innovation represented in the applicant plans which go beyond the expected and predictable availability of accessible facilities and programs for people with disabilities, including innovative accessible technologies implemented on a system wide basis. </P>
                <P>5. “Demonstrated Capability”, [15 points] which shall consider the extent to which the applicant and its consortium partners demonstrate the knowledge and skills to address the diverse needs and the diversity in population of people with disabilities, and the extent to which the applicant demonstrates the ability to effectively execute grant management responsibilities. </P>
                <SIG>
                    <DATED>Signed at Washington, DC, this 22nd day of May, 2000. </DATED>
                    <NAME>Laura Cesario, </NAME>
                    <TITLE>Grant Officer.</TITLE>
                </SIG>
                <EXTRACT>
                    <HD SOURCE="HD1">Appendix A: SF-424 </HD>
                    <HD SOURCE="HD1">Appendix B: Budget Information Form </HD>
                    <BILCOD>BILLING CODE 4510-30-P </BILCOD>
                </EXTRACT>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="33838"/>
                    <GID>EN25MY00.017</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="33839"/>
                    <GID>EN25MY00.018</GID>
                </GPH>
                <GPH SPAN="3" DEEP="604">
                    <PRTPAGE P="33840"/>
                    <GID>EN25MY00.019</GID>
                </GPH>
                <GPH SPAN="3" DEEP="523">
                    <PRTPAGE P="33841"/>
                    <GID>EN25MY00.020</GID>
                </GPH>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13153 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4510-30-C</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="33842"/>
                <AGENCY TYPE="N">LEGAL SERVICES CORPORATION </AGENCY>
                <SUBJECT>Grants Cooperative Agreements; Availability etc.: Civil Legal Services to Poor—Various States </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Legal Services Corporation. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Program Letters 98-1 and 98-6 regarding statewide planning and Grant Assurances for FY2001. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Program Letters 98-1 and 98-6 regarding statewide planning were issued in 1998 to solicit input on and assist recipients of Legal Services Corporation funding in improving the delivery of legal services to low-income persons. Recipients of such funding must also agree to the Grant Assurances for FY2001 as part of the competitive bidding process. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>June 26, 2000. Comments must be submitted on or before this date. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Comments should be submitted to Victor M. Fortuno General Counsel, Office of Legal Affairs, Legal Services Corporation, 750 First Street, NE, Washington, DC 20002-4250; 202-336-8800. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In 1998 the Legal Services Corporation (LSC) issued Program Letters 98-1 and 98-6 to all LSC recipients. These program letters solicited input from LSC recipients on improving the delivery of legal services to low-income persons through statewide planning and coordination among LSC recipients. These letters are also available via the Internet at ­http://ain/ainboard/RFP/Appxcvr.htm in Appendix I. Although not required to publish these documents, LSC has decided to do so. Statewide planning has become an increasingly important aspect of the delivery of legal services to low-income persons. </P>
                <P>All recipients of LSC funding must agree to the Grant Assurances. This document is also available via the Internet at http://ain/ainboard/ainboard.htm under Application Forms. The Grant Assurances addresses the recipient's agreement to comply with all applicable laws, rules, regulations, guidelines, instructions, etc. and to cooperate fully with all auditing, monitoring and compliance activities and requirements. Although not required to publish this document, LSC has decided to do so. </P>
                <P>Comments received by LSC regarding these documents will be considered as part of LSC's ongoing process of evaluating the best means of delivering legal services to low-income persons and ensuring LSC recipient compliance with all applicable laws, rules, regulations, guidelines, instructions, etc.</P>
                <SIG>
                    <NAME>Victor M. Fortuno,</NAME>
                    <TITLE>Vice President for Legal Affairs and General Counsel. </TITLE>
                </SIG>
                <HD SOURCE="HD1">Program Letter 98-1, February 12, 1998, State Planning</HD>
                <HD SOURCE="HD2">Summary </HD>
                <P>This Program Letter calls upon all LSC recipients to participate in a state planning process to examine, from a statewide perspective, what steps should be taken in their states to develop further a comprehensive, integrated statewide delivery system. State planners should evaluate whether all programs are working in a coordinated fashion to assure that pressing client needs are being met, that sufficient capacities for training and information sharing exist, that programs are moving forward together on technology, and are collaborating to increase resources and develop new initiatives to expand the scope and reach of their services.</P>
                <P>In states with a number of LSC-funded programs and/or the presence of very small programs, a key question to be answered is whether the current structure of the state delivery system, and specifically the number of programs, constitutes the most effective and economical way to meet client needs throughout the state. </P>
                <P>The state planning process should develop a report to be submitted to LSC on or before October 1, 1998. We will be guided by your recommendations when making our funding decisions for FY 1999 and beyond. </P>
                <HD SOURCE="HD2">Background </HD>
                <P>
                    1995 Program Letter. In July 1995, in anticipation of Congressional action on LSC's 1996 appropriation, we asked recipients in each state to participate in the development of a plan for the design, configuration and operation of LSC-funded programs in the state. In view of potential LSC funding cuts and Congressional restrictions on client services, we were especially concerned that recipients work closely with other stakeholders (
                    <E T="03">e.g.</E>
                    , state and local bar associations, IOLTA funders, the judiciary, client groups, non-LSC-funded programs, and others with an interest in legal services) to develop an integrated delivery system to address client needs. A subsequent August 1995 Program Letter outlined the issues and criteria the state planning process should address. Included were integration of LSC-funded programs into a statewide legal services system; advisability of consolidation of programs; consideration of efficient intake and provision of advice and brief service; appropriate use of technology; engagement of pro bono attorneys; and development of additional resources. 
                </P>
                <P>Responses to Changes in Laws Affecting Clients and LSC Recipients. Much has occurred since August 1995. Fundamental changes have been made in laws and programs affecting eligible clients—changes which have increased clients—need for legal information, advice, and representation. At the same time, LSC appropriation measures have resulted in deep funding cuts for many programs, elimination of LSC funding of national and state support entities, and dramatic changes in the range of services LSC recipients are permitted to perform. In response, many states have initiated planning processes, developed new partnerships to leverage resources, expanded funding sources, implemented new technologies, and launched innovative methods for serving clients. </P>
                <P>Efforts to develop and strengthen comprehensive delivery systems in order to improve and expand client services continue in many states. Equal Justice Commissions, Bar sponsored committees, and organizations of legal services providers continue to explore ways to maximize services in a changed and changing environment. LSC supports these ongoing state efforts and encourages others. </P>
                <P>1998 Grant Decisions. In the 1998 LSC grant competition, we determined that grants in several states that were eligible for three year funding should be made for a shorter period. For North Carolina, grants were made for one year. For New York, New Jersey, Pennsylvania and Virginia, grants were made for two years. The decision to award grants for a shorter period was made for two reasons: (1) To encourage recipients in these states to develop further their plans for a comprehensive, integrated statewide delivery system; and, (2) concern that the number of LSC-funded programs in these states may not constitute the most economical and effective configuration for delivering legal services to the low-income community. </P>
                <P>1998 Program Letter. This Program Letter calls upon all recipients to re-examine and adjust as necessary their state delivery plans in order to further improve and expand legal services to eligible clients within the state. </P>
                <HD SOURCE="HD2">A Comprehensive, Integrated Statewide Delivery System</HD>
                <P>
                    In re-evaluating delivery plans, recipients should examine the progress they have made in the past two and one 
                    <PRTPAGE P="33843"/>
                    half years in developing a comprehensive, integrated statewide delivery system. Careful planning and coordination is necessary to insure that pressing legal needs do not go unmet and that resources are used wisely and economically. States must continue to innovate and develop new strategies and alternative delivery models to make the most of scarce resources—to reach more clients, and to provide higher quality services through enhanced use of information technology; centralized intake systems providing advice, brief services, and referrals; expansion of community legal education, pro se, and other methods promoting client self-help; better coordination with volunteer private attorneys; and other, similar initiatives requiring substantial resources and expertise to undertake. 
                </P>
                <P>There are many ways for states to achieve these goals. Many excellent models exist of statewide fundraising, integrated technology, statewide and regional hotlines, pro se projects, taskforces and training. Recipients should evaluate which approaches will work best in their states to achieve an even stronger, more effective system for addressing client needs. </P>
                <P>Recipients must also examine how the present configuration of programs, and specifically the number of programs, impacts upon the overall effectiveness of the state delivery system. In this regard, it is especially important that each participant look at client services, not from the view of just one city, or one county, or one program, but from a statewide perspective. </P>
                <HD SOURCE="HD2">What Is Required by This Letter </HD>
                <P>In the past two and one half years, several states have undertaken extensive processes to evaluate their delivery systems and have implemented, or are in the process of implementing, many state planning recommendations. Additionally, some states have ongoing planning processes involving a wide variety of stakeholders in the civil justice system. We do not intend such states to repeat past, or supplant current processes. Instead, we ask recipients to either work within ongoing processes or develop new ones appropriate to the situation in each state. In either case, we hope recipients and other stakeholders will view this process as an opportunity to join together to strengthen the delivery system and improve and expand services to clients. </P>
                <P>In this context we call upon each LSC-funded program to share responsibility for ensuring that a statewide planning process, whether ongoing or to be initiated, addresses the questions discussed further below. For each question state planners should: </P>
                <P>• Assess the strengths and weaknesses of the current approach; </P>
                <P>• Establish goals to strengthen and expand services to eligible clients; and</P>
                <P>• Determine the major steps and a timetable necessary to achieve those goals. </P>
                <P>
                    A report should be submitted to LSC on or before October 1, 1998. 
                    <SU>1</SU>
                    <FTREF/>
                     If a state has recently developed a plan which addresses the substance of one or more of the following questions, for those questions, the state need only report on the pertinent section(s) of that plan. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         LSC will provide guidance at a later date on the format for this report.
                    </P>
                </FTNT>
                <P>In exceptional cases, it may not be possible for a state planning process to fully address all of the following questions. In such cases, recipients should contact the LSC staff member responsible for their state. </P>
                <P>The questions to be addressed are: </P>
                <P>1. How are intake and delivery of advice and referral services structured within the state? What steps can be taken to ensure a delivery network that maximizes client access, efficient delivery, and high quality legal assistance? </P>
                <P>2. Is there a state legal services technology plan? How can technological capacities be developed statewide to assure compatibility, promote efficiency, improve quality, and expand services to clients? </P>
                <P>3. What are the major barriers low-income persons face in gaining access to justice in the state? What efforts can be taken on a statewide basis to expand client access to the courts, provide preventive legal education and advice, and enhance self-help opportunities for low-income persons? </P>
                <P>4. Do program staff and pro bono attorneys throughout the state receive the training and have access to information and expert assistance necessary for the delivery of high quality legal services? How can statewide capacities be developed and strengthened to meet these needs? </P>
                <P>5. What is the current status of private attorney involvement in the state? What statewide efforts can be undertaken to increase the involvement of private attorneys in the delivery of legal services? </P>
                <P>6. What statewide financial resources are available for legal services to low-income persons within the state? How can these resources be preserved and expanded? </P>
                <P>7. Where there are a number of LSC-funded programs and/or the presence of very small programs, how should the legal services programs be configured within the state to maximize the effective and economical delivery of high quality legal services to eligible clients within a comprehensive, integrated delivery system? </P>
                <HD SOURCE="HD3">1. Intake and the Provision of Advice and Brief Services</HD>
                <P>How are intake and delivery of advice and referral services structured within the state? What steps can be taken to ensure a delivery network that maximizes client access, efficient delivery, and high quality legal assistance?</P>
                <P>A successful intake system is critical to effective and comprehensive delivery of legal services. Over the past two years many programs have instituted centralized telephone intake and delivery systems which provide high quality advice and brief service assistance, and promptly refer clients whose problems require more assistance to program case handlers or other resources. In a number of states, statewide or regional systems, using advanced telephone and computer technology, have consolidated these functions in one location where trained, experienced staff provide prompt access for clients and minimize the risk of multiple referrals or loss of clients. These systems improve the quantity and quality of advice, brief service and referral assistance while increasing the number of extended service cases which can be handled by the program.</P>
                <P>State planners should evaluate the current status of intake and delivery of advice and referral services within the state and develop strategies for improvement. Consideration should be given to developing regional and statewide intake and delivery systems which:</P>
                <P>• Are client-centered, providing ease of access to legal services and prompt, high quality assistance or referral; </P>
                <P>• Use specialization to enhance case evaluation and provision of advice, brief service and referral assistance; </P>
                <P>• Make effective use of technology; and</P>
                <P>• Provide oversight and follow-up to ensure high quality legal services and client satisfaction. . </P>
                <HD SOURCE="HD3">2. Effective Use of Technology </HD>
                <P>Is there a state legal services technology plan? How can technological capacities be developed statewide to assure compatibility, promote efficiency, improve quality, and expand services to clients?</P>
                <P>
                    Within individual programs, effective use of technology can reduce the cost and substantially enhance the quality of 
                    <PRTPAGE P="33844"/>
                    services. Collectively, technology can dramatically improve the capacity of staff throughout the state to quickly exchange and share information, improving their ability to stay current with the law, develop legal strategies, write briefs and otherwise serve clients. In the past two years, many programs have significantly increased their technological capacities. On a statewide level, programs have used new technologies to establish E-mail communication with all legal services staff throughout the state; to connect with other service providers; to exchange information with private attorneys participating in PAI efforts; to establish centralized brief/pleadings/forms/manuals/ information banks; to create resource centers for information on state law and policy developments; and to establish unified case management systems which allow for data collection and outcome measures. New technologies involving the Internet and advanced telephone and computer applications have also been used to provide legal and program resource information to clients.
                </P>
                <P>Improving and staying current with technology is costly and makes it all the more important that states take a unified approach and develop a technology plan that will maximize collective capacity while minimizing cost. A state technology plan should establish reasonable goals and set forth steps to:</P>
                <P>• Assure that all programs have networked computer access for all staff; integrated case management; computerized timekeeping; E-mail and the ability to electronically transfer documents; computerized financial management systems; and technological support; </P>
                <P>• Develop or improve compatible technological capacities which will allow all staff, statewide, to communicate with each other, share information, and take advantage of other efficiencies made possible by computerization; and</P>
                <P>• Use new technologies to provide legal and program resource information to clients and other interested persons. </P>
                <HD SOURCE="HD3">3. Increased Access to Self-Help and Prevention Information</HD>
                <P>What are the major barriers low-income persons face in gaining access to justice in the state? What efforts can be taken on a statewide basis to expand client access to the courts, provide preventive legal education and advice, and enhance self-help opportunities for low-income persons?</P>
                <P>Pro se, community legal education and access to courts efforts have great potential to address many of the legal needs of low-income persons. Programs in many states utilize these methods to increase legal information available to the public, empower clients to advocate on their own behalf, and increase access to the courts for all low-income people. Given the intensive effort required to implement such strategies, and the influence state laws and rules have on such initiatives, often these results can be realized more easily by coordinated state level efforts. In several states, for example, collaboration with state bar committees and state judicial administrations has resulted in rule changes, publication of pro se oriented materials and more accessible court systems. Likewise, the development of self-help and community legal education materials has benefitted from concerted statewide efforts involving a variety of organizations working to make justice more accessible.</P>
                <P>State planners should evaluate the status of pro se, community legal education, and access efforts in their state and determine what steps should be taken statewide to enhance their effectiveness in meeting client needs. Consideration should be given to:</P>
                <P>• Statewide coordination and/or production of pro se and community education materials, such as brochures in multiple languages, videos, cable-access TV programs, and projects designed to take advantage of new technologies such as computerized pro se programs and the world wide web; and</P>
                <P>• State level initiatives, including efforts with bar associations, the judiciary and other interested parties to increase access to the courts.</P>
                <HD SOURCE="HD3">4. Capacities for Training and Access to Information and Expert Assistance</HD>
                <P>Do program staff and pro bono attorneys throughout the state receive the training and have access to information and expert assistance necessary for the delivery of high quality legal services? How can statewide capacities be developed and strengthened to meet these needs?</P>
                <P>In the last two years several states have developed new or strengthened existing capacities to ensure that staff and pro bono attorneys throughout the state receive necessary training and have access to information and expert assistance essential for the delivery of high quality legal services. These states employ a variety of methods to provide staff and pro bono attorneys with training on substantive law and skills development, practice manuals and related poverty law materials, information on poverty law developments and strategies, and co-counseling for less experienced staff and pro bono attorneys. Communication, planning and ongoing discussion concerning major legal needs, poverty law developments, effectiveness of approaches, and commonalities in legal work, helps ensure productive use of resources. The use of new technologies has helped maximize the effectiveness of these efforts.</P>
                <P>State planners should evaluate current capacities for the provision of training and related services essential for the delivery of high quality legal services. Planners should:</P>
                <P>• Assess how a statewide approach can address the needs for these services of staff and pro bono attorneys throughout the state; and </P>
                <P>• Determine the steps necessary to provide these services as effectively and efficiently as possible. </P>
                <HD SOURCE="HD3">5. Engagement of Pro Bono Attorneys</HD>
                <P>What is the current status of private attorney involvement in the state? What statewide efforts can be undertaken to increase the involvement of private attorneys in the delivery of legal services? </P>
                <P>In the past two years, several states have been successful in enlisting or re-enlisting the state Bar, the judiciary and others in developing and supporting private attorney involvement throughout the state. These efforts have helped local private attorney involvement programs expand participation rates and the range and types of services available to clients. State planners should evaluate the current status of private attorney involvement in the state and consider how statewide strategies can increase engagement of pro bono attorneys and benefit clients throughout the state, including areas of the state with lower private attorney involvement.</P>
                <P>Consideration should be given to: </P>
                <P>• Renewed efforts to involve the Bar, the judiciary and other leaders in the legal community in promoting private attorney involvement; </P>
                <P>• Providing greater opportunities for attorney participation in a full spectrum of legal work, including advice and brief service, negotiation, administrative representation, pro se classes, transactional assistance, and simple and complex litigation; </P>
                <P>• Providing greater opportunities for attorneys to assist programs with training, co-counseling and mentoring staff; and</P>
                <P>
                    • Providing greater opportunities for law schools, corporate counsel, government attorneys, and other professionals to engage in pro bono activities. 
                    <PRTPAGE P="33845"/>
                </P>
                <HD SOURCE="HD3">6. Development of Additional Resources </HD>
                <P>What statewide financial resources are available for legal services to low-income persons within the state? How can these resources be preserved and expanded? </P>
                <P>In the past two years, many programs have increased the resources available to them through innovative grant projects, local fundraising and other efforts. Even more dramatic, however, are the increases programs have received in many states through collective development and/or expansion of statewide revenues such as state appropriations, filing fee surcharges, state fundraising campaigns, state bar dues checkoffs and direct state bar grants. Whether new or expanded, these revenues have almost always been the product of thoughtful planning with programs and other stakeholders working together. </P>
                <P>State planners should evaluate the possibilities for further statewide resource development and develop a statewide strategy to preserve, build, and/or create new financial and non-financial resources in their state. Since program efforts to build such statewide resources are more successful when many stakeholders participate, it is especially important for planners to involve a variety of community leaders in these efforts. </P>
                <HD SOURCE="HD3">7. Configuration of a Comprehensive, Integrated Statewide Delivery System </HD>
                <P>Where there are a number of LSC-funded programs and/or the presence of very small programs, how should the legal services programs be configured within the state to maximize the effective and economical delivery of high quality legal services to eligible clients within a comprehensive, integrated delivery system? </P>
                <P>In most states, the present delivery structure reflects national funding decisions made in the 1970's. In many states, those decisions were not determined by analysis of what delivery structure would yield the most economical and effective services to clients throughout the state. Moreover, those decisions were made before such major developments in legal services delivery such as IOLTA funding, private attorney involvement, law school clinical programs, hotlines, the emergence of other civil legal aid providers, and restrictions on recipients' non-LSC funds; and before the information revolution and the opportunities it presents with personal computers, E-mail, sophisticated telephone technology, and the Internet. In light of developments over the past twenty-five years, and especially since 1995, it is time to take a fresh look and re-evaluate those structures. </P>
                <P>Re-evaluation is particularly critical in states with a number of LSC-funded programs and/or the presence of very small programs. States with many programs often suffer from uneconomical and inefficient redundancy of effort, or no effort at all, in technology, training, fundraising, and development of client services such as intake, advice and referral systems or client education materials. Similarly, small programs often lack the resources necessary to develop proper staff supervision or appropriate specialization, or to acquire current technology necessary for maximum effectiveness. </P>
                <P>In addition, while individual programs may excel, a large number of programs or the presence of small programs may result in unnecessary diversion of the state's resources from client services to administrative overhead. Each program, no matter how large or small, must devote significant resources to A-133 audits, state and federal tax and wage reports, funding applications, recordkeeping, personnel policies, purchase and maintenance of technology and equipment, and other administrative tasks. Experienced and accomplished lawyers spend time on program administration when they could be using their talents to represent clients, train or mentor new lawyers and otherwise lead their program's legal work. </P>
                <P>Where these conditions exist, state planners must consider whether consolidation of programs would make better use of resources available in the state. </P>
                <P>There is no magic number of programs or a single delivery model that fits all states. In some states, a statewide LSC provider makes the most sense; in others, a regional approach or other configuration may be appropriate. Each state must examine what configuration, from a statewide perspective, maximizes services and benefits for clients throughout the state. Factors to be considered include: </P>
                <P>• Size, complexity, cultural and ethnic diversity/homogeneity of client population. </P>
                <P>• Geographic, physical, and historical distinctions and affinities within the state. </P>
                <P>• Variation in local client needs and ability to respond and set priorities accordingly. </P>
                <P>• Assessments of programs' performance and capacity to deliver effective and efficient legal services in accordance with LSC and other professional criteria. </P>
                <P>• Ease and efficiency of client access to services and opportunities for improvement. </P>
                <P>• Capacity to efficiently and effectively conduct community legal education, pro se and outreach activities. </P>
                <P>• Level, uniformity, and plans for further development of technological capacity. </P>
                <P>• Current levels of private bar involvement and potential for expansion. </P>
                <P>• The availability of training, expert assistance, and information about legal developments. </P>
                <P>• Current funding sources and potential to expand resources available to all programs. </P>
                <P>• Cultural and ethnic diversity of program leadership and management. </P>
                <P>• Relative costs associated with fiscal and administrative responsibilities and potential savings in management, board and administrative costs. </P>
                <P>In making grants for FY 1999 and beyond, we will look closely at each state where there is currently a number of LSC-funded programs and/or the presence of very small programs to assess whether careful consideration has been given to consolidation of LSC programs. We hope, and have faith, that in these states, this planning process will result in plans for merger and consolidation of programs and integration of services on a broader scale than we have previously seen, and that each state's plan will result in a configuration that is efficient and effective in providing access to justice for the state's low-income clients. </P>
                <HD SOURCE="HD2">Questions </HD>
                <P>LSC staff will be contacting recipients to discuss this Program Letter. In the meantime, if you have questions, please contact the LSC staff member responsible for your state. </P>
                <HD SOURCE="HD1">Program Letter 98-6, July 6, 1998, State Planning Considerations </HD>
                <HD SOURCE="HD2">Introduction </HD>
                <P>
                    On February 12, 1998, the Corporation issued Program Letter 98-1 calling upon all LSC recipients to participate in a state planning process to examine, from a statewide perspective, what steps should be taken in their states to further develop a comprehensive, integrated statewide delivery system. The Letter poses seven questions recipients are to address in their planning processes and requests recipients to submit a report to LSC on or before October 1, 1998. Many 
                    <PRTPAGE P="33846"/>
                    recipients have asked LSC to provide further guidance and additional information about how the state planning process will affect LSC grant decisions. Recipients have also inquired about the format for the October 1 report. This Program Letter responds to these requests. 
                </P>
                <HD SOURCE="HD2">State Planning Considerations </HD>
                <P>The attached State Planning Considerations have been developed to provide recipients and other stakeholders with more information about statewide goals, capacities and approaches recipients should consider in their planning processes. A number of other sources of information that may assist state planners and upon which these Considerations draw are referenced in the Planning Considerations. We hope these Planning Considerations will help states develop effective plans to strengthen their delivery systems and services to clients. We encourage recipients with any questions about the State Planning Considerations or planning process to contact the LSC staff member responsible for their state. </P>
                <HD SOURCE="HD2">How the State Planning Process Will Affect LSC Grant Decisions </HD>
                <P>
                    The Corporation is directed under the LSC Act to “insure that grants and contracts are made so as to provide the most economical and effective delivery of legal assistance to persons in both urban and rural areas.” 
                    <SU>2</SU>
                    <FTREF/>
                     The state planning process will provide information that helps LSC exercise this statutory responsibility. 
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Legal Services Corporation Act, Section 1007(a)(3).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">1. Competition </HD>
                <HD SOURCE="HD3">a. Duration of Grants </HD>
                <P>
                    The state planning process will provide information that helps LSC determine the duration of grants for service areas in the 1999 competition, 
                    <E T="03">i.e.,</E>
                     service areas that are eligible for grants of up to three years commencing January 1, 1999. 
                </P>
                <P>In the 1998 LSC grant competition, we determined that grants in several states that were eligible for three year funding would be made for a shorter period. The decision to award grants for a shorter period was made for two reasons: (1) To encourage recipients in these states to develop further their plans for a comprehensive, integrated statewide delivery system; and (2) concern that the configuration of LSC-funded programs in these states did not constitute the most economical and effective structure for delivering legal services to the low-income community. </P>
                <P>As with the 1998 competition, LSC will take into account state delivery plans and configuration of programs in determining the duration of grants for service areas now being competed. Where LSC believes states need to further develop their plans for a comprehensive, integrated statewide delivery system or where LSC remains concerned about the configuration of LSC-funded service areas, grants will be made for less than three years. </P>
                <HD SOURCE="HD3">b. Service Areas </HD>
                <HD SOURCE="HD3">1. 1999 Competition </HD>
                <P>The state planning process will not affect decisions about the number, size or configuration of service areas in competition this year. </P>
                <HD SOURCE="HD3">2. 2000 and Future Competition Years </HD>
                <P>Information received through the planning process will affect future decisions regarding the most appropriate number, size and configuration of LSC-funded service areas to be competed for the year 2000 and beyond. This includes service areas that become scheduled for those years because of one or two year grant awards made in the present 1999 competition. </P>
                <HD SOURCE="HD3">2. Grant Renewals </HD>
                <P>
                    The state planning process will not affect decisions about the number, size or configuration of service areas up for renewal or the duration of grant renewals, 
                    <E T="03">i.e.,</E>
                     previously made multi-year awards which are now up for renewal. Decisions on renewal of these grants will continue to be based upon a showing of the renewal applicant's continued ability “to perform the duties required under the terms of its grant.” 
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         45 CFR 1634.11.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Format for the October 1 Report </HD>
                <P>The attached Instructions for State Planning Reports provide information about the structure and format of the reports due at LSC on or before October 1, 1998. Please contact the LSC staff member responsible for your state if you have any questions.</P>
                <HD SOURCE="HD1">Instructions for State Planning Reports </HD>
                <P>Please submit reports to the Office of Program Operations on or before October 1, 1998. Reports should be no longer than 35 pages and should contain the name and telephone number of a contact person(s). The report should: </P>
                <P>A. Briefly describe the state planning process and participants. </P>
                <P>B. Address the following areas in the order presented. In addressing each area, please consider LSC's State Planning Considerations and: </P>
                <P>• Assess the strengths and weaknesses of the current approach; </P>
                <P>• Establish goals to strengthen and expand services to eligible clients; and</P>
                <P>• Determine the major steps and a timetable necessary to achieve those goals. </P>
                <HD SOURCE="HD3">1. Intake, Advice and Referral </HD>
                <P>How are intake and delivery of advice and referral services structured within the state? What steps can be taken to ensure a delivery network that maximizes client access, efficient delivery, and high quality legal assistance? </P>
                <HD SOURCE="HD3">2. Technology </HD>
                <P>Is there a state legal services technology plan? How can technological capacities be developed statewide to assure compatibility, promote efficiency, improve quality, and expand services to clients? </P>
                <HD SOURCE="HD3">3. Access to the Courts, Self-Help and Preventive Education </HD>
                <P>What are the major barriers low-income persons face in gaining access to justice in the state? What efforts can be taken on a statewide basis to expand client access to the courts, provide preventive legal education and advice, and enhance self-help opportunities for low-income persons? </P>
                <HD SOURCE="HD3">4. Coordination of Legal Work, Training, Information and Expert Assistance </HD>
                <P>Do program staff and pro bono attorneys throughout the state receive the training and have access to information and expert assistance necessary for the delivery of high quality legal services? How can statewide capacities be developed and strengthened to meet these needs? </P>
                <HD SOURCE="HD3">5. Private Attorney Involvement </HD>
                <P>What is the current status of private attorney involvement in the state? What statewide efforts can be undertaken to increase the involvement of private attorneys in the delivery of legal services? </P>
                <HD SOURCE="HD3">6. Resource Development </HD>
                <P>What statewide financial resources are available for legal services to low-income persons within the state? How can these resources be preserved and expanded? </P>
                <HD SOURCE="HD3">7. System Configuration </HD>
                <P>
                    How should the legal services programs be configured within the state to maximize the effective and economical delivery of high quality 
                    <PRTPAGE P="33847"/>
                    legal services to eligible clients within a comprehensive, integrated delivery system? 
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         States with only one LSC-funded program need not answer this question.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Form C—Assurances 2001 LSC Grant Competition </HD>
                <P>If applicant is successful and receives an LSC grant or contract, </P>
                <P>Applicant Hereby Assures and Certifies That: </P>
                <P>
                    1. It will comply with the Legal Services Corporation Act of 1974 as amended (LSC Act), and any applicable appropriations acts and any other applicable law, all requirements of the rules and regulations, policies, guidelines, instructions, and other directives of the Legal Services Corporation (Corporation or LSC), including the LSC 
                    <E T="03">Audit Guide for Recipients and Auditors,</E>
                     the 
                    <E T="03">Accounting Guide,</E>
                     the 
                    <E T="03">CSR Instruction Handbook</E>
                     and with any amendments of the foregoing adopted before or during the period of this grant. It understands that successful applicants may be expected to sign further assurances before the awarding of the grant. 
                </P>
                <P>2. It will not use funds received from a source other than the Legal Services Corporation for any activity inconsistent with the requirements of Public Law 106-113, Public Law 105-277, Public Law 105-119 and Public Law 104-134. </P>
                <P>3. If the Applicant is a non-profit organization, its governing board will set specific priorities in writing, consistent with the requirements of 45 CFR Part 1620. </P>
                <P>4. It agrees to be subject to all provisions of federal law relating to the proper use of federal funds listed in 45 CFR 1640.2(a)(1). Before the initiation of the contract, the Applicant 's employees and board members will have been informed of the federal law and its consequences as required in 45 CFR 1640.3. </P>
                <P>5. It has the legal authority to apply for and receive a grant from the Legal Services Corporation. </P>
                <P>6. It will provide legal services in accordance with the plans set out in its grant application, as modified in further negotiations with the Corporation, and agrees to provide high quality, economical, and effective legal assistance, as measured by generally accepted professional standards, the provisions of the LSC Act, or a rule, regulation or guidance issued by the Corporation. </P>
                <P>7. It will not discriminate on the basis of race, color, religion, gender, age, disability, national origin, or any other basis prohibited by law against: (1) Any person applying for employment or employed by the Applicant; or (2) any person seeking assistance from the Applicant or other program(s) supported in whole or in part by this grant. </P>
                <P>8. It will provide the Corporation with copies of the following policies applicable to the employees, partners, and applicants for employment funded in whole or in part under this grant: its Equal Opportunity Policy Statement, including its Complaint Review Procedure or internal means of handling employee grievances; and its Sexual Harassment Policy, including an effective complaint procedure. Each of these will have been reviewed and approved by its governing or policy board within the last three years. It will notify the Corporation prior to the implementation of changes to its Equal Opportunity Policy Statement. </P>
                <P>9. Notwithstanding grant assurance number 10 below, and § 1006(b)(3) of the LSC Act, 42 U.S.C. 2996e(b)(3), it shall make available financial records, time records, retainer agreements, client trust fund and eligibility records, and client names, except for those reports or records subject to the attorney-client privilege, to the Corporation and any federal department or agency that is auditing or monitoring the activities of the Corporation or of the Applicant and any independent auditor or monitor receiving federal funds to conduct such auditing or monitoring, including any auditor or monitor of the Corporation. </P>
                <P>
                    10. It will cooperate with all reasonable and necessary information collection, including surveys, questionnaires, monitoring, audit, case statistical report (CSR) data, compliance and evaluation activities undertaken by the Corporation or its agents. During normal business hours it will give any authorized representative of the Corporation or the Comptroller General of the United States access to and copies of all original records, books, papers and documents pertaining to the grant in its possession, custody or control, except for that properly subject to the attorney-client privilege, applicable rules of professional responsibility or attorney work product which may be withheld to the extent consistent with grant assurance 9 above. Access must be provided to materials with information otherwise available in the public record (
                    <E T="03">e.g.</E>
                     pleadings filed in open court) and to program financial records (
                    <E T="03">e.g.</E>
                     negotiable instruments, vendor files, travel records, journals and ledgers.) It agrees to provide the Corporation with the requested materials in a form that meets the Corporation's need for information and, to the extent possible, protecting the reasonable personal privacy interests of its staff members. Should it withhold records or information on these grounds, it shall disclose the withholding and the basis therefor to LSC. LSC may require the grantee to disclose the information if LSC determines that the justification for withholding it is inadequate. In the event that records are unreasonably withheld, the Applicant will be responsible for all reasonable and necessary expenses related to LSC's efforts necessary to obtain the release of such records. It will not take any retaliatory action against any employee because of any cooperation with or release of information to LSC representatives. 
                </P>
                <P>11. It agrees to implement all specific record keeping requirements contained in the LSC Act, regulations, appropriations act, other applicable law, and other applicable LSC directives and to implement, as required, any additional specific record keeping requirements that may be forthcoming from the Corporation during the grant period. </P>
                <P>12. It will give written notice to the Corporation within thirty (30) calendar days after any of the following occurrences which involve activities funded by the grant: </P>
                <P>a. A decision to close and/or relocate any main or staffed branch office; </P>
                <P>b. Change of Chairperson of the governing/policy body; </P>
                <P>c. Change of chief executive officer; </P>
                <P>d. Change in its Charter, Articles of Incorporation, By-laws or governing body structure; </P>
                <P>e. Receipt of any notice of a claim for attorneys' fees under the provisions of § 1006(f) of the LSC Act, 42 U.S.C. § 2996e(f). The Applicant will also forward, upon receipt, a copy of the pleading requesting these attorneys' fees; or </P>
                <P>f. Change in the Independent Public Accountant performing the grantee's annual financial audit. </P>
                <P>13. It agrees that, prior to any merger or consolidation or other change in its current identity or status as a legal entity, it will provide the Corporation with sixty (60) days written notice. If it proposes to transfer its interests in its LSC grant to another entity pursuant to a merger or consolidation, it will seek approval from the Corporation for such transfer and will submit a Successor in Interest Agreement for approval by the Corporation. </P>
                <P>14. In the event that the applicant ceases to be a recipient of LSC grant funds during the 2001 grant term for whatever reason, </P>
                <P>
                    a. It agrees to provide the Corporation with written notice at least sixty (60) 
                    <PRTPAGE P="33848"/>
                    days before the Applicant voluntarily ceases to be a recipient of LSC grant funds during the term of this grant. 
                </P>
                <P>b. It will submit to the LSC, Office of Program Performance, at the time that it provides the written notice in (a) above that it is voluntarily ceasing to be a recipient of LSC grant funds or within fifteen (15) days from being notified by LSC that it will cease to be a recipient of LSC grant funds, a plan for the orderly conclusion of the role and responsibilities of the applicant as a recipient of LSC funds. The plan should describe: </P>
                <P>1. The immediate transition planning with the new provider, particularly as related to intake, accounting of all open cases (including PAI cases) and transfer of existing cases and contracts; </P>
                <P>2. The disposition of the recipient's fund balance, if any, pursuant to 45 CFR Part 1628. The applicant understands that the LSC fund balance amount, including any derivative income from LSC-funded activities which exceeds the 10-25 percent threshold amount pursuant to 45 CFR Section 1628.3(d), unless waived by LSC in writing, shall be returned to the Corporation; </P>
                <P>3. An accounting of all real property purchased in whole or in part with LSC funds. The applicant understands and agrees to abide by any agreement it has with the Corporation governing the purchase of real property in whole or in part with LSC funds. The accounting should include: </P>
                <P>i. The address and a brief description of the property and the date it was acquired; </P>
                <P>ii. The total amount of funds expended to acquire or improve the property, including principal and interest payments, and payment for capital improvements; </P>
                <P>iii. The total amount of LSC funds expended to acquire or improve the property, including principal and interest payments, and payment for capital improvements; </P>
                <P>iv. The fair market value of the property; </P>
                <P>v. A statement indicating the program's plans for disposing of the property; and </P>
                <P>vi. Copies of any agreements or contracts governing the disposition of the property. </P>
                <P>4. The total costs associated with cessation of LSC funding, and funds available to meet those costs, supported by a budget detailing the planned close out expenditures, and plans for securing payment or reimbursement due under contract from non-LSC sources; and </P>
                <P>5. An accounting of all personal/non-expendable property purchased in whole or in part with LSC funds, which has a current book or market value exceeding $1,000. The accounting list should include for each item of property: </P>
                <P>i. A brief description of the property item; </P>
                <P>ii. The date of acquisition of the property item; </P>
                <P>iii. The total amount of funds expended to acquire the property; </P>
                <P>iv. The amount of LSC funds expended to acquire the property; </P>
                <P>v. The fair market value of the property; </P>
                <P>vi. A plan for disposing of all such property, pursuant to the 1981 Property Management Manual for LSC Programs or its duly adopted successor; and </P>
                <P>vii. If the property is to be transferred, an assurance that the program, acquiring the property, will use the property in connection with the delivery of legal assistance to low-income persons. </P>
                <P>
                    c. It shall certify at the time it submits the plan in (b) above that an Independent Public Accountant will audit the recipient's 2000 financial statements, internal controls and compliance with applicable laws and regulations in accordance with the 
                    <E T="03">LSC Audit Guide for Recipients and Auditors</E>
                     and 
                    <E T="03">Government Auditing Standards.</E>
                     It shall submit to LSC's Office of the Inspector General an engagement letter from its Independent Public Accountant that includes an estimate of the LSC-funded portion of the total estimated audit cost for FY 2000 under section 509(c) of Public Law 104-134, as incorporated by Public Law 105-277 and Public Law 106-113. 
                </P>
                <P>d. It shall certify at the time it submits the plan in (a) above that it will submit Grant Activity Reports in a format specified by the Corporation in a timely manner; </P>
                <P>e. It shall participate in an orderly and professional transition of functions to the new provider to deliver services in the service area; and </P>
                <P>f. The recipient understands and agrees that, after it gives notice to LSC or after receipt of notice from LSC of the cessation of funding, the receipt of all future installments after such notice shall be contingent upon satisfactory completion of all closeout obligations imposed by the Corporation including the obligations described herein. </P>
                <P>15. It will give telephonic notice to the LSC Office of Inspector General (OIG) within two (2) working days of the discovery of any information that indicates the Applicant may have been the victim of misappropriation, embezzlement or other theft or loss of any funds (LSC funds, non-LSC funds used for the provision of legal assistance or client funds). Such notice shall be followed by written notice by mail or facsimile within ten (10) calendar days. Written notice of a theft of any property other than funds will be provided to the OIG within ten (10) calendar days from the time of the discovery of the theft. The required notice shall be provided regardless of whether the funds or property are recovered. </P>
                <P>16. It will notify the Corporation within twenty (20) days of any of the following arising from an LSC funded activity: a monetary judgment; sanction or penalty entered against the program for matters such as Rule 11 sanctions; malpractice judgments; EEO claims; IRS penalties; penalties arising out of the Americans with Disabilities Act; or voluntary settlement of any similar action or matter; or any other matter which may have a substantial impact on its delivery of services. </P>
                <P>
                    17. It understands and agrees that it will arrange for an audit and execute an agreement with its auditor that meets the requirements of LSC's 
                    <E T="03">Audit Guide for Recipients and Auditors.</E>
                     The Applicant also understands and agrees that if it fails to have an audit acceptable to LSC 's Office of Inspector General (OIG) in accordance with LSC's 
                    <E T="03">Audit Guide for Recipients and Auditors,</E>
                     the following sanctions shall be available to the Corporation as recommended by the Office of Inspector General: (1) Disallowance of the cost of the audit as a charge against LSC funds; (2) the withholding of a percentage of the recipient's funding until the audit is completed satisfactorily; and (3) the suspension of the recipient's funding until an acceptable audit is completed. 
                </P>
                <P>18. It shall cooperate with the Corporation in the Corporation's efforts to follow up on the reportable conditions, findings, and recommendations found by LSC, the Government Accounting Office, and/or the Applicant's independent public accountants to ensure that instances of deficiencies and noncompliance are resolved in a timely manner. Applicant management shall expeditiously resolve all such reported conditions, findings, and recommendations, including those of sub-recipients, to the satisfaction of the Corporation. </P>
                <P>19. It understands that the LSC Office of Inspector General may remove, suspend or bar an independent public accountant, upon a showing of good cause and after notice and an opportunity to be heard. </P>
                <P>
                    20. It certifies that it has a computer that meets or exceeds the following specifications: Pentium/266mhz, or equivalent computer system, 64 megabytes of Random Access Memory; 4 gigabyte hard disk drive; color 
                    <PRTPAGE P="33849"/>
                    monitor; Internet access; and Netscape 4.7 or Internet Explorer 5.0 browser. 
                </P>
                <P>
                    The applicant certifies that it has, or will obtain, access to e-mail on each casehandler's desk 
                    <E T="03">before December 2001.</E>
                     The applicant further certifies that, by the same deadline, access to the World Wide Web will be available in each office that houses more than three persons. Each staff member will be appropriately trained in the use of applicable software. 
                </P>
                <P>
                    21. It will submit, for each year of the grant and for each service area for which a grant is awarded, Grant Activity Reports in a format and at a time determined by the Corporation. If, during the course of the grant year, Grant Activity Reports no longer accurately reflect actual activity (
                    <E T="03">e.g.,</E>
                     CSR, budget, and staffing data) of the program, it will revise and resubmit affected Grant Activity Reports to the Corporation. 
                </P>
                <P>22. It is aware of and agrees that an award of a multi-year grant under the competitive bidding process does not obligate LSC to disburse any funds that are not authorized or appropriated by Congress nor does it preclude the imposition of additional conditions, by LSC or the Congress, on any funds that are so disbursed. During calendar year 2001, authority for LSC to disburse some of the funds under the grant award may be rescinded by Congress, or sequestered, thereby reducing the actual amount of funds disbursed under the grant. Further, additional restrictions may be imposed on the use of funds as a result of such appropriation, authorization legislation, or other law. In subsequent years, the amount of and conditions upon funding may be changed to conform to Congressional appropriation levels and legislated restrictions. Such changes and reductions, however implemented by the Legal Services Corporation, shall not constitute a termination or suspension. </P>
                <P>23. It will maintain during the grant period and for a period of six (6) years from the date of termination of the grant all records pertaining to the grant. With respect to financial records, it will maintain records and supporting documentation sufficient for the Corporation, or an independent auditor selected by the Corporation, to audit those records and determine whether the costs incurred and billed are reasonable, allowable and necessary under the terms of the grant. In this regard, the Applicant will permit the Corporation or its auditor to review the originals of all financial records and supporting documentation, procedures and internal control systems. Additionally, the Corporation retains the right to perform, or engage independent auditors to perform such an audit, whether during or subsequent to the grant period. </P>
                <P>24. It shall retain closed client files for a period of not less than five (5) years. </P>
                <P>We have read these assurances and conditions and understand that if this application is approved for funding, the grant and all funds derived therefrom will be subject to these assurances. We certify that the Applicant will comply with these assurances if the application is approved. </P>
                <EXTRACT>
                    <FP SOURCE="FP-DASH"/>
                    <FP>Name of Executive Director/(or functional equivalent) </FP>
                    <FP SOURCE="FP-DASH"/>
                    <FP>Title </FP>
                    <FP SOURCE="FP-DASH"/>
                    <FP>Signature </FP>
                    <FP SOURCE="FP-DASH"/>
                    <FP>Date </FP>
                    <FP SOURCE="FP-DASH"/>
                    <FP>Name of Governing/Policy Board Chairperson (Or other organization official authorizing this application) </FP>
                    <FP SOURCE="FP-DASH"/>
                    <FP>Title </FP>
                    <FP SOURCE="FP-DASH"/>
                    <FP>Signature </FP>
                    <FP SOURCE="FP-DASH"/>
                    <FP>Date </FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13189 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7050-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">THE NATIONAL FOUNDATION ON THE ARTS AND THE HUMANITIES</AGENCY>
                <SUBJECT>Meetings of Humanities Panel</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>The National Endowment for the Humanities.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meetings. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the provisions of the Federal Advisory Committee Act (Public Law 92-463, as amended), notice is hereby given that the following meetings of the Humanities Panel will be held at the Old Post Office, 1100 Pennsylvania Avenue, NW., Washington, DC 20506.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Laura S. Nelson, Advisory Committee Management Officer, National Endowment for the Humanities, Washington, DC 20506; telephone (202) 606-8322. Hearing-impaired individuals are advised that information on this matter may be obtained by contacting the Endowment's TDD terminal on (202) 606-8282.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The proposed meetings are for the purpose of panel review, discussion, evaluation and recommendation on applications for financial assistance under the National Foundation on the Arts and the Humanities Act of 1965, as amended, including discussion of information given in confidence to the agency by the grant applicants. Because the proposed meetings will consider information that is likely to disclose trade secrets and commercial or financial information obtained from a person and privileged or confidential and/or information of a personal nature the disclosure of which would constitute a clearly unwarranted invasion of personal privacy, pursuant to authority granted me by the Chairman's Delegation of Authority to Close Advisory Committee meetings, dated July 19, 1993, I have determined that these meetings will be closed to the public pursuant to subsections (c)(4), and (6) of section 552b of Title 5, United States Code.</P>
                <P>
                    1. 
                    <E T="03">Date:</E>
                     June 23, 2000,
                </P>
                <P>
                    <E T="03">Time:</E>
                     8:30 a.m. to 6:00 p.m.,
                </P>
                <P>
                    <E T="03">Room:</E>
                     415,
                </P>
                <P>
                    <E T="03">Program:</E>
                     This meeting will review applications for Colleges, Universities, and Education Programs I, submitted to the Office of Challenge Grants at the May 1, 2000 deadline.
                </P>
                <P>
                    2. 
                    <E T="03">Date:</E>
                     June 28, 2000,
                </P>
                <P>
                    <E T="03">Time:</E>
                     8:30 a.m. to 6:00 p.m.,
                </P>
                <P>
                    <E T="03">Room:</E>
                     415,
                </P>
                <P>
                    <E T="03">Program:</E>
                     This meeting will review applications for Colleges, Universities, and Education Programs II, submitted to the Office of Challenge Grants at the May 1, 2000 deadline.
                </P>
                <SIG>
                    <NAME>Laura S. Nelson,</NAME>
                    <TITLE>Advisory Committee Management Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13102 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7536-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL SCIENCE FOUNDATION </AGENCY>
                <SUBJECT>U.S. National Assessment Synthesis Team; Notice of Meeting</SUBJECT>
                <P>In accordance with the Federal Advisory Committee Act (Pub. L. 92-463, as amended), the National Science Foundation announces the following meeting:</P>
                <P>
                    <E T="03">Name:</E>
                     National Assessment Synthesis Team (#5219).
                </P>
                <P>
                    <E T="03">Date and Time:</E>
                     May 31, 2000, 8:30 a.m.-5:30 p.m.; June 1, 2000, 8:30 a.m.-3:30 p.m.
                </P>
                <P>
                    <E T="03">Place:</E>
                     Renaissance Hotel, 999 Ninth Street, NW, Washington DC 20001.
                </P>
                <P>
                    <E T="03">Type of Meeting:</E>
                     Open.
                </P>
                <P>
                    <E T="03">Contact Person:</E>
                     Thomas Spence, National Science Foundation, 4201 Wilson Blvd., Suite 705, Arlington, VA 22230. Tel. 703-306-1502; Fax: 703-306-0372; E-mail tspence@nsf.gov. Interested persons should contact Ms. Susan Henson at the above number as soon as possible to ensure space 
                    <PRTPAGE P="33850"/>
                    provisions are made for all participants and observers.
                </P>
                <P>
                    <E T="03">Minutes:</E>
                     May be obtained subsequent to the meeting from the contact person listed above.
                </P>
                <P>
                    <E T="03">Purpose of Meeting:</E>
                     To review preparation of the report the National Assessment Synthesis Team is preparing for the interagency Subcommittee on Global Change Research to report on the findings of the National Assessment of the potential consequences of climate variability and climate change for the United States.
                </P>
                <P>
                    <E T="03">Agenda:</E>
                </P>
                <P>Day 1 (May 31): Members will review technical comments received and will discuss revisions to report; an opportunity for public comment will be provided in late afternoon.</P>
                <P>Day 2 (June 1): Discussion of technical comments and revisions will continue.</P>
                <P>
                    <E T="03">Reason for Late Notice:</E>
                     This same notice appeared in the 
                    <E T="04">Federal Register</E>
                     on May 18, 2000. The Committee was unaware at the time the notice was submitted that it would ultimately be published two days later than anticipated. Because this upcoming Committee meeting will result in a draft report which needs to be made available for a 60-day public comment period, as directed by Congress, it is necessary to continue the Committee's expeditious progress toward completion of its report.
                </P>
                <SIG>
                    <DATED>Dated: May 22, 2000.</DATED>
                    <NAME>Karen J. York,</NAME>
                    <TITLE>Committee Management Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13160  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7555-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION </AGENCY>
                <DEPDOC>[Docket No. 40-8698] </DEPDOC>
                <SUBJECT>Plateau Resources Limited </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Nuclear Regulatory Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of receipt of a request from Plateau Resources Limited to amend Source Material License SUA-1371 for the Shootaring Canyon Uranium Mill in Garfield County, Utah to authorize the receipt and disposal of Atomic Energy Act of 1954, as amended, 11e.(2) byproduct material and notice of opportunity for a hearing. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In a letter dated March 22, 2000, Plateau Resources Limited (PRL) requested that the U.S. Nuclear Regulatory Commission (NRC) amend Source Material License SUA-1371 for the Shootaring Canyon Uranium Mill in Garfield County, Utah to authorize the receipt and disposal of Atomic Energy Act of 1954, as amended (AEA), 11e.(2) byproduct material. The AEA defines 11e.(2) byproduct material as “the tailings or wastes produced by the extraction or concentration of uranium or thorium from any ore processed primarily for its source material content.” In support of its letter request, PRL enclosed a detailed report titled Supplement to Environmental Report, also dated March 22, 2000. The Supplement to Environmental Report provides the basis for the PRL request, a detailed description of the proposed action, and an environmental assessment of the impacts of the proposal to receive and dispose of off-site generated 11e.(2) byproduct material. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Richard Weller, Uranium Recovery and Low-Level Waste Branch, Division of Waste Management, Office of Nuclear Material Safety and Safeguards, U.S. Nuclear Regulatory Commission, Mail Stop T7-J8, Washington, DC 20555. Telephone (301) 415-7287. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The uranium mill at Shootaring Canyon operated for only three months in 1982, generating a small amount of mill tailings (11e.(2) byproduct material). The mill has been on standby status since that time. Currently, the impoundment at Shootaring Canyon for disposal of uranium mill tailings is filled to only about 1% of its licensed capacity and PRL proposes to use a portion of this available capacity to receive and dispose of off-site generated 11e.(2) byproduct material. PRL intends to employ the proper procedures and controls to ensure that only 11e.(2) byproduct material will be accepted for disposal. </P>
                <P>PRL's request to amend Source Material License SUA-1371 to authorize the receipt and disposal of 11e.(2) byproduct material, including the report titled Supplement to Environmental Report, is being made available for public inspection at the NRC's Public Document Room at 2120 L Street, NW (Lower Level), Washington DC 20555. </P>
                <P>
                    The NRC hereby provides notice of an opportunity for a hearing on the license amendment request under the provisions of 10 CFR Part 2, Subpart L, “Informal Hearing Procedures for Adjudications in Materials and Operator Licensing Proceedings.” Pursuant to § 2.1205(a), any person whose interest may be affected by this proceeding may file a request for a hearing. In accordance with § 2.1205(d), a request for a hearing must be filed within 30 days of the publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . The request for a hearing must be filed with the Office of the Secretary, either: 
                </P>
                <P>(1) By delivery to the Rulemakings and Adjudications Staff of the Office of the Secretary at One White Flint North, 11555 Rockville Pike, Rockville, MD 20852; or </P>
                <P>(2) By mail or telegram addressed to the Secretary, U.S. Nuclear Regulatory Commission, Washington, DC 20555, Attention: Rulemakings and Adjudications Staff. </P>
                <P>In accordance with 10 CFR 2.1205(f), each request for a hearing must also be served, by delivering it personally or by mail, to: </P>
                <P>(1) The applicant, Plateau Resources Limited, 877 North 8th West, Riverton, Wyoming 82501, Attention: Fred Craft; and </P>
                <P>(2) The NRC staff, by delivery to the Executive Director for Operations, One White Flint North, 11555 Rockville Pike, Rockville, MD 20852, or by mail addressed to the Executive Director for Operations, U.S. Nuclear Regulatory Commission, Washington, DC 20555. </P>
                <P>In addition to meeting other applicable requirements of 10 CFR Part 2 of the NRC's regulations, a request for a hearing filed by a person other than an applicant must describe in detail: </P>
                <P>(1) The interest of the requestor in the proceeding; </P>
                <P>(2) How that interest may be affected by the results of the proceeding, including the reasons why the requestor should be permitted a hearing, with particular reference to the factors set out in § 2.1205(h); </P>
                <P>(3) The requestor's areas of concern about the licensing activity that is the subject matter of the proceeding; and </P>
                <P>(4) The circumstances establishing that the request for a hearing is timely in accordance with § 2.1205(d). </P>
                <P>The request must also set forth the specific aspect or aspects of the subject matter of the proceeding as to which petitioner wishes a hearing. </P>
                <P>
                    In addition, members of the public may provide comments on the subject application within 30 days of the publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . The comments may be provided to David L. Meyer, Chief, Rules Review and Directives Branch, Division of Freedom of Information and Publications Services, Office of Administration, U.S. Nuclear Regulatory Commission, Washington, DC 20555. 
                </P>
                <P>Any hearing that is requested and granted will be held in accordance with the Commission's “Informal Hearing Procedures for Adjudications in Materials and Operator Licensing Proceedings” in 10 CFR Part 2, Subpart L. </P>
                <SIG>
                    <PRTPAGE P="33851"/>
                    <DATED>Dated at Rockville, Maryland, this 18th day of May 2000. </DATED>
                    <P>For the Nuclear Regulatory Commission. </P>
                    <NAME>Thomas H. Essig, </NAME>
                    <TITLE>Chief, Uranium Recovery and Low-Level Waste Branch, Division of Waste Management, Office of Nuclear Material Safety and Safeguards. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13159 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7590-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">UNITED STATES POSTAL SERVICE</AGENCY>
                <SUBJECT>Sunshine Act Meeting </SUBJECT>
                <DATES>
                    <HD SOURCE="HED">TIMES AND DATES:</HD>
                    <P> 1:00 p.m., Monday, June 5, 2000; 8:30 a.m., Tuesday, June 6, 2000.</P>
                </DATES>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE:</HD>
                    <P>Philadelphia, Pennsylvania, at the Four Seasons Hotel, One Logan Square, in the North Ballroom. </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS:</HD>
                    <P>June 5 (Closed); June 6 (Open).</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>
                    <P/>
                </PREAMHD>
                <HD SOURCE="HD3">Monday, June 5-1:00 p.m. (Closed)</HD>
                <FP SOURCE="FP-2">1. Strategic Planning.</FP>
                <FP SOURCE="FP-2">2. Postal Rate Commission Opinion and Recommended Decision in Docket No. C99-4, Complaint of Continuity Shippers Association. </FP>
                <FP SOURCE="FP1-2">3. eBusiness Approval Process.</FP>
                <FP SOURCE="FP1-2">4. Financial Performance.</FP>
                <FP SOURCE="FP1-2">5. Office of Inspector General Midyear Budget and Performance Results.</FP>
                <FP SOURCE="FP1-2">6. Compensation Issues.</FP>
                <FP SOURCE="FP1-2">7. Personnel Matters.</FP>
                <HD SOURCE="HD3">Tuesday, June 6-8:30 a.m. (Open) </HD>
                <FP SOURCE="FP1-2">1. Minutes of the Previous Meeting, May 1-2, 2000.</FP>
                <FP SOURCE="FP1-2">2. Remarks of the Postmaster General/Chief Executive Officer.</FP>
                <FP SOURCE="FP1-2">3. Cycling Team.</FP>
                <FP SOURCE="FP1-2">4. Audit Committee Charter.</FP>
                <FP SOURCE="FP1-2">5. Briefing on Information Platform.</FP>
                <FP SOURCE="FP1-2">6. Capital Investments.</FP>
                <FP SOURCE="FP-2">a. Recognition Improvement Program.</FP>
                <FP SOURCE="FP-2">b. Phoenix, Arizona, Priority Mail—Postal Processing Center.</FP>
                <FP SOURCE="FP1-2">7. Report on the Philadelphia Performance Cluster.</FP>
                <FP SOURCE="FP1-2">8. Tentative Agenda for the July 10-11, 2000, meeting in Washington, D.C.</FP>
                <FURINF>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION:</HD>
                    <P>David G. Hunter, Assistant Secretary of the Board, U.S. Postal Service, 475 L'Enfant Plaza, S.W., Washington, D.C. 20260-1000. Telephone (202) 268-4800.</P>
                    <SIG>
                        <NAME>David G. Hunter,</NAME>
                        <TITLE>Assistant Secretary.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13308  Filed 5-23-00; 2:28 pm]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">OFFICE OF MANAGEMENT AND BUDGET </AGENCY>
                <SUBJECT>Cumulative Report on Rescissions and Deferrals </SUBJECT>
                <DATE>May 1, 2000. </DATE>
                <P>Section 1014(e) of the Congressional Budget and Impoundment Control Act of 1974 (Public Law 93-344) requires a monthly report listing all budget authority for the current fiscal year for which, as of the first day of the month, a special message had been transmitted to Congress. </P>
                <P>This report gives the status, as of May 1, 2000, of three rescission proposals and two deferrals contained in one special message for FY 2000. The message was transmitted to Congress on February 9, 2000. </P>
                <HD SOURCE="HD1">Rescissions (Attachments A and C) </HD>
                <P>As of May 1, 2000, three rescission proposals totaling $128 million have been transmitted to the Congress. Attachment C shows the status of the FY 2000 rescission proposals. </P>
                <HD SOURCE="HD1">Deferrals (Attachments B and D) </HD>
                <P>As of May 1, 2000, $594 million in budget authority was being deferred from obligation. Attachment D shows the status of each deferral reported during FY 2000. </P>
                <HD SOURCE="HD1">Information From Special Message </HD>
                <P>
                    The special message containing information on the rescission proposals and deferrals that are covered by this cumulative report are printed in the edition of the 
                    <E T="04">Federal Register</E>
                     cited below: 
                </P>
                <EXTRACT>
                    <P>65 FR 9017, Wednesday, February 23, 2000 </P>
                </EXTRACT>
                <SIG>
                    <NAME>Jacob J. Lew, </NAME>
                    <TITLE>Director. </TITLE>
                </SIG>
                <HD SOURCE="HD1">Attachments</HD>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s220,12">
                    <TTITLE>
                        <E T="04">Attachment A.— Status of FY 2000 Rescissions</E>
                    </TTITLE>
                    <TDESC>[In millions of dollars] </TDESC>
                    <BOXHD>
                        <CHED H="1">  </CHED>
                        <CHED H="1">
                             Budgetary
                            <LI>resources </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Rescissions proposed by the President </ENT>
                        <ENT>128.0 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Rejected by the Congress </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Currently before the Congress for less than 45 days </ENT>
                        <ENT>128.0 </ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s220,12">
                    <TTITLE>
                        <E T="04">Attachment B.— Status of FY 2000 Deferrals</E>
                    </TTITLE>
                    <TDESC>[In millions of dollars] </TDESC>
                    <BOXHD>
                        <CHED H="1">  </CHED>
                        <CHED H="1">
                            Budgetary 
                            <LI>resources </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Deferrals proposed by the President </ENT>
                        <ENT>1,622.0 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Routine Executive releases through May 1, 2000 (OMB/Agency releases of $1,027.6 million)</ENT>
                        <ENT>−1,027.6 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Overturned by the Congress</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Currently before the Congress</ENT>
                        <ENT>594.4 </ENT>
                    </ROW>
                </GPOTABLE>
                <BILCOD> BILLING CODE 3110-01-P</BILCOD>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="33852"/>
                    <GID>EN25MY00.004</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="33853"/>
                    <GID>EN25MY00.005</GID>
                </GPH>
                <PRTPAGE P="33854"/>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13123 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3110-01-C </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-42796; File No. SR-NSCC-00-06]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; National Securities Clearing Corporation; Notice of Filing and Order Granting Accelerated Approval of a Proposed Rule Change Related to General Motors Corporate Action</SUBJECT>
                <DATE>May 18, 2000.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),
                    <SU>1</SU>
                    <FTREF/>
                     notice is hereby given that on May 15, 2000, the National Securities Clearing Corporation (“NSCC”) 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 primarily by NSCC. The Commission is publishing this notice and order to solicit comments from interested persons and to grant accelerated approval of the proposal.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">1. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>The purpose of the proposed rule change is to allow the General Motors Corporation (“GM”) corporate action to be processed through NSCC's continuous net settlement (“CNS”) system.</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, NSCC 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. NSCC has prepared summaries, set forth in sections (A), (B), and (C) below, of the most significant aspects of such statements.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The Commission has modified the text of the summaries prepared by NSCC.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">(A) Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>
                    GM has offered to exchange 1.065 shares of Class H common stock for each share of $1 
                    <FR>2/3</FR>
                     par value common stock up to an aggregate of 86,396,977 shares of $1 
                    <FR>2/3</FR>
                     par value common stock.
                    <SU>3</SU>
                    <FTREF/>
                     Under the terms of this tender offer, the treatment of a tender is dependent on the number of shares tendered and the calculation of the broker solicitation fee. Under normal circumstances, the differing treatments caused the tender offer to be ineligible for processing in CNS, and NSCC would exit the security from CNS and would issue balance orders. However, because of the size of this issue and the operational impact exiting this security from CNS would have on NSCC's participants, NSCC has filed this rule change to allow NSCC to process this corporate action in CNS. This filing and the procedures established by it will only be applicable to the voluntary GM corporate action referenced therein.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         According to GM, this offer will expire at midnight on Friday, May 19, 2000, unless extended, and the tender offer will have a three day protect that will expire on May 24, 2000, unless extended.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         For a detailed description of NSCC procedures for the GM voluntary reorganization, refer to NSCC Important Notice dated May 12, 2000, a copy of which is attached to NSCC's filing as Exhibit A. NSCC's filing is available through the Commission's Public Reference Section or through NSCC.
                    </P>
                </FTNT>
                <P>For the purposes of processing this tender offer only, the following additional procedures will be followed: NSCC will process both the round-lot (shareholders of more than 100 shares) and the odd-lot (shareholders of 99 shares or less) portions of this tender offer by using both the CNS G and H reorganization subaccounts. The round-lot portion of this offer will be processed in the CNS G account and the odd-lot portion of this offer will be processed in the CNS H account. This differentiation will permit NSCC to credit long participants with positions in the H account at 100 percent and positions in the G account at the amount determined in accordance with the terms of the offer. Long participants must follow normal CNS by 6:00 p.m. on expiration plus two (“E+2”). Short participant will receive their potential liability report as usual on the morning of E+2 and will receive the liability report on the morning of E+4. NSCC notes that the total number of shares for which short participants will be liable will be based on the total number of odd lot shares plus the number of round lot shares eligible for the exchange. Submission of shares by a long participant to the G and H subaccounts constitutes a representation by such participant that the request for protection conforms to the terms of the offer.</P>
                <P>In addition to processing the corporate action as described above, NSCC will take the following steps with respect to the broker solicitation fee. NSCC will establish positions in a “USER” CUSIP for all shares moved to CNS subaccounts G and H (long and short). These positions do not represent separate instructions for the delivery and receipt of any shares. These positions will be valued at .01 cent per share. On the same day that the positions are established, the corresponding values will be debited and credited through NSCC. Reversals of these amounts will take place through NSCC the following business day.</P>
                <P>NSCC will issue special receive and deliver instructions naming long and short participants for positions established in the “USER” CUSIP. Each special deliver instruction issued to a short participant represents liability to the named contra participant for any solicitation fees for which such contra participant is entitled to make claim under the terms of the corporate action. All such claims will be made directly between the parties as promptly as possible and are not guaranteed by NSCC.</P>
                <P>
                    NSCC believes that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder. In particular, the proposed rule change is consistent with Section 17A(b)(3)(F) of the Act 
                    <SU>5</SU>
                    <FTREF/>
                     which requires that the rules of a clearing agency be designed to promote the prompt and accurate clearance and settlement of securities transactions.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         15 U.S.C. 78q-1(b)(3)(F).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">(B) Self-Regulatory Organization's Statement on Burden on Competition</HD>
                <P>NSCC does not believe that the proposed rule change will have an impact on or impose a burden on competition.</P>
                <HD SOURCE="HD2">(C) Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>No written comments have been solicited or received. NSCC will notify the Commission of any written comments received by NSCC.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    The Commission finds that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder and particularly with the requirements of Section 17A(b)(3)(F).
                    <SU>6</SU>
                    <FTREF/>
                     Section 
                    <PRTPAGE P="33855"/>
                    17A(b)(3)(F) requires that the rules of a clearing agency be designed to promote the prompt and accurate clearance and settlement of securities transactions. Allowing this corporate action to be processed in the CNS system should help ensure the tenders processed through NSCC will be promptly and accurately cleared and settled.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 78q-1(b)(3)(F).
                    </P>
                </FTNT>
                <P>NSCC has requested that the Commission approve the proposed rule change prior to the thirtieth day after publication of the notice of the filing. The Commission finds good cause for approving the rule change prior to the thirtieth day after publication because such approval will allow NSCC to process this corporate action in the CNS system.</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. Persons making written submissions should file six copies thereof with the Secretary, Securities and Exchange Commission, 450 Fifth Street, NW, Washington, DC 20549-0609. 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 inspection and copying in the Commission's Public Reference Room, 450 Fifth Street, NW, Washington, DC 20549. Copies of such filing will also be available for inspection and copying at the principal office of NSCC. All submissions should refer to File No. SR-NSCC-00-06 and should be submitted by June 15, 2000.</P>
                <P>
                    <E T="03">It is therefore ordered,</E>
                     pursuant to Section 19(b)(2) of the Act,
                    <SU>7</SU>
                    <FTREF/>
                     that the proposed rule change (File No. SR-NSCC-00-06) be and hereby is approved.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>8</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Jonathan G. Katz,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13148  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8010-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SMALL BUSINESS ADMINISTRATION </AGENCY>
                <SUBJECT>National Small Business Development Center Advisory Board Public Meeting</SUBJECT>
                <P>The U.S. Small Business Administration National Small Business Development Center Advisory Board will hold a public meeting on Sunday, August 6, 2000, from 10 a.m. to 4 p.m. at the Double Tree Hotel, Portland, Maine to discuss such matters as may be presented by members, staff of the U.S. Small Business Administration, or others present. </P>
                <P>For further information, please write or call Ellen Thrasher, U. S. Small Business Administration, 409 Third Street, SW, Fourth Floor, Washington, DC 20416. Telephone number (202) 205-6817. </P>
                <SIG>
                    <NAME>Bettie Baca, </NAME>
                    <TITLE>Counselor to the Administrator. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13094 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8025-01-U ]</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <SUBJECT>Region IV, North Florida District; Jacksonville, Florida; Advisory Council Meeting; Public Meeting</SUBJECT>
                <P>The U. S. Small Business Administration, North Florida District Office, Jacksonville, Florida, Advisory Council will hold a public meeting from 2 p.m. to 3 p.m., June 15, 2000, at the Caribe Royale Resort, 14300 International Drive, Orlando, Florida, in conjunction with the SBA Florida State Lenders' Conference, to discuss such matters as may be presented by members, staff of the U. S. Small Business Administration, or others present. For further information, write or call Claudia D. Taylor, U. S. Small Business Administration, 7825 Baymeadows Way, Suite 100-B, Jacksonville, Florida 32256-7504, telephone (904) 443-1933. </P>
                <SIG>
                    <NAME>Bettie Baca, </NAME>
                    <TITLE>Counselor to the Administrator/Public Liaison. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13093 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8025-01-U </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF STATE </AGENCY>
                <DEPDOC>[Public Notice 3317] </DEPDOC>
                <SUBJECT>Civic Education Curriculum Development and Teacher Training Program for Romania </SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">NOTICE: </HD>
                    <P>Request for Proposals.</P>
                </PREAMHD>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Humphrey Fellowships and Institutional Linkages Branch of the Office of Global Educational Programs of the Bureau of Educational and Cultural Affairs announces an open competition for the Civic Education Curriculum Development and Teacher Training Project for Romania. Public and private non-profit organizations meeting the provisions described in IRS regulation 26 CFR 1.501c may submit proposals to cooperate with the Bureau in the administration of a two-year project to support the development and implementation of new curriculum units for an eleventh grade civic education and comparative government course in Romania. The grant will award up to $194,000 to facilitate the project. The U.S. organization will work in coordination with the Ministry of Education and its appointees in Romania; the public affairs section of the U.S. Embassy in Bucharest; and an advisory group of Romanian civic educators. The program will comprise two phases of activity: (1) Selection of an eight-member curriculum development team of Romanian educators and preliminary consultations in Bucharest; (2) an eight- to ten-week U.S.-based curriculum development workshop in which the team will produce draft curriculum units and a teacher's manual for an eleventh-grade comparative government course. </P>
                    <P>In addition to the activity described in this solicitation, additional program activities may be undertaken during a third phase. Contingent upon successful completion of Phases I and II, the grantee may be invited to continue program activities with additional funding that may be provided by the Bureau. These activities would include follow-up consultations in Romania to assist in the further development, review, and field-testing of the draft curricular materials and in the training of a larger group of Romanian practitioners in their utilization. </P>
                    <P>
                        The Bureau solicits detailed proposals from U.S. educational institutions and public and private non-profit organizations to develop and administer this project. Grantee organizations will consult regularly with the Bureau and with the public affairs section at the U.S. Embassy in Bucharest with regard to participant selection, program implementation, direction, and assessment. Proposals should demonstrate an understanding of the issues confronting education in Romania as well as expertise in civic education, political science, and curriculum development. The Bureau encourages applicants who can draw on the contributions of political scientists to civic education and comparative government curricula in the United 
                        <PRTPAGE P="33856"/>
                        States while adapting this experience to address Romanian educational needs. 
                    </P>
                    <P>The funding authority for the program cited above is provided through the Support for East European Democracy (SEED) Act. Programs and projects must conform with Bureau requirements and guidelines outlined in the Solicitation Package. The programs and projects of the Bureau of Educational and Cultural Affairs are subject to availability of funds. </P>
                    <HD SOURCE="HD1">Program Information </HD>
                    <P>
                        <E T="03">Overview:</E>
                         The goals of the project are to assist a team of Romanian educators to develop up-to-date curriculum units for a course in civic education and comparative government to be taught at the eleventh grade level, and to assist in training teachers to use these units in Romanian classrooms. The rationale for this project is that improving citizenship education at the high school level will better prepare Romanian students to participate actively in building a pluralistic, democratic society and will promote democratic relations among members of the school community, including students, teachers, school administrators, and parents while training teachers to assist in supporting these relationships. Applicants may suggest topics to be developed by the curriculum team; however, final determination of appropriate topics will be made by the curriculum development team in cooperation with the grantee organization and an advisory group of local curriculum development specialists in Romania during the first phase of the project. 
                    </P>
                    <HD SOURCE="HD1">Guidelines </HD>
                    <HD SOURCE="HD2">Program Planning and Implementation </HD>
                    <P>
                        Grants should begin on or around September 1, 2000, with Phase I of the project, in which a curriculum development team of eight practitioners (
                        <E T="03">e.g.,</E>
                         classroom teachers and curriculum specialists) will be chosen by a selection committee in Romania comprised of local civic education specialists, representatives of the U.S. grantee organization, and the public affairs section of the U.S. Embassy in Bucharest. A Ministry of Education official will be invited to provide liaison between the U.S. project director(s) and the Romanian government. In Phase I, the team will undertake preliminary work in Romania over a period of 3-6 months. Members of the curriculum development team, in consultation with specialists from the grantee organization and local Romanian civic education and political science specialists, will familiarize themselves with civic education curricula and teaching materials used in Romania, with materials used in the U.S. and with the needs of students in Romania, in order to select the topics to be covered in the curriculum units that will be drafted. 
                    </P>
                    <P>In Phase II, members of the curriculum development team will spend approximately eight to ten weeks in a highly structured U.S.-based workshop to be sponsored and organized by the U.S. grantee organization, and will attend focused curriculum seminars; observe relevant aspects of the U.S. educational system; and begin drafting teacher and student materials for the curriculum units in consultation with U.S. specialists. The grantee organization will be responsible for introducing the Romanian team to leading U.S. political science practitioners and civic educators with expertise that is pertinent to the topics to be explored, and to a broad range of relevant resources. The team should be familiarized with methods for effectively utilizing civic education and political science resources from various levels in a classroom setting. The workshop schedule should incorporate significant time for both individual and group work on drafting materials as well as intensive training on specific approaches to the teaching, development, and revision of civic education and comparative government topics. In addition, the workshop should include field experiences which are relevant to the materials being produced (such as visits to schools, matching the Romanian educators with U.S. teachers, and mentored attendance at professional association meetings). The grantee organization will cooperate with the curriculum development team, Romanian educators, and the Ministry of Education in Romania to design a pilot-test program for selected schools in Romania. </P>
                    <P>Possible future activities include work by the curriculum development team in centers throughout Romania with teacher trainers, local civic education specialists, political science specialists from Romanian universities, U.S. specialists from the grantee organization, and other Romanian specialists to provide introductory training for a larger group of practitioners in methods for testing and utilizing the draft curriculum units in civic education/comparative government classrooms. Revision of the draft curricular materials based on the results of field testing may be completed by the grantee organization and the Romanian curriculum development team during future phases of activity. </P>
                    <P>During these phases the Romanian Ministry of Education will provide the following assistance to the participants: </P>
                    <P>(1) Provide a contract for paid leave time for the curriculum development team during their stays in the U.S. and the subsequent in-service training work; </P>
                    <P>(2) Facilitate the logistics of in-service training sessions for teachers by providing appropriate space at regional teacher training centers (Casa Corpului Didactic). </P>
                    <HD SOURCE="HD2">Visa/Insurance/Tax Requirements </HD>
                    <P>U.S. lecturers and consultants participating in the project must be U.S. citizens. Programs must comply with J-1 visa regulations. Please refer to Program Specific Guidelines POGI) in the Solicitation Package for further information. Administration of the program must be in compliance with reporting and withholding regulations for federal, state, and local taxes as applicable. Recipient organizations should demonstrate tax regulation adherence in the proposal narrative and budget. </P>
                    <HD SOURCE="HD1">Budget Guidelines </HD>
                    <P>Grants awarded to eligible organizations with less than four years of experience in conducting international exchange programs will be limited to $60,000. </P>
                    <P>Applicants must submit a comprehensive budget for the entire program. Awards may not exceed $194,000. There must be a summary budget as well as breakdowns reflecting both administrative and program budgets. Applicants may provide separate sub-budgets for each program component, phase, location, or activity to provide clarification. The summary and detailed program and administrative budgets should be accompanied by a narrative which provides a brief rationale for each line item. The total administrative costs funded by the Bureau must be limited and reasonable. </P>
                    <P>Allowable costs for the program include the following: </P>
                    <P>(1) Administrative Costs, including salaries and benefits, of grantee organization. </P>
                    <P>(2) Program Costs, including general program costs and program costs for each Romanian participant in the U.S.-based curriculum development seminar. </P>
                    <P>Please refer to the Solicitation Package for complete budget guidelines and formatting instructions. </P>
                    <HD SOURCE="HD1">Announcement Title and Number </HD>
                    <P>
                        All correspondence with the Bureau concerning this RFP should reference 
                        <PRTPAGE P="33857"/>
                        the above title and number ECA/A/S/U-00-11. 
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION, CONTACT:</HD>
                    <P>The Humphrey Fellowships and Institutional Linkages Branch, ECA/A/S/U, Room 349, U.S. Department of State, 301 4th Street, SW, Washington, DC 20547, telephone 202 619-5289 and fax 202 401-1433, or hiemstra@pd.state.gov to request a Solicitation Package. The Solicitation Package contains detailed award criteria, required application forms, specific budget instructions, and standard guidelines for proposal preparation. Please specify Bureau Program Officer Paul Hiemstra on all other inquiries and correspondence. </P>
                    <P>
                        Please read the complete 
                        <E T="04">Federal Register</E>
                         announcement before sending inquiries or submitting proposals. Once the RFP deadline has passed, Bureau staff may not discuss this competition with applicants until the proposal review process has been completed. 
                    </P>
                    <HD SOURCE="HD1">To Download a Solicitation Package Via Internet </HD>
                    <P>The entire Solicitation Package may be downloaded from the Bureau's website at http://exchanges.state.gov/education/rfps. Please read all information before downloading. </P>
                    <HD SOURCE="HD1">Deadline for Proposals </HD>
                    <P>All proposal copies must be received at the Bureau of Educational and Cultural Affairs by 5 p.m. Washington, DC time on Friday, June 23, 2000. Faxed documents will not be accepted at any time. Documents postmarked the due date but received on a later date will not be accepted. Each applicant must ensure that the proposals are received by the above deadline. </P>
                    <P>Applicants must follow all instructions in the Solicitation Package. The original and 8 copies of the application should be sent to: U.S. Department of State, Bureau of Educational and Cultural Affairs, Ref.: ECA/A/S/U-00-11, Office of Grants Management, ECA/EX/PM, Room 336, 301 4th Street, SW, Washington, DC 20547. </P>
                    <P>Applicants must also submit the “Executive Summary” and “Proposal Narrative” sections of the proposal on a 3.5” diskette, formatted for DOS. These documents must be provided in ASCII text (DOS) format with a maximum line length of 65 characters. The Bureau will transmit these files electronically to the public affairs section at the U.S. Embassy in Bucharest for its review, with the goal of reducing the time it takes to get Embassy comments for the Bureau's grants review process. </P>
                    <HD SOURCE="HD1">Diversity, Freedom and Democracy Guidelines </HD>
                    <P>Pursuant to the Bureau's authorizing legislation, programs must maintain a non-political character and should be balanced and representative of the diversity of American political, social, and cultural life. “Diversity” should be interpreted in the broadest sense and encompass differences including, but not limited to ethnicity, race, gender, religion, geographic location, socio-economic status, and physical challenges. Applicants are strongly encouraged to adhere to the advancement of this principle both in program administration and in program content. Please refer to the review criteria under the “Support for Diversity” section for specific suggestions on incorporating diversity into the total proposal. Public Law 104-319 provides that “in carrying out programs of educational and cultural exchange in countries whose people do not fully enjoy freedom and democracy, ‘the Bureau’ shall take appropriate steps to provide opportunities for participation in such programs to human rights and democracy leaders of such countries.” Proposals should reflect advancement of this goal in their program contents, to the full extent deemed feasible. </P>
                    <HD SOURCE="HD1">Year 2000 Compliance Requirement (Y2K Requirement) </HD>
                    <P>The Year 2000 (Y2K) issue is a broad operational and accounting problem that could potentially prohibit organizations from processing information in accordance with Federal management and program specific requirements including data exchange with the Bureau. The inability to process information in accordance with Federal requirements could result in grantees' being required to return funds that have not been accounted for properly. </P>
                    <P>The Bureau therefore requires all organizations use Y2K compliant systems including hardware, software, and firmware. Systems must accurately process data and dates (calculating, comparing and sequencing) both before and after the beginning of the year 2000 and correctly adjust for leap years. </P>
                    <P>Additional information addressing the Y2K issue may be found at the General Services Administration's Office of Information Technology website at http://www.itpolicy.gsa.gov. </P>
                    <HD SOURCE="HD1">Review Process </HD>
                    <P>The Bureau will acknowledge receipt of all proposals and will review them for technical eligibility. Proposals will be deemed ineligible if they do not fully adhere to the guidelines stated herein and in the Solicitation Package. All eligible proposals will be reviewed by the program office, as well as the U.S. Department of State Office of East European Assistance, where appropriate. Eligible proposals will be forwarded to panels of Bureau officers for advisory review. Proposals may also be reviewed by the Department of State, Office of the Legal Adviser or by other Bureau elements. Final funding decisions are at the discretion of the Department of State Under Secretary for Public Diplomacy and Public Affairs. Final technical authority for assistance awards (grants or cooperative agreements) resides with the Bureau's Grants Officer. </P>
                    <HD SOURCE="HD1">Review Criteria </HD>
                    <P>Technically eligible applications will be competitively reviewed according to the criteria stated below. These criteria are not rank ordered and all carry equal weight in the proposal evaluation: </P>
                    <P>
                        <E T="03">1. Quality of the program idea:</E>
                         Proposals should exhibit originality, substance, precision, and relevance to the Bureau's mission, and responsiveness to the objectives and guidelines stated in this solicitation. Proposals should demonstrate substantive expertise in civic education, political science, and comparative government course development. 
                    </P>
                    <P>
                        <E T="03">2. Creativity and feasibility of program plan:</E>
                         A detailed agenda and relevant work plan should demonstrate substantive undertakings, logistical capacity, and a creative utilization of resources and relevant professional development opportunities. The agenda and work plan should be consistent with the program overview and guidelines described in this solicitation. 
                    </P>
                    <P>
                        <E T="03">3. Ability to achieve program objectives:</E>
                         Objectives should be reasonable, feasible, and flexible. Proposals should clearly demonstrate how the institution will meet the program's objectives and plan. 
                    </P>
                    <P>
                        <E T="03">4. Broad significance and long-term impact:</E>
                         Proposed programs should strengthen long-term mutual understanding, including maximum sharing of information and establishment of long-term institutional and individual linkages. Project objectives should have significant but realistically anticipated on-going consequences for the participants and for their surrounding societies and communities as well as for the growth and encouragement of freedom and democracy, and cooperation. 
                    </P>
                    <P>
                        <E T="03">5. Support of diversity:</E>
                         Proposals should demonstrate substantive support 
                        <PRTPAGE P="33858"/>
                        of the Bureau's policy on diversity. Achievable and relevant features should be cited in both program administration (selection of participants, program venue and program evaluation) and program content (orientation and wrap-up sessions, program meetings, resource materials and follow-up activities). The proposal should demonstrate an understanding of the specific diversity needs in Romania and strategies for addressing these needs as relevant to achieve program goals. 
                    </P>
                    <P>
                        <E T="03">6. Institutional capacity and record:</E>
                         Proposed personnel and institutional resources should be adequate and appropriate to achieve the program or project's goals. Proposals should demonstrate an institutional record of successful exchange programs, including responsible fiscal management and full compliance with all reporting requirements for past Bureau grants as determined by the grants staff. The Bureau will consider the past performance of prior recipients and the demonstrated potential of new applicants. 
                    </P>
                    <P>
                        <E T="03">7. Project evaluation:</E>
                         Proposals should include a plan to evaluate the project's success, both as the activities unfold and at the end of the program. A draft survey questionnaire or other technique plus description of a methodology to use to link outcomes to original project objectives are recommended. Successful applicants will be expected to submit intermediate program and financial reports after each project component is concluded or quarterly, whichever is less frequent. 
                    </P>
                    <P>
                        <E T="03">8. Cost-effectiveness/Cost-sharing:</E>
                         The overhead and administrative components of the proposal, including salaries and honoraria, should be kept as low as possible. All other items should be necessary and appropriate and should reflect a commitment to pursuing project objectives. Proposals should maximize cost-sharing through other private sector support as well as institutional direct funding contributions. 
                    </P>
                    <HD SOURCE="HD1">Authority </HD>
                    <P>Overall grant making authority for this program is contained in the Mutual Educational and Cultural Exchange Act of 1961, Public Law 87-256, as amended, also known as the Fulbright-Hays Act. The purpose of the Act is “to enable the Government of the United States to increase mutual understanding between the people of the United States and the people of other countries* * *; to strengthen the ties which unite us with other nations by demonstrating the educational and cultural interests, developments, and achievements of the people of the United States and other nations* * *and thus to assist in the development of friendly, sympathetic and peaceful relations between the United States and the other countries of the world.” The funding authority for the program above is provided through the Support for East European Democracy (SEED) Act. </P>
                    <P>The terms and conditions published in this RFP are binding and may not be modified by any Bureau representative. Explanatory information provided by the Bureau that contradicts published language will not be binding. Issuance of the RFP does not constitute an award commitment on the part of the Government. The Bureau reserves the right to reduce, revise, or increase proposal budgets in accordance with the needs of the program and the availability of funds. Awards made will be subject to periodic reporting and evaluation requirements. </P>
                    <HD SOURCE="HD1">Notification </HD>
                    <P>Final awards cannot be made until funds have been appropriated by Congress, allocated and committed through internal Department of State procedures. </P>
                    <SIG>
                        <DATED>Dated: May 16, 2000.</DATED>
                        <NAME>Evelyn S. Lieberman, </NAME>
                        <TITLE>Under Secretary for Public Diplomacy and Public Affairs, Department of State. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 00-12939 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4710-11-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF STATE </AGENCY>
                <DEPDOC>[Public Notice #3312] </DEPDOC>
                <SUBJECT>Shipping Coordinating Committee, Subcommittee on Safety of Life at Sea, Working Group on Fire Protection; Notice of Meeting </SUBJECT>
                <P>The U.S. Safety of Life at Sea (SOLAS) Working Group on Fire Protection will conduct an open meeting on Tuesday, June 13, 2000, at 9:30 AM, in room 6103 at U.S. Coast Guard Headquarters, 2100 Second Street, SW, Washington, DC 20593. The purpose of the meeting will be to discuss the outcome of the Forty-fourth Session of the International Maritime Organization's Subcommittee on Fire Protection, held February 21-25, 2000. In addition, preparations for the next session will also be discussed at the meeting. </P>
                <P>The meeting will focus on proposed amendments to the 1974 SOLAS Convention for the fire safety of commercial vessels. Specific discussion areas include: comprehensive review of SOLAS Chapter II-2, unified interpretations to SOLAS II-2 and related fire test procedures, recommendations on evacuation analysis for passenger ships and high-speed passenger craft, fire test procedures for fire retardant materials used in the construction of lifeboats, and use of perfluorocarbons in shipboard fire-extinguishing systems. </P>
                <P>Although the meeting will focus primarily on the outcome of the previous session, preparations and plans for the next session will also be discussed. This offers the opportunity for members of the public to be involved early in the standards development process. Members of the public wishing to make a statement on new issues or proposals at the meeting are requested to submit a brief summary to the U. S. Coast Guard five days prior to the meeting. </P>
                <P>Members of the public may attend this meeting up to the seating capacity of the room. Interested persons may obtain more information regarding the meeting of the SOLAS Working Group on Fire Protection by writing: Office of Design and Engineering Standards, Commandant (G-MSE-4), U.S. Coast Guard, 2100 Second St., SW, Washington, DC 20593, by calling: LCDR Kevin Kiefer at (202) 267-1444, or by visiting the following World Wide Website: http://www.uscg.mil/hq/g-m/mse4/stdimofp.htm. </P>
                <SIG>
                    <DATED>Dated: May 17, 2000. </DATED>
                    <NAME>Stephen M. Miller, </NAME>
                    <TITLE>Executive Secretary, Shipping Coordinating Committee, U.S. Department of State. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13193 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4710-07-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">OFFICE OF THE UNITED STATES TRADE REPRESENTATIVE</AGENCY>
                <SUBJECT>Generalized System of Preferences (GSP): Notice of Review Timetable and Pubic Hearings Regarding Additional Product Designation for Beneficiaries of the African Growth and Opportunity Act</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the United States Trade Representative.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice lists products that the Trade Policy Staff Committee (TPSC) will be reviewing for possible duty-free importation from certain sub-Saharan African countries as provided under the African Growth and Opportunity Act (AGOA), which Congress recently enacted. The notice provides the dates and places the TPSC will hold public hearings on this subject, explains how to make written comments on products included in the 
                        <PRTPAGE P="33859"/>
                        list, and provides the deadline for these submissions.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>GSP Subcommittee, Office of the United States Trade Representative, 600 17th Street, NW, Room 518, Washington, DC 20508. Telephone: (202) 395-6971.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Congress established the Generalized System of Preferences (GSP) program in Title V of the Trade Act of 1974, as amended (“Trade Act”) (19 U.S.C. 2461 
                    <E T="03">et seq.</E>
                    ). Under the GSP program, the President may exempt certain products of designated developing countries from import duties. The President implemented the program by Executive Order 11888 of November 24, 1975, and has modified it through later Executive Orders and Presidential Proclamations.
                </P>
                <P>On May 18, 2000, the President signed into law the Trade and Development Act of 2000, which includes the AGOA. The AGOA amends the GSP program, authorizing the President to provide GSP (duty-free) treatment for selected products from designated sub-Saharan African countries if, after receiving advice from the U.S. International Trade Commission, he determines that the products are not import-sensitive in the context of imports from these countries. The AGOA names those countries whose products the President may designate for duty-free importation.</P>
                <HD SOURCE="HD1">I. TPSC Review of Products To Be Selected for Duty-Free Treatment</HD>
                <P>This notice lists by Harmonized Tariff System numbers those products not currently receiving GSP treatment that the Congress determined are eligible for designation under the AGOA for such treatment when imported from sub-Saharan African countries. The TPSC's GSP Subcommittee will review this list, after holding hearings and receiving written comments from the public and advice from the International Trade Commission, to decide which of the products the TPSC will recommend to the President for GSP treatment if imported from countries designated as AGOA beneficiaries.</P>
                <P>Listing the products proposed for GSP eligibility does not indicate any opinion about the merits of granting eligibility for these products. Placement on the list indicates only that the products have been found eligible for review by the GSP Subcommittee and the TPSC, and that such review will take place.</P>
                <P>The GSP Subcommittee of the TPSC invites submissions supporting or opposing the granting of GSP eligibility for any article on the attached list. All such submissions should include an original and thirteen (13) copies in English and conform to 15 CFR 2007, particularly 2007.0, 2007.1(a)(1), 2007.1(a)(2), and 2007.1(a)(3). All submissions should identify the subject article(s) in terms of the current HTS nomenclature and should be provided by 5 p.m., July 5, 2000.</P>
                <P>All communications about public comments should be addressed to: Chairman of the GSP Subcommittee, Office of the United States Trade Representative, 600 17th Street, NW, Room 518, Washington, DC 20508. Telephone number: (202) 395-6971. Questions may be directed to any staff member of the GSP Information Center. Public versions of all documents relating to this review will be available for inspection by appointment in the USTR public reading room. Appointments may be made from 10 a.m. to noon and 1 p.m. to 4 p.m. by calling (202) 395-6186.</P>
                <P>Submissions that are granted “business confidential” status pursuant to 15 CFR 2203.6, and other qualifying information submitted in confidence pursuant to 15 CFR 2007.7, will not be available for public inspection. If a document contains such business confidential information, an original and thirteen (13) copies of the business confidential versions of the document along with an original and thirteen (13) copies of the non-confidential version must be submitted. The document that contains business confidential information should be clearly marked “business confidential” at the top and bottom of each page. The version that does not contain business confidential information (the public version) should also be clearly marked at the top and bottom of every page (either “public version” or “nonconfidential”).</P>
                <HD SOURCE="HD1">II. Requests To Participate in the Public Hearings</HD>
                <P>The GSP Subcommittee will hold hearings on September 7, 2000 and, if needed, on September 8, 2000 beginning at 10 a.m. in the Truman Room of the White House Conference Center, 726 Jackson Place, NW., Washington, DC. The hearings will be open to the public, and a transcript of the hearings will be available for public inspection or it can be purchased from the reporting company. No electronic media coverage will be allowed.</P>
                <P>All interested parties wishing to make an oral presentation at the hearings must submit the name, address, telephone number, and fax number of the witness or witnesses representing their organization to the Chairman of the GSP Subcommittee by 5 p.m. August 9, 2000 as well as an original and thirteen (13) copies (in English) or all written briefs or statements. Oral testimony before the GSP Subcommittee will be limited to five minute presentations that summarize or supplement information contained in the briefs or statements submitted for the record.</P>
                <P>If, by the close of business on August 9, 2000 no witnesses are scheduled to appear at the hearing, the hearing will be canceled. Any person interested in attending the hearing as an observer or non-participant may call the GSP Information Office (202) 395-6971 after August 9, 2000 to determine whether a hearing will be held.</P>
                <P>Post-hearing and rebuttal written briefs or statements will be accepted if they conform with the regulations cited above and if an original and thirteen (13) copies in English are submitted no later than 5 p.m. September 27, 2000. Parties not wishing to appear at the public hearings may submit pre-hearing written briefs or statements by August 9, 2000, and may submit post-hearing and rebuttal written briefs or statements by September 27, 2000. Comments by interested persons on the USITC Report prepared as part of this product review should be submitted as an original and thirteen (13) copies, in English, by 5 p.m. October 20, 2000.</P>
                <P>On behalf of the President and in accordance with section 111 of AGOA (Section 506A of the Trade Act), on May 22, 2000 the list of products proposed for duty-free treatment eligibility under the GSP was furnished to the U.S. International Trade Commission (USITC) to secure its advice on (1) the probable economic effect of the elimination of U.S. import duties under GSP on U.S. industries producing like or directly competitive products, and on consumers; and (2) to the extent possible, the level of U.S. sensitivity to imports of such Sub-Saharan products.</P>
                <HD SOURCE="HD1">Announcement of Products To Be Accepted for Designation as Eligible Articles for GSP Purposes When Imported Only From the Beneficiaries of the African Growth and Opportunity Act</HD>
                <P>
                    The AGOA authorizes the President to provide GSP (duty-free) treatment for selected products from designated sub-Saharan African countries if, after receiving advice from the U.S. International Trade Commission, he determines that the products are not import-sensitive in the context of imports from these countries. The list of products designated as eligible for duty-free treatment under the GSP as a result 
                    <PRTPAGE P="33860"/>
                    of the review will be announced this winter.
                </P>
                <SIG>
                    <NAME>H. John Rosenbaum,</NAME>
                    <TITLE>Assistant U.S. Trade Representative for Trade and Development.</TITLE>
                </SIG>
                <EXTRACT>
                    <HD SOURCE="HD1">Attachment: List of HTS Numbers of the Products Proposed for Duty-Free Treatment Eligibility Under GSP</HD>
                </EXTRACT>
                <BILCOD>BILLING CODE 3901-01-M</BILCOD>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="33861"/>
                    <GID>EN25my00.010</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="33862"/>
                    <GID>EN25my00.011</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="33863"/>
                    <GID>EN25my00.012</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="33864"/>
                    <GID>EN25my00.013</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="33865"/>
                    <GID>EN25my00.014</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="33866"/>
                    <GID>EN25my00.015</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="33867"/>
                    <GID>EN25my00.016</GID>
                </GPH>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13169  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3901-01-C</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="33868"/>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>RTCA Special Committee 159; Minimum Operational Performance Standards for Airborne Navigation Equipment Using Global Positioning System (GPS)</SUBJECT>
                <P>Pursuant to section 10(a)(2) of the Federal Advisory Committee Act (Pub. Law 92-463, 5 U.S.C., Appendix 2), notice is hereby given for a Special Committee 159 meeting to be held June 12-16, 2000, starting at 9:00 a.m. each day. The meeting will be held at RTCA, 1140 Connecticut Avenue, NW., Washington, DC 20036.</P>
                <P>The agenda will be as follows:</P>
                <P>Specific Working Group Sessions: June 12: Working Group 1, Third Civil Frequency. June 13: Working Group 6, GPS/Interference; Working Group 2C, GPS/Inertial. June 14: 9 a.m.-12 p.m., Working Group 4, Precision Landing Guidance (GPS/LAAS); Working Group 6, Interference; 1:30 p.m.-4:30 p.m., SC-159 Ad Hoc, Recommendation Support. June 15: Working Group 2, GPS/WAAS; Working Group 4, Precision Landing Guidance (LAAS). </P>
                <P>June 16: Plenary Session: (1) Chairman's Introductory Remarks; (2) Approve Summary of Previous Meeting; (3) Review Working Group (WG) Progress and Identify Issues for Resolution: (a) GPS/3rd Civil Frequency (WG-1); (b) GPS/WAAS (WG-2); (c) GPS/GLONASS (WG-2A); (d) GPS/Inertial (WG-2C); (e) GPS/Precision Landing Guidance (WG-4); (f) GPS/Airport Surface Surveillance (WG-5); (g) GPS Interference (WG-6); (h) SC-159 Ad Hoc; (4) Review of EUROCAE Activities; (5) Review/Approve Final Draft, NAVSTAR GPS L5 Civil Signal Specification; (6) Review/Approve Final Draft, SC-159 Response to the Johns Hopkins University Applied Physics Laboratory Recommendation Regarding Receiver Autonomous Integrity Monitoring; (7) Assignment/Review of Future Work; (8) Other Business; (9) Date and Location of Next Meeting; (10) Closing.</P>
                <P>Attendance is open to the interested public but limited to space availability. With the approval of the chairman, members of the public may present oral statements at the meeting.</P>
                <P>Persons wishing to present statements or obtain information should contact the RTCA Secretariat, at (202) 833-9339 (phone), (202) 833-9434 (fax). Members of the public may present a written statement to the committee at any time. </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on May 18, 2000. </DATED>
                    <NAME>Janice L. Peters,</NAME>
                    <TITLE>Designated Official.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13182  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Noise Exposure Map Notice Receipt of Noise Compatibility Program and Request for Review Austin-Bergstrom International Airport Austin, Texas</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Aviation Administration (FAA) announces its determination that the noise exposure maps submitted by City of Austin for Austin-Bergstrom International Airport under the provisions of Title 49 USC, Chapter 475 (hereinafter referred to as  “Title 49” and 14 CFR Part 150 are in compliance with applicable requirements. The FAA also announces that it is reviewing a proposed noise compatibility program that was submitted for Austin-Bergstrom International Airport under Part 150 in conjunction with the noise exposure maps and that this program will be approved or disapproved on or before November 8, 2000.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>The effective date of the FAA's determination on the noise exposure maps and the start of its review of the associated noise compatibility program are May 9, 2000. The public comment period ends July 8, 2000.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Nan L. Terry, Department of Transportation, Federal Aviation Administration, Fort Worth, Texas, 76193-0652, (817) 222-5607. Comments on the proposed noise compatibility program should also be submitted to the above office.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice announces that the FAA finds that the noise exposure map submitted for Austin-Bergstrom International Airport is in compliance with applicable requirements of Part 150, effective May 8, 2000. Further, FAA is reviewing a proposed noise compatibility program for that airport which will be approved or disapproved on or before November 8, 2000. This notice also announces the availability of this program for public review and comment.</P>
                <P>Under Title 49, an airport operator may submit to the FAA noise exposure maps which meet applicable regulations and which depict noncompatible land uses as of the date of submission of such maps, a description of projected aircraft operations, and the ways in which such operations will affect such maps. Title 49 requires such maps to be developed in consultation with interested and affected parties in the local community, government agencies, and persons using the airport.</P>
                <P>An airport operator who has submitted noise exposure maps that are found by the FAA to be in compliance with the requirements of Federal Aviation Regulations (FAR) Part 150, promulgated pursuant to Title 49, may submit a noise compatibility program for FAA approval which sets forth the measures the operator has taken or proposes for the reduction of existing noncompatible uses and for the prevention of the introduction of additional noncompatible uses.</P>
                <P>
                    On April 20, 1999, FAA published its approval of noise exposure maps for the Austin-Bergstrom International Airport in the 
                    <E T="04">Federal Register.</E>
                     On April 10, 2000, the City of Austin submitted a new 2004 noise exposure map. The FAA has completed its review of the 2004 the noise exposure maps and related descriptions submitted by City of Austin. The specific map under consideration is 2004 Future Condition Noise Exposure Map, Figure 10-1 in the submission.
                </P>
                <P>In addition to the 2004 future condition noise exposure map, the City of Austin submitted to the FAA on April 10, 2000, descriptions and other documentation which were produced during Austin-Bergstrom International Airport, Austin, Texas, Part 150 Noise Compatibility Study. It was requested that the FAA review this material as the noise exposure map, as described in Title 49, and that the noise mitigation measures, to be implemented jointed by the airport and surrounding communities, be approved as a noise compatibility program under Title 49.</P>
                <P>
                    The FAA has determined that this map for Austin-Bergstrom International Airport is in compliance with applicable requirements. This determination is effective on May 8, 2000. FAA's determination on an airport operator's noise exposure map(s) is limited to a finding that the map(s) was developed in accordance with the procedures contained in Appendix A of FAR Part 150. Such determination does not constitute approval of the applicant's data, information, or plans, or a commitment to approve a noise compatibility program or to fund the implementation of that program.
                    <PRTPAGE P="33869"/>
                </P>
                <P>If questions arise concerning the precise relationship of specific properties to noise exposure contours depicted on a noise exposure map submitted under section 103 of the Act, it should be noted that the FAA is not involved in any way in determining the relative locations of specific properties with regard to the depicted noise contours, or in interpreting the noise exposure maps to resolve questions concerning, for example, which properties should be covered by the provisions of Title 49. These functions are inseparable from the ultimate land use control and planning responsibilities of local government. These local responsibilities are not changed in any way under Part 150 or through FAA's review of detailed overlaying of noise exposure contours onto the map depicting properties on the surface rests exclusively with the airport operator which submitted those maps, or with those public agencies and planning agencies with which consultation is required under Title 49. The FAA has relied on the certification by the airport operator, under § 150.21 of FAR Part 150, that the statutorily required consultation has been accomplished.</P>
                <P>The FAA has formally received noise compatibility program for Austin-Bergstrom International Airport, also effective on May 8, 2000. Preliminary review of the submitted material indicates that it conforms to the requirements for the submittal of noise compatibility programs, but that further review will be necessary prior to approval or disapproval of the program. The formal review period, limited by law to a maximum of 180 days, will be completed on or before November 8, 2000.</P>
                <P>The FAA's detailed evaluation will be conducted under the provisions of 14 CFR Part 150, section 150.33. The primary considerations in the evaluation process are whether the proposed measures may reduce the level of aviation safety, create an undue burden on interstate or foreign commerce, or be reasonably consistent with obtaining the goal of reducing existing noncompatible land uses and preventing the introduction of additional noncompatible land uses.</P>
                <P>Interested persons are invited to comment on the proposed program with specific reference to these factors. All comments, other than those properly addressed to local land use authorities, will be considered by the FAA to the extent practicable. Copies of the noise exposure map, the FAA's evaluation of the map, and the proposed noise compatibility program are available for examination at the following locations:</P>
                <FP SOURCE="FP-1">Federal Aviation Administration, Airports Division, 2601 Meacham Boulevard, Fort Worth, Texas 76137</FP>
                <FP SOURCE="FP-1">Austin-Bergstrom International Airport, City of Austin, Aviation Department, 3600 Presidential Blvd., Austin, Texas 78719 </FP>
                <P>
                    Questions may be directed to the individual named above under the heading, 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    .
                </P>
                <SIG>
                    <DATED>Issued in Fort Worth, Texas, May 9, 2000.</DATED>
                    <NAME>Joseph G. Washington,</NAME>
                    <TITLE>Acting Manager, Airports Division.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13181  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Notice of Intent to Rule on Application To Impose and Use the Revenue From a Passenger Facility Charge (PFC) at Fayetteville Regional Airport, Fayetteville,  North Carolina</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of intent to rule on application. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA proposes to rule and invites public comment on the application to impose and use the revenue from a PFC at Fayetteville Regional Airport under the provisions of the Aviation Safety and Capacity Expansion Act of 1990 (Title IX of the Omnibus Budget Reconciliation Act of 1990) (Public Law 101-508) and Part 158 of the Federal Aviation Regulations (14 CFR Part 158).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before June 26, 2000.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments on this application may be mailed or delivered in triplicate to the FAA at the following address: Atlanta Airports District Office, 1701 Columbia Avenue, Suite 2-260, College Park, GA 30337-2747.</P>
                    <P>In addition, one copy of any comments submitted to the FAA must be mailed or delivered to Mr. Bradley S. Whited, Airport Director, of the City of Fayetteville at the following address: Mr. Bradley S. Whited, Airport Director, Fayetteville Regional Airport, P.O. Box 64218, Fayetteville, NC 28306.</P>
                    <P>Air carriers and foreign air carriers may submit copies of written comments previously provided to the City of Fayetteville under section 158.23 of Part 158.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lee Kyker, Manager of Airport Programs, Atlanta Airports District Office, 1701 Columbia Avenue, Suite 2-260, College Park, GA 30337-2747, (404) 305-7161. The application may be reviewed in person at this same location.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The FAA proposes to rule and invites public comment on the application to impose and use the revenue from a PFC at Fayetteville Regional Airport under the provisions of the Aviation Safety and Capacity Expansion Act of 1990 (Title IX of the Omnibus Budget Reconciliation Act of 1990) Pub. L. 101-508) and Part 158 of the Federal Aviation Regulations (14 CFR Part 158).</P>
                <P>On May 12, 2000, the FAA determined that the application to impose and use the revenue from a PFC submitted by the City of Fayetteville was substantially complete within the requirements of section 158.25 of Part 158. The FAA will approve or disapprove the application, in whole or in part, no later than September 8, 2000.</P>
                <P>The following is a brief overview of the application.</P>
                <P>
                    <E T="03">PFC Application No.:</E>
                     00-01-C-00-FAY.
                </P>
                <P>
                    <E T="03">Level of the proposed PFC:</E>
                     $3.00.
                </P>
                <P>
                    <E T="03">Proposed charge effective date:</E>
                     September 1, 2000.
                </P>
                <P>
                    <E T="03">Proposed charge expiration date:</E>
                     October 1, 2002.
                </P>
                <P>
                    <E T="03">Total estimated net PFC revenue:</E>
                     $942,620.
                </P>
                <P>Brief description of proposed project(s):</P>
                <FP SOURCE="FP-1">• Airport Entrance Road</FP>
                <FP SOURCE="FP-1">• Jetway System Modifications</FP>
                <FP SOURCE="FP-1">• Security System Upgrade</FP>
                <FP SOURCE="FP-1">• Preplan runway safety areas</FP>
                <FP SOURCE="FP-1">• Rehabilitate north general aviation ramp</FP>
                <FP SOURCE="FP-1">• Security system upgrade, Phase II</FP>
                <FP SOURCE="FP-1">• Design &amp; construct RSA, Rwy 4</FP>
                <FP SOURCE="FP-1">• Acquire land</FP>
                <FP SOURCE="FP-1">• Renovate terminal, Ph II</FP>
                <FP SOURCE="FP-1">• Construct RSA, Rwy 4, Ph 2</FP>
                <FP SOURCE="FP-1">• Land Purchase</FP>
                <FP SOURCE="FP-1">• Renovate terminal</FP>
                <FP SOURCE="FP-1">• Construct RSA</FP>
                <FP SOURCE="FP-1">• Acquire land</FP>
                <FP SOURCE="FP-1">• Rehabilitate Runway 10-28</FP>
                <FP SOURCE="FP-1">• Acquire land in fee</FP>
                <FP SOURCE="FP-1">• Construct fire training facility &amp; rehabilitate ARFF vehicle Update Airport Master Plan</FP>
                <FP SOURCE="FP-1">• Install taxiway guidance signs &amp; REILS</FP>
                <FP SOURCE="FP-1">• Construct new general aviation area (design only)</FP>
                <FP SOURCE="FP-1">• Acquire sweeper</FP>
                <FP SOURCE="FP-1">• Install terminal loading bridges</FP>
                <FP SOURCE="FP-1">• Acquire ARFF vehicle</FP>
                <FP SOURCE="FP-1">• Construct non-license vehicle road (design only)</FP>
                <FP SOURCE="FP-1">
                    • Taxiway K (design only)
                    <PRTPAGE P="33870"/>
                </FP>
                <FP SOURCE="FP-1">• Install utilities for general aviation</FP>
                <FP SOURCE="FP-1">• Design for Highway 301 Connector</FP>
                <FP SOURCE="FP-1">• Acquire land for airport development</FP>
                <FP SOURCE="FP-1">• Airport terminal development</FP>
                <FP SOURCE="FP-1">• Construct taxiway K (design only)</FP>
                <FP SOURCE="FP-1">• Construct GA apron (design only)</FP>
                <FP SOURCE="FP-1">• Acquire land for development</FP>
                <FP SOURCE="FP-1">• Rehabilitate terminal building</FP>
                <FP SOURCE="FP-1">• Install 107.14 security access system</FP>
                <FP SOURCE="FP-1">• Construct non-license vehicle road (NLVR)</FP>
                <FP SOURCE="FP-1">• Jet bridge modification</FP>
                <FP SOURCE="FP-1">• Construct taxiway K</FP>
                <P>Class or classes of air carriers which the public agency has requested not be required to collect PFCs: None</P>
                <P>
                    Any person may inspect the application in person at the FAA office listed above under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT.</E>
                </P>
                <P>In addition, any person may, upon request, inspect the application, notice and other documents germane to the application in person at the Federal Aviation Administration.</P>
                <SIG>
                    <DATED>Issued in Atlanta, Georgia on May 16, 2000.</DATED>
                    <NAME>Rans D. Black,</NAME>
                    <TITLE>Acting Manager, Atlanta Airports District Office Southern Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13180 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration </SUBAGY>
                <SUBJECT>Discretionary Cooperative Agreements To Assist in the Development of Crash Outcome Data Evaluation Systems </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability;—discretionary cooperative agreements to assist in the development and use of Crash Outcome Data Evaluation Systems. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Highway Traffic Safety Administration (NHTSA) announces a discretionary cooperative agreement program to assist states in the development and use of Crash Outcome Data Evaluation Systems (CODES) and solicits applications for projects under this program from states that have not previously been funded to develop CODES. Under this program states will link their existing statewide traffic records with medical outcome and charge data. The linked data will be used to support highway safety decision-making at the local, regional, and state levels to reduce deaths, non-fatal injuries, and health care costs resulting from motor vehicle crashes. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applications must be received at the office designated below on or before July 24, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Applications must be submitted to DOT/National Highway Traffic Safety Administration, Office of Contracts and Procurement (NAD-30), ATTN: Lamont O. Norwood/Mr. Mark Kromer, 400 7th Street SW, Room 5301, Washington, DC 20590. All applications submitted must include a reference to NHTSA Cooperative Agreement Program No. DTNH22-00-H-07212. Interested applicants should contact Mr. Norwood to obtain the application packet. Included in the application packet are reports about data linkage and applications for linked data developed by the CODES project. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        General administrative questions may be directed to Lamont O. Norwood, Office of Contracts and Procurement. All questions and requests for copies may be directed by e-mail at 
                        <E T="03">lnorwood@nhtsa.dot.gov</E>
                         or, by telephone, at (202) 366-8573. Programmatic questions relating to this cooperative agreement program should be directed to Dennis Utter, CODES Contracting Officer's Technical Representative (COTR), at NHTSA, Room 6125, (NRD-31) 400 7th Street SW, Washington, DC 20590, or by e-mail at 
                        <E T="03">dutter@nhtsa.dot.gov,</E>
                         or by telephone at (202) 366-5351. 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Statement of Work </HD>
                <HD SOURCE="HD2">Background </HD>
                <P>Crash data alone are unable to convey the magnitude of the medical and financial consequences of the injuries resulting from motor vehicle crashes or the success of highway safety decision-making to prevent them. Outcome information describing what happens to all persons involved in motor vehicle crashes, regardless of injury, is needed. </P>
                <P>Person-specific outcome information is collected at the crash scene and en route by EMS personnel, at the emergency department, in the hospital, and after discharge. When these data are computerized and merged statewide, they generate a source of population-based data that is available for use by state and local traffic safety and public health professionals. Linking these records to statewide crash data collected by police at the scene is the key to developing relationships among specific vehicles, crash, and occupant behavior characteristics and their medical and financial outcomes. </P>
                <P>The feasibility of linking crash and medical outcome (EMS, emergency department, hospital discharge, death certificate, claims, etc.) data was demonstrated by the CODES project. This project evolved from the Intermodal Surface Transportation Efficiency Act of 1991, which mandated that NHTSA prepare a Report to Congress about the benefits of safety belt and motorcycle helmet use. NHTSA provided funding to the States of Hawaii, Maine, Missouri, New York, Pennsylvania, Utah, and Wisconsin to link their state data and use the linked data to analyze the effectiveness of safety belts and motorcycle helmets. The Report was delivered to Congress in February 1996. In 1996, three CODES states (New York, Pennsylvania, and Wisconsin) and three states which linked crash and medical data without CODES funding (Alaska, Connecticut, and New Mexico) were awarded NHTSA research funds to develop state-specific applications for linked data. In 1997, NHTSA awarded grants for CODES linkage to Connecticut, New Hampshire, Maryland, North Dakota, South Dakota, Oklahoma, and Nevada. Iowa, Kentucky, Massachusetts, Nebraska, and South Carolina which were funded to implement the CODES linkage in 1998. Arizona, Delaware, Minnesota and Tennessee were funded in 1999. </P>
                <P>The CODES project also demonstrated that linked data have many uses for decision-making related to highway safety and injury control. In addition to demonstrating the effectiveness of safety belts and motorcycle helmets in preventing death, injury, and costs, the linked data were used to identify populations at risk for increased severity or high health care costs, the impact of different occupant behaviors on outcome, the safety needs at the community level, the allocation of resources for emergency medical services, the injury patterns by type of roadway and geographic location, and the benefits of collaboration on data quality. When crash, vehicle, and behavior characteristics were linked to outcome information, decision-makers could identify those prevention programs that had the most impact on preventing or reducing the medical and financial costs associated with motor vehicle crashes. </P>
                <P>
                    Data linkage fulfills expanded data needs without the additional expense and delay of new data collection. The linkage process itself provides feedback about data quality and content problems which leads to improvement in the state data. Thus, it is in NHTSA's interest to encourage states to qualify for CODES funding. NHTSA benefits from the improved quality of the state data, while the states benefit from state-specific 
                    <PRTPAGE P="33871"/>
                    medical and financial outcome information about motor vehicle crashes. 
                </P>
                <HD SOURCE="HD2">Objective </HD>
                <P>The objective of this Cooperative Agreement program is to provide resources to the applicant to: </P>
                <P>1. Coordinate the development and institutionalization of the capability to link state crash and medical outcome data to identify the medical and financial consequences of motor vehicle crashes. </P>
                <P>2. Utilize this information in crash analysis, problem identification, and program evaluation to improve decision-making at the local, state, and national levels related to preventing or reducing deaths, injuries, and direct medical costs associated with motor vehicle crashes. </P>
                <P>3. Provide NHTSA with population-based linked crash and injury data to analyze specific highway safety issues of interest to NHTSA in collaboration with the CODES states. </P>
                <P>4. Develop data linkage capabilities as a means of improving the quality of state data that support NHTSA's national data. </P>
                <P>This cooperative agreement is not intended to fund basic development of data systems, but rather to create linkages among existing records. However, it is hoped that this project will inspire States to develop and improve their state data and to expedite these activities in order to become eligible for CODES funding. </P>
                <HD SOURCE="HD2">General Project Requirements </HD>
                <P>1. Link statewide population-based crash to injury data for any two calendar years available since 1996, to produce a linked data file that, if not statewide, reflects a contiguous geographical area that contains at least three (3) million residents in which the residents obtain all levels of emergency medical care without the need to be transferred elsewhere, except in rare occurrences, when involved in motor vehicle crashes. The linked data must be representative and generalizable for highway traffic safety purposes in the state/area. All applicants must be able to clearly document what data are available and what data are missing and the significance of the missing data for highway traffic safety planning efforts. </P>
                <P>a. Develop a state/area-wide CODES that includes outcome information for all persons, injured and uninjured, involved in police reported motor vehicle crashes. </P>
                <P>(1) The CODES should consist of crash data linked to hospital and either EMS or emergency department data, preferably both. States without EMS or emergency department data are eligible if this type of outpatient information can be obtained from insurance claims data for everyone involved in a crash who is treated at an outpatient center. </P>
                <P>(2) Additional state/area-wide data (driver licensing, vehicle registration, citation/conviction records, insurance claims, HMO/managed care/etc., outpatient records, etc.) should be linked as necessary to meet state/area wide objectives. </P>
                <P>b. Set up processes for collaboration among the technical experts who manage the data files being linked. </P>
                <P>c. Assign an agency to be responsible for: </P>
                <P>(1) Obtaining a computer and linkage software to be dedicated to CODES activities (the computer and software resources may not be permanently tied to an existing computer network in such a way as to preclude their movement in the future, as directed by the CODES Board of Directors, to another organization more interested in continuing the linkage and application for the linked data); </P>
                <P>(2) Implementing probabilistic linkage methodology to facilitate tracking the crash victim from the scene to final disposition/recovery using existing computerized state/area-wide population-based databases; </P>
                <P>(3) Validating the linkage results by evaluating the rate of false positives and false negatives among the linked and unlinked records; </P>
                <P>(4) Analyzing the linked data; and, </P>
                <P>(5) Cross-training sufficient staff to ensure continuation of the linkage capability in spite of changes in organizational priorities or personnel during or after the project period. </P>
                <P>d. Document the file preparation, linkage and validation processes so that the linkage can be repeated efficiently during subsequent years after Federal funding ends and provide evidence of this documentation. </P>
                <P>e. Provide NHTSA a version of the linked data file with supporting documentation that conforms to State laws and regulations governing patient/provider confidentiality, yet satisfies minimum NHTSA data needs. </P>
                <P>2. Use the linked data to influence highway traffic safety and injury control decision-making by implementing at least one application of linked data that is expected to have a positive impact on reducing death, injury, and direct medical costs. </P>
                <P>3. Use the linked data to prepare management reports using a format standardized by NHTSA for a national CODES report. </P>
                <P>4. Develop the computer programs needed to translate the linked data into information useful for highway traffic safety and injury control at the local, regional, or state/area-wide level. </P>
                <P>a. Develop, for access within the State, a public-use version of the linked data, copies of which will be distributed upon request. </P>
                <P>b. Develop the resources necessary to produce and distribute routine reports, respond to data requests, and provide access to the linked data for analytical, management, planning, and other purposes after Federal funding ends. </P>
                <P>c. Use the Internet and other electronic mechanisms to efficiently distribute and share information generated from the linked data. </P>
                <P>5. Promote collaboration between the owners and users of the state/area-wide data to facilitate data linkage and applications for linked data. </P>
                <P>a. Establish a state/area-wide CODES collaborative network. </P>
                <P>(1) Convene a Board of Directors consisting of the data owners and major users of the state/area-wide data. The CODES Board of Directors will be responsible for managing and institutionalizing the linked data, establishing the data release policies for the linked data, supporting the activities of the grantee, ensuring that data linkage and application activities are appropriately coordinated within the state/area, and resolving common issues related to data accessibility, availability, completeness, quality, confidentiality, transfer, ownership, fee for service, management etc. The CODES Board of Directors shall meet bi-monthly. </P>
                <P>(2) Convene a CODES Advisory Group consisting of the CODES Board of Directors and other stakeholders interested in the use of linked data to support highway safety, injury control, EMS, etc. The CODES Advisory Group will be informed of the results of the data linkage, application of the data for decision-making, the quality of the state/area-wide data for linkage and the quality of the linked data for analysis. The CODES Advisory Group shall meet twice a year. </P>
                <P>b. Promote coordination of the various stakeholders through use of the Internet, teleconferencing, joint meetings, and other mechanisms to ensure frequent communication among all parties to minimize the expense of travel. </P>
                <P>6. Work collaboratively with NHTSA to implement the Cooperative Agreement. </P>
                <P>
                    a. 
                    <E T="03">Attend Initial Briefing Meeting.</E>
                     Each grantee shall attend a briefing meeting (date and time to be scheduled within 30 days after the award) in Washington, DC with NHTSA staff. The 
                    <PRTPAGE P="33872"/>
                    purpose of the meeting will be to review the goals and objectives of the project, discuss implementation of the linkage software, review the tasks to be specified in the action plan for the data linkage and applications of the linked data for highway safety or injury control decision-making and discuss the agendas for the Board of Directors and Advisory Group. 
                </P>
                <P>
                    b. 
                    <E T="03">Submit Detailed Action Plan and Schedule.</E>
                     Within 30 days after the briefing meeting, the grantee shall deliver a detailed action plan and schedule, covering the remaining funding period, for accomplishing the data linkage and incorporating information generated from linked data into the processes for highway safety or injury control decision-making. The action plan shall be subject to the technical direction and approval of NHTSA. 
                </P>
                <P>
                    c. 
                    <E T="03">Attend Technical Workshops.</E>
                     All grantees together shall attend two technology transfer workshops during project performance at locations convenient to the majority of CODES grantees. The first meeting, to be scheduled during the ninth or tenth month of funding, will be organized to share data linkage experiences, discuss standardized formats for management reports, review the proposed state-specific highway safety applications of linked data, and resolve common problems. The second meeting will be scheduled approximately 12 months after first technical assistance meeting, at the end of the funding period, for the purpose of sharing results and making recommendations for future CODES projects. 
                </P>
                <P>
                    d. 
                    <E T="03">Attend National Meeting.</E>
                     At the direction of the COTR, Grantee shall attend one national Meeting to report on progress or results from their CODES project. 
                </P>
                <P>
                    e. 
                    <E T="03">Progress Report.</E>
                     Grantee shall submit quarterly progress reports. During the period of performance, the grantee will provide letter-type written reports to the COTR. These reports will compare what was proposed in the Action Plan with actual accomplishments during the past quarter; what commitments have been generated; what follow up and state-level support is expected; what problems have been experienced and what may be needed to overcome the problems; and what is specifically planned to be accomplished during the next quarter. These reports will be submitted seven days after the end of each quarter. 
                </P>
                <P>f. Develop a plan to institutionalize the data linkage and applications for linked data after Federal funding ends. By the end of the 15th month of funding, each grantee shall submit a long-range plan and schedule to institutionalize data linkage and the use of linked data for highway safety and injury control decision-making within the state. </P>
                <P>
                    g. 
                    <E T="03">Project Report.</E>
                     The grantee shall deliver to NHTSA, at the end of the project, a final report describing the results of the data linkage process, and the applications of the linked data generated during the project. 
                </P>
                <HD SOURCE="HD2">NHTSA Involvement </HD>
                <P>NHTSA will be involved in all activities undertaken as part of the Cooperative Agreement program and will: </P>
                <P>1. Provide a Contracting Officer's Technical Representative (COTR) to participate in the planning and management of the Cooperative Agreement and coordinate activities between the grantee and NHTSA. </P>
                <P>2. Provide, at no cost to the grantee, training and technical assistance by a CODES expert for up to two weeks on-site and off-site during the project to assist the grantee in preparing the files for linkage, implementing probabilistic linkage techniques, validating the linkage results, developing applications for the linked data, and organizing the CODES Board of Directors and Advisory Group. </P>
                <P>3. Develop a format in which the linked data and supporting documentation will be delivered to NHTSA. </P>
                <P>4. Conduct Initial Briefing at NHTSA Headquarters in Washington, DC. (Date and time to be scheduled within 30 days after the award.) The purpose of the meeting will be to review the goals and objectives of the project, discuss implementation of the linkage software, identify the tasks to be specified in the action plan for the data linkage and applications of the linked data for highway safety or injury control decision-making, and discuss agendas for the Board of Directors and Advisory Group. </P>
                <P>5. Conduct two Technical Assistance meetings for the purpose of technology transfer. The first meeting, to be scheduled during the ninth or tenth month of funding, will be organized to share data linkage experiences, develop a standardized format for management reports, review the proposed state-specific highway traffic safety applications of linked data, and resolve common problems. The second meeting will be scheduled at the end of the funding period for the purpose of sharing results and making recommendations for future CODES projects. Locations for the Workshops will be determined based on the location of the Grantees. However, for the purpose of cost estimation, assume the workshops will be held in Washington, DC. </P>
                <P>6. Collaboratively work with the state when using the state's linked data to analyze and report on specific highway safety issues. </P>
                <P>7. When appropriate, NHTSA will publish state-specific reports on CODES applications. </P>
                <HD SOURCE="HD2">Period of Support </HD>
                <P>The project study effort described in this announcement will be supported through the award of up to four (4) Cooperative Agreements, depending upon the merit of the applications received and the availability of funding. It is anticipated that individual award amounts will range from $250,000-$300,000. Project efforts involving linkage of the state/area-wide data and applications for the linked data must be completed within twenty-one months after funding. </P>
                <HD SOURCE="HD2">Eligibility Requirements </HD>
                <P>The grantee must be a state agency involved with highway traffic safety, such as a State Highway Safety Office, Department of Transportation or other State agency with demonstrated activities in the highway traffic safety areas, to ensure active involvement by highway traffic safety stakeholders. States that have previously been funded to develop CODES are not eligible. Only one application should be submitted for a state/area. Because this Cooperative Agreement program requires extensive collaboration among the data owners in order to achieve the program objectives, it is envisioned that the grantee agency may need to actively involve the data owners in the development of the formal application and may need to sub-contract activities with at least one of them to implement a successful CODES. </P>
                <P>
                    While the general eligibility requirements are broad, applicants are advised that this Cooperative Agreement program is not designed to support basic developmental efforts. Although no single organization within any state/area has all of the required data capabilities, the application should demonstrate strong collaborative agreements with the data owners and access to at least the state/area-wide crash, hospital, and either EMS or emergency department data, or both, by the time of the award. States/areas that collect at least the date of birth and zip code of residence on their crash data and have state/area-wide health and/or vehicle insurance claims information may be eligible, in 
                    <PRTPAGE P="33873"/>
                    spite of the lack of EMS or emergency department information, if the claims data include everyone involved in motor vehicle crashes. In addition, it is important that the applicant indicate the level of commitment, with state/area funding and/or shared resources, by the data owners to meet program objectives, particularly institutionalization of the data linkage and applications for linked data. 
                </P>
                <HD SOURCE="HD1">Application Procedure </HD>
                <P>Each applicant must submit one original and two (2) copies of the application package to: DOT/National Highway Traffic Safety Administration, Office of Contracts and Procurement (NAD-30), ATTN: Lamont O. Norwood/Mark Kromer, 400 7th Street, SW., Room 5301, Washington, DC 20590. Applications must be typed on one side of the page only. An additional two (2) copies will facilitate the review process, but are not required. Applications must include a reference to NHTSA Cooperative Agreement Program No. DTNH22-00-H-07212. Only complete application packages received on or before 2 p.m. on July 24, 2000 will be considered. </P>
                <HD SOURCE="HD2">Application Contents </HD>
                <P>1. The application package must be submitted with OMB Standard Form 424 (REV. 7-97, including 424A and 424B), Application for Federal Assistance, with the required information filled in and assurances signed (SF 424B). While the Form 424A deals with budget information and Section B identifies Budget Categories, the available space does not permit a level of detail which is sufficient to provide for a meaningful evaluation of the proposed total costs. A supplemental sheet shall be provided which presents a detailed breakdown of the proposed costs (direct labor, including labor category, level of effort, and rate; direct materials including itemized equipment; travel and transportation, including projected trips and number of people traveling; subcontractors/subgrants, with similar detail, if known; and overhead), as well as any costs the applicant proposes to contribute or obtain from other sources in support of the project. Applicants shall assume that awards will be made during September 2000 and should prepare their applications accordingly. </P>
                <P>2. The application shall include a program narrative statement of not more than 20 pages, which addresses the following as a minimum: </P>
                <P>a. A brief description of the state/area in terms of its highway safety and injury control decision-making processes for planning, performance monitoring and other functions aimed at reducing death, injury, and costs of injuries resulting from motor vehicle crashes. This description should indicate how linked data will make a difference to the decision-making processes. </P>
                <P>
                    b. A brief description of the existing crash and medical outcome data files. Applicants will link state/area-wide population-based crash data to EMS (and/or emergency department or insurance claims) and hospital discharge data to obtain medical and financial outcomes for persons injured in motor vehicle crashes for any two calendar years of data available since 1996. Linkages to census, other traffic records (vehicle registration, driver licensing, roadway, conviction/citation, 
                    <E T="03">etc.</E>
                    ), insurance claims, 
                    <E T="03">etc.,</E>
                     are encouraged to meet priorities for highway safety and injury control decision-making. The following information should be included describing the state/area-wide data: 
                </P>
                <P>(1) The total crashes, total persons involved in crashes, total victims with injuries caused by a motor vehicle crash as identified or estimated and a descriptive profile of the total injuries by severity level, if available, state/area-wide. </P>
                <P>(2) Information about the current status of the data files to be linked, recorded using the format below: </P>
                <GPOTABLE COLS="7" OPTS="L2,tp0,i1" CDEF="s40,r50,r50,r75,r100,r50,r75">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Data files </CHED>
                        <CHED H="1">Reporting threshold (A)</CHED>
                        <CHED H="1">Rate of compliance with (A) </CHED>
                        <CHED H="1">Data years to be linked (19XX-19XX) </CHED>
                        <CHED H="1">Month and year when most recent data year will become available </CHED>
                        <CHED H="1">Percent of records computerized </CHED>
                        <CHED H="1">Can remaining records be computerized? (Y/N) </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Crash </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EMS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ED</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hospital </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Other </ENT>
                    </ROW>
                </GPOTABLE>
                <P>(3) The data elements chosen to identify persons and crashes and, for each, the missing data rate. </P>
                <P>(4) The data elements indicating type of injury, severity of injury, total charges, a payer source and, for each, the missing data rate. </P>
                <P>c. A brief description of the proposed sequence for linking the data files. </P>
                <P>d. A brief description of how staff from the various data owners will be cross-trained in the CODES linkage to compensate for potential future changes in organizational priorities and personnel. </P>
                <P>e. A brief description of the process to be used to ensure adequate documentation of the data files and linkage process. </P>
                <P>f. A brief description of how the linked data will be converted into information useful for the highway safety and injury control decision-making processes for the purpose of reducing death, injury, and costs resulting from motor vehicle crashes. </P>
                <HD SOURCE="HD3">Describe: </HD>
                <P>(1) The different types of decision-making processes, currently being utilized in the state/area, that identify highway traffic safety and injury control objectives and prioritize prevention programs that have the most impact on reducing death, injury and direct medical costs associated with motor vehicle crashes; and </P>
                <P>(2) Why linked data are needed to make these decision-making processes more effective and how the data will be incorporated. </P>
                <P>g. A brief description of each member of the CODES Board of Directors and the proposed arrangements describing the management and use of the linked data. </P>
                <P>3. The application shall include an appendix. A large appendix is strongly discouraged. Additional material should be included only if it is necessary to support information about data linkage, applications for linked data or institutionalization discussed in the application. Do not send copies of brochures, documents, etc., developed as the result of a collaborative effort in the state/area. The appendix should include the following: </P>
                <P>
                    a. Letters of support from each proposed member of the CODES Board of Directors. A letter of support should reflect the signer's level of commitment to the CODES project and thus should not be a form letter. The letter of support should document: 
                    <PRTPAGE P="33874"/>
                </P>
                <P>(1) Why linked data are important to the agency. </P>
                <P>(2) The priority assigned by the agency to obtain linked data compared to other responsibilities. </P>
                <P>(3) The agency's level of commitment in terms of the number of staff and the dollars or shared resources which will be available to support and institutionalize CODES. </P>
                <P>(4) The agency's willingness to collaborate with other data owners to support shared ownership of the linked data. </P>
                <P>(5) The agency's permission to release the linked data (or description of policies which would restrict transfer) to NHTSA at the end of the project. </P>
                <P>b. A brief description or letters of support should be included for the other stakeholders to be represented on the CODES Advisory Group. The letters of support should indicate the stakeholder's need for the linked data, and willingness to facilitate the linkage of state/area-wide data or use of linked data for decision-making. </P>
                <P>c. A list of activities in chronological order and a time line to show the expected schedule of accomplishments and their target dates. </P>
                <P>d. Descriptions of the proposed project personnel as follows: </P>
                <P>(1) Project Director: Include a resume along with a description of the director's leadership capabilities to make the various stakeholders work together. </P>
                <P>(2) Key personnel proposed for the data linkage and applications of linked data, and other personnel considered critical to the successful accomplishment of this project: include a brief description of qualifications, employment status (permanent, temporary) in the organization, and respective organizational responsibilities. The proposed level of effort in performing the various activities should also be identified. </P>
                <P>e. A brief description of the applicant's organizational experience in performing similar or related efforts, and the priority that will be assigned to this project compared to the organization's other responsibilities. </P>
                <P>f. A brief description of any potential delays in implementing the project because of requirements for legislative approval before CODES funds can be expended. </P>
                <P>
                    g. 
                    <E T="03">Data Use Agreement.</E>
                     A description of the existing State laws and regulations governing patient/provider confidentiality in the data files being linked that would restrict use of the data for linkage and/or for transfer of the CODES linked data to NHTSA and conditions under which the linked data file may be used by NHTSA. 
                </P>
                <HD SOURCE="HD2">Application Review Process and Evaluation Factors </HD>
                <P>Initially, all application packages will be reviewed to confirm that the applicant is an eligible recipient and to ensure that the application contains all of the items specified in the Application Content section of this announcement. Each complete application from an eligible recipient will then be evaluated by an Evaluation committee. The applications will be evaluated using the following criteria which are listed in descending order of importance: </P>
                <P>
                    1. 
                    <E T="03">Understanding the intent of the program</E>
                     (30%). The applicant's recognition of the importance of CODES to obtain medical and financial outcome data which are necessary for a comprehensive evaluation of the impact of highway safety and injury control countermeasures. The applicant's understanding of the importance of developing CODES as a meaningful and appropriate strategy for improving traffic records capabilities and ensuring the continuation of CODES after completion of this project. 
                </P>
                <P>
                    2. 
                    <E T="03">Technical approach for project completion</E>
                     (30%). The reasonableness and feasibility of the applicant's approach for successfully achieving the objectives of the project within the required time frame. The appropriateness and feasibility of the applicant's proposed plans for data linkage and applications for the linked data. Evidence that the applicant has the necessary authorization and support from data owners to access medical and non-medical state/area-wide data, particularly total charges and information about type and severity of injury, which are not routinely available for highway safety analyses and the necessary authorization to data. 
                </P>
                <P>
                    3. 
                    <E T="03">Project personnel</E>
                     (20%). The adequacy of the proposed personnel to successfully perform the project study, including qualifications and experience (both general and project related), the various disciplines represented, and the relative level of effort proposed for the professional, technical and support staff. 
                </P>
                <P>
                    4. 
                    <E T="03">Organizational capabilities</E>
                     (20%). The adequacy of organizational resources and experience to successfully manage and perform the project, particularly to support the collaborative network and respond to the increasing demand for access to the linked data. The proposed coordination with and use of other organizational support and resources, including other sources of financial support. 
                </P>
                <P>Depending upon the results of the evaluation process, NHTSA may choose to alter the number of awards. In addition, NHTSA may suggest revisions to applications as a condition of further consideration to ensure the most efficient and effective performance consistent with the objectives of the project. An organizational representative of the National Association of Governors' Highway Safety Representatives will be assisting in NHTSA's technical evaluation process. </P>
                <HD SOURCE="HD2">Special Award Selection Factors </HD>
                <P>After evaluating all applications received, in the event that insufficient funds are available to award to all meritorious applicants, NHTSA may consider the following special award factors in the award decision: </P>
                <P>1. Priority may be given to those applicants that have statewide data available for linkage. </P>
                <P>2. Priority may be given to applicants who have the highest probability of maintaining the collaborative network of data owners and users, of institutionalizing the linkage of the crash and medical outcome data on a routine basis, and of continuing to respond to data requests after the project is completed. </P>
                <P>3. Priority may be given to an applicant on the basis that the application fits a profile of providing NHTSA with a broad range of population densities (rural through metropolitan) with different highway safety needs. </P>
                <HD SOURCE="HD2">Terms and Conditions of the Award </HD>
                <P>1. Prior to award, each grantee must comply with the certification requirements of 49 CFR part 20, Department of Transportation New Restrictions on Lobbying, and 49 CFR part 29, Department of Transportation Government-wide Debarment and Suspension (Non-procurement) and Government-wide Requirements for Drug Free Workplace (Grants). In addition, grantees must certify that data release agreements have been signed by the owners of the data files being linked to transfer the CODES linked database to NHTSA, according to NHTSA specifications. </P>
                <P>2. Reporting Requirements and Deliverables: </P>
                <P>
                    a. 
                    <E T="03">Detailed Action Plan and Schedule.</E>
                     Within 30 days after the briefing meeting, the grantee shall deliver a detailed action plan and schedule for accomplishing the data linkage and applications of linked data for decision-making, showing any revisions to the approach proposed in the grantee's application. This detailed action plan will be subject to the technical direction 
                    <PRTPAGE P="33875"/>
                    and approval of NHTSA and will describe the following: 
                </P>
                <P>(1) The personnel and hardware resources required to perform the data linkage. </P>
                <P>(2) The process for obtaining the different files required for linkage. </P>
                <P>(3) The process for accelerating the data processing schedule, if necessary, so that the state/area-wide data are available in a timely manner for the linkage. </P>
                <P>(4) The process for verifying the data and performing additional edits on the linkage variables. </P>
                <P>(5) The process for resolving problems expected during linkage and their proposed solutions. </P>
                <P>(6) The process for documenting the content of the various linked data files, programs used for editing, and the linkage process itself. </P>
                <P>(7) The milestones for completing the various phases of the probabilistic linkage and validation processes. </P>
                <P>(8) The milestones for proposed meeting schedules and actions by the Board of Directors and Advisory Group. </P>
                <P>(9) Date(s) for providing the linked data to NHTSA. </P>
                <P>(10) The process for identifying the limitations of the final linked database or applications of the linked data, if any. </P>
                <P>(11) The process for ensuring access to the linked data as demand for information increases. </P>
                <P>(12) The process for choosing those applications of linked data that will have the most impact on reducing death, injury, and costs of injuries related to motor vehicle crashes. </P>
                <P>(13) The milestones for implementing the applications. </P>
                <P>(14) The benefits expected from the applications of the linked data. </P>
                <P>
                    b. 
                    <E T="03">Quarterly Progress Report.</E>
                     During the performance, the grantee will provide letter-type written reports to the NHTSA COTR. These reports will compare what was proposed in the Plan of Action with actual accomplishments during the past quarter; what commitments have been generated; what follow-up and state-level support is expected; what problems have been experienced and what may be needed to overcome the problems; and what is specifically planned to be accomplished during the next quarter. These reports will be submitted seven days after the end of each quarter. 
                </P>
                <P>
                    c. 
                    <E T="03">Board of Directors and Advisory Group Meetings.</E>
                     Copies of the agenda and minutes for each Board of Directors and Advisory Group Meeting will be attached to the Progress Report submitted to NHTSA immediately following the meeting. 
                </P>
                <P>
                    d. 
                    <E T="03">Institutionalization Plan.</E>
                     The grantee shall deliver to NHTSA, by the end of the 15th month of funding, a long-range plan and schedule to institutionalize data linkage and the use of linked data for highway safety and injury control decision-making within the state. 
                </P>
                <P>
                    e. 
                    <E T="03">Project Report.</E>
                     The grantee shall deliver to NHTSA, at the end of the project, a final report describing the results of the data linkage process, and the applications of the linked data. The report shall include the following: 
                </P>
                <P>(1) A description of the state/area wide linked crash and injury data; </P>
                <P>(2) A description of the file preparation; </P>
                <P>(3) A description of the linkage, validation processes and results; </P>
                <P>(4) A description of the extent of the documentation and how the documentation will facilitate linkage in subsequent years; </P>
                <P>(5) A discussion of the limitations of the linked data and subsequent applications of these data; </P>
                <P>(6) A description of the applications of linked data implemented for decision-making and results of the decision-making; </P>
                <P>(7) A description of how the data linkage and use of linked data for decision making has been institutionalized for decision-making; </P>
                <P>(8) A description of the documentation created to facilitate repeating of the linkage process and an estimate of how much time is needed to repeat the linkage in subsequent years; </P>
                <P>(9) A copy of the public-use formats that were successful for incorporating linked data into the decision-making processes for highway safety and injury control; and </P>
                <P>(10) A copy of the management reports prepared using the standardized format for the national CODES report. </P>
                <P>
                    f. 
                    <E T="03">CODES Linked Database.</E>
                     The grantee shall deliver to NHTSA after linkage, at the date specified in the Action Plan, the CODES linked databases. NHTSA will use the data to help facilitate the development of data linkage capabilities at the state/area-wide level and to encourage use of the linked data for decision making. 
                </P>
                <P>The deliverables will include: </P>
                <P>(1) The database in an electronic media and format acceptable to NHTSA, including all persons, regardless of injury severity (none, fatal, non-fatal), involved in a reported motor vehicle crash for any two calendar years of available data since 1996, and including medical and financial outcome information for those who are linked. </P>
                <P>(2) A copy of the file structure for the linked data file. </P>
                <P>(3) Documentation of the definitions and file structure for each of the data elements contained in the linked data files. </P>
                <P>(4) An analysis of the quality of the linked data and a description of any data bias which may exist based on an analysis of the false positive and false negative linked records. </P>
                <P>3. During the effective performance period of Cooperative Agreements awarded as a result of this announcement, the agreement as applicable to the grantee shall be subject to the National Highway Traffic Safety Administration's General Provisions for Assistance Agreements, dated July 1995. </P>
                <SIG>
                    <DATED>Issued: May 19, 2000. </DATED>
                    <NAME>Joseph Kanianthra, </NAME>
                    <TITLE>Acting Associate Administrator for Research and Development, National Highway Traffic Safety Administration. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13100 Filed 5-24-00; 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>
                <SUBJECT>Discretionary Incentive Grants To Support Increased Seat Belt Use Rates </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Announcement of discretionary grants to support innovative projects designed to increase seat belt use rates. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Highway Traffic Safety Administration (NHTSA) announces the second year of a discretionary grant program under Section 1403 of the Transportation Equity Act for the 21st Century (TEA-21) to provide funding to States for innovative projects to increase seat belt use rates. Consistent with last year, the goal of this program is to increase seat belt use rates across the nation in order to reduce the deaths, injuries, and societal costs that result from motor vehicle crashes. This notice solicits applications from the States, the District of Columbia and Puerto Rico, through their Governors' Representatives for Highway Safety, for funds to be made available in FY 2001. Detailed application instructions are provided in the Application Contents section of this Notice. The Section 157 Innovative grants will be awarded competitively based upon the evaluation results of the applications received. Detailed information on the evaluation criteria is provided in the Application Review Procedures and Evaluation Criteria section of this Notice. </P>
                </SUM>
                <DATES>
                    <PRTPAGE P="33876"/>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applications must be received by the office designated below on or before July 26, 2000. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Applications must be submitted to the National Highway Traffic Safety Administration, Office of Contracts and Procurement (NAD-30), ATTN: Amy Poling, 400 7th Street, SW, Room 5301, Washington, DC 20590. All applications submitted must include a reference to NHTSA Grant Program No. DTNH22-00-G-09200 </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>General administrative questions may be directed to Amy Poling, Office of Contracts and Procurement by e-mail at apoling@nhtsa.dot.gov. or by phone at (202) 366-9552. Programmatic questions relating to this grant program should be directed to Philip Gulak, Occupant Protection Division (NTS-12), NHTSA, 400 7th Street, SW, Room 5118, Washington, DC 20590, by e-mail at pgulak@nhtsa.dot.gov, or by phone at (202) 366-2708. Interested applicants are advised that no separate application package exists beyond the contents of this announcement. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>The Transportation Equity Act for the 21st Century (TEA-21), Pub.L. 105-178, was enacted on June 9, 1998. Section 1403 of TEA-21 contained a safety incentive grant program for use of seat belts. Under this program, funds are allocated each fiscal year from 1999 until 2003 to States that exceed the national average seat belt use rate or that improve their State seat belt use rate, based on certain required determinations and findings. Section 1403 provided that, beginning in fiscal year 2000, any funds remaining unallocated in a fiscal year after the determinations and findings related to seat belt use rates have been made are to be used to “make allocations to States to carry out innovative projects to promote increased seat belt use rates.” Today's notice solicits applications for funds that will become available in fiscal year 2001 under this latter provision. </P>
                <P>TEA-21 imposes several requirements under the innovative projects funding provision. Specifically, in order to be eligible to receive an allocation, a State must develop a plan for innovative projects to promote increased seat belt use rates and submit the plan to the Secretary of Transportation (by delegation, to NHTSA). NHTSA was directed to establish criteria governing the selection of State plans that are to receive allocations and was further directed to “ensure, to the maximum extent practicable, demographic and geographic diversity and a diversity of seat belt use rates among the States selected for allocations.” Finally, subject to the availability of funds, TEA-21 provides that the amount of each grant under a State plan is to be not less than $100,000. </P>
                <P>In the following sections, the agency describes the application and award procedures for receipt of funds under this provision, including requirements related to the contents of a State's plan for innovative projects and the criteria the agency will use to evaluate State plans and make selections for award. To assist the States in formulating plans that meet these criteria, we have provided an extensive discussion of strategies for increasing seat belt use and of the ways in which States might demonstrate innovation. Please refer to the Appendix at the end of this Notice for additional background information about strategies that have been used in the past to increase belt use. </P>
                <HD SOURCE="HD1">Objective of This Grant Program </HD>
                <P>The objective of this grant program is to increase State seat belt use rates, for both adults and children, by supporting the implementation of innovative projects that build upon strategies known to be effective in increasing seat belt use rates. Because one of the best ways to ensure that children develop a habit of buckling up is for parents to properly restrain them in child safety seats, efforts to increase the use of child safety seats, in addition to seat belts, may be included among the innovative efforts in a State's plan. However, efforts to increase seat belt use rates must remain the focus of the State's plan. </P>
                <HD SOURCE="HD1">Examples of Effective Innovative Strategies </HD>
                <P>Recent seat belt use increases in California, North Carolina, Louisiana, Georgia, Maryland, and the District of Columbia (see discussion in next section), as well as increases following national mobilizations, have demonstrated the tremendous potential of highly visible enforcement of strong laws to increase seat belt and child seat use. Given the dramatic results of these programs, NHTSA believes that highly visible enforcement is an important foundation upon which any effective program should be based. An extensive review of the efforts in both the United States and Canada demonstrates that, without a core of highly visible enforcement efforts, high usage rates have not been achieved in any major jurisdiction. </P>
                <P>In view of these findings, to be considered for award of funds under this program, the State's innovative project plan should be based on a core component of highly visible enforcement of its seat belt use law with the clear intent of increasing the State's seat belt use rate. A proposal to increase seat belt use in only a limited number of jurisdictions, that would have a questionable impact on the overall state seat belt use rate, may be rejected during the evaluation process. Other components of the plan should support the core enforcement component. If a State is already pursuing a significant and visible enforcement effort, the innovative project plan should detail components that support, expand, or complement the existing enforcement effort. States submitting an innovative project plan with a core component (and supporting components) based on an approach other than enforcement should provide a strong rationale for the proposed approach, preferably accompanied by research evidence, demonstrating the significant potential for increasing the State's seat belt use rate. NHTSA will carefully consider this rationale in its evaluation of the proposal. </P>
                <P>
                    A State may demonstrate innovation in its enforcement efforts in a number of ways. If a State is not currently engaged in any form of highly visible enforcement of its occupant protection laws, implementation of such a program, in and of itself, would be innovative to that State. Additionally, innovation may be demonstrated in gaining essential support, implementing statewide training programs, and planning the logistics for wide scale enforcement supported by public information activities. For States that already are engaged in substantial enforcement efforts, innovation can be demonstrated by expanding these efforts. This might include finding more effective ways to reach rural, urban, or diverse groups with strategies designed to address the problem of low seat belt use among those groups. States that have upgraded their laws recently to allow for primary enforcement may wish to initiate innovative ways to implement, enforce, and publicize their newly enacted legislation. For States with secondary enforcement laws, where a motorist must be stopped for another offense before being cited for failure to buckle up, innovation may be demonstrated by integrating the enforcement of the seat belt law with enforcement of another traffic safety law (
                    <E T="03">e.g.,</E>
                     an alcohol impaired driving law). Many opportunities for innovation exist, regardless of the State's current seat belt 
                    <PRTPAGE P="33877"/>
                    use rate or its ongoing efforts to increase it. 
                </P>
                <P>Following are some examples of innovative activities in support of a core component of enforcement:</P>
                <FP SOURCE="FP-1">—Initiate, or expand in novel ways, the operation of existing State or local enforcement-related campaigns; </FP>
                <FP SOURCE="FP-1">—Implement highly visible seat belt and child safety seat enforcement efforts in major urban areas, in rural areas, or throughout the State; </FP>
                <FP SOURCE="FP-1">
                    —Expand participation across the State in semi-annual national seat belt enforcement mobilizations (
                    <E T="03">i.e.,</E>
                     Operation ABC conducted in May and November); 
                </FP>
                <FP SOURCE="FP-1">—Plan and support efforts to train and motivate law enforcement officers, prosecutors and judges to consistently enforce, prosecute and adjudicate occupant protection law violations; </FP>
                <FP SOURCE="FP-1">—Mount a highly visible program to implement newly enacted legislation which upgrades the State's seat belt or child passenger safety law; </FP>
                <FP SOURCE="FP-1">—Initiate or expand public information and education programs designed to complement newly upgraded legislation and/or enhanced enforcement efforts; </FP>
                <FP SOURCE="FP-1">
                    —Establish new partnerships and coalitions to support ongoing implementation of legislation or enforcement efforts (
                    <E T="03">e.g.,</E>
                     health care and medical groups, partnerships with diverse groups, businesses and employers); 
                </FP>
                <FP SOURCE="FP-1">
                    —Initiate or expand public awareness campaigns targeted to specific populations that have low seat belt use (
                    <E T="03">e.g.,</E>
                     part-time users; parents of children 0-15 years old; minority populations, including Native Americans; rural communities; males 15-24 years old; occupants of light trucks and sport utility vehicles); 
                </FP>
                <FP SOURCE="FP-1">—Implement a program to train law enforcement personnel on the importance of seat belt use, the specifics of the State's seat belt use law, and the importance of enforcing such law to increase usage rates; </FP>
                <FP SOURCE="FP-1">
                    —Initiate or expand standardized child passenger safety training of police officers and/or child passenger safety checks and/or clinics across broad geographical areas (
                    <E T="03">e.g.,</E>
                     statewide, in major metropolitan areas, in rural areas of the State); 
                </FP>
                <FP SOURCE="FP-1">
                    —Initiate, or expand in novel ways, campaigns which use enforcement of other traffic laws (
                    <E T="03">e.g.,</E>
                     driving while intoxicated laws) as a means for implementing highly visible enforcement of seat belt use laws. 
                </FP>
                <P>If a State wishes to submit a plan proposing a core component other than enforcement, it should demonstrate innovation by proposing to perform supporting activities similar in scope to those listed above. The State should demonstrate that the proposed activities have the potential to increase the State's seat belt use rate.</P>
                <HD SOURCE="HD1">Self-Evaluations of Programs, Management and Resources </HD>
                <P>Meaningful and timely self-evaluations of each State's innovative programs, management, and associated resources are very important to improving programs in subsequent years. On an annual basis, grantees and NHTSA need to generate the most useful insights and most valuable lessons possible from the 157 program. Consequently, program evaluation will be a necessary component of each award (see Application Contents, Section C.2.e.). </P>
                <HD SOURCE="HD1">NHTSA Involvement </HD>
                <P>In support of the activities undertaken by this grant program, NHTSA will: </P>
                <P>1. Provide a Contracting Officer's Technical Representative (COTR) to coordinate activities between the Grantee and NHTSA during grant performance, and to serve as a liaison between NHTSA Headquarters, NHTSA Regional offices and the grantee. </P>
                <P>2. Provide information and technical assistance from government sources within available resources and as determined appropriate by the COTR. </P>
                <HD SOURCE="HD1">Availability of Funds and Period of Support </HD>
                <P>The efforts solicited in this announcement will be supported through the award of grants to a number of States, on the basis of the evaluation criteria identified below. The number of grants awarded will depend upon the merits of the applications received, the amount of funds available in fiscal year 2001, and the size of the grants awarded to individual States. The total amount of funds to be made available is not known at this time, as it is dependent upon appropriations by the Congress and the amount of allocations to States based on State seat belt use rates achieved (see discussion in Background section, above). However, the agency estimates that as much as $25-$30 million may become available for this program in fiscal year 2001. </P>
                <P>In accordance with TEA-21, the minimum amount of an individual grant award to a State will be $100,000, subject to the availability of funds. However, NHTSA may make individual awards in amounts significantly greater than $100,000, subject to the availability of funds and consistent with the merits of a State's application. In fiscal year 2000, forty-six Innovative grants were awarded. Those grants ranged from $121,500 to $1,557,608. At this time, neither the exact amount of funds available nor the number and proposed costs of meritorious State applications can be determined. There is no assurance that the number of grant awards in FY 2001 will be the same or similar to the number of awards in FY 2000, nor is there any assurance that those States that received awards in FY 2000 will receive awards in FY 2001. In addition, NHTSA may choose to fund an entire plan, or portions of a plan or it may choose to reject a plan, after review based on the evaluation criteria. There is no cost-sharing requirement under this program. The period of support for a grant under this program will be a total of 15 months, with 12 months of plan implementation, and three months for evaluation and preparation of the annual report. </P>
                <P>NHTSA estimates that the award of Section 157 Innovative Grants for fiscal year 2001 will occur during January 2001. </P>
                <HD SOURCE="HD1">Allowable Uses of Federal Funds </HD>
                <P>Allowable uses of Federal funds shall be governed by the relevant allowable cost section and cost principles referenced in 49 CFR part 18—Department of Transportation Uniform Administrative Requirements for Grants and Cooperative Agreements to State and Local Governments. Funds provided to a State under this grant program shall be used to carry out the activities described in the State's plan for which the grant is awarded. </P>
                <HD SOURCE="HD1">Eligibility Requirements </HD>
                <P>Only the 50 States, the District of Columbia, and Puerto Rico, through their Governors' Representatives for Highway Safety, will be considered eligible to receive funding under this grant program. </P>
                <HD SOURCE="HD1">Application Procedures </HD>
                <P>Each applicant must submit one original and two copies of the application package to: NHTSA, Office of Contracts and Procurement (NAD-30), ATTN: Amy Poling, 400 7th Street, SW, Room 5301, Washington, DC 20590. An additional three copies will facilitate the review process, but are not required. </P>
                <P>
                    Applications must be typed on one side of the page only. Applications must include a reference to NHTSA Grant Program No. DTNH22-00-G-09200. Only complete application packages submitted by a State's Governor's Representative for Highway Safety on or before July 26, 2000 will be considered. 
                    <PRTPAGE P="33878"/>
                </P>
                <HD SOURCE="HD1">Application Contents </HD>
                <P>This year, the required contents of each State's application will be based upon the State's application and award results for FY 2000 under this grant program. </P>
                <P>A. If a State received an award based on a one-year proposal and would like to continue the same or similar work, it may submit an updated or modified version of that proposal. The State is encouraged to modify or strengthen its proposal as appropriate to increase its effectiveness in raising its seat belt use rate. An evaluation component must be included. A Continuation Application using the SF 424 must be submitted which confirms that the same effort will be continued, or indicates what changes are proposed, along with the itemized budget for the proposed effort. </P>
                <P>B. If a State received an award based on a proposal that requested funding for several years, and the State wishes to continue the same effort, the State need only re-submit the part of its proposal (or a modified version of such), that relates to FY 2001. The State is encouraged to modify or strengthen its proposal to increase its effectiveness in raising its seat belt use rate. An evaluation component must be included. If there are any changes, additions, or deletions to the original scope of work identified and budgeted for the second year, a Continuation Application using the SF 424 must be submitted which provides a narrative explanation of the proposed differences, along with an itemized budget for the proposed effort. </P>
                <P>C. If a State is applying for the first time, or if a State applied and did not receive an award in FY 2000, or if the State is proposing a completely new effort, the State must include in its application all of the contents listed below:</P>
                <P>l. The application package must be submitted with OMB Standard Form 424, (Rev. 7-97 or 4-88, including 424A and 424B), Application for Federal Assistance, with the required information provided and the certified assurances included. While the Form 424-A deals with budget information, and section B identifies Budget Categories, the available space does not permit a level of detail which is sufficient to provide for a meaningful evaluation of the proposed costs. A supplemental sheet should be provided which presents a detailed breakdown of the proposed total project effort, including evaluation and reporting, (direct labor, including labor category, level of effort, and rate; direct materials, including itemized equipment; travel and transportation, including projected trips and number of people traveling; subcontracts/subgrants, with similar detail, if known; and overhead). and costs the applicant proposes to contribute or obtain from other sources in support of the projects in the innovative project plan. </P>
                <P>2. All applications shall include a State plan detailing innovative projects to increase seat belt use rates. The State plan must provide the following information:</P>
                <P>a. An Introduction section with a brief general description of the State's population density, any unique population characteristics, a short summary of the status of the seat belt use law in the State, and the pattern of estimated seat belt use rates for the State.</P>
                <P>b. A Discussion section that presents the principal goals and objectives of the proposed plan and articulates the potential to increase State seat belt use rates, with supporting rationale. This section should also identify any proposed partnerships, coalitions, or leveraging of resources that will be employed as a means to implement a comprehensive and significant enforcement effort, as well as public information or educational activities. Any known barriers to implementation of the State's plan should be identified, with a discussion of how such barriers will be overcome. Relevant data based on studies of the program should be included or footnoted. Supporting documentation from concerned interests other than the applicant may be included.</P>
                <P>
                    Documentation of existing public and/or political support may be included (
                    <E T="03">e.g.</E>
                     endorsement of the Governor, State Police or Patrol, State Association of Chiefs of Police, State Medical Society, etc).
                </P>
                <P>c. A Project Description section, with a detailed description of the innovative projects to be undertaken by the State under the plan, including, for each activity: </P>
                <P>
                    (1) the key strategies to be employed to achieve a significant seat belt use rate increase (
                    <E T="03">e.g.,</E>
                     enforcement, public information and education, training, incentive/reward efforts); 
                </P>
                <P>
                    (2) the innovative features (
                    <E T="03">e.g. </E>
                    new participants, expanded efforts, unique resources, design or technological innovations, reductions in cost or time, integration with existing State efforts, extraordinary community involvement); and 
                </P>
                <P>(3) a work plan listing milestones in chronological order to show the schedule of expected accomplishments and their target dates. For example, in a work plan based on an enforcement component, the State should provide the following information: </P>
                <P>A description of the proposed enforcement waves (if a sTEP-type enforcement activity is included in the State's proposal), detailing</P>
                <P>• The approximate dates when each wave will occur</P>
                <P>
                    • How long each wave will last (
                    <E T="03">i.e.</E>
                    , duration of actual intensified enforcement)
                </P>
                <P>• The number of law enforcement agencies that are expected to participate in each wave</P>
                <P>
                    • The approximate cumulative percentage of the State's population served by the participating 
                    <E T="03">local</E>
                     law enforcement agencies, and what affect this population could have on the State's seat belt use rate
                </P>
                <P>
                    • The kinds of law enforcement activities and strategies that will take place in each wave (
                    <E T="03">e.g.</E>
                    , checkpoints, saturation patrols, foot patrols at selected intersections, etc.)
                </P>
                <P>• The number of officers that will participate</P>
                <P>• The number of hours, on average, each officer will participate during each wave</P>
                <P>• The number of law enforcement contacts, on average, each officer is expected to make per hour during each wave</P>
                <P>• The percentage of these contacts, on average, that are expected to result in a citation for a seat belt or child passenger safety violation.</P>
                <P>A State that proposes a component other than enforcement should provide a similarly comprehensive work plan containing all relevant milestones.</P>
                <P>d. A Personnel section, which identifies the proposed program manager, key personnel and other proposed personnel considered critical to the successful accomplishment of the activities under the State's plan. A brief description of their qualifications and respective responsibilities shall be included. The proposed level of their effort and contributions to the various activities in the plan shall also be identified. Each organization, corporation, or consultant who will work on the innovative project plan shall be identified, along with a short description of the nature of the effort or contribution and relevant experience.</P>
                <P>
                    e. An Evaluation section, with a description of how the State will evaluate and measure the outcomes of the activities in its innovative project plan. It is critically important that the innovative programs funded as a result of this announcement be carefully evaluated so that others may learn the relative strengths and weaknesses of the 
                    <PRTPAGE P="33879"/>
                    strategies and approaches undertaken and what effects they have on seat belt use rates. The evaluation section should describe the methods for assessing actual results achieved under the plan. Outcomes can be documented in a number of ways. Increases in observed seat belt use and reductions in motor vehicle crash fatalities and injuries provide the ultimate measure of success. However, intermediate measures also may be used to measure progress. For a program based on an enforcement component, these measures may include: (i) Increases in the number of law enforcement personnel trained to enforce occupant protection laws; (ii) increased statewide participation in semi-annual enforcement mobilizations (Operation ABC); (iii) increased public perception of ongoing enforcement and public education activities; (iv) increased numbers of public and private sector partners involved in implementing the Statewide programs that support enforcement efforts; (v) the number of incentive programs, including those that complement enforcement efforts; or (vi) extent to which occupant protection enforcement activities are integrated with other State enforcement activities. Data sources should be identified, and collection and analysis approaches should be described. In particular, the State's proposal should describe how the State intends to assess the effectiveness of its project with respect to:
                </P>
                <P>• Seat belt use rates</P>
                <P>• Level of actual ticketing, other enforcement activities and activity to generate support for enforcement</P>
                <P>• Public awareness of ticketing and other enforcement efforts</P>
                <P>• Public support for seat belt and child passenger safety enforcement.</P>
                <P>• Encouraging specific enforcement-related media efforts</P>
                <P>For a program based on a component other than enforcement, the State should provide a similar level of detail in measuring progress and assessing outcomes.</P>
                <P>f. An Options section, in which the state may choose to propose either optional tasks or activities in addition to the core set of tasks or activities, or optional levels of effort. For either type of option, the State must include a separate budget which clearly delineates the costs associated with each optional task or level of effort. For example, a State may propose a project plan that includes five week-long enforcement waves with the annual project budget, as well as an optional level of effort for an additional sixth enforcement wave and its associated costs. Doing this will allow maximum flexibility in the amount of funding awarded to a State based on funds available. </P>
                <HD SOURCE="HD1">Application Review Procedures and Evaluation Criteria </HD>
                <P>Initially, all applications will be reviewed to confirm that the applicant is an eligible recipient and to ensure that the application contains all of the information required by the Application Contents section of the notice. Each complete application from an eligible recipient then will be evaluated by an Evaluation Committee. Incomplete applications will be rejected without further review. This evaluation includes a process of reviewing all grant applications; submitting technical, program and budget questions about the proposals to applicants, where necessary; reviewing answers to these questions; and engaging in negotiations where appropriate. This process is expected to extend over the course of several months, and applicants may expect correspondence of this nature throughout this time period. Using this process, the applications will be evaluated in accordance with the following criteria: </P>
                <P>
                    <E T="03">1. Evaluation Criterion 1 (80% of total score):</E>
                     The goal(s) the State proposes to achieve, as described in its innovative project plan. The overall soundness and feasibility of the plan for achieving the goal(s), and the potential effectiveness of the proposed activities in the plan for increasing the State's seat belt use rate. The extent to which the plan details a significant and comprehensive enforcement effort or, where another approach is selected, provides evidence supporting the effectiveness of the proposed approach. Regardless of method, the goal must be to increase the State's seat belt use rate. Under this first criterion, all applications will be evaluated using the following sub-factors: 
                </P>
                <P>(a) Is the State's plan sound and feasible to effectively achieve the stated goal(s) for increasing the State's seat belt use rate? </P>
                <P>(b) Does the plan detail a significant and comprehensive enforcement effort or, if another approach is proposed, is there evidence supporting the effectiveness of the approach? </P>
                <P>(c) Are the data collection methodologies and analytical approaches adequately described in the evaluation plan and will the plan effectively measure the outcomes of the proposed activities? </P>
                <P>
                    <E T="03">2. Evaluation Criterion 2 (20% of total score):</E>
                     The organizational resources the State will draw upon, and how the State will provide the program management capability and personnel expertise to successfully perform the activities in its innovative project plan. The adequacy of the proposed personnel (including subcontractor and subgrantee personnel) to successfully perform the proposed activities, including qualifications and experience, the various disciplines represented and the relative level of effort proposed for the professional, technical, and support staff, will be considered. 
                </P>
                <P>Each application will be reviewed and rated in accordance with the evaluation criteria outlined above. If an application receives a low rating, NHTSA may eliminate it from further consideration for award without discussions with an offeror. For applications that are not eliminated during this initial review, NHTSA may suggest revisions as a condition of further consideration, during the negotiation process described above, to ensure the most efficient and effective performance consistent with the objectives of achieving increased State seat belt use rates. It is anticipated that awards will be made in January 2001. </P>
                <HD SOURCE="HD1">Special Award Selection Factors </HD>
                <P>After evaluating all applications received, in the event that insufficient funds are available to award all requested amounts to all meritorious applicants, NHTSA may consider the following special award factors in the award decision: </P>
                <P>1. Every effort will be made to provide grants to a diverse group of States representing a broad range of geographic, demographic, and use rate characteristics. Thus, preference may be given to an applicant that fits the need for such diversity. </P>
                <P>2. Preference may be given to an applicant on the basis that its application is effectively integrated and coordinated with other ongoing efforts in the State, resulting in additional opportunity for immediately increasing seat belt use rates. This could include proposed cost-sharing strategies, and/or the use of other federal, State, local and private funding sources to complement those available under this announcement. </P>
                <HD SOURCE="HD1">Terms and Conditions of the Award </HD>
                <P>
                    1. Prior to award, each grantee must comply with the certification requirements of 49 CFR part 20, Department of Transportation New Restrictions on Lobbying, and 49 CFR part 29, Department of Transportation Government-wide Debarment and Suspension (Non-procurement) and Government-wide Requirements for Drug Free Workplace (Grants). 
                    <PRTPAGE P="33880"/>
                </P>
                <P>2. Reporting Requirements and Deliverables: </P>
                <P>a. Quarterly Progress Reports should include a summary of the previous quarter's enforcement and other activities and accomplishments, significant problems encountered or anticipated, a brief itemization of expenditures made during the quarter, and proposed activities for the upcoming quarter. Any decisions and actions required in the upcoming quarter should be included in the report. </P>
                <P>b. Draft Final Report: The grantee shall prepare a Draft Final Report that includes a complete description of the innovative projects conducted, including partners, overall program implementation, evaluation methodology and findings from the program evaluation. In terms of information transfer, it is important to know what worked and what did not work, under what circumstances, and what can be done to avoid potential problems in future projects. The grantee shall submit the Draft Final Report to the COTR 60 days prior to the end of the performance period. The COTR will review the draft report and provide comments to the grantee within 30 days of receipt of the document. </P>
                <P>c. Final Report: The grantee shall revise the Draft Final Report to reflect the COTR's comments. The revised final report shall be delivered to the COTR 15 days before the end of the performance period. The grantee shall supply the COTR : </P>
                <P>—A camera ready version of the document as printed. </P>
                <P>—A copy, on appropriate media (diskette, Syquest disk, etc.), of the document in the original program format that was used for the printing process. </P>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>Some documents require several different original program languages (e.g., PageMaker was the program format for the general layout and design and Power point was used for charts and yet another was used for photographs, etc.). Each of these component parts should be available on disk, properly labeled with the program format and the file names. For example, Power point files should be clearly identified by both a descriptive name and file name (e.g., 1994 Fatalities—chart1.ppt).</P>
                </NOTE>
                <P>—A complete version of the assembled document in portable document format (PDF) for placement of the report on the world wide web (WWW). This will be a file usually created with the Adobe Exchange program of the complete assembled document in the PDF format that will actually be placed on the WWW. The document would be completely assembled with all colors, charts, side bars, photographs, and graphics. This can be delivered to NHTSA on a standard 1.44 diskette (for small documents) or on any appropriate archival media (for large documents) such as a CD ROM, TR-1 Mini cartridge, Syquest disk, etc. </P>
                <P>—Four additional hard copies of the final document. </P>
                <P>3. During the effective performance period of grants awarded as a result of this announcement, the grant shall be subject to the National Highway Traffic Safety Administration's General Provisions for Assistance Agreements, dated July 1995. </P>
                <SIG>
                    <DATED>Issued on: May 19, 2000. </DATED>
                    <NAME>Rose A. McMurray, </NAME>
                    <TITLE>Associate Administrator for Traffic Safety Programs.</TITLE>
                </SIG>
                <EXTRACT>
                    <HD SOURCE="HD1">Appendix: Strategies That Have Proven Effective in Increasing Seat Belt Use </HD>
                    <P>Seat belts, when properly used, are 45 percent effective in preventing deaths in potentially fatal crashes and 50 percent effective in preventing serious injuries. No other safety device has as much potential for immediately preventing deaths and injuries in motor vehicle crashes. The current level of seat belt use across the nation prevents more than 9,500 deaths and well over 200,000 injuries annually. Through 1997, more than 100,000 deaths and an estimated 2.5 million serious injuries have been prevented by seat belt use. </P>
                    <P>But, seat belt use rates and the resulting savings could be much greater. As of 1999, the average use rate among States in the U.S. was still well below the goal of 85 percent announced by the President for the year 2000 and at least a dozen States have use rates below 60 percent. On the other hand, use rates of 85-95 percent are a reality in most developed nations with seat belt use laws, and at least six U.S. States and the District of Columbia achieved use rates greater than 80 percent in 1999. A national use rate of 90 percent (the President's goal for 2005), among front seat occupants of all passenger vehicles, would result in the prevention of an additional 5,500 deaths and 130,000 serious injuries annually. This would translate into a $9 billion reduction in societal costs, including $356 million for Medicare and Medicaid. </P>
                    <HD SOURCE="HD1">Effective Enforcement Based Strategies </HD>
                    <P>The history of efforts to increase seat belt use in the U.S. and in Canada suggests that highly visible enforcement of a strong seat belt law must be at the core of any effective program. No State has ever achieved a high seat belt use rate without such a component. Most States that have achieved rates greater than 70 percent have also had laws that allow for primary (standard) enforcement procedures. </P>
                    <P>Canada currently has a national seat belt use rate well above 90 percent. Nearly every province first attempted to increase seat belt use through voluntary approaches involving public information and education. These efforts were effective in achieving only very modest usage rates (no higher than 30 percent). Even the enactment of primary enforcement seat belt laws, without intense and highly visible enforcement, generally was not sufficient to achieve usage rates greater than 60-65 percent. By 1985, it became clear to Canadian and provincial officials that additional efforts would be needed to achieve levels of 80 percent or greater. These efforts, mounted from 1985 through 1995, centered around highly publicized “waves” of enforcement, a technique that had already been shown to increase seat belt use in Elmira, New York in 1985. When these procedures were implemented in the Canadian provinces, seat belt use generally increased from about 60 percent to well over 80 percent, within a period of 3-5 years. </P>
                    <P>The U.S. experience has been similar. Prior to 1980, many attempts were made to increase seat belt use through voluntary, persuasive, or educational methods. Most of these efforts were initiated at local, county, or state levels. Nationally, seat belt use remained very low, reaching only about 11 percent. From 1980-1984, efforts to increase seat belt use emphasized networking with various public and private groups to implement public education programs, incentives, and seat belt use policies. While there were some small gains documented in individual organizations, these efforts did not result in any significant increases in seat belt use in any large city or in any State. By the end of 1984, the national usage rate, as measured by a 19-city observational survey, was only about 15 percent. </P>
                    <P>In 1984, New York enacted the first mandatory seat belt use law and, from 1985 to 1990, at least 37 other States enacted such laws. Most of these laws were secondary enforcement laws that required an officer to observe another traffic violation before stopping and citing a driver for failure to wear a seat belt. During this period of time, the 19-city index of seat belt use increased from about 15 percent to nearly 50 percent. However, as was the case in Canada, the enactment of laws, by itself, was not sufficient to achieve high usage rates. </P>
                    <P>The Canadian successes using periodic, highly visible “waves” of enforcement, as well as scores of such efforts implemented in local jurisdictions in the U.S., prompted NHTSA to implement Operation Buckle Down (also called the “70 by ‘92” Program) in 1991. This two-year program focused on Special Traffic Enforcement Programs (STEPs) to increase seat belt use. It was followed by a national usage rate increase from about 53 percent in 1990 to 62 percent by the end of 1992 (as measured by a weighted aggregate of State surveys). Neither the level of enforcement nor its public visibility was uniform in every State. Had these “waves” of enforcement been implemented in a more uniform fashion in every State, the impact likely would have been much greater. </P>
                    <P>
                        In order to demonstrate the potential of periodic, highly visible enforcement in a more controlled environment, the State of North Carolina implemented its Click-It or Ticket program in 1993. In this program, 
                        <PRTPAGE P="33881"/>
                        waves of coordinated and highly publicized enforcement efforts (i.e., checkpoints) were implemented in every county. As a result, seat belt use increased statewide, from 65 percent to over 80 percent, in just a few months. This program provided the clearest possible evidence to demonstrate the potential of highly visible enforcement to increase seat belt use in a large jurisdiction (i.e, an entire State). 
                    </P>
                    <P>On the west coast, the State of California had expended much effort over the years to enforce its secondary enforcement law. These efforts were successful in increasing the statewide usage rate to about 70 percent, where it plateaued. In 1993, California became the first State to upgrade its seat belt law from secondary to primary enforcement. As a result, the rate of seat belt usage increased by 13 percentage points (from 70 percent to 83 percent) in the first year after the law was upgraded. </P>
                    <P>The California success was a major factor in rekindling interest among safety officials in upgrading their secondary enforcement laws as a way to increase seat belt use. In 1995, Louisiana became the second State to upgrade from secondary to primary enforcement. As a result, it experienced an 18 percentage point increase (from 50 percent to 68 percent) over the next two years. Next, Georgia upgraded its law and experienced a 15 percentage point increase (from 53 percent to 68 percent). After mounting a highly visible enforcement effort in 1998 (Operation Strap `N Snap), Georgia's usage increased by another 10 percentage points. Similarly, Maryland upgraded its seat belt law in 1997, immediately mounted a two-month enforcement effort, and experienced a 13 percentage point increase in usage. In 1998, the District of Columbia reported a 24 percentage point gain in usage (from 58% to 82%) after enacting one of the strongest seat belt use laws in the nation and implementing several waves of highly visible enforcement. Following a 1999 three-week enforcement effort in Elmira, New York, belt use increased to 90 percent. Taken together, the experiences of North Carolina, California, Louisiana, Georgia, Maryland, the District of Columbia and most recently Elmira, New York have clearly demonstrated that highly visible enforcement of strong laws has tremendous potential for increasing seat belt use rates. </P>
                    <P>Visible enforcement of strong laws also appears to be an essential component of any effective program to increase the use of child safety seats. This is important since early use of child safety seats contributes to the later use of seat belts by children and young adults. There is also a strong relationship between child safety seat use. Studies conducted in several States have found that child safety seat use is nearly three times as high when a driver is buckled up as when a driver is not buckled up. Thus, efforts to persuade adults to buckle up may be the single most important way to get young children protected. However, with child safety seats, correct use is a major concern and the training of law enforcement officers, parents, and advocates is needed to minimize incorrect use and to ensure age-appropriate graduation to seat belts among young children who have outgrown safety seats. Clearly, efforts to increase the use of seat belts and child safety seats are interdependent and complementary. </P>
                    <P>Prior to the 1977 passage of the Child Passenger Safety (CPS) law in Tennessee, very little progress was made to get young children buckled up. Nationally, child safety seat use was less than 15 percent at the time. However, the Tennessee law was followed by the enactment of primary enforcement CPS laws in all States by 1985. This wave of legislation resulted in a major increase in child restraint use. By 1990, usage was estimated to be above 80 percent for infants and about 60 percent for toddlers. </P>
                    <P>Unfortunately, problems such as child seat misuse, premature graduation to seat belt use that skips the important step of booster seat use, and variation in age coverage continue to exist. Another issue to emerge has been the danger posed by passenger side air bags to unrestrained and improperly restrained children. This has led to NHTSA's publication of a final rule for advanced air bags and a new emphasis on programs to increase the proper use of child safety seats and revitalized law enforcement efforts in this area. </P>
                    <HD SOURCE="HD1">Obstacles to Increasing Seat Belt Use </HD>
                    <P>Over the years, all of the States and many public and private sector organizations have been active participants in efforts to increase seat belt use. Public information and education efforts have been the dominant programs funded over the past two decades. Many States have identified major obstacles to enacting primary seat belt laws or implementing highly visible enforcement programs, even though such programs have been shown to result in high usage rates. Most frequently, State (and local) officials have identified a lack of resources for law enforcement as the single greatest barrier to implementing more intense, highly visible enforcement efforts. This lack of resources extends to funding, human resources, and public information support to conduct such campaigns. Over the past five years, many officials have indicated that, if they had the kind of resources provided to States like North Carolina for the Click It or Ticket program, they too would be able to mount similar programs and achieve similar results. The significant amount of funding that has become available under this grant program, combined with the additional new resources available under other TEA-21 programs, should drastically reduce this obstacle. </P>
                    <P>The second most frequently mentioned obstacle to mounting highly visible enforcement programs is a lack of support from key State and local leaders. Experience with the national mobilizations (Operation ABC) and with jurisdictions such as North Carolina, Georgia, Maryland and the District of Columbia suggests that this obstacle can be overcome to a significant degree by proactive efforts to gain the understanding, support and endorsement of various public and private organizations. Including a broad spectrum of such organizations as coalition members in the State's occupant protection program can be very effective in obtaining the commitment of key persons (e.g., the governor) and in gaining the support that is essential for sustained, highly visible enforcement efforts. Much innovation can be demonstrated in the way of developing public and official support for strong enforcement efforts. </P>
                    <P>Another obstacle frequently voiced by State and local enforcement officials is a lack of judicial and prosecutorial support for the enforcement of seat belt and child passenger safety laws. It has frequently been pointed out that an enforcement program can be undermined quickly if prosecutors fail to prosecute seat belt and child safety seat violations and judges repeatedly dismiss such cases. This can be overcome to some extent by educating prosecutors and judges across the State and urging them to value occupant protection laws as highly as any other traffic safety law. </P>
                    <HD SOURCE="HD1">Buckle Up America Campaign </HD>
                    <P>In October 1997, the Buckle Up America (BUA) Campaign established ambitious national goals: (a) to increase seat belt use to 85 percent and reduce child-related fatalities (0-4 years) by 15 percent by the year 2000; and (b) to increase seat belt use to 90 percent and reduce child-related fatalities by 25 percent by the year 2005. This Campaign advocates a four part strategy: (1) building public-private partnerships; (2) enacting strong legislation; (3) maintaining high visibility law enforcement; (4) and conducting effective public education. Central to this Campaign's success is the encouragement of primary seat belt use laws and the implementation of two major enforcement mobilizations each year (Memorial Day and Thanksgiving holidays). During the November 1999 mobilization conducted throughout the week surrounding Thanksgiving, over 7,100 police agencies from all 50 states participated in Operation ABC. </P>
                    <P>The BUA Campaign and the efforts of the Air Bag and Seat Belt Safety Campaign (including Operation ABC) provide a useful framework for the implementation of this grant program. They provide a blueprint for projects that States may wish to implement, using funds to be made available in accordance with this notice. Conversely, this grant program provides an unprecedented opportunity to achieve the ambitious goals established under the BUA Campaign. </P>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13099 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-59-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Research and Special Programs Administration</SUBAGY>
                <SUBJECT>International Standards on the Transport of Dangerous Goods; Public Meetings</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Research and Special Programs Administration (RSPA), Department of Transportation.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public meetings. </P>
                </ACT>
                <SUM>
                    <PRTPAGE P="33882"/>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice is to advise interested persons that RSPA will conduct public meetings in preparation for and to report the results of the eighteenth session of the United Nation's Sub-Committee of Experts on the Transport of Dangerous Goods (UNSCOE) to be held July 3-13, 2000 in Geneva, Switzerland.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>June 21, 2000 10 a.m.-1 p.m., Room 6244-6248; July 19, 2000, 10 a.m.-1 p.m., Room 6244-6248.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Both meetings will be held at DOT Headquarters, Nassif Building, Room 6244-6248, 400 Seventh Street SW., Washington, DC 20590.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Frits Wybenga, International Standards Coordinator, Office of Hazardous Materials Safety, or Bob Richard, Assistant International Standards Coordinator, Office of Hazardous Materials Safety, Department of Transportation, Washington, DC 20590; (202) 366-0656.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The primary purpose of the first meeting will be to prepare for the eighteenth session of the UNSCOE and to discuss U.S. positions on UNSCOE proposals. The primary purpose of the second meeting will be to provide a briefing on the outcome of the UNSCOE session and to prepare for the twenty-first Session of the United Nations Committee of Experts on the Transport of Dangerous Goods (UNSCOE) which is scheduled for December 4-13, 2000 in Geneva, Switzerland. Topics to be covered during the public meetings include: (1) Global harmonization of classification criteria, (2) Reformatting the UN Recommendations into a model rule, (3) Criteria for Environmentally Hazardous Substances, (4) Intermodal portable tank requirements including requirements for the transport of solids in portable tanks, (5) Requirements applicable to small quantities of hazardous materials in transport (limited quantities) including package marking requirements, package quantity limits and requirements applicable to consumer commodities, (6) Harmonized requirements for compress gas cylinders, (7) Classification of individual substances, (8) Requirements for bulk and non-bulk packagings used to transport hazardous materials and (9) Hazard communication requirements including harmonized shipping paper requirements.</P>
                <P>The public is invited to attend without prior notification.</P>
                <HD SOURCE="HD1">Documents</HD>
                <P>Copies of documents for the UNSCOE meeting may be obtained by downloading them from the United Nations Transport Division's web site at http://www.unece.org/trans/main/dgdb/dgsubc/dgscomm.html. Information concerning UN dangerous goods meetings including agendas can be downloaded at http://www.unece.org/trans/danger/meetings.htm#ST/SG. These sites may also be accessed through RSPA's Hazardous Materials Safety Homepage at http://hazmat.dot.gov/intstandards.htm. RSPA's site also provides information regarding the UNSCOE and related matters such as a summary of decisions taken at the 17th session of the UNSCOE, meeting dates and a summary of the primary topics which the UNSCOE plans to address in the 1999-2000 biennium.</P>
                <SIG>
                    <DATED>Issued in Washington, DC, on May 22, 2000.</DATED>
                    <NAME>Robert A. McGuire,</NAME>
                    <TITLE>Acting Associate Administrator for Hazardous Materials Safety.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 00-13183  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-60-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Surface Transportation Board </SUBAGY>
                <DEPDOC>[STB Finance Docket No. 33876] </DEPDOC>
                <SUBJECT>State of Georgia, Department of Transportation—Acquisition Exemption—Georgia Southwestern Railroad, Inc. </SUBJECT>
                <P>
                    The State of Georgia, Department of Transportation (GDOT), a noncarrier, has filed a verified notice of exemption under 49 CFR 1150.31 to acquire from Georgia Southwestern Railroad, Inc. (GSWR) certain railroad assets, including approximately 71.13 miles of rail line extending between Rochelle, GA (milepost 644.00), and a point near Preston, GA (milepost 713.00), and between Omaha, GA ( milepost 753.00), and Mahrt, AL (milepost 755.13).
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The transaction does not include the right or obligation to conduct common carrier freight operations. Heart of Georgia Railroad, Inc. (HOG) acquired the exclusive rail freight easement over the rail line. 
                        <E T="03">See Heart of Georgia Railroad, Inc.—Acquisition and Operation Exemption—State of Georgia and Georgia Southwestern Railroad, Inc.,</E>
                         STB Finance Docket No. 33867 (STB served May 4, 2000). HOG currently conducts and will continue to conduct common carrier freight operations over the rail line. Neither GDOT nor GSWR will have a common carrier obligation to provide freight services when this transaction is completed.
                    </P>
                </FTNT>
                <P>The transaction is scheduled to take place as soon as possible after the May 22, 2000 effective date of the exemption. </P>
                <P>
                    If the notice contains false or misleading information, the exemption is void 
                    <E T="03">ab initio.</E>
                    <SU>2</SU>
                    <FTREF/>
                     Petitions to reopen the proceeding to revoke the exemption under 49 U.S.C. 10502(d) may be filed at any time. The filing of a petition to revoke will not automatically stay the transaction. 
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         A motion to dismiss has been filed in this proceeding. The motion will be addressed in a subsequent Board decision.
                    </P>
                </FTNT>
                <P>An original and 10 copies of all pleadings, referring to STB Finance Docket No. 33876, must be filed with the Surface Transportation Board, Office of the Secretary, Case Control Unit, 1925 K Street, NW., Washington, DC 20423-0001. In addition, a copy of each pleading must be served on Luke Cousins, State of Georgia, Department of Transportation, #2 Capitol Square, S.W., Atlanta, GA 30334-1002. </P>
                <P>Board decisions and notices are available on our website at “WWW.STB.DOT.GOV.” </P>
                <SIG>
                    <DATED>Decided: May 18, 2000.</DATED>
                    <P>By the Board, David M. Konschnik, Director, Office of Proceedings. </P>
                    <NAME>Vernon A. Williams, </NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13171 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4915-00-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request </SUBJECT>
                <DATE>May 16, 2000. </DATE>
                <P>The Department of Treasury has submitted the following public information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Copies of the submission(s) may be obtained by calling the Treasury Bureau Clearance Officer listed. Comments regarding this information collection should be addressed to the OMB reviewer listed and to the Treasury Department Clearance Officer, Department of the Treasury, Room 2110, 1425 New York Avenue, NW., Washington, DC 20220. </P>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before June 26, 2000 to be assured of consideration. </P>
                </DATES>
                <PRTPAGE P="33883"/>
                <HD SOURCE="HD1">Bureau of Alcohol, Tobacco and Firearms (BATF) </HD>
                <P>
                    <E T="03">OMB Number:</E>
                     1512-0205. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     ATF F 5110.40. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Distilled Spirits Records and Monthly Report of Production Operations. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     The information collected is used to account for proprietor's tax liability, adequacy of bond coverage and protection of the revenue. The information also provides data to analyze trends in the industry, and plan efficient allocation of field resources, audit plant operations and compilation of statistics for government economic analysis. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business of other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     150. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent:</E>
                     2 hours. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting Burden:</E>
                     3,600 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1512-0247. 
                </P>
                <P>
                    <E T="03">Recordkeeping Requirement ID Number:</E>
                     ATF REC 5000/2. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Manufacturers of Ammunition, Records and Supporting Data of Ammunition Manufactured and Disposed of.
                </P>
                <P>
                    <E T="03">Description:</E>
                     These records are used by ATF in criminal investigations and compliance inspections in fulfilling the Bureau's mission to enforce the Gun Control Law. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Recordkeepers:</E>
                     50. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Recordkeeper:</E>
                     15 minutes. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Recordkeeping Burden:</E>
                     325 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1512-0292. 
                </P>
                <P>
                    <E T="03">Recordkeeping Requirement ID Number:</E>
                     ATF REC 5120/2. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Letterhead Applications and Notices Relating to Wine. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Letterhead applications and notices relating to wine are required to ensure that the intended activity will not jeopardize the revenue or defraud consumers. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     1,650. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent:</E>
                     30 minutes. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting Burden:</E>
                     825 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1512-0335. 
                </P>
                <P>
                    <E T="03">Recordkeeping Requirement ID Number:</E>
                     ATF REC 5150/4. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Letterhead Applications and Notices Relating to Tax-Free Alcohol. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tax-free alcohol is used for nonbeverage purposes in scientific research and medicinal uses by educational organizations, hospitals, laboratories, etc. Permits/Applications control authorized uses and flow. Protect tax revenue and public safety. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Not-for-profit institutions, Federal Government, State, Local or Tribal Government. 
                </P>
                <P>
                    <E T="03">Estimated Number of Recordkeepers:</E>
                     4,444. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Recordkeeper:</E>
                     30 minutes. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Recordkeeping Burden:</E>
                     2,222 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1512-0512. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     None. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Notices Relating to Payment of Firearms and Ammunition Excise Tax. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Excise taxes are collected on the sale or use of firearms and ammunition by firearms or ammunition manufacturers, importers or producers. Taxpayers who elect to pay excise taxes by electronic fund transfer must furnish a written notice upon election and discontinuance. Tax revenue will be protected. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     10. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent:</E>
                     6 minutes. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting Burden:</E>
                     1 hour.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1512-0540. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     ATF REC 5120/11. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Information Collection in Support of Small Producer's Wine Tax Credit. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     ATF needs this information to insure proper tax credit. The information is used by taxpayers in preparing their returns and by ATF to verify tax computation. Recordkeepers are wine producers who want to transfer their credit to warehouse operators and the transferees who take such credit. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Recordkeepers:</E>
                     280. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Recordkeeper:</E>
                     None. 
                </P>
                <P>
                    <E T="03">Estimated Total Recordkeeping Burden:</E>
                     1 hour. 
                </P>
                <P>
                    <E T="03">Clearance Officer:</E>
                     Robert N. Hogarth (202) 927-8930, Bureau of Alcohol, Tobacco and Firearms, Room 3200, 650 Massachusetts Avenue, NW., Washington, DC 20226. 
                </P>
                <P>
                    <E T="03">OMB Reviewer:</E>
                     Alexander T. Hunt (202) 395-7860, Office of Management and Budget, Room 10202, New Executive Office Building, Washington, DC 20503. 
                </P>
                <SIG>
                    <NAME>Lois K. Holland, </NAME>
                    <TITLE>Departmental Reports, Management Officer. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13116 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4810-31-U </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request </SUBJECT>
                <DATE>May 19, 2000. </DATE>
                <P>The Department of Treasury has submitted the following public information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Copies of the submission(s) may be obtained by calling the Treasury Bureau Clearance Officer listed. Comments regarding this information collection should be addressed to the OMB reviewer listed and to the Treasury Department Clearance Officer, Department of the Treasury, Room 2110, 1425 New York Avenue, NW., Washington, DC 20220. </P>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before June 26, 2000 to be assured of consideration. </P>
                </DATES>
                <HD SOURCE="HD1">Bureau of Alcohol, Tobacco and Firearms (BATF) </HD>
                <P>
                    <E T="03">OMB Number:</E>
                     1512-0038. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     ATF F 5030.6. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Authorization to Furnish Financial Information and Certificate of Compliance. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     The Right to Financial Privacy Act of 1978 limits access to records held by financial institutions and provides for certain procedures to gain access to the information. ATF F 5030.6 serves as both a customer authorization for ATF to receive information and as the required certification to the financial institution. 
                </P>
                <PRTPAGE P="33884"/>
                <P>
                    <E T="03">Respondents:</E>
                     Business of other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     2,000. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent:</E>
                     15 minutes. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting Burden:</E>
                     500 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1512-0059. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     ATF F 5120.29. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Bonded Wineries—Formula and Process for Wine, Letterhead Applications and Notices Relating to Formula Wine. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     ATF F 5120.29 is used to determine the classification of wines for labeling and consumer protection. The form describes the person filing, type of product to be made and restrictions to the labeling and manufacture. The form is also used to audit a product. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     600. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent:</E>
                     2 hours. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting Burden:</E>
                     1,200 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1512-0082. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     ATF F 1582-A (5120.24). 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Drawback on Wines Exported. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     When proprietors export wines that have been produced, packaged, manufactured, or bottled in the U. S., they file a claim for drawback or refund for the taxes that have already been paid on the wine. This form notifies ATF that the wine was in fact exported and helps to protect the revenue and prevent fraudulent claims. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals or households, Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     900. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent:</E>
                     1 hour, 7 minutes. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting Burden:</E>
                     2,025 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1512-0131. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     ATF F 5400.14/5400.15, Part III. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Renewal of Explosives License or Permit. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     This information collection activity is used for the renewal of explosives licenses and permits. This short renewal form is used in lieu of a more detailed application. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     2,500. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent:</E>
                     20 minutes. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting Burden:</E>
                     825 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1512-0554. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     ATF F 5000.28T. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     2000 Floor Stocks Tax Return (Cigarettes) and Recordkeeping Requirements. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     All persons who hold for sale any cigarettes on January 1, 2000, must take an inventory. A floor stocks tax has been imposed on cigarettes. The recordkeeping and the tax return for this tax are prescribed by ATF. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Recordkeepers:</E>
                     400,000. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Recordkeeper:</E>
                     30 minutes. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Other (One-time). 
                </P>
                <P>
                    <E T="03">Estimated Total Recordkeeping Burden:</E>
                     1,532,000 hours.
                </P>
                <P>
                    <E T="03">Clearance Officer:</E>
                     Robert N. Hogarth (202) 927-8930, Bureau of Alcohol, Tobacco and Firearms, Room 3200, 650 Massachusetts Avenue, N.W., Washington, DC 20226. 
                </P>
                <P>
                    <E T="03">OMB Reviewer:</E>
                     Alexander T. Hunt (202) 395-7860, Office of Management and Budget, Room 10202, New Executive Office Building, Washington, DC 20503. 
                </P>
                <SIG>
                    <NAME>Lois K. Holland,</NAME>
                    <TITLE>Departmental Reports Management Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13117  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-31-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request </SUBJECT>
                <DATE>May 12, 2000. </DATE>
                <P>The Department of Treasury has submitted the following public information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Copies of the submission(s) may be obtained by calling the Treasury Bureau Clearance Officer listed. Comments regarding this information collection should be addressed to the OMB reviewer listed and to the Treasury Department Clearance Officer, Department of the Treasury, Room 2110, 1425 New York Avenue, NW., Washington, DC 20220. </P>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before June 26, 2000 to be assured of consideration. </P>
                </DATES>
                <HD SOURCE="HD1">Internal Revenue Service (IRS) </HD>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0025. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 712. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Life Insurance Statement. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Form 712 is used to establish the value of life insurance policies for estate and gift tax purposes. The tax is based on the value of these policies. The form is completed by life insurance companies. 
                </P>
                <P>
                    <E T="03">Respondents: </E>
                    Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeepers:</E>
                     60,000. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent/Recordkeeper:</E>
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,p1,8/9,i1" CDEF="s100,r30">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Recordkeeping</ENT>
                        <ENT>18 hr., 11 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Learning about the law or the form</ENT>
                        <ENT>6 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Preparing and sending the form to the IRS</ENT>
                        <ENT>23 min. </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     1,120,800 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0257. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Forms 8109, 8109-B, and 8109-C. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title: </E>
                    Federal Tax Deposits (8109 and 8109-B); and FTD Address Change (8109-C). 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Federal Tax Deposit Coupons are used to deposit certain types of taxes at authorized depositaries. Coupons are sent to the IRS Centers for crediting to taxpayers' accounts. Data is used by the IRS to make the credit and to verify tax deposits claimed on the returns. The FTD Address change is used to change the address on the FTD coupons. All taxpayers required to make deposits are affected. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit, Not-for-profit institutions, Farms, Federal Government, State, Local or Tribal Government. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     9,300,700. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent:</E>
                     2 minutes. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion, Weekly, Monthly, Other (semi-weekly, monthly). 
                </P>
                <PRTPAGE P="33885"/>
                <P>
                    <E T="03">Estimated Total Reporting Burden:</E>
                     1,841,607 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1091. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 8810. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Corporate Passive Activity Loss or Credit Limitations. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Under section 469, losses and credits from passive activities, to the extent they exceed passive income (or, in the case of credits, the tax attributable to net passive income), are not allowed. Form 8810 is used by personal service corporations and closely held corporations to figure the passive activity loss and credits allowed and the amount of loss and credit to be reported on their tax return. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeepers:</E>
                     100,000. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent/Recordkeeper:</E>
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,p1,8/9,i1" CDEF="s100,r30">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Recordkeeping</ENT>
                        <ENT>26 hr., 19 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Learning about the law or the form</ENT>
                        <ENT>5 hr., 7 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Preparing and sending the form to the IRS</ENT>
                        <ENT>5 hr., 43 min. </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Frequency of Response: Annually.</E>
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     3,708,000 hours. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1683. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 56-A (formerly Forms 12575 and 12575-A). 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Notice Concerning Fiduciary Relationship—Illinois Type Land Trust. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     The data collected on the form provides trustees of Illinois Land Trusts a convenient method of reporting information related to creating, changing, and closing such trusts. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeepers:</E>
                     10,000. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent/Recordkeeper:</E>
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,p1,8/9,i1" CDEF="s100,r30">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Recordkeeping</ENT>
                        <ENT>40 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Learning about the law or the form</ENT>
                        <ENT>10 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Preparing the form</ENT>
                        <ENT>21 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Copying, assembling, and sending the form to the IRS</ENT>
                        <ENT>20 min. </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     15,100 hours.
                </P>
                <P>
                    <E T="03">Clearance Officer:</E>
                     Garrick Shear, Internal Revenue Service, Room 5244, 1111 Constitution Avenue, NW, Washington, DC 20224. 
                </P>
                <P>
                    <E T="03">OMB Reviewer:</E>
                     Alexander T. Hunt (202) 395-7860, Office of Management and Budget, Room 10202, New Executive Office Building, Washington, DC 20503. 
                </P>
                <SIG>
                    <NAME>Lois K. Holland,</NAME>
                    <TITLE>Departmental Reports, Management Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13118  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBJECT>Submission for OMB review; Comment Request </SUBJECT>
                <DATE>May 16, 2000. </DATE>
                <P>The Department of Treasury has submitted the following public information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Copies of the submission(s) may be obtained by calling the Treasury Bureau Clearance Officer listed. Comments regarding this information collection should be addressed to the OMB reviewer listed and to the Treasury Department Clearance Officer, Department of the Treasury, Room 2110, 1425 New York Avenue, NW., Washington, DC 20220. </P>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before June 26, 2000 to be assured of consideration. </P>
                </DATES>
                <HD SOURCE="HD1">Internal Revenue Service (IRS) </HD>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0120. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 1099-G. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Certain Government and Qualified State Tuition Program Payments.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Form 1099-G is used by governments (primarily state and local) to report to the IRS (and notify recipients of) certain payments (
                    <E T="03">e.g.,</E>
                     unemployment compensation and income tax refunds). IRS uses the information to insure that the income is being properly reported by the recipients on their returns. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Federal Government, State, Local or Tribal Government 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     2,900. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent:</E>
                     12 minutes. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Annually. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting Burden:</E>
                     11,149,325 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0190. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 4876-A. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Election To Be Treated as an Interest Charge DISC. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     A domestic corporations and its shareholders must elect to be an interest charge domestic international sales corporation (IC-DISC). Form 4876-A I used to make the election. IRS uses the information to determine if the corporation qualifies to be an IC-DISC. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeepers:</E>
                     1,000. 
                </P>
                <PRTPAGE P="33886"/>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent/Recordkeeper:</E>
                </P>
                <FP SOURCE="FP1-2">Recordkeeping—4 hr., 4 min.</FP>
                <FP SOURCE="FP1-2">Learning about the law or the form—1 hr., 47 min.</FP>
                <FP SOURCE="FP1-2">Preparing and sending the form to the IRS—1 hr., 54 min. </FP>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Other (One-Time Election).
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     5,760 hours. 
                </P>
                <P>
                    <E T="03">Clearance Officer:</E>
                     Garrick Shear, Internal Revenue Service, Room 5244, 1111 Constitution Avenue, NW, Washington, DC 20224. 
                </P>
                <P>
                    <E T="03">OMB Reviewer:</E>
                     Alexander T. Hunt (202) 395-7860, Office of Management and Budget, Room 10202, New Executive Office Building, Washington, DC 20503. 
                </P>
                <SIG>
                    <NAME>Lois K. Holland, </NAME>
                    <TITLE>Departmental Reports Management Officer. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13119 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request </SUBJECT>
                <DATE>May 16, 2000. </DATE>
                <P>The Department of Treasury has submitted the following public information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Copies of the submission(s) may be obtained by calling the Treasury Bureau Clearance Officer listed. Comments regarding this information collection should be addressed to the OMB reviewer listed and to the Treasury Department Clearance Officer, Department of the Treasury, Room 2110, 1425 New York Avenue, NW., Washington, DC 20220. </P>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before June 26, 2000 to be assured of consideration. </P>
                </DATES>
                <HD SOURCE="HD1">Internal Revenue Service (IRS) </HD>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0205. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 5452. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Corporate Report of Nondividend Distribution. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Form 5452 is used by corporations to report their nontaxable distributions as required Internal Revenue Code (IRC) 6042(d)(2). The information is used IRS to verify that the distributions are nontaxable as claimed. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business of other for-profit, Farms. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeepers:</E>
                     1,700. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent/Recordkeeper: </E>
                </P>
                <FP SOURCE="FP-1">Recordkeeping: 28 hr., 13 min.</FP>
                <FP SOURCE="FP-1">Learning about the law or the form: 58 min.</FP>
                <FP SOURCE="FP-1">Preparing the form: 2 hr., 24 min.</FP>
                <FP SOURCE="FP-1">Copying, assembling, and sending the form to the IRS: 16 min. </FP>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     54,145 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0902. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Forms 8288 and 8288-A. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     U.S. Withholding Tax Return for Dispositions by Foreign Persons of U.S. Real Property Interests (Form 8288); and Statement of Withholding on Dispositions by Foreign Persons of U.S. Real Property Interests (Form 8288-A). 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Form 8288 is used by the withholding agent to report and transmit the withholding to IRS. Form 8288-A is used to validate the withholding and to return a copy to the transferor for his/her use in filing a tax return. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit, Individuals or households 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeepers:</E>
                     4,918. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent/Recordkeeper:</E>
                </P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,xls80,xs80">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">  </CHED>
                        <CHED H="1">Form 8288 </CHED>
                        <CHED H="1">Form 8288-A </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Recordkeeping </ENT>
                        <ENT>5 hr., 16 min. </ENT>
                        <ENT>2 hr., 52 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Learning about the law or the form </ENT>
                        <ENT>5 hr., 8 min. </ENT>
                        <ENT>30 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Preparing and sending the form to the IRS </ENT>
                        <ENT>6 hr., 39 min. </ENT>
                        <ENT>34 min. </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     124,607 hours. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1257. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 8827. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Credit for Prior Year Minimum Tax—Corporation. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Section 53(d), as revised, allows corporations a minimum tax credit based on the full amount of alternative minimum tax incurred in tax years beginning after 1989, or a carryforward for use in a future year. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit, Farms. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     25,000. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent:</E>
                     1 hour. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Annually. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     25,000 hours. 
                </P>
                <P>
                    <E T="03">Clearance Officer:</E>
                     Garrick Shear, Internal Revenue Service, Room 5244, 1111 Constitution Avenue, NW, Washington, DC 20224. 
                </P>
                <P>
                    <E T="03">OMB Reviewer:</E>
                     Alexander T. Hunt (202) 395-7860, Office of Management and Budget, Room 10202, New Executive Office Building, Washington, DC 20503. 
                </P>
                <SIG>
                    <NAME>Lois K. Holland, </NAME>
                    <TITLE>Departmental Reports Management Officer. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13120 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Submission for OMB Review; Comment Request </SUBAGY>
                <SUBJECT> </SUBJECT>
                <DATE>May 18, 2000. </DATE>
                <P>The Department of Treasury has submitted the following public information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Copies of the submission(s) may be obtained by calling the Treasury Bureau Clearance Officer listed. Comments regarding this information collection should be addressed to the OMB reviewer listed and to the Treasury Department Clearance Officer, Department of the Treasury, Room 2110, 1425 New York Avenue, NW., Washington, DC 20220. </P>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before June 26, 2000 to be assured of consideration. </P>
                </DATES>
                <HD SOURCE="HD1">Internal Revenue Service (IRS) </HD>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0195.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 5213.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Election To Postpone Determination as To Whether the Presumption Applies That an Activity Is Engaged in for Profit. 
                </P>
                <PRTPAGE P="33887"/>
                <P>
                    <E T="03">Description:</E>
                     This form is used by individuals, partnerships, estates, trusts, and S corporations to make an election to postpone an IRS determination as to whether an activity is engaged in for profit for 5 years (7 years for breeding, training, showing, or racing horses). The data is used to verify eligibility to make the election. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit, Individual or households. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeepers:</E>
                     10,730. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent/Recordkeeper:</E>
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s30,r20">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">  </CHED>
                        <CHED H="1">  </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Recordkeeping </ENT>
                        <ENT>7 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Learning about the law or the form </ENT>
                        <ENT>10 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Preparing the form </ENT>
                        <ENT>10 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Copying, assembling, and sending the form to the IRS </ENT>
                        <ENT>20 min. </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     8,262 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0495.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 4506-A.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title: </E>
                    Request for Public Inspection or Copy of Exempt Organization IRS Form. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Internal Revenue Code section 6104 states that if an organization described in section 501(c) or (d) is exempt from taxation under section 501(a) for any taxable year, the application for exemption is open for public inspection. This includes all supporting documents, any letter or other documents issued by the IRS concerning the application, and certain annual returns of the organization. Form 4506-A is used to request public inspection or a copy of these documents. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit, Individuals or households, Not-for-profit institutions, Farms, Federal Government, State, Local or Tribal Government. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeepers:</E>
                     20,000. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent/Recordkeeper:</E>
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,r20">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">  </CHED>
                        <CHED H="1">  </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Recordkeeping </ENT>
                        <ENT>7 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Learning about the law or the form </ENT>
                        <ENT>3 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Preparing the form </ENT>
                        <ENT>13 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Copying, assembling, and sending the form to the IRS </ENT>
                        <ENT>14 min. </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     12,000 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0865.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 8264.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Application for Registration of a Tax Shelter.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Organizers of certain tax shelters are required to register them with the IRS using Form 8264. Other persons may have to register the tax shelter if the organizer doesn't. We use the information to five the tax shelter a registration number. Sellers of interests in the tax shelter furnish the number of investors who report the number on their tax returns. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit, Individuals or households. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeepers:</E>
                     1,000. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent/Recordkeeper:</E>
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,r20">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">  </CHED>
                        <CHED H="1">  </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Recordkeeping </ENT>
                        <ENT>31 hr., 49 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Learning about the law or the form </ENT>
                        <ENT>1 hr., 17 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Preparing, copying, assembling, and sending the form to the IRS </ENT>
                        <ENT>1 hr., 52 min. </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     34,960 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0881.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 8271.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Investor Reporting of Tax Shelter Registration Number.
                </P>
                <P>
                    <E T="03">Description:</E>
                     All persons who are claiming a deduction, loss, credit, or other tax benefit, or reporting any income on their returns from a tax shelter required to be registered (under IRC 6111) must report the tax shelter registration number on that return. Form 8271 is used for this purpose. We use the information to associate claimed benefits with the tax shelter and to determine if any compliance actions are needed. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals or households, Business or other for-profit, Not-for-profit institutions, Farms, State, Local or Tribal Government.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeepers:</E>
                     297,500. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent/Recordkeeper:</E>
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,r20">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">  </CHED>
                        <CHED H="1">  </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Recordkeeping </ENT>
                        <ENT>7 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Learning about the law or the form </ENT>
                        <ENT>8 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Preparing the form </ENT>
                        <ENT>17 min. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Copying, assembling, and sending the form to the IRS </ENT>
                        <ENT>10 min. </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Annually.
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     205,275 hours.
                </P>
                <P>
                    <E T="03">Clearance Officer:</E>
                     Garrick Shear, Internal Revenue Service, Room 5244, 1111 Constitution Avenue, NW, Washington, DC 20224. 
                </P>
                <P>
                    <E T="03">OMB Reviewer:</E>
                     Alexander T. Hunt (202) 395-7860, Office of Management and Budget, Room 10202, New Executive Office Building Washington, DC 20503. 
                </P>
                <SIG>
                    <NAME>Lois K. Holland, </NAME>
                    <TITLE>Departmental Reports Management Officer. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13121 Filed 5-24-00; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <SUBJECT>Advisory Committee on Minority Veterans, Notice of Meeting</SUBJECT>
                <P>The Department of Veterans Affairs (VA), in accordance with Public Law 103-446, and Public Law 92-463, (Committee) will be held from Monday, June 5, 2000 to Wednesday, June 7, 2000, in Washington, DC. The purpose of the Committee is to advise the Secretary of Veterans Affairs on the administration of VA benefits and services to minority veterans; to assess the needs of minority veterans and to evaluate whether VA compensation, medical and rehabilitation services, outreach, and other programs are meeting those needs. The Committee will make recommendations to the Secretary regarding such activities.</P>
                <P>The meeting will convene to room 830, VA Central Office Building, 810 Vermont Avenue, NW, Washington, DC, from 8:30 a.m. to 5:00 p.m. each day. On June 5, the Committee will focus on such health care issues as minority health—a global assessment, medical research, Board of Veterans Appeals (BVA) operations, and Minority and Veterans Business contacting. On Tuesday, June 6, the Committee will concentrate its effort on a report of a Veterans Identity Study, Hepatitis C infections, the cardiac care program evaluation, the Veterans' Benefits Administration's Road Map to Excellence and National Cemetery operations. The Committee will work in Subcommittees in the afternoon session. On Wednesday, June 7, the Committee will examine several diversity training programs and will begin drafting its annual report for Fiscal Year 2000.</P>
                <P>
                    These sessions will be open to the public. In order to notify the VA Security Office of the number of visitors to expect, those wishing to attend the meeting should contact Mr. Anthony T. 
                    <PRTPAGE P="33888"/>
                    Hawkins, Department of Veterans Affairs, at (202) 273-6708, before June 1, 2000. No time will be allocated for receiving oral presentations from the public. However, the Committee will accept written comments from interested parties on issues affecting minority veterans. Such comments should be referred to the Committee at the following address: Advisory Committee on Minority Veterans, Center for Minority Veterans (00M), U.S. Department of Veterans Affairs, 810 Vermont Avenue, NW, Washington, DC 20420.
                </P>
                <SIG>
                    <DATED>Dated: May 16, 2000.</DATED>
                    <FP>By Direction of the Secretary.</FP>
                    <NAME>Marvin R. Eason,</NAME>
                    <TITLE>Committee Management Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>FR Doc. 00-13167 Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <SUBJECT>Advisory Committee on the Readjustment of Veterans, Notice of Meeting</SUBJECT>
                <P>The Department of Veterans Affairs (VA) gives notice under Public Law 92-463 that a Meeting of the Advisory Committee on the Readjustment of Veterans will be held June 15 and 16, 2000. This will be a regularly scheduled meeting for the purpose of reviewing VA services of veterans, and to formulate Committee recommendations and objectives. The meeting on both days will be held at The American Legion, Washington Office, 1608 K Street, NW, Washington, DC. The agenda on both days will commence at 8:30 a.m. and adjourn at 4:30 p.m.</P>
                <P>The agenda for Thursday, June 15, will include reviews of Veterans Health Administration (VHA) special emphasis programs for prosthetics, environmental agents and post-traumatic stress disorder. The agenda for both days will also include strategic planning sessions to formulate goals and objectives for a Committee field visit to VA facilities to be conducted later in the year.</P>
                <P>On Friday, June 16, the Committee will review Veterans Benefits Administration (VBA) programs related to PTSD compensation, vocational rehabilitation and counseling, and transition assistance.</P>
                <P>The meeting will be open to the public. Those who plan to attend or who have questions concerning the meeting may contact Alfonso R. Batres, Chief Readjustment Counseling Officer, Department of Veterans Affairs Headquarters Office at (202) 273-8967.</P>
                <SIG>
                    <DATED>Dated: May 16, 2000.</DATED>
                    <FP>By Direction of the Secretary.</FP>
                    <NAME>Marvin R. Eason,</NAME>
                    <TITLE>Committee Management Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 00-13168  Filed 5-24-00; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-M</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>65</VOL>
    <NO>102</NO>
    <DATE>Wednesday, May 25, 2000</DATE>
    <UNITNAME>CORRECTIONS</UNITNAME>
    <CORRECT>
        <EDITOR>!!!DON!!!</EDITOR>
        <PREAMB>
            <PRTPAGE P="33889"/>
            <AGENCY TYPE="S">GENERAL SERVICES ADMINISTRATION</AGENCY>
            <CFR>41 CFR Part 102-36</CFR>
            <DEPDOC>[FPMR Amendment H-205]</DEPDOC>
            <RIN>RIN 3090-AF39</RIN>
            <SUBJECT>Disposition of Excess Personal Property</SUBJECT>
        </PREAMB>
        <SUPLINF>
            <HD SOURCE="HD2">Correction</HD>
            <P>In rule document 00-11921 beginning on page 31218 in the issue of Tuesday, May 16, 2000, make the following correction:</P>
            <SECTION>
                <SECTNO>§102-36.125</SECTNO>
                <SUBJECT>[Corrected]</SUBJECT>
                <P>On pages 31223 and 31224, in §102-36.125(b), the table should read as set forth:</P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,xls44,xs100">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Type of property </CHED>
                        <CHED H="1">GSA region </CHED>
                        <CHED H="1">Location </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Aircraft </ENT>
                        <ENT>9 FBP </ENT>
                        <ENT>San Francisco, CA 94102. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Firearms </ENT>
                        <ENT>7 FP-8 </ENT>
                        <ENT>Denver, CO 80225. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Foreign Gifts </ENT>
                        <ENT>FBP </ENT>
                        <ENT>Washington, DC 20406. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Forfeited Property </ENT>
                        <ENT>3 FP </ENT>
                        <ENT>Washington, DC 20407. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Standard Forms </ENT>
                        <ENT>7 FMP </ENT>
                        <ENT>Ft. Worth, TX 76102. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Vessels, civilian</ENT>
                        <ENT>4 FD </ENT>
                        <ENT>Atlanta, GA 30365. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Vessels, DOD </ENT>
                        <ENT>3 FPD </ENT>
                        <ENT>Philadelphia, PA 19107. </ENT>
                    </ROW>
                </GPOTABLE>
            </SECTION>
        </SUPLINF>
        <FRDOC>[FR Doc. C0-11921 Filed 5-24-00; 8:45 am]</FRDOC>
        <BILCOD>BILLING CODE 1505-01-D</BILCOD>
    </CORRECT>
    <VOL>65</VOL>
    <NO>102</NO>
    <DATE>Thursday, May 25, 2000</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="33891"/>
            <PARTNO>Part II</PARTNO>
            <AGENCY TYPE="P">Department of the Interiorÿ7E</AGENCY>
            <SUBAGY>Fish and Wildlife Service</SUBAGY>
            <HRULE/>
            <TITLE>National Wildlife Refuge System Administration Act as Amended by the National Wildlife Refuge System Improvement Act of 1997, Refuge Planning Policy; Notice</TITLE>
        </PTITLE>
        <NOTICES>
            <NOTICE>
                <PREAMB>
                    <PRTPAGE P="33892"/>
                    <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                    <SUBAGY>Fish and Wildlife Service </SUBAGY>
                    <SUBJECT>Refuge Planning Policy Pursuant to the National Wildlife Refuge System Administration Act as Amended by the National Wildlife Refuge System Improvement Act of 1997 </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Fish and Wildlife Service, Interior. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The U.S. Fish and Wildlife Service (Service or we) establishes requirements and guidance for National Wildlife Refuge System planning, including Comprehensive Conservation Plans (CCPs) and step-down management plans. This policy, which incorporates the CCP provisions of the National Wildlife Refuge System Administration Act, as amended, replaces Part 602 Chapters 1, 2, and 3 of the Fish and Wildlife Service Manual. The new policy will appear as Part 602 Chapters 1, 3, and 4. </P>
                        <P>Our policy for managing units of the National Wildlife Refuge System (Refuge System) is that we will manage all refuges in accordance with an approved CCP which, when implemented, will achieve refuge purposes; help fulfill the Refuge System mission; maintain and, where appropriate, restore the ecological integrity of each refuge and the Refuge System; help achieve the goals of the National Wilderness Preservation System; and meet other mandates. The CCP will guide management decisions and set forth goals, objectives, and strategies to accomplish these ends. We also may require step-down management plans to provide additional guidance for meeting CCP goals and objectives and to describe strategies and implementation schedules. Each plan will be consistent with principles of sound fish and wildlife management, available science, legal mandates, and our other policies, guidelines, and planning documents. We will prepare refuge plans that, above all else, ensure that wildlife comes first on national wildlife refuges. </P>
                    </SUM>
                    <DATES>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            This policy is effective upon publication in the 
                            <E T="04">Federal Register</E>
                            . 
                        </P>
                    </DATES>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>We will send a copy of the Fish and Wildlife Service Manual chapters on Refuge System planning to those who submitted comments on the draft policy and to anyone who would like to receive them. Please contact Liz Bellantoni, Refuge Planning Coordinator, Division of Refuges, U.S. Fish and Wildlife Service, at (703) 358-2422 if you would like to receive a copy. In addition, these chapters will be available on the Refuge System web site (http://refuges.fws.gov [select link to “Manual/Policies: Refuge Planning Policy']). </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>The National Wildlife Refuge System Administration Act of 1966 as amended by the National Wildlife Refuge System Improvement Act of 1997, 16 U.S.C. 668dd-668ee (Refuge Administration Act), provides an “Organic Act” for the National Wildlife Refuge System. It clearly establishes that wildlife conservation is the principal mission of the Refuge System; provides guidance to the Secretary of the Interior for management of the Refuge System; reinforces the importance of comprehensive planning for all units of the Refuge System; and gives Refuge Managers uniform direction and procedures for making decisions regarding wildlife conservation and uses of the Refuge System. </P>
                    <HD SOURCE="HD1">Planning and the Refuge Administration Act </HD>
                    <P>Except for those refuges in Alaska (which are subject to the refuge planning provisions of the Alaska National Interest Lands Conservation Act [ANILCA]), the Refuge Administration Act requires that we manage all national wildlife refuges according to an approved CCP. We will prepare a CCP by October 2012 for each refuge in existence at the time of passage of the National Wildlife Refuge System Improvement Act. For refuges established after passage of this Act, we will prepare CCPs when we staff the refuge and acquire a land base sufficient to achieve refuge purposes, but no later than 15 years after establishment of the refuge. The Refuge Administration Act also requires that we provide an opportunity for active public involvement during the preparation and revision of CCPs. These plans will guide management decisions and establish strategies for achieving the mission of the Refuge System and the purposes of each refuge unit. </P>
                    <HD SOURCE="HD1">Purpose of This Policy </HD>
                    <P>This policy establishes requirements and guidance for National Wildlife Refuge System planning, including CCPs and step-down management plans, and ensures that planning efforts comply with the provisions of the Refuge Administration Act. </P>
                    <HD SOURCE="HD1">Response to Comments Received </HD>
                    <P>
                        On August 13, 1999, we published a notice in the 
                        <E T="04">Federal Register</E>
                         (64 FR 44368) to establish requirements and guidance for Refuge System planning, including CCPs and step-down management plans. During the 60-day comment period, we received 41 comments from the following sources: non-government organizations (16), State agencies (14), Service employees (5), other Federal agencies (1), private citizens (4), and commercial businesses (1). Key points raised by the public and addressed in the final policy include: 
                    </P>
                    <P>• placing greater emphasis on wildlife first and elevating our commitment to maintain and, where appropriate, restore the ecological integrity of each refuge and the Refuge System as mandated by the National Wildlife Refuge System Improvement Act of 1997; </P>
                    <P>• basing management decisions on a thorough assessment of available science; </P>
                    <P>• defining our relationship with States and other agencies and their programs; </P>
                    <P>• identifying biological information necessary for planning and management; </P>
                    <P>• clarifying under what conditions we should revise a CCP; </P>
                    <P>• expediting or further clarifying our planning process; </P>
                    <P>• describing the relationship of CCPs to refuge purposes and Refuge System mission; and </P>
                    <P>• addressing issues related to recreation and public use. </P>
                    <P>We reviewed and considered all substantive comments received. Following are public comments and our responses grouped under eight broad headings: </P>
                    <HD SOURCE="HD2">I. Placing Greater Emphasis on Wildlife First and Elevating Our Commitment to Maintain and, Where Appropriate, Restore the Ecological Integrity of Each Refuge and the Refuge System as Mandated by the National Wildlife Refuge System Improvement Act of 1997 </HD>
                    <P>
                        <E T="03">Comment:</E>
                         The Service's drafting of the proposed planning policy is pursuant to the mandates contained in the National Wildlife Refuge System Improvement Act of 1997. The first and foremost goal of the Refuge Improvement Act is to ensure that wildlife conservation is the principal mission of the Refuge System. Although the Refuge Improvement Act established a hierarchy of appropriate and compatible wildlife-dependent uses of a refuge, wildlife conservation is paramount and every aspect of the Service's planning process must reflect this principal goal. The planning process should be preceded by, and indeed founded upon, first establishing the wildlife and ecological priorities of 
                        <PRTPAGE P="33893"/>
                        the refuge. Then the plan should consider certain public uses deemed compatible with the refuge purpose, the Refuge System mission, and the particular conditions of the refuge. This is particularly important since the CCP process includes the drafting or recertification of compatibility determinations. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have strengthened Section 1.5, “What are the goals of refuge planning?,” by adding as the very first goal, “A. To ensure that wildlife comes first in the National Wildlife Refuge System.” We have strengthened Section 3.3 (formerly Section 2.3), “What are our goals for Comprehensive Conservation Planning?,” by revising goal A. to read: “To ensure that wildlife comes first in the National Wildlife Refuge System and that we manage each refuge to help fulfill the mission of the Refuge System; maintain and, where appropriate, restore the ecological integrity of each refuge and the Refuge System; as well as achieve the specific purposes for which the refuge was established.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The draft planning policy should be revised each and every place where it pledges allegiance to the mission of the Refuge System and purposes of the individual refuges in order to also ensure that the planning process will advance the maintenance and restoration of biological integrity, diversity, and environmental health. For example, Section 602 FW 1.3 should be modified to state that, “We will manage all refuges in accordance with an approved CCP which, when implemented, will achieve refuge purposes, fulfill the System mission, maintain and restore biological integrity, diversity, and environmental health, and meet all other relevant mandates. The CCP will guide management decisions and set forth goals, objectives, and strategies to accomplish these ends * * *.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have incorporated similar language into the final policy. We are now using the term “ecological integrity” in lieu of the phrase “biological integrity, diversity, and environmental health.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Reword Section 602 FW 1.5 B to state that the goal of refuge planning is “To help ensure that we restore and maintain the biological integrity, diversity, and environmental health of each refuge and the Refuge System, and contribute to the conservation of the structure and function of the ecosystems of the United States.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have revised the text with modification. See 602 FW 1.5 C. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Reword Section 602 FW 1.6 B to define the term CCP as “A document that describes the desired future conditions of the refuge and provides long-range guidance and management direction to accomplish the purposes of the refuge, fulfill the mission of the System, restore and maintain the biological integrity, diversity, and environmental health of each refuge and the Refuge System, and meet other relevant mandates.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have revised the text with modification. See 602 FW 1.6 E. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Amend Section 602 FW 1.7 D, 2.1, 2.3 B, 2.4 A, 2.4 C (1)(b), (c), and (d)(ii), 2.4 C (4), 2.4 C (4)(d), and 2.4 C (7) to highlight the restoration and maintenance of biological integrity, diversity, and environmental health as a major feature of CCPs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have amended the text where appropriate. See Section 602 FW 1.7 D, 3.1 (formerly 2.1), 3.3 A (formerly 2.3 B), 3.4 A (formerly 2.4 A), and 3.4 C (1)(d) (formerly 2.4 C (1)(c)). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Reword Section 602 FW 2.4 C (1)(f) to require that CCPs set goals for appropriate indices of biological integrity, diversity, and environmental health.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have incorporated similar language into the final policy. See 602 FW 3.4 C (1)(g).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Reword Section 602 FW 2.4 C (1)(g) to require that CCPs identify additional problems, 
                        <E T="03">e.g.,</E>
                         “Identify any significant problems that may adversely affect the population and habitats of fish, wildlife, and plants (including candidate, threatened, and endangered species), the biological integrity, diversity, and environmental health or the wilderness characteristics within the planning unit, and the actions necessary to correct or mitigate such problems.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have addressed the need to identify and describe these problems in Section 3.4 C (1)(e)(x) and (xii) (formerly 2.4 C (1)(d)). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Reword Section 2.4 C (4)(d) to require that CCPs set objectives for appropriate indices of biological integrity, diversity, and environmental health.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe this is more appropriately done at the goal-setting level and have revised the text in Section 3.4 C (1)(g) (formerly 2.4 C (1)(f)) accordingly.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The policies that guide the refuge planning process must, above all else, ensure that CCPs put wildlife first. The draft planning policy makes an important start towards accomplishing this end, but should be modified in several places to drive home this point more explicitly and emphatically.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have modified the final policy in various places to emphasize that we will prepare CCPs that, above all else, ensure that wildlife comes first on national wildlife refuges. See 602 FW 1.3, 1.4 A, and 1.5 A, and 602 FW 3.3 A. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Existing language in the draft policy regarding the proposed action is inappropriately and inexplicably weak. Section 602 FW 2.4 C (4)(c) should be reworded to reflect that the planning team shall select as the proposed action in each CCP the alternative that best achieves planning unit purposes, vision and goals; fulfills the Refuge System mission; maintains and restores biological integrity, diversity, and environmental health; addresses the significant issues and relevant mandates, and is consistent with principles of sound fish and wildlife management. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We strengthened the language in the final policy as suggested, with minor modification. See 602 FW 3.4 C (4)(c). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 2.4 C (1)(c) should be modified to place the emphasis on meeting refuge purposes, Refuge System mission, and ecological integrity. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We made a related change in the final policy. See 602 FW 3.4 C (1)(d). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The planning policy appropriately makes conservation of biological diversity a major goal of refuge planning (Section 602 FW 1.5 B). What is lacking however, is a simple explanation of what this means. The Service should clarify within this section or in another appropriate place in the policy, that it intends to adopt a regional/ecological approach to conserving biological diversity. Simply put, the Service should ensure that its management activities benefit— and do not harm—those species, habitats, and natural processes that are rare and/or declining within the regional ecological context within which the planning unit occurs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We feel the recommended change is beyond the scope of this policy. A new policy addressing the ecological integrity of the National Wildlife Refuge System is currently being developed and will be published as 601 FW 3 of the Service Manual. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The planning policy needs to refer to the biological integrity policy when relying on that document for guidance. The planning policy also needs to incorporate these fundamental concepts to the extent possible in the absence of clear guidance from the future biological integrity policy. For example, 602 FW 1.3 should be revised as follows (underscored text are changes 
                        <PRTPAGE P="33894"/>
                        from the original language): “Each plan will be 
                        <E T="03">founded</E>
                         on principles of sound fish and wildlife management, available science, 
                        <E T="03">and the maintenance of biological integrity, diversity, and ecosystem health. Each plan will be consistent with</E>
                         legal mandates and our other policies, guidelines, and planning documents.” Amend 602 FW 2.1 to include similar language: “Comprehensive Conservation Plans (CCPs) describe the desired future conditions of a refuge, and provide long-range guidance and management direction for the Refuge Manager to accomplish the purposes of the refuge, contribute to the mission of the System, 
                        <E T="03">ensure that the biological integrity, diversity, and environmental health of the System are maintained,</E>
                         and meet other relevant mandates.” Biological integrity, diversity, and ecosystem health also need to be defined within the planning policy. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have incorporated the suggested text changes, with slight modification, into the final policy. In addition, we have defined the terms biological integrity, biological diversity, ecological integrity, and environmental health. These definitions are consistent with those which will appear in 601 FW 3 (ecological integrity policy). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Add the following language to Section 2.4 C (1)(g): Internal Scoping: “Identify significant opportunities to improve the health of refuge habitats or to improve the functioning of ecological systems.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have addressed the need to identify these opportunities in Section 3.4 C (1)(e).
                    </P>
                    <HD SOURCE="HD2">II. Basing Management Decisions on the Best Available Science </HD>
                    <P>
                        <E T="03">Comment:</E>
                         With regard to developing scientific and other data, such information may be gathered from a number of sources, including the various public comment periods provided by the proposed policy. Thus, when the CCP is presented for public comment, refuge planners should be seeking input and assistance from the scientific community and the public at large, and be responsive to and accountable for considering such scientific input, as would be the case during a notice and comment period under the National Environmental Policy Act (NEPA).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Indeed, we must seek and be responsive to considering the scientific input provided by resource experts, and all other publics, under NEPA. The final policy reflects these points.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 602 FW 2.3 D of the draft policy establishes a goal to  “support management decisions and their rationale by sound professional judgment,” a statement that appears reactive and defensive of status quo operations. To highlight the importance of science in decision making, this goal should be reworded.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We revised the above goal as follows: “To support management decisions and their rationale by using a thorough assessment of available science derived from scientific literature, on-site refuge data, expert opinion, and sound professional judgment.” See 602 FW 3.3 D.
                    </P>
                    <HD SOURCE="HD1">III. Defining Our Relationship With States and Other Agencies and Their Programs</HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter states that in Alaska the Department of Fish and Game is woefully underfunded and the Alaska State Legislature has imposed management “standards” regarding priorities for wildlife management that are inconsistent with the major purposes of National Wildlife Refuges in that state (
                        <E T="03">e.g.,</E>
                         to conserve fish and wildlife populations and habitats in their natural diversity). The commenter states that it is unrealistic to expect that refuge management plans will be the same as State plans especially when dealing with controversial issues. Furthermore, the public, Tribes, and non-governmental organizations should have the same opportunities for participation in the development and review of CCPs as do State and local governments and adjacent landowners.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 668dd (e)(1)(A)(iii) of the National Wildlife Refuge System Administration Act of 1966 as amended by the National Wildlife Refuge System Improvement Act of 1997, instructs the Secretary to “issue a final conservation plan for each planning unit consistent with the provisions of this Act and, to the extent practicable, consistent with fish and wildlife conservation plans of the State in which the refuge is located * * *” We believe that we have an obligation under this and other provisions of the Refuge Improvement Act to work closely with State fish and game agencies as we prepare our plans. It is important to note that the Act calls for our plans to be consistent with State plans “to the extent practicable,” and that our Regional Directors are the ultimate decision makers in the process. Congress directs our close working relationships with the States. We also believe we built sufficient opportunities into the process to allow all interested parties to participate in our planning efforts. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received a number of comments that the refuge planning teams should also include members of State and Tribal conservation agencies.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We changed the policy in Section 3.4 C (1)(a) to state that, “We will provide representatives from appropriate State and Tribal conservation agencies * * * the opportunity to serve on planning teams.” We will provide a formal written request inviting States, Tribes, and other appropriate agencies to join the refuge planning effort at the beginning of the process.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested that States be involved in step-down management plans.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The planning policy guidance provides for and we encourage this opportunity.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters requested that the Service participate in cooperative planning efforts with States and/or other agencies. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have worked closely with many States, other Federal agencies, and others and encourage cooperative management planning for fish and wildlife and natural resources whenever feasible.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some of the commenters questioned whether State agencies could be involved in addressing comments, plan review and implementation.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We encourage State and other agency involvement throughout the planning and management processes—including implementation and review. Furthermore, by being a member of the refuge planning team, State agencies will have a direct opportunity to assure that we accurately reflect or respond to their comments in the CCP document or in our analysis. While we recognize the need for input and feedback from others, we recognize the possibility of debate or alternative management direction, if guided solely by other influences. For this reason, while we encourage full input from the States and other entities in our plans, we retain management and decision-making authority for all units of the National Wildlife Refuge System, including approval of CCPs.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters asked about other possible partnerships with the Service, beyond CCPs, such as joint ventures and ecosystem planning.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We are appreciative of the interest of States and other organizations who wish to participate as a partner in our refuge and non-refuge projects. We encourage partnerships through our ecosystem approach. We invite agencies and organizations to contact our Regional Offices for more information on how to participate as a partner in our activities.
                        <PRTPAGE P="33895"/>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters questioned what determines adequate coordination with States, other agencies, and the public. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Adequate coordination with States, Tribes, other agencies, and the general public includes an invitation to participate, actual participation in our processes, regular and good communication, use of appropriate tools and materials to aid coordination, a sense of teamwork from all parties, and resulting successful partnerships beyond the planning phase. The Service's refuge planning policy developed herein provides for all the processes and procedures for us to meet our burden of responsibility, in regard to agency coordination. 
                    </P>
                    <HD SOURCE="HD2">IV. Identifying Biological Information Necessary for Planning and Management </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Criteria should be established for assessing the adequacy of data for making management decisions. The Service should consider delaying management choices until adequate information is available to make a decision informed by science. The U.S. Forest Service proposed planning rule states that if data are not adequate, this triggers a new or supplemental broad-scale assessment or local analysis before proceeding to decision making. It is suggested that the Service consider a similar modification of the proposed policy. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In situations where we are unable to develop new data for the CCP, the plan may identify the need for further data collection. In such cases we may delay decision making, pending additional data collection and analysis. There are many sources of data that can aid in plan development. We include a list of potential data sources in 602 FW 3.4 C (1)(e). A lack of data should not delay completion of the CCP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A number of commenters requested that the Service expand and clarify its policy and procedures for collection of data associated with CCPs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Based on the comments received, we have made extensive changes to Sections 3.4 C(1)(e) and (f), including additional discussion on data needs, data collection, data sources, use of outside experts and literature reviews, and data standards. 
                    </P>
                    <HD SOURCE="HD2">V. Clarifying Under What Conditions We Should Revise a CCP </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Additional guidance is necessary to clarify the limits of the adaptive management strategy. The Service's intention of revising a CCP every 15 years after establishment of the initial CCP comports with the requirements set forth in the Refuge Improvement Act. Moreover, the Service indicates that it will revise a CCP sooner than 15 years after the initial CCP is approved, “if conditions that affect the refuge or planning unit change significantly.” It is unclear at what point or under what conditions the CCP should, or must, be reviewed or reassessed, prior to the expiration of the 15-year period. The commenter believes that both the Refuge Manager and the public need further guidance as to when a review should be conducted as a result of changing ecological or other conditions presented to the refuge environment, including changes in science which may render a certain use obsolete or no longer compatible with the purposes for which the refuge was established. The Service should amend the draft policy so as to establish as near of an objective standard as possible, and include guidelines and examples for the use of refuge planners. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have modified Step 8, “Review and Revise Plan,” to provide additional guidance. We have revised Subsection (a) to instruct refuge planners and managers to “Modify the plan and associated management activities whenever monitoring and evaluation determine that we need changes to achieve planning unit purpose(s), vision, and goals.” Subsection (b) now states: “Revise the CCP when significant new information becomes available, ecological conditions change, major refuge expansion occurs, or when we identify the need to do so during plan review.” While these revisions are minimal, we believe we must provide additional guidance dealing with the principles of adaptive management and monitoring. However, we do not believe this type of guidance is appropriate in our planning policy. 
                        <E T="03">Fulfilling the Promise: The National Wildlife Refuge System</E>
                         includes a number of recommendations focused on developing programs for natural resource inventory and monitoring, habitat monitoring, and adaptive management. Once we fully implement these recommendations and establish programs, we will provide appropriate guidance and initiate training courses. Only then will we be able to utilize the principles of adaptive management to refine our approaches and determine how effectively we are accomplishing refuge goals and objectives. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters asked the Service to clarify what level of planning and plan revision is required for refuges. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Chapter 1 of the policy provides a general description of planning requirements. Chapter 3 (formerly Chapter 2) deals specifically with CCPs. Section 3.4 C(8) provides details on plan revision. In general, all newly established refuges will have a Conceptual Management Plan in place at the time of refuge establishment. We will develop CCPs as soon as possible but not later than 15 years after establishment of a refuge. We will review CCPs annually and make revisions as needed. We will revise CCPs at least every 15 years. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters were concerned that a change of management direction could occur with a change of Refuge Manager. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The planning policy states that the Refuge Manager shall manage the refuge under an approved CCP, and that plan revision should occur only when monitoring and evaluation documents the need for change in order to achieve planning unit purpose(s), goals, and objectives. The Regional Director approves the CCP with input and concurrence from many levels within the Service, as well as outside review and comment. 
                    </P>
                    <HD SOURCE="HD2">VI. Expediting or Further Clarifying Our Planning Process </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Implementing a “Public Participation Plan” early in the planning process before developing alternatives or drafting the plan will help the Service identify issues and define the desired future condition(s) of a particular refuge. Extra effort will be needed at this step of the process in order to establish a firm foundation for subsequent planning phases. Additional guidance would be helpful to ensure refuge planners make this effort. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We require the preparation of a “Public Participation Plan” (referred to as a “Public Involvement/Outreach Plan”) in Step 1, “Preplanning: Planning the Plan,” of our Comprehensive Conservation Planning process. We also provide guidance on preparing a “Public Involvement/Outreach Plan” during the Refuge Comprehensive Conservation Planning course offered at our National Conservation Training Center. This course is available to Service personnel and other planning team members who are about to begin the preparation of a refuge CCP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Integrating the CCP with various Environmental Assessments (EA)/Environmental Impact Statements (EIS) from the outset may not achieve the planning expediency that it is intended to achieve. To save time and money, it is suggested that the first step in the CCP process should be the development of a stand-alone “vision document” that generally describes the 
                        <PRTPAGE P="33896"/>
                        goals of the refuge and its desired future condition. After the goals of the refuge and its desired future condition are documented and agreed upon, then various EAs/EISs can be developed as a mechanism to examine the alternatives on how to achieve them. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         There is no need for a stand-alone vision document. The refuge vision statement and goals are integral parts of our CCP process. Identified in Step 1, “Preplanning: Planning the Plan,” we subsequently share them with the public in Step 2, “Initiate Public Involvement and Scoping,” and, based on the public's comments, modify them as appropriate in Step 3, “Review Vision Statement and Goals and Determine Significant Issues.” We ultimately use them to help identify our Proposed Action in the draft NEPA document in Step 4, “Develop and Analyze Alternatives, Including the Proposed Action.” The proposed action will be the one that best achieves the refuge purpose(s), vision, and goals; helps fulfill the Refuge System mission; maintains and, where appropriate, restores ecological integrity; addresses the significant issues and relevant mandates; and is consistent with principles of sound fish and wildlife management. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Incorporating “compatibility determinations” within the CCP process is a laudable goal. However, in light of the previously completed determinations, it may be advisable to allow this process to have its own time line independent from, but monitored by, the CCP process. These determinations may be examples where interim modifications (of the size or scope that would not require reopening the planning process) are needed between scheduled planning cycles. Additional guidance may be necessary to help determine when, where and how these interim modifications are made. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that incorporating compatibility determinations in our refuge CCPs is both efficient and makes good sense. The degree of public review and opportunities to comment provided in the CCP process will be more than adequate to fully comply with the provisions of the National Wildlife Refuge System Improvement Act of 1997. We believe that we will be able to accommodate most, if not all, interim modifications required for these determinations through the revision procedures of the process. While we will likely accommodate many of these modifications without reopening the entire planning process, we will undoubtedly reopen some. The process will be able to accommodate both situations. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed the concern that the lack of specific data should not impede the planning process, but rather incorporate and identify this shortcoming as a specific need of a particular refuge in the planning process. While the draft policy specifically mentions that the CCP can identify data needs as part of the plan, it does not provide direction to the effect that the planning process should continue and not be stalled as a result of incomplete data. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We revised the text of the policy in Step 1, “Preplanning: Planning the Plan, (e) Planning Area and Data Needs,” to indicate that “While we may not be able to develop new data for the CCP, we may identify the need for further data collection. A lack of data should not delay the completion of the CCP.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A concern has been raised regarding the “Internal Reviews” of the CCP, or subparts thereof, that are called for in the draft policy. In each reference to internal reviews, the draft policy directs that these should be conducted by “* * * following established regional procedures,” yet fails to identify what these procedures may be. The commenter believes that additional guidance is needed to provide a greater degree of consistency to the manner in which internal reviews are conducted. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The “established regional procedures” to which we refer deal primarily with the internal distribution of documents. We have revised the text of the policy in both Step 5, “Prepare Draft Plan and NEPA Document, (d) Internal Review,” and Step 6, “Prepare and Adopt Final Plan, (c) Internal Review,” to provide further guidance on the internal distribution of documents to include: “* * * refuge program managers, ecosystem managers, refuge staff and other appropriate Service programs and divisions, as well as other agency partners.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         From a public participation point of view, a commenter recommends that a generalized description of the types of circumstances in which “categorical exemptions” may be invoked would be helpful to include in the final policy. Another commenter noted that Section 2.4 C (8)(b) states that CCPs will be periodically reviewed and revised “* * * generally through the use of a categorical exclusion.” It was requested that the Service define exactly what category of actions, either individually or cumulatively, it determines will not have a significant effect on the human environment (40 CFR 1508.4). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         When revising a CCP, we expect our decision makers to ensure that, when we can categorically exclude an action, the action does, in fact, comply with the requirements and limitations described in the categorical exclusion. Because most categorical exclusions apply to a variety of our actions and different program activities, it is not possible, nor desirable, to address in this policy all possible actions or situations covered by a given categorical exclusion. Our NEPA policy already provides such guidance (see 550 FW 3.3). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The opening section of Part 602, (National Wildlife Refuge System Planning), Chapter 2, (Comprehensive Conservation Planning Process), says: “it is not the intent of this policy to provide step-by-step direction on how to prepare a CCP but rather to establish the requirements and standards to which we will hold all CCPs.” However, “requirements and standards” are either non-existent or very weak. Instead, the subsequent sections primarily describe the steps of the planning process. This is particularly apparent when it comes to wildlife-dependent recreational uses. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have revised the text of the policy in Section 3.1 (formerly Section 2.1), “What is the purpose of this chapter?,” to read, “This policy provides guidance, step-by-step direction, and establishes minimum requirements for all CCPs.” We will address the “requirements and standards” to which we originally referred in Part 601 of the Service Manual, “Mission, Goals, and Purposes of the National Wildlife Refuge System,” as well as through recommendations in 
                        <E T="03">Fulfilling the Promise: The National Wildlife Refuge System.</E>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         After describing the steps to be taken to ensure public involvement in the scoping process in Section 2.4 B(2), the policy requires a review of the vision statement and goals to determine significant issues (Section 2.4 B(3)). Item B(3) says, “based on this review, modify the vision and goals for the planning unit as appropriate.” The planner needs to keep in mind that Congress has set certain policies and requirements for the administration of the Refuge System. The following sentences should be added to B(3)(a):
                    </P>
                    <P>
                        “We need to keep in mind that the law sets forth some very specific policies and requirements for the administration of the Refuge System. These include the basic mission of the System and the direction that compatible wildlife-dependent recreation is a legitimate and appropriate general public use of the 
                        <PRTPAGE P="33897"/>
                        System, directly related to the mission of the System and the purposes of many refuges. Regardless of what may or may not develop during the public involvement and scoping process, the law requires that wildlife-dependent recreational uses be facilitated and expanded.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Step 2, “Initiate Public Involvement and Scoping,” instructs the planner to involve the public and gather comments on the existing vision statement, goals and objectives, potential issues, management actions and concerns, significant problems or impacts and opportunities or alternatives to resolve them. This is the very essence of the scoping process mandated by NEPA. Step 3, “Review Vision Statement and Goals and Determine Significant Issues,” further instructs the planner to review and evaluate the public's comments on the vision statement and goals and modify them as appropriate. It may not be appropriate to modify them based on the comments received. Professional planners understand that decisions are not based on majority opinion, and we charge them with making certain the public understands this most basic tenant of NEPA. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The Service properly states that one of the goals for the CCP is to “ensure that we manage each refuge to fulfill the mission of the System as well as the specific purposes for which we established that refuge.” The purposes for which the refuge was established should be the very foundation of every CCP. Thus, each CCP should begin with a recitation of the goals for which that particular refuge was established, as enunciated in the text of the refuge's authorizing documentation, and a narrative of how those goals relate to and fulfill the NWRS mission. Such an approach would not only ensure adherence to the refuge's purposes and Refuge System mission, but would be consistent with the intent of Congress in enacting the Refuge Improvement Act. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Step 1, “Preplanning: Planning the Plan,” now includes a new Subsection (b) Identify Refuge Purpose(s), History, and Establishing Authority. We instruct those preparing CCPs to “Document the history of refuge establishment and management, as well as refuge purposes and authorizing authority * * *” which “* * * will become driving forces in the process * * *” This is the first task the newly formed planning team undertakes, and we include this important material in Chapter I, “Introduction/Background” of the CCP (also see Exhibit 3-4).
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The Service's proposed policy would require additional expenditures of time on the part of FWS personnel, particularly Refuge System field personnel. There is concern that the demands imposed on Refuge Managers and their staffs by these proposed planning and related NEPA compliance requirements will adversely affect refuge staff's ability to maintain their commitment to current refuge operations, if additional funds and personnel are not made available. Thus, it is imperative that the level of commitment on the part of the Service toward proper planning and administration of the Refuge System be matched by a commitment from the Department of the Interior and Administration to seek an appropriate level of funding on a yearly basis, to provide additional staff and other resources, where needed. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize this potential problem. Congress increased our budget in 1996 to include funding dedicated to the preparation of CCPs. Our regional and field offices are using these funds to provide professional planning staff and services to assist refuge field personnel in the preparation of their plans. The CCPs themselves also will document the increased staffing and funding levels required for their full implementation. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Public participation is critical to the administration of a refuge and the Refuge System. Proposed Section 2.4 C (2)(a) appears to only provide the public with the ability to comment on the Notice of Intent to prepare a CCP only if the Service intends to prepare an EIS for the CCP. The public should have the ability to provide public comments as part of the scoping process when the Service intends to prepare a CCP, whether or not an EIS is drafted. This section should be amended to make clear that a comment period will follow the publication of a Notice of Intent to prepare a CCP, whether or not the Service intends to prepare an EIS, and if later in the process the Service decides to prepare an EIS, a public comment period would follow that announcement as well. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We did not intend to limit public participation during the scoping process. We have revised the text to remove any possible misconceptions concerning our desire to openly solicit public comment throughout the scoping process, whether or not we prepare an EIS. We have modified Section 3.4 C (2)(b) (formerly Section 2.4 C (2)(b)) to read: “Public scoping will continue until we prepare a draft CCP/NEPA document.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Amend the proposed public review period for a draft CCP/NEPA document to provide a 60-day comment period for an EA, as well as the currently proposed 60-day comment period when an EIS is to be drafted. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We modified the final policy (see 602 FW 3.4 C (5)(e)) to read, “Provide a minimum of 30 days for public review of a draft CCP with an EA and 45 days for a draft CCP with an integrated EIS.” The comment periods noted reflect the minimum comment periods authorized under current NEPA policies. We recognize that under many circumstances the comment period associated with a particular CCP will often be much longer depending on the nature and complexity of the plan. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Scientific data, collected from governmental and non-governmental organizations, academia and other sources are vital to refuge planning. Although the Service's draft policy acknowledges this importance, we feel that identifying the need for additional data is of equal importance to acknowledging the existence of data already in hand. The current reading of Section 2.4 C (1)(d) states that the planner “
                        <E T="03">can</E>
                         identify the need for additional data.” Such language does not adequately emphasize the importance of developing additional data. Hence, we recommend that the last sentence of 2.4 C (1)(d) be modified as follows: “You do not need to develop new data at the time of drafting the CCP. If current data exists, the CCP should state so and summarize the existing data; if no current data exists, the CCP should state so, and identify to the extent possible the type of data that will need to be developed.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have substantially revised the text of Section 3.4 C (1)(e) (formerly Section 2.4 C (1)(d)) based on a number of comments we received. 
                    </P>
                    <P>
                        <E T="03">Comment: 1.6 K. Planning Team Leader.</E>
                         Revise last sentence to read: “The Planning Team Leader manages the refuge planning process, and ensures compliance with applicable regulatory and policy requirements.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We made the recommended change in the final policy. See 602 FW 1.6 Q. 
                    </P>
                    <P>
                        <E T="03">Comment: 1.8 E. Planning Team Leader.</E>
                         Revise second sentence to read: “The Planning Team Leader, in consultation with the Refuge Manager, is responsible for identifying appropriate and proper representation on the interdisciplinary planning team.* * *” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We made the recommended change in the final policy. See 602 FW 1.8 E. 
                    </P>
                    <P>
                        <E T="03">Comment: 1.8 F. Refuge Supervisor.</E>
                         Insert at the end: “Once the plan is approved by the Planning Team Leader 
                        <PRTPAGE P="33898"/>
                        and the Refuge Manager, the Refuge Supervisor will also be responsible for review and approval of the plan prior to its submission to the next approval level.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We made the recommended change, with slight modification, in the final policy. See 602 FW 1.8 F. 
                    </P>
                    <P>
                        <E T="03">Comment: 1.8 G. Refuge Manager.</E>
                         Revise second sentence to read: “The Refuge Manager assures that the refuge staff participates in plan development, and is responsible for its content in terms of information relating to management of refuge resources and use activities.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The latter is the responsibility of the entire planning team, and not just the Refuge Manager. We have added this responsibility to 1.8 H., “Planning Team.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 1.2, “What does Part 602 apply to?” should be amended to include at the end of the sentence, “except coordination areas,” to be consistent with Section 1.6 C, which states “[w]e do not require CCPs for Coordination Areas.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         To clarify, Part 602 includes four parts. Part 602 FW 1 is a general overview of refuge planning and addresses more than just CCPs. It applies to all units of the National Wildlife Refuge System. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Although recreational and commercial trapping are clearly “wildlife-dependent recreational uses” of the Refuge System, it is unclear whether the planning policy requires compatibility determinations for these activities. Although the Refuge Improvement Act does not identify trapping as a “priority use” of the Refuge System, trapping is still a “wildlife-dependent recreational use” and should therefore mandate production of a compatibility determination, with full public review and comment. This point should be clarified in the planning policy. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         If a refuge plan included trapping as a use in our proposed action, it would require a compatibility determination under the provisions of this policy. We believe we adequately addressed this concern in Step 5, “Prepare Draft Plan and NEPA Document, Subpart (b) Compatibility Determinations.” This subpart requires refuge planners to “Complete new compatibility determinations or re-evaluate existing compatibility determinations as part of the CCP process for all individual uses, specific use programs, or groups of uses associated with the proposed action, when adequate information is available and where possible.” It further requires that we incorporate the draft compatibility determinations into the draft CCP as an appendix and obtain the required public review and comment as part of the draft CCP and NEPA document. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The draft policy only lists trapping as a component of “Population Management” in its list of step-down management plans in Section 3.5 of Part 602 FW 3. Step-down management plans are required for all hunting and fishing programs, but not for recreational and commercial trapping. The commenter interprets this to mean that commercial and recreational trapping will not be allowed on the National Wildlife Refuge System. If this interpretation is incorrect and commercial and recreational trapping will be allowed on the Refuge System, then the draft planning policy should include a step-down management plan for this wildlife-dependent recreational activity. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The commenter's interpretation is incorrect. Commercial and recreational trapping may be allowed on a refuge, but only if done as part of “Population Management.” As the commenter notes, we include “Population Management” in the list of step-down management plans. If trapping is to be a part of the management of wildlife populations, such as management of furbearer populations, protection of facilities, or controlling problem predators, we would require the refuge to address trapping and associated means of the population management program in such a plan. The reason that trapping does not appear on the list of priority wildlife-dependent recreational uses is that only the six activities listed therein are specifically identified in the Refuge Administration Act. Other refuge uses, whether listed on the list of step-down management plans specifically, or under a general category, will require planning and compliance, including a compatibility determination. As such, the current reference to trapping in 602 FW 4, Section 4.5, under “Population Management” was intentional and is correct. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The Service needs to disentangle NEPA from the CCP process. To that end, the commenter recommends that we revise Section 2.4 to require that an EA or an EIS be a document entirely independent of the CCP process. Alternately, the commenter requests that we justify the legal distinction behind the determination to integrate a NEPA document within a CCP and a determination to forego integration. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The language in Section 3.4 B (formerly Section 2.4 B) is correct. The Council on Environmental Quality's (CEQ) regulations require that “to the fullest extent possible, agencies shall prepare draft environmental impact statements concurrently with and integrated with environmental impact analyses and related surveys and studies required by the Fish and Wildlife Coordination Act (16 U.S.C. 661 
                        <E T="03">et seq.</E>
                        ), the National Historic Preservation Act of 1966 (16 U.S.C. 470 
                        <E T="03">et seq.</E>
                        ), the Endangered Species Act of 1973 (16 U.S.C. 1531 
                        <E T="03">et seq.</E>
                        ), and other environmental review laws and executive orders” (40 CFR 1502.25). The regulations also tie a similar requirement to the preparation of environmental assessments (40 CFR 1501.7(b)(3)). The confusion lies in the fact that the development of alternatives, analysis of impacts, and public participation occurs throughout this integrated process, up until the agency makes the final decision in the Record of Decision (ROD) (for an EIS) or a Finding of No Significant Impact (FONSI) or decision to prepare an EIS (for an EA). However, after the agency has made a decision on the content of the CCP, the CCP serves as the management plan for the Service. The NEPA document is useful then as a reference and to ensure that the Service maintains its commitment to the actions it intended to take, as analyzed in its NEPA document. The final policy recognizes the independent nature of the CCP following the completion of the integrated process. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The draft policy authorizes the continuance of wildlife-dependent recreational uses on an interim basis for lands newly acquired into the Refuge System, pending completion of a CCP. Section 2.4 (5)(d) states: “* * * the draft CCP and NEPA documents also must identify any existing wildlife-dependent recreational uses occurring on those lands. Also identify those uses deemed compatible that we may allow to continue on an interim basis once we acquire the lands, pending completion of a CCP.” However, it is unclear what authority makes an interim compatibility determination for such wildlife-dependent uses. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 668dd(d)(3)(A)(ii) of the National Wildlife Refuge System Administration Act of 1966 as amended by the National Wildlife Refuge System Improvement Act of 1997, states that: “On lands added to the System after March 25, 1996, the Secretary shall identify, prior to acquisition, withdrawal, transfer, reclassification, or donation of any lands, existing compatible wildlife-dependent 
                        <PRTPAGE P="33899"/>
                        recreational uses that the Secretary determines shall be permitted to continue on an interim basis pending completion of the comprehensive conservation plan for the refuge.” We will use our compatibility policy to make such determinations. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 2.4 B (6)(i), Part 602 FW 2 states that “[I]n some cases, we may require a 30-day public review period for the FONSI.” However, the proposed policy does not define what will trigger public review. This section should be revised to outline the criteria FWS will use to make this determination. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The CEQ established criteria for requiring such a review in the “Regulations for Implementing the Procedural Provisions of the National Environmental Policy Act” (40 CFR 1500-1508), and Executive Orders 11988 (Floodplain Management) and 11990 (Protection of Wetlands). The regulations require public review “* * * (a) if the proposal is a borderline case, 
                        <E T="03">i.e.,</E>
                         when there is a reasonable argument for preparation of an EIS; (b) if it is an unusual case, a new kind of action, or a precedent-setting case such as a first intrusion of even a minor development into a pristine area; (c) when there is either scientific or public controversy over the proposal; or (d) when it involves a proposal which is or is closely similar to one which normally requires preparation of an EIS.” The executive orders require public review if a proposed project would be built in and negatively impact a floodplain or wetland. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Exhibit 2 lists 41 statutes and executive orders that must be considered during Comprehensive Conservation Planning. All of the listed statutes and executive orders provide for environmental or cultural protections while the authorities applying to FWS land management responsibilities are missing. The list would be complete if the following statutes and executive orders were added: 
                    </P>
                    <P>1. Executive Order 12866 requiring economic impact analyses of any Federal action. </P>
                    <P>2. Regulatory Flexibility Act requiring the evaluation of the effects of any proposed action on small entities. </P>
                    <P>3. Mining and Minerals Policy Act of 1970 that applies to the Secretary of the Interior in carrying out any program as may be authorized by any law. </P>
                    <P>4. National Materials and Minerals Policy Research and Development Act of 1980, which mandates similar requirements as under the Mining and Minerals Policy Act. </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not intend the list of statutes and executive orders in Exhibit 3-2 to be all inclusive. It is simply a list of some of the more common ones that apply to many refuges. Other statutes and executive orders, such as those cited, also must be taken into consideration by the refuges to which they specifically apply. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The policy should have better requirements for public involvement so there is a consistent way for the public to be involved throughout the Refuge System. One commenter recommends the requirement for 
                        <E T="04">Federal Register</E>
                         notices for all CCPs at the scoping and public review stages, in addition to notices in local newspapers or radio. In many areas, refuge offices are not located within the actual refuge areas, so greater effort needs to be made to involve the public. Public notification and opportunity for comment should be required for all CCPs at the scoping phase when plan development or revision is initiated, in addition to a 30-60 day or more public comment period for draft plans. Copies of draft and final plans should be made available to any member of the public upon request and on a website. Statements that FWS shall “develop and implement a process to ensure active public participation” (see “Planning and the NWRSIA-97) give a minimum standard that is woefully inadequate and sets the stage for poor performance. Although later sections of the policy better explain notice and comment procedures, there are loopholes indicating that not all CCPs will require full public input and review. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The policy, as currently written, requires full public input and review for all CCPs. Step 1, “Preplanning: Planning the Plan,” requires the preparation of a Public Involvement/Outreach Plan for each CCP, and notes that “We integrate public involvement and outreach into each step and it continues throughout the planning process.” Step 2, “Initiate Public Involvement and Scoping,” requires that we publish a Notice of Intent in the 
                        <E T="04">Federal Register</E>
                         for each CCP, and “Using news releases to the local media and other appropriate means, (to) notify the affected public of the opportunity to participate in the preparation of the CCP * * *” Step 2 also notes that “Public scoping will continue until we prepare a draft CCP/NEPA document.” Step 5, “Prepare Draft Plan and NEPA Document,” requires that we publish a Notice of Availability in the 
                        <E T="04">Federal Register</E>
                         for each CCP, and “Notify the affected public of the availability of these documents through other appropriate means, as identified in the Public Involvement/Outreach Plan.” Step 5 also requires that we “Conduct appropriate public involvement activities as called for in the Public Involvement/Outreach Plan.” Step 6, “Prepare and Adopt Final Plan,” requires that we “Prepare a summary of the public comments received and a statement of the disposition of concerns expressed in those comments * * *” Step 6 also requires that we publish a Notice of Availability of the final approved CCP and NEPA document(s) in the 
                        <E T="04">Federal Register</E>
                        . Step 8, “Review and Revise Plan,” calls for us to “Continue informing and involving the public through appropriate means.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter commended the Service's statements in the draft planning policy that new wilderness reviews be conducted as one of the “required elements” of the CCP planning process but expressed disappointment that the draft policy does not provide guidance on how to conduct a wilderness review. (In fact, it alludes to a policy that has yet to be written.) Worse still, the policy includes a loophole that would allow refuges to defer wilderness reviews indefinitely. (A footnote to the policy reads: “Some of these required elements may not be available. In these cases, you need to develop objectives or strategies in the plan to acquire that information.”) 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that our policy on National Wildlife Refuge System planning is the proper place to provide detailed guidance on conducting wilderness reviews. We will provide this guidance in the forthcoming Director's Order on “Wilderness Review and Evaluation.” This Director's Order will provide guidance on conducting wilderness reviews pending completion of Part 610 of the Fish and Wildlife Service Manual, “Wilderness Management.” Concerning the “loophole,” we have removed the footnote from Exhibit 3-3. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Amend the policy to ensure that the vision statement for the refuge is clearly tied to the mission of the Refuge System, the purposes of the refuge, and the maintenance and restoration of biological integrity, diversity, and environmental health. The draft policy does not appear to provide guidance on the preparation of appropriate refuge visions. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have revised the definition of “Vision Statement” accordingly. See 602 FW 1.6 Z. We also have added additional guidance on the preparation of refuge vision statements to 602 FW 3.4 C (1)(g). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested that the Service add 
                        <PRTPAGE P="33900"/>
                        information on the history of settlement, land use, and land tenure of the refuge planning area. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have modified the policy by adding this item to Section 3.4 C (1)(e) and the Refuge Planning Checklist (Exhibit 3-3). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some comments were made about the National Wildlife Refuge System compatibility policy and process and the need to further explain its relationship to refuge planning. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         When preparing Comprehensive Conservation Plans (CCPs) and Conceptual Management Plans, refuge planning teams will use the compatibility process outlined in the agency's compatibility policy as defined in regulations. (See 603 FW 2 of the Service Manual.) We do not find it necessary to duplicate this information herein. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested that CCPs should provide supporting documentation and rationale for refuge objectives. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have modified Section 3.4 C (4)(d) (Objective Development) to require that CCPs include a short narrative summary, including appropriate literature citations, which provides the rationale for each objective. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested additional information on adaptive management and monitoring. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The refuge planning policy only touches on the need for adaptive management and monitoring to assure that we are meeting refuge purposes, goals, and objectives and that management strategies are appropriate. We will develop additional Service policy and guidance on both the adaptive management process and monitoring. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested that the policy include examples of planning products, such as statements for refuge goals, objectives, and strategies. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We find that having a number of examples in the actual policy is not appropriate. What we have done and will continue to improve upon, is to provide a handbook on developing quality goals, objectives, and strategies. Also, the National Conservation Training Center course on Refuge Comprehensive Conservation Planning provides both a training session as well as an expanded guide of resource material, including many examples of planning products. It is our intent to keep this information current and up-to-date with the best available information and examples. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Comments were raised which asked us to identify the standards for measuring Service success in achieving Refuge System and refuge planning goals. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In general, our measure of success is as follows: (1) complete plans; (2) implementation is preceding; and (3) monitoring and evaluation are under way to help assess and determine successful management actions. Additionally, we are in the process of developing a new policy chapter for the National Wildlife Refuge System, which will include identification of Refuge System goals. We have identified refuge planning goals in Chapter 1 of our planning policy. We also have initiated a process for national review of refuge CCPs to help us evaluate our planning process and products, including the capability to measure our successes and establishing standards to assure we are achieving our goals. We also are developing further guidance on adaptive management and monitoring, which will play key roles in determining the success of the refuge planning process. We sense that it may take a number of years until we can make an adequate assessment of the planning process and the resulting products before we can fully identify such measures and standards. As we further develop and refine this information, including it in future updates of the refuge planning policy will be appropriate. We invite feedback from the public and other agencies on our successes and needs for refinement throughout our planning efforts. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters asked how we would determine whether a CCP should be prepared for a single refuge or a complex of refuges. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We will determine the scope of a CCP on an individual, case-by-case basis. Developing a CCP or CCPs for an administrative complex of refuges is ecologically efficient and generally our desired approach. However, in many cases, doing single refuge plans, or plans for less than an entire refuge complex, may be more effective and efficient. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some questions were raised about the lead responsibilities, coordination and organizational relationship for developing CCPs within the Service. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Refuges and Wildlife Program has the lead in preparing plans (see “Who is responsible for implementing our policy?,” 602 FW 1.8). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A recommendation was made to provide a review copy of the draft CCP to all resource experts who contribute to a CCP's development. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We changed the policy in Section 3.4 C(5)(e) to reflect this recommendation. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters requested that the Service clarify the definition of “objective,” and expand upon the description of the objective development process, including explaining how objectives should be worded. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have included a revised definition of objectives in Section 1.6 N and a revised and expanded description of the objective development process in Section 3.4 C(4)(d). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 602 FW 1.3 and various other sections in the draft policy indicate that the plans will “contribute to” the System mission. In each such instance, the phrase “contribute to” should be replaced with the word “fulfills.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We slightly modified the recommended change in the final policy to read, “help fulfill the Refuge System mission.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The policy should call for bold vision statements of what the planning unit should be, or what we hope to do. The draft language in Section 602 FW 1.6 S uses words that are passive and indirect (what the planning unit “could be”). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We made the recommended change in the final policy. See 602 FW 1.6 Z. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 2.4 C(1)(d) should be modified to place the emphasis squarely on conservation of wildlife, habitat, and biological integrity, where it belongs. The Service should establish a two-stage process that first identifies and describes the management steps that are necessary to accomplish the first priority (“wildlife first”) and only then determine what opportunities for wildlife-dependent recreation will be provided (“wildlife-dependent recreation second”). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Refuge Improvement Act clearly states that wildlife comes first on refuges. We only would allow those wildlife-dependent uses deemed compatible and appropriate to occur. Section 602 FW 3.4 C(1)(e) (formerly Section 602 FW 2.4 C(1)(d)) identifies the steps in preplanning. At this stage we are gathering information only. Hence, we see no need to establish a two-stage process as suggested. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A two-stage process is also recommended for determining goals and objectives: wildlife comes first, wildlife-dependent recreation comes second. There is a fear that the draft policy would mix wildlife conservation and recreation together. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Again, we see no need to establish a two-stage process as suggested. The Refuge Improvement Act makes it quite clear that wildlife comes first on National Wildlife Refuges. 
                        <PRTPAGE P="33901"/>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 602 FW 2.4 C(1)(d) states that “You do not need to develop new data for the CCP.” This statement belies the commitments in Fulfilling the Promise to address the Refuge System's biological shortcomings. This sentence should be replaced with an admonition that a certain level of information is necessary before the planning process can be initiated in earnest. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We made the recommended change in the final policy. We modified 602 FW 3.4 C(1)(e) (formerly 602 FW 2.4 C(1)(d)) to read: “While we may not be able to develop new data for the CCP, we may identify the need for further data collection. A lack of data should not delay the completion of the CCP.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 602 FW 2.4 C(1)(d)(i) should be reworded to ensure that CCPs identify and describe the “
                        <E T="03">current and historic</E>
                         distribution, migration patterns, and abundance of fish, wildlife, and plants  * * *” In addition, this section should be amended to identify and describe “those fish, wildlife, and plants that are rare and/or declining within the regional ecological context within which the planning unit occurs.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Although we added the suggested language regarding rare and/or declining species to the final policy (see 602 FW 3.4 C(1)(e)(vii)), language pertaining to the “distribution, migration patterns, and abundance of fish, wildlife, and plants” remains unchanged to be consistent with language that appears in the Refuge Improvement Act. To help address the commenter's concern, we modified 602 FW 3.4 C(1)(e)(v) in the final policy to read, “Current and historic description of the flora and fauna, and the diversity of habitats and natural communities.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 602 FW 2.4 C(1)(d)(iii) should be reworded to ensure that CCPs identify and describe the “current and historic diversity of habitats and natural communities and those habitats and communities that are rare and/or declining within the regional ecological context within which the planning unit occurs.” In addition, Section 602 FW 2.4 C(1)(d)(vii) should be reworded to ensure that the plans identify and describe the “current and historic role of fire and other natural processes.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We incorporated the suggested changes, with slight modification, into the final policy. See 602 FW 3.4 C(1)(d)(v), (viii), and (xiii). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 602 FW 2.4 C(2)(c) should be modified so as to ensure that planners “identify any new information, issues, concerns * * *” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We made the recommended change in the final policy. See 602 FW3.4 C(2)(c). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 602 FW 2.4 C(4)(d) should be modified to adopt a System-wide general policy for implementing the Refuge Improvement Act's monitoring requirement. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         A System-wide policy that addresses monitoring within the Refuge System already exists in 701 FW 2 of the Service Manual. We are currently revising this policy guidance and will address the monitoring mandates of the Refuge Improvement Act, as necessary. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Concurrent with the publication of the final planning policy, the Service must publish interim guidance on how wilderness reviews are to be conducted. The guidance should state that the reviews should include: (1) An inventory of all qualifying areas, (2) an analysis of the suitability for their designation as wilderness, and (3) a recommendation for wilderness designation. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We expect that both the interim and final policy on wilderness will include inventory, study, and recommendation as steps needed to complete wilderness reviews. The inventory of the refuge should be broad-based to determine what areas would qualify as wilderness. The study would analyze in detail the resources, values, uses, and other characteristics of the qualifying areas (Wilderness Study Areas). The recommendation follows the study and would depend on its conclusions. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 1.7 A should be modified by adding “or critical habitat designations or proposals” after the words “endangered species recovery plans.” In addition, Section 2.4 C(1)(d)(xiii) should be amended to read “Existing special management areas 
                        <E T="03">or designations</E>
                         (
                        <E T="03">e.g.,</E>
                         wilderness, 
                        <E T="03">critical habitat designation or proposal,</E>
                         research natural area * * *).” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe the recommended change is unnecessary since the list is not meant to be all inclusive. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A new Section 2.4 C(1)(d)(xiv) should be added that indicates “Opportunities to reintroduce endangered, threatened, candidate, or other rare species to the planning unit.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe this information is appropriate to include in a section dealing with preplanning data needs (602 FW 3.4 C(1)(e)). Such actions would be more appropriate to include in the range of alternatives in the NEPA document. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 602 FW 2.4 C(5)(a) should be modified as follows: “Ensure that no activities are authorized on a national wildlife refuge that may interfere with the recovery of a threatened or endangered species, and ensure compliance regarding other programs and policies, including the Clean Water Act * * *” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe the current language in 602 FW 3.4 C (5)(a) that states “Ensure compliance regarding other programs and policies, including Section 7 of the Endangered Species Act; Sections 401 and 404 of the Clean Water Act * * *” already addresses the above concerns. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 1.5 F should be amended to reflect the Refuge Improvement Act by adding at the end “and to ensure that these uses receive enhanced consideration over general public uses in the Refuge System.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We made the recommended change in the final policy. See 602 FW 1.5 G. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 2.4 C (1)(d) should be amended by adding at the end a new paragraph “(xv) Conflicts that may occur or be expected to occur between non-priority uses and priority uses of the planning unit.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe this information is more appropriate in the section dealing with environmental consequences (602 FW 3.4 C (4)(f)) rather than the section dealing with preplanning data needs (formerly 602 FW 2.4 C (1)(d)). We made the suggested change in the final policy. See 602 FW 3.4 C (4)(f). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Planning requirements should be issued as regulations not as policy. Comprehensive Conservation Planning is an integral part of the Refuge Improvement Act, and issuing planning regulations to implement the Act is entirely consistent with Congressional and Administrative intent to promulgate nationally consistent plans for the Refuge System. This is an opportunity to institutionalize better science and clear national direction and maintain this guidance through changes in agency personnel, changes in agency structure, and changes in administrations. This would increase consistency, accountability, and enforceability within the Refuge System. Further, if promulgated as regulations, the Service would have additional justification to increase funding for refuge planning because the provisions of the regulations would be mandatory, as opposed to discretionary. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We assume that the commenter intended to suggest that our planning requirements be published in the Code of Federal Regulations (CFR) rather than in the Service Manual. We believe that one of the main objectives of this effort is to institutionalize better 
                        <PRTPAGE P="33902"/>
                        science and clear direction that will be maintained regardless of changes in personnel, etc. We believe that, for a number of reasons, the Service Manual, rather than the CFR, is the proper vehicle. 
                    </P>
                    <P>The issuance of planning requirements as part of the Service Manual will accomplish the requirements of the National Wildlife Refuge System Administration Act, as amended by the National Wildlife Refuge System Improvement Act. Publishing planning rules in the Service Manual rather than the CFR does not diminish the requirements that they contain. Refuge Managers will be bound by those requirements that are mandatory whether or not we publish them in the CFR. In addition, because the planning chapters contain rules, we will have to use the same notice and comment procedure utilized to adopt these chapters if we decide to amend or change them. </P>
                    <P>We have chosen to use the Service Manual because: (1) The requirements are primarily working rules of procedure for Refuge Managers to follow with regard to areas that they manage; (2) the planning chapters contain a mix of rules that we must follow and general guidance that we normally will adhere to but that we may deviate from as the particular situation warrants; (3) the planning chapters do not directly regulate the public; (4) the planning chapters and the Service Manual are available to the public through either the Department of the Interior or the Fish and Wildlife Service home pages on the World Wide Web or by request made to any refuge or Service field, regional, or headquarters office and, therefore, are as available to the public as they would be if published in the CFR; and (5) publishing in the Service Manual rather than the CFR does not affect the strength of any rules that are in the chapters nor does it exempt us from procedural requirements. </P>
                    <P>
                        <E T="03">Comment:</E>
                         The introductory sections of the draft planning policy identify an important and useful set of refuge planning goals (Sections 1.5 and 2.3). Especially important are the goals of ensuring that the System “contributes to the conservation of biological diversity and integrity and to the structure and function of the ecosystems of the United States” (Section 1.5 B) and encouraging that refuge planning be done in concert with an ecosystem approach (Section 2.3 C). However, those goals are not clearly identified as “national policy” and they are not integrated into the development of a vision and goals. While there is strong support for basing future refuge management on ecosystem goals, this emphasis needs to be much more clearly articulated. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize the need to establish national policy regarding Refuge System goals. This policy is currently under development and will eventually appear as 601 FW 1 of the Service Manual. We expect this policy to be available for public review and comment in spring 2000. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The definition of “all available information” should be adopted from the Proposed Compatibility Regulations (64 FR 49056) which includes as sources of information “planning documents, environmental assessments, environmental impact statements, annual narratives, information from previously conducted or on-going research, data from refuge inventories or studies, published literature on related biological studies, State conservation management plans, field management experience, etc.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We made the recommended change in the final policy. See 602 FW 3.4 C (1)(e). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The FWS must ensure that plans at the national, regional, and ecosystem levels are in place before refuge planning begins. The current schedule for CCP completion does not consider whether larger-scale priorities are in place, and does not provide enough time to develop sound individual CCPs. If this recommendation is not adopted, Refuge Managers must at the very least be required to state minimum inventory needs in their plans, if for no other reason than to ensure that they have the minimum baseline data they need in order to write their next plan. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We will coordinate CCP schedules so that they follow completion of national, regional, and ecosystem plans whenever possible. However, we recognize that in some instances we will develop CCPs before ecosystem and other plans are in place or updated. Our policy is to make management decisions using a thorough assessment of available science derived from scientific literature, on-site refuge data, expert opinion, and sound professional judgment. In situations where we are unable to develop new data for the CCP, the plan may identify the need for further data collection. In such cases we may delay decision making, pending additional data collection and analysis. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A section in the planning policy should be dedicated to issues external to refuge boundaries including how land acquisition and other ecosystem management tools fit in the context of Comprehensive Conservation Planning. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize the need for this additional guidance. Consequently, we will be adding an additional chapter, Land Protection Planning (602 FW 2), to the Service Manual in the near future. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Endangered and threatened species should be addressed separately within the planning policy. The Service's recommendations should provide direction for specific conservation and recovery planning for threatened and endangered species. Each refuge should be required to integrate specific threatened and endangered species Conservation and Recovery Plan implementation tasks into their CCP. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe there is a need to address endangered and threatened species separately within our policy. We address endangered and threatened species concerns at various steps throughout the planning process (see 602 FW 1.7 A and 602 FW 3.4 C (1)(a), (1)(e), (4)(d), (4)(f), (5)(a)). We agree that we should integrate Conservation and Recovery Plan implementation tasks for threatened and endangered species into refuge CCPs, where applicable. We advocate the development of goals, objectives, and strategies for the recovery and conservation of threatened and endangered species for any refuge with the potential for such. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The U.S. General Accounting Office (GAO) has identified four practical steps to successfully implementing ecosystem management (RCED-99-64). The Service should identify opportunities to make the proposed planning process more consistent with these steps, to ease the transition to an ecosystem approach. It is believed that the steps for ecosystem management that GAO has identified are consistent with the Refuge Improvement Act and with the Service's compatibility approach to determining the appropriateness of refuge uses. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We feel the recommended change is beyond the scope of this policy. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 2.4C (1)(d) should be modified to require identification of the relationship between the planning unit and its watershed, and planning teams should be encouraged to identify water quality threats by collaborating with the Environmental Protection Agency (EPA).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We see no need to specifically mention the relationship between the planning unit and its watershed since this relationship is encompassed by 602 FW 3.4 C (1)(e)(ii). With regard to the identification of 
                        <PRTPAGE P="33903"/>
                        water quality threats, we have incorporated the above suggestion with the exception that we did not specifically mention collaboration with the EPA. We added text to 602 FW 3.4 C (1)(e) that states: “Obtain information from Federal, Tribal, State, and local agencies * * *” We imply consultation with the EPA, as appropriate. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The Forest Service rule, released on October 5, 1999, acknowledges the dynamic nature, uncertainty and inherent variability of ecological systems of which we have incomplete data and knowledge. As a result the Forest Service explicitly encourages that variable natural processes be considered when defining desired future ecological conditions. The Forest Service also shifts its perspective from a focus on habitat and population to a focus on the ecosystem conditions necessary to assure a high likelihood of maintaining the viability of native and desired non-native species over time within the plan area. This shift in perspective would benefit the management of wildlife refuges as well. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize the benefit of looking at the ecosystem context of each refuge. Our policy provides direction for the Refuge Manager and planning team to assess ecological conditions of the watershed, ecosystem, and the relationship to the refuge (see 602 FW 1.7). Our policy also provides direction for adaptive management and monitoring, as well as direction to change refuge management in the event of new circumstances or information (see 602 FW 3). The Service also has existing policy and guidance on ecosystem management and will be developing new policy and guidance on ecological integrity. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 2.4 C (1)(d) should be modified to direct the planning team to identify and describe as appropriate, the structures, components, and functions of the ecosystem(s) of which the refuge is a part. In addition, Section 2.4 C (4)(d) should be modified to direct planning teams to develop objectives for ecosystem structures, components, and functions to maintain or restore the ecological health of the refuge. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We revised Section 3.4 C (1)(e) to reflect that the planning team should identify and describe the structures, components, and functions of the ecosystem(s) of which the planning unit is a part. However, we do not believe the planning team should be responsible for developing objectives related to the larger ecosystem. This responsibility belongs to our ecosystem teams. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 2.4 C (3)(b) should be modified to require that planning teams “determine significant issues and the appropriate scale at which to consider those issues.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We made the recommended change in the final policy. See 602 FW 3.4 C (3)(b). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The Forest Service rule proposed that “focal species” should be selected to serve as surrogate measures in the assessment of ecological integrity. We believe that with limited resources for monitoring and a need to assess the health of refuge habitats and ecological processes, the Service should adopt this strategy for monitoring ecological health. Specifically, 602 FW 2.4 C (7) should be modified to require monitoring of focal species, since their status and time trend provide insights into the integrity of the larger ecological system to which refuges belong, and ecological health is a strong overarching indicator of whether refuge management is generally successful or requires significant modification. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We feel this recommendation is more appropriately addressed in 701 FW 2 (the Service Manual chapter dealing with inventory and monitoring). This policy, currently under revision, will help provide guidance on how to accomplish monitoring strategies identified in the CCP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It would be useful for Refuge Managers to seek out information regarding trends in refuge ecological conditions. It is important not only to know the current status of refuge conditions, but also whether they are improving or declining, in order to most effectively prioritize management activities. Hence, Section 2.4 C (1)(d) should be modified to read: “Identify and describe the following conditions and their trends as appropriate.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We made the recommended change in the final policy. See 602 FW 3.4 C (1)(e). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It is recommended that Section 2.4 (1)(d) be amended so that planning teams would be strongly encouraged to collaborate with adjacent landowners including State, Federal, Tribal, and private landowners, especially to acquire data that may be relevant to planning decisions. Furthermore, planning teams should be encouraged to collaborate as appropriate with the Environmental Protection Agency, the Department of Agriculture's Forest Service and Natural Resources Conservation Service, the Department of Commerce's National Marine Fisheries Service, the United States Army Corps of Engineers, and relevant bureaus within the Department of the Interior such as the U.S. Geological Survey. Each of these agencies may be able to provide information that may dramatically improve the quality of CCPs with limited expense by the Service. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We incorporated the above suggestion into the final policy. We added language to 602 FW 3.4 C (1)(e) which states: “Obtain information from Federal, Tribal, State and local agencies, and private landowners concerning land management issues that may impact or relate to the planning unit.” We also substantially modified this section of the draft policy to include a wide variety of additional sources of information we will consult during the preplanning stage. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 2.4 C (3)(b) limits the consideration of issues in the CCP to those that are determined to be “significant” by the planning team. To ensure consistency across refuge units and to ensure that important ecological or public use issues are not excluded from consideration in some plans, it is necessary to establish criteria for determining which issues are “significant” and thereby warrant consideration in the CCP. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We incorporated the above recommendation into the final policy. We added the following language to the end of Section 602 FW 3.4 C (3)(b): “Significant issues typically are those that are: within our jurisdiction, suggest different actions or alternatives, and will influence our decision.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 2.4 C (4) should be significantly modified to ensure wildlife conservation objectives are considered first in the planning process. In addition, another slight modification of this section should be considered. For example, 602 FW 2.4 C (4)(e) directs planning teams to “develop inventory and monitoring strategies to measure implementation results in quantifiable and verifiable ways.” This should be elaborated to include direction to prioritize inventory and monitoring efforts in a manner “that maximizes the usefulness of acquired information in directing management activities toward the improved ecological health of the refuge.” This additional direction will lead to a more productive use of limited resources for monitoring. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We feel this recommendation is more appropriately addressed in 701 FW 2 (the Service Manual chapter dealing with inventory and monitoring). This policy, currently under revision, will provide guidance on how to accomplish monitoring strategies identified in the CCP. 
                        <PRTPAGE P="33904"/>
                    </P>
                    <HD SOURCE="HD2">VII. Describing the Relationship of CCPs to Refuge Purposes and Refuge System Mission </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters requested that the agency not overlook the quality of the individual refuges for sake of the “System.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Many sections of the policy identify the need for the planning team to acknowledge individual refuge purposes and functions. For example, see Sections 1.3 and 3.1. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some comments were received that requested the CCP policy provide more guidance on the implications of the Service's ecosystem approach to refuge planning and management. In particular, it has been noted that while the Service's ecosystem approach has goals for the effective conservation of natural biological diversity, and the perpetuation of natural communities, many refuges have created or possess artificial habitats, croplands, dikes and other structures. It has been pointed out that more guidance may be needed to help reconcile the differences between areas which may be managed for “naturalness” and those that may need to be highly manipulated or developed to support objectives. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize the great variability in the Refuge System. Many areas are representative of intact ecosystems or vegetation communities, while we may have developed others to provide for wetland habitats lost at a greater scale. We will require refuge planning efforts to review a host of information, including establishing authorities, refuge purposes, past management practices, ecosystem and watershed goals, activities of neighboring lands, and species goals and objectives throughout their ranges. Goals for the restoration or maintenance of biological diversity will be high on our list of priorities for many refuges, however, it will not be appropriate for every refuge in the Refuge System. For unless restoration of wildlife habitat takes place on vast developed areas so that we no longer have to manage highly manipulated refuges to make up for the loss of wetlands or the recovery and restoration of habitats for endangered species, some of our refuge management will continue to be “unnatural,” yet for the benefit of numerous wildlife species. We will be working nationally, and with our partners, to help identify and define how units of the Refuge System can best contribute to maintaining biodiversity and the context of each refuge within the greater ecosystem and landscape. 
                    </P>
                    <HD SOURCE="HD2">VIII. Addressing Issues Related to Recreation and Public Use </HD>
                    <P>
                        <E T="03">Comment:</E>
                         The National Wildlife Refuge System Improvement Act makes it clear that part of the planning process must be to consider, on a priority basis, wildlife-dependent uses and to facilitate such uses. In order to carry out the intent of Congress, the Service should add real “requirements and standards” to assure that adequate attention is paid to wildlife. For example, there should be language in Section 2.3 dealing with wildlife-dependent uses. This section sets out the goals for Comprehensive Conservation Planning mentioning the ecosystem concept, the use of sound professional judgment, public comment and several other “goals,” but nowhere does it refer to the goal of giving priority consideration to wildlife-dependent uses or to facilitating them. The commenter recommends the insertion of a new Subsection E, reading as follows, and the re-lettering of the existing Subsections, E, F, and G: 
                    </P>
                    <P>“E. To assure that wildlife-dependent recreational uses receive priority consideration during the planning process and that plans include steps to facilitate such uses.” </P>
                    <P>
                        <E T="03">Response:</E>
                         We have inserted a new Subsection 602 FW 3.3 E in the final policy that reads: “To ensure that the six priority wildlife-dependent recreational uses receive priority consideration during the preparation of CCPs.” We have re-lettered subsequent subsections F, G, and H. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         In Section 2.4 B (1)(d), which deals with “planning area, data needs, and data standards” in the preplanning process, item (x) should be expanded. Currently, that item says that the planning team should “identify and describe the following * * * (x) opportunities for compatible wildlife-dependent recreation.” This is quite weak compared to the stress on “facilitating” wildlife-dependent recreational uses contained in the Refuge Improvement Act. Item (x) should be revised to read as follows: 
                    </P>
                    <P>“(x) existing wildlife-dependent recreational uses, opportunities for continuing, facilitating and expanding such uses, and strategies to accomplish such continuation, facilitation and expansion.” </P>
                    <P>
                        <E T="03">Response:</E>
                         We have modified the wording in Step 1, “Preplanning: Planning the Plan, (e) Planning Area and Data Needs” (602 FW 3.4 C (1)(e)), to read as follows: “(xix) Existing and potential opportunities for wildlife-dependent recreation.” Developing the strategies associated with continuing, facilitating, or expanding such uses more appropriately belongs in Step 4, “Develop and Analyze Alternatives, Including the Proposed Action, (e) Strategy Development.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         In Section 2.4 B(1)(f), Vision and Goals, the third sentence contains a reference to “compatible wildlife-dependent recreation” in discussing the minimum goals that should be included in a CCP. This sentence should be expanded to read: 
                    </P>
                    <P>“At a minimum, each refuge should develop goals within the following management areas: the continuation, facilitation and expansion of opportunities for compatible wildlife-dependent recreation * * *” </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe the policy's current wording is appropriate. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 2.4 B(1)(g), Internal Scoping, refers to identification of problems with wildlife and habitats, assessments of water quality and quantity, potential need for administrative sites or visitor facilities, land acquisition, and controversial management actions. There is no reference at all to the continuation, facilitation and expansion of wildlife-dependent uses! The following sentence should be added to this provision: 
                    </P>
                    <P>“We also need to evaluate the current or potential wildlife-dependent uses and consider opportunities to continue, facilitate and expand such uses.” </P>
                    <P>
                        <E T="03">Response:</E>
                         We have moved the list to which you refer to Section 3.4 C (1)(e) “Planning Area and Data Needs,” and have added the following item, “(xix) Existing and potential opportunities for wildlife-dependent recreation.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         There is concern that with no public review and comment process in place, some wildlife-dependent uses may be allowed that are detrimental to the refuge and/or to wildlife inhabiting the refuge. Such uses may be allowed for many years, as refuges are not required to prepare CCPs until October 2012. The planning policy should reflect that a public review and comment process will be implemented for all interim wildlife-dependent uses. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe we adequately addressed this concern in Step 5, “Prepare Draft Plan and NEPA Document, Subpart (c) Pre-acquisition Compatibility Determinations.” This subpart requires that: “If our proposed action includes expanding the planning unit by acquiring new lands, the draft CCP and NEPA documents also must identify any existing wildlife-dependent recreational public uses deemed compatible that we will allow to continue after acquisition.” The public will have an opportunity to review and comment on all compatibility determinations. Our refuge planning 
                        <PRTPAGE P="33905"/>
                        policy directs that we incorporate pre-acquisition compatibility determinations into the draft CCP and NEPA document, where they will receive their required public review and comment. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters stated confusion with, or recommended changes to, the definition of wildlife-dependent recreational uses. In particular, some suggested we reconsider trapping, and other uses, as a wildlife-dependent recreational use. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we recognize that trapping of animals may be a form of wildlife-dependent recreation, the Refuge Administration Act, as amended, binds our definition of wildlife-dependent recreational uses, which only includes hunting, fishing, wildlife observation and photography, environmental education and interpretation. These are the priority public uses of the National Wildlife Refuge System. We recognize that we may consider other recreational and other activities, such as trapping, during the planning process. Such other uses or activities proposed on a refuge may or may not be both appropriate on the refuge and compatible with refuge purposes. We would not label other recreational uses that we find to be appropriate and compatible through the planning process as wildlife-dependent recreational uses, but would place them in a category of other recreation. Specific to trapping, we note that in many cases we would classify this activity as a commercial use, and require a permit and compatibility determination. We acknowledge that many of the wildlife-dependent recreational uses are “more than recreation,” in that the outdoor experience can provide the visitor with a wealth of experiences. However, we support and are bound by the definition in the Act. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         At least one commenter requested that we consider establishing carrying capacities for public uses and other uses. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Service is developing new policies on habitat management, priority wildlife-dependent recreation, and refuge uses (appropriate uses). We will recommend that carrying capacities be considered in the development of these policies. 
                    </P>
                    <HD SOURCE="HD1">Primary Author </HD>
                    <P>Charles J. Houghten, Acting Chief, Division of Refuge Planning, Pacific Region, U.S. Fish and Wildlife Service, is the primary author of this notice.</P>
                    <HD SOURCE="HD3">Refuge Management—Part 602 National Wildlife Refuge System Planning </HD>
                    <HD SOURCE="HD1">Chapter 1 Refuge Planning Overview.—602 FW 1 </HD>
                    <P>1.1 What is the purpose of Part 602 and this chapter? Part 602 provides guidance for National Wildlife Refuge System (Refuge System) planning, including specific chapters on the Comprehensive Conservation Planning Process (602 FW 3) and Step-Down Management Plans (602 FW 4). This chapter (602 FW 1) provides an overview of refuge planning. We will add an additional chapter, Land Protection Planning (602 FW 2), in the near future. </P>
                    <P>1.2 To what does Part 602 apply? Part 602 applies to all units of the National Wildlife Refuge System. </P>
                    <P>1.3 What is our policy for managing refuges? The U.S. Fish and Wildlife Service (Service or we) will manage all refuges in accordance with an approved Comprehensive Conservation Plan (CCP), which, when implemented, will achieve refuge purposes; help fulfill the Refuge System mission; maintain and, where appropriate, restore the ecological integrity of each refuge and the Refuge System; help achieve the goals of the National Wilderness Preservation System; and meet other mandates. The CCP will guide management decisions and set forth goals, objectives, and strategies to accomplish these ends. We also may require step-down management plans to provide additional details about meeting CCP goals and objectives and to describe strategies and implementation schedules. Each plan will be founded on principles of sound fish and wildlife management and available science, and be consistent with legal mandates and our other policies, guidelines, and planning documents. We will prepare refuge plans that, above all else, ensure that wildlife comes first on national wildlife refuges. </P>
                    <P>1.4 What are our authorities? Authorities listed below include laws that require us to manage units of the Refuge System in accordance with approved CCPs and to integrate refuge planning decisions with the National Environmental Policy Act (NEPA) process. </P>
                    <P>
                        A. National Wildlife Refuge System Administration Act of 1966 as amended by the National Wildlife Refuge System Improvement Act of 1997, 16 U.S.C. 668dd-668ee (Refuge Administration Act). This law states that “* * * the Secretary shall—(i) propose a comprehensive conservation plan for each refuge or related complex of refuges * * * in the System; (ii) publish a notice of opportunity for public comment in the 
                        <E T="04">Federal Register</E>
                         on each proposed conservation plan; (iii) issue a final conservation plan for each planning unit consistent with the provisions of this Act and, to the extent practicable, consistent with fish and wildlife conservation plans of the State in which the refuge is located; and (iv) not less frequently than 15 years after the date of issuance of a conservation plan under clause (iii) and every 15 years thereafter, revise the conservation plan as may be necessary.” This law provides additional detail on conservation planning for the Refuge System. Above all else, the law directs that wildlife comes first in the National Wildlife Refuge System. It does so by establishing that wildlife conservation is the principal mission of the Refuge System; by requiring that we maintain the biological integrity, diversity, and environmental health of each refuge and the Refuge System; and by mandating that we monitor the status and trends of fish, wildlife, and plants on each refuge. 
                    </P>
                    <P>B. Alaska National Interest Lands Conservation Act of 1980 as amended, 16 U.S.C. 140hh-3233, 43 U.S.C. 1602-1784 (ANILCA). Section 304 states, in part, “The Secretary shall prepare, and from time to time, revise, a comprehensive conservation plan * * * for each refuge.” You may find additional guidance on the content of these plans and management direction in this and other sections of ANILCA. If any provisions of the National Wildlife Refuge System Improvement Act of 1997 conflict with the provisions of ANILCA, the provisions of ANILCA will prevail for refuges in Alaska. </P>
                    <P>
                        C. National Environmental Policy Act (NEPA) of 1969, as amended, 42 U.S.C. 4321-4347, and the Council on Environmental Quality's (CEQ) Regulations for Implementing the Procedural Provisions of NEPA, 40 CFR 1500-1508. NEPA is the basic national charter for protection of the environment. The procedural provisions in CEQ's regulations require Federal agencies to integrate the NEPA process with other planning at the earliest possible time in order to provide a systematic interdisciplinary approach; identify and analyze the environmental effects of their actions; describe appropriate alternatives to the proposal; involve the affected State and Federal agencies, Tribal governments, and the affected public in the planning and decision-making process; and fully integrate all refuge proposals that may have an impact on the environment with the provisions of NEPA (40 CFR 1501.2). 
                        <PRTPAGE P="33906"/>
                    </P>
                    <P>1.5 What are the goals of refuge planning? </P>
                    <P>A. To ensure that wildlife comes first in the National Wildlife Refuge System. </P>
                    <P>B. To ensure that we manage the Refuge System for the conservation of fish, wildlife, plants, and their habitats and that refuge management achieves our policies, the Refuge System mission, and the purposes for which the refuge was established. </P>
                    <P>C. To ensure that the administration of the Refuge System contributes to the conservation of the ecological integrity of each refuge, the Refuge System, and to the structure and function of the ecosystems of the United States. </P>
                    <P>D. To ensure opportunities to participate in the refuge planning process are available to our other programs; Federal, State, and local agencies; Tribal governments; conservation organizations; adjacent landowners; and the public. </P>
                    <P>E. To provide a basis for adaptive management by monitoring progress, evaluating plan implementation, and updating refuge plans accordingly. </P>
                    <P>F. To promote efficiency, effectiveness, continuity, and national consistency in refuge management. </P>
                    <P>G. To help ensure consistent System-wide consideration of the six priority public uses—hunting, fishing, wildlife observation and photography, and environmental education and interpretation—established by the Refuge Administration Act and to ensure that these uses receive enhanced consideration over general public uses in the Refuge System. </P>
                    <P>H. To ensure that we preserve the wilderness character of refuge lands. </P>
                    <P>1.6 What do the following terms mean? (Quotations are from the Refuge Administration Act unless otherwise noted) </P>
                    <P>A. Adaptive Management. The rigorous application of management, research, and monitoring to gain information and experience necessary to assess and modify management activities. A process that uses feedback from refuge research and monitoring and evaluation of management actions to support or modify objectives and strategies at all planning levels. </P>
                    <P>B. Alternatives. Different sets of objectives and strategies or means of achieving refuge purposes and goals, helping fulfill the Refuge System mission, and resolving issues. </P>
                    <P>C. Biological Diversity. The variety of life, including the variety of living organisms, the genetic differences among them, and the communities in which they occur. </P>
                    <P>D. Biological Integrity. Biotic composition, structure, and functioning at the genetic, organism, and community levels consistent with natural conditions, including the natural biological processes that shape genomes, organisms, and communities. </P>
                    <P>E. Comprehensive Conservation Plan (CCP). A document that describes the desired future conditions of a refuge or planning unit and provides long-range guidance and management direction to achieve the purposes of the refuge; helps fulfill the mission of the Refuge System; maintains and, where appropriate, restores the ecological integrity of each refuge and the Refuge System; helps achieve the goals of the National Wilderness Preservation System; and meets other mandates. </P>
                    <P>F. Coordination Area. A wildlife management area made available to a State, by “(A) cooperative agreement between the United States Fish and Wildlife Service and the State fish and game agency pursuant to Section 4 of the Fish and Wildlife Coordination Act (16 U.S.C. 664); or (B) by long-term leases or agreements pursuant to the Bankhead-Jones Farm Tenant Act (50 Stat. 525; 7 U.S.C. 1010 et seq.).” States manage Coordination Areas, but they are part of the Refuge System. We do not require CCPs for Coordination Areas. </P>
                    <P>G. Ecological Integrity. The integration of biological integrity, natural biological diversity, and environmental health; the replication of natural conditions. </P>
                    <P>H. Ecosystem. A biological community together with its environment, functioning as a unit. For administrative purposes, we have designated 53 ecosystems covering the United States and its possessions. These ecosystems generally correspond with watershed boundaries, and their sizes and ecological complexity vary. </P>
                    <P>I. Environmental Health. Abiotic composition, structure, and functioning of the environment consistent with natural conditions, including the natural abiotic processes that shape the environment. </P>
                    <P>J. Goal. Descriptive, open-ended, and often broad statement of desired future conditions that conveys a purpose but does not define measurable units. </P>
                    <P>
                        K. Issue. Any unsettled matter that requires a management decision, 
                        <E T="03">e.g.,</E>
                         an initiative, opportunity, resource management problem, threat to the resources of the unit, conflict in uses, public concern, or the presence of an undesirable resource condition. 
                    </P>
                    <P>L. National Wildlife Refuge (refuge). “A designated area of land, water, or an interest in land or water within the Refuge System, but does not include Coordination Areas.” Find a complete listing of all units of the Refuge System in the current Annual Report of Lands Under Control of the U.S. Fish and Wildlife Service. </P>
                    <P>M. National Wildlife Refuge System Mission (mission). “The mission of the System is to administer a national network of lands and waters for the conservation, management, and, where appropriate, restoration of the fish, wildlife, and plant resources and their habitats within the United States for the benefit of present and future generations of Americans.” </P>
                    <P>N. Objective. A concise statement of what we want to achieve, how much we want to achieve, when and where we want to achieve it, and who is responsible for the work. Objectives derive from goals and provide the basis for determining strategies, monitoring refuge accomplishments, and evaluating the success of strategies. Make objectives attainable, time-specific, and measurable. </P>
                    <P>O. Planning Area. The area upon which the planning effort will focus. A planning area may include lands outside existing planning unit boundaries currently studied for inclusion in the Refuge System and/or partnership planning efforts. It also may include watersheds or ecosystems outside of our jurisdiction that affect the planning unit. At a minimum, the planning area includes all lands within the authorized boundary of the refuge. </P>
                    <P>
                        P. Planning Team. Planning teams are interdisciplinary in membership and function. Teams generally consist of a Planning Team Leader, Refuge Manager and staff biologists, a state natural resource agency representative, and other appropriate program specialists (
                        <E T="03">e.g.,</E>
                         social scientist, ecologist, recreation specialist). We also will ask other Federal and Tribal natural resource agencies to provide team members, as appropriate. The planning team prepares the CCP and appropriate NEPA documentation. 
                    </P>
                    <P>Q. Planning Team Leader. The Planning Team Leader typically is a professional planner or natural resource specialist knowledgeable of the requirements of NEPA and who has planning experience. The Planning Team Leader manages the refuge planning process and ensures compliance with applicable regulatory and policy requirements. </P>
                    <P>R. Planning Unit. A single refuge, an ecologically or administratively related refuge complex, or distinct unit of a refuge. The planning unit also may include lands currently outside refuge boundaries. </P>
                    <P>
                        S. Purposes of the Refuge. “The purposes specified in or derived from the law, proclamation, executive order, 
                        <PRTPAGE P="33907"/>
                        agreement, public land order, donation document, or administrative memorandum establishing, authorizing, or expanding a refuge, refuge unit, or refuge subunit.” For refuges that encompass Congressionally designated wilderness, the purposes of the Wilderness Act are additional purposes of the refuge. 
                    </P>
                    <P>T. Refuge Operating Needs System (RONS). The Refuge Operating Needs System is a national database that contains the unfunded operational needs of each refuge. We include projects required to implement approved plans and meet goals, objectives, and legal mandates. </P>
                    <P>U. Step-Down Management Plan. A plan that provides specific guidance on management subjects (e.g., habitat, public use, fire, safety) or groups of related subjects. It describes strategies and implementation schedules for meeting CCP goals and objectives. </P>
                    <P>V. Strategy. A specific action, tool, technique, or combination of actions, tools, and techniques used to meet unit objectives. </P>
                    <P>W. U.S. Fish and Wildlife Service Mission. Our mission is working with others to conserve, protect, and enhance fish, wildlife, and plants and their habitats for the continuing benefit of the American people. </P>
                    <P>X. Wilderness Review. The process we use to determine if we should recommend Refuge System lands and waters to Congress for wilderness designation. The wilderness review process consists of three phases: inventory, study, and recommendation. The inventory is a broad look at the refuge to identify lands and waters that meet the minimum criteria for wilderness. The study evaluates all values (ecological, recreational, cultural), resources (e.g., wildlife, water, vegetation, minerals, soils), and uses (management and public) within the Wilderness Study Area. The findings of the study determine whether we will recommend the area for designation as wilderness. </P>
                    <P>Y. Wildlife-Dependent Recreational Use. “A use of a refuge involving hunting, fishing, wildlife observation and photography, or environmental education and interpretation.” These are the six priority public uses of the Refuge System as established in the National Wildlife Refuge System Administration Act, as amended. Wildlife-dependent recreational uses, other than the six priority public uses, are those that depend on the presence of wildlife. We also will consider these other uses in the preparation of refuge CCPs, however, the six priority public uses always will take precedence. </P>
                    <P>Z. Vision Statement. A concise statement of what the planning unit should be, or what we hope to do, based primarily upon the Refuge System mission and specific refuge purposes, and other mandates. We will tie the vision statement for the refuge to the mission of the Refuge System; the purpose(s) of the refuge; the maintenance or restoration of the ecological integrity of each refuge and the Refuge System; and other mandates. </P>
                    <P>1.7 What is the relationship between Refuge System planning and other planning efforts? Refuge planning should maintain continuity and consistency with other planning efforts. The relationship between these planning efforts is hierarchical, starting from national plans to regional, State, and ecosystem-level plans, stepping down to refuge-specific plans. See Exhibit 1-1. The process of adaptive management uses feedback from refuge research and monitoring, and evaluation of management actions to support or modify objectives and strategies at all planning levels. </P>
                    <P>A. National and Regional Plans. We will review other Service documents that address particular programs, species, habitats, public uses, economic uses, archaeological resources, etc., when identifying issues to address in refuge planning. National and regional goals, objectives, strategies, and policies influence management planning for refuges. Source documents include: Fulfilling the Promise: The National Wildlife Refuge System, the Service Manual, the North American Waterfowl Management Plan, National Outreach Strategy, regional resource plans, endangered species recovery plans, migratory bird and flyway plans, fishery resource plans, Joint Venture plans, Partners in Flight plans, and strategies to promote the conservation of natural biological diversity. The contribution of the refuge to achieving regional and national goals will help implement our mission and ensure integrity of the Refuge System. </P>
                    <P>B. Service Ecosystem Plans, State Fish and Wildlife Conservation Plans, and Other Landscape-Level Plans. Refuge planning will reflect conservation goals and objectives for the landscapes in which the refuges are located. Refuges must review goals and objectives of existing ecosystem plans and determine how the refuge can best contribute to the functioning of the ecosystem. We will coordinate refuge planning with State conservation agencies, Tribal governments, other government agencies, and nongovernmental organizations. To the extent practicable, refuge plans will be consistent with the fish and wildlife conservation plans of the State and the conservation programs of Tribal, public, and private partners within the ecosystem. </P>
                    <P>C. Land Acquisition Planning. We integrate land acquisition and CCP planning throughout the land acquisition planning process. We describe three opportunities for integration in the following paragraphs: </P>
                    <P>(1) Refuge planning typically begins before the establishment of an area as a unit of the Refuge System. Land acquisition planning (usually resulting in a Land Protection Plan [LPP] and associated NEPA document) is a preliminary step in the continuous, integrated refuge planning process. This process eventually results in completion of a CCP and appropriate refuge step-down management plans. Other land use, species, or habitat protection planning efforts, or legislative or executive directives may precede land acquisition planning. Refuge establishment documentation (LPP and associated NEPA document) should identify the approved refuge boundary, refuge purpose(s), goals, and general management direction. See 341 FW 2. </P>
                    <P>(2) Planning for proposed new refuges or major expansions to existing refuges not undergoing a CCP will include the development of a Conceptual Management Plan (CMP) for the new unit. The CMP provides general, interim management direction. The CMP should identify refuge purpose(s), interim goals, and pre-existing compatible wildlife-dependent recreational uses (hunting, fishing, wildlife observation, photography, environmental education and interpretation) that we will allow to continue on an interim basis. The interim period is the duration of time between establishment of a new refuge or refuge expansion and the completion of an approved CCP. Refuges functioning under CMPs also will develop step-down management plans, as appropriate. </P>
                    <P>(3) Fully integrate land acquisition planning efforts into CCP preparation whenever possible. Some proposed new refuges or refuge expansions may warrant CCP development at the time of acquisition planning. Include appropriate Realty staff on the planning team when considering land acquisition during the CCP process to ensure consistency with land acquisition policy. See 341 FW 2. </P>
                    <P>
                        D. Comprehensive Conservation Plans (CCP). The CCP is a document that describes the desired future conditions of a refuge or planning unit and provides long-range guidance and management direction to achieve the purposes of the refuge; helps fulfill the 
                        <PRTPAGE P="33908"/>
                        mission of the Refuge System; maintains and, where appropriate, restores the ecological integrity of each refuge and the Refuge System; helps achieve the goals of the National Wilderness Preservation System; and meets other mandates. See 602 FW 3. For refuges established after October 9, 1997, prepare CCPs when the refuge obtains staff and acquires a land base sufficient to achieve refuge purposes, but no later than 15 years after we establish the refuge. Convert refuge long-range management plans (
                        <E T="03">e.g.,</E>
                         master plans and refuge management plans) approved prior to October 9, 1997, into CCPs with appropriate public involvement and NEPA compliance no later than October 2012. 
                    </P>
                    <P>E. Step-Down Management Plans. Step-down management plans provide the details (strategies and implementation schedules) necessary to meet goals and objectives identified in the CCP. CCPs will either incorporate or identify step-down management plans required to fully implement the CCP. After completion of the CCP, modify existing step-down management plans to accomplish stated goals and objectives as needed. See 602 FW 4. </P>
                    <P>F. Integration With Budget Development and Implementation. We will use CCPs to guide annual budget requests. We will identify the unfunded costs of implementing strategies in refuge plans using our budget databases, including the Refuge Operating Needs System (RONS), Maintenance Management System (MMS), and Land Acquisition Priority System (LAPS). As we complete or update each plan, we will review and update these databases to incorporate projects identified in CCPs. The total funding and staffing identified in these databases represents the additional resources required to fully implement the refuge plans. </P>
                    <P>1.8 Who is responsible for implementing our policy? </P>
                    <P>A. Director. The Director is responsible for providing national policy and ensuring adherence to refuge planning policy. </P>
                    <P>B. Regional Director. The Regional Director: (1) Ensures compliance with national planning policy, NEPA, and other applicable laws and policies; (2) approves CCPs, amendments to CCPs, and associated NEPA and other agency compliance documents; and (3) ensures that we manage refuges in accordance with approved CCPs. The Regional Director or designee approves step-down management plans, determines planning priorities, and allocates funds to develop and implement plans. </P>
                    <P>C. Regional Chief, National Wildlife Refuge System. The Regional Chief, National Wildlife Refuge System, is responsible for initiating and completing refuge plans, budgeting for planning, ensuring programmatic staff participation, and developing regional planning priorities. The Special Assistant for Ecosystems is responsible for ensuring that ecosystem teams participate in developing plans and implementing approved plans. </P>
                    <P>D. Refuge Planning Coordinator. The Washington Office, Division of Refuges, and each Region will designate a Refuge Planning Coordinator. In cooperation with representatives of our National Conservation Training Center, the Coordinators will establish and maintain appropriate training courses. Refuge Planning Coordinators will provide guidance and direction to assist Planning Team Leaders, regional and field-based planning staff, and planning team members. The Coordinators also are responsible for maintaining regional planning schedules and updating status reports and funding needs for the planning program. The Coordinators periodically will meet to review and recommend changes to planning policy, resolve common planning problems and issues, and help ensure national consistency. </P>
                    <P>E. Planning Team Leader. The Planning Team Leader is responsible for initiation of the planning process, preparation and completion of refuge plans, and ensuring that we meet compliance requirements. The Planning Team Leader, in consultation with the Refuge Manager, is responsible for identifying appropriate and proper representation on the interdisciplinary planning team, including team members, support personnel, and outside or contract assistance. The Refuge Manager and Planning Team Leader will submit the final CCP through line supervision for concurrence and approval by the Regional Director. </P>
                    <P>F. Refuge Supervisor. The Refuge Supervisor is responsible for overseeing participation of the Refuge Manager in CCP preparation and implementation, and for providing direction and guidance on compliance with Refuge System policy and regulations. Once the Planning Team Leader and Refuge Manager submit the plan, the Refuge Supervisor will be responsible for review and concurrence of the plan prior to its submission to the next level. </P>
                    <P>G. Refuge Manager. The Refuge Manager participates in the preparation of the CCP working closely with the Planning Team Leader. The Refuge Manager assures that the refuge staff participates in plan development. The Refuge Manager and Planning Team Leader submit the final CCP through line supervision for concurrence and approval by the Regional Director. The Refuge Manager is responsible for: making compatibility determinations; implementing approved CCPs and step-down management plans; tracking progress; and recommending changes to plans based on monitoring and evaluation. The Refuge Manager also reports plan accomplishments through standard reporting mechanisms and budgeting procedures. </P>
                    <P>H. Planning Team. The planning team, coordinated by the Planning Team Leader, is responsible for the initiation and completion of all planning steps, including public involvement and NEPA compliance, resulting in a refuge CCP. We describe the steps in 602 FW 3.4C. The planning team is responsible for the CCP's content in terms of information relating to management of refuge resources and use activities. The planning team will ensure that the CCP, when implemented, will achieve the purposes of the refuge and help fulfill the Refuge System mission. </P>
                    <P>I. Regional Environmental (NEPA) Coordinator. The Regional Environmental (NEPA) Coordinator provides technical assistance on NEPA-related matters.</P>
                    <BILCOD>BILLING CODE 4310-55-P </BILCOD>
                    <GPH SPAN="3" DEEP="509">
                        <PRTPAGE P="33909"/>
                        <GID>EN25MY00.000</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4310-55-C </BILCOD>
                    <PRTPAGE P="33910"/>
                    <HD SOURCE="HD1">Refuge Management—Part 602 National Wildlife Refuge System Planning </HD>
                    <HD SOURCE="HD1">Chapter 3 Comprehensive Conservation Planning Process 602—FW 3 </HD>
                    <P>3.1 What is the purpose of this chapter? Comprehensive Conservation Plans (CCPs) describe the desired future conditions of a refuge and provide long-range guidance and management direction to achieve refuge purposes; help fulfill the National Wildlife Refuge System (Refuge System) mission; maintain and, where appropriate, restore the ecological integrity of each refuge and the Refuge System; help achieve the goals of the National Wilderness Preservation System; and meet other mandates. The purpose of this chapter is to describe a systematic decision-making process that fulfills the requirements we are establishing for developing a CCP. This policy provides guidance, step-by-step direction, and establishes minimum requirements for all CCPs. Experienced planners lead the CCP process. We require all of our planners and strongly encourage Refuge Managers and other key planning team members attend the National Conservation Training Center (NCTC) course on Refuge Comprehensive Conservation Planning. </P>
                    <P>3.2 What is our policy for CCPs? The U.S. Fish and Wildlife Service (Service or we) must manage all national wildlife refuges according to an approved CCP. We will prepare a CCP by October 2012, for each refuge in existence at the time of passage of the National Wildlife Refuge System Improvement Act. For refuges established after passage of this Act, we will prepare CCPs when we staff the refuge and acquire a land base sufficient to achieve refuge purposes, but no later than 15 years after establishment of the refuge. To the extent practicable, we will coordinate the development of CCPs with affected States. We will continue to manage each refuge or planning unit with existing plans effective prior to October 9, 1997, to the extent these plans are consistent with the Refuge Administration Act, until we revise such plans or new CCPs supersede them. Upon completion of a CCP, we will manage the refuge or planning unit in a manner consistent with the CCP. We will revise the CCP every 15 years thereafter, or earlier, if monitoring and evaluation determine that we need changes to achieve planning unit purpose(s), vision, goals, or objectives. </P>
                    <P>3.3 What are our goals for Comprehensive Conservation Planning? </P>
                    <P>A. To ensure that wildlife comes first in the National Wildlife Refuge System and that we manage each refuge to help fulfill the mission of the Refuge System, maintain and, where appropriate, restore the ecological integrity of each refuge and the Refuge System, as well as achieve the specific purposes for which the refuge was established. </P>
                    <P>B. To provide a clear and comprehensive statement of desired future conditions for each refuge or planning unit. </P>
                    <P>C. To encourage use of an ecosystem approach when we conduct refuge planning. This includes conducting concurrent refuge planning for refuges within the same watershed or ecosystem and considering the broader goals and objectives of the refuges' ecosystems and watersheds when developing management direction (see Ecosystem Approach to Fish and Wildlife Conservation [Part 052 of the Service Manual]). </P>
                    <P>D. To support management decisions and their rationale by using a thorough assessment of available science derived from scientific literature, on-site refuge data, expert opinion, and sound professional judgment. </P>
                    <P>E. To ensure that the six priority wildlife-dependent recreational uses receive priority consideration during the preparation of CCPs. </P>
                    <P>F. To provide a forum for the public to comment on the type, extent, and compatibility of uses on refuges, including priority wildlife-dependent recreational uses. </P>
                    <P>G. To provide a uniform basis for budget requests for operational, maintenance, and capital improvement programs. </P>
                    <P>H. To ensure public involvement in refuge management decisions by providing a process for effective coordination, interaction, and cooperation with affected parties, including Federal agencies, State conservation agencies, Tribal governments, local governments, conservation organizations, adjacent landowners, and interested members of the public. </P>
                    <P>3.4 What is the Comprehensive Conservation Planning process? </P>
                    <P>A. The CCP process (see Exhibit 3-1) provides consistent guidelines for developing CCPs. We designed the planning process to result in the development of vision statements, goals, objectives, and strategies that achieve refuge or planning unit purpose(s); help fulfill the Refuge System mission; maintain and, where appropriate, restore the ecological integrity of each refuge and the Refuge System; help achieve the goals of the National Wilderness Preservation System; and meet other mandates. </P>
                    <P>B. Each CCP will comply with the provisions of the National Environmental Policy Act (NEPA) through the concurrent preparation of an Environmental Assessment (EA) or Environmental Impact Statement (EIS) that will accompany or be integrated with the CCP. We have integrated NEPA compliance requirements directly into the CCP process. When preparing an EA, consider integrating it into the draft CCP. When preparing an EIS with a CCP, integrate the documents. Following completion of the final CCP/NEPA document, the product of the planning process will be a stand-alone CCP, separate from the EA or EIS. </P>
                    <P>C. Our CCP planning process consists of the following eight steps. Although we display the steps sequentially, CCP planning and NEPA documentation are iterative processes. Cycling through some of the steps more than once or having several steps occurring simultaneously is normal. Actions within each of the eight steps may not be sequential. </P>
                    <HD SOURCE="HD3">(1) Preplanning: Planning the Plan </HD>
                    <P>
                        (a) Planning Team. The Regional Chief, National Wildlife Refuge System, appoints the Planning Team Leader. The Planning Team Leader assembles the planning team, which consists of the Planning Team Leader, the Refuge Manager and key staff members, and appropriate support staff or specialists from both regional and field offices (
                        <E T="03">e.g.,</E>
                         fisheries, cultural resources, endangered species, external affairs/outreach, realty, contaminants, migratory birds, water resources, etc.). We will provide representatives from appropriate State and Tribal conservation agencies, and any public agency that may have a direct land management relationship with the refuge, the opportunity to serve on planning teams. The Planning Team Leader will prepare a formal written request for participation by appropriate State and Tribal conservation agencies for signature by the Regional Director. Included in this request is an invitation to attend the NCTC course on Refuge Comprehensive Conservation Planning. Participation by these State and Tribal agencies shall not be subject to the Federal Advisory Committee Act. 
                    </P>
                    <P>
                        (b) Identify Refuge Purpose(s), History, and Establishing Authority. Document the history of refuge establishment and management, as well as refuge purposes and authorizing authority (
                        <E T="03">e.g.,</E>
                         legislation [including wilderness designation, if applicable], executive orders, administrative memoranda) (
                        <E T="03">see</E>
                         601 FW 1). These will become driving forces in the process and subsequently be reflected in the 
                        <PRTPAGE P="33911"/>
                        refuge vision statement, goals, objectives, and strategies in the CCP. 
                    </P>
                    <P>
                        (c) Identify Planning and Compliance Requirements and Special Designations. Review our agency and Refuge System mission statements and policies, as well as other existing legislation to help identify planning and compliance requirements. 
                        <E T="03">See</E>
                         Exhibit 3-2 for a list of laws and executive orders that may apply and Exhibit 3-3 for a checklist of elements we must include within a CCP. Identify and review other Service guidance such as Fulfilling the Promise: The National Wildlife Refuge System and mandates including laws, executive orders, regulations, and our policies, especially those with compliance requirements. Also review any existing special designation areas such as wilderness, research natural areas, wild and scenic rivers, wetlands of international importance (Ramsar sites), Western Hemisphere Shorebird Reserves, etc., and specifically address the potential for any new special designations. Concurrent with the CCP process we will conduct a wilderness review and incorporate a summary of the review into the CCP. (
                        <E T="03">See</E>
                         Part 610 of the Service Manual for guidance on conducting wilderness reviews.) Complete the inventory phase of the review during preplanning. If a Wilderness Study Area is identified, proceed with the study and recommendation phases of the review. (Note: An EIS is the NEPA document we must include in a recommendation or report on a legislative proposal to Congress [40 CFR 1506.8]. This requirement applies to all CCPs that contain wilderness recommendations.) 
                    </P>
                    <P>(d) Purpose and Need for the Plan. The purpose of developing the CCP is to provide the Refuge Manager with a 15-year management plan for the conservation of fish, wildlife, and plant resources and their related habitats, while providing opportunities for compatible wildlife-dependent recreational uses. The CCP, when fully implemented, should achieve refuge purposes; help fulfill the Refuge System mission; maintain and, where appropriate, restore the ecological integrity of each refuge and the Refuge System; help achieve the goals of the National Wilderness Preservation System; and meet other mandates. The CCP must be specific to the planning unit and identify the overarching wildlife, public use, or management needs for the refuge. </P>
                    <P>(e) Planning Area and Data Needs. Delineate the planning area on a map. Identify the relationship between the planning unit and its ecosystem(s) and watershed(s) as well as relationships between the planning unit and any other refuges or other important fish and wildlife habitats in the vicinity. Identify data available to address issues discussed in Step (h) Internal Scoping. Obtain information from Federal, Tribal, State and local agencies, and private landowners concerning land management issues that may impact or relate to the planning unit. To assist in determining species or resources of concern, consult the following: Federal threatened and endangered species lists; Migratory Nongame Birds of Management Concern in the United States; Partners in Flight Watch List; State lists of rare, threatened, endangered, or species of concern; National Audubon Society State Watch Lists; The Nature Conservancy's heritage program and ranking system; as well as State heritage databases and conservation data centers for additional sources of information. Also identify resource experts familiar with the key species and habitats in the planning area, and consult with these experts during the development of habitat objectives. Base CCPs on a comprehensive assessment of the existing scientific literature. Potential sources of information include planning documents, EAs, EISs, annual narrative reports, information from previously conducted or ongoing research, data from refuge inventories or studies, published literature on related biological studies, State conservation management plans, field management experience, etc. While we may not be able to develop new data for the CCP, we may identify the need for further data collection. A lack of data should not delay the completion of the CCP. Identify and describe the following conditions and their trends for the planning unit and, as appropriate, for the planning area: </P>
                    <P>(i) Context of the planning unit in relation to the surrounding ecosystem. </P>
                    <P>(ii) Structures, components, and functions of the ecosystem(s) of which the planning unit is a part. </P>
                    <P>(iii) Natural and historic role of fire and other natural occurrences affecting ecological processes. </P>
                    <P>(iv) Past land use and history of settlement, including a description of any changes in topography, hydrology, and other factors. </P>
                    <P>(v) Current and historic description of the flora and fauna and the diversity of habitats and natural communities. </P>
                    <P>(vi) Distribution, migration patterns, and abundance of fish, wildlife, and plant populations, including any threatened or endangered species, and related habitats. </P>
                    <P>(vii) Fish, wildlife, and plants and their habitats and communities that are rare and/or declining within the ecosystem. </P>
                    <P>(viii) Water resources including quality and quantity. </P>
                    <P>(ix) Archaeological and other cultural resources. </P>
                    <P>(x) Significant problems that may adversely affect the ecological integrity or wilderness characteristics and the actions necessary to correct or mitigate the problems. </P>
                    <P>(xi) Identify opportunities to improve the health of habitats or the functioning of ecosystems. </P>
                    <P>(xii) Significant problems that may adversely affect the populations and habitats of fish, wildlife, and plants (including candidate, threatened, and endangered species) and the actions necessary to correct or mitigate the problems. </P>
                    <P>(xiii) Known or suspected sources of environmental contaminants and their potential impacts on the planning unit (refer to the Contaminant Assessment Program). </P>
                    <P>(xiv) Land acquisition or habitat protection efforts. </P>
                    <P>(xv) Habitat management practices. </P>
                    <P>(xvi) Existing administrative resources, including staffing, funding, and facilities. </P>
                    <P>(xvii) Existing transportation patterns and related visitor facilities. </P>
                    <P>(xviii) Potential need for administrative sites, transportation improvements, or visitor facilities and areas within the planning unit that are suitable for such sites. </P>
                    <P>(xix) Existing and potential opportunities for wildlife-dependent recreation. </P>
                    <P>
                        (xx) Existing special management areas, or the potential for such designations (
                        <E T="03">e.g.,</E>
                         wilderness, research natural areas, and wild and scenic rivers). 
                    </P>
                    <P>
                        (f) Review All Available Information, Plans, Data, Maps, and Data Standards. Based on this review, determine what the initial planning area includes and identify any additional information and data needs, including mapping and GIS needs. Note: All Federal agencies and their contractors must comply with data standards endorsed by the Federal Geographic Data Committee (Executive Order 12906; 59 FR 17671, April 13, 1994). Of particular relevance to refuge planning are the National Vegetation Classification Standard (FGDC-STD-005) and the Classification of Wetlands and Deep Water Habitats (FGDC-STD-004). Compliance with these standards will facilitate the sharing and exchange of high-quality vegetation and wetland data among Federal agencies and their 
                        <PRTPAGE P="33912"/>
                        partners. We also are developing other data standards, such as cartographic standards for delineation of refuge boundaries and land status. 
                    </P>
                    <P>(g) Vision and Goals. Review the existing planning unit vision statement and goals and determine the need for revision. If these do not exist, prepare a draft vision statement and goals for consideration during public scoping. The vision statement should focus on what will be different in the future because of our efforts, capture the essence of what we are trying to do, and why. It should be future-oriented, concise, clear, compelling, and give a sense of purpose to our efforts. At a minimum, each refuge should develop goals for wildlife species or groups of species, habitat (including land protection needs), compatible wildlife-dependent recreation, other mandates (such as refuge-specific legislation, executive orders, special area designations, etc.), and fish, wildlife, and plant populations, as appropriate. The vision statement and goals will reflect planning unit purposes; help fulfill the mission of the Refuge System; maintain and, where appropriate, restore ecological integrity; and will be consistent with mandates and principles of sound fish and wildlife management. Planning unit goals also will reflect our ecosystem goals to the extent these goals do not conflict with the Refuge System mission or the purposes for which the refuge was established. We also may develop refuge goals for our other mandates. Subsequently, we will develop objectives for achieving planning unit goals (see 602 FW 3.4 C (4)(d) Objective Development). For additional information on developing goals and objectives, see the current edition of Writing Refuge Management Goals and Objectives: A Handbook. </P>
                    <P>(h) Internal Scoping. Begin the internal scoping process by identifying management concerns, issues, and opportunities to resolve them, as well as any potential impacts and alternatives that we may need to address in the CCP and NEPA analysis. Review the background, rationale, and the success or failure of any controversial management actions and identify any additional information and data needed where appropriate. </P>
                    <P>(i) Public Involvement/Outreach Planning. Prepare a Public Involvement/Outreach Plan indicating how and when we will invite the affected public to participate in CCP development. This plan will include establishing a mailing list and identifying appropriate techniques and materials to use in public involvement. We integrate public involvement and outreach into each step, and it continues throughout the planning process. For additional information on public involvement techniques, consult the Public Participation Handbook (U.S. Fish and Wildlife Service, 1985) or the NCTC Refuge Comprehensive Conservation Planning Course Handbook and Reference Notebook. </P>
                    <P>(j) Work Plan/Planning Schedule. Establish a work plan or planning schedule for the CCP. Determine who will be responsible for carrying out identified tasks, gathering information and data, and preparing products identified in the work plan or schedule. Identify all key NEPA compliance steps and public involvement activities. Identify any additional expertise, besides the planning team, required to prepare the CCP. This may include an economist, a facilitator for public and other meetings, other contracted professional services, etc. </P>
                    <P>(k) Planning Record. Establish a planning record to document the preparation of the CCP and NEPA compliance, and assign its maintenance to a team member. The planning record will serve as a valuable reference and provide important background and historical information. If there is a legal challenge to the CCP, use the planning record to construct the administrative record. For additional information on the planning record, consult the NCTC Refuge Comprehensive Conservation Planning Course Handbook and Reference Notebook. </P>
                    <HD SOURCE="HD3">(2) Initiate Public Involvement and Scoping </HD>
                    <P>
                        (a) Notice of Intent. Prepare a Notice of Intent (NOI) to prepare a CCP, with appropriate NEPA compliance, and publish the NOI in the 
                        <E T="04">Federal Register</E>
                        . The NOI initiates public scoping for the CCP/NEPA planning and decision-making process. If we initially determine that we will prepare an EIS for the CCP, the NOI should specify that. If at any time during the planning process we decide to prepare an EIS, we will publish in the 
                        <E T="04">Federal Register</E>
                         a new NOI to prepare an EIS and provide additional time for the public to comment. Should we publish a new NOI, we will use news releases and other appropriate means to notify the public. 
                    </P>
                    <P>(b) Public Scoping. Using news releases to the local media and other appropriate means, notify the affected public of the opportunity to participate in the preparation of the CCP and begin the scoping process. Involve the public and gather comments on any existing planning unit vision statement and goals. Encourage the public to help identify potential issues, management actions and concerns, significant problems or impacts, and opportunities or alternatives to resolve them. Public scoping will continue until we prepare a draft CCP/NEPA document. </P>
                    <P>(c) Issues and Data Needs. Analyze all comments gathered and recorded during the scoping process. Identify any new information, issues, concerns, or significant problems, opportunities to resolve them, and potential refinements or revisions of any existing planning unit vision statement and goals. Based on this analysis, identify any additional information and data needed. </P>
                    <HD SOURCE="HD3">(3) Review Vision Statement and Goals and Determine Significant Issues </HD>
                    <P>(a) Vision and Goals. Review and evaluate the public's comments on the planning unit vision statement and goals. Based on this review, modify the vision and goals for the planning unit as appropriate. </P>
                    <P>
                        (b) Determine Significant Issues. Review and evaluate all potential issues, management concerns, and problems and the opportunities to resolve them that the planning team and the public have identified. Identify those issues and concerns that are significant, and the appropriate scale at which to consider those issues. Document the rationale for selecting significant issues, as well as the rationale for not selecting the other issues and concerns (
                        <E T="03">e.g.,</E>
                         outside the scope of the CCP, does not contribute to achieving refuge purposes, Refuge System mission, etc.). Significant issues typically are those that are: Within our jurisdiction, suggest different actions or alternatives, and will influence our decision. We will refer those issues identified outside the scope of refuge planning to the pertinent Service program office or division. 
                    </P>
                    <HD SOURCE="HD3">(4) Develop and Analyze Alternatives, Including the Proposed Action</HD>
                    <P>
                        This part of the process is not sequential, it is iterative. Iterative procedures in this step of the process include: Issue assessment; refinement and development of goals, objectives, and strategies; analysis and comparison of impacts and benefits of management actions; and the packaging or combining of similar themes or programs to develop preliminary alternatives and assessment of their environmental consequences. The alternatives should reflect different sets of objectives and strategies to achieve refuge purposes, vision, and goals, help fulfill the Refuge System mission, and resolve issues. Prepare maps depicting the different strategies reflected in each alternative. Also display this information in a 
                        <PRTPAGE P="33913"/>
                        matrix comparing issues, impacts, and benefits for each alternative. 
                    </P>
                    <P>(a) No Action Alternative. Define the No Action Alternative, which is usually a continuation of current planning unit objectives and management strategies, with no changes or changes that would have occurred without the CCP. </P>
                    <P>(b) A Range of Alternatives. Develop a range of alternatives, or different approaches to planning unit management, that we could reasonably undertake to achieve planning unit goals and refuge purposes; help fulfill the Refuge System mission; maintain and, where appropriate, restore the ecological integrity of each refuge and the Refuge System; help achieve the goals of the National Wilderness Preservation System; meet other mandates, and resolve any significant issues identified. Alternatives consist of different sets of objectives and strategies for management of the refuge. Give equal effort to each alternative regarding specific objectives and strategies so that the decision maker can make an informed choice. NEPA requires an equal and full analysis of all alternatives considered for implementation. </P>
                    <P>(c) Proposed Action. The planning team will recommend a proposed action in the NEPA document for the CCP identifying the alternative that best achieves planning unit purposes, vision, and goals; helps fulfill the Refuge System mission; maintains and, where appropriate, restores the ecological integrity of each refuge and the Refuge System; addresses the significant issues and mandates; and is consistent with principles of sound fish and wildlife management. The proposed action is, for all practical purposes, the draft CCP for the planning unit. </P>
                    <P>
                        (d) Objective Development. Develop objectives to address each goal. Word objectives so it is clear what we can measure during monitoring to assess progress toward their attainment. Consult the Service Manual chapters on habitat management, populations management, wilderness management, and wildlife-dependent recreation during the development of objectives. Develop detailed, measurable objectives using available scientific literature and other appropriate information. Develop objectives with consideration of regional and Service ecosystem goals and objectives. Develop objectives for specific refuge habitat types, management units, key species (
                        <E T="03">e.g.,</E>
                         migratory birds and threatened and endangered species), wildlife-dependent recreation, monitoring populations of fish, wildlife, and plants and their habitats, and other areas of management, as appropriate. Objectives also may deal with refuge information needs (for example, including the development of baseline data), administrative needs, and any other issues we need to address to meet the goals of the refuge. Document in a short narrative summary the rationale, including appropriate literature citations, that supports each objective. Also consult the current edition of Writing Refuge Management Goals and Objectives: A Handbook. Developing detailed objectives at this stage will expedite development of step-down management plans when required. 
                    </P>
                    <P>(e) Strategy Development. Develop strategies to identify the specific actions, tools, or techniques that are necessary to accomplish each objective. Strategies represent specific projects that provide the detail required to assess and develop funding, staffing, and partnerships needed to implement the plan. Develop inventory and monitoring strategies to measure implementation results in quantifiable and verifiable ways. We may require step-down management plans to provide the specific details of how to achieve goals and objectives identified in the CCP. </P>
                    <P>(f) Environmental Consequences. Assess the environmental consequences (direct, indirect, and cumulative) of implementing each alternative as required by NEPA. Compare the consequences of implementing each alternative in relation to the No Action Alternative, which serves as a baseline. Describe the adverse and beneficial impacts of implementing each alternative on fish, wildlife, and plants, and their habitats; any threatened or endangered species; cultural resources; the local economy; the ability to provide opportunities for compatible wildlife-dependent recreational uses; conflicts between priority uses and other uses; and other issues identified earlier in the planning process. This analysis must provide the level of detail necessary to assess the compatibility of all proposed uses. Describe each alternative's ability to achieve planning unit purpose(s), vision, and goals; help fulfill the Refuge System mission; ensure that we maintain and, where appropriate, restore the ecological integrity of each refuge and the Refuge System; and address the significant issues and mandates. This assessment also will identify the funding, staffing, and facilities required for implementation of each alternative. </P>
                    <HD SOURCE="HD3">(5) Prepare Draft Plan and NEPA Document </HD>
                    <P>(a) Draft CCP and NEPA Document. Concurrently prepare the draft CCP and appropriate NEPA documentation (EA or EIS). When preparing an EA, consider integrating the draft CCP with the EA. When preparing an EIS with a CCP, integrate the documents. If the decision is to prepare a separate EA, see Exhibit 3-4 for a recommended CCP outline. If the documents are separate, the proposed action in the EA must contain all of the major actions of the draft CCP. If the decision is to merge the CCP and EA, see Exhibit 3-5 for a recommended outline. During the process of preparing the CCP, refer to Exhibit 3-3 to ensure inclusion of all required elements in the plan. Ensure compliance regarding other programs and policies, including: Section 7 of the Endangered Species Act; Sections 401 and 404 of the Clean Water Act; Sections 106 and 110 of the National Historic Preservation Act; Section 14 of the Archaeological Resources Protection Act; Executive Order 13007—Indian Sacred Sites; Executive Order 11988—Floodplain Management; Executive Order 11990—Protection of Wetlands; etc. See Exhibit 3-2 for a list of mandates to consider during the planning process. </P>
                    <P>(b) Compatibility Determinations. Complete new compatibility determinations or re-evaluate existing compatibility determinations as part of the CCP process for all individual uses, specific use programs, or groups of related uses associated with the proposed action. Prepared concurrently with the CCP, incorporate the draft compatibility determinations into the draft CCP as an appendix. We require public review and comment for all compatibility determinations. We can achieve this concurrently through public review and comment of the draft CCP and NEPA document. While other alternatives do not require compatibility determinations, assess the environmental consequences, and, for all practical purposes, compatibility of all uses proposed in those alternatives in the NEPA document. For additional information on compatibility determinations, see 603 FW 2. </P>
                    <P>(c) Pre-acquisition Compatibility Determinations. If our proposed action includes expanding the planning unit by acquiring new lands, the draft CCP and NEPA documents also must identify any existing wildlife-dependent recreational public uses deemed compatible that we will allow to continue after acquisition. Incorporate these pre-acquisition compatibility determinations into the draft CCP and NEPA document. </P>
                    <P>
                        (d) Internal Review. Submit the draft CCP and NEPA document for internal review within the Region following established procedures. Include in the review refuge program managers, 
                        <PRTPAGE P="33914"/>
                        ecosystem managers, refuge staff and other appropriate Service programs and divisions, as well as other agency partners. Also submit these documents for internal review to the Regional and Washington Office Planning Coordinators. Consider all comments received from the internal reviews and make appropriate changes to the draft document. Print the draft CCP and NEPA document and prepare for public review. 
                    </P>
                    <P>
                        (e) Public Notice, Review, and Comment. Prepare a Notice of Availability of the draft CCP and NEPA document and publish it in the 
                        <E T="04">Federal Register</E>
                        . Notify the affected public of the availability of these documents through other appropriate means, as identified in the Public Involvement/Outreach Plan. Public notices will make clear that we are seeking concurrent review on compatibility determinations. Provide a minimum of 30 days for public review of a draft CCP with an EA and 45 days for a draft CCP with an integrated EIS. Make copies of the draft CCP and NEPA document available to appropriate elected officials; Federal, State, and local agencies; Tribal governments; organizations; libraries (including NCTC); resource experts; adjacent landowners; and individuals requesting them. Conduct appropriate public involvement activities as called for in the Public Involvement/Outreach Plan. Document all public comments, both written and oral, received on the draft CCP and NEPA document as part of the planning record. 
                    </P>
                    <HD SOURCE="HD3">(6) Prepare and Adopt Final Plan </HD>
                    <P>(a) Public Comment, Analysis, and Response. Review and analyze all written and oral comments received from the public on the draft CCP and NEPA document. Determine which comments are substantive and warrant written response. Modify the document(s) as appropriate. Prepare a summary of the public comments received and a statement of the disposition of concerns expressed in those comments, noting where we have changed the document(s) or why we did not make such changes. Incorporate the summary and statement of disposition into the final document(s) (usually in the NEPA document or a CCP appendix). </P>
                    <P>(b) Final CCP and NEPA Document(s). Identify the preferred alternative and prepare the final CCP and appropriate NEPA documentation. The preferred alternative can be the proposed action, the no action alternative, another alternative, or a combination of actions or alternatives discussed in the draft CCP and NEPA document. Following completion of the final CCP/NEPA document, the product of the CCP process is a stand-alone CCP (the preferred alternative for the planning unit). During the process of preparing the final plan, refer to Exhibit 3-3 to ensure inclusion of all required elements. </P>
                    <P>(c) Internal Review. Submit the final document(s) for internal review within the Region according to established procedures. Refer to 3.4 C (5)(d) for a list of those to include in the review. Consider all comments received from the internal review and make appropriate changes to the final document(s). </P>
                    <P>(d) Decision Document. The decision document (either a Finding of No Significant Impact [FONSI] or a Record of Decision [ROD]) will certify that we have met agency compliance requirements and that the CCP, when implemented, will achieve the purposes of the refuge and help fulfill the Refuge System mission. </P>
                    <P>(i) CCP with an EA and FONSI. The Refuge Manager and Planning Team Leader submit the final CCP and FONSI through line supervision for concurrence and approval by the Regional Director. The Regional Director will sign and date both the FONSI and the final CCP. Following approval, print and distribute the final document(s) and appropriate appendices. Provide the FONSI to all interested and affected parties. Concurrent with the distribution of the FONSI, provide the final, approved, stand-alone CCP or a summary to all interested parties. In some cases we may require a 30-day public review period for the FONSI (see 550 FW 3.3 B (4)(c)). In these cases, we may not sign or release the final CCP until the end of the 30-day review. </P>
                    <P>(ii) CCP with an EIS and ROD. The Refuge Manager and Planning Team Leader submit the final EIS/CCP through line supervision for concurrence and approval to release these documents to the public. Provide these documents to interested and affected parties for at least 30 days prior to issuing a ROD. Following this period, submit the ROD through line supervision for concurrence and approval by the Regional Director. The Regional Director will sign and date both the ROD and the final CCP. Following approval, print the final documents and appropriate appendices. Provide the ROD or notification of its availability to all interested and affected parties. Concurrent with the release of the ROD, provide or make available the final, approved, stand-alone CCP or a summary to interested parties. Effective with the signing and release of the ROD, implement the CCP. </P>
                    <P>(iii) Stand-Alone CCP. The final product of the CCP process is a stand-alone CCP (the preferred alternative for the planning unit). </P>
                    <P>
                        (e) Public Notice. Prepare a Notice of Availability of the final approved CCP and NEPA document(s) and publish it in the 
                        <E T="04">Federal Register</E>
                        . Notify the affected public of the availability of the final document(s) through other appropriate means, as identified in the Public Involvement/Outreach Plan. Send copies of all final documents to the Regional and Washington Office Planning Coordinators. Make copies of the final approved CCP and NEPA document(s) available to appropriate elected officials; Federal, State, and local agencies; Tribal governments; organizations; libraries (including NCTC); adjacent landowners; and individuals requesting them. 
                    </P>
                    <HD SOURCE="HD3">(7) Implement Plan, Monitor, and Evaluate</HD>
                    <P>Following approval of the CCP and public notification of the decision, begin implementing the strategies identified in the CCP. Allocate funding and staff time to the priority strategies as defined in the CCP. Initiate the monitoring and evaluation process identified in the CCP to determine if we are making progress in achieving the planning unit purpose(s), vision, and goals. Monitoring should address habitat or population objectives, and the effects of management activities. See 701 FW 2. Describe the sampling design sufficiently so it may be replicated. Through adaptive management, evaluation of monitoring and research results may indicate the need to modify refuge objectives or strategies. </P>
                    <HD SOURCE="HD3">(8) Review and Revise Plan </HD>
                    <P>(a) Plan Review. Review the CCP at least annually to decide if it requires any revisions. Modify the plan and associated management activities whenever this review or other monitoring and evaluation determine that we need changes to achieve planning unit purpose(s), vision, and goals. </P>
                    <P>
                        (b) Plan Revision. Revise the CCP when significant new information becomes available, ecological conditions change, major refuge expansion occurs, or when we identify the need to do so during plan review. This should occur every 15 years or sooner, if necessary. All plan revisions should follow the procedures outlined in this policy for preparing plans and will require NEPA compliance. Document minor plan revisions that meet the criteria of a 
                        <PRTPAGE P="33915"/>
                        categorical exclusion in an Environmental Action Statement, in accordance with 550 FW 3.3 C. Contact the Regional NEPA Coordinator for an up-to-date list of categorical exclusions and for other NEPA assistance. If the plan requires a major revision, then the CCP process starts anew at the preplanning step. See 602 FW 3.4 C (1). 
                    </P>
                    <P>(c) Ongoing Public Involvement. Continue informing and involving the public through appropriate means.</P>
                    <BILCOD>BILLING CODE 4310-55-P</BILCOD>
                    <GPH SPAN="3" DEEP="480">
                        <PRTPAGE P="33916"/>
                        <GID>EN25MY00.001</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4310-55-C</BILCOD>
                    <EXTRACT>
                        <WIDE>
                            <PRTPAGE P="33917"/>
                            <HD SOURCE="HD1">Exhibit 3-2.—Mandates To Consider During Comprehensive Conservation Planning </HD>
                        </WIDE>
                        <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s200,20">
                            <TTITLE>  </TTITLE>
                            <BOXHD>
                                <CHED H="1">  </CHED>
                                <CHED H="1">Yes/No </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="11">Applicable Statutes: </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Alaska National Interest Lands Conservation Act of 1980, as amended </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">American Indian Religious Freedom Act of 1978 </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Americans With Disabilities Act of 1990 </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Anadromous Fish Conservation Act of 1965, as amended </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Antiquities Act of 1906 </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Archaeological and Historic Preservation Act of 1974 </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Archaeological Resources Protection Act of 1979, as amended </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Bald and Golden Eagle Protection Act of 1940, as amended </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Clean Air Act of 1970 </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Clean Water Act of 1974, as amended </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Coastal Zone Management Act of 1972, as amended </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Emergency Wetlands Resources Act of 1986 </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Endangered Species Act of 1973, as amended </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Farmland Protection Act of 1981, as amended </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Federal Cave Protection Act of 1988 </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Federal Noxious Weed Act of 1990 </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Fish and Wildlife Act of 1956 </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Fish and Wildlife Coordination Act of 1958 </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Fishery (Magnuson) Conservation and Management Act of 1976 </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Marine Mammal Protection Act of 1972, as amended </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Migratory Bird Conservation Act of 1929 </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Migratory Bird Hunting and Conservation Stamp Act of 1934 </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Migratory Bird Treaty Act of 1918, as amended </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">National Environmental Policy Act of 1969 </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">National Historic Preservation Act of 1966, as amended </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">National Wildlife Refuge System Administration Act of 1966, as amended </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Native American Graves Protection and Repatriation Act of 1990 </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Refuge Recreation Act of 1962, as amended </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Rivers and Harbors Act of 1899 </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Water Resources Planning Act of 1965 (sole-source aquifers) </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Wild and Scenic Rivers Act of 1968, as amended </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Wilderness Act of 1964, as amended </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="11">Applicable Executive Orders: </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Executive Order 11644, Use of Off-Road Vehicles on Public Lands </ENT>
                                <ENT>__________ </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Executive Order 11987, Exotic Organisms </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Executive Order 11988, Floodplain Management </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Executive Order 11990, Protection of Wetlands </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Executive Order 12898, Environmental Justice for Minority  Populations </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Executive Order 12962, Recreational Fisheries </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Executive Order 12996, Management and General Public Use of the National Wildlife Refuge System </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Executive Order 13007, Indian Sacred Sites </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Executive Order 13084, Consultation and Coordination With Indian Tribal Governments </ENT>
                                <ENT>__________</ENT>
                            </ROW>
                            <TNOTE>Note: This list is not all inclusive. There may be other executive orders and statutes that apply to a particular planning unit. </TNOTE>
                        </GPOTABLE>
                    </EXTRACT>
                    <EXHIBIT>
                        <HD SOURCE="HED">Exhibit 3-3.—Checklist of Required Comprehensive Conservation Plan Elements </HD>
                        <FP SOURCE="FP-2">__Short description of the planning unit to include: </FP>
                        <FP SOURCE="FP-2">__Size </FP>
                        <FP SOURCE="FP-2">__Establishment date </FP>
                        <FP SOURCE="FP-2">__Regional setting (include area map) </FP>
                        <FP SOURCE="FP-2">__Land acquisition or habitat protection efforts </FP>
                        <FP SOURCE="FP-2">__Current management (including a map) </FP>
                        <FP SOURCE="FP-2">__Current staffing </FP>
                        <FP SOURCE="FP-2">__Existing partnerships </FP>
                        <FP SOURCE="FP-2">__Purpose(s) for which the refuge was established </FP>
                        <FP SOURCE="FP-2">__Past land use and history of settlement, including a description of any changes in topography, hydrology, and other factors </FP>
                        <FP SOURCE="FP-2">__Existing transportation patterns and related visitor facilities </FP>
                        <FP SOURCE="FP-2">__Habitat management practices </FP>
                        <FP SOURCE="FP-2">__Refuge System mission and goals. </FP>
                        <FP SOURCE="FP-2">__Ecosystem goals and objectives. </FP>
                        <FP SOURCE="FP-2">__Goals and objectives for other landscape-level plans. </FP>
                        <FP SOURCE="FP-2">
                            __National goals and objectives for species, species groups, habitats and communities, or programs (
                            <E T="03">e.g.,</E>
                             shorebirds, an endangered species, priority public use program). 
                        </FP>
                        <FP SOURCE="FP-2">__Identify any mandates that apply to the area or the proposed plan. </FP>
                        <FP SOURCE="FP-2">__Description of the planning unit environment to include: </FP>
                        <FP SOURCE="FP1-2">__distribution, migration patterns, and abundance of fish, wildlife, and plant populations, including any threatened or endangered species and related habitats; </FP>
                        <FP SOURCE="FP1-2">__current and historic description of the flora and fauna, and the diversity of habitats and natural communities; </FP>
                        <FP SOURCE="FP1-2">__wildlife habitat and species relationships; </FP>
                        <FP SOURCE="FP1-2">__ability of the planning unit to meet the habitat needs of fish, wildlife, and plants, as they occur throughout their natural ranges; </FP>
                        <FP SOURCE="FP1-2">__vegetation types (Federal Geographic Data Committee compliant map required); </FP>
                        <FP SOURCE="FP1-2">__vegetation/land cover and wildlife habitat relationships; </FP>
                        <FP SOURCE="FP1-2">__significant problems that may adversely affect the ecological integrity or wilderness characteristics and the actions necessary to correct or mitigate the problems; </FP>
                        <FP SOURCE="FP1-2">__context of the planning unit in relation to the surrounding ecosystem; </FP>
                        <FP SOURCE="FP1-2">__structures, components, and functions of the ecosystem(s) of which the planning unit is a part; </FP>
                        <FP SOURCE="FP1-2">__fish, wildlife, and plants and their habitats and communities that are rare and/or declining within the ecosystem; </FP>
                        <FP SOURCE="FP1-2">__archaeological and cultural resources of the planning unit;</FP>
                        <FP SOURCE="FP1-2">__refuge land status map; </FP>
                        <FP SOURCE="FP1-2">
                            __natural and historic role of fire and other natural occurrences affecting ecological processes; 
                            <PRTPAGE P="33918"/>
                        </FP>
                        <FP SOURCE="FP1-2">
                            __existing special management areas (
                            <E T="03">e.g.,</E>
                             wilderness, wild and scenic rivers); 
                        </FP>
                        <FP SOURCE="FP1-2">__relationship between the planning unit and other refuges and protected areas. </FP>
                        <FP SOURCE="FP-2">__Document and describe the following: </FP>
                        <FP SOURCE="FP1-2">__significant problems that may adversely affect the populations and habitats of fish, wildlife, and plants within the planning unit (including candidate, threatened, and endangered species) and the actions necessary to correct or mitigate such problems; </FP>
                        <FP SOURCE="FP1-2">__water resources including quantity and quality; </FP>
                        <FP SOURCE="FP1-2">__known or suspected sources of environmental contaminants and their potential impacts on the planning unit (refer to the Contaminant Assessment Program); </FP>
                        <FP SOURCE="FP1-2">
                            __potential for special management area designations (
                            <E T="03">e.g.,</E>
                             wilderness, research natural areas, and wild and scenic rivers); 
                        </FP>
                        <FP SOURCE="FP1-2">__summary of management history; </FP>
                        <FP SOURCE="FP1-2">__other significant issues of management or public concern; </FP>
                        <FP SOURCE="FP1-2">__existing and potential opportunities for wildlife-dependent recreation; </FP>
                        <FP SOURCE="FP1-2">__existing administrative resources, including staffing, funding, and facilities; </FP>
                        <FP SOURCE="FP1-2">__potential need for administrative sites, transportation improvements, or visitor facilities and areas within the planning unit that are suitable for such sites. </FP>
                        <FP SOURCE="FP-2">__Vision statement. </FP>
                        <FP SOURCE="FP-2">__Goals for at least the following areas: </FP>
                        <FP SOURCE="FP1-2">__wildlife species or groups of species; </FP>
                        <FP SOURCE="FP1-2">__habitat (including land protection needs); </FP>
                        <FP SOURCE="FP1-2">__fish, wildlife, and plant populations, as appropriate; </FP>
                        <FP SOURCE="FP1-2">__compatible wildlife-dependent recreation; </FP>
                        <FP SOURCE="FP1-2">__others as needed to meet mandates (such as refuge-specific legislation, executive orders, special area designations, etc.). </FP>
                        <FP SOURCE="FP-2">__Objectives for each goal. </FP>
                        <FP SOURCE="FP-2">__Strategies to achieve each objective. </FP>
                        <FP SOURCE="FP-2">
                            __Map(s) of desired future conditions (
                            <E T="03">e.g.,</E>
                             habitat management areas, facilities, wildlife-dependent recreation sites, etc.). 
                        </FP>
                        <FP SOURCE="FP-2">__Identification of step-down management plans required to fully implement the CCP. </FP>
                        <FP SOURCE="FP-2">__Prioritized list of projects and estimated project costs (update priorities and cost estimates annually). </FP>
                        <FP SOURCE="FP-2">__Staffing and funding required to implement the plan. </FP>
                        <FP SOURCE="FP-2">__Potential partnership opportunities. </FP>
                        <FP SOURCE="FP-2">__Monitoring plan to evaluate the effectiveness of the plan and project implementation, including monitoring of target fish, wildlife, and plant populations and their habitats. </FP>
                        <FP SOURCE="FP-2">__Summary of public involvement process, comments received and their disposition, and consultation and coordination with other Federal agencies, State conservation agencies, and adjacent landowners. </FP>
                        <FP SOURCE="FP-2">__Compatibility determinations (including pre-acquisition compatibility determinations). </FP>
                        <FP SOURCE="FP-2">__Wilderness review. </FP>
                        <FP SOURCE="FP-2">__Habitat/Land Protection Plans (if applicable). </FP>
                        <FP SOURCE="FP-2">__NEPA documentation. </FP>
                    </EXHIBIT>
                    <EXHIBIT>
                        <HD SOURCE="HED">Exhibit 3-4.—Refuge Comprehensive Conservation Plan Recommended Outline </HD>
                        <FP SOURCE="FP-2">Cover Sheet </FP>
                        <FP SOURCE="FP-2">Title/Approval Page </FP>
                        <FP SOURCE="FP-2">Acknowledgments </FP>
                        <FP SOURCE="FP-2">Table of Contents </FP>
                        <FP SOURCE="FP-2">Summary </FP>
                        <FP SOURCE="FP-2">I. Introduction/Background </FP>
                        <FP SOURCE="FP1-2">Refuge Overview: History of Refuge Establishment, Acquisition, and Management </FP>
                        <FP SOURCE="FP1-2">Purpose of and Need for Plan </FP>
                        <FP SOURCE="FP1-2">NWRS Mission, Goals, and Guiding Principles </FP>
                        <FP SOURCE="FP1-2">Refuge Purpose(s) </FP>
                        <FP SOURCE="FP1-2">Refuge Vision Statement </FP>
                        <FP SOURCE="FP1-2">Legal and Policy Guidance </FP>
                        <FP SOURCE="FP1-2">Existing Partnerships </FP>
                        <FP SOURCE="FP-2">II. Planning Process </FP>
                        <FP SOURCE="FP1-2">Description of Planning Process </FP>
                        <FP SOURCE="FP1-2">Planning Issues </FP>
                        <FP SOURCE="FP-2">III. Summary Refuge and Resource Descriptions </FP>
                        <FP SOURCE="FP1-2">Geographic/Ecosystem Setting </FP>
                        <FP SOURCE="FP1-2">Refuge Resources, Cultural Resources, and Public Uses </FP>
                        <FP SOURCE="FP1-2">Special Management Areas </FP>
                        <FP SOURCE="FP-2">IV. Management Direction </FP>
                        <FP SOURCE="FP1-2">Refuge Management Direction: Goals, Objectives, and Strategies </FP>
                        <FP SOURCE="FP1-2">Refuge Management Policies and Guidelines </FP>
                        <FP SOURCE="FP-2">V. Implementation and Monitoring </FP>
                        <FP SOURCE="FP1-2">Funding and Personnel </FP>
                        <FP SOURCE="FP1-2">Step-Down Management Plans </FP>
                        <FP SOURCE="FP1-2">Partnership Opportunities </FP>
                        <FP SOURCE="FP1-2">Monitoring and Evaluation </FP>
                        <FP SOURCE="FP1-2">Plan Amendment and Revision </FP>
                        <FP SOURCE="FP-2">Appendices </FP>
                        <FP SOURCE="FP1-2">Glossary </FP>
                        <FP SOURCE="FP1-2">Bibliography </FP>
                        <FP SOURCE="FP1-2">RONS List </FP>
                        <FP SOURCE="FP1-2">MMS list </FP>
                        <FP SOURCE="FP1-2">Compatibility Determinations </FP>
                        <FP SOURCE="FP1-2">Habitat/Land Protection Plan(s) </FP>
                        <FP SOURCE="FP1-2">Compliance Requirements </FP>
                        <FP SOURCE="FP1-2">NEPA Documentation </FP>
                        <FP SOURCE="FP1-2">Summary of Public Involvement/Comments and Consultation/Coordination </FP>
                        <FP SOURCE="FP1-2">Mailing List </FP>
                        <FP SOURCE="FP1-2">List of Preparers </FP>
                        <FP SOURCE="FP1-2">Others, as appropriate</FP>
                    </EXHIBIT>
                    <EXHIBIT>
                        <HD SOURCE="HED">Exhibit 3-5.—EA or EIS Incorporating Elements of a CCP Recommended Outline</HD>
                        <FP SOURCE="FP-2">Cover Sheet </FP>
                        <FP SOURCE="FP-2">Acknowledgments </FP>
                        <FP SOURCE="FP-2">Table of Contents </FP>
                        <FP SOURCE="FP-2">Summary </FP>
                        <FP SOURCE="FP-2">I. Introduction, Purpose of and Need for Action </FP>
                        <FP SOURCE="FP1-2">Purpose of and Need for Plan </FP>
                        <FP SOURCE="FP1-2">NWRS Mission, Goals, and Guiding Principles </FP>
                        <FP SOURCE="FP1-2">History of Refuge Establishment, Acquisition, and Management </FP>
                        <FP SOURCE="FP1-2">Legal and Policy Guidance </FP>
                        <FP SOURCE="FP1-2">Refuge Purpose(s) </FP>
                        <FP SOURCE="FP1-2">Refuge Vision Statement </FP>
                        <FP SOURCE="FP1-2">Refuge Management Direction: Goals </FP>
                        <FP SOURCE="FP1-2">Refuge Management Policies and Guidelines </FP>
                        <FP SOURCE="FP1-2">Step-Down Management Plans </FP>
                        <FP SOURCE="FP1-2">Description of Planning Process </FP>
                        <FP SOURCE="FP1-2">Planning Issues </FP>
                        <FP SOURCE="FP1-2">Plan Amendment and Revision </FP>
                        <FP SOURCE="FP-2">II. Alternatives, Including the Service's Proposed Action </FP>
                        <FP SOURCE="FP1-2">Description of Each Alternative (also include maps depicting strategies for each alternative) </FP>
                        <FP SOURCE="FP1-2">Refuge Management Direction: Objectives and Strategies </FP>
                        <FP>  Funding and Personnel </FP>
                        <FP>  Partnership Opportunities </FP>
                        <FP>  Monitoring and Evaluation </FP>
                        <FP SOURCE="FP1-2">Alternatives Considered, but Eliminated from Detailed Study </FP>
                        <FP SOURCE="FP1-2">Summary Comparison of Alternatives </FP>
                        <FP SOURCE="FP-2">III. Affected Environment </FP>
                        <FP SOURCE="FP1-2">Geographic/Ecosystem Setting </FP>
                        <FP SOURCE="FP1-2">Refuge Resources, Cultural Resources, and Public Uses </FP>
                        <FP SOURCE="FP-2">IV. Environmental Consequences </FP>
                        <FP SOURCE="FP1-2">Environmental Effects of Each Alternative (also include a matrix comparing issues, impacts, and benefits for each alternative) </FP>
                        <FP SOURCE="FP-2">V. List of Preparers </FP>
                        <FP SOURCE="FP-2">VI. Consultation and Coordination with Others </FP>
                        <FP SOURCE="FP1-2">Summary of Public Involvement/Comments </FP>
                        <FP SOURCE="FP1-2">Mailing List </FP>
                        <FP SOURCE="FP-2">Appendices </FP>
                        <FP SOURCE="FP1-2">Glossary </FP>
                        <FP SOURCE="FP1-2">Bibliography </FP>
                        <FP SOURCE="FP1-2">RONS List </FP>
                        <FP SOURCE="FP1-2">MMS List </FP>
                        <FP SOURCE="FP1-2">Compatibility Determinations </FP>
                        <FP SOURCE="FP1-2">Habitat/Land Protection Plan(s) </FP>
                        <FP SOURCE="FP1-2">Compliance Requirements </FP>
                        <FP SOURCE="FP1-2">Others, as appropriate</FP>
                    </EXHIBIT>
                    <HD SOURCE="HD1">Refuge Management—Part 602 National Wildlife Refuge System Planning </HD>
                    <HD SOURCE="HD1">Chapter 4 Step-Down Management Planning—602 FW 4 </HD>
                    <P>4.1 What is the purpose of this chapter? This chapter provides guidance on step-down management planning. </P>
                    <P>
                        4.2 What is our policy for step-down management planning? The U.S. Fish and Wildlife Service (Service or we) will prepare step-down management plans when required by policy or when they may be necessary to provide strategies and implementation schedules for meeting goals and objectives identified in Comprehensive Conservation Plans (CCPs). Step-down management plans should include public involvement and National 
                        <PRTPAGE P="33919"/>
                        Environmental Policy Act (NEPA) compliance documentation, as appropriate. Develop step-down management plans following the planning process guidance in 602 FW 1 and 602 FW 3. 
                    </P>
                    <P>4.3 What is the applicability of step-down management planning and its relationship to Comprehensive Conservation Plans? </P>
                    <P>A. Step-down management planning is the formulation of detailed plans for meeting goals and objectives identified in the CCP. </P>
                    <P>B. Step-down management plans describe the specific strategies and implementation schedules we are to follow, “stepping down” from general goals and objectives. The preparation of new step-down management plans or substantial changes to existing step-down management plans typically will require further compliance with NEPA and other policies, and an opportunity for public review. For public use plans or other step-down management plans dealing with proposed uses of the refuge, prepare and append compatibility determinations to the plans. </P>
                    <P>C. The CCP will identify which step-down management plans are necessary and provide a schedule for their completion. After completion of the CCP, modify existing step-down management plans as needed to accomplish stated objectives. See 602 FW 3. In the absence of an approved CCP, we will develop step-down management plans to describe goals, objectives, strategies, implementation schedules, and details necessary to implement a management program. </P>
                    <P>D. As an alternative to separate step-down management plans, we may address management programs in detail during preparation of the CCP. Determining which programs we can address in detail in the CCP depends on several factors, including the degree of public interest, the amount of available information, and the complexity of the issues. </P>
                    <P>4.4 How do we combine step-down management plans? Address management subjects individually or combined into a single, integrated step-down management plan. This decision rests with the Refuge Manager. Base the decision on strategies defined in the CCP, the relationship between program areas, and the complexity of the programs under consideration. Some program areas, such as fire management and habitat management, logically suggest an integrated approach. </P>
                    <P>4.5 What is the list of potential step-down management plans? Following is the current list of potential refuge step-down management plans. Consider all of these plans during the CCP process. The CCP will document which plans we require for the planning unit. </P>
                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s25,xs72">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">
                                Step-down 
                                <LI>management plans </LI>
                            </CHED>
                            <CHED H="1">
                                Service manual 
                                <LI>reference </LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Occupational Safety and Health</ENT>
                            <ENT>(Parts 240-249) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Safety Program </ENT>
                            <ENT>(240 FW 1-9) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Safety Operations </ENT>
                            <ENT>(241 FW 1-9) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Industrial Hygiene </ENT>
                            <ENT>(242 FW 1-13) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Hazardous Materials Operations </ENT>
                            <ENT>(242 FW 6) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Water Rights </ENT>
                            <ENT>(Part 403) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Policy, Objectives, and Responsibilities </ENT>
                            <ENT>(403 FW 1) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Law Enforcement </ENT>
                            <ENT>(Parts 440-459) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pollution Control </ENT>
                            <ENT>(Parts 560-569) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Policy and Responsibilities </ENT>
                            <ENT>(560 FW 1) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Pollution Prevention </ENT>
                            <ENT>(560 FW 2) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Compliance Requirements </ENT>
                            <ENT>(Part 561) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Clean Water Act </ENT>
                            <ENT>(561 FW 3) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">RCRA—Hazardous Waste </ENT>
                            <ENT>(561 FW 6) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pesticide Use and Disposal </ENT>
                            <ENT>(Part 562) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Pest Management </ENT>
                            <ENT>(562 FW 1) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">External Threats to FWS Facilities </ENT>
                            <ENT>(Part 563) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Air Quality Protection </ENT>
                            <ENT>(563 FW 2) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">National Wildlife Refuge System (NWRS) Uses </ENT>
                            <ENT>(Part 603) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">NWRS Uses (Appropriate Refuge Uses) </ENT>
                            <ENT>(603 FW 1) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Priority Wildlife-Dependent Recreation </ENT>
                            <ENT>(Part 605) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Hunting </ENT>
                            <ENT>(605 FW 2) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Fishing </ENT>
                            <ENT>(605 FW 3) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Wildlife Observation </ENT>
                            <ENT>(605 FW 4) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Wildlife Photography </ENT>
                            <ENT>(605 FW 5) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Environmental Education </ENT>
                            <ENT>(605 FW 6) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Interpretation </ENT>
                            <ENT>(605 FW 7) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Wilderness Management </ENT>
                            <ENT>(Part 610) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Special Area Management </ENT>
                            <ENT>(Part 611) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Research Natural Areas </ENT>
                            <ENT>(611 FW 1) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Public Use Natural Areas </ENT>
                            <ENT>(611 FW 2) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Wild and Scenic Rivers </ENT>
                            <ENT>(611 FW 3) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">National Trails </ENT>
                            <ENT>(611 FW 4) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="12">Man in the Biosphere Reserve </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="12">Western Hemisphere Shorebird Reserves </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="12">Ramsar Convention on Wetlands </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Minerals Management </ENT>
                            <ENT>(Part 612) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Minerals and Mining </ENT>
                            <ENT>(612 FW 1) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Oil and Gas </ENT>
                            <ENT>(612 FW 2) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cultural Resources Management </ENT>
                            <ENT>(Part 614) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Habitat Management Planning </ENT>
                            <ENT>(Part 620) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Fire Management </ENT>
                            <ENT>(Part 621) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Population Management </ENT>
                            <ENT>(Part 701) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Inventory and Monitoring </ENT>
                            <ENT>(701 FW 2) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Propagation and Stocking </ENT>
                            <ENT>(701 FW 3) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Marking and Banding </ENT>
                            <ENT>(701 FW 4) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Disease Prevention and Control </ENT>
                            <ENT>(701 FW 7) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="02">Trapping </ENT>
                            <ENT>(701 FW 11) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Fishery Resources Management </ENT>
                            <ENT>(Part 710) </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Exotic Species </ENT>
                            <ENT>(Part 751) </ENT>
                        </ROW>
                    </GPOTABLE>
                    <SIG>
                        <DATED>Dated: May 16, 2000.</DATED>
                        <NAME>Jamie Rappaport Clark,</NAME>
                        <TITLE>Director.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 00-12931 Filed 5-24-00; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 4310-55-P </BILCOD>
            </NOTICE>
        </NOTICES>
    </NEWPART>
    <VOL>65</VOL>
    <NO>102</NO>
    <DATE>Thursday, May 25, 2000</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="33921"/>
            <PARTNO>Part III</PARTNO>
            <AGENCY TYPE="P">Department of Transportation</AGENCY>
            <SUBAGY>Federal Highway Administration</SUBAGY>
            <SUBAGY>Federal Transit Administration</SUBAGY>
            <HRULE/>
            <CFR>23 CFR Parts 450 and 1410</CFR>
            <CFR>49 CFR Parts 613 and 621</CFR>
            <TITLE>Statewide Transportation Planning; Metropolitan Transportation Planning; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="33922"/>
                    <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                    <SUBAGY>Federal Highway Administration </SUBAGY>
                    <CFR>23 CFR Parts 450 and 1410 </CFR>
                    <SUBAGY>Federal Transit Administration </SUBAGY>
                    <CFR>23 CFR Part 1410</CFR>
                    <CFR>49 CFR Parts 613 and 621 </CFR>
                    <DEPDOC>[FHWA Docket No. FHWA-99-5933]</DEPDOC>
                    <RIN>FHWA RIN 2125-AE62; FTA RIN 2132-AA66</RIN>
                    <SUBJECT>Statewide Transportation Planning; Metropolitan Transportation Planning</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCIES:</HD>
                        <P>Federal Highway Administration (FHWA), Federal Transit Administration (FTA), DOT. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice of proposed rulemaking (NPRM); request for comments.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            The FHWA and the FTA are jointly issuing this document which proposes revisions to the regulations governing the development of transportation plans and programs for urbanized (metropolitan) areas and statewide transportation plans and programs. These revisions are a product of statutory changes made by the Transportation Equity Act for the 21st Century (TEA-21) enacted on June 9, 1998, and generally would revise existing regulatory language to make it consistent with current statutory requirements. In addition, the proposed regulatory language addresses the implementation of Presidential Executive Order 12898 regarding Environmental Justice. These changes are being proposed in concert with revisions to regulations regarding environmental impact and related procedures which are published separately in today's 
                            <E T="04">Federal Register</E>
                            . The two rules are linked in terms of their working relationship and the FHWA and the FTA are soliciting comments on each rule individually, as well as their intended functional and operational interrelationships. 
                        </P>
                    </SUM>
                    <DATES>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Comments must be received on or before August 23, 2000. For dates of public information meetings see “Supplementary Information.” </P>
                    </DATES>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>All signed, written comments must refer to the docket number appearing at the top of this document and must be submitted to the Docket Clerk, U.S. DOT Dockets, Room PL-401, 400 Seventh Street, SW., Washington, DC 20590-0001. All comments received will be available for examination at the above address between 9 a.m. and 5 p.m., e.t., Monday through Friday, except Federal holidays. Those desiring notification of receipt of comments must include a self-addressed, stamped envelope or postcard. For addresses of public information meetings see “Supplementary Information.” </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>For the FHWA: Mr. Sheldon M. Edner, Metropolitan Planning and Policies Team (HEPM), (202) 366-4066 (metropolitan planning), Mr. Dee Spann, Statewide Planning Team (HEPS), (202) 366-4086 (statewide planning), or Mr. Reid Alsop, Office of the Chief Counsel (HCC-31), (202) 366-1371. For the FTA: Mr. Charles Goodman, Metropolitan Planning Division (TPL-12) (metropolitan planning), (202) 366-1944, Mr. Paul Verchinski, Statewide Planning Division (TPL-11)(statewide planning), (202) 366-6385, or Mr. Scott Biehl, Office of the Chief Counsel (TCC-30), (202) 366-0952. Both agencies are located at 400 Seventh Street, SW., Washington, DC 20590. Office hours for the FHWA are from 7:45 a.m. to 4:15 p.m., e.t., and for the FTA are from 8:30 a.m. to 5 p.m., e.t., Monday through Friday, except Federal holidays. </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">Electronic Access </HD>
                    <P>
                        Internet users may access all comments received by the U.S. DOT Dockets, Room PL-401, by using the universal resource locator (URL): 
                        <E T="03">http://dms.dot.gov.</E>
                         It is available 24 hours each day, 365 days each year. Please follow the instructions online for more information and help. 
                    </P>
                    <P>
                        An electronic copy of this document may be downloaded using a computer, modem and suitable communications software from the Government Printing Office's Electronic Bulletin Board Service at (202)512-1661. Internet users may reach the Office of the Federal Register's home page at: 
                        <E T="03">http://www.nara.gov/fedreg</E>
                         and the Government Printing Office's web page at: 
                        <E T="03">http://www.access.gpo.gov/nara.</E>
                    </P>
                    <HD SOURCE="HD1">Public Information Meetings </HD>
                    <P>
                        We will hold a series of seven public briefings within the comment period for the NPRM. The purpose of these briefings is to explain the content of the NPRM and encourage public input to the final rulemaking. The meetings will address this NPRM, the companion NPRM on the environmental (National Environmental Policy Act of 1969 (NEPA)) process, and the NPRM on Intelligent Transportation Systems Architecture consistency. The meetings will be scheduled from approximately 8 a.m. to 5 p.m. at the locations listed below. Further information and any changes in addresses, dates and other logistical information will be made available after the publication of this NPRM through the FHWA and the FTA websites, and through other public announcement avenues and the newsletters and websites of major stakeholder groups. Individuals wishing information, but without access to these sources, may contact the individuals listed in the above caption 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        .
                    </P>
                    <P>The structure of the meetings will emphasize brief presentations by the DOT staff regarding the content of the NPRM. A period for clarifying questions will be provided. Under current statutory and regulatory provisions, the DOT staff will not be permitted to engage in a substantive dialog regarding what the content of the NPRMs and the final regulations should be. Attendees wishing to express ideas and thoughts regarding the final content of the rules should direct those comments to the docket. Briefing sites will include: Boston, MA, Auditorium, Volpe National Transportation Systems Center, 55 Broadway, June 9, 2000; Atlanta, GA, Westin Peachtree Plaza Hotel, 210 Peachtree Street, June 20, 2000; Washington, D.C., Marriott Metro Center, 775 12th Street, NW, June 23, 2000; Chicago, IL, Holiday Inn Mart Plaza, 350 North Orleans Street, June 27, 2000; Denver, CO, Marriott City Center, 1701 California Street, June 30 , 2000; Dallas, TX, Hyatt Regency Hotel Dallas, 300 Reunion Boulevard, July 11, 2000; and, San Francisco, CA, Radisson Miyako, 1625 Post Street, July 19, 2000.</P>
                    <P>
                        As part of the outreach process planned for these proposed rules, the FHWA/FTA will be conducting a national teleconference on June 15, 2000 from 1-4 p.m. eastern time, through the auspices of the Center for Transportation and the Environment at North Carolina State University. The teleconference will be accessible through numerous downlink locations nationwide and further information can be obtained from Ms. Katie McDermott at 
                        <E T="03">kpm@unity.ncsu.edu.</E>
                         The purpose of the teleconference is to describe the proposed new statewide and metropolitan planning, National Environmental Policy Act of 1969 (NEPA), Public Law 91-190, 83 Stat. 852, implementation, and Intelligent Transportation Systems (ITS) rules. 
                    </P>
                    <P>
                        An overview of each of the three notices of proposed rulemaking (NPRMs) will be presented and the audience (remote and local) will have opportunities to ask questions and seek clarification of FHWA/FTA proposals. By sponsoring this teleconference it is hoped that interest in the NPRMs is 
                        <PRTPAGE P="33923"/>
                        generated, that stakeholders will be well informed about FHWA/FTA proposals, and that interested parties will participate in the rulemaking process by submitting written suggestions, comments and concerns to the docket. 
                    </P>
                    <HD SOURCE="HD1">Background </HD>
                    <P>Sections 1203, 1204, and 1308 of the TEA-21, Public Law 105-178, 112 Stat. 107, amended 23 U.S.C. 134 and 135, which require a continuing, comprehensive, and coordinated transportation planning process in metropolitan areas and States. Similar changes were made by sections 3004, 3005, and 3006 of the TEA-21 to 49 U.S.C. 5303-5306 which address the metropolitan planning process in the context of the FTA's responsibilities. We are proposing revisions to our current metropolitan and statewide planning regulations and are inviting comments on the proposed revisions. </P>
                    <HD SOURCE="HD1">General Information Concerning Development of Regulation </HD>
                    <HD SOURCE="HD2">Approach to Structure of Proposed Regulation </HD>
                    <P>
                        Revisions to the current regulation at 23 CFR part 450 are being proposed to reflect the impacts of the TEA-21. We have adopted an approach to the proposed revisions that will rely heavily on guidance and good practice. The proposed regulatory language attempts to respond to legislative mandates and changes with minimal amplification where feasible. In some cases, other factors, 
                        <E T="03">e.g.,</E>
                         court cases, presidential directives, etc., have provided a stimulus for change and amplification. In these instances, the agencies have tried to keep regulatory language to a minimum except where clarification would assist appropriate agencies and groups in complying. 
                    </P>
                    <P>
                        In a separate document in today's 
                        <E T="04">Federal Register</E>
                        , we propose to remove 23 CFR part 771 and add parts 1420 and 1430 in its stead. This regulation implements the FTA and the FHWA processes for complying with the Council on Environmental Quality's (CEQ) regulations for implementing the NEPA, Public Law 91-190, 83 Stat. 852. Jointly administered by the FTA and the FHWA, part 771 was last revised in 1987. The passage of the TEA-21 and its predecessor, the Intermodal Surface Transportation Efficiency Act of 1991 (ISTEA), Public Law 102-240, 105 Stat. 1914, have contributed legislative impetus to a revision. To facilitate compliance with section 1308 of the TEA-21 dealing with major investment studies and section 1309 addressing environmental streamlining and twelve years of court rulings and experience, we propose to revise the regulations regarding environmental impact and related procedures in conjunction with those for metropolitan and statewide transportation planning. In general, the intent is to more effectively link the two regulations to facilitate integration of decisions, reduce paperwork and analytical activity where feasible, and to refine procedures and processes to achieve greater efficiency of decision making. In addition, we believe that an integrated approach to planning and project development (NEPA process plus additional project level actions needed to prepare for project implementation) will contribute to more effective and environmentally sound decisions regarding investment choices and trade-offs. 
                    </P>
                    <P>In preparing this proposed rule, we have attempted to maintain or reduce the level of data collection and analyses that is currently required. We solicit comment on the extent to which this strategy has been achieved. Comments suggesting that the strategy has not been successful should identify specific requirements and/or provisions that increase burdens and provide specific reasons for this increase. The degree or extent of the increase should be identified also. Suggestions to lessen burdens are welcome. </P>
                    <P>In the proposed rule, we revised the section headings to utilize more commonplace language and for clarity. The substance of the sections is modified in some cases as described below. The organization of each section and overall flow of organization remains predominantly unchanged, except as indicated in the section-by-section discussion. </P>
                    <P>In addition, we are proposing a new numbering scheme. Current part 450 would be redesignated as part 1410. </P>
                    <HD SOURCE="HD2">Input to Development of Proposed Regulation </HD>
                    <P>
                        As noted above, the TEA-21 was signed into law on June 9, 1998. Subsequently, the DOT initiated a series of national meetings to solicit input regarding possible approaches to implementing the new legislation. The results of the principal public sessions in this outreach effort are summarized in “Listening to America: TEA-21 Outreach Summary, 1998.” This document was published by the Office of the Secretary, U.S. Department of Transportation. It is currently available online through the following website: 
                        <E T="03">www.fhwa.dot.gov/tea21/listamer.htm.</E>
                         Additionally, on February 10, 1999, we issued a discussion paper (Federal Highway Administration and Federal Transit Administration, TEA-21 Planning and Environmental Provisions: Options for Discussion) to further solicit public comments regarding previously provided suggestions. This discussion paper was designed to reflect comments from stakeholder groups and encourage all interested parties to provide additional detailed comments on approaches to implementing the statutory provisions for the planning and environmental sections of the law. The Options Paper is available online at 
                        <E T="03">www.fhwa.dot.gov/environment/tea21imp.htm.</E>
                    </P>
                    <HD SOURCE="HD2">Overall Strategy for Regulatory Development </HD>
                    <P>Our strategy for regulatory development has three principal elements: (1) Outreach and listening to stakeholders, (2) developing improvements that will allow the FHWA, the FTA, the States and metropolitan areas to demonstrate measurable progress toward achieving congressional objectives, and (3) looking internally, with our Federal partner agencies, at how we collectively can improve coordination and performance. </P>
                    <P>As indicated above, the FHWA and the FTA, in concert with the Office of the Secretary and other modal administrations within the DOT, developed and implemented an extensive public outreach process on all elements of the TEA-21. The process began shortly after the legislation was enacted on June 9, 1998, and various types of outreach activities have been underway since that time. The initial six-month departmentwide outreach process included twelve regional forums and over 50 focus groups and workshops (63 FR 40330, July 28, 1998). The DOT heard from over 3,000 people, including members of Congress, Governors and Mayors, other elected officials, transportation practitioners at all levels, community activists and environmentalists, freight shippers and suppliers, and other interested individuals. The input received was valuable and has helped us shape our implementation strategy, guidance and regulations. Those comments will be placed in this docket as informational background. </P>
                    <P>
                        With respect to the planning and environmental provisions of the TEA-21, we learned a great deal through the twelve regional forums and focus group sessions and subsequently implemented a second, more focused phase of outreach which included issuing an Options Paper for discussion on the Planning and Environmental Streamlining Provisions of the TEA-21. The contents of the Options Paper 
                        <PRTPAGE P="33924"/>
                        reflected input received up to that time and built upon the existing statewide and metropolitan planning regulations and our implementing regulation for the NEPA. We released the Options Paper on February 10, 1999, and received comments through April 30, 1999. 
                    </P>
                    <P>More than 150 different sets of comments were received from State Departments of Transportation (State DOTs), Metropolitan Planning Organizations (MPOs), counties, regional planning commissions, other Federal agencies, transit agencies, bicycle advocacy groups, engineering organizations, consultants, historical commissions, environmental groups, and customers—the American public. These comments were all reviewed and taken into consideration in the development of this notice of proposed rulemaking. </P>
                    <P>Another element of outreach included meetings between the FHWA and the FTA and key stakeholder groups, other Federal agencies, and the regional and field staff within the FHWA and the FTA. These sessions also helped guide us in developing this notice of proposed rulemaking. Comments on this NPRM are welcomed and will be taken into account prior to the issuance of a final regulation on statewide and metropolitan planning under the TEA-21. </P>
                    <P>The Options Paper comments are contained in the docket and are summarized below. This general summary is structured around the issues as presented in the Options Paper and seeks to provide an overall perspective on the range of opinions submitted to the FHWA and the FTA. Details on specific comments and input can be obtained by reviewing the materials in the docket. </P>
                    <P>These proposed rules were developed by an interagency task force of planners and environmental specialists of the FHWA and the FTA, with input from other DOT modal agencies, the U.S. Environmental Protection Agency (EPA), other Federal agencies and the Office of the Secretary, U.S. DOT. The task force reviewed all input received from the outreach process and through other sources which communicate regularly with the DOT. In addition, comments were solicited from the field staff of the FHWA and the FTA. </P>
                    <HD SOURCE="HD1">Summary of Comments Received on Options Paper </HD>
                    <P>The following discussion summarizes the comments received on the Options Paper and the response we are generally taking in structuring this proposed rule. This summary focuses only on the comments directly related to planning. The comments regarding environmental provisions, generally, are treated in the preamble to the proposed revision to 23 CFR 771. Cross-cutting issues as discussed in the Options Paper appear in both preambles, as appropriate. Since many commenters included both planning and environmental topics in their correspondence, an exact count of planning versus environment issues in the 150 comments received is not easy or useful. The summary is not intended to be complete or comprehensive. Rather, it is provided to give the public a general sense of the issues addressed in the comments received. The views of individual commenters can be obtained by consulting the docket as indicated above. </P>
                    <HD SOURCE="HD2">Planning Factors </HD>
                    <P>We were offered a number of options on how to ensure that the seven new planning factors added by the TEA-21 are addressed in the metropolitan and statewide planning processes. One option is to include the TEA-21 statutory language in the planning regulation and provide maximum flexibility to States and MPOs to tailor approaches to local conditions. In addition, it was suggested that we amplify the basic statutory language in this regulation by providing information to States and MPOs, including best practices on approaches to considering the factors, and technical assistance on planning practices which integrate consideration of the seven factors. A third possibility was to develop specific criteria for the consideration of each of the seven factors, include the criteria in this regulation, and require that State DOTs and MPOs demonstrate compliance through the planning certification process. </P>
                    <P>The vast majority of comments received on the planning factors, including those from the Institute of Transportation Engineers (ITE), the National Association of County Engineers (NACE), the Association of Metropolitan Planning Organizations (AMPO), and the American Association of State Highway and Transportation Officials (AASHTO), supported a twofold approach: (1) To include the TEA-21 statutory language in the planning regulation without further regulatory requirements, and (2) to provide technical assistance and information on current practices to States and MPOs to aid them in consideration of the planning factors. An additional point raised, by State DOTs and MPOs in particular, was that guidance, if issued by the FHWA and the FTA, should not be construed as constituting new, binding requirements on State DOTs and MPOs. </P>
                    <HD SOURCE="HD2">Systems Operation and Management and Integration of Intelligent Transportation Systems Into the Planning Process </HD>
                    <P>The TEA-21 directs that operation and management of the transportation system requires greater attention during planning. Capital investment, especially for new capacity but also for system preservation, has dominated traditional transportation planning analyses and decisions. Continuing fiscal constraint, growing sensitivity to environmental impacts of infrastructure and the need for prudent management of infrastructure all lead to a heightened consideration of systems management and operational strategies as part of systems planning. The emergence of various Intelligent Transportation System (ITS) technologies as useful tools in the operation and management of the transportation system has also highlighted the need to focus increased attention in this area. An additional factor in treating ITS as part of system operation and management are the requirements of section 5206(e) of the TEA-21 regarding the consistency of federally funded ITS projects (funded with highway trust fund dollars) with the National ITS Architecture. </P>
                    <P>Many individual State DOTs, MPOs, and their national associations (AMPO and AASHTO) expressed the view that the planning factor requiring consideration of strategies to promote efficient system management and operation is sufficient to direct States and MPOs to consider operations and management issues as an integral part of their planning efforts. They indicated that the seven factors are all important and that to highlight consideration of any one factor above all others is inappropriate. Further, they felt that treating operations and management issues with any additional emphasis would be duplicative and is not necessary. </P>
                    <P>Only one commenter, the Maricopa Association of Governments, explicitly addressed the ITS matter. This agency suggested that we implement a requirement for federally funded ITS projects to be in accord with a regional ITS plan that is developed through a cooperative process. </P>
                    <HD SOURCE="HD2">Cooperative Development of Revenue Forecasts </HD>
                    <P>
                        The TEA-21 retained the basic requirement for financially constrained metropolitan plans and statewide and metropolitan transportation improvement programs (STIPs/TIPs). 
                        <PRTPAGE P="33925"/>
                        The TEA-21 clarifies the requirement for cooperative development by States, MPOs, and transit agencies of estimated future levels of funding from local, State, or Federal sources that may reasonably be expected to be available to metropolitan areas. 
                    </P>
                    <P>In general, many State DOTs and the AASHTO seek the greatest flexibility while MPOs and local governments seek provisions which would ensure that they get a “fair share” of Federal funding. The NACE, the AMPO, the National Association of Counties (NACO), and the Surface Transportation Policy Project (STPP) observe that a formal process should be required based upon consensus of the State, MPO, and transit agencies (where applicable) and that the process should be documented and implemented with an adequate phase-in period provided. The national associations and many of their constituent members commented that the process which has evolved over the past several years is inadequate for MPO and local agency needs, and that the Congress intended that this be rectified through the TEA-21 clarifying language. Both the NACE and the AMPO support the development of formal procedures, including decision rules for allocating funds and the development of internal and external dispute resolution and appeals processes to ensure that revenue forecasting is a truly collaborative process. The NACE also suggests that the FHWA and the FTA serve as “honest brokers” between State transportation agencies and MPOs when there is disagreement on revenue forecasts and allocation. </P>
                    <HD SOURCE="HD2">Illustrative Projects </HD>
                    <P>Organizations and agencies, including the Indian Nation Council of Governments, the Public Policy Institute of California, the AMPO, and the EPA raised concerns about the need for coordination between States and MPOs in cases where illustrative projects are proposed to be added to metropolitan area plans or TIPs. Specifically, it was suggested that in metropolitan areas, MPOs should have explicit approval authority for the inclusion of such projects in transportation plans and TIPs and for the implementation of illustrative projects. </P>
                    <P>On the whole, respondents supported a position that illustrative projects are important to them, but that such projects should not be included in the transportation plan or TIP conformity analysis until formally amended into the Plan/TIP. In addition, there was considerable support for an approach which requires MPO concurrence on projects that are proposed to be advanced to an MPO plan and/or TIP. The Texas Natural Resources Conservation Commission and the Colorado DOT expressed concern that illustrative projects would be allowed to circumvent the planning process. State DOTs, in particular, advocated allowing illustrative projects to be included in the conformity analyses for plans and TIPs in order that it may be demonstrated that they will not jeopardize the conformity of plans and TIPs. </P>
                    <P>The AASHTO and several State DOTs felt that we are being too restrictive in our definition of a financially constrained plan. In short, these commenters request more flexibility. Some State DOTs, including the Texas, New Jersey, Missouri, and Virginia DOTs point out that they feel it entirely appropriate to conduct NEPA related project development activities and studies on such projects, outside of the fiscal constraint requirements. They endorse amending such projects into the plan and TIP when appropriate, and at that time trigger fiscal constraint and conformity requirements. </P>
                    <HD SOURCE="HD2">
                        <E T="03">Annual Listing of Projects</E>
                    </HD>
                    <P>During the outreach process, the Missouri DOT, and the Denver Regional Council of Governments (DRCOG) remarked that MPOs do not have the authority to obligate Federal funds and that States and transit agencies are the authorized recipients of Federal funds. Therefore, they suggest, the States, transit agencies, and/or the Federal government need to provide the necessary information to the MPOs in order that they may comply with the TEA-21 requirement for an annual listing of projects. </P>
                    <P>The AMPO recommended that we establish and maintain a project monitoring system for the purpose of tracking Federal highway and transit obligations and that we make this system accessible to the MPOs in order that it might provide the basis for the annual listing of projects. These stakeholders are concerned that there be clear direction to the implementing agencies (States and transit agencies) for meeting this TEA-21 requirement. Further, they are concerned that MPOs, without the assistance of implementing agencies, do not have the necessary information to comply with this requirement. The American Road and Transportation Builders Association (ARTBA) felt the annual list should include all obligated funds, rather than just projects with Federal funding. </P>
                    <P>The U.S. EPA believes a nationally uniform format for these lists should be developed and that such lists should be sent to State and Federal environmental agencies, the interagency consultation groups under the transportation conformity regulation, and others. </P>
                    <P>The Transportation Equity Network and the Center for Community Change advocate the preparation of this list on a zip-code basis and cited a U.S. Department of Housing and Urban Development (HUD) model. They suggest a zip-code based list is easily understandable by members of the public. </P>
                    <P>Many of those who commented supported an approach which would provide easy public access to information, through a wide means of communication, as noted above. Many stakeholders, including the AMPO and the Kentucky Transportation Cabinet, opposed a process which would require the development of such a list through the public involvement process of the MPO. However, the American Planning Association, the Surface Transportation Policy Project, the Urban Habitat Program, the Tri-State Transportation Campaign, and the National Association to Defend NEPA, among others, supported the dissemination of the list, once developed, through easily accessed public distribution channels. </P>
                    <HD SOURCE="HD2">
                        <E T="03">Coordination With Local Elected Officials in Non-Metropolitan Areas</E>
                    </HD>
                    <P>The NACO, the National Association of Development Organizations, the STPP, the York County Planning Commission (Pennsylvania), the Minnesota DOT, and the Georgia DOT all suggested that where regional planning organizations or councils of government exist, they be considered as an entity that States could work with to facilitate the engagement of elected officials. The NACE, U.S. House of Representative Bob Ney and others supported a two-phased approach: the FHWA and the FTA would provide the flexibility to States and local elected officials to develop a process, and then be provided ample time to document and formalize the process pursuant to the TEA-21. These commenters felt that the flexibility to tailor approaches is needed, but that documentation of the agreed upon approach is also needed to ensure it is implemented on a continuing basis. </P>
                    <P>
                        The National Association of Towns and Townships suggested more formal processes, like those that are in place in some States, where local governments form development districts or regional development commissions, modeled to some extent after the MPO process. The Land-of-the-Sky Regional Council indicated that this approach is necessary to ensure rural officials have 
                        <PRTPAGE P="33926"/>
                        a voice in decision making and that rural area needs are addressed. In addition, they suggest that such an approach ensures the coordination of a broad array of objectives relating to economic development, land use, and transportation. State DOTs in Idaho, Montana, North Dakota, South Dakota, Wyoming, New York, Virginia and Oklahoma suggested that existing local official consultation arrangements are adequate and that compliance with the TEA-21 provision merely requires documentation of existing arrangements. 
                    </P>
                    <HD SOURCE="HD2">
                        <E T="03">20-Year Forecast Period in Transportation Plans</E>
                    </HD>
                    <P>Commenters, including AASHTO, ITE, Virginia DOT, Texas DOT, Washington DOT, and Kansas DOT supported a clarification which reiterates that transportation plans must be for a 20-year minimum forecast period at the time of plan adoption. Further, the Capital District Transportation Authority, the Regional Transit Agency in Denver, the Central Puget Sound Regional Transit Agency, the Texas Natural Resources Conservation Commission, the Lackawanna County Regional Planning Commission and others felt that so long as metropolitan TIP updates and amendments (required every two years) are consistent with the metropolitan plan, then, a metropolitan plan update with a new 20-year forecast period should not be required. The STIP amendments and updates (also required every two years) would be governed by the State plan and its unique update schedule. </P>
                    <HD SOURCE="HD2">
                        <E T="03">Transportation Conformity Related Issues</E>
                    </HD>
                    <P>There are several issues related to the EPA conformity regulation in 40 CFR parts 51 and 93 that could be addressed in the revised planning regulations. These issues relate to clarifying requirements and definitions, and could lead to better integration of transportation and air quality planning, a principal objective of the EPA's regulation. These include: </P>
                    <P>1. Consistency between metropolitan plan update cycle and the point at which a conformity determination is required. </P>
                    <P>During the outreach process, and in many of the comments to the Options Paper, stakeholders indicated that they interpret the three-year clock for a plan (and required conformity analysis) as starting from the date the MPO approves the metropolitan plan. Agencies, including the Utah DOT, the New York DOT, and others commented that this provides certainty about the exact time frame in which the plan needs to be updated and that this is the preferred approach to clarifying this issue. </P>
                    <P>In nonattainment and maintenance areas, however, this approach is complicated by required MPO and Federal conformity findings. The AASHTO, and the Virginia DOT supported making the effective date of the plan the date of the Federal conformity finding. The AMPO indicated that it has no certainty as to when the FHWA and the FTA will approve a conformity determination on a metropolitan plan and thus, tying the effective date of the plan to an approval over which they feel they have no control does not, in its view, facilitate the planning process. </P>
                    <P>2. Transportation Control Measures (TCMs) in State Implementation Plans (SIPs). </P>
                    <P>Stakeholders, including the Bicycle Federation of America, the AASHTO, and the AMPO, observed that TCMs, for which Federal funding or approvals are required, must meet the TEA-21 planning requirements (i.e., come from a conforming and financially constrained transportation plan and TIP) and that attempting to circumvent this process, in order to place these measures in SIPs, undermines the transportation planning process. </P>
                    <P>3. Definitions: TIP Amendments, Conformity Lapse, TIP Extensions. </P>
                    <P>The FHWA and the FTA have considered clarifying ambiguous terms used in the ISTEA and the EPA's conformity regulation 40 CFR parts 51 and 93. The New Jersey DOT, the AMPO, the Utah DOT, the Texas Natural Resources Conservation Commission, the Wisconsin DOT, and the DRCOG have endorsed the concept of clarification of definitions and terms and want an opportunity to comment on proposed definitions. </P>
                    <HD SOURCE="HD1">Cross Cutting Issues </HD>
                    <P>There are a number of options for implementing the cross-cutting planning and environmental provisions of the TEA-21. Both regulatory and non-regulatory approaches were suggested to us. The concepts discussed in the proposed rule have been coordinated with other administrations within the DOT and with other Federal agencies. </P>
                    <HD SOURCE="HD2">A. Public Involvement </HD>
                    <P>Some State and local agencies have expressed interest in ways to integrate the public involvement process related to plan and TIP development with public involvement process related to the project development. Several stakeholder groups have noted the difficulties in getting public input on long-range plans and TIPs and the tendency for the public to be more inclined to participate in project-specific opportunities for input. They indicated that this tends to frustrate the public involvement efforts of State and MPO planners to obtain input on long-range transportation plans. During the public outreach process, we sought input in this area, as well as examples of successful techniques and approaches to engage the public on both project-level proposals and long-range plans and TIPs. </P>
                    <P>Comments from stakeholders were varied. However, there were a substantial number of comments that preferred the following two-fold approach: retaining the public involvement approach included in the planning regulation and modifying the NEPA regulation public involvement requirements to make our procedures the same (based on the FHWA, rather than the FTA, approach). This, they suggest, would allow States and MPOs to design processes that work best given local conditions and needs, yet would simplify the NEPA public involvement process by consolidating the FHWA and the FTA processes into one. </P>
                    <P>In arguments supporting this option, a considerable number of commenters, including State DOTs in Montana, Washington, New Jersey, Idaho, Wyoming, North Dakota, South Dakota, and the AASHTO, pointed out distinctions between the type of public involvement that must occur in the planning process and that which is sought in the NEPA process. They point out that these two processes, tailored according to each need, can serve two different purposes and can work without conflict. </P>
                    <P>
                        There were a number of comments on whether freight interests and representatives of transit users should be represented with voting membership on MPO boards. These commenters, including the NACE, all opposed this idea and observed that putting persons representing particular interests on voting boards with elected officials would dilute the representation of duly elected officials. Yet, the Bicycle Federation of America supported putting representatives of bicyclists and pedestrians on voting boards of MPOs to ensure that they have an opportunity to comment on transportation plans and programs. The Texas Natural Resources Conservation Commission, the Orange County Transportation Authority, the Arkansas DOT, and the Minnesota DOT supported a consistent approach to public involvement for both planning activities and the NEPA project 
                        <PRTPAGE P="33927"/>
                        development activities and suggested basing this approach on the current FHWA NEPA regulation (23 CFR part 771). The EPA suggested that the DOT needs to assist community leaders, MPOs, and the public in establishing performance goals and local accountability for public participation. 
                    </P>
                    <HD SOURCE="HD2">B. Environmental Justice and Equity </HD>
                    <P>There were a considerable number of commenters, including the AASHTO and many State DOTs, that opposed any suggestion that equity in the distribution of resources should be a factor used to assess whether environmental justice issues are being adequately addressed. These comments ranged from claims that such language, if included in regulation, would contradict the hard-fought TEA-21 provisions on the allocation of transportation funds to claims that such language would result in preempting States and MPOs from selecting the transportation projects and programs in their respective jurisdictions. Deep concern about this option and opposition to this approach was widespread and shared by MPOs and transit agencies who feel that geographic sub-allocation of funding based on demographics is short-sighted, and an inappropriate way to ensure the principles of environmental justice are honored. </P>
                    <P>Many commenters indicated that they believe the Executive Order 12898, Title VI of the Civil Rights Act of 1964, Public Law 88-352, 78 Stat. 241, as amended, and current NEPA requirements are sufficient to ensure that environmental justice concerns are addressed. The New Jersey DOT noted that benefits that accrue to users of investments should be a consideration in planning, and that this could possibly be measured in terms of mobility. </P>
                    <P>The Fulton County and Georgia Department of Environment and Community Development focused on the composition of appointed officials on regional authorities. This agency suggested that such authorities or decision making bodies should reflect the demographics of the region. This agency also suggested that all elements of the population affected by a particular decision should be sought out for their input. In addition, this commenter suggested that controversial project decisions should be analyzed to ensure that they conform to the Environmental Justice Presidential Executive Order. Finally, the commenter suggested that all decisions should be analyzed to ensure that no particular geographic sub-area is being over-burdened with adverse conditions resulting from transportation investments. </P>
                    <P>The U.S. Forest Service pointed out that lumping environmental justice and equity together is, in its view, a mistake. It suggested that the best option for public involvement, especially on issues concerning environmental justice, would be those procedures that incorporate collaboration processes early and often in the process. </P>
                    <P>One agency made the case that we should consider requiring environmental justice analyses of plans, programs and processes, and of major projects. The commenting agency suggested that we could adopt a set of requirements for recipients of our funding. Requirements would include: (1) Community group or nonprofit organization inclusion as equal and full partners in proposed projects; (2) applications for funding include community input in project development; and (3) external reviewers would make project selection decisions. </P>
                    <HD SOURCE="HD2">C. Elimination of Major Investment Study as Separate Requirement </HD>
                    <P>Section 1308 of the TEA-21 eliminates the major investment study (MIS), described in 23 CFR 450.318, as a separate requirement and calls for integration of the MIS, as appropriate, into the planning and NEPA analyses required under 23 CFR parts 450 and 771. Proponents supporting this legislative action cited instances where major investment studies were said to duplicate NEPA requirements, were time consuming and costly, and importantly, that results were not usefully integrated into the project development activities under NEPA. </P>
                    <P>The Options Paper articulated four general concepts (distilled from earlier stakeholder comments) focusing on strengthening the linkage between systems planning and project development. We thought this would facilitate broader consideration of transportation system development although, in some cases, commenters had other views as discussed below. </P>
                    <P>In all of the options, the intent was to faithfully implement the TEA-21 provision that exempts plans and programs from consideration under NEPA. The MPOs would not be required to conduct NEPA analyses on plans. However, they could more effectively utilize the analyses conducted during planning activities to facilitate compliance with NEPA requirements at a project level. If an MPO, as part of its planning process, chose to conduct a NEPA analysis on a plan, it would be a permissible, voluntary decision. In addition to the four options presented for input, the Options Paper included a number of questions to solicit a better understanding of stakeholders' needs and concerns. </P>
                    <P>There were a wide range of comments on the elimination of the MIS and on the options presented. The AASHTO felt that we should restrict regulatory language and allow States and MPOs to integrate the principles of the MIS, as appropriate, into planning and programming activities at their discretion. The AMPO suggested that we should allow States the flexibility to do the NEPA analysis in the planning process, as an option, but not as a requirement. In fact, many stakeholders were firmly opposed to any regulatory language integrating NEPA requirements into the planning process. </P>
                    <P>Most of the commenters supported better linkages between planning and project development and many commenters, including the Minnesota DOT, supported the development of purpose and need during planning studies and sub-regional analysis, but only with the proviso that resource agencies and others allow the use of this information in the NEPA process. On the other hand, the Virginia DOT, for example, was opposed to developing project purpose and need during planning if there is a lack of participation of resource agencies and other parties to the NEPA process who could then require that analysis be redone or revisited during the formal NEPA process. There was near unanimous support for streamlining through reducing duplicative requirements and practices, such as, revisiting issues during project development that were, in commenters views, fully explored during planning. </P>
                    <P>Many commenters supported options that offer the most flexibility to States and MPOs. The Florida DOT suggested blending the two most flexible options and developing regulatory language that ensures the principles of MIS not already addressed by other Federal regulations and statutes are included in the metropolitan planning and programming requirements. They also suggested that the planning regulation should include requirements for proactive agency coordination and public involvement, collaborative and multi-modal planning analysis of alternatives, and financial capacity analysis of alternatives. The Florida DOT also felt that the States should take the lead on these processes. </P>
                    <P>
                        The City of Irvine, Texas, suggested that the MIS process served as a good check on the system planning process and was a good way to build consensus and gain public input. Its traffic and 
                        <PRTPAGE P="33928"/>
                        transportation director suggested that expanding the purpose and need statement would help narrow down alternatives prior to the NEPA process. The same individual also suggested looking at the entire process to identify what environmental information could be both practical and useful at each level of analysis. 
                    </P>
                    <P>Additionally, and echoing earlier comments, stakeholders felt that the key to success in whatever approach is taken or required in regulation, is that Federal agencies participate early in the process and that they stay involved throughout the development of, and elimination of, alternatives. Consistent with this suggestion, the EPA commented that the only way they would give standing to previously conducted planning analyses during the NEPA project development stage is if there had been full opportunity for consultation in the metropolitan planning process, and if the resource agencies had “confidence that those plans were developed with environmentally desirable alternatives being considered.” </P>
                    <HD SOURCE="HD2">D. Cumulative and Secondary Impacts </HD>
                    <P>The Options Paper presented two scenarios which would help promote the consideration and evaluation of the cumulative and indirect effects of projects at a regional or large sub-regional scale, rather than on a project-by-project basis. In metropolitan areas, the former MIS requirement provided an opportunity for appropriate consideration of such effects across a sub-regional area where major, multiple transportation actions might be needed. With the elimination of the separate MIS requirement, the most logical venue for the consideration of such effects may be in the systems planning processes that support the development of metropolitan or statewide transportation plans. </P>
                    <P>One approach to implementing cumulative and secondary impact consideration would require an appropriate evaluation of these effects in a regional or sub-regional analysis, thus obviating the need for repetitious, project-by-project review. Such an approach might also provide an opportunity for more effective and efficient mitigation of cumulative impacts and the enhancement of adversely affected resources. Another possibility is to rely on a systems planning analysis of cumulative and indirect effects. In the absence of a robust planning-level review of these impacts, the project-by-project review as part of each NEPA evaluation would be required. </P>
                    <P>Some commenters, including the AASHTO and the Bicycle Federation of America, interpreted the first option as a requirement for enhancement projects whenever there are cumulative or indirect effects identified. A large number of commenters opposed this approach, but for two different reasons. The Bicycle Federation of America felt that using transportation enhancement funding to counterbalance the adverse impacts of projects is unacceptable and that such mitigation should be part of the project cost and implementation from the outset. Others, including State DOTs in Utah, New York, and Virginia, believed that a regional or subregional analysis is unrealistic, excessively costly, and of no value unless the study results were accepted by State and Federal environment and resource agencies. </P>
                    <P>
                        The Oregon DOT observed that the appropriate level to consider cumulative and indirect impacts is at a regional or sub-regional planning level, but not as an analysis 
                        <E T="03">per se;</E>
                         rather, as a plan to preserve and enhance habitat and preserve resources for future generations. A few examples of plans that accomplish this objective were provided. The New Jersey DOT, Texas DOT, and the American Road and Transportation Builders Association stated that the “science” for evaluating the impacts is not available and that we should provide funding, education, and tools to assist MPOs and States to develop the appropriate analysis tools. 
                    </P>
                    <P>Finally, the Lubbock and Byron College Station MPOs (both from Texas) indicated that cumulative and indirect impacts are, and should be, adequately addressed in consideration of the planning factors and that additional regulatory requirements are unnecessary and redundant. </P>
                    <HD SOURCE="HD2">Distribution Table </HD>
                    <P>For ease of reference, a distribution table is provided for the current sections and the proposed sections as follows: </P>
                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s150,r150">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">Old section </CHED>
                            <CHED H="1">New section </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">450.100. </ENT>
                            <ENT>1410.100.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.102. </ENT>
                            <ENT>1410.102.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.104. </ENT>
                            <ENT>1410.104.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Definitions </ENT>
                            <ENT O="oi2">Definitions. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Conformity lapse. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Conformity rule. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Management System </ENT>
                            <ENT O="oi4">Congestion management system [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Consultation </ENT>
                            <ENT O="oi4">Consultation [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Cooperation </ENT>
                            <ENT O="oi4">Cooperation [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Coordination </ENT>
                            <ENT O="oi4">Coordination [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Design concept. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Design scope. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Federally funded non-emergency transportation services. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Financial estimate. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Freight shipper. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Illustrative project. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Indian tribal government. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Interim Plan. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Interim Transportation Improvement Program. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">ITS integration strategy. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Maintenance area </ENT>
                            <ENT O="oi4">Maintenance area [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Management and operation. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Metropolitan planning area </ENT>
                            <ENT O="oi4">Metropolitan planning area. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Metropolitan planning organization </ENT>
                            <ENT O="oi4">Metropolitan planning organization. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Metropolitan transportation plan </ENT>
                            <ENT O="oi4">Metropolitan transportation plan. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Nonattainment area </ENT>
                            <ENT O="oi4">Nonattainment area. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Non-metropolitan local official. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Plan update. </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="33929"/>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Provider of freight transportation services. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Purpose and need. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Regionally significant project </ENT>
                            <ENT O="oi4">Regionally significant project [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">State </ENT>
                            <ENT O="oi4">State. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">State implementation plan </ENT>
                            <ENT O="oi4">State implementation plan. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Statewide transportation improvement program (STIP) </ENT>
                            <ENT O="oi4">Statewide transportation improvement program (STIP). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Statewide transportation improvement program (STIP) extension. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Statewide transportation plan </ENT>
                            <ENT O="oi4">Statewide transportation plan. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">TIP update. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Transportation control measures. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Transportation improvement program </ENT>
                            <ENT O="oi4">Transportation improvement program [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Transportation management area </ENT>
                            <ENT O="oi4">Transportation management area. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">Transportation plan update </ENT>
                            <ENT O="oi4">Transportation plan update. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Twenty year planning horizon. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">Urbanized area. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">None </ENT>
                            <ENT O="oi4">User of public transit. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.200 </ENT>
                            <ENT>1410.200. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.202 </ENT>
                            <ENT>1410.202. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.204 </ENT>
                            <ENT>1410.204. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.206(a)(1) </ENT>
                            <ENT>Removed. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.206(a)(2) through (a)(5) </ENT>
                            <ENT>1410.206(a)(1) through (a)(4). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.206(a)(5)[Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.206(b) </ENT>
                            <ENT>Removed </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.208(a) </ENT>
                            <ENT>1410.208(a) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.208(b) </ENT>
                            <ENT>1410.208(b) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.210(a) </ENT>
                            <ENT>1410.210(a) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.210(b) </ENT>
                            <ENT>1410.210(e) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.212(a) through (f) </ENT>
                            <ENT>1410.212(b) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.212(c) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.212(g) </ENT>
                            <ENT>1410.212(e). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.214 </ENT>
                            <ENT>1410.214 [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.216(a) introductory paragraph </ENT>
                            <ENT>1410.216(a). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.216(a)(1) through (a)(7) </ENT>
                            <ENT>1410.216(c)(1) through (c)(7). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.216(c)(8). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.216(a)(8) </ENT>
                            <ENT>1410.216(c)(9). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.216(a)(9) </ENT>
                            <ENT>1410.216(c)(10). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.216(b) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.216(b) </ENT>
                            <ENT>1410.216(d). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.216(c) </ENT>
                            <ENT>1410.216(e) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.216(f) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.216(d) </ENT>
                            <ENT>1410.216(g) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.218 [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.218 </ENT>
                            <ENT>1410.220 [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.220(a) introductory paragraph </ENT>
                            <ENT>1410.222(a) introductory paragraph. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.220(a)(1) </ENT>
                            <ENT>1410.222(a)(1) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.220(a)(2) </ENT>
                            <ENT>1410.222(a)(2) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.222(a)(3) through (a)(6) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.220(a)(3) </ENT>
                            <ENT>Removed. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.220(a)(4) </ENT>
                            <ENT>1410.222(a)(7). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.220(a)(5) </ENT>
                            <ENT>1410.222(a)(8). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.220(a)(6) </ENT>
                            <ENT>1410.222(a)(9). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410(a)(10) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.220(b) and (c) </ENT>
                            <ENT>1410.222(b) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.220(d) </ENT>
                            <ENT>1410.222(c) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.220(e) </ENT>
                            <ENT>1410.222(b)(3) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.220(f) </ENT>
                            <ENT>1410.222(d). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.220(g) </ENT>
                            <ENT>1410.222(e). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.222(a) through (d) </ENT>
                            <ENT>1410.224(a) through (d) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.224(e) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.224 </ENT>
                            <ENT>Removed. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.226 [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.300 </ENT>
                            <ENT>1410.300 [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.302 </ENT>
                            <ENT>1410.302 [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.304 </ENT>
                            <ENT>1410.304 [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.306(a) </ENT>
                            <ENT>1410.306(a) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.306(b) and (c) </ENT>
                            <ENT>1410.306(b) and (c) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.306(d) and (g) </ENT>
                            <ENT>1410.306(f) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.306(e) </ENT>
                            <ENT>1410.306(d). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.306(f) </ENT>
                            <ENT>1410.306(e). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.306(h) through (k) </ENT>
                            <ENT>1410.306(g) through (j) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.308(a) through (d) </ENT>
                            <ENT>1410.308(a) through (d) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.308(e) </ENT>
                            <ENT>1410.308(e) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.310(a) </ENT>
                            <ENT>1410.310(a) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="33930"/>
                            <ENT I="01">450.310(b) </ENT>
                            <ENT>Removed. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.310(b) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.310(c) </ENT>
                            <ENT>1410.310(c) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.310(d) </ENT>
                            <ENT>1410.310(h) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.310(e) </ENT>
                            <ENT>1410.310(d) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.310(f) </ENT>
                            <ENT>1410.310(e) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.310(g) </ENT>
                            <ENT>1410.310(f). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.310(g) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.310(h) </ENT>
                            <ENT>1410.310(i). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.312(a) </ENT>
                            <ENT>1410.312(a) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.312(b) </ENT>
                            <ENT>1410.312(b). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.312(c) </ENT>
                            <ENT>1410.312(c) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.312(d) </ENT>
                            <ENT>1410.312(d). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.312(e) through (i) </ENT>
                            <ENT>1410.312(e) through (i) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.312(j) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.314(a), (b) and (d) </ENT>
                            <ENT>1410.314(a), (b) and (c) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.314(c) </ENT>
                            <ENT>Removed </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.316(a) </ENT>
                            <ENT>1410.316(a) [Revised].</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.316(b)(1) </ENT>
                            <ENT>1410.316(b) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.316(b)(2) </ENT>
                            <ENT>1410.316(c) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.316(b)(3) </ENT>
                            <ENT>1410.316(d) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.316(b)(4) </ENT>
                            <ENT>1410.316(e) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.316(b)(5) </ENT>
                            <ENT>1410.316(f) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.316(g) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.316(c) </ENT>
                            <ENT>1410.316(h) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.316(d) </ENT>
                            <ENT>1410.316(i). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.316(j) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.318 </ENT>
                            <ENT>1410.318 [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.320(a) </ENT>
                            <ENT>Removed.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.320(b), (c) and (d) </ENT>
                            <ENT>1410.320(a), (b) and (c) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.322(a) </ENT>
                            <ENT>1410.322(a) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.322(b)(1) through (b)(7) </ENT>
                            <ENT>1410.322(b)(1) through (b)(7) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.322(b)(8) </ENT>
                            <ENT>Removed.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.322(b)(9) through (b)(11) </ENT>
                            <ENT>1410.322(b)(8) through (b)(10) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.322(b)(11) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.322(c) and (d) </ENT>
                            <ENT>1410.322(c) and (d) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.322(e) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.322(e) </ENT>
                            <ENT>1410.322(f). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.322(g) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.324(a) through (e) </ENT>
                            <ENT>1410.324(a) through (e) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.324(f)(1) through (f)(3) </ENT>
                            <ENT>1410.324(f)(1) through (f)(3) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.324(f)(4) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.324(f)(4) and (f)(5) </ENT>
                            <ENT>1410.324(f)(5) and (f)(6) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.324(g) through (o) </ENT>
                            <ENT>1410.324(g) through (o) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.324(p) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.326 </ENT>
                            <ENT>1410.326 [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.328 </ENT>
                            <ENT>1410.328 [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.330(a) and (b) </ENT>
                            <ENT>1410.330(a) and (b) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.330(c) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.332(a) </ENT>
                            <ENT>1410.332(b) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.332(b) </ENT>
                            <ENT>1410.332(c) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.332(c) </ENT>
                            <ENT>1410.332(a) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.332(d) and (e) </ENT>
                            <ENT>1410.332(d) and (e). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.334(a)(1) through (a)(5) </ENT>
                            <ENT>1410.334(a)(1) through (a)(5) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.334(a)(6) through (a)(8) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.334(b) through (f) </ENT>
                            <ENT>1410.334(b) through (f) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.334(g) </ENT>
                            <ENT>Removed. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1410.334(g) [Added]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.334(h) </ENT>
                            <ENT>1410.334(h) [Revised]. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">450.336 </ENT>
                            <ENT>Removed. </ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD1">Section-by-Section Discussion </HD>
                    <HD SOURCE="HD2">
                        <E T="03">Section 1410.100 Purpose</E>
                    </HD>
                    <P>Current § 450.100 would be redesignated as § 1410.100 and a technical correction would be made for a legislative citation. </P>
                    <HD SOURCE="HD2">
                        <E T="03">Section 1410.102 Applicability</E>
                    </HD>
                    <P>Current § 450.102 would be redesignated as § 1410.102. The text of this section is unchanged. </P>
                    <HD SOURCE="HD2">Section 1410.104 Definitions </HD>
                    <P>Current § 450.104 would be redesignated as § 1410.104. The definition of “conformity lapse” and “transportation control measure” would be added and would have the meaning given it in the EPA conformity regulation provided at 40 CFR 93.101, as follows: </P>
                    <P>
                        The term “lapse” means that the conformity determination for a transportation plan or TIP has expired, and thus there is no currently conforming transportation plan and TIP. 
                        <PRTPAGE P="33931"/>
                    </P>
                    <P>The term “congestion management system” would replace the previous definition of “management system” and would have the meaning given in the management system rule (23 CFR part 500). </P>
                    <P>The term “consultation” would have minor wording changes, but no substantive changes. </P>
                    <P>The word “programming” would be dropped from the definition of “coordination” to reflect the fact that programming is a subset of the planning process. The project development processes reference would be added to reflect the provisions of proposed § 1410.318. </P>
                    <P>Definitions are proposed for “design concept,” “design scope,” “federally funded non-emergency transportation services,” “financial estimate,” and “freight shipper” for clarification of legislative terminology. </P>
                    <P>The term “Governor” remains the same. </P>
                    <P>The terms “illustrative project” and “ITS integration strategy” would be added to reflect new legislative provisions. The term “Indian Tribal Government” is added for clarification. </P>
                    <P>The terms “Interim Plan” and “Interim Transportation Improvement Program” are added to clarify the basis for advancing exempt and existing and new TCM projects during a conformity lapse. Interim plans and TIPs must be developed in a manner consistent with 23 U.S.C. 134. They must be based on previous planning assumptions and goals; appropriately adjusted for currently available projections for population growth, economic activity and other relevant data. The public must be involved consistent with the regular transportation plan and program development processes. Financial planning and constraint, and, as appropriate, congestion management systems requirements must be satisfied, and interim TIPs must be approved by the MPO and the Governor.” </P>
                    <P>The term “maintenance area” would be revised to reflect the EPA definition used in the conformity regulation at 40 CFR parts 51 and 93. </P>
                    <P>A definition is proposed for “management and operation” to reflect the new legislative policy direction from the TEA-21. </P>
                    <P>The terms “metropolitan planning area,” “metropolitan planning organization,” “metropolitan transportation plan,” and “nonattainment area” would remain unchanged, except for legislative references. </P>
                    <P>A definition of “non-metropolitan local official” would be added to reflect the provisions of the TEA-21 regarding consultation between the State and these officials. </P>
                    <P>The terms “plan update,” “provider of freight services,” and “purpose and need” would be added to provide clarification of terminology. </P>
                    <P>The definition of “regionally significant” reflects the US EPA conformity rule (40 CFR parts 51 and 93). </P>
                    <P>The terms “State,” “State implementation plan,” “statewide transportation plan,” and “statewide transportation improvement program” would be unchanged. </P>
                    <P>A definition for “statewide transportation improvement program extension” would be added for clarification. </P>
                    <P>The term “transportation improvement program” would be revised slightly. The term “TIP update” would be added to provide information and direction on when a TIP must be updated . Anytime a non-exempt project is added to a TIP, the TIP must be updated. In attainment areas, the TIP must be updated whenever a regionally significant project is added to the TIP. </P>
                    <P>The definition of “transportation management area” would be unchanged. The terms “twenty year planning horizon, “urbanized area,” and “user of public transit” would be added to clarify legislative terminology. </P>
                    <HD SOURCE="HD1">Subpart B—Statewide Planning and Programming </HD>
                    <HD SOURCE="HD2">
                        <E T="03">Section 1410.200 Purpose of Regulations</E>
                    </HD>
                    <P>Current § 450.200 would be redesignated as § 1410.200. The statement of purpose would be amplified by reflecting the declaration of purpose articulated in the TEA-21. This amplification also supports greater consistency of purpose between metropolitan and statewide planning. </P>
                    <HD SOURCE="HD2">
                        <E T="03">Section 1410.202 Applicability of Regulation</E>
                    </HD>
                    <P>Current § 450.202 would be redesignated as § 1410.202. The text would be revised to add “project sponsors” as agencies affected by the provisions of this section. </P>
                    <HD SOURCE="HD2">
                        <E T="03">Section 1410.204 Definitions</E>
                    </HD>
                    <P>Current § 450.204 would be redesignated as § 1410.204. This section would remain the same. </P>
                    <HD SOURCE="HD2">
                        <E T="03">Section 1410.206 Statewide Transportation Planning Process:</E>
                         Basic Requirements 
                    </HD>
                    <P>Current § 450.206 would be redesignated as § 1410.206. </P>
                    <P>A new § 1410.206(a)(5) would be added. This section articulates the need for the State to develop and implement a process for demonstrating the consistency of plans and programs with the provisions of Title VI of the Civil Rights Act of 1964 and related legislation. We believe that such processes are already in place and that the clarification of minimum required information and analysis would benefit States and other agencies in meeting the existing requirement in the self-certification statement included in the STIP. </P>
                    <P>Current § 450.206(b) would be eliminated since it is redundant with § 450.210(a). </P>
                    <HD SOURCE="HD2">Section 1410.208 Consideration of Statewide Transportation Planning Factors </HD>
                    <P>Current § 450.208 would be redesignated as § 1410.208. Paragraph (a) would be revised by substituting the seven planning factors identified in the TEA-21 for those previously identified by the ISTEA. All parenthetical amplification has been deleted and the wording is that used by the statute. We plan to issue guidance regarding interpretation and application of the planning factors. We welcome suggestions on exemplary State and MPO procedures already in place or under development, and how those might be replicated in other State or MPO planning processes. We also recognize that it will take some time to develop syntheses of current practices and other tools. However, we will work with States, MPOs, and others to ensure that tools and examples are made available in a timely manner. </P>
                    <P>We are proposing to revise paragraph (b) to focus on other considerations that the TEA-21 states should be addressed in the planning process. Specifically, the concerns of non-metropolitan local officials and Indian Tribal Governments and Federal land managing agencies are spelled out as a source of concerns that shall be considered. </P>
                    <HD SOURCE="HD2">
                        <E T="03">Section 1410.210 Coordination of Planning Process Activities</E>
                    </HD>
                    <P>
                        Current § 450.210 would be redesignated as § 1410.210. Reflecting the simplification of language provided by the change in planning factors, paragraph (a) would be revised to focus on required planning coordination efforts. This general approach would eliminate the need to spell out in detail all of the specific coordination efforts previously articulated. We believe that the substance of coordination and the process overall remain intact even though the language is vastly simplified. References to the air quality planning process in § 1410.210(b) reflect the 
                        <PRTPAGE P="33932"/>
                        general role afforded the State transportation planning agency in the air quality planning process under 42 U.S.C. 7504 and the desirability of ensuring coordination of the air quality and transportation planning processes. The current wording of paragraph (b) would be retained as § 1410.210(e) with the addition of “safety concerns” to the list of issues to be coordinated. 
                    </P>
                    <HD SOURCE="HD2">Section 1410.212 Participation by Interested Parties </HD>
                    <P>Current § 450.212 would be redesignated as § 1410.212. Overall, current § 450.212 (public involvement) would be broadened to focus on all facets of participation in the statewide planning process. For example, the newly articulated provisions regarding consultation with non-metropolitan officials would be added to this section. In addition, the paragraphs would be redesignated. </P>
                    <P>Current §§ 450.212(a) through (f) would become § 1410.212(b) and be revised slightly to reflect increased emphasis for public involvement by minorities and low-income populations. The listing of interested parties to be afforded an opportunity to comment is revised to reflect the addition of transit users and freight service providers in statute. This listing reflects the wording of the statute. The FHWA and the FTA believe that the phrase “and other interested parties” reflects the intent of Congress to ensure that all citizens and groups are afforded an opportunity to participate. Comments are solicited as to whether there is a need to further elaborate the listing so as to demonstrate that the specific groups do not constitute an exclusive list of participants. A new § 1410.212(d) would be added to encourage the participation of state air quality and other agencies in the transportation planning process. The existing § 450.212(g) would become § 1410.212(e). </P>
                    <P>Section 1410.212(b)(2)(vii) makes provision for a periodic evaluation of its public involvement procedures by the State. The FHWA and the FTA believe that the assessment of such processes on a routine basis ensures their effectiveness and enhances continued improvement. The FHWA and the FTA also believe that the effectiveness of public involvement processes can be strengthened through the voluntary development of criteria on which to assess performance by States and MPOs. Where such criteria have been developed by the planning partners, the FHWA and the FTA will consider them in their certification reviews and planning findings, in addition to the generally applicable requirements for public involvement processes under § 1410.212(b)(2) and § 1410.316(b). </P>
                    <P>A new § 1410.212(c) focusing on participation by Federal agencies and Indian Tribal Governments would be added to support early involvement by these agencies and governments. Such involvement will facilitate streamlining of environmental decisions and ensure adequate consideration of key interests and viewpoints. The proposed wording for the involvement of Indian Tribal Governments reflects current deliberations within the Executive Branch regarding ways to more fully inform and engage Indian Tribal Governments in Federal decision making processes. </P>
                    <HD SOURCE="HD2">Section 1410.214 Content and Development of Statewide Transportation Plan </HD>
                    <P>Current § 450.214 would be redesignated as § 1410.214. Two new sections would be added to reflect legislative changes. Proposed § 1410.214(a)(3) would reflect the intelligent transportation system consistency requirement provided under section 5206(e) of the TEA-21. A separate rulemaking process will address the overall policy and procedures for architecture consistency. The wording reflects that portion of the consistency process that would be started in the statewide planning process for non-metropolitan area projects. We are interested in comments and observations regarding the feasibility of this process. In our view, the basic structure would reflect the activities normally conducted during transportation plan development. Proposed minor information collection additions to reflect utilization of electronic information sharing do not appear to be a major burden addition for planning. </P>
                    <P>In addition, proposed § 1410.214(d) would implement a provision, added by TEA-21, for an optional financial plan for statewide transportation plans. The TEA-21 did not impose a new requirement on the States. Rather, it offers up the option of a financial plan if decided upon by the statewide planning process participants. This section would spell out how this option would be approached through a statewide planning process. </P>
                    <HD SOURCE="HD2">Section 1410.216 Content and Development of Statewide Transportation Improvement Program </HD>
                    <P>Current § 450.216 would be redesignated as § 1410.216. The provisions of former § 450.216(a)(1) through (a)(9) would be redesignated and revised as § 1410.216(c) providing detailed information on the STIP. A new § 1410.216(b) would spell out the need to involve certain interests in the development of the STIP. The parties identified are the same as those identified for the development of the plan. </P>
                    <P>Regarding the detailed information requested for projects identified in a STIP in § 450.216(c), a new element (§ 1410.216(c)(8)) regarding ITS projects funded with highway trust funds would be added. This section reiterates the earlier planning level discussion and would direct that projects meeting the definition in § 1410.322(b)(11) would be included in a regional architecture as indicated in the rulemaking on ITS architecture consistency. </P>
                    <P>The new wording proposed in § 1410.216(f) articulates the legislative provision of an optional financial plan for STIPs. </P>
                    <HD SOURCE="HD2">Section 1410.218 Relation of Planning and Project Development Processes </HD>
                    <P>A new § 1410.218 would address an optional approach to linking statewide planning and project development processes in non-metropolitan areas. It mirrors proposed § 1410.318 which would apply to the metropolitan planning process. The intent of this section is to provide States with an option to more effectively rely on planning processes as a foundation for subsequent environmental and other project level analyses. Nothing in this section would mandate that a State adopt the option provided. If a State chose to take advantage of the option, the language lays out a framework to support the State's actions. This section also would make clear that project level actions shall be consistent with the State plan and program (see proposed § 1410.218(e)). For further information, please see the preamble section related to metropolitan planning, proposed § 1410.318. </P>
                    <HD SOURCE="HD2">Section 1410.220 Funding of Planning Process </HD>
                    <P>The content of the current § 450.218 would be moved here with changes made to the references and the section heading. </P>
                    <HD SOURCE="HD2">Section 1410.222 Approvals, Self-certification and Findings </HD>
                    <P>
                        Current § 450.220 would be redesignated as § 1410.222. Current § 450.220(a)(2) would be revised slightly. Proposed § 1410.222(a)(3) through (a)(5) would articulate the existing legislative and regulatory authorities. Subsequent paragraphs would be redesignated and remain 
                        <PRTPAGE P="33933"/>
                        generally unchanged. A new § 1410.222(a)(10) would be added. 
                    </P>
                    <P>We are proposing to modify existing § 450.220(b) slightly to indicate the relationship of the planning finding to self-certifications by the State. In addition, current language provided at § 450.220(c) would be redesignated and combined with a new § 1410.222(b) to clarify the relationship of findings with possible Federal actions. </P>
                    <P>Proposed § 1410.222(c) that details the approval period for a STIP would modify the text of current § 450.220(d). STIP extensions (and by their inclusion, TIP extensions) would be limited to 180 days. Further, no STIP extension would be granted in nonattainment and maintenance areas. We believe that this policy eliminates substantial confusion regarding application of the Clean Air Act (CAA) conformity provisions in nonattainment and maintenance areas. We also believe that the focus should be on ensuring regular STIP updates, rather than finding a way to maintain funding flows that may conflict with the provisions of the CAA. The overall limit on extensions serves the same general purpose for attainment areas of ensuring that updates are accomplished rather than continuing to rely on out of date documents. </P>
                    <HD SOURCE="HD2">Section 1410.224 Project Selection </HD>
                    <P>Current § 450.222 would be redesignated as § 1410.224 and the references to funding categories updated. Generally, however, it would remain unchanged. Proposed new paragraph (e) would provide the option for expedited procedures where agreed to by the planning participants. The current topic of this section (§ 450.224 phase-in requirements) would be eliminated. </P>
                    <HD SOURCE="HD2">Section 1410.226 Applicability of NEPA to Transportation Planning and Programming </HD>
                    <P>This section simply proposes to restate the provisions of the TEA-21 which direct that decisions by the Secretary regarding plans and programs are not Federal actions subject to the provisions of the NEPA. </P>
                    <HD SOURCE="HD1">Subpart C—Metropolitan Transportation Planning and Programming </HD>
                    <HD SOURCE="HD2">Section 1410.300 Purpose of Planning Process </HD>
                    <P>Current § 450.300 would be redesignated as § 1410.300. This statement would remain essentially unchanged. The exceptions are a minor wording change for clarity of Federal expectations with regard to plan content and the addition of the word “management” to reflect the revised declaration of policy in 23 U.S.C. 134(a) as revised by the TEA-21. </P>
                    <HD SOURCE="HD2">Section 1410.302 Organizations and Processes Affected by Planning Requirements </HD>
                    <P>Current § 450.302 would be redesignated as § 1410.302. The principal change would be to add organizations charged with “project development” in metropolitan areas to the affected organizations. This would reflect the general emphasis of the revised rule on more efficiently and effectively linking planning and project development as a means to streamlining decision making and towards ensuring that projects are based on the planning process. The statutory authorizing language reference would be added also. </P>
                    <HD SOURCE="HD2">Section 1410.304 Definitions </HD>
                    <P>Current § 450.304 would be redesignated as § 1410.304. This section would remain unchanged with the exception of referencing definitions in 49 U.S.C. Chapter 53. </P>
                    <HD SOURCE="HD2">Section 1410.306 What is a Metropolitan Planning Organization and How Is It Created </HD>
                    <P>Current § 450.306 would be redesignated as § 1410.306. Minor changes are proposed for existing § 450.306(a) to provide clarity regarding the designation of multiple MPOs serving a single metropolitan area. The wording would more clearly emphasize a preference for not designating more than one MPO in metropolitan areas. We believe that this is consistent with the intent of legislative language changes and the principles of comprehensive transportation planning for metropolitan areas. </P>
                    <P>Current §§ 450.306(b) and (c) would remain unchanged. Current § 450.306(d) and (g) would be combined and redesignated as § 1410.306(f), § 450.306(e) would be redesignated as § 1410.306(d) and § 450.306(f) would be redesignated as § 1410.306(e). Editing for clarity of intent would simplify the language. Current § 450.306(e) would be redesignated as § 1410.306(d). Sections 450.306(h) through (k) would be redesignated as §§ 1410.306 (g) through (j), respectively, and revised. </P>
                    <HD SOURCE="HD2">Section 1410.308 Establishing the Geographic Boundaries for Metropolitan Transportation Planning Areas. </HD>
                    <P>Current § 450.308 would be redesignated as § 1410.308. Revisions made by the TEA-21 to 23 U.S.C. 134 require the modification of existing § 450.308, which also would be edited for clarification of language. Boundaries in effect as of June 9, 1998, the date of presidential signature for the TEA-21, would remain in effect unless modified by the policy board of the MPO in cooperation with the Governor. The provisions of 23 U.S.C. 134, as modified by the ISTEA, required planning area boundaries to be extended to the limits of the nonattainment area where that area was larger than the transportation planning area. </P>
                    <P>New MPOs designated after June 9, 1998, would have to take into account the existence of non-attainment and maintenance areas and reflect them as agreed to by the Governor and local officials in the proposed metropolitan planning area boundaries. </P>
                    <P>In either case, the existing MPO or new MPO, non-attainment and maintenance areas left outside the metropolitan planning areas would have to be addressed in an agreement between the State and the MPO as proposed at paragraph § 1410.310(f). </P>
                    <P>The option of extending the metropolitan planning area boundary to the limits of the metropolitan statistical area would be retained as provided in the statute. This continuation and the changes discussed in the preceding paragraphs are captured in proposed revisions included in § 1410.308(a). </P>
                    <P>The wording of current § 450.308(b) would remain unchanged. The provisions of current § 450.308(c) would be slightly modified for clarification. No changes are proposed for § 450.308(d). </P>
                    <P>A new § 1410.308(e) proposes to address the expenditure of Surface Transportation Program funds attributable to a Transportation Management Area (TMA). The intent of the section is to more clearly state, what has been the FHWA and the FTA policy since 1992, that these funds cannot be expended outside the boundaries of the metropolitan area. They may be expended anywhere inside the metropolitan area including areas outside the urbanized area. </P>
                    <HD SOURCE="HD2">Section 1410.310 Agreements Among Organizations Involved in the Planning Process </HD>
                    <P>
                        Current § 450.310 would be redesignated as § 1410.310. Current § 450.310(a) would be retained in its current form except for the elimination of a reference to corridor and subarea studies. A new proposed § 1410.310(b) would state the overall relationship between planning and project development activities. This section would support the option for conducting project development activities as planning activities under the general relationship between 
                        <PRTPAGE P="33934"/>
                        planning and project development as established under the proposed new § 1410.318. 
                    </P>
                    <P>Current § 450.310(c) would be redesignated as § 1410.310(c) and the text would remain unchanged except for minor wording revisions for clarification. Section 450.310(d) would be redesignated as § 1410.310(h) and revised for clarity. Current § 450.310(e) would be revised by dropping the reference to a definition of a prospectus in § 450.104. A definition is not required since the nature of prospectus is well established in practice as a statement of ongoing planning activities that continue from year-to-year as a foundation for producing transportation plans and programs. </P>
                    <P>The current § 450.310(f) would be redesignated as § 1410.310(e) and modified slightly by a wording change to support the revisions to the air quality and transportation planning area boundary relationship. The change is intended to suggest that actions that would leave portions of nonattainment and maintenance areas outside a metropolitan transportation planning area, but contiguous to such an area, should be addressed in consultation with the FHWA, the FTA, and the EPA. The decision to leave such areas outside a metropolitan planning area is the responsibility of the Governor and the MPO acting cooperatively. </P>
                    <P>A proposed new § 1410.310(g) has been added to reflect the impact of section 5206(e) of the TEA-21. The proposed section requires an agreement among agencies planning and implementing ITS projects and is intended to ensure that the planning and operating agencies specifically agree on an approach to integrated ITS implementation consistent with the options provided in the National ITS Architecture. This provision would direct that this relationship should be covered by agreement within the metropolitan planning area and addresses the policy and operational issues affecting ITS implementation. Where current agreements do not already address these relationships, they would be modified to reflect the provisions of this section. Where possible, existing agreements, per the provisions of § 1410.310(i), would be modified to incorporate the ITS integration strategy required under proposed § 1410.322(b)(11). </P>
                    <P>A new proposed § 1410.310(h) would permit a single agreement for all activities under § 1410.310 where agreed to by the participants. The wording in current § 450.310(h) remains unchanged from its current text and would be included in a redesignated § 1410.310(i). </P>
                    <HD SOURCE="HD2">Section 1410.312 Planning Process Organizational Relationships </HD>
                    <P>Current § 450.312 would be redesignated as § 1410.312. Existing § 450.312(a) would be redesignated as § 1410.312(a) and modified in several places to reflect wording changes in the subsequent provisions of §§ 1410.314 through 1410.322. A phrase would be made to reflect international border planning with Canada and Mexico. </P>
                    <P>The text of current § 450.312(b) would be redesignated as § 1410.312(b) and remain unchanged. </P>
                    <P>The organization of current § 450.312(c) and some of the previous content would be modified and redesignated as § 1410.312(c). The content modifications are intended to clarify how MPO transportation planning activities and planning products are related to air quality planning activities and products. Under 42 U.S.C. 7504, MPOs and State transportation planning organizations are expected to have a formal role in air quality planning. At another level, the transportation and air quality planning processes would work more efficiently if the responsible agencies were more actively engaged in each other's processes. Hence, the proposed rule would more explicitly direct MPOs to participate in air quality planning activities. We would expect that the air quality planning agencies, under the U.S. EPA's conformity regulation (40 CFR parts 51 and 93), would be actively engaged in the transportation planning process. The development of transportation control measures is specifically revised to clarify that new TCMs proposed for funding with FHWA and/or FTA transportation funds or requiring an FHWA or FTA approval can occur during a conformity lapse, if new TCMs are included in an interim plan and interim TIP that satisfy the provisions of this part and are approved into a SIP with identified emission reduction benefits (specified but not necessarily credited in the applicable SIP). The proposals herein implement and clarify the planning regulations consistent with the “National Memorandum of Understanding between the US Department of Transportation and the US Environmental Protection Agency,” which was signed on April 19, 2000. This memorandum of understanding outlines procedures for advancing new TCMs during a conformity lapse. </P>
                    <P>Current § 450.312(d) would be redesignated as § 1410.312(d) and remain unchanged. </P>
                    <P>Minor wording changes would be made to current § 450.312(e) [proposed § 1410.312(e)] to clarify required coordination in circumstances where more than one MPO is involved in transportation planning for a contiguous metropolitan area, including multi-state areas. </P>
                    <P>Proposed § 1410.312(f) (current § 450.312(f)) would be revised for text clarity. Proposed § 1410.312(g) (current § 450.312(g)) would be revised to remove a specific reference to cooperative development of the congestion management system (CMS) since it is incorporated in the management system regulation provided at 23 CFR part 500. </P>
                    <P>Current § 450.312(h) is redesignated as § 1410.312(h) and revised. Proposed § 1410.312(i) (current § 450.312(i)) would be revised by replacing the words “involved appropriately” with “consulted” to more accurately reflect the statutory intention. </P>
                    <P>A new § 1410.312(j) is proposed to reflect the legislative changes of the TEA-21 which added several new discretionary grant programs. This section asserts that the projects (other than planning and research activities) funded through these programs must be addressed through the transportation planning process and included, as appropriate, in transportation plans and programs. Planning and research activities funded under the referenced programs are addressed in the Unified Planning Work Programs (UPWP) for each metropolitan planning area. </P>
                    <HD SOURCE="HD2">Section 1410.314 Planning Tasks and Work Program </HD>
                    <P>Current § 450.314(a) would be redesignated as § 1410.314(a). The provisions of this overall section remain largely unchanged except for wording revisions for clarity or to reflect modifications in other sections, e.g., elimination of the MIS proposed under § 1410.318. One change to § 450.314(a) proposes to drop the reference to TMAs. This is intended to suggest that all MPOs have a responsibility to meet the requirements of this section. It does not prevent a smaller, attainment area MPO from proposing a prospectus or a simplified work program. Paragraph (c) of current § 450.314 would be revised and redesignated as § 1410.314(c). A new paragraph (d) will be added as § 1410.314(d). </P>
                    <HD SOURCE="HD2">
                        <E T="03">Section 1410.316 Transportation Plan Development</E>
                    </HD>
                    <P>
                        Current § 450.316 would be redesignated as § 1410.316. Overall this section has extensive proposed revisions for several reasons. The 
                        <PRTPAGE P="33935"/>
                        metropolitan planning factors were revised by the TEA-21; reduced in number from 16 to 7. The wording in § 450.316(a) would be revised by substituting the seven planning factors identified in the TEA-21 for those previously identified by the ISTEA. All parenthetical amplification would be removed and the wording would be the same as that used in the statute. We plan to issue guidance regarding interpretation and application of the planning factors. This will be especially true of new planning goals, such as safety, environmental considerations, and operations and management, which have been added to the list. 
                    </P>
                    <P>The US EPA has suggested that the FTA and the FHWA amplify and elaborate the detail in the regulation regarding the meaning of the planning factors. The agencies have kept the language as stipulated in the statute. However, the agencies believe that substantial benefits can be realized by States and MPOs in applying the planning factors, under §§ 1410.214 and 1410.316(a), aggressively, most notably in supporting the provisions of § 450.318 below. The planning factors can serve as a key focal point for developing plans and programs and MPOs and States may develop specific rationales to guide their utilization in the plan development process. Indeed, where States and MPOs choose to develop their own performance criteria to monitor the results of planning, they may be well served by utilizing the planning factors as a base for those criteria. The FTA and the FHWA will support efforts by States and MPOs to utilize such criteria by addressing them in Federal reviews and assessments. In addition, the agencies will seek to develop specific examples of how the planning factors can support effective plan development and environmental streamlining. Streamlining, as an activity to reduce project level burden and delay, could be more readily achieved if the planning process provides an early consideration of the planning factors. </P>
                    <P>The FHWA and the FTA welcome suggestions on exemplary State and MPO procedures or data collection efforts already in place or under development and how those might be replicated in other State or MPO planning processes. We are interested also in specialized training efforts, e.g., safety, that may have been developed or needed by States and MPOs. We also recognize that it will take some time to develop syntheses of current practices and other tools. However, it is our intent to work with States, MPOs, and others to ensure that tools and examples are made available in a timely manner. </P>
                    <P>The public involvement provisions would be modified for clarity and would reflect the provisions of Presidential Executive Order 12898 on Environmental Justice and implementing DOT and FHWA orders. Similar changes have been made regarding references to compliance with the provisions of Title VI of the Civil Rights Act of 1964. The organization of § 450.316 would be modified slightly to reflect these changes and to provide clarity in understanding them. </P>
                    <P>The listing of interested parties to be afforded an opportunity to comment is revised to reflect the addition of transit users and freight service providers in statute. This listing reflects the wording of the statute. The FHWA and the FTA believe that the phrase “and other interested parties” reflects the intent of Congress to ensure that all citizens and groups are afforded an opportunity to participate. Comments are solicited as to whether there is a need to further elaborate the listing so as to demonstrate that the specific groups do not constitute an exclusive list of participants. </P>
                    <P>Section 1410.316(b)(9) makes provision for a periodic evaluation of its public involvement procedures by the State. The FHWA and the FTA believe that the assessment of such processes on a routine basis ensures their effectiveness and enhances continued improvement. The FHWA and the FTA also believe that the effectiveness of public involvement processes can be strengthened through the voluntary development of criteria on which to assess performance by States and MPOs. Where such criteria have been developed by the planning partners, the FHWA and the FTA will consider them in their certification reviews and planning findings. </P>
                    <P>Relatively small scale modifications to the public involvement provisions are proposed as follows: (1) The provision of timely information will be modified to encourage engagement of the public during the early stages of plan and TIP development; (2) demonstration of timely response to comments received would be revised to highlight response to input from minority and low-income populations; and (3) periodic MPO evaluations of public involvement effectiveness would now include an emphasis on the success obtained in engaging minority and low-income populations. </P>
                    <P>Current § 450.316(b)(2) is proposed to be redesignated as § 1410.316(c). Additional attention is drawn to the provisions of Executive Order 12898 and implementing DOT and FHWA orders. Specifically, data necessary for the purposes of conducting planning analyses for plan development are identified as contributors to the demonstration of compliance with the Executive Order. We are required to assure compliance with the Executive Order and will rely on the data identified under this section for that purpose. In addition, the statutory and regulatory requirements identified in this section apply to State DOTs, MPOs, and transit operators. Consequently, additional data and analyses are proposed as a basis for demonstrating that plans and resulting programs will be consistent with the referenced statutory requirements. Additional guidance will be issued to refine and amplify the basic framework established by these provisions. We believe, however, that much of the proposed data specification was previously required for assertions of compliance with Title VI and related statutory authorities and, hence, should not require a major new data collection effort. </P>
                    <P>In addition to the revised requirements of this section, the FHWA and the FTA continue to encourage attention to the selection of members of boards and committees that represent the demographic profile of the metropolitan planning area served. The ability to meet the needs of the community is enhanced by efforts designed to provide voice to as many segments of its membership as possible. The FHWA and the FTA solicit comments regarding additional strategies that may be effective in serving the interests of inclusiveness in transportation decision making. </P>
                    <P>Current §§ 450.316(b)(3) through 450.316(b)(5) would be redesignated as § 1410.316(d) through (f). Current § 450.316(c) would be redesignated as § 1410.316(g) and revised for clarity. Current § 450.316(d) is proposed to be redesignated as § 1410.316(h). </P>
                    <P>Proposed § 1410.316(i) is offered to encourage the coordination of federally funded non-emergency transportation services per the requirements of section 1203(d)(4) of the TEA-21. The section simply restates the legislative language. </P>
                    <HD SOURCE="HD2">
                        <E T="03">Section 1410.318 Relation of Planning and Project Development Processes</E>
                    </HD>
                    <P>
                        The TEA-21 eliminates the major investment study (MIS) as a separate requirement as set forth in the planning regulations and calls for integration of the requirement, as appropriate, into the planning and NEPA analyses required under proposed 23 CFR parts 1410 and 1420. Accordingly, current § 450.318 
                        <PRTPAGE P="33936"/>
                        would be revised to focus on the relationship between the planning and project development processes. 
                    </P>
                    <P>Section 1308 of the TEA-21 directs the US DOT Secretary to eliminate the separate MIS and its elements and integrate the remaining aspects of the MIS into the planning and NEPA regulations. The FHWA and FTA have attempted to do this by focusing on the fundamental basics of the MIS process, i.e., the cooperative relationship of planning and project development agencies, the early engagement of permit and resource agencies, flexible definition of the need to do analyses as decided by the participants and an appropriate level of public involvement. The MIS process did not require a specific methodology for studying alternatives, a specific set of alternatives to study, a particular format for reports, a specific public involvement or analytical process, or a specific set of projects to which the MIS applied. The US EPA has specifically suggested that the MIS process required and should require the use of cost benefit, costs effectiveness analysis and/or other related analytical techniques. The logic of this proposal is that early, effective consideration of social, environmental and economic considerations in planning analyses should permit more expedited consideration of these same issues, at a more micro level of detail, for subsequent NEPA analyses. By linking the planning and project development processes more effectively, the participants can reduce time required, analytical redundancy and process requirements by utilizing previously conducted work as a basis for subsequent analyses and efforts. It is the belief of the FTA and the FHWA that an aggressive utilization of the options provided here can strengthen the planning process and streamline the project development process substantially. The agencies are specifically interested in comments that address the extent to which the remaining aspects of the MIS process have been included in this proposal and suggestions for encouraging States and MPOs to more effectively take advantage of the options provided herein. </P>
                    <P>The overall structure of the relationship emphasizes alternatives for planning and sponsor agencies to integrate decision processes to take advantage of potential streamlining opportunities and for early consultation among the MPOs, State DOTs, and transit operators. The planning process is charged with providing an initial statement of purpose and need for proposed transportation improvements, identifying and evaluating alternatives (including, but not limited to, design concept and scope) and selecting an alternative and including it in the plan. This statement would not necessarily lead to a determination of purpose and need on a project-by-project basis for transportation improvements normally grouped (not specified individually) in a plan. An alternative could be a programmatic statement of purpose and need that identifies the basis for investing resources in a given transportation area such as safety or pavement resurfacing. </P>
                    <P>The consideration of alternatives and other planning level analyses done in support of plan development do not eliminate the need for considering all reasonable alternatives during the NEPA process. However, to the extent that the planning participants anticipate the required consideration of all reasonable alternatives in the planning process, they will significantly enhance, in our view, the efficiency of the NEPA process. Well documented, thorough planning analyses should permit the NEPA process to accept this information as a sound basis for reducing the alternatives considered and the detail required for others in the NEPA process. Provision also is made for policy preferences and guidance from planning policy bodies to be included on the record for consideration in subsequent decision steps. </P>
                    <P>Examples of issues that might be covered in the planning level consideration of alternatives include: the consideration of alternatives that in the past have been rejected for not fully meeting traditional concepts of purpose and need; more broadly defined purpose and need statements during the planning stage so that a full range of modal alternatives are considered; an alternatives analysis that examines “no-build” alternatives that use transportation demand strategies; and, flexibility to encourage the selection of alternatives which may have lower than originally desired levels of transportation service if there are cost, time, and impact savings. The FHWA and the FTA will work with the US EPA on guidance and training in this regard. </P>
                    <P>A number of alternative sources of information are identified as a basis for the development of purpose and need, a planning level analysis of alternatives (primarily at the level of concept and scope) and specification of a project for inclusion in the transportation plan. These information sources are utilized at the discretion of participating agencies (MPO, State DOT, and transit agency) acting jointly. The underlying logic of the proposal is that if the options to document thoroughly and analyze fully are chosen, this effort will lead to expedited analytical efforts in subsequent NEPA analyses. Less robust analytical and documentation efforts would force elaboration and analysis of alternatives during the NEPA process. </P>
                    <P>
                        The utilization of planning analyses as a basis for project development actions is explained. In particular the regulatory language specifies that the results of planning analyses shall serve as input to the environmental process under proposed 23 CFR part 1420 (current part 771), and other project level actions. Proposed § 1410.318(c) references the contents of proposed § 1420.201 to provide a frame of reference to data and analytical expectations in subsequent NEPA process steps, 
                        <E T="03">i.e.,</E>
                         the standard of analysis expected by the NEPA process for projects. Planning, systems level, analyses that address these data and analytical requirements can improve the efficiency of the NEPA process and reduce data and analytical efforts required. 
                    </P>
                    <P>The ability to streamline the planning and environmental relationship is dependent, in part, on appropriate decisions made by the planning participants. They can choose to develop a rigorous basis for establishing transportation purpose and need, identifying alternatives for evaluation, and assessing these alternatives through the planning process. Alternatively, they can choose to apply minimal analytical techniques. At the time the NEPA analyses are undertaken for project development, the agencies participating in that process will review the materials provided by the planning process. Minimal analyses in planning will have to be supplemented and elaborated to satisfy the needs of the NEPA process. More robust planning analyses should allow the NEPA process to reduce the need for revisiting and re-evaluating planning level studies and instead proceed to focus on project level considerations of location and design. Consequently, the consideration of alternatives should be more quickly and efficiently accomplished. </P>
                    <P>
                        A similar option exists with regard to documentation of planning results. A set of planning activities to be documented to facilitate this linkage is specified in § 1410.318(a)(2). The option to document is a discretionary option of the planning participants in cooperation with appropriate project sponsors. The focus is not on the details of documents but rather on the act of documenting the results of analyses and studies. Robust analyses coupled with sound documentation will permit more effective linkage and utilization of 
                        <PRTPAGE P="33937"/>
                        planning analyses and data collection in subsequent NEPA analyses. 
                    </P>
                    <P>The early involvement of Federal and State environmental and permit agencies is encouraged under proposed § 1410.318(d) to facilitate linking planning and environmental processes. The involvement of the FTA is required where planning studies are proposed to satisfy requirements of the Major Capital Investment Program administered by the FTA under 49 CFR part 611. The TEA-21 directive that Federal decisions on plans and programs are not considered a Federal action for NEPA purposes is restated in proposed § 1410.318(f) (the FHWA and the FTA do not approve plans but they do approve the State TIP which is not subject to NEPA). Finally, the basis for Federal project actions in plans and TIPs is specifically stated. The intent of this latter provision, in proposed § 1410.318(g), is to clearly substantiate the need for projects to be in plans before Federal actions can be taken on them. A particular point is made that project actions and the appropriate phase of a project must be in a plan and TIP before project actions can be taken. </P>
                    <HD SOURCE="HD2">Section 1410.320 Congestion Management System and Planning Process </HD>
                    <P>Current § 450.320 would be redesignated as § 1410.320 and would be revised to reflect the impact of the issuance of the Management System rule (23 CFR part 500) and the National Highway System Act of 1995, Public Law 104-59, 109 Stat. 568. The latter made management systems optional, except for the congestion management system in transportation management areas (TMA). Hence, the proposed language focuses on the continuing provisions of the congestion management system in TMAs, including the limitation on single occupant vehicle capacity increases which remains unchanged under the TEA-21. With the exception of current § 450.320(a) which would be removed, the remainder of the overall section is generally unchanged. </P>
                    <P>One option considered, but not included in this proposal, is to revise 23 CFR part 500 by transferring the provisions dealing with the congestion management system to the metropolitan planning rule. The FHWA and the FTA would welcome comments on this idea with regard to its utility and appropriateness. </P>
                    <HD SOURCE="HD2">Section 1410.322 Transportation Plan Content </HD>
                    <P>Current § 450.322 would be redesignated as § 1410.322. Current § 450.322(a) would be modified by adding a discussion of data assumptions for plan updates. Specifically, the language would clarify what must be considered in preparing a plan update, as a minimum. It also would reaffirm that the MPO must approve the content of a new plan or reaffirm existing plan content in conducting an update. We have chosen to provide this clarification in response to requests from stakeholders and to emphasize that a plan is a critical document. Piecemeal revisions that incrementally revise plans do not constitute an appropriate, accurate or meaningful basis for plan development, implementation, and/or subsequent decision making. </P>
                    <P>A proposed minor revision would be made to § 450.322(b)(2) to reflect the emphasis on management and operation of the transportation system. </P>
                    <P>Current §§ 450.322(b)(3) through (b)(6) would remain unchanged with the exception of minor edits for clarity. Current § 450.322(b)(7) would be revised to reflect the elimination of the MIS and redesignated as § 1410.322(b)(7). Current § 450.322(b)(8) would be removed. Current §§ 450.322(b)(9) and (10) would be redesignated as §§ 1410.322(b)(8) and (9), respectively. </P>
                    <P>Current § 450.322(b)(11) would be redesignated as § 1410.322(b)(10) and remain generally unchanged except for the addition of the reference to “illustrative projects.” Illustrative projects have no standing for transportation or air quality purposes until such time as a financing source has been identified and they have been formally amended into the plan by action of the MPO. At that point they could be added to a TIP as a project to be advanced. We expect that the MPO would coordinate its actions with the State DOT and transit operator and vice versa. Once formally added to a plan and TIP, these projects may be included in regional conformity findings, advanced, and subject to appropriate project level actions by the FHWA and the FTA. </P>
                    <P>
                        The remainder of § 450.322(b)(10) would remain generally unchanged since the TEA-21 either did not change key provisions or reenforced previous provisions required through regulation (
                        <E T="03">e.g.,</E>
                         cooperative estimates of revenue for plan development). With regard to estimated revenues, we have opted to rely on a cooperative process of State, MPO and transit operator estimation based on local preferences and arrangements. We would support the cooperative process through the provision of guidance and identification of good practices for emulation. 
                    </P>
                    <P>A new § 1410.322(b)(11) proposes to focus on intelligent transportation systems (ITS) and the National ITS Architecture. As provided in section 5206(e) of TEA-21, we have issued interim guidance on compliance with this new legislative requirement. This proposed wording is intended to be an integral element of the proposed regulatory issuance on compliance with this requirement. A companion NPRM issuance will be made for project development and national policy on consistency with the National ITS Architecture. It will support planning as the initial stage at which this consistency must begin. We are issuing the planning component through this NPRM and solicit comments on this proposal. </P>
                    <P>The existing wording of § 450.322(c) would be redesignated as § 1410.322(c) and would be modified to add users of public transit and freight shippers as directed by the TEA-21. A minor modification would be made to § 450.322(d) (proposed § 1410.322(d)) to clarify that if either the MPO or we fail to make a conformity determination, the Governor or the Governor's designee must be notified. </P>
                    <P>
                        A new § 1410.322(e) would refine the operating approach to plan changes and updates. The question of a 20-year horizon has received substantial discussion as indicated previously. As part of the clarification of the meaning of the term “20-year horizon,” we are proposing that a plan is valid for transportation purposes if it has a twenty year horizon at the time of adoption. If no major changes are made to the plan, 
                        <E T="03">e.g.,</E>
                         the addition of a non-exempt project, then the plan would remain valid as a basis for Federal actions until its next regularly scheduled update. This proposal also indicates that it is our intent that conformity determinations by the FHWA/FTA be made as close as possible to the MPO plan conformity finding, 
                        <E T="03">i.e.,</E>
                         as soon as possible after MPO plan adoption and conformity determination actions are taken. The three year period and the twenty year horizon would start at the point a Federal conformity determination is made on the plan for a nonattainment or maintenance area. This will eliminate confusion over the validity of the transportation plan in relation to air quality conformity determination. A new conformity determination would be required within eighteen months of certain SIP actions according to 40 CFR 93.104, even if the three year period had not expired at the time. In an attainment area, the plan would be valid for five 
                        <PRTPAGE P="33938"/>
                        years from MPO approval so long as no regionally significant projects are added. 
                    </P>
                    <P>The current requirement of § 450.322(e) that new plans and plan updates be provided to us would be included in proposed § 1410.322(f). </P>
                    <P>A new § 1410.322(g) would be added to authorize utilization of an interim plan during an anticipated conformity lapse. It is the intent of this section to permit funding of existing exempt, transportation control measures (TCMs) and other projects that can advance under a conformity lapse in accordance with 40 CFR parts 51 and 93. New TCMs under this provision can only be approved or funded during a conformity lapse when they have been included in an approved SIP with identified emission reduction benefits (but not necessarily credited in the applicable SIP). Inclusion in the SIP would have to occur before such TCMs can be advanced into completion of the NEPA process, design, right of way acquisition and/or construction). An interim plan may be used during a conformity lapse to advance projects that can proceed according to 40 CFR parts 51 and 93, including existing TCMs and existing and new exempt projects. It is the expectation of the US DOT that this provision would be utilized for new TCM projects where a conformity lapse would persist for six months or longer. An interim plan may be used for periods of less than six months to advance existing TCM and existing and new exempt projects. </P>
                    <HD SOURCE="HD2">Section 1410.324 Transportation Improvement Program Content </HD>
                    <P>Existing §§ 450.324(a) through (e) would have minor modifications to the text and be redesignated as §§ 1410.324(a) through (e). Please note, however, that an addition to proposed § 1410.324(b) would reflect the changes in proposed § 1410.222(c) to limit STIP/TIP extensions to 180 days in attainment areas. The prohibition against STIP/TIP extensions in nonattainment and maintenance areas is present also in proposed § 1410.324(b). Additionally, the current wording reflects TEA-21's confirmation of the previous regulatory provisions; most notably, the cooperative estimate of available funds. As indicated above, the estimation process would be achieved through locally identified processes. </P>
                    <P>
                        In existing § 450.324 (proposed § 1410.324), proposed paragraph (f)(1) would be unmodified. Paragraph (f)(2) would be modified to reflect changes in funding categories (
                        <E T="03">e.g.,</E>
                         minimum guarantee, etc.) and the elimination of the exemption for Motor Carrier State Assistance Program and 23 U.S.C. 402 safety program projects from being included in a TIP. The exemption for these two categories would be removed to reflect the ITS consistency requirement discussed above and the requirement that transportation projects funded with Federal-aid funds must satisfy the requirements of 23 U.S.C. and, where appropriate, be found conforming for air quality purposes. 
                    </P>
                    <P>
                        In current § 450.324(f)(3) (redesignated as § 1410.324(f)(3)), “approval” would be changed to “action” to reflect a broader concept regarding the range of our activities taken with regard to projects, 
                        <E T="03">i.e.,</E>
                         not all of them are labeled “approvals” but, yet, they must still be based on plans and programs. 
                    </P>
                    <P>Current §§ 450.324(f)(4) and (f)(5) would be modified and redesignated as §§ 1410.324(f)(5) and (f)(6), respectively. The changes are intended to clarify that all regionally significant projects in air quality non-attainment and maintenance areas, whether funded federally or otherwise, would be included in the metropolitan TIP. This allows full consideration of all projects in a regional conformity determination and ensures that the provisions of the CAA are met. </P>
                    <P>The three year conformity period for a TIP would start from the date of the conformity determination by the FHWA and the FTA. It is our expectation that the time period from the point of a Federal conformity determination on the TIP and its inclusion by the Governor's action in the STIP and the subsequent gubernatorial approval of the STIP and planning finding and STIP approval by the FHWA and the FTA would be monitored to ensure efficient and expeditious processing by all parties. </P>
                    <P>
                        With the exception of proposed minor changes for clarification regarding fiscal constraint, § 450.324(g) (proposed § 1410.324(g)) would be unchanged. The changes would reiterate the need for specification of funding sources for projects included in a TIP. The wording of existing § 450.324(h) (proposed § 1410.324(h)) would be unchanged. The content of § 450.324(i) (proposed § 1410.324(i)) would be modified to indicate that only regionally significant projects funded under Chapter 2 of 23 U.S.C. need be specifically identified in a TIP. These projects are typically “Federal Lands” projects, 
                        <E T="03">e.g.,</E>
                         Indian Reservation Roads, National Park Service Road, etc. The existing §§ 450.324(j) through (m) (proposed § 1410.324(j) through (m)) would be generally unchanged except for statutory reference modifications. 
                    </P>
                    <P>Existing § 450.324(n) (proposed § 1410.324(n)) would be modified to include an indication that projects are to be included on the TIP until fully authorized. A new § 1410.324(n)(5) is proposed to require that the TIP shall serve as the basis for an annual listing of projects, supplemented as appropriate, to ensure adequate public information regarding projects funded with Federal monies. Both changes are geared at ensuring greater clarity as to what projects must be included on a TIP. </P>
                    <P>The second change to proposed § 1410.324(n) serves another purpose—encouraging greater public knowledge regarding which projects have been advanced. In this case, we are opting to allow the planning participants the flexibility to design a process to comply with the legislative directive provided in section 134(h)(7)(B) of title 23 U.S.C. for an annual listing of projects. While the statute focuses on the MPO, we believe that the State DOT, transit operator, and the MPO operating jointly can produce the required information. </P>
                    <P>The MPO, in cooperation with its planning partners would, under this proposal, utilize the TIP as the basis for the annual listing. Each year the participating agencies would identify the projects that advanced (or did not) and publish the “list” jointly, in a fashion consistent with the public involvement provisions for the metropolitan area. Changes to the TIP would be acknowledged and reflected in modifications to the annual listing as appropriate. </P>
                    <P>Current § 450.324(o) would be redesignated as § 1410.324(o) with no other changes. </P>
                    <P>In general, we believe that it may be possible to further streamline the information and procedural requirements expected of TIPs, particularly with regard to financial information. We would be interested in any possible information reduction options that may be possible while maintaining the principles and practices of sound public involvement and fiscal constraint. </P>
                    <P>
                        A new § 1410.324(p) would be added to authorize utilization of an interim TIP during an anticipated conformity lapse. It is the intent of this section to permit funding of existing exempt, transportation control measures (TCMs) and other projects that can advance under a conformity lapse in accordance with 40 CFR parts 51 and 93. New TCMs under this provision can only be approved or funded when they have been included in an approved SIP with identified emission reduction benefits (but not necessarily credited in the 
                        <PRTPAGE P="33939"/>
                        applicable SIP). These TCMs would have to be included in the SIP before they can be advanced into completion of the NEPA process, design, right of way acquisition and/or construction). An interim plan may be used during a conformity lapse to advance projects that can proceed according to 40 CFR parts 51 and 93, including existing TCMs and existing and new exempt projects. It is the expectation of the US DOT that this provision would be utilized for new TCM projects where a conformity lapse would persist for six months or longer. An interim TIP may be used for periods of less than six months to advance existing TCM and existing and new exempt projects. 
                    </P>
                    <HD SOURCE="HD2">Section 1410.326 Transportation Improvement Program Modification </HD>
                    <P>Current § 450.326 would be redesignated as § 1410.326. The only change to this section would be to clarify when a new conformity determination is necessary. The addition of non-exempt projects, or replacement of an existing TIP by a new TIP, requires a new conformity determination. Similarly, moving a project or a phase of a project from year four, five, or later of a TIP to the first three years would be an amendment and require a new conformity determination. We believe that frequent modification of TIPs through the addition of non-exempt projects is inconsistent with the principles of fiscal constraint and public involvement. Hence, we intend to make it clear that a new conformity determination is necessary unless the changes to TIPs are minor, i.e., addition or deletion of exempt projects. </P>
                    <HD SOURCE="HD2">Section 450.328 Transportation Improvement Program Relationship to Statewide TIP </HD>
                    <P>Current § 450.328 would be redesignated as § 1410.328. The text would remain unchanged. </P>
                    <HD SOURCE="HD2">Section 1410.330 Transportation Improvement Program Action by FHWA/FTA </HD>
                    <P>Current § 450.330 would be redesignated as § 1410.330. The provisions of current §§ 450.330(a) and (b) would be redesignated as §§ 1410.330(a) and (b). There would be very minor wording changes for clarification or technical corrections. A new § 1410.330(c) would be added to address the addition of “illustrative projects” to TIPs. This paragraph makes it clear that no Federal action may be taken on these projects until they become formally included in the TIP as indicated previously. </P>
                    <P>Consistent with the overall purposes of the planning process and the need for Federal actions on planning processes and products as appropriate as described in this proposed regulation, project funding is contingent on the existence of a plan and TIP. If a plan and TIP are not updated as required herein, new funding actions cannot be taken. </P>
                    <HD SOURCE="HD2">Section 1410.332 Selecting Projects from a TIP </HD>
                    <P>Current § 450.332 would be redesignated as § 1410.332. Current §§ 450.332(a), (b) and (c) would be redesignated as §§ 1410.332((b), (c) and (a), respectively, with only citation corrections to the text. Proposed §§ 1410.332(d) and (e) (current §§ 450.332(d) and (e), respectively) would include citation corrections and in paragraph (e) the word “will” would become “shall” to reflect the force of law under the CAA. Consistent with previous program practice by the FHWA and the FTA, selecting a project for advancement from year two or three of a TIP does not require a TIP amendment. </P>
                    <HD SOURCE="HD2">Section 1410.334 Certifications </HD>
                    <P>Current § 450.334 would be redesignated as § 1410.334. Current § 450.334(a) would have three new paragraphs (a)(6) through (a)(8) under this proposal. These paragraphs add references to compliance with additional Federal statutes but do not represent new compliance requirements. These requirements previously existed and the regulations would be revised to point out their existence. </P>
                    <P>Paragraph (d) would be revised to clarify the basis for Federal certification actions in relation to Federal findings during the review process. The wording of current paragraph (e) would be the same as the sanctions specified in paragraph (f). Current paragraph (g) would be eliminated to reflect changes made by the TEA-21 (related to the failure to remain certified for two years after October 1994). A new proposed § 1410.334(g) would focus on the new statutory requirement for public involvement during a certification review. We previously required this through administrative directive. Hence, there would be no change in practice, other than to further encourage broad public outreach as part of certification reviews. </P>
                    <HD SOURCE="HD2">Phase-in of New Requirements </HD>
                    <P>No phase-in period for any requirements under the TEA-21 is proposed. Current § 450.336 would be removed. Comments on the desirability of such requirements and the specific areas for which they are warranted are welcome. </P>
                    <HD SOURCE="HD1">Rulemaking Analyses and Notices </HD>
                    <P>All comments received before the close of business on the comment closing date indicated above will be considered and will be available for examination in the docket at the above address. Comments received after the comment closing date will be filed in the docket and will be considered to the extent practicable. In addition to late comments, we will continue to file relevant information in the docket as it becomes available after the comment period closing date, and interested persons should continue to examine the docket for new material. </P>
                    <HD SOURCE="HD1">Executive Order 12866 (Regulatory Planning and Review) and DOT Regulatory Policies </HD>
                    <P>
                        We have determined that this rulemaking is a significant regulatory action within the meaning of Executive Order 12866 and under Department of Transportation regulatory policies and procedures because of substantial State, local government, congressional, and public interest. These interests involve receipt of Federal financial support for transportation investments, appropriate compliance with statutory requirements, and balancing of transportation mobility and environmental goals. This rulemaking is a revision to an existing regulation for which the costs of compliance have previously been addressed. The modifications proposed herein are intended to reduce current regulatory requirements (
                        <E T="03">e.g.,</E>
                         simplification of planning factors, elimination of separate MIS requirement, simplification of planning area boundary establishment, etc.) and to add some additional data analysis requirements (
                        <E T="03">e.g.,</E>
                         elaboration of environmental justice data analyses, preparation of an Intelligent Transportation Systems Integration Strategy, addition of operations and management responsibility, etc.). In preparing this proposal, the agencies have sought to maintain existing flexibility of operation wherever possible for States, MPOs, and other affected organizations and utilize already existing processes to accomplish any new tasks or activities. As a result, we believe that the economic impact of this rulemaking in comparison to the existing regulation should be the same or less. 
                    </P>
                    <P>
                        The marginal additional costs associated with these proposed rules are attributable to the streamlining 
                        <PRTPAGE P="33940"/>
                        provisions of the TEA-21. Achieving the goals of these provisions more efficiently and effectively warrants the regulatory changes proposed herein. Furthermore, we provide substantial financial assistance to States and MPOs to support compliance with the regulatory requirements of this part. Funding for the planning process increased substantially under the TEA-21 and should, we believe, off-set much of the economic impact on entities complying with these requirements. 
                    </P>
                    <P>
                        This proposed rule would revise existing metropolitan planning regulations of the FHWA and the FTA and conform those regulations to requirements of the TEA-21. While they incorporate some new requirements, the bulk of them have been in place for many years and States and metropolitan planning organizations have been implementing them. In the past, we have provided funding to support planning activities and production of required transportation documents, 
                        <E T="03">e.g.</E>
                        , transportation plans and improvement programs. During Fiscal Year 1999, the FHWA will provide in excess of $187 million for metropolitan planning and $492 million for State planning and research activities. The FTA provided $42 million for metropolitan planning. For both agencies, there is a statutory matching grant requirement which stipulates that recipients must match Federal funds at least on an 80 percent Federal, 20 percent recipient basis. To meet the State planning funds matching requirement, States will expend approximately $98 million. The MPOs will have to provide approximately $46 million of non-Federal funds to match the Federal metropolitan planning funds (the FHWA and the FTA funds combined). If the States and other recipient's choose not to accept Federal support for transportation they would not have to develop the plans and programs stipulated in this proposed rule. Hence, the Federal government provides a substantial economic incentive to encourage State and metropolitan planning. In addition, these rules support the EPA conformity regulation at 40 CFR parts 53 and 91 which establishes requirements for MPOs to perform regional transportation and emissions modeling and to document the regional air quality impacts of transportation improvements contained in plans and programs. 
                    </P>
                    <P>The impacts on the States and MPOs result mainly from modified data collection and analysis activities that may be necessary to implement the TEA-21 planning provisions. A single new provision in § 1410.322(b)(11) focuses on the requirements for satisfying section 5206(e) of the TEA-21 regarding demonstrating consistency of Intelligent Transportation Systems projects funded with highway trust fund dollars with the provisions of the National ITS Architecture. The economic impacts of this provision are addressed in the regulatory analysis being prepared for the specific rulemaking on ITS architecture consistency. We anticipate that the elements required in the planning process for ITS consistency would generally be undertaken anyway as a part of the plan development activities and do not require significant new processes or requirements of MPOs and States. </P>
                    <P>In general, we believe that the rule changes proposed here have added limited regulatory requirements. The impact of complying with the changes can be minimized by States and MPOs by using the flexibility provided in the proposed rule to reduce data collection and analysis costs. While there may be additional costs to some States and MPOs, the TEA-21 significantly increased the mandatory set-aside in Federal funds that must be used for transportation planning, and in addition, gives the States and MPOs the flexibility to use Federal capital dollars for transportation planning if they so desire. We are interested in the costs to States and MPOs of complying with the proposed requirements, including the expenditure of State and MPO funds above the required matching amounts. Comments on this matter are welcome. </P>
                    <P>The agencies welcome comment on the economic impacts of these proposed regulations. Comments, including those from the States and MPOs, regarding specific burdens, impacts, and costs would be most welcome and would aid us in more fully appreciating the impacts of this ongoing planning process requirement. Hence, we encourage comments on all facets of this proposal regarding its costs, burden, and impact. </P>
                    <HD SOURCE="HD1">Regulatory Flexibility Act </HD>
                    <P>In compliance with the Regulatory Flexibility Act (Public Law 96-354; 5 U.S.C. 601-612), we have evaluated the effects of these rules on small entities, such as, local governments and businesses. The proposed metropolitan and statewide planning regulations modify existing planning requirements. These modifications are substantially dictated by the statutory provisions of the TEA-21. We believe that the flexibility available to States and MPOs in responding to requirements has been maintained, if not enhanced, in this proposal. Accordingly, the FHWA and the FTA certify that this action would not have a significant economic impact on a substantial number of small entities. </P>
                    <P>We are interested in any comments regarding the potential economic impacts of these proposed rules on small entities and governments. Of specific concern are the additional costs of the incremental changes in our regulatory requirements. The agencies believe that these costs have been off-set largely by reduced statutory requirements and the flexibility built into the regulations. The agencies are requesting comments on these issues. </P>
                    <HD SOURCE="HD1">Executive Order 13132 (Federalism Assessment) </HD>
                    <P>This proposed action has been reviewed in accordance with the principles and criteria contained in Executive Order 13132, dated August 4, 1999, and it has been determined that this action does not have a substantial direct effect or sufficient Federalism implications on States and local governments that would limit the policymaking discretion of the States. Nothing in this document directly preempts any State law or regulation. The TEA-21 and its predecessors authorize the Secretary to implement the provisions for metropolitan and statewide planning. We believe that policies in these proposed rules are consistent with the principles, criteria and requirements of the Federalism Executive Order and the TEA-21. Comments on these conclusions are welcomed and should be submitted to the docket. </P>
                    <HD SOURCE="HD1">Executive Order 12372 (Intergovernmental Review) </HD>
                    <P>Catalog of Federal Domestic Assistance Program Numbers 20.205, Highway planning and Construction (or 20.217); 20.500, Federal Transit Capital Improvement Grants; 20.505, Federal Transit Technical Studies Grants; 20.507, Federal Transit Capital and Operating Assistance Formula Grants. The regulations implementing Executive Order 12372 regarding intergovernmental consultation in Federal programs and activities apply to these programs. </P>
                    <HD SOURCE="HD1">Paperwork Reduction Act </HD>
                    <P>
                        Under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3520), Federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct, sponsor, or require through regulations. We have determined that this proposal contains a requirement for minor additional data 
                        <PRTPAGE P="33941"/>
                        collection to satisfy the provisions of the TEA-21 associated with ITS and environmental justice. The FHWA and the FTA believe that this burden increase has been off-set by decreases in requirements associated with the seven planning factors and related matters. 
                    </P>
                    <P>
                        The reporting requirements for metropolitan UPWPs, transportation plans and transportation improvement programs are currently approved under OMB control number 2132-0529. An extension request was filed with OMB on January 28, 2000, and a Notice of Request for Extension was published in the 
                        <E T="04">Federal Register</E>
                         on April 7, 2000 (65 FR 18421). The analysis supporting this approval was conducted by the FTA on behalf of both the FTA and the FHWA since the regulations are jointly issued by both agencies. The reporting requirements for statewide transportation plans and programs are also approved under this same OMB control number. The information collection requirements addressed under the current OMB approval number (2132-0529) impose a total burden of 241,850 hours on the planning agencies that must comply with the requirements in the existing regulation. We initiated the preparation of materials to obtain a new three year approval from OMB in January 2000. The request for a new data collection approval will be filed with OMB before publication of this NPRM. The FHWA and the FTA are soliciting comments on this NPRM regarding the extent to which any additional burden, beyond that associated with the current collection requirement, will be incurred by States and MPOs. 
                    </P>
                    <P>The creation and submission of required reports and documents have been constrained to those specifically required by the TEA-21 or essential to the performance of our findings, certifications and/or approvals. The State plans are prepared on cycles individually determined by the States; the average is 10 such submissions per year. The State TIPs are prepared every two years. Approximately one third of all metropolitan areas prepare new plans every three years. The remaining metropolitan plans are updated every five years. We have assumed a distribution over several years for the plans. We have assumed that half of all TIPs are submitted annually. We assume an annual submission of unified planning work programs. By distributing the added burden for preparing these various submissions, the net result would be a minimal burden increase for each type of submission. </P>
                    <P>Interested parties are invited to send comments regarding any aspect of this information collection, including, but not limited to: (1) The necessity and utility of the information collection for the proper performance of the functions of the FHWA and the FTA; (2) the accuracy of the estimated burden; (3) ways to enhance the quality, utility, and clarity of the collected information; and (4) ways to minimize the collection burden without reducing the quality of the collected information. Comments submitted in response to the NPRM will be summarized and/or included in the request for OMB's clearance of this information collection. </P>
                    <HD SOURCE="HD1">National Environmental Policy Act </HD>
                    <P>
                        We have analyzed these proposed actions for the purpose of the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                        ). It is our determination this action is consistent with the provisions of 23 CFR 771.117(c)(20) which deems the issuance of regulations of this nature to meet the requirements for a Categorical Exclusion. 
                    </P>
                    <HD SOURCE="HD1">Unfunded Mandates Reform Act of 1995 </HD>
                    <P>
                        This rule does not impose a Federal mandate resulting in the expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100 million in any one year. (2 U.S.C. 1531 
                        <E T="03">et seq.</E>
                        ) 
                    </P>
                    <P>The requirements of 23 U.S.C. 134 and 135 are supported by Federal funds administered by the FHWA and the FTA. There is a legislatively established local matching requirement for these funds of twenty percent of the total project cost. The FHWA and the FTA believe that the costs of complying with these requirements is predominantly covered by the funds they administer. However, as has been the case with previous regulatory issuances, we welcome comments from States, MPOs, transit agencies and other organizations regarding the extent to which the cost of compliance is covered by the funds provided. </P>
                    <HD SOURCE="HD1">Executive Order 12988 (Civil Justice Reform) </HD>
                    <P>This action 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="HD1">Executive Order 13045 (Protection of Children) </HD>
                    <P>We have analyzed this action under Executive Order 13045, protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not concern an environmental risk to health or safety that may disproportionately affect children. </P>
                    <HD SOURCE="HD1">Executive Order 12630 (Taking of Private Property) </HD>
                    <P>This rule will not effect 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="HD1">Regulation Identification Number </HD>
                    <P>A regulation identification number (RIN) is assigned to each regulatory action listed in the Unified Agenda of Federal Regulations. The Regulatory Information Service Center publishes the Unified Agenda in April and October of every year. The RINs contained in the heading of this document can be used to cross-reference this action with the Unified Agenda. </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects </HD>
                    </LSTSUB>
                    <P>23 CFR Parts 450 and 1410 </P>
                    <P>Grant programs—transportation, Highways and roads, Mass transportation, Reporting and recordkeeping requirements.</P>
                    <P>49 CFR Part 613 </P>
                    <P>Grant programs—transportation, Mass transportation, Reporting and recordkeeping requirements. </P>
                    <P>49 CFR Part 621 </P>
                    <P>Grant programs—transportation, Mass transportation, Reporting and recordkeeping requirements. </P>
                    <HD SOURCE="HD1">Federal Highway Administration </HD>
                    <HD SOURCE="HD1">23 CFR Chapter I </HD>
                    <P>For reasons set forth in the preamble, and under the authority of 23 U.S.C. 134, 135, and 315, the FHWA proposes to amend Chapter I of title 23, Code of Federal Regulations, as follows: </P>
                    <PART>
                        <HD SOURCE="HED">PART 450—[REMOVED] </HD>
                        <P>1. Remove part 450. </P>
                        <HD SOURCE="HD1">23 CFR Chapter IV </HD>
                        <P>
                            2. For reasons set forth in the preamble, the Federal Highway Administration and the Federal Transit Administration propose to establish a new chapter IV in title 23, Code of Federal Regulations, consisting of part 1410 as set forth below: 
                            <PRTPAGE P="33942"/>
                        </P>
                    </PART>
                    <CHAPTER>
                        <HD SOURCE="HED">CHAPTER IV—FEDERAL HIGHWAY ADMINISTRATION AND FEDERAL TRANSIT ADMINISTRATION, DEPARTMENT OF TRANSPORTATION </HD>
                        <PART>
                            <HD SOURCE="HED">PART 1410—METROPOLITAN AND STATEWIDE PLANNING </HD>
                            <CONTENTS>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart A—Definitions </HD>
                                    <SECHD>Sec. </SECHD>
                                    <SECTNO>1410.100 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <SECTNO>1410.102 </SECTNO>
                                    <SUBJECT>Applicability. </SUBJECT>
                                    <SECTNO>1410.104 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart B—Statewide Transportation Planning and Programming </HD>
                                    <SECTNO>1410.200 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <SECTNO>1410.202 </SECTNO>
                                    <SUBJECT>Applicability. </SUBJECT>
                                    <SECTNO>1410.204 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <SECTNO>1410.206 </SECTNO>
                                    <SUBJECT>Statewide transportation planning process basic requirements. </SUBJECT>
                                    <SECTNO>1410.208 </SECTNO>
                                    <SUBJECT>Consideration of statewide transportation planning factors. </SUBJECT>
                                    <SECTNO>1410.210 </SECTNO>
                                    <SUBJECT>Coordination of planning process activities. </SUBJECT>
                                    <SECTNO>1410.212 </SECTNO>
                                    <SUBJECT>Participation by interested parties. </SUBJECT>
                                    <SECTNO>1410.214 </SECTNO>
                                    <SUBJECT>Content and development of statewide transportation plan. </SUBJECT>
                                    <SECTNO>1410.216 </SECTNO>
                                    <SUBJECT>Content and development of statewide transportation improvement program. </SUBJECT>
                                    <SECTNO>1410.218 </SECTNO>
                                    <SUBJECT>Relation of planning and project development processes. </SUBJECT>
                                    <SECTNO>1410.220 </SECTNO>
                                    <SUBJECT>Funding of planning process. </SUBJECT>
                                    <SECTNO>1410.222 </SECTNO>
                                    <SUBJECT>Approvals, self-certification and findings. </SUBJECT>
                                    <SECTNO>1410.224 </SECTNO>
                                    <SUBJECT>Project selection. </SUBJECT>
                                    <SECTNO>1410.226 </SECTNO>
                                    <SUBJECT>Applicability of NEPA to transportation planning and programming. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart C—Metropolitan Transportation Planning and Programming </HD>
                                    <SECTNO>1410.300 </SECTNO>
                                    <SUBJECT>Purpose of planning process. </SUBJECT>
                                    <SECTNO>1410.302 </SECTNO>
                                    <SUBJECT>Organizations and processes affected by planning requirements. </SUBJECT>
                                    <SECTNO>1410.304 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <SECTNO>1410.306 </SECTNO>
                                    <SUBJECT>What is a Metropolitan Planning Organization and how is it created? </SUBJECT>
                                    <SECTNO>1410.308 </SECTNO>
                                    <SUBJECT>Establishing the geographic boundaries for metropolitan transportation planning areas. </SUBJECT>
                                    <SECTNO>1410.310 </SECTNO>
                                    <SUBJECT>Agreements among organizations involved in the planning process. </SUBJECT>
                                    <SECTNO>1410.312 </SECTNO>
                                    <SUBJECT>Planning process organizational relationships. </SUBJECT>
                                    <SECTNO>1410.314 </SECTNO>
                                    <SUBJECT>Planning tasks and unified work program. </SUBJECT>
                                    <SECTNO>1410.316 </SECTNO>
                                    <SUBJECT>Transportation planning process and plan development. </SUBJECT>
                                    <SECTNO>1410.318 </SECTNO>
                                    <SUBJECT>Relation of planning and project development processes. </SUBJECT>
                                    <SECTNO>1410.320 </SECTNO>
                                    <SUBJECT>Congestion management system and planning process. </SUBJECT>
                                    <SECTNO>1410.322 </SECTNO>
                                    <SUBJECT>Transportation plan content. </SUBJECT>
                                    <SECTNO>1410.324 </SECTNO>
                                    <SUBJECT>Transportation improvement program content. </SUBJECT>
                                    <SECTNO>1410.326 </SECTNO>
                                    <SUBJECT>Transportation improvement program modification. </SUBJECT>
                                    <SECTNO>1410.328 </SECTNO>
                                    <SUBJECT>Metropolitan transportation improvement program relationship to statewide TIP. </SUBJECT>
                                    <SECTNO>1410.330 </SECTNO>
                                    <SUBJECT>Transportation improvement program action by FHWA/FTA. </SUBJECT>
                                    <SECTNO>1410.332 </SECTNO>
                                    <SUBJECT>Selecting projects from a TIP. </SUBJECT>
                                    <SECTNO>1410.334 </SECTNO>
                                    <SUBJECT>Federal certifications. </SUBJECT>
                                </SUBPART>
                            </CONTENTS>
                            <AUTH>
                                <HD SOURCE="HED">Authority:</HD>
                                <P>
                                    23 U.S.C. 134, 135, 315; 42 U.S.C. 7410 
                                    <E T="03">et seq.</E>
                                    ; 49 U.S.C. 5303-5305; 49 CFR 1.48 and 1.51. 
                                </P>
                            </AUTH>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart A  Definitions </HD>
                                <SECTION>
                                    <SECTNO>§ 1410.100 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <P>The purpose of this subpart is to provide definitions for terms used in this part which go beyond those terms defined in 23 U.S.C. 101(a) and 49 U.S.C. 5302. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.102 </SECTNO>
                                    <SUBJECT>Applicability. </SUBJECT>
                                    <P>The definitions in this subpart are applicable to this part, except as otherwise provided. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.104 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <P>Except as defined in this subpart, terms defined in 23 U.S.C. 101(a) and 49 U.S.C. 5302 are used in this part as so defined. </P>
                                    <P>
                                        <E T="03">Conformity lapse</E>
                                         means that the conformity determination for a transportation plan or TIP has expired, and thus there is no currently conforming transportation plan and TIP. 
                                    </P>
                                    <P>
                                        <E T="03">Conformity rule</E>
                                         means the EPA Transportation Conformity Rule, as amended, 40 CFR parts 51 and 93. 
                                    </P>
                                    <P>
                                        <E T="03">Congestion management system</E>
                                         means a systematic process for managing congestion that provides information on transportation system performance and on alternative strategies for alleviating congestion and enhancing the mobility of persons and goods to levels that meet State and local needs. 
                                    </P>
                                    <P>
                                        <E T="03">Consultation</E>
                                         means that one party confers with another party, in accordance with an established process, about an anticipated action and then keeps that party informed about actions taken. 
                                    </P>
                                    <P>
                                        <E T="03">Cooperation</E>
                                         means that the parties involved in carrying out the planning and/or project development processes work together to achieve a common goal or objective. 
                                    </P>
                                    <P>
                                        <E T="03">Coordination</E>
                                         means the comparison of the transportation plans, programs, and schedules of one agency with related plans, programs and schedules of other agencies and adjustment of plans, programs and schedules to achieve general consistency. 
                                    </P>
                                    <P>
                                        <E T="03">Design concept</E>
                                         means the type of facility identified by the project, e.g., freeway, expressway, arterial highway, grade-separated highway, reserved right-of-way rail transit, mixed-traffic rail transit, exclusive busway, etc. 
                                    </P>
                                    <P>
                                        <E T="03">Design scope</E>
                                         means the design aspects which will affect the proposed facility's impact on regional emissions, usually as they relate to vehicle or person carrying capacity and control, e.g., number of lanes or tracks to be constructed or added, length of project, signalization, access control including approximate number and location of interchanges, preferential treatment for high-occupancy vehicles, etc. 
                                    </P>
                                    <P>
                                        <E T="03">Federally funded non-emergency transportation services</E>
                                         means transportation services provided to the general public, including those with special transport needs, by public transit, private non-profit service providers, and private third-party contractors to public agencies. 
                                    </P>
                                    <P>
                                        <E T="03">Financial estimate</E>
                                         means a projection of Federal and State resources that will serve as a basis for developing plans and /or TIPs. 
                                    </P>
                                    <P>
                                        <E T="03">Freight shipper</E>
                                         means an entity that utilizes a freight carrier in the movement of its goods. 
                                    </P>
                                    <P>
                                        <E T="03">Governor</E>
                                         means the Governor of any one of the fifty States, or Puerto Rico, and includes the Mayor of the District of Columbia. 
                                    </P>
                                    <P>
                                        <E T="03">Illustrative project</E>
                                         means a transportation improvement that would be included in a financially constrained transportation plan and program if reasonable additional financial resources were available to support it. 
                                    </P>
                                    <P>
                                        <E T="03">Indian Tribal Government</E>
                                         means a duly formed governing body of an Indian or Alaska Native tribe, band, nation, pueblo, village, or community that the Secretary of the Interior acknowledges to exist as an Indian tribe pursuant to the Federally Recognized Indian Tribe List Act of 1994, 25 U.S.C. 479a. 
                                    </P>
                                    <P>
                                        <E T="03">Interim plan</E>
                                         means a plan composed of projects eligible to proceed under a conformity lapse (as defined in 40 CFR parts 51 and 93) and otherwise meeting all other provisions of this part including adoption by the MPOs. 
                                    </P>
                                    <P>
                                        <E T="03">Interim transportation improvement program</E>
                                         means a TIP composed of projects eligible to proceed under a conformity lapse (as defined in 40 CFR parts 51 and 93 ) and otherwise meeting all other provisions of this part including approval by the Governor. 
                                    </P>
                                    <P>
                                        <E T="03">ITS integration strategy</E>
                                         means a systematic approach for coordinating and implementing intelligent transportation system investments funded with Federal highway trust funds to achieve an integrated regional system. 
                                    </P>
                                    <P>
                                        <E T="03">Maintenance area</E>
                                         means any geographic region of the United States previously designated nonattainment pursuant to the Clean Air Act Amendments of 1990 (CAA) and subsequently redesignated to attainment subject to the requirement to develop a maintenance plan under section 175A of the CAA, as amended. 
                                        <PRTPAGE P="33943"/>
                                    </P>
                                    <P>
                                        <E T="03">Management and operation</E>
                                         means actions and strategies aimed at improving the person, vehicle and/or freight carrying capacity, safety, efficiency and effectiveness of the existing and future transportation system to enhance mobility and accessibility in the area served. 
                                    </P>
                                    <P>
                                        <E T="03">Metropolitan planning area</E>
                                         means the geographic area in which the metropolitan transportation planning process required by 23 U.S.C. 134 and 49 U.S.C. 5303-5306 must be carried out. 
                                    </P>
                                    <P>
                                        <E T="03">Metropolitan planning organization (MPO)</E>
                                         means the forum for cooperative transportation decision making for the metropolitan planning area pursuant to 23 U.S.C. 134 and 49 U.S.C. 5303. 
                                    </P>
                                    <P>
                                        <E T="03">Metropolitan transportation plan</E>
                                         means the official intermodal transportation plan that is developed and adopted through the metropolitan transportation planning process for the metropolitan planning area, in accordance with 23 U.S.C. 134 and 135 and 49 U.S.C. 5303. 
                                    </P>
                                    <P>
                                        <E T="03">Nonattainment area</E>
                                         means any geographic region of the United States which has been designated as nonattainment under section 107 of the CAA for any pollutant for which a national ambient air quality standard exists. 
                                    </P>
                                    <P>
                                        <E T="03">Non-metropolitan local official</E>
                                         means elected or appointed officials of general purpose local government, outside metropolitan planning areas, with jurisdiction/responsibility for transportation or other community development actions that impact transportation and elected officials for special transportation and planning agencies, such as economic development districts and land use planning agencies. 
                                    </P>
                                    <P>
                                        <E T="03">Provider of freight transportation services</E>
                                         means a shipper or carrier which transports or otherwise facilitates the movement of goods from one point to another. 
                                    </P>
                                    <P>
                                        <E T="03">Purpose and need</E>
                                         means the intended outcome and sustaining rationale for a proposed transportation improvement, including, but not limited, to mobility deficiencies for identified populations and geographic areas. 
                                    </P>
                                    <P>
                                        <E T="03">Regionally significant project</E>
                                         means a transportation project (other than an exempt project) that is on a facility which serves regional transportation needs (such as access to and from the area outside of the region, major activity centers in the region, major planned developments such as new retail malls, sports complexes, etc., or transportation terminals as well as most terminals themselves) and would normally be included in the modeling of a metropolitan area's transportation network, including at a minimum all principal arterial highways and all fixed guideway transit facilities that offer an alternative to regional highway travel. 
                                    </P>
                                    <P>
                                        <E T="03">State</E>
                                         means any one of the fifty States, the District of Columbia, or Puerto Rico. 
                                    </P>
                                    <P>
                                        <E T="03">State implementation plan (SIP)</E>
                                         means: 
                                    </P>
                                    <P>(1) The implementation plan which contains specific strategies for controlling emissions of and reducing ambient levels of pollutants in order to satisfy Clean Air Act (CAA) requirements for demonstrations of reasonable further progress and attainment (CAA secs. 182(b)(1), 182(c)(2)(A), 182(c)(2)(B), 187(a)(7), 189(a)(1)(B), and 189(b)(1)(A); and secs.192(a) and 192(b), for nitrogen dioxide of the CAA); or </P>
                                    <P>(2) The implementation plan under section 175A of the CAA as amended. </P>
                                    <P>
                                        <E T="03">Statewide transportation improvement program (STIP)</E>
                                         means a staged, multi-year, statewide, intermodal program of transportation projects which is consistent with the statewide transportation plan and planning processes and metropolitan plans, TIPs and processes pursuant to 23 U.S.C. 135. 
                                    </P>
                                    <P>
                                        <E T="03">Statewide transportation improvement program (STIP) extension</E>
                                         means the lengthening of the scheduled duration of an existing STIP, including the component metropolitan TIPs included in the STIP, beyond two years by joint administrative action of the FHWA and the FTA. STIP extensions are not allowed for metropolitan TIP portions of the STIP which are in nonattainment or maintenance areas as well as for those portions of the STIP containing projects in rural nonattainment or maintenance areas. 
                                    </P>
                                    <P>
                                        <E T="03">Statewide transportation plan</E>
                                         means the official statewide, intermodal transportation plan that is developed through the statewide transportation planning process pursuant to 23 U.S.C. 135. 
                                    </P>
                                    <P>
                                        <E T="03">TIP update</E>
                                         means the periodic re-examination and revision of TIP contents, including, but not limited to, non-exempt projects, on a scheduled basis, normally at least every two years. The addition or deletion of a non-exempt project or phase of a non-exempt project to a TIP shall be based on a comprehensive update of the TIP. 
                                    </P>
                                    <P>
                                        <E T="03">Transportation control measure</E>
                                         means any measure that is specifically identified and committed to in the applicable implementation plan that is either one of the types listed in section 108 of the CAA, or any other measure for the purpose of reducing emissions or concentrations of air pollutants from transportation sources by reducing vehicle use or changing traffic flow or congestion conditions. Notwithstanding the above, vehicle technology-based, fuel-based, and maintenance-based measures which control the emissions from vehicles under fixed traffic conditions are not TCMs. 
                                    </P>
                                    <P>
                                        <E T="03">Transportation improvement program (TIP)</E>
                                         means a staged, multi-year, intermodal program of transportation projects in the metropolitan planning area which is consistent with the metropolitan transportation plan. 
                                    </P>
                                    <P>
                                        <E T="03">Transportation Management Area (TMA)</E>
                                         means an urbanized area with a population over 200,000 (as determined by the latest decennial census) or other area when TMA designation is requested by the Governor and the MPO (or affected local officials), and officially designated by the Administrators of the FHWA and the FTA. The TMA designation applies to the entire metropolitan planning area(s). 
                                    </P>
                                    <P>
                                        <E T="03">Transportation plan update</E>
                                         means the periodic review, revision or reaffirmation of plan content, normally every three years in nonattainment and maintenance areas and five years in attainment areas or the update period for State plans as determined by the State. 
                                    </P>
                                    <P>
                                        <E T="03">Twenty year planning horizon</E>
                                         means a forecast period covering twenty years from the date of plan adoption, reaffirmation or modification in attainment areas and subsequent Federal conformity finding at the time of adoption in nonattainment and maintenance areas. The plan must reflect the most recent planning assumptions for current and future population, travel, land use, congestion, employment, economic activity and other related statistical measures for the metropolitan planning area. 
                                    </P>
                                    <P>
                                        <E T="03">Urbanized area (UZA)</E>
                                         means a geographic area with a population of at least 50,000 as designated by the U.S. Department of Commerce, Bureau of the Census based on the latest decennial census or special census as appropriate. 
                                    </P>
                                    <P>
                                        <E T="03">User of public transit</E>
                                         means any person or group representing such persons who use mass transportation open to the public other than taxis and other privately operated vehicles. 
                                    </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart B—Statewide Transportation Planning and Programming </HD>
                                <SECTION>
                                    <SECTNO>§ 1410.200 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <P>
                                        The purpose of this subpart is to implement 23 U.S.C. 135, which requires each State to carry out a transportation planning process that shall be continuing, cooperative, and 
                                        <PRTPAGE P="33944"/>
                                        comprehensive to the degree appropriate, based on the complexity of the transportation problems to be addressed. The transportation planning process shall be intermodal and shall develop a statewide transportation plan and transportation improvement program for all areas of the State, including those areas subject to the requirements of 23 U.S.C. 134 and 49 U.S.C. 5303-5305. The plan and program shall facilitate the development and integrated management and operation of safe transportation systems and facilities (including pedestrian walkways and bicycle transportation facilities) that will function as an intermodal transportation system for the State and an integral part of an intermodal transportation system for the United States. The intermodal transportation system shall provide for safe, efficient, economic movement of people and goods in all areas of the State and foster economic growth and development while minimizing transportation-related fuel consumption and air pollution. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.202 </SECTNO>
                                    <SUBJECT>Applicability. </SUBJECT>
                                    <P>The provisions of this subpart are applicable to States and any other agencies/organizations, such as MPOs, transit operators and air quality agencies, that are responsible for satisfying these requirements for transportation planning, programming and project development throughout the State pursuant to 23 U.S.C. 135. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.204 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <P>Except as otherwise provided in subpart A of this part, terms defined in 23 U.S.C. 101(a) are used in this part as so defined. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.206 </SECTNO>
                                    <SUBJECT>Statewide transportation planning process basic requirements. </SUBJECT>
                                    <P>(a) The statewide transportation planning process shall include, as a minimum, the following: </P>
                                    <P>(1) Data collection and analysis; </P>
                                    <P>(2) Consideration of factors contained in § 1410.208; </P>
                                    <P>(3) Coordination of activities as noted in § 1410.210; </P>
                                    <P>
                                        (4) Development of a statewide transportation plan for all areas of the State that considers a range of transportation options designed to meet the transportation needs (
                                        <E T="03">e.g.,</E>
                                         passenger, freight, safety, etc.) of the State including all modes and their connections; 
                                    </P>
                                    <P>(5) Development of a statewide transportation improvement program (STIP) for all areas of the State; and </P>
                                    <P>(6) Various processes to accomplish data collection and analyses essential for an effective transportation planning process, including a process to assure that, no person shall, on the grounds of race, color, sex, national origin, age, or physical handicap, be excluded from participation in, be denied benefits of, or be otherwise subjected to discrimination under any program or activity receiving Federal assistance from the U.S. Department of Transportation. These assurances shall be demonstrated through the following: </P>
                                    <P>(i) An assessment covering the State, including at a minimum the following: </P>
                                    <P>(A) A geographic and demographic profile of the State that identifies the low-income and minority, and where appropriate, elderly and persons with disabilities, components of this profile; </P>
                                    <P>(B) The transportation services available to or planned for these segments of the State population; </P>
                                    <P>
                                        (C) Any disproportionately high and adverse environmental effects, including interrelated social and economic effects, consistent with the provisions of Executive Order 12898 (59 FR 7629, 3 CFR, 1995 comp., p. 859) as implemented through US DOT Order 5610.2 and FHWA Order 6640.23; 
                                        <SU>1</SU>
                                        <FTREF/>
                                         and
                                    </P>
                                    <FTNT>
                                        <P>
                                            <SU>1</SU>
                                             DOT order 5610.2 and FHWA order 6640.23 are available for inspection and copying from DOT headquarters and field offices as prescribed at 49 CFR part 7.
                                        </P>
                                    </FTNT>
                                    <P>(D) Any denial of or a reduction in benefits; </P>
                                    <P>(ii) Consideration of comments received during public involvement efforts (consistent with the provisions of § 1410.212(b)) to ensure that expressed concerns of the elderly, minority individuals and persons with disabilities, have been addressed during plan and program decision making; </P>
                                    <P>(iii) Identification of prior and planned efforts to address any disproportionately high and adverse effects that are found; </P>
                                    <P>(iv) The results of paragraphs (a)(5)(i), (ii) and (iii) of this section will be documented in a manner to permit public review during appropriate project development activities; </P>
                                    <P>(v) The State may rely on information provided by a metropolitan planning organization for those segments of the population in metropolitan planning areas of the State; and </P>
                                    <P>(vi) In accordance with Executive Order 12898, DOT Order 5610.2, and FHWA Order 6640.23, nothing in paragraphs (a)(5)(i) through (vi) of this section are intended to nor shall they create any right to judicial review of any action taken by the agency, its officers or its recipients taken under this part to comply with such Orders. </P>
                                    <P>(b) [Reserved]. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.208 </SECTNO>
                                    <SUBJECT>Consideration of statewide transportation planning factors. </SUBJECT>
                                    <P>(a) Each statewide transportation planning process shall provide for consideration of projects and strategies that will: </P>
                                    <P>(1) Support the economic vitality of the United States, the States, and metropolitan areas, especially by enabling global competitiveness, productivity and efficiency; </P>
                                    <P>(2) Increase the safety and security of the transportation system for motorized and nonmotorized users; </P>
                                    <P>(3) Increase the accessibility and mobility options available to people and for freight; </P>
                                    <P>(4) Protect and enhance the environment, promote energy conservation, and improve quality of life; </P>
                                    <P>(5) Enhance the integration and connectivity of the transportation system, across and between modes throughout the State, for people and freight; </P>
                                    <P>(6) Promote efficient system management and operation; and </P>
                                    <P>(7) Emphasize the preservation of the existing transportation system. </P>
                                    <P>(b) In addition, in carrying out statewide transportation planning, the State shall consider, at a minimum, the following and other factors and issues that the planning process participants might identify which are important considerations within the statewide transportation planning process: </P>
                                    <P>(1) With respect to nonmetropolitan areas, the concerns of local elected officials representing units of general purpose local government; and </P>
                                    <P>(2) The concerns of Indian Tribal Governments and Federal land management agencies that have jurisdiction over land within the boundaries of the State. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.210 </SECTNO>
                                    <SUBJECT>Coordination of planning process activities. </SUBJECT>
                                    <P>(a) The statewide transportation planning process shall be carried out in coordination with adjacent States, adjacent countries as appropriate at the international borders, and with the metropolitan planning process required by subpart C of this part. </P>
                                    <P>
                                        (b) The statewide transportation planning process shall be coordinated with air quality planning and provide for appropriate conformity analyses to the extent required by the Clean Air Act (40 U.S.C. 175 and 176). The State shall carry out its responsibilities for the development of the transportation portion of the State Implementation Plan to the extent required by the Clean Air Act (42 U.S.C. 7504), as appropriate within the statewide transportation planning process. 
                                        <PRTPAGE P="33945"/>
                                    </P>
                                    <P>(c) Development of transportation plans, programs and planning activities shall be coordinated with related planning activities being carried out outside of metropolitan planning areas. </P>
                                    <P>(d) The statewide transportation planning process shall provide a forum for coordinating data collection and analyses to support, planning, programming and project development decisions. </P>
                                    <P>(e) The degree of coordination shall be based on the scale and complexity of many issues including transportation problems, safety concerns, land use, employment, economic, environmental, and housing and community development objectives, and other circumstances statewide or in subareas within the State. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.212 </SECTNO>
                                    <SUBJECT>Participation by interested parties. </SUBJECT>
                                    <P>(a) Non-metropolitan local official participation. </P>
                                    <P>(1) The State shall have a documented process for consultation with local officials in non-metropolitan areas within the continuing, cooperative and comprehensive planning process for development of the statewide transportation plan and the statewide transportation improvement program. The process shall be documented and cooperatively developed by both the State and nonmetropolitan local officials. </P>
                                    <P>(2) The process for participation of nonmetropolitan local officials shall not be reviewed or approved by the FHWA and the FTA. However, local official participation will be among the issues considered by the FHWA and the FTA in making the transportation planning finding called for in § 1410.222(b). </P>
                                    <P>(b) Public involvement. </P>
                                    <P>(1) Public involvement processes shall be open and proactive by providing complete information, timely public notice, full public access to key decisions, and opportunities for early and continuing involvement. </P>
                                    <P>(2) To satisfy these objectives public involvement processes shall provide for: </P>
                                    <P>(i) Early and continuing public involvement opportunities throughout the transportation planning and programming process; and </P>
                                    <P>(ii) Timely information about transportation issues and processes to citizens, affected public agencies, representatives of transportation agency employees, private providers of transportation, freight shippers, providers of freight transportation services, representatives of users of public transit, and other interested parties and segments of the community affected by transportation plans, programs, and projects; </P>
                                    <P>(iii) Reasonable public access to technical and policy information used in the development of the plan and STIP; </P>
                                    <P>(iv) Adequate public notice of public involvement activities and time for public review and comment at key decision points, including, but not limited, to action on the plan and STIP; </P>
                                    <P>(v) A process for demonstrating explicit consideration and response to public input during the planning and program development process, including responses to input received from persons with disabilities and minority, elderly, and low-income populations; </P>
                                    <P>(vi) A process for seeking out and considering the needs of those traditionally under served by existing transportation systems, including, but not limited to, low-income and minority populations which may face challenges accessing employment and other amenities; </P>
                                    <P>(vii) Periodic review of the effectiveness of the public involvement process to ensure that the process provides full and open access to all and revision of the process as necessary, with specific attention to the effectiveness of efforts to engage persons with disabilities, minority individuals, the elderly and low-income populations. </P>
                                    <P>(3) Public involvement activities carried out in a metropolitan area in response to metropolitan planning requirements in § 1410.322(c) or § 1410.324(c) may by agreement of the State and the MPO satisfy the requirements of this section. </P>
                                    <P>(4) During initial development and major revisions of the statewide transportation plan required under § 1410.214, the State shall provide citizens, affected public agencies and jurisdictions, representatives of transportation agency employees, private and public providers of transportation, representatives of users of public transit, freight shippers providers of freight transportation services and other interested parties a reasonable opportunity to comment on the proposed plan. The proposed plan shall be published, with reasonable notification of its availability, or otherwise made readily available for public review and comment. Likewise, the official statewide transportation plan (see § 1410.214(d)) shall be published, with reasonable notification of its availability, or otherwise made readily available for public information. </P>
                                    <P>(5) During development and major revision of the statewide transportation improvement program required under § 1410.216, the Governor shall provide citizens, affected public agencies and jurisdictions, representatives of transportation agency employees, private and public providers of transportation, representatives of users of public transit, freight shippers, providers of freight transportation services and other interested parties, a reasonable opportunity for review and comment on the proposed program. The proposed program shall be published, with reasonable notification of its availability, or otherwise made readily available for public review and comment. The approved program (see § 1410.222(b)) if it differs significantly from the proposed program, shall be published, with reasonable notification of its availability, or otherwise made readily available for public information. </P>
                                    <P>(6) The time provided for public review and comment for minor revisions to the statewide transportation plan or statewide transportation improvement program shall be determined by the State and local officials based on the complexity of the revisions. </P>
                                    <P>(7) The State shall, as appropriate, provide for public comment on existing and proposed procedures for public involvement throughout the statewide transportation planning and programming process. As a minimum, the State shall publish procedures and allow 45 days for public review and written comment before the procedures and any major revisions to existing procedures are adopted. </P>
                                    <P>(c) Federal agency and other government participation. The transportation planning process shall allow for participation of other governments and agencies, particularly Indian Tribal Governments and Federal lands managing agencies. The process for consulting with Indian Tribal Governments and Federal lands managing agencies shall be cooperatively developed and documented by both the State and the Indian Tribal Government(s) or the respective Federal lands managing agency. </P>
                                    <P>(d) State air quality agency and other state agency participation. The transportation planning process shall allow for participation of the State air quality agency and other state agencies as determined appropriate by the planning process participants. </P>
                                    <P>
                                        (e) Participation and the planning finding. The processes for participation of interested parties will be considered by the FHWA and the FTA as they make the planning finding required in § 1410.222(b) to assure that full and 
                                        <PRTPAGE P="33946"/>
                                        open access is provided to the decision making process. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.214 </SECTNO>
                                    <SUBJECT>Content and development of statewide transportation plan. </SUBJECT>
                                    <P>(a) The State shall develop a statewide transportation plan that shall: </P>
                                    <P>(1) Cover all areas of the State; </P>
                                    <P>(2) Be intermodal (including consideration and provision, as applicable, of elements and connections of and between transit, non-motorized, rail, commercial motor vehicle, waterway, and aviation facilities, particularly with respect to intercity travel) and statewide in scope in order to facilitate the safe and efficient movement of people and goods; </P>
                                    <P>(3) Address the development of intelligent transportation systems (ITS) investment strategies, including an ITS Integration Strategy consistent with the provisions of § 1410.322(b)(11), to support the development of integrated technology based investments, including metropolitan and non-metropolitan investments. The scope of the integration strategy shall be appropriate to the scale of investment anticipated for ITS during the life of the plan and shall address the level of resources and staging of planned investments. ITS Integration Strategy shall be developed and documented no later than the first update of the transportation plan or STIP that occurs two years following the effective date of the final rule; </P>
                                    <P>(4) Be reasonably consistent in time horizon among its elements, but cover a forecast period of at least 20 years; </P>
                                    <P>(5) Provide for development and integrated management and operation of bicycle and pedestrian transportation system and facilities which are appropriately interconnected with other modes; </P>
                                    <P>(6) Be coordinated with the metropolitan transportation plans required under 23 U.S.C. 134 and 49 U.S.C. 5303; </P>
                                    <P>(7) Reference, summarize or contain any applicable short range planning studies, strategic planning and/or policy studies, transportation needs studies, management system reports and any statements of policies, goals and objectives regarding issues, such as, transportation, economic development, housing, social and environmental effects, energy, etc., that were significant to development of the plan; </P>
                                    <P>(8) Reference, summarize or contain information on the availability of financial (including as appropriate an optional financial plan consistent with 23 CFR 1410.214(d)) and other resources needed to carry out the plan; and </P>
                                    <P>(9) Contain strategies that ensure timely compliance with the applicable SIP. </P>
                                    <P>(b) The following entities shall be involved in the development of the statewide transportation plan: </P>
                                    <P>(1) MPOs shall be involved on a cooperation basis for the portions of the plan affecting metropolitan planning areas; </P>
                                    <P>(2) Indian Tribal Governments and the Secretary of the Interior shall be involved on a consultation basis for the portions of the plan affecting areas of the State under the jurisdiction of an Indian Tribal Government; </P>
                                    <P>(3) Federal lands managing agencies shall be involved on a consultation basis for the portions of the program affecting areas of the State under their jurisdiction; </P>
                                    <P>(4) Affected local officials with responsibility for transportation shall be involved on a consultation basis for the portions of the plan in nonmetropolitan areas of the State. </P>
                                    <P>(c) In developing the statewide transportation plan, the State shall: </P>
                                    <P>(1) Provide for participation by interested parties as required under § 1410.212; </P>
                                    <P>(2) Provide for consideration and analysis as appropriate of specified factors as required under § 1410.208; </P>
                                    <P>(3) Provide for coordination as required under § 1410.210; and </P>
                                    <P>(4) Identify transportation strategies necessary to efficiently serve the mobility needs of people. </P>
                                    <P>(d) The statewide transportation plan may include a financial plan that: </P>
                                    <P>(1) Demonstrates how the adopted transportation plan can be implemented; </P>
                                    <P>(2) Indicates resources from public and private sources that are reasonably expected to be made available to carry out the plan; </P>
                                    <P>(3) Recommends any additional financing strategies for needed projects and programs; </P>
                                    <P>(4) Might include, for illustrative purposes, additional projects that would be included in the adopted transportation plan if reasonable additional resources beyond those identified in the financial plan were available. The State is not required to select any project from the illustrative list for implementation, and projects on the illustrative list cannot be advanced to implementation without an action by the Secretary of Transportation on the STIP. </P>
                                    <P>(e) The State shall provide and carry out a mechanism to adopt the plan as the official statewide transportation plan. </P>
                                    <P>(f) The plan shall be continually evaluated and periodically updated, as appropriate, using the procedures in this section for development and establishment of the plan. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.216 </SECTNO>
                                    <SUBJECT>Content and development of statewide transportation improvement program (STIP). </SUBJECT>
                                    <P>
                                        (a) Each State shall develop a statewide transportation improvement program for all areas of the State. In case of difficulties in developing the STIP portion for a particular area, 
                                        <E T="03">e.g.,</E>
                                         metropolitan area, Indian Tribal lands, etc., a partial STIP covering the rest of the State may be developed. The portion of the STIP in a metropolitan planning area (the metropolitan TIP developed pursuant to subpart C of this part) shall be developed in cooperation with the MPO. To assist metropolitan TIP development the State, the MPO and the transit operator will cooperatively develop timely estimates of available Federal and State funds which are to be utilized in developing the metropolitan TIP. Metropolitan planning area TIPs shall be included without modification in the STIP, directly or by reference, once approved by the MPO and the Governor and after needed conformity findings are made. Metropolitan TIPs in nonattainment and maintenance areas are subject to the FHWA and the FTA conformity findings before their inclusion in the STIP. In nonattainment and maintenance areas outside metropolitan planning areas, Federal findings of conformity must be made prior to placing projects in the STIP. The State shall notify the appropriate MPO, local jurisdictions, Federal land management agency, Indian Tribal Government, etc., when a TIP including projects under the jurisdiction of the agency has been included in the STIP. All title 23 U.S.C. and 49 U.S.C. Chapter 53 fund recipients will share information as projects in the STIP are implemented. The Governor shall provide for participation of interested parties in development of the STIP as required by § 1410.212. 
                                    </P>
                                    <P>(b) The following entities shall be involved in the development of the statewide transportation improvement program: </P>
                                    <P>(1) MPOs shall be involved on a cooperation basis for the portions of the program affecting metropolitan planning areas; </P>
                                    <P>(2) Indian Tribal Governments and the Secretary of the Interior shall be involved on a consultation basis for the portions of the program affecting areas of the State under the jurisdiction of an Indian Tribal Government; </P>
                                    <P>
                                        (3) Federal lands managing agencies shall be involved on a consultation basis for the portions of the program affecting 
                                        <PRTPAGE P="33947"/>
                                        areas of the State under their jurisdiction; and 
                                    </P>
                                    <P>(4) Affected local officials with responsibility for transportation shall be involved on a consultation basis for the portions of the program in nonmetropolitan areas of the State. </P>
                                    <P>(c) The STIP shall: </P>
                                    <P>
                                        (1) Include a list of priority transportation projects proposed to be carried out in the first three years of the STIP. Since each TIP is approved by the Governor, the TIP priorities will dictate STIP priorities for each individual metropolitan area. As a minimum, the lists shall group the projects that are to be undertaken in each of the years, 
                                        <E T="03">e.g.,</E>
                                         year 1, year 2, year 3; 
                                    </P>
                                    <P>(2) Cover a period of not less than three years, but may at State discretion cover a longer period. If the STIP covers more than three years, the projects in the additional years will be considered by the FHWA and the FTA only as informational; </P>
                                    <P>(3) Contain only projects consistent with the statewide plan developed under § 1410.214; </P>
                                    <P>(4) In nonattainment and maintenance areas, contain only transportation projects that have been found to conform, or which come from programs that conform, in accordance with the requirements contained in the EPA conformity regulation 40 CFR parts 51 and 93; </P>
                                    <P>(5) Contain a project, or an identified phase of a project, only if full funding can reasonably be anticipated to be available for the project within the time period contemplated for completion of the project. The STIP financial constraint will be demonstrated and maintained by year and the STIP shall include sufficient financial information to demonstrate which projects are to be implemented using current revenues and which projects are to be implemented using proposed revenue sources while the system as a whole is being adequately operated and maintained. In nonattainment and maintenance areas, projects included in the first two years of the current STIP/TIP shall be limited to those for which funds are available or committed. In the case of proposed funding sources, strategies for ensuring their availability shall be identified, preferably in an optional financial plan consistent with § 1410.216(f); </P>
                                    <P>(6) Contain all capital and non-capital transportation projects (including transportation enhancements, safety, Federal lands highways projects, trails projects, pedestrian walkways, and bicycle transportation facilities), or identified phases of transportation projects, proposed for funding under 49 U.S.C. Chapter 53 and/or title 23, U.S.C., excluding: </P>
                                    <P>(i) Metropolitan planning projects funded under 23 U.S.C. 104(f) and 49 U.S.C. 5303; </P>
                                    <P>(ii) State planning and research projects funded under 23 U.S.C. 307(c)(1) and 49 U.S.C. 5313(b)(except those funded with national highway system (NHS), surface transportation program (STP) and minimum guarantee funds that the State and MPO for a metropolitan area agree should be in the TIP and consequently must be in the STIP); and </P>
                                    <P>(iii) Emergency relief projects (except those involving substantial functional, locational or capacity changes); </P>
                                    <P>
                                        (7) Contain all regionally significant transportation projects requiring an action by the FHWA or the FTA whether or not the projects are to be funded with title 23, U.S.C., or 49 U.S.C. Chapter 53 funds, and/or selected funds administered by the Federal Railroad Administration, 
                                        <E T="03">e.g.,</E>
                                         addition of an interchange to the Interstate System with State, local and/or private funds, high priority or demonstration projects not funded under title 23, U.S.C., or 49 U.S.C. Chapter 53. (The STIP should include all regionally significant transportation projects proposed to be funded with Federal funds other than those administered by the FHWA or the FTA. It should also include, for information purposes, if appropriate and cited in any TIPs, all regionally significant projects, to be funded with non-Federal funds); 
                                    </P>
                                    <P>(8) Identify ITS projects funded with highway trust fund monies, including as appropriate an integration strategy, consistent with the statewide plan. Where ITS projects are identified that fit the provisions of § 1410.322(b)(11), an agreement shall exist between participating agencies in the project area that will govern their implementation. </P>
                                    <P>(9) Include for each project or phase the following: </P>
                                    <P>
                                        (i) Sufficient descriptive material (
                                        <E T="03">i.e.,</E>
                                         type of work, termini, length, etc.) to identify the project or phase; 
                                    </P>
                                    <P>(ii) Estimated total project cost, which may extend beyond the three years of the STIP; </P>
                                    <P>(iii) The amount of funds proposed to be obligated during each program year for the project or phase; </P>
                                    <P>(iv) For the first year, the proposed category of Federal funds and source(s) of non-Federal funds for the project or phase; </P>
                                    <P>(v) For the second and third years, the likely category of Federal funds and sources of non-Federal funds for the project or phase; </P>
                                    <P>(vi) Identification of the agencies responsible for carrying out the project or phase; and </P>
                                    <P>(10) For non-metropolitan areas, include in the first year only those projects which have been selected in accordance with the requirements in § 1410.224(c). </P>
                                    <P>(d) Projects that are not considered to be of appropriate scale for individual identification in a given program year may be grouped by function, work type, and/or geographic area using the applicable classifications under 23 CFR 1420.311(c) and (d) and/or 40 CFR part 93. In addition, projects funded under chapter 2 of 23 U.S.C. may be grouped by funding category and shown as one line item, unless they are determined to be regionally significant. </P>
                                    <P>(e) Projects in any of the first three years of the STIP may be moved to any other of the first three years of the STIP subject to the requirements of § 1410.224. </P>
                                    <P>(f) The statewide transportation improvement program may include a financial plan that: </P>
                                    <P>(1) Demonstrates how the adopted transportation improvement program can be implemented; </P>
                                    <P>(2) Indicates resources from public and private sources that are reasonably expected to be made available to carry out the program; </P>
                                    <P>(3) Recommends any additional financing strategies for needed projects and programs; </P>
                                    <P>(4) Might include, for illustrative purposes, additional projects that would be included in the transportation improvement program if reasonable additional resources beyond those identified in the financial plan were available. The State is not required to select any project from the illustrative list for implementation, and projects on the illustrative list cannot be advanced to implementation without an action by the Secretary on the STIP. </P>
                                    <P>(g) The STIP may be modified at any time under procedures agreed to by the cooperating parties consistent with the procedures established in this section (for STIP development), in § 1410.212 (for interested party participation) and in § 1410.222 (for the FHWA and the FTA approval). </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.218 </SECTNO>
                                    <SUBJECT>Relation of planning and project development processes. </SUBJECT>
                                    <P>
                                        (a) Depending upon its character and the level of detail desired as determined by the planning process participants, the statewide planning process products and analyses can be utilized as input to subsequent project development. The process described in § 1410.318 relating planning and project development may 
                                        <PRTPAGE P="33948"/>
                                        be utilized at the discretion of the statewide transportation planning process participants in non-metropolitan areas. Analyses performed within the statewide planning process to support project development lead to a statement of purpose and need for regionally significant proposed transportation investments. 
                                    </P>
                                    <P>(b) The results of analyses conducted under paragraph (a) of this section, at the option of the planning participants, may: </P>
                                    <P>(1) Be documented as part of the plan development record for consideration in subsequent project development actions; </P>
                                    <P>(2) Serve as input to the NEPA process required under 23 CFR 1420; </P>
                                    <P>(3) Provide a basis, in part, for project level decision making; and </P>
                                    <P>(4) Be proposed for consideration as support for actions and decisions by federal agencies other than US DOT; </P>
                                    <P>(c) To the extent feasible, Federal, State, and local agencies with subsequent project level responsibilities for investments included in a transportation plan, shall be involved in planning analyses and studies as a means to reduce subsequent project development analyses and studies, support decisionmaking, and provide early identification of key concerns for later consideration and analysis as needed. Where the processes available under § 1410.318(f) are invoked, the FHWA and the FTA shall be consulted. </P>
                                    <P>(d) Nothing in this section shall be interpreted as requiring formal NEPA review of or action on plans and TIPs. </P>
                                    <P>(e) The FHWA and the FTA project level actions, including, but not limited to issuance of a categorical exclusion, finding of no significant impact or a final environmental impact statement under 23 CFR 1420, right of way acquisition (with the exception of hardship and protective buying actions), interstate interchange approvals, high occupancy vehicle (HOV) conversions, funding of ITS projects, project conformity analyses and approval of final design and construction and transit vehicle acquisition may not be completed unless the proposed project action is included in a STIP which meets the requirements of this subpart. None of these project level actions can occur in nonattainment and maintenance areas unless the project conforms according to the requirements of the EPA's conformity rule (40 CFR parts 51 and 93). </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.220 </SECTNO>
                                    <SUBJECT>Funding of planning process. </SUBJECT>
                                    <P>Funds provided under 49 U.S.C. 5303, 5307, 5309, 5311, and 5313(b) and 23 U.S.C. 104(b)(1), 104(b)(3), 104(f), 105, and 505(a) may be used to accomplish activities in this subpart. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.222 </SECTNO>
                                    <SUBJECT>Approvals, self-certification and findings. </SUBJECT>
                                    <P>(a) At least every two years, each State shall submit the entire proposed STIP, and amendments as necessary, concurrently to the FHWA and the FTA for joint approval. The State shall certify that the transportation planning process is being carried out in accordance with all applicable requirements of: </P>
                                    <P>(1) 23 U.S.C. 134 and 135, 49 U.S.C. 5303-5305 and 5323(k), and this part; </P>
                                    <P>(2) Title VI of the Civil Rights Act of 1964, as amended (42 U.S.C. 2000d-1) and implementing regulations (49 CFR part 21 and 23 CFR part 230); </P>
                                    <P>(3) Section 162(a) of the Federal-Aid Highway Act of 1973 (23 U.S.C. 324); </P>
                                    <P>(4) The Older Americans Act of 1965, as amended (42 U.S.C. 6101); and </P>
                                    <P>(5) Section 504 of the Rehabilitation Act of 1973 (29 U.S.C. 794) and implementing regulations (49 CFR part 35); </P>
                                    <P>(6) Section 1101 of the Transportation Equity Act for the 21st Century (Public Law 105-178) regarding the involvement of disadvantaged business enterprises in the FHWA and the FTA funded projects (sec. 105(f), Public Law 97-424, 96 Stat. 2100; 49 CFR part 23); </P>
                                    <P>
                                        (7) The provisions of the Americans with Disabilities Act of 1990 (42 U.S.C. 12101 
                                        <E T="03">et seq.</E>
                                        ) and U.S. DOT regulations “Transportation for Individuals with Disabilities” (49 CFR parts 27, 37, and 38); 
                                    </P>
                                    <P>(8) The provisions of 49 CFR part 20 regarding restrictions on influencing certain Federal activities; </P>
                                    <P>(9) In States containing nonattainment and maintenance areas, sections 174 and 176 (c) and (d) of the Clean Air Act as amended (42 U.S.C. 7504, 7506 (c) and (d)); and </P>
                                    <P>(10) all other applicable provisions of Federal law. </P>
                                    <P>(b) The FHWA and the FTA Administrators, in consultation with, where applicable, Federal land managing agencies, will review the STIP or amendment and jointly make a finding (based on self-certifications made by the State and appropriate reviews established and conducted by FTA and FHWA) as to the extent the projects in the STIP are based on a planning process that meets or substantially meets the requirements of title 23, U.S.C., 49 U.S.C. Chapter 53 and subparts A, B, and C of this part. </P>
                                    <P>(1) If, upon review, the FHWA and the FTA Administrators jointly find that the planning process through which the STIP was developed meets the requirements of 23 U.S.C. 135 and these regulations (including subpart C where a metropolitan TIP is involved), they will unconditionally approve the STIP. </P>
                                    <P>(2) If the FHWA and the FTA administrators jointly find that the planning process through which the STIP was developed substantially meets the requirements of 23 U.S.C. 135 and these regulations (including subpart C where a metropolitan TIP is involved), they will act on the STIP or amendment as follows: </P>
                                    <P>(i) Joint conditional approval of the STIP subject to certain corrective actions being taken; </P>
                                    <P>(ii) Joint conditional approval of the STIP as the basis for approval of identified categories of projects; and/or </P>
                                    <P>(iii) Under special circumstances, joint conditional approval of a partial STIP covering only a portion of the State. </P>
                                    <P>(3) If, upon review, the FHWA and the FTA Administrators jointly find that the STIP or amendment does not substantially meet the requirements of 23 U.S.C. 135 and this part for any identified categories of projects, they will not approve the STIP or amendment. </P>
                                    <P>(c) The joint approval period for a new STIP or amended STIP shall not exceed two years. Where the State demonstrates, in writing, that extenuating circumstances will delay the submittal of a new STIP or amended STIP for approval, the FHWA and the FTA will consider and take appropriate action on requests to extend the approval beyond two years for all or part of the STIP for a limited period of time, not to exceed 180 days. Where the request involves projects in a metropolitan planning area(s), the affected MPO(s) must concur in the request and if the delay was due to the development and approval of the TIP, the affected MPO(s) must provide supporting information, in writing, for the request. If nonattainment and/or maintenance areas are involved, a request for an extension cannot be granted. </P>
                                    <P>(d) The FHWA and the FTA will notify the State of actions taken under this section. </P>
                                    <P>(e) Where necessary in order to maintain or establish operations, the Federal Transit Administrator and/or the Federal Highway Administrator may approve operating assistance for specific projects or programs funded under 49 U.S.C. 5307 and 5311 even though the projects or programs may not be included in an approved STIP. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.224 </SECTNO>
                                    <SUBJECT>Project selection. </SUBJECT>
                                    <P>
                                        (a) Except as provided in § § 1410.222(e) and 1410.216(c)(6), only 
                                        <PRTPAGE P="33949"/>
                                        projects included in the federally approved STIP shall be eligible for funds administered by the FHWA or the FTA. 
                                    </P>
                                    <P>(b) In metropolitan planning areas, transportation projects requiring 23 U.S.C. or 49 U.S.C. Chapter 53 funds administered by the FHWA or the FTA shall be selected from the approved TIP/STIP in accordance with procedures established pursuant to the project selection portion of the metropolitan planning regulation in subpart C of this part. </P>
                                    <P>(c) Outside metropolitan planning areas, transportation projects undertaken on the National Highway System with title 23 funds and under the bridge and Interstate maintenance programs shall be selected from the approved STIP by the State in consultation with the affected local officials. Federal lands highway projects shall be selected from the approved STIP in accordance with 23 U.S.C. 204. Other transportation projects undertaken with funds administered by the FHWA shall be selected from the approved STIP by the State in cooperation with the affected local officials, and projects undertaken with 49 U.S.C. Chapter 53 funds shall be selected from the approved STIP by the State in cooperation with the appropriate affected local officials and transit operators. </P>
                                    <P>(d) The projects in the first year of an approved STIP shall constitute an “agreed to” list of projects for subsequent scheduling and implementation. No further action under paragraphs (b) or (c) of this section is required for the implementing agency to proceed with these projects except that if appropriated Federal funds available are significantly less than the authorized amounts, § 1410.332(c) provides for a revised list of “agreed to” projects to be developed upon the request of the State, the MPO, or transit operators. If an implementing agency wishes to proceed with a project in the second and third year of the STIP, the procedures in paragraphs (b) and (c) of this section or as agreed to by the parties under paragraph (e) of this section must be used. </P>
                                    <P>(e) Expedited procedures which provide for the advancement of projects from the second or third years of the STIP may be used if agreed to by all the parties involved in the selection process. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.226 </SECTNO>
                                    <SUBJECT>Applicability of NEPA to transportation planning and programming. </SUBJECT>
                                    <P>Any decision by the Secretary concerning a transportation plan or transportation improvement program developed through the processes provided for in 23 U.S.C. 134 and 135 and 49 U.S.C. 5303 through 5305, shall not be considered to be a Federal action subject to review under NEPA. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart C—Metropolitan Transportation Planning and Programming </HD>
                                <SECTION>
                                    <SECTNO>§ 1410.300 </SECTNO>
                                    <SUBJECT>Purpose of planning process. </SUBJECT>
                                    <P>The purpose of this subpart is to implement 23 U.S.C. 134 and 49 U.S.C. 5303-5306 which require that a Metropolitan Planning Organization (MPO) be designated for each urbanized area (UZA) and that the metropolitan area have a continuing, cooperative, and comprehensive transportation planning process that results in plans and programs that consider all transportation modes and support metropolitan community development and social goals. The transportation plan and program shall facilitate the development, management and operation of an integrated, intermodal transportation system that enables the safe, efficient, economic movement of people and goods. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.302 </SECTNO>
                                    <SUBJECT>Organizations and processes affected by planning requirements. </SUBJECT>
                                    <P>The provisions of this subpart are applicable to agencies responsible for satisfying the requirements of the transportation planning, programming, and project development processes in metropolitan planning areas pursuant to 23 U.S.C. 134. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.304 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <P>Except as otherwise provided in subpart A of this part, terms defined in 23 U.S.C. 101(a) and 49 U.S.C. 5302 are used in this part as so defined. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.306 </SECTNO>
                                    <SUBJECT>What is a Metropolitan Planning Organization and how is it created? </SUBJECT>
                                    <P>(a) Designations of metropolitan planning organizations (MPOs) made after December 18, 1991, shall be by agreement among the Governor(s) and units of general purpose local governments representing 75 percent of the affected metropolitan population (including the central city or cities as defined by the Bureau of the Census), or in accordance with procedures established by applicable State or local law. A single metropolitan planning organization, to the extent possible, shall be designated to serve a metropolitan planning area containing: </P>
                                    <P>(1) A single UZA, or </P>
                                    <P>(2) Multiple UZAs that are contiguous with each other or located within the same Metropolitan Statistical Area (MSA). </P>
                                    <P>(b) The designation or redesignation shall clearly identify the policy body that is the forum for cooperative decision making that will be taking the required approval actions as the MPO. </P>
                                    <P>(c) To the extent possible, the MPO designated should be established under specific State legislation, State enabling legislation, or by interstate compact, and shall have authority to carry out metropolitan transportation planning. </P>
                                    <P>(d) Nothing in this subpart shall be deemed to prohibit an MPO from utilizing the staff resources of other agencies to carry out selected elements of the planning process. </P>
                                    <P>(e) Existing MPO designations remain valid until a new MPO is redesignated. Redesignation is accomplished by the Governor and local units of government representing 75 percent of the population in the area served by the existing MPO (the central city(ies) must be among those desiring to revoke the MPO designation). If the Governor and local officials decide to redesignate an existing MPO, but do not formally revoke the existing MPO designation, the existing MPO designation remains in effect until a new MPO is formally designated. </P>
                                    <P>(f) Redesignation of an MPO in a multistate metropolitan area requires the approval of the Governor of each State and local officials representing 75 percent of the population in the entire metropolitan planning area. The local officials in the central city(ies) must be among those agreeing to the redesignation. </P>
                                    <P>(g) Redesignation of an MPO covering more than one UZA requires the approval of the Governor(s) and local officials representing 75 percent of the population in the metropolitan planning area covered by the current MPO. The local officials in the central city(ies) in each urbanized area must be among those agreeing to the redesignation. </P>
                                    <P>
                                        (h) The voting membership of an MPO policy body designated/redesignated subsequent to December 18, 1991, and serving a TMA, must include representation of local elected officials, officials of agencies that administer or operate major modes or systems of transportation, 
                                        <E T="03">e.g.,</E>
                                         transit operators, sponsors of major local airports, maritime ports, rail operators, etc. (including all transportation agencies that were included in the MPO on June 1, 1991), and appropriate State officials. Where agencies that operate other major modes of transportation do not already have a voice on existing MPOs, the MPOs (in cooperation with the States) are encouraged to provide such agencies a voice in the decision making process, including representation/membership 
                                        <PRTPAGE P="33950"/>
                                        on the policy body and/or other appropriate committees. Further, where appropriate, existing MPOs should increase the representation of local elected officials on the policy board and other committees as a means for encouraging their greater involvement in MPO processes. Adding such representation to an MPO will not, in itself, constitute a redesignation action. 
                                    </P>
                                    <P>(i) Where the metropolitan planning area boundary for a previously designated MPO needs to be expanded, the membership on the MPO policy body and other committees, should be reviewed to ensure that the added area has appropriate representation. </P>
                                    <P>
                                        (j) Adding membership (
                                        <E T="03">e.g.,</E>
                                         local elected officials and operators of major modes or systems of transportation, or representatives of newly urbanized areas) to the policy body or expansion of the metropolitan planning area does not automatically require redesignation of the MPO. This may be done without a formal redesignation. The Governor and MPO shall review the previous MPO designation, State and local law, MPO bylaws, 
                                        <E T="03">etc.,</E>
                                         to determine if this can be accomplished without a formal redesignation. If redesignation is considered necessary, the existing MPO will remain in effect until a new MPO is formally designated or the existing designation is formally revoked in accordance with the procedures of this section. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.308 </SECTNO>
                                    <SUBJECT>Establishing the geographic boundaries for metropolitan transportation planning areas. </SUBJECT>
                                    <P>(a) The metropolitan planning area boundary shall, as a minimum, cover the UZA(s) and the contiguous geographic area(s) likely to become urbanized within, at a minimum, the twenty year forecast period covered by the transportation plan described in § 1410.322. </P>
                                    <P>(1) For existing MPOs, unless modified by agreement of the Governor and the MPO, the planning area boundaries shall be those in existence as of June 9, 1998. For MPOs designated after June 9, 1998, the boundaries shall be those agreed to by the Governor and local officials as indicated in § 1410.306(a). </P>
                                    <P>(2) The boundary may encompass the entire metropolitan statistical area or consolidated metropolitan statistical area, as defined by the Bureau of the Census. </P>
                                    <P>(3) For new MPOs, the planning area boundary shall reflect agreements between the MPO and the State DOT regarding the relationship of the metropolitan planning area boundary to any nonattainment and maintenance area within its designated limits or contiguous nonattainment or maintenance area excluded from the boundary. </P>
                                    <P>(b) The metropolitan planning area for a new UZA served by an existing or new MPO shall be established in accordance with these criteria. The current planning area boundaries for previously designated UZAs shall be reviewed and modified if necessary to comply with these criteria. </P>
                                    <P>(c) In addition to the criteria in paragraph (a) of this section, the planning areas currently in use for all transportation modes should be reviewed before establishing the metropolitan planning area boundary. Where appropriate, adjustments should be made to reflect the most comprehensive boundary to foster an effective planning process that ensures connectivity between modes and their operational integration, and promotes efficient overall transportation investment strategies in support of mobility and accessibility. </P>
                                    <P>(d) Approval of metropolitan planning area boundaries by the FHWA and/or the FTA is not required. However, metropolitan planning area boundary maps must be submitted to the FHWA and the FTA after their approval by the MPO and the Governor and be made publicly available. </P>
                                    <P>(e) The STP funds suballocated to urbanized areas greater than 200,000 in population shall not be utilized for projects outside the metropolitan planning area boundary. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.310 </SECTNO>
                                    <SUBJECT>Agreements among organizations involved in the planning process. </SUBJECT>
                                    <P>(a) The responsibilities for cooperatively carrying out transportation planning and programming shall be clearly identified in an agreement or memorandum of understanding among the State(s), operators of publicly owned mass transit, and the MPO. </P>
                                    <P>(b) Where project development activities are conducted under the planning process, they shall be documented in an agreement between the MPO and the applicable project sponsor addressing, at a minimum, the provisions of § 1410.318. </P>
                                    <P>(c) In nonattainment or maintenance areas, if the MPO is not designated as the agency responsible for air quality planning under section 174 of the Clean Air Act (42 U.S.C. 7504), there shall be an agreement between the MPO and the designated agency describing their respective roles and responsibilities for air quality related transportation planning. </P>
                                    <P>(d) Where the parties involved agree, the requirement for agreements specified in paragraphs (a), (b), and (c) of this section may be satisfied by including the responsibilities and procedures for carrying out a cooperative process in the unified planning work program or a prospectus. </P>
                                    <P>(e) If the metropolitan planning area does not include the entire nonattainment or maintenance area, there shall be an agreement among the State department of transportation, State air quality agency, affected local agencies, and the MPO describing the process for cooperative planning and analysis of all projects outside the metropolitan planning area but within the nonattainment or maintenance area. The agreement must indicate how the total transportation related emissions for the nonattainment or maintenance area, including areas both within and outside the metropolitan planning area, will be treated for the purposes of determining conformity in accordance with the U.S. EPA conformity regulation (40 CFR parts 51 and 93). The agreement shall address policy mechanisms for resolving conflicts concerning transportation related emissions that may arise between the metropolitan planning area and the portion of the nonattainment or maintenance area outside the metropolitan planning area. Proposals to exclude a portion of the nonattainment or maintenance area from the planning area boundary shall be coordinated with the FHWA, the FTA, the EPA, and the State air quality agency before a final boundary decision is made for the metropolitan planning area. </P>
                                    <P>
                                        (f) Where more than one MPO has authority within a metropolitan planning area, a nonattainment or maintenance area, and/or in the case of adjoining metropolitan planning areas, there shall be an agreement between the State department(s) of transportation and the MPOs describing how the processes and projects will be coordinated to assure the development of an overall transportation plan for the planning area(s). In metropolitan planning areas that are nonattainment or maintenance areas, the agreement shall include State and local air quality agencies, and be consistent with the provisions of § 1410.312(c). The agreement shall address policy mechanisms for resolving potential conflicts that may arise between the MPOs, 
                                        <E T="03">e.g.,</E>
                                         issues related to the exclusion of a portion of the nonattainment area from the planning area boundary. 
                                    </P>
                                    <P>
                                        (g) Where the planning process develops an ITS Integration Strategy 
                                        <PRTPAGE P="33951"/>
                                        under the provisions of § 1410.322(b)(11), there shall be an agreement among the MPO, the State DOT, the transit operator and other agencies as described in the ITS Integration Strategy. This agreement shall address policy and operational issues that will affect the successful implementation of the ITS Integration Strategy, including at a minimum ITS project interoperability, utilization of ITS related standards, and the routine operation of the projects identified in the ITS Integration Strategy; 
                                    </P>
                                    <P>(h) To the extent possible, a single cooperative agreement containing the understandings required by paragraphs (a) through (c) of this section among the State(s), the MPO, publicly owned operators of mass transportation services, and air quality agencies may be developed. Where the participating planning organizations desire, they may further consolidate agreements required by paragraphs (d) through (g) of this section with those addressed in paragraphs (a) through (c) of this section. </P>
                                    <P>(i) For all requirements specified in paragraphs (a) through (h) of this section, existing agreements shall be reviewed by the MPO, the State DOT and the transit operator for compliance and reaffirmed or modified as necessary to ensure participation by all appropriate modes. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.312 </SECTNO>
                                    <SUBJECT>Planning process organizational relationships. </SUBJECT>
                                    <P>
                                        (a) The MPO in cooperation with the State and with operators of publicly owned transit services shall be responsible for carrying out the metropolitan transportation planning process. The MPO, the State and transit operator(s) shall cooperatively determine their mutual responsibilities in the conduct of the planning process. They shall cooperatively develop the unified planning work program, transportation plan, and transportation improvement program specified in §§ 1410.314 through 1410.332. In addition, the development of the plan and TIP shall be coordinated with other providers of transportation, 
                                        <E T="03">e.g.,</E>
                                         sponsors of regional airports, maritime port operators, rail freight operators, and where appropriate, planning agencies in Mexico and/or Canada. 
                                    </P>
                                    <P>(b) The MPO shall approve the metropolitan transportation plan, plan amendments and plan updates. The MPO and the Governor shall approve the metropolitan transportation improvement program and any amendments. </P>
                                    <P>(c) In nonattainment or maintenance areas: </P>
                                    <P>(1) The transportation and air quality planning processes shall be coordinated; </P>
                                    <P>(2) TCMs proposed for FHWA and FTA funding and/or approvals shall come from a plan and TIP that fully meet the requirements of this subpart (new TCMs authorized to proceed during a conformity lapse will meet the requirements of this subpart if they are included in an interim plan and program and approved into a SIP with emission reduction benefits); and </P>
                                    <P>(3) MPOs shall participate in the development of motor vehicle emissions budgets, inventories and other transportation related air quality activities undertaken to develop SIPs to the extent required by the Clean Air Act (42 U.S.C. 7504). </P>
                                    <P>(d) In nonattainment or maintenance areas for transportation related pollutants, the MPO shall not approve any transportation plan or program which does not conform with the SIP, as determined in accordance with the U.S. EPA conformity regulation (40 CFR parts 51 and 93). </P>
                                    <P>(e) If more than one MPO has authority in a metropolitan planning area (including multi-State metropolitan planning areas) or in an area which is designated as nonattainment or maintenance for transportation related pollutants, the MPOs and the Governor(s) shall cooperatively establish the boundaries of the metropolitan planning area (addressing the required twenty year planning horizon and relationship to the nonattainment or maintenance areas) and the respective jurisdictional responsibilities of each MPO. The MPOs shall consult with each other and the State(s) to assure that plans and transportation improvement programs are coordinated for the entire metropolitan planning area, including, but not limited to, coordinated data collection, analysis and plan development. Alternatively, a single plan and/or TIP for the entire metropolitan area may be developed jointly by the MPOs in cooperation with their planning partners. Coordination efforts shall be documented in subsequent transmittals of the unified planning work program (UPWP) and various planning products (the plan, TIP, etc.) to the State(s), the FHWA, and the FTA. </P>
                                    <P>(f) The FTA and the FHWA must designate as transportation management areas all UZAs over 200,000 population as determined by the most recent decennial census. The TMAs so designated and those designated subsequently by the FTA and the FHWA (including those designated upon request of the MPO and the Governor) must comply with the special requirements applicable to such areas regarding congestion management systems, project selection, and planning certification. The TMA designation applies to the entire metropolitan planning area boundary. If a metropolitan planning area encompasses a TMA and other UZA(s), the designation applies to the entire metropolitan planning area regardless of the population of constituent UZAs. </P>
                                    <P>(g) In TMAs, the congestion management system shall be developed as part of the metropolitan transportation planning process. </P>
                                    <P>(h) The State shall cooperatively participate in the development of metropolitan transportation plans and metropolitan plans shall be coordinated with the statewide transportation plan. The relationship of the statewide transportation plan and the metropolitan plan is specified in subpart B of this part. </P>
                                    <P>(i) Where a metropolitan planning area includes Federal public lands and/or Indian Tribal lands, the affected Federal agencies and Indian Tribal Governments shall be consulted in the development of transportation plans and programs. </P>
                                    <P>(j) Discretionary grants awarded by the FHWA and the FTA under section 1221 of the TEA-21 (23 U.S.C. 101 note) (Transportation and Community and System Preservation Pilot Program), sections 1118 and 1119 of the TEA-21 (Borders and Corridors) and section 3037 (49 U.S.C. 5309 note) (Access to Jobs) shall be included in the appropriate metropolitan plan and program, except where these funds are utilized for planning and/or research activities. Applicants shall coordinate with the appropriate MPO to ensure that such projects are consistent with the provisions of this subpart. Where planning and research activities are funded under the Transportation and Community and System Preservation Pilot Program or the Borders and Corridors Program, they shall be identified in the Unified Planning Work Program as identified at § 1410.314. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.314 </SECTNO>
                                    <SUBJECT>Planning tasks and unified work program. </SUBJECT>
                                    <P>(a) The MPO(s) in cooperation with the State and operators of publicly owned transit shall develop unified planning work programs (UPWPs) that meet the requirements of 23 CFR part 420, subpart A, and: </P>
                                    <P>
                                        (1) Discuss the planning priorities facing the metropolitan planning area and describe all metropolitan transportation and transportation-related air quality planning activities 
                                        <PRTPAGE P="33952"/>
                                        anticipated within the area during the next one or two year period, regardless of funding sources or agencies conducting activities, in sufficient detail to indicate who will perform the work, the schedule for completing it and the products that will be produced; and 
                                    </P>
                                    <P>(2) Document planning activities to be performed with funds provided under title 23 and Chapter 53 of title 49 U.S.C. </P>
                                    <P>(b) Arrangements may be made with the FHWA and the FTA to combine the UPWP requirements with the work program for other Federal sources of planning funds. </P>
                                    <P>(c) In areas not designated as TMAs and which are in attainment for air quality purposes, the MPO in cooperation with the State and transit operator(s), with the approval of the FHWA and the FTA, may prepare a simplified statement of work, in lieu of a UPWP, that describes who will perform the work and the work that will be accomplished using Federal funds (administered under title 23 U.S.C. and Chapter 53 of title 49 U.S.C. If a simplified statement of work is used, it may be submitted as part of the statewide planning work program, in accordance with 23 CFR part 420. </P>
                                    <P>(d) MPOs, which include non-attainment or maintenance areas, should consult with the US EPA and state/local air agencies in the development of their UPWP regarding appropriate tasks to support attainment of air quality standards. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.316 </SECTNO>
                                    <SUBJECT>Transportation planning process and plan development. </SUBJECT>
                                    <P>(a) Each metropolitan planning process shall provide for consideration of projects and strategies that will: </P>
                                    <P>(1) Support the economic vitality of the metropolitan planning area, especially by enabling global competitiveness, productivity, and efficiency; </P>
                                    <P>(2) Increase the safety and security of the transportation system for motorized and non-motorized users; </P>
                                    <P>(3) Increase the accessibility and mobility options available to people and for freight; </P>
                                    <P>(4) Protect and enhance the environment, promote energy conservation, and improve quality of life; </P>
                                    <P>(5) Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; </P>
                                    <P>(6) Promote efficient system management and operation; and </P>
                                    <P>(7) Emphasize the efficient preservation of the existing transportation system. </P>
                                    <P>(b) In addition, the metropolitan transportation planning process shall develop and adopt a proactive public involvement process that provides complete information, timely public notice, full public access to key decisions, and supports early and continuing involvement of the public in developing plans and TIPs. To attain these objectives the process as developed shall meet the requirements and criteria as follows: </P>
                                    <P>(1) Require a minimum public comment period of 45 days before the public involvement process is initially adopted or revised; </P>
                                    <P>(2) Provide timely information about transportation issues and processes (including but not limited to initiation of plan and TIP updates, revisions and/or other modifications and the general structure of the planning process) to citizens, affected public agencies, representatives of transportation agency employees, users of public transit, freight shippers, private providers of transportation, other interested parties and segments of the community affected by transportation plans, programs and projects (including but not limited to central city and other local jurisdiction concerns); </P>
                                    <P>(3) Provide reasonable public access to technical and policy information used in the development of plans and TIPs and open public meetings where matters related to the Federal-aid highway and transit programs are being considered; </P>
                                    <P>(4) Require adequate public notice of public involvement activities and time for public review and comment at key decision points, including, but not limited to, approval of plans and TIPs (in nonattainment areas classified as serious and above, the comment period shall be at least 30 days for the plan, TIP and major amendment(s)); </P>
                                    <P>(5) Demonstrate explicit consideration, recognition and feedback to public input received during the planning and program development processes, including responses to input received from minority, elderly, low-income, and persons with disabilities populations; </P>
                                    <P>(6) Seek out and consider the needs of those traditionally under served by existing transportation systems, including, but not limited to, low-income, the elderly, persons with disabilities and minority populations; </P>
                                    <P>(7) When comments are received on the draft transportation plan or TIP (including the financial plan) as a result of the public involvement process or the interagency consultation process required under the U.S. EPA conformity regulations, a summary, analysis, and report on the disposition of comments shall be made part of the final plan and TIP; </P>
                                    <P>(8) If the final transportation plan or TIP differs significantly from the one which was made available for public comment by the MPO and raises new material issues which interested parties could not reasonably have foreseen from the public involvement efforts, an additional opportunity for public comment on the revised plan or TIP shall be made available; </P>
                                    <P>(9) Public involvement processes shall be periodically reviewed by the MPO in terms of their effectiveness in assuring that the process provides full and open access to all, with specific attention to the effectiveness of efforts to engage persons with disabilities, minority individuals, the elderly and low income populations; </P>
                                    <P>(10) These procedures will be reviewed by the FHWA and the FTA during certification reviews for TMAs, and as otherwise necessary for all MPOs, to assure that full and open access is provided to MPO decision making processes; </P>
                                    <P>(11) Metropolitan public involvement processes shall be coordinated with statewide public involvement processes and with project development public involvement processes wherever possible to enhance public consideration of the issues, plans, and programs and reduce redundancies and costs. </P>
                                    <P>(c) Transportation plan development and plans shall be consistent with Title VI of the Civil Rights Act of 1964, as amended (42 U.S.C. 2000d-1) and implementing regulations (49 CFR part 21 and 23 CFR part 230); section 162(a) of the Federal-Aid Highway Act of 1973 (23 U.S.C. 324); the Older Americans Act of 1965, as amended (42 U.S.C. 6101); the Americans With Disabilities Act of 1990 (Public Law 101-336, 104 Stat. 327, as amended) and implementing regulations (49 CFR parts 27, 37, and 38); section 504 of the Rehabilitation Act of 1973 (29 U.S.C. 794) and implementing regulations (49 CFR part 35), which ensure that no person shall, on the grounds of race, color, sex, national origin, age, or physical handicap, be excluded from participation in, be denied benefits of, or be otherwise subjected to discrimination under any program or activity receiving Federal assistance from the United States Department of Transportation. Consistency shall be demonstrated through: </P>
                                    <P>(1) An assessment covering the entire metropolitan planning area, including at a minimum the following: </P>
                                    <P>
                                        (i) A geographic and demographic profile of the metropolitan planning 
                                        <PRTPAGE P="33953"/>
                                        area that identifies the low-income and minority, and where appropriate, the elderly and persons with disabilities components of this profile, 
                                    </P>
                                    <P>(ii) The transportation services available to and planned for these segments of the metropolitan planning area's population, and </P>
                                    <P>(iii) Any disproportionately high and adverse environmental impacts, including interrelated social and economic impacts, affecting these populations, consistent with the provisions of Executive Order 12898 as implemented through U.S. DOT Order 5610.2 and FHWA Order 6640.23. Adverse effects can include a denial of or a reduction in benefits; </P>
                                    <P>(2) Consideration of comments received during public involvement efforts (consistent with the provisions of paragraph (b) of this section to ensure that expressed concerns of the elderly, low-income individuals, minority individuals and persons with disabilities, have been addressed during plan and program decision making; </P>
                                    <P>(3) Identification of prior and planned efforts to address any disproportionately high and adverse effects that are found; </P>
                                    <P>(4) The results of paragraphs (c)(1), (2), and (3) of this section will be documented in a manner to permit public review during appropriate project development activities. In accordance with Executive Order 12898, DOT Order 5610.2, and FHWA Order 6640.23, nothing in this subpart is intended to nor shall create any right to judicial review of any action taken by the agencies, their officers or recipients under this subpart to comply with such orders. </P>
                                    <P>(d) The transportation planning process shall identify actions necessary to comply with the Americans With Disabilities Act of 1990, U.S. DOT regulations “Transportation for Individuals With Disabilities” (49 CFR parts 27, 37, and 38) and section 504 of the Rehabilitation Act of 1973 and implementing regulations (49 CFR part 35). </P>
                                    <P>(e) The transportation plan development process shall provide for the involvement of traffic, ridesharing, parking, transportation safety and enforcement agencies; commuter rail operators; airport and port authorities; toll authorities; appropriate private transportation providers and where appropriate city officials; freight shippers; transit users. </P>
                                    <P>(f) The transportation planning process shall provide for the involvement of local, State, and Federal environmental resource and permit agencies as appropriate. </P>
                                    <P>(g) The transportation planning process shall provide for the involvement of Indian Tribal Governments and the Secretary of Interior on a consultation basis for the portions of the plan affecting areas under the jurisdiction of an Indian Tribal Government. </P>
                                    <P>(h) Simplified planning procedures may be proposed in non-TMAs which are in attainment for air quality purposes. The FHWA and the FTA shall review the proposed procedures for consistency with the requirements of this section. </P>
                                    <P>(i) The metropolitan transportation planning process shall include preparation of technical and other reports to assure documentation of the development, refinement, and update of the transportation plan. The reports shall be reasonably available to interested parties, consistent with paragraph (b) of this section. </P>
                                    <P>(j) The metropolitan planning process should provide a forum to coordinate all federally funded non-emergency transportation services within the metropolitan planning area. Where coordination processes are developed within the transportation planning process, at a minimum they should address the planning and delivery of services supporting access to jobs and reverse commute options, relying where feasible on existing processes and procedures. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.318 </SECTNO>
                                    <SUBJECT>Relation of planning and project development processes. </SUBJECT>
                                    <P>(a) In order to coordinate and streamline the planning and NEPA processes, the planning process, through the cooperation of the MPO, the State DOT and the transit operator, shall provide the following to the NEPA process: </P>
                                    <P>(1) An identification of an initial statement of purpose and need for transportation investments; </P>
                                    <P>(2) Findings and conclusions regarding purpose and need, identification and evaluation of alternatives studied in planning activities (including but not limited to the relevant design concepts and scope of the proposed action), and identification of the alternative included in the plan; </P>
                                    <P>(3) An identification of the planning documents that provide the basis for paragraphs (a)(1) and (a)(2) of this section; and </P>
                                    <P>(4) Formal expressions of policy support or comment by the planning process participants on paragraphs (a)(1) and (a)(2) of this section. </P>
                                    <P>(b) The following sources of information shall be utilized to satisfy paragraph (a) of this section at a level of detail agreed to by the MPO, the State DOT, and the transit operator: </P>
                                    <P>(1) Inventories of social, economic and environmental resources and conditions; </P>
                                    <P>(2) Analyses of economic, social and environmental consequences; </P>
                                    <P>(3) Evaluation(s) of transportation benefits, other benefits, costs, and consequences, at a geographic scale agreed to by the planning participants, of alternatives, including but not limited to the relevant design concepts and scope of the proposed action; </P>
                                    <P>(4) Data and supporting analyses to facilitate funding related decisions by Federal agencies where appropriate or required, including but not limited to 49 CFR part 611. </P>
                                    <P>(c) The products resulting from paragraphs (a) and (b) of this section shall be reviewed early in the NEPA process in accordance with § 1420.201 to determine their appropriate use. </P>
                                    <P>(d) In order to streamline subsequent project development analyses and studies, and promote better decision making, the FTA and the FHWA strongly encourage all Federal, State, and local agencies with subsequent project level responsibilities for investments included in a transportation plan to do the following: </P>
                                    <P>(1) Participate in planning analyses and studies to the extent possible; </P>
                                    <P>(2) Provide early identification of key concerns for later consideration and analysis as needed; and </P>
                                    <P>(3) Utilize the sources of information identified in paragraph (b) of this section. </P>
                                    <P>(e) The analyses conducted under paragraph (b)(3) of this section may serve as the alternatives analysis required by 49 U.S.C. 5309(e) for new fixed guideway transit systems and extensions and the information required under 49 CFR part 611 shall be generated. </P>
                                    <P>
                                        (f) Any decision by the Secretary concerning a transportation plan or transportation improvement program developed in accordance with this part shall not be considered to be a Federal action subject to review under NEPA (42 U.S.C. 4321 
                                        <E T="03">et seq.</E>
                                        ). At the discretion of the MPO, in cooperation with the State DOT and the transit operator, an environmental analysis may be conducted on a transportation plan. 
                                    </P>
                                    <P>
                                        (g) The FHWA and the FTA project level actions, including but not limited to issuance of a categorical exclusion, finding of no significant impact or final environmental impact statement under 23 CFR part 1420, approval of right of way acquisition, interstate interchange approvals, approvals of HOV 
                                        <PRTPAGE P="33954"/>
                                        conversions, funding of ITS projects, final design and construction, and transit vehicle acquisition, may not be completed unless the proposed project is included in a plan and the phase of the project for which Federal action is sought is included in the metropolitan TIP. None of these project-level actions can occur in nonattainment and maintenance areas unless the project conforms according to the requirements of the US EPA conformity regulation (40 CFR parts 51 and 93). 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.320 </SECTNO>
                                    <SUBJECT>Congestion management system and planning process. </SUBJECT>
                                    <P>(a) In TMAs designated as nonattainment for ozone or carbon monoxide, Federal funds may not be programmed for any project that will result in a significant increase in carrying capacity for single occupant vehicles (a new general purpose highway on a new location or adding general purpose lanes, with the exception of safety improvements or the elimination of bottlenecks) unless the project results from a congestion management system (CMS) meeting the requirements of 23 CFR part 500. Such projects shall incorporate all reasonably available strategies to manage the single occupant vehicle (SOV) facility effectively (or to facilitate its management in the future). Other travel demand reduction and operational management strategies, as appropriate for the corridor, but not appropriate for incorporation into the SOV facility itself, shall be committed to by the State and the MPO for implementation in a timely manner, but no later than the completion date for the SOV project. </P>
                                    <P>(b) In TMAs, the planning process must include the development of a CMS that provides for effective management of new and existing transportation facilities through the use of travel demand reduction and operational management. </P>
                                    <P>(c) The effectiveness of the congestion management system in enhancing transportation investment decisions and improving the overall efficiency of the metropolitan area's transportation systems and facilities shall be evaluated periodically, preferably as part of the metropolitan planning process. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.322 </SECTNO>
                                    <SUBJECT>Transportation plan content. </SUBJECT>
                                    <P>(a) The metropolitan transportation planning process shall include the development of a transportation plan addressing at least a twenty year planning horizon. The plan shall include both long-range and short-range strategies/actions, including, but not limited to, operations and management activities, that lead to the systematic development of an integrated intermodal transportation system that facilitates the safe and efficient movement of people and goods in addressing current and future transportation demand. The transportation plan shall be reviewed and updated every five years in attainment areas and at least triennially in nonattainment and maintenance areas to confirm its validity and its consistency with current and forecasted transportation and land use conditions and trends and to extend the forecast period. The transportation plan must be approved by the MPO. Update processes shall include a mechanism for ensuring that the MPO, the State DOT and the transit operator agree that the data utilized in preparing other existing modal plans providing input to the transportation plan are valid and benchmarked in relation to each other and the transportation plan. In updating a plan, the MPO shall base the update on the latest estimates and assumptions for population, land use, travel, employment, congestion, and economic activity. Reaffirmation or revisions of metropolitan plan contents and supporting analyses produced by an update review require approval by the MPO. </P>
                                    <P>(b) In addition, the plan shall, consistent with the following: </P>
                                    <P>(1) Identify the projected transportation demand of persons and goods in the metropolitan planning area over the period of the plan; </P>
                                    <P>
                                        (2) Identify adopted management and operations strategies (
                                        <E T="03">e.g.,</E>
                                         traveler information, traffic surveillance and control, incident and emergency response, freight routing, reconstruction and work zones management, weather response, pricing, fare payment alternatives, public transportation management, demand management, alternative routing, telecommuting, parking management, and intermodal connectivity) that address the need for improved system performance and the delivery of transportation services to customers under varying conditions; 
                                    </P>
                                    <P>(3) Identify pedestrian walkway and bicycle transportation facilities in accordance with 23 U.S.C. 217(g); </P>
                                    <P>(4) Reflect the consideration given to the results of the congestion management system, including in TMAs that are nonattainment areas for carbon monoxide and ozone, identification of SOV projects that result from a congestion management system that meets the requirements of 23 CFR part 500; </P>
                                    <P>(5) Assess capital investment and other measures necessary to preserve the existing transportation system (including requirements for operational improvements, resurfacing, restoration, and rehabilitation of existing and future major roadways, as well as operations, maintenance, modernization, and rehabilitation of existing and future transit facilities) and make the most efficient use of existing transportation facilities to relieve vehicular congestion and enhance the mobility of people and goods; </P>
                                    <P>(6) Include design concept and scope descriptions of all existing and proposed transportation facilities in sufficient detail, regardless of the source of funding, in nonattainment and maintenance areas to permit conformity determinations under the U.S. EPA conformity regulations at 40 CFR parts 51 and 93. In all areas, all proposed improvements shall be described in sufficient detail to develop cost estimates; </P>
                                    <P>(7) Reflect a multimodal evaluation of the transportation, socioeconomic, environmental, and financial impact of the overall plan; </P>
                                    <P>(8) Reflect, to the extent that they exist, consideration of: Comprehensive long-range land use plan(s) and development objectives; State and local housing goals and strategies, community development and employment plans and strategies, and environmental resource plans; linking low income households with employment opportunities as reflected in work force training and labor mobility plans and strategies; energy conservation goals; and the metropolitan area's overall social, economic, and environmental goals and objectives; </P>
                                    <P>(9) Indicate, as appropriate, proposed transportation enhancement activities as defined in 23 U.S.C. 101(a); and </P>
                                    <P>
                                        (10) Include a financial plan that demonstrates the consistency of proposed transportation investments (including illustrative projects where identified in the financial plan) with already available and projected sources of revenue. The financial plan shall compare the estimated revenue from existing and proposed funding sources that can reasonably be expected to be available for transportation uses, and the estimated costs of constructing, maintaining and operating the total (existing plus planned) transportation system over the period of the plan. Financial estimates utilized in preparing transportation plans (and TIPs) shall be developed through procedures cooperatively established and mutually agreed to by the MPO, the State DOT and the transit operator(s). The estimated revenue by existing revenue source (local, State, Federal and private) available for transportation projects 
                                        <PRTPAGE P="33955"/>
                                        shall be determined and any shortfalls identified. Proposed new revenues and/or revenue sources to cover shortfalls shall be identified, including strategies for ensuring their availability for proposed investments. Existing and proposed revenues shall cover all forecasted capital, operating, management, and maintenance costs. All cost and revenue projections shall be based on the data reflecting the existing situation and historical trends. For nonattainment and maintenance areas, the financial plan shall address the specific financial strategies required to ensure the implementation of projects and programs to reach air quality compliance. 
                                    </P>
                                    <P>(11) Include an ITS integration strategy for the purposes of guiding and coordinating the management and funding of ITS investments supported with highway trust fund dollars to achieve an integrated regional system. The scope of the integration strategy shall be appropriate to the scale of investment anticipated for ITS during the life of the plan and shall address the resource commitments and staging of planned investments. Provision shall be made to include participation from the following agencies, at a minimum, in the development of the integration strategy: Highway and public safety agencies; appropriate Federal lands agencies; State motor carrier agencies as appropriate; and other operating agencies necessary to fully address regional ITS integration. In determining how ITS investments will meet metropolitan goals and objectives, the integration strategy shall clearly assess existing and future ITS systems, including their functions and electronic information sharing expectations. Unique regional ITS initiatives (a program of related projects) that are multi-jurisdictional and/or multi-modal, ITS projects that affect regional integration of ITS systems, and projects which directly support national interoperability shall be identified. Documentation within the plan shall reflect the scale of investment and the needs and size of the metropolitan area. </P>
                                    <P>(c) There must be adequate opportunity for public official (including elected officials) and citizen involvement in the development of the transportation plan before it is approved by the MPO, in accordance with the requirements of § 1410.316(b). Such procedures shall include opportunities for interested parties (including citizens, affected public agencies, representatives of transportation agency employees, freight shippers, representatives of users of public transit, providers of freight transportation services, and private providers of transportation) to be involved in the early stages of the plan development/update process. The procedures shall include publication of the proposed plan or other methods to make it readily available for public review and comment and, in nonattainment TMAs, an opportunity for at least one formal public meeting annually to review planning assumptions and the plan development process with interested parties and the general public. The procedures also shall include publication of the approved plan or other methods to make it readily available for information purposes. </P>
                                    <P>(d) In nonattainment and maintenance areas for transportation related pollutants, the FHWA and the FTA, as well as the MPO, must make a conformity determination on any new/revised plan in accordance with the Clean Air Act and the EPA conformity regulations (40 CFR parts 51 and 93). If a conformity determination cannot be accomplished by either the MPO and or the FHWA and the FTA, the results will be communicated to the Governor or the Governor's designee and the public transit operator with an explanation of the potential consequences. </P>
                                    <P>(e) The FHWA and the FTA do not approve transportation plans. However, Federal actions and approvals, including, but not limited to, conformity determinations, planning findings (pursuant to § 1410.322(b)), STIP approvals, completion of the NEPA process, grant agreements, and project authorizations, are based on a transportation plan with a horizon of at least twenty years on the effective date of the plan. Plans that remain substantially unchanged (i.e., regionally significant projects in attainment areas and non-exempt projects in nonattainment and maintenance areas have not been added) after adoption may serve as the basis for subsequent Federal actions until such time as the next update. In attainment areas the effective date of the plan shall be its date of adoption by the MPO. In nonattainment and maintenance areas, the effective date shall be the date of a conformity determination by the FHWA and the FTA. </P>
                                    <P>(f) Although transportation plans do not need to be approved by the FHWA or the FTA, copies of any new/revised plans must be provided to each agency. </P>
                                    <P>(g) During a conformity lapse metropolitan areas can prepare an interim plan as a basis for advancing projects that are eligible to proceed under a conformity lapse (as defined in 40 CFR parts 51 and 93). In areas which expect to return to conformity earlier than six months, the emphasis should be on reestablishing conformity, rather than embarking on developing an interim plan and TIP. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.324 </SECTNO>
                                    <SUBJECT>Transportation improvement program content. </SUBJECT>
                                    <P>(a) The metropolitan transportation planning process shall include development of a transportation improvement program (TIP) for the metropolitan planning area by the MPO in cooperation with the State and public transit operators. </P>
                                    <P>(b) The TIP must be updated at least every two years and approved by the MPO and the Governor. The frequency and cycle for updating the TIP must be compatible with the STIP development and approval process. Since the TIP becomes part of the STIP, the TIP lapses when the FHWA and the FTA approval for the STIP lapses. In the case of extenuating circumstances, the FHWA and the FTA will consider and take appropriate action on requests to extend the STIP approval period for all or part of the STIP in accordance with § 1410.222(c). TIP extensions shall not be granted in nonattainment or maintenance areas. Although metropolitan TIPs are not approved individually by the FHWA or the FTA, they are approved as part of the STIP approval action by the FTA and the FHWA. Copies of any new or amended TIPs must be provided to each agency. Additionally, in nonattainment and maintenance areas for transportation related pollutants, the FHWA and the FTA, as well as the MPO, must make a conformity determination on any new or amended TIPs (unless the new amended TIP consists entirely of exempt projects) in accordance with the Clean Air Act requirements and the EPA conformity regulations (40 CFR parts 51 and 93). </P>
                                    <P>(c) There must be reasonable opportunity for public comment in accordance with the requirements of § 1410.316(b) and, in nonattainment TMAs, an opportunity for at least one formal public meeting during the TIP development process. This public meeting may be combined with the public meeting required under § 1410.322(c). The proposed TIP shall be published or otherwise made readily available for review and comment. Similarly, the approved TIP shall be published or otherwise made readily available for information purposes. </P>
                                    <P>
                                        (d) The TIP shall cover a period of not less than three years, but may cover a longer period if it identifies priorities and financial information for the additional years. The TIP must include a priority list of projects to be advanced in the first three years. As a minimum, 
                                        <PRTPAGE P="33956"/>
                                        the priority list shall group the projects that are to be undertaken in each of the years, i.e., year one, year two, year three. In nonattainment and maintenance areas, the TIP shall give priority to eligible TCMs identified in the approved SIP in accordance with the U.S. EPA conformity regulation (40 CFR parts 51 and 93) and shall provide for their timely implementation. 
                                    </P>
                                    <P>(e) The TIP shall be financially constrained by year and include a financial plan that demonstrates which projects can be implemented using current revenue sources and which projects are to be implemented using proposed revenue sources (while the existing transportation system is being adequately operated and maintained). The financial plan shall be developed by the MPO in cooperation with the State and the transit operator. Financial estimates utilized in preparing TIPs shall be developed through procedures cooperatively established and mutually agreed to by the MPO, the State DOT and the transit operator(s). It is expected that the State would develop this information as part of the STIP development process and that the estimates would be refined through this process. Only projects for which construction and operating funds can reasonably be expected to be available (and illustrative projects) may be included. In the case of new funding sources, strategies for ensuring their availability shall be identified. In developing the financial analysis, the MPO shall take into account all projects and strategies funded under title 23, U.S.C., 49 U.S.C. Chapter 53, other Federal funds, local sources, State assistance, and private participation. In nonattainment and maintenance areas, projects included for the first two years of the current TIP shall be limited to those for which funds are available or committed. </P>
                                    <P>(f) The TIP shall include: </P>
                                    <P>(1) All transportation projects, or identified phases of a project, (including pedestrian walkways, safety, bicycle transportation facilities and transportation enhancement projects) within the metropolitan planning area proposed for funding under title 23, U.S.C., and Federal Lands Highway projects. Title 49, U.S.C., Emergency relief projects (except those involving substantial functional, locational or capacity changes) and planning and research activities (except those funded with NHS, STP, and/or Minimum Guarantee funds) are exempt from this requirement. Planning and research activities funded with NHS, STP and/or Minimum Guarantee funds may be excluded from the TIP by agreement of the State and the MPO; </P>
                                    <P>(2) Only projects that are consistent with the transportation plan; </P>
                                    <P>(3) All regionally significant transportation projects for which an FHWA or FTA action is required whether or not the projects are to be funded with title 23, U.S.C., or title 49, U.S.C., funds, e.g., addition of an interchange to the Interstate System with State, local, and/or private funds, demonstration projects not funded under titles 23 and 49, U.S.C., etc.; </P>
                                    <P>(4) Any FTA or FHWA funded or approved projects submitted to EPA for consideration as a SIP TCM; </P>
                                    <P>(5) For air quality analysis in nonattainment and maintenance areas and informational purposes in other areas, all regionally significant transportation projects proposed to be funded with Federal funds, including intermodal facilities, not covered in paragraphs (f)(1) or (f)(3) of this section; and </P>
                                    <P>(6) For air quality analysis in nonattainment and maintenance areas and informational purposes in other areas, all regionally significant projects to be funded with non-Federal funds. </P>
                                    <P>(g) With respect to each project or project phase under paragraph (f) of this section the TIP shall include: </P>
                                    <P>
                                        (1) Sufficient descriptive material (
                                        <E T="03">i.e.</E>
                                        , type of work, termini, length, etc.) to identify the project or phase; 
                                    </P>
                                    <P>(2) Estimated total project cost (which may extend beyond the three years of the TIP); </P>
                                    <P>(3) The amount of Federal funds proposed to be obligated during each program year for the project or phase of the project; </P>
                                    <P>(4) Proposed category and source of Federal and non-Federal funds; </P>
                                    <P>(5) Identification of the recipient/subrecipient and State and local agencies responsible for carrying out the project or phase of the project; </P>
                                    <P>(6) In nonattainment and maintenance areas, identification of those projects or phases of projects which are identified as TCMs in the applicable SIP or are new TCMs with emissions benefits being submitted for SIP approval during a conformity lapse; and </P>
                                    <P>(7) In areas with Americans with Disabilities Act required paratransit and key station plans, identification of those projects or phases of projects which will implement the plans. </P>
                                    <P>(h) In nonattainment and maintenance areas, projects included shall be specified in sufficient detail (design concept and scope) to permit air quality analysis in accordance with the U.S. EPA conformity requirements (40 CFR parts 51 and 93). </P>
                                    <P>(i) Projects proposed for FHWA and/or FTA funding that are not considered by the State and the MPO to be of appropriate scale for individual identification in a given program year may be grouped by function, geographic area, and work type using applicable classifications under 23 CFR 1420.117 (c) and (d). In nonattainment and maintenance areas, classifications must be consistent with the exempt project classifications contained in the U.S. EPA conformity requirements (40 CFR parts 51 and 93). In addition, projects funded under Chapter 2 of 23 U.S.C. may be grouped by funding category and shown as one line unless they are determined to be regionally significant. </P>
                                    <P>(j) Projects utilizing Federal funds that have been allocated to the area pursuant to 23 U.S.C. 133(d)(3)(E) shall be identified. </P>
                                    <P>(k) The total Federal share of projects included in the TIP proposed for funding under 49 U.S.C. 5307 may not exceed formula backed apportioned funding levels available to the area for the program year. </P>
                                    <P>(l) Procedures or agreements that distribute suballocated Surface Transportation Program or urbanized area formula (49 U.S.C. 5307) funds to individual jurisdictions or modes within the metropolitan area by predetermined percentages or formulas are inconsistent with the legislative provisions that require MPOs in cooperation with the State and transit operators to develop a prioritized and financially constrained TIP and shall not be used unless they can be clearly shown to be based on considerations required to be addressed as part of the planning process. </P>
                                    <P>(m) For the purpose of including transit projects funded through Capital Investment Grants or Loans (49 U.S.C. 5309) in a TIP, the following approach shall be followed: </P>
                                    <P>(1) The total Federal share of projects included in the first year of the TIP shall not exceed levels of funding committed to the area; and </P>
                                    <P>(2) The total Federal share of projects included in the second, third and/or subsequent years of the TIP may not exceed levels of funding committed, apportioned, appropriated (including carryover and unobligated balances reasonably expected to be available, to the area. </P>
                                    <P>(n) As a management tool for monitoring progress in implementing the transportation plan, the TIP shall: </P>
                                    <P>
                                        (1) Identify the criteria and process for prioritizing implementation of transportation plan elements (including intermodal trade-offs) for inclusion in 
                                        <PRTPAGE P="33957"/>
                                        the TIP and any changes in priorities from previous TIPs; 
                                    </P>
                                    <P>(2) List major projects from the previous TIP that were implemented and identify any significant delays in the planned implementation of major projects; </P>
                                    <P>(3) In nonattainment and maintenance areas, describe the progress in implementing any required TCMs, including the reasons for any significant delays in the planned implementation and strategies for ensuring their advancement at the earliest possible time; and </P>
                                    <P>(4) In nonattainment and maintenance areas, include a list of all projects found to conform in a previous TIP. Projects shall be included in this list until construction has been fully authorized. </P>
                                    <P>(5) Serve as a basis for an annual listing of projects for which Federal funds have been obligated, supplemented as appropriate to ensure annual public access to information on the obligation of funds. </P>
                                    <P>(o) In order to maintain or establish operations, in the absence of an approved metropolitan TIP, the FTA and/or the FHWA Administrators, as appropriate, may approve operating assistance. </P>
                                    <P>(p) During a conformity lapses metropolitan areas may prepare an interim TIP as a basis for advancing projects that are eligible to proceed under a lapse (as defined in 40 CFR parts 51 and 93). In areas which expect to return to conformity earlier than six months, the emphasis should be on reestablishing conformity, rather than embarking on developing an interim plan and TIP. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.326 </SECTNO>
                                    <SUBJECT>Transportation improvement program modification. </SUBJECT>
                                    <P>The TIP may be modified at any time under procedures agreed to by the cooperating parties consistent with the procedures established in this part for its development and approval. In nonattainment or maintenance areas for transportation related pollutants, if the TIP is modified by adding or deleting non-exempt projects or is replaced with a new TIP, a new conformity determinations by the MPO and the FHWA and the FTA shall be made. Public involvement procedures consistent with § 1410.316(b) shall be utilized in modifying the TIP, except that these procedures are not required for TIP modifications that only involve projects of the type covered in § 1410.324(i). </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.328 </SECTNO>
                                    <SUBJECT>Metropolitan transportation improvement program relationship in statewide TIP. </SUBJECT>
                                    <P>(a) After approval by the MPO and the Governor, the TIP shall be included without modification, directly or by reference, in the STIP program required under 23 U.S.C. 135 and consistent with § 1410.220, except that in nonattainment and maintenance areas, a conformity finding by the FHWA and the FTA must be made before it is included in the STIP. After approval by the MPO and the Governor, a copy shall be provided to the FHWA and the FTA. </P>
                                    <P>
                                        (b) The State shall notify the appropriate MPO and Federal Lands Highways Program agencies, 
                                        <E T="03">e.g.</E>
                                        , Bureau of Indian Affairs and/or National Park Service, when a TIP including projects under the jurisdiction of these agencies has been included in the STIP. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.330 </SECTNO>
                                    <SUBJECT>Transportation improvement program action by FHWA/FTA. </SUBJECT>
                                    <P>(a) The FHWA and the FTA must jointly find that each metropolitan TIP is consistent with the metropolitan transportation plan produced by the continuing, comprehensive transportation process carried on cooperatively by the States, the MPOs and the transit operators in accordance with the provisions of 23 U.S.C. 134 and 49 U.S.C. 5307 and 5313(b). This finding shall be based on the self-certification statement submitted by the State and MPO under § 1410.334, a review of the metropolitan transportation plan and upon other reviews as deemed necessary by the FHWA and the FTA. </P>
                                    <P>(b) In nonattainment and maintenance areas, the FHWA and the FTA must also jointly determine, in accordance with 40 CFR parts 51 and 93, that the metropolitan TIP conforms with the applicable SIP and that priority has been given to the timely implementation of transportation control measures contained in the applicable SIP. As part of their review in nonattainment and maintenance areas requiring TCMs, the FHWA and the FTA will specifically consider any comments relating to the financial plans for the plan and TIP contained in the summary of significant comments required under § 1410.316(b). If the TIP is determined to be in nonconformance with the SIP, the FHWA and FTA shall return the TIP to the Governor and the MPO with an explanation of the joint determination and an explanation of potential consequences. If the TIP is found to conform with the SIP, the Governor and MPO shall be notified of the joint finding. After the FHWA and the FTA find the TIP to be in conformance, the TIP shall be incorporated, without modification, into the STIP, directly or by reference. </P>
                                    <P>(c) If an illustrative project is included in the TIP, no Federal action may be taken on that project by the FHWA and the FTA until it is formally included in the fiscally constrained and conforming plan and TIP. The MPOs are not required to include illustrative projects in future TIPs. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.332 </SECTNO>
                                    <SUBJECT>Selecting projects from a TIP. </SUBJECT>
                                    <P>(a) Once a TIP that meets the requirements of § 1410.324 has been developed and approved, the first year of the TIP shall constitute an “agreed to” list of projects for project selection purposes and no further project selection action is required for the implementing agency to proceed with projects, except where the appropriated Federal funds available to the metropolitan planning area are significantly less than the authorized amounts. In this case, a revised “agreed to” list of projects shall be jointly developed by the MPO, the State, and the transit operator if requested by the MPO, the State, or the transit operator. If the State or transit operator wishes to proceed with a project in the second or third year of the TIP, the specific project selection procedures stated in paragraphs (b) and (c) of this section must be used unless the MPO, the State, and the transit operator jointly develop expedited project selection procedures to provide for the advancement of projects from the second or third year of the TIP. </P>
                                    <P>(b) In areas not designated as TMAs and when § 1410.332(c) does not apply, projects to be implemented using title 23 funds other than Federal lands projects or title 49 funds shall be selected by the State and/or the transit operator, in cooperation with the MPO from the approved metropolitan TIP Federal Lands Highway Program projects shall be selected in accordance with 23 U.S.C. 204. </P>
                                    <P>
                                        (c) In areas designated as TMAs where § 1410.332(c) does not apply, all title 23 and title 49 funded projects, except projects on the NHS and projects funded under the bridge, and Federal Lands Highways programs, shall be selected by the MPO in consultation with the State and transit operator from the approved metropolitan TIP and in accordance with the priorities in the approved metropolitan TIP. Projects on the NHS and projects funded under the bridge program shall be selected by the State in cooperation with the MPO, from the approved metropolitan TIP. Federal Lands Highway Program projects shall 
                                        <PRTPAGE P="33958"/>
                                        be selected in accordance with 23 U.S.C. 204. 
                                    </P>
                                    <P>(d) Projects not included in the federally approved STIP shall not be eligible for funding with title 23 or title 49, U.S.C., funds. </P>
                                    <P>(e) In nonattainment and maintenance areas, priority shall be given to the timely implementation of TCMs contained in the applicable SIP in accordance with the U.S. EPA conformity regulations at 40 CFR parts 51 and 93. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 1410.334 </SECTNO>
                                    <SUBJECT>Federal certifications. </SUBJECT>
                                    <P>(a) The State and the MPO shall annually self-certify to the FHWA and the FTA that the planning process is addressing the major issues facing the area and is being conducted in accordance with all applicable requirements of: </P>
                                    <P>(1) 23 U.S.C. 134 and 49 U.S.C. 5303-5306; </P>
                                    <P>(2) Sections 174 and 176 (c) and (d) of the Clean Air Act (42 U.S.C. 7504, 7506 (c) and (d)); </P>
                                    <P>(3) Title VI of the Civil Rights Act of 1964 and the Title VI assurance executed by each State under 23 U.S.C. 324 and 29 U.S.C. 794; </P>
                                    <P>(4) Section 1003(b) of the Intermodal Surface Transportation Efficiency Act of 1991 (Public Law 102-240, 105 stat. 1914) regarding the involvement of disadvantaged business enterprises in the FHWA and the FTA funded planning projects (sec. 105(f), Public Law 97-424, 96 Stat. 2100; 49 CFR part 23); </P>
                                    <P>
                                        (5) Americans with Disabilities Act of 1990 (42 U.S.C. 12101 
                                        <E T="03">et seq.</E>
                                        ) and U.S. DOT regulations “Transportation for Individuals with Disabilities” (49 CFR parts 27, 37, and 38); 
                                    </P>
                                    <P>(6) Older Americans Act, as amended (42 U.S.C. 6101); and </P>
                                    <P>(7) The provisions of 49 CFR part 20 regarding restrictions on influencing certain Federal activities. </P>
                                    <P>(8) All other applicable provisions of Federal law. </P>
                                    <P>(b) The FHWA and the FTA jointly will review and evaluate the transportation planning process for each TMA (as appropriate but no less than once every three years) to determine if the process meets the requirements of this subpart. </P>
                                    <P>(c) In TMAs that are nonattainment or maintenance areas for transportation related pollutants, the FHWA and the FTA will also review and evaluate the transportation planning process to assure that the MPO has an adequate process to ensure conformity of plans and programs in accordance with procedures in 40 CFR parts 51 and 93. </P>
                                    <P>(d) Upon the review and evaluation conducted under paragraphs (b) and (c) of this section, the FHWA and the FTA shall take one of the following actions, as indicated: </P>
                                    <P>(1) Where the process meets the requirements of this part, jointly certify the transportation planning process; </P>
                                    <P>(2) Where the process substantially meets the requirements of this part, jointly certify the transportation planning process subject to certain specified corrective actions being taken; or </P>
                                    <P>(3) Where the process does not meet the requirements of this part, jointly certify the planning process as the basis for approval of only those categories of programs or projects that the Administrators may jointly determine and subject to certain specified corrective actions being taken. </P>
                                    <P>(e) A certification action under this section will remain in effect for three years unless a new certification determination is made sooner or a shorter term is specified in the certification report. </P>
                                    <P>(f) If, upon the review and evaluation conducted under paragraph (b) or (c) of this section, the FHWA and the FTA jointly determine that the transportation planning process in a TMA does not substantially meet the requirements, they may take the following action as appropriate: </P>
                                    <P>(1) Withhold up to twenty percent of the apportionment attributed to the relevant metropolitan planning area under 23 U.S.C. 133(d)(3), capital funds apportioned under 49 U.S.C. 5307-5309; or </P>
                                    <P>(2) Withhold approval of all or certain categories of projects. </P>
                                    <P>(g) In conducting a certification review, the FHWA and the FTA shall make provision, relying on the local public involvement processes and supplemented with other involvement strategies as appropriate, to engage the public in the review process. The FHWA and the FTA shall consider the public input received in arriving at a decision on a certification action. </P>
                                    <P>(h) The State and the MPO shall be notified of the actions taken under paragraph (f) of this section. Upon full, joint certification by the FHWA and the FTA, all funds withheld will be restored to the metropolitan area, unless the funds have lapsed. </P>
                                    <HD SOURCE="HD1">Federal Transit Administration</HD>
                                    <HD SOURCE="HD2">49 CFR Chapter VI </HD>
                                    <P>For the reasons set forth in the preamble, the Federal Transit Administration proposes to amend Chapter VI of title 49, Code of Federal Regulations, as follows: </P>
                                </SECTION>
                            </SUBPART>
                        </PART>
                        <PART>
                            <HD SOURCE="HED">PART 613—[REMOVED] </HD>
                            <P>3. Remove part 613. </P>
                            <P>4. Add part 621 to read as follows: </P>
                        </PART>
                        <PART>
                            <HD SOURCE="HED">PART 621—METROPOLITAN AND STATEWIDE PLANNING </HD>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart A—Planning </HD>
                            </SUBPART>
                            <CONTENTS>
                                <SECHD>Sec. </SECHD>
                                <SECTNO>621.100 </SECTNO>
                                <SUBJECT>Definitions. </SUBJECT>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart B—Statewide Transportation Planning and programming </HD>
                                    <SECTNO>621.200 </SECTNO>
                                    <SUBJECT>Statewide transportation planning and programming. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart C—Metropolitan Transportation Planning and Programming </HD>
                                    <SECTNO>621.300 </SECTNO>
                                    <SUBJECT>Metropolitan transportation planning and programming. </SUBJECT>
                                </SUBPART>
                            </CONTENTS>
                            <AUTH>
                                <HD SOURCE="HED">Authority:</HD>
                                <P>
                                    23 U.S.C. 134 and 135; 42 U.S.C. 7410 
                                    <E T="03">et seq.</E>
                                    ; 49 U.S.C. 5303-5309; 49 CFR .151. 
                                </P>
                            </AUTH>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart A—Planning </HD>
                                <SECTION>
                                    <SECTNO>§ 621.100 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <P>The regulations in 23 CFR 1410, subpart A, shall be followed in complying with the requirements of this subpart. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart B—Statewide Transportation Planning and programming </HD>
                                <SECTION>
                                    <SECTNO>§ 621.200 </SECTNO>
                                    <SUBJECT>Statewide transportation planning and programming. </SUBJECT>
                                    <P>The regulations in 23 CFR 1410 subpart B, shall be followed in complying with the requirements of this subpart. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart C—Metropolitan Transportation Planning and Programming </HD>
                                <SECTION>
                                    <SECTNO>§ 621.300 </SECTNO>
                                    <SUBJECT>Metropolitan transportation planning and programming </SUBJECT>
                                    <P>The regulations in 23 CFR part 1410, subpart C, shall be followed in complying with the requirements of this subpart. </P>
                                </SECTION>
                            </SUBPART>
                            <SIG>
                                <DATED>Issued on: May 18, 2000.</DATED>
                                <NAME>Vincent F. Schimmoller,</NAME>
                                <TITLE>Acting Executive Director, Federal Highway Administration.</TITLE>
                                <NAME>Nuria I. Fernandez,</NAME>
                                <TITLE>Acting Administrator, Federal Transit Administration.</TITLE>
                            </SIG>
                        </PART>
                    </CHAPTER>
                </SUPLINF>
                <FRDOC>[FR Doc. 00-13021 Filed 5-19-00; 1:15 pm]</FRDOC>
                <BILCOD>BILLING CODE 4910-MR-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>65</VOL>
    <NO>102</NO>
    <DATE>Thursday, May 25, 2000</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="33959"/>
            <PARTNO>Part IV</PARTNO>
            <AGENCY TYPE="P">Department of Transportation</AGENCY>
            <SUBAGY>Federal Aviation Administration</SUBAGY>
            <SUBAGY>Federal Transit Administration</SUBAGY>
            <HRULE/>
            <CFR>23 CFR Parts 771, 1420 and 1430</CFR>
            <CFR>49 CFR Parts 622 and 623</CFR>
            <TITLE>NEPA and Related Procedures for Transportation Decisionmaking, Protection of Public Parks, Wildlife and Waterfowl Refuges, and Historic Sites; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="33960"/>
                    <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                    <SUBAGY>Federal Highway Administration </SUBAGY>
                    <CFR>23 CFR Parts 771, 1420, and 1430 </CFR>
                    <SUBAGY>Federal Transit Administration </SUBAGY>
                    <CFR>23 CFR Parts 1420 and 1430 </CFR>
                    <CFR>49 CFR Parts 622 and 623 </CFR>
                    <DEPDOC>[FHWA Docket No. FHWA-99-5989 ] </DEPDOC>
                    <RIN>FHWA RIN 2125-AE64; FTA RIN 2132-AA43 </RIN>
                    <SUBJECT>NEPA and Related Procedures for Transportation Decisionmaking, Protection of Public Parks, Wildlife and Waterfowl Refuges, and Historic Sites </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCIES:</HD>
                        <P>Federal Highway Administration (FHWA), Federal Transit Administration (FTA), DOT. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice of proposed rulemaking (NPRM); request for comments. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The FHWA and the FTA are issuing this notice of proposed rulemaking to update and revise their National Environmental Policy Act of 1969 (NEPA) implementing regulation for projects funded or approved by the FHWA and the FTA. The current regulation was issued in 1987 and experience since that time as well as changes in legislation, most recently by the Transportation Equity Act for the 21st Century (TEA-21), call for an updated approach to implementation of NEPA for FHWA and FTA projects and actions. Under this proposed rulemaking, the FHWA/FTA regulation for implementing NEPA would be redesignated and revised to further emphasize using the NEPA process to facilitate effective and timely decisionmaking. </P>
                        <P>This NPRM is being issued concurrently with another notice of proposed rulemaking on metropolitan and statewide transportation planning. This coordinated approach to rulemaking will further the goal of the FTA and the FHWA to better coordinate the results of the planning processes with project development activities and decisions associated with the NEPA process. </P>
                    </SUM>
                    <DATES>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            Comments must be received on or before August 23, 2000. For dates of public information meetings see 
                            <E T="02">Supplementary Information.</E>
                        </P>
                    </DATES>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            Submit written, signed comments to the docket number appearing at the top of this document. You must submit your comments to the Docket Clerk, U.S. DOT Dockets, Room PL-401, 400 Seventh Street, SW., Washington, DC 20590-0001. All comments will be available for examination at the above address between 9 a.m. and 5 p.m., e.t., Monday through Friday, except Federal holidays. To receive notification of receipt of comments you must include a pre-addressed, stamped envelope or postcard. For addresses of public information meetings see 
                            <E T="02">Supplementary Information.</E>
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>For the FHWA: Mr. Fred Skaer, (202) 366-2058, Office of Planning and Environment, HEPE, or Mr. L. Harold Aikens, (202) 366-0791, Office of the Chief Counsel, HCC-31. For the FTA: Mr. Joseph Ossi, (202) 366-0096, Office of Planning, TPL-22, or Mr. Scott Biehl, (202) 366-0952, Office of the Chief Counsel, TCC-30. Office hours are from 7:45 a.m. to 4:15 p.m., e.t., Monday through Friday, except Federal holidays. </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">Electronic Access </HD>
                    <P>
                        Internet users may access all comments received by the U.S. DOT Dockets, Room PL401, by using the universal resource locator (URL):­
                        <E T="03">http://dms.dot.gov.</E>
                         It is available 24 hours each day, 365 days each year. Please follow the instructions online for more information and help. 
                    </P>
                    <P>
                        An electronic copy of this document may be downloaded by using a modem and suitable communications software from the Government Printing Office's Electronic Bulletin Board Service at (202) 512-1661. Internet users may reach the Office of the Federal Register's home page at: 
                        <E T="03">http://www.nara.gov/fedreg</E>
                         and the Government Printing Office's database at: 
                        <E T="03">http://www.access.gpo.gov/nara.</E>
                    </P>
                    <EXTRACT>
                        <HD SOURCE="HD1">Contents of Preamble </HD>
                        <P>• Background on the NEPA Rule </P>
                        <P>• Overall Strategy for Regulatory Development </P>
                        <P>• Relationship to U.S. DOT's Statewide and Metropolitan Planning Regulation and other Rulemaking Efforts </P>
                        <P>• Section-by-Section Analysis of the Proposed Rule for NEPA and Related Procedures for Transportation Decisionmaking </P>
                        <P>• Section-by-Section Analysis of the Proposed Rule for Protection of Public Parks, Wildlife and Waterfowl Refuges, and Historic Sites.</P>
                    </EXTRACT>
                    <HD SOURCE="HD1">Public Information Meetings </HD>
                    <P>We will hold a series of seven public briefings within the comment period for the NPRM. The purposes of these briefings is to explain the content of the NPRM and encourage public input to the final rulemaking. The meetings will address this NPRM, the companion NPRM on the metropolitan and statewide planning process and the NPRM on Intelligent Transportation Systems Architecture consistency. The meetings will be scheduled from approximately 8 a.m. to 5 p.m. at the locations listed below. Changes in the information below will be made available after the publication of this NPRM through the FHWA and the FTA websites, other public announcement avenues and the newsletters and websites of major stakeholder groups. Individuals wishing information but without access to these sources may contact the individuals listed above. </P>
                    <P>The structure of the meetings will emphasize brief presentations by the DOT staff regarding the content of the NPRM. A period for clarifying questions will be provided. Under current statutory and regulatory provisions, the DOT staff will not be permitted to engage in a substantive dialog regarding what the content of the NPRMs and the final regulations should be. Attendees wishing to express ideas and thoughts regarding the final content of the rules should direct those comments to the docket. Briefing sites will include: Boston, MA, Auditorium, Volpe National Transportation Systems Center, 55 Broadway, June 9, 2000; Atlanta, GA, Westin Peachtree Plaza Hotel, 210 Peachtree Street, June 20, 2000; Washington, D.C., Marriott Metro Center, 775 12th Street, NW, June 23, 2000; Chicago, IL, Holiday Inn Mart Plaza, 350 North Orleans Street, June 27, 2000; Denver, CO, Marriott City Center, 1701 California Street, June 30 , 2000; Dallas, TX, Hyatt Regency Hotel Dallas, 300 Reunion Boulevard, July 11, 2000; and, San Francisco, CA, Radisson Miyako, 1625 Post Street, July 19, 2000. </P>
                    <P>
                        As part of the outreach process planned for these proposed rules, the FHWA/FTA will be conducting a national teleconference on June 15, 2000 from 1 to 4 p.m., e.t., through the auspices of the Center for Transportation and the Environment at North Carolina State University. The teleconference will be accessible through numerous downlink locations nationwide and further information can be obtained from Ms. Katie McDermott at 
                        <E T="03">kpm@unity.ncsu.edu</E>
                         or (919) 515-8034. The purpose of the teleconference is to describe the proposed new statewide and metropolitan planning, NEPA implementation, and Intelligent Transportation Systems (ITS) rules. 
                    </P>
                    <P>
                        An overview of each of the three notices of proposed rulemakings (NPRMs) will be presented and the audience (remote and local) will have opportunities to ask questions and seek clarification of FHWA/FTA proposals. By sponsoring this teleconference it is 
                        <PRTPAGE P="33961"/>
                        hoped that interest in the NPRMs is generated, that stakeholders will be well informed about FHWA/FTA proposals, and that interested parties will participate in the rulemaking process by submitting written suggestions, comments and concerns to the docket. 
                    </P>
                    <HD SOURCE="HD1">Background </HD>
                    <P>
                        The FHWA and the FTA propose to update and revise the current regulation and guidance implementing the NEPA (42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                        ) for transportation projects using Federal funds or requiring Federal approval. 
                    </P>
                    <P>In this notice of proposed rulemaking, we are clearly communicating that our NEPA responsibilities include an affirmative duty to facilitate the development of transportation proposals which represent responsible stewardship of community and natural environmental resources. In the 13 years since the NEPA regulation was last issued, the nature of the highway and transit programs has evolved to reflect our country's changing transportation needs and the impact that the transportation network can have on a complex set of environmental, community, and economic considerations. What has not changed is the role of State and local officials and Federal land management agency decision makers to define transportation investment strategies, plan for a future transportation system that best reflects their community needs, and select and set priorities for transportation projects. </P>
                    <P>The NPRM was developed by an interagency Task Force of the FHWA and the FTA with input from other DOT modal agencies, the U.S. Environmental Protection Agency (EPA), other Federal agencies and the Office of the Secretary, U.S. DOT. The Task Force reviewed all input received from the outreach process which is described below and through other sources that communicate regularly with U.S. DOT. In addition, input was provided from the field staff of the FHWA and the FTA. </P>
                    <P>Over the past thirteen years we have developed an increased understanding of effective environmental analysis, a greater commitment to prevention of adverse environmental impacts, and a realization of the increased value of integrated agency and public coordination. Given these developments, our role to ensure that transportation projects are developed through a more effective and collaborative NEPA process at the State, local, and Federal levels becomes that much more pivotal. Our environmental rule reflects the understanding that NEPA is an important tool for helping make transportation decisions, rather than justifying decisions already made. In addition, we believe that a more coordinated approach to planning and project development (the NEPA process plus additional project level actions needed to prepare for project implementation) will contribute to more effective and environmentally sound decisions regarding investment choices and trade-offs. </P>
                    <P>By including the environmental streamlining provision in TEA-21, section 1309 of Public Law 105-178, 112 Stat. 108 at 232, the Congress intended that transportation planning and environmental considerations be better coordinated and that project delivery schedules be improved through a process that is efficient, comprehensive, and streamlined. Growing awareness of the need for a Federal role that would oversee development of a coordinated environmental review process is tempered with congressional intent that State and local decisions be respected. The most important Federal role in the transportation decisionmaking process is one where the FHWA and the FTA would facilitate other Federal agencies' early involvement and participation in NEPA activities so that redundant processes are identified and avoided. We will, in our role as lead agencies, highlight opportunities to use NEPA as a mechanism to address statutory responsibilities at Federal, State, and local levels of government. During the TEA-21 outreach process, there has been very strong support from our transportation and environmental partners for a better managed NEPA process which reflects these basic features: coordination, flexibility, and efficiency. </P>
                    <P>For these reasons, it is clear that a fundamentally new approach to NEPA is needed, one that emphasizes strong environmental policy, collaborative program solving approaches involving all levels of government and the public early in the process, and integrated and streamlined coordination and decisionmaking processes. Proposed approaches are included in this notice of proposed rulemaking. This NPRM fully supports “protection and enhancement of communities and the natural environment,” one of five U.S. DOT strategic goals. Translating this strategic direction into day-to-day operations requires that appropriate changes be made to regulations and nonregulatory operating guidance. </P>
                    <HD SOURCE="HD1">Overall Strategy for Regulatory Development </HD>
                    <P>Our strategy for regulatory development has three principal elements: (1) Outreach and listening to stakeholders; (2) developing improvements that will allow the FHWA, the FTA, States and metropolitan areas to demonstrate measurable progress toward achieving congressional intent and objectives; and (3) seeking ways to improve coordination and performance, both internally and with our Federal partner agencies. </P>
                    <HD SOURCE="HD2">Input to Development of Notice of Proposed Rulemaking </HD>
                    <P>We have used several venues to obtain feedback on how to improve the administration of NEPA. Of principal importance was the NEPA 25th Anniversary Workshop held in Chattanooga, Tennessee in 1995. Participants included a diverse group of governmental and nongovernmental individuals representing transportation and community interests, as well as those interested in protecting the natural environment. The blueprint document that resulted from the NEPA Workshop underscores the need for a fundamentally new approach to NEPA, one that focuses on decisionmaking rather than compliance. </P>
                    <P>The FHWA and the FTA, in concert with the Office of the Secretary and other modal administrations within the U.S. DOT, developed and implemented an extensive public outreach process on all elements of the TEA-21. The process began shortly after the legislation was enacted on June 9, 1998, and various types of outreach activities have been underway since that time. The initial six-month Departmentwide outreach process included twelve regional forums and over 50 focus groups and workshops (63 FR 40330, July 28, 1998). The U.S. DOT heard from over 3,000 people including members of Congress, Governors and Mayors, other elected officials, transportation practitioners at all levels, community activists and environmentalists, freight shippers and suppliers, and other interested individuals. The input received was valuable and has helped us shape implementation strategy, guidance, and regulations. </P>
                    <P>
                        With respect to the planning and environmental provisions of TEA-21, we learned a great deal through the twelve regional forums and focus group sessions and subsequently implemented a second, more focused phase of outreach which included issuing a discussion paper, “TEA-21 Planning and Environmental Provisions: Options for Discussion,” FHWA/FTA, February 1999. The content of the Options Paper reflected input received up to that time and built upon the existing statewide 
                        <PRTPAGE P="33962"/>
                        and metropolitan planning regulations and our NEPA implementing regulation. We released the Options Paper on February 9, 1999, and received comments through April 30, 1999. More than 150 different sets of comments were received from State Departments of Transportation (DOTs), Metropolitan Planning Organizations (MPOs), counties, regional planning commissions, other Federal agencies, transit agencies, bicycle advocacy groups, engineering organizations, consultants, historical commissions, environmental groups, and customers— the American public. These comments were all reviewed and taken into consideration in the development of this NPRM. Another element of outreach has included meetings with our key stakeholder groups, other Federal agencies, and the regional and field staff within our agencies. 
                    </P>
                    <P>This proposed rule will be one part of a widespread agency effort to provide clear and consistent guidance on how the NEPA process can be most effectively used to help applicants make transportation decisions which reflect a concern for social, economic, and environmental well-being. It provides the framework upon which we, along with State DOTs, MPOs, transit agencies, and Federal land management agencies, can base our approach to transportation decisionmaking. </P>
                    <P>We recognize that a wide range of issues exist in the realm of transportation and the environment. Our outreach effort associated with TEA-21, as well as feedback to the Options Paper, have highlighted many areas of concern for which the FHWA and the FTA policy should be more clearly articulated. However, not all of these areas will be directly addressed as part of this rule. For many topics for which we feel regulatory treatment is unnecessary or inappropriate, we intend to issue a comprehensive package of materials to provide detailed, nonregulatory information on how to incorporate such considerations into the NEPA process. In addition, certain other topics will be the subject of individual, separate regulations or guidance. </P>
                    <P>
                        The comprehensive package of informational materials is envisioned as a replacement both for the 1987 FHWA Technical Advisory 6640.8a on environmental documents and the FTA (formerly Urban Mass Transportation Administration) Circular 5620.1 
                        <SU>1</SU>
                        <FTREF/>
                         on environmental assessments. The timing of its development is intended to be consistent with the development of the regulations that will result from this NPRM. We anticipate that the comments we receive on the NPRM will help guide the creation of the informational materials, as well as the regulations. Thus, a more complete picture of our approach will be presented. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             The FHWA and the FTA internal directives are available for inspection and copying as prescribed at 49 CFR part 7.
                        </P>
                    </FTNT>
                    <P>Further, we have been working with Federal environmental agencies to implement the environmental streamlining provisions of TEA-21. The results of those activities are described in the section-by-section analysis discussion later in this preamble. </P>
                    <P>The TEA-21 outreach effort and comments on the Options Paper have all helped guide us in developing this notice of proposed rulemaking. Comments on this NPRM are welcomed and will be taken into account prior to the issuance of a final regulation containing updated NEPA implementation requirements. </P>
                    <HD SOURCE="HD1">Relationship to U.S. DOT's Statewide and Metropolitan Planning Regulation and Other Rulemaking Efforts </HD>
                    <P>There are four additional rulemaking activities either underway or planned which relate closely to this notice of proposed rulemaking. These include: the joint FHWA/FTA rules on statewide and metropolitan planning and on section 4(f), and the FHWA rules on acquisition of right-of-way and decision-build contracting. The relationship with the statewide and metropolitan planning rulemaking is described below, and the TEA-21 provisions and input received through the Options Paper on the other three issue areas follows: </P>
                    <HD SOURCE="HD2">Statewide and Metropolitan Planning </HD>
                    <P>Concurrent with the release of this notice of proposed rulemaking, the U.S. DOT is issuing a notice of proposed rulemaking to update and revise its statewide and metropolitan planning regulations (23 CFR part 450 and 49 CFR part 613). As proposed in these coordinated rulemaking actions, the statewide and metropolitan planning rule and the NEPA and transportation decisionmaking rules would both be moved to new parts: 1410 and 1420, respectively. This co-location is intended to underscore the integrated nature of transportation planning and the NEPA process. </P>
                    <P>We intend to ensure that the regulatory provisions governing statewide and metropolitan planning and NEPA work in a consistent and complementary fashion, and result in sound transportation decisions. We view the changes in TEA-21 as opportunities to improve and integrate planning and environmental processes to support more effective decisionmaking and it is in this context that both notices of proposed rulemaking were developed. It is our intent to establish consistency between the two regulations to allow our State and local transportation partners that choose to conduct social, economic, and environmental analysis at the planning stage to incorporate that analysis at the project development phase. This approach offers options for integrating project development efficiencies into the overall planning process, where States, MPOs, and transit agencies deem such action appropriate and desirable. </P>
                    <HD SOURCE="HD2">Section 4(f) (49 U.S.C. 303) </HD>
                    <P>
                        We propose to move the reference and citation for section 4(f) 
                        <SU>2</SU>
                        <FTREF/>
                         in title 23 of the Code of Federal Regulations. This proposal removes the provisions on section 4(f) from the NEPA rule and establishes a separate regulation for section 4(f). Years of applying section 4(f) to new and unprecedented situations have led to a history of case experience which must be reflected in the regulation. As a result, the rules governing section 4(f) have grown to the point that they warrant their own part in the regulations. We can envision a separate effort to revise and update the section 4(f) rule; however, we are proposing minor changes at this time. Nevertheless, we invite comment on suggested changes to the Section 4(f) rule of a more substantive nature. A comprehensive package of informational materials that will be released concurrent with this final regulation will elaborate on the continued fully integrated relationship between the NEPA process and the section 4(f) evaluation process. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             Section 4(f) of the Department of Transportation Act, which protected certain public lands and all historic sites, technically was repealed in 1983 when it was codified without substantive change, as 49 U.S.C. 303. This regulation continues to refer to section 4(f) because it would create needless confusion to do otherwise; the policies section 4(f) engendered are widely referred to as “section 4(f)” matters. A provision with the same meaning is found at 23 U.S.C. 138 and applies only to FHWA actions.
                        </P>
                    </FTNT>
                    <P>
                        The information within the proposed section 4(f) regulation has not changed in concept. However, new information has been added to bring the administration of section 4(f) evaluations up-to-date with FHWA and FTA programs such as Transportation Enhancements, Transit Enhancements, the Symms National Trail Program, etc. There has been little substantive change in the requirements of the section 4(f) regulation; rather the format of the information presented has been changed 
                        <PRTPAGE P="33963"/>
                        to reflect these program changes and proposed organizational changes. 
                    </P>
                    <P>The separation of the section 4(f) and NEPA procedures into separate regulations is not intended to fragment compliance with section 4(f) and NEPA. Our intent is to continue a fully integrated implementation under the unified and coordinated process provided by the NEPA procedures as an umbrella for addressing all relevant responsibilities, including section 4(f). Placing the two regulations in sequence within the Code of Federal Regulations, with cross references between them, is intended to communicate the continued integration of section 4(f) and the NEPA process. </P>
                    <HD SOURCE="HD2">Right-of-Way Acquisition </HD>
                    <P>Section 1301 of the TEA-21 allows the value of land acquired by a State or local government without Federal assistance to be credited to the State share of a federally-assisted project which uses that land. However, the law stipulated that the land acquisition must not influence the environmental assessment of the project, including the need to construct the project, the consideration of alternatives, and the selection of a specific location. </P>
                    <P>
                        The FHWA considered, under a separate rulemaking, covering “Right-of-Way Program Administration” published as a final rule in the December 21, 1999, 
                        <E T="04">Federal Register</E>
                        , an “early acquisition” policy to accommodate the acquisition of land or other property interests (including “at-risk” activities) by State or local agencies that may be deemed necessary while NEPA considerations are being concluded. These acquisitions would be considered “at-risk” in that the Federal reimbursement for a share of the acquisition costs would be forthcoming only if the acquired property is subsequently used in a federally-assisted project. Interested parties should refer to the December 21, 1999, final rulemaking (64 FR 71284-71297) in the 
                        <E T="04">Federal Register</E>
                        . 
                    </P>
                    <P>Advance right-of-way acquisition was the subject of considerable debate during the TEA-21 outreach efforts. Several commenters including the Capital Area MPO in Albany, NY, argued that the advance acquisition of right-of-way in rapidly growing areas is desirable, cost effective and good policy. These commenters view land acquisition as environmentally neutral, in that unused land can be disposed of, often at a profit. Others, including the National Coalition to Defend NEPA, noted the inherent conflict between allowing advance right-of-way acquisition and corridor preservation initiatives, and the selection of a preferred alternative as part of the NEPA process. The National Coalition to Defend NEPA argues that purchase of land represents a commitment to a particular project location and that it, therefore, would influence the assessment of the project under NEPA. </P>
                    <HD SOURCE="HD2">Design-Build Contracting </HD>
                    <P>Section 1307 of the TEA-21 permits a State or local transportation agency to award a design-build contract during project development provided that final design shall not commence before the NEPA process has been completed. </P>
                    <P>We have been concerned about design-build contracts (also called “turnkey” contracts) for federally-assisted projects being let before the NEPA process has been completed. To do so could give the appearance that the State or local transportation agency is fully committed to a single course of action, and that the NEPA process is simply a clearance exercise and not a true decisionmaking process. There may, however, be some situations in which design-build procurement can be structured to allow for the design-builders to work on an alternative emerging from the NEPA process. Our agencies recognize that the emerging interest in design-build contracting may warrant specific regulatory language or guidance addressing the relationship between design-build procurement and NEPA. </P>
                    <P>
                        During the TEA-21 outreach efforts, some commenters suggested that design-build contracting provisions could include clauses that would preclude work on construction or the “building” of projects until after the NEPA Record of Decision 
                        <SU>3</SU>
                        <FTREF/>
                         is made. The American Road and Transportation Builders Association (ARTBA) suggested that any work done on projects using this type of procurement method would be “at-risk” until the NEPA Record of Decision is announced, meaning that the work may have to be discarded if the NEPA process ultimately results in selection of an alternative project. In these cases, the State or local agency would not be eligible to receive Federal reimbursement until that time, and only if the action was consistent with the Record of Decision. The Virginia DOT suggested that design-build procurement awards should not be made until after the NEPA process had been concluded, at which point the specifics of the location and design decisions would be known. This approach has been used by the FTA in its Turnkey Demonstration Program. The Orange County Transportation Corridors Agency suggested that having a design-build agency on board at the earliest possible time is actually environmentally beneficial, since it can contribute valuable input in a timely way, to arrive at implementable and cost effective recommendations. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             NEPA Record of Decision is the documentation of final action by the FHWA and the FTA regarding their decision on a project action (final alternative chosen, impacts, mitigation and basis for decision, etc.) addressed in an Environmental Impact Statement.
                        </P>
                    </FTNT>
                    <P>For highway projects, the FHWA's Office of Infrastructure is responsible for developing regulations which implement this TEA-21 provision. It is currently engaged in fact-finding and consultation among transportation partners including the American Association of State Highway and Transportation Officials (AASHTO), and anticipates beginning the formal rulemaking process next year. Achieving a balance between realizing the fullest time-savings potential of design-build contracting and maintaining the integrity of the NEPA process will be the subject of considerable discussion during that rulemaking process. </P>
                    <P>Our agencies intend to adopt consistent policies on the NEPA-related aspects of the design-build issue for two reasons: (1) Transit projects should not have procedural disadvantages in comparison to highway projects, and (2) Federal transit law (49 U.S.C. 5304(e)) requires that the FTA and the FHWA conform their NEPA processes to each other's. </P>
                    <HD SOURCE="HD1">Section-by Section Analysis of the Proposed Rule on NEPA and Related Procedures for Transportation Decisionmaking </HD>
                    <P>This section of the notice of proposed rulemaking includes a section-by-section analysis of the proposed rule on NEPA and incorporates summary information on comments received on the Options Paper. All comments on the Options Paper are contained in the docket. The comments are, of necessity, summarized in each of the relevant sections of the proposed rule and are intended to provide an overall perspective on the comments submitted to the FHWA and the FTA. Details on specific comments and input can be obtained by reviewing the materials in the docket. </P>
                    <P>The proposed regulations have been reordered as to content and organized into the following four subparts: </P>
                    <FP SOURCE="FP-1">Subpart A—Purpose, Policy, and Mandate; </FP>
                    <FP SOURCE="FP-1">
                        Subpart B—Program and Project Streamlining; 
                        <PRTPAGE P="33964"/>
                    </FP>
                    <FP SOURCE="FP-1">Subpart C—Process and Documentation Requirements; and </FP>
                    <FP SOURCE="FP-1">Subpart D—Definitions. </FP>
                    <P>The following table highlights the reordering and organization for each proposed subpart: </P>
                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,r100">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">Proposed Section </CHED>
                            <CHED H="1">Current Section </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Subpart A—Purpose, Policy, and Mandate </ENT>
                            <ENT>None. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.101 Purpose of this regulation </ENT>
                            <ENT>771.101 Purpose. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.103 Relationship of this regulation to the CEQ regulation and other guidance </ENT>
                            <ENT>771.103 [Reserved] </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.105 Applicability of this regulation </ENT>
                            <ENT>
                                771.109(a) Applicability and responsibilities and 
                                <LI>771.111(f) Early coordination, public involvement, and project development. </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.107 Goals of the NEPA process </ENT>
                            <ENT>None. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.109 The NEPA umbrella </ENT>
                            <ENT>771.105 Policy. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.111 Environmental justice </ENT>
                            <ENT>771.105 Policy. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.113 Avoidance, minimization, mitigation, and enhancement responsibilities </ENT>
                            <ENT>771.105 Policy. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Subpart B—Program and Project Streamlining </ENT>
                            <ENT>None. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.201 Relationship of planning and project development processes </ENT>
                            <ENT>None. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.203 Environmental streamlining </ENT>
                            <ENT>None. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.205 Programmatic approvals </ENT>
                            <ENT>None. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.207 Quality assurance process </ENT>
                            <ENT>771.125 Final environmental impact statements. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.209 Alternate procedures </ENT>
                            <ENT>None. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.211 Use of this part by other U.S. DOT agencies </ENT>
                            <ENT>None. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.213 Emergency action procedures </ENT>
                            <ENT>771.131 Emergency action procedures. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Subpart C—Process and Documentation Requirements </ENT>
                            <ENT>None. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.301 Responsibilities of the participating parties </ENT>
                            <ENT>771.109 Applicability and responsibilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.303 Interagency coordination </ENT>
                            <ENT>771.111 Early coordination, public involvement, and project development. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.305 Public involvement </ENT>
                            <ENT>771.111 Early coordination, public involvement, and project development. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.307 Project development and timing of activities </ENT>
                            <ENT>771.111 Early coordination, public involvement, and project development, and </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>771.113 Timing of administration activities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.309 Classes of actions </ENT>
                            <ENT>771.115 Classes of actions. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.311 Categorical exclusions </ENT>
                            <ENT>771.117 Categorical exclusion. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.313 Environmental assessments </ENT>
                            <ENT>771.119 Environmental assessments. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.315 Findings of no significant impacts </ENT>
                            <ENT>771.121 Findings of no significant impacts. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.317 Draft environmental impact statements </ENT>
                            <ENT>771.123 Draft environmental impact statements. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.319 Final environmental impact statements </ENT>
                            <ENT>771.125 Final environmental impact statements. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.321 Record of decision </ENT>
                            <ENT>771.127 Record of decision. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.323 Re-evaluations </ENT>
                            <ENT>771.129 Re-evaluations. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.325 Supplemental environmental impact statements </ENT>
                            <ENT>771.130 Supplemental environmental impact statements. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Subpart D—Definitions </ENT>
                            <ENT>None. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.401 Terms defined elsewhere </ENT>
                            <ENT>None. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1420.403 Terms defined in this part </ENT>
                            <ENT>771.107 Definitions. </ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD1">Subpart A—Purpose, Policy and Mandate </HD>
                    <P>This proposed subpart sets out the framework for the FHWA/FTA NEPA process. It complements and supplements the United States Council on Environmental Quality (CEQ) provisions that serve a similar function for the entire Federal government. </P>
                    <HD SOURCE="HD2">Section 1420.101 Purpose of This Regulation </HD>
                    <P>Current § 771.101 would be redesignated as § 1420.101 and revised to establish that the focus of the proposed regulation is to conduct a decisionmaking process for transportation projects that, under NEPA, integrates and streamlines compliance with all transportation and environmental laws applicable to decisionmaking during project development. Reference is made to the regulations for transportation planning as being a contributing factor to this decisionmaking process. </P>
                    <HD SOURCE="HD2">Section 1420.103 Relationship of This Regulation to the CEQ Regulation and Other Guidance </HD>
                    <P>The proposed § 1420.103 does not appear in the current regulation. It clarifies that this regulation is to be read as a supplement to the CEQ's governmentwide regulations for implementing NEPA (40 CFR parts 1500-1508) and contains specific provisions for Federal surface transportation actions under our jurisdiction. Further, the proposed section acknowledges that, in addition to issuing revised NEPA regulations, we will conduct and fulfill our responsibilities under NEPA using any combination of approaches including, but not limited to, nonregulatory guidance, training, and technical assistance. </P>
                    <P>
                        The CEQ regulations cover regulatory definition and general environmental procedural requirements (
                        <E T="03">e.g.,</E>
                         acceptable development and evaluation of an acceptable range of alternatives). These are not repeated in this proposed rule because we want to avoid confusion by repeating or paraphrasing CEQ requirements. Reproducing requirements in the FHWA and the FTA environmental regulations that are identical to CEQ requirements could create potential conflicts and confusion as to the applicability of CEQ provisions not reproduced. Instead, the chosen approach makes a discernible connection between the different regulations, and provides the 
                        <PRTPAGE P="33965"/>
                        opportunity for general practitioners to increase their familiarity with and understanding of the CEQ regulations, a familiarity of which is essential to their ability to comply fully with all of the environmental requirements applicable to transportation projects. 
                    </P>
                    <HD SOURCE="HD2">Section 1420.105 Applicability of This Regulation </HD>
                    <P>The proposed section revises current §§ 771.109 and 771.111, Applicability and responsibilities and Early coordination, public involvement, and project development, respectively. The language appearing in paragraph (a) of the proposed section is a shortened version of paragraph (a) of current § 771.109. Paragraph (b) in the proposed section is essentially the existing criteria for allowable segmentation of projects, taken from paragraph (f) of § 771.111. </P>
                    <HD SOURCE="HD2">Section 1420.107 Goals of the NEPA Process </HD>
                    <P>Proposed section § 1420.107 is to be read in close conjunction with the subsequent proposed § 1420.109. Section 1420.107 would establish the goals of the FHWA/FTA transportation decisionmaking process. The goals are drawn from a variety of statutory mandates, including NEPA itself, and provisions of the various transportation laws that authorize our programs. The NEPA process is a partnership among Federal, State, and local governments and, at times, private entities. Our intent in this section is to establish a common understanding within the partnership of the goals to be achieved through the NEPA process. </P>
                    <P>The FHWA and the FTA reaffirm their role as lead Federal agencies, and underscore their responsibility to manage the NEPA process with the objective of achieving these goals. This responsibility extends to ensuring that Federal NEPA decisions pay appropriate deference to State and local decisions made in good faith and not coerce a particular Federal point of view. State and local decisions made with full consideration of a broad range of social, economic, and environmental factors, and with the advice of appropriate Federal and other State resource agencies (i.e., the agencies responsible under law for the protection or management of natural and community resources) and with public involvement are those most likely to advance the NEPA goals. </P>
                    <HD SOURCE="HD2">Section 1420.109 The NEPA Umbrella </HD>
                    <P>Proposed § 1420.109 would replace portions of current § 771.105, Policy. The proposed section sets forth our basic policy regarding how the decisionmaking process for surface transportation projects is to be conducted . The proposed section states the intent of our agencies to use the NEPA process as the overarching procedural construct under which the varied legal requirements, environmental issues, and public interests relevant to the transportation decision are brought to bear; hence the term “NEPA umbrella” is used to describe the concept. The consideration of a proposed action under NEPA concludes with a decision made in the best overall public interest: one that balances the need for safe and efficient transportation with the project's social, economic, environmental benefits and impacts, and the attainment of relevant environmental protection goals. </P>
                    <P>Experience in administering the NEPA process has shown that many practitioners do not fully understand or practice our approach of using the NEPA process as an umbrella for integrating their studies, reviews, or consultations and satisfying all relevant requirements in a single, integrated decisionmaking process. Instead, many have chosen to approach the various requirements as obstacles or hurdles to be addressed in a less than comprehensive fashion. Many delayed projects or failed processes can be traced back to a disintegrated and disconnected approach to meeting NEPA and other requirements. This section of the regulation is intended to clarify the preferred approach and explicitly demonstrate the multitude of factors that can influence Federal decisionmaking. Setting forth these expectations will contribute to a better, more efficient and timely NEPA process, one that is envisioned in the TEA-21 and highlighted in its section 1309 on environmental streamlining. </P>
                    <HD SOURCE="HD2">Section 1420.111 Environmental Justice </HD>
                    <P>Subsequent to the previous regulatory revision in 1987, the 1994 Executive Order 12898 on Environmental Justice was issued to address disproportionately high and adverse human health and environmental effects of Federal government programs, policies, and activities on minority populations and low income populations. This section would be added to present regulatory language from our policy on environmental justice that is articulated in the DOT Order 5610.2 on Environmental Justice (62 FR 18377, April 15, 1997). </P>
                    <HD SOURCE="HD2">Section 1420.113 Avoidance, Minimization, Mitigation, and Enhancement Responsibilities </HD>
                    <P>This section would present our policy regarding NEPA's mandate that Federal agencies, to the fullest extent possible, use all practicable means to restore and enhance, and avoid or minimize any possible adverse effects of their actions upon the quality of the human environment. </P>
                    <P>Our policy towards correcting adverse impacts is contained in the hierarchical but not necessarily sequential concepts of avoidance, minimization, and mitigation of impacts, and in the evaluation of environmental enhancements. The policy is consistent with the CEQ's approach to mitigation presented in 40 CFR 1500.2(f) and elsewhere, and would revise the language concerning mitigation of adverse impacts currently provided at § 771.105(d). The proposed language reflects also the broadened Federal funding eligibility for enhancement measures, such as transportation enhancement activities and transit enhancements, enacted with ISTEA and TEA-21. The section would address the eligibility for Federal funding (to the extent authorized by law), of measures to avoid, minimize, or mitigate impacts, or to provide or implement enhancements. </P>
                    <P>Our general responsibility for ensuring that mitigation is carried out would be presented in paragraph (d) of the proposed section, NEPA Commitments. These provisions would be redesignated from § 771.109(b) to streamline the subject matter of the new regulations; the original text would be revised to detail the responsibility for implementing mitigation measures and environmental enhancements that resulted from commitments made in the FHWA/FTA NEPA process. </P>
                    <HD SOURCE="HD1">Subpart B—Program and Project Streamlining </HD>
                    <P>This subpart would group together a set of provisions aimed at improving the NEPA process, either on individual projects or on a programwide basis, so that transportation decisions can be made in a timely and environmentally sensitive manner. It would respond in part to the TEA-21 chapter on flexibility and streamlining, which addresses major investment study integration (section 1308) and contains the provisions on environmental streamlining (section 1309). </P>
                    <HD SOURCE="HD2">Section 1420.201 Relation of Planning and Project Development Processes </HD>
                    <P>
                        This section would clarify the relationship of the transportation 
                        <PRTPAGE P="33966"/>
                        planning process and the project development process which is the subject of this NPRM. It reflects coordination with our concurrent proposed Metropolitan and Statewide Planning regulations; § 1420.318 of that proposed rule, and its preamble, provide further discussion of the relationship between the planning and project development processes. The section also stresses that the record of prior transportation planning activities, such as development of purpose and need and the systems-level evaluation of alternatives, shall be incorporated into the scoping or early coordination phases of an EIS or EA, respectively, in order to establish the alternatives to be advanced to the NEPA process. 
                    </P>
                    <P>Our agencies feel it is essential to clarify the nature of the linkage between planning and the NEPA process in this NPRM. The transportation planning process needs to be better coordinated with the project development/NEPA process so that transportation planning decisions can ultimately support the development of the individual projects which arise from transportation plans. During the TEA-21 outreach efforts, opinions varied over whether regulatory language or guidance should be used to integrate planning and programming activities, but most commenters agreed that the linkage between planning and project development needs to be cultivated. Many commenters, including the AASHTO and many State DOTs, opposed any regulatory language which would place requirements of NEPA into the planning process. Others, including the National Coalition to Defend NEPA, pointed to the need for the core values of the NEPA process to be incorporated into the planning process and suggested that regulatory language is in order. </P>
                    <P>The Options Paper discussed the notion that the establishment of purpose and need and the broad scale evaluation of alternatives can often be best accomplished during the planning process. How to frame the statement of purpose and need so that it is neither too narrow nor too broad is a continuing challenge. If too narrowly conceived, purpose and need can constrain the process with an unreasonably limited set of possible solutions; if too broadly constructed purpose and need may lead to an unmanageably large set of alternatives that unnecessarily bog down the process. Options to provide clearer direction regarding what constitutes an acceptable statement of purpose and need are being explored and we invite specific comments on this issue. </P>
                    <P>There was considerable support for allowing States and MPOs the option of addressing purpose and need in the planning process, and even to initiate the NEPA process at that time. This would allow stakeholders to conduct broad ranging planning and subregional studies, reach agreement on purpose and need during the planning process, and benefit from such analyses by using them directly in the NEPA process. There was also strong support for establishing a point during the NEPA process at which the participants would discuss and concur in a statement of purpose and need. </P>
                    <P>However, a considerable number of commenters, including many State DOTs and MPOs, objected to any mandate for the determination of purpose and need during planning and argued that it would burden the planning process and add considerable delay by seeking a determination of need at an inappropriate juncture. </P>
                    <P>The Surface Transportation Policy Project (STPP) recommended a two-stage NEPA process where the first phase would evaluate the range of social, fiscal, and environmental costs and benefits of various alternative visions for a corridor or community. Based on this evaluation, an initial statement of purpose and need would be articulated. This purpose and need statement would be very broad, an articulation of the goals for the area already arrived at through the planning process, for example. The STPP proposed that a wide field of inquiry would be maintained at this stage. Subsequent to this phase of evaluation, and once a detailed review of options is complete, an agency would have the information necessary to propose a revised, more specific statement of purpose and need. It would be this revised statement of purpose and need that would serve as the basis for a detailed review of alternatives under NEPA. Under both phases, the choice of a project purpose would be subject to public input. </P>
                    <P>The Environmental Law and Policy Center argued for the allowance of lower-cost and lesser impact project alternatives to be selected through the NEPA process even if they do not fully meet the stated purpose and need. Both the U.S. EPA and the U.S. Department of Interior argued for broadly defined purpose and need during planning to ensure that a full range of modal alternatives are considered. </P>
                    <P>The National Coalition to Defend NEPA expressed concern over the development of purpose and need during planning. It felt this could prematurely preclude options and alternatives and argued that, until the DEIS is completed, insufficient information is available with which to make such decisions. In short, it is concerned that defining purpose and need so early (in planning) could have the effect of “setting in stone” projects without adequate consideration of alternatives. </P>
                    <P>Commenters asked for examples, best practices and information on issues related to purpose and need determination, and there was general consensus that improvements in defining purpose and need are warranted. They felt that the difficulties articulated in the Options Paper relating to broad versus narrow statements of purpose and need are indeed real problems and that our agencies could provide useful guidance in this area. </P>
                    <P>We intend to provide continuity between the systems planning and project development processes so that the results of analysis performed during the planning stage, including project purpose and need, alternatives, public input, and environmental concerns are brought forward into project development. The proposed integration of the planning and project development process embodied in this regulation would enable a more broadly defined statement of purpose and need to be addressed at appropriate points in the integrated process. </P>
                    <P>
                        There has also been much discussion of the standing given to planning decisions on alternatives to be advanced or dropped from consideration. The proposed regulation envisions an active discussion of this issue during scoping, with the involvement of the responsible planning agencies (
                        <E T="03">i.e.</E>
                        , the MPO and/or the State DOT). Ultimately, the U.S. DOT agency, in cooperation with the applicant, must decide the range of alternatives to be evaluated in detail in the NEPA document. The proposed regulation allows these agencies to recognize planning decisions made with adequate supporting documentation. Though the form and content of this support will not be specified in the regulation, we expect to see some or all of the following offered in this context: technical studies as envisioned by proposed § 1420.318(b), documentation of public reviews and comments, formal policy board resolutions in the case of MPO actions, or other supporting materials. For proposed major transit investments, this review will also decide whether the documented planning activities constitute the Alternatives Analysis required by 49 U.S.C. 5309(e) or, alternatively, if the requirement must still be satisfied in the NEPA process. 
                    </P>
                    <P>
                        We propose to provide more detailed treatment on the subjects of purpose and 
                        <PRTPAGE P="33967"/>
                        need, and the development, analysis, and evaluation of alternatives in the comprehensive package of informational materials. This would include how to address alternatives which in the past have been rejected for not fully meeting traditional concepts of purpose and need. Further, we plan to showcase examples of successful practices which demonstrate how effective integration of planning and project development can protect communities and environmental resources and save time in providing needed transportation improvements. 
                    </P>
                    <P>Examples of issues that might be covered include: the further consideration of alternatives that may not fully meeting traditional concepts of purpose and need; more broadly defined purpose and need statements during the planning stage so that a full range of modal alternatives are considered; an alternative analysis that examines non-construction alternatives that use transportation demand strategies; and flexibility to encourage the consideration of alternatives which may have lower than originally desired levels of transportation service if there are cost, time, and impact savings that justify the lower levels of transportation service. </P>
                    <P>We are soliciting comments on a suggestion that specifically addressing the requirements of the major investment study in the planning process would enhance that process by forging a clearer link between the planning and the project-level NEPA processes, leading to greater streamlining at the project level. </P>
                    <HD SOURCE="HD2">Section 1420.203 Environmental Streamlining </HD>
                    <P>This new section would be added to reflect the requirements of section 1309 of the TEA-21. The basic premise of section 1309 of the TEA-21 was to address concerns relating to delays, unnecessary duplication of efforts and costs associated with the development of highway and transit projects. Section 1309 also stipulates that nothing in section 1309 shall affect the applicability of NEPA or any other federal environmental statute or affect the responsibility of any federal offices to comply with or enforce such statutes. The rule responds to the TEA-21 environmental streamlining provisions by establishing a process intended to coordinate Federal agency involvement in major highway and transit projects with the goals of identifying decision points and potential conflicts as early as possible, integrating the NEPA process as early as possible, encouraging the full and early participation of all relevant agencies, and establishing coordinated time schedules for agencies to act on a project. </P>
                    <P>This proposed section of the regulation establishes the “coordinated environmental review process” which section 1309 of the TEA-21 directed the Secretary of Transportation to develop and implement. Paragraph (a) lays out the elements of this coordinated environmental review process, providing a substantive but flexible set of actions to be taken by the U.S. DOT in cooperation with the applicant to ensure that the goals of section 1309 are met. An important element of this coordinated environmental review process is reaching closure among the Federal agencies on the scoping process. This paragraph calls for agency concurrence at the end of scoping, which could take various forms depending upon the mutual understandings and agreements of the Federal agencies. In the event of nonconcurrence, this paragraph provides also for means to resolve interagency disagreements at the earliest possible time. Paragraph (b) describes the process for applying the coordinated environmental review process to State level environmental reviews. Paragraph (c) would implement the provisions of the statute which allow the Secretary to decide not to apply section 1309 to the preparation of an environmental assessment. Paragraph (d) would implement the CEQ NEPA regulation provisions on paperwork reduction and clarifies that the NEPA documentation need not explicitly contain a finding that a particular impact does not exist. For example, if the environmental inventory revealed that there were no wetlands in the project area, a specific finding indicating that the project would have no impacts on wetlands would not be required. This provision would help to focus NEPA documents on important issues in accordance with the CEQ NEPA regulations' provision on paperwork reduction. </P>
                    <P>One consistent theme that emerged through the outreach process pointed to the need for early and up-front involvement of Federal agencies in the NEPA process and for close coordination and cooperation among the Federal agencies throughout the process. The State DOTs, the MPOs, the National Association of County Engineers, the U.S. EPA, and the U.S. Department of Interior all felt that Federal agency involvement is critical to successful implementation of the environmental streamlining provisions. They also recommend that our field offices and the resource agencies' field offices throughout the country have the authority to participate in, review, and respond to issues associated with the NEPA process. </P>
                    <P>Inasmuch as stakeholder sentiments echoed a need for early collaboration and close coordination with all interested and affected parties, they also strongly reinforced the need for flexibility at the State and local levels for implementing the goals of streamlining. A “one-size-fits-all” regulatory approach was soundly rejected by an overwhelming majority of stakeholders, other Federal agencies, practitioners, project sponsors, and field offices. </P>
                    <P>
                        We believe that successful implementation of environmental streamlining must be based upon a number of principles, and are pursuing a process that will ensure effective environmental decisionmaking in a timely manner. Both transportation and resource agencies must improve their environmental review processes. The U.S. DOT will provide national leadership on environmental streamlining, and is working with CEQ and headquarters offices of the EPA, the U.S. Army Corps of Engineers, the U.S. Fish and Wildlife Service, the U.S. National Park Service, the U.S. National Oceanic and Atmospheric Administration, the Advisory Council on Historic Preservation and others to obtain commitments to better decisionmaking. The framework for this commitment to the environment and to streamlining the environmental process is set forth in the national Memorandum of Understanding (MOU) which was entered into by the aforementioned agencies in July 1999.
                        <SU>4</SU>
                        <FTREF/>
                         We fully expect to track the commitments reflected in the national MOU. We recognize that tangible progress will evolve locally, and State by State, at different rates, based largely on good working relationships and trust established among the agencies at the field office level. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             This Memorandum of Understanding is available electronically from FHWA's website at 
                            <E T="03">http://www.fhwa.dot.gov/environment/strming.htm.</E>
                        </P>
                    </FTNT>
                    <P>
                        We are proposing to implement the environmental streamlining requirements largely outside of the regulatory process through the following means: (1) U.S. DOT memoranda of understanding with Federal or State agencies; (2) establishment of dispute resolution processes; (3) streamlining pilot efforts; (4) authorization of the U.S. DOT to approve State DOT or transit agency requests to reimburse Federal agencies for expenses associated with meeting expedited time frames; and (5) establishing performance measures to evaluate and measure success in both 
                        <PRTPAGE P="33968"/>
                        environmental stewardship and environmental streamlining. We have established an environmental streamlining page on the FHWA website to keep the public up to date on our ongoing activities and resources (http://www.fhwa.dot.gov/environment/strming.htm). We are also providing a detailed description of our work to date on the following: 
                    </P>
                    <HD SOURCE="HD3">(1) National MOU </HD>
                    <P>The central effort on the national MOU has been to craft an agreement among agencies which demonstrates a commitment to key principles and upon which further agreements can be executed at a local or regional level to address more specific issues. Establishing and maintaining clear and frank communication has been at the heart of the national MOU and would be the primary guide to further interagency agreements. </P>
                    <P>The process of developing the national MOU was aimed chiefly at responding to the concerns regarding early and up-front involvement of Federal agencies in the NEPA process and for close coordination and cooperation between Federal agencies throughout the process. We are working with representatives of other Federal agencies at the headquarters and field levels to develop a common understanding of the environmental streamlining provision and a coordinated implementation strategy. The development of the national MOU has followed the suggestion of AASHTO, Association of Metropolitan Planning Organizations (AMPO), and many State DOTs that the MOU include broad principles of agreement on how the NEPA process would be carried out but that project-specific or program-specific MOU's need to be developed at the State, regional, or local level, based upon these broad principles, and tailored to specific local circumstances or projects. </P>
                    <HD SOURCE="HD3">(2) Dispute Resolution Procedures </HD>
                    <P>Procedures for resolving conflict at the national, regional, and State levels are under development. Mediation methods and systems for alternative dispute resolution are being developed and training programs in these methods will be established. This approach will enable parties to seek timely intervention over disputes during the project development process, as a way to circumvent and minimize the number of environmentally unacceptable projects that may otherwise be referred to CEQ for resolution, by either reestablishing consensus on the need for the project or reaching consensus to drop the project entirely. Alternative dispute resolution strategies will be defined so that they can be effectively applied to improve institutional relationships among parties or to resolve conflicts surrounding specific project issues. </P>
                    <P>On the matter of dispute resolution procedures, commenters made three key points. They felt that explicit time frames for document reviews are needed and should be agreed to, to the fullest extent possible, up-front in the process. Secondly, they supported an approach where the parties to the MOU agree, at an early stage, on the level of information and detail that is needed at various steps in the NEPA process. Resource agencies expressed frustration with the timing and level of detail of information that they are asked to consider and act upon, and State and local implementing agencies expressed frustration due to uncertainties over what specific information and level of detail would be required of them by the Federal resource, regulatory and permitting agencies. A third point made by many stakeholders was that procedures on coordination, documentation, and communications should be agreed to as early as possible. They felt that this would help to resolve differences that arise at various points in the process and which can contribute to delays. </P>
                    <HD SOURCE="HD3">(3) Pilot Efforts Are One Effective Mechanism for Testing and Evaluating Change </HD>
                    <P>One specific topic suggested for pilot projects was from the North Carolina DOT and the American Road and Transportation Builders Association, which suggested the testing of alternative approaches to gaining interagency cooperation during the NEPA process. The Virginia DOT suggested that pilot project efforts should be directed at finding ways to resolve differences between Federal agencies. A third suggestion was that pilot projects should test approaches to providing States flexibility in carrying out the NEPA process. </P>
                    <P>Not all commenters supported the concept of pilot projects, however, and the National Coalition to Defend NEPA questions the legal authority of our agencies to conduct pilot projects and cautioned against using pilot projects to “back-door” the NEPA process. It was also concerned that pilot efforts not only involve partnership development between Federal and non-Federal partners and resource permitting agencies, but also include groups representing the public as well. </P>
                    <P>Based on the input received on the issue of pilot efforts, we are not proposing to establish a formal process for pilots at this time, through regulation or any other means. Instead, we will participate in pilot efforts on a case-by-case basis. These pilot efforts might be focused on a single project or on improving a particular process, but would not include the delegation of Federal NEPA responsibilities to States that was considered but not enacted in the TEA-21. We will continue to coordinate closely with the U.S. EPA, the AASHTO and others who are developing pilot efforts, and will actively assist in sharing information on efforts including lessons learned. </P>
                    <HD SOURCE="HD3">(4) Use of Titles 23 and 49, U.S.C., Funds To Pay for Environmental Agency Work </HD>
                    <P>The agency reimbursement language in the environmental streamlining provisions of the TEA-21 offers an opportunity to partially overcome an historic obstacle, that Federal agencies cannot involve themselves in the process early enough or regularly enough due to resource constraints within agencies. The TEA-21 includes specific conditions allowing States and transit agencies to use Federal transportation funds for reimbursement of expenses related to work done to meet the expedited time schedules required by section 1309 of the TEA-21. In addition, other statutory authorities exist for agency reimbursement, and we are exploring the full range of options for reimbursing agencies through any of the available authorities. Furthermore, approaches to developing collaborative efforts with other Federal agencies are being explored in order to develop model reimbursement agreements, and to facilitate the implementation of such agreements by Federal agency field staff. </P>
                    <P>
                        Due to the need for flexibility and the different practices and needs of various State and resource agencies, it was determined that nonregulatory guidance would most appropriately address the use of Federal transportation funds for reimbursing costs associated with streamlining. Hence, we engaged participation by many other affected Federal agencies to develop a single guidance package that would be useful to transportation and environmental agencies, including State DOT's and transit agencies and Federal, State, and local resource agencies. The breadth of situations that might be addressed under this provision was such that the guidance does not try to anticipate them all. Rather, it reinforces the Federal government's belief in effective interagency coordination and 
                        <PRTPAGE P="33969"/>
                        demonstrates a commitment from Headquarters offices to support field efforts in implementing this provision of the TEA-21. 
                    </P>
                    <P>There were a number of comments on this TEA-21 provision and a suggestion from the American Road and Transportation Builders Association that the principles to apply to reimbursement should include a provision that reimbursement for Federal agency activities to expedite NEPA reviews must be linked to a specific project, set of tasks, and person or position to be involved on behalf of the Federal agency. Others, including the Nevada and Missouri DOTs, felt that reimbursing an agency for working on one project over another is not a good approach. Reimbursing agencies for doing their jobs, it was argued, would introduce a bias into the NEPA process which would result in an expedited review or enhanced level of participation on some projects over others. </P>
                    <HD SOURCE="HD3">(5) Performance Measures </HD>
                    <P>Our agencies have a joint effort underway to evaluate the timeliness and the effectiveness of the NEPA process at arriving at decisions that are in the best overall public interest. Further information on this effort can be obtained from the FHWA. </P>
                    <HD SOURCE="HD2">Section 1420.205 Programmatic Approvals </HD>
                    <P>Section 1420.205 would be added to establish in regulation the FHWA/FTA practice of using programmatic environmental approvals as one way of addressing recurring situations in a streamlined manner. </P>
                    <P>This practice has been especially effective with categorical exclusions for meeting the NEPA requirements in uncomplicated and non-controversial situations. One example of this are programmatic categorical exclusion approvals in which FHWA and a State DOT established a set of environmental impact thresholds, which, if not exceeded, allow the State DOT to apply the categorical exclusion approval without a project specific review by FHWA. Periodically, the FHWA reviews a sample of projects after-the-fact to ensure that the approval was appropriately applied. Other examples of programmatic approvals include section 4(f) approvals for minor uses of parkland and approval to delegate certain USDOT responsibilities under the recently issued regulations implementing section 106 of the National Historic Preservation Act. The proposed section explicitly recognizes the appropriateness of programmatic approaches for compliance with NEPA and related statutes, but does not specify the types of actions for which programmatic approaches would be created. Programmatic approaches to meeting the NEPA requirements which would not directly involve project level Federal approvals would be subject to periodic process reviews to ensure that they are being properly applied. This would enable the Federal agencies to focus limited resources on more problematic project-level decisions and to maintain a quality assurance role for projects with beneficial or de minimis environmental impacts. There was general support for such an approach in comments on the Options Paper. We invite comments on public notice and interagency coordination processes appropriate for making programmatic approvals. </P>
                    <HD SOURCE="HD2">Section 1420.207 Quality Assurance Process </HD>
                    <P>This new proposed section would establish an internal responsibility for our agencies to employ appropriate quality management methods to assure that the NEPA responsibilities are carried out in a competent and timely manner. Such a process is intended to streamline the process by institutionalizing lessons learned throughout the administration of our programs and NEPA so that mistakes are not repeated and innovative approaches are fully implemented. </P>
                    <P>The requirements in the current regulation for legal sufficiency review of Final Environmental Impact Statements (FEIS) and prior concurrence of the Headquarters on certain FEISs would be incorporated into this proposed section. These processes have proven helpful in assuring the quality of analysis, coordination, and documentation and can prevent costly and timely lawsuits and conflicts. As proposed, the nature of legal sufficiency review and the threshold for requiring prior concurrence at Headquarters would not be specified in regulation, but would be the subject of internal orders. </P>
                    <HD SOURCE="HD2">Section 1420.209 Alternate Procedures </HD>
                    <P>This new section would be added to establish the procedures for processing and approving alternate procedures for complying with this regulation. This would give us the flexibility to partner with CEQ and State DOTs or transit agencies on NEPA reinvention efforts that achieve the goals of the NEPA process by using alternate methods or procedures that are more in tune with and supportive of non-Federal decisionmaking requirements. </P>
                    <HD SOURCE="HD2">Section 1420.211 Use of This Part by Other U.S. DOT Agencies </HD>
                    <P>In 1993, the U.S. DOT National Performance Review effort recommended that the NEPA procedures of the various modes be blended into a single process. Efforts to accomplish this unified procedure were purposely delayed until after passage of the surface transportation reauthorization which became TEA-21. Recent discussions within the U.S. DOT are now pointing toward a dual effort, one element of which would cover the entire department, the other of which is this proposed regulation covering just the FHWA and the FTA. To advance the first element, U.S. DOT would revise the U.S. DOT Order on NEPA to update the departmentwide statement of environmental policy and to remove barriers to collaboration between the U.S. DOT modes on NEPA issues. It would provide authority for one U.S. DOT agency to use the NEPA procedures of another U.S. DOT agency or to act as the agent for another U.S. DOT agency when a situation warrants. This proposed section clarifies in regulation that the internal order is considered legally sufficient to provide these authorities. The further action at the departmental level to amend the U.S. DOT Order on NEPA is under development. </P>
                    <P>Most Options Paper commenters, including State DOTs, MPOs, associations, and authorities supported a coordinated approach to NEPA within the U.S. DOT and its modal administrations. There was strong support for the elimination of differences in how the FHWA and the FTA manage the NEPA process and for a consolidation of these approaches in the updated regulation. In addition, there was strong support from New York DOT, the American Road and Transportation Builders Association and others for the elimination of provisions duplicating the CEQ regulations, which many thought would lead to a streamlined regulation. Finally, many commenters supported the notion of the FHWA and the FTA having strong oversight over the NEPA process. Equally important, commenters noted, is that there be a true partnership between Federal agencies and State and local agencies. </P>
                    <HD SOURCE="HD2">Section 1420.213 Emergency Action Procedures </HD>
                    <P>
                        This proposed section would contain the provision currently found at 23 CFR 771.131. 
                        <PRTPAGE P="33970"/>
                    </P>
                    <HD SOURCE="HD1">Subpart C—Process and Documentation Requirements </HD>
                    <P>This proposed subpart describes the requirements of carrying out the NEPA process, including establishing the roles of various governmental agencies and the public in the process, determining the appropriate level of environmental documentation under NEPA, and laying out the procedural requirements for processing NEPA documents. It complements and supplements the CEQ regulations that provide the general NEPA framework for the entire Federal government. In addition to the regulatory requirements described in this subpart, the FHWA's and FTA's comprehensive package of informational materials will provide detailed nonregulatory approaches to many of the subjects herein. </P>
                    <HD SOURCE="HD2">Section 1420.301 Responsibilities of the Participating Parties </HD>
                    <P>This is a new section that addresses some of the items currently contained within § 771.109. Paragraph (a) of the proposed section utilizes the current CEQ regulations (40 CFR 1500-1508) to define terms and set forth concepts, such as: Lead and cooperating agencies; the relationship between Federal agencies, applicants, and contractors; and enhancing the efficiency of the NEPA process through cooperation between Federal, State, and local agencies. </P>
                    <P>Paragraph (b) would clarify in regulation current practice for administering the NEPA process for projects implemented directly by the Federal government on Federal lands. Namely, it is a shared responsibility of the U.S. DOT and the Federal land management agency. The precise nature of the responsibility is specified in agreements or standard operating procedures. </P>
                    <P>In the previous regulations, the provision in 23 CFR 771.109(c) on agency responsibilities is largely repetitive of what is also found in CEQ's regulations on NEPA. For this rulemaking effort, we are reluctant to propose regulatory language which simply restates existing sections of another regulation, and would streamline this section accordingly. Paragraph (c) of the proposed section addresses the use of contractors in the NEPA process for contracting for environmental and engineering services. The proposed rule allows a State to procure the services of a consultant, under a single contract, for environmental impact assessment and for subsequent post-NEPA engineering and design work in accordance with the provisions of 23 U.S.C. 112(g), as amended by the TEA-21. </P>
                    <P>Section 1205 of the TEA-21 allows a State to procure under a single contract, the services of a consultant to prepare environmental documents for a project, and to perform subsequent final engineering and design work on the project. This would only occur if the State conducted a review assessing the objectivity of the environmental documentation. Experience has shown that, although on many projects consultants do prepare the bulk of the detailed analyses and NEPA documentation, this process involves close oversight by the State or local public agency and by the lead Federal agency. It is the ongoing responsibility of our agencies to ensure that all consultant work reflected in the NEPA process and documentation meets appropriate standards of objectivity and professionalism. </P>
                    <P>The contracting provisions were included in the TEA-21 to clarify our agencies' positions on the use of contractors for environmental and engineering design work for Federal transportation projects, and were chiefly aimed at addressing concerns of potential conflict of interest on the part of the consultants. </P>
                    <P>The U.S. DOT believes that more detailed nonregulatory guidance will best address the specifics of disclosure statements, other requirements of 40 CFR 1505.5(c), and the requirement for a review of the objectivity of the environmental document. </P>
                    <P>Generally speaking, commenters on the Options Paper felt that current level of oversight and review is sufficient, and that additional documentation to ensure objectivity is unnecessary. The EPA suggested the need for the development of Federal procedures for monitoring, investigating, and resolving conflicts that might result from this TEA-21 provision. </P>
                    <HD SOURCE="HD2">Section 1420.303 Interagency Coordination </HD>
                    <P>The proposed section would revise the current § 771.111 (a) through (e). The proposed section would simplify the current section by focusing on key terms and concepts that are the basis of an integrated decisionmaking process conducted under the NEPA umbrella. For example, the proposed section features the term “interagency coordination” to supplement the current “early coordination” in order to better express the collaborative intent of the FHWA/FTA NEPA process. The proposed section provides an explanation of the role and function of interagency coordination in the NEPA process. The term “interested agencies” would be added. The proposed section briefly outlines a procedure for notifying affected Federal, State, and local entities of the availability of approved documents for classes of action other than an EIS. </P>
                    <P>Scoping and early coordination can set the tone, positive or negative, for subsequent project development activities. Experience has shown that many of the conflicts which delay Federal approvals of highway and transit projects are somewhat predictable, and might be better anticipated and managed by using the scoping process as an early warning system. In addition, the development of interest-based negotiating and collaborative problem solving skills can help to craft implementable solutions. Two possible solutions emerged through the outreach process that could assist Federal agencies and applicants in performing more effective project scoping. One approach to the scoping of complex projects is that agencies agree on review schedules, but only after sufficient information on issues has emerged to allow them to gauge the required level of effort for their respective agencies. Another approach might make the scoping process, as part of an aggressive, high visibility project management role by our agencies as the lead Federal agenc(ies), a mechanism for identifying the issues, and agreeing on roles, time frames and methodologies associated with advancing the project, and possibly memorializing that agreement in a project MOU. </P>
                    <P>Both program reviews and feedback from stakeholders indicate that the FHWA and the FTA need to take a stronger leadership role in the NEPA process. Commenters including the National Coalition to Defend NEPA, the AASHTO, the American Road and Transportation Builders Association, and others reinforced this point in their comments on the Options Paper. These groups said that the FHWA and the FTA staff should attend meetings and serve as conflict resolution agents and mediators between other agencies. Also, they told us that we should provide information, such as, handbooks, best practices on scoping, and training for practitioners. As was the case in many areas, stakeholders including MPOs, State DOTs and others feel that much progress can be made in better integrating environmental and other considerations into the planning process through training, examples of where new approaches are working, handbooks and other useful materials. </P>
                    <P>
                        Many of the detailed considerations of the scoping process are outside the 
                        <PRTPAGE P="33971"/>
                        scope of this proposed rule, and will be addressed separately. Effective project scoping and interagency coordination is a chief topic of our environmental streamlining efforts, and will be given more detailed treatment in the comprehensive package of informational materials to be issued in conjunction with the final rule. Scoping may also be the subject of further guidance on its own. We will make full use of input received through the outreach efforts, as well as through our ongoing coordination with transportation and environmental agencies, in the development of this additional guidance. 
                    </P>
                    <HD SOURCE="HD2">Section 1420.305 Public Involvement </HD>
                    <P>Current § 771.111(h) would be redesignated as § 1420.305. It remains relatively unchanged for State DOTs except that the separate requirements specific to the FHWA and the FTA programs would be deleted; and new references specific to public involvement procedures, notification requirements, and accommodations for those with disabilities would be added. A requirement would be added to specifically ascertain if public involvement is warranted whenever a reevaluation is being conducted. Also a minimum 45-day public comment period would be established whenever public involvement procedures are initially adopted or revised. </P>
                    <P>The proposed rule also aims to consolidate requirements of our two agencies for public involvement so that the U.S. DOT can offer a more consistent approach on this subject. Based upon comments to the Options Paper, there was resounding support for a consistent approach to public involvement requirements between the FHWA and the FTA and this was cited by the National Coalition to Defend NEPA as one way to make the planning process more accessible and understandable to the public. This consolidation may mean that some transit agencies may have to formalize their public involvement procedures through board adoption, or revise their procedures to ensure their applicability to the NEPA process. The FTA does not expect to find many transit agencies without existing adopted procedures applicable to project development, but invites comment on this concern. We recognize the importance of public involvement to informed decisionmaking, and have issued a number of publications which provide nonregulatory guidance on how to increase the effectiveness of applicants' public involvement efforts. </P>
                    <P>The new § 1420.305(d) recognizes the need for public involvement on certain re-evaluations where the elapsed time may have altered public expectations. </P>
                    <HD SOURCE="HD2">Section 1420.307 Project Development and Timing of Activities </HD>
                    <P>Current § 771.113 would be redesignated as § 1420.307 and revised. The proposed section would clarify the circumstances in which the FHWA/FTA would not approve initiation and funding for certain activities, such as, final design activities. The proposed section would encourage compliance with the requirements of all applicable environmental laws, regulations, executive orders, and other related requirements be demonstrated prior to approval of the final environmental documents or categorical exclusion (CE) designation. Conditions under which agencies responsible for metropolitan and statewide planning would be notified in order to satisfy the planning and programming requirements of proposed 23 CFR part 1410 would be identified. </P>
                    <P>However, under the NPRM the FHWA and the FTA would not prevent State and local governments and private entities from taking certain actions that are “at risk” of being rendered useless by the final NEPA decision. Such actions include final design or land acquisition prior to NEPA approval, but do not include those that would have an adverse impact, such as, demolition or construction. The FHWA and the FTA would view at risk activities that actually substantially harm environment as so subverting the NEPA process that we would inform applicants that the action would be ineligible for FHWA or FTA financial assistance. The FHWA and the FTA would not finance such “at risk” actions, and would not allow their decisions to be influenced by the actions taken by others. For projects that will be federally-funded, the present regulation prohibits final design and land acquisition (with certain limited exceptions) prior to the completion of the NEPA process. The enforcement of this prohibition has been confounded by the fact that specific funding sources, especially for smaller projects, are often not identified until late in project development. Hence, the applicability of the Federal requirements that attach only to Federal funding sources is not yet determined at the time the “at risk” activities are initiated. </P>
                    <P>We are considering issuing guidance on how to handle such situations, especially in terms of disclosure responsibilities. </P>
                    <P>
                        We propose to clarify that full compliance with the transportation conformity rule (40 CFR parts 51 and 93) is required prior to the 
                        <E T="03">
                            approval of the final EIS, FONSI or CE 
                            <SU>5</SU>
                            <FTREF/>
                             designation.
                        </E>
                         As a result, this proposal would allow preliminary engineering for project development activities to be done prior to final NEPA approval without having to meet conformity requirements. We request public comment on our proposed clarification. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             Environmental Impact Statement (EIS), Finding of No Significant Impact (FONSI), categorical exclusion (CE).
                        </P>
                    </FTNT>
                    <P>We believe that this proposed change is allowed under current regulations. While the conformity rule requires that a project come from a conforming plan and transportation improvement program (TIP) before final NEPA approval, the rule does not explicitly specify that the project must be in a conforming plan and TIP in order to initiate the NEPA process. In fact, 40 CFR 93.126, table 2, identifies as exempt, “engineering to assess social, economic, and environmental effects of the proposed alternatives to that action.” We feel that this is an important distinction that may help to improve the quality of the NEPA process leading to more effective, efficient, and environmentally sound judgments, without compromising the planning process and air quality analysis. </P>
                    <P>We believe that the emissions impacts of the project should be considered as early as possible and continue to encourage the inclusion of projects in the plan and TIP conformity analysis as early as feasible prior to the completion of the NEPA process where it is feasible. Earlier inclusion of the project in the plan and TIP is beneficial for the overall development of the plan and TIP because regional analysis is used as a long term indicator of the area's emissions impacts and associated problems. Early analysis of projects in the plan and TIP allows a more comprehensive long term assessment of how emissions impacts can be minimized, whether through changes in the timing of projects or changes to the composition of the plan and TIP. </P>
                    <P>
                        However, a major problem with this approach is that it is counterproductive to corridor planning, prejudges alternatives and can limit thorough exploration of all feasible alternatives throughout the project development process. It can be counterproductive to, rather than supportive of, good long term transportation systems planning in certain circumstances. The reason for this is that in order for a project to be included in the regional plan and TIP and regional analysis prior to 
                        <PRTPAGE P="33972"/>
                        completion of NEPA, certain assumptions must be made about the project and related emissions impacts. It is difficult to define project design concept and scope that early in the planning process, especially for those projects requiring the highest level of environmental review and scrutiny. When taking complex projects through the project development process, it is very difficult to simply define two points of connection to the network, the number of lanes and facility type (that which is needed for regional analysis). Complex projects and corridor projects often examine multimodal options, some of which are not fully developed until later in the NEPA process. Under this scenario, the assumptions for regional analysis for conformity purposes may encourage an overly narrow alternatives analysis and constrain the environmental review process. We request comment on whether similar experiences have occurred in practice when accounting for preliminary engineering for project development in regional conformity analyses. 
                    </P>
                    <P>It is important to note that, under this proposal, preliminary development of new projects could proceed during a conformity lapse, since such activities would not need to meet conformity requirements. However, final NEPA documents on new projects could not be approved under this proposal until a new conforming plan and TIP are in place. </P>
                    <P>We believe the frequency requirements for conformity are sufficient to ensure that full emissions impacts of the projects are accounted for before projects move into the final design; therefore, long term risks are minimal and the projects must be included in the regional conformity emissions analysis prior to the completion of NEPA. The regional emissions analysis and conformity determinations can be made as frequently as once a year, but at a minimum at least every three years; therefore, it is reasonable to allow environmental reviews and the NEPA process to be initiated without the project being included in the conformity analysis. </P>
                    <HD SOURCE="HD2">Section 1420.309 Classes of Actions </HD>
                    <P>Current § 771.115 would be redesignated as § 1420.309 and the text would remain the same, except for the addition of certain intercity railroad and intermodal actions. </P>
                    <HD SOURCE="HD2">Section 1420.311 Categorical Exclusions </HD>
                    <P>
                        The proposed § 1430.311 would make several changes from the list of CEs in the current § 771.117 to reflect changes in the FHWA and the FTA programs since 1987. Modal limitations would be eliminated wherever possible. In addition, the CEs would be reordered and regrouped so that similar actions are listed together. The CEs would continue to be organized into two major groupings: those in paragraph (c) that require no further U.S. DOT agency approval, and those in paragraph (d) that require a written demonstration that the CE is appropriate. Paragraph (c) would clarify the need for NEPA approval by the U.S. DOT agency for listed CEs to which other environmental laws (
                        <E T="03">e.g.</E>
                        , section 106 of the National Historic Preservation Act) apply. 
                    </P>
                    <P>The proposed changes in CEs in paragraph (c) would be as follows: </P>
                    <P>Paragraph (c)(1) (non-construction activities) would incorporate the text of current § 771.117(c)(1), (c)(20), and part of (c)(16) without substantive change. It would add designations to the National Highway System to the list. </P>
                    <P>Paragraph (c)(2) (resurfacing) would move part of the text of current § 771.117(d)(1) to paragraph (c). Experience has shown that simple resurfacing of an existing pavement does not require additional written information for a CE determination. </P>
                    <P>Paragraph (c)(3) (routine maintenance) is not explicitly covered in the current § 771.117, but it is an important program activity, especially for transit with the re-definition of preventive maintenance as a capital expense. </P>
                    <P>Paragraph (c)(4) (ITS elements) is not explicitly covered in the text of current § 771.117. Installation of isolated ITS elements is proposed for paragraph (c), but an areawide coordination of multiple ITS elements that would have greater impact on the transportation system is proposed for paragraph (d)(2). </P>
                    <P>Paragraph (c)(5) (safety programs) would incorporate the text of current § 771.117(c)(4) and would add a current CE of the Federal Railroad Administration related to safety. </P>
                    <P>Paragraph (c)(6) (support facility improvements) would incorporate the current § 771.117(c)(12), but would extend it to cover toll facilities, control centers, and vehicle test centers, facilities that are similar in size and activity to those in the current CE. </P>
                    <P>Paragraph (c)(7) (carpool programs) uses a defined term to incorporate the text of current § 771.117(c)(13) except that carpool activities requiring land acquisition and construction (such as new parking lots) would be excluded and covered in paragraph (d)(6). </P>
                    <P>Paragraph (c)(8) (emergency repairs) would incorporate the text of current § 771.117(c)(9), but extends it to cover modes other than highways. </P>
                    <P>Paragraph (c)(9) (operating assistance) would incorporate the second part of the text of current § 771.117(c)(16) without substantive change. </P>
                    <P>Paragraph (c)(10) (vehicle acquisition) would incorporate the text of current § 771.117(c)(17) without substantive change. </P>
                    <P>Paragraph (c)(11) (purchase and lease of equipment) would incorporate the text of current § 771.117(c)(19), but would extend it to cover leases and the capital cost of contracting for transit services. </P>
                    <P>Paragraph (c)(12) (vehicle rehabilitation) would incorporate the current § 771.117(c)(14), but would extend it to cover conversions to alternative fuels. </P>
                    <P>Paragraph (c)(13) (track maintenance) would incorporate the text of current § 771.117(c)(18), but would extend it to cover wayside systems in addition to tracks and railbeds. </P>
                    <P>Paragraph (c)(14) (bicycle-pedestrian facilities) would incorporate the text of current § 771.117(c)(3) except that bicycle and pedestrian projects requiring land acquisition and construction (such as bike paths on new right-of-way) would be excluded and covered in paragraph (d)(19). </P>
                    <P>Paragraph (c)(15) (ADA accessibility) would incorporate the text of current § 771.117(c)(15) without substantive change. </P>
                    <P>Paragraph (c)(16) (signing, etc.) would incorporate the text of current § 771.117(c)(8) without substantive change. </P>
                    <P>Paragraph (c)(17) (property management) would incorporate the text of current § 771.117(c)(2), (5), and (11), and similar property management activities under the transit program. In addition, disposal of excess property would be moved from § 771.117(d)(6) because experience has shown that the sale or transfer of property does not have significant impact in and of itself, and the U.S. DOT agency does not have the statutory authority to control the subsequent use of property after it has been sold by the applicant. </P>
                    <P>
                        Paragraph (c)(18) (transportation enhancements) would incorporate the text of current § 771.117(c)(7) and (10), and would add other transportation enhancement activities and transit enhancements to the list. 
                        <PRTPAGE P="33973"/>
                    </P>
                    <P>Paragraph (c)(19) (noise walls) would incorporate the current § 771.117(c)(6) without substantive change. </P>
                    <P>Paragraph (c)(20) (mitigation banking) would be added due to the transportation enhancement provisions and changes in the mitigation policies of Federal resource agencies that allow or encourage this form of mitigation. </P>
                    <P>The proposed changes in CEs in paragraph (d) would be as follows: </P>
                    <P>Paragraph (d)(1) (highway rehabilitation) would incorporate the text of current § 771.117(d)(1) except that simple resurfacing is now proposed to be moved to paragraph (c) and would not require a written CE demonstration. </P>
                    <P>Paragraph (d)(2) (operational improvements) would incorporate part of the text of current § 771.117(d)(2), with clarification through examples of the ITS systems that would be covered. </P>
                    <P>Paragraph (d)(3) (safety improvements) would incorporate parts of the text of current § 771.117(d)(2) and (3) without substantive change. It would add safety-related programs of recent importance including seismic retrofit and mitigation of wildlife hazards. </P>
                    <P>Paragraph (d)(4) (bridge rehabilitation) would incorporate part of the text of current § 771.117(d)(3) with the clarification that the approaches to the bridge or tunnel would also be included in the project and that historic bridges and bridges providing access to ecologically sensitive areas are excluded. </P>
                    <P>
                        Paragraph (d)(5) (bridge replacement) would incorporate the remaining part of the text of current § 771.117(d)(3). If applicable, “section 106” (National Historic Preservation Act (16 U.S.C. 470 
                        <E T="03">et seq.</E>
                        )), “4(f)” (49 U.S.C. 303), “section 404” (Federal Water Pollution Control Act, as amended (33 U.S.C. 1251 to 1376)) and coastal zone management issues must be addressed in the CE documentation and coordinated with the other agencies in accordance with those statutes. 
                    </P>
                    <P>Paragraph (d)(6) (parking facilities) would incorporate activities from the current § 771.117(c)(13) and (d)(4), but would apply to all parking facilities, not just those on transportation fringes, if the CE conditions are met. </P>
                    <P>Paragraph (d)(7) (new operations centers) would be added as a CE primarily covering the construction of buildings to house the control centers from which ITS systems are operated and managed. </P>
                    <P>Paragraph (d)(8) (support facility construction) would incorporate the text of current § 771.117(d)(5) with the addition of other similarly sized support facilities. </P>
                    <P>Paragraph (d)(9) (access control) would incorporate the text of current § 771.117(d)(7) without substantive change. </P>
                    <P>Paragraph (d)(10) (track improvements) would incorporate the text of current § 771.117(c)(18) in situations where land acquisition is needed. </P>
                    <P>Paragraph (d)(11) (storage yards and shops) would incorporate the text of current § 771.117(d)(8) and (11) without substantive change. </P>
                    <P>Paragraph (d)(12) (building renovation) would incorporate the text of current § 771.117(d)(9) without substantive change. </P>
                    <P>Paragraph (d)(13) (transfer facilities) would incorporate the text of current § 771.117(d)(10) without substantive change. </P>
                    <P>Paragraph (d)(14) (ferry facilities) would be added as an explicit statement that work on existing ferry facilities may be a CE, but concern for water-related impacts necessitates its inclusion in paragraph (d) so that a written CE demonstration must be provided. </P>
                    <P>Paragraph (d)(15) (rail service demonstrations) would be added as a CE, based on our experience with previous similar cases. If the service demonstration were to lead to proposal for permanent service involving Federal financial support, that permanent project would be separately evaluated for its impacts. </P>
                    <P>Paragraph (d)(16) (advance land acquisition) would have three parts to it as follows: </P>
                    <P>(1) Paragraph (d)(16)(i) would allow the acquisition primarily of underutilized private railroad rights-of-way (ROW). It reflects current FTA practice where present or recent rail operations on the ROW ensure that adjacent land uses remain generally compatible with the continued transportation use of the ROW; </P>
                    <P>(2) Paragraph (d)(16)(ii) would respond to the provisions of the TEA-21 section 1301 without attempting to elaborate on those provisions. Such elaboration would be covered in separate guidance on the issue of advance land acquisition; and, </P>
                    <P>(3) Paragraph (d)(16)(iii) would incorporate the text of current § 771.117(d)(12) covering hardship and protective acquisitions, without substantive change. </P>
                    <P>Paragraph (d)(17) (joint development) would incorporate part of the text of current § 771.117(d)(6) without substantive change. </P>
                    <P>Paragraph (d)(18) (bicycle facilities) would incorporate activities covered in the text of current § 771.117(c)(3). With this change, bicycle projects involving land acquisition and construction would require a written CE demonstration. </P>
                    <P>Paragraph (d)(19) (storm water management) would add a new CE that covers a transportation enhancement activity that may involve land acquisition and construction of storm water detention or retention ponds. It is, therefore, proposed to be included in the list where a CE demonstration is required. </P>
                    <P>Paragraph (d)(20) (historic transportation facilities) would add a new CE that covers a transportation enhancement activity that will have section 106 (historic preservation) implications. It is, therefore, proposed to be included in the list where a CE demonstration is required. </P>
                    <P>Paragraph (d)(21) (other transportation enhancements) would add a new CE that covers the other transportation enhancement activities and transit enhancements that are not explicitly listed. </P>
                    <P>We propose additional, nonregulatory guidance on situations where a group of different, but related, categorically excluded actions may need to be evaluated as a whole if they have a net effect that warrants further environmental analysis (e.g., ITS projects throughout a corridor). </P>
                    <P>
                        Some commenters including the Michigan DOT, the AASHTO and others requested that advance right-of-way acquisition be added to the categorical exclusion list. The U.S. EPA was concerned about coordinating any expansions of the list with other Federal agencies and was particularly concerned about wetlands mitigation needs. The Ohio DOT suggested that rather than expand the list of categorical exclusions, our agencies develop “thresholds of significance” whereby projects within those thresholds would be those considered for categorical exclusions. Finally, a number of commenters, including the Ventura County Transportation Commission, the ARTBA, and the Oregon DOT supported the categorical exclusion of transportation enhancement activities and suggested categorically excluding congestion mitigation and air quality program (CMAQ) eligible projects. We have considered these comments in devising the proposed list. Nevertheless, we invite comment on these suggestions and on the appropriateness of the activities proposed to be categorically excluded, including whether or not specific activities should be included in the list under paragraph (c) or the list under paragraph (d). We encourage commenters to provide examples or information drawn from their 
                        <PRTPAGE P="33974"/>
                        experience bearing on the appropriateness of the proposed categorical exclusions. We also invite comments on the practice, begun with the 1987 regulation, of using an open-ended list of examples of activities that can be categorically excluded only after appropriate documentation has been prepared and approved on a case-by-case basis by the USDOT agency. 
                    </P>
                    <HD SOURCE="HD2">Section 1420.313 Environmental Assessments </HD>
                    <P>Current § 771.119 would be redesignated as § 1420.313 with some minor editing changes. </P>
                    <HD SOURCE="HD2">Section 1420.315 Findings of No Significant Impact </HD>
                    <P>Current § 771.121 would be redesignated as § 1420.121 with minor editing changes. </P>
                    <HD SOURCE="HD2">Section 1420.317 Draft Environmental Impact Statements </HD>
                    <P>The proposed section would revise the current § 771.123 by expanding the description of both public involvement procedures and the information products developed in accordance to the proposed 23 CFR part 1410. Paragraph (b) would specifically indicate that the scoping process must consider the results of the planning process including public involvement and interagency coordination. Items related to mitigation would be expanded to include environmental enhancements. Paragraph (b) would now emphasize public involvement and interagency coordination. Paragraph (c) would add language to our goals and policies in terms of implementing NEPA. The discussion on the use of consultants in the development of the draft EIS would be removed to avoid repetition with proposed § 1420.301. </P>
                    <HD SOURCE="HD2">Section 1420.319 Final Environmental Impact Statements </HD>
                    <P>Current § 771.125 would be redesignated as § 1420.319. Information would be added in paragraph (a)(1) to require any additional environmental studies, public involvement, and/or coordination to consider refinements of alternatives and mitigation to be presented in the FEIS. </P>
                    <HD SOURCE="HD2">Section 1420.321 Record of Decision </HD>
                    <P>Current § 771.127 would be redesignated as § 1420.321. In paragraph (a), the information about preparation of the notice of availability would be expanded to indicate where and to whom the notice should be provided. In paragraph (c), wording would be added to emphasize that mitigation and enhancement features associated with the selected alternative become enforceable conditions of any U.S. DOT actions. </P>
                    <HD SOURCE="HD2">Section 1420.323 Re-evaluations </HD>
                    <P>Current § 771.129 would be redesignated as § 1420.323. Paragraphs (a) through (c) are essentially unchanged from the current regulation. Paragraph (d) has been added to ensure public involvement and interagency coordination when the situation warrants. Guidance will be provided on this subject. We invite comment on how effective the proposed reevaluation provision would be in addressing projects which are implemented over an extended period of time, with construction occurring under multiple contracts. We also invite comment on the appropriate role of public involvement in reevaluations. </P>
                    <HD SOURCE="HD2">Section 1420.325 Supplemental Environmental Impact Statements </HD>
                    <P>Current § 771.130 would be redesignated as § 1420.325. It is essentially unchanged from the current regulation except that supplementation now includes consideration of public involvement and interagency coordination.</P>
                    <HD SOURCE="HD1">Section-by-Section Analysis of the Proposed Rule on Protection of Public Parks, Wildlife and Waterfowl Refuges, and Historic Sites </HD>
                    <P>For ease of reference, a distribution table is provided for the current sections and proposed sections as follows: </P>
                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,xs150">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">Current Section </CHED>
                            <CHED H="1">Proposed Section </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1430.101 Purpose. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">771.109(a)(1) and(2) and part of 771.135(b) </ENT>
                            <ENT>1430.105 Applicability. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">771.135(a) </ENT>
                            <ENT>1430.103 Mandate. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">771.135(c) and (e) </ENT>
                            <ENT>1430.109 Significance. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">771.135(p)(1),(2),(4), and (7) </ENT>
                            <ENT>1430.107 Use of land. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">771.135(d),(f),(g),(h), and (p)(5) </ENT>
                            <ENT>1430.111 Exceptions. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">771.135(a)(2), part of (b), part of (i), (j),(k),(l),(p)(3), and (p)(6) </ENT>
                            <ENT>1430.113 Evaluations under NEPA. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">771.135(m) and (o) </ENT>
                            <ENT>1430.115 Separate evaluations. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">771.135(i)[last sentence] </ENT>
                            <ENT>1430.117 Programmatic evaluations. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">771.135(o) </ENT>
                            <ENT>1430.119 Linkage to planning. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">None </ENT>
                            <ENT>1430.121 Definitions. </ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD2">Section 1430.101 Purpose </HD>
                    <P>This new section would be added to state that this regulation implements 49 U.S.C. 303 and 23 U.S.C. 138 (section 4(f)). </P>
                    <HD SOURCE="HD2">Section 1430.103 Mandate </HD>
                    <P>Current § 771.135(a)(1) would be redesignated as § 1430.103 without substantive change in text. </P>
                    <HD SOURCE="HD2">Section 1430.105 Applicability </HD>
                    <P>Current §§ 771.109(a)(1) and (2) provide the basis for this proposed section. Also, part of § 771.135(b) would be incorporated to make clear that the U.S. DOT agency decides the applicability of section 4(f). </P>
                    <HD SOURCE="HD2">Section 1430.107 Use of Land </HD>
                    <P>Current § 771.135(p)(1), (2), (4), and (7) would be redesignated as § 1430.107 without substantive change. </P>
                    <HD SOURCE="HD2">Section 1430.109 Significance of the Section 4(f) Resource </HD>
                    <P>Current § 135(c) and (e) would be redesignated as § 1430.109 without substantive change. </P>
                    <HD SOURCE="HD2">Section 1430.111 Exceptions </HD>
                    <P>
                        Current § 771.135(d), (g), (h), and (p)(5) would be redesignated as § 1430.111 without substantive change. The proposed section also incorporates the current § 771.135(f), except that the consultation requirement has been modified to be consistent with the new 36 CFR part 800 recently published by the Advisory Council on Historic Preservation. As proposed, the provision is silent with respect to the relationship between “adverse effects” under 36 CFR part 800 and “constructive use” under this regulation. We invite comment as to whether or not a specific relationship should be established in this regulation. We also invite comment as to other measures that we might take to better 
                        <PRTPAGE P="33975"/>
                        coordinate the section 4(f) process with the process established under 36 CFR 800. The proposed section also has three new provisions in paragraphs (a), (b), and (c), stating that section 4(f) would not apply to park roads, parkways, trails, transportation enhancement activities, and transit enhancements where the purpose of the U.S. DOT agency approval of transportation funding is to improve the section 4(f) resource. 
                    </P>
                    <HD SOURCE="HD2">Section 1430.113 Section 4(f) Evaluations and Determinations Under the NEPA Umbrella </HD>
                    <P>Current § 771.135(a)(2), (j), (k), (l), (p)(3), (p)(6), most of (i), and part of (b) would be redesignated as § 1430.113 without substantive change. The proposed section also would include a new provision in proposed paragraph (b) allowing consideration of the products of the planning process in the section 4(f) evaluation. Both the current and proposed regulation continue to codify in regulation language of the Supreme Court decision in Overton Park (401 U.S. 402 (1971)) that an avoidance alternative must be preferred unless the evaluation demonstrates that there are “unique problems or unusual features associated with it, or that the cost, the social, economical, or environmental impacts, or the community disruption resulting from such alternatives reach extraordinary magnitudes.” We invite comment on whether or not this standard deserves further definition in regulation or in guidance in light of changes to the highway program in the years since the court's decision. In particular, we would appreciate views on whether or not the qualitative importance or value of the section 4(f) resource should be explicitly taken into account in determining whether or not an avoidance alternative is “feasible and prudent,” especially when balancing the impacts of the various alternatives. </P>
                    <HD SOURCE="HD2">Section 1430.115 Separate Section 4(f) Evaluations </HD>
                    <P>Current § 771.135(m) and (n) would be redesignated as § 1430.115 without substantive change. </P>
                    <HD SOURCE="HD2">Section 1430.117 Programmatic Section 4(f) Evaluations</HD>
                    <P>The last sentence of current § 771.135(i) would be redesignated as § 1430.117, including a new explanatory introductory sentence. The proposed provision would provide a clear regulatory basis for programmatic section 4(f) evaluations and approvals, a practice which the Department of Transportation has used from time to time. For example, programmatic section 4(f) evaluations have been prepared for the following situations: Bikeways, historic bridges, projects involving minimal use of property for historic properties and projects involving minimal use of parkland. We invite suggestions of additional situations that would be appropriate subjects of future programmatic section 4(f) evaluations. </P>
                    <HD SOURCE="HD2">Section 1430.119 Linkage with Transportation Planning</HD>
                    <P>Current § 771.135(o) would be redesignated as § 1430.119 and would remain substantively unchanged except that the concept of a preliminary section 4(f) evaluation has been extended to the planning process in exactly the same way it previously applied to first-tier EISs. </P>
                    <HD SOURCE="HD2">Section 1430.121 Definitions </HD>
                    <P>A new § 1430.121 would be added to provide a consistent set of definitions of terms used in the planning regulations (23 CFR part 1410), the NEPA regulation (23 CFR part 1420), and this regulation (23 CFR part 1430). </P>
                    <HD SOURCE="HD1">Rulemaking Analyses and Notices </HD>
                    <P>All comments received before the close of business on the comment closing date indicated above will be considered and will be available for examination using the docket number appearing at the top of this document in the docket room at the above address or via the electronic addresses provided above. The FHWA and the FTA will file comments received after the comment closing date in the docket and will consider late comments to the extent practicable. The FHWA and the FTA may, however, issue a final rule at any time after the close of the comment period. In addition to late comments, the FHWA and the FTA will also continue to file in the docket relevant information becoming available after the comment closing date, and interested persons should continue to examine the docket for new material. </P>
                    <HD SOURCE="HD1">Executive Order 12866 (Regulatory Planning and Review) and DOT Regulatory Policies and Procedures </HD>
                    <P>We have determined that this proposed action is a significant regulatory action within the meaning of Executive Order 12866, and under the Department of Transportation regulatory policies and procedures because of substantial State, local government, congressional, and public interest. These interests involve receipt of Federal financial support for transportation investments, appropriate compliance with statutory requirements, and balancing of transportation mobility and environmental goals. We anticipate that the economic impact of this rulemaking will be minimal. Most costs associated with these rules are attributable to the provisions of the TEA-21, the ISTEA, the Clean Air Act (as amended), and other statutes including earlier highway acts. </P>
                    <P>We consider this proposal to be a means to simplify, clarify, and reorganize existing regulatory requirements. There have been no changes to NEPA or CEQ regulations. These rules would merely revise existing NEPA regulations of the FHWA and the FTA and conform those regulations to the environmental streamlining requirements of TEA-21. In response to congressional direction in TEA-21, the U.S. DOT is proposing to implement improved coordinated environmental review processes for highway and transit projects. States have been carrying out statewide transportation planning activities with title 23, U.S.C., and FTA planning and research funds for many years. Neither the individual nor the cumulative impact of this action would be significant because this action would not alter the funding levels available to the States for Federal or federally-assisted programs covered by the TEA-21. </P>
                    <P>The amendments impose no additional requirements. The environmental streamlining process under section 1309 of TEA-21 establishes coordinated environmental review processes by which U.S. DOT would work with other Federal agencies to assure that major highway and transit projects are advanced according to cooperatively determined time frames. Such processes have been incorporated into a memorandum of understanding between U.S. DOT and other Federal agencies. </P>
                    <HD SOURCE="HD1">Regulatory Flexibility Act </HD>
                    <P>
                        In compliance with the Regulatory Flexibility Act (5 U.S.C. 601-602), we have evaluated the effects of this rule on small entities, such as local governments and businesses. The TEA-21 provides the flexibility for these agencies to provide the resources necessary to meet any time limits established under environmental streamlining. Additionally, the FHWA has issued guidance concerning transportation funding for Federal agency coordination using a full range of options for reimbursement under appropriate authorities. Accordingly, the FHWA and the FTA certify that this action would not have a significant economic impact on a substantial 
                        <PRTPAGE P="33976"/>
                        number of small entities. This proposed action would merely update and clarify existing procedures. We specifically invite comments on the projected economic impact of this proposal, and will actively consider such information before completing our Regulatory Flexibility Act analysis when adopting final rules. 
                    </P>
                    <HD SOURCE="HD1">Environmental Impacts </HD>
                    <P>
                        We have also analyzed this proposed action for the purpose of the National Environmental Policy Act (42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                        ), and preliminarily conclude that this action would not have any effect on the quality of the human and natural environment and is therefore categorically excluded under 23 CFR 771.117(c)(20). The TEA-21 directs the implementation of a coordinated environmental review process for highway construction projects, yet, also ensures that such concurrent review shall not result in a significant adverse impact to the environment or substantively alter the operation of Federal law. Time periods for review shall be consistent with time periods established by the Council on Environmental Quality under 40 CFR 1501.8 and 1506.10. As stated in the TEA-21, nothing in section 1309 (the environmental streamlining section) shall affect the applicability of NEPA or any other Federal environmental statute or affect the responsibility of any Federal officer to comply with or enforce any such statute. 
                    </P>
                    <HD SOURCE="HD1">Executive Order 13132 (Federalism Assessment) </HD>
                    <P>This proposed action has been analyzed in accordance with the principles and criteria contained in Executive Order 13132, dated August 4, 1999, and it has been determined that this action does not have a substantial direct effect or sufficient Federalism implications on States and local governments that would limit the policymaking discretion of the States. Nothing in this document directly preempts any State law or regulation. The TEA-21 directs the DOT to establish an integrated NEPA review and permitting process and to encourage approvals as early as possible in the scoping and planning process, yet also to maintain an emphasis on a strong environmental policy. Throughout the proposed regulation there is an effort to keep administrative burdens to a minimum. </P>
                    <HD SOURCE="HD1">Executive Order 12372 (Intergovernmental Review) </HD>
                    <P>Catalog of Federal Domestic Assistance Program Number 20.205, Highway planning and construction (or 20.217, Motor Carrier Safety). The regulations implementing Executive Order 12372 regarding intergovernmental consultation on Federal programs and activities apply to this program. </P>
                    <HD SOURCE="HD1">Unfunded Mandates Reform Act of 1995 </HD>
                    <P>
                        This rule does not impose a Federal mandate resulting in the expenditure by State, local, tribal governments, in the aggregate, or by the private sector, of $100 million or more in any one year. (2 U.S.C. 1531 
                        <E T="03">et seq.</E>
                        ). 
                    </P>
                    <HD SOURCE="HD1">Paperwork Reduction Act </HD>
                    <P>This proposal contains no new collection of information requirements for purposes of the Paperwork Reduction Act of 1995, 44 U.S.C. 3501-3520. This notice of proposed rulemaking would encourage the coordination of approvals by Federal agencies involved in the NEPA process and could reduce the level of recordkeeping. </P>
                    <P>The information prepared by non-Federal parties pursuant to this proposed regulation is exempt from the requirements of the Paperwork Reduction Act. First, the collection of information does not entail reporting of information in response to identical questions. NEPA documents do not involve answering specific questions; they address issues relating to the requirements of multiple Federal environmental statutes. There are too many variables relating to the proposed action, the location in which the action is to be taken, and the statutes that are implicated (and to what extent) to permit a standardized format or content. The issues to be addressed in NEPA documents are therefore determined on a case by case basis. Each is a one of a kind document. </P>
                    <P>Second, the information is not requested of non-Federal entities but of Federal agencies. The State and local transportation departments and transit agencies compiling information are voluntarily serving as consultants to FHWA and FTA for their own convenience. As the proposers of the actions subject to NEPA, and the owners, operators, and maintainers of the resulting facility, and key decisionmakers regarding the choices involved in project development, it is easier for them to prepare the NEPA documents. Information is not requested of outside entities except within the PRA exception relating to “facts or opinions submitted in response from general solicitations of comments for the general public (5 CFR 1320.3(h)(4).” </P>
                    <P>Third, State and local departments of transportation and transit agencies develop this information reported to FHWA/FTA as a normal part of doing business. NEPA documents contain engineering and environmental information that is integral to developing projects in a way that conforms to State and local laws. The development of engineering and environmental information is an unavoidable step in project development whether or not the Federal government is involved. We invite comments on this analysis. </P>
                    <HD SOURCE="HD1">Executive Order 12630 (Taking of Private Property) </HD>
                    <P>This rule will not effect 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="HD1">Executive Order 12988 (Civil Justice Reform) </HD>
                    <P>This action 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="HD1">Executive Order 13045 (Protection of Children) </HD>
                    <P>We have analyzed this action under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not concern an environmental risk to healthy or safety that may disproportionately affect children. </P>
                    <HD SOURCE="HD1">Regulation Identification Number </HD>
                    <P>A regulation identification number (RIN) is assigned to each regulatory action listed in the Unified Agenda of Federal Regulations. The Regulatory Information Service Center publishes the Unified Agenda in April and October of each year. The RIN contained in the heading of this document can be used to cross reference this action with the Unified Agenda. </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects </HD>
                        <CFR>23 CFR Part 771 </CFR>
                        <P>Environmental protection, Grant programs—transportation, Highways and roads, Historic preservation, Public lands, Recreation areas, Reporting and recordkeeping requirements. </P>
                        <CFR>23 CFR Part 1420 </CFR>
                        <P>
                            Environmental impact statements, Grant programs—transportation, Highways and roads, Mass 
                            <PRTPAGE P="33977"/>
                            transportation, Reporting and recordkeeping requirements. 
                        </P>
                        <CFR>23 CFR Part 1430 </CFR>
                        <P>Environmental protection, Grant programs—transportation, Highways and roads, Historic preservation, Mass transportation, Public lands, Recreation areas, Reporting and recordkeeping requirements, Wildlife refuges. </P>
                        <CFR>49 CFR Part 622 </CFR>
                        <P>Environmental impact statements, Grant programs—transportation, Mass transportation, Reporting and recordkeeping requirements. </P>
                        <CFR>49 CFR Part 623 </CFR>
                        <P>Environmental protection, Grant programs—transportation, Mass Transportation, Public lands, Recreation areas, Reporting and recordkeeping requirements, Wildlife refuges.</P>
                    </LSTSUB>
                    <HD SOURCE="HD1">Federal Highway Administration </HD>
                    <LSTSUB>
                        <HD SOURCE="HED"> </HD>
                        <CFR>23 CFR Chapter I </CFR>
                        <P>For reasons set forth in the preamble, and under the authority of 23 U.S.C. 109, 128, 134, 138, and 315, the Federal Highway Administration proposes to amend Chapter I of title 23, Code of Federal Regulations, as follows:</P>
                    </LSTSUB>
                    <PART>
                        <HD SOURCE="HED">PART 771—[REMOVED] </HD>
                        <P>1. Remove part 771. </P>
                    </PART>
                    <LSTSUB>
                        <HD SOURCE="HED"> </HD>
                        <CFR>23 CFR Chapter IV </CFR>
                        <P>
                            For reasons set forth in the preamble, the Federal Highway Administration and the Federal Transit Administration propose to amend proposed Chapter IV in title 23, Code of Federal Regulations (published elsewhere in this 
                            <E T="04">Federal Register</E>
                            ), as set forth below:
                        </P>
                    </LSTSUB>
                    <P>2. Add parts 1420 and 1430 to read as follows: </P>
                    <PART>
                        <HD SOURCE="HED">PART 1420—NEPA AND RELATED PROCEDURES FOR TRANSPORTATION DECISIONMAKING</HD>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart A—Purpose, Policy, and Mandate </HD>
                        </SUBPART>
                        <CONTENTS>
                            <SECHD>Sec. </SECHD>
                            <SECTNO>1420.101</SECTNO>
                            <SUBJECT>Purpose. </SUBJECT>
                            <SECTNO>1420.103</SECTNO>
                            <SUBJECT>Relationship of this regulation to the CEQ regulation and other guidance. </SUBJECT>
                            <SECTNO>1420.105</SECTNO>
                            <SUBJECT>Applicability of this part. </SUBJECT>
                            <SECTNO>1420.107</SECTNO>
                            <SUBJECT>Goals of the NEPA process. </SUBJECT>
                            <SECTNO>1420.109 </SECTNO>
                            <SUBJECT>The NEPA umbrella. </SUBJECT>
                            <SECTNO>1420.111 </SECTNO>
                            <SUBJECT>Environmental justice. </SUBJECT>
                            <SECTNO>1420.113 </SECTNO>
                            <SUBJECT>Avoidance, minimization, mitigation, and enhancement responsibilities.</SUBJECT>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart B—Program and Project Streamlining </HD>
                                <SECTNO>1420.201 </SECTNO>
                                <SUBJECT>Relation of planning and project development processes. </SUBJECT>
                                <SECTNO>1420.203 </SECTNO>
                                <SUBJECT>Environmental streamlining. </SUBJECT>
                                <SECTNO>1420.205 </SECTNO>
                                <SUBJECT>Programmatic approvals. </SUBJECT>
                                <SECTNO>1420.207 </SECTNO>
                                <SUBJECT>Quality assurance process. </SUBJECT>
                                <SECTNO>1420.209 </SECTNO>
                                <SUBJECT>Alternate procedures. </SUBJECT>
                                <SECTNO>1420.211 </SECTNO>
                                <SUBJECT>Use of this part by other U.S. DOT agencies. </SUBJECT>
                                <SECTNO>1420.213 </SECTNO>
                                <SUBJECT>Emergency action procedures. </SUBJECT>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart C—Process and Documentation Requirements </HD>
                                <SECTNO>1420.301 </SECTNO>
                                <SUBJECT>Responsibilities of the participating parties. </SUBJECT>
                                <SECTNO>1420.303 </SECTNO>
                                <SUBJECT>Interagency coordination. </SUBJECT>
                                <SECTNO>1420.305 </SECTNO>
                                <SUBJECT>Public involvement. </SUBJECT>
                                <SECTNO>1420.307 </SECTNO>
                                <SUBJECT>Project development and timing of activities. </SUBJECT>
                                <SECTNO>1420.309 </SECTNO>
                                <SUBJECT>Classes of actions. </SUBJECT>
                                <SECTNO>1420.311 </SECTNO>
                                <SUBJECT>Categorical exclusions. </SUBJECT>
                                <SECTNO>1420.313 </SECTNO>
                                <SUBJECT>Environmental assessments. </SUBJECT>
                                <SECTNO>1420.315 </SECTNO>
                                <SUBJECT>Findings of no significant impact. </SUBJECT>
                                <SECTNO>1420.317 </SECTNO>
                                <SUBJECT>Draft environmental impact statements. </SUBJECT>
                                <SECTNO>1420.319 </SECTNO>
                                <SUBJECT>Final environmental impact statements. </SUBJECT>
                                <SECTNO>1420.321 </SECTNO>
                                <SUBJECT>Record of decision. </SUBJECT>
                                <SECTNO>1420.323 </SECTNO>
                                <SUBJECT>Re-evaluations. </SUBJECT>
                                <SECTNO>1420.325 </SECTNO>
                                <SUBJECT>Supplemental environmental impact statements.</SUBJECT>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart D—Definitions </HD>
                                <SECTNO>1420.401 </SECTNO>
                                <SUBJECT>Terms defined elsewhere. </SUBJECT>
                                <SECTNO>1420.403 </SECTNO>
                                <SUBJECT>Terms defined in this part.</SUBJECT>
                            </SUBPART>
                        </CONTENTS>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                23 U.S.C. 109, 128, 134, 138 and 315; 42 U.S.C. 2000d-2000d-4, 4321 
                                <E T="03">et seq.</E>
                                , and 7401 
                                <E T="03">et seq.</E>
                                ; 49 U.S.C. 303, 5301(e), 5303, 5309, and 5324 (b) and (c); 49 CFR 1.48, and 1.51; 33 CFR 115.60(b); 40 CFR parts 1500-1508. 
                            </P>
                        </AUTH>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart A—Purpose, Policy, and Mandate </HD>
                            <SECTION>
                                <SECTNO>§ 1420.101 </SECTNO>
                                <SUBJECT>Purpose. </SUBJECT>
                                <P>The purpose of this part is to establish policies and procedures of the Federal Highway Administration (FHWA) and the Federal Transit Administration (FTA) for implementing the National Environmental Policy Act of 1969 (NEPA) as amended, and to supplement the regulation of the Council on Environmental Quality (CEQ), 40 CFR parts 1500 through 1508. In concert with 23 CFR 1410 this part sets forth a NEPA process that integrates and streamlines the compliance with all applicable transportation and environmental laws that govern Federal transportation decisionmaking. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.103 </SECTNO>
                                <SUBJECT>Relationship of this regulation to the CEQ regulation and other guidance. </SUBJECT>
                                <P>The CEQ regulation lays out NEPA responsibilities for all Federal agencies. This FHWA/FTA regulation supplements the CEQ regulation with specific provisions regarding the FHWA/FTA approach to implementing NEPA for the Federal surface transportation actions under their jurisdiction. For a full understanding of NEPA responsibilities relative to the FHWA/FTA actions, the reader must refer to both this regulation and the CEQ regulation. In addition, the FHWA/FTA will rely on nonregulatory guidance materials, training courses, and documentation of best practices in the management of their NEPA responsibilities. The available materials and training course schedules are posted on the FHWA and the FTA web sites and can be obtained by contacting Planning and Environment Program Manager, Federal Highway Administration, Washington, DC 20590 or Associate Administrator for Planning, Federal Transit Administration, Washington, DC 20590. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.105 </SECTNO>
                                <SUBJECT>Applicability of this part. </SUBJECT>
                                <P>(a)(1) The provisions of this part and the CEQ regulation apply to actions where a U.S. DOT agency exercises sufficient control and has the statutory authority to condition the action or approval. Actions taken by the applicant or others that do not require any U.S. DOT agency approval or over which a U.S. DOT agency has no discretion, including, but not limited to, projects or maintenance on Federal-aid highways or transit systems not involving Federal-aid funds or approvals, and actions from which the U.S. DOT agency are excluded by law or regulation, are not subject to this part. </P>
                                <P>(2) This part does not apply to, or alter approvals by the U.S. DOT agencies made prior to the effective date of this part. </P>
                                <P>(3) NEPA documents accepted or prepared by the U.S. DOT agency after the effective date of this part shall be developed in accordance with this part. </P>
                                <P>(b) In order to ensure meaningful evaluation of alternatives and to avoid commitments to transportation improvements before they are fully evaluated, the actions covered by each environmental impact statement (EIS) or environmental assessment (EA), or designated a categorical exclusion (CE) shall: </P>
                                <P>(1) Have independent utility or independent significance, i.e., be usable and be a reasonable expenditure even if no additional transportation improvements in the area are made; </P>
                                <P>(2) Connect logical termini, if linear in configuration, and be of sufficient length or size to address environmental matters over a sufficiently wide area that all reasonably foreseeable impacts are considered; and </P>
                                <P>
                                    (3) Not restrict consideration of alternatives for other reasonably 
                                    <PRTPAGE P="33978"/>
                                    foreseeable transportation improvements. 
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.107 </SECTNO>
                                <SUBJECT>Goals of the NEPA process. </SUBJECT>
                                <P>(a) It is the intent of the U.S. DOT agencies that the NEPA principles of environmental stewardship and the Transportation Equity Act for the 21st Century (TEA-21) objective of timely implementation of transportation facilities and provision of transportation services should guide Federal, State, local, and tribal decisionmaking on all transportation actions subject to these laws. Accordingly, in administering their responsibilities under numerous transportation and environmental laws, the U.S. DOT agencies will manage the NEPA process to maximize attainment of the following goals: </P>
                                <P>
                                    (1) 
                                    <E T="03">Environmental ethic.</E>
                                     Federal actions reflect concern for, and responsible choices that preserve, communities and the natural environment, in accordance with the purpose and policy direction of NEPA (42 U.S.C. 4321 and 4331), and the specific mandates of statutes, regulations, and executive orders. 
                                </P>
                                <P>
                                    (2) 
                                    <E T="03">Environmental justice.</E>
                                     Disproportionate adverse effects on minority and low income populations are identified and addressed; no person, because of handicap, age, race, color, sex, or national origin, is excluded from participating in, denied the benefits of, or subject to discrimination under any U.S. DOT agency program or activity conducted in accordance with this regulation. 
                                </P>
                                <P>
                                    (3) 
                                    <E T="03">Integrated decisionmaking.</E>
                                     Federal transportation approvals are coordinated in a logical fashion with other Federal reviews and approvals, and with State, local, and tribal governmental actions, and actions by private entities, in recognition of interdependencies of decisions by the various parties and the procedural umbrella that the NEPA process provides for facilitating decisionmaking. 
                                </P>
                                <P>
                                    (4) 
                                    <E T="03">Environmental streamlining.</E>
                                     Federal transportation and environmental reviews and approvals are completed in a timely fashion through a coordinated review process. 
                                </P>
                                <P>
                                    (5) 
                                    <E T="03">Collaboration.</E>
                                     Transportation decisions are made through a collaborative partnership involving Federal, State, local, and tribal agencies, communities, interest groups, private businesses, and interested individuals. 
                                </P>
                                <P>
                                    (6) 
                                    <E T="03">Transportation problem solving.</E>
                                     Transportation decisions represent cost effective solutions to current and future problems based on an interdisciplinary evaluation of alternative courses of action. 
                                </P>
                                <P>
                                    (7) 
                                    <E T="03">Financial stewardship.</E>
                                     Public funds are used to achieve the maximum benefit for the financial investment in accordance with governing statutes and regulations. 
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.109 </SECTNO>
                                <SUBJECT>The NEPA umbrella. </SUBJECT>
                                <P>(a) In keeping with the above goals, it is the policy of the FHWA/FTA that the NEPA process be the means of bringing together all legal responsibilities, issues, and interests relevant to the transportation decision in a logical way to evaluate alternative courses of action, and that it lead to a single final decision regarding the key characteristics of a proposed action (such as, location, major design features, mitigation measures, and environmental enhancements). This decision shall be made in the best overall public interest based on a balanced consideration of the need for safe and efficient transportation; the social, economic, and environmental benefits and impacts of the proposed action; and the attainment of national, State, tribal, and local environmental protection goals. </P>
                                <P>(b) Any environmentally related study, review, or consultation required by Federal law should be conducted within the framework of the NEPA process to assure integrated and efficient decisionmaking. The State is encouraged to conduct its activities during the NEPA process toward the same goal. </P>
                                <P>(c) Federal responsibilities to be addressed in the NEPA process whenever applicable to the decision on the proposed action include, but are not limited to the following protections of: </P>
                                <P>
                                    (1) 
                                    <E T="03">Individual rights:</E>
                                </P>
                                <P>(i) Title VI of the Civil Rights Act of 1964 (42 U.S.C. 2000d-2000d-4) and related statutes; </P>
                                <P>
                                    (ii) Uniform Relocation Assistance and Real Property Acquisition Policies Act of 1970 (42 U.S.C. 4601 
                                    <E T="03">et seq.</E>
                                    ), as amended; 
                                </P>
                                <P>
                                    (iii) Americans with Disabilities Act (42 U.S.C. 12101 
                                    <E T="03">et seq.</E>
                                    ); 
                                </P>
                                <P>(iv) 49 U.S.C. 5332, nondiscrimination; </P>
                                <P>(v) 49 U.S.C. 5324(a), relocation requirements; </P>
                                <P>(vi) 23 U.S.C. 128 and 49 U.S.C. 5323(b), public hearing requirements; </P>
                                <P>
                                    (2) 
                                    <E T="03">Communities and community resources:</E>
                                </P>
                                <P>(i) Executive Order 12898 (59 FR 7629, 3 CFR, 1995 comp., p. 859), environmental justice for minority and low-income populations; </P>
                                <P>(ii) 49 U.S.C. 303, protection of public parks and recreation areas; </P>
                                <P>(iii) 23 U.S.C. 109(h), economic, social, and environmental effects of highways; </P>
                                <P>(iv) 49 U.S.C. 5324(b), economic, social, and environmental effects of transit;</P>
                                <P>(v) 23 U.S.C. 109(i), highway noise standards;</P>
                                <P>
                                    (vi) Clean Air Act (23 U.S.C. 109(j), 42 U.S.C. 7509 and 7521(a) 
                                    <E T="03">et seq.</E>
                                    ), as amended;
                                </P>
                                <P>(vii) Safe Drinking Water Act (42 U.S.C. 201 and 300);</P>
                                <P>(viii) Farmland Protection Policy Act of 1981 (7 U.S.C. 4201-4209);</P>
                                <P>(ix) National Flood Insurance Act (42 U.S.C. 1401, 2414, 4001 to 4127);</P>
                                <P>
                                    (x) Solid Waste Disposal Act (Public Law 89-272; 42 U.S.C. 6901 
                                    <E T="03">et seq.</E>
                                    );
                                </P>
                                <P>
                                    (xi) Resource Conservation and Recovery Act of 1976 (42 U.S.C. 6901 
                                    <E T="03">et seq.</E>
                                    );
                                </P>
                                <P>
                                    (xii) Comprehensive Environmental Response, Compensation, and Liability Act of 1980 (42 U.S.C. 9601 
                                    <E T="03">et seq.</E>
                                    );
                                </P>
                                <P>(xiii) Emergency Planning and Community Right to Know Act of 1986 (42 U.S.C. 11001 to 11050);</P>
                                <P>
                                    (3)
                                    <E T="03">Cultural resources and aesthetics:</E>
                                </P>
                                <P>(i) 49 U.S.C. 303, protection of historic sites;</P>
                                <P>
                                    (ii) National Historic Preservation Act (16 U.S.C. 470 
                                    <E T="03">et seq.</E>
                                    );
                                </P>
                                <P>(iii) 23 U.S.C. 109(h), economic, social, and environmental effects of highways;</P>
                                <P>(iv) 49 U.S.C. 5324(b), economic, social, and environmental effects of transit; </P>
                                <P>(v) 23 U.S.C. 109(i), highway noise standards; </P>
                                <P>
                                    (vi) Clean Air Act (23 U.S.C. 109(j), 42 U.S.C. 7509 and 7521(a) 
                                    <E T="03">et seq.</E>
                                    ), as amended; 
                                </P>
                                <P>(vii) Safe Drinking Water Act (42 U.S.C. 201 and 300); </P>
                                <P>(viii) Farmland Protection Policy Act of 1981 (7 U.S.C. 4201-4209); </P>
                                <P>(ix) National Flood Insurance Act (42 U.S.C. 1401, 2414, 4001 to 4127); </P>
                                <P>
                                    (x) Solid Waste Disposal Act (Public Law 89-272; 42 U.S.C. 6901 
                                    <E T="03">et seq.</E>
                                    ); 
                                </P>
                                <P>
                                    (xi) Resource Conservation and Recovery Act of 1976 (42 U.S.C. 6901 
                                    <E T="03">et seq.</E>
                                    ); 
                                </P>
                                <P>
                                    (xii) Comprehensive Environmental Response, Compensation, and Liability Act of 1980 (42 U.S.C. 9601 
                                    <E T="03">et seq.</E>
                                    ); 
                                </P>
                                <P>(xiii) Emergency Planning and Community Right to Know Act of 1986 (42 U.S.C. 11001 to 11050); </P>
                                <P>
                                    (3) 
                                    <E T="03">Cultural resources and aesthetics:</E>
                                </P>
                                <P>(i) 49 U.S.C. 303, protection of historic sites; </P>
                                <P>
                                    (ii) National Historic Preservation Act (16 U.S.C. 470 
                                    <E T="03">et seq.</E>
                                    ); 
                                </P>
                                <P>(iii) 23 U.S.C. 109(h), economic, social, and environmental effects of highways; </P>
                                <P>
                                    (iv) 49 U.S.C. 5324(b), economic, social, and environmental effects of transit; 
                                    <PRTPAGE P="33979"/>
                                </P>
                                <P>(v) Archeological and Historic Preservation Act (16 U.S.C. 469); </P>
                                <P>(vi) Archeological Resources Protection Act (16 U.S.C. 470aa to 47011); </P>
                                <P>(vii) Act for the Preservation of American Antiquities (16 U.S.C. 431 to 433); </P>
                                <P>
                                    (viii) American Indian Religious Freedom Act (42 U.S.C. 1996 
                                    <E T="03">et seq.</E>
                                    ); 
                                </P>
                                <P>(ix) Native American Grave Protection and Repatriation Act (25 U.S.C. 3001 to 3013); </P>
                                <P>(x) 23 U.S.C. 144(o), historic bridges; </P>
                                <P>(xi) 23 U.S.C. 530, wildflowers; </P>
                                <P>(xii) 23 U.S.C. 131, 136, 319, highway beautification; </P>
                                <P>
                                    (4) 
                                    <E T="03">Waters and water-related resources:</E>
                                </P>
                                <P>(i) 23 U.S.C. 109(h), economic, social, and environmental effects of highways; </P>
                                <P>(ii) 49 U.S.C. 5324(b), economic, social, and environmental effects of transit; </P>
                                <P>(iii) Federal Water Pollution Act, as amended (33 U.S.C. 1251 to 1376); </P>
                                <P>(iv) Wild and Scenic Rivers Act (16 U.S.C. 1271 to 1287); </P>
                                <P>(v) Land and Water Conservation Fund Act of 1965 (16 U.S.C. 460); </P>
                                <P>(vi) Water Bank Act (16 U.S.C. 1301 to 1311); </P>
                                <P>(vii) Executive Order 11990 (42 FR 26961; 3 CFR, 1977 comp., p. 121), protection of wetlands; </P>
                                <P>(viii) Emergency Wetlands Resources Act of 1986 (16 U.S.C. 3921 to 3931); </P>
                                <P>
                                    (ix) Rivers and Harbors Act of 1899 (33 U.S.C. 401 
                                    <E T="03">et seq.</E>
                                    ); 
                                </P>
                                <P>(x) Executive Orders 11988 (42 FR 26951; 3 CFR, 1977 comp., p. 1171) and 12148 (44 FR 43239; 3 CFR, 1979 comp., p. 412), floodplain management; </P>
                                <P>
                                    (5) 
                                    <E T="03">Wildlife, plants and natural areas:</E>
                                </P>
                                <P>(i) Endangered Species Act of 1973 (7 U.S.C. 136, 16 U.S.C. 1531 to 1543); </P>
                                <P>(ii) 49 U.S.C. 303, protection of wildlife and waterfowl refuges; </P>
                                <P>(iii) 23 U.S.C. 109(h), economic, social, and environmental effects of highways; </P>
                                <P>(iv) 9 U.S.C. 5324(b), economic, social, and environmental effects of transit;</P>
                                <P>(v) Marine Protection Research and Sanctuaries Act of 1972 (16 U.S.C. 1431 to 1445, 33 U.S.C. 1401 to 1445); </P>
                                <P>(vi) Fish and Wildlife Coordination Act (16 U.S.C. 661 to 666); </P>
                                <P>(vii) Wilderness Act (16 U.S.C. 1131 to 1136); </P>
                                <P>(viii) Wild and Scenic Rivers Act (16 U.S.C. 1271 to 1287); </P>
                                <P>(ix) Coastal Zone Management Act of 1972 (16 U.S.C. 1451 to 1464); </P>
                                <P>(x) Coastal Barrier Resources Act (16 U.S.C. 3501 to 3510, 42 U.S.C. 4028); </P>
                                <P>(xi) National Trails System Act (16 U.S.C. 1241 to 1249); </P>
                                <P>(xii) Executive Order 13112 (64 FR 6183), Invasive Species.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.111 </SECTNO>
                                <SUBJECT>Environmental justice.</SUBJECT>
                                <P>
                                    (a) In accordance with the goals established in Executive Order 12898, as implemented by DOT Order 5610.2 and the FHWA Order 6640.23,
                                    <SU>1</SU>
                                    <FTREF/>
                                     and the requirements of the Civil Rights Act of 1964, Title VI, and its implementing regulations, proposed actions shall be developed in a manner to avoid or mitigate disproportionately high and adverse human health or environmental effects, including interrelated social and economic effects, on low income populations and minority populations. Adverse effects can include a denial of or reduction in benefits.
                                </P>
                                <FTNT>
                                    <P>
                                        <SU>1</SU>
                                         These documents are available for inspection and copying as prescribed at 49 CFR part 7.
                                    </P>
                                </FTNT>
                                <P>(b) In performing an environmental analysis of proposed actions, applicants must analyze data necessary to determine whether the actions will have disproportionately high and adverse effects on low income and minority communities. When disproportionately high and adverse effects are found, the applicant must identify measures to address these disproportionate effects, including actions to avoid or mitigate them, or it must explain and justify why such measures cannot be taken.</P>
                                <P>(c) The findings and determinations made pursuant to paragraphs (a) and (b) of this section must be documented as part of the NEPA document prepared for the proposed action, or in a supplemental document if the NEPA process has been completed.</P>
                                <P>(d) In accordance with Executive Order 12898, DOT Order 5610.2, and the FHWA Order 6640.23, nothing in this section is intended to, nor shall create, any right to judicial review of any action taken by the agency, its officers or its recipients taken under this section to comply with such Orders.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.113 </SECTNO>
                                <SUBJECT>Avoidance, minimization, mitigation, and enhancement responsibilities. </SUBJECT>
                                <P>(a) In accordance with the goals established in § 1420.107, it is the policy of the FHWA and the FTA that proposed actions be developed as described in this section, to the fullest extent practicable. For the purposes of this section, “practicable” means a common sense balancing of environmental values with safety, transportation need, costs, and other relevant factors in decisionmaking. No additional findings or paperwork are required.</P>
                                <P>(1) Adverse social, economic, and environmental impacts to the affected human communities and the natural environment should be avoided.</P>
                                <P>(2) Where adverse impacts cannot be avoided, proposed measures should be developed to minimize adverse impacts.</P>
                                <P>(3) Measures necessary to mitigate unavoidable adverse impacts be incorporated into the action, or should be part of a mitigation program completed in advance of the action.</P>
                                <P>(4) Environmental enhancements should be evaluated and incorporated into the action as appropriate.</P>
                                <P>(b) Mitigation measures and environmental enhancements shall be eligible for Federal funding to the fullest extent authorized by law. </P>
                                <P>(c) NEPA commitments.</P>
                                <P>(1) It shall be the responsibility of the applicant in cooperation with the U.S. DOT agency to implement those mitigation measures and environmental enhancements, stated as commitments in the final EIS/ROD, EA/FONSI, or CE prepared or supplemented pursuant to this regulation, unless the commitment is modified or eliminated in a supplemental final EIS/ROD, EA/FONSI or CE, or re-evaluation approved by the U.S. DOT agency.</P>
                                <P>(2) If a final EIS/ROD, EA/FONSI, CE, or other U.S. DOT agency approval commits to coordination with another agency during the final design and construction phase, or during the operational phase of the action, the applicant is responsible for such coordination, unless the commitment is removed in a supplemental final EIS/ROD, EA/FONSI or CE, or re-evaluation approved by the U.S. DOT agency.</P>
                            </SECTION>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart B—Program and Project Streamlining </HD>
                            <SECTION>
                                <SECTNO>§ 1420.201 </SECTNO>
                                <SUBJECT>Relationship of planning and project development processes.</SUBJECT>
                                <P>(a) The planning products described in § 1410.318 shall be considered early in the NEPA process. The FTA and the FHWA encourage all Federal, State and local agencies with project level responsibilities for investments included in a transportation plan to participate in the planning process so as to maximize the usefulness of the planning products for the NEPA process and eliminate duplication.</P>
                                <P>
                                    (b) Applicants preparing documents under this part shall, to the maximum extent useful and practicable, incorporate and utilize analyses, studies, documents, and other sources of information developed during the transportation planning processes of 23 CFR part 1410 and other planning processes in satisfying the requirements of the NEPA process. The provisions of 40 CFR 1502.21 (incorporation by reference) will be used as appropriate. 
                                    <PRTPAGE P="33980"/>
                                </P>
                                <P>(c) During scoping for an EIS or early coordination for an environmental assessment, the U.S. DOT agency and the applicant shall, in consultation with the transportation planning agencies responsible for inclusion of the project in the metropolitan (if applicable) and statewide plan and program, review the record of previously completed planning activities, including any existing statement of purpose and need and evaluation of alternatives. Where the U.S. DOT agency, in cooperation with the applicant, determines that planning decisions are adequately supported, the detailed evaluation of alternatives required under § 1420.313(b) or § 1420.317(c) may be limited to the no action and reasonable alternatives requiring further consideration. In deciding which of the evaluations and conclusions of the planning process are adequately supported and may be incorporated during the NEPA process, the U.S. DOT agency and the applicant shall take into account the following:</P>
                                <P>(1) The validity and completeness of the supporting analyses,</P>
                                <P>(2) The public involvement process associated with those planning products,</P>
                                <P>(3) The degree of coordination with Federal, State, and local resource agencies with interest in or authority over the ultimate action(s); and </P>
                                <P>(4) The level of formal endorsement of the analyses and conclusions by participants in the planning process. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.203 </SECTNO>
                                <SUBJECT>Environmental streamlining. </SUBJECT>
                                <P>(a) For highway and mass transit projects requiring an environmental impact statement, an environmental assessment, or an environmental review, analysis, opinion, or environmental permit, license, or approval by operation of Federal law, as lead Federal agency, the U.S. DOT agency, in cooperation with the applicant, shall perform the following: </P>
                                <P>(1) Consult with the applicant regarding the issues involved, the likely Federal involvement, and project timing. </P>
                                <P>(2) Early in the NEPA process, contact Federal agencies likely to be involved in the proposed action to verify the nature of their involvement and to discuss issues, methodologies, information requirements, time frames and constraints associated with their involvement. </P>
                                <P>(3) Identify and use the appropriate means listed in 40 CFR 1500.4 and 1500.5 for reducing paperwork and reducing delay. </P>
                                <P>(4) Document the results of such consultation and distribute to the appropriate Federal agencies for their concurrence, identifying at a minimum the following: </P>
                                <P>(i) Federal reviews and approvals needed for the action,</P>
                                <P>(ii) Those issues to be addressed in the NEPA process and those that need no further evaluation, </P>
                                <P>(iii) Methodologies to be employed in the conduct of the NEPA process,</P>
                                <P>(iv) Proposed agency and public involvement processes, and</P>
                                <P>(v) A process schedule. </P>
                                <P>(5) Identify, during the course of completing the NEPA process, points of interagency disagreement causing delay and immediately take informal measures to resolve or reduce delay. If these measures are not successful in a reasonable time, the U.S. DOT agency shall initiate a dispute resolution process pursuant to section 1309 of the TEA-21. </P>
                                <P>(b) A State may request that all State agencies with environmental review or approval responsibilities be included in the coordinated environmental review process and, with the consent of the U.S. DOT agency, establish an appropriate means to assure that Federal and State environmental reviews and approvals are fully coordinated. </P>
                                <P>(c) At the request of the applicant, the coordinated environmental review process need not be applied to an action not requiring an environmental impact statement. </P>
                                <P>(d) In accordance with the CEQ regulations on reducing paperwork (40 CFR 1500.4), NEPA documents prepared by DOT agencies need not devote paper to impact areas and issues that are not implicated in the proposed action and need not make explicit findings on such issues. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.205 </SECTNO>
                                <SUBJECT>Programmatic approvals. </SUBJECT>
                                <P>(a) Nothing in this part shall prohibit the U.S. DOT agency from making approvals which apply to future actions consistent with the conditions established for such programmatic approvals. </P>
                                <P>(b) Applicants shall cooperate with the U.S. DOT agency in conducting program evaluations to ensure that such programmatic approvals are being properly applied. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.207 </SECTNO>
                                <SUBJECT>Quality assurance process. </SUBJECT>
                                <P>(a) The FHWA and the FTA shall institute a process to assure that actions subject to this part meet or exceed legal requirements and are processed in a timely manner. </P>
                                <P>(b) For actions processed with an environmental impact statement, this process shall include a legal sufficiency review and may require the prior concurrence of the Headquarters office in accordance with procedures established by the FTA and the FHWA. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.209 </SECTNO>
                                <SUBJECT>Alternate procedures. </SUBJECT>
                                <P>(a) An applicant may propose to the U.S. DOT agency alternative procedures for complying with the intent of this part with respect to its actions. </P>
                                <P>
                                    (b) The U.S. DOT agency shall publish such alternative procedures in the 
                                    <E T="04">Federal Register</E>
                                     for notice and comment and shall consult with the CEQ pursuant to 40 CFR 1507.3. 
                                </P>
                                <P>(c) After taking into account comments received, and negotiating with the applicant appropriate changes to such alternative procedures, the U.S. DOT agency shall approve such alternative procedures only after making a finding that the alternative procedures will be fully effective at complying with NEPA and related responsibilities. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.211 </SECTNO>
                                <SUBJECT>Use of this part by other U.S. DOT agencies. </SUBJECT>
                                <P>As authorized by the Secretary, other U.S. DOT agencies may use this part for specific actions or categories of actions under their jurisdiction. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.213 </SECTNO>
                                <SUBJECT>Emergency action procedures. </SUBJECT>
                                <P>Requests for deviations from the procedures in this part because of emergency circumstances shall be referred to the U.S. DOT agency for evaluation and decision in consultation with the CEQ in accordance with 40 CFR 1506.11. </P>
                            </SECTION>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart C—Process and Documentation Requirements </HD>
                            <SECTION>
                                <SECTNO>§ 1420.301 </SECTNO>
                                <SUBJECT>Responsibilities of the participating parties. </SUBJECT>
                                <P>(a) The CEQ regulation establishes rules for lead agencies (40 CFR 1501.5) and cooperating agencies (40 CFR 1501.6). It also encourages Federal agencies to cooperate with State and local agencies to eliminate duplication (40 CFR 1506.2) and defines the relationship between Federal agencies, applicants, and contractors (40 CFR 1506.5). </P>
                                <P>(b) For actions on Federal lands that are developed directly by the U.S. DOT agency in cooperation with the Federal land management agency, responsibilities for management of the NEPA process shall be as established by interagency agreement or procedure. </P>
                                <P>(c) Use of contractors. </P>
                                <P>
                                    (1) The U.S. DOT agency or an applicant may select and use contractors, in accordance with applicable contracting procedures, and the provisions of 40 CFR 1506.5(c), in support of their respective roles in the NEPA process. An applicant which is a 
                                    <PRTPAGE P="33981"/>
                                    State agency with statewide jurisdiction may select a contractor to assist in the preparation of an EIS. Where the applicant is not a State agency with statewide jurisdiction, the applicant may select a contractor, after coordination with the U.S. DOT agency to assure compliance with 40 CFR 1506.5(c) relative to conflict of interest. Contractors that have a role in the actual writing of a NEPA document shall execute a disclosure statement in accordance with 40 CFR 1506.5(c), specifying that such contractor has no financial or other interest in the outcome of the action (other than engineering with the exception allowed by paragraph (c)(2) of this section, if applicable), and will not acquire such an interest prior to the approval of the final NEPA document by the U.S. DOT agency or the termination of the contractor's involvement in writing the NEPA document, whichever occurs first. 
                                </P>
                                <P>(2) A State may procure the services of a consultant, under a single contract, for environmental impact assessment and subsequent engineering and design work, provided that the State conducts a review that assesses the objectivity of the NEPA work in accordance with the provisions of 23 U.S.C. 112(g). </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.303 </SECTNO>
                                <SUBJECT>Interagency coordination. </SUBJECT>
                                <P>(a) Interagency coordination during the NEPA process involves the early and continuing exchange of information with interested Federal, State, local public agencies, and tribal governments. Interagency coordination should begin early as part of the planning process and continue through project development, the preparation of an appropriate NEPA document, and, by agreement, into the implementation stage of the action. Interested agencies include those that express a continuing interest in any aspect of the actions during the planning process and project development processes. They include those agencies whose jurisdiction, responsibilities, or expertise may involve any aspect of the action or its alternatives. The purpose of interagency coordination is to aid in determining the class of action, the scope of the NEPA document, the identification of key issues, the appropriate level of analysis, methods of avoidance, minimization, and mitigation of adverse impact, opportunities for environmental enhancement, and related environmental requirements. Coordination early in the NEPA process must extend beyond agencies consulted during the planning process to those agencies whose interest begins only when preliminary designs of alternative actions are being developed. The appropriate frequency and timing of coordination with a particular agency will depend on the interests of the agency consulted. </P>
                                <P>(b) Federal land management entities, neighboring States, and tribal governments, that may be significantly affected by the action or by any of the alternatives shall be notified early in the NEPA process and their views solicited by the applicant in cooperation with the U.S. DOT agency. </P>
                                <P>(c) Upon U.S. DOT agency written approval of an EA, FONSI, separate section 4(f) determination, or CE designation, the applicant shall send a notice of availability of the approved document, or a copy of the approved document itself, to the affected units of Federal, State, and local government. The notice shall briefly describe the action and its location and impacts. Cooperating agencies shall be provided a copy of the approved document. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.305 </SECTNO>
                                <SUBJECT>Public involvement. </SUBJECT>
                                <P>(a) The applicant must have a continuing program of public involvement which actively encourages and facilitates the participation of transportation and environmental interest groups, citizens groups, private businesses, and the general public including minority and low income populations through a wide range of techniques for communicating and exchanging information. The applicant shall use the products of the public involvement process developed during planning pursuant to 23 CFR 1410.212 and 1410.316, whenever such information is reasonably available and relevant, to provide continuity between the public involvement programs. </P>
                                <P>(b) Each applicant developing projects under this part must adopt written procedures to carry out the public involvement requirements of this section and 40 CFR 1506.6, and, as appropriate, 23 U.S.C. 128, and 49 U.S.C. 5323(b) and 5324(b). The applicant's public involvement procedures shall apply to all classes of action as described in § 1420.309 and shall be developed in cooperation with other transportation agencies with jurisdiction in the same area, so that, to the maximum extent practicable, the public is presented with a consistent set of procedures that do not vary with the transportation mode of the proposed action or with the phase of project development. Where two or more involved parties have separate established procedures, a cooperative process for determining the appropriate public involvement activities and their consistency with the separate agency's procedures will be cooperatively established. </P>
                                <P>(c) Public involvement procedures must provide for the following: </P>
                                <P>(1) Coordination of public involvement activities with the entire NEPA process and, when appropriate, with the planning process. The procedures also must provide for coordination and information required to comply with public involvement requirements of other related laws, executive orders, and regulations; </P>
                                <P>(2) Early and continuing opportunities for the public to be informed about, and involved in the identification of social, economic, and environmental impacts and impacts associated with relocation of individuals, groups, or institutions; </P>
                                <P>(3) The use of an appropriate variety of public involvement activities, techniques, meeting and hearing formats, and notification media; </P>
                                <P>(4) A scoping process that satisfies the requirements of 40 CFR 1501.7; </P>
                                <P>(5) One or more public hearings or the opportunity for hearing(s) to be held at a convenient time and place that encourage public participation, for any project which requires the relocation of substantial numbers of people, substantially changes the layout or functions of connecting transportation facilities or of the facility being improved, has a substantial adverse impact on abutting property, substantially affects a community or its mass transportation service, otherwise has a substantial social, economic, environmental or other effect, or for which the U.S. DOT agency determines that a public hearing is in the public interest; </P>
                                <P>(6) Reasonable notice to the public of either a public hearing or the opportunity for a public hearing where a hearing is determined appropriate. Such notice shall indicate the availability of explanatory information; </P>
                                <P>(7) Where appropriate, the submission to the U.S. DOT agency of a transcript of each public hearing and a certification (pursuant to 23 U.S.C. 128 or 49 U.S.C. 5324(b)(2)) that a required hearing or hearing opportunity was offered. The transcript should be accompanied by copies of all written statements from the public, submitted either at the public hearing or during an announced period after the public hearing; </P>
                                <P>
                                    (8) Specific procedures for complying with the public and agency involvement and notification requirements for the following: EAs, Findings of no significant impact (FONSI), Draft EISs, Final EISs, and Records of decision (ROD); 
                                    <PRTPAGE P="33982"/>
                                </P>
                                <P>(9) Reasonable accommodations for participation by persons with disabilities, including, upon request, the provision of auxiliary aids and services for understanding speakers at meetings and environmental documents. </P>
                                <P>(d) Where a re-evaluation of NEPA documents is required pursuant to § 1420.323, the U.S. DOT agency and the applicant will determine whether changes in the project or new information warrant additional public involvement. </P>
                                <P>(e) A minimum public comment period of 45 days shall be provided prior to the initial adoption or substantial revision of public involvement procedures. </P>
                                <P>(f) Public involvement procedures in effect as of the date of this part remain valid, but will be reviewed periodically for effectiveness. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.307 </SECTNO>
                                <SUBJECT>Project development and timing of activities. </SUBJECT>
                                <P>(a) The FHWA and/or the FTA will not approve the initiation and will not authorize funding for final design activities, property acquisition (except the types of advance land acquisitions described in § 1420.311(d)(16)), purchase of construction materials or transit vehicles, or construction, until the following have been completed: </P>
                                <P>(1)(i) The action has been classified as a categorical exclusion (CE), or </P>
                                <P>(ii) A FONSI has been approved, or </P>
                                <P>(iii) A final EIS has been approved, made available for the prescribed period of time, and a record of decision has been signed; </P>
                                <P>(2) The U.S. DOT agency has received transcripts of public hearings held, and any required certifications that a hearing or opportunity for a hearing was provided; and </P>
                                <P>(3) The planning and programming requirements of 23 CFR part 1410 have been met. </P>
                                <P>(b) Before completion of the NEPA document, if it becomes apparent that the preferred alternative will not be consistent with the design concept and scope of the action identified in the relevant plan and TIP, the applicant shall immediately notify the State agency responsible for the State TIP, and, in metropolitan areas, the MPO, so that the planning and programming requirements of 23 CFR part 1410 can be satisfied prior to the approval of a final EIS, Record of Decision, FONSI or CE. </P>
                                <P>(c) Compliance with the requirements of all applicable environmental laws, regulations, executive orders, and other related requirements as set forth in § 1420.109 should be completed prior to the approval of the final EIS, FONSI, or the CE designation. If full compliance is not possible by the time the final EIS or FONSI is prepared, the final EIS or FONSI should reflect consultation with the appropriate agencies and provide reasonable assurance that the requirements will be met. However, full compliance with the U.S. EPA's conformity regulation at 40 CFR parts 51 and 93 is required prior to the approval of the ROD, FONSI or CE designation. Approval of the NEPA document constitutes adoption of DOT agency findings and determinations that are contained therein unless otherwise specified. The FHWA approval of the appropriate NEPA document will constitute its finding of compliance with the report requirements of 23 U.S.C. 128. The FTA approval of the appropriate NEPA document indicates compliance with 49 U.S.C. 5324(b) and fulfillment of the grant application requirements of 49 U.S.C. 5323(b), if such requirements are applicable to the action. </P>
                                <P>(d) The completion of the requirements set forth in this section is considered the U.S. DOT agency's acceptance of the location of the action and design concepts described in the NEPA document unless otherwise specified by the approving official. However, such acceptance does not commit the U.S. DOT agency to approve any future grant request to fund the preferred alternative. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.309 </SECTNO>
                                <SUBJECT>Classes of actions. </SUBJECT>
                                <P>(a) Class I (EISs). Actions that significantly affect the environment require an EIS (40 CFR 1508.27). The following are examples of actions normally requiring an EIS: </P>
                                <P>(1) A new controlled access freeway. </P>
                                <P>(2) A highway project of four or more lanes on a new location. </P>
                                <P>(3) New construction or major extension of fixed rail transit facilities (e.g., rapid rail, light rail, automated guideway transit). </P>
                                <P>(4) New construction or major extension of a separate roadway for buses or high occupancy vehicles not located within an existing highway facility. </P>
                                <P>(5) New construction or major extension of an intercity railroad not located within existing railroad right-of-way. </P>
                                <P>(6) A multimodal or intermodal facility that includes or requires any of the other Class I actions. </P>
                                <P>(b) Class II (Categorical Exclusions). Actions that do not individually or cumulatively have a significant environmental impact are excluded from the requirement to prepare an EA or EIS. A specific list of CEs normally not requiring NEPA documentation is set forth in § 1420.311(c). Additional actions not listed may be designated as CEs pursuant to § 1420.311(d), if documented environmental studies demonstrate that the action would not, either individually or cumulatively, have a significant environmental impact. </P>
                                <P>(c) Class III (EAs). Actions in which the significance of the environmental impact is not clearly established. All actions that are not Class I or II are Class III. All actions in this class require the preparation of an EA to determine the appropriate, subsequent NEPA document (i.e., Findings of no significant impact or EIS). </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.311 </SECTNO>
                                <SUBJECT>Categorical exclusions. </SUBJECT>
                                <P>(a) Categorical exclusions (CEs) are actions which meet the definition contained in 40 CFR 1508.4, and are known, on the basis of past experience with similar actions, not to involve significant environmental impacts. They are actions which: Do not induce significant impacts to planned growth or land use for the area; do not require the relocation of significant numbers of people; do not have a significant impact on any natural, cultural, recreational, historic or other resource; do not involve significant air, noise, or water quality impacts; do not have significant impacts on travel patterns; or do not otherwise, either individually or cumulatively, have any significant environmental impacts. </P>
                                <P>(b) Any action which normally would be classified as a CE but could involve unusual circumstances will require the U.S. DOT agency, in cooperation with the applicant, to conduct appropriate environmental studies to determine if the CE classification is proper. Such unusual circumstances include: </P>
                                <P>(1) Unique environmental impacts; </P>
                                <P>(2) Substantial controversy on environmental grounds; </P>
                                <P>(3) Significant impact on properties protected by 49 U.S.C. 303 (section 4(f)) or section 106 of the National Historic Preservation Act; or </P>
                                <P>(4) Inconsistencies with any Federal, State, or local law, requirement or administrative determination relating to the environmental aspects of the action. </P>
                                <P>
                                    (c) The following actions meet the criteria for CEs in the CEQ regulation (40 CFR 1508.4) and § 1420.311(a) of this regulation. If other environmental laws (i.e., those listed in § 1420.109(c)) do not apply to the action, then it does not require any further NEPA approval by the U.S. DOT agency. If the U.S. DOT agency is not sure of the applicability of one of these CEs or of other environmental laws to a particular proposed action, the applicant will be 
                                    <PRTPAGE P="33983"/>
                                    required to provide supporting documentation in accordance with paragraph (d) of this section. The following are CEs: 
                                </P>
                                <P>(1) Activities which do not involve or lead directly to construction, such as program administration (e.g., personnel actions, procurement of consulting services or office supplies); the promulgation of rules, regulations, directives, and legislative proposals; planning and technical studies; technical assistance activities; training and research programs; technology transfer activities; research activities as defined in 23 U.S.C. 501-507; archaeological planning and research; approval of a unified planning work program; development and establishment of management systems under 23 U.S.C. 303; approval of project concepts under 23 CFR part 476; preliminary engineering to define the elements of a proposed action or alternatives so that social, economic, and environmental effects can be assessed; Federal-aid system revisions which establish classes of highways; and designation of highways to the National Highway System. </P>
                                <P>(2) Modernization of a highway by resurfacing. </P>
                                <P>(3) Routine maintenance or minor rehabilitation of existing transportation facilities, including pavements, tracks, railbeds, bridges, structures, stations, terminals, maintenance shops, storage yards, and buildings, that occurs entirely on or within the facility, where there is no change in the character and use of the facility, and no substantial disruption of service or traffic; purchase of associated capital maintenance items; preventive maintenance of transit facilities, vehicles, and other equipment. </P>
                                <P>(4) Incorporation of an Intelligent Transportation Systems (ITS) element into an existing transportation facility or service, including the development, purchase, installation, maintenance, improvement, and operation of a traveler information system, incident management and emergency response system, traffic management and control system, security system, or MAYDAY system that enables public agencies to detect and respond to emergency situations. </P>
                                <P>(5) Activities included in the State's highway safety program under 23 U.S.C. 402; enforcement of railroad safety regulations, including the issuance of emergency orders. </P>
                                <P>(6) Improvement of existing rest areas, toll collection facilities, truck weigh stations, traffic management and control centers, and vehicle emissions testing centers where no substantial land acquisition or traffic disruption will occur. </P>
                                <P>(7) Carpool and vanpool projects, as defined in 23 U.S.C. 146, if no substantial land acquisition or traffic disruption will occur. </P>
                                <P>(8) Emergency repairs of highways, roads and trails under 23 U.S.C. 125; emergency repair of transit or railroad facilities after a natural disaster or catastrophic failure. </P>
                                <P>(9) Operating assistance to transit agencies. </P>
                                <P>(10) Acquisition of buses, rail vehicles, paratransit vehicles, and transit-support vehicles, where the use of these vehicles can be accommodated by existing facilities or by new facilities which are themselves CEs. </P>
                                <P>(11) Purchase or installation of operating or maintenance equipment to be located within an existing transportation facility with no significant impacts off the site; lease of existing facilities, vehicles, or other equipment for use in providing transit services; capital cost of contracting for transit services. </P>
                                <P>(12) Bus and rail car rehabilitation, including the retrofit or replacement of vehicles for alternative fuels, where the use of these vehicles can be accommodated by existing facilities or new facilities which are themselves CEs. </P>
                                <P>(13) Improvement of existing tracks, railbeds, communications systems, signal systems, security systems, and electrical power systems when carried out within the existing right-of-way without substantial service disruption. </P>
                                <P>(14) Construction of bicycle and pedestrian lanes, paths, and facilities within existing transportation facilities or right-of-ways; installation of equipment for transporting bicycles on transit vehicles. </P>
                                <P>(15) Alterations to transportation facilities or vehicles in order to make them accessible by persons with disabilities. </P>
                                <P>(16) Installation of fencing, signs, pavement markings, small passenger shelters, traffic signals, lighting, and railroad warning devices where no substantial land acquisition or traffic disruption will occur. </P>
                                <P>(17) Transfer of Federal lands pursuant to 23 U.S.C. 317 when the subsequent action is not an FHWA action; approvals of disposals of excess right-of-way; transfer of surplus assets, in accordance with 49 U.S.C. 5334(g); approval of utility installations along or across a transportation facility. </P>
                                <P>(18) Landscaping, streetscaping, public art and other scenic beautification; control and removal of outdoor advertising; acquisition of scenic easements and scenic or historic sites for the purpose of preserving the site. </P>
                                <P>(19) Installation of noise barriers or other alterations to existing facilities to provide for noise reduction; alterations to existing non-historic buildings to provide for noise reduction. </P>
                                <P>(20) Contributions to statewide or regional efforts to conserve, restore, enhance, and create wetlands or wildlife habitats. </P>
                                <P>
                                    (d) Additionally, for individual proposed actions to be categorically excluded under this section, the applicant shall submit documentation which demonstrates that the specific conditions or criteria for these CEs are satisfied, that significant environmental effects will not result, that the applicant's public involvement process is consistent with the procedures adopted pursuant to § 1420.305, that any appropriate interagency coordination has occurred, and that any other applicable environmental laws (
                                    <E T="03">e.g.,</E>
                                     those listed in § 1420.109(c)) have been satisfied. This demonstration may require investigations of specific areas of impact to determine whether the CE criteria are satisfied. If the DOT agency is not certain that the appropriateness of the CE has been demonstrated, additional documentation or an EA or EIS will be required of the applicant. Examples of actions for which a CE demonstration may be possible include, but are not limited to: 
                                </P>
                                <P>
                                    (1) Modernization of a highway through restoration, rehabilitation, reconstruction, adding shoulders, or adding auxiliary lanes (
                                    <E T="03">e.g.,</E>
                                     parking, weaving, turning, climbing lanes), or travel lanes in the median of an existing facility, including any such action necessary to accommodate other transportation modes on an existing facility. 
                                </P>
                                <P>(2) Transportation operational improvements, including those that use ITS, such as, freeway surveillance and control systems, traffic signal monitoring and control systems, transit management systems, electronic fare payment systems, and electronic toll collection systems. </P>
                                <P>(3) Transportation safety improvements and programs; hazard eliminations, including construction of grade separation to replace existing highway-railway grade crossings; projects to mitigate hazards caused by wildlife; and seismic retrofit of existing transportation facilities or structures. </P>
                                <P>(4) Rehabilitation or reconstruction of tunnels, bridges, and other structures, and the approaches thereto. </P>
                                <P>
                                    (5) Modification or replacement of an existing bridge on essentially the same alignment or location. 
                                    <PRTPAGE P="33984"/>
                                </P>
                                <P>(6) Construction of parking facilities or carpool and vanpool projects that involve land acquisition and construction. </P>
                                <P>(7) Construction of new buildings to house transportation management and control centers, carpool and vanpool operations centers, or vehicle emissions testing centers. </P>
                                <P>(8) Construction of new rest areas, toll collection facilities, truck weigh stations or auto emissions testing or safety testing facilities. </P>
                                <P>(9) Approvals for changes in highway access control. </P>
                                <P>(10) Improvement of existing tracks, railbeds, communications systems, signal systems, security systems, and electrical power systems, including construction of sidings or passing tracks; extension or expansion of rail electrification on existing, operating rail lines. </P>
                                <P>(11) Construction of new bus or rail storage and maintenance facilities in undeveloped areas or areas used predominantly for industrial or transportation purposes, where such facility is compatible with existing zoning, the site is located on or near a street with adequate capacity to handle anticipated traffic, and there is no significant air or noise impact on the surrounding community. </P>
                                <P>(12) Renovation, reconstruction, or improvement of existing rail, bus, and intermodal buildings and facilities, including conversion to use by alternative-fuel vehicles. </P>
                                <P>(13) Construction of bus transfer facilities (an open area consisting of passenger shelters, boarding areas, kiosks and related street improvements) or intermodal transfer facilities, when located in a commercial area or other high activity center in which there is adequate street capacity for projected traffic.</P>
                                <P>(14) Rehabilitation, renovation, or improvement of existing ferry terminals, piers, and facilities. </P>
                                <P>(15) Short-term demonstrations of rail service on existing tracks. </P>
                                <P>(16) An acquisition of land or property interests that meets the criteria of paragraph (d)(16)(i), (ii) or (iii) of this section may be evaluated against the criteria for a CE in the CEQ regulations (40 CFR 1508.4) and paragraph (a) of this section separately from any planned action that would use the land or property interests. Any subsequent action that would use the acquired right-of-way or property interests and would require a DOT agency action must be separately reviewed in accordance with this part prior to any construction on, or change in the land. The following types of acquisitions may qualify as CEs: </P>
                                <P>(i) Acquisition of an existing transportation right-of-way which is linear in its general configuration and is not publicly owned, such as a railroad or a private road, for the purpose of either maintaining preexisting levels of transportation service on the facility or of preserving the right-of-way for a future transportation action or transportation enhancement activity. </P>
                                <P>(ii) Acquisition of land, easements, or other property interests with the intent of preserving alternatives for a future transportation action, where the following conditions are met: The transportation action that would use the land or property interests has been specifically included in a transportation plan for the area adopted pursuant to 23 CFR part 1410 and such plan has been found by the U.S. DOT agency to conform to air quality plans in accordance with 40 CFR parts 51 and 93, if applicable; and the acquisition will not limit the evaluation of alternatives to the planned action that would use the land or property interests including shifts in alignment that may be required. </P>
                                <P>(iii) Acquisition of land or property interests for hardship or protective purposes where the following conditions are met: The transportation action that would use the land or property interests has been specifically included in a transportation plan for the area adopted pursuant to 23 CFR part 1410 and such plan has been found by the U.S. DOT agency to conform to air quality plans in accordance with 40 CFR parts 51 and 93, if applicable; the hardship and protective buying will be limited to a particular parcel or a small number of parcels related to the planned transportation action; and the acquisition will not limit the evaluation of alternatives to the planned action that would use the land or property interests, including shifts in alignment that may be required. </P>
                                <P>(17) Approvals for joint or limited use of right-of-way, where the proposed use does not have significant adverse impacts. </P>
                                <P>(18) Construction of a bicycle transportation facility on its own, new right-of-way. </P>
                                <P>(19) Mitigation of water pollution due to storm water runoff from transportation facilities. </P>
                                <P>(20) Rehabilitation and operation of historic transportation buildings, structures, or facilities (including historic railroad or bus facilities and canals). </P>
                                <P>(21) Transportation enhancement activities and transit enhancements defined in 23 U.S.C. 101 and 49 U.S.C. 5302. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.313 </SECTNO>
                                <SUBJECT>Environmental assessments. </SUBJECT>
                                <P>(a) An EA shall be prepared by the applicant in consultation with the U.S. DOT agency for each action(s) that is not a CE and does not clearly require the preparation of an EIS, or where the U.S. DOT agency believes an EA would assist in determining the need for an EIS. </P>
                                <P>(b) The EA shall evaluate the social, economic, and environmental impacts of the proposed action, reasonable alternatives that would avoid or reduce adverse impacts, measures which would mitigate adverse impacts, and environmental enhancements if any that would aid in harmonizing the action with the surrounding community. The EA shall discuss compliance with other related environmental laws, regulations, and executive orders. </P>
                                <P>(c) The EA is subject to U.S. DOT agency approval before it is made available to the public as a U.S. DOT agency document. </P>
                                <P>(d) For actions that require an EA, the applicant, in consultation with the U.S. DOT agency, shall do the following: </P>
                                <P>(1) Conduct interagency coordination in accordance with § 1420.303, beginning at the earliest appropriate time, to advise agencies of the proposed action and to achieve the following objectives: Determine which aspects of the proposed action have potential for social, economic, or environmental impact; identify alternatives and measures which might avoid or mitigate adverse impacts; identify environmental enhancements that might aid in harmonizing the action with the surrounding community; and identify other environmental review and coordination requirements which should be performed concurrently with the EA. The results of interagency coordination to the time of EA approval by the U.S. DOT agency shall be included in the EA. </P>
                                <P>(2) Provide for public involvement in accordance with the procedures established pursuant to § 1420.305. Public involvement to the time of EA approval by the U.S. DOT agency shall be summarized in the EA. </P>
                                <P>
                                    (e) The EA need not be circulated for comment but the document must be made available for inspection in public places readily accessible to the affected community in accordance with paragraphs (f) and (g) of this section. Notice of availability of the EA, briefly describing the action(s) and its impacts, or a copy of the EA, shall be sent by the applicant to the affected units of Federal, State and local government. 
                                    <PRTPAGE P="33985"/>
                                </P>
                                <P>(f) When, in accordance with the public involvement procedures established pursuant to § 1420.305, a public hearing on an action evaluated in an EA is held, the following shall occur: </P>
                                <P>(1) The EA shall be available at the public hearing and for a minimum of 15 days in advance of the public hearing. </P>
                                <P>(2) The notice of the public hearing in local newspapers shall announce the availability of the EA and where it may be obtained or reviewed. </P>
                                <P>(3) Pursuant to 40 CFR 1501.4(c) comments shall be submitted in writing to the applicant or the U.S. DOT agency within 30 days of publication of the notice of availability of the EA unless the U.S. DOT agency determines, for good cause, that a different period is warranted. </P>
                                <P>(g) When, in accordance with the public involvement procedures established pursuant to § 1420.305, a public hearing on an action evaluated in an EA is not held, the following shall occur: </P>
                                <P>(1) The applicant shall place a notice in a newspaper(s) similar to a public hearing notice at an appropriate stage of development of the action. </P>
                                <P>(2) The notice shall advise the public of the availability of the EA, state where information concerning the action may be obtained, and invite comments from all parties with an interest in the social, economic, or environmental aspects of the action. </P>
                                <P>(3) Pursuant to 40 CFR 1501.4(c) comments shall be submitted in writing to the applicant or the U.S. DOT agency within 30 days of the publication of the notice unless the U.S. DOT agency determines, for good cause, that a different period is warranted. </P>
                                <P>(h) If no significant impacts are identified, the applicant shall consider the public and agency comments received; revise the EA as appropriate; furnish the U.S. DOT agency a copy of the revised EA, the public hearing transcript, where applicable, and copies of any comments received and responses thereto; and recommend a FONSI. The revised EA shall also document compliance, to the fullest extent possible, with other related environmental laws, regulations, and executive orders applicable to the action, or provide reasonable assurance that the requirements will be met. Full compliance with the transportation conformity rule (40 CFR parts 51 and 93) and the planning regulation (23 CFR part 1410) is required before completion of the FONSI. </P>
                                <P>(i) If, at any point in the EA process, the U.S. DOT agency determines that the action is likely to have a significant impact on the environment, the preparation of an EIS will be required. </P>
                                <P>(j) Any action which normally would be classified as an EA but could involve unusual circumstances, such as, substantial controversy on community impact and/or environmental grounds, will require the U.S. DOT agency, in cooperation with the applicant, to determine if the EA is the appropriate level of documentation. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.315 </SECTNO>
                                <SUBJECT>Findings of no significant impact. </SUBJECT>
                                <P>(a) The U.S. DOT agency will review the EA and other documents submitted pursuant to § 1420.313 (e.g., copies of any hearing transcript and written comments, and the applicant's responses). If the U.S. DOT agency agrees with the applicant's recommendation of a FONSI, it will make such finding in writing and incorporate by reference the EA and any other related documentation. </P>
                                <P>(b) Pursuant to 40 CFR 1501.4(e)(2), for proposed actions which are either similar to ones normally requiring an EIS or are without precedent and the U.S. DOT agency is processing the action with an EA and expects to issue a FONSI, copies of the EA and proposed FONSI shall be made available for review by the public and affected units of government for a minimum of 30 days before the U.S. DOT agency makes its final decision. This public availability shall be announced by a notice similar to a public hearing notice. </P>
                                <P>(c) After a FONSI has been made by the U.S. DOT agency, a notice of availability of the FONSI shall be sent by the applicant to the affected units of Federal, State and local government, and the document shall be available from the applicant and the U.S. DOT agency upon request by the public. Notice shall also be sent to the State intergovernmental review contacts established under Executive Order 12372. </P>
                                <P>(d) Where substantial changes are made to the project and/or its potential impacts after the public review period for the EA, the applicant, pursuant to § 1420.323(c), shall make copies of the revised EA and the FONSI available for review by the public and affected units of government for a minimum of 30 days before the U.S. DOT agency makes its final decision, unless the U.S. DOT agency determines, for good cause, that a different period is warranted. </P>
                                <P>(e) If another Federal agency has issued a FONSI on an action which includes an element proposed for U.S. DOT agency action, the U.S. DOT agency will evaluate the other agency's EA/FONSI. If the U.S. DOT agency determines that this element of the action and its environmental impacts have been adequately identified and assessed, the U.S. DOT agency will issue its own FONSI in accordance with paragraphs (a), (b), (c) and (d) of this section, incorporating the other agency's FONSI and any other related documentation. If environmental issues have not been adequately identified and assessed, the U.S. DOT agency will require appropriate environmental studies to complete the assessment. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.317 </SECTNO>
                                <SUBJECT>Draft environmental impact statements. </SUBJECT>
                                <P>
                                    (a) A draft EIS shall be prepared when the U.S. DOT agency determines that the action(s) is likely to cause significant impacts on the environment or if the preparation of an EIS is otherwise appropriate. When the decision has been made by the U.S. DOT agency to prepare an EIS, the U.S. DOT agency will publish a Notice of Intent (40 CFR 1508.22) in the 
                                    <E T="04">Federal Register</E>
                                    . Applicants must announce the intent to prepare an EIS by appropriate means at the local level in accordance with the public involvement procedures established pursuant to § 1420.305. 
                                </P>
                                <P>
                                    (b) The U.S. DOT agency, in cooperation with the applicant, will publish the Notice of Intent and begin a scoping process to establish the scope of the draft EIS and the work necessary for its preparation. The documented results of the planning process relevant to the action, including the public involvement and interagency coordination that has occurred, must be considered in scoping. Scoping is normally achieved through the actions taken to comply with the public involvement procedures and interagency coordination required by §§ 1420.303 and 1420.305. The scoping process will: Review the range of alternatives and impacts and the major issues to be addressed in the EIS; aid in determining which aspects of the proposed action have potential for social, economic, or environmental impact; help identify measures which might mitigate adverse environmental impacts; identify environmental enhancements that might aid in harmonizing the action with the surrounding community; identify other environmental review and coordination requirements that must be performed concurrently with the EIS preparation; and achieve the other objectives of 40 CFR 1501.7 and environmental streamlining (§ 1420.203). If a public scoping meeting is to be held, it must be announced in the U.S. DOT agency 's Notice of Intent and by an appropriate means at the local level. 
                                    <PRTPAGE P="33986"/>
                                </P>
                                <P>(c) The draft EIS shall be prepared by the U.S. DOT agency in cooperation with the applicant or, where permitted by 40 CFR 1506.5, by the applicant with appropriate guidance and participation by the U.S. DOT agency. The draft EIS shall evaluate all reasonable alternatives and may rely on information developed in accordance with 23 CFR part 1410. The draft EIS shall discuss the reasons why other alternatives, which may have been considered, were eliminated from detailed study. The draft EIS shall evaluate the social, economic, and environmental impacts of the proposed action, reasonable alternatives that would avoid or reduce adverse impacts, measures which would mitigate adverse impacts, and environmental enhancements that would aid in harmonizing the action with the surrounding community. Alternatives must be sufficiently well-defined to allow full evaluation of the specific alignment and design variations that would avoid or minimize adverse impacts. The draft EIS shall summarize the public involvement and interagency coordination to the time of its approval. The draft EIS shall also summarize the studies, reviews, consultations, and coordination required by other related environmental laws, regulations, and executive orders to the extent appropriate at this stage in the environmental process. </P>
                                <P>(d) The U.S. DOT agency, when satisfied that the draft EIS complies with NEPA requirements, will approve the draft EIS for circulation by signing and dating the cover sheet. </P>
                                <P>(e) A lead, joint lead, or a cooperating agency shall be responsible for printing and distributing the draft EIS. The initial printing of the draft EIS shall be in sufficient quantity to meet requests for copies which can reasonably be expected from agencies, organizations, and individuals. Normally, copies will be furnished free of charge. However, with U.S. DOT agency concurrence, the party requesting the draft EIS may be charged a fee which is not more than the actual cost of reproducing the copy and also must be informed of the nearest location where the draft EIS may be reviewed without charge. </P>
                                <P>(f) The draft EIS shall be circulated for comment by the applicant on behalf of the U.S. DOT agency. The draft EIS shall be made available to the public and transmitted to agencies for comment no later than the time the document is filed with the Environmental Protection Agency in accordance with 40 CFR 1506.9. The draft EIS shall be transmitted to the following: </P>
                                <P>(1) Public officials, interest groups, and members of the public known to have an interest in the proposed action or alternatives; </P>
                                <P>(2) Federal, State and local government agencies expected to have jurisdiction or responsibility over, or interest or expertise in, the action, and to the State intergovernmental review contacts established under Executive Order 12372; and</P>
                                <P>(3) Neighboring States and Federal land management entities which may be affected by any of the alternatives. </P>
                                <P>(g) Public hearing requirements are to be carried out in accordance with the provisions of § 1420.305 and this section. Whenever a public hearing is held, the draft EIS shall be available at the public hearing and for a minimum of 15 days in advance of the public hearing. The availability of the draft EIS shall be mentioned, and public comments requested, in any public hearing notice and at any public hearing presentation. If a public hearing is not held, a notice shall be placed in a newspaper similar to a public hearing notice advising where the draft EIS is available for review, how copies may be obtained, and where the comments should be sent. </P>
                                <P>(h) Through the U.S. Environmental Protection Agency's notice of availability (40 CFR 1506.10), the U.S. DOT agency shall establish a period of not less than 45 days for the receipt of comments on the draft EIS. The draft EIS or a transmittal letter sent with each copy of the draft EIS shall identify where comments are to be sent and when the comment period ends. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.319 </SECTNO>
                                <SUBJECT>Final environmental impact statements. </SUBJECT>
                                <P>(a)(1) After circulation of a draft EIS and consideration of comments received, a final EIS shall be prepared by the U.S. DOT agency in cooperation with the applicant or, where permitted by 40 CFR 1506.5, by the applicant with appropriate guidance and participation by the U.S. DOT agency. Preparation of the final EIS will involve such additional public involvement, interagency coordination, and engineering or environmental studies as are necessary to consider the appropriateness of refinements in the alternatives and the incorporation of mitigation measures and environmental enhancements in response to comments received on the draft EIS. </P>
                                <P>(2) Every reasonable effort shall be made to resolve interagency disagreements on actions before processing the final EIS. If major issues remain unresolved, the final EIS shall identify those issues and the coordination and other efforts made to resolve them. </P>
                                <P>(3) The final EIS shall evaluate all reasonable alternatives considered and identify the preferred alternative. It shall also discuss substantive comments received on the draft EIS and responses thereto, summarize public involvement and interagency coordination, and describe the environmental design features, including mitigation measures and environmental enhancements, that are incorporated into the proposed action. Environmental design features or other mitigation measures presented as commitments in the final EIS shall be incorporated into the action. The final EIS shall also document compliance with other related environmental laws, regulations, and executive orders applicable to the action, and, if full compliance is not possible, provide reasonable assurance that the requirements will be met. </P>
                                <P>(b) The U.S. DOT agency will indicate approval of the final EIS by signing and dating the cover page. Approval of the final EIS does not commit the U.S. DOT agency to approve any future grant request. </P>
                                <P>(c) The initial printing of the final EIS shall be in sufficient quantity to meet the request for copies which can be reasonably expected from agencies, organizations, and individuals. Normally, copies will be furnished free of charge. However, with U.S. DOT agency concurrence, the party requesting the final EIS may be charged a fee which is not more than the actual cost of reproducing the copy and also must be informed of the nearest location where the final EIS may be reviewed without charge. </P>
                                <P>
                                    (d) The final EIS shall be transmitted to any persons, organizations, or agencies that made substantive comments on the draft EIS and to anyone requesting a copy, no later than the time the document is filed with the U.S. EPA. In the case of lengthy documents, the U.S. DOT agency may allow alternative circulation processes in accordance with 40 CFR 1502.19. The applicant shall publish a notice of availability in local newspapers and make the final EIS available through the mechanism established pursuant to DOT Order 4600.13 
                                    <SU>2</SU>
                                    <FTREF/>
                                     which implements Executive Order 12372. The final EIS shall be available for public review at the applicant's offices and at appropriate DOT agency offices for at least 30 days after the U.S. EPA publication of the 
                                    <E T="04">Federal Register</E>
                                     notice of availability. Copies should also be made available for public review at institutions such as local government 
                                    <PRTPAGE P="33987"/>
                                    offices, libraries, and schools, as appropriate. 
                                </P>
                                <FTNT>
                                    <P>
                                        <SU>2</SU>
                                         This document is available for inspection and copying as prescribed in 49 CFR part 7.
                                    </P>
                                </FTNT>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.321 </SECTNO>
                                <SUBJECT>Record of decision. </SUBJECT>
                                <P>
                                    (a) The U.S. DOT agency will complete and sign a record of decision (ROD) no sooner than 30 days after the U.S. EPA publication in the 
                                    <E T="04">Federal Register</E>
                                     of the notice of availability for the final EIS or 90 days after the U.S. EPA publication of the notice for the draft EIS, whichever is later. The ROD will present the basis for the decision as specified in 40 CFR 1505.2, summarize any mitigation measures and environmental enhancements that have been incorporated into the action, and document any required section 4(f) approval in accordance with 23 CFR part 1430. Until the ROD has been signed, no further approvals relative to the action may be given except those for administrative activities taken to secure further project funding and for other activities consistent with the limitation on actions in 40 CFR 1506.1. The applicant, in coordination with the U.S. DOT agency shall publish a notice of availability of the ROD for public review in a newspaper of general circulation, and, to the extent practicable, provide the approved ROD to all persons, organizations, and agencies that received a copy of the final EIS pursuant to § 1420.319(d). 
                                </P>
                                <P>(b) After issuance of a ROD, the U.S. DOT agency shall issue a revised ROD if it wishes to approve an alternative which was not identified as the preferred alternative but was fully evaluated in the final EIS or proposes to make substantial changes to the mitigation measures or findings discussed in the original ROD. Before issuing the revised ROD, the U.S. DOT agency shall consider whether additional notification, interagency coordination, and public involvement are needed in accordance with § 1420.303 and § 1420.305. To the extent practicable the approved revised ROD shall be provided to all persons, organizations and agencies that received a copy of the Final EIS pursuant to § 1420.319(d). </P>
                                <P>(c) Upon approval of the ROD, the mitigation and environmental enhancements in the final EIS associated with the alternative selected in the ROD become enforceable conditions of any subsequent grant related to the action or other DOT agency approval of the action. The U.S. DOT agency will ensure implementation of mitigation and environmental enhancements as described in § 1420.113. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.323 </SECTNO>
                                <SUBJECT>Re-evaluations. </SUBJECT>
                                <P>(a) A written evaluation of the draft EIS shall be prepared by the applicant in cooperation with the U.S. DOT agency if a final EIS is not approved by the U.S. DOT agency within three years from the date of the draft EIS circulation. The purpose of this evaluation is to determine whether a supplement to the draft EIS or a new draft EIS is needed. </P>
                                <P>(b) A written evaluation of the final EIS will be required before further approvals may be granted if major steps to advance the action (e.g., authority to undertake final design, authority to acquire a significant portion of the right-of-way, or approval of the plans, specifications and estimates) have not occurred within three years after the approval of the final EIS, final EIS supplement, or the last major DOT agency approval or grant. </P>
                                <P>(c) After approval of the EIS, FONSI, or CE designation, the applicant shall consult with the U.S. DOT agency prior to requesting any major approvals or grants to establish whether or not the approved environmental document or CE designation remains valid for the requested U.S. DOT action. These consultations will be documented when determined necessary by the U.S. DOT agency. </P>
                                <P>(d) A re-evaluation under this section shall include additional notification, interagency coordination, and public involvement as appropriate in accordance with § 1420.303 and § 1420.305. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 1420.325 </SECTNO>
                                <SUBJECT>Supplemental environmental impact statements. </SUBJECT>
                                <P>(a) A draft EIS or final EIS may be supplemented whenever the U.S. DOT agency determines that supplementation would improve decisionmaking, better inform the agency or the public, or serve other purposes. An EIS shall be supplemented whenever the U.S. DOT agency determines that: </P>
                                <P>(1) Changes to the proposed action would result in significant environmental impacts that were not evaluated in the EIS. </P>
                                <P>(2) New information or circumstances relevant to environmental concerns and bearing on the proposed action or its impacts would result in significant environmental impacts not evaluated in the EIS. </P>
                                <P>(b) A supplemental EIS will not be necessary where: </P>
                                <P>(1) The changes to the proposed action, new information, or new circumstances result in the actual lessening of adverse environmental impacts evaluated in the EIS without causing other environmental impacts that are significant and were not evaluated in the EIS; or </P>
                                <P>(2) The U.S. DOT agency decides to approve an alternative fully evaluated in an approved final EIS but not identified as the preferred alternative. In such a case, a ROD shall be prepared and circulated in accordance with § 1420.321. </P>
                                <P>(c) Where the U.S. DOT agency is uncertain of the significance of the new impacts, the applicant will develop appropriate environmental studies or, if the U.S. DOT agency deems appropriate, an EA to assess the impacts of the changes, new information, or new circumstances. If, based upon the studies, the U.S. DOT agency determines that a supplemental EIS is not necessary, the U.S. DOT agency shall so indicate in the project file. </P>
                                <P>(d) A supplement is to be developed using the same process and format (i.e., draft EIS, final EIS, and ROD) as an original EIS, except that scoping is not required. Public involvement and interagency coordination commensurate with the nature and scope of the supplemental EIS shall be conducted in accordance with § 1420.305 and the public involvement procedures developed thereunder. </P>
                                <P>(e) In some cases, a supplemental EIS may be required to address issues of limited scope, such as the extent of proposed mitigation or the evaluation of location or design variations for a limited portion of the overall project. Where this is the case, the preparation of a supplemental EIS shall not necessarily prevent the granting of new approvals; require the withdrawal of previous approvals; or require the suspension of project activities for any activity not directly affected by the supplement. If the changes in question are of such magnitude to require a new evaluation of the entire action, or more than a limited portion of the overall action, the U.S. DOT agency shall suspend any activities which would have an adverse environmental impact or limit the choice of reasonable alternatives, until the supplemental EIS is completed. </P>
                            </SECTION>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart D—Definitions </HD>
                            <SECTION>
                                <SECTNO>§ 1420.401 </SECTNO>
                                <SUBJECT>Terms defined elsewhere. </SUBJECT>
                                <P>The definitions contained in the CEQ regulation (40 CFR 1508) and in titles 23 (23 U.S.C. 101) and 49 of the United States Code (49 U.S.C. 14202) are applicable except as modified in § 1420.403. </P>
                            </SECTION>
                            <SECTION>
                                <PRTPAGE P="33988"/>
                                <SECTNO>§ 1420.403 </SECTNO>
                                <SUBJECT>Terms defined in this part. </SUBJECT>
                                <P>The following definitions apply to this part and to part 1430 of this chapter: </P>
                                <P>
                                    <E T="03">Action</E>
                                     means a surface transportation infrastructure or service investment (e.g., highway, transit, railroad, or mixed mode) proposed for direct implementation by the U.S. DOT agency or for the U.S. DOT agency financial assistance; and other activities, such as, joint or multiple use of right-of-way, changes in access control, that require a U.S. DOT agency approval or permit, but may or may not involve a commitment of Federal funds; and other FHWA or FTA program decisions, such as, promulgation of regulations and approval of programs, unless specifically defined by statute or regulation as not being an action. 
                                </P>
                                <P>
                                    <E T="03">Applicant</E>
                                     means the Federal, State or local governmental authority that the U.S. DOT agency works with to conduct environmental studies and prepare environmental documents. For transportation actions implemented by the Federal government on Federal lands, the U.S. DOT agency or the Federal land management agency will take on the responsibilities of the applicant described herein. 
                                </P>
                                <P>
                                    <E T="03">Environmental enhancement</E>
                                     means a measure which contributes to blending the proposed project harmoniously with its surrounding human communities and the natural environment and extends beyond those measures necessary to mitigate the specific adverse impacts resulting from a proposed transportation action. This includes measures eligible for Federal funding, such as transportation enhancement activities or transit enhancements, and measures funded by the applicant or by others. 
                                </P>
                                <P>
                                    <E T="03">Environmental studies</E>
                                     means the investigations of potential social, economic, or environmental impacts conducted: 
                                </P>
                                <P>(1) As part of the metropolitan or statewide transportation planning process under 23 CFR part 1410, </P>
                                <P>(2) To determine the NEPA class of action and scope of analysis, and/or </P>
                                <P>(3) To provide information to be included in a NEPA decision process. </P>
                                <P>
                                    <E T="03">Hardship acquisition</E>
                                     means the early acquisition of property by the applicant at the property owner's request to alleviate particular hardship to the owner, in contrast to others, because of an inability to sell his/her property. This is justified when the property owner can document on the basis of health, safety, or financial reasons that remaining in the property poses an undue hardship compared to others. 
                                </P>
                                <P>
                                    <E T="03">Planning process</E>
                                     means the process of developing metropolitan and statewide transportation plans and programs in accordance with 23 CFR part 1410. 
                                </P>
                                <P>
                                    <E T="03">Protective acquisition</E>
                                     means the purchase of land to prevent imminent development of a parcel which is needed for a proposed transportation corridor or site. Documentation must clearly demonstrate that development of the land would preclude future transportation use and that such development is imminent. Advance acquisition is not permitted for the sole purpose of reducing the cost of property for a proposed project. 
                                </P>
                                <P>
                                    <E T="03">Section 4(f)</E>
                                     means the provision in law which provides protection to certain public lands and all historic properties (now codified in 49 U.S.C. 303 and 23 U.S.C. 138). 
                                </P>
                                <P>
                                    <E T="03">Transportation conformity</E>
                                     means the process for assuring or conformity of transportation projects, programs, and plans with the purpose of State plans for attainment and maintenance of air quality standards under the U.S. EPA regulation at 40 CFR parts 51 and 93. The process applies only to areas designated as nonattainment or maintenance for a transportation related pollutant. 
                                </P>
                                <P>
                                    <E T="03">U.S. DOT agency</E>
                                     means the FHWA, the FTA, or the FHWA and the FTA together. In addition, U.S. DOT agency refers to any other agency within the U.S. Department of Transportation that uses this part as provided for in § 1420.209. 
                                </P>
                                <P>
                                    <E T="03">U.S. DOT agency approval</E>
                                     means the approval by FHWA/FTA of the applicant's request relative to an action. The applicant's request may be for Federal financial assistance, or it may be for some other U.S. DOT agency approval that does not involve a commitment of Federal funds. 
                                </P>
                            </SECTION>
                        </SUBPART>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART 1430—PROTECTION OF PUBLIC PARKS, WILDLIFE AND WATERFOWL REFUGES, AND HISTORIC SITES </HD>
                        <CONTENTS>
                            <SECHD>Sec. </SECHD>
                            <SECTNO>1430.101 </SECTNO>
                            <SUBJECT>Purpose. </SUBJECT>
                            <SECTNO>1430.103 </SECTNO>
                            <SUBJECT>Mandate. </SUBJECT>
                            <SECTNO>1430.105 </SECTNO>
                            <SUBJECT>Applicability. </SUBJECT>
                            <SECTNO>1430.107 </SECTNO>
                            <SUBJECT>Use of land. </SUBJECT>
                            <SECTNO>1430.109 </SECTNO>
                            <SUBJECT>Significance of the section 4(f) resource. </SUBJECT>
                            <SECTNO>1430.111 </SECTNO>
                            <SUBJECT>Exceptions. </SUBJECT>
                            <SECTNO>1430.113 </SECTNO>
                            <SUBJECT>Section 4(f) evaluations and determinations under the NEPA umbrella. </SUBJECT>
                            <SECTNO>1430.115 </SECTNO>
                            <SUBJECT>Separate section 4(f) evaluations. </SUBJECT>
                            <SECTNO>1430.117 </SECTNO>
                            <SUBJECT>Programmatic section 4(f) evaluations. </SUBJECT>
                            <SECTNO>1430.119 </SECTNO>
                            <SUBJECT>Linkage with transportation planning. </SUBJECT>
                            <SECTNO>1430.121 </SECTNO>
                            <SUBJECT>Definitions. </SUBJECT>
                        </CONTENTS>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P> 23 U.S.C. 138 and 315; 49 U.S.C. 303; 49 CFR 1.48 and 1.51. </P>
                        </AUTH>
                        <SECTION>
                            <SECTNO>§ 1430.101 </SECTNO>
                            <SUBJECT>Purpose. </SUBJECT>
                            <P>The purpose of this part is to implement 49 U.S.C. 303 and 23 U.S.C. 138 which were originally enacted as section 4(f) of the Department of Transportation Act of 1966 and are still commonly referred to as section 4(f). </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1430.103 </SECTNO>
                            <SUBJECT>Mandate. </SUBJECT>
                            <P>(a) The U.S. DOT agency may approve a transportation project that uses publicly owned land from a significant public park, recreation area, or wildlife and waterfowl refuge, or any land from a significant historic site only if the U.S. DOT agency has determined that: </P>
                            <P>(1) There is no feasible and prudent alternative to the use of land from the property; and </P>
                            <P>(2) The project includes all possible planning to minimize harm to the property resulting from such use. </P>
                            <P>(b) [Reserved] </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1430.105 </SECTNO>
                            <SUBJECT>Applicability. </SUBJECT>
                            <P>(a) This part applies to transportation projects that require an approval by the U.S. DOT agency, where the U.S. DOT agency has sufficient control and the statutory authority to condition the project or approval. </P>
                            <P>(b) The U.S. DOT agency will determine the applicability of section 4(f) in accordance with this part. </P>
                            <P>(c) This part does not apply to or alter approvals by the U.S. DOT agency made prior to the effective date of this regulation. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1430.107 </SECTNO>
                            <SUBJECT>Use of land. </SUBJECT>
                            <P>(a) Except as set forth in paragraph (b) of this section and § 1430.111, use of land occurs: </P>
                            <P>(1) When land is permanently incorporated into a transportation facility; </P>
                            <P>(2) When there is a temporary occupancy of land that is adverse to the statutory purpose of preserving the natural beauty of that land, as determined by the criteria in paragraph (b) of this section; or </P>
                            <P>(3) When there is a constructive use of land as determined by the criteria in paragraph (c) of this section. </P>
                            <P>(b) A temporary occupancy of land occurs when the use is so minimal that it does not constitute a use within the meaning of section 4(f) (§ 1420.403) when the following conditions are satisfied: </P>
                            <P>(1) The duration of the occupancy must be temporary, i.e., less than the time needed for construction of the project, and there should be no change in ownership of the land; </P>
                            <P>
                                (2) Scope of the work must be minor, i.e., both the nature and the magnitude of the changes to the section 4(f) resource are minimal; 
                                <PRTPAGE P="33989"/>
                            </P>
                            <P>(3) There are no anticipated permanent adverse physical impacts, nor will there be interference with the activities or purposes of the resource, on either a temporary or permanent basis; </P>
                            <P>(4) The land being used must be fully restored, i.e., the resource must be returned to a condition which is at least as good as that which existed prior to the project; and </P>
                            <P>(5) There must be documented agreement of the appropriate Federal, State, or local officials having jurisdiction over the resource regarding the above conditions. </P>
                            <P>(c) A constructive use of section 4(f) land occurs when the transportation project does not incorporate land from the section 4(f) resource, but the impacts of the project on the resource due to its proximity are so severe that the activities, features, or attributes that qualify the resource for the protection of section 4(f) are substantially impaired. The U.S. DOT agencies have reviewed the following situations and have determined that constructive use occurs when: </P>
                            <P>(1) The projected noise level increase attributable to the transportation project substantially interferes with the use and enjoyment of a noise-sensitive facility that is a resource protected by section 4(f), such as hearing the performances at a public outdoor amphitheater, sleeping in the sleeping area of a public campground, enjoyment of a historic site where a quiet setting is a generally recognized feature or attribute of the site's significance, or enjoyment of an urban park where serenity and quiet are significant attributes; </P>
                            <P>(2) The proximity of the project to the section 4(f) resource substantially impairs aesthetic features or attributes of a resource protected by section 4(f), where such features or attributes make an important contribution to the value of the resource. For example, substantial impairment of visual or aesthetic qualities occurs where a transportation structure is located in such proximity that it obstructs or eliminates the primary views of an architecturally significant historical building, or substantially detracts from the setting of a park or historic site which derives its value in substantial part from its setting; </P>
                            <P>(3) The project restricts access to the section 4(f) property and, as a result, substantially diminishes the utility of the resource; </P>
                            <P>(4) The vibration impact from operation of the project substantially impairs the use of a section 4(f) resource, such as vibration levels from a rail project that are great enough to affect the structural integrity of a historic building or substantially diminish the utility of the building; or </P>
                            <P>(5) The ecological intrusion of the project substantially diminishes the value of wildlife habitat in a wildlife or waterfowl refuge adjacent to the project or substantially interferes with the access to a wildlife or waterfowl refuge, when such access is necessary for established wildlife migration or critical life cycle processes. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1430.109 </SECTNO>
                            <SUBJECT>Significance of the section 4(f) resource. </SUBJECT>
                            <P>(a) Consideration under section 4(f) is required when the Federal, State, or local officials having jurisdiction over a park, recreation area or refuge determine that the entire section 4(f) resource is significant. In the absence of such a determination, the section 4(f) land will be presumed to be significant, unless the U.S. DOT agency and the officials with jurisdiction have agreed, formally or informally, that the resource is not significant. The U.S. DOT agency will review the significance determination to assure its reasonableness. </P>
                            <P>(b) Section 4(f) applies to all properties on or eligible for the National Register of Historic Places. The U.S. DOT agency, in cooperation with the applicant, will consult with the State Historic Preservation Officer (SHPO) and appropriate local officials to identify such historic sites. Section 4(f) applies only to historic sites on or eligible for the National Register unless the U.S. DOT agency determines that the application of section 4(f) to a historic site is otherwise appropriate. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1430.111 </SECTNO>
                            <SUBJECT>Exceptions. </SUBJECT>
                            <P>(a) Consideration under section 4(f) is not required for any park road or parkway project developed in accordance with 23 U.S.C. 204. </P>
                            <P>(b) Consideration under section 4(f) is not required for trail-related projects funded through the Symms National Recreational Trails Act of 1991 (16 U.S.C. 1261). </P>
                            <P>(c) Consideration under section 4(f) is not required for “transportation enhancement activities” as defined in 23 U.S.C. 101(a) and transit enhancements as defined in 49 U.S.C. 5302(a)(15) if: </P>
                            <P>(1) The use of the section 4(f) property is solely for the purpose of preserving or enhancing the activities, features, or attributes that qualify the property for section 4(f) protection; and </P>
                            <P>(2) The Federal, State, or local official having jurisdiction over the property agrees in writing that the use is solely for the purpose of preserving or enhancing the section 4(f) activities, features, or attributes of the property and will, in fact, accomplish this purpose. </P>
                            <P>(d) Where Federal lands or other public land holdings (e.g., State forests) are administered under statutes permitting management for multiple uses and are, in fact, managed for multiple uses, section 4(f) applies only to those portions of such lands which function as significant public parks, recreation areas, or wildlife refuges, or which are designated in the plans of the administering agency as being for, significant park, recreation, or wildlife purposes or historic sites. The determination as to which lands so function or are so designated, and the significance of those lands, shall be made by the officials having jurisdiction over the lands. The determination of significance shall apply to the entire area of lands which so function or are so designated. The U.S. DOT agency will review these determinations to assure their reasonableness. </P>
                            <P>(e) Consideration under section 4(f) is not required for the restoration, rehabilitation, or maintenance of transportation facilities that are on or eligible for the National Register when: </P>
                            <P>(1) Such work will not adversely affect the historic qualities of the facility that caused it to be on or eligible for the National Register, and </P>
                            <P>(2) The SHPO has been consulted and has not objected to the U.S. DOT agency finding in paragraph (e)(1) of this section. </P>
                            <P>(f) Archeological sites. </P>
                            <P>(1) Section 4(f) applies to all archeological sites on or eligible for inclusion in the National Register, including those discovered during construction except as set forth in paragraph (f)(2) of this section. When section 4(f) requirements apply to archeological sites discovered during construction, the section 4(f) process will be expedited. In such cases, the evaluation of feasible and prudent alternatives will take into account the level of investment already made in the project. The review process, including the consultation with other agencies, will be shortened as appropriate. </P>
                            <P>
                                (2) Section 4(f) requirements do not apply to archeological sites where the U.S. DOT agency, after consultation with the SHPO, determines that the archeological resource is important chiefly because of what can be learned by data recovery and has minimal value for preservation in place. This exception applies both to situations where data recovery is undertaken or where the U.S. DOT agency decides, with agreement of the SHPO, not to recover the data in the resource. 
                                <PRTPAGE P="33990"/>
                            </P>
                            <P>(g) Designations of park and recreation lands, wildlife and waterfowl refuges, and historic sites are sometimes made, and determinations of significance changed, late in the development of a project. With the exception of the treatment of archeological resources in paragraph (f) of this section, the U.S. DOT agency may permit a project to proceed without consideration under section 4(f) if the property interest in the section 4(f) lands was acquired for transportation purposes prior to the designation or change in the determination of significance and if an adequate effort was made to identify properties protected by section 4(f) prior to acquisition. </P>
                            <P>(h) Constructive use normally does not occur when: </P>
                            <P>(1) Compliance with the requirements of section 106 of the National Historic Preservation Act and 36 CFR part 800 for proximity impacts of the proposed action, on a site listed on or eligible for the National Register of Historic Places results in an agreement of no adverse effect; </P>
                            <P>(2) The projected traffic noise levels of a proposed nearby highway project do not exceed the FHWA noise abatement criteria given in Table 1, 23 CFR part 772, or the projected operational noise levels of a proposed nearby transit project do not exceed the noise impact criteria in the FTA guidelines (Federal Transit Administration, Transit Noise and Vibration Impact Assessment, April 1995, available from the FTA offices); </P>
                            <P>(3) The projected noise levels exceed the relevant threshold in paragraph (h)(2) of this section because of high existing noise, but the increase in the projected noise levels if the proposed project is constructed, when compared with the projected noise levels if the project is not built, is barely perceptible (3 dBA or less); </P>
                            <P>(4) A proposed transportation project will have proximity impacts on a section 4(f) property, but a governmental agency's right-of-way acquisition, an applicant's adoption of project location, or the U.S. DOT agency approval of a final NEPA document established the location of the project before the designation, establishment, or change in the significance of the section 4(f) property. However, if the property in question is a historic site that would be eligible for the National Register except for its age at the time that the project location is established, and construction of the project would begin after the site became eligible, then constructive use of the historic site may occur and such use must be evaluated; </P>
                            <P>(5) There are proximity impacts to a proposed public park, recreation area, or wildlife refuge, but the proposed transportation project and the resource are concurrently planned or developed. The following examples of such concurrent planning or development include, but are not limited to: </P>
                            <P>(i) Designation or donation of property for the specific purpose of such concurrent development by the entity with jurisdiction or ownership of the property for both the potential transportation project and the section 4(f) resource; or </P>
                            <P>(ii) Designation, donation, planning or development of property by two or more governmental agencies, with jurisdiction for the potential transportation project and the section 4(f) resource, in consultation with each other; </P>
                            <P>(iii) Overall (combined) proximity impacts caused by a proposed project do not substantially impair the activities, features, or attributes that qualify a resource for protection under section 4(f); </P>
                            <P>(iv) Proximity impacts will be mitigated to a condition equivalent to, or better than, that which would occur under a no-build scenario; </P>
                            <P>(v) Change in accessibility will not substantially diminish the utilization of the section 4(f) resource; or </P>
                            <P>(vi) Vibration levels from project construction activities are mitigated, through advance planning and monitoring of the activities, to levels that do not cause a substantial impairment of the section 4(f) resource. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1430.113 </SECTNO>
                            <SUBJECT>Section 4(f) evaluations and determinations under the NEPA umbrella. </SUBJECT>
                            <P>(a) Alternatives to avoid the use of section 4(f) properties and measures to minimize harm to such land shall be developed and evaluated by the applicant in cooperation with the U.S. DOT agency. Such evaluation shall be initiated early when alternatives are under study. An alternative that avoids section 4(f) property must be preferred unless the evaluation demonstrates that there are unique problems or unusual factors associated with it, or that the cost, the social, economic, or environmental impacts, or the community disruption resulting from such alternative reach extraordinary magnitudes. </P>
                            <P>(b) In accordance with the concept of the NEPA umbrella in 23 CFR 1420.109, the section 4(f) evaluation is normally presented in the draft environmental impact statement (EIS), the environmental assessment (EA), or the categorical exclusion (CE) documentation. The evaluation may incorporate relevant information from the planning process in accordance with § 1430.119. A separate section 4(f) evaluation may be necessary as described in section § 1430.115. </P>
                            <P>(c) The section 4(f) evaluation shall be provided for coordination and comment to the officials having jurisdiction over the section 4(f) property and to the U.S. Department of the Interior, and as appropriate to the U.S. Department of Agriculture and the U.S. Department of Housing and Urban Development. A minimum of 45 days shall be established by the U.S. DOT agency for receipt of comments. </P>
                            <P>(d) When adequate support exists for a section 4(f) determination, the discussion in the final EIS, the finding of no significant impact (FONSI), the CE documentation, or the separate section 4(f) evaluation shall specifically address the following: </P>
                            <P>(1) The reasons why the alternatives to avoid a section 4(f) property are not feasible and prudent; and </P>
                            <P>(2) All measures incorporated into the project that will be taken to minimize harm to the section 4(f) property. </P>
                            <P>(e) The U.S. DOT agency is not required to determine that there is no constructive use. However, such a determination may be made at the discretion of the U.S. DOT agency. When a constructive use determination is made, it will be based, to the extent it reasonably can, upon the following: </P>
                            <P>(1) Identification of the current activities, features, or attributes of a resource that qualify it for protection under section 4(f) and which may be sensitive to proximity impacts; </P>
                            <P>(2) An analysis of the proximity impacts of the proposed project on the section 4(f) resource. If any of the proximity impacts will be mitigated, only the net impact need be considered in this analysis. The analysis should also describe and consider the impacts which could reasonably be expected if the proposed project were not implemented, since such impacts should not be attributed to the proposed project; and </P>
                            <P>(3) Consultation, on the above identification and analysis, with the Federal, State, or local officials having jurisdiction over the park, recreation area, refuge, or historic site. </P>
                            <P>
                                (f) For actions processed with an EIS, the U.S. DOT agency will make the section 4(f) determination either in its approval of the final EIS or in the record of decision (ROD). Where the section 4(f) approval is documented in the final EIS, the U.S. DOT agency will summarize the basis for its section 4(f) approval in the ROD. Actions requiring the use of section 4(f) property, and 
                                <PRTPAGE P="33991"/>
                                proposed to be processed with a FONSI or classified as a CE, shall not proceed until the U.S. DOT agency has given notification of section 4(f) approval. For these actions, any required section 4(f) approval will be documented in the FONSI, in the CE approval, if one is provided, or in a separate section 4(f) document. 
                            </P>
                            <P>(g) The final section 4(f) evaluation will be reviewed for legal sufficiency. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1430.115 </SECTNO>
                            <SUBJECT>Separate section 4(f) evaluations. </SUBJECT>
                            <P>(a) Circulation of a separate section 4(f) evaluation will be required when: </P>
                            <P>(1) A proposed modification of the alignment or design would require the use of section 4(f) land after the CE, FONSI, draft EIS, or final EIS has been processed; </P>
                            <P>(2) A proposed modification of the alignment, design, or measures to minimize harm after an original section 4(f) approval, would result in a substantial increase in the use of section 4(f) land or a substantial reduction in the measures to minimize harm included in the project; </P>
                            <P>(3) The U.S. DOT agency determines, after processing the CE, FONSI, draft EIS, or final EIS that section 4(f) applies to a property; or </P>
                            <P>(4) An agency whose actions are not subject to section 4(f) requirements is the lead agency for the NEPA process on an action that involves section 4(f) property and requires a U.S. DOT agency action. </P>
                            <P>(b) If the U.S. DOT agency determines under paragraph (a) of this section or otherwise, that section 4(f) is applicable after the CE, FONSI, or ROD has been processed, the decision to prepare and circulate a section 4(f) evaluation will not necessarily require the preparation of a new or supplemental NEPA document. Where a separately circulated section 4(f) evaluation is prepared after the CE, FONSI, or ROD has been processed, such evaluation does not necessarily: </P>
                            <P>(1) Prevent the granting of new approvals; </P>
                            <P>(2) Require the withdrawal of previous approvals; or </P>
                            <P>(3) Require the suspension of project activities for any activity not affected by the new section 4(f) evaluation. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1430.117 </SECTNO>
                            <SUBJECT>Programmatic section 4(f) evaluations. </SUBJECT>
                            <P>The U.S. DOT agency, in consultation with the U.S. Department of the Interior and other agencies, as appropriate, may make a programmatic section 4(f) determination for a class of similar projects. Uses of section 4(f) land covered by a programmatic section 4(f) evaluation shall be documented and coordinated as specified in the programmatic section 4(f) evaluation. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1430.119 </SECTNO>
                            <SUBJECT>Linkage with transportation planning. </SUBJECT>
                            <P>(a) An analysis required by section 4(f) may involve different levels of detail where the section 4(f) involvement is addressed during the planning process or in a tiered EIS. </P>
                            <P>(b) When a planning document or a first-tier EIS is intended to provide the basis for subsequent project development as provided in § 1420.201 and 40 CFR 1502.20, the detailed information necessary to complete the section 4(f) evaluation may not be available at that stage in the development of the action. In such cases, an evaluation should be made of the potential impacts that a proposed action will have on section 4(f) land and whether those impacts could have a bearing on the decision to be made. A preliminary determination may be made at this time as to whether there are feasible and prudent locations or alternatives for the action to avoid the use of section 4(f) land. This preliminary determination shall consider all possible planning to minimize harm, to the extent that the level of detail at this stage allows. It is recognized that such planning at this stage will normally be limited to ensuring that opportunities to minimize harm at subsequent stages in the project development process have not been precluded by decisions made at this stage. This preliminary determination is then incorporated into official planning documents or the first-tier EIS. </P>
                            <P>(c) A section 4(f) approval made when additional design details are available will include a determination that: </P>
                            <P>(1) The preliminary section 4(f) determination made pursuant to paragraph (a) remains valid; and </P>
                            <P>(2) The criteria of § 1430.103 and § 1430.113(a) have been met. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1430.121 </SECTNO>
                            <SUBJECT>Definitions. </SUBJECT>
                            <P>The definitions contained in 23 CFR 1420.403, 23 U.S.C. 101(a), 49 U.S.C. 5302, and 40 CFR part 1508 are applicable to this part.</P>
                            <HD SOURCE="HD1">Federal Transit Administration </HD>
                        </SECTION>
                    </PART>
                    <LSTSUB>
                        <HD SOURCE="HED"> </HD>
                        <CFR>49 CFR Chapter VI</CFR>
                        <P>For the reasons set forth in the preamble, the Federal Transit Administration proposes to amend chapter VI of title 49, Code of Federal Regulations, as follows: </P>
                    </LSTSUB>
                    <P>3. Revise part 622 to read as follows: </P>
                    <PART>
                        <HD SOURCE="HED">PART 622—NEPA AND RELATED PROCEDURES FOR TRANSPORTATION DECISIONMAKING </HD>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart A—Purpose, Policy, and Mandate </HD>
                        </SUBPART>
                        <CONTENTS>
                            <SECHD>Sec. </SECHD>
                            <SECTNO>622.101 </SECTNO>
                            <SUBJECT>Cross-reference to subpart A of 23 CFR part 1420. </SUBJECT>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart B—Program and Project Streamlining </HD>
                                <SECTNO>622.201 </SECTNO>
                                <SUBJECT>Cross-reference to subpart B of 23 CFR part 1420. </SUBJECT>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart C—Process and Documentation Requirements </HD>
                                <SECTNO>622.301 </SECTNO>
                                <SUBJECT>Cross-reference to subpart C of 23 CFR part 1420. </SUBJECT>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart D—Definitions </HD>
                                <SECTNO>622.401 </SECTNO>
                                <SUBJECT>Cross-reference to subpart D of 23 CFR part 1420.</SUBJECT>
                            </SUBPART>
                        </CONTENTS>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                23 U.S.C. 109, 128, 134 and 138; 42 U.S.C. 2000d-2000d-4, 4321 
                                <E T="03">et seq.</E>
                                , and 7401 
                                <E T="03">et seq.</E>
                                ; 49 U.S.C. 303, 5301(e), 5303, 5309, and 5324(b) and (c); 49 CFR 1.51. 
                            </P>
                        </AUTH>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart A—Purpose, Policy, and Mandate </HD>
                            <SECTION>
                                <SECTNO>§ 622.101 </SECTNO>
                                <SUBJECT>Cross-reference to subpart A of 23 CFR part 1420. </SUBJECT>
                                <P>The regulations for complying with this subpart are set forth in subpart A of 23 CFR part 1420. </P>
                            </SECTION>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart B—Program and Project Streamlining </HD>
                            <SECTION>
                                <SECTNO>§ 622.201 </SECTNO>
                                <SUBJECT>Cross-reference to subpart B of 23 CFR part 1420. </SUBJECT>
                                <P>The regulations for complying with this subpart are set forth in subpart B of 23 CFR part 1420. </P>
                            </SECTION>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart C—Process and Documentation Requirements </HD>
                            <SECTION>
                                <SECTNO>§ 622.301 </SECTNO>
                                <SUBJECT>Cross-reference to subpart C of 23 CFR part 1420. </SUBJECT>
                                <P>The regulations for complying with this subpart are set forth in subpart C of 23 CFR part 1420. </P>
                            </SECTION>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart D—Definitions </HD>
                            <SECTION>
                                <SECTNO>§ 622.401 </SECTNO>
                                <SUBJECT>Cross-reference to subpart D of 23 CFR part 1420. </SUBJECT>
                                <P>The regulations for complying with this subpart are set forth in subpart D of 23 CFR part 1420. </P>
                                <P>
                                    4. Add a new part 623 to read as follows: 
                                    <PRTPAGE P="33992"/>
                                </P>
                            </SECTION>
                        </SUBPART>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART 623—PROTECTION OF PUBLIC PARKS, WILDLIFE AND WATERFOWL REFUGES, AND HISTORIC SITES </HD>
                        <CONTENTS>
                            <SECHD>Sec. </SECHD>
                            <SECTNO>623.101 </SECTNO>
                            <SUBJECT>Cross-reference to 23 CFR part 1430. </SUBJECT>
                        </CONTENTS>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>49 U.S.C. 303; 49 CFR 1.51. </P>
                        </AUTH>
                        <SECTION>
                            <SECTNO>§ 623.101 </SECTNO>
                            <SUBJECT>Cross-reference to 23 CFR part 1430. </SUBJECT>
                            <P>The regulations for complying with 49 U.S.C. 303 are set forth in 23 CFR part 1430. </P>
                        </SECTION>
                        <SIG>
                            <DATED>Issued on: May 18, 2000.</DATED>
                            <NAME>Vincent F. Schimmoller,</NAME>
                            <TITLE>Acting Executive Director, Federal Highway Administration.</TITLE>
                            <NAME>Nuria I. Fernandez,</NAME>
                            <TITLE>Acting Administrator, Federal Transit Administration.</TITLE>
                        </SIG>
                    </PART>
                </SUPLINF>
                <FRDOC>[FR Doc. 00-13022 Filed 5-19-00; 1:15 pm] </FRDOC>
                <BILCOD>BILLING CODE 4910-MR-P </BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>65</VOL>
    <NO>102</NO>
    <DATE>Thursday, May 25, 2000 </DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="33993"/>
            <PARTNO>Part V</PARTNO>
            <AGENCY TYPE="P">Department of Transportation</AGENCY>
            <SUBAGY>Federal Highway Administration</SUBAGY>
            <HRULE/>
            <CFR>23 CFR Parts 655 and 940</CFR>
            <TITLE>Intelligent Transportation System Architecture and Standards; Proposed Rule </TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="33994"/>
                    <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                    <SUBAGY>Federal Highway Administration </SUBAGY>
                    <CFR>23 CFR Parts 655 and 940 </CFR>
                    <DEPDOC>[FHWA Docket No. FHWA-99-5899] </DEPDOC>
                    <RIN>RIN 2125-AE65 </RIN>
                    <SUBJECT>Intelligent Transportation System Architecture and Standards </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Federal Highway Administration (FHWA), DOT. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice of proposed rulemaking (NPRM); request for comments. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            The FHWA proposes to implement section 5206(e) of the Transportation Equity Act for the 21st Century (TEA-21), enacted on June 9, 1998, requiring Intelligent Transportation System (ITS) projects funded through the highway trust fund to conform to the National ITS Architecture and applicable standards. Because it is highly unlikely that the entire National ITS Architecture would be fully implemented by any single metropolitan area or State, the FHWA proposes in this NPRM (the ITS Architecture NPRM) that the National ITS Architecture be used to develop a local implementation of the National ITS Architecture, which is referred to as an “ITS regional architecture.” Therefore, conformance with the National ITS Architecture is defined under this proposal as development of an ITS regional architecture based on the National ITS Architecture, and the subsequent adherence of ITS projects to the ITS regional architecture. The ITS regional architecture would consist of a concept of operations and a conceptual design, which would draw from the National ITS Architecture, but would be tailored to address the local situation and ITS investment needs. The ITS regional architecture follows from the ITS integration strategy developed in another NPRM entitled “Statewide Transportation Planning; Metropolitan Transportation Planning” also published in today's 
                            <E T="04">Federal Register</E>
                            . In this NPRM, the FHWA proposes the use of the system engineering process and applicable standards and interoperability tests adopted by the DOT. 
                        </P>
                    </SUM>
                    <DATES>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            Written comments must be received on or before August 23, 2000. For dates of public information meetings see 
                            <E T="02">Supplementary Information.</E>
                        </P>
                    </DATES>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            Signed, written comments should refer to the docket number that appears at the top of this document and must be submitted to the Docket Clerk, U.S. DOT Dockets, Room PL-40, 400 Seventh Street, SW, Washington, D.C. 20590-0001. All comments received will be available for examination at the above address between 9 a.m. and 5 p.m. e.t., Monday through Friday, except Federal holidays. Those desiring notification of receipt of comments must include a self-addressed, stamped envelope or postcard. For addresses of public information meetings see 
                            <E T="02">Supplementary Information.</E>
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            <E T="03">For technical information</E>
                            : Mr. Bob Rupert, (202) 366-2194, Office of Travel Management (HOTM-1) and Mr. Mike Freitas, (202) 366-9292, ITS Joint Program Office. 
                            <E T="03">For legal information</E>
                            : Mr. Wilbert Baccus, Office of the Chief Counsel (HCC-32), (202) 366-1346, Federal Highway Administration, 400 Seventh Street, SW., Washington, D.C. 20590. Office hours are from 8 a.m. to 4:30 p.m., e.t., Monday through Friday, except Federal holidays. 
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">Electronic Access </HD>
                    <P>
                        Internet users may access all comments received by the US DOT Dockets, Room PL-401, by using the universal resource locator (URL): 
                        <E T="03">http:­//dms.dot.gov.</E>
                         It is available 24 hours each day, 365 days each year. Please follow the instructions online for more information and help. 
                    </P>
                    <P>
                        An electronic copy of this document may be downloaded by using a computer, modem, and suitable communications software from the Government Printing Office's Electronic Bulletin Board Service at (202) 512-1661. Internet users may reach the Office of the 
                        <E T="04">Federal Register</E>
                        's home page at 
                        <E T="03">http://www.nara.gov/fedreg</E>
                         and the Government Printing Office's web page at: 
                        <E T="03">http://www.access.gpo.gov/nara.</E>
                    </P>
                    <P>
                        The document may also be viewed at the DOT's ITS home page at 
                        <E T="03">http://www.its.dot.gov.</E>
                    </P>
                    <HD SOURCE="HD1">Public Information Meetings </HD>
                    <P>The DOT will hold a series of seven public briefings within the comment period for the NPRM. The purposes of these briefings is to explain the content of the NPRM and encourage public input to the final rulemaking. The meetings will address this NPRM, a companion NPRM on the metropolitan and statewide planning process (FHWA RIN 2125-AE62; FTA RIN 2132-AA66), and the NPRM entitled, “NEPA [National Environmental Policy Act of 1969] and Related Procedures for Transportation Decisionmaking, Protection of Public Parks, Wildlife and Waterfowl Refuges, and Historic Sites” (NEPA/NPRM; FHWA RIN 2125-AE64; FTA RIN 2132-AA43). The meetings will be scheduled from approximately 8:00 a.m. to 5:00 p.m. at the locations listed below. Changes in the information below will be made available after the publication of this NPRM through the FHWA and the FTA websites, other public announcement avenues and the newsletters and websites of major stakeholder groups. Individuals wishing information but without access to these sources may contact the individuals listed above. </P>
                    <P>The structure of the meetings will emphasize brief presentations by the DOT staff regarding the content of the NPRMs. A period for clarifying questions will be provided. Under current statutory and regulatory provisions, the DOT staff will not be permitted to engage in a substantive dialog regarding what the content of the NPRMs and the final regulations should be. Attendees wishing to express ideas and thoughts regarding the final content of the rules should direct those comments to the docket. Briefing sites will include: Boston, MA, Auditorium, Volpe National Transportation Systems Center, 55 Broadway, June 9, 2000; Atlanta, GA, Westin Peachtree Plaza Hotel, 210 Peachtree Street, June 20, 2000; Washington, D.C., Marriott Metro Center, 775 12th Street NW, June 23, 2000; Chicago, IL, Holiday Inn Mart Plaza, 350 North Orleans Street, June 27, 2000; Denver, CO, Marriott City Center, 1701 California Street, June 30, 2000; Dallas, TX, Hyatt Regency Dallas, 300 Reunion Boulevard, July 11, 2000; and San Francisco, CA, Radisson Miyako, 1625 Post Street, July 19, 2000. </P>
                    <P>
                        As part of the outreach process planned for these proposed rules, the FHWA/FTA will be conducting a national teleconference on June 15, 2000 from 1-4 p.m. eastern time, through the auspices of the Center for Transportation and the Environment at North Carolina State University. The teleconference will be accessible through numerous downlink locations nationwide and further information can be obtained from Katie McDermott at kpm@unity.ncsu.edu. The purpose of the teleconference is to describe the proposed new statewide and metropolitan planning, National Environmental Policy Act (NEPA) implementation, and Intelligent Transportation Systems (ITS) rules. An overview of each of the three Notices of Proposed Rulemaking (NPRMs) will be presented and the audience (remote and local) will have opportunities to ask questions and seek clarification of 
                        <PRTPAGE P="33995"/>
                        FHWA/FTA proposals. By sponsoring this teleconference it is hoped that interest in the NPRMs is generated, that stakeholders will be well informed about FHWA/FTA proposals, and that interested parties will participate in the rulemaking process by submitting written suggestions, comments and concerns to the docket. 
                    </P>
                    <HD SOURCE="HD1">Introduction </HD>
                    <P>Section 5206(e) of the TEA-21, Public Law 105-178, 112 Stat. 107, at 457, requires ITS projects funded through the highway trust fund to conform to the National ITS Architecture, applicable or provisional standards, and protocols. </P>
                    <P>
                        The proposed implementing regulations for this provision of law are contained in two NPRMs. The first NPRM for revisions to the Statewide and Metropolitan transportation planning processes, 23 CFR part 1410, published separately in today's 
                        <E T="04">Federal Register</E>
                        , contains language specific to ITS projects pertaining to implementation of section 5206(e)—§§ 1410.104 (Definition of ITS Integration Strategy), 1410.310(g) (Agreements), 1410.322(b)(11) (Plan and Integration Strategy Content), 1410.214 (a)(3), and 1410.216(c)(8) (State Transportation Improvement Program Content). The second NPRM concerning the ITS Architecture would add part 940 to subchapter K to implement section 5206(e) of TEA-21. The FHWA believes the proposed rules, 23 CFR parts 1410 and 940, would implement the legislative requirement for conforming to the national architecture and standards. 
                    </P>
                    <HD SOURCE="HD1">Background </HD>
                    <P>Intelligent transportation systems represent the application of information processing, communications technologies, advanced control strategies, and electronics to the field of transportation. Information technology in general is most effective and cost beneficial when systems are integrated and interoperable. The greatest benefits in terms of safety, efficiency, and costs are realized when electronic systems are systematically integrated to form a whole in which information is shared with all and systems are interoperable. </P>
                    <P>In the transportation sector, successful ITS integration and interoperability require addressing two different and yet fundamental issues; that of technical and institutional integration. “Technical integration” of electronic systems is a complex issue that requires considerable up-front planning and meticulous execution for electronic information to be stored and accessed by various parts of a system. “Institutional integration” involves coordination between various agencies and jurisdictions to achieve seamless operations and/or interoperability. In order to achieve effective institutional integration of systems, agencies and jurisdictions must agree on the benefits of ITS and the value of being part of an integrated system. They must agree on roles, responsibilities, and shared operational strategies. Finally, they must agree on standards and, in some cases, technologies and operating procedures to ensure interoperability. In some instances, there may be multiple standards that could be implemented for a single interface. In this case, agencies will need to agree on a common standard or agree to implement a technical translator that will allow dissimilar standards to interoperate. This coordination effort is a considerable task that will happen over time, not all at once. Transportation organizations, such as, transit properties, State and local transportation agencies, and metropolitan planning organizations must be fully committed to achieving institutional integration in order for integration to be successful. The transportation agencies must also coordinate with agencies for which transportation is a key, but not a primary part of their business, such as, emergency management and law enforcement agencies. </P>
                    <P>Successfully dealing with both the technical and institutional issues requires a high-level conceptual view of the future system and careful, comprehensive planning. The framework for the system is referred to as the “architecture.” The architecture defines the system components, key functions, the organizations involved, and the type of information shared between organizations and parts of the system. The architecture is, therefore, fundamental to successful system implementation, integration, and interoperability. </P>
                    <HD SOURCE="HD1">The National ITS Architecture </HD>
                    <P>The Intermodal Surface Transportation Efficiency Act of 1991, Public Law 102-240, 105 Stat. 1914, initiated Federal funding for the ITS program. The program at that time was largely focused on research and development and operational tests of technologies. A key part of the program was the development of the “National ITS Architecture.” The National ITS Architecture provides a common structure for the design of ITS systems. The architecture defines the functions that could be performed to satisfy user requirements and how the various elements of the system might connect to share information. It is not a system design, nor is it a design concept. However, it does define the framework around which multiple design approaches can be developed, each one specifically tailored to meet the needs of the user, while maintaining the benefits of a common approach. The National ITS Architecture, Version 3.0 can be obtained from the ITS Joint Program Office of the DOT in CD-ROM format and on the ITS web site http://www.its.dot.gov. The effort to develop a common national system architecture to guide the evolution of ITS in the United States over the next 20 years and beyond has been managed since September 1993 by the FHWA. The National ITS Architecture describes in detail what types of interfaces should exist between ITS components and how they will exchange information and work together to deliver the given ITS user service requirements. The National ITS Architecture and standards can be used to guide multi-level government and private-sector business planners in developing and deploying nationally compatible systems. By ensuring system compatibility, the DOT hopes to accelerate ITS integration nationwide and develop a strong, diverse marketplace for related products and services. </P>
                    <P>It is highly unlikely that the entire National ITS Architecture will be fully implemented by any single metropolitan area or State. For example, the National ITS Architecture contains information flows for an Automated Highway System that is unlikely to be part of most regional implementations. However, the architecture has considerable value as a framework for local governments in the development of regional architectures by identifying the many functions and information sharing opportunities that may be desired. It can assist local governments with both of the key elements—technical interoperability and institutional coordination. </P>
                    <P>
                        The National ITS Architecture, because it aids in the development of a high-level conceptual view of a future system, can assist local governments in identifying applications that will support their future transportation needs. From an institutional coordination perspective, the National ITS Architecture helps local transportation planners to identify other stakeholders who may need to be involved and to identify potential integration opportunities. From a technical interoperability perspective, the National ITS Architecture provides a logical and physical architecture and 
                        <PRTPAGE P="33996"/>
                        process specifications to guide the design of a system. The National ITS Architecture also identifies interfaces where standards may apply, further supporting interoperability. 
                    </P>
                    <HD SOURCE="HD1">Transportation Equity Act for the 21st Century </HD>
                    <P>As noted above, section 5206(e) of the TEA-21 requires ITS projects funded from the highway trust fund to conform to the National ITS Architecture, applicable or provisional standards, and protocols. The purpose of the statute is to accelerate the deployment of interoperable ITS systems. Use of the National ITS Architecture provides significant benefits to local transportation planners and deployers as follows: </P>
                    <P>1. The National ITS Architecture provides assistance with technical design. It saves considerable design time because physical and logical architectures are already defined. </P>
                    <P>2. Information flows and process specifications are defined in the National ITS Architecture, allowing local governments to accelerate the process of defining system functionality. </P>
                    <P>3. The architecture identifies standards that will support interoperability now and into the future, but it leaves selection of technologies to local decisionmakers. </P>
                    <P>4. The architecture provides a sound engineering framework for integrating multiple applications and services in a region. </P>
                    <HD SOURCE="HD1">Transportation Planning Process </HD>
                    <P>The existing transportation planning processes under titles 23 and 49, U.S.C., require a continuing, comprehensive, and coordinated approach to assessing transportation needs, evaluating a range of solutions, and providing a coordinated response through transportation investments. The TEA-21 further emphasizes operations and management of the transportation network as a key consideration in transportation planning. The transportation planning process is currently institutionalized through statewide and metropolitan planning. </P>
                    <P>
                        Effective implementation of ITS requires careful and comprehensive planning. This notice of proposed rulemaking and the accompanying NPRM on Statewide and Metropolitan Transportation Planning, published separately in today's 
                        <E T="04">Federal Register</E>
                        , propose changes to 23 CFR part 1410 and explains how ITS would be integrated into the planning process. The ITS would become part of the transportation planning process through the locally defined ITS Integration Strategy. This ITS integration strategy would guide future investment decisions and foster integration and interoperability. Developing the strategy as part of the overall transportation planning process would ensure that ITS is given appropriate consideration as a solution for future transportation needs and services. 
                    </P>
                    <P>
                        Consequently, the DOT is issuing an NPRM (23 CFR part 1410), published separately in today's 
                        <E T="04">Federal Register</E>
                        , that proposes to incorporate ITS into the transportation planning process for both metropolitan and statewide planning (in addition to other changes needed to implement the TEA-21). The proposed provisions specific to ITS are set forth in 23 CFR 1410.104, 1410.214(a)(3), 1410.310(g), and 1410.322(b)(11). A summary of the proposed revisions follows: 
                    </P>
                    <P>During the development of the metropolitan and/or statewide transportation plan, if ITS applications are envisioned, the transportation plan shall address an ITS integration strategy. Provision shall be made to include participation of key operating agencies in the development of the integration strategy. The ITS integration strategy shall clearly assess existing and future ITS systems, including their functions and information sharing expectations. Planning for ITS shall produce an agreement among the Metropolitan Planning Organizations (MPOs), State DOTs, transit operators and other agencies which addresses policy and operational issues affecting the successful implementation of the ITS integration strategy. The policy statement shall address provisions to ensure ITS project interoperability, utilization of ITS related standards, and the routine operation of the projects. Further, as provided in proposed 23 CFR 1410.322 (b)(11), the transportation plan shall identify: </P>
                    <P>(1) Major regional ITS initiatives (a program of related projects that are multi-jurisdictional and/or multi-modal), </P>
                    <P>(2) ITS projects of a scale to affect regional integration of ITS systems, and </P>
                    <P>(3) ITS projects that directly support national interoperability. </P>
                    <HD SOURCE="HD1">Project Development Process </HD>
                    <P>The ITS integration strategy that is part of the transportation plan would be general in content, articulating key policies and a vision for the planning area. More detailed conceptual designs and operational procedures, as agreed upon by key stakeholders, are necessary to support project development. This proposed rule seeks to implement this approach as part of the project development process. There are two distinct sections to the proposal. The first deals with development of an ITS regional architecture that lays the foundation for integration in a metropolitan planning area or State. The second deals with final project design and ensuring conformance to both the ITS integration strategy and the ITS regional architecture. </P>
                    <HD SOURCE="HD1">Summary of Proposed Requirements </HD>
                    <HD SOURCE="HD2">I. The ITS Regional Architecture </HD>
                    <P>
                        This NPRM on the ITS Architecture and Standards would require development of a local implementation of the National ITS Architecture referred to as an ITS regional architecture that is consistent with the ITS integration strategy. The ITS regional architecture would be tailored to meet local needs, meaning that it may not address the entire National ITS Architecture and may also address services not included by the National ITS Architecture. The ITS regional architecture may be developed either through an initial regional development effort or incrementally as major ITS investments are anticipated. In either case, the ITS regional architecture should contain a concept of operations and a conceptual design that addresses the integration of new ITS projects as they are advanced. In this context, a “region” is a geographical area that is based on local needs for sharing information and coordinating operational strategies among multiple projects. A region can be specified at a metropolitan, statewide, multi-State, or corridor level. While “regions” for ITS development may be at any geographic scale, responsibility for planning rests with either the MPO or State planning process. For ITS purposes, a region is any geographic area designated by the planning process. The responsible planning entity (MPO or State) will address the ITS region and ITS planning. Where ITS regions cross planning boundaries, they should be coordinated by the appropriate planning entities (MPOs or States). For ITS Commercial Vehicle Operation projects, the size of the region should not be smaller than a State, with consideration for multi-State, national, and international applications. A regional approach promotes integration of transportation systems. The size of the region should reflect the breadth of the integration of transportation systems and may be at a metropolitan, statewide, multi-State or corridor level. 
                        <PRTPAGE P="33997"/>
                    </P>
                    <HD SOURCE="HD2">II. Project Development </HD>
                    <P>Additionally, the proposed regulations would require that all ITS projects be developed using a system engineering process, again recommending the use of the National ITS Architecture as a resource. Project development would be based on the relevant portions of the ITS integration strategy and the ITS regional architecture which the project implements. ITS projects would be required to use applicable ITS standards that have been officially adopted by the DOT and applicable interoperability tests officially adopted by the DOT. Where multiple standards exist, it will be the responsibility of the stakeholders to determine how best to achieve the interoperability they desire. </P>
                    <HD SOURCE="HD2">III. FHWA Project Oversight Procedures </HD>
                    <P>The FHWA project oversight procedures would remain consistent with routine Federal-aid project oversight. Documentation of the proposed ITS requirements would be required to be included in project documents. Any changes made in project design that impact either the ITS integration strategy or the ITS regional architecture would be documented and the appropriate revisions made and agreed to in the ITS integration strategy and/or the ITS regional architecture. All ITS projects that advance to design or preliminary engineering would be required to conform to the system engineering and conformity requirements immediately upon the effective date of a final rule on the National ITS Architecture and Standards. In the event that an applicable ITS regional architecture or ITS integration strategy does not exist, the applicable portions of the National ITS Architecture would be identified and used as the basis for analysis. All requirements of this proposal would apply for two years from the effective date of a final rule. Replacement of existing systems would not be required. </P>
                    <HD SOURCE="HD2">IV. Outreach Process </HD>
                    <P>In the spring of 1998, the FHWA held ten nationwide outreach meetings on a proposed conceptual approach for ensuring consistency with the National ITS Architecture. These meetings were intended to generate discussion and solicit input from the perspective of many different transportation stakeholders on the feasibility of the proposed FHWA approach. Meetings were attended by representatives of Federal, State, local and regional transportation agencies, public sector agencies that rely on Federal-aid funds for projects with ITS components, and interested parties from universities and the private sector. In general, stakeholders expressed the opinion that the interim guidance and the use of system engineering principles represent good practice. Stakeholders expressed a requirement for straightforward, unambiguous guidance that could be implemented with a minimum of additional paperwork, and largely agreed that the interim guidance met this requirement. For more information please see “National ITS Architecture Consistency Outreach Meetings: Summary Findings (1998)” which is included as part of this docket. </P>
                    <HD SOURCE="HD1">Rulemaking Analyses and Notices </HD>
                    <P>All comments received before the close of business on the comment closing date shown above will be considered and will be available for examination in the docket at the above address. Comments received after the comment closing date will be filed in the FHWA docket identified above and will be considered to the extent practicable, but the FHWA may issue a final rule at any time after the close of the comment closing period. In addition to late comments, the FHWA will also continue to file in the docket relevant information that becomes available after the comment closing date, and interested persons should continue to examine the docket for new material. </P>
                    <HD SOURCE="HD1">Executive Order 12866 (Regulatory Planning and Review) and DOT Regulatory Policies and Procedures </HD>
                    <P>The FHWA has preliminarily determined that this proposed action is not a significant regulatory action under Executive Order 12866 and within the meaning of the Department of Transportation regulatory policies and procedures. This determination is based upon the regulatory assessment of the proposed rule that indicates that the annual impact of the rule would not exceed $100 million nor would it adversely affect the economy, a sector of the economy, productivity, jobs, the environment, public health, safety, or State, local, or tribal governments. </P>
                    <P>The FHWA has prepared a preliminary regulatory evaluation (PRE) to accompany the NPRM. A copy of the PRE is included in the docket. The FHWA believes that this proposed action would implement the requirements of section 5206(e) of the TEA-21. Although this law requires ITS projects funded through the highway trust fund to conform to the National ITS Architecture, the FHWA would require development of a regional architecture consisting of a concept of operations and a conceptual design, and would require use of the system engineering process, applicable or provisional standards, and protocols, and interoperability tests developed by the DOT. In developing the proposed rule, the FHWA has sought to allow broad discretion to those entities impacted by the rule, in levels of response and approach, that are appropriate to particular plans and projects while conforming to the requirements of TEA-21. The FHWA has considered the costs and benefits of effective implementation of ITS through careful and comprehensive planning. ITS becomes part of the transportation planning process through the locally defined ITS Integration Strategy. This ITS strategy would guide future investment decisions and foster the benefits of integration and interoperability. Developing the strategy as part of the overall transportation planning process would ensure that ITS is given appropriate consideration as a solution for future transportation needs and services. </P>
                    <HD SOURCE="HD1">Costs </HD>
                    <P>The total costs of this NPRM over 10 years is estimated between $38.1 million and $44.4 million (the net present value over 10 years is between $22.3 million and $31.2 million). The annual constant dollar impact is estimated to range between $3.2 million and $4.4 million. These 10-year cost estimates include transportation planning cost increases, to MPOs ranging from $10.8 million to $13.5 million, and to States from $5.2 million to $7.8 million. Estimated costs to implementing agencies for the development of regional architectures range between $15.8 million and $23.2 million. </P>
                    <P>These costs do not include additional implementation costs for individual projects as commenters found the additional cost extremely difficult to estimate. Those who responded suggested that the increased cost of project implementation over current good practice would be minimal. However, because of the limited amount of data available on the additional implementation costs for individual projects, the FHWA is seeking additional data on this issue from commenters to this NPRM. </P>
                    <HD SOURCE="HD1">Benefits </HD>
                    <P>
                        The anticipated non-monetary benefits derived include savings from the avoidance of duplicative development, reduced overall development time, and earlier detection of potential incompatibilities. As with 
                        <PRTPAGE P="33998"/>
                        project implementation impacts, the benefits of the NPRM are very difficult to quantify in monetary terms. It is estimated that the coordination guidance provided through implementation of the NPRM can provide savings of approximately $150,000 to any potential entity seeking to comply with the requirements of section 5206(e) of the TEA-21 as compared with an entity having to undertake compliance individually. The costs may be offset by benefits derived from the reduction of duplicative deployments, reduced overall development time, and earlier detection of potential incompatibilities. 
                    </P>
                    <P>In order to assist the FHWA's analysis of costs and benefits for the final rule stage, the FHWA requests that commenters provide additional information on the following questions: </P>
                    <P>(1) Are there implementation costs to project designers and operators not properly represented in the present data? </P>
                    <P>(2) Are there updating and maintenance costs to any of the impacted entities not properly reflected in the present data? </P>
                    <P>A detailed discussion of how the FHWA prepared its estimates is provided in this NPRM for interested parties that are not able to review the PRE. </P>
                    <HD SOURCE="HD1">Regulatory Flexibility Act </HD>
                    <P>In compliance with the Regulatory Flexibility Act (5 U.S.C. 601-612), the FHWA has evaluated, through the regulatory assessment, the effects of this action on small entities (small businesses, small organizations, and local governments) and determined that this action will not have a significant impact on small entities. Small businesses and small organizations are not subject to this NPRM, which applies to government entities only. The rule accommodates small governmental entities in two significant ways. First, the planning component of the NPRM would apply to MPOs and States. An MPO is the required transportation planning organization for an urbanized area (23 CFR part 1410). An urbanized area, as defined in 23 U.S.C. 101, has a population of 50,000 or more. Therefore small government agencies for areas having populations of less than 50,000 would not be affected. Secondly, the self-scaling aspect of the ITS Architecture NPRM would permit the compliance requirements to vary with the magnitude of the ITS requirements of the entity (small ITS projects have correspondingly small compliance documentation requirements). Small entities, primarily transit agencies, coming within the project implementation component of the proposed rule would be accommodated through this self-scaling feature that imposes only limited requirements on small ITS activities. This same feature would also provide accommodation to MPOs that, while larger than the small entity definition of the Regulatory Flexibility Act, have only small ITS planning requirements. Accordingly, the FHWA preliminarily certifies that this proposed action would not have a significant impact on a substantial number of small entities. A copy of the analysis on the small entity impact is provided in the docket file. </P>
                    <HD SOURCE="HD1">Unfunded Mandates Reform Act of 1995 </HD>
                    <P>
                        This rule would not impose a Federal mandate resulting in the expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more in any one year. (2 U.S.C. 1531 
                        <E T="03">et seq.</E>
                        ). 
                    </P>
                    <HD SOURCE="HD1">Executive Order 13132 (Federalism) </HD>
                    <P>This action has been analyzed in accordance with the principles and criteria contained in Executive Order 13132, dated August 4, 1999, and it has been determined that this action does not have a substantial direct effect or sufficient federalism implications on States that would limit the policymaking discretion of the States. Nothing in this document directly preempts any State law or regulation. </P>
                    <HD SOURCE="HD1">Executive Order 12372 (Intergovernmental Review) </HD>
                    <P>Catalog of Federal Domestic Assistance Program Number 20.205, Highway planning and construction. The regulations implementing Executive Order 12372 regarding intergovernmental consultation on Federal programs and activities apply to this program. </P>
                    <HD SOURCE="HD1">Executive Order 12988 (Civil Justice Reform) </HD>
                    <P>This proposed action would meet 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="HD1">Executive Order 13045 (Protection of Children) </HD>
                    <P>We have analyzed this action under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This proposed rule is not economically significant and does not concern an environmental risk to health or safety that may disproportionately affect children. </P>
                    <HD SOURCE="HD1">Executive Order 12630 (Taking of Private Property) </HD>
                    <P>This proposed rule would not effect 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="HD1">Paperwork Reduction Act </HD>
                    <P>This proposed action does not contain information collection requirements for the purposes of the Paperwork Reduction Act of 1995, 44 U.S.C. 3501-3520. </P>
                    <HD SOURCE="HD1">National Environmental Policy Act </HD>
                    <P>The agency has analyzed this proposed action for the purposes of the National Environmental Policy Act of 1969, as amended (42 U.S.C. 4321), and has preliminarily determined that this proposed action would not have any effect on the quality of the environment. </P>
                    <HD SOURCE="HD1">Regulation Identification Number </HD>
                    <P>A regulation identification number (RIN) is assigned to each regulatory action listed in the Unified Agenda of Federal Regulations. The Regulatory Information Service Center publishes the Unified Agenda in April and October of each year. The RIN contained in the heading of this document can be used to cross reference this proposed action with the Unified Agenda. </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects </HD>
                        <CFR>23 CFR Part 655</CFR>
                        <P>Design standards, Grant programs-transportation, Highways and roads, Incorporation by reference, Signs and symbols, Traffic regulations. </P>
                        <CFR>23 CFR Part 940 </CFR>
                        <P>Design standards, Grant programs-transportation, Highways and roads, Intelligent transportation systems. </P>
                    </LSTSUB>
                    <SIG>
                        <DATED>Issued on: May 18, 2000.</DATED>
                        <NAME>Vincent F. Schimmoller,</NAME>
                        <TITLE>Acting Executive Director, Federal Highway Administration.</TITLE>
                    </SIG>
                    <P>In consideration of the foregoing, the FHWA proposes to amend Chapter I of title 23, Code of Federal Regulations, as set forth below: </P>
                    <PART>
                        <HD SOURCE="HED">PART 655—[AMENDED] </HD>
                        <P>1. Revise the authority citation for part 655 to read as follows: </P>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>23 U.S.C. 101(a), 104, 105, 109, 114, 135, 217, 315, and 402; and 49 CFR 1.48. </P>
                        </AUTH>
                        <SUBPART>
                            <PRTPAGE P="33999"/>
                            <HD SOURCE="HED">Subpart D—[Removed] </HD>
                        </SUBPART>
                        <P>2. Remove subpart D of part 655, consisting of §§ 655.401, 655.403, 655.407, 655.409, 655.411. </P>
                        <P>3. Add a new subchapter K, consisting of part 940, to read as follows: </P>
                        <EXTRACT>
                            <HD SOURCE="HD1">SUBCHAPTER K—INTELLIGENT TRANSPORTATION SYSTEMS</HD>
                        </EXTRACT>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART 940—INTELLIGENT TRANSPORTATION SYSTEM ARCHITECTURE AND STANDARDS </HD>
                        <CONTENTS>
                            <SECHD>Sec. </SECHD>
                            <SECTNO>940.1 </SECTNO>
                            <SUBJECT>Purpose. </SUBJECT>
                            <SECTNO>940.3 </SECTNO>
                            <SUBJECT>Definitions. </SUBJECT>
                            <SECTNO>940.5 </SECTNO>
                            <SUBJECT>Policy. </SUBJECT>
                            <SECTNO>940.7 </SECTNO>
                            <SUBJECT>Applicability. </SUBJECT>
                            <SECTNO>940.9 </SECTNO>
                            <SUBJECT>ITS regional architecture. </SUBJECT>
                            <SECTNO>940.11 </SECTNO>
                            <SUBJECT>Systems engineering analysis. </SUBJECT>
                            <SECTNO>940.13 </SECTNO>
                            <SUBJECT>Project implementation. </SUBJECT>
                            <SECTNO>940.15 </SECTNO>
                            <SUBJECT>Project administration. </SUBJECT>
                        </CONTENTS>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>23 U.S.C. 101, 109, 315, and 508; sec 5206(e), Pub. L. 105-178, 112 Stat. 457 (23 U.S.C. 502 note); and 49 CFR 1.48. </P>
                        </AUTH>
                        <SECTION>
                            <SECTNO>§ 940.1 </SECTNO>
                            <SUBJECT>Purpose. </SUBJECT>
                            <P>The purpose of this regulation is to provide policies and procedures relating to the Federal-aid requirements for intelligent transportation systems (ITS) projects funded through the highway trust fund. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 940.3 </SECTNO>
                            <SUBJECT>Definitions. </SUBJECT>
                            <P>
                                <E T="03">ITS integration strategy</E>
                                 means a systematic plan for coordinating and implementing ITS investments funded with highway trust funds to achieve an integrated regional transportation system. 
                            </P>
                            <P>
                                <E T="03">ITS project</E>
                                 means any project that in whole or in part funds the acquisition of technologies or systems of technologies (
                                <E T="03">e.g.</E>
                                 computer hardware or software, traffic control devices, communications link, fare payment system, automatic vehicle location system, etc.) that provide or contribute to the provision of one or more ITS user services as defined in the National ITS Architecture. 
                            </P>
                            <P>
                                <E T="03">ITS regional architecture</E>
                                 means a regional framework for ensuring institutional agreement and technical integration for the implementation of projects or groups of projects under an ITS integration strategy. 
                            </P>
                            <P>
                                <E T="03">National ITS Architecture</E>
                                 (also “national architecture”) means a common framework for ITS interoperability. The National ITS Architecture comprises the logical architecture and physical architecture which satisfy a defined set of user services. All of these documents are controlled by the FHWA, and are updated on an as-needed basis. New versions of the documents, when they are issued, will be available from the FHWA in hard copy and electronic format on the DOT web site at 
                                <E T="03">http://www.its.dot.gov.</E>
                            </P>
                            <P>
                                <E T="03">Region</E>
                                 is the geographical area that is based on local needs for sharing information and coordinating operational strategies in order to address transportation problems. The size of the region should be chosen to optimize integration of transportation systems by fostering the exchange of information on operating conditions across ITS systems and across a number of agencies and jurisdictions. 
                            </P>
                            <P>
                                <E T="03">Systems engineering</E>
                                 is the process to arrive at a final design of a system which is selected from a number of alternatives that would accomplish the same objectives. As in most disciplines, there are usually a number of technical solutions to a set of requirements. This process considers the total life cycle of the project in the evaluation of alternatives including not only the technical merit of potential solutions, but also the costs and relative value of the alternatives that are responsive to the needs of the customer. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 940.5 </SECTNO>
                            <SUBJECT>Policy. </SUBJECT>
                            <P>The ITS projects shall conform to the National ITS Architecture and standards in accordance with the regulations contained in 23 CFR part 1410. Conformance with the National ITS Architecture is interpreted to mean the use of the National ITS Architecture in developing a local implementation of the National ITS Architecture, referred to as an ITS regional architecture, and the subsequent adherence of all ITS projects to that ITS regional architecture. Development of the ITS regional architecture begins with the transportation planning process and the development of an ITS integration strategy for Statewide and Metropolitan Transportation Planning. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 940.7 </SECTNO>
                            <SUBJECT>Applicability. </SUBJECT>
                            <P>All ITS projects that are funded in whole or in part with the highway trust fund are subject to these provisions. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 940.9 </SECTNO>
                            <SUBJECT>ITS regional architecture. </SUBJECT>
                            <P>(a) An ITS regional architecture shall be developed for implementing the ITS integration strategy as provided in 23 CFR 1410. 214(a)(3) and 1410.322(b)(11) to guide the development of specific projects and programs. The ITS regional architecture shall conform with the applicable ITS integration strategy. The National ITS Architecture shall be used as a resource in the development of the ITS regional architecture. </P>
                            <P>(b) The ITS regional architecture may be developed either as an initial project development effort and updated as projects are initiated, or the ITS regional architecture may be developed incrementally as major ITS investments are initiated and updated with subsequent projects. In either case, provision shall be made to include participation from all agencies with which information-sharing is planned as specified in the ITS integration strategy. </P>
                            <P>(c) The ITS regional architecture shall include, at a minimum, the following: </P>
                            <P>(1) A “concept of operations” that addresses the roles and responsibilities of participating agencies, existing or required agreements for operations, and resources required to support the project, in order to implement the ITS integration strategy; </P>
                            <P>(2) A “conceptual design” sufficient to support subsequent project design regarding the following: </P>
                            <P>(i) System functional requirements; </P>
                            <P>(ii) Interface requirements and information exchanges with planned and existing systems and subsystems (for example, subsystems and architecture flows as defined in the National ITS Architecture); </P>
                            <P>(iii) Identification of key standards supporting regional and national interoperability, including uniformity and compatibility of equipment, practices and procedures to deliver ITS services; and </P>
                            <P>(iv) A prioritization of phases or steps required in implementation. </P>
                            <P>(d) The ITS regional architecture may be developed either as an initial project development effort and updated as projects are initiated, or the ITS regional architecture may be developed incrementally as major ITS investment s are initiated and updated with subsequent projects. If the ITS regional architecture is developed incrementally, the ITS projects meeting the criteria specified in 23 CFR 1410.322(b)(11) shall have an ITS architecture at the project level in order to advance to design or preliminary engineering. The ITS architectures developed for specific individual projects or initiatives that meet these criteria shall be coordinated with each other to form an ITS regional architecture. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 940.11 </SECTNO>
                            <SUBJECT>Systems engineering analysis. </SUBJECT>
                            <P>(a) All ITS projects shall be based on a systems engineering analysis. The National ITS Architecture is a resource that should be used in the development of ITS projects. </P>
                            <P>
                                (b) The analysis should be on a scale commensurate with the project scope. The basic elements of the analysis are as follows: 
                                <PRTPAGE P="34000"/>
                            </P>
                            <P>(1) Identification of applicable parts of the ITS regional architecture or ITS integration strategy; </P>
                            <P>(2) Preliminary analysis, including project objectives, existing systems resources, existing and future personnel and budget resources for operations, management and maintenance of systems; </P>
                            <P>(3) Analysis of alternative system configurations and technology options; </P>
                            <P>(4) Analysis of procurement options; and </P>
                            <P>(5) Identification of applicable standards and testing procedures, particularly those that support national interoperability. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 940.13 </SECTNO>
                            <SUBJECT>Project implementation. </SUBJECT>
                            <P>(a) The project specifications shall ensure that the project accommodates the sharing of electronic information and provides for the functionality and operation (both at the time of project implementation and in the future) between the agencies and jurisdictions as indicated in the ITS integration strategy and/or the ITS regional architecture. </P>
                            <P>(b) All ITS projects funded with highway trust funds shall use applicable ITS standards that have been officially adopted by the United States Department of Transportation (US DOT). </P>
                            <P>(c) The ITS standards that are pertinent to the project should be used as they become available, prior to adoption by the US DOT. </P>
                            <P>(d) All ITS projects funded with highway trust funds shall conduct the applicable interoperability tests that have been officially adopted by the US DOT. </P>
                            <P>(e) Interoperability tests that are pertinent to the project should be used as they become available, prior to adoption by the US DOT. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 940.15 </SECTNO>
                            <SUBJECT>Project administration. </SUBJECT>
                            <P>(a) Prior to authorization of highway trust funds for construction or implementation, there shall be a demonstrated linkage to the ITS regional architecture or to the ITS integration strategy, and a commitment to the operations, management and maintenance of the overall system. </P>
                            <P>(b) Documentation of compliance with the provisions of §§ 940.11 and 940.13 shall be developed by project sponsors. The documentation shall include identification of the portions of the ITS regional architecture and/or ITS integration strategy which are implemented through the project, and the identification of applicable ITS standards and/or interoperability tests that were considered or are specified in the project. Documentation of the rationale and interagency coordination strategies that were carried out to agree upon certain changes shall be provided in the event that any changes are made in the implementation of projects contrary to the ITS regional architecture and/or the ITS integration strategy. In addition, the ITS regional architecture and/or ITS integration strategy shall be updated to reflect the changes. </P>
                            <P>(c) ITS projects shall be monitored for compliance with this part under normal Federal-aid project oversight procedures. </P>
                            <P>
                                (d) Prior to (
                                <E T="03">two years after date of final rule publication in the</E>
                                  
                                <E T="0084">Federal Register</E>
                                ), the ITS architectures are not required for projects that meet any of the criteria as specified in 23 CFR 1410.322(b)(11). The criteria identify major regional ITS initiatives, ITS projects that affect regional integration of ITS systems, and projects which directly support national interoperability. 
                            </P>
                            <P>(e) In order to ensure that each project identified in 23 CFR 1410.322(b)(11) is coordinated with the evolving regional architecture provided in § 940.9(b), these projects shall be evaluated for institutional and technical integration with transportation systems and services within the region. Based upon this evaluation of the project(s), highway trust fund recipients shall immediately take the appropriate actions to ensure that the project(s) perform the following functions: </P>
                            <P>(1) Engages a wide range of stakeholders; </P>
                            <P>(2) Enables the appropriate electronic information sharing between stakeholders; </P>
                            <P>(3) Facilitates future ITS expansion; and </P>
                            <P>(4) Uses the applicable ITS standards provided in § 940.13(b). </P>
                            <P>
                                (f) All ITS projects that advance to design or preliminary engineering must conform with the system engineering and conformity requirements provided in §§ 940.11 on or before (
                                <E T="03">Insert effective date of final rule</E>
                                ). In the event that an applicable ITS regional architecture or ITS integration strategy does not exist, the applicable portions of the National ITS Architecture shall be identified and used as the basis for analysis. 
                            </P>
                        </SECTION>
                    </PART>
                </SUPLINF>
                <FRDOC>[FR Doc. 00-13023 Filed 5-19-00; 1:15 pm] </FRDOC>
                <BILCOD>BILLING CODE 4910-22-P </BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>65</VOL>
    <NO>102</NO>
    <DATE>Thursday, May 25, 2000</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="34001"/>
            <PARTNO>Part VI</PARTNO>
            <AGENCY TYPE="P">Department of Transportation</AGENCY>
            <SUBAGY>Federal Transit Administration</SUBAGY>
            <HRULE/>
            <TITLE>Request for Comment on the Federal Transit Administration National ITS Architecture Consistency Policy for Project Development; Notice</TITLE>
        </PTITLE>
        <NOTICES>
            <NOTICE>
                <PREAMB>
                    <PRTPAGE P="34002"/>
                    <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                    <SUBAGY>Federal Transit Administration </SUBAGY>
                    <DEPDOC>[FTA Docket No. FTA-99-6417] </DEPDOC>
                    <SUBJECT>Request for Comment on the Federal Transit Administration National ITS Architecture Consistency Policy for Project Development </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P> Federal Transit Administration (FTA), DOT. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            The Federal Transit Administration (FTA) announces a Request for Comment on the proposed FTA National ITS Architecture Consistency Policy for project development, which is defined in this document and in the Statewide Transportation Planning; Metropolitan Transportation Planning Notice of Proposed Rulemaking (NPRM published separately in today's 
                            <E T="04">Federal Register</E>
                            ). The Metropolitan and Statewide Planning Process, as it relates to ITS projects, is summarized in this notice for clarity. However, comments on the planning process should be directed to Docket No. FHWA-99-5933, docket for the NPRM. Comments on the project development policy, including answers to the questions asked in Section X, should be submitted to this docket. The Major Capital Investments rule, when made final, will also reference the National ITS Architecture Policy. The National ITS Architecture Policy statement is a product of statutory changes made by the Transportation Equity Act for the 21st Century (TEA-21) (P.L. 105-178) enacted on June 9, 1998. This notice proposes to require development of an ITS regional architecture, consisting of a concept of operations and a conceptual design, which draws from the National ITS Architecture but is tailored to address the local situation and ITS investment needs. This notice also proposes to require use of applicable standards and interoperability tests adopted by the United States Department of Transportation (US DOT). The proposal recommends the use of the National ITS Architecture and provisional standards and interoperability tests. 
                        </P>
                    </SUM>
                    <DATES>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Comments shall be submitted by August 23, 2000. </P>
                    </DATES>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>All signed, written comments must refer to the docket number appearing at the top of this document and must be submitted to the Docket Clerk, U.S. DOT Dockets, Room PL-401, 400 Seventh Street, SW, Washington, DC 20590-0001. All comments received will be available for examination at the above address between 9 a.m. and 5 p.m., e.t., Monday through Friday, except Federal holidays. Those desiring notification of receipt of comments must include a self-addressed, stamped envelope or postcard. </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            For Technical Information: Ron Boenau, Chief, Advanced Public Transportation Systems Division (TRI-11), at (202) 366-0195 or Brian Cronin, Advanced Public Transportation Systems Division (TRI-11), at (202) 366-8841. 
                            <E T="03">For Legal Information:</E>
                             Linda Sorkin, Office of the Chief Council (202) 366-1936. The FTA is located at 400 Seventh Street, SW, Washington, DC 20590. This notice is posted on the FTA website on the Internet under http://www.fta.dot/gov. 
                        </P>
                        <HD SOURCE="HD1">Electronic Access</HD>
                        <P>
                            Internet users may access all comments received by the U.S. DOT Dockets, Room PL-401, by using the universal resource locator (URL):  ­
                            <E T="03">http://dms.dot.gov.</E>
                             It is available 24 hours each day, 365 days each year. Please follow the instructions online for more information and help. 
                        </P>
                        <P>
                            An electronic copy of this document may be downloaded using a computer, modem and suitable communications software from the Government Printing Office's Electronic Bulletin Board Service at (202) 512-1661. Internet users may reach the Office of the Federal Register's home page at: 
                            <E T="03">http://www.nara.gov/fedreg</E>
                             and the Government Printing Office's web page at: 
                            <E T="03">http://www.access.gpo.gov/nara.</E>
                        </P>
                        <EXTRACT>
                            <HD SOURCE="HD1">Contents</HD>
                            <FP SOURCE="FP-2">I. Definitions </FP>
                            <FP SOURCE="FP-2">II. Background </FP>
                            <FP SOURCE="FP-2">III. Statewide and Metropolitan Planning Processes </FP>
                            <FP SOURCE="FP-2">IV. ITS Regional Architecture </FP>
                            <FP SOURCE="FP-2">V. ITS Projects </FP>
                            <FP SOURCE="FP-2">VI. Documentation </FP>
                            <FP SOURCE="FP-2">VII. Phasing </FP>
                            <FP SOURCE="FP-2">VIII. Oversight</FP>
                            <FP SOURCE="FP-2">IX. FTA Guidance </FP>
                            <FP SOURCE="FP-2">X. Questions</FP>
                        </EXTRACT>
                        <HD SOURCE="HD1">I. Definitions</HD>
                        <P>
                            <E T="03">Intelligent Transportation Systems (ITS)</E>
                            , as defined in TEA-21, means electronics, communications, or information processing used singly or in combination to improve the efficiency or safety of a surface transportation system. 
                        </P>
                        <P>
                            <E T="03">ITS Integration Strategy</E>
                             means a systematic plan for coordinating and implementing ITS investments funded with highway trust funds to achieve an integrated regional transportation system. 
                        </P>
                        <P>
                            <E T="03">ITS project</E>
                             means any project that, in whole or in part, funds the acquisition of technologies or systems of technologies (e.g. computer hardware or software, traffic control devices, communications links, electronic fare payment system, passenger information system, and automatic vehicle location system) that provide or contribute to the provision of one or more ITS user services as defined in the ITS National ITS Architecture. 
                        </P>
                        <P>
                            <E T="03">ITS Regional Architecture</E>
                             means a regional framework for ensuring institutional agreement and technical integration of technologies for the implementation of projects or groups of projects under an ITS Integration Strategy. 
                        </P>
                        <P>
                            <E T="03">National ITS Architecture</E>
                             (also “national architecture”) means a common framework for ITS integration and interoperability. The National ITS Architecture comprises the logical architecture and physical architecture that satisfy a defined set of user services. The logical architecture defines the functions and information flows, and guides the development of functional requirements for new systems and improvements. The physical architecture defines how the system should provide the required functionality defined in the logical architecture. 
                        </P>
                        <P>
                            A 
                            <E T="03">region</E>
                             is a geographical area that is based on local needs for sharing information and coordinating operational strategies in order to address transportation problems. The size of the region should be chosen to optimize integration of transportation systems by fostering the exchange of information on operating conditions across ITS systems and across a number of agencies and jurisdictions. 
                        </P>
                        <HD SOURCE="HD1">II. Background</HD>
                        <P>Section 5206(e) of TEA-21 requires that the Secretary of the DOT must</P>
                        <EXTRACT>
                            <P>“Ensure that intelligent transportation system projects carried out using funds made available from the Highway Trust Fund, * * * conform to the national architecture, applicable standards or provisional standards, and protocols developed under subsection(a).”</P>
                        </EXTRACT>
                        <P>On October 2, 1998, the DOT issued Interim Guidance on Conformity with the National ITS Architecture and Standards. The Interim Guidance reflects input received from Federal, State, local, and private sector transportation stakeholders in conjunction with the national transportation association forums and 10 outreach sessions held across the Nation in the spring of 1998. The intent of the Interim Guidance is to:</P>
                        <EXTRACT>
                            <PRTPAGE P="34003"/>
                            <P>• Foster integration. </P>
                            <P>• Encourage the incorporation of ITS into the transportation planning process, and </P>
                            <P>• Focus on near-term ITS projects with the greatest potential for affecting regional integration.</P>
                        </EXTRACT>
                        <P>
                            The Interim Guidance is available on the DOT website at 
                            <E T="03">www.its.dot.gov,</E>
                             and will remain in effect until the adoption of a final policy. The National ITS Architecture Policy presented in this proposal reflects comments from the transportation industry on the Interim Guidance. 
                        </P>
                        <P>The objectives for the FTA's National ITS Architecture Policy for project development are to: </P>
                        <EXTRACT>
                            <P>• Provide requirements for ITS project development for projects implemented wholly or partially with highway trust funds. </P>
                            <P>
                                • Achieve system integration (
                                <E T="03">e.g.</E>
                                 seamless traveler information system that electronically combines traveler information data from multiple transportation agencies in a region) for projects funded through the highway trust fund with all other projects contained in the ITS Integration Strategy. 
                            </P>
                            <P>• Engage stakeholders (state DOT's, transit agencies, public safety agencies, other transportation operating agencies). </P>
                            <P>• Enable electronic information and data sharing among stakeholders. </P>
                            <P>• Facilitate future expansion capability of the transportation infrastructure. </P>
                            <P>• Foster interoperability. </P>
                            <P>• Save design time through use of the National ITS Architecture.</P>
                        </EXTRACT>
                        <P>FTA has developed this proposed policy to meet the TEA-21 requirement contained in Section 5206(e) and the DOT/FTA goal to encourage effective deployment of ITS projects. Additionally, DOT and FTA encourage the coordination of local ITS strategies and projects to help meet national and local goals for mobility, accessibility, safety, security, economic growth and trade, and environment. </P>
                        <P>
                            The National ITS Architecture documents were developed by the US DOT, and are updated on an as-needed basis. The latest addition to the National ITS Architecture is the Archive Data User Service, which provides the ability to store and process data over an extended period of time. FTA is pursuing the addition of a Rail ITS user service within the National ITS Architecture. New versions of the documents, when they are issued, will be available from the US DOT in hard copy and electronic format on the DOT website at 
                            <E T="03">www.its.dot.gov.</E>
                             Version 3.0 is the latest version of the National ITS Architecture. 
                        </P>
                        <HD SOURCE="HD1">III. Statewide and Metropolitan Planning Processes </HD>
                        <P>
                            FTA and FHWA have developed an approach for coordinating this policy with requirements for statewide and metropolitan transportation planning processes. The proposed approach, contained in the Statewide Transportation Planning; Metropolitan Transportation Planning NPRM (published elsewhere in today's 
                            <E T="04">Federal Register</E>
                            ), explains how ITS is proposed to be integrated into the planning process. The Metropolitan and Statewide Planning Process, as it relates to ITS projects, is summarized in this section for clarity. However, comments on the planning process should be directed to Docket Number FHWA-99-5933, docket for the NPRM. 
                        </P>
                        <P>The approach in the NPRM includes the provision that states and MPOs are to develop a locally defined ITS Integration Strategy to guide future investment decisions and foster integration and interoperability [See the following sections: §§ 1410.104, 1410.322(b)(11), 1410.214 (a)(3), and 1410.216(c)(8)]. Included in development of the strategy, at a minimum, are highway, transit, and public safety agencies, appropriate federal lands agencies, state motor carrier agencies as appropriate, and other operating agencies necessary to fully address ITS integration. The Integration Strategy shall assess existing and future ITS systems, functions and electronic information sharing expectations. Unique regional ITS initiatives shall be identified in the Integration Strategy. Under the section for planning agreements [See Section 1410.310(i)], the NPRM also calls for an agreement among the MPO, the state DOT, the transit operator, and other agencies identified in the Integration Strategy. This agreement shall address policy and operational issues, including at a minimum ITS project interoperability, utilization of ITS related standards, and the routine operation of the projects identified in the ITS Integration Strategy. </P>
                        <HD SOURCE="HD1">IV. ITS Regional Architecture </HD>
                        <P>The proposed requirements contained in this section have been developed to facilitate the interoperability of projects funded through the highway trust fund (including the mass transit account) with other projects included in the ITS Integration Strategy. FTA proposes the development of an ITS Regional Architecture for implementing the ITS Integration Strategy per 49 CFR 1410.322(b)(11) and 1410. 214(a)(3) to guide the development of specific projects and programs. The FTA proposes to require that the ITS Regional Architecture conform with the applicable ITS Integration Strategy. This proposal suggests that the National ITS Architecture shall be used as a resource in the development of the ITS Regional Architecture. </P>
                        <P>The ITS Regional Architecture may be developed either as an initial project development effort and updated as projects are initiated, or the ITS Regional Architecture may be developed incrementally as major ITS investments are initiated and updated with subsequent projects. </P>
                        <P>Major ITS investments include the following three project categories:</P>
                        <EXTRACT>
                            <P>• Unique regional ITS initiatives (a program of related projects) that are multi-jurisdictional and/or multi-modal, </P>
                            <P>• ITS projects that affect regional integration of ITS systems, and </P>
                            <P>• Projects which directly support national interoperability.</P>
                        </EXTRACT>
                        <P>In either case, it is proposed that provision should be made to include participation from all agencies with which information-sharing is planned as specified in the ITS Integration Strategy. </P>
                        <P>This proposal recommends that the ITS Regional Architecture include, at a minimum and scalable to the size of the region, the following: </P>
                        <P>A. A concept of operations addressing: The roles and responsibilities of participating agencies and existing or required agreements for operations and resources required to support the project; </P>
                        <P>B. A conceptual design sufficient to support subsequent project design regarding system functional requirements; interface requirements and information exchanges with planned and existing systems and subsystems (for example, subsystems and architecture flows as defined in the National ITS Architecture); identification of key standards supporting national interoperability, including uniformity and compatibility of equipment, practices, and procedures to deliver ITS services; and, it must establish a priority of phases or steps required for implementation. </P>
                        <P>ITS projects that are considered to be major ITS investments are proposed to have an ITS project architecture developed that includes a concept of operations and conceptual design as defined above. The ITS project architecture could then serve as the initial ITS Regional Architecture, or if an ITS Regional Architecture exists, could be used to update the existing ITS Regional Architecture. </P>
                        <HD SOURCE="HD1">V. ITS Projects </HD>
                        <P>
                            This proposal recommends that all projects funded through the highway trust fund (including the mass transit account) shall be consistent with the ITS Integration Strategy, the inter-
                            <PRTPAGE P="34004"/>
                            agency agreement, and the ITS Regional Architecture and shall be coordinated with other ITS projects in the state/region. Additionally, it is proposed that the National ITS Architecture shall be used as a resource for interoperability and integration. This proposal recommends that projects financed by FTA are required to be consistent with DOT requirements for standards and interoperability testing as they are officially adopted by DOT. In the interim, grantees should use applicable standards and testing procedures. 
                        </P>
                        <P>As proposed, the project specifications will be required to ensure that the project accommodates the sharing of electronic information and provides for the functionality and operation (both at the time of project implementation and in the future) between the agencies and jurisdictions as indicated in the ITS Integration Strategy and/or the ITS Regional Architecture. </P>
                        <HD SOURCE="HD1">VI. Documentation </HD>
                        <P>This Notice proposes to require documentation of proposed ITS requirements be included in project documents. Documentation will also be required to include identification of the portions of the ITS Regional Architecture and/or ITS Integration Strategy, which are implemented through the project, and the identification of applicable ITS standards and/or interoperability tests that were considered or specified in the project. Any changes made in project design that impact the ITS Integration Strategy or ITS Regional Architecture are proposed to require to be documented. This Notice proposes that documentation of the rationale and interagency coordination strategies that were carried out to agree upon certain changes will be required to be provided in the event that any changes are made in the implementation of projects contrary to the ITS Integration Strategy or ITS Regional Architecture. In addition, this Notice proposes that the ITS Regional Architecture and/or ITS Integration Strategy be required to be updated to reflect the changes. </P>
                        <HD SOURCE="HD1">VII. Phasing </HD>
                        <P>This proposal suggests the phasing to be as follows: </P>
                        <EXTRACT>
                            <P>
                                • Prior to (insert the date two years after date of the final policy publication in the 
                                <E T="04">Federal Register</E>
                                ) the development of an ITS Regional Architecture and subsequent ITS project architectures will not be required for projects that meet the requirements for Major ITS Investments. 
                            </P>
                            <P>• All ITS projects that involve preliminary engineering, including system engineering, and which advance to final design must conform to the requirements for ITS Projects on or before (insert effective date of final policy). </P>
                            <P>• In the event that an applicable ITS Integration Strategy or ITS Regional Architecture does not exist, the applicable portions of the National ITS Architecture will be required to be identified and used as the basis for analysis. </P>
                            <P>• All National ITS Architecture Consistency Policy requirements will be required to apply on (insert date two years after effective date of final policy). </P>
                        </EXTRACT>
                        <HD SOURCE="HD1">VIII. Oversight </HD>
                        <P>This Notice proposes to require grantees to self-certify that they have met the National ITS Architecture consistency requirements. Existing FTA Oversight procedures will be used to verify self-certifications. FTA has allocated FTA Oversight funds from the fiscal year 1999 oversight budget to be used to provide the initial oversight and technical assistance to grantees regarding this policy. </P>
                        <HD SOURCE="HD1">IX. FTA Guidance </HD>
                        <P>FTA will develop appropriate guidance materials regarding the National ITS Architecture consistency requirements upon completion of the Statewide Transportation Planning; Metropolitan Transportation Planning NPRM process and after the comment period regarding this policy. </P>
                        <HD SOURCE="HD1">X. Questions </HD>
                        <P>In order to facilitate focused comments, FTA is asking the following questions regarding the proposed National ITS Architecture Consistency Policy for Project Development. </P>
                        <P>1. Do reviewers understand the definition of a major ITS investment as defined in Section IV, “ITS Regional Architecture,” or is more clarification needed, and if so please explain? </P>
                        <P>2. Do reviewers understand the definition of an ITS project, or is more clarification needed, and if so please explain? </P>
                        <P>3. Do reviewers understand the difference between a major ITS investment, and an ITS project, or is more clarification needed, and if so please explain? </P>
                        <P>4. Are the requirements for development of a Regional Architecture clear? If not, what is not clear about the requirement? </P>
                        <P>5. What additional guidance, if any, is required to explain how to implement this proposed policy? </P>
                        <P>6. The proposed rule allows regions to develop a Regional Architecture as a separate activity, or incrementally as major ITS investments are developed within a region. Do reviewers anticipate particular difficulties with implementing and documenting either approach? </P>
                        <P>7. Do reviewers understand the relationships between the Integration Strategy, the ITS Regional Architecture, and the ITS Project Architecture? </P>
                        <P>8. What additional guidance, if any, is required regarding phasing of this rule? </P>
                        <P>9. Are the oversight and documentation requirements clear? If not, what is not clear about the requirements? </P>
                        <SIG>
                            <DATED>Issued on: May 18, 2000. </DATED>
                            <NAME>Nuria I. Fernandez,</NAME>
                            <TITLE>Acting Administrator.</TITLE>
                        </SIG>
                    </FURINF>
                </PREAMB>
                <FRDOC>[FR Doc. 00-12913 Filed 5-19-00; 1:15 pm] </FRDOC>
                <BILCOD>BILLING CODE 4910-57-P </BILCOD>
            </NOTICE>
        </NOTICES>
    </NEWPART>
    <VOL>65</VOL>
    <NO>102</NO>
    <DATE>Thursday, May 25, 2000</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="34005"/>
            <PARTNO>Part VII</PARTNO>
            <AGENCY TYPE="P">Department of Education</AGENCY>
            <TITLE>William D. Ford Federal Loan Program; Notice</TITLE>
        </PTITLE>
        <NOTICES>
            <NOTICE>
                <PREAMB>
                    <PRTPAGE P="34006"/>
                    <AGENCY TYPE="S">DEPARTMENT OF EDUCATION </AGENCY>
                    <SUBJECT>William D. Ford Federal Direct Loan Program </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Department of Education. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice of the annual updates to the income contingent repayment (ICR) plan formula. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The Secretary announces the annual updates to the ICR Plan formula for 2000. Under the William D. Ford Federal Direct Loan (Direct Loan) Program, borrowers may choose to repay their student loans under the ICR plan, which bases the repayment amount on the borrower's income, family size, loan amount, and interest rate. Each year, the formula for calculating a borrower's payment is adjusted to reflect changes due to inflation. This notice contains the required updates based on inflation, which are examples of how the calculation of the monthly ICR amount is performed, the income percentage factors, the constant multiplier chart, and charts showing sample repayment amounts. These updates are effective from July 1, 2000 to June 30, 2001. </P>
                    </SUM>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Don Watson, U.S. Department of Education, Room 3045, ROB-3, 400 Maryland Avenue, SW., Washington, DC 20202-5400. Telephone: (202) 708-8242. If you use a telecommunications device for the deaf (TDD), you may call the Federal Information Relay Service (FIRS) at 1-800-877-8339. </P>
                        <P>
                            Individuals with disabilities may obtain this document in an alternate format (
                            <E T="03">e.g.,</E>
                             Braille, large print, audiotape or computer diskette) on request to the contact person listed in the preceding paragraph. 
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>Direct Loan Program borrowers may choose to repay their Direct Loans under the ICR Plan. The attachment to this Notice provides updates to four sources of information: examples of how the calculation of the monthly ICR amount is performed, the income percentage factors, the constant multiplier chart, and charts showing sample repayment amounts. </P>
                    <P>We have updated the income percentage factors to reflect changes based on inflation. We have revised the income percentage factor table by changing the dollar amounts of the incomes shown by a percentage equal to the estimated percentage change in the Consumer Price Index for all Urban Consumers from December 1999 to December 2000. Further, we provide examples of monthly repayment amount calculations and two charts that show sample repayment amounts for single, and married or head of household borrowers at various income and debt levels based on the updated income percentage factors. </P>
                    <P>The updated income percentage factors, at any given income, may cause a borrower's payments to be slightly lower than they were in prior years. This updated amount more accurately reflects the impact of inflation on a borrower's current ability to repay. </P>
                    <HD SOURCE="HD1">Electronic Access to This Document </HD>
                    <P>
                        You may review this document, as well as all other Department of Education documents published in the 
                        <E T="04">Federal Register</E>
                        , in text or Adobe Portable Document Format (PDF) on the Internet at the following sites: 
                    </P>
                    <FP SOURCE="FP-1">http://ocfo.ed.gov/fedreg.htm </FP>
                    <FP SOURCE="FP-1">http://www.ed.gov/news.html </FP>
                    <FP>To use the PDF, you must have the Adobe Acrobat Reader, which is available free at either of the previous sites. If you have questions about using the PDF, call the U.S. Government Printing Office (GPO), toll free at 1-888-293-6498 or in the Washington DC, area at (202) 512-1530.</FP>
                    <NOTE>
                        <HD SOURCE="HED">Note:</HD>
                        <P>
                            The official version of this document is the document published in the 
                            <E T="04">Federal Register</E>
                            . Free internet access to the official edition of the 
                            <E T="04">Federal Register</E>
                             and the Code of Federal Regulations is available on GPO access at: http://www.access.gpo.gov/nara/index.html
                        </P>
                    </NOTE>
                    <SIG>
                        <FP>(Catalog of Federal Domestic Assistance Number 84.268, William D. Ford Federal Direct Loan Program)</FP>
                        <P>
                            <E T="04">Program Authority:</E>
                             20 U.S.C. 1087 
                            <E T="03">et seq.</E>
                        </P>
                        <DATED>Dated: May 19, 2000. </DATED>
                        <NAME>Greg Woods, </NAME>
                        <TITLE>Chief Operating Officer. </TITLE>
                    </SIG>
                    <HD SOURCE="HD1">Attachment: Examples of the Calculations of Monthly Repayment Amounts</HD>
                    <EXAMPLE>
                        <HD SOURCE="HED">Example 1.</HD>
                        <P>This example assumes you are a single borrower with $15,000 in Direct Loans, the interest rate being charged is 8.25 percent, and you have an adjusted gross income (AGI) of $30,713. </P>
                        <P>
                            <E T="03">Step 1:</E>
                             Determine your annual payments based on what you would pay over 12 years using standard amortization. To do this, multiply your loan balance by the constant multiplier for 8.25 percent interest (0.1315449). The constant multiplier is a factor used to calculate amortized payments at a given interest rate over a fixed period of time. (The 8.25 percent interest rate used in this example is the maximum interest rate charged for all Direct Loans excluding Direct PLUS Loans and may not be your actual interest rate. You can view the constant multiplier chart below to determine the constant multiplier that you should use for the interest rate on your loan. If your exact interest rate is not listed, use the next highest for estimation purposes.)
                        </P>
                    </EXAMPLE>
                    <FP SOURCE="FP-2">• 0.1315449 × $15,000 = $1,973.17</FP>
                    <P>
                        <E T="03">Step 2:</E>
                         Multiply the result of Step 1 by the income percentage factor shown in the income percentage factor table that corresponds to your income and the divide the result by 100. (If your income is not listed in the income percentage factor table, calculate the applicable income percentage factor by following the instructions under “Interpolation” below.):
                    </P>
                    <FP SOURCE="FP-2">• 88.77 × $1,973.17 ÷ 100 = $1,751.58</FP>
                    <P>
                        <E T="03">Step 3:</E>
                         Determine 20 percent of your discretionary income. Because you are a single borrower, subtract the poverty level for a family of one, as published in the 
                        <E T="04">Federal Register</E>
                         on February 15, 2000 (65 FR 7555), from your income and multiply the result by 20%:
                    </P>
                    <FP SOURCE="FP-2">• $30,713 − $8,350 = $22,363 </FP>
                    <FP SOURCE="FP-2">• $22,363 × 0.20 = $4,472.60</FP>
                    <P>
                        <E T="03">Step 4:</E>
                         Compare the amount from Step 2 with the amount from Step 3. The lower of the two will be your annual payment amount. In this example, you will be paying the amount calculated under Step 2. To determine your monthly repayment amount, divide the annual amount by 12.
                    </P>
                    <FP SOURCE="FP-2">• $1,751.58 ÷ 12 = $145.97</FP>
                    <EXAMPLE>
                        <HD SOURCE="HED">Example 2.</HD>
                        <P>In this example, you are married. You and your spouse have a combined AGI of $58,040 and are repaying your loans jointly under the ICR plan. You have no children. You have a Direct Loan balance of $10,000, and your spouse has a Direct Loan balance of $15,000. Your interest rate is 8.25 percent. </P>
                        <P>
                            <E T="03">Step 1:</E>
                             Add your and your spouse's Direct Loan balances together to determine your aggregate loan balance: 
                        </P>
                        <FP SOURCE="FP-2">• $10,000 + $15,000 = $25,000</FP>
                    </EXAMPLE>
                    <P>
                        <E T="03">Step 2:</E>
                         Determine the annual payment based on what you would pay over 12 years using standard amortization. To do this, multiply your aggregate loan balance by the constant multiplier for 8.25 percent interest (0.1315449). (The 8.25 percent interest rate used in this example is the maximum interest rate charged for all Direct Loans excluding Direct PLUS Loans and may not be your actual interest rate. You can view the constant multiplier chart below to determine the constant multiplier that you should use for the interest rate on your loan. If your exact interest rate is not listed, use the next highest for estimation purposes.)
                    </P>
                    <FP SOURCE="FP-2">• 0.1315449 x $25,000 = $3,288.62 </FP>
                    <P>
                        <E T="03">Step 3:</E>
                         Multiply the result by the income percentage factor shown in the income percentage factor table that corresponds to your and your spouse's income and divide the result by 100. (If your and your spouse's aggregate income is not listed in the income percentage factor table, calculate the applicable income percentage factor by following the instructions under “Interpolation” below.): 
                    </P>
                    <FP SOURCE="FP-2">• 109.40 x $3,288.62 ÷ 100 = $3,597.75 </FP>
                    <P>
                        <E T="03">Step 4:</E>
                         Determine 20 percent of your aggregate income. To do this, subtract the poverty level for a family of 2, as published in the 
                        <E T="04">Federal Register</E>
                         on February 15, 2000 (65 FR 7555), from your aggregate income and multiply the result by 20 percent:
                    </P>
                    <FP SOURCE="FP-2">• $58,040 − $11,250 = $46,790 </FP>
                    <FP SOURCE="FP-2">• $46,790 x 0.20 = $9,358</FP>
                    <PRTPAGE P="34007"/>
                    <P>
                        <E T="03">Step 5:</E>
                         Compare the amount from Step 3 with the amount from Step 4. The lower of the two will be your annual payment amount. You and your spouse will pay the amount calculated under Step 3. To determine your monthly repayment amount, divide the annual amount by 12.
                    </P>
                    <FP SOURCE="FP-2">• $3,597.75 ÷ 12 = $299.81</FP>
                    <P>
                        <E T="03">Interpolation:</E>
                         If your income does not appear on the income percentage factor table, you will have to calculate the income percentage factor through interpolation. For example, assume you are single and your income is $25,000. 
                    </P>
                    <P>
                        <E T="03">Step 1:</E>
                         Find the closest income listed that is less than your income of $25,000 and the closest income listed that is greater than your income of $25,000. 
                    </P>
                    <P>
                        <E T="03">Step 2:</E>
                         Subtract the lower amount from the higher amount (for this discussion, we will call the result the “income interval”):
                    </P>
                    <FP SOURCE="FP-2">• $30,713 − $24,452 = $6,261</FP>
                    <P>
                        <E T="03">Step 3:</E>
                         Determine the difference between the two income percentage factors that are given for these incomes (for this discussion, we will call the result, the “income percentage factor interval”):
                    </P>
                    <FP SOURCE="FP-2">• 88.77% − 80.33% = 8.44%</FP>
                    <P>
                        <E T="03">Step 4:</E>
                         Subtract from your income the closest income shown on the chart that is less than your income of $25,000:
                    </P>
                    <FP SOURCE="FP-2">• $25,000 − $24,452 = $548 </FP>
                    <P>
                        <E T="03">Step 5:</E>
                         Divide the result by the income interval determined in Step 2:
                    </P>
                    <FP SOURCE="FP-2">• $548 ÷ $6,261 = 0.08753</FP>
                    <P>
                        <E T="03">Step 6:</E>
                         Multiply the result by the income percentage factor interval:
                    </P>
                    <FP SOURCE="FP-2">• 0.08753 x 8.44% = .73875%</FP>
                    <P>
                        <E T="03">Step 7:</E>
                         Add the result to the lower of the two income percentage factors used in Step 3 to calculate the income percentage factor interval for $25,000 in income:
                    </P>
                    <FP SOURCE="FP-2">• .73878% + 80.33% = 81.07% (rounded to the nearest hundredth) </FP>
                    <P>The result is the income percentage factor that will be used to calculate the monthly repayment amount under the ICR Plan. </P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s25,7p,r25,7">
                        <TTITLE>
                            <E T="04">Income Percentage Factors</E>
                        </TTITLE>
                        <TDESC>[Based on annual income] </TDESC>
                        <BOXHD>
                            <CHED H="1">
                                Single
                                <LI> </LI>
                            </CHED>
                            <CHED H="2">Income </CHED>
                            <CHED H="2">Percent factor </CHED>
                            <CHED H="1">Married/head of household </CHED>
                            <CHED H="2">Income </CHED>
                            <CHED H="2">Percent factor </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">8,028</ENT>
                            <ENT>55.00</ENT>
                            <ENT>8,028 </ENT>
                            <ENT>50.52 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11,047</ENT>
                            <ENT>57.79</ENT>
                            <ENT>12,669</ENT>
                            <ENT>56.68 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">14,215</ENT>
                            <ENT>60.57</ENT>
                            <ENT>15,098</ENT>
                            <ENT>59.56 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">17,455</ENT>
                            <ENT>66.23</ENT>
                            <ENT>19,738</ENT>
                            <ENT>67.79 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">20,550</ENT>
                            <ENT>71.89</ENT>
                            <ENT>24,452</ENT>
                            <ENT>75.22 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">24,452</ENT>
                            <ENT>80.33</ENT>
                            <ENT>30,713</ENT>
                            <ENT>87.61 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30,713</ENT>
                            <ENT>88.77</ENT>
                            <ENT>38,518</ENT>
                            <ENT>100.00 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">38,520</ENT>
                            <ENT>100.00</ENT>
                            <ENT>46,327</ENT>
                            <ENT>100.00 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">46,327</ENT>
                            <ENT>100.00</ENT>
                            <ENT>58,040</ENT>
                            <ENT>109.40 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">55,679</ENT>
                            <ENT>111.80</ENT>
                            <ENT>77,555</ENT>
                            <ENT>125.00 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">71,295</ENT>
                            <ENT>123.50</ENT>
                            <ENT>104,879</ENT>
                            <ENT>140.60 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">100,977</ENT>
                            <ENT>141.20</ENT>
                            <ENT>146,678</ENT>
                            <ENT>150.00 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">115,780</ENT>
                            <ENT>150.00</ENT>
                            <ENT>239,683</ENT>
                            <ENT>200.00 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">206,224 </ENT>
                            <ENT>200.00 </ENT>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s50,10">
                        <TTITLE>
                            <E T="04">Constant Multiplier Chart for 12-Year Amortization</E>
                        </TTITLE>
                        <BOXHD>
                            <CHED H="1">
                                Interest rate 
                                <LI>(percent) </LI>
                            </CHED>
                            <CHED H="1">Annual constant multiplier </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">7.00</ENT>
                            <ENT>0.1234057 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7.25</ENT>
                            <ENT>0.1250107 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7.46</ENT>
                            <ENT>0.1263678 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7.50</ENT>
                            <ENT>0.1266272 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7.75</ENT>
                            <ENT>0.1282550 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8.00</ENT>
                            <ENT>0.1298943 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8.25</ENT>
                            <ENT>0.1315449 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8.38</ENT>
                            <ENT>0.1324076 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8.50</ENT>
                            <ENT>0.1332067 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8.75</ENT>
                            <ENT>0.1348796 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9.00</ENT>
                            <ENT>0.1365637 </ENT>
                        </ROW>
                    </GPOTABLE>
                </SUPLINF>
                <FRDOC>[FR Doc. 00-13101 Filed 5-24-00; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 4000-01-P </BILCOD>
            </NOTICE>
        </NOTICES>
    </NEWPART>
    <VOL>65</VOL>
    <NO>102</NO>
    <DATE>Thursday, May 25, 2000 </DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="34009"/>
            <PARTNO>Part VIII</PARTNO>
            <AGENCY TYPE="P">Environmental Protection Agency</AGENCY>
            <CFR>40 CFR Part 63</CFR>
            <TITLE>National Emission Standards for Hazardous Air Pollutants for Source Categories; Final Rules </TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="34010"/>
                    <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                    <CFR>40 CFR Part 63 </CFR>
                    <DEPDOC>[AD-FRL-6706-1] </DEPDOC>
                    <SUBJECT>National Emission Standards for Hazardous Air Pollutants for Source Categories </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Environmental Protection Agency (EPA). </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Interpretative rule. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>This interpretative rule clarifies the construction by EPA of the applicability of sections 112(g) and 112(j) of the Clean Air Act (CAA), and of the regulations implementing these provisions for stationary combustion turbines in Subpart B—Requirements for Control Technology Determinations for Major Sources in Accordance With Clean Air Act Sections 112(g) and 112(j). </P>
                        <P>Specifically, EPA has determined that case-by-case maximum achievable control technology (MACT) determinations under subpart B must be made for all new or reconstructed major source stationary combustion turbines, regardless of whether they are part of a combined cycle system. Waste heat recovery units, including duct burners, which are part of a combined cycle system are considered to be steam generating units. New or reconstructed waste heat recovery units would not be subject to case-by-case MACT determinations under subpart B if they are electric utility steam generating units. </P>
                        <P>
                            Elsewhere in today's 
                            <E T="04">Federal Register</E>
                            , EPA is withdrawing the interpretative rule as published on April 21, 2000, at 65 FR 21636. This final interpretative rule supersedes the interpretative rule erroneously published at 65 FR 21636. 
                        </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                        <P>June 26, 2000. </P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            For further information, contact Sims Roy, Combustion Group, Emission Standards Division (MD-13), U.S. Environmental Protection Agency, Research Triangle Park, North Carolina 27711, telephone number: (919) 541-5263, facsimile: (919) 541-5450, electronic mail address: 
                            <E T="03">roy.sims@epa.gov.</E>
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P SOURCE="NPAR">
                        <E T="03">Regulated entities.</E>
                         Stationary combustion turbines which meet the criteria for major sources are the regulated entities addressed by this interpretative rule. 
                    </P>
                    <HD SOURCE="HD1">I. Why Is EPA Issuing This Interpretative Rule? </HD>
                    <P>The EPA has decided to issue this interpretative rule to resolve an ambiguity in the construction of the exclusion for electric utility steam generating units set forth in 40 CFR 63.40(c). That provision states, “The requirements of [40 CFR part 63, subpart B] do not apply to electric utility steam generating units unless and until such time as these units are added to the source category list pursuant to section 112(c)(5) of the Act.” This applicability exclusion was intended to limit the need for case-by-case MACT determinations for new or reconstructed sources under CAA section 112(g) and 40 CFR 63.40-63.44, but the same exclusion would also generally apply to case-by-case MACT determinations for new and existing sources pursuant to CAA section 112(j). </P>
                    <P>The term “electric utility steam generating unit” is defined in CAA section 112(a)(8) and at 40 CFR 63.41, as follows: </P>
                    <EXTRACT>
                        <P>The term “electric utility steam generating unit” means any fossil fuel fired combustion unit of more than 25 megawatts that serves a generator that produces electricity for sale. A unit that co-generates steam and electricity and supplies more than one-third of its potential electric output capacity and more than 25 megawatts electric output to any utility power distribution system for sale shall be considered an electric utility steam generating unit. </P>
                    </EXTRACT>
                    <P>The EPA explained its reasoning for the electric utility steam generating unit exclusion in the preamble to the final rule implementing CAA section 112(g) for new and reconstructed major sources (61 FR 68387, December 27, 1996). We noted that CAA section 112(n)(1) required us to perform a study of the hazards to public health associated with hazardous air pollutants (HAP) emissions from electric utility steam generating units. After completing the required study and considering the results, we are authorized to regulate such units under CAA section 112 if we determine such regulation is appropriate and necessary. We have not at this time made a determination whether such regulation is appropriate and necessary, but we are required by court order to make a determination by December 15, 2000. We excluded electric utility steam generating units from case-by-case MACT determinations under section 112(g) because we concluded that such determinations should only be made for sources which would otherwise be subject to section 112 MACT standards. </P>
                    <P>Stationary combustion turbines were included on the list of source categories issued pursuant to CAA section 112(c)(1), and we are, therefore, required to issue a MACT standard applicable to this category pursuant to CAA section 112(d). Proposal of the MACT standard for this source category is anticipated in late 2000, with promulgation in early 2002. </P>
                    <P>
                        Stationary combustion turbines may be used to generate electricity. These stationary combustion turbines are sometimes combined with waste heat recovery units which generate steam by extracting heat from the exhaust gases (
                        <E T="03">i.e.</E>
                        , combined cycle systems). The fact that stationary combustion turbines can be used to generate electricity has created some ambiguity about whether combustion turbines used in this manner are considered electric utilities. 
                    </P>
                    <P>On the one hand, EPA believes that the most reasonable construction of the statutory definition of electric utility steam generating units would not include any stationary combustion turbine, regardless of whether it is used by an electric utility to generate electricity, and regardless of whether it is attached to a waste heat recovery unit which generates steam. Accordingly, we are developing a MACT standard to regulate emissions from all stationary combustion turbines pursuant to CAA section 112(d). </P>
                    <P>On the other hand, we also recognize that the first sentence of the statutory definition creates ambiguity concerning whether an electric utility unit must even generate steam to be included. This ambiguity has been compounded by the language in the preamble to the final section 112(g) rule, which predicates the exclusion for electric utilities based on the study performed pursuant to CAA section 112(n)(1). That study did, in fact, include some very limited consideration of stationary combustion turbines. In light of these ambiguities, different permitting authorities have reached differing conclusions concerning whether a case-by-case MACT determination under section 112(g) is required for new or reconstructed major source stationary combustion turbines. At various times, offices within EPA have also given differing interpretations concerning whether a case-by-case MACT determination is required for such facilities. </P>
                    <P>
                        This interpretative rule is intended to clearly resolve the ambiguity in the construction of 40 CFR 63.40(c) as applied to stationary combustion turbines. This interpretative rule will become legally effective and binding on June 26, 2000. After that date, all EPA offices and permitting authorities must adhere to this interpretative rule. Those EPA offices and permitting authorities who become aware of this interpretative rule, or the construction of the statute set forth herein, prior to the effective 
                        <PRTPAGE P="34011"/>
                        date should adopt this construction to the full extent it is practicable to do so. However, EPA will not seek to revisit the legality of, or to otherwise reconsider, any final actions previously taken in good faith based on a conclusion that stationary combustion turbines used to generate electricity fall within the exclusion. 
                    </P>
                    <HD SOURCE="HD1">II. What Is the Agency's Interpretation? </HD>
                    <P>
                        The EPA construes the term “electric utility steam generating unit,” as defined by CAA section 112(a)(8) and 40 CFR 63.41, to exclude all stationary combustion turbines, regardless of whether or not such turbines are utilized to generate electricity or utilized by an electric utility, and regardless of whether or not such turbines are utilized in conjunction with waste heat recovery units (
                        <E T="03">i.e.</E>
                        , combined cycle systems). Therefore, a case-by-case MACT determination is required for each new or reconstructed stationary combustion turbine which is a major source. 
                    </P>
                    <P>
                        The phrase “steam generating unit” in the term “electric utility steam generating unit” is critical to interpreting which types of combustion units are covered by this definition and which types are not. The definition clearly covers a conventional fossil fuel fired steam generating unit (
                        <E T="03">e.g.</E>
                        , coal-fired boiler) which extracts heat from the combustion of fuel and generates steam for use in a steam turbine, which in turn provides shaft power to spin an electric generator and generate electricity. 
                    </P>
                    <P>However, we do not believe this term was intended to cover a stationary combustion turbine which extracts shaft power from the combustion of fuel and spins an electric generator to generate electricity. Such a combustion turbine does not extract heat to generate steam. In fact, there is no steam generated at all in a combustion turbine. Hence, we conclude that the term “electric utility steam generating unit” does not include any stationary combustion turbine, and that such turbines must be regulated under a section 112(d) MACT standard or a section 112(j) determination. Moreover, a case-by-case MACT determination under section 112(g) is required for any new or reconstructed stationary combustion turbine which is a major source. </P>
                    <P>This reasoning can be further applied to combined cycle systems. For purposes of this discussion, a combined cycle system is a combination of a stationary combustion turbine and a waste heat recovery unit. </P>
                    <P>In a combined cycle system, a combustion turbine extracts shaft power from the combustion of fuel and spins an electric generator to generate electricity. The hot exhaust gases from the combustion turbine are then routed to a separate “waste heat recovery unit.” The waste heat recovery unit extracts heat from the gases and generates steam for use in a steam turbine, which in turn provides shaft power to spin an electric generator and generate electricity. </P>
                    <P>The combustion turbine in a combined cycle system does not generate steam. It is not a “steam generating unit” and, therefore, is not an “electric utility steam generating unit.” </P>
                    <P>However, we also conclude that, because the waste heat recovery unit in a combined cycle system does generate steam, it is a steam generating unit. Whether a waste heat recovery unit in a new or reconstructed combined cycle system is subject to a case-by-case MACT is a moot point in many cases because the waste heat recovery unit is not an emission source. The emissions from the combustion turbine pass through the waste heat recovery unit, but the waste heat recovery unit is not a source of additional emissions. </P>
                    <P>There is another type of combined cycle system, however, in which the waste heat recovery unit does contribute additional emissions. In these types of combined cycle systems, fuel is burned in the duct, through the use of “duct burners,” just before the gases enter the waste heat recovery unit. </P>
                    <P>
                        These duct burners are analogous to the burners in steam generating units (
                        <E T="03">i.e.</E>
                        , boilers). Their only purpose is to burn fuel to generate more heat for extraction by the waste heat recovery unit in order for it to generate more steam. As a result, duct burners (where they are used) are considered part of the waste heat recovery unit in a combined cycle system—just as the burners in a boiler are considered part of the boiler. 
                    </P>
                    <P>Duct burners in combined cycle systems normally burn natural gas. Although it is unlikely that sufficient natural gas would be burned in a duct burner in a combined cycle system to result in emissions that would themselves exceed the major source threshold, a combined cycle system may have aggregate emissions which exceed the major source threshold. Therefore, in each instance where a stationary combustion turbine in a combined cycle system must meet MACT requirements because it is a major source of HAP, an associated duct burner will also be subject to MACT requirements unless it is found to be an electric utility steam generating unit. It is also possible that there could be instances where emissions from a duct burner in a waste heat recovery unit which is not an electric utility steam generating unit could cause the total emissions from a combined cycle system to exceed the major source threshold. </P>
                    <P>If the waste heat recovery unit in a combined cycle system operates with duct burners, and more than one-third of the potential electrical output capacity of the duct burners and more than 25 megawatts of the electrical output provided by the duct burners are provided to any utility power distribution system for sale, then the waste heat recovery unit is an electric utility steam generating unit and is not subject to case-by-case MACT determinations unless and until such units are added to the source category list pursuant to CAA section 112(c)(5). However, if the waste heat recovery unit in a combined cycle system operates with duct burners and less than one-third of the potential electrical output capacity of the duct burners or less than 25 megawatts of the electrical output provided by the duct burners are provided to any utility power distribution system for sale, then the waste heat recovery unit must also meet MACT requirements if the aggregate HAP emissions from the combined cycle system exceed the major source threshold. </P>
                    <HD SOURCE="HD1">III. What Additional Information Is Available? </HD>
                    <P>As mentioned above, EPA is developing MACT standards for stationary combustion turbines. This effort has resulted in collection of information regarding the performance, as well as the costs, associated with the use of various technologies to reduce emissions of HAP from stationary combustion turbines. </P>
                    <P>
                        In conjunction with today's interpretative rule, EPA is making available two memoranda, the first entitled, “Hazardous Air Pollutant (HAP) Emission Control Technology for New Stationary Combustion Turbines,” and the second entitled, “Oxidation Catalyst Costs for New Stationary Combustion Turbines.” These two memoranda compile and summarize information collected by EPA and may be of assistance in making any required case-by-case MACT determinations. These memoranda may be obtained by contacting EPA as shown under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         or downloaded directly by logging on to the following EPA website: http://www.epa.gov/ttn/uatw/combust/turbine/turbpg.html. 
                        <PRTPAGE P="34012"/>
                    </P>
                    <HD SOURCE="HD1">IV. Why Is EPA Withdrawing the Interpretative Rule Published on April 21, 2000? </HD>
                    <P>An error by EPA led to publication of a preliminary draft of the interpretative rule on April 21, 2000 at 65 FR 36321. </P>
                    <HD SOURCE="HD1">V. What Are the Impacts Associated With This Interpretative Rule? </HD>
                    <P>As mentioned above, this interpretative rule simply resolves current ambiguity concerning the applicability of CAA section 112 to new or reconstructed major source stationary combustion turbines. It is not intended to subject these entities to any new or additional regulatory requirements. </P>
                    <HD SOURCE="HD1">VI. What Is the Applicability of Other Review Requirements? </HD>
                    <P>Under Executive Order 12866 (58 FR 51736, October 4, 1993), this interpretative rule is not a “significant regulatory action” and is, therefore, not subject to review by the Office of Management and Budget. </P>
                    <P>
                        Section 553(b)(3)(A) of the Administrative Procedure Act provides that interpretative rules are not subject to notice-and-comment requirements. Interpretative rules which do not involve the internal revenue laws of the United States are not subject to the regulatory flexibility provisions of the Regulatory Flexibility Act (5 U.S.C. 601 
                        <E T="03">et seq.</E>
                        ). Because notice-and-comment requirements do not apply to this interpretative rule, this rule is also not subject to sections 202 and 205 of the Unfunded Mandates Reform Act of 1995 (UMRA) (2 U.S.C. 1532 and 1535). 
                    </P>
                    <P>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 interpretative rule also does not significantly or uniquely affect the communities of tribal governments, as specified by Executive Order 13084 (63 FR 27655, May 10, 1998). This interpretative rule will not have significant direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government, as specified in Executive Order 13132 (64 FR 43255, August 10, 1999). </P>
                    <P>This interpretative rule is also not subject to Executive Order 13045 (62 FR 19885, April 23, 1997) because it is not economically significant. This 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. This interpretative rule also does not involve special consideration of environmental justice related issues as required by Executive Order 12898 (59 FR 7629, February 16, 1994). </P>
                    <P>
                        In issuing this interpretative 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). The EPA has complied with Executive Order 12630 (53 FR 8859, March 15, 1988) by examining the takings implications of the interpretative 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 interpretative rule does not impose an information collection burden under the provisions of the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        ). The EPA's compliance with these statutes and Executive Orders for the underlying rule interpreted herein is discussed in the March 29, 1996 
                        <E T="04">Federal Register</E>
                         document (61 FR 14029). 
                    </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. We have established an effective date of June 26, 2000. The 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 rule is not a “major rule” as defined by 5 U.S.C. 804(2). 
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 40 CFR Part 63 </HD>
                        <P>Environmental protection, Air emissions control, Hazardous air pollutants, Combustion turbines.</P>
                    </LSTSUB>
                    <SIG>
                        <DATED>Dated: May 18, 2000. </DATED>
                        <NAME>Robert Perciasepe, </NAME>
                        <TITLE>Assistant Administrator, Office of Air and Radiation. </TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 00-13196 Filed 5-24-00; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 6560-50-P </BILCOD>
            </RULE>
            <RULE>
                <PREAMB>
                    <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                    <CFR>40 CFR Part 63 </CFR>
                    <DEPDOC>[AD-FRL-6706-2] </DEPDOC>
                    <SUBJECT>National Emission Standards for Hazardous Air Pollutants for Source Categories </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Environmental Protection Agency (EPA). </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Withdrawal of interpretative rule. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            The EPA is withdrawing the interpretative rule published in the 
                            <E T="04">Federal Register</E>
                             on April 21, 2000, at 65 FR 21363. That interpretative rule was intended to clarify the construction by EPA of the applicability of sections 112(g) and 112(j) of the Clean Air Act (CAA) to all stationary combustion turbines and waste heat recovery units in combined cycle systems. 
                        </P>
                        <P>
                            An administrative error led to publication of a preliminary draft of the interpretative rule, rather than the final interpretative rule EPA intended to publish. Concurrent with this withdrawal of the incorrect version of the interpretative rule published on April 21, 2000, EPA is publishing elsewhere in today's 
                            <E T="04">Federal Register</E>
                             a corrected version of the interpretative rule. 
                        </P>
                    </SUM>
                    <DATES>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>On May 25, 2000, EPA hereby withdraws the interpretative rule published at 65 FR 21363. The corrected interpretative rule will become legally effective on June 26, 2000.</P>
                    </DATES>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            For further information, contact Sims Roy, Combustion Group, Emission Standards Division (MD-13), U.S. Environmental Protection Agency, Research Triangle Park, North Carolina 27711, telephone number: (919) 541-5263, facsimile: (919) 541-5450, electronic mail address: 
                            <E T="03">roy.sims@epa.gov.</E>
                        </P>
                        <SIG>
                            <DATED>Dated: May 18, 2000. </DATED>
                            <NAME>Robert Perciasepe, </NAME>
                            <TITLE>Assistant Administrator, Office of Air and Radiation. </TITLE>
                        </SIG>
                    </FURINF>
                </PREAMB>
                <FRDOC>[FR Doc. 00-13197 Filed 5-24-00; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 6560-50-P </BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>65</VOL>
    <NO>102</NO>
    <DATE>Thursday, May 25, 2000 </DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="34013"/>
            <PARTNO>Part IX</PARTNO>
            <AGENCY TYPE="P">Department of Commerce</AGENCY>
            <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
            <HRULE/>
            <CFR>50 CFR Part 216</CFR>
            <TITLE>Taking and Importing Marine Mammals; Taking Marine  Mammals lncidental to Construction and Operation of Offshore Oil and Gas Facilities in the Beaufort Sea; Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="34014"/>
                    <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                    <SUBAGY>National Oceanic and Atmospheric Administration </SUBAGY>
                    <CFR>50 CFR Part 216 </CFR>
                    <DEPDOC>[Docket No. 990901241-0116-02; I.D. 123198B] </DEPDOC>
                    <RIN>RIN 0648-AM09 </RIN>
                    <SUBJECT>Taking and Importing Marine Mammals; Taking Marine Mammals Incidental to Construction and Operation of Offshore Oil and Gas Facilities in the Beaufort Sea </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>NMFS, upon application from BP Exploration (Alaska), 900 East Benson Boulevard, Anchorage, AK 99519 (BPXA) issues regulations to govern the unintentional take of a small number of marine mammals incidental to construction and operation of offshore oil and gas facilities at the Northstar development in the Beaufort Sea in state and Federal waters. Issuance of regulations governing unintentional incidental takes in connection with particular activities is required by the Marine Mammal Protection Act (MMPA) when the Secretary of Commerce (Secretary), after notice and opportunity for comment, finds, as here, that such takes will have a negligible impact on the species and stocks of marine mammals and will not have an unmitigable adverse impact on the availability of them for subsistence uses. These regulations do not authorize BPXA's activity as such authorization is not within the jurisdiction of the Secretary. Rather, these regulations authorize the unintentional incidental take of marine mammals in connection with such activities and prescribe methods of taking and other means of effecting the least practicable adverse impact on the species and its habitat, and on the availability of the species for subsistence uses. </P>
                    </SUM>
                    <DATES>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Effective May 25, 2000, until May 25, 2005. </P>
                    </DATES>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            A copy of the updated application, Technical Monitoring Plan, Biological Opinion, Environmental Assessment (EA), and a list of the references used in this document may be obtained by writing to Donna Wieting, Chief, Marine Mammal Conservation Division, Office of Protected Resources, National Marine Fisheries Service, 1315 East-West Highway, Silver Spring, MD 20910-3226, or by telephoning one of the contacts listed here (see 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                            ). 
                        </P>
                        <P>Comments regarding the burden-hour estimate or any other aspect of the collection of information requirement contained in this rule should be sent to the Chief, and to the Office of Information and Regulatory Affairs, Office of Management and Budget (OMB), Attention: NOAA Desk Officer, Washington, DC 20503. </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Kenneth R. Hollingshead (301) 713-2055, Brad Smith, (907) 271-5006. </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION: </HD>
                    <HD SOURCE="HD1">Background </HD>
                    <P>
                        Section 101(a)(5)(A) of the MMPA (16 U.S.C. 1361 
                        <E T="03">et</E>
                          
                        <E T="03">seq</E>
                        .) directs the Secretary to allow, upon request, the incidental, but not intentional taking 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 regulations are issued. 
                    </P>
                    <P>Permission may be granted for periods of 5 years or less if the Secretary finds that the taking will have a negligible impact on the species or stock(s) of affected marine mammals, will not have an unmitigable adverse impact on the availability of the species or stock(s) for subsistence uses, and if regulations are prescribed setting forth the permissible methods of taking and the requirements pertaining to the monitoring and reporting of such taking. </P>
                    <HD SOURCE="HD1">Summary of Request </HD>
                    <P>On November 30, 1998, NMFS received an application for Letters of Authorization (LOAs) granting an incidental, small take exemption under section 101(a)(5)(A) of the MMPA from BPXA to take marine mammals incidental to construction and operation of offshore oil and gas facilities at the Northstar and Liberty developments in the Beaufort Sea in state and Federal waters. On March 1, 1999 (64 FR 9965), NMFS published an advance notice of proposed rulemaking (ANPR) on BPXA's application and invited interested persons to submit comments, information, and suggestions concerning the application, and the structure and content of regulations if the application is accepted. During the 30-day comment period on that notice, comments were received from the Marine Mammal Commission (MMC), Greenpeace Alaska (Greenpeace), the Alaska Eskimo Whaling Commission (AEWC), the North Slope Borough (NSB), and the Inupiat Community of the Arctic Slope. Those comments were addressed in the preamble to the proposed rule which was published on October 22, 1999 (64 FR 57010). </P>
                    <P>
                        Because of delays in construction during 1999, and in issuing a proposed rule on this matter, on October 1, 1999, BPXA updated their application to NMFS. Among other things, the revised application removed from this rulemaking a request for a take of marine mammals incidental to construction and operation at Liberty. The revised application is available upon request (see 
                        <E T="02">ADDRESSES</E>
                        ). Following is a brief description of the proposed scope of work for the Northstar project. For more detailed descriptions please refer to the BPXA application. 
                    </P>
                    <HD SOURCE="HD1">Description of the Activity </HD>
                    <P>BPXA proposes to produce oil from the Northstar Unit offshore oil development. This development will be the first in the Beaufort Sea that uses a subsea pipeline to transport oil to shore and then into the Trans-Alaska Pipeline System. The Northstar Unit is located on Seal Island between 2 and 8 miles (mi)(3.2 and 12.9 kilometers (km)) offshore from Pt. Storkersen, AK. This unit is adjacent to the Prudhoe Bay industrial complex and is approximately 54 mi (87 km) northeast of Nuiqsut, a Native Alaskan community. </P>
                    <P>Construction began in December 1999 with the construction of ice roads. Both island construction and offshore pipeline installation is scheduled to occur in 2000. Construction activity includes the construction of several ice roads, one from West Dock and Pt. McIntyre to the Northstar gravel mine, one from the Kuparuk River delta mine site to Seal Island, and one along the pipeline route to Seal Island. The gravel-haul road will have a parallel alternate road to transport service equipment, construction materials and alternate gravel hauling when maintenance or repair of the main ice road is required. In addition to these main ice roads it is expected that three to four access roads will be cleared of snow to allow light vehicle traffic between the pipeline construction activities and the gravel-haul ice road. These on-ice access roads will have the snow cleared regularly, with intermittent flooding to maintain safe traffic conditions. </P>
                    <P>
                        It is estimated that during the winter approximately 16,800 large-volume haul trips between the onshore mine site and a reload area in the vicinity of Egg Island, and 28,500 lighter dump truck trips from Egg Island to Seal Island will be necessary to transport construction 
                        <PRTPAGE P="34015"/>
                        gravel to Seal Island. An additional 300 truck trips will be necessary to transport concrete-mat slope protection materials to the island. 
                    </P>
                    <P>Construction of a gravel island work surface for drilling and oil production facilities, and the construction and installation of two 10-inch (0.25-m) pipelines, one to transport crude oil and one for gas for field injection, will take place during the winter and into the open water season of 2000, while the transport and installation of the drill rig and associated equipment will occur during the summer, ending around September 1, 2000. The two pipelines will be buried together in a single trench. During the summer barges are expected to make approximately 90 to 100 round-trips from Prudhoe Bay or Endicott to support construction. </P>
                    <P>The operational phase will begin with drilling as early as the fourth quarter of 2000, and will continue for about 2 years. Power will be supplied by diesel generators. This phase of drilling will temporarily cease in mid-2001 to allow installation and start-up of process facilities. Drilling is expected to resume about November 2001. Drilling will continue until 23 development wells (15 production, 7 gas injection) are drilled. After drilling is completed, only production-related site activities will occur. In order to support operations at Northstar, the proposed operations activity includes the annual construction of an ice road from Pt. McIntyre to the shore crossing of the pipeline and along the pipeline route to Seal Island. Ice roads will be used to resupply needed equipment, parts, foodstuffs, and products, and for hauling wastes back to existing facilities. During the summer, barge trips will be required between West Dock or Endicott and the island for resupply. </P>
                    <P>Year-round helicopter access to Northstar is planned for movement of personnel, foodstuffs and emergency movement of supplies and equipment. Helicopters will fly at an altitude of at least 1,000 ft (305 m), except for takeoffs, landings, and safe-flight operations. </P>
                    <HD SOURCE="HD1">Comments and Responses </HD>
                    <P>On October 22, 1999 (64 FR 57010), NMFS published a notice of proposed rulemaking on BPXA's application and invited interested persons to submit comments, information, and suggestions concerning the application and proposed rule. During the 60-day comment period on that notice, comments were received from BPXA, the MMC, Greenpeace, the NSB, and the AEWC. Their comments are addressed here. </P>
                    <HD SOURCE="HD2">Activity Concerns </HD>
                    <P>
                        <E T="03">Comment 1</E>
                        : The NSB believes that the Northstar Project area analysis should not be limited to the area immediately adjacent to Seal Island and the pipeline corridor, but expanded to also include the proposed sealift route, and any other route to be used by ocean-going vessels in support of the project, aircraft and vessel paths, and any ice-free corridors to be maintained to facilitate oil spill response. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS agrees that a small number of takings by harassment of marine mammals could occur as a result of these activities, which were addressed in BPXA's application. However, it is NMFS policy that, in most cases, small take authorizations are unnecessary solely for transiting vessels, such as those described in BPXA's application and those providing transportation and supplies to NSB communities, unless the vessel activity has some potential to result in a significant biological response in the marine mammal(s) or affects the subsistence needs of Alaskan communities (
                        <E T="03">e.g.,</E>
                         conducting, or in support of seismic, and possibly ice-breaking). In most cases, vessels are presumed not to alter marine mammal behavior sufficient to constitute a taking by harassment. Because barges are expected to travel in inshore waters, where bowheads are less likely to occur, and to travel between Northstar, West Dock, and Barrow and, therefore, have, at most, minimal impact on subsistence whaling by Nuiqsut, and because there is no information that these vessels will have an adverse impact on bowhead whaling at Barrow, NMFS has determined that, based on the record, there will not be an unmitigable adverse impact on bowhead whaling from vessel movement in support of Northstar. If the AEWC determines otherwise, NMFS believes they will make vessel movement a subject of discussion for the Conflict and Avoidance Agreement (C&amp;AA). Under that agreement, BPXA will either agree to cease all vessel traffic between the beginning and end of the fall bowhead subsistence harvest, or limiting vessel traffic during this time period in accordance with the C&amp;AA. 
                    </P>
                    <P>While BPXA would be responsible for maintaining the ice-free channel in order to facilitate oil spill response, the U.S. Army Corps of Engineers (Corps) permit prohibits ice breaking until October 15, meaning that ice-breaking will not occur until after most, if not all of the bowhead migration and subsistence whaling have concluded for the year. Any ice-breaking occurring prior to the end of the bowhead subsistence harvest at Nuiqsut is not considered part of the request by BPXA and, therefore, cannot be authorized for a taking of marine mammals. </P>
                    <P>An estimate of incidental harassments by aircraft is not necessary because helicopters must remain at a minimum altitude of 1,000 ft (305 m), weather permitting (except when landing or taking off). NMFS understands that other permits require helicopters at Northstar to maintain an altitude of 1,500 ft (457 m). At 1,000-ft altitude and higher, takings of marine mammals are unlikely to occur. At altitudes lower than 1,000 ft (305 m), while seals may make minor behavioral changes to the helicopter noise, these changes are unlikely to alter seal behavior sufficient to constitute a take. Further reducing potential impacts, helicopter traffic will be between shore and Northstar and bowhead and beluga whales are normally found in waters north of Northstar, outside the area of helicopter traffic. </P>
                    <P>NMFS recognizes however, that helicopter traffic patterns may change in the future when, and if, additional oil development structures are sited. NMFS intends to review the impacts from structure to structure flights when these activities apply for an initial LOA under these regulations. Applicants are encouraged to address this form of taking on marine mammals, especially bowhead whales and the subsistence hunting of this species, when applying for an LOA. Failure to adequately address this issue may result in a delay in processing applications. </P>
                    <HD SOURCE="HD2">MMPA Concerns </HD>
                    <P>
                        <E T="03">Comment 2</E>
                        : Greenpeace states that the artificial segmentation of industrial activities on the North Slope (
                        <E T="03">e.g.,</E>
                         seismic, oil exploration, oil development) is not permitted under the MMPA. Later Greenpeace notes that the proposed actions artificially segment the environmental review of Northstar and its impacts, thereby violating the National Environmental Policy Act (NEPA) and the Endangered Species Act (ESA). As a result, Greenpeace requests that its March 10, 1999, comments on the Final Environmental Impact Statement (FEIS) for Northstar, be incorporated by reference. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : When Congress implemented the 1981 Amendments to the MMPA, which authorized the Secretary to allow specified activities to obtain an exemption from the MMPA's moratorium on taking without a requirement to waive the moratorium under section 101(a) of the MMPA, it 
                        <PRTPAGE P="34016"/>
                        put certain provisions on when and where the Secretary may grant those exemptions. One requirement was for the activity to be as specific as possible. Congress stated: “It is the intention of the Committee that both the specified activity and the specified region referred to in section 101(a)(5) be narrowly identified so that the anticipated effects will be substantially similar. Thus, for example, it would not be appropriate for the Secretary to specify an activity as broad and diverse as outer continental shelf oil and gas development. Rather, the particular elements of that activity should be separately specified, as, for example, seismic exploration, or core drilling.” (H.R. Rep. No. 97-228 at p. 19, 1981). To the extent practicable, NMFS follows this guidance when promulgating regulations under section 101(a)(5) of the MMPA. As discussed throughout this document, NMFS does not believe that its action is in violation of either NEPA or the ESA. 
                    </P>
                    <P>The Corps' draft environmental impact statement (DEIS), FEIS, and the comments that were submitted to the Corps on those documents are considered to be part of NMFS' Record of Decision on this matter. </P>
                    <P>
                        <E T="03">Comment 3</E>
                        : Greenpeace states that the proposed regulations fail to consider reasonably foreseeable exploration and development activities in the Beaufort Sea on the part of companies other than BPXA. The NSB expressed similar concerns regarding BPXA's application. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS has designed these regulations so that as new oil development units are constructed in the Beaufort Sea, and companies apply for a LOA for the taking of marine mammals, NMFS will need to make a finding that the “total taking by the activity” will have no more than a negligible impact on marine mammals and not have an unmitigable adverse impact on subsistence uses of these mammals. NMFS is not required to make these findings beforehand, when future activities remain speculative and impacts on marine mammals have not been fully assessed under NEPA. 
                    </P>
                    <P>NMFS believes that the Corps' FEIS addresses, to the extent possible, the cumulative impacts of past and future impacts on marine mammals and subsistence whaling (see Chapt. 10 of the FEIS). That document notes that “[T]he potential for future developments to cause or contribute to any deflection of the [bowhead] migration or impact the harvest will depend largely upon the proposed location with respect to the traditional migratory path and traditional harvest areas. Accordingly, proposed future projects will have to be analyzed on a case-by-case basis to determine whether and how they may cause or contribute to any effects on the bowhead migration or subsistence harvest.” </P>
                    <HD SOURCE="HD2">Application Concerns </HD>
                    <P>
                        <E T="03">Comment 4</E>
                        : The NSB encourages NMFS to require BPXA to submit a modified petition which contains the level of detail and an organization which will allow for a meaningful review of the potential impacts of proposed Northstar development. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS does not agree that NMFS should reject BPXA's application. On March 1, 1999, NMFS provided duplicate sets of NMFS' ANPR, including BPXA's application, on this action to the NSB. ANPRs are provided in order for the public to provide comments on the adequacy of an applicant's application for an incidental take and on the applicant's activity. The NSB did not provide NMFS with comments during that 30-day public comment period. In addition, as discussed within this document, NMFS believes the NSB does not provide sufficient justification for NMFS to determine that the application did not meet the requirements in § 216.104. 
                    </P>
                    <P>
                        <E T="03">Comment 5</E>
                        : The NSB notes that the application has more the appearance of a summary document than a completed document and is lacking in sufficient detail to allow for a meaningful assessment of whether the proposed activities meet the standards that will permit NMFS to issue the requested LOA. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : The MMPA requires NMFS to make its findings based on the best scientific evidence available that the total taking by the specified activity during the specified time period will have a negligible impact on species or stock of marine mammal(s) and will not have an unmitigable adverse impact on the availability of those species or stocks intended for subsistence purposes. NMFS is not restricted to the information provided by an applicant when making its findings, recognizing that some biases may be provided in an application. In those cases where the applicant provides the majority of the information for NMFS' findings, and supplementary documentation (
                        <E T="03">e.g.,</E>
                         a DEIS or FEIS) is lacking, NMFS holds applicants to a higher standard for determining what is an acceptable application. However, in those cases where supplementary information is available, especially when that information is provided independent of the applicant, NMFS believes that an application need not provide extensive detail that can easily be found elsewhere. In this case, the supplementary information was provided by the Corps in its DEIS and FEIS on this action. The difficulty for the applicant in this action was that it did not have access to the material and analyses provided in the DEIS prior to its release. In addition, as is their right, BPXA is not required to totally agree with the findings in the DEIS/FEIS. As a result, there may be certain distinctions between information contained in the application and that in the DEIS/FEIS. It is the responsibility of NMFS to determine which document, if either, is correct. 
                    </P>
                    <HD SOURCE="HD2">Proposed Rule Concerns </HD>
                    <P>
                        <E T="03">Comment 6</E>
                        : BPXA believes the proposed regulations are confusing regarding which portions of the rule address applications or petitions for rulemaking and which portions of the rule address applications for LOAs. BPXA recommends using specific terms consistently to contrast the two steps required to authorize the activity. BPXA suggests utilizing a petition for regulations, and a request for an LOA. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : These regulations do not distinguish between applications for LOAs and petitions for rulemaking. While an application for an LOA requires rulemaking, it is a single-step process under these regulations. NMFS believes the commenter has confused these regulations with those in subpart I, which distinguishes between petitions for regulations, applications for LOAs and applications for Incidental Harassment Authorizations (IHAs). Because subpart I is not being amended at this time, BPXA's recommendation cannot be accepted. It should be understood however, that NMFS does not intend to require a dual process for issuing future initial LOAs, that is, rulemaking followed by review of an application for an LOA. NMFS intends the two processes to proceed at the same time. 
                    </P>
                    <P>
                        <E T="03">Comment 7</E>
                        : BPXA presumes that the term “platform” in the rulemaking title includes drilling islands. The proposed activity does not involve an offshore oil rig platform but rather a permanent man-made gravel island. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : To avoid confusion, NMFS has replaced the term “platforms” with “facilities” to better describe the various types of oil and gas development activities that can obtain a small take authorization under this rulemaking. 
                    </P>
                    <P>
                        <E T="03">Comment 8</E>
                        : BPXA notes that the term “Northstar Oil and Gas Development Unit on Seal Island,” found in § 216.200(a), appears to limit the authorization for taking to the island and not include related activities such 
                        <PRTPAGE P="34017"/>
                        as the pipelines. BPXA recommends dropping the words “Unit on Seal Island” from that paragraph. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS agrees and has made the change. 
                    </P>
                    <P>
                        <E T="03">Comment 9</E>
                        : BPXA pointed out that NMFS regulations at § 216.104(a)(12) regarding a Plan of Cooperation (POC) differ from those in these regulations (§ 216.205). 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : In response to NMFS' proposed regulations (see 60 FR 28379, May 31, 1995) one commenter noted that not all activities required submission of formal POC. As a result, NMFS modified the interim rule (see 61 FR 15884, April 10, 1996) from that originally proposed. However, while in this rulemaking, a POC is viewed as essential, there is no requirement that it be a formal document, separate from the LOA application. 
                    </P>
                    <P>
                        <E T="03">Comment 10</E>
                        : BPXA noted that a POC is different from the C&amp;AA. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS agrees. A POC is a set of information provided to NMFS at the time an applicant requests an LOA for activities in the Arctic. The C&amp;AA is a formal agreement between the activity's participants and the AEWC. NMFS does not play a role in its development or implementation. As a courtesy, NMFS often receives a copy of the C&amp;AA after it is signed. 
                    </P>
                    <P>
                        <E T="03">Comment 11</E>
                        : BPXA recommends that NMFS consider including in the rule a time period by which NMFS must respond to an LOA request with either approval or denial. The applicant should be advised of a decision within a specified time period to avoid ongoing expectations of an LOA being granted or missing an entire season because NMFS approval or denial is not under any time limit. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : While NMFS understands the concern, rulemakings cannot be held to specific timelines which may preclude adequate public review and/or limit the decision-making process. Because rulemakings normally will take 8-12 months for completion, NMFS recommends applicants submit complete applications as close as possible to the time that the principal Federal agency releases its NEPA document for public review and comment. 
                    </P>
                    <P>
                        <E T="03">Comment 12</E>
                        : BPXA notes that it submitted its request for an LOA on November 30, 1998, and that this submission fulfills the requirement under § 216.207(d). 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS concurs. BPXA submitted its application for an LOA under § 216.104 on November 30, 1998, and a 30-day public comment period commenced on March 1, 1999 (64 FR 9965). Based in part on the comments received by NMFS and delays in both BPXA's construction schedule and NMFS' processing the application, BPXA submitted a revised LOA application on October 1, 1999 (received on October 15, 1999). A 60-day comment period on the revised LOA application began on October 22, 1999 (64 FR 57010). Those review periods satisfy the requirement of § 216.207(d). 
                    </P>
                    <HD SOURCE="HD2">LOA Concerns </HD>
                    <P>
                        <E T="03">Comment 13</E>
                        : The AEWC recommends that NMFS provide a minimum of 90 days for public review and comment on any new LOA request for arctic offshore production-related activities. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS believes that a 90-day public comment period is excessive and unnecessary given that new LOAs under these regulations will have several comment periods. First, either the Minerals Management Service or the Corps will provide for review and comment on a document under NEPA, presumably a DEIS, on any oil development in the Beaufort Sea. Such comment periods are a minimum of 45 days, and likely 60 days or longer. Second, NMFS will announce the availability of an application for a small take authorization incidental to the offshore production unit and will offer the public a minimum of 30 days for review of the application. Finally, if NMFS proposes regulations to govern the incidental taking, the public will be offered another comment period of 45-60 days, as was done for the Northstar authorization. Because NMFS' two review periods provide the public with a total of 75 to 90 days, subsequent to, or in conjunction with, the review period for the oil production project itself under NEPA, NMFS does not believe the additional time period is warranted. 
                    </P>
                    <P>It should be recognized however, that NMFS has already published and provided for public comment on BPXA's application for the Liberty oil development project (64 FR 9965, March 1, 1999). Because of a delay in timing for the start of the Liberty project due to NEPA, NMFS expects that BPXA will submit a revised application for Liberty. Because NMFS has already provided public notice on BPXA's application for a small take for the Liberty project, NMFS will not reannounce receipt of the application, but will proceed immediately to the proposed rule stage. As a result, and for this application only, NMFS expects to provide an extended public comment period of 90 days to allow the public adequate time for review both the application and the proposed rule, in lieu of providing another review limited to BPXA's Liberty application. </P>
                    <P>
                        <E T="03">Comment 14</E>
                        : BPXA believes that a public comment period should not be required for renewal of LOAs under § 216.209(a)(2) only during the petition for regulations. If the activity applied for does not fall within the scope of the existing regulations, then the petition process for new or revised regulations should be followed which includes a public comment period. Having concerns about the adequacy of section 101(a)(5)(A) of the MMPA to provide mitigation measures from the potential adverse impact from oil production, the AEWC and the NSB recommend that NMFS issue an LOA that is either only for construction at Northstar, or is limited to only one year, in order to provide an opportunity to discuss mitigation measures and other protections for oil production activities. In addition, the AEWC requests that the public be granted a minimum of 30 days to review a renewal of an LOA. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS has reviewed the LOA reissuance concerns and notes that it has 3 options: (1) Reissue an LOA annually based upon timely receipt of reports without public comment prior to reissuance, (2) reissue an LOA annually based upon timely reports after a public comment period, or (3) issue an LOA for all or a portion of the 5-year period of validity of the regulations. Because under implementing interim regulations (see § 216.106(e)), NMFS would be required to provide a 30-day public comment period (except in cases where there is a significant risk to impacted marine mammals) prior to withdrawal, or even temporary suspension of, an LOA, for failure to meet any of the requirements of the regulations or the LOA, issuing LOAs for periods greater than one year is generally not acceptable to NMFS. Whether an opportunity for public comment is provided depends entirely on whether NMFS determines that all substantive issues have been addressed satisfactorily during rulemaking. If so, then little would be accomplished by annually revisiting these issues. 
                    </P>
                    <P>
                        In this action however, several issues remain unresolved, the principal ones being the implementation of effective marine mammal mitigation and monitoring during oil production, the peer review of monitoring plans, and the submission of annual POCs. Therefore, NMFS has determined that LOA renewals under this rulemaking will have a requirement for a 30-day public review period, at least in the early years of renewal. However, in order to expedite the LOA renewal process, NMFS will open the review 
                        <PRTPAGE P="34018"/>
                        process to the following issues only: (1) New citable scientific data or information (including Traditional Knowledge) that indicates that the determinations made in this document are in need of reconsideration, (2) comments on the POC, and (3) comments on a proposed monitoring plan. NMFS will give full consideration to all comments submitted within the authorized comment period when making its determination on reissuance. In addition, because of the requirement to submit timely reports with an LOA renewal application, it is expected that there will be only a limited amount of time between the date a request for an LOA renewal is submitted, and the date of expiration of the current LOA. As a result, NMFS will act on a request for an LOA renewal in a timely manner, but is unlikely to extend the public comment period beyond 30 days, unless there are compelling circumstances. In addition, these regulations allow NMFS to waive the public comment period once either multi-year mitigation (including POCs) and monitoring plans have been submitted to NMFS and reviewed by the peer review process described in the LOA and NMFS determines that no significant issues remain substantially unresolved. 
                    </P>
                    <P>Since construction work at Northstar will continue through at least November, 2000, issuance of an LOA limited only to construction has been accepted by NMFS. In the meantime, discussion on appropriate mitigation and monitoring during production can continue. However, to ensure that takings resulting from uncompleted construction work late in 2000 or early 2001, if any, are covered, NMFS has made the LOA valid for a full 12 months, but only for construction. </P>
                    <P>
                        <E T="03">Comment 15</E>
                        : BPXA suggests that NMFS clarify that § 216.210(a) is intended to apply to the case of a proposed withdrawal of the LOA by NMFS, not by the applicant. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS agrees and has amended § 216.210(a) as recommended. 
                    </P>
                    <HD SOURCE="HD2">Take Level Concerns </HD>
                    <P>
                        <E T="03">Comment 16</E>
                        : Greenpeace states that NMFS accepts the applicant's assertion, with no scientific or other basis, that the number of takes of whales during operation and during construction of Northstar will be identical. There is no estimate of take or possible jeopardy from a variety of oil spill scenarios * * * and from the resultant cleanup activities. The NSB believes that it is unacceptable for the petition not to provide any estimate of the potential number of individuals of any subject species which could potentially be taken in the event of an oil spill associated with Northstar. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : While not identical, the estimated take levels by incidental harassment are similar. Calculations for incidental take levels by both construction and production are described in detail in the original and revised BPXA applications. NMFS believes that these calculations are based upon the best scientific information available. As a result, NMFS has accepted these take estimates. However, NMFS recognizes that, for reasons explained later in this document, these estimates do not include takes by harassment, injury, or mortality incidental to oil spills. 
                    </P>
                    <P>
                        <E T="03">Comment 17</E>
                        : BPXA noted that the estimated levels of take provided in the preamble to the proposed rule were not updated based upon estimates provided in the September 30, 1999, revised application. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : Unfortunately, updates could not be made to the preamble to the proposed rule because the revised application was not received in time to revise the proposed rulemaking without further delaying the release of the proposed rule. However, NMFS has made the appropriate corrections in this document. 
                    </P>
                    <HD SOURCE="HD2">Negligible Impact Concerns </HD>
                    <P>
                        <E T="03">Comment 18</E>
                        : The MMC notes that (1) the path of the fall bowhead migration varies substantially from year to year; (2) that in most years comparatively few bowhead whales are likely to pass within 10 km (6.2 mi) of the Northstar site; and, (3) that any changes in swimming speed, direction, or other behavior caused by Northstar activities are unlikely to affect the size or productivity of the bowhead population (or of bowheads to Alaska natives for subsistence purposes). Because the available data are insufficient to be confident that both the population level effects (and the impacts on Native subsistence hunting) would be negligible, the MMC believes it would be more appropriate to base the assessment of possible impacts on the worst case scenario, and considering possible cumulative impacts over the full 15-20 years that production is expected at the Northstar site, rather than basing the assessment on the best available estimate of the average take level over the next 5 years. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS does not agree that it should make an assessment of take levels over the 15-20 year lifetime of the Northstar Unit. Under the MMPA, NMFS must make a determination that the “total of such taking during each 5-year (or less) period concerned will have a negligible impact on such species or stock and will not have an unmitigable adverse impact on the availability of such species or stock for taking for subsistence purposes * * *.” 
                    </P>
                    <P>Also, NMFS does not consider it necessary to make a negligible impact determination on the worst case scenario. NMFS believes that using the worst case estimate does not provide a realistic estimate of harassment take levels. NMFS suggests that reviewers note the detailed explanation in the application on how BPXA estimated take levels. The best scientific data indicates that, between 1979 and 1997, a period of 18 years of data collection, bowheads came within 10 km (6.2 mi) of the site of the future Northstar Unit only during 1997 (BPXA, 1999). This being the case, there is simply no need to presume that this migratory deflection would occur during each of the next 5 years. However, NMFS has determined that, because this close-approach did occur in a recent year, a more reliable estimate of take can be made by presuming that this take level could occur again once or twice within the next 5 year period. Therefore, NMFS has determined that an average annual take by harassment, due to noise from construction and operation at Northstar, as calculated by BPXA (i.e., 173 (maximum 1,533) per year) would result in a maximum of 717 bowheads annually or approximately 9 percent of the revised 1993 estimated population size of 8,200 (95 percent CI, 7,200-9,400) (Hill and DeMaster, 1999; IWC, 1996). NMFS notes that this harassment will be limited to a deflection in migration and would be considered a taking by Level B harassment. Such a taking would result in only small numbers being taken and having no more than a negligible impact (both as defined in § 216.103) on bowhead whales. </P>
                    <P>
                        Finally, NMFS disagrees with the MMC that the available data are insufficient to be confident that both the population level effects (and the impacts on Native subsistence hunting) would be negligible. The take levels under discussion here are limited to harassment due to noise disturbance by construction and later production at the Northstar Unit. The level of noise produced at Northstar is expected to be substantially less than that produced during seismic surveys, and, unlike seismic, Northstar is stationary and located well inshore of the normal migratory path of the bowhead whale. In addition, the bowhead whale population has increased from approximately 4,400 (CV 3,500 to 5,300) (Zeh 
                        <E T="03">et</E>
                          
                        <E T="03">al</E>
                        ., 1993) in 1978 to 
                        <PRTPAGE P="34019"/>
                        approximately 8,200 in 1993 (Hill and DeMaster, 1999). A population increase of approximately 3.1 percent annually (Raftery 
                        <E T="03">et</E>
                          
                        <E T="03">al</E>
                        . 1995, NMFS, 1999), coincident with oil exploration and development activity (including seismic), provides evidence that takings due to harassment by noise at Northstar will not have more than a negligible impact on bowhead whales. 
                    </P>
                    <P>However, of more concern to NMFS is the impact, not by Northstar alone, but the cumulative impact in the future by several offshore oil developments and seismic activity on the subsistence lifestyle of the North Slope residents. This is discussed in more detail later in this document. </P>
                    <P>
                        <E T="03">Comment 19</E>
                        : Greenpeace notes that NMFS fails (1) to adequately consider the impact if the maximum number of bowhead whale takes (1,533 per year for the 5-year period or a total of 7,665 bowheads actually occurs, and (2) to justify its conclusion that the takings at this level would not be expected every year or would not jeopardize the species. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : Please refer to the response to previous comment. As noted in the application and in the preamble to the proposed rule, the taking of up to 173 (maximum 1,533/year) is limited to harassment, meaning the taking is for the short-term incidental harassment by noise disturbance, resulting in a short-term behavior change, such as a slight deflection of its westward migration route. 
                    </P>
                    <P>While NMFS recognizes that there is some potential that bowheads (and other marine mammal species) may be harassed, injured or killed due to an oil spill from Northstar, NMFS determined previously, under section 7 of the ESA, that oil and gas development at Northstar would not jeopardize the continued existence of the bowhead whale. </P>
                    <P>
                        <E T="03">Comment 20</E>
                        : The NSB questions the citation in BPXA's application (i.e., NMFS, 1997), whether NMFS subscribes to the policy regarding a determination of negligible impact where the impact may be more than negligible, but the likelihood of occurrence is minimal, and whether NMFS will continue this policy in regard to future proposed OCS development projects. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : The reference cited in the BPXA application is NMFS' 
                        <E T="04">Federal Register</E>
                         notice of issuance of an IHA to the ARCO Oil Company for oil exploration in Camden Bay, Alaska (see 62 FR 51637, October 2, 1997). In that document, NMFS stated that when making a negligible impact determination, NMFS can find that a negligible impact determination may be appropriate if the probability of occurrence is low, but the potential effects may be significant. This statement has been made by NMFS previously (see 53 FR 8474, March 15, 1988) and can also be found in NMFS' Programmatic EA (NMFS, 1995) for implementation of regulations found at subpart I of this part. In stating this policy for this and other activities, NMFS is following Congressional direction to balance the potential for a significant impact with the likelihood of that event occurring. The specific Congressional direction that justifies balancing probabilities with impacts states: “If potential effects of a specified activity are conjectural or speculative, a finding of negligible impact may be appropriate. A finding of negligible impact may also be appropriate if the probability of occurrence is low but the potential effects may be significant. In this case, the probability of occurrence of impacts must be balanced with the potential severity of harm to the species or stock when determining negligible impact. In applying this balancing test, the Service will thoroughly evaluate the risks involved and the potential impacts on marine mammal populations. Such determination will be made based on the best available scientific information.” (132 Cong. Rec. S 16305 (Oct. 15, 1986)). 
                    </P>
                    <P>
                        <E T="03">Comment 21</E>
                        : Greenpeace notes that the available information shows that if there is a major oil spill, the impacts would be severe, and, therefore, NMFS cannot find negligible impact. The risk of a long-term chronic leak, a large spill of 1,000 barrels or more, drill rig blowout and other occurrences exists. Because these events are still possible, BPXA must analyze and incorporate the marine mammal take that would occur. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : Keeping in mind the response to the previous comment, NMFS notes that, while a large oil spill, if it occurred, has the potential to have impacts on bowhead whales and other marine mammal species that are more than negligible, the possibility for a large oil spill to occur is believed by NMFS to be minimal. The Corps' FEIS describes in detail calculations it made for the probability for a major oil spill occurring at Northstar. According to that document there is a 1.6-5-percent chance of a major oil spill occurring along the offshore portion of the pipeline over the first 15 years of operation and a 7-percent chance that there would be a major spill due to platform operations over the life of the platform. NMFS accepts these estimates as the best information available. 
                    </P>
                    <P>Additionally, spilled oil would need to occur at a time and/or location where it could intercept bowhead whales or other marine mammal species. The FEIS describes the fate and consequences of having a major oil spill during different seasons of the year. NMFS also considers this information to be the best scientific information available. As a result, NMFS believes that, because the likelihood of a major oil spill occurring and impacting marine mammals is low for the period of these regulations, it is both impractical and speculative to calculate take levels for major oil spills. The low probability of a major oil spill impacting marine mammals also allows NMFS to make a determination that the taking would have no more than a negligible impact on marine mammals in accordance with Congressional direction mentioned previously. </P>
                    <P>However, NMFS recognizes that in the unlikely event that a major oil spill did occur, the impact has some potential to be more than negligible. As a result, NMFS has determined that, in the event a major oil spill occurs, NMFS will need to reassess immediately its determination in this document that the taking of marine mammals by oil and gas development activities in the Beaufort Sea is having no more than a negligible impact on marine mammals. If, because the takings are projected to exceed the levels used in this document to make a negligible impact finding, NMFS can no longer make a negligible impact determination, NMFS will immediately suspend the LOA issued for the oil development project causing the impact. Because the LOA suspension falls under the emergency determination for LOA suspension under these regulations, NMFS will not provide a 30-day public review period prior to suspension. However, NMFS believes the possibility of this situation occurring is remote. </P>
                    <P>
                        <E T="03">Comment 22</E>
                        : Greenpeace states that the NMFS assertion of negligible impact on endangered species or stock, despite the fact that no specific prediction will be made about the potential number of bowhead whales that would be taken as a result of an oil spill and cleanup, is arbitrary and capricious, and fails to utilize the best scientific and commercial data available. The conclusion of negligible impact is not supported by any assertion of fact. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : Please see the response to the previous two comments. The FEIS discusses the potential for a large oil spill, either through a break in the pipeline or a blowout. As mentioned previously, NMFS adopts this documentation as the best scientific information available. In addition, mitigation measures in place at Northstar, including weekly inspection 
                        <PRTPAGE P="34020"/>
                        overflights of the pipeline (in addition to possibly more frequent flights transporting people and supplies), and incorporation of the LEO spill detection system reduce the potential for chronic leaks to go undetected for long periods of time. 
                    </P>
                    <P>
                        <E T="03">Comment 23</E>
                        : Greenpeace contends that NMFS only cursorily addresses impacts from oil spills and cleanup and fails to analyze the cumulative exposures or the risk to the entire bowhead population from a prolonged disruption of a biologically important behavior or from injury or take over the life of the Northstar project, or due to a catastrophic oil spill. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : The MMPA requires NMFS to make a determination that the total of such taking during each 5-year (or less) period concerned will have a negligible impact on the species or stock of marine mammal, not whether the takings will be negligible over the entire 20-30 year lifespan of Northstar. Also, it is not necessary for NMFS to fully describe the impacts and the determinations made in that regard in the preamble to a proposed rule. The concerns raised by Greenpeace were fully addressed by the Corps in its FEIS. Based upon that document, NMFS believes the taking will have no more than a negligible impact (as defined in § 216.103). 
                    </P>
                    <P>
                        <E T="03">Comment 24</E>
                        : Greenpeace states that oil spill trajectory modeling has not been done to support the conclusion of negligible impact, or the conclusion that the impact will be limited because the trajectory will be confined to the shoreline. Also, Greenpeace states that there is no consideration being given of the persistence of oil in the environment when considering level or numbers of take. The toxicity of oil can persist in the environment for more than ten years. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : As mentioned previously, NMFS believes that the potential for a large oil spill occurring during the 5-year period of these regulations is remote. Therefore, NMFS believes that the recommended studies or considerations are unnecessary for it to make its negligible impact determination. 
                    </P>
                    <P>
                        <E T="03">Comment 25</E>
                        : Greenpeace states that NMFS has provided no legal justification for authorizing incidental take nor has it utilized the best scientific and commercial data available for any of its conclusions. In the draft regulations, NMFS ignored important scientific information indicating greater oil spill and noise impacts and failed to acknowledge deficiencies in many of the studies BPXA relied on in its application, as noted by Albert (1996, 1997). 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS uses the best scientific and commercial information available when making determinations of negligible impact on marine mammal species and no unmitigable adverse impact on species/stocks for subsistence purposes. NMFS believes that this information is contained in the BPXA application, NMFS' biological opinion and the Corps FEIS on Northstar provides this information. Without Greenpeace providing a reference for Albert (1996, 1997) NMFS is unable to respond further to the statement. 
                    </P>
                    <HD SOURCE="HD2">Subsistence Concerns </HD>
                    <P>
                        <E T="03">Comment 26</E>
                        : The AEWC notes that the BPXA application estimates the distances from the Northstar Unit to the traditional hunting areas for 3 fall bowhead whale subsistence villages. However, because the bowhead whale moves in a single westward migration, this information is of limited relevance to NMFS' evaluation of potential adverse impacts on subsistence. Adverse impacts to bowhead whales could affect the subsistence hunting of any or all 10 of the villages depending upon the severity and timing of any oil spill and the perceptions by the various villages on how the oil affected the quality of the subsistence product. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : While the bowhead whale moves in a single westward migration in the fall, except for the unlikely occurrence of a significant oil spill (greater than 1,000 barrels), wherein all 10 villages' bowhead subsistence harvest may be affected, NMFS believes that the impact on bowhead whales from Northstar will be limited to 3 villages, and in particular Nuiqsut. Nuiqsut has the greatest potential to be impacted by development at Northstar, as its whaling customarily takes place in the vicinity of the island. 
                    </P>
                    <P>In the past, NMFS has requested, without success, information regarding the locations where successful bowhead whale takes occur in the Beaufort Sea. Considering that whalers are provided with GPS receivers, this information should be available. This information could provide scientists with data to make assessments on the impacts from oil and gas production activities on Beaufort Sea subsistence whaling. In the interim, NMFS uses the more general information provided by the applicant. </P>
                    <P>Based on the information to date, however, NMFS has determined that the potential for a major oil spill to occur, and for that oil to intercept bowhead whales in the migratory corridor, which in turn, could affect the subsistence harvest of all 10 villages, is unlikely. </P>
                    <P>
                        <E T="03">Comment 27</E>
                        : The NSB notes that one of their primary concerns is the potential for planned (oil development) activities to disrupt fall subsistence whaling by the village of Nuiqsut. NSB believes it is difficult to clearly identify all of the activities associated with construction and operations which are expected to occur during this critical period. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : Activities that have some potential to occur during the same period as Nuiqsut subsistence whaling would include any activities scheduled, but not completed, prior to September. These are described in BPXA's application. However, activities that may occur during that time period may be influenced by agreements made during the C&amp;AA negotiations. Based upon previous C&amp;AAs, and recent statements made by BPXA at a stakeholders meeting in Seattle, NMFS presumes that any activity that creates noise, or has the potential to disturb bowheads, either acoustically or visually, either will not take place or will be modified during the fall subsistence hunt for bowheads. However, even without an agreement to curtail activities during this period, NMFS does not believe these activities will create sufficient level of noise to result in an unmitigable adverse affect on subsistence uses of the bowhead. 
                    </P>
                    <P>
                        <E T="03">Comment 28</E>
                        : The AEWC notes that the annual C&amp;AA is not entered into between BPXA and NSB residents, but by the AEWC on behalf of its bowhead whale subsistence hunters. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS concurs and has made the correction in this document. 
                    </P>
                    <HD SOURCE="HD2">Mitigation Concerns </HD>
                    <P>
                        <E T="03">Comment 29</E>
                        : The AEWC recommends that NMFS take this opportunity to convene a meeting, or a series of meetings, with the AEWC and other interested parties to (1) address arctic offshore oil production-related impacts to marine mammals and subsistence hunting, and (2) discuss appropriate additional mitigation measures during Northstar oil production. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS concurs that a meeting, or a series of meetings, to address mitigation measures that might be adopted by the industry in the event that an oil spill occurs is warranted. In that regard, NMFS hosted a meeting on February 24, 2000, between the AEWC/NSB and the oil industry to start a dialogue to identify monitoring measures for both noise and oil that might be initiated to address both short- and long-term, cumulative impacts. Future meetings are also planned. However, these meetings should not be confused with the peer-review meetings normally held in late spring for the open 
                        <PRTPAGE P="34021"/>
                        water noise monitoring and early fall for on-ice noise monitoring in Seattle, WA. 
                    </P>
                    <P>
                        <E T="03">Comment 30</E>
                        : Greenpeace notes that during the ice covered season, BPXA proposes no mitigation before mid-March, based on the assumption that female ringed seals establish their birth lairs before pupping in late March or April. Noting that ringed seals begin to build lairs as soon as the ice is covered with snow, BPXA must mitigate harassment of ringed seals prior to initiation of any construction activities, regardless of when they commence. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : The primary ice roads used during Northstar construction (and later during oil production), must be almost straight-line in order to effectively transport gravel from the mine site to Seal Island and for construction of the pipeline. Once Northstar and the pipeline are constructed, only a single primary offshore road will need to be constructed annually, that one along the pipeline corridor. As a result, there is little mitigation that has been identified that would be practical and effective during the construction of these primary roads in the early part of the winter season. However, secondary ice roads constructed later in the season, are not believed to be confined to a set track and can be constructed to avoid seal structures. As a result, NMFS has imposed mitigation measures in the LOA which requires (1) Using trained dogs to locate seal structures on all ice roads, (2) avoiding seal structures by a minimum of 150 m (492 ft) during construction of any roads other than the gravel and pipeline primary roads, and (3) avoiding, to the greatest extent practicable, disturbance of any located seal structure after March 20. 
                    </P>
                    <P>It should be recognized that mitigation (using trained dogs) conducted this year during primary ice road construction was implemented because BPXA did not have an authorization for harassment under the MMPA, and therefore needed to avoid, to the greatest extent possible, harassing ringed seals. At a workshop later this year, NMFS will assess the value and practicality of using trained dogs as a mitigation measure to locate seal structures on the ice and then halting activity around the structure until either the animal voluntarily vacates the structure or biological observers determine that the structure is unoccupied. Alternatively, NMFS may determine that it is preferable for the ringed seals to be discouraged, by incidental construction noise, from converting breathing holes into seal structures where pups may later be born, and potentially injured or killed at some later time. </P>
                    <P>Section 101(a)(5)(A)(ii)(I) of the MMPA provides for regulations setting for the permissible methods of taking and other means effecting the least practicable adverse impact on the affected species or stock and its habitat. As ringed seals construct several breathing holes and lairs within its territory, they do not rely on a single structure during the year. Ice roads constructed early in the year will result in some minor harassment as ringed seals abandon certain breathing holes, if the noise is disturbing to them. NMFS believes this may be preferable to avoiding all harassment of ringed seals during ice road construction (how that would be accomplished has not been identified) and then having the newborn pup, who may be more sensitive to noise than an adult, abandon a birthing lair prior weaning, and having that pup succumb to the effects. </P>
                    <P>
                        <E T="03">Comment 31</E>
                        : Greenpeace notes that BPXA is proposing to have marine mammal monitors conduct watches commencing 30 minutes prior to such noisy activities as impact hammering and offloading during the open water season. Greenpeace states that given frequent and often extended periods of impaired visibility in the Beaufort Sea due to fog and low, or no, light conditions, BPXA should include work restrictions during these times. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS does not agree. BPXA proposed having marine mammal monitors to conduct observations for 8 hours/day for 2-3 days during each major type of construction activity, and during quiet periods before and/or after these activities occur. Monitors must conduct observations a minimum of 30 minutes prior to starting noisier activities. If a marine mammal is observed within an area that might cause Level A harassment (180 dB for cetaceans, 190 dB for pinnipeds), work cannot start until the marine mammal has left the safety zone. NMFS has clarified this requirement in the LOA to require marine mammal monitor(s) be on watch during all daylight hours for any activity that results in a SPL of at least 180 dB at any distance which exceeds the island's land/water interface. This monitoring must begin in daylight at least 30 minutes prior to beginning the activity. Also, the entire safety zone must be visible during the entire pre-activity monitoring time period in order for the activity to begin. This means that noisy activities cannot start, or be restarted after a time period set in the LOA during low visibility and nighttime periods. 
                    </P>
                    <P>As an extra precaution, work is required to cease whenever a marine mammal enters its respective safety zone as noted by an observer. However, while certain work must not start-up until the observer can ensure that the safety zones are free of marine mammals, once that work begins it need not cease simply because weather precludes adequate observation during inclement weather or nighttime. NMFS presumes that anthropogenic noise in the area around Northstar will discourage marine mammal presence if the noise is bothersome to the animals. </P>
                    <P>
                        <E T="03">Comment 32</E>
                        : Greenpeace was concerned that BPXA proposes to intentionally harass marine mammals as a form of mitigation in the event of an oil spill. Greenpeace believes that NMFS should not approve the intentional use of harassment to reduce the level of serious injury or mortality. Greenpeace notes that regardless of whether this technique constitutes acceptable mitigation (and Greenpeace asserts it does not), it is not practical given the persistence of oil in the environment. There is no information or reasoned analysis of how long intentional harassment will be used as a mitigation strategy during an oil spill and just how much reduction in Level A harassment will be achieved. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : The intentional harassment of marine mammals for the health and welfare of the animal is under another provision of the MMPA and not under this section. In the event that a significant oil spill occurred, NMFS and other agencies would determine how best to protect marine mammals from oil. 
                    </P>
                    <P>
                        <E T="03">Comment 33</E>
                        : Greenpeace is concerned that BPXA cites its Oil Discharge Prevention and Contingency Plan (ODPCP) as a mitigation measure for protecting marine mammals. Mitigation should not be assumed until BPXA can reasonably prove its ability to respond and remove oil from the environment. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : While NMFS considers the ODPCP to be a mitigation measure to reduce impacts to marine mammals, NMFS also recognizes the inability to respond to an oil spill in the waters surrounding Northstar at certain times and in certain conditions. These constraints to respond in all seasons and weather conditions has been discussed in detail in Chapter 8 of the Corps FEIS. 
                    </P>
                    <P>
                        <E T="03">Comment 34</E>
                        : The MMC recommends that NMFS review the ODPCP to assure that the risk of spills has been estimated appropriately; require modification of the contingency plan if everything feasible has not been done to minimize the risk of spills occurring and impacting marine mammals; and provide for periodic site inspections as part of the long-term monitoring 
                        <PRTPAGE P="34022"/>
                        program to assure that the contingency plan can be implemented as and when necessary. Finally, the MMC recommends that an assessment of the contingency plan and any monitoring requirements be included in any 
                        <E T="04">Federal Register</E>
                         document published to promulgate final regulations on this action. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS believes that it has neither the expertise to determine the adequacy of the ODPCP, nor the authority under the MMPA to require the ODPCP be modified by BPXA or to place these requirements on Federal or state agencies with such authority. As the MMC noted in its comment, the ODPCP has been approved by the U.S. Department of Transportation, the U.S. Coast Guard, the Minerals Management Service (MMS), and the State of Alaska Department of Environmental Conservation. For its determinations of negligible impact, NMFS relies on the information, including estimates of risk from oil spills, contained in the FEIS. 
                    </P>
                    <HD SOURCE="HD2">Monitoring Concerns </HD>
                    <P>
                        <E T="03">Comment 35</E>
                        : The NSB believes that the proposed marine mammal monitoring plan in its present form is inadequate. The plan, and especially the proposal for passive acoustic monitoring of fall migrating bowhead whales, should be revised and made clearer. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : BPXA's technical plan for marine mammal and acoustic monitoring during construction of Northstar was submitted to NMFS in May, 1999, as a supplement to its November 1998, petition. That plan was reviewed at the peer review workshop held in Seattle, WA on July 1, 1999, and revised in August 1999, based on the recommendations made during the workshop. The NSB participated in that workshop. NMFS does not believe that it is necessary at this time to request BPXA to revise the plan prior to providing all parties at the workshop an opportunity to respond. Since this plan will be reviewed again later this year, the comments and recommendations made by the NSB will be placed on this year's meeting agenda. 
                    </P>
                    <P>
                        <E T="03">Comment 36</E>
                        : Greenpeace notes that, although NMFS is proposing regulations governing the taking of marine mammals during the construction and operation of Northstar, the accompanying marine mammal monitoring program only applies to project construction. The monitoring program fails to outline a program for monitoring marine mammal takes during Northstar operation. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : BPXA's revised monitoring plan as submitted on September 1, 1999, provides detailed description of proposed monitoring during construction. This monitoring had been amended based on comments received during the Arctic Peer Review Workshop held in Seattle, WA on July 1, 1999. 
                    </P>
                    <P>A detailed description of monitoring during Northstar operations was not submitted at the time because that monitoring program would not begin until oil drilling operations began, approximately November 2000. BPXA will submit a monitoring plan for operations in sufficient time for that plan to be reviewed by peers and the general public. NMFS anticipates public review on the monitoring plan during the first year of operations will be conducted during the public comment period on an application for LOA renewal, which will be contingent on submission of an adequate monitoring plan. In the interim, BPXA will continue monitoring impacts as described in the August 20, 1999, Technical Monitoring Plan. As stated in BPXA's application, monitoring during operations will require evaluation based on the results of monitoring during construction and any other information that becomes available in the interim. NMFS intends to continue past practice and have annual submissions of proposed monitoring plans and to have those plans peer reviewed prior to implementation. </P>
                    <P>
                        <E T="03">Comment 37</E>
                        : Greenpeace believes that specific monitoring requirements should be included in the regulations, not in the LOA. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : If specific monitoring conditions are contained in the regulations, modifications to the monitoring would require an amendment to the regulations prior to implementation. This would prevent prompt implementation of revised monitoring based on the annual review process, or in response to an unusual event, as can be done by having specific monitoring conditions contained in an LOA. As a result, NMFS has not adopted this recommendation. However, it should be noted that BPXA must comply with the conditions of the LOA, so it would be responsible for implementing any monitoring identified in the LOA. 
                    </P>
                    <P>
                        <E T="03">Comment 38</E>
                        : Greenpeace states that NMFS cannot assume that the impacts of the Northstar operations on marine mammals will be negligible in the absence of a detailed monitoring program to back up that assertion. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS believes that the results from monitoring are useful to support or refute its determinations that takings are having a negligible impact on affected marine mammal stocks and not having an unmitigable adverse impact on subsistence uses of marine mammals. However, a detailed monitoring program is not a requirement under the MMPA before NMFS can make these determinations; the MMPA requires only that a monitoring program be required under regulations authorizing the taking. For Northstar, NMFS expects that, through the peer review process, a comprehensive monitoring program will be implemented that will provide the necessary information on impacts on marine mammals. 
                    </P>
                    <P>
                        <E T="03">Comment 39</E>
                        : Greenpeace states that BPXA's proposed plan to establish a peer review process as outlined in its monitoring plan is not sufficiently independent to meet the standards of the MMPA. The regulations should require BPXA to submit the monitoring plans well in advance so that NMFS can instigate its own independent peer review, and require that its recommendations be incorporated into the final plans. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : The peer review process described in BPXA's Technical Plan for Marine Mammal and Acoustic Monitoring During Construction of BP's Northstar Oil Development in the Alaskan Beaufort Sea, 2000, is the same as NMFS' Arctic Peer Review Workshop held annually in Seattle, WA. Participants in this workshop, and similar workshops held to discuss on-ice monitoring of seals, typically include representatives from industry, the NSB, the AEWC, universities, environmental organizations, and state and Federal government. 
                    </P>
                    <P>
                        It should be understood that independent peer review in this context means a review by other than NMFS, the oil industry and its contractors, and the AEWC/NSB. However, independent peer review is not required for authorizations issued under section 101(a)(5)(A) of the MMPA. While peer review of monitoring plans has been incorporated into these regulations in accordance with findings made at a workshop held in Seattle in 1994 with the AEWC, the oil and gas industry and others, independent peer review is at the discretion of NMFS. On April 9, 1999 (64 FR 17347), NMFS requested nominations for the voluntary participation in the peer review process. Due to a lack of interest expressed by the public in response to this notice, NMFS has decided to reserve use of an independent peer review to matters of significant dispute between the AEWC, NMFS, and/or the Holder of an LOA. In general, specific requirements for independent peer review will be 
                        <PRTPAGE P="34023"/>
                        determined in advance and noted in an LOA. 
                    </P>
                    <P>
                        <E T="03">Comment 40</E>
                        : Both the MMC and BPXA note that the preamble to the proposed rule failed to mention the acoustic monitoring program for bowhead whales described in BPXA's revised application and monitoring plan. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS acknowledges the oversight. BPXA's technical plan for marine mammal and acoustic monitoring during construction at Northstar proposed seven monitoring tasks, not six. These tasks are listed elsewhere in this document. 
                    </P>
                    <P>
                        <E T="03">Comment 41</E>
                        : The MMC recommends that NMFS review past aerial survey data to determine whether the surveys conducted by the MMS are likely to provide sufficient information to assess the utility of the proposed acoustic monitoring and if the MMS' surveys are judged unlikely to provide sufficient data, require that additional surveys be done during the construction phase to document the presumed effectiveness of the acoustic monitoring. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : Thank you for this recommendation. As noted in BPXA's application, use of an acoustical monitoring system is planned to be tested in 2000. The purpose of the system is, in part, to assess the feasibility of its use as an alternative to aerial surveys. In addition to MMS surveys, additional aerial surveys for bowheads are conducted in the region to assess impacts from seismic work. This data would also be available for analysis. As a result, the MMC's comments have been forwarded to NMFS scientists and others for consideration. However, NMFS recommends MMC scientists participate in the peer review workshops so that the concerns of the MMC can be addressed more directly. 
                    </P>
                    <P>
                        <E T="03">Comment 42</E>
                        : The MMC, because of perceived uncertainties in the data regarding impacts to ringed seals and polar bears and interactions between these two species, recommends that monitoring of polar bears and polar bear den sites required by regulations and LOAs issued by the U.S. Fish and Wildlife Service (USFWS) will be coordinated with the ringed seal monitoring required by this set of regulations and LOAs. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS is unaware of any evidence that increased interactions between polar bears and ringed seals will occur as a result of construction of ice roads and the reconstruction of Seal Island. To the extent practicable, on-ice monitoring of ringed seals and polar bears has been, and will be, coordinated. NMFS notes that often the same biological observers conducting ringed seal observations are also conducting polar bear observations. In addition, the USFWS has attended on-ice peer review workshops wherein NMFS and others review previous monitoring and upcoming monitoring plans. The MMC concerns expressed here will be reviewed at the next meeting. NMFS recommends that, if the MMC has any suggestions regarding appropriate study designs to determine whether oil and gas activity results in increased interactions between polar bears and ringed seals, they should provide that information to NMFS prior to the next on-ice peer review meeting. 
                    </P>
                    <P>
                        <E T="03">Comment 43</E>
                        : Greenpeace asserts that BPXA's monitoring program relies on ineffective methods for monitoring ringed seals. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : To the extent practicable, NMFS follows the guidelines in Swartz and Hofman (1991) when reviewing and making recommendations on monitoring oil and gas activities in Arctic waters. Based on that document, and the results of a workshop held in Seattle in October 1999, BPXA has implemented a monitoring program using dogs to locate ringed seal structures in the ice. However, NMFS notes that using dogs this winter, prior to issuance of an LOA, does not mean that dogs will be required each year that ice roads are constructed. That determination will be based in part on the recommendations of scientists and the value of the information provided by this method of data collection. Generally, in cases where ice roads are constructed early in the year, under an LOA or IHA to take marine mammals, NMFS has questioned the need for dogs to monitor harassment takings. However, in order to protect newborn pups, dogs will be required under an LOA, whenever new, secondary, ice roads are constructed after March 1. 
                    </P>
                    <P>Following Swartz and Hofman (1991), NMFS has determined that the Before-After Control-Impact (BACI) study of ringed seal distribution meets the monitoring requirements for assessing impacts on ringed seals during wintertime construction and operation. This does not mean however, that additional or alternative ringed seal monitoring will not be required in future years under an LOA. Such monitoring may be imposed as a result of future peer review workshops. </P>
                    <HD SOURCE="HD2">Reporting Concerns </HD>
                    <P>
                        <E T="03">Comment 44</E>
                        : The AEWC requests that, when scheduling review periods, NMFS give due consideration to the time of year when that period will occur. Spring bowhead whale subsistence hunting generally is most intense for our communities during April, May, and June. In addition, the annual meetings of the International Whaling Commission, usually are scheduled sometime between early May and mid-July. These meetings last a total of 4 weeks and require intense preparation. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : Considering that the fall bowhead whaling season begins around September 1 and continues for several weeks, wherein the AEWC is also not available for reviewing documents and meeting, there is limited time during the year for an annual review. 
                    </P>
                    <P>As proposed previously, an interim report was due 180 days prior to expiration of an LOA. If an LOA expires early in the year, as is expected with the Northstar LOA, then the report would be due 6 months prior to that date, or in late summer of the previous year. Because of the timing, this report obviously could not include an assessment of the activity's impact on bowhead whales and the subsistence harvest that year since the fall migration would only be starting at that time. Therefore, this report would need to contain an assessment of the previous year's impact on bowhead whales, requiring the use of dated information, and putting the data out of synchrony with the actual taking of marine mammals during that LOA period of validity. However, this is realistic considering that it takes 6-7 months to incorporate MMS aerial survey data on bowheads into an analysis of impacts from an oil and gas exploration or development activity. </P>
                    <P>
                        As a result, because of the importance of having a peer review of both monitoring plans and the results from previous monitoring, NMFS has amended the regulations and is requiring holders of LOAs to provide two interim reports, the first due 90 days after the end of the on-ice season (approximately September 15
                        <E T="51">th</E>
                         for the report), and the second due 90 days after the end of the fall bowhead migration in the Beaufort Sea (approximately February 1
                        <E T="51">st</E>
                         for the report). NMFS will also require a draft comprehensive report by May 1
                        <E T="51">st</E>
                         of the year following the year of validity of the LOA. NMFS recognizes that this means that the first year LOA for Northstar will only have a report on the on-ice monitoring due to NMFS by the time NMFS needs to consider a renewal of the first-year LOA. 
                    </P>
                    <P>
                        Finally, NMFS will require a final comprehensive report on all marine mammal monitoring and research conducted by the holder of its LOAs during the period of these regulations 
                        <PRTPAGE P="34024"/>
                        must be submitted at least 240 days prior to expiration of these regulations or 240 days after the expiration of these regulations, if renewal of the regulations has not been requested. 
                    </P>
                    <P>
                        <E T="03">Comment 45</E>
                        : The NSB believes that the proposed method for project review (two reviews/year, one through the mail) is not adequate. One meeting is needed to review the draft proposal and a second meeting is needed to review the draft report. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS disagrees that a meeting is necessary solely to review BPXA's draft monitoring report(s). For continuity, this report (which is a report on the results of previous years' monitoring programs), is usually reviewed and critiqued at the same time the NSB and others are recommending monitoring measures for the upcoming season. NMFS believes that discussion on the results of previous monitoring at the same time as discussion of the upcoming monitoring plan, facilitates recommendations on appropriate monitoring and/or research. 
                    </P>
                    <P>In addition, recognizing the period of time when NSB residents are not available to meet (discussed previously in this document) and because the NSB, NMFS, and others are already sponsoring and/or participating in three meetings annually on this issue, one for open water monitoring, a second for winter (on-ice) monitoring, and a third to address short- and long-term monitoring for effects from potential oil spills on marine mammals, a fourth meeting limited to discussion on the results of previous year's monitoring is simply not practical at this time. </P>
                    <HD SOURCE="HD2">ESA Concerns </HD>
                    <P>
                        <E T="03">Comment 46</E>
                        : Greenpeace contends that the proposed rule (64 FR 57010, October 22, 1999) violates section 7(a)(2) of the ESA because it fails to insure that actions to approve regulations are not likely to jeopardize the continued existence of endangered species, after required consultation and using the best scientific and commercial data available. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : With the issuance of a Biological Opinion (BO) on March 4, 1999, NMFS completed formal consultation with the Corps under section 7 of the ESA for the construction and operation of the Northstar project. The BO, which found that the construction and operation of the Northstar project activity will not jeopardize the continued existence of any species under the jurisdiction of NMFS, was based upon the best scientific and commercial data available. Because issuance of these regulations and an LOA to BPXA for the incidental take of bowhead whales is also considered a Federal action, NMFS has conducted a consultation under section 7 with itself on this action. The finding by NMFS is that an authorization for the taking of bowhead whales incidental to construction and production of the Northstar Unit, under section 101(a)(5)(A) of the MMPA, while it may adversely affect bowhead whales, is not likely to jeopardize its continued existence. If new information is obtained which affect bowhead whales in a manner or to an extent not previously considered, or if the level of incidental take is exceeded, reinitiation of consultation will be undertaken. 
                    </P>
                    <P>
                        <E T="03">Comment 47</E>
                        : Greenpeace also contends that, by proposing the regulation, NMFS has made an irreversible and irretrievable commitment of resources with respect to the Northstar project, which has the effect of foreclosing the formulation or implementation of reasonable and prudent alternative measures which would not violate section 7(a)(2) of the ESA. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS does not agree that it has made an irreversible and irretrievable commitment of resources in conjunction with proposing regulations for the project. NMFS completed its section 7 responsibilities prior to issuance of this final rule. 
                    </P>
                    <P>
                        <E T="03">Comment 48</E>
                        : Greenpeace believes that the proposed rule (64 FR 57010, October 22, 1999) fails to utilize its authorities in furtherance of the purposes of section 7(a)(1) of the ESA by carrying out programs for the conservation of endangered species. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : Conservation recommendations under section 7(a)(1) of the ESA were provided by NMFS to the Corps in the Northstar BO. These include: (1) Vessel operations should be scheduled to minimize operations after August 31 of each year in order to reduce potential harassment of migrating bowhead whales, (2) utilize agitation technique for placement of sheetpiling and piling instead of pile-driving whenever practicable, (3) develop and conduct an acoustic monitoring study during construction and initial operation, and (4) conduct or support studies to describe the impact of Northstar on the migrational path of bowhead whales in the Beaufort Sea. 
                    </P>
                    <P>Additional conservation recommendations to reduce impacts on the endangered bowhead whale are contained in these regulations, the BPXA LOA, and the Incidental Take Statement issued to the Corps under section 7(a)(2) of the ESA. </P>
                    <P>
                        <E T="03">Comment 49</E>
                        : Greenpeace notes that the proposed rule (64 FR 57010, October 22, 1999) states that NMFS has begun consultation under section 7, but that there has been no public release of information concerning the scope of consultation nor of a biological assessment which adequately assess these impacts. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : While there is no requirement in the ESA for making that information public, this document notifies the public of the completion of section 7 consultation. Recognizing that impacts on listed species will result from the activity itself, not from the issuance of an authorization for the incidental taking, NMFS has determined that the issuance of 5-year regulations for the Northstar Project, and a 1-year LOA, may affect bowhead whales, the action was unlikely to jeopardize the stock's continued existence. Because Biological Assessments are written at the discretion of the action agency, and because a BO was written previously on the major action (i.e., on construction and operation of Northstar), a new Biological Assessment is not necessary for this action and, therefore, one was not prepared. 
                    </P>
                    <P>
                        <E T="03">Comment 50</E>
                        : There was no incidental take statement in the Northstar BO. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : That is correct. Whenever a marine mammal species listed as endangered or threatened under the ESA is involved, section 7(b)(4)(C) of the ESA requires that the taking is also authorized pursuant to section 101(a)(5) of the MMPA. Until the requirements of both the MMPA and ESA are met, an incidental take statement cannot be issued. The issuance of an LOA to BPXA for Northstar will meet the MMPA requirements and an Incidental Take Statement can be, and will be, issued shortly. 
                    </P>
                    <P>
                        <E T="03">Comment 51</E>
                        : Greenpeace states that the proposed rule results in a taking of a protected species in violation of section 9 of the ESA. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : The taking of endangered bowhead whales incidental to the construction and operation of the Northstar Unit is not expected to be in violation of section 9 of the ESA. Under the terms of section 7(b)(4) and section 7(o)(2), taking that is incidental to, and not intended as part of, the agency action is not considered to be prohibited taking under the ESA provided that such taking is in compliance with the terms and condition of the Incidental Take Statement. As mentioned previously, the incidental taking of bowhead whales under the ESA will be authorized through an Incidental Take Statement issued under section 7 of the ESA. 
                    </P>
                    <P>
                        <E T="03">Comment 52</E>
                        : The original Northstar BO did not address the quantitative 
                        <PRTPAGE P="34025"/>
                        information submitted by BPXA in its incidental take publication regarding expected level of takes, such as 173-1,533 bowheads annually, or sources of impacts, such as 16,800 large-volume haul trips, 28,500 dump trucks, etc. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : The Biological Assessment was first submitted to NMFS by the Corps on May 19, 1998, with supplemental information provided on July 10, 1998. This was prior to BPXA submitting information for an IHA on August 12, 1998 (63 FR 57096, October 26, 1998), or on November 30, 1998, for this action. While NMFS could have included this additional information in its BO, this information was considered preliminary at the time and unnecessary for making a determination on whether or not the activity could jeopardize the bowhead whale's continued existence. Estimates of bowhead whale takes by harassment have been evaluated during this rulemaking and will be incorporated as appropriate into the Incidental Take Statement. NMFS notes however, that the activities mentioned by the commenter will occur during the winter and will not affect bowheads. 
                    </P>
                    <P>
                        <E T="03">Comment 53</E>
                        : Greenpeace believes that NMFS has failed to conduct a North Slope-wide assessment of the impacts to bowhead whales from reasonably foreseeable exploration and development activities in the Beaufort Sea. 
                    </P>
                    <P>
                        <E T="03">Response</E>
                        : NMFS' evaluation of the cumulative effects on bowhead whales, by Beaufort Sea activities, were addressed in part V. of the March 4, 1999, BO. 
                    </P>
                    <P>Description of Habitat and Marine Mammal Affected by the Activity </P>
                    <P>
                        The DEIS and FEIS prepared for the Northstar development (Corps, 1998, 1999) contains a detailed description of the Beaufort Sea ecosystem and its associated marine mammals. Those documents are part of the record of decision of this rulemaking. A copy of the FEIS is available from the Corps upon request (see 
                        <E T="02">ADDRESSES</E>
                        ). 
                    </P>
                    <HD SOURCE="HD2">Marine Mammals </HD>
                    <P>
                        The Beaufort/Chukchi Seas support a diverse assemblage of marine mammals, including bowhead whales (
                        <E T="03">Balaena</E>
                          
                        <E T="03">mysticetus</E>
                        ), gray whales (
                        <E T="03">Eschrichtius</E>
                          
                        <E T="03">robustus</E>
                        ), beluga whales (
                        <E T="03">Delphinapterus</E>
                          
                        <E T="03">leucas</E>
                        ), ringed seals (
                        <E T="03">Phoca</E>
                          
                        <E T="03">hispida</E>
                        ), spotted seals (
                        <E T="03">Phoca</E>
                          
                        <E T="03">largha</E>
                        ) and bearded seals (
                        <E T="03">Erignathus</E>
                          
                        <E T="03">barbatus</E>
                        ). Descriptions of the biology and distribution of these species and of others can be found in several documents (e.g., Hill and DeMaster, 1998) including the BPXA application (BPXA, 1999) and the previously mentioned FEIS. Please refer to those documents for specific information on these species. These documents are part of this rulemaking. In addition to the species mentioned in this paragraph, Pacific walrus (
                        <E T="03">Odobenus</E>
                          
                        <E T="03">rosmarus</E>
                        ) and polar bears (
                        <E T="03">Urus</E>
                          
                        <E T="03">maritimus</E>
                        ) also have the potential to be taken. Appropriate applications for taking these species under the MMPA have been submitted to the USFWS by BPXA. 
                    </P>
                    <HD SOURCE="HD1">Potential Effects on Marine Mammals </HD>
                    <HD SOURCE="HD2">Noise Impacts </HD>
                    <P>Sounds and non-acoustic stimuli will be generated during construction by vehicle traffic, ice-cutting, pipeline construction, offshore trenching, gravel dumping, sheet pile driving, and vessel and helicopter operations. Sounds and non-acoustic stimuli will be generated during oil production operations by generators, drilling, production machinery, gas flaring, camp operations and vessel and helicopter operations. The sounds generated from construction and production operations and associated transportation activities will be detectable underwater and/or in air some distance away from the area of the activity, depending upon the nature of the sound source, ambient noise conditions, and the sensitivity of the receptor. At times, some of these sounds are likely to be strong enough to cause an avoidance or other behavioral disturbance reaction by small numbers of marine mammals or to cause masking of signals important to marine mammals. The type and significance of behavioral reaction is likely to depend on the species and season, and the behavior of the animal at the time of reception of the stimulus, as well as the distance and level of the sound relative to ambient conditions. </P>
                    <P>In winter and spring, on-ice travel and construction activities will displace some small numbers of ringed seals along the ice road and pipeline construction corridors. BPXA began winter construction activities in mid-December, 1999, well in advance of female ringed seals establishing birthing lairs beginning in the latter half of March. The noise and general human activity may displace female seals away from activity areas and could negatively affect the female and young, if the female remained in the vicinity of the ice road. </P>
                    <P>
                        During the open-water season, all six species of whales and seals could potentially be exposed to vessel or construction noise and to other stimuli associated with the planned operations. Vessel traffic is known to cause avoidance reactions by whales at certain times (Richardson 
                        <E T="03">et</E>
                          
                        <E T="03">al</E>
                        ., 1995). Pile driving, helicopter operations, and possibly other activities may also lead to disturbance of small numbers of seals or whales. In addition to disturbance, some limited masking of whale calls or other low-frequency sounds potentially relevant to bowhead whales could occur (Richardson 
                        <E T="03">et</E>
                          
                        <E T="03">al</E>
                        ., 1995; BPXA, 1999). 
                    </P>
                    <P>
                        A more detailed description of potential impacts from construction and operational activities on marine mammals can be found in BPXA's application (BPXA, 1999) and the Corps' FEIS (Corps, 1999). That information is accepted by NMFS as a summation of the best scientific information available on the impacts of noise on marine mammals in this area. Additional information used by NMFS in this determination can be found in Richardson 
                        <E T="03">et</E>
                          
                        <E T="03">al</E>
                        . (1995) and the references provided in BPXA's application. 
                    </P>
                    <HD SOURCE="HD2">Oil Spill Impacts </HD>
                    <P>For reasons stated in the application, BPXA believes that the effects of oil on seals and whales in the open waters of the Beaufort Sea are likely to be negligible, but there could be effects on whales in areas where both oil and the whales are at least partially confined in leads or at the ice edge. In the spring, bowhead and beluga whales migrate through offshore leads in the ice. However, given the probable alongshore trajectory of oil spilled from Northstar, in relation to the whale migration route through offshore waters, interactions between oil and whales are unlikely in the spring. In the summer, bowheads are normally found in Canadian waters, and beluga whales are found far offshore. As a result, at this time of the year, these species will be unaffected should a spill occur. However, oil that persists in the Beaufort Sea into the fall or winter and is not contained and/or removed may impact bowhead whales. </P>
                    <P>
                        In the fall, the migration route of bowheads can be close to shore. If bowheads were moving through leads in the pack ice, or were concentrated in nearshore waters, or if the oil migrated seaward of the barrier islands, some bowhead whales might not be able to avoid oil slicks and could be subject to prolonged contamination. However, because the autumn migration of bowhead whales past Northstar extends over several weeks and because most of the whales travel along routes well north of Northstar, according to BPXA, only a small minority of the whales are likely to intercept patches of spilled oil. The effects of oil on these whales have been described in several documents (BPXA, 1999; Corps, 1999; Loughlin 
                        <E T="03">et</E>
                          
                        <PRTPAGE P="34026"/>
                        <E T="03">al</E>
                        . (1994), which NMFS reviewed during this rulemaking. 
                    </P>
                    <P>Ringed seals exposed to oil during the winter or early spring could die if exposed to heavy doses of oil for prolonged periods of time. Prolonged exposure could occur if fuel or crude oil was spilled in or reached nearshore waters, was spilled in a lead used by seals, or was spilled under the ice when seals have limited mobility. Individual seals residing in these habitats may not be able to avoid prolonged contamination and some would die. Studies in Prince William Sound indicated a long-term decline of 36 percent in numbers of molting harbor seals located on those haulouts affected by oil from the EXXON VALDEZ spill. In addition, newborn seal pups, if contacted by oil, will likely die from oiling through loss of insulation and resulting hypothermia (BPXA, 1999). Because the number of ringed and bearded seals in the central Beaufort Sea represents a relatively small portion of their total populations, and even large oil spills are not expected to extend over large areas, relatively few ringed and bearded seals would be impacted, and impacts on regional population size would be expected to be minor. </P>
                    <P>In addition to oil contacting marine mammals, oil spill cleanup activities could increase disturbance effects on either whales or seals, causing temporary disruption and possible displacement effects (MMS, 1996; BPXA, 1999). In the event of a large spill contacting and extensively oiling coastal habitats, the presence of response staff, equipment, and many low-flying aircraft involved in the cleanup will (depending on the time of the spill and cleanup), potentially displace seals and other marine mammals. However, the potential effects on bowhead and beluga whales are expected to be less than those on seals. The whales tend to occur well offshore where cleanup activities (during the open water season) are unlikely to be concentrated (BPXA, 1999). Also, because bowheads are transient and during the majority of the year, absence from the area would lessen the likelihood of impact by cleanup activities. </P>
                    <HD SOURCE="HD2">Estimated Level of Incidental Take </HD>
                    <P>
                        BPXA (1999) estimates that, during the ice-covered period, 91 (maximum 125) ringed seals and 1 (maximum 5) bearded seals potentially may be incidentally harassed during construction activities and 77 (maximum 105) ringed seals and 1 (maximum 5) bearded seals potentially may be incidentally harassed annually during oil production activities. BPXA estimates these takings by harassment during the ice-covered season by assuming that seals within 3.7 km (2.3 mi) of Seal Island, within 1.85 km (1.1 mi) of the pipeline construction corridor and related work areas, and within 0.66 km (0.4 mi) of ice roads will be “taken” annually. These anticipated levels of potential take are estimated based on observed densities of seals during recent (1997-1999) BPXA/LGL aerial surveys in the Northstar area during spring (Miller 
                        <E T="03">et</E>
                          
                        <E T="03">al</E>
                        ., 1998; Link 
                        <E T="03">et</E>
                          
                        <E T="03">al</E>
                        ., 1999; Moulton and Elliott, 1999) plus correction factors for seals missed by aerial surveyors. NMFS however, concurs with BPXA (1999) that these “take” estimates could result in an overestimate of the actual numbers of seals “taken,” if all seals within these disturbance distances do not move from the area. It should be noted that NMFS does not consider an animal to be “taken” if it simply hears a noise, but does not make a biologically significant response to avoid that noise. 
                    </P>
                    <P>NMFS notes moreover, that BPXA has recently adopted new methods for on-ice monitoring of ringed seals which include the use of dogs to find seal structures. These new methods may result in a better estimate of the numbers of seals actually taken by different industrial activities. </P>
                    <P>During the open-water season, BPXA (1999) estimates that 7 (maximum 22) ringed seals, 1 spotted seal, 1-5 bearded seals, 173 (maximum 1,533) bowhead whales, less than 5 gray whales, and 6 (maximum 45) beluga whales may be incidentally harassed annually whether from construction or operations. BPXA assumes that seals and beluga whales within 1 km (0.6 mi) radius of Seal Island will be harassed incidental to construction and other activities on the island. Assumed “take” radii for bowhead whales are based on the distance at which the received level of construction noise from the island would diminish below 115 dB re 1 μPa. This distance has been estimated as 3.2 km (2 mi). </P>
                    <P>Although the potential impacts to the several marine mammal species known to occur in these areas is expected to be limited to harassment, a small number of marine mammals may incur lethal and serious injury. Most effects, however, are expected to be limited to temporary changes in behavior or displacement from a relatively small area near the construction site and will involve only small numbers of animals relative to the size of the populations. However, the inadvertent and unavoidable take by injury or mortality of small numbers of ringed seal pups may occur during ice clearing for construction of ice roads. In addition, some injury or mortality of whales or seals may result in the event that an oil spill occurs. As a result, BPXA requested that, because a small number of marine mammals might be injured or killed, that takings by mortality also be covered by the regulations. However, BPXA does not indicate the level of incidental take resulting from an oil spill at Northstar during either the ice-covered period or the open-water period. Because of the unpredictable occurrence, nature, seasonal timing, duration, and size of an oil spill occurring during the 5-year authorization period of these regulations, a specific prediction cannot be made of the estimated number of takes by an oil spill. </P>
                    <P>According to BPXA, in the unlikely event of a major oil spill at Northstar or from the associated subsea pipeline, numbers of marine mammals killed or injured are expected to be small and the effects on the populations negligible. While NMFS agrees that a major oil spill is unlikely during the 5-year period of these regulations, and believes that it is even less likely that spilled oil will intercept large numbers of marine mammals, NMFS cannot necessarily conclude that the effects on marine mammal populations will be negligible. Depending upon magnitude of the spill, its location and seasonality, an oil spill could have the potential to affect ringed and bearded seals, and/or bowhead and beluga whales. Because of the large population size of ringed seals and bearded seals and the small number of animals in the immediate vicinity of the Northstar facility, and because spilled oil is unlikely to disperse widely and, therefore, affect large numbers of seals, NMFS has determined that the effect on ringed and bearded seals will be negligible, even in the unlikely event that a major oil spill occurred. </P>
                    <P>
                        Bowhead and beluga whales, however, while potentially less likely to come into contact with spilled oil because of their more prevalent offshore distribution, and potentially less seriously affected when in oiled waters provided their passage is not blocked, may be affected more seriously, if impacted, because of their smaller population sizes. However, based upon the Corps' analysis that there is less than a 10-percent chance of a major oil spill occurring during the 20-30 year lifespan of Northstar, and because NMFS believes that the potential for a major oil spill occurring during the 5-year period of these regulations and intercepting these species would be significantly less than 10 percent (approaching 1 percent), NMFS can 
                        <PRTPAGE P="34027"/>
                        make a determination that the taking of these two species incidental to construction and operation at the Northstar oil production facility will have no more than a negligible impact on them. 
                    </P>
                    <HD SOURCE="HD2">Impacts on Subsistence Uses </HD>
                    <P>This section contains a summary on the potential impacts from construction and operational activities on subsistence needs for marine mammals. A more detailed description can be found in BPXA's application. This information, in conjunction with information provided by the AEWC and NSB in their comments, and information provided in the Corps' FEIS, is accepted by NMFS as the best information available to date on the potential effects on the availability of marine mammals for subsistence uses in the Beaufort Sea area. Should new information on the impacts to subsistence harvest of bowhead whales become available that may be contrary to the determination made here, NMFS will consider the information during review of a request for future LOAs and/or their renewal. </P>
                    <HD SOURCE="HD2">Noise Impacts </HD>
                    <P>
                        The disturbance and potential displacement of bowhead whales and other marine mammals by sounds from vessel traffic, on-island construction activities (
                        <E T="03">e.g.,</E>
                         impact hammering), and production activities are one of the principle concerns related to subsistence use of the area. The harvest of marine mammals is central to the culture and subsistence economies of the coastal North Slope communities. In particular, if elevated noise levels are displacing migrating bowhead whales farther offshore, this could make the harvest of these whales more difficult and dangerous for hunters. The harvest could also be affected if bowheads become more skittish when exposed to vessel or impact-hammering noise (BPXA, 1999). 
                    </P>
                    <P>Construction activities and associated vessel and helicopter support began in December 1999, and are expected to continue into September or October 2000, depending upon ice conditions. Few bowhead whales approach the Northstar area before the end of August, and subsistence whaling generally does not begin until after September 1 and occurs in areas well east of the construction site. Therefore, a substantial portion of the Northstar development is expected to be completed when no bowhead whales are nearby and when no whaling is underway. Insofar as possible, BPXA expects vessel and aircraft traffic near areas of particular concern for whaling will be completed before the end of August. In addition, BPXA does not expect impact hammering to occur during the period when subsistence hunting of migrating bowhead whales is underway. NMFS expects that construction activities that have the potential to disturb bowheads just prior to, and during the bowhead subsistence hunt, would be subject for discussion and resolution during the C&amp;AA discussions. However, even without an agreement to curtail activities during this period, NMFS does not believe these activities will create sufficient level of noise to result in an unmitigable adverse affect on subsistence uses of the bowhead. </P>
                    <P>Underwater sounds from drilling and production operations on an artificial gravel island are not very strong, and are not expected to travel more than about 10 km (6.2 mi) from the source. BPXA states that even those bowheads traveling along the southern edge of the migration corridor are not expected to be able to even hear sounds from Northstar until the whales are well west of the main hunting area. </P>
                    <P>Drilling will begin in the latter part of 2000 but will temporarily cease in mid-2001 to allow installation and start-up of processing facilities. Drilling is expected to resume by November 2001, after the bowhead season, and continue until approximately November, 2002. Drilling is, therefore, unlikely to impact either the bowheads or the subsistence needs for this species, prior to the 2002 bowhead season. </P>
                    <P>Nuiqsut is the community closest to the area of the proposed activity, and it harvests bowhead whales only during the fall whaling season. In recent years, Nuiqsut whalers typically take zero to four whales each season (BPXA, 1999). Nuiqsut whalers concentrate their efforts on areas north and east of Cross Island, generally in water depths greater than 20 m (65 ft). Cross Island, the principle field camp location for Nuiqsut whalers, is located approximately 28.2 km (17.5 mi) east of the Northstar construction activity area. </P>
                    <P>Whalers from the village of Kaktovik search for whales east, north, and west of their village. Kaktovik is located approximately 200 km (124.3 mi) east of Northstar. The westernmost reported harvest location was about 21 km (13 mi) west of Kaktovik, near 70°10'N. 144°W. (Kaleak, 1996). That site is approximately 180 km (112 mi) east of Northstar. </P>
                    <P>Whalers from the village of Barrow search for bowhead whales much further from the Northstar area, greater than 250 km (&gt;175 mi) west. </P>
                    <P>While the effects on migrating bowheads from noise created by Northstar construction or production are not expected to extend into the area where Nuiqsut hunters usually search for bowheads and, therefore, are not expected to affect the accessibility of bowhead whales to hunters, it is recognized that it is difficult to determine the maximum distance at which reactions occur (Moore and Clark, 1992). As a result, in order to avoid any unmitigable adverse impact on subsistence needs and to reduce potential interference with the hunt, the timing of various construction activities at Northstar as well as barge and aircraft traffic in the Cross Island area will be addressed in a C&amp;AA between BPXA and the AEWC on behalf of its bowhead whale subsistence hunters. Also, NMFS believes that the September 1999, Technical Monitoring Plan that will be implemented by BPXA will provide information that will help resolve uncertainties about the effects of construction noise on the accessibility of bowheads to hunters. </P>
                    <P>While Northstar activity has some potential to influence subsistence seal hunting activities, the most important sealing area for Nuiqsut hunters is off the Colville delta, extending as far west as Fish Creek and as far east as Pingok Island (BPXA, 1999). Pingok Island is about 24 km (15 mi) west of Northstar. The peak season for seal hunting is during the summer months, but some hunting is conducted on the landfast ice in late spring. In summer, boat crews hunt ringed, spotted and bearded seals (BPXA, 1999). Thus, it is unlikely that construction activity will have a significant negative impact on Nuiqsut seal hunting. </P>
                    <HD SOURCE="HD2">Oil Spill Impacts </HD>
                    <P>
                        Oil spills have the potential to affect the hunt for bowhead whales. While oil spills from production drilling or pipelines could occur at any time of the year, NMFS believes that only if a significant spill occurred just prior to or during the subsistence bowhead hunt and spread into offshore waters would a reduction in the availability of bowhead whales for subsistence uses be possible. While unlikely, oil spills could extend into the bowhead hunting area under certain wind and current conditions. BPXA (1999) states that even in the event of a major spill, it is unlikely that more than a small number of those bowheads encountered by hunters would be contaminated by oil. However, disturbance associated with reconnaissance and cleanup activities could affect bowhead whales and, thus, accessibility of bowheads to hunters. As 
                        <PRTPAGE P="34028"/>
                        a result, in the unlikely event that a major oil spill occurred during the relatively short fall bowhead whaling season, it is possible that bowhead whale hunting could be significantly affected. Moreover, even with no more than a negligible impact on those marine mammals that would be subject to subsistence hunting, individuals and communities as a whole, may perceive that the whale or seal meat or products are tainted or somehow unfit to eat or use. This could further impact subsistence hunting of these animals. However, NMFS believes that because (1) the probability of a large oil spill is less than 10 percent over the 20-30 years of Northstar operations, (2) bowhead whales in the vicinity of Northstar and hunted only in the months of September and October, limiting exposure time, (3) only under certain wind and sea conditions would it be likely that oil would reach the bowhead subsistence hunting area, (4) there will be an oil spill response program in effect that will be as effective as possible in Arctic waters, and (5) other mitigation measures have been suggested in the event that oil did contact bowheads, NMFS has determined that the construction and operation at Northstar is unlikely to result in an unmitigable adverse impact on subsistence uses of marine mammals during the period of these regulations. However, NMFS will continue to assess this determination as monitoring and mitigation measures are incorporated and improved through experience and as additional offshore developments are proposed. NMFS may revise or clarify its determinations during these rulemakings. 
                    </P>
                    <HD SOURCE="HD1">Impacts on Habitat </HD>
                    <P>Invertebrates and fish, the nutritional basis for those whales and seals found in the Beaufort Sea, may be affected by construction and operation of the Northstar project. Fish may react to noise from Northstar with reactions being quite variable and dependent upon species, life history stage, behavior, and the sound characteristics of the water. Invertebrates are not known to be affected by noise. Benthic invertebrates would be affected by island and pipeline construction and overburden placement on the seabottom. Fish may be temporarily or permanently displaced by the island. These local, short-term effects are unlikely to have an impact on marine mammal feeding, except on a very local scale. </P>
                    <P>In the event of a large oil spill, fish and zooplankton in open offshore waters are unlikely to be seriously affected. Fish and zooplankton in shallow nearshore waters could sustain heavy mortality if an oil spill were to remain within an area for several days or longer. These affected nearshore areas may then be unavailable for use as feeding habitat for seals and whales. However, because these seals and whales are mobile, and bowhead feeding is uncommon along the coast near Northstar, effects would be minor during the open water season. In winter, effects of an oil spill on ringed seal food supply and habitat would be locally significant in the shallow nearshore waters in the immediate vicinity of the spill and oil slick. However, effects overall would be negligible. </P>
                    <HD SOURCE="HD1">Mitigation Measures </HD>
                    <P>Several mitigation measures were proposed by BPXA to reduce harassment takes to the lowest level practicable and have been adopted, with modification, by NMFS. Additional measures may be added or modified in LOAs. Presently identified measures include: </P>
                    <P>(1) BPXA will begin winter construction activities in December. This will eliminate contact with lairs that are actively used as birthing lairs. Because it is still necessary to determine the number of structures impacted by winter construction, BPXA will survey the area(s) using trained dogs, to identify and avoid ringed seal structures by a minimum of 150 m (492 ft), if practicable. </P>
                    <P>(2) Other than work done on the primary ice roads, if construction activities are initiated in undisturbed areas BPXA will survey the area(s), using trained dogs, in order to identify and avoid ringed seal structures by a minimum of 150 m (492 ft); after March 20, activities should avoid, to the greatest extent practicable, disturbance of any located seal structure. </P>
                    <P>(3) During the open water season, BPXA will establish and monitor, during the daytime, a 190 dB re 1 μPa safety range for seals around the island for those construction activities with SPLs that exceed that level. Establishing the safety range will require the collection and analysis of sound attenuation in the waters of the Northstar site. </P>
                    <P>(4) While whales are unlikely to approach the island during impact hammering or other noisy activities, a 180 dB re 1 μPa safety zone will be established and monitored during daylight hours around the island. </P>
                    <P>(5) If any marine mammals are observed within their respective safety range, operations will cease until such time as the observed marine mammals have left the safety zone. </P>
                    <P>(6) Project scheduling indicates that impact hammering will not occur during the period for subsistence hunting of westward migrating bowhead whale. </P>
                    <P>(7) Helicopter flights to support Northstar construction will be limited to a corridor from Seal Island to the mainland, and, except when limited by weather, will maintain a minimum altitude of 1,000 ft (305 m). </P>
                    <P>
                        (8) Drilling activities will temporarily cease during the bowhead whale migration during the first year of drilling activity (
                        <E T="03">i.e.,</E>
                         September, 2001). 
                    </P>
                    <HD SOURCE="HD1">Monitoring Measures </HD>
                    <P>
                        A detailed description of BPXA's proposed monitoring program for implementation during the construction phase at Northstar can be found in both the revised BPXA application (BPXA, 1999) and revised Technical Monitoring Plan (LGL, LGL and Greeneridge, 1999). The open-water season portion of BPXA's May 6, 1999, monitoring plan was reviewed by scientists and others attending the annual open-water peer-review workshop held in Seattle on July 1, 1999. The Technical Monitoring Plan was revised to incorporate recommendations made during this meeting and submitted to NMFS on September 1, 1999. This document was provided to the public during the comment period on the proposed rule. Peer review on the on-ice portion of the plan was conducted on October 14-15, 1999. Recommendations from that workshop were incorporated into work conducted this past winter and will be incorporated, as appropriate, into future monitoring plans. A copy of the September 1, 1999, revised monitoring plan is available upon request (see 
                        <E T="02">ADDRESSES</E>
                        ). Peer review of technical plans for monitoring during production activities will be conducted at future peer review meetings. 
                    </P>
                    <P>A summary of marine mammal monitoring that will be conducted during Northstar construction this year is provided here. </P>
                    <P>
                        Monitoring will employ both marine mammal observations and acoustic measurements and recordings. During the open-water period, monitoring will consist of (1) acoustic measurements of sounds produced by construction activities through boat-based hydrophones, sonobuoys deployed by boat, and autonomous seafloor acoustic recorders; (2) observations of marine mammals (primarily seals) from an elevated platform on Seal Island, which will be made during periods with and without construction underway; and, (3) 
                        <PRTPAGE P="34029"/>
                        acoustic monitoring of the bowhead whale migration. Additional monitoring may be required by NMFS through the peer review workshops. 
                    </P>
                    <P>During the ice-covered season, BPXA proposes to continue an ongoing (since the spring, 1997) Before-After/Control-Impact Study on the distribution and abundance of ringed seals in relation to development of the offshore oil and gas resources in the central Beaufort Sea. Collection and analysis of data before and after construction is expected to provide a reliable method for assessing the impact of oil and gas activities on ringed seal distribution in the Northstar construction area. Other winter/spring monitoring will include (1) on-ice searches for ringed seal lairs in areas where construction starts in the mid-March through April period, (2) assessment of abandonment rates for seal holes, and (3) acoustic measurements of sounds and vibrations from construction. Additional monitoring may be required by NMFS through the peer review workshops. </P>
                    <P>NMFS expects that the technical monitoring plan for production will be submitted to NMFS later this year and subject to review by NMFS biologists and revised appropriately prior to implementation. </P>
                    <HD SOURCE="HD1">Reporting Measures </HD>
                    <P>BPXA is required to provide two reports annually to NMFS. The first report is due 90 days after either the ice roads are no longer usable or spring aerial surveys are completed, whichever is later. The second report is required to be forwarded to NMFS 90 days after the formation of ice in the central Alaskan Beaufort Sea prevents water access to Northstar. These reports must include the dates and locations of construction activities, details of marine mammal sightings, estimates of the amount and nature of marine mammal takes, and any apparent effects on accessibility of marine mammals to subsistence hunters. </P>
                    <P>A draft final technical report must be submitted to NMFS by April 1 of each year. The final technical report must fully describe the methods and results of all monitoring tasks and a complete analysis of the data. The draft final report will be subject to peer review before being finalized by BPXA. </P>
                    <HD SOURCE="HD1">Determinations </HD>
                    <P>NMFS has determined that the impact of construction and operation of the Northstar project in the U.S. Beaufort Sea will result in no more than a temporary modification in behavior by certain species of cetaceans and pinnipeds. During the ice-covered season, pinnipeds close to the island may be subject to incidental harassment due to the localized displacement from construction of ice roads, from transportation activities on those roads, and from construction and production activities at Northstar. As cetaceans will not be in the area during the ice-covered season, they will not be affected. </P>
                    <P>During the open-water season, the principal construction- and operations-related noise activities will be impact hammering, helicopter traffic, vessel traffic, and other general construction/production activity on Seal Island. Sheet-pile driving is expected to be completed prior to whales being present in the area. Sounds from construction/production activities on the island are not expected to be detectable more than about 5-10 km (3.1-6.2 mi) offshore of the island. Disturbance to bowhead or beluga whales by on-island activities will be limited to an area substantially less than that distance. Helicopter traffic will be limited to nearshore areas between the mainland and the island and is unlikely to approach or disturb whales. Barge traffic will be located mainly inshore of the whales and will involve vessels moving slowly, in a straight line, and at constant speed. Little disturbance or displacement of whales by vessel traffic is expected. While behavioral modifications may be made by these species to avoid the resultant noise, this behavioral change is expected to have no more than a negligible impact on the animals. </P>
                    <P>While the number of potential incidental harassment takes will depend on the distribution and abundance of marine mammals (which vary annually due to variable ice conditions and other factors) in the area of operations, because the activity is in shallow waters inshore of the main migration corridor for bowhead whales and far inshore of the main migration corridor for belugas, the number of potential harassment takings is estimated to be small. In addition, no take by injury and/or death is anticipated, and the potential for temporary or permanent hearing impairment will be avoided through the incorporation of the mitigation measures mentioned in this document. No rookeries, areas of concentrated mating or feeding, or other areas of special significance for marine mammals occur within or near the planned area of operations. </P>
                    <P>Because bowhead whales are east of the construction/production area in the Canadian Beaufort Sea until late August/early September, activities at Northstar are not expected to impact subsistence hunting of bowhead whales prior to that date. Appropriate mitigation measures to avoid an unmitigable adverse impact on the availability of bowhead whales for subsistence needs will be the subject of consultation between BPXA and subsistence users. </P>
                    <P>Also, while construction/production at Northstar has some potential to influence seal hunting activities by residents of Nuiqsut, because (1) the peak sealing season is during the winter months, (2) the main summer sealing is off the Colville Delta, and (3) the zone of influence from Northstar on beluga and seals is fairly small, NMFS believes that Northstar construction/production will not have an unmitigable adverse impact on the availability of these stocks for subsistence uses. </P>
                    <P>NMFS has determined that the potential for an offshore oil spill occurring is low (less than 10 percent over 20-30 years (Corps, 1999)) and the potential for that oil intercepting whales or seals is even lower (about 1.2 percent (Corps, 1999)). Because of this low potential and because of the seasonality of bowheads, NMFS has determined that the taking of marine mammals incidental to construction and operation at the Northstar oil production facility will have no more than a negligible impact on them. In addition, because there will be an oil spill response program in effect that will be as effective as possible in Arctic waters, and because other mitigation measures have been suggested in the event that oil did contact bowheads, NMFS has determined that there will not be an unmitigable adverse impact on subsistence uses of marine mammals. </P>
                    <HD SOURCE="HD1">Changes to the Proposed Rule </HD>
                    <P>In addition to the modifications made to the proposed rule as a result of comments discussed previously and corrections of minor typographical errors, the following amendments have been made to the document. </P>
                    <P>Section 216.207 has been amended to clarify that this paragraph is intended only for the initial submission of an application for an LOA, not for subsequent renewals. </P>
                    <P>Section 216.209(a)(2) has been amended to note the time needed for receipt of the monitoring reports required under 216.205. </P>
                    <HD SOURCE="HD2">ESA </HD>
                    <P>
                        On March 4, 1999, NMFS concluded consultation with the Corps on permitting the construction and operation at the Northstar site. The finding of that consultation was that construction and operation at Northstar is not likely to jeopardize the continued existence of the bowhead whale stock. 
                        <PRTPAGE P="34030"/>
                        No critical habitat has been designated for this species; therefore, none will be affected. Because issuance of a small take authorization to BPXA under section 101(a)(5) of the MMPA is a Federal action, NMFS has completed section 7 consultation on this action. The finding of this consultation was that the issuance of the authorization was unlikely to adversely affect the bowhead whale. 
                    </P>
                    <HD SOURCE="HD2">NEPA </HD>
                    <P>
                        On June 12, 1998 (63 FR 32207), the Environmental Protection Agency (EPA) noted the availability for public review and comment a DEIS prepared by the Corps under NEPA on Beaufort Sea oil and gas development at Northstar. Comments on that document were accepted by the Corps until August 31, 1998 (63 FR 43699, August 14, 1998). On February 5, 1999 (64 FR 5789), EPA noted the availability for public review and comment, a FEIS prepared by the Corps under NEPA on Beaufort Sea oil and gas development at Northstar. Comments on that document were accepted by the Corps until March 8, 1999. For information on obtaining a copy of the FEIS, please contact the Corps (see 
                        <E T="02">ADDRESSES</E>
                        ). Based upon a review of the FEIS, the comments received on the DEIS and FEIS, and the comments received during this rulemaking, NMFS has adopted the Corps FEIS and has determined that it is not necessary to prepare supplemental NEPA documentation. 
                    </P>
                    <HD SOURCE="HD1">Classification </HD>
                    <P>This action has been determined to be significant for purposes of Executive Order 12866. </P>
                    <P>Until these regulations are effective, BPXA cannot be issued an LOA authorizing takings incidental to construction and operation at Northstar. Therefore, since these regulations relieve a restriction on BPXA, the prohibitions on the issuance of an LOA, are not subject to a 30-day delay in effective date under 5 U.S.C. 553(d)(1). </P>
                    <P>The Chief Counsel for Regulation of the Department of Commerce certified, at the proposed rule stage, to the Chief Counsel for Advocacy of the Small Business Administration that this final rule will not have a significant economic impact on a substantial number of small entities within the meaning of the Regulatory Flexibility Act. This final rule will affect only one or two large oil producing companies which, by definition, are not small businesses. It will also affect a small number of contractors providing services related to monitoring the impact of oil development in the Beaufort Sea on marine mammals. Some of the affected contractors may be small businesses, but the number involved would not be substantial. Further, since the monitoring requirement is what would lead to the need for their services, the economic impact on them would be beneficial. For all the above reasons, a regulatory flexibility analysis is not required. </P>
                    <P>This final rule contains collection-of-information requirements subject to the provisions of the Paperwork Reduction Act (PRA). These requirements have been approved by OMB under control number 0648-0151, and include an application for an LOA, an interim report, and a final report. Other information requirements in the rule are not subject to the PRA since they apply only to a single entity and, therefore, are not contained in a rule of general applicability. </P>
                    <P>Notwithstanding any other provision of law, no person is required to respond to nor shall a person be subject to a penalty for failure to comply with a collection of information subject to the requirements of the PRA unless that collection of information displays a currently valid OMB control number. </P>
                    <P>
                        The reporting burden for the approved collections-of-information are estimated to be approximately 3 hours for an application for a LOA, and 80 hours each for interim and final reports. These estimates include the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection-of-information. Send comments regarding these burden estimates, or any other aspect of this data collection, including suggestions for reducing the burden, to NMFS and OMB (see 
                        <E T="02">ADDRESSES</E>
                        ). 
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 50 CFR Part 216 </HD>
                        <P>Exports, Fish, Imports, Indians, Labeling, Marine mammals, Penalties, Reporting and recordkeeping requirements, Seafood, Transportation.</P>
                    </LSTSUB>
                    <SIG>
                        <DATED>Dated: May 18, 2000. </DATED>
                        <NAME>Penelope D. Dalton, </NAME>
                        <TITLE>Assistant Administrator for Fisheries, National Marine Fisheries Service. </TITLE>
                    </SIG>
                    <REGTEXT TITLE="50" PART="216">
                        <AMDPAR>For reasons set forth in the preamble, 50 CFR part 216 is amended as follows: </AMDPAR>
                        <PART>
                            <HD SOURCE="HED">PART 216—REGULATIONS GOVERNING THE TAKING AND IMPORTING OF MARINE MAMMALS </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 216 continues to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                16 U.S.C. 1361 
                                <E T="03">et</E>
                                  
                                <E T="03">seq</E>
                                .
                            </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="50" PART="216">
                        <AMDPAR>2. Subpart R is added to part 216 to read as follows: </AMDPAR>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart R—Taking of Marine Mammals Incidental to Construction and Operation of Offshore Oil and Gas Facilities in the U.S. Beaufort Sea </HD>
                        </SUBPART>
                        <CONTENTS>
                            <SECHD>Sec.</SECHD>
                            <SECTNO>216.200</SECTNO>
                            <SUBJECT>Specified activity and specified geographical region. </SUBJECT>
                            <SECTNO>216.201</SECTNO>
                            <SUBJECT>Effective dates. </SUBJECT>
                            <SECTNO>216.202</SECTNO>
                            <SUBJECT>Permissible methods of taking. </SUBJECT>
                            <SECTNO>216.203</SECTNO>
                            <SUBJECT>Prohibitions. </SUBJECT>
                            <SECTNO>216.204</SECTNO>
                            <SUBJECT>Mitigation. </SUBJECT>
                            <SECTNO>216.205</SECTNO>
                            <SUBJECT>Measures to ensure availability of species for subsistence uses. </SUBJECT>
                            <SECTNO>216.206</SECTNO>
                            <SUBJECT>Requirements for monitoring and reporting. </SUBJECT>
                            <SECTNO>216.207</SECTNO>
                            <SUBJECT>Applications for Letters of Authorization. </SUBJECT>
                            <SECTNO>216.208</SECTNO>
                            <SUBJECT>Letters of Authorization. </SUBJECT>
                            <SECTNO>216.209</SECTNO>
                            <SUBJECT>Renewal of Letters of Authorization. </SUBJECT>
                            <SECTNO>216.210</SECTNO>
                            <SUBJECT>Modifications to Letters of Authorization. </SUBJECT>
                        </CONTENTS>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart R—Taking of Marine Mammals Incidental to Construction and Operation of Offshore Oil and Gas Facilities in the U.S. Beaufort Sea </HD>
                            <SECTION>
                                <SECTNO>§ 216.200</SECTNO>
                                <SUBJECT>Specified activity and specified geographical region. </SUBJECT>
                                <P>Regulations in this subpart apply only to the incidental taking of those marine mammal species specified in paragraph (b) of this section by U.S. citizens engaged in oil and gas development activities in areas within state and/or Federal waters in the U.S. Beaufort Sea specified in paragraph (a) of this section. The authorized activities as specified in a Letter of Authorization issued under §§ 216.106 and 216.208 include, but may not be limited to, site construction, including ice road and pipeline construction, vessel and helicopter activity; and oil production activities, including ice road construction, and vessel and helicopter activity, but excluding seismic operations. </P>
                                <P>(a)(1) Northstar Oil and Gas Development; and </P>
                                <P>(2) [Reserved] </P>
                                <P>
                                    (b) The incidental take by harassment, injury or mortality of marine mammals under the activity identified in this section is limited to the following species: bowhead whale (
                                    <E T="03">Balaena</E>
                                      
                                    <E T="03">mysticetus</E>
                                    ), gray whale (
                                    <E T="03">Eschrichtius</E>
                                      
                                    <E T="03">robustus</E>
                                    ), beluga whale (
                                    <E T="03">Delphinapterus</E>
                                      
                                    <E T="03">leucas</E>
                                    ), ringed seal (
                                    <E T="03">Phoca</E>
                                      
                                    <E T="03">hispida</E>
                                    ), spotted seal (
                                    <E T="03">Phoca</E>
                                      
                                    <E T="03">largha</E>
                                    ) and bearded seal (
                                    <E T="03">Erignathus</E>
                                      
                                    <E T="03">barbatus</E>
                                    ). 
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 216.201</SECTNO>
                                <SUBJECT>Effective dates. </SUBJECT>
                                <P>Regulations in this subpart are effective from May 25, 2000, until May 25, 2005. </P>
                            </SECTION>
                            <SECTION>
                                <PRTPAGE P="34031"/>
                                <SECTNO>§ 216.202</SECTNO>
                                <SUBJECT>Permissible methods of taking. </SUBJECT>
                                <P>(a) Under Letters of Authorization issued pursuant to §§ 216.106 and 216.208, the Holder of the Letter of Authorization may incidentally, but not intentionally, take marine mammals by harassment, injury, and mortality within the area described in § 216.200(a), provided the activity is in compliance with all terms, conditions, and requirements of the regulations in this subpart and the appropriate Letter of Authorization. </P>
                                <P>(b) The activities identified in § 216.200 must be conducted in a manner that minimizes, to the greatest extent practicable, any adverse impacts on marine mammals, their habitat, and on the availability of marine mammals for subsistence uses. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 216.203</SECTNO>
                                <SUBJECT>Prohibitions. </SUBJECT>
                                <P>Notwithstanding takings authorized by § 216.200 and by a Letter of Authorization issued under §§ 216.106 and 216.208, no person in connection with the activities described in § 216.200 shall: </P>
                                <P>(a) Take any marine mammal not specified in § 216.200(b); </P>
                                <P>(b) Take any marine mammal specified in § 216.200(b) other than by incidental, unintentional harassment, injury or mortality; </P>
                                <P>(c) Take a marine mammal specified in § 216.200(b) if such taking results in more than a negligible impact on the species or stocks of such marine mammal; or </P>
                                <P>(d) Violate, or fail to comply with, the terms, conditions, and requirements of the regulations in this subpart or a Letter of Authorization issued under § 216.106. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 216.204</SECTNO>
                                <SUBJECT>Mitigation. </SUBJECT>
                                <P>The activity identified in § 216.200(a) must be conducted in a manner that minimizes, to the greatest extent possible, adverse impacts on marine mammals and their habitats. When conducting operations identified in § 216.200, the mitigation measures contained in the Letter of Authorization issued under §§ 216.106 and 216.208 must be utilized. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 216.205</SECTNO>
                                <SUBJECT>Measures to ensure availability of species for subsistence uses. </SUBJECT>
                                <P>When applying for a Letter of Authorization pursuant to § 216.207, or a renewal of a Letter of Authorization pursuant to § 216.209, the applicant must submit a Plan of Cooperation that identifies what measures have been taken and/or will be taken to minimize any adverse effects on the availability of marine mammals for subsistence uses. A plan must include the following: </P>
                                <P>(a) A statement that the applicant has notified and met with the affected subsistence communities to discuss proposed activities and to resolve potential conflicts regarding timing and methods of operation; </P>
                                <P>(b) A description of what measures the applicant has taken and/or will take to ensure that oil development activities will not interfere with subsistence whaling or sealing; </P>
                                <P>(c) What plans the applicant has to continue to meet with the affected communities to notify the communities of any changes in operation. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 216.206</SECTNO>
                                <SUBJECT>Requirements for monitoring and reporting. </SUBJECT>
                                <P>(a) Holders of Letters of Authorization issued pursuant to §§ 216.106 and 216.208 for activities described in § 216.200 are required to cooperate with the National Marine Fisheries Service, and any other Federal, state or local agency monitoring the impacts of the activity on marine mammals. Unless specified otherwise in the Letter of Authorization, the Holder of the Letter of Authorization must notify the Administrator, Alaska Region, National Marine Fisheries Service, or his/her designee, by letter or telephone, at least 2 weeks prior to initiating new activities potentially involving the taking of marine mammals. </P>
                                <P>(b) Holders of Letters of Authorization must designate qualified on-site individuals, approved in advance by the National Marine Fisheries Service, to conduct the mitigation, monitoring and reporting activities specified in the Letter of Authorization issued pursuant to § 216.106 and § 216.208. </P>
                                <P>(c) Holders of Letters of Authorization must conduct all monitoring and/or research required under the Letter of Authorization. </P>
                                <P>
                                    (d) Unless specified otherwise in the Letter of Authorization, the Holder of that Letter of Authorization must submit interim reports to the Director, Office of Protected Resources, National Marine Fisheries Service, no later than 90 days after completion of the winter monitoring season (approximately September 15th), and 90 days after the open water monitoring season (approximately February 1
                                    <E T="51">st</E>
                                    ). This report must contain all information required by the Letter of Authorization. 
                                </P>
                                <P>
                                    (e) A draft annual comprehensive report must be submitted by May 1
                                    <E T="51">st</E>
                                     of the year following the issuance of a LOA; 
                                </P>
                                <P>(f) A final annual comprehensive report must be submitted within the time period specified in the governing Letter of Authorization. </P>
                                <P>(g) A final comprehensive report on all marine mammal monitoring and research conducted during the effective period of the regulations in this subpart must be submitted to the Director, Office of Protected Resources, National Marine Fisheries Service at least 240 days prior to expiration of these regulations or 240 days after the expiration of these regulations if renewal of the regulations will not be requested. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 216.207</SECTNO>
                                <SUBJECT>Applications for Letters of Authorization. </SUBJECT>
                                <P>(a) To incidentally take bowhead whales and other marine mammals pursuant to the regulations in this subpart, the U.S. citizen (see definition at § 216.103) conducting the activity identified in § 216.200, must apply for and obtain either an initial Letter of Authorization in accordance with §§ 216.106 and 216.208, or a renewal under § 216.209. </P>
                                <P>(b) The application for an initial Letter of Authorization must be submitted to the National Marine Fisheries Service at least 180 days before the activity is scheduled to begin. </P>
                                <P>(c) Applications for initial Letters of Authorization must include all information items identified in § 216.104(a). </P>
                                <P>(d) NMFS will review an application for an initial Letter of Authorization in accordance with § 216.104(b) and, if adequate and complete, will publish a notice of receipt of a request for incidental taking and, in accordance with Administrative Procedure Act requirements, a proposed amendment to § 216.200(a). In conjunction with amending § 216.200(a), the National Marine Fisheries Service will provide a minimum of 45 days for public comment on the application for an initial Letter of Authorization. </P>
                                <P>(e) Upon receipt of a complete application for an initial Letter of Authorization, and at its discretion, the National Marine Fisheries Service may submit the monitoring plan to members of a peer review panel for review and/or schedule a workshop to review the plan. Unless specified in the Letter of Authorization, the applicant must submit a final monitoring plan to the Assistant Administrator prior to the issuance of an initial Letter of Authorization. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 216.208</SECTNO>
                                <SUBJECT>Letters of Authorization. </SUBJECT>
                                <P>
                                    (a) A Letter of Authorization, unless suspended, revoked or not renewed, will be valid for a period of time not to exceed the period of validity of this subpart, but must be renewed annually 
                                    <PRTPAGE P="34032"/>
                                    subject to annual renewal conditions in § 216.209. 
                                </P>
                                <P>(b) Each Letter of Authorization will set forth: </P>
                                <P>(1) Permissible methods of incidental taking; </P>
                                <P>(2) Means of effecting the least practicable adverse impact on the species, its habitat, and on the availability of the species for subsistence uses; and </P>
                                <P>(3) Requirements for monitoring and reporting, including any requirements for the independent peer-review of proposed monitoring plans. </P>
                                <P>(c) Issuance and renewal of each Letter of Authorization will be based on a determination that the number of marine mammals taken by the activity will be small, that the total number of marine mammals taken by the activity as a whole will have no more than a negligible impact on the species or stock of affected marine mammal(s), and will not have an unmitigable adverse impact on the availability of species or stocks of marine mammals for taking for subsistence uses. </P>
                                <P>
                                    (d) Notice of issuance or denial of a Letter of Authorization will be published in the 
                                    <E T="04">Federal Register</E>
                                     within 30 days of a determination. 
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 216.209</SECTNO>
                                <SUBJECT>Renewal of Letters of Authorization. </SUBJECT>
                                <P>(a) A Letter of Authorization issued under § 216.106 and § 216.208 for the activity identified in § 216.200 will be renewed annually upon: </P>
                                <P>(1) Notification to the National Marine Fisheries Service that the activity described in the application submitted under § 216.207 will be undertaken and that there will not be a substantial modification to the described work, mitigation or monitoring undertaken during the upcoming season; </P>
                                <P>(2) Timely receipt of the monitoring reports required under § 216.205, and the Letter of Authorization issued under § 216.208, which have been reviewed by the National Marine Fisheries Service and determined to be acceptable, and the Plan of Cooperation required under § 216.205; and </P>
                                <P>(3) A determination by the National Marine Fisheries Service that the mitigation, monitoring and reporting measures required under § 216.204 and the Letter of Authorization issued under §§ 216.106 and 216.208, were undertaken and will be undertaken during the upcoming annual period of validity of a renewed Letter of Authorization. </P>
                                <P>(b) If a request for a renewal of a Letter of Authorization issued under §§ 216.106 and 216.208 indicates that a substantial modification to the described work, mitigation or monitoring undertaken during the upcoming season will occur, the National Marine Fisheries Service will provide the public a minimum of 30 days for review and comment on the request. Review and comment on renewals of Letters of Authorization are restricted to: </P>
                                <P>(1) New cited information and data that indicates that the determinations made in this subpart are in need of reconsideration, </P>
                                <P>(2) The Plan of Cooperation, and </P>
                                <P>(3) The proposed monitoring plan. </P>
                                <P>
                                    (c) A notice of issuance or denial of a Renewal of a Letter of Authorization will be published in the 
                                    <E T="04">Federal Register</E>
                                     within 30 days of a determination. 
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 216.210</SECTNO>
                                <SUBJECT>Modifications to Letters of Authorization. </SUBJECT>
                                <P>(a) In addition to complying with the provisions of §§ 216.106 and 216.208, except as provided in paragraph (b) of this section, no substantive modification (including withdrawal or suspension) to the Letter of Authorization by the National Marine Fisheries Service, issued pursuant to §§ 216.106 and 216.208 and subject to the provisions of this subpart shall be made until after notification and an opportunity for public comment has been provided. For purposes of this paragraph, a renewal of a Letter of Authorization under § 216.209, without modification (except for the period of validity), is not considered a substantive modification. </P>
                                <P>
                                    (b) If the Assistant Administrator determines that an emergency exists that poses a significant risk to the well-being of the species or stocks of marine mammals specified in § 216.200(b), a Letter of Authorization issued pursuant to §§ 216.106 and 216.208 may be substantively modified without prior notification and an opportunity for public comment. Notification will be published in the 
                                    <E T="04">Federal Register</E>
                                     within 30 days subsequent to the action. 
                                </P>
                            </SECTION>
                        </SUBPART>
                    </REGTEXT>
                </SUPLINF>
                <FRDOC>[FR Doc. 00-13184 Filed 5-24-00; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 3510-22-F </BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>65</VOL>
    <NO>102</NO>
    <DATE>Thursday, May 25, 2000</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="34033"/>
            <PARTNO>Part X</PARTNO>
            <PRES>The President</PRES>
            <EXECORDR>Executive Order 13157—Increasing Opportunities for Women-Owned Small Businesses</EXECORDR>
        </PTITLE>
        <PRESDOCS>
            <PRESDOCU>
                <EXECORD>
                    <TITLE3>Title 3—</TITLE3>
                    <PRES>
                        The President
                        <PRTPAGE P="34035"/>
                    </PRES>
                    <EXECORDR>Executive Order 13157 of May 23, 2000</EXECORDR>
                    <HD SOURCE="HED">Increasing Opportunities for Women-Owned Small Businesses</HD>
                    <FP>
                        By the authority vested in me as President by the Constitution and the laws of the United States of America, including the Small Business Act, 15 U.S.C. 631, 
                        <E T="03">et seq</E>
                        ., section 7106 of the Federal Acquisition Streamlining Act of 1994 (Public Law 103-355), and the Office of Federal Procurement Policy, 41 U.S.C. 403, 
                        <E T="03">et seq</E>
                        ., and in order to strengthen the executive branch's commitment to increased opportunities for women-owned small businesses, it is hereby ordered as follows:
                    </FP>
                    <FP>
                        <E T="04">Section 1.</E>
                        <E T="03"> Executive Branch Policy.</E>
                         In order to reaffirm and strengthen the statutory policy contained in the Small Business Act, 15 U.S.C. 644(g)(1), it shall be the policy of the executive branch to take the steps necessary to meet or exceed the 5 percent Government-wide goal for participation in procurement by women-owned small businesses (WOSBs). Further, the executive branch shall implement this policy by establishing a participation goal for WOSBs of not less than 5 percent of the total value of all prime contract awards for each fiscal year and of not less than 5 percent of the total value of all subcontract awards for each fiscal year.
                    </FP>
                    <FP>
                        <E T="04">Sec. 2.</E>
                        <E T="03"> Responsibilities of Federal Departments and Agencies.</E>
                         Each department and agency (hereafter referred to collectively as “agency”) that has procurement authority shall develop a long-term comprehensive strategy to expand opportunities for WOSBs. Where feasible and consistent with the effective and efficient performance of its mission, each agency shall establish a goal of achieving a participation rate for WOSBs of not less than 5 percent of the total value of all prime contract awards for each fiscal year and of not less than 5 percent of the total value of all subcontract awards for each fiscal year. The agency's plans shall include, where appropriate, methods and programs as set forth in section 4 of this order.
                    </FP>
                    <FP>
                        <E T="04">Sec. 3.</E>
                        <E T="03"> Responsibilities of the Small Business Administration.</E>
                         The Small Business Administration (SBA) shall establish an Assistant Administrator for Women's Procurement within the SBA's Office of Government Contracting. This officer shall be responsible for:
                    </FP>
                    <ST1>(a)</ST1>
                    <TXT>working with each agency to develop and implement policies to achieve the participation goals for WOSBs for the executive branch and individual agencies;</TXT>
                    <ST1>(b)</ST1>
                    <TXT>advising agencies on how to implement strategies that will increase the participation of WOSBs in Federal procurement;</TXT>
                    <ST1>(c)</ST1>
                    <TXT>evaluating, on a semiannual basis, using the Federal Procurement Data System (FPDS), the achievement of prime and subcontract goals and actual prime and subcontract awards to WOSBs for each agency;</TXT>
                    <ST1>(d)</ST1>
                    <TXT>preparing a report, which shall be submitted by the Administrator of the SBA to the President, through the Interagency Committee on Women's Business Enterprise and the Office of Federal Procurement Policy (OFPP), on findings based on the FPDS, regarding prime contracts and subcontracts awarded to WOSBs;</TXT>
                    <ST1>(e)</ST1>
                    <TXT>
                        making recommendations and working with Federal agencies to expand participation rates for WOSBs, with a particular emphasis on agencies in which the participation rate for these businesses is less than 5 percent;
                        <PRTPAGE P="34036"/>
                    </TXT>
                    <ST1>(f)</ST1>
                    <TXT>providing a program of training and development seminars and conferences to instruct women on how to participate in the SBA's 8(a) program, the Small Disadvantaged Business (SDB) program, the HUBZone program, and other small business contracting programs for which they may be eligible;</TXT>
                    <ST1>(g)</ST1>
                    <TXT>developing and implementing a single uniform Federal Government-wide website, which provides links to other websites within the Federal system concerning acquisition, small businesses, and women-owned businesses, and which provides current procurement information for WOSBs and other small businesses;</TXT>
                    <ST1>(h)</ST1>
                    <TXT>developing an interactive electronic commerce database that allows small businesses to register their businesses and capabilities as potential contractors for Federal agencies, and enables contracting officers to identify and locate potential contractors; and</TXT>
                    <ST1>(i)</ST1>
                    <TXT>working with existing women-owned business organizations, State and local governments, and others in order to promote the sharing of information and the development of more uniform State and local standards for WOSBs that reduce the burden on these firms in competing for procurement opportunities.</TXT>
                    <FP>
                        <E T="04">Sec. 4.</E>
                        <E T="03"> Other Responsibilities of Federal Agencies.</E>
                         To the extent permitted by law, each Federal agency shall work with the SBA to ensure maximum participation of WOSBs in the procurement process by taking the following steps:
                    </FP>
                    <ST1>(a)</ST1>
                    <TXT>designating a senior acquisition official who will work with the SBA to identify and promote contracting opportunities for WOSBs;</TXT>
                    <ST1>(b)</ST1>
                    <TXT> requiring contracting officers, to the maximum extent practicable, to include WOSBs in competitive acquisitions;</TXT>
                    <ST1>(c)</ST1>
                    <TXT>prescribing procedures to ensure that acquisition planners, to the maximum extent practicable, structure acquisitions to facilitate competition by and among small businesses, HUBZone small businesses, SDBs, and WOSBs, and providing guidance on structuring acquisitions, including, but not limited to, those expected to result in multiple award contracts, in order to facilitate competition by and among these groups;</TXT>
                    <ST1>(d)</ST1>
                    <TXT>implementing mentor-protege programs, which include women-owned small business firms; and</TXT>
                    <ST1>(e)</ST1>
                    <TXT>offering industry-wide as well as industry-specific outreach, training, and technical assistance programs for WOSBs including, where appropriate, the use of Government acquisitions forecasts, in order to assist WOSBs in developing their products, skills, business planning practices, and marketing techniques.</TXT>
                    <FP>
                        <E T="04">Sec. 5.</E>
                        <E T="03"> Subcontracting Plans.</E>
                         The head of each Federal agency, or designated representative, shall work closely with the SBA, OFPP, and others to develop procedures to increase compliance by prime contractors with subcontracting plans proposed under section 8(d) of the Small Business Act (15 U.S.C. 637(d)) or section 834 of Public Law 101-189, as amended (15 U.S.C. 637 note), including subcontracting plans involving WOSBs.
                    </FP>
                    <FP>
                        <E T="04">Sec. 6.</E>
                        <E T="03"> Action Plans.</E>
                         If a Federal agency fails to meet its annual goals in expanding contract opportunities for WOSBs, it shall work with the SBA to develop an action plan to increase the likelihood that participation goals will be met or exceeded in future years.
                    </FP>
                    <FP>
                        <E T="04">Sec. 7.</E>
                        <E T="03"> Compliance.</E>
                         Independent agencies are requested to comply with the provisions of this order.
                    </FP>
                    <FP>
                        <E T="04">Sec. 8.</E>
                        <E T="03"> Consultation and Advice.</E>
                         In developing the long-term comprehensive strategies required by section 2 of this order, Federal agencies shall consult with, and seek information and advice from, State and local governments, WOSBs, other private-sector partners, and other experts.
                    </FP>
                    <PRTPAGE P="34037"/>
                    <FP>
                        <E T="04">Sec. 9.</E>
                        <E T="03"> Judicial Review.</E>
                         This order is for internal management purposes for the Federal Government. It does not create any right or benefit, substantive or procedural, enforceable at law or equity by a party against the United States, its agencies, its officers, its employees, or any other person.
                    </FP>
                    <PSIG>wj</PSIG>
                    <PLACE>THE WHITE HOUSE,</PLACE>
                    <DATE>May 23, 2000.</DATE>
                    <FRDOC>[FR Doc. 00-13367</FRDOC>
                    <FILED>Filed 5-24-00; 8:45 am]</FILED>
                    <BILCOD>Billing code 3195-01-P</BILCOD>
                </EXECORD>
            </PRESDOCU>
        </PRESDOCS>
    </NEWPART>
</FEDREG>
