Funnily enough, I have had this problem in real life with Dispatch giving bogus altitudes/routing for such a short flight. In reverse, from KBWI-KNGU, it computes a suitable altitude of 16000, but KNGU-KBWI it chooses FL290, which is not possible. Obviously I can manually put in an altitude of FL180.
On further inspection, looks like SimBrief chose an altitude that would work for the entire STAR, but the route enters the arrival at CAPKO which only requires to be at altitude 9000. So I think the system could be made smarter to consider this when automatically choosing a cruising altitude.
The problem here is likely that SimBrief currently doesn’t consider altitude restrictions on the SID/STAR. If it were able to consider the CAPKO restriction at 9000, it would probably have chosen a lower altitude.
In this specific case, the issue is exacerbated by the fact that you’re extremely light. 4 passengers, 0 cargo, and very little fuel on a B767-300 is going to climb like an absolute rocket. Ignoring the CAPKO restriction (as SimBrief currently does unfortunately), I have no doubt that FL290 is the most efficient altitude.
To be clear, that doesn’t mean that I would have chosen FL290 either, but SimBrief (like most flight planning systems) is tuned to find the optimum altitude. It’s very difficult to “teach” a computer to think like a human and have an opinion about the altitude it has selected.
I think the first step here will be to improve SimBrief so that it accounts for SID and STAR restrictions when determining the TOC/TOD points. That’s already on my to-do list, I’m just not sure how long it might be before I can work on it at the moment.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.