 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Reported aircraft go around for runway 25R and flew over reporter's aircraft holding in position on the same runway.
| Attributes | |
| ACN | 385721 |
| Time | |
| Date | 199711 |
| Day | Mon |
| Local Time Of Day | 0001 To 0600 |
| Place | |
| Locale Reference | airport : las |
| State Reference | NV |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other Other |
| Flight Phase | ground : holding |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | Boeing Company Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach landing : go around |
| Route In Use | arrival other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 240 flight time total : 17000 flight time type : 10000 |
| ASRS Report | 385721 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 240 flight time total : 4000 flight time type : 1500 |
| ASRS Report | 385845 |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance other |
| Consequence | Other |
| Miss Distance | horizontal : 0 vertical : 300 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | other |
Narrative:
We were cleared in position and hold on runway 25R by the local controller. While in position and hold aircraft down-field was cleared to cross our runway and 'contact ground on other side.' we held in position for approximately 2 mins. The next thing we heard was 'go around.' we heard a voice say 'we didn't see him either.' we saw a boeing jet executing a missed approach over the top of us. The tower then switched it to approach frequency and approximately 20 seconds later cleared us for takeoff. Takeoff and departure were normal with no further problems. We had not heard any xmissions to the other jet or had heard him being cleared to land. After departure I asked the tower whether we needed to talk to someone about what happened and he stated 'no, but I need to talk to someone.' supplemental information from acn 385845: tower controller seemed distracted when we first contacted him after switching from ground when nearing the hold short for runway 25R. At that hour, the ground controller seemed to be working more than one frequency. We know that during slack periods controllers are given two or more frequencys/jobs. I believe a contributing factor in this incident could have been a tower controller given too many 'unrelated' duties, where he couldn't give his full attention to controling his airspace/runways.
Original NASA ASRS Text
Title: RPTED ACFT GAR FOR RWY 25R AND FLEW OVER RPTR'S ACFT HOLDING IN POS ON THE SAME RWY.
Narrative: WE WERE CLRED IN POS AND HOLD ON RWY 25R BY THE LCL CTLR. WHILE IN POS AND HOLD ACFT DOWN-FIELD WAS CLRED TO CROSS OUR RWY AND 'CONTACT GND ON OTHER SIDE.' WE HELD IN POS FOR APPROX 2 MINS. THE NEXT THING WE HEARD WAS 'GAR.' WE HEARD A VOICE SAY 'WE DIDN'T SEE HIM EITHER.' WE SAW A BOEING JET EXECUTING A MISSED APCH OVER THE TOP OF US. THE TWR THEN SWITCHED IT TO APCH FREQ AND APPROX 20 SECONDS LATER CLRED US FOR TKOF. TKOF AND DEP WERE NORMAL WITH NO FURTHER PROBS. WE HAD NOT HEARD ANY XMISSIONS TO THE OTHER JET OR HAD HEARD HIM BEING CLRED TO LAND. AFTER DEP I ASKED THE TWR WHETHER WE NEEDED TO TALK TO SOMEONE ABOUT WHAT HAPPENED AND HE STATED 'NO, BUT I NEED TO TALK TO SOMEONE.' SUPPLEMENTAL INFO FROM ACN 385845: TWR CTLR SEEMED DISTRACTED WHEN WE FIRST CONTACTED HIM AFTER SWITCHING FROM GND WHEN NEARING THE HOLD SHORT FOR RWY 25R. AT THAT HR, THE GND CTLR SEEMED TO BE WORKING MORE THAN ONE FREQ. WE KNOW THAT DURING SLACK PERIODS CTLRS ARE GIVEN TWO OR MORE FREQS/JOBS. I BELIEVE A CONTRIBUTING FACTOR IN THIS INCIDENT COULD HAVE BEEN A TWR CTLR GIVEN TOO MANY 'UNRELATED' DUTIES, WHERE HE COULDN'T GIVE HIS FULL ATTN TO CTLING HIS AIRSPACE/RWYS.
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.