Narrative:

The R30 controller advised me that air carrier X entered oakland center's airspace without a hand off. When the oakland controller called the R30 controller observed the limited data block about three miles south of the boundary. The R30 controller stated he didn't depart the flight plan when he issued the clearance; the pilot didn't check on; apparently he had radio problems; and there was no code observed. Recommendation; the controller self identified that he normally departs the flight plan; but didn't in this case. There was some casual conversation taking place which may have contributed to the incident. I was observing the controller during the time he issued the clearance and he was attentive to sector operations.

Google
 

Original NASA ASRS Text

Title: ZSE Controller described a ZOA airspace entry event when ERAM equipment failed to start a track on the subject aircraft; the reporter noting the aircraft was absent of transponder information.

Narrative: The R30 Controller advised me that Air Carrier X entered Oakland Center's airspace without a hand off. When the Oakland Controller called the R30 Controller observed the limited data block about three miles south of the boundary. The R30 Controller stated he didn't depart the flight plan when he issued the clearance; the pilot didn't check on; apparently he had radio problems; and there was no code observed. Recommendation; the Controller self identified that he normally departs the flight plan; but didn't in this case. There was some casual conversation taking place which may have contributed to the incident. I was observing the Controller during the time he issued the clearance and he was attentive to sector operations.

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