Narrative:

On visual approach 34L; on glideslope; with ATC verified altimeter setting of 30.06; ATC verified altitude of 8300'; we showed a difference of about 175'. We verified MALSR and PAPI lighting on visual approach and landed without incident. Aircraft altimeters checked pre and post flight within aom limits. We mentioned the difference to reno tower; and he indicated that it has happened before. In fact; I have heard tower say to other carriers; many times; that they were low on approach; when they were showing on glidepath with correct altimeter on runway 16. There seems to be a known issue regarding disparity between aircraft; ATC; and approach fix altitudes. If there is a known issue; then I humbly suggest it should be addressed.

Google
 

Original NASA ASRS Text

Title: B737 Captain reported aircraft showed altitude discrepancy from that displayed by ATC. Pilot reports this anomaly is common at that particular airport.

Narrative: On visual approach 34L; on glideslope; with ATC verified altimeter setting of 30.06; ATC verified altitude of 8300'; we showed a difference of about 175'. We verified MALSR and PAPI lighting on visual approach and landed without incident. Aircraft altimeters checked pre and post flight within AOM limits. We mentioned the difference to Reno Tower; and he indicated that it has happened before. In fact; I have heard Tower say to other carriers; many times; that they were low on approach; when they were showing on glidepath with correct altimeter on Runway 16. There seems to be a known issue regarding disparity between aircraft; ATC; and approach FIX altitudes. If there is a known issue; then I humbly suggest it should be addressed.

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.