Bringing g the PUBLIC WORKSHOP Venice Municipal Airport New Opportunities Presented for Venice City Council & Citizens of Venice September 25, 2009 Slide 1
Bringing g the Welcome & Introductions May 12th Workshop Counting Program Runway Design Standards Definitions & Illustrations Alternative Scenarios for discussion Public input Next steps May 12 th Council workshop provided an opportunity to discuss data, project goals and receive public comment. Slide 2
Bringing the May 12th Workshop: Summary of Comments Gulf Shores Homes Located in Runway 13 Runway Protection Zone (RPZ) Preserve Lake Venice Golf Course Maintain Airport As-Is Existing Levels No Expansion / No Growth Comply with FAA Standards Maintain Facilities That Are Safe Modern Well-maintained i Financially Strong Good to Neighbors Slide 3
Bringing the May 12th Workshop: Summary of Comments Ensure Airport has Emergency Transport Capabilities Right-hand h Traffic Pattern to Runway 4 Grass Strip Parallel to Runway 4 Improve Public Understanding & Information About the Airport Aircraft Noise & Impact on Surrounding Communities Fumes from Idling Aircraft Slide 4
Bringing the Airport Reference Code (ARC) Airport Reference Code Definitions: Approach Category Design Group Airport Reference Code (ARC) Aircraft Approach Category A B C D Aircraft Design Group I II III Approach Speed Less than 91 knots 91 knots or more but less than 121 knots 121 knots or more but less than 141 knots 141 knots or more but less than 166 knots Wingspan Up to but not including 49 feet 49 feet up to but not including 79 feet 79 feet up to but not including 118 feet Slide 5
Aircraft Counting Sensors Six Months March August, 2009 2009 Preliminary Data VNC C-I Example: Lear 25 C-II Example: Citation X A-I Example: Cessna 182 B-I Example : Beech C23 Slide 6
Aircraft Counting Sensors Six Months March August, 2009 2009 Preliminary Data VNC D-I Example: Lear 60 B-I Example: Hawker 800XP B-II Example: Falcon 50 C-I Example: Beechjet 400A Slide 7
Aircraft Counting Sensors Six Months March August, 2009 2009 Preliminary Data VNC Operations March 2009 April 2009 May 2009 June 2009 July 2009 August 2009 Total to Date A-I 3,048 2,238 2,188 1,760 2,406 1,124 12,764 A-II 6 0 6 4 4 2 22 B-I 114 126 58 82 86 42 508 B-II 178 148 70 64 104 40 604 C-I 44 40 36 10 12 10 152 C-II 38 22 16 2 22 4 104 D-I 10 2 0 0 0 2 14 D-II 0 8 2 0 0 4 14 H 2 0 0 0 2 0 4 Touch and Go s recorded 1,686 *832 1,478 1,793 1,391 1,464 8,644 Total Operations 5,126 3,416 3,854 3,715 4,027 2,692 22,830 *System Error no operations collected 4/3-4/17 Slide 8
Aircraft Operations Sensors First Six Months 2009 Preliminary Data Venice Counting Sensors, Preliminary Data Count, March through August, 2009 Slide 9
Bringing g the What Will the Data Tell Us? Critical Aircraft and Activity Forecast Welcome & Introductions May 12th Workshop Counting Program Runway Design Standards Definitions & Illustrations Are there 500 annual operations of C aircraft operating at VNC? Compare data to master plans, FAA/FDOT forecasts Review in light of today s economic climate Comparison of other Florida airports Business activity vs. recreational Is a new forecast warranted? D fi iti & Ill t ti Review in light of today s economic Alternative Scenarios for discussion Public input Next steps Slide 10
Runway Design Standards Definitions & Illustrations Bringing the Runway Protection Zone (RPZ) Size varies based on ARC, aircraft, & visibility minimums Enhance the protection ti of people and property on the ground Clearing is Desirable Some uses Okay - Golf Courses (not including club houses) Agricultural (not forestry or livestock) Parking lots Incompatible Land Uses Residences Places of public assembly Fuel storage Slide 11
Runway Protection Zone (RPZ) B-II vs. C-II Slide 12
Runway Design Standards Definitions & Illustrations Bringing the Runway Protection Zone (RPZ) Airports are encouraged to attain compatible zoning in RPZs and around the airport. Airports are encouraged to have sufficient interest in RPZs purchase in fee simple, purchase an easement, or adequate zoning to protect encroachment. In cases where land is already developed and impractical for airport owner to acquire FAA RPZ land use standards have recommendation status. Slide 13
Runway Design Standards Definitions & Illustrations Bringing the Runway Safety Area (RSA) A defined surface surrounding the runway intended to provide a measure of safety in the event of an aircraft s excursion from the runway by significantly reducing the extent of personal injury and aircraft damage during overruns, undershoots, & veer-offs. Size varies based on ARC & visibility ibilit minimums i FAA Order 5200.8, Runway Safety Area Program FAA AC 150/5300-13 13, latest changes. Slide 14
Runway Safety Area (RSA) B-II vs. C-II Slide 15
Runway Design Standards Definitions & Illustrations Bringing the Runway Safety Area (RSA) The FAA accelerated the improvement of runway safety areas that do not meet agency design standards. The FAA expects to make all practicable improvements by 2015. Engineered Material Arresting Systems, or EMAS. The FAA conducted research to develop a soft-ground arrestor system to quickly stop aircraft that overrun the end of a runway. EMAS bed provides a safety enhancement on runway ends where there is not enough level, cleared land for a standard RSA. EMAS has been installed at more than 41 runway ends at 28 airports with plans to install 15 additional EMAS systems at 9 additional airports. Use FAA Order 5200.9 to determine maximum cost to improve RSA. Slide 16
Runway Design Standards Definitions & Illustrations Bringing the Runway Object Free Area (ROFA) A two-dimensional ground area surrounding the runway must be clear of parked aircraft and objects other than those whose location is fixed by function. Ground objects must not protrude above the elevation of the RSA edge. Width varies from 250 to 800 feet Length beyond end of runway varies between 300 & 1,000 feet. Slide 17
Runway Object Free Area (ROFA) B-II vs. C-II Slide 18
Bringing g the Alternative Scenarios for Discussion Welcome & Introductions May 12th Workshop Counting Program Existing Conditions Keep As-Is Regardless of Current Aviation Demand Runway Design Standards Comply to Standards for Existing Traffic Definitions iti & Illustrations ti Modify Airport Alternative Scenarios for discussion Public input Next steps Comply to Standards d for Existing Traffic Modify Adjacent Land Uses Reduction of Airport Reference Code / Design Aircraft Slide 19
Bringing the Alternative Scenarios for Discussion: 1 Existing Conditions As-Is As-Is Condition Entails: Existing runway widths, lengths, & standards (C-II) RPZ on 13 end will contain incompatible land uses Driving range and parts of golf course impede compliant RSA & ROFA standards d Existing aircraft types and levels maintained Results Does Not meet FAA/FDOT requirements, FAA approval unlikely future funding jeopardized. Violates grant assurances. Regular maintenance, financially sustainable, & emergency transport capable all maintained through City financing Noise abatement t program continues Slide 20
Alternative 1 As-Is Conditions Depicted Slide 21
Bringing the Alternative Scenarios for Discussion: 2 Meet FAA Standards Modify Airport Modify Airport to Meet FAA Standards Runway 13 End Runway 13 RPZ pulled onto airport (no homes) Threshold displaced Runway 31 End Alternatives Keep as-is or Extend 31 pavement to make up for loss Runway 31 operations use declared distances Slide 22
Alternative 2:13-31 Meet Standards: Modify Airport Slide 23
Bringing the Alternative Scenarios for Discussion: 2: 4-22 Meet FAA Standards Modify Airport Modify Airport to Meet FAA Standards Runway 4 End RPZ pulled in to clear club house Threshold displaced EMAS Option (Cost is significant = $4.2 m. plus $5.1 in life cycle costs) Satisfies RSA requirement but not ROFA or RPZ Runway 22 End Runway ends at displaced threshold Slide 24
Bringing the Alternative Scenarios for Discussion: 4-22 Meet FAA Standards Modify Airport Maximum Feasible RSA Expenditure Slide 25
Alternative 2:4-22 Modify Airport Slide 26
Bringing the Alternative Scenarios for Discussion: 3 Meet FAA Standards Modify Adjacent Land Use Modify Adjacent Land Uses to Meet FAA Standards Runway 13 End Voluntary purchase assurance program or avigation easement of homes in RPZ Runway 4 End Relocate driving range & reconfigure golf course portions that impede RSA/ROFA/RPZ Acres along Harbor Drive available to reconfigure Slide 27
Alternative 3 Modify Adjacent Land Uses Slide 28
Bringing the Alternative Scenarios for Discussion: 4 Reduction of Airport Reference Code / Design Aircraft Reduce Airport Reference Code: Reduce entire runway system to B-II standards No changes to adjacent land uses FAA unlikely to support jeopardize future funding Violates Grant assurances Safety issues Hawker 800 Slide 29
Alternative 4 Reduce Airport Reference Code: BII Slide 30
Runway Length Requirements Bringing the Calculation Criteria: Max Temp - 91 F Airport Elevation 18 ft. msl 75% of Fleet Lear 35, Lear 45 applies to airports primarily intended to serve medium size population communities with a diversity of usage & a greater potential for increased aviation activities. Also airports that are intended to serve low-activity. 100% of Fleet would not apply at VNC Slide 31
Bringing the Preliminary Runway Length Requirements Preliminary Results Dry Pavement: 75% of Fleet at 60% useful load = 4,600 ft. 75% of Fleet at 90% useful load = 6,800 ft. Preliminary i Results Wet Pavement: 75% of Fleet at 60% useful load = 5,290 ft. 75% of Fleet at 90% useful load = max. 7,000 ft. Calculations conducted using from FAA 150/5325-4b Slide 32
Bringing g the Airport Opportunities & Constraints Welcome & Introductions May 12th Workshop Counting Program Runway Design Standards Definitions iti & Illustrations ti Alternative Scenarios for discussion Public input Next steps Alternatives selected for further study Runway Design Aircraft Safety Area Object Free Area Protection Zone Operations Market Traffic Type Traffic Patterns Management Financial Impact Airport Facilities Taxiways Aircraft parking Hangars Slide 33
Bringing g the Venice Municipal Airport Study Process and Schedule Baseline Analysis (Camera Counts, Critical Design Aircraft, Existing Conditions, Operational Conditions) General Visions With a Goal (Work with City on Conceptual Goals) Vision Plans (Develop Alternative Plans to Achieve Conceptual Goals) Opportunities & Constraints (Objective Analysis of Community and Aeronautical Impacts) July 09 Aug 09 Sept 09 Oct 09 Nov 09 Dec 09 Jan 10 Consensus Building (Public Input with Goal of City Council s Decision) Final Plan (Adopt Plan to Incorporate into Master Plan for FAA Approval) Slide 34
Discussion & Input Slide 35