Date: 201706
Local time of day: 0601-1200
Location: DFW.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Descent
Airspace: Class A ZFW
ATC / advisory: Center ZFW
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Confusion
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: We were level at FL240 and cleared to descend via the BEREE1 arrival into DFW. I verified we were in 'prof' and dialed in 11000 into the Altitude select window. We were between POWND and WUUKY and I noticed the airplane wanted to start the descent and we were high on 'prof' and I was concerned about future altitude and speed restraints on the STAR. Without thinking and double checking; I had the FO delete the restriction at WUUKY and we began the descent. After calling out of FL240 to center; they queried us on if we had the correct STAR loaded in the FMS and told us to maintain FL230. At this point; I realized my mistake. About 30 seconds later after we crossed WUUKY; Center gave us the descend via clearance again and we flew the rest of the STAR properly and landed uneventfully at DFW. Center did not say anything about a traffic conflict.On the ground; I could not put in the proper cruise altitude in the FMS due to a higher altitude restraint on our cleared routing. Since we were only climbing to FL240; I deleted the FL300 to FL240 window at WUUKY and put a hard altitude of FL240 so I could put the proper cruise altitude into the FMS. During the execution of the STAR; I cleared the altitude at WUUKY when I saw the airplane wanted to descend and we were getting high on profile. I was not thinking about the FL240 restriction at WUUKY and I should not have cleared the altitude and just accepted the high indications until reaching WUUKY. Even though I briefed the entire star and checked the altitudes before we began the STAR; I did not pay attention to the WUUKY fix with the altitude restraint of FL240 when we got the descend via clearance. This was a dumb mistake on a short flight into high density traffic area. I should not be adjusting altitudes on the STAR and I should double check the restrictions as we approach each point. If I would have double checked where we were instead of fixating on the high profile indication; I think this could have been prevented.


Second narrative: Human error caused this event to occur. The leg to DFW is short and busy. We had a number of crossing restrictions on this STAR; and unfortunately deleted one of these altitude constrictions. As pilot monitoring I should not have cleared this restriction without cross reference to the depicted STAR on our STAR diagram.


Synopsis: MD11 flight crew reported deleting a crossing restriction on the BEREE1 Arrival to allow the aircraft to descend on the FMC profile. They did not realize that the altitude deleted was an actual restriction and not just their cruising altitude.