Hey all, hopefully someone can help with this.I've noticed some strange behaviour surrounding the JS41's FMS and it's interpretation of SIDS. As an example, flying the NZWN Runway 34 RUGDI3 SID yields some strange results.Here's the code for the Airac 0911 SID, I've checked it against documentation and the syntax certainly appears to be correct:

SID RUGDI3 RNW 34 TRK 341 UNTIL 2000 HDG 050 INTERCEPT RADIAL 010 TO FIX RUGDI FIX RUGDI AT OR BELOW 4000 FIX PPNB

This coincides well with the actual published SID:

• [*]Maintain RWY centreline to 2000ft[*]At 2000ft turn RIGHT, track 050

This has been noted regarding other aircraft too, read this:http://forums1.avsim.net/index.php?showtop...05&hl=ARINC(and you can search for other similar posts) and yes, you are stuck.

I have noted this too, and just manually fly the SID, or use the SID info input into the AP using HDG mode and/or NAVAID info...Works well with practice, and hones those skills...Conversations with a couple of ATPLs over the years on flights between the UK and Germany have indicated that the SID/STAR is cleared and programmed, though the actual flight path is a vectored departure or arrival...IVAO reflects this a fair bit as well I noticed...Andrew

The JS41 FMS does not have the power of the systems in the B737/747/MD11. According the the Bendix manual, it only provides fix-to-fix navigation When the (correct) synatx calls for a floating pseudowaypoint such as required in the TRK XXX INTERCEPT XXX RADIAL the FMS will not correctly interpret the command. It is possible to manually set up a track to intercept a bearing to a fix, we worked on this feature pretty hard during the beta testing, but it will not follow the sidstar procedure.I am updating my US SIDSTAR collection to provide full JS41 compliant procedures except for turbojet only procedures. However, this will take several cycles to accomplish.I think the actual FMS data, in this example, would have had RUGDI as the first fix in the flightplan and the crew would have had to either manually fly the heading and intercept the desired radial or set it up using the FMS feature (see pg 110 in the AOM on how to set up an intercept course to a waypoint).

I had noticed that the fms did that and just thought i was entering the sid information wrong so just did a manual departure. And to be honest never understood what the tkxxx really meant since I had never seen it in the fmc on my leveld as that is the only other add on i have for fsx.

Seems to be working for me.Though my Sid file was from cycle 0812.But the line instruction in my file looks the same as yours, and I was sitting at the Rwy 34 threshold.SID RUGDI2 RNW 34 TRK 341 UNTIL 2000 HDG 050 INTERCEPT RADIAL 010 TO FIX RUGDI FIX RUGDI AT OR BELOW 4000 FIX PPNB The FMS was programmed to handle that instruction, but maybe there's something in the file or database it doesn't like or that confused it ? I'm just guessing I dunno at the moment.But I agree with the orginal poster its not correct, the DTK is showing 182 in the FMS for some reason. Maybe somethingdifferent about the runway coordinates ?? Again just making a wild guess.Regards.Ernie.

Seems to be working for me.

Damn! Can we compare notes? In specific, I'd like to know the coordinates your files have for RW34 in NZWN.txt and in wpNavAPT.txtAlso, when lined up on 34, what do FSX and the FMS give as your coordinates?It makes sense, though, that an FMS for an aircraft of this size is not very capable with pseudowaypoints. I'm pretty sure, however, that a locally based JS41 flies the RNAV UNRIT2 SID off runway 16 in WN. It's issued the SID because it equipment line in the plan shows "G", and it doesn't appear to have issues flying it. I suppose it could have a different FMS (were they all delivered with this one?), or one could manually fly the intercept, and then transition to RNAV. Now I'm curious!In any case, thanks for all your help, at least now I know the limitations of the aircraft systems and can fly accordingly.Cheers,James

Damn! Can we compare notes? In specific, I'd like to know the coordinates your files have for RW34 in NZWN.txt and in wpNavAPT.txt

No rwy coordinates in my NZWN.txt file.wpNavAPT.txt its...WELLINGTON INT NZWN34 05951341-41.334939 174.806358109.9034100024

Also, when lined up on 34, what do FSX and the FMS give as your coordinates?

FSX: S41:20.10' / E174:48.38'FMS: S41 20.06 / E174 48.22 Regards.Ernie.

Hmmm, more or less exactly the same as mine. Ah well!