Wikipedia:WikiProject Deletion sorting/Aviation

WP:DELAV

This is a collection of discussions on the deletion of articles related to Aviation. It is one of many deletion lists coordinated by WikiProject Deletion sorting. Anyone can help maintain the list on this page.

Adding a new AfD discussion

Adding an AfD to this page does not add it to the main page at WP:AFD. Similarly, removing an AfD from this page does not remove it from the main page at WP:AFD. If you want to nominate an article for deletion, go through the process on that page before adding it to this page. To add a discussion to this page, follow these steps:

Edit this page and add {{Wikipedia:Articles for deletion/PageName}} to the top of the list. Replace "PageName" with the relevant article name, i.e. the one on the existing AFD discussion. Also, indicate the title of the article in the edit summary as it is particularly helpful to add a link to the article in the edit summary. When you save the page, the discussion will automatically appear.
You should also tag the AfD by adding {{subst:delsort|Aviation|~~~~}} to it, which will inform editors that it has been listed here. You may place this tag above or below the nomination statement or at the end of the discussion thread.

Note that there are a few scripts and tools that can make this easier.

Removing a closed AfD discussion

Closed AfD discussions are automatically removed by a bot.

Other types of discussions

You can also add and remove links to other discussions (prod, CfD, TfD etc.) related to Aviation.

Further information

For further information see Wikipedia's deletion policy and WP:AfD for general information about Articles for Deletion, including a list of article deletions sorted by day of nomination.

Archived discussions (starting from September 2007) may be found at:

WikiProject Deletion sorting/Aviation/archive

Purge page cache

watch

Aviation Articles for Deletion (WP:AFD)[edit]

2024 Colombia Mil Mi-17 crash[edit]

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

Per WP:NOTNEWS. The majority of news sources are primary. There is a failure of WP:CONTINUEDCOVERAGE with coverage ending three weeks ago and WP:SUSTAINED. Aviationwikiflight (talk) 13:14, 20 May 2024 (UTC)[reply]

Note: This discussion has been included in the deletion sorting lists for the following topics: Aviation, Events, and Colombia. Aviationwikiflight (talk) 13:26, 20 May 2024 (UTC)[reply]

• Keep a crash with 9 fatalities is not an everyday occurence, it succeeds WP:NOTNEWS due to the number of fatalities and is the second most fatal helicopter crash this year second to the Lumut Mid-air collision this year, it is the single most fatal crash this year also. Lolzer3000 (talk) 14:42, 20 May 2024 (UTC)[reply]

Just because something is not an everyday occurence doesn't mean it has to be included. If we were to do this, we would have hundreds of articles on accidents that are likely not notable enough to be included in wikipedia other than the number of deaths.

Events that are only covered in sources published during or immediately after an event, without further analysis or discussion, are likely not suitable for an encyclopedia article. All news coverage ended three weeks ago. Even searching the term brings up different helicopter accidents not related to this event.

All news sources whether cited or not are all primary sources without much analysis of the event and are all short in length. The event doesn't have much significant coverage with no secondary sources.

If a helicopter with three people on board crashed and it were the second deadliest (or first) helicopter accident of the year, would an article on that accident need to be created? Aviationwikiflight (talk) 15:42, 20 May 2024 (UTC)[reply]

Per WP:NOTNEWS this should be deleted. Frankly 2024 Lumut mid-air collision probably should be deleted as well. Allan Nonymous (talk) 20:08, 20 May 2024 (UTC)[reply]

The 2024 Lumut mid-air collision had significant coverage as i've listed below :

[1]

[2]

[3]

3 Mainstream sources from seperate parts around the world covered it, however thats for a different discussion, here we have :

[4]

[5]

only 2 here but still enough to cover this and pass Notability guidelines here combined with the sources cited in the article. Lolzer3000 (talk) 15:10, 22 May 2024 (UTC)[reply]

The first source is just a bing search that brings up absolutely nothing related to this accident. The only news shown are from the 2024 Varzaqan helicopter crash.

The second source given is a primary source that adds nothing new to the accident. As stated before, the article must have clearly sustained continued coverage which the event fails. As tragic as the accident was, the event clearly does not have significant coverage and lacks secondary sources. Aviationwikiflight (talk) 16:58, 22 May 2024 (UTC)[reply]

Sorry about the first one, was in a rush to pack up for class didnt see i linked a random bing search this is what i was trying to link : [6] my apoligies! Lolzer3000 (talk) 17:52, 22 May 2024 (UTC)[reply]

Hamid Reza Seyedi[edit]

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

