An aircraft on final to sfo made two go arounds because of conflicting traffic. One was a crossing r...

Attributes
ACN	1283741
Time
Date	201507
Local Time Of Day	1201-1800
Place
Locale Reference	SFO.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Large Transport
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Takeoff
Flight Plan	IFR
Person 1
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Person 2
Function	Pilot Not Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Narrative:

Two back to back go-arounds performed at sfo. Sfo landing runway 28R/left and departing runway 01R/left during day VMC. On approach to 28R everything normal and cleared to land 28R by tower. Tower subsequently directs go-around due to possible conflict with traffic departing on intersecting runway. Normal go-around performed and vectored back for visual approach on 28L. Once again tower clears us to land. Tower also directs a heavy aircraft to cross approach end of runway 28L and hold short of 28R. Now we are on short final and notice that the heavy has crossed 28L; our runway of intended landing; but has stopped with its tail sticking over the hold short line for 28L. Captain plays it safe and performs a go-around. We get vectored back around for another visual to 28L and land normally.crew did the right thing by performing these two go-arounds.in the first go-around; sfo tower should not have cleared an aircraft for takeoff on 01 when we were about to land on 28R.second case; the crew of the heavy needed to pull forward more to ensure aircraft tail was clear of the runway they just crossed.

Original NASA ASRS Text

Title: An aircraft on final to SFO made two go arounds because of conflicting traffic. One was a crossing runway departure traffic and the second was an aircraft not clear of the runway.

Narrative: Two back to back Go-Arounds performed at SFO. SFO landing Runway 28R/L and departing Runway 01R/L during day VMC. On approach to 28R everything normal and cleared to land 28R by tower. Tower subsequently directs Go-Around due to possible conflict with traffic departing on intersecting runway. Normal Go-Around performed and vectored back for visual approach on 28L. Once again Tower clears us to land. Tower also directs a heavy aircraft to cross approach end of runway 28L and hold short of 28R. Now we are on short final and notice that the heavy has crossed 28L; our runway of intended landing; but has stopped with its tail sticking over the hold short line for 28L. Captain plays it safe and performs a Go-Around. We get vectored back around for another visual to 28L and land normally.Crew did the right thing by performing these two Go-Arounds.In the first Go-Around; SFO tower should not have cleared an aircraft for takeoff on 01 when we were about to land on 28R.Second case; the crew of the heavy needed to pull forward more to ensure aircraft tail was clear of the runway they just crossed.

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.

An aircraft on final to sfo made two go arounds because of conflicting traffic. One was a crossing runway departure traffic and the second was an aircraft not clear of the runway.