Narrative:

I was giving OJT on mll low D side. We received a manual handoff on aircraft X departing fsm landing xra. Normally this aircraft would never enter our airspace but he was deviating around WX. We attempted numerous times to put a vp flight plan in (because it can be input faster than amended) and the computer showed accepted but when we 'fr' him there was only call sign; code and altitude; so we tried a flight plan message that also showed accepted but had the same results. I was making notes on the input by the trainee while the manual handoff was being made and didn't notice the aircraft had penetrated zcm airspace prior to handoff. I am still perplexed by how the host showed accept on the flight plan messages and still showed no flight plan in and passed to zcm.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZFW INSTRUCTOR CTLR EXPERIENCED DIFFICULTIES IN ENTERING FLT PLAN INFO IN THE COMPUTER RESULTED IN AN UNAUTH AIRSPACE ENTRY.

Narrative: I WAS GIVING OJT ON MLL LOW D SIDE. WE RECEIVED A MANUAL HDOF ON ACFT X DEPARTING FSM LNDG XRA. NORMALLY THIS ACFT WOULD NEVER ENTER OUR AIRSPACE BUT HE WAS DEVIATING AROUND WX. WE ATTEMPTED NUMEROUS TIMES TO PUT A VP FLT PLAN IN (BECAUSE IT CAN BE INPUT FASTER THAN AMENDED) AND THE COMPUTER SHOWED ACCEPTED BUT WHEN WE 'FR' HIM THERE WAS ONLY CALL SIGN; CODE AND ALTITUDE; SO WE TRIED A FLT PLAN MESSAGE THAT ALSO SHOWED ACCEPTED BUT HAD THE SAME RESULTS. I WAS MAKING NOTES ON THE INPUT BY THE TRAINEE WHILE THE MANUAL HDOF WAS BEING MADE AND DIDN'T NOTICE THE ACFT HAD PENETRATED ZCM AIRSPACE PRIOR TO HDOF. I AM STILL PERPLEXED BY HOW THE HOST SHOWED ACCEPT ON THE FLT PLAN MESSAGES AND STILL SHOWED NO FLT PLAN IN AND PASSED TO ZCM.

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.