BLP fails WP:GNG and all relevant biography guidelines. The basic problem is a lack of WP:SIGCOV in any sources. Quick review of existing sources: 1, 3/8, and 4 are WP:ROUTINE/WP:TRIVIAL coverage, not significant mentions. Source 2 has no reference to the subject. 5, 9 and 10 are primary source bios. 6 and 7 are trivial mentions in lists of speakers. 11-15 are references to the subject's own writing and thus ineligible for notability. A WP:BEFORE search turns up no additional sources to point to notability. Dclemens1971 (talk) 00:39, 20 May 2024 (UTC)[reply]

Note: This discussion has been included in the deletion sorting lists for the following topics: People, Aviation, Transportation, and Iran. WCQuidditch ☎ ✎ 01:13, 20 May 2024 (UTC)[reply]

Kion de Mexico[edit]

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

The seventeen years that the article on this company has existed as an unsourced stub exceeds the fifteen years for which the company itself actually existed. I would suggest merging somewhere, but only if sources could be found to support content to be merged. BD2412 T 14:29, 19 May 2024 (UTC)[reply]

Note: This discussion has been included in the deletion sorting lists for the following topics: Companies and Mexico. BD2412 T 14:29, 19 May 2024 (UTC)[reply]
Note: This discussion has been included in the list of Aviation-related deletion discussions. Spiderone^{(Talk to Spider)} 15:54, 19 May 2024 (UTC)[reply]
Delete - Fails WP:NCORP. I don't even find the sources that would allow a merge. Maybe a redirect to the parent company but I do not find a source to verify that. --CNMall41 (talk) 21:29, 20 May 2024 (UTC)[reply]

Mont-Tremblant/Lac Ouimet Water Aerodrome[edit]

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

Fails WP:NBUILDING and WP:GNG. Long defunct airport, Only "reference" stated is the Nav Canada Wikipedia article, which make no mention of this airport, and is improper as Wikipedia is not a reliable source.

Note: this is TC LID CST9, NOT Mont-Tremblant/Saint-Jovite Airport (TC LID: CSZ3), so if you are determining if there are any WP:RS to find, they are different airports. Zinnober9 (talk) 02:15, 19 May 2024 (UTC)[reply]

Note: This discussion has been included in the deletion sorting lists for the following topics: Travel and tourism, Transportation, and Canada. Zinnober9 (talk) 02:15, 19 May 2024 (UTC)[reply]
Keep. The 15 March 2007 Canada Flight Supplement mentioned in the article is a valid reference. Eastmain (talk • contribs) 05:45, 19 May 2024 (UTC)[reply]
Note: This discussion has been included in the list of Aviation-related deletion discussions. WCQuidditch ☎ ✎ 06:14, 19 May 2024 (UTC)[reply]
Comment - The nominator is mistaken about the source. The information is not sourced from, or claimed to be sourced from the Nav Canada Wikipedia article, but rather the Canada Water Aerodrome Supplement. The link to the Wikipedia article is for clarity as the CWAS does not appear to be available online other than for purchase from Nav Canada. - ZLEA _T\^C 07:06, 19 May 2024 (UTC)[reply]
Redirect. This is a 2005 article created when Wikipedia was much smaller, articles like this were welcomed, and notability was perhaps a bit looser. However, there was never any ideas as to the fate of abandoned aerodrome articles. Some have been redirected to "List of airports in province", others to List of defunct airports in Canada, and others still remain. The only thing this aerodrome has going for it in terms of notability is that there was a death associated with it. Doesn't really make it notable. As per the others the source is the printed, water, version of the Canada Flight Supplement. I owned copies but haven't bought one in a few years. CambridgeBayWeather (solidly non-human), Uqaqtuq (talk), Huliva 15:16, 20 May 2024 (UTC)[reply]

United Airlines Flight 1175[edit]

AfDs for this article:

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

Fails WP:EVENT and WP:LASTING.

I note the previous AfDs and the contentious debate surrounding this article. It was previously deleted at an AfD in 2018, then restored by a deletion review in 2021. It survived a second AfD on the basis of continuing coverage and publication of new information which (allegedly) demonstrated the significance and lasting impact of this incident. This new information was almost entirely related to:

The release of the NTSB report in late 2020; and
Engine failures on United Airlines Flight 328 and Japan Airlines 904, involving the same type of aircraft and engine.

Any time that an incident resulted in a news spike, it is likely that the release of the accident report may receive at least some coverage in secondary sources, but more often than not, this just means that the official investigation has concluded. Notability would be inherited from the content of that report, rather than its existence. In this case, it appears the report recommended changing routine inspection intervals for operators of PW4000 engines. This is a fairly predictable outcome that impacts a specific group of operators - more notable would be an unexpected finding that leads to sweeping changes to regulations across the industry as a whole, but even then it would be more appropriate to cover this in Pratt & Whitney PW4000 article. The article itself quotes the NTSB as saying they had not confirmed a link to the other incidents mentioned above that generated the media spike. Of the references cited that have been published from 2020 onwards, there is little to indicate significant WP:LASTING coverage of this incident. Most either provide trivial mentions of United 1175 while discussing other incidents, are WP:SENSATIONAL, or do not demonstrate WP:PERSISTENCE in the form of detailed case studies, rather they are rehashing what was already reported on in 2018. Other additions to the article in a bid to demonstrate notability have been irrelevant or unencyclopedic - including several paragraphs detailing the history Boeing 777 fatal accidents and hull-losses, an individual's filing of a lawsuit for emotional distress or timelines of the crew performing routine procedures such as initiating fuel crossfeeds and lowering the landing gear. I just removed a sentance and reference from 2018 that said United were planning to offer passengers on flight 1175 refunds! Dfadden (talk) 05:12, 18 May 2024 (UTC)[reply]

