37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 538650 |
Time | |
Date | 200202 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
State Reference | IN |
Altitude | msl bound lower : 35000 msl bound upper : 39000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zid.artcc artcc : zkc.artcc |
Operator | common carrier : air carrier |
Make Model Name | B737-700 |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain instruction : instructor oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 225 flight time total : 24800 flight time type : 8200 |
ASRS Report | 538650 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer instruction : trainee |
Qualification | pilot : commercial pilot : instrument pilot : multi engine |
Experience | flight time last 90 days : 16 flight time total : 3500 flight time type : 16 |
ASRS Report | 538651 |
Events | |
Anomaly | altitude deviation : excursion from assigned altitude inflight encounter other non adherence : company policies non adherence : clearance other anomaly other anomaly other anomaly other |
Independent Detector | atc equipment other atc equipment : radar other controllera other flight crewa |
Resolutory Action | controller : issued new clearance flight crew : exited adverse environment flight crew : regained aircraft control flight crew : overrode automation other |
Consequence | faa : investigated faa : reviewed incident with flight crew other |
Supplementary | |
Problem Areas | Aircraft Environmental Factor Flight Crew Human Performance Weather |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
About 2.5 hours into our flight, first officer requested to use the restroom. I agreed. It was the first officer's leg. He had made mention twice that the airspeed control was a challenge during this first portion of the 6 hour leg. The aircraft was stable and within an acceptable speed range as the first officer left the flight deck (reference time/security reference door pinning). I was also busy with the route on the release and studying the route segment breakdown. I soon noticed a subtle buffet and directed all my attention to the buffet to adjust the power as needed. We had made constant adjustments since at cruise altitude there had been constant intermittent light chop. At the time of the occurrence the ride was relatively smooth. Initially, I noticed the airspeed was once again varying from target speed. The speed decreased as much as 20-25 KTS in a short moment at which time I checked the engine gauges to make certain all was normal. The speed change made me think something was non normal. After a brief assessment of all instruments, I realized the speed was continuing to decrease. Pitch was increasing. I decided to disengage the autoplt to be able to feel the aircraft and initiate the recovery. Once I had the aircraft in my hands, I could tell it was approaching a low speed buffet. I started a shallow descent rate of about 300-400 FPM and contacted center and stated I had encountered a burble of turbulence and needed to descend now. The controller asked to what altitude. I responded FL350. He then cleared me to FL350. I had already applied climb thrust to assist in the speed recovery. I don't remember any more said from the controller. The descent rate was still shallow. I continued the descent even though I had a satisfactory recovery to normal flight characteristics. (First officer returns.) with everything back to normal, I requested to be cleared back up to FL390. The controller cleared us to FL390. Nothing more was said by the controller. During the climb, I re-engaged the autoplt and gave the aircraft back to the first officer. A frequency change to ZKC was received and we made the changeover (contacted ind quality assurance -- not researched yet). I told him that this small part of the whole occurrence made it sound like an altitude deviation, but that I had requested FL350 and was cleared to that altitude by the controller. He just replied that he had not yet researched the incident. He took my name and phone number. He suggested that I make notes for future reference. Comments: it was obvious that the aircraft got into the low speed buffet range and was very sensitive on the controls. There was a group of distrs surrounding the first officer leaving the cockpit due to the required security measures. Airspeed control had been in need of constant attention for quite a while with the first officer making many throttle position changes. I noticed a major temperature change of almost 10 degrees about the time of the occurrence. We also hit a patch of light turbulence with the temperature deviation. I anticipated that the first officer had adjusted the power down slightly to compensate for a speed increase just prior to leaving the cockpit. The opc was checked once the first officer was back in his seat to compare the present conditions to the performance we experienced. We did hit the low end of the speed range. The CDU showed the maximum cruise altitude to be FL398 at the time of the occurrence. The power was set for maximum climb but the acceleration was very slow at which point I decided to start the descent to expedite the recovery and prevent any further degradation of speed. The IOE was a slight factor due to lack of experience on the first officer side, however, was not the cause, in my opinion. The dispatch release showed the large temperature deviation along the route about the area we experienced the occurrence. ATC never indicated that there was a problem with the occurrence. Supplemental information from acn 538651: captain asked for a phone number to follow up. Captain called ARTCC and was notified that some investigation is being made.
Original NASA ASRS Text
Title: AN ALTDEV EXCURSION MADE DURING A LOSS OF AIRSPD AND AN APCH TO STALL BY A B737-700 AT FL390 ON FREQ WITH ZID, IN.
Narrative: ABOUT 2.5 HRS INTO OUR FLT, FO REQUESTED TO USE THE RESTROOM. I AGREED. IT WAS THE FO'S LEG. HE HAD MADE MENTION TWICE THAT THE AIRSPD CTL WAS A CHALLENGE DURING THIS FIRST PORTION OF THE 6 HR LEG. THE ACFT WAS STABLE AND WITHIN AN ACCEPTABLE SPD RANGE AS THE FO LEFT THE FLT DECK (REF TIME/SECURITY REF DOOR PINNING). I WAS ALSO BUSY WITH THE RTE ON THE RELEASE AND STUDYING THE RTE SEGMENT BREAKDOWN. I SOON NOTICED A SUBTLE BUFFET AND DIRECTED ALL MY ATTN TO THE BUFFET TO ADJUST THE PWR AS NEEDED. WE HAD MADE CONSTANT ADJUSTMENTS SINCE AT CRUISE ALT THERE HAD BEEN CONSTANT INTERMITTENT LIGHT CHOP. AT THE TIME OF THE OCCURRENCE THE RIDE WAS RELATIVELY SMOOTH. INITIALLY, I NOTICED THE AIRSPD WAS ONCE AGAIN VARYING FROM TARGET SPD. THE SPD DECREASED AS MUCH AS 20-25 KTS IN A SHORT MOMENT AT WHICH TIME I CHKED THE ENG GAUGES TO MAKE CERTAIN ALL WAS NORMAL. THE SPD CHANGE MADE ME THINK SOMETHING WAS NON NORMAL. AFTER A BRIEF ASSESSMENT OF ALL INSTS, I REALIZED THE SPD WAS CONTINUING TO DECREASE. PITCH WAS INCREASING. I DECIDED TO DISENGAGE THE AUTOPLT TO BE ABLE TO FEEL THE ACFT AND INITIATE THE RECOVERY. ONCE I HAD THE ACFT IN MY HANDS, I COULD TELL IT WAS APCHING A LOW SPD BUFFET. I STARTED A SHALLOW DSCNT RATE OF ABOUT 300-400 FPM AND CONTACTED CTR AND STATED I HAD ENCOUNTERED A BURBLE OF TURB AND NEEDED TO DSND NOW. THE CTLR ASKED TO WHAT ALT. I RESPONDED FL350. HE THEN CLRED ME TO FL350. I HAD ALREADY APPLIED CLB THRUST TO ASSIST IN THE SPD RECOVERY. I DON'T REMEMBER ANY MORE SAID FROM THE CTLR. THE DSCNT RATE WAS STILL SHALLOW. I CONTINUED THE DSCNT EVEN THOUGH I HAD A SATISFACTORY RECOVERY TO NORMAL FLT CHARACTERISTICS. (FO RETURNS.) WITH EVERYTHING BACK TO NORMAL, I REQUESTED TO BE CLRED BACK UP TO FL390. THE CTLR CLRED US TO FL390. NOTHING MORE WAS SAID BY THE CTLR. DURING THE CLB, I RE-ENGAGED THE AUTOPLT AND GAVE THE ACFT BACK TO THE FO. A FREQ CHANGE TO ZKC WAS RECEIVED AND WE MADE THE CHANGEOVER (CONTACTED IND QUALITY ASSURANCE -- NOT RESEARCHED YET). I TOLD HIM THAT THIS SMALL PART OF THE WHOLE OCCURRENCE MADE IT SOUND LIKE AN ALTDEV, BUT THAT I HAD REQUESTED FL350 AND WAS CLRED TO THAT ALT BY THE CTLR. HE JUST REPLIED THAT HE HAD NOT YET RESEARCHED THE INCIDENT. HE TOOK MY NAME AND PHONE NUMBER. HE SUGGESTED THAT I MAKE NOTES FOR FUTURE REF. COMMENTS: IT WAS OBVIOUS THAT THE ACFT GOT INTO THE LOW SPD BUFFET RANGE AND WAS VERY SENSITIVE ON THE CTLS. THERE WAS A GROUP OF DISTRS SURROUNDING THE FO LEAVING THE COCKPIT DUE TO THE REQUIRED SECURITY MEASURES. AIRSPD CTL HAD BEEN IN NEED OF CONSTANT ATTN FOR QUITE A WHILE WITH THE FO MAKING MANY THROTTLE POS CHANGES. I NOTICED A MAJOR TEMP CHANGE OF ALMOST 10 DEGS ABOUT THE TIME OF THE OCCURRENCE. WE ALSO HIT A PATCH OF LIGHT TURB WITH THE TEMP DEV. I ANTICIPATED THAT THE FO HAD ADJUSTED THE PWR DOWN SLIGHTLY TO COMPENSATE FOR A SPD INCREASE JUST PRIOR TO LEAVING THE COCKPIT. THE OPC WAS CHKED ONCE THE FO WAS BACK IN HIS SEAT TO COMPARE THE PRESENT CONDITIONS TO THE PERFORMANCE WE EXPERIENCED. WE DID HIT THE LOW END OF THE SPD RANGE. THE CDU SHOWED THE MAX CRUISE ALT TO BE FL398 AT THE TIME OF THE OCCURRENCE. THE PWR WAS SET FOR MAX CLB BUT THE ACCELERATION WAS VERY SLOW AT WHICH POINT I DECIDED TO START THE DSCNT TO EXPEDITE THE RECOVERY AND PREVENT ANY FURTHER DEGRADATION OF SPD. THE IOE WAS A SLIGHT FACTOR DUE TO LACK OF EXPERIENCE ON THE FO SIDE, HOWEVER, WAS NOT THE CAUSE, IN MY OPINION. THE DISPATCH RELEASE SHOWED THE LARGE TEMP DEV ALONG THE RTE ABOUT THE AREA WE EXPERIENCED THE OCCURRENCE. ATC NEVER INDICATED THAT THERE WAS A PROB WITH THE OCCURRENCE. SUPPLEMENTAL INFO FROM ACN 538651: CAPT ASKED FOR A PHONE NUMBER TO FOLLOW UP. CAPT CALLED ARTCC AND WAS NOTIFIED THAT SOME INVESTIGATION IS BEING MADE.
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.