How do you find, read and use Australian aviation charts?

For Aviation & Real-World Flying, find Australian aviation charts through Airservices Australia’s official aeronautical information and chart services, then choose VTC/VNC/WAC for visual navigation, ERC/TAC for IFR routing, ERSA for aerodrome details, or DAP for departures, arrivals and approaches. Read the legend and verify the effective date, AIP supplements and NOTAMs.

There is no single all-purpose Australian chart. A normal flight uses several publications in layers, with each one answering a different part of the planning or flying task.

Choose the right Australian aviation chart

For VFR, the usual progression is WAC or VNC for the route, VTC near complex terminal airspace, and ERSA for each aerodrome. For IFR, use PCA for the overview, ERC and TAC for the route, DAP for procedures, and ERSA for the aerodrome itself.

Where can I find official Australian aviation charts?

The official publisher is Airservices Australia, and operational charts should be obtained through its aeronautical information and chart services rather than from an undated search-engine copy. Our separate walkthrough covers finding the official Australian AIP, DAP and ERSA material by airport code.

1. Search by location indicator and name. Australian aerodrome publications normally use a four-letter location indicator such as YSSY, not the three-letter airline code. Not every landing area has an ICAO indicator, so search by its published name when necessary.
2. Select the publication for the task. ERSA supplies facility information, while the DAP index leads to aerodrome and instrument procedure charts. Use the visual or en-route chart catalogue for route maps.
3. Check the effective date. The download date does not establish validity. Confirm that the chart or publication is effective for the date of the flight; material released for a future AIRAC cycle must not be used early.
4. Collect changes outside the chart. Check applicable AIP amendments, AIP supplements and NOTAMs. Temporary airspace, navaid outages, runway closures and amended procedures may not be drawn on the underlying chart.
5. Keep the matching legend. Symbols and annotation conventions differ between visual, en-route, terminal and procedure charts. Do not decode an Australian VTC using assumptions learned from an FAA sectional.

How do I read Australian chart symbols?

Read the identification panel, units, legend and marginal notes before interpreting the route or airspace. Our broader workflow for identifying chart types, legends, routes and altitude information explains the fundamentals; Australian charts add their own abbreviations and publication conventions.

1. Confirm the chart identity. Check its title, geographic coverage, edition or effective date and scale. A WAC is suitable for broad planning but cannot replace the terminal detail of a VTC.
2. Verify the units. Altitudes and elevations are generally shown in feet, route distances in nautical miles and runway dimensions in metres. Tracks and bearings are normally magnetic unless the chart says otherwise. Times in aeronautical publications are generally UTC unless specifically marked.
3. Read both vertical limits of airspace. Identify the class, base and upper limit for every shelf crossed by the route. SFC means the surface, while an FL value is a pressure flight level rather than an altitude on local QNH. Adjacent controlled-airspace steps can have different bases.
4. Separate permanent boundaries from activation status. Prohibited, restricted and danger areas have published designators and limits, but the printed boundary alone may not reveal whether an area is active for the flight. Consult its published conditions and relevant NOTAMs.
5. Interpret terrain and IFR altitudes in context. Spot heights, obstacles and terrain tint do not guarantee clearance from every feature. On an ERC, an LSALT supplies obstacle protection for its stated route context; it is not automatically an ATC clearance or a procedure altitude.
6. Check communications and operating hours. A CTAF identifies the frequency used for traffic broadcasts, not the airspace class or the operating status of a tower. Some aerodromes change operating arrangements outside published tower hours.

Chart scale also affects what is omitted. If a boundary, waypoint or aerodrome detail looks ambiguous on a small-scale chart, move to the larger-scale chart or the referenced AIP section rather than estimating its position.

How do ERSA and DAP work together?

Use ERSA to understand the aerodrome and DAP to follow its published charted procedures. Reading only one of them can leave out a runway limitation, local caution, communications detail or procedure requirement.

• Before arrival or departure: review the ERSA facility entry, runway data, communications, lighting, local traffic procedures and cautions.
• For ground movement: use the applicable DAP aerodrome or parking chart, but remember that the diagram does not constitute a taxi clearance.
• For an instrument departure or arrival: check the correct procedure name, runway, transition, altitude and speed restrictions. Our guide to decoding SID and STAR transitions and constraints covers that sequence in detail.
• For an instrument approach: brief the plan view, profile, frequencies, minima and missed approach. See our method for working through an approach chart’s plan, profile, minima and missed approach.

Do not estimate a turn, distance or descent point from the apparent drawing scale of a DAP procedure. Procedure diagrams may be schematic; fly the published fixes, tracks, distances and restrictions.

How do I use Australian charts in a flight simulator?

In a flight simulator, use a chart set that matches the aircraft navigation database and check that the simulated airport layout represents the same runway and taxiway configuration. This matters in Microsoft Flight Simulator, X-Plane, Prepar3D and older platforms such as FSX.

1. Choose a coherent date. For present-day procedure practice, use the latest effective charts with matching navigation data. Do not combine a new DAP procedure with an old FMC route and assume the magenta line is correct.
2. Compare the procedure before loading it. Match the procedure name, runway, transition, fixes and altitude constraints between the chart and the aircraft. A missing waypoint or differently coded transition usually indicates a navigation-data mismatch.
3. Check the scenery. A runway number or taxiway that differs from the chart often points to old scenery, a runway renumbering or an airport-layout update. For ground practice, matching scenery is more important than forcing the aeroplane onto a charted taxiway that does not exist in the simulator.
4. Use the chart as the primary briefing source. Built-in world maps and moving maps are useful for orientation, but they may simplify airspace, omit ERSA cautions or use a different data cycle.
5. Resolve discrepancies before departure. Update the simulator’s navdata or airport scenery where possible, manually construct the route only where the aircraft permits it, or select a procedure represented consistently in both chart and database.

Common Australian chart mistakes

A mistake we see constantly is combining valid information from different dates and treating the result as one valid briefing.

• Using a cached PDF without checking its effective date.
• Searching by an IATA code when the DAP or ERSA index expects the Australian location indicator.
• Using a WAC or VNC where a VTC is needed to resolve stepped controlled airspace.
• Flying a DAP procedure without reading the corresponding ERSA cautions and local procedures.
• Assuming a CTAF label means the aerodrome is uncontrolled at all times.
• Treating LSALT, an ATC-cleared level and a procedure altitude restriction as interchangeable.
• Ignoring NOTAMs because the printed chart appears complete.

For real-world operations, only effective official publications, the required weather and NOTAM briefing, and instructions from the responsible aviation authorities or operator should be used. A simulator-compatible chart set is useful for practice, but an old scenery or navdata compromise must never be carried into an actual flight.