Section 500 - Process for Class II Projects

Section 510.00 - Overview

Transportation projects in Idaho are typically reviewed as NEPA Class II Categorical Exclusions (CE). Since this Classification is the most common for ITD projects, this chapter provides guidance for the efficient methodology to process the CEs. Most of the information found in this chapter is included elsewhere in the Environmental Process Manual (EPM) but this concise chapter will serve as a quick reference for most of the issues arising from a CE environmental clearance.

510.01 Abbreviations and Acronyms.

CE	Categorical Exclusion
EE	Environmental Evaluation
EPM	Environmental Process Manual
ITD	Idaho Transportation Department
NEPA	National Environmental Policy Act
NOAA	National Oceanic and Atmospheric Administration
USFWS	United States Fish and Wildlife Service

Section 520.00 - Standards

There are no statutorial regulations for CE format or content. The standards and format presented here have been agreed upon by ITD, FHWA and the various resource agencies involved. The primary goals in preparing the CE package are consistency, accuracy, clarity and brevity.

Consistently following a set format will lead to greater efficiency in preparation and greater confidence in the document by the reviewers. Eliminating extraneous material and summarizing the pertinent information in the narrative will simplify the document, save file space and speed up review. Being precise in descriptions will end confusion in what is being proposed and the impacts of the proposal.

Section 530.00 - Format Guidance

530.01 Purpose and Need. The first step in the process is to establish Purpose and Need. The fundamental legal guidance on Purpose and Need Statements comes from the NEPA CEQ regulation, Section 1502.13—the Purpose and Need Statement “shall briefly specify the underlying purpose and need to which the agency is responding in proposing the alternatives including the proposed action.” This is generally completed in advance of the EE preparation but it should be continually visited throughout the project development and into the final EE package preparation. Without a firm understanding of the project purpose and why the project is needed, the various aspects of the project documentation will be chaotic.

Very basically describe the purpose for the action. This statement should reflect what is checked in the Project Purpose and Benefits section of the ITD 654 and 651 forms and also match what is described in the Concept Report. Pay particular attention to this issue as the project may evolve from the time the Concept Report is first drafted to the time the Environmental Evaluation package is prepared.

530.01.01 Purpose Statement. The Purpose statement does not describe any construction methods. Describe the project purpose in general terms such as to improve safety, or improve traffic flow or capacity from point A to point B, etc. The statement covers the final goal of the project and is intentionally more global in concept than is the project description. This lack of detail is intentional so as not to predetermine an alternative if more than one alternative is available. Describing where the project is to be constructed or how it is to be constructed is an automatic predetermination of what the project will be.

Ø The Purpose is analogous to the problem. It is the “what” of the proposal.

Ø The Purpose should focus on the state transportation system. Other important issues to be addressed by the project such as local transportation systems, livability, and the environment should be identified as Goals and Objectives elsewhere in the narrative.

Ø The Purpose can be stated in a single sentence or at least a very short paragraph. The Purpose should be stated as the positive outcome that is expected. For example, the purpose is to reduce congestion in the interstate corridor from MP xxx.x to MP xxx.x.

Ø It should avoid stating a solution as a purpose, as in “the purpose of the project is to build a bypass”.

Ø Where appropriate, Purpose should be stated broadly enough so that more than one transportation mode can be considered and multi-modal solutions are not dismissed prematurely.

Ø The Purpose should be stated in a manner so that a list of intermediate steps could be posed as the solution, scaled to the needs of the community, if appropriate.

If the project is a grade separation or bridge replacement it will naturally be confined to a particular area. In a case of this type the Purpose statement still should be centered on concepts such as safety or traffic flow or some aspect of the transportation system that will be improved by the project, not the project itself.

530.01.02 Need. For the project should be a more lengthy statement. For example, describe the project need in terms of the number of accidents in a given segment or where the level of service at the intersection is D and should be B or flow can be increased to reduce air pollution if a curve is reduced or removed, etc. Here again the need statement does not describe construction methods. A Need statement will include some data such as traffic counts or accident statistics to verify why the project is needed.

Ø Need should establish the evidence that the problem does or will exist if projected population and planned land use growth are realized or maintenance cannot keep up with deterioration.

