Narrative:

Sfo airport configuration was landing runway 28L/right and departing runway 01L/right. The primary SID in use for richmond sector was the trukn SID. Sfo tower scanned aircraft X flight plan which showed trukn SID. The departure controllers were expecting this pilot to depart runway 01 on the trukn SID. Aircraft X departed runway 28 on we had no idea what route or altitude. When the pilot was queried on what departure he was issued and what altitude he had been assigned; it was discovered he was re-cleared on the santana SID and stopped at 3;000 feet by the tower. But we had no idea; so we have to act based on the assumption the pilot was departing runway 28 on the trukn SID; which is a right turn heading 040 and climbing to 19000 feet. Instead of the pilot departing directly into richmond airspace as expected; the pilot departed into sutro sector airspace without prior coordination. Per LOA (letter of agreement); the tower is required to scan the strip noting runway 28 departure for all flights that will depart runway 28 on this configuration to departure control. This did not happen. Nor was there any verbal coordination. Departure control bases all control instructions/separation on what is scanned on the flight plan strips received from sfo tower. Sfo tower does not seem to understand the importance of communicating amended flight plan information to the departure controllers because this happens with alarming frequency. This is the second incident of this type I have witnessed this week.sfo tower usually claims the strip was scanned correctly. I have no idea if this excuse is being used as a 'get out of jail free' card or if there is truly an equipment issue. The result is; we have aircraft entering another controller's airspace without prior coordination resulting in potential loss of separation with other aircraft. Sfo tower also claims that amended flight plan information need not be forwarded to departure control because it is covered in the nct/sfo LOA. I am not sure why the tower feels the LOA replaces required coordination of amended flight plan information; but this misunderstanding introduces unnecessary high risk of loss of separation into the NAS. The LOA states what can be assigned based on runway/flow configurations; not what has been assigned. We have no way of knowing if the flight plan has been amended from what was originally scanned unless the tower makes and fdio amendment and re-scans; or verbally coordinates the change directly with the [other controllers]. It's that simple. Our responsibilities are clearly stated in the air traffic order. You cannot enter another controller's airspace without prior coordination. We are required to electronically or verbally forward amended flight plan information to the receiving controller. Whatever is on the IFR flight strip is exactly what the receiving controller is expecting the pilot to execute. I recommend that sfo tower comply with the requirements regarding entering another controller's airspace and forwarding of amended flight plan information.

Related reports:

Google
 

Original NASA ASRS Text

Title: NCT TRACON Departure Controller reported an aircraft departed on a different route than was coordinated via automated strip scanning from the Tower. The Tower Controller states they accomplished the automated strip scan correctly.

Narrative: SFO airport configuration was landing runway 28L/R and departing runway 01L/R. The primary SID in use for Richmond Sector was the Trukn SID. SFO tower scanned Aircraft X flight plan which showed Trukn SID. The departure controllers were expecting this pilot to depart runway 01 on the Trukn SID. Aircraft X departed runway 28 on we had no idea what route or altitude. When the pilot was queried on what departure he was issued and what altitude he had been assigned; it was discovered he was re-cleared on the Santana SID and stopped at 3;000 feet by the tower. But we had no idea; so we have to act based on the assumption the pilot was departing runway 28 on the Trukn SID; which is a right turn heading 040 and climbing to 19000 feet. Instead of the pilot departing directly into Richmond airspace as expected; the pilot departed into Sutro Sector airspace without prior coordination. Per LOA (Letter of Agreement); the tower is required to scan the strip noting Runway 28 departure for all flights that will depart Runway 28 on this configuration to departure control. This did not happen. Nor was there any verbal coordination. Departure control bases all control instructions/separation on what is scanned on the flight plan strips received from SFO tower. SFO tower does not seem to understand the importance of communicating amended flight plan information to the departure controllers because this happens with alarming frequency. This is the second incident of this type I have witnessed this week.SFO tower usually claims the strip was scanned correctly. I have no idea if this excuse is being used as a 'get out of jail free' card or if there is truly an equipment issue. The result is; we have aircraft entering another controller's airspace without prior coordination resulting in potential loss of separation with other aircraft. SFO tower also claims that amended flight plan information need not be forwarded to departure control because it is covered in the NCT/SFO LOA. I am not sure why the tower feels the LOA replaces required coordination of amended flight plan information; but this misunderstanding introduces unnecessary high risk of loss of separation into the NAS. The LOA states what CAN be assigned based on runway/flow configurations; not what HAS been assigned. We have no way of knowing if the flight plan has been amended from what was originally scanned unless the tower makes and FDIO amendment and re-scans; or verbally coordinates the change directly with the [other controllers]. It's that simple. Our responsibilities are clearly stated in the air traffic order. You cannot enter another controller's airspace without prior coordination. We are required to electronically or verbally forward amended flight plan information to the receiving controller. Whatever is on the IFR flight strip is exactly what the receiving controller is expecting the pilot to execute. I recommend that SFO tower comply with the requirements regarding entering another controller's airspace and forwarding of amended flight plan information.

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.