ZTL controller concerned with BE20 incorrect flight plan clearance.

Attributes
ACN	519856
Time
Date	200108
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : vxv.vortac
State Reference	TN
Altitude	msl single value : 29000
Environment
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : ztl.artcc
Operator	general aviation : personal
Make Model Name	Super King Air 200/Huron
Operating Under FAR Part	Part 91
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller limited radar : 19 controller military : 0 controller non radar : 19 controller radar : 19 controller supervisory : 0.25 controller time certified in position1 : 15 controller time certified in position2 : 2
ASRS Report	519856
Person 2
Affiliation	other
Function	flight crew : single pilot
Events
Anomaly	other anomaly other
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	faa : investigated
Supplementary
Problem Areas	Flight Crew Human Performance Company ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

Pilot of BE20 departed lzu (near atl) and was 'cleared as filed.' ATC's flight plan was lzu..notwo.J91.buley.J186.ape.J83.djb.J545.yxu..cytz. When pilot was given a shortcut to an intermediate point on J91, he stated that his plan did not have J91, he was showing dkk as his next fix. I do not know where this error occurred -- it was reported to the supervisor, but I am not aware of the results of their investigation (if any). The pilot never diverged from the path we (ATC) expected him to take due to a fortunate circumstance (having been cleared on a shorter routing for an early part of the flight). If this error had gone undetected past vxv (on J91), the aircraft would have begun to diverge rapidly from the course we anticipated, potentially resulting in a loss of separation, or entering the next sector without correct coordination or a handoff.

Original NASA ASRS Text

Title: ZTL CTLR CONCERNED WITH BE20 INCORRECT FLT PLAN CLRNC.

Narrative: PLT OF BE20 DEPARTED LZU (NEAR ATL) AND WAS 'CLRED AS FILED.' ATC'S FLT PLAN WAS LZU..NOTWO.J91.BULEY.J186.APE.J83.DJB.J545.YXU..CYTZ. WHEN PLT WAS GIVEN A SHORTCUT TO AN INTERMEDIATE POINT ON J91, HE STATED THAT HIS PLAN DID NOT HAVE J91, HE WAS SHOWING DKK AS HIS NEXT FIX. I DO NOT KNOW WHERE THIS ERROR OCCURRED -- IT WAS RPTED TO THE SUPVR, BUT I AM NOT AWARE OF THE RESULTS OF THEIR INVESTIGATION (IF ANY). THE PLT NEVER DIVERGED FROM THE PATH WE (ATC) EXPECTED HIM TO TAKE DUE TO A FORTUNATE CIRCUMSTANCE (HAVING BEEN CLRED ON A SHORTER ROUTING FOR AN EARLY PART OF THE FLT). IF THIS ERROR HAD GONE UNDETECTED PAST VXV (ON J91), THE ACFT WOULD HAVE BEGUN TO DIVERGE RAPIDLY FROM THE COURSE WE ANTICIPATED, POTENTIALLY RESULTING IN A LOSS OF SEPARATION, OR ENTERING THE NEXT SECTOR WITHOUT CORRECT COORD OR A HDOF.

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.