What Is METAR? The 2026 Guide for Drone Operators

Updated May 19, 2026.

METAR is an observation. It tells the operator what the weather looked like at the airport surface within the last hour. It is not a forecast, and the airport is rarely where the drone is actually flying. Operators who treat the most recent METAR as the answer to "is it safe to fly?" miss the gap between the runway reading and the urban canyon, ridge, or treeline where the aircraft is operating in the next thirty minutes.

The reason METAR still matters in 2026 is regulatory anchoring. The §107.51 cloud-clearance rules treat the ceiling reported in the nearest METAR as the legal reference point for "below the clouds." The visibility minimum (3 statute miles from the pilot location) cross-references the METAR visibility for any inspector reviewing a flight log. METAR is the document that an audit calls into evidence; on-site observation and the TAF forecast are the documents the operator actually flies by.

Quick answer: What is METAR? METAR (Meteorological Aerodrome Report) is the hourly coded weather observation issued by airports and weather stations worldwide. A METAR reports wind, visibility, weather phenomena, cloud cover, temperature, dew point, and altimeter setting at the observation site. For drone operators, METAR is the regulatory anchor for §107.51 compliance and a starting reference, not the on-site weather.

What is METAR and what does it tell a drone operator?
The METAR format in 30 seconds
The four METAR fields that matter most for drones
METAR vs. TAF: observed weather vs. forecast weather
The gap between airport weather and drone operating weather
METAR thresholds for go/no-go decisions
Where to access METAR data in 2026
METAR in the §107.51 compliance picture

What is METAR and what does it tell a drone operator?

METAR (Meteorological Aerodrome Report, sometimes Meteorological Terminal Aviation Routine Weather Report) is a coded hourly weather observation issued by airports and dedicated weather stations under ICAO Annex 3 and WMO Publication No. 782. The format is the same in Tokyo, London, and Atlanta, which is why a drone operator in any country reads the same fields in the same order.

For a Part 107 operator, a METAR delivers four pieces of operationally relevant data: wind direction and speed (with gust), visibility, ceiling (the lowest broken or overcast cloud layer), and surface temperature. Everything else in the report (dew point, altimeter setting, remarks, runway visual range) is either contextual or relevant only to manned aviation. A drone operator who reads the four operational fields and ignores the rest is reading the report correctly.

The 2026 reality is that METAR access usually routes through partner apps or platform integrations rather than the raw text. That is fine for routine flights. It is a problem when the partner app summarises the report incorrectly, when the integration lags by an hour, or when an inspector asks for the raw METAR that the flight log claims to have referenced. Reading the raw format remains a load-bearing skill for drone compliance at audit time.

The METAR format in 30 seconds

A METAR is a single line of space-separated fields in a fixed order. The example below is a typical observation:

METAR KJFK 121251Z 24016G24KT 10SM FEW250 21/M04 A3012 RMK AO2

The fields decode as follows:

METAR. The report type. METAR for the routine hourly observation; SPECI for a special report issued between hours when significant change is detected.
KJFK. The four-letter ICAO station identifier. Not the three-letter IATA code (JFK) used on airline tickets.
121251Z. Day of the month and Zulu (UTC) time. Day 12 of the month, 12:51 UTC.
24016G24KT. Wind direction (240°), speed (16 knots), gust (24 knots), unit (knots). Gusts are reported when they exceed steady wind by at least 10 knots.
10SM. Visibility, 10 statute miles. International stations use metres; 9999 means 10 km or more.
FEW250. Cloud cover code and base altitude in hundreds of feet AGL. Few clouds at 25,000 feet. Coverage codes are SKC/CLR (clear), FEW, SCT, BKN, OVC.
21/M04. Surface temperature 21°C, dew point minus 4°C. The M prefix indicates below zero.
A3012. Altimeter setting, 30.12 inches of mercury. International stations use Q1020 (hectopascals).
RMK AO2. Remarks begin. AO2 indicates a fully automated station with precipitation discrimination.

Weather phenomena, when present, appear between visibility and cloud fields. The codes follow intensity + descriptor + phenomenon. A few worth memorising:

