Jump to content

Wikipedia talk:WikiProject Airports

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
(Redirected from Wikipedia talk:AIRPORT)

Destination lists - naming of airports

[edit]

There’s been a fair bit of discussion lately about the naming of airports, such as above about Navi Mumbai, and separately about New York Newark. It’s a little surprising given the established guidelines for destination lists states Use city names for destinations (not the airport names), and only disambiguate using airport names when there are multiple airports serving the same city, and separately Differentiate between multiple airports in one city using "–" (en dash) (e.g., "London–Heathrow", not "London Heathrow"). Obviously special cases will exist (Navi Mumbai may well be one of them), but for example New York Newark seems pretty cut and dry… what do other editors think? Danners430 tweaks made 11:54, 26 April 2026 (UTC)[reply]

I wonder if New York–Newark comes under the same bracket as Luton Airport, or should that be London–Luton? The airlines have a vested interest in promoting an airport's proximity and connection with a major city, whilst the local residents might prefer to see themselves as entirely separate. Who exactly qualifies as WP:RS in these cases, and does Wikipedia get the casting vote?
Don't forget that according to Ryanair, some quite obscure and remote airports can be linked to major cities if it suits them. See Hahn airport.

At the request of Ryanair, the major operator of flights to/from the airport, the airport was named Frankfurt-Hahn Airport from 2001

WendlingCrusader (talk) 13:55, 26 April 2026 (UTC)[reply]
My personal view is that WP:COMMONNAME is tangentially applicable here - the list is a list of places you can fly to, so surely it should be what is most commonly listed in booking systems and news articles? So if you’re booking a flight, does it show up as “New York (Newark)” (ignore the formatting for now) or does it show up as simply “Newark”? Danners430 tweaks made 14:10, 26 April 2026 (UTC)[reply]
That sounds like being contrary to the "Wikipedia is not a travel guide" principle. Jan olieslagers (talk) 15:19, 26 April 2026 (UTC)[reply]
Not sure what you mean? There’s been umpteen RfCs as to whether these lists should exist at all, none have decided to remove them… so the lists are here to stay, this is just about how to name the airports in the table. Danners430 tweaks made 15:28, 26 April 2026 (UTC)[reply]
Indeed, that is (or "was", at least) Ryanair's standard policy. Before they would fly to them, Ostend airport had to be renamed "Ostend/Bruges" to attract more (stupid) tourists, and Charleroi had to become "Brussels South". These commercial names to airports are so evaporative that I should like to NOT apply WP:COMMONNAME to aerodromes, but rather use the official name, as can be found in the AIP for major airports, and for many smaller aerodromes. Jan olieslagers (talk) 15:19, 26 April 2026 (UTC)[reply]
@Jan olieslagers per the talk page guidelines, please stop placing your reply above others. Replies go in chronological order. Danners430 tweaks made 15:34, 26 April 2026 (UTC)[reply]
I'm going fishing. Bye bye! Jan olieslagers (talk) 15:37, 26 April 2026 (UTC)[reply]
Fish won't byte :( I always learned to reply just below the phrase I am replying to, with indentation increased one step. Been doing so for many years, and yours is the first ever complaint about it. Enough said? Jan olieslagers (talk) 16:25, 30 April 2026 (UTC)[reply]
I do get what you're saying - but if you notice, my reply is ALSO replying to that same comment... we're both replying to the same comment, and responses should be in chronological order. Indeed, if you click the "reply" link, it will automatically place your reply at the bottom of that thread. Danners430 tweaks made 16:27, 30 April 2026 (UTC)[reply]
I am not in the least surprised that you dont't get my meaning. Let me try to put it another way: if replies in this kind of thread were really wanted and intended to be posted in strictly chronological order, there would be no, zero, nada added value in our indentation system with accumulating ":" signs. Or what do you think we have it for? As I was taught long ago, it serves to keep answers associated with the point they answer to; regardless of chronology. Which seems wise and useful and handy to me, and - for as far as I can see - to all contributors except you. Jan olieslagers (talk) 17:02, 30 April 2026 (UTC)[reply]
That's great - except it goes against the talk page guidelines....... Danners430 tweaks made 17:11, 30 April 2026 (UTC)[reply]
Thank you, but - excusing my stupidity - could you please point me to the exact passus in the talk page guidelines that you keep referring to? It seems not impossible that we are interpreting the text differently. Jan olieslagers (talk) 17:41, 30 April 2026 (UTC)[reply]
I'm specifically talking about Help:Talk pages#Replying to an existing thread - Add your comment below the last entry in the discussion. If you want to respond to a specific comment, you can place your response directly below it. Use a colon (:) to indent your message to create a threaded message. See Indentation below for more information on indenting talk pages with colons., and the section on threading below that - Each comment should be indented one more level than the comment it replies to, which may or may not be the preceding comment. The best explanation is the example box in the threading section, which clearly shows subsequent replies go after intermediate replies (excuse my clumsy wording there). Danners430 tweaks made 17:46, 30 April 2026 (UTC)[reply]
[quote]If you want to respond to a specific comment, you can place your response directly below it. Use a colon (:) to indent your message to create a threaded message.[/quote] This is exactly precisely what I was referring to, and what has ever been normal practice for me. Can we agree up to here? Apologies gently accepted, I know only too well how easy it is to stumble over phrasings, however clumsy or clever! Kindly from Portugal, Jan olieslagers (talk) 18:06, 30 April 2026 (UTC)[reply]
I do agree up to there - however, I’d recommend having a look at the example shown in the threading section. You can see two replies - and the first reply has itself received a reply, yet the second reply to the original comment is underneath the first reply. That example is pretty much exactly what happened here.
I’d also recommend the section on the reply tool - it’s the easiest way to respond to messages. Danners430 tweaks made 18:25, 30 April 2026 (UTC)[reply]
Basically, replies should be indented like this-

First post in a thread

First reply to first post
Reply to first reply to first post
Reply to reply to reply to first post
Second reply to first post
Reply to second reply to first post
Reply to reply to second reply to first post
Reply to reply to reply to second reply to first post
Third reply to first post
Reply to third reply to first post
Reply to reply to third reply to first post
Etcetera. The exact timestamps don't matter here - following the threads downwards does. If the second reply gets two follow-ups before the first one does, the first one's second and third etc, followups still go before all of the second reply's thread. - The Bushranger One ping only 22:02, 30 April 2026 (UTC)[reply]

Airport Subtitle Format

[edit]

Is there a preferred format for airport subtitles[a] in the article lede? There isn't any guidance WP:AIRPORT-CONTENT and I've seen varying approaches:[b]

  • Erie–Ottawa International Airport, (Carl R. Keller Field)
  • Middletown Regional Airport, also known as Hook Field
  • Ohio University Airport or Gordon K. Bush Airport

I would tend to lean toward the second example as the first is confusing due to the absence of a non-bolded word between the official name and subtitle[c] and the third seems to imply a false equivalence between the two names. However, I want to know what others think.

As a secondary question, should the subtitle be included in the infobox in some manner? I've encountered a few cases (1, 2, 3) of the navtivename parameter being improperly used for this purpose. Perhaps a subtitle parameter in the infobox would solve this? –Noha307 (talk) 23:44, 27 April 2026 (UTC)[reply]

Notes

  1. ^ Defined as a secondary name not used as part of the official name of the airport. Almost always either a superseded name for the airport that has been retained and/or one added to honor an individual regarded as important in its history.
  2. ^ I did come across a previous talk page discussion on a similar subject, but it seems to describe two coequal names. For example, at joint-use airports like CFB Goose Bay. Part of the problem is that the airports themselves seem to have conflicting usage and unclear branding (e.g. 1, 2, 3) in regard to these names.
  3. ^ As per MOS:BOLDALTNAMES, which states the first occurrence of the title and significant alternative names ... are placed in bold, the subtitles should very likely be bolded, as they would strongly seem to qualify as significant.

AIRPORT-CONTENT

