Date: 202003
Local time of day: 0601-1200
Location: GYR.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operating under: Part 91
Flight plan: IFR
Flight phase: Climb
Airspace: Class E ZAB
ATC / advisory: TRACON P50
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Communication Breakdown; Confusion; Situational Awareness
Second reporter function: Pilot Flying; Captain
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Manuals; Chart Or Publication; Human Factors; Procedure
Primary problem: Chart Or Publication

Narrative: Ground Control at GYR gave a clearance of PODER3.RUPOY; radar vectors; 'Drake'; INW; (Saint John) SJN; [...] as filed. PNF (Pilot Not Flying) asked for further clarification/spelling of the Saint John fix which they replied as SJN. Read back clearance. Then read back; reviewed and confirmed routing with PF (Pilot Flying) the flight plan in MCDU (Multipurpose Control Display Unit) before engine start.  Upon initial climb out and level off at 5;000 ft we were given a right turn towards DRAKE which was in the direction of flight to ZZZ. ATC asked if we were turning direct DRAKE which we replied yes.  At this time we asked for the spelling of DRAKE and he replied it was a VOR with the identifier of DRK. We had asked if we could proceed towards INW which ATC replied unable. They asked us to ident and turn to a heading of north which we complied with immediately. PF queried ATC stating we had a fix named DRAKE in the direction of flight that was mistakenly entered.  After a vector of north we were then told to proceed direct to rest of route; unchanged. No further action necessary. Better clarification from clearance or ground on SID (Standard Instrument Departure) departure to a VOR fix that is not depicted on the chart. Especially when the VOR name could be mistaken as a waypoint fix being it has the correct number of characters and is in the direction of flight. Suggest that the DRK VOR be listed as a possible radar vector fix on the POTER3 departure chart. Full route clearance instructions with spellings of fixes should be provided in every verbal clearance moving forward especially departing from an unfamiliar airport.


Second narrative: Crew received a clearance from GYR Ground to fly the POTER3 Departure radar vectors DRK. After departure; and flying the departure procedure the crew was given a radar vector to turn right direct DRK. The SIC (Second In Command) who loading the FMS misinterpreted the intersection DRAKE with the VOR spelled DRK also known as DRAKE. The DRAKE intersection was in our direction of flight; so it looked normal. After we were off course for a few seconds ATC gave us a heading of north to avoid other airspace. We received the correct spelling of the fix and proceed without further incident. Properly review map to check routing. If I expanded the map out to 200 miles I would have seen the course reversal and assumed something was wrong. The intersection DRAKE is in Colorado.


Synopsis: Flight Crew reports confusion with intersection naming same as navaid.