report of - ICAO

REPORT OF

THE TWELFTH MEETING OF ASIA AND PACIFIC

REGIONAL OPERATIONAL METEOROLOGICAL (OPMET)

BULLETIN EXCHANGE WORKING GROUP (ROBEX WG/12)

17 – 19 March 2014

Beijing, China

Approved by the Meeting

and published by the ICAO Asia and Pacific Office, Bangkok

INTERNATIONAL CIVIL AVIATION ORGANIZATION

ASIA AND PACIFIC OFFICE

The views expressed in this Report should be taken as those of

the Meeting and not the Organization.

ROBEX WG/12 i-1

Table of Contents

History of the Meeting Page

Introduction ............................................................................................................................................. i-3

Attendance .............................................................................................................................................. i-3

Opening of the Meeting .......................................................................................................................... i-3

Chair and Secretariat ............................................................................................................................... i-3

Organization and language of the meeting ............................................................................................. i-3

Required action recorded by the meeting ............................................................................................... i-3

Report on ROBEX WG/12

Agenda Item 1: Organizational matters:

a) Adoption working arrangements ............................................................................... 1

b) Adoption of agenda ................................................................................................... 1

Agenda Item 2: Review of follow-up from previous meetings:

a) Action arising from ROBEX WG/11 ........................................................................ 3

b) Relevant APANPIRG/24 Conclusions ...................................................................... 3

Agenda Item 3: OPMET information:

a) OPMET availability .................................................................................................. 5

b) OPMET timeliness and regularity ............................................................................. 5

c) Status reports from the Regional OPMET Data Banks ............................................. 7

Agenda Item 4: OPMET exchange:

a) IROG Back-up procedures and tests ....................................................................... 10

b) RODB monitoring and quality control procedures ................................................. 10

c) Exchange of OPMET in a digital format ................................................................. 10

d) Other ROBEX issues ............................................................................................... 10

Agenda Item 5: Guidance material:

a) ROBEX Handbook .................................................................................................. 12

b) APAC ICD .............................................................................................................. 12

c) OPMET related FASID tables ................................................................................. 13

Agenda Item 6: Future work programme and review of terms of reference ........................................... 14

Agenda Item 7: Any other business ......................................................................................................... 14

ROBEX WG/12

Table of Contents

i-2

Report on Conjoint Session of ROBEX WG/12 and MET/H TF/4

Agenda Item 1: VAAC back-up tests ...................................................................................................... 15

Agenda Item 2: SIGMET and Advisory Information

- SIGMET test/Regional SIGMET monitoring and coordination .................................. 16

- Review SIGMET Guide .............................................................................................. 18

- Advisory information .................................................................................................. 18

- Other SIGMET/advisory related business ................................................................... 19

List of Attachments

Attachment 1: List of Participants

Attachment 2: List of Working and Information Papers

Attachment 3: Follow-up of ROBEX WG/12 agreed action

Attachment 4: Order of business

Attachment 5: Follow-up of ROBEX WG/11 agreed action

Attachment 6: APANPIRG/24 Conclusions/Decisions – Action Plan (MET-related)

Attachment 7: Work programme

List of Attachments for the conjoint session

Attachment C1: Wellington/Darwin VAAC back-up test procedures

Attachment C2: Scheme of cooperation between VAACs Tokyo-Darwin

Attachment C3: Summary of WC and WV SIGMET test results

Attachment C4: WS SIGMET test result by Singapore

Attachment C5: Template and draft form for ASIA/PAC SIGMET Guide, 5th Edition

Attachment C6: Proposed changes to ASIA/PAC SIGMET Guide, 5th Edition by Hong Kong, China

Attachment C7: Proposed changes to ASIA/PAC SIGMET Guide, 5th Edition by Australia

_ _ _ _ _ _ _ _ _ _ _ _ _

ROBEX WG/12 i-3

History of the Meeting

1. Introduction

1.1 The Twelfth Meeting of the Asia and Pacific (APAC) Regional Operational

Meteorological (OPMET) Bulletin Exchange Working Group (ROBEX WG/11) of the Meteorology

Sub-group (MET SG) of the APAC Air Navigation Planning and Implementation Regional Group

(APANPIRG) was held in Beijing, China, from 17 to 19 March 2014. A conjoint session with the

Fourth Meeting of the Meteorological Hazards Task Force (MET/H TF/4) was conducted on 19

March 2014.

2. Attendance

2.1 The meeting was attended by 33 experts from Australia, Cambodia, China, Fiji

Islands, India, Indonesia, Japan, New Zealand, the Philippines, Republic of Korea (ROK), Singapore,

Thailand, Viet Nam and the International Civil Aviation Organization (ICAO). Additional 7

participants from China, Hong Kong-China, Japan and Thailand joined the meeting for the conjoint

session with the MET/H TF/4 on 19 March 2014. The List of Participants is provided in Attachment

1 to this Report.

3. Opening of the meeting

3.1 Mr. Xiao Jing, Deputy Chief, APAC Regional Sub-Office, provided opening remarks

to the meeting and extended a welcome to all the participants to the ICAO Regional Sub-Office.

4. Chair and Secretariat

4.1 Ms. Sujin Promduang presided over the meeting in the role as chairperson of the

ROBEX WG and was assisted by Mr. Chan Pak Wai, chairperson of the MET/H TF, during the

conjoint session on 19 March 2014.

4.2 Mr. Peter Dunda, Regional Officer, Aeronautical Meteorology, acted as Secretary of

the meeting.

5. Organization and language of the meeting

5.1 The meeting met as a single body. Working language was English including all

papers and this report. The meeting considered 15 Working Papers, 4 Information Papers and 1

flimsy, plus 6 Working Papers and 6 Information Papers in the conjoint session with MET/H TF/4. A

list of papers is provided in Attachment 2 to this Report.

6. Required action recorded by the meeting

6.1 Agreed action by the meeting is recorded in the table in Attachment 3 to this Report.

_ _ _ _ _ _ _ _ _ _ _ _ _

ROBEX WG/12 1

Report on Agenda Items

Agenda Item 1: Organizational matters:

a) Adoption working arrangements

b) Adoption of agenda

1.1 The agenda was adopted by the meeting as follows:

Agenda Item 1: Organizational matters

a) Adoption working arrangements

b) Adoption of agenda

Agenda Item 2: Review of follow-up from previous meetings

a) Action arising from ROBEX WG/11

b) Relevant APANPIRG/24 Conclusions

Agenda Item 3: OPMET information

a) OPMET availability

b) OPMET timeliness and regularity

c) Status reports from the Regional OPMET Data Banks

Agenda Item 4: OPMET exchange

a) IROG Back-up procedures and tests

b) RODB monitoring and quality control procedures

c) Exchange of OPMET in a digital format

d) Other ROBEX issues

Agenda Item 5: Guidance material

a) ROBEX Handbook

b) APAC ICD

c) OPMET related FASID tables

Agenda Item 6: Future work programme and review of terms of reference

Agenda Item 7: Any other business

2 ROBEX WG/12


Conjoint session ROBEX WG/12 / MET/H TF/4 (19/03/2014)

Agenda Item 1:

VAAC Backup Tests

Agenda Item 2: SIGMET and advisory information

a) SIGMET tests

b) Regional SIGMET monitoring and coordination

c) Review SIGMET Guide

d) Advisory information

e) Other SIGMET/advisory related business

1.2 The proposed order of business of the meeting, including the conjoint session with the

MET/H TF/4 meeting on Wednesday 19 March 2014, was adopted by the chairperson as a guide for

the conduct of the meeting. The order of business is given in Attachment 4 to this Report.

_ _ _ _ _ _ _ _ _ _ _ _ _

ROBEX WG/12 3


Agenda Item 2: Review of follow-up from previous meetings

a) Action arising from ROBEX WG/11

b) Relevant APANPIRG/24 Conclusions

ROBEX WG/11

2.1 The meeting reviewed progress on the 9 items (11/1 – 11/9) agreed for action by the

eleventh meeting of the Regional OPMET Bulletin Exchange Working Group (ROBEX WG/11), held

in Bangkok, Thailand from 11 to 13 March 2013, including 3 items agreed for action by the conjoint

session (ROBEX WG/11 / MET/H TF/3 on 13 March 2013) and allocated to the ROBEX WG for

follow-up (WP/2 refers).

2.2 The meeting considered 3 of the items agreed for action in 2013 to be completed and

the remaining 6 to be in progress. A table summarizing the agreed actions and the status of follow-up

is contained in Attachment 5 to this Report.

2.3 With respect to 11/3 – IROG back-up procedures, Australia advised the meeting that

its current systems were unable to support the back-up of another Inter-regional OPMET gateway

(IROG), however Australia was planning to upgrade its systems in approximately 2 years, at which

time back-up arrangements for IROG Tokyo could be pursued.

2.4 In relation to 11/8 – Follow-up on SIGMET monitoring, Australia apprised the

meeting of assistance it provided to the Solomon Islands (January 2014) in collaboration with the

World Meteorological Organization (WMO) in the form of training and assessment of aeronautical

meteorological personnel in the preparation of SIGMET (and TAF) and that a report on the activity

and recommended actions was provided to the WMO and the Solomon Islands and a copy of the

report will be provided to ICAO.

2.5 Also related to 11/8 – Follow-up on SIGMET monitoring, the meeting noted that

Australia was in the process of planning an assistance activity in Papua New Guinea that would

perform an assessment (diagnostic) of that State’s national weather service and had invited the ICAO

to participate in the activity as the subject matter expert for aeronautical meteorological service.

ICAO’s participation would provide an opportunity for technical assistance to Papua New Guinea to

facilitate the implementation of ICAO provisions for aeronautical meteorological service, particularly

for SIGMET.

APANPIRG/24

2.6 The meeting reviewed progress on the 5 Conclusions and 3 Decisions closely related

to the field of meteorology (MET) adopted by the twenty fourth meeting of the APAC Air Navigation

Planning and Implementation Regional Group (APANPIRG/24), held in Bangkok, Thailand from 24

to 26 June 2013 (WP/3 refers).

2.7 The meeting noted that follow-up to 4 of the Conclusions and 1 Decision from

APANPIRG/24 was completed and the follow-up to 1 Conclusion and 2 Decisions was in progress. A

table summarizing the status of follow-up to the APANPIRG/24 Conclusions and Decisions closely

related to MET is contained in Attachment 6 to this Report.

2.8 In relation to C 24/48 – Migration to WAFS gridded global forecasts in WMO GRIB

Edition 2 code form as soon as possible, Australia apprised the meeting of assistance it provided to

Fiji (Nov 2013 – March 2014) for an interim source of GRIB Edition 1 code form data, sourced from

WAFC Washington via the GTS, in the period after the date at which the WAFS Provider States were

invited to cease the transmission of WAFS products in WMO GRIB Edition 1 code form. Fiji reported

4 ROBEX WG/12


that it was yet to organize an operational data feed for GRIB Edition 2 code form data and was

seeking support from Fiji MET service. The meeting noted that, as this issue was more closely related

to the work of the WAFS Task Force (WAFS TF), the Secretariat would coordinate with the WAFS

TF and provide any necessary technical advice to Fiji to facilitate its migration to GRIB Edition 2

code form.

2.9 In relation to D 24/52 – Survey on the implementation of meteorological competency,

Australia apprised the meeting that the WMO had provided training to States in the Regional

Association V on meteorological competencies and quality management systems and, as part of this

activity, WMO was assessing the implementation of meteorological competencies amongst States. In

view of the above, the meeting noted that the ICAO should coordinate with the WMO where possible

with respect to the survey on the implementation of meteorological competency for aeronautical

meteorological personnel in the APAC Region.

_ _ _ _ _ _ _ _ _ _ _ _ _ _

ROBEX WG/12 5


Agenda Item 3: OPMET information:

a) OPMET availability

b) OPMET timeliness and regularity

c) Status reports from the Regional OPMET Data Banks

OPMET availability, timeliness and regularity

3.1 The meeting reviewed results of monitoring of the availability of OPMET data from

the APAC Region on the Satellite Distribution System for Information Relating to Air Navigation

(SADIS) and WAFS internet file service (WIFS) over a period of 9 weeks (commencing 26 December

2013) conducted by the International Air Transport Association (IATA) (WP/10 refers).

3.2 Monitored against the OPMET requirements set out in the APAC air navigation plan,

volume II, Facilities and Services Implementation Document (FASID) Table MET 2A, dated

February 2014, and IATA’s criteria for regular and satisfactory OPMET availability (data available in

at least 7 of the 9 weeks of monitoring and at least 75% of the total expected number of messages

received), the IATA showed that 90.0% of METAR (SA) and 92.4% of TAF (FT) were available

meeting the criteria above for APAC Aerodrome Operational Planning (AOP) aerodromes. IATA

considered that all other AOP aerodromes did not meet its requirements for OPMET availability.

3.3 Similarly, the IATA showed that 83.2% of METAR (SA) and 96.8% of TAF (FT)

were available meeting the criteria above for Non-AOP aerodromes. IATA considered that all other

Non-AOP aerodromes did not meet its requirements for OPMET availability.

3.4 The meeting noted that, while IATA had observed a significant improvement in

OPMET availability from the APAC Region in recent years, IATA highlighted (in the attachments to

WP/10) numerous locations where OPMET availability during the monitoring period did not meet its

requirements.

3.5 The Philippines indicated that possible misalignment of the FASID Table MET 2A

requirements with respect to the current requirements for OPMET data from Non-AOP aerodromes in

the Philippines may have contributed to the IATA OPMET monitoring results that showed

information from some locations did not meet requirements.

3.6 The meeting also noted that the monitoring results provided by IATA showed (for

some locations) OPMET was unavailable in WIFS but was available in SADIS, indicating that the

flow of OPMET to the WIFS gateway may require further investigation to identify the cause of the

observed discrepancies.

3.7 In discussing the distribution of OPMET from the APAC Region to the SADIS and

WIFS gateways, the meeting agreed it would be useful for the Secretariat to liaise with the SADIS

and WIFS Provider States to ensure that adequate contingencies are built in to the ROBEX system to

ensure consistency of APAC OPMET availability on the two systems.

3.8 The meeting noted that IATA had incorrectly referred to “ftp” (in WP/10) as the data

provision used in WIFS, which was not technically correct, however the meeting also noted this had

no significant bearing on the validity of the OPMET monitoring results presented to the meeting.

3.9 Additionally, the meeting noted that IATA had stated that “All OPMET data

currently available should be distributed”. While the meeting considered that was valid insofar as all

OPMET information (METAR, SPECI and TAF) required in SADIS and WIFS should be distributed

in accordance with the requirements listed in FASID Table MET 2A, the meeting also noted that the

6 ROBEX WG/12


provision of OPMET for Non-AOP aerodromes was entirely at the discretion of States, so where

States had not agreed to provide OPMET for Non-AOP aerodromes (in FASID Table MET 2A) the

OPMET data for such locations may not be distributed.

3.10 The meeting reviewed results of monitoring of the compliance, regularity and

availability of OPMET data from the APAC Region conducted by Regional OPMET Data Banks

(RODBs) Singapore, Tokyo and Bangkok between 1 and 31 January 2014 in accordance with the

methodology provided in the APAC ROBEX Handbook (WP/5, WP/11 and WP/13 refer).

3.11 The meeting noted that the table of results presented by Japan indicated that some

individual locations recorded significantly low performance indices.

3.12 The results presented by Thailand showed a comparison of OPMET received by the 4

APAC RODBs (Bangkok, Brisbane, Singapore and Tokyo) which, in the case of 49 locations for

METAR and 46 locations for TAF, had significant differences in the results indicating that there may

have been differences between RODBs in their application of the monitoring procedures, which, if

true, should be resolved.

3.13 The results presented by Thailand also showed that METAR was not available at 33

locations and TAF was not available from 5 locations.

3.14 The table below shows the average of each of the three indices for compliance,

regularity and availability measured by RODB Singapore:

Jan 14 Compliance Index Regularity Index Availability Index

FT 0.95 0.95 0.98

SA 0.84 0.89 0.96 Table 1: PIs for OPMET Measurement, 1-31 January 2014 (measured by RODB Singapore)

3.15 The following table highlights the low compliancy for TAF and METAR

exchanged under the ROBEX Scheme as measured by RODB Singapore:

ROBEX WG/12 7


Table 2: Low Compliancy for TAF and METAR, 1-31 January 2014 (measured by RODB Singapore)

3.16 The following tables summarize the missing OPMET in the ASI and PAC region that

were not received during the monitoring period in accordance with Annex 1 of SADIS User Guide /

FASID Table MET 2A:

Table 3: OPMET availability in ASI region, 1-31 January 2014 (measured by RODB Singapore)

TTAAii CCCC Compliancy

FTPS31 NLWW 0.00

FTPS31 NSTU 0.00

FTPS31 NWWW 0.00

FTIN32 VNKT 0.27

FTIN32 VOHY 0.00

FTIN32 VRMM 0.00

TTAAii CCCC Compliancy TTAAii CCCC Compliancy

SANG31 AYGN 0.03 SATH41 VTSK 0.00

SANG31 AYMH 0.00 SATH32 VTSR 0.00

SANG31 AYMO 0.02 SATH33 VTUI 0.50

SANG31 AYNZ 0.06 SATH41 VTUJ 0.00

SANG31 AYPY 0.38 SATH33 VTUO 0.37

SANG31 AYVN 0.04 SATH33 VTUQ 0.00

SANG31 AYWK 0.08 SAID31 WABB 0.17

SAPS31 NGTA 0.00 SAID33 WABP 0.00

SAPS31 NIUE 0.23 SAID33 WAJJ 0.00

SAPS32 NLWW 0.00 SAID33 WAKK 0.00

SAPS31 NSTU 0.00 SAID33 WALR 0.00

SAPS32 NVSS 0.00 SAID32 WAMM 0.01

SAPS32 NVVV 0.03 SAID33 WATT 0.25

SAPK31 OPGD 0.00 SAID33 WICT 0.00

SAIN33 VQPR 0.44 SAID31 WIDD 0.45

SATH31 VTCP 0.48 SAID32 WIDN 0.00

SATH41 VTPB 0.04

Compliance Indices for TAF < = 0.5 and = 0

Compliance Indices for METAR < = 0.5 and = 0

8 ROBEX WG/12


Table 4: Missing TAF/METAR shown by their respective location identifiers in the ASI region, 1-31 January

2014 (measured by RODB Singapore)

Table 5: OPMET availability in PAC region, 1-31 January 2014 (measured by RODB Singapore)

Table 6: Missing TAF/METAR shown by their respective location identifiers in the PAC region, 1-31 January

2014 (measured by RODB Singapore)

3.17 The meeting noted that the monitoring by RODB Singapore showed reasonably good

results of between 95% and 98% on average for TAF compliance, regularity and availability during

the 31-day monitoring period. However, the information provided by RODB Singapore also showed a

comparatively low result of 84% for the compliance of METAR and, furthermore, this was

attributable to a small number of locations with significantly low compliance indices. The monitoring

results also showed a significant number of aerodromes in the region for which METAR reports were

not available.

3.18 The meeting also noted the following results reported by RODB Singapore:

Both TAF and METAR were not available at 4 aerodromes listed in the AOP

Tables;

TAF was not available at 2 aerodromes listed in the AOP Tables and 2 Non-AOP

aerodromes;

ROBEX WG/12 9


METAR was not available at 8 aerodromes listed in the AOP Tables and 11 Non-

AOP aerodromes;

Overall, TAF was available for 97% of AOP and non-AOP aerodromes; and

Overall, METAR was available for 93% of the AOP aerodromes and 86% of non-

AOP aerodromes – compared with the respective ROBEX WG targets of 95%

and 90%.

3.19 The meeting also noted that a repetition of poor OPMET monitoring results for some

locations in recent years may indicate long-term problems at some locations, which would require

urgent attention.

3.20 In view of the above discussions, and to facilitate further improvements in OPMET

availability in the APAC Region, the meeting agreed that the RODBs in coordination with the

Secretariat should investigate the results provided by IATA where OPMET availability (on SADIS

and WIFS) did not meet the requirements of IATA and to address any issues identified, such as

incorrect distribution lists or misalignment of requirements in the FASID Table MET 2A, that would

prevent achieving optimal availability of OPMET. The meeting also agreed the Secretariat should

coordinate with States to address the issues that resulted in poor results of OPMET monitoring for the

specific locations identified by OPMET monitoring activities (Agreed action 12/1 refers).

3.21 With respect to the regional procedures and practices for OPMET monitoring as

agreed in the ROBEX Handbook, which required all RODBs to participate, the meeting noted that

although RODB Nadi had not participated in recent years the meeting was pleased that the

representative from Fiji confirmed RODB Nadi’s commitment to become involved and participate in

the regional OPMET monitoring activities as required. The meeting agreed that the RODB’s and the

Secretariat should facilitate Fiji’s integration into the OPMET monitoring process.

_ _ _ _ _ _ _ _ _ _ _ _ _ _

10 ROBEX WG/12


Agenda Item 4: OPMET exchange:

a) IROG Back-up procedures and tests

b) RODB monitoring and quality control procedures

c) Exchange of OPMET in a digital format

d) Other ROBEX issues

IROG Back-up procedures and tests

4.1 The meeting reviewed results presented by Thailand on the ninth real-time backup

test between IROG Singapore and IROG Bangkok conducted on 7 February 2014 (WP/12 refers).

4.2 The meeting was pleased to note the results, which indicated that RODB Bangkok

successfully received 477 out of 497 expected METAR bulletins and successfully transmitted 585 out

of 605 expected METAR and TAF bulletins with an average transit time of 1 minute.

4.3 The meeting did note that a number of Jakarta METAR bulletins were missing during

the test and Indonesia confirmed that local communication issues of a technical nature, at the time of

the test, were likely to have contributed to this result rather than some problem with the IROG back-

up arrangements.

Exchange of OPMET in a digital format

4.4 The meeting was pleased to note progress reported by Singapore in the

implementation of extensible markup language (XML) -based OPMET using the AvXML Version 1

developed by the WMO Task Team on Aviation XML (TT-AvXML) and the ICAO Meteorological

Aeronautical Requirements and Information Exchange Project Team (MARIE-PT), which included

XML validation, message switching, the setup of an air traffic services message handling system

(AMHS) interface and the planned and/or on-going activities up until October 2014 (IP/3 refers).

4.5 The meeting was also pleased to note the plans for the support of the ICAO logical

data model, known as the ICAO Meteorological Information Exchange Model (IWXXM), and the

reception and distribution of meteorological products in IWXXM format in Australia. The meeting

noted that Australia would develop the IWXXM data model to meet Australia’s requirements such as

how to handle Australian-specific products and Australia’s registered differences to ICAO Annex 3

(IP/4 refers).

4.6 In view of the discussion above, the meeting agreed that in order to facilitate the

implementation of digital exchange in the APAC Region, the Secretariat should coordinate with

States to present a comprehensive report of the activities, plans and identified implementation issues

with respect to the exchange of OPMET in a digital form to the next meeting of the MET SG for

further consideration (Agreed action 12/2 refers).

Other ROBEX issues

4.7 The meeting reviewed a proposal presented by Thailand to improve the reliability,

efficiency and accessibility of OPMET distributed by IROGs in the APAC Region by taking

advantage of RODB Brisbane’s direct connection to the Africa and Indian Ocean (AFI) Region and

could be utilized for APAC-AFI inter-regional exchange, which was currently provided by RODB

Bangkok (WP/4 refers).

4.8 The meeting appreciated the proposal by Thailand and agreed that the scheme

presented in the working paper (WP/4) should be used by the group as the basis for the review of the

structure of the ROBEX scheme that was included in the work programme of the ROBEX WG.

ROBEX WG/12 11


4.9 In relation to the ROBEX scheme, the meeting recalled that, originally, a set of test

data was used in the APAC Region to verify and validate the exchange of OPMET. The meeting

indicated the desire to repeat this activity to ensure the consistency of reporting by RODBs (Agreed

action 12/3 refers).

_ _ _ _ _ _ _ _ _ _ _ _ _

12 ROBEX WG/12


Agenda Item 5: Guidance material:

a) ROBEX Handbook

b) APAC ICD

c) OPMET related FASID tables

ROBEX Handbook

5.1 The meeting reviewed the latest updates applied to the ROBEX Handbook in

November 2013 and progress towards further updates proposed by the ROBEX Working Group and

the Meteorology Sub-Group (WP/6 refers).

5.2 The meeting recalled that a number of suggested updates needed to be progressed

before inclusion in the ROBEX Handbook, which included updates to the definitions and/or guidance

for:

performance indices for OPMET monitoring;

IROG exchange;

TAF exchange (with respect to the filing time for TAF in accordance with

Amendment 76 to Annex 3, which requires that TAF shall be issued not earlier

than 1 hour prior to the beginning of its validity period); and

digital exchange of meteorological information.

5.3 The meeting also reviewed proposed updates to the ROBEX Handbook Table A,

Table B and Table C, presented by Thailand, that would realign the ROBEX Handbook with current

requirements for OPMET at a number of locations in Viet Nam (WP/14 refers).

5.4 Thailand also apprised the meeting on the methods used to determine compliance,

availability and regularity when conducting OPMET monitoring in accordance with the instructions

provided in the ROBEX Handbook (flimsy 1 refers). The meeting noted a number of potential issues

associated with the calculation and application of performance indices for OPMET that should be

addressed, including:

assumption that all METAR are issued half-hourly rather than hourly;

performance indices may not necessarily monitor the timeliness of OPMET; and

confirmation on whether or not the RODBs apply the performance indices in a

consistent manner.

5.5 In view of the discussions above, the meeting agreed that an ad-hoc group comprising

RODB experts should be tasked to progress the required ROBEX Handbook updates (Agreed action

12/4 refers).

APAC ICD

5.6 The meeting reviewed information relating to updates required to the APAC Interface

Control Document (ICD) that describes OPMET exchange in support of the ROBEX scheme. Noting

that Singapore had provided the Regional Office with updates to Appendix D of the ICD in August

2013, and that the information was yet to be published in the ICD, the meeting agreed that RODBs

ROBEX WG/12 13


should provide the Regional Office with any outstanding updates to their respective appendices in the

document in time for the next update of the ICD to be published soon after 1 May 2014 (WP/7 and

Agreed action 12/5 refer).

OPMET related FASID tables

5.7 The meeting reviewed details of recent amendments to APAC FASID Tables MET

that had been approved or processed since the last meeting (WP/8 refers).

5.8 In reviewing the updates to FASID Tables MET 1A and MET 2A, the meeting noted

with concern that the explanation of the tables referred to TAF with validity 9 hours and 18 hours,

which was not a requirement in accordance with ICAO Annex 3 or regional agreement in the APAC

air navigation plan. The meeting agreed that the Secretariat should convey this concern to ICAO and

determine whether an appropriate amendment proposal would be required to remove references to 9

hours and 18 hours validity TAF in the FASID Tables MET 1A and MET 2A (Agreed action 12/6

refers).

5.9 In reviewing the updates to FASID Table MET 6, the meeting noted possible

inconsistencies in the requirements specified for Malaysia (in WP/8) and agreed the Secretariat should

check the latest version of FASID Table MET 6 to ensure it reflects current requirements (Agreed

action 12/7 refers).

5.10 Indonesia advised the meeting that, while the recent amendments to FASID Tables

MET 1A and MET 2A realigned the requirements with respect to locations in Indonesia, the tables in

the ROBEX Handbook had also become misaligned and would require corresponding updates

(Agreed action 12/8 refers).

5.11 The meeting noted updates proposed by Australia to FASID Tables MET 1B, MET

3A and MET 3B concerning changes to meteorological watch offices (MWOs) Cairns and Townville

(WP/15 refers) and agreed that the Secretariat should coordinate with Australia to produce a proposal

to amend the FASID accordingly (Agreed action 12/9 refers).

5.12 In view of the discussions above, the meeting agreed that States should review their

respective requirements in FASID Tables MET and inform the Regional Office on areas that require

updates.

_ _ _ _ _ _ _ _ _ _ _ _ _

14 ROBEX WG/12


Agenda Item 6: Future work programme and review of terms of reference

6.1 The meeting reviewed the document containing the Terms of Reference and the Work

Programme for the ROBEX Working Group in view of providing updates where necessary (WP/9

refers).

6.2 A break-out group comprising representatives from RODBs reviewed the work

programme in detail and the meeting agreed to the updates provided to tasks and target dates

formulated by the group and included in Attachment 7 to this Report.


Next Meeting

7.1 Dates for the next meeting (ROBEX WG/13) were tentatively agreed in the week

commencing 16 March 2015, back-to-back with MET/H TF/5, including the conjoint session with

MET/H TF/5.

_ _ _ _ _ _ _ _ _ _ _ _ _

ROBEX WG/12 15


REPORT ON CONJOINT SESSION OF ROBEX WG/12 AND MET/H TF/4, 19 March 2014

Agenda Item 1: VAAC back-up tests

1.1 The meeting reviewed back-up test procedures for Volcanic Ash Advisory Centres

(VAACs) Wellington and Darwin presented by New Zealand and was pleased to note that this

effectively completed Activity 4.1 of the ROBEX WG work plan (WP/C2 refers).

1.2 The meeting made some minor editorial adjustments to the VAAC back-up test

procedures presented by New Zealand, as shown in Attachment C1 to the Report, and requested the

Secretariat to include the VAAC back-up test procedures between Wellington and Darwin in the next

amendment or edition of the APAC Regional SIGMET Guide (Agreed action 12/10 and 4/1 refers).

1.3 Japan informed the meeting of the Scheme of Cooperation (SoC) endorsed by

VAACs Tokyo and Darwin, which came into force on 1 March 2014 (IP/C1 refers). The outline of the

scheme of cooperation between VAACs Tokyo and Darwin is provided in Attachment C2 to the

Report.

1.4 With the presentation of the information above, the meeting was pleased to note the

significant progress in the follow-up to agreed action 11/7 (from ROBEX WG/11) represented by the

SoC endorsed by VAACs Tokyo and Darwin and the VAAC back-up test procedures developed for

VAACs Wellington and Darwin.

_ _ _ _ _ _ _ _ _ _ _ _ _ _

16 ROBEX WG/12



a) SIGMET tests

b) Regional SIGMET monitoring and coordination

c) Review SIGMET Guide

d) Advisory information

e) Other SIGMET/advisory related business

SIGMET tests / Regional SIGMET monitoring and coordination

2.1 The meeting reviewed results presented by the SIGMET test focal point, Japan, on

the APAC SIGMET tests conducted on 12 and 19 November 2013 to test the issuance and reception

of SIGMET messages for tropical cyclones (WC SIGMET) and volcanic ash (WV SIGMET) in

accordance with the schedule agreed at ROBEX WG/11 for the 2013 SIGMET tests (WP/C3 refers).

The WC and WV SIGMET test results tables (presented by Japan) are provided in Attachment C3 to

this Report.

2.2 The meeting noted that the overall results from both the WC and WV SIGMET tests

in 2013 were almost the same as those in 2012. However, the meeting also noted that in some cases in

2013, identical test bulletins were received multiple times from certain meteorological watch offices

(MWOs), which the meeting observed could cause confusion among participating countries and

obfuscate the results of the SIGMET tests.

2.3 With respect to the WC and WV SIGMET test results table, the meeting suggested

some clarification should be provided to States/MWOs where results in the ‘priority’ column of the

table showed that test SIGMET were received with two priority indicators (FF/GG).

2.4 In reviewing the test results where no test WC SIGMET were received, the meeting

noted that in some cases, as informed by Australia and New Zealand, rather than being indicative of

errors in the SIGMET system, the nil results were due to the respective MWO’s inability to issue WC

SIGMET messages (either test or real) for certain flight information regions (FIRs) because the

MWO’s systems (for SIGMET issuance) were deliberately not configured to do so in areas where

tropical cyclones do not occur. Australia advised that this was the case for MWO YDRM, which was

not configured to issue WC SIGMET for the portion of FIR YMMM that falls within its area of

responsibility. Likewise, New Zealand advised that MWO NZKL was not configured to issue WC

SIGMET for FIR NZZC.

2.5 Additionally, two States in the meeting reported that specific guidance was not

available to MWOs on how to proceed in a situation when the test advisory message for tropical

cyclone/volcanic ash (which is required to trigger the issuance of test WC/WV SIGMET) is not

received. The meeting recognized that this (absence of specific guidance) may contribute to

unexpected recording of nil test WC/WV SIGMET from the MWOs concerned.

