Laserfiche WebLink
<br />,,' <br /> <br />uaili~4 <br /> <br />Federal Register / Vol. 67, No, 235/ Friday, December 6, 2002/ Proposed Rules <br /> <br />72779 <br /> <br />FSH 1909,15. Whether a proposed <br />project is categorically excluded from <br />NEPA documentation, or is considered <br />in an EA or EIS depends upon whether <br />that project would have a significant <br />effect on the environment. <br />For those projects that the agency <br />believes there may be significant effects. <br />an EIS will be prepared to display those <br />effects. Pursuant to the FSH <br />requirements, EIS's are required for <br />actions in certain circumstances, for <br />example, herbicide application, or road <br />construction in an inventoried road less <br />area. In addition, the Forest Service <br />Iypically documents oilier types of <br />projects in an EIS. For example. large <br />timber sale projects are normally <br />documented in an EIS. Another example <br />of a type of project that may be <br />documented in an EIS would be an <br />approval of a plan of operation for a <br />large hard-rock mining operation. <br />The reason to do an EA is to <br />determine whether or not an EIS is <br />necessary and to document agency <br />NEPA compliance when an EIS is not <br />necessary. The EA will briefly provide <br />sufficient evidence and analvsis for <br />determining whether to prepare an EIS <br />or to reach a finding of no significant <br />impact for the proposed action. <br />Projects typically documented in an <br />EA are those projects that, at the time of <br />the proposal. the Forest Service believes <br />will not have significant environmental <br />effects. Examples of types of projects <br />typically documented in an EA include <br />smaller timber sale proiects, road <br />construction, campground construction. <br />special use authorizations, and fuels <br />reduction. <br />The FSH also lists categories of <br />actions that are excluded from NEPA <br />documentation because they do not <br />individually or cumulatively have a <br />significant effect on the human <br />elwironment and have been found to <br />hHV~ lIU such effect in procedures <br />adopted by the agency in <br />implementation of the regulations. <br />Existing categories include road <br />maintenance. administrative site <br />maintenance. or trail construction. <br />Whether a project is documented in <br />an EIS or an EA or whether it is <br />categorically excluded from NEPA <br />documentation, land and resource <br />management plan analyses will provide <br />critical baseline and trend data that will <br />inform the site-specific analysis for the <br />project. Project level NEPA <br />documentation will i3nalyze project <br />effects as needed. depending on the <br />nature of the project and the applicable <br />issues, and known information. Project <br />analyses will supplement and use <br />monitoring data, pertinent assessments, <br />inventories. research, and the plan <br /> <br />analysis information. This plan analysis <br />information will be available regardless <br />of whether the plan is documented in an <br />EA. EIS, or categorically excluded from <br />NEPA documentation. <br />Categorical exclusion for planning: H <br />this proposed rule is adopted. <br />conforming changes would be required <br />in FSH 1909.15, section 20.6. A new <br />categorical exclusion pertaining to <br />categories of plan decisions may be <br />adopted for plan decisions that do not <br />individually or cumulatively have a <br />significant effects on the human <br />environment and are found to have no <br />such effect by the agency based on the <br />implementation of this proposed rule. A <br />separate Federal Register notice would <br />be published to provide public notice of <br />the proposed category and request for <br />comment. <br />Public comment: The agency <br />recognizes that the manner in which the <br />proposed rule applies NEPA with <br />respect to new plans, plan amendments, <br />and plan revisions is a departure from <br />the approach taken in the 2000 rule and <br />the 1982 rule requiring an EIS for plan <br />revisions. significant amendments, or <br />new plans. This departure is based on <br />the agency's extensive experience with <br />land and resource management <br />planning over the years. That <br />experience indicates that attempting to <br />draw precise conclusions about the <br />environmental effects of plan direction <br />is subject to analytical uncertainty and <br />is ultimately of limited value for <br />purposes of informed decision-making <br />in compliance with NEPA. However, the <br />agency recognizes that some level of <br />NEPA documenta!ion for plan direction <br />is warranted. and that there may be <br />substantial disagreement over the extent <br />ofNEPA analvsis and documentation <br />that is appropriate. With this proposed <br />rule, the Forest Service is attempting to <br />strike an appropriate balance between <br />broad-scale plan-level analysis and <br />finer-scale project-level ani:tlysis with <br />sufficient inter-relationship between the <br />two to ensure NEPA compliance for all <br />decisions. Therefore. the Forest Service <br />specifically requests comments and <br />suggestions from the public regarding <br />how the "significance" of land and <br />resource management plan direction is <br />applied in this proposed rule, what plan <br />decisions authorize an action or commit <br />funding or resources that could have a <br />significant effecl on the environment <br />and the circumstances for which an EA <br />or ElS for a \,lan would be appropriate. <br />It is usefu to summarize the <br />differences between elements of NEPA <br />application in the 2000 rule and in this <br />proposed rule. This summary <br />consolidates discussion present in other <br />parts of this preamble. <br /> <br />Type of NEPA documentation: The <br />2000 rule requires preparation of an EIS <br />for a plan revision (36 CFR 219.9(d)). <br />The proposed rule states plans may be <br />categorically excluded from <br />documentation in an EA or EIS when <br />the Responsible Official determines that <br />the action fits an established Categorical <br />Exclusion category and no extraordinary <br />circumstances are present. <br />Public involvement: The 2000 rule has <br />detailed requirements on who should be <br />involved in planning (99219.13- <br />21g.17). The proposed fule has <br />essentially the same requirements, <br />altJlOugh they are more succinctly <br />stated. These requirements would still <br />apply for plans categorically excluded <br />from documentation in an EA or EIS. <br />The Forest Service will ensure that <br />categorically excluding land and <br />resource mani3gement plans from <br />documentation in an EA or EIS does not <br />result in an adverse or disproportionate <br />effect on groups of people identified <br />under Title VI of the Civil Rights Act, <br />the Executive Order 12898- <br />Environmental Justice or other civil <br />rights laws, regulations. and orders. <br />These identified groups include <br />minorities, seniors, women, subsistence <br />lifestyle populations. Tribes, and low <br />income populations. By definition in <br />NEPA, a categorical exclusion address <br />only those actions which do not <br />individually or cumulatively have a <br />significant effect on the human <br />environment and for which, therefore. <br />neither an EA nor an EIS is required (40 <br />CFR 1508.4). Pursuant to agency policy <br />set out in Forest Service Handbook <br />1909.15. Chapter 10, the Responsible <br />Official would still be required to <br />identify potentially affected and <br />interested agencies. organizations, and <br />individuals during the planning <br />process. regardless of which type of <br />documentation is used. Additionallv. <br />specific Forest Service guidance on- <br />scoping under NEPA will still apply to <br />categorical exclusions. <br />Issues: The 2000 rule has very <br />detailed requirements for issue <br />identification. The proposed rule does <br />not. While the proposed rule would still <br />require the Responsible Official to <br />document a rationale for issue <br />identification in the proposed rule. it is <br />likely that this documentation would be <br />briefer as he or she would not need to <br />cross reference an extensive list of issue <br />sources (refer to S 219.5 in this <br />preamble). The requirements in the <br />proposed rule for issue identification <br />would still apply for plans categorically <br />excluded from documentation in an EA <br />DrEIS, <br />Analysis: The 2000 rule contains very <br />detailed requirements for what can be <br />