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.

Wild target altitude assignments on a route

Featured Replies

Using X-Plane 12.3.3 and AIRAC 2513 with 0.2.7A PIlotATC

FMS plan generated from Simbrief is:

I
1100 Version
CYCLE 2513
ADEP KMFR
DEPRWY RW14
SID JKSN1
ADES KSEA
DESRWY RW16R
STAR HAWKZ8
STARTRANS BTG
NUMENR 6
1 KMFR ADEP 1335.000000 42.374964 -122.873289
3 OED DRCT 17000.000000 42.479575 -122.912933
11 CUTTR V595 17000.000000 42.689275 -122.728519
11 RENAA DRCT 33000.000000 43.441561 -122.411128
3 BTG DRCT 34000.000000 45.747811 -122.591536
1 KSEA ADES 2900.000000 47.449889 -122.311778
 

Actual Kawkz approach:
https://www.1800wxbrief.com/Website/aip/tpp/00582HAWKZ.pdf
https://www.1800wxbrief.com/Website/aip/tpp/00582HAWKZ_C.pdf

 

Actual target altitude assignments on import of the .fms file:

R14: 1335
alt 1800:2100
int: 4000
OED: 7200
CUTTR: 17999  (show alt restrictions between 10500-17999; in reality it is MEA 10500 northbound, but the limit of 17999 appears to be because it is a waypoint on IFR low charts; IMO there should be no upper restriction here; note LNM also shows this restriction.)(?)
RENAA: FL 340
BTG: FL 340
PTERA: FL340
TOD: FL 340
KRIEG: 6000 (MEA is 10000)
HAWKZ: 6000 (crossing restriction is A12000)
LIINE: 6000
PIKEZ: 15000  (A12000/B15000)
COFAY: 6000
BREVE: 11000 (A10000/B11000)
NETTZ: 6000 (A8000)
KWEST: 6000 (A7000)
VASHN: 6000 (6000 hard)
KSEA: 432

The database seems to have the crossing altitude restrictions right, but P2ATC seems to only respect the Below constraints (if started out above, it will go to at least the below constraint).  If there is no constraint, it seems to pick the hard altitude at the end of the arrival.  (In reality wouldn't the restriction on COFAY be A(min(prev.waypt,next.waypt))/B(max(prev.waypt,next.waypt)) ? Above constraints aren't respected at all, and it doesn't seem to interpolate the target altitude for a straight line distance between the two waypoints which is what I would expect.  I can't seem to override the target altitudes.  When I do, it just goes and lighlights the "alt" line above.

How can I fix P2ATC to get a better descent profile?

Edited by DrSoftware
typos

  • Author

Another example:

On BRIXX4 arrival to KSJC between CORKK and BRIXX.  BRIXX has a hard altitude of 12,000 ft and a hard speed of 250K.  Yet, ATC says "maintain 17000 feet" (needless to say I was already well on my way down to 12,000)

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.