Note: This discussion has been included in the list of Aviation-related deletion discussions. Dfadden (talk) 05:12, 18 May 2024 (UTC)[reply]
Note: This discussion has been included in the deletion sorting lists for the following topics: Events, California, and Hawaii. WCQuidditch ☎ ✎ 06:06, 18 May 2024 (UTC)[reply]

Keep. The event meets Wikipedia:Notability (events)#Duration of coverage in that it has received significant coverage in 2019, 2020, 2021, 2022 even years after it took place on 13 February 2018.
The event has become notable since it resulted in a new mandate by the Federal Aviation Administration (WP:LASTING) and it has continued to receive sustained coverage years after the event (WP:CONTINUEDCOVERAGE), even if some of those sources are prompted by another event happening or by regional or local sources that have some connection with the event. If the event were non-notable, it would not continue to receive significant coverage years later.
Sources published from one month to four years after the event (ordered chronologically) that provide significant coverage about United Airlines Flight 1175:
1. "NTSB's initial probe finds likely cause of engine blowout on United flight to Hawaii". Honolulu Star-Advertiser. 2018-03-07. Archived from the original on 2021-02-28. Retrieved 2021-02-28.
2. Morales, Manolo (2019-08-23). "United pilot recalls averting airline disaster". KHON-TV. Archived from the original on 2021-02-28. Retrieved 2021-02-28.
3. O'Connor, John (2020-06-06). "United, others sued for 2018 in-flight incident". Guam Daily Post. Archived from the original on 2021-02-28. Retrieved 2021-02-28.
4. "NTSB releases final report on cause of engine blowout on United flight to Hawaii". KHON-TV. 2020-06-30. Archived from the original on 2021-02-28. Retrieved 2021-02-28.
5. Vasile, Zachary F. (2020-07-03). "NTSB: Pratt inspection missed cracked fan blade". Journal Inquirer. Archived from the original on 2021-02-28. Retrieved 2021-02-28.
6. Andrew, Scottie (2021-02-22). "Another United Airlines flight experienced a right engine failure in 2018". CNN. Archived from the original on 2021-02-28. Retrieved 2021-02-28.
7. Mayer, Erick Haw (2021-02-27). "En 2018 otro Boeing 777 de United Airlines sufrió una falla de motor" [In 2018 another United Airlines Boeing 777 suffered an engine failure]. Transponder 1200 (in Spanish). Archived from the original on 2021-02-28. Retrieved 2021-02-28.
  From a Google Translate of https://www.facebook.com/notes/1674174042602267/: "Founded on April 26, 2011, Transponder 1200 is a journalistic medium specialized in aviation that, for more than eight years, has positioned ourselves as a benchmark in the global aeronautical industry. With correspondents in Brazil, Colombia, Argentina, Ecuador, France, Germany and Mexico, we are a medium in constant growth, innovative and improving our publishing house, always managing to be in the taste of our readers, partners and clients. We are affiliated to the Federation of Associations of Mexican Journalists A.C., by APECOMOR."
8. Tangel, Andrew; Sider, Alison (2021-03-19). "United's Recent Engine Failure Spooked Denver. It's Happened Before". The Wall Street Journal. Archived from the original on 2021-03-19. Retrieved 2024-05-19.
9. Parvaneh, Fred (2022-04-15). "Captain Behnam, Pilot Who Prevented 2018 Plane Crash, Tells All". Kayhan Life. Archived from the original on 2024-05-19. Retrieved 2024-05-19.
Additional sources that provide fewer words of coverage:
1. Tangel, Andrew; Sider, Alison (2021-02-25). "Boeing Moved to Replace 777 Engine Covers Before Recent Failures". The Wall Street Journal. Archived from the original on 2021-02-25. Retrieved 2021-02-28.
  The article notes, "After the 2018 failure on the United 777, the FAA mandated that fan blades on the type of engine involved undergo special thermal-acoustic image inspections—using sound waves to detect signs of cracks—every 6,500 flights."
