 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An air carrier dispatcher reported a flight departed with out of date information because of a breakdown in communications.
| Attributes | |
| ACN | 1341899 |
| Time | |
| Date | 201602 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Regional Jet 700 ER/LR (CRJ700) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Dispatcher |
| Qualification | Dispatch Dispatcher |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
As I was building the release for this flight; I was getting an error that the drift-down alternates could not be calculated because of an error. [Name] told me to file it and make sure that the drift-down information was on the release. I filed it; checked the release; and the information was missing. After I corrected this issue; I called [the associated ARTCC] to pull the flight strip; sent the correct [flight plan] and sent an ACARS message to the crew and then called ops to pass the info to the crew to print the new [flight plan]. While the flight was enroute; I got a message from the crew that the route given to them by ATC was not matching what was on the release. I sent him the correct flight summary; the drift-down information and the weather for his escape airport. I then did a pen and ink for the new [flight plan]. The captain said he was not notified by the gate agent and did not receive the ACARS.there was a breakdown of communication. The gate agent did not notify the crew to print the new [flight plan]; and the crew did not receive the ACARS message. Next time I [will] directly call the captain and follow up to ensure that they have the correct [flight plan].
Original NASA ASRS Text
Title: An air carrier dispatcher reported a flight departed with out of date information because of a breakdown in communications.
Narrative: As I was building the release for this flight; I was getting an error that the drift-down alternates could not be calculated because of an error. [Name] told me to file it and make sure that the drift-down information was on the release. I filed it; checked the release; and the information was missing. After I corrected this issue; I called [the associated ARTCC] to pull the flight strip; sent the correct [flight plan] and sent an ACARS message to the crew and then called Ops to pass the info to the crew to print the new [flight plan]. While the flight was enroute; I got a message from the crew that the route given to them by ATC was not matching what was on the release. I sent him the correct flight summary; the drift-down information and the weather for his escape airport. I then did a pen and ink for the new [flight plan]. The Captain said he was not notified by the gate agent and did not receive the ACARS.There was a breakdown of communication. The gate agent did not notify the crew to print the new [flight plan]; and the crew did not receive the ACARS message. Next time I [will] directly call the Captain and follow up to ensure that they have the correct [flight plan].
Data retrieved from NASA's ASRS site 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.