Narrative:

The performance data for our flight printed incorrectly in such a way that the take off data for runway 27 appeared in the column for runway 36. I brought this to the attention of the dispatcher who said it did not show that way in sabre. I had the tlh station print new data using a different printer and it still showed the same misinformation. [I] noticed it during preflight because runway 27 single engine departure track appeared to be missing; computer or printer error. Computer error that needs to be investigated; someone could easily use runway 27 performance data on the more restrictive runway 36.

Related reports:

Google
 

Original NASA ASRS Text

Title: Regional jet Captain describes an apparent printer error that showed the take off data for Runway 27 in the column for Runway 36. The data appears correctly in Sabre but a second attempt with a different printer produces the same results.

Narrative: The performance data for our flight printed incorrectly in such a way that the take off data for Runway 27 appeared in the column for Runway 36. I brought this to the attention of the Dispatcher who said it did not show that way in Sabre. I had the TLH station print new data using a different printer and it still showed the same misinformation. [I] noticed it during preflight because Runway 27 single engine departure track appeared to be missing; computer or printer error. Computer error that needs to be investigated; someone could easily use Runway 27 performance data on the more restrictive Runway 36.

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.