2. Siemaszko, Corky (2021-02-22). "Plane engine that caught fire on United Airlines flight over Denver has troubled history". NBC News. Archived from the original on 2021-02-28. Retrieved 2021-02-28.
  The article notes, "But an NTSB investigation of the Feb. 13, 2018, malfunction of a Pratt & Whitney engine on the Honolulu-bound United flight faulted the company for not doing more stringent inspections."
3. Levin, Alan (2021-02-21). "Engine Failure Spurs Boeing 777 Groundings in U.S. and Japan". Bloomberg News. Archived from the original on 2021-02-28. Retrieved 2021-02-28.
There is sufficient coverage in reliable sources to allow the subject to pass Wikipedia:Notability#General notability guideline, which requires "significant coverage in reliable sources that are independent of the subject".
Cunard (talk) 09:51, 19 May 2024 (UTC)[reply]

Thankyou Cunard for pinging participants from the previous nomination - I did leave messages for the previous nominator and article creator on their respective talk pages as well.

WP:CONTINUEDCOVERAGE is only one factor in determining notability per WP:EVENT. The context of the lasting coverage needs to be taken into consideration against all applicable policies and guidelines. It's less about how long the media coverage lasts for and much more about whether that coverage actually establishes the lasting significance of a particular event. Just because reliable sources exist and continue to be published, doesn't mean the subject merits a stand-alone wikipedia article.

There are clear guidelines on what constitutes WP:PRIMARY and WP:SECONDARY sources in the policy on original research which explicitly states: "Do not base an entire article on primary sources, and be cautious about basing large passages on them." Wikipedia is not a collection of news reports.

Considering this, the sources provided above are mostly primary, and while they may be reliable and independent, most provide little evidence of notability for this incident. They do not meet the threshold to pass WP:LASTING or WP:EVENT because:

1. Is reliable and factual, but is a primary source per WP:PRIMARYNEWS that does not provide any analysis on the incident - it just reports what was in the NTSB's preliminary report, which is an example of WP:ROUTINE.

2. Per WP:PRIMARYNEWS, this article consists of an interview with the pilot recounting the incident and should be considered a primary, not a secondary source. Primary sources rarely establish notability.

3. An individual passenger filing a lawsuit as a result of distress/minor injury an in-flight incident is not inherently notable and is a WP:ROUTINE occurrence. If this lawsuit were a successful class action that determined the airline/manufacturer was grossly negligent, an argument could be made that the lawsuit established notability. As it is, the article is an example of sensationalism, which WP:EVENT states is a poor basis for encyclopedic merit.

4. Is a primary source per WP:PRIMARYNEWS. There is also no new significant information included in this source. It that just states the final report is due to be released later that week and restates the summary of the preliminary report which is referenced elsewhere - again fails WP:ROUTINE

5. Another routine primary source that reports on the findings of the NTSB final report without conducting any analysis

6. Probably the closest yet to an actual secondary source, as it does discuss the events retrospectively in the context of some analysis, but does not draw any conclusive links between the incidents, just points out that there were similarities. To draw any conclusions that the modes of failure were actually related based on this article would not meet WP:NOR. Thus it does not demonstrate the significance of United 1175 that is required to meet WP:EVENT and WP:LASTING

7. This is a primary source per WP:PRIMARYNEWS. As I am relying on Google translate to read the text, it is difficult for me to critique. However based on the translation appears to be about the 2021 Denver incident with a mention of United Flight 1175 being only recounting the basic facts of the incident and that authorities will investigate determine if the incidents are linked which might indicate a broader issue with PW4000 engines.

8. I do consider this Wall Street Journal a good secondary source. While it does analyse United Flight 1175 in some level of detail, this is in the context of a broader series of uncontained fan blade failures of Pratt and Whitney and CFM International engines. It is likely this article would demonstrate each of the incidents discussed are notable enough to be mentioned in the articles for the respective engine models. However, notability is not inherited. Eg. The idea that that this particular incident qualifies for a stand-alone article merely because it was associated with some other, legitimately notable subject (ongoing issues with the engines themselves) is not actually proof of its notability!

9. Like 2, is an interview with the pilot recounting the incident and should be considered a primary, not a secondary source. Despite being published four years after the accident, it also provides no new facts or analysis that would demonstrate lasting significance.

The three other sources that provide less depth also do provide some level of analysis (although 3. is relatively trivial). However once again, that analysis focusses on a series of separate incidents involving failures of PW4000 engines. As above, I would argue that the actually notable subject being analysed here is the mode of failure of the engine, thus it should be discussed in the article on the engine, rather than a standalone article on this incident.

If we are able to cut the article back to just the information supported by sources 7, 8 and the 3 additional brief mentions, I'd support a merge of this content into the Pratt and Whitney PW4000 article, or a redirect to the same target. Dfadden (talk) 12:20, 19 May 2024 (UTC)[reply]

