Near midair collision.

Attributes
ACN	292540
Time
Date	199412
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : shn
State Reference	WA
Altitude	agl bound lower : 800 agl bound upper : 800
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : smf
Operator	other
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	climbout : takeoff climbout : initial ground : holding
Flight Plan	None
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	other : unknown
Flight Phase	descent : approach landing : go around other
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : commercial pilot : cfi
Experience	flight time total : 1000
ASRS Report	292540
Person 2
Affiliation	Other
Function	flight crew : single pilot
Events
Anomaly	aircraft equipment problem : less severe conflict : nmac non adherence : far
Independent Detector	other flight crewa
Resolutory Action	flight crew : took evasive action flight crew : overcame equipment problem none taken : unable
Consequence	Other
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	Pilot Deviation

Narrative:

Problem: I departed runway 23, shn, with my first load of the day. I called unicom, announced my intentions (ie, taking off runway 23, climbing to 9500 ft over airport, etc.) took off and at about 800 ft AGL I noticed an aircraft cross my horizon (from right to left). I had that bad feeling that I screwed up. I called approach control on the same radio I used for CTAF. No answer. I again tried to call approach, this time on the other radio (#2). It worked. Throughout my climb I attempted to hail approach on #1 radio. Never got them. Only on #2. Suspecting failure of #1 radio. I proceeded to use #2 exclusively. It turns out that I did force someone, who was on left base to runway 05 to change his pattern. He announced his position on CTAF, shetton unicom tried to call me and I did not hear either of them. Shetton unicom did hear me as I was re-entering the pattern. But by then I was on #2 radio. Lesson learned: I should have thoroughly checked the pattern before takeoff by doing a 360 degree turn before my takeoff roll. I may have spotted the traffic on left base to runway 05 thereby realizing sooner that I had a communications problem.

Original NASA ASRS Text

Title: NMAC.

Narrative: PROB: I DEPARTED RWY 23, SHN, WITH MY FIRST LOAD OF THE DAY. I CALLED UNICOM, ANNOUNCED MY INTENTIONS (IE, TAKING OFF RWY 23, CLBING TO 9500 FT OVER ARPT, ETC.) TOOK OFF AND AT ABOUT 800 FT AGL I NOTICED AN ACFT CROSS MY HORIZON (FROM R TO L). I HAD THAT BAD FEELING THAT I SCREWED UP. I CALLED APCH CTL ON THE SAME RADIO I USED FOR CTAF. NO ANSWER. I AGAIN TRIED TO CALL APCH, THIS TIME ON THE OTHER RADIO (#2). IT WORKED. THROUGHOUT MY CLB I ATTEMPTED TO HAIL APCH ON #1 RADIO. NEVER GOT THEM. ONLY ON #2. SUSPECTING FAILURE OF #1 RADIO. I PROCEEDED TO USE #2 EXCLUSIVELY. IT TURNS OUT THAT I DID FORCE SOMEONE, WHO WAS ON L BASE TO RWY 05 TO CHANGE HIS PATTERN. HE ANNOUNCED HIS POS ON CTAF, SHETTON UNICOM TRIED TO CALL ME AND I DID NOT HEAR EITHER OF THEM. SHETTON UNICOM DID HEAR ME AS I WAS RE-ENTERING THE PATTERN. BUT BY THEN I WAS ON #2 RADIO. LESSON LEARNED: I SHOULD HAVE THOROUGHLY CHKED THE PATTERN BEFORE TKOF BY DOING A 360 DEG TURN BEFORE MY TKOF ROLL. I MAY HAVE SPOTTED THE TFC ON L BASE TO RWY 05 THEREBY REALIZING SOONER THAT I HAD A COMS PROB.

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.