 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A general aviation pilot reported ATC issues prior to release; and then after takeoff from north las vegas airport.
| Attributes | |
| ACN | 1315992 |
| Time | |
| Date | 201512 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | VGT.Airport |
| State Reference | NV |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Aircraft |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Route In Use | SID NOTWN4 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Single Pilot Pilot Flying |
| Qualification | Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Commercial |
| Experience | Flight Crew Last 90 Days 20 Flight Crew Total 5000 Flight Crew Type 700 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
On the VMC day; there was confusion over the SID; the verbal clearance received was the NOTWN4. The clearance showing in the ATC computer was RTTRN2 per flightaware.com (discovered later). I noted that the RTTRN2 SID was not approved for the assigned runway. There was some confusion between las TRACON and vgt tower as the release was delayed to the point that I told the tower I was considering cancelling the IFR clearance and departing VFR west under the bravo. They then said that the release was about ready; I waited. As soon as I departed 30L and contacted departure I received an urgent (ATC voice tension) turn 090 and expedited climb to 7;000 which was my initial altitude assigned. I was just beginning my turn to a track of 313 to ruzco and continued the climb to 7;000 as vectored. One misjudgment on my part was that I was depending on the GPS route to ruzco and had not set the 313 radial off las and the moving map display was set to a larger than optimal range so the track was not very visible. My suggestion would be to change the NOTWN4 for a straight out departure to intercept the 313 off las. RTTRN2 should remain unchanged unless the airspace northeast of vgt could be utilized for the SID from R7; 12R and 12L.
Original NASA ASRS Text
Title: A general aviation pilot reported ATC issues prior to release; and then after takeoff from North Las Vegas airport.
Narrative: On the VMC day; there was confusion over the SID; the verbal clearance received was the NOTWN4. The clearance showing in the ATC computer was RTTRN2 per Flightaware.com (discovered later). I noted that the RTTRN2 SID was not approved for the assigned runway. There was some confusion between LAS TRACON and VGT Tower as the release was delayed to the point that I told the Tower I was considering cancelling the IFR clearance and departing VFR west under the Bravo. They then said that the release was about ready; I waited. As soon as I departed 30L and contacted departure I received an urgent (ATC voice tension) turn 090 and expedited climb to 7;000 which was my initial altitude assigned. I was just beginning my turn to a track of 313 to RUZCO and continued the climb to 7;000 as vectored. One misjudgment on my part was that I was depending on the GPS route to RUZCO and had not set the 313 radial off LAS and the moving map display was set to a larger than optimal range so the track was not very visible. My suggestion would be to change the NOTWN4 for a straight out departure to intercept the 313 off LAS. RTTRN2 should remain unchanged unless the airspace NE of VGT could be utilized for the SID from R7; 12R and 12L.
Data retrieved from NASA's ASRS site 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.