Cpr pilot complains of ATC procedure in flight plan handling.

Attributes
ACN	203202
Time
Date	199202
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : mco
State Reference	FL
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : czeg
Operator	general aviation : corporate
Make Model Name	Small Transport
Flight Phase	climbout : takeoff cruise other ground : preflight
Route In Use	enroute airway : v267 enroute other
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : cfi pilot : instrument pilot : commercial
Experience	flight time last 90 days : 40 flight time total : 10000 flight time type : 500
ASRS Report	203202
Person 2
Affiliation	government : faa
Function	other personnel other
Qualification	other
Events
Anomaly	non adherence : clearance other anomaly other
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation other

Narrative:

I don't believe ATC personnel are quite clear or knowledgeable about the different type of RNAV units that are installed in aircraft. Examples VOR-DME-LORAN-latitude long etc. For the controller to know what system is being used by the pilot is important to both. In my case on a flight from mco, to mvn with a fuel stop at pdk I was issued a clearance I could not accomplish with my RNAV system. (VOR/DME and LORAN). Our is mco. I was given radar vectors to V267-vna 142/018 direct (filed as an intermediate point at request of FSS). Jax probably figured I could to jvc direct vna 142/018. With my equipment I can't do this without drawing a line in a crowded cockpit and setting way points. Very difficult. Also, off of pdk I was given a latitude-long in my clearance which I couldn't accept. Instead of an all inclusive RNAV designator, different letters should be assigned to different RNAV systems just as 1A-1B-1D and so on. My point being if ATC knew the system available to the pilot things would go much smoother. By the way I have suggested this to FAA many times. They didn't bother to reply.

Original NASA ASRS Text

Title: CPR PLT COMPLAINS OF ATC PROC IN FLT PLAN HANDLING.

Narrative: I DON'T BELIEVE ATC PERSONNEL ARE QUITE CLR OR KNOWLEDGEABLE ABOUT THE DIFFERENT TYPE OF RNAV UNITS THAT ARE INSTALLED IN ACFT. EXAMPLES VOR-DME-LORAN-LAT LONG ETC. FOR THE CTLR TO KNOW WHAT SYS IS BEING USED BY THE PLT IS IMPORTANT TO BOTH. IN MY CASE ON A FLT FROM MCO, TO MVN WITH A FUEL STOP AT PDK I WAS ISSUED A CLRNC I COULD NOT ACCOMPLISH WITH MY RNAV SYS. (VOR/DME AND LORAN). OUR IS MCO. I WAS GIVEN RADAR VECTORS TO V267-VNA 142/018 DIRECT (FILED AS AN INTERMEDIATE POINT AT REQUEST OF FSS). JAX PROBABLY FIGURED I COULD TO JVC DIRECT VNA 142/018. WITH MY EQUIP I CAN'T DO THIS WITHOUT DRAWING A LINE IN A CROWDED COCKPIT AND SETTING WAY POINTS. VERY DIFFICULT. ALSO, OFF OF PDK I WAS GIVEN A LAT-LONG IN MY CLRNC WHICH I COULDN'T ACCEPT. INSTEAD OF AN ALL INCLUSIVE RNAV DESIGNATOR, DIFFERENT LETTERS SHOULD BE ASSIGNED TO DIFFERENT RNAV SYSTEMS JUST AS 1A-1B-1D AND SO ON. MY POINT BEING IF ATC KNEW THE SYS AVAILABLE TO THE PLT THINGS WOULD GO MUCH SMOOTHER. BY THE WAY I HAVE SUGGESTED THIS TO FAA MANY TIMES. THEY DIDN'T BOTHER TO REPLY.

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.