37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 266448 |
Time | |
Date | 199403 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : mei |
State Reference | MS |
Altitude | msl bound lower : 28000 msl bound upper : 28000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : ztl artcc : zme tower : san |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | cruise other |
Route In Use | enroute : direct |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise other |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 8000 flight time type : 2400 |
ASRS Report | 266448 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 190 flight time total : 13000 flight time type : 4000 |
ASRS Report | 266199 |
Events | |
Anomaly | non adherence : published procedure other anomaly other |
Independent Detector | other other : unspecified atc |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew faa : investigated |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Inter Facility Coordination Failure Operational Deviation |
Narrative:
Air carrier X encountered continuous light chop while cruising at FL310 and asked ZTL for a ride report. Atl handed us off to memphis, explaining they would have better information regarding the flight conditions. ZME reported a smooth ride at all altitudes. We asked for lower, reporting the continuous light chop at FL310. We were cleared to FL280. After cruising at FL280 for a while, the captain and I began discussing the need to begin our descent for our arrival at jackson, ms, when we heard the controller ask another company aircraft flight (Y123 versus X123) what altitude they were at. This was the first time we'd heard this call sign on the frequency, and, due to the similarity of the call signs and nature of the question, we immediately wondered if the 2 call signs and been confused. When we asked the controller for a lower altitude, he told us we were on the wrong frequency and handed us off to another mem controller. When we checked in, the new controller immediately asked us who had cleared us to FL280. When we replied it was the previous controller, he asked for the frequency. The rest of the flight proceeded without incident, but we were fairly certain the 2 call signs had been confused and we weren't supposed to have been at FL280. On the ground, the captain confirmed this via telephone with ZME. The supervisor explained the controller was new and had confused our call signs. Fortunately, there never was a traffic conflict.
Original NASA ASRS Text
Title: ACR X ON WRONG FREQ WITH SIMILAR CALL SIGN. ACFT WAS MISTAKENLY ISSUED DSCNT. PENETRATED ADJOINING AIRSPACE AT WRONG ALT.
Narrative: ACR X ENCOUNTERED CONTINUOUS LIGHT CHOP WHILE CRUISING AT FL310 AND ASKED ZTL FOR A RIDE RPT. ATL HANDED US OFF TO MEMPHIS, EXPLAINING THEY WOULD HAVE BETTER INFO REGARDING THE FLT CONDITIONS. ZME RPTED A SMOOTH RIDE AT ALL ALTS. WE ASKED FOR LOWER, RPTING THE CONTINUOUS LIGHT CHOP AT FL310. WE WERE CLRED TO FL280. AFTER CRUISING AT FL280 FOR A WHILE, THE CAPT AND I BEGAN DISCUSSING THE NEED TO BEGIN OUR DSCNT FOR OUR ARR AT JACKSON, MS, WHEN WE HEARD THE CTLR ASK ANOTHER COMPANY ACFT FLT (Y123 VERSUS X123) WHAT ALT THEY WERE AT. THIS WAS THE FIRST TIME WE'D HEARD THIS CALL SIGN ON THE FREQ, AND, DUE TO THE SIMILARITY OF THE CALL SIGNS AND NATURE OF THE QUESTION, WE IMMEDIATELY WONDERED IF THE 2 CALL SIGNS AND BEEN CONFUSED. WHEN WE ASKED THE CTLR FOR A LOWER ALT, HE TOLD US WE WERE ON THE WRONG FREQ AND HANDED US OFF TO ANOTHER MEM CTLR. WHEN WE CHKED IN, THE NEW CTLR IMMEDIATELY ASKED US WHO HAD CLRED US TO FL280. WHEN WE REPLIED IT WAS THE PREVIOUS CTLR, HE ASKED FOR THE FREQ. THE REST OF THE FLT PROCEEDED WITHOUT INCIDENT, BUT WE WERE FAIRLY CERTAIN THE 2 CALL SIGNS HAD BEEN CONFUSED AND WE WEREN'T SUPPOSED TO HAVE BEEN AT FL280. ON THE GND, THE CAPT CONFIRMED THIS VIA TELEPHONE WITH ZME. THE SUPVR EXPLAINED THE CTLR WAS NEW AND HAD CONFUSED OUR CALL SIGNS. FORTUNATELY, THERE NEVER WAS A TFC CONFLICT.
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.