AMC & GM to Part-MET — Issue 1, Amendment 2

Annex IV to ED Decision 2022/004/R ‘AMC and GM to Part-MET — Issue 1, Amendment 2’

The text of the amendment is arranged to show deleted, new or amended text as shown below: — deleted text is struck through; — new or amended text is highlighted in blue; — an ellipsis ‘[…]’ indicates that the rest of the text is unchanged.

Annex V to ED Decision 2017/001/R is amended as follows:

GM1 MET.OR.100 Meteorological data and information

GENERAL — TERMS IN PART-MET

Whereas ‘provide’ is used solely in connection with the provision of MET service, ‘issue’ is used solely in connection with cases where the obligation specifically extends to sending out (disseminate) the information to a user. Furthermore, ‘supply’ is used solely in connection with cases where either ‘issue’ or ‘disseminate’ applies.

GM12 MET.OR.100 Meteorological data and information GM1 MET.OR.110 Meteorological information exchange requirements

GENERAL

Operational meteorological information is disseminated to international OPMET databanks and tothe centres responsible for the operation of the aeronautical fixed service iInternet-based services. as specified in GM1 MET.0R.110.

AMC1 MET.OR.200(a)(1) Meteorological reports and other information

ROUTINE OBSERVATIONS

Aeronautical Mmeteorological stations should make routine observations throughout the 24 hours of each day or as determined by the competent authority.

GM1 MET.OR.200(a)(2)Meteorological reports and other information

Local special reports should be transmitted to local air traffic services units as soon as the specified conditions occur. By agreement between the aeronautical meteorological station and the appropriate ATS unit, local special reports are not required to be disseminated in respect of: […]

GM1 MET.OR.200(a)(3) Meteorological reports and other information

(a) For aerodromes not serving scheduled international commercial air transport operations, an aeronautical meteorological station may disseminate hourly METAR. (b) Such dissemination, as well as the criteria to provide SPECI, should be agreed between the competent authority and the meteorological services provider.

AMC2 MET.OR.200(a)(3) Meteorological reports and other information

DISSEMINATION OF METAR

METAR, and corrections thereto, should be disseminated to international OPMET databanks and to centres responsible for the operation of aeronautical fixed service Internet-based services.

GM1 MET.OR.200(a)(3) Meteorological reports and other information

Procedures for disseminating METAR to users are described in ICAO EUR Doc 018 ‘EUR OPMET DATA MANAGEMENT HANDBOOK’.

AMC1 MET.OR.200(b) Meteorological reports and other information

SPECI

Where required, SPECI should be issued whenever changes when the following criteria are met:

(a) when the mean surface wind direction has changed by 60° or more from that given in the latest report, the mean speed before and/or after the change being 10 kt or more; (b) when the mean surface wind speed has changed by 10 kt or more from that given in the latest local report; (c) when the variation from the mean surface wind speed (gusts) has changed by 10 kt or more from that at the time of the latest local report, the mean speed before and/or after the change being 15 kt or more; (d) when the onset, cessation or change in intensity of any of the following weather phenomena occurs: (1) freezing precipitation; (2) moderate or heavy precipitation, including showers thereof; and (3) thunderstorm, with precipitation; (e) when the onset or cessation of any of the following weather phenomena occurs: (1) freezing fog; (2) thunderstorm, without precipitation; (f) when the amount of a cloud layer below 1 500 ft (450 m) changes: (1) from scattered (SCT) or less to broken (BKN) or overcast (OVC); or (2) from BKN or OVC to SCT or less.

AMC2 MET.OR.200(b) Meteorological reports and other information

DISSEMINATION OF SPECI

SPECI dissemination should be identical to METAR dissemination.

GM1 MET.OR.200(b) Meteorological reports and other information

DISSEMINATION OF SPECI

SPECI representing a deterioration of meteorological conditions should be disseminated immediately after the observation. SPECI representing a deterioration of one weather element and an improvement in another weather element should also be disseminated immediately after the observation and should then be treated as deterioration reports.

GM2 MET.OR.200(b) Meteorological reports and other information

DISSEMINATION OF SPECI

A SPECI representing an improvement in conditions should be disseminated only after the improvement has been maintained for 10 minutes; it should be amended before dissemination, if necessary, to indicate the conditions prevailing at the end of that 10-minute period.

GM3 MET.OR.200(b) Meteorological reports and other information

Procedures for disseminating SPECI to users are described in ICAO EUR Doc 018 ‘EUR OPMET DATA MANAGEMENT HANDBOOK’.

AMC1 MET.OR.200(cd) Meteorological reports and other information

[…]

AMC1 MET.OR.210 Observing meteorological elements

DISPLAY

Where automated equipment forms part of an integrated semi-automatic observing system, displays of data which are made available to the local ATS units should be a subset of and displayed parallel to those available in the aeronautical meteorological stations or aerodrome meteorological offices. In those displays, each meteorological element should be annotated to identify, as appropriate, the locations for which the element is representative.

AMC1 MET.OR.220(a) Aerodrome forecasts

DISSEMINATION OF TAF

TAF, as well as corrections and amendments thereto, should be disseminated to international OPMET databanks and to centres responsible for the operation of aeronautical fixed service Internet-based services.

GM1 MET.OR.220(a) Aerodrome forecasts

DISSEMINATION OF TAF

TAF and amendments thereto are disseminated to international OPMET databanks and the centres designated for the operation of the aeronautical fixed service Internet-based services. Guidance on the dissemination of TAF to users is provided in ICAO EUR Doc 018 ‘EUR OPMET DATA MANAGEMENT HANDBOOK’.

GM1 MET.OR.225(b) Forecasts for landing

TREND FORECAST

A TREND forecast is understood as being a concise statement of the expected significant changes in the meteorological conditions at that aerodrome to be appended to a METAR or SPECI, and if agreed between the aeronautical meteorological station and the appropriate ATS unit, as well in a local routine report and a local special report as well.

AMC1 MET.OR.235(c) Aerodrome warnings and wind shear warnings and alerts

Wind shear alerts should be updated at least every minute. They should be cancelled as soon as the headwind/tailwind change falls below 15 kt (7.5 m/s).

