Trouble at SEQM

[ubersu 23]

Flying the RNAV (RNP) X 36 approach to SEQM per the attached LIDO plate (SEQM RNAV (RNP) X 36 Approach.jpg), I see a break in the course line at QM003 (SEQM RNAV (RNP) X 36.jpg).  If I delete that waypoint and re-insert it (SEQM RNAV (RNP) X 36 ModQM003.jpg), the line completes correctly.  It seems that the aircraft doesn't know where QM003 is when reading the procedure, even though the coordinates given in the AIRAC data for the approach and match (with slightly different accuracy) those given in the waypoints.txt file:

APPTR,R36-X,36,ARNOK
IF,ARNOK,0.49861111,-78.11194444, ,0.0,0.0,2,25000,0,0,0,0,0,0,
TF,QM017,0.10241389,-78.47446111,0, ,0.0,0.0,0,0.00,2,18000,0,0,0,0,0,0,2.0
TF,QIT,-0.03846667,-78.51125833,0, ,0.0,0.0,0,0.00,2,17000,0,1,230,0,0,0,2.0
TF,QM001,-0.13347500,-78.48268056,0, ,0.0,0.0,0,0.00,2,14300,0,0,0,0,0,0,3.1
TF,QM002,-0.21593333,-78.49720833,0, ,0.0,0.0,0,0.00,2,13000,0,1,210,0,0,0,3.1
RF,QM003,-0.26887222,-78.48756944,1,CCW,152,4.6,2,12200,0,0,0,0,0,0,3.1
RF,QM004,-0.28911944,-78.47019167,1,CCW,132,4.6,2,11800,0,0,0,0,0,0,3.1
RF,EGOVU,-0.30472222,-78.42809722,1,CCW1,94,4.2,2,11100,0,1,180,0,0,0,3.1
TF,QM005,-0.30530556,-78.40165000,0, ,0.0,0.0,0,0.00,2,10900,0,0,0,0,0,0,3.1

and

 FINAL,R36-X,36,R,3,0, ,0,0,0,0
IF,QM005,-0.30530556,-78.40165000, ,0.0,0.0,2,10900,0,0,0,0,0,0,
RF,DABET,-0.25116944,-78.34899444,1,CCW2,360,3.1,2,10100,0,0,0,0,2,0,3.1
TF,RW36,-0.14265000,-78.35362500,0, ,0.0,0.0,0,0.00,1,7965,0,0,0,0,3,1,3.1
TF,QM006,0.02372500,-78.36072500,0, ,0.0,0.0,0,0.00,2,8310,0,0,0,0,0,0,1.0
TF,QM018,0.10252222,-78.43632778,0, ,0.0,0.0,0,0.00,0,0,0,0,0,0,0,0,1.0
TF,ILPEX,0.14519167,-78.53493611,0, ,0.0,0.0,0,0.00,2,13000,0,0,0,0,0,1,1.0
HM,ILPEX,0.14519167,-78.53493611,2, ,0.0,0.0,165,8.00,2,16000,0,1,230,0,0,0,0,
 

are correct.  I am using the NavdataPro 1508 AIRAC. Please see the attached files for illustrations.

Regards,

DJ

 

 

Please login to display this image.

Please login to display this image.

Please login to display this image.

[The Dude 6537]

I have also seen this problem at another airport. I will pass it on to the dev, he should be able to sort it out. Could take till SP4 I am afraid.

Thanks for reporting!

[ubersu 23]

Thank you kindly - it's an odd one.

Regards,

DJ