Ø Need should be factually and numerically based.

Ø Need should support the assertion made in the purpose statement. For example, if the purpose statement is based on safety improvements, the need statement should support the assertion that there is or will be a safety problem to be corrected.

530.01.03 Narrative. In the text of the narrative for the CE, construction methods are described in the Project Description statement. Project Purpose, Project Need and Project Description are three separate and unique statements. The project description statement should go into as much detail as necessary to present the reviewer with an accurate picture of what methods, sequences, materials and machinery will be used to complete construction. There should also be an indication of the seasonal timing and expected duration of the construction period.

530.02 ITD 654 Form. There are two versions of the ITD 654 form: 654 and 651 (\\HQGSSV01\Forms\ITDForms\0501-1000\0654.doc). The 651 is very similar to the 654 but it is intended as a draft to be included in the Concept Report, when planning the preliminary design and as a scoping tool when working with consultants. Including the 651 with the preliminary Concept Report or the preliminary design is of great help to anyone reviewing the project in the preliminary stages. Do not confuse the 654(a) with either of these forms. 654(a) is similar only in number and it is used to document the hazardous materials survey for the project.

Completing Form 654 is the second step for preparation of the EE package. Working from the top of the form downward: Fill in the first section including the Work Authority and Program Year. These are time saving devices for HQ reviewers after this form has left the district office. Fill in the blanks regarding project number and location and verify that the milepost numbers entered here are the same numbers that appear on the preliminary plan sheets and the Concept Report. Fill in the second section completely.

Be careful to check two boxes in the Air Quality section: one to signify Attainment/Non-attainment and one to signify Exempt/Non-exempt. In the Project Purpose and Benefits section, mark with a single mark all the items that apply to the project. Now, double mark the one item that is the primary purpose for the project. Go back and check the Purpose and Need Statement and verify that it agrees with what you have just checked.

For the Project Impact section of the 651 form, check all items that apply. At the beginning stages of the project, you may not be able to determine the exact nature of the impact or if there will even be an impact in any given category. If you are in doubt, check the Unknown box. This is a Draft form and the exact nature of the impacts will be determined by the upcoming evaluation of the impacts. If there is no impact, leave both boxes blank.

In the 651 it is very helpful to include a brief project summary in the Project Description space on the back side of the sheet. If this is a final 654 the project description will generally be included in the narrative. If a narrative is not included, such as in the case of some ITS signs or de-icing equipment, a brief paragraph on the 654 is very helpful to reviewers.

Note that the 27 items of concern do not have to be adversely or permanently impacted. Is there enough concern about the item to warrant additional discussion in the narrative text? If so, check the yes box. Construction noise is an impact in virtually all projects but it is not a permanent, adverse impact. It still should be checked. A bicycle path that links two previously un-connected paths or areas may very well constitute a change in Travel Patterns for cyclists. If so, it should be checked. Any item that is impacted by the project must be checked and if the project would normally impact an item, but in this case does not, check the yes box and explain in the narrative why the expected impact does not occur.

Sign the form. The signature on the 651 means only that the signator has prepared the draft to the best of his/her knowledge of the project at that time. The signature on the 654 form carries more import and means the various categories have been studied and the impacts are as indicated.

Once the appropriate category surveys have been completed, the final 654 can be completed for inclusion in the EE. Fill the form out with the appropriate information and on the back page of the 654, check the appropriate items. A 654 being inserted into a final EE must be signed in both signatory blocks. If the signatures are unreadable, please print the name of the signator beneath the signature.

With the Purpose and Need and form 654 completed and in agreement, the basic foundation of the EE is formed. The package can be assembled in the following format.

530.03 Environmental Evaluation Format. (See Section 100.02)

Ø Title Page: Include Categorical Exclusion Approval Block for FHWA, or in the case of 23 C FR 771.117(c) projects, for ITD. Also include the project number, key number, date of preparation and county of location.

Ø Table of Contents: Even for small projects a table of contents can be helpful. Always number the pages of the main body of the document and include the numbers in the Table of Contents. If possible, consecutively number the entire document. If it is not practical to number the entire document, be sure all appendices are indicated in a manner that makes them easy to find and reference. Do not number each narrative section with its own page number sequence. Number the pages consecutively from the beginning of the narrative presentation to the end.

