Narrative:

With late night operations in place, air carrier X had been cleared direct dfw. When controller a assumed control of air carrier X, he reclred air carrier X over cqy (cedar creek VORTAC) which is a cornerpost used for normal day operations. This new routing was entered in the computer and strips printed at controller B's sector. Knowing this routing was not in accordance with procedures dictated by an LOA which was effective at that time, controller B went over to the area of controller a and informed him as to the proper routing and that late night operations were in effect. Controller a did not reclr air carrier X back direct dfw as he should, but instead initiated a handoff to controller B. Controller B expected the required coordination call from controller a because air carrier X was not proceeding direct dfw in accordance with late night operations directives. Air carrier X entered controller B's airspace without proper coordination and without a handoff taken and, additionally, is placed on controller B's frequency. Chain of events: controller a refused to acknowledge and comply with late night operation procedures even after controller B personally informed him that the LOA was in effect and what routing controller a should use. Controller a failed to coordinate a routing with controller B which was different from that which air carrier X should have been cleared. Controller a failed to contain air carrier X within his airspace until a handoff had been accepted. Controller a switched air carrier X to controller B's frequency prematurely.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZFW CTLRS UNABLE TO RESOLVE LATE NIGHT CONFIGN TFC FLOWS REVERT TO FREQ CHANGE OF ACR ON AN UNAUTH RTE LNDG DFW.

Narrative: WITH LATE NIGHT OPS IN PLACE, ACR X HAD BEEN CLRED DIRECT DFW. WHEN CTLR A ASSUMED CTL OF ACR X, HE RECLRED ACR X OVER CQY (CEDAR CREEK VORTAC) WHICH IS A CORNERPOST USED FOR NORMAL DAY OPS. THIS NEW ROUTING WAS ENTERED IN THE COMPUTER AND STRIPS PRINTED AT CTLR B'S SECTOR. KNOWING THIS ROUTING WAS NOT IN ACCORDANCE WITH PROCS DICTATED BY AN LOA WHICH WAS EFFECTIVE AT THAT TIME, CTLR B WENT OVER TO THE AREA OF CTLR A AND INFORMED HIM AS TO THE PROPER ROUTING AND THAT LATE NIGHT OPS WERE IN EFFECT. CTLR A DID NOT RECLR ACR X BACK DIRECT DFW AS HE SHOULD, BUT INSTEAD INITIATED A HDOF TO CTLR B. CTLR B EXPECTED THE REQUIRED COORD CALL FROM CTLR A BECAUSE ACR X WAS NOT PROCEEDING DIRECT DFW IN ACCORDANCE WITH LATE NIGHT OPS DIRECTIVES. ACR X ENTERED CTLR B'S AIRSPACE WITHOUT PROPER COORD AND WITHOUT A HDOF TAKEN AND, ADDITIONALLY, IS PLACED ON CTLR B'S FREQ. CHAIN OF EVENTS: CTLR A REFUSED TO ACKNOWLEDGE AND COMPLY WITH LATE NIGHT OP PROCS EVEN AFTER CTLR B PERSONALLY INFORMED HIM THAT THE LOA WAS IN EFFECT AND WHAT ROUTING CTLR A SHOULD USE. CTLR A FAILED TO COORDINATE A ROUTING WITH CTLR B WHICH WAS DIFFERENT FROM THAT WHICH ACR X SHOULD HAVE BEEN CLRED. CTLR A FAILED TO CONTAIN ACR X WITHIN HIS AIRSPACE UNTIL A HDOF HAD BEEN ACCEPTED. CTLR A SWITCHED ACR X TO CTLR B'S FREQ PREMATURELY.

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