Wrong level calculation on westbound Carebeean flights

[tmncm 0]

Hello,

I was trying to make a flight between LPPT and TFFF and found that at a certain point of Atlantic PFPX was calculating odd FL, instead of even FL.

N0472F320 BUSE2P BUSEN DCT KOMUT/M079F340 DCT 38N020W DCT BEKUN/M080F330 DCT GOMOS/M080F350 DCT 34N040W 31N045W 27N050W/M081F370 23N055W DCT SESPO SESP6F

Everything is good until BEKUN.

I also try to override this changes using the second tab to fly BEKUN and GOMOS at FL340, 34N040W and 31N045W at FL360, and 23N055W at FL380. However, no matter what combination I do always that I make a speed/altitude change in advanced tab speed/altitude the only result is even worst:

N0473F320 BUSE2P BUSEN DCT KOMUT/M080F320 DCT 38N020W DCT BEKUN/M079F310 DCT GOMOS DCT 34N040W 31N045W 27N050W 23N055W DCT SESPO SESP6F

Can anyone of the developers help with this one?

Thanks for your time.

[valcas370 4]

The firts route has passed preliminary validation on CFMU using generic aircraft parameters.

[tmncm 0]

Hello,

Yes indeed, the FP can pass the CFMU, however, I think that CFMU will not evaluate direction and level of flight in MNPS/Oceanic airspace. CFMU can actually pass but I think the levels are still wrong.

This in an example of a LFPG-TFFF flight (same direction - westbound)

N0493F320 LGL UN491 KOKOS/M084F320 UN585 REGHI UN480 ETIKI/M084F340 DCT 46N015W 44N020W 40N030W/M084F360 35N040W 26N050W 18N058W DCT 1539N06006W FOF/0747

After ETIKI is always even.

But the more awkward is the fact even if I make a manual level change via the second tab all the compute flght is done at FL310 like posted above, witch let me believe it's a bug

[FlightSimSoft.com 283]

There has been a bug in the flight level allocation when using imported routes. Fixed in 1.05.

[tmncm 0]

There has been a bug in the flight level allocation when using imported routes. Fixed in 1.05.

Hello Christian, thanks for the update in 1.05.

I had computed the same flight and still have the same error when passing through BEKUN.

-N0463F390 BUSEN DCT KOMUT/M080F380 DCT 38N020W DCT BEKUN/M080F370 DCT GOMOS DCT 34N040W 31N045W 27N050W 23N055W DCT SESPO SESP6F

I had computed this example with no payload and after the descend from FL380 to F370, there are no more step climbs. If I compute the flight with payload he gives me a odd flight level resctrion in BEKUN and no more steps all the way.

However, I tried to compute a LPPT-KMIA flight also going thought LPPO airspace but this time with a manual route only with coordinates.

-N0467F330 BUSEN DCT KOMUT/M080F340 DCT 38N020W 38N030W/M080F360 38N040W 38N050W 37N055W/M081F380 35N060W DCT BALOO DCT ANTIG M328 BAAGR G437 ZQA FOWEE5

This flight plan is perfect, the FL is even all the way.

It seems that the problem resides in the fact that he becomes confused when switching from coordinates to intersections (from 38N202W to BEKUN) when overflying LPPO? Could it be?

[tmncm 0]

If it helps, I tried to switch from BEKUN DCT GOMOS and using a 37N030W in manual route and give me also a awkward result

-N0465F340 BUSEN DCT KOMUT/M080F340 DCT 38N020W 37N030W/M080F320 34N040W 31N045W 27N050W 23N055W DCT SESPO SESP6F

One more time the airplane descend from FL340 to FL320 then no more step climbs all the way to final destination

Thanks

[heidem 5]

Just thinking out loud. Please forgive me if it not relates to your issue

Portuguese airspace, which includes Santa Maria FIR works with different flightlevels.

Magnetic tracks from 90 degrees to 269 degrees use odd flight levels, while magnetic tracks from 270 degrees to 089 degrees use even flightlevels.

[tmncm 0]

Hello Heidem,

Affirm. Portugal is divided in 2 FIRs (LPPC and LPPO). LPPC is north/south RVSM as you said and LPPO is the traditional westbound and eastbound FL rule

The LPPC is well design in PFPX, at least in all my test, however I had found some issues when planning overflights in LPPO as states in my post