Narrative:

We were issued clearance to taxi to runway 28R via taxiway b-f hold short of runway 1L. Multiple departures are taking place on runway 1L/right. An A320 is observed departing off runway 1L as we approached the runway. We hold short of runway 1L on tower frequency for approximately 1 minute. A partially blocked transmission '&taxi to runway 28' is issued by the tower.' the captain adds power to cross runway 1L as the 2 annoying backseat drivers; one of which is me; begin advocating that the clearance was not completely clear. The captain then stops the aircraft with the nose just over the hold line. The right seat then calls tower; 'tower; confirm cleared to cross runway 1L and runway 1R.' the response from the tower; in a very sarcastic and aggressive tone; 'aircraft X; I cleared you to taxi to runway 28; now continue your taxi.' the tone seemed defiant that he would not use the terminology cleared to cross runway 1L and runway 1R. The right seat read back; 'aircraft X cleared to cross runway 1L and runway 1R hold short runway 28L.' especially in sfo with staggered departures off of runway 1L and runway 1R; being cleared to cross them both verbally is desired; as sometimes you cross runway 1L and hold short of runway 1R for another departure. In aviation; there is absolutely no excuse to respond to a runway crossing clearance with sarcasm. Sfo has had its share of near misses with runway incursions. The FAA is focused on preventing them. Perhaps someone should clue in this particular tower controller as he seemed to be lacking the high standards we generally witness at sfo. Typically they are very professional. Recommendations: currently the fars dictate: a clearance to 'taxi to' the takeoff runway assigned to the aircraft is not a clearance to cross that assigned takeoff runway; or to taxi on that runway at any point; but is a clearance to cross other runways that intersect the taxi route to that assigned takeoff runway. (Title 14 of the code of federal regulations (14 crash fire rescue equipment) 91.129(i)). This allows the controller to say 'taxi to' or 'continue to runway xx' after having issued a hold short clearance for a runway that intersects the taxi route. Perhaps consideration should be given to requiring the verbiage 'cross runway xx' any time a 'hold short of runway xx' was previously issued. This would differentiate it from the hold short of a taxiway and the continue taxi clearance; but the incursion problem is primarily a runway issue; not so much of a taxiway issue. This is what the majority of pilots anticipate and desire; whether taxiing to a departure runway or waiting to cross an active runway after landing. It seems simple; if it is an active runway and you are told to hold short; you expect to hear cleared to cross when it is time to cross.

Related reports:

Google
 

Original NASA ASRS Text

Title: B777 Relief Pilot reports a clearance to cross Runways 1L and 1R at SFO is partially blocked. A request for clarification results in a sarcastic response from the Ground Controller.

Narrative: We were issued clearance to taxi to Runway 28R via Taxiway B-F hold short of Runway 1L. Multiple departures are taking place on Runway 1L/R. An A320 is observed departing off Runway 1L as we approached the runway. We hold short of Runway 1L on Tower frequency for approximately 1 minute. A partially blocked transmission '&taxi to Runway 28' is issued by the Tower.' The Captain adds power to cross Runway 1L as the 2 annoying backseat drivers; one of which is me; begin advocating that the clearance was not completely clear. The Captain then stops the aircraft with the nose just over the hold line. The right seat then calls Tower; 'Tower; confirm cleared to cross Runway 1L and Runway 1R.' The response from the Tower; in a very sarcastic and aggressive tone; 'Aircraft X; I cleared you to taxi to Runway 28; now continue your taxi.' The tone seemed defiant that he would not use the terminology cleared to cross Runway 1L and Runway 1R. The right seat read back; 'aircraft X cleared to cross Runway 1L and Runway 1R hold short Runway 28L.' Especially in SFO with staggered departures off of Runway 1L and Runway 1R; being cleared to cross them both verbally is desired; as sometimes you cross Runway 1L and hold short of Runway 1R for another departure. In aviation; there is absolutely no excuse to respond to a runway crossing clearance with sarcasm. SFO has had its share of near misses with runway incursions. The FAA is focused on preventing them. Perhaps someone should clue in this particular Tower Controller as he seemed to be lacking the high standards we generally witness at SFO. Typically they are very professional. Recommendations: Currently the FARs dictate: A clearance to 'taxi to' the takeoff runway assigned to the aircraft is not a clearance to cross that assigned takeoff runway; or to taxi on that runway at any point; but is a clearance to cross other runways that intersect the taxi route to that assigned takeoff runway. (Title 14 of the Code of Federal Regulations (14 CFR) 91.129(i)). This allows the Controller to say 'taxi to' or 'continue to Runway XX' after having issued a hold short clearance for a runway that intersects the taxi route. Perhaps consideration should be given to requiring the verbiage 'Cross Runway XX' any time a 'hold short of Runway XX' was previously issued. This would differentiate it from the hold short of a taxiway and the continue taxi clearance; but the incursion problem is primarily a runway issue; not so much of a taxiway issue. This is what the majority of pilots anticipate and desire; whether taxiing to a departure runway or waiting to cross an active runway after landing. It seems simple; if it is an active runway and you are told to hold short; you expect to hear cleared to cross when it is time to cross.

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