37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 406511 |
Time | |
Date | 199806 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : tys |
State Reference | TN |
Altitude | msl bound lower : 2500 msl bound upper : 3600 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : tys |
Operator | common carrier : air carrier |
Make Model Name | B727-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | approach : visual arrival other enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : commercial pilot : instrument pilot : atp |
Experience | flight time last 90 days : 160 flight time total : 14100 flight time type : 1830 |
ASRS Report | 406511 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | non adherence : published procedure other anomaly other other spatial deviation |
Independent Detector | aircraft equipment other aircraft equipment : unspecified |
Resolutory Action | flight crew : exited adverse environment flight crew : took evasive action |
Consequence | Other |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | other |
Situations | |
ATC Facility | procedure or policy : unspecified |
Airport | other physical facility |
Narrative:
It was our 4TH flight segment of the day, including a divert for WX earlier. It was night (approximately AB15), scattered clouds with visibility reported at 6 mi with haze. We approached tys from the south on an IFR flight plan, in contact with approach control. We were told to expect vectors for a visual approach to runway 23R, and were vectored around the northeast side of the field, and given dscnts down to 2500 ft MSL. The copilot, flying the approach, had briefed a visual approach and had the ILS runway 23R tuned in for a backup. The other navigation radio was still on the vxv VOR for position orientation. We had been vectored around a left base at approximately 12-15 mi northeast of the airport, eventually given a 230 degree vector, told we were 12 mi from the airport and cleared the visual approach. ILS indications were below GS and left of localizer course, and we were in level flight at 2500 ft MSL. Somewhere in between about 7-11 mi northeast of the airport, the GPWS sounded 'whoop, whoop, pull up.' we could see the lights on the ground but the hazy night conditions with no discernible horizon made it impossible to positively insure there was no terrain or obstacle which might be a factor. We commenced a pull-up, and reached approximately 3600 ft MSL before the GPWS silenced. We reported our climb to approach control, and from that altitude acquired a better look at the airport and were able to continue to a normal landing. The ILS for runway 23R shows an MSA of 8800 ft. Although, I had been to tys many times before and knew there is terrain around the airport, I wasn't immediately sure we were clear of all terrain because of the marginal visual conditions. Fatigue may also have been a factor. We were fortunate in that we did not overboost any engines, if we had been totally IMC I suspect we would have. After the fact, approach said GPWS warnings like ours had happened before. A rider on our jump seat said he had seen it happen before, too. Since it appears our experience was not an isolated case, I suggest a review to either adjust the MVA, or publish the fact that a GPWS warning is possible although at a safe vectoring altitude. It might save unnecessary engine overboosts, possible traffic conflicts, and unnecessarily scaring passenger (and pilots!) callback conversation with facility specialist revealed the following information: facility specialist advised that a 30 day evaluation is being conducted with airport users to obtain information if there is frequent/infrequent GPWS resolutions encountered when conducting an approach to tys airport, runway 23. The survey was the result of inquiry initiated by an airport user. At this point in the survey, only one type of jet aircraft has experienced GPWS resolutions. Investigation of a recent user complaint determined all controller actions were in accordance with facility procedures and policies. Radar/DME are required to conduct the runway 23 approach. The MVA has been recently verified, as required by FAA review policy. Controller radar indicators display required obstructions. The MSA (8800 ft) should not be confused with MVA. MSA and MVA are developed by differing criteria.
Original NASA ASRS Text
Title: A B727 FLC EXERCISES AN EVASIVE CLB IN RESPONSE TO A GPWS ALERT WHILE MAKING A NIGHT VISUAL APCH TO TYS RWY 23. THE ACFT WAS DSNDED TO AN MVA OF 2500 FT WHEN THE ALERT OCCURRED. THE MSA IS 8800 FT AND THE INITIAL APCH ALT IS 3600 FT.
Narrative: IT WAS OUR 4TH FLT SEGMENT OF THE DAY, INCLUDING A DIVERT FOR WX EARLIER. IT WAS NIGHT (APPROX AB15), SCATTERED CLOUDS WITH VISIBILITY RPTED AT 6 MI WITH HAZE. WE APCHED TYS FROM THE S ON AN IFR FLT PLAN, IN CONTACT WITH APCH CTL. WE WERE TOLD TO EXPECT VECTORS FOR A VISUAL APCH TO RWY 23R, AND WERE VECTORED AROUND THE NE SIDE OF THE FIELD, AND GIVEN DSCNTS DOWN TO 2500 FT MSL. THE COPLT, FLYING THE APCH, HAD BRIEFED A VISUAL APCH AND HAD THE ILS RWY 23R TUNED IN FOR A BACKUP. THE OTHER NAV RADIO WAS STILL ON THE VXV VOR FOR POS ORIENTATION. WE HAD BEEN VECTORED AROUND A L BASE AT APPROX 12-15 MI NE OF THE ARPT, EVENTUALLY GIVEN A 230 DEG VECTOR, TOLD WE WERE 12 MI FROM THE ARPT AND CLRED THE VISUAL APCH. ILS INDICATIONS WERE BELOW GS AND LEFT OF LOC COURSE, AND WE WERE IN LEVEL FLT AT 2500 FT MSL. SOMEWHERE IN BTWN ABOUT 7-11 MI NE OF THE ARPT, THE GPWS SOUNDED 'WHOOP, WHOOP, PULL UP.' WE COULD SEE THE LIGHTS ON THE GND BUT THE HAZY NIGHT CONDITIONS WITH NO DISCERNIBLE HORIZON MADE IT IMPOSSIBLE TO POSITIVELY INSURE THERE WAS NO TERRAIN OR OBSTACLE WHICH MIGHT BE A FACTOR. WE COMMENCED A PULL-UP, AND REACHED APPROX 3600 FT MSL BEFORE THE GPWS SILENCED. WE RPTED OUR CLB TO APCH CTL, AND FROM THAT ALT ACQUIRED A BETTER LOOK AT THE ARPT AND WERE ABLE TO CONTINUE TO A NORMAL LNDG. THE ILS FOR RWY 23R SHOWS AN MSA OF 8800 FT. ALTHOUGH, I HAD BEEN TO TYS MANY TIMES BEFORE AND KNEW THERE IS TERRAIN AROUND THE ARPT, I WASN'T IMMEDIATELY SURE WE WERE CLR OF ALL TERRAIN BECAUSE OF THE MARGINAL VISUAL CONDITIONS. FATIGUE MAY ALSO HAVE BEEN A FACTOR. WE WERE FORTUNATE IN THAT WE DID NOT OVERBOOST ANY ENGS, IF WE HAD BEEN TOTALLY IMC I SUSPECT WE WOULD HAVE. AFTER THE FACT, APCH SAID GPWS WARNINGS LIKE OURS HAD HAPPENED BEFORE. A RIDER ON OUR JUMP SEAT SAID HE HAD SEEN IT HAPPEN BEFORE, TOO. SINCE IT APPEARS OUR EXPERIENCE WAS NOT AN ISOLATED CASE, I SUGGEST A REVIEW TO EITHER ADJUST THE MVA, OR PUBLISH THE FACT THAT A GPWS WARNING IS POSSIBLE ALTHOUGH AT A SAFE VECTORING ALT. IT MIGHT SAVE UNNECESSARY ENG OVERBOOSTS, POSSIBLE TFC CONFLICTS, AND UNNECESSARILY SCARING PAX (AND PLTS!) CALLBACK CONVERSATION WITH FACILITY SPECIALIST REVEALED THE FOLLOWING INFO: FACILITY SPECIALIST ADVISED THAT A 30 DAY EVALUATION IS BEING CONDUCTED WITH ARPT USERS TO OBTAIN INFO IF THERE IS FREQUENT/INFREQUENT GPWS RESOLUTIONS ENCOUNTERED WHEN CONDUCTING AN APCH TO TYS ARPT, RWY 23. THE SURVEY WAS THE RESULT OF INQUIRY INITIATED BY AN ARPT USER. AT THIS POINT IN THE SURVEY, ONLY ONE TYPE OF JET ACFT HAS EXPERIENCED GPWS RESOLUTIONS. INVESTIGATION OF A RECENT USER COMPLAINT DETERMINED ALL CTLR ACTIONS WERE IN ACCORDANCE WITH FACILITY PROCS AND POLICIES. RADAR/DME ARE REQUIRED TO CONDUCT THE RWY 23 APCH. THE MVA HAS BEEN RECENTLY VERIFIED, AS REQUIRED BY FAA REVIEW POLICY. CTLR RADAR INDICATORS DISPLAY REQUIRED OBSTRUCTIONS. THE MSA (8800 FT) SHOULD NOT BE CONFUSED WITH MVA. MSA AND MVA ARE DEVELOPED BY DIFFERING CRITERIA.
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.