Narrative:

Center cleared this aircraft direct smoov and failed to enter it into enroute automation modernization (eram) (eram showed the aircraft routed over the howrr transition for the smoov arrival). I eventually noticed that the aircraft was not flying the route I expected it to fly; and that's when I had to figure out how to clear him back onto the route and issue a descend via clearance. So I have him direct smoov and issued the descend via clearance; but I had forgotten that the crossing restriction for smoov is at or above 10;000 feet. It had been 12;000 feet for ages before these new optimal profile descent arrivals. The aircraft descended early down to 10;000 feet into A80 macon sector's airspace before crossing the boundary for the new shelf which has been set aside for this descent. There was no loss of separation or conflict. 10;000 feet at transfer of control point smoov is a terrible design. It dramatically increases complexity and controller phraseology in any situation where an aircraft isn't flying the entire arrival as published. Today; it was because a prior controller in ZJX shortcutted the aircraft direct smoov (even though they're not supposed to); but during thunderstorm season there will be many times when aircraft will be deviating off of the published route for the STAR. The transfer of control point (tcp) (smoov) should be changed to at or above 11;000 feet; at the very least; thus totally eliminating any risk of an aircraft descending too soon into approach airspace without excessive verbiage from the controller.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air Traffic Controller reported working with a new arrival procedure that was issued an incorrect crossing restriction to an aircraft.

Narrative: Center cleared this aircraft direct SMOOV and failed to enter it into Enroute Automation Modernization (ERAM) (ERAM showed the aircraft routed over the HOWRR transition for the SMOOV arrival). I eventually noticed that the aircraft was not flying the route I expected it to fly; and that's when I had to figure out how to clear him back onto the route and issue a DESCEND VIA clearance. So I have him direct SMOOV and issued the DESCEND VIA clearance; but I had forgotten that the crossing restriction for SMOOV is at or above 10;000 feet. It had been 12;000 feet for ages before these new Optimal Profile Descent arrivals. The aircraft descended early down to 10;000 feet into A80 MACON sector's airspace before crossing the boundary for the new shelf which has been set aside for this descent. There was no loss of separation or conflict. 10;000 feet at Transfer of Control Point SMOOV is a terrible design. It dramatically increases complexity and controller phraseology in any situation where an aircraft isn't flying the entire arrival as published. Today; it was because a prior controller in ZJX shortcutted the aircraft direct SMOOV (even though they're not supposed to); but during thunderstorm season there will be many times when aircraft will be deviating off of the published route for the STAR. The Transfer of Control Point (TCP) (SMOOV) should be changed to at or above 11;000 feet; at the very least; thus totally eliminating any risk of an aircraft descending too soon into approach airspace without excessive verbiage from the controller.

Data retrieved from NASA's ASRS site 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.