GM1 MET.OR.240(a)(1) Information for use by operator or flight crew GM1 MET.OR.240(ab)(2) Information for use by operator or flight crew

GENERAL

[…]

GM1 MET.OR.240(ad)(4) Information for use by operator or flight crew

SIGMET

[…]

GM1 MET.OR.240(e) Information for use by operator or flight crew

SPACE WEATHER ADVISORY

Space weather advisory information is received from space weather centres (SWXCs) in accordance with ICAO Annex 3 ‘Meteorological Service for International Air Navigation’ and ICAO Doc 10100 ‘Manual on Space Weather Information in Support of International Air Navigation’.

AMC1 MET.OR.245(f)(3) Meteorological watch and other information

AIRCRAFT IN FLIGHT

If the information requested from an aircraft in flight is not available in the associated meteorological watch office, that meteorological watch office should request the assistance of another meteorological watch office or another aerodrome meteorological office in providing it.

AMC2 MET.OR.250(a) SIGMET

DISSEMINATION OF SIGMET

SIGMET, and cancellations thereof, should be disseminated to international OPMET databanks and to centres responsible for the operation of aeronautical fixed service Internet-based services.

GM1 MET.OR.250(a) SIGMET

DISSEMINATION OF SIGMET

Procedures for the dissemination of SIGMET to users are described in ICAO EUR Doc 018 ‘EUR OPMET DATA MANAGEMENT HANDBOOK’. (a) SIGMET are disseminated to meteorological watch offices and WAFCs and to other meteorological offices. SIGMET for volcanic ash are also disseminated to VAACs. (b) SIGMET are disseminated to international OPMET databanks and the centres designated for the operation of the aeronautical fixed service Internet-based services.

AMC1 MET.OR.255(a) AIRMET

DISSEMINATION OF AIRMET

AIRMET, and cancellations thereof, should be disseminated to international OPMET databanks and to centres responsible for the operation of aeronautical fixed service Internet-based services.

GM1 MET.OR.255(a) AIRMET

DISSEMINATION OF AIRMET

Procedures for the dissemination of AIRMET to users are described in ICAO EUR Doc 018 ‘EUR OPMET DATA MANAGEMENT HANDBOOK’. (a) AIRMET are disseminated to meteorological watch offices in adjacent flight information regions and to other meteorological watch offices or aerodrome meteorological offices, as agreed by the competent authorities concerned. (b) AIRMET are transmitted to international operational meteorological databanks and the centres for the operation of the aeronautical fixed service Internet-based services.

Chapter 4 — Requirements for volcanic ash advisory centres (VAACs)

AMC1 MET.OR.265(a) Volcanic ash advisory centre responsibilities

DISSEMINATION OF VOLCANIC ASH ADVISORY

Volcanic ash advisory information should be disseminated to: (a) the European aviation crisis coordination cell;

(b) international OPMET databanks and to centres responsible for the operation of aeronautical fixed service Internet-based services.

GM2 MET.OR.265(a) Volcanic ash advisory centre responsibilities

DISSEMINATION OF VOLCANIC ASH ADVISORY

Procedures for the dissemination of volcanic ash advisory information to users are described in ICAO EUR Doc 018 ‘EUR OPMET DATA MANAGEMENT HANDBOOK’.

Chapter 5 — Requirements for tropical cyclone advisory centres (TCACs)

AMC1 MET.OR.270(a) Tropical cyclone advisory centre responsibilities

DISSEMINATION OF TROPICAL CYCLONE ADVISORY

Tropical cyclone advisory information should be disseminated to international OPMET databanks and to centres responsible for the operation of aeronautical fixed service Internet-based services.

GM1 MET.OR.270(a) Tropical cyclone advisory centre responsibilities

DISSEMINATION OF TROPICAL CYCLONE ADVISORY

Procedures for the dissemination of tropical cyclone advisory information to users are described in ICAO EUR Doc 018 ‘EUR OPMET DATA MANAGEMENT HANDBOOK’.

Chapter 6 — Requirements for world area forecast centres (WAFCs)

AMC1 MET.OR.275(a) World area forecast centre responsibilities

DISSEMINATION OF WORLD AREA FORECAST CENTRE (WAFC) GRIDDED GLOBAL FORECASTS AND FORECASTS OF SIGNIFICANT WEATHER (SIGWX)

World area forecast centre (WAFC) gridded global forecasts and forecasts of significant weather (SIGWX) should be disseminated to: (a) other WAFCs; (b) centres responsible for the operation of aeronautical fixed service Internet-based services.

AMC1 MET.TR.115(a) Meteorological bulletins

DATA TYPES AND CODE FORMS FOR METEOROLOGICAL INFORMATION

The data types and code forms applicable to specified meteorological information should be as follows:

(a) ICAO Meteorological Information Exchange Model (IWXXM) GML form; (b) alphanumeric code form; (c) abbreviated plain language form; (d) ‘gridded binary’ (GRIB) code form; (e) ‘binary universal form for the representation of meteorological data’ (BUFR) code form; (f) portable network graphics (PNG) form.

GM1 MET.TR.115(a) Meteorological bulletins

ALPHANUMERICAL FORMAT DATA TYPES AND CODE FORMS FOR METEOROLOGICAL INFORMATION

The format of the meteorological bulletins is understood to be that in alphanumerical format. The specifications for data types and code forms for meteorological information should be as follows: — IWXXM GML form; — IWXXM context (class) diagrams with identified features, types and allowed enumerations are published in the WMO Manual on Codes (WMO-No. 306) Volume I.3, Part D ‘Representations derived from data models’; — Guidance on the implementation of IWXXM is provided in ICAO Doc 10003 ‘Manual on the ICAO Meteorological Information Exchange Model (IWXXM)’; — Guidance on the implementation and exchange of IWXXM in the EUR Region is provided in ICAO EUR Doc 033 ‘Guidelines for the Implementation of OPMET Data Exchange using IWXXM in the EUR Region’; — Alphanumeric code form as specified in the WMO Manual on Codes (WMO-No. 306), Volume I.1, Part A ‘Alphanumeric Codes’; — Abbreviated plain language form as prescribed in the AMC (AMC1 MET.TR.115(a), AMC1 MET.TR.200(a), AMC1 MET.TR.200(a)(12), AMC3 MET.TR.215(a), AMC1 MET.TR.235(a), AMC1 MET.TR.235(c), AMC2 MET.TR.250(a), AMC1 MET.TR.255(a), AMC1 MET.TR.265, AMC1 MET.TR.270) describing the meteorological information being provided; — ‘Gridded binary’ (GRIB) code form as specified in the WMO Manual on Codes (WMO-No. 306), Volume I.2, Part B ‘Binary Codes’; — ‘Binary universal form for the representation of meteorological data’ (BUFR) code form as specified in the WMO Manual on Codes (WMO-No. 306), Volume I.2, Part B ‘Binary Codes’; — portable network graphics (PNG) form.

