Narrative:

Aircraft X was on an IFR flight plan; destination svn. The prior sector placed ILS in the scratchpad and handed the aircraft off to me. Svn only has one ILS which is to runway 28; although runway 10 was in use. Since I received the aircraft with ILS in the scratchpad I assumed the verbal opposite direction coordination was already completed by the previous sector. I initiated a hand off to svn tower using automation and the approach to the opposite direction runway was clearly visible in the scratchpad. Svn accepted the automated hand off approximately 15 miles away from the airport. I cleared the aircraft and switched [them] at approximately a 10 mile final. It was only after clearing the aircraft for the ILS and transferring communications that I had realized the coordination was not completed. At this point aircraft X was on a short final. I then called svn tower to let them know I was aware of the missed coordination and it was entirely my fault and they implied that they were aware of the aircraft's intentions and the event was a nonissue. It is important to note that svn does not have automatic releases and no other aircraft were affected by the missed coordination. No recommendations. This was a situation where I did not apply the correct procedures as outlined in our LOA due to an inaccurate assumption.

Related reports:

Google
 

Original NASA ASRS Text

Title: A SAV Tracon Controller accepts a handoff on an aircraft that has an ILS in the scratch pad area. The ILS refers to the ILS for runway 28; but 10 is in use. The Controller assumes coordination has been done; hands off aircraft; and flashes the aircraft to Tower. The Controller then realizes; with aircraft on a 10 mile final; that coordination hasn't been done and then coordinates with the Tower. Tower advises there is no problem; they see the scratch pad. The Tower does not have automatic releases.

Narrative: Aircraft X was on an IFR flight plan; destination SVN. The prior sector placed ILS in the scratchpad and handed the aircraft off to me. SVN only has one ILS which is to runway 28; although Runway 10 was in use. Since I received the aircraft with ILS in the scratchpad I assumed the verbal opposite direction coordination was already completed by the previous sector. I initiated a hand off to SVN Tower using automation and the approach to the opposite direction runway was clearly visible in the scratchpad. SVN accepted the automated hand off approximately 15 miles away from the airport. I cleared the aircraft and switched [them] at approximately a 10 mile final. It was only after clearing the aircraft for the ILS and transferring communications that I had realized the coordination was not completed. At this point Aircraft X was on a short final. I then called SVN Tower to let them know I was aware of the missed coordination and it was entirely my fault and they implied that they were aware of the aircraft's intentions and the event was a nonissue. It is important to note that SVN does not have automatic releases and no other aircraft were affected by the missed coordination. No recommendations. This was a situation where I did not apply the correct procedures as outlined in our LOA due to an inaccurate assumption.

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.