 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZNY controller describes a situation where an aircraft shows up on his frequency without his knowledge. The aircraft wasn't handed off or coordinated with N90. Controller had to figure out where aircraft was going and attempt to get it there. Another data tag of the same call sign added to the problem.
| Attributes | |
| ACN | 1263599 |
| Time | |
| Date | 201505 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZNY.ARTCC |
| State Reference | NY |
| Aircraft 1 | |
| Make Model Name | Widebody Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Route In Use | None |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 29 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
Aircraft X departure from jfk climbing to FL120. No handoff from N90; aircraft just showed up on frequency stating direct shipp climbing to FL120. N90 controller made no verbal contact to manually handoff the aircraft or coordinate route. New ATC procedure in effect; no handoff required; route doesn't matter; ensure communication change prior to leaving airspace. There was an associated track; which I slewed up. It was an aircraft X tag with a destination of ZZZ via greki. I was not aware of who had track control. There were multiple flight plans. I asked the supervisor for some help on the H position to fix this situation. Flight time in R66 for this flight is less than 5 minutes. We never did get it fixed. Manually coordinated with R86 with information that the OCEAN21 system had an ICAO flight plan to be utlized for coordination with oceanic sector D87.an error was made somewhere. Don't expect this to be a one time incident; because of the current culture. Procedurally we have taken a step back. Ensuring accuracy of flight data has taken a back seat.
Original NASA ASRS Text
Title: ZNY Controller describes a situation where an aircraft shows up on his frequency without his knowledge. The aircraft wasn't handed off or coordinated with N90. Controller had to figure out where aircraft was going and attempt to get it there. Another data tag of the same call sign added to the problem.
Narrative: Aircraft X departure from JFK climbing to FL120. No handoff from N90; aircraft just showed up on frequency stating direct SHIPP climbing to FL120. N90 controller made no verbal contact to manually handoff the aircraft or coordinate route. New ATC procedure in effect; no handoff required; route doesn't matter; ensure communication change prior to leaving airspace. There was an associated track; which I slewed up. It was an Aircraft X tag with a destination of ZZZ via GREKI. I was not aware of who had track control. There were multiple flight plans. I asked the supervisor for some help on the H position to fix this situation. Flight time in R66 for this flight is less than 5 minutes. We never did get it fixed. Manually coordinated with R86 with information that the OCEAN21 system had an ICAO flight plan to be utlized for coordination with Oceanic sector D87.An error was made somewhere. Don't expect this to be a one time incident; because of the current culture. Procedurally we have taken a step back. Ensuring accuracy of flight data has taken a back seat.
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.