Any Unknown or Unlisted Aircraft Manufacturer
Air Traffic Control Developmental
Communication Breakdown; Confusion; Distraction; Human-Machine Interface
ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Provided Assistance; Air Traffic Control Separated Traffic
ATC Equipment / Nav Facility / Buildings; Procedure
Aircraft operating at flight level 290 and Mach 0.68 was not coordinated by Piarco Center to NY Center. Aircraft entered the NY/Piarco Boundary at 18N050W without coordination. The flight was not protected by Ocean21 non radar because coordination wasn't completed. This became aware to me at the sector when receiving a position report over 18N050W without any flight plan on the aircraft. After calling Piarco Center; working with another Controller at NY; and commercial radio we located the flights current position; altitude and speed. The Carrier was verified inside of our airspace; and that Piarco Center had never coordinated the flight. No loss of separation occurred. Require Piarco ATC to get their automated AIDC system up and running; and become on line with ZNY. With automated ABI messages and the automated passing of flight plans this would never happen. ZNY could receive every flight plan and receive current aircraft data through the same method as we do with Santa Maria ATC (to the east of NY Airspace). Their system needs to get turned on; there is no reason in this day and age why automation; cannot be accomplished between the two facilities. It absolutely promotes a safer operation; and more efficient operation lowering controller workload; and increasing the flying public's safety.
Reporter did not receive flight progress or handoff from a Foreign Center; causing an airspace violation.