37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1609145 |
Time | |
Date | 201901 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Falcon 20FJF/20C/20D/20E/20F |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Route In Use | Vectors |
Flight Plan | IFR |
Component | |
Aircraft Component | Autoflight System |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 25 Flight Crew Total 17500 Flight Crew Type 80 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance |
Miss Distance | Horizontal 26000 Vertical 1100 |
Narrative:
While cruising at FL360; we were told by ATC center to descend in less than 2 minutes to FL340; and turn to heading 220. I am not sure what order those instructions were given. I was the pilot flying. I decided to initially start my descent around 2;000 feet a minute; to guarantee compliance. I uncoupled altitude hold on the aps-80 autopilot; and engaged altitude select; I started the airplane descending by rolling the autopilot vertical trim wheel down. The only way to know how much trim has been imputed is by watching the airplane react. I also selected the heading mode and turned the airplane to [heading] 220; I am not sure about the sequence. The airplane was descending at 2;000 feet per minute plus; at approximately 35;000 feet; I used the autopilot trim wheel to slow the descent. After slowing the descent and at approximately 34;400 feet; both pilots called out that the altitude select mode was engaged; because we know that it is imperative to check that the altitude select mode is engaged; as it sometimes disengages without warning. We both saw the airplane leveling at FL340.ATC center gave us a direct to zzzzz intersection and a frequency change. I [entered] direct to zzzzz in the left FMS; while the other pilot changed frequencies and updated his FMS.I looked at the altimeter and noticed that the airplane was climbing through approximately 35;000 feet at a high rate of climb. I did not hear an altitude alert. I shouted a couple of expletives getting the other pilots attention; disengaged the autopilot and rapidly descended back to FL340. During that time; I heard our TCAS I report a traffic alert. I looked out the window; but did not see any traffic. We were also given instructions by ATC center again to descend to FL340 during the time we were recovering from the uncommanded climb. The most reasonable answer for this situation is a late and over-correcting with the autopilot trim wheel; but to the best of my knowledge I did not do that. I also fly a falcon 10 with a similar autopilot. The little experience I have had with these airplanes has taught me not to over correct or correct the rate of assent or descent close to the programmed altitude. It is possible that we had a trim malfunction or runaway. I have experienced autopilot runaway on older airplanes with similar autopilots.although we were not excessively busy; the need for an immediate descent; a heading change; a direct to; and a frequency change in less than two minutes was probably a contributing factor; taking our full attention from noting a total completion of the level off.
Original NASA ASRS Text
Title: Falcon 20 First Officer reported an autopilot issue resulted in an altitude excursion and TCAS Traffic Advisory.
Narrative: While cruising at FL360; we were told by ATC Center to descend in less than 2 minutes to FL340; and turn to heading 220. I am not sure what order those instructions were given. I was the Pilot Flying. I decided to initially start my descent around 2;000 feet a minute; to guarantee compliance. I uncoupled altitude hold on the APS-80 autopilot; and engaged altitude select; I started the airplane descending by rolling the autopilot vertical trim wheel down. The only way to know how much trim has been imputed is by watching the airplane react. I also selected the heading mode and turned the airplane to [heading] 220; I am not sure about the sequence. The airplane was descending at 2;000 feet per minute plus; at approximately 35;000 feet; I used the autopilot trim wheel to slow the descent. After slowing the descent and at approximately 34;400 feet; both pilots called out that the altitude select mode was engaged; because we know that it is imperative to check that the altitude select mode is engaged; as it sometimes disengages without warning. We both saw the airplane leveling at FL340.ATC Center gave us a direct to ZZZZZ intersection and a frequency change. I [entered] Direct to ZZZZZ in the left FMS; while the other pilot changed frequencies and updated his FMS.I looked at the altimeter and noticed that the airplane was climbing through approximately 35;000 feet at a high rate of climb. I did not hear an altitude alert. I shouted a couple of expletives getting the other pilots attention; disengaged the autopilot and rapidly descended back to FL340. During that time; I heard our TCAS I report a traffic alert. I looked out the window; but did not see any traffic. We were also given instructions by ATC Center again to descend to FL340 during the time we were recovering from the uncommanded climb. The most reasonable answer for this situation is a late and over-correcting with the autopilot trim wheel; but to the best of my knowledge I did not do that. I also fly a Falcon 10 with a similar autopilot. The little experience I have had with these airplanes has taught me not to over correct or correct the rate of assent or descent close to the programmed altitude. It is possible that we had a trim malfunction or runaway. I have experienced autopilot runaway on older airplanes with similar autopilots.Although we were not excessively busy; the need for an immediate descent; a heading change; a Direct to; and a frequency change in less than two minutes was probably a contributing factor; taking our full attention from noting a total completion of the level off.
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.