37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1063767 |
Time | |
Date | 201301 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZID.ARTCC |
State Reference | IN |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Air carrier X was enroute from dca to mci. The filed route was: dca..ldn.J134.stl..mcm.BQS4.mci air carrier X was cleared via verbal clearance at dca with a pdr: ldn.J134.hnn air carrier X questioned clearance delivery about the route after hnn; whether 'it was still stl or if it was hnn to mcm.' clearance delivery advised that after hnn it was 'back to the airway J34 stl.' air carrier X acknowledged. At hnn; air carrier X turned off the route and preceded direct stl. When questioned; air carrier X said that dca changed his route and that he even questioned it to make sure it wasn't 'skipping an air route or stl'; and claimed that he was cleared after hnn direct stl. At ZID; we are seeing this as a frequent and recurring problem with departures from the dc metro area. For several years; this has been an issue (pilots skipping fixes after hitting a point on a pdr) along J134. I previously suspected that this was either an FMS data base/programming problem; or a pilot knowledge/complacency issue. After hearing the question at clearance delivery followed by still more confusion; I believe that this is a pilot knowledge/compliance issue. The csa 'qa' staff is either unwilling or unable to conduct a thorough examination of this issue. Intended or not; the appearance is that if there is no 'paint scraping' that they don't intend to do anything. There have been countless similar occurrences reported via the mor process. The mors are closed without the benefit of a factual investigation. Recommendations include: eliminating pdrs when the filed route matches the pdr; or nearly matches for functional purposes. I previously made the recommendation to discontinue the pre departure clearance program and revert to verbal clearances. This incident seems to indicate that some pilots do not even understand the verbal clearance. Add additional route elements to the portion of the clearance issued with the pdr. Teach the users how to read and interpret the route segments as they apply to 'as filed.' require air carriers to brief all flight crews on a recurring basis. Publish via aim and other appropriate publications.
Original NASA ASRS Text
Title: ZID Controller described a course deviation by an Air Carrier flying from DCA to MCI listing PDR vs. file route differences along with 'route' interpretation issues as causal factors.
Narrative: Air Carrier X was enroute from DCA to MCI. The filed route was: DCA..LDN.J134.STL..MCM.BQS4.MCI Air Carrier X was cleared via verbal clearance at DCA with a PDR: LDN.J134.HNN Air Carrier X questioned Clearance Delivery about the route after HNN; whether 'it was still STL or if it was HNN to MCM.' Clearance Delivery advised that after HNN it was 'back to the airway J34 STL.' Air Carrier X acknowledged. At HNN; Air Carrier X turned off the route and preceded direct STL. When questioned; Air Carrier X said that DCA changed his route and that he even questioned it to make sure it wasn't 'skipping an air route or STL'; and claimed that he was cleared after HNN direct STL. At ZID; we are seeing this as a frequent and recurring problem with departures from the DC metro area. For several years; this has been an issue (pilots skipping fixes after hitting a point on a PDR) along J134. I previously suspected that this was either an FMS data base/programming problem; or a pilot knowledge/complacency issue. After hearing the question at Clearance Delivery followed by still more confusion; I believe that this is a pilot knowledge/compliance issue. The CSA 'QA' staff is either unwilling or unable to conduct a thorough examination of this issue. Intended or not; the appearance is that if there is no 'paint scraping' that they don't intend to do anything. There have been countless similar occurrences reported via the MOR process. The MORs are closed without the benefit of a factual investigation. Recommendations include: Eliminating PDRs when the filed route matches the PDR; or nearly matches for functional purposes. I previously made the recommendation to discontinue the PDC program and revert to verbal clearances. This incident seems to indicate that some pilots do not even understand the verbal clearance. Add additional route elements to the portion of the clearance issued with the PDR. Teach the users how to read and interpret the route segments as they apply to 'as filed.' Require air carriers to brief all flight crews on a recurring basis. Publish via AIM and other appropriate publications.
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.