Okay. Not a VFR day.

 

PAWG 191816Z 27007KT 1/2SM VV002 10/08 A3019 RMK AO1 WEA: FG (MCQ)

 

Not good enough for the RNP.

Foiled! That's one reason I like SE... ya just never know what you'll get. But absolutely... VFR up there is the best!

...but there won't be any film at11 cause I am stumped!!!

 

 

//PAPG (JOHNSON PETERSBURG)

//Worldwide Navaid Database for PMDG

//Exported via DFD v1.0 14.1025

//Software copyright © 2014 Richard Stefan, NAVData-Service

//Support available via forum at http://forum.navigraph.com

//

//Data provided by Navigraph - www.navigraph.com

//Source data copyright © 2014 Jeppesen

//This data may be used for ground based recreational computer game

//simulation software only, and may not be recompiled, interpreted,

//or distributed for any purpose without the written consent of Navigraph.

//The contents of this database is dated and must not be used for real

//world navigation as it is unlawful and unsafe to do so.

//

//------------------------------------------------------

//AIRAC Cycle : 1412 (13/NOV/2014 - 10/DEC/2014) - Ver.1

// chasNav

//------------------------------------------------------

 

FIXES

FIX JERDU LATLON N 57 9.59034 W 132 52.10802

FIX P0000 LATLON N 57 10.026942 W 133 13.122346

FIX WUBDO LATLON N 57 6.31332 W 133 37.13586

FIX ZARUT LATLON N 57 3.01584 W 133 47.79186

FIX PAJN5 COLOCATED SSR 042.4 23.6

//FIX PAJN6 COLOCATED SSR 047.6 18.6

//FIX PAJN7S COLOCATED SSR 085.3 28.9

FIX PAPGD COLOCATED LVD 325.7 19.4

FIX PAPGD1 COLOCATED LVD 341.3 19.5

FIX PAPGE COLOCATED LVD 346.1 19.4

FIX PAPG1A COLOCATED LVD 324.2 33.9

FIX PAPG1B COLOCATED LVD 323.7 17.3

FIX PAPG1C COLOCATED LVD 328.2 15.4

FIX PAPG2 COLOCATED LVD 333.8 14.6

FIX PAPG3 COLOCATED LVD 340.8 14.0

FIX PAPG3A COLOCATED LVD 347.3 13.2

FIX PAPG3B COLOCATED LVD 352.3 14.4

FIX PAPG3C COLOCATED LVD 355.6 14.8

FIX PAPG3D COLOCATED LVD 356.8 16.2

FIX PAPG4 COLOCATED LVD 351.3 17.6

FIX PAPG5 COLOCATED LVD 348.2 18.9

FIX PAPG6 COLOCATED LVD 347.4 19.3

FIX PAPG7 COLOCATED LVD 348.8 19.8

ENDFIXES

 

RNWS

RNW 05

RNW 23

ENDRNWS

 

SIDS

SID PTRSG1

RNW 05 TRK 050 UNTIL 520 HDG 300 INTERCEPT RADIAL 344 TO FIX JERDU FIX JERDU FIX P0000 FIX WUBDO FIX ZARUT

RNW 23 TRK 230 UNTIL 520 HDG 230 VECTORS

ENDSIDS

 

APPROACHES

APPROACH RNAV05L FIX PAPG1A FIX PAPG1B FIX PAPG1C FIX PAPG2 FIX PAPG3 FIX PAPG3A FIX PAPG3B FIX PAPG3C FIX PAPG3D FIX PAPG4 FIX PAPG5 FIX PAPG6 FIX PAPG7

 

APPROACH RNAV05S FIX PAPG1A FIX PAPGD FIX PAPGD1 FIX PAPGE FIX PAPG7

ENDAPPROACHES

 

END OF PAPG.TXT

 

 

 

Ok, was bored so got it debugged.  There were a few issues, some of which I'm certain were problems, others of which might have been (I just kept changing things till it worked).

 

1.  You for certain can not define a COLOCATED fix until you've already defined the fix it's based off of... so for instance, you need to define SSR before you can define PAJN5, and you need to define LVD before you can define all the rest.  Yes, I know SSR and LVD exist in the NGX nav database already - but it doesn't matter.  Any fix used in a procedure NEEDS to be defined in the FIXES section of the SIDSTAR txt file.  And they're parsed in order, so SSR and LVD need to be defined before their respective colocated fixes.

 

2. I'm not sure you can use decimal degrees in colocated fixes - may have to round to the nearest whole degree.  Just a guess there.

 

3. Approaches section - each approach at the very least needs to end at a runway, and a missed approach procedure is possibly required as well.  Also, you MAY need to specify at least one hard crossing altitude at one fix for the box to create an actual GP leg.

 

