Complicated Sids and Stars?
Thread Starter
Join Date: Sep 2013
Location: Detroit, Michigan
Age: 27
Posts: 5
Likes: 0
Received 0 Likes
on
0 Posts
Complicated Sids and Stars?
I've had experience flying the Van Nuys Nine departure out of KBUR in X-Plane. It is quite the handful and you have to be especially meticulous in reading those cross radials and DME distances otherwise you will miss those very important turns!! Speaking of turns, the very first turn after overflying the Van Nuys VOR for 4 dme involving a turn onto a radial of 323 from the LAX VOR until 24 DME which identifies the Twine intersection, the depending upon your route its either a segment to the AVE VOR, or a turn on a radial of 046 from the Ventura VOR. At this point, your flying to the Lange Intersection which is identified by crossing a radial of 342 from the LAX VOR, then it's a left turn to a bearing of 038 from the Palmdale VOR crossing Slapp (D17 Palmdale) then Boget (D12 Palmdale). After overflying the Palmdale VOR it's rather straightforward from then on flying to the Dagget VOR. But there is one complicated Star that I flew on this same day called the ZIGGY FOUR into KONT! Now that is an arrival; a rather sloppy one at that, but that is just my humble opinion. Does anybody have some suggestions for any particularly difficult instrument procedures? I want to give them a try. 
PS:I'd prefer /A procedures, you know, the old fashioned way of doing things. No RNAV!! 
PS:I'd prefer /A procedures, you know, the old fashioned way of doing things. No RNAV!!
Join Date: Mar 2001
Location: I wouldn't know.
Posts: 4,499
Likes: 0
Received 0 Likes
on
0 Posts
To be honest, haven't flown any SID or STAR on basic instruments since i moved into twins. Does anybody in the real world still do that? Without anything loaded into the box?
You can reduce the workload by a good deal if You use a well thought out nav setup and have the other pilot (if available) reset the navaids as required.
For example if You put VNY on NAV 1, showing track 255 on the HSI and additionally the same VOR on a RMI needle (if available) You have the first two legs to VNY and IPIHO covered. NAV 2 could show LAX track 323.
When You are established on LAX 323, depending on the onward route, switching NAV1 to VTU track 046 or GMN track 322 makes sense. And so on.
Fixes like SLABB, LANGE and BOGET are not only defined via crossing radials from other stations but also via DME fixes from the station You are tracking to/from, so I would not really bother adding workload by having them doubly defined using Nav2, especially on such a rather complicated departure.
As to Your second question: LOWI/Innsbruck has several very interesting approaches and missed approach/balked landing procedures. I recommend the KTI approach with a balked landing, engine failure shuttle procedure and climbout to RTT.
For example if You put VNY on NAV 1, showing track 255 on the HSI and additionally the same VOR on a RMI needle (if available) You have the first two legs to VNY and IPIHO covered. NAV 2 could show LAX track 323.
When You are established on LAX 323, depending on the onward route, switching NAV1 to VTU track 046 or GMN track 322 makes sense. And so on.
Fixes like SLABB, LANGE and BOGET are not only defined via crossing radials from other stations but also via DME fixes from the station You are tracking to/from, so I would not really bother adding workload by having them doubly defined using Nav2, especially on such a rather complicated departure.
As to Your second question: LOWI/Innsbruck has several very interesting approaches and missed approach/balked landing procedures. I recommend the KTI approach with a balked landing, engine failure shuttle procedure and climbout to RTT.
Last edited by Tu.114; 23rd Dec 2013 at 07:35.
