Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Procedures for Queenstown, NZ

Featured Replies

  • Replies 116
  • Views 24.1k
  • Created
  • Last Reply

Top Posters In This Topic

  • Author
http://www.geaviatio...arning-rnp.htmlI found this. Not sure if you are aware of it. Click the link, and click the top picture. You will find what I think to be a RNP-AR SID from ZQN runway 5.Ash Frew.
Thanks Ash, but I already have that pic. It is the Cardrona 1 RNP SID from runway 5, which I have already coded. I have rummaged all through the GE/Naverus site trying to gather every little morsel they might drop. I also managed a couple poor resolution pix of the RNAV 23 and the RNAV-Z 05. Not high res enough to read properly, but I did gather some data from them.The file is pretty much done. I have two approaches left to code, but they are the conventional VORD Alpha and VORD Bravo. The VORD Charlie is done and tested. The beta testing of the RNP procedures is pretty much complete, unless any real-world pilots who have flown these are willing to shed some light on it. All the conventional SIDs are also finished and work OK.After those two procedures are coded I should be uploading to AVSIM. I will post here when it is finished in case anyone is following the thread.

I was under the impression the QN waypoint data in the RNP approaches is reliant on the DME from SH and not a fixed location. I have seen a few radar dumps of 733's and A320's on the RNP approach's and there is a slight variation on each approach.

Mark Ward

  • Author
I was under the impression the QN waypoint data in the RNP approaches is reliant on the DME from SH and not a fixed location. I have seen a few radar dumps of 733's and A320's on the RNP approach's and there is a slight variation on each approach.
Well I guess you could always relate the position of anything to the nearest VOR/DME. But I can assure you that its relation to SH is not published anywhere that I have seen. And keep in mind, the NGX does not accept collocated fix plotting. You can only define positions in the terminal procedures text file by using the LAT/LON coordinates. So even if you new the collocated description for a fix, you would still need to fire up the some to plot it and then extract the coordinates.The variations probably come from weather, which will surely affect the performance of the aircraft. Having not seen the radar data you talk about I can only guess that this variation was minor in nature and within the RNP. The other possible explanation is that different operators might have different data produced for them and specifically tailored for their aircraft types. Maybe the 737 has different turning capabilities than an A320 and so therefore requires different protections and turn radiuses. Again, I don't know why the variations. What I can tell you is that my file will be based not he data I have seen from AIP NZ on their public website, which seems to match some of the pictorials I have seen of the Naverus Qantas charts.

Bingo on the variations, hence why the QN waypoint locations are slightly different. I could do some digging and see if I can get the lat/longs for the QN waypoints if they are infact fixed.

Mark Ward

  • Author
Bingo on the variations, hence why the QN waypoint locations are slightly different. I could do some digging and see if I can get the lat/longs for the QN waypoints if they are infact fixed.
What would help as well would be to see the charts. Then I could name the all the waypoints on all the procedures accurately. The charts are crucial in order to know which fix is which, otherwise the positions would be worthless. They also have to be in Minutes to 3-5 decimal places in order to be the most accurate. If you find such data, please PM and I will use it to update my work. For now, I plan on releasing what I have after I code the other two VORD approaches. So any changes would come in the form of an update at a later time.Thanks

Hi Mariano,Been going through my cupboard as I new I had some charts stuffed i away. I have no idea if they are any good to you. I will list them below and let me know if any good. I am a bit dumb when it comes to RNP chatrs so I maybe listing scrap paper, so please bear that in mind.!/ VFR/ aip visual flight guide issued by CAA This one is available on Navgraph ? so not what your after, thought I would list anyway.2/Area chart NZQN. Shows DME arc and arrival way points etc.Heaps of other charts that were given to me by a ANZ pilot in 2009.They are probably not much help without a RNP, but I will let you be the judge.Thanks for all the work you are doing.Cheers

Edited by ZK-SUH

