Cannot find transitions (EHAM)
-
-
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.
-
@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.
@Dreadnought1906 The aircraft comes with a default database from cycle 2503 installed to that location.
Not sure what you mean by 'connection' with Navigraph, but you'll be able to update the the navdata through the Navigraph hub if you have a subscription.
-
@Dreadnought1906 The aircraft comes with a default database from cycle 2503 installed to that location.
Not sure what you mean by 'connection' with Navigraph, but you'll be able to update the the navdata through the Navigraph hub if you have a subscription.
@JF-John said in Cannot find transitions (EHAM):
@Dreadnought1906 The aircraft comes with a default database from cycle 2503 installed to that location.
Not sure what you mean by 'connection' with Navigraph, but you'll be able to update the the navdata through the Navigraph hub if you have a subscription.
I do have a subscription and it updated. But I have both the F100 and the F70. Does the F70 entry cover both aircraft? Is the inclusion of all those files just in case the buyer doesn't have Navigraph?
-
The F70 Professional and F100 Professional will appear as separate products in the Navigraph Hub, with each product requiring its respective navdata to be updated.
If a product doesn't appear in the Navigraph Hub, that usually means the Navigraph Hub hasn't detected that it is installed. We would recommend reinstalling the product that isn't appearing in the Navigraph Hub, then launching a flight in it so that the 'work' folder for the product in LocalState gets created.
Mark - Just Flight
