37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 224125 |
Time | |
Date | 199210 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : hpn |
State Reference | NY |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : corporate |
Make Model Name | Light Transport, Low Wing, 2 Turbojet Eng |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Light Transport, Low Wing, 2 Turbojet Eng |
Flight Phase | climbout : takeoff |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : ground |
Qualification | controller : non radar |
Experience | controller non radar : 5 |
ASRS Report | 224125 |
Person 2 | |
Affiliation | government : faa |
Function | controller : local |
Qualification | controller : non radar |
Events | |
Anomaly | conflict : ground critical non adherence : published procedure non adherence : required legal separation |
Independent Detector | other flight crewa |
Resolutory Action | other |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 100 vertical : 0 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error Inter Facility Coordination Failure |
Narrative:
Cpr X requested taxi to the active. As ground controller, I gave him instructions to proceed to runway 34 to hold short of runway 29. As the cpr X approached the hold line of runway 29 at taxiway east, I requested permission to cross runway 29 at taxiway east from the local controller. Quite sure that I had heard him specifically say 'cross,' I proceeded to clear the cpr X to cross runway 29. I few seconds later, the pilot keyed up and, in so many words, let me know that he did not appreciate clearance to cross when an light transport was on departure roll on runway 29. Had the pilots not performed their routine doublechk prior to crossing, there could have been serious consequences. What caused the problem, obviously, was a misunderstanding in communication between myself and the local controller. There is no way that as a ground controller I would have crossed an active runway without coordination. Yet, the local controller says no such authorization was relayed. As a remedy, I would suggest that ground controllers remain diligent about scanning the runways.
Original NASA ASRS Text
Title: ATCT INTERFAC COORD. GND CTLR UNAUTHORIZED RWY XING WITH CPR X HAD LTSS FROM LTSS ON TKOF ROLL. SYS ERROR.
Narrative: CPR X REQUESTED TAXI TO THE ACTIVE. AS GND CTLR, I GAVE HIM INSTRUCTIONS TO PROCEED TO RWY 34 TO HOLD SHORT OF RWY 29. AS THE CPR X APCHED THE HOLD LINE OF RWY 29 AT TAXIWAY E, I REQUESTED PERMISSION TO CROSS RWY 29 AT TAXIWAY E FROM THE LCL CTLR. QUITE SURE THAT I HAD HEARD HIM SPECIFICALLY SAY 'CROSS,' I PROCEEDED TO CLR THE CPR X TO CROSS RWY 29. I FEW SECONDS LATER, THE PLT KEYED UP AND, IN SO MANY WORDS, LET ME KNOW THAT HE DID NOT APPRECIATE CLRNC TO CROSS WHEN AN LTT WAS ON DEP ROLL ON RWY 29. HAD THE PLTS NOT PERFORMED THEIR ROUTINE DOUBLECHK PRIOR TO XING, THERE COULD HAVE BEEN SERIOUS CONSEQUENCES. WHAT CAUSED THE PROBLEM, OBVIOUSLY, WAS A MISUNDERSTANDING IN COM BTWN MYSELF AND THE LCL CTLR. THERE IS NO WAY THAT AS A GND CTLR I WOULD HAVE CROSSED AN ACTIVE RWY WITHOUT COORD. YET, THE LCL CTLR SAYS NO SUCH AUTHORIZATION WAS RELAYED. AS A REMEDY, I WOULD SUGGEST THAT GND CTLRS REMAIN DILIGENT ABOUT SCANNING THE RWYS.
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.