77.238.65.171 (talk) No edit summary |
77.238.65.171 (talk) |
||
Line 376: | Line 376: | ||
Question: Was hijacking of EgyptAir flight MS181 part from Flydubai Flight 981 investigation? |
Question: Was hijacking of EgyptAir flight MS181 part from Flydubai Flight 981 investigation? |
||
⚫ | |||
Today this is most effective way to do Air Accident Investigations. Golden rule: If questions about a disaster that you investigate become too uncomfortable you can always make hijacking to answer them. |
|||
http://edition.cnn.com/2016/03/29/world/hijacked-egyptair-plane-live-update/index.html?adkey=bn |
|||
For example, Have you ever wondered is any logic in the fact that Investigators always include experts from the company that make the crashed plane? Like the criminal investigator to invite the killer who do killing to take part in his own investigation. |
|||
⚫ |
Revision as of 08:07, 29 March 2016
This article is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Czech Airlines divert
This is FlightRadar24 data of Czech Airlines flight OK914 / CSA914 from Prague to Rostov on 18 March 2016, which diverted to Krasnodar.
https://www.flightradar24.com/data/flights/ok914/#9232f55 — Preceding unsigned comment added by 178.143.107.35 (talk) 09:24, 19 March 2016 (UTC)
- Relevance ? MilborneOne (talk) 09:43, 19 March 2016 (UTC)
- It arrived to Rostov shortly after midnight, meaning in the early hours of 19 March 2016 local time. It diverted to Krasnodar just a few hours before FlyDubai crashed. Relevance: ABSOLUTE. The pilots decided not to land in Rostov due to weather conditions. Had the pilots of FlyDubai made the same decision a few hours later, the crash would not have happened.
- You are wrong because the crash did not occur due to wind, as seen from the video, ATC audio and Flightradar24. The aircraft was at 4000 feet when the incident occurred, the wind was not even a contributing cause. It made two landing attempts which is absolutely a reasonable decision in these wind conditions. Aeroflot's flight 1166 made three attempts before diverting. FlyDubai only made two. It would probably consider diverting to Krasnodar after the second go-around, or waiting in a holding pattern for some more time. The Czech flight is irrelevant because it did not attempt landing, unlike the Aeroflot flight which tried 3 times, and which we mention in the article. The Czech flight was merely waiting in the holding pattern and did not even descend to pattern altitude. --Anthony Ivanoff (talk) 11:05, 19 March 2016 (UTC)
- Again, there was nothing wrong with the conditions at 4000 feet above ground, and Aeroflot made 3 successful go-arounds. So an aircraft that diverted due to the wind is irrelevant. It is absolutely a normal operating procedure to land with these wind conditions. The plane did not crash due to the wind at the airport. It's just as if the Czech plane would divert because of a medical emergency: irrelevant to this crash. --Anthony Ivanoff (talk) 11:20, 19 March 2016 (UTC)
- Sorry, if reliable sources indicate the Czech flight is related to the accident then we can report it, we cant make stuff up. MilborneOne (talk) 11:11, 19 March 2016 (UTC)
- Absolute majority of sources only report the Aeroflot flight which made 3 attempts and which is a normal operating procedure. --Anthony Ivanoff (talk) 11:19, 19 March 2016 (UTC)
I have to correct myself. The FlyDubai crash occurred at 01:41 UTC, which was exactly when the Czech Airline flight was arriving to the area and descending to 12,000f. The holding pattern of CSA flight took place shortly after the crash. So, the Czech Airlines flight is not relevant. My apologies. — Preceding unsigned comment added by 178.143.107.35 (talk) 11:27, 19 March 2016 (UTC)
L:There is a relevance because hours apart with same weather one was safely dierted.Lihaas (talk) 13:33, 19 March 2016 (UTC)
- You are presuming the cause of the accident was the weather, again it is not for us to jump to conclusions. MilborneOne (talk) 14:13, 19 March 2016 (UTC)
Named pilot was Cypriot, not Greek
See [1], though it doesn't say he was the captain. 62.228.107.188 (talk) 13:00, 19 March 2016 (UTC)
- Yep, the TV aso mentioned the oddity. Just caught the name, I guess.Lihaas (talk) 13:32, 19 March 2016 (UTC)
Flight Aware tracking log
I am unsure how this could best be used for this article, however her is a link to the FlightAware flight tracking log for the subject: https://flightaware.com/live/flight/FDB981/history/20160318/1745Z/OMDB/URRR/tracklog .--RightCowLeftCoast (talk) 15:41, 19 March 2016 (UTC)
British English
It's safe to say by this point that this article uses British English (localised, 24-hr. time, etc.), so I've added the British English banner to the top of this page. If anyone disagrees, please leave a comment here so that consensus may be established. Cheers! Colonel Wilhelm Klink (Complaints|Mistakes) 22:00, 19 March 2016 (UTC)
- Agree , but would you be so kind check the text of this article from time to time, to ensure that its Britishness is not corrupted? :-) Daniel (talk) 22:29, 19 March 2016 (UTC)
- Sure, but if it's copyedited at some point, the form of English might change depending on the whims of the copyeditor. I've seen it happen before, either from British to American or American to British. The main thing to ensure is conformity throughout the article. Colonel Wilhelm Klink (Complaints|Mistakes) 22:50, 19 March 2016 (UTC)
- Sometimes non-native English speakers keep different input sources, they might not be conscious of that :-) --TerrainAhead ×TALK× 23:38, 19 March 2016 (UTC)
- Sure, but if it's copyedited at some point, the form of English might change depending on the whims of the copyeditor. I've seen it happen before, either from British to American or American to British. The main thing to ensure is conformity throughout the article. Colonel Wilhelm Klink (Complaints|Mistakes) 22:50, 19 March 2016 (UTC)
Flydubai or FlyDubai?
I noticed that BBC World Service, New York Times Washington Post, Associated Press, Los-Angeles Times and other reputable sources, cited in this article, all spell the airline's name as FlyDubai. So I suggest to use this spelling of the airline's name throughout this article. If anyone disagrees, please leave a comment here so that consensus may be established. Thank you. Daniel (talk) 23:07, 19 March 2016 (UTC)
- You have a point; however, the Wikipedia article for the airline has the spelling as "Flydubai", and so does the company's official website. My opinion is that either spelling is proper, so you should edit as you see fit. Colonel Wilhelm Klink (Complaints|Mistakes) 23:15, 19 March 2016 (UTC)
- The airline appears to describe itself as "flydubai", not "Flydubai" or "FlyDubai". A {{Lowercase title}} template may therefore be appropriate for both this article and the flydubai article. Bahnfrend (talk) 01:54, 21 March 2016 (UTC)
- That template was added when the article was created but it kept getting removed multiple times by trolls..its actually 'flydubai' (no caps whatsoever)...--Stemoc 02:47, 21 March 2016 (UTC)
- The spelling of the phrase "flydubai Flight 981" seems counterintuitive to English spellers, but a case can be made that it is the proper spelling. Either Way, we should establish a consensus here.– Gilliam (talk) 02:50, 21 March 2016 (UTC)
- According to Manual of Style/Capital letters/Trademarks, "for trademarks, editors should ... use the style that most closely resembles standard English text formatting and capitalization rules. For trademarks that are given in mixed or non-capitalization by their owners (such as adidas), follow standard English text formatting and capitalization rules for proper names (in this case, Adidas)." Daniel (talk) 03:10, 21 March 2016 (UTC)
- ... and it then goes on to say "The mixed or non-capitalized formatting should be mentioned in the article lead ..." A similar comment is made in Wikipedia:Manual_of_Style/Trademarks#Trademarks that begin with a lowercase letter: "Conventionally, articles usually give the normal English spelling in the lead, followed by a note such as "(stylized as ...)" with the stylized version ..." But neither this article nor the flydubai article does either of these things. And I might add that I think this style rule is both inappropriate and discriminatory - why are we allowed to use "IBM" instead of "Ibm", and "Häagen-Dazs" instead of "Hagen-Daz", but not "flydubai" instead of "Flydubai"? Bahnfrend (talk) 15:34, 21 March 2016 (UTC)
- Despite your disagreement with this Wikipedia policy, are you ready to comply with it? Daniel (talk) 15:57, 21 March 2016 (UTC)
- I'm not advocating non compliance. But I am saying that the policy is inappropriate, and that in any case this article doesn't comply with the style guide. Bahnfrend (talk) 10:36, 22 March 2016 (UTC)
- The Manual of Style does not demand that a special notice about the peculiarities of the trademarks' spelling, should be placed in the lead of all articles, where this trademark is mentioned. I agree, that it is appropriate to point out in the Flydubai article itself, that this airline prefers to spell its name with a lowercase letter at the beginning, but such special notice is absolutely irrelevant in this article about the air crash. Daniel (talk) 11:19, 22 March 2016 (UTC)
- I'm not advocating non compliance. But I am saying that the policy is inappropriate, and that in any case this article doesn't comply with the style guide. Bahnfrend (talk) 10:36, 22 March 2016 (UTC)
- I think the adidas/Adidas example most closely resembles this situation and that we should begin the word with a capital letter. However, I don't think it's appropriate to add a capital in the middle of the word because many trademarks are compound words that don't capitalize the second word within the compound word. Thus, I think that "Flydubai" should be used, not "flydubai" or "FlyDubai". AHeneen (talk) 00:03, 23 March 2016 (UTC)
- Despite your disagreement with this Wikipedia policy, are you ready to comply with it? Daniel (talk) 15:57, 21 March 2016 (UTC)
- ... and it then goes on to say "The mixed or non-capitalized formatting should be mentioned in the article lead ..." A similar comment is made in Wikipedia:Manual_of_Style/Trademarks#Trademarks that begin with a lowercase letter: "Conventionally, articles usually give the normal English spelling in the lead, followed by a note such as "(stylized as ...)" with the stylized version ..." But neither this article nor the flydubai article does either of these things. And I might add that I think this style rule is both inappropriate and discriminatory - why are we allowed to use "IBM" instead of "Ibm", and "Häagen-Dazs" instead of "Hagen-Daz", but not "flydubai" instead of "Flydubai"? Bahnfrend (talk) 15:34, 21 March 2016 (UTC)
- According to Manual of Style/Capital letters/Trademarks, "for trademarks, editors should ... use the style that most closely resembles standard English text formatting and capitalization rules. For trademarks that are given in mixed or non-capitalization by their owners (such as adidas), follow standard English text formatting and capitalization rules for proper names (in this case, Adidas)." Daniel (talk) 03:10, 21 March 2016 (UTC)
- The spelling of the phrase "flydubai Flight 981" seems counterintuitive to English spellers, but a case can be made that it is the proper spelling. Either Way, we should establish a consensus here.– Gilliam (talk) 02:50, 21 March 2016 (UTC)
- That template was added when the article was created but it kept getting removed multiple times by trolls..its actually 'flydubai' (no caps whatsoever)...--Stemoc 02:47, 21 March 2016 (UTC)
- The airline appears to describe itself as "flydubai", not "Flydubai" or "FlyDubai". A {{Lowercase title}} template may therefore be appropriate for both this article and the flydubai article. Bahnfrend (talk) 01:54, 21 March 2016 (UTC)
Agree, just like airberlin :) --TerrainAhead ×TALK× 00:12, 23 March 2016 (UTC)
- Agree and withdraw my suggestion to use FlyDubai, instead of Flydubai. Daniel (talk) 00:28, 23 March 2016 (UTC)
New information
Aviation experts among Wikipedians might probably be interested in the following information which was published recently:
- Standard Arrival Chart Instrument 1
- Standard Arrival Chart Instrument 2
- Instrument Approach Chart, ILS
- Instrument Approach Chart, NDB
- Aerodrome Chart
- Aerodrome Ground Movement and Aircraft Parking Chart
- Three METAR during the first approach and two METAR during the second approach
Daniel (talk) 02:08, 20 March 2016 (UTC)
Ignore the news about "fire on board" before the crash which is seen by the cameras
Thе bright light that is visible from the cameras before crash is only LANDING LIGHTS that are very powerful and camera distort this bright light to looking as "the plane is on fire". Only information that can be derives from this cameras is that it hit the ground with first left tail section, left wing and nose up (landing lights are directed to the cameras from right) with speed between 18000-24000 feet per minute vertical speed (about 0.3 sec on the cameras for 30-40 meters distance, i.e. 90-120 m/s or about 18000-24000 fpm ). https://www.youtube.com/watch?v=IBJ32eVWVNc — Preceding unsigned comment added by 77.238.65.171 (talk) 10:20, 20 March 2016 (UTC)
- Agree This is just an example of sensationalism, so typical for tabloids. Daniel (talk) 11:20, 20 March 2016 (UTC)
- I agree, but we have the policy Wikipedia:No original research, so we can't say this unless a reliable source says so. AHeneen (talk) 21:15, 20 March 2016 (UTC)
- Guys, it's not any sort of lights. It's a missile falling. Passenger flights don't fly at 60 degree angles and don't land at 60 degrees either, do they? Russians likely accidentally shot that plane somewhere else and made a cover-up. That would explain a lot of things like damaged black boxes. You didn't have damaged black boxes even on MH17 which Russian Buk missile shot. And they say this plane was nearly empty on fuel before impact. And the only video is from some place far far away. No cameras in the airport? Seriously? First bad landing of Flydubai? No, that one is yet to happen. Ibmua (talk) 12:07, 22 March 2016 (UTC)
I think the light too bright to indicate landing lights. The attitude seemed "flying" in that the nose was down, flashing wingtip lights visible. So hitting "tail first" nose up seems inconsistent with high speed and stable attitude. Markrkrebs (talk) 11:37, 23 March 2016 (UTC)
Additionally, speed was high before the descent. This suggests strongly that no wind condition could cause loss of control: the aircraft was established on a go-around with good speed. There will be much more data from the recorders so it should be easy to understand what really happened soon. Meanwhile, my speculation is some kind of dramatic failure, not a pilot error or weather. Markrkrebs (talk) 11:30, 24 March 2016 (UTC)
short of the runway?
The article currently says "The aircraft crashed about 250m (800ft) short of the runway". If the landing had already been aborted, is "short of the runway" the correct term? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:30, 20 March 2016 (UTC)
- It actually crashed about 250m (800ft) from the edge of the runway, slightly to the left of it, which can be seen now from the photo of the crash location. Thank you for noticing it. Daniel (talk) 15:18, 20 March 2016 (UTC)
- "before the runway threshold" would work. AHeneen (talk) 21:08, 20 March 2016 (UTC)
- Since it fall from the sky, I would say it doesn't matter at what point of the runway. Wykx (talk) 21:13, 20 March 2016 (UTC)
Flydubai's first crash
I don't feel like this trivia belongs in the introduction. Is there a better place for it in the article? 62.228.200.32 (talk) 17:09, 20 March 2016 (UTC)
- Well, according to WP:LEAD, the lead section should explain the notability of the article's subject. I think, that is why this piece of information was placed here. This crash was the only one for an airline with an excellent safety record. Daniel (talk) 17:54, 20 March 2016 (UTC)
- ? A passenger aircraft crash is notable irrespective of who the operator is. 62.228.200.32 (talk) 18:01, 20 March 2016 (UTC)
- There were a lot of crashes in the history and many of them do not have its own Wikipedia article. If you take a look on other air crash articles, you will notice, that it is always mentioned in the lead section if, i.e., the crash was the dealiest in history, or in this country, or in this airline, or the only crash of this type of aircraft, etc. Daniel (talk) 18:30, 20 March 2016 (UTC)
- No person is gonna read the first paragraph, where it says both plane and occupants disintegrated, and wonder, 'hey, why is this notable?', only to be enlightened by the revelation that this was the first Flydubai crash. 62.228.200.32 (talk) 19:09, 20 March 2016 (UTC)
- We can't predict what influences the air crash would make on the airline and yet to give a conclusion. This might be the most notable thing we have about the airline so far. After knowing the causes, we could add more details to it. Let's just wait :-) --TerrainAhead ×TALK× 20:19, 20 March 2016 (UTC)
- Fair enough, I guess. 62.228.200.32 (talk) 22:02, 20 March 2016 (UTC)
- We can't predict what influences the air crash would make on the airline and yet to give a conclusion. This might be the most notable thing we have about the airline so far. After knowing the causes, we could add more details to it. Let's just wait :-) --TerrainAhead ×TALK× 20:19, 20 March 2016 (UTC)
- No person is gonna read the first paragraph, where it says both plane and occupants disintegrated, and wonder, 'hey, why is this notable?', only to be enlightened by the revelation that this was the first Flydubai crash. 62.228.200.32 (talk) 19:09, 20 March 2016 (UTC)
- There were a lot of crashes in the history and many of them do not have its own Wikipedia article. If you take a look on other air crash articles, you will notice, that it is always mentioned in the lead section if, i.e., the crash was the dealiest in history, or in this country, or in this airline, or the only crash of this type of aircraft, etc. Daniel (talk) 18:30, 20 March 2016 (UTC)
- ? A passenger aircraft crash is notable irrespective of who the operator is. 62.228.200.32 (talk) 18:01, 20 March 2016 (UTC)
Resolved I moved this information to the special sub-section about the airline. Daniel (talk) 15:40, 23 March 2016 (UTC)
- Thanks! 128.0.208.243 (talk) 22:34, 23 March 2016 (UTC)
Flight path
Though the map was removed as a copyvio (the map layer was Google's), the last few moments of the flight can be mapped from public ADS-B data released by Flightradar24. 62.228.200.32 (talk) 22:05, 20 March 2016 (UTC)
- I believe this data is not available for any use, even non-commercial. Can you link to the terms of use of their data? --Anthony Ivanoff (talk) 10:38, 23 March 2016 (UTC)
- I'm not sure, but I'm having a bit of a hard time seeing how Flightradar24 might be able to claim copyright over the raw data output of a publicly-funded software publicly transmitted over radio waves. 93.109.172.116 (talk) 09:03, 28 March 2016 (UTC)
Better aircraft photo?
Searching through the commons and found 2 other photos of A6-FDN. These other photos show the 738 on final approach from an angle presenting the front of the aircraft, rather than the back. Are these better photos, or is the current one fine? A340swazzen (talk) 06:52, 21 March 2016 (UTC)
- I think the current one is fine. Daniel (talk) 10:58, 21 March 2016 (UTC)
- Shall we put a photo of the crash site in the information box and put the aircraft photo we have now by the description of the aircraft?--TerrainAhead ×TALK× 17:55, 21 March 2016 (UTC)
- I do not think it's necessary. According to the template, the image provided in this infobox should be a "picture of the accident or incident or its aftermath, or, if involving a single aircraft, that aircraft". So this image is perfectly OK. Daniel (talk) 18:32, 21 March 2016 (UTC)
- Agree You're right. The crash was so bad that the aircraft was totally smashed into small pieces :( Nobody is going to recognise the aircraft from those photos... --TerrainAhead ×TALK× 22:16, 21 March 2016 (UTC)
- I do not think it's necessary. According to the template, the image provided in this infobox should be a "picture of the accident or incident or its aftermath, or, if involving a single aircraft, that aircraft". So this image is perfectly OK. Daniel (talk) 18:32, 21 March 2016 (UTC)
- Shall we put a photo of the crash site in the information box and put the aircraft photo we have now by the description of the aircraft?--TerrainAhead ×TALK× 17:55, 21 March 2016 (UTC)
Similar accidents
Until the air accident investigation establish the definite cause of the crash, we can only speculate about similarity of this case with others. That is why I moved the link about another crash, provided by Petebutt from "See also" section here. As soon as the results of the investigation are announced, we can put those accidents, which had similar reasons with Flight FZ981, back to "See also" section. Feel free to add more cases to the list. The explanation of similarity would be helpful. Daniel (talk) 16:19, 23 March 2016 (UTC)
- They are almost identical:- B737, bad weather, at night, go-around, impacting the ground at high velocity in a near vertical dive, no distress call. How more similar do you want them?--Petebutt (talk) 06:42, 24 March 2016 (UTC)
- To User:Petebutt: I completely agree with you, that Flydubai Flight 981 and Tatarstan Airlines Flight 363 look not just similar, but virtually identical, judging by all unofficial information we have at the moment. But I would still be reluctant to create the "See also" section now. As you see, some editors on this talk page insisted that it was a pilot's suicide, and they may try to push the Germanwings case into that section, others insisted that it was a fire on board, or a missile, etc. So I suggest to wait for the preliminary results of the official investigation. It's a matter of some weeks, if not days, and then we can have a definite, comprehensive and most reliable answer about the cause of this crash. Daniel (talk) 11:56, 24 March 2016 (UTC)
- Look again this case and when investigation end, Daniel - "some weeks" is very optimistic prognosis.* Tatarstan Airlines Flight 363 — Preceding unsigned comment added by 77.238.65.171 (talk) 13:10, 24 March 2016 (UTC)
- @Petebutt:: Would you like, meanwhile, to do some clean-up in the Tatarstan Airlines Flight 363 article? I think, at the moment, it might be a little bit complicated for an average reader to comprehend all the details of that accident from the description which is provided there. I tried to write the lead section there now, but I'm not sure that I got all the details correctly. Daniel (talk) 02:23, 25 March 2016 (UTC)
- To User:Petebutt: I completely agree with you, that Flydubai Flight 981 and Tatarstan Airlines Flight 363 look not just similar, but virtually identical, judging by all unofficial information we have at the moment. But I would still be reluctant to create the "See also" section now. As you see, some editors on this talk page insisted that it was a pilot's suicide, and they may try to push the Germanwings case into that section, others insisted that it was a fire on board, or a missile, etc. So I suggest to wait for the preliminary results of the official investigation. It's a matter of some weeks, if not days, and then we can have a definite, comprehensive and most reliable answer about the cause of this crash. Daniel (talk) 11:56, 24 March 2016 (UTC)
Resolved You are right, according to the latest media reports, reportedly based on the information from the Flight 981 flight recorders, the circumstances of these two crashes were identical and I restore the "See also" section with the link to Tatarstan Airlines Flight 363. Thank you. Daniel (talk) 07:11, 26 March 2016 (UTC)
Trim Runaway?
Reference 42 is a good one, somewhat hard to interpret through translation (as I must) but upon manual control resumption, pressing the trim button would not result in a big transient because "trim" (the stabilizer tailplane bias position) is a slowly accumulating bias. Barring some mechanical failure, it can't move fast. We need to understand if there was an autotrim function active during the autopilot operation. If something failed there, then the trim could have "wound up" to a large nose down value due to a small persistent error. In a simple mechanical autopilot, that error could be a nervous pilot pushing or pulling back unconsciously all the time. Knowing if that was possible here requires understanding how the autotrim is implemented in this autopilot (and I don't) because another possibility would be that trim does not run at all when the AP is engaged.
If autotrim WERE engaged, and if the control servos are stronger than the pilot then trim runaway could build up a stabilizer bias position too large to be overcome by strength of manual input to the elevator. I say "stronger" because only moments before the loss of control the AP WAS successfully trimming the aircraft against what was almost surely the very same stabilizer trim (bias) offset, so we need some explanation why the pilots couldn't also overpower the offset.
Speculation: if shear caused a minor stall, and if the elevator authhority were only slightly greater than the trim, then recovery would be very slow. Markrkrebs (talk) 10:17, 26 March 2016 (UTC)
Thanks for linking the document. I read closely and didn't see anything alarming about STS: maybe you can clarify your concern? A few pages before that, is a discussion of stabilizer trim, including "control column actuated stabilizer trim cutout switches" which may be telling. To me that implies the autotrim does actuate the stabilizer, does respond to elevator trim and is particularly designed to notice and disengage if that trim load is coming from the control column. ...which seems like a very solid design. Note also that trim "hat" (the knupfel from the russian article) input automatically disengages the autopilot, another proper design element. These elements are intended to preclude trim runaway. The article you linked does seem to say they can be overridden, leaving a chance for pilot error. Anyway to summarize I do not understant your complaint about STS: it would have been pulling, too, because speed was high. Markrkrebs (talk) 10:46, 26 March 2016 (UTC)
Amplifying: "...does respond to elevator trim loads..." Markrkrebs (talk) 10:47, 26 March 2016 (UTC)
Lost your comment. Did I delete it by accident? Sorry. Please re-add your comment. Markrkrebs (talk) 11:03, 26 March 2016 (UTC)
References have changed so this discussion no longer refers to 42 but instead 29, by Kondrashov, discussing the tailplane setting and cockpit quote "pull up." Markrkrebs (talk) 11:31, 26 March 2016 (UTC)
'... with 5,000 hours being the minimum required for a captain at Flydubai'
This may not be the case with promotions and it might not have been the case when Sokratous was promoted. In general, promotions are offered according to seniority and staff shortage. The airline may have set a minimum number of hours for promotion to a captain or it may not have. If it did, we don't know what that number is. A job listing for a direct hire is not a valid source; and, I venture, it's probably where the newspaper got their info from as well. 93.109.172.116 (talk) 10:56, 26 March 2016 (UTC)
- @93.109.172.116: 5,000 hours of total flying time is a minimum requirement for a captain's position in most of the major airlines. This piece of information is very important, as I have seen several media reports, which described Socratous as a "very experienced" captain. Capt. Sullenberger, who saved all the people on board in 2009 accident was described by media in the same words, as a "very experienced" captain. But he had logged 19,663 flight hours by the time of his accident. Even a first officer on the Sullenberger's plane had 15,643 flight hours, that is 2.6 times more than Capt.Socratous. Most of the readers are unaware of this and that is why I believe this piece of information is important, as it allows any reader to access the Socratous flying experinece more accurately. Daniel (talk) 12:23, 26 March 2016 (UTC)
- No, it isn't 5,000 hours as a general rule. I don't see what Sullenberger has to do with anything, or what the reading public might be able to gather from it, either. If you've not got definitive evidence Sokratous was required to complete 5k hours, I'll be removing it again later. 93.109.172.116 (talk) 12:37, 26 March 2016 (UTC)
- I support removing this info because it creates a wrong impression in a non-technical reader that the captain was somehow not skilled enough. --Anthony Ivanoff (talk) 12:25, 27 March 2016 (UTC)
Resolved I withdraw my objections. Daniel (talk) 13:33, 27 March 2016 (UTC)
Speed Trim System
The speed trim system (STS) is a speed stability augmentation system designed to improve flight characteristics during operations with a low gross weight, aft center of gravity and high thrust when the autopilot is not engaged. The purpose of the STS is to return the airplane to a trimmed speed by commanding the stabilizer in a direction opposite the speed change. The STS monitors inputs of stabilizer position, thrust lever position, airspeed and vertical speed and then trims the stabilizer using the autopilot stabilizer trim. As the airplane speed increases or decreases from the trimmed speed, the stabilizer is commanded in the direction to return the airplane to the trimmed speed. This increases control column forces to force the airplane to return to the trimmed speed. As the airplane returns to the trimmed speed, the STS commanded stabilizer movement is removed.
STS operates most frequently during takeoffs, climb and go-arounds. Conditions for speed trim operation are listed below:
• Airspeed between 100 KIAS and Mach 0.5
• 10 seconds after takeoff
• 5 seconds following release of trim switches
• Autopilot not engaged
• Sensing of trim requirement
http://www.737ng.co.uk/B_NG-Flight_Controls.pdf — Preceding unsigned comment added by 77.238.65.171 (talk) 10:59, 26 March 2016 (UTC)
Stall Identification
Stall identification and control is enhanced by the yaw damper, the Elevator Feel Shift (EFS) module and the speed trim system. These three systems work together to help the pilot identify and prevent further movement into a stall condition.
During high AOA operations, the SMYD reduces yaw damper commanded rudder movement.
The EFS module increases hydraulic system A pressure to the elevator feel and centering unit during a stall. This increases forward control column force to approximately four times normal feel pressure. The EFS module is armed whenever an inhibit condition is not present. Inhibit conditions are: on the ground, radio altitude less than 100 feet and autopilot engaged. However, if EFS is active when descending through 100 feet RA, it remains active until AOA is reduced below approximately stickshaker threshold. There are no flight deck indications that the system is properly armed or activated.
As airspeed decreases towards stall speed, the speed trim system trims the stabilizer nose down and enables trim above stickshaker AOA. With this trim schedule the pilot must pull more aft column to stall the airplane. With the column aft, the amount of column force increase with the onset of EFS module is more pronounced.
http://www.737ng.co.uk/B_NG-Flight_Controls.pdf
B737 Speed Trim System Bug
B737 Speed Trim System Bug was the reason for the crash of "Flydubai Flight 981" and "Tatarstan Airlines Flight 363". As I said to you Daniel, they test these systems in simulators, not in real field test. This bug act like a SUICIDE PILOT, when real pilots trying to 'pull up', it ill logic do exact opposite 'nose down' maneuver "to return the airplane to a trimmed speed" - this lead to continuously increasing negative angle of attack because GATHERING OF INFORMATION FROM REAL LIFE DEVICES is not like SIMULATION ONE. I think that the question "IS AUTOPILOT MUST TAKE CONTROL OVER PILOT IN EXTREME SITUATIONS LIKE STALL?" get its answer. — Preceding unsigned comment added by 77.238.65.171 (talk) 11:10, 26 March 2016 (UTC)
- The case with Tatarstan Airlines Flight 363 is very interesting one. I need to investigate it further, but as I remember, the final report ruled that it was a pilot's error, as he never done a go-around in real life before (only in training), traces of alcohol was discovered in his blood, etc. But one expert in the commission filed a "minority report" ("a special opinion"), which is unheard of in any air crash investigation in Russia or USSR. His opinion was published in Russian, alongside the official report on IAC's website. I didn't examine it thoroughly yet, but as I remember, this expert blamed some intrinsic mechanical failure of one of Boeing 737 systems in this crash. This expert was a representative of Federal Air Transport Agency (Russian analogue of FAA) in the commission. Daniel (talk) 12:55, 26 March 2016 (UTC)
- This will be Daniel huge scandal for Boeing and I have no doubt that they will try to cover it up. I hope that they have enough brain to realize, however, that if it happened again - someone will start asking questions. I have already started to harass AAIB - they will not withstand pressure if their competence is questioned. For years, there are disputes on whether to allow the autopilot to control planes in critical situations or not. Biggest manufacturers such as Boeing and Airbus trying surreptitiously to put pilot control under control by "semi-autopilot" systems like this STS and Airbus's Fly-by-wire. Thus, they make flights considerably more dangerous than PURE autopilot or manually control planes, because PILOTS ARE NOT FULLY AWARE WHAT EXACTLY IS THEIR CONTROL OVER AIRCRAFT and therefore are not fully aware of actions they can take in critical situations. I'm sure that the pilots of Flight 981 and Flight 363 are fully surprised when they do 'pull up' action and plane go down instead. In those 40 seconds, I doubt whether engineers who has created these systems would have guessed what was happening and how to get out of the situation in this short interval. Sometimes I'm surprised how the media use phrases "very experience", "not experience" if it has any relevance in these cases where the plane do what it should not and pilots knowledge are not matter at all - because what he must know is known only by few people in the world. The work of these systems is a well-kept secret. You can not find more than a few lines of information about them - basically superficial such. You take complex decisions in critical situations with minimum information - I do not know what an experienced pilot you must to be - to be able to handle it. Most worst, after such incidents - they take a few pilots and inserted them in such a hopeless situation in SIMULATOR and of course, most of them fail - a fraction manage to cope because of fraud (for example, some instructor give them seemingly insignificant additional information)and in END: Blame ALWAYS pilots because such technical illiteracy is widespread among them that companies need to punish them as they cut wages and make pointless courses to "increase" their professionalism.
- The scenario is repeated every time in the same way:
- Flight 363
- "regular violation of the crew members worlk-rest regime and vacation liability that could result in chronic-fatigue build and negatively effect the crew members performance;"
- Flight 981
- "Pilots ‘worked to death’: Flydubai whistleblower says fatigue-related crash predicted"
Full Russia-1 TV news report
For those Wikipedians, who do not speak Russian, here is a more detailed account of this TV report. I agree, that not all this information should end up in the article's body, but it might be useful for the editors of this article.
According to Russia-1 TV news report of 25 March, citing an undisclosed source in the air crash investigation commission, the CVR and FDR flight recordings revealed the following sequence of events. At 3:40:00 the captain made a decision to abort a second landing attempt, due to severe weather conditions, and to climb to flight level 50 (5,000 feet (1,500 m)). For the next 40 seconds the aircraft was climbing up, in the autopilot regime, with a 15 degrees angle. Before the aircraft reached the designated flight level, the captain disengaged the autopilot. Right after that, the aircraft began the nosedive.
It is unclear yet, why the captain decided to disable the autopilot, but according to one suggestion, the aircraft may have experienced the wind shear at that moment and the captain decided to manually level the aircraft. The moment the autopilot was disconnected, the tailplane, for some reason, has turned into a nosedive position. According to one suggestion, during turbulence, when the captain was cutting off the autopilot, he accidentally pressed the tailplane thumb controller, without realizing it. Another possibility is that the tailplane went into the nosedive position because of some unknown mechanical malfunction in Boeing 737.
The CVR, reportedly, recorded the following final words of the flight crew:
3:40:40 Don't worry, don't worry, don't worry.
3:40:45 Don't do that, don't do that, don't do that!
3:40:50 Pull up! Pull up! Pull up!
The pilots were pulling the aircraft's control columns, trying to level the aircraft with the help of elevators, without realizing that their efforts are futile, as the problem was caused by the wrong tailplane position.
For the last six seconds of the aircraft's dive (3:40:54-3:41:00), all that can be heard are "inhuman screams," the channel's source said. At 3:41:00 the aircraft impacted the ground.
The Interstate Aviation Committee didn't make any comments, regarding the information presented in the Russia-1 TV report. Daniel (talk) 16:30, 26 March 2016 (UTC)
- "According to one suggestion, during turbulence, when the captain was cutting off the autopilot, he accidentally pressed the tailplane thumb controller, without realizing it." According to other suggestion there was little probability two pilots of two different plane in almost the same circumstances to pressed the tailplane thumb controller accidentally.
- Stabilizer
- The horizontal stabilizer is positioned by a single electric trim motor controlled through either the stab trim switches on the control wheel or autopilot trim. The stabilizer may also be positioned by manually rotating the stabilizer trim wheel.
- Stab Trim Switches
- http://www.flaps2approach.com/journal/tag/b737-300-throttle-quadrant
- For example look where these switches are and how someone can activate them accidentally. And most important the activation of Stab Trim Switches is registered by FDR.
- https://img.planespotters.net/photo/230000/original/n73283-united-airlines-boeing-737-824wl_PlanespottersNet_230834.jpg
- P.s. As I told you Daniel, they have already started a campaign aimed to discredit pilots and blame them for this accident. How you think, is it very easy to get CVR data in such investigation? I can tell you, for example, that if some investigator spreed this information - he may pay for that with his life literally. A lawsuit against Boeing can cost BILLION to the company. No one inside can afford such thing without permission and access to this information is highly limited. They themselves spreed it to prepare society for their lies. — Preceding unsigned comment added by 77.238.65.171 (talk), Today
Stabilizer not moveable because of strong tailwinds 737-ALL
"BACKGROUND: The crew started the After Landing checklist when the aircraft was parked and the engines stopped. During the After Landing check, the crew moved the horizontal stabilizer to the “Aircraft Nose Down” (AND) position. When the stabilizer came to 4 units, it stopped (correctly) and the Stabilizer Trim Motor could not move up or down electrically. The problem could not be solved by telephone so Technicians flew to the station. They started the hydraulic pumps and set the FLAP to the NOT UP position. Then the Stabilizer Trim Motor operated correctly.
NOTE: The movement of the Stabilizer Trim Motor depends on the Flap position. When the Flap is: UP – Stabilizer Trim movement is approximately 4 -17 units. NOT UP – Stabilizer Trim movement is approximately 0 -17 units.
PROBLEM: When the stabilizer moved up (AND), a strong tailwind also moved the elevator up (Aircraft Nose Up) (ANU). This caused the column cutout switches to disconnect the electrical power to the Stabilizer Trim Motor.
WHAT HAPPENED: The Elevator Control Column was in the ANU position and the stabilizer was commanded to the AND position. . Because the two commands oppose each other, the column cutout switches disconnected the Stabilizer Trim Motor.
ACTION 1: If you think that this problem has occurred, Start the EMDP, system A or B The Elevator Control Column moves to the neutral position Set the FLAP to the NOT UP position Use the Stabilizer Trim Switches to move the Stabilizer up and down.
ACTION 2: Also, to see if the Stabilizer Trim motor operates correctly, set the STAB TRIM OVERRIDE switch to OVERRIDE (This bypasses the column cutout switches). Use the Stabilizer Trim Switches to move the Stabilizer up and down.
REFER TO: SDS 27-41
NOTE: This event was on a B737-6/7/8/900 but could even occur on the B737-3/4/500 because the system is similar. The B737-3/4/500 has only one control cutout switch."
http://www.sjap.nl/stabilizer-not-moveable-because-of-strong-tailwinds-737-all/
- As you can see the reason for the crash of Flights 981 and 363 already is known. Obviously STRONG WINDS and STABILIZER TRIMMING on B737-ALL are not good combinations and can lead to failure that can CRASH PLANES exactly in phase on "GOING AROUND" procedure in windy weather! Question now is Why Boeing continue to lie, and trying to put pressure on investigators to blame pilots?
— Preceding unsigned comment added by 77.238.65.171 (talk) 08:11, 27 March 2016 (UTC)
Wikipedia article mentioned in media
This Wikipedia article was mentioned in the low-profile Russian-language news reports (1, 2), reporting about a conspiracy theory of one blogger, that the crash in Rostov didn't actually happen. As a proof, this guy pointed also on the fact, that Wikipedia article about the crash appeared online three hours after the accident: "How can you write an article only three hours after the tragedy?", he says. Daniel (talk) 15:00, 27 March 2016 (UTC)
- Well, that's amusing! ...and sad. 93.109.172.116 (talk) 15:17, 27 March 2016 (UTC)
- "How can you write an article only three hours after the tragedy?" :-))) No,I read somewhere that this article was write BEFORE crash, but when "he" or "they" realizing their error about Time Zone, feeling embarrassed by their stupidity, they change version as "only three hours". 77.238.65.171 (talk) 17:11, 27 March 2016 (UTC)
While 'trying to switch off the autopilot'
Could you point me to where this connection was made in the Russian report? 93.109.172.116 (talk) 15:49, 27 March 2016 (UTC)
- Here is the text of the original TV report: "Почему включился в режим пике стабилизатор — вопрос. Он приводится в действие кнопкой, которую пилоты называют "кнюпель". То есть во время турбулентности командир, переходя в ручной режим, мог случайно зацепить этот кнюпель, и не заметил". Do you know Russian? - Daniel (talk) 16:27, 27 March 2016 (UTC)
- No, I do not. But I was hoping I could get the gist of it 'cause a lot appears to have been lost in translation. Thanks. 93.109.172.116 (talk) 18:43, 27 March 2016 (UTC)
- I'll try to translate it as close to the source, as possible: Why the stabiliser switched to the dive mode is the question. It is activated by a button, which the pilots call a "knüppel". So during the turbulence the captain, going into the manual mode, may have accidentally hooked this knüppel and did not notice it. - Daniel (talk) 20:52, 27 March 2016 (UTC)
- Thank you. 93.109.172.116 (talk) 08:54, 28 March 2016 (UTC)
- I'll try to translate it as close to the source, as possible: Why the stabiliser switched to the dive mode is the question. It is activated by a button, which the pilots call a "knüppel". So during the turbulence the captain, going into the manual mode, may have accidentally hooked this knüppel and did not notice it. - Daniel (talk) 20:52, 27 March 2016 (UTC)
- No, I do not. But I was hoping I could get the gist of it 'cause a lot appears to have been lost in translation. Thanks. 93.109.172.116 (talk) 18:43, 27 March 2016 (UTC)
Why this "inadvertently trim switch on his yoke" theory don't hold
First, because FDR data indicate such PRESSING of switch trim buttons on the Yoke. It would not be an assumption BUT proven fact that will determine the cause of the crash IMMEDIATELY and INDISPUTABLY. In practice, the investigation will end.
Second, and if the AUTOPILOT DISENGAGE button on the Yoke as pressed too (which can also be proven by FDR data) - it will mean only one thing:
DELIBERATE PRESSING ON AUTOPILOT DISENGAGE AND TRIM SWITCH BUTTONS IN SEQUENCE - I.E. PROVEN SUICIDE!
P.s. Of course, such an option is not excluded (I told about it in previous comment, еven I suppose that the suicide pilot can play the role of unsuspecting man in front of CVR). This will be some sort of a suicide with insurance fraud goal. But not very smart way to do it.
P.p.s Accidental pressing these buttons in this sequence of events is almost excluded because they are so designed to prevent it. You must move your THUMB consciously and in specific way.
http://1.bp.blogspot.com/-L-WZkhPkqas/TVOHfzanegI/AAAAAAAAAjk/S-ZrpNl2ezo/s1600/CaptControlYoke.JPG
77.238.65.171 (talk) 06:56, 28 March 2016 (UTC)
Alaska Airlines Flight 261
Video of jackscrew failure sequence:
"... IMMEDIATELY AFTER AUTOPILOT WAS DISCONNECTED BY THE FLIGHT CREW...THE STABILIZER TRAVEL FROM ITS JAM POSITION TO...NOSE DOWN POSITION..."
https://en.wikipedia.org/wiki/Alaska_Airlines_Flight_261#First_dive_and_recovery
77.238.65.171 (talk) 08:30, 28 March 2016 (UTC)
New leak
See [2], though maybe we should wait before adding it to the article. 93.109.172.116 (talk) 09:56, 28 March 2016 (UTC)
- I've seen it this morning. The original Kommersant article is here. The author of this article cited an unnamed source "close to investigation", but didn't state that his source was actually a member of the IAC's investigation team, as was specifically mentioned in the Russia-1 TV report, refering to their source. In effect, he is contradicting the Russia-1 TV report, saying that the climb after the second aborted landing was done by the flying pilot, not on autopilot. According to Kommersant, during a climb a pilot pulled the control stick up too much, causing a stall break and an uncontrollable nosedive. They say, their version explains the words from the CVR, which were revealed earlier in the Russia-1 TV report: "don't worry", "don't do that" and "pull up". According to Kommersant, the second pilot realised the stall danger and attempted to prevent it by pushing his own control column to bring the Boeing’s nose down, while the flying pilot was yelling at his colleague not to do it. This article does not provide any new factual information, as was in the case of Russia-1 TV report. It merely tries to explain the words on the CVR, even without a claim that this information is coming from the member of the investigation team. So I would consider it a pure speculation and agree that we should wait for the information from the IAC. - Daniel (talk) 10:55, 28 March 2016 (UTC)
- unnamed source "close to investigation" - mean that IAC is started to spread rumors. Before time I have complain in European Commission asking them to start an investigation against Bureau of Enquiry and Analysis for Civil Aviation Safety because internal "unnamed source close to investigation" has released information to the media before they made a statement or report - something they have no right to do. "Unnamed source close to investigation" quickly became officially BEA to not start lawsuit against them. These informal and illegal statements are Statistical Survey refining their lies in advance. In simple words WHAT IAC SAY CAN NOT BE BRING BACK, THEREFORE THEY FIRST PLACE THEIR UNOFFICIAL LIES IN THE MOUTH OF "UNNAMED SOURCE CLOSE TO INVESTIGATION", THEN CHECK WHAT WILL BE THE RESPOND, BEFORE OFFICIAL STATEMENT. And such SEVERE STALL SITUATION WAS NEVER COME ON FLIGHT 981, this can easily be demonstrated even with data from FlightRadar24, and such lie can not be easy push to the media by IAC because this will be bring number of FDR DATA REQUESTS. Don't buy it. Cheap sensationalism. Boeing will eat the DICK this time - and there will be not salvation for them while not admitting their guilt. 77.238.65.171 (talk) 11:20, 28 March 2016 (UTC)
'Investigators from the Russian Investigative Committee participate in all actions of the IAC investigation. If IAC finds somebody to blame- RIC will prosecute them, according to law'
In what way do they participate? The IAC does not look for people to 'blame' - that's a gross misunderstanding of the purpose of an air accident investigation. 93.109.172.116 (talk) 21:49, 28 March 2016 (UTC)
- Investigators from the Investigative Committee of Russia (I abbreviate it to ICR) accompany the IAC experts in all their investigative actions. The ICR representatives participate in the meetings of the IAC. They will also sign the final report of the IAC investigation. If the IAC commission in its evaluation of the actions of the ATC, meteorological services or any other staff members, will find any negligence, the ICR will prosecute those people according to the law. - Daniel (talk) 22:17, 28 March 2016 (UTC)
- Do you have a source for any of this? I fail to see why federal investigators would be meddling in the safety investigation. I've skimmed the Tatarstan crash report and there appears to be a solitary mention of the ICR on p. 12; if I'm understanding it correctly, the ICR conducted some sort of preliminary investigation, but they don't even bother to say what their findings were. 93.109.172.116 (talk) 00:06, 29 March 2016 (UTC)
- Look even on the protocol of the IAC Commission final meeting for the case you just mentioned. Mr.Nikiktin (Никитин А.А.) on the list of the participants - is a representative of the ICR (представитель СК РФ)!!! Why do you think, that other editors have "gross misunderstanding" of the things, they write about??? Do you really believe that being a pilot from Cyprus makes you a great expert in the air crash investigation process in Russia? Let me work on this article, trying to improve it, instead of wasting time, counter-acting your accusations that I have "gross misunderstanding" in the air crash investigation process. - Daniel (talk) 03:17, 29 March 2016 (UTC)
- Do you have a source for any of this? I fail to see why federal investigators would be meddling in the safety investigation. I've skimmed the Tatarstan crash report and there appears to be a solitary mention of the ICR on p. 12; if I'm understanding it correctly, the ICR conducted some sort of preliminary investigation, but they don't even bother to say what their findings were. 93.109.172.116 (talk) 00:06, 29 March 2016 (UTC)
This talk page in the Russian blogosphere
Excerpts from the discussion on this talk page, namely several comments about different versions of this crash made here by user 77.238.65.171, have been translated into Russian and published in the Russian blogosphere. The author of the blog said, that he has sent to AAIB a request for information, whether Emil Enchev, who is writing here as user 77.238.65.171, participated in the investigation of Germanwings Flight 9525, and promised to publish the AAIB reply in his blog. - Daniel (talk) 22:00, 28 March 2016 (UTC)
- "participated in the investigation of" - He is NOT participated in Investigation of Flight 9525 - and user is not mention such thing. He don't work for AAIB. AAIB don't participated in Flight 9525 case too. He only informed them about the reason for the crash BEFORE any other to know about it. Obviously Russian bloggers very like to ask questions before understand them. You can ask and FlightRadar24 too. Bye the way, yesterday I informed AAIB, that I will try to initiate lawsuit against them for CORRUPTION, CRIMINAL CONSPIRACY WITH BOEING, TAMPERING WITH RESULTS OF THE INVESTIGATION in the case of Tatarstan Airlines Flight 363.
- Daniel how to see where I mention that I PARTICIPATED IN THE INVESTIGATION of Flight 9525, because I do not think I said that. Do you mind to quote here this thing.
- And Daniel what about you to quote here my old comments as EnchevEG in Wiki Flight 9525 talk page and DATE when they was write or to ask moderators for them. I have feeling that AAIB will make big mistake AND I WILL FUCK THEM. Soon you will find out the truth about INMARSAT FAKE THEORIES and how they use them for drag millions of dollars in fruitless searching of MH370 where it is not. Or how INMARSAT stop manufacture of ACARS to do test their FAKE "GROUNDBREAKING" MATH.
- And I wait this RUSSIAN IDIOT to past here AAIB answer as HE WAS PROMISED. One week and no answer yet.
- And Daniel what about you to quote here my old comments as EnchevEG in Wiki Flight 9525 talk page and DATE when they was write or to ask moderators for them. I have feeling that AAIB will make big mistake AND I WILL FUCK THEM. Soon you will find out the truth about INMARSAT FAKE THEORIES and how they use them for drag millions of dollars in fruitless searching of MH370 where it is not. Or how INMARSAT stop manufacture of ACARS to do test their FAKE "GROUNDBREAKING" MATH.
- Daniel how to see where I mention that I PARTICIPATED IN THE INVESTIGATION of Flight 9525, because I do not think I said that. Do you mind to quote here this thing.
- "participated in the investigation of" - He is NOT participated in Investigation of Flight 9525 - and user is not mention such thing. He don't work for AAIB. AAIB don't participated in Flight 9525 case too. He only informed them about the reason for the crash BEFORE any other to know about it. Obviously Russian bloggers very like to ask questions before understand them. You can ask and FlightRadar24 too. Bye the way, yesterday I informed AAIB, that I will try to initiate lawsuit against them for CORRUPTION, CRIMINAL CONSPIRACY WITH BOEING, TAMPERING WITH RESULTS OF THE INVESTIGATION in the case of Tatarstan Airlines Flight 363.
— Preceding unsigned comment added by 77.238.65.171 (talk) 05:28, 29 March 2016 (UTC)
@user:77.238.65.171 Can you read understand and take on what is written at WP:NOTSOAPBOX your multiple entries here in my opinion go way over that line. Also it is best to avoid using ALL CAPS in exchanges it tends to have the opposite affect you are actually wanting, SHOUTING helps no one in building a reliable encyclopedia. Thanks Andrewgprout (talk) 05:47, 29 March 2016 (UTC)
- Andrewgprout I do not give a shit about the rules of wiki. If something you do not like delete or fix as you usually do here.77.238.65.171 (talk) 05:58, 29 March 2016 (UTC)
- @user:77.238.65.171 I really believe you should not answer like that to a reasonable and polite request. - Daniel (talk) 06:55, 29 March 2016 (UTC)
Daniel why you mention this Russian blogger here on the first place?! I understand if he received a reply from AAIB and publish it here, but I don't understand why you do it? "You are now famous in Russia" Do you really think that I want to become famous?! If I want it, i will NOT delete my comments for example here http://physicsbuzz.physicscentral.com/2014/03/how-did-inmarsat-really-find-flight.html and it would work. Do you know that I'm the biggest 'FAN' of INMARSAT, probably the only one from whom Inmarstat afraid? Ask and them too if you want. But please ask questions in right manner. I'm Bulgarian, and my English is not perfect, but even that is not enough I to say that I'M PART FROM ANY INVESTIGATION OFFICIALLY. You are Russian probably. If you don't understand my English, simply ask me, and I will try to clarify what I mean. By the way I'm the man who tell JACC that the signals from Towed Pinger Locator are not from MH370 but from TPL itself one month before they announce it. Ask them too. I wait you to start asking question to them, because I wait day when they will FUCK THEMSELVES with LIES in WRITTEN FORM, because I really like to keep correspondence :-) But I'm sure that most probably, for this reason, they will not answer you at all. They are some crafty and corrupt Mouses - do not wait they to go alone in the light. 77.238.65.171 (talk) 06:35, 29 March 2016 (UTC)
- @user:77.238.65.171 When I sent you a message "You are now famous in Russia :-)", I wanted to cheer you up. Sorry if it did upset you. I found it very amusing that somebody in Russia not only reads what we write here in the talk page, but even translates it and publish in their own blogs. Nobody is citing me, though, only you :-( And I was really surprised that this blogger not only published the comments from here, but even went as far as writing to AAIB with an enquiry - Daniel (talk) 06:53, 29 March 2016 (UTC)
- But I'm not surprise that he not waiting for an answer from AAIB. As I said I'm surprise that you mention it here without need from that because this Russian idiot is trying to make me impostor. By the way I understand Russian too. Whatever77.238.65.171 (talk) 07:44, 29 March 2016 (UTC)
@user:77.238.65.171 You asked me to find your quote about Flight 9525. I believe it is here, where you said "I'm the man who solve the case of Germanwings Flight 9525 under 1 hour after crush, when investigators have no idea what happen and where they are on earth. If you want ask AAIB, my name is Emil Enchev. Now we wait one-two day to see even I speculate or not" - Daniel (talk) 06:43, 29 March 2016 (UTC)
- And i think that is clearly enough. "i'm the man who solve" and "when investigators" - does both parts not opposed enough to understand that I'm not part of the SET "INVESTIGATORS"?! May be "solve the case" is confusing part but I don't really know how to tell it in other way. What is that word when someone tell exact reason for the crash if not "solve"?! Its very interesting, why this Russian moron, don't see history on Wiki GW 9525 talk page and date on it?! Is this history only for moderators, I don't understand. I really don't understand almost nothing from this WIKI things. You can ask AAIB, are they informed by Emil Enchev what is the reason for the crash of GW 9525, long before investigators to know it. As I said AAIB was not part of this investigation, but I doubt that they are not informed BEA about my hypothesis. Obviously they don't bother to answer him, because after that may be must answer to more awkward questions like "Why after Emil Enchev informed them about this threat they release this https://www.youtube.com/watch?v=SHvfYQXx7Go when the same person expressly warned them not to do it?" You ask me "Why you don't heard my name to be mention anywhere?" The short answer are two: 1. Because I don't want it. 2. Because they don't want it. 77.238.65.171 (talk) 07:12, 29 March 2016 (UTC)
- @user:77.238.65.171 I suggest, just forget about it. But please do not forget what User:Andrewgprout have requested above. - Daniel (talk) 07:17, 29 March 2016 (UTC)
- I once tried to get out of the shadow and they crucified me (i was a plagiarist and so on) :-)) Since then I realized that these things with the fame are not for me. I can fucked all US NSA with a hundred lines of code do you think that they will humiliate me publicly for one or two crashed planes?! They can just keep quiet and nothing more. They know that plane crashes are only strange hobby of this Asperger's Autistic :-) but real think that he work are more dangerous for them. P.s. Now to see how long my comments will be on this page. http://mymathforum.com/number-theory/12131-enchev-s-conjecture-goldbach-s-conjecture-twin-pairs.html77.238.65.171 (talk) 07:30, 29 March 2016 (UTC)
- @user:77.238.65.171 I suggest, just forget about it. But please do not forget what User:Andrewgprout have requested above. - Daniel (talk) 07:17, 29 March 2016 (UTC)
Hijacked EgyptAir flight MS181: Live updates
Question: Was hijacking of EgyptAir flight MS181 part from Flydubai Flight 981 investigation?
Today this is most effective way to do Air Accident Investigations. Golden rule: If questions about a disaster that you investigate become too uncomfortable you can always make hijacking to answer them.
For example, Have you ever wondered is any logic in the fact that Investigators always include experts from the company that make the crashed plane? Like the criminal investigator to invite the killer who do killing to take part in his own investigation.
77.238.65.171 (talk) 07:56, 29 March 2016 (UTC)