 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Emb-175 captain reported that the company filed route once again did not match the route on file with ATC.
| Attributes | |
| ACN | 1581931 |
| Time | |
| Date | 201809 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 170/175 ER/LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Parked |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Fuel Issue |
Narrative:
This is a continuing issue and problem with policy and procedures at [this company]. When we were given our clearance from ZZZ; we were given [departure clearance and transition] as filed. However [one of this fixes] was not on the flight plan on our release. After questioning ATC and having a discussion with them; the ATC strip filed by the company is not the route that they put on the release. ATC then notified us this is again happening on a continuing basis causing route issues and possible conflicts. We agreed to take a full route clearance which did not match the release at all. The release had [route X] the ATC strip was [route Y]. The fuel was miscalculated at that point for the route on the release not on the ATC strip. Due to a maintenance swap we had enough fuel; only because it was fueled for a different segment. I contacted dispatch via ACARS with no response on why this is not only happening but accepted again. If we would have taken the as filed we would have been severely off course from what ATC had assigned. On the way we were given direct ZZZZ1 intersection. When we made the turn ATC started asking us where we were going. We stated direct to ZZZZ1 intersection; but in reality we were turning completely away from ZZZZ1 intersection. We ended up getting vectors from ATC to avoid military airspace. Upon further investigation it appears ZZZZ1 intersection is not in the database and at some point someone created an incorrect waypoint named ZZZZ1 intersection around 100 miles away from where ZZZZ1 intersection really is.[suggest] changes need to happen to be sure that the dispatch release and the ATC strip match. This is an issue that keeps popping up every few months and can cause serious complications to the pilots and ATC. Database issues keep happening and must have resolution along with training on manually created waypoints.
Original NASA ASRS Text
Title: EMB-175 Captain reported that the company filed route once again did not match the route on file with ATC.
Narrative: This is a continuing issue and problem with policy and procedures at [this company]. When we were given our clearance from ZZZ; we were given [Departure clearance and transition] As Filed. However [one of this fixes] was not on the flight plan on our release. After questioning ATC and having a discussion with them; the ATC strip filed by the company is not the route that they put on the release. ATC then notified us this is again happening on a continuing basis causing route issues and possible conflicts. We agreed to take a full route clearance which did not match the release at all. The release had [Route X] the ATC strip was [Route Y]. The Fuel was miscalculated at that point for the route on the release not on the ATC strip. Due to a maintenance swap we had enough fuel; only because it was fueled for a different segment. I contacted dispatch via ACARS with no response on why this is not only happening but accepted again. If we would have taken the As Filed we would have been severely off course from what ATC had assigned. On the way we were given direct ZZZZ1 intersection. When we made the turn ATC started asking us where we were going. We stated direct to ZZZZ1 intersection; but in reality we were turning completely away from ZZZZ1 intersection. We ended up getting vectors from ATC to avoid military airspace. Upon further investigation it appears ZZZZ1 intersection is not in the database and at some point someone created an incorrect waypoint named ZZZZ1 intersection around 100 miles away from where ZZZZ1 intersection really is.[Suggest] changes need to happen to be sure that the dispatch release and the ATC strip match. This is an issue that keeps popping up every few months and can cause serious complications to the pilots and ATC. Database issues keep happening and must have resolution along with training on manually created waypoints.
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.