Flight Control Problem Could be the Autopilot
Moderators: sky's the limit, sepia, Sulako, lilfssister, North Shore
Flight Control Problem Could be the Autopilot
It makes sense that an inadvertent autopilot activation could cause confusion. Something to consider when analyzing a flight control issue.....
"C-GOVX, a Piper Navajo PA-31 operated by Les Levées Aéroscan Inc., was on a flight of
aerial photograph according to visual flight rules under the code SCANNER1 from the airport
from Quebec / Jean Lesage, QC (CYQB) with 2 crew members on board. While the device
was flying following a line of aerial photographs at an altitude of 13,000 feet, the pilot with
controls felt the aircraft stick suddenly stiffen in the roll axis. By forcing
with two hands in order to keep the stick straight and prevent the aircraft from making a turn, the pilot in
Controls declared an emergency and the aircraft returned to land on runway 25 at CYQB. Once
with the aircraft parked, it was noted that the autopilot's "ROLL" function button was
triggered. By disabling it, the controls are returned to normal. An inspection of the
maintenance concluded that there was no technical anomaly in the piloting system
automatic."
"C-GOVX, a Piper Navajo PA-31 operated by Les Levées Aéroscan Inc., was on a flight of
aerial photograph according to visual flight rules under the code SCANNER1 from the airport
from Quebec / Jean Lesage, QC (CYQB) with 2 crew members on board. While the device
was flying following a line of aerial photographs at an altitude of 13,000 feet, the pilot with
controls felt the aircraft stick suddenly stiffen in the roll axis. By forcing
with two hands in order to keep the stick straight and prevent the aircraft from making a turn, the pilot in
Controls declared an emergency and the aircraft returned to land on runway 25 at CYQB. Once
with the aircraft parked, it was noted that the autopilot's "ROLL" function button was
triggered. By disabling it, the controls are returned to normal. An inspection of the
maintenance concluded that there was no technical anomaly in the piloting system
automatic."
Re: Flight Control Problem Could be the Autopilot
I would say the AP functioned perfectly. Perhaps a better way to think of it is the flight control problem was due to the AP, but possibly caused by poor automation mode awareness, bad SOP, misuse of SOP, poor training/misunderstanding of AP function.
Re: Flight Control Problem Could be the Autopilot
Or bad design. You should always be able to overcome an autopilot.
Going for the deck at corner
Re: Flight Control Problem Could be the Autopilot
The pilot did overcome the autopilot and landed the aircraft.
Re: Flight Control Problem Could be the Autopilot
Overcome as in kick the autopilot mode off.
Going for the deck at corner
-
- Rank 5
- Posts: 341
- Joined: Thu Aug 12, 2004 3:25 am
Re: Flight Control Problem Could be the Autopilot
Oh THAT overcome.
Not the overcome as in overcome.
Not the overcome as in overcome.
"I'd rather have it and not need than to need it and not have it" Capt. Augustus McCrae.
Re: Flight Control Problem Could be the Autopilot
I'm no longer sure what we are talking about. From what I read, the autopilot could have been switched off but was not. The pilot physically overcame the autopilot to land the aircraft.
Re: Flight Control Problem Could be the Autopilot
It might be something to check if the flight controls suddenly become stiff.
Re: Flight Control Problem Could be the Autopilot
In the aircraft I fly, when you put a certain control force against the autopilot commands, the autopilot will automatically disengage that axis as it generally means that you purposely want to do something else than what the autopilot is commanding. This design should be incorporated in every autopilot.
Going for the deck at corner
- KISS_MY_TCAS
- Rank 5
- Posts: 339
- Joined: Tue Mar 09, 2004 7:31 am
- Location: ask your mom, she knows!
Re: Flight Control Problem Could be the Autopilot
Every autopilot I've ever seen works this way, the servos have clutches that when a specified force is applied to the column or flight control, the servo will command the computer to disengage. It is measured at the servo by the amount of torque the servo needs to generate to maintain the selected command, any more than that value it should disconnect. Either bad info in the report, or a dangerously malfunctioning autopilot.AuxBatOn wrote: ↑Sat Aug 22, 2020 8:58 pm
In the aircraft I fly, when you put a certain control force against the autopilot commands, the autopilot will automatically disengage that axis as it generally means that you purposely want to do something else than what the autopilot is commanding. This design should be incorporated in every autopilot.
Re: Flight Control Problem Could be the Autopilot
Ah I understand now.
When an aircraft has hydraulically actuated flight controls, the autopilot obviously cannot be overcome by human force, hence the need for it to sense the input and disconnect. In any aircraft I am familiar with this is a last resort and not the "correct" way to disconnect the autopilot.
When flight controls are directly connected to the control surfaces and the servos are connected to the control run, the servo doesn't know the difference between aerodynamic forces and pilot control inputs. The clutches are adjusted so that they don't slip from aerodynamic forces, but are kept low enough so that the pilot can overpower the servos. If there is a problem with the autopilot, the human pilot overpowers it, turns it off, and then removes power to the autopilot via switch or breaker.
This is the nature of these autopilots. While it would be theoretically possible to add something into the controls runs to sense whether each push or pull is coming from the control end or the surface end, I would think the downside of the added complexity would outweigh any gains.
When an aircraft has hydraulically actuated flight controls, the autopilot obviously cannot be overcome by human force, hence the need for it to sense the input and disconnect. In any aircraft I am familiar with this is a last resort and not the "correct" way to disconnect the autopilot.
When flight controls are directly connected to the control surfaces and the servos are connected to the control run, the servo doesn't know the difference between aerodynamic forces and pilot control inputs. The clutches are adjusted so that they don't slip from aerodynamic forces, but are kept low enough so that the pilot can overpower the servos. If there is a problem with the autopilot, the human pilot overpowers it, turns it off, and then removes power to the autopilot via switch or breaker.
This is the nature of these autopilots. While it would be theoretically possible to add something into the controls runs to sense whether each push or pull is coming from the control end or the surface end, I would think the downside of the added complexity would outweigh any gains.
-
- Rank 2
- Posts: 97
- Joined: Wed Jun 04, 2008 12:36 pm
Re: Flight Control Problem Could be the Autopilot
Have a look at the series of MD11 pitch control incidents which in some cases killed people. Some involved the autopilot being overpowered by the pilot and then re-engaging in pitch. Aft C of G created instability and the resulting pitch oscillations produced large +/- g forces.
-
- Top Poster
- Posts: 8132
- Joined: Tue Apr 15, 2008 12:25 pm
- Location: Winterfell...
Re: Flight Control Problem Could be the Autopilot
Yes. It’s child’s play to introduce a disconnect system into an irreversible powered flight control system or a FBW aircraft.
Not so much at the small, manual, general aviation side of things. All they have is a clutch or servo you can overpower, or a button to disconnect.
Not so much at the small, manual, general aviation side of things. All they have is a clutch or servo you can overpower, or a button to disconnect.
Geez did I say that....? Or just think it....?
-
- Top Poster
- Posts: 5868
- Joined: Wed Feb 18, 2004 7:17 pm
- Location: West Coast
Re: Flight Control Problem Could be the Autopilot
As a general comment auto pilot systems knowledge seems to be week in the 703 world. At one 703 company I flew for, not one pilot knew how to do a pre-flight function check for the KFC 200 autopilot. They also did not understand why you never want to give the wheel a nudge when the auto pilot was working.
Re: Flight Control Problem Could be the Autopilot
You cannot physically overcome or disengage the autopilot in the DH8 100/300/400 by applying any amount of force to the control column. Also, there is no way to disengage pitch or roll A/P functions separately. You can temporarily disengage the A/P with the TCS button on the control column, but the A/P will automatically reengage when you let go of the button.
Re: Flight Control Problem Could be the Autopilot
So how do you disconnect the autopilot on a dash 8 then?
It's also worth noting that if ease of disconnection is an overriding factor, the B737 is probably the best system out there. Just look at it the wrong way and it disconnects.
It's also worth noting that if ease of disconnection is an overriding factor, the B737 is probably the best system out there. Just look at it the wrong way and it disconnects.
Re: Flight Control Problem Could be the Autopilot
That is actually bad news as well. I have seen the aircraft drifting off course because the control wheel was accidentally bumped which disconnected the lateral mode.
Now I always check the modes when the control wheel is bumped, although the newer types seem less susceptible to this happening
Re: Flight Control Problem Could be the Autopilot
Here are the ways to disconnect the auto pilot in a Dash 8 ... from the Q400 AOM ... including failure modes and inhibits -
Bullet 8 contradicts what airway said above.
The flight crew disengage the AP manually using the AP or YD pushbutton on the FGCP. The flight crew also manually disengage the AP by pressing an AP Disengage Switch, by selecting Go Around or by operating manual pitch trim.
The Autopilot disengages when one of the following conditions is met:
1• AHRS 1 or AHRS 2 is failed.
2• AHRS 1 and AHRS 2 disagree.
3• ADC 1 or ADC 2 is failed.
4• ADC 1 and ADC 2 disagree.
5• The aeroplane is not airborne.
6• The crew press the AP or YD pushbutton on the FGCP (manual disengagement).
7• The crew operates manual pitch trim, setting the Manual Pitch Trim AP Disconnect discrete, except if
TCS is active (automatic disengagement).
8• The crew manually override the AP using the control column.
9• The crew press an AP Disengage Switch (manual disengagement).
10• The TCS function fails.
11• A Stall Warning AP Disconnect discrete from SPM 1 or SPM 2 is set.
12• A GA switch is selected (manual disengagement).
13• An AP actuator failure is detected.
14• The Yaw Damper disengages automatically.
15• Internal AFCS monitoring is failed.
16• A Power interrupt greater than the transparency time occurs.
17• The aeroplane attitude is outside the domain limits
Bullet 8 contradicts what airway said above.
The flight crew disengage the AP manually using the AP or YD pushbutton on the FGCP. The flight crew also manually disengage the AP by pressing an AP Disengage Switch, by selecting Go Around or by operating manual pitch trim.
The Autopilot disengages when one of the following conditions is met:
1• AHRS 1 or AHRS 2 is failed.
2• AHRS 1 and AHRS 2 disagree.
3• ADC 1 or ADC 2 is failed.
4• ADC 1 and ADC 2 disagree.
5• The aeroplane is not airborne.
6• The crew press the AP or YD pushbutton on the FGCP (manual disengagement).
7• The crew operates manual pitch trim, setting the Manual Pitch Trim AP Disconnect discrete, except if
TCS is active (automatic disengagement).
8• The crew manually override the AP using the control column.
9• The crew press an AP Disengage Switch (manual disengagement).
10• The TCS function fails.
11• A Stall Warning AP Disconnect discrete from SPM 1 or SPM 2 is set.
12• A GA switch is selected (manual disengagement).
13• An AP actuator failure is detected.
14• The Yaw Damper disengages automatically.
15• Internal AFCS monitoring is failed.
16• A Power interrupt greater than the transparency time occurs.
17• The aeroplane attitude is outside the domain limits
Re: Flight Control Problem Could be the Autopilot
If an autopilot is unable to cope with the forces it is subjected to (regardless of pilot input or aerodynamic forces) it should disconnect. It is a fairly simple logic to implement (if the difference between the commanded output and the actual output grows by y over x seconds, disconnect). It means the autopilot is not able to do its task and control should be handed back to the pilot.iflyforpie wrote: ↑Sun Aug 23, 2020 8:34 am Yes. It’s child’s play to introduce a disconnect system into an irreversible powered flight control system or a FBW aircraft.
Not so much at the small, manual, general aviation side of things. All they have is a clutch or servo you can overpower, or a button to disconnect.
Going for the deck at corner