37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1088463 |
Time | |
Date | 201305 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | IAH.Airport |
State Reference | TX |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | A319 |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Aircraft 2 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Person 2 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Ground Incursion Taxiway |
Narrative:
Following push-back (we were instructed to push tail east for a 15L departure); we called ramp for taxi clearance. We were instructed to taxi to rb and proceed to spot X. Ramp control informed us there was an inbound jet (from the rb bridge) on rb that was giving way to us. When the captain noticed the inbound jet; it had already transitioned to the rc line inbound. That area of the ramp is very dark and the signage is poor. As a result; the captain misjudged the location to the jet and consequently we also joined rc instead of rb. By the time we realized our error we had taxied beyond spot Y and were beginning to encroach upon taxiway wb. Adding further confusion to our taxi clearance; there was also an A320 proceeding westbound on rb (possibly RA; area is very dark and difficult to tell exactly which line they were on) that we were never told anything about. So; as we began our taxi southbound to join the rb line; the A320 was proceeding westbound towards wb. As a result of their position on the ramp area; we assumed the line north of their position was rb. Unfortunately; that was not the case as the line to their north turned out to be rc. Then this same A320 joined wb northbound. This crew continued their taxi despite our relative position to taxiway wb. In fact; the wingtip of the A320 came within an uncomfortably close distance of the nose/flight deck area of our aircraft. At no point did the A320 slow or stop and permit us to maneuver to a safe area. They merely taxied off the centerline to the west and created a very dangerous situation.poor lighting/signage in the ramp area with multiple taxi lines/call spots; in a very poorly light ramp area; and the close proximity to a taxiway the potential for improper maneuvering is very high. Also within that same small area; there are 3 radio frequencies (ramp; clearance; ground) aircraft are required to talk to. Depending on position and what instructions have been given to each aircraft each one could be on a separate frequency reducing area situational awareness dramatically. Improve lighting/signage in ramp area. Streamline the ATC process by eliminating frequency changes in small area/short distance. Have ground support push aircraft on to the appropriate taxi line (RA; rb; rc) prior to disconnect.
Original NASA ASRS Text
Title: A319 flight crew reports being confused by their taxi clearance and the Romeo taxi lines south of the west ramp at IAH.
Narrative: Following push-back (we were instructed to push tail east for a 15L departure); we called Ramp for taxi clearance. We were instructed to taxi to RB and proceed to Spot X. Ramp Control informed us there was an inbound jet (from the RB Bridge) on RB that was giving way to us. When the Captain noticed the inbound jet; it had already transitioned to the RC line inbound. That area of the ramp is very dark and the signage is poor. As a result; the Captain misjudged the location to the jet and consequently we also joined RC instead of RB. By the time we realized our error we had taxied beyond Spot Y and were beginning to encroach upon taxiway WB. Adding further confusion to our taxi clearance; there was also an A320 proceeding westbound on RB (possibly RA; area is very dark and difficult to tell exactly which line they were on) that we were never told anything about. So; as we began our taxi southbound to join the RB line; the A320 was proceeding westbound towards WB. As a result of their position on the ramp area; we assumed the line north of their position was RB. Unfortunately; that was not the case as the line to their north turned out to be RC. Then this same A320 joined WB northbound. This crew continued their taxi despite our relative position to taxiway WB. In fact; the wingtip of the A320 came within an uncomfortably close distance of the nose/flight deck area of our aircraft. At no point did the A320 slow or stop and permit us to maneuver to a safe area. They merely taxied off the centerline to the west and created a very dangerous situation.Poor lighting/signage in the ramp area With multiple taxi lines/call spots; in a very poorly light ramp area; and the close proximity to a taxiway the potential for improper maneuvering is very high. Also within that same small area; there are 3 radio frequencies (Ramp; Clearance; Ground) aircraft are required to talk to. Depending on position and what instructions have been given to each aircraft each one could be on a separate frequency reducing area situational awareness dramatically. Improve lighting/signage in ramp area. Streamline the ATC process by eliminating frequency changes in small area/short distance. Have ground support push aircraft on to the appropriate taxi line (RA; RB; RC) prior to disconnect.
Data retrieved from NASA's ASRS site as of July 2013 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.