 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737 crew continued an unstabilized visual approach to bwi after an ATC weather vector lined them with the runway closer than expected.
| Attributes | |
| ACN | 847772 |
| Time | |
| Date | 200908 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | BWI.Airport |
| State Reference | MD |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach Final Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Deviation - Speed All Types Inflight Event / Encounter Unstabilized Approach |
Narrative:
On approach and landing into baltimore; approach control was vectoring us around some weather. We were holding 250 KTS at 2000 ft and then slowed to 210 KTS as we were vectored in closer. The controller then turned us toward the final approach fix for the visual approach. We then put in flaps and started slowing more. The runway looked closer being visual so the autopilot was turned off and nose was lowered to descend to the runway. We put gear down and tried to slow more. We passed through 1000 ft not stabilized. We then received glideslope warning and corrected. We were still waiting for the speed to slow for flaps 30. With runway in sight we got terrain warning but continued since runway was in sight and no terrain was a factor. Flaps 30 and we landed. We were being vectored around weather near the airport. Approach control brought us in closer than expected and planning got behind with speed control. Corrected for the glideslope and visually having the runway insight with no terrain as a factor. Not being stable at 1000 ft and receiving glideslope warning then terrain warning; we should have executed a go-around even though the field was visual.
Original NASA ASRS Text
Title: A B737 crew continued an unstabilized visual approach to BWI after an ATC weather vector lined them with the runway closer than expected.
Narrative: On approach and landing into Baltimore; Approach Control was vectoring us around some weather. We were holding 250 KTS at 2000 FT and then slowed to 210 KTS as we were vectored in closer. The Controller then turned us toward the final approach fix for the visual approach. We then put in flaps and started slowing more. The runway looked closer being visual so the autopilot was turned off and nose was lowered to descend to the runway. We put gear down and tried to slow more. We passed through 1000 FT not stabilized. We then received glideslope warning and corrected. We were still waiting for the speed to slow for Flaps 30. With runway in sight we got terrain warning but continued since runway was in sight and no terrain was a factor. Flaps 30 and we landed. We were being vectored around weather near the airport. Approach Control brought us in closer than expected and planning got behind with speed control. Corrected for the glideslope and visually having the runway insight with no terrain as a factor. Not being stable at 1000 FT and receiving glideslope warning then terrain warning; we should have executed a go-around even though the field was visual.
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.