 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Atx Y takeoff on occupied runway had less than standard separation from small transport X. System error.
| Attributes | |
| ACN | 225525 |
| Time | |
| Date | 199210 |
| Day | Thu |
| Local Time Of Day | 0001 To 0600 |
| Place | |
| Locale Reference | atc facility : oak |
| State Reference | CA |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tower : jfk |
| Operator | general aviation : personal |
| Make Model Name | Small Transport |
| Flight Phase | landing other |
| Flight Plan | VFR |
| Aircraft 2 | |
| Operator | common carrier : air taxi |
| Make Model Name | Small Transport, Low Wing, 2 Recip Eng |
| Flight Phase | climbout : takeoff |
| Flight Plan | VFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | controller : local |
| Qualification | controller : non radar |
| ASRS Report | 225525 |
| Person 2 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : private |
| Events | |
| Anomaly | conflict : ground less severe non adherence : published procedure non adherence : required legal separation |
| Independent Detector | other controllera |
| Resolutory Action | none taken : detected after the fact |
| Consequence | Other |
| Miss Distance | horizontal : 2000 vertical : 0 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Small transport X was inbound from the west. 2-3 mi west of oak, I cleared small transport X to land runway 27R. About 5 mins later, atx X requested to depart runway 9L. I scanned the runway and saw nothing. The d-brite showed nothing. I then cleared atx Y for takeoff runway 9L. Ground control requested to cross runway 27R and left at B. I stated 'hold.' it was at this time I realized I had 2 aircraft on the runway. I told small transport X turn right immediately or now, I am not sure. Separation was lost on the runway. I can only surmise that small transport X was close to the airport and on base turn as the reason the d-brite dropped the data tag and lost radar, and also the reason I didn't see his lights. There was also portable flood lights at the approach end of runway 27L that were being used to aid in dumping sludge as landfill. The lights were shining into the tower cabin attendant -- a distraction and a glare. An absolute way to prevent this from happening again would be to change the noise abatement procedure and not have opposite direction operations -- use only 1 direction, in this case runway 27.
Original NASA ASRS Text
Title: ATX Y TKOF ON OCCUPIED RWY HAD LTSS FROM SMT X. SYS ERROR.
Narrative: SMT X WAS INBOUND FROM THE W. 2-3 MI W OF OAK, I CLRED SMT X TO LAND RWY 27R. ABOUT 5 MINS LATER, ATX X REQUESTED TO DEPART RWY 9L. I SCANNED THE RWY AND SAW NOTHING. THE D-BRITE SHOWED NOTHING. I THEN CLRED ATX Y FOR TKOF RWY 9L. GND CTL REQUESTED TO CROSS RWY 27R AND L AT B. I STATED 'HOLD.' IT WAS AT THIS TIME I REALIZED I HAD 2 ACFT ON THE RWY. I TOLD SMT X TURN R IMMEDIATELY OR NOW, I AM NOT SURE. SEPARATION WAS LOST ON THE RWY. I CAN ONLY SURMISE THAT SMT X WAS CLOSE TO THE ARPT AND ON BASE TURN AS THE REASON THE D-BRITE DROPPED THE DATA TAG AND LOST RADAR, AND ALSO THE REASON I DIDN'T SEE HIS LIGHTS. THERE WAS ALSO PORTABLE FLOOD LIGHTS AT THE APCH END OF RWY 27L THAT WERE BEING USED TO AID IN DUMPING SLUDGE AS LANDFILL. THE LIGHTS WERE SHINING INTO THE TWR CAB -- A DISTR AND A GLARE. AN ABSOLUTE WAY TO PREVENT THIS FROM HAPPENING AGAIN WOULD BE TO CHANGE THE NOISE ABATEMENT PROC AND NOT HAVE OPPOSITE DIRECTION OPS -- USE ONLY 1 DIRECTION, IN THIS CASE RWY 27.
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.