Learn how to land at Mykonos (LGMK) in a flight simulator: choose runway 16 or 34, fly the right approach, manage wind and stop safely.
To land at Mykonos (LGMK) in a flight simulator, choose runway 16 or 34 from the actual wind, load a procedure your aircraft and navigation database support, stabilise before short final, and touch down firmly in the touchdown zone. Do not assume Mykonos has an ILS or carry surplus speed.
The method applies in Microsoft Flight Simulator, X-Plane, Prepar3D and FSX, although available procedures can differ with navigation data and scenery. LGMK has one runway approximately 1,900 metres long and 30 metres wide, at a field elevation of about 400 feet. Airliners therefore need proper landing-performance planning rather than guesswork.
Which runway and approach should I use at LGMK?
Use runway 34 with a northerly wind and runway 16 with a southerly wind, provided the crosswind, tailwind, runway condition and aircraft limits are acceptable. Choose from the actual weather or ATIS, not Mykonos's usual seasonal wind or an unreliable simulator ATC assignment.
Check the procedure list in the FMC, GPS or simulator flight planner against your current approach chart. A procedure available in one simulator or navigation-data cycle may be absent or coded differently in another.
| Approach option | When to choose it | Main trap |
|---|---|---|
| RNP/RNAV | Your aircraft supports it and its database contains the complete procedure | An advisory vertical path is not automatically equivalent to an ILS glideslope |
| VOR/DME or another non-precision procedure | The required navaid and distance information are available | APP mode may not provide vertical guidance; observe every altitude and distance restriction |
| Visual approach | Visibility and cloud permit continuous visual reference | Late alignment and the narrow-runway illusion can pull the aircraft below the proper path |
| ILS or localiser | Only when explicitly listed in the active database or chart and the signal identifies correctly | Pressing APP does not create a localiser or glideslope where none is provided |
For a visual arrival, establish on an extended final rather than making a rushed turn close to the threshold. Our guide to visual runway alignment and glide-path technique covers the centreline, PAPI and go-around skills needed here.
How should I fly the Mykonos landing?
- Set the weather and altimeter. Obtain the surface wind, visibility, runway condition and local QNH. Because LGMK is roughly 400 feet above sea level, a gate of 1,000 feet above the aerodrome is approximately 1,400 feet indicated on local QNH, not 1,000 feet indicated.
- Select the runway and valid procedure. Load the complete arrival and approach, remove unintended discontinuities only when you understand the next leg, and confirm the runway remains suitable for the wind. If simulator ATC assigns an excessive tailwind, request the opposite runway or go around.
- Calculate landing performance. Use the aircraft's performance tool, checklist or published data with the actual weight, wind and runway condition. Base the calculation on the declared landing distance available, which may not equal the runway's full physical length. Jet crews should also review our airliner approach and landing workflow.
- Brief the guidance and missed approach. Set the navigation source, minima, missed-approach altitude, course and radio frequency where required. For an RNP approach, check that GPS integrity and the intended lateral and vertical modes are available; for a conventional approach, identify the tuned navaid.
- Reduce energy early. Complete most deceleration before short final. On a three-degree path, a useful initial descent estimate is groundspeed multiplied by five: 130 knots gives about 650 feet per minute. Follow the published path if it is steeper or contains specific restrictions.
- Pass the stabilised-approach gate. A common airline standard is stabilised by 1,000 feet above aerodrome level in instrument conditions or 500 feet in visual conditions, though the aircraft's own procedure takes precedence. You should be configured, on the correct path and centreline, within the permitted speed range and using a manageable descent rate.
- Touch down in the touchdown zone. Follow the PAPI where it is depicted and working, maintain the corrected approach speed, and use only a small flare. Aim for a positive touchdown rather than floating in pursuit of an exceptionally soft landing.
- Confirm the stopping devices. Check that spoilers or lift dump deploy, reverse thrust operates as expected, and wheel braking is effective while maintaining the centreline. Do not rush a turn-off; backtracking may be required depending on the runway exit and traffic situation.
Why will APP mode not capture at Mykonos?
APP is not a generic button that follows every published approach. It normally arms localiser and glideslope capture for an ILS, while RNP and VOR procedures require different lateral and vertical modes.
- Wrong approach type: a VOR approach has no ILS glideslope, while an RNP approach normally uses the aircraft's GPS-based guidance.
- Wrong navigation source: some cockpits must be switched between GPS/FMS and VLOC or NAV radio guidance.
- Bad intercept: approaching the final course from above the glide path or at an excessive angle can prevent capture.
- Unidentified or incorrect signal: verify the tuned frequency, course and identifier rather than copying numbers from an old tutorial.
- Data mismatch: updated navigation data can disagree with older stock scenery or an add-on airport. Reload a procedure that exists in both systems, or fly a suitable visual approach in good conditions.
Watch the flight-mode annunciator rather than assuming the autopilot accepted the command. If the expected mode does not arm or capture, disconnect or select an appropriate basic mode, maintain a safe path manually, and go around if the approach becomes unstable.
How do wind and visual illusions affect the landing?
Mykonos's relatively narrow runway can look farther away and make the aircraft seem higher than it really is, tempting the pilot into a low approach. Cross-check the PAPI, vertical-path indication and descent rate instead of judging height from runway width alone.
Strong or gusty winds can change the required crab, bank and groundspeed quickly. Apply the gust correction specified for the aircraft, but do not add an arbitrary speed margin: every unnecessary knot increases float and stopping distance on a runway of this length.
When should I go around at Mykonos?
Go around whenever the aircraft is not stable by the applicable gate, the runway cannot be kept in sight on a visual approach, or a safe touchdown in the touchdown zone is no longer assured. Other clear triggers are an unresolved warning, excessive crosswind, runway occupancy, a large PAPI deviation or a prolonged float.
Follow the published missed-approach track and altitude rather than continuing straight ahead without checking terrain and restrictions. If flying visually without a loaded procedure, brief a safe go-around route before beginning the approach.
Why do I keep running out of runway?
Excess approach speed, a late touchdown and delayed spoiler deployment cause most Mykonos overruns in a simulator. A wet runway, tailwind, excessive landing weight, ineffective brake-axis calibration or thrust levers left above idle can make the problem much worse.
Do not salvage a long float by forcing the aircraft onto the runway or braking while it is still light on the wheels. Go around while sufficient runway remains, then correct the speed and aiming point; these flare and touchdown corrections for smoother landings also help prevent floating beyond the touchdown zone.