Narrative:

I was working ground control combined with clearance delivery/flight data and cabin attendant coordinator when a PA32 called for an IFR clearance to 16J. There was no clearance posted for this aircraft and I advised the aircraft clearance on request. The aircraft requested to taxi while waiting for the IFR clearance. I gave the aircraft taxi instructions to runway 9R; informed the aircraft to remain on my frequency and then tried to retrieve the IFR clearance manually from the fdio and found that there was no squawk code; because the proposed time was further out than 30 mins. I then amended the proposed time to receive a squawk code. Now having the squawk code I started to formulate the strip marking as required. I was not familiar with the airport 16J; so I did not know what heading to mark on the departure strip. I then asked the pilot for his on course heading to 16J. The pilot gave me the on course heading and I placed the appropriate heading; departure frequency; squawk code and runway assignment on the IFR departure strip. I gave the aircraft the IFR clearance and then I believe I started to receive other calls on ground and got preoccupied with the other aircraft that had been standing by; while I was working on the IFR clearance. I placed the strip at the local 2 position without making and receiving the correct automated coordination with orlando approach through the stars. The aircraft called LC2 for departure and received a takeoff clearance. LC2 does not get the coordination list displayed on his stars rtdw; as it is at the LC1 stars rtdw; indicating the needed coordination for taxi with orlando approach. No separation was lost at any time. I believe the combining of FD/clearance delivery to ground control and the lack of the coordination list being displayed at the LC2 stars rtdw were the main contributors to the missed coordination.

Related reports:

Google
 

Original NASA ASRS Text

Title: SFB CTLR DESCRIBED COORD FAILURE EVENT WHEN AUTOMATED COORD WAS NOT COMPLETED; CITING POSITION COMBINATION WORKLOADS AS CONTRIBUTORY.

Narrative: I WAS WORKING GND CTL COMBINED WITH CLRNC DELIVERY/FLT DATA AND CAB COORDINATOR WHEN A PA32 CALLED FOR AN IFR CLRNC TO 16J. THERE WAS NO CLRNC POSTED FOR THIS ACFT AND I ADVISED THE ACFT CLRNC ON REQUEST. THE ACFT REQUESTED TO TAXI WHILE WAITING FOR THE IFR CLRNC. I GAVE THE ACFT TAXI INSTRUCTIONS TO RWY 9R; INFORMED THE ACFT TO REMAIN ON MY FREQ AND THEN TRIED TO RETRIEVE THE IFR CLRNC MANUALLY FROM THE FDIO AND FOUND THAT THERE WAS NO SQUAWK CODE; BECAUSE THE PROPOSED TIME WAS FURTHER OUT THAN 30 MINS. I THEN AMENDED THE PROPOSED TIME TO RECEIVE A SQUAWK CODE. NOW HAVING THE SQUAWK CODE I STARTED TO FORMULATE THE STRIP MARKING AS REQUIRED. I WAS NOT FAMILIAR WITH THE ARPT 16J; SO I DID NOT KNOW WHAT HDG TO MARK ON THE DEP STRIP. I THEN ASKED THE PLT FOR HIS ON COURSE HDG TO 16J. THE PLT GAVE ME THE ON COURSE HDG AND I PLACED THE APPROPRIATE HDG; DEP FREQ; SQUAWK CODE AND RWY ASSIGNMENT ON THE IFR DEP STRIP. I GAVE THE ACFT THE IFR CLRNC AND THEN I BELIEVE I STARTED TO RECEIVE OTHER CALLS ON GND AND GOT PREOCCUPIED WITH THE OTHER ACFT THAT HAD BEEN STANDING BY; WHILE I WAS WORKING ON THE IFR CLRNC. I PLACED THE STRIP AT THE LCL 2 POS WITHOUT MAKING AND RECEIVING THE CORRECT AUTOMATED COORD WITH ORLANDO APCH THROUGH THE STARS. THE ACFT CALLED LC2 FOR DEP AND RECEIVED A TKOF CLRNC. LC2 DOES NOT GET THE COORD LIST DISPLAYED ON HIS STARS RTDW; AS IT IS AT THE LC1 STARS RTDW; INDICATING THE NEEDED COORD FOR TAXI WITH ORLANDO APCH. NO SEPARATION WAS LOST AT ANY TIME. I BELIEVE THE COMBINING OF FD/CD TO GC AND THE LACK OF THE COORD LIST BEING DISPLAYED AT THE LC2 STARS RTDW WERE THE MAIN CONTRIBUTORS TO THE MISSED COORD.

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