Rdu controller providing OJT experienced airspace deviation when departure traffic leveled at lower ...

Narrative:

The leading factors began on initial radar contact. The trainee did not recognize the aircraft stopped his climb at 20. Normal jet departures climb to 70. I allowed time for the trainee to observe this; however we began to get busy with more departures. I stepped in and asked the pilot to confirm his altitude. The pilot verified 20; which was a misunderstanding of the departure procedure. Note (not the first time this has happened) I instructed the aircraft to climb to 120; which is the normal altitude to deliver aircraft to the center. For whatever reason; the trainee took the aircraft out of hand off status; and pointed the aircraft out to fay approach control. I did not catch this mistake as quickly. The aircraft was out of 105 when I observed the aircraft was no longer automating to center. I instructed the aircraft to maintain 100 and began coordinating with the center. The center said to put the aircraft on a 100 heading due to an active altra. The trainee turned the aircraft to a 100 heading; however the aircraft was in fayetteville's airspace. We did not have control for turns. I should have taken over from the trainee much sooner and departure procedure needs to be re-written. We have had numerous misunderstandings due to poorly written departure procedures.

Original NASA ASRS Text

Title: RDU Controller providing OJT experienced airspace deviation when departure traffic leveled at lower than cleared altitude; confused by chart notations; which led to the confused airspace coordination event.

Narrative: The leading factors began on initial RADAR Contact. The trainee did not recognize the aircraft stopped his climb at 20. Normal jet departures climb to 70. I allowed time for the trainee to observe this; however we began to get busy with more departures. I stepped in and asked the pilot to confirm his altitude. The pilot verified 20; which was a misunderstanding of the Departure Procedure. Note (not the first time this has happened) I instructed the aircraft to climb to 120; which is the normal altitude to deliver aircraft to the Center. For whatever reason; the trainee took the aircraft out of hand off status; and pointed the aircraft out to FAY Approach Control. I did not catch this mistake as quickly. The aircraft was out of 105 when I observed the aircraft was no longer automating to Center. I instructed the aircraft to maintain 100 and began coordinating with the Center. The Center said to put the aircraft on a 100 heading due to an active ALTRA. The trainee turned the aircraft to a 100 heading; however the aircraft was in Fayetteville's airspace. We did not have control for turns. I should have taken over from the trainee much sooner and departure procedure needs to be re-written. We have had numerous misunderstandings due to poorly written departure procedures.

Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

Attributes
ACN	912283
Time
Date	201010
Local Time Of Day	1201-1800
Place
Locale Reference	RDU.Airport
State Reference	NC
Aircraft 1
Make Model Name	Citation V/Ultra/Encore (C560)
Operating Under FAR Part	Part 91
Flight Phase	Climb
Route In Use	SID FAY3
Flight Plan	IFR
Person 1
Function	Departure
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 89.5 Flight Crew Total 5300 Flight Crew Type 364.2
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy

Rdu controller providing OJT experienced airspace deviation when departure traffic leveled at lower than cleared altitude; confused by chart notations; which led to the confused airspace coordination event.