Wikipedia:Articles for deletion/Log/2010 September 5

Source: Wikipedia, the free encyclopedia.

Purge server cache

  • Keep as per Mjroots. yet another waste of time by an editor who doesn't seem to have read
    WP:NOTLAW--Wikireader41 (talk) 14:38, 5 September 2010 (UTC)[reply
    ]
  • That's a nice little piece of ABF right there. I wonder if any wandering admin is watching out for CIVIL violations in these Afds, as I have been assured is actually happening. MickMacNee (talk) 15:19, 5 September 2010 (UTC)[reply]
    Although it's ironic you want to cite BURO to claim this Afd is a waste of time. If these outcomes are so common, BURO makes it pretty clear that there should actually already be a Guideline somewhere to justify it, as the existing community consensus regarding what should be accepted and what should be rejected. However, I have looked high and low, and I have never once found a Guideline that even comes close to what Mjroots suggests makes a notable aircrash. So, you can either keep on running around making these kinds of afd votes displaying just how much contempt you have for people who don't follow your interpretation of existing policies, or you can try and write the Guideline you seem to think documents common practice and common sense for these aircrashes. Although I warn you, the folks at VPP are pretty hot on what BURO handily describes as the principles of policies, and very much realise that written policies and guidelines should be taken seriously unless there is a good reason they may be changed to reflect evolving consensus. MickMacNee (talk) 15:33, 5 September 2010 (UTC)[reply]
  • Comment It's nice to know I "waste[d]" your time. Aren't you the one who to the effort to click "Edit" and time in the wikicode to say delete? So I don't know how I caused you to "waste your time." —
    moral♪♫ 18:05, 5 September 2010 (UTC)[reply
    ]
Of course we can't, but this (747 crashing + the fact its a UPS plane) isnt like every other plane crashes. And you would be surprised how many other articles on plane crashes we have, most havingless significance than this. Fattyjwoods Push my button 02:05, 6 September 2010 (UTC)[reply]
Further to my earlier comment, this AFD has a snowball's chance..., the latest count is overwhelmingly in favour of Keep. Bzuk (talk) 20:25, 5 September 2010 (UTC)[reply]
In this
any biscuits for turning up and commenting, even though it's apparently a lost cause? MickMacNee (talk) 20:50, 5 September 2010 (UTC)[reply
]
What? I gave my opinion (!voted) more then once in this Afd!? (not counting this comment...) That would be done in human error, which I am capable of but in looking around, I don't quite see where you think I made such an error. Pmedema (talk) 22:43, 5 September 2010 (UTC)[reply]
I was talking to Bzuk, hence the indentation. MickMacNee (talk) 23:28, 5 September 2010 (UTC)[reply]
  • Keep - Meets
    WP:N, in that it has sufficient independent third party refs to establish notability, which is the deciding standard. - Ahunt (talk) 20:46, 5 September 2010 (UTC)[reply
    ]

Since

moral♪♫ 16:58, 6 September 2010 (UTC)[reply
]

Arbitrary break 1

