A320 CREW MISSES CROSSING RESTR AFTER CLOSE-IN RWY CHANGE ON SEAVU 1 ARR TO LAX.

Date: 2007-03 · Aircraft: A320 · Phase: approach

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

Synopsis

A320 CREW MISSES CROSSING RESTR AFTER CLOSE-IN RWY CHANGE ON SEAVU 1 ARR TO LAX.

Narrative

ARR TO LAX FMGC SET UP FOR SEAVU 1 STAR TO RWY 24R (RWY 25R WAS IN SECONDARY). ALL FIXES AND ALTS WERE CONFIRMED AND BRIEFED. AT KONZL WAS CLRED SEAVU 1 RWY 25R. WE WENT TO HEADING AND ACTIVATED THE SECONDARY (TO PUT RWY 25R AS THE ARR). SET LOWEST ALT IN FCU AND ENGAGED MANAGED DESCENT AT PER STANDARD OPERATING PROC. INSIDE CATAW (CROSSED AT 14000 FT IN DESCENT) APCH CTL RECLRED US TO RWY 24R. WE NOW HAD TO REPROGRAM THE FMGC SINCE WE HAD ALREADY USED THE SECONDARY FLT PLAN ON THE INITIAL CLRNC TO RWY 25R. THE ACFT REVERTED TO VERTICAL SPEED DESCENT AND 7000 FT WAS STILL THE ALT IN THE FCU. THE SEAVU 1 WAS AGAIN PROGRAMMED IN AND ACFT SET UP FOR MANAGED DESCENT BUT WE WERE ALREADY THROUGH 12000 FT OUTSIDE DIXXN (WHICH WAS TO BE CROSSED AT OR ABOVE 12000 FT). WE LEVELED AT 10000 AND ADVISED APCH CONTROL THAT WE HAD DESCENDED THROUGH 12000 FT PRIOR TO DIXXN DUE TO LATE RE-CLRNC. THEY REPLIED 'NO PROB THERE WAS NO TFC ANYWHERE NEAR US.' CAPT FLYING AND FO WAS REPROGRAMMING FMGC. CLOSE IN RE-CLRNC AND SEAVU 1 PLATE DOES NOT SHOW DIXXN AT OR ABOUT 12000 FT IN LARGER VIEW (ONLY IN THE EXPLODED VIEW IN BOTTOM CORNER OF THE PLATE DOES IT SHOW THE CROSSING RESTR). WE HAD CONFIRMED ALTS WERE IN THE FMGC PRIOR TO THE APCH BUT WHEN RE-CLRED IT REVERTED TO VERTICAL SPEED AND DID NOT CAPTURE THE RESTR ALTS.

More incidents for this aircraft family →

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