B737 Undifferentiated or Other Model
Flight Crew Air Transport Pilot (ATP)
Confusion; Distraction; Situational Awareness
ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach
Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
ATC Equipment / Nav Facility / Buildings; Procedure
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.
Air Carrier First Officer reported ATC issued a low altitude alert even though they were in compliance with the glidepath for their approach.