Wrong time calculation at end of approach segment (TNCM ULUBA1 via MNOLO)

[albertom]

LFPG - TNCM

Route: N0448F360 LGL5A LGL UT176 ROLEN UZ15 DIDAK DCT AKEMO DCT RIVAK DCT SIVIR DCT PASAS DCT 44N015W 42N020W DCT VFL DCT 38N030W 35N040W 33N045W 31N050W 27N055W DCT RKDIA M576 MNOLO ULUBA1

Cost index 15, passengers 221, cargo 770, fuel 45500kg

 

Before loading the STAR and approach for TNCM  (FMC route loaded up to MNOLO)  the estimated times on the FPLN page were correct, including the last estimate for TNCM. The fuel prediction page also showed a plausible value for fuel remaining at destination (2.5)

After loading the STAR and approach, all time estimates seem correct up until short final, but for some reason the very last little segment from 700ft to the airport has an estimate of 3 hours! Consequently, the fuel prediction page also shows a big negative value for fuel at destination, based on this erroneous time.

 

 

 

Despite this I'm having a blast with the A300. Many thanks for the work done so far -- I post this more out of curiosity than for actual need of a fix.

 

[albertom]

I think I found my own answer. There are two fixes called OTMOT. One is on the approach shown above after MNOLO, the other is significantly to the South.

I think the A300 is having trouble resolving this ambiguity. What's interesting is the map on the ND clearly shows which fix is the problem. The FPLN page on the other hand seems to get it right (segment TO and FROM OTMOT have correct enroute times) but then the last leg is completely off.

[richboy2307]

Hi @albertom

We'll take a look at this. Can I also confirm are you using Navigraph or default navdata? 

Thanks!

[albertom]

Hi,

MSFS base navdata updated to 2405

Edited June 7, 2024 by albertom