37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1155841 |
Time | |
Date | 201403 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | SBA.TRACON |
State Reference | CA |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
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) 6 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
I was training a cpc it who I thought was further ahead than he really is. Air carrier departed sba heading 140 climbing to 8;000 ft. After many other automation issues; the trainee finally initiated an automated handoff of air carrier to ZLA. We did not end up shipping air carrier until he was leaving 6;800 ft. At the same time we were dealing with a few other coordinations and must have missed the read back of the frequency. I had to prompt the trainee to get a point out with ntd approach because we were going to violate their airspace as the air carrier was level at 8;000 ft. We accomplished the point out but there were no red flags in my mind because when we are late giving a handoff and or frequency change; it is not uncommon to see aircraft fly level for a little while. ZLA called down and asked for communication with the aircraft and to put him on a 020 heading. He reached out to the aircraft several times with no reply. Finally after the air carrier violated W532 which was hot during a live fire exercise (suspended prior to the violation). The aircraft called us for a turn. The trainee just shipped aircarft to center and we failed to issue the heading. I should have been more assertive and not let the trainee go as far as he did.
Original NASA ASRS Text
Title: Developmental did not issue heading as instructed by ARTCC to avoid penetration of Warning Area.
Narrative: I was training a CPC IT who I thought was further ahead than he really is. Air carrier departed SBA heading 140 climbing to 8;000 FT. After many other automation issues; the trainee finally initiated an automated handoff of air carrier to ZLA. We did not end up shipping air carrier until he was leaving 6;800 FT. At the same time we were dealing with a few other coordinations and must have missed the read back of the frequency. I had to prompt the trainee to get a point out with NTD Approach because we were going to violate their airspace as the air carrier was level at 8;000 FT. We accomplished the point out but there were no red flags in my mind because when we are late giving a handoff and or frequency change; it is not uncommon to see aircraft fly level for a little while. ZLA called down and asked for communication with the aircraft and to put him on a 020 heading. He reached out to the aircraft several times with no reply. Finally after the air carrier violated W532 which was hot during a live fire exercise (suspended prior to the violation). The aircraft called us for a turn. The trainee just shipped aircarft to Center and we failed to issue the heading. I should have been more assertive and not let the trainee go as far as he did.
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.