A B737 check airman reports a pilot on day 2 of IOE executed a go around on an unstabilized approach...

Attributes
ACN	751955
Time
Date	200708
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : rdu.airport
State Reference	NC
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : rdu.tower
Operator	common carrier : air carrier
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	landing : go around
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain observation : company check pilot oversight : pic
Experience	flight time last 90 days : 126 flight time type : 8000
ASRS Report	751955
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : company policies other anomaly
Independent Detector	other flight crewa
Resolutory Action	flight crew : executed go around flight crew : regained aircraft control
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

We had just come to the end of a long flight. The first officer was on his second day; and had already flown 2 legs. This was his third for the day. We were in a -700 and got high because of his inexperience. (We had discussed configns; techniques and computations several times and he just simply got behind.) a go around was initiated as directed by the pilot monitoring. On the go around we were vectored initially to runway 5L; and then changed to runway 5R. We did not get the localizer course set in properly and inadvertently intercepted final for runway 5L; then corrected to runway 5R. We were within parameters for the stabilized approach with 1 speed callout for low speed (slightly below reference -- correcting). The runway has a slope; and a 'firm' landing was made; but certainly within the 'norm' for company flts. The first officer is truly doing a good job and just got to the end with a not so pleasant completion to his flying for the day. Pay more attention to the 'fatigue' factor for a new first officer.

Original NASA ASRS Text

Title: A B737 CHECK AIRMAN REPORTS A PILOT ON DAY 2 OF IOE EXECUTED A GAR ON AN UNSTABILIZED APCH AND FOLLOWED WITH A FIRM TOUCHDOWN. FATIGUE A FACTOR.

Narrative: WE HAD JUST COME TO THE END OF A LONG FLT. THE FO WAS ON HIS SECOND DAY; AND HAD ALREADY FLOWN 2 LEGS. THIS WAS HIS THIRD FOR THE DAY. WE WERE IN A -700 AND GOT HIGH BECAUSE OF HIS INEXPERIENCE. (WE HAD DISCUSSED CONFIGNS; TECHNIQUES AND COMPUTATIONS SEVERAL TIMES AND HE JUST SIMPLY GOT BEHIND.) A GAR WAS INITIATED AS DIRECTED BY THE PLT MONITORING. ON THE GAR WE WERE VECTORED INITIALLY TO RWY 5L; AND THEN CHANGED TO RWY 5R. WE DID NOT GET THE LOC COURSE SET IN PROPERLY AND INADVERTENTLY INTERCEPTED FINAL FOR RWY 5L; THEN CORRECTED TO RWY 5R. WE WERE WITHIN PARAMETERS FOR THE STABILIZED APCH WITH 1 SPD CALLOUT FOR LOW SPD (SLIGHTLY BELOW REF -- CORRECTING). THE RWY HAS A SLOPE; AND A 'FIRM' LNDG WAS MADE; BUT CERTAINLY WITHIN THE 'NORM' FOR COMPANY FLTS. THE FO IS TRULY DOING A GOOD JOB AND JUST GOT TO THE END WITH A NOT SO PLEASANT COMPLETION TO HIS FLYING FOR THE DAY. PAY MORE ATTN TO THE 'FATIGUE' FACTOR FOR A NEW FO.

Data retrieved from NASA's ASRS site as of January 2009 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.

A B737 check airman reports a pilot on day 2 of IOE executed a go around on an unstabilized approach and followed with a firm touchdown. Fatigue a factor.