37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1659088 |
Time | |
Date | 201906 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SAN.Airport |
State Reference | CA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citation Excel (C560XL) |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | A319 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Inflight Event / Encounter Wake Vortex Encounter Inflight Event / Encounter Loss Of Aircraft Control |
Narrative:
Wake turbulence encounter while on RNAV Y runway 27 approach to san. We were approximately 4 miles from FAF (final approach fix) at about 3000 ft when the aircraft rolled violently to the left beyond 60 degrees. The PF (pilot flying) applied full right aileron and pulled up to get out of the wake vortices's. I notified ATC (socal approach) and asked if there was an aircraft ahead of us. They said there was an airbus. After landing I called socal approach to get more information. The supervisor looked at the radar data and told me that we were 5 miles in trail of an airbus A319 and this met their separation requirements. I asked him about our flight path and he said there was no noticeable course or altitude deviation on the radar. I told him that had we been informed that there was an A319 ahead of us we would have adjusted our flight path to stay above the wake. Evidently ATC is not required to do that. Fortunately we had no passengers and no one was injured.at the time of the incident radio communications was very quiet so ATC did not seem to be dealing with a heavy workload and I feel they would have had time to tell us of the traffic ahead. While ATC may not be required to give a wake turbulence warning I feel that there are enough variables and unknowns about this phenomenon that flight crews need as much information as possible to insure safety.
Original NASA ASRS Text
Title: CE-560XLS Captain reported encountering wake turbulence on arrival into SAN 5 miles in trail of an A319 that resulted in a 'violent' roll.
Narrative: Wake turbulence encounter while on RNAV Y Runway 27 approach to SAN. We were approximately 4 miles from FAF (Final Approach Fix) at about 3000 ft when the aircraft rolled violently to the left beyond 60 degrees. The PF (Pilot Flying) applied full right aileron and pulled up to get out of the wake vortices's. I notified ATC (SoCal Approach) and asked if there was an aircraft ahead of us. They said there was an Airbus. After landing I called SoCal approach to get more information. The Supervisor looked at the radar data and told me that we were 5 miles in trail of an Airbus A319 and this met their separation requirements. I asked him about our flight path and he said there was no noticeable course or altitude deviation on the radar. I told him that had we been informed that there was an A319 ahead of us we would have adjusted our flight path to stay above the wake. Evidently ATC is not required to do that. Fortunately we had no passengers and no one was injured.At the time of the incident radio communications was very quiet so ATC did not seem to be dealing with a heavy workload and I feel they would have had time to tell us of the traffic ahead. While ATC may not be required to give a wake turbulence warning I feel that there are enough variables and unknowns about this phenomenon that flight crews need as much information as possible to insure safety.
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.