To paraphrase Donna Moss in The West Wing I may have overstated a little, but just a little; a cockpit fire is a very serious matter, and I'd say that investigators would want to arrive at a basic understanding of the cause very quickly in case it's a fleet-wide problem or has widespread relevance to air safety (like the Cincinnati DC-9 fire). There are lots of seemingly-small things that happen to aircraft that don't result in WP articles, but which do have fleet-wide ramifications. There was a Qantas aircraft that had a serious electrical failure a few years ago; it turned out that a drip tray under one of the galleys was not installed correctly and galley waste liquid was overflowing onto an electrical centre. This had fleet-wide consequences in that inspections found quite a few similar problems in the fleet, across a number of carriers. I agree that people are in too much of a rush to create these articles before anything is really known other than that the aircraft crashed, I agree that "hull loss" does not equal "notable"; however we have the article now and at the risk of being accused of CRYSTAL, the cockpit fire is to me the stand-out factor. If it turns out that the cause is one of the crew dropping a cigarette or some other isolated event, then by all means re-open the deletion discussion. YSSYguy (talk) 00:44, 7 September 2010 (UTC)[reply]
The issue with this is more OR than CRYSTAL. You've taken the reports of a fire, but as far as I can see, everything beyond that is your own speculation without the actual evidence in this actual crash to back it (albeit the general theory is based on not unreasonable assumptions and aviation pratices), and that is what you are basing your vote on. A basic CRYSTAL vote would see someone simply assertiong something will happen, such as when people claim that something simply being investigated means it will have significance whatever the outcomes, whereas you've gone a bit more complex than that, and have implied you accept this could after all turn out to be an insignificant crash, and want to keep on a provisional basis. To keep on that basis is I think quite wrong and against the inclusion policy, because it does not take account of
good arguments, that it is notable here and now, on the RS evidence available. Don't get me wrong, if there was even a scrap of RS evidence right now that this crash is believed to have had a cause which has fleet wide consequences, I could be persuaded to vote keep, but as far as I can see, this RS doesn't exist. As an aside, I would have actually thought if the pilot was smoking, it would be a pretty big deal no? MickMacNee (talk) 18:14, 7 September 2010 (UTC)[reply
]
  • Strong keep - It's preposterous that we're wasting time on this discussion. Of course a fatal hull-loss crash of a nearly-new 747 with US crew and ownership is going to generate sufficient RS to sustain the article. The fact that nobody has published anything but news in the first days after the crash is hardly surprising. Show me a similar crash that didn't eventually meet GNG and I might reconsider. LeadSongDog come howl! 19:20, 7 September 2010 (UTC)[reply]
    I don't think the idea that lots of news coverage can 'sustain an article' is a revelation to anybody here. The issue is, whether that is the purpose of Wikipedia or not, per EVENT and per NOT#NEWS. You'd have a better case for expressing incredulity that anybody could even think this, if you yourself had actually found a similar incident that had an article, which detailed exactly how it had lasting historical significance, rather than asking others to look for you. We have a list of 747 hull losses, there must be one on there I'm sure. MickMacNee (talk) 19:40, 7 September 2010 (UTC)[reply]
    Ok, I'll race you. Can you find a non-notable before I find a notable? LeadSongDog come howl! 21:23, 7 September 2010 (UTC)[reply]
    Turns out we have already have articles on every fatal 747 hull loss except the 27 November 2001 MK Airlines Boeing 747 crash, in Nigeria, of a 20 year old aircraft in which one crew member was killed. Perhaps we need to write that one too. LeadSongDog come howl! 22:06, 7 September 2010 (UTC)[reply]
    Really? What about the 1976 Iranian Air Force freighter? that was the first one I saw without an article on the list. If it's true, then perhaps a few of those need to be put through AFD? Because I would be amazed if every single one of those 49 crashed met 2 criteria of
    WP:EVENT. If it is only possible to write an article about it from contemporary news reporting, and it doesn't meet 2 criteria of AIRCRASH, then we are back to square one. I think I can almost guarantee we will be seeing that spring up in an article in one form or another, very soon. MickMacNee (talk) 22:26, 7 September 2010 (UTC)[reply
    ]
    Actually, it does have one - MK Airlines Flight 1602. It's not what I would call convincing. It appears to have been created on the assumption that a 747 loss is automatically notable, which again brings us back to square one - which came first, the chicken or the egg? Are they all notable becuase they all (maybe?) have articles, or do they all have articles because they are all notable? There's certainly no evidence in that specific article that that crash meets EVENT or AIRCRASH. MickMacNee (talk) 22:34, 7 September 2010 (UTC)[reply]
    Ah, you're right: we do need an article on
    WP:V. We should perhaps inquire if the full Nigerian report is available through the NTSB reading room in Washington.LeadSongDog come howl! 17:37, 8 September 2010 (UTC)[reply
    ]
    LeadSong: Have you checked the Nigerian accident investigation agency to see if any report copies are available on its website? WhisperToMe (talk) 19:27, 8 September 2010 (UTC)[reply]
    I had a look, but couldn't find much. There's a lot of "under construction" on that website. Tragically, it seems that had the lessons of that 2001 event only been taken for action Sosoliso_Airlines_Flight_1145 four years later might have been avoided at the same airport. Its official report (avail on Skybrary) reads like a virtual replay, but with 105 killed. Bad wx, no power for the runway lighting during "daylight" hours, instrument approach below threshold, missed the runway, struck an exposed concrete culvert, and burned. This may have finally inspired serious reforms in Nigerian air safety, we'll see. LeadSongDog come howl! 20:08, 8 September 2010 (UTC)[reply]
  • Keep We are invited to consider whether the article fails notability under the policy
    WP:NOTNEWS which in turn asks whether the subject of the article has enduring WP:Notability. WP:NOTNEWS then gives clarifying remarks which lead me to suspect this subject is "enduring". In the guideline WP:Notability it seems to me the only aspect by which this well-referenced article could "fail" is the general notability guideline where, because all five criteria seem to me to have been met, the article has a presumption of meeting the notability criterion for being kept. The matter is then referred to consensus. So, in this case there is no policy for deletion and we are asked to try and decide amongst ourselves whether the article is worth keeping. The matter becomes quite subjective. I happen to think the article is very well worth keeping and I note there are detailed bodies of such information for the US[35] and UK[36], for example, aimed at a broad audience. For me, merely not liking articles about air accidents and observing that they are reported as news, is nowhere near enough to sustain a delete argument. I think this nomination is unhelpful to the encyclopedia. Thincat (talk) 21:29, 7 September 2010 (UTC)[reply
    ]
    I follow your logic, but you've completely missed out the part of NOT#NEWS that went on to mention
    WP:EVENT, which is the guideline that fleshes out the subjective 'is this just news' question for things like aircrashes, once the 5 N criteria have been met. And by the by, NTSB/AAIB reports are not meant for a broad audience, they are primarily intended to be used by legislators and the aviation industry. They are published for reasons of full disclosure, and cover far more incidents and accidents than Wikipedia ever would, even in the most inclusive of set-ups. MickMacNee (talk) 22:26, 7 September 2010 (UTC)[reply
    ]

