AN SF340 HAS A POTENTIAL CONFLICT WITH A BE76 ON TKOF ON XING RWY. THE DUCHESS WAS NOT WILLING TO WAIT FOR TKOF BEHIND THE SF340 SO USED A XING RWY. NO SELF ANNOUNCEMENT WAS MADE BY THE BE76 PLT.

Date: 1998-04 · Aircraft: SF 340A

Anomalies: conflict-ground-conflict|critical|deviation-discrepancy-procedural-other-unknown|deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-far|other-unspecified

Synopsis

AN SF340 HAS A POTENTIAL CONFLICT WITH A BE76 ON TKOF ON XING RWY. THE DUCHESS WAS NOT WILLING TO WAIT FOR TKOF BEHIND THE SF340 SO USED A XING RWY. NO SELF ANNOUNCEMENT WAS MADE BY THE BE76 PLT.

Narrative

WAITING FOR IFR CLRNC TO MSP. FO WAS MONITORING BOTH CTAF AND CLRNC (FSS). CAPT MONITORING CTAF. ANOTHER ACFT (BEECHJET) JUST CANCELED IFR INBOUND. CAPT HAD HIM IN SIGHT ON DOWNWIND. FO RECEIVED CLRNC TO DEPART. CAPT MADE ANNOUNCEMENT ON CTAF WE WERE DEPARTING RWY 13 STRAIGHT OUT DEP AND THANKED BEECHJET FOR CANCELING. FO COMPLETED BEFORE TKOF CHK AND RWY ITEMS CHK. THE CAPT (ME) ADDED TKOF PWR. AROUND 50 KTS WE SIGHTED THE DUCHESS ROTATING AT 12 O'CLOCK ON THE CROSS RWY; APPROX 2000 FT AHEAD. WE CONTINUED A NORMAL TKOF. AFTER COMPLETION OF AFTER TKOF CHK WE CONTACTED THE DUCHESS TO SEE IF HE WAS ON FREQ. HE WAS AND I ASKED IF HE MADE A TKOF ANNOUNCEMENT. HE SAID NO. UNFORTUNATELY; THIS WAS A PERFECTLY LEGAL MOVE. A STUPID ONE; BUT LEGAL. I BELIEVE HE CHOSE THE OTHER RWY SO HE WOULD NOT HAVE TO WAIT IN LINE BEHIND US AS WE WAITED APPROX 3 MINS FOR OUR IFR CLRNC. THIS SIT HAS COST LIVES IN THE PAST; IE; BEECH 1900D IN QUINCY. DO YOU THINK THE FLYING PUBLIC WOULD LIKE TO HEAR ABOUT THESE SITS?

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