GM3 MET.TR.115(a) Meteorological bulletins

HEADING

Detailed specifications on format and contents of the heading are given in the WMO Publication No 386, ‘Manual on the Global Telecommunication System’, Volume I, and in the ICAO Doc 8896 ‘ICAO Manual of Aeronautical Meteorological Practice’(ICAO Doc 8896).

GM1 MET.TR.115(a)(2) Meteorological bulletins

LOCATION INDICATOR

ICAO location indicators are listed in ICAO Doc 7910 - Location Indicators.

AMC1 MET.TR.200(a) Meteorological reports and other information

TEMPLATE FOR LOCAL ROUTINE REPORT AND LOCAL SPECIAL REPORT

Local routine reports and local special reports should be issued in abbreviated plain language, in accordance with the template below.

GM1 MET.TR.200(a) Meteorological reports and other information

RANGES AND RESOLUTIONS — LOCAL ROUTINE REPORT AND LOCAL SPECIAL REPORT

(a) The ranges and resolutions for the numerical elements included in local routine reports and local special reports are shown below.

(b) The explanations for the abbreviations can be found in ICAO Doc 8400 ‘Procedures for Air Navigation Services — ICAO Abbreviations and Codes (PANS-ABC)’.

(a) The ranges and resolutions for the numerical elements included in the local routine report and local special report are shown below.

* There is no aeronautical requirement to report surface wind speeds of 100 kt (50 m/s) or more; however, provision has been made for reporting wind speeds up to 199 kt (99 m/s) for nonaeronautical purposes, as necessary. ** Under circumstances as specified in AMC1 MET.TR.205(e)(13); otherwise a resolution of 100 ft (30 m) is to be used. (b) The explanations for the abbreviations can be found in ICAO Doc 8400 ‘Procedures for Air Navigation Services — ICAO Abbreviations and Codes (PANS-ABC)’.

GM2 MET.TR.200(a) Meteorological reports and other information

LOCAL ROUTINE REPORT AND LOCAL SPECIAL REPORT — EXAMPLES OF ELEMENTS

Non-exhaustive examples of the different elements used in the formulation of local routine reports and local special reports are provided below.

GM1 MET.TR.200(a)(2) Meteorological reports and other information

LOCATION INDICATORS

The location indicators and their significations are published in ICAO Doc 7910 – ‘Location Indicators’.

AMC1 MET.TR.200(a)(4) Meteorological reports and other information

AUTOMATED REPORTING

Local routine report, and local special report, and METAR and SPECI from automatic observing systems should be identified with the word ‘AUTO’.

GM1 MET.TR.200(a)(4) Meteorological reports and other information

AUTOMATED REPORTING

METAR, lLocal routine report, and local special report, METAR and SPECI from automatic observing systems may be used as agreed between the aeronautical meteorological stations and the users.

AMC1 MET.TR.200(a)(12) Meteorological reports and other information

SUPPLEMENTARY INFORMATION — SEMI-AUTOMATIC OBSERVING SYSTEM

(a) In local routine report, and local special report, and in METAR and SPECI, when reported by a semi-automatic observing system, the following recent weather phenomena should be reported, up to a maximum of three groups, in the supplementary information: […]

AMC2 MET.TR.200(a)(12) Meteorological reports and other information

SUPPLEMENTARY INFORMATION — AUTOMATIC OBSERVING SYSTEM

In local routine report, and local special report, and in METAR and SPECI, when reported by an automatic observing system, the following recent weather phenomena should be reported, up to a maximum of three groups, in the supplementary information: […]

AMC3 MET.TR.200(a)(12) Meteorological reports and other information

SUPPLEMENTARY INFORMATION — WIND SHEAR

Information on wind shear should be included as supplementary information in local routine report, and local special report, and in METAR and SPECI, where local circumstances so warrant.

AMC4 MET.TR.200(a)(12) Meteorological reports and other information

SUPPLEMENTARY INFORMATION — SEA-SURFACE TEMPERATURE AND STATE OF THE SEA

In METAR and SPECI, information on sea-surface temperature and the state of the sea or the significant wave height, from aeronautical meteorological stations established on offshore structures in support of helicopter operations, should be included in the supplementary information.

GM1 to AMC1 MET.TR.200(a)(12) Meteorological reports and other information

SUPPLEMENTARY INFORMATION — RECENT WEATHER PHENOMENA

‘Recent weather phenomena’ is understood as being the weather phenomena observed at the aerodrome during the period since the last issued routine report or last hour, whichever is the shorter, but not at the time of observation.

GM12 to AMC3 MET.TR.200(a)(12) Meteorological reports and other information

SUPPLEMENTARY INFORMATION — LOCAL CIRCUMSTANCES

Local circumstances include but are not necessarily limited to wind shear of non-transitory nature such as might be associated with low-level temperature inversions or local topography.

GM3 MET.TR.200(a)(12) Meteorological reports and other information

SUPPLEMENTARY INFORMATION — WIND SHEAR

The inclusion of wind shear in the supplementary information is understood to be addressed, as a minimum, in local routine report, local special report, METAR and SPECI when reported by a semiautomatic observing system.

GM1 MET.TR.200(b) & (c) Meteorological reports and other information

EXAMPLE OF METAR AND LOCAL ROUTINE REPORT

GM1 MET.TR.200(b) Meteorological reports and other information AMC1 MET.TR.200(c) Meteorological reports and other information

METAR AND SPECI — CODE FORM

