 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Dispatcher coming on duty notes that his predecessor has filed a flight plan with the wrong equipment code; due to the aircraft assigned to the flight having an out of date nav data base.
| Attributes | |
| ACN | 853041 |
| Time | |
| Date | 200909 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ORD.Airport |
| State Reference | IL |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Parked |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Dispatcher |
| Qualification | Dispatch Dispatcher |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
I took over this flight from the person who dispatched it originally. He was confused on the suffix equipment code that he was to file with when the FMS database was out of date. I caught the suffix error but the crew caught the route issue. The suffix equipment with the FMS database out of date should be 'sdgw' and the navigation/rnvd1e2a1 taken out as well. The dispatcher had it filed as if nothing was wrong. The route dct stl dct fsm dct windu had VOR's that were too far apart. Stl to fsm was 276NM and from fsm to windu was 271NM. So I refiled and amended the release. More training at recurrent time to make sure everyone knows how to file with the FMS database out of date as well as other equipment missing. Digging deeper into this area for understanding may help some. Also; if you don't know then don't file it until you look it up in the manual. Double checking the route not only for non RNAV issues but distance between VOR's as well.
Original NASA ASRS Text
Title: Dispatcher coming on duty notes that his predecessor has filed a flight plan with the wrong equipment code; due to the aircraft assigned to the flight having an out of date Nav data base.
Narrative: I took over this flight from the person who dispatched it originally. He was confused on the suffix equipment code that he was to file with when the FMS database was out of date. I caught the suffix error but the crew caught the route issue. The suffix equipment with the FMS database out of date should be 'SDGW' and the NAV/RNVD1E2A1 taken out as well. The dispatcher had it filed as if nothing was wrong. The route DCT STL DCT FSM DCT WINDU had VOR's that were too far apart. STL to FSM was 276NM and from FSM to WINDU was 271NM. So I refiled and amended the release. More training at recurrent time to make sure everyone knows how to file with the FMS database out of date as well as other equipment missing. Digging deeper into this area for understanding may help some. Also; if you don't know then don't file it until you look it up in the manual. Double checking the route not only for NON RNAV issues but distance between VOR's as well.
Data retrieved from NASA's ASRS site as of April 2012 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.