Narrative:

Alternate requirements. Upon arrival into mci area, the WX required that we shoot a CAT I ILS to runway 19R. I used the hgs and landed uneventfully. After landing and shutting down the engines at the gate, we discussed the fact that the fog had come up very rapidly and as far as we knew unforecast. We decided to call dispatch to tell them about the fog so they could let the other aircraft coming into mci know and plan for it. Prior to calling, I reviewed my WX packet from our flight and then noticed that on the last line of the forecast there was indeed a forecast 'tempo' for 1100 ft broken. We should have had an alternate. I missed it, totally my fault! The release was created several hours prior to our event. I did not call dispatch prior to departure because we had just come over from mci, where the WX was 15000 ft broken and over 10 mi visibility. I assumed that the WX was still fine. In the back of my mind was also the fact that when we just had flown over to stl from mci earlier, mci was our alternate for that leg because it was great WX. These 2 items contributed to my failure to notice the 'tempo' remark. This again is my fault! The WX package and release also contributed to the event in my opinion. The release was created several hours in advance by a different dispatcher. I know this is a common practice and understand why. I also am not blaming the dispatcher -- this was totally my error. The WX package also contributed. If you notice the forecast was listed as 'tempo' XA15 then stopped, a new line started 11 broken, then another new line. I am just guessing, but think in hindsight that this contributed to my missing the 11 broken remark. What did I learn? I make it a habit to put a check mark by each item I review. I did it in this case as well, but still goofed, why? I need to slow down and be sure that not only do I review each item but also read each item. Again, I accept full responsibility for this error, no one else was at fault. Supplemental information from acn 568053: upon arrival in the mci terminal area, we received the ATIS and determined we were required to accomplish a CAT I ILS approach. The captain used the hgs. We landed uneventfully. Once the aircraft was secured at the gate, we reviewed the WX package from our flight and it was noted that an alternate was required, however, not listed. We missed the 'tempo' remark on the second line of the forecast. A factor that contributed to this was that the dispatch report (release) was printed and completed in the system at XA28 and our flight was scheduled to depart stl at XE00. The event taught us that we must review the WX more carefully and review the dispatch release.

Google
 

Original NASA ASRS Text

Title: B737-300 CREW MISSED THE WX RPT LINE THAT REQUIRED AN ALTERNATE ARPT BE LISTED ON THE DISPATCH RELEASE.

Narrative: ALTERNATE REQUIREMENTS. UPON ARR INTO MCI AREA, THE WX REQUIRED THAT WE SHOOT A CAT I ILS TO RWY 19R. I USED THE HGS AND LANDED UNEVENTFULLY. AFTER LNDG AND SHUTTING DOWN THE ENGS AT THE GATE, WE DISCUSSED THE FACT THAT THE FOG HAD COME UP VERY RAPIDLY AND AS FAR AS WE KNEW UNFORECAST. WE DECIDED TO CALL DISPATCH TO TELL THEM ABOUT THE FOG SO THEY COULD LET THE OTHER ACFT COMING INTO MCI KNOW AND PLAN FOR IT. PRIOR TO CALLING, I REVIEWED MY WX PACKET FROM OUR FLT AND THEN NOTICED THAT ON THE LAST LINE OF THE FORECAST THERE WAS INDEED A FORECAST 'TEMPO' FOR 1100 FT BROKEN. WE SHOULD HAVE HAD AN ALTERNATE. I MISSED IT, TOTALLY MY FAULT! THE RELEASE WAS CREATED SEVERAL HRS PRIOR TO OUR EVENT. I DID NOT CALL DISPATCH PRIOR TO DEP BECAUSE WE HAD JUST COME OVER FROM MCI, WHERE THE WX WAS 15000 FT BROKEN AND OVER 10 MI VISIBILITY. I ASSUMED THAT THE WX WAS STILL FINE. IN THE BACK OF MY MIND WAS ALSO THE FACT THAT WHEN WE JUST HAD FLOWN OVER TO STL FROM MCI EARLIER, MCI WAS OUR ALTERNATE FOR THAT LEG BECAUSE IT WAS GREAT WX. THESE 2 ITEMS CONTRIBUTED TO MY FAILURE TO NOTICE THE 'TEMPO' REMARK. THIS AGAIN IS MY FAULT! THE WX PACKAGE AND RELEASE ALSO CONTRIBUTED TO THE EVENT IN MY OPINION. THE RELEASE WAS CREATED SEVERAL HRS IN ADVANCE BY A DIFFERENT DISPATCHER. I KNOW THIS IS A COMMON PRACTICE AND UNDERSTAND WHY. I ALSO AM NOT BLAMING THE DISPATCHER -- THIS WAS TOTALLY MY ERROR. THE WX PACKAGE ALSO CONTRIBUTED. IF YOU NOTICE THE FORECAST WAS LISTED AS 'TEMPO' XA15 THEN STOPPED, A NEW LINE STARTED 11 BROKEN, THEN ANOTHER NEW LINE. I AM JUST GUESSING, BUT THINK IN HINDSIGHT THAT THIS CONTRIBUTED TO MY MISSING THE 11 BROKEN REMARK. WHAT DID I LEARN? I MAKE IT A HABIT TO PUT A CHK MARK BY EACH ITEM I REVIEW. I DID IT IN THIS CASE AS WELL, BUT STILL GOOFED, WHY? I NEED TO SLOW DOWN AND BE SURE THAT NOT ONLY DO I REVIEW EACH ITEM BUT ALSO READ EACH ITEM. AGAIN, I ACCEPT FULL RESPONSIBILITY FOR THIS ERROR, NO ONE ELSE WAS AT FAULT. SUPPLEMENTAL INFO FROM ACN 568053: UPON ARR IN THE MCI TERMINAL AREA, WE RECEIVED THE ATIS AND DETERMINED WE WERE REQUIRED TO ACCOMPLISH A CAT I ILS APCH. THE CAPT USED THE HGS. WE LANDED UNEVENTFULLY. ONCE THE ACFT WAS SECURED AT THE GATE, WE REVIEWED THE WX PACKAGE FROM OUR FLT AND IT WAS NOTED THAT AN ALTERNATE WAS REQUIRED, HOWEVER, NOT LISTED. WE MISSED THE 'TEMPO' REMARK ON THE SECOND LINE OF THE FORECAST. A FACTOR THAT CONTRIBUTED TO THIS WAS THAT THE DISPATCH RPT (RELEASE) WAS PRINTED AND COMPLETED IN THE SYS AT XA28 AND OUR FLT WAS SCHEDULED TO DEPART STL AT XE00. THE EVENT TAUGHT US THAT WE MUST REVIEW THE WX MORE CAREFULLY AND REVIEW THE DISPATCH RELEASE.

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.