37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1419020 |
Time | |
Date | 201701 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | RNO.Airport |
State Reference | NV |
Environment | |
Flight Conditions | Mixed |
Light | Dusk |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Other RNAV RNP Y 16R |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 197 |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Inflight Event / Encounter CFTT / CFIT |
Narrative:
This flight was flown into rno during a period of variable weather and visibilities with intermittent snow and rain in the area. The arrival time was near dusk. I was the pilot flying and we briefed and flew the RNAV rnp Y 16R. The approach was flown in accordance with our standard procedures with .3 set on the rnp on the legs page and the anp showing a .01 accuracy. I believe the temperature was above freezing. The approach was backed up with the rno ILS to 16R with 110.9 set in both navigation radios. While on the approach approximately one mile prior to mastr; and in contact with rno tower; the tower issued a low altitude alert to us. No egpws cautions or warnings occurred. We checked both egpws indications and raw radio altimeter indications and all were normal and green. We were monitoring aircraft status on the approach; the approach mode was in LNAV and VNAV path and our path indicators were centered for vertical and lateral deviations. The autopilot and autothrottles were engaged in cmd mode. Nothing on the approached looked abnormal and the ghost glide path indications from the 16R ILS were centered with the VNAV path indications.as the aircraft rolled out on final near okite all localizer indications were centered as well. Basically everything worked fine with the aircraft and we landed uneventfully. Upon our taxi back we queried the tower concerning the low altitude alert while on the approach. They said that if the aircraft is near one of the mountains while on the approach that their equipment will signal the warning. I think that if this is part of the normal procedure while flying the RNAV rnp approaches that there should be a note either on the approach plate or within the company 10-7 pages to prevent confusion.this is a high threat airport when it comes to terrain. The RNAV rnp approaches reduce the risks extensively. If our procedures are going to cause an ATC low altitude warning; then we need to know that either on the approach plate or on the company information page. I really should get no warning from ATC when the approach is flown properly.
Original NASA ASRS Text
Title: B737 Captain reported receiving a low altitude alert from ATC on approach to RNO even though the aircraft appeared to be on course and altitude.
Narrative: This flight was flown into RNO during a period of variable weather and visibilities with intermittent snow and rain in the area. The arrival time was near dusk. I was the Pilot Flying and we briefed and flew the RNAV RNP Y 16R. The approach was flown in accordance with our Standard Procedures with .3 set on the RNP on the LEGS page and the ANP showing a .01 accuracy. I believe the temperature was above freezing. The approach was backed up with the RNO ILS to 16R with 110.9 set in both NAV radios. While on the approach approximately one mile prior to MASTR; and in contact with RNO Tower; the Tower issued a Low Altitude Alert to us. No EGPWS Cautions or Warnings occurred. We checked both EGPWS indications and raw radio altimeter indications and all were normal and green. We were monitoring aircraft status on the approach; the approach mode was in LNAV and VNAV PATH and our path indicators were centered for vertical and lateral deviations. The autopilot and autothrottles were engaged in CMD mode. Nothing on the approached looked abnormal and the ghost glide path indications from the 16R ILS were centered with the VNAV PATH indications.As the aircraft rolled out on final near OKITE all Localizer indications were centered as well. Basically everything worked fine with the aircraft and we landed uneventfully. Upon our taxi back we queried the Tower concerning the low altitude alert while on the approach. They said that if the aircraft is near one of the mountains while on the approach that their equipment will signal the warning. I think that if this is part of the normal procedure while flying the RNAV RNP approaches that there should be a note either on the approach plate or within the Company 10-7 pages to prevent confusion.This is a high threat airport when it comes to terrain. The RNAV RNP approaches reduce the risks extensively. If our procedures are going to cause an ATC low altitude warning; then we need to know that either on the approach plate or on the Company information page. I really should get no warning from ATC when the approach is flown properly.
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.