Narrative:

While the flight was holding due to thunderstorms at ZZZ; the dispatcher began to evaluate closer alternates. The dispatcher checked sps notams in sabre and noted the tower was notamed closed but there was no runway closure notams in sabre. Upon further evaluation and checking notams on the FAA website; the dispatcher saw that there in fact was a NOTAM in effect for runway 15R/33L closed that was not in sabre. The runway was closed with work in progress. The NOTAM was sent to the NOTAM management system but was never published into sabre. Flight planning published the NOTAM after becoming aware of the discrepancy. This could have been a dangerous situation if the flight attempted to land on this closed runway with possible work equipment on the runway; tower closed and at night time.

Google
 

Original NASA ASRS Text

Title: An air carrier Dispatcher reported that important NOTAM information regarding a runway closer was not published in the company's flight planning software.

Narrative: While the flight was holding due to thunderstorms at ZZZ; the Dispatcher began to evaluate closer alternates. The Dispatcher checked SPS NOTAMs in SABRE and noted the Tower was NOTAMed closed but there was no runway closure NOTAMs in SABRE. Upon further evaluation and checking NOTAMs on the FAA website; the Dispatcher saw that there in fact was a NOTAM in effect for runway 15R/33L CLOSED that was not in SABRE. The runway was closed with work in progress. The NOTAM was sent to the NOTAM Management System but was never published into SABRE. Flight Planning published the NOTAM after becoming aware of the discrepancy. This could have been a dangerous situation if the flight attempted to land on this closed runway with possible work equipment on the runway; tower closed and at night time.

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.