TABLE OF CONTENTS
EXECUTIVE SUMMARY v
SECTION 1 - PROGRAM OVERVIEW Page 1-1
1.0 PROGRAM HISTORY Page 1-1
1.1 PROGRAM OVERSIGHT Page 1-2
1.2 PROJECT DEFINITIONS Page 1-3
1.3 LOCATION MAP Page 1-4
SECTION 2 - PROJECT PRIORITIZATION SYSTEM Page 2-1
2.0 BACKGROUND Page 2-1
2.1 PRIORITIZATION MODEL DEVELOPMENT Page 2-1
2.1.1 Goals. Page 2-1
2.1.2 Evaluation Criteria. Page 2-2
2.2 PROJECT EVALUATION WORKSHEETS. Page 2-7
SECTION 3 - PUBLIC INVOLVEMENT Page 3-1
3.0 PUBLIC INVOLVEMENT APPROACH Page 3-1
3.1 MEETING SUMMARIES Page 3-1
3.1.1 First Public Meeting. Page 3-1
3.1.2 Second Public Meeting. Page 3-3
3.1.3 Third Public Meeting. Page 3-5
3.1.4 Final Public Meeting. Page 3-7
SECTION 4 - AIRPORT CLASSIFICATION & DEVELOPMENT STANDARDS Page 4-1
4.0 INTRODUCTION Page 4-1
4.1 AIRPORT CLASSIFICATION Page 4-1
4.1.1. Existing Airport Classification Page 4-1
4.1.2. FAA NPIAS Classification Page 4-3
4.1.3. Other State Airport Classifications. Page 4-3
4.1.4. Recommended Vermont State Airport Classification Page 4-3
4.1.4.1 - Facility Use. Page 4-4
4.1.4.2 - Approach Category. Page 4-5
4.1.4.3 - Design Group. Page 4-5
4.2 VAOT AVIATION DEVELOPMENT STANDARDS Page 4-7
4.2.1. Aircraft Parking Aprons. Page 4-7
4.2.1.1. - Transient Apron. Page 4-7
4.2.1.2 - Based Aircraft Apron Page 4-8
4.2.1.3. - Aircraft Parking Apron Demand. Page 4-8
4.2.2. Hangar Demand. Page 4-10
4.2.3. Fueling Facilities. Page 4-10
4.2.4. Terminal/Administration Buildings. Page 4-11
4.2.5. Auto Parking. Page 4-12
4.2.6. Auto Access. Page 4-13
4.2.7. Airfield Navigational Aids. Page 4-13
4.2.7.1. - Visual Airport Navigational Aids. Page 4-15
4.2.7.2. - Non-Precision Airport Navigational Aids Page 4-15
4.2.8. Airport Instrument Approaches Page 4-15
4.2.9. Security Fencing Page 4-16
4.2.10. Taxiway Systems. Page 4-16
4.2.11. Current Airport Layout Plan Page 4-16
4.2.12. Americans with Disabilities Act (ADA) Compliance Page 4-16
4.2.13. Maintenance of Infrastructure Page 4-17
4.2.14. Airport Picnic Areas Page 4-17
4.3 FAA SAFETY STANDARDS Page 4-17
4.3.1. Aircraft Characteristics Page 4-17
4.3.1.1 - Aircraft Weight Page 4-17
4.3.1.2 - Airport Reference Code. Page 4-18
4.3.2. Runway Design Standards Page 4-18
4.3.2.1 - Runway Safety Area (RSA). Page 4-18
4.3.2.2 - Runway Protection Zone (RPZ Page 4-19
4.3.2.3 - Runway Object Free Area Page 4-19
4.3.2.4 - Controlled Activity Area Page 4-20
4.3.2.5 - Obstacle Free Zone Page 4-20
4.3.2.6 - Primary Surface. Page 4-20
4.3.2.7 - Obstacle Transition Surface. Page 4-21
4.3.2.8 - Runway Line of Sight Standards. Page 4-21
4.3.2.9 - Runway Threshold. Page 4-21
4.3.3 - Taxiway Design Standards Page 4-24
4.3.3.1 - Taxiway Safety Area (TSA) Page 4-25
4.3.3.2 - Distance from Taxiway Centerline Page 4-25
4.3.3.3 - Taxiway and Taxilane Object Free Area Page 4-25
4.3.4 Airport Safety Standard Summary Page 4-26
SECTION 5 - PROJECT EVALUATION Page 5-1
5.0 PROJECT RANKING METHODOLOGY Page 5-1
5.1 PLANNING LEVEL COST ESTIMATES Page 5-5
5.2 AVIATION CAPITAL PROJECT SUMMARY Page 5-5
SECTION 6 - FINANCIAL OVERVIEW Page 6-1
6.0 INTRODUCTION Page 6-1
6.1 VERMONT AVIATION BUDGET REQUEST COMPONENTS Page 6-1
6.2 TYPICAL FUNDING SOURCES Page 6-2
6.2.1. State-Owned Airports Funding. Page 6-2
6.2.2. Burlington International Airport Funding Page 6-4
6.2.3. Fair Haven Municipal Airport Funding Page 6-4
6.3 VERMONT AIRPORT CAPITAL FACILITY PROGRAM FUNDING Page 6-6
6.3.1. Annual Funding Requirements Page 6-7
SECTION 7 - UPDATING PROCEDURES Page 7-1
7.0 UPDATING OVERVIEW Page 7-1
7.1 PUBLIC NOTIFICATION Page 7-1
7.2 PUBLIC MEETING PREPARATION Page 7-5
7.2.1. Public Meeting Agenda Page 7-5
7.2.1.1 - Program Background And Overview. Page 7-7
7.2.1.2 - Project Prioritization Model. Page 7-7
7.2.1.3 - Overview of Airport Activity Levels. Page 7-7
7.2.1.4 - Review of 2000 Aviation Program. Page 7-7
7.2.1.5 - Draft 2001 Ranking of 5-year Aviation Program. Page 7-7
7.2.1.6 - Review of Airport Project Evaluations. Page 7-7
7.2.1.7 - Documentation of Local Support. Page 7-8
7.2.1.8 - Open Discussion. Page 7-8
7.2.2. Meeting Locations. Page 7-8
7.2.3. Record Keeping. Page 7-8
7.2.4. Draft Prioritization of Projects. Page 7-8
7.2.4.1 - Preliminary Ranking Meeting Page 7-9
7.2.4.2 - Meeting Minutes Page 7-10
7.2.4.3 - Computerized Data Entry. Page 7-10
7.3 COMMENT PERIOD Page 7-10
7.4 FINALIZATION OF PROJECT EVALUATIONS Page 7-10
7.5 PRESENTATION OF REVISED PROGRAM TO SAC Page 7-10
7.6 DISTRIBUTION OF PROJECT EVALUATION WORKSHEETS Page 7-10
7.7 ANNUAL PROGRAM FUNDING Page 7-11
SECTION 8 - COMPUTERIZED PRIORITIZATION MODEL Page 8-1
8.1 PRIORITIZATION MODEL OVERVIEW Page 8-1
8.2 PROJECT PRIORITY RANKING SCREEN Page 8-1
8.2.1 Airport Categories Page 8-1
8.2.1.1 Activity Page 8-2
8.2.1.2 Ratings Page 8-3
8.2.2 Project Categories Page 8-3
8.2.2.1 Project Selector Page 8-3
8.2.2.2 Project Information Page 8-4
8.2.2.3 Project Points Sub-Tabs Page 8-4
8.2.3 Project Totals and Report Page 8-5
8.2.4 Printing Summary Reports Page 8-6
8.2.5 Editing Category Parameters Page 8-7
APPENDIX A Page A-1
AIRPORT MEETING MINUTES Page A-1
APPENDIX B Page B-1
PROJECT EVALUATION WORKSHEETS - 0-5 YEAR PROGRAM Page B-1
APPENDIX C Page C-1
PROJECT EVALUATION WORKSHEETS - 0-20 YEAR PROGRAM Page C-1
APPENDIX D Page D-1
NPIAS ACIP STANDARD DESCRIPTIONS Page D-1
APPENDIX E Page E-1
BURLINGTON INTERNATIONAL AIRPORT SUMMARY OF CAPITAL IMPROVEMENT PROGRAMS Page E-1
APPENDIX F Page F-1
FAA ORDER 5100.38A Page F-1
EXECUTIVE SUMMARY
INSERT SEPARATE FILE
SECTION 1 - PROGRAM OVERVIEW
1.0 PROGRAM HISTORY
In 1997 the Vermont Legislature directed the Vermont Agency of Transportation (VAOT) to review its aviation funding policies and procedures, provide direction for public investment in airports, investigate underlying policy assumptions, and to identify steps to move toward a more intentional and targeted approach to improving air facilities. This request resulted in the preparation of the 1998 "Vermont Airport System Policy Plan." This plan identified a number of findings related to VAOT's aviation policies, including the following:
By Vermont law, the VAOT is responsible for the operation of the ten State-owned airports. Along with this responsibility comes the obligation of the State to operate and maintain the airports, maintain airport master plans or layout plans, make funding decisions, and act as a liaison with the FAA. Given the fact that legislative appropriations for capital improvements and maintenance at the airports has fluctuated from $1.3 million in 1987, $592,000 in 1992, and $3.3 million in 1999, VAOT has done surprisingly well to keep the airports in as good a condition as they are. What has been missing, however, is a policy to improve (rather than just maintain) the airports, and to move from the "worst first" approach to a more pro-active development approach. To this end, the 1998 Vermont Airport System Policy Plan made the following recommendations:
VAOT is currently proceeding with many of these recommendations. First, to assist in the development of detailed planning and capital improvement costs, VAOT is preparing Airport Master Plan or Airport Layout Plan Updates at the EF Knapp, Newport, Rutland, Caledonia County, Franklin County, Hartness, John H. Boylan, Middlebury, and William H. Morse State Airports. Secondly, in May, 1998, VAOT established the State Aviation Council (SAC) to assist in the development of aviation policy. Finally, in December, 1998, VAOT contracted with the aviation planning consultant Dufresne-Henry, Inc. to assist in the completion of several of the remaining Vermont Airport System Policy Plan recommendations. Specifically, Dufresne-Henry was charged with the development of the Vermont Airport Capital Facility Program, including the following work tasks:
This report represents the conclusion of this work. The results of these activities are summarized in the following sections of this report.
1.1 PROGRAM OVERSIGHT
In the development of the Vermont Airport Capital Facility Program, VAOT felt it necessary to have a broad spectrum of public and private interests assist in the review of this study. It was determined that the newly established SAC would be an ideal forum to provide this input. When the SAC was established, its goals were defined as:
The SAC agreed to provide input to this study as an advisory body, and also established a smaller Technical Advisory Committee (TAC) that met with the consultant to provide input throughout the project. The TAC met on five occasions to assist in the development of project goals, project evaluation criteria, airport classifications, and appropriate development standards. The TAC also served as a sounding board for issues to be presented before the SAC body.
1.2 PROJECT DEFINITIONS
Aviation projects which are discussed and evaluated in this program are Capital Improvement projects. Because there is no clear definition of what a "capital" project (versus a "maintenance" project), the following definition is presented which generally distinguishes between the two types of projects. There will likely be individual exceptions to this definition, however, most projects will fall fairly definitively in one of these categories.
Maintenance projects are those projects which meet one or more of the following criteria:
Typical Examples - Minor Roof Repair, Tree Clearing Around Hazard Beacons, Pavement Crack Sealing, Pavement Striping, Building Painting, Minor Building Repair, Routine Obstruction Removal On Airport Property.
Capital projects are those projects which meet one or more of the following criteria:
Typical Examples - Any Type of New Construction (Pavements, Buildings, Utilities), Pavement Reconstruction or Overlay, Initial Obstruction Removal on a Large Scale (Greater than ½ Acre).
1.3 LOCATION MAP
A map of the Vermont Airport System follows this page, and indicates all public use airport facilities. This particular study was limited to publicly owned, public use facilities; hence, the Basin Harbor, Warren-Sugarbush, Post Mills, North Windham and Mount Snow Airports shown on this map are not discussed in this report, as they are privately owned.
SECTION 2 - PROJECT PRIORITIZATION SYSTEM
2.0 BACKGROUND
The State of Vermont relies heavily on FAA funding to undertake the construction of major projects at the state-owned airports. For the 10 State-owned facilities, the FAA provides approximately $750,000 in matching funds annually. In addition, VAOT supplies a 6% match for FAA grants to the Burlington International Airport, and has previously supplied a similar match for an Airport Master Plan for the Fair Haven Municipal Airport. Currently VAOT uses their experience and knowledge of the airports' needs to determine where to apply these funds. VAOT desired to have a more quantitative method to determine the priority of the projects to be undertaken with the limited available Federal and State funds. As part of the Vermont Airport Capital Facility Program, a Project Prioritization System was developed by a Technical Advisory Committee (TAC), with the assistance of the Consultant. The TAC consisted of the following individuals:
Roger Damon Caledonia County State Airport
George Coy Franklin County State Airport
Bill Rossmassler Lamoille County Regional Planning
Bob McMullin (Later Replaced by Rich Turner) VAOT/Maintenance & Aviation
Scott Bascom VAOT/Policy & Planning
Jeff Scionti VAOT/Maintenance & Aviation
Paul Tober VAOT/Policy & Planning
2.1 PRIORITIZATION MODEL DEVELOPMENT
2.1.1 Goals. The goals recommended by the TAC for the Vermont Airport Capital Facility Program prioritization system were developed in a meeting held on December 21, 1999. It was determined that the prioritization system must:
With these factors in mind, the TAC recommended four primary goals of the prioritization system:
2.1.2 Evaluation Criteria. To assist in the development of an Airport Project Prioritization System, similar systems from 11 States were compiled and reviewed. The systems which were reviewed were from the following states:
Alabama
Arizona
Illinois
Iowa
Kansas
Louisiana
New York
Pennsylvania
Virginia
Wisconsin
Wyoming
VERMONT AIRPORT CAPITAL FACILITY PROGRAM
EVALUATION WORKSHEET DEFINITIONS (REVISED 2/28/00)
Acronyms: NPIAS (National Plan of Integrated Airport System) Code - FAA Airport Code which describes Activity Level of Airport
NAVAIDS - Navigation Aid ARFF - Aircraft Rescue and Firefighting
| # | CRITERIA | DEFINITION | MEASUREMENT | |
| ITEM | POINTS | |||
| AIRPORT CRITERIA AIRPORT CRITERIA | ||||
| 1 | Airport Operations | Considers the number of annual operations at the airport to gauge the level of activity. An operation is defined as a takeoff or a landing of a fixed or rotary wing aircraft, including airplanes, gliders, helicopters and ultra light aircraft. One "Touch and Go" training procedure would account for 2 operations - one landing and one take-off. | Greater Than 20,000 Annual
Operations
5,001 - 20,000 Annual Operations 0 - 5,000 Annual Operations |
50
30 10 |
| 2 | Based Aircraft | Considers the number of based aircraft at the airport to gauge the level of activity. | Greater Than 45 Based Aircraft
11 - 45 Based Aircraft 1 - 10 Based Aircraft |
50
30 10 |
| 3 | Geographic Proximity | Gives points to remote airports. The intent is to recognize the importance of airports which can provide access to less populated areas. Travel time is calculated as the distance measured in a straight line from the airport to a metropolitan area (village or city with a population greater than 7,500 people) divided by a speed of 30 miles per hour. | Greater Than ½ Hour
1/4 - ½ Hour Less Than 1/4 Hour |
20
12 6 |
| 4 | Governmental & Local Support | Gives points to facilities which have demonstrated local and regional support. Support is measured by evaluating three specific areas - attendance at Airport Capital Facility Program Meetings, documented history of community and business support of the airport, and existing or proposed development of local zoning regulations which specifically address development adjacent to the airport. Points will be given in each of these three areas, and should consider the size of the population within the vicinity of the airport, to give additional points for smaller airports with particularly strong local and government support. | 4A - Meeting Attendance
Strong Attendance Moderate Attendance Weak Attendance |
6 4 2 |
| 4B - History of Local Support
Measured by documented summary of projects undertaken by airport without State or Federal Aid; letters of support from local businesses, users of the airport, and quasi-public entities; existence of an active airport advisory group, commission, or other entity; history of coordinating with and inviting VAOT to participate in local airport activities; history of use of the airport for public events, such as car shows, air shows, fairs, etc. |
8 - 0 | |||
| 4C - Zoning Which Addresses
Protection of Airport & Surrounding
Airspace
Existing Airport Land Use Zoning Proposed Airport Land Use Zoning Not Yet Enacted No Airport Land Use Zoning |
6 4 0 | |||
| 4 - Governmental & Local Support Score | Total Points | |||
| PROJECT CRITERIA PROJECT CRITERIA | ||||
| 5 | Economic Development | Gives points for projects with documented proof that the project is required to maintain or attract new entities, businesses, air carrier service, or mail/freight shipping service, or to enhance the economic development of a local business. In order to give credit for this criteria, written documentation is required from either a user, a business that would benefit from the potential improvement, or a local quasi-public entity stating the economic benefit of the improvement in terms that can be measured (dollars), if possible. The benefit should be measured in increased payroll dollars or increased business revenue. | Documentation of Economic Benefit
of Project with ...
Project Required to Maintain or Attract a New Business, Air Carrier Service or Mail/Freight Shipping Service Greater than $1,000,000 Annual Economic Benefit Enhancement $100,001 - $1,000,000 Annual Economic Benefit Enhancement $10,001 - $100,000 Annual Economic Benefit Enhancement $0 - $10,000 Annual Economic Benefit Enhancement No Specific Dollar Amount of Benefit Identified No Documentation of Economic Benefit of Project |
40 40 20 12 4 2 0 |
| 6 | Special Program/Multi-Year Funding | Gives points for projects with particular support, or which are otherwise considered to be particularly important. Also provides 5 points for multi-year projects that are currently underway to recognize fact that unless mitigating circumstances indicate otherwise, the project should be progressing forwarding. | Subjective Ranking
5 Points For Multi-Year Projects Currently Underway |
20 - 0 |
| 7 | Project Type | Considers the type of project to be undertaken, with priority given to airside construction. For pavement rehabilitation or reconstruction projects, additional points will be given based on the Pavement Condition Index (PCI) score of the pavement to be rehabilitated. The PCI score shall be the based on the Pavement Management Study completed by Clough, Harbour & Associates for VAOT in March of 1999. | Primary Runway
Primary Runway Taxiway Planning Aprons/Connector Taxiways NAVAIDS Land Acquisition Hangar Site Development Snow Removal/ARFF Equipment & Bldgs. Secondary Runway Terminal/Landside Airfield Electrical/Vaults |
100
90 90 80 70 70 60 60 60 50 40 |
| For Pavement Rehabilitation or
Reconstruction Projects, add
Following Points
PCI Rating 0 - 19 20 - 39 40 - 59 60 - 79 80 - 100 |
20 16 12 8 4 0 | |||
| 5 - Project Type | Total of Points | |||
| 8 | FAA Priority Points | Points are given for projects eligible for FAA funding, based on the FAA's priority ranking system. This will help to tie the VAOT prioritization system into the FAA system. | FAA Priority Ranking Score
100 - 90 89 - 80 79 - 70 69 - 60 59 - 50 49 - 40 39 - 30 29 - 20 19 - 10 9 - 0 Projects Not Eligible for FAA Funding |
20 18 16 14 12 10 8 6 4 2 0 |
| 9 | Upgrade to FAA Standards | Gives points for projects which will upgrade the airport to FAA safety standards. These standards include construction of or improvements to runway and taxiway safety areas, runway and taxiway widths, and runway and taxiway gradient; obstruction identification, lighting and/or removal (including land or easement acquisition for removal of these obstructions); and relocation of a runway threshold for avoiding approach obstructions. | Project Will Completely Bring
Airport into Compliance with an
FAA Safety Requirement
Project Will Partially Bring Airport into Compliance with an FAA Safety Requirement Project Is Not Related to an FAA Safety Requirement |
100
50 0 |
| 10 | VAOT Development Standards | Gives points for projects which will upgrade the airport to VAOT's minimum development standards. These standards include installation of perimeter security fencing around the entire airport; construction of a taxiway system to remove aircraft from the active runways; construction of aprons to meet forecasted aircraft demand; weather reporting device, runway lights and ground communication outlets for instrument approach airports; maintenance of existing infrastructure; development of a public picnic area; and the preparation or update of the airport layout plan or master plan. | Project Will Completely Meet a
VAOT Development Requirement
Project Will Partially Meet a VAOT Development Requirement Project Is Not Related to, or is in Excess of, a VAOT Development Requirement |
100
50 0 |
| 11 | Previously Programmed Federal or State Aid | Gives significant evaluation points to projects with State or Federal funding programmed to the project. Points are given on a sliding scale, ranging from 200 points to 0 points. | Funding Programmed for Current
Year
Funding Programmed 1 Year Out Funding Programmed 2 Years Out Funding Programmed >2 Years Out or No Funding Programmed |
200
150 50 0 |
| 12 | Cost/Benefit | Gives points for projects that will significantly increase the utility of the airport at a relatively small cost. To be eligible, project must cost less than $75,000. Evaluation is based on the project's ability to increase the utility of the airport, and the project cost. | 12A - Project Cost
$0 - $5,000 $5,001 - $25,000 $25,001 - $75,000 |
50 30 10 |
| 12B - Benefit
Project Has Potential for Significant Increased Use of Airport Project Has Potential for Minor Increased Use of Airport Project Has No Potential for Increased Use of Airport |
50 30 0 | |||
| 12 - Cost/Benefit | Total of Points | |||
| 13 | Resource Impact | Gives points to projects which are not anticipated to have significant resource impact. Also penalizes facilities which are anticipated to have significant resource impact. | No anticipated resource impact
Minor resource impact - no mitigation anticipated Major resource impact - mitigation anticipated |
40
20 0 |
| 14 | Project Interest and Support | Gives points for projects with demonstrated local interest and support. Examples of project support could be procurement of some or all financial assistance outside of VAOT and FAA sources, assistance in providing construction project material and/or labor, and letters of support from local businesses, users of the airport, and quasi-public entities attesting to the benefits of the proposed project. Project opposed by an organized group or several individuals are given negative points. Points given in these areas should consider the size of the population within the vicinity of the airport, to give additional points for smaller airports with particularly strong local and government support. | 14A - Project Support
Measured by letters of support from local businesses, users of the airport, and quasi-public entities; resolutions or other formal motions from public and quasi-public entities; documentation of public meetings expressing support for the project; or a documented willingness to procure some or all financial assistance outside of VAOT and FAA sources and/or assistance in providing construction project material or labor. |
20 - 0 |
| 14B - Project Opposition
Measured by the level of organized, documented opposition to the project. |
0 - (-20) | |||
| 14 - Project Interest and Support | Total Points | |||
| TOTAL POTENTIAL AIRPORT POINTS (CRITERIA 1 - 4) | 140 | |||
| TOTAL POTENTIAL PROJECT POINTS (CRITERIA 5-14) | 760 | |||
| MAXIMUM POSSIBLE PROJECT RANKING | 900 | |||
2.2 PROJECT EVALUATION WORKSHEETS.
One of the primary desires of VAOT was to create a project prioritization system that was easily understood by all parties who may wish to review the project rankings. To help facilitate this ease of review, a one page summary of each project evaluation was created. This worksheet concisely summarizes all pertinent information on the proposed project, including the airport location, a project description, cost, project duration, and the summarized evaluation sheet. A sample of this worksheet follows, as well as a blank worksheet. A detailed explanation of the evaluation process can be found in Section Five, Project Evaluation.
INSERT 2 BLANK WORKSHEETS
SECTION 3 - PUBLIC INVOLVEMENT
3.0 PUBLIC INVOLVEMENT APPROACH
As part of the Airport Capital Facility Program process, a significant effort was expended to present the program to the public, both for their information and to obtain their input on the program that VAOT was developing. To this end, a series of four rounds of public meetings were held in December 1998/January 1999; July, 1999; October, 1999; and December, 1999. With the exception of the last round of meetings, all public meetings were held at the 12 System Airports where space was available. For the Fair Haven Municipal and John H. Boylan State Airports, the meetings were held at the Fair Haven and Brighton Town Offices, and due to the large turn-out, the last public meeting for the Caledonia County State Airport was held at the Lyndon Town offices. The final round of public meetings consisted of three regional presentations at locations in Montpelier, St. Johnsbury, and Rutland. A total of 38 public informational meetings were held.
The intent of these public meetings was to maximize public involvement, and to make those groups associated with the various airports part of the decision-making process. Based on comments received throughout this study, it appears that this goal was successfully achieved.
3.1 MEETING SUMMARIES
3.1.1 First Public Meeting. To kick off the project, a series of inventory meetings were held at each of the 12 system airports between December 17, 1998 and January 7, 1999. Due to the timing of the meetings during the holiday season, attendance varied widely, however, positive and informative input was received at all meetings.
The meetings were composed of several elements:
The total number of meeting attendees were as follows:
Table 3-1
First Public Meeting Attendance
| Airport | Meeting Date | Attendees* |
| Burlington International | December 21, 1998 | 4 |
| Caledonia County | December 18, 1998 | 3 |
| E.F. Knapp | December 18, 1998 | 2 |
| Fair Haven Municipal | January 7, 1999 | 3 |
| Franklin County | December 21, 1998 | 6 |
| Hartness | January 6, 1999 | 14 |
| John H. Boylan | December 17, 1998 | 5 |
| Middlebury | January 5, 1999 | 8 |
| Morrisville-Stowe | December 18, 1998 | 3 |
| Newport | December 17, 1998 | 4 |
| Rutland | January 7, 1999 | 14 |
| William H. Morse | January 8, 1999 | 5 |
* Does not include VAOT staff or Consultants
While these meetings generally focused on an inventory of the airport facilities and an overview of the Airport Capital Facility Program, a wide variety of comments were also expressed at these meetings. Some of the more significant comments that were raised included:
3.1.2 Second Public Meeting. The second round of public meetings were once again held at each of the 12 system airports, between July 12 and July 23, 1999. The focus of these meetings was to update the public on the work completed to date, and to set the groundwork for the public involvement in the support elements of the project ranking model. The primary items of discussion were:
The total number of meeting attendees were as follows:Table 3-2
Second Public Meeting Attendance
| Airport | Meeting Date | Attendees* |
| Burlington International | July 15, 1999 | 1 |
| Caledonia County | July 21,1999 | 12 |
| E.F. Knapp | July 14,1999 | 13 |
| Fair Haven Municipal | July 13,1999 | 7 |
| Franklin County | July 15,1999 | 25 |
| Hartness | July 14,1999 | 12 |
| John H. Boylan | July 22,1999 | 12 |
| Middlebury | July 13,1999 | 5 |
| Morrisville-Stowe | July 20,1999 | 7 |
| Newport | July 21,1999 | 9 |
| Rutland | July 23,1999 | 13 |
| William H. Morse | July 12,1999 | 6 |
* Does not include VAOT staff or Consultants
This second round of meetings generally had higher attendance then the first meeting, and many more comments were raised at these meetings, including the following:
3.1.3 Third Public Meeting. As with the previous two rounds, the third series of public meetings were once again held at the 12 system airports, between October 12 and October 29, 1999. There was one exception to this - the staff at the Burlington International Airport indicated that since their projects were not being evaluated under this program, and there had been little public interest, that they did not see the need of the third public meeting.
The focus of these meetings was to update the public on the work completed to date, to present the draft prioritized list of projects, and gather public support and comment on the program. The primary items of discussion were:
The total number of meeting attendees were as follows:
Table 3-3
Third Public Meeting Attendance
| Airport | Meeting Date | Attendees* |
| Caledonia County | October 27,1999 | 34 |
| E.F. Knapp | October 28,1999 | 39 |
| Fair Haven Municipal | October 15,1999 | 1 |
| Franklin County | October 25,1999 | 24 |
| Hartness | October 14,1999 | 2 |
| John H. Boylan | October 26,1999 | 7 |
| Middlebury | October 12,1999 | 16 |
| Morrisville-Stowe | October 18,1999 | 69 |
| Newport | October 19,1999 | 3 |
| Rutland | October 29,1999 | 29 |
| William H. Morse | October 13,1999 | 4 |
* Does not include VAOT staff or Consultants
This third round of meetings had fairly erratic attendance, with one meeting having only 1 individual attend, while another meeting had almost seventy people in attendance. These meetings focused much more on the rankings of the projects at the individual airport and the final modifications to the prioritization model, and therefore general discussion related to the process itself was fairly limited. Nonetheless, there were some more general comments that were discussed, including the following:
3.1.4 Final Public Meeting. The public involvement phase of this program concluded with three regional meetings held in December, 1999. These meeting were held in Montpelier, St. Johnsbury and Rutland. The intent of these meetings was to walk the audience through the complete development and implementation of the program. The agenda for this meeting was as follows:
VAOT concluded these meetings with a charge to the local communities to undertake a concerted effort in early 2000 to gather and document local support for the airports and their associated projects, with the anticipation of the Airport Capital Facility Program being fully implemented in May of 2000.
The reader is directed to the technical appendix, where complete meeting minutes can be found.
SECTION 4 - AIRPORT CLASSIFICATION & DEVELOPMENT STANDARDS
4.0 INTRODUCTION
To assist VAOT in the determination of appropriate levels of development for the System Airports, the Consultant created standards which all airports should consider when evaluating their future facility needs. These standards are broken down into two primary categories - safety, which is generally addressed by FAA standards, and facility development, which is generally addressed by VAOT standards, as defined under this project. The Facility Development Standards are based on appropriate levels of facility improvements as determined by VAOT. Section 4.2 addresses the establishment of these standards. Preceding this section is a discussion on the classification of the Vermont Airport System. The FAA Safety Standards are nationally recognized guidelines, based exclusively on the design aircraft, which is defined by the largest aircraft which regularly uses the facility. Section 4.3 addresses the establishment of these standards.
4.1 AIRPORT CLASSIFICATION
Prior to creating appropriate development standards, it is necessary to define the role of the airport. Once this definition is complete, standards that are appropriate for the activity type and level at the airports can be defined. In a working meeting with the TAC on June 21, 1999, the classification system for the Vermont Airports was created. A review of this definition process follows:
4.1.1. Existing Airport Classification. While it is not currently used for development standards, the existing airport system was classified by VAOT in a study completed in 1973, and subsequently updated in 1983. This classification system was comprised of four types of airports - Air Carrier, Economic Development General Aviation Airports, Aviation Specialty Airports, and Other Public Landing Strips. Table 4-1 summarizes the classifications of the current public use airports in Vermont, with their associated definitions.
TABLE 4-1
1983 VERMONT AIRPORT SYSTEM PLAN AIRPORT CLASSIFICATIONS FOR PUBLIC USE FACILITIES(1)
| FACILITY | CLASSIFICATION | DESCRIPTION |
| Burlington International | Air Carrier | Airports designed to support scheduled air service; 5,000 foot long and 150 foot wide minimum paved runway |
| Rutland State | ||
| William Morse State | Economic Development
General Aviation Airports |
Airports designed to support corporate aircraft; must have all-weather operational reliability; 4,000 foot long and 100 foot wide minimum paved runway; emergency landing strip potential |
| E.F. Knapp State | ||
| Newport State | ||
| Caledonia County | ||
| Franklin County | ||
| Middlebury State | ||
| Morrisville-Stowe State | ||
| Mount Snow | ||
| Hartness State | ||
| Basin Harbour | Aviation
Specialty Airports |
Airports designed to serve sport and pleasure flying; recreational; emergency landing strip potential; 3,000 to 4,000 foot minimum paved runway |
| Fair Haven | ||
| John Boylan State | ||
| Post Mills | ||
| Warren-Sugarbush | ||
| North Windham | Other Public
Landing Strips |
Airports designed to serve owners of small aircraft; casual operations; emergency landing strip potential; 2,000 foot minimum grass runway |
4.1.2. FAA NPIAS Classification. The National Plan of Integrated Airport Systems (NPIAS) provides for five levels of classifications, including:
The NPIAS is tied into both the activity level of the airport {Commercial Service Airports (Primary) and Other Commercial Service Airports (Non-Primary)} and the airport's functional role {Reliever Airports and General Aviation Airports}. However, the NPIAS does not give the definition of the smaller, general aviation airports that comprise the majority (11 of the 12 airports) of the Vermont Airport System.
4.1.3. Other State Airport Classifications. In addition to the FAA's NPIAS classifications, and VAOT's existing classification system, other classification systems from various states were reviewed. A brief summary of the distinctives used, along with comments on their applicability to Vermont, are as follows:
4.1.4. Recommended Vermont State Airport Classification. After a review of the various classification systems used by other states, the TAC elected to use a two-tiered classification system, which incorporates a facility use descriptor (the airport role or function) and the FAA's facility classification, which is otherwise known as the Airport Reference Code. The facility use descriptor will generally define the development standards, whereas the Airport Reference Code (ARC) will generally define the FAA required safety standards. A detailed discussion of these descriptors follows.
4.1.4.1 - Facility Use. The facility use descriptors that were established for Vermont are:
Table 4-2 shows each of the Vermont system airports and their associated facility use classifications.
TABLE 4-2
VERMONT AIRPORT SYSTEM FACILITY USE DESCRIPTORS
| Airport | Facility Use Descriptor |
| Burlington International Airport | Commercial Service |
| Rutland State Airport | Commercial Service |
| Caledonia County State Airport | General Aviation |
| E. F. Knapp State Airport | General Aviation |
| Franklin County State Airport | General Aviation |
| Hartness State Airport | General Aviation |
| Newport State Airport | General Aviation |
| William H. Morse State Airport | General Aviation |
| Middlebury State Airport | General Aviation |
| Morrisville-Stowe State Airport | General Aviation |
| John H. Boylan State Airport | Aviation Specialty |
| Fair Haven Municipal Airport | Aviation Specialty |
The second part of the airport classification is the Airport Reference Code (ARC). The ARC is a coding system the FAA developed to assist airports and airport sponsors in establishing which particular design standards are appropriate for which airport. The ARC employs characteristics for both the physical component of the aircraft and the operational component. The Approach Category is the portion of the ARC which describes a grouping based upon aircraft operating characteristics, namely, the approach speed of the aircraft. The Airplane Design Group is the portion of the ARC which describes a grouping based upon the aircraft physical characteristics. The Approach Category and the Airplane Design Group are defined below:
4.1.4.2 - Approach Category. The approach category groups operational characteristics of aircraft based upon its approach speed. The FAA considers the approach speed to be equal to 1.3 times the stall speed in a landing configuration at the aircraft's maximum certificated landing weight. Runway design standards are partially based upon the approach category. The approach categories are delineated into the following five groups:
| Category A: | Approach speed equals less than 91 knots. |
| Category B: | Approach speed equals 91 knots or more, but less than 121 knots. |
| Category C: | Approach speed equals 121 knots or more, but less than 141 knots. |
| Category D: | Approach speed equals 141 knots or more, but less than 166 knots. |
| Category E: | Approach speed equals 166 knots or more. |
4.1.4.3 - Design Group. The Airplane Design Group considers the physical characteristics of aircraft based upon wingspan. Certain runway design standards are based upon the airplane design group and taxiway design standards are entirely based upon this group. The Airplane Design Group is delineated into the following six groups:
| Group I: | Airplane wingspan up to 49 feet |
| Group II: | Airplane wingspan equals 49 feet up to 79 feet |
| Group III: | Airplane wingspan equals 79 feet up to 118 feet |
| Group IV: | Airplane wingspan equals 118 feet up to 171 feet |
| Group V: | Airplane wingspan equals 171 feet up to 214 feet |
| Group VI: | Airplane wingspan equals 214 feet up to 262 feet |
The airport or airport sponsor typically refers to the ARC to ensure that airfield projects adhere to the appropriate design standards. The airport or airport sponsor should also periodically compare aircraft operating at the airport and the established airport ARC. The ARC should be equal to the most demanding aircraft that operates or intends to operate at the airport on a regular basis.
Airports containing two or more runways should design most airfield facilities to the most demanding ARC and design specific areas to a less restrictive ARC. This will avoid the unnecessary over-development and the additional maintenance needs that go along with the excess development. The following table shows the Vermont system airports, their established ARC and the airplane characteristics that pertain to this ARC:
Table 4 - 3
Established Airport Reference Codes
| Airport | ARC | Designed for the following Aircraft Characteristics |
| Burlington International Airport | D-V | Approach speed equals 141 knots up to 166 knots.
Wingspan equals 171 feet up to 214 feet. |
| Rutland State Airport | C-II | Approach speed equals 91knots up to 121 knots.
Wingspan equals 49 feet up to 79 feet. |
| Caledonia County State Airport | B-II | Approach speed equals 91knots up to 121 knots.
Wingspan equals 49 feet up to 79 feet. |
| E. F. Knapp State Airport | B-II | Approach speed equals 91knots up to 121 knots.
Wingspan equals 49 feet up to 79 feet. |
| Franklin County State Airport | B-II | Approach speed equals 91knots up to 121 knots.
Wingspan equals 49 feet up to 79 feet. |
| Hartness State Airport | B-II | Approach speed equals 91knots up to 121 knots.
Wingspan equals 49 feet up to 79 feet. |
| Newport State Airport | B-II | Approach speed equals 91knots up to 121 knots.
Wingspan equals 49 feet up to 79 feet. |
| William H. Morse State Airport | B-II | Approach speed equals 91knots up to 121 knots.
Wingspan equals 49 feet up to 79 feet. |
| Morrisville-Stowe State Airport | B-II | Approach speed equals 91knots up to 121 knots.
Wingspan equals 49 feet up to 79 feet. |
| Middlebury State Airport | B-I | Approach speed equals 91knots up to 121 knots.
Wingspan equals less than 49 feet. |
| John H. Boylan State Airport | A-I | Approach speed equals less than 91 knots.
Wingspan equals less than 49 feet. |
| Fair Haven Municipal Airport | A-I | Approach speed equals less than 91 knots.
Wingspan equals less than 49 feet. |
4.2 VAOT AVIATION DEVELOPMENT STANDARDS
This Section of the Vermont Capital Facility Program establishes the airport development standards for the Vermont state airports under study. This evaluation primarily focuses on the airport terminal area (aprons, hangars, fuel farms, auto parking and access, and administration/terminal buildings).
The airport development standards analysis uses two primary means of establishing levels of improvements - the airport facility use (Commercial Service, General Aviation, Aviation Specialty), and the activity level of the airport. An inventory of terminal facilities is presented, and then these results are compared to theoretical facility requirements. Requirements are determined from the unconstrained forecasts of aircraft operations and planning guidelines presented in Advisory Circular 150/5300-13 Airport Design.
New facilities or facility improvements are recommended with the goal of maintaining a viable and effective airport for its users. The following subsections address the ability of the existing airport facilities to accommodate current aviation demands and to recommend the appropriate development standards to add or improve these facilities to meet these demands.
4.2.1. Aircraft Parking Aprons. Aprons are areas at the airport which provide aircraft parking, access to terminal facilities, fueling, deicing, ground power units, tow vehicles, ground transportation to terminal areas and other typical support needs for aircraft. Apron areas are typically divided into two categories for determining the existing aircraft parking needs, as well as future aircraft parking needs. The two apron categories are based upon the expected length of use. The two apron categories are transient aprons and aprons for based aircraft.
Transient aprons are normally located closest to the terminal. The determining factor for transient aprons is that the aircraft may stay for a period of time (from quick stops to overnights) but the aircraft is not based at the airport. Aprons for based aircraft are typically separate from these aprons. Based aircraft aprons are typically located near hangars, tie down areas and aircraft service areas.
To determine total apron demand, transient apron requirements are determined from a formula derived from the itinerant operations forecast developed earlier. Based aircraft apron needs are calculated from an assumed percentage of the based aircraft forecasts.
4.2.1.1. - Transient Apron. Advisory Circular 150/5300-13, Appendix 5 presents a methodology for calculating itinerant parking demand in instances where actual field surveys are unavailable. The following calculations are presented to estimate itinerant parking demand.
Calculate the average peak daily itinerant operations for the most active month. Assume the active month is 15% busier than average month
Assume the average busy itinerant day is 10 percent more active than the average day.
Assume that a certain portion of the itinerant airplanes will be on the apron during the day. For this analysis it will be assumed that 30 percent of the total busy day itinerant operations will be parked on the apron at any one time.
Calculate the area needed on the basis of 360 square yards (s.y.) of apron space for all transient aircraft (Airport Design recommends a range of 300 SY for single engine up to 700 SY for General Aviation jets. A weighted mid-point of 360 SY will be applied).
4.2.1.2 - Based Aircraft Apron. The first step is to obtain the number of based aircraft requiring apron tie-down space. For purposes of this analysis, it will be assumed that 50 percent of all based aircraft will opt for tiedowns over more expensive hangars. Because most based aircraft that use tiedowns in lieu of hangars are single engine aircraft, a budget of 300 SY of parking apron per aircraft will be used to calculate demand.
There will be variations on this assumption from airport to airport depending upon a number of caveats. This includes the availability of existing hangars and the respective cost to each aircraft owner. A surplus capacity of low cost hangars will tend to lessen tiedown demand at northern tier airports, with severe winter conditions, such as experienced at the Vermont system facilities.
There may also be a specific use such as the air freight operation at the William H. Morse State Airport, that results in a significant number of the larger twin engine aircraft remaining on the apron instead of being hangared. Nonetheless, this system analysis will provide a theoretical determination of apron demand which should be further refined as individual Master Plan is developed.
4.2.1.3. - Aircraft Parking Apron Demand. Apron area required for the Vermont System Airports within the next five years (Year 2004) and the existing apron availability is summarized in Table 4-4.
TABLE 4-4
EXISTING APRON SPACE AND APRON SPACE NEEDED FOR APPROPRIATE STANDARDS - 2004
W. H.
Morse
State
Airport (Requiring tiedown space) (300 SY per aircraft) (15% Greater then Average) (30% of PMAD) (360 SY per aircraft)
Rutland
State
Airport
Caledonia
County
Airport
E.F.
Knapp
State
Airport
Franklin
County
State
Airport
Hartness
State
Airport
Newport
State
Airport
Middlebury
State
Airport
Morrisville-Stowe
State
Airport
John H.
Boylan
State
Airport
Fair
Haven
Mun.
AirportBased-Aircraft Apron Standards Total Based Aircraft
46
19
49
57
42
20
49
46
36
1
2 50% of Based Aircraft
23
9
25
28
21
10
24
23
18
1
1 Based Aircraft Apron (SY)
6,900
2,700
7,500
8,400
6,300
3,000
7,200
6,900
5,400
300
300 Itinerant Aircraft Apron Standards Total Operations
32,400
6,400
15,750
37,500
26,800
8,100
16,100
37,500
21,100
600
500 Itinerant Operations
20,520
3,300
6,300
18,700
8,000
5,000
7,700
7,500
7,400
400
400 Peak Month Operations
1,966
316
604
1,792
767
479
738
719
709
38
38 Peak Month Avg. Day (PMAD)
(10% Greater then Average)
72
11
20
60
26
16
25
24
24
1
1 Itinerant Parking Demand
22
3
6
18
8
5
7
7
7
0
0 Itinerant Aircraft Apron (SY)
7,787
1,138
2,174
6,451
2,760
1,725
2,656
2,587
2,553
138
138 Total Apron Demand (SY)
14,687
3,839
9,674
14,852
9,060
4,725
9,857
9,488
7,953
438
438 Existing Apron Area (SY)1
12,000
6,900
5,400
9,000
18,000
8,000
12,500
12,500
8,200
0
0 Excess or (Deficit) (SY)
(2,687)
3,062
(4,274)
(5,852)
8,940
3,275
2,644
3,013
247
(438)
(438)
Source: Dufresne-Henry, Inc., analysis
1 Existing Apron Area Does not Account for Grass Tie-Downs
4.2.2. Hangar Demand. Hangar demand is a function of a number of different variables. This includes airport location, type of aircraft to be hangared, costs and seasonal variation. As previously stated, most higher performance aircraft will be hangared, while single engine and light twins are usually split between tiedowns and storage facilities. In the northern climes, some aircraft owners will hangar their aircraft in the winter and tiedown in the summer.
At most airports with a preponderance of GA activity, there are two types of hangars that are available to aircraft owners. The first is the T-hangar, typically an individual unit strictly providing storage to single engine and light twin aircraft. Often the individual units are "nested" together to form singular hangar structures ranging from five to ten units per structure.
The second style of hangar is the corporate type. This structure not only provides storage capabilities to based aircraft, but can also provide a venue for aircraft maintenance, FBO offices, and pilot lounges. Generally, these structures range from 5,000 SF to 10,000 SF.
Forecasting hangar demand is very subjective. Because hangars are ineligible for AIP funding and are usually financed by the private sector, cost is usually the determining factor. If an FBO or corporate operation decides to construct a new hangar, this can occur overnight with no correlation to based aircraft hangar needs. On the other hand, there may be a strong demand for new T-hangars, but due to costs to respective aircraft owners, the project does not happen.
It will be assumed that there may be a need to construct some type of hangar(s) at all of the airports under study within the five year development period. The underlying purpose is to ensure that there is adequate space to provide these facilities for each of the airports. For those airports with current Master Plans, hangar demand is depicted on each of the respective ALPs, and is carried over into this study. For all other facilities, the following development assumptions will be applied to project hangar demand through the five year planning period.
Table 4 - 5
Hangar Requirements
| Airport
Reference Code |
Hangar Requirements |
| Aviation Specialty | 1 - 5 unit T-Hangar |
| General Aviation | 1 - 10 Unit T-Hangar |
| 1 - 5,000 SF Corporate Hangar | |
| Commercial Service | 1 - 10 Unit T-Hangar |
| 2 - 10,000 SF Corporate Hangars |
4.2.3. Fueling Facilities. Fueling facilities at GA airports are similar to hangars. They are typically funded by the private sector, or built by the Sponsor and leased to an FBO. As a matter of policy, all attended airports should, at a minimum, have an available supply of AVGAS. The need for Jet-A should be made at each airport based on demand and the services provided by the FBO.
4.2.4. Terminal/Administration Buildings. Airport buildings are designed to house specific airport support needs or functions. The fixed base operator (FBO) building typically provides commercial space for aircraft maintenance and repair, flight lessons, charter, fuel sales, and other aircraft commercial support activities. The administration building can accommodate the pilot, passengers, public, and the airport management. The administration building should be located near the FBO but sufficiently separated to preclude conflict between airplanes operating from these areas. In keeping with VAOT policy, all public facilities should be ADA compliant.
It should be noted that lower activity airports may not initially justify the construction of either an FBO or administrative building. The initial airport building is often a maintenance hangar with the attached offices. For an airport to consider construction of a separate administrative type building, there should be a minimum of ten departures and arrivals during the peak hours of a busy day. All attended airports should have as a minimum an area set aside in a hangar or other similar structure which provides a public phone (accessible 24 hours a day); ADA compliant rest rooms; a telephone recording describing the airport facilities and operating hours; a pilot's lounge or waiting area; and a bulletin board.
If construction of an administrative building is necessary, the minimum facilities should accommodate a pilot briefing area, restrooms, an informational booth or bulletin board, a public phone (accessible 24 hours a day) and a telephone recording. This room should have easy access to the restrooms and parking areas. Table 4-6, Existing Administration Building Ammenities describes the current availability of the services described in the above text at each of the Vermont state-owned airports. Airports with commercial service should allow for access to public transportation services at the administration building in addition to the above minimum services. This can range from providing a regularly scheduled bus stop to a simple information kiosk which has phone numbers and information for services such as cabs, rental cars, hotels, restaurants, etc.
Where feasible, airports should also attempt to provide multi-modal links to other transportation networks. One existing example is the parking lot at the Morrisville-Stowe State Airport, which is utilized as a park-and-ride facility due to its proximity to Route 100.
Table 4 - 6
Existing Administrative Building Ammenities
|
Airport Name |
Ammenities Provided? | |||||
| Public
Phone |
Rest
Rooms |
Food |
Telephone
Recording |
Pilot
Lounge |
Bulletin
Board | |
| Rutland State | yes | yes | yes | yes | yes | yes |
| Caledonia County State | yes | yes | no | yes | yes | yes |
| E. F. Knapp State | yes | yes | yes | yes | yes | yes |
| Franklin County State | yes | yes | no | yes | yes | yes |
| Hartness State | yes | yes | no | yes | yes | yes |
| Newport State | yes | yes | no | yes | yes | yes |
| William H. Morse State | yes | yes | no | yes | yes | yes |
| Middlebury State | yes | yes | no | yes | yes | yes |
| Morrisville-Stowe State | yes | yes | no | yes | yes | yes |
| John H. Boylan State | yes | no | no | no | no | yes |
| Fair Haven Municipal | no | no | no | no | no | no |
4.2.5. Auto Parking. Auto parking at commercial service facilities is divided between airline passengers and other users and tenants of the airport. Users and tenants include GA passengers and pilots, airport based employees and often rental car companies.
There is only one commercial service airport under study, and based on a review of the current Master Plan, parking needs for airline passengers have been determined to be adequate through the planning period. At the other GA airports there are several general planning guidelines that should be used to assess parking needs.
For GA passengers and pilots it is recommended that there should be one space for fifty percent of the based aircraft and 1.5 spaces for the peak day itinerant aircraft parked on the itinerant apron. There should also be adequate parking for airport employees and other visitors. For purposes of this analysis, a total demand of ten employees and visitors will be assumed. It is understood that there may be several airports with a greater demand, but generally this demand is accommodated at each tenants' base of operation. Parking facilities for public buildings should provide for appropriate levels of ADA compliant parking spaces. For airports with nighttime operations, the parking lots should provide for some type of security lighting.
As was done to quantify airport apron needs, parking requirements are determined from existing Master Plans where applicable. Table 4-7 summarizes the parking demand using either the above assumptions or Master Plan data.
Based on review of the table, it would appear that most airports within the system study are under capacity for auto parking. Field reconnaissance of these facilities indicates that the analysis may overstate the parking shortage. This is likely due to several factors, including the basis of the analysis deriving from a peak demand quantification that will only occur sporadically during the summer months. It should also be acknowledged that the assessment of existing parking may not account for many based pilots parking their autos near their aircraft, or in their hangars.
4.2.6. Auto Access. Auto access at any airport focuses on two issues; access to the airport and internal access to airport facilities. At a minimum, access to all airports with paved runways should be a paved, two lane roadway and conform to the minimum standards set forth in each municipalities' bylaws concerning roadway development.
Internal access should be designed to provide a positive separation between airside and terminal area facilities. Ideally, there should be no auto traffic on airport runways, taxiways or aprons. Internal access roads are usually separated from these airside areas with security fencing and gates. In addition to terminal area facility access, there should also be adequate access provided for airport maintenance and emergency vehicles to reach all points of the airfield operation areas.
4.2.7. Airfield Navigational Aids. Navigational Aids is a broad term which encompasses equipment which is utilized by the pilot either on the approach to the airport, or in preparation to depart the airport. The equipment necessary for each type of airport varies, but generally should consist of some type of weather information, vertical approach guidance, horizontal approach guidance, and airfield lighting. The type of equipment necessary is dependant on the approach type of the airport - either a visual approach or a non-precision approach. Table 4-8 summarizes the navigational aid requirements of the Vermont Airport System.
Table 4 - 7
Existing and Required Vehicle Parking
| Airport Name | Spaces Needed | Existing Spaces | Surplus
or Deficit | ||||
| Based A/C | 50% Based | Itinerant | 1.5 * Itinerant | Total | |||
| Rutland State | 46 | 23 | 72 | 108 | 131 | 100 | -31 |
| Caledonia County State | 19 | 10 | 11 | 17 | 26 | 15 | -11 |
| E. F. Knapp State | 49 | 25 | 20 | 30 | 55 | 50 | -5 |
| Franklin County State | 57 | 29 | 60 | 90 | 119 | 50 | -69 |
| Hartness State | 42 | 21 | 26 | 39 | 60 | 50 | -10 |
| Newport State | 20 | 10 | 16 | 24 | 34 | 30 | -4 |
| William H. Morse State | 49 | 25 | 25 | 38 | 62 | 50 | -12 |
| Middlebury State | 46 | 23 | 24 | 36 | 59 | 35 | -24 |
| Morrisville-Stowe State | 36 | 18 | 24 | 36 | 54 | 50 | -4 |
| John H. Boylan State | 1 | 1 | 1 | 2 | 2 | 0 | -2 |
| Fair Haven Municipal | 2 | 1 | 1 | 2 | 3 | 0 | -3 |
Table 4 - 8
Appropriate Airport Navigational Aids
| Airport Name | Approach
Type |
Glide Slope
Indicator |
Lighting | Hazard Beacons | Rotating
Beacon |
GCO | AWOS | Wind Direction Indicator |
| Rutland State | Non-Precision | PAPI | MIRLS | yes | yes | yes | yes | yes |
| Caledonia County State | Non-Precision | PAPI | MIRLS | yes | yes | yes | yes | yes |
| E. F. Knapp State | Precision | PAPI | HIRLS | yes | yes | yes | yes | yes |
| Franklin County State | Non-Precision | PAPI | MIRLS | yes | yes | yes | yes | yes |
| Hartness State | Non-Precision | PAPI | MIRLS | yes | yes | yes | yes | yes |
| Newport State | Non-Precision | PAPI | MIRLS | yes | yes | yes | yes | yes |
| William H. Morse State | Non-Precision | PAPI | MIRLS | yes | yes | yes | yes | yes |
| Middlebury State | Visual | no | no | no | no | no | no | yes |
| Morrisville-Stowe State | Non-Precision | PAPI | MIRLS | yes | yes | yes | yes | yes |
| John H. Boylan State | Visual | no | no | no | no | no | no | yes |
| Fair Haven Municipal | Visual | no | no | no | no | no | no | yes |
A/C - Aircraft PAPI - Precision Approach Path Indicator MIRLS - Medium Intensity Runway Lights HIRLS - High Intensity Runway Lights GCO - Ground Communication Outlet AWOS - Automated Weather Observation System
4.2.7.1. - Visual Airport Navigational Aids. For airports with no published approach, the appropriate airfield navigational aids should be considered as a lighted wind sock for rudimentary weather information (wind direction) and airport identification. No visual approach guidance is necessary.
4.2.7.2. - Non-Precision Airport Navigational Aids. For airports with a non-precision approach, the appropriate weather reporting equipment should be considered as a lighted wind sock for rudimentary weather information (wind direction), and an Automated Weather Observation System (AWOS) or an Automated Surface Observation System (ASOS). These two systems consist of identical equipment, with the only difference being that ASOS were installed under a Federal Program by the National Oceantic and Atmospheric Administration (NOAA), whereas AWOS are funded by the airport sponsor. An AWOS or ASOS consists of a 30-35 foot high tower, and several smaller towers within an fenced area of approximately 20 feet by 30 feet. These towers support several weather observation sensors which provide wind, visibility and precipitation data to pilots utilizing the airport.
Visual approach guidance should be provided via a Precision Approach Path Indicator (PAPI) or equivalent for at least one runway at the airport.
Airports that have nighttime operations should provide nighttime visual guidance with pilot controlled Medium Intensity Runway Lights (MIRLs). For airports with nighttime Instrument Flight Rule (IFR) operations, to assist the pilot during low weather operations, any required obstruction lights and an airport rotating beacon are required.
All airports which have either a non-precision or a precision approach should have a ground communication outlet (GCO). Without an GCO, there is no direct radio communication link between pilots and the Terminal Control Area (TCA). When departing from an Airport under IFR conditions, the pilot must file a flight plan and obtain a clearance from TCA prior to departure. Without the GCO, the pilots must use a payphone at the airport, and are given a void time limit of 5-15 minutes. If the pilot has not departed by this time, another clearance must be obtained. The GCO would allow the pilot to contact TCA directly from the aircraft, which could save several minutes. During inclement weather conditions, or while waiting for a aircraft making an approach to the airport, these few minutes could be the difference between departing on time, or having to leave the aircraft, return to the terminal building, and contact TCA for another clearance.
4.2.8. Airport Instrument Approaches. At the end of January, 1999, results concluding a six month long risk assessment test sponsored by the FAA confirmed that augmented GPS can be the only "sole-service" navigation system installed in an aircraft. GPS has planned to make most precision approaches within then next ten years. Currently, the FAA has determined that GPS establishes a safer approach than both the Non-Directional Beacon (NDB) and the Very-high frequency Omnidirectional Range (VOR) for turning or circling approaches. Because of the effort that the FAA is putting into GPS, it is anticipated that eventually precision approaches will be executed utilizing GPS rather then ground based equipment. However, the completion date for GPS precision approaches has been delayed several times, and at the time of the writing of this report, no official deadline has been established.
Currently, the FAA is funding a Local Area Augmentation System (LAAS) to augment the GPS satellites. The LAAS will provide land-based equipment developed to incorporate additional accuracy into the airspace system. This system will provide the accuracy needed to conduct precision approaches. Since the FAA is currently no longer procuring and installing land-based conventional instrument approach equipment (such as localizers and glideslopes) as a general practice, and GPS precision approaches may still be several years from implementation, other types of precision approach equipment should be considered for installation at the Vermont System Airports that require an upgrade to a precision approach. If this upgrade is required, the airport and VAOT will have to work closely with the FAA to justify this expenditure. One such airport which is investigating this option is Rutland State, which is evaluating the feasibility of a Transponder Landing System (TLS) to provide a precision approach. This equipment is not yet certified by the FAA, but is expected to be shortly. It has the capability of providing curved and "dog-leg" approach and missed approaches, which could have significant benefits for airports in mountainous terrain such as the Vermont Airports.
To be considered as a potential candidate for a precision approach upgrade, the airport must have a minimum of five peak hour instrument operations, and the upgrade must provide a minimum of a 10% reduction in the ceiling or visibility minimums. Since it is likely that the FAA will be requested to provide funding, or at least to take over maintenance of the approach equipment once the installation is complete, FAA concurrence of the installation of a full precision approach is mandatory.
4.2.9. Security Fencing. All of Vermont state-owned airports should have a full perimeter fence installed to protect against the inadvertent entry of personnel or wildlife. Most all of the Vermont state-owned airports currently have at least partial security fencing installed.
4.2.10. Taxiway Systems. As stated in Advisory Circular 150/5300-13, a basic airport should consist of at least one runway, a full parallel taxiway and adequate transverse(connecting) taxiways. Although there are no specific guidelines indicating when a full parallel taxiway should be added to the airfield layout, it is recommended that all commercial service airports within the state system have a full parallel taxiway for each runway. It is also recommended that those GA airports with an ARC of B-II or higher be evaluated for a full parallel taxiway on each airport's primary runway.
The requirement for a taxiway system is typically triggered by either an airfield capacity constraint, or the need to increase airfield safety. The recommendation for a full parallel taxiway cannot be justified for any of the airports due to airfield capacity, but it should be a goal for at least a partial parallel taxiway to the primary runway end. As an interim measure, if a partial parallel taxiway cannot be justified due to economic or environmental constraints, a runway turnaround (a widened section of pavement at the runway end to facilitate the turning around of aircraft) should be installed at all runway ends without taxiway access.
4.2.11. Current Airport Layout Plan. To be considered for FAA funding, a project must be shown on an approved Airport Layout Plan (ALP). The FAA requires that all ALPs be kept current. At a minimum, the ALP should be updated every 10 years, and sooner if there has been a significant change in the level of operations or the type of aircraft regularly operating at the airport.
4.2.12. Americans with Disabilities Act (ADA) Compliance. It is the policy of the State of Vermont and the Federal Government to not discriminate on the basis of disabilities. All public use facilities at the airport (terminals, FBO offices and administrative buildings) should be constructed or modified to meet current ADA requirements.
4.2.13. Maintenance of Infrastructure. The FAA, VAOT and the local community have invested literally millions of dollars into the construction of the airport facilities in Vermont. As a policy, it is incumbent on VAOT to regularly maintain and repair these facilities. Those projects which are required to maintain the existing airports (i.e., runway pavement overlays, building rehabilitations, or major NAVAID repair) should be given a high priority.
4.2.14. Airport Picnic Areas. VAOT has received numerous requests to install picnic facilities at the airports for the use of itinerant pilots, as well as the general public. As part of VAOT's desire to reach out to the local population and explore possible uses of the airport that could benefit the community, consideration should be given for the installation of low cost picnic facilities. These sites should be located in areas where there is convenient public access, but not in areas which would encourage inadvertent entrance to the airside. If necessary, security fencing could be installed to provide positive separation between the picnic area and the airside.
4.3 FAA SAFETY STANDARDS
The FAA has published guidelines that will establish the appropriate airport safety standards for each of the Vermont system airports. The safety guidelines outlined below have been previously developed by the FAA for airport development and improvement in the Airport Design Advisory Circular (AC 150/5300-13). These guidelines ensure that safety is the main focus of any airport facility improvement or development. The FAA recommends that all airports and airport sponsors follow these guidelines.
The Airport Design Advisory Circular (AC) transitions from a recommendation status to becoming a requirement for airports or airport sponsors requesting federal aid. These guidelines have been established over many years of research and development testing by the FAA, National Transportation Safety Board (NTSB) and the United States Department of Transportation (USDOT). The Airport Design Advisory Circular is periodically appended with changes in design standards as the operational characteristics of aircraft change and new safety enhancements are developed. The Airport Design Advisory Circular provides many airport development standards that will be complimentary to the appropriate standards for the Vermont state airports.
4.3.1. Aircraft Characteristics. Many design standards pertaining to aircraft operating areas found in the Airport Design Advisory Circular are based upon aircraft characteristics and approach visibility minimums. There are aircraft characteristics that set specific design criteria for the aircraft intending to operate at the airport. These aircraft characteristics provide a basis to determine which specific design standard are appropriate for an individual airport. The three aircraft characteristics which the airport design standards refer to are the weight, the approach speed and the wingspan. The following section explains each of the above aircraft characteristics.
4.3.1.1 - Aircraft Weight. The FAA refers to an aircraft's maximum certificated takeoff weight when establishing runway and taxiway design standards in the Airport Design AC. The following two aircraft sizes reference this weight.
| Small Aircraft: | aircraft weighing 12,500 pounds or less at the maximum certificated takeoff weight. |
| Large Aircraft: | aircraft weighing more than 12,500 pounds at the maximum certificated takeoff weight. |
4.3.1.2 - Airport Reference Code. The next two aircraft characteristics which provide guidance to the specific standards that will be applicable to the airport have been grouped into the FAA Airport Reference Code system. This coding system was previously described in Section 4.1.4.
4.3.2. Runway Design Standards. This section describes the various runway design standards, as established in the Airport Design Advisory Circular. This section will reference the layouts depicted in Figure 4-1.

Figure 4-1 - Runway Design Standards
4.3.2.1 - Runway Safety Area (RSA). The RSA is an imaginary protection surface centered along the runway centerline, surrounding each runway. The terrain in the RSA must be clear of all obstacles to reduce the risk of damage to airplanes in the event of an undershoot, overshoot, or excursion from the runway. The RSA must have the following design characteristics:
4.3.2.2 - Runway Protection Zone (RPZ). The RPZ is an area off the runway end that enhances the protection of people and property on the ground. The RPZ is trapezoidal in shape and centered about the extended runway centerline. It is related to the approach and begins 200 feet beyond the runway end, regardless of whether or not the runway has a displaced threshold. The RPZ consists of the following Runway Object Free Area (OFA) and Controlled Activity Area.
Table 4-9
Runway Protection Zone (RPZ) Dimensions
| Approach Visibility
Minimums |
Facilities Expected
to Serve |
Runway Protection Zone Dimensions | |||
| Length
(I) |
Inner
Width (J) |
Outer
Width (K) |
RPZ
Acres | ||
| Visual and Not Lower Than 1 - Mile | Small Aircraft Exclusively | 1,000 ft. | 250 ft. | 450 ft. | 8.035 |
| Visual and Not Lower Than 1 - Mile | Aircraft Approach Categories A & B | 1,000 ft. | 500 ft. | 700 ft. | 13.770 |
| Visual and Not Lower Than 1 - Mile | Aircraft Approach Categories C & D | 1,700 ft. | 500 ft. | 1,010 ft. | 29.465 |
| Not Lower Than 3/4 - Mile | All Aircraft | 1,700 ft. | 1,000 ft. | 1,510 ft. | 48.978 |
| Lower Than 3/4 - Mile | All Aircraft | 2,500 ft. | 1,000 ft. | 1,750 ft. | 78.914 |
Notes:
1. The RPZ dimensional standards are for the runway end with the specified approach visibility minimums. The departure RPZ dimensional standards are equal to or less than the approach RPZ dimensional standards. When a RPZ begins other than 200 feet beyond the runway end, separate approach and departure RPZs should be provided. Refer to AC 150/5300-13 Change 5, Appendix 14 for approach and departure RPZs.
2. Letters correspond to the dimensions on Runway Design Standards Figure.
Source: Advisory Circular 150/5300-13 Change 5 "Airport Design".
4.3.2.3 - Runway Object Free Area (ROFA) is an area on the surface centered along the runway centerline that is free of any objects, except for the objects that need to be located there because of their function. The only obstacles that are allowed in the ROFA are those that need to be located there due to their function. These obstacles may be lighting, navigational aids, signs and service roads. All objects installed in the ROFA must be designed to break away easily on impact.
4.3.2.4 - Controlled Activity Area is the portion of the RPZ beyond and to the sides of the ROFA. The function and use in this area is restricted.
The ROFA and the Controlled Activity Area vary in size according to the Aircraft Design Group for which the runway is designed and the approach procedures to the runway (visual, non-precision, and precision).
4.3.2.5 - Obstacle Free Zone (OFZ). The OFZ is the three dimensional airspace situated along the runway and extended runway centerline. This airspace is above the established airport elevation and below 150 feet. This area is required to be cleared of taxiing and parked airplanes and object penetrations, with the exception of NAVAIDs that have been designed to easily break away on impact. The OFZ contains the runway OFZ, the inner-approach OFZ and the inner-transitional OFZ.
The Runway OFZ is the area surrounding the runway along the runway centerline and at the same elevation as the runway centerline. The Runway OFZ extends 200 feet beyond each end of the runway. The width of the Runway OFZ is determined by the aircraft size which the runway serves. The Runway OFZ widths are:
The Inner-Approach OFZ is an area centered along the approach area and only applies to runways with an approach lighting system. The inner-approach OFZ begins 200 feet beyond the runway threshold at the same elevation as the runway threshold and extends 200 feet beyond the last light unit in the approach lighting system. The width is equal to the Runway OFZ. The inner-approach OFZ rises in elevation at a slope of 50:1 away from the runway end.
The Inner-Transitional OFZ is an area located along the sides of precision instrument runways and the inner-approach OFZ. The inner-transitional OFZ surface slopes 3:1 out from the edges of the Runway OFZ and Inner-Approach OFZ to a height of 150 feet above the established airport elevation.
4.3.2.6 - Primary Surface. The Primary Surface is an imaginary surface area surrounding the runway and centered along the runway. The elevation at any point is the same as the elevation of the nearest point on the runway centerline. The width of the primary surface is as follows:
4.3.2.7 - Obstacle Transition Surface. The Transition Surface is a two-dimensional plane beginning at the edge of the Primary Surface rising at an upward slope of 7:1.
4.3.2.8 - Runway Line of Sight Standards. Along individual runways, two points five feet above the runway centerline must be mutually visible along the entire runway length. If the runway has a parallel taxiway extending the full runway length, then the line of sight may be obstructed for any point five feet above the runway centerline to any other point five feet above the runway centerline, for only one-half of the runway's length.
4.3.2.9 - Runway Threshold. The runway threshold is the beginning pavement area of the runway suitable for landing. Runway thresholds located other than at the beginning of the runway pavement are referred to as follows:
TABLE 4-10 Runway Design Standards for Airplane Approach Category A & B
Visual And Not Lower Than ¾ - Statute Mile Approach Visibility Minimums
| RUNWAY
CHARACTERISTICS |
DIMENSION | AIRPLANE DESIGN GROUP | ||||
| I | I | II | III | IV | ||
| Runway Length | A | Refer to AC 150/5325 - 4 | ||||
| Runway Width | B | 60 ft. | 60 ft. | 75 ft. | 100 ft. | 150 ft. |
| Runway Shoulder Width | N/A | 10 ft. | 10 ft. | 10 ft. | 20 ft. | 25 ft. |
| Runway Blast Pad | ||||||
| Width | C | 80 ft. | 80 ft. | 95 ft. | 140 ft. | 200 ft. |
| Length | D | 60 ft. | 100 ft. | 150 ft. | 200 ft. | 200 ft. |
| Runway Safety Area | ||||||
| Width | E | 120 ft. | 120 ft. | 150 ft. | 300 ft. | 500 ft. |
| Length Beyond Runway End | F | 240 ft. | 240 ft. | 300 ft. | 600 ft. | 1,000 ft. |
| OFZ Width and Length | Refer to AC 150/5300-13 Change 5 | |||||
| Runway Object Free Area | ||||||
| Width | G | 250 ft. | 400 ft. | 500 ft. | 800 ft. | 800 ft. |
| Length Beyond Runway End3 | H | 240 ft. | 240 ft. | 300 ft. | 600 ft. | 1,000 |
Notes:
1. Letters correspond to the dimensions on Runway Design Standards figure.
2. These dimensional standards pertain to facilities for only small airplanes. Small airplanes are aircraft 12,500 pounds or less maximum certificated takeoff weight.
3. The runway safety area and runway object free area lengths begin at each runway end when stopway is not provided. When stopway is provided, these lengths begin at stopway end.
Source: Advisory Circular 150/5300-13 Change 5 "Airport Design".
TABLE 4-11 Runway Design Standards for Airplane Approach Category A & B
Lower Than ¾ - Statute Mile Approach Visibility Minimums
| RUNWAY CHARACTERISTIC | DIMENSION | AIRPLANE DESIGN GROUP | ||||
| I | I | II | III | IV | ||
| Runway Length | A | Refer to AC 150/5325 - 4 | ||||
| Runway Width | B | 75 ft. | 100 ft. | 100 ft. | 100 ft. | 150 ft. |
| Runway Shoulder Width | 10 ft. | 10 ft. | 10 ft. | 20 ft. | 25 ft. | |
| Runway Blast Pad | ||||||
| Width | C | 95 ft. | 120 ft. | 120 ft. | 140 ft. | 200 ft. |
| Length | D | 60 ft. | 100 ft. | 150 ft. | 200 ft. | 200 ft. |
| Runway Safety Area | ||||||
| Width | E | 300 ft. | 300 ft. | 300 ft. | 400 ft. | 500 ft. |
| Length Beyond Runway End | F | 600 ft. | 600 ft. | 600 ft. | 800 ft. | 1,000 ft. |
| OFZ Width and Length | Refer to AC 150/5300-13 Change 5 | |||||
| Runway Object Free Area | ||||||
| Width | G | 800 ft. | 800 ft. | 800 ft. | 800 ft. | 800 ft. |
| Length Beyond Runway End3 | H | 240 ft. | 240 ft. | 600 ft. | 800 ft. | 1,000 ft. |
Notes:
1. Letters correspond to the dimensions on Runway Design Standards figure.
2. These dimensional standards pertain to facilities for only small airplanes. Small airplanes are aircraft 12,500 pounds or less maximum certificated takeoff weight.
3. The runway safety area and runway object free area lengths begin at each runway end when stopway is not provided. When stopway is provided, these lengths begin at stopway end.
Source: Advisory Circular 150/5300-13 Change 5 "Airport Design".
TABLE 4-12 Runway Design Standards for Airplane Approach Category C & D
| RUNWAY CHARACTERISTICS | DIMENSION | AIRPLANE DESIGN GROUP | |||||
| I | II | III | IV | V | VI | ||
| Runway Length | A | Refer to AC 150/5325 - 4 | |||||
| Runway Width | B | 100 ft. | 100 ft. | 100 ft. | 150 ft. | 150 ft. | 200 ft. |
| Runway Shoulder Width | 10 ft. | 10 ft. | 20 ft. | 25 ft. | 35 ft. | 40 ft. | |
| Runway Blast Pad | |||||||
| Width | C | 120 ft. | 120 ft. | 140 ft. | 200 ft. | 220 ft. | 280 ft. |
| Length | D | 100 ft. | 150 ft. | 200 ft. | 200 ft. | 400 ft. | 400 ft. |
| Runway Safety Area | |||||||
| Width | E | 500 ft. | 500 ft. | 500 ft. | 500 ft. | 500 ft. | 500 ft. |
| Length Beyond Runway End | F | 1,000 ft. | 1,000 ft. | 1,000 ft. | 1,000 ft. | 1,000 ft. | 1,000 ft. |
| OFZ Width and Length | Refer to AC 150/5300-13 Change 5 | ||||||
| Runway Object Free Area | |||||||
| Width | G | 800 ft. | 800 ft | 800 ft | 800 ft. | 800 ft. | 800 ft. |
| Length Beyond Runway End3 | H | 1,000 ft. | 1,000 ft. | 1,000 ft. | 1,000 ft. | 1,000 ft. | 1,000 ft. |
Notes:
1. Letters correspond to the dimensions on Runway Design Standards figure.
2. These dimensional standards pertain to facilities for only small airplanes. Small airplanes are aircraft 12,500 pounds or less maximum certificated takeoff weight.
3. The runway safety area and runway object free area lengths begin at each runway end when stopway is not provided. When stopway is provided, these lengths begin at stopway end.
Source: Advisory Circular 150/5300-13 Change 5 "Airport Design".
4.3.3 - Taxiway Design Standards. This section describes the various taxiway design standards, as established in the Airport Design AC. Taxiways are paved areas (separate access ways or lanes painted on aprons) over which airplanes move (taxi) from one part of an airport to another. One of their more important uses is to provide access between airside terminal areas and the runways.
There are three types of taxiways: parallel, exit and access. Taxiways parallel to runways generally provide a route for aircraft to reach certain distant points on the runway. Exit taxiways, which usually connect runways to parallel taxiways, provide paths for aircraft to leave the runway after they have landed. Access taxiways and taxilanes provide a means for aircraft to move among the various airside components of the airport - T-hangars, terminal tie-downs, fueling areas, runways, etc.
Since aircraft often land and/or takeoff at a relatively great distance from a terminal, good access to those distant points helps to improve the overall operational efficiency of an airport.
The design of the airfield taxiway system is intended to increase airfield capacity and enhance operational safety between arriving and departing aircraft. Throughout the Vermont system airports included in this program, taxiway development for the sake of increasing operational capacity can not be justified. This issue is typically limited to the nation's large air carrier airports. However, there are related safety concerns at these smaller commercial service and GA airports that should be addressed. This includes the need to avoid back-taxiing on active runways, especially at uncontrolled fields with commercial service and/or a relatively high number of larger GA aircraft operations.
4.3.3.1 - Taxiway Safety Area (TSA). The TSA is the imaginary surface surrounding the taxiway. The terrain in the TSA must be clear of objects to reduce the risk of damage to an airplane that unintentionally strays off the taxiway. The TSA must also incorporate the following characteristics:
4.3.3.2 - Distance from Taxiway Centerline to Fixed or Movable Object. The distance from the taxiway's centerline to a distance where no objects are allowed, even the maintenance and service road edges.
4.3.3.3 - Taxiway and Taxilane Object Free Area (OFA). A taxilane is the portion of the aircraft parking area used for access between taxiways and aircraft parking positions. The taxiway and taxilane OFAs are centered on the taxiway and taxilane centerlines. The taxiway and taxilane clearing standards prohibit service vehicle roads, parked airplanes, and above ground objects, except for objects that need to be there for navigational and aircraft ground maneuvering purposes. Vehicles may operate within the OFA provided they give the right-of-way to on-coming aircraft.
TABLE 4-13 Taxiway Standards
| TAXIWAY CHARACTERISTICS | DIMENSIONS | AIRPLANE DESIGN GROUP | |||||
| I | II | III | IV | V | VI | ||
| Taxiway Width | A | 25 ft. | 35 ft. | 50 ft. | 75 ft. | 75 ft. | 100 ft. |
| Taxiway Edge Safety Margin | 5 ft. | 7.5 ft. | 10 ft. | 15 ft. | 15 ft. | 20 ft. | |
| Taxiway Pavement
Fillet Configuration |
Refer to AC 150/5300-13 Change 5 | ||||||
| Taxiway Shoulder Width | 10 ft. | 10 ft. | 20 ft. | 25 ft. | 35 ft.5 | 40 ft.5 | |
| Taxiway Safety Area Width | B | 49 ft. | 79 ft. | 118 ft. | 171 ft. | 214 ft. | 262 ft. |
| Taxiway Object Free Area Width | 89 ft. | 131 ft. | 186 ft. | 259 ft. | 320 ft. | 386 ft. | |
| Taxilane Object Free Area Width | 79 ft. | 115 ft. | 162 ft. | 225 ft. | 276 ft. | 334 ft. | |
Notes:
1 Letters correspond to the dimensions on Taxiway Design Standards figure.
2 For airplanes in Airplane Design Group III with a wheelbase equal to or greater than 60 feet, the standard taxiway width is 60 feet.
3 The taxiway edge safety margin is the minimum acceptable distance between the outside of the airplane wheels and the pavement edge.
4 For airplanes in Airplane Design Group III with a wheelbase equal to or greater than 60 feet, the taxiway edge safety margin is 15 feet.
5 Airplanes in Airplane Design Groups V and VI normally require stabilized or paved taxiway shoulder surfaces.
Source: Advisory Circular 150/5300-13 Change 5 "Airport Design".

4.3.4 Airport Safety Standard Summary
The following tables summarize the Pertinent Development and Safety Standards for the 11 publically owned, public use general aviation airports in the Vermont Airport System. At the conclusion of these tables is a summary of the VAOT and FAA standards for the Vermont Airport system, which can be found in Table 4-14.
PERTINENT DEVELOPMENT AND SAFETY STANDARDS
| ||||||
|
FAA Safety Standards | ||||||
| Design Criteria
Airport Reference Code B-II |
Design Standards
(Runway Ends) |
Existing Conditions
(Runway Ends) |
Within
Standards | |||
| 2 | 20 | 2 | 20 | |||
| Runway Safety Area | Length | 300 feet | 300 | 300 | Yes | |
| Width | 150 feet | 150 | 150 | Yes | ||
| Runway Protection Zone (Should Own or Have Land Use Control Over Property in RPZ) | Length | 1,000 feet | - | No | ||
| Inner Width | 500 feet | - | No | |||
| Outer Width | 700 feet | - | No | |||
| Runway Object Free Area | Length Beyond Runway End | 300 feet | 300 | 300 | Yes | |
| Width | 500 feet | 500 | 500 | Yes | ||
| Part 77 Primary Surface Width | 500 feet | N/A | N/A | |||
| Taxiway Safety Area Width | 79 feet | 50 | No | |||
| Taxiway Object Free Area Width | 131 feet | 131 | Yes | |||
| Runway Width | 75 feet | 60 | No | |||
| Taxiway Width | 35 feet | 25 | No | |||
| Runway/Taxiway Separation | 240 feet | 225 | No | |||
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS (CONT.)
| ||
|
VAOT Development Standards | ||
|
Item |
Criteria | Within Standards |
| Aircraft Parking Aprons | Based on Transient and Based Aircraft Activity. | No |
| Fueling Systems | For attended airports, adequate supply of AVGas. Jet-A storage based on demand. | Yes |
| Terminal/Administrative Building | Minimum of 10 peak hour operations to warrant separate administrative building. Otherwise, provide phone, rest rooms, telephone recording, lounge and bulletin board. | Yes |
| Auto Parking | One public parking space for 50% of each based aircraft, and 1.5 parking spaces for each peak day itinerant operation. | No |
| VFR Airport NAVAIDS | Lighted Windsock | N/A |
| IFR Airport NAVAIDS | Lighted Windsock, AWOS, PAPI or equivalent for primary runway end, MIRLs, Rotating Beacon, Necessary Obstruction Lights, GCO, | No |
| Precision Approach | Minimum of five peak hour instrument operations, and the upgrade must provide a minimum of a 10% reduction in the ceiling or visibility minimums. | N/A |
| Security Fencing | Full perimeter fencing to the extent feasible. | No |
| Taxiway System | Full parallel taxiway for commercial service airports. For B-II ARC and greater, consider full or at a minimum a partial parallel taxiway to the primary runway end. | Yes |
| ALP | Update ALP at least every 10 years, or sooner if there are significant changes in the character of the airport. | Yes |
| ADA Compliance | All public facilities should be ADA compliant. | Yes |
| Picnic Facilities | Where appropriate and safe, picnic and/or camping facilities should be constructed at the airport for use by both the local population and itinerant pilots. | No |
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS
| Edward F. Knapp State Airport (MPV) | ||||||||||
| Design Criteria
Airport Reference Code B-II |
Design Standards | Existing Conditions
(Runway Ends) |
Within
Standards | |||||||
| 17 | 35 | 5 | 23 | 17 | 35 | 5 | 23 | |||
| Runway Safety Area | Length | 300 feet | 300 | 300 | 300 | 300 | Yes | |||
| Width | 150 feet | 100 | 100 | 100 | 100 | No | ||||
| Runway Protection Zone (Should Own or Have Land Use Control Over Property in RPZ) | Length | 1,000 feet | - | - | No | |||||
| Inner Width | 500 feet | - | - | No | ||||||
| Outer Width | 700 feet | - | - | No | ||||||
| Runway Object Free Area | Length Beyond Runway End | 300 feet | 300 | 300 | 300 | 300 | Yes | |||
| Width | 500 feet | 500 | 500 | 500 | 500 | Yes | ||||
| Part 77 Primary Surface Width | 500 feet | N/A | N/A | N/A | ||||||
| Taxiway Safety Area Width | 79 feet | 79 | Yes | |||||||
| Taxiway Object Free Area Width | 131 feet | 131 | Yes | |||||||
| Runway Width | 75 feet | 75 feet | 150 | 100 | Yes | |||||
| Taxiway Width | 35 feet | 35 | Yes | |||||||
| Runway/Taxiway Separation | 240 feet | 160 | 200 | No | ||||||
Source - 2000 Partial Master Plan Update, URS Greiner Woodward Clyde, Inc.
PERTINENT DEVELOPMENT AND SAFETY STANDARDS (CONT.)
| ||
|
VAOT Development Standards | ||
|
Item |
Criteria | Within Standards |
| Aircraft Parking Aprons | Based on Transient and Based Aircraft Activity. | No |
| Fueling Systems | For attended airports, adequate supply of AVGas. Jet-A storage based on demand. | Yes |
| Terminal/Administrative Building | Minimum of 10 peak hour operations to warrant separate administrative building. Otherwise, provide phone, rest rooms, telephone recording, lounge and bulletin board. | Yes |
| Auto Parking | One public parking space for 50% of each based aircraft, and 1.5 parking spaces for each peak day itinerant operation. | Yes |
| VFR Airport NAVAIDS | Lighted Windsock | N/A |
| IFR Airport NAVAIDS | Lighted Windsock, AWOS, PAPI or equivalent for primary runway end, MIRLs, Rotating Beacon, Necessary Obstruction Lights, GCO, | Yes |
| Precision Approach | Minimum of five peak hour instrument operations, and the upgrade must provide a minimum of a 10% reduction in the ceiling or visibility minimums. | Yes |
| Security Fencing | Full perimeter fencing to the extent feasible. | No |
| Taxiway System | Full parallel taxiway for commercial service airports. For B-II ARC and greater, consider full or at a minimum a partial parallel taxiway to the primary runway end. | No |
| ALP | Update ALP at least every 10 years, or sooner if there are significant changes in the character of the airport. | Yes |
| ADA Compliance | All public facilities should be ADA compliant. | Yes |
| Picnic Facilities | Where appropriate and safe, picnic and/or camping facilities should be constructed at the airport for use by both the local population and itinerant pilots. | No |
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS
| Fair Haven Municipal Airport (1B3) | ||||||
|
Design Criteria Airport Reference Code A-I |
Design Standards
(Runway Ends) |
Existing Conditions
(Runway Ends) |
Within
Standards | |||
| 2 | 20 | 2 | 20 | |||
| Runway Safety Area | Length | 240 feet | 240 | 240 |
Yes | |
| Width | 120 feet | 120 | 120 | Yes | ||
| Runway Protection Zone (Should Own or Have Land Use Control Over Property in RPZ) | Length | 1,000 feet | - | No | ||
| Inner Width | 250 feet | - | No | |||
| Outer Width | 450 feet | - | No | |||
| Runway Object Free Area | Length Beyond Runway End | 240 feet | 240 | 240 | Yes | |
| Width | 250 feet | 250 | 250 | Yes | ||
| Part 77 Primary Surface Width | 250 feet | N/A | N/A | |||
| Taxiway Safety Area Width | 49 feet | N/A | N/A | |||
| Taxiway Object Free Area Width | 89 feet | N/A | N/A | |||
| Runway Width | 60 feet | 50 | No | |||
| Taxiway Width | 25 feet | N/A | N/A | |||
| Runway/Taxiway Separation | 150 feet | N/A | Yes | |||
Data Source - 1988 Master Plan Update - Rist-Frost Associates, P.C.
PERTINENT DEVELOPMENT AND SAFETY STANDARDS (CONT.)
| ||
|
VAOT Development Standards | ||
|
Item |
Criteria | Within Standards |
| Aircraft Parking Aprons | Based on Transient and Based Aircraft Activity. | No |
| Fueling Systems | For attended airports, adequate supply of AVGas. Jet-A storage based on demand. | N/A |
| Terminal/Administrative Building | Minimum of 10 peak hour operations to warrant separate administrative building. Otherwise, provide phone, rest rooms, telephone recording, lounge and bulletin board. | N/A |
| Auto Parking | One public parking space for 50% of each based aircraft, and 1.5 parking spaces for each peak day itinerant operation. | No |
| VFR Airport NAVAIDS | Lighted Windsock | No |
| IFR Airport NAVAIDS | Lighted Windsock, AWOS, PAPI or equivalent for primary runway end, MIRLs, Rotating Beacon, Necessary Obstruction Lights, GCO, | N/A |
| Precision Approach | Minimum of five peak hour instrument operations, and the upgrade must provide a minimum of a 10% reduction in the ceiling or visibility minimums. | N/A |
| Security Fencing | Full perimeter fencing to the extent feasible. | No |
| Taxiway System | Full parallel taxiway for commercial service airports. For B-II ARC and greater, consider full or at a minimum a partial parallel taxiway to the primary runway end. | N/A |
| ALP | Update ALP at least every 10 years, or sooner if there are significant changes in the character of the airport. | No |
| ADA Compliance | All public facilities should be ADA compliant. | N/A |
| Picnic Facilities | Where appropriate and safe, picnic and/or camping facilities should be constructed at the airport for use by both the local population and itinerant pilots. | Yes |
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS
| Franklin County State Airport (FSO) | ||||||
| Design Criteria
Airport Reference Code B-II |
Design Standards
(Runway Ends) |
Existing Conditions
(Runway Ends) |
Within
Standards | |||
| 1 | 19 | 1 | 19 | |||
| Runway Safety Area | Length | 300 feet | 300 | 200 | No | |
| Width | 150 feet | 150 | 150 | Yes | ||
| Runway Protection Zone (Should Own or Have Land Use Control Over Property in RPZ) | Length | 1,000 feet | - | No | ||
| Inner Width | 500 feet | - | No | |||
| Outer Width | 700 feet | - | No | |||
| Runway Object Free Area | Length Beyond Runway End | 300 feet | 300 | 300 | Yes | |
| Width | 500 feet | 500 | 500 | Yes | ||
| Part 77 Primary Surface Width | 500 feet | N/A | N/A | |||
| Taxiway Safety Area Width | 79 feet | 79 | Yes | |||
| Taxiway Object Free Area Width | 131 feet | 131 | Yes | |||
| Runway Width | 75 feet | 60 | No | |||
| Taxiway Width | 35 feet | 20 | No | |||
| Runway/Taxiway Separation | 240 feet | N/A | N/A | |||
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS (CONT.)
| ||
|
VAOT Development Standards | ||
|
Item |
Criteria | Within Standards |
| Aircraft Parking Aprons | Based on Transient and Based Aircraft Activity. | No |
| Fueling Systems | For attended airports, adequate supply of Avgas. Jet-A storage based on demand. | Yes |
| Terminal/Administrative Building | Minimum of 10 peak hour operations to warrant separate administrative building. Otherwise, provide phone, rest rooms, telephone recording, lounge and bulletin board. | Yes |
| Auto Parking | One public parking space for 50% of each based aircraft, and 1.5 parking spaces for each peak day itinerant operation. | No |
| VFR Airport NAVAIDS | Lighted Windsock | N/A |
| IFR Airport NAVAIDS | Lighted Windsock, AWOS, PAPI or equivalent for primary runway end, MIRLs, Rotating Beacon, Necessary Obstruction Lights, GCO, | No |
| Precision Approach | Minimum of five peak hour instrument operations, and the upgrade must provide a minimum of a 10% reduction in the ceiling or visibility minimums. | N/A |
| Security Fencing | Full perimeter fencing to the extent feasible. | No |
| Taxiway System | Full parallel taxiway for commercial service airports. For B-II ARC and greater, consider full or at a minimum a partial parallel taxiway to the primary runway end. | No |
| ALP | Update ALP at least every 10 years, or sooner if there are significant changes in the character of the airport. | Yes |
| ADA Compliance | All public facilities should be ADA compliant. | Yes |
| Picnic Facilities | Where appropriate and safe, picnic and/or camping facilities should be constructed at the airport for use by both the local population and itinerant pilots. | No |
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS
| Hartness State Airport (VSF) | ||||||||||
| Design Criteria
Airport Reference Code B-II (R/W 5-23) Airport Reference Code B-I (R/W 11-29) |
Design Standards
(Runway Ends) |
Existing Conditions
(Runway Ends) |
Within
Standards | |||||||
| 5 | 23 | 11 | 29 | 5 | 23 | 11 | 29 | |||
| Runway Safety Area | Length | 300 ft | 240 ft | 100 | 100 | 150 | 150 | No | ||
| Width | 150 ft | 120 ft | 150 | 150 | 150 | 150 | Yes | |||
| Runway Protection Zone (Should Own or Have Land Use Control Over Property in RPZ) | Length | 1,000 ft | 250 ft | - | - | No | ||||
| Inner Width | 500 ft | 450 ft | - | - | No | |||||
| Outer Width | 700 ft | 450 ft | - | - | No | |||||
| Runway Object Free Area | Length beyond runway end | 300 ft | 240 ft | 300 | 300 | 240 | 240 | Yes | ||
| Width | 500 ft | 400 ft | 500 | 500 | 400 | 400 | Yes | |||
| Part 77 Primary Surface Width | 1000 ft | 500 ft | N/A | N/A | N/A | |||||
| Taxiway Safety Area Width | 79 feet | 79 | Yes | |||||||
| Taxiway Object Free Area Width | 131 feet | 131 | Yes | |||||||
| Runway Width | 75 feet | 60 feet | 100 | 75 | Yes | |||||
| Taxiway Width | 35 feet | 35 | Yes | |||||||
| Runway/Taxiway Separation | 240 ft | N/A | N/A | N/A | ||||||
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS (CONT.)
| ||
|
VAOT Development Standards | ||
|
Item |
Criteria | Within Standards |
| Aircraft Parking Aprons | Based on Transient and Based Aircraft Activity. | Yes |
| Fueling Systems | For attended airports, adequate supply of Avgas. Jet-A storage based on demand. | Yes |
| Terminal/Administrative Building | Minimum of 10 peak hour operations to warrant separate administrative building. Otherwise, provide phone, rest rooms, telephone recording, lounge and bulletin board. | Yes |
| Auto Parking | One public parking space for 50% of each based aircraft, and 1.5 parking spaces for each peak day itinerant operation. | Yes |
| VFR Airport NAVAIDS | Lighted Windsock | N/A |
| IFR Airport NAVAIDS | Lighted Windsock, AWOS, PAPI or equivalent for primary runway end, MIRLs, Rotating Beacon, Necessary Obstruction Lights, GCO, | Yes |
| Precision Approach | Minimum of five peak hour instrument operations, and the upgrade must provide a minimum of a 10% reduction in the ceiling or visibility minimums. | N/A |
| Security Fencing | Full perimeter fencing to the extent feasible. | No |
| Taxiway System | Full parallel taxiway for commercial service airports. For B-II ARC and greater, consider full or at a minimum a partial parallel taxiway to the primary runway end. | No |
| ALP | Update ALP at least every 10 years, or sooner if there are significant changes in the character of the airport. | Yes |
| ADA Compliance | All public facilities should be ADA compliant. | Yes |
| Picnic Facilities | Where appropriate and safe, picnic and/or camping facilities should be constructed at the airport for use by both the local population and itinerant pilots. | Yes |
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS
| John H. Boylan State Airport (5B1) | ||||||
| Design Criteria
Airport Reference Code A-I |
Design Standards
(Runway Ends) |
Existing Conditions
(Runway Ends) |
Within
Standards | |||
| 14 | 32 | 14 | 32 | |||
| Runway Safety Area | Length | 240 feet | 100 | 25 | No | |
| Width | 120 feet | 120 | 100 | No | ||
| Runway Protection Zone (Should Own or Have Land Use Control Over Property in RPZ) | Length | 1,000 feet | - | No | ||
| Inner Width | 250 feet | - | No | |||
| Outer Width | 450 feet | - | No | |||
| Runway Object Free Area | Length Beyond Runway End | 240 feet | 240 | 240 | Yes | |
| Width | 250 feet | 250 | 250 | Yes | ||
| Part 77 Primary Surface Width | 250 feet | N/A | N/A | |||
| Taxiway Safety Area Width | 49 feet | N/A | N/A | |||
| Taxiway Object Free Area Width | 89 feet | N/A | N/A | |||
| Runway Width | 60 feet | 100 | Yes | |||
| Taxiway Width | 25 feet | N/A | N/A | |||
| Runway/Taxiway Separation | 150 feet | N/A | N/A | |||
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS (CONT.)
| ||
|
VAOT Development Standards | ||
|
Item |
Criteria | Within Standards |
| Aircraft Parking Aprons | Based on Transient and Based Aircraft Activity. | Yes |
| Fueling Systems | For attended airports, adequate supply of Avgas. Jet-A storage based on demand. | N/A |
| Terminal/Administrative Building | Minimum of 10 peak hour operations to warrant separate administrative building. Otherwise, provide phone, rest rooms, telephone recording, lounge and bulletin board. | N/A |
| Auto Parking | One public parking space for 50% of each based aircraft, and 1.5 parking spaces for each peak day itinerant operation. | No |
| VFR Airport NAVAIDS | Lighted Windsock | Yes |
| IFR Airport NAVAIDS | Lighted Windsock, AWOS, PAPI or equivalent for primary runway end, MIRLs, Rotating Beacon, Necessary Obstruction Lights, GCO, | N/A |
| Precision Approach | Minimum of five peak hour instrument operations, and the upgrade must provide a minimum of a 10% reduction in the ceiling or visibility minimums. | N/A |
| Security Fencing | Full perimeter fencing to the extent feasible. | No |
| Taxiway System | Full parallel taxiway for commercial service airports. For B-II ARC and greater, consider full or at a minimum a partial parallel taxiway to the primary runway end. | N/A |
| ALP | Update ALP at least every 10 years, or sooner if there are significant changes in the character of the airport. | Yes |
| ADA Compliance | All public facilities should be ADA compliant. | N/A |
| Picnic Facilities | Where appropriate and safe, picnic and/or camping facilities should be constructed at the airport for use by both the local population and itinerant pilots. | No |
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS
Airport Reference Code B-I (Runway Ends) (Runway Ends) Standards
Middlebury State Airport (6BO) Design Criteria
Design Standards
Existing Conditions
Within
1
19
1
19
Runway Safety Area
Length
240 feet
150
240
No
Width
120 feet
120
120
Yes Runway Protection Zone
(Should Own or Have Land
Use Control Over Property
in RPZ)
Length
1,000 feet
-
No
Inner
Width
500 feet
-
No
Outer
Width
700 feet
-
No Runway Object Free Area
Length
Beyond
Runway
End
240 feet
240
240
Yes
Width
250 feet
250
250
Yes Part 77 Primary Surface Width
500 feet
N/A
N/A Taxiway Safety Area Width
79 feet
79
Yes Taxiway Object Free Area Width
131 feet
131
Yes Runway Width
60 feet
50
No Taxiway Width
35 feet
25
No Runway/Taxiway Separation
240 feet
150
No
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS (CONT.)
VAOT Development Standards Item
Middlebury State Airport (6BO)
Criteria
Within
Standards Aircraft Parking Aprons
Based on Transient and Based Aircraft Activity.
Yes Fueling Systems
For attended airports, adequate supply of Avgas. Jet-A
storage based on demand.
Yes Terminal/Administrative
Building
Minimum of 10 peak hour operations to warrant separate
administrative building. Otherwise, provide phone, rest
rooms, telephone recording, lounge and bulletin board.
Yes Auto Parking
One public parking space for 50% of each based aircraft,
and 1.5 parking spaces for each peak day itinerant operation.
Yes VFR Airport NAVAIDS
Lighted Windsock
Yes IFR Airport NAVAIDS
Lighted Windsock, AWOS, PAPI or equivalent for primary
runway end, MIRLs, Rotating Beacon, Necessary
Obstruction Lights, GCO,
N/A Precision Approach
Minimum of five peak hour instrument operations, and
the upgrade must provide a minimum of a 10% reduction
in the ceiling or visibility minimums.
N/A Security Fencing
Full perimeter fencing to the extent feasible.
No Taxiway System
Full parallel taxiway for commercial service airports. For B-II ARC and greater, consider full or at a minimum a partial
parallel taxiway to the primary runway end.
Yes ALP
Update ALP at least every 10 years, or sooner if there are
significant changes in the character of the airport.
Yes ADA Compliance
All public facilities should be ADA compliant.
No Picnic Facilities
Where appropriate and safe, picnic and/or camping facilities
should be constructed at the airport for use by both the local
population and itinerant pilots.
No
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS
Airport Reference Code B-II (Runway Ends) (Runway Ends) Standards
Morrisville-Stowe State Airport (MVL) Design Criteria
Design Standards
Existing Conditions
Within
1
19
1
19
Runway Safety Area
Length
300 feet
100
200
No
Width
150 feet
150
150
Yes Runway Protection Zone
(Should Own or Have Land
Use Control Over Property in
RPZ)
Length
1,000 feet
-
No
Inner
Width
500 feet
-
No
Outer
Width
700 feet
-
No Runway Object Free Area
Length
Beyond
Runway
End
300 feet
300
Yes
Width
500 feet
500
Yes Part 77 Primary Surface Width
500 feet
N/A
N/A Taxiway Safety Area Width
79 feet
79
Yes Taxiway Object Free Area Width
131 feet
131
Yes Runway Width
75 feet
75
Yes Taxiway Width
35 feet
20
No Runway/Taxiway Separation
240 feet
N/A
N/A
Data Source - December 1990 Master Plan Update, Gerry W. D'Amico, P.E.
PERTINENT DEVELOPMENT AND SAFETY STANDARDS (CONT.)
VAOT Development Standards Item
Morrisville-Stowe State Airport (MVL)
Criteria
Within
Standards Aircraft Parking Aprons
Based on Transient and Based Aircraft Activity.
? Fueling Systems
For attended airports, adequate supply of Avgas. Jet-A
storage based on demand.
Yes Terminal/Administrative
Building
Minimum of 10 peak hour operations to warrant separate
administrative building. Otherwise, provide phone, rest
rooms, telephone recording, lounge and bulletin board.
Yes Auto Parking
One public parking space for 50% of each based aircraft,
and 1.5 parking spaces for each peak day itinerant operation.
Yes VFR Airport NAVAIDS
Lighted Windsock
N/A IFR Airport NAVAIDS
Lighted Windsock, AWOS, PAPI or equivalent for primary
runway end, MIRLs, Rotating Beacon, Necessary
Obstruction Lights, GCO,
No Precision Approach
Minimum of five peak hour instrument operations, and
the upgrade must provide a minimum of a 10% reduction
in the ceiling or visibility minimums.
N/A Security Fencing
Full perimeter fencing to the extent feasible.
No Taxiway System
Full parallel taxiway for commercial service airports. For B-II ARC and greater, consider full or at a minimum a partial
parallel taxiway to the primary runway end.
No ALP
Update ALP at least every 10 years, or sooner if there are
significant changes in the character of the airport.
No ADA Compliance
All public facilities should be ADA compliant.
Yes Picnic Facilities
Where appropriate and safe, picnic and/or camping facilities
should be constructed at the airport for use by both the local
population and itinerant pilots.
Yes
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS
Airport Reference Code B-II (Runway Ends) (Runway Ends) Standards
Newport State Airport (EFK) Design Criteria
Design Standards
Existing Conditions
Within
5
23
18
36
5
23
18
36
Runway Safety Area
Length
300 feet
300
50
300
300
No
Width
150 feet
150
150
150
150
Yes Runway Protection Zone
(Should Own or Have Land
Use Control Over Property in
RPZ)
Length
1,000 feet
-
No
Inner
Width
500 feet
-
No
Outer
Width
700 feet
-
No Runway Object Free Area
Length
Beyond
Runway
End
300 feet
300
300
300
300
Yes
Width
500 feet
500
500
500
500
Yes Part 77 Primary Surface Width
500 feet
N/A
N/A
N/A Taxiway Safety Area Width
79 feet
79
Yes Taxiway Object Free Area Width
131 feet
131
Yes Runway Width
75 feet
75 feet
150
100
Yes Taxiway Width
35 feet
50
Yes Runway/Taxiway Separation
240 feet
N/A
N/A
N/A
Source - 2000 Partial Master Plan Update, Dubois & King.
PERTINENT DEVELOPMENT AND SAFETY STANDARDS (CONT.)
VAOT Development Standards Item
Newport State Airport (EFK)
Criteria
Within
Standards Aircraft Parking Aprons
Based on Transient and Based Aircraft Activity.
No Fueling Systems
For attended airports, adequate supply of Avgas. Jet-A
storage based on demand.
Yes Terminal/Administrative
Building
Minimum of 10 peak hour operations to warrant separate
administrative building. Otherwise, provide phone, rest
rooms, telephone recording, lounge and bulletin board.
Yes Auto Parking
One public parking space for 50% of each based aircraft,
and 1.5 parking spaces for each peak day itinerant operation.
Yes VFR Airport NAVAIDS
Lighted Windsock
N/A IFR Airport NAVAIDS
Lighted Windsock, AWOS, PAPI or equivalent for primary
runway end, MIRLs, Rotating Beacon, Necessary
Obstruction Lights, GCO,
No Precision Approach
Minimum of five peak hour instrument operations, and
the upgrade must provide a minimum of a 10% reduction
in the ceiling or visibility minimums.
N/A Security Fencing
Full perimeter fencing to the extent feasible.
Yes Taxiway System
Full parallel taxiway for commercial service airports. For B-II ARC and greater, consider full or at a minimum a partial
parallel taxiway to the primary runway end.
No ALP
Update ALP at least every 10 years, or sooner if there are
significant changes in the character of the airport.
Yes ADA Compliance
All public facilities should be ADA compliant.
Yes Picnic Facilities
Where appropriate and safe, picnic and/or camping facilities
should be constructed at the airport for use by both the local
population and itinerant pilots.
No
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS
Airport Reference Code C-II Runway 1-19 B-II Runway 13-31 (Runway Ends) (Runway Ends) Standards Runway
End
Design Criteria
Design Standards
Existing Conditions
Within
1
19
13
31
1
19
13
31
Runway Safety Area
Length
1,000 ft
300 ft
300
300
295
240
No
Width
500 ft
150 ft
400
400
150
150
No Runway Protection Zone
(Should Own or Have Land
Use Control Over Property in
RPZ)
Length
1,700 ft
1000 ft
-
-
No
Inner
Width
500 ft
500 ft
-
-
No
Outer
Width
1,010 ft
700 ft
-
-
No Runway Object Free Area
Length
Beyond
1,000 ft
300 ft
1000
300
Yes
Width
800 ft
500 ft
800
800
500
500
Yes Part 77 Primary Surface Width
500 ft
N/A
N/A
N/A Taxiway Safety Area Width
79 feet
79
Yes Taxiway Object Free Area Width
131 feet
131
Yes Runway Width
100 feet
75 feet
100
75
Yes Taxiway Width
35 feet
35
Yes Runway/Taxiway Separation
300 feet
240 feet
Varies
N/A
No
Source - 2000 Partial Master Plan Update, URS Greiner Woodward Clyde, Inc.
PERTINENT DEVELOPMENT AND SAFETY STANDARDS (CONT.)
VAOT Development Standards Item
Rutland State Airport (RUT)
Criteria
Within
Standards Aircraft Parking Aprons
Based on Transient and Based Aircraft Activity.
No Fueling Systems
For attended airports, adequate supply of Avgas. Jet-A
storage based on demand.
Yes Terminal/Administrative
Building
Minimum of 10 peak hour operations to warrant separate
administrative building. Otherwise, provide phone, rest
rooms, telephone recording, lounge and bulletin board.
Yes Auto Parking
One public parking space for 50% of each based aircraft,
and 1.5 parking spaces for each peak day itinerant operation.
Yes VFR Airport NAVAIDS
Lighted Windsock
N/A IFR Airport NAVAIDS
Lighted Windsock, AWOS, PAPI or equivalent for primary
runway end, MIRLs, Rotating Beacon, Necessary
Obstruction Lights, GCO,
Yes Precision Approach
Minimum of five peak hour instrument operations, and
the upgrade must provide a minimum of a 10% reduction
in the ceiling or visibility minimums.
No Security Fencing
Full perimeter fencing to the extent feasible.
No Taxiway System
Full parallel taxiway for commercial service airports. For B-II ARC and greater, consider full or at a minimum a partial
parallel taxiway to the primary runway end.
No ALP
Update ALP at least every 10 years, or sooner if there are
significant changes in the character of the airport.
Yes ADA Compliance
All public facilities should be ADA compliant.
Yes Picnic Facilities
Where appropriate and safe, picnic and/or camping facilities
should be constructed at the airport for use by both the local
population and itinerant pilots.
No
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS
Airport Reference Code B-II (Runway Ends) (Runway Ends) Standards
William H. Morse State Airport (5B5) Design Criteria
Design Standards
Existing Conditions
Within
13
31
13
31
Runway Safety Area
Length
300 feet
300
200
No
Width
150 feet
150
150
Yes Runway Protection Zone
(Should Own or Have
Land Use Control Over
Property in RPZ)
Length
1,000 feet
-
No
Inner
Width
500 feet
-
No
Outer
Width
700 feet
-
No Runway Object Free Area
Length
beyond
runway
end
300 feet
300
300
Yes
Width
500 feet
500
500
Yes Part 77 Primary Surface Width
500 feet
N/A
N/A Taxiway Safety Area Width
79 feet
79
Yes Taxiway Object Free Area Width
131 feet
131
Yes Runway Width
75 feet
75
Yes Taxiway Width
35 feet
35
Yes Runway/Taxiway Separation
240 feet
N/A
N/A
Source: Dufresne-Henry Analysis
PERTINENT DEVELOPMENT AND SAFETY STANDARDS (CONT.)
VAOT Development Standards Item
William H. Morse State Airport (5B5)
Criteria
Within
Standards Aircraft Parking Aprons
Based on Transient and Based Aircraft Activity.
No Fueling Systems
For attended airports, adequate supply of Avgas. Jet-A
storage based on demand.
Yes Terminal/Administrative
Building
Minimum of 10 peak hour operations to warrant separate
administrative building. Otherwise, provide phone, rest
rooms, telephone recording, lounge and bulletin board.
Yes Auto Parking
One public parking space for 50% of each based aircraft,
and 1.5 parking spaces for each peak day itinerant operation.
Yes VFR Airport NAVAIDS
Lighted Windsock
N/A IFR Airport NAVAIDS
Lighted Windsock, AWOS, PAPI or equivalent for primary
runway end, MIRLs, Rotating Beacon, Necessary
Obstruction Lights, GCO,
No Precision Approach
Minimum of five peak hour instrument operations, and
the upgrade must provide a minimum of a 10% reduction
in the ceiling or visibility minimums.
N/A Security Fencing
Full perimeter fencing to the extent feasible.
No Taxiway System
Full parallel taxiway for commercial service airports. For B-II ARC and greater, consider full or at a minimum a partial
parallel taxiway to the primary runway end.
No ALP
Update ALP at least every 10 years, or sooner if there are
significant changes in the character of the airport.
Yes ADA Compliance
All public facilities should be ADA compliant.
Yes Picnic Facilities
Where appropriate and safe, picnic and/or camping facilities
should be constructed at the airport for use by both the local
population and itinerant pilots.
No
Source: Dufresne-Henry Analysis
TABLE 4-14 VAOT and FAA Standards
| Reference
Section |
Item | Criteria/
Dimensions |
|
VAOT Development Standards | ||
| 4.2.1 | Aircraft Parking Aprons | Based on Transient and Based Aircraft Activity. Calculate area for 30% of peak day activity of transient aircraft, and 50% of total number of based aircraft. |
| 4.2.2 | Hangar Demand | Since hangars are constructed with private funds, development will be accomplished as needed. Space should be set aside for hangars as summarized in Table 4-5. |
| 4.2.3 | Fueling Systems | For attended airports, adequate supply of Avgas. Jet-A storage based on demand. |
| 4.2.4 | Terminal/Administrative Building | Minimum of 10 peak hour operations to warrant a
separate administrative building. Otherwise, provide
phone, rest rooms, telephone recording, lounge and
bulletin board.
Commercial service airports should provide access to public transportation. Intermodal access to other transportation networks should be encouraged. |
| 4.2.5 | Auto Parking | One public parking space for 50% of each based aircraft, and 1.5 parking spaces for each peak day itinerant operation. |
| 4.2.7.1 | VFR Airport NAVAIDS | Lighted Windsock |
| 4.2.7.2 | IFR Airport NAVAIDS | Lighted Windsock, AWOS, PAPI or equivalent for primary runway end, MIRLs, Rotating Beacon, Necessary Obstruction Lights, GCO |
| 4.2.8 | Precision Approach Upgrade | Minimum of five peak hour instrument operations, and the upgrade must provide a minimum of a 10% reduction in the ceiling or visibility minimums. FAA concurrence is required. |
| 4.2.9 | Security Fencing | Full perimeter fencing to the extent feasible. |
| 4.2.10 | Taxiway System | Full parallel taxiway for commercial service airports. For B-II ARC and greater, consider full or at a minimum a partial parallel taxiway to the primary runway end. |
| 4.2.11 | ALP | All airports should have an ALP update at least every 10 years, or sooner if there are significant changes in the character of the airport. |
| 4.2.12 | ADA Compliance | All public facilities should be ADA compliant. |
| 4.2.13 | Maintenance of Infrastructure | Priority should be given to projects which maintain existing infrastructure. |
| 4.2.14 | Picnic Facilities | Where appropriate and safe, picnic and/or camping facilities should be constructed at the airport for use by both the local population and itinerant pilots. |
|
FAA Safety Standards | ||
| 4.3.2.1 | Runway Safety Area - Width and Length Beyond Runway End | Based on Airplane Approach Category, Airplane Design Group and Visibility |
| Approach Category A & B
Visual Approach and Not Lower than 3/4 Mile I - 120 ft Wide, 240 ft. beyond Runway End II - 150 ft Wide, 300 ft. beyond Runway End III - 300 ft Wide, 600 ft. beyond Runway End IV - 500 ft Wide, 1000 ft. beyond Runway End Lower than 3/4 Mile I-III - 300 ft Wide, 600 ft. beyond Runway End IV - 500 ft Wide, 1000 ft. beyond Runway End | ||
| Approach Category C & D
500 ft Wide, 1000 ft. beyond Runway End | ||
| 4.3.2.2 | Runway Protection Zone | Dimensions based on approach minimums, aircraft size and aircraft approach categories. (See Table 4-11). FAA policy is to either own or have easement control over RPZs. |
| 4.3.2.3 | Runway Object Free Area Width and Length Beyond Runway End | Based on Airplane Approach Category, Airplane Design Group and Visibility |
| Approach Category A & B
Visual Approach and Not Lower than 3/4 Mile I - 250 ft Wide, 240 ft. beyond Runway End II - 500 ft Wide, 300 ft. beyond Runway End III - 800 ft Wide, 600 ft. beyond Runway End IV - 800 ft Wide, 1000 ft. beyond Runway End Lower than 3/4 Mile I - 800 ft Wide, 240 ft. beyond Runway End II - 800 ft Wide, 600 ft. beyond Runway End III - 800 ft Wide, 800 ft. beyond Runway End IV - 800 ft Wide, 1000 ft. beyond Runway End | ||
| Approach Category C & D
800 ft Wide, 1000 ft. beyond Runway End | ||
| 4.3.2.6 | Primary Surface Width | Width Based on Airport Use and Approach Category |
| Utility Runway
Visual Approach - 250 ft Non-precision Approach - 500 ft. | ||
| Other Then Utility Runway
Visual Approach - 250 ft Non-precision Approach, >3/4 Mile - 500 ft. Non-precision Approach, <3/4 Mile - 1000 ft. Precision Approach, - 1000 ft. | ||
| 4.3.2.8 | Runway Line of Sight | Two points five feet above runway must be mutually visible along entire runway length. |
| 4.3.3 | Taxiway Width | Based on Airplane Design Group
I - 25 ft. II - 35 ft. III - 50 ft. IV, V - 75 ft. VI - 100 ft. |
| 4.3.3.1 | Taxiway Safety Area Width | Based on Airplane Design Group
I - 49 ft. II - 79 ft. III - 118 ft. IV - 171 ft. V - 214 ft. VI - 262 ft. |
| 4.3.3.3 | Taxiway Object Free Area Width | Based on Airplane Design Group
I - 89 ft. II - 131 ft. III - 186 ft. IV - 259 ft. V - 320 ft. VI - 386 ft. |
| 4.3.3.3 | Taxilane Object Free Area Width | Based on Airplane Design Group
I - 79 ft. II - 115 ft. III - 162 ft. IV - 225 ft. V - 276 ft. VI - 334 ft. |
SECTION 5 - PROJECT EVALUATION
5.0 PROJECT RANKING METHODOLOGY
With the establishment of the Project Prioritization System and the identification of potential air capital facility projects, the next step in the development of the prioritized list of projects involved the input of the project into the computer model, evaluating the projects based on the established criteria, and then calculating a project rating score. To demonstrate how this was done, a fictional project consisting of a transient apron expansion was utilized (see Figure 1), and the rating of this project is demonstrated as follows:
1. Airport Operations. Estimated annual operations at the XYZ Airport are 24,500, therefore 50 points were awarded.
2. Based Aircraft. There are 48 aircraft based at the XYZ Airport, therefore 50 points were awarded.
3. Geographic Proximity. The estimated driving time to a populated area of 7,500 people or more, in this case Megatropolis, is 10 minutes. This driving time is awarded 6 points.
4. Governmental Support. This criteria is broken into three subcriteria - Total Meeting Attendance, History of Local Support, and Airport Zoning. The evaluation of each is described below.
4A - Total Meeting Attendance. Attendance at the three public meetings held in support of the Airport Capital Facility Program in 1999 averaged 12 people. When compared to an overall average of 20 people attending these meetings at the other airports, this is fairly low attendance, particularly given the fact that the airport is only 10 minutes from Megatropolis. For these reasons, this criteria was given a score of 2 points.
4B - History of Local Support. The XYZ Airport has not historically had a great deal of visible support, but in 1999 there has been a noticeable increase in the level of support from local businesses, the local Chamber of Commerce, the Town, and the Regional Planning Commission. In December, the Village and the Town both passed resolutions of support for the continuing improvements at the airport. Based on these activities, criteria 4B was given a score of 4 points.
4C - Zoning Addressing Protection of the Airport. The Town of Megatropolis has in place zoning which restricts residential development adjacent to XYZ Airport. It also limits the height of industrial buildings in the vicinity of the airport. In recognition of this zoning, criteria 4C was given a score of 6 points.
Total Points for Criteria 4 - Governmental Support. The level of Governmental Support was rated a 12 out of a possible 20 points.
5. Economic Development. The fixed base operator indicated in a letter to VAOT that if the proposed apron expansion were to be constructed, he would be able to provide additional overnight tie-down parking for 10 transient aircraft that must now be turned away and sent to an adjacent airport. Assuming an average of 30 overnight transient aircraft per week, and a tiedown fee of $20, this will result in an annual revenue increase of $31,200. This level of annual economic benefit results in a score of 12 points.
6. Special Program/Multi-Year. This project is not a multi-year program that is currently underway, nor has it been designated by VAOT to have particular support or special interest. It therefore was given no points under this category.
7. Project Type. This criteria is broken into two subcriteria - Project Type, and Pavement Condition Index Rating. The evaluation of each is described below.
7A - Project Type. The proposed project is a transient aircraft parking apron, and was therefore given 80 points under this subcriteria.
7B - Pavement Condition Index Rating. The pavement condition index rating only applies for construction activities involving existing pavements. Since this is a new apron, no points were given under this criteria.
Total Points for Criteria 7 - Project Type. The Project Type criteria was given a score of 80 points.
8. FAA Priority Points. The National Plan of Integrated Airport Systems (NPIAS) Project Priority System ranks projects eligible for FAA funding based on airport activity, project purpose (capacity, planning, reconstruction, etc.), facility component (runway, apron, building, etc.), and project type (construction, master planning, visual approach aids, etc.). As can be seen in the NPIAS Project Evaluation Table (Figure 2), for an Airport Code C (at least 20 based aircraft or 8,000 itinerant operations), the expansion of an existing apron is awarded 44 points. VAOT's proposed project evaluation system then translates the NPIAS Ranking score to a scale of 0 to 10 points. For this particular project, 10 points were awarded. A complete copy of the NPIAS Project Priority System can be found in Appendix C.
9. Upgrade to Standards. This project does not upgrade the airport to FAA safety standards, therefore, no points were awarded in this category.
10. VAOT Development Standards. Section 4.2.1 defines the appropriate levels of apron development, based on the anticipated number of based and itinerant aircraft. Currently, this level of activity warrants an additional 15,000 square feet of apron area, which is being proposed under this project. Since the apron expansion that is being considered fully meet a VAOT Development Standard, this criteria was given a score of 100 points.
11. Previously Programmed Federal/State Aid. There is no currently identified Federal or State funding for this project, therefore no points were awarded.
12. Cost/Benefit. This criteria only applies to projects costing less than $75,000, and therefore no points were awarded.
13. Resource Impact. The proposed apron is located in a disturbed area, adjacent to the existing apron. There are no wetlands, forested woodlands, or areas of potential archeological or historical significance shown on the Airport Layout Plan for this site. Since no impact to resources in anticipated, this criteria was given the maximum 40 points.
Insert Figure 2 (NPIAS Scoresheet)
14. Local Interest and Support. This criteria is broken into two subcriteria - Project Support, and Project Opposition. The evaluation of each is described below.
14A - Project Support. In December, the Village and the Town both passed resolutions of support for the expansion of the itinerant aircraft apron at the airport. The fixed base operator indicated in a letter to VAOT that the proposed apron expansion was necessary to provide additional overnight tie-down parking for transient aircraft that must now be turned away and sent to an adjacent airport. He also attached three letters from businesses who indicated that they would utilize the XYZ airport on a weekly or monthly basis for bringing in corporate executives if sufficient apron space were available. Based on this level of support, 15 points were awarded under this subcriteria.
14B - Project Opposition. No letters of opposition were received for this project, therefore, no negative points were awarded under this subcriteria.
Total Points for Criteria 14. Local Interest and Support. The Local Interest and Support criteria was given a score of 15 points.
The total of points given for each criteria results in a project rating score of 375.
5.1 PLANNING LEVEL COST ESTIMATES
The costs identified for the development of the capital improvement projects are planning level only, and for the most part were estimated without the benefit of any level of design effort. They are meant to give only an order-of-magnitude cost for the program, and should not be used for anything other than the development of an overall State-wide aviation funding program. The estimated costs for the identified projects are based on the level of information known about the project, the airport conditions (soil types, environmental constraints, etc.), the assumed limits of construction, etc. As projects are selected and funded for planning and/or design, more specific project costs should be developed early on in the planning stages, and the budgets should be adjusted accordingly.
5.2 AVIATION CAPITAL PROJECT SUMMARY
The following two tables summarize the ranking of the Vermont Airport Capital Facility Program projects identified under this program, and reflects the results of the prioritization model during the initial program development in 1999 and 2000. The "0 - 5 Year Development Program" list of projects served as the basis of the State FY 2001 Aviation Program. The "6 - 20 Year Development Program" listing will serve as a pool of projects to pull from each year as completed projects are removed from the program. For a more detailed discussion of the "6 - 20 Year Development Program" list, see Section 7.2.4.
The reader is directed to Appendix B, where all project evaluation worksheets for the 0 - 5 Year Development Program and the 6 - 20 Year Development Program can be found.
VERMONT AIRPORT CAPITAL FACILITY PROGRAM
0 - 5 YEAR DEVELOPMENT PROGRAM
| RANK | AIRPORT | PROJECT NAME | COST | SCORE |
| 1 | Newport | Runway 18-36 Rehabilitation | $1,500,000 | 459 |
| 2 | E. F. Knapp | Fueling Apron/Taxiway | $100,000 | 457 |
| 3 | Caledonia County | Airfield/Runway Lighting | $650,000 | 452 |
| 4 | Rutland | MALSR Land Acquisition | $900,000 | 428 |
| 5 | W. H. Morse | Ground Communication Outlet | $15,000 | 412 |
| 6 | John H. Boylan | Turf Runway Improvements | $10,000 | 412 |
| 7 | John H. Boylan | Obstruction Removal | $30,000 | 411 |
| 8 | E. F. Knapp | Rehabilitate Runway 17-35 | $1,500,000 | 401 |
| 9 | Middlebury | Rehabilitate Fueling Apron | $15,000 | 389 |
| 10 | Rutland | Rehabilitate Taxiway B | $25,000 | 388 |
| 11 | Rutland | Rehabilitate Taxiway A | $18,000 | 388 |
| 12 | Morrisville-Stowe | Install VASI | $25,000 | 382 |
| 13 | Franklin County | Rehabilitate Southeast Transient Apron | $55,000 | 375 |
| 14 | Franklin County | RSA Improvements | $275,000 | 375 |
| 15 | Morrisville-Stowe | Master Plan Update | $100,000 | 370 |
| 16 | Franklin County | Airport Campground | $5,000 | 365 |
| 17 | Rutland | Hangar Site Prep. | $100,000 | 365 |
| 18 | Middlebury | Terminal / Hangar Replacement | $1,000,000 | 362 |
| 19 | Rutland | Airport Campground | $5,000 | 360 |
| 20 | Middlebury | Airport Campground | $5,000 | 359 |
| 21 | Newport | Runway 5-23 Rehabilitation | $600,000 | 358 |
| 22 | Caledonia County | Rehabilitate Taxiway B | $20,000 | 358 |
| 23 | Hartness | Repair Obstruction Beacons/Lights | $225,000 | 356 |
| 24 | Franklin County | Apron (South) | $350,000 | 355 |
| 25 | Franklin County | Ground Communication Outlet | $15,000 | 355 |
| 26 | W. H. Morse | RSA Improvements | $275,000 | 350 |
| 27 | E. F. Knapp | Rehabilitate Taxiway A | $75,000 | 349 |
| 28 | Hartness | RSA Improvements | $150,000 | 346 |
| 29 | Caledonia County | Rehabilitate Runway 2-20 | $450,000 | 344 |
| 30 | Caledonia County | Ground Communication Outlet | $15,000 | 341 |
| 31 | W. H. Morse | Airport Campground | $5,000 | 340 |
| 32 | Newport | Taxiway A Rehabilitation | $70,000 | 333 |
| 33 | Hartness | Rehabilitate Apron | $115,000 | 331 |
| 34 | Hartness | Parking Lot Improvements | $10,000 | 330 |
| 35 | Caledonia County | Airport Campground | $5,000 | 326 |
| 36 | Newport | Airport Campground | $5,000 | 321 |
| 37 | W. H. Morse | PAPI Installation, Runway 13 | $30,000 | 316 |
| 38 | Morrisville-Stowe | Remove Ground Penetrations | $1,000,000 | 316 |
| 39 | E. F. Knapp | Rehabilitate Runway 5-23 | $480,000 | 315 |
| 40 | W. H. Morse | Runway Turn Around | $55,000 | 312 |
| 41 | Newport | AWOS Installation | $65,000 | 311 |
| 42 | Rutland | R/W 19 Safety Area | $3,865,000 | 310 |
| 43 | Middlebury | Obstruction Removal | $100,000 | 309 |
| 44 | John H. Boylan | RSA Improvements | $32,000 | 308 |
| 45 | Rutland | Parallel Taxiway | $420,000 | 302 |
| 46 | Caledonia County | PAPI Study, Installation | $30,000 | 302 |
| 47 | Franklin County | Security Fencing | $50,000 | 300 |
| 48 | Franklin County | Obstruction Removal | $100,000 | 295 |
| 49 | Fair Haven Municipal | Master Plan Update | $75,000 | 293 |
| 50 | E. F. Knapp | Parking Lot Improvements | $100,000 | 291 |
| 51 | W. H. Morse | Obstruction Removal | $100,000 | 290 |
| 52 | John H. Boylan | Airport Campground | $5,000 | 288 |
| 53 | Franklin County | Runway Extension | $820,000 | 287 |
| 54 | E. F. Knapp | Partial Parallel Taxiway | $275,000 | 279 |
| 55 | E. F. Knapp | Easement Acquisition | $120,000 | 279 |
| 56 | E. F. Knapp | Transient Ramp | $100,000 | 277 |
| 57 | Rutland | Apron Lighting | $70,000 | 270 |
| 58 | Middlebury | T-Hangar Site | $80,000 | 269 |
| 59 | Hartness | Obstruction Removal | $100,000 | 266 |
| 60 | Newport | Transient Ramp | $300,000 | 265 |
| 61 | W. H. Morse | Aircraft Parking Apron | $234,000 | 260 |
| 62 | Rutland | Perimeter Fencing | $52,000 | 260 |
| 63 | Fair Haven Municipal | GPS Approach | $0 | 259 |
| 64 | Caledonia County | Easement Acquisition | $32,000 | 256 |
| 65 | Franklin County | Hangar Site Prep. | $10,000 | 255 |
| 66 | Caledonia County | Obstruction Removal | $100,000 | 254 |
| 67 | W. H. Morse | Security Fencing | $63,000 | 240 |
| 68 | W. H. Morse | Easements | $32,000 | 240 |
| 69 | Caledonia County | T-Hangar Site Prep. | $12,000 | 239 |
| 70 | Hartness | Rehabilitate Hangar 6 | $63,000 | 239 |
| 71 | Rutland | Sand Storage Shed | $35,000 | 238 |
| 72 | E. F. Knapp | Pedestrian Walkway | $5,000 | 237 |
| 73 | Rutland | Snow Removal Equipment | $350,000 | 230 |
| 74 | E. F. Knapp | Land Acquisition | $125,000 | 227 |
| 75 | Hartness | T-Hangar Site Development | $17,000 | 226 |
| 76 | Fair Haven Municipal | Telephone/Restroom Facilities | $15,000 | 219 |
| 77 | Rutland | Terminal Improvements | $90,000 | 218 |
| 78 | W. H. Morse | T-Hangar Access Road | $30,000 | 186 |
| 79 | Fair Haven Municipal | Hangar Site Prep. | $10,000 | 169 |
| 80 | John H. Boylan | Terminal Improvements | $50,000 | 158 |
| TOTALS | $18,415,000 |
Source: Various Vermont Airport Master Plans and Airport Layout Plan Reports
VERMONT AIRPORT CAPITAL FACILITY PROGRAM
6 - 10 YEAR PROJECT LISTING
| RANK | AIRPORT | PROJECT NAME | COST | SCORE* |
| 1 | Morrisville-Stowe | Install VASI | $75,000 | 328 |
| 2 | Middlebury | Runway Extension | $800,000 | 324 |
| 3 | Rutland | Reconstruct/Overlay Runway 1-19 | $1,400,000 | 322 |
| 4 | Rutland | Reconstruct/Expand Terminal Apron | $765,000 | 298 |
| 5 | Franklin County | Install PAPI | $45,000 | 298 |
| 6 | E. F. Knapp | Reconstruct Terminal Apron | $225,000 | 284 |
| 7 | Caledonia County | Runway Extension/Relocation | $1,500,000 | 284 |
| 8 | Newport | Drainage Improvements, Runway 18-36 | $250,000 | 282 |
| 9 | Middlebury | Security Fencing | $75,000 | 272 |
| 10 | Franklin County | Security Fencing | $50,000 | 272 |
| 11 | Franklin County | Construct Parallel Taxiway | $775,000 | 264 |
| 12 | Middlebury | Extend Parallel Taxiway | $500,000 | 262 |
| 13 | Rutland | Parallel Taxiway, Runway 1 | $304,000 | 258 |
| 14 | Middlebury | Aircraft Parking Apron | $240,000 | 254 |
| 15 | Franklin County | Expand Aircraft Parking Apron (I) | $300,000 | 252 |
| 16 | John H. Boylan | Construct Paved Runway | $1,000,000 | 252 |
| 17 | Franklin County | Expand Aircraft Parking Apron (II) | $200,000 | 252 |
| 18 | Rutland | Construct Apron, Access Taxiway | $275,000 | 248 |
| 19 | Rutland | Parallel Taxiway, Runway 31 | $200,000 | 248 |
| 20 | Rutland | Apron Expansion | $102,000 | 246 |
| 21 | Morrisville-Stowe | Runway Reconstruction/Extension | $4,000,000 | 246 |
| 22 | W. H. Morse | Partial Parallel Taxiway | $250,000 | 244 |
| 23 | W. H. Morse | Parallel Taxiway, Runway 31 End | $1,000,000 | 244 |
| 24 | E. F. Knapp | Airport Campground | $5,000 | 242 |
| 25 | E. F. Knapp | Parallel Taxiway, Runways 5 and 17 | $600,000 | 242 |
| 26 | Hartness | Full Parallel Taxiway | $1,500,000 | 238 |
| 27 | E. F. Knapp | Reconstruct Taxiways A, B & C | $320,000 | 236 |
| 28 | Rutland | Runway 1-19 Lighting | $70,000 | 234 |
| 29 | E. F. Knapp | Parallel Taxiway, Runway 23 | $378,000 | 234 |
| 30 | E. F. Knapp | Apron Expansion | $220,000 | 234 |
| 31 | W. H. Morse | Apron Expansion | $250,000 | 232 |
| 32 | Caledonia County | Install Airfield Fencing | $40,000 | 230 |
| 33 | Hartness | Stub Taxiway, Runway 11 | $250,000 | 228 |
| 34 | Rutland | Perimeter Fencing | $35,000 | 226 |
| 35 | Hartness | Expand Aircraft Parking Apron | $335,000 | 226 |
| 36 | Caledonia County | Parallel Taxiway | $825,000 | 224 |
| 37 | Franklin County | Runway Extension | $820,000 | 224 |
| 38 | E. F. Knapp | Easement Acquisition - R/W 5 RPZ | $175,000 | 222 |
| 39 | Rutland | Perimeter Fencing | $35,000 | 216 |
| 40 | Rutland | Terminal Expansion | $81,000 | 215 |
| 41 | Caledonia County | T-Hangar Apron and Sitework | $175,000 | 214 |
| 42 | E. F. Knapp | Perimeter Fencing | $52,000 | 212 |
| 43 | W. H. Morse | Runway Extension | $2,000,000 | 204 |
| 44 | E. F. Knapp | Perimeter Fencing | $52,000 | 202 |
| 45 | John H. Boylan | Security Fencing | $75,000 | 198 |
| 46 | Rutland | Precision Approach, Runway 19 | $1,170,000 | 186 |
| 47 | Rutland | Land Acquisition | $1,130,000 | 186 |
| 48 | Rutland | Land Acquisition | $540,000 | 186 |
| 49 | Newport | Runway 18-36 Extension | $2,000,000 | 184 |
| 50 | John H. Boylan | Aircraft Parking Apron | $560,000 | 182 |
| 51 | Rutland | Snow Removal & Grass Equipment | $275,000 | 176 |
| 52 | Fair Haven Municipal | Expand Aircraft Parking Apron | $925,000 | 172 |
| 53 | E. F. Knapp | Industrial Park Land Acquisition | $2,000,000 | 170 |
| 54 | W. H. Morse | Land Acquisition | $150,000 | 170 |
| 55 | E. F. Knapp | Grass Mowing Equipment | $75,000 | 170 |
| 56 | Rutland | Electrical Vault | $325,000 | 162 |
| 57 | Rutland | New Airport Road | $500,000 | 162 |
| 58 | E. F. Knapp | Snow Removal Equipment | $200,000 | 160 |
| 59 | Fair Haven Municipal | Airfield Lighting | $400,000 | 146 |
| 60 | Fair Haven Municipal | Vehicle Parking Lot | $37,500 | 146 |
| 61 | Fair Haven Municipal | Construct Paved Runway | $1,680,000 | 144 |
| 62 | Fair Haven Municipal | 500 Foot Runway Extension | $2,275,000 | 144 |
| 63 | E. F. Knapp | High Mast Lighting, Terminal Area | $70,000 | 140 |
| 64 | Caledonia County | Terminal/State Office Building | $750,000 | 128 |
| 65 | Fair Haven Municipal | Stub Taxiway & Apron | $325,000 | 124 |
| 66 | Fair Haven Municipal | Install 10,000 gallon AVGas Tank | $75,000 | 92 |
| TOTALS |
$38,086,500 |
Source: Various Vermont Airport Master Plans and Airport Layout Plan Reports
* Project Score Does Not Include Criteria 5, 12B or 14. See Section 7.2.4 for additional information
SECTION 6 - FINANCIAL OVERVIEW
6.0 INTRODUCTION
The financial overview section of this report is intended to focus on two primary issues: first, to provide a synopsis of the aviation funding mechanisms and procedures for the Vermont Airport system, and second, to define the levels of investment necessary to maintain and develop the system over the next five years. The following sections will define the various funding sources, restrictions on use of these funds, historic fiscal requirements, and projections for future expenditures.
6.1 VERMONT AVIATION BUDGET REQUEST COMPONENTS
All expenditures for maintenance and improvements at the Vermont System Airports must be included in the annual VAOT budget request, and approved by the State Legislature. The budget is comprised of four primary components: State-Owned Airport Capital Improvements, Burlington International Airport (BIA) Capital Improvements, State-Owned Airport Maintenance program, and State Aviation Administration. As the scope of this program is limited to aviation capital improvements, the latter two funding requirements will not be addressed here.
It must be emphasized that the potential exists for a fifth budget component - State funding for improvements at the Fair Haven Municipal Airport. Similar to BIA, Fair Haven is a publically owned, public use airport that is eligible for State funds to match Federal Aviation Administration (FAA) Airport Improvement Program (AIP) grants. While VAOT has no statutory obligation to provide financial assistance to Fair Haven or Burlington, under Title 5, Section 691 of Vermont Law, the State can provide financial assistance for projects funded by the FAA. Specifically, this statues states:
§ 691. GRANTS BY STATE
For the purpose of developing adequate air facilities for this state through assistance to municipalities in the acquirement, construction, expansion, enlargement, or improvement of an airport in this state, the secretary is authorized to grant from available appropriations to a municipality a sum not exceeding three-fifths of the sum of the local matching funds required to support funds granted by the federal government. However, for the construction, expansion, enlargement or improvement of airports sponsored by the state of Vermont in conjunction with the federal government, the amount of state funds may match as necessary the sum granted by the federal government.
While Fair Haven has not recently requested funding to supplement FAA grants, under Title 5 the State is enabled to provide up to 6% of an approved project's total cost, with the FAA providing 90% and the Town of Fair Haven paying the remaining 4%.
6.2 TYPICAL FUNDING SOURCES
Funding for capital projects at airports in the State of Vermont is derived from either local, State or Federal sources, or combinations thereof. Sections 6.2.1. through 6.2.4 provide additional information on the types of funds available for the various airport, historic funding levels, and limitations placed on the availability and use of these funds.
6.2.1. State-Owned Airports Funding. Capital improvements at the ten state-owned airports are typically funded by FAA AIP State Apportionment Funds, FAA AIP Discretionary funds, or State Appropriations. The AIP State Apportionments that are annually provided to Vermont are approximately $750,000. Typically these grants are reserved for larger projects, such as runway reconstructions or new taxiway systems. Since these projects tend to cost in excess of $750,000, the State must combine consecutive apportionments over two or three years, until sufficient money is available for the construction. In addition to the annual State Apportionment, Vermont can pursue discretionary funds from the FAA under this same program. While there is no programmed amount of money set aside for Vermont for discretionary projects, if there is sufficient justification for the project (typically for safety reasons), the FAA may provide a discretionary grant above and beyond the State Apportionment. Both of these grants require matching funds. For State-owned airports, this match is 10% of an approved project's total cost, with the FAA providing the remaining 90%.
To be eligible for FAA funding, the projects must be on a Federally approved Airport Layout Plan (ALP). The ALP is a detailed drawing of the airport and its surrounding environs, with proposed development depicted on the drawing. The grants are approved by the FAA on a case-by-case basis, with safety enhancement projects having priority over all other projects. Once funds are allocated, they can only be expended on the approved project, and cannot be transferred.
The third typical funding source for capital project at the State-owned airports is State Appropriations. These projects are 100% State funded under VAOT's Annual Transportation Bill.
Figure 6-1 graphically depicts historical legislative appropriation levels for Vermont's State-Owned Airports. As can be seen from this graphic, from 1992 to 1999, State appropriation for aviation capital improvement projects has averaged $464,000, and the State FY 2000 budget had a significant funding increase to a level of $2.07 million. During this same time period the level of FAA Airport Improvement Program (AIP) funding has seen a much greater variation, with $2.3 million (this includes the State matching funds for the grant) being provided in 1997, compared to $45,000 in 1998. The reason for this variation, as discussed earlier, is due to the relatively low level of State Apportionment funding provided by the FAA to VAOT each year. Because these funds are generally saved for up to 3 years, and then dispersed to complete the construction of a large project, there are periods of time where little or no federal funds are expended.

Source: VAOT Capital Program and Project Development Plans (SY 1994 - 2000)
6.2.2. Burlington International Airport Funding. Capital improvements at the Burlington International Airport (BIA) are typically funded by FAA AIP Entitlement Funds, FAA AIP Discretionary funds, State Appropriation Funds (6% of FAA grant), Local funding (4% of FAA grant), and Passenger Facility Charges (PFC's). The AIP grant program is identical for both the State-Owned Airports and BIA, however, Burlington has specific set-aside "entitlement" funds based on it's designation as a commercial service airport. The entitlement appropriations that are annually provided to BIA are approximately $2,250,000. The State provides a 6% match of an approved project's total cost, with the City of Burlington providing the remaining 4%.
In addition to the FAA grant program and State matching appropriations, BIA funds major projects under the PFC program. The PFC fee is imposed as an additional $3 charge included in each airline ticket for each passenger arriving or departing BIA. The recently completed terminal expansion and parking garage projects were funded under this program, and additional projects are expected to be funded similarly. Since these funds are derived and spent locally, and not passed through the State, they are not included in the historic or projected funding levels.
Figure 6-2 graphically depicts the historical legislative appropriation levels for BIA.
6.2.3. Fair Haven Municipal Airport Funding. Capital improvements at the Fair Haven Municipal Airport can be funded through three sources - FAA AIP Discretionary funds, State Appropriation Funds (6% of FAA grant), and Local funding (4% of FAA grant, as well as 100% locally funded projects). The AIP grant program, again, is identical for both the State-Owned Airports and Fair Haven, however, Fair Haven is only eligible for discretionary funding. In 1988 an FAA grant was issued for a Master Plan, but since then, no funding has been approved by the FAA or the State.
6.2.4. Other Airport Funding Sources. In addition to the previously described "typical" funding sources, VAOT has been increasingly looking to less traditional routes to obtain funds for aviation projects. In fact, one of the project evaluation criteria under this program is "Project Interest and Support", where points are awarded for projects with committed local funding support. An example of this is a runway extension feasibility study being undertaken at the Morrisville-Stowe State Airport, which is funded by the Lamoille County Planning Commission. Similarly, supporters of the John Boylan State Airport have stated that they are willing to undertake an obstruction removal (i.e., tree clearing) project at the airport using volunteer labor, if VAOT would define the areas to be cleared.
VAOT has also been successful in utilizing Federal Highway Administration SPR funds for State-Wide Aviation Planning projects, such as the Airport Capital Facility Planning. The successor to this program, the FHWA Transportation Equity Act for the 21st Century (TEA-21) may also offer similar creative funding alternatives.

Source: VAOT Capital Program and Project Development Plans (SY 1994 - 2000)
6.3 VERMONT AIRPORT CAPITAL FACILITY PROGRAM FUNDING
Before a discussion of annual aviation funding requirements is undertaken, a cautionary note on the funding requirements presented here is in order. It must be emphasized that the projects shown in this program represent a "snapshot" of the airport needs at one particular point in time. It is fully expected that as this program is implemented, additional needs will be identified and added to project lists, and some projects which have been previously slated for completion will be eliminated. This is a normal part of the aviation programming process, and should be expected. Each year that VAOT utilizes the procedures summarized in this report, they should do so with an eye towards carefully evaluating the proposed projects to ensure that they should be pursued. The vast majority of the projects were identified during Master Planning efforts which were undertaken during 1999 and 2000. In this time period, 9 of the 10 State-owned airports were undergoing various types of planning studies, none of which were completed at the time of the writing of this report. Upon completion of these studies, it is possible, and even likely, some modifications to the project lists will occur. As this occurs, the program should be adjusted to add, remove, or modify the impacted projects.
It also must be noted that the costs identified for the development of the capital improvement projects are planning level costs only, and for the most part were estimated without the benefit of any level of design effort. They are meant to give only an order-of-magnitude cost for the program, and should not be used for anything other than the development of an overall State-wide aviation funding program. The estimated costs for the identified projects are based on the level of information known about the project, the airport conditions (soil types, environmental constraints, etc.), the assumed limits of construction, etc. As projects are selected and funded for planning and/or design, more specific project costs should be developed early on in the planning stages, and the budgets should be adjusted accordingly.
Section 5 summarized the total anticipated funding requirements for the Vermont Airport Capital Facility Program for the State-Owned Airports, and the Fair Haven Municipal Airport for a period of 20 years. It was estimated that during the next five years, a total of 80 projects with a combined cost of $18.4 million will need to be accomplished. This project cost total is based upon the short-term (0 - 5 year planning horizon) needs at the airports, as defined in the most recent Airport Master Plans. These projects are primarily rehabilitation and safety orientated, and are necessary to counter the previous policy of delaying necessary capital improvements, as was identified in the 1998 Vermont Airport System Policy Plan.
For the 6-20 year planning period, a total of 66 projects with a combined cost of $38.1 million has been identified to be accomplished at the 10 State-Owned Airports, and the Fair Haven Municipal Airport. These projects tend to include major construction, such as runway extensions, which may not prove to be economically viable. Since projections beyond the first 5 years are not particularly definitive, for the purposes of this report only the first five year program will be addressed.
In addition to these funding needs, the Burlington International Airport Year Capital Improvement Program (See Appendix D) indicates that the airport will be seeking a total of $469,000 in State matching funds over the next 5 years, or an average of $94,000 annually. These funds will be used to match a total of approximately $7,040,000 in AIP grants.
6.3.1. Annual Funding Requirements. The dollar volume of projects completed each year will vary, depending primarily on the funding levels provided to VAOT in the Transportation Bill. All funding for aviation capital projects in Vermont must be approved by Legislature in the annual VAOT budget. This includes all State and FAA AIP funds for both State Owned and Municipally Owned Airports. All appropriations are for a 12 month period, and unexpended monies must be approved for use in the following State Fiscal Year, or they do not carry over.
For estimating purposes, an average annual cost to undertake the 5 Year Capital Facility Program presented in Section 5 is assumed by dividing the total program cost by the five year period. This results in an anticipated annual funding budget of $3.68 million, not including the estimated State Apportionment and FAA AIP funding needs of the Burlington International Airport, which is $7,509,000. AIP funding is in flux as of the writing of this report, with a new bill stalled in Congress. Two versions of this bill are under consideration, both of which provide significant increases in funding over the current bill. Since it does not appear that resolution of the bill is likely before this report is finalized, it is assumed that the current AIP State Apportionment funding level of approximately $750,000 annually will remain constant.
Given that $3,680,000 has been estimated as an annual budget to accomplish the 5 Year program (State-Owned Airports and Fair Haven Municipal Airport only), and FAA State Apportionments are anticipated to remain at the $750,000 level, $2,930,000 will need to be funded annually, either from the Transportation Bill, or other alternative sources. Compared to the proposed State FY 2001 budget of $2,363,000, this will require a 24% aviation budget increase. As was stated earlier, the funding for these primarily rehabilitation and safety orientated projects are necessary to counter the previous policy of delaying necessary capital improvements.
Figure 6-3 summarizes VAOT's estimated aviation funding requirements for the next five years, which includes State and Federal Funding for the Vermont Airport System.

Source: D-H Analysis
SECTION 7 - UPDATING PROCEDURES
7.0 UPDATING OVERVIEW
With the development of the Airport Capital Facility Program completed in early 2000, the next phase of this program is implementation, beginning with the annual updating phase. As a natural progression of the extension public support elements of this project, VAOT has developed a set of procedures to solicit the advice of the public, airport users, and interested parties as the upcoming airport capital program is being developed. This section describes the procedures that should be undertaken, commencing in late spring, as VAOT undertakes the next cycle of capital project development.
7.1 PUBLIC NOTIFICATION
At the conclusion of the initial stage of this program, a mailing list was formalized, drawing from individuals representing towns, villages and cities associated with the airports; regional planning commissions; industrial development authorities; chambers of commerce; pilots and users groups; airport tenants; transportation advisory committees; and utilizing addresses provided on the meeting attendance sheets of the over 40 meetings that were held in conjunction with the development of the program. The resulting list of interested parties is in excess of 500 individuals. This information will serve as the backbone of the public notification process.
In mid-April of each year an announcement should be sent to all individuals who are on the current mailing list notifying them of the date, time and location of the public information meetings, as well as a concise summary of the items to be discussed. In addition, a legal ad and a press release should be sent to all newspapers that cover areas in which the airports are located to provide even greater coverage of the meetings.
An sample public announcement, legal ad and press release follow, as well as contact phone numbers for newspapers that should be contacted at least 3 weeks prior to the meetings:
SAMPLE MEETING ANNOUNCEMENT

SAMPLE LEGAL NOTICE

SAMPLE PRESS RELEASE
TABLE 7-1 NEWSPAPER CONTACTS
| NEWSPAPER | LOCATION | PHONE | FAX | DAILY OR
WEEKLY |
| The Bennington Banner | Bennington | 447-7567 | 442-3413 | Daily |
| The Burlington Free Press | Burlington | 863-3441 | 862-5622 | Daily |
| The Caledonian Record | St. Johnsbury | 748-8121 | 748-1613 | Daily |
| The Newport Daily Express | Newport | 334-6568 | 334-6891 | Daily |
| The Rutland Herald | Rutland | 775-5511 | 775-2423 | Daily |
| St. Albans Messenger | St. Albans | 524-9771 | 527-1948 | Daily |
| The Times Argus | Barre-Montpelier | 479-0191 | 479-4032 | Daily |
| The Addison Independent | Middlebury | 388-4944 | 388-3100 | Weekly |
| The Reporter | Springfield | 885-2246 | 885-9821 | Weekly |
| News and Citizen | Morrisville | 888-2212 | 888-2173 | Weekly |
7.2 PUBLIC MEETING PREPARATION
Prior to holding the public information meetings, there are several items which VAOT must accomplish. The first task should be to hold an internal working meeting with appropriate VAOT staff to review the agenda, and complete the preliminary ranking of the upcoming five year aviation capital program. In addition, at the next scheduled State Aviation Council meeting, a briefing should be held to update the council on the public meetings.
7.2.1. Public Meeting Agenda. It is essential that a thorough meeting agenda be prepared and adhered to throughout the public meeting process. One point that was made very clear in the 44 public meetings held during the preparation of this program - information presented at the meetings must be consistent, to eliminate the appearance of favoritism or bias towards an airport or project. A draft agenda which can be used as the base for VAOT's public meetings follows.
7.2.1.1 - Program Background And Overview. The meetings should be opened with an
overview of the development of the Capital Facility Program, and a discussion of the public
involvement process that was utilized throughout the process.
7.2.1.2 - Project Prioritization Model. Although most people will likely have some familiarity of the project prioritization model, some may not, and an overview of the model is in order. Handouts that should be used for this portion of the meeting include a copy of the evaluation worksheet (specific to the airport meeting, if possible), and the criteria definition sheet. A copy of the criteria definition sheet can be found in Chapter 2. Because this could be a lengthy discussion, the focus should be on the criteria which the local parties can have input on - i.e., Criteria 4, Governmental & Local Support; Criteria 5, Economic Development; Criteria 12B, Benefit (if project is less than $75,000); and Criteria 14, Project Interest and Support.
7.2.1.3 - Overview of Airport Activity Levels. The current number of based aircraft and annual operations should be reviewed with the public, airport users and airport manager. If significant changes have occurred in the last year that impact these numbers, the appropriate change in Criteria 1, Airport Operations and Criteria 2, Based Aircraft should be made.
7.2.1.4 - Review of 2000 Aviation Program. VAOT should take this opportunity to discuss the current year's program, and to inform the public on major airport issues. Projects that are currently underway should be reviewed, and any work that is anticipated to begin later in the calendar year should be discussed. Also, any state-wide or national aviation topics that would be of interest to the airport's could be brought up at this time.
7.2.1.5 - Draft 2001 Ranking of 5-year Aviation Program. The preliminary prioritized list of projects to be undertaken in the next five years should be presented to the meeting attendees. VAOT should be cautioned to not let the meeting get bogged down in a discussion of "us and them" - i.e., the focus should be on planned projects for the subject airport, and not on what other airports have planned for improvements. The intent of this portion of the meeting is show project trends, and the overall scope of project development.
During this portion of the presentation, it is likely that new projects will be suggested for consideration. VAOT should acknowledge the potential to consider these projects, but must make it clear to the audience that only projects which are either specifically addressed in the Airport Master Plan, or will not conflict with development depicted on the ALP will be considered. Occasionally, some projects which may be suggested fall under the category of maintenance projects (See Section 1.2 for maintenance and capital project definitions). If this is the case, VAOT should point out that bi-annual maintenance meetings are held at each airport, and the project will be identified in this meeting.
7.2.1.6 - Review of Airport Project Evaluations. As a natural transition from the broad view of the overall five year program, the meeting should now focus on the specific projects at the subject airport. Copies of the project evaluation worksheets should be handed out, and the description should be discussed to ensure the audience is clear on the specifics of the projects. Similar to the earlier discussion on the project prioritization model, most of the time should be spent on Criteria 4, 5, 12B and 14. VAOT must make it very clear at this point in the meeting that the rankings are preliminary, were based on discussions with the users during the previous year, and VAOT is open to their input on modifications to the scores.
7.2.1.7 - Documentation of Local Support. The discussion of documentation of local support is really a continuation of the discussion of Airport Project Evaluations. VAOT should present to the audience a summary of documentation (if any) that has been received in the previous year demonstrating local support of the airport and specific projects. Opposition which has been documented should also be presented. The need for documentation of the level of support should be re-iterated, and perhaps VAOT should consider providing some particularly effective examples of letters or resolutions of support that have been received that could be useful for the airport to use as a template. A deadline of 4 to 6 weeks from the meeting date should be set for acceptance of addition documented support or opposition. In fairness to the airports, this deadline should be established as a specific period of time from the meeting, to ensure airports which have earlier meetings are not given more time to respond than airports with meetings at the end of the schedule.
7.2.1.8 - Open Discussion. This final topic should be an open forum for any items of discussion that the public wishes to bring up.
7.2.2. Meeting Locations. The draft meeting announcement indicates suggested locations for the public meetings. Based on experience from the previous meetings, these locations should provide sufficient space for the anticipated attendance. VAOT should contact the airport managers prior to sending out the announcements to get a sense for the level of interest for these meetings. If interest is particularly high, an alternative meeting location may be desirable. The meeting announcement also states that refreshments will be provided. This is an effective way to increase attendance, particularly since the meeting is held during the normal dinner hour.
7.2.3. Record Keeping. Throughout the year, it is expected that correspondence (letters, e-mail, resolutions, meeting minutes, etc.) will be sent to VAOT regarding support or opposition to airports and/or specific projects planned to be undertaken at the airports. As this information is received, copies should be filed in one central location for use during the project evaluations. Two folders should be established for each airport, one for support of or opposition to the airport, and one for support of or opposition to projects at the airport. In many cases one item of may be sent regarding support of both the airport and specific projects. In this case, a copy of the letter should be filed in both folders. Prior to the draft prioritization meeting (discussed in Section 7.2.4.1), copies of these files should be made and distributed to the appropriate VAOT staff.
7.2.4. Draft Prioritization of Projects. Prior to the public meetings, VAOT must prepare a preliminary ranking of the 5 year aviation capital program. For the meetings to be held in 2000, this list of projects has already been identified as the 0 - 5 Year Development Program, which can be found in Section 5. For subsequent years, projects from the 6 - 20 Year Development Program must be used to select additional projects to be added to the current program, to replace projects which have been completed and removed from the program. The recommended procedure to determine the number of projects to move forward onto the current program is to add the top ranked projects whose cumulative score equals 110% of the current year funding level. For example, if in 2000 approximately $2.5 million were spent on aviation capital projects, then projects totaling approximately $2.75 million should be moved from the 6 - 20 Year Development Program into the 5 year program.
Projects from the 6 - 20 Year Development Program will have already been scored in all the criteria except those requiring public input - i.e., 5, 12B, and 14. These criteria should be left at zero, and the public support of opposition shown during the meetings can be used to rank these criteria.
7.2.4.1 - Preliminary Ranking Meeting. Because of the significant time required to do a thorough evaluation of projects, it is recommended that pertinent VAOT staff set aside at least one day in a remote location (the DTA's office at the EF Knapp State Airport has been used in the past, and may be an appropriate location), to review all the projects in the 5 Year Program. Correspondence which has been received from the previous year should be reviewed to determine the levels of support for the airport and the projects.
Criteria 1 and 2 should not be modified without any information from an airport, or from data obtained through VAOT operations counts, in the preliminary ranking meeting. As a result of the public input, however, this may warrant changes based on increases or decreases to airport activity. There should be no modifications to Criteria 3, 7, 8, 9, 10 and 13 unless the criteria definition has been changed. Unless this is the case, these scores will not change as long as the project remains in the 5 Year Development Plan.
It is highly recommended that VAOT evaluate Criteria 4 for all airports prior to any other review of criteria. It is important to get a strong sense of the support for all the airports as a whole, so the individual airports can be ranked in comparison with the others. It is also recommended that the justification for the scores which are given under criteria 4 are documented, so that the inevitable challenge as to the rationale for a low score (as perceived by the supporters of the airport) can be addressed without ambiguity.
The next criteria to be tackled is 5, Economic Development. If no documented information has been provided as to the economic impact of the proposed project, then this criteria must be given a score of zero. If documentation has been received, then the economic benefit, if it has not already been calculated, must be determined. If the documentation indicates that the project will result in additional jobs, then the benefit should be calculated utilizing an assumed annual salary. For lack of any information, a salary of $30,000 should be used. If additional revenue is anticipated as a result of the project, this revenue should not include any secondary economic impact. All measurement of benefit should be direct, and not indirect or induced.
Criteria 6, Special Program/Multi-Year Funding should only be given a score if VAOT is in the midst of a multi-year program of development, a portion of which is the project under consideration. The subjective ranking portion of this criteria should only be incorporated after the public informational meeting, and is to be used at VAOT's discretion to add additional point to projects as it deems appropriate.
If funds have been programmed for the project, then Criteria 11, Previously Programmed Federal or State Aid must be evaluated. Otherwise, this criteria is scored as a zero.
Criteria 12 addresses the benefit of lower cost projects. VAOT must evaluate the benefit of the project, which can be based on correspondence, or on VAOT's expectations of the project benefit.
Finally, Criteria 14 must be evaluated based only on documentation received by VAOT. This documentation must be thoroughly reviewed, as this is a subjective area that cannot be easily measured.
7.2.4.2 - Meeting Minutes. At the completion of the preliminary ranking meeting, a set of meeting minutes should be prepared which summarizes all scoring decisions made during the working session. This document will no doubt be useful to refer to when VAOT is called to justify their scoring decisions, especially for the "softer" issues of support and economic development or benefit.
7.2.4.3 - Computerized Data Entry. During the preliminary ranking meeting, scores assigned to the projects should be directly entered into the AIMS module. If this is not possible (e.g., the meeting is held at a remote site, and VAOT does not have the software loaded onto a portable computer, then the information should be manually summarized, then entered into the AIMS module. Because it extremely helpful to see preliminary rankings as scores are entered into the computer model, VAOT is strongly encouraged to have a copy of the software installed on a laptop computer that can be used during this working session.
7.3 COMMENT PERIOD
As was discussed in Section 7.2.1.7, a period of four to six weeks should be provided to allow for public input on the project rankings. This schedule should be enforced, and correspondence received after the due date should not be considered in the finalization of the current year program. Late correspondence should included in the airport correspondence files for use in the following year's project evaluation.
7.4 FINALIZATION OF PROJECT EVALUATIONS
At the conclusion of the comment period, VAOT should reconvene the evaluation team to consider modifications of the project scores. The items to be considered are similar to the items addressed in Section 7.2.4.1. Again, it is strongly recommended that modifications to project scores be documented in the form of meeting minutes for future reference.
7.5 PRESENTATION OF REVISED PROGRAM TO SAC
When the project evaluations have been finalized, the revised 5 Year program should be presented before the State Aviation Council at their next regularly scheduled meeting.
7.6 DISTRIBUTION OF PROJECT EVALUATION WORKSHEETS
The finalized project evaluation worksheets and 5 Year Development Program should be distributed as follows:
TABLE 7-2
DISTRIBUTION OF PROJECT EVALUATIONS
|
Entity |
Project
Worksheets |
5 Year
Development Program |
| Airport Manager | I | X |
| Airport User Group | I | X |
| Regional Planning Commission | C | X |
| State Aviation Council | X |
Key: I - Individual Worksheets for the Specific Airport Only
C - Comprehensive Package of All Worksheets in the 5 Year Program
In addition to this distribution list, VAOT staff members will have access to the worksheets via the computerized project evaluation program, and can generate additional copies of the sheets as necessary. It is anticipated that initially either hard copies or electronic media will be used to distribute the project evaluation worksheets. At an appropriate time, consideration should be given to posting the project worksheets on VAOT's web page for general public access.
7.7 ANNUAL PROGRAM FUNDING
Each year VAOT will be committing a significant amount of manpower to update the Vermont Airport Capital Facility Program, as outlined in this Section. It is estimated that approximately 120 man-hours will be required from the Policy & Planning Division and the Maintenance & Aviation Division to accomplish this work. Steps should be taken to fund this effort on an annual basis, and to budget sufficient funds for expenses related to the program, such as reproductions costs, conference room rentals, refreshments at meetings, etc.
VERMONT AIRPORT CAPITAL FACILITY PROGRAM - PUBLIC INFORMATION MEETINGS
SCHEDULE OF ACTIVITIES
| ACTIVITY | MARCH | APRIL | MAY | JUNE | JULY | AUGUST | ||||||||||||||||
| 7.1 Prepare Legal Announcement, Press Release | ||||||||||||||||||||||
| 7.1 Prepare Public Announcement | ||||||||||||||||||||||
| 7.1 Send out Newspaper and Public Announcements | ||||||||||||||||||||||
| 7.2 State Aviation Council Update | ||||||||||||||||||||||
| 7.2 Internal Working Meeting, Preliminary Rankings | ||||||||||||||||||||||
| 7.2.1 Public Meetings | ||||||||||||||||||||||
| 7.3 Public Comment Period | ||||||||||||||||||||||
| 7.4 Finalization of Project Rankings | ||||||||||||||||||||||
| 7.5 Presentation of Final Project Rankings to SAC | ||||||||||||||||||||||
| 7.6 Distribution of Final Project Rankings | ||||||||||||||||||||||
SECTION 8 - COMPUTERIZED PRIORITIZATION MODEL
See Separate Word File
8.1 PRIORITIZATION MODEL OVERVIEW
8.2 PROJECT PRIORITY RANKING SCREEN
8.2.1 Airport Categories
8.2.1.1 Activity
8.2.1.2 Ratings
8.2.2 Project Categories
8.2.2.1 Project Selector
8.2.2.2 Project Information
8.2.2.3 Project Points Sub-Tabs
8.2.3 Project Totals and Report
8.2.4 Printing Summary Reports
8.2.5 Editing Category Parameters
APPENDIX A
AIRPORT MEETING MINUTES
Burlington International Airport
Meeting Minutes
Caledonia County State Airport
Meeting Minutes
E. F. Knapp State Airport
Meeting Minutes
Fair Haven Municipal Airport
Meeting Minutes
Franklin County State Airport
Meeting Minutes
Hartness State Airport
Meeting Minutes
John H. Boylan State Airport
Meeting Minutes
Middlebury State Airport
Meeting Minutes
Morrisville-Stowe State Airport
Meeting Minutes
Newport State Airport
Meeting Minutes
Rutland State Airport
Meeting Minutes
William H. Morse State Airport
Meeting Minutes
APPENDIX B
PROJECT EVALUATION WORKSHEETS - 0-5 YEAR PROGRAM
Caledonia County State Airport
Project Evaluation Worksheets
E. F. Knapp State Airport
Project Evaluation Worksheets
Fair Haven Municipal Airport
Project Evaluation Worksheets
Franklin County State Airport
Project Evaluation Worksheets
Hartness State Airport
Project Evaluation Worksheets
John H. Boylan State Airport
Project Evaluation Worksheets
Middlebury State Airport
Project Evaluation Worksheets
Morrisville-Stowe State Airport
Project Evaluation Worksheets
Newport State Airport
Project Evaluation Worksheets
Rutland State Airport
Project Evaluation Worksheets
William H. Morse State Airport
Project Evaluation Worksheets
APPENDIX C
PROJECT EVALUATION WORKSHEETS - 0-20 YEAR PROGRAM
Caledonia County State Airport
Project Evaluation Worksheets
E. F. Knapp State Airport
Project Evaluation Worksheets
Fair Haven Municipal Airport
Project Evaluation Worksheets
Franklin County State Airport
Project Evaluation Worksheets
Hartness State Airport
Project Evaluation Worksheets
John H. Boylan State Airport
Project Evaluation Worksheets
Middlebury State Airport
Project Evaluation Worksheets
Morrisville-Stowe State Airport
Project Evaluation Worksheets
Newport State Airport
Project Evaluation Worksheets
Rutland State Airport
Project Evaluation Worksheets
William H. Morse State Airport
Project Evaluation Worksheets
APPENDIX D
NPIAS ACIP STANDARD DESCRIPTIONS
APPENDIX E
BURLINGTON INTERNATIONAL AIRPORT SUMMARY OF CAPITAL IMPROVEMENT PROGRAMS
APPENDIX F
FAA ORDER 5100.38A
1. Source - Vermont Airport System Plan, 1973, Updated 1983