I've compared the current wpnavfix.txt file with the current charts for the RNAV and RNAV Z. Putting aside the "QN*" for the moment, the only waypoint that is not in the existing data is FRNKK. FRNKK is not in the VATNZ files either.Obviously, one of the QN* waypoints are in the wpnavfix file. They are, however all to be found in the NZQN.txt file that is available from VATNZ. For some, they are identified via latitude/longitude, but for others they are coded as "colocated" with a place/bearing/distance fix.It's possible to enter the lat/long waypoints into the CDU, although only to one decimal place (the data is given with up to four decimal places). It's also possible to add them to the wpnavfix file, although some syntax changes are required. It's also necessary to convert the data to decimal - bearing in mind that the VATNZ data has the seconds already decimalised. Eg:FIX QN662 LATLON S 45 05.0000 E 168 43.3043 converts to S45 05' 00" E 168 43' 18" in DDMMSSThis can be converted to decimal using this calculatorThe correct syntax in wpnavfix would therefore be:QN662-45.083333 168.721667The "colocated" waypoints can be entered very simply via the CDU: ie QN019 is entered using NZQN024/4.2The problem with editing the wpnavfix file is that every new cycle will overwrite it. I'm considering creating a separate txt file that can be copied into every new iteration of the airac cycle - but I suspect that there is a lot of time involved.

Here's FRNKKFRNKK NC S 45 01 44.5, E 168 41 19.1 from 0706061200from the document http://www.caa.govt....cant_Points.pdf

awesome! Thanks

but for others they are coded as "colocated" with a place/bearing/distance fix.

In the process of putting something together for NZQN. I am finding that the "colocated" method of defining fixes no longer works in the NGX FMC. I've used this before with the FS9 NG and the 744, but now I get an error. The other thing that does not work is the "navaid" lable instead of "fix". I really liked using that in procedures, but it almost seems like the NGX FMC reads only the airport text file for referencing the terminal procedures. It has no "built in database" if you will, to cross reference. But I guess all of this would be explained in the SDK, when it is released.Anyway, that file that John has posted has many of the fix names with coordinates, which is excellent. The only ones missing are the "QNXX" coordinates.

these any help?

these any help?

Those are the regular VOR circling approaches, I have the Jepp and state charts for those already. I am looking for the RNP Naverus / or Jepp charts showing the name of the fixes and the coordinates. The plates won't have them itself but the must be listed somewhere.