System: MSFS2024, ASUS Rog Stryx Z790-A,  Intel i9-14900KF,  Asus ROG Ryujin III 360 , Asus Hyperion Case,Rog Stryx 4090 OC, Samsung 970 EVO M.2 SSD, 1Tb Samsung 860 EVO SSD,64Gb G Skill Memory, Asus Aura 1200W Gold PSU,Win 11 ,LG C4 48" 4K OLED Screen., Airbus TCA Full Kit, Stream Deck XL. WinWing FCU, EFIS, MCDU

 

  • Author

No need, only if they say RNP or RNAV, that is what I am after. The rest are all available from AIP NZ. In fact, the RNP charts are available from AIP NZ as well, but they lack a lot of info (fix names and procedural heights).Thanks

Mariano,this is amazing stuff! Keep it up..I would really like to be able to fly proper RNAV approaches into NZQN as it's a great, challenging approach..I'm flying them badly manually atm, and just guessing the QN fixes from the NZ AIP charts as I circle..Can't wait! Well donebestjake

JAKE EYRE
It's a small step from the sublime to the ridiculous...Napoleon Bonaparte
newSigBetaTeam.gif
lancairuk.jpg

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!!
Jeff/John/Mariano,I won't quote the whole post as it would just waste space. Amazing work with these fixes. I really want to build a plan using a planning tool into NZQN. I reckon with the fixes you have here I can at least put something rudimentary together; perhaps not full RNP/RNAV but semi..Forgive me for being dumb (this isn't my bag but I love a challenge) The co-located fixes; are they distance measured on a radial from the Slope Hill VOR/DME? I'm not familiar with manually entering fixes into the FMC. Any help on using these would be greatly appreciated, The lot that have RW co-ords, can they be entered into FSCommander or the FMC (or any other FSX planning tool) as manual waypoints just as they are? (I entered one into FSC and it crashed it!)I can then work out heights and speeds manually.I know you guys are working on this properly, and you know what you are doing, but I'd love to try to put a basic plan together.Thanksbestjake

JAKE EYRE
It's a small step from the sublime to the ridiculous...Napoleon Bonaparte
newSigBetaTeam.gif
lancairuk.jpg

EDIT: I think I was being a bit thick here. You mean radius from NZQN (like it says in the list duh) which, according to FSC is S45 01 15 E168 44 20 Am I correct? If so, I will post some early, rudimentary but geographically accurate procedures soon. I have found it relatively easy to create the accurate fixes using the user waypoint function of FSC and just naming them, so they are now in the user dastabase and can be selected as part of any approach to NZQN. I can re-create the RNP05/23 on AIPNZ quite easily. I am now going to create heights and speeds in the FMC and save out and reverse engineer it back into a planning tool to create a full custom loadable approach. Technically they aren't approaches, as I have no idea how to edit/add the approach files in NGX/Navigraph, but I will post FSC PMDG and FSX plans and perhaps someone with a larger brain and more patience can turn them into proper STARs

JAKE EYRE
It's a small step from the sublime to the ridiculous...Napoleon Bonaparte
newSigBetaTeam.gif
lancairuk.jpg

EDIT again: it seems FSCommander will let me save a set of waypoints as an approach segment. I can now add RNAVRW05/23 to the end of any journey. Not much help if you don't have FSC. It can export whole plans but not just route segments/custom approaches. You have to have a start and end point (the end point will always be NZQN obv.)

JAKE EYRE
It's a small step from the sublime to the ridiculous...Napoleon Bonaparte
newSigBetaTeam.gif
lancairuk.jpg

