Medium Large Transport
Air Traffic Control Fully Certified
Air Traffic Control Radar 36; Air Traffic Control Time Certified In Pos 1 (yrs) 24
Confusion; Situational Awareness
ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Procedure
Aircraft was on the TRYST1 arrival (new RNAV).  I descended the aircraft to 6;000 and switched him to Dallas South.  They were busy and by the time they started him down; the aircraft clipped the corner of DR1's airspace (or maybe was 1/2 mile away).  This aircraft was left on the newly designed arrival.  I did not know that the arrival would end up in an airspace violation if I did not turn it off of the arrival.  I understand that I have 'pre-arranged coordination' through that area; but since I did not expect him to go through there; I did not display it to DR1 nor did I display DR1's aircraft as is required for 'Pre-arranged'.This arrival should be changed as to not go through someone else's airspace if I leave him on it.  It should be designed to go from Dallas East airspace to Dallas South's airspace.  An arrival should never be designed to require me to use 'Pre-Arranged Coodination' airspace since that would also require me to make other steps such as displaying the aircraft to DR1 and also to watch all of DR1's tracks while going through this area.  It should also not require me to vector off of the newly designed arrival as the 7110.65 states that we should leave the aircraft on an RNAV Procedure to the extent possible.  In this instance if I could not ensure that the aircraft would be descended; then I would vector off from now on to ensure that it misses DR1's airspace.
D10 controller describes a flight that he descends and ships to another sector. The aircraft clips the corner of a non pointed-out airspace. The Controller has pre-arraigned coordinated use of that airspace; but did not realize the aircraft was going to enter said airspace during the arrival.