An instructor pilot and his student landed on a closed runway at UUU when his preflight NOTAM check showed no runway closures.

Narrative

Before departing New Bedford (EWB) for Newport State (UUU); I checked the NOTAM publication on the FAA website. The most recent publication was issued on Feb/2009. There were no published NOTAMs for Newport State(UUU). I then departed EWB for UUU with my student. I climbed to 2000 ft (MSL). Once outside of New Bedford's class delta airspace; I immediately switched over to Newport State ASOS (132.075). The winds were favoring Runway 34. I then switched over to Newport State CTAF/Unicom (122.8). There I stated my position 10 miles to the north and asked for airport advisories. There was no reply. At five miles out I then stated my intentions to land on Runway 34 and to remain in left close traffic. After; I made a position report for the base and final leg for Runway 34. I touched down on Runway 34. I then proceeded to depart on Runway 34 for left close traffic. After liftoff; I stated that I was on upwind leg and intended to remain in left close traffic. Someone then came over the radio and told me that Runway 16/34 was closed. I told him that I checked the NOTAMs and that there had been no report of runway closures at UUU. He reported that Runway 16/34 was closed one more time. I then stated that we would depart the pattern to the north. After landing back at EWB; I called Flight Service and they told me that Runway 16/34 was closed at Newport State. In hind sight; I should have called to get an updated brief in addition to checking the published NOTAMs.