Narrative:

Swo tower earlier called for a clearance; hold for release on aircraft X. They called for release and were given 050. They responded to 'show him off in 3 minutes.' the aircraft was not departed from the departure list. At xa:17 the aircraft called up and was given an altimeter. It was around this time a d-side sat down and with how busy I was I thought the aircraft just had yet to tag up and did not realize it had not been departed. The coast track remained over swo airport and at xa:37 a new d-side called the tower to inquire about aircraft X who said he had departed roughly 20 minutes prior. I transmitted to the aircraft; who had never been radar identified who was now level at 050 and inside tul approach airspace. Once departed he tagged up and the d-side called tul to coordinate further with the airspace violation. Swo tower is one of our busiest airports and does not have fdio (flight data input/output). According to the LOA departures are supposed to be within 2 minutes and require a call to say the aircraft is rolling/departing. They have become lax about this; and we have as well by accepting it. I have seen this problem occur before; as well as swo calling for a release; the aircraft being departed from the departure list; and then because they weren't actually rolling yet the tower calling back to cancel the release. This causes problems as well with saving flight plans and the potential for flight plans not being removed and later on showing as overdue. Fdio would solve this.

Google
 

Original NASA ASRS Text

Title: ZKC Developmental reported of releasing an aircraft off of a controlled airport and not getting radar contact on it until 24 minutes after it departed. This aircraft also violated another Approach Control's airspace. Procedure to call reporting the aircraft as rolling or departing; is reportedly not being followed.

Narrative: SWO tower earlier called for a clearance; hold for release on Aircraft X. They called for release and were given 050. They responded to 'show him off in 3 minutes.' The aircraft was not departed from the departure list. At XA:17 the aircraft called up and was given an altimeter. It was around this time a D-side sat down and with how busy I was I thought the aircraft just had yet to tag up and did not realize it had not been departed. The coast track remained over SWO airport and at XA:37 a new D-side called the tower to inquire about Aircraft X who said he had departed roughly 20 minutes prior. I transmitted to the aircraft; who had never been radar identified who was now level at 050 and inside TUL approach airspace. Once departed he tagged up and the D-side called TUL to coordinate further with the airspace violation. SWO tower is one of our busiest airports and does not have FDIO (Flight Data Input/Output). According to the LOA departures are supposed to be within 2 minutes and require a call to say the aircraft is rolling/departing. They have become lax about this; and we have as well by accepting it. I have seen this problem occur before; as well as SWO calling for a release; the aircraft being departed from the departure list; and then because they weren't actually rolling yet the tower calling back to cancel the release. This causes problems as well with saving flight plans and the potential for flight plans not being removed and later on showing as overdue. FDIO would solve this.

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.