Arbitrary break 2

  • Delete. Wow. My eyes hurt, I've read this twice over and gone to the bother of reading the guidelines...
WP:AIRCRASH
, if you actually work through, also says there is no notability here, but that essay is still being debated on its talk page. The guys over there should get it sorted one way or the other to avoid these ridiculous AfDs.
The Long Version. My argument follows the line of logic that I believe the other deleters are using but might not have set out like this.
WP:EVENT
, so I will do that guideline the honour of going through each point:
An event that is a precedent or catalyst for something else of lasting significance is likely to be notable.
Not at the moment, and impossible to assess without a
WP:CRYSTALBALL
.
Notable events usually have significant impact over a wide region, domain, or widespread societal group.
Well, the impact at the moment is only in the news. Are there going to be any changes as a result of this event? Well, who knows, still no
WP:CRYSTALBALL
here.
An event must receive significant or in-depth coverage to be notable.
The guideline focuses on in-depth information, but at the moment there are only reports of the event, so not enough notability here for me, at the moment.
Next is Duration of coverage
To hard to ascertain, but not likely to last that long. I can't even see the crash results being reported internationally, but, oh, that would require my
WP:CRYSTALBALL
again.
Significant national or international coverage is usually expected for an event to be notable. Wide-ranging reporting tends to show significance, but sources that simply mirror or tend to follow other sources, or are under common control with other sources, are usually discounted.
There is indeed diverse coverage at the moment, but I don't believe that's the point of this clause, it's looking for something deeper, all we see at the moment are "sources that simply mirror", perhaps not literally, but they're all reporting the same superficial facts.
So my conclusion from the guidelines, which are the consensus view of notability at en.wp, is that this event is not notable. There is some additional colour from
WP:AIRCRASH
, where this event ticks A3 - Airline - First, deadliest, or most significant accident for a particular airline but just above it there is the statement If the accident or incident matches criteria only in this section, then coverage should normally be on the article about the aircraft or airline.. So according to that page it fails as well. There is some discussion on its talk page as to whether the inclusion grounds are too tight, so I wouldn't want to apply it as gospel either way.
The keepers generally seem to argue that as this is "non-standard" news,
WP:EVENT
.
I think that's enough! Once more facts are forthcoming about this crash we can re-assess, but at the moment this article is for a non-notable event. Bigger digger (talk) 00:15, 9 September 2010 (UTC)[reply]
Comment: A few issues:
"To hard to ascertain, but not likely to last that long." - Take a look at the coverage of Air France Flight 447. The coverage lasts and lasts, and lasts, and lasts. See, many of the responders are aware of how aviation accidents involving large airliners are covered. They do not last a short time. The coverage may stop for a while, but it comes back and back and back again.
"The guideline focuses on in-depth information, but at the moment there are only reports of the event, so not enough notability here for me, at the moment." I would argue that coverage is already "in-depth" because the media is beginning to explore theories and possible reasons why the UPS plane crashed. When that happens, the coverage is "in-depth." - For that matter, I just found a Wall Street Journal article which explicitly says that the UPS crash is raising concerns over smoke in airline cockpits. Another WSJ link discussed how there had been a long-running debate about how to combat smoke in airline cockpits. This alone is "in-depth" coverage.
"I can't even see the crash results being reported internationally, but, oh, that would require my WP:CRYSTALBALL again." When a crash of an American cargo airliner happens in the UAE with two deaths, the results will and are being reported internationally. Two countries are involved, and it will involve a relationship between the US and the UAE. This is already apparent. One cannot use WP:CRYSTALBALL to attack that reasoning. It's common sense.
"An event that is a precedent or catalyst for something else of lasting significance is likely to be notable." - The way the aviation industry works, with its focus on preventing accidents and analyzing the heck out of existing ones to get as much data as possible, it is almost certain that this accident will be a precedent for preventing something else or starting something new. Everything from TWA 800 to Swissair 111 to Korean Air 801 - all have become catalysts for doing something different. It is what the aviation industry does.
BTW, thank you for the TLDR summary! It helps us determine how to get a consensus on this matter.
WhisperToMe (talk) 02:27, 9 September 2010 (UTC)[reply]
Thanks WTM. I'm still of the opinion that your points contribute to the newsworthy-ness of the event, rather than its encyclopedic notability. That can only be ascertained some time down the line in order to satisfy
WP:EVENT (and no, I don't know how much time will be required, but the Sept 7th WSJ article about smoke issues is a step in the right direction). No worries for the TLDR, where was yours?!! Bigger digger (talk) 13:18, 9 September 2010 (UTC)[reply
]
Ack, I think my TLDR ran away into the sunset ;)
I found another source from a Louisville, KY paper that stated that the NTSB had been advocating for additional fire protections on cargo aircraft. This was put in the context of UPS Flight 6. It seems certain that UPS Flight 6 will be a figure in the debate over fire protection equipment on cargo aircraft.
WhisperToMe (talk) 20:50, 9 September 2010 (UTC)[reply]
And when you no longer have to write "it seems certain" I'll be welcoming this article back, but at the moment that's
WP:CRYSTAL. No tl;dr needed here! Cheers, Bigger digger (talk) 21:55, 9 September 2010 (UTC)[reply
]
As this progresses, once the level of debate increases I'll strike out "it seems certain" and replace it with "it is certain."
WhisperToMe (talk) 03:25, 10 September 2010 (UTC)[reply]
Most of your reasoning relies on the
WP:Original research. We don't want this in articles, but it is necessary for assessing the notability of a subject since we will find few reliable sources that directly say "subject X is notable for inclusion in Wikipedia.") --memset (talk) 14:26, 10 September 2010 (UTC)[reply
]
Comment: I wholeheartedly agree with the assessment. Because of the way this scenario is playing out, I have every reason to believe that this is a notable accident. WhisperToMe (talk) 16:01, 10 September 2010 (UTC)[reply]

Historically important as it is the first UPS accident involving a complete hull loss and the expiration of crew. —Preceding unsigned comment added by 166.183.206.41 (talk) 16:53, 11 September 2010 (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.