 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B757 flight crew reports getting low during the FMS bridge visual to runway 28R at sfo; after getting high due to ATC speed restrictions. In order to get back on profile the aircraft was configured early and descends below the normal approach path resulting in a low altitude alert from the tower. The approach is continued to a normal landing.
| Attributes | |
| ACN | 1178932 |
| Time | |
| Date | 201406 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | SFO.Tower |
| State Reference | CA |
| Aircraft 1 | |
| Make Model Name | B757-200 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
After cedes on the mod 5 arrival we were cleared via the FMS bridge visual 28R route; but not the altitude profile. Our descent was controlled by ATC and our airspeed was gradually slowed to as low as 160 KTS to sequence behind a B777 landing 28R. This left us high between garow and janny and the first officer elected to configure to landing configuration there to facilitate a vertical path correction. We ended up rolling out on final well below glideslope. Tower issued an altitude alert and an altimeter setting of 29.71. We had set 29.91 when descending below FL180 as understood and read back in response to ATC. The first officer asked about whether we should go-around and I told him to level off and intercept the glideslope. This was accomplished and a TDZ landing resulted. At the time my feeling was that we were correcting to the glide-slope from below on center line and on speed with cavu weather. In retrospect and debrief we both agreed that a go-around was called for in this situation. We both felt rushed throughout the approach and the proper response would have been to go-around and set up again.
Original NASA ASRS Text
Title: B757 flight crew reports getting low during the FMS Bridge Visual to Runway 28R at SFO; after getting high due to ATC speed restrictions. In order to get back on profile the aircraft was configured early and descends below the normal approach path resulting in a low altitude alert from the Tower. The approach is continued to a normal landing.
Narrative: After CEDES on the MOD 5 Arrival we were cleared via the FMS Bridge Visual 28R route; but not the altitude profile. Our descent was controlled by ATC and our airspeed was gradually slowed to as low as 160 KTS to sequence behind a B777 landing 28R. This left us high between GAROW and JANNY and the First Officer elected to configure to landing configuration there to facilitate a vertical path correction. We ended up rolling out on final well below glideslope. Tower issued an altitude alert and an altimeter setting of 29.71. We had set 29.91 when descending below FL180 as understood and read back in response to ATC. The First Officer asked about whether we should go-around and I told him to level off and intercept the glideslope. This was accomplished and a TDZ landing resulted. At the time my feeling was that we were correcting to the glide-slope from below on center line and on speed with CAVU weather. In retrospect and debrief we both agreed that a go-around was called for in this situation. We both felt rushed throughout the approach and the proper response would have been to go-around and set up again.
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.