 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An A319 first officer expressed concern that it is difficult to reconcile the pre departure clearance delivered filed route with company downloaded FMGC route because the formats are different and; even if identical; may require point by point comparisons with airways charts to assure they are the same.
| Attributes | |
| ACN | 1116552 |
| Time | |
| Date | 201309 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | A319 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Other Parked pre-departure |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer |
| Experience | Flight Crew Last 90 Days 150 Flight Crew Total 12000 Flight Crew Type 1900 |
| Events | |
| Anomaly | Other Unwanted situation |
Narrative:
Recently the pilots have been made very aware of the issue of missing revised segments to the ATC cleared routes. This was such an issue; that the format of the pre departure clearance has been changed to highlight the revised segment section of the clearance.now there is a new threat to preflighting and programming the fmgcs. The new flight planning system downloads the filed route via data-link directly to the FMGC. The pilots are to insert the departure and arrival runways with the appropriate SID; STAR and transitions; and to then verify the route against the ofp and the pre departure clearance. The danger we are now encountering is that the documents (ofp and pre departure clearance) we use to verify the proper programming are sources of conflicting data.our ofp filed route was:PATSS3 patss dct nelie FLOSI2The pre departure clearance filed route was:PATSS3 patss nelie ign IGN265 flosi FLOSI2Examination of the ofp waypoint by waypoint; as if this was a class ii overwater flight; proved that the ofp and pre departure clearance were in agreement; however; this is not the normal SOP for verifying FMGC programming.--the ATC filing section of the ofp must be complete; as many times the pre departure clearance filed route will be greatly abbreviated by inserting ''''''''' then destination; leaving the pilots with no complete source document to use to verify the programmed route of flight.--these inconsistencies are a source of confusion and will lead to programming errors; loss of aircraft separation in flight; and certificate actions against pilots.
Original NASA ASRS Text
Title: An A319 First Officer expressed concern that it is difficult to reconcile the PDC delivered filed route with company downloaded FMGC route because the formats are different and; even if identical; may require point by point comparisons with airways charts to assure they are the same.
Narrative: Recently the pilots have been made very aware of the issue of missing revised segments to the ATC cleared routes. This was such an issue; that the format of the PDC has been changed to highlight the revised segment section of the clearance.Now there is a new threat to preflighting and programming the FMGCs. The new flight planning system downloads the filed route via data-link directly to the FMGC. The pilots are to insert the departure and arrival runways with the appropriate SID; STAR and transitions; and to then verify the route against the OFP and the PDC. The danger we are now encountering is that the documents (OFP and PDC) we use to verify the proper programming are sources of conflicting data.Our OFP filed route was:PATSS3 PATSS DCT NELIE FLOSI2The PDC filed route was:PATSS3 PATSS NELIE IGN IGN265 FLOSI FLOSI2Examination of the OFP waypoint by waypoint; as if this was a Class II overwater flight; proved that the OFP and PDC were in agreement; however; this is not the normal SOP for verifying FMGC programming.--The ATC filing section of the OFP must be complete; as many times the PDC filed route will be greatly abbreviated by inserting ''''''''' then destination; leaving the pilots with no complete source document to use to verify the programmed route of flight.--These inconsistencies are a source of confusion and will lead to programming errors; loss of aircraft separation in flight; and certificate actions against pilots.
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.