250/10000 limit on weird locations
-
Hi all,
Did a number of flights past weeks and I really love the Fokkers, but on some flights (mostly to EBBR), the 250/10000 limit is calculated mid STAR or even just before the final approach fix. This also results in the TOD being wrongly calculated (very/too late). Today I did a return flight from LOWW to LKPR and back, on the first leg everything was fine, on the return flight it happened again on the NER5N arrival for LOWW34, 250/10000 limit was calculated between waypoints where the speed restriction already was 230. On one flight from EHAM to EBBR the 250/10000 limit was just before the final app fix. I was able to take screenshots this time. It can be user error too of course in which case I appreciate some help to avoid it
-
This is a standard transition level change. Depending on the Fokker 100/70 the JF secs modelled on and the standard speed limitation in most places is 250 knots below 10000 FT. It does not account for the STAR.
The FMS will prioritise the descent profile over speed, it'll prioritise the speed that is a larger text over the speed limitation.
You can also adjust the speed limitation for below 10000 by selecting the line key to the right of the SPD/LIM.
Also all the height limit state 6000 FT and above. That and ABOVE is why the SPD LIM is in that place.
-
I don't see an issue with the placement of the LIM waypoint here, as @JabbyJabara says those are all 6000+ restrictions so you wouldn't expect to be at 6000ft until WW974. What was your cruise altitude for the flight?
As for whether the LIM point would reflect an earlier speed restriction, we had quite a bit of debate over this internally but found evidence amongst the documentation that it always will display the standard 250/10,000ft but the aircraft will stick to the procedure speed restriction.
