# 5% of the airports are missing runway coordinates in the CIFP files

**URL:** <https://forum.navigraph.com/t/5-of-the-airports-are-missing-runway-coordinates-in-the-cifp-files/16084>\
**Category:** General non MSFS data\
**Created:** [June 21, 2024, 11:01am UTC](https://forum.navigraph.com/t/5-of-the-airports-are-missing-runway-coordinates-in-the-cifp-files/16084 "2024-06-21T11:01:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![amelingu](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@amelingu](https://forum.navigraph.com/u/amelingu)\
**Post date:** [June 21, 2024, 11:01am UTC](https://forum.navigraph.com/t/5-of-the-airports-are-missing-runway-coordinates-in-the-cifp-files/16084/1 "2024-06-21T11:01:06Z")

</div>

Hello,

About the Native X-Plane data, I found this related topic :

> [@Missing runway threshold coordinates in XP11/XP12 data](https://forum.navigraph.com/t/missing-runway-threshold-coordinates-in-xp11-xp12-data/10790):
>
> For example at EGLC, runway 09 is missing fields 9, 10 and 11 (5.36 latitude, 5.37 longitude, 5.69 threshold displacement distance) (as are many other runways). 09 Jan 2019 Runway fields 9, 10 and 11 are no longer optional, but required …suggests you use a Laminar-provided parser to convert from ARINC 424 to the native X-Plane format? If so, could you ensure that you’re using the latest available version of said Laminar parser and, if necessary, kindly ask them to fix it so it produces …

I noticed too, that 823 airports have missing coordinates for runway thresholds (I have the full list if you are interested).

I understand that these coordinates are not mandatory for the sim to properly load procedures, but they become essential if we want to understand how runways might have been renamed when magnetic declination changed over time.

Moreover, these coordinates provide a strong validation basis for artists to place runways accurately. They are one of the key elements to ensure the airports are modeled accurately in X-Plane.

Finally, given the fact that some runways are completely missing from the CIFP files (for example at 0A7, 1N2, 31A, CAJ9, 5U1, 5NC2, LFEG, KEDW etc…), having missing coordinates makes it almost impossible to avoid certain traps when it comes to determining how runways have been renamed.

I really hope you could fix this in the coming AIRAC updates.

Best regards,  
Guillaume AMELINE

---

<div class="post-metadata">

**Author:** ![NAVData](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/navdata/32/30549_2.png) [@NAVData](https://forum.navigraph.com/u/NAVData)\
**Post date:** [June 21, 2024, 1:18pm UTC](https://forum.navigraph.com/t/5-of-the-airports-are-missing-runway-coordinates-in-the-cifp-files/16084/2 "2024-06-21T13:18:57Z")

</div>

Hi,  
the runways are part of the ‘APT.DAT’ file which are not part of the AIRAC updates. So, when you need the thresholds, please use this file, instesd the CIFP files. The runway “information” in the CIFP file has another function amd as you wrote are not mandatory to set.

Also, you can compare the charts with the data to see, if a runway ident is changed or not. Again, you should not validate this against the CIFP files.

Hope that helps  
Richard

---

<div class="post-metadata">

**Author:** ![amelingu](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@amelingu](https://forum.navigraph.com/u/amelingu)\
**Post date:** [June 25, 2024, 1:18am UTC](https://forum.navigraph.com/t/5-of-the-airports-are-missing-runway-coordinates-in-the-cifp-files/16084/3 "2024-06-25T01:18:29Z")

</div>

Hi, thanks for your answer.

Unfortunately, it is not very helpful.

That is precisely the apt.dat that I am trying to fix, because it does not follow the magnetic variations fast enough… it needs manual editing, Laminar Research approval against some outdated CIFP data and a scenery cut, which can take up to 3 years to properly depict an updated runway name.

Why do the CIFP files contain coordinates for 95% of the thresholds worldwide, then?

---

<div class="post-metadata">

**Author:** ![NAVData](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/navdata/32/30549_2.png) [@NAVData](https://forum.navigraph.com/u/NAVData)\
**Post date:** [June 25, 2024, 10:32am UTC](https://forum.navigraph.com/t/5-of-the-airports-are-missing-runway-coordinates-in-the-cifp-files/16084/4 "2024-06-25T10:32:01Z")

</div>

> [@amelingu](#):
>
> Why do the CIFP files contain coordinates for 95% of the thresholds worldwide, then?

It will be used for missed approach when some exist.

Cheers  
Richard

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/1X/4cc83e90d70ab312b1bd2d7527bddad309607265.png) [@system](https://forum.navigraph.com/u/system)\
**Post date:** [July 2, 2024, 10:32am UTC](https://forum.navigraph.com/t/5-of-the-airports-are-missing-runway-coordinates-in-the-cifp-files/16084/5 "2024-07-02T10:32:06Z")

</div>

Closed on July 2, 2024, 10:32am UTC

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