So, here's my revision that I tested, and it loads in the box ok.  Haven't test flown the procedures, I'll leave that to you ;-)

 

//---------------------------------------------------------------------

//PAPG (JOHNSON PETERSBURG)

//Worldwide Navaid Database for PMDG

//Exported via DFD v1.0 14.1025

//Software copyright © 2014 Richard Stefan, NAVData-Service

//Support available via forum at http://forum.navigraph.com

//

//Data provided by Navigraph - www.navigraph.com

//Source data copyright © 2014 Jeppesen

//This data may be used for ground based recreational computer game

//simulation software only, and may not be recompiled, interpreted,

//or distributed for any purpose without the written consent of Navigraph.

//The contents of this database is dated and must not be used for real

//world navigation as it is unlawful and unsafe to do so.

//

//------------------------------------------------------

//AIRAC Cycle : 1412 (13/NOV/2014 - 10/DEC/2014) - Ver.1

// chasNav

//------------------------------------------------------

FIXES

FIX JERDU LATLON N 57 9.59034 W 132 52.10802

FIX P0000 LATLON N 57 10.02694 W 133 13.12234

FIX WUBDO LATLON N 57 6.31332 W 133 37.13586

FIX ZARUT LATLON N 57 3.01584 W 133 47.79186

FIX SSR LATLON N 58 10.65948 W 135 15.53166

FIX PAJN5 COLOCATED SSR 042 23.6

//FIX PAJN6 COLOCATED SSR 048 18.6

//FIX PAJN7S COLOCATED SSR 085 28.9 

FIX LVD LATLON N 56 28.06248 W 133 04.98684

FIX PAPGD COLOCATED LVD 326 19.4

FIX PAPGD1 COLOCATED LVD 341 19.5

FIX PAPGE COLOCATED LVD 346 19.4

FIX PAPG1A COLOCATED LVD 324 33.9

FIX PAPG1B COLOCATED LVD 324 17.3

FIX PAPG1C COLOCATED LVD 328 15.4

FIX PAPG2 COLOCATED LVD 334 14.6

FIX PAPG3 COLOCATED LVD 341 14.0

FIX PAPG3A COLOCATED LVD 347 13.2

FIX PAPG3B COLOCATED LVD 352 14.4

FIX PAPG3C COLOCATED LVD 356 14.8

FIX PAPG3D COLOCATED LVD 357 16.2

FIX PAPG4 COLOCATED LVD 351 17.6

FIX PAPG5 COLOCATED LVD 348 18.9

FIX PAPG6 COLOCATED LVD 347 19.3

FIX PAPG7 COLOCATED LVD 349 19.8

ENDFIXES

 

RNWS

RNW 05

RNW 23

ENDRNWS

 

SIDS

SID PTRSG1

RNW 05 TRK 050 UNTIL 520 HDG 300 INTERCEPT RADIAL 344 TO FIX JERDU FIX JERDU FIX P0000 FIX WUBDO FIX ZARUT

RNW 23 TRK 230 UNTIL 520 HDG 230 VECTORS

ENDSIDS

 

APPROACHES

APPROACH RNVL05 FIX PAPG1A FIX PAPG1B FIX PAPG1C FIX PAPG2 FIX PAPG3 FIX PAPG3A FIX PAPG3B FIX PAPG3C FIX PAPG3D FIX PAPG4 FIX PAPG5 FIX PAPG6 1400 FIX PAPG7 RNW 05 FIX LVD HOLD AT FIX LVD RIGHT TURN INBOUNDCOURSE 300 ALT 6000 SPEED 200 LEGTIME 1

//

APPROACH RNVS05 FIX PAPG1A FIX PAPGD FIX PAPGD1 FIX PAPGE 1400 FIX PAPG7 RNW 05 FIX LVD HOLD AT FIX LVD RIGHT TURN INBOUNDCOURSE 300 ALT 6000 SPEED 200 LEGTIME 1

ENDAPPROACHES

//------------------------------------------------------------------------------------------------------

Wowwwwweeeee!

 

1. You for certain can not define a COLOCATED fix until you've already defined the fix it's based off of... so for instance, you need to define SSR before you can define PAJN5, and you need to define LVD before you can define all the rest. Yes, I know SSR and LVD exist in the NGX nav database already - but it doesn't matter. Any fix used in a procedure NEEDS to be defined in the FIXES section of the SIDSTAR txt file. And they're parsed in order, so SSR and LVD need to be defined before their respective colocated fixes.

 

--huh!!!...great find!...especially with the redundant fixes!! I was aware of previously declaring a variable before referencing it, My programming background...but I could not accept the notion of a redefined variable, until you pointed it out to me.

 

2. I'm not sure you can use decimal degrees in colocated fixes - may have to round to the nearest whole degree. Just a guess there.

