 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Geg TRACON controller reported not noticing an aircraft had descended below the glidepath while performing on the job training.
| Attributes | |
| ACN | 1735314 |
| Time | |
| Date | 202003 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | GEG.TRACON |
| State Reference | WA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | PC-12 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Final Approach |
| Route In Use | Other Instrument Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Route In Use | Vectors |
| Person 1 | |
| Function | Approach Instructor |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Inflight Event / Encounter CFTT / CFIT |
Narrative:
I was providing OJT (on the job training) on west radar and we were in a north flow. Aircraft X came over requesting an RNAV approach into ZZZ and was cleared direct to a zzzzz. Shortly after aircraft X was given the approach clearance and told to cross zzzzz at 5000 ft. The pilot read everything back correctly from the clearance and I observed the pilot crossing zzzzz at the correct altitude. TRACON called to request approval for aircraft Y direct to the field and I think I zoomed my scope out to look at the aircraft. I then turned my attention to aircraft Y and did not scan back to aircraft X before my trainee switched them to the ZZZ tower. Shortly after the frequency change was given another controller said 'I think he too low.' at that point I went back to aircraft X and realized they were at 3500 ft. Descending and needed to be at 3900 ft. On that segment of the approach. I told the trainee to call tower and tell them to issue a low altitude alert. The controller said 'you want me to do it now?' I told them that aircraft X needed to be at 3900 ft. On that segment of the approach. The lowest I observed the aircraft descend to was 3300 ft. On the approach segment before starting their climb back up.I was disappointed in myself for not scanning back and recognizing that aircraft X was low on the approach when they were switched. My trainee is at a stage where I am trying to give him a little more autonomy and help him feel like he has ownership/responsibility for the position. Unfortunately; I let my guard down a little too much and didn't recognize the situation quickly enough. I did feel a little extra tired today and not quite as focused as I usually am.in the future I am going to stay more vigilant no matter what stage the trainee is at. In addition I am also going to hold off on changing the color of the data block to blue until I scan their altitude and give them a frequency change. From a technology standpoint I was disappointed that the low altitude alert did not go off in this situation. The red font with la (low altitude alert) really grabs your attention and I think it would have helped us recognize this situation earlier.
Original NASA ASRS Text
Title: GEG TRACON Controller reported not noticing an aircraft had descended below the glidepath while performing on the job training.
Narrative: I was providing OJT (On the Job Training) on West Radar and we were in a North Flow. Aircraft X came over requesting an RNAV Approach into ZZZ and was cleared direct to a ZZZZZ. Shortly after Aircraft X was given the approach clearance and told to cross ZZZZZ at 5000 ft. The pilot read everything back correctly from the clearance and I observed the pilot crossing ZZZZZ at the correct altitude. TRACON called to request approval for Aircraft Y direct to the field and I think I zoomed my scope out to look at the aircraft. I then turned my attention to Aircraft Y and did not scan back to Aircraft X before my trainee switched them to the ZZZ Tower. Shortly after the frequency change was given another controller said 'I think he too low.' At that point I went back to Aircraft X and realized they were at 3500 ft. descending and needed to be at 3900 ft. on that segment of the approach. I told the trainee to call Tower and tell them to issue a low altitude alert. The controller said 'you want me to do it now?' I told them that Aircraft X needed to be at 3900 ft. on that segment of the approach. The lowest I observed the aircraft descend to was 3300 ft. on the approach segment before starting their climb back up.I was disappointed in myself for not scanning back and recognizing that Aircraft X was low on the approach when they were switched. My trainee is at a stage where I am trying to give him a little more autonomy and help him feel like he has ownership/responsibility for the position. Unfortunately; I let my guard down a little too much and didn't recognize the situation quickly enough. I did feel a little extra tired today and not quite as focused as I usually am.In the future I am going to stay more vigilant no matter what stage the trainee is at. In addition I am also going to hold off on changing the color of the data block to blue until I scan their altitude and give them a frequency change. From a technology standpoint I was disappointed that the Low Altitude Alert did not go off in this situation. The red font with LA (Low Altitude Alert) really grabs your attention and I think it would have helped us recognize this situation earlier.
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.