Aerosoft Aspen Extended 1.00
Page 8
There are several Visual Approaches available (only to runway 15, of course) but they are only possible with
Radar guidance, 6,000 ft. ceiling and 10 miles visibility. All of them are complex and need good local
knowledge. You will find start situations (flights) for all published procedures. We strongly recommend you
abort one landing to test the missed approach procedure.
Please note that ALL published approaches are forbidden at night. In fact the
airport is almost not used before sunrise -00:30 and after sunset +00:30.
MISS ED APPROACH
As the airport has high mountains to the East, South and the West you will need to make a right turn towards
300° and intercept the back course of the localizer (108.5 radial 300) while climbing at max rate. It is a good
idea to exercise this in good weather before getting caught in bad weather and with malfunctioning
equipment. When you do try it you will learn value a co-pilot to take over some of your tasks.
DEPAR TURE
First of all, your aircraft must be capable of a 460’ climb rate (remember the airport altitude and possible
issues with the Density Altitude) and remember: only runway 33 is available. Departures on runway 15 are rare
and always need written permission.
Standard departures climb out at heading 340° to 8,700’ and then turn heading 270° while climbing to 16,000’
[i.e. replace full stop by comma] to intercept the outbound back course 300 radial of localizer PKN (108.5).
Please note that ALL published departures are forbidden at night. In fact the
airport is almost not used before sunrise -00:30 and after sunset +00:30.
KNO WN ISSUES
AI traffic will both take-off and land from EITHER runway 15 or 33 (they will favor runway 15 except in
stronger tailwinds). This is a well-established FSX/Prepar3d AI limitation that prevents simultaneous
take-offs and landings from opposite ends of a runway.
The IPKN localizer feather points backwards in the FSX/Prepar3d map view. This is because the
localizer back course rather than front course is used for KASE climb out/missed approach.
In FSX, the tarmac may flicker when viewed at higher zoom levels (around 0.8 upwards) and from
higher altitudes. This flickering shouldn't be visible during normal flight.
In FSX, DX10 preview windsocks are unlit at night. This is due to FSX incompatibility with conditional
display model light maps.
Car traffic appears and disappears at the edges of LOD tiles. This is an FSX/Prepar3d bug.
The scenery contains a 'dummy' ILS approach, in addition to the real world localizer, VOR-DEM and
GPS approaches. This approach is only used by AI traffic to land successfully on runway 15.
P3d users with error reporting turned on may receive warnings on exit regarding taxiway width. This
does not affect the functionality of the scenery.
The user aircraft shadow will be several cm beneath the aircraft while taxiing.