WRONG RTE ISSUED TO SMA X.

Date: 1994-06 · Aircraft: Skyhawk 172/Cutlass 172 · Phase: ground

Anomalies: deviation-discrepancy-procedural-published-material-policy|other-unspecified

Synopsis

WRONG RTE ISSUED TO SMA X.

Narrative

SMA X; A C172; HAD A FLT PLAN FILED TO CAK FROM ROA. THERE WERE 2 FLT PLANS; 1 SHOWING AIRWAYS WITH SOME ERRORS IN IT; AND THE SECOND WAS DIRECT TO SOME LATITUDES/LONGITUDES (PRESUMABLY CAK) DIRECT CAK. THIS STRIP HAD A NOTATION OF FRC INDICATING THAT THE RTE WAS NOT WHAT THE PLT FILED AND THAT WE SHOULD ISSUE A FULL RTE CLRNC. THE ACFT WAS NOT EQUIPPED WITH RNAV; SO THE DIRECT ROUTING WAS NOT FEASIBLE. ALTHOUGH NOT THE SUBJECT OF MY RPT; IT SHOULD BE NOTED THAT OUR FRIENDS AT FLT SVC; IF UNABLE TO GET A FLT PLAN INTO THE COMPUTER; WILL DO EXACTLY WHAT WAS DONE ON THE SECOND STRIP -- PUT IT IN DIRECT TO THE DEST AND PUT FRC IN THE REMARKS. SOMETIMES THEY FORGET TO PUT THE FRC IN; RESULTING IN A PF ONE RTE; AND THE CTLRS BELIEVING THAT ANOTHER RTE IS BEING FLOWN. IN THIS CASE; I WAS FAMILIAR WITH THE ROUTING DUE TO EXPERIENCE GAINED AT ANOTHER FACILITY. I LOOKED UP THE RTE ON A CHART TO VERIFY IT AND SHOWED IT TO THE CLRNC DELIVERY PERSON BEFORE THE ACFT CALLED. AS I CAME BACK UP AFTER A BREAK; I NOTICED THAT CLRNC HAD AMENDED THE FLT PLAN AND ISSUED THE CLRNC TO X. I NOTICED THAT THE ROUTING WAS DIFFERENT THAN I HAD SUGGESTED AND CONTAINED AN AIRWAY GOING TO A VOR THAT WAS NOT ON THAT AIRWAY. I BROUGHT THIS TO THE ATTN OF THE CLRNC PERSON; WHO SAID 'THE COMPUTER TOOK IT; SO IT'S ALL RIGHT.'

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.