Yes that is the case. I'm not sure if we'll be able to get the requested change into the 2.0 version, which is pretty much locked down now, but we should be able to introduce a more complex model that allows you to specify the IAS/TAS/fuel flow for different altitudes per power setting in the next version.

Thanks Tim,



So for using it at the moment, if I do three legs at different altitudes where I will have different IAS do I create three different cruise profiles with different IAS and then modify each leg to choose the correct cruise profile so that TAS is calculated correctly?



If that's the case (for the time being), can I request another small change to the new route box?



Ideally I'd like to be able select the aircraft, cruise profile and have an override cruise checkbox which would allow TAS and Fueldlow settings. And to top things off from something somebody else said if we could have a default winds setting (similar to what you have in the enroute conditions window) where we could set 000/0 if we want to do all planning on this route with a default of no wind.



Yours in anticipation ,



Derek...

Interesting, thanks. Our new flight modelling stuff will make it possible for us to introduce models of that complexity in the future but right now we've kept it simple and offered only power setting to IAS and fuel burn, IAS being automatically turned into TAS as necessary. This improves dramatically on our previous model but we want to take it one step at a time.

Hi Tim,

With our PA32 and FliteStar I have a constant power aircraft model where I set for each power different altitudes, prop, mp, tas and fuel burns for ISA, ISA-20, ISA+20. When starting the flight planning I enter the RPM and MP I'm going to use and FliteStar works out the rest for the different altitides I fly.

It also has a number of other methods, but that's the simple one I use.

Graeme, I've tracked down what you're seeing to two things. The first is a bug which has now been fixed. The second is that making the start or finish leg longer or shorter will produce minor variations in the total average GS of the leg because proportionally more distance covered during the leg will be at the (presumably faster) cruise speed.

Cheers!

Hi Tim,



Just to be clear, the issue I reported yesterday with maving a waypoint and seeing varying TAS and GS and wind 000/00 set - no other variables were changed, altitude, aircraft and profile remained constant.



--Graeme

G-AHAU, Andreas, Isle of Man

SkyDemon looks at the cruise profile you've set for a leg and uses the IAS that profile produces, converting it to TAS as necessary.

Perhaps our aircraft model isn't yet sophisticated enough to accurately model the aircraft you fly. How do you normally set the aircraft up for different legs? Do you fly a particular IAS or power setting or some other config?

Hmmm - OK - I'll need to figure out how to enter the information into the aircraft model for different IAS at different levels. Will SkyDemon select the appropriate cruise setting based on the level - ie if I fly one longish leg at 3000 and one longish leg at FL120 where both IAS and TAS and GS will be quite different

TAS is a function of IAS and the altitude you're at, so SkyDemon is able to calculate it pretty accurately at every point on your journey.

I'm really confused with how the plog calculates TAS as we can only enter IAS in aircraft cruise profiles. Any tips/tricks (I'm used to dealing with TAS when flight planning for FliteStar etc)