Narrative:

I was working local control with radar coordinator combined to me. Aircraft X was cleared to land on runway 28L. Runway 28R was closed and amass was set appropriately showing runway 28R closed. I saw aircraft X lined up for runway 28L on short final over the lights and I then scanned some strips. Amass alerted; 'warning! Go around! Runway two eight right!' I immediately looked at the asde and saw the alert for runaway 28R as well as a target on runway 28L. I realized that the alert was probably a false alert. I immediately looked at runway 28L and saw aircraft X touching down on the runway near november. I scanned the runway and it appeared clear. There was nothing I could do anyway. The false alert really surprised me and it took quite awhile for me to recover. I was quite fatigued at the time. It was xc:13 in the morning and I had been up since xa:00. I was tired and had not had adequate rest for the entire workweek. I had worked xl:00-xt:00 on tuesday; xk:20-xs:20 on wednesday and xc:30-xk:30 on the previous day thursday. It is difficult to get adequate rest when working the rotating shifts that we work. In addition I was working two positions (local control and radar control) combined during a very complex operation. There was a lot of coordination with departure control as well as with ground control; clearances needed to be changed; strips needed to be marked; the city was conducting the runway inspections; and training was going on at ground control. With all that was going on I had less time to be aware of or anticipate the possibility of the false alert. As a result I was taken by surprise when the false alert happened.

Related reports:

Google
 

Original NASA ASRS Text

Title: SFO Controller described when landing traffic was not issued a mandatory go-around instruction following a false AMASS alert indicating any action on their part simply would not have been in time.

Narrative: I was working Local Control with Radar Coordinator combined to me. Aircraft X was cleared to land on Runway 28L. Runway 28R was closed and AMASS was set appropriately showing Runway 28R closed. I saw Aircraft X lined up for Runway 28L on short final over the lights and I then scanned some strips. AMASS alerted; 'WARNING! GO AROUND! RUNWAY TWO EIGHT RIGHT!' I immediately looked at the ASDE and saw the alert for Runaway 28R as well as a target on Runway 28L. I realized that the alert was probably a false alert. I immediately looked at Runway 28L and saw Aircraft X touching down on the runway near November. I scanned the runway and it appeared clear. There was nothing I could do anyway. The false alert really surprised me and it took quite awhile for me to recover. I was quite fatigued at the time. It was XC:13 in the morning and I had been up since XA:00. I was tired and had not had adequate rest for the entire workweek. I had worked XL:00-XT:00 on Tuesday; XK:20-XS:20 on Wednesday and XC:30-XK:30 on the previous day Thursday. It is difficult to get adequate rest when working the rotating shifts that we work. In addition I was working two positions (Local Control and Radar Control) combined during a very complex operation. There was a lot of coordination with Departure Control as well as with Ground Control; clearances needed to be changed; strips needed to be marked; the City was conducting the runway inspections; and training was going on at Ground Control. With all that was going on I had less time to be aware of or anticipate the possibility of the false alert. As a result I was taken by surprise when the false alert happened.

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