Site hosted by Angelfire.com: Build your free website today!
Blog Tools
Edit your Blog
Build a Blog
View Profile
« September 2024 »
S M T W T F S
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30
Entries by Topic
All topics
Announcements
City Council Resolution
Code of Virginia
Contracts
General Business
News Articles
Project Funding  «
Public Involvement
Purpose and Need
Steering Committee
Commonwealth of Virginia Links
Virginia Dept. of Transportation
Local Government Links
City of Charlottesville
Albemarle County
You are not logged in. Log in
STAMP-2025: Sensible Alternatives to the Meadow Creek Parkway
Thursday, 7 September 2006
FHWA responds to inquiry concerning project segmentation
Topic: Project Funding
Below is a copy of a letter from FHWA addressing concerns about project segmentation. I do not agree with parts of the analysis provided by FHWA and plan to respond to FHWA (and here) outlining these points. But, to provide information in a timely manner, I have posted the letter without comment at this time.


U S Department
of Transportation


Federal Highway
Administration

Virginia Division
(804)775-3320

 

August 31,2006

P.O. Box 10249
400 N. 8th Street Rm. 750
Richmond, Virginia 23240

 

IN REPLY REFER To:

Route 250 Bypass/McIntire
Road Interchange;
Charlottesville, Virginia

Mr. Peter Kleeman, Ph.D.
407 Hedge Street
Charlottesville, Virginia 22902

Dear Mr. Kleeman:

We are in receipt of your letter dated June 26, 2006, concerning the Route 250 Bypass/McIntire Road Interchange project being developed by the City of Charlottesville. In your letter, you raised questions about the Route 250 Bypass/McIntire Road Interchange project and the McIntire Road Extended/Meadow Creek Parkway project proceeding independently of one another in light of recent funding decisions made by the Commonwealth Transportation Board (CTB) in developing Virginia's Transportation Six-Year Improvement Program (Six-Year Program). You also cited FHWA's response dated April 4, 2005, to your previous inquiry, concluding that because the "criteria" addressed in that letter are no longer satisfied, the Route 250 Bypass/'McIntire Road Interchange project and the McIntire Road Extended/Meadow Creek Parkway project should be considered one integrated project.

In his recent conversation with you by telephone, Mr. Ken Myers mentioned that funding in the Six-Year Program was one way (and the simplest way) of demonstrating that the Route 250 Bypass/McIntire Road Interchange project and the McIntire Road Extended/Meadow Creek Parkway project are independent of one another. However, it is far from being the only way. By virtue of its inclusion in the United Jefferson Area Mobility Plan 2025 for construction, the Constrained Long Range Plan (CLRP) for the region, the McIntire Road Extended/Meadow Creek Parkway project is considered a committed project. When FHWA prepares a NEPA document, the no-build alternative is defined as all committed projects from the CLRP (i.e. those projects funded for construction) minus the project being subjected to NEPA. The Six-Year Program plays no role in defining the no-build alternative, and it has no standing with respect to FHWA's metropolitan or statewide planning requirements; instead, it is the CLRP that is the controlling document for determining whether or not a project is considered committed.

In addition, just because two related projects appear in the same funding document such as the Six-Year Program, this funding document does not dictate the scope of the project being analyzed for purposes of NEPA. In fact, when FHWA completes an environmental document in air quality attainment areas like Charlottesville, there is no regulatory requirement that the project be funded for any subsequent phases in the Transportation Improvement Program (TIP), CLRP, or Statewide TIP. Therefore, whether projects are funded for any phase beyond NEPA does not dictate the scope of a project for purposes of NEPA analysis in air quality attainment areas. Further, it is impractical to allow funding to play any role in the development of the scope of a project for purposes of NEPA analysis when those funding decisions can change annually. If we were to react to the CTB's decision to remove construction funding for the McIntire Road Extended/Meadow Creek Parkway project from the Six-Year Program by combining the Route 250 Bypass/Mclntire Road Interchange project and the McIntire Road Extended/Meadow Creek Parkway project into a single project for purposes of NEPA analysis, it logically follows that if the CTB were to put funding back into the Six-Year Program during the next allocation cycle, we would then have cause to separate the two projects again.

