 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B767-300 pilot reports on his company's inadequate flight planning computer system, that is unable to recognize what airway various vortacs are on.
| Attributes | |
| ACN | 580868 |
| Time | |
| Date | 200305 |
| Day | Mon |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : lax.airport |
| State Reference | CA |
| Altitude | agl single value : 0 |
| Environment | |
| Light | Dusk |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | B767-300 and 300 ER |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : holding ground : taxi |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| ASRS Report | 580868 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | other personnel |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | Company |
| Primary Problem | Company |
Narrative:
This report is an example of an overall problem with the flight planning system used by company. With this flight ready for departure and already in the cue for takeoff, ATC issued a revised route. Our flight planning system will not accept many rtes as cleared by ATC. There are numerous fixes that our system does not recognize as being attached to airways even though every other flight planning system including the FAA and commercial chart company do. As an example, our system does not recognize that jot is on J60, or lvz is on J70. This list goes on and on. This creates an inordinate workload for the dispatcher as he or she tries to guess what and where the problem lies. In addition, it has delayed flts that are #1 for departure as we fumble through this antiquated system trying to get a flight plan to a waiting flight.
Original NASA ASRS Text
Title: B767-300 PLT RPTS ON HIS COMPANY'S INADEQUATE FLT PLANNING COMPUTER SYS, THAT IS UNABLE TO RECOGNIZE WHAT AIRWAY VARIOUS VORTACS ARE ON.
Narrative: THIS RPT IS AN EXAMPLE OF AN OVERALL PROB WITH THE FLT PLANNING SYS USED BY COMPANY. WITH THIS FLT READY FOR DEP AND ALREADY IN THE CUE FOR TKOF, ATC ISSUED A REVISED RTE. OUR FLT PLANNING SYS WILL NOT ACCEPT MANY RTES AS CLRED BY ATC. THERE ARE NUMEROUS FIXES THAT OUR SYS DOES NOT RECOGNIZE AS BEING ATTACHED TO AIRWAYS EVEN THOUGH EVERY OTHER FLT PLANNING SYS INCLUDING THE FAA AND COMMERCIAL CHART COMPANY DO. AS AN EXAMPLE, OUR SYS DOES NOT RECOGNIZE THAT JOT IS ON J60, OR LVZ IS ON J70. THIS LIST GOES ON AND ON. THIS CREATES AN INORDINATE WORKLOAD FOR THE DISPATCHER AS HE OR SHE TRIES TO GUESS WHAT AND WHERE THE PROB LIES. IN ADDITION, IT HAS DELAYED FLTS THAT ARE #1 FOR DEP AS WE FUMBLE THROUGH THIS ANTIQUATED SYS TRYING TO GET A FLT PLAN TO A WAITING FLT.
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.