CFT3 in the wrong place?

Flying from CYXY to CFT3 and I noticed that Little Navmap puts it in the wrong place.

I don’t know if the data in the DB is incorrect or LNM is playing games with me.

Here’s what I’m seeing:

Perhaps there’s a typo somewhere in the lat/longs?

A post was split to a new topic: Cft3 post to be confirmed

Thanks Ian.

If I enable the “use Navigraph for navaids and procedures” option in LNM, the airport appears in the correct place. LNM also seems to be referencing a file at


If I enable the “use Navigraph for all features” option in LNM, the airport appears in the correct place, but it adds a new airport to the southeast.

Thinking that maybe there’s something amiss with the FMS data, I did a fresh install of the Navigraph data. Tests revealed that the mystery airport appeared again if I followed the steps above.

I dug into the sqllite files in LNM for Navigraph and found multiple references to this new airport that are tied to Navigraph, and are consistent to what I’m seeing in LNM.

Here’s the data from the airport table in little_navmap_navigraph.sqllite (831 is the airport ID for the mystery airport in question):

|831|831|1|CFT3|Finlayson Lake|||CAN|CY||0|0|0|0|||||0|0|0|1|0|0|0|0|0|0|0|1|0|0|0|0|0|0|0|0|0|0|0|1847|50|133.914001464844||1|||1|0||-130.774795532227|61.6922874450684|-130.532379150391|61.6509437561035|19.6060028076172|||8000 3094|-130.773895263672|61.6913871765137|

Here’s the data from the runway table in the same sqllite file. Removing this record removes the mystery airport from LNM but retains the real airport in it’s correct location.

476 831 951 952 1847 50 133.914001464844 0 0 0 -130.540069580078 61.6544609069824 -130.532379150391 61.6509437561035 3094 -130.536209106445 61.652702331543

Runway data from v_airport_runway in the same sqllite file:

|831|CFT3|Finlayson Lake|CAN|||1847|50||476|951|952|03|||
|831|CFT3|Finlayson Lake|CAN|||1847|50||476|951|952|21|||

The data in this table is consistent with what appears in the mystery airport

I’m happy to jump on a Discord video call and verify the data that I’m seeing on this end. I think there’s some inconsistencies between Navigraph data and what MSFS is providing, esp with runway numbers as yours are correct but MSFS isn’t.

Let me know. :slight_smile:

I can confirm that the runway coordinates are wrong but that´s not an issue from our data provider because Jeppesen doesn´t provide this airport. It´s a merge from another source. We will check this, possible we will remove this airport due this issue …

Anyway, thanks for the hint - when it´s possible, we correct it …

Ah ha! That must be it. Thanks Richard.

Appreciate the help.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.