The Boeing 777 Thrust Asymmetry Compensation (TAC)

As Boeing’s first Fly-By-Wire aircraft (although not necessarily fly-by-wire by the Airbus definition) the 777 introduced a flight control augmentation system that the first fly by wire Airbus aircraft did not – Thrust Assymetry Compensation, or TAC.

The 777 Rudder

The basic problem is clear. During an engine failure on a twin wing-mounted engine aircraft there is an assymetry between the left and right sides – that is, typically one of the engines is producing lots and lots of thrust; the other is producing none at all (and in fact may well be producing extra drag with windmilling fan blades, etc). A pilot therefore needs to counter the quite strong tendency of the aircraft to yaw towards the failed engine or else lose control of the aircraft altogether. Sufficient rudder pedal input on the flight deck is required to deflect the rudder on the tail to offset the asymmetry. A badly handled engine failure can result in poor climb performance – or none at all. The loss of an engine in today’s big twins typically results in a loss of 50% of available thrust – and over 80% of available performance.

Simple in concept – the TAC provides an input to the rudder (eventually) which assists the pilot in maintaining control of the aircraft. This lowers workload on the pilot and aids in maximising the performance of the critical after takeoff engine climb out phase. What could be simpler?

Not The Rudder

The first thing that needs to be said, is that TAC typically does not provide a rudder input. In fact, the TAC drives the rudder trim control that in turn drives the rudder pedals on the bottom of the pilot’s feet, which drives the rudder. This is a crucial distinction since it means that normally all TAC input to the flight controls is felt directly by the pilot through the aircraft’s controls. This is the major critical distinction between Airbus and Boeing in this regard. Boeing provides true tactile feedback.

How Does It Work?

Contrary to common belief – TAC does not detect the asymmetric yaw of the aircraft and counter it. TAC works strictly on engine parameters, calculating thrust produced by both engines in order to determine any disparity. Should that disparity increase beyond a certain threshold (nominally about 10% of max thrust) then TAC begins to feed in rudder trim. The larger the disparity, the larger the trim/rudder input. There is no inertial involvement in the TAC calculation. That is, the IRS doesn’t detect yaw and provide this information to the TAC. Apart from the result of thrust calculations – TAC is also advised if the thrust computation is valid – but more on this later.

What about Takeoff?

You may have noticed the hole in this – could you deal with the sudden loss of thrust during an engine failure on take-off, with only the Rudder Trim? I think not, and neither can/does TAC.

In response to a sudden loss of thrust during take-off, TAC commands a high rate rudder input direct to the flight control surfaces – this rudder deflection is not fed back through to the rudder pedals. At the same time the TAC commands a high rate rudder trim input (remember there are two rates of trim input on the 777 – half twist is half rate trim, full twist is full rate trim command) which moves the rudder pedals until the amount of rudder commanded by the rudder pedals (as felt by the pilot) is the same as is being commanded by the TAC direct to the rudders as a result of the thrust discrepancy. It’s important for pilot’s to realise this when experiencing an engine failure on take-off with the TAC working. Instinctively (I hope) all pilots will apply rudder to keep the aircraft straight on the runway during an engine failure – TAC or no TAC. At this time, they are operating in concert with the TAC, which is fine. However, once airborne, pilots will need to make a conscious decision to assess whether the TAC is working, and release the rudder (slowly).


Unfortunately, the TAC can and does fail – including during engine failures. In fact, if a TAC is going to fail during any engine failure, it will be during the more destructive ones. As counter-intuitive as this may seem, there’s a reason for it. Of course it fails all the time in the simulator and there’s a very good reason for that – so you can practice manual rudder control during engine failures!

Occasionally, during catastrophic engine failures, there are short periods of time when the engine parameters feed into the on board computers are invalid. When this is sensed by the TAC – it fails. Since TAC feeds in rudder pressure based on calculated thrust difference – if it can’t calculate thrust on an engine – it can’t safely feed in rudder.

The good news is that once the fuel control switch has been move to cut-off (engine secure), the TAC can be cycled and will return. It knows now exactly how much thrust is coming from that damaged engine – none.

