XSG-5871
CIFP Runway 07 Data preventing correct depiction of runway for gateway validation.
Airport Metadata Issue
Reported by:
anthony_d
on August 23, 2018 7:14 AM
Assigned to:
Julian Lockwood
The CIFP data (as interpreted in WED1.7.2) shows the end of the runway being at the same position as runway threshold. As a result, correct configuration of the runway is being returned as an error (see screenshot)
According to satellite image, and official AIP documentation:
https://ais.avinor.no/AIP/Latest/aip/ad/enbo/EN_AD_2_ENBO_2-1_en.pdf
End of runway is at Taxiway M intersection, but the displaced threshold is at Taxiway J/A Intersection.
In this instance the CIFP data is inconsistent with official documentation.
According to official notes, the runway extension west of Runway 07 Theshold is for military aircraft only, which may explain the inconsistency between CIFP and AIP documentation.
In situations like these, there needs to be an exception to allow CIFP data to be overrulled in order to allow the Runway to be marked correctly.
| Airport Identifier | ENBO |
|---|
Julian Lockwood August 26, 2018 12:01 AM
CIFP data is updated periodically in X-Plane, and may be slightly outdated at any given time. Gateway airports must always concur with the version of CIFP data present in X-Plane, even if changes have occurred to the real airport since that data was published. This is because the FMS and GPS units in X-Plane also use the CIFP data for flight planning. It is therefore recommended to submit the airport to the Gateway according to the CIFP validation in WED, even if this is outdated.