IFR conditions on METARs
-
Hi all.
For those better versed in aviation weather than I am, aren't IFR minima supposed to be broken at or below 1000 AGL? In this picture:
the METAR is reported as IFR, when I'm pretty sure it's supposed to be VFR or MVFR at best.
Any opinions? Is labeling this METAR as IFR an error?
-
@f35blightningii
Take a look at those 2 METARS:KSFO 290356Z 29014KT 10SM FEW003 12/11 A2991
KSFO 290456Z 29013KT 10SM FEW003 SCT005 12/11 A2992
The 1st one is VFR as the low clouds are FEW (1-2 octas)
But the 2nd one is IFR as the total cloud cover of low clouds (FEW+SCT) is more than 4 octas
(assuming clouds at 300ft and 500ft are not overlapping)
-
-
@f35blightningii
Now I took a better look and ... I am confused !!!
windy says IFR, flightaware says VFR
https://flightaware.com/resources/airport/KSFO/weatherWe have to ask windy: the IFR sign is coming from NOAA (or any other source)
or is "computed" from windy's software by only "reading" the METAR ?
-
-
That's what I mean. The FlightIntel app on Android also listed my first post's conditions as VFR. As for the AIRMET, the fog and mist burn off in the middle of the day and only start creeping back into to the SFO area in the evening, but I'm pretty sure few and scattered don't count as IFR. Maybe MVFR instead.
-
Yes, this is incorrect. VFR is for vis >5sm and Cig > 3000
MVFR is vis 3>5sm and Cig 1000>3000
IFR is vis 1>3sm and Cig 500>1000
LIFR is vis
-
I admit that METAR -> conditions parser is not perfect
-
Whenever METAR parser fails it reports IFR or LIFR conditions
-
Looks like it's been fixed. Thanks guys!
