37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 172464 |
Time | |
Date | 199103 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : rdu |
State Reference | NC |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Large Transport, Low Wing, 2 Turbojet Eng |
Navigation In Use | Other Other |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : ground |
Qualification | controller : non radar |
ASRS Report | 172464 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : published procedure other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : unable |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
During an outbnd hub complex (26 simultaneous departures) I, as the ground controller, observed an large transport taxiing toward a parallel taxiway, yet to make radio contact. Being the only large transport on the ramp at the time, I quickly ascertained the call sign to be air carrier X. I tried on several occasions to make radio contact (unsuccessful). Air carrier X make his way onto taxiway bravo, stopped and paused for a min or so; realizing the infraction, turned back into the terminal ramp and proceeded to the normal taxi point and called. Although the movement of air carrier X caused no problems in the pilot's mind, I had already adjusted outbnd and inbound traffic to compensate for his possible actions. We have standard exit points at rdu and agreements with air carrier ramp tower on how aircraft enter and exit the ramp. The problem (I feel) is that the crew is more involved in preflight taxi and lose sight of their actual movement. Also it is a more apparent problem with larger or heavy aircraft.
Original NASA ASRS Text
Title: ACR X TAXIED ONTO CONTROLLED TXWY WITHOUT ATC CLRNC. PLTDEV.
Narrative: DURING AN OUTBND HUB COMPLEX (26 SIMULTANEOUS DEPS) I, AS THE GND CTLR, OBSERVED AN LGT TAXIING TOWARD A PARALLEL TXWY, YET TO MAKE RADIO CONTACT. BEING THE ONLY LGT ON THE RAMP AT THE TIME, I QUICKLY ASCERTAINED THE CALL SIGN TO BE ACR X. I TRIED ON SEVERAL OCCASIONS TO MAKE RADIO CONTACT (UNSUCCESSFUL). ACR X MAKE HIS WAY ONTO TXWY BRAVO, STOPPED AND PAUSED FOR A MIN OR SO; REALIZING THE INFRACTION, TURNED BACK INTO THE TERMINAL RAMP AND PROCEEDED TO THE NORMAL TAXI POINT AND CALLED. ALTHOUGH THE MOVEMENT OF ACR X CAUSED NO PROBS IN THE PLT'S MIND, I HAD ALREADY ADJUSTED OUTBND AND INBND TFC TO COMPENSATE FOR HIS POSSIBLE ACTIONS. WE HAVE STANDARD EXIT POINTS AT RDU AND AGREEMENTS WITH ACR RAMP TWR ON HOW ACFT ENTER AND EXIT THE RAMP. THE PROB (I FEEL) IS THAT THE CREW IS MORE INVOLVED IN PREFLT TAXI AND LOSE SIGHT OF THEIR ACTUAL MOVEMENT. ALSO IT IS A MORE APPARENT PROB WITH LARGER OR HVY ACFT.
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.