37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1119421 |
Time | |
Date | 201209 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.TRACON |
State Reference | US |
Aircraft 1 | |
Make Model Name | Regional Jet 700 ER/LR (CRJ700) |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Saab 340 Undifferentiated |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
While I was conducting training on the position; my developmental was vectoring a crj-700 at 8;000 for sequencing to the [STAR]. There was a saab 340 stacked underneath the crj-700 at 7;000. A pilatus pc-12 was an overflight at 8;000 going direct. My developmental stopped the crj-700 at 8;000 from the [STAR] profile descent reference the saab 340 at 7;000; but got caught up with issuing speed control on arrivals being switched to final; and forgot to turn the crj-700. I let the situation go too long before instructing the developmental to take action. Recommendation; better control of the position. The developmental is in the late stages of training on this position; working on extended hours and I didn't want to break in. I should have made a mention of the developing situation sooner in a more; 'don't forget about [the pc-12] out there at 8; 000;' providing information only; and still allowing time to take action. It is a tough line when letting a developmental work through tough traffic situations. You don't want to override them; or say something too soon. You want them to recognize the traffic. Being overbearing on the position can work to your disadvantage. But being extremely vigilant is my responsibility and taking action to ensure separation is being maintained is my job. I will be more pro-active in pointing out traffic to the developmental and taking action sooner.
Original NASA ASRS Text
Title: TRACON Controller providing OJT was late in issuing guidance to the Developmental resulting in a loss of separation.
Narrative: While I was conducting training on the position; my Developmental was vectoring a CRJ-700 at 8;000 for sequencing to the [STAR]. There was a Saab 340 stacked underneath the CRJ-700 at 7;000. A Pilatus PC-12 was an overflight at 8;000 going direct. My Developmental stopped the CRJ-700 at 8;000 from the [STAR] profile descent reference the Saab 340 at 7;000; but got caught up with issuing speed control on arrivals being switched to final; and forgot to turn the CRJ-700. I let the situation go too long before instructing the Developmental to take action. Recommendation; better control of the position. The Developmental is in the late stages of training on this position; working on extended hours and I didn't want to break in. I should have made a mention of the developing situation sooner in a more; 'don't forget about [the PC-12] out there at 8; 000;' providing information only; and still allowing time to take action. It is a tough line when letting a developmental work through tough traffic situations. You don't want to override them; or say something too soon. You want them to recognize the traffic. Being overbearing on the position can work to your disadvantage. But being extremely vigilant is my responsibility and taking action to ensure separation is being maintained is my job. I will be more pro-active in pointing out traffic to the Developmental and taking action sooner.
Data retrieved from NASA's ASRS site as of July 2013 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.