Date: 201405
Local time of day: 1801-2400
Location: ZOA.ARTCC, CA
Light: Night
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZOA
ATC / advisory: Center ZOA
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Provided Assistance
Contributing factors: Procedure
Primary problem: Procedure

Narrative: I was working a high priority aircraft to SFO. I was just finishing sequencing at least 5 aircraft to LAS. My D-side was a trainee who had fallen well behind. I was just advised by my Supervisor that the aircraft in front of the high priority aircraft who was at the same altitude needed to hold for 20 minutes. At this point I glanced at Sector 29 and noticed they had 3 aircraft flashing handoff to us. Aircraft X was out of about FL300 climbing to an interim altitude of FL310 and 1 minute from our boundary. I quickly did a traffic scan and moved my slew ball to accept the handoff. While the handoff was still flashing at me; the interim altitude came out and now Aircraft X was climbing to FL350. I did another traffic scan and accepted the handoff. I then checked his flight plan. Normally I would do this before accepting a handoff but he was about to enter my airspace. Aircraft X's flight plan showed him cleared LIN direct DTA. Aircraft X was at least 7 miles north of this diverging to the north toward an ATCAA 400 and below that was 5 minutes in front of him. I called Sector 29 and chastised them for changing Aircraft X's altitude during the handoff and told them he was not on his route and asked where he was going. They did not know where Aircraft X was going and had shipped him to me. #1 The R-side at 29 needs to be made aware of how dangerous it can be to change an altitude or route after initiating the handoff. He needs to be trained on proper operating practices.#2 The R-side and D-side need to be trained on reading flight plans and checking that aircraft are flying their filed route.#3 The 7110.65 needs to be changed. Prior to 3 years ago 5-4-5 (b) was written in a manner that nearly everyone agreed that once a handoff was initiated for the first time; if you changed anything; you needed to call the receiving sector. About 3 years ago 5-4-5 (b) was changed to state: ' Verbally obtain the receiving controller's approval prior to making any changes to an aircraft's flight path; altitude; or data block information while the handoff is being initiated or after acceptance; unless otherwise specified by a LOA or a facility directive'. Many Oakland and Salt Lake ARTCC controllers as well as classroom instructors are teaching that you can now initiate a handoff; take the handoff back; change the aircraft's route; altitude or anything else and initiate the handoff again and there is no requirement to call and coordinate. This can be extremely dangerous. There are many controllers who take handoffs back; change something and initiate the handoff again in less than 2 seconds. I teach trainees to scan for handoffs; read the flight plan; scan for traffic then accept the handoff. It takes well more than 2 seconds for almost everyone to read a flight plan and scan for traffic. If the route or altitude is changed during this time; it can and has lead to very unsafe situations. Now some controllers are taking it a step further and changing routes and altitudes while the handoff is being made and not coordinating. I complained about this to our old management a little over a year ago but nothing was done. PLEASE CHANGE 5-4-5 (b) to read 'Verbally obtain the receiving controller's approval prior to making any changes to an aircraft's flight path; altitude; or data block information after the hand off is initiated for the first time or after acceptance unless otherwise specified by a LOA or a facility directive.




Synopsis: ZOA Controller describes situation in which he has taken a handoff and then observes the flight in an other direction. He calls the other sector and they have issued a route change with out advising the receiving Controller.