Part 175. D- Data Product Specification- Aeronautical … 175. D- Data Product Specification- Aeronautical Data Originators: CASR Part 173 Providers 6 of 32 Version 2: Effective 11

Ensure document is current before use © Airservices Australia 2017 1 of 32

Part 175. D- Data Product Specification- Aeronautical Data Originators: CASR Part 173 Providers

ATS-DPS-0006

Version 2

Effective 11 July 2017

Authorised: Grant Rawstorn ATM Data Services Manager


2 of 32 Version 2: Effective 11 July 2017 ATS-DPS-0006

Change summary Version Date Change description

1 23 May 2017 Initial Document. This document replaces ATS MAN-0085 (NRFC 34825)

2 11 July 2017 Replaced VNAV example chart (NRFC 35269) This document was created using Generic Document Template C-TEMP0047 Version 8.

Table of contents 1 Background ............................................................................................................................... 4 2 Purpose ...................................................................................................................................... 4 3 Terms and conditions ............................................................................................................... 4 4 Data Specification requirements ............................................................................................. 4 4.1 Notification dates ......................................................................................................................... 4 4.2 Data requirements ....................................................................................................................... 5 4.3 Electric format ............................................................................................................................. 5 4.4 Data alternations and error tracking ............................................................................................ 5 4.5 Data verification .......................................................................................................................... 5 4.6 Data integrity ............................................................................................................................... 6 4.7 NOTAM ....................................................................................................................................... 6 4.8 AIP Supplement .......................................................................................................................... 6 5 Publication Process .................................................................................................................. 6 6 Design Style Guide ................................................................................................................... 9 6.1 Standard Properties .................................................................................................................. 10 7 Chart Guidelines ..................................................................................................................... 15 7.1 Chart Sizing Guide .................................................................................................................... 15 7.2 Aerodrome Chart (Page 1) ........................................................................................................ 16 7.3 Aerodrome Chart (Page 2) ........................................................................................................ 17 7.4 Apron Chart ............................................................................................................................... 18 7.5 Standard Instrument Departure (SID) Procedure Chart ........................................................... 19 7.6 Standard Arrival Route (STAR) Chart ....................................................................................... 20 7.7 NDB Procedure Chart ............................................................................................................... 21 7.8 VOR/DME Procedure Chart ...................................................................................................... 22 7.9 ILS and/or LOC Procedure Chart .............................................................................................. 23 7.10 DME or GNSS Arrival Procedure Chart .................................................................................... 24 7.11 RNAV (GNSS) Procedure Chart ............................................................................................... 25 7.12 RNAV (GNSS) Procedure Chart- Baro-VNAV (if applicable) .................................................... 26 7.13 RNP-AR Procedure Chart ......................................................................................................... 27 7.14 Colour Charts (Contours) .......................................................................................................... 28 8 ARINC 424 Coding Table (Template) ..................................................................................... 29 9 Procedure Verification Certificate (Template) ...................................................................... 30 10 Definitions ................................................................................................................................ 32


ATS-DPS-0006 Version 2: Effective 11 July 2017 3 of 32

11 References ............................................................................................................................... 32



1 Background Airservices Australia (Airservices) ATM Data Services: Aeronautical Information Management business unit, under the Air Services Act 1995, provides aeronautical data/information necessary for the safety, regularity and efficiency of air navigation, giving effect to Australia’s obligation under the Chicago Convention on International Civil Aviation.

Civil Aviation Safety Regulation (CASR) Part 175 under the Civil Aviation Act 1988 establishes standards and requirements for the quality and integrity of data and information used in air navigation, in particular as published in the Aeronautical Information Publication (AIP), on aeronautical charts and contained within aeronautical navigation databases.

As the principal supplier of aeronautical information service for Australia, Airservices is responsible for the publishing of aeronautical documentation, which is then distributed to pilots and businesses in Australia, and around the world.

Under CASR Part 175, Airservices must provide an aeronautical data originator (CASR Part 173 Service Provider) with a Data Product Specification (DPS), so that aeronautical data can be obtained through a quality controlled process.

2 Purpose The purpose of this document is to prescribe the information exchange protocols for the submission, modification and withdrawal of aeronautical data or information which may be published in the Integrated Aeronautical Information Publication (IAIP), or Aeronautical Datasets.

