 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Radio communication problem reported by air carrier captain. Loss of communication frequency. Unable to establish radio contact for a period of time.
| Attributes | |
| ACN | 305982 |
| Time | |
| Date | 199505 |
| Day | Sun |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : etx |
| State Reference | PA |
| Altitude | msl bound lower : 11000 msl bound upper : 11000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zny tracon : phl |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : flight engineer pilot : atp pilot : cfi |
| Experience | flight time last 90 days : 150 flight time total : 19000 flight time type : 2500 |
| ASRS Report | 305982 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : atp |
| Events | |
| Anomaly | aircraft equipment problem : less severe non adherence : clearance other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | other other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Aircraft |
| Air Traffic Incident | Pilot Deviation |
Narrative:
En route to philadelphia, PA, after crossing the east texas VOR, we experienced what appears to have been communications failure. We were working on the problem and at the same time received an ACARS message to contact approach control from our dispatcher. Re-establishing contact with center he immediately turned us over to approach control. (This was just prior to mazie intersection, our final en route fix.) there was no traffic conflict and lost communications procedures were followed. After landing maintenance changed the #1 radio as a precautionary measure. No damage appears this time other than anxiety on the part of the controllers and ourselves this time. A recommendation could be that some type of warning device that would alert you of communication failure could have precluded this situation. After all, there seems to be flags, lights and warning devices for almost any other failure -- why not immediate recognition of communication failure?
Original NASA ASRS Text
Title: RADIO COM PROB RPTED BY ACR CAPT. LOSS OF COM FREQ. UNABLE TO ESTABLISH RADIO CONTACT FOR A PERIOD OF TIME.
Narrative: ENRTE TO PHILADELPHIA, PA, AFTER XING THE EAST TEXAS VOR, WE EXPERIENCED WHAT APPEARS TO HAVE BEEN COMS FAILURE. WE WERE WORKING ON THE PROB AND AT THE SAME TIME RECEIVED AN ACARS MESSAGE TO CONTACT APCH CTL FROM OUR DISPATCHER. RE-ESTABLISHING CONTACT WITH CTR HE IMMEDIATELY TURNED US OVER TO APCH CTL. (THIS WAS JUST PRIOR TO MAZIE INTXN, OUR FINAL ENRTE FIX.) THERE WAS NO TFC CONFLICT AND LOST COMS PROCS WERE FOLLOWED. AFTER LNDG MAINT CHANGED THE #1 RADIO AS A PRECAUTIONARY MEASURE. NO DAMAGE APPEARS THIS TIME OTHER THAN ANXIETY ON THE PART OF THE CTLRS AND OURSELVES THIS TIME. A RECOMMENDATION COULD BE THAT SOME TYPE OF WARNING DEVICE THAT WOULD ALERT YOU OF COM FAILURE COULD HAVE PRECLUDED THIS SIT. AFTER ALL, THERE SEEMS TO BE FLAGS, LIGHTS AND WARNING DEVICES FOR ALMOST ANY OTHER FAILURE -- WHY NOT IMMEDIATE RECOGNITION OF COM FAILURE?
Data retrieved from NASA's ASRS site as of July 2007 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.