Narrative:

We were initially cleared into dfw via the SEEVR1 arrival. We noticed a notam on the ATIS that warned flight crews descending below 11000 at stonz and 3 other fixes. We noted that this wasn't on our arrival. While flying direct to rrnet; we were cleared via the BRDJE1 arrival; which also uses rrnet as a fix. We re-briefed the new arrival noting that this included this fix crossing that the ATIS had warned. The task saturation was quite busy during the descent. The lca's have been teaching us to set the lowest altitude on the 'descend via' arrivals. This is how we had our fcp configured. Somehow; we failed to level off at stonz at 11000 and caught our error over the fix at 10000. Our fcp was set to level off at 8000 at rockz. We notified ATC of our error and were issued a new clearance to remain at 10000. We continued and landed without incident. I think the biggest mistake was to set the altitude preselect at the lowest hard altitude when there is a higher hard altitude to obey. If we would have set our altitude preselect at the highest hard altitude; the aircraft would have leveled off and then we could have set the next one after the level off. I recently finished oe on the crj 900 and I was taught to set in the lowest altitude; but this will not protect from this type of event. Setting the next hard altitude may be a better technique in this situation. Descend via RNAV arrivals in general increase the flight deck workload many times over and exponentially increase the chance of deviations in aircraft without VNAV and auto throttles like the crj. Obviously this has been a problem at dfw since it was stated in the atis.

Related reports:

Google
 

Original NASA ASRS Text

Title: CRJ-900 flight crew reports missing a crossing restriction at STONZ on the BRDJE1 RNAV arrival to DFW. The minimum altitude on the arrival of 8000 feet was set in the MCP and the vertical speed was being controlled via the autopilot; as the aircraft has no VNAV capability.

Narrative: We were initially cleared into DFW via the SEEVR1 arrival. We noticed a notam on the ATIS that warned flight crews descending below 11000 at STONZ and 3 other fixes. We noted that this wasn't on our arrival. While flying direct to RRNET; we were cleared via the BRDJE1 arrival; which also uses RRNET as a fix. We re-briefed the new arrival noting that this included this fix crossing that the ATIS had warned. The task saturation was quite busy during the descent. The LCA's have been teaching us to set the lowest altitude on the 'descend via' arrivals. This is how we had our FCP configured. Somehow; we failed to level off at STONZ at 11000 and caught our error over the fix at 10000. Our FCP was set to level off at 8000 at ROCKZ. We notified ATC of our error and were issued a new clearance to remain at 10000. We continued and landed without incident. I think the biggest mistake was to set the altitude preselect at the lowest hard altitude when there is a higher hard altitude to obey. If we would have set our altitude preselect at the highest hard altitude; the aircraft would have leveled off and then we could have set the next one after the level off. I recently finished OE on the CRJ 900 and I was taught to set in the lowest altitude; but this will not protect from this type of event. Setting the next hard altitude may be a better technique in this situation. Descend Via RNAV arrivals in general increase the flight deck workload many times over and exponentially increase the chance of deviations in aircraft without VNAV and auto throttles like the CRJ. Obviously this has been a problem at DFW since it was stated in the atis.

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.