Date: 201409
Local time of day: 0601-1200
Location: ZID.ARTCC, IN
Light: Daylight
Aircraft: Medium Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZID
ATC / advisory: Center ZID
Reporter organization: Government
Reporter function: Enroute; Handoff / Assist
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: Procedure
Primary problem: Procedure

Narrative: Aircraft X was cleared to cross FRIZN at 110. At about 20 miles north of FRIZN (4 min) the radar controller asked Aircraft X if he was still going to make FRIZN at 110. The response was yes although as we looked at it we all thought that there was no way he was going to make the crossing. At about 5 miles (1 min) from FRIZN Aircraft X had about 6000 feet to descend to make the crossing and he comes back and says that he is going to be high at FRIZN. The Radar Controller issues a descent to 110. Since this was a known issue and especially with Aircraft X company I asked the Radar if I could talk to Aircraft X. He agreed and I asked Aircraft X if he was showing a range of altitudes in his FMS or if it was an AOA 110 at FRIZN or if it was a hard altitude. He thought it said AOA 110. I explained the issue we had been experiencing and he thought it may be limited to the series.This has not been our experience at ZID as it has happened with other series aircraft and some other type aircraft carriers. Shortly there after another aircraft came in for the same arrival and was issued the same clearance. I again asked the R to speak and he agreed. I asked the aircraft the same questions as Aircraft X as to what his FMS was showing and he said that it shows an AOA 110 but they were going to cross FRIZN at 110. He said that they have to go into the FMS and override the OPD (optimum profile descent) altitude (AOA 110) in order to make the crossing at FRIZN at 110 otherwise it assumes you are on the OPD.This has been a recurring problem and we have discussed it in the airspace meeting on multiple occasions. Each time we reiterate the importance to file reports on all occurrences although I don't think that all people are filing because in a lot of instances. The issue is addressed before there is an actual PD and coordination is completed with SDF to amend the crossing restriction. ZID 530 office was going to contact Aircraft X's company since they seemed to be the highest offender. I do not know what the result of that call was as of now. I think that this is a huge safety issue especially if you are issuing the crossing for traffic as well as to meet LOA inbound to the airport. If Aircraft X is having this issue on the FRIZN OPD how are they dealing with this on other OPD arrivals? The pilots need to identify if their FMS is showing AOA or if it is a hard altitude and if they have to over ride the OPD.




Synopsis: ZID Controller describes a problem with At or Above (AOA) altitude that pilots have in the FMS; but the Controller requests a hard altitude.  Pilots show an AOA altitude and have to manipulate the FMS to cross at a specific altitude.