Challenger 350 First Officer reported engine failure during climbout resulting in a return to the departure airport.
Synopsis
Challenger 350 First Officer reported engine failure during climbout resulting in a return to the departure airport.
Narrative
On takeoff at approximately 800-1000 ft AGL; the aircraft began to shake violently. I was the PF and initially thought it may have been a flight control issue because the yoke was shaking from the vibrations. The PM (PIC) said we had an engine failure; but by the time I looked at the EICAS the engine had recovered and I was not clear what he was talking about. As we leveled at 2000 ft; there was another violent shake of the entire aircraft and we both saw the right engine N1 down at 20%; which again recovered quickly once the power was reduced. The PIC/PM immediately requested priority handling with ATC on initial check in. We accepted delay vectors while we set up for an overweight landing back to ZZZ. We both agreed to keep the engine on for the time being (low altitude/low airspeed (~200kts)) as it was producing thrust; and agreed not to wait to burn off fuel and get on the ground. We flew an RNAV approach to RWY XX at ZZZ; landed without issue and returned to the FBO. Detected with significant aircraft vibration and EICAS indications.Cause unknown; but two engine compressor stalls/surges suspected.Advised ATC; prepared for landing; returned to departure field. Suggestions: Crew reacted appropriately; with professionalism and poise per training. No additional suggestions to offer.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.