 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
The flight crew of an air carrier MD80 assumed that a NAVAID was still OTS and held their heading, awaiting vectors to final, just as they had been doing for a number of months. They were surprised when the approach controller corrected them.
| Attributes | |
| ACN | 425640 |
| Time | |
| Date | 199901 |
| Day | Sun |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : bld airport : las |
| State Reference | NV |
| Altitude | msl bound lower : 10000 msl bound upper : 10000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : teb |
| Operator | common carrier : air carrier |
| Flight Phase | cruise other |
| Route In Use | arrival other arrival star : star |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : flight engineer |
| Experience | flight time last 90 days : 250 flight time total : 12300 flight time type : 1200 |
| ASRS Report | 425640 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : cfi |
| Experience | flight time last 90 days : 200 flight time total : 7000 flight time type : 1200 |
| ASRS Report | 425026 |
| Events | |
| Anomaly | non adherence : published procedure non adherence : clearance other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | other |
| Consequence | Other |
| Supplementary | |
| Air Traffic Incident | Pilot Deviation |
Narrative:
During descent on fuzzy 4 arrival, I listened to ATIS, did not notice that ATIS did not include any reference to boulder VOR. ATC told us to descend via fuzzy 4 arrival, as they had almost the entire time bld VOR was OTS, 6-10 months. Usually, after fuzzy, we fly 100 degree heading or are given a heading to fly. This time, ATC said, 'call sign, you are flying the fuzzy 4 arrival, aren't you?' we checked the bld VOR and found that it was back in service. By this time, we had passed through the bld 260 degree radial. We were then given direct bld. Being a terrible creature of habit and despite the knowledge that no reference to bld VOR being OTS means that it works, cockpit workload distracted me from checking the bld VOR. A special remark on the ATIS ('bld VOR back in service') would have helped. ATC might've also said something. I can't help but wonder how many pilots were caught by this same scenario.
Original NASA ASRS Text
Title: THE FLC OF AN ACR MD80 ASSUMED THAT A NAVAID WAS STILL OTS AND HELD THEIR HEADING, AWAITING VECTORS TO FINAL, JUST AS THEY HAD BEEN DOING FOR A NUMBER OF MONTHS. THEY WERE SURPRISED WHEN THE APCH CTLR CORRECTED THEM.
Narrative: DURING DSCNT ON FUZZY 4 ARR, I LISTENED TO ATIS, DID NOT NOTICE THAT ATIS DID NOT INCLUDE ANY REF TO BOULDER VOR. ATC TOLD US TO DSND VIA FUZZY 4 ARR, AS THEY HAD ALMOST THE ENTIRE TIME BLD VOR WAS OTS, 6-10 MONTHS. USUALLY, AFTER FUZZY, WE FLY 100 DEG HDG OR ARE GIVEN A HEADING TO FLY. THIS TIME, ATC SAID, 'CALL SIGN, YOU ARE FLYING THE FUZZY 4 ARR, AREN'T YOU?' WE CHKED THE BLD VOR AND FOUND THAT IT WAS BACK IN SVC. BY THIS TIME, WE HAD PASSED THROUGH THE BLD 260 DEG RADIAL. WE WERE THEN GIVEN DIRECT BLD. BEING A TERRIBLE CREATURE OF HABIT AND DESPITE THE KNOWLEDGE THAT NO REF TO BLD VOR BEING OTS MEANS THAT IT WORKS, COCKPIT WORKLOAD DISTRACTED ME FROM CHKING THE BLD VOR. A SPECIAL REMARK ON THE ATIS ('BLD VOR BACK IN SVC') WOULD HAVE HELPED. ATC MIGHT'VE ALSO SAID SOMETHING. I CAN'T HELP BUT WONDER HOW MANY PLTS WERE CAUGHT BY THIS SAME SCENARIO.
Data retrieved from NASA's ASRS site as of July 2007 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.