# \[EDDH\] AIRAC 2203 missing altitude restrictions

**URL:** https://forum.navigraph.com/t/eddh-airac-2203-missing-altitude-restrictions/7817
**Category:** General non MSFS data
**Tags:** airac
**Created:** [April 9, 2022, 11:33am UTC](https://forum.navigraph.com/t/eddh-airac-2203-missing-altitude-restrictions/7817 "2022-04-09T11:33:33Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![SantinoDE](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@SantinoDE](https://forum.navigraph.com/u/SantinoDE)
#### Post date: [April 9, 2022, 11:33am UTC](https://forum.navigraph.com/t/eddh-airac-2203-missing-altitude-restrictions/7817/1 "2022-04-09T11:33:33Z")

</div>

Hello there, i use AIRAC 2203 in the FSL A320. I have noticed, that all STARS missing the altitude restriction in EDDH (HAM). Example: NOLGO1P NOLGO at FL110 or below. RARUP1D RARUP at FL110 or below, RIBSO1S RIBSO at FL110 or below.

Maybe you can fix that in one of the next AIRAC updates.

Greetings from Hamburg!

---

<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: [April 9, 2022, 2:05pm UTC](https://forum.navigraph.com/t/eddh-airac-2203-missing-altitude-restrictions/7817/2 "2022-04-09T14:05:20Z")

</div>

Hi,  
sorry, I can´t reproduce it …

![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/7/7008c247fd1a59bae57c0f89b7d528f402b7dfa0.png)

![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/8/816d060f20e1f2aa9c179495b8fee68addaca8ed.png)

Are you sure, that you use the FMS correctly?  
Cheers,  
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: [April 9, 2022, 3:41pm UTC](https://forum.navigraph.com/t/eddh-airac-2203-missing-altitude-restrictions/7817/3 "2022-04-09T15:41:46Z")

</div>

I believe that you will find this to be an FSL issue.

Where a flightplan is loaded and ending at the STAR entry point upon selecting the approach procedure via the MCDU the initial STAR data is dropped instead retaining the flightplan waypoint.

![capture_001_09042022_164339](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/5/5d3c62026470a8195dcd6e80974dd46ba4aa4dfe.jpeg)

Without the flightplan and selecting a STAR the restriction is loaded as per Richards post.

---

<div class="post-metadata">

### Author: ![SantinoDE](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@SantinoDE](https://forum.navigraph.com/u/SantinoDE)
#### Post date: [April 11, 2022, 10:26am UTC](https://forum.navigraph.com/t/eddh-airac-2203-missing-altitude-restrictions/7817/4 "2022-04-11T10:26:35Z")

</div>

Thank you for the reply.

Now i use the same STAR as Richard, but i have tu manually input the ALT CSTR manually. Very strange thats only at EDDH for me.  
I have for now only a picture of NOLGO after editing it by myself:

 ![2022-4-11_12-21-7-362](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/e/e446756cc33a598ff576748a28e360a0471f858e.jpeg)

---

<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: [April 11, 2022, 10:31am UTC](https://forum.navigraph.com/t/eddh-airac-2203-missing-altitude-restrictions/7817/5 "2022-04-11T10:31:20Z")

</div>

… but the difference is now, that you set a hard “AT 11000” and not a “AT OR BELOW 11000” as charted. I´m not sure, why do you want it and why you don´t accept the system, but anyway fine when it´s solved now …

Cheers,  
Richard

---

<div class="post-metadata">

### Author: ![SantinoDE](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@SantinoDE](https://forum.navigraph.com/u/SantinoDE)
#### Post date: [April 11, 2022, 10:39am UTC](https://forum.navigraph.com/t/eddh-airac-2203-missing-altitude-restrictions/7817/6 "2022-04-11T10:39:13Z")

</div>

I know but before setting 11000 at NOLGO, there was no ALT CONSTR for me.

---

<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: [April 11, 2022, 10:56am UTC](https://forum.navigraph.com/t/eddh-airac-2203-missing-altitude-restrictions/7817/7 "2022-04-11T10:56:42Z")

</div>

> [@SantinoDE](#):
>
> .

That occurs everywhere when a flightplan is loaded, the STAR selected and it has rescrictions on the first waypoint. The MCDU appears to use the last route waypoint rather than that of the STAR entry that contains the restriction data. You can see that in my post earlier and looks to be an FSL issue.

---

<div class="post-metadata">

### Author: ![SantinoDE](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@SantinoDE](https://forum.navigraph.com/u/SantinoDE)
#### Post date: [April 11, 2022, 11:13am UTC](https://forum.navigraph.com/t/eddh-airac-2203-missing-altitude-restrictions/7817/8 "2022-04-11T11:13:41Z")

</div>

Okay, than its my issue perhaps

But thanks for the help

---

<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: [April 13, 2022, 11:13am UTC](https://forum.navigraph.com/t/eddh-airac-2203-missing-altitude-restrictions/7817/9 "2022-04-13T11:13:50Z")

</div>

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