2.6 In view of the discussions in 2.2 to 2.5 above, the meeting suggested the SIGMET

test procedures should be reviewed and updated, where appropriate, particularly to eliminate any

unintentional recording of nil test SIGMET in future tests that may result when an MWO deliberately

does not issue WC SIGMET (and therefore does not issue test WC SIGMET) or when an MWO does

not receive a test advisory message for tropical cyclone or volcanic ash. To this end, the meeting

requested the Secretariat to: (a) update the information in the SIGMET Guide (currently in Appendix

H), containing the list of WMO headings for SIGMET bulletins used by APAC MWOs (which would

be used as a basis for compilation SIGMET test results), to reflect the limitations in WC SIGMET

issuance from certain MWOs as notified by States; and (b) include specific guidance in the SIGMET

test procedures, in the SIGMET Guide (currently in Appendix J), for the issuance of test WC/WV

ROBEX WG/12 17


SIGMET when a test advisory message for tropical cyclone/volcanic ash is not received (Agreed

action 12/11 and 4/2 refers).

2.7 The meeting noted that the overall participation in WC/WV SIGMET tests hadn’t

improved significantly over the period of 7 years of testing, but was also encouraged by the

participation in the meeting of some States, which presented the opportunity to resolve some long-

standing issues with respect to repetitive SIGMET test errors.

2.8 The meeting reviewed results and detailed analysis presented by the SIGMET test

focal point Singapore on the APAC SIGMET test (SIGMET Test 9) conducted on 26 November 2013

to test the issuance and reception of SIGMET messages for phenomena other than tropical cyclones

and volcanic ash (WS SIGMET), in accordance with the schedule agreed at ROBEX WG/11 for the

2013 SIGMET tests (WP/C4 refers). The WS SIGMET test results tables (presented by Singapore) are

provided in Attachment C4 to this Report.

2.9 The meeting noted that overall participation by MWOs and States in WS SIGMET

Test 9 increased by 3% and 9% to 78% and 66%, respectively, compared to the previous year’s test

results – which was attributable, mostly, to participation in 2013 from Bangladesh and Nepal.

2.10 Additionally, the average reception rate by the five RODBs in WS SIGMET Test 9

also increased (by 7%) on the 2012 result. The meeting was pleased to note that three European

Regional OPMET Centres (EUR ROCs) recorded a high rate of reception (91%).

2.11 The meeting noted that the WS SIGMET Test 9 results indicated nil test SIGMET

were received at RODB Bangkok and RODB Nadi from the Indonesian MWO at Makassar/Sultan

Hasanuddin (WAAA).

2.12 In view of the discussions above in 2.1 to 2.11 with respect to the WC/WV SIGMET

tests and WS SIGMET test, including the analyses of SIGMET test results presented by Japan and

Singapore, the meeting agreed that the annual State letter notifying details of the 2013 SIGMET test

results should urge States to resolve the errors identified in the tests and to report back to ICAO on

any issues that cannot be resolved so as to enable the Secretariat to provide, or coordinate the

provision of, targeted assistance to States to address the SIGMET test errors where necessary (Agreed

action 12/12 and 4/3 refers).

2.13 The meeting appreciated the update provided by Australia with respect to addressing

the errors in test SIGMET messages issued from Australia, as reported in the previous year’s (2012)

SIGMET test results (IP/C3 refers), and was pleased to note that Australia had implemented the

correct SIGMET message terminator (=) and correct length of SIGMET sequence number (3

characters) to resolve the formatting errors reported in previous SIGMET tests.

2.14 Additionally, Australia had requested ICAO to update the regional air navigation plan

(specifically, FASID Table MET 1B) to remove the requirement for MWO services at Cairns

(YBCS), in line with current requirements, which would resolve the issue of nil test SIGMET

messages from YBCS (Agreed action 12/13 and 4/4 refers). Furthermore, Australia advised that it

had implemented the use of the correct SIGMET sequence number (Z99) for test SIGMET, though

the current distribution of SIGMET messages with Z99 sequence number required manual processing,

which resulted in delays in distribution, and that full automation for distribution of SIGMET messages

with Z99 sequence number was planned at a date to be determined.

18 ROBEX WG/12


Review SIGMET Guide

2.15 The meeting reviewed the last amendments to the Regional SIGMET Guide

published in November 2013 and reviewed the draft, future updates to the SIGMET Guide provided

by the Meteorological Warnings Study Group (METWSG) for consideration and possible adoption as

the basis for an updated, Fifth Edition of the Asia/Pacific Regional SIGMET Guide (WP/C1 refers).

2.16 The meeting recalled that the METWSG had tasked an ad-hoc group to

comprehensively review all the Regional SIGMET Guides in existence in ICAO Regions, resolve the

regional inconsistencies with respect to the generic content of the guides and develop a

comprehensive, generic document, aligned with Amendment 76 to Annex 3, for use by Regions as a

Regional SIGMET Guide template (METWSG Actions Agreed 4/3 and 5/4 refer). The template

developed by the METWSG ad-hoc group became available in October 2013 (Inter-Office

Memorandum Ref: AN 10/22 refers). The template was reviewed and adapted in draft form (for the

Asia/Pacific Region) by the Secretariat and is provided in Attachment C5 to the Report.

2.17 The meeting appreciated additional comments on the draft Asia/Pacific Regional

SIGMET Guide (5th Edition) provided by Hong Kong, China (WP/C5 refers). A summary of the

comments from Hong Kong, China is provided in Attachment C6 to the Report.

2.18 Additional suggested changes to the draft Asia/Pacific Regional SIGMET Guide (5th

Edition) were also provided to the meeting in a table prepared by Australia. The table of some of the

suggested changes is provided in Attachment C7 to the Report.

2.19 The meeting noted that both Australia and Hong Kong-China, as members of the

METWSG, had already contributed to the development of the Regional SIGMET Guide template that

was proposed as the basis for the draft Asia/Pacific Regional SIGMET Guide (5th Edition) and that

the additional comments and changes were submitted based on the adaptation of the template for

regional use.

2.20 Noting that some of the additional comments and changes suggested in the meeting

will be of relevance to the Regional SIGMET Guide template, the meeting agreed that an ad-hoc

group comprising Australia (Rapporteur), Hong Kong-China, Japan, New Zealand and ICAO be

formed to reassess all the suggested changes to the Regional SIGMET Guide template provided in the

meeting a produce comprehensive revision to be forwarded to the Secretariat to liaise and coordinate

further with other ICAO Regions. Based on the work of the ad-hoc group, a draft Asia/Pacific

Regional SIGMET Guide (5th Edition) would then be presented for consideration by the MET SG

(Agreed action 12/14 and 4/5 refers).

2.21 Viet Nam raised some issues of a technical nature concerning the issuance of WC

SIGMET when a tropical cyclone occurs near or on the boundary of an MWO’s area of responsibility.

The meeting noted the issues and, as they were of a technical nature, invited Viet Nam to discuss the

issues further with the tropical cyclone advisory centre (TCAC) provider States, and other States with

MWO responsibilities, present at the meeting.

Advisory information

2.22 Australia provided the meeting with a report on activities of the VAAC Darwin,

which highlighted recent developments, challenges, advisory information provided and future planned

events (IP/C2 refers). The meeting noted with interest the volcanic activity situational awareness

products introduced by VAAC Darwin during 2013 that were provided to support aviation users in the

collaborative decision making process.

ROBEX WG/12 19


2.23 Japan apprised the meeting of recent global discussions on the regional-based

approach for the provision of information relating to hazardous meteorological conditions, which took

into account the use of numerical weather prediction tools. The METWSG had completed a high-level

strategic statement relating to the short- and long-term vision for the provision of information relating

to hazardous meteorological conditions for review and possible endorsement at the ICAO

Meteorology Divisional Meeting in July 2014 (IP/C5 refers).

Other SIGMET/advisory related business

2.24 Australia discussed a system under development that would produce two versions of

the same SIGMET message: one for international users that would comply with Amendment 76 to

ICAO Annex 3 provisions for the use of geographical coordinates for the location of phenomenon and

one for domestic users that may include the use of PCA1 locations, as required by those particular

users (WP/C6 refers). The meeting agreed that the intent of Australia’s proposal, i.e., to meet the

ICAO requirements with respect to the location of phenomenon in SIGMET, would be seen as a

positive development, but also cautioned Australia on the potential for confusion if international users

unintentionally received the non-compliant, domestic version of SIGMET from such a system.

2.25 The meeting noted with interest the information provided by the ROK on forecast

guidance for turbulence used in support of SIGMET issuance by the Korea Meteorological

Administration (KMA) (IP/C4 refers) and invited the ROK to provide a detailed report on the

progress and performance of the system at a future meeting and to provide any useful information on

the algorithms used that may help other States in forecasting turbulence.

2.25 Australia raised some concerns with the proposed draft Amendment 77 to ICAO

Annex 3 insofar as the revised provisions for SIGMET were concerned (IP/C7 refers). The meeting

noted that States may wish to bring the issues raised to the attention of the relevant ICAO groups and

meetings.

_ _ _ _ _ _ _ _ _ _ _ _ _

1 Planning Chart Australia

1 - 1

The Twelfth Meeting of the Asia/Pacific ROBEX Working Group (ROBEX WG/12)

ICAO Regional Sub-Office, Beijing, China

17 – 19 March 2014

LIST OF PARTICIPANTS

STATE/ORGANIZATION/N

AME

DESIGNATION/ADDRESS TEL/FAX/E-MAIL

AUSTRALIA (2)

Ms. Susan E. O’Rourke Section Head, Meteorological Authority

Strategy, Parliamentary, International &

Communications Branch

GPO Box 1289

Melbourne VIC 3001

AUSTRALIA

Tel: +61 (3) 9669 4662

MB: +61 418 234 138

E-mail:

[email protected]

[email protected]

Mr. Tim A. Hailes

National Manager, Regional Aviation Weather

Service

Australian Bureau of Meteorology

Weather & Ocean Services Branch

GPO Box 1289

Melbourne VIC 3001

AUSTRALIA

Tel: +61 (3) 9669 4273

MB: 61427 840 175

E-mail: [email protected]

[email protected]

CAMBODIA (4)

Mr. Sineath Khuon Deputy Director of Aeronautical Services

Department

State Secretariat of Civil Aviation (SSCA)

#62, Preah Norodom Blvd.

Phnom Penh

CAMBODIA

Tel: +855 (23) 427 141

MB: +855 16 933 552

Fax: +855 (23) 211 019


Mr. Vandy Heang Chief of Navigation – In charge of Meteorology



Phnom Penh

CAMBODIA

Tel: +855 (23) 427 041

MB:: +855 1566 2561

Fax: +855 (23) 211 019


Mr. Thol Chvea Official of Met-Office (ANS)



Phnom Penh

CAMBODIA

Tel: +855 (23) 224 259

MB:: +855 12 586 738

Fax: +855 (23) 224 258


Mr. Vuthy Khy Official of Met-Office (ANS)



Phnom Penh

CAMBODIA

Tel: +855 (23) 232 4259

MB:: +855 7777 1577

Fax: +855 (23) 2322 4258


CHINA (6)

Attachment 1 to the Report

mailto:[email protected]








1 - 2


AME


Mr. Guo Xiang Engineer

Aviation Meteorological Center

Air Traffic Management Bureau

Civil Aviation Administration of China

P.O. Box 2272

Shilihe, Chaoyang District

Beijing 100122

PEOPLE’S REPUBLIC OF CHINA

Tel: +86 (10) 6749 9866

MB: +86 138 100 42 711

Fax: +86 (10) 67332446


Miss Cao Shan Engineer




P.O. Box 2272


Beijing 100122


Tel: +86 (10) 6749 9872

MB: +86 152 108 3 0357

Fax: +86 (10) 6733 2446


Mr. Han Qingyuan Engineer




P.O. Box 2272


Beijing 100122


Tel: +86 (10) 6749 9827

MB: +86 136 5105 2683

Fax: +86 (10) 8792 2094


Mr. Shi Bujiu Director MET Division

Meteorological Center, North China


Beijing 100621


Tel: +86 (10) 6459 2335

MB: +86 136 5423 1477

Fax: +86 (10) 6733 2446

E-mail: shibujiu@263,net

Mr. Zhang Qiang Engineer

Meteorological Center North China


Beijing 100621


Tel: +86 (10) 6459 2550

MB: +86 130 518 05695

Fax: +86 (10) 6459 2550


Mr. Feng Xiangyang Engineer

Meteorological Center, North China


Beijing 100621


Tel: +86 (10) 6459 6876

MB: +86 1333 101 7598

Fax: +86 (10) 6459 6597


FIJI (1)

Mr. William L. Reece Station Manager (CNS/ATM/Airports)

Airports Fiji Limited

P.O. Box 9210

Nadi Airport

FIJI ISLANDS

Tel: +679 673 1198

Fax: +679 673 1123


INDIA (1)








1 - 3


AME


Ms. Neetha K. Gopal

Scientist “D”

Central Aviation Meteorological Division

India Meteorological Department

c/o Director General of Meteorology

Mausam Bhawan Lodi Road

New Delhi 110003

INDIA

Tel: +91 (11) 4382 4208

MB: +91 901 3975 5999

Fax: +91 (11) 2461 5371


INDONESIA (3)

Mr. Indra Gunawan Chief of Airspace Management

Directorate General of Civil Aviation

Ministry of Transportation

Jl. Medan Merdeka Barat No. 8

Karya Building 5th

Floor

Jakarta 10110

INDONESIA

Tel:

Fax:

E-mail:

Mr. Mustari Heru Jatmika Chief of Aeronautical Meteorology Division

Indonesian Meteorological, Climatology

and Geophysical Agency

Jalan Angakasa I

Kemayoran

Jakarta Pusat

INDONESIA

Tel: +62 (21) 424 6321

MB: +62 853 99057442

Fax: +62 (21) 654 6315


Mr. Zulkarnian Senior Forecaster of Aeronautical Meteorology

Indonesian Meteorological, Climatology

and Geophysical Agency

Jalan Angakasa I

Kemayoran

Jakarta Pusat

INDONESIA

Tel: +62 (21) 424 6321

MB: +62 813 8539 1410

Fax: +62 (21) 654 6315


[email protected]

JAPAN (2)

Mr. Yuichi Yamakoshi Senior Scientific Officer

Aeronautical Meteorology Division

Administration Department

Japan Meteorological Agency

1-3-4 Otemachi, Chiyoda-ku

Tokyo 1008122

JAPAN

Tel: +81 (3) 3212 8341 Ext. 3351

Fax: +81 (3) 3284 0180


Mr. Norihisa Washitake Scientific Officer

Aeronautical Meteorology Division

Administration Department



Tokyo 1008122

JAPAN

Tel: +81 (3) 3212 8341 Ext. 2285

Fax: +81 (3) 3212 8968


[email protected]

PHILIPPINES (1)








1 - 4


AME


Ms. Hannagrace F. Cristi Senior Weather Specialist

Aeronautical Meteorology Forecaster

Aeronautical Meteorology Services Section

Weather Division

PAGASA-DOST

Room 415, 4th

Floor

International Passenger Terminal Building

NAIA I, Parañaque City, Metro Manila

PHILIPPINES

Tel: +63 (2) 8522927, 879 5269

MB: +63 917 456 9882

Fax: +63 (2) 832 3023


NEW ZEALAND (1)

Mr. Keith W. Mackersy Senior Meteorological Specialist

Civil Aviation Authority of New Zealand

P.O. Box 3555

Wellington 6140

NEW ZEALAND

Tel: +64 (4) 904 0543

MB: +64 216 55321

Fax: +64 (4) 569 2024


REPUBLIC OF KOREA (3)

Ms. Park Ji eun Assistant Director / Forecast Division

Korea Meteorological Administration

272 Gonghang-Ro

Joonku, Incheon City

REPUBLIC OF KOREA

Tel: +82 (32) 740 2820

MB: +82 (10) 8554 4337

Fax: +82 (32) 740 2817


Ms. Kim Youn Jeong Assistant Director/ Information Technology

Support Division


272 Gonghang-Ro


REPUBLIC OF KOREA

Tel: +82 (32) 740 2850

MB: +82 (10) 6374 5922

Fax: +82 (32) 740 2847

E-mail: [email protected] [email protected]

Ms. Lee Jin Kyoung Assistant Director/ Planning & Operation

Division


272 Gonghang-Ro


REPUBLIC OF KOREA

Tel: +82 (32) 740 2802

MB: +82 (10) 2702 7741

Fax: +82 (32) 740 2807

E-mail: [email protected] [email protected]

SINGAPORE (1)

Mr. Goh Wee Poh Executive Meteorological Engineer

Meteorological Service Singapore

P.O. Box 8

Singapore Changi Airport

SINGAPORE 918141

Tel: +65 6542 5059

MB: +65 9879 0461

Fax: +65 6542 5026


THAILAND (6)

Mr. Somchai Yimsricharoenkit Director of Aeronautical Meteorology

Forecast Division

Bureau of Aeronautical Meteorology

6th

Floor, ATC Complex

Suvarnabhumi International Airport

Rachatheva, Bang Phli

Samut Prakarn 10540

THAILAND

Tel: +66 (2) 134 0011 Ext. 214

Fax: +66 (2) 134 0010











1 - 5


AME


Ms. Sujin Promduang Acting Director, Aeronautical Information and

Flight Data Manager Centre

Aeronautical Radio of Thailand Ltd.

102 Ngamduplee

Tungmahamek, Satorn

Bangkok 10120

THAILAND

Tel: +66 (2) 285 9083

MB: +66 81915 0560

Fax: +66 (2) 287 8645


Mr. Thavit Nowvaratkoonchai Engineering Manager


102 Ngamduplee

Tungmahamek, Satorn

Bangkok 10120

THAILAND

Tel: +66 (2) 285 9579

Fax: +66 (2) 287 8645


Mr. Worapong Jirojkul Senior Systems Engineer


102 Ngamduplee

Tungmahamek

Sathorn, Bangkok 10120

THAILAND

Tel: +66 (2) 287 8075

Fax: +66 (2) 287 8645


Sub. Lt. Prinya Viyasilpa Engineering Manager


102 Ngamduplee, Sathorn

Bangkok 10120

THAILAND

Tel: +66 (2) 287 8037

Fax: +66 (2) 285 9253


Ms. Narissara Na Rangsri Aeronautical Communication and ATS Manager


102 Ngamduplee

Tungmahamek

Sathorn, Bangkok 10120

THAILAND

Tel: +66 (2) 285 9084

Fax: +66 (2) 287 8645


VIET NAM (2)

Mr. Ha Bien Van Vice Chief of MWO

Gia Lam Meteorological Watch Office

Viet Nam Air Traffic Management (VATM)

Corporation

5/200 Nguyen Son Street

Bode Ward, Longbien District

Hanoi

SOCIALIST REPUBLIC OF VIET NAM

Tel: +84 (4) 3872 1698

MB: +84 125 696 368

Fax: +84 (4) 3873 0060


Ms. Nguyen Oanh Lan Official of Gia Lam Meteorological Watch

Office (MWO Gialam)

5/200 Nguyen Son Street

Longbien District

Hanoi

SOCIALIST REPUBLIC OF VIET NAM

Tel: +84 (4) 3872 1698

MB: +84 939 47588

Fax: +84 (4) 3873 0060


ICAO (1)








1 - 6


AME


Mr. Peter C. Dunda Regional Officer MET

International Civil Aviation Organization

Asia and Pacific Office

252/1, Vibhavadi Rangsit Road

Ladyao, Chatuchak

Bangkok 10900

THAILAND

Tel: +66 (2) 537 8189 Ext. 153 Ext. 153

Fax: +66 (2) 537 8199


_ _ _ _ _ _ _ _ _ _ _ _ _



2 - 1


THE TWELFTH MEETING OF ASIA/PACIFIC ROBEX

WORKING GROUP (ROBEX WG/12)

ICAO Regional Sub-Office, Beijing, China

17 – 19 March 2014

LIST OF WORKING AND INFORMATION PAPERS

WP/IP

No.

Agenda Item Subject Presented by

WP/1 - Provisional Agenda Secretariat

WP/2 2 (a) Review of ROBEX WG/11 Agreed Action Secretariat

WP/3 2 (b) Review of Follow-up to Relevant APANPIRG/24

Conclusions/Decision

Secretariat

WP/4 4 (d) Review of IROG in ASIA/PAC Region Thailand

WP/5 3 (a) Review of OPMET Monitoring Report Singapore

WP/6 5 (a) Review Updates to the ROBEX Handbook Secretariat

WP/7 5 (b) Review Updates to the ASIA/PAC ICD Secretariat

WP/8 5 (c) Updates to OPMET Related FASID Tables Secretariat

WP/9 6 Review the Future Work Programme of the ROBEX

Working Group

Secretariat

WP/10 3 (a) Availability of OPMET from ASIA/PAC IATA

WP/11 3 (a, b) RODB Tokyo Performance Indices for METAR and TAF Japan

WP/12 4 (a) ASIA/PAC Inter-Regional OPMET Gateway Backup

Exercise between RODB Bangkok and RODB Singapore

Thailand

WP/13 3 (a, b) Performance Indices of ASIA/PAC RODBS Thailand

WP/14 5 (a) Updates to the ROBEX Handbook Thailand

WP/15 5 (c) Changes to FASID Tables Australia

2 - 2

WP/IP

No.

Agenda Item Subject Presented by

LIST OF INFORMATION PAPERS

IP/1 - Meeting Bulletin Secretariat

IP/2 3 (a) Plan for Improvement of the Performance (PIs) Republic of

Korea

IP/3 4 (c) Progress Report of Digital Exchange of OPMET Using XML Singapore

IP/4 4 (c) Status and Plans for IWXXM in Australia Australia

CONJOINT PAPERS

WP/C1 2 (c) Review of the Asia/Pacific Regional SIGMET Guide Secretariat

WP/C2 1 Wellington/Darwin VAAC Backup Test Procedures New Zealand

WP/C3 2 (a) Progress with SIGMET Tests – WC and WV Japan

WP/C4 2 (a) Review of WS SIGMET Test 9 Singapore

WP/C5 2 (c) Review of the Asia/Pacific Regional SIGMET Guide Hong Kong,

China

WP/C6 2 (e) Inclusion of Location within SIGMETS Australia

IP/C1 1 Mutual Backup Operation between VAACS Tokyo and

Darwin

Japan

IP/C2 2 (a) VAAC Darwin Report Australia

IP/C3 2 (a) Australia’s Review of Actions from 2012 SIGMET Tests Australia

IP/C4 2 (e) Development and Use of Korea Turbulence Guidance Republic of

Korea

IP/C5 2 (d) Recent Progress on Regional Hazardous Weather Information Japan

IP/C6 2 (e) Proposed Changes to SIGMET Format Australia

_ _ _ _ _ _ _ _ _ _ _ _ _ _

ROBEX WG/12


3 - 1

FOLLOW-UP OF ROBEX WG/12

AGREED ACTION

Status on 19 March 2014

(√ = completed)

No. Title/description Follow-up action (target/completion dates in brackets)

12/1

Improvement of OPMET availability on SADIS and WIFS

Identify and address issues where OPMET availability on SADIS and

WIFS did not meet the requirements of IATA.

RODBs in coordination with the Secretariat to investigate the results of

IATA OPMET monitoring (on SADIS and WIFS) and address issues

such as incorrect distribution lists or misalignment of requirements in the

FASID Table MET 2A. Secretariat to coordinate with States to address

the issues related to specific locations (June 2014).

12/2

Facilitating the implementation of digital exchange in the APAC

Region

Report on the activities, plans and identified implementation issues with

respect to the exchange of OPMET in a digital form.

Secretariat to coordinate with States a comprehensive report of the

activities, plans and identified implementation issues with respect to the

exchange of OPMET in a digital form for the next meeting of the MET

SG (June 2014).

12/3

Verification and validation of the exchange of OPMET

Verify and validate the exchange of OPMET in the APAC Region using

a set of test data.

RODBs to construct a test dataset, perform calculations, compare results

and to standardize (report to next meeting).

12/4 ROBEX Handbook updates

Develop and publish updates to the ROBEX Handbook.

Ad-hoc group comprising RODB experts to progress the required

ROBEX Handbook updates as discussed under agenda item 5 of the

Report; Secretariat to publish the updates (June 2014).

12/5 ICD updates

Develop and publish updates to the ICD.

RODBs to provide updates for their respective appendices in the ICD;

Secretariat to publish the updates (June 2014).

12/6

Requirement for aerodrome forecasts in TAF code in FASID Tables

MET 1A and MET 2A

Verify the inclusion of TAF with validity 9 hours and 18 hours in the

explanation of the FASID Tables MET 1A and MET 2A.

Secretariat to determine whether an appropriate amendment proposal

would be required to remove references to 9 hours and 18 hours validity

TAF in the FASID Tables MET 1A and MET 2A (June 2014).

ROBEX WG/12


3 - 2


12/7

Review of FASID Table MET 6

Review FASID Table MET 6 for possible inconsistencies in the

requirements specified for Malaysia.

Secretariat to ensure the latest version of FASID Table MET 6 reflects

current requirements (June 2014).

12/8

Updates to ROBEX Handbook

Update the ROBEX Handbook to realign with amendments to FASID

Tables MET 1A and MET 2A with respect to locations in Indonesia.

Secretariat to include updates to realign the ROBEX Handbook with

amendments to FASID Tables MET 1A and MET 2A with respect to

locations in Indonesia are included in the ROBEX Handbook updates

(Agreed Action 12/4 refers) (June 2014).

12/9

Amendment to FASID Tables MET 1B, MET 3A and MET 3B

Amendment to FASID Tables MET 1B, MET 3A and MET 3B

concerning MWOs Cairns and Townville.

Secretariat in coordination with Australia to develop and process an

amendment proposal to FASID Tables MET 1B, MET 3A and MET 3B

concerning MWOs Cairns and Townville (June 2014).

12/10

(MET/H TF 4/1)

SIGMET Guide/VAAC back-up test procedures

VAAC back-up test procedures between Wellington and Darwin to be

included in the next amendment or edition of the APAC Regional

SIGMET Guide

Secretariat to include VAAC back-up test procedures in SIGMET Guide

(Target date TBD in 2014, in coordination with ad-hoc group’s revision

of SIGMET Guide for presentation to MET SG/18)

12/11

(MET/H

TF 4/2)

SIGMET Guide/SIGMET test procedures

a) List of WMO headings for SIGMET bulletins used by APAC MWOs

(to be used for compilation of SIGMET test results) to be updated to

reflect the limitations in WC SIGMET issuance from certain MWOs as

notified by States in the next amendment or edition of the APAC

Regional SIGMET Guide; and

b) Specific guidance for the issuance of test WC/WV SIGMET when a

test advisory message for tropical cyclone/volcanic ash is not received to

be included in the SIGMET test procedures in the next amendment or

edition of the APAC Regional SIGMET Guide.

Secretariat to include (a) updated information on WC SIGMET issuance

and (b) specific guidance for non-receipt of test advisory messages in

SIGMET tests in SIGMET Guide

(Target date TBD in 2014, in coordination with ad-hoc group’s revision

of SIGMET Guide for presentation to MET SG/18)

ROBEX WG/12


3 - 3


12/12

(MET/H

TF 4/3)

SIGMET test results

a) ICAO State letter urging States to resolve the errors identified in the

2013 SIGMET tests (reported by Japan and Singapore and provided in

Attachments C3 and C4 to the Report); and

b) States to advise ICAO on any issues that cannot be resolved or require

further coordination/assistance to address the SIGMET test errors.

(a) Secretariat to issue State letter (April 2014)

(b) States respond if necessary (June 2014)

12/13

(MET/H TF 4/4)

Proposal for amendment of FASID Table MET 1B – Cairns (YBCS)

Update the regional air navigation plan, FASID Table MET 1B, to

remove the requirement for MWO services at Cairns (YBCS) – in line

with current requirements.

Secretariat (in coordination with Australia) to prepare and process the

PfA (June 2014)

12/14

(MET/H TF 4/5)

Draft Asia/Pacific Regional SIGMET Guide (5th Edition)

Comprehensive revision of the draft Asia/Pacific Regional SIGMET

Guide (5th Edition) based on the suggested changes in Attachments C5,

C6 and C7 to the Report.

Ad-hoc group comprising Australia (Rapporteur), Hong Kong-China,

Japan, New Zealand and ICAO to produce the revised draft Asia/Pacific

Regional SIGMET Guide (5th Edition) and forward to the Secretariat for

inter-regional coordination then to the MET SG for further consideration

(June 2014).

12/15

(MET/H

TF 4/6)

Guidance on SIGMET for radioactive cloud

Guidance on the issuance of SIGMET for radioactive cloud for possible

inclusion in the Regional SIGMET Guide.

Ad-hoc group comprising China (Rapporteur), Hong Kong-China and

Japan to develop guidance on the issuance of SIGMET for radioactive

cloud and forward to the ad-hoc group revising the draft Regional

SIGMET Guide (5th Edition) (June 2014).

12/16

(MET/H

TF 4/7)

Guidance on the use of SIGMET for radioactive cloud

Guidance and/or training on the use of the information provided in

SIGMET for radioactive cloud.

Secretariat to raise the issue with an appropriate ICAO group or user

group (June 2014).

12/17

(MET/H TF 4/8)

Guidance on integration of aerodromes with national tsunami

warning systems

Guidance on how to integrate aerodromes into national tsunami warning

systems where such systems are in place.

Ad-hoc group comprising Japan (Rapporteur) and Indonesia to review

the tsunami survey results and develop regional guidance on the

provision of tsunami warning information directly from the relevant

tsunami warning centres to the ‘at-risk’ aerodromes (June 2014).

ROBEX WG/12


3 - 4


12/18

(MET/H

TF 4/9)

Survey results for radioactive cloud and tsunami

Information gathered by the surveys to be shared with other relevant

groups.

Secretariat to forward the information gathered by the surveys to ICAO

HQ to be shared with other relevant groups (May 2014).

12/19

(MET/H

TF 4/10)

Notification of implementation of the new standardized international

volcano database for the preparation of volcanic ash advisories

Notification of the implementation of the new database for volcanic ash

advisory (VAA) messages by VAAC Tokyo.

Secretariat to liaise with ICAO HQ to determine whether there are any

requirements for notification to others such as the IAVW-related

organizations, ATCs and MWOs in the VAAC Tokyo area of

responsibility, as well as the EUR/NAT Regional Office (May 2014).

12/20

(MET/H

TF 4/11)

Impact of non-implementation of the new volcano database on

VAAC back-up arrangements

VAAC back-up procedures between Darwin and Tokyo to be reviewed

and updated if necessary to address the interim period before the new

database is implemented by VAAC Tokyo.

VAAC Tokyo, in conjunction with VAAC Darwin, to review the impact

of VAAC Tokyo not referring to the new volcano database and take

necessary actions as required (May 2014).

12/21

(MET/H

TF 4/12)

Updates to the SIGMET posters

Revision of SIGMET posters to realign the posters with the SIGMET

changes envisaged in Amendment 77 to Annex 3 in 2016.

Ad-hoc group consisting of Australia, Hong Kong-China and New

Zealand (Rapporteur) to review and update the SIGMET posters to

realign with Amendment 77 to Annex 3 in 2016.

12/22

(MET/H TF 4/13)

MWO and ACC AFTN addresses for VAA information

List of MWO and ACC locations and AFTN addresses for distribution of

VAA information from VAACs Darwin and Wellington.

Secretariat to: (a) source the lists of MWO and ACC locations for

distribution of VAA information from VAACs Darwin and Wellington;

and (b) issue a State Letter requesting updates to the MWO and ACC

location information for distribution of VAA information in the APAC

Region, including AFTN addresses (May 2014).

_ _ _ _ _ _ _ _ _ _ _ _ _ _

ROBEX WG/12


4 - 1

Order of Business

Monday 17 March 2014

0830 – 0900 Registration (for ROBEX WG/12 and MET/H TF/4)

0900 – 1030

Opening of the meeting (ROBEX WG/12) Secretariat

Agenda Item 1: Organizational matters

a) Adoption working arrangements Secretariat

b) Adoption of agenda WP/1 Chairperson

Agenda Item 2: Review of follow-up from previous

meetings

a) Action arising from ROBEX WG/11 WP/2 Secretariat

b) Relevant APANPIRG/24 Conclusions WP/3 Secretariat

