# Airway N603 missing in data

**URL:** <https://forum.navigraph.com/t/airway-n603-missing-in-data/23985>\
**Category:** General non MSFS data\
**Created:** [July 31, 2026, 5:39am UTC](https://forum.navigraph.com/t/airway-n603-missing-in-data/23985 "2026-07-31T05:39:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jjgonzalezt](https://avatars.discourse-cdn.com/v4/letter/j/c68b51/32.png) [@jjgonzalezt](https://forum.navigraph.com/u/jjgonzalezt)\
**Post date:** [July 31, 2026, 5:39am UTC](https://forum.navigraph.com/t/airway-n603-missing-in-data/23985/1 "2026-07-31T05:39:03Z")

</div>

Hello,

I was doing a flight that arrived in EKCH and realized that airway N603 was missing.

The airwway is located in EKDK FIR and starts at RAMUD waypoint and ends in TNO VOR.

This data is available on the Dannish AIP [https://aim.naviair.dk/media/files/fsdt4pb00xm/AIP\_DK\_AIRAC\_AMDT\_09%20JUL2026\_SUP\_09JUL2026.pdf](https://aim.naviair.dk/media/files/fsdt4pb00xm/AIP_DK_AIRAC_AMDT_09%20JUL2026_SUP_09JUL2026.pdf) on section ENR 3.2-18

 ![Screenshot (10)](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/2/e/2ead3e67635ea99e8d55265df2b18dc1b532fa62.png)

---

<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:** [July 31, 2026, 9:30am UTC](https://forum.navigraph.com/t/airway-n603-missing-in-data/23985/2 "2026-07-31T09:30:08Z")

</div>

Hi,  
The airway is present in our source, so could you provide more details about the sim and where you’re missing this airway?

Thank you  
Richard

---

<div class="post-metadata">

**Author:** ![srcooke](https://avatars.discourse-cdn.com/v4/letter/s/9d8465/32.png) [@srcooke](https://forum.navigraph.com/u/srcooke)\
**Post date:** [July 31, 2026, 10:53am UTC](https://forum.navigraph.com/t/airway-n603-missing-in-data/23985/3 "2026-07-31T10:53:03Z")

</div>

N603 exists in NG between TESPI and TNO VOR, the RAMUD - TESPI leg is missing in NG charts map, PFPX and PMDG.

 ![Screenshot 2026-07-31 115059](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/c/c/ccfe7a217427e1952e2cbe767371b6ec0f0e7511.png)

Steve

---

<div class="post-metadata">

**Author:** ![Rodeo314](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/rodeo314/32/103_2.png) [@Rodeo314](https://forum.navigraph.com/u/Rodeo314)\
**Post date:** [July 31, 2026, 8:29pm UTC](https://forum.navigraph.com/t/airway-n603-missing-in-data/23985/4 "2026-07-31T20:29:34Z")

</div>

The document is a bit old but appears to still be valid, I cannot find any newer and/or superseding version of it.

I found the same data in a document with a narrower scope (EK\_ENR\_3\_2\_en.pdf) on autorouter, and then also the same restricted scope document on the Denmark AIP website with a direct link:

> **[EK\_ENR\_3\_2\_en.pdf](https://aim.naviair.dk/media/files/mmsbfi0p2t1/EK_ENR_3_2_en.pdf)**
>
> 775.49 KB

Investigating a little further, I found that in Navigraph data, N603 was amended with the release of cycle 2512:

- before 2512: BEREP → RAMUD → TESPI → ROSBI → INPUN → TNO
- since 2512: TESPI → ROSBI → INPUN → TNO

The removal of the segment BEREP → RAMUD is in line with the document (it seems that segment should possibly have been removed earlier, since it already is absent from the AIP document amended in 2024); on the other hand, the removal of RAMUD → TESPI does appear potentially erroneous.

Looking for confirmation, I figured I would try eurocontrol’s IFPUV validation system as a secondary “reference” or at least a point of comparison:

- it does not know BEREP N603 RAMUD

 ![Screenshot 2026-07-31 at 22.10.43](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/3/2/323f78d8074be6c26b3b82d4d405e96320878cdc.jpeg)

- _ **but does accept RAMUD N603 TESPI** _

 ![Screenshot 2026-07-31 at 22.21.23](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/2/9/29475b122a522e9c540ccb8f1f1a0a59ca84aee1.jpeg)

I am only guessing here, but it is possible that in removing an incorrect leg from N603, Jeppesen also accidentally removed another leg that should have remained part of this airway.

It does seem like this should be reported to Navigraph’s data provider as a possible mistake.

Regards,

Tim

---

<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:** [August 7, 2026, 8:30pm UTC](https://forum.navigraph.com/t/airway-n603-missing-in-data/23985/5 "2026-08-07T20:30:27Z")

</div>

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