ODOT Programmatic ESA Consultation on the Federal-Aid Highway Program (FAHP) User’s Guide...

ODOT Programmatic ESA Consultation on the Federal-Aid Highway Program (FAHP)User’s Guide Training, June-July 2013

When a new project begins early coordination, the project proponent (REU or local agency) will alert project stakeholders via E-mail regarding:

• Project Name

• Key #

• Location

• General concept of project with anticipated activities that may affect species - e.g., turning lane project with new impervious surface area

• Anticipated dates for key project milestones - e.g., DAP, PS&E, Bid-let- As best as known at time of Initiation

Information for FAHP Project Information for FAHP Project InitiationInitiation

(0)


Project NotificationProject Notification• It’s a process, not just a form• Timing based on FHWA requirements for

NEPA approval (e.g., CE Close-out Report)• Begin Notification process about 12-weeks

prior to deadline for NEPA approval– Local agency should get REU review before this– “Easy” projects may take less time, complex

projects or if new to the FAHP may need more– FHWA review 2-4 weeks– NMFS review likely 2-8 weeks

• Range depends on complexity and allows for requests for additional information


Project Notification (cont.)Project Notification (cont.)• Activities NOT Requiring Services

Approval– Meet in-water work period(s)– Manual weed control or meets standards (pg 40)– Bridge replacement that meets fluvial performance and

pile driving hydroacoustic standards (pgs 25,36)– No stream channel or waterway enhancements, or

meet standards (pg 28) – Stormwater flow management in drainage basins larger

that 100 mi2 & meets standards (pg 18) – None or only minor modifications to buffer distances,

riparian habitat impacts• minor modifications must be described in the Project

Notification, including justification for lack of adverse impacts

Page references are for May 2013 User’s Guide


SeeUser’s Guide pg 5


Project Notification (cont.)Project Notification (cont.)• Activities Requiring Services Approval

– Actions with required mitigation (pg 17)– In-water work extension– Fisheries restoration– Weed control that does not meet standards (pg40) – Blasting in/near aquatic habitats

• only allowed when listed species will not be present

– Bridge replacement cannot meet fluvial performance or pile driving hydroacoustic standards (pgs 25,36)

– Stream channel or waterway enhancements does not meet standards (pg 28)

– Flow management in a drainage basin < 100 mi2– Other modifications to FAHP design standards that may

result in direct impacts to listed aquatic resources


Project Notification (cont.)Project Notification (cont.)• Check FAHP Website for current template• Attachments? (see pg 11, Table 4)

• Quality Control– Check completeness & math; check consistency among

Project Activities, Description, Stormwater Management, Habitat Effects, Attachments

– Check latest Summary of Take (FAHP website)

• Create Project ftp folder • Electronic signatures (Biologist, Constr.

Project Manager, REU Manager)– See Append. 4 for digital signature instructions

Page & Append. references are for May 2013 User’s Guide


Project Notification (cont.)Project Notification (cont.)• Upload completed Notification Report to

Project’s ftp folder• REU transmits Notification to FHWA

– E-mail notice to Region FHWA Op. Engineer– link Project’s ftp folder– cc FAHP Project stakeholders– See Append. 5 for E-mail content– Must include early coordination information

• All Notifications require review/approval by FHWA


Project Notification (cont.)Project Notification (cont.)FHWA Operations Engineer’s “duties”:

– Review for FAHP scope, not an exclusion– Ensure sufficient early coordination – When approved, digitally sign– If No Services Approval:

• save as “FINAL”, upload to ftp• e-mail transmittal “TO” REU, cc stakeholders & NMFS

liaison

– If Services Approval:• save as “TO_SERVICES”, upload to ftp• E-mail transmittal “TO” NMFS liaison for review and

approval, cc stakeholders

– See Append. 5 for E-mail content


Project Notification (cont.)Project Notification (cont.)NMFS Liaison “duties”:

– If No Services Approval, review only• If disagree, coordinate with NRU first to

determine recourse

– If Services Approval:• Coordinate technical review by NMFS specialists,

as applicable• Coordinate digital signature and approval from

Branch Manager• Save as new file (“FINAL”), upload to ftp• E-mail notice to FHWA, cc stakeholders


Project Notification (final steps)Project Notification (final steps)REU’s final “duties”:• Ideally, within 2 weeks of final approval• Save copy of “approval” E-mail(s), upload

to Project’s ftp folder• Delete older versions of Notification form

so that ftp folder only has “FINAL”• Check FAHP projects map

– coordinate with NRU if status not updated, other information not correct


Illustration by Joseph Tomelleri

ODOT Programmatic ESA Consultation on the Federal-Aid Highway Program (FAHP) User’s Guide...

Documents

Transcript of ODOT Programmatic ESA Consultation on the Federal-Aid Highway Program (FAHP) User’s Guide...