Narrative:

I was working sectors 45/46 combined. The supervisor took the d-side to help another sector, moderately busy. Tys handed off a PA28(?) at 6000 ft northbound. I took the handoff before I realized I didn't have a strip. Flight plan readout says direct luk. But there are latitude/longitudes in the flight plan. Route display shows route going to a point 30 mi northwest of tys and then a turn towards luk. Someone had put in the wrong latitude/longitudes. I called tys approach to verify aircraft was proceeding direct luk. I fixed the flight data. Looked up and the regional jet was in sector 44's airspace. Turned him 90 degrees back into my airspace and called sector 44 with a pointout. They showed me some traffic to miss. The rj had filed tri odf MACEY2 atl with 'anr' in the remarks section. There was a pdr/PAR on the strip tri sot odf MACEY2 atl. Every other rj I've seen from this company files the correct routing. This one was going direct odf instead of sot. That's why he was in sector 44's airspace. Understaffed. Latitude/longitude in flight plan (approach can't tell if it is right or wrong). Non standard route (what does 'anr' mean?) pdr/PAR not issued? Deviation.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZTL CTLR EXPERIENCED OPDEV WITH ADJACENT SECTOR AIRSPACE BECAUSE OF ROUTING UNCERTAINTY.

Narrative: I WAS WORKING SECTORS 45/46 COMBINED. THE SUPVR TOOK THE D-SIDE TO HELP ANOTHER SECTOR, MODERATELY BUSY. TYS HANDED OFF A PA28(?) AT 6000 FT NBOUND. I TOOK THE HDOF BEFORE I REALIZED I DIDN'T HAVE A STRIP. FLT PLAN READOUT SAYS DIRECT LUK. BUT THERE ARE LATITUDE/LONGITUDES IN THE FLT PLAN. RTE DISPLAY SHOWS RTE GOING TO A POINT 30 MI NW OF TYS AND THEN A TURN TOWARDS LUK. SOMEONE HAD PUT IN THE WRONG LATITUDE/LONGITUDES. I CALLED TYS APCH TO VERIFY ACFT WAS PROCEEDING DIRECT LUK. I FIXED THE FLT DATA. LOOKED UP AND THE REGIONAL JET WAS IN SECTOR 44'S AIRSPACE. TURNED HIM 90 DEGS BACK INTO MY AIRSPACE AND CALLED SECTOR 44 WITH A POINTOUT. THEY SHOWED ME SOME TFC TO MISS. THE RJ HAD FILED TRI ODF MACEY2 ATL WITH 'ANR' IN THE REMARKS SECTION. THERE WAS A PDR/PAR ON THE STRIP TRI SOT ODF MACEY2 ATL. EVERY OTHER RJ I'VE SEEN FROM THIS COMPANY FILES THE CORRECT ROUTING. THIS ONE WAS GOING DIRECT ODF INSTEAD OF SOT. THAT'S WHY HE WAS IN SECTOR 44'S AIRSPACE. UNDERSTAFFED. LATITUDE/LONGITUDE IN FLT PLAN (APCH CAN'T TELL IF IT IS RIGHT OR WRONG). NON STANDARD RTE (WHAT DOES 'ANR' MEAN?) PDR/PAR NOT ISSUED? DEV.

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.