Narrative:

Aircraft X inbound tvk and requested an RNAV approach to runway 16 due to IMC conditions. Aircraft X advised they had the current weather. Another sector informed me that the notams were read to the pilot. I reviewed the notams for the airport prior to issuing approach clearance. The notams at the time were PAPI OTS; runway end lgts OTS and one obst large transport OTS. Aircraft X was cleared for RNAV approach and was instructed how to cancel IFR and frequency change was approved. Aircraft X cancelled IFR clearance in the air after breaking out of IMC. Shortly after; aircraft X queried if I was still able to hear them. I replied I could. Aircraft X asked if there was a NOTAM for a runway or airport closure. I replied 'negative'.there were no notams for airport or runway closure at the airport. Aircraft X reported a lighted yellow X on the runway approach end and saw construction personnel and equipment on the runway. Aircraft X executed a go-around and circled the airport. Aircraft X requested IFR clearance to a nearby alternate airport and landed safely. I reported the incident to the controller in charge (controller in charge). I assumed the airport to be closed until I was told otherwise. I made a note of this at the sector and passed the information on to my relief. The next day; the notams showed the first and last 500 ft of the runway were closed.the runway and/or airport closure NOTAM was not displayed on at the time the approach clearance was issued. Either the NOTAM was not issued or valid at the time the approach clearance was issued or through some glitch; the NOTAM was not properly displayed at the sector. The status of runway and airport notams is critical to safety and should always be accurate.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZAU Center Controller reported that an aircraft had to go-around after being issued an RNAV Approach due to equipment and personnel on the runway.

Narrative: Aircraft X inbound TVK and requested an RNAV Approach to Runway 16 due to IMC conditions. Aircraft X advised they had the current weather. Another sector informed me that the NOTAMs were read to the pilot. I reviewed the NOTAMs for the airport prior to issuing approach clearance. The NOTAMs at the time were PAPI OTS; RWY END LGTS OTS and one OBST LGT OTS. Aircraft X was cleared for RNAV approach and was instructed how to cancel IFR and frequency change was approved. Aircraft X cancelled IFR clearance in the air after breaking out of IMC. Shortly after; Aircraft X queried if I was still able to hear them. I replied I could. Aircraft X asked if there was a NOTAM for a runway or airport closure. I replied 'negative'.There were no NOTAMs for airport or runway closure at the airport. Aircraft X reported a lighted yellow X on the runway approach end and saw construction personnel and equipment on the runway. Aircraft X executed a go-around and circled the airport. Aircraft X requested IFR clearance to a nearby alternate airport and landed safely. I reported the incident to the CIC (Controller in Charge). I assumed the airport to be closed until I was told otherwise. I made a note of this at the sector and passed the information on to my relief. The next day; the NOTAMs showed the first and last 500 ft of the runway were closed.The runway and/or airport closure NOTAM was not displayed on at the time the approach clearance was issued. Either the NOTAM was not issued or valid at the time the approach clearance was issued or through some glitch; the NOTAM was not properly displayed at the sector. The status of runway and airport NOTAMs is critical to safety and should always be accurate.

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.