Neither does NEPA dictate the sequence in which projects are to be constructed. Even though we maintain our position that the McIntire Road Extended/Meadow Creek Parkway project remains a committed project by virtue of its inclusion in the CLRP, nothing requires VDOT to construct it in advance of the Route 250 Bypass/McIntire Road Interchange project. Notwithstanding, based on recent discussions with VDOT and the City of Charlottesville, it is their intent to advertise and construct both the McIntire Road Extended/Meadow Creek Parkway project and the Route 250 Bypass/Mclntire Road Interchange project at the same time to minimize disruption to the adjacent communities and the traveling public. Therefore, while funding to construct the McIntire Road Extended/Meadow Creek Parkway project is not currently included in the Six-Year Program, VDOT and the City are working to put the funding back into the Six-Year Program to complete the project on a timetable consistent with the schedule for the Route 250 Bypass/McIntire Road Interchange project.

In your letter you also made a couple of references to segmentation implying that FHWA, in proceeding with the Route 250 Bypass/McIntire Road Interchange project as a separate project in light of recent funding decisions by the CTB, is segmenting the interchange project from the McIntire Road Extended/Meadow Creek Parkway project. Segmentation occurs when a federal agency artificially divides a larger project into smaller projects with the intent of evading NEPA requirements such as the preparation of an Environmental Impact Statement. When the McIntire Road Extended project was developed in the early 1990s, it was developed with an at-grade intersection at the Route 250 Bypass demonstrating that the interchange was not needed for the extension to function properly in the design year of the extension. When FHWA issued a FONSI for the McIntire Road Extended project in 1995 before VDOT made a decision to fund the project with state funds, an interchange was not included as part of the improvement. Therefore, FHWA never segmented a larger project (i.e. the McIntire Road Extended project) by removing the interchange. It was only recently that an interchange project using federal funds was initiated, approximatdy 10 years after the FONSI for McIntire Road Extended was issued. In contrast, the McIntire Road Extended/Meadow Creek Parkway project is currently in the right-of-way acquisition/utility relocation phase. Besides, if FHWA were to add the Route 250 Bypass interchange to the McIntire Road Extended/Meadow Creek Parkway project, FHWA would merely re-evaluate the Environmental Assessment/FONSI that was already completed for the McIntire Road Extended project before it was de-federalized; we would not re-initiate the NEPA process all over again.

The principal issue here is whether a group of related actions constitute a single federal action for purposes of NEPA. While the McIntire Road Extended/Meadow Creek Parkway project is not considered a federal action that FHWA has jurisdiction over, FHWA has developed its own guidelines to follow when determining if segmentation is an issue related to a particular project, which takes into account court decisions on the matter. These guidelines, which are found in the 1993 paper titled Guidance on the Development of Logical Project Termini, address the concept of logical termini and independent utility. The concepts of logical termini and independent utility are closely tied to the purpose and need of a project. A review of the purpose and need for the McIntire Road Extended/Meadow Creek Parkway project demonstrates that it is fundamentally different than the purpose and need that is being developed for the Route 250 Bypass/McIntire Road Interchange project. If FHWA were to determine that the Route 250 Bypass/McIntire Road Interchange project was integral to whether or not the McIntire Road Extended/Meadow Creek Parkway project satisfied its purpose and need, then there would be cause to consider the two projects in a single NEPA document. However, the McIntire Road Extended/Meadow Creek Parkway project will serve its purpose and need whether or not the interchange is constructed. Accordingly, FHWA has determined that the Route 250 Bypass/McIntire Road Interchange project and the McIntire Road Extended/Meadow Creek Parkway project each have independent utility and the development of the former does not federalize the later.