I consider all of these sources to contribute to the event meeting Wikipedia:Notability (events). You wrote of source 6 "Probably the closest yet to an actual secondary source, as it does discuss the events retrospectively in the context of some analysis, but does not draw any conclusive links between the incidents" and of source 8 "I do consider this Wall Street Journal a good secondary source. While it does analyse United Flight 1175 in some level of detail, this is in the context of a broader series". Even if all the other sources are disregarded (something I would disagree with), these two sources by themselves are sufficient for United Airlines Flight 1175 to meet Wikipedia:Notability (events). Regarding the WP:NOTINHERITED assertion about source 8, the essay is about Wikipedia editors claiming a subject has inherited notability when that subject has not been covered by reliable sources. This is not the case here since the subject has been amply covered by reliable sources. Wikipedia:Notability#General notability guideline says, "Significant coverage is more than a trivial mention, but it does not need to be the main topic of the source material." Cunard (talk) 09:07, 22 May 2024 (UTC)[reply]

Comment: Pinging Wikipedia:Articles for deletion/United Airlines Flight 1175 (2nd nomination) participants: SportingFlyer (talk · contribs), Pontificalibus (talk · contribs), Dhaluza (talk · contribs), StonyBrook (talk · contribs), SunDawn (talk · contribs), Sandstein (talk · contribs), Ambrosiawater (talk · contribs), Oakshade (talk · contribs), Scope creep (talk · contribs), SmokeyJoe (talk · contribs), Tigerdude9 (talk · contribs), and Vaticidalprophet (talk · contribs). Cunard (talk) 09:51, 19 May 2024 (UTC)[reply]
Keep: I was pinged by Cunard. The article has reliable sources to meaningful content, dating three years after the event. WP:EVENT and WP:LASTING are passed by ongoing coverage of three years. Ongoing coverage cannot be expected to mean endlessly never ending coverage. SmokeyJoe (talk) 10:05, 19 May 2024 (UTC)[reply]
No objection to User:Dfadden‘s merge ideas, if properly done, per WP:Editing policy, but mergers, especially complex mergers, should not be done through AfD. SmokeyJoe (talk) 06:31, 20 May 2024 (UTC)[reply]
Delete this is a bit of an WP:IAR delete because of the sources, but this was basically a completely run-of-the-mill aviation event which just happened to be well covered. I expect this to be kept given our sourcing rules, but we generally do not keep articles on flight disasters where no one was hurt and nothing important happened as a result unless they were extremely unusual or well covered (the BA flight flying into ash near Indonesia, for instance). Just because we can source an article does not mean we have to have an article on the topic. I do expect this to be kept, and I almost sat this one out as a result, but common sense dictates this really wasn't that important of an aviation event. SportingFlyer T·C 17:42, 19 May 2024 (UTC)[reply]
“ run-of-the-mill aviation event which just happened to be well covered” is a self contradiction, if you accept that Wikipedia covers things that others cover, in reliable sources, where “covers” implies secondary source content, not mere repetition. Run-of-the-mill is like churnalism which is characterised by repetition. The three years ongoing sources are not churnalism. This is no standout article, but it is good enough, and could be a good example of the comprehensiveness of Wikipedia. SmokeyJoe (talk) 06:29, 20 May 2024 (UTC)[reply]
The link you have provided to secondary source is a general article. Wikipedia has a policy on how WP:SECONDARY sources are interpreted and used to establish notability. The majority of news reports about contemporary events are actually considered primary sources unless they contain detailed analysis or are written retrospectively and look at the impacts of an event over time. This is covered in the policy WP:PRIMARYNEWS. By the standard of these policies (and arguments in AfDs should be supported by actual policy), it is nowhere near as clear cut simple as saying its covered in reliable news outlets, therefore it meets GNG. Things like interviews with the pilot are most definitely NOT secondary sources in this context. Also, you have misrepresented what churnalism means in regards to WP:MILL - the first line of that policy states "Something that is run-of-the-mill is a common, everyday, ordinary item that does not stand out from the rest." Churnalism on the other hand is "a pejorative term for a form of journalism in which instead of original reported news, pre-packaged material such as press releases or stories provided by news agencies are used to create articles in newspapers and other news media." Eg. repetition of press releases or mirrors of the same work under different mastheads. These are NOT the same thing. Not even close. Churnalism is not even mentioned in the policy WP:MILL (although it is mentioned in WP:RS). Dfadden (talk) 07:47, 20 May 2024 (UTC)[reply]
You’re not telling me anything I don’t know. The article won’t be deleted because it meets the Wikipedia-notability threshold. You need to decide whether you want to argue for deletion, or for a merger, because they are not compatible. SmokeyJoe (talk) 08:44, 20 May 2024 (UTC)[reply]
Just because sources cover an event or a topic does not mean we need to have an article on the topic. The Aviation Herald lists this as an incident as opposed to an accident or crash, which are generally notable, and the lasting coverage is basically just a mention that it happened. There's also bias involved here - because two of these incidents occurred on American planes, there's more coverage available to Wikipedia than for the exact same Japanese incident, which does not have an article. As I said, I do expect this to be kept because people will see coverage and stop there, but this event really does not fit the mold of the types of aviation accidents which we are likely to have articles on, and as such I am making a common sense delete vote. SportingFlyer T·C 19:59, 22 May 2024 (UTC)[reply]
It has enough sources, over enough time, to pass the GNG. Passing the GNG does not mean it needs its own article, agreed. It could be merged somewhere, as Dfadden suggests. Merging is not achieved by deleting at AfD. AfD is the wrong venue for merging, especially complicated merges. SmokeyJoe (talk) 22:32, 22 May 2024 (UTC)[reply]
I have no problem with a merge, and AfDs can result in the merge of a page as you well know. SportingFlyer T·C 04:38, 23 May 2024 (UTC)[reply]
Keep per the argument and WP:LASTING coverage provided by Cunard. If it doesn't have lasting impact, why would CNN give the incident in-depth coverage over three years later?[7] and why would the FAA mandate new inspection processes based on the incident? Oakshade (talk) 22:39, 20 May 2024 (UTC)[reply]
There is nothing particularly notable about the FAA issuing an airworthiness directive to require changes to inspection intervals as a result of a mechanical failure! That's just an example of an organisation that is responsible for risk mitigation doing its job to provide additional layers of safety. Cracks were missed at the previous routine inspection - so a simple way of addressing that is to require engineers to look more often. Revision of inspection intervals happens nearly every time there is an unexpected mechanical failure of an aircraft component that is otherwise maintained in line with the manufacturers guidance. If this had been an Emergency Airworthiness Directive, then yeah, it would be notable like Qantas Flight 72, another non-fatal incident. Dfadden (talk) 21:54, 22 May 2024 (UTC)[reply]
Comment Unfortunately, the media loves to hype up and place undue weight on negative news, and aviation incidents are a common target. News spikes surrounding negative aviation stories have been increasing over the last few decades and are to be expected even for the most mundane of incidents. By triggering negative emotional responses, this can distort our perceptions of how significant an incident really is - as was demonstrated by van der Meer et al. (2019) [8] Dfadden (talk) 22:04, 22 May 2024 (UTC)[reply]
Keep. I am pinged by Cunard as well. The action of FAA to release an airworthiness directive changing how the engine is inspected made the incident to be quite notable. The incident also grounded aircraft on multiple countries, showing that it's not just "another" accident but an accident that is treated more seriously. The article also mentioned that Boeing changed the design of the engine by strengthening its covers, another proof that this is not just "another accident". A routine accident won't spark an international grounding of aircraft and a redesign of the aircraft. ✠ SunDawn ✠ (contact) 12:01, 23 May 2024 (UTC)[reply]

