Narrative:

At about XA45 on jul/xa/95, I was turned inbound on the ILS runway 04 approach into rwi. As we intercepted the localizer inbound about 2 mi outside jambe intersection, ZDC called VFR traffic less than 500 ft above us and going the same direction. The right seat pilot saw the traffic first, then I also saw him. We watched him descend rapidly ahead of us, apparently on the localizer, and we saw him descend into the clouds below us. I confirmed that this was the traffic center had called on our TCASII. We switched to rocky mount radio and continued our approach. We reported 4.8 mi out inbound, then a baron called downwind for runway. We broke out at about 800 ft with lower scud over the airport and landed. The baron landed behind us. After landing I spoke to the pilot of the baron. When I told him that his descent into clouds VFR was illegal as well as unsafe, he became indignant and stated that he had done nothing wrong. I called center to discuss the event with them as they had requested, and I called winston-salem FSDO and spoke to FSDO representative about this. I have attached a copy of the statement I sent him. I have 2 major concerns about this event. 1ST, the pilot of the baron apparently does not know the regulations regarding flying in clouds and his attitude told me that he really doesn't care that he operates in a manner that is both unsafe and illegal. 2ND, I think that part of the reason this situation developed is that the personnel at rocky mount radio do not update their WX to match changing sits, but merely report the last hourly observation without checking to see if there has been any change. They were reporting 500 ft scattered, 15000 ft scattered, 25000 ft broken and 5 mi in fog when we made our approach. However, we descended into a fairly solid deck just below 2000 ft and broke out of the bottom at about 800 ft. The field was actually IFR, but they had not revised their observation to match the actual WX.

Related reports:

Google
 

Original NASA ASRS Text

Title: RPTR PERCEIVES ANOTHER ACFT DSNDED THROUGH CLOUDS IN CTL ZONE VFR.

Narrative: AT ABOUT XA45 ON JUL/XA/95, I WAS TURNED INBOUND ON THE ILS RWY 04 APCH INTO RWI. AS WE INTERCEPTED THE LOC INBOUND ABOUT 2 MI OUTSIDE JAMBE INTXN, ZDC CALLED VFR TFC LESS THAN 500 FT ABOVE US AND GOING THE SAME DIRECTION. THE R SEAT PLT SAW THE TFC FIRST, THEN I ALSO SAW HIM. WE WATCHED HIM DSND RAPIDLY AHEAD OF US, APPARENTLY ON THE LOC, AND WE SAW HIM DSND INTO THE CLOUDS BELOW US. I CONFIRMED THAT THIS WAS THE TFC CTR HAD CALLED ON OUR TCASII. WE SWITCHED TO ROCKY MOUNT RADIO AND CONTINUED OUR APCH. WE RPTED 4.8 MI OUT INBOUND, THEN A BARON CALLED DOWNWIND FOR RWY. WE BROKE OUT AT ABOUT 800 FT WITH LOWER SCUD OVER THE ARPT AND LANDED. THE BARON LANDED BEHIND US. AFTER LNDG I SPOKE TO THE PLT OF THE BARON. WHEN I TOLD HIM THAT HIS DSCNT INTO CLOUDS VFR WAS ILLEGAL AS WELL AS UNSAFE, HE BECAME INDIGNANT AND STATED THAT HE HAD DONE NOTHING WRONG. I CALLED CTR TO DISCUSS THE EVENT WITH THEM AS THEY HAD REQUESTED, AND I CALLED WINSTON-SALEM FSDO AND SPOKE TO FSDO REPRESENTATIVE ABOUT THIS. I HAVE ATTACHED A COPY OF THE STATEMENT I SENT HIM. I HAVE 2 MAJOR CONCERNS ABOUT THIS EVENT. 1ST, THE PLT OF THE BARON APPARENTLY DOES NOT KNOW THE REGS REGARDING FLYING IN CLOUDS AND HIS ATTITUDE TOLD ME THAT HE REALLY DOESN'T CARE THAT HE OPERATES IN A MANNER THAT IS BOTH UNSAFE AND ILLEGAL. 2ND, I THINK THAT PART OF THE REASON THIS SIT DEVELOPED IS THAT THE PERSONNEL AT ROCKY MOUNT RADIO DO NOT UPDATE THEIR WX TO MATCH CHANGING SITS, BUT MERELY RPT THE LAST HRLY OBSERVATION WITHOUT CHKING TO SEE IF THERE HAS BEEN ANY CHANGE. THEY WERE RPTING 500 FT SCATTERED, 15000 FT SCATTERED, 25000 FT BROKEN AND 5 MI IN FOG WHEN WE MADE OUR APCH. HOWEVER, WE DSNDED INTO A FAIRLY SOLID DECK JUST BELOW 2000 FT AND BROKE OUT OF THE BOTTOM AT ABOUT 800 FT. THE FIELD WAS ACTUALLY IFR, BUT THEY HAD NOT REVISED THEIR OBSERVATION TO MATCH THE ACTUAL WX.

Data retrieved from NASA's ASRS site as of July 2007 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.