Code	Phenomenon	Notes
RA	Rain	Prefixed `-` (light), unprefixed (moderate), `+` (heavy)
SN	Snow	Same intensity prefixes
FG	Fog	Visibility under 1 km
BR	Mist	Visibility 1–5 km
TSRA	Thunderstorm with rain	Combined descriptor + phenomenon
FZRA	Freezing rain	Combined descriptor + phenomenon
VC	In the vicinity (5–10 mi out)	Prefix for nearby phenomena

CAVOK (ceiling and visibility OK) in international reports replaces visibility and cloud fields when conditions are good (10 km+ visibility, no significant cloud below 5,000 ft, no significant weather). NSC means no significant cloud. Either one short-circuits the rest of the cloud/visibility decoding.

The four METAR fields that matter most for drones

Drone airframes operate well inside the weather envelope manned aviation considers benign, which means the four fields below carry most of the go/no-go signal.

Wind and gust. Surface wind on the runway is a starting estimate for wind at 100–400 feet AGL where the drone is actually flying. Building edges, ridge lines, and tree canopies create localised gust factors that the METAR does not capture. A METAR reporting 24016G24KT (16 knot steady, 24 knot gust) gives the operator a baseline; the on-site anemometer reading at takeoff is the operational figure.
Visibility. Reported from the observation station, not from the operating site. A 10 SM visibility downtown does not guarantee 10 SM visibility on a foggy ridge twenty miles inland. §107.51 requires 3 SM visibility from the remote pilot in command location regardless of what the airport reports.
Ceiling. The lowest broken or overcast layer defines the ceiling. A 1,200-foot ceiling from a METAR is a hard constraint for §107.51 cloud-clearance compliance (operating altitude + 500 ft must stay clear of clouds). For most Part 107 operations the constraint is operational rather than legal, since drones are capped at 400 ft AGL and the structure exception only goes 400 ft above the structure.
Temperature. Surface temperature is the input to battery state-of-health. Below 0°C, lithium polymer batteries lose meaningful capacity (manufacturer-specific curves vary; the fleet maintenance reference covers the testing). Above 35°C, motor and ESC thermal margins shrink. METAR temperature is the airport-surface reading; on-site temperature in direct sun or shaded canyons can deviate significantly.

The remaining fields (dew point, altimeter, remarks) matter at the margins. A small temperature/dew-point spread (within 4°C) raises fog probability and should trigger a TAF check. Rapid altimeter changes between hourly METARs indicate an approaching pressure system. The remarks section sometimes carries useful trend information (PRESRR for pressure rising rapidly, for example).

METAR vs. TAF: observed weather vs. forecast weather

A METAR is an observation; a TAF (Terminal Aerodrome Forecast) is a forecast. Both share the airport, the codes, and the format. They cover different time horizons.

Report	What it is	Time horizon	Issued
METAR	Observed weather at the station	Current hour (past hour included)	Hourly, with SPECI between hours
TAF	Forecast weather at the station	24–30 hours forward, in periods	Every 6 hours at most airports

The operator's question is rarely "what is the weather right now?" The relevant question is what the weather will be twenty minutes into the flight, which is the TAF's job. A typical TAF line breaks the forecast period into bands using FM (from), BECMG (becoming), and TEMPO (temporary) descriptors, each with its own wind/visibility/cloud forecast. Routine drone flight planning treats METAR and TAF as a pair, not as substitutes.

A worked example: an inspection flight planned for 14:00 local where the most recent METAR shows 10SM SCT040 22/15. Sounds fine. The TAF for the same station reads FM1300 14012G22KT 5SM -SHRA BKN025 BECMG 1416 12015G25KT 3SM TSRA OVC012. Translation: between 14:00 and 16:00, the forecast goes to 3 SM visibility in thunderstorms with rain and an overcast 1,200-foot ceiling. The METAR alone misses the storm window completely. The pair of METAR + TAF captures it.

For commercial drone work, both are required reading. The pre-flight checklist template should list both, alongside the broader pre-flight checklist routine, and the flight log should record both as evidence the operator checked.

The gap between airport weather and drone operating weather

The METAR is observed at the airport surface, typically next to a runway, at a station several feet above ground. The drone is operating somewhere else, often at 100–400 feet AGL, often in terrain or built environment that the airport surface does not reflect.

