Hi,
Recently a new app has appeared for SPQU, RNAV10
this app has its terminallegs waypoint ids fine but their coordinates are wrong in the procedure and is being showing wrongly inside the aircraft, and therefore not flyable.
Also this app (rnav10 and rnav28), and other more I’ve recently found appearing in airports in Perú are airline private charts (latam, jetsmart and star Peru) and not from the public official source. I’m not sure whether they should be included in the navdata.
Whoever posted them to you may be doing something not legal.
Hi,
Sorry, but I don’t really understand this posting. What do you mean by new app? What app do you mean?
Here is what I see in our chart app:
The path looks good, and the waypoints are correct.
Also, can you provide a few basics, like which sim you mean, which aircraft add-on you mean, whether you are using any 3rd-party sceneries,…
Could you take a few screenshots to show your issue?
Thank you
Richard
This is the real private latam chart. Flying the navigraph rnav10 in the fenix 320, QU622 is right at the runway, and the other waypoints are moved one step to the right. Don’t have de nd.db3 file in my phone to check it, but I’d say terminallegs have wrong coordinates. Later at home I can provide all data from the database
Also there’s no hold at geman in the real chart (only at the missed approach)
Here is how it is show in the aircraft (i’ve checked the DB, thought it was the TerminalLegs coordinates, but they seem to be correct, somehow it’s wrongly displayed)
I can confirm that I have also checked the waypoint coordinates, and I can´t see any issues here. So, the navdata seems to be correct.
Do you use any 3rd party scenery?
Cheers,
Richard
It’s a third party payware scenery, but airport is where it should be, not displaced.
As I “own” a virtual airline in IVAO (latamperuvirtual.com) and as I’ve had access to the private charts of latam, I’ve programmed myself that same approach (all database inserts) in the navigraph database for the fenix. My approach is well paint, so there must be something wrong in that approach. Will try and research why
I think I’ve found the reason.
QU426 doesn’t have good coordinates and is a little more to the East than where it should be.
The following two waypoints have good coordinates, but as their terminallegs are repositioned related to the distance to the previous waypoint., they are displayed where they shouldn’t
I’m asking a friend inside Corpac to check the proper coordinates of that waypoint. Will tell as soon as I get them.
Thank you very! much for your help in this case - much appreciated …
Cheers,
Richard
PS: I will remove the auto-close feature here
Hi
Here are QU426 real coordinates
-16.3297° -71.7756°
I guess that should fix that Rnav approach (I can’t test it as I’m out on a trip until next Saturday)