3 Terms and conditions This document has been developed to provide all CASR Part 173 approved procedure design organisations (the Provider) with the information necessary to produce and submit procedure charts (Procedures) for publication that are compatible with the Australian AIP format.

This document also establishes the processes and procedures for how the Provider must coordinate with Airservices in the publishing of Procedures in the Australian AIP.

4 Data Specification requirements

4.1 Notification dates Information or data can be provided or submitted to Airservices at any time throughout the year. However, the data must be submitted by specific cut-off dates in order to be published in the next available amendment, as detailed in the publication calendar: http://www.airservicesaustralia.com/publications/document-amendment-calendar/

http://www.airservicesaustralia.com/publications/document-amendment-calendar/



Note: 1) Airservices Aeronautical Database is updated in line with the Aeronautical

Information Regulation and Control (AIRAC) date; incorporating the new data into our publications every three to six months.

2) The AIRAC Effective Date is the internationally agreed date at which time-critical aeronautical documentation, the IAIP, becomes effective. Consequently, CASR Part 175 has regulatory obligations for the AIS Provider and for the Data originator in respect of the AIRAC timing and change management processes. Depending on the nature of the aeronautical data, 28 or 56 days notification periods apply as defined in the ICAO SARPS.

3) Aeronautical Data should be supplied to Airservices for publication in the IAIP and on Aeronautical Charts in alignment with the Aeronautical Information Regulation and Control (AIRAC) list of Effective Dates.

4.2 Data requirements The style properties for charts is defined in Design Style Guide in this document. Data entry format for aeronautical information used in AIP Products is as per the requirements in ICAO Annex 4 and Annex 15. Incomplete information may be returned to the proponent for clarification purposes.

4.3 Electric format The authenticated electronic means by which aeronautical information and data is supplied to Airservices is by email. The common method to ensure that Airservices can readily identify any changes from existing published data or information is to use “mark-up” format to indicate where changes are required or to provide complete new text.

4.4 Data alternations and error tracking Requests for alterations to the aeronautical data are to be communicated to Airservices by email request to [email protected]

Airservices should be advised of any new, amended, or deleted information.

Airservices should be notified when an error has occurred in the data or information. Errors detected in the data must also be notified to: [email protected]

4.5 Data verification Data Originators must nominate to Airservices, persons who have the knowledge and competence to carry out the responsibilities of an “AIP responsible person”. A registration form is available for this purpose and can be requested from Airservices via email: [email protected]

mailto:[email protected]





4.6 Data integrity Source data can only be accepted from the registered Data Originator. The registered Data Originator has an enduring responsibility for the accuracy levels of the data or information, and must ensure that the data is reviewed at least annually and immediately inform Airservices of any changes to the data.

4.7 NOTAM NOTAM requests must be coordinated with the DAP Editor.

4.8 AIP Supplement Information promulgated by AIP Supplement, must be coordinated with Airservices and must adhere to the defined notifications periods required for the AIRAC.

5 Publication Process The Provider will follow the publication process for Procedures as set out below:

1) All procedures must be presented in accordance with the Design Style Guide as described in this document.

2) All waypoint identifiers are to be obtained/checked and approved by the ATM Data Services prior to the submission of any design for publishing. Requests are to be sent to: [email protected]

3) During the design or amendment of a Procedure by the Provider (which will require publication by the ATM Data Services), the Provider must seek Air Traffic Control coordination in order to determine if there is any effect on existing procedures or other potential safety issues (refer Notes at the end of this section)

4) A final Procedure Chart in the format required by the ATM Data Services, and as detailed in the Design Style Guide should be sent to: [email protected]

5) If the new Procedure is at a location that does not currently have an Aerodrome Chart then one is to be provided by the Provider as detailed in the Design Style Guide. This should be sent to: [email protected]

6) The Procedure, when supplied to Airservices, is to include the following information:

a) a copy of the Procedure Verification Certificate (template attached) acknowledging/verifying that all approvals have been given, and with all supporting documentation, in electronic format, attached;

b) acknowledgement that CASA approval has been received, and the approver’s name provided;

c) signed confirmation that an appropriate environmental assessment has been carried out in relation to the Procedure;

