Windshear alert activated while a B737-700 was on a visual approach at 400 ft. The crew ignored the ...

Narrative:

On final approach we got a windshear alert and did not initiate a go-around. I was the pilot flying. The weather was VFR; it was a visual approach; and the ride was smooth. The alert was surprising because there was no indication that any windshear was in the area at the time. The ride was smooth and uneventful. Our decision was also based on the aircraft doing strange things prior to this event. On the previous departure; when the autothrottles were engaged for takeoff they did not advance until I set the proper N1s. Twice the aircraft leveled off 250 ft above the altitude requested in the MCP window in VNAV. Later the autothrottles did respond on toga for departure and the flight director bars did not display on the pfd. This aircraft had done strange things so when we got the windshear alert there was absolutely nothing that we felt would give the aircraft that indication. The previous issues made us feel it was a glitch. If the weather would have been suspect; LLWS advisories; or even windshear forwarded by the tower or other aircraft; this would have been different. Since it was severe clear and smooth as glass; with no visual clues of any windshear whatsoever being in the area; we did not initiate the go-around.

Original NASA ASRS Text

Title: Windshear alert activated while a B737-700 was on a visual approach at 400 FT. The crew ignored the alert and landed because there were no low level windshear warnings and the weather was clear and smooth. The aircraft had previous unrelated automation problems.

Narrative: On final approach we got a windshear alert and did not initiate a go-around. I was the pilot flying. The weather was VFR; it was a visual approach; and the ride was smooth. The alert was surprising because there was no indication that any windshear was in the area at the time. The ride was smooth and uneventful. Our decision was also based on the aircraft doing strange things prior to this event. On the previous departure; when the autothrottles were engaged for takeoff they did not advance until I set the proper N1s. Twice the aircraft leveled off 250 FT above the altitude requested in the MCP window in VNAV. Later the autothrottles did respond on TOGA for departure and the flight director bars did not display on the PFD. This aircraft had done strange things so when we got the windshear alert there was absolutely nothing that we felt would give the aircraft that indication. The previous issues made us feel it was a glitch. If the weather would have been suspect; LLWS advisories; or even windshear forwarded by the Tower or other aircraft; this would have been different. Since it was severe clear and smooth as glass; with no visual clues of any windshear whatsoever being in the area; we did not initiate the go-around.

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.

Attributes
ACN	917759
Time
Date	201010
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Component
Aircraft Component	GPWS
Person 1
Function	First Officer Pilot Flying
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy

Windshear alert activated while a B737-700 was on a visual approach at 400 ft. The crew ignored the alert and landed because there were no low level windshear warnings and the weather was clear and smooth. The aircraft had previous unrelated automation problems.