# CHI point not found on airways

**URL:** <https://forum.navigraph.com/t/chi-point-not-found-on-airways/6327>\
**Category:** General\
**Created:** [October 11, 2021, 9:01pm UTC](https://forum.navigraph.com/t/chi-point-not-found-on-airways/6327 "2021-10-11T21:01:00Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![PBflyer](https://avatars.discourse-cdn.com/v4/letter/p/f14d63/32.png) [@PBflyer](https://forum.navigraph.com/u/PBflyer)\
**Post date:** [October 11, 2021, 9:01pm UTC](https://forum.navigraph.com/t/chi-point-not-found-on-airways/6327/1 "2021-10-11T21:01:00Z")

</div>

Dear sirs,

during flight planning, Navigraph charts returns error when CHI point is involved in airways (Italy airspace).

For example:

CHI: The point CHI was not found on the airway Z906  
CHI: The point CHI was not found on the airway Z388  
CHI: The point CHI was not found on the airway M167

This also happen with Navigraph autoroute function, i.e. from LIBP to LIPZ icao codes, the application found the route LIBP OTRET M736 ANC L612 CHI LIPZ but an error says “CHI: The point CHI was not found on the airway L612”. Then, the flight plan remain incomplete.

As reported in current italian AIP (ENR 3.1-1 AIRSPACE UP TO FL305 INCLUDED / ATS ROUTES), CHI seems to be part of all mentioned airways.

Detail of the points in AIP:

CHIOGGIA VOR/DME ‘CHI’  
45°04’16’‘N 012°16’53’'E

(CHIOGGIA NDB ‘CHI’)  
(45°04’18’‘N 012°16’53’'E)

Why is this happening?

Thanks a lot in advance!

All the best,  
Paolo  
(a Navigraph enthusiast!)

![CHI_point](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/d/d2134ab3a1dc512d1a9d1ecd067e5ee0d8da457e.jpeg)

![CHI_error](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/1/1e75021ced107782399546a32a8a4ea621125ef4.jpeg)

---

<div class="post-metadata">

**Author:** ![SIC0027](https://avatars.discourse-cdn.com/v4/letter/s/9dc877/32.png) [@SIC0027](https://forum.navigraph.com/u/SIC0027)\
**Post date:** [October 12, 2021, 8:34am UTC](https://forum.navigraph.com/t/chi-point-not-found-on-airways/6327/2 "2021-10-12T08:34:20Z")

</div>

The same problem for ZAG, airoute L603, L604…!

[ZAG|690x496](https://forum.navigraph.com/uploads/short-url/ozCdNdBKSg8nYMdukqI4bEBTRd8.jpeg)

![zag 1](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/1/188d923f0787f2678438d455dfa615d7bdb6076a.jpeg)

---

<div class="post-metadata">

**Author:** ![Ian](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/ian/32/154_2.png) [@Ian](https://forum.navigraph.com/u/Ian)\
**Post date:** [October 12, 2021, 11:14pm UTC](https://forum.navigraph.com/t/chi-point-not-found-on-airways/6327/3 "2021-10-12T23:14:15Z")

</div>

We have an issue where an airway has a waypoint with same name VOR and NDB located together. We are working on a solution.

Cheers  
Ian

---

<div class="post-metadata">

**Author:** ![stephen](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/stephen/32/10435_2.png) [@stephen](https://forum.navigraph.com/u/stephen)\
**Post date:** [October 13, 2021, 10:50am UTC](https://forum.navigraph.com/t/chi-point-not-found-on-airways/6327/4 "2021-10-13T10:50:16Z")

</div>

Hi,

We have issued a fix in our route calculator now, and this issue should be resolved. Please verify!

Regards,

Stephen

---

<div class="post-metadata">

**Author:** ![PBflyer](https://avatars.discourse-cdn.com/v4/letter/p/f14d63/32.png) [@PBflyer](https://forum.navigraph.com/u/PBflyer)\
**Post date:** [October 13, 2021, 6:28pm UTC](https://forum.navigraph.com/t/chi-point-not-found-on-airways/6327/5 "2021-10-13T18:28:27Z")

</div>

It works perfectly now, thanks a lot Stephen!

All the best,  
Paolo

---

<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:** [October 15, 2021, 6:28pm UTC](https://forum.navigraph.com/t/chi-point-not-found-on-airways/6327/6 "2021-10-15T18:28:52Z")

</div>

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