Narrative:

We departed runway 27 at san. Our departure required us to proceed to jetti intersection and then continue on the departure. I was the non-flying pilot and noticed we were making a slight right turn taking us off course and I so advised the flying pilot. We then realized our command bars were giving us different indications. At this time the controller asked what heading we were on. I replied that we were on a 305 heading. She gave us a 275 heading and told us to go direct pgy VOR. By this time we had already transferred the autopilot back to the left side and determined the right side was giving us erroneous information. We had been cleared to FL410 but upon reaching FL270 we let the new controller know we were having issues with one of our navigation systems and requested FL290 until we determined we were legal to enter rvsm airspace. We later notified the controller we were able to continue our climb. Either that controller or the next advised us to call TRACON and told us it was for a deviation. The rest of the flight was uneventful and later on into the flight the systems seemed to be working.in the departure phase of this flight; everything was happening very quickly. Trying to determine the faulty side and making the proper adjustment to correct the deviation took some time. As soon as we noticed the erroneous indications of the instruments; we should have asked for a heading and then worked on finding a solution to our situation.

Google
 

Original NASA ASRS Text

Title: When the pilot flying's FMS provided erroneous guidance during the BE-400's departure from SAN; the flight crew switched roles and utilized the Captain's side avionics to complete their journey. ATC suggested the possibility of a deviation during their departure but none had been issued at the time of their submission.

Narrative: We departed Runway 27 at SAN. Our departure required us to proceed to JETTI Intersection and then continue on the departure. I was the non-flying pilot and noticed we were making a slight right turn taking us off course and I so advised the flying pilot. We then realized our command bars were giving us different indications. At this time the Controller asked what heading we were on. I replied that we were on a 305 heading. She gave us a 275 heading and told us to go direct PGY VOR. By this time we had already transferred the autopilot back to the left side and determined the right side was giving us erroneous information. We had been cleared to FL410 but upon reaching FL270 we let the new Controller know we were having issues with one of our navigation systems and requested FL290 until we determined we were legal to enter RVSM airspace. We later notified the Controller we were able to continue our climb. Either that Controller or the next advised us to call TRACON and told us it was for a deviation. The rest of the flight was uneventful and later on into the flight the systems seemed to be working.In the departure phase of this flight; everything was happening very quickly. Trying to determine the faulty side and making the proper adjustment to correct the deviation took some time. As soon as we noticed the erroneous indications of the instruments; we should have asked for a heading and then worked on finding a solution to our situation.

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