The problem we've seen with Navigraph is that their format for procedures is inconsistent. We obviously have to write code to parse the file and interpret the procedures and Navigraph will have, in the same file, two separate syntax for the same type of procedure...and while we read one of them fine, there is a new one in there also that would take a bit of effort to parse. What this means is that if you use the navigraph dataset, then some procedure will be missing from the FMS. Ultimately, we can add code to parse this "strange syntax", but its not our first choice. The fact that there is two 'competing' syntax in the file for the same procedure type doesn't make any sense and we'd rather navigraph correct the issue. If they do that, then there is absolutely no problem with using the navigraph format. We will look into the issue post release. -tkyler