B757 landing lga is issued go around during flare, flight crew fails to hear and react to go around ...

Attributes
ACN	617992
Time
Date	200405
Day	Tue
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : lga.airport
State Reference	NY
Altitude	agl bound lower : 0 agl bound upper : 30
Environment
Weather Elements	Rain
Light	Daylight
Aircraft 1
Controlling Facilities	tower : lga.tower
Operator	common carrier : air carrier
Make Model Name	B757-200
Operating Under FAR Part	Part 121
Flight Phase	descent : approach landing : roll landing other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	617992
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	incursion : runway incursion : landing without clearance non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	flight crew : landed as precaution none taken : insufficient time
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance Navigational Facility Weather
Primary Problem	Navigational Facility

Narrative:

Right about flare we heard a 'go around' command issued by tower but, did not hear the flight number. We assumed it was the aircraft behind us because we were just about to touch down. After touchdown, the tower advised us that they were sorry for the confusion. It was a glitch on their end. I called the tower to get details and discovered that the 'amass' system (not familiar with the acronym) had issued a conflict. However, the manager on duty said that this was an anomaly in the system because a rain shower that was passing the airport had set it off in error. Apparently, the controller is mandated to issue the go around command in this case. I discussed with the controller that neither the first officer nor I heard the flight number associated with the command and that we were 'locked' into the landing at that point. I suggested that if the command is issued again in the future that it should be very authoritative and clearly audible so that the crew can react without confusion.

Original NASA ASRS Text

Title: B757 LNDG LGA IS ISSUED GAR DURING FLARE, FLT CREW FAILS TO HEAR AND REACT TO GAR INSTRUCTIONS.

Narrative: RIGHT ABOUT FLARE WE HEARD A 'GAR' COMMAND ISSUED BY TWR BUT, DID NOT HEAR THE FLT NUMBER. WE ASSUMED IT WAS THE ACFT BEHIND US BECAUSE WE WERE JUST ABOUT TO TOUCH DOWN. AFTER TOUCHDOWN, THE TWR ADVISED US THAT THEY WERE SORRY FOR THE CONFUSION. IT WAS A GLITCH ON THEIR END. I CALLED THE TWR TO GET DETAILS AND DISCOVERED THAT THE 'AMASS' SYS (NOT FAMILIAR WITH THE ACRONYM) HAD ISSUED A CONFLICT. HOWEVER, THE MGR ON DUTY SAID THAT THIS WAS AN ANOMALY IN THE SYS BECAUSE A RAIN SHOWER THAT WAS PASSING THE ARPT HAD SET IT OFF IN ERROR. APPARENTLY, THE CTLR IS MANDATED TO ISSUE THE GAR COMMAND IN THIS CASE. I DISCUSSED WITH THE CTLR THAT NEITHER THE FO NOR I HEARD THE FLT NUMBER ASSOCIATED WITH THE COMMAND AND THAT WE WERE 'LOCKED' INTO THE LNDG AT THAT POINT. I SUGGESTED THAT IF THE COMMAND IS ISSUED AGAIN IN THE FUTURE THAT IT SHOULD BE VERY AUTHORITATIVE AND CLRLY AUDIBLE SO THAT THE CREW CAN REACT WITHOUT CONFUSION.

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

B757 landing lga is issued go around during flare, flight crew fails to hear and react to go around instructions.