 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
On takeoff and airborne at las airport runway 19L, a B737 was advised by the local controller that traffic was rolling out on runway 25R.
| Attributes | |
| ACN | 594347 |
| Time | |
| Date | 200309 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : las.airport |
| State Reference | NV |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : takeoff ground : takeoff roll |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tower : las.tower |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Flight Phase | ground : taxi landing : roll |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Experience | flight time last 90 days : 257 flight time total : 15084 flight time type : 10684 |
| ASRS Report | 594347 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Experience | flight time last 90 days : 150 flight time total : 5000 flight time type : 1000 |
| ASRS Report | 594348 |
| Events | |
| Anomaly | conflict : ground less severe incursion : runway non adherence : published procedure non adherence : required legal separation |
| Independent Detector | other controllera other flight crewa other flight crewb |
| Resolutory Action | controller : issued advisory none taken : detected after the fact |
| Miss Distance | horizontal : 150 |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
I was cleared for takeoff on runway 19L, and during the takeoff roll, tower called me and advised me of traffic on my left on the ground, and that they were not talking to him. I saw an airliner rolling out on runway 25R approaching my runway, and since I was very close to vr at this point, I rotated. The other aircraft did turn off before reaching my runway, so I did not fly over his aircraft, and I was well clear of him as I passed over runway 25R. Departure continued normally with no comments from anyone. We never did come close, but if that airplane had continued onto runway 19L, it would have made for some scary seconds. Even if he had, I am sure that I would have cleared his aircraft, since I had plenty of speed and climbing fast at that point. I contacted company ATC specialist upon landing in and described the event for him. He contacted the tower, and had a discussion with them. Supplemental information from acn 594348: during takeoff on runway 19L at las, just prior to V1/vr tower advised us of traffic on the ground to the left side. They were not in contact with this aircraft at the time. The traffic on the ground did stop short of runway 19L as we rotated, and no harm was done. This was clearly the las tower/ground controller's fault. We had been cleared for takeoff, and we were near V1/vr when the tower notified us of the traffic. Human mistakes can and will happen on both sides. I have great respect for vegas ATC, and I am glad they made the decision to point out the traffic to us. Just goes to show anything can happen, even on a clear blue VMC vegas day. Captain's leg runway 19L. Callback: called reporter to verify runway other aircraft used for landing. The reporter sated the other aircraft landed on runway 25R and turned off on taxiway A7. He said the controller did not state a land and hold short procedure was being used. He said the incident was not a close call.
Original NASA ASRS Text
Title: ON TKOF AND AIRBORNE AT LAS ARPT RWY 19L, A B737 WAS ADVISED BY THE LCL CTLR THAT TFC WAS ROLLING OUT ON RWY 25R.
Narrative: I WAS CLRED FOR TKOF ON RWY 19L, AND DURING THE TKOF ROLL, TWR CALLED ME AND ADVISED ME OF TFC ON MY L ON THE GND, AND THAT THEY WERE NOT TALKING TO HIM. I SAW AN AIRLINER ROLLING OUT ON RWY 25R APCHING MY RWY, AND SINCE I WAS VERY CLOSE TO VR AT THIS POINT, I ROTATED. THE OTHER ACFT DID TURN OFF BEFORE REACHING MY RWY, SO I DID NOT FLY OVER HIS ACFT, AND I WAS WELL CLR OF HIM AS I PASSED OVER RWY 25R. DEP CONTINUED NORMALLY WITH NO COMMENTS FROM ANYONE. WE NEVER DID COME CLOSE, BUT IF THAT AIRPLANE HAD CONTINUED ONTO RWY 19L, IT WOULD HAVE MADE FOR SOME SCARY SECONDS. EVEN IF HE HAD, I AM SURE THAT I WOULD HAVE CLRED HIS ACFT, SINCE I HAD PLENTY OF SPD AND CLBING FAST AT THAT POINT. I CONTACTED COMPANY ATC SPECIALIST UPON LNDG IN AND DESCRIBED THE EVENT FOR HIM. HE CONTACTED THE TWR, AND HAD A DISCUSSION WITH THEM. SUPPLEMENTAL INFO FROM ACN 594348: DURING TKOF ON RWY 19L AT LAS, JUST PRIOR TO V1/VR TWR ADVISED US OF TFC ON THE GND TO THE L SIDE. THEY WERE NOT IN CONTACT WITH THIS ACFT AT THE TIME. THE TFC ON THE GND DID STOP SHORT OF RWY 19L AS WE ROTATED, AND NO HARM WAS DONE. THIS WAS CLRLY THE LAS TWR/GND CTLR'S FAULT. WE HAD BEEN CLRED FOR TKOF, AND WE WERE NEAR V1/VR WHEN THE TWR NOTIFIED US OF THE TFC. HUMAN MISTAKES CAN AND WILL HAPPEN ON BOTH SIDES. I HAVE GREAT RESPECT FOR VEGAS ATC, AND I AM GLAD THEY MADE THE DECISION TO POINT OUT THE TFC TO US. JUST GOES TO SHOW ANYTHING CAN HAPPEN, EVEN ON A CLR BLUE VMC VEGAS DAY. CAPT'S LEG RWY 19L. CALLBACK: CALLED RPTR TO VERIFY RWY OTHER ACFT USED FOR LNDG. THE RPTR SATED THE OTHER ACFT LANDED ON RWY 25R AND TURNED OFF ON TXWY A7. HE SAID THE CTLR DID NOT STATE A LAND AND HOLD SHORT PROC WAS BEING USED. HE SAID THE INCIDENT WAS NOT A CLOSE CALL.
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.