They say pictures speak louder than words... I think so.
Note: The arrival was for both runways. The end of the green line is where ATC will vector you to the runway you're landing on.
The puzzling thing was, it looked like (on the map) we were lined up on 27R on approach. I double checked that 26L was in the MCDU. I held the runway diagram and counted runways confirming we were lining up on the correct runway. We double checked that the correct frequency was tuned. We were in VMC conditions.
The question was... why this map display?
My friend at Airbus has the same philosophy as I do: It's within your network that you find the answers.
He says, " I learned long ago that it’s really about having a network of people who are a lot smarter than I am on such topics... here’s what they answered – after they both said something like, “sounds like it was a return to the departure airport to me”
"This would be a normal display (technically speaking) if the flight departed from 27R and landed on 26L.
Although the departure threshold is sequenced in the FMS at Take-Off, it remains displayed on ND for the rest of the flight. However one does not frequently have an opportunity to see this, as generally you are landing at a Destination airport different from the Origin airport. 27R appears to be white on the ND, which would again suggest that it was just displaying the departure runway.
Looking at the scale that the ND is set at, my guess is that the two runways are superimposed on top of each other. In fact as they got closer and reduced their range both runways would have appeared separately – the landing runway in green and the departing runway in white. The fact that “26L” is displayed on the ND also leads me to believe that indeed runway 26L was there and would have been seen if the range were reduced."
Yes, we were landing on 26L. We departed off of 27R. But the confusion was the fact we initially programed 27R for the landing. When we changed it, it stayed on the map. So we'd thought. It really was there all the time, but we were busy being vectored. This is one of those "coincidences" they call "distractors" in training.
Thankfully VMC conditions helped confirm we were where we needed to be, as did the frequencies and the runways in front of us.
So.... I learned something interesting about Overweight Landings during this search for answers on the map. More to come on Thursday!
Enjoy the Journey!
XOX Karlene
The 767 actually does something similar. If you depart, and return to the same airport, there will be an orientation line extending the centerline from your departure runway still. That doesn't mean it erases your arrival runway, but in order to get rid of it, as it can be distracting, you have to go back to the DEP/ARR page and either delete the takeoff runway or change it to the same runway you are landing on.
ReplyDeleteAh... so we could have just changed the "departure" runway and then this "picture" wouldn't have been there. Good to know! Thanks!
ReplyDeleteWow, trust but verify indeed! Great advice in any aspect of life, vital in flying. :)
ReplyDeleteHeather, yes...vital for sure!
ReplyDeleteWow, it's so important to know all the ins and outs and in-betweens! Double and triple checking never made more sense!
ReplyDeleteWhen you're in the clouds... IMC...you lose some of your situational awareness...that's when we have to fight disbelief!
ReplyDeletehow come 26 left is not in white while 27 right is?
ReplyDelete27R is in white because it's the departure runway.
Delete