In conclusion, FHWA has considered your concerns and not found cause to consider the Route 250 Bypass/McIntire Road Interchange project and the McIntire Road Extended/Meadow Creek Parkway project as a single project subject to NEPA. In other words, the development of the Route 250 Bypass/McIntire Road Interchange project does not federalize the non-federally funded McIntire Road Extended/Meadow Creek Parkway project. The funding decisions made by the CTB do not dictate the scope of a project being analyzed for purposes of NEPA, and projects included in a CLRP for construction are considered committed projects by FHWA. Finally, both the Route 250 Bypass/McIntire Road Interchange project and the McIntire Road Extended/Meadow Creek Parkway project have independent utility and will serve a purpose even if the other improvement isn't implemented. We hope you find this information and explanation helpful. If you have any additional questions or comments, please contact me at (804) 775-3338.

      Sincerely,

      Roberto Fonseca Martinez
      Division Administrator

      Signature: Edward Sundra

By: Edward Sundra
      Environmental Specialist, Sr.


posted by Peter T. Kleeman - techniquest@netscape.net

Posted by va3/stamp2025 at 10:37 AM EDT
Updated: Thursday, 7 September 2006 11:07 AM EDT
Permalink | Share This Post
Friday, 30 June 2006
Combining Route 250 Bypass/McIntire Road Interchange with Meadow Creek Parkway and McIntire Road Extended projects
Topic: Project Funding

Due to lack of funding in the Virginia FY07-12 Six-Year Improvement Program, it appears that the interchange project, the Meadow Creek Parkway, and the McIntire Road Extended projects should be combined into one project - if any of these projects are to receive Federal-aid Highway funds. Below is a letter sent to FHWA outlining the rationale for a request for combining these projects.
June 26, 2006

Mr. Kenneth Myers
Planning and Environment Team Leader
FHWA Virginia Division
400 North 8th Street
Richmond Virginia 23240
Dear Mr. Myers:

I reviewed your response to my April 4, 2005 inquiry (attached) concerning developing the Route 250 Bypass/ McIntire Road Interchange project independent of the Meadow Creek Parkway and McIntire Road Extended projects in light of recent decisions on transportation funding by the Commonwealth Transportation Board. Your response indicated that the federally funded Route 250 Bypass/ McIntire Road Interchange project would not federalize the Meadow Creek Parkway or McIntire Road Extended projects on the basis of those being fully funded in Virginia’s Six-Year Improvement Program and on that basis being considered a committed project. But now, neither of these two projects satisfies this criterion. It now appears inappropriate for the interchange to be an independent Federal-aid Highway project. I recommend that you re-coordinate these projects with VDOT as a single project if in fact federal funds are to be used in preliminary engineering, right-of-way acquisition, or construction of the interchange portion of this project.

The current FY 07-12 Six-Year Improvement Program provides no funding for either the Meadow Creek Parkway or the McIntire Road Extended project. Based on your criteria, it is clear that these two projects cannot be considered approved elements in the evaluation of future improvements. There is no commitment by the Commonwealth of Virginia to construct either the Meadow Creek Parkway or McIntire Road Extended. The current situation with only the interchange being developed as a Federal-aid Highway project appears not to be in compliance with established federal regulations and guidance on project segmentation.

Based on this lack of financial commitment by the Commonwealth of Virginia, it appears essential that the Route 250 Bypass/McIntire Road Interchange project, the Meadow Creek Parkway project, and the McIntire Road Extended project all be considered as one integrated project with logical termini located at Rio Road to the north, and U.S. Route 250 Bypass to the south. I believe that this combination of projects should be re-coordinated immediately with VDOT and the City of Charlottesville prior to further development of any of the project elements. The purpose and need for the combined project should also be reconsidered to reflect the regional need to meet projected traffic demand between growth areas in Albemarle County north and east of downtown Charlottesville. This combined project and the recently proposed Eastern Connector project should be considered alternatives for meeting this demand.

I look forward to hearing from you concerning this request to ensure that these projects are developed consistent with Federal-aid Highway program requirements, the National Environmental Policy Act (NEPA), and section 4(f) parkland protections for McIntire Park.