METAR and SPECI, and corrections thereto, should be encoded using: (a) the IWXXM GML form as specified in point (a) of AMC1 MET.TR.115(a); and (b) the alphanumeric code form for METAR as specified in point (b) of AMC1 MET.TR.115(a).

GM1 MET.TR.200(c)(1) Meteorological reports and other information

METAR — CODE FORM

The METAR code form is contained in the WMO Publication No 306, Manual on Codes, Volume I.1, Part A — Alphanumeric Codes.

GM1 MET.TR.200(c)(2) Meteorological reports and other information

METAR — DIGITAL FORM

(a) When METAR is disseminated in a digital form, this is in addition to the METAR code form. (b) Guidance on the information exchange model, GML, and the metadata profile is provided in the Manual on the Digital Exchange of Aeronautical Meteorological Information (ICAO Doc 10003).

GM1 MET.TR.200(f) Meteorological reports and other information

ISSUANCE OF LOCAL SPECIAL REPORTS AND SPECI

Point (f) in of MET.TR.200 relates to the list of criteria to provide local special reports and SPECI when a meteorological change occurs. The agreement between the meteorological service provider and the competent authority is introduced as these criteria are usually agreed with the competent authority. Also, in introducing this agreement, the nature of the transposed provision (Appendix 3, 2.3.3 Recommendation) of ICAO Annex 3 remains.

AMC1 MET.TR.200(f)(8) Meteorological reports and other information

ISSUANCE OF SPECI

Other criteria based on local aerodrome operating minima are to be considered in accordance with point (j) of AMC1 MET.TR.220(f).

AMC1 MET.TR.205(b)(1) Reporting of meteorological elements

VISIBILITY

In METAR and SPECI, visibility should be reported as prevailing visibility. When the visibility is not the same in different directions and: […]

AMC1 MET.TR.205(b)(3) Reporting of meteorological elements

VISIBILITY — VALUES

In local routine reports and local special reports, when instrumented systems are used for the measurement of visibility: […]

AMC1 MET.TR.205(c) Reporting of meteorological elements

RUNWAY VISUAL RANGE (RVR) — TOUCHDOWN ZONE VALUES

In METAR and SPECI: […]

AMC1 MET.TR.205(c)(1) Reporting of meteorological elements

(a) 50 m should be considered the lower limit, and 2 000 m the upper limit for RVR. (b) Outside ofBeyond these limits, local routine reports, and local special reports, and METAR and SPECI should merely indicate that the RVR is less than 50 or more than 2 000 m.

AMC1 MET.TR.205(c)(3) Reporting of meteorological elements

RUNWAY VISUAL RANGE (RVR) — VALUES FOR METAR AND SPECI

[…]

AMC1 MET.TR.205(d) Reporting of meteorological elements

PRESENT WEATHER PHENOMENA — AUTOMATIC OBSERVING SYSTEM

In local routine report, and local special report, and METAR and SPECI reported by an automatic observing system, the following types of present weather phenomena should be reported, using their respective abbreviations and relevant criteria, as appropriate: […]

AMC2 MET.TR.205(d) Reporting of meteorological elements

PRESENT WEATHER PHENOMENA — SEMI-AUTOMATIC OBSERVING SYSTEM

In local routine report, and local special report, and METAR and SPECI reported by a semi-automatic observing system, the following types of present weather phenomena should be reported, using their respective abbreviations and relevant criteria, as appropriate: […]

AMC3 MET.TR.205(d) Reporting of meteorological elements

PRESENT WEATHER PHENOMENA — UNIDENTIFIED PRECIPITATION (UP)

In automated local routine report, and local special report, and METAR and SPECI, in addition to drizzle (DZ), rain (RA) and snow (SN), the abbreviation ‘UP’ should be used for unidentified precipitation when the type of precipitation cannot be identified by the automatic observing system.

AMC1 MET.TR.205(d)(3) Reporting of meteorological elements

PRESENT WEATHER PHENOMENA — ADDITIONAL CHARACTERISTICS

(a) In local routine report, and local special report, and METAR and SPECI, only when reported by a semi-automatic observing system, the following characteristics of present weather phenomena, as necessary, should be reported using their respective abbreviations and relevant criteria, as appropriate: […] (b) In automated local routine report, and local special report, and METAR and SPECI, when showers (SH) referred to above cannot be determined based upon a method that takes account of the presence of convective cloud, the precipitation should not be characterised by ‘SH’.

AMC2 MET.TR.205(d)(3) Reporting of meteorological elements

PRESENT WEATHER PHENOMENA — INTENSITY

In local routine report, and local special report, and in METAR and SPECI, the relevant intensity or, as appropriate, the proximity to the aerodrome of the reported present weather phenomena should be indicated as follows: […] Vicinity (VC) Between approximately 8 and 16 km of the aerodrome reference point and used only in METAR and SPECI with present weather when not reported under AMC1 MET.TR.205(d)(3) and MET.TR.205(d)(3).

AMC1 MET.TR.205(e)(1) Reporting of meteorological elements

CLOUD

In local routine report, and local special report, and METAR and SPECI: […]

AMC2 MET.TR.205(e)(1) Reporting of meteorological elements

CLOUD — AUTOMATIC OBSERVING SYSTEM

When an automatic observing system is used to report local routine reports, and local special reports, and METAR and SPECI: […]

AMC1 MET.TR.205(e)(3) Reporting of meteorological elements

At aerodromes where low-visibility procedures are established for approach and landing, as agreed between the aeronautical meteorological station and the appropriate ATS unit, in local routine reports and local special reports, the height of cloud base should be reported in steps of 50 ft up to and including

300 ft (90 m) and in steps of 100 ft (30 m) between 300 ft (90 m) and 10 000 ft (3 000 m), and the vertical visibility in steps of 50 ft (15 m) up to and including 300 ft (90 m) and in steps of 100 ft (30 m) between

300 ft (90 m) and 2 000 ft (600 m).

GM2 MET.TR.210 Observing meteorological elements

OPERATIONALLY DESIRABLE ACCURACY OF OBSERVATION

AMC1 MET.TR.210(a) Observing meteorological elements

SURFACE WIND

[…]

