37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 314087 |
Time | |
Date | 199508 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : slc |
State Reference | UT |
Altitude | agl bound lower : 100 agl bound upper : 200 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : slc tower : slc |
Operator | common carrier : air carrier |
Make Model Name | B727-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach landing other |
Route In Use | approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : atp pilot : instrument pilot : flight engineer |
Experience | flight time last 90 days : 200 flight time total : 9000 flight time type : 3500 |
ASRS Report | 314087 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | inflight encounter other |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : returned to intended course or assigned course other |
Consequence | Other |
Supplementary | |
Air Traffic Incident | other |
Narrative:
During visual approach to runway 34 at salt lake international at approximately 100-200 ft AGL, we encountered wake turbulence from a B-757 that we had followed at 4 1/2 to 5 mi. Captain advanced power toward go around and flew out of the turbulence and then made an uneventful landing I the touchdown zone of runway 34. Contributing factor might have been the rapid crossing of our runway threshold of 2 B-737-300 at high thrust just moments before we encountered the turbulence. The effect of the turbulence was a rapid roll to the right of about 20 degrees followed by one to the left about 20 degrees and a slight descent force. Callback conversation with reporter revealed the following information: the reporter said that everything seemed to be going fine. Their B727-200 was a little too close to the preceding B757-200, but the crew was staying above the GS and they were in smooth air. As they were approaching the runway however, the captain allowed the aircraft to settle below the GS where the wake was waiting. The recovery was well done, according to the first officer. The landing was somewhat firm and the ATCT local controller asked if the wing movement was due to normal turbulence or wake. One of the passenger complained at some length about the crew's flying technique this passenger also apparently complained to the FAA about the landing and the company talked to the captain, but the reporter was not contacted. Callback conversation with reporter revealed the following information on 314086: reporter participated in the wake turbulence callback program. Reporter stated that this turbulence was the sharpest and most jolting of anything he has ever been in. He felt the captain did a good job of maintaining control of the aircraft and landed in the touchdown zone of the runway even though he applied almost full power to fly out of the turbulence. The landing was hard enough that 1 passenger wanted them grounded and asked for all their names and certificate numbers. This reporter had to meet with the company's chief pilot to explain the situation. Reporter stated that there were 2 B-737-300's that had to hurry across runway before their aircraft touched down, and speculates that those 2 aircraft may have added to the effects of the wake turbulence. They may have moved the B-757 wake closer to the landing B-727 or created their own turbulence with the jet blast across the runway.
Original NASA ASRS Text
Title: WAKE TURB -- ACR HITS THE WAKE OF ANOTHER ACR ON SHORT FINAL APCH.
Narrative: DURING VISUAL APCH TO RWY 34 AT SALT LAKE INTL AT APPROX 100-200 FT AGL, WE ENCOUNTERED WAKE TURB FROM A B-757 THAT WE HAD FOLLOWED AT 4 1/2 TO 5 MI. CAPT ADVANCED PWR TOWARD GAR AND FLEW OUT OF THE TURB AND THEN MADE AN UNEVENTFUL LNDG I THE TOUCHDOWN ZONE OF RWY 34. CONTRIBUTING FACTOR MIGHT HAVE BEEN THE RAPID XING OF OUR RWY THRESHOLD OF 2 B-737-300 AT HIGH THRUST JUST MOMENTS BEFORE WE ENCOUNTERED THE TURB. THE EFFECT OF THE TURB WAS A RAPID ROLL TO THE R OF ABOUT 20 DEGS FOLLOWED BY ONE TO THE L ABOUT 20 DEGS AND A SLIGHT DSCNT FORCE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR SAID THAT EVERYTHING SEEMED TO BE GOING FINE. THEIR B727-200 WAS A LITTLE TOO CLOSE TO THE PRECEDING B757-200, BUT THE CREW WAS STAYING ABOVE THE GS AND THEY WERE IN SMOOTH AIR. AS THEY WERE APCHING THE RWY HOWEVER, THE CAPT ALLOWED THE ACFT TO SETTLE BELOW THE GS WHERE THE WAKE WAS WAITING. THE RECOVERY WAS WELL DONE, ACCORDING TO THE FO. THE LNDG WAS SOMEWHAT FIRM AND THE ATCT LCL CTLR ASKED IF THE WING MOVEMENT WAS DUE TO NORMAL TURB OR WAKE. ONE OF THE PAX COMPLAINED AT SOME LENGTH ABOUT THE CREW'S FLYING TECHNIQUE THIS PAX ALSO APPARENTLY COMPLAINED TO THE FAA ABOUT THE LNDG AND THE COMPANY TALKED TO THE CAPT, BUT THE RPTR WAS NOT CONTACTED. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO ON 314086: RPTR PARTICIPATED IN THE WAKE TURB CALLBACK PROGRAM. RPTR STATED THAT THIS TURB WAS THE SHARPEST AND MOST JOLTING OF ANYTHING HE HAS EVER BEEN IN. HE FELT THE CAPT DID A GOOD JOB OF MAINTAINING CTL OF THE ACFT AND LANDED IN THE TOUCHDOWN ZONE OF THE RWY EVEN THOUGH HE APPLIED ALMOST FULL PWR TO FLY OUT OF THE TURB. THE LNDG WAS HARD ENOUGH THAT 1 PAX WANTED THEM GNDED AND ASKED FOR ALL THEIR NAMES AND CERTIFICATE NUMBERS. THIS RPTR HAD TO MEET WITH THE COMPANY'S CHIEF PLT TO EXPLAIN THE SIT. RPTR STATED THAT THERE WERE 2 B-737-300'S THAT HAD TO HURRY ACROSS RWY BEFORE THEIR ACFT TOUCHED DOWN, AND SPECULATES THAT THOSE 2 ACFT MAY HAVE ADDED TO THE EFFECTS OF THE WAKE TURB. THEY MAY HAVE MOVED THE B-757 WAKE CLOSER TO THE LNDG B-727 OR CREATED THEIR OWN TURB WITH THE JET BLAST ACROSS THE RWY.
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.