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.

Fenix & iFly 737 MAX STAR Discrepancy

Featured Replies

Random question here.   My home airport is Providence, RI (KPVD) and I fly into quite a bit with the Fenix and iFly.   The standard STAR for Providence when coming up the coast is the JORDN2 arrival.   It's a very simple STAR, pretty much just hit waypoint JORDN at 11,000' and you have one other waypoint and that's it.   

Question is - in both the Fenix and iFly, when using that STAR, the FCM has me much higher at JORDN, typically around 17,000' which doesn't give me much time to descend to the correct approach altitude.   I can easily overide this in the FMC but I'm just curious why both aircraft don't reflect the hard limit that is shown in the STAR?  Is this a glitch or is this accurate RL behavior? 

39 minutes ago, 11bee said:

JORDN2

The chart says *expect to cross at*. This kind of info is not coded in the database. You can find that often in the US.

cheers,
NiIs U.

AMD 5800X3D | 32GB DDR4 RAM @ 3200MHz | RTX 4070 12GB @ 1920x1050px

5 hours ago, 11bee said:

Random question here.   My home airport is Providence, RI (KPVD) and I fly into quite a bit with the Fenix and iFly.   The standard STAR for Providence when coming up the coast is the JORDN2 arrival.   It's a very simple STAR, pretty much just hit waypoint JORDN at 11,000' and you have one other waypoint and that's it.   

Question is - in both the Fenix and iFly, when using that STAR, the FCM has me much higher at JORDN, typically around 17,000' which doesn't give me much time to descend to the correct approach altitude.   I can easily overide this in the FMC but I'm just curious why both aircraft don't reflect the hard limit that is shown in the STAR?  Is this a glitch or is this accurate RL behavior? 

Perhaps has something to do with programming the FMC/MCDU for that STAR and transition. In a scenario landing for RWY 5, at JORDAN, it is "expected to cross at 11000" not a hard altitude, so the FMC/MCDU is looking ahead to find a hard altitude. In our case, the next hard altitude is at CUTSI (2000 ft), and along that STAR, with the transition, we really have no other mandatory crossing ATC restrictions. So, when the T/D is computed for an "idle" descent, your altitude might vary above JORDAN due to other factors. In my case, in reference to aircraft loads and weather conditions for RWY 5, IT DID COMPUTE 13,500, and for RWY 23, with PVD transition, it was FL210, my CRZ ALT. Now, if you want to cross JORDAN at 11000, just put a hard altitude at that point.

747 Captain for the last 39 years, and still learning. 

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.