NPD-cycle1306_iFly737NG_MHTG-RNAV-approaches

[janar737 0]

Hello All,

Did anybody try to fly the RNAV 02 or RNAV 20 approaches to MHTG (Toncontin Intl, Honduras) with the iFly 737NG and NavDataPro cycle 1306? I am asking because I run into some serious problems doing so. Let me explain :

Already after loading these approaches in the FMC the path on the ND does not look trustworthy, with waypoints plotted far outside the expected trajectory and if I fly the MHTG RNAV 02 approach I end up continuous circling around the center point (TG0R1) of the LT arc between TG015 and TG014 and equally, if I fly the MHTG RNAV 20 approach I end up circling around the center point (TG0R5) of the LT arc between TG024 and TG023.

Does anybody encounter the same problems, or, equally interesting, does anybody have no problems at all with these approaches and can you fly them as intended ???

See you, Jan

[vonmar 8]

Jan,

I took a look and this is what I see (screenshot) on the ND and the distances between waypoints on the FMC.

[janar737 0]

Hi Vaughan,

It looks like you have the same problem as I have, because my ND shows the same picture.

To compare I add below the main part of the MHTG RNAV 02 approach chart .

See you, Jan

[PeterW 23]

Thx for reporting. I have to check it in detail, but it might be connected to a similar problem we are currently working with iFly on a fix. I'll keep you updated.

[easyaviation 0]

Same here. It looks like iFly's FMC causes this particular approach to be incorrectly draw as the issue occurs with both, Navigraph and Aerosoft databases.

PS: iFly AIRAC 1306 - MHTG - missing VOR DME 20 & VOR DME 02

[janar737 0]

Hello All,

Found a simple workaround to get these (and other RNAV approaches where the FMC 'goes wild' calculating rf-legs) working as intended. Just add the 'arrival' heading of the waypoint where the (1st)rf-leg starts

For MHTG RNAV 02 and RNAV 20 this can be done as described below.

Find the file MHTG.app (in FSX/iFly/navdata/STARS) and open it in Notepad

1. Go the line

R02,02,TG015,+14.173128,-087.323794,0,1,000,0,1,250,2,0,7000,0,0,000,0,000,000,0,

and change it to

R02,02,TG015,+14.173128,-087.323794,0,1,222,0,1,250,2,0,7000,0,0,000,0,000,000,0,

2. Go to the line

R20,20,TG024,+14.208308,-087.206603,0,1,000,0,1,220,2,0,6500,0,0,000,0,000,000,0,

and change it to

R20,20,TG024,+14.208308,-087.206603,0,1,209,0,1,220,2,0,6500,0,0,000,0,000,000,0,

Save the file and your are done.

See you, Jan

[vonmar 8]

I will just wait for the NavDataPro Navdata 1306 cycle update.

Besides, per the iFly forum there are two problems with approaches.

One is an iFly Gauge problem where CDU waypoints are disappearing. This gauge stuff will need a fix from iFly.

The other is this RNAV Navdata causing ... flying circles.

I assume it is a Navdata problem per the post on iFly forum.

If not, then it is an iFly problem executing the Navdata problem.

[PeterW 23]

I have solved the problem together with iFly, but we have to wait until they release a bugfix for the gauge. It will probably be part of their open beta version 3.1.3. This inlcudes also some other procedure improvement we could identify.

[janar737 0]

Hi Peter

Thanks a lot for your efforts

Hopefully the 3.1.3 update will land soon

See you, Jan