 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
L30 departure controller reports noticing a departing BE400 well below the required altitude for terrain separation and the HOOVR3 SID restrictions. The foreign pilot had trouble switching to the correct departure control frequency.
| Attributes | |
| ACN | 1147261 |
| Time | |
| Date | 201402 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | L30.TRACON |
| State Reference | NV |
| Aircraft 1 | |
| Make Model Name | Beechjet 400 |
| Flight Phase | Initial Climb |
| Route In Use | SID HOOVR3 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Departure |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 38 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
I was relieving the developmental and instructor on dag. During the briefing; a BE400 reports on frequency; the developmental advises the pilot to contact departure on 133.95 which is the correct and published departure control frequency. I took the sector; signed-on; and started to adjust my radar scope when the BE400 asks for the departure frequency again. I displayed the aircraft because it wasn't on my tag and had only a limited data block; told the mead controller that I still had him on frequency and requested control. I then climbed the BE400 to 19;000 ft and turned him to heading 100 away from natcf's [nellis] airspace. I then noticed how low he was and advised the pilot to climb immediately for terrain. I then radar identified him; turned him back on course; and advised him to contact ZLA. The pilot did not appear to comply with the published HOOVR3 minimum obstacle climb rate of 328 ft per NM to 5;000 ft. I recommend the departure frequencies be highlighted and clarified on all las vegas dp's; because this wrong frequency issue happens frequently even with us registered aircraft; yet alone foreign ones.
Original NASA ASRS Text
Title: L30 Departure Controller reports noticing a departing BE400 well below the required altitude for terrain separation and the HOOVR3 SID restrictions. The foreign pilot had trouble switching to the correct departure control frequency.
Narrative: I was relieving the Developmental and Instructor on DAG. During the briefing; a BE400 reports on frequency; the Developmental advises the pilot to contact Departure on 133.95 which is the correct and published departure control frequency. I took the sector; signed-on; and started to adjust my RADAR scope when the BE400 asks for the departure frequency again. I displayed the aircraft because it wasn't on my tag and had only a limited data block; told the MEAD Controller that I still had him on frequency and requested control. I then climbed the BE400 to 19;000 FT and turned him to heading 100 away from NATCF's [Nellis] airspace. I then noticed how low he was and advised the pilot to climb immediately for terrain. I then RADAR identified him; turned him back on course; and advised him to contact ZLA. The pilot did not appear to comply with the published HOOVR3 minimum obstacle climb rate of 328 FT per NM to 5;000 FT. I recommend the Departure frequencies be highlighted and clarified on all Las Vegas DP's; because this wrong frequency issue happens frequently even with U.S. registered aircraft; yet alone foreign ones.
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.