Ø State Location Map & Vicinity Sketch: Two maps are sufficient. One will show the general area of the project and the second will be of the project vicinity. If the area map is of such scale that it does not include any landmarks, it may be useless in depicting the general area. Also if it is of such a large area of the state that the project cannot be discerned, it may be useless. The vicinity map should cover the area of the project and enough local landmarks so there is no question as to the project location.

The maps must be of a quality that they can easily be read and the text and legend must be of a size that can be easily read.

Ø Project Area Photographs: Several (wide angle would be helpful) photos of the general habitat and topography in the project vicinity should be included. Include close up pictures of project components that may be an issue. For instance, if the project is a C.R.A.B.S. job with a culvert replacement there should be pictures of each end of the culvert and the area that will be disturbed by the replacement activity. If an eagle roost, perch or nest tree is going to be impacted by the project, include a photo showing the relationship of the tree to the project. Also mark this tree on the vicinity map or a separate project map. If there is an impact area that may be a questionable endangered plant habitat, include pictures of the area even though they should have been included in the BE/BA.

Ø ITD-654 Form, Environmental Evaluation: See discussion under section (B) above.

Ø Purpose & Need Description: See discussion under Purpose and Need above, Section (A).

Ø Project Description: Make certain that the project is adequately described. This includes, but is not limited to, the methods, materials and machinery, timing (time of year and length of time), sequence of operations, what will be removed, what will be replaced, how debris, dust and damage is controlled, etc. Many of the methods of construction and types of machinery may not be known until the contract is let and the contractor decides how he is going to approach the project. In the project description, provide as much information as you can expect to be reasonably accurate.

Ø Environmental Evaluation Narrative: This is the body of the EE. When describing the numbered items from the 654 form (and the project description), remember that this text is conveying a mental picture of the project to persons who have never seen the project and may have never seen the project area. Be clear, be concise and be accurate. Refer to the 654 form and start with ACRES OF NEW R/W. Draft a brief statement that explains why new R/W is needed and how much is needed. If new R/W is not needed then start with the first item that does involve the project.

Check provisions for bicycle and pedestrian use. Also check the bottom section of the 783a form in the concept report to be certain that the Design Section has acknowledged bicycles and pedestrians and that the Project description section of the EE text covers bicycle/pedestrian use.

This is the place to explain why some of the items are checked even though they may not have lasting adverse impacts. There may be construction noise but it can be mitigated by working only in daylight hours, not on weekends, having muffled engines, etc

In those areas where there may be impact or even substantial impact, expand the response to clearly explain what the impact is and why it cannot be avoided. Remember that none of the impacts can be significant. If there is a significant impact, the CE is inappropriate and an EIS must be prepared.

Cover all the items on the 654 form that have been checked yes as well as the items in the section under the project identification section. List them in sequence as they appear on the 654 form.

Explain why there is no impact when one would assume there would be an impact. For instance, addition of a passing lane in an area of Prime Farmland would indicate an impact to that farmland. Why is there no impact?

Ø Mitigation Plan Report: Prepare a page/section that lists all the mitigation from the narrative. This section must be complete and accurate and reflect all the mitigation that was approved in the FWS concurrence, Corp. of Engineers 404 permit and from any other resource agency that has commented on the evaluation. The Mitigation Plan will be inserted into the final contract and will become the point of reference the contractor and inspectors will use to make sure that the mitigation intended by the resource agencies will actually be installed on the earth.

Ø Public Involvement Summary (See Chapter 4 of ITD Guidebook to Public Involvement)

Ø Correspondence and Support Documentation: In this section include phone call logs, conversations, correspondence, etc. that is not contained in any of the supplemental reports referenced in the EE and that are important to the understanding of the EE conclusions.

Ø Discipline reports: Summarize the impacts and the body of the report in the narrative. Include the actual report as an attachment to the EE

Ø Summarized Concept Report (i.e., ITD-783, Draft Design Study Report Narrative, Vicinity Sketch, 783-A with Typicals, Traffic Data Request form, a Safety Evaluation when appropriate, and 783B). No plan sheets except Typicals are to be included. Concept Report materials are to determine if the project as described in the EE is consistent with what was proposed in the concept stage.

