Narrative:

The C560 was a departure off the dfw area. The B737 was sbound opposite direction of the C560. The C560 was climbed to FL270. The C560 came back and requested FL290 for a final. The B737 was sbound at FL290. The right side issued the C560 climb clearance to FL280 and was issued the B737 traffic. The C560 read back FL290. It was believed by the r-side that the C560 read back FL280. The C560 climbed to FL290. The B737 was still at FL290 sbound head-on with the C560. I had just assumed the d-side and had been on position less than 2 mins when the incident took place. I was busy acclimating myself to the position, ie, looking for potential manual conflictions, determining if any point outs needed to be made, catching the flight progress strips up-to-date, handling calls from other controllers. During this period somehow I never heard the r-side issue the C560 climb to FL280, thus I was unable to catch the incorrect readback. The recording equipment shows that the readback came through, but I never heard it. I became aware of the problem when I glanced at the radar scope and saw that the C560 and the B737 were head-on approximately 10 mi apart. Conflict alert had not gone off yet. The C560 was out of FL287 climbing still. I immediately informed the r-side who immediately descended the C560 back to FL280. The B737 was climbed to FL310. The C560 said he thought he had been cleared to FL290. The B737 did receive an RA (TCASII) and was starting to make a turn away from the C560. The C560 pilot did call in later and admitted supposedly that he was not positive as to his assigned flight level. A pilot deviation is supposed to be filed against him. The pilot (C560) said he climbed FL290 because that was what he requested. I believe WX in the area may have distraction some. Planes were on the west side of the sector deviating. More attention to go there. I think the r-side did a good job of trying to get the planes separated once the problem was known. Supplemental information from acn 548759: gave aircraft #1 climb to FL280. Aircraft #2 was at FL290. Aircraft #1 climbed to FL290. Supplemental information from acn 548758: we were cleared to FL270, and requested FL290. We were told it would be a few mins. We were told FL280. We responded FL280. Immediately we were told FL290. We responded FL290. At about FL288, center told us to 'descend, you were cleared to FL280, you have traffic at FL290.' we said, 'we thought we were cleared to FL290, sorry.' they said the FL290 call was pointing out traffic, not an altitude for us to climb. I reported it back as an altitude to climb to. The controllers are so busy and talk so fast, if not too fast. Their sentences and wording all run together when talking to all of the aircraft in their area. It is hard to understand who they are talking to. A pilot does their best to pick out their call sign, and their information. The ATC controller gets so busy, they sometimes do not catch it if a pilot reads it back wrong. Callback conversation with reporter acn 548902 revealed the following information: reporter stated he had just assumed the radar associate position. He said the position was a little busy and that the briefing was properly performed. While scanning the sector, he noticed the head-on conflict between the C560 and the B737. He immediately told the radar controller that the C560 was climbing through his assigned altitude. He also saw the B737 taking evasive action.

Google
 

Original NASA ASRS Text

Title: ALT EXCURSION BY C560 CREW CAUSES CONFLICTION WITH B737 AT CRUISE ALT.

