Narrative:

Abb sector from ZID called regarding a handoff I had just accepted via automated means. The cessna 310 was entering my airspace from the south; and the track would take the aircraft through huf approach's airspace for approximately 8 NM before reaching my airspace. Normally; this type of coordination means abb sector would have received a point out from huf prior to transferring control to me. When the 310 was nearly at the abb/huf boundary (within 30 sec and 2 NM); abb called me asking if huf had coordinated the point out by any chance -- abb could not reach huf via any means of communication. I said I would try to call huf. While I was trying the shout line; abb switched the 310 to my frequency. The 310 continued through huf airspace for a few miles then transited my airspace without incident. Meanwhile; my TRACON controller in charge attempted to establish contact with huf; but was unsuccessful. After approximately 20 minutes ZID assumed responsibility for huf's airspace because of a communication issue. Recommendation; the root cause of this incident can better be established from a tech ops perspective. However; the high reliability of automation and equipment has established an expectation that all coordination will be accomplished nearly instantaneously. This is a reminder that we should not take procedural due diligence for granted. When I am handing an aircraft off to another controller in the future; I will be careful to establish all coordination in a timely manner; so as to accomplish the coordination prior to an airspace boundary.

Related reports:

Google
 

Original NASA ASRS Text

Title: IND Controller described an airspace incursion when equipment malfunctions and non-adherence to procedures resulted in the event.

Narrative: ABB sector from ZID called regarding a handoff I had just accepted via automated means. The Cessna 310 was entering my airspace from the south; and the track would take the aircraft through HUF Approach's airspace for approximately 8 NM before reaching my airspace. Normally; this type of coordination means ABB sector would have received a point out from HUF prior to transferring control to me. When the 310 was nearly at the ABB/HUF boundary (within 30 sec and 2 NM); ABB called me asking if HUF had coordinated the point out by any chance -- ABB could not reach HUF via any means of communication. I said I would try to call HUF. While I was trying the shout line; ABB switched the 310 to my frequency. The 310 continued through HUF airspace for a few miles then transited my airspace without incident. Meanwhile; my TRACON CIC attempted to establish contact with HUF; but was unsuccessful. After approximately 20 minutes ZID assumed responsibility for HUF's airspace because of a communication issue. Recommendation; the root cause of this incident can better be established from a Tech Ops perspective. However; the high reliability of automation and equipment has established an expectation that all coordination will be accomplished nearly instantaneously. This is a reminder that we should not take procedural due diligence for granted. When I am handing an aircraft off to another controller in the future; I will be careful to establish all coordination in a timely manner; so as to accomplish the coordination prior to an airspace boundary.

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