Narrative:

After receiving a load plan and finding we had more freight than planned; we received new fuel burn and data from dispatch. I went to the printed takeoff data sheet and determined that runway 16L was required for departure due to runway limits and max power was required. In addition; rno gound informed us that company had contacted them confirming that runway 16L was available for our departure; further confirming that the printed data was correct. The issue is that 16L is 2;000 feet shorter than 16R and the data required a 16L departure. We departed 16L as per the data with max power. On departure; we received a 500 feet call off of the radar altimeter when passing over a small mountain at the end of the runway. As we reflected on the data; we thought there may be an issue with the data. It seems as if the runway numbers are transposed on the data sheet. (16L was actually for 16R) I spoke with dispatch and discussed with him my concerns. He agreed it did not make sense as printed and there were no known issues as to why it would be that way. He also said that they have had 'issues like this' and have 'people working on it'. It is great they are working on it; but the crews need to be informed of the potential issue. As we move to pure electronic data; these issues could prove fatal. Other rno issues. Runway 7-25 is unusable by our aircraft type; yet we have data for it. Also; note to turn on ap at 200 feet is not fleet specific.

Google
 

Original NASA ASRS Text

Title: A twin engine heavy jet flight crew departed RNO 16L after discussions about the max power takeoff and the aircraft's performance. After takeoff the hill off the end of 16L unexpectedly activated the radio altimeter with an EGPWS alert at 500 feet climbing.

Narrative: After receiving a load plan and finding we had more freight than planned; we received new fuel burn and data from dispatch. I went to the printed takeoff data sheet and determined that runway 16L was required for departure due to runway limits and max power was required. In addition; RNO gound informed us that Company had contacted them confirming that runway 16L was available for our departure; further confirming that the printed data was correct. The issue is that 16L is 2;000 feet shorter than 16R and the data required a 16L departure. We departed 16L as per the data with max power. On departure; we received a 500 feet call off of the radar altimeter when passing over a small mountain at the end of the runway. As we reflected on the data; we thought there may be an issue with the data. It seems as if the runway numbers are transposed on the data sheet. (16L was actually for 16R) I spoke with dispatch and discussed with him my concerns. He agreed it did not make sense as printed and there were no known issues as to why it would be that way. He also said that they have had 'issues like this' and have 'people working on it'. It is great they are working on it; but the crews need to be informed of the potential issue. As we move to pure electronic data; these issues could prove fatal. Other RNO issues. Runway 7-25 is unusable by our aircraft type; yet we have data for it. Also; note to turn on AP at 200 feet is not fleet specific.

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.