Beechjet 400
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 38
Situational Awareness; Other / Unknown
ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance
Human Factors
I was relieving the Developmental and Instructor on DAG. During the briefing; a BE400 reports on frequency; the Developmental advises the pilot to contact Departure on 133.95 which is the correct and published departure control frequency. I took the sector; signed-on; and started to adjust my RADAR scope when the BE400 asks for the departure frequency again. I displayed the aircraft because it wasn't on my tag and had only a limited data block; told the MEAD Controller that I still had him on frequency and requested control. I then climbed the BE400 to 19;000 FT and turned him to heading 100 away from NATCF's [Nellis] airspace. I then noticed how low he was and advised the pilot to climb immediately for terrain. I then RADAR identified him; turned him back on course; and advised him to contact ZLA. The pilot did not appear to comply with the published HOOVR3 minimum obstacle climb rate of 328 FT per NM to 5;000 FT. I recommend the Departure frequencies be highlighted and clarified on all Las Vegas DP's; because this wrong frequency issue happens frequently even with U.S. registered aircraft; yet alone foreign ones.
L30 Departure Controller reports noticing a departing BE400 well below the required altitude for terrain separation and the HOOVR3 SID restrictions. The foreign pilot had trouble switching to the correct departure control frequency.