What does AWOS mean in aviation, and how do pilots use it?
AWOS in aviation means Automated Weather Observing System. Learn what it reports, how pilots use it, its limits, and how it differs from ATIS and ASOS.
AWOS stands for Automated Weather Observing System. It is an airport-based set of sensors that automatically measures local weather and broadcasts or distributes the observation. Pilots use the available wind, visibility, cloud, temperature, dew-point and pressure data to plan take-off and landing, set the altimeter and check operating limits.
This answer follows real-world practice, the focus of our Aviation & Real-World Flying section, then applies it to flight simulation. Exact capabilities and legal uses vary by country, aviation authority and installation, so the airport’s published station details govern.
What does AWOS mean in aviation?
In aviation, AWOS means an automated system that observes weather at or near an airport and makes that observation available to pilots, controllers and weather services. A commissioned AWOS may provide an official surface observation, but it is not a forecast or a complete pre-flight weather briefing.
The system combines weather sensors, processing equipment and one or more ways of distributing the result. Pilots may receive the observation through a repeating synthesised voice broadcast, a published telephone service or digital weather data, depending on the installation.
A radio broadcast usually identifies the airport, gives the observation time and reads the available measurements. AWOS is not one universal equipment package: the name alone does not guarantee that visibility, ceiling, precipitation or lightning information will be included.
What does an AWOS weather report include?
An AWOS weather report includes only the elements measured by that station’s installed and serviceable sensors.
| Reported element | How pilots use it | Main limitation |
|---|---|---|
| Wind direction, speed and gusts | Estimate headwind, tailwind and crosswind components and assess runway suitability | A sensor at one location may not represent the wind at both runway ends or on final approach |
| Visibility | Compare the reported value with departure, arrival and instrument-approach requirements | An automated sensor samples a limited area and may miss localised fog, rain or obscuration |
| Sky condition and ceiling | Assess cloud clearance and compare the ceiling with applicable procedures or operating rules | A ceilometer samples a small part of the sky; automated layers are calculated from that limited sample over time |
| Temperature and dew point | Calculate aircraft performance and assess the possibility of fog, frost or saturation | A small temperature–dew-point spread suggests possible saturation but does not prove that fog will form |
| Altimeter setting or QNH | Set the local pressure reference on the aircraft altimeter | The wrong airport, stale report or confusion between inHg and hPa can create a serious altitude error |
| Precipitation, thunderstorms or freezing rain | Identify hazardous weather detected near the station | These elements require optional sensors and are not available at every AWOS |
Missing information does not mean favourable weather. If the voice says a sensor is unavailable, or simply omits an element that the station does not support, the pilot must obtain that information elsewhere when it is required.
Do all AWOS stations report the same information?
No: an AWOS reports only what its particular equipment and classification support.
In the United States, the commonly encountered classifications broadly progress as follows:
- AWOS-A provides an altimeter setting.
- AWOS-AV provides an altimeter setting and visibility.
- AWOS I or AWOS-1 adds wind, temperature, dew point and related pressure or density-altitude information.
- AWOS II or AWOS-2 adds visibility to the AWOS I measurements.
- AWOS III or AWOS-3 adds sky condition and ceiling.
Suffixes may identify optional precipitation, thunderstorm or freezing-rain detection. These labels are not universal outside the United States, and even similarly named stations can differ, so pilots should check the published capability and maintenance status rather than infer it from the name.
The same sensors may also feed a coded METAR or SPECI. In a METAR, AUTO identifies an observation produced without human intervention; its absence may indicate human augmentation or a different reporting arrangement. Our explanation of METAR wind, visibility, cloud and pressure groups shows how the spoken measurements appear in coded form.
How do pilots use AWOS before take-off or landing?
Pilots use AWOS by identifying the correct station, copying a complete and timely observation, then applying each relevant value to the planned operation.
- Find the published outlet. Use the airport information to obtain the correct frequency, telephone number or digital source. Confirm the airport identifier rather than assuming that the first weather broadcast received belongs to the intended field.
- Listen to a complete cycle. Copy the time, wind, visibility, cloud, temperature, dew point, pressure and remarks that are available. Do not treat an omitted or failed sensor as reporting clear conditions.
- Check the observation time and status. Weather can change faster than a stored or relayed report. A maintenance message, missing element or old observation calls for another source and a more conservative assessment.
- Apply the wind. Calculate runway components using the steady wind and gusts. At an uncontrolled airport, AWOS helps with runway selection but does not declare an active runway; pilots must also consider traffic, the windsock, runway condition and local procedures. At a controlled airport, ATC assigns the runway.
- Compare conditions with the applicable limits. Use visibility and ceiling as required by the published procedure and operating rules. Ceiling is not the controlling value for every approach, so copy the actual minima rather than relying on a general flight category.
- Calculate aircraft performance. Use temperature, pressure, airport elevation, runway condition and wind in the aircraft’s approved performance method. AWOS supplies inputs; it does not calculate a safe take-off or landing distance for the pilot.
- Set and verify the altimeter. Enter the reported setting using the correct inHg or hPa scale. While parked at a surveyed airport, indicated altitude should be reasonably consistent with field elevation within expected instrument tolerances. A large discrepancy requires a check of the station, units, report age and instrument; do not simply force the altimeter to read field elevation. See our guidance on when to update and cross-check an altimeter setting.
- Recheck before the critical phase. Obtain another observation before departure or arrival if conditions are changing, then compare it with the windsock, visible weather, ATC updates and aircraft indications.
Wind-reference conventions deserve care. Coded METAR wind is normally referenced to true north, while radio wind used operationally may be given relative to magnetic north under local rules. Pilots should follow the convention specified by the relevant authority rather than adding or subtracting magnetic variation by assumption.
Is AWOS the same as ASOS or ATIS?
AWOS is not the same as ASOS or ATIS, although all three may provide airport weather.
| Service | What it provides | How pilots should treat it |
|---|---|---|
| AWOS | Automated local weather from the sensors installed at that airport | Check the station’s actual capabilities; the AWOS name does not guarantee a complete observation |
| ASOS | An automated surface observation, often forming part of a national weather-observing programme | Use the reported elements and status rather than assuming ASOS is always more capable than every AWOS |
| ATIS | Airport weather plus operational information such as runways, approaches, significant notices and an identifying letter | Obtain it when published at a controlled airport and report the information identifier when contacting ATC |
ATIS may incorporate weather produced by AWOS or ASOS, but it adds the operational picture that a standalone weather broadcast lacks. If ATC subsequently gives updated wind or pressure, pilots use that update according to local procedures rather than relying on an older ATIS cycle.
A dedicated AWOS outlet is for receiving weather, not making traffic calls. At an uncontrolled airport, use the published traffic frequency separately. Our side-by-side explanation of AWOS, ASOS and ATIS covers their roles and when each source is appropriate.
Can pilots rely on an automated weather observation?
A serviceable, commissioned AWOS can be an official source of local weather, but pilots must recognise what its sensors cannot observe.
- It samples a limited area. Fog, rain, wind shear or low cloud can affect one runway end or the approach while missing the sensor location.
- It reports observations, not forecasts. AWOS does not show what a front, thunderstorm or fog bank will do during the next stage of the flight.
- It has no broad visual judgement. Automation can classify detected cloud or precipitation but cannot describe the whole airport environment as a trained observer might.
- It can fail partially. The broadcast may continue while one sensor is marked missing or out of service.
- It does not provide the full airport status. A standalone AWOS does not replace notices, runway-condition information, clearances or traffic awareness.
- It describes surface conditions. Surface wind and temperature do not reveal the complete turbulence, icing or wind profile aloft.
A mistake we often see in simulator flying and real-world study is treating a favourable automated number as more authoritative than an obvious conflict outside the windscreen. AWOS is evidence to assess, not permission to continue regardless of actual conditions.
What should pilots do if AWOS seems wrong or is unavailable?
Pilots should verify the station and use other approved information whenever an AWOS report conflicts significantly with observed conditions or required data is unavailable.
Listen again to confirm the identifier, observation time, units and maintenance remarks. Cross-check ATIS, ASOS, a coded observation, ATC information, the windsock and visible weather as applicable. A nearby airport may reveal a regional trend, but it does not necessarily represent conditions at the destination.
Do not substitute a nearby altimeter setting for a missing local setting unless the instrument procedure or governing rules explicitly permit it. Some approaches prescribe higher minima or become unavailable when the required local pressure source is missing.
If the reliable evidence indicates conditions below personal, aircraft, procedural or regulatory limits, the correct response is to delay, discontinue the approach, go around or divert. A suspected equipment fault should be reported to ATC or the airport operator through the appropriate channel.
How should flight-simulator pilots use AWOS?
Flight-simulator pilots should use AWOS to practise the same cockpit workflow while recognising that the broadcast, navigation database and rendered weather may come from different data sources.
Copy the observation, calculate wind components, select or confirm the runway, compare visibility and ceiling with the procedure, set local pressure and brief the likely conditions. This is more useful than treating the voice report as background audio.
If the expected AWOS cannot be heard:
- Check the simulated airport data. A real airport’s frequency may have changed or may not be represented in the simulator’s navigation database or scenery.
- Check the radio setup. Put the frequency in the active COM window, select the correct receiver on the audio panel and confirm that the aircraft’s electrical and avionics systems are powered.
- Consider reception and implementation. Some simulators simplify radio range or omit individual automated transmitters, particularly at smaller airports.
- Identify the weather source. Live weather, a preset, an add-on and a network session can use different observations or update times. The broadcast may therefore disagree with the windsock, map or visual cloud layer.
- Do not confuse ATIS with AWOS. A silent ATIS does not prove that no automated weather service exists, and an AWOS broadcast will not supply runway assignments or other ATIS information.
For Microsoft Flight Simulator, our radio and automated-weather troubleshooting steps cover the common causes of a missing or silent airport broadcast without relying on version-specific menu paths.