The Washington State Department of Transportation (WSDOT) Aviation is developing a strategic plan and management procedures for the 17 state-managed airports within Washington State. Of these airports, WSDOT owns eight, leases one, and operates the remaining eight under conditional use permits. It is necessary for WSDOT Aviation to examine the role the state-managed airports serve in the state’s overall transportation system. The State-Managed Airport Study will help WSDOT understand the comparative benefit of investing in these airports versus others in the statewide system.
- Communicate and provide updates to the public on the project, news, events, and management of the airports.
- Define the purpose and role of the state-operated airport system through an independent assessment.
- Conduct a detailed assessment of existing facilities.
- Standardize airport operating agreements.
- Integrate with the current statewide system plan effort LATS.
- Identify management objectives, standards, operating procedures and policies.
- Background Assessment and Study Analysis of State Managed Airports:
- Aviation Planning Council review and integration with the Washington Long-Term Air Transportation Study (LATS) and Washington Transportation Plan:
- Washington Aviation System Plan Policies
- Integration with Airport Classification System and Performance Measures
- State Managed Airport Handbook:
- Management Principles
- Best Management Practices and Regulations
- Development of Airport Master Plans and Airport Layout Plans
Wilbur Smith Associates, a firm with expertise in aviation engineering and planning, will perform an independent assessment of the WSDOT-Managed airports and recommend a direction for future investment in the system. Once the assessment is completed, the consulting team and WSDOT Aviation will work with a Study Advisory Committee (SAC) to develop recommendations for policy and implementation strategies.
- March 2007: Project Kick-off
- June 2007: Release of independent assessment
- August 2007: Policy and performance objectives
- September 2007: Study Advisory Committee meets
- October 2007: Recommendations for best management practices
- November 2007: First LATS Aviation Planning Council meeting
- January 2008: Final draft policy and management strategies completed
- April 2008: Public review and presentation to LATS Aviation Planning Council
- July 2008: Aviation Planning Council initiates 30-day public review/comment on draft statewide policies
- September 2008: Begin State-Managed Airports Handbook
- July 2009: Aviation Planning Council submits final recommendations
- September - October 2009: Public comment on State-Managed Airports Handbook
- November 2009: Final State-Managed Airports Handbook
Updated September 2009
WSDOT will be hosting a series of public outreach meetings to receive feedback on the State-Managed Airports Handbook:
September 22, 2009
4 p.m. to 6 p.m.
North Beach Jr/Sr High School
336 State Route 115
Ocean Shores, WA 98569
September 24, 2009
4 p.m. to 6 p.m.
WSDOT Maintenance Bldg
1210 "G" Street
Walla Walla, WA 99362
October 14, 2009
3 p.m. to 5 p.m.
Arlington Boys and Girls Club
18513 59th Ave NE
Arlington, WA 98223-7846
October 15, 2009
4 p.m. to 6 p.m.
WSDOT Spokane HQ
2714 N Mayfair Street
State Managed Airports Communication Plan (pdf 48 kb)
Airport Independent Assessment - October 2007 (pdf 947 kb)
Policies and Performance Objectives - February 2008 (pdf 290 kb)
Recommendations for Best Management Practices - February 2008 (pdf 362 kb)
Recommendations for Policy Management Principles - February 2008 (pdf 22 kb)
Aviation Planning Council Presentation (page 22)- April 2008 (pdf 8
State-Managed Airports Study Advisory Committee (pdf 25 kb)
State-Managed Airports Study Fact Sheet (pdf 42 kb)
To request copies of project materials or to submit comments, please contact:
WSDOT Aviation Communications
Receive e-mail alerts about WMA and other state aviation news. Email your request to subscribe to the Aviation News Service.
To request a project briefing, please contact firstname.lastname@example.org