CREW USED PREVIOUS DEP'S CLRNC INSTEAD OF THE CORRECT ONE CAUSING COM AND CLRNC PROBS AT FTY; GA.

Date: 2000-05 · Aircraft: Light Transport; Low Wing; 2 Turbojet Eng

Anomalies: deviation-altitude-overshoot|deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|other-comm-prob

Synopsis

CREW USED PREVIOUS DEP'S CLRNC INSTEAD OF THE CORRECT ONE CAUSING COM AND CLRNC PROBS AT FTY; GA.

Narrative

DEPARTED FTY. WAS TOLD TO CONTACT DEP CTL (NO FREQ GIVEN). PNF ATTEMPTED CONTACT; BUT RECEPTION WAS WEAK AND UNREADABLE. PF CONTINUED RWY HDG AND EVENTUALLY LEVELED AT 6000 FT. AFTER SEVERAL ATTEMPTS TO CONTACT DEP CTL; THE PNF RETURNED TO FTY TWR TO VERIFY THE FREQ. THE FREQ GIVEN WAS NOT THE SAME AS THE ONE ORIGINALLY ATTEMPTED. WE THEN OBTAINED GOOD COM WITH ATL DEP. THE CTLR IDENTED US AND QUESTIONED OUR CLRNC ALT AND FREQ. WE READ BACK THE ALT (6000 FT) AND FREQ (123.85) THAT WE HAD COPIED DOWN. HE STATED THAT WE SHOULD HAVE BEEN GIVEN 3000 FT AND 121.0. WE AND THE CTLR WERE PUZZLED AS TO WHY WE HAD THE WRONG INFO. HE ISSUED US A FURTHER CLRNC. WHILE ENRTE AND AFTER ARRIVING; WE ANALYZED STEP-BY-STEP WHAT WE HAD DONE TO SEE IF WE HAD INADVERTENTLY DONE WRONG. WE DISCOVERED THAT WE HAD LOOKED AT AND USED THE ALT AND FREQ OF A PREVIOUS FLT'S CLRNC THAT WAS WRITTEN ON THE SAME PAGE OF THE NOTE PAD. THERE WAS ABOUT 30 MINS BTWN COPYING THE CLRNC AND ENG START; SO ENOUGH TIME HAD PASSED THAT I DID NOT RECOGNIZE THAT WHAT WE WERE USING WAS NOT WHAT I REMEMBERED AND THE PNF POSTED THE ALT AND FREQ ON THE INSTS; BUT THE PF ACTUALLY OBTAINED THE CLRNC; SO THERE WAS A BREAK IN NORMAL ROUTINE. NEEDLESS TO SAY; THERE WAS AN IMMEDIATE CHANGE IN PROCS INSTITUTED; IE; REMOVE AND DESTROY OLD COMPLETED CLRNCS; OR; IF KEPT FOR SOME REASONS; PUT THEM OUT OF HARMS WAY. ALSO; THE PERSON THAT COPIES THE CLRNC SHOULD POST THE CLRNC ALTS; RTES; AND FREQS ON THE APPROPRIATE INST.

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