B737 flight crew reported the SJC2 SID route provides a turn that could lead into converging traffic...

Attributes
ACN	1587868
Time
Date	201810
Local Time Of Day	1801-2400
Place
Locale Reference	SJC.Airport
State Reference	CA
Environment
Light	Night
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	SID SJC2
Flight Plan	IFR
Aircraft 2
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	SID SJC2
Flight Plan	IFR
Person 1
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 240 Flight Crew Type 1584
Person 2
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 485
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types

Narrative:

We flew the new SID out of sjc. We were number 2 behind a company aircraft on the tecky 2 SID. As they were headed southeast to sptns; we were cleared for takeoff and flew the SID in accordance with company policy. We were following the FMS guidance while hand flying. Approach queried us about company departure procedures. There were two previous company flights earlier in the week that looked like they were turning early on the new SJC2 SID that would have potentially caused traffic alerts. They were the same situation as ours; a SJC2 SID following a tecky 2 SID. We both looked at the different departures on our flight home; and we noticed that the sjc 2 SID has a 113 degree heading intercept to oak R121 outbound to moony. This puts the aircraft on an intercept heading with an aircraft on the tecky 2 SID flying a wider turn to a 125 degree heading to sptns. The controller was trying to understand what could be causing the traffic conflicts; whether it was hand flying with an early turn; or a FMS coding error.

Original NASA ASRS Text

Title: B737 flight crew reported the SJC2 SID route provides a turn that could lead into converging traffic.

Narrative: We flew the new SID out of SJC. We were number 2 behind a Company aircraft on the TECKY 2 SID. As they were headed southeast to SPTNS; we were cleared for takeoff and flew the SID in accordance with Company policy. We were following the FMS guidance while hand flying. Approach queried us about Company departure procedures. There were two previous Company flights earlier in the week that looked like they were turning early on the new SJC2 SID that would have potentially caused traffic alerts. They were the same situation as ours; a SJC2 SID following a TECKY 2 SID. We both looked at the different departures on our flight home; and we noticed that the SJC 2 SID has a 113 degree heading intercept to OAK R121 outbound to MOONY. This puts the aircraft on an intercept heading with an aircraft on the TECKY 2 SID flying a wider turn to a 125 degree heading to SPTNS. The Controller was trying to understand what could be causing the traffic conflicts; whether it was hand flying with an early turn; or a FMS coding error.

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