Originally Posted by
FlightDetent
F-16 re FLEX Temp / AST method. A fictitious temperature is fed to ECU so that a reduced thurst is provided by the engine. This reduced thrust level is pre-calculated to provide exactly the amount of remaining thrust needed for the EFATO - Go case.
For the purpose of this thread, the HOW (Temp) is not relevant, also the De-Rate feature could be used (same goal). The WHAT is - for every takeoff a different thrust is used and thus a reference acceleration pattern is hard to define.
Originally Posted by
vilas
Airbus is generally quick to find fixes and both these issues have fixed. Flex temperature is very much a part of the C/L for a long time now. As far as config warning is concerned in conventional A320 it was just an assurance that you are not outside takeoff configuration. Now Airline can opt for new app that will compare the actual configuration with the MCDU entry. Acceleration check in my opinion is not possible when thrust settings vary by as much as 40% nor is it required when everything else is in place. Trend arrow is a good indicator it can even indicate a wind shear.
I am going to disagree a little with some of that. Using FLEX/De-Rate will give you closer acceleration for different weights, (for the same aircraft on the same runway length), than using TOGA for every take-off regardless of actual weight. (very light A320 with a very high FLEX temp accelerates similar to heavy A320 with low FLEX, very light A320 with TOGA accelerates much faster than very heavy A320 with TOGA.)
Not suggesting an acceleration check would work.