 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZNY controller described an airspace incursion claiming that the tmu failed to correct a bad routing that led to the event.
| Attributes | |
| ACN | 1045333 |
| Time | |
| Date | 201210 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZNY.ARTCC |
| State Reference | NY |
| Aircraft 1 | |
| Make Model Name | Challenger Jet Undifferentiated or Other Model |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Other / Unknown Deviation - Track / Heading All Types |
Narrative:
Due to a hurricane approaching; rides in the local area were bad. An earlier report of severe turbulence at FL320 was reported approximately 45 minutes prior to me assuming the sector; so I made sure I issued advisories to all aircraft. My workload increased due to more time spent on the frequency. I received a call from sector 10 asking if I noticed the routing on a challenger. Initially I didn't know who they were talking about. He explained the aircraft was direct a fix I've never heard of. I told him I had no idea what he was talking about. After reviewing the situation I realized that the challenger had a bad routing that was not corrected by tmu. The aircraft made a right turn much earlier than anticipated and entered sector 73's airspace without any coordination from me. I do not know if sector 10 caught the bad routing prior to him entering sector 73's airspace. For years we have been complaining that tmu does a less than satisfactory job of catching bad routes out of new york center. A study was done and concluded there was a problem. The report was given to one of the stmc's in tmu. A study was done by tmu and they determined there was such a minuscule number of bad routes no action would be needed.
Original NASA ASRS Text
Title: ZNY Controller described an airspace incursion claiming that the TMU failed to correct a bad routing that led to the event.
Narrative: Due to a hurricane approaching; rides in the local area were bad. An earlier report of severe turbulence at FL320 was reported approximately 45 minutes prior to me assuming the sector; so I made sure I issued advisories to all aircraft. My workload increased due to more time spent on the frequency. I received a call from Sector 10 asking if I noticed the routing on a Challenger. Initially I didn't know who they were talking about. He explained the aircraft was direct a fix I've never heard of. I told him I had no idea what he was talking about. After reviewing the situation I realized that the Challenger had a bad routing that was not corrected by TMU. The aircraft made a right turn much earlier than anticipated and entered Sector 73's airspace without any coordination from me. I do not know if Sector 10 caught the bad routing prior to him entering Sector 73's airspace. For years we have been complaining that TMU does a less than satisfactory job of catching bad routes out of New York Center. A study was done and concluded there was a problem. The report was given to one of the STMC's in TMU. A study was done by TMU and they determined there was such a minuscule number of bad routes no action would be needed.
Data retrieved from NASA's ASRS site as of July 2013 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.