No. 674 Squadron AAC[edit]

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

Insufficient independent references to prove notability. PercyPigUK (talk) 15:49, 16 May 2024 (UTC)[reply]

Note: This discussion has been included in the deletion sorting lists for the following topics: Military, Aviation, and United Kingdom. PercyPigUK (talk) 15:49, 16 May 2024 (UTC)[reply]
Weak keep or merge as it appears to be notable but heavily relies on a single sourcing from RAF. So It could have been a strong keep only if there were more sources for this article. Although merging in Royal Air Force is always an option. Based Kashmiri ^TALK 10:10, 19 May 2024 (UTC)[reply]
Merge to RAF Barkston Heath. The squadron has only existed there, so its history forms part of the history of the station. Buckshot06 (talk) 08:06, 21 May 2024 (UTC)[reply]

2005 Kavatshi Airlines Antonov An-26B crash[edit]

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

Accident doesn't demonstrate needed notability for an article. Fails the general notability guideline, the event criteria, WP:CONTINUEDCOVERAGE and doesn't demonstrate any lasting effects. Whilst the event does have coverage (minimal), the majority of them are in french with all of them being short stories. I haven't been able to find any coverage post-2005 involving this accident. Aviationwikiflight (talk) 12:47, 16 May 2024 (UTC)[reply]

Note: This discussion has been included in the deletion sorting lists for the following topics: Events, Aviation, and Democratic Republic of the Congo. Aviationwikiflight (talk) 15:03, 16 May 2024 (UTC)[reply]

•Keep Yet again another Antonov accident that doesnt fail WP:NOTNEWS, an accident with 11 fatalities is not an everyday occurance. Lolzer3000 (talk) 14:19, 17 May 2024 (UTC)[reply]

Just because an event doesn't fail WP:NOTNEWS doesn't mean it automatically gets a keep. No lasting effects were demonstrated from the accident. It has been 18 years since the accident and the accident has not demonstrated any (long-term) impacts. The event does not have significant nor reliable coverage.

