37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1043711 |
Time | |
Date | 201210 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SFO.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying First Officer |
Experience | Flight Crew Last 90 Days 200 Flight Crew Total 11010 Flight Crew Type 2400 |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
Taxing out for departure to runway 28L at sfo; after [we were] being advised to expect 28L. I requested a weight and balance uplink for 28L. Holding short number 1; sfo tower clears us to cross 28L for 28R. I advise that we were told to expect 28L for departure and that we did not have the numbers for 28R. Local then tells us he can not give 28L for traffic and to continue holding short of 28L. Advise when you have your numbers for 28R. I then send another a weight and balance request for 28R. We receive the data and I load the FMC and reselect the new departure runway and departure per our flight manual procedures. Once the captain and I verified everything was in order for 28R I advised tower we had our numbers for 28R and were ready for departure. Sfo tower then comes back with a line up and wait clearance for 28L. I then ask again; you just told us 28R; while I was querying the tower the captain began to cross the hold short line as instructed by ATC. Tower then replies to my query you need to have numbers for both runways; that's how we do it here. Now I am scrambling to reload the 28L data in the FMC and re-confirm the departure runway and SID. Sfo tower then issues a quick hold short instruction but the nose was across the line already as previously instructed. Then local controller sees this and re-issues a line up and wait clearance. As I'm finishing up the verification tower issues an immediate takeoff clearance for 28L. Checklists complete; runway verification callout complete and the captain is now calling for auto throttles as we accelerate for takeoff. While rolling on 28L I hear the tower command a go around for the aircraft on final. We followed our established procedures and ATC kept changing the plan and trying to rush us. Had we not followed our procedures I believe many other errors could have happened.
Original NASA ASRS Text
Title: Air Carrier First Officer is told to expect Runway 28L at SFO and FMC and weight and balance information are loaded for Runway 28L. Runway 28R is assigned and the crew advises that they cannot accept Runway 28R without reprogramming and are told to hold short and advise when ready. When the crew announces ready the Tower instructs to line up and wait Runway 28L which the crew is again not ready for and results in a takeoff delay and a go around for an aircraft on approach.
Narrative: Taxing out for departure to Runway 28L at SFO; after [we were] being advised to expect 28L. I requested a weight and balance uplink for 28L. Holding short number 1; SFO Tower clears us to cross 28L for 28R. I advise that we were told to expect 28L for departure and that we did not have the numbers for 28R. Local then tells us he can not give 28L for traffic and to continue holding short of 28L. Advise when you have your numbers for 28R. I then send another a weight and balance request for 28R. We receive the data and I load the FMC and reselect the new departure runway and departure per our Flight Manual procedures. Once the Captain and I verified everything was in order for 28R I advised Tower we had our numbers for 28R and were ready for departure. SFO Tower then comes back with a line up and wait clearance for 28L. I then ask again; you just told us 28R; while I was querying the Tower the Captain began to cross the hold short line as instructed by ATC. Tower then replies to my query you need to have numbers for both runways; that's how we do it here. Now I am scrambling to reload the 28L data in the FMC and re-confirm the departure runway and SID. SFO Tower then issues a quick hold short instruction but the nose was across the line already as previously instructed. Then Local Controller sees this and re-issues a line up and wait clearance. As I'm finishing up the verification Tower issues an immediate takeoff clearance for 28L. Checklists complete; runway verification callout complete and the Captain is now calling for auto throttles as we accelerate for takeoff. While rolling on 28L I hear the Tower command a go around for the aircraft on final. We followed our established procedures and ATC kept changing the plan and trying to rush us. Had we not followed our procedures I believe many other errors could have happened.
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.