Master the Princess Juliana Airport approach and landing: Runway 10 profile, Maho Beach height, ILS, crosswinds and go-around decisions.
To land at Princess Juliana Airport (TNCM), fly the charted Runway 10 procedure or establish a stabilised visual final over Simpson Bay and Maho Beach, follow the glideslope or PAPI, cross the threshold at the normal height, and touch down in the touchdown zone. If speed, alignment or descent becomes unstable, go around.
Within our Aviation & Real-World Flying coverage, the key point is that TNCM uses ordinary stabilised-approach discipline despite its extraordinary sight picture. Real crews must use current charts, NOTAMs, ATC clearances, aircraft performance data and company procedures; simulator pilots should use charts that match their scenery and navigation data.
What makes the Princess Juliana approach difficult?
Runway 10 lies only a short distance beyond Maho Beach, a road and the airport fence, creating a strong temptation to fly lower than the proper approach path. Water provides few height and closure cues, while the beach, spectators and fence can dominate the view just when attention should move towards the runway aiming point.
The runway is roughly 2,300 metres, or 7,500 feet, long. That is adequate for many aircraft but leaves no excuse for excess speed, a long float or a touchdown beyond the normal zone, especially with a wet surface, tailwind or heavy aeroplane. Terrain east of the airport also makes the published missed-approach routing part of the briefing rather than an afterthought.
How do you fly the Runway 10 approach?
- Choose and brief the correct procedure. Confirm Runway 10 is appropriate for the wind and ATC clearance. Review the approach type, minima, missed approach, runway condition and landing-distance calculation. Never select Runway 10 solely to reproduce the famous beach view.
- Establish final early. Join the published instrument procedure or align with the runway while still well west of the island. For uncharted simulator practice only, starting 8–10 NM from the threshold at roughly 2,500–3,000 feet above aerodrome elevation gives room to establish a three-degree path. Our visual-final technique explains the correct sight picture and aiming-point method.
- Configure before the beach. Select landing flap, complete the landing checklist and settle at the aircraft's calculated target speed. Many operators use stabilisation gates of 1,000 feet above aerodrome level in IMC and 500 feet in VMC, although the applicable aircraft or operator procedure takes precedence. At the gate, the aeroplane should be on path, on speed, in landing configuration and require only small corrections.
- Hold the vertical path. Follow the glideslope when cleared on the instrument approach or maintain the PAPI indication when it is available and reliable. A useful three-degree estimate is groundspeed multiplied by five: 140 knots requires about 700 feet per minute, while 100 knots needs about 500. Correct with small power changes rather than large pitch movements.
- Aim beyond the threshold. The threshold itself is not the touchdown aiming point. Keep the standard aiming markings steady in the windscreen, cross the threshold at the charted or normal threshold-crossing height, and resist any urge to descend towards the beach or fence.
- Control the wind. Maintain the crab required to track the extended centreline, then de-crab during the flare or use the approved wing-low technique for the aircraft. Caribbean winds can be gusty and may change between the water and runway; our explanation of crab, de-crab and wing-low crosswind control covers the control inputs in detail.
- Flare and touch down normally. Shift the view towards the far end as the runway expands in the windscreen, reduce power as appropriate, and make a small flare. Touch down in the touchdown zone without holding the aeroplane off for an exceptionally soft landing. Confirm spoilers or speedbrakes, wheel braking and reverse thrust operate as the aircraft manual requires.
- Go around when the approach is no longer stable. Excess speed, excessive sink, unresolved drift, a late runway change or loss of visual reference are all valid reasons. Apply the aircraft's normal go-around procedure and follow the published missed-approach route; do not improvise a low-level circuit around terrain. The full simulator go-around sequence covers power, pitch, configuration and mode changes.
Which runway should you land on at TNCM?
Use the runway assigned by ATC or favoured by the actual wind and landing performance, not Runway 10 merely because it passes over Maho Beach. Easterly trade winds often favour Runway 10, but Runway 28 can be used when conditions and airport operations require it.
Runway 28 has its own approach geometry and terrain considerations. Brief its chart independently rather than reversing the Runway 10 technique. If the available runway creates an excessive tailwind, crosswind or landing-distance problem, delay, divert or use the operational alternative appropriate to the flight.
How low should you fly over Maho Beach?
There is no special Maho Beach altitude; the correct Runway 10 glidepath determines the aircraft's height over the beach. On a nominal three-degree path, the aircraft is about 300 feet above threshold elevation at one nautical mile and crosses the threshold near the procedure's published crossing height, commonly around 50 feet for transport-category approaches.
Do not target a memorised clearance above the beach, road or fence. Those objects are not approach references, and aircraft size changes the apparent clearance because the cockpit and landing gear follow different paths. Fly the glideslope or PAPI with the cockpit, then allow the landing gear geometry and normal flare to produce the touchdown.
Can you use the ILS or autopilot at Princess Juliana?
Runway 10 can be approached using published instrument guidance when the procedure is present in the applicable chart and navigation data and the aid is in service. Tune and identify the aid, set the charted inbound course, intercept from below, and confirm that the localiser and glideslope indications move in the expected direction. Our instrument intercept and ILS capture guidance explains the complete sequence.
The autopilot can reduce workload, but approach mode will not correct a wrong frequency, navigation source, course or intercept. Disconnect in accordance with the aircraft's limitations and the pilot's plan, then continue visually once the required references are available.
An ILS signal does not automatically authorise an autoland. The runway installation, aircraft, operator and crew must all support the required operation. In a simulator, add-on aircraft and airport scenery may model those capabilities differently.
Common TNCM approach mistakes and fixes
Most failed Princess Juliana landings begin before the flare, usually through an incorrect sight picture, excess speed or an attempt to salvage an unstable approach.
| What happens | Likely cause | Correction |
|---|---|---|
| Aircraft passes unusually low over the beach | Aiming at the threshold or chasing the dramatic view | Return to the glideslope or PAPI and use the runway aiming point |
| Pitch and power oscillate on short final | Looking too close to the nose and making large corrections | Trim the aircraft, look farther down the runway and use small power changes |
| Aircraft floats beyond the touchdown zone | Excess approach speed, an unjustified gust additive or a late flare | Fly the calculated target speed and go around when the landing zone is no longer assured |
| Aircraft drifts away from the centreline | Crosswind correction removed too early | Maintain the crab until the flare, then de-crab while preventing sideways drift |
| ILS, PAPI and runway appear misaligned | Incorrect tuning or a mismatch between scenery and navigation data | Verify the chart, identifier, course, scenery and navdata rather than splitting the difference |
| Stopping distance becomes marginal | Tailwind, wet runway, excessive speed or a late touchdown | Recalculate before landing and go around if the touchdown is not made in the planned zone |
Simulator practice that builds the correct sight picture
The most effective simulator practice starts with a simple visual setup and introduces one complication at a time. Use daylight, good visibility, a light headwind and a normal cockpit camera position; an external camera or extreme field of view makes height judgement unreliable.
- Begin 8–10 NM west of Runway 10, already aligned and near the three-degree path.
- Repeat with the same aircraft, weight, flap setting and target speed until the aiming point remains fixed without large corrections.
- Add a crosswind, gusts and rain separately rather than enabling every difficulty at once.
- Practise the missed approach deliberately, including autopilot mode awareness and the published route.
- If electronic guidance and the visible runway disagree, check the simulator's airport scenery and navigation-data alignment before practising further.