 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-800 captain reported communication issue with company personnel in regard to scheduling and flight release.
| Attributes | |
| ACN | 1620803 |
| Time | |
| Date | 201902 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Taxi |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
After push back I received an ACARS message displaying the name of a different captain. I stopped the push and contacted the dispatcher to find out what was going on. The dispatcher responded right away and advised not to move until this condition was corrected. I responded immediately confirming with him that I would not move until this issue was resolved. A few minutes later I received the new corrected flight release and we were able to continue.upon arrival in ZZZ I had a voicemail from crew tracking to contact them if I had received this message. My phone was off and in my bag as directed by the fom and I never received this message until my arrival in ZZZ.I think for future events it is imperative for crew tracking to make positive contact with a crew in the event of a change to their published sequence. I don't know what the answer is; but we all have to be on the same page to conduct a safe and efficient operation.
Original NASA ASRS Text
Title: B737-800 Captain reported communication issue with company personnel in regard to scheduling and flight release.
Narrative: After push back I received an ACARS message displaying the name of a different Captain. I stopped the push and contacted the Dispatcher to find out what was going on. The Dispatcher responded right away and advised not to move until this condition was corrected. I responded immediately confirming with him that I would not move until this issue was resolved. A few minutes later I received the new corrected flight release and we were able to continue.Upon arrival in ZZZ I had a voicemail from Crew Tracking to contact them if I had received this message. My phone was off and in my bag as directed by the FOM and I never received this message until my arrival in ZZZ.I think for future events it is imperative for Crew Tracking to make positive contact with a crew in the event of a change to their published sequence. I don't know what the answer is; but we all have to be on the same page to conduct a safe and efficient operation.
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.