-good guess...unfortunately I found that the NGX FMC COLOCATED references can't use decimals, (as you can see, the GTN750 can)only integers...thus deprecating the accuracy of colocated fixes.

 

3. Approaches section - each approach at the very least needs to end at a runway, and a missed approach procedure is possibly required as well. Also, you MAY need to specify at least one hard crossing altitude at one fix for the box to create an actual GP leg.

---verifying that...I am sure you are correct.

 

Thanks a million!!!

 

...I'll be flying/revising it tonite..film at...err..12?

 

Yer a champ!

 

Chas

here is the result.

 

enjoy

 

https://youtu.be/Lh-WX_sFR00

 

thanks SD,

 

chas

I discovered that John O'Duffy's approaches from several years ago are still in the library and still work...a bit of an unstable approach, but it worked. FRAPS isn't recording my AA as well...should probably just have used ShadowPlay.

 

https://youtu.be/v1aQ6haNX5s

Nicely done!

 

Chas

Actually it was Steve Fulton and Hal Anderson who did the pioneering work for Alaskan in Juneau for RNP AR.

 

I had the pleasure of meeting Hal and working with Steve for a number of years when I introduced RNP AR procedures at 15 airports throughout Australia i 2006 when Steve and Hal still owned Naverus before GE got their hands on it.

 

Fantastic times. This AR stuff is mickey mouse and fun to work with and fly.

 

Thought that was the case. There used to be another gent that lurked these forums who was also part of the design/inception of RNP proc's for Australia. Do you know whom I talk of? Also, did you play any part in having RNP made public so we commoners could use them? If you did, thanks a million! They fly great!

 

Anyway, I'm yet to do some simming in Alaska. I can't wait!

 

Brian Nellis

 

If interested, here is my youtube channel. A few RNP approaches into some Aust. airports. https://www.youtube.com/channel/UCeskE2l3OZaq4cdTp3BbXOw

Hey Cooper ,

 

Thanks for the vids ...watched the Melbourne, Rwy 34...can't find INTL. approaches in sky vector.

 

From the vid, nice long arc...almost a DME ARC, can't understand though WHY it is RNP.

 

Is the procedure available here?

 

Chas

Hey Cooper ,

 

Thanks for the vids ...watched the Melbourne, Rwy 34...can't find INTL. approaches in sky vector.

 

From the vid, nice long arc...almost a DME ARC, can't understand though WHY it is RNP.

 

Is the procedure available here?

 

Chas

I guess this runway has an RNP approach because there are no Precision Approaches that serve it. RNP AR approaches are the best way to get as low as possible, following the best track possible. From Airservices Australia's perspective, I would guess it's easier to build an RNP procedure, than to upgrade airport/RW34 infrastructure.

 

I use Navigraph NavData for the NGX. In that, you get all the publicly available RNAV RNP proc's available, worldwide. As far as the charts go, you can get them from here http://www.airservicesaustralia.com/aip/pending/dap/AeroProcChartsTOC.htm

 

Sorry to all. Didn't intend to change the topic to RNP in general.

 

Brian Nellis

A great topic!

Good news to get some of these super "Alaskan specific" approaches available!

Thank You very much for sharing!

Well the RNAV RNP works well into RW26! Had to disconnect at DA (0.20/433 feet); you can see why here https://www.youtube.com/watch?v=pLYlAc2kxLs

 

My first sim session in Alaska/Juneau.

 

Quite a good looking country you guys have there!

 

Brian Nellis

Well the RNAV RNP works well into RW26! Had to disconnect at DA (0.20/433 feet); you can see why here https://www.youtube.com/watch?v=pLYlAc2kxLs

 

My first sim session in Alaska/Juneau.

 

Quite a good looking country you guys have there!

 

Brian Nellis

 

Nice video. I just did RNP 26 in a two-week-old -900ER on Tuesday. It smelled great.

 

I've never had a GPWS warning in JNU on the approach. Something needs tweaking.

 

Oh, and 8/26 is closed! You're supposed to land on taxiway Alpha.

Oh, and 8/26 is closed! You're supposed to land on taxiway Alpha.

Must've skipped over that notam... my bad

 

I've never had a GPWS warning in JNU on the approach. Something needs tweaking.

Good to know! There must be an issue with FSX terrain or something.

 

Nice video.

 Thanks. The youtube video seems laggy. I just watched the shadowplay footage and there's no lag. I hate watching laggy video, so sorry about that. I don't know who the culprit is; youtube or handbrake.

 

I just did RNP 26 in a two-week-old -900ER on Tuesday. It smelled great.

You must provide a video, or it didn't happen

 

Brian Nellis

 

 

You must provide a video, or it didn't happen

 

I wish. It was a beautiful day. Have some stills I took of the freighter landing a little while later.