MD80 FLT CREW CONCERNED WITH ALLOWABLE XWIND AT ZZZ.

Narrative

ANY ALL-NIGHTER; PARTICULARLY AN ALL-NIGHTER TURN IS PRONE TO FATIGUE AND SAFETY ISSUES. IT IS NOT NATURAL TO STAY UP ALL NIGHT AND THIS PARTICULAR PAIRING HAD US LNDG AT A CIRCADIAN LOW. THIS COMBINED WITH THE MAJOR WINDSTORM THAT HIT THE PUGET SOUND MADE THIS EVENT EVEN MORE DIFFICULT. SOME OTHER FACTS THAT CAUSED SOME TROUBLE FOR US WAS THE ARPT WIND METER HAD BROKEN EARLIER IN THE NIGHT. THE ARPT WAS ESTIMATING WINDS THAT WERE AT OR OVER OUR MAX XWIND LIMIT (60 KTS XWIND ACCORDING TO THE GPS WIND READOUT ON THE FIRST APCH). WE WERE NOT SURE ABOUT THE LEGALITY OF THESE RPTED WINDS. WE ATTEMPTED TO CONTACT DISPATCH; BUT THE INBOUND RADIO FREQ WAS INOP. OPS WAS OFFLINE TOO DUE TO A PWR OUTAGE. WE ULTIMATELY DID CONTACT DISPATCH (AFTER THE FIRST APCH) AND THEY WERE NO HELP. THE ONLY GUIDANCE WAS TO DO ANOTHER APCH AND THEN DIVERT TO GEG. WE WERE TIRED; BUMPING AROUND AND IN NEED SOME INFO ON THE LEGALITY OF THE ESTIMATED WIND RPT. WE WERE ON OUR OWN AT XA30. ON OUR SECOND APCH (WINDS WERE DOWN TO A STEADY STATE AND PROVIDED 'ONLY' A XWIND COMPONENT OF 25 KTS); WE WERE SUCCESSFUL AND WERE EXTREMELY RELIANT UPON THE GPS WIND PAGE FOR OUR WIND DATA. WE WERE IN A NON-EFIS ACFT. I WOULD LIKE TO SEE SOME GUIDANCE FROM THE COMPANY; FAA AND ATC ON 'ESTIMATED WINDS' AND THE LEGALITY OF USING THIS DATA. DISPATCH COULD HAVE AND SHOULD HAVE ADVISED OF THE SIGNIFICANCE OF THE WIND EVENT; THE PWR OUTAGE AND FREQ FAILURES. WE WOULD HAVE HAD A BETTER PLAN GOING INTO THIS EVENT.