Narrative:

While in cruise flight at FL290 ATC issued instructions to slow to 280 KIAS (approximately 20 KIAS). I changed autoflt modes from 'vertical navigation' to 'MCP speed' to comply. Shortly after ATC cleared us to FL280. I selected and executed FL280 in the FMC, however the autoplt did not begin a descent because I did not reselect VNAV and it was therefore not in the correct mode to respond to FMC commands. The controller then cleared a B727 behind us to 'accelerate maximum forward speed, descend and maintain FL290.' a conflict developed because of our delay vacating FL290. On TCASII the B727 was at our closest point 2 NM laterally and 700 ft vertically and in sight visually. ATC queried us about our altitude and I expedited our descent. Separation was lost for a matter of seconds. Contributing factors may have been: fatigue. This was the last of 5 legs and approaching the end of an 8 hour duty day and 7 hour hard time flying day. Complacency -- this was our third slc-den leg of the day. Distractions -- the captain was eating lunch and setting up for the arrival. Mistaking autothrottle movement and aircraft pitch change (to airspeed change, not altitude change) for proper response rather than proper primary instrument verification (automation complacency). Difference in equipment speed between B737 and the B727 and the combination of a 'slow down, descend clearance' at an altitude below a 'speed up, descend' clearance to a higher and much faster aircraft. Supplemental information from acn 423282: I set FL280 and pointed at the MCP window until the first officer confirmed it. I thought it might get bumpy, so I turned on the fasten seat belt sign and told my first officer I was off the radio to make the final announcement and notify the flight attendants that I'd be seating them shortly. As we received the initial instruction to slow, I looked to my left to get my mouthpiece and check my map. At this point my first officer deselected VNAV. I never realized we had changed modes. When we were instructed to descend, I saw her (first officer) type in the new altitude. Our company has a procedure, where the PNF sets the new altitude in the MCP and points at the MCP window until the PF acknowledges. I did this, and thinking we were in VNAV assumed the aircraft would begin its descent. Inactions by captain: never really confirmed we were in descent. Did not maintain silence until descent began. This may have distracted first officer. Inactions by first officer: never entered proper mode to begin descent. Never confirmed descent began. Recommendations: when a new mode is selected on MCP, it should be announced. PNF after pointing at MCP should point at the vertical speed indicator to confirm descent, if it is to begin shortly. If not, he should point at FMA and confirm proper mode selected. Captain should provide for an undistracting work environment, by holding off on the announcements and talking until descent has actually begun. Supplemental information from acn 423428: ZDV asked the B737 to slow to 280 KTS and asked us to pick our speed up. Very shortly after this ZDV cleared the B737 to descend to FL280 from FL290, then immediately gave us a clearance to FL290 and told us to keep our speed up. I began looking for the B737 again. I saw on the TCASII that the B737 was still at FL290. We were descending through FL300. I adjusted the scale on TCASII and found we only had about 3 mi horizontal separation. I pointed this out to the captain who leveled us off at FL295. Soon after that ZDV called the B737 and asked if he had begun his descent and he replied that he was starting down now. Once our TCASII indicated we had 1000 ft separation, we continued our descent to FL290. Contributing factors: I don't think that ATC considered the fact that a B727 told to descend and keep their speed up is going to come down much more rapidly than a B737 with a speed restr. Giving both of these aircraft their descent clrncs simultaneously when they are already at the minimum vertical IFR separation is going to cause a conflict. Also the B737 being a glass cockpit, is going to take longer to initiate the descent due to the typing involved for the FMS and the slow pitch rate of the autoplt. The B727 is non- glass. You just point the nose down and you are descending. It is a lot less involved. To avoid this in the future I think if ATC needs to descend 2 aircraft at adjacent flight levels who don't have horizontal spacing, they should delay giving the descent clearance to the second aircraft until the first aircraft has reached its newly assigned altitude.

Google
 

Original NASA ASRS Text

Title: A B737-300 SUBJECT TO A SPD RESTR DELAYS ITS DSCNT FROM FL290 TO FL280. A DSNDING, OVERTAKING B727 EXPERIENCES A POTENTIAL CONFLICT WITH THAT ACFT WHEN CLRED TO FL290.

