B737 flight crew reported that fatigue and distractions resulted in the approach being flown to 500 ...

Attributes
ACN	1392765
Time
Date	201610
Local Time Of Day	1801-2400
Place
Locale Reference	ORF.Airport
State Reference	VA
Environment
Flight Conditions	Mixed
Light	Night
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Flight Plan	IFR
Person 1
Function	Pilot Not Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 241
Person 2
Function	Pilot Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 151 Flight Crew Type 800
Events
Anomaly	Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Unstabilized Approach

Narrative:

I was pm on an ILS into orf runway 5. We broke through a cloud layer and were turned on a vector to intercept final. The PF turned too far and went through final; and he realized he was getting wrong information due to the wrong ILS frequency set. I redialed it in for him. We had started to descend as well and I asked him to level off at 1500 ft until we were straightened out. We had already gotten to gear down flaps 15 at this point. Tower queried us to if we had the field in sight; which we did. We then intercepted glideslope and started down once we got straightened out; and did not do the 1000 ft call due to workload and just plain missed it. Our speeds were 133/148 due to gusty winds and I should have noticed the power settings were off as well. I called 500 ft and verified cleared to land. Shortly after the too low flaps squawk went off and I realized we hadn't done the landing checklist. We were still at flaps 15. I selected flaps 30; armed the speedbrake; and did the landing checklist before the 100 ft call came; and we elected to land uneventfully.the first officer stated; before we took off; he was tired so to please speak up. I was unhelpful to him as pm by not staying on top of things and let our crew down by not heightening my awareness.

Original NASA ASRS Text

Title: B737 flight crew reported that fatigue and distractions resulted in the approach being flown to 500 ft AGL without the Landing Checklist being run.

Narrative: I was PM on an ILS into ORF Runway 5. We broke through a cloud layer and were turned on a vector to intercept final. The PF turned too far and went through final; and he realized he was getting wrong information due to the wrong ILS frequency set. I redialed it in for him. We had started to descend as well and I asked him to level off at 1500 ft until we were straightened out. We had already gotten to gear down flaps 15 at this point. Tower queried us to if we had the field in sight; which we did. We then intercepted glideslope and started down once we got straightened out; and did not do the 1000 ft call due to workload and just plain missed it. Our speeds were 133/148 due to gusty winds and I should have noticed the power settings were off as well. I called 500 ft and verified cleared to land. Shortly after the Too Low Flaps squawk went off and I realized we hadn't done the Landing Checklist. We were still at flaps 15. I selected flaps 30; armed the speedbrake; and did the Landing Checklist before the 100 ft call came; and we elected to land uneventfully.The FO stated; before we took off; he was tired so to please speak up. I was unhelpful to him as PM by not staying on top of things and let our crew down by not heightening my awareness.

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.

B737 flight crew reported that fatigue and distractions resulted in the approach being flown to 500 ft AGL without the landing checklist being run.