Enroute controller described a failed coordination event between facility controllers and the pilot ...

Narrative:

Today commander 114 originally called sector xx to pick up flight following. The controller placed the aircraft on approach frequency since he was still in that airspace. With approach; the aircraft picked up an IFR clearance and continued onto his destination. After entering sector xx; the controller confirmed that he had the weather and NOTAMS and cleared him for the GPS approach in IFR conditions. Another controller then plugged into the sector to relieve the sector. Before the briefing started the controller being relieved cleared the aircraft to CTAF and asked the relieving controller if he/she got that. All acknowledged and then the recorded briefing began. The controller being relieved indicated that he/she thought about the aircraft but lost track of time and thought that that the aircraft had cancelled. It was not until the relieved controller came back from break that a data block was still there. The two controllers questioned each other about the aircraft and that is the first time that I knew about the incident. I gathered the strip and the information and immediately called the front desk so that an alnot could be issued. I have spoken to the controllers involved and they are aware of the severity of the incident. I told them to make sure that information is on the recorded briefing and to not keep anything to themselves.

Original NASA ASRS Text

Title: Enroute Controller described a failed coordination event between facility controllers and the pilot of an aircraft inbound to a non-towered airport that resulted an ALNOT and Search and Rescue intervention.

Narrative: Today Commander 114 originally called Sector XX to pick up flight following. The Controller placed the aircraft on Approach frequency since he was still in that airspace. With Approach; the aircraft picked up an IFR clearance and continued onto his destination. After entering Sector XX; the Controller confirmed that he had the weather and NOTAMS and cleared him for the GPS approach in IFR conditions. Another Controller then plugged into the sector to relieve the sector. Before the briefing started the Controller being relieved cleared the aircraft to CTAF and asked the relieving Controller if he/she got that. All acknowledged and then the recorded briefing began. The Controller being relieved indicated that he/she thought about the aircraft but lost track of time and thought that that the aircraft had cancelled. It was not until the relieved Controller came back from break that a data block was still there. The two Controllers questioned each other about the aircraft and that is the first time that I knew about the incident. I gathered the strip and the information and immediately called the front desk so that an ALNOT could be issued. I have spoken to the Controllers involved and they are aware of the severity of the incident. I told them to make sure that information is on the recorded briefing and to not keep anything to themselves.

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

Attributes
ACN	1056880
Time
Date	201212
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Aircraft 1
Make Model Name	Commander 114/A/B/TC
Flight Phase	Parked
Flight Plan	IFR
Person 1
Function	Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

Enroute controller described a failed coordination event between facility controllers and the pilot of an aircraft inbound to a non-towered airport that resulted an alnot and search and rescue intervention.