Golden Eagle 421
Air Traffic Control Fully Certified
Communication Breakdown
ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Procedure; Airspace Structure; Human Factors
There was a TFR in place for fire fighting with airspace penetrating a significant portion of SAF's Class D airspace to the northwest. SAF ATCT called for release of Aircraft X stating he was ready to depart Runway 28. I gave approval for release and assigned an altitude of 15;000. I assumed that an 'as filed' clearance was my safest bet and that the Tower would ensure separation from the TFR as it was in their airspace and the filed flight plan was Eastbound away from the protected area. Shortly after authorizing release; the aircraft departed and checked in. He proceeded to question whether he should continue on runway heading or turn on course; which surprises me as he is flying directly toward the TFR; and ultimately violated separation standards for that airspace. After inquiring what the Tower gave him as a clearance; I ultimately explained that I wasn't able to provide course guidance since he was still well below my MIA. I eventually advised him to turn on course to avoid the TFR. The aircraft turned Eastbound and was handled otherwise without incident. When a TFR impacts airspace to this degree; some procedure needs to be worked up quickly to ensure separation. Even if it's an ad hoc set of initial departure headings or relevant ATIS information for pilots. This is the 3rd time I have personally experienced a pilot departing SAF under an 'as filed' clearance where the pilot has departed and not turned on course in a timely manner; thinking/waiting for ATC to provide additional instructions. Perhaps a mandatory ODP should be assigned for aircraft proceeding northeast/east/southeast bound out of SAF due to the terrain; but that wasn't so much an issue in this case. Ultimately; in this case; I feel the proximity of the TFR; combined with the departing Runway 28 put the aircraft at unnecessary risk of violating that airspace. Runway 28 should not be available for departures while this TFR is in effect.
ZAB Controller described a fire fighting TFR incursion involving a released IFR departure from SAF. The reporter noted no temporary procedures were in place to ensure clearance from the TFR airspace.