37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1749640 |
Time | |
Date | 202007 |
Aircraft 1 | |
Make Model Name | B777-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Component | |
Aircraft Component | AC Generator/Alternator |
Person 1 | |
Function | Dispatcher |
Qualification | Dispatch Dispatcher |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
Received call from [maintenance] stating that they had received a satcom call from aircraft X regarding their left idg (integrated drive generator) not working. Crew spoke to [maintenance] directly; I was not involved in the conversation; though I should have been. This flight was still in an ETOPS area of operation; and idg problems have an ETOPS impact and if the crew was required to start the APU; would have a fuel impact. Because [the crew] spoke to [maintenance] without dispatch on the line; no position report was obtained; either. After the fact; [I] figured out that a satcom call which came in earlier at another desk was the airborne aircraft X. However; at that time; there was another flight of a different flight date on the ground and it was thought that was the flight calling; not the one in the air. In any case; the airborne aircraft X crew apparently was offered to be transferred to their dispatcher (which would have been me) but insisted on being transferred directly to [maintenance] instead. I didn't realize what had transpired until after [maintenance] contacted me.not sure what happened or why crew did not involve dispatch in their communication with maintenance. Fortunately; there was no operational impact and flight continued uneventfully to ZZZ. Remind crews that when they have an issue enroute; unless an immediate emergency or something else that doesn't permit; they need to keep their dispatcher in the loop and involved in order to ensure proper operational control is maintained.
Original NASA ASRS Text
Title: Dispatcher reported flight crew neglected to notify Dispatcher of an engine component failure during flight. Flight crew contacted Maintenance directly.
Narrative: Received call from [Maintenance] stating that they had received a SATCOM call from Aircraft X regarding their left IDG (Integrated Drive Generator) not working. Crew spoke to [Maintenance] directly; I was not involved in the conversation; though I should have been. This flight was still in an ETOPS area of operation; and IDG problems have an ETOPS impact and if the crew was required to start the APU; would have a fuel impact. Because [the crew] spoke to [Maintenance] without Dispatch on the line; no position report was obtained; either. After the fact; [I] figured out that a SATCOM call which came in earlier at another desk was the airborne Aircraft X. However; at that time; there was another flight of a different flight date on the ground and it was thought that was the flight calling; not the one in the air. In any case; the airborne Aircraft X crew apparently was offered to be transferred to their Dispatcher (which would have been me) but insisted on being transferred directly to [Maintenance] instead. I didn't realize what had transpired until after [Maintenance] contacted me.Not sure what happened or why crew did not involve dispatch in their communication with Maintenance. Fortunately; there was no operational impact and flight continued uneventfully to ZZZ. Remind crews that when they have an issue enroute; unless an immediate emergency or something else that doesn't permit; they need to keep their dispatcher in the loop and involved in order to ensure proper operational control is maintained.
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.