Narrative: THE C560 WAS A DEP OFF THE DFW AREA. THE B737 WAS SBOUND OPPOSITE DIRECTION OF THE C560. THE C560 WAS CLBED TO FL270. THE C560 CAME BACK AND REQUESTED FL290 FOR A FINAL. THE B737 WAS SBOUND AT FL290. THE R SIDE ISSUED THE C560 CLB CLRNC TO FL280 AND WAS ISSUED THE B737 TFC. THE C560 READ BACK FL290. IT WAS BELIEVED BY THE R-SIDE THAT THE C560 READ BACK FL280. THE C560 CLBED TO FL290. THE B737 WAS STILL AT FL290 SBOUND HEAD-ON WITH THE C560. I HAD JUST ASSUMED THE D-SIDE AND HAD BEEN ON POS LESS THAN 2 MINS WHEN THE INCIDENT TOOK PLACE. I WAS BUSY ACCLIMATING MYSELF TO THE POS, IE, LOOKING FOR POTENTIAL MANUAL CONFLICTIONS, DETERMINING IF ANY POINT OUTS NEEDED TO BE MADE, CATCHING THE FLT PROGRESS STRIPS UP-TO-DATE, HANDLING CALLS FROM OTHER CTLRS. DURING THIS PERIOD SOMEHOW I NEVER HEARD THE R-SIDE ISSUE THE C560 CLB TO FL280, THUS I WAS UNABLE TO CATCH THE INCORRECT READBACK. THE RECORDING EQUIP SHOWS THAT THE READBACK CAME THROUGH, BUT I NEVER HEARD IT. I BECAME AWARE OF THE PROB WHEN I GLANCED AT THE RADAR SCOPE AND SAW THAT THE C560 AND THE B737 WERE HEAD-ON APPROX 10 MI APART. CONFLICT ALERT HAD NOT GONE OFF YET. THE C560 WAS OUT OF FL287 CLBING STILL. I IMMEDIATELY INFORMED THE R-SIDE WHO IMMEDIATELY DSNDED THE C560 BACK TO FL280. THE B737 WAS CLBED TO FL310. THE C560 SAID HE THOUGHT HE HAD BEEN CLRED TO FL290. THE B737 DID RECEIVE AN RA (TCASII) AND WAS STARTING TO MAKE A TURN AWAY FROM THE C560. THE C560 PLT DID CALL IN LATER AND ADMITTED SUPPOSEDLY THAT HE WAS NOT POSITIVE AS TO HIS ASSIGNED FLT LEVEL. A PLTDEV IS SUPPOSED TO BE FILED AGAINST HIM. THE PLT (C560) SAID HE CLBED FL290 BECAUSE THAT WAS WHAT HE REQUESTED. I BELIEVE WX IN THE AREA MAY HAVE DISTR SOME. PLANES WERE ON THE W SIDE OF THE SECTOR DEVIATING. MORE ATTN TO GO THERE. I THINK THE R-SIDE DID A GOOD JOB OF TRYING TO GET THE PLANES SEPARATED ONCE THE PROB WAS KNOWN. SUPPLEMENTAL INFO FROM ACN 548759: GAVE ACFT #1 CLB TO FL280. ACFT #2 WAS AT FL290. ACFT #1 CLBED TO FL290. SUPPLEMENTAL INFO FROM ACN 548758: WE WERE CLRED TO FL270, AND REQUESTED FL290. WE WERE TOLD IT WOULD BE A FEW MINS. WE WERE TOLD FL280. WE RESPONDED FL280. IMMEDIATELY WE WERE TOLD FL290. WE RESPONDED FL290. AT ABOUT FL288, CTR TOLD US TO 'DSND, YOU WERE CLRED TO FL280, YOU HAVE TFC AT FL290.' WE SAID, 'WE THOUGHT WE WERE CLRED TO FL290, SORRY.' THEY SAID THE FL290 CALL WAS POINTING OUT TFC, NOT AN ALT FOR US TO CLB. I RPTED IT BACK AS AN ALT TO CLB TO. THE CTLRS ARE SO BUSY AND TALK SO FAST, IF NOT TOO FAST. THEIR SENTENCES AND WORDING ALL RUN TOGETHER WHEN TALKING TO ALL OF THE ACFT IN THEIR AREA. IT IS HARD TO UNDERSTAND WHO THEY ARE TALKING TO. A PLT DOES THEIR BEST TO PICK OUT THEIR CALL SIGN, AND THEIR INFO. THE ATC CTLR GETS SO BUSY, THEY SOMETIMES DO NOT CATCH IT IF A PLT READS IT BACK WRONG. CALLBACK CONVERSATION WITH RPTR ACN 548902 REVEALED THE FOLLOWING INFO: RPTR STATED HE HAD JUST ASSUMED THE RADAR ASSOCIATE POS. HE SAID THE POS WAS A LITTLE BUSY AND THAT THE BRIEFING WAS PROPERLY PERFORMED. WHILE SCANNING THE SECTOR, HE NOTICED THE HEAD-ON CONFLICT BTWN THE C560 AND THE B737. HE IMMEDIATELY TOLD THE RADAR CTLR THAT THE C560 WAS CLBING THROUGH HIS ASSIGNED ALT. HE ALSO SAW THE B737 TAKING EVASIVE ACTION.

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.