ABE CTLR EXPERIENCED OPERROR WITH OPPOSITE DIRECTION RWY TFC WHEN DISTR BY OTHER DUTIES.

Date: 2005-06 · Aircraft: B727 Undifferentiated or Other Model · Phase: taxi

Anomalies: atc-issue-all-types|conflict-ground-conflict|less-severe

Synopsis

ABE CTLR EXPERIENCED OPERROR WITH OPPOSITE DIRECTION RWY TFC WHEN DISTR BY OTHER DUTIES.

Narrative

LCL/GND COMBINED IN THE TWR; STANDARD OP. RWY 24; WINDS OUT OF SW 10-12 KTS. INBOUND CRJ2 WANTED RWY 6; QUICKER FROM SW. I APPROVED IT; ALTHOUGH THOUGHT IT UNUSUAL DUE TO WIND VELOCITY. THE CTLR I RELIEVED CALLED ON IN-HOUSE PHONE AND TOLD ME HE WAS STILL 'SIGNED ON' IN THE TWR ON CRU-X PROGRAM; AUTOMATED PROGRAM FOR TRACKING TIME-ON-POS. IT TOOK MY 4TH TRY TO SIGN ME ON AT THE RIGHT TIME; AS A B727 CALLED 'READY.' THE SIGN-ON COMPUTER IS ALMOST ON THE FAR SIDE OF THE TWR. I RAN OVER TO LCL AND CLRED B727 FOR TKOF (RWY 24). AS I PUT THE HAND SET DOWN; I SAW CRJ2 ON LNDG ROLLOUT (RWY 6). I QUICKLY RESCINDED B727 TKOF CLRNC; BUT HE RESPONDED HE WAS OVER THE HOLD LINE. NEITHER PLT SEEMED PERTURBED BY THE EVENTS; ALTHOUGH I WAS. SAFETY WAS TECHNICALLY COMPROMISED; THOUGH CHANCE OF COLLISION WAS NIL. I WAS WRONG; BUT DID MY THINKING A RWY 6 ARR WAS SO UNUSUAL; OUT OF THE QUESTION; OR MESSING WITH THE CRU-X COMPUTER CAUSE THIS? TRUTH BE TOLD; I SCREWED UP. MY MIND; WITH THE WIND; WAS A STRAIGHT RWY 24 MODE; BUT THE COMPUTER ENTRIES CERTAINLY DISTR ME. HAD I NOT BEEN DOING REQUIRED COMPUTER PAPERWORK AWAY FROM THE LCL POS; I'M SURE THIS WOULDN'T HAVE HAPPENED.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.