37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 551256 |
Time | |
Date | 200206 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : las.airport |
State Reference | NV |
Altitude | agl single value : 0 |
Aircraft 1 | |
Controlling Facilities | tracon : l30.tracon tower : las.tower |
Operator | common carrier : air carrier |
Make Model Name | MD-80 Series (DC-9-80) Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 551256 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | Chart Or Publication |
Primary Problem | Chart Or Publication |
Narrative:
Inbound to las on the clare one arrival approaching skebr intersection approach cleared us for the skebr one arrival. I mistakenly assumed he wanted us to continue our current arrival because our next waypoint was the skebr intersection. The first officer corrected me to the skebr 'RNAV' one arrival. We were unable this arrival because we were in a non EFIS MD80. Approach then provided vectors. When departing las in an EFIS airplane 1 hour later, our filed clearance was the las one departure to aces intersection. Pre departure clearance was not provided, I assume because they revised our departure to the aces one departure as filed. My question or problem is that in both of these instances the word RNAV was left out of our clearance even though it appears in the title of both the departure and the arrival they expected us to fly. I also think these procedures are setups for miscom because different procedures use some of the same waypoints. An example of potential trouble is someone filed for the las one to aces, instead of the aces 'RNAV' one. Would depart runway 25R on runway heading into rising terrain waiting for a vector while departure control thinks this person would turn on their own. In my opinion this is highly probable especially if the word 'RNAV' is left out of the aces 'RNAV' one because 2 of the 3 words are then the same. Las one aces versus aces one. Please ask them to rename waypoints on different departures and arrival so there can be little doubt which procedure is intended.
Original NASA ASRS Text
Title: FLC CONFUSES ARR NAME AND ARR FIX.
Narrative: INBOUND TO LAS ON THE CLARE ONE ARR APCHING SKEBR INTXN APCH CLRED US FOR THE SKEBR ONE ARR. I MISTAKENLY ASSUMED HE WANTED US TO CONTINUE OUR CURRENT ARR BECAUSE OUR NEXT WAYPOINT WAS THE SKEBR INTXN. THE FO CORRECTED ME TO THE SKEBR 'RNAV' ONE ARR. WE WERE UNABLE THIS ARR BECAUSE WE WERE IN A NON EFIS MD80. APCH THEN PROVIDED VECTORS. WHEN DEPARTING LAS IN AN EFIS AIRPLANE 1 HR LATER, OUR FILED CLRNC WAS THE LAS ONE DEP TO ACES INTXN. PDC WAS NOT PROVIDED, I ASSUME BECAUSE THEY REVISED OUR DEP TO THE ACES ONE DEP AS FILED. MY QUESTION OR PROB IS THAT IN BOTH OF THESE INSTANCES THE WORD RNAV WAS LEFT OUT OF OUR CLRNC EVEN THOUGH IT APPEARS IN THE TITLE OF BOTH THE DEP AND THE ARR THEY EXPECTED US TO FLY. I ALSO THINK THESE PROCS ARE SETUPS FOR MISCOM BECAUSE DIFFERENT PROCS USE SOME OF THE SAME WAYPOINTS. AN EXAMPLE OF POTENTIAL TROUBLE IS SOMEONE FILED FOR THE LAS ONE TO ACES, INSTEAD OF THE ACES 'RNAV' ONE. WOULD DEPART RWY 25R ON RWY HEADING INTO RISING TERRAIN WAITING FOR A VECTOR WHILE DEP CTL THINKS THIS PERSON WOULD TURN ON THEIR OWN. IN MY OPINION THIS IS HIGHLY PROBABLE ESPECIALLY IF THE WORD 'RNAV' IS LEFT OUT OF THE ACES 'RNAV' ONE BECAUSE 2 OF THE 3 WORDS ARE THEN THE SAME. LAS ONE ACES VERSUS ACES ONE. PLEASE ASK THEM TO RENAME WAYPOINTS ON DIFFERENT DEPS AND ARR SO THERE CAN BE LITTLE DOUBT WHICH PROC IS INTENDED.
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.