CL-350 flight crew reported hearing loud bangs and feeling aircraft vibration just after takeoff. Flight crew returned to departure airport and determined the right engine had experienced a surge.
Synopsis
CL-350 flight crew reported hearing loud bangs and feeling aircraft vibration just after takeoff. Flight crew returned to departure airport and determined the right engine had experienced a surge.
Narrative
Right seat- pilot flying/Left seat- pilot monitoring. During takeoff Runway XX; shortly after becoming airborne at approximately 10-30' off the ground; we heard a series of loud bangs on the left side of the aircraft. Unsure what was the cause; we elected to keep the landing gear down in case it was a blown tire and tire debris hitting the side of the aircraft. As the pilot monitoring; I did not see any deviation in the engine instrument display. We continued our climb to 2000' MSL and communicated with tower what had happened. We told them we wanted to orbit over the airfield while we worked through the problem. Still thinking it was a landing gear or tire issue; we made two passes near the tower so they could look for any damage to the aircraft. They said they saw no indication of tire failure or problems with the landing gear. We also had the airport check the runway for any debris. They stated there was no debris on or off the runway. Tower informed us that an individual heard the loud bangs during our takeoff and thought it was an engine compressor stall. We attempted to contact the company; but were unable. We discussed possibly diverting to a different airport with a longer runway. We decided if it was an engine problem diverting to a different airport was not a good idea. Landing back at our departure airport was the best option. At that time; [requested priority handling] and set up for the RNAV(GPS) Runway XX approach to land. On landing there were no issues. Pilot flying used minimum braking to slow the aircraft. I took control of the aircraft at about 40 kts and came to stop on the runway. We had Crash and Rescue personnel inspect the aircraft. They informed us there was no damage. We decided to leave the flaps fully extended until we could verify there was no damage or issues with the flaps. We taxied to the ramp. After shutdown; we completed a detailed inspection of the aircraft. No damage was found. Intakes and exhaust of both engines appeared normal. In review of the Aircraft Maintenance Service message history; R Engine Notice XX-XXXXX RIGHT ENGINE UNEXPECTED SURGE was present. We believe the right engine surge was a result of the left engine compressor stall. We contacted the CL350S program supervisor; aircraft maintenance; and the Chief Pilot as soon as possible.Suggestions: Conduct compressor stall training in the simulator as part of the annual training cycle.
Second reporter narrative
Winds 010-10 knots 10 SM ClearTemp 27 C Dew Point 14 Alt 30.12 No passengers (ferry leg from ZZZ - ZZZ1) A few seconds after rotation there was a series of loud consecutive pops" followed by an aircraft shutter/vibration. Crew proceeded upwind on runway heading and leveled at 2;000 ft. Once stable; entered into an extended traffic pattern to troubleshoot and began QRC and QRH search for any "blown tire" or "compressor stall" non EICAS related procedure since it was determined these where the two most likely causes. (Landing gear was left down and locked in case it was a blown tire or other gear related issue) Crew did several "fly over passes" to allow tower to observe the gear thru binoculars. Also; the crew requested a full runway inspection to check for any FOD or tire shreds. (No issues or debris observed) After this there was extensive discussion and decision about landing at the most suitable airport. Additionally; crew tried to contact the company but unable to reach. Tower also reported that someone in the vicinity of our departure reported what sounded like a compressor stall coming from our aircraft during our rotation. Crew decided; after adequate fuel burn; to land back at departure airport on the longest runway available. (Runway XX- 9002 ft long) We [requested priority handling] and fire/crash rescue placed on standby. Crew made landing without further incident and with no brakes applied as a precaution. Once on runway; the fire team did their inspection and cleared us to return back to parking. Upon shutdown we were able to review the fault messages which revealed a right engine unexpected engine surge. (ATA 71-00 Powerplant)Also immediately contacted CL350 program supervisor and maintenance after shutdown.Suggestions: Suggest review if any non EICAS procedure/guidance is warranted in QRC or QRH for "Blown tire" or "Compressor Stall""
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.