G'day Dan, very much appreciated.
In my updated SIDS STAR file for NZQN, I have been running through entry by entry for my additional APPROACHES, FIXES and GATES and did come to the conclusion also that ERROR at the "FIXES" line did mean there was an issue with the syntax somewhere in the file. I verified by checking every new additional fix one by one to see if the FMC showed and error and you guessed it, no error appeared. Also adding gates at the airport did not cause an issue either.
I was also experimenting with by writing in one extra fix at a time to see if there was a limit to the number of fixes in an APPROACH line. This did not seem to cause an issue either.
What I did find was the use of TRK in the APPROACHES section causes an error and the SIDS/STARS for that airport doesn't appear in the FMC.
Now that I can put in many fixes in the approach (making sure I don't use TRK) this helps me write accurate "real world" approaches for NZQN (and others).
Are there any other traps in writing the syntax for these files? I have read the "PMDG 737NG How to make Terminal Procedures" from the Avsim library as well as the "Tutorial on how to create and adapt data files for PMDG FMC" by Luca T. I'm pretty sure the TRK issue was not mentioned.
Also in the real world approach charts for NZQN (in particular RNAV Y RWY 23) there are smooth arcs required between each fix to navigate safely through the mountainous terrain. By writing FIX OVERFLY this has helped align the approach better but is there a command to place a smooth arc between each fix in the approach??
Thanks and regards, Martin