37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1646734 |
Time | |
Date | 201905 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | RIC.Airport |
State Reference | VA |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | EMB ERJ 170/175 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
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 - Altitude Crossing Restriction Not Met Deviation - Altitude Undershoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
From the SPIDR3 arrival; which ends at deeer; we were cleared for the RNAV rnp Y runway 16; deeer transition. The last hard altitude on the STAR is spidr at 8;000 [feet]. The first altitude restriction on the approach is deeer; 9 miles after spidr; at 4;000 [feet]. The FMS showed a hard altitude of 4;000 [feet] at deeer. The vertical profile showed a hard altitude at deeer depicted with the magenta lines above and below the number 4;000; and the aircraft was in VNAV mode; on pth. Without any 'unable next altitude' message; the plane crossed deer at 5;700 [feet] (while the vertical profile depicted us precisely on pth and at 4;000 [feet]) and continued towards the next fix sooby which was correctly depicted as at or above 4;000 [feet]. Upon realizing the error; we overrode the automation to expedite the descent to 4;000 [feet]; then re-engaged VNAV. The controller never mentioned our altitude; only conversing nearly continuously with a VFR aircraft just west of our course; trying to keep them and us constantly aware of each other's position. As far as we can tell; this was an automation error. We were able to duplicate the altitude assignments after blocking in; and reprogramming the FMS for the arrival and approach. It once again depicted spidr at 8;000 [feet]; deeer at 4;000 [feet]; and sooby at or above 4;000 [feet]. All correct. Contributing to the automation error may have been the large descent required from spidr to deeer; dropping 4;000 feet in just nine miles. Our understanding is that if the FMS thought this was not possible; we should have gotten an 'unable next altitude' message; or the vertical profile should have depicted us high at deeer. Neither happened. Please correct us if it is apparent that there is something about RNAV approaches or FMS usage that we do not understand. Otherwise; please consult with the designers of this arrival/approach to change the altitude restriction at deeer to 'at or above.'
Original NASA ASRS Text
Title: EMB-175 Captain reported a lack of agreement between the SPDR 3 RNAV arrival termination fix and the mandatory altitude at the IAF of the RNAV (RNP) Y RWY 16 approach into RIC airport.
Narrative: From the SPIDR3 arrival; which ends at DEEER; we were cleared for the RNAV RNP Y RWY 16; DEEER transition. The last hard altitude on the STAR is SPIDR at 8;000 [feet]. The first altitude restriction on the approach is DEEER; 9 miles after SPIDR; at 4;000 [feet]. The FMS showed a hard altitude of 4;000 [feet] at DEEER. The vertical profile showed a hard altitude at DEEER depicted with the magenta lines above and below the number 4;000; and the aircraft was in VNAV mode; on PTH. Without any 'unable next altitude' message; the plane crossed DEER at 5;700 [feet] (while the vertical profile depicted us precisely on PTH and at 4;000 [feet]) and continued towards the next fix SOOBY which was correctly depicted as at or above 4;000 [feet]. Upon realizing the error; we overrode the automation to expedite the descent to 4;000 [feet]; then re-engaged VNAV. The Controller never mentioned our altitude; only conversing nearly continuously with a VFR aircraft just west of our course; trying to keep them and us constantly aware of each other's position. As far as we can tell; this was an automation error. We were able to duplicate the altitude assignments after blocking in; and reprogramming the FMS for the arrival and approach. It once again depicted SPIDR at 8;000 [feet]; DEEER at 4;000 [feet]; and SOOBY at or above 4;000 [feet]. All correct. Contributing to the automation error may have been the large descent required from SPIDR to DEEER; dropping 4;000 feet in just nine miles. Our understanding is that if the FMS thought this was not possible; we should have gotten an 'unable next altitude' message; OR the Vertical profile should have depicted us high at DEEER. Neither happened. Please correct us if it is apparent that there is something about RNAV approaches or FMS usage that we do not understand. Otherwise; please consult with the designers of this arrival/approach to change the altitude restriction at DEEER to 'at or above.'
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.