Sincerely,

signature: Peter Kleeman

Peter Kleeman

From: Myers, Kenneth [Kenneth.Myers@fhwa.dot.gov]
To: Peter T. Kleeman (E-mail) [techniquest@netscape.net]
Cc: Fonseca, Roberto [Roberto.Fonseca@fhwa.dot.gov]
Sent: Wed, 27 Apr 2005 13:10:19 -0400
Subject: RE: Designating Localities as Lead Agency for NEPA documentation

Mr. Kleeman:

Your inquiry of April 4 has been forwarded to me for response. We have reviewed the project status and coordinated with VDOT in preparing the attached response to address your two concerns.

Sincerely,

Kenneth R. Myers
Planning & Environmental Program Manager
FHWA, Virginia Division
(804) 775-3353
Kenneth.Myers@fhwa.dot.gov

-----Original Message-----
From: Peter T. Kleeman [mailto:techniquest@netscape.net]
Sent: Monday, April 04, 2005 10:37 AM
To: Fonseca, Roberto; philip.shucet@vdot.virginia.gov
Subject: Designating Localities as Lead Agency for NEPA documentation

Dear Sirs:

I have reviewed the "Agreement for Project Development and Administration by the City of Charlottesville Route 250 Bypass Interchange Project" and am concerned that the City of Charlottesville will apparently be acting as the lead agency in development of the NEPA document necessary for this project. I reviewed what appear to be the relevant sections of NEPA (Section 102) and 23 CFR 771 and believe that it is not legitimate for the City to be the lead agency for NEPA development. I am also concerned that the City of Charlottesville does not have the expertise in NEPA document development and related requirements including Section 4(f) analysis essential for this Federal-aid Highway project.

I also am concerned about treating the interchange and the portion of the Meadow Creek Parkway project through the McIntire Park (a section 4(f) protected property) as separate project with the NEPA document only considering the interchange. It is my understanding that Federal Court rulings have maintained that projects of this type cannot be segmented, but rather considered in one environmental document so that the full environmental impacts of the project are provided to the public for consideration.

I would very much like to receive from you justification for allowing the City of Charlottesville to be the lead agency for development of a NEPA document on any Federal-aid Highway project, and secondly, how the segmentation of this project is not in violation of Federal Court rulings against segmentation.

Sincerely,

Peter T. Kleeman

Response to Kleeman Inquiry

One of the concerns was that the project agreement between VDOT and the City of Charlottesville would have the City acting as lead agency under NEPA. This is a misunderstanding of the contract language. We have reviewed the language in the proposed, yet unexecuted, agreement and it in no way suggests that Charlottesville would act as lead agency. FHWA will act a lead agency for NEPA, and VDOT will retain appropriate NEPA oversight of the project as a responsible statewide agency. The agreement would allow the City to administer the project, a common arrangement that is utilized in many States.

In response to the second part of the inquiry, VDOT and FHWA have reviewed the status of the Meadowcreek Parkway and the U.S. 250 interchange at McIntire Road in Charlottesville. The purpose of this review was to determine if the new federally funded U.S. 250 interchange study would federalize the Meadowcreek Parkway. Our conclusion is that it would not, based on the following:

1) Proposed projects with location approvals and funding commitments may serve as logical termini for other projects that are being considered in the planning, feasibility or early preliminary engineering phases.

2) The Meadowcreek Parkway is a state funded project that has a location approval and is fully funded in the Working Draft FY06-11 SYIP. Right of Way is scheduled to begin in December this year, and construction is scheduled to begin in FY08.

3) The funded Meadowcreek Parkway project includes an at-grade intersection at the 250 Bypass.

4) Based on above items 1-3, it is appropriate to consider the Meadowcreek Parkway as an approved element of the transportation system in the evaluation of future improvements.

5) The Department is pursuing a separate project that will evaluate the construction of an interchange at the 250 Bypass, the existing at-grade intersection with McIntire Road and the terminus of the approved location Meadowcreek Parkway. This project was a new project in the current (FY05-10) program. The project was funded for PE only ($1.25M). There are no additional funds allocated to this project in the Working Draft FY06-11 SYIP (over the next 6 years).

