A g-v had a power surge which caused the FMS's to shift into the single operation mode but no cas al...

Narrative:

Upon receiving clearance on the ground; clearance gave us our SID. Myself as the captain entered this into the FMS with the first officer confirming it. Tower cleared us for departure with an initial heading of 095. Upon climbing through 13;000 MSL we had a quick electrical bus transfer which caused our FMS to go into single operation and the auto throttle disengaged. The first officer verified it was a power surge and that all other operations were normal. We never received any other cas messages and the ones that where displayed cleared before we could verify what they were. While evaluating the situation; center cleared us to join the departure. The first officer sequenced the FMS '2' with next two waypoints. Five miles from first waypoint we where given a climb to FL230. We started our climb with LNAV on FMS 1. Upon leveling at FL230 ATC gave us traffic at our one o'clock which we acknowledged. At this point ATC asked us if we were proceeding to the following waypoint. At this point I realized that FMS 1 was on single operation and was in command of the flight director and was not receiving data from FMS 2; which had the correct route. FMS 1 sequenced to a waypoint on the airway further out. We placed the FMS in to 'dual mode' and the FMS sequence to the cleared point. After landing with no other aircraft discrepancies; I called center and they verified our navigation error and were told they did not lose aircraft separation. During our debrief the crew discussed the distraction that caused our error. Our conclusion to avoid an incident such as this is to immediately verify route in all FMS's in a prompt manner. We will also notify ATC if any discrepancies are found to verify appropriate route. In closing I would like to add; from the time of the anomaly to the time of the navigation error was a very short amount of time.

Original NASA ASRS Text

Title: A G-V had a power surge which caused the FMS's to shift into the single operation mode but no CAS alert was issued. The crew failed to notice until a track deviation occurred and ATC cleared them on the departure routing.

Narrative: Upon receiving clearance on the ground; Clearance gave us our SID. Myself as the Captain entered this into the FMS with the First Officer confirming it. Tower cleared us for departure with an initial heading of 095. Upon climbing through 13;000 MSL we had a quick electrical bus transfer which caused our FMS to go into single operation and the auto throttle disengaged. The First Officer verified it was a power surge and that all other operations were normal. We never received any other CAS messages and the ones that where displayed cleared before we could verify what they were. While evaluating the situation; Center cleared us to join the departure. The First Officer sequenced the FMS '2' with next two waypoints. Five miles from first waypoint we where given a climb to FL230. We started our climb with LNAV on FMS 1. Upon leveling at FL230 ATC gave us traffic at our one o'clock which we acknowledged. At this point ATC asked us if we were proceeding to the following waypoint. At this point I realized that FMS 1 was on single operation and was in command of the Flight Director and was not receiving data from FMS 2; which had the correct route. FMS 1 sequenced to a waypoint on the airway further out. We placed the FMS in to 'dual mode' and the FMS sequence to the cleared point. After landing with no other aircraft discrepancies; I called Center and they verified our navigation error and were told they did not lose aircraft separation. During our debrief the crew discussed the distraction that caused our error. Our conclusion to avoid an incident such as this is to immediately verify route in all FMS's in a prompt manner. We will also notify ATC if any discrepancies are found to verify appropriate route. In closing I would like to add; from the time of the anomaly to the time of the navigation error was a very short amount of time.

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.

Attributes
ACN	925957
Time
Date	201101
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.ARTCC
State Reference	US
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Make Model Name	Gulfstream V / G500 / G550
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Captain Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 48 Flight Crew Total 8200 Flight Crew Type 275
Events
Anomaly	Aircraft Equipment Problem Critical Deviation - Procedural Clearance Deviation - Track / Heading All Types

A g-v had a power surge which caused the FMS's to shift into the single operation mode but no cas alert was issued. The crew failed to notice until a track deviation occurred and ATC cleared them on the departure routing.