37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1358869 |
Time | |
Date | 201605 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | CRP.TRACON |
State Reference | TX |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 146 |
Events | |
Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
We were assigned the RNAV (GPS) runway 18 into corpus christi. ATC gave us direct to cavla intersection; told us to cross cavla at 2100 ft and cleared us for the approach. The pilot flying set 1700 ft into the altitude window and verified that LNAV and VNAV were active. As we descended towards cavla; the pilot flying entered a speed at cavla of 200 knots. It took a long while for VNAV to compute the new input. As we were about to cross cavla; VNAV disconnected. I pointed this out to the pilot flying and we dipped slightly under 2100 ft. He reestablished the aircraft at 2100 ft and then set the altitude selector to zeros and started a vertical speed of around 1000 ft fpm descent. The next fix on the approach was peers and the charted altitude is 1700 ft. Although I knew he had already set zero in the altitude window; when I looked at the nd (navigation display) I noticed that the range to altitude line was right at peers intersection. Forgetting for a moment that he had set zeros; I thought that we were on profile to cross peers at 1700 ft; but we were actually on a glidepath that was putting us well below the correct altitude. When I figured this out I mentioned to the pilot flying that we should set 1700 ft in the altitude selector as we were no longer in VNAV; but by that time we were already flying below 1700 ft. We were around 1400 ft when the pilot flying corrected the altitude and climbed back up to 1700 ft. We were in VMC conditions with the airport in sight. The flight landed without further incident.
Original NASA ASRS Text
Title: Air carrier flight crew descended below cleared altitude while on an RNAV approach to CRP.
Narrative: We were assigned the RNAV (GPS) Runway 18 into Corpus Christi. ATC gave us direct to CAVLA intersection; told us to cross CAVLA at 2100 ft and cleared us for the approach. The Pilot Flying set 1700 ft into the altitude window and verified that LNAV and VNAV were active. As we descended towards CAVLA; the Pilot Flying entered a speed at CAVLA of 200 knots. It took a long while for VNAV to compute the new input. As we were about to cross CAVLA; VNAV disconnected. I pointed this out to the Pilot Flying and we dipped slightly under 2100 ft. He reestablished the aircraft at 2100 ft and then set the altitude selector to zeros and started a Vertical Speed of around 1000 ft fpm descent. The next fix on the approach was PEERS and the charted altitude is 1700 ft. Although I knew he had already set zero in the altitude window; when I looked at the ND (Navigation Display) I noticed that the range to altitude line was right at PEERS intersection. Forgetting for a moment that he had set zeros; I thought that we were on profile to cross PEERS at 1700 ft; but we were actually on a glidepath that was putting us well below the correct altitude. When I figured this out I mentioned to the Pilot Flying that we should set 1700 ft in the altitude selector as we were no longer in VNAV; but by that time we were already flying below 1700 ft. We were around 1400 ft when the Pilot Flying corrected the altitude and climbed back up to 1700 ft. We were in VMC conditions with the airport in sight. The flight landed without further incident.
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.