Narrative:

1) what happened: system deviation which resulted in loss of sep of 2 IFR aircraft. 2) how was problem discovered: only when the audio visibility C/a went off. 3) what actions were taken: the aircraft on my frequency was given instructions to descend below the conflicting aircraft's altitude. 4) evasive action: none. 5) factors contributing: a) the sector in which sep was lost is seldom open. B) the aircraft on my frequency was on the wrong beacon code, therefore no altitude information was available C) ZNY put the aircraft on a route and altitude that was not conforming to our letter of agreement. 6) why do I believe situation occurred?: ZNY controller did not know his or her airspace. 7) suggestion to prevent: we at bwi work too many sectors in too many configns. ZNY is not familiar with our procedures. Our automation needs to be improved.

Google
 

Original NASA ASRS Text

Title: MLG CONFLICTED WITH AN SMT RESULTING IN A LOSS OF SEPARATION.

Narrative: 1) WHAT HAPPENED: SYS DEVIATION WHICH RESULTED IN LOSS OF SEP OF 2 IFR ACFT. 2) HOW WAS PROB DISCOVERED: ONLY WHEN THE AUDIO VIS C/A WENT OFF. 3) WHAT ACTIONS WERE TAKEN: THE ACFT ON MY FREQ WAS GIVEN INSTRUCTIONS TO DSND BELOW THE CONFLICTING ACFT'S ALT. 4) EVASIVE ACTION: NONE. 5) FACTORS CONTRIBUTING: A) THE SECTOR IN WHICH SEP WAS LOST IS SELDOM OPEN. B) THE ACFT ON MY FREQ WAS ON THE WRONG BEACON CODE, THEREFORE NO ALT INFO WAS AVAILABLE C) ZNY PUT THE ACFT ON A ROUTE AND ALT THAT WAS NOT CONFORMING TO OUR LETTER OF AGREEMENT. 6) WHY DO I BELIEVE SITUATION OCCURRED?: ZNY CTLR DID NOT KNOW HIS OR HER AIRSPACE. 7) SUGGESTION TO PREVENT: WE AT BWI WORK TOO MANY SECTORS IN TOO MANY CONFIGNS. ZNY IS NOT FAMILIAR WITH OUR PROCS. OUR AUTOMATION NEEDS TO BE IMPROVED.

Data retrieved from NASA's ASRS site as of August 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.