 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
L30 controller described a conflict event resulting from controllers at nellis not keeping vgt landing traffic in tight and there by avoiding las departures.
| Attributes | |
| ACN | 977450 |
| Time | |
| Date | 201111 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | L30.TRACON |
| State Reference | NV |
| Aircraft 1 | |
| Make Model Name | Super King Air 200 |
| Flight Phase | Descent |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach Departure |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
A BE20 was IFR into vgt. Nellis AFB was working the aircraft. The dag position took a point out for the IFR landing. Didn't point the aircraft out to our position because they assumed the traffic wouldn't be a factor. The BE20 took about a 5 mile right base into runway 30L. We had 2 departures that came off that were in confliction with the arrival of three air carriers was the second departure and as it turned out; wasn't a factor; just too close for comfort. The B737 departing runway 1R at las was instantly head on with the BE20. Traffic was called. Our departure; the B737; was too low to vector due to MVA's. There may have been divergence; once tmu called vgt and asked them to tighten up the base for the BE20. Nellis needs to keep the vgt IFR arrivals much tighter into the airport. If they aren't doing this; the dag sector who takes the point out needs to point out the traffic to affected sectors; or initiate a call for release (crash fire rescue equipment).
Original NASA ASRS Text
Title: L30 Controller described a conflict event resulting from controllers at Nellis not keeping VGT landing traffic in tight and there by avoiding LAS departures.
Narrative: A BE20 was IFR into VGT. Nellis AFB was working the aircraft. The DAG position took a point out for the IFR landing. Didn't point the aircraft out to our position because they assumed the traffic wouldn't be a factor. The BE20 took about a 5 mile right base into Runway 30L. We had 2 departures that came off that were in confliction with the arrival of three Air Carriers was the second departure and as it turned out; wasn't a factor; just too close for comfort. The B737 departing Runway 1R at LAS was instantly head on with the BE20. Traffic was called. Our departure; the B737; was too low to vector due to MVA's. There may have been divergence; once TMU called VGT and asked them to tighten up the base for the BE20. Nellis needs to keep the VGT IFR arrivals much tighter into the airport. If they aren't doing this; the DAG sector who takes the point out needs to point out the traffic to affected sectors; or initiate a Call for Release (CFR).
Data retrieved from NASA's ASRS site as of April 2012 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.