RPTR STATES THAT SECTOR WAS BUSY AND STANDARD SEPARATION WAS LOST BTWN ACFT X AND Y.

Date: 1999-08 · Aircraft: A320

Anomalies: atc-issue-all-types|conflict-airborne-conflict|inflight-event-encounter-weather-turbulence

Synopsis

RPTR STATES THAT SECTOR WAS BUSY AND STANDARD SEPARATION WAS LOST BTWN ACFT X AND Y.

Narrative

ACFT X HAD DEPARTED BOS AND HAD DEVIATED TO THE NE TO AVOID WX. FOR TFC; I ISSUED A VECTOR TO ACFT X TO 070 DEGS AND CLBED HIM TO FL350. TFC WAS BEGINNING TO PICK UP AND SEVERAL ACFT CHKED ON AND BEGAN ASKING ABOUT WX AND RIDES. DUE TO BAD WX W OF BOS; ALL ARRS WERE BEING RERTED OVER ENE -- SCUPP. THE SECTOR W OF ME CALLED TO COORDINATE A TFC SIT AND THEN AN ACFT I HAD POINTED OUT TO ANOTHER SECTOR REQUESTED A WX DEV AND I HAD TO COORDINATE WITH THAT SECTOR. THE FREQ WAS BECOMING CONGESTED AND ACFT WERE TAKING THE WRONG CALLS. I TURNED ACFT X N AND THEN NW THINKING I HAD CLRED THE TFC. I THEN SAW ACFT X WAS IN CONFLICT WITH ACFT Y AT FL330. THE ACFT X WAS ONLY OUT OF FL334 AND CONVERGING WITH ACFT Y. I ISSUED A TURN TO ACFT Y TO THE SE AND TURNED ACFT X TO THE N. ACFT Y SAW ACFT X ON TCASII AND ACFT X SAW ACFT Y VISUALLY AND THE POINT SEPARATION WAS LOST. JUST PRIOR TO THE DEV; I RECEIVED SEVERAL HDOFS FROM THE OTHER SECTOR AND OVERLAPPING DATA BLOCK CAUSED SOME CONFUSION AS TO ACFT IDENT. ADDITIONALLY; I LET FREQ CONGESTION DISTRACT ME FROM MY TFC SCAN. AS TFC BEGAN BUILDING; I SHOULD HAVE REQUESTED THE SECTOR BE SPLIT TO ELIMINATE SOME OF THE FREQ PROBS AND TO TAKE ADVANTAGE OF BETTER RANGE ON THE RADAR.

More incidents for this aircraft family →

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