FATS check... can't forget the FATS check!!!
the speeds were dumped out when they changed runways.I think they didn't set v-speeds, and then bro rotated too early (thusly, didn't guess the proper v speed), and then when the plane didn't fly how he expected it, he crapped his pants, landed, and performed a tail strike on landing.
The tail strike should have been obvious. If things were screwy in the air because the plane was too slow, then you're obviously going to hit the tail.
Well done, overall.
I don't think they purposefully took the runway without having data in. More so, they had passed that point in the checklist, runway switched, data dumped, message was cleared on mcdu without actually checking. Took off in flx with no flx data, ignored the ecam has a nuisance, and then we saw the outcome. Lots of errors that lead to the end result.Operationally, what would be the implication of fixing this error? E.g., stop progress towards takeoff for 30 seconds, run a checklist for two minutes, tell Ground you have to pull aside for ten minutes?
.
"Ugh tower, we are going to have to call maintenance to check something out. Is this taxiway okay?"Operationally, what would be the implication of fixing this error? E.g., stop progress towards takeoff for 30 seconds, run a checklist for two minutes, tell Ground you have to pull aside for ten minutes?
I'm guessing the thrust levers were set to the Flex T/O detent without the computer having a value(?), which produced the THR LEVERS NOT SET alert.
the speeds were dumped out when they changed runways.
FATS check... can't forget the FATS check!!!
Am I reading this wrong, or does the airbus actually call an abort for you?!
Am I reading this wrong, or does the airbus actually call an abort for you?!
Unfortunately this is airbus knowledge 101. If you don't have a flex temp set and put the thrust in the flex/mct detent, around 60 knots you'll get a caution and a "thrust not set" message. At my carrier, that's a briefed item that we do not abort for and just set thrust to the toga detent. By doing so, the FMA goes to the normal takeoff look and the plane is happy.
Instead, he ignored it. So, passing through 80 knots, the plane thinks "oh, so I guess you're landing or something?", and sounds the "retard, retard." (This time it really is directed at you personally)
They ignored that and put the plane in the air, but of course the FMA and FDs looked really out of whack. Confused, instead of flying the plane like you should, he slapped it back to the ground...completing the sequence of doing exactly what shouldn't have been done.
Cue evacuation selfies from the pax!
(It should be noted I have no insider knowledge on this. I'm just helping the non-French speakers understand what the article is saying.)
In a way it reminds me of Palm 90. Airplanes not flying like it should, something seems wrong, let's try to force it into the air instead of pushing the thrust levers through the instrument panel.I'm not one to Monday morning quarterback these things, but it does baffle me that someone would ignore a TOGA command on the takeoff roll. If I'm hearing that, I'm either doing as the computer says or rejecting the takeoff. I'm not just ignoring it.
In a way it reminds me of Palm 90. Airplanes not flying like it should, something seems wrong, let's try to force it into the air instead of pushing the thrust levers through the instrument panel.
Do most airplanes do that? The SAAB has T/O inhibit mode. It inhibits most of the warnings except for a select few.Reading it wrong.
I am sure @PeanuckleCRJ will correct me if I am wrong, but you don't get minor stuff come up on the ECAM during the takeoff phase.