Skip to content
+91 9711451451
Rational Technologies
RTPL PRODUCT SEARCH

What are you looking for?

Runway markings lead toward the airfield and tree line at Skellefteå Airport, Sweden.

Airport Weather Observing System (AWOS)

Integrated airport meteorological observation, data processing and reporting, configured around runway requirements and operational interfaces.

Discuss an AWOS Requirement

One observation system.
Multiple operational needs.

Connect the measurements made across an airfield with the people and systems that need a consistent weather picture.

  1. 01

    Observe

    Measure relevant conditions at representative airfield positions.

  2. 02

    Process

    Collect, check and bring observations into a coordinated system.

  3. 03

    Report

    Prepare the configured aviation reports and operational displays.

  4. 04

    Distribute

    Make information available through agreed user and data interfaces.

The reporting workflow, observer input and degree of automation are defined for each configuration.

Measurement coverage begins
with the airfield.

Different observations need different exposure. Begin with the runway layout, the operating requirement and the conditions each position must represent.

Representative observation positionsConcept only · Not to scale
Representative airfield observation coverageA single runway with separate symbolic wind positions A1 and A2, visibility and optional RVR positions B1 to B3, surface meteorology C and cloud observation D. Lines lead to a meteorological processing and operations destination. Locations are illustrative, not an approved placement plan. RUNWAY END / OBSERVATION ZONEMID-RUNWAYOPPOSITE END 0927 A1A2B1B2B3CD WINDWINDSURFACECLOUD Meteorological processing / operations A–D: measurement families · See key belowNRepresentative airfield observation coverage, mobile viewThe same conceptual single-runway system, rotated for readability. Wind A1 and A2 are on one side. Visibility and optional RVR B1 to B3 are on the opposite side. Separate surface weather C and cloud D positions connect to meteorological processing and operations. Use the text key below. No distances or approved positions are implied. 0927 A1A2B1B2B3CD Meteorological processingand operations ROTATED VIEW
Observation data pathRVR positions, where configuredPositions are symbolic, not prescribed locations.

Representative wind positions for the runway and local exposure.

Visibility observations; additional RVR positions where required.

Temperature, humidity, pressure and precipitation functions.

Cloud base and sky-condition inputs from the selected system.

Final siting, obstacle clearances, frangibility, exposure and observation coverage require a project-specific review with the relevant aviation and meteorological authorities.

The meteorological picture,
assembled from relevant measurements.

Define the observation functions first. Select instruments, positions and processing around the required aviation information.

01 / Wind

Surface wind

Wind speed, direction and the required averaging or gust treatment, related to representative runway positions.

Explore wind instruments
02 / Air

Temperature and humidity

Air temperature and relative humidity, with exposure and shielding suited to the site and the required derived values.

Explore temperature & humidity
04 / Visibility

Visibility and present weather

Visibility and weather identification from the selected observation method. An RVR requirement adds its own measurement and processing scope.

Explore visibility & present weather
05 / Cloud

Cloud height / sky condition

Cloud-base and related sky-condition information, with the required sensor coverage and observation workflow.

Explore cloud observation
06 / Precipitation

Precipitation and supplementary observations

Precipitation measurement and any additional observation needed for the airfield’s operating conditions.

Explore precipitation instruments
Additional scope, where required

RVR, lightning / thunderstorm detection and other specialist observations are defined separately. Catalogue availability does not establish compatibility with a proposed AWOS.

From field measurement
to aviation information.

A connected architecture brings observations from the airfield into processing, reporting and the interfaces required by airport users.

AWOS / Conceptual information architectureRead left to right
01

Field measurement

Surface weather
Visibility & cloud
RVR / supplementaryWhere configured
02

Data acquisition

Collect observations from the selected field instruments.

03

Communications

Carry observations over the defined site links.

04

Central processing

Data checks & validationConfigured calculationsReport preparation

Observation context remains part of the information pathway.

05

User interfaces

Meteorological staff
Air traffic control

Displays and reporting workflows for the relevant user.

06

Data distribution

Aviation reports
Agreed system interfaces

Recipients and formats defined in the project scope.

Configured supporting layers
  • System status & alarms
  • Historical records
  • Optional redundancy
  • Remote diagnostics

