EGSS Runway designations

Hi,

I have a FMS Data subscription for Navigraph for P3Dv5.3.

I planned a flight this morning from EGSS to EIDW. Using Aivlasoft EFB and the PMDG 737NGXu CDU the runways were shown as 04C and 22C. Consequently no SIDs were available.

Looking at the latest NATS charts the designations are 04/22. Why the discrepancy? I understand from another topic the designations were temporarily changed in 2023. With a single runway why the need for a C addition?

04C/22C are still designated alongside 04/22 in the AIP

They provide displaced thresholds when required.

But surely there are many other runways with displaced thresholds. Why is Stansted singled out?

Presumably a decision by the UK Civil Aviation Authority, perhaps because said displaced threshold and the regular threshold are used interchangeably depending on ongoing construction at the airport.

The official AIP lists both 04/22 and 04C/22C

Regards,

Tim

Not the standard displacement Ray.

I’m away from my PC but my main concern is to make Aivlasoft EFB see 04/22 as the primary runways so the SID can be seen.

As I recall you can do that through the database builder Ray.

I’m now in front of my computer. The FMC is fine as it shows both 04/22 and 04C/22C runways.

The problem lies in Aivlasoft EFB. When I load a plan and select DEP in the CDU I only have 04C and 22C. A message below says "No procedures available due to reasons unknown.

In the EFB Database Builder on the Enhance / Update Runways tab I have an entry for Stansted which has been there for ages.

It has 04 and 22 as Ident SIM entries and 04C and 22C as Mapping ARINC.

There’s no guidance for this in the EFB manual and the forum is shut. I’ve deleted it and rebuilt the d/b. Problem persists.

I’ve now reinstated the original entries and rebuilt the d/b. Problem persists.

EFB shows three AFCADs for EGSS. The UK2000 is top, GBEarth second and default last. I checked the UK2000 AFCAD and runways of 04/22 are correct. So it’s something in EFB I can’t fathom.

This is what I’ve entered. I appreciate it’s not a Navigraph problem but any assistance appreciated.

I have removed the file holding the EGSS runway change and rebuilt the database.

But annoyingly when I select DEP in EFB the runways are shown as 04C/22C. Where is that info coming from? Not my AFCADs as I’ve checked them all.

Could someone at Navigraph please check the SID entries for EGSS.
Are they set for 04C and 22C rather than 04 and 22?

Not in the database formats I am familiar with; all SID procedures are assigned to 04/22, STAR procedures are assigned to all runways (04 04C 22 22C) and all approaches are assigned to either 04 or 22 except the RNAV-Y which is available for 04C and 22C instead.

Regards,

Tim

You are telling EFB to use 04C/22C Ray.

My mapping is 04/04 and 22/22 this results in the runwaymappings file indicating:

EGSS 04|nil 04C|04 22|nil 22C|22

Hi,
no, we don’t have terminal procedures assigend to 04C/22C … only to 04/22. So the data are ok so far.

Cheers
Richard

Thanks Stephen. I’ll have another go in half an hour after the football has finished.

Runwaymappings file? Where’s that? My files are all bin and encrypted.

\AivlaSoft\EFB2\Server\Logfiles

This is driving me mad. I’ve restored the original AFCAD so 04/22 are the runways.

I’ve edited the runwaymappings file so it matches yours. I’ve also added EGSS to the Enhance / Update Runways in Database Builder.

Rescanned all scenery but when I select a plan for EGSS and select DEP the runways are 04C and 22C.

Why?

Try excluding the GBEarth afcad adding the entry to BglSceneryExclude.txt located \AivlaSoft\EFB2\Server\DbBuilder\Base

I added it and rebuilt. Still no joy. In the Client on the Airport Info tab only two BGLs now show. UK2000 and default.

Do I need that entry in Enhance Runways in the DB Builder?