Narrative:

We were cleared on the LECTR1 arrival into dtw which is for landing north but the airport was landing south. We were between shanx and hanbl on the arrival and were maintaining 17000 ft and had not been given a descend via clearance yet. On the LECTR1; the hanbl fix says to cross at or above 11000 ft. ATC told us to switch to the HANBL1 arrival. In hindsight I cannot remember how the controller phrased the clearance but it was a little confusing so I verified that we were now cleared on the HANBL1 and we were cleared to descend via; which he confirmed. My first officer (first officer) dialed in 11000 ft; which I confirmed; and he started a descent. The controller then asked us if we were going direct to hanbl; which I confirmed. He then told us to descend and maintain 15000 ft; which we complied with. At that point I realized that we still had the LECTR1 arrival in the FMS. I then switched the arrival and my first officer confirmed it. I then pulled up the HANBL1 arrival on my charts and saw that the crossing restriction for hanbl on the HANBL1 arrival is different and requires us to cross between FL210 and 17000 ft. At that point I realized that we had descended too early on the new arrival segment and made an altitude deviation. The main factor in this deviation was my inexperience with these new arrivals into dtw. I had not been flying for several weeks after these arrival came into effect; so this was only the 4th or 5th time I had gone into dtw with these new arrivals. We were expecting to get switched onto another arrival but I didn't know which one it would be. When ATC cleared us we were already well into the old arrival and I think that we were both anxious about starting down for the old crossing restrictions. When we were switched I just assumed that since the new arrival had the same fix that the crossing restriction would be the same. The fact that both arrivals had the same fix and the fact that we wouldn't be making a lateral change in our flight path for at least 10 miles made me think that I had some time to change the arrival in the FMS and that the descent should take priority in my monitoring duties. This is the third airport that I have been based at that has switched over to RNAV arrivals so I was prepared for a teething period with both how we fly them and how ATC assigned them. I knew that there can be confusing clearances given as the controller get used to the arrivals; which is why I verified the descend clearance when they switched our arrival. However after this incident happened I couldn't remember of any arrivals in the past that had the same arrival fix on two different arrivals with two different altitude restrictions. Perhaps an [alert] could be issued if this problem is happening with other crews. I think it might be a unique situation to dtw; where our prior experience might not be enough of a safeguard against this type of issue happening to other crews unless they are made aware of the issue.

Google
 

Original NASA ASRS Text

Title: CRJ900 Captain reported missing crossing restriction due to wrong STAR entered into FMS.

Narrative: We were cleared on the LECTR1 arrival into DTW which is for landing north but the airport was landing south. We were between SHANX and HANBL on the arrival and were maintaining 17000 ft and had not been given a descend via clearance yet. On the LECTR1; the HANBL fix says to cross at or above 11000 ft. ATC told us to switch to the HANBL1 arrival. In hindsight I cannot remember how the controller phrased the clearance but it was a little confusing so I verified that we were now cleared on the HANBL1 and we were cleared to descend via; which he confirmed. My FO (First Officer) dialed in 11000 ft; which I confirmed; and he started a descent. The controller then asked us if we were going direct to HANBL; which I confirmed. He then told us to descend and maintain 15000 ft; which we complied with. At that point I realized that we still had the LECTR1 arrival in the FMS. I then switched the arrival and my FO confirmed it. I then pulled up the HANBL1 arrival on my charts and saw that the crossing restriction for HANBL on the HANBL1 arrival is different and requires us to cross between FL210 and 17000 ft. At that point I realized that we had descended too early on the new arrival segment and made an altitude deviation. The main factor in this deviation was my inexperience with these new arrivals into DTW. I had not been flying for several weeks after these arrival came into effect; so this was only the 4th or 5th time I had gone into DTW with these new arrivals. We were expecting to get switched onto another arrival but I didn't know which one it would be. When ATC cleared us we were already well into the old arrival and I think that we were both anxious about starting down for the old crossing restrictions. When we were switched I just assumed that since the new arrival had the same fix that the crossing restriction would be the same. The fact that both arrivals had the same fix and the fact that we wouldn't be making a lateral change in our flight path for at least 10 miles made me think that I had some time to change the arrival in the FMS and that the descent should take priority in my monitoring duties. This is the third airport that I have been based at that has switched over to RNAV arrivals so I was prepared for a teething period with both how we fly them and how ATC assigned them. I knew that there can be confusing clearances given as the controller get used to the arrivals; which is why I verified the descend clearance when they switched our arrival. However after this incident happened I couldn't remember of any arrivals in the past that had the same arrival fix on two different arrivals with two different altitude restrictions. Perhaps an [alert] could be issued if this problem is happening with other crews. I think it might be a unique situation to DTW; where our prior experience might not be enough of a safeguard against this type of issue happening to other crews unless they are made aware of the issue.

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.