ZTL controller expressed frustration regarding an incorrect filed flight plan.

Attributes
ACN	610103
Time
Date	200403
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : hmv.vortac
State Reference	TN
Altitude	msl bound lower : 31000 msl bound upper : 33000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : ztl.artcc
Operator	general aviation : corporate
Make Model Name	Citationjet, C525/C526
Operating Under FAR Part	Part 91
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 22
ASRS Report	610103
Person 2
Affiliation	company : corporate
Function	flight crew : captain oversight : pic
Events
Anomaly	non adherence : published procedure non adherence other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance flight crew : returned to original clearance
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

Aircraft X departed jqf (concord, nc) for ane. As soon as aircraft X checked in I started quizzing him about his flight plan. He filed jqf direct to a fix on the EAU6 arrival to ane. He filed via internet. I asked how he was cleared. (Notice full route clearance in the remarks section.) he was cleared jqf hornet 1 naly hmv direct to the latitude/longitudes then the eauclaire 6 arrival to ane. He accepted the clearance even though he didn't know where the latitude/longitudes were. He later discovered they belonged to ane. So he was cleared hmv ane EAU6 ane. This is a multifaceted problem. 1) the pilot filed a flight plan that was not in accordance with the aim. 2) on-line service provider inserted the latitude/longitudes (that the pilot didn't file) to 'make' the data processing work. 3) clt approach cleared the aircraft to the latitude/longitudes. 4) the first center sector did not review the proposed flight plan and correct it, as they are required to do. 5) the pilot accepted the clearance without knowing where the latitude/longitudes were. 6) nobody bothered to fix it, even after the error was discovered. 7) I cleared him to bae (where the arrival starts) EAU6 ane.

Original NASA ASRS Text

Title: ZTL CTLR EXPRESSED FRUSTRATION REGARDING AN INCORRECT FILED FLT PLAN.

Narrative: ACFT X DEPARTED JQF (CONCORD, NC) FOR ANE. AS SOON AS ACFT X CHKED IN I STARTED QUIZZING HIM ABOUT HIS FLT PLAN. HE FILED JQF DIRECT TO A FIX ON THE EAU6 ARR TO ANE. HE FILED VIA INTERNET. I ASKED HOW HE WAS CLRED. (NOTICE FULL RTE CLRNC IN THE REMARKS SECTION.) HE WAS CLRED JQF HORNET 1 NALY HMV DIRECT TO THE LATITUDE/LONGITUDES THEN THE EAUCLAIRE 6 ARR TO ANE. HE ACCEPTED THE CLRNC EVEN THOUGH HE DIDN'T KNOW WHERE THE LATITUDE/LONGITUDES WERE. HE LATER DISCOVERED THEY BELONGED TO ANE. SO HE WAS CLRED HMV ANE EAU6 ANE. THIS IS A MULTIFACETED PROB. 1) THE PLT FILED A FLT PLAN THAT WAS NOT IN ACCORDANCE WITH THE AIM. 2) ON-LINE SVC PROVIDER INSERTED THE LATITUDE/LONGITUDES (THAT THE PLT DIDN'T FILE) TO 'MAKE' THE DATA PROCESSING WORK. 3) CLT APCH CLRED THE ACFT TO THE LATITUDE/LONGITUDES. 4) THE FIRST CTR SECTOR DID NOT REVIEW THE PROPOSED FLT PLAN AND CORRECT IT, AS THEY ARE REQUIRED TO DO. 5) THE PLT ACCEPTED THE CLRNC WITHOUT KNOWING WHERE THE LATITUDE/LONGITUDES WERE. 6) NOBODY BOTHERED TO FIX IT, EVEN AFTER THE ERROR WAS DISCOVERED. 7) I CLRED HIM TO BAE (WHERE THE ARR STARTS) EAU6 ANE.

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.