1030 – 1100 Group Photo & Coffee/Tea Break

1100 – 1200

Agenda Item 3: OPMET information

a) OPMET availability WP/10 IATA

IP/2 ROK

WP/5 Singapore

1200 – 1300 Lunch Break

1300 – 1430

b) OPMET timeliness and regularity WP/11 Japan

WP/13 Thailand

c) Status reports from the RODBs

Agenda Item 4: OPMET exchange

a) IROG Back-up procedures and tests WP/12 Thailand

1430 – 1445 Coffee/Tea Break

1445 - 1600

b) RODB monitoring and quality control

procedures

c) Exchange of OPMET in a digital format IP/3 Singapore

IP/4 Australia

d) Other ROBEX issues WP/4 Thailand

ROBEX WG/12


4 - 2

Tuesday 18 March 2014

0900 Start of business

0900 - 1030

Agenda Item 5: Guidance material

a) ROBEX Handbook WP/6 Secretariat

WP/14 Thailand

Flimsy 1 Thailand


1045 - 1200

b) ASIA/PAC ICD WP/7 Secretariat

c) OPMET related FASID tables WP/8 Secretariat

WP/15 Australia

Agenda Item 6: Future work programme and review WP/9 Secretariat

of terms of reference


Break-out group RODBs


1300 – 1430

Break-out group RODBs

Reading of the draft report

1430 – 1445 Break

1445 – 1600

Review of draft report

ROBEX WG/12


4 - 3

Wednesday 19 March 2014

0830 – 0900 Registration (for new participants only)

0900 - 1030

Opening of the conjoint session Secretariat

(ROBEX WG/12 and MET/H TF/4)

Agenda Item 1: VAAC Backup Tests WP/C2 New Zealand

IP/C1 Japan


a) SIGMET tests WP/C3 Japan

WP/C4 Singapore


1045 - 1200

b) Regional SIGMET monitoring and IP/C3 Australia

coordination

c) Review SIGMET Guide WP/C1 Secretariat

WP/C5 Hong Kong

China

d) Advisory information IP/C2 Australia


1300 – 1430

cont. IP/C5 Japan

e) Other SIGMET/advisory related business WP/C6 Australia

IP/C4 ROK

IP/C7 Australia

1430 – 1445 Break

MET/H TF/4 commences

ROBEX WG/12


5 - 1

FOLLOW-UP OF ROBEX WG/11

AGREED ACTION

Status on 19 March 2014

(√ = completed)

No.

Title/Action

Follow-up action

(target/completion dates in

brackets)

11/1

Status of OPMET provision in Bhutan.

That, the Secretariat (by way of State Letter) verifies the

status of implementation of OPMET information in Bhutan to

meet the requirements for international air navigation.

State Letter √

(April 2013/March 2014)

Verification of status in progress

(May 2014)

11/2

Follow-up on OPMET monitoring.

That, the Secretariat (with assistance from RODBs and

IATA):

a) verify the results of RODB and IATA OPMET

monitoring; and

b) highlight results of OPMET monitoring to States to

address problems where OPMET availability, compliance

or regularity do not meet requirements.

State Letter √


11/3

IROG back-up procedures.

That, RODBs Brisbane and Tokyo develop and test IROG

back-up procedures based on the procedures developed by

RODBs Bangkok and Singapore in the ROBEX Handbook,

Appendix D.

IROG back-up procedures and

back-up test

Australia advised current system

unable to back-up another IROG;

planned upgrade in approx. 2 years;

back-up arrangements with IROG

Tokyo could be pursued then

11/4

ROBEX Handbook – updates.

That,

a) the Secretariat incorporates updates provided by the

meeting in Attachment 9 to the Report in the next

amendment to the ROBEX Handbook; and

b) States provide the Secretariat with further updates

required in time for the next major amendment of the

ROBEX Handbook in September 2013.

ROBEX Handbook amendment √

(April 2013/November 2014)

Submission of updates for the

ROBEX Handbook

In progress (July 2013)

ROBEX Handbook amendment

In progress (September 2013)

11/5

ASIA/PAC ICD – updates.

That,

a) the Secretariat incorporates updates provided by the

meeting in Attachment 10 to the Report in the next

amendment to the ASIA/PAC ICD; and

b) States provide the Secretariat with further updates

required in time for the next major amendment of the

ASIA/PAC ICD in September 2013.

ASIA/PAC ICD amendment

In progress (April 2013)

Submission of updates for the

ASIA/PAC ICD

In progress (July 2013)

ASIA/PAC ICD amendment


ROBEX WG/12


5 - 2

11/6

FASID – updates.

That, the Secretariat with assistance from States primarily

concerned develop proposal for amendment to FASID as

agreed by the meeting in section 4 of the Report.

Proposal for amendment of FASID

√

(April 2013/February 2014)

11/7

Follow-up on VAAC back-up test.

That, the VAAC provider States review the VAAC back-up

test procedures and amend if necessary to ensure:

a) instructions for States are clear on what action is and is

not required by MWOs; and

b) best practice to disseminate VAA in a secure manner to

reach all known users, preferably via the AFTN.

VAAC back-up test procedures

reviewed and amended if necessary

In progress (August 2013)

11/8

Follow-up on SIGMET monitoring.

That, the Secretariat promulgate the results of SIGMET

monitoring by RODBs Singapore and Brisbane presented in

the Appendix L to this Report, which indicated that no

SIGMET were issued by Afghanistan, Nauru, Papua New

Guinea and Solomon Islands, to the States concerned in order

to urgently facilitate the establishment and implementation of

effective corrective action plans to address deficiencies

related to SIGMET not provided in accordance with

requirements.

State Letter

√


11/9

SIGMET Guide – updates.

That, the Secretariat incorporates:

a) updates provided by the meeting in Appendix N to the

Report in the next amendment to the SIGMET Guide;

and

b) an example to report a situation when no ash is expected

in the forecast section of a SIGMET in time for the next

major amendment of the SIGMET Guide in September

2013.

SIGMET Guide amendments

√ (April 2013/November 2013)


_ _ _ _ _ _ _ _ _ _ _ _ _ _

ROBEX WG/12


6 - 1

APANPIRG/24 Conclusions/Decisions – Action Plan (MET-related)

Conclusion/

Decision No

---

Strategic

Objective*

Title of Conclusion/Decision Text of Conclusion/Decision Responsibility Deliverable Target date

Status as of10

March 2014

C 24/30

A & C

XML Trial over

ATN/AMHS

That, ICAO be invited to provide guidance on the

requirements for end-user product/message in

respect of XML coded NOTAM and OPMET

messages.

ICAO APAC

Office

IOM to HQ

December 2013 COMPLETED

IOM to HQ. Ref.:

T 8/9.6:AP-

CNS0114/13

(11 Oct. 13)

C 24/48

A & C

Migration to WAFS gridded

global forecasts in WMO

GRIB Edition 2 code form

as soon as possible

That, in view of the cessation of GRIB1 on 14

November 2013, States be invited to:

a) urgently migrate to receiving, decoding and

using the WAFS gridded global forecasts in WMO

GRIB Edition 2 code form as soon as possible, if

they have not already done so; and

b) if required, urgently contact their

workstation/software providers or consider

contacting another State already using the GRIB2

datasets for assistance in migrating to GRIB2.

Note: States who feel unable to migrate prior to 14

November 2013 should advise ICAO as soon as

possible.

ICAO APAC

Office

State letter July 2013 COMPLETED

State letter Ref.: T

4/8.1:AP118/13

(MET) issued 6

August 2013

ROBEX WG/12


Conclusion/

Decision No

---

Strategic

Objective*


Status as of10

March 2014

C 24/49

A & C

Improvements to SIGMET

Implementation and

Distribution

That, the ICAO be invited to urge:

a) MWOs to improve upon the compliance and

availability of SIGMET information; and

b) Regional OPMET databanks to ensure that

all SIGMET data is forwarded to the SADIS and

WIFS Providers in accordance with section 1.2.2 of

Appendix 6 to ICAO Annex 3 — Meteorological

Service for International Air Navigation.

ICAO APAC

Office



4/7.5:AP120/13

(MET) issued 9

August 2013

C 24/50

A & C

Use of VONA format

That, States be invited to consider ways to ensure

implementation of the VONA format to report

volcanic activities by Volcano Observatories.

ICAO APAC

Office



4/9.1.1:AP126113

(MET) issued 20

August 2013

C 24/51

A & C

Assessment of bilateral

agreements for the provision

of SIGMET services

That, in coordination with ICAO, States to

investigate and assess the feasibility of

implementing effective bilateral agreements for the

provision of SIGMET services as a corrective

action towards resolution of air navigation

deficiencies listed in the MET field.

ICAO APAC

Office & States

State Letter and

Working paper

developed

September 2013 &

March 2014

IN PROGRESS

D 24/52

A & C

Survey on the

implementation of

meteorological competency

That, ICAO coordinates a survey on the level of

implementation of competency assessment,

qualifications and training for meteorological

personnel providing service for international air

navigation and report the result to the MET SG/18

meeting.

ICAO APAC

Office

State Letter and

Working paper

developed

September 2013 &

March 2014

IN PROGRESS

ROBEX WG/12


6 - 3

Conclusion/

Decision No

---

Strategic

Objective*


Status as of10

March 2014

D 24/53

A & C

Guidance on QMS,

competencies and cost

recovery

That, ICAO investigates opportunities to provide

States with guidance information regarding

implementation of QMS, competencies and cost

recovery within the APAC Region

ICAO APAC

Office



4/7.1.2:AP039/14

(MET) issued 11

March 2014

D 24/59

A & C

ATM/AIS/SAR, AOP, CNS

and MET Deficiency List

That, the list of air navigation deficiencies reported

and identified in ATM/AIS/SAR, AOP, CNS and

MET Deficiency List be updated as detailed in

Appendix A to D to the Report on Agenda Item 4.

ICAO APAC

office

Updated deficiency

list

December 2013 COMPLETED

_ _ _ _ _ _ _ _ _ _ _ _ _ _

ROBEX WG/12


7 - 1

ICAO APAC REGIONAL OPMET BULLETIN EXCHANGE

WORKING GROUP (ROBEX WG)

1. COMPOSITION

The ROBEX WG is made up of members from States representing the five APAC Regional OPMET Data Banks (RODBs):

Australia/Brisbane, Fiji/Nadi, Japan/Tokyo, Singapore and Thailand/Bangkok; the World Area Forecast System (WAFS),

Satellite Distribution System (SADIS) and WAFS Internet File System (WIFS) Provider States: United Kingdom and United

States; the three APAC Volcanic Ash Advisory Centres (VAACs): Australia/Darwin, Japan/Tokyo and New

Zealand/Wellington; the designated focal points for SIGMET tests and regional OPMET bulletin exchange (ROBEX); and

the International Air Transport Association (IATA).

Secretariat Address Contact

Mr. Peter Dunda

ICAO

Regional Officer MET


252/1, Vibhavadi Rangsit Road

Ladyao, Chatuchak

Bangkok 10900

Thailand

Tel: +66 (2) 537-8189 Ext. 153

Fax: +66 (2) 537-8199

Email: [email protected]

Chair Address Contact

Ms. Sujin

Promduang

THAILAND

(Bangkok RODB)

General Administrative Manager

Aeronautical Information Management Centre


102 Ngamduplee, Sathorn, Bangkok 10120

Thailand

Tel: +66 (2) 285 9083

Fax: +66 (2) 287 3131


Members Address Contact

Mr. Aidan Cooley

AUSTRALIA

(Brisbane RODB)

ATM Systems Specialist

Airservices

Locked Bag 747

Eagle Farm QLD 4009

Tel: +61 (7) 3866 3762

Mob: +61 417 434 975

Fax: +61 (7) 3866 3506


Mr. Tim Hailes

AUSTRALIA

(Brisbane RODB &

Darwin VAAC)

National Manager

Regional Aviation Weather Services

Weather & Ocean Services Branch

Australian Bureau of Meteorology

GPO 1289

Melbourne VIC 3001

Tel: +61 (3) 9669 4273

Mob: +61 4 2784 0175


Cc: [email protected]

Mr William Reece

FIJI

(Nadi RODB)

Station Officer Telecoms (Training & Standards)

Airports Fiji Limited,

Private Mail Bag, Nadi Airport

Fiji Islands

Tel: +679 673 1198

Mob: +679 990 6105

Fax: +679 673 1198


Mr. Yuichi

Yamakoshi

JAPAN

(Tokyo RODB &

Tokyo VAAC)

Senior Scientific Officer

Administration Division

Forecast Department



Tokyo 100-8122

Tel: +81 (3) 3212 8341


Mr Keith Mackersy

NEW ZEALAND

(Wellington

VAAC)

Meteorological Specialist

Civil Aviation Authority of New Zealand

PO Box 3555

Wellington

Tel: +64 4 9040543

Fax: +64 4 9041543









ROBEX WG/12


7 - 2

Members Address Contact

Ms. Chua Guat Mui

SINGAPORE

(Singapore RODB)

Principal Technical Officer

Meteorological Services Singapore

P.O. Box 8, Singapore Changi Airport Post Office

Singapore 918141

Tel: +65 6542 2861

Fax: +65 6542 2915


Mr. Chris Tyson

UNITED

KINGDOM

(WAFC London)

SADIS Manager & International Aviation Analyst

Met Office, Fitzroy Road

Exeter Devon EX1 3PB

Tel: +44 (0) 1392 884892

Fax: +44 (0) 870 900 5050


Mr. Steven

Albersheim

UNITED STATES

(WAFC

Washington)

Federal Aviation Administration

Senior Meteorologist, Programme Lead

International

FAA Headquarters

800 Independence Ave, S.W.

Washington, D.C. 20591

Tel: +1 (202) 385 7185

Fax: +1 (202) 385 7240


Hans-Rudi

Sonnabend

IATA

Head of Meteorological Services

Lufthansa Systems Aeronautics GmbH

Am Prime Parc 2

D-65479 Raunheim

Germany

Tel: +49 (69) 6969 0362

Fax: +49 (69) 6969 4736

Email:

[email protected]

[email protected]

2. DESCRIPTION

Objective Increase OPMET availability and reliability needed for flight planning (efficiency) and in-flight re-

planning (safety).

Benefits Increase in safety and efficiency (time and fuel savings).

Terms of Reference Under guidance from the ICAO Secretariat:

- Review the OPMET exchange schemes in the APAC, and MID and neighbouring Regions

and develop proposals for their optimization, taking into account the requirements by the

aviation users and the current trends for global OPMET exchange;

- Develop standardized quality control, monitoring and management procedures related to

ROBEX and other exchange schemes for OPMET information;

- Review the regional guidance material related to OPMET exchange;

- Liaise with other groups dealing with communication and/or management aspects of the

OPMET exchange in APAC, and other ICAO Regions and the WAFS Provider States (e.g.,

APAC ATN Implementation Coordination Group, BMG EUR Region, CNS/MET SG MID

Region, SADISOPSG).

Work Programme The work to be addressed by the ROBEX WG includes:

- Examine new and existing requirements for OPMET exchange in APAC, and MID and other

neighbouring regions along with the WAFS Provider States and assess the feasibility of

satisfying these requirements, taking into account the availability of the data;

- Keep the ROBEX scheme and other OPMET exchange schemes under review and prepare

proposals for updating and optimizing the schemes;

- Review and update of the procedures for inter-regional OPMET exchange and ensure the

availability of the required APAC and MID OPMET data for SADIS and WIFS;

- Review the regional guidance material on OPMET exchange to ensure procedures are

provided for the exchange of all required OPMET data types: SA, SP, FT, WS, WC, WV, FK,

FV and UA;

- Conduct trials and develop procedures for quality control, monitoring and management of the

OPMET exchange to foster implementation of quality management of OPMET data by the

ROBEX centres and the RODBs;

- Report on deficiencies in the format and dissemination of OPMET messages;

- Participate in the testing, and implementation and awareness of the transition to digital

exchange of OPMET using a code form based on XML/GML;

- Conduct regular regional VAAC back-up and SIGMET tests;

- Develop quality control guidance material and promote implementation of quality control for

OPMET management.






ROBEX WG/12


7 - 3

3. COMMUNICATION STRATEGIES

Description Target Audience Delivery Method Frequency / Date Responsibility

Work Plan ROBEX WG Members Document via email &

ROBEX WG Meeting

As required but reviewed at

the ROBEX WG Meeting

and the MET SG

Chair

General

correspondence

ROBEX WG Members Email As required ROBEX WG

Members

Task Force Meeting ROBEX WG Members Meeting Annually Chair

Status & Milestone

Reports

ICAO Secretariat and

ROBEX WG Members

Report via email & WP

at ROBEX WG Meeting

Annually Chair

Task Force Report All APAC States Working Paper at MET

SG

Annually Chair

4. PERFORMANCE FRAMEWORK FORM (PFF)

Tasks Time Frame Responsibilit

y

Status Milestone

Task 1: Improve the availability of

OPMET data

Ongoing ROBEX WG 1

Task 2: Improve timeliness,

compliance and regularity of OPMET

exchange

Ongoing ROBEX WG 2

Task 3: Identify gaps in processes,

procedures and OPMET exchange

Ongoing ROBEX WG 3, 4, 5

Task 4: Review regional guidance

material related to OPMET data

Ongoing ROBEX WG 3, 4, 5, 6

Task 5: Facilitate and monitor the

migration to AIM and new MET codes

(e.g. XML)

2013-2016 ROBEX WG 7

Task 6: Review the RODB structure TBC ROBEX WG 8

5. MILESTONES

Milestone Accountability Dates Status

Milestone 1: Achieve 95% (90%) or greater OPMET availability

for AOP (non-AOP) aerodromes at RODBs and WAFCs.

ROBEX WG Annually

Jun

Milestone 2: Achieve OPMET timeliness, compliance and

regularity index of 0.95 (0.90) for AOP (non-AOP) aerodromes

at RODBs and WAFCs.

ROBEX WG Annually

Jun

Milestone 3: Improved issuance and compliance of test

SIGMETs Tests.

ROBEX WG Annually

Jun

Milestone 4: VAAC Back-up Tests conducted, analysed and

report complete.

VAAC Back-up

Focal Points

Annually

Jun

Milestone 5: IROG Back-up Tests conducted, analysed and

report complete.

Bangkok RODB Annually

Mar

Milestone 6: RODB Monitoring procedures updated in ROBEX

Handbook

Secretariat Jun 2014

Milestone 7: Report to ROBEX WG & MET SG on digital

OPMET exchange (i.e. XML) & testing.

Secretariat &

Chair

Annually

Mar & May

Milestone 8: RODB structure review complete. ROBEX WG TBC

ROBEX WG/12


7 - 4

6. WORK PLAN

Activity / Milestone Accountability Predecessors Date Status

Activity 1: Increasing OPMET availability at RODBs & WAFCs (95 and 90% for AOP and non-AOP aerodromes)

Activity 1.1: Assist Nadi RODB in

conducting OPMET availability testing

Brisbane RODB - Nov 2014

Activity 1.2: Perform real time monitoring if

required

RODBs & IATA - If required

Activity 1.3: Monitor RODB OPMET

reception in Jan and use Dec as PI threshold.

RODBs - Annually

Dec/Jan

Activity 1.4: Monitor SADIS/WIFS OPMET

reception.

IATA - Annually

Jan

Activity 1.5: Score against FASID Table

MET 1A and 2A.

Singapore, Tokyo,

Bangkok RODBs

& IATA

1.3 & 1.4 Annually

Feb

Activity 1.6: Report results and deficiencies

to ROBEX WG meeting.

Bangkok RODBs

& IATA

1.5 Annually

Mar

Activity 1.7: Report summary of OPMET

availability results to MET SG

Secretariat & Chair 1.6 Annually

May

Activity 1.8: Advise States of OPMET

deficiencies.

Secretariat 1.7 Annually

Jun

Activity 1.9: Provide support for States to

rectify deficiencies if requested.

RODBs 1.8 As required

Activity 1.10: Develop a common dataset

and assess the consistency between RODBs

of the 'availability' calculation and

standardise.

Singapore, Tokyo,

Bangkok RODBs

- Jul 2014

Milestone 1: Achieve 95% (90%) or greater

OPMET availability for AOP (non-AOP)

aerodromes at RODBs & WAFCs.

ROBEX WG 1.9 Annually

Jun

Activity 2: Improving OPMET timeliness, compliance and regularity

Activity 2.1: Assist Nadi RODB to collect

the data for conducting OPMET testing

Brisbane RODB - Nov 2014

Activity 2.2: Monitor OPMET timeliness,

compliance and regularity in Jan and use Dec

as PI threshold.

RODBs & IATA - Annually

Dec/Jan

Activity 2.3: Collate and analyse data Singapore, Tokyo,

Bangkok RODBs

& IATA

2.2 Annually

Feb

Activity 2.4: Report State irregularities to

ROBEX WG meeting

Bangkok RODBs

& IATA

2.3 Annually

Mar

Activity 2.5: Report summary of OPMET

timeliness, compliance and regularity results

to METSG

Chair 2.4 Annually

May

Activity 2.6: Inform States of compliance Secretariat 2.5 Annually

Jun

ROBEX WG/12


7 - 5

6. WORK PLAN


Activity 2.7: Provide support for States to

rectify deficiencies if requested.

RODBs 2.6 As required

Activity 2.8: Develop a common dataset and

assess the consistency between RODBs of

the 'compliance' and 'regularity' calculation

and standardise.

Singapore, Tokyo,

Bangkok RODBs

- Jul 2014

Milestone 2: Achieve 95% (90%) or greater

OPMET timeliness, compliance and

regularity for AOP (non-AOP) aerodromes at

RODBs & WAFCs.


Jun

Activity 3: SIGMET Tests

Activity 3.1: Review SIGMET Test

procedures

ROBEX WG - Annually

Aug

Activity 3.2: State Letter regarding SIGMET

Tests


Sep

Activity 3.3: Conduct WC SIGMET Tests RODBs 3.2 Annually 1st

Wed in Nov

To be conducted on 5 Nov

2014

Activity 3.4: Conduct WV SIGMET Tests RODBs 3.2 Annually

2nd

Wed in

Nov

To be conducted on 12

Nov 2014

Activity 3.5: Conduct WS SIGMET Tests RODBs 3.2 Annually 3rd

Wed in Nov

To be conducted on 19

Nov 2014

Activity 3.6: Collate and analyse test data RODBs 3.3 - 3.5 Annually

Jan

Activity 3.7: Report to ROBEX WG SIGMET Focal

Points

3.6 Annually

Mar

Activity 3.8: Report on SIGMET Test

Results to MET SG.

Chair 3.7 Annually

May

Activity 3.9: Advise States of SIGMET

deficiencies


Jun

Milestone 3: Improved issuance and

compliance of test SIGMETs


Jun

Activity 4: VAAC Back-up Tests

Activity 4.1: Review VAAC Back-up Test

procedures to include Wellington

ROBEX WG and

VAACs

May 2014

and then

annually Jan

Activity 4.2: Update VAAC Back-up

Procedures in SIGMET Guide


May

Activity 4.3: State Letter regarding VAAC

Back-up Tests


Jul

Activity 4.4: Conduct VAAC Back-up Test

between Darwin and Tokyo

VAACs 4.3 Annually

Sep – TBC

Activity 4.5: Conduct VAAC Back-up Test

between Darwin and Wellington

VAACs 4.3 Annually

Oct – TBC

ROBEX WG/12


7 - 6

6. WORK PLAN


Activity 4.6: Collect test results and send to

VAAC Back-up Test Focal PointProvider

State members

RODBs 4.4 Annually

Sep & Oct

(TBC)

Activity 4.7: Analyse Test results VAAC Back-up

Focal

PointsMembers

4.5 Annually

Nov

Activity 4.8: Report to ROBEX WG VAAC Back-up

Focal

PointsMembers

4.6 Annually

Feb

Activity 4.9: Report to MET SG. Chair 4.8 Annually

May

Activity 4.10: Advise relevant States,

VAACs and RODBs of any deficiencies.


Jun

Milestone 4: VAAC Back-up Tests

conducted, analysed and report complete.

VAAC Back-up

Focal

PointsMembers

4.8 Annually

Jun

Activity 5: IROG Back-up Tests

Activity 5.1: Identify Investigate feasibility

for IROG back-up arrangements testing of

IROG Tokyo & Brisbane

Secretariat - Oct 2014

Activity 5.2: Review IROG Back-up Test

procedures to include all IROG.

All IROGs - Annually

Feb

Activity 5.3: Updated IROG Back-up

Procedures in ROBEX Handbook.


May

Activity 5.4: Identify list of MET Bulletins

to monitor.

All IROGs - Annually

Jan/Feb

Activity 5.5: Conduct IROG Back-up Tests All IROGs 5.4 Annually

Jan/Feb

Activity 5.6: Collect & analyse test results All IROGs 5.5 Annually

Feb

Activity 5.7: Report to ROBEX WG Bangkok RODB 5.6 Annually

Mar

Milestone 5: IROG Back-up Tests

conducted, analysed and report complete.

Bangkok RODB 5.7 Annually

Mar

Activity 6: APAC RODB Monitoring procedures

Activity 6.1: Letter to ROBEX Centres

requesting confirmation that ROBEX

Handbook Appendix A, B & C has the

correct information regarding the Bulletins.

Also ask for Hours of Operation and Issue

Times of METAR and TAF.

Secretariat - May 2014

Activity 6.2: Review ROBEX Handbook

Appendix A & B table structure to include

columns for Hours of Operation and Issue

Times.

Chair 6.1 Jul 2014

ROBEX WG/12


7 - 7

6. WORK PLAN


Activity 6.3: Review monitoring procedure

in ROBEX Handbook.

All RODBs - Aug 2014

Activity 6.4: RODBs to indicate differences

in procedures and resolve these differences.

All RODBs 6.3 Aug 2014

Activity 6.5: Any changes to RODB

monitoring procedures and updates to

Appendix A, B and C in ROBEX Handbook.

Secretariat 6.2 & 6.4 Sep 2014

Milestone 6: RODB Monitoring procedures

updated in ROBEX Handbook

Secretariat 6.5 Sep 2014

Activity 7: New OPMET Exchange Formats

Activity 7.1: Monitor migration to AIM and

new OPMET codes (i.e. XML/GML).

Secretariat - As required

Activity 7.2: Review documentation relating

to the XML schema version 1.0, release

candidate 2. Feedback through Secretariat.

RODBs May 2014

Activity 7.3: Report to MET SG on plans for

implementation of XML schema at APAC

RODBs.

Secretariat Next

meeting

MET SG

Activity 7.4: Conduct a trial of the new XML

schema developed by WMO TT-AvXML.

Singapore RODB - Oct 2014

Activity 7.5: Consider options and strategies

to deal with digital data exchange of OPMET

data in its area of responsibility, including

non-compliance of OPMET products with

requirements of WMO TT-AvXML schema.

RODBs Feb 2015

Activity 7.6: Increase awareness of the

requirement of digital exchange of OPMET

data and the impact.

RODBs As required

Activity 7.7: Report to ROBEX WG

regarding testing and implementation of

digital OPMET exchange in APAC.

Secretariat 7.1-7.6 Annually

Mar

Milestone 7: Report to ROBEX WG & MET

SG on digital OPMET exchange (i.e. XML)

& testing.


May

Activity 8: Review RODB Structure

Activity 8.1: Review optimum inter-regional

exchange of APAC OPMET data. In

particular consolidate data sent to AFI from

either Bangkok or Brisbane.

Bangkok &

Brisbane RODBs

- May 2014

Activity 8.2: Review ROBEX Scheme

diagram vs Table in 11.1 of ROBEX

Handbook.

All RODBs 8.1 May 2014

Activity 8.3: Review AFTN network

diagram and add an AMHS diagram in the

ROBEX Handbook.

Secretariat - Aug 2014

ROBEX WG/12


7 - 8

6. WORK PLAN


Activity 8.4: Review RODB structure taking

into account:

o Capability;

o Message structure (XML)

readiness;

o Delivery methods (internet,

AHMS);

o New Products (i.e. ATM

requirements).

ROBEX WG - TBC

Milestone 8: RODB structure review

complete.

ROBEX WG - TBC

_ _ _ _ _ _ _ _ _ _ _ _ _

ROBEX WG/12

Attachment C1 to the Report

C1 - 1

WELLINGTON/DARWIN VAAC BACK-UP TEST PROCEDURES

1. Introduction 1.1 The International Airways Volcano Watch Operations Group (IAVWOPSG) recognized the need for the regular testing of VAAC back-up procedures that would ensure the continuing availability of Volcanic Ash Advices and identify deficiencies in the dissemination procedures of back-up products. Therefore, the second meeting of IAVWOPSG held in Bangkok, 15 to 19 March 2004, adopted Conclusion 2/19, as follows:

Conclusion 2/19 – Inclusion of VAAC back-up procedures in Doc 9766

That the Secretariat include in Doc 9766, Handbook on the International Airways Volcano Watch (IAVW) – Operational Procedures and Contact List, the VAAC back-up procedures agreed by the group.

1.2 Appendix D, paragraph f) of ICAO Doc.9766 - Handbook on International Airways Volcano Watch (IAVW) states that:

The back-up arrangements should be tested at least annually.

1.3 The Wellington and Darwin VAACs have developed a mutual back-up arrangement that includes procedures for undertaking a back-up test as described in this document. 2. Purpose and Scope of VAAC Back-up tests 2.1 The purpose of the VAAC back-up test is to ensure that internal procedures for the handover of responsibility and the issue of products for the other VAAC’s area of responsibility are robust and functional. 2.2 The scope of the test also includes checking the dissemination pathways of the Volcanic Ash Advisory (VAA) messages. 2.3 The test is not designed to check the issuance of Volcanic Ash SIGMET and so there is no requirement to issue test SIGMETs. 3. Back-up test procedures 3.1 Procedures for Wellington – Darwin VAAC Back-up tests 3.1.1 Internal procedures related to handover of responsibility and issuance of VAAs for the other VAAC’s area of responsibility will be tested and the results included in a final report. 3.2 Procedures for testing the dissemination of back-up VAAs 3.2.1 On the specified date at 0100 UTC the Wellington VAAC will issue a test Volcanic Ash Advisory (VAA) for the Darwin VAAC area of responsibility south of latitude 20S. The message will indicate that it is a TEST and will follow the format given in Section 4 of these procedures. 3.2.2 Recipients of the message should send a confirmation email to the address given in the message, including the message text and the time received.

ROBEX WG/12


C1 - 2

3.2.3 MWOs should NOT issue a test SIGMET. 3.2.4 At 0200 UTC the Darwin VAAC will issue a test VAA for the Wellington VAAC area of responsibility. The message will indicate that it is a TEST and will follow the format given in Section 4 of these procedures. 3.2.5 Recipients of the message should send a confirmation email to the address given in the message, including the message text and the time received. 3.2.6 MWOs should NOT issue a test SIGMET. 3.2.7 In the event of a major eruption in either area the test may be cancelled. 3.3 Processing of the test results 3.3.1 The Wellington and Darwin participating Asia/Pacific VAACs, in conjunction with the Asia/Pacific Regional OPMET Databanks (RODBs), will analyse the received responses to the test messages and present the results to IAVWOPSG/9 in 2015 or an appropriate expert group (or groups) that may be required to progress international airways volcano watch (IAVW) related work. 4. Format of test VAA for the external test 4.1 From VAAC Wellington to for VAAC Darwin

FVAU01 ADRM DDHHMM VA ADVISORY DTG: YYYYMMDD/HHMMZ VAAC: DARWIN VOLCANO: TEST 9999-999 PSN: N1000 E10000 AREA: UNKNOWN SUMMIT ELEV: 9999M ADVISORY NR: YYYY/N INFO SOURCE: TEST TEST TEST AVIATION COLOUR CODE: NIL ERUPTION DETAILS: TEST TEST TEST OBS VA DTG: 99/9999Z OBS VA CLD: WIND SFC/FL999 999/99KT FCST VA CLD +6 HR: NO VA EXP FCST VA CLD +12 HR: NO VA EXP FCST VA CLD +18 HR: NO VA EXP RMK: THIS IS A TEST ADVISORY ISSUED BY WELLINGTON VAAC FOR THE DARWIN VAAC AREA OF RESPONSIBILITY SOUTH OF LATITUDE 20S. PLEASE ACKNOWLEDGE RECEIPT OF THIS ADVISORY BY SENDING AN EMAIL TO [email protected] DARWIN VAAC. NXT ADVISORY: NO FURTHER ADVISORIES=

