37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 851877 |
Time | |
Date | 200909 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | LAS.Airport |
State Reference | NV |
Aircraft 1 | |
Make Model Name | B737 Next Generation Undifferentiated |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Inflight Event / Encounter Wake Vortex Encounter |
Narrative:
While being vectored for a visual approach to runway 19L at las; controller and pilot workload was high. Approach control frequency was so congested we were waiting our turn for check-in for roughly 30 seconds. Once on frequency; numerous 10; 20; and 40 degree heading changes were issued along with traffic calls for a helicopter and 2 737's to my left (at approximately our 10 o'clock position). I was issued a visual approach clearance to runway 19L with a restriction to maintain 3500 ft until intercepting the runway 19L centerline from a westerly heading. Both crewmembers were looking for called traffic but acquisition was difficult due to the numerous densely packed buildings in the line of sight to the targets. The autopilot and autothrottles were off in anticipation of a landing clearance. The helicopter traffic was again called low and close at approximately 10 o'clock position nearly coincident with a call for a 737 crossing the runway 19L centerline in front of me for a visual for runway 19R. While looking for traffic as I was turning left to intercept the runway 19L centerline; I may have inadvertently descended below the 3500 ft restriction and a TCAS RA occurred. At the same time the RA alerted I saw the helicopter below me out my left window in a right turn to a northeasterly heading and passing under my aircraft. As I continued for landing the wake from the runway 19R 737 was encountered and was evident but fortunately; not significantly disruptive. The approach continued to a normal landing following the TCAS RA. The event site location radial and distance above are approximations. The environment of runway 19 parallel landings is particularly challenging due to the proximity of mountains and nellis AFB. I would have preferred more spacing in a situation like this and if in a similar situation again; I will likely abort the approach. Better ATC speed control and arrival fix separation planning may help las better manage final approach controller workload in such a restrictive airspace environment. This was my first trip to las in nearly a year. I asked the first officer if this congestion was common at las as he had been to las frequently in the last several months. Unfortunately; he indicated that it was.
Original NASA ASRS Text
Title: A B737 flight crew reported high workload and frequency congestion on approach to LAS that led to an altitude deviation. The approach was also complicated by a wake encounter.
Narrative: While being vectored for a visual approach to Runway 19L at LAS; Controller and pilot workload was high. Approach Control frequency was so congested we were waiting our turn for check-in for roughly 30 seconds. Once on frequency; numerous 10; 20; and 40 degree heading changes were issued along with traffic calls for a helicopter and 2 737's to my left (at approximately our 10 o'clock position). I was issued a visual approach clearance to Runway 19L with a restriction to maintain 3500 FT until intercepting the Runway 19L centerline from a westerly heading. Both crewmembers were looking for called traffic but acquisition was difficult due to the numerous densely packed buildings in the line of sight to the targets. The autopilot and autothrottles were off in anticipation of a landing clearance. The helicopter traffic was again called low and close at approximately 10 o'clock position nearly coincident with a call for a 737 crossing the Runway 19L centerline in front of me for a visual for Runway 19R. While looking for traffic as I was turning left to intercept the Runway 19L centerline; I may have inadvertently descended below the 3500 ft restriction and a TCAS RA occurred. At the same time the RA alerted I saw the helicopter below me out my left window in a right turn to a northeasterly heading and passing under my aircraft. As I continued for landing the wake from the Runway 19R 737 was encountered and was evident but fortunately; not significantly disruptive. The approach continued to a normal landing following the TCAS RA. The event site location radial and distance above are approximations. The environment of Runway 19 parallel landings is particularly challenging due to the proximity of mountains and Nellis AFB. I would have preferred more spacing in a situation like this and if in a similar situation again; I will likely abort the approach. Better ATC speed control and arrival fix separation planning may help LAS better manage final Approach Controller workload in such a restrictive airspace environment. This was my first trip to LAS in nearly a year. I asked the First Officer if this congestion was common at LAS as he had been to LAS frequently in the last several months. Unfortunately; he indicated that it was.
Data retrieved from NASA's ASRS site as of April 2012 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.