Wikipedia:WikiProject Airports/page content/sandbox

Airlines and destinations

Passenger

Airlines	Destinations
Aeroméxico	Seasonal: Cancún
Air France	Algiers Seasonal: Calvi, Dublin, Eilat–Ovda, Halifax, Kittilä, Oujda, Rhodes
Delta Air Lines	Atlanta, Austin (begins March 2, 2018), Boston, Detroit, Los Angeles, Minneapolis/St. Paul, Paris–Charles de Gaulle, Salt Lake City, Seattle/Tacoma Seasonal: Cancún, Orlando
Delta Connection	Austin (ends March 1, 2018), Baltimore, Boston, Cincinnati, Cleveland, Columbus–Glenn, Detroit, Fort Lauderdale, Hartford, Indianapolis, Minneapolis/St. Paul, Nashville, New York–JFK, New York–LaGuardia, Newark, Orlando, Philadelphia, Tampa, Washington–National Seasonal: Fort Myers, Miami
Shandong Airlines	Beijing–Capital, Changchun (resumes May 18, 2018), Chiang Mai, Dalian, Fuzhou, Guilin, Harbin, Kunming, Phnom Penh, Pyongyang (suspended), Qingdao, Shanghai–Pudong, Shenyang, Shijiazhuang, Xiamen, Zhengzhou

Cargo

Airlines	Destinations	Refs
Amazon Air	Cincinnati
FedEx Express	Indianapolis, Memphis Seasonal: Oakland

Format

1. Do not use template substitution with the {{Airport destination list}} template.
2. If both a passenger and cargo table are included, each table should be contained in ===Passenger=== and ===Cargo=== headings.
3. Do not remove begins/ends/resumes tags until the date has occured. Any references included with these tags do not need to be removed when the tag is removed.
4. For flights that do not operate year round, destinations should be listed on a separate line from year-round destinations, with seasonal destinations listed after the Seasonal label. Only include beginning or ending dates for new seasonal routes.
5. Do not include flags for airlines or the actual destination.
6. Do not create a seperate table sepcifically for domestic (national), international, or charter flights.
7. Do not list the terminal(s) or concourse(s) that airlines operate from in the third column of the table.

Content

1. Do not list secondary carriers for code share flights. For example, if Air New Zealand operates a domestic flight under its own flight number and an additional Singapore Airlines codeshare, the codeshare should not be listed.
2. For flights operated by one airline but marketed by another, so that the flight uses only the marketing airline's flight number, avoid using the term operated by or dba, an abbreviation of the American business term doing business as (e.g. "Alaska Airlines", not "Alaska Airlines operated by Skywest Airlines").
3. Do not include ad-hoc, irregular, or private charter services.
4. Per WP:VERIFY, references must be included for "any material whose verifiability has been challenged or is likely to be challenged," and this includes the list of destinations.
5. Charter, Seasonal, and Seasonal Charter routes should ideally include an explict route that verifies the route is regularly scheduled and not ad-hoc, irregular, or a private charter.

Naming conventions

1. Use city names for destinations (not the airport names), and only disambiguate using airport names when there are multiple airports serving the same city.
2. Differentiate between multiple airports in one city using "–" (en dash) (e.g., "London–Heathrow", not "London Heathrow").
3. Differentiate between multiple airports in cities with the same by including the state or country ISO 3166-2 code using "()" (parenthesis) (e.g., "Columbus (OH)" and "Columbus (GA)"; "San Jose (CA)" and "San José (CR)").
4. For airport systems where one airport is much larger, only disambiguate the smaller airport (e.g., "Cincinnati" and "Cincinnati–Lunken"; "Orlando" and "Orlando/Sanford").
5. For airports equally serving multiple large cities, combine the city names using "/" (slash) (e.g. "Seattle/Tacoma"; "Dallas/Fort Worth").
6. Use the actual cities served if the airport serves a smaller city located near a large city (e.g., "Beauvais", not "Paris–Beauvais"; "Rygge", not "Oslo–Rygge").
7. List non-stop and direct flights only. That means the flight number and the aircraft, starts at this airport and continues to one or more airports. Avoid using the description 'via' since that is more correctly listed as another destination. If passengers cannot disembark at a stop on a direct flight, then do not list it as a destination or as 'via'. Direct flights are not always non-stop flights. However, avoid listing direct flights that contain a stop at a domestic hub, as virtually all of these are simply flights from one "spoke city" to a hub, with the plane continuing from the hub to a second spoke city. Furthermore, these flights often involve plane changes, despite the direct designation. Including these flights dramatically increases the length of destination listings, artificially inflates the airline's presence at a location and requires constant updating, as these "timetable direct" destinations have little rhyme or reason and may change as often as every week or two.

Cargo only

Cargo airlines may be included after Airlines and destinations but are not necessary. The decision about whether cargo airlines add encyclopedic value to an airport can be made on an airport-by-airport basis and reliable sources should be a consideration whether to include cargo airlines in an article.

1. If cargo airlines are included, cargo destinations are optional.
2. Only list routes operated with all-cargo aircraft. Passenger/cargo combination flights should be listed in the Passenger section.
3. Similar to the Passenger section, avoid using the term operated by or dba, an abbreviation of the American business term doing business as (e.g. "Amazon Air", not "Amazon Air operated by ABX Air"; "DHL Aviation", not "DHL Aviation operated by AeroLogic").
4. A reliable source such as a cargo timetable should be explicitly listed verifying the service of each cargo airline.
5. All other guidelines from the Passenger list still apply.