ZFW controller described operational deviation when all landline communication with tul approach fai...

Attributes
ACN	765810
Time
Date	200712
Local Time Of Day	1801 To 2400
Place
Locale Reference	navaid : okm.vor
State Reference	OK
Altitude	msl single value : 10000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zfw.artcc
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar controller : handoff position
Qualification	controller : radar
Experience	controller radar : 20 controller time certified in position1 : 10
ASRS Report	765810
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	FAA
Primary Problem	FAA

Narrative:

I was working the mlc sector. To the best of my knowledge everything except for the #5 shout line to tul approach was in working order. I was notified by my supervisor that the #5 shout line to tul approach was going to be taken OTS. At about XA19Z I called tul approach on the dial line to make sure that I was going to be able to have communications with them. I was never advised of any other problems with the approach; and that it was normal operations. Approximately 20 mins later I called tul approach on the dial line and then on the shout line attempting to handoff aircraft X. When they didn't answer either line I turned aircraft X to the southeast and then south to exit their airspace. I advised my supervisor that I might have had an airspace deviation. I asked aircraft X to switch to tul approach on 124.0 to see if they could talk to anyone. He returned and told me that the controllers at tul approach advised that they were ATC zero. I advised my supervisor of the tul situation. I then cleared aircraft X and another company jet that was in-trail to mlc to hold. I was told by my supervisor that ZKC (who takes over the airspace in event of ATC zero at tul) was not aware of tul being ATC zero. I then got a call from ZME also wanting to know if I could get hold of tul and that an aircraft had told them that tul was ATC zero.

Original NASA ASRS Text

Title: ZFW CTLR DESCRIBED OPDEV WHEN ALL LANDLINE COM WITH TUL APCH FAILED AND ARRS CROSSED AIRSPACE BOUNDARY BEFORE HDOF.

Narrative: I WAS WORKING THE MLC SECTOR. TO THE BEST OF MY KNOWLEDGE EVERYTHING EXCEPT FOR THE #5 SHOUT LINE TO TUL APCH WAS IN WORKING ORDER. I WAS NOTIFIED BY MY SUPVR THAT THE #5 SHOUT LINE TO TUL APCH WAS GOING TO BE TAKEN OTS. AT ABOUT XA19Z I CALLED TUL APCH ON THE DIAL LINE TO MAKE SURE THAT I WAS GOING TO BE ABLE TO HAVE COMS WITH THEM. I WAS NEVER ADVISED OF ANY OTHER PROBS WITH THE APCH; AND THAT IT WAS NORMAL OPS. APPROX 20 MINS LATER I CALLED TUL APCH ON THE DIAL LINE AND THEN ON THE SHOUT LINE ATTEMPTING TO HDOF ACFT X. WHEN THEY DIDN'T ANSWER EITHER LINE I TURNED ACFT X TO THE SE AND THEN S TO EXIT THEIR AIRSPACE. I ADVISED MY SUPVR THAT I MIGHT HAVE HAD AN AIRSPACE DEV. I ASKED ACFT X TO SWITCH TO TUL APCH ON 124.0 TO SEE IF THEY COULD TALK TO ANYONE. HE RETURNED AND TOLD ME THAT THE CTLRS AT TUL APCH ADVISED THAT THEY WERE ATC ZERO. I ADVISED MY SUPVR OF THE TUL SIT. I THEN CLRED ACFT X AND ANOTHER COMPANY JET THAT WAS IN-TRAIL TO MLC TO HOLD. I WAS TOLD BY MY SUPVR THAT ZKC (WHO TAKES OVER THE AIRSPACE IN EVENT OF ATC ZERO AT TUL) WAS NOT AWARE OF TUL BEING ATC ZERO. I THEN GOT A CALL FROM ZME ALSO WANTING TO KNOW IF I COULD GET HOLD OF TUL AND THAT AN ACFT HAD TOLD THEM THAT TUL WAS ATC ZERO.

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.

ZFW controller described operational deviation when all landline communication with tul approach failed and arrs crossed airspace boundary before handoff.