Air carrier first officer reported that the performance computer only contained information for runw...

Narrative:

We were descending to hou in VFR conditions and they were landing runway 13R. While entering the landing data I noticed that the available runways were showing 12R and 12L. 13R and 13L were not a listed option. We noticed on the 10-9 that hou had renumbered/changed the 12's to 13's earlier this month. The database was showing current with an expiration of (date). I triple checked and compared the airport and runway information and data with the runway lengths found on the 10-9 and 10-9a. We both agreed that the only issue was a slight re-numbering of the runways and that otherwise there was no threat or hazard. We landed safely without incident. Upon landing; maintenance was contacted and the captain mentioned it to one of the local chief pilots. Later on; in a different aircraft; I looked at the runway data for hou. I noticed that 12 right and 12 left; as well as; 13R and 13L were an option for landing data. With the earlier aircraft in question this data was missing; yet still deemed current. There was an oversight somewhere in the update process.

Original NASA ASRS Text

Title: Air carrier First Officer reported that the performance computer only contained information for Runways 12L/R. The runways had recently been renumbered and the crew elected to use the Runway 12R data.

Narrative: We were descending to HOU in VFR conditions and they were landing Runway 13R. While entering the landing data I noticed that the available runways were showing 12R and 12L. 13R and 13L were not a listed option. We noticed on the 10-9 that HOU had renumbered/changed the 12's to 13's earlier this month. The database WAS showing current with an expiration of (date). I triple checked and compared the airport and runway information and data with the runway lengths found on the 10-9 and 10-9a. We both agreed that the only issue was a slight re-numbering of the runways and that otherwise there was no threat or hazard. We landed safely without incident. Upon landing; Maintenance was contacted and the Captain mentioned it to one of the local Chief Pilots. Later on; in a different aircraft; I looked at the runway data for HOU. I noticed that 12 R and 12 L; AS WELL AS; 13R and 13L were an option for landing data. With the earlier aircraft in question this data was missing; yet still deemed current. There was an oversight somewhere in the update process.

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.

Attributes
ACN	1402903
Time
Date	201611
Local Time Of Day	0601-1200
Place
Locale Reference	I90.TRACON
State Reference	TX
Environment
Light	Daylight
Aircraft 1
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	Descent
Component
Aircraft Component	Electronic Flt Bag (EFB)
Person 1
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 146 Flight Crew Type 720
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy

Air carrier first officer reported that the performance computer only contained information for runways 12L/right. The runways had recently been renumbered and the crew elected to use the runway 12R data.