ZTL controller described company flight identification procedure that results in limited ATC compute...

Narrative:

Air carrier X has a recurring problem of using some call signs on multiple trip legs. Within 1 week air carrier X1 and air carrier X2 were departing atl while duplicate call signs were airborne to atl from midwest. A80 (atl approach) is unable to depart the flight plan in their computer with the active duplicate call signs. The aircraft fly to the ZTL boundary and A80 is unable to hand off the track without modifying the call sign. A80 claims they are unable to do this. ZTL must then work the aircraft with no track or flight plan until manual coordination is completed. Air carrier X must use separate call signs on each leg. A80 must be able to modify call signs. A80 knows the aircraft is not departed in computer and yet they allow it to fly up to ZTL without ZTL having a flight plan or radar handoff. Atl tower probably also plays a role in problem. ZTL is expected to correct previous controller's inaction and yet ZTL may be too busy for unexpected and last-min additional workload.

Original NASA ASRS Text

Title: ZTL CTLR DESCRIBED COMPANY FLT ID PROC THAT RESULTS IN LIMITED ATC COMPUTER FUNCTIONALITIES WITH REGARD TO HDOFS; DATA BLOCK INFO; ETC.

Narrative: ACR X HAS A RECURRING PROB OF USING SOME CALL SIGNS ON MULTIPLE TRIP LEGS. WITHIN 1 WK ACR X1 AND ACR X2 WERE DEPARTING ATL WHILE DUPLICATE CALL SIGNS WERE AIRBORNE TO ATL FROM MIDWEST. A80 (ATL APCH) IS UNABLE TO DEPART THE FLT PLAN IN THEIR COMPUTER WITH THE ACTIVE DUPLICATE CALL SIGNS. THE ACFT FLY TO THE ZTL BOUNDARY AND A80 IS UNABLE TO HAND OFF THE TRACK WITHOUT MODIFYING THE CALL SIGN. A80 CLAIMS THEY ARE UNABLE TO DO THIS. ZTL MUST THEN WORK THE ACFT WITH NO TRACK OR FLT PLAN UNTIL MANUAL COORD IS COMPLETED. ACR X MUST USE SEPARATE CALL SIGNS ON EACH LEG. A80 MUST BE ABLE TO MODIFY CALL SIGNS. A80 KNOWS THE ACFT IS NOT DEPARTED IN COMPUTER AND YET THEY ALLOW IT TO FLY UP TO ZTL WITHOUT ZTL HAVING A FLT PLAN OR RADAR HDOF. ATL TWR PROBABLY ALSO PLAYS A ROLE IN PROB. ZTL IS EXPECTED TO CORRECT PREVIOUS CTLR'S INACTION AND YET ZTL MAY BE TOO BUSY FOR UNEXPECTED AND LAST-MIN ADDITIONAL WORKLOAD.

Data retrieved from NASA's ASRS site as of January 2009 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.

Attributes
ACN	763292
Time
Date	200711
Place
Locale Reference	airport : atl.airport
State Reference	GA
Altitude	msl single value : 23000
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller time certified in position1 : 25 controller time certified in position2 : 10
ASRS Report	763292
Events
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	Company
Primary Problem	Company

ZTL controller described company flight identification procedure that results in limited ATC computer functionalities with regard to handoffs; data block information; etc.