Bellingham International Airport
Template:Short description Template:Use American English Template:Use mdy dates Script error: No such module "Infobox".Template:Template otherScript error: No such module "Check for unknown parameters".
Bellingham International Airport (Template:Comma separated entries) is three miles (5 km) northwest of Bellingham, in Whatcom County, Washington, United States. BLI covers 2,190 acres (886 ha) of land,[1][2] and is the fourth-largest commercial airport in Washington.
The airport, located in an unincorporated area of Whatcom County,[3] is a low-fare alternative to Vancouver International Airport, and an estimated 65% of customers come from Canada.[4][5] It is only Script error: No such module "convert". from downtown Vancouver, and only Script error: No such module "convert". from the Peace Arch Border Crossing, where Greater Vancouver starts.
History
The Works Progress Administration (WPA) began studying a potential airport for Whatcom County in late 1935 as part of a program to build airports in large Washington cities.[6] A plan to build an airport west of Bellingham was endorsed by the Washington's state WPA office by the end of the year and the head office the following July.[7][8] On October 20, 1936, Whatcom County purchased Script error: No such module "convert". from Charles F. Larrabee to build an airport using WPA funds.[9]
Construction of the airport began on October 22 under the supervision of the WPA.[10] Three runways were planned, but only the first was built initially; it was Template:Cvt long by Template:Cvt wide, and it was completed and dedicated on June 1, 1940.[11] Temporary Port of Entry status was secured early, but the slow construction left it in a continually tenuous state – United Airlines would only base there if the field were safe enough for their DC-3s, and it maintained its Port of Entry status.Script error: No such module "Unsubst".
In 1940, the United States Army Corps of Engineers took over the project and expanded the airport to three full runways, revetments for parking aircraft, and development of personnel quarters on Script error: No such module "convert"..Script error: No such module "Unsubst". The airport opened to the public on December 7, 1941, having employed hundreds of people during its construction. The initial runway, oriented in a northwest-to-southeast direction, was now Template:Cvt long. The two new runways were another Template:Cvt runway oriented northwest-to-southeast, and a north–south runway that had an initial length of Template:Cvt but would be extended another Template:Cvt to cross Bakerview Road.[12] Following the Attack on Pearl Harbor the same day, Whatcom County offered the use of the airport to the U.S. military, who seized it on December 10.[13][14] During World War II the airport was used by Fourth Air Force for air defense of the Pacific Coast. It was later used by Air Transport Command and Air Technical Service Command as an intermediate ferrying field for Lend-Lease aircraft being flown to Alaska for subsequent transfer to the Soviet Union.
The United States Army Air Forces closed the facility in September 1946, and it was turned over to the War Assets Administration for disposal. A terminal, designed by F. Stanley Piper, was built by United Airlines in anticipation of civilian use.[14] The airport was slowly returned to Whatcom County and redeveloped as a civil airport in the late 1940s. With the rising costs and need for repairs, Whatcom county sold the Airport to the Port of Bellingham for one dollar in 1957. Because of costs, the Port of Bellingham could only resurface the longest of the runways (16/34).[14] Runway 16/34 is still the only runway used as it provides adequate year-round wind coverage for aircraft servicing Bellingham. The airport closed runway 12/30 in 1986, and runway 2/20 was shut down in 1997.[11] The two diagonal runways have fallen into disrepair, their easternmost ends used as taxiways between tarmacs and the sole remaining runway.
Airline service from Bellingham had a modest beginning. During the late 1970s and early 1980s, Harbor Airlines, a commuter air carrier based in Washington, operated nonstop shuttle service to Seattle–Tacoma International Airport with small Britten-Norman Islander twin prop aircraft.[15] By the mid-1980s, Harbor Air had been replaced by San Juan Airlines, a commuter air carrier based in Bellingham which operated shuttle flights to Seattle/Tacoma with Embraer EMB-110 Bandeirante turboprops and Cessna 402 prop aircraft.[16] San Juan Airlines continues to serve the airport at the present time.
In 1985, Pacific Southwest Airlines (PSA) initiated Bellingham's first passenger jet service with McDonnell Douglas MD-80s direct to Los Angeles, San Diego and San Francisco with all PSA flights including a stop at Seattle/Tacoma. PSA was acquired by USAir which continued to serve Bellingham with Boeing 737-300s. Alaska Airlines introduced MD-80 jets in the late 1980s, competing with USAir with both airlines operating nonstop jet service to Seattle/Tacoma and direct one stop service to other destinations. USAir then changed its name to US Airways and eventually merged with American Airlines in 2015; however, by the early 1990s, USAir had ceased serving Bellingham.[17] During the late 1980s, Alaska Airlines was joined by Horizon Air, a wholly owned subsidiary of the Alaska Air Group, with this regional airline flying nonstop service with turboprops to Seattle/Tacoma.[18] Aircraft operated by Horizon Air into the airport over the years included such propjets as the Fairchild Swearingen Metroliner, the de Havilland Canada DHC-8 Dash 8 and the Dornier 328. Horizon Air, which currently operates flights for Alaska Airlines, continues to serve Bellingham at the present time with nonstop service to Seattle/Tacoma flown with the Embraer E175.[19] Commencing in the late 1980s, United Express was serving the airport with nonstop flights to Seattle–Tacoma International Airport on behalf of United Airlines via code sharing agreements with the respective operating air carriers.[20] North Pacific Airlines operated the first United Express flights into Bellingham with British Aerospace BAe Jetstream 31 propjets and were followed by SkyWest Airlines flying as United Express with Embraer EMB-120 Brasilia turboprops. United Express no longer serves Bellingham.
In the 1990s homes were purchased to extend the runway in an effort to attract air carriers. The assumption was that there would not be a third runway at Sea-Tac airport. The airport has seen a high turnover rate.
In September 2010 the airport completed a $26 million resurfacing of the runway to allow aircraft up to the size of Boeing 757s. This project was completed to enable Allegiant Air to operate Boeing 757-200 service nonstop to Hawaii, although this service has since ended.[21] The largest aircraft currently serving Bellingham as of July 2019 are Allegiant Air's Airbus A320 aircraft flying to several destinations on the West Coast.
Terminal
Terminal upgrades were completed in two phases in the 1980s. The first phase was completed in 1980. The second phase, or the expansion phase, was constructed because of increased passenger volumes and the arrival of new air carriers. In 1985, a separate International Terminal was built to the south in order to accommodate the Federal Inspection Services necessary for international travelers to access the United States; it was connected to the main terminal through a covered walkway. The main terminal was approximately 26,000 square feet and included three levels: the basement, the ground floor, and the second floor. The basement housed a small storage facility; the ground floor was where the entire passenger processing area was held; and the second floor contained office space. There was one concession stand: Halibut Henry's store, where light snacks, coffee drinks, gifts, and sundries were offered. The International Terminal was a one-level building consisting of Script error: No such module "convert".. It served several functions, including the housing of the Federal Inspection Service, FIS offices, Allegiant Airline's mechanic offices, and Bellingham Aviation Service's ground support equipment maintenance.[22]
The airport underwent another $38.5-million terminal expansion in the early 2010s. After the first phase was completed in June 2011, the number of gates increased from 2 to 5, and the overall gate boarding area increased to Script error: No such module "convert".. With the completion of the second phase in February 2014, the size of the terminal increased from Template:Cvt. In addition, the size of the ticketing lobby area was tripled so that the former 2-station area could now support 20 ticketing stations, the baggage claim area was increased to Template:Cvt, and the Template:Cvt was replaced with a Template:Cvt baggage carousel for arriving passengers.[23] The cost of the expansion to the terminal building was covered by surcharges from passengers and parking fees.
Commercial airline service expansion
The early 21st century saw rapid expansion at the Bellingham International Airport from several air carriers operating mainline jet aircraft with these airlines being motivated by the potential passenger loads from lower mainland British Columbia in Canada. Allegiant's commitment to the airport has led to a rapid rise in passenger numbers and the introduction of a number of nonstop destinations served from Bellingham. Other airlines initially recognized the potential of Bellingham International's location and further expanded service into the airport, but all commercial airlines except Alaska, Allegiant, and Southwest had departed as of 2023.
In early 2007 Bellingham International hosted nonstop service to three destinations by the short-lived Western Airlines which was operating Boeing 737-400 jets and was based in Bellingham. Western attempted to establish a small hub at the airport with nonstop service to Ontario, California (ONT), Phoenix, Arizona (via the Phoenix-Mesa Gateway Airport, AZA) and San Diego, California (SAN). Later the same year, Skybus Airlines operated nonstop flights to their Columbus, Ohio (CMH) hub with Airbus A319 jetliners but then shut down quickly like Western Airlines had done earlier. Between June 2006 and April 2008, Delta Air Lines also used to serve Bellingham with flights to Salt Lake City operated by their regional affiliate SkyWest Airlines.
On March 1, 2008, Allegiant Air opened up their sixth base at Bellingham International Airport. The airline currently bases a number of aircraft in Bellingham which serves as a "focus city" for the airline. In 2012 Allegiant announced service to two locations in the Hawaiian islands (Honolulu and Kahului) from Bellingham after receiving ETOPS certification from the FAA for their 757 aircraft. Alaska also entered the market with flights to Honolulu, Kahului and Kona. As of July 2019, both Allegiant and Alaska no longer serve Hawaii from Bellingham. Allegiant has also unsuccessfully tried serving other markets from Bellingham in recent years, such as Denver, Tucson, Reno, and Anchorage.
In September 2010 the airport completed a $26 million resurfacing of the runway to allow aircraft up to the size of Boeing 757s to utilize the airport.[24] This project was completed in order to serve Allegiant 757 service to Honolulu and Maui which began operations in November 2012.[21]
In response to the increased low-fare competition offered by Allegiant in their home state, Alaska Airlines expanded service from Bellingham International during the 2010s, adding service to Portland, Las Vegas, Honolulu, Kahului, and Kona, all of which are now discontinued. In early 2012, Frontier Airlines announced the addition of a daily seasonal summer service from Bellingham to its main hub in Denver beginning May 2012. Frontier flew Airbus A319 and Embraer ERJ-190 jets from Bellingham but subsequently ceased serving the airport.
On November 7, 2021, Southwest Airlines began service at Bellingham International Airport. Initial service includes twice daily flights to Oakland, CA (OAK) and once daily service to Las Vegas, NV (LAS).[25]
The runway and taxiway resurfacing and improvement projects were funded with FAA Airport Improvement Program (AIP) grants covering 95% of project costs. In 2010 the FAA contribution towards airport projects was $27,267,000. The 5% local match came from BLI Passenger Facility Charge accounts. FAA AIP grants also have contributed to the acquisition of additional Airport Rescue Fire Fighting (ARFF) equipment, aircraft de-ice equipment and other surface projects. The BLI PFC fee per passenger is currently at the FAA mandated maximum of $4.50 per enplaned passenger. The terminal and ramp expansion projects are not AIP eligible as they are revenue generating facilities for the airport. The Port of Bellingham issued revenue bonds for $31,719,550 to pay for the terminal expansion. The debt service for the bonds also comes from BLI PFC accounts. In this way, the users of the airport facilities are the ones actually paying for the facility.
General aviation
Bellingham International Airport is also a busy general aviation (GA) facility, with numerous flights oriented towards sightseeing in the San Juan Islands, Victoria in British Columbia, or the Canadian Gulf Islands. The majority of GA operations are commercial in nature, including charters, flight training, transient flights, and private business operations, and the airport serves as a port of entry for international travelers. GA facilities occupy about Template:Cvt south of the passenger terminal, and include tie-down spaces, numerous hangars, and a dedicated GA terminal.[22]
Military units
The Washington Air National Guard (WANG) once occupied a 7.5-acre site at Bellingham International Airport. The Washington Air National Guard is home of the 262nd Combat Communications Squadron. The 262nd's mission is to train and equip combat communications personnel, where they field, install, operate, and maintain Ground Mobile Force communications.[26] In other words, the 262nd equips soldiers with their battlefield communication systems and trains them how to use and maintain the equipment. The WANG base consists of vehicle storage, a headquarters building, a maintenance building, and other miscellaneous storage buildings.
The WANG site has now been demolished for a hangar project by a local developer.[27]
Airlines and destinations
Passenger
Script error: No such module "Unsubst". Template:Airport destination list San Juan Airlines merged with Northwest Sky Ferries in 2009. This merged airline offers scheduled and charter flights from Bellingham to the San Juan Islands in Washington, Seattle, Tacoma, Port Angeles, Olympia, and British Columbia. San Juan Airlines also serves Bellingham; offering scheduled and charter flights to the San Juan Islands and British Columbia.[22] Northwest Sky Ferry and San Juan airlines offer prop aircraft service with Cessna 206, 207 and 182 airplanes.[28]
On April 25, 2024 Southwest Airlines announced it would halt operations at Bellingham International Airport (Denver, Las Vegas, Oakland) after August 4, 2024.[29]
| Destination map |
|---|
| Script error: No such module "Location map/multi". |
Cargo
Template:Airport destination list
Statistics
Top destinations
| Rank | City | Passengers | Carriers |
|---|---|---|---|
| 1 | Template:Flagicon Las Vegas, Nevada | 111,000 | Allegiant, Southwest |
| 2 | Template:Flagicon Seattle/Tacoma, Washington | 60,180 | Alaska |
| 3 | Template:Flagicon Oakland, California | 36,400 | Allegiant, Southwest |
| 4 | Template:Flagicon Phoenix/Mesa, Arizona | 19,760 | Allegiant |
| 5 | Template:Flagicon Los Angeles, California | 15,000 | Allegiant |
| 6 | Template:Flagicon Palm Springs, California | 13,530 | Allegiant |
| 7 | Template:Flagicon Denver, Colorado | 5,350 | Southwest |
| 8 | Template:Flagicon San Diego, California | 3,400 | Allegiant |
| Rank | Airline | Passengers | Share |
|---|---|---|---|
| 1 | Allegiant Air | 265,000 | 50.03% |
| 2 | Southwest Airlines | 146,000 | 27.52% |
| 3 | SkyWest Airlines | 119,000 | 22.45% |
Passenger numbers
| Year | Passengers | Change | Passenger totals 2008–present (in hundreds of thousands) |
|---|---|---|---|
| 2008 | 535,000 | - | <timeline>
ImageSize = width:auto height:250 barincrement:30 PlotArea = left:30 bottom:17 top:11 right:17 AlignBars = justify Period = from:0 till:12 TimeAxis = orientation:vertical Colors = id:gray value:gray(0.5) id:line1 value:gray(0.9) id:line2 value:gray(0.7) ScaleMajor = start:0 increment:1 gridcolor:line2 ScaleMinor = start:0 increment:1 gridcolor:line1 PlotData= color:blue width:22 bar:2008 from:start till:5.35000 bar:2009 from:start till:6.35000 bar:2010 from:start till:7.73000 bar:2011 from:start till:10.03000 bar:2012 from:start till:11.16000 bar:2013 from:start till:11.63000 bar:2014 from:start till:10.73749 bar:2015 from:start till:8.78000 bar:2016 from:start till:8.35860 bar:2017 from:start till:7.40044 bar:2018 from:start till:7.36372 bar:2019 from:start till:6.71232 bar:2020 from:start till:1.96512 bar:2021 from:start till:3.20320 bar:2022 from:start till:6.33386 bar:2023 from:start till:6.20000 bar:2024 from:start till:5.29000 </timeline> |
| 2009 | 635,000 | Template:Change | |
| 2010 | 773,000 | Template:Change | |
| 2011 | 1,003,000 | Template:Change | |
| 2012 | 1,116,000 | Template:Change | |
| 2013 | 1,163,000 | Template:Change | |
| 2014 | 1,073,749 | Template:Change | |
| 2015 | 878,000 | Template:Change | |
| 2016 | 835,860 | Template:Change | |
| 2017 | 740,044 | Template:Change | |
| 2018 | 736,372 | Template:Change | |
| 2019 | 671,232 | Template:Change | |
| 2020 | 196,512 | Template:Change | |
| 2021 | 320,320 | Template:Change | |
| 2022 | 633,386 | Template:Change | |
| 2023 | 620,000 | Template:Change | |
| 2024 | 529,000 | Template:Change |
See also
References
Script error: No such module "Template wrapper".
<templatestyles src="Reflist/styles.css" />
- ↑ Cite error: Script error: No such module "Namespace detect".Script error: No such module "Namespace detect".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "Citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ a b Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ a b c Script error: No such module "citation/CS1".
- ↑ http://www.departedflights.com, Nov. 15, 1979 & April 1, 1981 editions, Official Airline Guide (OAG), Seattle-Bellingham flight schedules
- ↑ http://www.departedflights.com, Feb. 15, 1985 Official Airline Guide (OAG), Seattle-Bellingham flight schedules
- ↑ http://www.departedflights.com, Oct. 1, 1991 Official Airline Guide (OAG), Seattle-Bellingham flight schedules
- ↑ http://www.departedflights.com, Dec. 15, 1989 Official Airline Guide (OAG), Bellingham flight schedules
- ↑ https://www.bellinghamherald.com/news/local/article271166797.html, Jan. 15, 2023, The Bellingham Herald
- ↑ http://www.departedflights.com, Dec. 15, 1989 & April 2, 1995 & June 1, 1999 editions, Official Airline Guide (OAG), Seattle-Bellingham flight schedules
- ↑ a b Script error: No such module "citation/CS1".
- ↑ a b c Script error: No such module "citation/CS1".
- ↑ Script error: No such module "Citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
Script error: No such module "Check for unknown parameters".
External links
- Script error: No such module "Official website".Script error: No such module "Check for unknown parameters".
- WSDOT Pilot's Guide: Bellingham International (PDF 69 kb)
- WSDOT Economic Impacts: Bellingham International
- FAA Airport Diagram (PDF), effective Error: Invalid time.
- FAA Terminal Procedures for BLI, effective Error: Invalid time.
- Resources for this airport:
- AirNav airport information for KBLI
- ASN accident history for BLI
- FlightAware airport information and live flight tracker
- NOAA/NWS weather observations: current, past three days
- SkyVector aeronautical chart for KBLI
- FAA current BLI delay information
Script error: No such module "Navbox".
Template:Airports in Washington
Script error: No such module "Military navigation".
Template:Authority control
- Pages with script errors
- Pages with reference errors
- Pages with broken file links
- Wikipedia articles incorporating text from the Air Force Historical Research Agency
- Airports in Washington (state)
- Buildings and structures in Bellingham, Washington
- Transportation buildings and structures in Whatcom County, Washington
- Airfields of the United States Army Air Forces in Washington (state)
- Airfields of the United States Army Air Forces Air Transport Command in North America
- 1940 establishments in Washington (state)
- Airports established in 1940