Talk:1967 Lake Erie skydiving disaster
![]() | 1967 Lake Erie skydiving disaster has been listed as one of the Engineering and technology good articles under the good article criteria. If you can improve it further, please do so. If it no longer meets these criteria, you can reassess it. Review: April 18, 2024. (Reviewed version). |
![]() | A fact from 1967 Lake Erie skydiving disaster appeared on Wikipedia's Main Page in the Did you know column on 19 July 2023 (check views). The text of the entry was as follows:
| ![]() |
![]() | This article is rated GA-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||
|
Did you know nomination
edit- The following is an archived discussion of the DYK nomination of the article below. Please do not modify this page. Subsequent comments should be made on the appropriate discussion page (such as this nomination's talk page, the article's talk page or Wikipedia talk:Did you know), unless there is consensus to re-open the discussion at this page. No further edits should be made to this page.
The result was: promoted by Vaticidalprophet (talk) 02:42, 15 July 2023 (UTC)
- ... that an air traffic controller's mixup of two planes' locations caused 16 skydivers to drown when they unknowingly jumped from above Lake Erie? Source: Jackson, Tom (2017-08-14). "Disaster 50 years ago killed 16 sport parachutists". Sandusky Register. Ogden Newspapers. Retrieved 2023-07-02.
Moved to mainspace by Tamzin (talk). Self-nominated at 01:44, 10 July 2023 (UTC). Post-promotion hook changes for this nom will be logged at Template talk:Did you know nominations/1967 Lake Erie skydiving disaster; consider watching this nomination, if it is successful, until the hook appears on the Main Page.
- General eligibility:
- New enough:
- Long enough:
- Other problems:
Policy compliance:
- Adequate sourcing:
- Neutral:
- Free of copyright violations, plagiarism, and close paraphrasing:
- Other problems:
Hook: Hook has been verified by provided inline citation |
---|
|
QPQ: Done. |
Overall: @Tamzin: Nice work! Earwigs score [satisfactory], Hook is interesting, and length is also within the limit. Thanks RV (talk) 15:45, 10 July 2023 (UTC)
- @RAJIVVASUDEV: Hope it's all right, I've made a small post-review tweak to the hook, changing "over" to "from above", to avoid the potential misreading that they somehow jumped from one side of Lake Erie to another. Thanks for the review! -- 'zin[is short for Tamzin] (she|they|xe) 16:27, 10 July 2023 (UTC)
- @Tamzin: It's good. Thank you for notifying me. Thanks RV (talk) 17:10, 10 July 2023 (UTC)
Wind speed on lake
editHi Tamzin, thanks for this article. Just wondering, "winds of eight miles per hour (13 km/h)" is very light. I think where ref 16 Sandusky Register has "The temperature and wind eight miles out were enough" refers to distance ie "search area a line about eight miles offshore". 8 mph is roughly 7 knots or 13 km which, according to Beaufort scale#Modern scale, is a "Gentle breeze". From boaters' descriptions it was much stronger? JennyOz (talk) 11:58, 19 July 2023 (UTC)
- @JennyOz: You're completely right. My mistake. Removed; I'll take a look later at whether any of the other sources give the windspeed. (I vaguely recall that one of the NYT cites does.) -- Tamzin[cetacean needed] (she|they|xe) 18:02, 19 July 2023 (UTC)
- Thanks for the tweak. JennyOz (talk) 05:17, 20 July 2023 (UTC)
GA Review
editThe following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
GA toolbox |
---|
Reviewing |
- This review is transcluded from Talk:1967 Lake Erie skydiving disaster/GA1. The edit link for this section can be used to add comments to the review.
Nominator: Tamzin (talk · contribs) 20:26, 1 April 2024 (UTC)
Reviewer: Pi.1415926535 (talk · contribs) 20:58, 15 April 2024 (UTC)
@Tamzin: Nice work on this article. Just a few minor copyedits and some suggestions; no issues with the sections not listed here. Pi.1415926535 (talk) 23:09, 15 April 2024 (UTC)
- Thanks so much for the review, @Pi.1415926535! I've responded below. I welcome your thoughts. -- Tamzin[cetacean needed] (they|xe) 20:37, 17 April 2024 (UTC)
- @Tamzin: A few replies below; everything I didn't reply to looks good. Pi.1415926535 (talk) 22:41, 17 April 2024 (UTC)
- @Pi.1415926535: Thanks! Think I've handled the remaining issues. -- Tamzin[cetacean needed] (they|xe) 03:48, 18 April 2024 (UTC)
- Passing it now, great work! Pi.1415926535 (talk) 04:11, 18 April 2024 (UTC)
- @Pi.1415926535: Thanks! Think I've handled the remaining issues. -- Tamzin[cetacean needed] (they|xe) 03:48, 18 April 2024 (UTC)
- @Tamzin: A few replies below; everything I didn't reply to looks good. Pi.1415926535 (talk) 22:41, 17 April 2024 (UTC)
Infobox and lede
edit- Infobox and lede should both clarify that this was in the US
- Done -- Tamzin[cetacean needed] (they|xe) 20:19, 17 April 2024 (UTC)
- Per MOS:GEOLINK, I recommend having the link read "Huron, Ohio" instead of just "Huron"
- The Buffalo example in GEOLINK has always been ambiguous to me as to whether the link must extend to the second-level division, or whether one may only link the locality, as in the Sydney example. My approach has been to only link locality, for accessibility reasons: To someone who has trouble distinguishing between small areas of blue and black, it's not obvious that the comma in "Huron, Ohio" is blue and thus that "Ohio" is part of the same link. (I have this exact vision problem, although I compensate for it by underlining all links in my common.css, which makes it clear when a link spans multiple words.) Anyways, I'm happy to ask at WT:MOSLINK for clarification on the Sydney and Buffalo examples if you'd like, but that's my thinking. -- Tamzin[cetacean needed] (they|xe) 20:19, 17 April 2024 (UTC)
- I'm not opposed to having a discussion there to clarify - if you start it, I'll add my two cents - but I won't hold GA up over it. Pi.1415926535 (talk) 22:41, 17 April 2024 (UTC)
- Pinged you there, but, xlink to Wikipedia talk:Manual of Style/Linking § Ambiguity in GEOLINK examples for posterity. -- Tamzin[cetacean needed] (they|xe) 03:48, 18 April 2024 (UTC)
- I'm not opposed to having a discussion there to clarify - if you start it, I'll add my two cents - but I won't hold GA up over it. Pi.1415926535 (talk) 22:41, 17 April 2024 (UTC)
- The Buffalo example in GEOLINK has always been ambiguous to me as to whether the link must extend to the second-level division, or whether one may only link the locality, as in the Sydney example. My approach has been to only link locality, for accessibility reasons: To someone who has trouble distinguishing between small areas of blue and black, it's not obvious that the comma in "Huron, Ohio" is blue and thus that "Ohio" is part of the same link. (I have this exact vision problem, although I compensate for it by underlining all links in my common.css, which makes it clear when a link spans multiple words.) Anyways, I'm happy to ask at WT:MOSLINK for clarification on the Sydney and Buffalo examples if you'd like, but that's my thinking. -- Tamzin[cetacean needed] (they|xe) 20:19, 17 April 2024 (UTC)
- I'd recommend having the lede sentence be shorter and just indicate the scope of the disaster. Something like
On August 27, 1967, sixteen skydivers drowned in Lake Erie...
Currently, you have to read the whole first paragraph to know that the disaster was drowning.- How's this? -- Tamzin[cetacean needed] (they|xe) 20:19, 17 April 2024 (UTC)
- Is there any source newer than 1992 that indicates whether there have been deadlier accidents? I know the industry intentionally hides that sort of information, so the current source and wording is fine if nothing newer is available.
- I have been unable to find any sources more recent than the '92 article. I think that if any event had since surpassed this one for post-jump fatalities, it would have come up in my research at some point, if only in passing, but I can't prove that, hence the hedging with "as of 1992". -- Tamzin[cetacean needed] (they|xe) 20:19, 17 April 2024 (UTC)
Lead-up
edit- I recommend left-aligning the image so that it doesn't get pushed down by the infobox. (I know that image alignment can be controversial, but I find that keeping images with the accompanying text is most important.)
- I'm relatively pro-sandwiching as well, when it's a lesser of two evils. Done. -- Tamzin[cetacean needed] (they|xe) 20:26, 17 April 2024 (UTC)
- Worth linking "Ortner Airport" to List of airports in Ohio where it's mentioned?
- I'm not sure. I previously had this redlinked, but at Wikipedia:Articles for deletion/Ortner Airport, User:TheLongTone made a case against notability. While that AfD wasn't precedential because it ended in a speedy deletion, I looked myself and found I couldn't argue with their assessment. (If sources do exist, it's somewhere very specialist.) I suppose I could link to that list, probably through a redirect, but I'm not sure if the list gives any useful information to the reader that isn't already in this article. -- Tamzin[cetacean needed] (they|xe) 20:26, 17 April 2024 (UTC)
- Same GEOLINK change for Wakeman, Ohio
- Per above. -- Tamzin[cetacean needed] (they|xe) 20:26, 17 April 2024 (UTC)
- Link to aircraft registration before listing the number
- The letter "N" is linked to N-number, a redirect to Aircraft registration § United States. Is that too subtle? -- Tamzin[cetacean needed] (they|xe) 20:26, 17 April 2024 (UTC)
- I think it's a hair too subtle - the reader shouldn't have to click on the link to know what the number is supposed to be. Pi.1415926535 (talk) 22:41, 17 April 2024 (UTC)
- Changed. -- Tamzin[cetacean needed] (they|xe) 03:48, 18 April 2024 (UTC)
- I think it's a hair too subtle - the reader shouldn't have to click on the link to know what the number is supposed to be. Pi.1415926535 (talk) 22:41, 17 April 2024 (UTC)
- The letter "N" is linked to N-number, a redirect to Aircraft registration § United States. Is that too subtle? -- Tamzin[cetacean needed] (they|xe) 20:26, 17 April 2024 (UTC)
- Were both the 20k and 30k jumpers to deploy chutes at 3k feet? If so, change
They were
toAll were
.- The Time source does not say what height the 30k jumpers would deploy at. -- Tamzin[cetacean needed] (they|xe) 20:26, 17 April 2024 (UTC)
- I would then clarify in the article that the 20k jumpers would open at 3k, as the current wording is ambiguous. Pi.1415926535 (talk) 22:41, 17 April 2024 (UTC)
- I've actually just cut it entirely. I say later that they did jump at that height, so it would only be worth mentioning the planned jump height if it were different from what actually happened. -- Tamzin[cetacean needed] (they|xe) 03:48, 18 April 2024 (UTC)
- I would then clarify in the article that the 20k jumpers would open at 3k, as the current wording is ambiguous. Pi.1415926535 (talk) 22:41, 17 April 2024 (UTC)
- The Time source does not say what height the 30k jumpers would deploy at. -- Tamzin[cetacean needed] (they|xe) 20:26, 17 April 2024 (UTC)
Incident
edit- The first sentence here most duplicates the last sentence in the previous section.
- Fixed -- Tamzin[cetacean needed] (they|xe) 20:30, 17 April 2024 (UTC)
Aftermath
editfollowing days, the final body being
-->following days; the final body was
- Done -- Tamzin[cetacean needed] (they|xe) 20:36, 17 April 2024 (UTC)
- I see you've created Freeman v. United States (1975); I would recommend creating Dreyer v. United States (1972), Freeman v. United States, and Dreyer v. United States as additional redirects. Not a GA requirement, obviously, but worth doing real quick.
- The PTOPIC for Freeman is almost certainly this 2011 case, and PTOPIC on Dreyer is ambiguous between the '72 case and some recent 9th Circuit cases, but I've created the date-disambiguated Dreyer. Good catch. Think I had meant to do that at some point.
:)
-- Tamzin[cetacean needed] (they|xe) 20:36, 17 April 2024 (UTC)
- The PTOPIC for Freeman is almost certainly this 2011 case, and PTOPIC on Dreyer is ambiguous between the '72 case and some recent 9th Circuit cases, but I've created the date-disambiguated Dreyer. Good catch. Think I had meant to do that at some point.
Overall
edit- GA review (see here for what the criteria are, and here for what they are not)
- It is reasonably well written.
- It is factually accurate and verifiable, as shown by a source spot-check.
- a (reference section): b (inline citations to reliable sources): c (OR): d (copyvio and plagiarism):
- a (reference section): b (inline citations to reliable sources): c (OR): d (copyvio and plagiarism):
- It is broad in its coverage.
- a (major aspects): b (focused):
- a (major aspects): b (focused):
- It follows the neutral point of view policy.
- Fair representation without bias:
- Fair representation without bias:
- It is stable.
- No edit wars, etc.:
- No edit wars, etc.:
- It is illustrated by images and other media, where possible and appropriate.
- a (images are tagged and non-free content have non-free use rationales): b (appropriate use with suitable captions):
- a (images are tagged and non-free content have non-free use rationales): b (appropriate use with suitable captions):
- Overall:
- Pass/Fail:
- Pass/Fail: