Hmmm, engines on IDDLE, no noise, no fuel consumption, no emmision - no problem.
I too late cancelled EXPED descent. With better planning, this shortcut is possible without break the rule 250kts under FL100, but impossible keep 210 kts over SPR.
- Code (): Select all
IRL, I would reject advice for that shortcut, but IMHO, any ATC will not issue that advice
For the passengers is 6000 fpm EXPED descent on speedbrakes bit uncomfortable.
EDIT :
merspieler wrote in Tue Jul 20, 2021 4:47 pm:Fly AKITO1N arrival using your calculated TOD from lets say FL370. Once over AKITO, fly direct SPR and the stright in runway 23(simulating direct in radar vectors)... Try it out... You will have trouble if you're higher than about FL250 or so over AKITO.
Based on the alt restriction at SOVAD (7000ft) I'd expect you to be at least at around FL320 at AKTIO.
Why don't you record and share your _FIRST_ attempt?... and we shall see...
Here is video :
https://www.youtube.com/watch?v=s5HtVs5HHmEAnd some resources :
AKITO STAR -
https://www.vacc.ch/file/357, chart date 2019-04-25
ILS22 approach -
https://www.vacc.ch/file/10, chart date 2020-12-03
Conclusion :
It was my first attempt for that large shortcut, I expected Go-Around.
In the approach chart I found speed restriction 210 kts at SPR, this is impossible to comply with this shortcut.
- Code (): Select all
But again, initial TOD has been calculated for full AKITO STAR, not shortened by 40 nm.
If I would start descent 67 nm before AKITO according with SEC-FPLN, all would be OK without any speeding and other constraints violations. This shortcut is possible only in the sim, not in the real plane with 160 screaming passengers behind my back. TOD calculation is perfectly usable and it is very good aid for the pilots.
I hope, FG A320family will obtain TOD (and TOC) prediction and full vertical navigation in short time, with these features will be fully comparable with other payware (FSL, Aerosoft, Tollis etc.) for commercial sims.