37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1352973 |
Time | |
Date | 201605 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | CLT.Airport |
State Reference | NC |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Medium Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Ground Event / Encounter Other / Unknown |
Narrative:
Clt was in late night configuration; landing and departing on only runway 5. We were cleared for visual approach to runway 5. Clt tower cleared us to land on runway 5. The controller seemed flustered with the work load of only using runway 5 for both landings and takeoffs. During rollout after landing on runway 5; tower instructed us to turn left unto D; left on M; hold short of 36R. The first officer read back instructions to turn left on D; left on M; hold short of 36R. We expedited off the runway as instructed; turning left at D; left at M; and holding short of 36R. Another aircraft was cleared for takeoff and another was cleared to land; with the tower controller sounding flustered with all radio calls to the aircraft on tower frequency.the tower controller then told us to 'on mike cross runway 5' which is not possible since M does not cross runway 5; but instead crosses runway 36R; [the runway] we are holding short of. The first officer responded to the tower controller by asking; 'confirm you want us to cross runway 36R on taxiway mike' the tower controller responded; in a highly irritated and flustered tone 'negative cleared to cross runway 5 on mike'. Runway 5 was the runway that an aircraft was currently taking off on with another landing on short final. The first officer responded to the tower that we were holding short of runway 36R on taxiway M as instructed; not short of runway 5.I stayed put and told the first officer we would sit there holding short of runway 36R on taxiway M until the tower controller got themselves figured out and gave us a proper clearance to cross the correct runway. After about a minute of barking orders at the other aircraft on frequency; the tower instructed us; correctly this time to 'cross runway 36R on mike; taxi to the ramp' we read back the instructions; and now; having been proper clearance to cross the proper runway; we crossed runway 36R and proceeded to the ramp without further incident.of particular concern to me with this event is that the tower controller; twice in a row; even after we queried the error after the first mistake; gave us clearance to cross a runway we were not holding short of; but rather the runway that was in use with an aircraft both actively taking off and landing at that time. Runway 36R intersects runway 5 and this could have led to a very bad situation if we or another aircraft crossed the active runway with an aircraft currently on departure roll and one on final. I believe this would be a good learning experience for the tower controllers in clt since in other instances if we or another crew was not paying attention it could have led to a very bad situation.[I suggest a] better late night procedure for clt tower; having another controller working at that point could have helped out the controller working tower; as they were clearly overloaded by the level of operations they were handling at the time. Have clt tower use this as a learning experience to better their operations.
Original NASA ASRS Text
Title: Pilot reported landing at CLT then being issued incorrect crossing instructions from the Tower Controller. Pilot questioned Controller twice; then sat there until the Controller figured out where they were and corrected the instructions.
Narrative: CLT was in late night configuration; landing and departing on only Runway 5. We were cleared for visual approach to Runway 5. CLT Tower cleared us to land on Runway 5. The controller seemed flustered with the work load of only using Runway 5 for both landings and takeoffs. During rollout after landing on Runway 5; Tower instructed us to turn left unto D; left on M; hold short of 36R. The First Officer read back instructions to turn left on D; left on M; hold short of 36R. We expedited off the runway as instructed; turning left at D; left at M; and holding short of 36R. Another aircraft was cleared for takeoff and another was cleared to land; with the Tower Controller sounding flustered with all radio calls to the aircraft on Tower frequency.The Tower Controller then told us to 'on Mike cross Runway 5' which is not possible since M does not cross Runway 5; but instead crosses Runway 36R; [the runway] we are holding short of. The First Officer responded to the Tower Controller by asking; 'confirm you want us to cross Runway 36R on Taxiway Mike' The Tower Controller responded; in a highly irritated and flustered tone 'negative cleared to cross Runway 5 on Mike'. Runway 5 was the Runway that an aircraft was currently taking off on with another landing on short final. The First Officer responded to the Tower that we were holding short of Runway 36R on Taxiway M as instructed; not short of Runway 5.I stayed put and told the First Officer we would sit there holding short of Runway 36R on Taxiway M until the Tower Controller got themselves figured out and gave us a proper clearance to cross the correct runway. After about a minute of barking orders at the other aircraft on frequency; the tower instructed us; correctly this time to 'Cross Runway 36R on Mike; taxi to the ramp' we read back the instructions; and now; having been proper clearance to cross the proper runway; we crossed Runway 36R and proceeded to the ramp without further incident.Of particular concern to me with this event is that the Tower Controller; twice in a row; even after we queried the error after the first mistake; gave us clearance to cross a runway we were not holding short of; but rather the runway that was in use with an aircraft both actively taking off and landing at that time. Runway 36R intersects Runway 5 and this could have led to a very bad situation if we or another aircraft crossed the active runway with an aircraft currently on departure roll and one on final. I believe this would be a good learning experience for the Tower Controllers in CLT since in other instances if we or another crew was not paying attention it could have led to a very bad situation.[I suggest a] better late night procedure for CLT Tower; having another controller working at that point could have helped out the controller working Tower; as they were clearly overloaded by the level of operations they were handling at the time. Have CLT Tower use this as a learning experience to better their operations.
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.