37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1442438 |
Time | |
Date | 201704 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | BWI.Airport |
State Reference | MD |
Environment | |
Flight Conditions | Mixed |
Light | Night |
Aircraft 1 | |
Make Model Name | A321 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | STAR RAVNN6 |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe |
Narrative:
We were cleared to descend via the ravnn 6 arrival and I had read the warning from the union about problems on this arrival. The aircraft reached FL230 at fzeek. Constraint was displayed in the FMA indicating that the aircraft would stop descent and hold FL230. When the aircraft reached 200 ft above fzeek; the autopilot reverted from managed descent mode to basic mode vertical speed. I quickly mashed the altitude button; forcing the aircraft to level off. The [FMC] shows that the aircraft will join the descent profile just before reaching fzeek where a constraint altitude is set up. It shows the aircraft will continue the descent passing whhte. I think there must be a problem in the jeppesen coding of the arrival; but this reminds me of other reports I wrote concerning the points downe on the redeye 2 and skoll which is on the 24R approach. Both of the points are at 10000 ft; and the aircraft would sometimes continue the descent ignoring the 2nd constraint altitude.pay very close attention to the automation on any arrival that has two consecutive points of the same altitude on an arrival/approach. There was a warning that was published years ago about the lax arrivals for similar circumstances. As you can see; the way this problem was fixed (at lax) was by rewriting the arrivals so that there were no two points with the same altitudes.
Original NASA ASRS Text
Title: A321 flight crew reported a continued problem with the FMS complying with the altitude restrictions on the RAVNN6 Arrival into BWI.
Narrative: We were cleared to descend via the RAVNN 6 arrival and I had read the warning from the union about problems on this arrival. The aircraft reached FL230 at FZEEK. Constraint was displayed in the FMA indicating that the aircraft would stop descent and hold FL230. When the aircraft reached 200 ft above FZEEK; the autopilot reverted from managed descent mode to basic mode vertical speed. I quickly mashed the altitude button; forcing the aircraft to level off. The [FMC] shows that the aircraft will join the descent profile just before reaching FZEEK where a constraint altitude is set up. It shows the aircraft will continue the descent passing WHHTE. I think there must be a problem in the Jeppesen coding of the arrival; but this reminds me of other reports I wrote concerning the points DOWNE on the REDEYE 2 and SKOLL which is on the 24R approach. Both of the points are at 10000 ft; and the aircraft would sometimes continue the descent ignoring the 2nd constraint altitude.Pay very close attention to the automation on any arrival that has two consecutive points of the same altitude on an arrival/approach. There was a warning that was published years ago about the LAX arrivals for similar circumstances. As you can see; the way this problem was fixed (at LAX) was by rewriting the arrivals so that there were no two points with the same altitudes.
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.