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.

Issue with flightplan FBW 320N

Featured Replies

Why is the flightplan (see below) in the MCDU only displaying it correct for 2 seconds in the Flightplanner screen.
After two seconds it's changed into the flightplan as you can see below.
It should go from DENUT to ATWIT as programmed in the MCDU.

spacer.pngspacer.png

Edited by altenae

MSI Tomahawk Z790, I7-13700K, DDR5 6000mhz, MSI 4090, 3x SSD 980 PRO, Corsair 360 Liguid CPU cooler, Corsair H1200V2 power.

Hello altenae ,

I did a quick route , all ok (screenshot).

Would need more information on your data entry.

 

spacer.png

 

Best Regards,

Vaughan Martell  PP-ASEL KDTW

  • Author
2 hours ago, vonmar said:

 


Hello altenae ,

I did a quick route , all ok (screenshot).

Would need more information on your data entry.

 

spacer.png

 

It was a flight from LEAL (runway 10) to EHRD (ILS-Y 24)
Why the sharp turn to EHRD and nog going via ATWIT

Edited by altenae

MSI Tomahawk Z790, I7-13700K, DDR5 6000mhz, MSI 4090, 3x SSD 980 PRO, Corsair 360 Liguid CPU cooler, Corsair H1200V2 power.

ATWIT is your final approach fix it's only like 10nm from Rwy24 threshold, but btw DENUT and ATWIT you are missing an entire STAR, so you are coming at almost 180° from your next leg and final landing course : DENUT -> ATWIT is 040ish then you turn left almost 180 degrees to ATWIT -> RWY24 on a 240 heading, that's why it can't be displayed correctly.

LNAV calculation doesn't yet include predicted speeds (which is actually VNAV calculations), so it thinks you're flying the turn with 300kts and therefore tries to draw a very early turn (because otherwise it would overshoot the turn completely).
It will be drawn correctly once you are at the actual speed down there, so nothing to worry about.

For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.

5 hours ago, Fiorentoni said:

LNAV calculation doesn't yet include predicted speeds (which is actually VNAV calculations), so it thinks you're flying the turn with 300kts and therefore tries to draw a very early turn (because otherwise it would overshoot the turn completely).
It will be drawn correctly once you are at the actual speed down there, so nothing to worry about.

Important to note that this is also not really an ideal path which you would keep IRL either.

 Airbus LNAV does not do anything magical with sharp turns, if it overshoots, it's not gonna try anything clever.

Developer - FlyByWire Simulations

11 hours ago, altenae said:

Why is the flightplan (see below) in the MCDU only displaying it correct for 2 seconds in the Flightplanner screen.
After two seconds it's changed into the flightplan as you can see below.
It should go from DENUT to ATWIT as programmed in the MCDU.

spacer.pngspacer.png

Did you delete a discontinuiity ? This is not routing I'd expect in a valid flight plan.

Developer - FlyByWire Simulations

  • Author
6 hours ago, holland786 said:

Did you delete a discontinuiity ? This is not routing I'd expect in a valid flight plan.

No I did not. 

I have flown the flightplan and when I arrived at that point it was correct. 

Just like "fiorentoni" posted:

It will be drawn correctly once you are at the actual speed down there, so nothing to worry about.

MSI Tomahawk Z790, I7-13700K, DDR5 6000mhz, MSI 4090, 3x SSD 980 PRO, Corsair 360 Liguid CPU cooler, Corsair H1200V2 power.

Archived

This topic is now archived and is closed to further replies.

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.