ROBEX WG/12


C1 - 3

4.2 From VAAC Darwin to for VAAC Wellington

FVPS01 NZKL DDHHMM VA ADVISORY DTG: YYYYMMDD/HHMMZ VAAC: WELLINGTON VOLCANO: TEST 9999-999 PSN: N1000 E10000 AREA: UNKNOWN SUMMIT ELEV: 9999M ADVISORY NR: YYYY/N INFO SOURCE: TEST TEST TEST AVIATION COLOUR CODE: NIL ERUPTION DETAILS: TEST TEST TEST OBS VA DTG: 99/9999Z OBS VA CLD: WIND SFC/FL999 999/99KT FCST VA CLD +6 HR: NO VA EXP FCST VA CLD +12 HR: NO VA EXP FCST VA CLD +18 HR: NO VA EXP RMK: THIS IS A TEST ADVISORY ISSUED BY DARWIN VAAC FOR THE WELLINGTON VAAC AREA OF RESPONSIBILITY. PLEASE ACKNOWLEDGE RECEIPT OF THIS ADVISORY BY SENDING AN EMAIL TO [email protected] WELLINGTON VAAC. NXT ADVISORY: NO FURTHER ADVISORIES=

_ _ _ _ _ _ _ _ _ _ _ _ _ _

ROBEX WG/12


C2 - 1

THE OUTLINE OF THE SCHEME OF COOPERATION

BETWEEN VAACS TOKYO AND DARWIN

1. The areas of responsibility for VAACs Tokyo and Darwin to be backed up

VAAC Darwin takes charge of the whole area of responsibility of VAAC Tokyo,

while VAAC Tokyo takes charge of part of the area of responsibility of VAAC Darwin north

from 20 degrees south.

ROBEX WG/12


C2 - 2

2. Conceptual chart of VAAC back-up (case where VAAC Tokyo is backed up as an example)

(1) When functions of VAAC Tokyo are lost and the request for back-up is sent.

(2) When VAAC Tokyo resumes its operation

JMA BoM

Aviation Users in AoR of VAAC Tokyo

1. Request for back-up

2. Acceptance

3. Notification of back-up

JMA BoM

Aviation Users in AoR of VAAC Tokyo

1. Request for termination of back-up

2. Acceptance

3. Notification of the termination

ROBEX WG/12


C3 - 1

Summary of WC and WV SIGMET Test Results

MWO TTAAii CCCC FIR Priority TTAAii CCCC YYGGgg MWO FIR VTBB YBBB NFZZ WSZZ RJTD

AYPY WCNG20 AYPY AYPY - - - - - - - - - - -

AYPY WCNW20 AYPY ANAU - - - - - - - - - - -

AYPY WCSO20 AYPY AGGG - - - - - - - - - - -

KKCI WCPN01-13 KKCI KZAK FF WCPN01 KKCI 120200 KKCI KZAK - - - 0203 0209

NFFN WCFJ01,02,… NFFN NFFF FF WCFJ01 NFFN 120000 NFFN NFFF 0209 0208 0208 0208 0209

NTAA WCPF21 NTAA NTTT GG WCPF20 NTAA 120205 NTAA NTTT 0214 0206 0206 0207 0207

NZKL WCNZ21 NZKL NZZC - - - - - - - - - - -

NZKL WCPS21 NZKL NZZO FF WCPS21 NZKL 120212 NZKL NZZO 0212 0212 0212 0212 0212

OPKC WCPK31 OPKC OPKR GG WCPK31 OPKC 120205 OPKC OPKC 0208 0208 0208 0208 0212

OPLA WCPK31 OPLA OPLR GG WSPK31 OPLA 120200 OPLA OPLA 0200 0157 0200 0200 -

PAWU WCAK01-09 PAWU PAZA - - - - - - - - - - -

PHFO WCPA01-13 PHFO KZAK WCPA01 PHFO 120200 PHFO KZAK - - - 0203 0200

RCTP WCCI31 RCTP RCAA FF WCCI31 RCTP 120200 RCTP RCAA 0204 0200 0204 0204 0204

RJTD WCJP31 RJTD RJJJ GG WCJP31 RJTD 120205 RJTD RJJJ 0205 0205 0205 0205 0224

RKSI WCKO31 RKSI RKRR FF WCKO31 RKSI 120201 RKSI RKRR 0202 0202 0202 0202 0202

RPLL WCPH31 RPLL RPHI FF WCPH31 RPLL 120200 RPLL RPHI 0200 0200 0200 0200 0200

VABB WCIN31 VABB VABF FF WCIN31 VABB 120205 VABB VABF 0206 0203 0205 0205 0206

VCBI WCSB31 VCBI VCBI - - - - - - - - - - -

VECC WCIN31 VECC VECF FF WCIN31 VECC 120205 VECC VECF 0205 0205 0205 0205 0205

VGHS WCBW20 VGHS VGFR FF WCBW20 VGHS 120205 VGHS VGFR 0205 0205 0205 0205 0205

VHHH WCSS20 VHHH VHHK FF WCSS20 VHHH 120203 VHHH VHHK 0203 0203 0203 0203 0202

VIDP WCIN31 VIDP VIDF FF WCIN31 VIDP 120205 VIDP VIDF 0210 0201 0205 0210 0210

VLVT WCLA31 VLVT VLVT - - - - - - - - - - -

VOMM WCIN31 VOMM VOMF FF WCIN31 VOMM 120205 VOMM VOMF 0204 0203 0218 0204 0204

VRMM WCMV31 VRMM VRMF - - - - - - - - - - -

VTBS WCTH31 VTBS VTBB FF WCTH31 VTBS 120212 VTBS VTBB 0217 0218 0224 0217 0217

VVGL WCVS31 VVGL VVNB FF WCVS31 VVGL 120201 VVGL VVNB 0203 0159 0203 0203 0203

VVGL WCVS31 VVGL VVTS FF WCVS31 VVGL 120202 VVGL VVTS 0204 0201 0204 0205 0204

VYYY WCBM31 VYYY VYYY - - - - - - - - - - -

WAAA WCID21 WAAA WAAF - - - - - - - - - - -

WIII WCID20 WIII WIIF FF WCID20 WIII 120218 WIII WIII 0229 0224 0229 0229 0229

WMKK WCMS31 WMKK WBFC FF WCMS31 WMKK 120220 WBKK WBFC 0221 0220 0221 0221 0221

WMKK WCMS31 WMKK WMFC FF WCMS31 WMKK 120220 WMKK WMFC 0221 0220 0220 0220 0220

WSSS WCSR20 WSSS WSJC FF WCSR20 WSSS 120205 WSSS WSJC 0205 0205 0205 0205 0205

YBRF WCAU01 ABRF YBBB WCAU01 ADRM 120158 YBRF YBBB - 0158 - - -

YBRF WCAU01 ABRF YMMM - - - - - - - - - - -

YDRM WCAU01 ADRM YBBB WCAU01 ADRM 120204 YPDM YBBB 0204

YDRM WCAU01 ADRM YMMM - - - - - - - - - - -

YPRF WCAU01 APRF YBBB WCAU01 APRF 120220 YPRF YBBB - 0220 - - -

YPRF WCAU01 APRF YMMM WCAU01 APRF 120219 YPRF YMMM - 0219 - - -

ZBAA WCCI33 ZBAA ZBPE FF WCCI33 ZBAA 120205 ZBAA ZBPE 0204 0202 0202 0204 0204

ZGGG WCCI35 ZGGG ZGZU FF WCCI35 ZGGG 120205 ZGGG ZGZU 0200 0200 0200 0200 0200

ZJHK WCCI35 ZJHK ZJSA FF WCCI35 ZJHK 120203 ZJHK ZJSA 0209 0209 0209 0209 0209

ZKPY WCKR31 ZKPY ZKKP - - - - - - - - - - -

ZSSS WCCI34 ZSSS ZSHA GG WCCI34 ZSSS 120205 ZSSS ZSHA 0201 0200 0200 0201 0201

ZUUU WCKP31 ZUUU VDPP FF WCKP31 ZUUU 120202 ZUUU VDPP 0203 0203 0203 0203 0203

Header According to SIGMET Guide Test Result Received Time GGgg (UTC)

Table 1: Summary of the WC SIGMET test

1 results (presented by Japan)

1 APAC SIGMET test conducted on 12 November 2013 to test the issuance and reception of SIGMET messages

for tropical cyclones (WC SIGMET)

ROBEX WG/12


C3 - 2

MWO TTAAii CCCC FIR Priority TTAAii CCCC YYGGgg MWO FIR VTBB YBBB NFZZ WSZZ RJTD

AYPY WVNG20 AYPY AYPY - - - - - - - - - - -

AYPY WVNW20 AYPY ANAU - - - - - - - - - - -

AYPY WVSO20 AYPY AGGG - - - - - - - - - - -

KKCI WVPN01-13 KKCI KZAK GG WVPN01 KKCI 190200 KKCI KZAK - - - 0219 0211

NFFN WVFJ01,02,… NFFN NFFF FF WVFJ01 NFFN 190000 NFFN NFFF - 0205 0205 0205 0205

NTAA WVPF21 NTAA NTTT - - - - - - - - - - -

NZKL WVNZ21 NZKL NZZC FF WVNZ21 NZKL 190206 NZKL NZZC 0207 0206 0206 0206 0206

NZKL WVPS21 NZKL NZZO FF WVPS21 NZKL 190206 NZKL NZZO 0207 0206 0206 0206 0206

OAKB WVAH31 OAKB OAKX - - - - - - - - - - -

OPKC WVPK31 OPKC OPKR GG WSPK31 OPKC 190205 OPKC OPKR 0215 0214 0214 0214 -

OPLA WVPK31 OPLA OPLR GG WVPK31 OPLA 190200 OPLA OPLA 0206 0204 0205 0205 0205

PAWU WVAK01-09 PAWU PAZA - - - - - - - - - - -

PHFO WVPA01-13 PHFO KZAK - - - - - - - - - - -

RCTP WVCI31 RCTP RCAA FF WVCI31 RCTP 190207 RCTP RCAA 0208 0207 0207 0211 0208

RJTD WVJP31 RJTD RJJJ GG WVJP31 RJTD 190205 RJTD RJJJ 0207 0206 0206 0206 0209

RKSI WVKO31 RKSI RKRR FF WVKO31 RKSI 190203 RKSI RKRR 0204 0203 0203 0204 0204

RPLL WVPH31 RPLL RPHI FF WVPH31 RPLL 190200 RPLL RPHI 0202 0201 0201 0201 0201

UELL WVRA32 RUYK UELL - - - - - - - - - - -

UEST WVRA38 RUYK UEST - - - - - - - - - - -

UHHH WVRA31 RUHB UHHH - - - - - - - - - - -

UHMA WVRA31 RUPV UHMP - - - - - - - - - - -

UHMA WVRA32 RUPV UHMA - - - - - - - - - - -

UHMM WVRA31 RUMG UHMM - - - - - - - - - - -

UHPP WVRA31 RUPK UHPP FF WVRA31 RUPK 190245 UHPP UHPP - - - - 0245

UIAA WVRA31 RUCH UIAA - - - - - - - - - - -

UIII WVRA31 RUIR UIII - - - - - - - - - - -

VABB WVIN31 VABB VABF - - - - - - - - - - -

VCBI WVSB31 VCBI VCBI - - - - - - - - - - -

VECC WVIN31 VECC VECF - - - - - - - - - - -

VGHS WVBW20 VGHS VGFR FF/GG WVBW20 VGHS 190209 VGHS VGFR 0208 - - 0213 0212

VHHH WVSS20 VHHH VHHK FF WVSS20 VHHH 190203 VHHH VHHK 0204 0203 0203 0204 0204

VIDP WVIN31 VIDP VIDF FF WVIN31 VIDP 190205 VIDP VIDF 0212 0209 0213 0216 0212

VLVT WVLA31 VLVT VLVT GG WVLA31 VLVT 190205 VLVT VLVT 0346 0337 0344 0347 0347

VOMM WVIN31 VOMM VOMF FF WVIN31 VOMM 190205 VOMM VOMF 0207 0205 0205 0206 0207

VRMM WVMV31 VRMM VRMF - - - - - - - - - - -

VTBS WVTH31 VTBS VTBB FF WVTH31 VTBS 190218 VTBS VTBB 0225 0225 0227 0225 0225

VVGL WVVS31 VVGL VVNB FF WVVS31 VVGL 190201 VVGL VVNB 0204 0200 0200 0204 0204

VVGL WVVS31 VVGL VVTS FF WVVS31 VVGL 190202 VVGL VVTS 0206 0202 0202 0206 0206

VYYY WVBM31 VYYY VYYY - - - - - - - - - - -

WAAA WVID21 WAAA WAAF FF WVID21 WAAA 190208 WAAA WAAF - 0205 - 0205 0212

WIII WVID20 WIII WIIF DD/FF WVID20 WIII 190200 WIII WIIF 0227 0206 0206 0215 0215

WMKK WVMS31 WMKK WBFC FF WVMS31 WMKK 190205 WBKK WBFC 0208 0208 0210 0208 0210

WMKK WVMS31 WMKK WMFC FF WVMS31 WMKK 190205 WMKK WMFC 0205 0205 0205 0205 0205

WSSS WVSR20 WSSS WSJC FF WVSR20 WSSS 190205 WSSS WSJC 0205 0205 0205 0205 0205

YDRM WVAU01 ADRM YBBB GG WVAU01 ADRM 190205 YPDM YBBB 0207 0205 0205 0205 0212

YDRM WVAU01 ADRM YMMM GG WVAU01 ADRM 190206 YPDM YMMM 0207 0206 0210 0206 0207

ZBAA WVCI33 ZBAA ZBPE FF WVCI33 ZBAA 190205 ZBAA ZBPE 0203 0201 0201 0204 0203

ZGGG WVCI35 ZGGG ZGZU FF WVCI35 ZGGG 190205 ZGGG ZGZU 0204 0203 0203 0205 0204

ZHHH WVCI45 ZHHH ZHWH GG WVCI45 ZHHH 190240 ZHHH ZHWH 0247 0244 0246 0249 0245

ZJHK WVCI35 ZJHK ZJSA FF WVCI35 ZJHK 190205 ZJHK ZJSA 0207 0207 0207 0208 0207

ZKPY WVKR31 ZKPY ZKKP - - - - - - - - - - -

ZLXY WVCI37 ZLXY ZLHW FF/GG WVCI37 ZLXY 190203 ZLXY ZLHW 0203 0202 0202 0208 0204

ZMUB WVMO31 ZMUB ZMUB FF WVMO31 ZMUB 190206 ZMUB ZMUB 0207 - - 0207 0207

ZSSS WVCI34 ZSSS ZSHA FF/GG WVCI34 ZSSS 190205 ZSSS ZSHA 0203 0201 0201 0208 0202

ZUUU WVCI36 ZUUU ZPKM FF WVCI36 ZUUU 190207 ZUUU ZPKM 0208 0208 0208 0208 0208

ZUUU WVKP31 VDPP VDPP FF WVKP31 ZUUU 190203 ZUUU VDPP - 0204 0204 0205 -

ZWWW WVCI39 ZWWW ZWUQ FF/GG WVCI39 ZWWW 190205 ZWWW ZWUQ 0212 0200 0200 0212 -

ZYTX WVCI38 ZYTX ZYSH FF WVCI38 ZYTX 190205 ZYTX ZYSH 0218 0218 0219 0219 0218

Header According to SIGMET Guide Test Result Received Time GGgg (UTC)

Table 2: Summary of the WV SIGMET test

2 results (presented by Japan)

2 APAC SIGMET test conducted on 19 November 2013 to test the issuance and reception of SIGMET messages

for volcanic ash (WV SIGMET)

ROBEX WG/12


C4 - 1

WS SIGMET test1 results (presented by Singapore)

1 Afghanistan, Kabul (OAKB)

2 Australia, Cairns (YBCS) for YBBB FIR

3 Fuji, Nadi (NFFN)

4 Lao PDR, Vientiane (VLVT)

5 Mongolia, Ulaanbaatar (ZMUB)

6 Myanmar, Yangon (VYYY)

7 Nauru, by Port Moresby (AYPY)

8 Papua New Guinea, Port Moresby (AYPY)

9 Solomon Islands, by Port Moresby (AYPY)

10 Sri Lanka, Colombo (VCBI)

11 DPR Korea, Sunan (ZKPY)

12 United States, Kansas City (KKCI)

Table 1: States/MWOs that did not participate in WS SIGMET Test 9

SIGMET

Test 9

RODB

Reception

Bangkok

RODB

Brisbane

RODB

Singapore

RODB

Tokyo

RODB

Nadi

RODB

Test 9 245 48 of 50 49 of 50 50 of 50 50 of 50 48 of 50

(Nov 2013) 98% 96% 98% 100% 100% 96% Table 2: RODB Reception of WS SIGMET Test 9

SIGMET

Test 9

ROC

Reception

LOWM

ROC

LFPW

ROC

EGGY

ROC

EHDB

SADIS

EBBR

RODB

Test 9 220 45 of 50 44 of 50 47of 50 40 of 50 44 of 50

(Nov 2013) 91% 90% 88% 94% 80% 88% Table 3: EUR ROC, RODB and SADIS User Reception of WS SIGMET Test 9

TTAAii CCCC YYGGgg MWO FIR / UIR

WSZA31 FAOR 260853 FAJA FAOR

WSMG31 FMMI 260854 FMMI FMMM

WSMA31 FIMP 261025 FIMM FIMP

WSMA31 FIMP 261030 FIMM FIMP

WSZB31 FLKK 260905 FLFI FLKK

WSZB31 FLKK 261200 FWLL FLKK

WSZB31 FLKK 261240 FWLL FLKK

WSZB31 FLKK 261320 FWLL FLKK Table 4: WS SIGMET test messages received from AFI MWOs (between 0845-1035 UTC)

1 APAC SIGMET test (SIGMET Test 9) conducted on 26 November 2013 to test the issuance and reception of SIGMET

messages for phenomena other than tropical cyclones and volcanic ash (WS SIGMET)

ROBEX WG/12


C4 - 2

SIGMET Test 1-9 State participation MWO participation Test SIGMETs issued

Test 1 (Feb 2006) 44% 55% 56%

Test 2 (Feb 2007) 42% 53% 48%

Test 3 (Jan 2008) 50% 59% 62%

Test 4 (Feb 2009) 41% 63% 67%

Test 5 (Nov 2009) 70% 81% 80%

Test 6 (Nov 2010) 55% 73% 73%

Test 7 (Nov 2011) 62% 80% 79%

Test 8 (Nov 2012) 55% 75% 76%

Test 9 (Nov 2013) 66% 78% 79%

Table 5: Comparison of participation (States & MWOs) in SIGMET Tests 1-9

SIGMET

Test 1-9

RODB

Reception

Bangkok

RODB

Brisbane

RODB

Singapore

RODB

Tokyo

RODB

Nadi

RODB

Test 1

(Feb 2006) 75% 45% 90% 80% 85%

Test 2

(Feb 2007) 84% 68% 90% 94% 84%

Test 3

(Jan 2008) 91% 76% 95% 100% 92%

Test 4

(Feb 2009) 93% 86% 93% 100% 93%

Test 5

(Nov 2009) 90% 82% 90% 98% 90%

Test 6

(Nov 2010) 90% 87% 98% 100% 98% 67%

Test 7

(Nov 2011) 89% 84% 90% 100% 94% 76%

Test 8

(Nov 2012) 91% 92% 94% 100% 79% 90%

Test 9

(Nov 2013) 98% 96% 98% 100% 100% 96%

Table 6: RODB Reception of SIGMET Test 1-9

ROBEX WG/12


C4 - 3

State, MWOs (FIR) DTG (YYGGgg) Received DTG

French Polynesia,

TAHITI/Faaa

260200

Invalid DTG : 260128

(Time received: 26/0200)

Message content:

GG WSSSYMYX

260200 NTAAYMYX

WSPF21 NTAA 260128

NTTT SIGMET Z99 VALID 260200/260210 NTAA-

NTTT TAHITI FIR THIS IS A TEST SIGMET,

PLEASE DISREGARD =

Table 7: Test SIGMET message errors – invalid date/time group (DTG) in the WMO Heading

MWO Location FIR Priority Message Content

TAHITI/Faaa NTTT GG

GG WSSSYMYX

260200 NTAAYMYX

WSPF21 NTAA 260128

NTTT SIGMET Z99 VALID 260200/260210

NTAA-

NTTT TAHITI FIR THIS IS A TEST

SIGMET, PLEASE DISREGARD

LAHORE/Allama Iqbal Intl OPLR GG

GG WSSSYMYX

260205 OPLAYFYX

WSPK31 OPLA 260205

OPLR SIGMET Z99 VALID 260205/260215

OPLA-

THIS IS A TEST SIGMET. PLEASE

DIREGARD (.)

TEST WS ADVISORY NUMBER 01

RECEIVED AT 260200Z=

KARACHI/Jinnah Intl

OPKR

GG

GG WSSSYMYX

260158 OPKCYMYA

WSPK31 OPKC 260200

OPKC SIGMET Z99 VALID

260200/260210 OPKC-

THIS IS A TEST SIGMET, PLEASE

DISREGARD=

MALE/Intl VRMF DD

DD WSSSYMYX

260200 VRMMYMYX

WSMV31 VRMM 260200

VRMF SIGMET Z99 VALID

260200/260210 VRMM-

THIS IS A TEST SIGMET,PLEASE

DISREGARD=

ADELAIDE/Adelaide

BRISBANE/Brisbane

DARWIN/Darwin

HOBART/Hobart

MELBOURNE/Melbourne

MELBOURNE/World Met.

YMMM

YBBB

DD

GG

GG WSSSYMYX

260159 YPRFYMYX

WSAU21 APRF 260159

YBBB SIGMET Z99 VALID

260200/260210 YPRF -

YBBB BRISBANE FIR THIS IS A TEST

ROBEX WG/12


C4 - 4

Centre

PERTH/Perth

SYDNEY/Sydney

SIGMET PLEASE DISREGARD=

GG WSSSYMYX

260200 YSRFYMYX

WSAU21 ASRF 260159


260200/260210 YSRF -

GG WSSSYMYX

260200 YMMCYMYX

WSAU21 AMMC 260201


260220/260230 YMMC-

THIS IS A TEST SIGMET PLEASE

DISREGARD=

DD WSSSYMYX

260204 YMRFYMYX

WSAU21 AMRF 260204


260205/260215 YMRF -

YBBB BRISBANE FIR THIS IS A TEST

SIGMET PLEASE DISREGARD=

DD WSSSYMYX

260217 YPRMYMYX

WSAU21 APRM 260217

YMMM SIGMET C01 VALID

260215/260225 YPRM -

YMMM MELBOURNE FIR THIS IS A

TEST SIGMET PLEASE DISREGARD=

SHANGHAI/Hongqiao ZSHA DD

GG WSSSYMYX

260159 ZSSSYMYX

WSCI34 ZSSS 260205

ZSHA SIGMET Z99 VALID 260205/260215

ZSSS-

THIS IS A TEST SIGMET, PLEASE

DISREGARD=

URUMQI/Diwopu

ZWUQ

GG

GG WSSSYMYX

260202 ZWWWYZYX

WSCI39 ZWWW 260201

ZWUQ SIGMET Z99 VALID

260205/260215 ZWWW-


DISREGARD=

WUHAN/Tianhe

ZHWH GG

GG WSSSYMYX

260200 ZHHHYMYX

WSCI45 ZHHH 260205

ZHWH SIGMET Z99 VALID

260205/260210 ZHHH-


DISREGARD=

ROBEX WG/12


C4 - 5

Table 8: Test SIGMET message errors – incorrect priority group

MWO Location MWO Incorrect

Sequence No.

Message Content

HONOLULU/Honolulu

Intl PHFO

NOVEMBER

1

WSPA01 PHFO 260200

SIGPAN

KZAK SIGMET NOVEMBER 1 VALID

260200/260215 PHFO-

OAKLAND OCEANIC FIR. THIS IS A TEST

SIGMET. PLEASE DISREGARD.

Table 9: Test SIGMET message errors – incorrect sequence number

Invalid FIR Identifier Karachi FIR &

SRR

GG WSSSYMYX

260158 OPKCYMYA

WSPK31 OPKC 260200

OPKC SIGMET Z99 VALID 260200/260210 OPKC-

THIS IS A TEST SIGMET, PLEASE DISREGARD=

Table 10: Test SIGMET message errors – invalid FIR code

ROBEX WG/12


C4 - 6

Area Served

Location MWO Name TTAAii CCCC FIR Priority TTAAii CCCC YYGGgg MWO FIR / UIR VTBB YBBN WSSS RJTD NFFN Remarks

Afghanistan KABUL AD OAKB Kabul FIR and SSR WSAH31 OAKB OAKX Not in Asia/Pac Region

Australia ADELAIDE/Adelaide YPRM Melbourne FIR WSAU21 APRM YMMM DD WSAU21 APRM 260217 APRM YMMM 02:18 02:17 02:18 02:18 02:17

BRISBANE/Brisbane YBRF Brisbane FIR WSAU21 ABRF YBBB GG WSAU21 ABRF 260201 ABRF YBBB 02:04 02:01 02:05 02:04 02:01

BRISBANE/Brisbane YBRF Melbourne FIR WSAU21 ABRF YMMM FF WSAU21 ABRF 260211 ABRF YMMM 02:12 02:11 02:12 02:12 02:11

CAIRNS/Cairns Intl YBCS Brisbane FIR WSAU21 ABCS YBBB

DARWIN/Darw in YPDM Brisbane FIR WSAU21 ADRM YBBB GG WSAU21 ADRM 260202 ADRM YBBB 02:05 02:02 02:05 02:05 02:02

DARWIN/Darw in YPDM Melbourne FIR WSAU21 ADRM YMMM GG WSAU21 ADRM 260203 ADRM YMMM 02:06 02:03 02:07 02:06 02:03

HOBART/Hobart YMHF Melbourne FIR WSAU21 AMHF YMMM GG WSAU21 AMHF 260201 AMHF YMMM 02:04 02:01 02:04 02:04 02:01

MELBOURNE/Melbourne YMRF Brisbane FIR WSAU21 AMRF YBBB DD WSAU21 AMRF 260204 AMRF YBBB 02:05 02:04 02:06 02:06 02:04

MELBOURNE/Melbourne YMRF Melbourne FIR WSAU21 AMRF YMMM DD WSAU21 AMRF 260205 AMRF YMMM 02:06 02:05 02:06 02:07 02:05

MELBOURNE/World Met. Centre YMMC Brisbane FIR WSAU21 AMMC YBBB GG WSAU21 AMMC 260201 AMMC YBBB 02:03 02:00 02:03 02:03 02:00

MELBOURNE/World Met. Centre YMMC Melbourne FIR WSAU21 AMMC YMMM GG WSAU21 AMMC 260201 AMMC YMMM 02:03 02:00 02:04 02:03 02:00

PERTH/Perth YPRF Brisbane FIR WSAU21 APRF YBBB GG WSAU21 APRF 260159 APRF YBBB 02:02 01:59 02:02 02:02 01:59

PERTH/Perth YPRF Melbourne FIR WSAU21 APRF YMMM GG WSAU21 APRF 260159 APRF YMMM 02:00 01:59 02:00 02:00 01:59

SYDNEY/Sydney YSRF Brisbane FIR WSAU21 ASRF YBBB GG WSAU21 ASRF 260159 ASRF YBBB 02:02 01:59 02:03 02:02 01:59

SYDNEY/Sydney YSRF Melbourne FIR WSAU21 ASRF YMMM GG WSAU21 ASRF 260159 ASRF YMMM 02:01 02:00 02:01 02:01 02:00

Bangladesh DHAKA/Zia Intl VGHS Dhaka FIR & SRR WSBW20 VGHS VGFR FF WSBW20 VGHS 260200 VGHS VGFR 01:59 02:00 01:59 02:03 02:00

Cambodia CHENGDU/Shuangliu for PHNOM-PENH (VDPP) ZUUU Phnom-Penh FIR & SRR WSKP31 ZUUU VDPP FF WSKP31 ZUUU 260204 ZUUU VDPP 02:04 02:02 02:04 02:04 02:02

China BEIJING/Capital ZBAA Beijing FIR & SRR WSCI33 ZBAA ZBPE FF WSCI33 ZBAA 260205 ZBAA ZBPE 02:01 02:01 02:01 02:01 02:00

GUANGZHOU/Baiyan ZGGG Guangzhou FIR & SRR WSCI35 ZGGG ZGZU FF WSCI35 ZGGG 260205 ZGGG ZGZU 02:00 02:00 02:01 02:01 02:00

CHENGDU/Shuangliu ZUUU Kunming FIR & SRR WSCI36 ZUUU ZPKM FF WSCI36 ZUUU 260202 ZUUU ZPKM 02:02 02:01 02:02 02:02 02:01

XI'AN/Xianyang ZLXY Lanzhou FIR and SRR WSCI37 ZLXY ZLHW FF WSCI37 ZLXY 260203 ZLXY ZLHW 02:01 02:02 02:04 02:04 02:02

HAIKOU/Meilan ZJHK Sanya FIR & SRR WSCI35 ZJHK ZJSA FF WSCI35 ZJHK 260210 ZJHK ZJSA 02:25 02:41 02:25 02:25 02:41

SHANGHAI/Hongqiao ZSSS Shanghai FIR & SRR WSCI34 ZSSS ZSHA GG WSCI34 ZSSS 260205 ZSSS ZSHA 02:00 01:59 02:00 02:00 01:59

SHENYANG/Taoxian ZYTX Shenyang FIR & SRR WSCI38 ZYTX ZYSH FF WSCI38 ZYTX 260205 ZYTX ZYSH 02:01 02:00 02:01 02:01 02:01

TAIBEI/Taibei Intl RCTP Taibei FIR & SRR WSCI31 RCTP RCAA FF WSCI31 RCTP 260200 RCTP RCAA 02:00 02:00 02:01 02:00 02:00

URUMQI/Diw opu ZWWW Urumqi FIR & SRR WSCI39 ZWWW ZWUQ GG WSCI39 ZWWW 260201 ZWWW ZWUQ 02:01 02:02 02:01 02:01 02:02

WUHAN/Tianhe ZHHH Wuhan FIR & SRR WSCI45 ZHHH ZHWH GG WSCI45 ZHHH 260205 ZHHH ZHWH 02:01 02:00 02:07 02:01 02:00

HONG KONG/Hong Kong Intl VHHH Hong Kong FIR & SRR WSSS20 VHHH VHHK FF WSSS20 VHHH 260200 VHHH VHHF 02:01 02:00 02:01 02:01 02:00

DPR Korea SUNAN ZKPY Pyongyang FIR & SRR WSKR31 ZKPY ZKKP

Fiji NADI/Nadi Intl NFFN Nadi FIR & SRR WSFJ01,02.. NFFN NFFF 02:57/current

French Polynesia TAHITI/Faaa NTAA Tahiti FIR & SRR WSPF21,22 NTAA NTTT GG WSPF21 NTAA 260128 NTAA NTTT 02:00 02:00 02:00 02:00 02:00 incorrect DTG

India CHENNAI/Chennai VOMM Chennai FIR & SRR WSIN31 VOMM VOMF FF WSIN31 VOMM 260205 VOMM VOMF 02:06 02:04 02:06 02:06 02:04

DELHI/Indira Ghandi Intl VIDP Delhi FIR & SRR WSIN31 VIDP VIDF FF WSIN31 VIDP 260206 VIDP VIDF 02:05 02:03 02:05 02:07 02:03

KOLKATA VECC Kolkata FIR & SRR WSIN31 VECC VECF FF WSIN31 VECC 260205 VECC VECF 02:05 02:05 02:06 02:07 02:05

MUMBAI/Chhatrapati Shivaji Intl. VABB Mumbai FIR & SRR WSIN31 VABB VABF FF WSIN31 VABB 260205 VABB VABF 01:55 02:01 01:56 02:02 02:01

Indonesia JAKARTA/Soekamo-Hatta WIII Jakarta FIR/UIR & SRR WSID20 WIII WIIF FF WSID20 WIII 260210 WIII WIIF 02:08 02:05 02:18 02:08 02:05

UJUNG PANDANG/Hasanuddin WAAA Ujung Pandang FIR/UIR & SRR WSID21 WAAA WAAF FF WSID21 WAAA 260229 WAAA WAAF 02:26 02:26 02:33

