37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1530116 |
Time | |
Date | 201803 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | L30.TRACON |
State Reference | NV |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Bonanza 33 |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | SID RTTRN3 |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Challenger CL600 |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 2 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Student Flight Crew Private |
Experience | Flight Crew Last 90 Days 20 Flight Crew Total 200 Flight Crew Type 10 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
I was working the departure sectors and released an IFR aircraft off a satellite airport. While aircraft X was departing I was coordinating with center because aircraft Y said he could only operate at 240 knots. When I got off the line I noticed aircraft X had missed the outbound radial on the departure and was operating in an area of higher terrain. I turned the aircraft and issued a low altitude alert. After that was read back I issued the aircraft a climb to 100 feet to allow the aircraft to get out of the higher MVA's (minimum vectoring altitudes) so I could turn the aircraft back to the east. I coordinated with the adjacent approach to maneuver the aircraft on a 080 heading climbing to 10;000 feet. There were a few other thing going on at the time. I was sequencing aircraft via RNAV departures and looked again and aircraft X had turned southeast bound. I questioned the aircraft and then cleared aircraft X direct to las. Meanwhile; aircraft Z departed and was initially given 19;000 feet. I amended the clearance to 10;000 feet thinking I had to miss over flight traffic at 10;500 feet. For whatever reason I thought aircraft X was issued 9;000 feet. By the time I saw the situation there was very little I could do to save the situation. I called traffic and resumed working the remainder of the aircraft. I consider this a lapse and or poor judgment because I deal with these types of situations often. I take full responsibility for the loss.
Original NASA ASRS Text
Title: ATC Controller and GA pilot reported an operation in the wrong direction and below the Minimum Vectoring Altitude; that resulted in a vector in conflict with a departing air carrier.
Narrative: I was working the departure sectors and released an IFR aircraft off a satellite airport. While Aircraft X was departing I was coordinating with Center because Aircraft Y said he could only operate at 240 knots. When I got off the line I noticed Aircraft X had missed the outbound radial on the departure and was operating in an area of higher terrain. I turned the aircraft and issued a low altitude alert. After that was read back I issued the aircraft a climb to 100 feet to allow the aircraft to get out of the higher MVA's (Minimum Vectoring Altitudes) so I could turn the aircraft back to the east. I coordinated with the adjacent Approach to maneuver the aircraft on a 080 heading climbing to 10;000 feet. There were a few other thing going on at the time. I was sequencing aircraft via RNAV departures and looked again and Aircraft X had turned southeast bound. I questioned the aircraft and then cleared Aircraft X direct to LAS. Meanwhile; Aircraft Z departed and was initially given 19;000 feet. I amended the clearance to 10;000 feet thinking I had to miss over flight traffic at 10;500 feet. For whatever reason I thought Aircraft X was issued 9;000 feet. By the time I saw the situation there was very little I could do to save the situation. I called traffic and resumed working the remainder of the aircraft. I consider this a lapse and or poor judgment because I deal with these types of situations often. I take full responsibility for the loss.
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.