The EE package is not to be bound. Larger documents sometimes require binding to keep them manageable but no EE package should be that large. Keeping the textual portion to plus or minus twenty pages and attaching all discipline reports will allow the EE to remain concise. The reason for not binding is to eliminate the file space required for most binding. Large spiral bindings and. three ring binders require an inordinate amount of storage. A single spring clip in the upper left document corner keeps the document under control and does not require any file space.

For all documents except Categorical Exclusions, forward three copies to the HQ Environmental Section in care of the Environmental Section Manager. If the EE is acceptable, two copies will be forwarded to FHWA. For CEs, forward two copies to HQ and one will be forwarded to FHWA. If the document requires changes, try to accomplish the changes by E-mail to avoid the mail time between HQ and the District.

Section 540.00 - Technical Guidance

540.01 Discipline Reports. A Discipline Report is simply a convenient name for the various reports that all districts are currently preparing. For instance, a noise report, a wetland report, an EJ report are all Discipline Reports. The term is used in this manual to encompass the series of reports being discussed in a particular narrative instead of listing each report by name.

Discipline reports are typically prepared for District Offices by Consultants to document environmental studies and investigations. The reports form the basis for Categorical Exclusions, environmental documents such as EAs, EISs, and Section 4(f) evaluations. The reports describe the affected environment and detail the probable environmental impacts of project alternatives. They are used to help identify the least environmentally damaging alternative and provide information to others interested in the subject area.

The technical portion of the report provides evidence that all major potential impacts have been considered, presents information to support findings of significant impacts, and demonstrates clearly that the study is in compliance with the requirements of environmental law. Reports should only present factual data or expert opinion that is defensible in court. Once the report is written, the expert develops a summary that incorporates all the key areas pertinent to the discipline study. These summaries become the basic components of the environmental document.

540.02 Report Outline. After data has been collected, inventories compiled, and analyses completed, for each discipline, the consultant prepares a formal discipline report. All discipline reports are developed in a similar format so they can be easily adapted to the needs of the environmental document. Some Discipline Reports, such as a BE/BA (See Exhibit 1000-8) do have unique formats. Generally, discipline reports contain the following information but not necessarily in the same order:

Ø Background discussion on why the particular expertise area is critical to this project.

Ø Study methodology.

Ø Coordination with other groups or agencies.

Ø Affected environment (existing conditions).

Ø Summary of findings

Ø Predicted impacts of each alternative.

Ø Indirect impacts (when appropriate).

Ø Cumulative Impacts.

Ø Mitigation recommended for construction and operational impacts.

Ø Bibliography.

Each of the above topics should be addressed, but when information is brief, they may be combined. Before developing the report, the EIS or EA outline should also be reviewed, so significant details required for the environmental document are not overlooked.

Discipline reports are prepared so that field information can be presented in order to determine impacts and arrive at mitigation measures. The reports are not intended to be the definitive dissertation on the state of the discipline in science. For instance, a noise report does not have to begin with a complete section on what noise is and how we perceive noise. That basic knowledge is assumed. In a BE/BA it is not necessary to go into great depth on the description of the species. Here again, that basic knowledge is assumed. The discipline reports should be as concise as possible and still convey the detailed information on the impacts from the project and mitigation measures.

540.03 The BE/BA Clearance Process. The BE/BA is a collaborative effort between the district and USFWS and/or NOAA Fisheries (the Services). The process is actually a combination consultation/co-authorship/clearance effort with early and continual communication with the Services a vital component of successful completion of the consultation. For details of the complete consultation process.

To summarize the ESA consultation process, before any environmental field work is committed, the district should consult with the Services. If the district is comfortable that all listed species and critical habitat is not impacted by the project, a No Effect letter should be prepared for FHWA. Consult with the appropriate Operations Engineer at FHWA to determine that the No Effect letter is appropriate. No additional consultation with the Services is needed.

If May Affect, Not likely to Adversely Affect determinations appear likely, then with the consultant, contact the Services and discuss the project, the species list and the project probable projects impacts to determine the depth of information the Services will require for concurrence on the BE/BA.

