Narrative:

I was acting as PIC of a scheduled part 121 flight from new york (lga) to columbus, ohio (cmh). We were being vectored by new york center and flying an assigned heading parallel to our route, J-80. We received a clearance to climb to FL280. We set the altitude alerter and started out from FL230. Shortly after passing FL250 (about 25200 ft) center instructed us to level at FL260. The aircraft was being flown by the first officer and was climbing at a rapid rate, so he hurriedly leveled at FL260. At the same time center advised us of traffic at our 10 O'clock position, and at FL270. I was looking for the traffic and had him in sight. Our flight paths were merging. While I was watching the aircraft my attention was drawn back inside to the ivsi which had illuminated and our TCASII alert went off. I immediately saw that we had departed FL260 and were climbing. We had already passed FL265 when I instructed the first officer to return to FL260 as soon as possible!! We did so but not before setting off an RA for the other aircraft who started to climb. Center asked us our altitude and by then we were just about level at FL260 again. The error in this situation was ours. Although we were leveled at FL260 we never had a chance to reset our altitude alerter and after a few minutes the first officer thought we had been re-cleared to FL280, but we had not been due to the flight above us at FL270 and merging from our left. I failed to catch the climb because I was keeping the aircraft in sight. I do feel that contributing factors are the amount of radio calls and frequency changes required when departing new york. Frequently there are numerous calls required to contact new york center controllers. There is a high amount of vectoring and altitude clrncs issued. These events happen at a rapid pace. Sometimes it becomes difficult to keep up.

Google
 

Original NASA ASRS Text

Title: DC-9 ACFT IN CLB WAS STOPPED SHORT OF ASSIGNED ALT DUE TO HIGHER TFC. ALT ALERTER NOT RESET AND PF, THOUGHT THEY WERE STILL GOING TO THE ORIGINAL ALT AND COMMENCED CLB CAUSING LOSS OF SEPARATION AND TCASII ALERTS ON BOTH ACFT.

Narrative: I WAS ACTING AS PIC OF A SCHEDULED PART 121 FLT FROM NEW YORK (LGA) TO COLUMBUS, OHIO (CMH). WE WERE BEING VECTORED BY NEW YORK CTR AND FLYING AN ASSIGNED HDG PARALLEL TO OUR ROUTE, J-80. WE RECEIVED A CLRNC TO CLB TO FL280. WE SET THE ALT ALERTER AND STARTED OUT FROM FL230. SHORTLY AFTER PASSING FL250 (ABOUT 25200 FT) CTR INSTRUCTED US TO LEVEL AT FL260. THE ACFT WAS BEING FLOWN BY THE FO AND WAS CLBING AT A RAPID RATE, SO HE HURRIEDLY LEVELED AT FL260. AT THE SAME TIME CTR ADVISED US OF TFC AT OUR 10 O'CLOCK POS, AND AT FL270. I WAS LOOKING FOR THE TFC AND HAD HIM IN SIGHT. OUR FLT PATHS WERE MERGING. WHILE I WAS WATCHING THE ACFT MY ATTN WAS DRAWN BACK INSIDE TO THE IVSI WHICH HAD ILLUMINATED AND OUR TCASII ALERT WENT OFF. I IMMEDIATELY SAW THAT WE HAD DEPARTED FL260 AND WERE CLBING. WE HAD ALREADY PASSED FL265 WHEN I INSTRUCTED THE FO TO RETURN TO FL260 ASAP!! WE DID SO BUT NOT BEFORE SETTING OFF AN RA FOR THE OTHER ACFT WHO STARTED TO CLB. CTR ASKED US OUR ALT AND BY THEN WE WERE JUST ABOUT LEVEL AT FL260 AGAIN. THE ERROR IN THIS SIT WAS OURS. ALTHOUGH WE WERE LEVELED AT FL260 WE NEVER HAD A CHANCE TO RESET OUR ALT ALERTER AND AFTER A FEW MINUTES THE FO THOUGHT WE HAD BEEN RE-CLRED TO FL280, BUT WE HAD NOT BEEN DUE TO THE FLT ABOVE US AT FL270 AND MERGING FROM OUR L. I FAILED TO CATCH THE CLB BECAUSE I WAS KEEPING THE ACFT IN SIGHT. I DO FEEL THAT CONTRIBUTING FACTORS ARE THE AMOUNT OF RADIO CALLS AND FREQUENCY CHANGES REQUIRED WHEN DEPARTING NEW YORK. FREQUENTLY THERE ARE NUMEROUS CALLS REQUIRED TO CONTACT NEW YORK CTR CTLRS. THERE IS A HIGH AMOUNT OF VECTORING AND ALT CLRNCS ISSUED. THESE EVENTS HAPPEN AT A RAPID PACE. SOMETIMES IT BECOMES DIFFICULT TO KEEP UP.

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.