Talk:Ural Airlines Flight 178
![]() | This article is rated B-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||
|
Destination
As Crimeas status is disputed, I changed the destination to be in Crimea (neither Ukraine nor Russia). Then that dispute can hopefully be left out of the article. -- 188.151.51.78 (talk) 11:39, 17 August 2019 (UTC)
See also section
I've removed two accidents caused by ice ingestion. IMvHO, the three accidents now left are sufficient. Mjroots (talk) 17:21, 23 August 2019 (UTC)
Content removed from reactions
Per WP:BRD, starting a discussion here. Why should that information be included? Keep in mind that the subject of this article is an airplane crash, not some controversial Ukrainian website... 107.190.33.254 (talk) 21:01, 3 September 2019 (UTC)
- You seem to have no idea what's going on between Ukraine and Russia and Crimea and all, if you think it is irrelevant. Staszek Lem (talk) 21:27, 3 September 2019 (UTC)
- No, I am aware of the disputes between Russia and Ukraine, but they have nothing to do with this article... 107.190.33.254 (talk) 21:59, 3 September 2019 (UTC)
- Yes it has immediately to do with the article: all world praises the pilots, while Ukraine lists them on the witch-hunt website. Staszek Lem (talk) 22:17, 3 September 2019 (UTC)
- That's not our problem, (your argument appears to be WP:SYNTH at best) and thus we are in no need to report it (WP:NOTNEWS), especially when it shines by it's lack of significant mention in more sources (the website of the Ukrainian organization is WP:PRIMARY and doesn't warrant it's POV being reported, and the Russian source only has a short story on the matter - so we should avoid mentioning it so as not to give it WP:UNDUE weight). In any case, when it is not crucial to the subject (and, in this case, it clearly has no significant impact), it is better to avoid any statements which are controversial, even more so when their origin is WP:FRINGE. 107.190.33.254 (talk) 00:39, 4 September 2019 (UTC) Edit: see also the above section about "Destination" - I think that is a right way to proceed, and we should keep the Crimea dispute ("broadly construed") out of this article (especially since the link is rather tenuous... merely because the flight was headed to Crimea does not suddenly make this a part of the conflict). 107.190.33.254 (talk) 00:42, 4 September 2019 (UTC)
- WP:PRIMARY was used here to confirm the fact reported in in secondary source. Yes is is a short, but glaring story, widely circulated in Rusian media. Yes, it is crucial for subject: the crew is under the threat in a whole country. FYI some journalists were killed after landing in Mirotvorets, while other people were severely harassed by ukronazis. And there is no controversy: a plain fact readers can judge for themselves. Yes, merely because the flight was headed to Crimea makes it a violation of Ukrainian law; moreover, I remember a Russian ship or two were seized because among its destinations were Crimean ports, or something. Staszek Lem (talk) 02:28, 4 September 2019 (UTC)
- P.S. Hell, this was reported even by BBC! (ref added). Staszek Lem (talk) 02:33, 4 September 2019 (UTC)
- That's not our problem, (your argument appears to be WP:SYNTH at best) and thus we are in no need to report it (WP:NOTNEWS), especially when it shines by it's lack of significant mention in more sources (the website of the Ukrainian organization is WP:PRIMARY and doesn't warrant it's POV being reported, and the Russian source only has a short story on the matter - so we should avoid mentioning it so as not to give it WP:UNDUE weight). In any case, when it is not crucial to the subject (and, in this case, it clearly has no significant impact), it is better to avoid any statements which are controversial, even more so when their origin is WP:FRINGE. 107.190.33.254 (talk) 00:39, 4 September 2019 (UTC) Edit: see also the above section about "Destination" - I think that is a right way to proceed, and we should keep the Crimea dispute ("broadly construed") out of this article (especially since the link is rather tenuous... merely because the flight was headed to Crimea does not suddenly make this a part of the conflict). 107.190.33.254 (talk) 00:42, 4 September 2019 (UTC)
- Yes it has immediately to do with the article: all world praises the pilots, while Ukraine lists them on the witch-hunt website. Staszek Lem (talk) 22:17, 3 September 2019 (UTC)
- No, I am aware of the disputes between Russia and Ukraine, but they have nothing to do with this article... 107.190.33.254 (talk) 21:59, 3 September 2019 (UTC)
The crew being "under threat in a whole country" is relevant to the crew, but not to the flight. The BBC gives it a short paragraph. The talk about "ukronazis" doesn't go in the article in any case, so while your opinion has been politely noted, it is not necessary. I have changed what is in the article to match better with the BBC article (since that is an truly independent source which can be trusted for stuff like this)... 107.190.33.254 (talk) 03:33, 4 September 2019 (UTC)
is relevant to the crew, but not to the flight
-- bullshit. Let's delete the section "Crew", then. BBC? Independent? It was long time ago when BBC was a true example if true journalism. Now it is full of fake news and political bias. No further disagreement, anyway. Staszek Lem (talk) 16:59, 4 September 2019 (UTC)- The article as it currently stands is acceptable. We report good, and bad, on both sides, without bias for or against, but neutrally. Mjroots (talk) 17:55, 4 September 2019 (UTC)
Commons files used on this page or its Wikidata item have been nominated for deletion
The following Wikimedia Commons files used on this page or its Wikidata item have been nominated for deletion:
Participate in the deletion discussion at the nomination page. —Community Tech bot (talk) 03:22, 10 March 2022 (UTC)
GA review
- This review is transcluded from Talk:Ural Airlines Flight 178/GA1. The edit link for this section can be used to add comments to the review.
Nominator: RandomInfinity17 (talk · contribs) 02:45, 22 April 2025 (UTC)
Reviewer: RecycledPixels (talk · contribs) 04:37, 6 May 2025 (UTC)
Hello, I am RecycledPixels. I will review this article over the next few days. I usually take the review in several steps, and not normally in order. Please don't respond or edit this GA review page until I've completed item #7, the "overall assessment" field at the end, which is my sign that I have completed my steps, the ball is in your court, and I will wait for you to respond. That way we won't be disrupting each other with edit conflicts during this process. I will also ping you to let you know I have finished my part. RecycledPixels (talk) 04:37, 6 May 2025 (UTC)
Rate | Attribute | Review Comment |
---|---|---|
1. Well-written: | ||
![]() |
1a. the prose is clear, concise, and understandable to an appropriately broad audience; spelling and grammar are correct. | Clear and concise
This is a pretty broad definition that is generally considered to mean, "is it understandable?" The article passes this standard, although it really needs an extensive copy edit. There are a lot of convoluted statements that I think can be expressed more clearly than they are at the moment. Part of the problem is that there is a lot of passive voice use in the article, which makes it more difficult for a reader to understand WHO did WHAT, but other issues are word choice that I think could use some polishing. Not to worry, though, because these comments exceed what I consider the GA standard of "clear and concise" to be. However, you'll need to iron this out if you ever have a goal is to take it beyond GA, which I hope you do because it is a valuable topic with plenty of reliable sources. Understandable to a broad audience Marginally passes, although I'd rather see less jargon in the "Accident" and "Investigation" sections, which is tricky to do when your sources are written for a technical audience. A particular example would be pretty much most of the third paragraph of the "Accident" section, after the third sentence. Imagine reading the article out loud to a twelve-year-old to explain the incident. Would they understand what was going on in any of that section? Spelling and grammar issues:
|
![]() |
1b. it complies with the Manual of Style guidelines for lead sections, layout, words to watch, fiction, and list incorporation. | MOS:LEAD issues:
MOS:LAYOUT issues:
MOS:WTW issues:
|
2. Verifiable with no original research, as shown by a source spot-check: | ||
![]() |
2a. it contains a list of all references (sources of information), presented in accordance with the layout style guideline. | Citation 5 (Orenburzhie.ru) is geoblocked and/or a dead link, please provide archive link (22 Sep 2020 seems to work ok). Citation 21 (Meduza) needs author information (listed at the bottom of the article). Citation 84 (FlightGlobal) needs access date because web sources can change, so we need to know on what date you looked at that site and saw the information you cited. Citation 85 (RBK Group) needs authors (listed at the bottom of the article). Citation 90 (FlightGlobal) needs date accessed. Citation 93 (Chita.ru) needs author information (listed at the bottom of the article).
What statement is citation #2 (CFM International) supporting in the Aircraft subsection of the Background section?
|
![]() |
2b. reliable sources are cited inline. All content that could reasonably be challenged, except for plot summaries and that which summarizes cited content elsewhere in the article, must be cited no later than the end of the paragraph (or line if the content is not in prose). | I performed a check of all citations that appear in the "Background" section as well as the first two paragraphs of the "Accident" section. A total of 20 citations appear, which represents approximately 18% of the 108 total citations that appear in the article. For the accident report citations, the page numbers in the Russian-language report do not correspond to the page numbers in the English-language report, so I used section numbers, images, and page layouts in the Russian-language report to identify the corresponding pages in the English translation, and used the English version to perform fact checks. There were two minor issues that I encountered:
Crew and passengers section
Accident section
|
![]() |
2c. it contains no original research. | I have not found any issues with what I consider to be original research. |
![]() |
2d. it contains no copyright violations or plagiarism. | None of the sections checked in detail showed signs of close paraphrasing or copyright violations. Automated check also performed, no concerns. |
3. Broad in its coverage: | ||
![]() |
3a. it addresses the main aspects of the topic. | The minimum content that I expect to find in a comprehensive aviation accident article is a description of the accident, the immediate aftermath, the investigative process, and the result of the investigation. It should also contain details about the aircraft, details about the passengers and crew, and some background information about the flight, and these can be brief. This article covers all the major aspects of this event that I would expect to find in a comprehensive article. |
![]() |
3b. it stays focused on the topic without going into unnecessary detail (see summary style). | The accident report contains a ton of well-cited information, but some of the information in this article tends to drift into "too much information" territory. For example, the description of the push-back process with exact times the engines were started and which taxiways the aircraft used weren't factors in the big picture. Same thing with some of the routine aspects of the takeoff, such as the exact second the takeoff clearance was given, and how many seconds it took for the nose to liftoff. Did the use of flex temp play a factor in the accident? It might have because different settings may have changed the point of liftoff, but the relevance isn't obvious. Is it important to know the aircraft's airspeed at the time Yusupov called out, "Come on, fly past, bird" etc., or would it be sufficient to say something like "as the aircraft accelerated down the runway"? There is a ton of detail here, but I get distracted from the important aspects when there is too much detail.
|
![]() |
4. Neutral: it represents viewpoints fairly and without editorial bias, giving due weight to each. | I didn't think I'd have any issues with neutrality in an aviation accident article, and I've had to think about it a while, but I have a problem with the neutrality of the last paragraph of the "Reactions" section, and the inclusion of what appears to be a private Ukrainian doxing site's opinions. Does any of that information improve the reader's understanding of the crash?
The criticism of the MAK's release of the final report via Telegram also seems oddly critical without giving reason. Wikipedia calling out the MAK for doing it wrong is very different from relevant agencies and organizations calling out the release of the report via Telegram, but there's no mention of that anywhere. The first three paragraphs of the "Investigation" section currently read as Wikipedia expressing criticism about the actions of the flight crew. After mentioning that MAK conducted the investigation into the accident, helped by BEA and AAIB, the next section starts out with "The crew did not apply proper procedures..." and continues to list everything the crew did wrong, rather than stating that when the MAK released its report, the report said all these things. This is a major issue. The later paragraphs are better, but it would be better if the report was clearly identified as the issues that were raised by the MAK. |
![]() |
5. Stable: it does not change significantly from day to day because of an ongoing edit war or content dispute. | Since the major article revision on 21 April, edits to the article have been maintenance-related and uncontroversial. |
6. Illustrated, if possible, by media such as images, video, or audio: | ||
![]() |
6a. media are tagged with their copyright statuses, and valid non-free use rationales are provided for non-free content. | All images are appropriately and plausibly tagged with copyright status. I have to AGF one of the images, "Wreckage of Ural Airlines Flight 178 (3).jpg", because it is attributed to the website of the Ministry of Emergency Situations, but the source link is to Aviation Safety Network. I poked around the Internet Archives of the mchs.gov.ru site and I can't find any photos of any plane crashes when I searched around August 2019 or July 2021 when the image was uploaded, so I'll need to trust that the caption on the ASN site is accurate. I didn't spend more than 15 minutes searching. If this article ever went up for FAC, I'd expect this to be a sticking point unless the original publication location for this photo can be verified. |
![]() |
6b. media are relevant to the topic, and have suitable captions. | I'm not sure what the image "Ural Airlines Flight 178 autopilot disconnection.jpg" is trying to show me with the caption "Recreation of flight parameters when the autopilot disconnected". If there is something in particular I should be paying attention to, it should be identified in the caption. If the image is only of marginal relevance, it should be removed. The alt text on that image contains more information, but still does not help me understand the relevance of the image. Likewise, I think the caption "Overview of the accident site: can use a slightly expanded caption because all of the tags in the image are in Russian and I don't know what any of the points mean. (The image description on commons appears to have translations). The caption of the neighborhood dump has a mention "with several gulls on top" but I can't make that out from the image, probably because of resolution issues. How about something along the line of identifying the photo as the neighborhood dump and stating something along the line of it had had a problem with attracting gulls to the area, or something like that? |
![]() |
7. Overall assessment. | @RandomInfinity17: Not yet. Don't be discouraged by the number of red minus marks, I really don't feel like there is a lot of work that needs to be done to meet the GA standard, most of the items I've pointed out should be pretty straightforward to resolve. The neutrality issue is probably the biggest issue I have with it, and will probably take the most work. I'm happy to place this nomination on hold to give you time to make changes, then when you're done, ping me and I'll see how it's coming along.
Even though I like this table format of GA review because it keeps me focused on the narrow parameters of what the criteria of what a GA article is, and I think it does a pretty good job of teaching and explaining the GA criteria to nominators, the complexity of wiki markup sometimes makes responding to my comments tends to be a bit of a pain. What has worked in the past is to add your responses in italics within the table immediately after my comments, or just making a new section below this table. I've taken a swing at least at making my reviews easier to respond to with a different template format, but I don't know where I left off because I've lost it in my piles of unfinished articles. If you strongly disagree with my review and feel like I'm completely out in space, or you don't think you'll have to get back to this in a decent amount of time, just let me know and I can quickfail it so you can renominate it any time you're ready. RecycledPixels (talk) 02:00, 7 May 2025 (UTC) |
Additional suggestions that not part of the GA criteria. Whether or not these are implemented will not affect whether this article passes or fails the GA nomination.
- Some issues with false precision with the {{convert}} templates, such as "after the ingestion of a medium-sized bird 1.5 lb (0.68 kg)", "One of the birds ingested into the left engine was considered large, with a weight of above 2.5 lb (1.1 kg)", and "4,950 m (16,240 ft) from the end of Runway 12". See Help:Convert#Rounding
- Be consistent with conversions. Metric->imperial (most likely) or imperial->metric throughout the article.
- Archive links to web citations are great to have to prevent link rot. It's pretty simple to do, just go to https://web.archive.org/ , enter the URL in the "Save Page Now" field, and the Wayback Machine will do most of the rest of the work. Then add the citation template fields archive-url=, archive-date=, and url-status=live to the citation templates. That helps protect the article when some bored kid comes long five years from now and maliciously changes facts that we can't verify from the original source.
- In the first paragraph of the "Accident" section, clarify that when Yusupov said they would only address ECAM issues after 400 ft., that it refers to 400 ft. above ground level, not 400 ft. altitude.
- All (specific) comments in 1a have been addressed except for The failure for Murzin to properly call out "Positive climb". I don't see the grammar error here, may you please be more specific? RandomInfinity17 (talk - contributions) 22:51, 7 May 2025 (UTC)
- The complete sentence is
The failure for Murzin to properly call out "Positive climb" resulted in Yusupov's failure to raise the gear, and in later interviews to the MAK, he said he never heard Murzin call out "Climb".
"The failure FOR x TO y" is grammatically incorrect. You would write, "Murzin's failure to properly call out POSITIVE CLIMB resulted in ... " (grammatically correct, simpler and clearer) or you could write "The improper call out of POSITIVE CLIMB resulted in... " (less desirable because it hides who made the improper call) or "The failure of (something) resulted in..." or other variations that use Murzin as the subject of the sentence rather than Murzin's failure to follow correct procedures. There are also some "he" pronouns later in that sentence that could use clarification, since you've mentioned two people, but I think that second item is more of a stylistic preference than a grammatical error that runs up against Criteria 1a. RecycledPixels (talk) 15:35, 8 May 2025 (UTC)- Advise taken. RandomInfinity17 (talk - contributions) 23:33, 8 May 2025 (UTC)
- The complete sentence is
- All (specific) comments in 1a have been addressed except for The failure for Murzin to properly call out "Positive climb". I don't see the grammar error here, may you please be more specific? RandomInfinity17 (talk - contributions) 22:51, 7 May 2025 (UTC)
- Second concern in 1b addressed, but I do think it is valuable for the reader to know how the results of the report were made public. The fact that the previous sentence says "the last update to the investigation on the MAK website was an interim statement made one year after the accident" makes the reader wonder why the next paragraph is about the results of the supposedly never-released investigation. Bringing up the fact that it was posted on Telegram resolves this question. But feel free to explain your argument more. RandomInfinity17 (talk - contributions) 22:57, 7 May 2025 (UTC)
- The article in its current form is 4,864 words. The lead section is 405 words, and the three sentences in the lead about the report is 71 of those 405 words (18%). The four sentences about this in the body of the article total 124 words (3% of the body's 4,459 words). Even if this isn't a neutrality issue, you're running up against MOS:LEADREL, "According to the policy on due weight, emphasis given to material should reflect its relative importance to the subject, according to published reliable sources. This is true for both the lead section and the body of the article. If there is a difference in emphasis between the two, editors should seek to resolve the discrepancy."
- In addition to that, there's still the issue of neutrality of that I brought up under criteria 4. The whole section appears to be based on the September 7, 2022 Meduza article. That article quotes an anonymous source from within Rosaviatsiya that says that MAK's process is to first release the report to the airline and the regulator, allow the airlines to make changes to their policies and allow the regulator to make new policies, and only then publish the report for the public. That source also adds that they are sure that the report will be published on the website, and that it's just a matter of time. The leaked document is dated August 16, 2022, so less than a month before the Meduza article was published. Much of the vocal criticism appears to be based on statements by aviation journalist Andrei Menshenin. Who is he? Maybe he's a really prominent subject matter expert, and maybe he's just a blogger with an axe to grind, I don't know. On the other hand, today, the mak-iac.org website still lists the accident as "investigation ongoing", so about what I'd expect and not a good look for them. In order to resolve my neutrality concern, I'd like to see more (recent if possible) reporting by reliable sources that the failure to officially release the report is worthy of note, and not just "how it's always been done" because the report could embarrass certain prominent political figures who had gushingly praised the pilots in the aftermath. RecycledPixels (talk) 16:45, 8 May 2025 (UTC)
- For the comment about the lead, I just removed the entire paragraph about the report not being published; too much weight given to it. As for the concerns about neutrality, I'll probably get to this after finishing my first round of comments on the Western 636 GA. RandomInfinity17 (talk - contributions) 23:33, 8 May 2025 (UTC)
- All comments in 2a addressed RandomInfinity17 (talk - contributions) 23:10, 7 May 2025 (UTC)
- All comments in 2b addressed RandomInfinity17 (talk - contributions) 23:17, 7 May 2025 (UTC)
- 3b addressed, but feel free to point out any other details you think need addressing (aside from paragraph 3 of accident, I will get to that soon). RandomInfinity17 (talk - contributions) 23:32, 7 May 2025 (UTC)
- First point of 4 addressed; paragraph removed. As for the second you point you brought up, I don't know how the phrase it better. I added an extra sentence on why it might have been never officially published, but I don't know if it is enough. For the third point, I started to add what you were looking for, but I will probably add more. RandomInfinity17 (talk - contributions) 00:01, 8 May 2025 (UTC)
- I discussed this further in the 1b section above. RecycledPixels (talk) 16:46, 8 May 2025 (UTC)
- All comments in 6b addressed. RandomInfinity17 (talk - contributions) 00:12, 8 May 2025 (UTC)
- Additional suggestion 1, 2, and 4 implemented. For 2, I used imperial because it is the unit the MAK used in their investigation and what is used in aviation generally. I might add archive links to everything at some later on, but probably not now. RandomInfinity17 (talk - contributions) 00:53, 8 May 2025 (UTC)
- I was surprised to see that Russian aviation had switched to imperial units from metric. I came across comments about that when I was looking up the issue about the release of the accident report. What could go wrong? RecycledPixels (talk) 16:48, 8 May 2025 (UTC)
- Second concern in 1b addressed, but I do think it is valuable for the reader to know how the results of the report were made public. The fact that the previous sentence says "the last update to the investigation on the MAK website was an interim statement made one year after the accident" makes the reader wonder why the next paragraph is about the results of the supposedly never-released investigation. Bringing up the fact that it was posted on Telegram resolves this question. But feel free to explain your argument more. RandomInfinity17 (talk - contributions) 22:57, 7 May 2025 (UTC)
- I think I would like this review to be placed on hold to give me time to address understandability and neutrality. RandomInfinity17 (talk - contributions) 01:03, 8 May 2025 (UTC)
- I've put it on hold. I try to stay as hands-off as possible through this part of the process as possible, so when you're ready for me to take another look at it, please ping me. RecycledPixels (talk) 17:16, 8 May 2025 (UTC)
- Thanks! RandomInfinity17 (talk - contributions) 23:33, 8 May 2025 (UTC)
- I've put it on hold. I try to stay as hands-off as possible through this part of the process as possible, so when you're ready for me to take another look at it, please ping me. RecycledPixels (talk) 17:16, 8 May 2025 (UTC)