(b) For METAR and SPECI, the surface wind observations should be representative of the conditions above the whole runway where there is only one runway, and the whole runway complex where there is more than one runway.

AMC1 MET.TR.210(a)(3) Observing meteorological elements

SURFACE WIND — AVERAGING

The averaging period for measuring variations from the mean wind speed (gusts) reported in accordance with MET.TR.205(a)(3)(iii) should be 3 seconds for local routine report, local special report, METAR, SPECI, and for wind displays used for depicting variations from the mean wind speed (gusts) in ATS units.

GM1 MET.TR.210(a)(3)(ii) Meteorological reports and other information

SURFACE WIND — AVERAGING — MARKED DISCONTINUITY

A marked discontinuity occurs when there is an abrupt and sustained change in wind direction of 30° or more, with a wind speed of 10 kt (5 m/s) before or after the change, or a change in wind speed of 10 kt (5 m/s) or more, lasting at least 2 minutes.

AMC1 MET.TR.210(b)(1) Observing meteorological elements

VISIBILITY — GENERAL

[…] (e) For METAR and SPECI, the visibility observations should be representative of the aerodrome.

AMC1 MET.TR.210(c)(12) Observing meteorological elements

RUNWAY VISUAL RANGE (RVR) — SITING

[…]

AMC1 MET.TR.210(c)(23) Observing meteorological elements

RUNWAY VISUAL RANGE (RVR) — RUNWAY LIGHT INTENSITY

[…] (d) In METAR and SPECI, the RVR should be based on the maximum light intensity available on the runway.

GM1 MET.TR.210(c)(23) Observing meteorological elements

RUNWAY VISUAL RANGE (RVR) — USE OF INSTRUMENTED SYSTEMS

[…]

GM2 MET.TR.210(c)(23) Observing meteorological elements

RUNWAY VISUAL RANGE (RVR)

[…]

GM1 MET.TR.210(c)(45)(ii)(B) Observing meteorological elements

RUNWAY VISUAL RANGE (RVR) — AVERAGING

[…]

AMC1 MET.TR.210(d)(1) Observing meteorological elements

PRESENT WEATHER — GENERAL

[…] (b) For METAR and SPECI, the present weather information should be representative of the conditions at the aerodrome and, for certain specified present weather phenomena, in its vicinity.

AMC1 MET.TR.210(e) Observing meteorological elements

CLOUDS — GENERAL

[…] (b) Cloud observations for METAR and SPECI should be representative of the aerodrome and its vicinity.

AMC1 MET.TR.210(f) Observing meteorological elements

AIR TEMPERATURE AND DEW-POINT TEMPERATURE

Observations of air temperature and dew-point temperature for local routine report, and local special report, and for METAR and SPECI, should be representative of the whole runway complex.

AMC1 MET.TR.210(f) Observing meteorological elements

AIR TEMPERATURE AND DEW-POINT TEMPERATURE

Observations of air temperature and dew-point temperature for local routine reports, and local special reports, and METAR and SPECI should be representative of the whole runway complex.

GM1 to AMC3 MET.TR.215(a) Forecasts and other information

[…]

GM1 MET.TR.215(e)(1) & (2) Forecasts and other information

MODEL CHARTS

This guidance provides examples of model charts. […]

(d) SIGNIFICANT WEATHER CHART (MEDIUM LEVEL)

MODEL SWM

AMC2 MET.TR.215(f) Forecasts and other information

CHARTS

(a) The minimum number of charts for flights between flight level 250 and flight level 630 should include a high-level SIGWX chart (flight level 250 to flight level 630) or a medium-level SIGWX chart (flight level 100 to flight level 450), if appropriate, and a forecast flight level 340250 hPa wind and temperature chart. […]

GM2 MET.TR.215(f) Forecasts and other information

MAP PROJECTIONS — CORRECT CONVERSION BETWEEN DIFFERENT MAP PROJECTIONS

When plotting shapes, particularly polygons, on maps, appropriate corrections are necessary if they are plotted on projections different to those used in the production of the original forecast area.

GM3 MET.TR.215(i) Forecasts and other information

CLIMATOLOGICAL DATA FOR AERODROME PLANNING PURPOSES

Climatological data required for aerodrome planning purposes areis set out in GM1 ADR-DSN.B.015(f) ‘Data to be used’.

GM2 MET.TR.220 Aerodrome forecasts

TAF — EXAMPLE OF CANCELLATION

GM3 MET.TR.220 Aerodrome forecasts

TAF — ACCURACY

The accuracy of TAF should be monitored using appropriate verification methodologies as agreed with the competent authority. The verification should identify the accuracy of the forecast against the required change criteria for the forecast elements: wind direction, wind speed, visibility, precipitation, cloud amount, and cloud height. Where provided, maximum and minimum temperature forecasts in TAF should be verified.Guidance on operationally desirable accuracy of TAF is given below:

AMC1 MET.TR.220(b) Aerodrome forecasts

TAF — CODE FORM

TAF, and amendments thereto, should be encoded using: (a) the IWXXM GML form as specified in point (a) of AMC1 MET.TR.115(a); and (b) the alphanumeric code form for TAF as specified in point (b) of AMC1 MET.TR.115(a).

GM2 MET.TR.220(b) Aerodrome forecasts

TAF CODE FORM

The TAF code form is contained in the WMO Publication No 306, Manual on Codes, Volume I.1, Part A — Alphanumeric Codes.

AMC1 MET.TR.220(c) Aerodrome forecasts

PERIOD OF VALIDITY

[…] (d) If so agreed between the competent authority and the meteorological services provider, TAF valid for 24 or 30 hours may be issued every 3 hours, and the validity should commence at 00, 03, 06, 09, 12, 15, 18 and 21 UTC. (de) At aerodromes with limited hours of operation, the beginning of the period of validity of a TAF should commence at least 1 hour prior to the aerodrome resuming operations, or more as agreed between the aerodrome meteorological office and the operators concerned, to meet planning requirements for flights that arrive at the aerodromes as soon as it is opened for use.

GM1 MET.TR.220(d) Aerodrome forecasts

TAF — DIGITAL FORM

