Md-82 flight crew reported an altitude overshoot resulted when the pilot flying experienced some con...

Narrative:

[Flight] to dfw. Original clearance was dct fewww SEEVR3 dfw. ATC changed our arrival from the SEEVR3 to the BRDJE3 arrival. Gfms was reprogrammed and verified. I then selected and viewed the BRDJE3 arrival on my ipad air and used the checkmark to list it at the bottom of the screen. Shortly after receiving the new clearance ATC gave us numerous heading; altitude and speed changes. Then ATC cleared us direct to the brdje fix and to descend via the BRDJE3 arrival.due to the reroute I now had both the SEEVR3 and BRDJE3 arrivals check marked on my ipad. I inadvertently selected the SEEVR3 arrival and believed I had selected the BRDJE3 arrival. I then zoomed in my ipad screen to the brdje fix and started my descent. Both arrivals are nearly identical; and both have brdje fixes but have different altitudes associated with the brdje fix. My first officer initially missed the incorrect altitude for BRDJE3 due to cockpit duties. However he did quickly discover the mistake. We very briefly descended below the 17;000 ft altitude and then immediately climbed back to 17;000 ft before joining the arrival at brdje. At no time were there any traffic conflicts and we received no calls from ATC. The remainder of the arrival was normal.this was my first trip using the new ipad air and the jepp FD-pro program. From now on when I get an arrival reroute; I will uncheck and remove the previous assigned arrival and only have one arrival in the charts selected for use on that leg. This will prevent accidental selection when toggling between other charts. I will also be more vigilant in verifying that I am viewing the correct chart; prior to zooming in the ipad screen. In addition I will also ensure that both crewmembers are 100% in the loop and fully in concurrence when setting up new fix clearances.

Original NASA ASRS Text

Title: MD-82 flight crew reported an altitude overshoot resulted when the pilot flying experienced some confusion associated with two arrivals being simultaneously loaded in his iPad.

Narrative: [Flight] to DFW. Original clearance was DCT FEWWW SEEVR3 DFW. ATC changed our arrival from the SEEVR3 to the BRDJE3 arrival. GFMS was reprogrammed and verified. I then selected and viewed the BRDJE3 arrival on my iPad Air and used the checkmark to list it at the bottom of the screen. Shortly after receiving the new clearance ATC gave us numerous heading; altitude and speed changes. Then ATC cleared us direct to the BRDJE fix and to descend via the BRDJE3 arrival.Due to the reroute I now had both the SEEVR3 and BRDJE3 arrivals check marked on my iPad. I inadvertently selected the SEEVR3 arrival and believed I had selected the BRDJE3 arrival. I then zoomed in my iPad screen to the BRDJE fix and started my descent. Both arrivals are nearly identical; and both have BRDJE fixes but have different altitudes associated with the BRDJE fix. My first officer initially missed the incorrect altitude for BRDJE3 due to cockpit duties. However he did quickly discover the mistake. We very briefly descended below the 17;000 ft altitude and then immediately climbed back to 17;000 ft before joining the arrival at BRDJE. At no time were there any traffic conflicts and we received no calls from ATC. The remainder of the arrival was normal.This was my first trip using the new iPad Air and the Jepp FD-Pro program. From now on when I get an arrival reroute; I will uncheck and remove the previous assigned arrival and only have one arrival in the charts selected for use on that leg. This will prevent accidental selection when toggling between other charts. I will also be more vigilant in verifying that I am viewing the correct chart; prior to zooming in the iPad screen. In addition I will also ensure that both crewmembers are 100% in the loop and fully in concurrence when setting up new fix clearances.

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.

Attributes
ACN	1353003
Time
Date	201605
Local Time Of Day	1801-2400
Place
Locale Reference	DFW.Airport
State Reference	TX
Environment
Light	Daylight
Aircraft 1
Make Model Name	MD-82
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Route In Use	STAR BRDJE3
Flight Plan	IFR
Component
Aircraft Component	Tablet
Person 1
Function	Captain Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Person 2
Function	First Officer Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

Md-82 flight crew reported an altitude overshoot resulted when the pilot flying experienced some confusion associated with two arrivals being simultaneously loaded in his ipad.