Skip to content

ASRS 2078297

ACN 2078297 · 2023-08 · EMB ERJ 170/175 ER/LR

ERJ-170 flight crew reported encountering wake turbulence on descent into SDF that resulted in a momentary overspeed.

Wake Turbulence Encounters DescentPart 121

Pilot narratives

Verbatim, de-identified by NASA. Placeholders: ZZZ, X, Y.

Reporter 1

Soon after being handed off to SDF Approach we were assigned a heading and issued a descent from 12,000 to 3,000. We had experienced smooth air throughout the entire descent. While descending through 11,800 in FPA (Flight Path Angle) -2.2 with 310 selected as the airspeed, we encountered moderate wake turbulence for about a minute. The airspeed jumped up and indicated red for a second or less, aural “high speed” was heard twice. My FO (First Officer) noted the speed indicated 318 during the alerts. I took corrective action via idle thrust and speedbrakes. We wrote up the encounter and notified Dispatch and Maintenance once at the gate. I should have slowed earlier in the terminal environment and expected the possibility of a wake encounter given we were arriving during the beginning of the company push.

Reporter 2

In descent on the REDSTONE6 into SDF, Captain had the speed bug set about 310. The flight had been very smooth thus far, not a single complaint of chop or turbulence. At 12,000 ft., we received a clearance down to 3000 ft. Captain set 10,000 in the altitude bug to level at 10, slowdown, and then continue the descent down to 3,000. Shortly after beginning descent, around 11,800 ft., we hit some unexpected wake turbulence and it shot the airspeed up just above the barber pole. As soon as the wake was hit, the Captain pulled the thrust levers to idle and opened the speedbrakes, but it was too late. The highest speed I personally saw was 318 kt., and we received the “HI SPEED” annunciation twice. We were in this condition for roughly one second; maybe just over, maybe just under. Once we recovered, we continued on and completed the flight without further incident. Upon reaching the gate, Dispatch and Maintenance were notified and it was written up. As a side note, I would like to say that I believe the Captain handled this situation well and give props to his reaction time and doing all he could to return us to a safe bank angle and airspeed as quickly as possible from the abrupt wake that caught us both off guard. Flying at such an airspeed can be a gamble, simply bugging 300 instead of 310 could have averted this issue.

NASA classification · Anomalies

  • Deviation - Speed
  • Inflight Event / Encounter

NASA classification · Assessments

Contributing Factors / Situations
Environment - Non Weather Related · Procedure
Primary Problem
Ambiguous

ASRS reports are voluntary, de-identified by NASA, and represent the reporter's perspective; they are not investigated and cannot be used to infer prevalence. Authoritative source: asrs.arc.nasa.gov ↗