37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 556789 |
Time | |
Date | 200208 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | intersection : mirok |
State Reference | NY |
Altitude | msl bound lower : 8000 msl bound upper : 11000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : l30.tracon |
Operator | common carrier : air carrier |
Make Model Name | B737-800 |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | arrival star : mirok one |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 140 flight time total : 22000 flight time type : 3000 |
ASRS Report | 556789 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | other anomaly other other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued advisory controller : issued new clearance |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Company Airspace Structure Aircraft ATC Human Performance |
Primary Problem | ATC Human Performance |
Narrative:
After passing mirok on the mirok one arrival into las we were cleared by approach control to proceed direct to utare. Since utare was not on our arrival or leg's page we questioned approach about where the fix was. Following that we were given vectors for the runway 25L localizer. While on this vector approach control requested we call them after our arrival. I spoke to someone, I assume a supervisor, who was concerned why we did not follow the arrival after mirok and did not know where utare was. I told him we were cleared the mirok one arrival and that utare is not on that arrival. I confirmed this by referring to our pre departure clearance and explained we had not received a changeover clearance to fly the LYNSY1. He stated that we should expect this since we were flying an FMC equipped aircraft and should have questioned this immediately upon reaching mirok. My concern is how can the approach controller have a strip that states we are on the LYNSY1 when our original clearance of the mirok one had never been changed.
Original NASA ASRS Text
Title: A B737-800 FLC IS VECTORED THEN QUESTIONED AS TO WHY THEY COULD NOT FLY TO WAYPOINT UTARE WHEN ON THE MIROK ONE ARR INTO LAS, NV.
Narrative: AFTER PASSING MIROK ON THE MIROK ONE ARR INTO LAS WE WERE CLRED BY APCH CTL TO PROCEED DIRECT TO UTARE. SINCE UTARE WAS NOT ON OUR ARR OR LEG'S PAGE WE QUESTIONED APCH ABOUT WHERE THE FIX WAS. FOLLOWING THAT WE WERE GIVEN VECTORS FOR THE RWY 25L LOC. WHILE ON THIS VECTOR APCH CTL REQUESTED WE CALL THEM AFTER OUR ARR. I SPOKE TO SOMEONE, I ASSUME A SUPVR, WHO WAS CONCERNED WHY WE DID NOT FOLLOW THE ARR AFTER MIROK AND DID NOT KNOW WHERE UTARE WAS. I TOLD HIM WE WERE CLRED THE MIROK ONE ARR AND THAT UTARE IS NOT ON THAT ARR. I CONFIRMED THIS BY REFERRING TO OUR PDC AND EXPLAINED WE HAD NOT RECEIVED A CHANGEOVER CLRNC TO FLY THE LYNSY1. HE STATED THAT WE SHOULD EXPECT THIS SINCE WE WERE FLYING AN FMC EQUIPPED ACFT AND SHOULD HAVE QUESTIONED THIS IMMEDIATELY UPON REACHING MIROK. MY CONCERN IS HOW CAN THE APCH CTLR HAVE A STRIP THAT STATES WE ARE ON THE LYNSY1 WHEN OUR ORIGINAL CLRNC OF THE MIROK ONE HAD NEVER BEEN CHANGED.
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.