(a) When TAF is disseminated in digital form, this is in addition to the TAF code form. (b) Guidance on the information exchange model, GML, and metadata profile is provided in ICAO Doc 10003 ‘Manual on the ICAO Meteorological Information Exchange Model’.

GM1 MET.TR.220(e)(2)(i) Aerodrome forecasts

TAF — PHENOMENA REDUCING VISIBILITY

When the visibility is forecast to be 5 000 m or less, the forecast weather phenomenon reducing visibility may be included in TAF, e.g. phenomena, and combinations thereof, such as FG, BR, HZ, -RA, -SN, etc.

GM1 MET.TR.220(f)(1) Aerodrome forecasts

TAF — USE OF CHANGE AND TIME INDICATORS

Guidance on the use of change and time indicators in TAF is given below:

GM1 MET.TR.225(c)(7)(ii) Forecasts for landing

TREND FORECASTS — USE OF CHANGE INDICATORS

Guidance on the use of change indicators in trend forecasts is given in the table below.

AMC1 MET.TR.225(c)(7)(iii) Forecasts for landing

USE OF CHANGE GROUPS — TEMPO

(a) When the change is forecast to begin and end wholly within the trend forecast period, the beginning and end of the change should be indicated by using the abbreviations ‘FM’ and ‘TL’ respectively, with their associated time groups.When the period of the temporary fluctuations in the meteorological conditions is forecast to begin and end wholly within the TREND forecast period, the beginning and end of the period of the temporary fluctuations should be indicated by using the abbreviations ‘FM’ and ‘TL’ respectively, with their associated time groups. (b) When the change is forecast to commence at the beginning of the trend forecast period but be completed before the end of that period, the abbreviation ‘FM’ and its associated time group should be omitted and only ‘TL’ and its associated time group should be used.When the period of the temporary fluctuations is forecast to commence at the beginning of the TREND forecast period but cease before the end of that period, the abbreviation ‘FM’ and its associated time group should be omitted and only ‘TL’ and its associated time group should be used. (c) When the change is forecast to begin during the trend forecast period and be completed at the end of that period, the abbreviation ‘TL’ and its associated time group should be omitted and only ‘FM’ and its associated time group should be used.When the period of the temporary fluctuations is forecast to begin during the TREND forecast period and cease by the end of that period, the abbreviation ‘TL’ and its associated time group should be omitted and only ‘FM’ and its associated time group should be used. (d) When the change is forecast to occur at a specified time during the trend forecast period, the abbreviation ‘AT’ followed by its associated time group should be used.When the period of the temporary fluctuations is forecast to commence at the beginning of the TREND forecast period and cease by the end of that period, both abbreviations ‘FM’ and ‘TL’ and their associated time groups should be omitted and the change indicator ‘TEMPO’ should be used alone. (e) When the change is forecast to commence at the beginning of the trend forecast period and be completed by the end of that period, or when the change is forecast to occur within the trend forecast period but the time is uncertain, the abbreviations ‘FM’, ‘TL’ or ‘AT’ and their associated time groups should be omitted and the change indicator ‘TEMPO’ should be used alone.

AMC1 MET.TR.235 Aerodrome warnings and wind shear warnings and alerts

AERODROME WARNINGS — FORMATTEMPLATE FOR AERODROME WARNINGS

(a) Aerodrome warnings should be issued in accordance with the template below or in another format where required by operators or aerodrome meteorological offices.

(b) When the above template is used, the sequence number referred to in the template should correspond to the number of aerodrome warnings issued for a given aerodrome since 00.01 UTC on the day concerned.

GM1 MET.TR.235 Aerodrome warnings and wind shear warnings and alerts

RANGES AND RESOLUTIONS — AERODROME WARNINGS

(a) The ranges and resolutions for the numerical elements included in aerodrome warnings are shown below.

(b) The explanations for the abbreviations can be found in ICAO Doc 8400 ‘Procedures for Air Navigation Services — ICAO Abbreviations and Codes (PANS-ABC)’.

RANGES AND RESOLUTIONS — AERODROME WARNINGS

(a) The ranges and resolutions for the numerical elements included in aerodrome warnings are shown below:

(b) The explanations for the abbreviations can be found in the Procedures for Air Navigation Services — ICAO Abbreviations and Codes (PANS ABC, ICAO Doc 8400).

GM2 MET.TR.235 Aerodrome warnings and wind shear warnings and alerts

AERODROME WARNINGS — EXAMPLES OF ELEMENTS

Non-exhaustive examples of the different elements used in the formulation of aerodrome warnings are provided below.

GM3 MET.TR.235 Aerodrome warnings and wind shear warnings and alerts

PHENOMENON (M) — TOX CHEM

When issuing an aerodrome warning due to information related to toxic chemical affecting an aerodrome and or volcanic ash deposition, the warning should be filed by means of the use of free text up to 32 characters, e.g. TOX CHEM FCST XXXX AIRPORT NEARBY WKN. (XXXX = ICAO Location Indicator)

AMC1 MET.TR.235(c) Aerodrome warnings and wind shear warnings and alerts

FORMAT OF WIND SHEAR WARNINGS — FORMAT

(a) The use of text in additional to the abbreviations listed in the template in Table 6 of Appendix 41 should be kept to a minimum. The additional text should be prepared in abbreviated plain language using ICAO-approved abbreviations and numerical values.

[…]

AMC2 MET.TR.250(a) SIGMET

SIGMET — CODE FORM

SIGMET, and cancellations thereof, should be encoded using: (a) the IWXXM GML form as specified in point (a) of AMC1 MET.TR.115(a); (b) abbreviated plain language as specified in point (c) of AMC1 MET.TR.115(a).

AMC3 MET.TR.250(a) SIGMET

FORMAT

SIGMET, when issued in graphical format, should be as specified below: (a) SIGMET FOR TROPICAL CYCLONE — MODEL STC

(b) SIGMET FOR VOLCANIC ASH — MODEL SVA, MERCATOR PROJECTION

(c) SIGMET FOR VOLCANIC ASH — MODEL SVA, POLAR STEREOGRAPHIC PROJECTION

(d) SIGMET FOR PHENOMENA OTHER THAN TROPICAL CYCLONES AND VOLCANIC ASH — MODEL SGE

