37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1628806 |
Time | |
Date | 201903 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZLA.ARTCC |
State Reference | CA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Learjet 35 |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Supervisor / CIC |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 14 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X departure from runway 3 at vcv. Departure release included right turn direct fix on flight plan. This turn took the aircraft toward highest terrain in immediate vicinity which is displayed on radar.the incident occurred a week ago. A controller at that tower reported it to an flm at my facility 2 days later. That flm (front line manager) filed a report two days ago with incorrect time. I was made aware of the incident via report but saw nothing when I reviewed. Later; I was told the correct time from our staff support specialist and reviewed the incident. It does look like a safety issue but I didn't become aware of it for a week after the event. The ATCT controller kept the information for 2 days. The flm here kept the information for [a few more] days. Timely reporting not accomplished. I will inform the controller of the event and provide opportunity to report when he reports for duty today. The flm from our facility has already prepared a briefing package for correcting the safety event in the future; but my employee hasn't even been informed yet. I feel this is being treated in a punitive rather than safety enhancing manner. This is not a just culture.report safety events as soon as practical rather than conducting detailed analysis and corrective action plan prior to reporting the event.
Original NASA ASRS Text
Title: ZLA ARTCC Front Line Manager reported that an aircraft was given a heading which took it towards high terrain; and also reported that the FLM was unaware of the incident until a week later.
Narrative: Aircraft X departure from Runway 3 at VCV. Departure release included right turn direct fix on flight plan. This turn took the aircraft toward highest terrain in immediate vicinity which is displayed on radar.The incident occurred a week ago. A Controller at that Tower reported it to an FLM at my facility 2 days later. That FLM (Front Line Manager) filed a report two days ago with incorrect time. I was made aware of the incident via report but saw nothing when I reviewed. Later; I was told the correct time from our Staff Support Specialist and reviewed the incident. It does look like a safety issue but I didn't become aware of it for a week after the event. The ATCT controller kept the information for 2 days. The FLM here kept the information for [a few more] days. Timely reporting not accomplished. I will inform the Controller of the event and provide opportunity to report when he reports for duty today. The FLM from our facility has already prepared a briefing package for correcting the safety event in the future; but my employee hasn't even been informed yet. I feel this is being treated in a punitive rather than safety enhancing manner. This is not a just culture.Report safety events as soon as practical rather than conducting detailed analysis and corrective action plan prior to reporting the event.
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.