Narrative:

The ruudy two departure was programmed in the UNS1 FMS. I selected navigation on the flight director on the runway to follow the departure procedure. After departure the V bars continued to show runway heading instead of the departure route. When we contacted departure they gave us a turn and climb and asked what departure we were using. We responded with the ruudy two but got no indication for the turn point. As far as I know there were no conflicts with other traffic and the rest of the flight was normal.there are several factors that caused this issue. The first is the flight crew's inexperience with this particular aircraft/avionics combination. My co-captain and I had a total of 4 flights in this north number between us. As chief pilot I requested that we not be paired together until I had 100 hours PIC (pilot in command) in the hs-125-800 because we both were typed early this year. The company is not staffed adequately to even consider it. I have 40 hours PIC and 110 hours total in the hawker. The next contributing issue is training. Avionics training takes a back seat to checking all of the necessary boxes to get through a part 135 check ride. If we could do progressive checks we would have time to do more training on systems and avionics. Avionics training is almost non-existent at training facilities. There just is not enough time for it in the four or five days recurrent training every six months and each operator in the class is running a different avionics package. Another factor is that I am required to fly six different airframes of two different type certificates all of the time. I fly three different hawker models; all with different avionics suites under the hs-125 type rating. I also fly three different citation models under my citation type rating. These aircraft also all have different avionics packages. Errors in programming will happen.

Google
 

Original NASA ASRS Text

Title: An air taxi flight crew aboard an HS125-800SP suffered a track deviation on the RUUDY SID from TEB. Cite lack of familiarity with the avionics due to inexperience and cross qualification on six different aircraft; each with unique avionics systems.

Narrative: The RUUDY TWO departure was programmed in the UNS1 FMS. I selected NAV on the Flight Director on the runway to follow the departure procedure. After departure the V bars continued to show runway heading instead of the departure route. When we contacted Departure they gave us a turn and climb and asked what departure we were using. We responded with the RUUDY TWO but got no indication for the turn point. As far as I know there were no conflicts with other traffic and the rest of the flight was normal.There are several factors that caused this issue. The first is the flight crew's inexperience with this particular aircraft/avionics combination. My Co-Captain and I had a total of 4 flights in this N number between us. As Chief Pilot I requested that we not be paired together until I had 100 hours PIC (pilot in command) in the HS-125-800 because we both were typed early this year. The company is not staffed adequately to even consider it. I have 40 hours PIC and 110 hours total in the Hawker. The next contributing issue is training. Avionics training takes a back seat to checking all of the necessary boxes to get through a Part 135 check ride. If we could do progressive checks we would have time to do more training on systems and avionics. Avionics training is almost non-existent at training facilities. There just is not enough time for it in the four or five days recurrent training every six months and each operator in the class is running a different avionics package. Another factor is that I am required to fly six different airframes of two different type certificates all of the time. I fly three different Hawker models; all with different avionics suites under the HS-125 Type rating. I also fly three different Citation models under my Citation Type rating. These aircraft also all have different avionics packages. Errors in programming WILL happen.

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