What is KMCO, and what should flight sim pilots know?

KMCO is the ICAO identifier for Orlando International Airport in Florida, the region’s main airline gateway. Flight sim pilots should expect four parallel north–south runways, busy Class B traffic, procedure-heavy arrivals, active-runway crossings, long taxi routes and fast-changing convective weather, and must keep charts, scenery and FMS navdata aligned.

What does KMCO mean?

For our Aviation & Real-World Flying readers, KMCO identifies Orlando International Airport, while MCO is its IATA and FAA identifier. The MCO code survives from McCoy Air Force Base, which previously occupied the site.

A mistake we see constantly is selecting KORL because it contains “Orlando”, or choosing Sanford when the flight plan calls for MCO. Enter KMCO and check that the last character is the letter O, not zero.

KMCO runway and terminal layout

Orlando International has two parallel-runway groups with the terminal area between them. The runway number changes from 17 to 18 across the airport because the magnetic alignment differs slightly.

Terminals A and B are opposite sides of the original central terminal complex; Terminal C is a separate terminal farther south. Gate and airline assignments vary between simulator databases and scenery editions, so use the allocated stand rather than relying on an old airline parking list.

The inner-runway crossings are KMCO’s main ground hazard. Stop at every hold-short marking unless specifically cleared across, even if the simulator’s default ATC becomes silent or draws a route through the runway. Keep the KMCO airport diagram and procedure charts open rather than trying to reconstruct the layout from the moving map.

How should flight sim pilots plan an arrival to Orlando?

Plan a KMCO arrival by aligning the airport code, charts, scenery, navdata, expected runway and parking position before descent.

1. Confirm the destination. Verify KMCO in the flight plan, GPS or FMS and compare its position with Orlando International rather than Orlando Executive or Sanford.
2. Check data compatibility. The chart, FMS procedure and installed airport should represent broadly the same layout and procedure cycle. For real-world flying, only approved operational charts and notices are suitable; community charts and simulator data are training aids.
3. Brief the arrival. Check the STAR transition, altitude and speed constraints, then identify where ATC is likely to issue vectors or a runway transition. Our guide to interpreting SID and STAR transitions and constraints covers the chart-reading detail.
4. Prepare the approach. Load the anticipated approach, but verify the exact runway, left or right suffix, final approach course, minima and missed approach after receiving the assignment. A STAR ending near an approach does not guarantee a straight-in clearance.
5. Plan the ground route. Note the terminal, gate and likely active-runway crossings before landing. If the stand is unfamiliar, use our post-landing gate and taxi procedure rather than following an unreliable GPS line across the apron.

Which runway and approach should I expect at KMCO?

The assigned KMCO runway depends on wind, traffic flow, aircraft performance, approach availability and closures, not simply which pavement is closest to the gate. Runways 17 and 18 point south; runways 35 and 36 point north.

Instrument databases commonly provide ILS and RNAV choices, but equipment and minima are not identical for every runway. Verify the runway number, L/R suffix, localiser identifier and final course both when loading the FMS and when reading back the clearance. On a parallel approach, selecting the correct number but the wrong suffix can place the aircraft on the adjacent final.

Expect vectors, speed control and late runway changes during busy airline operations. Under US procedures, assignment of a STAR alone is not permission to descend through its restrictions; wait for an altitude instruction or a “descend via” clearance. VFR pilots entering the Orlando Class B need an explicit Class B clearance where the simulator or online controller models real procedures—a transponder code or “stand by” is not clearance.

Why do KMCO charts, scenery and the FMS disagree?

KMCO mismatches usually come from airport scenery, navigation data and charts representing different dates. Terminal construction, renamed taxiways, altered parking positions or revised procedures may appear in one source but not another.

• An older airport package may omit Terminal C or show superseded taxi and stand layouts.
• The FMS may use a different navdata cycle from the chart, producing missing transitions or unexpected fixes.
• Two complete KMCO scenery packages may be active together, causing duplicate buildings, uneven surfaces or conflicting taxi signs.
• Built-in ATC may use its own runway and gate database rather than the visible add-on airport.

Keep only one full airport replacement active, check its compatibility notes and align the simulator’s navdata where the platform permits. For compatible legacy installations, our KMCO scenery for FSX and Prepar3D adds taxiway, parking and sign detail, but scenery alone does not update FMS procedures.

If a charted taxiway is absent from the rendered airport, taxi according to the surface that actually exists and advise the controller of the mismatch. If the FMS procedure and chart differ materially, request vectors or use a procedure represented correctly in both rather than constructing a hybrid arrival from mismatched fixes.

Orlando weather and performance traps

Thunderstorms, heavy rain and abrupt wind changes are the weather problems most likely to disrupt a KMCO arrival. A sea-breeze boundary can change the runway flow, while an easterly or westerly wind creates a crosswind component across every north–south runway.

Do not treat a convective cell on final as ordinary rain. Deviate, hold, accept another runway or divert as conditions require, using weather radar only where the simulated aircraft models it credibly. Live-weather flights also benefit from enough fuel for vectors, holding and a runway change.

Orlando is close to sea level, but hot, humid conditions still reduce take-off and climb performance. Wet-runway braking, windshear and reduced visibility may be more significant than terrain, particularly when using an aircraft add-on with detailed performance and failure modelling.

Common KMCO mistakes

Most failed KMCO arrivals result from airport identification, data alignment or ground discipline rather than difficult aircraft handling.