37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 465220 |
Time | |
Date | 200003 |
Day | Sun |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : pbi.airport |
State Reference | FL |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Controlling Facilities | tower : pbi.tower |
Operator | common carrier : air carrier |
Make Model Name | Beechcraft Twin Turboprop Jet Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : takeoff roll |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : pbi.tower |
Operator | general aviation : corporate |
Make Model Name | Gulfstream IV |
Operating Under FAR Part | Part 91 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : ground |
Qualification | controller : radar |
Experience | controller radar : 14 |
ASRS Report | 465220 |
Person 2 | |
Affiliation | government : faa |
Function | controller : local |
Qualification | controller : radar |
Events | |
Anomaly | conflict : ground less severe incursion : runway non adherence : published procedure non adherence : required legal separation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance none taken : detected after the fact |
Consequence | faa : investigated |
Miss Distance | horizontal : 2000 vertical : 500 |
Supplementary | |
Problem Areas | ATC Facility ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Intra Facility Coordination Failure Operational Deviation |
Narrative:
I was working ground control. I had 2 GLF4 aircraft and a CL60 taxiing for departure to runway 9L from FBO. Taxi route: taxiway east cross runway 31 taxiway F cross runway 9L taxiway C to runway 9L. I had previously taxied a commuter to runway 13 for departure. When I placed the commuter's departure strip in the local control strip bay, I informed local and cabin attendant coordinator (supervisor) that I needed to cross the departure end of runway 13, 3 times. I answered a few more calls then heard local say 'you're good for runway 13.' I took that as approval to cross runway 13 departure end and issued clrncs to cross runway 13 with the 2 GLF4's and the CL60. Local told me to 'stop that guy,' pointing at the first GLF4. I looked and saw the BE02 that had departed, and the nose of the GLF4 appeared to be on the runway. 2 issues I feel contributed to this error: 1) when working ground control and having a local controller approve my request to cross an active runway without using the phraseology 'cross,' I've always questioned the coordination. I broke my own rule and did not affect positive coordination for the runway crossing. 2) at pbi, aircraft parked at the FBO's have to cross 2 active runways, regardless of route, to get to runway 9L. Runway incursions will probably continue with this taxi flow.
Original NASA ASRS Text
Title: ACFT Y IS GIVEN A CLRNC TO CROSS THE RWY AS ACFT X IS TAKING OFF.
Narrative: I WAS WORKING GND CTL. I HAD 2 GLF4 ACFT AND A CL60 TAXIING FOR DEP TO RWY 9L FROM FBO. TAXI RTE: TXWY E CROSS RWY 31 TXWY F CROSS RWY 9L TXWY C TO RWY 9L. I HAD PREVIOUSLY TAXIED A COMMUTER TO RWY 13 FOR DEP. WHEN I PLACED THE COMMUTER'S DEP STRIP IN THE LCL CTL STRIP BAY, I INFORMED LCL AND CAB COORDINATOR (SUPVR) THAT I NEEDED TO CROSS THE DEP END OF RWY 13, 3 TIMES. I ANSWERED A FEW MORE CALLS THEN HEARD LCL SAY 'YOU'RE GOOD FOR RWY 13.' I TOOK THAT AS APPROVAL TO CROSS RWY 13 DEP END AND ISSUED CLRNCS TO CROSS RWY 13 WITH THE 2 GLF4'S AND THE CL60. LCL TOLD ME TO 'STOP THAT GUY,' POINTING AT THE FIRST GLF4. I LOOKED AND SAW THE BE02 THAT HAD DEPARTED, AND THE NOSE OF THE GLF4 APPEARED TO BE ON THE RWY. 2 ISSUES I FEEL CONTRIBUTED TO THIS ERROR: 1) WHEN WORKING GND CTL AND HAVING A LCL CTLR APPROVE MY REQUEST TO CROSS AN ACTIVE RWY WITHOUT USING THE PHRASEOLOGY 'CROSS,' I'VE ALWAYS QUESTIONED THE COORD. I BROKE MY OWN RULE AND DID NOT AFFECT POSITIVE COORD FOR THE RWY XING. 2) AT PBI, ACFT PARKED AT THE FBO'S HAVE TO CROSS 2 ACTIVE RWYS, REGARDLESS OF RTE, TO GET TO RWY 9L. RWY INCURSIONS WILL PROBABLY CONTINUE WITH THIS TAXI FLOW.
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.