ok, with thanks to Mariano, Jeff, john and everyone else who's been on this, for all owners of FSC, here are the co-located fixes (not, as Mariano correctly wants) to an accurate 3 decimal places, as I did it with my mouse looking at the LAT/LON readouts as I was clicking; but it works. Also, thanks to that IFR Significant points list (great find that) the named fixes. These are actually in FSC (they say not in database on the FMC in NGX)If you have FSC, just add these to the Q section in the userWP.txt file in the FSC9database folder exactly as you see here, they can then be added as waypoints. (copy from the // to the the stuff in bold)I've also tried to uploaded the actual arrival files so you can just stick them in the relevant folder, which is FSC9segmentsarrivals but it says "you are not allowed to upload this kind of file" it's a .arr file. I've added the actual fixes in the file below. Just save them to a file called NZQN.arr in the folder I mention earlier.FIXESstart copy//QN032 ;QN032 ;-45.06183;168.5737FRNKK ;FRNKK ;-45.02883;168.6887QN004 ;QN004 ;-45.0245;168.7057QN004 ;QN004 ;-45.0245;168.7057QNRW05 ;QNRW05 ;-45.01917;168.7343QN028 ;QN028 ;-44.98133;168.7188QN025 ;QN025 ;-44.95633;168.7608QN022 ;QN022 ;-44.94817;168.7965QN019 ;QN019 ;-44.97533;168.814QN013 ;QN013 ;-45.00267;168.7932QN009 ;QN009 ;-45.012;168.7738QNRW23 ;QNRW23 ;-45.0165;168.7582end copyApproach fixes (save to nzqn.arr)start copy//[FSC Segment]NZQN[bEGIN]NZQN RNP0505WP=1,Fix,AURUM,AURUM,-44.7523,168.6512,0.00,23.907,1WP=2,Int,LADIP,LADIP,-44.7871,168.5662,0.00,23.907,1WP=3,Int,ADBAB,ADBAB,-44.9211,168.4419,0.00,23.907,1WP=4,Fix,BENET,BENET,-45.0442,168.4405,0.00,24.725,1WP=5,Fix,RATPT,RATPT,-45.0682,168.4488,0.00,24.725,1WP=6,Fix,WALPK,WALPK,-45.0956,168.5487,0.00,24.725,1WP=7,Uwp,QN032,QN032,-45.0618,168.5737,0.00,24.725,1WP=8,Uwp,FRNKK,FRNKK,-45.0288,168.6887,0.00,24.725,1WP=9,Uwp,QN004,NZQN FIX QN004,-45.0245,168.7057,0.00,24.725,1WP=10,Uwp,NZQHRW05,NZQHRW05,-45.0192,168.7343,0.00,24.725,1[bEGIN]NZQN RNAV2323WP=1,Fix,AURUM,AURUM,-44.7523,168.6512,0.00,23.907,1WP=2,Int,LADIP,LADIP,-44.7871,168.5662,0.00,23.907,1WP=3,Int,ADBAB,ADBAB,-44.9211,168.4419,0.00,23.907,1WP=4,Fix,BENET,BENET,-45.0442,168.4405,0.00,24.725,1WP=5,Fix,RATPT,RATPT,-45.0682,168.4488,0.00,24.725,1WP=6,Fix,WALPK,WALPK,-45.0956,168.5487,0.00,24.725,1WP=7,Uwp,QN032,QN032,-45.0618,168.5737,0.00,24.725,1WP=8,Uwp,FRNKK,FRNKK,-45.0288,168.6887,0.00,24.725,1WP=9,Uwp,QN028,QN028,-44.9813,168.7188,0.00,23.907,1WP=10,Uwp,QN025,QN025,-44.9563,168.7608,0.00,23.907,1WP=11,Uwp,QN022,QN022,-44.9482,168.7965,0.00,23.907,1WP=12,Uwp,QN019,QN019,-44.9753,168.8140,0.00,23.907,1WP=13,Uwp,QN013,QN013,-45.0027,168.7932,0.00,24.725,1WP=14,Uwp,QN009,QN009,-45.0120,168.7738,0.00,24.725,1WP=15,Uwp,QNRW23,QNRW23,-45.0165,168.7582,0.00,24.725,1end copyI have not added missed approach procedures yet..Got to go and do some RL for a while Talking%20Ear%20Off.gifEDIT: and can I add that these are in no way a substitute for what Mariano is working on, they are solely for FSC owners to have a bit of fun while they wait :)

Edited by quadraspleen

JAKE EYRE
It's a small step from the sublime to the ridiculous...Napoleon Bonaparte
newSigBetaTeam.gif
lancairuk.jpg

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.