AMC4 MET.TR.250(a) SIGMET

COORDINATION WITH NEIGHBOURING METEOROLOGICAL WATCH OFFICES (MWOs)

An MWO should coordinate SIGMET with neighbouring MWO(s), especially when the en-route weather phenomenon extends or is expected to extend beyond the MWO’s specified area of responsibility, to ensure harmonised SIGMET provision.

GM5 MET.TR.250(a) SIGMET

EXAMPLE OF SIGMET FOR RADIOACTIVE CLOUD

GM7 MET.TR.250(a) SIGMET

COORDINATION WITH NEIGHBOURING METEOROLOGICAL WATCH OFFICES (MWOs)

Guidance on the bilateral or multilateral coordination between MWOs of neighbouring States for the provision of SIGMET can be found in ICAO EUR Doc 014 ‘EUR SIGMET and AIRMET Guide’.

AMC1 MET.TR.250(c) SIGMET

SEQUENCE NUMBER

(a) The three-character sequence number should be constructed using a single letter identifying the phenomenon, followed by two numeric characters corresponding to the number of SIGMET issued for that phenomenon for the specified flight information region since 00.01 UTC on the day concerned.

(b) The letters to be used as the first character for the SIGMET sequence number to indicate the specified en-route weather and other phenomena for which the SIGMET has been issued should be:

(c) When SIGMET is issued for test purposes (‘TEST’ status indicator used in the SIGMET), then the appropriate letter for exchange test purposes should be used, i.e. ‘Y’ for a TEST volcanic ash SIGMET. When SIGMET is issued for exercise purposes (‘EXER’ status indicator used in the SIGMET), then the letter chosen should correspond to that used under normal circumstances, i.e. ‘A’ for a SIGMET issued during a volcanic ash exercise.

GM1 MET.TR.250(d) SIGMET

CRITERIA RELATED TO PHENOMENA

[…] (f) Turbulence is considered: (1) severe whenever the peak value of the cube root of the EDR equals or exceeds 0.70.45; and (2) moderate whenever the peak value of the cube root of the EDR is equal to or above 0.40.20 and below or equal to 0.70.45. […]

GM1 MET.TR.250(f)(1) SIGMET

SIGMET - DIGITAL FORM

(a) When SIGMET is disseminated in digital form, this is in addition to the SIGMET code form. (b) Guidance on the information exchange model, GML, and metadata profile is provided in ICAO Doc 10003 'Manual on the ICAO Meteorological Information Exchange Model'.

AMC1 MET.TR.250(g) SIGMET

FORMAT

SIGMET, when issued in graphical format, should be as specified below: (a) SIGMET FOR TROPICAL CYCLONE — MODEL STC (b) SIGMET FOR VOLCANIC ASH — MODEL SVA (c) SIGMET FOR PHENOMENA OTHER THAN TROPICAL CYCLONE AND VOLCANIC ASH — MODEL SGE

AMC1 MET.TR.255(a) AIRMET

AIRMET — CODE FORM

AIRMET, and cancellations thereof, should be encoded using: (a) the IWXXM GML form as specified in point (a) of AMC1 MET.TR.115(a); (b) abbreviated plain language as specified in point (c) of AMC1 MET.TR.115(a).

GM1 MET.TR.255(e) AIRMET

AIRMET — DIGITAL FORM

(a) When AIRMET is disseminated in digital form, this is in addition to the AIRMET code form. (b) Guidance on the information exchange model, GML, and metadata profile is provided in ICAO Doc 10003 ‘Manual on the Meteorological Information Exchange Model’.

AMC1 MET.TR.260 Area forecasts for low-level flights

AMENDMENT OF AREA FORECASTS FOR LOW-LEVEL FORECASTSFLIGHTS

(a) In case thethat an area forecast for low-level flights is not issued in combination with AIRMET/low-level forecast concept is not fully implemented, the criteria for amendments to the area forecast for low-level flights should as a minimum include the weather phenomena hazardous to low-level flights, which would otherwise constitute the criteria for the issuance of AIRMET. […]

Chapter 4 — Technical requirements for volcanic ash advisory centres (VAACs)

AMC1 MET.TR.265 Volcanic ash advisory centre responsibilities

VOLCANIC ASH ADVISORY — CODE FORM

Volcanic ash advisory should be disseminated using: (a) the IWXXM GML form as specified in point (a) of AMC1 MET.TR.115(a); (b) abbreviated plain language as specified in point (c) of AMC1 MET.TR.115(a).

AMC2 MET.TR.265 Volcanic ash advisory centre responsibilities

VOLCANIC ASH ADVISORY INFORMATION — GRAPHICAL FORMAT

The volcanic ash advisory information listed in Appendix 6 to Annex V (Part-MET) to Regulation (EU) 2017/373, when prepared in graphical format, should be as specified below and issued using the portable network graphics (PNG) format as specified in point (f) of AMC1 MET.TR.115(a):

Example of volcanic ash advisory in graphical format from the London VAAC. Mercator projection.

Note: The example above is fictitious.

Example of volcanic ash advisory in graphical format from the Toulouse VAAC. Mercator projection.

Note: The example above is fictitious.

Example of volcanic ash advisory in graphical format from the Wellington VAAC. Polar stereographic projection.

Note: The example above is fictitious.

GM1 MET.TR.265(a) Volcanic ash advisory centres (VAACs) responsibilities

EXAMPLES OF ADVISORY FOR VOLCANIC ASH

GM1 MET.TR.265(b) Volcanic ash advisory centres (VAACs) responsibilities

VOLCANIC ASH ADVISORY — DIGITAL FORM

(a) When volcanic ash advisory is disseminated in digital form, this is in addition to the volcanic ash advisory code form. (b) Guidance on the information exchange model, GML, and metadata profile is provided in in ICAO Doc 10003 ‘Manual on the Meteorological Information Exchange Model’.

AMC1 MET.TR.265(c) Volcanic ash advisory centres (VAACs) responsibilities

VOLCANIC ASH ADVISORY INFORMATION — GRAPHICAL FORMAT

