 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An A320 captain reported that the aircraft's FMGC database fails to comply with the published 228 degree heading outbound from lbv on the shfty RNAV STAR to runway 24 at rsw. Reporter advised when the RNAV(GPS) runway 24 approach is selected it reprograms the 'heading and associated route discontinuity' prior to rodde waypoint on the approach to a continuous leg; sans discontinuity.
| Attributes | |
| ACN | 1149739 |
| Time | |
| Date | 201402 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | RSW.Airport |
| State Reference | FL |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | A320 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent Initial Approach |
| Route In Use | STAR SHFTY TWO |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Navigation Database |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
On the shfty two arrival into rsw the mcdu is wrong! It appears to be auto sequencing; which is something it should not do. Also; I believe this has happened in atl as well if I remember the last union update. According to the arrival after reaching lbv you are supposed to take a 228 heading for runway 24 (see note 2 on the arrival). If you put this arrival in and then put the RNAV 24 runway in; the box puts in lbv direct rodde; which is the IAF for the approach. But again this is not what you are cleared; you are supposed to take the 228 heading that is on the arrival. We caught this during our descent brief and asked ATC what they wanted; they concurred that after arriving at lbv they expect us to be on the 228 heading not direct rodde. I do not know why the box is auto sequencing things now; but it is not right; please put an alert out to the crews about this arrival.
Original NASA ASRS Text
Title: An A320 Captain reported that the aircraft's FMGC database fails to comply with the published 228 degree heading outbound from LBV on the SHFTY RNAV STAR to Runway 24 at RSW. Reporter advised when the RNAV(GPS) RWY 24 approach is selected it reprograms the 'heading and associated route discontinuity' prior to RODDE waypoint on the approach to a continuous leg; sans discontinuity.
Narrative: On the SHFTY TWO arrival into RSW the MCDU is wrong! It appears to be auto sequencing; which is something it should not do. Also; I believe this has happened in ATL as well if I remember the last Union update. According to the arrival after reaching LBV you are supposed to take a 228 heading for Runway 24 (see note 2 on the arrival). If you put this arrival in and then put the RNAV 24 runway in; the box puts in LBV direct RODDE; which is the IAF for the approach. But again this is not what you are cleared; you are supposed to take the 228 heading that is on the arrival. We caught this during our descent brief and asked ATC what they wanted; they concurred that after arriving at LBV they expect us to be on the 228 heading not direct RODDE. I do not know why the box is auto sequencing things now; but it is not right; please put an alert out to the crews about this arrival.
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.