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.

T/D way too early

Featured Replies

Hey T7 pilots, now that I am also an proud owner I have a question about the top of descent. It was calculated way too early.

 

I made a flight from KJFK to EHAM. I trie to explain the waypoint sequence with altitudes calculated by the T7:

 

On my cruise I had two stepclimbs from FL370 to FL 380 and than to FL390.

 

After the T/D symbol on the ND there where 4 waypoints I think before the STAR:

 

T/D

WPT 1 - FL390

WPT 2 - FL390

WPT 3 - FL390 and the next wpt had the first lower alt

WPT 4 - FL380 ...all other wpt had normal descent altitudes.

 

I ignored the calculated T/D and started my own descent with FLCH before WPT4. The VNAV deviation at the end where 14000 ft or so ^^

 

Now I search for the reason of it. I understand VNAV well I think, but I dont know what I have maybe done wrong... maybe you? :-)

 

Thank you!

Klaus Schmitzer

i7-14700KF 5.6GHz Water Cooled /// ZOTAC RTX 4070 TI Super 16GB /// 32GB RAM DDR5 /// Win11 /// SSDs only

DCS - XP12 - MSFS2020

 

 


After the T/D symbol on the ND there where 4 waypoints I think before the STAR:

T/D
WPT 1 - FL390
WPT 2 - FL390
WPT 3 - FL390 and the next wpt had the first lower alt
WPT 4 - FL380 ...all other wpt had normal descent altitudes.

 

I've never seen that... you should have descending crossing altitudes at all waypoints after the TOD symbol.

 

Try this:  Set up another flight at KJFK and enter the same route and preflight the FMS.  Now look at the LEGS pages and find the TOD and see if the same thing happens. Please provide a copy of your flight plan if you can reproduce this with it.

Dan Downs KCRP

  • Author

First I also thinked about winds but they where done by ASN and requested before. I dont think it can cause it.

 

@downscc: Will trie this asap!

 

Thank you guys

Klaus Schmitzer

i7-14700KF 5.6GHz Water Cooled /// ZOTAC RTX 4070 TI Super 16GB /// 32GB RAM DDR5 /// Win11 /// SSDs only

DCS - XP12 - MSFS2020

  • Commercial Member

 

 


WPT 4 - FL380 ...all other wpt had normal descent altitudes.

 

What color was this FL380? White or magenta?

Kyle Rodgers

  • Author

What color was this FL380? White or magenta?

Unfortunately I cant remember... maybe he was white.

What do you think about?

Klaus Schmitzer

i7-14700KF 5.6GHz Water Cooled /// ZOTAC RTX 4070 TI Super 16GB /// 32GB RAM DDR5 /// Win11 /// SSDs only

DCS - XP12 - MSFS2020

  • Commercial Member

Unfortunately I cant remember... maybe he was white.

What do you think about?

 

I'm guessing something in the nav data called for it (which would be displayed in magenta). Here at IAD, we had a STAR that had people descend pretty early on, level out a bit, and then descend again. I think that part of it has since been revised, but it was definitely one where it pulled you below your cruise alt pretty far out.

Kyle Rodgers

At EHAM, there isn't such a restriction. For arrivals from the USA, these are the first altitude restrictions of the STARs:

TOPPA @ FL250B

MOLIX @ FL230B

LAMSO @ FL230B

REDFA @ FL230B

Marc

I just flew the LAMS1A into EHAM last night... no problems. Descent started right off the UK coast as expected.

 

Again, please try to reproduce then share the specifics. We're just guess now.

Dan Downs KCRP

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.