Narrative:

I received a clearance from henderson executive ground control that read (cleared heading 180 degree radar vectors to shead intersection; climb and maintain 6000 ft; expect 14000 ft 10 mins after departure; squawk xbcd; departure control 118.4). Unfortunately; I failed to identify the shead intersection before departing and during the radar vectoring; I could not find it on the las vegas area chart or the en route chart because it was not there. For one thing I had it misspelled. Once I had it spelled properly; I was able to program it into my GPS (KLN89B) and proceed on the assigned route. This caused a lot of clarifying questions with a very busy approach controller. Several of his xmissions were stepped on; requiring me to re-ask for information and spelling of the intersection. It would eliminate a lot of confusion if when clrncs are issued that contain rtes different from what is filed; they contain fixes which are shown on the appropriate en route chart and/or area chart. Shead intersection; while it is contained in the GPS database; is not shown on either the area chart for las vegas or the en route chart. If it had been depicted; I would have easily found it and got the spelling correct. While no violation occurred as I was still on the vector and climbing to the altitude assigned by atcm the controller was not happy with me for having to clarify the route information a couple of times when he was quite busy. In hindsight; I should have received further clarification while on the ground or refuse to accept a clearance that contained an intersection I could not find (I will certainly be diligent to do this in the future); but I also thank ATC should only use intxns that are depicted on the charts.

Related reports:

Google
 

Original NASA ASRS Text

Title: A C182 PLT DEPARTING HND WAS CLRED TO SHEAD INTXN WHICH IS NOT ON LAS VEGAS AREA OR ENRTE CHARTS. IT TOOK SEVERAL CALLS TO THE BUSY DEP CTLR TO DETERMINE SPELLING OF THE FIX.

Narrative: I RECEIVED A CLRNC FROM HENDERSON EXECUTIVE GND CTL THAT READ (CLRED HDG 180 DEG RADAR VECTORS TO SHEAD INTXN; CLB AND MAINTAIN 6000 FT; EXPECT 14000 FT 10 MINS AFTER DEP; SQUAWK XBCD; DEP CTL 118.4). UNFORTUNATELY; I FAILED TO IDENT THE SHEAD INTXN BEFORE DEPARTING AND DURING THE RADAR VECTORING; I COULD NOT FIND IT ON THE LAS VEGAS AREA CHART OR THE ENRTE CHART BECAUSE IT WAS NOT THERE. FOR ONE THING I HAD IT MISSPELLED. ONCE I HAD IT SPELLED PROPERLY; I WAS ABLE TO PROGRAM IT INTO MY GPS (KLN89B) AND PROCEED ON THE ASSIGNED RTE. THIS CAUSED A LOT OF CLARIFYING QUESTIONS WITH A VERY BUSY APCH CTLR. SEVERAL OF HIS XMISSIONS WERE STEPPED ON; REQUIRING ME TO RE-ASK FOR INFO AND SPELLING OF THE INTXN. IT WOULD ELIMINATE A LOT OF CONFUSION IF WHEN CLRNCS ARE ISSUED THAT CONTAIN RTES DIFFERENT FROM WHAT IS FILED; THEY CONTAIN FIXES WHICH ARE SHOWN ON THE APPROPRIATE ENRTE CHART AND/OR AREA CHART. SHEAD INTXN; WHILE IT IS CONTAINED IN THE GPS DATABASE; IS NOT SHOWN ON EITHER THE AREA CHART FOR LAS VEGAS OR THE ENRTE CHART. IF IT HAD BEEN DEPICTED; I WOULD HAVE EASILY FOUND IT AND GOT THE SPELLING CORRECT. WHILE NO VIOLATION OCCURRED AS I WAS STILL ON THE VECTOR AND CLBING TO THE ALT ASSIGNED BY ATCM THE CTLR WAS NOT HAPPY WITH ME FOR HAVING TO CLARIFY THE RTE INFO A COUPLE OF TIMES WHEN HE WAS QUITE BUSY. IN HINDSIGHT; I SHOULD HAVE RECEIVED FURTHER CLARIFICATION WHILE ON THE GND OR REFUSE TO ACCEPT A CLRNC THAT CONTAINED AN INTXN I COULD NOT FIND (I WILL CERTAINLY BE DILIGENT TO DO THIS IN THE FUTURE); BUT I ALSO THANK ATC SHOULD ONLY USE INTXNS THAT ARE DEPICTED ON THE CHARTS.

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.