{"id":"F2005B02601","name":"Manual of Standards Part 171 - Aeronautical Telecommunication and Radio Navigation Services","slug":"manual-of-standards-part-171-aeronautical-telecommunication-and-radio-navigation-services","collection":"legislative_instrument","jurisdiction":"commonwealth","status":"in_force","isInForce":true,"actNumber":null,"makingDate":null,"administeringDepartment":null,"currentVersion":{"id":32859,"registerId":"commonwealth-F2005B02601-current","compilationNumber":null,"startDate":"2026-04-01","status":"InForce","reasons":null,"registeredAt":null},"sections":[{"sectionNumber":"1","sectionType":"section","heading":"Manual of Standards Part 171 - Aeronautical Telecommunication and Radio Navigation Services","content":"Manual of Standards Part 171 — Aeronautical Telecommunication and Radio Navigation Services\n\nas amended\n\nmade under subsection 9 (1) of the Civil Aviation Act 1988 and regulation 171.017 of the Civil Aviation Safety Regulations 1998.\n\nThis compilation was prepared on 3 March 2016 taking into account amendments up to Manual of Standards Parts 139, 171, 172 and 173 Amendment Instrument 2016 (No. 1).\n\nPrepared by the Flight Standards Branch, Standards Division, Civil Aviation Safety Authority, Canberra.\n\n  \n\nContents\n\nPage\n\nChapter 1 Introduction\n\nSection 1.1 General\n\nSection 1.2 Definitions\n\nChapter 2 Aeronautical telecommunication and radio navigation services and facilities\n\nSection 2.1 Aeronautical telecommunication services\n\nSection 2.2 Aeronautical radio navigation services\n\nSection 2.3 Aeronautical telecommunication and radio navigation facilities\n\nChapter 3 Safety management system\n\nSection 3.1 Standards for the safety management system\n\nSection 3.2 Standards for safety case preparation\n\nChapter 5 Technician qualifications, training and certification\n\nSection 5.1 Technician qualifications\n\nSection 5.2 Technician training and certification\n\nChapter 6 Test equipment and test facilities\n\nSection 6.1 Test facilities for aeronautical telecommunication or radio navigation services and facilities\n\nChapter 7 Document data availability and control\n\nSection 7.1 Documents to be held by the provider\n\nSection 7.2 Document and data control processes\n\nChapter 8 Records\n\nSection 8.1 Records system and procedures\n\nSection 8.2 Site logs\n\nChapter 9 Security\n\nSection 9.1 Security program for aeronautical telecommunication and radio navigation facilities\n\nChapter 10 Standards for facilities and equipment\n\nSection 10.1 Landing system facilities suitable for Special Authorisation Category I and II operations\n\nNotes to Manual of Standards Part 171\n\nChapter 1 Introduction\n\nSection 1.1 General\n\n1.1.1 Background\n\n1.1.1.1 The standards pertaining to the regulation of Aeronautical Telecommunication and Radio Navigation service providers in this Manual are established by the Civil Aviation Safety Regulations [Part 171](file:///\\\\cbr1cif01\\group\\SD&FT\\FSB\\ATMSS\\Regulations\\avreg\\rules\\1998CASR\\171\\171casr.doc) — Approved Aeronautical Telecommunication and Radionavigation Service Providers. Part 171 has its basis in the Standards and Recommended Practices in Annex 10 to the Convention on International Civil Aviation.\n\n1.1.2 Document set\n\n1.1.2.1 The document hierarchy consists of:\n\n(a) the Civil Aviation Act 1988 (the Act); and\n\n(b) relevant Civil Aviation Safety Regulations (CASRs); and\n\n(c) the Manual of Standards (MOS); and\n\n(d) Advisory Circulars (ACs).\n\n1.1.2.2 The regulatory documents establish, for service providers, a comprehensive description of system requirements and the means of meeting them.\n\n1.1.2.2A The Act establishes the Civil Aviation Safety Authority (CASA) with safety related functions relating to civil aviation and, in particular, the safety regulation of civil air operations in Australian territory.\n\n1.1.2.3 CASRs establish the regulatory framework (Regulations) within which all service providers must operate.\n\n1.1.2.4 The MOS comprises specifications (Standards) prescribed by CASA, of uniform application, determined to be necessary for the safety of air navigation. In those parts of the MOS where it is necessary to establish the context of standards to assist in their comprehension, the sense of parent regulations has been reiterated. The MOS is a disallowable legislative instrument. This means that it is an instrument that is not enforceable unless it is registered on the Federal Register of Legislative Instruments (FRLI). It must be tabled in both Houses of the Parliament within 6 sitting days after registration on FRLI, and is subject to scrutiny and disallowance by either House of the Parliament.\n\n1.1.2.5 Readers should understand that in the circumstance of any perceived disparity of meaning between MOS and CASRs, primacy of intent rest with the CASR. Where there is any inconsistency between the regulations and the MOS, the regulations prevail.\n\n1.1.2.6 Service providers must document internal actions (Rules) in their own Operational Manuals, to ensure compliance with the standards.\n\n1.1.2.7 ACs provide recommendations and guidance material to illustrate a means, but not necessarily the only means, of complying with the Regulations. ACs may explain certain regulatory requirements by providing interpretive and explanatory material. It is expected that service providers will document internal actions in their own Operational Manuals, to put into effect those, or similarly adequate, practices.\n\n1.1.3 Differences between ICAO standards and those in MOS\n\n1.1.3.1 Notwithstanding the above, where there is a difference between a standard prescribed in ICAO Annexes and the Manual of Standards (MOS), the MOS standard shall prevail.\n\n1.1.4 Differences published in AIP\n\n1.1.4.1 Australian differences to the ICAO Standards and Recommended Practices are published in AIP GEN 1.7.\n\n1.1.5 MOS documentation change management\n\n1.1.5.1 Responsibility for the technical content of the MOS resides with the relevant technical area within Flight Standards Branch, Standards Division of CASA.\n\n1.1.5.2 This document is issued and amended under the authority of the Director of Aviation Safety.\n\n1.1.5.2A Suggested changes to this MOS must be directed to the Manager, Air Traffic Management Systems Standards Section, Flight Standards Branch, Standards Division of CASA.\n\n1.1.5.3 Requests for any change to the content of the MOS may be initiated by:\n\n• technical specialist areas within CASA;\n\n• Aeronautical Telecommunication and Radio Navigation service providers;\n\n• ATS service providers.\n\n1.1.5.4 The need to change standards in the MOS may be generated by a number of causes. These may be to:\n\n• ensure safety;\n\n• ensure standardisation;\n\n• respond to changed CASA standards;\n\n• respond to amendments to the ICAO Annexes;\n\n• accommodate new initiatives or technologies.\n\n1.1.6 Related documents\n\n1.1.6.1 These standards should be read in conjunction with ICAO Annex 10 Volumes I to V inclusive, and ICAO Doc 8071 Volume I — Testing of Ground-Based Radio Navigation Systems.\n\n  \nSection 1.2 Definitions\n\n| Definition                             | Meaning                                                                                                                                                                                                                                 |\n| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Aeronautical telecommunication service | An aeronautical broadcast service, or an aeronautical fixed service, or an aeronautical mobile service that supports an ATS, or any system that processes or displays air traffic control data.                                         |\n| Aeronautical radio navigation service  | A radio navigation service intended for the benefit and for the safe operation of aircraft.                                                                                                                                             |\n| ATS                                    | Air Traffic Service as defined in Annex 11 to the Convention on International Civil Aviation.                                                                                                                                           |\n| ATS provider                           | A person or organisation approved as an ATS provider under CASR Part 172.                                                                                                                                                               |\n| Facility                               | One or more items of equipment, at one or more locations, that provide an aeronautical telecommunication or radio navigation service.                                                                                                   |\n| Safety Management System (SMS)         | A system that defines the policies, procedures and practices for managing:(a) the safe provision of services; and(b) any changes to the provision of those services.                                                                    |\n| Safety case                            | A document that provides evidence and argument that a service or facility, or a proposed change to the design of a service or facility, meets safety objectives or levels for the service or facility.                                  |\n| Support service                        | A service, provided to a service provider, that:(a) is necessary for the functioning of a telecommunication or radionavigation service; and(b) consists of information in electronic form and the carrier that carries the information. |\n\n  \n\nChapter 2 Aeronautical telecommunication and radio navigation services and facilities\n\nCASR reference: CASR Part 171.020 (2) (d) — List of aeronautical telecommunication and radio-navigation services\n\nSection 2.1 Aeronautical telecommunication services\n\n2.1.1 Classification of services\n\n2.1.1.1 Aeronautical telecommunication services are the ground-based stations of those services defined hereunder supporting an Air Traffic Service provided under [Part 172](file:///\\\\cbr1cif01\\group\\SD&FT\\FSB\\ATMSS\\Regulations\\avreg\\rules\\1998CASR\\172\\172casr.doc). Airborne stations are not included.\n\n(a) Aeronautical Broadcasting Service. A broadcasting service intended for the transmission of information relating to air navigation.\n\n> Note AWIB stations are not included.\n\n(b) Aeronautical Fixed Service. A telecommunication service between specified fixed points provided primarily for the safety of air navigation and for the regular, efficient and economical operation of air services.\n\n(c) Aeronautical Fixed Telecommunication Network Service. A worldwide system of aeronautical fixed circuits provided, as part of the aeronautical fixed service, for the exchange of messages and/or digital data between aeronautical fixed stations having the same or compatible communication characteristics.\n\n(d) Aeronautical Telecommunication Network Service. An inter-network that allows ground, air-ground and avionics data sub-networks to inter-operate by adopting common interface services and protocols based on the International Organisation for Standardization (ISO) Open Systems Interconnect (OSI) reference model.\n\n(e) Aeronautical Mobile Service. A mobile service between aeronautical ground stations and aircraft stations, in which survival craft stations may participate; emergency position-indicating radio-beacon stations may also participate in this service on distress and emergency frequencies. This service does not include ground stations that are provided for other than ATS purposes.\n\n> Note UNICOM, Certified Air/Ground Radio Services (CAGRS), Pilot Activated Lighting (PAL) and Aerodrome Frequency Response Unit (AFRU) stations are not included.\n\n(f) Any telecommunication service which processes or displays air traffic control data (including aviation meteorological data) for use by an ATS provider under [Part 172](file:///\\\\cbr1cif01\\group\\SD&FT\\FSB\\ATMSS\\Regulations\\avreg\\rules\\1998CASR\\172\\172casr.doc).\n\n(g) Electronic briefing and flight plan lodgement service for the use of pilots.\n\nSection 2.2 Aeronautical radio navigation services\n\n2.2.1 Classification of services\n\n2.2.1.1 A radio navigation service intended for the benefit, and for the safe operation of aircraft.\n\n2.2.1.1 Radio navigation services include radio determination (radar surveillance services) supporting ATS.\n\nSection 2.3 Aeronautical telecommunication and radio navigation facilities\n\n2.3.1 Classification of facilities\n\n2.3.1.1 The following list classifies the kinds of facilities used for the provision of aeronautical telecommunication and radio navigation services:\n\n(a) VHF air/ground voice communication facilities;\n\n(b) HF air/ground voice communication facilities;\n\n(c) UHF air/ground voice communication facilities;\n\n(d) Precision approach radio navigation aids;\n\n(e) Instrument Landing System facilities;\n\n(f) Non-precision radio navigation aids;\n\n(g) Distance Measuring Equipment;\n\n(h) VHF Omni-range (VOR) facilities;\n\n(i) Non-directional beacons (NDB);\n\n(j) Flight data processing facilities;\n\n(k) Flight information facilities;\n\n(l) Radar data processing facilities;\n\n(m) Primary surveillance radar facilities;\n\n(n) Secondary surveillance radar facilities;\n\n(o) Surface movement radar facilities;\n\n(p) Precision runway monitor facilities;\n\n(q) Automatic dependent surveillance system facilities;\n\n(r) Voice switching and control facilities;\n\n(s) ATS point to point communication facilities;\n\n(t) Air/ground data links;\n\n(u) Ground to ground data interchange networks;\n\n(v) Human Machine Interface systems, including Tower Consoles, ATS Work Stations, and Display facilities;\n\n(w) Uninterruptable and emergency power supplies;\n\n(x) Essential services in buildings and in equipment shelters housing facilities (electrical power supplies, air-conditioning, and security facilities);\n\n(y) Global Navigation Satellite System ground based augmentation stations or facilities;\n\n(z) Aeronautical databases used in or by a facility;\n\n(aa) Meteorological Display Systems used for ATS;\n\n(bb) Voice and Data Recording facilities;\n\n(cc) Any other facilities supporting ATS provided under [Part 172](file:///\\\\cbr1cif01\\group\\SD&FT\\FSB\\ATMSS\\Regulations\\avreg\\rules\\1998CASR\\172\\172casr.doc).\n\n  \nChapter 3 Safety management system\n\nCASR reference: CASR 171.086 Safety management system\n\nSection 3.1 Standards for the safety management system\n\n3.1.1 Necessary features of Safety Management System\n\n3.1.1.1 The necessary features of an SMS are:\n\n(a) the service provider’s safety policy and objectives; and\n\n(b) the organisational and staff responsibilities for safety matters; and\n\n(c) the establishment of the levels of safety that apply to the services, and the monitoring of the levels of safety achieved; and\n\n(d) the process for internal safety reviews; and\n\n(e) the process for the internal reporting and management of safety concerns and incidents; and\n\n(f) the process for the identification, assessment, control and mitigation of existing and potential safety hazards in service provision; and\n\n(g) the definition of the interface arrangements for safety management and the relative associated responsibilities and procedures with internal functional groups and with aerodrome operators and support service providers; and\n\n(h) the processes for the management of changes to existing services.\n\nSection 3.2 Standards for safety case preparation\n\n3.2.1 Standards\n\n3.2.1.1 Safety cases are to be based on a recognised methodology for safety risk assessment.\n\n3.2.1.2 The safety risk assessment in a safety case:\n\n(a) identifies all potential safety hazards associated with the operation of each service, in normal and abnormal modes of operation;\n\n(b) assesses the safety risk of each hazard;\n\n(c) identifies the means of mitigation of unacceptable safety risks.\n\n> Note Guidelines for the preparation of safety cases have been published by CASA in Advisory Circular AC 171-02.\n\n3.2.1.3 Existing ATEL/ANAV services and/or facilities having a demonstrated history of safe operation for more than two years at the date of initial certification do not need to be covered by a baseline safety case.\n\n3.2.1.4 A safety case is prepared to support a proposed new service, or a proposed change to an existing service, if:\n\n(a) the effect of the service or change would be that the service would not be in accordance with the certificate issued to the service provider under regulation 11.060 of CASR; or\n\n(b) the new service or proposed change requires prior notification to CASA because of a requirement to do so in the service provider’s safety management system.\n\n> Note Internal safety assessments for changes in accordance with regulation 171.040 of CASR are undertaken in accordance with the service provider’s safety management system.\n\n  \n\nChapter 5 Technician qualifications, training and certification\n\nCASR reference: CASR Part 171.050\n\nSection 5.1 Technician qualifications\n\n5.1.1 Minimum academic qualifications\n\n5.1.1.1 The minimum academic qualification for technicians performing operation and maintenance functions associated with aeronautical telecommunication facilities and/or radionavigation facilities is a diploma of technology in one of the following:\n\n(a) radio engineering;\n\n(b) communications engineering;\n\n(c) electrical engineering;\n\n(d) electronic engineering;\n\n(e) computer science;\n\n(f) information technology; or\n\n(g) qualifications equivalent to the above qualifications.\n\n5.1.1.2 For those technicians that carry out or supervise electrical and mechanical trades work only, the minimum qualification is an electrical or mechanical trades qualification, as relevant.\n\n5.1.1.3 Where an organisation considers, and CASA agrees, that the operation and maintenance of a particular type of facility is not technically complex, lesser qualifications may be acceptable for those technicians who operate and maintain that type of facility.\n\nSection 5.2 Technician training and certification\n\n5.2.1 Authorising certificate\n\n5.2.1.1 Approved organisations provide technicians with an authorising certificate which:\n\n(a) establishes the identity of the technician;\n\n(b) details the scope of the authorisation granted to the technician by listing the facilities, or types of facilities, which the technician is authorised to operate and/or maintain; and\n\n(c) includes a date of effect, and the period of time for which each of the authorisations remain current.\n\n5.2.1.2 An organisation must not grant a technician an authorising certificate in respect to a particular facility or a class of facility unless it has established that the technician:\n\n(a) has undergone a competency based course of instruction or on-the-job training specific to that facility or that class of facility; and\n\n(b) has been assessed to be competent in the operation and maintenance of the facility or the class of facility by an assessor who:\n\n(i) has been trained and accredited in the Assessment Units of Certificate IV in Assessment and Workplace Training as developed under the auspices of the Australian National Training Authority; and\n\n(ii) holds formal recognition of competency in the unit being assessed, at or above the level being assessed; and has current knowledge of the workplace and job/role of the person being assessed.\n\n(c) However, if an assessor does not have all the competencies at (b) (i) and (b) (ii), one person with the competencies in (b) (i) and one or more persons with the competencies in (b) (ii) may work together to conduct assessments.\n\n5.2.2 Refresher training and recency checking procedure\n\n5.2.2.1 Approved organisations must also have a process for refresher training and recency checking of technicians to ensure the on-going retention of technician’s competency on the facility types for which an authorising certificate has been granted.\n\n  \nChapter 6 Test equipment and test facilities\n\nCASR reference: CASR Part 171.070\n\nSection 6.1 Test facilities for aeronautical telecommunication or radio navigation services and facilities\n\n6.1.1 Standards\n\n6.1.1.1 An organisation has available the necessary test facilities for use in the operation and maintenance of services and facilities.\n\n6.1.1.2 Organisations use documented procedures to control, calibrate, and maintain test equipment.\n\n6.1.1.3 Calibrated test equipment is used in maintenance of a service or facility.\n\n6.1.1.4 Calibration is carried out at prescribed intervals for each type of test equipment and the calibration is traceable to national measurement standards.\n\n6.1.1.5 Records of the calibration status of each item of test equipment are retained.\n\n6.1.1.6 Each item of test equipment carries a visual identification of its calibration status, the date that the equipment was last calibrated, and the prescribed calibration periodicity.\n\n6.1.1.7 An organisation is to assess the validity of previous test results whenever an item of test equipment is found to be out of calibration.\n\n  \n\nChapter 7 Document data availability and control\n\nCASR reference: CASR Part 171.075\n\nSection 7.1 Documents to be held by the provider\n\n7.1.1 Standards\n\n7.1.1.1 Documentation that is essential for the provision of services under the certificate are:\n\n(a) Annex 10 Volumes I to V inclusive, and Annex 11;\n\n(b) the functional specification and technical specification of services and facilities;\n\n(c) records of the configuration of facilities;\n\n(d) facility operation and maintenance plans;\n\n(e) interface agreements with other organisations;\n\n(f) facility technical manuals or instructions;\n\n(g) local instructions and technical procedures; and\n\n(h) safety cases.\n\nSection 7.2 Document and data control processes\n\n7.2.1 Standards\n\n7.2.1.1 Document and data control processes are those which control the authorisation, publication, distribution, and amendment, of all documentation issued, or required, by the organisation.\n\n7.2.1.2 These processes are to ensure that:\n\n(a) documents are authorised by a designated authority;\n\n(b) the currency of documentation can be readily determined;\n\n(c) documents are available at locations where needed by staff;\n\n(d) only current versions of documents are available; and\n\n(e) a master copy of all documentation is securely held.\n\n7.2.1.3 All documents that are related to and referenced in the Operations Manual are to be indexed in the Operations Manual.\n\n  \n\nChapter 8 Records\n\nCASR reference: CASR Part 171.080\n\nSection 8.1 Records system and procedures\n\n8.1.1 General\n\n8.1.1.1 The records system and procedures identify, collect, index, store, and maintain records necessary for the safe provision of services.\n\n8.1.2 Standards\n\n8.1.2.1 The procedures must ensure that legible and permanent records are kept which provide a traceable history over the lifecycle of services. Records kept include:\n\n(a) records of design, manufacturing, procurement, installation, testing, commissioning, modification, and decommissioning;\n\n(b) records of the designated authorities for the design, operation and maintenance for each system;\n\n(c) records of hazard analysis and risk assessments;\n\n(d) records of facility performance and facility maintenance history including performance parameter values, test facilities utilised, identity of authorised technicians conducting operation and maintenance, changes to maintenance procedures;\n\n(e) records of facility failures and faults\n\n(f) records of defect reports and associated defect investigations;\n\n(g) records of technician’s competencies, including details of experience, qualifications, training, competency assessments, and facility authorisations.\n\nSection 8.2 Site logs\n\n8.2.1 Standards for site logs\n\n8.2.1.1 Site logs are kept for all facilities used to provide an aeronautical telecommunication service or a radionavigation service.\n\n8.2.1.2 The site log records all occurrences and actions relating to operation, maintenance, modification, failure, faults, and removal from and restoration to service.\n\n8.2.1.3 Entries in site logs include the date/time of the entry and the occurrence and are signed by the technician or other person making the entry.\n\n8.2.1.4 Site log records are retained for at least five years.\n\n  \n\nChapter 9 Security\n\nCASR reference: CASR Part 171.085\n\nSection 9.1 Security program for aeronautical telecommunication and radio navigation facilities\n\n9.1.1 Purpose\n\n9.1.1.1 The purpose of a security program is to minimise the risk of unauthorised access, entry by animals, or malicious damage to a service or facilities.\n\n9.1.2 Standards\n\n9.1.2.1 The security program includes the physical security measures, and the procedures to be followed, for:\n\n(a) preventing and detecting intentional or unintentional damage to any facility or equipment used for providing an aeronautical telecommunication or radionavigation service;\n\n(b) responding to a threat of intentional damage to a facility or equipment;\n\n(c) preventing unauthorised people from having access to any facility or equipment used by the provider in providing an aeronautical telecommunication or radionavigation service.\n\n  \n\nChapter 10 Standards for facilities and equipment\n\nCASR reference: paragraph 171.017 (1) (b)\n\nSection 10.1 Landing system facilities suitable for Special Authorisation Category I and II operations\n\n10.1.1 Special Authorisation Category I operations\n\n10.1.1.1 The landing system facilities on a runway are suitable for Special Authorisation Category I instrument approach operations if all of the following requirements are met:\n\n(a) the runway has:\n\n(i) an ILS that is a dual transmitter facility classified at least I/T/1; or\n\n(ii) if the requirement in sub-subparagraph (i) is not met and the runway is to be used by only HUD-equipped aircraft — an ILS certified and maintained to meet ICAO Annex 10, Volume I requirements for Category I ILS to at least ILS Point “C”; or\n\n(iii) taking into account any associated operating limitation, a precision approach facility that has performance characteristics at least equivalent to an ILS mentioned in sub-subparagraph (i) or (ii);\n\n(b) if 2 separate ILS facilities serve opposite ends of the runway — a system is in operation to ensure that only the localiser serving the approach direction in use will radiate;\n\n(c) the controlling ATC element has facilities to remotely monitor the operational status of the precision approach facility.\n\n10.1.1.2 If the service provider informs a certified designer or authorised designer that the landing system facilities on a runway are suitable for Special Authorisation Category I operations, the provider must also inform the designer whether the precision approach facility, because of its performance classification, is suitable for only HUD-equipped aircraft.\n\n> Note The terms certified designer and authorised designer are defined in regulation 173.010 of CASR.\n\n10.1.2 Special Authorisation Category II operations\n\n10.1.2.1 The landing system facilities on a runway are suitable for Special Authorisation Category II instrument approach operations if all of the following requirements are met:\n\n(a) the runway has:\n\n(i) an ILS classified at least II/D/2; or\n\n(ii) taking into account any associated operating limitation, a precision approach facility that has performance characteristics at least equivalent to an ILS mentioned in sub-subparagraph (i);\n\n(b) if 2 separate ILS facilities serve opposite ends of the runway — a system is in operation to ensure that only the localiser serving the approach direction in use will radiate;\n\n(c) any ILS facility has an ILS frequency-paired DME.\n\n> Notes to\n\n > Note: Manual of Standards Part 171\n\n> Note 1\n\n> Note: The \n> \n> > Note: Manual of Standards Part 171\n> \n>  (in force under the Civil Aviation Safety Regulations 1998) as shown in this compilation comprises \n> \n> > Note: Manual of Standards Part 171\n> \n>  amended as indicated in the Tables below.\n\n> Note: > Note: Table of Orders\n\n| Year andnumber                                                                    | Date of notificationin Gazette/registration on FRLI | Date ofcommencement      | Application, saving ortransitional provisions |\n| --------------------------------------------------------------------------------- | --------------------------------------------------- | ------------------------ | --------------------------------------------- |\n| MOS 171                                                                           | —                                                   | 1 May 2003               |                                               |\n| MOS 171 2006 No. 1                                                                | FRLI 15 August 2006(see F2006L02666)                | 16 August 2006(see s. 2) |                                               |\n| Manual of Standards Parts 139, 171, 172 and 173 Amendment Instrument 2016 (No. 1) | FRLI 13 January 2016(see F2016L00042)               | 3 March 2016(see s. 2)   |                                               |\n\n```html\n<table cellspacing=\"0\" cellpadding=\"0\" style=\"width:352.7pt; margin-bottom:0pt; border-collapse:collapse\"><thead><tr><td colspan=\"2\" style=\"width:341.9pt; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span class=\"CharENotesHeading\" style=\"font-size:10pt; font-weight:bold\">Table of Amendments</span></p><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span>ad. = added or inserted</span><span> </span><span>am. = amended</span><span> </span><span>rep. = repealed</span><span> </span><span>rs. = repealed and substituted</span></p></td></tr><tr><td style=\"width:108pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmend\" style=\"margin-right:0pt; margin-bottom:3pt\"><span>Provision affected</span></p></td><td style=\"width:223.1pt; border-top:0.75pt solid #000000; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmend\" style=\"margin-right:0pt\"><span>How affected</span></p></td></tr></thead><tbody><tr><td style=\"width:108pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">Para. 1.1.2.1</span></p></td><td style=\"width:223.1pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">rs. F2016L00042</span></p></td></tr><tr><td style=\"width:108pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">Para. 1.1.2.2A</span></p></td><td style=\"width:223.1pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">ad. F2016L00042</span></p></td></tr><tr><td style=\"width:108pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">Para. 1.1.2.4</span></p></td><td style=\"width:223.1pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">rs. F2016L00042</span></p></td></tr><tr><td style=\"width:108pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">Para. 1.1.5.1</span></p></td><td style=\"width:223.1pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">rs. F2016L00042</span></p></td></tr><tr><td style=\"width:108pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">Para. 1.1.5.2</span></p></td><td style=\"width:223.1pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">rs. F2016L00042</span></p></td></tr><tr><td style=\"width:108pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">Para. 1.1.5.2A</span></p></td><td style=\"width:223.1pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">ad. F2016L00042</span></p></td></tr><tr><td style=\"width:108pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">Subpara. 3.2.1.4 (a)</span></p></td><td style=\"width:223.1pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">am. F2016L00042</span></p></td></tr><tr><td style=\"width:108pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">Chapter 10</span></p></td><td style=\"width:223.1pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">ad. F2016L00042</span></p></td></tr><tr><td style=\"width:108pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">s. 1.2</span></p></td><td style=\"width:223.1pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">am. MOS 171 2006 No. 1</span></p></td></tr><tr><td style=\"width:108pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">Chapter 3 (after heading)</span></p></td><td style=\"width:223.1pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">ad. MOS 171 2006 No. 1</span></p></td></tr><tr><td style=\"width:108pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">s. 3.1</span></p></td><td style=\"width:223.1pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">am. MOS 171 2006 No. 1</span></p></td></tr><tr><td style=\"width:108pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">s. 3.2</span></p></td><td style=\"width:223.1pt; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">am. MOS 171 2006 No. 1</span></p></td></tr><tr><td style=\"width:108pt; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">Chapter 4</span></p></td><td style=\"width:223.1pt; border-bottom:0.75pt solid #000000; padding-right:5.4pt; padding-left:5.4pt; vertical-align:top\"><p class=\"TableOfAmendHead\" style=\"margin-right:0pt\"><span style=\"font-size:9pt\">rep. MOS 171 2006 No. 1</span></p></td></tr></tbody></table>\n```","sortOrder":0}],"analysis":{"flash_summary_failed":{"failed":true,"reason":"A positive credit balance is required for all requests, including BYOK, so fallback providers remain available. Add credits at https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fai%3Fmodal%3Dtop-up to continue.","source":"analysis-cron"},"flash_summary":{"complexity_score":6,"scope_assessment":{"changed":true,"description":"This compilation incorporates later amendments (2006 and 2016) that expanded and clarified the MOS beyond the original 2003 edition. Notable scope changes include the addition of Chapter 10 (detailed landing system criteria for Special Authorisation Category I and II operations) and inserted administrative and governance detail (e.g. new or amended clauses on CASA responsibility for MOS content and change management in 1.1.5, and amendments to safety case notification and certification cross-references in Chapter 3). These changes add explicit technical criteria for runway landing system suitability and additional procedural/administrative requirements, increasing the MOS's operational and technical reach compared with the original instrument."},"complexity_factors":["Multiple chapters (10) covering technical, organisational and procedural areas (SMS, safety cases, technician qualifications, test equipment, documents, records, security, facility standards)","Cross-references to multiple external instruments — CASR Parts 11, 171, 172, 173 and ICAO Annexes (frequent external dependencies)","Defined terms in the interpretation section that are reused across the MOS (definitions such as Aeronautical telecommunication service, Facility, SMS, Safety case, Support service)","Long lists and enumerations (e.g. 29 facility types in section 2.3.1, multi-part ILS classification criteria in 10.1)","Conditional logic and exemptions (e.g. safety case exemptions for services with >2 years safe history, CASA discretion to accept lesser qualifications)","Procedural and documentary requirements with retention periods and traceability rules (calibration traceability, records lifecycle, five-year site log retention)","Nested certification and assessor competency requirements for technician authorisations (5.2.1.2 with combined assessor arrangements)","Interlocking operational and technical requirements (e.g. remote monitoring, frequency pairing, localiser control for ILS suitability) creating dependencies between infrastructure, operations and certification"],"plain_english_summary":"**What this document is and what it does**\n\n- This Manual of Standards (Part 171) sets out the detailed, technical standards that organisations must meet if they provide ground-based aeronautical telecommunication or radio‑navigation services in Australia. It is made under the Civil Aviation Act 1988 and the Civil Aviation Safety Regulations (CASRs). (See sections 1.1.1, 1.1.2, 2.1.1 and 2.3.1.)\n\n- The MOS does not create policy in the abstract; it prescribes the concrete features of systems, facilities, processes and records that CASA expects service providers to have in place so those services can be delivered safely and consistently. (See 1.1.2.2 and 1.1.2.4.)\n\n**Who this affects**\n\n- Approved aeronautical telecommunication and radio navigation service providers (the organisations that operate ground stations, networks and associated facilities). (Definitions and scope: Section 1.2; classifications: Sections 2.1.1, 2.2.1 and 2.3.1.)\n- Air Traffic Service (ATS) providers that rely on these services (cross‑referenced to CASR Part 172). (See section 2.1.1.1 and 2.3.1(cc).)\n- Technicians and maintenance staff who operate or maintain the equipment (qualification, training and authorisation requirements in Chapter 5). (See Sections 5.1 and 5.2.)\n- Designers, certifying bodies and CASA, to the extent the manual guides certification, safety cases and operational suitability (see Chapters 3 and 10).\n\n**Concrete obligations and technical requirements (how it works mechanically)**\n\n- Definitions and scope: the MOS defines which ground-based telecommunication and radio-navigation services and facilities are covered (e.g. VHF/HF/UHF air/ground voice, ILS, VOR, DME, radar, datalinks, GNSS augmentation, meteorological displays, recorders, power supplies, databases). (Section 2.1, 2.2, 2.3.)\n\n- Safety management system (SMS): providers must have an SMS that includes policy, assigned responsibilities, safety performance levels, internal reviews and reporting, hazard identification and change management. Safety cases supporting new services or significant changes must use recognised safety‑risk assessment methods and identify hazards, risk levels and mitigation. Providers with services that have a two‑year safe history may be exempt from producing a baseline safety case. (Sections 3.1 and 3.2; see 3.2.1.1–3.2.1.4.)\n\n- Technician qualifications and certification: minimum educational requirements for technicians (diploma in radio/communications/electrical/electronic/computer science/IT or equivalent); trade qualifications allowed for those doing only electrical/mechanical trades work; CASA can agree to lesser qualifications for simple facilities. Organisations must issue authorising certificates to technicians only after competency‑based training and assessment by accredited assessors, and must maintain refresher and recency processes. (Sections 5.1.1 and 5.2.1–5.2.2.)\n\n- Test equipment and calibration: organisations must have appropriate test facilities, use documented procedures for calibration and maintenance, keep calibration traceable to national standards, mark calibration status on equipment and retain calibration records; if equipment is found out of calibration the validity of prior test results must be assessed. (Section 6.1.)\n\n- Document and data control: providers must hold key documents (e.g. ICAO Annex 10/11, functional/technical specs, configuration records, operation and maintenance plans, interface agreements, safety cases) and implement document control processes to ensure authorised, current and accessible documentation, with a secured master copy. (Chapter 7.)\n\n- Records and site logs: providers must retain legible, permanent records across the life cycle (design, procurement, testing, commissioning, maintenance, faults, defect investigations, technician competence records). Site logs must record occurrences and actions, be signed and retained for at least five years. (Chapter 8; sections 8.1 and 8.2.)\n\n- Security: providers must have a security program to reduce unauthorised access, animal entry and malicious damage, and set out physical security measures and response procedures. (Chapter 9.)\n\n- Specific facility standards: the MOS lists detailed facility types and technical conditions. For example, Chapter 10 sets requirements for landing systems to be suitable for Special Authorisation Category I and II instrument approaches (detailed ILS classification, remote monitoring, DME pairing and localiser control requirements). (Section 10.1.)\n\n**How the MOS fits with other rules and international standards**\n\n- The MOS sits under the Civil Aviation Act and the CASRs and is intended to be consistent with ICAO Annexes. Where MOS and CASRs conflict, CASRs prevail. (See 1.1.2.2–1.1.2.5.)\n\n- The MOS states that where it differs from ICAO Annex standards, the MOS standard shall prevail for Australian application. (Section 1.1.3.1.)\n\n- CASA issues and amends the MOS; the document is a disallowable legislative instrument (it must be registered and is subject to parliamentary disallowance processes). (Section 1.1.2.4.)\n\n**Stated rationale and a practical test against costs and incentives**\n\n- The MOS explicitly exists to ensure safety and standardisation and to implement ICAO-derived Standards and Recommended Practices in an Australian context. (Section 1.1.1 and 1.1.5.4.)\n\n- Practical costs and burdens on providers arise from:\n  - establishing and maintaining an SMS, producing safety cases for new services or significant changes, and meeting safety case methodology standards (Sections 3.1–3.2);\n  - personnel costs for technicians with minimum qualifications and ongoing training/recency checks, plus assessor accreditation requirements (Section 5);\n  - capital and operational costs for test facilities, calibrated equipment and traceable calibration chains (Section 6);\n  - administrative costs from recordkeeping, document control and retention (Chapters 7–8);\n  - physical security and facility protection costs (Chapter 9);\n  - equipment upgrades to meet facility-specific performance or classification requirements (Chapter 10). \n\n- Incentives created by the MOS:\n  - incumbent providers with at least two years of safe operation avoid baseline safety-case work for existing services (3.2.1.3), which concentrates a compliance advantage with established operators;\n  - CASA retains discretion to accept lesser technician qualifications for simpler facilities (5.1.1.3), which can reduce costs for low‑complexity providers but creates a need to prove that complexity is low to CASA;\n  - explicit requirements for interoperability, documentation and interface agreements promote integration across providers and ATS organisations (7.1.1(e), 2.3.1(v), 7.2.1). \n\n**Trade-offs, implementation risks and likely operational effects**\n\n- Trade-offs: higher up‑front and ongoing compliance costs versus reduced operational risk and improved system interoperability. Equipment and staffing requirements can raise barriers to entry for new or small providers; the MOS contains limited mechanisms (CASA agreement to lower qualification thresholds, exemptions for long‑running services) that partly mitigate this.\n\n- Implementation risk: CASA exercises technical judgment (authority over MOS content and acceptance of safety cases and qualifications). That discretion concentrates decision‑making in the regulator and requires clear, documented CASA processes to limit uncertainty for providers (1.1.5.1–1.1.5.3).\n\n- Behavioural effects: organisations will be incentivised to document procedures, retain records, formalise competence assessment, and invest in calibration and security. Some service modifications will trigger safety cases and regulatory review, potentially slowing rapid changes but increasing oversight of safety impacts. (3.2.1.4 and 1.1.5.3.)\n\n**Key compliance milestones and easily overlooked rules**\n\n- Safety cases are required for new services or changes that are outside an organisation's certificate or that the SMS says require prior notification (3.2.1.4).\n- Technicians must be assessed by properly trained and accredited assessors before being authorised (5.2.1.2(b)).\n- Calibration traceable to national measurement standards and visible calibration status marking are mandatory (6.1.1.4–6.1.1.6).\n- Site logs must be kept for all facilities and retained for at least five years (8.2.1.1–8.2.1.4).\n\n**Sections expressly relied upon in this summary**: 1.1.1–1.1.6 (document set and hierarchy), 1.2 (definitions), 2.1–2.3 (service and facility classifications), 3.1–3.2 (SMS and safety cases), 5.1–5.2 (technician qualifications and certificates), 6.1 (test equipment), 7.1–7.2 (documents and control), 8.1–8.2 (records and logs), 9.1 (security), 10.1 (landing system standards)."},"kimi_summary":{"content_quality":"ok","complexity_score":5,"scope_assessment":{"changed":true,"description":"The original 2003 instrument appears to have focused on core telecommunication and navigation service standards. The 2006 amendments added comprehensive Safety Management System requirements (Chapter 3) and removed Chapter 4 entirely. The 2016 amendments significantly expanded scope by adding Chapter 10 with detailed technical standards for Special Authorisation Category I and II landing operations—moving beyond general service provision into specific operational approvals for low-visibility approaches. The document has evolved from basic service standards to encompass safety management systems, security programs, and precision approach certification."},"complexity_factors":["Moderate length with 10 chapters covering distinct operational domains (safety management, technician certification, equipment standards, documentation, security)","7 defined terms in Section 1.2, but heavy reliance on external definitions from ICAO Annexes and CASR Part 171/172","Extensive cross-referencing to Civil Aviation Safety Regulations (CASR), ICAO Annexes 10 and 11, and Advisory Circulars","Nested conditional requirements in Chapter 10 (Special Authorisation Category I/II operations) with multiple sub-paragraphs and alternative compliance paths","Technical specificity requiring domain knowledge (e.g., ILS classifications like 'I/T/1' and 'II/D/2', HUD-equipped aircraft distinctions)","Hierarchical document structure (Act → Regulations → MOS → ACs) with explicit primacy rules creating layered interpretation requirements","Exception provisions (e.g., 3.2.1.3 exempting services with 2+ years safe operation from baseline safety case requirements)","Competency-based training requirements referencing external Australian training frameworks (Certificate IV in Assessment and Workplace Training)"],"plain_english_summary":"This document sets out the technical and operational standards that companies must meet when providing ground-based communication and navigation services for aircraft in Australia. These services include radio towers, radar systems, instrument landing systems (ILS), and data networks that air traffic controllers rely on to keep planes safe.\n\n**Who it affects:**\n- Companies approved to provide aeronautical telecommunication and radio navigation services (such as Airservices Australia and other certified providers)\n- Technicians who install, maintain, and operate this equipment\n- Air traffic service providers who depend on these systems\n\n**What it requires:**\n- **Safety management:** Providers must have formal systems to identify hazards, assess risks, and manage safety across their operations. They must prepare \"safety cases\" (detailed risk assessments) for new services or major changes.\n- **Qualified staff:** Technicians need relevant engineering diplomas or trade qualifications, plus specific training and certification for each type of equipment they work on. Their competencies must be regularly checked.\n- **Equipment standards:** All test equipment must be properly calibrated and traceable to national standards. Facilities must meet specific technical requirements, including detailed rules for landing systems used in low-visibility \"Special Authorisation Category I and II\" operations.\n- **Documentation and records:** Providers must maintain extensive records including site logs, maintenance histories, technician qualifications, and safety assessments. Documents must be controlled to ensure staff always use current versions.\n- **Security:** Physical security programs must protect facilities from unauthorised access, animals, and deliberate damage.\n\n**Why it matters:**\nThese systems are the invisible infrastructure that allows pilots to communicate with the ground, navigate in bad weather, and land safely. A failure in these services can directly cause accidents. The standards align with international rules (ICAO Annex 10) but where Australian rules differ, the Australian standards prevail."}},"importantCases":[],"_links":{"self":"/api/acts/manual-of-standards-part-171-aeronautical-telecommunication-and-radio-navigation-services","history":"/api/acts/manual-of-standards-part-171-aeronautical-telecommunication-and-radio-navigation-services/history","analysis":"/api/acts/manual-of-standards-part-171-aeronautical-telecommunication-and-radio-navigation-services/analysis","conflicts":"/api/acts/manual-of-standards-part-171-aeronautical-telecommunication-and-radio-navigation-services/conflicts","importantCases":"/api/acts/manual-of-standards-part-171-aeronautical-telecommunication-and-radio-navigation-services/important-cases","documents":"/api/acts/manual-of-standards-part-171-aeronautical-telecommunication-and-radio-navigation-services/documents"}}