The volcanic ash advisory information listed in Appendix 6 to Annex V (Part-MET) to Regulation (EU) 2017/373, when prepared in graphical format, should be as specified below. [Graphic] Example of volcanic ash advisory in graphical format from the London VAAC. Note: The example above is fictional.

Chapter 5 — Technical requirements for tropical cyclone advisory centres (TCACs)

AMC1 MET.TR.270 Tropical cyclone advisory centre responsibilities

TROPICAL CYCLONE ADVISORY — CODE FORM

Tropical cyclone advisory should be disseminated using: (a) the IWXXM GML form as specified in point (a) of AMC1 MET.TR.115(a); (b) abbreviated plain language as specified in point (c) of AMC1 MET.TR.115(a).

AMC2 MET.TR.270 Tropical cyclone advisory centre responsibilities

TROPICAL CYCLONE ADVISORY — GRAPHICAL FORMAT

The tropical cyclone advisory information listed in Appendix 7 to Annex V (Part-MET) to Regulation (EU) 2017/373, when prepared in graphical format, should be as specified below and issued using the portable network graphics (PNG) format as specified in point (f) of AMC1 MET.TR.115(a):

Example of tropical cyclone advisory in graphical format from the La Réunion TCAC.

Note: The example above is based on a real event.

GM1 MET.TR.270(b) Tropical cyclone advisory centres (TCACs) responsibilities

ADVISORY FOR TROPICAL CYCLONES — EXAMPLE

GM1 MET.TR.270(c) Tropical cyclone advisory centres (TCACs) responsibilities

TROPICAL-CYCLONE ADVISORY — DIGITAL FORM

(a) When a tropical cyclone advisory is disseminated in digital form, this is in addition to the tropical cyclone advisory code form.

(b) Guidance on the information exchange model, GML, and metadata profile is provided in in ICAO Doc 10003 ‘Manual on the Meteorological Information Exchange Model’.

AMC1 MET.TR.270(d) Tropical cyclone advisory centres (TCACs) responsibilities

TROPICAL CYCLONE ADVISORY INFORMATION — GRAPHICAL FORMAT

The tropical cyclone advisory information listed in Appendix 7 to Annex V (Part-MET) to Regulation (EU) 2017/373, when prepared in graphical format, should be as specified below.

AMC2 MET.TR.275(a) World area forecast centre responsibilities

WORLD AREA FORECAST CENTRE GLOBAL GRIDDED FORECASTS — CODE FORM

World area forecast centre global gridded forecasts should be encoded using the GRIB code form as specified in point (d) of AMC1 MET.TR.115(a).

GM1 MET.TR.275(a) World area forecast centres (WAFCs) responsibilities

GRIB CODE

The GRIB code form is contained in the WMO Publication No 306, Manual on Codes, Volume I.2, Part B — Binary Codes.

GM2 MET.TR.275(a) World area forecast centres (WAFCs) responsibilities

BUFR CODE

The BUFR code form is contained in the WMO Publication No 306, Manual on Codes, Volume I.2, Part B — Binary Codes.

GM1 MET.TR.275(b)(3) World area forecast centres (WAFCs) responsibilities

GRID POINT FORECASTS

(a) Layers centred at a flight level referred to in MET.TR.275(b)(3)(v) and (vii) have a depth of 100 hPa. (b) Layers centred at a flight level referred to in MET.TR.275(b)(3)(viii) have a depth of 100 hPa for flight levels below 240, then 50 hPa for flight levels 240 and above.

GM2 MET.TR.275(b)(3) World area forecast centre responsibilities

GRID POINT FORECASTS

The turbulence referred to in MET.TR.275(b)(3)(viii) encompasses all types of turbulence, including clear-air turbulence and in-cloud turbulence.

GM3 MET.TR.275(b)(3) World area forecast centre responsibilities

GRID POINT FORECASTS

The exact pressure levels (hPa) for MET.TR.275(b)(3) (i), (ii), (iii), (iv), (vii), and (viii) are provided in ICAO Doc 8896 ‘Manual of Aeronautical Meteorological Practice’.

AMC1 MET.TR.275(c) World area forecast centre responsibilities

WORLD AREA FORECAST CENTRE (WAFC) GLOBAL FORECASTS OF SIGNIFICANT WEATHER — CODE FORM

World area forecast centre (WAFC) global forecasts of significant weather should be disseminated using: (a) the IWXXM GML form as specified in point (a) of AMC1 MET.TR.115(a); (b) the BUFR code form as specified in point (e) of AMC1 MET.TR.115(a).

AMC1 MET.TR.275(d) World area forecast centres (WAFCs) responsibilities

MEDIUM-LEVEL SIGWX FORECASTS

The medium-level SIGWX forecasts provided for flight levels between 100 and 250450 for limited geographical areas should cover the areas as shown in in Table 2 of Appendix 21.

GM1 to Appendix 1 ‘Template for METAR and SPECI’

METAR AND SPECI — EXAMPLES OF ELEMENTS

Non-exhaustive examples of the different elements used in the formulation of METAR and SPECI are provided below.

GM1 to Appendix 3 ‘Template for TAF’

TAF — EXAMPLES OF ELEMENTS

Non-exhaustive examples of the different elements used in the formulation of TAF are provided below.

GM1 to Appendix 4 ‘Template for wind shear warnings’

WIND SHEAR WARNINGS — EXAMPLES OF ELEMENTS

Non-exhaustive examples of the different elements used in the formulation of wind shear warnings are provided below.

GM1 to Appendix 5 ‘Template for SIGMET and AIRMET’

SIGMET AND AIRMET — EXAMPLES OF ELEMENTS

Non-exhaustive examples of the different elements used in the formulation of SIGMET and AIRMET are provided below.

GM1 to Appendix 6 ‘Template for advisory for volcanic ash’

ADVISORY FOR VOLCANIC ASH — EXAMPLES OF ELEMENTS

Non-exhaustive examples of the different elements used in the formulation of advisory for volcanic ash are provided below.

GM1 to Appendix 7 ‘Template for advisory for tropical cyclones’

ADVISORY FOR TROPICAL CYCLONES — EXAMPLES OF ELEMENTS

Non-exhaustive examples of the different elements used in the formulation of advisory for tropical cyclones are provided below.