37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 201005 |
Time | |
Date | 199202 |
Day | Sun |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : slc |
State Reference | UT |
Altitude | msl bound lower : 8000 msl bound upper : 8400 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : slc |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Navigation In Use | Other Other |
Flight Phase | cruise other |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : commercial pilot : flight engineer pilot : atp |
Experience | flight time last 90 days : 125 flight time total : 16500 flight time type : 4000 |
ASRS Report | 201005 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 135 flight time total : 11800 flight time type : 4000 |
ASRS Report | 201004 |
Events | |
Anomaly | altitude deviation : excursion from assigned altitude conflict : ground less severe non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | aircraft equipment other aircraft equipment : unspecified |
Resolutory Action | controller : issued new clearance flight crew : exited adverse environment flight crew : took evasive action |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | vertical : 1300 |
Supplementary | |
Air Traffic Incident | Pilot Deviation other |
Situations | |
ATC Facility | procedure or policy : unspecified |
Narrative:
While we were tracking in on the slc 34L localizer, the slc RVR went below our CAT IIIA landing mins. We were instructed to climb to 8000 ft, and turn to a heading of 180. After we were level at 8000 ft, and on the 180 heading for some time, we received a continuous terrain warning from the GPWS. This was over a completely dark area, as opposed to areas to the east and north of us where we could see the glow of lights through the fog. I initiated a climb and the first officer advised approach control that we were climbing because of terrain proximity warning, and that we needed a higher altitude immediately. The approach controller stated that he was providing terrain clearance for us and for us to maintain 8000 ft. (The approach controller was also very busy with several other aircraft in the area). He gave us a turn back to the northeast to intercept the localizer. I turned to the designated heading and descended back to 8000 ft from the vicinity of the 8400 ft that I had climbed to. The first officer sated that he had seen the radar altimeter indicating between 1300-1400 ft AGL, and that it was decreasing. We were in the area just to the east of the oquirah mountains with no obstruction lights in sight and with a known spur of high terrain extending out to the east. Perhaps a higher vector altitude would be appropriate in this area. At this point I want to emphasize that the GPWS warning was so loud as to be overpwring. This made it very difficult for us to communicate both inside and outside the cockpit. We had to shout to each other and had great difficulty understanding the controller's traffic at 9000 ft. I could not understand if he was talking about traffic directly above us, or the traffic that I could see in the distance ahead of us. The first officer did not catch the traffic call at all because of the high volume of the terrain warning. I have always thought that the GPWS warnings were too loud. Overpwring, and tenacious, and this instance has certainly reinforced that feeling. Supplemental information from acn 201004: the controller insisted that we maintain 8000, but did give us a turn toward the center of the valley. We turned, but ignored the altitude instruction and continued the climb enough to silence the GPWS warning. A controller's ex post facto statement that he is providing obstacle clearance is small comfort when 'whoop, whoop, pull up' is ringing in one's ear. A crew without GPWS, unfamiliar with the country, given no lost communication instruction and 'overlooked' for a few mi might have plowed in the mountain. Remember freighter at slc some yrs ago?
Original NASA ASRS Text
Title: GPWS WARNING ALERT WHILE ON RADAR VECTORS OVER DESIGNATED MOUNTAINOUS TERRAIN CAUSES ACR FLC TO EXECUTE A CLB CREATING AN ALTDEV ALT EXCURSION. RPT CITES GPWS AURAL INTERFERENCE AS DAMAGING TO INTER CREW COM AND ATC COM.
Narrative: WHILE WE WERE TRACKING IN ON THE SLC 34L LOC, THE SLC RVR WENT BELOW OUR CAT IIIA LNDG MINS. WE WERE INSTRUCTED TO CLB TO 8000 FT, AND TURN TO A HDG OF 180. AFTER WE WERE LEVEL AT 8000 FT, AND ON THE 180 HDG FOR SOME TIME, WE RECEIVED A CONTINUOUS TERRAIN WARNING FROM THE GPWS. THIS WAS OVER A COMPLETELY DARK AREA, AS OPPOSED TO AREAS TO THE E AND N OF US WHERE WE COULD SEE THE GLOW OF LIGHTS THROUGH THE FOG. I INITIATED A CLB AND THE FO ADVISED APCH CTL THAT WE WERE CLBING BECAUSE OF TERRAIN PROX WARNING, AND THAT WE NEEDED A HIGHER ALT IMMEDIATELY. THE APCH CTLR STATED THAT HE WAS PROVIDING TERRAIN CLRNC FOR US AND FOR US TO MAINTAIN 8000 FT. (THE APCH CTLR WAS ALSO VERY BUSY WITH SEVERAL OTHER ACFT IN THE AREA). HE GAVE US A TURN BACK TO THE NE TO INTERCEPT THE LOC. I TURNED TO THE DESIGNATED HDG AND DSNDED BACK TO 8000 FT FROM THE VICINITY OF THE 8400 FT THAT I HAD CLBED TO. THE FO SATED THAT HE HAD SEEN THE RADAR ALTIMETER INDICATING BTWN 1300-1400 FT AGL, AND THAT IT WAS DECREASING. WE WERE IN THE AREA JUST TO THE E OF THE OQUIRAH MOUNTAINS WITH NO OBSTRUCTION LIGHTS IN SIGHT AND WITH A KNOWN SPUR OF HIGH TERRAIN EXTENDING OUT TO THE E. PERHAPS A HIGHER VECTOR ALT WOULD BE APPROPRIATE IN THIS AREA. AT THIS POINT I WANT TO EMPHASIZE THAT THE GPWS WARNING WAS SO LOUD AS TO BE OVERPWRING. THIS MADE IT VERY DIFFICULT FOR US TO COMMUNICATE BOTH INSIDE AND OUTSIDE THE COCKPIT. WE HAD TO SHOUT TO EACH OTHER AND HAD GREAT DIFFICULTY UNDERSTANDING THE CTLR'S TFC AT 9000 FT. I COULD NOT UNDERSTAND IF HE WAS TALKING ABOUT TFC DIRECTLY ABOVE US, OR THE TFC THAT I COULD SEE IN THE DISTANCE AHEAD OF US. THE FO DID NOT CATCH THE TFC CALL AT ALL BECAUSE OF THE HIGH VOLUME OF THE TERRAIN WARNING. I HAVE ALWAYS THOUGHT THAT THE GPWS WARNINGS WERE TOO LOUD. OVERPWRING, AND TENACIOUS, AND THIS INSTANCE HAS CERTAINLY REINFORCED THAT FEELING. SUPPLEMENTAL INFO FROM ACN 201004: THE CTLR INSISTED THAT WE MAINTAIN 8000, BUT DID GIVE US A TURN TOWARD THE CTR OF THE VALLEY. WE TURNED, BUT IGNORED THE ALT INSTRUCTION AND CONTINUED THE CLB ENOUGH TO SILENCE THE GPWS WARNING. A CTLR'S EX POST FACTO STATEMENT THAT HE IS PROVIDING OBSTACLE CLRNC IS SMALL COMFORT WHEN 'WHOOP, WHOOP, PULL UP' IS RINGING IN ONE'S EAR. A CREW WITHOUT GPWS, UNFAMILIAR WITH THE COUNTRY, GIVEN NO LOST COM INSTRUCTION AND 'OVERLOOKED' FOR A FEW MI MIGHT HAVE PLOWED IN THE MOUNTAIN. REMEMBER FREIGHTER AT SLC SOME YRS AGO?
Data retrieved from NASA's ASRS site as of July 2007 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.