Three gaps account for most of the operational mismatch:

Vertical gradient. Surface wind is rarely the wind at 200 feet AGL. Buildings and ridges create turbulence that extends hundreds of feet upward; calm surface readings can hide dangerous gusts above. The weather-considerations reference covers the gradient effect in detail.
Horizontal distance. A METAR taken 15 nautical miles from the operating site can capture a different micro-climate. Coastal fog, valley inversions, and isolated thunderstorm cells all show up in one location and not the other.
Time lag. A METAR is up to an hour old by the next observation. SPECI reports fill in significant changes, but the time between the SPECI trigger and the broadcast can still be 5–10 minutes. For thunderstorm passages and sudden wind shifts, ten minutes is the difference between a go and a no-go.

The operational answer is to read the METAR as the regulatory anchor and the starting baseline, then verify on-site at the takeoff point. A hand-held anemometer, a visual check on the ceiling, and a phone weather app showing the local NWS observation together close the gap. Platforms that integrate live weather feeds with the flight planner (weather integration) compress that workflow into a single screen, but the discipline of cross-checking remains.

METAR thresholds for go/no-go decisions

Concrete thresholds keyed to §107.51 plus operational margin:

Visibility below 3 SM at the operating area. No-go. The §107.51 minimum is a hard legal floor for the pilot location, and the operating area should not be worse than the reporting station.
Visibility 3–5 SM. Caution. Legal under §107.51 but operational margin is thin. Reduce flight envelope; increase visual observer coverage. Treat any further visibility drop as no-go.
Ceiling at or below operating altitude + 500 ft. No-go. §107.51 cloud clearance requires 500 ft below clouds. A 600-ft ceiling rules out 100-ft operations under the rule.
Wind/gust above 60% of airframe rated max. Caution. Wind tolerance is rated for steady flight; gust factors above 50% of steady wind tighten the margin.
Wind/gust at or above 80% of airframe rated max. No-go. No headroom for unexpected gusts or recovery manoeuvres.
Temperature below 0°C or above 35°C. Caution. Battery and motor performance both degrade outside this band. Adjust flight duration and reserve margins.
Active TSRA, TSGR (thunderstorm with hail), or +SHRA in the METAR or TAF for the operating window. No-go. Lightning, hail, and heavy precipitation all carry equipment-damaging severity.

These thresholds are starting points. Each operation type (agricultural drone work, public safety and emergency response, urban inspection) has its own calibrated margins. The risk assessment guide covers the calibration workflow. Routine drone operations sit in Class G airspace, where the §107.51 cloud-clearance and visibility floors still apply. Controlled-airspace flights routed through LAANC authorisation carry the same §107.51 weather check on top of the airspace approval.

Where to access METAR data in 2026

The authoritative METAR source for the United States is the Aviation Weather Center, operated by NOAA with FAA coordination. The site delivers current METAR reports, TAF forecasts, SIGMETs, AIRMETs, and the standard analysis products in a single interface. The METAR data page provides observation-level access by station identifier or geographic bounding box.

Three other access paths matter operationally:

Direct station queries. The NWS surface observations system covers automated stations that may not be ICAO-coded. The NWS time-series tool returns historical observation strings useful for incident reconstruction and flight-log evidence.
FAA-approved partner apps. The same partner ecosystem that replaced the original B4UFLY airspace tool delivers METAR and TAF in mobile-friendly formats. These apps decode the codes for non-pilot operators and combine the weather layer with the airspace authorisation layer.
Platform integrations. Flight planning and operations platforms ingest METAR via the NOAA API and surface the operationally relevant fields next to the flight plan. The advantage is that the weather record attaches to the flight in the same data record as the airspace authorisation and the pre-flight check, which matters for drone flight reports and post-incident review.

The authoritative source remains aviationweather.gov. Partner apps and platform integrations pull from the same underlying NOAA feed, but the audit-defensible reference is the raw METAR string at the timestamp of the flight. The FAA aviation handbooks index (including AC 00-45 Aviation Weather Services) covers the regulatory expectation for weather information sources.

METAR in the §107.51 compliance picture

