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.

Small SID programming problem -450' Conditional Waypoint

Featured Replies

I figured out how to program SIDs and STARs. It's actually quite easy once you've got the hang of it.At any rate, I'm having a problem this bit of code for RKPK (Gimhae Int'l, Pusan).SID NKDG4A.TOPAX.N RNW 36L RNW 36R HDG 350 UNTIL 450 NAVAID KADCK 7000 FIX D230U NAVAID TOPAXThe main problem is this bit of code: "HDG 350 UNTIL 450."(Note that runway hdg is 001, and you're required to make the left turn to 350 immediately after take-off for obstacle clearance.)The problem is that the conditional waypoint (450) doesn't display properly on the Nav Display - it displays the waypoint about 750 feet (approx) **before** of the end of rwy 36, and just a little off to the left due to the hdg, which is fine. I wish I had a screen shot to show you just how funny the angle between the end of the runway and the 450' cond. waypoint looks.The interesting thing is that if I change the altitude in the conditional waypoint to, say, 800 feet, the waypoint in that case will display properly on the ND: it will in fact appear at some point well **beyond** the end of rwy 36.Any ideas on how to correct this?It's almost as if the conditional waypoint is calculated from the point of (calculated) rotation, not the end of the rwy or screen height.Bryan

Hate to burst your bubble but syntax will be different in SU2's SIDSTARS. [h4]Best Wishes,Randy J. Smithhttp://img.villagephotos.com/p/2003-8/196432/winglets_lg.jpg [h3] AMD XP 2200 |MUNCHKIN 512 DDR RAM |ECS[/b ][i] K7S5A MB[/i] |GF2 MX 32 MEG and still runs GOOD!|WIN XP PRO |MITSUBISHI DIAMOND PLUS 91 19"[/h3]

Randy J Smith

Hello BryanI've had a look at this point (450) on the ND and it shows probably where I would expect it. However it is not on an intercept heading therefore you wont be able to engage LNAV.Do you have a chart you could mail me and I'll have a look at a way around this.Simon

Hi Simon,Here's the link for the chart.As I say, the line connecting the floating waypoint to the end of rwy 36 goes "backward" about maybe 750' from the end of the rwy as displayed on the ND. I don't get this problem if I make the floating waypoint higher, ie., 800 feet.http://flyfreesky.com.ne.kr/korean/kimhae/10-3A.gif

Hello BryanTry KEEP HDG UNTIL 150 HDG 350 UNTIL 450, I see the backwards line on the ND too. The backwards line didnt make any difference in flight though. The line not following a smooth path in 180 curves is know to the team already, it may be a similar gremlin. You need to define the 165 hdg to KADUCK as well, let me know if you want help with this.Simon

Thanks, Simon, I'll give that a whirl and see what happens. Regarding the hdg of 165 to Kaduck, I've used the intercept radial command and while it worked ok, it just never looked that great. Hopefully the updated code in SR-2 will make it look better, smoother.Bryan

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.