I noticed that the O’HARE 8 DEP SID from KORD isn’t showing up in the Fenix A320/21/19 database, even though it should be available. I’m on the latest AIRAC through Navigraph, so everything should be current. Interestingly, the SID does appear in the iniBuilds A320neo and other aircraft even though they are not using the Navigraph Data because I didn’t install it for the whole sim, only Fenix.
I have a real life picture that I can provide of the SID entered into a real MCDU, and it displayed on the ND if you need evidence.
Would really appreciate it if this could be looked into.
KMDW also has a vector departure and so as many other airports that you included, and I wouldn’t call it useless, because if it were, it wouldn’t exist in the real world.
Without a SID:
KORD09R - 2170 - DISCONTINUITY - [First Waypoint]
With a SID:
KORD09R - 1080 - MANUAL - DISCONTINUITY - [First Waypoint]
The problem is it’s using the airport elevation plus 1500 ft as the altitude constraint — which makes no operational sense. It should be using the correct altitude constraint from the actual procedure, even if it’s a vector SID. Entering straight into a discontinuity after takeoff isn’t realistic.
Hi,
The difference between KORD and KMDW is the initial climb phase. The HARE8 contains no sequences out of each runway, so it´s not coded in our data—only radar vectors. The CICER3 departure consists of a minimum sequence per runway plus the radar vectors. Therefore, you must code this part.
I´m not sure where the altitude constraint (with and without SID) comes from because the only altitude constraints I see are 3000ft (crossing D5.5/GCO) and 4000ft (crossing 8.5/GCO) at KORD. So, I don´t know where your altitudes come from.
With “useless” (at KORD), I meant that you expect radar vectors immediately without any other sequence before:
This is “useless” and will not be coded in the standard data:
KORD09R - MANUAL - DISCONTINUITY - [First Waypoint]
I’m not referring to CICER3 because, as you mentioned, that’s a different type of departure. I’m talking about MIDWAY 7, which is almost identical to OHARE 8.
Sorry for the confusion regarding the altitude constraints. What I meant was the altitude of the transition waypoint when entering manual flight. So, without a SID, the altitude for the “transition waypoint” defaults to the airport elevation plus 1500 feet, instead of the actual required altitude. This isn’t shown on the charts, but it is part of the flight plan.
When there is a SID, the transition waypoint altitude reflects the correct, intended altitude to transition into manual. For example:
Runway 22L without SID: 2160 ft
Runway 22L with SID: 480 ft
It’s frustrating that I can’t enjoy flying the same procedures used at my local airport. I’m paying for navigational data from Jeppesen, but it’s missing a SID. And when I ask for it to be fixed, I’m told it’s not important. That’s really disappointing.
My second screenshot in my previous answer is the MIDWA7, and also, here you see a clear statement before the vectors, a VM leg (defines a specific heading until a manual termination):
That’s the reason why this is coded in the database. All these are missing at KORD. At KORD you don´t have ANY such sequences before, therefore not coded in the standard database.
