37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 836100 |
Time | |
Date | 200905 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | CLE.Airport |
State Reference | OH |
Aircraft 1 | |
Make Model Name | A319 |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Pilot Not Flying |
Experience | Flight Crew Last 90 Days 210 Flight Crew Total 12500 Flight Crew Type 6900 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
FMGC programming issue. Filed and cleared via pre departure clearance for AMRST2 departure from cle runway 6R. Loaded AMRST2 departure; vwv transition. The FMGC deleted the 1500 ft point and inserted huddz intersection as the next fix. The published departure says to fly assigned heading for vectors; then expect 'vectors to intercept djb R-265 to amrst.' if we had not referenced the published departure; and followed the FMGC as loaded; we would have made an immediate left turn to huddz. The published departure starts at djb; with a route segment to huddz; then on to amrst. We tried entering runway 10 with the AMRST2/vwv; and the FMGC did the same thing -- deleted the 1500 ft point and linked the departure end of the runway to huddz as the next point. This needs to be fixed soon; or someone is going to trust the box and make a big mistake that may lead to a midair collision.
Original NASA ASRS Text
Title: A319 pilot reports the FMGC improperly displays and navigated the AMRST2 SID from CLE.
Narrative: FMGC programming issue. Filed and cleared via PDC for AMRST2 departure from CLE Runway 6R. Loaded AMRST2 departure; VWV transition. The FMGC deleted the 1500 FT point and inserted HUDDZ intersection as the next fix. The published departure says to fly assigned heading for vectors; then expect 'vectors to intercept DJB R-265 to AMRST.' If we had not referenced the published departure; and followed the FMGC as loaded; we would have made an immediate left turn to HUDDZ. The published departure starts at DJB; with a route segment to HUDDZ; then on to AMRST. We tried entering Runway 10 with the AMRST2/VWV; and the FMGC did the same thing -- deleted the 1500 FT point and linked the departure end of the runway to HUDDZ as the next point. This needs to be fixed soon; or someone is going to trust the box and make a big mistake that may lead to a midair collision.
Data retrieved from NASA's ASRS site as of April 2012 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.