Go Back  PPRuNe Forums > Flight Deck Forums > Rumours & News
Reload this Page >

Tu 134 crashed in Russia

Wikiposts
Search
Rumours & News Reporting Points that may affect our jobs or lives as professional pilots. Also, items that may be of interest to professional pilots.

Tu 134 crashed in Russia

Thread Tools
 
Search this Thread
 
Old 23rd Jun 2011, 12:47
  #41 (permalink)  
 
Join Date: Apr 2010
Location: St. Petersburg
Posts: 270
Likes: 0
Received 0 Likes on 0 Posts
With the nuclear men - I think nah. Who would bother. It is not a strange co-incidence, as if there are many of them left in the country who can build a nuclear power station :o)) All old Soviet anyway, not much choice :o) There was some equipment bought for Petrozavodsk, which they flew to check, what is bought. Ordinary.

One would say don't fly 31 year old TU, that spent 1.5 years standing still before the flight, and is not on his regular flight, on tops, but is fished out from nowhere last minute replacing the line standard one (Bombardier), in fog, about which the control tower man told his wife going to work
"I won't allow tonight to land even a crow", with the pilot who hasn't been on holidays for 3 years doing charter flights, and other interesting details emerging.
Alice025 is offline  
Old 23rd Jun 2011, 14:55
  #42 (permalink)  
 
Join Date: Apr 2010
Location: St. Petersburg
Posts: 270
Likes: 0
Received 0 Likes on 0 Posts
...

Alcohol found in blood of Aman Ataev, 50-yr old Navigator.

...
Alice025 is offline  
Old 23rd Jun 2011, 18:24
  #43 (permalink)  
 
Join Date: Mar 2009
Location: us
Age: 63
Posts: 206
Likes: 0
Received 0 Likes on 0 Posts
...this story has been denied by authorities saying they haven't run any such tests yet
vovachan is offline  
Old 23rd Jun 2011, 20:43
  #44 (permalink)  
 
Join Date: Oct 2002
Location: London UK
Posts: 7,648
Likes: 0
Received 18 Likes on 15 Posts
Originally Posted by Kulverstukas
UPD:

This was not scheduled flight, regular carrier on this line is RusLine but they use Bombardier CRJ-200 which can take only 50 paxes vs 68 of Tu134. RusAir is charter and business carrier.
I am presuming, from piecing elements together, that this was actually the RusLine flight No. 243 daily schedule from Moscow (and operating pretty much on time), but the regular CRJ had been replaced on this day by a subchartered Tu134 from RusAir (any connection ? Possibly not).
WHBM is offline  
Old 23rd Jun 2011, 20:48
  #45 (permalink)  
Thread Starter
 
Join Date: Sep 2005
Location: Moscow, Russia
Posts: 1,011
Likes: 0
Received 0 Likes on 0 Posts
the regular CRJ had been replaced on this day by a subchartered Tu134 from RusAir
And I have no information if this crew flew this destination before. Also there is rumour (from crew relatives) that they was not much flew together (Cpt was new to the company).

Also this airfield is (as Smolensk, agian ) half military.
Kulverstukas is offline  
Old 23rd Jun 2011, 22:12
  #46 (permalink)  
 
Join Date: Apr 2010
Location: St. Petersburg
Posts: 270
Likes: 0
Received 0 Likes on 0 Posts
vovachan,
I am very sorry, and very glad it isn't so. Also read the Investigaion committee denies this media "news".
Alice025 is offline  
Old 30th Jun 2011, 12:08
  #47 (permalink)  
 
Join Date: Nov 2007
Location: Europe
Posts: 24
Likes: 0
Received 0 Likes on 0 Posts
Unhappy CFIT

Typical case: non-precision approach, poor visibility, descent below MDA, crash as a result. Not much to talk about
DeRodeKat is offline  
Old 30th Jun 2011, 14:54
  #48 (permalink)  
Thread Starter
 
Join Date: Sep 2005
Location: Moscow, Russia
Posts: 1,011
Likes: 0
Received 0 Likes on 0 Posts
Interfax today post that all CVR was fully decoded. But most inetersting part is "as was mentioned before, CPT was not in the cabin at the time of incident".
Kulverstukas is offline  
Old 19th Sep 2011, 10:00
  #49 (permalink)  
 
Join Date: Aug 2008
Location: est
Posts: 77
Likes: 0
Received 0 Likes on 0 Posts
Final report published (in Russian).

