02.01.2015 Views

Airport Master Plan 2012 - City of Waterville

Airport Master Plan 2012 - City of Waterville

Airport Master Plan 2012 - City of Waterville

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

As stated in the facility requirements, the present taxiway configuration at WVL is generally adequate to<br />

serve the present level <strong>of</strong> operational activity at the <strong>Airport</strong>. Runway 5-23 is served by a full-length<br />

parallel taxiway which allows for safe and efficient aircraft movement to and from Runway 5-23. The<br />

infrequent use <strong>of</strong> Runway 14-32 and the potential closure <strong>of</strong> Runway 14-32 in the future does not support<br />

a parallel taxiway alternative to Runway 14-32. However, there are a number <strong>of</strong> taxiway alternatives that<br />

could provide the <strong>Airport</strong> with more direct routes to airport facilities such as: The current Terminal Area,<br />

Aircraft Tie-Down Areas, Fueling Facilities, and Hangar Facilities.<br />

Regarding the present Taxiway configuration at WVL, if an aircraft is taxiing north on Taxiway „A”, with<br />

the current Hangar Area or the Terminal Facility Area as their destination, a nearly 135 degree left-hand<br />

turn onto taxiway “D” is required. From a planning and operational perspective, this current situation<br />

appears to be the most significant issue associated with the <strong>Airport</strong>‟s taxiway system.<br />

In order to provide the most direct routes as possible, to and from the Terminal area, as well as potential<br />

taxiways associated with the closure <strong>of</strong> Runway 14-32, Taxiway Alternatives include:<br />

T0: No-Build (Status Quo)<br />

T1a: Construct New Taxiway “E” that connects Taxiway “D” to Taxiway “A”<br />

See Figure T1a.<br />

T1b: Construct New Taxiway “E” that connects Taxiway “D” to Taxiway “A”<br />

See Figure T1b.<br />

T1c: Construct an extension <strong>of</strong> Taxiway “B” that connects it to Taxiway “D”<br />

See Figure T1c.<br />

T2: Should Runway 14-32 close permanently, use a portion <strong>of</strong> Runway 14-32 to create an<br />

additional stub taxiway between taxiways “B” and “C”.<br />

See Figure T2.<br />

T0: No Build (Status Quo)<br />

The no-build scenario will result in no enhancements to the current taxiway system. Aircraft travelling<br />

north on Taxiway “A” will continue to be required to make a sharp left turn should their destination be<br />

the current Terminal Area or the facilities adjacent to Taxiway “D”.<br />

T1a: Construct New Taxiway “E”<br />

Alternative T1a would eliminate the need for pilots exiting Runway 5-23 via Taxiway “B” to<br />

make the 135 degree turn onto Taxiway “D” that leads to the terminal area. Existing aircraft<br />

movements to or from the Runway 5 end to the terminal hangar area are inefficient and would be<br />

significantly improved with constructing a Taxiway “E”. The T1a alternative is most efficient<br />

should the <strong>Airport</strong> decide to construct Phase II <strong>of</strong> the Terminal Apron. As Figure T1a shows, this<br />

location <strong>of</strong> Taxiway “E” would provide for direct access to the Phase II Terminal Apron, however<br />

it does restrict future development along TW “D”.<br />

Since the Phase II Terminal Apron has already been designed to support Gulfstream type aircraft,<br />

constructing Taxiway “E” in this location would provide transient and corporate jet aircraft with<br />

convenient direct access to the Phase II parking area.<br />

Placing Taxiway “E” in this location would result in a 390 foot long taxiway.<br />

The <strong>City</strong> <strong>of</strong> <strong>Waterville</strong> Maine<br />

Alternatives Analysis – Page 4-4<br />

<strong>Airport</strong> Solutions Group, LLC & The Louis Berger Group, Inc. December 2011

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!