 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot reports of incorrect routing for two airports pairs and wanted to make others aware of the problem.
| Attributes | |
| ACN | 1182748 |
| Time | |
| Date | 201406 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | K90.TRACON |
| State Reference | MA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 91 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
We were to operate a ferry flight from ack to avp. The clearance received from kack ATCT was an 'as filled' clearance. The filed routing was dct cmk dct huo dct. Upon departure cape approach assigned us a northerly heading direct lfv when able. We mentioned that lfv was not on our filled routing. Cape approach queried us which clearance we received. Once informed of the 'as filled' clearance; cape approach gave us a new heading and a handoff to ZBW; I believe it was ZBW center; but not sure whether it was center or approach -- and to expect a re-route from the next controller. Upon change of frequency we received a re-route that added about 50 NM to the routing; dct pvd dct center dct dny dct laayk dct. Upon query; ZBW clarified that the filled routing was an invalid routing for these two airport pairs; and that the center failed to notify ack ATCT. I wanted to make sure the company reviews the northeast routings for accuracy and validity; the next routing wasn't valid either on the avp to gon airport pair. Secondly; I wanted to point out an apparent break in communications between the ARTCC and the ATCT in this case. It may have been a one time event; but if not; I wanted to point a potential safety problem.
Original NASA ASRS Text
Title: Pilot reports of incorrect routing for two airports pairs and wanted to make others aware of the problem.
Narrative: We were to operate a ferry flight from ACK to AVP. The clearance received from KACK ATCT was an 'As Filled' clearance. The filed routing was DCT CMK DCT HUO DCT. Upon departure Cape Approach assigned us a northerly heading direct LFV when able. We mentioned that LFV was not on our filled routing. Cape Approach queried us which clearance we received. Once informed of the 'As Filled' clearance; Cape Approach gave us a new heading and a handoff to ZBW; I believe it was ZBW Center; but not sure whether it was Center or Approach -- and to expect a re-route from the next Controller. Upon change of frequency we received a re-route that added about 50 NM to the routing; DCT PVD DCT CTR DCT DNY DCT LAAYK DCT. Upon query; ZBW clarified that the filled routing was an invalid routing for these two airport pairs; and that the Center failed to notify ACK ATCT. I wanted to make sure the Company reviews the Northeast routings for accuracy and validity; the next routing wasn't valid either on the AVP to GON airport pair. Secondly; I wanted to point out an apparent break in communications between the ARTCC and the ATCT in this case. It may have been a one time event; but if not; I wanted to point a potential safety problem.
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.