 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Dispatcher's normal NOTAM source gave no, or inaccurate, information. Checking all available sources he was able to safely dispatch his flts to a foreign destination.
| Attributes | |
| ACN | 469750 |
| Time | |
| Date | 200004 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : sbgl.airport |
| State Reference | FO |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | Large Transport |
| Operating Under FAR Part | Part 121 |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | other personnel oversight : coordinator |
| Qualification | other |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | other personnel other oversight : coordinator |
| Qualification | other other : local ops |
| Events | |
| Anomaly | non adherence : published procedure other anomaly other |
| Independent Detector | other other : dispatch-1 |
| Resolutory Action | other |
| Supplementary | |
| Problem Areas | Company FAA |
| Primary Problem | Company |
| Situations | |
| Publication | NOTAMS |
Narrative:
While flight planning gig departures and arrs for apr/xa/00, I went through normal procedures of checking all aspects of flight. After pulling all information for gig, I found that one of the responses for the NOTAM request was no NOTAM in the file. This led me to believe that no NOTAMS were active for this day, but in fact after phone call from gig operations stating that a runway was closed I concluded that there might be a problem. I confirmed with gig operations that a runway was closed and also an OM was unusable. The only place we could find other NOTAMS was on the internet and some of them stated unstable ILS approachs. I coordinated with capts and gig operations along with ATC to acquire any other NOTAMS that might affect flight safety and this was quite time consuming. Apparently we have a communications problem with the NOTAMS office and our navigation data facility. This problem must be addressed immediately.
Original NASA ASRS Text
Title: DISPATCHER'S NORMAL NOTAM SOURCE GAVE NO, OR INACCURATE, INFO. CHKING ALL AVAILABLE SOURCES HE WAS ABLE TO SAFELY DISPATCH HIS FLTS TO A FOREIGN DEST.
Narrative: WHILE FLT PLANNING GIG DEPS AND ARRS FOR APR/XA/00, I WENT THROUGH NORMAL PROCS OF CHKING ALL ASPECTS OF FLT. AFTER PULLING ALL INFO FOR GIG, I FOUND THAT ONE OF THE RESPONSES FOR THE NOTAM REQUEST WAS NO NOTAM IN THE FILE. THIS LED ME TO BELIEVE THAT NO NOTAMS WERE ACTIVE FOR THIS DAY, BUT IN FACT AFTER PHONE CALL FROM GIG OPS STATING THAT A RWY WAS CLOSED I CONCLUDED THAT THERE MIGHT BE A PROB. I CONFIRMED WITH GIG OPS THAT A RWY WAS CLOSED AND ALSO AN OM WAS UNUSABLE. THE ONLY PLACE WE COULD FIND OTHER NOTAMS WAS ON THE INTERNET AND SOME OF THEM STATED UNSTABLE ILS APCHS. I COORDINATED WITH CAPTS AND GIG OPS ALONG WITH ATC TO ACQUIRE ANY OTHER NOTAMS THAT MIGHT AFFECT FLT SAFETY AND THIS WAS QUITE TIME CONSUMING. APPARENTLY WE HAVE A COMS PROB WITH THE NOTAMS OFFICE AND OUR NAV DATA FACILITY. THIS PROB MUST BE ADDRESSED IMMEDIATELY.
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.