Jump to content

Recommended Posts

Posted (edited)

image.png

1. LSK2R is missing small white font  [M]_ or [FT] in front of the dashes

2. LSK2R the dashes have to be 1 column right

Edited by Der Michel
  • Like 1

Specs:
CPU-14900K, RAM-64GB-6800, GPU-4090

  • Der Michel changed the title to FMS issues - PERF TO page - 1.03
Posted (edited)
3 hours ago, ArtAir said:

Also need to confirm is it related to ORIGIN/DEST data

Not my remarks. The unit is airpline setting. Nothing is related to origin/dest.

Of course both pictures are not from same FMS state.

Edited by Der Michel

Specs:
CPU-14900K, RAM-64GB-6800, GPU-4090

  • 2 weeks later...
Posted

Currently it's possible to CONFIRM TO DATA via LSK6R after RWY change. That Confirm is only for P4. You aim at P3. 

Honeywell: P3

"If the flight crew enters V1, VR or V2 and the takeoff runway, or the takeoff shift, is changed, but the origin airport remains the same, the MCDU scratchpad displays CHECK TAKEOFF DATA. However, all the takeoff parameters are retained."

Honeywell: P4

"If the takeoff shift, or the flaps/THS, or the runway is changed after V1, VR or V2 insertion, but the origin airport remains the same, the MCDU CHECK TAKEOFF DATA message appears. All takeoff parameters are retained except in case of runway change. In case of runway change, the parameters are invalidated, but still displayed adjacent to each field. The “CONFIRM TO DATA” prompt in [6R] allows reverting to the previous valves."

Specs:
CPU-14900K, RAM-64GB-6800, GPU-4090

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...