Narrative:

Air carrier X checked in at FL280 heading towards psk. We didn't have a strip on the airplane. The data block showed him landing pit. I descended air carrier X to FL270 and told him it was to keep him right for direction when he turned the corner. Air carrier X turned the corner up J53. The aircraft was handed off but I forgot to switch him. ZDC called over the line asking if we knew about the mode C intruder. It was air carrier X, who was on a tmu swap route. He was supposed to go rdu./.psk hvq jpu WISKE1 pit. In that I didn't know that and evidently the pilot didn't, we didn't notice anything wrong. ZID took the handoff, the aircraft turned into ZDC's airspace and was dropped off the scope. A multitude of errors contributed to the deviation. The ZTL quality assurance is still trying to sort it all out. The area was short staffed. Everyone was still tired from the day before (8000+ operations with level 6 thunderstorms). The strip was not delivered in a timely manner. I and my d-side were too busy to do our jobs right. Another typical day at ZTL. Callback conversation with reporter revealed the following information: analyst learned from the callback that the reporter has not been charged with the deviation, that the reporter was told it was a tmu rerte with the clearance being given by the rdu ground controller during the aircraft's taxi for departure, that the reporter thought the aircraft was rted via J53 which reporter claimed is the standard route for traffic to pit. The reporter missed the error message after the directed handoff to ZDC and was not aware it had been taken by ZID. Reporter is unsure if the flight crew received routing via J53 or if by reporter's statement to them regarding the corner and altitude that the flight crew mistook the information as implying that they turn onto J53. Reporter claims the facility is below the staffing level.

Related reports:

Google
 

Original NASA ASRS Text

Title: RPTR SIT IN WHICH AN ACR B737 ENTERED ZDC'S AIRSPACE ON J53 INSTEAD OF ZID'S DIRECT HVQ. APPARENT FLC ATC MISUNDERSTANDING ON RTE TO BE FLOWN.

Narrative: ACR X CHKED IN AT FL280 HDG TOWARDS PSK. WE DIDN'T HAVE A STRIP ON THE AIRPLANE. THE DATA BLOCK SHOWED HIM LNDG PIT. I DSNDED ACR X TO FL270 AND TOLD HIM IT WAS TO KEEP HIM R FOR DIRECTION WHEN HE TURNED THE CORNER. ACR X TURNED THE CORNER UP J53. THE ACFT WAS HANDED OFF BUT I FORGOT TO SWITCH HIM. ZDC CALLED OVER THE LINE ASKING IF WE KNEW ABOUT THE MODE C INTRUDER. IT WAS ACR X, WHO WAS ON A TMU SWAP RTE. HE WAS SUPPOSED TO GO RDU./.PSK HVQ JPU WISKE1 PIT. IN THAT I DIDN'T KNOW THAT AND EVIDENTLY THE PLT DIDN'T, WE DIDN'T NOTICE ANYTHING WRONG. ZID TOOK THE HDOF, THE ACFT TURNED INTO ZDC'S AIRSPACE AND WAS DROPPED OFF THE SCOPE. A MULTITUDE OF ERRORS CONTRIBUTED TO THE DEV. THE ZTL QUALITY ASSURANCE IS STILL TRYING TO SORT IT ALL OUT. THE AREA WAS SHORT STAFFED. EVERYONE WAS STILL TIRED FROM THE DAY BEFORE (8000+ OPS WITH LEVEL 6 TSTMS). THE STRIP WAS NOT DELIVERED IN A TIMELY MANNER. I AND MY D-SIDE WERE TOO BUSY TO DO OUR JOBS RIGHT. ANOTHER TYPICAL DAY AT ZTL. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: ANALYST LEARNED FROM THE CALLBACK THAT THE RPTR HAS NOT BEEN CHARGED WITH THE DEV, THAT THE RPTR WAS TOLD IT WAS A TMU RERTE WITH THE CLRNC BEING GIVEN BY THE RDU GND CTLR DURING THE ACFT'S TAXI FOR DEP, THAT THE RPTR THOUGHT THE ACFT WAS RTED VIA J53 WHICH RPTR CLAIMED IS THE STANDARD RTE FOR TFC TO PIT. THE RPTR MISSED THE ERROR MESSAGE AFTER THE DIRECTED HDOF TO ZDC AND WAS NOT AWARE IT HAD BEEN TAKEN BY ZID. RPTR IS UNSURE IF THE FLC RECEIVED ROUTING VIA J53 OR IF BY RPTR'S STATEMENT TO THEM REGARDING THE CORNER AND ALT THAT THE FLC MISTOOK THE INFO AS IMPLYING THAT THEY TURN ONTO J53. RPTR CLAIMS THE FACILITY IS BELOW THE STAFFING LEVEL.

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.