[edit]

Just to let the WikiProject know, I've boldly updated WP:AIRPORT-CONTENT to reflect the closure of the most recent destination list RfC, as well as add the one before that. I've also made a few tweaks. Please feel free to tweak as needed! Danners430 tweaks made 16:05, 30 April 2026 (UTC)[reply]

There is a requested move discussion at Talk:Uyuni Airport#Requested move 10 April 2026 that may be of interest to members of this WikiProject. TarnishedPathtalk 12:00, 1 May 2026 (UTC)[reply]

Distance from...

[edit]

There is a wide variation of distances given in the lead of airport articles. A few examples in the UK include:

  • Foobar airport is 5 nautical miles (9 km; 6 mi) north of Dullsville
  • Foobar airport is 6 miles (10 km) north of Dullsville
  • Foobar airport is 6 miles (10 km; 5 NM) north of Dullsville
  • Foobar airport is six miles (ten kilometres) north of Dullsville

So I looked but cannot find definitive guidance in this project. The last example, spelled-out, I dislike intensely, but I have no strong feelings on miles vs kilometres vs nautical miles, I just like things to be consistent across airports in the same country.

Thoughts / pointers to existing guidance? 10mmsocket (talk) 07:35, 5 May 2026 (UTC)[reply]

My 2 cents: Nautical miles not te be used in this context (but some AIP's give the information like this); use decimal or imperial depending on what is usual in the given place, with autoconversion. Jan olieslagers (talk) 10:54, 5 May 2026 (UTC)[reply]
I believe in many cases, at least in the United States, it is taken directly from the FAA's Airport Master Record which has "CBD TO AIRPORT (NM):" as point #3 on the form and which takes a value of, for example, "03 SE", or "3 nautical miles southeast". –Noha307 (talk) 03:19, 13 May 2026 (UTC)[reply]
I have been editing (removing) these nautical miles for about a month now, so I welcome this discussion, although it's a pity I have only just noticed it today.
  1. Whilst airports have a specific reference point, I don't know how that applies to towns and cities, except in the case of London with some people regarding Charing Cross as the notional centre. But what about other places in the UK? So it is a plain fact these distances can only be approximations.
  2. Further evidence of this comes because the numbers are invariably rounded to whole nautical miles, as listed by the OP above.
  3. Against that, other countries may use fractions of NM, as in Antwerp airport is "2.9 NM SE of Antwerp". As to exactly where in Antwerp that relates, I don't know, but my guess is that the authorities in Belgium measured the distance in km first, rounded it off, and then converted it to 2.9 NM. Most probably a classic case of false precision?
  4. My viewpoint is that if we were dealing with anything that was not an airfield, and we didn't have the benefit of the CAA loading the gun, we would simply cite miles and km, rounded to an appropriate accuracy. For example, take Slough. No, really, please take it!
Footnote; I am using the following template {{convert|5|NM|mi km|0|order=out}} which starts with NM but outputs 6 miles (9 km)
WendlingCrusader (talk) 14:36, 14 May 2026 (UTC)[reply]
For the UK, the number in NM can be referenced because it's on the second row of the NATS page for the airport, e.g. for Heathrow. So we could use the number but I think it's of little encyclopaedic value, so using your conversion example is a good idea. 10mmsocket (talk) 16:50, 14 May 2026 (UTC)[reply]

There is a requested move discussion at Talk:Western Sydney International Airport#Requested move 19 May 2026 that may be of interest to members of this WikiProject. Qwerty123M (talk) 03:13, 19 May 2026 (UTC)[reply]

When linked to as a destination from other airports, can we agree to call this simply "Navi Mumbai"? I'm seeing some edits using "Mumbai-Navi", but we don't call NYC "York-New". Asamboi (talk) 22:26, 18 May 2026 (UTC)[reply]

The question is whether the airport serves the city of Mumbai (which it does) or whether Navi Mumbai is its own district. New York is a different matter - although yes, by our guidelines we should be using “New York-JFK” for example. It’s probably best a question asked at the WikiProject level rather than here, since it affects many articles, not just this one. Danners430 tweaks made 06:03, 19 May 2026 (UTC)[reply]
Navi Mumbai is administratively a separate city, it's not a part of the city of Mumbai. Asamboi (talk) 12:13, 19 May 2026 (UTC)[reply]
Literally even the lead of this article states that it's in the Mumbai metropolitan region. Same as how London Luton is referred to as London despite being miles away. But again - it's a debate for the WikiProject since we're discussing edits in other articles. Danners430 tweaks made 12:16, 19 May 2026 (UTC)[reply]
Newark Liberty International Airport is in the NYC metro region, but its agreed short form on Wikipedia is "Newark", not "New York-Newark". Asamboi (talk) 12:18, 19 May 2026 (UTC)[reply]
It hasn't necessarily been agreed - it's only been brought up once when discussing something unrelated… and I'd argue strongly against it being known simply as Newark - you fly to New York (Newark) airport, you don't buy a ticket to Newark.
Now I'm going to close this and move this to the WikiProject as for the last time, this isn't a discussion that can be had here. Danners430 tweaks made 12:37, 19 May 2026 (UTC)[reply]
@Asamboi Discussion moved here as the appropriate venue. Danners430 tweaks made 12:39, 19 May 2026 (UTC)[reply]
Also pinging @WendlingCrusader and @Jan olieslagers as you participated in the related discussion above Danners430 tweaks made 12:40, 19 May 2026 (UTC)[reply]
I have already given as my opinion that aerodromes should be named in WP as they are in the AIP, overruling WP:COMMONNAME. Jan olieslagers (talk) 16:51, 19 May 2026 (UTC)[reply]
This is nothing to do with naming of articles - but how they are listed in destination lists. I would still disagree however - COMMONNAME is policy. Danners430 tweaks made 16:55, 19 May 2026 (UTC)[reply]
Please read more carefully. I did not mention the naming of articles. I did mention the naming of aerodromes. Jan olieslagers (talk) 17:32, 19 May 2026 (UTC)[reply]
… you said “aerodromes should be named in WP…” - to most people that would read as though you’re talking about what that airport should be called on Wikipedia which usually refers to the article name. But understood if that’s not what you meant. Danners430 tweaks made 18:05, 19 May 2026 (UTC)[reply]
This does, in my opinion, raise the question of whether the blanket rule for airport naming where there are multiple airports serving a single city is appropriate, or whether we should start a list of exceptions. For example:
  • Navi Mumbai, the subject of this discussion - even the article itself is named Navi Mumbai as the COMMONNAME
  • New York airports - Newark for example is currently simply called "Newark" (I personally would like to see it changed to New York Newark, but that's besides the point)
  • London airports - the majority of London's airports are already named in the format "London [Airport]" - albeit without the hyphen.
Personally, and of course I'm open to discussion here, we should keep the existing guidance in WP:AIRPORT-CONTENT - but include a list of exceptions, which we can agree on here or on a case-by-case basis. Danners430 tweaks made 12:57, 19 May 2026 (UTC)[reply]
(Please forgive me if this response is in the wrong place; I don't wish to intervene in the scrap involving Jan.)
So, the penny has just dropped regarding the name Navi Mumbai. I now read that it means New Mumbai, hence the OPs reference to York‑New. Presumably "Navi" is obvious to some people, but as this is EN-Wikipedia, many would only see the "Navi Mumbai" as two words that make up a foreign-language name. In that context, the OP has a fair point that 'Mumbai - Navi' is inappropriate. The nearest equivalent situation I can think of is... (ironically), Delhi versus New Delhi airport. In fact the situations appear all but identical, with two closely related cities, and an airport serving both.
A quick poll of destination lists (Heathrow, Cairo, Helsinki) shows that flights to New Delhi airport (in the city of New Delhi) are typically reduced to a simple Delhi in destination lists. By that measure, flights to Navi Mumbai airport should always be listed as simply as Mumbai. Sorted!
WendlingCrusader (talk) 18:48, 19 May 2026 (UTC)[reply]
The issue with Mumbai is that Mumbai has a second airport - Chhatrapati Shivaji Maharaj International Airport, which would be shortened to Mumbai-Shivaji, since both are listed as serving the metropolitan area of Mumbai. Danners430 tweaks made 19:45, 19 May 2026 (UTC)[reply]
CSMI is not Mumbai's second airport, it's Mumbai's only airport.
A better analog for Navi Mumbai is Noida International Airport, which is in the greater Delhi region, but is located in the city of Noida, Uttar Pradesh (think Newark, New Jersey). Asamboi (talk) 21:22, 19 May 2026 (UTC)[reply]
The lead of Navi Mumbai literally says it serves the metropolitan area of Mumbai… Therefore the metropolitan area of Mumbai has two airports. Danners430 tweaks made 21:45, 19 May 2026 (UTC)[reply]
The Mumbai Metropolitan Region (note capital letters) spans 6,328 sq.km and extends far beyond the city of Mumbai. It is roughly analogous to the New York metropolitan area, which contains the airports of JFK and LaGuardia (which are in New York City proper) as well as Newark (which is in the metro area, but not in New York).
The agreed short forms for the airports in New York proper are New York-JFK and New York-LaGuardia; the one outside NYC is Newark. Likewise, the short form of the one airport in Mumbai proper is simply "Mumbai", and while the one outside it is "Navi Mumbai".
This is all incredibly obvious to anybody who is familiar with the cities in question, and it's rather frustrating to have to debate this with people who, with all due respect, clearly are not. Asamboi (talk) 08:27, 20 May 2026 (UTC)[reply]
I feel like one thing needs to be made very clear… Wikipedia is a worldwide project - it’s not written for local people, it’s written for ALL readers - whether said reader is familiar or unfamiliar with the local area. If there are nuances that are only known to people who is familiar with the cities in question, then said nuances either need explaining to the reader (such as you would with an abbreviation) or excluded altogether.
Please don’t take this the wrong way - but Wikipedia is NOT written for the people of Mumbai. It’s written for everyone.
In this specific case, the nuance is the fact that Navi Mumbai is not in the city of Mumbai itself, but rather a suburb - but still part of the same metropolitan area. So tell me - how exactly do you expect someone who isn’t intimately familiar with Mumbai to know which airport is being referred to when all they see is “Mumbai”? Answer - you can’t. Because they don’t have the background knowledge. So how do we solve that? By differentiating the two airports - one is Navi Mumbai, the other Mumbai-Shivaji.
Oh and by the way, you still haven’t pointed to where it was ever agreed that New York (Newark) be referred to simply as “Newark” when it too serves NY, same as JFK and Laguardia. Danners430 tweaks made 08:35, 20 May 2026 (UTC)[reply]
First up, my initial plea was that we call Navi Mumbai airport "Navi Mumbai", not "Mumbai-Navi" (shudder). I see you've come around to agree with me on this, so that's great.
If you want to start calling BOM something else, that's actually a different debate, both whether it's necessary (no) and what the disambiguation would be. Again, locals would not call it Mumbai-Shivaji (it's in fact a running joke locally that everything in Mumbai is called Shivaji), it would be Mumbai-CSMI, just like the airport in NYC is not New York-Kennedy but New York-JFK. (And the I in CSMI is important, because CSMT is a railway station!)
Finally, calling EWR "Newark" is an established consensus that I had nothing do with. If you'd like to try to overturn it, be my guest, but the burden of proof to form a new consensus that this is superior is on you. Asamboi (talk) 08:54, 20 May 2026 (UTC)[reply]
If you look at the post I posted above... this is a bigger debate than just Mumbai. There have been other disagreements about such naming schemes beyond simply Mumbai - so it's time to stop having individual discussions, and have a broader discussion as to whether the current guidelines are fit for purpose. Because if we apply the current guidelines, Navi Mumbai does become Mumbai-Navi, JFK becomes New York-JFK, Newark becomes New York-Newark, LaGuardia becomes New York-LaGuardia, and Heathrow becomes London-Heathrow. I think we're all in agreement that this may be appropriate in the majority of situations where a city has two airports - but in many cases, such as those under discussion, it doesn't work. So we need to come up with something better, or establish a list of agreed-upon exceptions. Danners430 tweaks made 08:58, 20 May 2026 (UTC)[reply]
... and the something better and/or the agreed-upon exceptions should work equally well regardless of whether or not the reader has local knowledge. "Mumbai-Navi" for NMI makes a local shudder, but "Mumbai" (undisambiguated) for BOM is potentially confusing to non-locals. Rosbif73 (talk) 09:12, 20 May 2026 (UTC)[reply]
... where have I disagreed with that? I'm simply trying to get a wider discussion going... Danners430 tweaks made 09:14, 20 May 2026 (UTC)[reply]
Sorry, I was just attempting to clarify the requirement, not suggesting that any of the current participants hadn't understood. Rosbif73 (talk) 09:21, 20 May 2026 (UTC)[reply]
The current guidelines state Use city names for destinations (not the airport names), and only disambiguate using airport names when there are multiple airports serving the same city.
Since Mumbai and Navi Mumbai are not the same city, the correct airport name is "Navi Mumbai".
Even if you believe they are the same city and thus need disambiguation, the name would be "Mumbai-Navi Mumbai".
But there is no universe where NMI is called "Mumbai-Navi", because neither the airport nor the city is called "Navi". It's an inseparable part of the name, just like we don't call JFK "York-New". Asamboi (talk) 11:25, 20 May 2026 (UTC)[reply]
That’s essentially the point I’m making though - that the guidelines need overhauling Danners430 tweaks made 11:28, 20 May 2026 (UTC)[reply]
Uhh, no, I'm stating that the guidelines are fine and it's only your interpretation of them that's wrong.
If you want to propose revising them in general, then I suggest you create a new thread for that, because the title of this one is scoped to NMI. Asamboi (talk) 11:36, 20 May 2026 (UTC)[reply]
Except the guidelines are far from fine. We’ve agreed on an exception for Navi Mumbai (I’m not going to argue the point here - it’s an exception to the norm), and we’ve identified further exceptions such as NY Newark. I’ll happily create another thread, but I resent your assertion that my interpretation is “wrong”. Danners430 tweaks made 11:48, 20 May 2026 (UTC)[reply]
How is it an exception? The current guidelines say you use city alone (Navi Mumbai) or city and airport (Mumbai-Navi Mumbai). You can't get "Mumbai-Navi" out of them, because "Navi" is neither city nor airport. Asamboi (talk) 12:18, 20 May 2026 (UTC)[reply]
Read Rosbif’s response below regarding what the majority of people understand to be the city of Mumbai. I’m not arguing with you on this any further. Danners430 tweaks made 12:21, 20 May 2026 (UTC)[reply]
Quoting myself: Even if you believe they are the same city and thus need disambiguation, the name would be "Mumbai-Navi Mumbai". The name of the airport is not "Navi" and it cannot be abbreviated "Navi". Asamboi (talk) 12:30, 20 May 2026 (UTC)[reply]
I consider this discussion closed. You’re arguing over a nonsensical point even though we’ve already agreed to call the airport “Navi Mumbai” which is what you wanted in the first place. WP:DROPTHESTICK. Danners430 tweaks made 12:37, 20 May 2026 (UTC)[reply]
While I appreciate your frustration, the problem is that we're discussing the link text for use on the destination lists of other airport articles, and the majority of readers of those articles will not be familiar with, and probably not even care about, the distinction between the various cities forming the metropolitan area, any more than they care whether London City Airport is in the City of London (it isn't). All they care about is the area that each airport serves. If they wanted to visit Mumbai, they would presumably be equally well served by flights to BOM or NMI. Rosbif73 (talk) 08:41, 20 May 2026 (UTC)[reply]
I agree with this. Neither "Mumbai" nor "Navi Mumbai" need disambiguation. — Reywas92Talk 13:44, 20 May 2026 (UTC)[reply]
Navi Mumbai doesn't, since "Navi" is, in effect, the disambiguation. However the other airport in the Mumbai metro area - Shivaji - does need disambiguating so it's clear it's not the same as Navi. Again, we may know it as an obvious fact... but the general reader does not. Danners430 tweaks made 13:59, 20 May 2026 (UTC)[reply]
I think the current common usage already makes the distinction clear enough. When searching on airline booking platforms, the airports are shown simply as “Mumbai” and “Navi Mumbai”, That reflects how passengers and the general public actually identify these airports. “Mumbai” alone is still overwhelmingly associated with the main airport. “Mumbai-Shivaji” or “Mumbai-CSM” feel artificial and are not widely used by normal travelers. UrbanGridIndia (talk) 18:26, 20 May 2026 (UTC)[reply]
I’m sorry but I fundamentally disagree. If you have simply “Mumbai”, any reader that doesn’t happen to know about the existence of Navi Mumbai then the reader has no idea which airport is meant. Obviously if Navi Mumbai is also served by the same airline that confusion doesn’t occur - but that’s very rare… readers would normally only see “Mumbai” or “Navi Mumbai” in isolation - and seeing “Mumbai” without the context of the existence of Navi makes for confusion. Danners430 tweaks made 18:52, 20 May 2026 (UTC)[reply]
Can you please stop saying silly phrases like "the existence of Navi"? As you know, it's not called Navi! Newark isn't confusing because of the existence of New either. Just because Navi Mumbai exists does not mean that "Mumbai" isn't straightforwardly Mumbai Airport. Unlike Rome Airport, London Airport, New York Airport, Moscow Airport, Paris Airport, and others of Category:Airport disambiguation pages, Mumbai Airport is known to be the airport in Mumbai, and both readers informed and uninformed of the Navi Mumbai airport opening can understand that. No one says "Mumbai Shivaji" like they say "London Heathrow" or "Paris Orly". The preexisting airport is not (yet) called any other way besides Mumbai airport or its full official name. Reywas92Talk 20:16, 20 May 2026 (UTC)[reply]
Oh I didn’t realise it was mandatory to say certain things. Sorry, I’ll say what I please.
It doesn’t matter that nobody says “Mumbai Shivaji” - if a normal reader, ie one that doesn’t know the difference between Mumbai City and Navi Mumbai, reads a destination list that only lists “Mumbai Airport” - what do you think they will think? They won’t know whether it’s the airport actually in Mumbai City, or whether it’s the airport in Navi Mumbai… because there’s no reference point for them. Nobody is disputing that the metro area of Mumbai has two airports - one in the city itself, and one in Navi Mumbai. But to the casual reader, who at the end of the day is who Wikipedia is written for whether we like it or not, the two airports need to be differentiated. Easy enough with Navi - it’s simply “Navi Mumbai Airport”, listed as “Navi Mumbai”. But the other one, because it’s also called Mumbai and in the same metropolitan area, can’t simply be called “Mumbai” because it will cause confusion to said regular reader - hence the disambiguator. If you have a better disambiguator than “Shivaji”, by all means suggest it. Danners430 tweaks made 21:12, 20 May 2026 (UTC)[reply]
I applaud @Danners430 for struggling against the tide of inconsistent dissent here. On the one hand we have @Asamboi freely admitting that the whole city (of Delhi) is frequently but mistakenly called "New Delhi", whilst @Reywas92 earnestly insists that readers both informed and uninformed of the Navi Mumbai airport opening must surely understand that Mumbai Airport is known to be the airport in Mumbai. Let me give you a reality check and remind you that this is EN-Wikipedia, and that many readers here struggle with the basic definition of what exactly is London, let alone the megacity of Delhi or whatever makes up Mumbai and its metropolitan area.
Those of us with a degree in local geography might point out that London City airport is best placed to serve the East End, whilst Heathrow is much closer to the West End, and both Luton and Stansted are perfect for North London, except that term is typically only used in the context of a football derby between Arsenal and Spurs.
Ridiculous? Yes. Now try to imagine how your arguments might sound to others. And I don't believe it is just me.
@Danners430 is working his socks off to try to arrive at a solution here, that hopefully assists all readers, even if doesn't suit all editors. He deserves your support in that endeavour.
WendlingCrusader (talk) 23:05, 20 May 2026 (UTC)[reply]
Readers both informed and uninformed of the Navi Mumbai airport opening must surely understand that Mumbai Airport is known to be the airport in Mumbai. Well, yes, having Mumbai Airport link to Mumbai Airport in Mumbai would seem pretty obvious even to the uninformed :)
Slightly more seriously, names are complicated and we have to assume some degree of familiarity, particularly in the tight confines of an airline destination list. Luzhou can be confused with Liuzhou, Xi'an Xianyang Airport is not Xiangyang Airport, Kertajati is the main airport for Bandung while the airport commonly known as Bandung Airport isn't, etc.
And TBH even the disambiguations don't help if you really have no idea: quick, is the main airport of Kuala Lumpur Kuala Lumpur-Subang or Kuala Lumpur-Sepang? If I'm visiting Sao Paulo, should I fly into Congonhas or Guarulhos? But if a reader is unsure, they can always click on the link and find out. Asamboi (talk) 06:13, 21 May 2026 (UTC)[reply]
It's actually not analogous at all. New Delhi is a district of the city of Delhi, and it contains no airports at all. (It is, however, the capital of India, which is why the whole city is often but mistakenly called "New Delhi".) Indira Gandhi International Airport aka Delhi International Airport is in Delhi, but not New Delhi. Asamboi (talk) 21:19, 19 May 2026 (UTC)[reply]
(I'm a resident of Navi Mumbai) I don't want to take part in whether disambiguation should or should not happen, just providing name suggestions:
  • BOM: Mumbai, Mumbai-CSM, Mumbai-BOM, Mumbai-Chhatrapati (Shivaji is just a random word in the name)
  • NMI: Navi Mumbai, Mumbai-NMI (Navi just means new)
I would also like to point out an interesting fact, NMI isn't in the city of Navi Mumbai, it's not even in the same district. The closest city is Panvel, which comes up to the border of the airport in the east. These parts of Panvel, along with Ulwe on the western side of the airport, were supposed to be part of Navi Mumbai when they were built, but that didn't end up happening. A lot of people, even in Mumbai, treat these as part of Navi Mumbai, but they are as much a part of Navi Mumbai as Navi Mumbai is of Mumbai. Arnav Bhate (talkcontribs) 10:49, 22 May 2026 (UTC)[reply]

Airport naming in destination lists

[edit]

Since the above thread has devolved into nonsensical arguments… I’d like to propose that we need to update the guidelines relating to what airports are called in another airport article’s destination list. The current guidelines state that where a city has multiple airports, they should be written in the format [City]-[Airport disambiguator] - for example Rome-Fiunicino. While this works in the majority of cases, it doesn’t always fit - for example Navi Mumbai instead of Mumbai-Navi.

Do we revise the guidelines, or do we create a list of exceptions? Danners430 tweaks made 11:51, 20 May 2026 (UTC)[reply]

  • Oppose. The guidelines are just fine in general, and they also work just fine for the specific case of Navi Mumbai.
The whole thread above, which explains all of this in excruciating detail, seems to resolve around the misconception that there's an airport called "Navi" that is in "Mumbai". But it's not: Navi Mumbai International Airport is thus named because it's in the city of Navi Mumbai, and "Navi Mumbai" is a single inseparable unit like "New York". You can't call the airport Mumbai-Navi any more than you can call JFK "York-New JFK" or MSY "Orleans-New". Asamboi (talk) 12:29, 20 May 2026 (UTC)[reply]
I’m not going to get into another pointless debate about Mumbai. There are thousands of other cities around the world with multiple airports in a single city aside from Mumbai which I’m addressing here. And your point about “York-New” is absolute nonsense, since New York is the city name - “New” isn’t the disambiguator. Danners430 tweaks made 12:32, 20 May 2026 (UTC)[reply]
And in the case under discussion, "Navi Mumbay" is the name of the city. The parallellism with "New York" is obvious: calling the airport "Navi-Bombay" is ridiculous. Just as ridiculous "York-New" Jan olieslagers (talk) 12:39, 20 May 2026 (UTC)[reply]
To anyone except people that happen to know about Mumbai geography, the city in question is Mumbai. For the last and final time, this discussion is not about Mumbai - it is a general discussion about the naming of all airports. The discussion about Mumbai is above, not here. Asamboi, you wanted me to split out the discussion since it was about a broader topic, I have done so. Stop circling back to the topic being discussed elsewhere. Danners430 tweaks made 12:46, 20 May 2026 (UTC)[reply]
“York-New” is absolute nonsense, since New York is the city name - “New” isn’t the disambiguator. That's exactly right! And "Navi" is not the disambiguator either! You're so close to finally understanding this now :) Asamboi (talk) 22:41, 20 May 2026 (UTC)[reply]
I’m going to pretend you never wrote that last sentence, as otherwise I’d be leaving a note about WP:CIVIL on your talk page. And you appear to have completely ignored what I said above. This is nothing whatsoever to do with Mumbai. Seriously pal - WP:DROPTHESTICK. Danners430 tweaks made 22:49, 20 May 2026 (UTC)[reply]
The difficulty here is that literally the only example you have proposed to argue that the current scheme is broken is Mumbai. If there are others, please list a few of them, tell us how the current guidelines are failing them, and propose alternatives. Asamboi (talk) 05:55, 21 May 2026 (UTC)[reply]
The relevant part of the guidelines states Use city names for destinations (not the airport names), and only disambiguate using airport names when there are multiple airports serving the same city.. It seems to me that the primary issue is the definition of "city" – EWR is not in New York City (nor even in the state of New York), NMI is not in the city of Mumbai, none of London's airports are in the City of London and only two of the six are in the London boroughs, and so on. It would be tempting to suggest simply replacing "city" by "metropolitan area" in the guidelines, but the administrative definition and the general understanding (as interpreted both by locals and by others who are less familiar with the locality) of what constitutes each city and its metropolitan area varies considerably. Compounding that, we have airports marketed as serving given cities but not actually located anywhere near the city or its metropolitan area (XCR purporting to serve Paris despite being 150 km from the city centre, for example). Rosbif73 (talk) 12:48, 20 May 2026 (UTC)[reply]
My personal thought would be to apply a form of WP:COMMONNAME honestly - what would the general public (ie the reader) know the airport as? The most extreme example I can think of is Frankfurt-Hahn - thanks to Ryanair’s aggressive marketing, pretty much everyone knows it as Frankfurt Hahn, despite being closer to Luxembourg!
So in cases like London, not much changes - it’s still London Heathrow, London City, London Gatwick etc. Same with New York (New York JFK, New York Newark) and Mumbai (Mumbai Shivaji, Navi Mumbai). Note the latter - there needs to be flexibility to allow for situations like NMI where the standard format doesn’t really work, to allow us to name it “Navi Mumbai”.
Other airports, such as Rome Fiunicino, would remain unchanged unless we decide to change it Danners430 tweaks made 12:55, 20 May 2026 (UTC)[reply]
Note that I've just made a BOLD change which I trust will satisfy participants here without substantially changing the intent of the guidelines. Rosbif73 (talk) 07:11, 21 May 2026 (UTC)[reply]

 You are invited to join the discussion at Wikipedia:Village pump (proposals) § RFC: Should we remove mentions of public transport access from infoboxes. Zackmann08's proposal seeks to remove the parking= and publictransit= parameters from several infoboxes. Thryduulf (talk) 22:26, 22 May 2026 (UTC)[reply]

3rd opinion - flag icons

[edit]

There seems to be a bit of an impasse at Talk:Amsterdam Airport Schiphol over the use of flag icons in the stats section of the article. Some other opinions would be welcome at this point. 10mmsocket (talk) 15:08, 25 May 2026 (UTC)[reply]

Airport naming in destination lists for Delhi and Noida airports

[edit]

I noticed that, following the opening of Noida International Airport, several destination lists have been updated to replace "Delhi" with "Delhi–Gandhi" and "Noida" with "Delhi–Noida".

However, Noida International Airport is located in Uttar Pradesh and primarily serves Noida and western Uttar Pradesh rather than Delhi itself. Referring to the airport as "Delhi–Noida" may be misleading, as readers unfamiliar with the region could assume that the airport is located in Delhi or primarily serves Delhi. WP:AIRPORT-CONTENT states that destination lists should use the actual city served and provides examples such as "Beauvais", not "Paris–Beauvais", and "Rygge", not "Oslo–Rygge". Based on this wording, I believe "Noida" would be more consistent with the guideline than "Delhi–Noida", since the airport is located in and primarily serves Noida rather than Delhi. UrbanGridIndia (talk) 17:16, 15 June 2026 (UTC)[reply]

AFAIK, Noida International Airport was built to relieve traffic at Indira Gandhi International Airport and serve the wider NCR, not just Uttar Pradesh. There are sources describe it as part of the Delhi-NCR airport system. Even its IATA code, DXN, uses "D" for Delhi.
A comparable example is Soekarno–Hatta International Airport in Indonesia. Although it is located in Tangerang, destination lists use "Jakarta" because that is the metropolitan area it primarily serves. Likewise, "Delhi–Noida" can be understood as describing the market served rather than the airport's administrative location, while also differentiating it from the existing Delhi airport, which will be referred to as "Delhi–Gandhi". Ckfasdf (talk) 18:22, 15 June 2026 (UTC)[reply]
I do not think the comparison with Soekarno–Hatta International Airport is entirely equivalent. Although It is located in Tangerang, it is situated immediately adjacent to the Jakarta. In contrast, Noida International Airport is approximately 80 km from Delhi which makes it a less practical option for most passengers travelling to or from Delhi.
For this reason, I believe that describing the airport as "Delhi–Noida" may overstate its connection with Delhi and could be misleading to readers who are unfamiliar with the region. UrbanGridIndia (talk) 01:56, 16 June 2026 (UTC)[reply]
Since I am Indonesian, I may be a bit biased by Indonesian practice. Another similar example is Narita International Airport. Although it is located in Chiba Prefecture, about 60 km east of central Tokyo, we generally use "Tokyo–Narita" in destination lists.
WP:AIRPORT-CONTENT also states, Use city names for destinations (not the airport names), and only disambiguate using airport names when there are multiple airports serving the same city or metropolitan area. To me, this suggests that we should follow the market served, rather than the airport's administrative division. Since Noida International Airport is intended to serve the Delhii-NCR market alongside IGI Airport, "Delhi–Noida" seems consistent with that approach. Ckfasdf (talk) 12:59, 16 June 2026 (UTC)[reply]
By that logic we should rename Newark to New York–Newark instead of just Newark. Will that be considered valid? Newark too serves the Metropolitan areas of New Yowk City itself.
Noida, Ghaziabad are totally different cities than Delhi. They maybe built to reduce congestion in Delhi Airport but this argument is totally vague to rename Noida as Delhi–Noida or Ghaziabad as Delhi–Hindon. Doesn't make sense at all. Same goes for Mumbai and Navi Mumbai as well. And this terminology is more confusing than if they are mentioned as different cities. FlyJet777 (talk) 13:32, 16 June 2026 (UTC)[reply]
And I for one would wholeheartedly agree with such logic. The airports are built to serve a specific place, and passengers purchase tickets to that specific place. They don’t buy tickets to Newark, they buy tickets to New York, and 9/10 times they happen to go to Newark, JFK etc. Danners430 tweaks made 13:51, 16 June 2026 (UTC)[reply]
I guess I'm the 1/10...I fly specifically to Newark often, not a ticket to New York. Reywas92Talk 14:00, 16 June 2026 (UTC)[reply]
How's that any different to a number of people choosing to specifically fly into London Gatwick because it's more convenient, or similarly choosing to fly into laGuardia because it's closer to their destination? Danners430 tweaks made 14:01, 16 June 2026 (UTC)[reply]
Because Newark airport is named for the city and known as such. "Gatwick" is only a name not a city and therefore simply cannot be your destination, so it has to specify London as the place served. I wouldn't put only "LaGuardia" in the lists since that's also a name, but that can be done for Newark. Reywas92Talk 14:19, 16 June 2026 (UTC)[reply]
All three of those are the same in that they are airports that serve a larger city (New York or London), named after something else (Newark, Gatwick or LaGuardia) because it's necessary to differentiate between multiple airports in reasonably close proximity, all serving the same large city. Newark serves New York primarily, it is located in Newark. That is why I've argued it should be New York-Newark or New York (Newark) previously. LaGuardia and Gatwick are the same. Those are literally just the two that sprung to mind. Danners430 tweaks made 14:23, 16 June 2026 (UTC)[reply]
And flights to Hollywood Burbank Airport and Long Beach Airport are listed as to "Burbank" and "Long Beach" even though many users of those airports are actually going to Los Angeles or elsewhere in the Los Angeles metropolitan area. It's unnecessary to say "Los Angeles–Burbank" and "Los Angeles–Long Beach" either. Now when I start typing in Los Angeles at https://www.alaskaair.com/ it gives me options for LAX, LGB, SNA, BUR, and ONT, but I don't think we need excessive grouping and unnecessary disambiguation in these tables just because airports' catchment areas overlap in a region. Reywas92Talk 14:57, 16 June 2026 (UTC)[reply]
Gatwick was originally a locality too (first attested in the 13th century, and Gatwick Manor continued to exist until it was subsumed into the airport), but that's beside the point. The point is that airports don't generally serve single cities, and indeed often aren't even located in the city they are named after. Another important point that we must consider is that a "city" is a geographic entity whose definition varies widely from one country to another. Rosbif73 (talk) 14:31, 16 June 2026 (UTC)[reply]
Destination lists should primarily use city names, with disambiguation only when necessary. UrbanGridIndia (talk) 13:33, 16 June 2026 (UTC)[reply]
Noida International Airport's primary function is to serve the cities of Noida and Greater Noida alongside Mathura-Vrindavan and the secondary function is to de-congest Delhi Airport. The airport doesn't serve the city of Delhi. Terming it as Delhi–Noida only creates more confusion than giving clarity. I propose we write Navi Mumbai, Ghaziabad and Noida by their respective city names only. FlyJet777 (talk) 13:40, 16 June 2026 (UTC)[reply]
Wholeheartedly oppose, for the reasons I just mentioned above. Danners430 tweaks made 13:51, 16 June 2026 (UTC)[reply]
I see that "or metropolitan area" was unilaterally added last month. I don't see a consensus for that and have reverted that. — Reywas92Talk 13:53, 16 June 2026 (UTC)[reply]
It was part of a discussion directly above, and was added without as part of that discussion. Pinging @Rosbif73 Danners430 tweaks made 13:56, 16 June 2026 (UTC)[reply]
Yes, I added that "or metropolitan area" BOLDly, but I referenced the then-ongoing discussion in my edit summary and mentioned the edit in the discussion. I fail to see why it should be contentious: airports' catchment areas are generally more extensive than just single cities. Rosbif73 (talk) 14:22, 16 June 2026 (UTC)[reply]
At this point a flight to "Delhi" is unambiguously a flight to Delhi Airport, which redirects to Indira Gandhi International Airport. Whether or not Noida airport is referred to as just Noida, I don't think "Delhi" needs any disambiguation. — Reywas92Talk 13:56, 16 June 2026 (UTC)[reply]
Every place I've looked, I'm being sold tickets to "Delhi", and that includes both airports. Indeed, the latter's lead section even includes the sourced statement The airport is intended to complement Indira Gandhi International Airport as part of the Delhi-NCR region's dual-airport system. It is literally designed to serve Delhi and the National Capital Region, in the exact same way that IGIA is. Danners430 tweaks made 13:59, 16 June 2026 (UTC)[reply]
Imagine a person travelling to delhi books a flight to Noida Airport, only to later discover that thay have to take a two hour drive to reach Delhi. UrbanGridIndia (talk) 14:09, 16 June 2026 (UTC)[reply]
So what you're saying is the article, which you have helped write, is wrong, and the source that states it serves Delhi and the NCR is wrong? Danners430 tweaks made 14:10, 16 June 2026 (UTC)[reply]
It is unlikely that this airport will serve Delhi, given that Delhi is already served by its own major international airport. UrbanGridIndia (talk) 14:17, 16 June 2026 (UTC)[reply]
Again - there is a sourced statemene that says that it does already serve Delhi. Again, are you claiming that the source is wrong? Danners430 tweaks made 14:18, 16 June 2026 (UTC)[reply]
Could you share the source? UrbanGridIndia (talk) 15:45, 16 June 2026 (UTC)[reply]
Got it. Apologies for the oversight. UrbanGridIndia (talk) 15:56, 16 June 2026 (UTC)[reply]
Excuse me but what part of Mumbai and Navi Mumbai or Delhi and Noida are different cities is hard to understand? Are San Jose and San Francisco the same cities as well? or New York and Newark are same?
Regarding the tickets, whenever I look for flights to NYC I see flights to EWR as well. So what? Sorry to say but your argument doesn't make any sense. @Danners430 FlyJet777 (talk) 14:03, 16 June 2026 (UTC)[reply]
Pinging @Asamboi to the discussion. FlyJet777 (talk) 14:04, 16 June 2026 (UTC)[reply]
Literally directly above your comment, I've quoted part of the Noida article lead, which is sourced. It literally serves Delhi. An airport does not have to be in a city to serve that city. London Heathrow isn't in London City, neither are the vast majority of airports. That doesn't mean they don't serve that city as that is the primary destination for travellers. We list the city served by an airport in the destination list, we always have, and the guidelines have stated this for years. Why are we changing this now? Danners430 tweaks made 14:08, 16 June 2026 (UTC)[reply]
NCR is a vast region having multiple cities. Noida & Greater Noida too come in that region. Also as I mentioned above, if we go by your logic then we should re-write Newark as New York–Newark. But that won't make any sense as those two are different cities serving different cities. Noida International Airport primarily caters Noida & Greater Noida, not Delhi. Also this source here [Airport] clearly mentions that the airport will cater to residents of Noida, Greater Noida & Western UP, not Delhi (primarily).
The logic you are applying here would be applicable if we had proposed writing Jewar instead of Noida as the airport is geographically located in Jewar. But that's clearly not the case here. FlyJet777 (talk) 14:19, 16 June 2026 (UTC)[reply]
This isn't my logic - it's literally stated in the Noida article that it serves Delhi. As I said to UrbanGridIndia - are we claiming the source is wrong? Danners430 tweaks made 14:21, 16 June 2026 (UTC)[reply]
I suggest you to read the last para of the source you quoted Delhi-NCR airport system. It caters to many states, but primarily Noida & Greater Noida. Not Delhi or Uttarakhand or anywhere else. FlyJet777 (talk) 14:27, 16 June 2026 (UTC)[reply]
Noida airport serves NCR - Yes
Does it serve Delhi - No
Noida airport almost 80km away can’t serve Delhi which already has India’s largest airport. UrbanGridIndia (talk) 14:30, 16 June 2026 (UTC)[reply]
Wikipedia follows what reliable sources say. If multiple reliable sources say that an airport serves a given city, an individual editor's opinion that it "can't" is (with all due respect) irrelevant. Note that I haven't yet looked at how sources describe DXN's catchment area, and thus have no opinion on the matter. My focus here is improving the general guidelines rather than this specific example. Rosbif73 (talk) 14:42, 16 June 2026 (UTC)[reply]
Sandefjord Airport, Torp is 110km from Oslo, or a couple of hours by train or bus. Distance is not always a barrier to service. CMD (talk) 14:43, 16 June 2026 (UTC)[reply]
Airlines and destinations section, Sandefjord Airport, Torp is referred to simply as "Sandefjord" rather than "Oslo–Sandefjord". UrbanGridIndia (talk) 16:08, 16 June 2026 (UTC)[reply]
That is not relevant to the claim that an airport can't serve a city 80km away from it. CMD (talk) 16:14, 16 June 2026 (UTC)[reply]
Got your point. UrbanGridIndia (talk) 17:04, 16 June 2026 (UTC)[reply]
Doesn't matter if it's 80km away - it still serves Delhi. Frankfurt-Hahn is over 100km from Frankfurt airport, but some still say it serves Frankfurt... well, mostly a yellow and blue Irish airline. The point is, distance isn't really that relevant here. Danners430 tweaks made 17:24, 16 June 2026 (UTC)[reply]
This discussion was intended solely to address the correct naming conventions for Airlines and destinations section and was not about the region or area served by an airport. UrbanGridIndia (talk) 17:37, 16 June 2026 (UTC)[reply]
That is what dictates what an airport is called in the destinations lists - the city (currently) or metropolitan area (agreed but now reverted) served by the airport. Hence Zayed International Airport becomes “Abu Dhabi”, for a very random example picked off my watchlist. Danners430 tweaks made 17:46, 16 June 2026 (UTC)[reply]
I'm curious on this point – if it weren't for Ryanair, would anybody realistically argue that Hahn serves Frankfurt? It feels like a principle that can become malleable to the point of absurdity; after all, Southampton Airport has a direct, frequent, and not-overly-long train service to London (74 miles and 59 chains apparently, or 119 km in new money). XAM2175 (T) 22:51, 18 June 2026 (UTC)[reply]
London Heathrow isn't in London City, neither are the vast majority of airports. Heathrow is four-and-a-quarter times larger than the entire City of London; it's probably reasonable to assume that demolishing the entire city and substantial portions of its surrounding boroughs in order to give it said airport would not have been popular.
Less humorously, Heathrow lies quite clearly within Greater London – an actual administrative division rather than a statistical agglomeration – and I note that the History of Heathrow Airport article holds that it opened as Harmondsworth Aerodrome before its operator settled on the name Great West Aerodrome. The London appellation only seems to have come about when as a matter of government policy Heathrow was deliberately designated London's primary airport over the increasingly-constrained Croydon.
Also, WP:LOCALCON is a thing. XAM2175 (T) 22:36, 18 June 2026 (UTC)[reply]
All of this bickering and nitpicking could be easily avoided by adopting a simple methodology: 1) name aerodrome (which includes airports) articles with the official name, as per AIP; 2) create redirects for all (potential) common names. Why make life more complicated? Jan olieslagers (talk) 16:27, 16 June 2026 (UTC)[reply]
The dispute appears to be about city destination lists, rather than article titles. Perhaps it would be simpler to just say "Destination: John F. Kennedy International Airport", rather than try and figure out some arbitrary distance beyond which airports no longer serve a destination (or perhaps within which they can serve multiple cities). CMD (talk) 17:05, 16 June 2026 (UTC)[reply]
Actually, I do think so. Only I am not sure that JFK is in the AIP with that name ... but I was too lazy to check. It may be argued that the official names of airports may be less clear to the public in general - but then again,we are not creating a travel guide, we are creating and maintaining an encyclopedia. Jan olieslagers (talk) 17:54, 16 June 2026 (UTC)[reply]
Point 6 of Airlines and destinations in WP:AIRPORT-CONTENT clearly states that the actual cities served should be used. NCR is a broader region comprising 25 cities across three states and one union territory, with each city having its own distinct identity. As explicitly mentioned in WP:AIRPORT-CONTENT, it would be better to use the city names instead of "NCR-Delhi" as this is more precise and less likely to create confusion or contradictions. UrbanGridIndia (talk) 17:17, 16 June 2026 (UTC)[reply]
Just pinging @RPC7778 after your recent edit Danners430 tweaks made 17:22, 16 June 2026 (UTC)[reply]
() Since I was pinged: this thread is an exact analogue of the Mumbai/Navi Mumbai debate we had above on this very page. The solution is also the same: there is no actual risk of confusion and disambiguation is unnecessary, DEL is just "Delhi" and DXN is just "Noida".
Once again, I note that everybody on this page who's familiar with the airports in question seems unanimous on this, and it's people who aren't who are proposing silly labels like "Delhi-Gandhi", which nobody in the history of India has used to describe DEL. (If you had to, it would be Delhi-IGI... but you don't.) Asamboi (talk) 21:06, 16 June 2026 (UTC)[reply]
Except that’s not the solution - both airports serve Delhi, just like Mumbai airports serve Mumbai. The agreement above was absolutely sensible in that we call Navi “Navi Mumbai”, which makes sense given the city name… but you still need to disambiguate the other airport, since both serve Mumbai itself. The same applies here - both airports serve Delhi, and as was the case with Mumbai the Wikipedia articles in question literally confirm that. Danners430 tweaks made 21:09, 16 June 2026 (UTC)[reply]
I think you need to stop repeatedly stating that "both airports serve Delhi." Noida Airport and Hindon Airport also serve Uttar Pradesh, yet we are not renaming them to "UP–Noida" or "UP–Hindon," nor are we doing the same for any other airport in Uttar Pradesh
As explicitly stated in WP:AIRPORT-CONTENT, the destination list should use the city name where the airport is located. Unless there are multiple airports serving the same city and disambiguation is necessary, the city name alone should be used. UrbanGridIndia (talk) 02:11, 17 June 2026 (UTC)[reply]
I don’t quite see how you’re missing the point here… the Noida Airport article literally unambiguously states that the airport was designed to complement the other Delhi airport, and serves the city of Delhi. This isn’t me making something up - this is literally what the article states, with sources to back it up. Danners430 tweaks made 06:23, 17 June 2026 (UTC)[reply]
The statement that the airport was designed to complement the other Delhi airport simply means that it was built to help reduce the load on Delhi Airport. Currently, Delhi Airport serves not only passengers from the NCR but also travelers from many parts of North India.
However, this discussion is not about the areas served by the airports. Both airports serve the NCR and surrounding states. The issue here is the naming convention, which, as stated in WP:AIRPORT-CONTENT, should use the city in which the airport is located. UrbanGridIndia (talk) 09:56, 17 June 2026 (UTC)[reply]
Luton Airport is in Luton, not London... yet because it serves London, it's listed as London-Luton. Heathrow is in Hounslow, and is listed as London-Heathrow. Noida is in Noida, and yet should be listed as Delhi, because like the two previous examples it serves a larger city. Danners430 tweaks made 10:06, 17 June 2026 (UTC)[reply]
Noida is not a small suburb or a district within the NCR. It is one of the largest cities in India, with its own distinct identity and significance. UrbanGridIndia (talk) 10:12, 17 June 2026 (UTC)[reply]
We’re also circling back to the argument “those that are familiar with the airports in question…” - this is the English Wikipedia, a worldwide project. With the greatest of respect, it’s not written for people that are “familiar with the airports in question” - it’s written for the regular reader, who may have local knowledge or no knowledge at all. Danners430 tweaks made 21:12, 16 June 2026 (UTC)[reply]
Then it is even more important for readers who have no prior knowledge of the area to clearly understand that Delhi and Noida are different cities. Linking Noida Airport with Delhi could create confusion and mislead readers who are unfamiliar with the region. UrbanGridIndia (talk) 01:59, 17 June 2026 (UTC)[reply]
Look. In my opinion if we are keeping Delhi & Noida as Delhi-Gandhi & Delhi-Noida then we shall rename Newark as New York-Newark as well. We can't be two faced about it. If one changes, the other one has to change as well. However, since this totally doesn't make sense, we shall keep Delhi as Delhi and Noida as Noida, Mumbai as Mumbai and Navi Mumbai as Navi Mumbai. Also @Danners430 do you understand that the literal translation of "Navi Mumbai" is New Mumbai? Navi Mumbai is a totally different city "primarily serving the city of Navi Mumbai" and "reducing congestion" in Mumbai. When you write it as Mumbai-Navi it sounds like Mumbai-New which is totally nonsense, much like York-New.
What you said about LaGuardia or Hahn above cannot be applied here since their equivalent to these two cases would be "Jewar" and "Ulwe", which no one is writing. We write the primary cities, and those are Noida and Navi Mumbai in this case. We can cite multiple sources of this fact. So instead of propping up an issue where there is literally none (thereby also creating confusion), let's keep the city names instead of writing silly names like Delhi-Gandhi, something which literally no one knows or refers to while talking about Delhi International Airport or Mumbai-Navi which is even more laughable to say the least. FlyJet777 (talk) 04:38, 17 June 2026 (UTC)[reply]
No, this is not what we’re doing (not least because there’s no consensus).
If we’re going to change the guidelines for these airports, then we need to change the guidelines across the board. Using names like “Delhi-Gandhi” is literally the agreed-upon method of disambiguation… it’s the style guidelines for the WikiProject. We have multiple airports serving one city, Delhi, so they get disambiguated. For New York, I’ve already stated that I would be all for linking Newark to New York, because again it does serve NYC as its primary market. Danners430 tweaks made 06:22, 17 June 2026 (UTC)[reply]
Where it was agreed to use “Delhi-Gandhi”? UrbanGridIndia (talk) 06:24, 17 June 2026 (UTC)[reply]
When it became necessary to disambiguate because there are multiple airports serving Delhi - see my reply to you above. If the discussion is changing to merely change what it’s called to something other than “Gandhi”, then that’s likely a different discussion to be had at this point. Danners430 tweaks made 06:29, 17 June 2026 (UTC)[reply]
When did it become necessary to disambiguate Delhi Airport? Delhi has only one airport.
The other two airports are located within the NCR. Delhi is part of the NCR; Delhi itself is not the NCR.
As you mentioned above, the addition of metropolitan area in WP:AIRPORT-CONTENT was reverted because there was no consensus for that approach. Therefore, we should continue using city names only. If you believe the current guidance is incorrect, please seek consensus to update the guideline first. Until then, I do not see any benefit in extending this discussion further. Based on the existing guidance, we should be using city names only. UrbanGridIndia (talk) 10:06, 17 June 2026 (UTC)[reply]
Except there was consensus - it wasn't disputed during the previous discussion, and indeed it satisfied the previous discussion. By reverting it, we've reopened that discussion again. The intent of Airport Content, which we can absolutely discuss and find consensus on, is that the airports should be listed as the city served by the airport. If an airport is outwith the city it serves, that shouldn't prevent it being listed as that city. Danners430 tweaks made 10:09, 17 June 2026 (UTC)[reply]
Actually, I do not see that the discussion regarding Mumbai and Navi Mumbai was ever formally closed, it appears to have continued for a long time. I think the introduction of metropolitan area names has only made the issue more complicated and created unnecessary overlap. Using city names is a much simpler and clearer approach, and it avoids these ambiguities. UrbanGridIndia (talk) 10:15, 17 June 2026 (UTC)[reply]
Since I was pinged here, I'm just gonna comment that I was the first one to introduce "Mumbai–Navi/Mumbai–Shivaji" and "Sydney–Western" in A&D tables. So yeah, I'm somewhat partly to blame for this mess. RPC7778 (talk) 12:00, 17 June 2026 (UTC)[reply]
I think we should disambiguate both Delhi and Mumbai. I also think we should be doing "New York–Newark". @Danners430: How about using "Delhi–IG" or "Delhi–IGI" or "Delhi–IGIA" instead of "Delhi–Gandhi"? "Delhi–Gandhi" just sounds plain weird to me. If you don't want abbreviations, then "Delhi–Indira" would still be better. For Mumbai, maybe "Mumbai–CSMI" or the likes instead of "Mumbai–Shivaji"? I would prefer a location based disambiguator, but then we can't use either Santacruz or Sahar, as they cover only one terminal, and Palam is too unknown and likely to cause confusion. I think writing "Navi Mumbai" instead of "Mumbai–Navi" would be just as clear, as it still contains "Mumbai", so I would prefer that, or prefer writing the full "Mumbai–Navi Mumbai", as "Navi" is not an independent word here. We can document it as an exception. Arnav Bhate (talkcontribs) 10:23, 17 June 2026 (UTC)[reply]
WP:AIRPORT-CONTENT states that destination lists should use the actual city served and provides examples such as "Beauvais", not "Paris–Beauvais", and "Rygge", not "Oslo–Rygge".
If you still believe that airports should be grouped under a single metropolitan area, it would be better to start a new discussion, seek consensus, and update the guidance accordingly. Only after that should we revisit the naming issue.
For now, based on the existing guidance, we should be using city names only. UrbanGridIndia (talk) 10:29, 17 June 2026 (UTC)[reply]
My friend, discussion is literally what we’re doing right now. However I am drafting an RfC to rehash the entire issue, as it’s pretty obvious that there’s significant disagreement, so a formal discussion is necessary. At the moment I’m just finding good examples to use that aren’t NYC, Delhi or Mumbai to make the discussion as neutral as possible. Danners430 tweaks made 10:33, 17 June 2026 (UTC)[reply]
That sounds reasonable.
My point is simply that, under the current guidance, destination lists are expected to use city names, with disambiguation only where necessary. Since there is no consensus supporting metropolitan-area naming at present, I believe we should continue following the existing guidance until any new consensus is established through the RfC. UrbanGridIndia (talk) 10:39, 17 June 2026 (UTC)[reply]
But these airports do serve Delhi and Mumbai. Arnav Bhate (talkcontribs) 10:39, 17 June 2026 (UTC)[reply]
and also nearby states and cities. UrbanGridIndia (talk) 10:45, 17 June 2026 (UTC)[reply]
Frankfurt Airport also serves Wiesbaden, Mainz and large swathes of Hessen and parts of Bavaria/Rheinland. But it's listed as Frankfurt because that's the primary city served by the airport. Danners430 tweaks made 10:49, 17 June 2026 (UTC)[reply]
Similarly, the primary city served by Noida Airport is Noida, not Delhi. UrbanGridIndia (talk) 10:56, 17 June 2026 (UTC)[reply]
I've started an RfC at WT:WikiProject Aviation (since this also kind of affects airline lists) to hash this out once and for all. Danners430 tweaks made 10:52, 17 June 2026 (UTC)[reply]

Passenger numbers for "Statistics" section are not consistent

[edit]

Many US airport articles have a section called "Statistics" where the busiest routes and the busiest carriers are listed, with data sourced from the Bureau of Transportation Statistics. These tables are labeled just with "Passengers". However, it seems that the passenger counts are not computed the same way for the two tables (in the source): in the destination lists, it's number of arriving and departing passengers, whereas in the airline lists, I think it's something like just number of departing passengers. This is jarring on pages like Ithaca Tompkins Regional Airport]: there are two airlines, each flying to one destination, so one would think the destination passenger counts and corresponding airline passenger counts would match, but instead one is approximately double the other (e.g. 80,250 for Endeavor Air, which only flies to JFK). Should we consider clarifying the meaning of these "Passenger" counts? CapitalSasha ~ talk 13:38, 19 June 2026 (UTC)[reply]

"Begins" date removal

[edit]

Just for info, I've opened a bot request to automate the removal of "begins" dates from the destination tables, to lessen the maintenance load on editors Danners430 tweaks made 08:31, 23 June 2026 (UTC)[reply]