LATE DSCNT CLRNC IS ACCEPTED AND XING RESTR IS NOT MET ON ARR TO LAX; CA.
Synopsis
LATE DSCNT CLRNC IS ACCEPTED AND XING RESTR IS NOT MET ON ARR TO LAX; CA.
Narrative
INBOUND TO LAX ON THE PDZ 3 ARR; WE WERE GIVEN KONZL AT 17000 FT. XING KONZL WE WERE GIVEN A FREQ CHANGE THAT WAS GARBLED/WALKED ON. I CALLED BACK 3 TIMES BEFORE THE CTLR WOULD CONFIRM THE FREQ. SWITCHING OVER; WE WERE CLRED VIA THE PROFILE DSCNT. BY NOW THE TRTLE XING RESTR WAS COMING UP AND WE WERE BEHIND THE DSCNT PROFILE. THE FO FLYING INITIATED THE DSCNT; BUT I HAD TO COME ON THE YOKE AND PUSH OVER AGGRESSIVELY TO TRY TO MAKE THE TRTLE RESTR AT 16000 FT MSL. I ESTIMATE WE WERE 200-300 FT HIGH PASSING TRTLE. THERE WERE 2 DISTINCT FACTORS THAT COMBINED TO LEAD TO THE PROB. 1) COMS. OVERALL RADIO COMS VIA ATC HAS DETERIORATED TO THE POINT I SINCERELY FEEL IS A NEGATIVE SAFETY FACTOR. THE 3 ATTEMPTS TO CLARIFY THE PROPER FREQ COST 3-5 NM; WHICH LED TO THE LATE CLRNC FOR THE PROFILE DSCNT. WE HAD APPROX 3 M TO MAKE THE DSCNT AFTER RECEIVING THE DSCNT CLRNC. 2) ALTHOUGH THE FMC WAS PROGRAMMED FOR THE XING RESTR PROPERLY; THE FO HAD NO SENSE OF URGENCY OR POS AWARENESS DURING THE DSCNT INITIATION. HE HAD POSTED THE LATEST CHANGE FOR THE PDZ 3 ARR WHICH SHOWED TRTLE AT OR ABOVE 16000 FT MSL. HOWEVER; THAT CHANGE WAS NOT EFFECTIVE FOR ANOTHER 8 DAYS. I HAD THE PROPERLY DATED CHART OUT TO MONITOR THE ARR; BUT DUE TO WORKING THE RADIO; I WAS 1-2 MI SLOW TO REALIZE THE FO WASN'T FOLLOWING THE VNAV INFO (TRTLE AT 16000 FT MSL) DUE TO THE AT OR ABOVE MODIFICATION IN THE PDZ 4 ARR.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.