An air carrier captain rolled out on iah runway 26R following FMS/LNAV commands after ATC issued an ...

Attributes
ACN	826797
Time
Date	200903
Local Time Of Day	1801-2400
Place
Locale Reference	IAH.Airport
State Reference	TX
Environment
Flight Conditions	Mixed
Light	Night
Aircraft 1
Make Model Name	Large Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Route In Use	Visual Approach
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	First Officer Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Multiengine
Person 2
Function	Pilot Flying Captain
Events
Anomaly	Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence

Narrative:

On approach to iah; approach was pushing for visual approach to runway 26L. Captain was flying and entered runway info into the box. It became clear an ILS would be necessary due to low cloud deck east of field. While on a base turn vector; first officer (me) verified ILS frequencies dialed in correct and correct identification and briefed off of chart (heads down) as captain rolled out on final (V bars centered up). Turns out captain had entered runway 26R in FMS and 26L in 'navigation.' our raw data localizer is only about 1/8 inch big on primary flight display and I did not catch it being full deflection as everything else was correct and I had been heads down. Controller caught error on radar; we verified; broke out and were cleared visual to runway 26R. Main factor was fatigue -- end of 12-hour day; 4 legs; and 8 hours flying. Assisting in error was controller pushing for visual to last second; it was dark; and I was too tired to do all my duties (pilot not flying) and verify pilot flying duties.

Original NASA ASRS Text

Title: An air carrier Captain rolled out on IAH Runway 26R following FMS/LNAV commands after ATC issued an ILS 26L clearance which was tuned; identified and available for a LOC/ILS approach. Fatigue was an issue.

Narrative: On approach to IAH; approach was pushing for visual approach to Runway 26L. Captain was flying and entered runway info into the box. It became clear an ILS would be necessary due to low cloud deck east of field. While on a base turn vector; First Officer (me) verified ILS frequencies dialed in correct and correct ID and briefed off of chart (heads down) as Captain rolled out on final (V bars centered up). Turns out Captain had entered Runway 26R in FMS and 26L in 'Navigation.' Our raw data LOC is only about 1/8 inch big on Primary Flight Display and I did not catch it being full deflection as everything else was correct and I had been heads down. Controller caught error on radar; we verified; broke out and were cleared visual to Runway 26R. Main factor was fatigue -- end of 12-hour day; 4 legs; and 8 hours flying. Assisting in error was Controller pushing for visual to last second; it was dark; and I was too tired to do all my duties (pilot not flying) and verify pilot flying duties.

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

An air carrier captain rolled out on iah runway 26R following FMS/LNAV commands after ATC issued an ILS 26L clearance which was tuned; identified and available for a localizer/ILS approach. Fatigue was an issue.