Per WP:EVENTCRIT:

_{Events are probably notable if they have enduring historical significance and meet the general notability guideline, or if they have a significant lasting effect.} Event does not fulfill this criteria.
_{Events are also very likely to be notable if they have widespread (national or international) impact and were very widely covered in diverse sources, especially if also re-analyzed afterwards (as described below).} No widespread impact or coverage in diverse sources with no analysis of the accident.
_{Events having lesser coverage or more limited scope may or may not be notable; the descriptions below provide guidance to assess the event.} Event has limited coverage.
_{Routine kinds of news events (including most crimes, accidents, deaths, celebrity or political news, "shock" news, stories lacking lasting value such as "water cooler stories," and viral phenomena) – whether or not tragic or widely reported at the time – are usually not notable unless something further gives them additional enduring significance.} Nothing inherently notable about this accident even if tragic.

Post-2005, I haven't been able to find any coverage regarding this accident thus failing WP:CONTINUEDCOVERAGE. Aviationwikiflight (talk) 15:07, 17 May 2024 (UTC)[reply]

an accident like this is indefinetly going to fail the 10-year test that many deletion authors go by, no accident has continued coverage over 19 years. Lolzer3000 (talk) 21:01, 21 May 2024 (UTC)[reply]

For sure no accident will have continued coverage for over 19 years but an accident should at least be mentioned/ talked about for at least a year especially for an accident with that many fatalities. All news sources are primary sources which means it is impossible to source reliable secondary sources. All news sources only state the circumstances of the accident without any analysis of the accident failing WP:INDEPTH.

The event fails the general notability guidelines as it has no significant coverage and no reliable secondary sources. Aviationwikiflight (talk) 12:12, 22 May 2024 (UTC)[reply]

Agreeable here, i can only find a singular source covering it 6 days later, linked below, there is an in depth summary in 2005 in aviation so the general deletion of the article itself wouldnt be a problem because the information is still pertained in the summary.

[9] (the mentioned link) Lolzer3000 (talk) 16:45, 22 May 2024 (UTC)[reply]

The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.

The result was soft delete‎. Based on minimal participation, this uncontroversial nomination is treated as an expired PROD (a.k.a. "soft deletion"). Editors can request the article's undeletion. ✗plicit 14:38, 23 May 2024 (UTC)[reply]

Cinebulle[edit]

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

I wasn't able to find significant coverage in independent reliable sources. toweli (talk) 10:58, 16 May 2024 (UTC)[reply]

Note: This discussion has been included in the deletion sorting lists for the following topics: Technology and Aviation. toweli (talk) 10:58, 16 May 2024 (UTC)[reply]
Delete me neither. no sigcov. --BoraVoro (talk) 14:52, 16 May 2024 (UTC)[reply]

The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.

P80 Air[edit]

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

Promo sock creation for an airline that might begin operations late 2024. Fails GNG and NCORP, sources in article and found in BEFORE do not have WP:SIRS addressing the subject directly and indepth. // Timothy :: talk 22:21, 11 May 2024 (UTC)[reply]

Note: This discussion has been included in the deletion sorting lists for the following topics: Companies, Travel and tourism, Aviation, and Thailand. WCQuidditch ☎ ✎ 01:48, 12 May 2024 (UTC)[reply]
Delete Saw this in NPP and debated taking it to AfD myself. Agree fully with the nomination. Trainsandotherthings (talk) 01:57, 12 May 2024 (UTC)[reply]
Delete: WP:TOOSOON. Not necessarily promotional but does not satisfy WP:NCORP. '''[[User:CanonNi]]''' (talk • contribs) 03:02, 12 May 2024 (UTC)[reply]
Keep. It's not WP:TOOSOON if there are already independent reliable sources providing in-depth coverage of the subject, and Thai business news media have been doing so with their own analyses of the family's business structure since 2022.[10][11][12][13] --Paul_012 (talk) 09:19, 12 May 2024 (UTC)[reply]
None of the above sources meets WP:SIRS
1. promotional from MarketingOops.com
2. name mention, no SIGCOV
3. Youtube promo video
4. Promo about founder, nothing SIGCOV addressing the subject directly and indepth
// Timothy :: talk 12:01, 12 May 2024 (UTC)[reply]
I beg to differ.
Marketingoops is an online magazine covering brands and advertising; the content in their articles is their original analysis. They do carry PR pieces, which are tagged "PR News" at the top, like these. The above piece is not one of them.

The Manager 360° business magazine article is about the airline business landscape, focusing on two emerging airlines—Really Cool Airlines and P80 Air—plus the established Bangkok Airways. So the subject is the focus of a third of the article, not a mere name mention.

