Narrative:

Narrative:we were cleared to line up and wait runway 24L at cle as the preceding E170 began its takeoff roll. Just as it [became] airborne; cle tower cleared us for takeoff. As we accelerated down the runway; I commented that the spacing looked a little tight as the E170 could be seen climbing down range; still aligned with the runway. Our rotation and initial climb on the CAVVS2 SID was normal. As we climbed through approximately 2;500 feet MSL and began the left turn towards kyrie (206 heading); we experienced a significant wake turbulence event. The aircraft rolled left about 25 degrees in 1 second; our rate of climb was temporarily reduced; and we ended up left of course. We offset to the left for a few miles without incident and then proceeded to kyrie and resumed the departure. Several attempts were made to ATC to advise of the presumed encounter with the wake turbulence from the preceding E170 traffic.probable cause:the E170 was flying the gtlke SID. Both the cavvs and gtlke sids share the same initial course before the gtlke proceeds west and the cavvs south-southwest. I was informed by the ATC supervisor I spoke with at cle approach that spacing was legal (6;000 feet and preceding traffic airborne) for our departure. Weather conditions appear to have been favorable (light or no winds) for the wake turbulence to remain along the shared flight path between the 2 sids.possible solution:we could have asked for a delay on the runway prior to departing; however; cle was in a single runway operation at the time so that may have been limited. Attempting to out-climb the preceding traffic to avoid the wake turbulence (we tried; but were close to max takeoff weight due to fuel onboard for a long flight).

Related reports:

Google
 

Original NASA ASRS Text

Title: Beechjet 400 First Officer reported a track deviation occurred departing CLE after encountering wake turbulence from preceding EMB-170.

Narrative: Narrative:We were cleared to line up and wait Runway 24L at CLE as the preceding E170 began its takeoff roll. Just as it [became] airborne; CLE Tower cleared us for takeoff. As we accelerated down the runway; I commented that the spacing looked a little tight as the E170 could be seen climbing down range; still aligned with the runway. Our rotation and initial climb on the CAVVS2 SID was normal. As we climbed through approximately 2;500 feet MSL and began the left turn towards KYRIE (206 heading); we experienced a significant wake turbulence event. The aircraft rolled left about 25 degrees in 1 second; our rate of climb was temporarily reduced; and we ended up left of course. We offset to the left for a few miles without incident and then proceeded to KYRIE and resumed the departure. Several attempts were made to ATC to advise of the presumed encounter with the wake turbulence from the preceding E170 traffic.Probable Cause:The E170 was flying the GTLKE SID. Both the CAVVS and GTLKE SIDs share the same initial course before the GTLKE proceeds west and the CAVVS south-southwest. I was informed by the ATC Supervisor I spoke with at CLE Approach that spacing was legal (6;000 feet and preceding traffic airborne) for our departure. Weather conditions appear to have been favorable (light or no winds) for the wake turbulence to remain along the shared flight path between the 2 SIDs.Possible Solution:We could have asked for a delay on the runway prior to departing; however; CLE was in a single runway operation at the time so that may have been limited. Attempting to out-climb the preceding traffic to avoid the wake turbulence (we tried; but were close to max takeoff weight due to fuel onboard for a long flight).

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.