Japan TOKYO (CITY) RJTD Fukuoka FIR & Tokyo SRR WSJP31 RJTD RJJJ FF WSJP31 RJTD 260205 RJTD RJJJ 02:05 02:05 02:05 02:05 02:05

Lao PDR VIENTIANE/Wattay VLVT Vientiane FIR & SRR WSLA31 VLVT VLVT

Malaysia SEPANG/KL International Airport WMKK Kota Kimabalu FIR & SRR WSMS31 WMKK WBFC FF WSMS31 WMKK 260200 WMKK WBFC 02:00 02:00 02:00 02:01 02:00

SEPANG/KL International Airport WMKK Kuala Lumpur FIR & SRR WSMS31 WMKK WMFC FF WSMS31 WMKK 260200 WMKK WMKC 02:02 02:02 02:02 02:02 02:01

Maldives MALE/Intl VRMM Male FIR & SRR WSMV31 VRMM VRMF DD WSMV31 VRMM 260200 VRMM VRMF 02:00 02:00 02:00 02:00 02:00

Mongolia ULAANBAATAR ZMUB Ulaanbaatar FIR & SRR WSMO31 ZMUB ZMUB

Myanmar YANGON/Yangon International VYYY Yangon FIR & SRR WSBM31 VYYY VYYY

Nauru PORT MORESBY on behalf of NAURU (ANYN) AYPY Nauru FIR & SRR WSNW20 AYPY ANAU

Nepal KATHMANDU VNKT Kathmandu FIR & SRR WSNP31 VNKT VNSM FF WSNP31 VNKT 260205 VNKT VNSM 02:05 02:05 02:05 02:05 02:05

New Zealand WELLINGTON (Aviation Weather Centre) NZKL New Zealand FIR & SRR WSNZ21 NZKL NZZC FF WSNZ21 NZKL 260219 NZKL NZZC 02:20 02:19 02:20 02:20 02:19

WELLINGTON (Aviation Weather Centre) NZKL Auckland Oceanic FIR & SRR WSPS21 NZKL NZZO FF WSPS21 NZKL 260220 NZKL NZZO 02:20 02:20 02:20 02:20 02:20

Pakistan KARACHI/Jinnah Intl OPKC Karachi FIR & SRR WSPK31 OPKC OPKR GG WSPK31 OPKC 260200 OPKC OPKC 01:58 01:58 01:58 02:08 01:58 incorrect FIR ID

LAHORE/Allama Iqbal Intl OPLA Lahore Fir & SRR WSPK31 OPLA OPLR GG WSPK31 OPLA 260205 OPLA OPLR 02:05 02:05 02:06 02:19 02:05

Papua New Guinea PORT MORESBY/Intl AYPY Port Moresby FIR & SRR WSNG20 AYPY AYPY

Phillippines MANILA/Ninoy Aquino Intl, Pasay City, Metro Manila RPLL Manila FIR & SRR WSPH31 RPLL RPHI FF WSPH31 RPLL 260201 RPLL RPHI 02:01 02:01 02:02 02:01 02:01

Republic of Korea INCHEON RKSI Incheon FIR & SRR WSKO31 RKSI RKRR FF WSKO31 RKSS 260203 RKSS RKSI 02:03 02:03 02:04 02:03 02:03

Singapore SINGAPORE/Changi WSSS Singapore FIR & SRR WSSR20 WSSS WSJC FF WSSR20 WSSS 260205 WSSS WSJC 02:05 02:05 02:05 02:05 02:05

Solomon Islands PORT MORESBY on behalf of HONIARA (Henderson - AGGH) AYPY Honiara FIR & SRR WSSO20 AYPY AGGG

Sri Lanka COLOMBO/Bandaranaike Intl Airport Colombo VCBI Colombo FIR & SRR WSSB31 VCBI VCBI

Thailand BANGKOK/Suvamabhumi Intl Airport VTBS Bangkok FIR & SRR WSTH31 VTBS VTBB FF WSTH31 VTBS 260230 VTBS VTBB 02:32 02:34 02:32 02:32 02:34

United States ANCHORAGE/Anchorage Intl PAWU Anchorage FIR WSAK01-09 PAWU PAZA

HONOLULU/Honolulu Intl PHFO Oakland Oceanic & Honolulu SRR WSPA01-13 PHFO KZAK FF WSPA01 PHFO 260200 PHFO KZAK 02:03 02:00

KANSAS CITY KKCI Oakland Oceanic FIR WSPN01-13 KKCI KZAK 02:15/current

Vietnam Gia Lam VVGL Hanoi FIR & SRR WSVS31 VVGL VVNB FF WSVS31 VVGL 260201 VVGL VVNB 02:03 01:59 02:03 02:03 01:59

Gia Lam VVGL Ho-Chi-Minh FIR & SRR WSVS31 VVGL VVTS FF WSVS31 VVGL 260200 VVGL VVTS 02:02 01:58 02:02 02:02 01:58

StateMeteorological Watch Office (MWO) SIGMET Guide Transmitted Header RODB Reception

Table 11: Summary of test WS SIGMET messages received at RODBs

ROBEX WG/12


C4 - 7

Area Served

Location MWO Name TTAAii CCCC FIR Priority TTAAii CCCC YYGGgg MWO FIR / UIR LOWM LFPW EGGY EHDB EBBR Remarks

Afghanistan KABUL AD OAKB Kabul FIR and SSR WSAH31 OAKB OAKX Not in Asia/Pac Region

Australia ADELAIDE/Adelaide YPRM Melbourne FIR WSAU21 APRM YMMM DD WSAU21 APRM 260217 APRM YMMM 02:18 02:18 02:18 02:18 02:18

BRISBANE/Brisbane YBRF Brisbane FIR WSAU21 ABRF YBBB GG WSAU21 ABRF 260201 ABRF YBBB 02:05 02:05 02:05 02:05

BRISBANE/Brisbane YBRF Melbourne FIR WSAU21 ABRF YMMM FF WSAU21 ABRF 260211 ABRF YMMM 02:12 02:12 02:12 02:12

CAIRNS/Cairns Intl YBCS Brisbane FIR WSAU21 ABCS YBBB

DARWIN/Darw in YPDM Brisbane FIR WSAU21 ADRM YBBB GG WSAU21 ADRM 260202 ADRM YBBB 02:05 02:05 02:05 02:05

DARWIN/Darw in YPDM Melbourne FIR WSAU21 ADRM YMMM GG WSAU21 ADRM 260203 ADRM YMMM 02:07 02:05 02:05 02:05

HOBART/Hobart YMHF Melbourne FIR WSAU21 AMHF YMMM GG WSAU21 AMHF 260201 AMHF YMMM 02:04 02:04 02:04 02:04

MELBOURNE/Melbourne YMRF Brisbane FIR WSAU21 AMRF YBBB DD WSAU21 AMRF 260204 AMRF YBBB 02:06 02:06 02:06 02:06 02:06

MELBOURNE/Melbourne YMRF Melbourne FIR WSAU21 AMRF YMMM DD WSAU21 AMRF 260205 AMRF YMMM 02:06 02:06 02:06 02:07 02:06

MELBOURNE/World Met. Centre YMMC Brisbane FIR WSAU21 AMMC YBBB GG WSAU21 AMMC 260201 AMMC YBBB 02:03 02:04 02:03 02:04 02:03

MELBOURNE/World Met. Centre YMMC Melbourne FIR WSAU21 AMMC YMMM GG WSAU21 AMMC 260201 AMMC YMMM 02:03 02:04 02:03 02:05 02:03

PERTH/Perth YPRF Brisbane FIR WSAU21 APRF YBBB GG WSAU21 APRF 260159 APRF YBBB 02:00 02:00 02:00 02:03 02:00

PERTH/Perth YPRF Melbourne FIR WSAU21 APRF YMMM GG WSAU21 APRF 260159 APRF YMMM 02:02 02:02 02:02 02:01 02:02

SYDNEY/Sydney YSRF Brisbane FIR WSAU21 ASRF YBBB GG WSAU21 ASRF 260159 ASRF YBBB 02:01 02:03 02:01 02:01 02:01

SYDNEY/Sydney YSRF Melbourne FIR WSAU21 ASRF YMMM GG WSAU21 ASRF 260159 ASRF YMMM 02:03 02:03 02:01 02:04 02:01

Bangladesh DHAKA/Zia Intl VGHS Dhaka FIR & SRR WSBW20 VGHS VGFR FF WSBW20 VGHS 260200 VGHS VGFR 01:59 01:59 01:59 01:59

Cambodia CHENGDU/Shuangliu for PHNOM-PENH (VDPP) ZUUU Phnom-Penh FIR & SRR WSKP31 ZUUU VDPP FF WSKP31 ZUUU 260204 ZUUU VDPP 02:04 02:04 02:04 02:05 02:04

China BEIJING/Capital ZBAA Beijing FIR & SRR WSCI33 ZBAA ZBPE FF WSCI33 ZBAA 260205 ZBAA ZBPE 02:01 02:01 02:01 02:02 02:01

GUANGZHOU/Baiyan ZGGG Guangzhou FIR & SRR WSCI35 ZGGG ZGZU FF WSCI35 ZGGG 260205 ZGGG ZGZU 02:01 02:01 02:01 02:01 02:01

CHENGDU/Shuangliu ZUUU Kunming FIR & SRR WSCI36 ZUUU ZPKM FF WSCI36 ZUUU 260202 ZUUU ZPKM 02:02 02:01 02:02 02:03 02:02

XI'AN/Xianyang ZLXY Lanzhou FIR and SRR WSCI37 ZLXY ZLHW FF WSCI37 ZLXY 260203 ZLXY ZLHW 02:04

HAIKOU/Meilan ZJHK Sanya FIR & SRR WSCI35 ZJHK ZJSA FF WSCI35 ZJHK 260210 ZJHK ZJSA 02:43 02:43 02:25 02:25 02:25

SHANGHAI/Hongqiao ZSSS Shanghai FIR & SRR WSCI34 ZSSS ZSHA GG WSCI34 ZSSS 260205 ZSSS ZSHA 02:00 02:01 02:00 02:00 02:00

SHENYANG/Taoxian ZYTX Shenyang FIR & SRR WSCI38 ZYTX ZYSH FF WSCI38 ZYTX 260205 ZYTX ZYSH 02:00 02:01 02:01 02:01

TAIBEI/Taibei Intl RCTP Taibei FIR & SRR WSCI31 RCTP RCAA FF WSCI31 RCTP 260200 RCTP RCAA 02:01 02:01 02:01 02:01 02:01

URUMQI/Diw opu ZWWW Urumqi FIR & SRR WSCI39 ZWWW ZWUQ GG WSCI39 ZWWW 260201 ZWWW ZWUQ 02:01 02:01 02:01 02:01 02:01

WUHAN/Tianhe ZHHH Wuhan FIR & SRR WSCI45 ZHHH ZHWH GG WSCI45 ZHHH 260205 ZHHH ZHWH 02:04 02:04 02:04 02:04

HONG KONG/Hong Kong Intl VHHH Hong Kong FIR & SRR WSSS20 VHHH VHHK FF WSSS20 VHHH 260200 VHHH VHHF 02:01 02:01 02:01 02:01 02:01

DPR Korea SUNAN ZKPY Pyongyang FIR & SRR WSKR31 ZKPY ZKKP

Fiji NADI/Nadi Intl NFFN Nadi FIR & SRR WSFJ01,02.. NFFN NFFF FF WSFJ03 NFFN 260000 NFFN NFFF 02:57/current,

French Polynesia TAHITI/Faaa NTAA Tahiti FIR & SRR WSPF21,22 NTAA NTTT GG WSPF21 NTAA 260128 NTAA NTTT 02:00 02:00 02:02 incorrect DTG

India CHENNAI/Chennai VOMM Chennai FIR & SRR WSIN31 VOMM VOMF FF WSIN31 VOMM 260205 VOMM VOMF 02:06 02:08 02:06 02:06 02:06

DELHI/Indira Ghandi Intl VIDP Delhi FIR & SRR WSIN31 VIDP VIDF FF WSIN31 VIDP 260206 VIDP VIDF 02:04 02:04 02:04 02:04 02:04

KOLKATA VECC Kolkata FIR & SRR WSIN31 VECC VECF FF WSIN31 VECC 260205 VECC VECF 02:05 01:33 02:05 02:06 01:33

MUMBAI/Chhatrapati Shivaji Intl. VABB Mumbai FIR & SRR WSIN31 VABB VABF FF WSIN31 VABB 260205 VABB VABF 01:55 01:55 01:55 01:55 01:55

Indonesia JAKARTA/Soekamo-Hatta WIII Jakarta FIR/UIR & SRR WSID20 WIII WIIF FF WSID20 WIII 260210 WIII WIIF 04:45 04:55 02:08 01:01 01:01

UJUNG PANDANG/Hasanuddin WAAA Ujung Pandang FIR/UIR & SRR WSID21 WAAA WAAF FF WSID21 WAAA 260229 WAAA WAAF

Japan TOKYO (CITY) RJTD Fukuoka FIR & Tokyo SRR WSJP31 RJTD RJJJ FF WSJP31 RJTD 260205 RJTD RJJJ 02:05 02:05 02:05 02:05 02:05

Lao PDR VIENTIANE/Wattay VLVT Vientiane FIR & SRR WSLA31 VLVT VLVT

Malaysia SEPANG/KL International Airport WMKK Kota Kimabalu FIR & SRR WSMS31 WMKK WBFC FF WSMS31 WMKK 260200 WMKK WBFC 02:00 02:00 02:00 02:01 02:00

SEPANG/KL International Airport WMKK Kuala Lumpur FIR & SRR WSMS31 WMKK WMFC FF WSMS31 WMKK 260200 WMKK WMKC 02:02 02:02 02:02 02:02

Maldives MALE/Intl VRMM Male FIR & SRR WSMV31 VRMM VRMF DD WSMV31 VRMM 260200 VRMM VRMF 02:00 02:00 02:00 02:01 02:00

Mongolia ULAANBAATAR ZMUB Ulaanbaatar FIR & SRR WSMO31 ZMUB ZMUB

Myanmar YANGON/Yangon International VYYY Yangon FIR & SRR WSBM31 VYYY VYYY

Nauru PORT MORESBY on behalf of NAURU (ANYN) AYPY Nauru FIR & SRR WSNW20 AYPY ANAU

Nepal KATHMANDU VNKT Kathmandu FIR & SRR WSNP31 VNKT VNSM FF WSNP31 VNKT 260205 VNKT VNSM 02:05 02:05

New Zealand WELLINGTON (Aviation Weather Centre) NZKL New Zealand FIR & SRR WSNZ21 NZKL NZZC FF WSNZ21 NZKL 260219 NZKL NZZC 02:19 02:19 02:19 02:20 02:19

WELLINGTON (Aviation Weather Centre) NZKL Auckland Oceanic FIR & SRR WSPS21 NZKL NZZO FF WSPS21 NZKL 260220 NZKL NZZO 02:02 02:20 02:20 02:20 02:20

Pakistan KARACHI/Jinnah Intl OPKC Karachi FIR & SRR WSPK31 OPKC OPKR GG WSPK31 OPKC 260200 OPKC OPKC 01:58 incorrect FIR ID

LAHORE/Allama Iqbal Intl OPLA Lahore Fir & SRR WSPK31 OPLA OPLR GG WSPK31 OPLA 260205 OPLA OPLR 02:05 02:05 02:05 02:06 02:05

Papua New Guinea PORT MORESBY/Intl AYPY Port Moresby FIR & SRR WSNG20 AYPY AYPY

Phillippines MANILA/Ninoy Aquino Intl, Pasay City, Metro Manila RPLL Manila FIR & SRR WSPH31 RPLL RPHI FF WSPH31 RPLL 260201 RPLL RPHI 02:02 02;05 02:02 02:02

Republic of Korea INCHEON RKSI Incheon FIR & SRR WSKO31 RKSI RKRR FF WSKO31 RKSS 260203 RKSS RKSI 02:03 02:03 02:03 02:04 02:03

Singapore SINGAPORE/Changi WSSS Singapore FIR & SRR WSSR20 WSSS WSJC FF WSSR20 WSSS 260205 WSSS WSJC 02:05 02:05 02:05 02:05 02:05

Solomon Islands PORT MORESBY on behalf of HONIARA (Henderson - AGGH) AYPY Honiara FIR & SRR WSSO20 AYPY AGGG

Sri Lanka COLOMBO/Bandaranaike Intl Airport Colombo VCBI Colombo FIR & SRR WSSB31 VCBI VCBI

Thailand BANGKOK/Suvamabhumi Intl Airport VTBS Bangkok FIR & SRR WSTH31 VTBS VTBB FF WSTH31 VTBS 260230 VTBS VTBB 02:32 02:32 02:32 02:33 02:32

United States ANCHORAGE/Anchorage Intl PAWU Anchorage FIR WSAK01-09 PAWU PAZA

HONOLULU/Honolulu Intl PHFO Oakland Oceanic & Honolulu SRR WSPA01-13 PHFO KZAK FF WSPA01 PHFO 260200 PHFO KZAK 02:11 02:11 02:03 02:11 02:03

KANSAS CITY KKCI Oakland Oceanic FIR WSPN01-13 KKCI KZAK FF WSPN02 KKCI 260215 KKCI KZAK 02:15/current

Vietnam Gia Lam VVGL Hanoi FIR & SRR WSVS31 VVGL VVNB FF WSVS31 VVGL 260201 VVGL VVNB 02:02 02:03 02:03

Gia Lam VVGL Ho-Chi-Minh FIR & SRR WSVS31 VVGL VVTS FF WSVS31 VVGL 260200 VVGL VVTS 02:03 02:02 02:02 02:03 02:03

StateMeteorological Watch Office (MWO) SIGMET Guide Transmitted Header EUR ROC, RODB & SADIS Reception

Table 12: Summary of test WS SIGMET messages received at EUR ROC, RODB and SADIS

ROBEX WG/12


(66 pages) i

INTERNATIONAL CIVIL AVIATION ORGANIZATION

ASIA/PACIFIC REGIONAL SIGMET GUIDE

FIFTH EDITION ― <<INSERT MONTH AND YEAR>>

(ii)

RECORD OF AMENDMENTS AND CORRIGENDA

Amendments Corrigenda

No. Date of

issue

Date

entered Entered by No.

Date of

issue

Date

entered Entered by

— — — — — — — —

(iii)

TABLE OF CONTENTS

Page

Part 1: Introduction

1.1 General............................................................................................................................... 1-1

Part 2: Responsibilities and coordination

2.1 General............................................................................................................................... 2-1

2.2 Meteorological watch office (MWO) responsibilities ...................................................... 2-1

2.3 Air traffic services (ATS) unit responsibilities .................................................................. 2-3

2.4 Pilot responsibilities .......................................................................................................... 2-3

2.5 Coordination between MWOs and ATS units ................................................................... 2-4

2.6 Coordination between MWOs, VAACs, TCACs and State volcano observatories........... 2-4

Part 3: Procedures for preparation of SIGMET information

3.1 General............................................................................................................................... 3-1

3.2 SIGMET phenomena ......................................................................................................... 3-1

3.3 Allowable abbreviations .................................................................................................... 3-2

3.4 SIGMET structure ............................................................................................................. 3-3

3.5 SIGMET format ................................................................................................................. 3-3

3.5.1 WMO header ........................................................................................................ 3-4

3.5.2 First line of SIGMET ............................................................................................ 3-4

3.5.3 Structure of the meteorological part of SIGMET for weather phenomena other than

for volcanic ash and tropical cyclone ................................................................... 3-5

3.5.4 Structure of the meteorological part of SIGMET for volcanic ash ....................... 3-13

3.5.5 Structure of the meteorological part of SIGMET for tropical cyclone ................. 3-19

3.5.6 Cancellation of SIGMET ...................................................................................... 3-21

3.5.7 Amendment of SIGMET ...................................................................................... 3-22

3.6 Dissemination of SIGMET ................................................................................................ 3-23

Appendices

Appendix A — SIGMET guidance table: Simplified from Annex 3 Table A6-1 ................... A-1

Appendix B — SIGMET examples ......................................................................................... B-1

Appendix C — SIGMET test procedures ……………………………………... .................... C-1

— — — — — — — —

1-1

1. INTRODUCTION

1.1. General

1.1.1. The main purpose of this regional SIGMET guide is to provide guidance for

standardization and harmonization of the procedures and formats related to the

preparation and issuance of aeronautical meteorological information pertaining to

specified en-route hazardous weather phenomena, known as SIGMET. The guidance

is complementary to Annex 3 to the Convention on International Civil Aviation –

Meteorological Services for International Air Navigation, the Standards and

Recommended Practices (SARPs) contained therein regarding SIGMET, and to the

SIGMET-related provisions in ICAO Regional Air Navigation Plans (ANPs).

1.1.2. ICAO provisions concerning the preparation and issuance of SIGMET information

are primarily contained in:

Annex 3 - Meteorological Service for International Air Navigation, Part I,

Chapters 3 and 7 and Part II, Appendix 6;

Annex 11 - Air Traffic Services, Chapter 4, 4.2.1 and Chapter 7, 7.1;

Regional Air Navigation Plans, Basic ANP, Part VI - Meteorology (MET);

Regional Air Navigation Plans, Volume II, FASID, Part VI – Meteorology

(MET) FASID, Tables MET 1B, MET 3A and MET 3B;

Procedures for Air Navigation Services – Air Traffic Management (PANS-

MET, Doc 4444), Chapter 9, 9.1.3.2;

Regional Supplementary Procedures (Doc 7030), Part 1, 11.2;

ICAO Abbreviations and Codes (Doc 8400);

Handbook on the International Airways Volcano Watch (IAVW) –

Operational Procedures and Contact List (Doc 9766);

Manual of Aeronautical Meteorological Practice (Doc 8896), Chapters 1 and

4;

Manual on Coordination between Air Traffic Services, Aeronautical

Information Services and Aeronautical Meteorological Services (Doc 9377).

1.1.3. This regional SIGMET guide is primarily intended to assist meteorological watch

offices (MWOs) in preparing and disseminating SIGMET information in

conformance with the format prescribed in Annex 3. The explanations of the format

to be used are accompanied by examples. The regional SIGMET guide also provides

information regarding the necessary coordination between the MWOs, air traffic

services (ATS), volcanic ash advisory centres (VAACs), tropical cyclone advisory

centres (TCACs) and pilots, and their respective responsibilities.

——————

2-1

2. RESPONSIBILITIES AND COORDINATION

2.1. General

2.1.1. SIGMET messages provide information on hazardous meteorological phenomena;

hence they are considered a high priority among other types of meteorological

information provided to the aviation users. The primary purpose of SIGMET is for in-

flight service, which requires timely transmission of the SIGMET messages to pilots

by the ATS units and/or through VOLMET and D-VOLMET. Further information on

the responsibilities of each party involved in the SIGMET process can be found in the

Manual on Coordination between Air Traffic Services, Aeronautical Information

Services and Aeronautical Meteorological Services (Doc 9377).

2.1.2. Airlines are the main users of the SIGMET information. They contribute to the

effectiveness of the SIGMET service through issuance of special air-reports reported

by pilots to the ATS units. Special air-reports are among the most valuable sources of

information for the MWOs in the preparation of SIGMET. The ATS units receiving

special air-reports should forward them to their associated MWOs without delay.

2.1.3. In view of the foregoing, it should be well understood that the effectiveness of the

SIGMET service depends strongly on the level of collaboration between the MWOs,

ATS units, pilots, TCACs, VAACs and State volcano observatories. That is why,

close coordination between these parties, as well as mutual understanding of their

needs and responsibilities are essential for the successful implementation of the

SIGMET service.

2.1.4. For the special cases of SIGMET for volcanic ash and tropical cyclones, the MWOs

are provided with advisories from VAACs and TCACs respectively, as designated in

the regional ANPs.

2.1.5. SIGMET is also used for flight planning. This requires global dissemination of

SIGMET through the regional OPMET data banks (RODBs), the aeronautical fixed

service (AFS) satellite distribution system (SADIS 2G), the Internet-based Secure

SADIS FTP service and the WAFS Internet File Service (WIFS). SIGMET should

also be distributed to the World Area Forecast Centres (WAFCs) London and

Washington for use in the preparation of the significant weather (SIGWX) forecasts.

2.2. Meteorological watch office (MWO) responsibilities

2.2.1. SIGMET is to be issued by the MWO in order to provide timely information on the

occurrence or expected occurrence of specified en-route weather phenomena affecting

the safety of the flight operations in the MWO’s area of responsibility. SIGMET

provides information concerning the location, extent, intensity and expected evolution

of the specified phenomena.

2.2.2. Information about the provision of the SIGMET service, including details on the

designated MWO(s), is to be included in the State’s Aeronautical Information

Publication (AIP) as required by Annex 15 – Aeronautical Information Service,

Appendix 1, GEN 3.5.8.

2.2.3. If a State is temporarily unable to meet its obligations for establishing MWO(s) and

for provision of SIGMET, arrangements have to be made for another State to assume

this responsibility. Such delegation of responsibilities is to be agreed by the

meteorological authority of each State concerned and should be notified by a

NOTAM, within the State’s AIP and in a letter to the ICAO Regional Office

concerned.

2-2

2.2.4. The meteorological authority concerned should ensure that the MWO obligations and

responsibilities are clearly defined and assigned to the unit designated to serve the

MWO. Corresponding operational procedures should be established and the

meteorological staff should be trained accordingly.

2.2.5. In preparing SIGMET information MWOs should follow the format prescribed in

Annex 3, Appendix 6, Table A6-1. Whilst Table A6-1 is the authoritative source, this

regional SIGMET guide provides more specific instructions on how SIGMET should

be compiled. The aim is to ensure that SIGMET is produced reliably and consistently

worldwide.

2.2.6. SIGMET must be issued only for those weather phenomena listed in Annex 3,

Appendix 6, 1.1.4 and only when specified criteria for their intensity and spatial

extent are met.

2.2.7. The MWOs should be adequately equipped in order to be able to identify, analyze and

forecast those phenomena for which SIGMET is required. The MWO should make

use of all available sources of information including:

special air-reports passed to the MWO from ATS (voice communication);

special air-reports received from automated downlink;

numerical Weather Prediction (NWP) data, especially high resolution models

where available;

meteorological observations, including those from automatic weather stations

and human observers;

upper wind information;

information from meteorological satellites;

weather radar (including Doppler radar);

State volcano observatories;

International Atomic Energy Agency (IAEA) through the relevant World

Meteorological Organization (WMO) Regional Specializes Meteorological

Centre (RSMC) for radioactive cloud;

local knowledge;

volcanic ash or tropical cyclone advisory messages.

2.2.8. On receipt of a special air-report from the associated ACC or FIC, the MWO should:

a) issue SIGMET information based on the special-air report; or

b) send the special air-report for onward transmission in the case that the

issuance of SIGMET information is not warranted (e.g., the phenomenon

concerned is of transient nature).

2.2.9. Appropriate telecommunication means should be available at the MWO in order to

ensure timely dissemination of SIGMET according to a dissemination scheme, which

should include transmission to:

local ATS users;

aerodrome MET offices within its area of responsibility, where SIGMET is

required for briefing and/or flight documentation;

other MWOs in accordance with regional air navigation plans;

Centres designated for transmission of VOLMET or D-VOLMET where

SIGMET is required for those transmissions;

responsible ROBEX centres and regional OPMET data bank (RODB). It

should be arranged that, through the ROBEX scheme, SIGMETs are sent to

2-3

the designated RODB in the other ICAO regions, to the WAFCs and to the

SADIS and WIFS providers;

2.2.10. In issuing SIGMET for tropical cyclones or volcanic ash, the MWOs should include

as appropriate the advisory information received from the responsible TCAC or

VAAC. In addition to the information received from the TCAC and VAAC, the

MWOs may use the available complementary information from other reliable sources.

2.3. Air traffic service (ATS) unit responsibilities

2.3.1. Close coordination should be established between the MWO and the corresponding

ATS unit (ACC or FIC) and arrangements should be in place to ensure:

receipt without delay and display at the relevant ATS units of SIGMET

issued by the associated MWO;

receipt and display at the ATS unit of SIGMETs issued by MWOs

responsible for the adjacent FIRs/ACCs if these SIGMETs are required

according to 2.3.4 below; and

transmission without delay by the ATS unit of special air-reports received

through voice communication to the associated MWO.

2.3.2. SIGMET information should be transmitted to aircraft with the least possible delay on

the initiative of the responsible ATS unit, by the preferred method of direct

transmission followed by acknowledgement or by a general call when the number of

aircraft would render the preferred method impracticable.

2.3.3. SIGMET information transmitted to aircraft-in-flight should cover a portion of the

route up to two hours flying time ahead of the aircraft. SIGMET should be transmitted

only during the time corresponding to their period of validity.

2.3.4. Air traffic controllers should ascertain whether any of the currently valid SIGMETs

may affect any of the aircraft they are controlling, either within or outside the

FIR/CTA boundary, up to two hours flying time ahead of the current position of the

aircraft. If this is the case, the controllers should at their own initiative transmit the

SIGMET promptly to the aircraft-in-flight likely to be affected. If necessary, the

controller should pass to the aircraft available SIGMETs issued for the adjacent

FIR/CTA, which the aircraft will be entering, if relevant to the expected flight route.

2.3.5. The ATS units concerned should also transmit to aircraft-in-flight the special air

reports received, for which SIGMET has not been issued. Once a SIGMET for the

weather phenomenon reported in the special air report is made available this

obligation of the ATS unit expires.

2.4. Pilot responsibilities

2.4.1. Timely issuance of SIGMET information is largely dependent on the prompt receipt

by MWOs of special air-reports. It is essential that pilots prepare and transmit such

reports to the ATS units whenever any of the specified en-route meteorological

conditions are encountered or observed.

2.4.2. It should be emphasized that, even when automatic dependent surveillance (ADS) is

being used for routine air-reports, pilots should continue to make special air-reports.

2.4.3. Pilots should compile special air-reports and disseminate to ATS by air-ground data

link as per Annex 3, Appendix 4, 1.2 and Procedures for Air Navigation Services –

Air Traffic Management (PANS-ATM, Doc 4444), 4.12.3.2, or by voice

communication as per Annex 3, Appendix 4, 1.3 and PANS-ATM (Doc 4444),

4.12.3.3.

2-4

Note. ― The MWO will compile special air-reports for uplink as per Annex 3,

Appendix 6, and as reported using the instructions given PANS-ATM, Appendix 1.

2.5. Coordination between MWOs and ATS units

2.5.1. To achieve the best service to aviation and as part of the collaborative decision-

making process, close coordination between the MWO and the ATS units is required.

This is of particular importance for the avoidance of hazardous weather.

2.5.2. A Letter of Agreement between the ATS authority and the meteorological authority is

also recommended (as per Annex 3, 4.2) to outline the responsibilities and

coordination processes between the MWOs and ATS units.

2.6. Coordination between MWOs, VAACs, TCACs and State volcano observatories

2.6.1. Amongst the phenomena for which SIGMET information is required, volcanic ash

and tropical cyclones are of particular importance.

2.6.2. Since the identification, analysis and forecasting of volcanic ash and tropical cyclones

requires considerable scientific and technical resources, normally not available at each

MWO, VAACs and TCACs have been designated to provide volcanic ash advisories

and tropical cyclone advisories respectively to the users and assist the MWOs in the

preparation of SIGMETs for those phenomena. Close coordination should be

established between the MWO and its responsible VAAC and/or TCAC.

2.6.3. Information regarding the VAACs and TCACs areas of responsibility and lists of

MWOs and ACC/FICs to which advisories are to be sent is provided in the regional

ANPs FASID Tables MET 3A and MET 3B. Volcanic ash advisories and tropical

cyclone advisories are required for global exchange through SADIS and WIFS as they

are used by the operators during the pre-flight planning. Nevertheless, it should be

emphasized that SIGMET information is still required especially for in-flight re-

planning. SIGMETs should be transmitted to aircraft-in-flight through voice

communication, VOLMET or D-VOLMET, thus providing vital information for

making in-flight decisions regarding large-scale route deviations due to volcanic ash

clouds or tropical cyclones.

2.6.4. Information from State volcano observatories is an important part of the process for

issuance of volcanic ash advisories and SIGMETs. Information from a State volcano

