Narrative:

On visual approach to runway 4 at ama; heading to outer marker; runway off first officer (first officer) side. He said he had runway in sight. I went to enlarge my approach pictorial on ipad to verify altitudes and it disappeared. It took me repeated tapping to get page up so I was distracted. While my attention was diverted; the first officer apparently made a right turn to go between marker and runway. He then announced he was high and started a descent. I was confused as it seemed too soon and questioned where runway was; as I still could not see it due to angle of approach. As he turned I saw a short runway he was headed for and announced 'that is not ama; do not descend'. He became confused. We both called go-around. We began a go-around and saw the ama runway ahead of us. We were a little high but headed for it. We configured for landing. He was high and one sink rate warning below 1000 feet. I called sink rate. He brought power up and I thought he was going around but he continued descent and we landed. It all happened very fast. I thought we were high but it was very difficult to tell as the runway has very little lighting and markings. We landed a little long and exited the usual taxiway. We debriefed. I explained it was always better to go to marker and that if he was confused we should have gone around as I could not see runway until the 90 degree turn and was relying on him to see it at that point. I did not know he had not been to this airport before.better crew coordination. If you are unsure say so. Slow down. Go around. If you are tired/fatigued let the other pilot know. Don't work 6 days in a row. I don't understand why ama does not get better runway lights and markings. It is a black hole that can suck you in.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air carrier Flight Crew described a night visual approach to Runway 4 at AMA with the First Officer flying that resulted in the misidentification of TDW as AMA. The Captain detected the error and a go around was initiated then AMA was sighted and the go around was abandoned. An unstable approach was flown to landing at AMA. Fatigue was cited as a factor by the First Officer.

Narrative: On visual approach to Runway 4 at AMA; heading to outer marker; runway off First Officer (FO) side. He said he had runway in sight. I went to enlarge my approach pictorial on iPad to verify altitudes and it disappeared. It took me repeated tapping to get page up so I was distracted. While my attention was diverted; the FO apparently made a right turn to go between marker and runway. He then announced he was high and started a descent. I was confused as it seemed too soon and questioned where runway was; as I still could not see it due to angle of approach. As he turned I saw a short runway he was headed for and announced 'that is not AMA; do not descend'. He became confused. We both called go-around. We began a go-around and saw the AMA runway ahead of us. We were a little high but headed for it. We configured for landing. He was high and one sink rate warning below 1000 feet. I called sink rate. He brought power up and I thought he was going around but he continued descent and we landed. It all happened very fast. I thought we were high but it was very difficult to tell as the runway has very little lighting and markings. We landed a little long and exited the usual taxiway. We debriefed. I explained it was always better to go to marker and that if he was confused we should have gone around as I could not see runway until the 90 degree turn and was relying on him to see it at that point. I did not know he had not been to this airport before.Better crew coordination. If you are unsure say so. Slow down. Go around. If you are tired/fatigued let the other pilot know. Don't work 6 days in a row. I don't understand why AMA does not get better runway lights and markings. It is a black hole that can suck you in.

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.