POTENTIAL CONFLICT BTWN ONE IFR COMMUTER AND ONE SMA WHILE ON RADAR TA SVC AT SUU FACILITY.

Date: 1993-08 · Aircraft: Light Transport; Low Wing; 2 Turboprop Eng

Anomalies: conflict-airborne-conflict|deviation-discrepancy-procedural-far|other-unspecified

Synopsis

POTENTIAL CONFLICT BTWN ONE IFR COMMUTER AND ONE SMA WHILE ON RADAR TA SVC AT SUU FACILITY.

Narrative

LEVEL AT 7000 APCH CALLED TFC; AN SMA AT 7300 FT; 12 O'CLOCK; 5 MI; SWBOUND. I ASKED IF IT WAS LEVEL AT 7300 AND THE PLT REPLIED THEY WERE DSNDING. ABOUT 15 SECONDS LATER APCH AGAIN CALLED TFC 12 O'CLOCK 1 MI AT 7100. BEFORE ANY EVASIVE ACTION COULD BE INITIATED TFC WAS SPOTTED PASSING SLIGHTLY ABOVE AND TO THE R. WE WERE IFR; THE SMA WAS RECEIVING FLT FOLLOWING. NEITHER OF US WAS GIVEN ANY INFO TO AVOID A POTENTIAL CONFLICT. APCH GAVE THE TFC CALLS IN A ROUTINE MANNER AND DID NOT INDICATE ANY URGENCY. WHEN THE SMA PLT TOLD THE CTLR HE THOUGHT SEPARATION WAS INADEQUATE; SHE ADVISED HIM TO CHANGE FREQS AND DID NOT ACKNOWLEDGE HIS COMMENT. DURING THE ENTIRE EPISODE THE CTLR DID NOT INDICATE ANY CONCERN. HER TONE OF VOICE WAS UNCHANGED; AND SHE NEVER INDICATED TFC POS OTHER THAN THE 5 MI CALL AND THE 1 MI CALL; NEITHER OF WHICH WE ACKNOWLEDGED HAVING SPOTTED THE TFC. AS FAR AS I CAN REMEMBER THE SMA WAS NEVER GIVEN OUR POS; EXCEPT BY HEARING APCH TALKING TO US. THE CTLR WAS FAIRLY BUSY WITH OTHER ADVISORY TFC BUT NOT SO MUCH TAT THE CONFLICT COULD NOT HAVE BEEN ANTICIPATED OR MORE TIMELY TFC INFO COULD HAVE BEEN GIVEN.

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