observatory should be in the form of a Volcano Observatory Notification for Aviation

(VONA) and include information on significant pre-eruption volcanic activity,

volcanic eruptions or the presence of volcanic ash clouds. The format of the VONA is

given in the Handbook on the International Airways Volcano Watch (IAVW) –

Operational Procedures and Contact List (Doc 9766), Appendix E.

—————————

3-1

3. PROCEDURES FOR PREPARATION OF SIGMET INFORMATION

3.1. General

3.1.1. SIGMET is intended for transmission to aircraft in flight either by ATC or by

VOLMET or D-VOLMET, and therefore, SIGMET messages should be kept concise.

To this end, SIGMET information is prepared using approved ICAO abbreviations, a

limited number of non-abbreviated words and, numerical values of a self-explanatory

nature.

3.1.2. The increasing use of automated systems for handling the aeronautical meteorological

information by the users makes it essential that all types of OPMET information,

including SIGMET messages, are prepared and issued in the prescribed standardized

format. Therefore, the format of the SIGMET message, as specified in Annex 3,

Appendix 6, should be strictly followed by the MWOs.

3.1.3. The MWO should maintain watch over the evolution of the phenomenon for which a

SIGMET has been issued. If the phenomenon persists or is expected to persist beyond

the period of validity of the SIGMET, another SIGMET message for a further period

of validity should be issued with updated information. SIGMETs for volcanic ash and

tropical cyclone should be updated at least every 6 hours, while SIGMET for all other

phenomena should be updated at least every 4 hours.

3.1.4. SIGMET should be promptly cancelled when the phenomenon is no longer occurring

or no longer expected to occur in the MWO’s area of responsibility.

3.1.5. Some SIGMET are generated using information from special air-reports (received by

voice communications or data link (downlink)). The reporting of turbulence and icing

used in special air-reports includes both moderate and severe categories (as per Doc

4444, Appendix 1).

Note. ― Although the categories for the reporting, by pilots, of moderate and severe

turbulence in special air-reports is provided in PANS-ATM (Doc 4444), some pilots report turbulence

as “moderate to severe”. A MWO is then faced with determining which category to use in a special

air-report (uplink) or in a SIGMET message for severe turbulence. Some States elect to treat such

“moderate to severe” observations as ‘severe’ in the context of using the report to prompt the

issuance of a special air-report (uplink) or a SIGMET message.

3.2. SIGMET phenomena

3.2.1. SIGMET shall only be issued for the phenomena listed in Table 1 below and only

using the abbreviations as indicated.

Phenomena

Abbreviation

Description

OBSC TS Thunderstorms that are obscured by haze or smoke or cannot be

readily seen due to darkness.

EMBD TS Thunderstorms that are embedded within cloud layers and cannot

be readily recognized.

FRQ TS Frequent thunderstorms where, within the area of thunderstorms,

there is little no separation between adjacent thunderstorms with

a maximum spatial coverage greater than 75%. SQL TS A squall line indicating that a line of thunderstorms with little or

no space between clouds. OBSC TSGR Thunderstorms with hail that are obscured by haze or smoke or

cannot be readily seen due to darkness. EMBD TSGR Thunderstorms with hail that are embedded within cloud layers

3-2

Phenomena

Abbreviation

Description

and cannot be readily recognized. FRQ TSGR Frequent thunderstorms with hail, within the area of

thunderstorms, there is little or no separation between adjacent

thunderstorms with a maximum spatial coverage greater than

75%.

SQL TSGR A squall line indicating that a line of thunderstorms with hail

with little or no space between clouds.

TC A tropical cyclone with a 10 minute mean surface wind speed of

17m/s (34 kt) or more.

SEV TURB Severe turbulence referring to:

low-level turbulence associated with strong surface winds;

rotor streaming; or

clear air turbulence, whether in cloud or not in cloud.

Note. ― Turbulence should not be used in connection with

convective clouds. Severe turbulence shall be considered

whenever the peak value of the cube root of EDR exceeds 0.7.

SEV ICE Severe icing not associated with convective cloud.

SEV ICE

(FZRA)

Severe icing caused by freezing rain and not associated with

convective cloud.

SEV MTW Severe mountain wave the accompanying downdraft is 3 m/s

(600 ft/min) or more or when severe turbulence is observed or

forecast.

HVY DS Heavy duststorm where the visibility is below 200 m and the sky

is obscured.

HVY SS Heavy sandstorm where the visibility is below 200 m and the sky

is obscured.

VA Volcanic ash

RDOACT CLD Radioactive cloud Table 1: SIGMET phenomena abbreviations and descriptions

3.3. Allowable abbreviations

3.3.1. Abbreviations that can be used in the meteorological section of SIGMET include are

given in Table 1 above and in Table 2 below.

Abbreviation Meaning Abbreviation Meaning

ABV Above NE North-east APRX Approximate or

approximately

NNE North-north-east

AT At (followed by time) NNW North-north-west

BLW Below NM Nautical miles BTN Between NO No

CB Cumulonimbus cloud NW North-west

CLD Cloud OBS Observe or observed or

observation

CNL Cancel or cancelled PSN Position E East or eastern longitude S South or southern latitude

ENE East-north-east SE South-east ESE East-south-east SFC Surface

EXP Expect or expected or

expecting

SSE South-south-east

3-3

Abbreviation Meaning Abbreviation Meaning FCST Forecast SSW South-south-west

FIR Flight information region STNR Stationary FL Flight level SW South-west

FT Feet TO To INTSF Intensify or intensifying TOP Cumulonimbus cloud top

(height) KM Kilometres W West or western longitude

KT Knots WI Within (area)

LCA Location WID Width or wide M Metres WKN Weaken or weakening

MOV Move or moving or

movement

WNW West-north-west

MT Mountain WSW West-south-west N North or northern latitude Z Coordinated Universal Time

NC No change Table 2: SIGMET phenomena abbreviations and descriptions.

3.4. SIGMET structure

3.4.1. A SIGMET message consists of:

- WMO Abbreviated Heading Line (WMO AHL) – all SIGMETs are preceded

by an appropriate WMO AHL;

- First line, containing location indicators of the respective ATS unit and MWO,

sequential number and period of validity;

- SIGMET main body, containing information concerning the observed or

forecast weather phenomenon for which the SIGMET is issued together with its

expected evolution within the period of validity;

3.4.2. The first two parts of the SIGMET message are common for all types of SIGMET.

The format and content of the third part is different; that is why, in the following

paragraphs the meteorological part of the SIGMET message is described separately

for the three types of SIGMET.

3.4.3. Inclusion of more than one instance of a phenomenon in a SIGMET.

Footnote 21 to Table A6-1 permits the inclusion of more than one instance of a

phenomenon within a single SIGMET, but footnote 26 to Table A6-1 restricts the use

of the conjunction 'AND' to volcanic ash and tropical cyclone SIGMETs only. In both

these cases only two 'instances' are permitted. As such, some States have determined

that multiple instances of the same phenomena for SIGMET other than for volcanic

ash and tropical cyclones should not be used.

3.5. SIGMET format

Note. ― In the following text, square brackets - [ ] - are used to indicate an optional

or conditional element, and angled brackets - < > - for symbolic representation of a variable element,

which in a real SIGMET accepts a discrete numerical value.

3-4

3.5.1. WMO header

T1T2A1A2ii CCCC YYGGgg [BBB]

3.5.1.1. The group T1T2A1A2ii is the bulletin identification (WMO AHL) for the SIGMET

message. It is constructed in the following way:

T1T2 Data type designator WS – for SIGMET for meteorological phenomena other than

volcanic ash cloud or tropical cyclone

WC – for SIGMET for tropical cyclone

WV – for SIGMET for volcanic ash

A1A2 Country or territory

designators

Assigned according to Table C1, Part II of Manual on the

Global Telecommunication System, Volume I – Global

Aspects (WMO Publication No. 386) ii Bulletin number Assigned on national level according to p 2.3.2.2, Part II of

Manual on the Global Telecommunication System, Volume I

– Global Aspects (WMO Publication No. 386) Table 3: Specification of the WMO Abbreviated Header Line for SIGMET

3.5.1.2. CCCC is the ICAO location indicator of the communication centre disseminating the

message (this may be the same as the MWO location indicator).

3.5.1.3. YYGGgg is the date/time group; where YY is the day of the month and GGgg is the

time of transmission of the SIGMET in hours and minutes UTC (normally this time is

assigned by the disseminating (AFTN) centre).

3.5.2. First line of SIGMET

CCCC SIGMET [nn]n VALID YYGGgg/YYGGgg CCCC-

3.5.2.1. The meaning of the groups in the first line of the SIGMET is as follows:

CCCC ICAO location indicator of the ATS unit serving the FIR or CTA to

which the SIGMET refers SIGMET Message identifier [nn]n Daily sequence number (see 3.5.2.2) VALID Period of validity indicator YYGGgg/YYGGgg Validity period of the SIGMET given by date/time group of the

beginning and date/time group of the end of the period (see 3.5.2.3) CCCC ICAO location indicator of the issuing MWO - Mandatory hyphen to separate the preamble from the text

Table 4: Elements making up the first line of SIGMET

3.5.2.2. The numbering of SIGMETs starts every day at 0001 UTC. The sequence number

should consist of up to three symbols and may be a combination of letters and

numbers, such as:

- 1, 2, …

- 01, 02, …

- A01, A02, …

Examples:

RPMM SIGMET 3 VALID 121100/121700 RPLL-

3-5

WSJC SIGMET A04 VALID 202230/210430 WSSS-

Note 1. ― No other combinations should be used, like “CHARLIE 05” or “NR7”.

Note 2. ― Correct numbering of SIGMET is very important since the number is used for reference in

communication between ATC and pilots and in VOLMET and D-VOLMET.

Note 3. ― In accordance with Annex 5 – Units of Measurement to be Used in Air and Ground

Operations, when the validity period ends at midnight, YY should be set for the following day and

GGgg should be '0000'. i.e. SIGMET validity ending at midnight on the 23rd

day of the month should

be expressed as '240000'.

3.5.2.3. The following regulations apply when determining the validity period:

- The period of validity of a WS SIGMET should be not more than 4 hours;

- The period of validity of a WC or WV SIGMET should not be more than 6 hours;

- In case of a SIGMET for an observed phenomenon, the filing time (date/time

group in the WMO header) should be the same or very close to the time in the

date/time group indicating the start of the SIGMET validity period;

- When the SIGMET is issued for a forecast phenomenon:

o the beginning of validity period should be the time of the expected

commencement (occurrence) of the phenomenon in the MWO area of

responsibility;

o the time of issuance of a WS SIGMET should be not more than 4 hours

before the start of validity period (i.e., expected time of occurrence of the

phenomenon); and for WC (tropical cyclone) and WV (volcanic ash)

SIGMET the lead time should be not more than 12 hours.

3.5.2.4. The period of validity is that period during which the SIGMET information is valid

for transmission to aircraft in flight.

Examples:

1) First two lines of a SIGMET for an observed phenomenon:

WSTH31 VTBS 241120

VTBB SIGMET 3 VALID 241120/241500 VTBS–

2) First two lines of a SIGMET for a forecast phenomenon (expected time of

occurrence 1530)

WSSR20 WSSS 311130

WSJC SIGMET 1 VALID 311530/311930 WSSS-

3.5.3. Structure of the meteorological part of SIGMET for weather phenomena other

than for volcanic ash and tropical cyclone

3.5.3.1. The meteorological part of a SIGMET for weather phenomena consists of elements as

shown in the table below.

3-6

Start of the second line of the message

1 2 3 4 5 6 7 8

Name of the

FIR/UIR or

CTA

Description of the

phenomenon

Observed

or forecast Location Level

Movement

or expected

movement

Changes in

intensity

Forecast

position

See

3.5.3.2

See

3.5.3.3

See

3.5.3.4

See

3.5.3.5

See

3.5.3.6

See

3.5.3.7

See

3.5.3.8

See

3.5.3.9

Table 5: Elements making up the meteorological part of SIGMET

3.5.3.2. Name of the FIR/UIR or CTA

CCCC <name> FIR[/UIR]

or CCCC <name> CTA

The ICAO location indicator and the name of the FIR/CTA are given followed by the appropriate

abbreviation: FIR, FIR/UIR or CTA. The name may consist of up to 10 characters.

Examples: VTBB BANGKOK FIR

3.5.3.3. Phenomenon

The phenomenon description consists of a qualifier and a phenomenon abbreviation. SIGMET should

be issued only for the following phenomena observed or forecast at cruising levels (irrespective of

altitude):

- thunderstorms – if they are OBSC, EMBD, FRQ or SQL with or without hail (GR);

- turbulence – only SEV

- icing – only SEV with or without FZRA

- mountain waves – only SEV

- dust storm – only HVY

- sand storm – only HVY

- radioactive cloud – RDOACT CLD

The appropriate abbreviations and combinations, and their meaning are given in Table 1.

3.5.3.4. Indication whether the phenomenon is observed or forecast

OBS

or OBS AT GGggZ

or FCST

or FCST AT GGggZ

The indication whether the phenomenon is observed or forecast is given by using the abbreviations

OBS or FCST. OBS AT and FCST AT may be used, in which case they are followed by a time group

in the form GGggZ. If the phenomenon is observed, GGgg is the time of the observation in hours and

minutes UTC. If the exact time of the observation is not known the time is not included. When the

3-7

phenomenon is based on a forecast without a reported observation, the time given for GGggZ

represents the time of commencement of the phenomenon.

Examples:

OBS

OBS AT 0140Z

FCST

FCST AT 0200Z

3.5.3.5. Location of the phenomenon

The location of the phenomenon is given with reference to geographical coordinates (latitude and

longitude). Latitude and longitude may be reported in degrees, or in degrees and minutes. When

reporting in degrees the format will be Nnn or Snn for latitude, and Ennn or Wnnn for longitude.

When reporting in degrees and minutes the format will be Nnnnn or Snnnn for latitude, and

Ennnnn or Wnnnnn for longitude. The MWOs should try to be as specific as possible in reporting

the location of the phenomenon and, at the same time, to avoid overwhelming the SIGMET with too

many coordinates, which may be difficult to process or follow when transmitted by voice radio.

The following are the possible ways to describe the location of the phenomenon:

1) An area of the FIR defined by a polygon. . Minimum 4 coordinates1, and not

normally more than 7 coordinates. This is the format preferred operationally by

users.

Symbolically, this is indicated as:

WI <Nnn[nn]> or <Snn[nn]> <Wnnn[nn]> or <Ennn[nn]> -

<Nnn[nn]> or <Snn[nn]> <Wnnn[nn]> or <Ennn[nn]> -





<Nnn[nn]> or <Snn[nn]> <Wnnn[nn]> or <Ennn[nn]>

For example:

WI N6030 E02550 – N6055 E02500 – N6050 E02630 –

N6030 E02550

WI N60 E025 – N62 E27 - N58 E030 - N59 E26 - N60 E025

Note. ― The points of a polygon should be provided in a clockwise order, and the

end point should be a repeat of the start point.

1 Including the last point as a repeat of the first point to explicitly close the polygon

3-8

Use of polygons with complex FIR boundaries.

Annex 3 (18th Edition, July 2013) specifies that the points of a polygon '... should be kept to a

minimum and should not normally exceed seven'. However, some FIR boundaries are complex, and it

would be unrealistic to expect that a polygon would be defined that followed such boundaries exactly.

As such, some States have determined that the polygon points be chosen in relation to the complex

boundary such that the FIR boundary approximates, but is wholly encompassed by, the polygon, and

that any additional area beyond the FIR boundary be the minimum that can be reasonably and

practically described. Caution should however be exercised in those instances where international

aerodromes are located in close proximity to such a complex FIR boundary. Appendix B provides

examples and advice with regard to describing such areas.

2a) In a sector of the FIR defined relative to a specified line joining two points on the

FIR boundary2.

Symbolically this is indicated as:

<N OF> or <NE OF> or <E OF> or <SE OF> or <S OF> or

<SW OF> or <W OF> or <NW OF> LINE <Nnn[nn]> or

<Snn[nn]> <Wnnn[nn]> or <Ennn[nn]> - <Nnn[nn]> or

<Snn[nn]> <Wnnn[nn]> or <Ennn[nn]>

For example:

NE OF LINE N2500 W08700 – N2000 W08300

W OF LINE N20 E042 – N35 E045

2b) In a sector of the FIR defined relative to a line of latitude and a line of longitude

(effectively a quadrant);


<N OF> or <S OF> or <Nnn[nn]> or <Snn[nn]> AND

<E OF> or <W OF> <Wnnn[nn]> or <Ennn[nn]>

For example:

N OF N1200 AND E OF W02530

S OF N60 W OF E120

2c) In a sector of the FIR defined relative to a line of latitude or longitude

(effectively a segment), where a coordinate of latitude (or longitude) defines a

line, and the preceding descriptor defines on which side of the line the

phenomena is expected


<N OF> or <S OF> <Nnn[nn]> or <Snn[nn]> or


2 or so close to the FIR boundary so as to leave no doubt that the intent is for the line to connect to the FIR boundary at that

point (this is to allow for some small margin of error when judging the coordinates where the specified line would intersect

the FIR boundary.

3-9

For example:

N OF S2230

W OF E080

3) At a specific point within the FIR, indicated by a single coordinate of latitude

and longitude.




For example:

N5530 W02230

S23 E107

More detail on reporting the location of the phenomena is given in the examples provided in

Appendix B to this guide.

3.5.3.6. Flight level

Symbolically, the options permitted are:

FLnnn

or SFC/FLnnn

or SFC/nnnnM

or SFC/nnnnFT

or FLnnn/nnn

or TOP FLnnn

or ABV FLnnn

or TOP ABV FLnnn

In more detail, the location or extent of the phenomenon in the vertical is given by one or more of the

above methods, as follows:

1) reporting at a single flight level

For example: FL320

2) reporting a layer extending from the surface to a given height in meters or feet

For example: SFC/3000M or SFC/9900FT

3-10

3) reporting a layer extending from a given FL to a higher flight level

For example: FL250/FL290

4) reporting a layer where the base is unknown, but the top is given:

For example: TOP FL350

5) reporting a layer where the top is unknown, but the base is given:

For example: ABV FL350

Additional examples:

EMBD TS … TOP ABV FL340

SEV TURB … FL180/210

SEV ICE … SFC/FL150

SEV MTW … FL090

3.5.3.7. Movement

Rate of movement is indicated in the following way:

MOV <direction> <speed>KMH[KT]

or STNR

Direction of movement is given with reference to one of the sixteen points of compass (N, NNE, NE,

ENE, E, ESE, SE, SSE, S, SSW, SW, WSW, W, WNW, NW, NNW). Speed is given in KMH or KT. The

abbreviation STNR is used if no significant movement is expected.

Examples:

MOV NNW 30KMH

MOV E 25KT

STNR

Note. ― When also including a forecast position, care should be taken to ensure that

the rate of movement and forecast position are consistent.

3.5.3.8. Expected changes in intensity

The expected evolution of the phenomenon’s intensity is indicated by one of the following

abbreviations:

INTSF

or WKN

or NC

3-11

3.5.3.9. Forecast position of the hazardous phenomena at the end of the validity period of the

SIGMET message

Note. ― Annex 3 (18th Edition, July 2013) enables SIGMET to contain explicit

forecast position information relating to hazardous phenomena other than volcanic ash or tropical

cyclone.

FCST <GGgg>Z

FCST is mandatory for this section. The GGggZ group should indicate the end of validity period as

given in the first line of the SIGMET message.

Note. ― In accordance with Annex 5 – Units of Measurement to be Used in Air and

Ground Operations, when the validity period ends at midnight, YY should be set for the following day

and GGgg should be '0000'. i.e. SIGMET validity ending at midnight on the 23rd

day of the month

should be expressed as '240000'.

The forecast position of the phenomenon is given with reference to geographical coordinates (latitude

and longitude). Latitude and longitude may be reported in degrees, or in degrees and minutes. When





many coordinates, which may be difficult to process or follow when transmitted via voice radio.

The following are the possible ways to describe the forecast position of the phenomenon:

1) An area of the FIR defined by a polygon. Minimum 43 coordinates, and not


users.



<Nnn[nn]> or<Snn[nn]> <Wnnn[nn]> or <Ennn[nn]> -





<Nnn[nn]> or<Snn[nn]> <Wnnn[nn]> or <Ennn[nn]>

For example:

WI N6030 E02550 – N6055 E02500 – N6050 E02630 –

N6030 E02550

WI N60 E025 – N62 E27 - N58 E030 - N59 E26 - N60 E025




3-12

2a) In a sector of the FIR defined relative to specified line joining two points on the

FIR boundary4.


<N OF> or <NE OF> or <E OF> or <SE OF> or <S OF> or

<SW OF> or <W OF> or <NW OF> LINE <Nnn[nn]> or

<Snn[nn]> <Wnnn[nn]> or <Ennn[nn]> - <Nnn[nn]> or

<Snn[nn]> <Wnnn[nn]> or <Ennn[nn]>

For example:

NE OF LINE N2500 W08700 – N2000 W08300

W OF LINE N20 E042 – N35 E045


(effectively a quadrant);


<N OF> or <S OF> or <Nnn[nn]> or <Snn[nn]> AND <E OF>

or <W OF> <Wnnn[nn]> or <Ennn[nn]>

For example:

N OF N1200 AND E OF W02530

S OF N60 W OF E120

2b) In a sector of the FIR defined relative to a line of latitude or longitude

(effectively a segment), where a coordinate of latitude (or longitude) defines a

line, and the preceding descriptor defines on which side of the line the

phenomena is expected


<N OF> or <S OF> <Nnn[nn]> or <Snn[nn]> or


For example:

N OF S2230

W OF E080

3) At a specific point within the FIR, indicated by a single coordinate of latitude

and longitude.


4 or so close to the FIR boundary so as to leave no doubt that the intent is for the line to connect to the FIR boundary at that

point (this is to allow for some small margin of error when judging the coordinates where the specified line would intersect

the FIR boundary.

3-13



For example:

N5530 W02230

S23 E107

More details on reporting the location of the phenomenon are given in the examples in Appendix B to

this guide.

Note. ― Currently, there is no provision for indicating changes to the levels affected by

phenomena between the initial position and the forecast position. As such, and as per footnote 31 to

Table A6-1 of Annex 3 (18th Edition, July 2013), it should be assumed that the levels affected remain

the same for both initial and forecast positions.

3.5.4. Structure of the meteorological part of SIGMET for volcanic ash

3.5.4.1. The general structure of the meteorological part of the SIGMET message for volcanic

ash is given in the table below.

1 2 3 4 5 6 7 8

Name of the

FIR/UIR or

CTA

Name and location

of the volcano

and/or indicator

for VA cloud

Time of

observation

or forecast

Location

Level and

extent of

the

volcanic

ash cloud

Movement

or expected

movement

Changes in

intensity

Forecast

position

See

3.5.4.2

See

3.5.4.3

See

3.5.4.4

See

3.5.4.5

See

3.5.4.6

See

3.5.4.7

See

3.5.4.8

See

3.5.4.9

Table 6: Elements making up the meteorological part of VA SIGMET



or CCCC <name> CTA

The ICAO location indicator and the name of the FIR/CTA are given followed by the

appropriate abbreviation: FIR, FIR/UIR or CTA. The name may consist of up to 10

characters.

Examples:

VTBB BANGKOK FIR

3.5.4.3. Name and location of the volcano and/or indicator for VA cloud

There are three combinations that may be used in this section.

1) If the location of the eruption is known but is un-named then the following format

is appropriate:

VA ERUPTION PSN <lat,lon> VA CLD

3-14

Where ‘VA ERUPTION’ is mandatory. ‘PSN’ is an abbreviation for ‘position’,

followed by the latitude and longitude, followed by the mandatory ‘VA CLD’.

2) If the erupting volcano is known and named then the following format is

appropriate:

VA ERUPTION MT ASHVAL PSN <lat,lon> VA CLD

Where ‘VA ERUPTION’ is mandatory. ‘MT’ is an abbreviation for ‘mountain’ to

be followed by the volcano's name. ‘PSN’ is an abbreviation for ‘position’,

followed by the latitude and longitude, followed by the mandatory ‘VA CLD’.

3) If the source of the volcanic ash is uncertain, then the following format is

appropriate:

VA CLD

The location (latitude and longitude) of the volcano, when known and reported,

may be reported in degrees, or in degrees and minutes. When reporting in degrees

the format will be Nnn or Snn for latitude, and Ennn or Wnnn for longitude.

When reporting in degrees and minutes the format will be Nnnnn or Snnnn for

latitude, and Ennnnn or Wnnnnn for longitude.

For example:

VA ERUPTION PSN N27 W017 VA CLD

VA ERUPTION MT ASHVAL PSN S1530 E07315 VA CLD

3.5.4.4. Time of observation or forecast

OBS AT <GGgg>Z

or FCST AT <GGgg>Z

The time of observation is taken from the source of the observation – satellite image, special air-

report, report from a volcano observing station, etc. If the VA cloud is not yet observed over the FIR

but the volcanic ash advisory received from the responsible VAAC indicates that the cloud is going to

affect the FIR within the next 12 hours, SIGMET should be issued according as above and the

abbreviation FCST AT <GGgg>Z should be used.

Examples:

OBS AT 0100Z

FCST AT 1200Z

3.5.4.5. Location of the phenomenon

The location of the phenomenon is given with reference to geographical coordinates (latitude and

longitude). Latitude and longitude may be reported in degrees, or in degrees and minutes. When



3-15



many coordinates, which may be difficult to process or follow when transmitted by voice

communication.

The following are the possible ways to describe the location of the VA phenomenon:

1) An area of the FIR defined by a polygon. Minimum 4 coordinates5, and not


users.









For example:

WI N6030 E02550 – N6055 E02500 – N6050 E02630 –

N6030 E02550

WI N60 E025 – N62 E27 - N58 E030 - N59 E26 - N60 E025





minimum and should not normally exceed seven'. However, some FIR boundaries are complex,

and it would be unrealistic to expect that a polygon would be defined that followed such

boundaries exactly. As such, some States have determined that the polygon points be chosen in

relation to the complex boundary such that the FIR boundary approximates, but is wholly

encompassed by, the polygon, and that any additional area beyond the FIR boundary be the

minimum that can be reasonably and practically described. Caution should however be

exercised in those instances where international aerodromes are located in close proximity to

such a complex FIR boundary. Appendix B provides examples and advice with regard to

describing such areas.

2) Covering the entire FIR or CTA (this is only permitted for volcanic ash)

ENTIRE FIR

or ENTIRE CTA

For describing an area of volcanic ash by reference to a zone defined by line of specified width,

see the 'Level and extent' section that follows.


3-16

3.5.4.6. Level and extent of the volcanic ash cloud

When the Location of volcanic ash is described using the available descriptors in the 'Location

section', the Level of the volcanic ash may be described using descriptors used for other phenomena,

i.e. FLnnn

or SFC/FLnnn

or SFC/nnnnM

or SFC/nnnnFT

or FLnnn/nnn

or TOP FLnnn

or ABV FLnnn

or TOP ABV FLnnn

In more detail, the location or extent of the phenomenon in the vertical is given by one or more of the

above methods, as follows:

1) reporting at a single flight level

For example:

FL320

2) reporting a layer extending from the surface to a given height in meters or feet

For example:

SFC/3000M

SFC/9900FT

3) reporting a layer extending from a given FL to a higher flight level

For example:

FL250/FL290

4) reporting a layer where the base is unknown, but the top is given:

For example:

TOP FL350

5) reporting a layer where the top is unknown, but the base is given:

For example:

3-17

ABV FL350

Where it is preferred to describe the area affected by volcanic ash by describing a zone defined by a

line of specified width (rather than a polygon), the following level/extent combination should be used:

FL<nnn/nnn> <nnn>KM WID LINE BTN [<(lat,lon)P1 -

(lat,lon)P2 - … >]

or FL<nnn/nnn> <nnn>NM WID LINE BTN [<(lat,lon)P1 -

(lat,lon)P2 - … >]

Example:

FL150/210 50KM WID LINE BTN S0530 E09300 – N0100 E09530 –

N1215 E11045 – N1530 E01330

If the VA cloud spreads over more than one FIR, separate SIGMETs should be issued by all MWOs

whose FIRs are affected. In such a case, the description of the volcanic ash cloud by each MWO

should encompass the part of the cloud, which lies over the MWO’s area of responsibility. The

MWOs should try and keep the description of the volcanic ash clouds consistent by checking the

SIGMET messages received from the neighbouring MWOs.

3.5.4.7. Movement or expected movement of the VA cloud


or STNR

The direction of movement is given by the abbreviation MOV (moving), followed by one of the sixteen

points of compass: N, NNE, NE, ENE, E, ESE, SE, SSE, S, SSW, SW, WSW, W, WNW, NW, and NNW. The

speed of movement is given in KMH or KT.

Examples:

MOV E 35KMH

MOV SSW 20KT

STNR

Note. ― When also including a forecast position, care should be taken to ensure that

the rate of movement and forecast position are consistent

3.5.4.8. Expected changes in intensity

The expected evolution of the phenomenon’s intensity is indicated by one of the following

abbreviations:

INTSF

or WKN

or NC

3-18

3.5.4.9. Forecast position of the Volcanic Ash cloud at the end of the validity period of the

SIGMET message

The area affected by a volcanic ash cloud at the end of the validity period can be

described in the following ways.

As a polygon, using the following format:

FCST <GGgg>Z VA CLD APRX <(lat,lon)P1 - (lat,lon)P2 - … >

Example:

FCST 1800Z VA CLD APRX N6300 W02000 – N6030 W01700 –

N5815 W02230 – N6100 W02400 – N6300 W02000...

or, as a line of ash (of specified width in KM) defined by a sequence of coordinates

FCST <GGgg>Z VA CLD APRX nnKM WID LINE BTN <(lat,lon)P1 -

(lat,lon)P2 - … >

Example:

FCST 1800Z VA CLD APRX 90KM WID LINE BTN S4000 W09000 –

S4300 W08500 – S3800 W07500 - S4500 W06000...

or, as a line of ash (of specified width in NM) defined by a sequence of coordinates

FCST <GGgg>Z VA CLD APRX nnNM WID LINE BTN <(lat,lon)P1 -

(lat,lon)P2 - … >

Example:

FCST 1800Z VA CLD APRX 55NM WID LINE BTN S4000 W09000 –

S4300 W08500 – S3800 W07500 - S4500 W06000...

The GGggZ group should indicate the end of validity period as given in the first line of the SIGMET

message. The description of the expected position of the volcanic ash cloud is given by a number of

points forming a simplified geometrical approximation of the cloud.

Note. ― Currently, there is no provision for indicating changes to the levels affected

by volcanic ash between the initial position and the forecast position. As such, as per footnote 31 to

Table A6-1 of Annex 3 (18th Edition, July 2013), it should be assumed that the levels affected remain

the same for both initial and forecast positions.

Inclusion of multiple instances of volcanic ash phenomena.

Footnote 26 of Table A6-1 permits the word 'AND' in the 'Forecast position' section "To be used for

[describing] two volcanic ash clouds or two centres of tropical cyclones simultaneously affecting the

FIR concerned".

With regard to the portrayal of complex volcanic ash events (which implies multiple areas of volcanic

ash at multiple levels) basic guidance in this regard is provided in Appendix B.

3-19

3.5.5. Structure of the meteorological part of SIGMET for tropical cyclone

3.5.5.1. The general structure of the meteorological part of the SIGMET messages for tropical

cyclone is given in the table below.

1 2 3 4 5 6 7 8

Name of the

FIR/UIR or

CTA

Name of the

tropical

cyclone

Time of

observation

or forecast

Location

of the TC

centre

Vertical and

horizontal extent

of the CB cloud

formation

around TC

centre

Movement

or expected

movement

Changes in

intensity

Forecast

position

See

3.5.5.2

See

3.5.5.3

See

3.5.5.4

See

3.5.5.55

See

3.5.5.6

See

3.5.5.7

See

3.5.5.8

See

3.5.5.9

Table 7: Elements making up the meteorological part of TC SIGMET



or CCCC <name> CTA

The ICAO location indicator and the name of the FIR/CTA are given followed by the appropriate

abbreviation: FIR, FIR/UIR or CTA. The name may consist of up to 10 characters.

Example:

VTBB BANGKOK FIR

3.5.5.3. Name of the tropical cyclone

TC <name> (up to 10 characters, or 'NN' if not named)

