Narrative:

I was not fully configured and about 10 KTS fast at the thousand foot call and elected to continue the approach; subsequently unstable. The first officer made the correct call-outs 'not stable; go-around.' on approach to 17R at pudong 1;500 feet to glideslope (G/south) intercept; 160 KTS. I planned to call flaps 20; gear down at intercept but tower interrupted with RVR reports and clearance to land. (I was still trying to get my seat adjusted and HUD display set since it was my first landing certified to use the HUD which added to my loss of situational awareness momentarily.) all I got out was flaps 20 call before the PNF responded to the tower. By now we're 1;300 feet AGL when I call for gear down/flaps 30 with 15 KTS to lose. PNF commented at about 1;200 feet we weren't going to be stable at 1;000 feet. Flaps and speed both reached at 1;000 feet AGL at the same time but the before landing checklist was not complete therefore it should have been a go-around. If I had it do over I would have gone around; and I will next time! And I would most definitely have been fully configured at 'G/south alive;' call instead of waiting. Not good CRM along with poor leadership which; I'm sure frustrated the PNF to no end. I took full responsibility and we debriefed it thoroughly. Please see above comments but basically allowed the HUD to become a distraction rather than a landing aid.comply with standard operating procedures at all times.

Google
 

Original NASA ASRS Text

Title: A widebody Captain flying his first approach utilizing HUD failed to achieve stabilized approach criteria until right at 1;000 AGL at which time the First Officer advised a go-around was appropriate per SOP. The Captain opted to continue the approach and landed safely. A complete debrief of the event ensued after parking.

Narrative: I was not fully configured and about 10 KTS fast at the thousand foot call and elected to continue the approach; subsequently unstable. The First Officer made the correct call-outs 'NOT STABLE; GO-AROUND.' On approach to 17R at Pudong 1;500 feet to glideslope (G/S) intercept; 160 KTS. I planned to call Flaps 20; Gear Down at intercept but Tower interrupted with RVR reports and clearance to land. (I was still trying to get my seat adjusted and HUD display set since it was my first landing certified to use the HUD which added to my loss of situational awareness momentarily.) All I got out was Flaps 20 call before the PNF responded to the Tower. By now we're 1;300 feet AGL when I call for Gear Down/Flaps 30 with 15 KTS to lose. PNF commented at about 1;200 feet we weren't going to be stable at 1;000 feet. Flaps and speed both reached at 1;000 feet AGL at the same time but the Before Landing Checklist was not complete therefore it should have been a go-around. If I had it do over I would have gone around; and I will next time! And I would most definitely have been fully configured at 'G/S ALIVE;' call instead of waiting. Not good CRM along with poor leadership which; I'm sure frustrated the PNF to no end. I took full responsibility and we debriefed it thoroughly. Please see above comments but basically allowed the HUD to become a distraction rather than a landing aid.Comply with standard operating procedures at all times.

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.