AIRBORNE CARJ FLC CHALLENGED BY PTK TWR ABOUT COMMON FREQ USAGE WHEN FLC COORDS WITH BUF TWR FOR RWY USAGE AS DIRECTED BY BUF APCH CTL.

Date: 2002-05 · Aircraft: Regional Jet CL65; Undifferentiated or Other Model · Phase: cruise

Anomalies: deviation-discrepancy-procedural-published-material-policy|other-common-freq-interference

Synopsis

AIRBORNE CARJ FLC CHALLENGED BY PTK TWR ABOUT COMMON FREQ USAGE WHEN FLC COORDS WITH BUF TWR FOR RWY USAGE AS DIRECTED BY BUF APCH CTL.

Narrative

ENRTE FROM CVG TO BUF; AS PER NOTAM; I CONTACTED BUF APCH ON FREQ 126.5 20 MINS PRIOR TO ARR TO COORDINATE USE OF RWY 5/23. BUF APCH ADVISED ME TO CONTACT BUF TWR ON FREQ 120.5. AFTER MY INITIAL CALL; BUF TWR'S RESPONSE WAS BLOCKED; BUT ON SECOND ATTEMPT; COM WAS ESTABLISHED. I EXPLAINED THAT WE WERE 20 MINS OUT; AND WISHED TO COORDINATE FOR LNDG ON RWY 5/23. HIS REPLY WAS THEN BLOCKED REPEATEDLY; AND I ASKED HIM TO REPEAT SEVERAL TIMES. I THEN HEARD PONTIAC TWR XMITTING THAT I WAS ON HIS FREQ AND MUST CEASE XMISSION. I ATTEMPTED TO EXPLAIN; REASONABLY; THAT I WAS ALREADY IN CONTACT WITH BUF TWR PER BUF APCH INSTRUCTIONS. AT THAT TIME; THE PTK CTLR BECAME BELLIGERENT AND THREATENING; STATING THAT HE HAD MY CALL SIGN; AND THIS WAS MY LAST WARNING. I APOLOGIZED TO HIM; AND RETURNED TO BUF APCH; ASKING FOR COORD BY LANDLINE. THROUGHOUT THE XMISSION; I HEARD NO OTHER ACFT. BUF APCH STATED THAT BUF TWR ROUTINELY HEARS ACFT CALLING PONTIAC TWR. CAUSES: 1) APCH'S RECOMMENDATION FOR ACFT TO CALL TWR WHEN TOO HIGH (ACFT IN FLT LEVELS). 2) TWRS TOO CLOSE TOGETHER ON SHARED FREQ. COMMENT: THIS COM NEEDED ONLY 1 CALL AND A REPLY. BY BEING RUDE AND ANGRY; THIS CTLR INCREASED THE DURATION OF CONGESTION AND NEARLY PROVOKED A VERBAL BATTLE. FREQ CONGESTION REQUIRES INCREASED TACT AND PROFESSIONALISM; NOT AUTHORITARIAN THREATS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR ADVISED THAT SUBSEQUENT TRIPS INTO BUF TILL MONTH'S END CAUSED NO FURTHER DIFFICULTIES. TRACON EFFECTED TWR COORD FOR RWY USAGE.

More incidents for this aircraft family →

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