TAC fails for at least the following reasons:

  • Rudder Trim Failure
  • Loss of thrust data from 2 of 3 channels of the EDIU
  • Loss of Left AND Right Engine running data (you’ve got bigger problems!)
  • R/L1/V ACE’s failed/direct mode or the PFC not in Normal mode
  • TAC Switch OFF or Failed

Trimming on TAC

It’s a common error for crew to occasionally trim on top of TAC. This should clearly be avoided, but it’s not a train smash. Anytime you find that you’ve trimmed on TAC – use the Trim Cancel Switch to remove all pilot inputs – this will not affect TAC operation.

The rudder trim inputs by the Pilot and the TAC are not cumulative – it’s a case of who does most wins. If you trim more than the TAC would, your trim affects the aircraft. If you apply less trim than the TAC – TAC is trimming the aircraft. However as thrust comes off the live engine, TAC will reduce trim input – but pilot trim input will remain.

How Much Trim?

It’s a common belief that TAC applies slightly inadequate trim in order to leave the pilot with some feeling as to the asymmetric nature of the flight, and there is some justification for this belief based on documentation in the FCOM and FCTM. However, if you manually trim the aircraft yourself (no TAC) then you’re aiming for control wheel neutral (no aileron deflection, assessed through the aileron trim indication on the control wheel), a slight angle of bank towards the live engine, and a small slip on the balance indicator. This is the aircraft in trim with minimum drag for efficient engine out flight.

If this sounds familiar, it’s how you’ve been trimming out twin engine aircraft since you did your first multi engine conversion in the dim dark past.

The funny thing is, if you leave TAC alone in steady state flight and let it do it’s job, this is the flight configuration it establishes. Believe what you will.


In summary, TAC usually works and works well. It doesn’t preclude the pilot from making inputs during engine failures – far from it. The design actually encourages the pilot to fly the aircraft and merely assists if the job isn’t quite being done well enough. Most pilots can fly quite well when the TAC fails and only realise later on that it happened that way. Perhaps the most common error is forgetting about the TAC and trimming on top, which is why the trim cancel switch is there.

TAC Fun Facts

  • TAC is not functional on take-off until after 70 Knots CAS
  • If the TAC is switched off – any trim applied by the TAC remains in
  • If the TAC fails – any trim applied is removed (Trim centred)
  • TAC is limited to about 60% of available rudder
  • TAC is not active if any reverser is deployed
  • Thrust difference of about 6000lbs (10%) is required to engage TAC
  • TAC then remains engaged until about a 3% difference in calculated thrust

Shortt URL for this post:

1 comment

  1. Hennie van Zyl

    Some additional info about the TAC. We get so used to nearly always having the TAC fail during and engine failure. Maybe some good reading..

    The Sim Standards Team asked Boeing the following questions:

    1. Can you provide the possibility that TAC will fail for each of the failures; Engine Severe Damage/Sep & Engine Limit/Surge/Stall?


    For severe engine damage, if the engine does not continue to run to command, TAC will compensate. The TAC System will not compensate for the thrust loss associated with fan foreign object damage as there will be no indicated thrust difference. Approximately 10% of the time, TAC may disengage during severe engine damage, and will not compensate.
    For engine surge/stall, it is not likely that TAC will disengage (~1% of surge/stall events)

    2. What are the requirements for TAC operation that are at risk in the above failures? (i.e. what will fail with these malfunctions that can cause TAC to become inoperative?)


    For engine separation, loss of the N1 signal will result in TAC becoming inoperative. For engine severe
    damage/surge/stall, a significant discrepancy between N1 and N3, PS3 and P5 can result in TAC becoming inoperative.
    3. Does it seem reasonable to fail TAC every time the faults Engine Severe Damage/Sep & Engine Limit/Surge/Stall are entered into the SIM?


    No, it does not seem reasonable to fail TAC every time the faults Engine Severe Damage/Sep & Engine Limit/Surge Stall are entered into the simulator.

    Boeing recommends the following probabilities of TAC disengagement:

    Engine separation 100%
    Severe engine damage 10%
    Engine surge/stall 1%

Leave a Reply

Your email address will not be published. Required fields are marked *