Date: 201407
Local time of day: 1201-1800
Location: IAD.Airport, DC
Flight conditions: VMC
Light: Daylight
Aircraft: Gulfstream IV / G350 / G450
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZDC
ATC / advisory: Center ZDC
Aircraft component: FMS/FMC
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Confusion; Distraction; Human-Machine Interface; Workload
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Contributing factors: Procedure; Aircraft
Primary problem: Aircraft

Narrative: Cleared to descend via GIBBZ 2 STAR into IAD. At about FL240 FMS and VNAV were confirmed armed for descent with altitude preselect dialed down to 7;000 FT. Watched profile and waited for VNAV bug in PFD; but did not appear. Rechecked FMS programming and confirmed correct. Still no vertical VNAV bug on PFD. Started descent via VS to stay on profile. Then selected direct to next crossing altitude; then FGC fail - FGC 1 failed then auto reverted to FGC 2. About 15 seconds later; FGC 2 failed. About 17;000 FT; requested ATC radar vectors off of STAR to [run] checklist and address issue while continuing descent. During level off; descended about 300 FT low to about 6;700 FT very briefly while assessing current status before getting established back at 7;000 FT. PM PFD displayed different crossing altitudes and began to display vertical descent bug.When FGC's failed; we lost autopilot; auto throttles; FGC panel functions. Per checklist; reset by pulling FGC breakers for about 15 seconds each and reset. Normal operations afterward. During assessment of initial situation; we were continuing on STAR profile until we decided we would not be able to properly meet the profile speed and altitude restrictions while assessing and running the checklist. It is possible that we may not have been exactly on the crossings up to the point of asking for vectors off the STAR to run the checklist; however I believe we met them.We now believe there may have been a possible disagreement between the FMS's that the FGC's could not resolve which may have triggered the FGC's failing. No further issues have been seen during the following flights. In the future; if a similar event were to occur; I will suggest immediately removing ourselves from the STAR and away from the traffic flow instead of continuing for a while on the STAR. There were no traffic conflicts or communication from ATC regarding any missed altitudes or airspeeds. Vectored to ILS visual 19C for VFR landing in VMC conditions.




Synopsis: A GIV crew experienced dual Flight Guidance Computer (FGC) failures during an RNAV arrival; but reset them while completing with reset checklist. A suspected unresolved disagreement between FMS's caused the FGC shutdown.