 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-800 with an in-flight emergency was unable to communicate with dispatch on the prescribed frequency.
| Attributes | |
| ACN | 782438 |
| Time | |
| Date | 200804 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : zzz.airport |
| State Reference | US |
| Aircraft 1 | |
| Controlling Facilities | artcc : zzz.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | other personnel |
| Qualification | other |
| ASRS Report | 782438 |
| Events | |
| Anomaly | aircraft equipment problem : critical other anomaly ground encounters other |
| Resolutory Action | none taken : unable |
| Supplementary | |
| Problem Areas | Aircraft Company |
| Primary Problem | Company |
Narrative:
I noticed on computer that flight abc was returning to ZZZ. I called center to find out if my computer was correct and they informed me that the flight had an APU fire warning and was returning to ZZZ. The chief dispatcher called maintenance control to see if they had heard anything and was told that line maintenance had called maintenance control with the information. About 10 mins later the flight call me on the outbound company radio frequency to see if I knew what they were doing. They had tried initially to call on the inbound frequency (the correct frequency in this case) but was unable to get dispatch or maintenance control; so they relayed their information to line maintenance. The inbound frequency has not been working for about a week or more. There have been trouble tickets opened; but so far no fix. This needs to be fixed as soon as possible because both line maintenance; and to a lesser degree maintenance control does not know our far responsibility to the airborne flts and neither passed on this information. This was a safety of flight issue and because of this radio problem we were out of the loop.
Original NASA ASRS Text
Title: B737-800 WITH AN IN-FLIGHT EMER WAS UNABLE TO COMMUNICATE WITH DISPATCH ON THE PRESCRIBED FREQ.
Narrative: I NOTICED ON COMPUTER THAT FLT ABC WAS RETURNING TO ZZZ. I CALLED CTR TO FIND OUT IF MY COMPUTER WAS CORRECT AND THEY INFORMED ME THAT THE FLT HAD AN APU FIRE WARNING AND WAS RETURNING TO ZZZ. THE CHIEF DISPATCHER CALLED MAINT CTL TO SEE IF THEY HAD HEARD ANYTHING AND WAS TOLD THAT LINE MAINT HAD CALLED MAINT CTL WITH THE INFO. ABOUT 10 MINS LATER THE FLT CALL ME ON THE OUTBOUND COMPANY RADIO FREQ TO SEE IF I KNEW WHAT THEY WERE DOING. THEY HAD TRIED INITIALLY TO CALL ON THE INBOUND FREQ (THE CORRECT FREQ IN THIS CASE) BUT WAS UNABLE TO GET DISPATCH OR MAINT CTL; SO THEY RELAYED THEIR INFO TO LINE MAINT. THE INBOUND FREQ HAS NOT BEEN WORKING FOR ABOUT A WK OR MORE. THERE HAVE BEEN TROUBLE TICKETS OPENED; BUT SO FAR NO FIX. THIS NEEDS TO BE FIXED ASAP BECAUSE BOTH LINE MAINT; AND TO A LESSER DEGREE MAINT CTL DOES NOT KNOW OUR FAR RESPONSIBILITY TO THE AIRBORNE FLTS AND NEITHER PASSED ON THIS INFO. THIS WAS A SAFETY OF FLT ISSUE AND BECAUSE OF THIS RADIO PROB WE WERE OUT OF THE LOOP.
Data retrieved from NASA's ASRS site as of May 2009 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.