Date: 201211
Local time of day: 1201-1800
Location: ZLC.ARTCC, UT
Flight conditions: IMC
Weather elements / visibility: Icing; Rain; Turbulence; Snow; 6
Light: Dusk
Aircraft: Small Transport; Low Wing; 2 Turbojet Eng
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Approach
Airspace: Class E ZLC
ATC / advisory: Center ZLC
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Confusion; Training / Qualification; Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Became Reoriented
Contributing factors: Equipment / Tooling; Human Factors; Procedure; Weather
Primary problem: Human Factors

Narrative: I set up an approach in the recently installed IFMS system. The approach was input for the ILS 20 at CDC using MEGGI as the IAF. For some reason the IFMS system was anticipating a steep turn for the outbound leg of the approach. The Center Controller commented that it was showing south [me] of course; which I acknowledged. He continued to press me on the variance to direct. I acknowledged that I was seeing the same thing and finally just asked him to cancel that approach and take me to MLF (Milford) for the Milford Transition to the ILS. That is when the problems got bad; I could not get the previous inserted approach out of the IFMS system to input a new one. It was not allowing me to remove the old (I am sure it is my lack of experience with the 'button-ology'). The Controller was frustrated as was I; so I finally asked for Vectors to MLF. He continued to tell me how far off course I was; and asking if I was navigating to MLF. I told him I was trying. I continued to ask for vectors and the Controller continued to tell me how far my variance was to the correct course. Our communication was not working well. In the end I arrived at MLF and made the turn back to the 154 to VELDE; again requesting vectors. The Controller continued to give me my variance; but never once (to my memory) gave me a vector to my needed waypoint. I finally arrived at VELDE and began the approach; when the Controller told me to break off the approach and climb to 14;000 FT. I declined. I had used up much of my reserve in the process of finding my way to MLF and back to VELDE. I told him I was low on fuel and was going to make the approach. He then cleared me for the approach and I successfully flew the approach under less than ideal conditions. I experienced ice; turbulence; and 35 KTS gusting winds.My error was not knowing the IFMS system as well as I should have. I did not know how to get rid of the incorrect information on the screen and in the system to re-input the correct information. My only complaint was the Controller's lack of willingness to give vectors as requested. I have only had one other situation when I needed the 'urgent help' of a controller. A Center Controller calmly talked me through a bad case of vertigo. He saved my life. This Controller was less than empathetic or helpful.




Synopsis: Pilot of a small jet experienced course deviations on the ILS2 Approach to CDC due to unfamiliarity with a newly installed IFMS system and apparent lack of assistance from ATC.