The PIC of a citation 550 used the wrong SID when departing srq, causing a track deviation.

Attributes
ACN	572694
Time
Date	200301
Day	Sat
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : srq.airport
State Reference	FL
Altitude	msl single value : 1500
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Controlling Facilities	tracon : tpa.tracon tower : srq.tower
Operator	general aviation : corporate
Make Model Name	Citation II S2/Bravo
Operating Under FAR Part	Part 91
Flight Phase	climbout : initial
Route In Use	departure : on vectors departure sid : sarasota
Flight Plan	IFR
Person 1
Affiliation	company : corporate
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : commercial pilot : atp pilot : cfi
Experience	flight time last 90 days : 65 flight time total : 13000 flight time type : 5000
ASRS Report	572694
Person 2
Affiliation	company : corporate
Function	flight crew : first officer
Events
Anomaly	non adherence : published procedure non adherence : far non adherence : clearance non adherence : company policies other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance flight crew : became reoriented
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Taxiing out on parallel taxiway a to runway 14 at srq, the first officer was in the left seat and I was running the checklist from the right seat. Part of our checklist requires a callout of compass headings, which were indicating 320 degrees at that time. I finished the taxi checklist and began briefing the SID (it was filed as part of our flight plan). I briefed the SID for runway 32 instead of runway 14. Switched over to tampa approach immediately after takeoff and tampa called us asking if we were in a left turn (the SID for runway 32 requires a left turn at 0.9 DME). I replied in the affirmative and he immediately gave us a northerly heading. We complied, then I asked if there was a problem. He said no, that he was just surprised (the SID for runway 14 calls for runway heading). I knew then what I had done. I think the combination of running a checklist, seeing 320 degrees on the compass and monitoring the first officer's actions provided an environment for my error. The situation could have been avoided if I had included the following in my briefing: 'the SID for runway xx is XXX.' that statement would either have taken me to the correct text or alerted the first officer to my error.

Original NASA ASRS Text

Title: THE PIC OF A CITATION 550 USED THE WRONG SID WHEN DEPARTING SRQ, CAUSING A TRACK DEV.

Narrative: TAXIING OUT ON PARALLEL TXWY A TO RWY 14 AT SRQ, THE FO WAS IN THE L SEAT AND I WAS RUNNING THE CHKLIST FROM THE R SEAT. PART OF OUR CHKLIST REQUIRES A CALLOUT OF COMPASS HDGS, WHICH WERE INDICATING 320 DEGS AT THAT TIME. I FINISHED THE TAXI CHKLIST AND BEGAN BRIEFING THE SID (IT WAS FILED AS PART OF OUR FLT PLAN). I BRIEFED THE SID FOR RWY 32 INSTEAD OF RWY 14. SWITCHED OVER TO TAMPA APCH IMMEDIATELY AFTER TKOF AND TAMPA CALLED US ASKING IF WE WERE IN A L TURN (THE SID FOR RWY 32 REQUIRES A L TURN AT 0.9 DME). I REPLIED IN THE AFFIRMATIVE AND HE IMMEDIATELY GAVE US A NORTHERLY HDG. WE COMPLIED, THEN I ASKED IF THERE WAS A PROB. HE SAID NO, THAT HE WAS JUST SURPRISED (THE SID FOR RWY 14 CALLS FOR RWY HDG). I KNEW THEN WHAT I HAD DONE. I THINK THE COMBINATION OF RUNNING A CHKLIST, SEEING 320 DEGS ON THE COMPASS AND MONITORING THE FO'S ACTIONS PROVIDED AN ENVIRONMENT FOR MY ERROR. THE SIT COULD HAVE BEEN AVOIDED IF I HAD INCLUDED THE FOLLOWING IN MY BRIEFING: 'THE SID FOR RWY XX IS XXX.' THAT STATEMENT WOULD EITHER HAVE TAKEN ME TO THE CORRECT TEXT OR ALERTED THE FO TO MY ERROR.

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.