Date: 201202
Local time of day: 1801-2400
Location: ZLA.ARTCC, CA
Aircraft: Shorts SD-330
Flight plan: IFR
Flight phase: Cruise
Airspace: Class E ZLA
ATC / advisory: Center ZLA
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: Nellis Control began a hand off of a Shorts 330 to me. The aircraft had just progressed BTY Southbound. The flight plan indicated the aircraft was filed RNO./.BTY..EED..BXK..TFD..MJJ. Due to limited RADAR below 140 in ZLA16; we require all aircraft to be placed on an airway in that vicinity. I called Nellis and requested the aircraft be routed via V135.CLARR..EED. Radio communications are a problem with aircraft low level in that area also and all of my communications with the pilot were very scratchy at best and many things had to be repeated. The aircraft checked in level at 130 and appeared to be on the airway; however I did verify with the pilot that they were established on V135. The pilot responded that they were not established and were given direct CLARR from the previous controller. I issued a clearance to join the airway to CLARR; advised the pilot that the routing was because I would probably loose RADAR with him; and the pilot responded. At some point I thought the pilot requested direct 'Bard' which was not on his flight plan. I told the pilot that BZA was not on the flight plan and again told him I needed him on the airway because of RADAR limitations. I then read the pilot his entire clearance to verify everything was correct; which he said it was. Then; approximately 2 minutes later; I noticed the aircraft make a 25+ degree left turn off course still level at 130 and head towards a MIA of 145. Upon questioning the pilot told me they were going to EED and couldn't find CLARR. I put the aircraft on a 160 heading to intercept the airway and again told the pilot I needed him on the airway for RADAR coverage. I observed the aircraft turn to the 160 heading then 1 minute later he started to climb. Upon questioning; the pilot told me that 'according to the flight plan he was supposed to climb' and that I had given him a climb clearance to 16;000. I told him to climb to 160 since at that altitude I wouldn't lose RADAR and reissued the entire clearance again. Once the aircraft climbed above 150; I cleared him direct to EED and gave him the possible deviation phone number. Better radios and RADAR in that area would definitely help. I could barely hear many things the pilot said and I still am not 100% sure the read backs I heard were accurate. However; I don't see how the pilot could have thought I told him to climb. In addition I don't know why Nellis failed to issue the correct clearance before I even talked to him.




Synopsis: ZLA Controller described a confused climb clearance and routing event involving an aircraft being transferred from Nellis ATC; the reporter listing problematic radio/RADAR coverage and incorrect routing issuance as causal factor.