The description of the tropical cyclone consists of the abbreviation TC followed by the international

name of the tropical cyclone given by the corresponding WMO RSMC. If disturbance is expected to

become a TC, but is not named at the time the forecast is issued, 'NN' is used for the TC name. .

Examples:

TC GLORIA

TC 04B

TC NN

3.5.5.4. Time of observation or forecast

OBS AT <GGgg>Z

or FCST AT <GGgg>Z

3-20

The time in UTC is given in hours and minutes, followed by the indicator Z. Normally, time is taken

from the MWO's own observations or from a TC advisory received from the responsible TCAC. If the

TC is not yet observed in the FIR but the tropical cyclone advisory received from the responsible

TCAC, or any other TC forecast used by the MWO, indicates that the TC is going to affect the FIR

within the next 12 hours, SIGMET should be issued and the abbreviation FCST AT <GGgg>Z

should be used.

Examples:

OBS AT 2330Z

FCST AT 0900Z

3.5.5.5. Location of the TC centre

<location>

The location of the TC centre is given by its lat/long coordinates in degrees or degrees and minutes.

Example:

N1535 E14230

3.5.5.6. Vertical and horizontal extent of the CB cloud formation around TC centre

CB TOP [ABV or BLW] <FLnnn> WI <nnnKM or nnnNM> OF

CENTRE

Examples:

CB TOP ABV FL450 WI 200NM OF CENTRE

CB TOP FL500 WI 250KM OF CENTRE

CB TOP BLW FL550 WI 250NM OF CENTRE

3.5.5.7. Movement or expected movement


or STNR

The direction of movement is given by the abbreviation MOV (moving), followed by one of the sixteen

points of compass: N, NNE, NE, ENE, E, ESE, SE, SSE, S, SSW, SW, WSW, W, WNW, NW, and NNW. The

speed of movement is given in KMH or KT.

Examples:

MOV NNW 30KMH

MOV E 25KT

3-21

3.5.5.8. Intensity change

The expected change of the intensity of the tropical cyclone is indicated by one of the following

abbreviations:

INTSF

or

WKN

or NC

3.5.5.9. Forecast Position of the TC centre at the end of the validity period of the SIGMET

message

FCST <GGgg>Z TC CENTRE <location>

The time given by GGggZ should be the same as the end of validity period indicated in the first line of

the SIGMET message. Since the period of validity is up to 6 hours (normally, 6 hours), this is a 6-

hour forecast of the position of the TC centre.

The forecast position of the TC centre is given by its lat/long coordinates following the general rules

of reporting lat/long information provided in the examples in Appendix B to this Guide.

Example:

FCST 1200Z TC CENTRE N1430 E12800

Inclusion of multiple instances of Tropical Cyclone phenomena.

Footnote 26 of Table A6-1 permits the word 'AND' in the 'Forecast position' section "To be used for

[describing] two volcanic ash clouds or two centres of tropical cyclones simultaneously affecting the

FIR concerned".

With regard to the portrayal of two tropical cyclones, simple guidance is provided in Appendix B.

3.5.6. Cancellation of SIGMET

3.5.6.1. Annex 3, 7.1.2 requires that "SIGMET information shall be cancelled when the phenomena

are no longer occurring or are no longer expected to occur in the area”.

3.5.6.2. As such, it is mandatory for an MWO to cancel any SIGMET that is currently valid but for

which the specified phenomena no longer exists or is expected to exist.

3.5.6.3. The cancellation is done by issuing the same type of SIGMET (i.e. WS, WV or WC) with

the following structure:

- WMO heading with the same data type designator;

- First line that contains as period of validity the remaining time of the original

period of validity;

- Second line, which contains the name of the FIR or CTA, the combination CNL

SIGMET, followed by the sequence number of the original SIGMET and its

original validity period.

3-22

3.5.6.4. A cancellation SIGMET should have a unique sequence number, and should follow the

format below.

For a SIGMET that is cancelled during its period of validity, the cancellation SIGMET

will be of the form:

As an example, an original SIGMET of:

YMMM SIGMET A01 VALID 260300/260700 YPRF-

YMMM MELBOURNE FIR EMBD TS FCST WI 120NM OF S1542 E9530 TOP

FL450 MOV SW 5KT INTSF=

If it were to be cancelled early (i.e. prior to 0700 UTC), then the following would be

appropriate:

YMMM SIGMET A02 VALID 260600/260700 YPRF-

YMMM MELBOURNE FIR CNL SIGMET A01 260300/260700=

Where:

- the sequence number will be the next incrementing, unique sequence number.

- the validity time will be the time remaining between issuance and the end time

of the original SIGMET.

- the sequence number of the original (and to be cancelled) SIGMET shall follow

'CNL SIGMET '.

- the original validity time of the original (and to be cancelled) SIGMET shall be

included in the message after the reference to the original SIGMET's sequence

number.

For SIGMET for volcanic ash only, the following is permitted:

WSAU21 ADRM 202155 YBBB SIGMET E03 VALID 202155/210000 YPDM- YBBB BRISBANE FIR CNL SIGMET E01 202000/210000 VA MOV TO WXYX

FIR=

Where the FIR (WXYZ in the example) into which the volcanic ash has moved is indicated.

3.5.7. Amendment of SIGMET

3.5.7.1. If it is known that an existing SIGMET no longer accurately describes the existing or

expected future evolution of the phenomena a new SIGMET, correctly describing the

hazard should be issued, followed immediately by a cancellation of the original, erroneous

SIGMET. The new SIGMET should be issued before the cancellation in order to ensure

there is always a SIGMET in force and that the cancellation is not mistakenly understood to

mean that the hazard has completely dissipated.

Originally issued SIGMET, later determined to no longer be accurate (bold text identifies

points that will be changed):

WSAU21 ADRM 201855 YBBB SIGMET E01 VALID 202000/210000 YPDM- YBBB BRISBANE FIR SEV TURB FCST WI S1530 E13700 - S1900 E13730

– S2000 E13130 - S1600 E13500 - S1530 E13700 SFC/FL120 MOV SE

12KT WKN=

3-23

Updated SIGMET (bold text identifies points that have been changed):

WSAU21 ADRM 202155 YBBB SIGMET E02 VALID 202200/210000 YPDM- YBBB BRISBANE FIR SEV TURB FCST WI S1530 E13700 - S2000 E13750

– S2045 E13245 - S1600 E13500 - S1530 E13700 SFC/FL120 MOV SE

12KT WKN=

Cancellation SIGMET (this cancels the original SIGMET):

WSAU21 ADRM 202155 YBBB SIGMET E03 VALID 202155/210000 YPDM- YBBB BRISBANE FIR CNL SIGMET E01 202000/210000=

3.6. Dissemination of SIGMET

3.6.1. SIGMET is part of operational meteorological (OPMET) information. According to Annex

3, the telecommunication facilities used for the exchange of the operational meteorological

information should be the aeronautical fixed service (AFS).

3.6.2. The AFS consists of a terrestrial segment, AFTN or ATN (AMHS), and a satellite segment

which comprises the SADIS provided by WAFC London, as well as the Internet-based

Secure SADIS FTP and WIFS services provided by WAFC London and WAFC

Washington respectively. Note that SIGMET priority indicator is FF for flight safety

messages (Annex 10, Volume II, 4.4.1.1.3 refers).

3.6.3. Currently, AFTN links should be used by the MWOs to send the SIGMET, as follows:

- to the adjacent MWOs and ACCs6 using direct AFTN addressing;

- when required for VOLMET or D-VOLMET, SIGMET should be sent to the relevant

centre providing the VOLMET service;

- SIGMET should be sent to all regional OPMET Data Banks (RODB);

- it should be arranged that SIGMET is relayed to the SADIS and WIFS providers for

satellite/public internet dissemination, as well as to the WAFCs London and

Washington, either through the ROBEX scheme, or directly by the issuing MWO;

- SIGMET for volcanic ash should be disseminated to the responsible VAAC.

3.6.4. Through SADIS and WIFS, SIGMET is disseminated to all authorised users. In this way,

SIGMET is available on a global basis, meeting the aeronautical requirements.

— — — — — — — —

6 For this dissemination it is required that SIGMET is available at the ACCs for transmission to aircraft in flight for the route

ahead up to a distance corresponding to two hours flying time.

A-1

APPENDIX A

SIGMET GUIDANCE TABLE: SIMPLIFIED FROM ANNEX 3 TABLE A6-1

Note. ― The table below seeks to provide more explicit guidance than that given in Table A6-1 of Annex 3 (18th Edition, July 2013). It does this by

removing all references to the AIRMET message and special air-report message elements contained in Table A6-1. The table below simplifies the available

options and provides more specific expansion of the symbolic structure of SIGMET messages, with guidance sub-titles where appropriate. It should be noted

that Annex 3, Appendix 6, Table A6-1 remains the authoritative reference.

Ref No.

Element as specified in Chapter 5 and Appendix 6

Detailed Content Expanded symbolic - These ‘expanded’ symbolic representations of the various SIGMET code elements represent the interpretation of Table A6-1 of Annex 3. MWOs are encouraged to align their SIGMETs with the guidelines below.

Examples. These examples of various SIGMET code elements represent the interpretation A6-1 of Annex 3. MWOs are encouraged to align their SIGMETs with the examples below.

1.1 Location indicator of

FIR/CTA (M)1

ICAO location indicator of the ATS unit serving the FIR or CTA to which the SIGMET refers (M)

nnnn YUCC2

YUDD2

1.2 Identification Message identification and sequence number

(M)3

n

nn

nnn

SIGMET 5

SIGMET A3

SIGMET B10

1.3 Validity period Day-time groups indicating the period of validity in UTC (M)

VALID nnnnnn/nnnnnn VALID 221215/221600

VALID 101520/101800

VALID 252000/260000

VALID 122000/130400 (6 hour validity applicable

to TC or VA only)

1.4 Location indicator of MWO (M)

Location indicator of MWO originating the message with a separating hyphen (M)

nnnn- YUDO–2

YUSO–2

1.5 Name of the FIR/CTA or aircraft identification (M)

Location indicator and name of the FIR/CTA for which the SIGMET is issued (M)

nnnn nnnnnnnnnn FIR

nnnn nnnnnnnnnn FIR/UIR

nnnn nnnnnnnnnn CTA

YUCC AMSWELL FIR2

YUDD SHANLON FIR/UIR2

YUDD SHANLON FIR2

YUCC AMSWELL CTA

2.1 Phenomenon (M)4 Description of phenomenon causing the issuance of SIGMET

OBSC5 TS

OBSC5 TSGR

6

EMBD7 TS

OBSC TS

OBSC TSGR

EMBD TS

EMBD TSGR

A-2

Ref No.




(C) EMBD7 TSGR

6

FRQ8 TS

FRQ8 TSGR

6

SQL9 TS

SQL9 TSGR

6

TC nnnnnnnnnn

TC NN10

SEV TURB11

SEV ICE12

SEV ICE (FZRA)12

SEV MTW12

HVY DS

HVY SS

VA ERUPTION PSN Nnn[nn] or Snn[nn] Ennn[nn] or

Wnnn[nn] VA CLD

VA ERUPTION MT nnnnnnnnnn PSN Nnn[nn] or Snn[nn]

Ennn[nn] or Wnnn[nn] VA CLD

VA CLD

RDOACT CLD

FRQ TS

FRQ TSGR

SQL TS

SQL TSGR

TC GLORIA

TC NN

SEV TURB

SEV ICE

SEV ICE (FZRA)

SEV MTW

HVY DS

HVY SS

VA ERUPTION PSN N27 W017 VA CLD

VA ERUPTION PSN S1200 E01730 VA CLD

VA ERUPTION MT ASHVAL PSN S15 E073 VA CLD

VA ERUPTION MT VALASH PSN N2030 E02015 VA CLD

VA CLD

RDOACT CLD

2.2 Observed or forecast phenomenon (M)

Indication whether the information is observed and expected to continue, or forecast (M)

OBS

OBS AT nnnnZ

FCST

FCST AT nnnnZ

OBS AT 1210Z

OBS

FCST AT 1815Z

FCST

A-3

Ref No.




2.3 Location (C)18

Location (referring to latitude and longitude (in degrees and minutes))

1) An area of the FIR defined by a polygon. The end point shall be a repeat of the start point. Minimum 4 coordinates and not normally more than 7 coordinates.

WI24 Nnn[nn] or Snn[nn] Wnnn[nn] or Ennn[nn] – Nnn[nn]

or Snn[nn] Wnnn[nn] or Ennn[nn] – Nnn[nn] or Snn[nn]

Wnnn[nn] or Ennn[nn][ - Nnn[nn] or Snn[nn] Wnnn[nn]

or Ennn[nn] – Nnn[nn] or Snn[nn] Wnnn[nn] or

Ennn[nn]]

or 2a) In a sector of the FIR defined relative to a specified line joining two points on the FIR boundary (or so close to the FIR boundary so as to leave no doubt that the intent is for the line to connect to the FIR boundary at that point).

[N][NE][E][SE][S][SW][W][NW] OF [LINE] Nnn[nn] or

Snn[nn] Wnnn[nn] or Ennn[nn] – Nnn[nn] or Snn[nn]

Wnnn[nn] or Ennn[nn]

or

2b) In a sector of the FIR defined relative to a line of latitude and a line of longitude (effectively a quadrant);

N OF Nnn[nn] AND W OF Wnnn[nn] or

N OF Nnn[nn] AND E OF Wnnn[nn] or

S OF Nnn[nn] AND W OF Wnnn[nn] or

S OF Nnn[nn] AND E OF Wnnn[nn] or

N OF Nnn[nn] AND W OF Ennn[nn] or

N OF Nnn[nn] AND E OF Ennn[nn] or

S OF Nnn[nn] AND W OF Ennn[nn] or

S OF Nnn[nn] AND E OF Ennn[nn] or

or 2c) In a sector of the FIR defined relative to a line of latitude or longitude (effectively a segment);

N OF Nnn[nn] or

S OF Nnn[nn] or

1) An area of the FIR defined by a polygon. The end point shall be a repeat of the start point. Minimum 4 coordinates (including the last point as a repeat of the first), and not normally more than 7 coordinates.

WI N6030 E02550 – N6055 E02500 – N6050 E02630 -

N6030 E02550

WI N30 W067 – N32 W070 – N35 W068 - N30 W067

or 2a) In a sector of the FIR defined relative to a specified line joining two points on the FIR boundary (or so close to the FIR boundary so as to leave no doubt that the intent is for the line to connect to the FIR boundary at that point).

NE OF LINE N2515 W08700 – N2000 W08330 S OF LINE S14 E150 – S14 E155

or

2b) In a sector of the FIR defined relative to a line of latitude and a line of longitude (effectively a quadrant);

S OF N3200 AND E OF E02000

S OF S3215 AND W OF E10130

S OF N12 AND W OF E040 N OF N35 AND E OF E078

or

2c) In a sector of the FIR defined relative to a line of latitude or longitude (effectively a segment); N OF S2230 S OF S43

A-4

Ref No.




N OF Snn[nn] or

S OF Snn[nn] or

W OF Wnnn[nn] or

E OF Wnnn[nn] or

W OF Ennn[nn] or E OF Ennn[nn]

or 3) At a specific point within the FIR;

Nnn[nn] Wnnn[nn] or

Nnn[nn] Ennn[nn] or

Snn[nn] Wnnn[nn] or Snn[nn] Ennn[nn]

or

4) A reference to the whole FIR/CTA

ENTIRE FIR21

ENTIRE CTA21

E OF E01700 E OF W005

or 3) At a specific point within the FIR;

N5530 W02230 S12 E177

or

4) A reference to the whole FIR/CTA

ENTIRE FIR

ENTIRE CTA

2.4 Level (C)18

Flight level or altitude and extent

(C)19

1) Generic height/range descriptors to be used when 'Location' descriptors above are used.

FLnnn SFC/FLnnn

SFC/nnnnM

SFC/nnnnFT

FLnnn/nnn

TOP FLnnn

ABV FLnnn

TOP ABV FLnnn

or 20

2) Radius from TC centre from which CB related to Tropical Cyclone ONLY may be expected.

CB TOP FLnnn WI nnn{KM/NM} OF CENTRE CB TOP ABV FLnnn WI nnn{KM/NM} OF CENTRE

1) Generic height/range descriptors.

FL180

SFC/FL070

SFC/9000FT

FL050/080

FL310/450

TOP FL390

ABV FL280

TOP ABV FL100

or 20

2) Radius from TC centre from which CB related to Tropical Cyclone ONLY may be expected.

CB TOP FL500 WI 270KM OF CENTRE

CB TOP FL500 WI 150NM OF CENTRE

A-5

Ref No.




CB TOP BLW FLnnn WI nnn{KM/NM} OF CENTRE

or 21

3) Zone defined by a line of specified width within which volcanic ash is expected.

FLnnn/nnn nnKM WID LINE22 BTN Nnn[nn] or Snn[nn]

Wnnn[nn] or Ennn[nn] – Nnn[nn] or Snn[nn] Wnnn[nn] or

Ennn[nn] – Nnn[nn] or Snn[nn] Wnnn[nn] or Ennn[nn][ -

Nnn[nn] or Snn[nn] Wnnn[nn] or Ennn[nn]]

or

FLnnn/nnn nnNM WID LINE22 BTN Nnn[nn] or Snn[nn]

Wnnn[nn] or Ennn[nn] – Nnn[nn] or Snn[nn] Wnnn[nn] or

Ennn[nn] – Nnn[nn] or Snn[nn] Wnnn[nn] or Ennn[nn][ -

Nnn[nn] or Snn[nn] Wnnn[nn] or Ennn[nn]]

CB TOP ABV FL450 WI 250KM OF CENTRE CB TOP BLW FL530 WI 150NM OF CENTRE

or 21

3c) Zone defined by a line of specified width within which volcanic ash is expected.

FL310/450 100KM WID LIN BTN S4330 E02200 –

N4315 E02230 – N4230 E02300 – N4145 E02230 –

N4130 E02145

or

FL310/450 60NM WID LIN BTN S4330 E02200 – N4315

E02230 – N4230 E02300 – N4145 E02230 – N4130

E02145

2.5 Movement or expected movement

(C)18

Movement or expected movement (direction and speed) with reference to one of the sixteen points of compass, or stationary (C)

MOV[N][NNE][NE][ENE][E][ESE][SE][SSE][S][SSW][SW][WSW

][W][WNW][NW][NNW] nnKMH

or

MOV[N][NNE][NE][ENE][E][ESE][SE][SSE][S][SSW][SW][WSW

][W][WNW][NW][NNW] nnKT

or

STNR

MOV E 40KMH

MOV E 20KT

MOV SE

STNR

2.6 Changes in intensity

(C)18

Expected changes in intensity (C)

INTSF

or

WKN

or

NC

WKN

INTSF

NC

A-6

Ref No.




2.7 Forecast position

(C)18, 19, 28

Forecast position of volcanic ash cloud or the centre of the TC or other hazardous

phenomena25

at the

end of the validity period of the SIGMET message (C)

1a) Specific to Tropical Cyclone only.

FCST nnnnZ TC CENTRE Nnnnn or Snnnn Ennnnn or Wnnnnn FCST nnnnZ TC CENTRE Nnn or Snn Ennn or Wnnn

[AND]23

or

2a) Specific to Volcanic Ash only: A polygon defining an ash cloud. The end point shall be a repeat of the start point. Minimum 4 coordinates and not normally more than 7 coordinates.

FCST nnnnZ VA CLD APRX Nnn[nn] or Snn[nn] Wnnn[nn] or

Ennn[nn]– Nnn[nn] or Snn[nn] Wnnn[nn] or Ennn[nn] [ –

Nnn[nn] or Snn[nn] Wnnn[nn] or Ennn[nn]] [ – Nnn[nn] or

Snn[nn] Wnnn[nn] or Ennn[nn]]

or

2b) Specific to VA only: A zone, defined by a line of specified width, defining an ash cloud.

FCST nnnnZ VA CLD APRX nnKM (nnNM) WID LINE22

BTN

Nnn[nn] or Snn[nn] Wnnn[nn] or Ennn[nn]– Nnn[nn] or

Snn[nn] Wnnn[nn] or Ennn[nn] [ – Nnn[nn] or Snn[nn]

Wnnn[nn] or Ennn[nn]] [ – Nnn[nn] or Snn[nn] Wnnn[nn] or Ennn[nn]]

[AND]23

or

2c) affecting entire FIR or CTA

FCST nnnnZ ENTIRE FIR21

or

FCST nnnnZ ENTIRE CTA21

1a) Specific to Tropical Cyclone only.

FCST 2200Z TC CENTRE N2740 W07345

FCST 1600Z TC CENTRE S15 W110

or

2a) Specific to Volcanic Ash only: A polygon defining an ash cloud. The end point shall be a repeat of the start point. Minimum 4 coordinates and not normally more than 7 coordinates.

FCST 1700Z VA CLD APRX S15 E075 – S15 E081 –

S17 E083 – S18 E079 – S15 E075

or

2b) Specific to VA only: A zone defined by a line of specified width, defining an ash cloud.

FCST 1700Z VA CLD APRX 180KM WID LINE BTN S15

E075 – S15 E081 – S17 E083 – S18 E079

FCST 1700Z VA CLD APRX 90NM WID LINE BTN S15

E075 – S15 E081 – S17 E083 – S18 E079

or

2c) affecting entire FIR or CTA

FCST 1400Z ENTIRE FIR21

or

FCST 0300Z ENTIRE CTA21

or

A-7

Ref No.




or

3a) Specific to hazards other than TC or VA, an area of the FIR defined by a polygon. The end point shall be a repeat of the start point. Minimum 4 (including the last point being a repeat of the first point) coordinates, and not normally more than 7 coordinates.

FCST nnnnZ WI24 Nnn[nn] or Snn[nn] Wnnn[nn] or

Ennn[nn] – Nnn[nn] or Snn[nn] Wnnn[nn] or Ennn[nn] –

Nnn[nn] or Snn[nn] Wnnn[nn] or Ennn[nn][ - Nnn[nn] or

Snn[nn] Wnnn[nn] or Ennn[nn] – Nnn[nn] or Snn[nn]

Wnnn[nn] or Ennn[nn]]

or

3b) Specific to hazards other than TC or VA, in a sector of the FIR defined relative to specified line joining two points on the FIR boundary (or so close to the FIR boundary so as to leave no doubt that the intent is for the line to connect to the FIR boundary at that point).

FCST nnnnZ [N][NE][E][SE][S][SW][W][NW] OF [LINE]

Nnn[nn] or Snn[nn] Wnnn[nn] or Ennn[nn] – Nnn[nn] or

Snn[nn] Wnnn[nn] or Ennn[nn]

or

3c) Specific to hazards other than TC or VA, in a sector of the FIR defined relative to a line of latitude and a line of longitude (effectively a quadrant);

FCST nnnnZ N OF Nnn[nn] AND W OF Wnnn[nn] or

FCST nnnnZ N OF Nnn[nn] AND E OF Wnnn[nn] or

FCST nnnnZ S OF Nnn[nn] AND W OF Wnnn[nn] or

FCST nnnnZ S OF Nnn[nn] AND E OF Wnnn[nn] or

FCST nnnnZ N OF Nnn[nn] AND W OF Ennn[nn] or

FCST nnnnZ N OF Nnn[nn] AND E OF Ennn[nn] or

FCST nnnnZ S OF Nnn[nn] AND W OF Ennn[nn] or

FCST nnnnZ S OF Nnn[nn] AND E OF Ennn[nn] or

3a) Specific to hazards other than TC or VA, an area of the FIR defined by a polygon. The end point shall be a repeat of the start point. Minimum 4 coordinates (including the last point being a repeat of the first point), and not normally more than 7 coordinates.

FCST 1600Z WI N6030 E02550 – N6055 E02500 –

N6050 E02630 - N6030 E02550

FCST 0800Z WI N30 W067 – N32 W070 – N35 W068 -

N30 W067

or

3b) Specific to hazards other than TC or VA, in a sector of the FIR defined relative to specified line joining two points on the FIR boundary (or so close to the FIR boundary so as to leave no doubt that the intent is for the line to connect to the FIR boundary at that point).

FCST 2100Z NE OF N2500 W08700 – N2000 W08300 FCST 1200Z NE OF LINE N2500 W08700 – N2000 W08300 FCST 1600Z S OF S14 E150 – S14 E155 FCST 2000Z S OF LINE S14 E150 – S14 E155

or

3c) Specific to hazards other than TC or VA, in a sector of the FIR defined relative to a line of latitude and a line of longitude (effectively a quadrant);

FCST 1600Z S OF N3200 AND E OF E02000

FCST 0600Z S OF S3215 AND W OF E10130

FCST 1230Z S OF N12 AND W OF E040 FCST 0300Z N OF N35 AND E OF E078

A-8

Ref No.




or

3d) Specific to hazards other than TC or VA, in a sector of the FIR defined relative to a line of latitude or longitude (effectively a segment);

FCST nnnnZ N OF Nnn[nn] or

FCST nnnnZ S OF Nnn[nn] or

FCST nnnnZ N OF Snn[nn] or

FCST nnnnZ S OF Snn[nn] or

FCST nnnnZ W OF Wnnn[nn] or

FCST nnnnZ E OF Wnnn[nn] or

FCST nnnnZ W OF Ennn[nn] or FCST nnnnZ E OF Ennn[nn]

or

3e) Specific to hazards other than TC or VA, at a point:

FCST nnnnZ Nnn[nn] Wnnn[nn] or

FCST nnnnZ Nnn[nn] Ennn[nn] or

FCST nnnnZ Snn[nn] Wnnn[nn] or

FCST nnnnZ Snn[nn] Ennn[nn]

or

3d) Specific to hazards other than TC or VA, in a sector of the FIR defined relative to a line of latitude or longitude (effectively a segment);

FCST 1600Z N OF S2230 FCST 1130Z S OF S43 FCST 0800Z E OF E01700 FCST 1200Z E OF W005

or

3e) Specific to hazards other than TC or VA, at a point:

FCST 0800Z N5530 W02230 FCST 1500Z S12 E177

Cancellation of

SIGMET (C)27

Cancellation of SIGMET referring to its identification

CNL SIGMET n

nnnnnn/nnnnnn

CNL SIGMET nn

nnnnnn/nnnnnn

CNL SIGMET nnn

nnnnnn/nnnnnn

or

CNL SIGMET n

nnnnnn/nnnnnn VA MOV TO nnnn FIR21

CNL SIGMET 2

102000/11000027

CNL SIGMET 12

101200/10160027

CNL SIGMET A12

031600/03200027

CNL SIGMET 3

251030/251630 VA MOV TO YUDO FIR27

A-9

Ref No.




CNL SIGMET nn

nnnnnn/nnnnnn VA MOV TO nnnn FIR21

CNL SIGMET nnn


CNL SIGMET 06


CNL SIGMET B10


Table A-1: Expanded SIGMET template

A-10

Footnotes to table: (note: the number in brackets at the end of each footnote refers to the footnote

reference in Table A6-1 of Annex 3, 18th Edition, July 2013).

1. See 4.1. “Recommendation.— In cases where the airspace is divided into a flight information

region (FIR) and an upper flight information region (UIR), the SIGMET should be identified

by the location indicator of the air traffic services unit serving the FIR. Note.— The SIGMET

message applies to the whole airspace within the lateral limits of the FIR, i.e. to the FIR and to

the UIR. The particular areas and/or flight levels affected by the meteorological phenomena

causing the issuance of the SIGMET are given in the text of the message.” (2)

2. Fictitious location. (3)

3. In accordance with 1.1.3 “The sequence number referred to in the template in Table A6-1 shall

correspond with the number of SIGMET messages issued for the flight information region

since 0001 UTC on the day concerned. The meteorological watch offices whose area of

responsibility encompasses more than one FIR and/or CTA shall issue separate SIGMET

messages for each FIR and/or CTA within their area of responsibility.” (4)

4. As per 1.1.4 “In accordance with the template in Table A6-1, only one of the following

phenomena shall be included in a SIGMET message, using the abbreviations as indicated

below [list of SIGMET phenomena follows]” (7)

5. In accordance with 4.2.1 a) “obscured (OBSC) if it is obscured by haze or smoke or cannot be

readily seen due to darkness”. (8)

6. In accordance with 4.2.4 “Hail (GR) should be used as a further description of the

thunderstorm, as necessary” (9)

7. accordance with 4.2.1 b) “embedded (EMBD) if it is embedded within cloud layers and cannot

be readily recognized” (10)

8. In accordance with 4.2.2 “An area of thunderstorms should be considered frequent (FRQ) if

within that area there is little or no separation between adjacent thunderstorms with a

maximum spatial coverage greater than 75 per cent of the area affected, or forecast to be

affected, by the phenomenon (at a fixed time or during the period of validity)” (11)

9. In accordance with 4.2.3 “Squall line (SQL) should indicate a thunderstorm along a line with

little or no space between individual clouds.” (12)

10. Used for unnamed tropical cyclones. (13)

11. In accordance with 4.2.5 and 4.2.6 “Severe turbulence (TURB) should refer only to: low-level

turbulence associated with strong surface winds; rotor streaming; or turbulence whether in

cloud or not in cloud (CAT). Turbulence should not be used in connection with convective

clouds.” and “Turbulence shall be considered: a) severe whenever the peak value of the cube

root of EDR exceeds 0.7” (14)

12. In accordance with 4.2.7 “Severe icing (ICE) should refer to icing in other than convective

clouds. Freezing rain (FZRA) should refer to severe icing conditions caused by freezing rain”.

(15)

13. In accordance with 4.2.8 “A mountain wave (MTW) should be considered: a) severe whenever

an accompanying downdraft of 3.0 m/s (600 ft/min) or more and/or severe turbulence is

observed or forecast; and b) moderate whenever an accompanying downdraft of 1.75–3.0 m/s

(350–600 ft/min) and/or moderate turbulence is observed or forecast.” (16)

14. In accordance with 2.1.4. (17)

15. In accordance with 4.2.1 c). (18)

16. In accordance with 4.2.1 d). (19)

A-11

17. The use of cumulonimbus, CB, and towering cumulus, TCU, is restricted to AIRMETs in

accordance with 2.1.4. (20).

18. In the case of the same phenomenon covering more than one area within the FIR, these

elements can be repeated, as necessary. (21)

19. Only for SIGMET messages for volcanic ash cloud and tropical cyclones. (22)

20. Only for SIGMET messages for tropical cyclones. (23)

21. Only for SIGMET messages for volcanic ash. (24)

22. A straight line between two points drawn on a map in the Mercator projection or a straight line

between two points which crosses lines of longitude at a constant angle. (25)

23. To be used for two volcanic ash clouds or two centres of tropical cyclones simultaneously

affecting the FIR concerned. (26)

24. The number of coordinates should be kept to a minimum and should not normally exceed

seven. (27)

25. Optionally can be used in addition to Movement or Expected Movement. (28)

26. To be used for hazardous phenomena other than volcanic ash cloud and tropical cyclones. (29)

27. End of the message (as the SIGMET/AIRMET message is being cancelled). (30)

28. The levels of the phenomena remain fixed throughout the forecast period. (31)

29. During any SIGMET test message, no other information should be included after the specified

text. (N/A)

— — — — — — — —

B-1

APPENDIX B

SIGMET EXAMPLES

Note. ― The figures used in this appendix are intended simply to clarify the intent of the

SIGMET message in abbreviated plain language, and therefore how each SIGMET should be

constructed by MWOs and also interpreted by users. The figures used are not intended to give

guidance on how a SIGMET in graphical format should be produced.

Examples of ‘WS’ SIGMET. See the sections for SIGMET for volcanic ash only (WV) and SIGMET

for tropical cyclone only (WC) for examples specific to those phenomena.

Contents

General

1) An area of the FIR defined by a polygon.


2a) In a sector of the FIR defined relative to specified line joining two points on the FIR

boundary


(effectively a quadrant)

2c) In a sector of the FIR defined relative to a line of latitude or longitude (effectively a

segment)

3) At a specific point within the FIR

4) Volcanic Ash SIGMET only

Multiple areas of in SIGMET for volcanic ash

Covering entire FIR/CTA

Multiple areas in SIGMET for tropical cyclone

5) Tropical Cyclone SIGMET only

General

Explanation of fictional FIR.

In each of the examples below, a fictional FIR area is indicated, with portions of adjacent FIRs also

