Narrative:

Small aircraft X reported on my frequency. I had no prior knowledge of the aircraft and when he reported on the frequency there was confusion because in addition to having no prior knowledge, the only flight plan information we had was on another aircraft and the data block on the aircraft was small aircraft X, a call sign normally used for VFR aircraft between orl and mco approach. I am not sure at what point the data block displayed on the scope, but the first time I realized where the aircraft was, or at least the data block, small aircraft X was about 5 mi from the departure end of the runway and he had traffic in his 1 O'clock and 1 1/2 mi, small aircraft Y, who had departed orl ahead of him on an IFR flight plan. Small aircraft X was also IFR and orl had cleared him for takeoff believing him to be VFR. Supplemental information from acn 233947: I was working the satellite coordinator position at mco. Orlando executive's departures were on a call for release basis. Small aircraft Y was released and airborne. Very shortly thereafter, small aircraft X was observed departing orlando executive airport. Executive tower called on the landline and said small aircraft X had accidentally gotten off the airport (no release obtained or given). The separation between small aircraft Y and small aircraft X at this point was 1 1/2 mi and 500 ft. The departure controller called the traffic and small aircraft X said he did not have the previous departure in sight -- small aircraft Y was then issued a turn and separation was achieved.

Related reports:

Google
 

Original NASA ASRS Text

Title: ATCT TRACON INTERFAC COORD SMA X RELEASED WITH LTSS BEHIND SMA Y. SYS ERROR.

Narrative: SMA X RPTED ON MY FREQ. I HAD NO PRIOR KNOWLEDGE OF THE ACFT AND WHEN HE RPTED ON THE FREQ THERE WAS CONFUSION BECAUSE IN ADDITION TO HAVING NO PRIOR KNOWLEDGE, THE ONLY FLT PLAN INFO WE HAD WAS ON ANOTHER ACFT AND THE DATA BLOCK ON THE ACFT WAS SMA X, A CALL SIGN NORMALLY USED FOR VFR ACFT BTWN ORL AND MCO APCH. I AM NOT SURE AT WHAT POINT THE DATA BLOCK DISPLAYED ON THE SCOPE, BUT THE FIRST TIME I REALIZED WHERE THE ACFT WAS, OR AT LEAST THE DATA BLOCK, SMA X WAS ABOUT 5 MI FROM THE DEP END OF THE RWY AND HE HAD TFC IN HIS 1 O'CLOCK AND 1 1/2 MI, SMA Y, WHO HAD DEPARTED ORL AHEAD OF HIM ON AN IFR FLT PLAN. SMA X WAS ALSO IFR AND ORL HAD CLRED HIM FOR TKOF BELIEVING HIM TO BE VFR. SUPPLEMENTAL INFO FROM ACN 233947: I WAS WORKING THE SATELLITE COORDINATOR POS AT MCO. ORLANDO EXECUTIVE'S DEPS WERE ON A CALL FOR RELEASE BASIS. SMA Y WAS RELEASED AND AIRBORNE. VERY SHORTLY THEREAFTER, SMA X WAS OBSERVED DEPARTING ORLANDO EXECUTIVE ARPT. EXECUTIVE TWR CALLED ON THE LANDLINE AND SAID SMA X HAD ACCIDENTALLY GOTTEN OFF THE ARPT (NO RELEASE OBTAINED OR GIVEN). THE SEPARATION BTWN SMA Y AND SMA X AT THIS POINT WAS 1 1/2 MI AND 500 FT. THE DEP CTLR CALLED THE TFC AND SMA X SAID HE DID NOT HAVE THE PREVIOUS DEP IN SIGHT -- SMA Y WAS THEN ISSUED A TURN AND SEPARATION WAS ACHIEVED.

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