SPECI Reports in Aviation: The “Interrupt-Driven” Weather Update Pilots Actually Feel
- wifiCFI
- Feb 12
- 5 min read
If METARs are the steady heartbeat of surface weather reporting, SPECI reports are the adrenaline spikes: unscheduled updates issued when conditions change enough to matter operationally—right now.
A SPECI can be the difference between launching on an approach you still have minimums for… or finding out the field just dropped into fog, the ceiling collapsed, or a thunderstorm rolled onto final.
Below is a practical look at what SPECIs are, what triggers them, how to read them, and how to use them well.
Study this full length lesson (video, podcast, flashcards, and quiz) here: Full Length Lesson >
What is a SPECI?
SPECI is the identifier used for a special (unscheduled) aerodrome weather observation issued when certain criteria are met.
A key point: a SPECI isn’t a “partial” report. In most systems, it’s essentially a full METAR-style observation, just taken outside the normal schedule. In U.S. guidance, SPECI is described as an unscheduled observation that generally contains the same data elements as a routine METAR (with limited exceptions for rare “single-element specials” in extreme situations).
METAR vs SPECI: Same format, different “why”
METAR (routine)
A METAR is the routine observation issued on a fixed schedule (the exact schedule can vary by country and station, but many are hourly or half-hourly).
SPECI (special)
A SPECI is issued when one or more elements meet defined criteria significant to aviation—think visibility/ceiling thresholds, thunderstorms, freezing precipitation, wind shifts, etc.
Useful U.S. nuance: if special criteria are met exactly at the time a routine report is due, the report is typically coded as METAR, not SPECI.
Why SPECIs matter operationally
Many flight decisions are “threshold decisions”:
Can we legally start or continue an approach?
Are we above alternate minimums?
Are crosswinds within aircraft or company limits?
Is a runway change likely?
Is convective weather now affecting the field?
SPECI triggers are designed to fire when conditions cross meaningful thresholds. So when you see a SPECI, assume: something operationally important changed.
Who creates them (and what “truth” they represent)
Many aerodrome reports are generated by automated weather stations, sometimes with human augmentation (for example, observers adding visibility, weather, and cloud details when automation can’t represent it well).
Also important: METAR/SPECI values represent the best observation at the time, not a promise of what you’ll see in every corner of the airport environment. Weather varies rapidly—especially in fog, snow showers, and convective conditions—so treat SPECIs as high-quality snapshots that you should integrate with other information.
When does a SPECI get issued?
This is where people get tripped up: SPECI criteria can vary by country/authority. The core concept is consistent (issue a special report when conditions cross operational thresholds), but the exact thresholds and rules differ.
Below are two commonly referenced frameworks:
United States: Federal Meteorological Handbook No. 1 (FMH‑1)
International baseline: ICAO Annex 3
If you fly internationally (or even just read reports from different states/authorities), don’t assume every SPECI trigger list is identical.
Common U.S. SPECI triggers (FMH‑1 style)
The U.S. trigger set is built around changes likely to affect runway selection, approach legality, and safety. Common examples include:
Wind-related
Wind shift: a direction change of 45° or more in less than 15 minutes with wind speed 10 knots or more throughout the shift.
Visibility and RVR
Visibility crossing key thresholds (commonly including 3 / 2 / 1 statute miles, plus an additional threshold tied to local approach minima).
Runway Visual Range (RVR) crossing operationally significant values (one commonly cited value is 2400 feet on the highest-designated RVR runway).
High-impact phenomena (starts/ends)
Tornado, funnel cloud, waterspout observed (and when it ends).
Thunderstorm begins or ends.
Squalls.
Certain precipitation events begin/end/change intensity (for example: hail, freezing precipitation, ice pellets, snow).
Ceiling and low-level obscuration
Ceiling forming/dissipating or crossing key thresholds (commonly including 3000 / 1500 / 1000 / 500 feet, plus a threshold tied to local approach minima).
A new cloud layer or obscuration appears below 1000 feet when none was previously reported below 1000 feet.
Rare but critical events
Volcanic eruption first noted.
Aircraft mishap (upon notification).
“Miscellaneous” situations deemed operationally critical.
Timing detail that matters
In U.S. practice, the time group on the SPECI is tied to when the criterion was met or noted, not merely when the message was transmitted.
Anatomy of a SPECI: how to read one quickly
The good news: a SPECI looks like a METAR, just with SPECI at the front.
Typical group flow:
Report type: SPECI
Station ID (ICAO code)
Time (UTC DDHHMMZ)
Wind
Visibility
RVR (if reported)
Present weather
Sky condition (or vertical visibility / obscured sky)
Temperature / dewpoint
Altimeter / QNH
Remarks (RMK)
Practical tips: using SPECIs like a pro
1) Treat SPECI as a “threshold crossing alert”
A SPECI often means “we crossed something that matters.” Use it as a trigger to re-check:
Approach minima (straight-in vs circling)
Alternate legality and fuel planning
Crosswind/tailwind limits
RVR requirements (if applicable)
ATIS changes and runway configuration
2) Always check the timestamp logic
SPECIs are time-sensitive. Learn how your region treats the observation time (criterion met vs transmission time), and don’t assume the report is “brand new” just because it just popped up in an app.
3) Know your region’s trigger list
Don’t memorize every number from every standard—memorize the concept: visibility, ceiling, thunderstorms, freezing precip, significant wind changes. Then keep a quick reference for your operating region if you need the exact threshold set.
4) Don’t over-trust a “one-off improvement”
If a field pops back above minimums, be cautious—some systems confirm improvements over a short period before publishing them as “real” improvements. A single good-minute between fog pulses shouldn’t drive a major go/no-go decision.
5) Use SPECI + TAF + radar/satellite as a system
A SPECI is a snapshot. Pair it with:
The TAF (what’s expected next),
Convective products if storms are involved,
PIREPs and situational awareness tools for what’s happening around the airport.
Bottom line
A SPECI is aviation’s “don’t wait for the next scheduled update” surface weather report: a METAR-style observation published because conditions crossed thresholds that matter to flight operations.
If you learn the trigger logic and get fast at scanning the key groups (time → wind → visibility/RVR → ceiling → weather), SPECIs become one of the most useful real-time inputs in both preflight planning and terminal decision-making.
Study Full Aviation Courses:
wifiCFI's full suite of aviation courses has everything you need to go from brand new to flight instructor and airline pilot! Check out any of the courses below for free:
Study Courses:
Checkride Lesson Plans:
Teaching Courses: