I noticed that on the Navigraph’s navdata and charts there is missing the arrival MEN7T1 LFMT as on the chart below
MEN7T is in the Navigraph database. Which simulator and aircraft/addon are you using?
Regards,
Tim
Looking at the chart a bit closer, there does seem to be an alternative “MEN7T RNAV” by ATC routing (from GIGNA to ASTEG), which is available standalone in the NG database as GIGNA 7K but not as an alternative routing for MEN 7T.
The routing is also drawn on the official chart:
But also seemingly only as “GIGNA 7K” which seems to line up with what’s available in the Navigraph db.
Regards,
Tim
it’s in msfs but in reality on the real airplane in the mcdu there is the choice between MEN7T & MEN7T1 which is as on my charts
Most likely MEN7T1 is a tailored procedure provided by Lufthansa systems would be my guess.
Regards,
Tim
1 Like
Hi,
Tim is correct here. Lido is an airline-driven provider and not as Jeppesen, a global airline-independent provider. That’s why the coverage is not so complete or different worldwide from the Jeppesen source.
In this case, this procedure is tailored by Lufthansa with its procedure ident. In real (according to the AIP), this procedure doesn’t exist under this ident, as Tim referenced.
Thanks, Tim, you are correct! Thanks for your support/help!
Cheers
Richard
Lido has same DB coverage as Jeppesen and is as well a global airline independent provider. Charting coverage is a different story and airline driven.
The reason why MEN7T1 and 2 are used is that the same ident in AIP has different routings published. One conventional and one RNAV based. To separate them 1 and 2 are added as suffix in DB. Those are not tailored, otherwise you would of course not see them.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.