Wikipedia talk:WikiProject Aviation
Add topicWikiProject:Aviation exists to co-ordinate Wikipedia's aviation content. However, if you are here to ask a question or raise a concern about a particular article, it may be better directed to one of the following sub-projects:
|
watch · edit · discuss | |
|---|---|
| |
|
Did you know
Articles for deletion
Proposed deletions
Categories for discussion
A-Class review
Good article nominees
Good topic candidates
Featured article reviews
Requested moves
Articles to be split
Articles for creation
| |
| View full version (with review alerts) |
| Please place new discussions at the bottom of the talk page. |
| This is the talk page for discussing WikiProject Aviation and anything related to its purposes and tasks. |
|
| Archives: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27Auto-archiving period: 45 days |
| The WikiProject Aviation project was featured in a WikiProject Report written by Rock drum in the Signpost on 9 August 2010. |
| Aviation WikiProject Articles for review |
|
|
WikiProject |
|---|
| General information |
|
Josh Cahill - self/paid editing?
[edit]Can someone take a look at this article? Recent edits by a single-purpose account look like either paid editing or autobiographical editing. I'd be interested to see if anyone else thinks this article smells funny. Thanks. 10mmsocket (talk) 19:35, 1 October 2026 (UTC)
- @Asamboi you have already deleted some of the editor's content. Any insights? 10mmsocket (talk) 19:37, 1 October 2026 (UTC)
- Yeah, this article has a *looooong* and sorry history of COI editing (see Talk:Josh Cahill/Archive 1), and DWContributor (talk · contribs) is totally not suspiciously contributing exclusively to this article. I've given him a COI warning and will prune the fluff yet again once it settles down a bit. Asamboi (talk) 00:41, 2 October 2026 (UTC)
- Thanks for that. I reverted back to your last edit and tagged the article as COI/Paid. Let's see if the editor responds. 10mmsocket (talk) 08:40, 2 October 2026 (UTC)
- Yeah, this article has a *looooong* and sorry history of COI editing (see Talk:Josh Cahill/Archive 1), and DWContributor (talk · contribs) is totally not suspiciously contributing exclusively to this article. I've given him a COI warning and will prune the fluff yet again once it settles down a bit. Asamboi (talk) 00:41, 2 October 2026 (UTC)

