Date: 201502
Local time of day: 0001-0600
Location: ZSE.ARTCC, WA
Light: Night
Aircraft: Small Transport
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class D OTH; Class E ZSE
ATC / advisory: Center ZSE
Reporter organization: Government
Reporter function: Enroute; Instructor
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Training / Qualification; Situational Awareness; Troubleshooting; Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I was conducting OJTI on R-36 (combined with 30 and 10).  I don't recall exactly but I am pretty confident it was VFR and OTH was advertising visual approaches.  Just before we took the position; OTH TWR called to request a release on Aircraft X.  The previous controller gave the release without restrictions before beginning the relief briefing.  Aircraft X had a filed route of OTH..UBG..PDX and altitude request of 150.  Aircraft X came up on our frequency 'Out of 800 feet on runway heading.'  The CPC-IT acknowledged and issued the OTH altimeter.  I then immediately keyed up and asked the pilot to verify they were assigned runway heading and which runway they departed.  She responded with 'Affirmative; runway 22.'  We do not have radar to the ground in this area.  Per our LOA; OTH is to assign the routing relayed by Sector 36 in the departure clearance to aircraft.  There is no procedure that allows ZSE or OTH TWR to assign headings on departure.  Only the OTH5 SID; ODP or 'As filed' routing clearances are legal.  A minute later we radar identified Aircraft X approximately 5 miles SW of OTH at about 20.  With the aircraft inside a 30 MIA; I told the CPC-IT to issue Aircraft X 'Leaving 30; cleared direct UBG' to return the aircraft on course ASAP; since they were effectively heading in the opposite direction of their desired course.Another controller from our area had a similar event occur with OTH TWR a few weeks ago but this was my first direct experience.  I was admittedly a bit surprised and initially wasn't sure what to think.  My instinct was to give OTH TWR the benefit of the doubt and assume that the pilot of Aircraft X was somehow mistaken about their clearance.  I eventually decided to call OTH TWR back and tell them that this particular aircraft had come over to us on a runway heading.  The controller replied simply; 'We don't give runway heading' and re-iterated that they issued 'Direct UBG' in this case.  I simply said 'OK' and gave my initials.  In hindsight; the OTH TWR response struck me as a bit odd.  Personally; if I was working at OTH; had issued 'Direct UBG' or 'As filed' to this pilot and the center controller later called to tell me the aircraft come over assigned runway heading I would have likely replied; 'Really?!  That's crazy!  I issued such and such...'  You get the idea.There needs to be a discussion with OTH TWR regarding departure clearances and/or takeoff instructions.  This is unacceptable.




Synopsis: ZSE Controller describes an aircraft departure procedure that was not followed; and blames the tower for not issuing the correct routing.