I have data for the Mooney Bravo and want to build the performance files for it to use. I need to clarify one thing...
If I build the [CLIMB] portion by 1000 foot increments between 0 and 24000 feet, and want to build the [CRUISE] portion by 1000 foot increments between 5000 and 25000 feet and want to build the [DESCENT] portion by 1000 feet between 25000 and 0 feet does that work?
Every example I've looked at seems to have [CLIMB] up to a point BELOW [CRUISE] and then [CRUISE] above CLIMB up to the maximum for the aircraft [the Mooney is 25000 feet] and then has DESCENT starting under the [CRUISE] alititude.
I might want to climb to 22000 today, and only 10000 tomorrow, depending on where I am flying, and when I build the table information with both climb and cruise at 10000 feet, I seem to get the flight plan using the wrong data for that altitude if it is in for BOTH Climb and Cruise.
I would have thought that if I say cruise should be at 10000 feet the program would use CLIMB data through 9000 feet, use CRUISE data for 10000 feet, and use DESCENT data coming down from 10000 feet. The next plan may use the same aircraft but cruise at 15000 feet, so the plan should use that 15000 and the data for CLIMB through 14000, CRUISE at 15000 and DESCENT from that 15000, but I am not certain that is what is actually happening.
Of course I could have 15 different Mooney names and profiles, one for each cruise altitude, but that seems silly to me. Am I misinterpreting what I am seeing when I use the table I've constructed?
RsH
_________________ ===============================
If this is illegal where you are, do not read it.
|