This is obviously the most interesting bit. If this really came from 9268, then maybe the stress caused the non-flying pilot to accidentally press the transmitter button. Or was this a call from a shocked tower controller watching the plane dash towards the end of the runway?

flyflyflyIts calls not from controller of Tower or Precision - i'm sure! Different voices and sound of noise. And its not voice from PNF.I think that was calls from RWZ near end of the runway (because calls from begining of the runway was not able to recieved by feed reciever - see calls from IFly) or other aircraft/technical staff from the ground.

Hi, Happy new year to everyone.I was wondering, and maybe it is just a coincidence, but I can’t find any logical explanation to the flight data of 9268. As recorded by “Flightradar24.com” RA-9268 was 17km/10,5miles from UUWW/VKO doing 176kt/326km.h. then 6km north of the runway he was at 131kt/243km.h. which I gather is normal, but then 2km from touchdown on rwy19 he is again doing 143kt/265km.h. Naturally I first suspected some kind of inaccuracy, but neither in VKO or in any other airport (I checked many other flights) does the plain speedup shortly before landing. That is not, except if he is performing a missed approach, which the communication recorded by Live ATC does not presume. Maybe they were throttling the craft after suffering a slump due to sudden tail wind? The wind was 260. Or is that to wild a presumption. In any case the Russians say- the craft suffered a zhestkaia pasadka (Hard landing) which could suggest the unexpected speed of 143kt was not an inaccuracy. The majority of aircrafts, tu204 including, read aprox. 125 to 133 and the 9268 was empty and very light.A

METAR reported gusty wind conditions at the time, which alone could explain quick changes of (ground) speed. But even if the approach wasn't perfect and they were a little fast and maybe touched down a little late (as some people claim in other forums), that still wouldn't explain why they overran with such enormous speed. It was a very experienced crew - a basic flying mistake alone seems just too unlikely to trap them in such a terrible accident. Much more likely they were facing a massive problem they had never experienced before - and couldn't solve/comprehend within the few seconds of their landing roll.

Probably the best current guess is a connection to the TU204 advisory which Rosaviatsia issued on Dec 31st (two days after the accident), requiring pilots to keep thrust at idle for 2 seconds after deploying thrust reversers, and to double check yellow/green "thrust reverser unlocked" lights before advancing throttles to the "max reverse thrust" setting (see aviation herald link above).

Also, some days before the event, there was a TU204 maintenance advisory due to gear WOW (weight on wheels) switch failure issues.

Both combined could trigger a terrible situation: pilot selecting reverse thrust / thrust reversers not deploying due to failed WOW switches (which keeps the reversers locked to avoid airborne deployment) / pilot applying "max reverse thrust" anyway (now resulting in massive forward thrust instead) while wheel brakes were applied to decelerate (wheel brakes are not locked by missing WOW switches). This would also be consistent with the crash video, where spoilers do not seem to be deployed (would also be locked down by a missing WOW signal).

There's no official confirmation though, that the thrust reverser advisory is connected to the Moscow crash at all. So, the timing of this could be pure coincidence - or just be precautionary...

Other T204 Aircraft in the Redwings fleet are having issues with thrust reversers not functioning correctly. This is pertaining to T204 RA-64049, sister to RA-64047, the aircraft lost in the crash. RA-64049 had two issues with reversers with-in a 9 day period.

No indication of any malfunction, like faulty WOW switches. Instead, they just never got enough pressure on both main landing gear struts at the same time (very light aircraft, fast landing, strong crosswind), so the automatic spoilers didn't trigger and thrust reverser deployment was blocked. They immediately moved thrust levers to "max reverse thrust" anyway (without waiting for confirmed reverser deployment), resulting in 90% forward thrust. They applied wheel brakes, but hardly decelerated at all.