Narrative:

While descending with approach I was given a clearance to turn to [a] heading of 110 and descend from 8;000 ft to 4;000 ft. I selected the heading and vs modes and started a descent at the rate of 1;000 fpm. I had received ATIS info [and] had programmed the RNAV approach. As I started the descent; I was cleared direct to an intersection that was not in my legs page and I initially could not find the intersection on the approach chart. As the aircraft descended to around 5;500 ft; the descent rate decreased but due to trying to locate the intersection and enter it into the FMS; I did not notice the descent rate change. As I was asking ATC to verify the fix; I received a traffic alert and when I finished my transmission; ATC was giving me a turn to a heading of 090 for traffic avoidance.my transmission was covering ATC as he was trying to separate the traffic. After leveling off at 4;000 ft I again attempted to enter the fix into the flight plan with no success. After asking for a heading and an altitude to sort out the problem; I discovered the auto sequencing mode had become inhibited. A discontinuity message would not allow me to enter the fix and I could not display it in the map mode. Once this was corrected I was given direct the fix for the approach. This was my first flight in this aircraft and this model of avionics. I have not flown single pilot in many years and the workload; in addition to FMS issues was very distracting. Also; while trying to verify the location of the fix; I was transmitting at the same time ATC was advising of my descent rate decrease.

Related reports:

Google
 

Original NASA ASRS Text

Title: The pilot of a King Air 350 experienced a heading deviation while attempting to program the unfamiliar FMS during an RNAV approach; resulting in a traffic alert.

Narrative: While descending with Approach I was given a clearance to turn to [a] HDG of 110 and descend from 8;000 FT to 4;000 FT. I selected the HDG and VS modes and started a descent at the rate of 1;000 fpm. I had received ATIS Info [and] had programmed the RNAV approach. As I started the descent; I was cleared direct to an intersection that was not in my legs page and I initially could not find the intersection on the approach chart. As the aircraft descended to around 5;500 FT; the descent rate decreased but due to trying to locate the intersection and enter it into the FMS; I did not notice the descent rate change. As I was asking ATC to verify the fix; I received a traffic alert and when I finished my transmission; ATC was giving me a turn to a heading of 090 for traffic avoidance.My transmission was covering ATC as he was trying to separate the traffic. After leveling off at 4;000 FT I again attempted to enter the fix into the flight plan with no success. After asking for a heading and an altitude to sort out the problem; I discovered the auto sequencing mode had become inhibited. A discontinuity message would not allow me to enter the fix and I could not display it in the map mode. Once this was corrected I was given direct the fix for the approach. This was my first flight in this aircraft and this model of avionics. I have not flown single pilot in many years and the workload; in addition to FMS issues was very distracting. Also; while trying to verify the location of the fix; I was transmitting at the same time ATC was advising of my descent rate decrease.

Data retrieved from NASA's ASRS site 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.