37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 373537 |
Time | |
Date | 199707 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : atl |
State Reference | GA |
Altitude | msl bound lower : 35000 msl bound upper : 35000 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : ztl |
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 | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller non radar : 15 controller radar : 15 controller supervisory : 1 |
ASRS Report | 373537 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : unable |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | other |
Narrative:
While working intermediate altitude airspace north of atlanta, I was moderately busy with 7-9 aircraft. Most of the aircraft were either deviating for WX or transitioning to higher/lower altitude. Air carrier WWWW was northbound at FL310 and about to enter the airspace. I heard an aircraft call to check in, but I did not understand the call sign and asked the pilot to say again. Again I asked the pilot to repeat, and I thought I heard air carrier xyz. Since I was not expecting air carrier xyz, I used the computer to search for air carrier xyz without success. After failing to locate the aircraft, I asked the pilot to say again one more time. This time the pilot answered with 'air carrier WWWW' and I acknowledged his transmission. Later I finally realized the pilot had been calling himself 'air carrier FFFF.' he continued to use this call sign throughout my sector and at least the next sector. Of course, I'm well aware that pilots are not required to use standard phraseology (as controllers are) but the confusion, delay, and extra xmissions needed to locate and identify this aircraft were most unwelcome.
Original NASA ASRS Text
Title: ACR PLT USES NON STANDARD PHRASEOLOGY WHEN USING CALL SIGN RESULTING IN THE CTLR ASKING THE PLT 3 TIMES REPEAT ACFT CALL SIGN. THE ACR PLT CONTINUED USING THE CONFUSING CALL SIGN WHILE IN THE CTLR'S AIRSPACE.
Narrative: WHILE WORKING INTERMEDIATE ALT AIRSPACE N OF ATLANTA, I WAS MODERATELY BUSY WITH 7-9 ACFT. MOST OF THE ACFT WERE EITHER DEVIATING FOR WX OR TRANSITIONING TO HIGHER/LOWER ALT. ACR WWWW WAS NBOUND AT FL310 AND ABOUT TO ENTER THE AIRSPACE. I HEARD AN ACFT CALL TO CHK IN, BUT I DID NOT UNDERSTAND THE CALL SIGN AND ASKED THE PLT TO SAY AGAIN. AGAIN I ASKED THE PLT TO REPEAT, AND I THOUGHT I HEARD ACR XYZ. SINCE I WAS NOT EXPECTING ACR XYZ, I USED THE COMPUTER TO SEARCH FOR ACR XYZ WITHOUT SUCCESS. AFTER FAILING TO LOCATE THE ACFT, I ASKED THE PLT TO SAY AGAIN ONE MORE TIME. THIS TIME THE PLT ANSWERED WITH 'ACR WWWW' AND I ACKNOWLEDGED HIS XMISSION. LATER I FINALLY REALIZED THE PLT HAD BEEN CALLING HIMSELF 'ACR FFFF.' HE CONTINUED TO USE THIS CALL SIGN THROUGHOUT MY SECTOR AND AT LEAST THE NEXT SECTOR. OF COURSE, I'M WELL AWARE THAT PLTS ARE NOT REQUIRED TO USE STANDARD PHRASEOLOGY (AS CTLRS ARE) BUT THE CONFUSION, DELAY, AND EXTRA XMISSIONS NEEDED TO LOCATE AND IDENT THIS ACFT WERE MOST UNWELCOME.
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.