 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737 ng flight crew reported a false egpws predictive windshear warning on short final to bos runway 27.
| Attributes | |
| ACN | 983816 |
| Time | |
| Date | 201112 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | BOS.Airport |
| State Reference | MA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737 Next Generation Undifferentiated |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | GPWS |
| Person 1 | |
| Function | Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 153 Flight Crew Type 12500 |
| Person 2 | |
| Function | First Officer |
| Experience | Flight Crew Last 90 Days 123 |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical |
Narrative:
On the descent into bos; the first officer mentioned the fact that on a previous flight landing runway 27 in bos he had experienced a predictive windshear alert (go around; windshear ahead). This occurred with a corresponding uncommanded system test of the windshear alerting system. He said that they went ahead and landed because they determined there was a malfunction of some kind; which caused the system to begin a test. They were called by a company representative who asked why they didn't go around and they explained the malfunction. The company representative was satisfied they had done the correct thing. Well; fast forward to yesterday. The same thing happened to us with the system going into the test mode and giving us the aural; 'go around; windshear ahead' alert. I don't know what is causing this; but we need to find out for two reasons. First; we need to preclude possible unnecessary missed approaches. Second; we need to prevent negative learning in that we are supposed to go around when we get a warning. Find out what is causing this and either fix the problem or at least alert crew to the possibility of the system going into the test mode and giving an invalid warning.
Original NASA ASRS Text
Title: A B737 NG flight crew reported a false EGPWS predictive windshear warning on short final to BOS Runway 27.
Narrative: On the descent into BOS; the First Officer mentioned the fact that on a previous flight landing Runway 27 in BOS he had experienced a predictive windshear alert (Go Around; Windshear Ahead). This occurred with a corresponding uncommanded system test of the windshear alerting system. He said that they went ahead and landed because they determined there was a malfunction of some kind; which caused the system to begin a test. They were called by a Company representative who asked why they didn't go around and they explained the malfunction. The Company representative was satisfied they had done the correct thing. Well; fast forward to yesterday. The same thing happened to us with the system going into the test mode and giving us the aural; 'Go Around; Windshear Ahead' alert. I don't know what is causing this; but we need to find out for two reasons. First; we need to preclude possible unnecessary missed approaches. Second; we need to prevent negative learning in that we are supposed to go around when we get a warning. Find out what is causing this and either fix the problem or at least alert crew to the possibility of the system going into the test mode and giving an invalid warning.
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.