37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1426990 |
Time | |
Date | 201702 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZTL.ARTCC |
State Reference | GA |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | SID ESTRR2 |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance |
Narrative:
While departing clt on the ESTRR2 departure approaching debie; we were in contact with ATC on frequency 127.87. We were issued a climb to 30000 feet. We read back the clearance and confirmed the set altitude and began our climb and subsequent level off at 30000 feet. We could hear ATC communicating with other aircraft. We did notice ATC talking to 'carrier abcd' multiple times both prior to and after our climb. It should be noted that the controller's diction was somewhat difficult to understand. We received an ACARS message to contact atlanta center on 125.62. We could still hear ATC chatter on 127.87; however we switched to 125.62 as directed. Upon normal check on 125.62 the controller responded with an unusual response of 'carrier aecd; where ya been.' I responded with the accurate response that we were on 127.87; we could hear on 127.87; and we're never given a handoff by 127.87. The controller responded 'ok'. She (ATC) issued us a climb and then asked; 'carrier aecd; who told you to climb to 300?' I responded that the last controller did. I then asked if there was a problem? The controller responded that she controls the airspace above 23000 feet and she had to move an aircraft as we 'just climbed on up to 300'. We were given a new frequency; and upon check on we're given a climb to 38000 feet. Shortly thereafter we were told to phone call ATC during normal business hours. Not clear as to why the event occurred the way it had. We were both monitoring the radio; and cockpit chatter was minimal. We both agree that there was never a controller call in regards to our altitude change after our read back of the original altitude clearance to climb to 30000 feet. No attempts were heard from ATC in any way using our call sign. The controller was slightly difficult to understand; and his transmission strength was less than perfect; but we could follow his calls to other aircraft. We did hear the calls to carrier abcd; and perhaps they were erroneously directed towards us; but we had no reason to suspect we were being called. Barring new communication technology; it would be hard to suggest a change. We believed we were complying correctly with all ATC clearances; and were keeping vigilant radio listening. Perhaps the controllers diction could've been clearer.
Original NASA ASRS Text
Title: Air carrier flight crew received a climb clearance to 30;000 feet. The crew received an ACARS message to contact ATC on a different frequency where the Controller stated they should not have been climbing.
Narrative: While departing CLT on the ESTRR2 departure approaching DEBIE; we were in contact with ATC on frequency 127.87. We were issued a climb to 30000 feet. We read back the clearance and confirmed the set altitude and began our climb and subsequent level off at 30000 feet. We could hear ATC communicating with other aircraft. We did notice ATC talking to 'Carrier ABCD' multiple times both prior to and after our climb. It should be noted that the controller's diction was somewhat difficult to understand. We received an ACARS message to contact Atlanta center on 125.62. We could still hear ATC chatter on 127.87; however we switched to 125.62 as directed. Upon normal check on 125.62 the controller responded with an unusual response of 'Carrier AECD; where ya been.' I responded with the accurate response that we were on 127.87; we could hear on 127.87; and we're never given a handoff by 127.87. The controller responded 'ok'. She (ATC) issued us a climb and then asked; 'Carrier AECD; who told you to climb to 300?' I responded that the last controller did. I then asked if there was a problem? The controller responded that she controls the airspace above 23000 feet and she had to move an aircraft as we 'just climbed on up to 300'. We were given a new frequency; and upon check on we're given a climb to 38000 feet. Shortly thereafter we were told to phone call ATC during normal business hours. Not clear as to why the event occurred the way it had. We were both monitoring the radio; and cockpit chatter was minimal. We both agree that there was never a controller call in regards to our altitude change after our read back of the original altitude clearance to climb to 30000 feet. No attempts were heard from ATC in any way using our call sign. The controller was slightly difficult to understand; and his transmission strength was less than perfect; but we could follow his calls to other aircraft. We did hear the calls to Carrier ABCD; and perhaps they were erroneously directed towards us; but we had no reason to suspect we were being called. Barring new communication technology; it would be hard to suggest a change. We believed we were complying correctly with all ATC clearances; and were keeping vigilant radio listening. Perhaps the controllers diction could've been clearer.
Data retrieved from NASA's ASRS site 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.