Cannot find transitions (EHAM)
-
I have updated nav data using navigraph hub to latest for the F70. As I was arriving at EHAM, landing runway 18R with NORK2A STAR, the FMS does not show any transitions to approach runway. Just as a test, I loaded the Fenix A320 and I see all the transitions for this given STAR.
The manual says: "If a transition is available in the Navdata for the selected SID, a SID Transition (SID TRANS) page will open, allowing for selection of the transition. Pressing the LSKL key next to the desired transition, followed by the LSK6L (INSERT) key, will input the transition into the flight plan."
However I do not see this option. There should be about seven transitions for this runway, but none show in the FMS.
Wondering if I am doing something wrong?
-
-
Yes, its a quirk of the older CDU's. We spent quite a bit of time comparing this to the real world unit to get this right. If you ever need to only enter an approach without a transition, you simply hit RETURN on the APPR transition page. Counter intuitive but correct.
-
I'm having this problem with LOWW and EGLL. When I press *INSERT, I am still not seeing the transitions
-
Reinstalling my navdata fixed it for me
-
Yes, its a quirk of the older CDU's. We spent quite a bit of time comparing this to the real world unit to get this right. If you ever need to only enter an approach without a transition, you simply hit RETURN on the APPR transition page. Counter intuitive but correct.
@JF-John dawd
I'm a bit confused. I had this happen twice to me. Once on EGKK and LFBO. I wasn't able to choose a transition to the approach, but it seemed like the FMS chose the correct Transiiton itself. TIMBA for EGKK and FUZAP for LFBO.
Is that intended behaviour? If I wanted to take a different transition to the approach For example in EGKK WILLO. How would i do that in the FMS?
-
I noticed when installing the F70 and F100 that it contains SID and STAR data for pretty much every airport in the world.
Look in the aircraft directory under \Work\NavData\Proc
I would guess that their connection with Navigraph data is not finalized and maybe this is a workaround that will eventually be removed? Depending on how old the data is that they put in, it would not be surprising if some things in current Navigraph data are missing or different than in the FMS.
