 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Tri-cities regional radar controller reported not complying with a directive that no longer allows the departure controller to vector aircraft off an airport until they reach the minimum vectoring altitude.
| Attributes | |
| ACN | 1447840 |
| Time | |
| Date | 201705 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | TRI.Tower |
| State Reference | TN |
| Aircraft 1 | |
| Make Model Name | Light Transport |
| Flight Phase | Initial Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Departure |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 18 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
For years as a radar controller at several radar facilities I have been able to radar identify departures and then turn them on course when departing the primary airport because the departure areas were flight checked and charted; etc.. Last week we received a directive that evolved into instruction that we could not do so until the departure had met the MVA. This session was my first working radar since all of that occurred. As aircraft X departed he checked on; I radar identified them and; as I have done a zillion times; said 'turn right on course' while the plane was still 900FT below the MVA (and above the depicted obstruction in the area). I immediately realized what I had done and corrected my instruction to comply with the MVA. But the tape recorded me un-keying the headset for an instant so I guess that counts as an error.I reported it to my front line manager (flm) and then checked the tapes to hear if I had; indeed; un-keyed. I had.go back to what has been safe [in the past] and allow us to issue headings/vectors on contact to departures off the primary airport.
Original NASA ASRS Text
Title: Tri-Cities Regional Radar Controller reported not complying with a directive that no longer allows the departure Controller to vector aircraft off an airport until they reach the Minimum Vectoring Altitude.
Narrative: For years as a radar controller at several radar facilities I have been able to radar identify departures and then turn them on course when departing the primary airport because the departure areas were flight checked and charted; etc.. Last week we received a directive that evolved into instruction that we could not do so until the departure had met the MVA. This session was my first working radar since all of that occurred. As Aircraft X departed he checked on; I radar identified them and; as I have done a zillion times; said 'turn right on course' while the plane was still 900FT below the MVA (and above the depicted obstruction in the area). I immediately realized what I had done and corrected my instruction to comply with the MVA. But the tape recorded me un-keying the headset for an instant so I guess that counts as an error.I reported it to my Front Line Manager (FLM) and then checked the tapes to hear if I had; indeed; un-keyed. I had.Go back to what has been safe [in the past] and allow us to issue headings/vectors on contact to departures off the primary airport.
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.