http://www.mak.ru/russian/investigat...t_ra-65691.pdf

"The reason for the crash of the Tu-134A RA-65 691 during the approach in the conditions worse than weather minimums of the airfield, aircraft and Captain, was the failure of the crew to make the decision to go-around and descending the aircraft below the minimum safe altitude in the absence of visual contact with approach lights and landmarks, which led to a collision with the trees and the ground in controlled flight.
Contributing factors were:
- Poor communication in the crew and resource management (CRM) from the Captain in the performance of the approach, which expressed in the subordinance of the Captain to the navigator's instructions, who was in a mild degree of alcoholic intoxication, and the missing of any activity of the FO on the final stage of the emergency flight.
- Flight navigator being in a state of mild intoxication.
- Unjustified weather forecast 18:00 06/20/2011 03:00 06/21/2011 and the forecast for landing from 19:00 to 21:00 06/20/2011 by height of cloud, visibility and severe weather - fog, as well as the discrepancy transferred to the crew for 30 or 10 minutes before the landing of the weather at the airport Petrozavodsk actual weather that occurred at the time of SARS in the OMB-LMM INC = 12 °.
- The failure of the crew to check the ARC and other devices for integrated control of aircraft on final, while using information navigator satellite navigation system KLN-90B (in violation of the Flight Manual Supplement for the Tu-134 (see Section 4, paragraph 0.11)). "
liider is offline  
Old 19th Sep 2011, 11:30
  #50 (permalink)  
 
Join Date: Aug 2008
Location: Thessaloniki, GRECE
Age: 41
Posts: 67
Likes: 0
Received 0 Likes on 0 Posts
Contributing factors were:

- unsatisfactory crew resource management by the commander who effectively removed the first officer from the control loop in the final stages of the accident flight and who subordinated himself to the navigator showing increased activity however in the state of mild alcoholic intoxication.

- the navigator was in the state of mild alcoholic intoxication



I wonder why everyone yells when some people shout the obvious about drunken Russian pilots.
Christodoulidesd is offline  
Old 19th Sep 2011, 13:05
  #51 (permalink)  
pee
 
Join Date: Feb 2005
Location: Finland
Posts: 590
Likes: 0
Received 0 Likes on 0 Posts
Precisely, 0,81‰. Much too much generally speaking, maybe not enough for him?
pee is offline  
Old 19th Sep 2011, 14:09
  #52 (permalink)  
 
Join Date: Sep 2011
Location: 40 North 75 West
Posts: 16
Likes: 0
Received 0 Likes on 0 Posts
Percent Blood Alchohol Units Question

0,81‰
I presume that's the equivalent to .08% used in the US. Note the single zero in the denominator versus the double zero in the published report. That's generally the legal limit in the US for driving an automobile.
I think you would be dead at 0.8% blood alcohol content.
???
SLF305 is offline  
Old 19th Sep 2011, 14:31
  #53 (permalink)  
 
Join Date: Mar 2009
Location: us
Age: 63
Posts: 206
Likes: 0
Received 0 Likes on 0 Posts
yes this ‰ is the "per mil" sign, which is is 1/10 of a percent
PS:
.08 BAC may be borderline legal under the very generous US law but driving in this condition is NOT a good idea

Last edited by vovachan; 19th Sep 2011 at 14:55.
vovachan is offline  
Old 19th Sep 2011, 17:44
  #54 (permalink)  
 
Join Date: Jan 2003
Location: Southampton
Posts: 859
Received 40 Likes on 19 Posts
Russian air crash navigator was drunk

One of the pilots at the controls of a Russian passenger plane that crashed in June killing 47 people was drunk on the job, an investigation has found.
Poor journalism from The Telegraph Russian air crash navigator was drunk - Telegraph. I don't think that it's too difficult to find out the difference between a pilot and a navigator.
Saintsman is online now  
Old 19th Sep 2011, 18:10
  #55 (permalink)  
 
Join Date: Jul 2005
Location: btw SAMAR and TOSPA
Posts: 566
Likes: 0
Received 0 Likes on 0 Posts
Bendix KLN90B

setup by a mildly intoxicated navigator for final approach
threemiles is offline  
Old 19th Sep 2011, 18:37
  #56 (permalink)  
 
