Date: 201204
Local time of day: 0601-1200
Location: GEU.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: King Air C90 E90
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Initial Climb
Airspace: Class B PHX
ATC / advisory: TRACON LUF; Tower GEU
Reporter organization: Corporate
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Human Factors; Procedure
Primary problem: Procedure

Narrative: I filed an IFR flight plan from Glendale; AZ (GEU) to Roswell; NM (ROW). When I contacted the Glendale Ground Control to receive my IFR clearance I was told the clearance would be issued by Luke AFB Departure controllers immediately on departure; and we were issued by the Glendale Tower a take off clearance with a left downwind departure from Runway 19. I missed the left downwind departure instruction as I was involved in internal communications related to aircraft take off limitations with the other pilot in the aircraft. While departing Glendale; AZ (GEU); I inadvertently penetrated the Phoenix Class B airspace prior to receiving my IFR clearance. I believe several factors contributed to this violation. As the PIC and acting as a CFI I had a certificated pilot as the flying pilot gaining turbine experience. Communication between the two of us was temporarily focused on the proper operation of the aircraft inside the cockpit and situational awareness was lost on my part. Based on the communication with the Glendale Tower Controller I operated under the assumption that an IFR clearance from Luke AFB would be immediate. Immediately after take off; I tried to contact Luke AFB Approach several times and received no immediate reply. Finally; after calling several times; Luke Approach responded with a transponder code. This entire event occurred in a matter of 3-5 minutes; and lack of communication on the part of all parties including myself; was a definite factor. Once communication was established with Luke Approach the use of our N# and a transponder code issued; I operated under the belief that we were now on an IFR clearance; and still awaiting the clearance details. The Glendale; AZ Airport itself has many pitfalls that promote airspace violations. GEU is situated between Luke AFB and the Phoenix Class B airspace and utilizes unusual procedures for departures. The Glendale Airport Control Tower is a non FAA facility and the Non FAA controllers operating this Tower facility have limited control of aircraft arriving or departing GEU. It is also interesting to note that for aircraft departing from Runway 19 at Glendale; there is no procedure in place for the Tower facility to issue IFR clearances. I have never seen a controlled airport (FAA or Contract) that could not issue IFR clearances for all operations departing that facility. Glendale is unique in that the Tower can issue IFR clearances for departures from Runway 1; but not from Runway 19. This appears to be an ongoing struggle between Luke AFB and the Phoenix TRACON; and I was unaware of this unusual limitation until after the fact. The immediate airspace above Glendale is controlled by Luke AFB Approach controllers; and civil aircraft are handled as secondary with low priority by the Luke AFB controllers which I believe was also a major contributing factor in this event.




Synopsis: Corporate IFR departure from GEU entered PHX Class B while awaiting the issuance of an IFR clearance from Luke ATC; the reporter questioning the fact that GEU controllers are unable to issue certain IFR clearances prior to take off.