Publication: Magyar Közlöny
Issue: MK-2007-70 (Year: 2007, Number: 70)
Era: 2004-2010
Section: Melléklet a 2007. évi XLVI. törvényhez
Paragraph Index: 1255

d) if required, a three-letter indicator. Note 1.— Detailed specifications on format and contents of the heading are given in the WMO Manual on the Global Telecommunication System, Volume I and are reproduced in the Manual of Aeronautical Meteorological Practice (Doc 8896). SIGMET and AIRMET messages, volcanic ash and tropical cyclone advisory information Abbreviated plain-language amendments to Amended TAF and METAR 0–900 km Trend forecasts TAF SPECI more than 900 km 2007/70/II. szám Annex 3 — Meteorological Service for International Air Navigation Appendix 10 25/11/04 APP 10-2 Note 2.— ICAO location indicators are listed in Location Indicators (Doc 7910). 2.1.4 Structure of bulletins Meteorological bulletins containing operational meteorological information to be transmitted via the AFTN shall be encapsulated in the text part of the AFTN message format. 2.2 World area forecast system products 2.2.1 Telecommunications for the supply of WAFS products Recommendation.— The telecommunications facilities used for the supply of world area forecast system products should be the aeronautical fixed service. 2.2.2 Quality requirements for charts Recommendation.— Where world area forecast system products are disseminated in chart form, the quality of the charts received should be such as to permit reproduction in a sufficiently legible form for flight planning and documentation. Charts received should be legible over 95 per cent of their area. 2.2.3 Quality requirements for transmissions Recommendation.— Transmissions should be such as to ensure that their interruption should not exceed 10 minutes during any period of 6 hours. 2.2.4 Heading of bulletins containing WAFS products Meteorological bulletins containing WAFS products in digital form to be transmitted via aeronautical fixed service facilities shall contain a heading as given in 2.1.3. 3. USE OF AERONAUTICAL MOBILE SERVICE COMMUNICATIONS 3.1 Content and format of meteorological messages 3.1.1 The contents and format of reports, forecasts and SIGMET information transmitted to aircraft shall be consistent with the provisions of Chapters 4, 6 and 7 of this Annex. 3.1.2 The contents and format of air-reports transmitted by aircraft shall be consistent with the provisions of Chapter 5 of this Annex and the Procedures for Air Navigation Services — Air Traffic Management (PANS-ATM, Doc 4444), Appendix 1. 3.2 Content and format of meteorological bulletins The substance of a meteorological bulletin transmitted via the aeronautical mobile service shall remain unchanged from that contained in the bulletin as originated. 4. USE OF AERONAUTICAL DATA LINK SERVICE — D-VOLMET 4.1 Detailed content of meteorological information available for D-VOLMET 4.1.1 Recommendation.— The aerodromes for which METAR, SPECI and TAF are to be available for uplink to aircraft in flight should be determined by regional air navigation agreement. 4.1.2 Recommendation.— The flight information regions for which SIGMET and AIRMET messages are to be available for uplink to aircraft in flight should be determined by regional air navigation agreement. 4.2 Criteria related to information to be available for D-VOLMET 4.2.1 Recommendation.— The latest available METAR, SPECI, TAF, SIGMET and AIRMET should be used for uplink to aircraft in flight. 4.2.2 Recommendation.— TAF included in the D- VOLMET should be amended as necessary to ensure that a forecast, when made available for uplink to aircraft in flight, reflects the latest opinion of the meteorological office concerned. 4.2.3 Recommendation.— If no SIGMET message is available for a flight information region, an indication of “NIL SIGMET” should be included in the D-VOLMET. 4.3 Format of information to be available for D-VOLMET The content and format of reports, forecasts and SIGMET and AIRMET information included in D-VOLMET shall be consistent with the provisions of Chapters 4, 6 and 7 of this Annex. 2007/70/II. szám Appendix 10 Annex 3 — Meteorological Service for International Air Navigation APP 10-3 25/11/04 5. USE OF AERONAUTICAL BROADCASTING SERVICE — VOLMET BROADCASTS 5.1 Detailed content of meteorological information to be included in VOLMET broadcasts 5.1.1 Recommendation.— The aerodromes for which METAR, SPECI and TAF are to be included in VOLMET broadcasts, the sequence in which they are to be transmitted and the broadcast time should be determined by regional air navigation agreement. 5.1.2 Recommendation.— The flight information regions for which SIGMET messages are to be included in scheduled VOLMET broadcasts should be determined by regional air navigation agreement. Where this is done, the SIGMET message or an indication of “NIL SIGMET” should be transmitted at the beginning of the broadcast or of a five-minute time block. 5.2 Criteria related to information to be included in VOLMET broadcasts 5.2.1 Recommendation.— When a report has not arrived from an aerodrome in time for a broadcast, the latest available report should be included in the broadcast, together with the time of observation. 5.2.2 Recommendation.— TAF included in scheduled VOLMET broadcasts should have a period of validity of 9 hours; they should be issued every 3 hours and should, between these routine issues, be amended as necessary to ensure that a forecast, when transmitted, reflects the latest opinion of the meteorological office concerned. 5.3 Format of information to be included in VOLMET broadcasts 5.3.1 The content and format of reports, forecasts and SIGMET information included in VOLMET broadcasts shall be consistent with the provisions of Chapters 4, 6 and 7 of this Annex. 5.3.2 Recommendation.— VOLMET broadcasts should use standard radiotelephony phraseologies. Note.— Guidance on the standard radiotelephony phraseologies to be used in VOLMET broadcasts is given in the Manual on Coordination between Air Traffic Services, Aeronautical Information Services and Aeronautical Meteorological Services (Doc 9377), Appendix A. 2007/70/II. szám ANNEX 3 ATT A-1 25/11/04 ATTACHMENT A. OPERATIONALLY DESIRABLE AND CURRENTLY ATTAINABLE ACCURACY OF MEASUREMENT OR OBSERVATION Note.— The guidance contained in this table relates to Chapter 4 — Meteorological observations and reports, in particular to 4.1.9. . Element to be observed Operationally desirable accuracy of measurement or observation* Attainable accuracy** of measurement or observation (1994) Mean surface wind Direction: ± 10° Speed: ± 2 km/h (1 kt) up to 19 km/h (10 kt) ± 10% above 19 km/h (10 kt) Direction: ± 5° Speed: ± 2 km/h (1 kt) up to 37 km/h (20 kt) ± 5% above 37 km/h (20 kt) Variations from the mean surface wind ± 4 km/h (2 kt), in terms of longitudinal and lateral components as above Visibility ± 50 m up to 600 m ± 10% between 600 m and 1 500 m ± 20% above 1 500 m ± 50 m up to 500 m ± 10% between 500 m and 2 000 m ± 20% above 2 000 m up to 10 km Runway visual range ± 10 m up to 400 m ± 25 m between 400 m and 800 m ± 10% above 800 m ± 25 m up to 150 m ± 50 m between 150 m and 500 m ± 10% above 500 m up to 2 000 m Cloud amount ± 1 okta In daylight an observer can attain an accuracy of ± 1 okta at the point of observation. In darkness, and when atmospheric phenomena limit the viewing of low cloud, there will be difficulty in attaining that accuracy. Cloud height ± 10 m (33 ft) up to 100 m (330 ft) ± 10% above 100 m (330 ft) ± 10 m (33 ft) up to 1 000 m (3 300 ft) ± 30 m (100 ft) above 1 000 m (3 300 ft) up to 3 000 m (10 000 ft) Air temperature and dewpoint temperature ± 1°C ± 0.2 °C Pressure value (QNH, QFE) ± 0.5 hPa ± 0.3 hPa * The operationally desirable accuracy is not intended as an operational requirement; it is to be understood as a goal that has been expressed by the operators. ** The accuracy stated refers to assessment by instruments (except for cloud amount); it is not normally attainable in observations made without the aid of instruments. 2007/70/II. szám ANNEX 3 ATT B-1 25/11/04 ATTACHMENT B. OPERATIONALLY DESIRABLE ACCURACY OF FORECASTS Note 1.— The guidance contained in this table relates to Chapter 6 — Forecasts, in particular to 6.1.1. Note 2.— If the accuracy of the forecasts remains within the operationally desirable range shown in the second column, for the percentage of cases indicated in the third column, the effect of forecast errors is not considered serious in comparison with the effects of navigational errors and of other operational uncertainties. Element to be forecast Operationally desirable accuracy of forecasts Minimum percentage of cases within range TAF Wind direction ± 30° 80% of cases Wind speed ± 9 km/h (5 kt) up to 46 km/h (25 kt) ± 20% above 46 km/h (25 kt) 80% of cases Visibility ± 200 m up to 700 m ± 30% between 700 m and 10 km 80% of cases Precipitation Occurrence or non-occurrence 80% of cases Cloud amount ± 2 oktas 70% of cases Cloud height ± 30 m (100 ft) up to 120 m (400 ft) ± 30% between 120 m (400 ft) and 3 000 m (10 000 ft) 70% of cases Air temperature ± 1°C 70% of cases TREND FORECAST Wind direction ± 30° 90% of cases Wind speed ± 9 km/h (5 kt) up to 46 km/h (25 kt) ± 20% above 46 km/h (25 kt) 90% of cases Visibility ± 200 m up to 700 m ± 30% between 700 m and 10 km 90% of cases Precipitation Occurrence or non-occurrence 90% of cases Cloud amount ± 2 oktas 90% of cases Cloud height ± 30 m (100 ft) up to 120 m (400 ft) ± 30% between 120 m (400 ft) and 3 000 m (10 000 ft) 90% of cases 2007/70/II. szám Annex 3 — Meteorological Service for International Air Navigation Attachment B 25/11/04 ATT B-2 FORECAST FOR TAKE-OFF Wind direction ± 30° 90% of cases Wind speed ± 9 km/h (5 kt) up to 46 km/h (25 kt) ± 20% above 46 km/h (25 kt) 90% of cases Air temperature ± 1°C 90% of cases Pressure value (QNH) ± 1 hPa 90% of cases AREA, FLIGHT AND ROUTE FORECASTS Upper-air temperature ± 3°C (Mean for 900 km/500 NM) 90% of cases Upper wind ± 28 km/h (15 kt) up to flight level 250 ± 37 km/h (20 kt) above flight level 250 (Modulus of vector difference for 900 km/500 NM) 90% of cases Significant en-route weather phenomena and cloud Occurrence or non-occurrence Location: ± 100 km/60 NM Vertical extent: ± 600 m/2 000 ft 80% of cases 70% of cases 70% of cases Element to be forecast Operationally desirable accuracy of forecasts Minimum percentage of cases within range 2007/70/II. szám ANNEX 3 ATT C-1 25/11/04 ATTACHMENT C. BACK-UP PROCEDURES AT THE WORLD AREA FORECAST CENTRES (See Chapter 3, 3.2.2 of this Annex.) 1. INTRODUCTION A WAFC will provide any or all of the WAFS services as needed when the interruption of the operation of the other WAFC occurs. WAFC London and WAFC Washington have studied a number of potential service interruption and outage scenarios, reviewed the current communication links between the two WAFCs, and agreed upon the appropriate responses to each interruption in service. 2. INTERRUPTIONS IN NUMERICAL WEATHER PREDICTION (NWP) OR SIGNIFICANT WEATHER (SIGWX) FORECAST PRODUCTION 2.1 WAFC London interruptions 2.1.1 A global gridpoint NWP model runs in Exeter. The output from this NWP model forms the basis for the wind and temperature forecasts in the Gridded Binary (GRIB) code form. Two, largely identical, supercomputers are housed in separate computer halls, allowing the model to run on either machine. Therefore, routine or non-routine maintenance can be performed on one of the supercomputers without affecting the operational capability of WAFC London. In the rare event that the model cannot be run on either supercomputer, the following course of action would be taken. When the first model run is delayed significantly or is not available, a decision will be made to use the output from the previous model run, incremented by the appropriate number of hours. In the event that the output from a second, consecutive run is unavailable, WAFC London would process the GRIB data routinely received from WAFC Washington to produce the required WAFS forecasts. If the WAFC Washington data cannot be processed, WAFC Washington may be notified to begin the production of the back-up SIGWX forecasts. These forecasts along with other WAFS data are then sent to the WAFC London message-switching centre for normal distribution. 2.1.2 In the event of a failure at the primary operational workstation, the forecaster would use one of the back-up workstations located on the forecast floor, or in the back-up operations centre. If WAFC London is affected by a massive failure, paragraph 5 describes the action under “Total outage of a WAFC”. 2.2 WAFC Washington interruptions 2.2.1 A global spectral model runs at the National Centres for Environmental Prediction (NCEP) and produces the WAFC Washington NWP output. This forms the basis for the wind and temperature forecasts in the GRIB code form. NCEP maintains the ability to run the global model on redundant systems in the case of a failure of the primary system. If the NWP is significantly delayed or missing due to the failure of the primary or secondary computer systems, a decision is made to use the NWP data routinely received from WAFC London at the National Weather Service Telecommunications Gateway (NWSTG), incremented by the appropriate number of hours, to produce the WAFS forecasts. 2.2.2 If the primary operational workstation fails, the forecaster would use a back-up workstation located on the forecast floor. If the WAFC Washington SIGWX production centre is out, WAFC London is called on to produce all of the WAFC Washington SIGWX forecasts. These forecasts are then switched back to the NWSTG with the routine WAFC London SIGWX forecasts for dissemination via the International Satellite Communications System (ISCS). If WAFC Washington is affected by a massive failure, paragraph 5 describes the action under “Total outage of a WAFC”. 3. INTERRUPTIONS IN MESSAGE SWITCHING 3.1 WAFC London interruptions Two message switches exist at WAFC London. In the rare event of a failure at the primary switch, the back-up switch would be used to send and receive data. The back-up message switch can be immediately connected to the Washington and Toulouse WMO global telecommunication system (GTS) routes, and is permanently connected to the satellite distribution system for information relating to air navigation (SADIS) in the event of failure of the primary switch. In the extremely unlikely event that WAFC London cannot connect to the GTS, an integrated services digital network (ISDN) circuit between Silver Spring and Exeter will be used to send and receive data. This circuit is a physical back-up to the link that is normally in place, and is used only when a major failure occurs. 2007/70/II. szám Annex 3 — Meteorological Service for International Air Navigation Attachment C 25/11/04 ATT C-2 3.2 WAFC Washington interruptions An integrated services digital network (ISDN) circuit is maintained between WAFC London and the ISCS uplink site. In the rare event that the message switch at the NWSTG is out WAFC London would be notified to begin sending WAFS products on the ISDN circuit directly to the ISCS uplink site. The ISCS satellites then broadcast these products normally. A back-up message switch at another site is scheduled for implementation in 2004. 4. INTERRUPTIONS IN SATELLITE UPLINK AND SATELLITE DISTRIBUTION SYSTEMS The operation of the satellite communications systems used to provide the SADIS and ISCS broadcasts of the WAFS data is outside the control of the two WAFCs. The reliability and availability of these services is guaranteed by the commercial operators, and not by the two WAFCs. 5. TOTAL OUTAGE OF A WAFC 5.1 WAFC London outage It is considered extremely unlikely that WAFC London would ever be totally out. A new state of the art infrastructure ensures that both computers can operate completely independent of each other. Separate primary and back-up power supplies are furnished for each computer. The back-up procedures carried out will depend on the nature of the outage. In a worst-case scenario when the primary supercomputer becomes inoperable and the WAFC Washington — WAFC London GTS link cannot be regained, the ISDN circuit described in paragraph 4 would be used to send and receive data from Washington. Thus, the failure of the primary supercomputer would not affect the ability of WAFC London to disseminate WAFS products on the SADIS broadcast or send them to Washington for broadcast on the ISCS. In the event of the forecast office at WAFC London becoming unserviceable, WAFC Washington may be contacted to initiate back-up production of all the highlevel and medium-level SIGWX forecasts routinely produced by WAFC London. It should be noted that a back-up forecast office is provisioned at WAFC London in a separate wing of the building. Thus, it is considered highly unlikely that WAFC London would be totally unable to produce their WAFS SIGWX forecasts. The SIGWX forecasts would still be available for SADIS uplink from either forecast office in such a scenario assuming that either computer is available. 5.2 WAFC Washington outage The WAFS product generation facilities are located at multiple sites. Thus, WAFC Washington would never be completely out. The back-up procedures carried out would depend on the facility affected, and have been described above. Two independent data paths exist from the message-switching centre. Thus, a cable cut would not disrupt communications to or from the switch. However, in a scenario where the Washington message switch is completely out, the distribution of products to WAFC London and to the ISCS is also severed. A separate location for a back-up message switch is planned, but will not be implemented until 2004. 6. ROUTINE AND BACK-UP SIGNIFICANT WEATHER FORECASTS Table C-1 summarizes the ICAO areas to be used by WAFCs Washington and London for both routine and back-up SIGWX forecasts. 2007/70/II. szám Attachment C Annex 3 — Meteorological Service for International Air Navigation ATT C-3 25/11/04 Table C-1. Routine and back-up SIGWX areas with WMO headers SWH area Primary WAFC WMO header A Washington PGEE07 KKCI B London PGSE06 EGRR B1 Washington PGIE07 KKCI C London PGRE06 EGRR D London PGZE06 EGRR E London PGGE06 EGRR F Washington PGGE07 KKCI G London PGCE06 EGRR H London Washington PGAE06 EGRR PGAE07 KKCI I Washington PGBE07 KKCI J Washington PGJE07 KKCI K London PGKE06 EGRR M Washington PGDE30 KKCI NAT Washington PGNE40 KKCI EUR London PGDE15 EGRR MID London PGCE15 EGRR S ASIA London PGZE15 EGRR 2007/70/II. szám ATTACHMENT D. SELECTED CRITERIA APPLICABLE TO AERODROME REPORTS (The guidance in this table relates to Chapter 4 and Appendix 3.) Notes.— 1. Considered for the past 10 minutes (exception: if the 10-minute period includes a marked discontinuity (i.e. RVR changes or passes 150, 350, 600 or 800 m, lasting > 2 minutes), only data after the discontinuity to be used). A simple diagrammatic convention is used to illustrate those parts of the 10-minute period prior to the observation relevant to RVR criteria, i.e. AB, BC and AC. 2. Layer composed of CB and TCU with a common base should be reported as “CB”. 3. Considered for the past 10 minutes (exception: if the 10-minute period includes a marked discontinuity (i.e. the direction changes > 30° with a speed > 20 km/h or the speed changes > 20 km/h lasting > 2 minutes), only data after the discontinuity to be used). 4. If several directions, the most operationally significant direction used. 5. Let R1 = any 1-minute mean RVR-value during period AC, R10 = 10-minute mean RVR-value during period AC, R5(AB) = 5-minute mean RVR-value during period AB and R5(BC) = 5-minute mean RVR-value during period BC. 6. CB (cumulonimbus) and TCU (towering cumulus = cumulus congestus of great vertical extent) if not already indicated as one of the other layers. 7. Time averaging, if applicable, indicated in the upper left-hand corner. 8. N/A = not applicable. 9. QFE is to be included if required. Reference elevation for QFE should be aerodrome elevation except for precision approach runways, and nonprecision approach runways with threshold > 2 m (7 ft) below or above aerodrome elevation, where the reference level should be the relevant threshold elevation.

Source: https://magyarkozlony.hu/hivatalos-lapok/4c6310a937d14bac566ee9c9d944896656c292dd/dokumentumok/5a6ac3c6db12e692ae41096677ad5f072d2cc9f3/letoltes