Dispatch Dispatcher
Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Manuals; Human Factors; Chart Or Publication
Comparing FDC NOTAMs between our Dispatch Monitor and WSI I found instances where NOTAMs were in our system but no longer valid in WSI. I also found instances where NOTAMs were in WSI that were missing in our system. Here are some examples found today. I had to manually delete the following NOTAMs that were no longer in WSI but still in our software: FDC 4/0889 CMH IAP PORT COLUMBUS INTL COLUMBUS OH. ILS OR LOC RWY 28L AMDT 29... ILS OR LOC RWY 28R AMDT 4... ILS OR LOC RWY 10L AMDT 19... ILS OR LOC RWY 10R AMDT 9A... ALTERNATE MINIMUMS NA APE VORTAC UNMONITORED. 1402210551-1408210551EST FDC 4/1011 MCI IAP KANSAS CITY INTL KANSAS CITY MO. ILS OR LOC RWY 27 AMDT 3... MISSED APPROACH CLIMB TO 1600 THEN CLIMBING RIGHT TURN TO 4000 ON HEADING 330 AND RBA VOR/DME R-137 TO BOWLR INT/RBA 17.62 DME AND HOLD. TOP VORTAC OUT OF SERVICE. 1402211433-1408211433EST FDC 4/1006 MCI IAP KANSAS CITY INTL KANSAS CITY MO. ILS OR LOC RWY 9 AMDT 14... RADAR REQUIRED FOR PROCEDURE ENTRY EXCEPT FOR AIRCRAFT EQUIPPED WITH SUITABLE RNAV SYSTEM WITH GPS TOP VORTAC OUT OF SERVICE. I had to manually add this NOTAM that was in WSI but not in our system: FDC! FDC 4/0535 MCI IAP KANSAS CITY INTL; KANSAS CITY; MO. ILS OR LOC RWY 9; AMDT 14... ALTERNATE MINIMUMS NA; TOP VORTAC UNMONITORED.The automation that adds/deletes NOTAMs in our system does not seem to be working. To provide [relevant coverage] the system could be fixed or at the very least dispatchers could be notified that it is not working and a procedure put in place to make sure that the NOTAMs in our weather packet are complete and valid.
A Dispatcher advised that the commercial service providing flight planning services and/or flight crew tablet generated flight info frequently conflict with one another as to current FDC NOTAMs.