Narrative:

There have been many issues with runway closures and restrictions that have not been coordinated verbally or through the integrated display system (ids)-4. I mentioned this dozens of times to the traffic management specialists (tm) and front line manager's but there is always some bad excuse for the lack of this easy and critical information. Today it became a serious situation. Aircraft X was assigned runway 16R because runway 16L was closed. Abeam the airport the tm advised runway 16L was open and I offered aircraft X their choice of runways and they wanted runway 16L. Aircraft X went around and we found out it was due to the 'aircraft not being configured'. At this point both finals sectors were being relieved. The tower handed off the go-around to departure control and they assigned runway 16R. The tower ids-4 was advertising that we were landing runways' 16R; 16L and 17R and 16L was closed. Obviously; this is conflicting information. A few seconds later it changed to show no runway closures. Discussions in the break room later confirmed that the arrival sectors were not told about a runway 16R closure. When aircraft X was on a base leg 10 miles from the airport the tm came over to the the new finals controller and said 'you're not really going to put that guy on 16R are you'? The controller looked at the ids; saw no restrictions; and said 'uh; yeah' in a confused voice. During the most critical phase of flight; on their second approach; aircraft X was forced to change runways for the fourth time to avoid landing on a runway with equipment on it. It's very; very easy. Put runway closures in the 'runway closures' of the ids. Put runway restrictions in the 'runway restrictions' page of the ids. Secondly; I've mentioned this problem dozens of times to the flms but I'm 'blown off' every time.

Google
 

Original NASA ASRS Text

Title: A TRACON Controller was not notified of a runway closure. The Controller states that this is a routine occurrence.

Narrative: There have been many issues with runway closures and restrictions that have not been coordinated verbally or through the Integrated Display System (IDS)-4. I mentioned this dozens of times to the Traffic Management Specialists (TM) and Front Line Manager's but there is always some bad excuse for the lack of this easy and critical information. Today it became a serious situation. Aircraft X was assigned Runway 16R because Runway 16L was closed. Abeam the airport the TM advised Runway 16L was open and I offered Aircraft X their choice of runways and they wanted Runway 16L. Aircraft X went around and we found out it was due to the 'aircraft not being configured'. At this point both Finals Sectors were being relieved. The tower handed off the go-around to Departure Control and they assigned Runway 16R. The Tower IDS-4 was advertising that we were landing Runways' 16R; 16L and 17R AND 16L was closed. Obviously; this is conflicting information. A few seconds later it changed to show no runway closures. Discussions in the break room later confirmed that the Arrival Sectors were not told about a Runway 16R closure. When Aircraft X was on a base leg 10 miles from the airport the TM came over to the the new Finals Controller and said 'You're not really going to put that guy on 16R are you'? The controller looked at the IDS; saw no restrictions; and said 'uh; yeah' in a confused voice. During the most critical phase of flight; on their second approach; Aircraft X was forced to change runways for the fourth time to avoid landing on a runway with equipment on it. It's very; very easy. Put runway closures in the 'runway closures' of the IDS. Put runway restrictions in the 'runway restrictions' page of the IDS. Secondly; I've mentioned this problem dozens of times to the FLMs but I'm 'blown off' every time.

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.