d) a copy of the environmental assessment;






e) a copy of any correspondence provided by Air Traffic Control, (including confirmation that the required coordination by Air Traffic Control has occurred);

f) a list of critical obstacles relevant to the procedures provided, as well as any available survey reports;

g) a list of waypoint coordinates (coordinate definition is to be 1/100 of a second of arc in WGS-84) relevant to the procedures provided;

h) Procedure coding information in the form of ARINC 424 coded waypoints, and path terminator definitions relevant to the Procedure provided;

i) all raw data necessary to support ARINC 424/FMS coding must be provided in electronic format for the purposes of publication, data storage and release to third parties for coding;

j) a copy of the Procedure in Adobe PDF format Version 9 (unless otherwise advised by Airservices) with the effective date and page reference numbers enabled as editable; and

k) a digital file in Bentley Microstation DGN (or compatible) format, if requested by Airservices.

7) Airservices will advise of the likely publication date using the e-mail address of the Provider as detailed in the Procedure Verification Certificate.

8) The Provider shall monitor NOTAM published by the NOTAM Office (NOF), to guarantee integrity of a designed Procedure. The Provider shall notify the ATM Data Services and NOF of Procedure amendments, as required.

9) If a Provider determines that a NOTAM is required, all details are to be provided to: [email protected]

10) The use of any Waypoints must be coordinated with Airservices by sending an email to [email protected]

All waypoints (except RNAV (GNSS)) must be obtained from Airservices, the waypoint can only be published after ICAO approved the intended use of the applicable waypoint based on a proximity check in the ICAO ICARD (International Codes and Routes Designators) system.

11) RNAV (GNSS) Procedure waypoints shall be named using a unique five letter code and should not be pronounceable, eg: SCBWA.

• The first three letters will be the last three letters of the airport ICAO code identifier (eg: SCB for YSCB). An alternative is the use of the aerodrome IATA code, where the ICAO code is not available for use. Airservices will advise the first three letters where ICAO and IATA codes are not available.

• The fourth letter will be the direction from which the procedure approaches the airport (eg: N, S, E, or W). It should be based on true direction; however exceptions can be made with reasoning.

• The fifth letter will identify the procedure fix type (I for the IF, F for the FAF, M for the MAPt, T for the MATF and H for the MAHF).

• A right hand offset IAF of the first RNAV procedure at an aerodrome shall be suffixed by the letter ‘A’. Subsequent IAF’s shall have their suffix increment alphabetically clockwise around the aerodrome. The suffix reserved for subsequent fixes, and other uses, shall not be used. This will





exclude ‘I’, ‘F’, ‘M’, ‘T’,’H’, ‘O’ and combination ‘NB’ (where procedure is from North). IAF letters should not be used more than once at an aerodrome.

NOTES:

1. Should the Provider seek the services of Airservices ATC resources in the development of the Procedures, the services will be provided under the terms and conditions of a Services Agreement or Deed of Standing Offer.

2. The Provider will not be charged a fee for the publishing of a Procedure, but should AIM services be required external to the Publication Process, the services will be provided under the terms and conditions of a Services Agreement or Deed of Standing Offer.

3. All relevant Aeronautical Data provided to Airservices will be included in the state AIP.



6 Design Style Guide This style guide consists of sample charts for the following chart types:

• Aerodrome Chart • Apron Chart • Standard Instrument Departure (SID) Procedure • Standard Terminal Arrival Route (STAR) Procedure • NDB Procedure • VOR/DME Procedure • ILS and/or LOC Procedure • DME or GNSS Arrival Procedure • RNAV (GNSS) Procedure • RNAV (GNSS) Baro-VNAV Procedure • RNP-AR Procedure • Colour Chart (Contours)

As well as a chart sizing guide, which applies to all chart types, the following legends are applicable throughout the guide, and in the production of the charts.

LINE WEIGHT (WT) LINE STYLE (LC)

LINE TYPE WEIGHT (mm)

1 0.050

3 0.170

5 0.350

10 0.480

14 0.650

20 0.800

LINE STYLE (mm)

0 0.0

1 (0.40,0.30)

2 (1.75,1.05)

3 (1.60,0.70)

4 (2.8,1.05)(0.70,1.05)