6) When determining if the 250 Interchange has independent utility, we must determine if it is a useable and reasonable expenditure if no additional transportation improvements in the area are made. Since the Meadowcreek Parkway will be constructed regardless of whether the interchange moves forward, the interchange is an independent project.

7) Therefore, the federal action is limited to the federal-aid interchange and federal involvement with the interchange does not federalize the Meadowcreek Parkway.


posted by Peter T. Kleeman - techniquest@netscape.net

Posted by va3/stamp2025 at 11:33 AM EDT
Permalink | Share This Post
Tuesday, 21 February 2006
SAFETEA-LU Funding
Topic: Project Funding

Here are the sections of the most recent transportation legislation references to funding of the Meadowcreek Parkway Interchange in SAFETEA-LU (PL 109-59). It is interesting to note that the funding is designated for the Meadowcreek Parkway Interchange which is a clear link between this funding and the parkway project.

SEC. 1702. PROJECT AUTHORIZATIONS.

Subject to section 117 of title 23, United States Code, the amount listed for each high priority project in the following table shall be available (from amounts made available by section 1101(a)(16) f this Act) for fiscal years 2005 through 2009 to carry out each such project:

Highway Projects High Priority Projects
------------------------------------------------
No: 5044
State: VA
Project Description: Construct Meadowcreek Parkway Interchange, Charlottesville
Amount: $25,000,000
-------------------------------------------------

SEC. 1934. TRANSPORTATION IMPROVEMENTS.

(a) Authorization of Appropriations.--
(1) In general.--For each of fiscal years 2005 through 2009, there are authorized to be appropriated from the Highway Trust Fund (other than the Mass Transit Account) such sums as are necessary to make allocations in accordance with paragraph (2)to carry out each project described in the table contained in
subsection (c), at the amount specified for each such project in that table.
(2) Allocation percentages.--Of the total amount specified for each project described in the table contained in subsection c), 10 percent for fiscal year 2005, 20 percent for fiscal year 2006, 25 percent for fiscal year 2007, 25 percent for fiscal year 2008, and 20 percent for fiscal year 2009 shall be allocated to carry out each such project in that table.

(b) Contract Authority.--
(1) In general.--Funds authorized to be appropriated to carry out this subsection shall be available for obligation in the same manner as if the funds were apportioned under chapter 1 of title 23, United States Code, except that the funds shallremain available until expended.
(2) Federal share.--The Federal share of the cost of a project under this section shall be determined in accordance with section 120 of such title.

(c) Table.--The table referred to in subsections (a) and (b) is as follows:

Transportation Improvements
-------------------------------------------------
No: 408
State: VA
Project Description: Construct Meadowcreek Parkway Interchange, Charlottesville
Amount: $2,000,000
-------------------------------------------------


posted by Peter Kleeman - techniquest@netscape.net

Posted by va3/stamp2025 at 6:09 PM EST
Permalink | Share This Post
Friday, 18 November 2005
Reprogramming of
Topic: Project Funding


This just in from Rich Collins

On Nov. 17 the Washington Post reported that of the 6,000 plus "earmarked projects" in the transportation bill the so-called Bridge to Nowhere was eliminated along with another Alaskan pork barrel item but Alaska would keep the $600 plus million allocated for any project (including the earmarked project). This is interesting because it shows that even huge pork projects that are subject to political heat stay in the appropriation bill, and remain within the states that were the recipients.

It suggests to me that if the $27 million earmarked for the Route 250 Bypass/ McIntire Road Interchange project might be "earmarked" for the jurisdictions that received the earmarked funds. We need to let Butch Davies and others know that they should have a back-up position if they fail to get the interchange.

posted by Peter T. Kleeman - send comments to techniquest@netscape.net


Posted by va3/stamp2025 at 1:03 PM EST
Permalink | Share This Post

Newer | Latest | Older