ZFW CTLR TRACKS OBSERVES ACR SF34 FLC FAIL TO TURN ON COURSE. WHEN THE FLC IS CHALLENGED; PLT ADMITS TO FILED RTE CONFUSION; EXPECTING VECTORS TO DEST. CTLR RECOGNIZES THAT ACR CONSTANTLY FILES INCORRECT ROUTING TO SJT.

Date: 1999-03

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-published-material-policy|other-unspecified

Synopsis

ZFW CTLR TRACKS OBSERVES ACR SF34 FLC FAIL TO TURN ON COURSE. WHEN THE FLC IS CHALLENGED; PLT ADMITS TO FILED RTE CONFUSION; EXPECTING VECTORS TO DEST. CTLR RECOGNIZES THAT ACR CONSTANTLY FILES INCORRECT ROUTING TO SJT.

Narrative

ACFT #1 (X) WAS ON A SID WITH THE ABI TRANSITION. ACFT #2 (Y) WAS ON A SID TO AN ENRTE TRANSITION. ACFT #1 WAS TO PROCEED OVER MQP VOR; MQP 253 DEG RADIAL TO ABI 069 DEG RADIAL TO ABI. ACFT #2 WAS FILED MQP DIRECT SJT (147 NM) AND CLRED AS FILED (SF34 AND AT42/72'S ARE ALL SLANT A EQUIPPED '/A'). ACFT #2 WAS UNABLE TO NAV ON HIS FILED AND CLRED RTE. INSTEAD; THE PLT OF ACFT #2 DEPARTED MQP ON THE 253 DEG RADIAL. APPROX 10 MI W OF MQP; I NOTICED ACFT #2 N OF COURSE AND ASKED HIM ABOUT HIS HDG. THE PLT OF ACFT #2 ADVISED HE WAS TRACKING THE MQP 253 DEG RADIAL; NOT PROCEEDING DIRECT TO SJT. AT THAT TIME; THE ADJACENT SECTOR FORCED A DATA BLOCK ON ACFT #1 ONTO MY SCOPE. ACFT #2 WAS 7 MI BEHIND ACFT #1; AND 35 KTS FASTER. I TURNED ACFT #2 S AND THEN ISSUED A RADAR VECTOR TOWARD SJT FOR THE ACFT. ON QUESTIONING THE PLT OF ACFT #2; HE INDICATED THE RTE DOES NOT HAVE A KNOWN PROC FOR NAV (THAT THEY ARE AWARE OF) AND ARE GENERALLY EXPECTING A RADAR VECTOR. THE PLTS OF ACFT #2 ADMITTED CONFUSION REGARDING THEIR CLRNC AND MEANS OF NAV. I REVIEWED BOTH THE WORTH 1 AND THE COYOTE 3 SIDS. NEITHER HAS A PUBLISHED TRANSITION TO SJT. ZFW AUTOMATION INDICATES THE RTE IS A 'GARBAGE' RTE THAT ALLOWS AVOIDANCE OF IDENTING A PREFERENTIAL RTE. WE CANNOT FIND ANY RECORD OF THE RTE BEING FLT CHKED; AND WITH AN 80 NM SVC VOLUME NAVAID LIMITATION FOR COMMON TURBOPROP ALTS. ACFT #2 IS APPARENTLY FILING IMPROPER RTES VIA THEIR KNOWLEDGE OF OUR COMPUTER FLOWS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: ANALYST ASKED WHAT IN-HOUSE COORD HAD BEEN COMPLETED; IDENTING THE PROB AND A RESOLUTION. RPTR STATED THAT HE WAS CONCERNED WITH THE ABILITY OF AIRSPACE AND PROC TO RESOLVE THE PROB. ALTHOUGH HIS OPERATIONAL AREA HAS A SUPVR IDENTED WITH A COLLATERAL RESPONSIBILITY OVER THIS ISSUE; HE HAD NOT BROUGHT IT TO HIS 'COMPLETE' ATTN. THERE IS NO CTLR WORK GROUP AVAILABLE WITHIN HIS OPERATIONAL AREA TO RESOLVE PROCEDURAL ISSUES. THE RPTR ADVISED THAT RECENTLY; THE ACR FLYING THIS RTE HAS FILED AN ALT INTO THE STRATUM WHICH WILL ALLOW DIRECT VOR NAV; BUT 'EACH TIME THEY DEPART; THEY ASK FOR THE LOWER ALT;' THUS NEGATING THE VOR SVC NAV LIMITS; AND REQUEST RADAR VECTORS. THE RPTR WAS NOT AWARE OF ANY CONTACT WITH THE USER TO STATE THE ATC PROB OR TO ATTEMPT RESOLUTION.

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