37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 123963 |
Time | |
Date | 198908 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : sat |
State Reference | TX |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | landing other |
Person 1 | |
Affiliation | government : faa |
Function | controller : ground |
Qualification | controller : non radar |
ASRS Report | 123963 |
Person 2 | |
Affiliation | government : faa |
Function | controller : local |
Qualification | controller : non radar |
Events | |
Anomaly | conflict : ground critical incursion : runway non adherence : published procedure non adherence : required legal separation |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : investigated |
Miss Distance | unspecified : 2000 vertical : 0 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error Intra Facility Coordination Failure |
Narrative:
Vehicle a contacted ground control to cross runway 12R at taxiway P. Ground control scanned and observed what he thought was vehicle a at taxiway M. Ground control coordinated with local control to cross 12R at M, behind a landing aircraft. Local approved the crossing. Ground control observed the aircraft landing and rolling past M. Ground control told vehicle a to cross runway 12R. Vehicle a crossed runway 12R at intersection P approximately 2000' in front of the landing aircraft. The problem was discovered as ground control saw vehicle a crossing at taxiway P, in front of the landing aircraft. No action or evasive action was taken as the vehicle had cleared the runway. Factors contributing to the situation include: an extremely high number of vehicles on the airport. Allowing vehicles to cross a runway at any taxiway, instead of one or two designated. Poor scanning by ground control. I believe the situation occurred because of poor scanning by ground control, along with too many crossing intxns for vehicles. My suggestion to prevent a recurrence is designate 1 or 2 intxns at each runway where all vehicles must cross.
Original NASA ASRS Text
Title: GND CTLR CROSSED VEHICLE A TO CROSS RWY IN FRONT OF AN ACFT LNDG. OPERATIONAL ERROR. SYSTEM ERROR.
Narrative: VEHICLE A CONTACTED GND CTL TO CROSS RWY 12R AT TXWY P. GND CTL SCANNED AND OBSERVED WHAT HE THOUGHT WAS VEHICLE A AT TXWY M. GND CTL COORDINATED WITH LCL CTL TO CROSS 12R AT M, BEHIND A LNDG ACFT. LCL APPROVED THE XING. GND CTL OBSERVED THE ACFT LNDG AND ROLLING PAST M. GND CTL TOLD VEHICLE A TO CROSS RWY 12R. VEHICLE A CROSSED RWY 12R AT INTXN P APPROX 2000' IN FRONT OF THE LNDG ACFT. THE PROBLEM WAS DISCOVERED AS GND CTL SAW VEHICLE A XING AT TXWY P, IN FRONT OF THE LNDG ACFT. NO ACTION OR EVASIVE ACTION WAS TAKEN AS THE VEHICLE HAD CLRED THE RWY. FACTORS CONTRIBUTING TO THE SITUATION INCLUDE: AN EXTREMELY HIGH NUMBER OF VEHICLES ON THE ARPT. ALLOWING VEHICLES TO CROSS A RWY AT ANY TXWY, INSTEAD OF ONE OR TWO DESIGNATED. POOR SCANNING BY GND CTL. I BELIEVE THE SITUATION OCCURRED BECAUSE OF POOR SCANNING BY GND CTL, ALONG WITH TOO MANY XING INTXNS FOR VEHICLES. MY SUGGESTION TO PREVENT A RECURRENCE IS DESIGNATE 1 OR 2 INTXNS AT EACH RWY WHERE ALL VEHICLES MUST CROSS.
Data retrieved from NASA's ASRS site as of August 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.