5 (1.40,1.40)

6 (2.10,0.70)(0.70,0.70)(0.70,0.70)

7 (2.80,0.70)(1.40,0.70)

FONT STYLE (FT)

MISCELLANEOUS

ABRV FONT STYLE

FT=A - Arial

FT=AI - Arial Italic

FT=AB - Arial Bold

FT=ABI - Arial Bold Italic

FT=A,Black - Arial Black

ABRV MEANING

FT - FONT

TX - TEXT SIZE (mm)

LV - LEVEL

CO - COLOUR

C/S - % CADscript SHADE

WT - LINE WEIGHT

LC - LINE STYLE

R/S - ROW SPACING (mm)

Table 1: STANDARD STYLE LEGENDS FOR ALL CHARTS



6.1 Standard Properties There are a number of standard properties that are to be applied to all charts in addition to the provisions of ICAO Annex 4 – Aeronautical Charts, as outlined below:

6.1.1 Chart Sizing/Layout Plates published by Airservices must adhere to the sizing as represented in the Sizing Diagram as demonstrated below in this style guide. The size of individual boxes may be adjusted to accommodate details, but should retain the proportions shown in this guide.

6.1.2 Scale In general all the Procedure Charts are drawn 1:500 000.

The scale varies on: • Aerodrome Charts - from 1:20 000 to 1:50 000 • Apron Charts - from 1:6 000 to 1:15 000 • Helicopter Landing charts (in general based on 1:500 000. Any scale variations

are specified on the chart).

The linear scale bar is required on every chart with topographic data, indicating the scale value and distance in nautical miles (NM).

The general scale bars are provided as Cells and are outlined in the Symbol/Cell Library.

6.1.3 Typography The only two fonts permitted for use on plates published by Airservices are Arial and Arial Black.

The text depicted in this guide is listed in mm, where this measurement equals the height of the text. When using TrueType and PostScript fonts, the listed mm size can be converted to a point size by multiplying by 72 and dividing by 25.4 (25.4mm = 72pt). A visual check should be made to ensure a match with the text sizes that have been used by Airservices.

6.1.4 Colour Table Colour used on any chart shall come from the colour table utilised by Airservices to ensure consistency with charts being incorporated into the DAP.

The colour table file (in format .tblis) is available from Airservices, and can be request by email: [email protected]

6.1.5 Shading Shading is indicated as appropriate using Bentley CADScript properties, in accordance with the legend supplied in this guide.




6.1.6 Use of Logo Procedures design organisations are permitted to place their logo on the bottom of the page, however, the logo used should not exceed the dimensions of 8mm (height) x 30mm (width).

6.1.7 Symbols/Cells Symbols/Cells used on all charts must be from the Airservices Cell Library as detailed below:



6.1.8 Projection UTM Projection is used on all charts.

The UTM system employs zones, each 6° of longitude in width. The coordinate format is shown in DEGREES MINUTES SECONDS (DMS). Parallels and meridians with graduation marks along the edge of the chart are shown at:

• 10 minute interval on Procedure Charts • 1 minute interval on Aerodrome Chart

6.1.9 Magnetic Variation The charts include the True North and Magnetic Variation symbol, with either an East or West value.



6.1.10 Topography The following data is represented on charts [Reference: ICAO. (2009). Annex 4 - Aeronautical Charts]: • Drainage and hydrographical detail: large open water features with generalized

shorelines, lakes, rivers and seasonal waterways. • Built up areas of major urban centres. • Buildings associated with the aerodrome. • Roads and Railways. • Contours (relief), when required. • Spot elevations that constitute a hazard to air navigation.

River LV=12 CO=1 WT=10 CS=0.85

Major Road LV=7 CO=4 WT=14 CS=0.85

Contours LV=2 CO=140 WT=2 CS=0.5 Filled with colours as specified In CONTOUR STANDARDS p. 25

Railway CELL: RLWY LV=6 CO=2 WT=10 CS=0.85

Build-Up Area LV=1 CO=21 CELL: BUA150/150

Water Body LV=12 CO=1 WT=10 CS=0.85 Filled with CO=1 and CS=0.85



