Any Unknown or Unlisted Aircraft Manufacturer
Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Communication Breakdown; Situational Awareness
Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Took Evasive Action
Airspace Structure; Human Factors; Procedure
Departed HND planning to obtain IFR flight plan when out of LAS area.  When handed off to LAS Departure climbing out on east side down wind departure about 6000 and climbing; stated altitude and climbing to 17.5.  Departure said [I] was in their airspace-without clearance; descend below class B airspace.  Started immediate descent (rising terrain ahead East of HND) and asked what altitude to clear airspace.  Approach said get your maps out.  I continued descent as permitted by terrain.  Soon was handed to next controller who said stay below 8000 and call approach on land line when able.  My error not expecting to violate class B when handed direct from tower to departure control.  I thought the hand off would let departure control know I was coming.  I did not know that I needed to get permission to enter the B airspace since I was handed off to departure; thus I expected altitude and vectors to fit in with their traffic.  What I got was look it up and stay out of the airspace.  I do not know of any conflicting traffic.  The second departure controller gave an altitude which was easily complied with.  A single pilot finds it more helpful to be advised of an altitude and/or vector to be in compliance with the airspace than 'look it up'.  A word from the tower controller that class B airspace overlies the airport and the hand off doesn't give clearance into the class B should help the transient avoid this situation.
Pilot departs HND airport and assumes he is cleared into the LAS Class Bravo because he is under flight following.  Pilot violates LAS Class Bravo and is told to descend below it by LAS Approach Controller.