Narrative:

We were on aircraft X to ZZZ. As we were on approach to runway xx; while extending our flaps to 10; we received a #1 leading edge transit light. We performed a go-around and asked for delay vectors to run the QRH (quick reference handbook). We performed all checklists and got our performance data needed to land on runway xx. We landed xx with no other issues and had fire trucks meet us just in case of hot brakes. After taxiing off the runway; we requested brake-cooling data [from the performance data system]. We received an error message telling us to input correct runway. We tried every combination possible and double-checked everything. We never got the brake-cooling data. Fire truck personnel took heat readings of the brakes and said they were 300 degrees and everything looked normal. We asked our dispatcher to see if he could run the brake-cooling numbers for us. He came up with the same error message. We also had a jumpseater who tried to work the brake-cooling data with his ipad app; and he came up with same error message.the captain talked with dispatch again and gave him all the landing data and the brake temperature reading from the fire department; to have him talk with maintenance control to see if we were good to taxi to the gate. We all agreed (maintenance control; dispatch; and us) that we were good to taxi to the gate. It was 25 minutes from landing to the time we got to the gate. Maintenance was standing by to check brake temps and said they were 250 degrees at the gate. Biggest question for us is why none of us could pull up brake-cooling data with all the different resources we were trying to use for our flight.

Google
 

Original NASA ASRS Text

Title: B737 First Officer reported a Flap/Slat issue resulted in a fast landing and hot brakes; but then unable to access the brake-cooling data.

Narrative: We were on Aircraft X to ZZZ. As we were on approach to Runway XX; while extending our flaps to 10; we received a #1 Leading Edge transit light. We performed a go-around and asked for delay vectors to run the QRH (Quick Reference Handbook). We performed all checklists and got our performance data needed to land on Runway XX. We landed XX with no other issues and had fire trucks meet us just in case of hot brakes. After taxiing off the runway; we requested brake-cooling data [from the performance data system]. We received an error message telling us to input correct runway. We tried every combination possible and double-checked everything. We never got the brake-cooling data. Fire truck personnel took heat readings of the brakes and said they were 300 degrees and everything looked normal. We asked our Dispatcher to see if he could run the brake-cooling numbers for us. He came up with the same error message. We also had a Jumpseater who tried to work the brake-cooling data with his iPad app; and he came up with same error message.The Captain talked with Dispatch again and gave him all the landing data and the brake temperature reading from the Fire Department; to have him talk with Maintenance Control to see if we were good to taxi to the gate. We all agreed (Maintenance Control; Dispatch; and us) that we were good to taxi to the gate. It was 25 minutes from landing to the time we got to the gate. Maintenance was standing by to check brake temps and said they were 250 degrees at the gate. Biggest question for us is why none of us could pull up brake-cooling data with all the different resources we were trying to use for our flight.

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.