Narrative:

While on approach at 1;500ft; we asked the tower to circle due to being about 100lbs over landing weight. They issued a right 360; and then began vectors. Within a minute of the circle; we had a left engine fault light. At this moment; tower asked why we were circling; we said we needed to troubleshoot a light. Ran the checklist and it did not extinguish. Initially the throttle was responsive to inputs but erratic in N1. Still on vectors; we let ATC know we were ready to land and they vectored us back toward the airport. During this approach; we got a right engine fault approximately 10 miles from the field. Shortly after the right engine fault; I noticed the left engine was unresponsive to any thrust changes and stayed at 67.1% N1 despite throttle position. Captain verified. We discussed a plan to cut the engine immediately prior to landing so we did not run off the runway or off the side. We both agreed that we needed its thrust given that the right side was now unreliable and erratic. Somewhere around 5 miles out; we lost the N1 and believe it's indications on the MFDU but still had backups.we took the visual and flew straight to the field. Captain requested a switch to the longer runway; ATC was unable. I was cross controlling the airplane to stay on centerline; then cutoff the left engine approximately 100 feet. Landing was within the landing zone; on centerline; no thrust-reversers were deployed and roll out was uneventful. [I] suggest [pilots] train this scenario in the sim; we improvised quickly.

Related reports:

Google
 

Original NASA ASRS Text

Title: CE-560 First Officer reported that while on approach they had a left engine fault light and then shortly after got a right engine fault light.

Narrative: While on approach at 1;500ft; we asked the tower to circle due to being about 100lbs over landing weight. They issued a right 360; and then began vectors. Within a minute of the circle; we had a left engine fault light. At this moment; Tower asked why we were circling; we said we needed to troubleshoot a light. Ran the checklist and it did not extinguish. Initially the throttle was responsive to inputs but erratic in N1. Still on vectors; we let ATC know we were ready to land and they vectored us back toward the airport. During this approach; we got a right engine fault approximately 10 miles from the field. Shortly after the right engine fault; I noticed the left engine was unresponsive to any thrust changes and stayed at 67.1% N1 despite throttle position. Captain verified. We discussed a plan to cut the engine immediately prior to landing so we did not run off the runway or off the side. We both agreed that we needed its thrust given that the right side was now unreliable and erratic. Somewhere around 5 miles out; we lost the N1 and believe it's indications on the MFDU but still had backups.We took the visual and flew straight to the field. Captain requested a switch to the longer runway; ATC was unable. I was cross controlling the airplane to stay on centerline; then cutoff the left engine approximately 100 feet. Landing was within the landing zone; on centerline; no thrust-reversers were deployed and roll out was uneventful. [I] suggest [pilots] train this scenario in the sim; we improvised quickly.

Data retrieved from NASA's ASRS site 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.