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.

Unable 270 Kts at XXXX

Featured Replies

 

 


STAR: simplifies a transition between en route and approach segments of flight.

Transition: simplifies a transition between en route and approach segments of flight.

 

EDDF is a good example of how the distinction between approach transition and STAR has been muddied, but we have plenty of that in the US.  US implementations have been easier to understand, for example the LAX arrivals do not distinguish between approaches; rather, each approach has an different approach transition to meet the STAR (e.g., RIIVR or SEAVU).  However, even the US is starting to blur the lines between STAR and approach at places like KATL, KDFW or KIAH where the STAR has different legs (e.g., left or right downwind or turn to base entry) to take you to the point where you get vectored to final approach..... these legs are not arrival transitions (they do not connect enroute to STAR:) nor are they approach transitions (they belong to the STAR not the approach).  I've yet seen an acceptable terminology for these.  I am curious as to how they are selected RW using ARINC format (not PMDG navdata format) in the FMS/CDU.

Dan Downs KCRP

  • Replies 33
  • Views 8.2k
  • Created
  • Last Reply

Top Posters In This Topic

  • Commercial Member

 

 


However, even the US is starting to blur the lines between STAR and approach at places like KATL, KDFW or KIAH where the STAR has different legs (e.g., left or right downwind or turn to base entry) to take you to the point where you get vectored to final approach.

 

Yeah. This is starting at IAD, too. The terminology is a little clunky because of it:

"Descend via the HYPER5 arrival, Runway 1L transition for Runway 1C."

 

 

 


I am curious as to how they are selected RW using ARINC format (not PMDG navdata format) in the FMS/CDU.

 

What do you mean here? The action of selecting it is the same, even though our formats in the background are different.

Kyle Rodgers

 

 


What do you mean here? The action of selecting it is the same, even though our formats in the background are different.

 

I assume the method is the same, but the terminology?  Navigraph encodes it as "HYPER5.01C" how does it actually look in the commercial product?

Dan Downs KCRP

  • Commercial Member

I assume the method is the same, but the terminology?  Navigraph encodes it as "HYPER5.01C" how does it actually look in the commercial product?

 

I thought they were the same. I have a request in to the next few cubes over to see the original data.

Kyle Rodgers

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.