Cessna departing sac reported an near midair collision with other pattern traffic. Reporter claims A...

Narrative:

I was departing sac for a flight. I requested and was given a nct departure frequency and transponder code by the ground controller for traffic advisories for the flight. I taxied to runway 20. Tower cleared me for takeoff. After initial climb; I turned to a heading of approximately 050 to fly toward my destination. After the turn and in the climb passing 1;000 ft the tower told me there was another aircraft entering the pattern (while I don't recall the tower controller telling me so; I assumed left downwind for runway 20). As I recall the tower told me the aircraft was at 1;400 ft. I believe the tower called the traffic at 1 o'clock and 3 miles. I announced that I would level at 1;100 ft until I had the traffic in sight. I announced that I was looking; but did not see the other aircraft. Later the tower announced that the aircraft was at 12:00 and less than a mile at my altitude. At the same time my active traffic system gave me an oral and visual warning 'traffic 12:00 less than a mile same altitude. I immediately made a steep dive maneuver. While I had continued a visual scan for the aircraft from the time it was first announced; I never saw it. The other aircraft radioed in a rather frightened voice 'that was very close;' and made some other comment to the tower. The tower controller responded in a very angry and sarcastic tone that if both pilots had bothered to look for each other it would not have been a problem. The tower controller also claimed that the other aircraft's transponder had stopped reporting for a few seconds. As I recall; I then asked the tower if he saw us why he didn't suggest specific altitudes or a vector to avoid a near miss. I don't recall the tower's exact words; but it was defensive and curt. I said that perhaps we should discuss the incident later. But after I landed I decided the tower controller's attitude was so sarcastic and defensive that a further discussion was not likely to be beneficial or productive. After the near miss and brief radio comments between the tower and the two aircraft; the tower instructed me to switch and contact nct. I did so; and the remainder of the flight was uneventful. It may be appropriate for FAA to offer instruction to the sac tower controllers for better traffic separation of departing and arriving aircraft.

Original NASA ASRS Text

Title: Cessna departing SAC reported an NMAC with other pattern traffic. Reporter claims ATC's lack of action regarding the conflict was concerning.

Narrative: I was departing SAC for a flight. I requested and was given a NCT Departure frequency and transponder code by the Ground Controller for traffic advisories for the flight. I taxied to Runway 20. Tower cleared me for takeoff. After initial climb; I turned to a heading of approximately 050 to fly toward my destination. After the turn and in the climb passing 1;000 FT the Tower told me there was another aircraft entering the pattern (while I don't recall the Tower Controller telling me so; I assumed left downwind for Runway 20). As I recall the Tower told me the aircraft was at 1;400 FT. I believe the Tower called the traffic at 1 o'clock and 3 miles. I announced that I would level at 1;100 FT until I had the traffic in sight. I announced that I was looking; but did not see the other aircraft. Later the Tower announced that the aircraft was at 12:00 and less than a mile at my altitude. At the same time my active traffic system gave me an oral and visual warning 'traffic 12:00 less than a mile same altitude. I immediately made a steep dive maneuver. While I had continued a visual scan for the aircraft from the time it was first announced; I never saw it. The other aircraft radioed in a rather frightened voice 'That was very close;' and made some other comment to the Tower. The Tower Controller responded in a very angry and sarcastic tone that if both pilots had bothered to look for each other it would not have been a problem. The Tower Controller also claimed that the other aircraft's transponder had stopped reporting for a few seconds. As I recall; I then asked the Tower if he saw us why he didn't suggest specific altitudes or a vector to avoid a near miss. I don't recall the Tower's exact words; but it was defensive and curt. I said that perhaps we should discuss the incident later. But after I landed I decided the Tower Controller's attitude was so sarcastic and defensive that a further discussion was not likely to be beneficial or productive. After the near miss and brief radio comments between the Tower and the two aircraft; the Tower instructed me to switch and contact NCT. I did so; and the remainder of the flight was uneventful. It may be appropriate for FAA to offer instruction to the SAC Tower controllers for better traffic separation of departing and arriving aircraft.

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

Attributes
ACN	1137321
Time
Date	201312
Local Time Of Day	1201-1800
Place
Locale Reference	SAC.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Cessna 340/340A
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	Direct
Flight Plan	None
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	Initial Approach
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 25 Flight Crew Total 8000 Flight Crew Type 3000
Events
Anomaly	Conflict NMAC
Miss Distance	Horizontal 100 Vertical 100

Cessna departing sac reported an near midair collision with other pattern traffic. Reporter claims ATC's lack of action regarding the conflict was concerning.