indicated. The FIR areas are overlaid on a coordinate grid, in order that the example plain language

SIGMETs can be explicitly related to the intended meaning.

B-2

For some cases, examples are given where the FIR has boundaries that are complex (country borders

for example, especially when defined by rivers)

Fictional FIR is used for the examples.

Repetition of start point as last coordinate.

In accordance with practices and procedures laid down for other aeronautical bulletins (i.e.

NOTAM), it is recommended that the last point of a polygon is a repeat of the first point of the

polygon. This will ensure that the polygon has been closed, and that no points have been

omitted.

'Direction' of encoding of the points of a polygon

In accordance with practices and procedures laid down for other aeronautical bulletins and

international practice (e.g. BUFR encoding of WAFS significant weather (SIGWX) forecasts),

it is recommended that the points of a polygon are provided in a 'clockwise' sense. This assists

automated systems in determining the 'inside' of polygons.

B-3

1) An area of the FIR defined by a polygon. The end point should be a repeat of the start point.

When the SIGMET does not include a ‘forecast position’ section.

YUDD SIGMET 2 VALID 101200/101600 YUSO –

YUDD SHANLON FIR/UIR SEV TURB FCST WI N4230 E02145 – N4315 E02115 –

N4345 E02145 – N4330 E02215 – N4245 E02230 - N4230 E02145 FL250/370

MOV ESE 20KT INTSF=

With an explicit forecast position:



N4345 E02145 – N4330 E02215 – N4245 E02230 - N4230 E02145 FL250/370

MOV ESE 20KT INTSF FCST 1600Z WI N4145 E02315 – N4230 E02200 – N4330

E02215 – N4315 E02345 - N4145 E02315=

B-4




N4130 E02200 – N4107 E02130 – N4123 E2045 - N4230 E02052 FL250/370

MOV SE 30KT WKN=




N4130 E02200 – N4107 E02130 – N4123 E02045- N4230 E02052 FL250/370

MOV SE 30KT WKN FCST 1600Z WI N4230 E02052 – N4145 E02245 – N4045

E02330 – N4040 E02248 – N4123 E02045- N4230 E02052 =



minimum and should not normally exceed seven'. However, some FIR boundaries are complex, and it

would be unrealistic to expect that a polygon would be defined that followed such boundaries exactly.

As such, some States have determined that the polygon points be chosen in relation to the complex

boundary such that the FIR boundary approximates, but is wholly encompassed by, the polygon, and

B-5

that any additional area beyond the FIR boundary be the minimum that can be reasonably and

practically described. Caution should however be exercised in those instances where international

aerodromes are located in close proximity to such a complex FIR boundary.

In the examples below, it would not be practical to follow the NE boundaries exactly. The point close

to N4330 E02245 is obviously a 'major' turning point along the FIR boundary, but the other, numerous

and complex turning points can only be approximated when constrained to seven points.




N4330 E02445 – N4200 E02455 – N4230 E02245- N4315 E02145 FL250/370

MOV SE 20KT WKN=




N4330 E02445 – N4200 E02455 – N4230 E02245- N4315 E02145 FL250/370

MOV SE 20KT WKN FCST 1600Z WI N4300 E02245 – N4415 E02315 – N4322

E02452 – N4155 E02445 – N4215 E02330- N4300 E02245=

B-6

2a) In a sector of the FIR defined relative to specified line joining two points on the FIR

boundary.



YUDD SHANLON FIR/UIR SEV TURB FCST NE OF LINE N4230 E02052 – N4100

E02430 FL250/370 MOV NE 15KT WKN=




E02430 FL250/370 MOV NE 15KT WKN FCST 1600Z NE OF LINE N4346 E02122 –

N4130 E02452=

B-7



E02430 FL250/370 MOV NE 15KT WKN FCST 1600Z NE OF LINE N4346 E02122 –

N4130 E02457=

2b) In a sector of the FIR defined relative to a line of latitude and a line of longitude (effectively a

quadrant)



YUDD SHANLON FIR/UIR SEV TURB FCST S OF N4300 AND W OF E02215

FL250/370 MOV S 12KT WKN=

B-8

When the SIGMET does include a ‘forecast position'.



YUDD SHANLON FIR/UIR SEV TURB FCST S OF N4300 AND W OF E02215

FL250/370 MOV S 12KT WKN FCST 1600Z S OF 4215 AND W OF E02215=

2d) In a sector of the FIR defined relative to a line of latitude or longitude (effectively a segment)



YUDD SHANLON FIR/UIR SEV TURB FCST N OF N43 FL250/370 MOV N 15KT WKN=

B-9

When the SIGMET does include a ‘forecast position’ section.


YUDD SHANLON FIR/UIR SEV TURB FCST N OF N437 FL250/370 MOV N 15KT WKN

FCST 1600Z N OF N44=


YUDD SHANLON FIR/UIR SEV TURB FCST N OF N438 FL250/370 MOV N 15KT WKN

FCST 1600Z N OF N44=

7 It would be equally valid to use 'N4300'. 8 It would be equally valid to use 'N4300'.

B-10

3) At a specific point within the FIR;



YUDD SHANLON FIR/UIR SEV TURB OBS N4245 E02230 FL250/370 STNR WKN=

4) Volcanic Ash SIGMET Only

When the VA SIGMET does not include a ‘forecast position’ section.


YUDD SHANLON FIR/UIR VA ERUPTION MT ASHVAL PSN N4315 E02115 VA CLD

OBS AT 1200Z WI N4315 E02145 – N4345 E02145 - N4230 E02215 – N4245

E02230 – N4230 E02145 - N4315 E02115 FL250/370 MOV ESE 20KT NC=

B-11

When the SIGMET does include a ‘forecast position’ section (no rate of movement).

For VA (eruption ceased, ash cloud persists downwind):



OBS AT 1200Z WI N4315 E02115 – N4345 E02145 N4330 E02215 – N4245

E02230 – N4230 E02145 - N4315 E02115 FL250/370 MOV ESE 20KT NC FCST

1800Z VA CLD APRX N4330 E02215 – N4315 E02345 – N4145 E02315 – N4230

E02200 - N4330 E02215=

For VA (eruption on-going):



OBS AT 1200Z WI N4315 E02115 - N4245 E02145 – N4330 E02215 –- N4245

E02230 – N4230 E02145 – N4315 E2115 FL250/370 MOV ESE 20KT NC FCST

1800Z VA CLD APRX N4315 E02115 - N4330 E02215 – N4315 E02345 – N4145

E02315 – N4230 E02200 – N4315 E02115=

B-12

For VA (eruption ceasing, ash dispersing):



OBS AT 1200Z WI N4315 E02115 - N4345 E02145 – N4330 E02215 – N4245

E02130 - N4230 E02145 N4315 E02115 FL250/370 MOV ESE 20KT WKN FCST

1800Z NO VA EXP=

For VA (eruption on-going), defining the area affected as a line of specified width:



FCST 1200Z FL310/450 100KM WID LINE BTN N4330 E02200 – N4315 E02230 –

N4230 E02300 – N4145 E02230 – N4130 E02145 NC FCST 1800Z VA CLD APRX

100KM WID LIN BTN N4330 E02200 – N4315 E02300 – N4215 E02415 – N4115

E02400 – N4030 E02315=

B-13

5) Covering entire FIR (volcanic ash only).


YUDD SHANLON FIR/UIR SEV TURB FCST ENTIRE FIR FL250/370 STNR WKN=

Multiple areas in SIGMET for volcanic ash.

Strictly, the only way to include a second instance of a volcanic ash cloud in a SIGMET message is to

use the 'AND' option in the 'Forecast position' section.

In the example below, two areas of volcanic ash cloud (at different levels) are forecast to move as

described. The normal courier font refers to the northernmost areas of ash, and the italicised font refers

to the southernmost areas of ash during the period. 'AND' is highlighted in bold to identify the

separation of the two features.



OBS AT 1200Z WI N4315 E02115 – N4345 E02145 N4330 E02215 – N4245

E02230 – N4230 E02145 - N4315 E02115 FL250/370 MOV ESE 20KT NC FCST

1800Z VA CLD APRX N4330 E02215 – N4315 E02345 – N4145 E02315 – N4230

E02200 - N4330 E02215 AND N4200 E02115 – N4217 E02130 – N4145 E02200

– N4130 E02130 – N4200 E02100 FL150/300 MOV ESE 20KT NC FCST 1800Z VA

B-14

CLD APRX N4200 E02145 – N4145 E02215 – N4100 E02215 - N4130 E02130 -

N4200 E02145=

The above only works if there are two instances of ash at the start and end of the period. If the number

of ash areas is different at the start and end, it is recommended that separate SIGMETs be issued as

necessary.

6) Tropical Cyclone SIGMET Only


YUDD SHANLON FIR/UIR TC GLORIA FCST AT 1200Z N2200 W06145 CB TOP

FL500 WI 75NM OF CENTRE MOV NW 20KT WKN FCST 1800Z TC CENTRE N2330

W06315=

Multiple areas in SIGMET for tropical cyclone.

Strictly, the only way to include a second instance of a tropical cyclone in a SIGMET is to use the

'AND' option in the 'Forecast position' section.

The example below demonstrates how two separate TCs, and the CB within a specified radius of those

TCs, can be described. The normal courier font refers to TC Gloria, and the italicised font refers to TC

Harriet. 'AND' is highlighted in bold to identify the separation between information for the two

features.

B-15


YUDD SHANLON FIR/UIR TC GLORIA FCST AT 1200Z N2100 W06200 CB TOP

FL500 WI 20NM OF CENTRE MOV NW 20KT WKN FCST 1800Z TC CENTRE N2230

W06330 AND TC HARRIET FCST AT 1200Z N2215 W06100 CB TOP FL400 WI 20NM

OF CENTRE MOV NW 20KT WKN FCST 1800Z TC CENTRE N2345 W06230=

— — — — — — — —

C-1

APPENDIX C

SIGMET TEST PROCEDURES

CHAPTER 1 ― REGIONAL SIGMET TEST PROCEDURES

1. Introduction

1.1. The Meteorology Divisional Meeting (2002) formulated Recommendation 1/12 b),

Implementation of SIGMET requirements, which called, inter alia, for the relevant planning and

implementation regional groups (PIRGs) to conduct periodic tests of the issuance and reception of

SIGMET messages, especially those for volcanic ash.

1.2. This document describes the procedures for conducting regional SIGMET tests as described in

this document. The test procedures encompass all the three types of SIGMET, as follows:

SIGMET for volcanic ash (WV SIGMET);

SIGMET for tropical cyclone (WC SIGMET); and

SIGMET for other weather phenomena (WS SIGMET).

1.3. The requirements for dissemination of SIGMET are specified in Annex 3, Appendix 6, 1.2 and in

this guide (page 3-23).

1.4. Tropical cyclone and volcanic ash cloud SIGMETs will be referred to hereafter as WC SIGMET

(due to the T1T2 section of the WMO AHL being set to WC) and WV SIGMET (due to the T1T2 section of

the WMO AHL being set to WV) respectively. All other SIGMET types will be referred to by WS (due to

the T1T2 section of the WMO AHL being set to WS).

2. Purpose and scope of regional SIGMET tests

2.1. The purpose of the regional SIGMET tests is to check the awareness of participating MWOs of

the ICAO requirements for the issuance of SIGMET and the compliance of the States’ procedures for

preparation and dissemination of SIGMET bulletins with the relevant ICAO Standards and

Recommended Practices (SARPs) and regional procedures.

2.2. Note: an MWO is at liberty to issue SIGMET test messages for local reasons (i.e. testing of local

systems/routing etc.). Whilst such tests may not involve other MWOs or agencies directly, it is

recommended that the general principles of this guide be followed with regard to local, ad hoc testing.

2.3. Hereafter, references to 'SIGMET tests' or 'tests' should be understood to refer to regional

SIGMET tests.

2.4. The scope of the tests is to check also the interaction (where appropriate, depending on regional

requirements) between the tropical cyclone advisory centres (TCAC) and volcanic ash advisory centres

(VAAC), and the MWOs in their areas of responsibility. Therefore, where the issuance of WC and WV

SIGMET is being tested, the TEST SIGMET messages initiated by the MWO should normally be

triggered by a test advisory issued by the respective TCAC or VAAC.

C-2

2.5. The regional OPMET data banks (RODB) will monitor the dissemination by filing all TEST

SIGMETs and advisories and the corresponding reception times. The monitoring results for WC, WV and

WS SIGMET will be provided in the form of summaries to the SIGMET test focal points given in section

3.4.1.3 with a copy to the Regional Office concerned

2.6. A consolidated summary report will be prepared by both the SIGMET test focal points and

submitted to the ICAO regional office concerned. The report will include recommendations for

improvement of the SIGMET exchange and availability. The results of the tests should be reported to the

appropriate regional OPMET bulletin exchange/data management group and MET Sub-group meetings.

2.7. Participating States, for which discrepancies of the procedures or other findings are identified by

the tests, will be advised by the ICAO Regional Office and requested to take necessary corrective action.

3. SIGMET test procedures

3.1. Procedures for WC and WV SIGMET tests

3.1.1. Participating units

3.1.1.1. Tropical Cyclone Advisory Centres (TCAC): Darwin

Honolulu

Miami

Nadi

New Delhi

Tokyo

Réunion

3.1.1.2. Volcanic Ash Advisory Centres (VAAC): Anchorage

Darwin

Tokyo

Toulouse

Washington

Wellington

3.1.1.3. Regional OPMET Data Banks (RODB): Bangkok

Brisbane

Nadi

Singapore

Tokyo

3.1.1.4. Meteorological Watch Offices (MWO): All MWOs listed in FASID Tables MET 3A and MET 3B of the ASIA/PAC Basic ANP

and FASID (Doc 9673), under the responsibility of the corresponding TCACs and VAACs.

Note: The participation of MWOs of States outside ASIA/PAC region, but listed in Doc 9673 (FASID

Tables MET 3A and MET 3B) should be coordinated through the ICAO Regional Office concerned.

3.1.2. WV/WC SIGMET test messages

C-3

3.1.2.1. On the specified date for the test at 0200 UTC the participating VAAC and TCAC should

issue a TEST VA or TC advisory. To accommodate the MID Region in the WC SIGMET Test, TCAC

New Delhi will issue a TEST TC advisory at 0800 UTC on the specified date for the test only to MWOs

in the MID Region in addition to the 0200 UTC TEST TC advisory issued only to MWOs in the Asia

Region. The structure of the TEST advisories should follow the standard format given in Annex 3 with

indication that it is a test message as shown on pages C-6 and C-7.

3.1.2.2. MWOs, upon receipt of the TEST VA or TC advisory, should issue a TEST SIGMET for

volcanic ash (WV) or tropical cyclone (WC), respectively, and send it to all participating RODBs. The

WMO AHL, the first line of the SIGMET, and the FIR reference in the second line of the SIGMET

should be valid entries. The remainder of the body of the message should contain only the specified text

informing recipients in plain language that the message is a test. TEST SIGMETs should normally have

short validity periods (10 minutes), but where appropriate TEST SIGMET may be issued with validity

periods up to the maximum allowed (4 hours for WS, 6 hours for WC and WV').

3.1.2.3. If the MWO does not receive the TEST VA or TCA advisory within 30 minutes of the

commencement time of the test then they should still issue a TEST SIGMET indicating that the VAA or

TCA was not received. See pages C-7 and C-8 for examples of the test SIGMET message.

3.1.2.4. To avoid over-writing of a valid SIGMET, a TEST SIGMET for VA or TC should not be sent

in the case where there is a valid SIGMET of the same type for the MWO’s area of responsibility.

However, in this case the responsible MWO should notify the WV/WC SIGMET test focal point as given

in 3.4.1.3 so that they can be excluded from the analysis.

3.2. Procedures for WS SIGMET tests

Note. ― The WS SIGMET is initiated by the MWO at the designated time in 3.2.2. It is not

initiated by an advisory as in the WC and WV SIGMET tests.

3.2.1. Participating units

Each Regional Office should develop its own list of participating units, using the template below:

3.2.1.1. Regional OPMET Data Banks (RODB): Bangkok

Brisbane

Nadi

Singapore

Tokyo

3.2.1.2. Meteorological Watch Offices (MWO): All MWOs listed in FASID Table MET 1B of ASIA/PAC Basic ANP and FASID (Doc

9673).

3.2.2. WS SIGMET Test Message

3.2.2.1. The MWOs should issue a TEST SIGMET during the 10-minute period between 0200

UTC and 0210 UTC.

C-4

3.2.2.2. The WMO AHL, the first line of the SIGMET, and the FIR reference in the second line

of the SIGMET should be valid. The remainder of the body of the message should contain only the

specified text informing recipients in plain language that the message is a test. TEST SIGMETs should

normally have short validity periods (10 minutes), but where appropriate TEST SIGMET may be issued

with validity periods up to the maximum allowed (4 hours for WS, 6 hours for WC and WV').

3.3. Common procedures

3.3.1. Special procedure to avoid overwriting of a valid WV/WC/WS SIGMET

3.3.1.1. It is vital to ensure that TEST SIGMET is unique so that it is not confused with operational

SIGMET and avoid overwriting a valid operational SIGMET in an automated system. In order to prevent

this it is suggested that:

3.3.1.2. Test SIGMETs will use the next normally available sequence number for test SIGMET

messages or the first available sequence number of any pre-defined letter assigned to test SIGMETs for

those States identifying SIGMETs using an alphanumerical sequence number (ex: T1 or Z99)

For example, a SIGMET test is scheduled for 0200 UTC on the 29th. The TEST SIGMET

is issued as follows:

WSAU01 YBRF 290200

YBBB SIGMET Z99 VALID 290200/290210 YBRF-

YBBB BRISBANE FIR TEST SIGMET PLEASE DISREGARD=

3.3.2. The test date and time

3.3.2.1. ICAO Regional Office will set a date and time for each SIGMET test after consultation with

the participating VAACs, TCACs and RODBs. The information about the agreed date and time will be

sent to all States concerned by a State letter and copied to the States’ SIGMET Tests Focal Points.

3.3.2.2. Tests for different types of SIGMET should preferably be conducted on separate dates.

3.3.2.3. SIGMET tests for WC, WV and WS should be conducted at least yearly.

3.3.3. Dissemination of test SIGMETs and advisories

3.3.3.1. All TEST TC/VA advisories should be sent by the TCACs and VAACs to the participating

units, as specified in the Regional Air Navigation Plan. The relevant AFTN addresses should be

identified as part of the Region specific documentation.

3.3.3.2. All TEST SIGMETs should be sent by the MWOs to the participating units, as specified in the

Regional Air Navigation Plan identified by each Regional Office. The relevant AFTN addresses should

be identified as part of the Region specific documentation.

3.3.3.3. RODBs that are nominated as IROGs will relay the test bulletins to their corresponding IROG.

3.3.3.4. SIGMET tests should be terminated within 2 hours of the test start time. Exceptionally, where

the test requires SIGMETs to be valid for up to 4 hours, then tests may be extended to a maximum of 4

hours for WS SIGMET and 6 hours for WC and WV SIGMET.

C-5

3.3.4. Coordination with the ATS units

3.3.4.1. MWOs should inform the associated ATS units of the forthcoming SIGMET tests by a

suitable advanced notice.

3.4. Processing of the test messages and results

3.4.1.1. The RODBs should file all incoming TEST advisories and SIGMETs and perform an analysis

of the availability, timeliness of arrival and the correctness of the WMO bulletin headings. A SIGMET

TEST Summary Table, as shown on pages C-8 and C-9 of this guide, should be prepared by each RODB

and sent to the regional SIGMET test focal point given in section 3.4.1.3., with a copy to the ICAO

Regional Office.

3.4.1.2. The SIGMET test focal points should prepare the final report of the test and present to the

ICAO Regional Office. A summary report should be submitted to the next regional OPMET bulletin

exchange/data management group and MET Sub-group meetings.

3.4.1.3. The current SIGMET test focal points for the Asia/Pacific Region are as follows:

Asia/Pacific Region

WS SIGMET summary table sent to:

Ms. CHUA Guat Mui

Chief Technical Officer

Weather Services Department

Meteorological Service Singapore

P.O. Box 8, Singapore Changi Airport Post Office

SINGAPORE 918141

Tel: +65 (3) 6542 2861

Fax: +65 (3) 6542 2915

e-mail: [email protected]

WV/WC SIGMET summary table sent to:

Mr. Yuichi Yamakoshi

Senior Scientific Officer / Administration Division

Forecast Department, Japan Meteorological Agency


Tokyo 100-8122

JAPAN

Tel: +81 (3) 3212 8341

Fax: +81 (3) 3284 0180

e-mail: [email protected]

——————


C-6

SIGMET TEST PROCEDURES

Format of TEST Advisories and SIGMETs

1. Format of TEST Volcanic Ash Advisory

VA ADVISORY

DTG: YYYYMMDD/0200Z

VAAC: <<NAME OF VAAC>>

VOLCANO: TEST

PSN: UNKNOWN

AREA: <<NAME OF VAAC>> VAAC AREA

SUMMIT ELEV: UNKNOWN

ADVISORY NR: YYYY/nn

INFO SOURCE: NIL

AVIATION COLOUR CODE: NIL

ERUPTION DETAILS: NIL

OBS VA DTG: DD/GGggZ

OBS VA CLD: ASH NOT IDENTIFIABLE FROM SATELLITE DATA

FCST VA CLD +6 HR: DD/0800Z SFC/FL600 NO ASH EXP



RMK: THIS IS A TEST VA ADVISORY. MWO SHOULD NOW ISSUE A TEST

SIGMET FOR VA. PLEASE REFER TO THE LETTER FROM <<REGION>>

REGIONAL OFFICE DATED xxxxxxxxxx.

NXT ADVISORY: NO FURTHER ADVISORIES=

2. Format of TEST Tropical Cyclone Advisory

TC ADVISORY

DTG: YYYYMMDD/0200Z

TCAC: <<NAME OF TCAC>>

TC: TEST

NR: nn (actual number)

PSN: NIL

MOV: NIL

C: NIL

MAX WIND: NIL

FCST PSN +06HR: NIL

FCST MAX WIND +06HR: NIL

FCST PSN +12HR: NIL


FCST PSN +18HR: NIL


FCST PSN +24HR: NIL


C-7

RMK: THIS IS A TEST TC ADVISORY. MWO SHOULD NOW ISSUE A TEST

SIGMET FOR TC. PLEASE REFER TO THE LETTER FROM <<REGION>>

REGIONAL OFFICE DATED xxxxxxxxxx.

NXT MSG: NIL=

3. Format of TEST SIGMET for Volcanic Ash

WVXXii CCCC YYGGgg

CCCC SIGMET Z99 VALID YYGGgg/YYGGgg CCCC−

CCCC <<NAME>> FIR THIS IS A TEST SIGMET, PLEASE DISREGARD.

TEST VA ADVISORY NUMBER xx RECEIVED AT YYGGggZ=

or

WVXXii CCCC YYGGgg



TEST VA ADVISORY NOT RECIEVED=

Example: WVJP31 RJTD 170205

RJJJ SIGMET Z99 VALID 170205/170215 RJTD-

RJJJ FUKUOKA FIR THIS IS A TEST SIGMET, PLEASE DISREGARD.

TEST VA ADVISORY NUMBER 1 RECEIVED AT 170200Z=

WVJP31 RJTD 170205



TEST VA ADVISORY NOT RECEIVED=

4. Format of TEST SIGMET for Tropical Cyclone

WCXXii CCCC YYGGgg



TEST TC ADVISORY NUMBER xx RECEIVED AT YYGGggZ=

or

WCXXii CCCC YYGGgg



TEST TC ADVISORY NOT RECEIVED=

Example: WCJP31 RJTD 100205


C-8


TEST TC ADVISORY NUMBER 1 RECEIVED AT 180200Z=

WCJP31 RJTD 100205



TEST TC ADVISORY NOT RECEIVED=

5. Format of TEST SIGMET for other weather phenomena

WSXXii CCCC YYGGgg


CCCC <<NAME>> FIR THIS IS A TEST SIGMET, PLEASE DISREGARD=

Example: WSJP31 RJTD 240205


RJJJ FUKUOKA FIR THIS IS A TEST SIGMET, PLEASE DISREGARD=

——————

CHAPTER 2 ― SAMPLE TABLE TO USED BY REGIONAL OPMET DATA BANKS

Name of RODB Tokyo

Date of Test 2011/11/17

Target (VA or TC) VA

VA Advisories (FV)

TTAAii CCCC YYGGgg Received Time(UTC) Comments/Remarks

FVAK23 PAWU 170159 01:59:29

FVAU01 ADRM 170201 02:01:53

FVFE01 RJTD 170200 02:00:09

FVPS01 NZKL 170207 02:08:27

FVXX02 LFPW 170202 02:02:41

FVXX25 KNES 170200 02:02:01

VA SIGMET (WV)

TTAAii CCCC YYGGgg MWO FIR Received Time(UTC) Comments/Remarks

WVAK01 PAWU 170200 PAWU PAZA 02:00:11

WVAU01 ADRM 170201 YDRM YBBB 02:02:04

WVCI31 RCTP 170205 RCTP RCAA 02:04:58

WVCI33 ZBAA 170205 ZBAA ZBPE 02:05:26

WVCI34 ZSSS 170205 ZSSS ZSHA 02:02:34

WVCI35 ZJHK 170201 ZJHK ZJSA 02:03:34

WVCI36 ZUUU 170205 ZUUU ZPKM 02:11:04

WVCI37 ZLXY 170205 ZLXY ZLHW 02:07:44

WVCI38 ZYTX 170205 ZYTX ZYSH 02:01:50

WVCI39 ZWWW 170202 ZWWW ZWUQ 02:02:40

WVCI45 ZHHH 170204 ZHHH ZHWH 02:08:52

C-9

WVFJ01 NFFN 170000 NFFN NFFF 02:15:46

WVIN31 VOMM 170201 VOMM VOMF 02:09:57

WVJP31 RJTD 170205 RJTD RJJJ 02:06:24

WVKP31 ZUUU 170206 ZUUU VDPP 02:12:23

WVLA31 VLVT 170200 VLVT VLVT 02:01:03

WVMS31 WMKK 170205 WMKK WBFC 02:04:28

WVPA01 PHFO 170201 PHFO KZAK 02:02:09

WVPH31 RPLL 170210 RPLL RPHI 02:08:43

WVPN01 KKCI 170200 KKCI KZAK 02:00:11

WVRA31 RUCH 170205 RUCH UIAA 02:08:01

WVRA31 RUHB 170206 RUHB UHHH 02:07:57

WVRA31 RUMG 170205 RUMG UHMM 02:08:59

WVRA31 RUPV 170200 RUPV UHMP 02:09:13

WVRA31 RUSH 170205 RUSH UHSS 02:04:22

WVRA31 RUVV 170202 RUVV UHWW 02:03:13

WVRA32 RUPV 170200 RUPV UHMA 02:06:01

WVRA32 RUYK 170207 RUYK UELL 02:07:28

WVRA33 RUHB 170202 RUHB UHBB 02:02:49

WVSR20 WSSS 170205 WSSS WSJC 02:05:38

WVSS20 VHHH 170202 VHHH VHHK 02:03:05

WVTH31 VTBS 170211 VTBS VTBB 02:13:53

WVVS31 VVGL 170200 VVGL VVNB 02:05:06

WVVS31 VVGL 170208 VVGL VVTS 02:14:38

― END ―

ROBEX WG/12


C6 - 1

Proposed Changes provided by Hong Kong-China to the draft Asia/Pacific Regional SIGMET

Guide (5th

Edition) (contained in Attachment C5)

1) Add “which may affect safety of aircraft operations” after “hazardous weather phenomena” in

para. 1.1.1 and 2.1.1 to align with the definition given in ICAO Annex 3 and the priority

indicator “FF” used in disseminating SIGMET as a flight safety message;

2) For illustration of best practice examples, the optional time group “AT GGggZ” be included

as far as possible in all the examples of the draft when “FCST” is used for element “Observed

and forecast phenomenon”;

3) Add an example describing a zone of volcanic ash cloud defined by FLnnn/nnn [APRX

nnnKM BY nnnKM] for completeness sake;

4) Move the background information of the jargons (WS SIGMET, WC SIGMET and WV

SIGMET) given in Appendix C (SIGMET Test Procedures) to Section 3.5.1 (regarding WMO

header) of the main text;

5) Reinstate the explanation of the usage of optional group [BBB] in Section 3.5.1 which has

been deleted in the latest draft;

6) Replace the example given on page B-13 to illustrate the use of “ENTIRE FIR” by one for

volcanic ash cloud instead of severe turbulence as the use of “ENTIRE FIR/CTA” is restricted

to volcanic ash only; and

7) Reinstate the table of the WMO headings for SIGMET bulletins used by Asia/Pacific MWOs

as given in Appendix H to the current Asia/Pacific Regional SIGMET Guide (4th Edition,

Amendment No. 10 dated 14-11-2013) and the table of WMO headings for TC and VA

advisory bulletins is given in Appendix I as these tables in the current SIGMET Guide are the

only document consolidating all the relevant WMO headings in the Region and this

information is not available in other documents for the Region such as Asia and Pacific

Regions Air Navigation Plan and ROBEX Handbook.

_ _ _ _ _ _ _ _ _ _ _ _ _

ROBEX WG/12


C7 - 1

Paragraph Suggested changes provided by Australia to the draft Asia/Pacific Regional SIGMET

Guide (5th Edition) (contained in Attachment C5)

1.1.2 Remove underline from Doc 8896

2.2.8b) Need to clarify to who Special AIREP is to be forwarded to if a SIGMET is not issued.

3.2.1 EMBD TS – What does 'readily recognized' mean? By whom/what? Can this be satellite,

manual obs, pilot?

3.2.1 SQL TS (& TSGR) – What guidance can be provided for 'little or no space'? Does 'cloud'

really mean CB cloud?

3.5.3.1, Table 5 Add: M (for mandatory) or C (for conditional) in relevant columns.

3.5.3.4 … the time of commencement of the phenomenonvalidity.

3.5.3.5 … by a polygon. . (ie. remove the second full-stop)

3.5.3.6 Add: nnnn/nnnFT

3.5.3.6 FL250/FL290

3.5.3.7 MOV <direction><speed>KMH[KT]

or MOV <direction><speed>KT

3.5.3.9 Note: - Annex 3 (18th Edition, July 2013) enables SIGMET to contain explicit forecast

position for the end of the validity period relating to for all SIGMET-related hazardous

phenomena other than volcanic ash or tropical cyclone.

3.5.3.9 The forecast position ……

…….. S23 E107

Refer to section 3.5.3.5 for examples.

3.5.3.9 Note: - Currently …….forecast positions. If levels differ significantly then separate

SIGMET should be issued.


3.5.4.6 Add: nnnn/nnnFT

3.5.4.6 FL250/FL290

3.5.4.6 Should also include the following at the end of 3.4.5.6 to reflect the intent of Annex 3,

Chapter 7, clause 7.1.4:

The SIGMET should be based on the VAA unless additional information is available. This

additional information must be forwarded to the responsible VAAC without delay.



3.5.4.9 Add: Refer to graphical examples in Appendix B.

Consideration should be given to having the textual examples reflecting specific graphical

examples in Appendix B.

3.5.4.9 Underline to indicate a sub-heading: Inclusion of multiple instances of volcanic ash

phenomena.


3.5.5.6 CB TOP [ABV or BLW] <FLnnn> WI <nnnKM or nnnNM> OF CENTRE



Appendices Many of the Appendices are missing. They should be:

Appendix A — SIGMET Guidance Table: Simplified from Annex 3 Table A6-1 ........... A-1

Appendix B — SIGMET Examples ........................................................................................ B-1

Appendix C — FASID Table MET 1B – Meteorological Watch Offices .............................. C-1

Appendix D — FASID Table MET 3A – Tropical Cyclone Advisory Centres ...................... D-1

Appendix E — FASID Table MET 3B – Volcanic Ash Advisory Centres ............................ E-1

Appendix F — WMO Headings for SIGMET bulletins ......................................................... F-1

Appendix G — WMO Headings for Advisory bulletins ......................................................... G-1

Appendix H — Dissemination addresses ……………………………………... ..................... H-1

Appendix I — SIGMET test procedures ……………………………………... .................... I-1

Appendix J — VAAC backup test procedures ……………………………………... ........... J-1

report of - ICAO

Documents

Transcript of report of - ICAO