ZTL controller described a failed altitude crossing event resulting in airspace incursions; the repo...

Narrative:

I was working the controller in charge position in area 2 when the R29 controller informed me that aircraft X had descended unexpectedly into gso approach airspace. He called the gso controller and made a point out after the aircraft had already descended into their airspace. He had already transferred communications to clt approach when the incident occurred. Aircraft X was a rdu departure on the kells 2 opd arrival into clt. The aircraft was vectored off course then turned direct majic and instructed to 'descend via the kells 2 arrival; south transition.' the aircraft should have crossed majic at or above 13;000 ft per the kells 2 descent profile. When I was notifying the watch desk of the incident I noticed a strip for aircraft Y; also off of rdu; on the area desk with 'kells descended to 12;600 ft' written on it from approximately 4 hours before. I called the day shift supervisor and he informed me that it was the same situation; which the aircraft had descended below the published altitude at majic after being vectored off course. There is an obvious safety issue here that needs to be addressed as soon as possible. Suspend kells operations for rdu departures until the problem can be identified and resolved.

Original NASA ASRS Text

Title: ZTL Controller described a failed altitude crossing event resulting in airspace incursions; the report including both the ATC and flight crew perspectives regarding this event.

Narrative: I was working the CIC position in Area 2 when the R29 Controller informed me that Aircraft X had descended unexpectedly into GSO Approach airspace. He called the GSO Controller and made a point out after the aircraft had already descended into their airspace. He had already transferred communications to CLT Approach when the incident occurred. Aircraft X was a RDU departure on the KELLS 2 OPD arrival into CLT. The aircraft was vectored off course then turned direct MAJIC and instructed to 'descend via the KELLS 2 Arrival; South transition.' The aircraft should have crossed MAJIC at or above 13;000 FT per the KELLS 2 descent profile. When I was notifying the watch desk of the incident I noticed a strip for Aircraft Y; also off of RDU; on the area desk with 'KELLS descended to 12;600 FT' written on it from approximately 4 hours before. I called the day shift supervisor and he informed me that it was the same situation; which the aircraft had descended below the published altitude at MAJIC after being vectored off course. There is an obvious safety issue here that needs to be addressed ASAP. Suspend KELLS operations for RDU departures until the problem can be identified and resolved.

Data retrieved from NASA's ASRS site as of July 2013 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	1052583
Time
Date	201212
Local Time Of Day	1801-2400
Place
Locale Reference	CLT.Airport
State Reference	NC
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	STAR KELLS2
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Altitude Overshoot Deviation - Procedural Published Material / Policy

ZTL controller described a failed altitude crossing event resulting in airspace incursions; the report including both the ATC and flight crew perspectives regarding this event.