Continue to be in contact with the Services during the preparation of the BE/BA. When the draft is complete to the satisfaction of the Services, send that completed BE/BA to ITD HQ for review. HQ will check for policy and mitigation compliance and forward the final BE/BA to the Services with a cover letter requesting concurrence.

The concurrence letter and two copies of the BE/BA will be sent to FHWA as part of the Environmental Evaluation.

If it is determined in the initial meetings with the Services or at any point in preparation of the BE/BA, that there is a May affect, likely to adversely affect determination, the draft BE/BA will be sent to ITD HQ and it will be sent to FHWA to request formal consultation with the Services.

The preparation of BE/BAs must also be re-examined by each district.

Rethink the need for BE/BAs. The general perception has been that any listed species occurring on a specific FWS list must be surveyed with a new, consultant prepared, BE/BA. This is not necessarily always true. Carefully consider your project and the impact it may have on species or habitat.

Ø If all the listed species and critical habitat can be covered with a No Effect determination, no BE/BA is needed.

Ø Use existing information in your files or from outside sources. If a project is being proposed in an area where a biological survey has been done in the recent past, build on that information, regardless of which agency prepared the information, and possibly eliminate the need for an additional BE/BA. An example is a recent bridge replacement project. Investigation shows that a recent EIS for a recreation area containing the project and a BE/BA for replacement of a boat ramp less than one hundred feet from the bridge replacement project had been completed by the Forest Service, with concurrence from FWS. That BE/BA and EIS are acceptable and current information that may have been used in lieu of a new BE/BA for the same species. Although the ITD project may have different impacts, the consultation could be built upon the avoidance, minimization, mitigation concept instead of rework all the background species and habitat information.

Ø Plan ahead. If a series of projects will be proposed for a concise geographic area, plan on doing a “batched” approach with one document instead of a BE/BA for each project. A batched BE/BA can be general for those species that will cover large areas of ground where the project is located. Where species are confined to smaller areas, the BE/BA will have to be more specific and cover each alternative in detail.

Ø A “no effect” call can be made in many instances but it is not always prudent. For instance, it may take substantial work by a consultant to prove that there is no population of a species in an area where habitat exists. If you are certain that your project will have little or no impact on the species or critical habitat, simply “assume presence” and offer mitigation if mitigation is appropriate and feasible. This does not require a consultant or a BE/BA. Mitigation is not always required. ESA does not require mitigation for every impact and NEPA requires that mitigation be only considered. If mitigation is appropriate, prepare to mitigate. If mitigation is very difficult to determine and would have little affect on a very small impact, don’t offer it and explain why it is not offered.

For instance, wolves, grizzly bears and lynx are wide ranging species that may from time to time travel across a project site area. It would be far easier to assume that the species may rarely traverse the site area and explain why the project will have no discernable impact than it would be to “prove” the species will never be in the area. This “May Effect, Not Likely to Adversely Effect” determination will require a general description of the habitat and the possible impacts.

Ø For projects that have multiple species with determinations of May Effect and No Effect,

Include the No Effect information in the BE/BA. If the determination is only No Effect, do not forward the No Effect statement to the Services but work directly with FHWA just as would be done with the Services.

Ø If there is no reasonable or feasible way to prepare mitigation measures and the impact is very small or nil, in the text of the BE/BA describe why there is a slight chance of impact, how small the impact would be if any, explain why mitigation is unreasonable or unfeasible and don’t offer any. You have considered mitigation and that is the basic requirement under NEPA. (see Exhibit 200.1, question 19)

Ø Look closely at your project to determine if you are not already offering mitigation as part of the project. Are you using BMPs that cut down erosion or dust? Are you avoiding additional impact by minimizing the project size? Is the construction window outside of the normal seasonal presence of the species? Does any aspect of the construction tend to avoid, minimize or enhance any part of the ambient habitat? These are all mitigations or compensations that may be admissible for the impact being described.

Ø Pay heed to historic range for endangered species. If the species has not been seen in your project area for 50 years but was once there, thoroughly document that fact, assume presence, and explain why no mitigation is being presented. However, for instance, if your project is in a historic Bull trout range and no trout has been seen there for 40 years because of a blocking culvert downstream, then a plan to retrofit or replace that culvert should be included in the project or a separate project should be instituted to rectify the culvert restrictions.

