ON THE WRONG FREQUENCY DURING THE LYNSY RNAV ONE ARR TO LAS; NV. HAVING NO CLRNC TO DESCEND VIA THE ARR; AN ACR CREW DESCENDS WITHOUT CLRNC.

Date: 2002-10 · Aircraft: B737-700

Anomalies: deviation-altitude-excursion-from-assigned-altitude|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy

Synopsis

ON THE WRONG FREQUENCY DURING THE LYNSY RNAV ONE ARR TO LAS; NV. HAVING NO CLRNC TO DESCEND VIA THE ARR; AN ACR CREW DESCENDS WITHOUT CLRNC.

Narrative

CLRNC GIVEN BY LAS VEGAS APCH TO CROSS LYNSY INTXN AT 250 KTS AT 12000 FT. DID NOT RECEIVE CLRNC TO DESCEND PAST LYNSY. CONTINUED TO DESCEND TO CROSS UTARE AT 210 KTS 8000 FT. APCHING UTARE APCH FREQUENCY GIVEN MAY HAVE BEEN INCORRECTLY SET. WE NEVER HEARD ANY FURTHER INSTRUCTIONS. AFTER 1 TO 2 MINS OF SILENCE WE DETERMINED THE FREQUENCY TO BE IN ERROR. CALLED TWR WHO PUT US ON CORRECT FREQUENCY AND WE CONTINUED APCH. TWR INFORMED US TO CALL APCH SUPVR; WHICH THE CAPT DID AT THE GATE. SUPVR WAS CONCERNED ABOUT DESCENT WITHOUT CLRNC AND LAPSE IN COM. NO FURTHER STATEMENTS WERE MADE BETWEEN US AND SUPVR. IF WE WOULD HAVE QUESTIONED THE DESCENT PAST LYNSY; WE WOULD HAVE FIGURED OUT SOONER THAT WE WERE ON WRONG FREQUENCY AND THAT WE DID NOT HAVE CLRNC TO DESCEND. ANOTHER CONTRIBUTING FACTOR COULD HAVE BEEN THAT WHILE I WAS MAKING A PA TO CUSTOMERS; CTR CLRED US TO CROSS LYNSY AT 250 KTS 12000 FT. I ASSUMED THAT THE CLRNC WAS ALSO CLRNC TO DESCEND ON THE ARR. THIS COUPLED WITH BEING ON THE WRONG APCH FREQ WERE MAJOR CONTRIBUTORS TO ALT CONFLICT.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.