 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Upon receiving a 'monitor radar display' aural warning while initiating the flare for landing (during atmospheric conditions consistent with potential predictive windshear alerts) the captain of a B737-700 opted to complete the landing rather than initiate a go-around.
| Attributes | |
| ACN | 1200569 |
| Time | |
| Date | 201409 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ATL.Airport |
| State Reference | GA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Landing |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 247 Flight Crew Type 10000 |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Flight Deck / Cabin / Aircraft Event Other / Unknown Inflight Event / Encounter Weather / Turbulence |
Narrative:
Approaching to land in atlanta on runway 27; there was a thunderstorm north of the airport. Approximately 15 seconds prior to touchdown we received a 'monitor radar display' aural alert. The crew elected to continue the landing. The wind was a constant 20 knots through the final and landing sequence. The tower did not issue any windshear warnings and no aircraft in front or behind our aircraft executed a go-around. After aircraft shutdown at the gate; we reviewed the QRH; which confirmed our suspicion that we; indeed; should have gone around.a more thorough review of items in the QRH such as this could be accomplished. During the landing flare; I was ready to execute the go-around once I received the 'monitor radar display;' however; I was erroneously waiting for the 'windshear ahead; go-around' warning from the automated system. This type of alert can trap a lot of crews since we are often spring loaded to act only after receiving aural warnings and not aural 'cautions.' since this happened just before beginning the landing flare; there wasn't a lot of time for discussion during the event.
Original NASA ASRS Text
Title: Upon receiving a 'monitor radar display' aural warning while initiating the flare for landing (during atmospheric conditions consistent with potential predictive windshear alerts) the Captain of a B737-700 opted to complete the landing rather than initiate a go-around.
Narrative: Approaching to land in Atlanta on Runway 27; there was a thunderstorm north of the airport. Approximately 15 seconds prior to touchdown we received a 'monitor radar display' aural alert. The Crew elected to continue the landing. The wind was a constant 20 knots through the final and landing sequence. The Tower did not issue any windshear warnings and no aircraft in front or behind our aircraft executed a go-around. After aircraft shutdown at the gate; we reviewed the QRH; which confirmed our suspicion that we; indeed; should have gone around.A more thorough review of items in the QRH such as this could be accomplished. During the landing flare; I was ready to execute the go-around once I received the 'monitor radar display;' however; I was erroneously waiting for the 'windshear ahead; go-around' warning from the automated system. This type of alert can trap a lot of Crews since we are often spring loaded to act only after receiving aural warnings and not aural 'cautions.' Since this happened just before beginning the landing flare; there wasn't a lot of time for discussion during the event.
Data retrieved from NASA's ASRS site 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.