Air carrier did not comply with departure clearance and may have conflicted with arriving traffic.

Attributes
ACN	122536
Time
Date	198909
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : bzn
State Reference	MT
Altitude	msl bound lower : 11000 msl bound upper : 13000
Environment
Flight Conditions	Marginal
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	climbout : initial
Route In Use	departure other enroute airway : zlc
Flight Plan	IFR
Aircraft 2
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Retractable Gear
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller non radar : 4 controller radar : 3
ASRS Report	122536
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I just sat down on radar position. Air carrier X called on the ground at bzn requesting clearance to slc. An small aircraft was 10 mi east of bzn at 11000' inbound to bzn. Another small plane was about 15 mi east of bzn wbound at 12000'. Air carrier X was given a clearance to slc. The departure procedure at bzn is to climb west on V343 within 20 mi to cross the VOR for V343 on course at or above 6800'. Air carrier X reported 6 mi west of the VOR at 9000'. I cleared him to 15000' and asked him to report leaving 13000'. I was using the 44 KT rule and the small aircraft was still east of the VOR. I cleared the small aircraft for an ILS approach. Air carrier X then reported over the VOR leaving 13000'. He should have climbed straight up the arwy. When he was still on the ground, he questioned why he couldn't climb south on V343. I told him that, due to traffic, the me southbound was not available. I also advised him to expect a vector on course upon radar identify. The radar is limited near bzn below 14000'. I do not know if sep was lost between air carrier X and the 2 smaller planes. If air carrier X was confused, he should have questioned me.

Original NASA ASRS Text

Title: ACR DID NOT COMPLY WITH DEP CLRNC AND MAY HAVE CONFLICTED WITH ARRIVING TRAFFIC.

Narrative: I JUST SAT DOWN ON RADAR POS. ACR X CALLED ON THE GND AT BZN REQUESTING CLRNC TO SLC. AN SMA WAS 10 MI E OF BZN AT 11000' INBND TO BZN. ANOTHER SMALL PLANE WAS ABOUT 15 MI E OF BZN WBOUND AT 12000'. ACR X WAS GIVEN A CLRNC TO SLC. THE DEP PROC AT BZN IS TO CLB W ON V343 WITHIN 20 MI TO CROSS THE VOR FOR V343 ON COURSE AT OR ABOVE 6800'. ACR X RPTED 6 MI W OF THE VOR AT 9000'. I CLRED HIM TO 15000' AND ASKED HIM TO RPT LEAVING 13000'. I WAS USING THE 44 KT RULE AND THE SMA WAS STILL E OF THE VOR. I CLRED THE SMA FOR AN ILS APCH. ACR X THEN RPTED OVER THE VOR LEAVING 13000'. HE SHOULD HAVE CLBED STRAIGHT UP THE ARWY. WHEN HE WAS STILL ON THE GND, HE QUESTIONED WHY HE COULDN'T CLB S ON V343. I TOLD HIM THAT, DUE TO TFC, THE ME SBND WAS NOT AVAILABLE. I ALSO ADVISED HIM TO EXPECT A VECTOR ON COURSE UPON RADAR IDENT. THE RADAR IS LIMITED NEAR BZN BELOW 14000'. I DO NOT KNOW IF SEP WAS LOST BTWN ACR X AND THE 2 SMALLER PLANES. IF ACR X WAS CONFUSED, HE SHOULD HAVE QUESTIONED ME.

Data retrieved from NASA's ASRS site as of August 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.