37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1411263 |
Time | |
Date | 201612 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZNY.ARTCC |
State Reference | NY |
Aircraft 1 | |
Make Model Name | Widebody Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Radar 12 |
Person 2 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
I just sat down at the right side for three sectors. The previous controller was dealing with two aerial refueling-777 refueling blocks and must have missed the aircraft at FL340 approaching the fir. The aircraft did not check on as expected. Neither controller (the right or the RA) noticed it and it entered center without coordination. The center called us inquiring about the aircraft as soon as I sat down. My RA spoke with them and told them they thought it was an air carrier based on our flight strips. At that time boston center called also and I picked up. They asked who it was and I said we believe it was aircraft X; we weren't talking to him yet and I apologized on behalf of last controller. Then; my RA called arinc and had them call the airplane to give them boston's frequency. We observed the code change on the aircraft when boston got in contact with them.I am not sure why the aircraft did not get the comm change via controller pilot data link communications (cpdlc) as expected. I am not totally sure how the previous controllers missed it other than being preoccupied with the other aircraft.
Original NASA ASRS Text
Title: A Controller and flight crew reported the aircraft entered ZBW airspace on an oceanic route without contacting ATC prior to entry. ATC failed to issue the VHF frequency to the crew earlier.
Narrative: I just sat down at the R side for three sectors. The previous controller was dealing with two Aerial Refueling-777 refueling blocks and must have missed the aircraft at FL340 approaching the FIR. The aircraft did not check on as expected. Neither controller (the R or the RA) noticed it and it entered center without coordination. The Center called us inquiring about the aircraft as soon as I sat down. My RA spoke with them and told them they thought it was an air carrier based on our flight strips. At that time Boston center called also and I picked up. They asked who it was and I said we believe it was Aircraft X; we weren't talking to him yet and I apologized on behalf of last controller. Then; my RA called ARINC and had them call the airplane to give them Boston's frequency. We observed the code change on the aircraft when Boston got in contact with them.I am not sure why the aircraft did not get the comm change via Controller Pilot Data Link Communications (CPDLC) as expected. I am not totally sure how the previous controllers missed it other than being preoccupied with the other aircraft.
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.