Learn what AWOS means in aviation, what it reports, how pilots use it for take-off and landing, and which automated sensor limits matter.
AWOS (Automated Weather Observing System) is an airport-based system that automatically measures and broadcasts local weather. In real-world aviation, pilots listen before take-off or landing for wind, visibility, cloud, temperature, dew point and pressure, depending on the installation, then assess runway choice, performance and operating minima.
What does an AWOS report?
An AWOS report contains only the weather elements supported by that particular installation; the AWOS name does not guarantee a complete observation. The computer-generated voice usually repeats the airport identifier, observation time, measured conditions and any unavailable sensors.
| Reported element | How pilots use it | Key limitation |
|---|---|---|
| Wind direction, speed and gusts | Select a suitable runway and calculate headwind, tailwind and crosswind components | Measured at one sensor location; brief fluctuations may not appear |
| Visibility | Compare conditions with departure, arrival and instrument-approach requirements | A fixed sensor cannot represent every part of the airport or approach path |
| Sky condition and ceiling | Assess cloud clearance, approach conditions and the likelihood of entering cloud | A ceilometer samples the sky directly above or near the sensor |
| Temperature and dew point | Calculate performance and identify possible fog, frost or saturation | A narrow spread suggests possible saturation but does not guarantee fog |
| Altimeter setting | Set local pressure on the aircraft altimeter | Wrong units, an old observation or the wrong airport can produce a serious error |
| Precipitation or lightning | Identify potentially hazardous weather near the airport | Only suitably equipped AWOS installations provide these elements |
In the United States, AWOS-A provides an altimeter setting only. AWOS I normally adds wind, temperature and dew point; AWOS II adds visibility; and AWOS III adds sky condition and ceiling. Equipment suffixes can indicate precipitation, thunderstorm, lightning or freezing-rain detection. These classifications are not universal, so pilots must check the published capability for the airport.
Some commissioned systems also create a coded METAR, which may contain AUTO when the observation has no human augmentation. Our guide to decoding METAR weather groups explains how the voice information appears in the written report.
How do pilots use AWOS before take-off or landing?
Pilots use AWOS by listening to a complete observation, checking its time and status, then applying each reported value to the planned operation.
- Find the correct outlet. Obtain the published AWOS radio frequency, telephone number or data source from the airport information. Confirm the airport identifier rather than assuming the first broadcast heard belongs to the intended field.
- Listen to the complete cycle. Copy the wind, visibility, cloud, temperature, dew point, pressure and remarks. A missing element means that information is unavailable, not that the condition is favourable.
- Check the observation time. Weather can change faster than a stored or relayed report. Treat maintenance messages and stale observations as warning signs.
- Apply the wind. Calculate the runway component using both steady wind and gusts. At an uncontrolled airport, AWOS supports runway selection but does not declare an active runway; traffic, runway condition and local procedures still matter. At a controlled airport, ATC assigns the runway.
- Compare weather with limits. Check visibility against the applicable approach requirement and consider the ceiling wherever operating rules or procedures require it. Use temperature and airport elevation for take-off and landing performance calculations.
- Set and verify the altimeter. Select the reported altimeter setting or QNH using the correct inHg or hPa scale. While parked at a surveyed airport, the indicated altitude should be reasonably close to field elevation. A large discrepancy calls for a recheck of the airport, units, observation and instrument. See our explanation of when pilots update an altimeter setting.
- Recheck before the critical phase. Listen again before departure or arrival if conditions are changing, then cross-check the broadcast against the windsock, visible weather, ATC information and aircraft indications.
Wind-reference conventions also need attention. Coded METAR wind is normally referenced to true north, while operational radio wind may be presented relative to magnetic north under local conventions. Pilots should use the convention specified by the relevant aviation authority instead of applying variation by assumption.
Is AWOS the same as ASOS or ATIS?
AWOS, ASOS and ATIS are related but not interchangeable. AWOS and ASOS are sensor-based weather systems, while ATIS combines airport weather with operational information such as the landing runway, approach, significant notices and an identifying letter.
At a towered airport, pilots normally obtain the published ATIS because an AWOS observation alone does not include clearances or the full operational picture. At an uncontrolled airport, AWOS may provide weather while a separate traffic frequency carries pilot position reports. Our comparison of AWOS, ASOS and ATIS services covers the distinctions in more detail.
Can pilots rely on an automated weather observation?
A commissioned AWOS can provide an official local observation, but it is not a forecast, a complete weather briefing or a substitute for what the pilot can see and experience.
- It samples a small area. Fog, rain, wind shear or low cloud may affect one end of a runway or the approach while missing the sensor.
- It lacks human judgement. Automation can classify cloud and precipitation, but it cannot describe the weather with the contextual detail of a trained observer.
- It omits airport operations. AWOS does not report every closure, hazard, traffic conflict or runway restriction.
- It can fail partially. A report may remain available while one sensor is marked missing or out of service.
- It describes the surface. Surface temperature and wind do not reveal the full icing, turbulence or wind profile aloft.
What should pilots do if AWOS seems wrong?
Pilots should treat a significant conflict between AWOS and observed conditions conservatively. Recheck the station identifier and time, obtain other approved reports, compare the windsock and visible weather, and report a suspected fault to ATC or the airport operator.
Another airport's observation can show a regional trend, but it does not replace destination weather when local reporting is required. If actual conditions appear below personal, aircraft or regulatory limits, the safe response is to delay, discontinue the approach, go around or divert rather than rely on a favourable automated number.
How should flight-simulator pilots use AWOS?
In a flight simulator, AWOS is most useful for practising the real procedure: copy the observation, choose or confirm a runway, calculate wind components, check minima and set local pressure. The broadcast and rendered weather can disagree if the simulator, live-weather service or an add-on uses different data or update times.
A silent ATIS does not necessarily mean that an airport has no weather frequency; the field may publish AWOS or ASOS instead. Our Microsoft Flight Simulator radio-weather troubleshooting advice explains what to check when the expected broadcast is unavailable.