37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1420247 |
Time | |
Date | 201701 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ATL.Airport |
State Reference | GA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B717 (Formerly MD-95) |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Inflight Event / Encounter Wake Vortex Encounter |
Narrative:
We were on the downwind abeam the approach end of runway 28 descending through 7000 at 210 kts with thrust levers at idle and spoilers out. The captain was looking out the window trying to locate the traffic we were following. At this time we experienced an unexpected pocket of wake turbulence that caused a momentary stick shaker; autopilot disconnect and approximately 15 degree bank to the right. I immediately recovered the aircraft to wings leveled and the total event; from start to finish was a few seconds. The event was resolved so quickly that the captain was unaware of what transpired until I told him (he thought I disconnected the autopilot due to the wake turbulence). The captain then queried ATC on what type of aircraft we were following. It was a 717 on the base leg to the visual for runway 27L (a parallel runway) that was approximately 10 miles away and three thousand feet lower than us. I then reduced my descent rate and no other wake turbulence was experienced and no other issues occurred during the duration of the flight.the threat was the undesired aircraft state caused by the wake turbulence. The best thing we can do as a crew is be aware that wake turbulence can occur even when you have adequate altitude and distance separation.
Original NASA ASRS Text
Title: CRJ-200 First Officer reported encountering wake turbulence while on approach to ATL airport behind a B717 inbound to a parallel runway.
Narrative: We were on the downwind abeam the approach end of Runway 28 descending through 7000 at 210 kts with thrust levers at idle and spoilers out. The Captain was looking out the window trying to locate the traffic we were following. At this time we experienced an unexpected pocket of wake turbulence that caused a momentary stick shaker; autopilot disconnect and approximately 15 degree bank to the right. I immediately recovered the aircraft to wings leveled and the total event; from start to finish was a few seconds. The event was resolved so quickly that the Captain was unaware of what transpired until I told him (He thought I disconnected the autopilot due to the wake turbulence). The Captain then queried ATC on what type of aircraft we were following. It was a 717 on the base leg to the visual for Runway 27L (a parallel runway) that was approximately 10 miles away and three thousand feet lower than us. I then reduced my descent rate and no other wake turbulence was experienced and no other issues occurred during the duration of the flight.The threat was the undesired aircraft state caused by the wake turbulence. The best thing we can do as a crew is be aware that wake turbulence can occur even when you have adequate altitude and distance separation.
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.