if your TOD is coming too late, check what constraints are set. They might be “at or above” constraints and hence, you will arrive high because it assumes you will be vectored. Change them to “at” constraints in order to hit everything dead on.
1 Like
Typical turboprop descent profiles do involve allowing the aircraft to accelerate to the barber pole (well, just short of) and then maintaining. I find that maintaining a lower speed and thus a lower rate of descent makes for a smoother and more predictable descent. 400-500 torque for the initial phase of the descent should see you down nicely at around 170 IAS depending on where you leave the power. The slower descent might help you. I’ve been using ~450 above FL100 and ~350 below FL100 and the NXi VNAV profiles have been spot on.
1 Like
It should correct the required rate of descent/GPA dynamically in relation to your speed. I’ve never come in high on VNAV.
1 Like
Fyi real life pilots that helps me to code FM and systems descend on full idle, you just mute the check gear aural by hitting the PFD alert button, and down you go…
Emergency descend is similar but you do flap 10, gear down, and down you go like a bullet is an IRL procedure.
Best,
R
3 Likes
Oh forgot to say for both operations you set FLC, for the first as required, for the second 168kts.
Best
R.
2 Likes
Thanks all for your posts. Clearly I have been descending wrong if full idle is a parameter in the VNAV calculation and the reason why I have been arriving high at BOD/approach fix. The upshot of this being I’m not carrying enough drag and covering the ground between TOD and BOD too quickly. That said, I hope that the VNAV takes GS into account during the descent to command the V/S that complies with the computed profile? If not, it has been a double whammy of descending too fast in a brisk tailwind not accounted for by either the pilot or automation! I will try flights with little/no tailwind component and headwind to see what happens. Back to basics!
WAIT! FLC NOT VNV for descent?
When they want to descend fast yes… you can use VNV if you prefer.
Best,
R
1 Like
I’m very certain it does. But more of a question for Working Title as this is G1000NXi functionality. Gotta say, I prefer using FLC to descend as well over VNAV. I can use the ALT SEL arc to make sure I hit any altitude restrictions.
1 Like
@SimbolFSReborn Is just wanna pop in and gratulate for your great aicraft you have done. It can be clearly seen, your put all your heart and soul into this. Masterpiece! Thank you 
4 Likes
Thanks again all for your thoughts. Taking the matter of brisk tailwinds off the table, was just able to complete a descent in VNV mode to IAF on schedule with power pulled back to just above that landing gear warning horn threshold torque of 300 lbs/ft. Pulling all the way back to full idle seemed too slow, so I went with this power setting to see if the VNAV calculated profile could be achieved, and it was. Could be that somewhere around this power setting could be considered “flight idle” rather than full idle? Anyway, mission accomplished with a nominal tailwind component of 6 kts. Will try headwind and tailwind flights next to see what happens in automation when I do my part of the piloting correctly. And to be clear, this is by no means critical of the model or the good work, just me getting comfortable in the airplane. Cheers!
1 Like
Just finished a short flight in headwinds. VNV worked ok; few observations:
- The FSR500 Airframe in SimBrief Descent Profile will default to 175 kts
- Reducing power too soon in anticipation of TOD doesn’t work, it’s not a jet!
- Reducing power too late after TOD earns an airspeed warning AND…
- A whole bunch of things cancel the VNV descent mode without warning!
- It would seem we can descend between flight idle (300 lbs/ft) and 175 kts
- The “banana” appears in VNV, so it is easy to monitor the automation.
Would be great if we can get a chime when the Garmin changes mode from what we had selected. Unless I am looking right at that part of the display, it’s easy to miss then have to chase the descent profile which is not great if it gets too far off. Anyway, this is the most comprehensive G1000NXi implementation I have flown with so most of this is about that, and the more I use it, the less I like it. But I love this FSR500 so far!
An idle descent would allow you to stay higher longer for sure. I’d probably do that if I were paying for fuel too!
Anyone else using VR with this one and find the FPS is far worse than others? It is such a shame, other than the poor FPS and the insane taxi speed lol, this is a fantastic airplane.
1 Like
You should be taxiing using beta-range to mitigate the powerful neutral thrust common to most turboprops.
How? with my honeycomb bravo there is only reverse detent, and then it is above taxi…
You have to map it to +100% to -100% and adjust your curve so beta range is say the bottom 20% of your axis. Or whatever you prefer.
Downside is that there won’t be a detent and you could easily go into beta during flight if you’re not careful. That is if you don’t mod your bravo, of course.
Or, map the detent to reverse thrust and then you move the lever forward to decrease the throttle.
1 Like
You can use F2 to go in to beta and the thrust lever for everything else
As for VR performance in our beta tests it was all ok, i suspect your VR settings are maxed out, use onebof the .LITE liveries if you want to keep those maxed andbit should help.
R.
The manual gives you some options on how to map this with throttle levers. There is detailed explanation on how to set it up. It is worth checking out because it will make the aircraft much more enjoyable for you.
2 Likes