 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Mem departure controller described multiple events when departure aircraft established contact on the wrong departure frequency.
| Attributes | |
| ACN | 780777 |
| Time | |
| Date | 200804 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : mem.airport |
| State Reference | TN |
| Environment | |
| Light | Daylight |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : departure |
| Qualification | controller : radar |
| Experience | controller non radar : 6.5 controller radar : 12.5 controller time certified in position1 : 5.7 |
| ASRS Report | 780777 |
| Events | |
| Anomaly | non adherence : published procedure |
| Independent Detector | other controllera |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | ATC Human Performance Chart Or Publication Flight Crew Human Performance |
| Primary Problem | Ambiguous |
Narrative:
I was working west departure. At about XA38; I observed a data tag for air carrier X (a DC95) appear on my scope. I heard the departure east controller instruct the pilot to contact me on my frequency. The routing for air carrier X was such that the proper departure frequency was the west departure frequency. At about XA57; I observed a data tag for aircraft Y (an F2TH) appear on my scope. Again; I heard the east departure controller instruct the pilot of aircraft Y to contact me on departure west frequency. Not only was the west departure frequency the proper frequency for aircraft Y's route of flight; but; in accordance with a change in procedures that our facility was issued approximately 1 month ago because of an incident in which an aircraft that was flying similar routing to aircraft Y had nearly hit another aircraft because of an improper frequency; this aircraft should have been instructed by the local controller to contact the departure west frequency prior to leaving the local controller's frequency.
Original NASA ASRS Text
Title: MEM DEP CTLR DESCRIBED MULTIPLE EVENTS WHEN DEP ACFT ESTABLISHED CONTACT ON THE WRONG DEP FREQ.
Narrative: I WAS WORKING W DEP. AT ABOUT XA38; I OBSERVED A DATA TAG FOR ACR X (A DC95) APPEAR ON MY SCOPE. I HEARD THE DEP E CTLR INSTRUCT THE PLT TO CONTACT ME ON MY FREQ. THE ROUTING FOR ACR X WAS SUCH THAT THE PROPER DEP FREQ WAS THE W DEP FREQ. AT ABOUT XA57; I OBSERVED A DATA TAG FOR ACFT Y (AN F2TH) APPEAR ON MY SCOPE. AGAIN; I HEARD THE E DEP CTLR INSTRUCT THE PLT OF ACFT Y TO CONTACT ME ON DEP W FREQ. NOT ONLY WAS THE W DEP FREQ THE PROPER FREQ FOR ACFT Y'S RTE OF FLT; BUT; IN ACCORDANCE WITH A CHANGE IN PROCS THAT OUR FACILITY WAS ISSUED APPROX 1 MONTH AGO BECAUSE OF AN INCIDENT IN WHICH AN ACFT THAT WAS FLYING SIMILAR ROUTING TO ACFT Y HAD NEARLY HIT ANOTHER ACFT BECAUSE OF AN IMPROPER FREQ; THIS ACFT SHOULD HAVE BEEN INSTRUCTED BY THE LCL CTLR TO CONTACT THE DEP W FREQ PRIOR TO LEAVING THE LCL CTLR'S FREQ.
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.