DURING DEP FLOW CTL DELAYS; A CLRNC IS REISSUED 2 TIMES. WHEN ENRTE; THE FLT CREW FLYING THE FINAL CLRNC IS QUESTIONED BY THE CTLR; WHO IS APPARENTLY USING AN EARLIER ROUTING; ABOUT WHAT THEIR ROUTING WAS.

Narrative

EWR WAS UNDER DEP FLOW MGMNT. AFTER CALLING CLRNC; WE WERE GIVEN AN AMENDED DEP AS FOLLOWS: EWR6 PARKE J6 MRB HNN AS FILED (IIU BUM...). WE PUSHED AT XA43. ON TAXI; AT APPROX XB30; WE WERE TOLD TO GO TO CLRNC FOR A RERTE AS FOLLOWS: EWR6 PARKE HVQ BWG LIT IRW.... AFTER TKOF; WHEN NEAR PARKE; WE WERE CLRED DIRECT ON COURSE. THE FMC WAS PROGRAMMED TO GO FROM PARKE TO HVQ PER OUR LAST CLRNC. SHORTLY AFTER PASSING PARKE; NEW YORK ATC SAID WE WERE 5 MI OFF COURSE. WE WERE RECLRED TO JOIN J6 TO MRB. I ASKED THE CTLR TO READ TO US THE FULL RTE CLRNC HE HAD. EWR6 PARKE J6 MRB HNN IIU. I QUESTIONED THIS ROUTING AND HE THEN CORRECTED PARKE J6 MRB J6 COLLS HVQ BWG LIT.... EWR CLRNC WAS GIVING MANY RERTES AT THE TIME. I KNOW BOTH THE FO AND I LISTENED AND COPIED THE SAME AMENDED CLRNC AS 'PARKE DIRECT HVQ.' SOMEHOW THE COM HAD BROKEN DOWN. IF THE INFO THAT THE RERTE COMPUTER GENERATES COULD BE FORWARDED DIRECTLY TO ATC AND THE CREW VIA ACARS; THE PROBS OF OMISSION IN CLRNC READINGS COULD BE GREATLY REDUCED. THIS ATC CTLR IN EWR CLRNC OMITTED THE PORTION FROM PARKE J6 MRB J6 COLLS HVQ OR GAVE US WRONG INFO. FORTUNATELY; THANKS TO OTHER ALERT CTLRS; THIS DID NOT TURN INTO A CONFLICT WITH OTHER ACFT.