 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A300 captain reported that an autothottle malfunction resulted in a thrust imbalance on takeoff; and was initially mistaken for an engine failure.
| Attributes | |
| ACN | 1690490 |
| Time | |
| Date | 201910 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | A300 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Takeoff |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Autothrottle/Speed Control |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
On takeoff at about 500 ft. AGL; the number one engine began rolling back. We initially thought we had an engine failure and about the same time tower contacted us to switch to departure at which time we notified tower we thought we had an engine failure and [advised ATC]. We were instructed to fly runway heading and we continued our climb to 5;000 ft. I got the autopilot on and looked down and saw the number one throttle was back at or near idle; and saw the ECAM message of asymmetrical throttles. We saw the #1 engine was still operating within normal parameters; just at a low N1. I then advanced the throttle to match the number 2 throttle and saw the engine was fine; just that the number one throttle went back to idle for no apparent reason. After we brought the power back up; checked all engine parameters; and went through the QRH procedure; we concluded nothing was wrong with the engine and told ATC we did not need to [request priority handling] after all and we continued on to destination where we wrote up the incident and deferred the auto throttles. We concluded the auto throttle reduced the number one engine to at or near idle for no obvious reason.
Original NASA ASRS Text
Title: A300 Captain reported that an autothottle malfunction resulted in a thrust imbalance on takeoff; and was initially mistaken for an engine failure.
Narrative: On takeoff at about 500 ft. AGL; the number one engine began rolling back. We initially thought we had an engine failure and about the same time Tower contacted us to switch to departure at which time we notified Tower we thought we had an engine failure and [advised ATC]. We were instructed to fly runway heading and we continued our climb to 5;000 ft. I got the autopilot on and looked down and saw the number one throttle was back at or near idle; and saw the ECAM message of asymmetrical throttles. We saw the #1 engine was still operating within normal parameters; just at a low N1. I then advanced the throttle to match the number 2 throttle and saw the engine was fine; just that the number one throttle went back to idle for no apparent reason. After we brought the power back up; checked all engine parameters; and went through the QRH procedure; we concluded nothing was wrong with the engine and told ATC we did not need to [request priority handling] after all and we continued on to destination where we wrote up the incident and deferred the auto throttles. We concluded the auto throttle reduced the number one engine to at or near idle for no obvious reason.
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.