Date: 201703
Local time of day: 1801-2400
Location: ZZZZ.ARTCC, FO
Light: Night
Aircraft: Gulfstream G200 (IAI 1126 Galaxy)
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZZ
Aircraft component: Air/Ground Communication
Component problem: Failed
Reporter organization: Personal
Reporter function: Other / Unknown
Human factors: Confusion; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Last night while 1 hour 40 minutes from [our destination] we got a series of EICAS messages that didn't at all seem connected. I placed a phone call to Tech Ops to try to track down the issue. They assured me it sounded like just indication issues and that it shouldn't be a problem. We continued our flight. About 30 minutes later (about 1 hour from [our destination]) we heard 2 beeps on the radio followed by what sounded almost like a tesla coil noise. I heard ATC try to contact us; we could not transmit back. Instead; we squawked ident. ATC asked us to Squawk Ident again if we could hear them; and we complied. 2 minutes later; the radios went down completely; we could only hear every 3rd word or so if anything so we squawked 7600 followed by 7700. I tried reaching ATC on HF as well; but was unsuccessful.At some point; I called [someone] I know from the Sat phone who is an Air Traffic Controller at [the destination airport] to see if she could put me in touch with Approach via phone. Later approach called me while in holding for the approach.There were other; smaller things happening in the aircraft that made us worry that we could lose more systems as time progressed. I will leave those out as they have no relevance on what ATC saw; however MX has been notified of these issues as well.We were not assigned an arrival at this point; so we continued on to our last fix. Afterword; we entered holding and descended in the hold. It was at this point that Approach reached us via the Sat phone; we informed them of our status and our intention to shoot the ILS approach after holding was complete. They agreed. Upon getting to a safe altitude to begin the approach from; we began to try to configure the aircraft. This is when we realized that the flaps did not; in fact work. We re-entered holding to trouble shoot this issue. ATC; in return called to ask us for our intentions. I explained to them that we were having another issue with our flaps and they asked us if we could take a vector on the phone so that they could get Aircraft in to [the airport] while we ran our checklist. We complied. They took us away from the approach and asked us to orbit while we worked the issue and to keep them on the line. I asked them to have ARFF standing by (due to the no-flap situation) as well as a 'follow me' car once we land. After running the checklist we informed them that we were ready to attempt the approach. We then made an uneventful no-flap approach and landing.




Synopsis: G200 Safety Manager reported communications failure in flight following a series of EICAS messages that seemed unrelated. When begining the approach; the flaps would not extend and a no flap landing ensued; using a cell phone for ATC communications.