37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1107021 |
Time | |
Date | 201308 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | GTF.Airport |
State Reference | MT |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
I suggested we fly the RNAV Z (rnp) to runway 21 at gtf since it was now clear skies and the approach sets up just like a base leg visual approach for runway 21. It also allows for practicing RNAV procedures. The first officer briefed the approached and we verified the FMS. The only changes we made to the FMS were putting a slower speed at the FAF kudey of 125 KIAS and a hard altitude of 4;700. We asked for direct yogos from ZLC center and were cleared the approach from yogos at or above 6;100 from gtf approach. After passing yogos the first officer performed his lav procedures and set 3;700 in the altitude window and speed intervened to 170; I believe. We obtained VNAV path between yogos and zilep. We were in VNAV path for the remainder of the approach. I was clearing outside the majority of the approach and pointing out visual references since the first officer had never been to gtf. As we approached kudey; I pointed out the tall towers on final that are near the turn to final. However; as we began to get closer it appeared to me that we were descending too low toward the towers. I checked inside and we were still VNAV path. I told the first officer we needed to climb. Shortly thereafter we received a GPWS call for 'obstacle.' the first officer disconnected the autopilot and initiated a level off or slight climb. We continued to get an 'obstacle' call out. At that time I said we need to climb more. The first officer initiated a more aggressive climb at this time. In the process we got one GPWS warning for an obstacle. Since we were VMC; daylight and visually could see the towers we did not perform an escape maneuver. After we got past the towers; we were reestablished on the approach and still in VNAV path. However; I could see the PAPI's for the runway and they were showing 4 reds. I called this out and said we are showing low. Meanwhile the first officer continued calling for configuration of the aircraft. By 800 AGL we were stable and on good PAPI indications and continued the approach to landing.during the debrief we could not figure out why we were on VNAV path and would receive GPWS call outs on the approach. We can not think of anything that we did that was incorrect. As far as we can tell; we performed RNAV procedures correctly. The only thing we changed in the FMS was the speed at kudey (the FAF). I believe we put the correct altitude to correspond with kudey. An aircraft system of some type may have caused this; however; I did not make an entry in the logbook. Not sure how I would have written it up and what maintenance could check. I checked the RNAV Y approach for runway 21. It has a crossing altitude of 5;300 ft over the towers. The RNAV Z is 4;700. The towers are listed at 4;117. I do not know when a GPWS call will be made for an obstacle but that is less than 600 ft clearance on the approach for the Z. I have flown the Z approach in VMC several times. Not sure if it is the exact approach or if it has changed recently. It does seem like a low clearance altitude over the towers on the Z approach. Good thing we can fly these approaches in VMC conditions only. That would not have been fun in night IMC.
Original NASA ASRS Text
Title: Air carrier flight crew in day VMC experiences A EGPWS terrain warning during the RNAV Z to Runway 21 at GTF with autopilot and autothrottles connected. The towers which caused the warning are visually avoided and when the PAPI is sighted; it also indicates low. A normal landing ensues.
Narrative: I suggested we fly the RNAV Z (RNP) to Runway 21 at GTF since it was now clear skies and the approach sets up just like a base leg visual approach for Runway 21. It also allows for practicing RNAV procedures. The First Officer briefed the approached and we verified the FMS. The only changes we made to the FMS were putting a slower speed at the FAF KUDEY of 125 KIAS and a hard altitude of 4;700. We asked for direct YOGOS from ZLC Center and were cleared the approach from YOGOS at or above 6;100 from GTF Approach. After passing YOGOS the First Officer performed his LAV procedures and set 3;700 in the altitude window and speed intervened to 170; I believe. We obtained VNAV Path between YOGOS and ZILEP. We were in VNAV Path for the remainder of the approach. I was clearing outside the majority of the approach and pointing out visual references since the First Officer had never been to GTF. As we approached KUDEY; I pointed out the tall towers on final that are near the turn to final. However; as we began to get closer it appeared to me that we were descending too low toward the towers. I checked inside and we were still VNAV Path. I told the First Officer we needed to climb. Shortly thereafter we received a GPWS call for 'Obstacle.' The First Officer disconnected the autopilot and initiated a level off or slight climb. We continued to get an 'Obstacle' call out. At that time I said we need to climb more. The First Officer initiated a more aggressive climb at this time. In the process we got one GPWS warning for an obstacle. Since we were VMC; daylight and visually could see the towers we did not perform an escape maneuver. After we got past the towers; we were reestablished on the approach and still in VNAV Path. However; I could see the PAPI's for the runway and they were showing 4 reds. I called this out and said we are showing low. Meanwhile the First Officer continued calling for configuration of the aircraft. By 800 AGL we were stable and on good PAPI indications and continued the approach to landing.During the debrief we could not figure out why we were on VNAV Path and would receive GPWS call outs on the approach. We can not think of anything that we did that was incorrect. As far as we can tell; we performed RNAV procedures correctly. The only thing we changed in the FMS was the speed at KUDEY (the FAF). I believe we put the correct altitude to correspond with KUDEY. An aircraft system of some type may have caused this; however; I did not make an entry in the logbook. Not sure how I would have written it up and what maintenance could check. I checked the RNAV Y approach for Runway 21. It has a crossing altitude of 5;300 FT over the towers. The RNAV Z is 4;700. The towers are listed at 4;117. I do not know when a GPWS call will be made for an obstacle but that is less than 600 FT clearance on the approach for the Z. I have flown the Z approach in VMC several times. Not sure if it is the exact approach or if it has changed recently. It does seem like a low clearance altitude over the towers on the Z approach. Good thing we can fly these approaches in VMC conditions only. That would not have been fun in night IMC.
Data retrieved from NASA's ASRS site as of July 2013 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.