Narrative:

Preparing for a night IFR flight from north carolina to virginia; my weather briefing indicated clear skies north of the nc/va border and no airmets for icing. Approaching my destination and getting ready for the descent; I found myself above an un-forecasted overcast layer. The clouds are no problem since I was flying IFR; but the OAT was reading 0* C so there is the concern for icing if I descended. I checked the local AWOS stations around me; and they were all reporting clear skies; which was not true. The sirius xm/WX satellite image confirmed what I was seeing: complete overcast skies below. This differed from the weather briefing and AWOS stations below. Because I was out of range; I asked ATC to check the weather at my destination. He gave me information near my destination but couldn't give me the destination's weather. I told the controller that the weather stations around me were all reporting clear skies (but it was clearly overcast); and I expressed my concerns for icing if I descended into the clouds. I also expressed my concern for the false ceiling information provided by the AWOS stations and if I was stuck on top; I would have to do a 180 degree turn back towards richmond to get under the clouds and then do another 180 degree turn to get back to the north. The controller was very helpful and said he would give me anything I needed. The AWOS at my destination was once again; clear skies and 10SM visibility. When I checked in with the next controller; I told him I found a hole to descend and he told me to expect the visual approach. Even though I was near the airport; I was still in and out of IMC (above freezing temp; no icing) and could not see the airport so I had to do the ILS approach. About 5 miles out I cancelled IFR after just getting the airport in sight. On short final I noticed the smell of smoke and the runway lights were hard to see. After I landed; I made a PIREP that the airport was about 4SM visibility and it was hard to see the airport because of smoke. I checked the AWOS again and it once again said clear and 10SM visibility. This was clearly not the case. The reason I am writing this report is because this is the 3rd time I have experienced inaccurate ceiling and visibility data reported by AWOS stations this year; all of which were at night and in the state of virginia. Because I have had previous experiences with false weather data that caught me off guard; my judgments and decisions were based on taking a proactive approach to prevent a potential situation from occurring by talking with ATC and letting him know of the situation. Safety is my number one priority; and when un-forecasted weather occurs; I want to make sure I do everything I can to ensure the result of the flight is safe and successful. I was told that I made a big deal out of it by talking to ATC about it; but I believe you have to expect the unexpected when you realize the weather being reported is completely wrong and you have no idea what the weather is going to be like ahead. I think what really caused the problem was my inability to descend and getting trapped above an un-forecasted overcast layer; and my frustration that the weather stations continued reporting clear and 10SM visibility when it clearly wasn't. Corrective action: fly at a lower altitude; but you wouldn't know if the weather stations were all saying clear and 10SM vis. This is the 3rd time I've recognized this problem with inaccurate weather stations and I can't be the only pilot that has recognized this issue.

Google
 

Original NASA ASRS Text

Title: A General Aviation pilot describes a night IFR flight with a forecast for clear skies at his destination. Approaching his destination he finds himself above an undercast layer with an OAT of 0 degrees Celsius. AWOS is still reporting clear skies and 10 SM visibility. Eventually a hole is found but an ILS approach is required due to smoke reducing visibility at the destination airport.

Narrative: Preparing for a night IFR flight from North Carolina to Virginia; my weather briefing indicated clear skies north of the NC/VA border and no AIRMETs for icing. Approaching my destination and getting ready for the descent; I found myself above an un-forecasted overcast layer. The clouds are no problem since I was flying IFR; but the OAT was reading 0* C so there is the concern for icing if I descended. I checked the local AWOS stations around me; and they were all reporting Clear skies; which was not true. The Sirius XM/WX satellite image confirmed what I was seeing: complete overcast skies below. This differed from the weather briefing AND AWOS stations below. Because I was out of range; I asked ATC to check the weather at my destination. He gave me information near my destination but couldn't give me the destination's weather. I told the controller that the weather stations around me were all reporting clear skies (but it was clearly overcast); and I expressed my concerns for icing if I descended into the clouds. I also expressed my concern for the false ceiling information provided by the AWOS stations and if I was stuck on top; I would have to do a 180 degree turn back towards Richmond to get under the clouds and then do another 180 degree turn to get back to the north. The controller was very helpful and said he would give me anything I needed. The AWOS at my destination was once again; Clear skies and 10SM visibility. When I checked in with the next controller; I told him I found a hole to descend and he told me to expect the visual approach. Even though I was near the airport; I was still in and out of IMC (above freezing temp; no icing) and could not see the airport so I had to do the ILS approach. About 5 miles out I cancelled IFR after just getting the airport in sight. On short final I noticed the smell of smoke and the runway lights were hard to see. After I landed; I made a PIREP that the airport was about 4SM visibility and it was hard to see the airport because of smoke. I checked the AWOS again and it once again said CLR and 10SM visibility. This was clearly not the case. The reason I am writing this report is because this is the 3rd time I have experienced inaccurate ceiling and visibility data reported by AWOS stations this year; all of which were at night and in the state of Virginia. Because I have had previous experiences with false weather data that caught me off guard; my judgments and decisions were based on taking a proactive approach to prevent a potential situation from occurring by talking with ATC and letting him know of the situation. Safety is my number one priority; and when un-forecasted weather occurs; I want to make sure I do everything I can to ensure the result of the flight is safe and successful. I was told that I made a big deal out of it by talking to ATC about it; but I believe you have to expect the unexpected when you realize the weather being reported is completely wrong and you have no idea what the weather is going to be like ahead. I think what really caused the problem was my inability to descend and getting trapped above an un-forecasted overcast layer; and my frustration that the weather stations continued reporting Clear and 10SM visibility when it clearly wasn't. Corrective Action: Fly at a lower altitude; but you wouldn't know if the weather stations were all saying CLR and 10SM vis. This is the 3rd time I've recognized this problem with inaccurate weather stations and I can't be the only pilot that has recognized this issue.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.