Narrative:

Aircraft X called on the ground at ZZZ for IFR clearance to 20A. I cleared and released aircraft X to 20A with instructions to enter controlled air space heading and climb to 4000 MSL. He called me airborne and I radar identified him. He requested the RNAV 23 to 20A. I cleared him for the approach. Passing the IAF; I told him to report cancellation of IFR and to change to advisory frequency. He changed to advisory frequency. Approximately one mile from 20A; aircraft X reported IFR cancellation. I did check the NOTAMS page on the nids (national information display system) before assuming sr (radar position); but I unintentionally overlooked 20A because it is used very seldom.I did not check the nids to see the notams for 20A at the time of event due to the volume and complexity of active traffic. I was also in the process of splitting sectors with another controller to reduce the workload. The traffic became complex quickly and unexpectedly. It wasn't until I was relieved that I was told runway 5/23 at 20A was NOTAM closed this morning. The controller in charge called the local sheriff to check on the status of aircraft X. The sheriff reported he had to go around due to vehicles on the runway and circled to a safe landing after vehicles were clear.NOTAMS for runway closures and other significant outages are verbally disseminated to the controlling facilities at least 24 hours prior. This NOTAM was passed to bhm around xa:00 on the day of the NOTAM becoming active. The NOTAM began at xb:00.

Related reports:

Google
 

Original NASA ASRS Text

Title: BHM TRACON Controller reported he cleared an aircraft for an approach to Robins Field (20A).The Controller did not check the NOTAMs for the airport and the runway was closed.

Narrative: Aircraft X called on the ground at ZZZ for IFR clearance to 20A. I cleared and released Aircraft X to 20A with instructions to enter controlled air space heading and climb to 4000 MSL. He called me airborne and I radar identified him. He requested the RNAV 23 to 20A. I cleared him for the approach. Passing the IAF; I told him to report cancellation of IFR and to change to advisory frequency. He changed to advisory frequency. Approximately one mile from 20A; Aircraft X reported IFR cancellation. I did check the NOTAMS page on the NIDS (National Information Display System) before assuming SR (Radar position); but I unintentionally overlooked 20A because it is used very seldom.I did not check the NIDS to see the NOTAMs for 20A at the time of event due to the volume and complexity of active traffic. I was also in the process of splitting sectors with another controller to reduce the workload. The traffic became complex quickly and unexpectedly. It wasn't until I was relieved that I was told runway 5/23 at 20A was NOTAM closed this morning. The CIC called the local sheriff to check on the status of Aircraft X. The sheriff reported he had to go around due to vehicles on the runway and circled to a safe landing after vehicles were clear.NOTAMS for runway closures and other significant outages are verbally disseminated to the controlling facilities at least 24 hours prior. This NOTAM was passed to BHM around XA:00 on the day of the NOTAM becoming active. The NOTAM began at XB:00.

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.