 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier first officer reported ATC issued a low altitude alert even though they were in compliance with the glidepath for their approach.
| Attributes | |
| ACN | 1755807 |
| Time | |
| Date | 202008 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ABQ.Airport |
| State Reference | NM |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter Unstabilized Approach |
Narrative:
We were cleared for the RNAV rnp Z 26 into abq from brkbd. During the approach; tower notified us of a 'low altitude alert' and asked if we were still on the approach. I was the pilot flying and verified we were on the approach. I verified we were still on the VNAV path; I crosschecked our next waypoint in the FMC to verify we were still listed as 'at or above' the specified altitude as well as the efb approach plate. I scanned our map display for terrain information and also visually acquired it. Everything looked good as far as altitude and terrain was concerned. I got distracted enough that the pilot monitoring started to recommend flaps and gear as I got behind the aircraft and was slow to slow down. It wasn't until reviewing the post flight report did I realize the flaps were set below 1000 feet at approximately 800 feet; which was not a stabilized approach. My only question is; if I were on the approach and on the VNAV path; why did it trigger a low altitude alert from tower. The notification caused enough of a distraction for me to lose track of my airspeed and resulted into a potential and unrecognized unstabilized approach.
Original NASA ASRS Text
Title: Air Carrier First Officer reported ATC issued a low altitude alert even though they were in compliance with the glidepath for their approach.
Narrative: We were cleared for the RNAV RNP Z 26 into ABQ from BRKBD. During the approach; Tower notified us of a 'Low Altitude Alert' and asked if we were still on the approach. I was the Pilot Flying and verified we were on the approach. I verified we were still on the VNAV PATH; I crosschecked our next waypoint in the FMC to verify we were still listed as 'At or Above' the specified altitude as well as the EFB Approach Plate. I scanned our Map Display for Terrain information and also visually acquired it. Everything looked good as far as altitude and terrain was concerned. I got distracted enough that the Pilot Monitoring started to recommend flaps and gear as I got behind the aircraft and was slow to slow down. It wasn't until reviewing the post flight report did I realize the flaps were set below 1000 feet at approximately 800 feet; which was not a stabilized approach. My only question is; if I were on the Approach and on the VNAV PATH; why did it trigger a Low Altitude Alert from Tower. The notification caused enough of a distraction for me to lose track of my airspeed and resulted into a potential and unrecognized unstabilized approach.
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.