Join Date: Mar 2007
Location: south east UK
Posts: 375
Likes: 0
Received 0 Likes on 0 Posts
Less than three months to final report. Makes you wonder why it takes others so long.
Because the others do it properly and don't just look for the superficial causes.

yeah, drunk navigator, pilot bust minimums causes crash. end-of. what a load of tosh.

What about the systems that let those people be there with that attitude? what about the society that thinks drinking on the job is normal? etc etc etc.

A decent air accident investigation system that finds the real systemic causes and a culture and society that addresses them is why most of Europe, the US and others have a very good aviation safety system.
Russia has none of those attributes and has the worst, or very close to the worst, aviation safety record on the planet.
I utterly detest the following phrase as its used by all the elf-and-safety idiots but "safety is no accident" is a fairly relevent phrase.
757_Driver is offline  
Old 19th Sep 2011, 19:50
  #57 (permalink)  
 
Join Date: Mar 2009
Location: us
Age: 63
Posts: 206
Likes: 0
Received 0 Likes on 0 Posts
The report is actually quite revealing. The captain had a hard landing classified as an incident for which he was supposed to be busted down to f/o but in the end he just quietly resigned with a clean record. Found another job, new employer none the wiser. The medical pre-flight check which might have caught the navigator, happened only on paper.
vovachan is offline  
Old 20th Sep 2011, 06:10
  #58 (permalink)  
 
Join Date: Jun 2009
Location: USA
Posts: 64
Likes: 0
Received 0 Likes on 0 Posts
Speed of Accident Reports

Less than three months to final report. Makes you wonder why it takes others so long.
We seem to be regressing.

I was recently struck by how quickly the accident report of Northwest 2 was issued in 1938. It involved a brand-new Lockheed Super Electra that lost the upper parts of its vertical stabilizers near Bozeman, MT, due to flutter, and crashed in a flat spin. The investigators were confronted with the proverbial smoking hole, yet the final report was presented to the Bureau of Air Commerce only 19 days after the accident.

During that interval, the investigators made a site visit, identified that components were missing from the accident scene, interviewed eye witnesses, collected data on the flight and the crew, oversaw a series of tests at the manufacturer to confirm the suspicion that flutter was the cause, developed a correction with the manufacturer and tested it, held four days of public hearings, agreed on a cause, and wrote the report.

This was before CVRs, FDRs, computer models, entrenched politics, bureaucracy and lawyers. I guess life was simpler in those days.

Last edited by ST27; 20th Sep 2011 at 12:29.
ST27 is offline  
Old 23rd Sep 2011, 20:31
  #59 (permalink)  
 
Join Date: Jun 2002
Location: Orlando, FL, USA
Posts: 108
Likes: 0
Received 0 Likes on 0 Posts
Sorry to be so uninformed but would someone please explain to me what a "navigator" is on a Russian airliner. Where does he sit, what are his qualifications/training, what is his authority with relation to the Captain? What exactly does he do? Why is this person necessary at all?
surplus1 is offline  
Old 23rd Sep 2011, 22:05
  #60 (permalink)  
 
Join Date: Jan 2008
Location: Herts, UK
Posts: 748
Likes: 0
Received 0 Likes on 0 Posts
We seem to be regressing.

I was recently struck by how quickly the accident report of Northwest 2 was issued in 1938. It involved a brand-new Lockheed Super Electra that lost the upper parts of its vertical stabilizers near Bozeman, MT, due to flutter, and crashed in a flat spin. The investigators were confronted with the proverbial smoking hole, yet the final report was presented to the Bureau of Air Commerce only 19 days after the accident.

During that interval, the investigators made a site visit, identified that components were missing from the accident scene, interviewed eye witnesses, collected data on the flight and the crew, oversaw a series of tests at the manufacturer to confirm the suspicion that flutter was the cause, developed a correction with the manufacturer and tested it, held four days of public hearings, agreed on a cause, and wrote the report.

This was before CVRs, FDRs, computer models, entrenched politics, bureaucracy and lawyers. I guess life was simpler in those days.
Must say, the very same thoughts struck me when over a year after the BA38, 777 Heathrow threshold arrival... RR still hadn't developed a new FOHE by then. During the war they produced a new version of the Merlin nearly every 3 months... and even quicker when the FW190 was chasing Spit Vs all over the sky.

Last edited by HarryMann; 25th Sep 2011 at 23:59.
HarryMann is offline  


Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.