37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1325968 |
Time | |
Date | 201601 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZMA.ARTCC |
State Reference | FL |
Aircraft 1 | |
Make Model Name | Citation V/Ultra/Encore (C560) |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Oceanic |
Flight Plan | IFR |
Person 1 | |
Function | Instructor Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 23.0 |
Person 2 | |
Function | Trainee Enroute |
Qualification | Air Traffic Control Developmental |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I was providing OJT instruction to a trainee. He was coordinating 4 or 5 estimates to the adjacent ARTCC. The adjacent ARTCC read back the first 4 estimates correctly. When we were coordinating aircraft X; we coordinated the time and altitude on the strip. The adjacent center controller hesitated for a few seconds on this particular estimate; and read back a different time. I missed the readback. I do not know why I missed it.in other ATC software flight plan processing; if you try to enter an estimate into the system that was 5 hours in the past; you will get a reject message. Apparently atop (oceanic ATC flight plan processing) does not do this. There should be a logic check about what kind of times they can enter into the system to prevent them from entering wildly inaccurate times. That would help. On my part; I should not place too much faith in a trainee; ever. Complacency happens to instructors.
Original NASA ASRS Text
Title: A ZMA Controller trainee passed flight estimates to another facility. The receiving facility read back one of the estimates incorrectly and it was not caught by the trainee or the instructor.
Narrative: I was providing OJT Instruction to a trainee. He was coordinating 4 or 5 estimates to the adjacent ARTCC. The adjacent ARTCC read back the first 4 estimates correctly. When we were coordinating Aircraft X; we coordinated the time and altitude on the strip. The adjacent Center controller hesitated for a few seconds on this particular estimate; and read back a different time. I missed the readback. I do not know why I missed it.In other ATC software flight plan processing; if you try to enter an estimate into the system that was 5 hours in the past; you will get a reject message. Apparently ATOP (Oceanic ATC flight plan processing) does not do this. There should be a logic check about what kind of times they can enter into the system to prevent them from entering wildly inaccurate times. That would help. On my part; I should not place too much faith in a trainee; ever. Complacency happens to Instructors.
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.