Narrative:

During takeoff from runway 28R from intersection east at sfo; we experienced significant engine thrust turbulence from a landed B747. ATC cleared us into position on runway 28R from east intersection after the B747 passed by from landing on the same runway. The [B747] aircraft exited 28R on K and held between 28R and 28L. ATC cleared us for takeoff after [the B747] cleared runway 28R on K in quick [succession]. During the takeoff roll and as we approached the B747; it appeared the aircraft was very close to runway 28R. Our aircraft actually reached V1 and became airborne just prior to intersection K where the B747 was waiting to cross runway 28L. As the flying pilot in the left seat; I glanced over and saw that the rear third of the large aircraft appeared to be still protruding across the 28R runway. As we passed by at approximately 50 feet; we experienced significant turbulence and airflow disruption from the idling B747 on taxiway K between 28R and 28L. I don't think ATC (sfo tower) should clear any aircraft for takeoff when a large B747 type aircraft is holding between the parallel runways 28L and 28R. I don't believe there is enough room for that size aircraft to hold short of runway 28L and be fully clear of 28R especially on K taxiway. I also feel the jet blast is significant enough to disrupt the airflow enough or case enough shear to have a significant impact on safety. Certainly if the B747 was cleared to cross 28L on K taxiway and powered up its engines as we passed by at low altitude and low airspeed the outcome could be catastrophic. I would also like to see the ground surveillance radar on this event to see just how much of that B747 was intruding into the south side of runway 28R at K intersection. From east intersection; the aircraft appeared clear and we also relied on tower to confirm that landing aircraft is clear of the runway which I don't think they could or did.

Related reports:

Google
 

Original NASA ASRS Text

Title: Corporate jet Captain reported experiencing significant engine thrust turbulence from a B747 that had exited their takeoff runway and was holding short of a parallel runway.

Narrative: During takeoff from Runway 28R from intersection E at SFO; we experienced significant engine thrust turbulence from a landed B747. ATC cleared us into position on Runway 28R from E intersection after the B747 passed by from landing on the same runway. The [B747] aircraft exited 28R on K and held between 28R and 28L. ATC cleared us for takeoff after [the B747] cleared Runway 28R on K in quick [succession]. During the takeoff roll and as we approached the B747; it appeared the aircraft was very close to Runway 28R. Our aircraft actually reached V1 and became airborne just prior to intersection K where the B747 was waiting to cross Runway 28L. As the flying pilot in the left seat; I glanced over and saw that the rear third of the large aircraft appeared to be still protruding across the 28R runway. As we passed by at approximately 50 feet; we experienced significant turbulence and airflow disruption from the idling B747 on taxiway K between 28R and 28L. I don't think ATC (SFO Tower) should clear any aircraft for takeoff when a large B747 type aircraft is holding between the parallel Runways 28L and 28R. I don't believe there is enough room for that size aircraft to hold short of Runway 28L and be fully clear of 28R especially on K taxiway. I also feel the jet blast is significant enough to disrupt the airflow enough or case enough shear to have a significant impact on safety. Certainly if the B747 was cleared to cross 28L on K taxiway and powered up its engines as we passed by at low altitude and low airspeed the outcome could be catastrophic. I would also like to see the ground surveillance radar on this event to see just how much of that B747 was intruding into the south side of Runway 28R at K intersection. From E intersection; the aircraft appeared clear and we also relied on Tower to confirm that landing aircraft is clear of the runway which I don't think they could or did.

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.