My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Draft EUG Master Plan Update, February 2010
COE
>
City of Eugene
>
Ordinances
>
2010 No. 20450-20469
>
Ordinance No. 20463
>
Draft EUG Master Plan Update, February 2010
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/29/2010 5:36:43 PM
Creation date
9/29/2010 5:35:49 PM
Metadata
Fields
Template:
Council Ordinances
CMO_Document_Number
20463
Document_Title
Draft EUG Master Plan Update, February 2010
Adopted_Date
9/27/2010
Approved Date
9/27/2010
Signer
Kitty Piercy
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
218
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
<br />CHAPTER5 <br />FINANCIAL FEASIBILITY ANALYSIS <br />As shown in Table 5-1, the CIP is projected to be funded by outlays from the following sources: <br />$58,061,908 from AIP entitlement funds, $5,534,719 from AIP discretionary funds, $32,271,873 from PFC <br />revenue (not inclusive of debt service on bonds issued for terminal and access road improvements), <br />$15,901,500 from local sources (the Airport’s Operating and Capital Reserve and Depreciation Reserve <br />Funds), $3,000,000 from Customer Facility Charge revenues, and $4,610,000 from other funding sources <br />including a $110,000 grant from “Connect Oregon” in FY 2008 for the Phase II Air Cargo Ramp <br />Expansion Project, as well as a $4.5 million allocation from the FAA’s Facilities and Equipment Program <br />in FY 2021 for a new FAA air traffic control facility. <br />The CIP presented in Table 5-1 does not include certain projects, such as general aviation hangars and <br />private business developments, which may be funded by other private sources. For purposes of this <br />analysis, it was assumed that tenant-financed projects would not be constructed until demand warrants <br />(i.e., demand and unit user revenues make it feasible to develop and finance additional hangar facilities). <br />3. Funding for the Program <br />Based on the descriptions of the capital improvement projects presented in Table 5-1, the phasing of <br />these projects, their associated costs, and eligible funding amounts as identified in the previous sections, <br />a proposed funding plan for the Airport’s CIP was developed. Federal participation in Airport capital <br />development is based on the Airport Improvement Program as re-authorized in 2003. This analysis <br />assumes continuance of AIP and PFC funding through the planning period without major changes. <br />However, in the past, these programs have experienced fluctuations in levels of funding and interruptions <br />in funding availability; therefore, it is imperative for Airport management to consider maintaining reserve <br />funds to support Airport activities should such fluctuations and interruptions occur in the future. It is <br />further recommended that since a host of the projects described in this plan are contingent upon sufficient <br />aviation demand to support their ongoing operations upon completion, Airport management should <br />closely examine the true need for their implementation prior to committing to undertaking project design <br />and/or construction. In developing the funding plan for capital improvements, the controlling objectives <br />were to maximize the use of resources from AIP and PFC funds and to minimize Airport/local funding <br />requirements. <br />It is assumed that costs for the CIP will be generated from a combination of the following potential funding <br />sources: <br />Federal AIP Grants <br />Passenger Facility Charges <br />Airport Operating and Capital Reserves <br />Customer Facility Charges <br />Private Funding <br />These funding sources are discussed in further detail below. <br />5-10 <br />Eugene Airport Master Plan Update <br />(February 2010) <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.