AC 150/5220-16C Automated Weather Observing Systems (AWOS) for Non-Federal Applications
Contains the FAA standard for non-Federal Automated Weather Observing Systems.
This document is cancelled. It may have been replaced. Check the official source before relying on it.
Text read by OCR from a scanned file. Check the original, as some words may be misread.
Advisory
Circular
U.S. Department of Transportation
Federal Aviation Administration
Subject: AUTOMATED WEATHER Date:12/13/99 AC No: OBSERVING SYSTEMS (AWOS) FOR Initiated by: 150/5220-16C NON-FEDERAL APPLICATIONS AUA-430 Change:
1. PURPOSE. This advisory circular (AC) contains the Federal Aviation Administration's (FAA) standard for non-Federal AWOS's.
2. CANCELLATION. AC 150/5220-16B, AWOS's for Non-Federal Applications, dated 11/13/95, is canceled.
3. DEFINITION. An AWOS is a computerized system that automatically measures one or more weather parameters, analyzes the data, prepares a weather observation that consists of the parameter(s) measured, and broadcasts the observation to the pilot using an integral very high frequency (VHF) radio or an existing navigational aid (NAVAID) which may provide long-line dissemination of the observations.
4. APPLICATION. The provisions of this AC are effective immediately for all systems, or portions thereof, that are submitted for type certification or for previously type-certified systems that are submitted for modification of their type certification certificate. An AwOS that has been manufactured, installed, and maintained according to the criteria in this AC constitutes a National Weather Service (NwS)-approved source for weather information; is approvable as a source of weather information that partially satisfies Federal Aviation Regulations (FAR); may be eligible to receive a broadcast frequency assignment or broadcast over a NAVAID; may be eligible to distribute its weather over the national weather network; and may be eligible for funding under Federal grant programs.
5. CONTENT OF THIS AC. Accordingly, this AC provides guidance about the program elements that should be incorporated into an Awos. It provides the guidance and suggestions for one method, but not the only method, of complying with all pertinent regulations.
6. PRINCIPAL CHANGES. Provides clarification as to what system performance verification testing is, why it is important to have
valid performance verification checks and references, and why these checks should be accomplished at acceptable intervals. Adds minimum desired and maximum operating tolerances, references, performance checks, and intervals that, when used, should support reliable system performance and user confidence. Provides an incentive for manufacturers to utilize valid verification techniques and technological improvements to ensure and enhance system reliability. Redefines AwoS wind sensor tolerances to be consistent with other FAA-approved wind sensors. Clarifies information about type acceptance and maintenance documentation needs. Makes word changes to clarify sentence meanings. Significant changes are annotated with a vertical line at the left of the text.
7. HISTORICAL INFORMATION ABOUT THE PREVIOUS CHANGE DATED 11/13/95. Added that the FAA is committed to adoption of a version of the METAR format. Added the requirement for the AWOS maintenance technician to comply with the qualification requirements in most recent version of Order 6700.20(), Non-Federal Navigational Aids and Air Traffic Control Facilities. Added the requirement for VHF and ultra-high frequency (UHF) radio parameters to be listed in the Maintenance Manual. Added that AwOS manufacturers are encouraged to design their systems in accordance with FAA Standards 019 and 020 and the National Electrical Code (NEC) and to be installed in accordance with local codes. Corrected the specification for the reference visible light transmissometer standard. Added the requirement for a 90-second manual voice message at towered locations. Modified the requirement for periodic data validation. Corrected a number of editorial errors and administrative oversights.
8. REQUESTS FOR INFORMATION. Further information concerning AWOS standards and the FAA type-approval process may be obtained from the Weather Sensors product team office at the Federal Aviation Administration, 800 Independence Avenue, S.W., Washington, D.C. 20591 Attention: AWOS Program Office, AUA-430, Telephone (202) 366-5439.
PandaHercher William R. Voss
Director of Air Traffic Systems Development, AUA-1
CHAPTER 1. INTRODUCTION
CHAPTER 1. INTRODUCTION
1. FUNCTIONAL DESCRIPTION. An AWOS automatically measures meteorological parameters, reduces, and analyzes the data via computer, and broadcasts weather reports which can be received by aircraft operating up to 10,000 feet above ground level and 25 nautical miles from the AwOs. Pilots may use weather information provided by the Awos to partially fulfill the requirements of various FARs. For example, at airports with instrument approaches, an AwOs weather report eliminates the remote altimeter penalty and, thereby, allows use of the published minimum descent altitude.
2. WEATHER SENSORS. The AWOS is a modular system utilizing a central processor which may receive input from several sensors. Five standard groups of sensors are defined in subparagraphs a-h; however, an AwOs may be certified with any combination of sensors. Depending upon system design, additional sensors may be certified to any AwOS configuration.
a. AWOS A. The AWOS A system contains only dual-pressure sensors that measure pressure and report altimeter setting to the pilot.
b. AWOS I. The AWOS I system contains the AWOS A sensors, plus sensors to measure wind data (speed, direction, and gusts), temperature, dewpoint, and report density altitude.
c. AWOS II. The AWOS II system contains the AWOS I system sensors, plus a visibility sensor.
d. AWOS III. The AWOS III system contains all the AWOS II system sensors, plus a cloud-height sensor.
e. AWOS III P. The AWOS III P system contains all the AWOS III system sensors, plus a precipitation identification sensor.
f. AWOS III T. The AWOS III T system contains all the AWOS III system sensors and includes a thunderstorm/lightning reporting capability.
g. AWOS III P/T. The AWOS III P/T system contains all the AWOS III system sensors, plus a precipitation identification sensor and a thunderstorm/lightning reporting capability.
h. AWOS IV. The AWOS IV system contains all the AWOS III system sensors, plus precipitation occurrence, type and accumulation, freezing rain, thunderstorm, and runway surface condition sensors.
3. OUTPUT MEDIA FOR AWOS WEATHER INFORMATION.
a. The output of the Awos is reported by a computer-generated voice, which is transmitted to pilots over the voice output of a NAVAID or via a discrete VHF transmitter. The transmission may be continuous or may be a 3-minute broadcast triggered by three clicks of a pilot's microphone on the AwOs broadcast frequency (if the AwOs broadcasts over a VHF discrete frequency radio). System design may permit the transmission of the identification of a NAVAID by using the AWOS voice capability. In all cases where the voice output of a navigational aid is used, provision should be made so that the failure of an AWOs would in no way result in any failure of the NAVAID being used.
b. AwOS messages may be offered via other formats that the owner chooses to provide, including a telephone dial-up service. An option allows AwOs III (or greater capability) data to be disseminated via the AwOs data acquisition system (ADAS) so that the weather information is available nationally for forecasting and flight planning purposes. To contribute to this network, the AwOs should have an interface module that puts the data into a format that is compatible with the centrally located ADAS. An ADAS is located in each air route traffic control center (ARTCC) and collects and consolidates Awos reports for input to the national network. The data communications protocol and other details of the interface between the AwOS and the ADAS may be obtained from the office listed on the front of this AC.
The sponsor of an AwOs that has been linked to the national weather network via ADAS would be required to sign a Memorandum of Agreement with the FAA Air Traffic Division in the applicable FAA region that commits them:
(1) to convert the AWOS data to the current or future ADAS format, when used with the ADAS interface.
(2) to the current METAR format.
(3) to a reporting frequency (e.g., number of reports per hour) in accordance with criteria directed by the FAA.
(4) to bear all communications, quality assurance, troubleshooting, and administrative costs to interconnect their AWOS to the ADAS.
(5) to provide a point of contact for use by the FAA and others to report problems with the AwOs or with the communications link to the ADAs. (The point of contact would be available by telephone and responsive during normal business hours, and is encouraged to be responsive on a 24-hour a day basis.)
c. The output of the AwOs weather observation is controlled by one of four modes of operation. Mode 1 is applicable to all systems; modes 2, 3, and 4 are applicable only to systems configured with an operator terminal (OT). Modes 3 and 4 require an agreement with the NwS to maintain a Non-Federal Observer (NF Obs) program to augment and backup the AwoS system.
(1) Mode 1, Full-time Automated Operation. In this mode, the AwOS operates 24 hours/day without any manual input. The automated weather observations are updated on a minute-by-minute basis. There is no weather observer input to the AwOs. However, a manual observing capability may be maintained as backup provided that an agreement exists with the NWS to maintain a manual observingcapability.
(2) Mode 2, Full-time Automated Operation with Local Notice to Airmen (NOTAM). Operation in this mode is the same as Mode 1, with the addition of the capability to append a manually recorded NOTAM to the automated voice reports [par 31a(1)(iv) and 32]. The airport manager is responsible for the NOTAM information. The NOTAM information is heard on the local voice broadcast, it is not transmitted long line. There is no weather observer input.
(3) Mode 3, Full-time Automated Operation with Manual Weather Augmentation and Local NOTAM Option. Operation in this mode provides the capability for a weather observer to manually augment the automated observation by appending a weather entry to the observation during the weather observer duty hours. The observer duty hours should be published in the Airport/Facility Directory. The addition of a local NOTAM, per subparagraph c(2) is also permitted in this mode of operation, provided there is no interference with the observer augmentation. The weather observer is responsible for the accuracy and timeliness of the added weather information. The weather to be added is limited to thunderstorms, all types of precipitation, and obstructions to vision. The
weather added by the observer is to be manually recorded and appended to the automated voice reports using the operator terminal (OT) microphone and, as applicable, entered manually (using the AwOS keyboard) into the system for transmission over the Service A teletype network. The procedures in Federal Meteorological Handbook No. 1 (FMH-1), and the FAA Order 7900.5, Surface Weather Observing, apply.
(4) Mode 4, Part-time Manual Operation. Mode 4 is normally used for backup. This mode permits a weather observer to enter a complete manual observation into the system. The procedures in FMH-1 and Order 7900.5 apply to the recording and formatting of these manual observations. As applicable, the manual observations are transmitted over the "Service A" network. Voice dissemination of the observations should be done manually using the OT microphone. The manual observations include input from the automated AwOS outputs available to the weather observer on the OT display, to be modified to Order 7900.5 requirements. For example, the manual observation includes manually derived ceiling/sky condition and visibility, using FMH-1 definitions, which differ somewhat from the AWOS algorithms. Temperature, dewpoint, wind direction/speed, and altimeter setting are the same and are used exactly as presented on the AwOs OT display. Sea-level pressure, if required to be included in the observation, is normally computed manually, since it is not an output included in the AwOs automated output.
d. International Aviation Routine Weather Report Format (METAR).
(1) As of July 1, 1996, the United States Government and the FAA implemented a version of the METAR format. Change from the surface aviation observation (SAO) to the METAR format was effective as of July 1, 1996.
(2) All AWOS's must meet METAR format requirements. Longline distribution of wind direction should be in "True" while local dissemination (radio and telephone) will be "Magnetic." Every AwOs must be type certified with this format. Each manufacturer offering to market such a system must submit a type-certification request to the FAA in accordance with the procedures in this AC to demonstrate that their system outputs in the METAR format.
(3) All AwOS data output to the national weather network is to be in the METAR format.
(4) An interface control document is currently developed. A current copy is available from the Weather Sensors product team office at the address listed on the front of this AC.
4. FAA'S FACILITY PERFORMANCE AND INSPECTION RESPONSIBILITY. The General Aviation Revitalization Act of 1994 reaffirmed the FAA's responsibility and authority to regulate and inspect air navigation facilities, including aviation meteorological services. The establishment and maintenance of non-Federal facilities, including AWOS systems, are covered in FAA Order 6700.20(), Non-Federal Navigational Aids and Air Traffic Control Facilities.
a. Chapters 3 and 4 of this AC provide the FAA's minimum acceptable operating standards and references for a non-Federal AwOs system. Chapter 4 also provides the expected minimum checks and maximum maintenance intervals between checks.
b. FAA-owned meteorological/AwOS equipment tolerances are found in FAA Order 6560.13B, Maintenance of Aviation Meteorological Systems and Miscellaneous Aids.
c. Non-Federal AwOS systems require periodic performance verification. According to FAA Order 6700.20(), this verification is required to be accomplished only by a qualified technician with the proper FAA verification authority.
d. Verification is the written assurance that the facility, system, or service is providing the required/advertised service to the user. System performance checks are made to identify and correct changes or drifting of performance parameters and to provide documented assurance to the user of the validity of the published service. Both of these reasons are considered when making decisions regarding what performance checks should be performed and what the intervals should be between accomplishing these checks.
e. If results of these checks are satisfactory, a maintenance technician with FAA verification authority will document this fact by making a system verification entry in the facility's FAA Form 6030-1, Facility Maintenance Log. If the checks are not satisfactory, the system or individual sensor should not be used.
CHAPTER 2.CERTIFICATION AND COMMISSIONING PROCESS
CHAPTER 2.CERTIFICATION AND COMMISSIONING PROCESS
5. PROCESS OVERVIEW. In order to provide confidence in the quality of the meteorological data that the Awos provides to users in the aviation community, the FAA has initiated a three-part AwOS certification and commissioning process.
a. The manufacturer should provide the FAA with the test data and other documentation to demonstrate that the Awos system meets the criteria of this AC (paragraph 6, type approval). Upon completion of all the requirements set forth in this manual, the FAA grants approval to the specific system documented in the request.
b. Prospective sponsors (owners) wanting to install an AwOs system for public use should closely coordinate their plans with the FAA regional non-Federal facilities program manager (this person may be called the non-Federal coordinator in some regions) and follow the procedures provided. FAA (Order 6700.20()) requires that a Memorandum of Understanding (MOU) and an Operations and Maintenance Manual (OMM) be established and agreed to between the sponsor and the FAA prior to commissioning the AwOS for public use. The MOU/OMM is used to ensure that there is a mutual understanding of what is required to operate and maintain a commissioned AwOs system. After the AWOS is installed on site, and the MOU/OMM is signed, the FAA conducts a commissioning ground inspection to verify that the system is installed and operating correctly and that the owner has the resources to maintain the system in proper operating condition (paragraph 11, facility commissioning). A flight inspection is required for NAVAIDS used for AWOS dissemination. This process should be successfully completed for the AwOS to be commissioned by the FAA and to be authorized to operate.
c. Finally, there may be periodic visits to the operating AWOs by the FAA and other technical representatives to verify that the system continues to operate correctly. Guidance for these visits may be found in paragraph 14 (Ongoing System Validation) and Chapter 4 (Minimum Operating Requirements) of this AC, the facility MOU/OMM, and the FAA Order 6700.20().
6. MANUFACTURER SUBMITTALS FOR TYPE APPROVAL. The FAA grants approval to an Awos design after review and approval of three submittals from the manufacturer. The first submittal is for type
approval and consists of test procedures and data sheets that demonstrate that the proposed AwOs configuration meets the hardware and software criteria of this AC. This submittal should include a single matrix showing each specific requirement from this AC, cross-referenced to the specific location (paragraph, page, etc.) within the manufacturer's submittal where the requirement has been addressed. The second submittal consists of warranty, training, and maintenance documents intended to support the Awos system owner. The third submittal consists of a configuration control plan that identifies the components and options approved for use with the system. Requests for type approval should be sent to the Weather Sensors product team office at the address listed in paragraph 8, page 2. Product approval may be revoked (or an individual site may be removed from service) if:
a. The equipment has an unacceptable failure rate.
b. There is a deficiency that precludes or hampers valid performance verification of the operating system.
c. Changes are made to either the software or hardware without FAA approval.
d. Transmitted data does not conform to Federal Meteorological Handbook (FMH)-1 or FAA Order 7900.5.
e. The manufacturer fails to honor the warranty.
7. TEST PROGRAM. Chapter 3 of this manual contains the performance and testing standards for each component of the AwOs. The manufacturer should demonstrate compliance with these standards through performance testing (where a test is specified) or by analysis and inspection. The manufacturer provides all necessary equipment and bears all testing costs. Prior to performing tests the manufacturer should propose a test plan to the FAA containing detailed procedures for conducting the tests, as well as the name and location of the facility where the tests are to be conducted. Prior FAA review of the test plan should minimize the likelihood of improper test procedures that might result in rejection of the data. It is the responsibility of the manufacturer to provide credible test data to the FAA that is based on fact, and representative of the equipment being certified. Submissions should include all data collected during a test; data should not be omitted because it falls outside of the recommended acceptable limits of this AC. After completion of the tests, the manufacturer
should reduce the data to an easily understood format to demonstrate conformity with this AC. If the manufacturer has previously performed testing, the test procedures and data sheets from these tests may be submitted for FAA approval. However, the FAA reserves the right to witness testing and examine raw data.
8. SYSTEM DOCUMENTATION. The manufacturer should submit three copies of the draft documentation described in this paragraph to the FAA for review and approval. The System Description Manual, Maintenance Manual, Installation and Checkout Manual, Operating Instructions Manual, and Annual System Revalidation Plan Manual should be provided as separate manuals. These documents are intended to assist the AwOs owner in installing, operating, and maintaining the system. The items may be cross-referenced to avoid duplication, but the elements of each portion of each document should be clear. (For example, the maintenance procedures that are performed during the annual system revalidation should be explicitly referenced.)
After the FAA has approved these manuals, 12 copies of these approved documents should be submitted to the FAA Weather Sensors product team office before type approval of any system (or any system modification requiring a change in any of these documents) would be granted. These copies are distributed to each FAA regional office and other appropriate FAA offices to keep them apprised of all type accepted systems, sensors, and approved changes. If a,manufacturer modifies the initially approved configuration, then three copies of the revised supporting documentation should be submitted for approval.After approval by the FAA, 12 copies of the approved change documents should be submitted to the FAA Weather Sensors product team office for distribution to FAA offices. The FAA should receive these 12 copies before type approval is granted and the system is offered for sale.
a. System Description. The system description identifies and catalogs the hardware components to the level of the smallest field-replaceable module and describes computer software. The principles of system operation are described using schematics, block diagrams, and flow diagrams. For peripheral devices, the performance parameters are included along with the name and address of the original manufacturer.
b. Manufacturer's Maintenance Manual. The manufacturer's Maintenance Manual should contain a comprehensive maintenance
program to be implemented by the owner to ensure reliable and accurate performance over the life of the system. As a minimum, the program should define all maintenance activities that are required within a period of 5 years and a recommended frequency (e.g., quarterly, annually) for each operation. The following topics should be addressed in the Maintenance Manual:
(1) Maintenance Procedures. The manual should contain a step-by-step procedure for each scheduled (i.e., periodic) and unscheduled (i.e., repair) maintenance operation. It should discuss calibration methods, troubleshooting procedures, suggested spare parts, and identify all test equipment required. This document should also include the detailed procedures (e.g., the keystrokes) the maintenance technician follows when using the operator terminal to perform maintenance on the system.
(2) System Performance Parameters. The manual should contain a complete listing of the test points, sensor outputs, waveforms, and other parameters which indicate system performance that may be measured in the field. If these quantities are field adjustable, then an initial value (for use during initial certification) and an operating tolerance (for use during the annual verification) should be given. The key system parameters should also be identified; i.e., those values which best indicate system performance and to be checked most frequently. The frequency of scheduled maintenance actions (e.g., monthly, quarterly, and annually) should also be given.
(3) Data Recording Forms. The manual contains three types of forms designed to aid the system owner in recording the system performance data described in subparagraph (2).
(a) The Comprehensive Facility Performance and Adjustment Data form (similar to FAA Form 6030-17) is an initial facility commissioning data form which should be completed at system commissioning and after major repair work (i.e., after a major component has been replaced). The form contains the standards and tolerances of each component, all of the initial commissioning checks required, space to record the actual result of each performance check, and another space to enter the standard or reference value expected from each check.
(b) The Technical Performance Record (similar to FAA Form 6000-8) is a data record form that is used to record the results of performance checks accomplished during routine and
nonroutine maintenance visits. It may also be used as a checklist of all of the scheduled maintenance to be done at the facility during a specific routine periodic maintenance (PM) visit (e.g., during a visit to accomplish scheduled monthly, quarterly, or annual PM's). The form should also include the standards and tolerances required to be measured with a space to record each result. It is to be used to record the actions during the monthly and quarterly maintenance visit, the annual validation inspection, during nonroutine maintenance performed to capture any changes to sensor or system parameters, and to log the results of tests conducted after an aviation accident. Separate forms may be established and used to cover different PM visits.
(c) The third form is the FAA Form 6030-1. The FAA will provide this Form. Instructions for its use should be found in the FAA/sponsor MOU/OMM. All site visits should be documented on this form. It provides a historical record of all maintenance actions accomplished on the AwOs. The technician should list all maintenance actions accomplished (e.g., "monthly periodic maintenance actions completed, " "dewpoint sensor replaced"), any damage should be logged (e.g., "bullet hole in vertical fin of the wind sensor, needs replacement"), any problem with the Awos should be noted (e.g., "dew point sensor disconnected, replacement required"). When a system or component repair or adjustment has been accomplished, the maintenance technician should make a performance verification statement on this Form. In all cases, the technician completing the action and making the Form entry should be identified on the Form. These forms also contain the date of the action, the facility name and location, and other identifying data. More information on completion of the Form 6030-1 may be found in the MOU/OMM or the FAA Order 6700.20().
(4) Installation and Checkout Manual. This document should thoroughly describe the installation and checkout procedures to be followed by the technician at the installation site.
(5) Operating Instructions (i.e., an Observer Handbook). Provides detailed instructions for a weather observer to operate the system. This document should describe and provide instructions for operation in each of the four modes (paragraph 3c), it should explain the procedures when using the operator terminal to augment or to backup the AwOS, or to disseminate NOTAM information.
(6) Training Program. The training program should consist of a summary of the knowledge and skills that a maintenance
technician should possess to service an Awos. This document should also propose a program to familiarize maintenance technicians with the maintenance and operation of the AwOs. The training program may be conducted on site, at the factory, via home study, or by other means suggested by the manufacturer. The training program should cover both concepts and practical performance. It should contain a written test that may be used to measure a person's knowledge of the system. The manufacturer should submit to the FAA a 50-question open book test with an answer sheet and an additional 50 questions and answers (a total of 100 questions and answers) that may be used by the FAA to test the competence of a maintenance technician on the specific system being submitted to the FAA for approval. The FAA will also administer a performance examination to any technician seeking verification authority. This exam will require the technician to demonstrate the ability to accomplish all commissioning and annual reverification tests.
(7) Annual System Revalidation Plan. This plan should contain the recommended procedures to conduct an annual inspection of the facility to verify and document that it is in the approved configuration and operating within tolerance (paragraph 14).
(8) Warranty. The manufacturer should submit a statement certifying the following minimum warranty for the equipment:
This equipment has been manufactured and should perform in accordance with requirements of the FAA AC 150/5220-16. Any defect in design, materials, or workmanship which may occur during proper and normal use during a period of 1 year from date of installation or a maximum of 2 years from shipment should be corrected by repair or replacement by the manufacturer fee on board (f.o.b.) factory.
9. CONFIGURATION CONTROL PLAN. Due to the modular nature of the Awos, many system components such as sensors and peripheral devices may be interchangeable. Since type approval is given only to specific combinations of components, the manufacturer should establish a configuration control mechanism that would uniquely identify each FAA-approved system and its components. Before type approval is granted, the manufacturer should submit a Configuration Control plan. The configuration control plan should be explained and include the procedures for configuration control of all hardware and software system documentation. The identifying information for each system should be permanently inscribed on a system name plate. Changes to an approved configuration should be submitted for FAA approval to the Weather Sensors product team
office at the address listed on the front of this AC. The manufacturer may incorporate minor product improvement changes after notifying and obtaining approval from the FAA. Major changes, such as a sensor or a major software change should be fully supported by documentation and appropriate test data. (Major changes normally require the assignment of a new configuration number.) Every change to an approved Awos should be supported by revised configuration controlled documentation. The plan should also address:
a. The manufacturer's arrangement for assigning a configuration identification number/symbol/etc., and the means used to identify which system components are included in a particular system configuration.
b. Procedures for notifying system owners of changes in the approved configuration of their Awos.
c. Procedures for identifying and maintaining a record of the configuration of each operational system that has been sold and installed by the manufacturer.
d. A definition of major and minor product improvement changes.
e. Procedures for the configuration control of documentation, to include procedures for issuing changes, numbering, and dating pages.
10.PLANNING THE AWOS INSTALLATION.
a. All airport owners, sponsors, or other parties contemplating purchase and installation of a non-Federal AwOS should coordinate with the FAA before the equipment is ordered. The regional FAA non-Federal facilities program manager (non-Federal coordinator) is the official FAA point of contact in the region and is responsible for the overall project coordination between the sponsor and other elements in the FAA. Airport sponsors desiring to obtain a grant under the Airport Improvement Program (AIP) to install an AWOS, should also coordinate with the FAA Airport District Office that has jurisdiction over its specific geographical area. The FAA non- Federal program manager should coordinate the proposal with the FAA Regional Flight Standards Division, Airports District Office, Air Traffic Division, regional frequency management officer (FMO), and other offices as needed.
b. The selection of a voice outlet frequency for the Awos is a critical issue. Therefore, it is advisable to coordinate with the respective FAA regional FMO in the early planning stages of the facility, since there are a limited number of frequencies available for this purpose. The following order of frequency priority has been established by the FAA and should be used to the extent possible in establishing Awos ground-to-air communications outlets:
(1) Assigned Automated Terminal Information Service (ATIS) frequency. At part-time towered locations, the AwOS operates independently from the ATIS during nonoperational hours and utilizes the existing ATIS voice outlet frequency.
(2) VHF omnidirectional radio range (VOR) or VHF omnidirectional radio range/tactical air navigation (VORTAC) (except doppler VOR) with voice capability.
The VOR/VORTAC must be located within 3 nautical miles (nm) of the airport and not used to broadcast other information such as Enroute Flight Advisory System (EFAS).
(3) Nondirectional radio beacon (NDB) with voice capability. The NDB must be located within three nm of the airport. At locations where frequency congestion in the VHF air-ground band is not expected to be a problem, the use of an NDB should be considered as the fourth priority. The NDB frequency may have to be changed if the existing frequency is not in the 325 to 415 kilohertz (kHz) range.
(4) Any 25 kHz spaced discrete VHF air-ground communications channel in the air traffic control band (118-137 MHz). Any request for a discrete VHF frequency assignment should include a justification statement on why an NDB or VOR/VORTAC is not being used for the AwOS transmission. The regional FMO should include this justification in the supplementary details field in the frequency assignment application form. To minimize the potential for interference, certain VHF frequencies have been designated specifically for AwOs use and should be considered before any other discrete frequency in the 118-137 MHz band is used.
The service volume for an AwOs voice outlet (excluding those broadcasts over existing ATIS systems) is normally limited to 10,000 feet above ground level and 25 nm from the AwOs. The regional Air Traffic Division should approve requirements in excess
of this value. Under no circumstances should the radius of the service volume exceed the terminal control area. c. If the AwoS system proposed for installation does not meet the requirements of this AC or any other FAA-approved standards, the FAA may not assign the system a broadcast frequency.
d. After an AwOS III, or greater, has been certified and commissioned by the FAA, it becomes the weather source for the airport. Any existing manual weather observation program whose hours conflict with the AwOs III should be terminated. However, as specified in paragraph 3c, the AwOS owner may elect to maintain a manual observation capability to back up the Awos in the event the system, or any critical parameter (windspeed/direction, ceiling/sky condition, visibility, altimeter setting), fails. In addition, the AwOS owner may elect to augment the AwOS output with specified parameters (e.g., thunderstorms or precipitation) that are not within the capability of the AwOs. In these cases, the supplementary aviation weather reporting station (SAWRS) agreement with the NwS should be amended accordingly.
11.FACILITY COMMISSIONING. The FAA should formally commission the AwOS facility before it becomes available for public use. After receiving approval of a broadcast frequency, the owner may procure and install the AwOS facility. At least 120 days prior to the anticipated commissioning date, the owner should notify the FAA Regional Flight Standards Division so that routine revisions may be made to the instrument approach procedures. As the system approaches operational readiness, the owner should request a commissioning ground inspection by Regional Airway Facilities (AAF) personnel. This inspection includes participation by the owner or owner's maintenance representative. The commissioning inspection consists of the tests and checks in subparagraphs a-e, a review of the operations and maintenance documents on file at the facility, recording of initial facility performance data which should be retained as commissioning documentation in the facility reference data file (FRDF), or similar historic record locations.
a. Siting and Installation. The AwOs is a permanent facility and is located, constructed, and installed in accordance with applicable code requirements. It should be installed by a technician who is fully qualified in electronic applications who has a knowledge of the operations, testing, and maintenance of the AWOs, and is either a maintenance technician employed at the manufacturer's factory or has been certified by the FAA. The procedures in the FAA-approved Installation and Checkout Manual
should be performed (paragraph 8c). A regional FAA AAF representative should verify that the AwOS equipment was installed in accordance with the siting criteria contained in the current version of FAA Order 6560.20, Siting Criteria for Automated Weather Observing Systems (AwOS), and that the checkout procedures have been performed. Any exceptions to the siting order should be justified as being the best practical solution for meeting the intent of the siting criteria. Any discrepancies found during this inspection should be rectified before the facility can be commissioned.
b. Performance Test. The AWOS owner's FAA-approved maintenance representative should operate the system and measure all system performance parameters described in this AC and the manufacturer's Maintenance Manual. The initial commissioning data are recorded on a Comprehensive Facility Performance and Adjustment Data forms, or other approved commissioning data forms and retained at the facility in the FRDF as commissioning documentation.
c. Flight Inspection. All NAVAID facilities (e.g., VOR, NDB) used as a voice outlet to broadcast weather information should be flight inspected to assure that operation of the NAVAID has not been derogated. If, during flight inspection, it is determined that performance of the NAVAID has been affected, the AWOS should not be activated until the malfunction has been corrected (e.g., through modification or by employing a separate discrete frequency transmitter to broadcast the weather). An AwOS utilizing a discrete frequency transmitter is not required to undergo a flight inspection.
d. Notification of the Weather Sensors Product Team. Following successful completion of the commissioning inspection, the FAA regional non-Federal facilities program manager should notify the FAA Weather Sensors product team office of the commissioning date, broadcast frequency, voice access telephone number, system owner, and maintenance arrangements.
e. Relocation of an AwOS. In the event that an AWOS is removed from service to be relocated, a "decommissioning" NOTAM should be issued, instead of a "facility out-of-service" NOTAM. After relocation, a facility commissioning inspection should be performed.
12.ONSITE DOCUMENTATION.The following documentation should comprise the FRDF. It should contain all pertinent onsite
documentation and is to be maintained and kept at the facility. The FAA should review it at the commissioning inspection.
a. Type Approval. A copy of the FAA letter to the manufacturer granting type approval for the Awos system design should be included. The subsystems should be inspected to verify that the Awos installed is configured for which the type approval was given.
b. Frequency Allocation Approval. A copy of the documentation from the Federal Communications Commission (FCC) assigning the approved operating frequencies (if appropriate) should be included in the FRDF.
c. Manufacturer's Documentation. Copies of the AwOS operating instructions (paragraph 8.4), manufacturer's Maintenance Manual (paragraph 8b), and system description (paragraph 8a) should be included in the FRDF. When changes are made to these documents initially placed in the FRDF, the manufacturer should forward revisions to the AwOS owner.
d. Operational Procedures. Site-specific operational procedures that set forth mandatory site procedures for both routine and nonscheduled situations should be included in the FRDF. These procedures may incorporate appropriate sections of the manufacturer's manuals. The following items should be covered:
(1) Physical security of the facility.
(2) Maintenance and operations by authorized persons, including who to notify if a weather parameter is discovered out of tolerance or other maintenance is necessary.
(3) Posting of licenses and signs.
(4) Notice to the FAA when any AWOS service has been suspended, or when a critical weather parameter is out of tolerance.
(5)Keeping of station logs and other technical reports.
(6) Names, addresses, and telephone numbers of persons to be notified in the event of system failure.
(7) Procedures for periodic scheduled shutdown maintenance, including the office responsible for generating NOTAMs for routine
or nonscheduled shutdowns. Also, an explanation of the kinds of activities (such as construction or grading) in the vicinity of the AwOs facility that may require shutdown or reverification of the AWOS.
(8) Procedures for amending or revising the site instructions.
(9) Procedures to be followed to freeze the AwOs data in the archive file in the data processor for a specified period before and after the time of an aircraft accident or incident, and the procedures to be followed to retrieve these data. These procedures should describe the responsibility for accomplishing those actions. They should be automatically accomplished in the event of an accident, incident, or upon the request of a member of the FAA.
(10) Locations of AwOs components on the airport. This includes the result of the survey to establish the elevation of the barometric pressure sensors.
(11) A MOU signed by the owner and the FAA regional AAF Division manager. This Memorandum should state that the owner agrees to maintain, repair, and modify the AwOs in accordance with the requirements, standards, or criteria governing AwOs, particularly those contained or defined in the agreed to FAA/Sponsor OMM. The owner understands that noncompliance with the the specific site's FAA/Sponsor MOU/OMM may result in the AWOS's removal from service or decommissioning.
(12) A copy of any agreement with the NWS to maintain a SAWRS capability to augment or back up the AwOs.
e. Commissioning Documentation. The initial commissioning documentation form such as the Comprehensive Facility Performance and Adjustment Data form, should be completed during commissioning to record initial values. and the respective standard or reference values.
13.MAINTENANCE PROGRAM. Contents shows that a Maintenance program has been established. The Maintenance program should cover a minimum period of 5 years (as established in paragraph 8b) and should consist of properly trained personnel meeting all FCC and FAA requirements, adequate test equipment, and resources to fulfill the manufacturer's recommended scheduled maintenance and calibration procedures defined in the manufacturer's Maintenance
Manual. The Maintenance program is the responsibility of the owner, but may only be performed by a person meeting FAA and FCC requirements. A person meeting FCC and FAA AWOS maintenance requirements will be issued a FAA verification authority letter.
a. Maintenance Personnel. The owner should show that the Maintenance program adopted has qualified personnel available to maintain the AWOS system. FAA Order 6700.20A, Non-Federal Navigational Aids and Air Traffic Control Facilities, contains the qualifications for maintenance technicians that maintain non- Federal facilities. They should have the special knowledge and skills needed to maintain the AwoS facility and should have completed the manufacturer's training program or the FAA-approved Concepts Bypass exam (paragraph 8e). They should be able to demonstrate proficiency in accomplishing the required maintenance procedures and using the specialized test equipment. The FAA will issue an unrestricted FAA verification authority letter to the candidate maintenance person if he/she is able to meet the concepts and performance requirements of the AwoS system and has a FCC general radiotelephone license for maintenance of the associated transmitter.
b. Test Equipment. The owner should have available at the facility, at the time of commissioning, all test equipment required by the approved maintenance plan for maintenance and calibration of the facility. Test equipment must be capable of accurately measuring the appropriate technical standards and tolerances needed for facility verification. Test equipment should be calibrated in accordance with the schedule submitted to (and approved by) the FAA during type acceptance. In case an acceptable test equipment calibration schedule was not included, test equipment will be calibrated as per the test equipment manufacturer's recommendations or the FAA/Sponsor MOU/OMM. Test equipment calibration should be traceable to national standards, and proof of calibration (e.g., a current calibration sticker) should accompany each piece of test equipment when it is being used. After commissioning, the test equipment should be available when required for scheduled system maintenance and calibration or for repairs after system failure.
c. Annual Performance/Configuration Revalidation. The owner should plan for complying with the manufacturer's recommended procedure for annual system revalidation (paragraph 8f and 14). This plan should include a list of the procedures to be followed during the revalidation and the source of the qualified person to conduct the inspection.
14.ONGOING SYSTEM VALIDATION. To verify that the system is being properly maintained and that the system retains an approved configuration, the following ongoing validation program should be conducted.
a. Performance/Configuration Revalidation. A FAA regional qualified technical representative should inspect each Awos annually in accordance with the manufacturer's approved Annual System Revalidation Plan (paragraph 8f). This inspection should include the items in subparagraphs (1) through (4), and the results should be recorded on an Annual Technical Performance Record form or on a Comprehensive Facility Performance and Adjustment Data form identified as being used for annual revalidation and retained on file at the facility.
(1) Verify that the Maintenance program is being followed and properly documented.
(2) Perform a comprehensive check and calibration to verify that system performance is within the limits specified by the manufacturer's documentation and to ensure that every component of the system is operating properly.
(3) Verify that the AWOS configuration is the same as approved at the time of commissioning or as formally modified in accordance with approved configuration control procedures. Additionally, it should be determined that all mandatory configuration changes approved by the FAA have been accomplished and documented.
(4) Verify that a summary of all maintenance (hardware and software) performed since the last report is on file at the facility.
b. FAA Site Visits. FAA inspectors will periodically visit certified non-Federal AWOS facilities. During the inspection, the FAA inspector will verify that the system operates within tolerance, that all maintenance tasks have been properly performed and documented, and that the FAA has approved the Awos configuration. The inspector may review the facility's FAA Form 6030-1 log and other documentation to verify if scheduled (periodic) and unscheduled maintenance, and the documentation of these activities, have been accomplished in accordance with this AC, the approved FAA/Sponsor MOU/OMM, the manufacturer's
Maintenance Manual, and the annual system revalidation plan provided to and approved by the FAA during the type approval process. The owner's maintenance technician holding FAA verification authority should provide access to the site and accomplish any tests on the facility requested by the FAA representative during the visit. The FAA will provide the sponsor a written inspection report following completion of the inspection. The FAA representative may visit the site with a sponsor's representative without the non-Federal technician's presence provided no tests or adjustments are planned or accomplished on the AwOS equipment.
c. Mandatory Configuration Changes. If the FAA determines that an Awos system, or any element of the system, is providing data that could be in error, the FAA may direct the system manufacturer to issue a mandatory configuration change order to the owners of similar systems. The system owner should disable the appropriate part of the system and should request that the FAA issue a NOTAM describing the missing parameter and giving an estimate of the time for which it will be disabled.
d. Unacceptable Failure Rate. Equipment that proves unreliable is to be removed from the approval listing. The determination of unreliability should be based on judgment and experience with similar equipment. Where ch equipment is determined to have an unsatisfactory failure rate or is deficient in workmanship or materials, the manufacturer is to be notified in writing as to the basis for this determination. The manufacturer should then notify the FAA in writing as to its plan of action for resolving the issue. If the manufacturer does not resolve the problem within a reasonable time (the timeframe would, of necessity, be based on safety considerations/the nature of the problem), the equipment would be removed from the approval listing. The FAA reserves the right to require the equipment to undergo any or all qualification/calibration tests when the equipment has been determined unreliable or deficient in design, materials, or workmanship. Owners of similar AwOs's should be notified of any problems uncovered during this retesting through the configuration control procedure discussed in paragraphs 9 and 14c.
Failure to meet the criteria of this program may result in decommissioning the AwOs facility (i.e., withdrawal of the broadcast frequency authorization).
CHAPTER 3. PERFORMANCE AND TESTING SPECIFICATIONS FOR AWOS
15.GENERAL. This chapter contains the performance standards and testing specifications for components of the AwOs. Equipment should comply with these standards to establish partial compliance with the Code of Federal Regulations (CFR). However, some of the following tests are intended to be performed in a laboratory environment and may not be able to be duplicated in the field. Current standards and tolerances are those which were approved during type acceptance. These are intended only as guidelines based on standards approved at type acceptance.. If a manufacturer has specified additional checks to be performed, requested and received approval for different checks to be performed, or specified that tighter tolerances be required, then these will be detailed in the FAA-approved Maintenance Manual for that specific type-certified AwOs.
CHAPTER 3. PERFORMANCE AND TESTING SPECIFICATIONS FOR AWOS
16.DEFINITIONS.
a. Root Mean Square Error (RMSE). RMSE is determined by comparing the output value with the true value of a parameter according to the following equation:
1N
Where
N = Number of independent comparisons M = Measured value T = True value
b. Time Constant. After a step change in the value of a parameter measured by a sensor, the time constant is the length of time it takes the sensor to register a given percentage (63 percent unless otherwise specified) of the change.
c. Resolution. The resolution of a sensor is the value of the least significant digit that is given as sensor output.
d. Variance. For the purposes of this AC, variance is defined as the difference between the value of the reference sensor and the sensor under test.
e. Thunderstorm. For purposes of this AC, a "thunderstorm" occurs when a single cumulonimbus cloud (cell) generates one or
more flashes of lightning which can be cloud-to-ground, in-cloud, or cloud-to-cloud. At any one time, a period of storm activity may consist of a number of thunderstorms or cells within the area surrounding the reference point.
17.GENERAL PERFORMANCE STANDARDS.This paragraph addresses aspects of performance that are applicable to the Awos as a whole. The electromagnetic interference, transient, and lightning protection standards are also applicable to the entire system and are addressed in paragraphs 33 and 34.
a. Input Power. AwOS equipment operates from a 120/240 V (±10 percent), 60 Hz ac (±5 Hz), 3-wire single-phase service.
b. Loss of Power. The Awos system should return to normal operation without human intervention after a power outage. When power is restored, the system should not output erroneous data.
c. Wind Sensor Tower. If a separate tower is used for the wind sensor, daytime marking and nighttime lighting should be provided in accordance with the guidelines set forth in AC 70/7460-1H, Specification for Obstruction Marking and Lighting.
(1) It should be lighted with a dual L-810 fixture placed within 5 feet of the top of the tower. The two lamps on the L-810 should be wired in parallel. The standards for the L-810 fixtures may be found in AC 150/5345-43, Specification for Obstruction Lighting Equipment, which may be ordered from the Department of Transportation, Utilization and Storage, M-443.2, Washington, DC 20590.
(2) Since the nominal height for this tower is 30 to 33 feet and since most towers are manufactured in 10 foot sections, a waiver to AC 70/7460-1H has been granted to permit a six-band marking, with the bands alternating between aviation orange (the top band) and aviation white. This pattern will permit dip painting the tower at the factory without sacrificing the level of safety provided by the standard tower.
d. VHF Transmitter. It is the FAA policy that the output of the AWOS will be transmitted on an existing NAVAID voice outlet whenever practical. When the AWOS is broadcast over a NAVAID, that NAVAID will be given a flight check during the initial commissioning procedure and will be given an annual flight check in conjunction with the annual AwOS verification. If there is no
NAVAID available, then the output will be broadcast via a separate VHF transmitter that will be licensed by the FCC. The transmitter operates in the 118-137 MHz band on a frequency assigned by the FAA. The transmitter will have a FCC type-acceptance with the following operational parameters:
Channel Spacing: 25 kHz
Normal radio frequency (RF) Power Output: nominal 2.5 watts (+/-10 percent), at the transmitter output or the transmitter output power necessary to generate a maximum effective radiated power of 1 watt. Note: Other transmitter powers between 1 and 10 watts may be authorized based on unusual circumstances. However, the FCC license always lists the maximum effective radiated power authorized for any AwOs.
The FAA may authorize power output levels between 2.5 watts and 10 watts (maximum), if needed, to meet unusual circumstances.
Frequency stability: ±0.001 percent (-30° to +60° C)
Percentage of modulation: 65 percent to 95 percent
Voltage standing wave ration (VSWR) at transmitter: 3.0 to 1
VSWR at antenna: 3.0 to 1
Antenna: Omnidirectional
Line Loss: Should use coax with less than 3 db of line loss per 100 feet for lines over 30-feet long. May use coax with up to 10 db per 100 feet for lines up to 30-feet long.
VSWR at the antenna and line loss do not normally need to be measured if line length between transmitter and antenna is less than 50 feet.
Emission type: 6A3E
Spurious and harmonic emissions: 80 db down from the carrier minimum up to 90 percent modulation
Occupied Bandwidth No less than 99 percent of the emitted signal energy should be contained within a 25kHz bandwidth.
Frequency, power-out, percent modulation, vSWR at the transmitter. If necessary, due to line length, VSWR at the antenna and transmission line loss should be measured and recorded during initial and annual reverification checks.
e. Generation of the NAVAID Identifier by the AWOS. When the AWOS message is broadcast over a NAVAID, the AWOS should be designed to provide both the NAVAID tone identifier and the AWOS weather data over the NAVAID frequency. The tone should be generated between every Awos voiced weather message and should only be generated between messages. This design should eliminate the interference between the AwOS voice and the NAVAID generated tone identifier and provides for better identification of the NAVAID in marginal conditions. If this design is adopted, it is imperative that the NAVAID automatically return to using its internal tone generator to provide the identifier, if the AwOs capability to provide the NAVAID identifier has been lost.
f. VHF/UHF Data Link Radio Transmitter. When a VHF or UHF radio is used to transfer data between components of the system, the transmitter will have FCC type-acceptance, and the power output should be limited to the minimum necessary to accomplish the job and should not exceed 1 watt. The FCC issues the license for the use of the facility and assigns the frequency. Frequency stability, deviation/percent modulation, VSwR, and initial/operating power output should be in accordance with FCC regulations and should be clearly defined in the manufacturer's Maintenance Manual. AM and FM data link radio transmitter specifications are contained in FAA Order 6560.13B. No data link radios authorized under Part 15 of the FCC rules (47 CFR, Part 15) may be used to transfer data between components of the system.
g. Code Requirements. The Awos should be designed in accordance with applicable paragraphs of the NEC and should be installed in accordance with local code requirements.
18.OPERATING ENVIRONMENT. Al1 AWOS equipment and sensors should demonstrate that they meet all operating tolerances under the environmental conditions described in this AC and, as can be expected, in a normal operating environment. Equipment that cannot satisfy the full range of conditions may be waived for operation in locales where those conditions do not occur. Waivers will only be permitted if sufficient evidence is provided to the FAA to warrant a waiver.
a. Site Elevation. From 100 feet below sea level to 10,000 feet above sea level. b. Equipment Installed Indoors in a Conditioned Space. (1) Temperature. From +40° to +105° F (+5° to +40° C). (2) Relative Humidity. 5 percent to 90 percent (noncondensing).
c. Equipment Installed Outdoors.
(1) Temperature. Class 1: -30° to +130° F (-35° to +55° C) Class 2: -65° to +130° F (-55° to +55° C) (2) Relative Humidity. 5 percent to 100 percent.
(3) Wind. Up to 85 knots. (4) Hail. Up to 1/2 inch in diameter. (5) Ice Buildup. Freezing rain rate equivalent to a buildup of 1/2 inch per hour, lasting for a period of 1 hour. The accuracy of the wind sensors is permitted to deteriorate during icing conditions. (6) Rain. Up to 3-inches per hour, with 40 knot winds.
19.WINDSPEED AND DIRECTION SENSOR.
a. Performance Standard.
(1) Windspeed Sensor. (a) Range. The sensor should respond to a threshold of 2 knots and a maximum of at least 85 knots. (b) Accuracy. The windspeed sensor should provide an accuracy of ± 2 knots up to 40 knots. Above 40 knots, RMSE should be within ± 5 percent. (c) Resolution. The resolution should be 1 knot.
(d) Distance Constant. The distance constant should be less than 10 meters. The method for calculation is given in subparagraph b(1) (ii).
(e) Threshold. 2 knots.
(2) Wind Direction Sensor. This sensor should be aligned to true north and withstand a windspeed of 85 knots without damage.
(a) Range. 1° to 360° in azimuth.
(b) Threshold. 2 knots.
(c) Accuracy. Within +/- 5° (RMSE)
(d) Resolution. To nearest 1°; dead band not to exceed 7°wide.
(e) Time constant. Less than 2 seconds.
b. Performance Testing. Testing should be conducted in a calibrated wind tunnel, except for the wind direction accuracy tes that is conducted on a bench test fixture. The windspeed sensor should be compared against a calibrated pitot-static tube or transfer reference standard traceable to the National Institute of Standards and Technology. Sonic anemometers should be tested in a wind tunnel for directions using a rotating base. The test procedure in subparagraphs (1) and (2) should be used. During freezing rain conditions, the wind sensor accuracy may deteriorate to + or - 15 percent windspeed, + or - 10 degrees wind direction, and up to 3 sec. time constant response time.
(1)Windspeed.
(a) Accuracy and Resolution. The test is conducted under "no rain" conditions. Four full-test cycles (2-85 knots) should be conducted in increments of 2 knots between 2 and 10 knots, in increments of 10 knots between 10 and 80 knots, and at 85 knots. During these test runs, data should be gathered to demonstrate compliance with the requirements for accuracy and resolution. Tests demonstrating acceptable accuracy during environmental extremes as listed in paragraph 18 are to be conducted.
(b) Distance constant. The distance constant should be computed according to the following formula:
D= T X W
Where:
D = Distant constant (in meters). T = Time constant. W = Windspeed (meters per second) in the wind tunnel.
The distance constant should be determined from an average of 10 runs (5 runs each with the tunnel wind speed at 10 knots [5 meter/sec] and at 20 knots [10 meter/sec] with the sensor propeller speed at the zero at time zero). The distance constant should be less than 10 meters for the sensor to pass this test. If the sensor is of a type with no moving parts (i.e., no propeller), the manufacturer should develop a test for FAA approval to demonstrate compliance with the distance constant requirement.
(2)Wind Direction.
(a) Accuracy. This test should be conducted on a bench st fixture under "no rain" conditions. The accuracy of the sensor should be checked at each 10° increment. The accuracy should be checked in 2° increments between 350° and 010° (a dead band of up to 7° wide is permissible). Two complete test cycles should be conducted, and RMSE accuracy should be within specified limits. Tests demonstrating acceptable accuracy during environmental extremes as listed in paragraph 18 are to be conducted.
(b) Time Constant. The time constant should be determined from an average of 10 runs (5 runs each with the tunnel speed at 10 knots and at 20 knots). The vane should be displaced 10° from the indicated wind direction and released. The time constant should be less than 2 seconds to reach within 5° of the indicated wind direction.
20.AMBIENT TEMPERATURE SENSOR.
a. Performance Standards. The sensor should be thermally isolated to accurately measure environments below:
(1) Range. From -35° to +55°C (-30° to +130°°F) for Class 1 systems.
From -55° to +55°C (-65° to +130F) for Class 2 systems.
(2) Accuracy. 1F RMSE for the entire range of the sensor, with a maximum error of 2F.
(3) Resolution. Not greater than 1F.
(4) Time Constant. Not greater than 2 minutes.
b. Performance Testing.
(1) Accuracy. Temperature accuracy should be verified using a calibrated reference instrument traceable to the National Institute of Standards and Technology. The temperature sensor should be exercised through the full range of the device in 20°F increments. This 20° change in chamber temperature should be accomplished within 5 minutes of the test, and the sensor reading should be taken 5 minutes after the chamber temperature is stable. This test cycle should be performed a total of eight times (or four times with two sensors in the chamber). These cycles should include two increasing and two decreasing temperature cycles without radiation heating and two increasing and two decreasing temperature cycles with radiation heating on the aspirated enclosure of 1.6 gram-calories per square centimeter per minute. The accuracy of the sensor should be within 1°F (RMSE) for each test cycle (a total of 9 data points for each Class 1 system cycle; 11 data points for each Class II system cycle).
(2) Time Constant. The sensor should be placed in a chamber and stabilized at 85F. The temperature should be rapidly raised (within 1 minute) 5° (to 90°F); the time constant should be 2 minutes or less. The same test should be repeated with a 5° decrease in temperature within 1 minute. The time constant should be 2 minutes or less.
21.DEWPOINT SENSOR. A single thermal shield and aspirator unit may include both the dewpoint and temperature sensors.
a. Performance Standards.
(1) Operating Range. From -30° to +90°F
(2) Dewcell Protection. If the dewpoint sensor is a dewcell, it should not be damaged if the sensor becomes excessively
wet (e.g., from precipitation or from absorption of moisture after a loss of power). The dewcell probe should return to normal operation, without damage and without human intervention, within 30 minutes after the abnormal, excessively wet condition is alleviated (i.e., after precipitation ends) or after restoration of power.
(3)Resolution. Not greater than 1F.
(4) Time constant. Less than 2 minutes.
(5) Accuracy. The accuracy should be as follows (all errors are RMSE):
(a) 2°°F dewpoint for dry bulb temperatures of +30° to +90°F (80 to 100 percent relative humidity), with a maximum error of 3°°F at any dry bulb temperature.
(b) 3F dewpoint for dry bulb temperature of +30° to +120°°F (15 to 75 percent relative humidity) with a maximum error of 4°F at any dry bulb temperature.
(c) 4°F dewpoint for dry bulb temperatures of -20° to 20°°F (25 to 95 percent relative humidity) with a maximum error of 5° at any dry bulb temperature. The minimum dewpoint required is -30°F.
b. Performance Testing.
(1) Accuracy. All tests should be performed with the sensor in the aspirated enclosure supplied with the sensor. Temperature and dewpoint accuracy should be verified using calibrated reference instruments traceable to the National Institute of Standards and Technology. The data points given in subparagraphs (i) through (iii) should be taken during four test runs (two with increasing humidity and two with decreasing humidity.) This may be reduced to two test runs if two sensors are placed in the chamber. During the test run, the change in temperature/relative humidity should be accomplished within 5 minutes, and the sensor reading should be taken 5 minutes after the temperature and humidity have stabilized. The following data points should be demonstrated and the RMSE calculated to demonstrate the error in each category.
(a) With an error not to exceed 2F (RMSE) dewpoint, 30°F temperature; 80, 90, 100 percent relative humidity 60°F temperature; 80, 90, 100 percent relative humidity 90°F temperature; 80, 90, 100 percent relative humidity
(b) With an error not to exceed 3F (RMSE) dewpoint, 30°F temperature; 15, 45, 75 percent relative humidity 60°F temperature; 15, 45, 75 percent relative humidity 90°F temperature; 15, 45, 75 percent relative humidity 120°F temperature; 15, 40 percent relative humidity
(c) With an error not to exceed 4F (RMSE) dewpoint, -20F temperature; between 65 and 95 percent relative humidity 0°°F temperature; 25, 60, 95 percent relative humidity +20°F temperature; 25, 60, 95 percent relative humidity
(2) Time Constant. At ambient temperature and 50 percent relative humidity, change the dewpoint +5°F (within 1 minute), and then -5°F (within 1 minute). In each case, the time constant should be less than 2 minutes.
(3) Power Interruption. At ambient temperature and 90 percent relative humidity, with the sensor operating normally, disconnect the power from the sensor for a period of 1 hour. Power should then be reapplied and the sensor should return to normal operation and accuracy within 30 minutes.
22.PRESSURE SENSOR.
a. Design. Two pressure sensors should be provided for each AwOS system. All pressure sensors should have provisions for venting to the outside of the building where required. Pressure variations due to airflow over the venting interface should be avoided. The venting interface should be designed to avoid any damp pressure variation and oscillation due to "pumping" or "breathing" of the pressure sensor, venting, and porting equipment.
Each sensor should have to be connected to the venting interface (from separate outside vents through dedicated piping to the sensors). Means should be provided to avoid insect nesting and moisture entrapment in the venting interface.
b. Performance Standards.
(1) Altitude Ranges. High pressure should be standard atmospheric pressure at -100 feet plus 1.5 inHg (30.03 + 1.5 = 31.53 inHg). Low pressure should be standard atmospheric pressure at +10,000 feet minus 3.0 inHg(20.58 - 3.00 = 17.58 inHg).
(2) Pressure Range. The sensor should be capable of measuring a pressure range at any fixed location (station) of +1.5 to -3.0 inHg from the standardatmospheric pressure at that location. Pressure sensors should have a provision for setting the sensor to the station elevation to the nearest 1 foot over the range of -100 feet to +10,000 feet.
(3) Accuracy. The accuracy should be 0.01 inHg RMSE at all altitudes from -100 to +10,000feet mean sea level (MSL), maximum error 0.02 inHg at any one pressure.
(4) Resolution. The resolution of the barometer should be displayed in 0.001 in Hg increments.
(5) Differential Accuracy. The sensor should exhibit an average differential accuracy of 0.01 inHg or less between a series of two pressure measurements taken from the same sensor 3 hours apart. Ambient temperature over this 3-hour period should not change more than 5°F. Ambient pressure should not vary more than 0.1 inHg (RMSE) over the 3-hour period.
(6) Maximum Drift With Time. Each sensor should be stable and continuously accurate within 0.01 inHg RMSE for a period of not less than 6 months. The maximum error should be 0.02 inHg.
c. Performance Tests.
(1) Accuracy. Both pressure sensors should successfully complete the following accuracy test. A calibrated barometer or transfer standard with an accuracy of at least 0.003 inHg, that is traceable to the National Institute of Standards and Technology, should be used as a standard during testing. Two test cycles should be performed on each pressure sensor. One test cycle is
defined as running the sensor through the full pressure range at each of the three ambient temperatures. Before taking measurements, allow sufficient time for the sensor to achieve steady state at each data point (not to exceed 5 minutes). The RMSE should be within the specified limits.
(a) Pressure Range. The pressure sensors should be tested through the full range of performance (normally 17.5 to 32.0 inHg) in 1-inHg increments of both increasing and decreasing pressure. Partial range (4.5 inHg) pressure sensors should be tested by setting the sensor to a pressure altitude from zero to 10,000 feet in 500-foot increments. The sensor should be tested from minus 3.0 inHg to +1.5 inHg at 0.5 inHg increments at each pressure altitude.
(b) Temperature Range. The sensor should be tested at ambient (approximately +85F) and at the hot and cold extremes called for in the environmental requirements.
(2) Differential Accuracy. Differential accuracy (change in accuracy) of the pressure sensor should be tested at ambient temperature (approximately 85°F) and ambient barometric pressure.
(a) Take 14 measurements of pressure on the pressure sensor under test and 14 measurements of pressure on the reference barometer. These measurements should be taken about 5 seconds apart and all 14 measurements should be completed within 90 seconds. This time should be called t=0.
(b) Repeat the 14 measurements on the pressure sensor under test and 14 measurements of pressure on the reference barometer after an elapsed time of 3 hours. The ambient temperature should have changed less than 5°F, and the ambient pressure should have changed not more than 0.1 inHg. This time should be called t=3.
(c) Compute the average reading of the reference barometer at t=0. Compute the average reading of the reference barometer at t=3. Determine the difference in the two averages. If the difference is greater than 0.1 inHg, or if the average difference between the reference and the test barometer at either t=0 or t=3 is greater than 0.02 inHg, repeat steps (i) and (ii).
(d) Compute the 14 errors in reading between the sensor and reference barometer at t=0.
(e) Compute the 14 errors in reading between the sensor and reference barometer at t=3.
(f) Subtract the 14 t=0 errors from the 14 t=3 errors determined in steps (iv) and (v). Preserve the order of subtraction such that the first t=0 error is subtracted from the first t-3 error. These differences are the changes in accuracy (the differential accuracy).
(g) Compute the average and standard deviation of the 14 changes in accuracy determined in step (vi). The average differential accuracy should be no greater than 0.010 inHg. The standard deviation should be less than 0.003 inHg.
(3) Resolution. The manufacturer should demonstrate that the barometer resolution is displayed in 0.001 inHg increments.
(4) Drift Over Time. Testing should be accomplished to determine maximum drift [paragraph 22b(6)] over a 6-month period.
23.CLOUD HEIGHT SENSOR.
a. General. The cloud height sensor should have a design range of 12,500 feet, or greater. The sensor should provide an output of three cloud layers representative of the sky conditions when surface visibilities are equal to or greater than 1/4 mile. Sensors should comply with the performance standards throughout their design range.
b. Performance Standards. The sensor should detect the height of atmospheric phenomena (i.e., clouds and obscuring phenomena aloft) or, in the event the phenomena are surface based (e.g., fog), provide an estimate of the contact height (CH) or vertical visibility (VV). CH is defined as the vertical height above ground at which visual reference to recognized lights or objects on the surface can be established sufficiently to permit visual determination of the ground plane and position. VV is defined as the vertical distance that an observer can see vertically into surface-based obscuring phenomena (e.g., dust, fog, sand, etc.), or the height corresponding to the upper limit of the return of the ceilometer signal, or the height corresponding to the height at which a balloon would completely disappear during the presence of surface-based phenomena (i.e., an obscured sky).The sensor should have the capability of discriminating between a negative response
(i.e., no hit), resulting from no phenomena within the sensor's design range, and a sensor error/fault. The sensor should not indicate a response (i.e., hit) that is not the result of the detection of atmospheric phenomena.
(1) Range. The sensor should measure cloud heights and the heights of obscuring phenomena aloft to a minimum of 12,500 feet.
(2) Accuracy. Under laboratory conditions, the sensor should provide an accuracy of 100 feet or 5 percent, whichever is greater.
(3) Resolution. Not greater than: 50-feet surface. to 5,500 feet; 250 feet from 5,501 to 10,000 feet; 500 feet above 10,000 feet.
(4) Detection Performance. The sensor should perform within the limits specified in paragraphs 23c(2) and 23c(3).
(5) Sampling. The sensor should provide an output at least once every 30 seconds. However, to extend sensor life, this sampling rate may be reduced to provide at least one sample every 3 minutes when. no cloud, obscuring phenomena aloft, or CH/VV valu (i.e., hits) are detected for the preceding 15 minutes.
(6) Eye Safety. The cloud height sensor should be designed to conform to ANSI-Z 136.1, Accessible Emission Limits for Laser Radiation, with Class 3b maximum accessible emission level applied to direct viewing without optical instruments (excluding ordinary eye glasses). This document may be obtained from the American National Standards Institute, 1430 Broadway, New York, New York, 10018. Interlock device(s) in the laser power circuit should be provided to disable the laser when any doors are open or the cover is removed to prevent inadvertent exposure of the laser emission to the eyes of the technician or others. The interlock(s) may have a manual override in order that power can be purposely restored during maintenance.
(7) Laser Power Stability. The sensor should contain a self-check, self-adjusting feature that should maintain laser output power at the level necessary to sustain sensor detection and accuracy. When this adjustment can no longer provide the compensation necessary to maintain the sensor within specified operational limits, sensor operation should be terminated.
(8) Optics Contamination. An air blower or other device should be used to reduce the contamination of the sensor optics. A signal should be generated to indicate the amount of optics contamination, thereby indicating the need for optics cleaning.
(a) Snow. The ceilometer window should demonstrate an ability to remain clear of snow under the condition of snow accumulating at a rate of 2 inches per hour for 1 hour at a temperature of 20°F.
(b) Ice. The ceilometer window should remain clear of ice for 60 minutes under conditions of freezing rain with a maximum accretion rate of 1⁄2-inch per hour radial thickness of clear ice.
c. Performance Testing.
(1) Accuracy Test. The signal should be projected horizontally to a target at known distances (two distances, separated by at least 1,000 feet, from 100 to 5,500 feet; two distances, separated by at least 1,000 feet, from 5,600 to 10,000 feet; and one distance beyond 10,000 feet). Al1 range points should be within the accuracies specified in aragraph 23b(2). This test is a laboratory test conducted at full ated power output. It is not intended to be duplicated when the AwOS is installed in the field.
(2) Detection Tests Under Uniform Sky Conditions.
(a) Test Conditions. The sensor should be tested under the following conditions:
Group A. Visibility greater than 3 miles, with a minimum of 10 percent of the data sets in each subgroup (table 1) collected with light precipitation (rain and snow) occurring, and a minimum of 10 percent with moderate precipitation (rain and snow) occurring.
Table 1. Group A Test Conditions
Subgroup Cloud Height (feet) 1 100-700 2 800-1500 3 1600-3000 4 3100-5500 5 5600-12500
Group B. Visibility equal to or less than 3 miles, but equal to or greater than 1 mile, with a minimum of 10 percent of the data sets in each subgroup(table 2) with light precipitation (rain and snow) occurring, and a minimum of 10 percent with moderate precipitation (rain and snow) occurring.
Group C. Visibility equal to or greater than 1/4, but less than 1 mile, with a minimum of 10 percent of the data sets in each subgroup (table 3) collected with light precipitation (rain and snow) occurring, and a minimum of 10 percent with moderate precipitation (rain and snow) occurring.
Table 2. Group B Test Conditions
Subgroup Cloud Height (feet) 1 100-700 2 800-1500 3 1600-3000 4 3100-5500 5 5600-12500
Table 3. Group C Test Conditions
Subgroup Cloud Height (feet) 1 100-700 2 800-1500 3 1600-3000 4 3100-5500 5 5600-12500
Group D. Not more than 3/10 total sky coverage with the lowest cloud layer at 20,000 feet or higher under the visibility conditions in table 4, with a maximum of 80 percent of the data in each subgroup collected under daytime conditions.
Table 4. Group D Test Conditions
Subgroup Visibility (miles)
1 Equal to or greater than 1, but 1ess than 3
2 Equal to or greater than 3, but less than 7
AC150/5220-16C
3 Equal to or greater than 7
(b) Collection of Test Data.
(i) A minimum of 25 data sets should be collected for each subgroup in Groups A through C (i.e., a minimum of 125 data sets should be collected under each group). However, if weather conditions at the test site over a period of 1 year make collection of at least 25 data sets in every subgroup impossible, the FAA should consider approval of a lesser number of data sets in the affected subgroups after analysis of available data. Further, for test data to be acceptable, a continuous test period should be selected to allow for collection of representative data.
3 Equal to or greater than 7
Also, it should be clear that all data collected during the test period were considered. Any data not used should be explained. For example, if data analysis in a subgroup is truncated after 25 data sets are analyzed, this fact should be documented and explained.
One data set is defined as the second 10-minute period during which a uniform cloud or obscuration is detected by a rotating beam eilometer (RBC) or is determined by a qualified weather observer. n order to be classified as a uniform cloud or obscuration, the RBC should continuously measure (or a qualified weather observer should determine) a cloud, obscuration aloft, or vertical visibility height (for a 30-minute period) that does not vary from its mean height more than the variance shown in table 5 more than 5 percent of the time.
(ii) A minimum of 25 data sets should be collected. for each subgroup under Group D. One data set is defined as the second 10-minute period of any consecutive 30-minute period during which the cloud/sky coverage/visibility conditions specified for group D are met.
Table 5. Criteria for Determining Uniform Cloud Layers
Mean Height (as determined by observer or as Variance measured by RBC) (feet) Equal to or less than 1,000 ft. 200
Greater than 1,000 ft., but equal to or less than 2,000 ft. 300
Greater than 2,000 ft., but equal to or less than 400 3,000 ft.
Greater than 3,000 ft., but equal to or less than 5,000 ft. 500 Greater than 5,000 ft., but equal to or less than 7,000 ft. 600 Greater than 7,000 ft., but equal to or less than 9,000 ft. 700 Greater than 9,000 ft., but equal to or less than 12,500 ft. 800
(c) Test Standards
(i) An FAA-approved cloud height indicator whose accuracy-is traceable to a NWS approved and calibrated RBC, or observations taken by a qualified weather observer, should be the standard for determining heights and sky conditions.
(ii) An FAA-approved visibility sensor whose accuracy is traceable to an FAA standard should be the standard for determining visibilities.
(iii) Liquid precipitation measurements should be made using an FAA-approved 0.01 inch per tip tipping bucket precipitation gage. Light precipitation is defined as one, but not more than two buckets tips in a 10-minute period. Moderate precipitation is defined as more than two, but not more than five tips in a 10-minute period. Heavy precipitation is defined as more than five tips in a 10-minute period. A qualified weather observer should determine the intensity of frozen precipitation.
(d) Criteria for Acceptance Under Uniform Sky Conditions.
(i) Groups A, B, and C conditions. The mean height of the cloud, obscuration aloft, or vertical visibility (measured by the RBC or determined by a qualified weather observer) should be determined for each data set. The variance for each cloud, obscuration aloft, and CH/VV height (i.e., hit) detected by the candidate sensor in each data set should be computed. Eightyeight percent of the data sets within a subgroup (e.g., 22 out of 25 minimum) should satisfy the following condition: 90 percent of the heights determined by the candidate sensor in each data set should agree with the mean height measured by the RBC or determined by a qualified weather observer within the variance limits as shown in table 6. Negative responses, i.e., no hits by the candidate sensor, should be included as data points and considered to be outside the variance limits. Also, the no-hit percentage in each
subgroup should not exceed 5 percent. The candidate sensor should successfully demonstrate the conditions in table 6 for each subgroup to pass this test. Failure of any subgroup constitutes failure of the test.
(ii) Group D conditions. Not more than one false hit per data set in each subgroup. More than one false hit per data set should constitute failure of the test.
(3) Detection Tests Under Ragged Overcast or Obscured Sky Conditions.
(a) Heights (cloud/obscuration aloft or CH/VV) measured by the candidate sensor should be compared with heights measured by the RBC or determined by a qualified weather observer during ragged overcast or obscured sky conditions. Valid data should be that collected during overcast or obscured sky conditions below 12,500 feet as verified by an RBC hit percentage of 95 percent or more, or as determined by a qualified weather observer, during a 20-minute period. Negative responses, i.e., no hits, should be included as data points and considered to be outside the variance limits. Calculate the percent of heights (i.e., hits) by the ndidate sensor falling within the ranges in subparagraph (i) nder each of the conditions specified in subparagraph (ii) with allowable height variances as specified as in table 6. Data should be collected under as many of the conditions as possible; however, the FAA may accept less than the specified requirement after evaluation of the available data. For test data to be accepted, a continuous test period should be selected to allow for representative data collection. It should also be clear that all data collected during the test period were considered. Any data not used should be explained.
Table 6. Criteria to Satisfy Groups A, B, and C Conditions
Variance (feet) for Variance Mean height (as determined by cloud and obscuration for CH/VV observer or as measured by RBC) aloft heights (feet) values (feet) Equal to or less than 1,000 ft. 200 400
Greater than 1,000 ft., but 300 600 equal to or less than 2,000 ft.
Greater than 2,000 ft., but 400 800 equal to or less than 3,000 ft.
Variance (feet) for Variance Mean height (as determined by cloud and obscuration for CH/VV observer or as measured by RBC) aloft heights (feet) values (feet) Greater than 3,000 ft., but 500 1,000 equal to or less than 5,000 ft.
Greater than 5,000 ft., but 600 1,200 equal to or less than 7,000 ft.
Greater than 7,000 ft., but 700 1,400 equal to.or less than 9,000 ft.
Greater than 9,000 ft., but 800 1,600 equal to or less than 12,500 ft.
(b) Height ranges (as determined by RBC or qualified observer)
(i) 100 - 700 feet
(ii) 800 -1,500 feet
(iii) 1,600 -3,000 feet
(iv) 3,100 -5,500 feet
(v) 5,600 -12,500 feet
(c) Conditions:
(i) No precipitation. Visibilities 1/4 to 1 mile, 1 to 3 miles, and greater than 3 miles.
(ii) Light or moderate precipitation (rain and snow). Visibilities 1/4 to 1 mile, 1 to 3 miles, and greater than 3 miles.
(iii) Heavy precipitation (rain and snow). Visibilities 1/4 to 1 mile, 1 to 3 miles, and greater than 3 miles. (d) A minimum of 90 percent weighted average of the hits by the candidate sensor should fall within the range of the RBC or
within the height range determined by a qualified weather observer. Also, the weighted negative response, (i.e., no hit) percentage should not exceed 5 percent.
24.VISIBILITY SENSOR.
a. Performance Standards.
(1) Range. The visibility sensor should be capable of determining visibilities from less than 1/4 mile to 10 miles. A method of calibration traceable to the FAA-approved standards in paragraph 24b should be provided.
(2) Resolution. In terms of equivalent visibility, the sensor should provide data to report visibility values as follows (in statute miles): less than 1/4, 1/4, 1/2, 3/4, 1, 1-1/4, 1-1/2, 2, 2-1/2, 3, 4, 5, 7, and 10 miles. For information, revisions to the Federal Standard Algorithms and the ADAS Interface Control Document (ICD) are being processed to add the following additional incremental reporting values (in statute miles) for Awos located with an airport traffic control tower: 3/8, 5/8, 7/8, 2-1/4, and 2-3/4 miles.
(3) Accuracy. The sensor should agree with the transmissometer standards as follows:
Table 7. Visibility Sensor Accuracy Requirement.
Reference Transmissometer Reading Acceptable Sensor Variance 1/4 through 1-1/4 ± 1/4 1-1/2 through 1-3/4 + 1/4, -1/2 2 through 2-1/2 ± 1/2 3 through 3-1/2 + 1/2, -1 4, and greater than 4 ± 1
(4) Time Constant. The time constant should not exceed 3 minutes.
(5) Ambient Light Sensor. The visibility sensor should contain an ambient light sensor (i.e., a photocell) to measure the ambient luminance within its field of view and generate a signal to the visibility sensor to indicate whether the ambient light level is day or night. It should indicate day for increasing illumination between 0.5 and 3 foot-candles (FC) and night for decreasing illumination between 3 and 0.5 FC. This sensor may be exposed to ambient light levels as high as 50 FC.
b. FAA-Approved Visibility Standards. The high visibility reference standard should be a visible light transmissometer(s) that uses a narrow band of light centered at 0.55 microns (95 percent of the response within ±0.03 microns of 0.55 microns) for visibility ranges to an extinction coefficient of 3 mile-1. At higher extinction coefficients, an FAA-approved transmissometer(s) that includes some infrared radiation may be substituted as a standard. Comparisons with scatter-type instruments (different from those being tested) may be used to correct for small drifts in reference standard calibration.
c. Performance Tests. The visibility sensor should be tested using FAA-approved transmissometers as the reference standard.
(1) Accuracy Testing.
(a) At least 2 months of accuracy test data should be accumulated, assuring that a representative number of valid test points are experienced at each of the reporting increments [par 24a(2)], and under conditions of both with and without precipitation. All data collected during the test should be included in the test report. Any samples not included in determining the candidate sensor's accuracy should be fully explained. For example, data collected under inhomogeneous conditions may be excluded from the accuracy analysis, if so explained. The test data should consist of a number of independent samples of 10 minutes each, with at least 5 minutes between each sample. Samples should consist of visibilities from less than 1/4 mile, to greater than 10 miles, and should be weighted in the following ratio:
70 percent without precipitation (i.e, with fog, under clear conditions, and with approximately 5 percent of the data points collected under summer haze conditions)
30 percent with precipitation (e.g., 15 percent with rain, 15 percent with snow)
(b) Eighty percent (overall weighted average) of the total of all sensor test data points should agree with the transmissometer standard within the allowed variances from less than 1/4 through 5 miles.
(c) Eighty percent of the sensor test samples that are obtained when the transmissometer reads greater than 5 miles should be 5 miles or greater.
(2)Time Constant Demonstration. Under conditions of 10-mile visibility, a technique should be used to reduce the sensor detector output to 1 mile or less. After the restriction is applied, the time constant should be measured to reflect the reduction of visibility. After a period of 10 minutes, the artificial restriction to visibility should be removed, and the sensor time constant should be measured to reflect the increase in visibility. The time constant should be equal to or less than 3 minutes.
(3) Ambient Light Sensor Testing. The manufacturer should demonstrate that the ambient light sensor complies with paragraph 24a(5) and the visibility output is updated accordingly when the light sensor changes status from day-to-night or night-to-day.
25. PRECIPITATION OCCURRENCE AND ACCUMULATION SENSOR(S). The term "precipitation" is defined as including all forms (i.e., liquid, eezing, frozen, or combinations thereof). The term precipitation amount" is the liquid or liquid equivalent amount. The precipitation sensor provides an indication of precipitation occurrence and measures the precipitation amount.The sensor(s) may be designed as a single or separate unit.
a. Performance Standards.
(1) Precipitation Occurrence Sensor. The sensor should detect the occurrence of precipitation as specified. It should not "false alarm" on other moisture sources such as dew and frost.
(a) Precipitation Onset. The sensor should detect the onset of precipitation 95 percent of the time as follows:
(i) With the precipitation rate of 0.11-inches per hour or more, the sensor should detect the onset of precipitation within 1 minute.
(ii) With precipitation rates of 0.05 to 0.10-inches per hour, the sensor should detect the onset of precipitation within 2 minutes.
(iii) With precipitation rates of 0.01 to 0.04-inches per hour, the sensor should detect the onset of precipitation within 5 minutes.
(iv) With a precipitation rate of less than 0.01, but equal to or greater than 0.0005-inches per hour, the goal should be the detection of the onset of precipitation within 10 minutes.
(b) Precipitation Cessation. The sensor should detect the cessation of precipitation within 5 minutes, 95 percent of the time.
(2) Precipitation (Liquid Equivalent) Accumulation. The sensor should be capable of measuring the precipitation amount with a range of 0.01 to 5-inches per hour, with a resolution of 0.01 inches and an accuracy of 0.002 inches per hour (RMSE), or 4 percent of actual (whichever is greater).
b. Performance Testing. The manufacturer should conduct a test program to demonstrate that the precipitation occurrence and accumulation sensor(s) meet the performance requirements under the environmental conditions found in paragraph 18.
26.Precipitation Type Sensor. The term "precipitation type" as used herein includes the following: rain, drizzle, snow, ice pellets, and hail. The precipitation type sensor should provide an indication of the type of precipitation occurring, or should output "precipitation" for any precipitation (liquid, freezing, frozen, or combinations thereof) when a type cannot be identified. However, recognizing that the sensor technology is not yet available to identify ice pellets and hail, a precipitation type sensor may qualify by identifying only rain, drizzle, and snow while outputting "precipitation" for those types not identified. The sensor unit may be designed as a separate unit or may be combined with the requirements of other parts of this AC (e.g., paragraph 24) so that one unit fulfills the requirements of two or more paragraphs.
a. The sensor should identify the type of precipitation when the rate of precipitation equals or exceeds 0.002 inches per hour, with the goals for accuracy as follows:
(1) Within the temperature range of: (a) +28°F to +38F, identify precipitation type correctly as:
(i) Rain: 90 percent of the cases.
(ii) Drizzle: 80 percent of the cases. (iii)Snow: 90 percent of the cases. (iv) Ice pellets (optional):50 percent of the cases. (b) Less than +28°F. Identify precipitation type correctly as snow in 99 percent of the cases. (c) Greater than +38°F, identify precipitation type correctly as: (i) Rain: 99 percent of the cases. (ii) Drizzle: 90 percent of the cases.
(iii)Hail (optional): 90 percent of the cases. (2) Priority: Only one precipitation type should be reported, with the reporting priority established in subparagraphs (a) through (f).
(a) Hail.
(b) Ice pellets.
(c) Snow.
(d) Rain.
(e) Drizzle. (f) Precipitation, no type defined. b. Performance Tests. The manufacturer should conduct a test program to demonstrate that the sensor satisfies the performance standards under the environmental conditions in paragraph 18. As a minimum, the following test conditions should be satisfied.
(1) Prior to testing, the AwOS manufacturer should develop and submit a test plan to the FAA for approval to the address shown at the front of this AC. The test plan should clearly outline the tests to be performed, it should define the capabilities of the . sensor to be tested, and it should include a detailed description of the test procedures. It should contain a clear statement of pass/fail criteria. The test plan should identify the location(s) and the proposed time planned for the tests. All data collected during the test should be incorporated into the test report. Any data not included in determining the candidate sensor's compliance with the requirements of this circular should be fully explained.
(2) The test should be conducted in two phases. One phase should be conducted in a test chamber with varying conditions simulated to generate drizzle, rain, snow, hail, and ice pellets. At least 15 events (at various rates of accumulation) should be simulated for each of these conditions to demonstrate the above requirements and the results should be included in the test report.
(3) The second phase of the test should be conducted at a location(s) and during the times when there is a propensity for drizzle, rain, snow, hail, and ice pellets and where there is a qualified weather observer on duty. The test report should compar the performance of the sensor under test with the log maintained by the official observer at the test location.
27.Thunderstorm Detection Sensor or Network. This stand-alone sensor or thunderstorm detection network should detect the presence of a thunderstorm within 30 nm of an airport, should locate the thunderstorm, and should provide this data in such a form that the information can be incorporated into the Awos voice and data weather message.
a. Performance Standards.
(1) Range and direction. Thunderstorms within 30 nm of the reference point on the airport should be reported. Direction is expressed in compass octants for distances from 10 to 30 nm.
(2) Resolution. The thunderstorm location should be defined within 1 nm of the location of the actual location of the thunderstorm/lightning.
(3) Accuracy.
(a) The standard detects strikes within 10 nm of the reference point:
(i) Detection Accuracy. Ninety percent of all thunderstorms identified and located within this area by the thunderstorm sensor/network standards should have been detected by the thunderstorm sensor/network under test.
(ii) Location Accuracy. The distance from each thunderstorm located by the sensor standard within 10 nm of the reference point, and the corresponding thunderstorm located by the sensor/network under test, should be computed. The RMSE of these distances accumulated during the test period should not exceed 3 nm.
(b) The standard detects strikes between 10 nm and 30 nm of the reference point:
(i) Detection Accuracy. Eighty percent of all thunderstorms identified and located within this area by the hunderstorm sensor/network standards should have been detected by ie thunderstorm sensor/network under test.
(ii) Location Accuracy. The distance from each thunderstorm located by the sensor standard between 10 nm and 30 nm of the reference point, and the corresponding thunderstorm located by the sensor/network under test, should be computed.The RMSE of these distances accumulated during the test period should not exceed 6 nm.
(4) False Reports. Not more than 2 percent of all thunderstorms reported by the sensor under test should have been caused by sources other than a naturally occurring thunderstorm.
(5) Sensor/System Reporting to the AwOS. The thunderstorm sensor/network should update the Awos once each minute.
b. Performance Tests. The manufacturer should conduct a test program to demonstrate that the thunderstorm sensor/network meets the performance standards under the environmental conditions identified in paragraph 18.
(1) Prior to Testing. The AwOs manufacturer should develop and submit a test plan to the FAA for approval at the address shown at the front of this AC. The test plan should outline the tests to be performed, it should clearly define the capabilities of the sensor/network to be tested, and it should include a detailed description of, and the capabilities of, the method that should be used to prove that the sensor is performing in accordance with the performance standards (paragraph 27a). It should define the criteria necessary for the standard(s), as well as the sensor/network under test, to recognize a thunderstorm. A clear statement of pass/fail criteria should be included. If the sensor/network proposed should only detect cloud-to-ground lightning or if it should detect other evidence of a thunderstorm, this fact should be clearly identified. The test plan should identify the locations and the proposed time planned for the tests. The test should be conducted in at least two locations (i.e., reference points) where there is a propensity for thunderstorms.
(2) Duration of the Test. The test should encompass a sufficient period of time to accomplish the following minimum detection/location events to prove that the sensor/network under test conforms with the requirements of this circular. A thunderstorm day is a day during which thunderstorm data are accumulated from the standard(s) and the sensor/network under test
(a) Summer Environment. Thunderstorms should have been detected during at least 25 thunderstorm days during the summer months at a location where there is a high level of thunderstorms generated by summertime convection activity. It is desirable that at least 100 thunderstorms (i.e., cells) should have been detected and located by the standard(s) during the summer test.
(b) Winter Environment. Thunderstorms should have been detected during at least 10 thunderstorm days during the months of November through February at a cold weather location where there is a propensity for thunderstorms associated with mid-latitude winter storms. It is desirable that at least 20 thunderstorms (i.e., cells) should have been detected and located by the standard(s) during the winter test.
(3) Thunderstorm Detection Standards. All means available within the test area to identify and locate thunderstorms should be used. These "standards" should include:
(a) Qualified Weather Observer(s). Qualified weather observers should be used to identify and locate thunderstorms within the vicinity of the reference point. The observer should identify a thunderstorm in accordance with the criteria in FMH-1. The time and the estimated location (bearing and distance) should be logged when identifying the existence (beginning time) of a thunderstorm. Once a thunderstorm has been identified, observations should be recorded every 10 minutes. The ending time of the thunderstorm should be identified. The results of these observations should be plotted on a grid of approximately 3 nm squares, with the reference point in the center, and an area encompassing a circle with a radius of 10 nm. The scale of this plot should be the same as the scale of the radar echo plot. A plot should be made every 10 minutes. All plots for these tests (e.g., observer, radar, network, system/network under test) should be based upon the same time periods (e.g., beginning on the same minute).
(b) Weather Radar. Weather radar may be used to identify and locate thunderstorms within the area under test. The radar antenna should be located within 30 miles of the reference point. Level three and greater intensity radar echoes should, by hemselves, constitute the detection of a thunderstorm. Level two adar echces, when correlated with another standard observation of a thunderstorm or with a report from the sensor/network under test, should constitute detection of a thunderstorm. However, if the sensor/network under test does not recognize a level two radar echo as a thunderstorm, and the level two echo is the only evidence of a thunderstorm, a thunderstorm should not be assumed to be present. Plots of the area under test from the radar screen should be made every 10 minutes and should depict levels two through six radar echoes. Plots should be made on a grid of approximately 3 nm squares with the reference point as the center. The highest intensity level should be marked in each grid square.
(c) Thunderstorm Network(s) as a Reference Standard. Network(s) may be used to identify and locate thunderstorms. Thunderstorms identified and located by a thunderstorm sensor network should be plotted on a grid identical to the grid used for the radar echo plot (i.e., approximately 3 nm squares on a 30 nm radius circle, with the reference point as the center). Plots should be made of the area under test every 10 minutes.
(d) Secondary Reference Systems. The use of secondary reference systems should be fully defined in the test plan.
(4) Execution of the Test. After the test plan is approved, the manufacturer should perform the test in accordance with the test plan. All data collected during the test should be included in the test results. Any data omitted from the results should be fully explained. Thunderstorms identified and located by the thunderstorm sensor/network under test should be plotted on a grid identical to the grid used for the radar echo plot (i.e., approximately 3 nm squares on a 30 nm radius circle, with the reference point as the center). Plots should be made of the area under test every 10 minutes. The test plan should establish the criteria for the system that is tested, as well as all of the sensor/network standards, to be operational. As a minimum, in order for a thunderstorm day to be counted in the test results, a qualified weather observer should take observations and the weather radar should be operational when testing.
(5) Test Report. A report should be prepared and submitted to the FAA by the AwOS manufacturer, in accordance with the requirements of this AC, to obtain certification of its AWOS with a thunderstorm detection, location, and reporting capability. Data obtained during this test should be analyzed as follows:
(a) Within 10 nm of the reference point. The grid plot. obtained from the sensor under test should be matched with the grid plots obtained from the standards (qualified weather observer, the weather radar, thunderstorm sensor network, etc.), for each 10 minute increment. Thunderstorm occurrences should be matched as previously described (e.g., paragraphs 27b(3)(ii) and 27b(4)) and anomalies explained.
(i) The number of test sensor/network identifications should be compared with the number of thunderstorms identified by the standards. The percentage detection accuracy should be computed and compared with the requirement in paragraph 27a(3)(i)a.
(ii) The number of test sensor/network identifications that are in the same or an adjacent 3 nm grid square as the thunderstorm identified by the observer/sensor/ network standard should compared with the number of thunderstorms identified by the standards. The percentage location accuracy should be computed and compared with the requirement in paragraph 27a(3)(i)b.
(b) Between 10 nm and 30 nm of the reference point. The grid plots obtained from the sensor under test should be matched with the grid plots obtained from the standards (qualified weather observer, the weather radar, thunderstorm sensor network, etc.) for each 10-minute increment.Thunderstorm occurrences should be matched and anomaliesexplained.
(i) The number of test sensor/network identifications should be compared with the number of thunderstorms identified by the standards. The percentage detection accuracy should be computed and compared with the requirement in paragraph 27b(3) (ii)A.
(ii) The number of test sensor/network thunderstorm identifications should be counted that are in the same, an adjacent, or in a grid square separated by one square from the 3 nm grid square where an observer/sensor/network standard located a thunderstorm. This number should be compared with the number of thunderstorms identified by the standards. The percentage location accuracy should be computed and compared with the requirement in paragraph 27a(3) (ii)B.
(c) The number of thunderstorms identified by the ensor/network under test that cannot be matched with a thunderstorm identified by the standards (i.e., false signals) should be counted and compared with the total number of thunderstorms identified by the standards. The percentage of false signals should not be greater than the percentage identified in paragraph27b(4).
(6) Basis of the reporting algorithm. The AWOs sensor/system should locate and report a thunderstorm within one of 10 areas of a circle with the reference point as the center and a radius of 30 nm, as follows:
Within a circle with a radius of 5 nm, with the reference point at the center.
Within the circular area between 5 nm and 10 nm from the reference point.
Within one of eight 45-degree clockwise sectors of the circular area between 10 nm and 30 nm from the reference point, beginning with the 22.5 degree radial from the reference point.
(7) AWOS Report of a Thunderstorm (TS). The AWOS voice and data report should be in accordance with the latest Governmentfurnished algorithm. This algorithm processes lightning strike data through a 15-minute moving window, i.e., each strike is expired 15 minutes after it is received. With certain exceptions, the algorithm should report a thunderstorm when two lightning strikes have been received within the 30 mile radius circle within 15 minutes.
Within the 5 nm radius, the voiced report is "TS at the airport."
Between 5 and 10 nm of the airport, the voiced report is "TS in the vicinity."
Continue reading ↓ 120 of 163 passages shown