Narrative:

We were in position on runway 01L assigned the sstck SID on departure. A B737 was on runway 01R and cleared for takeoff and then we were cleared for takeoff immediately after them. From my position I could not see them as they were lined up behind my field of view. We immediately began our takeoff roll using flaps 3 configuration. I had lined the aircraft just left of centerline; to avoid running over the centerline lights on takeoff roll and to compensate for the strong left crosswind. My flying partner is a very experienced pilot and performed a normal takeoff keeping the aircraft aligned as I had given it to him and he rotated and was airborne just prior to crossing the intersecting runways. After rotation the flight director commanded a slight right turn which he did not follow maintaining his initial runway track. The SID directs flying a heading of 014 until 520 feet then turning left to sstik. Just after I raised the gear; we heard 'monitor vertical speed' and the vvi indicator turned red followed immediately by 'clear of conflict'. This happened so quickly we didn't have time to react to it. By now the flight director was commanding a full left turn to sstik and tower handed us over to nocal departure. We continued the climb out. After completing the after takeoff check and checking with norcal; I had time to reflect on what had happened. We had received a TCAS resolution advisory (RA) but the first part of it was inhibited because of our altitude. When we climbed above the inhibit altitude we heard the tail end of the warning. I suspect the aircraft on 01R drifted into our TCAS threat zone triggering the event. Again; I could not see the aircraft on the other runway; so I am not sure where they were in relation to our position but I know the sids on 01R direct a right turn away from the runway track. The problem with the RNAV departures in sfo is they do not account for aircraft in close proximity to each other and direct straight out tracks for longer than they should. I have also witnessed the flight directors in strong crosswinds; as it did in this case direct a turn that exacerbates the potential for a close encounter. I did not report this event to ATC because by the time I had figured out what had occurred we were well beyond their frequency.

Related reports:

Google
 

Original NASA ASRS Text

Title: A320 Captain reported receiving an Resolution Advisory (RA) shortly after takeoff from Runway 1L in SFO; presumably from another aircraft that took off from Runway 1R.

Narrative: We were in position on Runway 01L assigned the SSTCK SID on departure. A B737 was on runway 01R and cleared for takeoff and then we were cleared for takeoff immediately after them. From my position I could not see them as they were lined up behind my field of view. We immediately began our takeoff roll using flaps 3 configuration. I had lined the aircraft just left of centerline; to avoid running over the centerline lights on takeoff roll and to compensate for the strong left crosswind. My flying partner is a very experienced pilot and performed a normal takeoff keeping the aircraft aligned as I had given it to him and he rotated and was airborne just prior to crossing the intersecting runways. After rotation the Flight Director commanded a slight right turn which he did not follow maintaining his initial runway track. The SID directs flying a heading of 014 until 520 feet then turning left to SSTIK. Just after I raised the gear; we heard 'Monitor Vertical Speed' and the VVI indicator turned red followed immediately by 'Clear of Conflict'. This happened so quickly we didn't have time to react to it. By now the Flight Director was commanding a full left turn to SSTIK and tower handed us over to NOCAL Departure. We continued the climb out. After completing the After Takeoff Check and checking with NORCAL; I had time to reflect on what had happened. We had received a TCAS Resolution Advisory (RA) but the first part of it was inhibited because of our altitude. When we climbed above the inhibit altitude we heard the tail end of the warning. I suspect the aircraft on 01R drifted into our TCAS threat zone triggering the event. Again; I could not see the aircraft on the other runway; so I am not sure where they were in relation to our position but I know the SIDs on 01R direct a right turn away from the runway track. The problem with the RNAV departures in SFO is they do not account for aircraft in close proximity to each other and direct straight out tracks for longer than they should. I have also witnessed the Flight Directors in strong crosswinds; as it did in this case direct a turn that exacerbates the potential for a close encounter. I did not report this event to ATC because by the time I had figured out what had occurred we were well beyond their frequency.

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.