37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1399829 |
Time | |
Date | 201611 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | LAX.Airport |
State Reference | CA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | EMB ERJ 170/175 ER/LR |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Inflight Event / Encounter Wake Vortex Encounter |
Narrative:
On an empty repositioning flight (part 91) to lax we experienced wake turbulence which caused 20 degrees of bank at about 2100 feet AGL. There was only me and the first officer onboard the plane. We had a 737 (if I identified that correctly) about 4 to 5 miles ahead; and another aircraft approaching 24R. The first officer was pilot flying and automation was engaged (a/P and a/T). We were on speed 180; and on profile with flaps 3; approaching point limma. Aircraft first started to shake and then suddenly started to bank to the right. I immediately took the control; disconnected the a/P and brought back the wings to level. After that rapid turn it started to smooth out and we were almost over point limma so we started to configure the plane and continued the approach with ap/at disengaged. We were stable at; and below 1000 feet and landing and the rest of approach were uneventful and normal. After landing tower advised on wake turbulence experience. Before we touched down we got 3 EICAS msgs of at fail; aoa limit fail; and windshear fail. Once we touched down all of those msgs disappeared and instead we got 4 blue advisory msgs of ads probe 1; 2; 3; 4 fail. Since it was just a mx repositioning flight we had to take the plane to hangar. During taxi to hangar the APU did not start and because the hangar area was busy we had to power down the plane. Dispatcher and maintenance had been contacted and advised of the issues and problem we experienced before landing. With the concurrence of maintenance APU restarted and the plane computers restarted with no EICAS msgs. Mx mentioned that receiving those messages during encounter with strong wake turbulence is typical. I guess being very light; with only me and first officer onboard made us more sensitive to wake of nearby traffic.
Original NASA ASRS Text
Title: EMB-175 Captain reported receiving several EICAS messages on system anomalies that were determined to be a result of a wake turbulence encounter during approach. All items were successfully cleared after landing.
Narrative: On an empty repositioning flight (Part 91) to LAX we experienced wake turbulence which caused 20 degrees of bank at about 2100 feet AGL. There was only me and the First Officer onboard the plane. We had a 737 (If I identified that correctly) about 4 to 5 miles ahead; and another aircraft approaching 24R. The First Officer was pilot flying and automation was engaged (A/P and A/T). We were on speed 180; and on profile with flaps 3; approaching point LIMMA. Aircraft first started to shake and then suddenly started to bank to the right. I immediately took the control; disconnected the A/P and brought back the wings to level. After that rapid turn it started to smooth out and we were almost over point LIMMA so we started to configure the plane and continued the approach with AP/AT disengaged. We were stable at; and below 1000 feet and landing and the rest of approach were uneventful and normal. After landing tower advised on Wake Turbulence experience. Before we touched down we got 3 EICAS msgs of AT FAIL; AOA LIMIT FAIL; and WINDSHEAR FAIL. Once we touched down all of those msgs disappeared and instead we got 4 blue advisory msgs of ADS PROBE 1; 2; 3; 4 FAIL. Since it was just a MX repositioning flight we had to take the plane to hangar. During taxi to hangar the APU did not start and because the hangar area was busy we had to power down the plane. Dispatcher and maintenance had been contacted and advised of the issues and problem we experienced before landing. With the concurrence of maintenance APU restarted and the plane computers restarted with no EICAS msgs. MX mentioned that receiving those messages during encounter with strong wake turbulence is typical. I guess being very light; with only me and First Officer onboard made us more sensitive to wake of nearby traffic.
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.