There is no checklist and there is no one and only way to meet the requirements for Section 7 compliance. Always consider a combination of project design features, alternative locations, construction periods, mitigation banking, and innovation when determining project impacts and avoidance.

Section 550.00 - Exhibits

Exhibit 500-1 Environmental Evaluation.

ITD 0654 (Rev. 12/02)

Date	District	Route #		City/County

Project Name					Project #		Key #

Work Authority			Program Year			Termini (Mp To Mp)

Acres of New Public R/W	Acres of New Private R/W		(Discuss the existing use of R/W to be acquired, plus adjacent land use, zoning, development plans, etc. on attached Environmental Summary Sheet)

TriBE/BAl Impact					Public Interest Expected?
FORMCHECKBOX Cultural FORMCHECKBOX Archeological FORMCHECKBOX Reservation FORMCHECKBOX None					FORMCHECKBOX Yes FORMCHECKBOX No
Air Quality
FORMCHECKBOX Attainment Area		FORMCHECKBOX Non-Attainment Area		FORMCHECKBOX CO FORMCHECKBOX PM Exempt Project FORMCHECKBOX Yes FORMCHECKBOX No
Type One Project (i.e., New Location, Substantial Alignment Change, Addition of a Through-Traffic Lane)						FORMCHECKBOX Yes FORMCHECKBOX No
Construction Impacts Requiring Special Provisions (Enter Details on Reverse Side )						FORMCHECKBOX Yes FORMCHECKBOX No
Program Year					Design Year
ADT FORMTEXT DHV FORMTEXT % Trucks FORMTEXT Posted Speed FORMTEXT					ADT DHV % Trucks Posted Speed
Distance of Nearest Noise Receptor to Centerline
Existing FORMTEXT Proposed FORMTEXT

Project Purpose and Benefits

Double mark (xx) only the item that best describes the Primary Reason for Proposing this Project Single mark (x) all Other Relevant Items
	Maintain/Improve User Operating Conditions	Enhance Accessibility for the Disabled/Safety
	Maintain/Improve Traffic Flow	Enhance Pedestrian Safety and/or Capacity
	Time Savings	Enhance Bicycle Safety and/or Capacity
	Increase Capacity	Traffic Composition Enhancement (e.g., Truck Route, HOV Lane, Climbing Lane)
	Reduce Congestion	Visual/Cultural Enhancement (e.g., Landscaping, Historic Preservation)
	Reduce Hazard(s)	Environmental Enhancement (e.g., Air Quality, Noise Attenuation, Water Quality)
	Reduce Highway User Operating Costs	Economic Prudence (e.g., Repair Less Expensive than Replacement, B/C Ratio)
	Other, List (e.g., Driver Convenience and Comfort regarding Rest Area Projects)

Check Any of the Following That Require Avoidance, Minimization, or Discussion (If Yes, describe in the Environmental Document or CE)

		Yes	No			Yes	No
