B737-700 FLT CREW MISSES XING RESTR ON ARR INTO OAK.

Date: 2004-03 · Aircraft: B737-700

Anomalies: deviation-altitude-crossing-restriction-not-met|deviation-altitude-excursion-from-assigned-altitude|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy

Synopsis

B737-700 FLT CREW MISSES XING RESTR ON ARR INTO OAK.

Narrative

DSNDING FOR OAK ON THE PANOCHE 2 ARR; WE HAD BEEN CLRED TO CROSS BORED INTXN AT 10000 FT. APPROX 10-15 NM FROM BORED WE WERE GIVEN ANOTHER CLRNC TO CROSS BORED AT 10000 FT THEN DSND TO 8000 FT. SINCE I WAS FLYING AND NEARLY LEVEL AT 10000 FT; THE FO LEFT FREQ TO CALL OAK BASE FOR A GATE. I WAS STILL VIEWING AN 80 NM SCALE ON THE MAP DISPLAY. AFTER LEVELING AT 10000 FT AND SLOWING TO 250 KTS; I COMMENCED A SLOW DSCNT TO 8000 FT. APPROX 9500 FT; ATC RADIOED THAT I SHOULD CROSS BORED AT 10000 FT. I THEN REALIZED I HAD ABOUT 4-5 NM TO GO BEFORE THE FIX. I STARTED A CLB TO CROSS BORED WITH NO FURTHER PROBS. I TOTALLY DROPPED THE XCHK OF THE FMC OUT OF MY SCAN. WITH THE 80 NM MAP SCALE; I THOUGHT I WAS NEARLY ON TOP OF BORED AS I STARTED MY DSCNT. THE FO WAS BUSY WITH THE RADIO AND DID NOT NOTICE MY GRADUAL DSCNT. I REALIZE THE FIX CHANGES COLOR ON THE MAP AFTER XING IT; BUT THAT DID NOT OCCUR TO ME AT THE TIME. MY INATTENTION TO DETAIL CONTRIBUTED TO THE MISTAKE DURING A CRITICAL TIME OF NO BACKUP FROM THE FO. I NEEDED TO HAVE HAD THE MAP IN A MORE USEFUL AND DETAIL ORIENTED SCALE. I ALSO NEEDED TO HAVE XCHKED THE FIX ON AN APPROPRIATE CDU DISPLAY. SUPPLEMENTAL INFO FROM ACN 610351: WE LEVELED OFF IN COMPLIANCE TO THE ATC RESTR OF BORED AT 10000 FT AND 250 KTS. ALT HOLD ILLUMINATED. FO SELECTED 8000 FT IN ALT SELECT. FO WENT OFF FREQ TO CALL COMPANY FOR GATE INFO.

More incidents for this aircraft family →

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