 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-300 aircraft taxiing didn't follow written taxi routing as shown on airport diagram chart. Ground controller didn't specify specific routing when initially contacted, but just said to taxi sbound on aa.
| Attributes | |
| ACN | 380504 |
| Time | |
| Date | 199709 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : lax |
| State Reference | CA |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other Other |
| Flight Phase | ground other : taxi |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| ASRS Report | 380504 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument |
| Events | |
| Anomaly | non adherence : published procedure non adherence : clearance |
| Independent Detector | other controllera |
| Resolutory Action | other |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Intra Facility Coordination Failure Pilot Deviation |
Narrative:
Landed runway 24R lax and after crossing runway 24L instructed to taxi 'aa' sbound by first ground controller and then given a new frequency for ground. Contacted him and his entire response was 'roger.' proceeded on 'aa' and left on taxiway C because air carrier X was on taxiway B waiting for 'aa.' ground control then told us we were taxiing without a clearance. He thought we had been assigned the 'bridge route.' we had not received the 'bridge route.' the biggest problem is the verbal clutter on the airport diagram page for lax. The 'bridge route' is in the upper right portion of the fold out page but the route itself is on the far left side of the page. Also 'bridge route' does not mention checkpoint 3. Spoke with the tower supervisor and he agrees the page needs to be changed. Tower supervisor said first ground controller dropped the ball by not giving us 'bridge route' but thinking we would know to do the 'route' instinctively.
Original NASA ASRS Text
Title: B737-300 ACFT TAXIING DIDN'T FOLLOW WRITTEN TAXI ROUTING AS SHOWN ON ARPT DIAGRAM CHART. GND CTLR DIDN'T SPECIFY SPECIFIC ROUTING WHEN INITIALLY CONTACTED, BUT JUST SAID TO TAXI SBOUND ON AA.
Narrative: LANDED RWY 24R LAX AND AFTER XING RWY 24L INSTRUCTED TO TAXI 'AA' SBOUND BY FIRST GND CTLR AND THEN GIVEN A NEW FREQ FOR GND. CONTACTED HIM AND HIS ENTIRE RESPONSE WAS 'ROGER.' PROCEEDED ON 'AA' AND LEFT ON TXWY C BECAUSE ACR X WAS ON TXWY B WAITING FOR 'AA.' GND CTL THEN TOLD US WE WERE TAXIING WITHOUT A CLRNC. HE THOUGHT WE HAD BEEN ASSIGNED THE 'BRIDGE RTE.' WE HAD NOT RECEIVED THE 'BRIDGE RTE.' THE BIGGEST PROB IS THE VERBAL CLUTTER ON THE ARPT DIAGRAM PAGE FOR LAX. THE 'BRIDGE RTE' IS IN THE UPPER R PORTION OF THE FOLD OUT PAGE BUT THE RTE ITSELF IS ON THE FAR L SIDE OF THE PAGE. ALSO 'BRIDGE RTE' DOES NOT MENTION CHECKPOINT 3. SPOKE WITH THE TWR SUPVR AND HE AGREES THE PAGE NEEDS TO BE CHANGED. TWR SUPVR SAID FIRST GND CTLR DROPPED THE BALL BY NOT GIVING US 'BRIDGE RTE' BUT THINKING WE WOULD KNOW TO DO THE 'RTE' INSTINCTIVELY.
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.