5.01 Information for the AIP through an AIS provider
(1) An aerodrome operator must report the information specified in subsection (2) to an AIS provider for publication in the AIP.
(2) The information for subsection (1) is information about the following, in accordance with, or as supplemented under, sections 5.03 to 5.09:
(a) the aerodrome;
(b) the movement area;
(c) the visual aids;
(d) the navigation aids;
(e) the rescue and firefighting services;
(f) the ground services;
(g) the aerodrome operational procedures.
(3) The information mentioned in subsection (1) must be reported in the format specified by the AIS provider.
5.02 Information to be included in aerodrome manual
The aerodrome manual must contain all of the information mentioned in subsection 5.01 (2) that is reported to the AIS provider.
5.03 Aerodrome information
An aerodrome diagram
(1) A single aerodrome diagram must illustrate the following:
(a) the layout of runways, taxiways and aprons;
(b) the nature of the runway surfaces;
(c) the designations and lengths of the runways;
(d) the designations of the taxiways;
(e) the location of illuminated and non-illuminated wind direction indicators;
(f) the location of the aerodrome reference point;
(g) the location of the terminal buildings;
(h) the location of any helicopter runway type FATO areas or helicopter aiming points;
(i) the location of any glider runway strips, if located external to a runway strip;
(j) the location and type of a VASIS, if provided.
Aerodrome administration statement
(2) An aerodrome administration statement must include the following:
(a) the aerodrome operator’s name, postal address, telephone number, email address, website and facsimile number (where applicable);
(b) the name and telephone number of the person nominated by the operator to be the contact for any matters arising outside normal business hours;
Note The relevant email address and facsimile number (where applicable) should also be provided.
(c) whether the aerodrome is for part military use, public use, private use or a combination of these uses.
Note Aerodrome use charges may also be included in the statement.
(3) For paragraphs (2) (a) and (b), the telephone numbers, email addresses and facsimile numbers must be numbers or addresses that are regularly monitored for incoming calls, emails or faxes.
Aerodrome location statement
(4) An aerodrome location statement must include the following for the aerodrome:
(a) its name;
(b) the State or Territory in which it is located;
(c) the latitude and longitude based on the aerodrome reference point;
(d) the Y location code indicator;
(e) the elevation;
(f) the currency of any Type A and B charts.
5.04 Movement area information
(1) For each runway designation, the information must include the following:
(a) the runway code number;
Note See paragraph 4.01 (2) (a).
(b) the runway bearings, in degrees magnetic;
(c) the length and width of the runway and its surface type, or, if non-homogeneous runway surfaces are provided across the length and width of the runway, the runway surface types;
Note See also Note 4 under Table 6.02 (1).
(d) for instrument runways:
(i) the geographic location coordinates of the threshold; and
(ii) the elevation of the midpoint of the runway threshold;
(e) either:
(i) until the end of 26 November 2025 — the strength rating of the runway pavement calculated using the ACN-PCN rating system; or
(ii) subject to subsection (1A), the strength rating of the runway pavement calculated using the ACR-PCR rating system;
Note 1 Aerodrome operators have a transition period until the end of 26 November 2025 to adopt the ACR‑PCR rating system and report the PCR value. If the PCR value is not reported for the 27 November 2025 date, being the Aeronautical Information, Regulation and Control (AIRAC) date, the relevant pavement will be published in the AIP ERSA as “unrated”.
Note 2 Guidance on assessing and reporting PCRs is contained in the ICAO Aerodrome Design Manual (Doc 9157, Part 3), as in force or existing from time to time.
(f) the length and width of the runway strip;
(g) the runway slope;
(h) the runway declared distances and STODA;
(i) the established OLS for the runway;
(j) if published — relevant:
(i) Type A charts for any significant obstacles within the take-off area up to 10 km from the end of the runway; and
(ii) Type B charts for any other obstacles around the aerodrome;
(k) identification of any obstacle-free zone;
(l) identification of any arrester system, its location and description.
(1A) For subparagraph (1) (e) (ii):
(a) the bearing strength of a pavement intended for aircraft with an MTOW greater than 5 700 kg must be determined and reported using the ACR-PCR method contained in CASA Advisory Circular (AC) 139.C-07: Strength rating of aerodrome pavements (AC 139.C-07), as in force from time to time; and
(b) the bearing strength of a pavement intended for aircraft with an MTOW equal to or less than 5 700 kg may be determined and reported using the ACR-PCR method contained in AC 139.C-07, as in force from time to time.
Note For an aerodrome operator, determining and reporting the bearing strength of a pavement intended for smaller aircraft is optional, but where it is done it must be done using the ACR-PCR method contained in AC 139.C-07, as in force or existing from time to time.
Runway strip availability
(2) If the aerodrome operator prepares the runway strip and makes it available for take-offs and landings, the information must include details of:
(a) such availability; and
(b) any limitations on such availability.
Note The provision of a glider runway strip is an example of runway strip availability. See also Chapter 6, Division 6.
Taxiways
(3) For each taxiway, the information must include the following:
(a) the aerodrome reference code letter;
(b) the width;
(c) the surface type;
(d) the designation.
Aprons
(4) For each apron of an aerodrome with international operations, the information must include the following:
(a) the surface type;
(b) the location, elevation and designation of any aircraft parking position or stand;
(c) details of any parking guidance provided.
(5) For each apron of an aerodrome that does not have international operations, the information:
(a) must include the surface type; and
(b) may include the location and designation of any aircraft parking position or stand.
5.05 Visual aids
Approach and runway lighting systems
(1) The information must include details of the following (as applicable) for approach and runway lighting systems:
(a) the type, length and intensity of the approach lighting system;
(b) the runway threshold lights, colour and wing bars;
(c) the type of visual approach slope indicator system;
(d) the length of the runway touchdown zone lighting;
(e) the length, longitudinal spacing, colour and intensity of the runway centreline lights;
(f) the length, longitudinal spacing, colour and intensity of the runway edge lights;
Note The references to intensity in paragraphs (a), (e) and (f), refer to the number of stages as described in the data product specification under Part 175 of CASR.
(g) the colour of the runway end lights and wing bars;
(2) The information must include details of the following:
(a) the location, characteristics and hours of operation of any aerodrome beacons;
(b) the lighting systems for taxiways, including taxi holding positions and stop bars;
(c) the lighting systems for aprons, including the location and type of VDGSs;
(d) any other movement area lighting systems;
(e) any obstacle lighting provided for OLS infringements;
(f) any secondary power supply, including its switch-over time.
5.06 Navigation aids
The information must include details of any navigation aid provided by the aerodrome operator.
5.07 Rescue and firefighting services
The information must include the category of any rescue and firefighting service (ARFFS) provided by the aerodrome operator and based at the aerodrome.
5.08 Ground services
The information must include details of the following:
(a) fuel suppliers and their contact details, including regularly monitored after-hours contact details;
(b) any aerodrome weather information broadcasts provided by the aerodrome operator;
(c) ground-to-air communication systems, for example UNICOM, aerodrome frequency response units (AFRU) and approved air-ground operator services provided by the aerodrome operator;
(d) any other aviation-related services made available to pilots by the aerodrome operator.
5.09 Aerodrome operational procedures
Standard taxi routes
(1) The information must include the location and designation of standard taxi routes determined by:
(a) the aerodrome operator; or
(b) the ATS provider.
Special procedures
(2) The information must include any special procedures unique to the aerodrome which pilots would reasonably be expected to know in the interests of aviation safety.
Notices
(3) The information must include cautionary or administrative information relating to the safe use of the aerodrome.
Low-visibility procedures
(4) If low-visibility procedures are established at the aerodrome — the information must include the following:
(a) the runways and equipment used under low-visibility procedures;
(b) the defined meteorological conditions under which low-visibility procedures are initiated, used and terminated;
(c) the ground markings and lighting used under low-visibility procedures.
CHAPTER 5
Division 2 Standards for information
5.10 Standards for information published in the AIP through an AIS provider
(1) In this section and section 5.11:
DPS means the AIS provider’s data product specification (as in force or existing from time to time) that is required under regulation 175.160 of CASR.
(2) The information mentioned in subsections 5.01 (1) and (2) must be determined and reported to the AIS provider in accordance with:
(a) the DPS; and
(b) regulation 175.460 for the DPS.
(3) The information mentioned in sections 5.12 to 5.17 must be reported or provided to the AIS provider in accordance with:
(a) the DPS; or
(b) if there is no DPS for the information — in accordance with the requirements (if any) specified in sections 5.12 to 5.17.
5.11 Standards for information to be included in aerodrome manual
(1) The information mentioned in section 5.02 must be determined and reported in the aerodrome manual in accordance with the DPS.
(2) The information mentioned in sections 5.12 to 5.17 must be reported in, or provided with, the aerodrome manual in accordance with:
(a) the DPS; or
(b) if there is no DPS for the information — in accordance with the requirements (if any) specified in sections 5.12 to 5.17.
5.12 Movement area – runways – declared distances information
(1) For each runway direction, the following distances must be reported in metres, with feet equivalent shown in brackets:
(a) take-off run available (TORA);
(b) take-off distance available (TODA);
(c) accelerate-stop distance available (ASDA);
(d) landing distance available (LDA).
Note The expressions used in this subsection are defined in section 3.01.
Intersection departure take-off distances available
(2) At an aerodrome where air traffic procedures allow taxiway intersection departures, the TODA from each relevant taxiway intersection must be reported.
Note The method of determining the take-off distances available at an intersection is similar to that used at a runway end. This is to ensure that the same performance parameters (for example, line-up allowance) are consistently applied for the line-up manoeuvre, whether entering the runway at the runway end or from some other intersection.
(3) Where a taxiway intersection is at right angles to the runway, the TODA from the taxiway intersection must be measured from the perpendicular line that:
(a) continues the taxiway edge; and
(b) is behind the aircraft when it commences its take-off roll.
Note This is illustrated in Figure 5.12 (3).
(4) Where a taxiway intersection is not at right angles to the runway, the TODA from the taxiway intersection must be measured from the perpendicular line that is:
(a) from the point where the continuation of the taxiway edge meets the runway edge; and
(b) behind the aircraft when it commences its take-off roll.
Note This is illustrated in Figure 5.12 (4).
Note: Shows the calculation of intersection departure information for a perpendicular runway entry from the taxiway.
Figure 5.12 (3) Calculation of intersection departure information for a perpendicular runway entry (illustrates matters)
Shows the calculation of intersection departure information for a non-perpendicular runway entry from the taxiway.
Figure 5.12 (4) Calculation of intersection departure information for a non‑perpendicular runway entry (illustrates matters)
(5) Intersection departure information must be reported as follows:
(a) RWY [runway designation] — TKOF from TWY [taxiway designation];
(b) RWY remaining [in metres and feet] — Reduce all DIST by [reduced distance, in metres and feet].
Note Here is an example of how to record the information:
(a) RWY 14 — TKOF from TWY A;
(b) RWY remaining 1085 (3560) — Reduce all DIST by 360 (1181).
(6) The code number of the OLS standard under section 7.16 for each runway must be reported in accordance with section 5.04.
Note For the applicable runway code number, see Table 4.01 (3).
(7) The selection of the critical obstacle must be based on:
(a) a survey of the full take-off surface in accordance with the nominated runway code number; and
(b) the applicable OLS standards specified in Chapter 7 of this MOS.
(8) The gradient from the end of the TODA to the top of the critical obstacle within the take-off climb area must be reported as a percentage figure. However, if there is no obstacle, a value of 1.2% must be reported.
Fences or levee banks
(9) If a fence or levee bank is located so close to a runway strip end that the take-off gradient is greater than 5%, the take-off gradient may be reported based on the next most critical obstacle within the take-off area provided that a note is added:
(a) advising that the fence or levee bank has not been taken into account in the calculation of the TODA and STODA gradients; and
(b) giving the location and height of the fence or levee bank.
Supplementary take-off distance available (STODA)
(10) For a TODA having an obstacle clear gradient of more than 1.6%, the STODA must be reported for obstacle clear take-off gradients of 1.6%, 1.9%, 2.2%, 2.5%, 3.3% and 5%, up to the gradient associated with the TODA, unless the corresponding STODA for a particular gradient is less than 800 m.
Note In calculating the STODA, care must be taken to ensure that a shielded object does not become critical for the lesser take-off distances, and that the slope of the runway is taken into account.
Threshold elevation
(11) For an instrument runway, the elevation of the midpoint of the runway threshold must be reported, measured in feet to an accuracy of 1 foot, based on the Australian Height Datum (AHD).
Aerodrome obstacle charts — Types A and B
(12) If a Type A or B chart is prepared, its currency must be reported by reference to:
(a) its date of preparation; or
(b) its sequential edition or issue number.
Note: Precision approach terrain chart
(13) If an aerodrome obstacle chart is provided by an aerodrome operator, it must be in accordance with the standards and procedures set out in ICAO Annex 4.
Note: Aerodrome Terrain and Obstacle Chart — ICAO (Electronic)
(14) If an aerodrome terrain and obstacle chart is provided by an aerodrome operator, it must be prepared and published as an Aerodrome Terrain and Obstacle Chart — ICAO (Electronic), in accordance with ICAO Annex 4.
One-direction runways
(15) If a runway direction cannot be used for take-off or landing, the declared distance must be reported as “nil” and accompanied by an explanation.
Note: Example: “TKOF 14 and LAND 32 not AVBL due surrounding terrain.”
5.13 Movement area — taxiways
Taxiway width
(1) The minimum width of the taxiway must be reported in metres.
Nature of taxiway surface
(2) The taxiway surface type must be reported as 1 of the following:
(a) bitumen seal;
(b) asphalt;
(c) concrete;
(d) gravel;
(e) grass;
(f) natural surface.
(3) If only the central portion of the taxiway is sealed, this must be reported.
Note This would relate to a non-homogeneous runway surface.
Taxiway designation
(4) For the taxiway record:
(a) each main taxiway and each short feeder taxiway must have a designation; and
(b) subject to paragraph (c), the designation must be a single letter used without numbers; and
(c) for each short feeder taxiway — an alpha-numeric designator may be used.
5.14 Movement area — aprons
Nature of apron surface
(1) The apron surface type must be reported as 1 of the following:
(a) bitumen seal;
(b) asphalt;
(c) concrete;
(d) gravel;
(e) grass;
(f) natural surface.
(2) The location and coordinates of all primary and secondary parking positions must be reported:
(a) for an aerodrome that has scheduled international air transport operations; and
(b) for an aerodrome without scheduled international air transport operations — if the operator has supplied parking position designations to an AIS provider for publication in the AIP.
Note See also subsections 5.04 (4) and 5.04 (5).
(3) For subsection (2):
(a) a location must be reported in degrees, minutes, seconds and hundredths of seconds of latitude and longitude; and
(b) elevation must be reported to the nearest foot.
5.15 Visual aids
Lighting systems
(1) All aerodrome lighting systems must be reported using the abbreviations set out in the AIP.
Note Runway lights include runway edge, threshold and runway end lights, and, where stopways are provided, stopway lights.
Note: Visual Docking Guidance System (VDGS) including Advanced Visual Docking Guidance System (A-VDGS)
(2) For an aerodrome apron of a kind mentioned in subsection 5.04 (4) or 5.04 (5), the type of guidance system must be reported as follows:
(a) if a VDGS or A-VDGS is provided — the type of system;
(b) if a pilot stop line is provided in lieu of a VDGS or A-VDGS — the word “Pilot”;
(c) if a marshaller is provided in lieu of a VDGS or A-VDGS — the word “Marshaller”.
5.16 Navigation aids
If the aerodrome operator provides a navigation aid, the geographic location coordinates and operating frequency must be recorded.
5.17 Additional hazard information
Local hazards that may adversely affect aviation safety (local hazard data) must be recorded, including the following:
(a) operating restrictions on the manoeuvring area;
(b) continual wildlife hazards at the aerodrome or in its vicinity, including descriptions, locations, and times or seasonal information;
Note Requirements for managing wildlife hazards are specified in Chapter 17. As a guide, the aerodrome vicinity, for the purposes of wildlife hazards, may be considered as being:
for sources of attractants and wildlife movements which present a hazard — within a radius of 3 km from all the runways of an aerodrome; and
for significant sources of attractants or hazardous wildlife movements across the aerodrome site — within a radius of 8 km from the aerodrome reference point.
(c) apron or parking position restrictions outside daylight hours;
(d) any activities within the circuit area that are hazardous to aviation;
Note For example shooting ranges, explosive areas (such as mine sites or military ordinance practice areas), wind farms or sources of gaseous plumes (such as gas driven generators, refineries or furnaces).
(e) other aviation activities such as helicopter, ultralight or glider operations within the circuit area.
Note In general terms, for aircraft engaged in general aviation with an approximate climb rate of 500 ft per minute, the circuit area may be considered as being within a radius of 3 km of the aerodrome reference point. For higher performance turboprop or jet engine aircraft, CASA recommends that a larger area should be considered for the circuit or circling area.