37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1366013 |
Time | |
Date | 201606 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | STP.Airport |
State Reference | MN |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citation V/Ultra/Encore (C560) |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | Autopilot |
Person 1 | |
Function | Pilot Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Altitude Overshoot Deviation - Procedural Clearance |
Narrative:
We were given a crossing restriction at bitlr of 6;000 ft MSL. We started out of FL200 roughly 50-60 nm out from bitlr. Prior to bitlr we requested direct to rulde off the GPS rwy 32 in stp. The controller came back and stated that he would clear us instead to babco off the ILS rwy 32 in 10 miles. At 1000 ft prior to level off (6;000 ft). The altitude alert did chime and the light indicator came on and we also verified that the autopilot was armed to capture at 6;000 ft. During this time we got cleared to babco intersection for the visual rwy. 32 into stp. The pm was then entering in the waypoint into the FMS and the PF was both flying and watching the pm entering the information into the FMS. So; around 800 ft below the altitude assigned; the PF reacted by disengaging the autopilot; applying power and pitch up to climb back 6000 ft upon reaching 6000 ft; the autopilot was reengaged and no further issues. At no time did msp approach say anything about our altitude. The crew did note that the altitude alert system did not alert them to being 200 ft low during this event.during the next flight; the crew noticed several times that the altitude select on the #2 autopilot was disarming and at no time were there any altitude deviations. Each time that there was a new altitude; the altitude alert functioned properly. Approximately 200 ft prior to level off; the attitude select would disarm. The crew determined that the #2 autopilot is malfunctioning at which point #1 autopilot was used for the remainder of that flight. Once on the ground; the crew notified maintenance.
Original NASA ASRS Text
Title: CE-560 flight crew reported overshooting an altitude restriction when the #2 autopilot malfunctioned.
Narrative: We were given a crossing restriction at BITLR of 6;000 ft MSL. We started out of FL200 roughly 50-60 nm out from BITLR. Prior to BITLR we requested direct to RULDE off the GPS Rwy 32 in STP. The controller came back and stated that he would clear us instead to BABCO off the ILS Rwy 32 in 10 miles. At 1000 ft prior to level off (6;000 ft). The altitude alert did chime and the light indicator came on and we also verified that the autopilot was armed to capture at 6;000 ft. During this time we got cleared to BABCO intersection for the visual Rwy. 32 into STP. The PM was then entering in the waypoint into the FMS and the PF was both flying and watching the PM entering the information into the FMS. So; around 800 ft below the altitude assigned; the PF reacted by disengaging the autopilot; applying power and pitch up to climb back 6000 ft Upon reaching 6000 ft; the autopilot was reengaged and no further issues. At no time did MSP approach say anything about our altitude. The crew did note that the altitude alert system did NOT alert them to being 200 ft low during this event.During the next flight; the crew noticed several times that the altitude select on the #2 autopilot was disarming and at no time were there any altitude deviations. Each time that there was a new altitude; the altitude alert functioned properly. Approximately 200 ft prior to level off; the attitude select would DISARM. The crew determined that the #2 autopilot is malfunctioning at which point #1 autopilot was used for the remainder of that flight. Once on the ground; the crew notified maintenance.
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.