Conceptual roles, not a wiring diagram or a verified bill of materials. Instrument interfaces, resilience and distribution pathways must be confirmed for the selected system.

A documented system pathway

RTPL lists CORTEX AWOS with MetObserver processing and reporting, alongside central processing, RVR and ATIS resources. Use these as the starting point for a defined configuration.

Explore CORTEX AWOS

Weather information
where it is needed.

One observation pathway can serve different responsibilities. Define what each user needs to see, review and receive.

ProcessingObserve & report

Meteorological personnel

Configured displays, report preparation and access to historical observations support the meteorological workflow.

CORTEX documentation lists METAR, SPECI, MET REPORT and SPECIAL. Formats and observer responsibilities are confirmed for the selected configuration.

ProcessingOperational display

Air traffic control

Relevant runway weather information presented through the agreed operational display and update pathway.

Display content, positions, alarms and continuity requirements form part of the airport interface specification.

ProcessingData recipients

Connected systems

Reporting and data exchange through supported interfaces, with ATIS / D-ATIS or other recipients included where specified.

Existing system protocols, ownership and acceptance requirements must be checked before an interface is proposed.

Related RTPL resourcesCentral processing CORTEX RVR ATIS / D-ATIS

A system shaped by the airfield,
not a fixed package.

Start with the observation requirement, then establish the positions, infrastructure and information pathways needed to meet it.

Essential observation

Define the required weather functions, a representative observation site and the initial processing and reporting workflow.

A focused observation requirement

Expanded runway coverage

Add observation positions or RVR scope where operational requirements call for a more distributed runway weather picture.

Additional positions and measurement scope

Integrated multi-position airfield system

Coordinate multiple sensor sites, user positions and supported interfaces, with continuity requirements defined across the system.

Coordinated sites, users and interfaces

Illustrative scoping examples only. These are not fixed packages, certified classes or guaranteed configurations.

What defines the scope?

  • Runway layout & operational needs
  • Required observations
  • Visibility / RVR requirements
  • Site & infrastructure conditions
  • Power & communications
  • Reporting & interfaces
  • Continuity & maintenance requirements

From requirements
to a defined system configuration.

Structure the engineering discussion around a reviewable requirement, a clear system boundary and agreed responsibilities.

  1. 01

    Requirements and siting

    Establish the airfield layout, observation objectives, relevant authority requirements and site information needed for review.

    Define the requirement
  2. 02

    System configuration

    Review measurement functions, field positions, acquisition, communications and central processing as one connected scope.

    Define the system boundary
  3. 03

    Integration and verification

    Identify interface specifications, verification criteria and the acceptance evidence required from each project participant.

    Agree what must be demonstrated
  4. 04

    Handover and support planning

    Set out documentation, training, maintenance responsibilities and any requested support within the agreed proposal.

    Agree the delivery responsibilities

The contracted scope determines supply, installation, civil works, commissioning, approvals and support responsibilities. These are not assumed to be included.

Before you define the requirement.

Four practical questions for an airport weather project.

How is AWOS different from a general weather station?

An AWOS connects airfield observations with aviation-specific processing, reporting and operational users. A general weather station alone does not establish the required airport coverage, reporting workflow, system assurance or authority acceptance.

Is RVR always part of the AWOS configuration?

No. RVR scope depends on the airport’s operational and authority requirements. Where it is required, visibility measurement, background luminance, runway-light information and processing need to be considered together for the selected RVR method.

Can the system integrate with existing airport systems?

Potential interfaces must be reviewed against both systems’ documentation. Share existing equipment, software versions, protocols and required data formats. An integration is proposed only after compatibility, responsibilities and acceptance criteria are established.

What information is needed to prepare a proposal?

Provide the airfield location and runway layout, required observations, visibility / RVR needs, reporting and interface objectives, available power and communications, existing equipment, project stage and target timing. Identify the relevant aviation and meteorological stakeholders.

Planning an airport weather observation system?

Share the airfield configuration, measurement requirements and reporting objectives. RTPL can review the required system scope.

01What to measure
02Operating environment
03Required record
Explore products

This form continues to RTPL’s contact page. It does not confirm that your requirement has been received.