Can anyone please explain the correct procedure for departing YBCS RW15 using the SID shown below? I've also shown what I see in the FMS. I'd like to be able to set up a realistic departure but not sure how to achieve this.

 

 

every city in Oz has a RADAR SID...it is a SID where you will be given radar vectors, you depart on a certain heading with certain restrictions, and then you turn to whatever radar vectors you are given.

 

In the example above, when yo uline up, tower would tell you..."ABC, turn left heading 020, runway 15, clear for takeoff"...

 

What you do is depart, climb at 4% gradient to 600ft heading 149 (runway heading). then either passing 400ft or at 2.5DME, you turn heading 020 as instructed. The departures controller will then give you further vectors.

I'll split the departure into two things:

Lateral navigation, and,

Vertical navigation.

 

Lateral Navigation.

>> Track 149 degrees

>> Turn left onto your ASSIGNED HEADING (between 350 deg and 030 deg) AFTER passing 400ft, or passing the Departure End of Runway (DER), which is 2.6 NM DME from the CS VOR.

>> Maintain ASSIGNED HEADING.

>> When directed to, contact departures for further vectors.

 

>>>> Lateral navigation NOTES: (which appear at the top, right hand corner of your chart)

- When turning left, a minimum bank angle of 25 degrees shall be used until on ASSIGNED HEADING.

- Maximum Indicated airspeed is not to be greater than 190 knots until on ASSIGNED HEADING.

 

Vertical Navigation

>> You are required to climb at 4% climb gradient until you reach 600 ft

>> After 600ft, you are required to climb at 3.3% climb gradient

 

>>>> Vertical navigation NOTES:

- Charts usually show a little climb gradient box, which will show Vertical Speeds for different ground speeds. From that, you can determine if you will be able to achieve the required climb gradients.

 

Mike McKenna. (see above explanation. Much more simple and easier to understand).

It looks like the SID is not coded correctly. Where does that 080 TRACK come in? And there's 0 length to the 030 HDG. Usually that's followed by a DISCO.

 

If you can't find someone to fix the SID, then you could simply fly the SID in HDG SEL.

You have chosen the SWIFT7 departure in your FMC which is a completely different procedure.

 

I am not sure if the CS9 is programmed in the database, if not, select the runway only and fly the departure manually - or program it in your FMC manually using the numerous methods.

All you have to do on this SID is turn onto the appropriate heading... you might find that HDG SEL is a much better tool for this than LNAV!

 

As others have mentioned, this is a Radar SID. It is of absolutely no use unless there is a radar controller present. If there is no appropriate SID for your departure (highly like at Cairns ) simply take off, avoid the hills off to the west and south and join the magenta line!

Can anyone please explain the correct procedure for departing YBCS RW15 using the SID shown below?

 

 

 

 

1: Takeoff.

2: Fly straight ahead till you pass 400ft or the end of the runway. If you get to 400ft before the end of the runway, start turning. If you get to the end of the runway before you reach 400ft, start turning.

3: Turn away from the west and south without hitting hills.

4: Continue in Heading mode on one of the 4 headings. 350° 030° 070° or 329° depending on which runway you took off from and the direction to your next waypoint (or ATC assigned heading).

5: Wait for Air Traffic Control to do something else.

 

6: do that something else ATC told you do.

7: - When ATC tell you to track direct to a waypoint and resume own navigation, line select the next waypoint in the FMC's leg page, and then engage LNAV.

 

If you don't have Air Traffic Control, just follow the heading appropriate for the runway you took off from till you reach about 6000ft, then complete step 7

 

If you are using the default FSX Air Traffic Control, consider treating it as if there is no Air Traffic Control, instead FSX Default ATC is best considered Air Traffic Trololol. It may well fly you straight into hills.

Gents, thank you for your responses. I have been having a closer look at the SWIFT7 SID which would appear to be coded correctly (AIRAC cycle : 1212)...

 

RNW 15 TRK 149 UNTIL 2.6 FROM FIX CS SPEED 190 HDG 030 INTERCEPT RADIAL 080 TO FIX CS TRK 080 UNTIL 4000 TURN RIGHT DIRECT FIX SWIFT

 

...although not sure why the SPEED 190 constraint is needed.

 

As we can see the FMS is unable to turn to a 030 heading (or track). I even tried using the SWIFT7 departure with the MD11 and get the same results (image below). I then tried testing various modifications to the SID and would like to present two cases here in relation to lines 1 and 2 on the LEGS page...

 

RNW 15 TRK 149 UNTIL 410 HDG 015 UNTIL 3000 TURN RIGHT DIRECT FIX SWIFT

 

 

 

RNW 15 TRK 149 UNTIL 410 HDG 015 UNTIL 7000 TURN RIGHT DIRECT FIX SWIFT

 

 

 

It appears that as I increase the altitude constraint (from 3000 to 7000) I get closer to achieving a heading of 030 which suggests the altitude is a limiting factor on a heading change from the RW track.

 

