Narrative:

I was working seavr-lo (37) right and D combined. I took a handoff on CE550 descending from decod-hi (42); inbound to 4t2 (a non-STAR airport) via sasie..fuz..4t2. This route is usually issued rather than the 'pref route' byp..BYP248..FUZ035..fuz..destination as they mirror each other inside D10 airspace. I issued CE550 'cross sasie at 110.' I saw the handoff initiated to dfw approach (D10). As CE550 approached sasie (the boundary between ZFW and D10); I used a 'holler line' to D10 dallas north to call for a handoff. With no answer; I called a second time. Both calls used call sign and/or fix. I immediately turned CE550 away from approach airspace; then made 2 more calls before D10 answered. Total time between my first call and fourth call was less the 50 seconds. The aircraft never entered approach airspace; closest lateral approximately 1 1/2 mi. However; FAA has interpreted 7110.65R 5-4-5(a) language of 'complete a radar handoff prior to aircraft's entering the airspace delegated to the receiving controller' to mean '2 1/2 mi prior' as contained in 7110.65 5-5-10(a) (2) and (3); notwithstanding the 1 1/2 mi in 5-5-10(a) (1). Further; I noted the handoff blinking to D1D rather the usual D1N. I do not have any idea what internal confign D10 is working at any given time; so I did not inquire to D10. Upon review; the NAS automation flashed the handoff to D1D not D1N because the route was 'splatted.' I was unaware this might be a problem as sasie; a boundary fix; was included in the route. Looking forward; I do not know how ZFW will be able to avoid deviations in the future 1) if D10 will not take handoffs in a timely manner; 2) if D10 will not answer calls in a timely fashion; and 3) the volume of traffic collecting over a cornerpost prohibits spinning aircraft without a detrimental ripple effect to trailing aircraft (there is nowhere to spin them).

Google
 

Original NASA ASRS Text

Title: ZFW CTLR EXPERIENCED OPDEV WHEN ACFT ENTERED D10'S AIRSPACE WITHOUT HDOF/COORD; CTLR ALLEGES FAILED AUTOMATION AND COORD AS CAUSAL.

Narrative: I WAS WORKING SEAVR-LO (37) R AND D COMBINED. I TOOK A HDOF ON CE550 DSNDING FROM DECOD-HI (42); INBOUND TO 4T2 (A NON-STAR ARPT) VIA SASIE..FUZ..4T2. THIS RTE IS USUALLY ISSUED RATHER THAN THE 'PREF RTE' BYP..BYP248..FUZ035..FUZ..DEST AS THEY MIRROR EACH OTHER INSIDE D10 AIRSPACE. I ISSUED CE550 'CROSS SASIE AT 110.' I SAW THE HDOF INITIATED TO DFW APCH (D10). AS CE550 APCHED SASIE (THE BOUNDARY BTWN ZFW AND D10); I USED A 'HOLLER LINE' TO D10 DALLAS NORTH TO CALL FOR A HDOF. WITH NO ANSWER; I CALLED A SECOND TIME. BOTH CALLS USED CALL SIGN AND/OR FIX. I IMMEDIATELY TURNED CE550 AWAY FROM APCH AIRSPACE; THEN MADE 2 MORE CALLS BEFORE D10 ANSWERED. TOTAL TIME BTWN MY FIRST CALL AND FOURTH CALL WAS LESS THE 50 SECONDS. THE ACFT NEVER ENTERED APCH AIRSPACE; CLOSEST LATERAL APPROX 1 1/2 MI. HOWEVER; FAA HAS INTERPED 7110.65R 5-4-5(A) LANGUAGE OF 'COMPLETE A RADAR HDOF PRIOR TO ACFT'S ENTERING THE AIRSPACE DELEGATED TO THE RECEIVING CTLR' TO MEAN '2 1/2 MI PRIOR' AS CONTAINED IN 7110.65 5-5-10(A) (2) AND (3); NOTWITHSTANDING THE 1 1/2 MI IN 5-5-10(A) (1). FURTHER; I NOTED THE HDOF BLINKING TO D1D RATHER THE USUAL D1N. I DO NOT HAVE ANY IDEA WHAT INTERNAL CONFIGN D10 IS WORKING AT ANY GIVEN TIME; SO I DID NOT INQUIRE TO D10. UPON REVIEW; THE NAS AUTOMATION FLASHED THE HDOF TO D1D NOT D1N BECAUSE THE RTE WAS 'SPLATTED.' I WAS UNAWARE THIS MIGHT BE A PROB AS SASIE; A BOUNDARY FIX; WAS INCLUDED IN THE RTE. LOOKING FORWARD; I DO NOT KNOW HOW ZFW WILL BE ABLE TO AVOID DEVS IN THE FUTURE 1) IF D10 WILL NOT TAKE HDOFS IN A TIMELY MANNER; 2) IF D10 WILL NOT ANSWER CALLS IN A TIMELY FASHION; AND 3) THE VOLUME OF TFC COLLECTING OVER A CORNERPOST PROHIBITS SPINNING ACFT WITHOUT A DETRIMENTAL RIPPLE EFFECT TO TRAILING ACFT (THERE IS NOWHERE TO SPIN THEM).

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