1.	Noise Criteria Impacts*	FORMCHECKBOX	FORMCHECKBOX	17.	Threatened/Endangered Species*	FORMCHECKBOX	FORMCHECKBOX
2.	Change in Access or Access Control	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX Listed FORMCHECKBOX Proposed	FORMCHECKBOX	FORMCHECKBOX
3.	Change in Travel Patterns	FORMCHECKBOX	FORMCHECKBOX	18.	Air Quality Impacts	FORMCHECKBOX	FORMCHECKBOX
4.	Neighborhood or Service Impacts	FORMCHECKBOX	FORMCHECKBOX	19.	Inconsistent With Air Quality Plan	FORMCHECKBOX	FORMCHECKBOX
5.	Economic Disruption	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX SIP FORMCHECKBOX TIP
6.	Inconsistent W/Local or State Planning	FORMCHECKBOX	FORMCHECKBOX	20.	Stream Alteration/Encroachment**	FORMCHECKBOX	FORMCHECKBOX
7.	Minorities, Low Income Populations	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX IWDR FORMCHECKBOX F&G FORMCHECKBOX COE (404)
8.	Displacements*	FORMCHECKBOX	FORMCHECKBOX	21.	Flood Plain Encroachment*	FORMCHECKBOX	FORMCHECKBOX
9.	Section 4(f) Lands-DOT Act 1966*	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX Longitudinal FORMCHECKBOX Traverse
	(i.e., Public Parks/Rec Areas/Trails, Wildlife/Waterfowl Refuges, Wild or Scenic Rivers, Historic Sites/Bridges, Archaeological Resources			22.	Regulatory Floodway	FORMCHECKBOX	FORMCHECKBOX
					FORMCHECKBOX PE Cert. & FEMA Approval FORMCHECKBOX Revision
				23.	Navigable Waters**	FORMCHECKBOX	FORMCHECKBOX
10.	LWCF Recreation Areas/6(f) Lands*	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX CG (Sec 9) FORMCHECKBOX COE (Sec 10) FORMCHECKBOX Dept. Lands
11.	Section 106-Nat. Hist. Preserv. Act*	FORMCHECKBOX	FORMCHECKBOX	24.	Wetlands*	FORMCHECKBOX	FORMCHECKBOX
12.	FAA Airspace Intrusion**	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX Jurisdictional** (404) FORMCHECKBOX Non-Jurisdictional
13.	Visual Impacts	FORMCHECKBOX	FORMCHECKBOX	25.	Sole Source Aquifer	FORMCHECKBOX	FORMCHECKBOX
14.	Prime Farmland*, Parcel Splits	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX Exempt Project FORMCHECKBOX Non-Exempt**
15.	Known/Suspected "Hazmat" Risks	FORMCHECKBOX	FORMCHECKBOX	26.	Water Quality, Runoff Impacts	FORMCHECKBOX	FORMCHECKBOX
16.	Wildlife/Fish Resources/Habitat**	FORMCHECKBOX	FORMCHECKBOX	27.	NPDES-General Permit	FORMCHECKBOX	FORMCHECKBOX
					(If no, complete sediment-erosion control plan)

*If yes to these items, supplemental reports or documentation are required (e.g., Relocation Report; Wetlands Determination/Finding; Fish and Wildlife Species List Update; SCS Form AD-1006, Biological Assessment, etc.)

**If yes to these items, a letter of input is required from the appropriate agency.

Recommendation

FORMCHECKBOX A. The project does not individually or cumulatively have a significant adverse effect on the human environment
(Categorical Exclusion)	FORMCHECKBOX 23 CFR 771.117(c), i.e., Special and Programmatic
	FORMCHECKBOX 23 CFR 771.117(d), i.e., FHWA Approval
FORMCHECKBOX B. There is insufficient information to support A above or no precedent exists. (Environmental Assessment)
FORMCHECKBOX C. The project will result in a significant effect on the human environment. (Environmental Impact Statement)

Prepared By (Consultant, District Environmental Planner, or LHTAC Signature*)	Date

Reviewed By (District Environmental Planner, Project Development Engineer, or LHTAC Signature*)	Date

*One Signature by a Planner and one by Engineer or Consultant

Construction Impacts Requiring Special Provisions

FORMTEXT

___________________________________________________________________________________________________

_________

___________________________________________________________________________________________________

Exhibit 500-2 Conceptual Environmental Evaluation

ITD 0651 (Rev. 11/02)

Date	District	Route #		City/County

Project Name					Project #		Key #
					FORMTEXT		FORMTEXT
Work Authority			Program Year			Termini (Mp To Mp)
						FORMTEXT

Acres of New Public R/W	Acres of New Private R/W		Located on Indian Reservation, TriBE/BAl Lands, Etc.?
			FORMCHECKBOX Yes FORMCHECKBOX No
Air Quality
FORMCHECKBOX Attainment Area	FORMCHECKBOX Non-Attainment Area	FORMCHECKBOX CO FORMCHECKBOX PM 10 FORMCHECKBOX PM 2.5 FORMCHECKBOX Exempt Project
Type One Project (I.E., New Location, Substantial Alignment Change, Addition of a Through-Traffic Lane):
FORMCHECKBOX Yes FORMCHECKBOX No
Construction Impacts Requiring Special Provisions (Enter Details on Separate Sheet )
FORMCHECKBOX Yes FORMCHECKBOX No

Project Purpose and Benefits

Double mark (xx) only the item that best describes the Primary Reason for Proposing this Project Single mark (x) all Other Relevant Items
	Maintain/Improve User Operating Conditions	Enhance Accessibility for the Disabled/Safety
	Maintain/Improve Traffic Flow	Enhance Pedestrian Safety and/or Capacity
	Time Savings	Enhance Bicycle Safety and/or Capacity
	Increase Capacity	Traffic Composition Enhancement (e.g., Truck Route, HOV Lane, Climbing Lane)
	Reduce Congestion	Visual/Cultural Enhancement (e.g., Landscaping, Historic Preservation)
	Hazard Reduction	Environmental Enhancement (e.g., Air Quality, Noise Attenuation, Water Quality)
	Reduce Highway User Operating Costs	Economic Prudence (e.g., Repair Less Expensive than Replacement, B/C Ratio)
	Other, List (e.g., Driver Convenience and Comfort regarding Rest Area Projects)

Check Any of the Following That Are Adversely Impacted by the Project

		Yes	Unknown			Yes	Unknown
1.	Noise Criteria Impacts	FORMCHECKBOX	FORMCHECKBOX	18.	Air Quality Impacts	FORMCHECKBOX	FORMCHECKBOX
2.	Change in Access or Access Control	FORMCHECKBOX	FORMCHECKBOX	19.	Inconsistent With Air Quality Plan	FORMCHECKBOX	FORMCHECKBOX
3.	Change in Travel Patterns	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX SIP FORMCHECKBOX TIP
4.	Neighborhood or Service Impacts	FORMCHECKBOX	FORMCHECKBOX	20.	Stream Alteration/Encroachment	FORMCHECKBOX	FORMCHECKBOX
5.	Economic Disruption	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX IWDR FORMCHECKBOX F&G FORMCHECKBOX COE (404)
6.	Inconsistent W/Local or State Planning	FORMCHECKBOX	FORMCHECKBOX	21.	Flood Plain Encroachment	FORMCHECKBOX	FORMCHECKBOX
7.	Environmental Justice	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX Longitudinal FORMCHECKBOX Traverse
8.	Displacements	FORMCHECKBOX	FORMCHECKBOX	22.	Regulatory Floodway	FORMCHECKBOX	FORMCHECKBOX
9.	Section 4(f) Lands-DOT Act 1966	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX PE Cert. & FEMA Approval FORMCHECKBOX Revision
10.	LWCF Recreation Areas/6(f) Lands	FORMCHECKBOX	FORMCHECKBOX	23.	Navigable Waters	FORMCHECKBOX	FORMCHECKBOX
11.	Section 106-Nat. Hist. Preserv. Act	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX CG (Sec 9) FORMCHECKBOX COE (Sec 10) FORMCHECKBOX Dept. Lands
12.	FAA Airspace Intrusion	FORMCHECKBOX	FORMCHECKBOX	24.	Wetlands	FORMCHECKBOX	FORMCHECKBOX
13.	Visual Impacts	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX Jurisdictional (404) FORMCHECKBOX Non-Jurisdictional
14.	Prime Farmland, Parcel Splits	FORMCHECKBOX	FORMCHECKBOX	25.	Sole Source Aquifer	FORMCHECKBOX	FORMCHECKBOX
15.	Known/Suspected "Hazmat" Risks	FORMCHECKBOX	FORMCHECKBOX		FORMCHECKBOX Exempt Project FORMCHECKBOX Non-Exempt
16.	Wildlife/Fish Resources/Habitat	FORMCHECKBOX	FORMCHECKBOX	26.	Water Quality, Runoff Impacts	FORMCHECKBOX	FORMCHECKBOX
17.	Threatened/Endangered Species	FORMCHECKBOX	FORMCHECKBOX	27.	NPDES-General Permit	FORMCHECKBOX	FORMCHECKBOX
	FORMCHECKBOX Listed FORMCHECKBOX Proposed	FORMCHECKBOX	FORMCHECKBOX		(If no, complete sediment-erosion control plan)

Prepared By	Date

Comments