Narrative:

Our clearance was the reno 4 as filed-llc. While we were setting up our cockpit; we asked the ground controller which runway we could expect for departure. The reply was runway 16R. We briefed the commercial chart page for runway 16R and set the radios accordingly. Since I was flying this leg; I had the irno localizer tuned on my side for the required DME and the first officer had fmg tuned on her side for the required cross radials. The rno 4 departure page has in the initial climb grid; that departures on runway 16R should expect heading assigned by ATC. So I had my navigation set for the departure course. When we were cleared for takeoff runway 16R the tower did not specify a heading; so we asked and were then told to fly the irno localizer. I had the localizer already tuned; so we proceeded with the takeoff. At about 700 ft; I lost all navigation and my flight director momentarily. When it came back on; it showed a slight deviation left of course. I made a small correction; and then the controller said that he showed us drifting left of course. I added a little more correction; and at this point the controller said that we were getting close to higher terrain and gave us a left turn and subsequent vectors on course. We reported the navigation malfunction to departure control. After we passed through the transition altitude; we reviewed what had just happened. It became apparent that since I did not anticipate the irno localizer and did not have the 164 degree heading in the obs window that I was receiving false navigation information. Thankfully; departure control was watching and corrected my mistake. We did not receive any GPWS or terrain warnings. The area of confusion is in the clearance for the rno 4 and then changing the runway 16R initial climb without telling the crew beforehand. The irno localizer is specifically for departure on runway 16L.

Related reports:

Google
 

Original NASA ASRS Text

Title: Flight crew of heavy transport aircraft fail to follow back course of localizer as cleared following takeoff from runway 16R at RNO which wasn't correct either for their departure runway.

Narrative: Our clearance was the Reno 4 as filed-LLC. While we were setting up our cockpit; we asked the Ground Controller which runway we could expect for departure. The reply was Runway 16R. We briefed the commercial chart page for Runway 16R and set the radios accordingly. Since I was flying this leg; I had the IRNO LOC tuned on my side for the required DME and the First Officer had FMG tuned on her side for the required cross radials. The RNO 4 departure page has in the initial climb grid; that departures on Runway 16R should expect heading assigned by ATC. So I had my navigation set for the departure course. When we were cleared for takeoff Runway 16R the Tower did not specify a heading; so we asked and were then told to fly the IRNO LOC. I had the LOC already tuned; so we proceeded with the takeoff. At about 700 ft; I lost all navigation and my Flight Director momentarily. When it came back on; it showed a slight deviation left of course. I made a small correction; and then the Controller said that he showed us drifting left of course. I added a little more correction; and at this point the Controller said that we were getting close to higher terrain and gave us a left turn and subsequent vectors on course. We reported the navigation malfunction to Departure Control. After we passed through the transition altitude; we reviewed what had just happened. It became apparent that since I did not anticipate the IRNO LOC and did not have the 164 degree heading in the OBS window that I was receiving false navigation information. Thankfully; Departure Control was watching and corrected my mistake. We did not receive any GPWS or terrain warnings. The area of confusion is in the clearance for the RNO 4 and then changing the Runway 16R initial climb without telling the crew beforehand. The IRNO LOC is specifically for departure on Runway 16L.

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