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.

Des Path Unachievable

Featured Replies

  • Author

My concern is i never had this b4 SP1Prior to the last update the FMC always calculated correctly and i never had des path message.the vnav would take me right down to vor loc and then i would manually take it in the rest of the way

John C

Try use 30!! According real pilots form this Forum this would be the standard CI! GOL in Brazil have used 27!
I could for the sake of reality yes, but I do not harm the environment neither I pay for the fuel and aboveall my trips are definitely quicker.Anyway I agree that the reality CI is between 20 and 30 yes.

I tried with starting the descent about 10 miles before TD .The descent was perfect till I entered the STAR.Then the plane did:- not slow down to the calculated speeds ( stayed 20-30 knots above it )- not descent fast enough ( descended at 1000ft/min max )I did not get a Des Path Unachievable message.When using the airbrakes the AT gave more power...The only thing I can do is slew down the plane for 1000ft just before it should capture the localizer.As I have better fps with SP1 I would like to stay with that instead of returning to HF4.All suggestions are welcome.And if someone wants to try the flight ( 50 minutes ) and see what happens I will post the info needed.

5950x3d 5.4-5.7 GHz - Asus ROG 870 Crosshair Apex - GSkill Neo 2x 24 Gb 6000 mhz / cas 26 -  MSI RTX 5090 Gaming Trio OC - 1x SSD M2 6000 2TB - 1x SSD M2 2800/1800 1Tb -  Corsair 5400  case - Corsair 360 liquid cooling set  - 3x 75’ TCL tv.

13600  6 cores @ 5.1 GHz / 8 cores @ 4.0 GHz (hypterthreading on) - Asus ROG Strix Gaming D - GSkill Trident 4x Gb 3200 MHz cas 15 - Asus TUF RTX 4080 16 Gb  - 1x SSD M2 2800/1800 2TB - 2x  Sata 600 SSD 500 Mb - Corsair D4000 Airflow case - NXT Krajen Z63 AIO liquide cooling - 

FOV : 200 degrees

My flightsim vids :  https://www.youtube.com/user/fswidesim/videos?shelf_id=0&sort=dd&view=0

 

  • Author
I tried with starting the descent about 10 miles before TD .The descent was perfect till I entered the STAR.Then the plane did:- not slow down to the calculated speeds ( stayed 20-30 knots above it )- not descent fast enough ( descended at 1000ft/min max )I did not get a Des Path Unachievable message.When using the airbrakes the AT gave more power...The only thing I can do is slew down the plane for 1000ft just before it should capture the localizer.As I have better fps with SP1 I would like to stay with that instead of returning to HF4.All suggestions are welcome.And if someone wants to try the flight ( 50 minutes ) and see what happens I will post the info needed.
I agree the problem starts when entering the STAR

John C

- London Luton rw 26 to Amsterdam Schiphol rw 06- Cruise altitude 25.000ft- Arrival wind : EastTake off and fly to cruise level 25000 at CLNThen :- SONDO .674/250----------83.4 nm to- SUGOL 267/11703------16.6 nm to- EH606 240/7185-------11.1 nm to- SOKSI 220/4000A------4.0 nm to- EH613 202/3212--------2.4 nm to- EH614 173/2900A------3.0 nm to- EH609 160/2000--------2.2 nm to- EH616 160/1310--------4.1 nm to- RW 06 49

5950x3d 5.4-5.7 GHz - Asus ROG 870 Crosshair Apex - GSkill Neo 2x 24 Gb 6000 mhz / cas 26 -  MSI RTX 5090 Gaming Trio OC - 1x SSD M2 6000 2TB - 1x SSD M2 2800/1800 1Tb -  Corsair 5400  case - Corsair 360 liquid cooling set  - 3x 75’ TCL tv.

13600  6 cores @ 5.1 GHz / 8 cores @ 4.0 GHz (hypterthreading on) - Asus ROG Strix Gaming D - GSkill Trident 4x Gb 3200 MHz cas 15 - Asus TUF RTX 4080 16 Gb  - 1x SSD M2 2800/1800 2TB - 2x  Sata 600 SSD 500 Mb - Corsair D4000 Airflow case - NXT Krajen Z63 AIO liquide cooling - 

FOV : 200 degrees

My flightsim vids :  https://www.youtube.com/user/fswidesim/videos?shelf_id=0&sort=dd&view=0

 

Maybe you are experiencing the idle thrust problem that other users found. Please confirm if when the problem begins, your idle is around 40% N1 with a clear (no flaps, no gears) configuration.Someone found that is linked to TAT temp, check if problem begins at around 2 or 3°C

Regards

Andrea Daviero

I tried with starting the descent about 10 miles before TD .The descent was perfect till I entered the STAR.Then the plane did:- not slow down to the calculated speeds ( stayed 20-30 knots above it )- not descent fast enough ( descended at 1000ft/min max )I did not get a Des Path Unachievable message.When using the airbrakes the AT gave more power...The only thing I can do is slew down the plane for 1000ft just before it should capture the localizer.As I have better fps with SP1 I would like to stay with that instead of returning to HF4.All suggestions are welcome.And if someone wants to try the flight ( 50 minutes ) and see what happens I will post the info needed.
I'm afraid PIC007's advice isn't very good and shows a lack of understanding.If you press DES NOW, and you're in VNAV PATH, it'll descend at 1000fpm until you reach an altitude restriction or intercept the descent path (this assumes the ALT in the MCP is set to a lower level). At this point you're no better off than if you'd just let the plane descend from its calculated top of descent point.If you're having trouble getting down, check this out http://forum.avsim.net/topic/344559-do-you-really-need-speedbrakes-video-part-2/

Jordan Forrest

I have had the same issue. I thought I had made some bad programming between UN623 and the STAR for ENBR RWY17. For the occation, a lot of the altitudes was AT or Above (A). Maybe I should have removed the A on a couple of them to force it.I noticed that the plane could have descended a lot faster than it did at the moment Des Path U was announced.
I had same issue yesterday when flying ENVA to ENBR.

Antonio H.

 

pmdg_j41_banner.jpg

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.