§107.51 sets four operational limits: maximum airspeed 87 knots, maximum altitude 400 ft AGL (with the structure exception), minimum visibility 3 SM from the remote pilot in command location, and a minimum distance from clouds of 500 ft below and 2,000 ft horizontal. The two that touch METAR are visibility and cloud clearance.

The FAA's expectation for a Part 107 operator is that visibility and ceiling were checked before takeoff against a current source. METAR is the standard source. An inspector reviewing a flight log after a complaint will look for evidence that the METAR (or the equivalent forecast/observation) was consulted at the right time. A flight log that records the METAR string at the takeoff timestamp passes that check; one that records "weather: good" does not. The pilot flight hours log and any incident reporting record should reference the same METAR string for traceability.

The 2026 enforcement reality is unchanged from the airspace-side picture. The civil penalty ceiling for Part 107 violations is $75,000 per violation under the FAA Reauthorization Act of 2024. A visibility or cloud-clearance violation under §107.51 is a separate violation from any airspace authorisation lapse or no-fly zone incursion, which means a single flight can stack multiple penalties. The defence in either case is the documentation trail: pre-flight check timestamp, METAR or equivalent reference, NOTAM and TFR confirmation, Remote ID broadcast evidence, and a recurring audit cadence that keeps the trail discoverable.

For Part 108 BVLOS operations (in late-stage rulemaking as of May 2026), the BVLOS compliance workflow is expected to require automated weather-source integration with the flight authorisation system. METAR will remain the underlying observation; the system around it gets tighter.

Three things to fix this quarter

Reading METAR is a skill; using it consistently is a programme. Three concrete actions:

Record the raw METAR string in every flight log. Not "weather: clear." The 60-character METAR line at the takeoff timestamp. This single change converts the weather check from a memory to an artefact and survives the audit it was meant to pass.
Pair METAR with TAF for any flight more than 15 minutes long. The TAF catches the storm window the METAR misses. A go/no-go decision based on METAR alone is the most common pattern under any "we got caught in unexpected weather" incident.
Cross-check the airport METAR against a site observation before every flight. A hand-held anemometer at the takeoff point and a visual check of the ceiling close the airport-to-site gap. The two-minute check has more operational value than the report from 15 miles away.

The penalty for a §107.51 visibility or cloud-clearance violation is $75,000 per occurrence under the 2024 ceiling. The three checks above cost about three minutes per operation.

FAQ

What is the difference between METAR and TAF?

METAR is an observed weather report covering the current and most recent hour. TAF (Terminal Aerodrome Forecast) is a forecast covering the next 24–30 hours, issued every 6 hours at most major airports. Drone operators planning anything beyond a 15-minute flight benefit from reading both.

How often is a METAR updated?

Hourly for routine observations. Between hourly METARs, automated and staffed stations can issue SPECI (special) reports when specific change thresholds are crossed: visibility, wind, ceiling, weather-phenomena onset, or pressure shifts. SPECI follows the same format as METAR but with SPECI as the leading identifier.

What METAR conditions ground a drone under §107.51?

Visibility below 3 statute miles at the operating site or a ceiling that does not leave 500 feet of cloud clearance above the planned operating altitude. Both are §107.51 minimums. The §107.51 visibility minimum is measured from the remote pilot in command location, not the airport, so the operating-site reality governs.

Can I rely on METAR for the actual conditions where my drone will fly?

No. METAR is observed at the airport surface, often miles from the operating site and minutes-to-an-hour out of date. It is the regulatory anchor and the starting reference. On-site observation, a TAF forecast for the operating window, and any flight-data monitoring feeds from the aircraft itself fill in what METAR cannot.

Ready to keep weather records on the same page as flight logs?

DroneBundle attaches the METAR string (raw, with timestamp) to each flight in the operations record, alongside the pre-flight checklist, airspace authorisation, and post-flight log. The weather evidence is queryable on incident review and exportable for audit pulls without digging through separate weather apps. Tour the features to see the operations record in full, or the live tracking page for in-flight telemetry that pairs with the weather log.

Start your free trial today, no credit card required.

Or try the live demo to see weather records, flight logs, and compliance documentation in one workflow.