FLT CREW OF B738 ARE ACCUSED BY ZSE CTLR OF FAILING TO COMPLY WITH SID 'VIA' CLRNC THEY DID NOT RECEIVE. VERBAL ALTERCATION RESULTS.

Date: 2004-03 · Aircraft: B737-800 · Phase: descent

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

Synopsis

FLT CREW OF B738 ARE ACCUSED BY ZSE CTLR OF FAILING TO COMPLY WITH SID 'VIA' CLRNC THEY DID NOT RECEIVE. VERBAL ALTERCATION RESULTS.

Narrative

IN THE INITIAL STAGES OF THE CHINS 5 ARR INTO SEA; ZLC CLRED OUR ACFT TO DSND PLT'S DISCRETION FROM FL350 TO FL240. ON CHKING IN TO ZSE THE CO-PLT RPTED LEVEL (STILL) AT FL350 BUT NEGLECTED TO MENTION THE PART OF THE CLRNC TO DSND PLT'S DISCRETION TO FL240. AT THE TOP OF DSCNT POINT COMPUTED BY OUR FMC TO SATISFY THE XING RESTRS SPECIFIED ON THE CHINS; I BEGAN THE DSCNT AND RPTED 'OUT OF FL350 DSNDING PLT'S DISCRETION TO FL240.' THE FREQ WASN'T CONGESTED BUT STILL I DIDN'T CONSIDER IT VERY UNUSUAL THAT THE CTLR DIDN'T ACKNOWLEDGE THIS CALL; SINCE SOME SEEM TO CONSIDER IT SUPERFLUOUS IN THE FIRST PLACE. I EXPECTED AND WAS WAITING FOR A 'DSND VIA' CLRNC. SEVERAL MINS LATER STILL AT FL240; WE RECEIVED A QUERY FROM THE CTLR AS TO WHETHER WE WERE GOING TO COMPLY WITH THE RESTR (16000 FT) AT RADDY. WE RESPONDED THAT OUR MOST RECENT CLRNC HAD US STILL AT FL240. HE THEN CLRED US TO DSND VIA THE CHINS 5 ARR; BUT SOON THEREAFTER WE REQUESTED RELIEF AT RADDY (DUE TO THE LATENESS OF THE DSCNT OUT OF FL240). THIS ELICITED A VERY TESTY AND SOMEWHAT UNPROFESSIONAL RESPONSE FROM THE CTLR PATRONIZING US ABOUT THE BASICS OF READING 'THE CHART IN FRONT OF YOU.' I RESPONDED THAT 'JUST TO CLARIFY; WE HAVE NEVER RECEIVED A DSND VIA CLRNC.' HIS RESPONSE WAS ALONG THE LINES OF; 'YOU WERE GIVEN A DSND VIA CLRNC UPON CHKING IN AND I CAN SEND YOU THE TAPE!' IT'S UNUSUAL TO HEAR THIS DEGREE OF ARROGANCE OUT OF ANYBODY OTHER THAN AN XYZ LCL CTLR; AND IT IS UNPRECEDENTED IN MY EXPERIENCE FROM SOMEONE WHO SHOULDN'T HAVE BEEN SO SURE OF HIS LACK OF COMPLICITY IN THE CONFUSION THAT CAUSED THE ALLEGED FAILURE TO COMPLY WITH A CLRNC. MY PHONE CALL TO THE CTR SUPVR A FEW HRS LATER PROVIDED SOME INSIGHT INTO WHAT HAD HAPPENED. THOUGH WE HAD NOT BEEN GIVEN THE DSND VIA CLRNC UPON CHK-IN; HE QUOTED FOR ME THE PRECISE MIN AND SECOND THAT WE HAD BEEN GIVEN THE CLRNC. MY RESPONSE WAS SOMETHING ALONG THE LINES OF; 'OH REALLY?' AND AT WHAT MIN AND SECOND DID WE SUPPOSEDLY ACKNOWLEDGE THIS CLRNC?' HE SAID THAT THOUGH THERE WASN'T AN ACKNOWLEDGEMENT PER SE; THERE WAS SOME RADIO STATIC AND WE RPTED THAT WE WERE DSNDING TO FL240. I TOLD HIM THAT WAS ME RPTING OUT OF FL350 PLT'S DISCRETION TO FL240 AND THAT THE CTLR AND I HAD OBVIOUSLY STEPPED ON EACH OTHER; BUT REGARDLESS; HOW DOES A CLIPPED XMISSION FROM ME CONCERNING SOMETHING ABOUT DSNDING TO FL240 SUBSTITUTE FOR A PROPER READBACK FOR SOMETHING AS CRITICAL AS A DSND VIA CLRNC? HE ADMITTED THAT IT DIDN'T. I ALSO ASKED HIM FOR HIS OPINION OF THE DEGREE OF PROFESSIONALISM SHOWED BY THE CTLR WHEN I TRIED TO CLARIFY THAT WE HAD NEVER RECEIVED OR ACKNOWLEDGED A DSND VIA CLRNC; BUT HE SAID THAT HE HADN'T LISTENED THAT FAR. IN SUMMARY; I BELIEVE NOW THAT WE COULD AND OR SHOULD HAVE BEEN QUICKER ABOUT QUESTIONING WHAT THE PLAN WAS FOR FURTHER DSCNT BUT THAT THE ESSENCE OF THE MIX-UP WAS THE CTLR'S FAILURE TO ENSURE THAT THE CLRNC WAS NOT ONLY GIVEN BUT PROPERLY RECEIVED AND ACKNOWLEDGED. WE NEVER HAD AN OPPORTUNITY TO HEAR THE CLRNC BECAUSE IT CAME SIMULTANEOUSLY WITH OUR REQUIRED CALL LEAVING FL350.

More incidents for this aircraft family →

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