Hi EveryoneI have the Flight 1 Mustang and have included the latest Navigraph data however I find that a lot of the RNAV approaches in Australia are not present and would like to build my own. Flight 1 does not want to support this with any information at all for building my own approaches based on the data available and was wondering if anyone had cracked the code so I can have a go at it at my own risk.CheersBarra

Hi EveryoneI have the Flight 1 Mustang and have included the latest Navigraph data however I find that a lot of the RNAV approaches in Australia are not present and would like to build my own. Flight 1 does not want to support this with any information at all for building my own approaches based on the data available and was wondering if anyone had cracked the code so I can have a go at it at my own risk.CheersBarra

Why would you expect Flight1 to support Navigraph's database? That's the job of Navigraph!

Hi EveryoneI have the Flight 1 Mustang and have included the latest Navigraph data however I find that a lot of the RNAV approaches in Australia are not present and would like to build my own. Flight 1 does not want to support this with any information at all for building my own approaches based on the data available and was wondering if anyone had cracked the code so I can have a go at it at my own risk.CheersBarra

The mustang data is standard also for the Coolsky MD-80. Perhaps someone at the Coolsky website (http://coolsky.no) has tried this out?You should have a Navigraph/NavData/Proc folder in your main FSX folder. There are text files in there for each Airport (I counted 72 aussie airports). As best as I can tell, the procedures are spelled out in plain text files. Such as:SID,KAT1,34L,2CA,0,335.0,2,800,0,1,0,0,0,0CD, ,0,0,0,SY,0.0,0.0,290.0,10.0,0,0,0,1,0,0,0,0DF,KAT,-33.710833,150.299722,0, ,0.0,0.0,0,0,0,1,0,0,0,0Now there is the ARINC 424 Standard Document which defines what those first codes mean (CA, CD, DF, etc) but I really can't work out what the rest of the numbers are for (some obviously look like Lat/Lon values). You could perhaps inquire about them in the Navigraph forums? I do know that Airport Design Editor can make procedure files and you could reverse-engineer the resulting XML files to get the information required to create the required Navigraph text format. However, AIRAC source-data for Navigraph likely only contains these 72 airports at this time (at least in the Flight1-compatible format), so I'm not sure if there are other aussie procedures.In the end, you can probably triangulate a solution between the Navigraph, Coolsky and fsdeveloper.com forums. I mention Coolsky as those folks are generally pretty friendly and helpful.It looks to be quite a task, but if you are willing to keep after it, perhaps someone will accept your updates are a regular part of the Navigation data. I'm not certain that the Mustang developers will do much for you, but Espen at Coolsky might be open. It doesn't hurt to join the aforementioned forums and ask around.

FWIW, the entire database is bog-standard Microsoft Excel. The problem is that there are actually five (or six) databases that are all tied together via an index number. You would add a new entry to the very bottom of the main (airport) section of the database, giving it the next highest number...The real "fly in the oinment" is that frequencies are encoded in some format I've yet to figure out! :(

FWIW, the entire database is bog-standard Microsoft Excel. The problem is that there are actually five (or six) databases that are all tied together via an index number. You would add a new entry to the very bottom of the main (airport) section of the database, giving it the next highest number...The real "fly in the oinment" is that frequencies are encoded in some format I've yet to figure out! :(

Fr. Bill,Are you sure? When I install the Navigraph data for the Coolsky/Mustang/Fokker (called GEN_10xx by Navigraph), all of the data is flat-file text. It all lives under Drive:\FS_INSTALL_ROOT\Navigraph\NavData and Drive:\FS_INSTALL_ROOT\Navigraph\NavData\Proc. While I can't decipher the exact structure of the files, it is at least all plain-text. I wonder if you're thinking of what CaptainSim does or what Wilco/FT does with their data?I haven't had the Mustang installed for about 6 months now, but I know that Navigraph lists the Mustang as using the same DB as does the MD80.

I was thinking more specifically of the format the database is for our CX v2.0, as well as that used by several other products that I've looked at. I've never looked at the others you mention, so it is quite possible that they have specified a different format for their database. It would be nice if everyone used a common format because it would reduce the cost to produce and maintain, resulting in lower cost to the consumer.Unfortunately, it's likely that not every programmer is familiar enough with accessing the Excel database, or there was some other compelling reason for using a "flat file" DB... :(

Has anyone made progress on this, in the meantime?Both the Mustang and the C182T use this databasewhich is described in some detail by Hans Hartmannhere: http://www.digital-aviation.de/files/pa31t/FMS_Format_v2.zipThis description is version 2.03, but I've heard mention of version 2.04..Since the database is light on Canadian RNAV approaches, I would liketo add some, like CYCD etc

IIRC, Navigraph has a procedure for reporting "errors" or missing data. Has anyone contacted them directly?Vic

IIRC, Navigraph has a procedure for reporting "errors" or missing data. Has anyone contacted them directly?Vic

I have..

FWIW, the entire database is bog-standard Microsoft Excel. The problem is that there are actually five (or six) databases that are all tied together via an index number. You would add a new entry to the very bottom of the main (airport) section of the database, giving it the next highest number...The real "fly in the oinment" is that frequencies are encoded in some format I've yet to figure out! :(

What database (it's name) are you referring to?

What database (it's name) are you referring to?

Navdata/Proc.I've been able to create an RNAV entry for CYCD which at least works on my system,using this slightly outdated description and comparing to other airports.Use at your own risk!CYCD.txtAPPTR,R16,16,NANOOIF,NANOO,49.264167,-124.244167, ,0.0,0.0,0,0,0,1,0,0,0,0TF,IGROL,49.238667,-123.991833,0, ,0.0,0.0,0.0,0.0,2,2500,0,1,0,0,0,0TF,OBNES,49.225667,-123.866167,0, ,0.0,0.0,0.0,0.0,2,2000,0,1,0,0,0,0FINAL,R16,16,G,4IF,OBNES,49.225667,-123.866167, ,0.0,0.0,1,2000,0,1,0,0,1,0TF,DUVKO,49.142667,-123.868167,0, ,0.0,0.0,0.0,0.0,2,1000,0,1,0,0,2,0TF,ALNUP,49.090333,-123.869333,0, ,0.0,0.0,0.0,0.0,2,400,0,1,0,0,3,0TF,RW16,49.058167,-123.870167,0, ,0.0,0.0,0.0,0.0,1,93,0,1,0,0,0,0VA,1,68.0,2,463,0,1,0,0,0,0TF,FAXTO,49.076767,-123.493572,0, ,0.0,0.0,0.0,0.0,1,3000,0,1,0,0,0,0