Date: 201403
Local time of day: 0601-1200
Location: FAT.TRACON, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna Citation Mustang (C510)
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class C FAT
ATC / advisory: Ground FAT; TRACON FAT; Tower FAT
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Corporate
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Multiengine
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors; Airspace Structure; Chart Or Publication; Procedure
Primary problem: Human Factors

Narrative: I filed a flight plan from FAT to SMF using an online flight planning service. I picked up the clearance from FAT clearance delivery and they cleared me via runway heading; (off Runway 29L); LINDN; SAC VOR; direct; maintain 10;000. I repeated the clearance and delivery confirmed readback was correct. I entered the clearance into the Garmin G1000 FMS. Upon routing inspection on the map; it showed LINDN to be south of FAT; and then a northerly V turn back to SAC. This looked odd so I called Ground frequency prior to taxi to request clarification that this was actually clearance's intention. Ground asked me to standby as they checked with clearance and then called back on the radio to say that this was; indeed; the preferred clearance; down to LINDN and back to SAC. This looked strange to me visually so I asked if after departure I would be then vectored back on course. Ground replied in the affirmative. I taxied out and; once airborne; Tower handed me off to Departure. Departure restricted my climb to 4;000 feet and cleared me direct to LINDN. After I punched in direct to LINDN the aircraft initiated a turn to the left to head direct to LINDN. At this point the Controller asked me where I was going and I replied that as per instructions the aircraft was going direct to LINDN. The Controller asked me to immediately turn right to a northwesterly heading and level off at 10;000; which I promptly did. After leveling off the Controller asked me to proceed directly again to LINDN. At this point I asked the Controller to repeat the identifier for the intended checkpoint; and he spelled out LIN. At this point; it became clear that there are two points with the same sounding name within the vicinity of Fresno on opposite sides; so I cleared LINDN out and punched in LIN and proceeded on course direct to LIN. The flight was subsequently uneventful. Upon landing I contacted Fresno Tower and Fresno FSDO to provide them with the necessary pilot information.




Synopsis: A Citation pilot departing on a flight from FAT to SMF understood his clearance to depart Runway 29L at FAT; proceed direct LINDN; direct SAC; direct.  After takeoff when; to Departure's surprise; he started the sharp left turn direct to LINDN intersection; 200NM south of FAT; Departure and the reporter realized the intended fix pronounced 'linden' was the LIN VOR 100NM north of FAT well on the way to his destination; not the airways fix LINDN just north of Los Angeles.