Narrative:

A C560/G filed jqf, latitude/longitude, dtw, FL390. I was working moped sector alone. I noticed that aircraft X hadn't filed the appropriate routing and corrected it, putting 'full route clearance' in remarks. Moments later, I noticed tmu had issued a WX rerte to an air carrier departing clt. I called the supervisor down to inquire about the WX rerte. A WX rerte was in effect and I hadn't been informed. Aircraft X departed about this time (XP26Z). Before I could get the strip in the bay, I got a remove strips message on aircraft X. I pulled up the data block to determine who had track controller. Aircraft X was within 5 mi of jqf. The computer responded that there was no track on aircraft X, even though I was looking at it. About 60 seconds later, the track dropped off. Tmu had amended the route. The data block, acquired on sector 28 because the computer was now processing the flight at FL390. Sector 28 dropped the track. Clt made a manual handoff to me. Aircraft X was now cleared via hmv iiu. No coordination on the route. As soon as aircraft X checked on, he asked for a rerte to det. The pilot claims he intended to go to det all along, but the wrong identify got in the flight plan (mysteriously). I hope you can count all the little errors in this report. This is indicative of operations at ZTL these days. I don't have to tell you that aviation accidents are caused by several errors put together. We have a lot of errors these days.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZTL CTLR CONCERNED WITH INTRAFAC, WX RERTE COORD FAILURES.

Narrative: A C560/G FILED JQF, LATITUDE/LONGITUDE, DTW, FL390. I WAS WORKING MOPED SECTOR ALONE. I NOTICED THAT ACFT X HADN'T FILED THE APPROPRIATE ROUTING AND CORRECTED IT, PUTTING 'FULL RTE CLRNC' IN REMARKS. MOMENTS LATER, I NOTICED TMU HAD ISSUED A WX RERTE TO AN ACR DEPARTING CLT. I CALLED THE SUPVR DOWN TO INQUIRE ABOUT THE WX RERTE. A WX RERTE WAS IN EFFECT AND I HADN'T BEEN INFORMED. ACFT X DEPARTED ABOUT THIS TIME (XP26Z). BEFORE I COULD GET THE STRIP IN THE BAY, I GOT A REMOVE STRIPS MESSAGE ON ACFT X. I PULLED UP THE DATA BLOCK TO DETERMINE WHO HAD TRACK CTLR. ACFT X WAS WITHIN 5 MI OF JQF. THE COMPUTER RESPONDED THAT THERE WAS NO TRACK ON ACFT X, EVEN THOUGH I WAS LOOKING AT IT. ABOUT 60 SECONDS LATER, THE TRACK DROPPED OFF. TMU HAD AMENDED THE RTE. THE DATA BLOCK, ACQUIRED ON SECTOR 28 BECAUSE THE COMPUTER WAS NOW PROCESSING THE FLT AT FL390. SECTOR 28 DROPPED THE TRACK. CLT MADE A MANUAL HDOF TO ME. ACFT X WAS NOW CLRED VIA HMV IIU. NO COORD ON THE RTE. AS SOON AS ACFT X CHKED ON, HE ASKED FOR A RERTE TO DET. THE PLT CLAIMS HE INTENDED TO GO TO DET ALL ALONG, BUT THE WRONG IDENT GOT IN THE FLT PLAN (MYSTERIOUSLY). I HOPE YOU CAN COUNT ALL THE LITTLE ERRORS IN THIS RPT. THIS IS INDICATIVE OF OPS AT ZTL THESE DAYS. I DON'T HAVE TO TELL YOU THAT AVIATION ACCIDENTS ARE CAUSED BY SEVERAL ERRORS PUT TOGETHER. WE HAVE A LOT OF ERRORS THESE DAYS.

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.