Jump to content

Lack of NavDataPro coverage


GBL9AL

Recommended Posts

Hi,

It seems like there is a distinct lack of coverage in the FMMM - Antananarivo FIR and FIMM - Mauritius FIR.

An example is airways UA609 the current revision of your 1211 AIRAC data has this airway end at enroute point VEMAR (FMMM - Antananarivo FIR), which is correct however it then turns into the UA609G (Source AIP Ascena ENR 3-2-23, dated 26 July 2012) onwards to enroute point MAEVA and terminates at APKOT. This data is missing.

LIDO navdata then has the airway change into UA609F (This airway is not in any AIP, its not listed in AIP Ascena or AIP Mauritius, but is noted on ENR 6.1 of the Mauritius AIP) to waypoint TIBAG when it becomes UM609F to PLS VOR (Mauritius AIP ENR 3-1.1, dated 19 March 2009).

Other SELECTED airways affected by similar problems seem to be UA400, UA401, UA402, UA474, UA655, UB790, UG594, UG595, UG652, UG653, UR348, UR400, UR401 and UR780 all the problems are within the FMMM - Antananarivo FIR or FIMM - Mauritius FIR.

As someone who works with Navdata day to day at work, I understand the problems that AIRAC amendments/supplements and NOTAMs cause!

Regards

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use