Here is the SWIFT7 SID loaded on the MD11...

 

 

 

This is really interesting and I'm hoping that someone on the forum might be able to shed some light on this.

INTCPT is not a waypoint or even a specific fixed location. The MD11 indications show pretty well correct for being on the ground still. After it gets airborne, the F/D will request a left turn which will continue to turn left till it is about to intercept the 080 radial out of Cairns, then it will command a right turn to line up with the 080 outbound course to 4000ft.

 

I notice the 737 is missing the INT(ercept 08) order. Not sure why this is so. I'd fly it to see what happens. Remember that Left turn to (through) 030 is important, there's hills higher than your aircraft is at that point.

 

The FMCs (should) concentrate on the "intercept 080 outbound course" thing more than the "heading 030".

 

The actual SID chart has a maximum speed of 190 knots till tracking 030. This is so you have a turn which is of a certain radius. If you flew the turn at 250 knots you might find some terrain looking to spoil your day.

 

There may be an opportunity here to also tune the VOR 113.0 & set course 080 and monitor the raw VOR/DME data on the First Officers side to see how the route flown (directed by Flight Director) equates to the raw data of the 080 radial intercept.

 

I notice the 737 is missing the INT(ercept 08) order. Not sure why this is so. I'd fly it to see what happens. Remember that Left turn to (through) 030 is important, there's hills higher than your aircraft is at that point.

 

Trent, I'm still a little unclear what's actually happening with this SID. It appears to have the the intercept...

 

RNW 15 TRK 149 UNTIL 2.6 FROM FIX CS SPEED 190 HDG 030 INTERCEPT RADIAL 080 TO FIX CS TRK 080 UNTIL 4000 TURN RIGHT DIRECT FIX SWIFT

 

Here are some screen images of the departure...ignore my speed which I have set too low.

 

Before take off

 

 

Turning to 030

 

 

AP Engaged

 

 

LNAV engaged - starts to turn towards SWIFT

 

 

Continues turn towards SWIFT - Intercept not achieved

I dont know how they do it in real life but i always fly the swift 7 dep manually, . I noticed in the NGX introduction that it says to arm the lnav on the ground, the intercept course must be within 5 degs of the runway heading, maybe that has something to do with it

I take off at 500ft turn left to 030 degrees,fly to intercept the 080 radial line of the cs vor, then fly the radial to 4000 ft then turn right to swift

jeff

As i was typing you posted Tom, if you are engaging lnav pn air it says in the introduction that it has to be less than 90 degs, i dont know if that is the problem its only a suggestion.

jeff

If you get to 4000ft before you get to the 080 radial, technically you can track direct swift from that point. The FMS will do this (I hope, Havn't tried).

 

If you are at 4000ft in that last picture, that's normal behaviour.

 

If it's turning direct SWIFT before 4000ft is reached, then the FMS is doing it wrong. Maybe due to procedure design, maybe due to ... dunno. But 4000ft = Direct Swift even if you have not touched the 080 radial line.

 

The 3rd picture however (autopilot engaged, heading select 030) is a little worriesome, The 4000ft marker is clearly not alligned with either 1: The CS 080 radial, or 2: a position on a 080 radial away from your aircraft. I would have expected one of these to be the case (the first one imo). and then as you hit 4000ft the magenta line would switch to direct track SWIFT. Maybe try holding altitude at 3000ft (below hills omg) and seeing what it does there? (yeh I'm not optimistic at the moment)

If you get to 4000ft before you get to the 080 radial, technically you can track direct swift from that point. The FMS will do this (I hope, Havn't tried).

 

I do get to 4000 before the intercept so perhaps I need to try your suggestion and maintain 3000 and engage LNAV while I'm heading 030. It still is a little puzzling though.

 

I noticed in the NGX introduction that it says to arm the lnav on the ground, the intercept course must be within 5 degs of the runway heading, maybe that has something to do with it

 

I used to arm the LNAV on the ground but not since using FS2Crew where Heading is selected before LNAV (although still trying to understand the proper flow for this). I suppose if I use Cut Back on the TO then my rate of climb will be lower and I might get to the intercept before 4000 on Heading 030, then fly 080 until 4000 then engage LNAV. Or just fly manual until 4000 but I'm more interested in the behaviour of the SID in the FMS (per my earlier screen shots). Interesting...

I believe there is an error in the navigraph data for the SWIFT 7 departure. Here's how I generally fly the procedure.

• Prior to departure set the active NAV 1 frequency to 113.00, set course bug to 080°, set heading bug to 030° and Arm VNAV leave LNAV for now.
  
• Depart from RWY 15 hand fly the left turn to 030° maintaining a minimum bank angle of 25°.
  
• Once Tracking 030° arm HDG SEL and VOC LOC and engage A/P CMD A
  
• Once above 4,000' AND established the CS 080° Radial open the FMC LEGS page
  
• Select LSK1L twice (or whatever happens to be next to SWIFT). Execute the Modified route and arm LNAV. the autopilot should start tracking directly to SWIFT.