ZID CTLR HAS OPERROR BTWN MD88 AND RJ WHEN SEQUENCING FOR IN TRAIL SPACING. CTLR BELIEVES TMU ACTIONS CONTRIBUTED.

Date: 2006-09 · Aircraft: Regional Jet CL65; Undifferentiated or Other Model · Phase: cruise

Anomalies: conflict-airborne-conflict

Synopsis

ZID CTLR HAS OPERROR BTWN MD88 AND RJ WHEN SEQUENCING FOR IN TRAIL SPACING. CTLR BELIEVES TMU ACTIONS CONTRIBUTED.

Narrative

THE SITUATION OCCURRED DUE TO SEQUENCING TO CLT ARPT. THE SECTOR HAD BEEN EXTREMELY BUSY WITH VERY COMPLEX TFC SITUATIONS. CONTRIBUTING FACTORS: TMU! I WAS THE D-SIDE TRYING TO HELP THE RADAR CTLR. THE SECTOR HAD BEEN BUSY AND I HAD BEEN MOVING DATA BLOCKS AND COORD. THE SUPVR CAME TO TELL ME THAT CLT NEEDED TO BE 25 MI IN-TRAIL. THERE WAS NOTHING POSTED FOR CLT ARRS. THE LOW SECTORS TRIED TO CALL AND SEQUENCE AN ACFT AT LOWER ALT WHICH WE HAVE NEVER DONE BEFORE. BUT THIS WAS A REQUIREMENT OF TMU. I TOLD OUR SUPVR THAT WE NEVER SEQUENCED LOW ALT ACFT AND HE SAID TMU SAID SEQUENCE THEM. I CALLED THE ATL CTLR AND HE SAID THEY JUST NEED SPD AND NO IN-TRAIL (AS IN MILES). I TOLD THE SUPVR AND HE CALLED TMU. TMU SAID SEQUENCE THEM ALL; SO MY RADAR HAD ALREADY TURNED THE ACFT TO GET HIM IN-TRAIL AND DID NOT NOTICE THE ACFT PICKED UP A LOT OF SPD. I DID NOT HEAR HIM TURN THE ACFT AND TO WHAT HDG HE ISSUED BECAUSE I WAS BEING BOTHERED BY THE SUPVR AND TMU. I THINK IF I WOULD HAVE BEEN PAYING ATTN TO EVERY DETAIL AT THE SECTOR AND NOT BEING BOTHERED BY THE SUPVR AND TMU MAYBE THIS ERROR WOULD NOT HAVE HAPPENED; I REALLY FEEL THE UNNECESSARY INFO FROM TMU WHICH WAS NOT NEEDED PLAYED A BIG FACTOR IN THIS OPERROR.

More incidents for this aircraft family →

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