The YouTube video is a news scoop by the online arm of Thansettakij, a major business newspaper, discussing how the airline fits into owners' businesses properties, and its announced business plans. It is not a promo video created by the subject.

The Thansettakij article has four paragraphs discussing the airline. Granted, it's not the main focus of the article, which is about the owners and their business group.
--Paul_012 (talk) 14:46, 12 May 2024 (UTC)[reply]

Delete promotional, not yet independently covered or fully launched airlines. --扱. し. 侍. (talk) 09:34, 13 May 2024 (UTC)[reply]

Keep per the significant coverage in reliable sources found by Paul 012 (talk · contribs), whose detailed analysis shows that P80 Air meets Wikipedia:Notability (organizations and companies)#Primary criteria through significant coverage in the national newspaper Manager Daily, the major business newspaper Thansettakij [th], and the magazine Marketing Oops!. Cunard (talk) 09:47, 15 May 2024 (UTC)[reply]

Relisted to generate a more thorough discussion and clearer consensus.
Please add new comments below this notice. Thanks, Liz ^{Read! Talk!} 21:53, 18 May 2024 (UTC)[reply]

Delete Regurgitated company info and announcements and exec profiles does not meet GNG/WP:NCORP criteria for establishing notability. HighKing⁺⁺ 13:35, 23 May 2024 (UTC)[reply]

F-WWAI[edit]

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

Once citations to unreliable blogs like Simple Flying and Planespotters were removed, there isn't any citation here and most of what I can find about this plane is user generated. I suggest it be merged into Airbus A320 family. Avgeekamfot (talk) 09:51, 5 May 2024 (UTC)[reply]

Note: This discussion has been included in the list of Aviation-related deletion discussions. Spiderone^{(Talk to Spider)} 12:35, 5 May 2024 (UTC)[reply]
Keep - There are many sources I've found regarding this aircraft [14] [15] [16] 220.253.4.146 (talk) 22:48, 10 May 2024 (UTC)[reply]
There's really not much information regarding the aircraft in [1] and the two other sources that you've given, [2] and [3] are only brief mentions of the aircraft. Aviationwikiflight (talk) 14:46, 11 May 2024 (UTC)[reply]

Relisted to generate a more thorough discussion and clearer consensus.
Please add new comments below this notice. Thanks, ✗plicit 12:59, 12 May 2024 (UTC)[reply]

Merge with Airbus#Products: There are good information tomorrow from the article. Merging to the manufacturer is the best option for WP: Articles for Deletion#Alternative to Deletion. Safari Scribe^{Edits! Talk!} 11:39, 18 May 2024 (UTC)[reply]

Relisted to generate a more thorough discussion and clearer consensus.
Please add new comments below this notice. Thanks, Liz ^{Read! Talk!} 16:56, 19 May 2024 (UTC)[reply]

Carrier Air Group SIX[edit]

(Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL)

No evidence that this formation meets the GNG. Of the currently-cited sources, 2, 3, and 5 are self-published, not independent, and not reliable (except for direct quotes from Navy documents in source 3). Source 1 [17] seems to list only establishment and disestablishment dates (not sigcov), which is more than I expected from a source supposedly covering "1910-1920" – it seems the citing editor made a typo, the citation should read "1910-2010". Source 4 [18] doesn't seem to mention this unit at all. In sum, there are 0 sources that count toward the GNG, and I couldn't find anything in a before search. Toadspike (talk) 10:03, 3 May 2024 (UTC)[reply]

Note: This discussion has been included in the deletion sorting lists for the following topics: Military and United States of America. Toadspike (talk) 10:03, 3 May 2024 (UTC)[reply]

This can also be redirected to List of United States Navy aircraft wings. Toadspike (talk) 10:05, 3 May 2024 (UTC)[reply]

Note: This discussion has been included in the list of Aviation-related deletion discussions. WCQuidditch ☎ ✎ 15:46, 3 May 2024 (UTC)[reply]
Keep Subject is notable. WP:BEFORE seems to have overlooked Moroson, Lundstrom, Hammel, and books on the Battle of the Eastern Solomons or the Battle of Philippine Sea. Hawkeye7 (discuss) 20:35, 3 May 2024 (UTC)[reply]
I am willing to withdraw this nomination if you can properly cite those books in the article. With that information alone, it is very hard to know what books you are talking about. For example, I don't know how to find a book by "Moroson", and could not find one with such a name on either battle you mentioned. Toadspike (talk) 08:09, 6 May 2024 (UTC)[reply]

Relisted to generate a more thorough discussion and clearer consensus.
Please add new comments below this notice. Thanks, ✗plicit 12:56, 10 May 2024 (UTC)[reply]

Relisted to generate a more thorough discussion and clearer consensus.
Please add new comments below this notice. Thanks, Doczilla _{Ohhhhhh, no!} 07:09, 18 May 2024 (UTC)[reply]