Find KMCO airport charts, diagrams and gate maps, then use them correctly for IFR procedures, taxiing, runway selection and simulator parking.
For our Aviation & Real-World Flying reference library and for flight simulation, our KMCO chart collection with downloadable PDFs provides Orlando International’s airport diagram, runway data, frequencies, SIDs, STARs and approach plates. Use the diagram for taxiing; use a gate map or scenery layout only to choose the terminal, stand or parking position.
Which KMCO chart do I need?
Use the airport diagram for ground movement, procedure charts for IFR routing, and a gate or scenery map for parking selection.
| Chart or map | Use at KMCO | Check before using it |
|---|---|---|
| Airport diagram | Runways, taxiways, holding points, hotspots and terminal locations | Exact taxiway identifiers, runway crossings and any temporary closure information |
| SID | Instrument departure from Orlando | Assigned runway, transition, altitude and speed restrictions |
| STAR | Instrument arrival into the Orlando terminal area | Transition, expected runway and any discontinuity between the arrival and approach |
| Approach plate | Instrument approach and missed-approach procedure | Approach type, runway, frequency or course where applicable, minima and missed-approach instructions |
| Gate or scenery map | Terminal, concourse and simulator parking selection | Whether its gate labels match the scenery actually installed |
KMCO versus MCO
Search aviation chart libraries and simulator avionics with KMCO, the ICAO identifier. MCO is the passenger-facing IATA code and may not be recognised by chart indexes, flight-management systems or airport-selection tools that expect an ICAO code.
How do I use KMCO charts in a flight simulator?
Keep the airport diagram and relevant procedure plates available from pre-flight planning until the aircraft is parked.
- Check the chart date. Read the effective or revision information on each PDF. A newer chart may contain procedures or taxiway details absent from older simulator scenery and navigation data.
- Confirm the exact runway. KMCO has two numbered parallel pairs, so the suffix matters. Runway 17L becomes 35R in the opposite direction, while 17R becomes 35L; similarly, 18L becomes 36R and 18R becomes 36L. Do not choose a runway merely because it is nearest the terminal.
- Brief the IFR procedure. Check the SID or STAR transition, mandatory restrictions and expected approach before entering it in the FMS. If a procedure name or waypoint is missing, the chart and simulator navigation database probably use different AIRAC cycles.
- Plan the ground route. Trace the route from the parking position to the assigned runway, marking every runway crossing, holding point and hotspot. Our guide to airport-diagram symbols, holding points and hotspots explains the markings without duplicating the KMCO-specific chart.
- Follow the clearance, not the pencilled route. ATC may assign different taxiways, a different parallel runway or an amended procedure. Keep the diagram open and verify each sign before turning.
- Account for simulator limitations. If default ATC rejects a charted frequency or the FMS lacks a published procedure, use the data recognised by that simulator installation or align the chart and navigation-data cycles. Never invent a waypoint simply to make a newer plate fit older data.
Why does the KMCO gate map not match my scenery?
A real KMCO gate map often differs from simulator scenery because gate assignments, terminal structures and apron layouts change independently of aeronautical procedure charts. Airport diagrams are designed for safe ground movement and may show terminal outlines without labelling every passenger gate.
The scenery itself is the deciding reference for an exact simulator parking position. Older scenery may predate Terminal C or later taxiway and apron changes, while parking records may use generic stand names rather than the labels printed on a terminal map.
- For an exact gate departure: inspect the simulator’s airport-selection screen and confirm that the chosen parking position exists before loading the flight.
- For an arrival: use the terminal map to choose the correct area, then follow the stand identifiers available in the installed scenery.
- For FSX: compare the default airport with this KMCO scenery featuring assigned parking and revised ground detail. Its parking layout, signs and taxiways may still differ from another add-on or a newer real-world map.
A gate map must not replace the airport diagram: it rarely contains complete taxiway designations, runway holding positions or hotspots.
Do I need a VFR chart for the Orlando area?
Use a terminal area chart when the flight includes VFR routing through or around Orlando’s controlled airspace. Our Tampa–Orlando terminal area chart for regional VFR planning adds nearby airports, navigation features and Class B airspace context, but it does not replace the KMCO airport diagram on the ground.
Real-world use
For an actual flight, simulator chart collections and scenery maps are reference aids rather than the sole operational source. Use publications and briefing material approved for the operation and valid at departure time, and check notices for temporary closures or procedure changes. A gate map never authorises taxiing or a runway crossing.