Narrative:

We were lined up for a visual approach; fully configured and descending out of approximately 700 RA when we received an aural 'windshear!' and the windshear annunciator on the PNF's ADI. PNF called out 'windshear!' recovery! (I don't know why I added 'recovery' but I did.) within a split second; PF was executing the windshear recovery maneuver. I scanned back at my (PNF) instruments and noticed my airspeed indicator rolling back past reference and as it moved to -10 reference; I commanded 'pitch! Pitch! Pitch!' (just to emphasize to the PF that we needed to get out of this windshear.). Seconds after the command; I scanned my instruments and noticed my airspeed indicator was about 30 KTS slower than my standby asi and my first officer's asi. We were climbing out of about 1500 ft when I alerted the first officer of the asi discrepancies and we both decided that the windshear event was a false warning and thusly transitioned to a go around. We advised ATC and before returning to the airport needed to talk to maintenance and run some checklists. We advised maintenance we had 2 EICAS messages: 'rudder ratio' and 'mach trim fail;' and 1 status message 'elevator asymmetry.' maintenance tried to troubleshoot and had no luck getting the EICAS messages to go away. We noted the 15 KT crosswind restr due to the rudder ratio message and first officer discussed the possibility of another windshear warning and stall warning on final (which we did not receive during the previous windshear event). We elected to ignore the warning if other indications looked normal. We landed without incident and I briefed the flight attendants after the flight. Callback conversation with reporter revealed the following information: post flight inspection by maintenance revealed that a bird strike had occurred on the left side of the radome; jamming bird debris into the captain's pitot tube; rendering it inoperative.

Related reports:

Google
 

Original NASA ASRS Text

Title: B757 CAPT REPORTS WINDSHEAR WARNING AT 700 FT AGL ON APPROACH. DURING RECOVERY CAPT NOTES LARGE AIRSPEED DISCREPANCY BETWEEN CAPT AND FO AIRSPEED INDICATORS.

Narrative: WE WERE LINED UP FOR A VISUAL APCH; FULLY CONFIGURED AND DSNDING OUT OF APPROX 700 RA WHEN WE RECEIVED AN AURAL 'WINDSHEAR!' AND THE WINDSHEAR ANNUNCIATOR ON THE PNF'S ADI. PNF CALLED OUT 'WINDSHEAR!' RECOVERY! (I DON'T KNOW WHY I ADDED 'RECOVERY' BUT I DID.) WITHIN A SPLIT SECOND; PF WAS EXECUTING THE WINDSHEAR RECOVERY MANEUVER. I SCANNED BACK AT MY (PNF) INSTS AND NOTICED MY AIRSPD INDICATOR ROLLING BACK PAST REF AND AS IT MOVED TO -10 REF; I COMMANDED 'PITCH! PITCH! PITCH!' (JUST TO EMPHASIZE TO THE PF THAT WE NEEDED TO GET OUT OF THIS WINDSHEAR.). SECONDS AFTER THE COMMAND; I SCANNED MY INSTS AND NOTICED MY AIRSPD INDICATOR WAS ABOUT 30 KTS SLOWER THAN MY STANDBY ASI AND MY FO'S ASI. WE WERE CLBING OUT OF ABOUT 1500 FT WHEN I ALERTED THE FO OF THE ASI DISCREPANCIES AND WE BOTH DECIDED THAT THE WINDSHEAR EVENT WAS A FALSE WARNING AND THUSLY TRANSITIONED TO A GAR. WE ADVISED ATC AND BEFORE RETURNING TO THE ARPT NEEDED TO TALK TO MAINT AND RUN SOME CHKLISTS. WE ADVISED MAINT WE HAD 2 EICAS MESSAGES: 'RUDDER RATIO' AND 'MACH TRIM FAIL;' AND 1 STATUS MESSAGE 'ELEVATOR ASYMMETRY.' MAINT TRIED TO TROUBLESHOOT AND HAD NO LUCK GETTING THE EICAS MESSAGES TO GO AWAY. WE NOTED THE 15 KT XWIND RESTR DUE TO THE RUDDER RATIO MESSAGE AND FO DISCUSSED THE POSSIBILITY OF ANOTHER WINDSHEAR WARNING AND STALL WARNING ON FINAL (WHICH WE DID NOT RECEIVE DURING THE PREVIOUS WINDSHEAR EVENT). WE ELECTED TO IGNORE THE WARNING IF OTHER INDICATIONS LOOKED NORMAL. WE LANDED WITHOUT INCIDENT AND I BRIEFED THE FLT ATTENDANTS AFTER THE FLT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: POST FLIGHT INSPECTION BY MAINTENANCE REVEALED THAT A BIRD STRIKE HAD OCCURRED ON THE LEFT SIDE OF THE RADOME; JAMMING BIRD DEBRIS INTO THE CAPT'S PITOT TUBE; RENDERING IT INOPERATIVE.

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