Jump to content

Wikipedia:Articles for deletion/United Airlines Flight 328: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Keep
Line 52: Line 52:
*'''Keep''' - Uncontained failures in modern jet engines are rare, something like one per million flights. This one caused large chunks of engine to rain down on a populated area, which I would guess is even more rare. --[[User:Bongwarrior|Bongwarrior]] ([[User talk:Bongwarrior|talk]]) 06:32, 22 February 2021 (UTC)
*'''Keep''' - Uncontained failures in modern jet engines are rare, something like one per million flights. This one caused large chunks of engine to rain down on a populated area, which I would guess is even more rare. --[[User:Bongwarrior|Bongwarrior]] ([[User talk:Bongwarrior|talk]]) 06:32, 22 February 2021 (UTC)
*'''Keep''' "engine failures are routine incidents" - maybe, but not for those inflight at the time. Easily passes WP:GNG. '''[[User:Lugnuts|<font color="002bb8">Lugnuts</font>]]''' <sup>[[User talk:Lugnuts|Fire Walk with Me]]</sup> 06:39, 22 February 2021 (UTC)
*'''Keep''' "engine failures are routine incidents" - maybe, but not for those inflight at the time. Easily passes WP:GNG. '''[[User:Lugnuts|<font color="002bb8">Lugnuts</font>]]''' <sup>[[User talk:Lugnuts|Fire Walk with Me]]</sup> 06:39, 22 February 2021 (UTC)
*’’’Keep’’’ clearly notable & its v handy to have a Wiki page as a collated set of Reliable Sources on this. [[User:NBeale|NBeale]] ([[User talk:NBeale|talk]]) 07:01, 22 February 2021 (UTC)

Revision as of 07:01, 22 February 2021

United Airlines Flight 328 (edit | talk | history | protect | delete | links | watch | logs | views) – (View log)
(Find sources: Google (books · news · scholar · free images · WP refs· FENS · JSTOR · TWL)

Aviation incident in which a plane landed safely with a burned-out engine. This is a case of WP:NOTNEWS. Yes, it has news coverage, but not everything that gets news coverage needs a Wikipedia article, especially given that engine failures are routine incidents. This merits a mention in the aircraft and/or airport article at most. Sandstein 21:28, 21 February 2021 (UTC)[reply]

Note: This discussion has been included in the list of Aviation-related deletion discussions. Sandstein 21:28, 21 February 2021 (UTC)[reply]
Note: This discussion has been included in the list of Colorado-related deletion discussions. CAPTAIN RAJU(T) 21:33, 21 February 2021 (UTC)[reply]
Note: This discussion has been included in the list of Events-related deletion discussions. CAPTAIN RAJU(T) 21:34, 21 February 2021 (UTC)[reply]
And yeah, same goes for hi-jackings, dual engine fires, hydraulics, cabin fires, surges, and practically every other emergency. We just follow checklists, and deal with them. ThatIPEditor (talk) 05:41, 22 February 2021 (UTC)[reply]
Note: This discussion has been included in the list of Transportation-related deletion discussions. ...William, is the complaint department really on the roof? 23:05, 21 February 2021 (UTC)[reply]
Should probably also be mentioned at Pratt & Whitney PW4000, whatever the outcome here. Martinevans123 (talk) 23:23, 21 February 2021 (UTC)[reply]
The FAA is orderering increased inspections and trying to get other countries to do the same.[1] This shouldn't be up for discussion at this point.Alpacaaviator (talk) 00:14, 22 February 2021 (UTC)[reply]
  • Delete Not notable, albeit impressive looking damage to the nacelle, and concluded by a perfectly uneventful single engine flight back to the airport and safe landing. From an aircraft safety PoV, it's a minor incident. Btw, by all appearances, the failure was well contained. An "uncontained failure" is a very specific type of failure which implies a breach of the engine case, which is clearly not the case here. Arugia (talk) 00:20, 22 February 2021 (UTC)[reply]
  • Keep, per WP:AIRCRASH, as noted above. An uncontrolled engine failure with pieces of the engine falling out of the sky is a serious accident. There will be an in-depth investigation and follow-up coverage, we can be certain of that. Not a WP:NOTNEWS situation. Nsk92 (talk) 00:27, 22 February 2021 (UTC)[reply]
  • Keep The nomination is based upon a vague wave at WP:NOTNEWS. What that policy actually says is "routine news reporting of announcements, sports, or celebrities is not a sufficient basis for inclusion in the encyclopedia". The incident in question was not routine; it is in the news for the opposite reason – because it was quite dangerous, dramatic and unusual. For an example of routine news about sports and celebrities, see ITN which currently leads with Djokovic winning a tennis tournament – a very routine occurrence, as he's won that event 8 times before. This demonstrates that the policy is a dead letter and so it's the policy which should be deleted. Andrew🐉(talk) 00:37, 22 February 2021 (UTC)[reply]
  • Too soon (delete or redirect) Per me previous comment above for the target. But this is probably a case of WP:TOOSOON. Planes have engine failures semi-routinely (if, luckily, rarely), and while sure it's in the news (cause we don't have a madman US president doing crazy things, so of course got to fill it with something else), unless this brings about some form of lasting impact (as in serious safety recommendations from a report) beyond dramatic and unusual pictures, there's no reason to have an article about it yet. Hell, even if the NTSB do launch an investigation there's no reason to have an article, there's plenty of routine incidents that get investigated that we don't have articles on. RandomCanadian (talk / contribs) 01:09, 22 February 2021 (UTC)[reply]
