Page 28 - Highway Engineering Handbook Building and Rehabilitating the Infrastructure

ENVIRONMENTAL ISSUES 11

• Section 4(f) evaluation (if required)
• EA revisions (if required)
Purpose and Need for the Proposed Action. A succinct description of the purpose and
need for the proposed action should be provided at the beginning of the EA. The need for
the project should be based on an objective evaluation of current information and future
anticipated conditions. This section of the EA should identify the transportation problem(s)
or other needs which the proposed action is intended to address (40 CFR 1502.13). The sec-
tion should clearly demonstrate that a need exists and should define the need in terms
understandable to the general public. The statement of purpose and need will form the basis
for identifying of reasonable alternatives and in selecting a preferred alternative.
Consistent with joint FHWA and Federal Transit Administration (FTA) guidance
(July 23, 2003 Joint Memorandum from Mary E. Peters, administrator of FHWA and
Jennifer L. Dorn, administrator of FTA), the Purpose and Need Statement must be as con-
cise and understandable as possible. Although it serves as the cornerstone for the subse-
quent identification and evaluation of alternatives, it should not specifically discuss any
alternative or range of alternatives, nor should it be so narrowly drafted that it unreasonably
points to a single solution, thereby circumventing necessary environmental review before
a selection is made. In general, the “need” for an action should be defined as the trans-
portation system deficiencies that will be addressed by the action, while the “purpose” for
the action should be described as the objectives that will be met to address the deficiencies.
Table 1.4 identifies the types of information that could be incorporated into the EA to
demonstrate the need for a proposed action.
Project Description and Alternatives. Included in this section of the EA should be a
project description written in clear, nontechnical language. It should include the location
and geographic limits of the project and its major design features and typical sections; a
location map (district, regional, county, or city map depicting state highways, major roads,
and well-known features to orient the reader to the project location); a vicinity map

TABLE 1.4 Information to Establish Need for Highway Projects

Project status: Briefly describe the project history including actions taken to date, other agencies
and governmental units involved, action spending, schedules, etc.
System linkage: Is the proposed project needed as a “connecting link”? How does the project fit in
the transportation system?
Capacity: Is the capacity of an existing facility inadequate for the present and projected traffic?
Would the proposed project provide needed additional capacity? What is the level(s) of service for
existing and proposed facilities?
Transportation demand: Is the project identified in an adopted statewide or metropolitan
transportation plan as needed to meet current or projected demand?
Legislation: Is there a federal, state or local governmental mandate for the action?
Social demands or economic development: Is the project needed to address projected economic
development or changes in land use?
Modal interrelationships: Is the proposed project needed to interface with and complement airports,
rail and port facilities, or mass transit services?
Safety: Is the proposed project needed to correct an existing or potential safety hazard? Is the
existing accident rate excessively high compared to that of similar facilities in the region or state?
Roadway deficiencies: Is the proposed project needed to correct existing roadway deficiencies (e.g.,
substandard geometrics, load limits on structures, inadequate cross-section, or high maintenance costs)?