Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument
Flight Crew Last 90 Days 66; Flight Crew Total 2808; Flight Crew Type 2000
Airspace Violation All Types
Human Factors
I filed IFR direct to OSI VOR then direct destination per the departure procedure for Runway 12. At takeoff the winds were 310 at 6-8 knots. Since it was VFR I elected to takeoff on Runway 30 and we were at full fuel and within 150 pounds of gross weight.There is a local noise restriction in this direction requiring a climb of 500 feet before turning and right traffic toward the hills running parallel to the runway.Passing 500 feet I started the right turn and immediately knew I had made a mistake. I did not feel comfortable with the turn to come up short of the hills nor was I sure I would be high enough to adequately clear the tops or any obstruction. I froze for a moment then called NorCal with my position and to start IFR flight plan. They gave me a squawk code and informed me of Bravo intrusion.Without the hills and the unknown of obstructions the turn was doable. I was alternately heads down looking at the graphical depiction of the airspace during the process which contributed to my delayed responses and decision making.I did not make any extreme maneuvers to avoid the Bravo rather I called NorCal. A downwind take off was technically doable; but I thought the conditions favored the upwind choice. I was mistaken. Delaying the flight was also an option although weather along my route was changing.I searched the AFD and other sources for comments about Runway 30 at HAF prior to takeoff; but did not see anything that aroused my suspicion. The only airport signs I saw were concerning the noise restrictions although the sign posted at the runway was faded and hard to read.
GA pilot reported a Bravo airspace intrusion on departure from HAF due to an aircraft close to max gross weight and terrain considerations.