Date: 201308
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: PMC; Performance/Thrust Management Computer
Component problem: Design; Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Time Pressure; Workload; Communication Breakdown
Second reporter function: First Officer; Pilot Not Flying
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: Other After the fact
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure; Airport
Primary problem: Airport

Narrative: Our destination airport was closed due to painting activities of the runways. [The shorter of the two] runway[s]; 18/36; was due to open [first]. Upon our arrival; Dispatch gave us a diversion plan [including an] alternate airport. According to our calculations; we had only 10 minutes worth of fuel to hold. During our descent; we had already briefed a visual arrival into Runway 18. We were then given a hold but only had to make one turn in the hold when they gave us vectors for the airport. At this time; our main concern was the fuel situation since we now were getting close to our divert fuel limit. As we were being vectored to the airport; ATC told us to expect Runway 36. During this very dynamic time we asked our Company Captain jumpseater to help us out and run the landing data for Runway 36. He ran the data; handed it to us and we verified that the landing data was met. We had plenty of landing distance. We were vectored for the visual approach and landed without any problems. During a conversation with our Dispatcher on our next flight it was brought to my attention that landing on Runway 36 was only authorized in an emergency. We now realized that we had missed reading the note on the airport information page and the note on the runway selection page on the performance data computer which clearly indicates that Runway 36 was to be used only in an emergency.First of all; we should have reviewed the 10-7 page again after given a new runway assignment and also we should have completed the OPC calculations by ourselves. However; I also think that during this dynamic time; we utilized our resources by allowing the company pilot to run the landing data and; unfortunately; he missed the runway note next to the Runway 36 selection before proceeding to the runway landing data page.


Second narrative: [It would help if the note on the airport info page was] more visible. It is currently in CAPS; but a different color; like red would make it stand out. Additionally; [when Runway 36 is selected is selected on the landing data computer] as the landing runway; have a pop-up box display that makes you acknowledge that this is an emergency use only runway similar to the boxes at other airports that pop up and won't let you proceed until you acknowledge the warning. Our training should emphasize to crews that if you receive a change to the landing approach or runway to be sure and review the airport information page for possible restrictions.


Synopsis: When they learned the primary runway at their destination was not available due to painting in progress; the flight crew of a B737 accepted an approach and landing to another runway and only later became aware the runway was restricted to emergency use only.