Narrative:

Aircraft Y filed a flight plan via duats that was not in accordance with the aim. The NAS programming would not accept the flight plan as filed (because it was filed wrong) so duats put in whatever and placed 'frc' in the remarks. The first center sector did not review the flight plan so tys approach cleared the aircraft to the latitude/longitudes that duats placed in the flight plan (that was filed wrong) to 'make it work.' I finally forced the controller below me to fix it before I would accept the handoff. This problem has existed for several yrs and is growing. Not one single controller prior to my sector had any idea what fix this aircraft was proceeding direct to. We don't recognize latitude/longitudes. The computer does, but not the humans. Despite numerous attempts -- trouble reports, ucr's, NASA reports, aimed at numerous people -- pilots, controllers, mgrs, ATP-1 and duats personnel, no one will address the problem. FSS personnel are also placing latitude/longitudes in the flight plans. Controllers are doing it. Pilots are doing it. I have discovered numerous errors in the latitude/longitudes in the past. Several where the pilot was steering more than 90 degrees off course from the erroneous latitude/longitude. 1) pilot files flight plan that does not comply with aim 5-1-7. 2) duats inserts latitude/longitude to 'fix' flight plan that is still wrong. 3) flight plan prints at ZTL and 1ST center sector does not correct flight plan. 4) tys clearance delivery reads 'frc' to pilot including latitude/longitude. 5) aircraft departs, flight plan still hasn't been fixed. 6) aircraft transitions into 1ST center sector. Controller doesn't fix flight plan. 7) aircraft transitions into 2ND center sector. Controller doesn't fix flight plan. 8) I refuse handoff until the flight plan is fixed with the pilot flying over a recognizable fix.

Google
 

Original NASA ASRS Text

Title: ZTL CTLR EXPRESSED FRUSTRATION REGARDING FLT PLAN FILING AND PROCESSING INVOLVING BOTH PLTS AND CTLRS USING LAT AND LONGITUDES TO DEFINE A FLT PLAN RTE.

Narrative: ACFT Y FILED A FLT PLAN VIA DUATS THAT WAS NOT IN ACCORDANCE WITH THE AIM. THE NAS PROGRAMMING WOULD NOT ACCEPT THE FLT PLAN AS FILED (BECAUSE IT WAS FILED WRONG) SO DUATS PUT IN WHATEVER AND PLACED 'FRC' IN THE REMARKS. THE FIRST CTR SECTOR DID NOT REVIEW THE FLT PLAN SO TYS APCH CLRED THE ACFT TO THE LAT/LONGITUDES THAT DUATS PLACED IN THE FLT PLAN (THAT WAS FILED WRONG) TO 'MAKE IT WORK.' I FINALLY FORCED THE CTLR BELOW ME TO FIX IT BEFORE I WOULD ACCEPT THE HDOF. THIS PROB HAS EXISTED FOR SEVERAL YRS AND IS GROWING. NOT ONE SINGLE CTLR PRIOR TO MY SECTOR HAD ANY IDEA WHAT FIX THIS ACFT WAS PROCEEDING DIRECT TO. WE DON'T RECOGNIZE LAT/LONGITUDES. THE COMPUTER DOES, BUT NOT THE HUMANS. DESPITE NUMEROUS ATTEMPTS -- TROUBLE RPTS, UCR'S, NASA RPTS, AIMED AT NUMEROUS PEOPLE -- PLTS, CTLRS, MGRS, ATP-1 AND DUATS PERSONNEL, NO ONE WILL ADDRESS THE PROB. FSS PERSONNEL ARE ALSO PLACING LAT/LONGITUDES IN THE FLT PLANS. CTLRS ARE DOING IT. PLTS ARE DOING IT. I HAVE DISCOVERED NUMEROUS ERRORS IN THE LAT/LONGITUDES IN THE PAST. SEVERAL WHERE THE PLT WAS STEERING MORE THAN 90 DEGS OFF COURSE FROM THE ERRONEOUS LAT/LONGITUDE. 1) PLT FILES FLT PLAN THAT DOES NOT COMPLY WITH AIM 5-1-7. 2) DUATS INSERTS LAT/LONGITUDE TO 'FIX' FLT PLAN THAT IS STILL WRONG. 3) FLT PLAN PRINTS AT ZTL AND 1ST CTR SECTOR DOES NOT CORRECT FLT PLAN. 4) TYS CLRNC DELIVERY READS 'FRC' TO PLT INCLUDING LAT/LONGITUDE. 5) ACFT DEPARTS, FLT PLAN STILL HASN'T BEEN FIXED. 6) ACFT TRANSITIONS INTO 1ST CTR SECTOR. CTLR DOESN'T FIX FLT PLAN. 7) ACFT TRANSITIONS INTO 2ND CTR SECTOR. CTLR DOESN'T FIX FLT PLAN. 8) I REFUSE HDOF UNTIL THE FLT PLAN IS FIXED WITH THE PLT FLYING OVER A RECOGNIZABLE FIX.

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.