Narrative:

A tfr over bkw airport was scheduled to void at XA00z. At XA01z I asked the r-controller at azq low if the vip aircraft had departed. He stated that he had seen neither depart. Bkw is part of crw approach; but ZID owns 110 and above over bkw. I called crw approach and they verified that both vip aircraft were still on the ground. Do we extend the tfr? Crw approach said yes. So I verified that we would extend the tfr until further advised. On the ground at blf was an aircraft waiting for the tfr to end so that he could fly from blf to bkw. He knew when the tfr was scheduled to end; and wisely checked with the azq low controller before departing for bkw. Several minutes later; crw approach appred'ed one vip aircraft departing off of bkw and asked for higher than 100; the azq low controller released it to FL210. A few minutes later; a limited data block squawking the code assigned to the vip aircraft was observed just south of bkw; climbing and turning east. We then observed on uret (user request evaluation tool) that the flight had been handed off to ZDC sector 22. There was no coordination from crw approach about bypassing the azq low sector; and no call that the first vip aircraft had cleared our airspace. Recommendation; ZID should have been advised well before the tfr timed out that it was still needed. It should have been coordinated with the watch desk; who would have advised the affected sectors. Additionally; there should have been some notification sent via the NOTAMS to warn pilots that the tfr was being extended. Crw approach should have handed the first vip aircraft off to the azq low sector; rather than bypassing it without coordination.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZID Controller voiced concern that a TFR covering VIP aircraft movements within CRW TRACON airspace was extended but no notification provided to controllers or pilots.

Narrative: A TFR over BKW airport was scheduled to void at XA00z. At XA01z I asked the R-Controller at AZQ LOW if the VIP aircraft had departed. He stated that he had seen neither depart. BKW is part of CRW Approach; but ZID owns 110 and above over BKW. I called CRW Approach and they verified that both VIP aircraft were still on the ground. Do we extend the TFR? CRW Approach said yes. So I verified that we would extend the TFR until further advised. On the ground at BLF was an aircraft waiting for the TFR to end so that he could fly from BLF to BKW. He knew when the TFR was scheduled to end; and wisely checked with the AZQ LOW Controller before departing for BKW. Several minutes later; CRW Approach APPRED'ed one VIP aircraft departing off of BKW and asked for higher than 100; the AZQ LOW Controller released it to FL210. A few minutes later; a limited data block squawking the code assigned to the VIP aircraft was observed just south of BKW; climbing and turning east. We then observed on URET (User Request Evaluation Tool) that the flight had been handed off to ZDC Sector 22. There was no coordination from CRW Approach about bypassing the AZQ LOW sector; and no call that the first VIP aircraft had cleared our airspace. Recommendation; ZID should have been advised well before the TFR timed out that it was still needed. It should have been coordinated with the watch desk; who would have advised the affected sectors. Additionally; there should have been some notification sent via the NOTAMS to warn pilots that the TFR was being extended. CRW Approach should have handed the first VIP aircraft off to the AZQ LOW sector; rather than bypassing it without coordination.

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