 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZNY controller reported recurring unsafe events within an oceanic sector.
| Attributes | |
| ACN | 1566305 |
| Time | |
| Date | 201807 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZNY.ARTCC |
| State Reference | NY |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| 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 Time Certified In Pos 1 (yrs) 32 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Working D87 nonradar oceanic sector. Noticed a limited data radar target approximately 30 NM inside my airspace. No ocean 21 data block...no protected profile...no coordination. Called R86 atlantic sector to inquire; if they knew who it was. Responded aircraft X deviating south of course. The aircraft was routed via slatn inbound to R86/R65. Unsafe situation; aircraft in nonradar airspace not probed for separation and no flight information in the system...big blue sky theory...how many more times is this going to happen before something serious happens? Yes it's happened before. ZNY management was notified of the incident and as far as I know the mandatory occurrence report was filed; but you never know. Separation was not lost because I was able to apply radar separation between all aircraft at FL360. Its a simple fix no westbound traffic routed via slatn....use joboc to the north or marig to the south. Deviations can not exceed 60NM left of track into joboc; otherwise reroute to marig. No restriction on deviation into marig....simple.
Original NASA ASRS Text
Title: ZNY Controller reported recurring unsafe events within an oceanic sector.
Narrative: Working D87 nonradar oceanic sector. Noticed a limited data radar target approximately 30 NM inside my airspace. No Ocean 21 data block...NO PROTECTED PROFILE...NO COORDINATION. Called R86 ATLANTIC Sector to inquire; if they knew who it was. Responded Aircraft X deviating south of course. The aircraft was routed via SLATN inbound to R86/R65. UNSAFE situation; aircraft in nonradar airspace not probed for separation and no flight information in the system...Big Blue Sky Theory...How many more times is this going to happen before something serious happens? Yes it's happened before. ZNY management was notified of the incident and as far as I know the Mandatory Occurrence Report was filed; but you never know. Separation was not lost because I was able to apply radar separation between all aircraft at FL360. Its a simple fix NO WESTBOUND traffic routed via SLATN....USE JOBOC to the north or MARIG to the south. Deviations can not exceed 60NM left of track into JOBOC; otherwise reroute to MARIG. No restriction on deviation into MARIG....SIMPLE.
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.