37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 521689 |
Time | |
Date | 200108 |
Day | Sat |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : ont.airport |
State Reference | CA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air taxi |
Make Model Name | Airliner 99 |
Operating Under FAR Part | Part 135 |
Flight Phase | ground : taxi ground : position and hold ground : takeoff roll |
Flight Plan | VFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : combined local controller : supervisor oversight : supervisor |
Qualification | controller : radar |
Experience | controller limited radar : 3 controller military : 8 controller radar : 7 controller supervisory : 3 controller time certified in position1 : 3 |
ASRS Report | 521689 |
Person 2 | |
Affiliation | government : faa |
Function | controller : local |
Qualification | controller : developmental |
Events | |
Anomaly | incursion : runway non adherence : clearance non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : investigated |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Intra Facility Coordination Failure Pilot Deviation |
Narrative:
I was in training in local control, combined with cabin attendant coordinator. A BE99 was holding short of runway 26L. There was a problem with his flight plan, while I was talking to flight data about it, the developmental instructed the aircraft to cross runway 26L and hold short of runway 26R. The aircraft crossed runway 26L and into position on runway 26R. I discovered the incursion while scanning the runways. I asked who was on 26R, and the developmental said no one should be. When I reviewed the tape, I discovered the pilot had not acknowledged any instructions, he just crossed runway 26L and onto runway 26R. This incident happened because I was working out the problem with his flight plan and the developmental went to the next call without getting a readback from the pilot. There was no loss of separation with the other aircraft and he was cleared for takeoff. This was a case of miscom of both sides, the pilots for not acknowledging the control instruction, and ours for not restating the hold short instructions.
Original NASA ASRS Text
Title: ONT LC DEVELOPMENTAL DOES NOT CHALLENGE BE99 NON-READBACK TO CROSS AND HOLDSHORT AS PLT TAXIES ONTO OTHER PARALLEL RWY.
Narrative: I WAS IN TRAINING IN LCL CTL, COMBINED WITH CAB COORDINATOR. A BE99 WAS HOLDING SHORT OF RWY 26L. THERE WAS A PROB WITH HIS FLT PLAN, WHILE I WAS TALKING TO FLT DATA ABOUT IT, THE DEVELOPMENTAL INSTRUCTED THE ACFT TO CROSS RWY 26L AND HOLD SHORT OF RWY 26R. THE ACFT CROSSED RWY 26L AND INTO POS ON RWY 26R. I DISCOVERED THE INCURSION WHILE SCANNING THE RWYS. I ASKED WHO WAS ON 26R, AND THE DEVELOPMENTAL SAID NO ONE SHOULD BE. WHEN I REVIEWED THE TAPE, I DISCOVERED THE PLT HAD NOT ACKNOWLEDGED ANY INSTRUCTIONS, HE JUST CROSSED RWY 26L AND ONTO RWY 26R. THIS INCIDENT HAPPENED BECAUSE I WAS WORKING OUT THE PROB WITH HIS FLT PLAN AND THE DEVELOPMENTAL WENT TO THE NEXT CALL WITHOUT GETTING A READBACK FROM THE PLT. THERE WAS NO LOSS OF SEPARATION WITH THE OTHER ACFT AND HE WAS CLEARED FOR TKOF. THIS WAS A CASE OF MISCOM OF BOTH SIDES, THE PLTS FOR NOT ACKNOWLEDGING THE CTL INSTRUCTION, AND OURS FOR NOT RESTATING THE HOLD SHORT INSTRUCTIONS.
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.