Radar controller reports MU2 pilot filed for high altitude routing without access to jet route chart...

Attributes
ACN	675284
Time
Date	200510
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : sax.vortac
State Reference	NJ
Altitude	msl single value : 24000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zny.artcc
Operator	general aviation : personal
Make Model Name	MU-2
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 radar : 18
ASRS Report	675284
Person 2
Affiliation	other
Function	flight crew : single pilot
Events
Anomaly	non adherence : clearance non adherence : far other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Supplementary
Problem Areas	Chart Or Publication Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Pilot checked on frequency at FL240 over sax VOR. A few mins later; the aircraft was observed on a wbound heading over the stw VOR; approximately 5 mi off route and diverging further away. (Upon check-in; pilot had requested how to spell 'empty' (an intersection on his route of flight). He was given the appropriate spelling and verified route J80 empty hfy). Pilot was put on a 260 degree heading and asked if he thought he was cleared direct to empty. He advised 'no.' then issued direct etx J80 and acknowledged. Approaching J80; pilot advised he would need a heading for J80. When asked why; the pilot informed he did not have jet route charts. Pilot was issued low level routing and victor airways. The deviation over stw VOR at FL240 could have been dangerous as jfk arrs cross stw VOR at FL230. Luckily; none were there at the time. After doing some research; the pilot had filed direct destination at FL200. He was then cleared via sax J80 empty direct destination. This pilot knew he had no jet route charts and filed at flight levels anyway. Then it seems he tried to 'fake it.' can't really figure out what he was thinking.

Original NASA ASRS Text

Title: RADAR CTLR RPTS MU2 PLT FILED FOR HIGH ALT ROUTING WITHOUT ACCESS TO JET RTE CHARTS. GOT CAUGHT ON TRACK DEV AND DIRECTED TO LOW ALT AIRWAY RTE TO DEST.

Narrative: PLT CHKED ON FREQ AT FL240 OVER SAX VOR. A FEW MINS LATER; THE ACFT WAS OBSERVED ON A WBOUND HDG OVER THE STW VOR; APPROX 5 MI OFF RTE AND DIVERGING FURTHER AWAY. (UPON CHK-IN; PLT HAD REQUESTED HOW TO SPELL 'EMPTY' (AN INTXN ON HIS RTE OF FLT). HE WAS GIVEN THE APPROPRIATE SPELLING AND VERIFIED RTE J80 EMPTY HFY). PLT WAS PUT ON A 260 DEG HDG AND ASKED IF HE THOUGHT HE WAS CLRED DIRECT TO EMPTY. HE ADVISED 'NO.' THEN ISSUED DIRECT ETX J80 AND ACKNOWLEDGED. APCHING J80; PLT ADVISED HE WOULD NEED A HDG FOR J80. WHEN ASKED WHY; THE PLT INFORMED HE DID NOT HAVE JET RTE CHARTS. PLT WAS ISSUED LOW LEVEL ROUTING AND VICTOR AIRWAYS. THE DEV OVER STW VOR AT FL240 COULD HAVE BEEN DANGEROUS AS JFK ARRS CROSS STW VOR AT FL230. LUCKILY; NONE WERE THERE AT THE TIME. AFTER DOING SOME RESEARCH; THE PLT HAD FILED DIRECT DEST AT FL200. HE WAS THEN CLRED VIA SAX J80 EMPTY DIRECT DEST. THIS PLT KNEW HE HAD NO JET RTE CHARTS AND FILED AT FLT LEVELS ANYWAY. THEN IT SEEMS HE TRIED TO 'FAKE IT.' CAN'T REALLY FIGURE OUT WHAT HE WAS THINKING.

Data retrieved from NASA's ASRS site as of January 2009 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.

Radar controller reports MU2 pilot filed for high altitude routing without access to jet route charts. Got caught on track deviation and directed to low altitude airway route to destination.