Narrative: WHILE IN CRUISE FLT AT FL290 ATC ISSUED INSTRUCTIONS TO SLOW TO 280 KIAS (APPROX 20 KIAS). I CHANGED AUTOFLT MODES FROM 'VERT NAV' TO 'MCP SPD' TO COMPLY. SHORTLY AFTER ATC CLRED US TO FL280. I SELECTED AND EXECUTED FL280 IN THE FMC, HOWEVER THE AUTOPLT DID NOT BEGIN A DSCNT BECAUSE I DID NOT RESELECT VNAV AND IT WAS THEREFORE NOT IN THE CORRECT MODE TO RESPOND TO FMC COMMANDS. THE CTLR THEN CLRED A B727 BEHIND US TO 'ACCELERATE MAX FORWARD SPD, DSND AND MAINTAIN FL290.' A CONFLICT DEVELOPED BECAUSE OF OUR DELAY VACATING FL290. ON TCASII THE B727 WAS AT OUR CLOSEST POINT 2 NM LATERALLY AND 700 FT VERTLY AND IN SIGHT VISUALLY. ATC QUERIED US ABOUT OUR ALT AND I EXPEDITED OUR DSCNT. SEPARATION WAS LOST FOR A MATTER OF SECONDS. CONTRIBUTING FACTORS MAY HAVE BEEN: FATIGUE. THIS WAS THE LAST OF 5 LEGS AND APCHING THE END OF AN 8 HR DUTY DAY AND 7 HR HARD TIME FLYING DAY. COMPLACENCY -- THIS WAS OUR THIRD SLC-DEN LEG OF THE DAY. DISTRACTIONS -- THE CAPT WAS EATING LUNCH AND SETTING UP FOR THE ARR. MISTAKING AUTOTHROTTLE MOVEMENT AND ACFT PITCH CHANGE (TO AIRSPD CHANGE, NOT ALT CHANGE) FOR PROPER RESPONSE RATHER THAN PROPER PRIMARY INST VERIFICATION (AUTOMATION COMPLACENCY). DIFFERENCE IN EQUIP SPD BTWN B737 AND THE B727 AND THE COMBINATION OF A 'SLOW DOWN, DSND CLRNC' AT AN ALT BELOW A 'SPD UP, DSND' CLRNC TO A HIGHER AND MUCH FASTER ACFT. SUPPLEMENTAL INFO FROM ACN 423282: I SET FL280 AND POINTED AT THE MCP WINDOW UNTIL THE FO CONFIRMED IT. I THOUGHT IT MIGHT GET BUMPY, SO I TURNED ON THE FASTEN SEAT BELT SIGN AND TOLD MY FO I WAS OFF THE RADIO TO MAKE THE FINAL ANNOUNCEMENT AND NOTIFY THE FLT ATTENDANTS THAT I'D BE SEATING THEM SHORTLY. AS WE RECEIVED THE INITIAL INSTRUCTION TO SLOW, I LOOKED TO MY L TO GET MY MOUTHPIECE AND CHK MY MAP. AT THIS POINT MY FO DESELECTED VNAV. I NEVER REALIZED WE HAD CHANGED MODES. WHEN WE WERE INSTRUCTED TO DSND, I SAW HER (FO) TYPE IN THE NEW ALT. OUR COMPANY HAS A PROC, WHERE THE PNF SETS THE NEW ALT IN THE MCP AND POINTS AT THE MCP WINDOW UNTIL THE PF ACKNOWLEDGES. I DID THIS, AND THINKING WE WERE IN VNAV ASSUMED THE ACFT WOULD BEGIN ITS DSCNT. INACTIONS BY CAPT: NEVER REALLY CONFIRMED WE WERE IN DSCNT. DID NOT MAINTAIN SILENCE UNTIL DSCNT BEGAN. THIS MAY HAVE DISTRACTED FO. INACTIONS BY FO: NEVER ENTERED PROPER MODE TO BEGIN DSCNT. NEVER CONFIRMED DSCNT BEGAN. RECOMMENDATIONS: WHEN A NEW MODE IS SELECTED ON MCP, IT SHOULD BE ANNOUNCED. PNF AFTER POINTING AT MCP SHOULD POINT AT THE VERT SPD INDICATOR TO CONFIRM DSCNT, IF IT IS TO BEGIN SHORTLY. IF NOT, HE SHOULD POINT AT FMA AND CONFIRM PROPER MODE SELECTED. CAPT SHOULD PROVIDE FOR AN UNDISTRACTING WORK ENVIRONMENT, BY HOLDING OFF ON THE ANNOUNCEMENTS AND TALKING UNTIL DSCNT HAS ACTUALLY BEGUN. SUPPLEMENTAL INFO FROM ACN 423428: ZDV ASKED THE B737 TO SLOW TO 280 KTS AND ASKED US TO PICK OUR SPD UP. VERY SHORTLY AFTER THIS ZDV CLRED THE B737 TO DSND TO FL280 FROM FL290, THEN IMMEDIATELY GAVE US A CLRNC TO FL290 AND TOLD US TO KEEP OUR SPD UP. I BEGAN LOOKING FOR THE B737 AGAIN. I SAW ON THE TCASII THAT THE B737 WAS STILL AT FL290. WE WERE DSNDING THROUGH FL300. I ADJUSTED THE SCALE ON TCASII AND FOUND WE ONLY HAD ABOUT 3 MI HORIZ SEPARATION. I POINTED THIS OUT TO THE CAPT WHO LEVELED US OFF AT FL295. SOON AFTER THAT ZDV CALLED THE B737 AND ASKED IF HE HAD BEGUN HIS DSCNT AND HE REPLIED THAT HE WAS STARTING DOWN NOW. ONCE OUR TCASII INDICATED WE HAD 1000 FT SEPARATION, WE CONTINUED OUR DSCNT TO FL290. CONTRIBUTING FACTORS: I DON'T THINK THAT ATC CONSIDERED THE FACT THAT A B727 TOLD TO DSND AND KEEP THEIR SPD UP IS GOING TO COME DOWN MUCH MORE RAPIDLY THAN A B737 WITH A SPD RESTR. GIVING BOTH OF THESE ACFT THEIR DSCNT CLRNCS SIMULTANEOUSLY WHEN THEY ARE ALREADY AT THE MINIMUM VERT IFR SEPARATION IS GOING TO CAUSE A CONFLICT. ALSO THE B737 BEING A GLASS COCKPIT, IS GOING TO TAKE LONGER TO INITIATE THE DSCNT DUE TO THE TYPING INVOLVED FOR THE FMS AND THE SLOW PITCH RATE OF THE AUTOPLT. THE B727 IS NON- GLASS. YOU JUST POINT THE NOSE DOWN AND YOU ARE DSNDING. IT IS A LOT LESS INVOLVED. TO AVOID THIS IN THE FUTURE I THINK IF ATC NEEDS TO DSND 2 ACFT AT ADJACENT FLT LEVELS WHO DON'T HAVE HORIZ SPACING, THEY SHOULD DELAY GIVING THE DSCNT CLRNC TO THE SECOND ACFT UNTIL THE FIRST ACFT HAS REACHED ITS NEWLY ASSIGNED ALT.

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.