Narrative:

Aircraft X was flying VFR to [destination] at 6;500 feet and needed to be radar identified as I believe approach had only started a VFR plan but did not complete radar identification. I was just starting my shift for the day and was to be the radar controller. However; the approach was limited ATC and we had acquired their airspace. Aircraft X checked on and was radar identified; at which time he informed ZAU that he wanted to stay VFR/045. Between other communications with other aircraft aircraft X was trying to get in touch with ATC; I made 3 attempts to contact him to see what his intentions were as his altitude was descending and he was making a turn. Aircraft X responded; however; I could not make out the complete transmission besides cancel VFR and asked him to repeat. He then informed us that he was canceling VFR flight following as the weather was too low to continue and he was going to return to his airport. I verified he requested to cancel and return to his airport when he was descending below the mia. VFR was canceled and 1200 was squawked as my d-side rerouted the aircraft back to its departure point and the datablock was dropped. It was not until several hours later was I informed there was an alnot out for this aircraft as the flight plan still transmitted to [original destination] and overdue. After informing the supervisors the aircraft had correctly canceled due to weather and stayed in VFR conditions; and they saw on the falcon [replay computer] that the flight plan had changed that the search had stopped. I was also informed they had listened to the tapes to check on his whereabouts. Even with this happening they did not realize the VFR cancelation.first recommendation would be to check the eram system on why the flight plan did not drop from [original destination tower flight data]. Second would be to separate the approach control to its own sector as this is rarely worked by most controllers in the area and extremely rare circumstance at ZAU. Third would be extra diligence in checking the tapes as the aircraft had canceled and seems to have said ZZZ1 on the tapes as return airport. As well the flight plan was entered through approach.

Google
 

Original NASA ASRS Text

Title: An aircraft on a VFR Flight Plan cancelled flight following and advised Center they were turning around for weather to land. The ARTCC controllers amended the flight plan to route the aircraft flight plan back to its departure airport. The destination Tower did not notice the revision or the software did not process the revision to the destination Tower. They correctly assumed the aircraft was overdue. An ALNOT was issued and search procedures for the aircraft were initiated. ARTCC Supervisors and controllers who worked the aircraft at the ARTCC researched sector recordings and radar display replays. They discovered the aircraft had cancelled on the ARTCC frequency and returned to an airport other than its original departure airport.

Narrative: Aircraft X was flying VFR to [destination] at 6;500 feet and needed to be radar identified as I believe approach had only started a VFR plan but did not complete radar identification. I was just starting my shift for the day and was to be the radar controller. However; the approach was limited ATC and we had acquired their airspace. Aircraft X checked on and was radar identified; at which time he informed ZAU that he wanted to stay VFR/045. Between other communications with other aircraft Aircraft X was trying to get in touch with ATC; I made 3 attempts to contact him to see what his intentions were as his altitude was descending and he was making a turn. Aircraft X responded; however; I could not make out the complete transmission besides cancel VFR and asked him to repeat. He then informed us that he was canceling VFR flight following as the weather was too low to continue and he was going to return to his airport. I verified he requested to cancel and return to his airport when he was descending below the MIA. VFR was canceled and 1200 was squawked as my D-side rerouted the aircraft back to its departure point and the datablock was dropped. It was not until several hours later was I informed there was an ALNOT out for this aircraft as the flight plan still transmitted to [original destination] and overdue. After informing the supervisors the aircraft had correctly canceled due to weather and stayed in VFR conditions; and they saw on the FALCON [replay computer] that the flight plan had changed that the search had stopped. I was also informed they had listened to the tapes to check on his whereabouts. Even with this happening they did not realize the VFR cancelation.First recommendation would be to check the ERAM system on why the flight plan did not drop from [original destination tower flight data]. Second would be to separate the approach control to its own sector as this is rarely worked by most controllers in the area and extremely rare circumstance at ZAU. Third would be extra diligence in checking the tapes as the aircraft had canceled and seems to have said ZZZ1 on the tapes as return airport. As well the flight plan was entered through approach.

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.