 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 captain reported a track deviation on approach to las as a result of high workload related to a late runway change.
| Attributes | |
| ACN | 1315732 |
| Time | |
| Date | 201512 |
| Place | |
| Locale Reference | LAS.Airport |
| State Reference | NV |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR SUNST3 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 129 |
| Events | |
| Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Approaching the fuzzy intersection on the SUNST3 arrival; we were told to maintain current heading for vectors to runway 1L. I centered up the heading bug and selected heading sel and immediately began to fumble with the efb as we had not briefed this approach (as we were expecting runway 25L). As we began to brief the new approach and the first officer was looking at the landing numbers on the opc; the aircraft began to turn slightly to the left as apparently LNAV was still engaged as we passed over fuzzy. Just about then ATC gave us heading to fly further to the right.task saturation was definitely a factor in this case as there were many things that needed to be done on short notice. I was also concerned about high terrain at night and staying in the class B airspace surrounding it. The class B was of particular concern as ATC was pushing hard for a visual approach; the DME on the las VOR was out of service and we were in a 737 with no map mode or any way to clearly define the airspace boundaries! Next time I think I'll just request the runway we had already briefed as it was favorable for the winds and was advertised as the landing runway on the ATIS.
Original NASA ASRS Text
Title: B737 Captain reported a track deviation on approach to LAS as a result of high workload related to a late runway change.
Narrative: Approaching the FUZZY intersection on the SUNST3 Arrival; we were told to maintain current heading for vectors to Runway 1L. I centered up the heading bug and selected HDG SEL and immediately began to fumble with the EFB as we had not briefed this approach (as we were expecting Runway 25L). As we began to brief the new approach and the First Officer was looking at the landing numbers on the OPC; the aircraft began to turn slightly to the left as apparently LNAV was still engaged as we passed over FUZZY. Just about then ATC gave us heading to fly further to the right.Task saturation was definitely a factor in this case as there were many things that needed to be done on short notice. I was also concerned about high terrain at night and staying in the Class B airspace surrounding it. The Class B was of particular concern as ATC was pushing hard for a visual approach; the DME on the LAS VOR was out of service and we were in a 737 with no map mode or any way to clearly define the airspace boundaries! Next time I think I'll just request the runway we had already briefed as it was favorable for the winds and was advertised as the landing runway on the ATIS.
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.