Hi,
I’m reporting a wrong routing and missing speed constrains on the ORI6P departure out of LIME RWY28.
Attached you find a picture of the real plane ND and one of the PMDG. Both fly the ORI 6P. You will find the the real one is intercepting the bearing 067 to ORI NDB while the PMDG just goes Directly to the NDB. For your reference I also attach a Navtech chart where you can see that the inbound should be 067!
Furthermore looking at the FMC the first waypoint should say 180B/ 1180A instead 180/1180. Why? If you assign it as 180/1180 the airplane is forced to fly 180kts exactly and be at 1180 exactly at this given point. But we want to climb above 1180ft right? Most likely we will also be slower than 180kt because we just took of. That’s why.
The same applies for the waypoint ME611. It should be 210B instead of 210 exactly.
Please have a look at it and let me know if you need more information.
Hi,
this is a coding limitation in the PMDG syntax because you can´t code this in this form:
... TRK 282 UNTIL AT OR ABOVE 1180 SPEED AT OR BELOW 180 ...
That´s not possible even when correct. On the other hand you can also read the first altitude restriction as “not below 1180” because also on your chart you see the MNM 1180 that does only mean, you may not turn BEFORE you reached 1180ft - when you pass the 1180ft than you can proceed the turn. The speed restriction of max 180 kts are not possible due the syntax limitation as I have written above. I assume that the 210 kts in the FMC will be set automatically and come from the the ME611 waypoint but as you see in the coded line, we don´t have this speed restriction - only at ME611:
SID ORI6P RNW 28 TRK 282 UNTIL 1180 FIX ME609 AT OR ABOVE 4000 FIX OVERFLY ME611 SPEED 210 TURN LEFT DIRECT FIX ORINB
So, it´s coded correct, according the file-specification - that´s a combination of format limitation and possible FMC logic in the PMDG.
Cheers,
Richard
Hi,
According to PMDG support the problem is with the data that you provide. Because as you say the coding is: “DCT ORI fix” but it should be intercept 067 to ORI fix.
What needs to be done here? Can you get in touch with PMDG?
Best
Nils
Hi,
here are the coding from the AIP Italy:
You see on the last sequence the “path terminator” CF, which means “course to fix” - which means “067 to ORI” right and we have all this information but CF legs can only be coded in the PMDG syntax as “DIRECT FIX …” there is no possibility from syntax to say “course DIRECT FIX” or similar else.
Of course you can also code this as “intercept” for the PMDG- as an example HDG 037 INTERCEPT 067 TO ORINB but than you have the problem with the leg before because the PMDG syntax doesn´t allow to add a turn instruction with this kind of intercept and heading 037 is more than a 180° turn and the PMDG would it make possible in the wrong direction (shortest turn).
So, as a compromise, we code this as DIRECT ORINB without the course due the PMDG syntax limitation.
Cheers,
Richard
PS: … and by the way, when you fly this procedure you will see, that the PMDG will make the “intercept to” approx. heading 060, depending on your speed after ME611 - so with this compromise, the PMDG works fantastic
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.