The article Air Tahoma has been proposed for deletion because of the following concern:
Tagged as needing more sources for 18 years. No other language has a reliably sourced article from which to translate. Doesn't have significant coverage and is unlikely to get any, since it's defunct.
You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.
Please consider improving the page to address the issues raised. Removing {{proposed deletion/dated}} will stop the proposed deletion process, but other deletion processes exist. In particular, articles for deletion allows discussion to reach consensus for deletion based on established criteria.
If the proposed deletion has already been carried out, you may request undeletion of the article at any time. Bearian (talk) 01:04, 9 October 2026 (UTC)
- I have redirected to List of defunct airlines of the United States (A–C) in lieu of the PROD. @Bearian:, please consider WP:BLARing articles like this like so in the future instead of prodding them. - The Bushranger One ping only 01:24, 9 October 2026 (UTC)
- Oh, sure. Bearian (talk) 01:25, 9 October 2026 (UTC)
Created new article, on Yaniv Hayun
[edit]Created new article, on Yaniv Hayun. The individual civilian who went to the cockpit in a recent airline attempted hijacking, and both removed the assailant who was attacking the captain, and then, with no formal training, pulled up the plane's descent. Thank you, Princessa Unicorn (talk) 15:15, 13 October 2026 (UTC)
IATA codes should be current
[edit]I removed the IATA code from Plymouth City Airport because it wasn't confirmed by IATA. But it was put back by User:Farzeymedic with a historical reference. I think it would be better if IATA codes were always currently active. Otherwise, since IATA codes are reused, we can have multiple articles with the same IATA code, which is confusing. I suggest we update the documentation on Template:Infobox_airport to state that the IATA code must be currently active. We should be consistent, so if we decide not to have current IATA codes, we should add code BUT to both RAF Burtonwood and Bathpalathang. --Ysangkok (talk) 17:52, 13 October 2026 (UTC)
- I see your point of view, I was of the understanding that IATA codes were not reused even after being decommissioned but I am obviously mistaken as you’ve provided a clear example. The reason for me re-adding was for historical reference so it whether this could be displayed in article if able to be suitable cited. Farzeymedic (talk) 18:10, 13 October 2026 (UTC)
- If a code is historic, then mark it as such in the infobox. A footnote as to the current use of the code may be in order. Mjroots (talk) 18:12, 13 October 2026 (UTC)
- I agree with Mjroots. If there are reliable sources convirming that an airport once had an IATA code, then we should include it while marking it as historical. That said, there isn't really a convenient way to do that in the infobox, so maybe we should consider updating Template:Infobox airport to accommodate historical codes. - ZLEA TǀC 21:06, 13 October 2026 (UTC)
- Re ZLEA - IATA = FOO (historic) should be enough. Mjroots (talk) 08:12, 14 October 2026 (UTC)
- Sensible. Agree. 10mmsocket (talk) 08:15, 14 October 2026 (UTC)
- Mmm, myself would prefer old_iata=FOO or historic_iata=FOO or such - we should make sure the given code can never be interpreted as being current. But this would indeed require an update to the template. Jan olieslagers (talk) 19:49, 14 October 2026 (UTC)
- We could just pull it from wikidata:Property:P238 Wikidata. That way, the possible sources of this information are reduced not just in English Wikipedia, but across all Wikipedias... wikidata:Property:P582 is what you'd set on the statement of an old IATA code. Ysangkok (talk) 20:57, 14 October 2026 (UTC)
- No, because (as I read it) P238 points explicitly to a currently valid code - and we are here discussing codes that are no longer valid. And P582 seems to require an exact date/time of termination - which seems difficult to determine. Jan olieslagers (talk) 21:23, 14 October 2026 (UTC)
- All properties can be qualified. That is the point of qualification, that they work across properties. For example, see wikidata:Q145#P6. Why should P6 here be any different from P238? Date/times do not need to be precise. See wikidata:Help:Dates#Qualifiers. You can see that there are validity ranges in the 15th century that only have the granularity of the whole year. Ysangkok (talk) 15:48, 16 October 2026 (UTC)
- No, because (as I read it) P238 points explicitly to a currently valid code - and we are here discussing codes that are no longer valid. And P582 seems to require an exact date/time of termination - which seems difficult to determine. Jan olieslagers (talk) 21:23, 14 October 2026 (UTC)
- We could just pull it from wikidata:Property:P238 Wikidata. That way, the possible sources of this information are reduced not just in English Wikipedia, but across all Wikipedias... wikidata:Property:P582 is what you'd set on the statement of an old IATA code. Ysangkok (talk) 20:57, 14 October 2026 (UTC)
- Re ZLEA - IATA = FOO (historic) should be enough. Mjroots (talk) 08:12, 14 October 2026 (UTC)
- But why not put the historical marker in a qualifier? Then it could be shared across wikis and the infobox could pull it automatically. Ysangkok (talk) 18:16, 14 October 2026 (UTC)
- I agree with Mjroots. If there are reliable sources convirming that an airport once had an IATA code, then we should include it while marking it as historical. That said, there isn't really a convenient way to do that in the infobox, so maybe we should consider updating Template:Infobox airport to accommodate historical codes. - ZLEA TǀC 21:06, 13 October 2026 (UTC)
- If a code is historic, then mark it as such in the infobox. A footnote as to the current use of the code may be in order. Mjroots (talk) 18:12, 13 October 2026 (UTC)
If I may be allowed to offer a broader view: for reasons unknown, IATA once assigned codes to aerodromes that never needed one. For one example, I will mention "OBL" that they assigned to Zoersel (EBZR), a NATO reserve air base that never saw any commercial traffic nor any prospect of such. A couple of years ago they seem to have realised this, and started a correction, withdrawing quite a lot of irrelevant airport codes. Unfortunately, the old codes are still widespread on the www, and time and again people will - with the best of intentions - re-add them inappropriately. Also, may it be noted that the IATA coding with only three alphabetics is woefully inadequate for the many aerodromes with commercial service, so that their clean-up is very understandable. Jan olieslagers (talk) 19:00, 13 October 2026 (UTC)
Tesla Roadster (second generation) 'Flying car'
[edit]Tesla has just performed some sort of publicity stunt supposedly demonstrating 'flying cars': one with fans claimed to hold it upside down by generating 2g of suction, and another with thrusters using compressed air which supposedly enabled it to climb vertically, do a roll over a set of other Tesla vehicles, and land. Elon Musk acknowledged that the vehicles were unmanned, and frankly, the physics of the 'flying' version look all off (it was moving forward level, upside down, with the thrusters pushing the vehicle down at one point). In my opinion, we should wait until sources with the credibility to actually comment on the physics involved etc, before we start suggesting that this hype has anything to do with any vehicle that ever reaches the market. The mass media simply don't have the expertise to comment on the actual feasibility of the thing. Or maybe they do, but print it anyway, just because everyone else does.
Anyway, can people keep a sceptical eye on Tesla Roadster (second generation), Flying car and any other articles where this hype is being pushed, and at least try to keep a semblance of credibility in the articles.
Some media links - no doubt there will be many more in the next day or so. CNN (With a more sceptical headline than most): , Independant: , Wired (also sceptical) , Fox (credulous):
You are invited to join the discussion at talk:No Fly List § Internal no fly lists for unruly passengers. Sdkb talk 22:47, 18 October 2026 (UTC)
Please add additional sources. Thanks in advance. Bearian (talk) 01:26, 20 October 2026 (UTC)
You are invited to join the discussion. Dw31415 (talk) 11:26, 20 October 2026 (UTC)
Requested move at Talk:Iran–Israel conflict § Requested move 20 October 2026
[edit]
An editor has requested that Iran–Israel conflict be moved to Iran–Israel war, which may be of interest to this WikiProject. You are invited to participate in the move discussion. LIrala (talk) 20:32, 20 October 2026 (UTC)
(Notification provided by Move+)
Edit request at Talk:Shane Lundgren
[edit]Hello. There is a pending conflict-of-interest edit request proposing a sourced rewrite of Shane Lundgren, an aviator known for Antonov An-2 flights across Siberia and to the North Pole in the 1990s. I posted it on behalf of the article's subject (unpaid), so I won't edit the article myself. If an editor from this project has time to review it, that would be appreciated. Thank you. Richard Hynek (talk) 18:21, 21 October 2026 (UTC)
2026 In Aviation
[edit]Question about the inclusion of two events and an addition of a new section to the 2026 in aviation article.
There should be a retirements section, due to retirements of many kinds of aircraft this year, however, since it was not appearing in the previous years, I was wondering if it has been phased out or if that it should be added.
Also, there should be two added events, IDK if they are notable enough tho:
~2026-53148-17 (talk) 21:36, 27 October 2026 (UTC)
- @~2026-53148-17: Per WP:BOLD, you could add the retirements if you have reliable sources. Aviation accidents ideally need to have a stand-alone article. Does that apply here? Mjroots (talk) 09:13, 28 October 2026 (UTC)
- Given that there was only ever one Solar Impulse 2 built, given the fact that it was unmanned when it crashed, and given the limited coverage of the crash, I'd have thought that a separate article on the incident was unmerited. AndyTheGrump (talk) 09:59, 28 October 2026 (UTC)
- I'd tend to agree that a separate crash article is unnecessary; the crash is already mentioned briefly in Solar Impulse 2#Skydweller Aero. However I'm not convinced that this, nor the Philippines Air Force collision, are noteworthy enough for the 2026 in aviation page. Rosbif73 (talk) 10:07, 28 October 2026 (UTC)
- okay. ~2026-53148-17 (talk) 21:53, 28 October 2026 (UTC)
- Given that there was only ever one Solar Impulse 2 built, given the fact that it was unmanned when it crashed, and given the limited coverage of the crash, I'd have thought that a separate article on the incident was unmerited. AndyTheGrump (talk) 09:59, 28 October 2026 (UTC)
List of flight information regions and area control centers
[edit]I think List of flight information regions and area control centers should be split or merged with Flight information region and Area control center. Unless those two articles can be expanded, it would make more sense to split/merge the list into them. I think its best to start a discussion here first for those more in touch with the topic to consider, before formally proposing it. My inclination is to split the information between the two parent articles and delete the list, or if somehow it makes sense to keep the list as well, then do that, but the information makes more sense on the parent articles. Please ping in first reply, and Ill monitor after that. ← Metallurgist (talk) 06:11, 28 October 2026 (UTC)
- Do you mean merging all 3? Splitting the table into two separate tables would be detrimental, as the two concepts are linked 1:1. CMD (talk) 06:32, 28 October 2026 (UTC)
- I would also support merging all three if there is enough overlap, which there probably is. ← Metallurgist (talk) 06:48, 29 October 2026 (UTC)
- Oppose both options as it's unclear why we should have an article that explains what flight information regions and area control centers are, while listing them at the same time, and why we should split them into two nearly identical lists. SH360! (Must edit! Must chat!) 04:59, 30 October 2026 (UTC)
- I would also support merging all three if there is enough overlap, which there probably is. ← Metallurgist (talk) 06:48, 29 October 2026 (UTC)
WestJet Fleet
[edit]I tried posting this on the Airlines area but it failed. So I want to confirm that WestJet retired the 737-6CT in 2021, I have two sources to back it up, but someone reverts my edits claiming it's 2023. ~2026-53148-17 (talk) 18:44, 31 October 2026 (UTC)
- Note that 737-6CT in a 737-600 with the CT customer code.
Request for Aviation Museum Article Advice
[edit]I was hoping that some of the contributors here could offer some suggestions or assistance with the situation of two aviation (and/or military) museum articles. I have tried to address them myself, but I recognize that I am only one person and I feel like I am at the point where I feel like my own personal biases could be compromising my objectivity. Therefore, another set of eyes would be beneficial.
The first is the recently renamed North American Aerospace Museum. When the then Evergreen Aviation and Space Museum opened, it included as part of the museum the "Wings and Waves Waterpark". However, following significant financial difficulties, the waterpark became a separate entity. In other words, it is still present and open adjacent to the museum, but it is no longer operated by the museum. Some edits (1, 2) by a connected contributor have removed mention of the waterpark from the article. (Another edit improperly removed a well referenced section about financial difficulties.) However, the waterpark is still relevant to the museum's history and, based on its proximity (approximately 725 feet (221 m) from entry door to entry door), is something that the average reader would expect to see in the article. The role in the museum's history could be covered by a mention in the history section, but I'm not sure how to handle the other half of the issue. Furthermore, finding reliable sources that state the museum no longer owns the waterpark is difficult and, as I noted in an edit summary, they can be contradictory. On the other hand, anything other than the history section generally only describes the current, and not past, status of the museum. To include it there could be give the wrong impression.
The second is the Evansville Wartime Museum. I was emailed by an employee of the museum who had some concerns about the article. Some of the changes they requested were easy corrections or improvements born out of my unfamiliarity with the museum. (As an aside, I want to state for the record that said staff member has been both understanding and helpful. I don't want to leave the impression that they were uncooperative as may sometimes be implied in these cases.) However, others are trickier. The biggest problem is the complicated history of its origins. One group ("heritage commission"), recovered a P-47, began restoring it and shut down. Another group ("foundation") then purchased the project, but it was destroyed in a fire. The foundation organization then purchased an airworthy P-47 and has loaned it to the museum. Critically, the aircraft is "owned and insured" by the foundation – which still exists – and not the museum.[1] (Note that the museum changed its name, apparently as a result of a trademark dispute by a former board member.[2])
The staff member feels there is too much weight put on the previous organizations and that there should be a stronger distinction made between the museum and the organizations. However, it seems to me that although not all groups are directly connected to the museum, they are all integral to its history as it strongly appears that the museum would not exist without them. Therefore, it would be impossible to explain the museum's existence without them and therefore their inclusion in the history section of the article is necessary. (Furthermore, the thread that runs through all of them illustrates Evansville's long-running effort to cover its role during World War II.)
So, there are two parts to this second case: First, to what extent should the previous organization be covered and what is the best means of incorporating the distinction between them and the museum? Second, what is the best means of incorporating the foundation's ownership of the aircraft? Any input would be appreciated. –Noha307 (talk) 00:40, 2 November 2026 (UTC)
- Update: After I made additional edits to the Evansville Wartime Museum article, the staff member was largely satisfied with the result. So consider the second question resolved. The first still stands. –Noha307 (talk) 02:48, 3 November 2026 (UTC)
References
- ↑ Jagielo, Tim (2 April 2024). "Evansville Wartime Museum Closed for Up to One Year Following Storm Damage to Hangar Roof, Door". WNIN. Retrieved 1 November 2026.
- ↑ Overhauser, Paul B. (19 December 2016). "Indiana Trademark Litigation: Founding Member of Museum Registers Trademark Under His Own Name, Sues Museum for Use". Indiana Intellectual Property Law News. Retrieved 1 November 2026.
Essay on aircraft lead images
[edit]For years, we have been using informal selection criteria to choose lead images of aircraft. These have never really been written down in a convenient location that can be referenced in discussions, so I decided to write a user essay (see User:ZLEA/What makes a good aircraft lead image) to objectively explain what the ideal aircraft lead image looks like with examples for most criteria. At 10mmsocket's recommendation, I propose that we make this an official WikiProject Aviation advice page. - ZLEA TǀC 01:00, 2 November 2026 (UTC)
- I'm not sure I'd agree that it is ready to be made 'official'. In my opinion, it risks imposing questionable criteria in contexts where the 'best' image may not fit in with the 'TL;DR' definition given. In particular, it is likely to be problematic for early aircraft, where aerial photography was rare, where in general images of aircraft in flight tended to be of poor quality, and where a good photograph of an aircraft on the ground is likely to give the reader a much better idea of the aircraft's configuration and appearance. The first priority in depicting an object in a lede image should be clarity, rather than any particular image layout. AndyTheGrump (talk) 01:38, 2 November 2026 (UTC)
- Good point. Maybe the preface to all of this then is "Where a selection of available images exists...." 10mmsocket (talk) 12:35, 2 November 2026 (UTC)
- I'd go with 'where a large selection of high-quality images is available'. And even then, we need to emphasise that the purpose of the lede image is to illustrate the aircraft, and that particularly for aircraft of unusual configuration, it is more important to show distinguishing features than to conform to what are essentially stylistic norms. Just picking a random example off the top of my head, consider the Custer Channel Wing. A side-on profile view would be about the least helpful to anyone wanting to understand what makes that configuration special. AndyTheGrump (talk) 14:02, 2 November 2026 (UTC)
- Fully agree 10mmsocket (talk) 15:46, 2 November 2026 (UTC)
- How does this look? By the way, feel free to edit the page directly if you have ideas for improvements. I'm preparing for a cross country move, so I probably won't be as available as I'd have liked to work on it. - ZLEA TǀC 16:58, 2 November 2026 (UTC)
- I don't think that really solves the problem. What constitutes an 'ideal' image depends on the aircraft, as I have noted above. I can fully understand why the recommendations your essay makes would be valid for typical modern airliners, where the basic configuration differs little and readers are already likely to have a good idea of what they are looking at. We can't however make such assumptions more generally, and illustrating an aircraft's unique characteristics has to be more important. Anyway, I'll have a think about it, and see if I can come up with something that addresses this issue. AndyTheGrump (talk) 22:07, 2 November 2026 (UTC)
- How does this look? By the way, feel free to edit the page directly if you have ideas for improvements. I'm preparing for a cross country move, so I probably won't be as available as I'd have liked to work on it. - ZLEA TǀC 16:58, 2 November 2026 (UTC)
- Fully agree 10mmsocket (talk) 15:46, 2 November 2026 (UTC)
- I'd go with 'where a large selection of high-quality images is available'. And even then, we need to emphasise that the purpose of the lede image is to illustrate the aircraft, and that particularly for aircraft of unusual configuration, it is more important to show distinguishing features than to conform to what are essentially stylistic norms. Just picking a random example off the top of my head, consider the Custer Channel Wing. A side-on profile view would be about the least helpful to anyone wanting to understand what makes that configuration special. AndyTheGrump (talk) 14:02, 2 November 2026 (UTC)
- Good point. Maybe the preface to all of this then is "Where a selection of available images exists...." 10mmsocket (talk) 12:35, 2 November 2026 (UTC)
- Overall, it seems pretty darn good. A few, far-from-comprehensive, thoughts:
- My first reaction is that the left facing requirement seems arbitrary. However, I see that it an actual Wikipedia policy. I'm still not completely sold on it, but, to your point, I have seen some original aircraft manufacturer drafting manuals that state profile views should face left.
- Why should images depict a clean configuration? I think I would broadly agree with this, but it is deserving of an explanation. I have a few thoughts, but I don't want to bias your response.
- How much debate goes on over the selection of a lead image for an article? It's not something I've really followed, but I seem to recall in passing some cases where it resulted in an edit war. I ask because the more this happens, the greater the justification for having a policy rather than just a guideline.
- I've come up with very basic criteria for aircraft 3-views in the specifications section, but so far I've really only used them for myself. Plus two or three of theme are just commons sense things for any image. I don't know if we need a policy on this, but since it is related I wanted to mention it. –Noha307 (talk) 06:31, 16 November 2026 (UTC)
- My two euro-cents: I can see no reason why the "lead image" should show a clean configuration aircraft. As a counter-example, take our lead picture for the Tupolev Tu-134, which I think perfectly okay and useful - it clearly shows the aircraft's outline and configuration - the first requirement - but on top of that it shows the landing gear, belly airbrake, and deployed flaps. All of which may be relevant. So I should say that there ought to be a picture of the plane in landing configuration - it needn't be the lead image, but it should be if there are no other pictures. Jan olieslagers (talk) 19:36, 16 November 2026 (UTC)
- Jan olieslagers The reason for preferring a clean configuration is that it's the typical state of the aircraft while in operation. The landing gear, flaps, etc. are typically extended for brief periods during takeoff and landing, and such a configuration is not representative of how the aircraft was intended to perform its primary function of flight. I've updated the page to explain the clean configuration preference.
- Sorry, I don't agree. While it is true that aircraft spend the vast majority of their lifespan airborne, i.e. in "clean configuration", they will rarely be seen like that. Most views will be while on the ground, with at least the landing gear deployed, rudders and flaps depending on the pilots. Jan olieslagers (talk) 19:04, 17 November 2026 (UTC)
How much debate goes on over the selection of a lead image for an article?
Far more than is necessary, in my opinion. This recently-closed one for Lockheed L-1011 TriStar lasted nearly 6 months, and was only started after a slow edit war over the image. - ZLEA TǀC 00:50, 17 November 2026 (UTC)- On this point, I fully concur :) ! Jan olieslagers (talk) 19:04, 17 November 2026 (UTC)
- Jan olieslagers The reason for preferring a clean configuration is that it's the typical state of the aircraft while in operation. The landing gear, flaps, etc. are typically extended for brief periods during takeoff and landing, and such a configuration is not representative of how the aircraft was intended to perform its primary function of flight. I've updated the page to explain the clean configuration preference.
Aircrash language and dates
[edit]Does an aviation incident article adopt the language and date settings of the airline's home country, or the country in which the incident occurred? Two examples:
- Pan Am Flight 103 - US airline, UK crash, using UK settings
- Redcoat Air Cargo Flight 103 - UK airline, US crash, using UK settings (because I set them that way for this newly-created article according to my interpretation of MOS:TIES)
I think it would be useful to have some clarity and thus consistency. Obviously there's no need to change existing articles (MOS:RETAIN) but it could help new articles. 10mmsocket (talk) 12:33, 2 November 2026 (UTC)
- Initial choice of language is down to the creator. Although I normally use British English, I do use American English where there is a strong tie to the United States. Changing language should be discussed, not done arbitrarily. Mjroots (talk) 09:59, 3 November 2026 (UTC)
Requested move at Talk:2026 Palm Beach County Learjet 60 crash § Requested move 3 November 2026
[edit]
An editor has requested that 2026 Palm Beach County Learjet 60 crash be moved to 2026 Florida Learjet 60 crash, which may be of interest to this WikiProject. You are invited to participate in the move discussion. Raskuly 🐰 05:10, 6 November 2026 (UTC)
(Notification provided by Move+)
Discussion at Talk:Boeing 787 Dreamliner § Infobox image
[edit]
You are invited to join the discussion at Talk:Boeing 787 Dreamliner § Infobox image, which is within the scope of this WikiProject. S5A-0043🚎(Talk) 04:54, 7 November 2026 (UTC)
One of your project's articles has been nominated for the Main Page
[edit]Hello. Please note that Air sports, which is within this project's scope, has been nominated to be featured on the Main Page for seven days as This Week's Article for Improvement. You are welcome to participate in the discussion at Wikipedia:AFI/Nominations § Air sports and help us decide whether it meets our criteria. If the nomination is successful, the article will be added to the holding area and wait to be scheduled to appear on Wikipedia's Main Page for a period of seven days. For the Articles for improvement project, |
There is a proposal to delete this article / merge with the fire Dw31415 (talk) 01:31, 9 November 2026 (UTC)

