Page 13 - AFMAN 15-111, 12 MAR 2019
P. 13

AFMAN15-111  12 MARCH 2019                                                                  13



                   3.3.4.  Report Modifier (AUTO or COR). The observation report modifier can be either COR
                   or AUTO.

                       3.3.4.1.  COR is entered into the report modifier group when a corrected METAR or SPECI
                       is transmitted.

                       3.3.4.2.  AUTO  identifies  the  report  as  a  fully  automated  report  with  no  human
                       intervention. AUTO is automatically included in reports when the weather technician signs
                       off the automated dissemination system (ADS) indicating the observations are no longer
                       being augmented.
                       3.3.4.3.  AUTO and COR will not be seen in the same observation. If the term COR is
                       used, the observation cannot be reported as AUTO, since a weather technician is manually
                       correcting the observation. (T-0).
               3.4.  Coding Missing Data in METAR and SPECI Reports.   When an element does not occur,
               or  cannot  be  observed,  the  corresponding  group  and  preceding  space  are  omitted  from  that
               particular report. When a FBWOS cannot provide an element due to sensor failure, the software
               will automatically place a missing data flag (M) in the corresponding data field. The system will
               also  include  the  maintenance  indicator  ($)  at  the  end  of  the  observation.  Together,  these  two
               characters will cue the weather technicians to contact ATC agencies and maintenance personnel
               and begin back-up procedures.
               3.5.  Remarks (RMK).   Remarks, found in Attachment 3, generally elaborate on parameters
               reported in the body of the report, and will be included in all METAR and SPECI observations if
               required. Remarks will be separated from the altimeter group by a space and the contraction RMK.
               If there are no remarks, the contraction RMK will not be entered. (T-0).

                   3.5.1.  METAR/SPECI remarks fall into 2 major categories:  (1) Automated and Augmented;
                   and (2) Additive and Maintenance Data. Attachment 3 gives an overview of remarks and their
                   order of entry.

                   3.5.2.  Remarks will be made IAW the following: (T-0).
                       3.5.2.1.  Use  of  Contractions  and  Abbreviations.  Where  plain  language  is  called  for,
                       authorized  contractions,  abbreviations  and  symbols  will  be  used  to  conserve  time  and
                       space. However, in no case should an essential remark be omitted for the lack of readily
                       available contractions. In such cases, the only requirement is that the remark be clear. For
                       a detailed list of authorized contractions, see the list of abbreviations and acronyms in
                       Attachment 1 and FAA Order JO 7340 Series, Contractions.
                       3.5.2.2.  Time Entries in Remarks. Use UTC minutes past the hour if the time reported
                       occurs during the same hour the observation is taken. UTC hours and minutes are used if
                       the hour is different from the hour of the observation or this manual prescribes the use of
                       hour and minutes.

                       3.5.2.3.  Additive  data  will  be  reported  at  0000,  0600,  1200,  and  1800  UTC.  When
                       applicable, augment these reports with snow depth during controlled airfield hours. There
                       is no requirement to augment/back-up additive data outside controlled airfield hours. (T-
                       0).
   8   9   10   11   12   13   14   15   16   17   18