 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Dispatcher reports that his dispatch computer does not alert in a timely manner when flight delays will cause two aircraft with the same flight number to be in the same airspace.
| Attributes | |
| ACN | 1089721 |
| Time | |
| Date | 201305 |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Aircraft 2 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Person 1 | |
| Function | Dispatcher |
| Qualification | Dispatch Dispatcher |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
Once again I was alerted to a need for a radio number (callsign) way too late in the process by [the dispatch computer]/dispatch view. Despite the release notes for dispatch view (version 1.1) saying the radio number conflict alert issue was resolved; it clearly was not! My flight [123] pushed on time. Unknown to me there was a late inbound [123] ETA 20 minutes later. I was alerted by the system just four minutes prior. So two [123]'s in the airspace at the same time; both in sterile cockpit. I sent a message to my outbound [123] to make him aware and told him to use extreme caution for next few minutes until the other [123] was on ground and at gate. This needs to be fixed as soon as possible before we have an accident!
Original NASA ASRS Text
Title: Dispatcher reports that his dispatch computer does not alert in a timely manner when flight delays will cause two aircraft with the same flight number to be in the same airspace.
Narrative: Once again I was alerted to a need for a radio number (callsign) way too late in the process by [the Dispatch Computer]/Dispatch View. Despite the release notes for Dispatch View (version 1.1) saying the radio number conflict alert issue was resolved; it clearly was not! My flight [123] pushed on time. Unknown to me there was a late inbound [123] ETA 20 minutes later. I was alerted by the system just four minutes prior. So two [123]'s in the airspace at the same time; both in sterile cockpit. I sent a message to my outbound [123] to make him aware and told him to use extreme caution for next few minutes until the other [123] was on ground and at gate. This needs to be fixed ASAP before we have an accident!
Data retrieved from NASA's ASRS site as of July 2013 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.