X-Plane scenery incorrectly lists 5M6 as airport identifier for Pepperell Airport located in Pepperell MA. However the correct FAA Identifier for Pepperell Airport is 26MA as indicated on airnav and skyvector websites. The correct airport name for the FAA Identifier 5M6 is the Sugar Springs Airpark in Gladwin MI. Lat/Long coordinates for Sugar Springs Airpark are 44.1403708 / -84.4369750
Airport identifier-code changes are accomplished by re-submitting the airport to the Gateway. The primary (original) X-Plane Airport ID must remain the same, but the appropriate metadata (ICAO, FAA, IATA, etc.) should be inserted in WED, and the modified airport uploaded to the Gateway.
------------
Airport name changes are accomplished by re-submitting the airport to the Gateway. The primary (original) X-Plane Airport ID must remain the same, with the new name present.
Pepperell is actually 26MA (which does not currently exist in the gateway) but is identified in the gateway as 5M6. 5M6 is actually Sugar Springs (Scenery Pack ID 2887) which is currently listed as 0MI1 in the gateway. 0MI1 is a private helipad in someone's back yard and that helipad does not exist in the gateway nor is it depicted on any navigational charts that I could find.
Additionally, Pepperell is showing the reference datum as the coordinates for Sugar Springs. I haven't checked the datum for Sugar Springs, but I'd guess it has the coordinates for Lawler Heliport.
Please remove ID 5M6 from Pepperell and asign 26MA to this instead. Then remove 0MI1 from Sugar Springs and replace it with 5M6, leaving 0MI1 not used anywhere or you can add it as a heliport. You may need to adjust the reference datum as well or I could do it when I edit the airport.
For new construction at a NEW location: Please file a new airport code request
For an EXISTING airport mis-located in X-Plane: Adjust the airport location and re-submit to the Gateway
For an EXISTING airport with a new identifier: Re-submit the airport to the Gateway. Place new identifier in the meta data-field ONLY (ICAO, FAA, IATA, etc.)
For an EXISTING airport with an incorrect identifier: Re-submit the airport to the Gateway. Place correct identifier in the meta data-field ONLY (ICAO, FAA, IATA, etc.)
For an EXISTING airport with a NEW name: Re-submit the airport to the Gateway with the name modified as required.
You must be logged in to participate in the discussion
X-Plane scenery incorrectly lists 5M6 as airport identifier for Pepperell Airport located in Pepperell MA. However the correct FAA Identifier for Pepperell Airport is 26MA as indicated on airnav and skyvector websites. The correct airport name for the FAA Identifier 5M6 is the Sugar Springs Airpark in Gladwin MI. Lat/Long coordinates for Sugar Springs Airpark are 44.1403708 / -84.4369750
Julian Lockwood May 27, 2019 6:51 PM
Airport identifier-code changes are accomplished by re-submitting the airport to the Gateway. The primary (original) X-Plane Airport ID must remain the same, but the appropriate metadata (ICAO, FAA, IATA, etc.) should be inserted in WED, and the modified airport uploaded to the Gateway.
------------
Airport name changes are accomplished by re-submitting the airport to the Gateway. The primary (original) X-Plane Airport ID must remain the same, with the new name present.
Pepperell is actually 26MA (which does not currently exist in the gateway) but is identified in the gateway as 5M6. 5M6 is actually Sugar Springs (Scenery Pack ID 2887) which is currently listed as 0MI1 in the gateway. 0MI1 is a private helipad in someone's back yard and that helipad does not exist in the gateway nor is it depicted on any navigational charts that I could find.
Additionally, Pepperell is showing the reference datum as the coordinates for Sugar Springs. I haven't checked the datum for Sugar Springs, but I'd guess it has the coordinates for Lawler Heliport.
Please remove ID 5M6 from Pepperell and asign 26MA to this instead. Then remove 0MI1 from Sugar Springs and replace it with 5M6, leaving 0MI1 not used anywhere or you can add it as a heliport. You may need to adjust the reference datum as well or I could do it when I edit the airport.
Julian Lockwood June 23, 2020 5:16 PM
For new construction at a NEW location: Please file a new airport code request
For an EXISTING airport mis-located in X-Plane: Adjust the airport location and re-submit to the Gateway
For an EXISTING airport with a new identifier: Re-submit the airport to the Gateway. Place new identifier in the meta data-field ONLY (ICAO, FAA, IATA, etc.)
For an EXISTING airport with an incorrect identifier: Re-submit the airport to the Gateway. Place correct identifier in the meta data-field ONLY (ICAO, FAA, IATA, etc.)
For an EXISTING airport with a NEW name: Re-submit the airport to the Gateway with the name modified as required.