Narrative:

Departed lbb with safety FAA observer on the jumpseat. En route at cruise altitude, FAA inspector asked for dispatch release and WX packet. FAA then advised that dispatch release alternate was okc, but WX packet had hou as alternate with hou WX listed, but no okc WX. I tried to get this taken care of en route, but frequency congestion, short flight and arrival WX did not allow it. FAA advised to file as soon as possible report to find out where communication breakdown was. Contributing factor: captain did not pay close enough attention to paperwork.

Google
 

Original NASA ASRS Text

Title: A B737 FLT CREW IS NOTIFIED BY A JUMPSEATING FAA INSPECTOR THAT THEIR ALTERNATE ON THE DISPATCH RELEASE DOESN'T MATCH THAT OF THE WX PACKET. ALSO, THAT THEY DO NOT HAVE THE WX FOR THE DISPATCH RELEASE ALTERNATE.

Narrative: DEPARTED LBB WITH SAFETY FAA OBSERVER ON THE JUMPSEAT. ENRTE AT CRUISE ALT, FAA INSPECTOR ASKED FOR DISPATCH RELEASE AND WX PACKET. FAA THEN ADVISED THAT DISPATCH RELEASE ALTERNATE WAS OKC, BUT WX PACKET HAD HOU AS ALTERNATE WITH HOU WX LISTED, BUT NO OKC WX. I TRIED TO GET THIS TAKEN CARE OF ENRTE, BUT FREQ CONGESTION, SHORT FLT AND ARR WX DID NOT ALLOW IT. FAA ADVISED TO FILE ASAP RPT TO FIND OUT WHERE COM BREAKDOWN WAS. CONTRIBUTING FACTOR: CAPT DID NOT PAY CLOSE ENOUGH ATTN TO PAPERWORK.

Data retrieved from NASA's ASRS site as of July 2007 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.