That there are plenty of notable accidents that don't currently have articles is not a reason to delete this one. It is a reason to create articles for those other accidents. Lasting impact into the ages is not required for notability. We just need significant coverage by independent sources that is not transient, and doesn't disappear after a few days. In this case the rarity and the unusual nature of this particular accident make such vanishing coverage rather unlikely. In such situations rather than deleting the article now the correct approach is to wait and revisit the matter in six months or so. If the coverage has disappeared by then, the article can be re-nominated for AfD. But it is alwats easier to destroy than to build, and we are supposed to be in the buiseness of building the encyclopedia. Nsk92 (talk) 01:21, 22 February 2021 (UTC)[reply]
I also strongly echo Andrew about the misuse of WP:NOTNEWS. If almost every piece of coverage talks about how rare this kind of event is, then it doesn't count as routine. Gnomingstuff (talk) 03:09, 22 February 2021 (UTC)[reply]
  • Strong keep, especially given the breaking news that some planes will be grounded Johndavies837 (talk) 03:12, 22 February 2021 (UTC)[reply]
  • Keep: As others have said, rare event. Side note, if the aftermath (such as the grounding of the other 777s) becomes the bigger story, it would be good to rename/restructure the article. Sewageboy (talk) 03:15, 22 February 2021 (UTC)[reply]
  • Keep A lot of people saying "delete" are seemingly implying that because this incident may be mundane from a disaster perspective that somehow means it doesn't meet notability. Which, even if that were true, doesn't seem consistent with what is currently seen as notable on Wikipedia -- there's a lot of articles documenting flights that didn't end in total fire and carnage. If articles like this one about unruly passengers can exist and be featured on the home page, I don't see why an engine exploding can't. 68.117.55.155 (talk) 03:16, 22 February 2021 (UTC)[reply]
  • Keep: First of all, this event has gotten quite a lot of media attention. Second, these types of catastrophic engine failures are pretty rare. Third, the engine used on this flight (a Pratt & Whitney PW4000) has had a history of catastrophic engine failures (see Korean Air Flight 2708 for example). Due to the problems with this particular engine, there is likely going to be some major developments with the engine type. These three things show that this is a noteworthy article and should be kept on the site. Southwest Fan 101 (talk) 04:00, 22 February 2021 (UTC) — Preceding unsigned comment added by 2600:1700:A030:A870:C04A:599B:EC3F:D8F0 (talk) [reply]
  • Keep. This article has just become highly-notable, just look at this BBC story with very rare footage of a fiery jet turbine shot from the cabin in mid-filght. Cordially, History DMZ (HQ) (wire) 05:15, 22 February 2021 (UTC)[reply]
  • Keep, as this has prompted an airworthiness directive and also action from international regulators, notably Japan ([2]). This is obviously an AfD on fast-shifting information but the keep !votes are increasing in frequency. Sammi Brie (she/her • tc) 05:26, 22 February 2021 (UTC)[reply]

References

  • Keep: Keep, because that although that single engine failed is common, we do not usually consider this "routine", and it is still a incident. But this one is a commercial scheduled flight, making it not "routine". Might need some parts deleted because that they aren't reliable sources, but, I think it is best to keep. ThatIPEditor (talk) 05:39, 22 February 2021 (UTC)[reply]
  • Keep: This is not a routine engine failure but a widely reported incident that saw debris shed over a populated area. Planes grounded, and some chance that these aircraft (old 777s powered by P&W engines) will be withdrawn from service altogether as a result. ProhibitOnions (T) 06:28, 22 February 2021 (UTC)[reply]
  • Keep - Uncontained failures in modern jet engines are rare, something like one per million flights. This one caused large chunks of engine to rain down on a populated area, which I would guess is even more rare. --Bongwarrior (talk) 06:32, 22 February 2021 (UTC)[reply]
  • Keep "engine failures are routine incidents" - maybe, but not for those inflight at the time. Easily passes WP:GNG. Lugnuts Fire Walk with Me 06:39, 22 February 2021 (UTC)[reply]
  • ’’’Keep’’’ clearly notable & its v handy to have a Wiki page as a collated set of Reliable Sources on this. NBeale (talk) 07:01, 22 February 2021 (UTC)[reply]