Ahh ok...Well someone in 2005 was askin for the same info on here, but never got a reply.....its just newzealand ''init'''.. and the ''oh so secretive state''.The forum link : http://forum.avsim.net/topic/183452-nzqn-rnav-chart/

Is by any chance New Zealand AIP freely available? Europe has EAD by Eurocontrol, but I have no idea about NZ.

Is by any chance New Zealand AIP freely available? Europe has EAD by Eurocontrol, but I have no idea about NZ.

http://www.aip.net.nz/

The only ones missing are the "QNXX" coordinates.

See below for the co-ordinates of all of the QN* fixes - except the "co-located" ones. I'd upload them in a txt file, but don't know how!!FIX QN004 COLOCATED NZQN 237 1.5FIX QN007 COLOCATED NZQN 234 2.5FIX QN008 COLOCATED NZQN 212 4.0FIX QN009 COLOCATED NZQN 046 1.5FIX QN012 COLOCATED NZQN 189 4.25FIX QN013 COLOCATED NZQN 040 2.5FIX QN014 COLOCATED NZQN 166 3.75FIX QN015 COLOCATED NZQN 150 3.00FIX QN016 COLOCATED NZQN 189 0.75FIX QN017 COLOCATED NZQN 239 1.50FIX QN018 COLOCATED NZQN 033 3.00FIX QN019 COLOCATED NZQN 024 4.2FIX QN022 COLOCATED NZQN 004 5.00FIX QN025 COLOCATED NZQN 348 4.00FIX QN028 COLOCATED NZQN 316 2.50FIX QN032 COLOCATED NZQN 225 7.50FIX QN112 COLOCATED NZQN 316 1.00FIX QN114 LATLON S 45 05.25 E 168 44.18FIX QN115 LATLON S 45 01.46 E 168 41.53FIX QN116 LATLON S 45 04.23 E 168 42.18FIX QN117 LATLON S 45 03.34 E 168 45.36FIX QN118 LATLON S 45 00.44 E 168 44.39FIX QN119 LATLON S 45 01.49 E 168 41.40FIX QN121 LATLON S 45 03.36 E 168 44.02FIX QN124 LATLON S 44 59.58 E 168 43.32FIX QN125 LATLON S 44 51.05 E 168 37.32FIX QN126 LATLON S 44 48.29 E 168 35.45FIX QN127 LATLON S 45 02.41 E 168 41.19FIX QN128 LATLON S 45 04.35 E 168 42.16FIX QN129 LATLON S 45 04.05 E 168 44.08FIX QN404 LATLON S 45 01.50 E 168 42.90FIX QN408 LATLON S 45 01.84 E 168 41.58FIX QN412 LATLON S 45 02.54 E 168 40.26FIX QN416 LATLON S 45 04.69 E 168 40.78FIX QN423 LATLON S 45 00.11 E 168 44.18FIX QN424 LATLON S 44 56.50 E 168 42.53FIX QN425 LATLON S 44 55.03 E 168 43.26FIX QN426 LATLON S 44 49.58 E 168 50.04FIX QN427 LATLON S 44 48.20 E 168 51.46FIX QN428 LATLON S 44 54.37 E 168 44.31FIX QN429 LATLON S 44 54.40 E 168 44.26FIX QN430 LATLON S 44 53.52 E 168 46.23FIX QN431 LATLON S 44 56.11 E 168 41.34FIX QN432 LATLON S 44 56.23 E 168 36.02FIX QN433 LATLON S 44 55.13 E 168 41.28FIX QN450 LATLON S 45 00.26 E 168 48.89FIX QN451 LATLON S 45 00.2614 E 168 49.0468FIX QN454 LATLON S 44 59.8864 E 168 51.4540FIX QN600 COLOCATED NZQN 051 1.5FIX QN610 LATLON S 44 59.02 E 168 48.16FIX QN612 LATLON S 44 57.35 E 168 48.39FIX QN613 LATLON S 44 55.48 E 168 47.42FIX QN614 LATLON S 44 53.20 E 168 42.11FIX QN615 LATLON S 44 52.50 E 168 39.39FIX QN616 LATLON S 44 52.31 E 168 40.43FIX QN617 LATLON S 44 55.43 E 168 49.17FIX QN618 LATLON S 44 54.26 E 168 49.44FIX QN619 LATLON S 44 54.00 E 168 50.42FIX QN620 LATLON S 44 54.09 E 168 51.00FIX QN624 COLOCATED NZQN 033 3.00FIX QN631 COLOCATED NZQN 046 1.5FIX QN632 COLOCATED NZQN 348 4.00FIX QN633 LATLON S 45 00.33 E 168 47.26FIX QN634 LATLON S 44 59.19 E 168 48.18FIX QN635 LATLON S 44 58.01 E 168 48.11FIX QN636 LATLON S 44 57.18 E 168 46.55FIX QN637 LATLON S 44 58.01 E 168 45.35FIX QN638 COLOCATED NZQN 046 1.5FIX QN639 LATLON S 45 00.33 E 168 48.33FIX QN640 LATLON S 45 00.03 E 168 50.42FIX QN641 LATLON S 44 58.44 E 168 51.36FIX QN642 LATLON S 44 57.27 E 168 50.43FIX QN643 LATLON S 44 57.19 E 168 48.48FIX QN644 LATLON S 45 01.48 E 168 43.03FIX QN645 LATLON S 45 03.00 E 168 41.49FIX QN646 LATLON S 45 04.13 E 168 43.16FIX QN647 LATLON S 45 05.18 E 168 44.57FIX QN648 LATLON S 45 07.04 E 168 44.58FIX QN649 LATLON S 45 07.59 E 168 43.09FIX QN650 LATLON S 45 07.28 E 168 41.02FIX QN651 LATLON S 45 05.51 E 168 40.22FIX QN652 LATLON S 45 04.02 E 168 40.31FIX QN653 LATLON S 45 02.31 E 168 41.29FIX QN654 LATLON S 45 01.4814 E 168 42.9846FIX QN658 LATLON S 45 02.8939 E 168 40.7044FIX QN661 LATLON S 45 02.53 E 168 41.38FIX QN662 LATLON S 45 05.0000 E 168 43.3043FIX QN663 LATLON S 45 04.50 E 168 43.45FIX QN664 LATLON S 45 01.49 E 168 43.46FIX QN674 LATLON S 45 02.06 E 168 41.28FIX QN675 LATLON S 45 04.06 E 168 37.18FIX QN677 LATLON S 44 58.12 E 168 40.40

well the AIP has in document 3.6 Domestic Approach Procedures Updated 18 May-11(including STAR)RNP approaches with named waypoints. Jeff here supplied the fix positions, so that should be enough to construct terminal procedures I guess? Also I guess there just has to be a calculator that makes colocated coords into a proper grid coords. (ZULU proc seems to only use COORD waypoints, not colocated.)

Jeff here supplied the fix positions, so that should be enough to construct terminal procedures I guess? Also I guess there just has to be a calculator that makes colocated coords into a proper grid coords. (ZULU proc seems to only use COORD waypoints, not colocated.)

Unfortunately, many of the QN fixes in that post are in the collocated format. I have that document, and AIP State charts depicting the RNP/RNAV procedures. The problem is that the state charts don't name every fix along the track. It only names some. The PDF file linked previously has many of the common named waypoints in it, but it is missing the QN ones. The best solution would be to have access to the Naverus charts that show the waypoint names. Right now, the only option is to eyeball the location based on the map pictorial and then pull the coordinates from FSX. Alternatively, magnify the state pictorials and grid them with the lat/lon overlaid on the pictorial. It is quite complicated because there are areas where the scale changes.Another problem with the state charts is that they don't show the all of the altitudes required, as well as the missed approach waypoints. It shows the MAP as a dashed track and the instructions simply say "follow the RNAV track". It has nothing to do with secrecy by the way, it is just about money. Naverus charges, and probably quite a lot, to produce these procedures. So they are not keen to distribute it freelyAnyway, I will make them anyways, it is just gonna be a little harder and not exactly fully realistic. But my goal will be to get the aircraft to follow the track as much as possible and as realistically as possible. And again, if anybody has any info they can provide, which has not already been provided here in this thread, I would surely appreciate it and it would help to make these procedures more accurate and realistic.

Hi Mariano,I've found a useful calculator that enables place/bearing/distance to be converted to lat/long. I was a little concerned about the VATNZ data, because the location is specifies for NZQN has different co-ordinates from those used in FSX. However, using the same calculator, I worked out that the difference between the two ZNQN's was less than 13 metres, so I doubt that it matters terribly much.I'm in the process, then, of generating decimal lat/long for each of the co-located "QN" waypoints, which can then be added to "wpnavfix.txt".jeff

I'm in the process, then, of generating decimal lat/long for each of the co-located "QN" waypoints, which can then be added to "wpnavfix.txt".

Hi Jeff, you actually don't want to do that. The fixes should go in the "NZQN" file, they are only used there, and if you put them in the "wpnavfix.txt", you will have to put them in the NZQN anyways. Not to mention that they will need to be updated everytime Navigraph updates their airac.Thanks for that link, that is a great calculator. I will definitely use that for some conversions. I don't think you have to tolerate the inacuracy, can't you just enter the NZQN coordinates from the Navigraph data? Unless I misunderstand the calculator.

We need Jason to pipe in!! (think he was one of the Beta testers).This discussion came up in a thread when NGX was in developement and RNAV, RNP approaches were being discussed for implementation as far as the FMC was concerned. Being a kiwi he talked about this and was going to test an approach such as this. I assume with the raduis to fix isnt modelled as yet he hasnt had the opportunity,Jason . . where are you??!!Keep up the great work to all involved above - been wanting this also - you sound like a dedicated bunch.Also i have a publication from January this year (Australian Aviation mag) which had an article on this approach - Naveris constructed this for Qantas. Nice screen shot of the ND with waypoints etc developed for them soley.Same problem though no co-ords published but waypoints are there (which also differ from NZ AIP).