Narrative:

Aircraft departed on time. Weather was VFR 3 knot winds out of the southwest. We taxied out to runway 23 for departure. All aircraft indications were normal and in the green. We were cleared for takeoff. The captain called set thrust. Thrust was set and everything appeared normal on the gauges. I noticed a noise I have not heard before but I thought it might be noise from the runway or possibly bearings in the nose wheel. As the speed increased I glanced down at the N2 vibe and noticed that it was higher than it had been on previous legs but it was not indicating in the yellow arc. The indications were still in the normal range. My eyes darted up to the EICAS and noticed it had unboxed and right fadec fault 2 was now posted but it was after 80kts and it is a white advisory message. Because I was scanning carefully to see if I could determine the source of the noise; I missed my 80kts call and the captain said 80kts as I was saying 100kts. V1 and vr were about 134kts.after we rotated and were climbing out initially; the noise became a rumble the captain asked if I heard that noise. I said yes. We looked at the instruments. The N2 vibe was now in the yellow arc and climbing slowly. I think it had been only 2 or 3 seconds after rotation and I had just put the gear up. We continued climbing. I said 'we need to shut the engine down.' about that time we got a smoke aft lav message and a flight attendant call. The captain told me to answer the call. The flight attendant reported smoke in the cabin. I told her we were returning to the airport immediately. I started to run the smoke aft lav checklist and noticed the engine vibe was very high and the itt on the right engine had just turned red. The captain instructed me to run the engine fire/severe engine damage checklist. The captain pulled the right engine back to idle. I pulled out the immediate action items card and we shut down the right engine. We followed the QRH procedure which concluded with the single engine procedures checklist. We planned to land overweight.as I was reading the checklist the captain received vectors back to the airport to land on runway 5. The captain notified the flight attendants that it would be a normal landing. We touched down in the beginning of the touchdown zone and exited the runway before the end. As we taxied to the gate; the firetrucks followed and didn't see any outward indications of a fire. When we parked; the firemen came onboard and checked the aft lav for fire indications. No fire indications were found. The captain spoke with them and they departed. We deplaned and I conducted a post flight walk around. I saw no outward indications of a fire; no indications of a bird strike or any other abnormality. The threats during the event were smoke aft lav; smoke reported in the cabin and possible severe engine damage. I missed the 80kts call because I was trying to figure out where the strange noise was coming from. I was really thinking it must be the runway surface. I see the N2 vibration all the time so that didn't concern me much. The right fadec fault 2 advisory started a concern in the back of my mind; but we were already past 80kts when it came to my attention. The right fadec fault 2 is a white advisory message.

Related reports:

Google
 

Original NASA ASRS Text

Title: A CRJ-700 engine was shut down shortly after takeoff because of a high engine vibration and the cabin smoke.

Narrative: Aircraft departed on time. Weather was VFR 3 knot winds out of the southwest. We taxied out to runway 23 for departure. All aircraft indications were normal and in the green. We were cleared for takeoff. The Captain called set thrust. Thrust was set and everything appeared normal on the gauges. I noticed a noise I have not heard before but I thought it might be noise from the runway or possibly bearings in the nose wheel. As the speed increased I glanced down at the N2 vibe and noticed that it was higher than it had been on previous legs but it was not indicating in the yellow arc. The indications were still in the normal range. My eyes darted up to the EICAS and noticed it had unboxed and R FADEC FAULT 2 was now posted but it was after 80kts and it is a white advisory message. Because I was scanning carefully to see if I could determine the source of the noise; I missed my 80kts call and the captain said 80kts as I was saying 100kts. V1 and VR were about 134kts.After we rotated and were climbing out initially; the noise became a rumble the Captain asked if I heard that noise. I said yes. We looked at the instruments. The N2 vibe was now in the yellow arc and climbing slowly. I think it had been only 2 or 3 seconds after rotation and I had just put the gear up. We continued climbing. I said 'we need to shut the engine down.' About that time we got a SMOKE AFT LAV message and a flight attendant call. The Captain told me to answer the call. The flight attendant reported smoke in the cabin. I told her we were returning to the airport immediately. I started to run the SMOKE AFT LAV checklist and noticed the engine vibe was very high and the ITT on the right engine had just turned red. The Captain instructed me to run the Engine Fire/Severe Engine damage checklist. The Captain pulled the right engine back to idle. I pulled out the immediate action items card and we shut down the right engine. We followed the QRH procedure which concluded with the Single Engine Procedures checklist. We planned to land overweight.As I was reading the checklist the Captain received vectors back to the airport to land on Runway 5. The Captain notified the flight attendants that it would be a normal landing. We touched down in the beginning of the touchdown zone and exited the runway before the end. As we taxied to the gate; the firetrucks followed and didn't see any outward indications of a fire. When we parked; the firemen came onboard and checked the AFT LAV for fire indications. No fire indications were found. The Captain spoke with them and they departed. We deplaned and I conducted a post flight walk around. I saw no outward indications of a fire; no indications of a bird strike or any other abnormality. The threats during the event were SMOKE AFT LAV; smoke reported in the cabin and possible severe engine damage. I missed the 80kts call because I was trying to figure out where the strange noise was coming from. I was really thinking it must be the runway surface. I see the N2 vibration all the time so that didn't concern me much. The R FADEC FAULT 2 advisory started a concern in the back of my mind; but we were already past 80kts when it came to my attention. The R FADEC FAULT 2 is a white advisory message.

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.