Even our Medevacs are required to keep under 250, unless they declared an emergency for rare case of life or death
Thatās right - thereās a speed restriction of 250 kias when under 10k. The climb profiles Iām using are from Cessna test data, which presumably means they tested with unrestricted speed / climb. IRL, you would have to stay under 250 until reaching 10k feet.
So is it possible to do 250/290/80 or 250/300/80, or must one stick to the 250/270/80?
You could do all three if you wanted. There are at least three climb profiles that Cessna tested for Longitude and provided data on - at least in the documentation I have. Itās also possible to do a 250/270/0.78 profile as well. Generally speaking, the results are fairly similar and the differences are in distance traveled during the climb and some slight differences in fuel consumption.
The more headwinds you have, the faster you want to climb to altitude, to lower your fuel consuption asap.
So headwinds would be 270/.78 & tailwind 300/.80 i guess
The Longitude I am using is not modded.
This thread is for the modded Longitude
As mentionned, this thread is for the modded longitude.
You should really try it, as one of the many fixes in includes, is the AP swaying
I will find the mod and apply it. Thanks for the help!
So happy youāre getting so much mileage out of the modded Longitude. What sort of performance decline from WT V5.1? Did you mean the sim frame rate or something related to the aircraft performance?
There is a recent conversation about an issue with limits on the allowed autothrottle N1% in the WT V5.1 config files, and a solution you could apply.
One question, where i can edit those files? can you tell me the route please? thank you
Please look through the forum entries for the past couple of days and you can find this information.
I was trying to tweak the āācrossoverāā value on the G3000 mod.
the default 29 375ā is too low, making the barber pole higher, and if youāre only paying attention to the BP youāll bust the 325 and get an overspeed warning
The perfect 325kt/m 0.84 crossover is at 30 660ā with no weather
while doing some tests, I realized that I cant held 0.84 with no warning below about 42 800ā, with auto-throttle
the warning starts earlier the lower you are
at 39 900ā its 0.839
at 37 500 its 0.838
at 34 500 its 0.837
at 31 100 its 0.836
so basically you cant really go at .84 before FL430
I was wondering if im the only one getting that?
I dont remember if it was like that before
Considering that 0.84 is max speed, I donāt think itās unrealistic that that speed is not doable in the climb. That is far above the high speed climb profile. Where did you get your data that 0.84 is possible in climb phase?
If Iām not mistaken, I think @genbrien is saying that either the Mach 0.84 overspeed aural alert trigger limit isnāt tracking with the reported Mach number in the PFD speed tape or the speed tape is going into barber pole before M0.84 is reached. In other words the aural alert and/or barber pole redline is being triggered before the aircraft reaches 0.84 and the problem is worse as the aircraft descends. Is this an accurate summary? @genbrien could you confirm which issue youāre experiencing (or if both)?
This
You cant fly a leveled plane at 0.84 below FL430 without having a warning (you might a little below, but itāll be a very tiny limit for ON/OFF warning)
Im just wondering if it was always like that, if its only on my end, or something changed
So, correct me if Iām wrong but is the 0.84 mach limit absolute, or does it depend on altitude, ISA, and other things which are accounted for in the barber pole? What Iām asking is in the real aircraft, is the barber pole āred lineā always at the same speed? Or does it vary?
Is the 0.84 published maximum always the maximum at all altitudes, or is it just that thatās the fastest the aircraft can go under specific circumstances, but sometimes the maximum is less than this?
Like, can I fly the Longitude at mach 0.84 at FL10 IRL? And if not, why not?
The way I read the WT G3000 update, they have fixed the dynamic barber pole redline so that it solves the problem Dakfly ran into a few months back.
Or am I reading it wrong?
I feel it is down on power at Cruise Altitude and not able to get to .840 using AT, so maybe it is a AT issue.
Did you read the last dozen or so posts where we discus the recent WT mod and how it limits cruise performance?