A B737-300 flight crew, departing rno, utilized the wrong SID.

Attributes
ACN	458163
Time
Date	199912
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : rno.ils
State Reference	NV
Altitude	msl single value : 8200
Aircraft 1
Controlling Facilities	tracon : rno.tracon
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : intermediate altitude climbout : takeoff
Route In Use	departure sid : mustang 5
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : rno.tracon
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 290 flight time total : 15000 flight time type : 7000
ASRS Report	458163
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 25 flight time total : 9500 flight time type : 25
ASRS Report	458165
Events
Anomaly	altitude deviation : overshoot non adherence : clearance non adherence : published procedure other spatial deviation
Independent Detector	atc equipment : conflict alert aircraft equipment : tcas other controllera
Resolutory Action	controller : issued advisory controller : separated traffic none taken : detected after the fact
Consequence	other
Miss Distance	horizontal : 0 vertical : 700
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Departing reno for houston, ATC clearance issued on ground for departure. Flight plan called for mustang 5 departure. Clearance issued 'apparently' changed the departure to a reno 2 departure. Upon takeoff, the mustang 5 departure was flown because all I heard was cleared as filed. Upon initiating the left turn at 3 DME rno to fmg, departure called and asked us what departure we were issued and said we had traffic. TCASII gave a traffic warning (no RA) and nothing else. The screen showed an aircraft below and to our 1 O'clock position (-700 ft below). Contributing factors: 1) no pre departure clearance. Did not hear rno 2, only hard as filed. 2) performing IOE for a first officer transitioning from DC9 to B737. Very high workload. 3) briefed the mustang 5 departure and special engine out procedures extensively at gate, further locking myself into flying the mustang 5 departure. 4) first flight for both pilots into and out of reno.

Original NASA ASRS Text

Title: A B737-300 FLC, DEPARTING RNO, UTILIZED THE WRONG SID.

Narrative: DEPARTING RENO FOR HOUSTON, ATC CLRNC ISSUED ON GND FOR DEP. FLT PLAN CALLED FOR MUSTANG 5 DEP. CLRNC ISSUED 'APPARENTLY' CHANGED THE DEP TO A RENO 2 DEP. UPON TKOF, THE MUSTANG 5 DEP WAS FLOWN BECAUSE ALL I HEARD WAS CLRED AS FILED. UPON INITIATING THE L TURN AT 3 DME RNO TO FMG, DEP CALLED AND ASKED US WHAT DEP WE WERE ISSUED AND SAID WE HAD TFC. TCASII GAVE A TFC WARNING (NO RA) AND NOTHING ELSE. THE SCREEN SHOWED AN ACFT BELOW AND TO OUR 1 O'CLOCK POS (-700 FT BELOW). CONTRIBUTING FACTORS: 1) NO PDC. DID NOT HEAR RNO 2, ONLY HARD AS FILED. 2) PERFORMING IOE FOR A FO TRANSITIONING FROM DC9 TO B737. VERY HIGH WORKLOAD. 3) BRIEFED THE MUSTANG 5 DEP AND SPECIAL ENG OUT PROCS EXTENSIVELY AT GATE, FURTHER LOCKING MYSELF INTO FLYING THE MUSTANG 5 DEP. 4) FIRST FLT FOR BOTH PLTS INTO AND OUT OF RENO.

Data retrieved from NASA's ASRS site as of July 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.