B737-300 CREW DID NOT COMPLY WITH AN ISSUED CROSSING RESTRICTION ON THE SKEBR 1 STAR INTO LAS.

Date: 2001-11 · Aircraft: B737-300 · Phase: approach

Anomalies: deviation-altitude-undershoot|deviation-altitude-crossing-restriction-not-met|deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-far|other-crew-distraction-with-non-pertenant-paperwork-during-descent

Synopsis

B737-300 CREW DID NOT COMPLY WITH AN ISSUED CROSSING RESTRICTION ON THE SKEBR 1 STAR INTO LAS.

Narrative

APCHING DAGETT ON THE PAMONA SIX DEP OUT OF ONTARIO; WE WERE GIVEN A CLRNC FROM FL290 TO DSND TO FL250 TO EXPECT FL240 AT MISEN INTXN ON THE SKEBR ONE ARRIVAL INTO LAS VEGAS. THE PNF READ THE CLRNC BACK CORRECTLY AND THE PF REPEATED THE READBACK. BOTH PLTS ATTENDED TO SOME PAPERWORK (LOGBOOK ENTRIES) FROM DEP AFTER THE COM WITH ATC. AFTER REVIEWING THE SKEBR ONE ARRIVAL ILLUSTRATION AND THE FMC PROFILE; BOTH WHICH READ 'MISEN FL240 MIM;' THE PF UNDERSTOOD AT OR ABOVE FL240 AT MISEN; RATHER THAN THE HARD ALT ASSIGNED. AS THE PF BEGAN HIS DSCNT; ATC QUESTIONED OUR PROFILE AND THE MISUNDERSTANDING BECAME APPARENT. WE WERE TOO HIGH TO MAKE THE RESTRICTION. SOME CONTRIBUTING FACTORS THAT LEAD TO THE ERROR INCLUDE THE VERY SHORT DURATION OF THE FLT WITH BOTH PLTS ATTENDING TO THEIR LOGBOOKS RATHER THAN THE DSCNT PROFILE. NEW RNAV PROCS WERE IN EFFECT WHICH WERE RELATIVELY NEW TO THE CREW. IN ADDITION THE DAGGETT VOR WAS INOP; SO THE FAMILIAR PATTERN OF ESTABLISHING SIT AWARENESS WAS UNAVAILABLE. ATC MADE LITTLE DIFFERENTIATION BETWEEN THE ILLUSTRATED PROFILE AND THE ALT ASSIGNED. LESSONS LEARNED INCLUDE: PAY ATTENTION TO THE NEW ARRIVALS INTO LAS; BOTH FLCS AND ATC ARE NEW TO THE PROCS. THE STD CUES FOR SIT AWARENESS ARE NO LONGER DISPLAYED; PAY ATTENTION. DON'T GET DISTRACTED ON THE SHORT FLTS AS A FLC. ATC COULD MAKE MORE OF AN EFFORT TO DIFFERENTIATE DSCNT PROFILES; ESPECIALLY WHEN PROCS ARE NEW. BOTH CREWMEMBERS SHOULD BETTER MANAGE FMC AND BACK EACH OTHER UP.

More incidents for this aircraft family →

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