TRACK DEV.

Date: 1995-03 · Aircraft: SF 340A

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|other-unspecified

Synopsis

TRACK DEV.

Narrative

AFTER TKOF; WE FLEW HDG 050 DEGS ASSIGNED. DEP CTL CLRED US DIRECT AZQ VOR. I PROCEEDED TO ENTER THE VOR NAVAID INTO THE KNS 660 RNAV COMPUTER. HOWEVER; INSTEAD OF THE CORRECT IDENT AZQ; I MISTAKENLY ENTERED AZO. THIS CAUSED A 30-40 DEG DEV FROM THE COURSE. THE FREQ FOR AZQ VOR WAS NOT VERIFIED BY USE OF NAV CHARTS OR MORSE CODE. INSTEAD WE USED THE FREQ OF THE RNAV BOX AND OMITTED TO IDENT PROPER FREQ BY MORSE CODE. THE RED VOR FLAG WAS ALSO NOT NOTICED. ZID QUESTIONED OUR COURSE AND GAVE US A NEW VECTOR OF HDG 030 DEGS TO INTERCEPT THE FLM 150 DEG RADIAL. A CONFLICT WAS NOT CREATED. IT IS ESSENTIAL TO IDENT AND VERIFY NAVAID FREQS BY USE OF PROPER NAV CHARTS AND MORSE CODE. FAILURE TO DO SO CAUSED OUR DEV. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THIS WAS THE FIRST TRIP TOGETHER FOR THESE INTREPID AIRMEN; THE SECOND DAY OF A 3 DAY TRIP. THIS INCIDENT HAPPENED AFTER A 'HIGH SPD LAYOVER;' 6 HRS OF ATTEMPTED REST. THE KNS 660 TUNES VORS THAT ARE SELECTED BY IDENT LETTERS; BUT ONE MUST PUT IN THE RIGHT LETTERS. THE FO ADMITS THAT HE PUT IN A WRONG LETTER; THE CAPT DID NOT NOTICE; AND NEITHER ATTEMPTED TO IDENT BY THE MORSE CODE. THEY WERE 'ONLY ABOUT 30 DEGS OFF' IN HDG. ARTCC WAS NOT UPSET. THE RPTR HAS NOT HEARD ABOUT THIS FROM THE FAA.

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