6.1.11 Contour (Relief) Relief on charts is shown if the approach gradient is other than 3° or if the spot height level is 600m (2000ft) above the aerodrome elevation within 6NM radius or if spot height level is 1200m (4000ft) above aerodrome elevation within the coverage of the chart. All relief exceeding 150m (500ft) above aerodrome elevation shall be shown by smoothed contour lines, contour values and layer tints printed in brown. [Reference: ICAO. (2009). Annex 4 - Aeronautical Charts]

Contour Interval: Increment at 150m (500ft).

Contour Outline: Each contour to have an outline: CO=136, WT=2, C/S=0.5

Contour values: FT=Al, CO=140 TX=0:0:280.

If the background consists of dark shades - allow for masking behind the contour values using block filled with CO=2.

CONTOUR Above AD ELEV

COLOUR (ASA Table)

C/S (%) COLOUR TINT

GRAYSCALE TINT

8th Contour 237 0.05





3rd Contour 100 0.55

2nd Contour 50 0.65

1st Contour 20 0.75



7 Chart Guidelines

7.1 Chart Sizing Guide



7.2 Aerodrome Chart (Page 1)



7.3 Aerodrome Chart (Page 2)



7.4 Apron Chart



7.5 Standard Instrument Departure (SID) Procedure Chart



7.6 Standard Arrival Route (STAR) Chart



7.7 NDB Procedure Chart



7.8 VOR/DME Procedure Chart



7.9 ILS and/or LOC Procedure Chart



7.10 DME or GNSS Arrival Procedure Chart



7.11 RNAV (GNSS) Procedure Chart



7.12 RNAV (GNSS) Procedure Chart- Baro-VNAV (if applicable)



7.13 RNP-AR Procedure Chart



7.14 Colour Charts (Contours)

NOTE: Line styles and font specifications as per standard procedure charts.

For contour details refer to ‘Contour (Relief)’ in this document.



8 ARINC 424 Coding Table (Template) The table below is the acceptable format for Airservices to receive ARINC 424 data from external suppliers. In addition to the below table, data should also be supplied in an original raw data format.

The below table is available as an excel spreadsheet from Airservices, upon request from: [email protected]





9 Procedure Verification Certificate (Template)

AERODROME (or identifier):

List of NEW / AMENDED procedures to be incorporated into the Australian AIP Departure and Approach Procedures (DAP) 1 6

2 7

3 8

4 9

5 10

Approval / Authorisation / Requirement Attached

/ Approver or Assessment provided by (Name),

if applicable Environmental Assessment

ATC Assessment

CASA Approval

Waypoint Names Approved

Waypoint Co-ordinates Provided

Critical Obstacle List Provided

Procedure coding information in ARINC424

Comments: Name and email address for correspondence relating to these procedures:

All design and validation work is compliant with CASR Part 173 Manual of Standards and/or ICAO Document 8168 (PANS-OPS), as appropriate.

Chief Designer Name:

Chief Designer Signature: Date:

PROCEDURE VERIFICATION CERTIFICATE TEMPLATE

Part 2 – Chief Designer Certification (173.100(1))

Part 1- Production Record



WILL BE PROVIDED BY AIRSERVICES IN WORD FORMAT

FOR USE BY ALL PART 173 PROVIDERS ON REQUEST



10 Definitions Within this document, the following definitions apply:

Term Definition

AIP Aeronautical Information Publication

AIRAC Aeronautical Information Regulation and Control

CASA Civil Aviation Safety Authority

CASR Civil Aviation Safety Regulation

DPS Data Product Specification

IAIP Integrated Aeronautical Information Package

WGS-84 World Geographic System 1984

11 References Title Number

ICAO Annex 4: Aeronautical Charts

ICAO Annex 14: Aerodromes

ICAO Annex 15: Aeronautical Information Services

ICAO Doc 8126: Aeronautical Information Services Manual

ICAO Doc 8168: Flight procedures

CASR Part 139: Aerodromes

CASR Part 173: Instrument Flight Procedure Design

CASR Part 175: Aeronautical Information Management

ISO 9000 Quality Management

MOS Part 139: Aerodromes

Documents

Part 175. D- Data Product Specification- Aeronautical … 175. D- Data Product Specification- Aeronautical Data Originators: CASR Part 173 Providers 6 of 32 Version 2: Effective 11